[Desktop-packages] [Bug 1302348] [NEW] after today's Trusty updates/restart, NM will not connect to wifi
Public bug reported: I see all the wireless signals in the neighborhood, but the connect button does not connect my laptop to the internet. Also, history seems lost, as it reports that my wifi has never been used, when it was in use a few minutes before. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: network-manager 0.9.8.8-0ubuntu5 ProcVersionSignature: Ubuntu 3.13.0-22.44-generic 3.13.8 Uname: Linux 3.13.0-22-generic x86_64 ApportVersion: 2.14-0ubuntu1 Architecture: amd64 CurrentDesktop: KDE Date: Thu Apr 3 22:43:11 2014 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2013-06-18 (289 days ago) InstallationMedia: Kubuntu 13.04 Raring Ringtail - Release amd64 (20130424) IpRoute: default via 192.168.15.1 dev eth0 proto static 192.168.15.0/24 dev eth0 proto kernel scope link src 192.168.15.3 metric 1 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: network-manager UpgradeStatus: Upgraded to trusty on 2014-03-04 (30 days ago) ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1302348 Title: after today's Trusty updates/restart, NM will not connect to wifi Status in “network-manager” package in Ubuntu: New Bug description: I see all the wireless signals in the neighborhood, but the connect button does not connect my laptop to the internet. Also, history seems lost, as it reports that my wifi has never been used, when it was in use a few minutes before. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: network-manager 0.9.8.8-0ubuntu5 ProcVersionSignature: Ubuntu 3.13.0-22.44-generic 3.13.8 Uname: Linux 3.13.0-22-generic x86_64 ApportVersion: 2.14-0ubuntu1 Architecture: amd64 CurrentDesktop: KDE Date: Thu Apr 3 22:43:11 2014 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2013-06-18 (289 days ago) InstallationMedia: Kubuntu 13.04 Raring Ringtail - Release amd64 (20130424) IpRoute: default via 192.168.15.1 dev eth0 proto static 192.168.15.0/24 dev eth0 proto kernel scope link src 192.168.15.3 metric 1 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: network-manager UpgradeStatus: Upgraded to trusty on 2014-03-04 (30 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1302348/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1299499] Re: kwin crashes on desktop startup with wobbly windows enabled
Martin: did you try with a clean session, or tried to enable the effects? Just logging out / in doesn't do anything. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1299499 Title: kwin crashes on desktop startup with wobbly windows enabled Status in Mesa: Confirmed Status in “mesa” package in Ubuntu: Confirmed Bug description: kwin reports a crash while starting up, and desktop effects are not enabled for the session. ProblemType: Crash DistroRelease: Ubuntu 14.04 Package: kde-window-manager 4:4.11.8-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-20.42-generic 3.13.7 Uname: Linux 3.13.0-20-generic x86_64 ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 AssertionMessage: kwin: ../../../../../../../src/mesa/drivers/dri/i965/brw_reset.c:43: brw_get_graphics_reset_status: Assertion `brw-hw_ctx != ((void *)0)' failed. CrashCounter: 1 CurrentDesktop: KDE Date: Sat Mar 29 11:11:04 2014 ExecutablePath: /usr/bin/kwin InstallationDate: Installed on 2014-02-03 (53 days ago) InstallationMedia: Ubuntu-Server 13.10 Saucy Salamander - Release amd64 (20131016) ProcCmdline: /usr/bin/kwin --crashes 2 ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash Signal: 6 SourcePackage: kde-workspace StacktraceTop: __GI_raise (sig=sig@entry=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:56 __GI_abort () at abort.c:89 __assert_fail_base (fmt=0x7f7a0d7c2718 %s%s%s:%u: %s%sAssertion `%s' failed.\n%n, assertion=assertion@entry=0x7f79edba7a63 brw-hw_ctx != ((void *)0), file=file@entry=0x7f79edba7a28 ../../../../../../../src/mesa/drivers/dri/i965/brw_reset.c, line=line@entry=43, function=function@entry=0x7f79edba7a80 brw_get_graphics_reset_status) at assert.c:92 __GI___assert_fail (assertion=0x7f79edba7a63 brw-hw_ctx != ((void *)0), file=0x7f79edba7a28 ../../../../../../../src/mesa/drivers/dri/i965/brw_reset.c, line=43, function=0x7f79edba7a80 brw_get_graphics_reset_status) at assert.c:101 ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so Title: kwin assert failure: kwin: ../../../../../../../src/mesa/drivers/dri/i965/brw_reset.c:43: brw_get_graphics_reset_status: Assertion `brw-hw_ctx != ((void *)0)' failed. UpgradeStatus: Upgraded to trusty on 2014-03-03 (26 days ago) UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1299499/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1298611] Re: [FFe] apparmor signal and ptrace mediation
The debdiff attached for apparmor looks good, aside from missing some Breaks: on the old versions of the packages that need to go in at the same time (because their policies will cease to be sufficient once ptrace/signal mediation support lands). Jamie has pushed the added Breaks; once they're available, I'm ok with this going in. ** Changed in: apparmor (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1298611 Title: [FFe] apparmor signal and ptrace mediation Status in “apparmor” package in Ubuntu: Confirmed Status in “apparmor-easyprof-ubuntu” package in Ubuntu: New Status in “libvirt” package in Ubuntu: New Status in “lightdm” package in Ubuntu: New Status in “linux” package in Ubuntu: Fix Released Status in “lxc” package in Ubuntu: New Bug description: Background: kernel and apparmor userspace updates to support signal and ptrace mediation. These packages are listed in one bug because they are related, but the FFes may be granted and the uploads may happen at different times. = linux = Summary: This feature freeze exception is requested for signal and ptrace mediation via apparmor in the kernel. When used with a compatible apparmor userspace, signals and ptrace rules are supported. When used without a compatible apparmor userspace (eg, on a precise system with a trusty backport kernel), signal and ptrace mediation is not enforced (ie, you can use this kernel with an old userspace without any issues). The fine grained mediation of signals and ptraces also incorporates improved versioning support that allows this kernel to better support older and newer userspaces. This allows for this version of the kernel to work as a backport kernel unmodified (currently a patch and config are used to provide backport kernels). The kernel patch is available at git://kernel.ubuntu.com/jj/ubuntu-trusty.git in the trusty-alpha6 branch apparmor-alpha6-sync Testing: * 12.04 system with backported kernel: DONE * test-apparmor.py: PASS (runs extensive tests (upstream and distro)) * exploratory manual testing: PASS (networking, aa-enforce with firefox, firefox works, apparmor blocks access, etc) * aa-status: PASS * lxc: PASS (containers can be created, started, shutdown) * libvirt: PASS (VMs started via openstack, and test-libvirt.py from QRT passes all tests) * 14.04 system (non-Touch) with current apparmor userspace: DONE (relevant parts of https://wiki.ubuntu.com/Process/Merges/TestPlans/AppArmor) * test-apparmor.py: PASS (runs extensive tests (upstream and distro)) * exploratory manual testing: PASS (networking, aa-enforce with firefox, firefox works, apparmor blocks access, etc) * aa-status: PASS * lxc: PASS (containers can be created, started, shutdown) * libvirt: PASS (QRT/script/test-libvirt.py (though there are 3 failures unrelated to apparmor)) * click-apparmor QRT touch image tests: PASS * apparmor-easyprof-ubuntu QRT touch image tests: PASS * 14.04 system (non-Touch) with updated apparmor userspace capable of supporting signal and ptrace mediation: DONE (relevant parts of https://wiki.ubuntu.com/Process/Merges/TestPlans/AppArmor. Note: this is marked 'done' from the kernel perspective-- the apparmor userspace upload is being prepared and tests assume userspace is using latest patches on the list) * test-apparmor.py: PASS (runs extensive tests (upstream and distro)) * exploratory manual testing: PASS (networking, aa-enforce with firefox, firefox works, apparmor blocks access, etc) * aa-status: PASS * lxc: PASS (containers can be created, started, shutdown) * libvirt: PASS (QRT/script/test-libvirt.py (though there are 3 failures unrelated to apparmor)) * click-apparmor QRT touch image tests: PASS * apparmor-easyprof-ubuntu QRT touch image tests: PASS Justification: This feature is required to support comprehensive application confinement on Ubuntu Touch. This feature adds a significant security benefit to libvirt's qemu guest isolation which is fundamental to Ubuntu on Server/Cloud. This feature also adds a welcome improvement to administrators wishing to further protect their systems. = apparmor userspace = Summary: This feature freeze exception is requested for signal and ptrace mediation for apparmor userspace. When used with a compatible kernel, signals and ptrace rules are supported. When used without a compatible kernel (eg, on Ubuntu Touch for a few weeks or with upstream kernels), signal and ptrace rules are skipped (ie, you can use this userspace with other kernels without issue). Testing: * 14.04 system with current kernel (Touch, kernel doesn't have signal and ptrace mediation yet): * https://wiki.ubuntu.com/Process/Merges/TestPlans/AppArmor: PASS (includes click-apparmor, apparmor-easyprof-ubuntu,
[Desktop-packages] [Bug 1302353] [NEW] regression: ibus ignores keyboard layout
Public bug reported: The recent update of unity packages introduced a bad regression for ibus users. I assume the fault lies with unity since ibus hasn't been updated for several weeks and my machine was fine until about two days ago around which time some unity updates rolled in. I have a German keyboard layout (QWERTZ not QWERTY as in the US case). I use anthy and mozc for Japanese input. Since two days ago the default layout with the Japanese IME are a US layout throwing me off when blind- typing. To look into the matter, I opened ibus-setup and there are three Input methods listed there: English - English (US), Japanese - Anthy and Japanese -Mozc. German was conspicuously absent . I eventually managed to add a German layout to it but the next time I call ibus-setup the US layout is back as default. In other words, the explicit choice I'm trying to force doesn't stick. There are four keyboard layouts currently defined in System Settings - Text Entry - Input sources to use, none of them have anything to do with a US-layout; de1, de2, anthy and mozc. I cycle through them via Super+Space. Anthy is set to use the system default layout. The regression is that it currently inists on US layout with no way to even override this silly choice. ** Affects: unity (Ubuntu) Importance: Undecided Status: New ** Tags: regression-release trusty -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dp-unity https://bugs.launchpad.net/bugs/1302353 Title: regression: ibus ignores keyboard layout Status in “unity” package in Ubuntu: New Bug description: The recent update of unity packages introduced a bad regression for ibus users. I assume the fault lies with unity since ibus hasn't been updated for several weeks and my machine was fine until about two days ago around which time some unity updates rolled in. I have a German keyboard layout (QWERTZ not QWERTY as in the US case). I use anthy and mozc for Japanese input. Since two days ago the default layout with the Japanese IME are a US layout throwing me off when blind-typing. To look into the matter, I opened ibus-setup and there are three Input methods listed there: English - English (US), Japanese - Anthy and Japanese -Mozc. German was conspicuously absent . I eventually managed to add a German layout to it but the next time I call ibus-setup the US layout is back as default. In other words, the explicit choice I'm trying to force doesn't stick. There are four keyboard layouts currently defined in System Settings - Text Entry - Input sources to use, none of them have anything to do with a US-layout; de1, de2, anthy and mozc. I cycle through them via Super+Space. Anthy is set to use the system default layout. The regression is that it currently inists on US layout with no way to even override this silly choice. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1302353/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1302353] Re: regression: ibus ignores keyboard layout
** Description changed: The recent update of unity packages introduced a bad regression for ibus users. I assume the fault lies with unity since ibus hasn't been updated for several weeks and my machine was fine until about two days ago around which time some unity updates rolled in. I have a German keyboard layout (QWERTZ not QWERTY as in the US case). I use anthy and mozc for Japanese input. Since two days ago the default layout with the Japanese IME are a US layout throwing me off when blind- typing. To look into the matter, I opened ibus-setup and there are three Input methods listed there: English - English (US), Japanese - - Anthy and Japanese -Mozc. German was conspicuously absent (and it was - impossible to add in my default locale - see bug XXX). I eventually - managed to add a German layout to it but the next time I call ibus-setup - the US layout is back as default. In other words, the explicit choice - I'm trying to force doesn't stick. + Anthy and Japanese -Mozc. German was conspicuously absent . I + eventually managed to add a German layout to it but the next time I call + ibus-setup the US layout is back as default. In other words, the + explicit choice I'm trying to force doesn't stick. ** Description changed: The recent update of unity packages introduced a bad regression for ibus users. I assume the fault lies with unity since ibus hasn't been updated for several weeks and my machine was fine until about two days ago around which time some unity updates rolled in. I have a German keyboard layout (QWERTZ not QWERTY as in the US case). I use anthy and mozc for Japanese input. Since two days ago the default layout with the Japanese IME are a US layout throwing me off when blind- typing. To look into the matter, I opened ibus-setup and there are three Input methods listed there: English - English (US), Japanese - Anthy and Japanese -Mozc. German was conspicuously absent . I eventually managed to add a German layout to it but the next time I call ibus-setup the US layout is back as default. In other words, the explicit choice I'm trying to force doesn't stick. + + There are four keyboard layouts currently defined in System Settings - + Text Entry - Input sources to use, none of them have anything to do + with a US-layout; de1, de2, anthy and mozc. I cycle through them via + Super+Space. Anthy is set to use the system default layout. The + regression is that it currently inists on US layout with no way to even + override this silly choice. ** Also affects: ibus (Ubuntu) Importance: Undecided Status: New ** Description changed: The recent update of unity packages introduced a bad regression for ibus users. I assume the fault lies with unity since ibus hasn't been updated for several weeks and my machine was fine until about two days ago around which time some unity updates rolled in. I have a German keyboard layout (QWERTZ not QWERTY as in the US case). I use anthy and mozc for Japanese input. Since two days ago the default layout with the Japanese IME are a US layout throwing me off when blind- typing. To look into the matter, I opened ibus-setup and there are three Input methods listed there: English - English (US), Japanese - Anthy and Japanese -Mozc. German was conspicuously absent . I - eventually managed to add a German layout to it but the next time I call - ibus-setup the US layout is back as default. In other words, the - explicit choice I'm trying to force doesn't stick. + eventually managed to add a German layout to it and delete the US layout + but the next time I call ibus-setup the US layout is back as default. + In other words, the explicit choice I'm trying to force doesn't stick. There are four keyboard layouts currently defined in System Settings - Text Entry - Input sources to use, none of them have anything to do with a US-layout; de1, de2, anthy and mozc. I cycle through them via Super+Space. Anthy is set to use the system default layout. The regression is that it currently inists on US layout with no way to even override this silly choice. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dp-unity https://bugs.launchpad.net/bugs/1302353 Title: regression: ibus ignores keyboard layout Status in “ibus” package in Ubuntu: New Status in “unity” package in Ubuntu: New Bug description: The recent update of unity packages introduced a bad regression for ibus users. I assume the fault lies with unity since ibus hasn't been updated for several weeks and my machine was fine until about two days ago around which time some unity updates rolled in. I have a German keyboard layout (QWERTZ not QWERTY as in the US case). I use anthy and mozc for Japanese input. Since two days ago the default layout with the Japanese IME are a US layout
[Desktop-packages] [Bug 1301257] Re: rhythmbox crashed when syncing with iPad (iOS7.1)
** Bug watch added: GNOME Bug Tracker #727582 https://bugzilla.gnome.org/show_bug.cgi?id=727582 ** Also affects: rhythmbox via https://bugzilla.gnome.org/show_bug.cgi?id=727582 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to rhythmbox in Ubuntu. https://bugs.launchpad.net/bugs/1301257 Title: rhythmbox crashed when syncing with iPad (iOS7.1) Status in The Rhythmbox Music Management Application: Unknown Status in “rhythmbox” package in Ubuntu: New Bug description: [ 35.642883] rhythmbox[2290]: segfault at 1f0036 ip 7ff1d6c07c3d sp 7fffe662ee10 error 4 in libgobject-2.0.so.0.4000.0[7ff1d6bd5000+4f000] ProblemType: Crash DistroRelease: Ubuntu 14.04 Package: rhythmbox 3.0.1-1ubuntu16 ProcVersionSignature: Ubuntu 3.13.0-20.42-generic 3.13.7 Uname: Linux 3.13.0-20-generic x86_64 ApportVersion: 2.14-0ubuntu1 Architecture: amd64 CrashCounter: 1 CurrentDesktop: Unity Date: Wed Apr 2 10:31:47 2014 ExecutablePath: /usr/bin/rhythmbox InstallationDate: Installed on 2014-03-20 (12 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140318) ProcCmdline: /usr/bin/rhythmbox ProcEnviron: XDG_RUNTIME_DIR=set SHELL=/bin/bash LANGUAGE=de_DE PATH=(custom, no user) LANG=de_DE.UTF-8 SegvAnalysis: Segfault happened at: 0x7ff1d6c07c3d g_type_check_value_holds+61: testb $0x8,0x16(%rbx) PC (0x7ff1d6c07c3d) ok source $0x8 ok destination 0x16(%rbx) (0x1f0036) not located in a known VMA region (needed writable region)! SegvReason: writing unknown VMA Signal: 11 SourcePackage: rhythmbox StacktraceTop: g_type_check_value_holds () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgpod.so.4 itdb_parse () from /usr/lib/x86_64-linux-gnu/libgpod.so.4 rb_ipod_db_new () from /usr/lib/rhythmbox/plugins/ipod/libipod.so ?? () from /usr/lib/rhythmbox/plugins/ipod/libipod.so Title: rhythmbox crashed with SIGSEGV in g_type_check_value_holds() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers To manage notifications about this bug go to: https://bugs.launchpad.net/rhythmbox/+bug/1301257/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1284635] Re: Keyboard layout changes after login
I reported a similar problem in bug 1302353 but it only started two days ago after upgrading a bunch of unity packages. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1284635 Title: Keyboard layout changes after login Status in “ibus” package in Ubuntu: Triaged Status in “ibus” source package in Trusty: Triaged Bug description: installed trusty beta1 with keyboard layout set correctly during install install completes, login to new install - layout as set during install once logged in - layout set to US and keyboard layout set during install is missing from list ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: keyboard-configuration 1.70ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-12.32-generic 3.13.4 Uname: Linux 3.13.0-12-generic i686 ApportVersion: 2.13.2-0ubuntu5 Architecture: i386 CurrentDesktop: XFCE Date: Tue Feb 25 12:55:56 2014 InstallationDate: Installed on 2014-02-25 (0 days ago) InstallationMedia: Xubuntu 14.04 LTS Trusty Tahr - Alpha i386 (20140225) PackageArchitecture: all SourcePackage: console-setup UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1284635/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1302353] Re: regression: ibus ignores keyboard layout
** Description changed: The recent update of unity packages introduced a bad regression for ibus users. I assume the fault lies with unity since ibus hasn't been updated for several weeks and my machine was fine until about two days ago around which time some unity updates rolled in. I have a German keyboard layout (QWERTZ not QWERTY as in the US case). I use anthy and mozc for Japanese input. Since two days ago the default layout with the Japanese IME are a US layout throwing me off when blind- typing. To look into the matter, I opened ibus-setup and there are three Input methods listed there: English - English (US), Japanese - Anthy and Japanese -Mozc. German was conspicuously absent . I - eventually managed to add a German layout to it and delete the US layout - but the next time I call ibus-setup the US layout is back as default. - In other words, the explicit choice I'm trying to force doesn't stick. + eventually managed to add a German layout to it and delete the US + layout. I then restart ibus with ibus restart only to find the US + keyboard layout not only back but it's default again. Argh! In other + words, the explicit choice I'm trying to force doesn't stick. There are four keyboard layouts currently defined in System Settings - Text Entry - Input sources to use, none of them have anything to do with a US-layout; de1, de2, anthy and mozc. I cycle through them via Super+Space. Anthy is set to use the system default layout. The regression is that it currently inists on US layout with no way to even override this silly choice. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1302353 Title: regression: ibus ignores keyboard layout Status in “ibus” package in Ubuntu: New Status in “unity” package in Ubuntu: New Bug description: The recent update of unity packages introduced a bad regression for ibus users. I assume the fault lies with unity since ibus hasn't been updated for several weeks and my machine was fine until about two days ago around which time some unity updates rolled in. I have a German keyboard layout (QWERTZ not QWERTY as in the US case). I use anthy and mozc for Japanese input. Since two days ago the default layout with the Japanese IME are a US layout throwing me off when blind-typing. To look into the matter, I opened ibus-setup and there are three Input methods listed there: English - English (US), Japanese - Anthy and Japanese -Mozc. German was conspicuously absent . I eventually managed to add a German layout to it and delete the US layout. I then restart ibus with ibus restart only to find the US keyboard layout not only back but it's default again. Argh! In other words, the explicit choice I'm trying to force doesn't stick. There are four keyboard layouts currently defined in System Settings - Text Entry - Input sources to use, none of them have anything to do with a US-layout; de1, de2, anthy and mozc. I cycle through them via Super+Space. Anthy is set to use the system default layout. The regression is that it currently inists on US layout with no way to even override this silly choice. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1302353/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1247545] Re: Extra keyboard layouts are added to IBus
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: ibus (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1247545 Title: Extra keyboard layouts are added to IBus Status in “ibus” package in Ubuntu: Confirmed Bug description: From time to time, extra keyboard layouts are added to the list of selectable layouts and input methods, without being added by the user. One way I triggered this just a moment ago was: 1) Use a European system keyboard layout with some non-ASCII (8-bit) characters. 2) Activate the Use system keyboard layout option. 3) Activate Intelligent Pinyin, Anthy etc. and verify that the non-ASCII characters can be entered. 4) Restart IBus and try again if the above didn't work. 5) Deactivate the Use system keyboard layout option and repeat steps 2-4 to verify that the non-ASCII characters cannot be entered this time. 6) Activate the Use system keyboard layout option and repeat steps 2-4 to verify that they can be entered again. At some point during the process, a Japanese keyboard layout was added to the list of selectable layouts! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1247545/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1247545] Re: Extra keyboard layouts are added to IBus
I reported something similar in bug 1302353. Only that in my case a US layout was added, made default and I can't remove it :-( -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1247545 Title: Extra keyboard layouts are added to IBus Status in “ibus” package in Ubuntu: Confirmed Bug description: From time to time, extra keyboard layouts are added to the list of selectable layouts and input methods, without being added by the user. One way I triggered this just a moment ago was: 1) Use a European system keyboard layout with some non-ASCII (8-bit) characters. 2) Activate the Use system keyboard layout option. 3) Activate Intelligent Pinyin, Anthy etc. and verify that the non-ASCII characters can be entered. 4) Restart IBus and try again if the above didn't work. 5) Deactivate the Use system keyboard layout option and repeat steps 2-4 to verify that the non-ASCII characters cannot be entered this time. 6) Activate the Use system keyboard layout option and repeat steps 2-4 to verify that they can be entered again. At some point during the process, a Japanese keyboard layout was added to the list of selectable layouts! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1247545/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1301401] Re: Windows Live account doesn't login on Ubuntu 14.04 beta
Are you still seeing this issue in 14.04? ** Changed in: empathy (Ubuntu) Status: New = Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to empathy in Ubuntu. https://bugs.launchpad.net/bugs/1301401 Title: Windows Live account doesn't login on Ubuntu 14.04 beta Status in “empathy” package in Ubuntu: Incomplete Bug description: eduar@envy4:~$ lsb_release -rd Description: Ubuntu Trusty Tahr (development branch) Release: 14.04 eduar@envy4:~$ apt-cache policy empathy empathy: Instalados: 3.8.6-0ubuntu7 Candidato: 3.8.6-0ubuntu7 Tabla de versión: *** 3.8.6-0ubuntu7 0 500 http://co.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages 100 /var/lib/dpkg/status eduar@envy4:~$ apt-cache policy telepathy-gabble telepathy-gabble: Instalados: 0.18.2-1 Candidato: 0.18.2-1 Tabla de versión: *** 0.18.2-1 0 500 http://co.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages 100 /var/lib/dpkg/status Hello all. I'm trying to setup my Windows Live account (@outlook.com) in Empathy. It used to work OK on Ubuntu 12.04.4 64 bits. However, in 14.04 it doesn't works. When I add an account, it asks me for my username and password, I give it permissions to access my data, and the account is shown OK on the Online accounts window. However, when I go Online, Empathy shows a wheel in the middle, just turning around, but nothing else happens. After a while, it gives me a red error message x...@outlook.com Network error I have the debug in pastebin: http://pastebin.com/8vQdM4Pg Thanks! ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: empathy 3.8.6-0ubuntu7 ProcVersionSignature: Ubuntu 3.13.0-21.43-generic 3.13.8 Uname: Linux 3.13.0-21-generic x86_64 ApportVersion: 2.14-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Wed Apr 2 08:41:58 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2014-03-30 (2 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Beta amd64 (20140326) ProcEnviron: LANGUAGE=es_CO:es PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=es_CO.UTF-8 SHELL=/bin/bash SourcePackage: empathy UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/1301401/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1293252] Re: gnome-panel crashed with signal 5 in _XReply()
** Information type changed from Private to Public -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-panel in Ubuntu. https://bugs.launchpad.net/bugs/1293252 Title: gnome-panel crashed with signal 5 in _XReply() Status in “gnome-panel” package in Ubuntu: New Bug description: ? ProblemType: Crash DistroRelease: Ubuntu 14.04 Package: gnome-panel 1:3.8.0-1ubuntu9 ProcVersionSignature: Ubuntu 3.13.0-17.37-generic 3.13.6 Uname: Linux 3.13.0-17-generic x86_64 ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Sun Mar 16 23:53:20 2014 ExecutablePath: /usr/bin/gnome-panel GsettingsChanges: InstallationDate: Installed on 2014-02-28 (16 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140224) ProcCmdline: gnome-panel ProcEnviron: LANGUAGE=de_DE PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=de_DE.UTF-8 SHELL=/bin/bash Signal: 5 SourcePackage: gnome-panel StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6 ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6 _XReply () from /usr/lib/x86_64-linux-gnu/libX11.so.6 XSync () from /usr/lib/x86_64-linux-gnu/libX11.so.6 ?? () from /usr/lib/x86_64-linux-gnu/libcairo.so.2 Title: gnome-panel crashed with signal 5 in _XReply() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-panel/+bug/1293252/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1300393] Re: Connected external monitor causes very high cpu usage by compiz
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: compiz (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to compiz in Ubuntu. https://bugs.launchpad.net/bugs/1300393 Title: Connected external monitor causes very high cpu usage by compiz Status in “compiz” package in Ubuntu: Confirmed Bug description: Steps to reproduce: connect a external monitor an login to unity - the cpu usage of compiz increases insanely high by just moving some window around. In this state unity is not really usable. There is no difference if the external monitor is used for output or not. It just have to be connected when login. And there are no problems when the monitor is unconnected when login and connected after. $ lsb_release -rd Description: Ubuntu Trusty Tahr (development branch) Release: 14.04 $ apt-cache policy compiz compiz: Installed: 1:0.9.11+14.04.20140328-0ubuntu1 Candidate: 1:0.9.11+14.04.20140328-0ubuntu1 Version table: *** 1:0.9.11+14.04.20140328-0ubuntu1 0 500 http://de.archive.ubuntu.com/ubuntu/ trusty/main i386 Packages 100 /var/lib/dpkg/status $ /usr/lib/nux/unity_support_test -p OpenGL vendor string: Intel Open Source Technology Center OpenGL renderer string: Mesa DRI Intel(R) 945GM x86/MMX/SSE2 OpenGL version string: 1.4 Mesa 10.1.0 Not software rendered:yes Not blacklisted: yes GLX fbconfig: yes GLX texture from pixmap: yes GL npot or rect textures: yes GL vertex program:yes GL fragment program: yes GL vertex buffer object: yes GL framebuffer object:yes GL version is 1.4+: yes Unity 3D supported: yes ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: compiz 1:0.9.11+14.04.20140328-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-18.38-generic 3.13.6 Uname: Linux 3.13.0-18-generic i686 .tmp.unity.support.test.0: ApportVersion: 2.13.3-0ubuntu1 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 CurrentDesktop: Unity Date: Mon Mar 31 21:07:35 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: virtualbox, 4.3.6, 3.13.0-18-generic, i686: installed virtualbox, 4.3.6, 3.13.0-19-generic, i686: installed virtualbox, 4.3.6, 3.13.0-20-generic, i686: installed GraphicsCard: Intel Corporation Mobile 945GM/GMS, 943/940GML Express Integrated Graphics Controller [8086:27a2] (rev 03) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:01bd] Subsystem: Dell Device [1028:01bd] InstallationDate: Installed on 2013-10-24 (157 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release i386 (20131016.1) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: Dell Inc. MM061 PackageArchitecture: all ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-18-generic root=UUID=7796fb02-f0a7-4355-988f-94862a77bffa ro quiet splash SourcePackage: compiz UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/13/2007 dmi.bios.vendor: Dell Inc. dmi.bios.version: A17 dmi.board.name: 0KD882 dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA17:bd06/13/2007:svnDellInc.:pnMM061:pvr:rvnDellInc.:rn0KD882:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: MM061 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.11+14.04.20140328-0ubuntu1 version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-1ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.15.0-1ubuntu7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Mon Mar 31 21:00:53 2014 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 43264 vendor LPL xserver.version: 2:1.15.0-1ubuntu7 To manage notifications about this
[Desktop-packages] [Bug 1302359] [NEW] Regarding screen freezing a dimming
Public bug reported: This screen dimming problem has been around Gnome Ubuntu-based distros forever, at least since around 8.x. You can search and see how far back it goes. Today, I am using ArtistX 13.04 and looked for a solution again. It still exists, I see. The dimming/freezing has no set pattern when the problem will strike, although using a browser frequently exhibits the symptoms. It drove me nuts enough that I gave up on Ubuntu years ago. Apparently, I was able to sent in an xorg report, so I hope that worked for you. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: xorg 1:7.7+1ubuntu4 ProcVersionSignature: Ubuntu 3.8.0-30.44-generic 3.8.13.6 Uname: Linux 3.8.0-30-generic i686 .tmp.unity.support.test.0: ApportVersion: 2.9.2-0ubuntu8.5 Architecture: i386 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 Date: Fri Apr 4 02:20:47 2014 DistUpgraded: Fresh install DistroCodename: raring DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices [AMD] nee ATI Redwood LE [Radeon HD 5550] [1002:68da] (prog-if 00 [VGA controller]) Subsystem: Hightech Information System Ltd. Device [1787:2297] InstallationDate: Installed on 2014-04-03 (0 days ago) InstallationMedia: ArtistX 13.04 - Release i386 MachineType: Gigabyte Technology Co., Ltd. H61M-DS2 REV 1.2 MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-30-generic root=UUID=b9234e94-693f-4652-a14a-f52301e98389 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/12/2011 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: FB dmi.board.name: H61M-DS2 REV 1.2 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrFB:bd10/12/2011:svnGigabyteTechnologyCo.,Ltd.:pnH61M-DS2REV1.2:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnH61M-DS2REV1.2:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: H61M-DS2 REV 1.2 dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz 1:0.9.9~daily13.06.19~13.04-0ubuntu1 version.libdrm2: libdrm2 2.4.46-1ubuntu0.1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.1.7-1ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.1.7-1ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.13.3-0ubuntu6.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2b2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.1.0-0ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.21.6-0ubuntu4.3 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.7-0ubuntu1 xserver.bootTime: Thu Apr 3 18:22:53 2014 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputUSB USB Keykoard KEYBOARD, id 8 inputUSB USB Keykoard KEYBOARD, id 9 inputSONiX eclipse mobile_mouse MOUSE, id 10 xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.13.3-0ubuntu6 xserver.video_driver: radeon ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug compiz-0.9 i386 raring ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1302359 Title: Regarding screen freezing a dimming Status in “xorg” package in Ubuntu: New Bug description: This screen dimming problem has been around Gnome Ubuntu-based distros forever, at least since around 8.x. You can search and see how far back it goes. Today, I am using ArtistX 13.04 and looked for a solution again. It still exists, I see. The dimming/freezing has no set pattern when the problem will strike, although using a browser frequently exhibits the symptoms. It drove me nuts enough that I gave up on Ubuntu years ago. Apparently, I was able to sent in an xorg report, so I hope that worked for you. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: xorg 1:7.7+1ubuntu4 ProcVersionSignature: Ubuntu 3.8.0-30.44-generic 3.8.13.6 Uname: Linux 3.8.0-30-generic i686 .tmp.unity.support.test.0: ApportVersion: 2.9.2-0ubuntu8.5 Architecture: i386 CompizPlugins:
[Desktop-packages] [Bug 1301720] Re: [Text Entry] There is no English input in Traditional Chinese default enviroment
@gunnarhj hey, Because in default Traditional Chinese environment, there is no English input. Either way users need to add it by themselves or to know the hidden shortcut in each input methods. And I think this should be a bug, as English input does not existed at fresh install or live desktop. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1301720 Title: [Text Entry] There is no English input in Traditional Chinese default enviroment Status in “unity-control-center” package in Ubuntu: Incomplete Bug description: Default settings should provie english input method even when using Traditional Chinese, since most of commands still requires to input ascii charaters. Found this issue on 14.04 beta2 with locale: LANG=zh_TW.UTF-8 LANGUAGE= LC_CTYPE=zh_TW.UTF-8 LC_NUMERIC=zh_TW.UTF-8 LC_TIME=zh_TW.UTF-8 LC_COLLATE=zh_TW.UTF-8 LC_MONETARY=zh_TW.UTF-8 LC_MESSAGES=zh_TW.UTF-8 LC_PAPER=zh_TW.UTF-8 LC_NAME=zh_TW.UTF-8 LC_ADDRESS=zh_TW.UTF-8 LC_TELEPHONE=zh_TW.UTF-8 LC_MEASUREMENT=zh_TW.UTF-8 LC_IDENTIFICATION=zh_TW.UTF-8 LC_ALL= ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity-control-center 14.04.3+14.04.20140324-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-19.40-generic 3.13.6 Uname: Linux 3.13.0-19-generic x86_64 ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 CasperVersion: 1.339 CurrentDesktop: Unity Date: Thu Apr 3 03:50:26 2014 ExecutablePath: /usr/bin/unity-control-center LiveMediaBuild: Ubuntu 14.04 LTS Trusty Tahr - Beta amd64 (20140326) ProcEnviron: TERM=xterm SHELL=/bin/bash PATH=(custom, no user) LANG=zh_TW.UTF-8 XDG_RUNTIME_DIR=set SourcePackage: unity-control-center UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_unity-control-center: activity-log-manager 0.9.7-0ubuntu12 deja-dup 29.5-0ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-control-center/+bug/1301720/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1293252] Re: gnome-panel crashed with signal 5 in _XReply()
Thanks for your report. Do you know a way to reproduce this issue? Did you get it several times? The stacktrace is good, but it looks like the error is not in gnome- panel itself, but probably in cairo. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-panel in Ubuntu. https://bugs.launchpad.net/bugs/1293252 Title: gnome-panel crashed with signal 5 in _XReply() Status in “gnome-panel” package in Ubuntu: New Bug description: ? ProblemType: Crash DistroRelease: Ubuntu 14.04 Package: gnome-panel 1:3.8.0-1ubuntu9 ProcVersionSignature: Ubuntu 3.13.0-17.37-generic 3.13.6 Uname: Linux 3.13.0-17-generic x86_64 ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Sun Mar 16 23:53:20 2014 ExecutablePath: /usr/bin/gnome-panel GsettingsChanges: InstallationDate: Installed on 2014-02-28 (16 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140224) ProcCmdline: gnome-panel ProcEnviron: LANGUAGE=de_DE PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=de_DE.UTF-8 SHELL=/bin/bash Signal: 5 SourcePackage: gnome-panel StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6 ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6 _XReply () from /usr/lib/x86_64-linux-gnu/libX11.so.6 XSync () from /usr/lib/x86_64-linux-gnu/libX11.so.6 ?? () from /usr/lib/x86_64-linux-gnu/libcairo.so.2 Title: gnome-panel crashed with signal 5 in _XReply() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-panel/+bug/1293252/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1300792] Re: libreoffice toolbar icons large and ugly - no matter what theme
Thanks for reporting this bug and making Ubuntu better. It looks a problem with your desktop environment. Do you notice this only in LibreOffice or also in other applications? ** Changed in: libreoffice (Ubuntu) Status: New = Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1300792 Title: libreoffice toolbar icons large and ugly - no matter what theme Status in “libreoffice” package in Ubuntu: Incomplete Bug description: Since the last update to libreoffice, the toolbar icons are too large to fit right in the toolbar and seems to be using the wrong size of icons which causes them to be blocky. I've tried changing the settings in libreoffice between different libreoffice themes and size and the icon appearance does not change. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: libreoffice-common 1:4.2.3~rc2-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-20.42-generic 3.13.7 Uname: Linux 3.13.0-20-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14-0ubuntu1 Architecture: amd64 CurrentDesktop: KDE Date: Tue Apr 1 09:28:42 2014 InstallationDate: Installed on 2014-03-21 (10 days ago) InstallationMedia: It PackageArchitecture: all SourcePackage: libreoffice UpgradeStatus: Upgraded to trusty on 2014-03-24 (7 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1300792/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1192028] Re: Compiz refresh rate resets to 50 Hz automatically
Does this bug render the system unusable? ** Changed in: hundredpapercuts Status: Triaged = Incomplete ** Changed in: compiz (Ubuntu) Status: Triaged = Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to compiz in Ubuntu. https://bugs.launchpad.net/bugs/1192028 Title: Compiz refresh rate resets to 50 Hz automatically Status in Compiz: Confirmed Status in One Hundred Papercuts: Incomplete Status in “compiz” package in Ubuntu: Incomplete Bug description: There have been similar bug reports to this one, such as bug #1009338 and bug #1027868, but I believe this case is different. The problem I am having is that even after I set the refresh rate options in compiz to 60 Hz (after disabling the Detect Refresh Rate option), a reboot will have the settings revert. If I change settings in the compiz config settings manager, they should remain even after a reboot. --- .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: u'/proc/driver/nvidia/gpus/0' .proc.driver.nvidia.registry: Binary: .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 313.30 Wed Mar 27 16:56:45 PDT 2013 GCC version: gcc version 4.7.3 (Ubuntu/Linaro 4.7.3-1ubuntu1) .tmp.unity.support.test.0: ApportVersion: 2.9.2-0ubuntu8.1 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 DistUpgraded: 2013-04-28 10:18:35,447 DEBUG enabling apt cron job DistroCodename: raring DistroRelease: Ubuntu 13.04 DistroVariant: ubuntu GraphicsCard: NVIDIA Corporation G84M [GeForce 8600M GT] [10de:0407] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:022e] InstallationDate: Installed on 2011-10-16 (611 days ago) InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012) MachineType: Dell Inc. XPS M1530 MarkForUpload: True NonfreeKernelModules: nvidia Package: compiz 1:0.9.9~daily13.04.18.1~13.04-0ubuntu1 PackageArchitecture: all ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-23-generic root=UUID=67324911-aae9-47ca-a177-6c818959ed59 ro quiet splash ProcVersionSignature: Ubuntu 3.8.0-23.34-generic 3.8.11 Tags: raring raring ubuntu compiz-0.9 Uname: Linux 3.8.0-23-generic x86_64 UpgradeStatus: Upgraded to raring on 2013-04-28 (50 days ago) UserGroups: adm admin audio cdrom dialout dip fuse lpadmin netdev plugdev sambashare vboxusers video dmi.bios.date: 11/19/2008 dmi.bios.vendor: Dell Inc. dmi.bios.version: A12 dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA12:bd11/19/2008:svnDellInc.:pnXPSM1530:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: XPS M1530 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.9~daily13.04.18.1~13.04-0ubuntu1 version.ia32-libs: ia32-libs 20090808ubuntu36 version.libdrm2: libdrm2 2.4.43-0ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.1.1-0ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.1.1-0ubuntu3 version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A version.xserver-xorg-core: xserver-xorg-core 2:1.13.3-0ubuntu6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2b2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.1.0-0ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.21.6-0ubuntu4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.7-0ubuntu1 xserver.bootTime: Mon Jun 17 17:22:09 2013 xserver.configfile: /etc/X11/xorg.conf xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.13.3-0ubuntu6 To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/1192028/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1302214] Re: no obvious way to click the shutdown dialog from lightdm
Hi Robert, yes - I'm the only account (administrator) - The shutdown and restart options are visible in indicator-session when I log-in. I'm also seeing this bug report with those shutdown and restart options in indicator-session - https://bugs.launchpad.net/bugs/1302221 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-greeter in Ubuntu. https://bugs.launchpad.net/bugs/1302214 Title: no obvious way to click the shutdown dialog from lightdm Status in “unity-greeter” package in Ubuntu: New Bug description: Please see the attached picture. Choosing the indicator shutdown option from lightdm displays the shutdown dialog. However, there is no obvious feedback as to how to actually shutdown from the dialog. There is no click feedback - pressing Y doesnt shutdown - so how do you actually shutdown from the login screen? ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: lightdm 1.9.14-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-22.44-generic 3.13.8 Uname: Linux 3.13.0-22-generic x86_64 ApportVersion: 2.14-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Thu Apr 3 22:48:47 2014 InstallationDate: Installed on 2014-02-22 (40 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140220.1) ProcEnviron: LANGUAGE=en_GB:en TERM=xterm PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-greeter/+bug/1302214/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1226962] Re: Hotkeys not functional in non-latin keyboard layout in 13.10 and 14.04
** Changed in: unity (Ubuntu) Status: Fix Released = Triaged ** Changed in: unity-settings-daemon (Ubuntu) Status: Fix Released = Triaged ** Changed in: indicator-keyboard (Ubuntu) Status: Fix Released = Triaged -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. Matching subscriptions: dp-unity https://bugs.launchpad.net/bugs/1226962 Title: Hotkeys not functional in non-latin keyboard layout in 13.10 and 14.04 Status in LibreOffice Productivity Suite: Confirmed Status in IBus: New Status in Indicator keyboard: Fix Released Status in Inkscape: A Vector Drawing Tool: New Status in Mutter: Fix Released Status in The OpenOffice.org Suite: New Status in Unity: Fix Released Status in “gnome-settings-daemon” package in Ubuntu: Triaged Status in “gnome-terminal” package in Ubuntu: Triaged Status in “indicator-keyboard” package in Ubuntu: Triaged Status in “unity” package in Ubuntu: Triaged Status in “unity-settings-daemon” package in Ubuntu: Triaged Status in “gnome-settings-daemon” package in Fedora: Unknown Bug description: New keyboard layout changer in Ubuntu 13.10 introduce old-new bug. Any system or application hotkey witch use char (for example: ctrl+alt+t for terminal or ctrl+t for new tab in browser) become unfunctional when selected non-latin keyboard layout. Hotkeys with F1-12, numbers and other non-character buttons works perfectly. Window manager hotkeys not affected by this bug. All hotkeys in system parameters-keyboard-hotkeys-windows works perfect with any keyboard layout. Workaround for some system hotkeys and two layouts (english and non- latin): rebind all hotkeys in your local layout. For example instead of ctrl+alt+t use ctrl+alt+τ (greek tau). That hotkey still work with english layout. If you use english and two different non-latin layouts this workaround helps only with one of them. -- For other layout switching problems introduced in Ubuntu 13.10 you can see bug 1218322. -- To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1226962/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1302365] Re: totem crashed with SIGABRT
*** This bug is a duplicate of bug 034 *** https://bugs.launchpad.net/bugs/034 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #034, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: CoreDump.gz https://bugs.launchpad.net/bugs/1302365/+attachment/4064779/+files/CoreDump.gz ** Attachment removed: Disassembly.txt https://bugs.launchpad.net/bugs/1302365/+attachment/4064781/+files/Disassembly.txt ** Attachment removed: ProcMaps.txt https://bugs.launchpad.net/bugs/1302365/+attachment/4064783/+files/ProcMaps.txt ** Attachment removed: ProcStatus.txt https://bugs.launchpad.net/bugs/1302365/+attachment/4064784/+files/ProcStatus.txt ** Attachment removed: Registers.txt https://bugs.launchpad.net/bugs/1302365/+attachment/4064785/+files/Registers.txt ** Attachment removed: Stacktrace.txt https://bugs.launchpad.net/bugs/1302365/+attachment/4064786/+files/Stacktrace.txt ** Attachment removed: ThreadStacktrace.txt https://bugs.launchpad.net/bugs/1302365/+attachment/4064787/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 034 ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/1302365 Title: totem crashed with SIGABRT Status in “totem” package in Ubuntu: New Bug description: No idea what happened. ProblemType: Crash DistroRelease: Ubuntu 14.04 Package: totem 3.10.1-1ubuntu4 ProcVersionSignature: Ubuntu 3.13.0-21.43-generic 3.13.8 Uname: Linux 3.13.0-21-generic x86_64 ApportVersion: 2.14-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Fri Apr 4 08:48:59 2014 ExecutablePath: /usr/bin/totem InstallationDate: Installed on 2013-12-22 (102 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20131221) LogAlsaMixer: Error: command ['/usr/bin/amixer'] failed with exit code 1: amixer: Mixer attach default error: No such file or directory ProcCmdline: totem /home/username/Ubuntu\ One/xwax/dnb/Pharrell\ Williams\ -\ Happy\ (Makoto\ 170\ Edit)\ (170.0\ VPM).mp3 ProcEnviron: SHELL=/bin/bash LANGUAGE=de_DE PATH=(custom, user) LANG=de_DE.UTF-8 Signal: 6 SourcePackage: totem StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/gio/modules/libdconfsettings.so ?? () from /usr/lib/x86_64-linux-gnu/gio/modules/libdconfsettings.so ?? () from /usr/lib/x86_64-linux-gnu/gio/modules/libdconfsettings.so ?? () from /usr/lib/x86_64-linux-gnu/gio/modules/libdconfsettings.so ?? () from /usr/lib/x86_64-linux-gnu/gio/modules/libdconfsettings.so Title: totem crashed with SIGABRT UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm autopilot cdrom dip lpadmin plugdev sambashare scanner sudo XsessionErrors: (process:2241): dconf-CRITICAL **: unable to create file '/home/daniel/.cache/dconf/user': Keine Berechtigung. dconf will not work properly. (process:2241): dconf-CRITICAL **: unable to create file '/home/daniel/.cache/dconf/user': Keine Berechtigung. dconf will not work properly. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1302365/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1302348] Re: after today's Trusty updates/restart, NM will not connect to wifi
dito, same here. worked fine with beta2, was broken after yesterdays update. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1302348 Title: after today's Trusty updates/restart, NM will not connect to wifi Status in “network-manager” package in Ubuntu: New Bug description: I see all the wireless signals in the neighborhood, but the connect button does not connect my laptop to the internet. Also, history seems lost, as it reports that my wifi has never been used, when it was in use a few minutes before. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: network-manager 0.9.8.8-0ubuntu5 ProcVersionSignature: Ubuntu 3.13.0-22.44-generic 3.13.8 Uname: Linux 3.13.0-22-generic x86_64 ApportVersion: 2.14-0ubuntu1 Architecture: amd64 CurrentDesktop: KDE Date: Thu Apr 3 22:43:11 2014 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2013-06-18 (289 days ago) InstallationMedia: Kubuntu 13.04 Raring Ringtail - Release amd64 (20130424) IpRoute: default via 192.168.15.1 dev eth0 proto static 192.168.15.0/24 dev eth0 proto kernel scope link src 192.168.15.3 metric 1 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: network-manager UpgradeStatus: Upgraded to trusty on 2014-03-04 (30 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1302348/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1201180] Re: powerbtn.sh conflicts with logind
rubik-cube: there are some issues with your patch: 1) Do not hardcode x86_64-linux-gnu triplet, which only works on amd64. Instead, you can use `dpkg-architecture -qDEB_HOST_MULTIARCH` for example. 2) `test -L /usr/bin/qdbus` will be *always* true, as the binary is managed by qtchooser. 3) Finally, please generate a proper debdiff with a changelog entry. Also, please note that instead of specifying full paths to qdbus binary, you can just run `qdbus -qt4` or `qdbus -qt5` without caring about the paths (though not sure if it's helpful here). Unsubscribing sponsors unless these issues are resolved. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1201180 Title: powerbtn.sh conflicts with logind Status in “acpid” package in Ubuntu: Fix Released Status in “gnome-session” package in Ubuntu: Fix Released Status in “kde-workspace” package in Ubuntu: Triaged Status in “systemd” package in Ubuntu: Fix Released Status in “systemd-shim” package in Ubuntu: Invalid Bug description: In saucy the PC powers down as soon as I press the power button, it seems that systemd is calling poweroff, but I'm not sure if it's doing that in response of some other event (i.e. as callback of a dbus call): root 4998 0.0 0.0 177932 2104 ?Sl 20:41 0:00 /usr/lib/x86_64-linux-gnu/systemd-shim root 5012 0.0 0.0 4440 624 ?S20:41 0:00 \_ sh -c /sbin/poweroff root 5013 0.0 0.0 4440 628 ?S20:41 0:00 \_ /bin/sh /sbin/shutdown -h -P now In any case the caller or systemd itself should be aware that there's a session-manager running and that it shouldn't actually directly power off the system then. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/acpid/+bug/1201180/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1302371] [NEW] apport-kde crashes while trying to create crash report
Public bug reported: I am unable to send apport crash because apport itself crashes. I'm attaching crash report generated by DrKonqi. ** Affects: apport (Ubuntu) Importance: Undecided Status: New ** Tags: crash trusty ** Attachment added: Crash report generated by DrKonqi https://bugs.launchpad.net/bugs/1302371/+attachment/4064807/+files/python3-20140404-131833.kcrash.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1302371 Title: apport-kde crashes while trying to create crash report Status in “apport” package in Ubuntu: New Bug description: I am unable to send apport crash because apport itself crashes. I'm attaching crash report generated by DrKonqi. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1302371/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1302105] Re: Highlight glitch while scrolling the services list
Thanks Edwin for reporting this bug. I just checked, and I can reproduce it as well. ** Also affects: gnome-control-center-signon Importance: Undecided Status: New ** Changed in: gnome-control-center-signon (Ubuntu) Status: New = Confirmed ** Changed in: gnome-control-center-signon Status: New = Confirmed ** Changed in: gnome-control-center-signon Importance: Undecided = Medium ** Changed in: gnome-control-center-signon Assignee: (unassigned) = Alberto Mardegan (mardy) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center-signon in Ubuntu. https://bugs.launchpad.net/bugs/1302105 Title: Highlight glitch while scrolling the services list Status in Online Accounts: GNOME Control Center: Confirmed Status in “gnome-control-center-signon” package in Ubuntu: Confirmed Bug description: On the Online Accounts panel, if I scroll the list of services (on the right side) the highlight is repeated. That is, say I have the mouse over Twitter, when I scroll the list with the mouse wheel the highlighting is drawn over Twitter and newly hovered items. I've added a screenshot. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity-control-center-signon 0.1.7~+14.04.20140211.2-0ubuntu4 ProcVersionSignature: Ubuntu 3.13.0-20.42-generic 3.13.7 Uname: Linux 3.13.0-20-generic x86_64 ApportVersion: 2.14-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Thu Apr 3 14:19:56 2014 InstallationDate: Installed on 2014-03-16 (18 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140316) SourcePackage: gnome-control-center-signon UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center-signon/+bug/1302105/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1261666] Re: [pulseaudio] module.c: Failed to load module module-echo-cancel (argument: aec_method=webrtc): initia lization failed.
I would also like to have webrtc for echo cancellation in pulseaudio. Currently pulseaudio with webrtc is the best choice as echo canceller for mumble. (The mumble built in echo canceller is really bad compared to having pulse echo cancellation before). But one system with speex and another with webrtc show significant differences, webrtc is much better. This is unfortunately missing under ubuntu. Could it be added? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1261666 Title: [pulseaudio] module.c: Failed to load module module-echo-cancel (argument: aec_method=webrtc): initia lization failed. Status in “pulseaudio” package in Ubuntu: Triaged Bug description: Hello! 13.10. Trying to load module-echo-cancel with webrtc and get: [pulseaudio] module.c: Failed to load module module-echo-cancel (argument: aec_method=webrtc): initia lization failed. I guess this is wrong... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1261666/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1298740] Re: unity-settings-daemon warns when IBus engine layout is default
I add supplement report of Ikuya's report, - This fix included serious regression, that breaks japanese keyboard layout. How to reproduce this regression: 1) install Ubuntu 2) select Japanese 3) open termianl 4) exec gedit 5) type from your keyboard: shift +2 with ibus activated. actual: show '@' expected: '' - Background: In common Japanese environments, that use JP keyboard layout(106/109 keyboards, http://upload.wikimedia.org/wikipedia/commons/thumb/8/81/109keyboard.svg /841px-109keyboard.svg.png) Therefor, this fix cause us explicit settings, that breaks Japanese keyboard layout in ibus-anty/mozc. It seems that JP keyboard treats as us layout. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1298740 Title: unity-settings-daemon warns when IBus engine layout is default Status in Unity Settings Daemon: In Progress Status in “unity-settings-daemon” package in Ubuntu: Fix Released Bug description: To reproduce: Add Russian keyboard layout and Chinese (Pinyin or Intelligent Pinyin) input method. Switch to Russian layout. Switch to Chinese IM. Try to input pinyin, result is still Cyrillic characters. unity-settings-daemon emits the following warning: (unity-settings-daemon:14828): keyboard-plugin-WARNING **: Couldn't upload new XKB keyboard description Some IBus engines were updated to have a layout of default rather than us, and xkb doesn't accept it as a possible layout from /usr/share/X11/xkb/rules/evdev. To manage notifications about this bug go to: https://bugs.launchpad.net/unity-settings-daemon/+bug/1298740/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1192028] Re: Compiz refresh rate resets to 50 Hz automatically
The system is still usable. I think that users that do not watch (HD) videos or play animated games will not notice this bug at all. On the other hand, users that do all this things and are used to e.g. smooth video playback (from e.g. 12.04) will be very disappointed about this (quality regression) bug. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to compiz in Ubuntu. https://bugs.launchpad.net/bugs/1192028 Title: Compiz refresh rate resets to 50 Hz automatically Status in Compiz: Confirmed Status in One Hundred Papercuts: Incomplete Status in “compiz” package in Ubuntu: Incomplete Bug description: There have been similar bug reports to this one, such as bug #1009338 and bug #1027868, but I believe this case is different. The problem I am having is that even after I set the refresh rate options in compiz to 60 Hz (after disabling the Detect Refresh Rate option), a reboot will have the settings revert. If I change settings in the compiz config settings manager, they should remain even after a reboot. --- .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: u'/proc/driver/nvidia/gpus/0' .proc.driver.nvidia.registry: Binary: .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 313.30 Wed Mar 27 16:56:45 PDT 2013 GCC version: gcc version 4.7.3 (Ubuntu/Linaro 4.7.3-1ubuntu1) .tmp.unity.support.test.0: ApportVersion: 2.9.2-0ubuntu8.1 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 DistUpgraded: 2013-04-28 10:18:35,447 DEBUG enabling apt cron job DistroCodename: raring DistroRelease: Ubuntu 13.04 DistroVariant: ubuntu GraphicsCard: NVIDIA Corporation G84M [GeForce 8600M GT] [10de:0407] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:022e] InstallationDate: Installed on 2011-10-16 (611 days ago) InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012) MachineType: Dell Inc. XPS M1530 MarkForUpload: True NonfreeKernelModules: nvidia Package: compiz 1:0.9.9~daily13.04.18.1~13.04-0ubuntu1 PackageArchitecture: all ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-23-generic root=UUID=67324911-aae9-47ca-a177-6c818959ed59 ro quiet splash ProcVersionSignature: Ubuntu 3.8.0-23.34-generic 3.8.11 Tags: raring raring ubuntu compiz-0.9 Uname: Linux 3.8.0-23-generic x86_64 UpgradeStatus: Upgraded to raring on 2013-04-28 (50 days ago) UserGroups: adm admin audio cdrom dialout dip fuse lpadmin netdev plugdev sambashare vboxusers video dmi.bios.date: 11/19/2008 dmi.bios.vendor: Dell Inc. dmi.bios.version: A12 dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA12:bd11/19/2008:svnDellInc.:pnXPSM1530:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: XPS M1530 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.9~daily13.04.18.1~13.04-0ubuntu1 version.ia32-libs: ia32-libs 20090808ubuntu36 version.libdrm2: libdrm2 2.4.43-0ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.1.1-0ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.1.1-0ubuntu3 version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A version.xserver-xorg-core: xserver-xorg-core 2:1.13.3-0ubuntu6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2b2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.1.0-0ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.21.6-0ubuntu4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.7-0ubuntu1 xserver.bootTime: Mon Jun 17 17:22:09 2013 xserver.configfile: /etc/X11/xorg.conf xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.13.3-0ubuntu6 To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/1192028/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1302374] [NEW] No sound after upgrade packages and dist
Public bug reported: Hi. I upgrade packages in the morning, next upgrade kernel (dist-upgrade) and after restart i have no sound, no tray sound icon. Below history what I'm done: Start-Date: 2014-04-04 08:02:30 Commandline: apt-get upgrade Upgrade: apt:amd64 (0.9.15.4ubuntu2, 0.9.15.4ubuntu3), kerneloops-daemon:amd64 (0.12+git20090217-3ubuntu7, 0.12+git20090217-3ubuntu8), libfontembed1:amd64 (1.0.50-0ubuntu1, 1.0.51-0ubuntu1), libgdiplus:amd64 (2.11+git20131008.9732566-4ubuntu1, 2.11+git20131008.9732566-5ubuntu1), libgail-3-0:amd64 (3.10.7-0ubuntu4, 3.10.7-0ubuntu5), python-samba:amd64 (4.1.3+dfsg-2ubuntu5, 4.1.6+dfsg-1ubuntu1), apt-transport-https:amd64 (0.9.15.4ubuntu2, 0.9.15.4ubuntu3), libindicator3-7:amd64 (12.10.2+14.04.20140304-0ubuntu1, 12.10.2+14.04.20140402-0ubuntu1), libphonon4:amd64 (4.7.1-0ubuntu7, 4.7.1-0ubuntu8), language-pack-pl:amd64 (14.04+20140321, 14.04+20140401), gsettings-ubuntu-schemas:amd64 (0.0.1+14.04.20140224-0ubuntu1, 0.0.1+14.04.20140401-0ubuntu1), phonon:amd64 (4.7.1-0ubuntu7, 4.7.1-0ubuntu8), gir1.2-packagekitglib-1.0:amd64 (0.8.12-1ubuntu4, 0.8.12-1ubuntu5), gir1.2-gtk-3.0:amd64 (3.10.7-0ubuntu4, 3.10.7-0ubuntu5), apt-utils:amd64 (0.9.15.4ubuntu2, 0.9.15.4ubuntu3), ubuntu-minimal:amd64 (1.322, 1.324), plymouth-theme-ubuntu-text:amd64 (0.8.8-0ubuntu15, 0.8.8-0ubuntu16), parted:amd64 (2.3-17, 2.3-18), libgudev-1.0-0:amd64 (204-5ubuntu13, 204-5ubuntu16), python-apt:amd64 (0.9.3.4build1, 0.9.3.5), command-not-found:amd64 (0.3ubuntu10, 0.3ubuntu12), tzdata-java:amd64 (2014a-1, 2014b-1), file:amd64 (5.14-2ubuntu2, 5.14-2ubuntu3), libmagic1:amd64 (5.14-2ubuntu2, 5.14-2ubuntu3), python3-commandnotfound:amd64 (0.3ubuntu10, 0.3ubuntu12), libglib2.0-0:amd64 (2.40.0-1ubuntu1, 2.40.0-2), libapt-inst1.5:amd64 (0.9.15.4ubuntu2, 0.9.15.4ubuntu3), libnss3-1d:amd64 (3.15.4-1ubuntu6, 3.15.4-1ubuntu7), libgtk-3-bin:amd64 (3.10.7-0ubuntu4, 3.10.7-0ubuntu5), libbluetooth3:amd64 (4.101-0ubuntu10, 4.101-0ubuntu11), bluez-cups:amd64 (4.101-0ubuntu10, 4.101-0ubuntu11), plymouth:amd64 (0.8.8-0ubuntu15, 0.8.8-0ubuntu16), libnss3-nssdb:amd64 (3.15.4-1ubuntu6, 3.15.4-1ubuntu7), ubuntu-standard:amd64 (1.322, 1.324), libglib2.0-data:amd64 (2.40.0-1ubuntu1, 2.40.0-2), bluez-alsa:amd64 (4.101-0ubuntu10, 4.101-0ubuntu11), gir1.2-gudev-1.0:amd64 (204-5ubuntu13, 204-5ubuntu16), indicator-application:amd64 (12.10.1+14.04.20140324-0ubuntu1, 12.10.1+14.04.20140402-0ubuntu1), samba-common-bin:amd64 (4.1.3+dfsg-2ubuntu5, 4.1.6+dfsg-1ubuntu1), cups-browsed:amd64 (1.0.50-0ubuntu1, 1.0.51-0ubuntu1), libparted0debian1:amd64 (2.3-17, 2.3-18), python-commandnotfound:amd64 (0.3ubuntu10, 0.3ubuntu12), cups-filters-core-drivers:amd64 (1.0.50-0ubuntu1, 1.0.51-0ubuntu1), language-pack-gnome-en:amd64 (14.04+20140321, 14.04+20140401), xfdesktop4-data:amd64 (4.11.4-1ubuntu2, 4.11.5-0ubuntu1), acpid:amd64 (2.0.21-1ubuntu1, 2.0.21-1ubuntu2), ubuntu-sso-client:amd64 (13.10-0ubuntu4, 13.10-0ubuntu5), command-not-found-data:amd64 (0.3ubuntu10, 0.3ubuntu12), samba-libs:amd64 (4.1.3+dfsg-2ubuntu5, 4.1.6+dfsg-1ubuntu1), libapt-pkg4.12:amd64 (0.9.15.4ubuntu2, 0.9.15.4ubuntu3), python3-apt:amd64 (0.9.3.4build1, 0.9.3.5), libgtk-3-0:amd64 (3.10.7-0ubuntu4, 3.10.7-0ubuntu5), bluez:amd64 (4.101-0ubuntu10, 4.101-0ubuntu11), libnss3:amd64 (3.15.4-1ubuntu6, 3.15.4-1ubuntu7), indicator-sound:amd64 (12.10.2+14.04.20140324.is.12.10.2+14.04.20140320-0ubuntu1, 12.10.2+14.04.20140401-0ubuntu1), apache2-data:amd64 (2.4.7-1ubuntu3, 2.4.7-1ubuntu4), python-smbc:amd64 (1.0.13-0ubuntu6, 1.0.14.1-0ubuntu2), cups-filters:amd64 (1.0.50-0ubuntu1, 1.0.51-0ubuntu1), libplymouth2:amd64 (0.8.8-0ubuntu15, 0.8.8-0ubuntu16), unity-settings-daemon:amd64 (14.04.0+14.04.20140310-0ubuntu2, 14.04.0+14.04.20140402-0ubuntu1), smbclient:amd64 (4.1.3+dfsg-2ubuntu5, 4.1.6+dfsg-1ubuntu1), lightdm:amd64 (1.9.13-0ubuntu1, 1.9.14-0ubuntu1), libgtk-3-common:amd64 (3.10.7-0ubuntu4, 3.10.7-0ubuntu5), language-pack-gnome-pl:amd64 (14.04+20140321, 14.04+20140401), python-ubuntu-sso-client:amd64 (13.10-0ubuntu4, 13.10-0ubuntu5), liblightdm-gobject-1-0:amd64 (1.9.13-0ubuntu1, 1.9.14-0ubuntu1), xfdesktop4:amd64 (4.11.4-1ubuntu2, 4.11.5-0ubuntu1), xserver-xorg-video-sis:amd64 (0.10.7-0ubuntu5, 0.10.7-0ubuntu6), apache2:amd64 (2.4.7-1ubuntu3, 2.4.7-1ubuntu4), tzdata:amd64 (2014a-1, 2014b-1), libglib2.0-bin:amd64 (2.40.0-1ubuntu1, 2.40.0-2), apache2-bin:amd64 (2.4.7-1ubuntu3, 2.4.7-1ubuntu4), libwbclient0:amd64 (4.1.3+dfsg-2ubuntu5, 4.1.6+dfsg-1ubuntu1), linux-libc-dev:amd64 (3.13.0-20.42, 3.13.0-22.44), python-apt-common:amd64 (0.9.3.4build1, 0.9.3.5), samba-common:amd64 (4.1.3+dfsg-2ubuntu5, 4.1.6+dfsg-1ubuntu1), language-pack-en:amd64 (14.04+20140321, 14.04+20140401), plymouth-label:amd64 (0.8.8-0ubuntu15, 0.8.8-0ubuntu16), libpackagekit-glib2-16:amd64 (0.8.12-1ubuntu4, 0.8.12-1ubuntu5), libsmbclient:amd64 (4.1.3+dfsg-2ubuntu5, 4.1.6+dfsg-1ubuntu1), libcupsfilters1:amd64 (1.0.50-0ubuntu1, 1.0.51-0ubuntu1) End-Date:
[Desktop-packages] [Bug 1302368] Re: evolution crashed when check folder in Subscriptions dialog
*** This bug is a duplicate of bug 1293144 *** https://bugs.launchpad.net/bugs/1293144 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1293144, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: CoreDump.gz https://bugs.launchpad.net/bugs/1302368/+attachment/4064795/+files/CoreDump.gz ** Attachment removed: Disassembly.txt https://bugs.launchpad.net/bugs/1302368/+attachment/4064797/+files/Disassembly.txt ** Attachment removed: ProcMaps.txt https://bugs.launchpad.net/bugs/1302368/+attachment/4064799/+files/ProcMaps.txt ** Attachment removed: ProcStatus.txt https://bugs.launchpad.net/bugs/1302368/+attachment/4064800/+files/ProcStatus.txt ** Attachment removed: Registers.txt https://bugs.launchpad.net/bugs/1302368/+attachment/4064801/+files/Registers.txt ** Attachment removed: Stacktrace.txt https://bugs.launchpad.net/bugs/1302368/+attachment/4064802/+files/Stacktrace.txt ** Attachment removed: ThreadStacktrace.txt https://bugs.launchpad.net/bugs/1302368/+attachment/4064803/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 1293144 ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evolution in Ubuntu. https://bugs.launchpad.net/bugs/1302368 Title: evolution crashed when check folder in Subscriptions dialog Status in “evolution” package in Ubuntu: New Bug description: evolution crashed with SIGSEGV in g_closure_invoke() ProblemType: Crash DistroRelease: Ubuntu 14.04 Package: evolution 3.10.4-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-22.44-generic 3.13.8 Uname: Linux 3.13.0-22-generic x86_64 ApportVersion: 2.14-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Fri Apr 4 09:52:23 2014 ExecutablePath: /usr/bin/evolution InstallationDate: Installed on 2014-02-25 (37 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140224) ProcCmdline: evolution SegvAnalysis: Segfault happened at: 0x7f66c246c520:mov0x18(%r14),%rdi PC (0x7f66c246c520) ok source 0x18(%r14) (0x0018) not located in a known VMA region (needed readable region)! destination %rdi ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: evolution StacktraceTop: ?? () from /usr/lib/evolution/3.10/libevolution-mail.so.0 g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_signal_emit () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: evolution crashed with SIGSEGV in g_closure_invoke() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1302368/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1063358] Re: Wireless authentication required dialog opens multiple times
I have the exact same problem, but with 802.1x authentication. I've included a part of a screenshot as illustration. Only viable solution is to log out and back in.. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-applet in Ubuntu. https://bugs.launchpad.net/bugs/1063358 Title: Wireless authentication required dialog opens multiple times Status in “network-manager-applet” package in Ubuntu: Confirmed Bug description: When the wireless applet is disconnected from a wireless router that is password-protected (WPA-2), the wireless authentication window opens. After approximitely 5 mins, another one opens on top of the first. This continues, and as the windows take about two minutes to become responsive, they stack up quickly when you are away for a period of time. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: network-manager-gnome 0.9.6.2-0ubuntu5 ProcVersionSignature: Ubuntu 3.5.0-16.25-generic 3.5.4 Uname: Linux 3.5.0-16-generic i686 ApportVersion: 2.6.1-0ubuntu1 Architecture: i386 Date: Mon Oct 8 07:06:03 2012 ExecutablePath: /usr/bin/nm-applet IfupdownConfig: auto lo iface lo inet loopback InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release i386 (20111012) IpRoute: default via 192.168.123.254 dev wlan0 proto static 169.254.0.0/16 dev wlan0 scope link metric 1000 192.168.123.0/24 dev wlan0 proto kernel scope link src 192.168.123.177 metric 9 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: network-manager-applet UpgradeStatus: Upgraded to quantal on 2012-07-12 (87 days ago) mtime.conffile..etc.xdg.autostart.nm.applet.desktop: 2012-06-24T07:30:18.478928 nmcli-con: NAME UUID TYPE TIMESTAMPTIMESTAMP-REAL AUTOCONNECT READONLY DBUS-PATH Wired connection 1a2a25387-07d8-475f-904a-b25b432ae732 802-3-ethernet1347071471 Sat 08 Sep 2012 14:31:11 NZST yes no /org/freedesktop/NetworkManager/Settings/1 x23 Wireless Connection 08f90b80-d18d-4a5e-9587-0410124546d4 802-11-wireless 1349633171 Mon 08 Oct 2012 07:06:11 NZDT yes no /org/freedesktop/NetworkManager/Settings/0 nmcli-dev: DEVICE TYPE STATE DBUS-PATH eth0 802-3-ethernetunavailable /org/freedesktop/NetworkManager/Devices/1 wlan0 802-11-wireless connected /org/freedesktop/NetworkManager/Devices/0 nmcli-nm: RUNNING VERSIONSTATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN running 0.9.6.0connected enabled enabled enabledenabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1063358/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1063358] Re: Wireless authentication required dialog opens multiple times
I have the exact same problem, but with 802.1x authentication. I've included a part of a screenshot as illustration. Only viable solution is to log out and back in.. ** Attachment added: Screenshot of bug https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1063358/+attachment/4064831/+files/AuthenticationDialog.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-applet in Ubuntu. https://bugs.launchpad.net/bugs/1063358 Title: Wireless authentication required dialog opens multiple times Status in “network-manager-applet” package in Ubuntu: Confirmed Bug description: When the wireless applet is disconnected from a wireless router that is password-protected (WPA-2), the wireless authentication window opens. After approximitely 5 mins, another one opens on top of the first. This continues, and as the windows take about two minutes to become responsive, they stack up quickly when you are away for a period of time. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: network-manager-gnome 0.9.6.2-0ubuntu5 ProcVersionSignature: Ubuntu 3.5.0-16.25-generic 3.5.4 Uname: Linux 3.5.0-16-generic i686 ApportVersion: 2.6.1-0ubuntu1 Architecture: i386 Date: Mon Oct 8 07:06:03 2012 ExecutablePath: /usr/bin/nm-applet IfupdownConfig: auto lo iface lo inet loopback InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release i386 (20111012) IpRoute: default via 192.168.123.254 dev wlan0 proto static 169.254.0.0/16 dev wlan0 scope link metric 1000 192.168.123.0/24 dev wlan0 proto kernel scope link src 192.168.123.177 metric 9 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: network-manager-applet UpgradeStatus: Upgraded to quantal on 2012-07-12 (87 days ago) mtime.conffile..etc.xdg.autostart.nm.applet.desktop: 2012-06-24T07:30:18.478928 nmcli-con: NAME UUID TYPE TIMESTAMPTIMESTAMP-REAL AUTOCONNECT READONLY DBUS-PATH Wired connection 1a2a25387-07d8-475f-904a-b25b432ae732 802-3-ethernet1347071471 Sat 08 Sep 2012 14:31:11 NZST yes no /org/freedesktop/NetworkManager/Settings/1 x23 Wireless Connection 08f90b80-d18d-4a5e-9587-0410124546d4 802-11-wireless 1349633171 Mon 08 Oct 2012 07:06:11 NZDT yes no /org/freedesktop/NetworkManager/Settings/0 nmcli-dev: DEVICE TYPE STATE DBUS-PATH eth0 802-3-ethernetunavailable /org/freedesktop/NetworkManager/Devices/1 wlan0 802-11-wireless connected /org/freedesktop/NetworkManager/Devices/0 nmcli-nm: RUNNING VERSIONSTATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN running 0.9.6.0connected enabled enabled enabledenabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1063358/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1302377] [NEW] LibreOffice Writer mail merge wizard needs Base to operate but there's no message
Public bug reported: Ubuntu comes without LibreOffice Base by default. In LibreOffice Writer, in Mail Merge wizard, at step 3, there's a window that allows you to select data sources. It does not work (basically, after selecting a file you cannot proceed) unless Base is installed. Expected behaviour: LibreOffice prompting about installing Base, in the same way it does when you want to run Bibliography Wizard ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: libreoffice-writer 1:4.2.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-16.36-generic 3.13.5 Uname: Linux 3.13.0-16-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Apr 4 09:08:17 2014 InstallationDate: Installed on 2014-03-08 (26 days ago) InstallationMedia: Ubuntu-GNOME 14.04 Trusty Tahr - Alpha amd64 (20140226) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=pl_PL.UTF-8 SHELL=/bin/bash SourcePackage: libreoffice UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: libreoffice (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1302377 Title: LibreOffice Writer mail merge wizard needs Base to operate but there's no message Status in “libreoffice” package in Ubuntu: New Bug description: Ubuntu comes without LibreOffice Base by default. In LibreOffice Writer, in Mail Merge wizard, at step 3, there's a window that allows you to select data sources. It does not work (basically, after selecting a file you cannot proceed) unless Base is installed. Expected behaviour: LibreOffice prompting about installing Base, in the same way it does when you want to run Bibliography Wizard ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: libreoffice-writer 1:4.2.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-16.36-generic 3.13.5 Uname: Linux 3.13.0-16-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Apr 4 09:08:17 2014 InstallationDate: Installed on 2014-03-08 (26 days ago) InstallationMedia: Ubuntu-GNOME 14.04 Trusty Tahr - Alpha amd64 (20140226) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=pl_PL.UTF-8 SHELL=/bin/bash SourcePackage: libreoffice UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1302377/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1302374] Re: No sound after upgrade packages and dist
Same issue on my i386 system: - the sound icon is active - get no sound - the dummy hardware is selected inside the sound System Settings. And there is no other hardware choice. So that is the main problem to resolve. ** Tags added: i386 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1302374 Title: No sound after upgrade packages and dist Status in “pulseaudio” package in Ubuntu: Confirmed Bug description: Hi. I upgrade packages in the morning, next upgrade kernel (dist-upgrade) and after restart i have no sound, no tray sound icon. Below history what I'm done: Start-Date: 2014-04-04 08:02:30 Commandline: apt-get upgrade Upgrade: apt:amd64 (0.9.15.4ubuntu2, 0.9.15.4ubuntu3), kerneloops-daemon:amd64 (0.12+git20090217-3ubuntu7, 0.12+git20090217-3ubuntu8), libfontembed1:amd64 (1.0.50-0ubuntu1, 1.0.51-0ubuntu1), libgdiplus:amd64 (2.11+git20131008.9732566-4ubuntu1, 2.11+git20131008.9732566-5ubuntu1), libgail-3-0:amd64 (3.10.7-0ubuntu4, 3.10.7-0ubuntu5), python-samba:amd64 (4.1.3+dfsg-2ubuntu5, 4.1.6+dfsg-1ubuntu1), apt-transport-https:amd64 (0.9.15.4ubuntu2, 0.9.15.4ubuntu3), libindicator3-7:amd64 (12.10.2+14.04.20140304-0ubuntu1, 12.10.2+14.04.20140402-0ubuntu1), libphonon4:amd64 (4.7.1-0ubuntu7, 4.7.1-0ubuntu8), language-pack-pl:amd64 (14.04+20140321, 14.04+20140401), gsettings-ubuntu-schemas:amd64 (0.0.1+14.04.20140224-0ubuntu1, 0.0.1+14.04.20140401-0ubuntu1), phonon:amd64 (4.7.1-0ubuntu7, 4.7.1-0ubuntu8), gir1.2-packagekitglib-1.0:amd64 (0.8.12-1ubuntu4, 0.8.12-1ubuntu5), gir1.2-gtk-3.0:amd64 (3.10.7-0ubuntu4, 3.10.7-0ubuntu5), apt-utils:amd64 (0.9.15.4ubuntu2, 0.9.15.4ubuntu3), ubuntu-minimal:amd64 (1.322, 1.324), plymouth-theme-ubuntu-text:amd64 (0.8.8-0ubuntu15, 0.8.8-0ubuntu16), parted:amd64 (2.3-17, 2.3-18), libgudev-1.0-0:amd64 (204-5ubuntu13, 204-5ubuntu16), python-apt:amd64 (0.9.3.4build1, 0.9.3.5), command-not-found:amd64 (0.3ubuntu10, 0.3ubuntu12), tzdata-java:amd64 (2014a-1, 2014b-1), file:amd64 (5.14-2ubuntu2, 5.14-2ubuntu3), libmagic1:amd64 (5.14-2ubuntu2, 5.14-2ubuntu3), python3-commandnotfound:amd64 (0.3ubuntu10, 0.3ubuntu12), libglib2.0-0:amd64 (2.40.0-1ubuntu1, 2.40.0-2), libapt-inst1.5:amd64 (0.9.15.4ubuntu2, 0.9.15.4ubuntu3), libnss3-1d:amd64 (3.15.4-1ubuntu6, 3.15.4-1ubuntu7), libgtk-3-bin:amd64 (3.10.7-0ubuntu4, 3.10.7-0ubuntu5), libbluetooth3:amd64 (4.101-0ubuntu10, 4.101-0ubuntu11), bluez-cups:amd64 (4.101-0ubuntu10, 4.101-0ubuntu11), plymouth:amd64 (0.8.8-0ubuntu15, 0.8.8-0ubuntu16), libnss3-nssdb:amd64 (3.15.4-1ubuntu6, 3.15.4-1ubuntu7), ubuntu-standard:amd64 (1.322, 1.324), libglib2.0-data:amd64 (2.40.0-1ubuntu1, 2.40.0-2), bluez-alsa:amd64 (4.101-0ubuntu10, 4.101-0ubuntu11), gir1.2-gudev-1.0:amd64 (204-5ubuntu13, 204-5ubuntu16), indicator-application:amd64 (12.10.1+14.04.20140324-0ubuntu1, 12.10.1+14.04.20140402-0ubuntu1), samba-common-bin:amd64 (4.1.3+dfsg-2ubuntu5, 4.1.6+dfsg-1ubuntu1), cups-browsed:amd64 (1.0.50-0ubuntu1, 1.0.51-0ubuntu1), libparted0debian1:amd64 (2.3-17, 2.3-18), python-commandnotfound:amd64 (0.3ubuntu10, 0.3ubuntu12), cups-filters-core-drivers:amd64 (1.0.50-0ubuntu1, 1.0.51-0ubuntu1), language-pack-gnome-en:amd64 (14.04+20140321, 14.04+20140401), xfdesktop4-data:amd64 (4.11.4-1ubuntu2, 4.11.5-0ubuntu1), acpid:amd64 (2.0.21-1ubuntu1, 2.0.21-1ubuntu2), ubuntu-sso-client:amd64 (13.10-0ubuntu4, 13.10-0ubuntu5), command-not-found-data:amd64 (0.3ubuntu10, 0.3ubuntu12), samba-libs:amd64 (4.1.3+dfsg-2ubuntu5, 4.1.6+dfsg-1ubuntu1), libapt-pkg4.12:amd64 (0.9.15.4ubuntu2, 0.9.15.4ubuntu3), python3-apt:amd64 (0.9.3.4build1, 0.9.3.5), libgtk-3-0:amd64 (3.10.7-0ubuntu4, 3.10.7-0ubuntu5), bluez:amd64 (4.101-0ubuntu10, 4.101-0ubuntu11), libnss3:amd64 (3.15.4-1ubuntu6, 3.15.4-1ubuntu7), indicator-sound:amd64 (12.10.2+14.04.20140324.is.12.10.2+14.04.20140320-0ubuntu1, 12.10.2+14.04.20140401-0ubuntu1), apache2-data:amd64 (2.4.7-1ubuntu3, 2.4.7-1ubuntu4), python-smbc:amd64 (1.0.13-0ubuntu6, 1.0.14.1-0ubuntu2), cups-filters:amd64 (1.0.50-0ubuntu1, 1.0.51-0ubuntu1), libplymouth2:amd64 (0.8.8-0ubuntu15, 0.8.8-0ubuntu16), unity-settings-daemon:amd64 (14.04.0+14.04.20140310-0ubuntu2, 14.04.0+14.04.20140402-0ubuntu1), smbclient:amd64 (4.1.3+dfsg-2ubuntu5, 4.1.6+dfsg-1ubuntu1), lightdm:amd64 (1.9.13-0ubuntu1, 1.9.14-0ubuntu1), libgtk-3-common:amd64 (3.10.7-0ubuntu4, 3.10.7-0ubuntu5), language-pack-gnome-pl:amd64 (14.04+20140321, 14.04+20140401), python-ubuntu-sso-client:amd64 (13.10-0ubuntu4, 13.10-0ubuntu5), liblightdm-gobject-1-0:amd64 (1.9.13-0ubuntu1, 1.9.14-0ubuntu1), xfdesktop4:amd64 (4.11.4-1ubuntu2, 4.11.5-0ubuntu1), xserver-xorg-video-sis:amd64 (0.10.7-0ubuntu5, 0.10.7-0ubuntu6), apache2:amd64 (2.4.7-1ubuntu3, 2.4.7-1ubuntu4), tzdata:amd64 (2014a-1, 2014b-1), libglib2.0-bin:amd64 (2.40.0-1ubuntu1, 2.40.0-2), apache2-bin:amd64 (2.4.7-1ubuntu3, 2.4.7-1ubuntu4), libwbclient0:amd64
[Desktop-packages] [Bug 1301257] Re: rhythmbox crashed when syncing with iPad (iOS7.1)
** Changed in: rhythmbox Status: Unknown = New ** Changed in: rhythmbox Importance: Unknown = Critical -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to rhythmbox in Ubuntu. https://bugs.launchpad.net/bugs/1301257 Title: rhythmbox crashed when syncing with iPad (iOS7.1) Status in The Rhythmbox Music Management Application: New Status in “rhythmbox” package in Ubuntu: New Bug description: [ 35.642883] rhythmbox[2290]: segfault at 1f0036 ip 7ff1d6c07c3d sp 7fffe662ee10 error 4 in libgobject-2.0.so.0.4000.0[7ff1d6bd5000+4f000] ProblemType: Crash DistroRelease: Ubuntu 14.04 Package: rhythmbox 3.0.1-1ubuntu16 ProcVersionSignature: Ubuntu 3.13.0-20.42-generic 3.13.7 Uname: Linux 3.13.0-20-generic x86_64 ApportVersion: 2.14-0ubuntu1 Architecture: amd64 CrashCounter: 1 CurrentDesktop: Unity Date: Wed Apr 2 10:31:47 2014 ExecutablePath: /usr/bin/rhythmbox InstallationDate: Installed on 2014-03-20 (12 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140318) ProcCmdline: /usr/bin/rhythmbox ProcEnviron: XDG_RUNTIME_DIR=set SHELL=/bin/bash LANGUAGE=de_DE PATH=(custom, no user) LANG=de_DE.UTF-8 SegvAnalysis: Segfault happened at: 0x7ff1d6c07c3d g_type_check_value_holds+61: testb $0x8,0x16(%rbx) PC (0x7ff1d6c07c3d) ok source $0x8 ok destination 0x16(%rbx) (0x1f0036) not located in a known VMA region (needed writable region)! SegvReason: writing unknown VMA Signal: 11 SourcePackage: rhythmbox StacktraceTop: g_type_check_value_holds () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgpod.so.4 itdb_parse () from /usr/lib/x86_64-linux-gnu/libgpod.so.4 rb_ipod_db_new () from /usr/lib/rhythmbox/plugins/ipod/libipod.so ?? () from /usr/lib/rhythmbox/plugins/ipod/libipod.so Title: rhythmbox crashed with SIGSEGV in g_type_check_value_holds() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers To manage notifications about this bug go to: https://bugs.launchpad.net/rhythmbox/+bug/1301257/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1302374] Re: No sound after upgrade packages and dist
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: pulseaudio (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1302374 Title: No sound after upgrade packages and dist Status in “pulseaudio” package in Ubuntu: Confirmed Bug description: Hi. I upgrade packages in the morning, next upgrade kernel (dist-upgrade) and after restart i have no sound, no tray sound icon. Below history what I'm done: Start-Date: 2014-04-04 08:02:30 Commandline: apt-get upgrade Upgrade: apt:amd64 (0.9.15.4ubuntu2, 0.9.15.4ubuntu3), kerneloops-daemon:amd64 (0.12+git20090217-3ubuntu7, 0.12+git20090217-3ubuntu8), libfontembed1:amd64 (1.0.50-0ubuntu1, 1.0.51-0ubuntu1), libgdiplus:amd64 (2.11+git20131008.9732566-4ubuntu1, 2.11+git20131008.9732566-5ubuntu1), libgail-3-0:amd64 (3.10.7-0ubuntu4, 3.10.7-0ubuntu5), python-samba:amd64 (4.1.3+dfsg-2ubuntu5, 4.1.6+dfsg-1ubuntu1), apt-transport-https:amd64 (0.9.15.4ubuntu2, 0.9.15.4ubuntu3), libindicator3-7:amd64 (12.10.2+14.04.20140304-0ubuntu1, 12.10.2+14.04.20140402-0ubuntu1), libphonon4:amd64 (4.7.1-0ubuntu7, 4.7.1-0ubuntu8), language-pack-pl:amd64 (14.04+20140321, 14.04+20140401), gsettings-ubuntu-schemas:amd64 (0.0.1+14.04.20140224-0ubuntu1, 0.0.1+14.04.20140401-0ubuntu1), phonon:amd64 (4.7.1-0ubuntu7, 4.7.1-0ubuntu8), gir1.2-packagekitglib-1.0:amd64 (0.8.12-1ubuntu4, 0.8.12-1ubuntu5), gir1.2-gtk-3.0:amd64 (3.10.7-0ubuntu4, 3.10.7-0ubuntu5), apt-utils:amd64 (0.9.15.4ubuntu2, 0.9.15.4ubuntu3), ubuntu-minimal:amd64 (1.322, 1.324), plymouth-theme-ubuntu-text:amd64 (0.8.8-0ubuntu15, 0.8.8-0ubuntu16), parted:amd64 (2.3-17, 2.3-18), libgudev-1.0-0:amd64 (204-5ubuntu13, 204-5ubuntu16), python-apt:amd64 (0.9.3.4build1, 0.9.3.5), command-not-found:amd64 (0.3ubuntu10, 0.3ubuntu12), tzdata-java:amd64 (2014a-1, 2014b-1), file:amd64 (5.14-2ubuntu2, 5.14-2ubuntu3), libmagic1:amd64 (5.14-2ubuntu2, 5.14-2ubuntu3), python3-commandnotfound:amd64 (0.3ubuntu10, 0.3ubuntu12), libglib2.0-0:amd64 (2.40.0-1ubuntu1, 2.40.0-2), libapt-inst1.5:amd64 (0.9.15.4ubuntu2, 0.9.15.4ubuntu3), libnss3-1d:amd64 (3.15.4-1ubuntu6, 3.15.4-1ubuntu7), libgtk-3-bin:amd64 (3.10.7-0ubuntu4, 3.10.7-0ubuntu5), libbluetooth3:amd64 (4.101-0ubuntu10, 4.101-0ubuntu11), bluez-cups:amd64 (4.101-0ubuntu10, 4.101-0ubuntu11), plymouth:amd64 (0.8.8-0ubuntu15, 0.8.8-0ubuntu16), libnss3-nssdb:amd64 (3.15.4-1ubuntu6, 3.15.4-1ubuntu7), ubuntu-standard:amd64 (1.322, 1.324), libglib2.0-data:amd64 (2.40.0-1ubuntu1, 2.40.0-2), bluez-alsa:amd64 (4.101-0ubuntu10, 4.101-0ubuntu11), gir1.2-gudev-1.0:amd64 (204-5ubuntu13, 204-5ubuntu16), indicator-application:amd64 (12.10.1+14.04.20140324-0ubuntu1, 12.10.1+14.04.20140402-0ubuntu1), samba-common-bin:amd64 (4.1.3+dfsg-2ubuntu5, 4.1.6+dfsg-1ubuntu1), cups-browsed:amd64 (1.0.50-0ubuntu1, 1.0.51-0ubuntu1), libparted0debian1:amd64 (2.3-17, 2.3-18), python-commandnotfound:amd64 (0.3ubuntu10, 0.3ubuntu12), cups-filters-core-drivers:amd64 (1.0.50-0ubuntu1, 1.0.51-0ubuntu1), language-pack-gnome-en:amd64 (14.04+20140321, 14.04+20140401), xfdesktop4-data:amd64 (4.11.4-1ubuntu2, 4.11.5-0ubuntu1), acpid:amd64 (2.0.21-1ubuntu1, 2.0.21-1ubuntu2), ubuntu-sso-client:amd64 (13.10-0ubuntu4, 13.10-0ubuntu5), command-not-found-data:amd64 (0.3ubuntu10, 0.3ubuntu12), samba-libs:amd64 (4.1.3+dfsg-2ubuntu5, 4.1.6+dfsg-1ubuntu1), libapt-pkg4.12:amd64 (0.9.15.4ubuntu2, 0.9.15.4ubuntu3), python3-apt:amd64 (0.9.3.4build1, 0.9.3.5), libgtk-3-0:amd64 (3.10.7-0ubuntu4, 3.10.7-0ubuntu5), bluez:amd64 (4.101-0ubuntu10, 4.101-0ubuntu11), libnss3:amd64 (3.15.4-1ubuntu6, 3.15.4-1ubuntu7), indicator-sound:amd64 (12.10.2+14.04.20140324.is.12.10.2+14.04.20140320-0ubuntu1, 12.10.2+14.04.20140401-0ubuntu1), apache2-data:amd64 (2.4.7-1ubuntu3, 2.4.7-1ubuntu4), python-smbc:amd64 (1.0.13-0ubuntu6, 1.0.14.1-0ubuntu2), cups-filters:amd64 (1.0.50-0ubuntu1, 1.0.51-0ubuntu1), libplymouth2:amd64 (0.8.8-0ubuntu15, 0.8.8-0ubuntu16), unity-settings-daemon:amd64 (14.04.0+14.04.20140310-0ubuntu2, 14.04.0+14.04.20140402-0ubuntu1), smbclient:amd64 (4.1.3+dfsg-2ubuntu5, 4.1.6+dfsg-1ubuntu1), lightdm:amd64 (1.9.13-0ubuntu1, 1.9.14-0ubuntu1), libgtk-3-common:amd64 (3.10.7-0ubuntu4, 3.10.7-0ubuntu5), language-pack-gnome-pl:amd64 (14.04+20140321, 14.04+20140401), python-ubuntu-sso-client:amd64 (13.10-0ubuntu4, 13.10-0ubuntu5), liblightdm-gobject-1-0:amd64 (1.9.13-0ubuntu1, 1.9.14-0ubuntu1), xfdesktop4:amd64 (4.11.4-1ubuntu2, 4.11.5-0ubuntu1), xserver-xorg-video-sis:amd64 (0.10.7-0ubuntu5, 0.10.7-0ubuntu6), apache2:amd64 (2.4.7-1ubuntu3, 2.4.7-1ubuntu4), tzdata:amd64 (2014a-1, 2014b-1), libglib2.0-bin:amd64 (2.40.0-1ubuntu1, 2.40.0-2), apache2-bin:amd64 (2.4.7-1ubuntu3, 2.4.7-1ubuntu4), libwbclient0:amd64 (4.1.3+dfsg-2ubuntu5, 4.1.6+dfsg-1ubuntu1), linux-libc-dev:amd64 (3.13.0-20.42, 3.13.0-22.44),
[Desktop-packages] [Bug 1063359] Re: Wireless authentication required dialog opens multiple times
*** This bug is a duplicate of bug 1063358 *** https://bugs.launchpad.net/bugs/1063358 Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: network-manager-applet (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-applet in Ubuntu. https://bugs.launchpad.net/bugs/1063359 Title: Wireless authentication required dialog opens multiple times Status in “network-manager-applet” package in Ubuntu: Confirmed Bug description: When the wireless applet is disconnected from a wireless router that is password-protected (WPA-2), the wireless authentication window opens. After approximitely 5 mins, another one opens on top of the first. This continues, and as the windows take about two minutes to become responsive, they stack up quickly when you are away for a period of time. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: network-manager-gnome 0.9.6.2-0ubuntu5 ProcVersionSignature: Ubuntu 3.5.0-16.25-generic 3.5.4 Uname: Linux 3.5.0-16-generic i686 ApportVersion: 2.6.1-0ubuntu1 Architecture: i386 Date: Mon Oct 8 07:06:03 2012 ExecutablePath: /usr/bin/nm-applet IfupdownConfig: auto lo iface lo inet loopback InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release i386 (20111012) IpRoute: default via 192.168.123.254 dev wlan0 proto static 169.254.0.0/16 dev wlan0 scope link metric 1000 192.168.123.0/24 dev wlan0 proto kernel scope link src 192.168.123.177 metric 9 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: network-manager-applet UpgradeStatus: Upgraded to quantal on 2012-07-12 (87 days ago) mtime.conffile..etc.xdg.autostart.nm.applet.desktop: 2012-06-24T07:30:18.478928 nmcli-con: NAME UUID TYPE TIMESTAMPTIMESTAMP-REAL AUTOCONNECT READONLY DBUS-PATH Wired connection 1a2a25387-07d8-475f-904a-b25b432ae732 802-3-ethernet1347071471 Sat 08 Sep 2012 14:31:11 NZST yes no /org/freedesktop/NetworkManager/Settings/1 x23 Wireless Connection 08f90b80-d18d-4a5e-9587-0410124546d4 802-11-wireless 1349633171 Mon 08 Oct 2012 07:06:11 NZDT yes no /org/freedesktop/NetworkManager/Settings/0 nmcli-dev: DEVICE TYPE STATE DBUS-PATH eth0 802-3-ethernetunavailable /org/freedesktop/NetworkManager/Devices/1 wlan0 802-11-wireless connected /org/freedesktop/NetworkManager/Devices/0 nmcli-nm: RUNNING VERSIONSTATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN running 0.9.6.0connected enabled enabled enabledenabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1063359/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1224575] Re: gnome-control-center keyboard no longer has way to modify caps lock key behavior
The proposed workaround with gnome-tweak-tool doesn't work for me. I can change the behaviour of Caps Lock in some ways, but not in others. Swiching Caps Lock with ESC works, but disabling it doesn't! (I use Unity with German localization. Could that affect the behaviour?) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1224575 Title: gnome-control-center keyboard no longer has way to modify caps lock key behavior Status in GNOME Control Center: New Status in “gnome-control-center” package in Ubuntu: Triaged Bug description: Up until Raring, it was trivial to use the gnome-control-center to modify caps lock key behavior. In earlier versions you could do the following: - Launch System Settings - Click on Keyboard Layout - Click on Options - These options allow one to modify Caps Lock Key behavior (for example swap it with ESC) In newer versions of Saucy I try to do the following: - Launch System Settings - Click on Keyboard - Click on Layout Settings - Cannot find a location similar to these older options These older 'Keyboard Layout Options' made it very easy to do things like swaping Caps Lock for ESC which make vim users much happier. WORKAROUND == Use gnome-tweak-tool -- For other layout switching problems introduced in Ubuntu 13.10 you can see bug 1218322. -- ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: gnome-control-center 1:3.6.3-0ubuntu36 ProcVersionSignature: Ubuntu 3.11.0-7.13-generic 3.11.0 Uname: Linux 3.11.0-7-generic x86_64 ApportVersion: 2.12.1-0ubuntu3 Architecture: amd64 Date: Thu Sep 12 11:33:58 2013 InstallationDate: Installed on 2013-09-12 (0 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Alpha amd64 (20130912) MarkForUpload: True SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_gnome-control-center: activity-log-manager 0.9.7-0ubuntu4 deja-dup 27.3.1-0ubuntu1 gnome-control-center-datetime 13.10.0+13.10.20130903-0ubuntu1 gnome-control-center-signon 0.1.7~+13.10.20130724.1-0ubuntu1 gnome-control-center-unity1.3daily13.06.14.1-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1224575/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1302383] [NEW] Selecting Reboot leads to a Log out question
Public bug reported: Steps to reproduce: Execute gnome-session-quit --reboot and notice a Log out dialog. Expected a Reboot dialog. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: gnome-session-bin 3.9.90-0ubuntu12 ProcVersionSignature: Ubuntu 3.13.0-22.44-generic 3.13.8 Uname: Linux 3.13.0-22-generic x86_64 ApportVersion: 2.14-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Fri Apr 4 09:24:18 2014 InstallationDate: Installed on 2013-11-04 (150 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20131103) ProcEnviron: LANGUAGE=sv TERM=xterm PATH=(custom, no user) LANG=sv_SE.UTF-8 SHELL=/bin/bash SourcePackage: gnome-session UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-session (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1302383 Title: Selecting Reboot leads to a Log out question Status in “gnome-session” package in Ubuntu: New Bug description: Steps to reproduce: Execute gnome-session-quit --reboot and notice a Log out dialog. Expected a Reboot dialog. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: gnome-session-bin 3.9.90-0ubuntu12 ProcVersionSignature: Ubuntu 3.13.0-22.44-generic 3.13.8 Uname: Linux 3.13.0-22-generic x86_64 ApportVersion: 2.14-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Fri Apr 4 09:24:18 2014 InstallationDate: Installed on 2013-11-04 (150 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20131103) ProcEnviron: LANGUAGE=sv TERM=xterm PATH=(custom, no user) LANG=sv_SE.UTF-8 SHELL=/bin/bash SourcePackage: gnome-session UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1302383/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1302348] Re: after today's Trusty updates/restart, NM will not connect to wifi
Same issue here. I'm on an Asus VivoPC with rtl8821ae wireless card which has just been included in the 14.04 kernel. Network manager shows wireless as disabled, no connections available, can't enable it. It also shows that it's not connected to anything, even if my wired connection seems to be working fine. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1302348 Title: after today's Trusty updates/restart, NM will not connect to wifi Status in “network-manager” package in Ubuntu: New Bug description: I see all the wireless signals in the neighborhood, but the connect button does not connect my laptop to the internet. Also, history seems lost, as it reports that my wifi has never been used, when it was in use a few minutes before. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: network-manager 0.9.8.8-0ubuntu5 ProcVersionSignature: Ubuntu 3.13.0-22.44-generic 3.13.8 Uname: Linux 3.13.0-22-generic x86_64 ApportVersion: 2.14-0ubuntu1 Architecture: amd64 CurrentDesktop: KDE Date: Thu Apr 3 22:43:11 2014 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2013-06-18 (289 days ago) InstallationMedia: Kubuntu 13.04 Raring Ringtail - Release amd64 (20130424) IpRoute: default via 192.168.15.1 dev eth0 proto static 192.168.15.0/24 dev eth0 proto kernel scope link src 192.168.15.3 metric 1 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: network-manager UpgradeStatus: Upgraded to trusty on 2014-03-04 (30 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1302348/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1298611] Re: [FFe] apparmor signal and ptrace mediation
** Branch linked: lp:ubuntu/trusty-proposed/apparmor-easyprof-ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1298611 Title: [FFe] apparmor signal and ptrace mediation Status in “apparmor” package in Ubuntu: Confirmed Status in “apparmor-easyprof-ubuntu” package in Ubuntu: New Status in “libvirt” package in Ubuntu: New Status in “lightdm” package in Ubuntu: New Status in “linux” package in Ubuntu: Fix Released Status in “lxc” package in Ubuntu: New Bug description: Background: kernel and apparmor userspace updates to support signal and ptrace mediation. These packages are listed in one bug because they are related, but the FFes may be granted and the uploads may happen at different times. = linux = Summary: This feature freeze exception is requested for signal and ptrace mediation via apparmor in the kernel. When used with a compatible apparmor userspace, signals and ptrace rules are supported. When used without a compatible apparmor userspace (eg, on a precise system with a trusty backport kernel), signal and ptrace mediation is not enforced (ie, you can use this kernel with an old userspace without any issues). The fine grained mediation of signals and ptraces also incorporates improved versioning support that allows this kernel to better support older and newer userspaces. This allows for this version of the kernel to work as a backport kernel unmodified (currently a patch and config are used to provide backport kernels). The kernel patch is available at git://kernel.ubuntu.com/jj/ubuntu-trusty.git in the trusty-alpha6 branch apparmor-alpha6-sync Testing: * 12.04 system with backported kernel: DONE * test-apparmor.py: PASS (runs extensive tests (upstream and distro)) * exploratory manual testing: PASS (networking, aa-enforce with firefox, firefox works, apparmor blocks access, etc) * aa-status: PASS * lxc: PASS (containers can be created, started, shutdown) * libvirt: PASS (VMs started via openstack, and test-libvirt.py from QRT passes all tests) * 14.04 system (non-Touch) with current apparmor userspace: DONE (relevant parts of https://wiki.ubuntu.com/Process/Merges/TestPlans/AppArmor) * test-apparmor.py: PASS (runs extensive tests (upstream and distro)) * exploratory manual testing: PASS (networking, aa-enforce with firefox, firefox works, apparmor blocks access, etc) * aa-status: PASS * lxc: PASS (containers can be created, started, shutdown) * libvirt: PASS (QRT/script/test-libvirt.py (though there are 3 failures unrelated to apparmor)) * click-apparmor QRT touch image tests: PASS * apparmor-easyprof-ubuntu QRT touch image tests: PASS * 14.04 system (non-Touch) with updated apparmor userspace capable of supporting signal and ptrace mediation: DONE (relevant parts of https://wiki.ubuntu.com/Process/Merges/TestPlans/AppArmor. Note: this is marked 'done' from the kernel perspective-- the apparmor userspace upload is being prepared and tests assume userspace is using latest patches on the list) * test-apparmor.py: PASS (runs extensive tests (upstream and distro)) * exploratory manual testing: PASS (networking, aa-enforce with firefox, firefox works, apparmor blocks access, etc) * aa-status: PASS * lxc: PASS (containers can be created, started, shutdown) * libvirt: PASS (QRT/script/test-libvirt.py (though there are 3 failures unrelated to apparmor)) * click-apparmor QRT touch image tests: PASS * apparmor-easyprof-ubuntu QRT touch image tests: PASS Justification: This feature is required to support comprehensive application confinement on Ubuntu Touch. This feature adds a significant security benefit to libvirt's qemu guest isolation which is fundamental to Ubuntu on Server/Cloud. This feature also adds a welcome improvement to administrators wishing to further protect their systems. = apparmor userspace = Summary: This feature freeze exception is requested for signal and ptrace mediation for apparmor userspace. When used with a compatible kernel, signals and ptrace rules are supported. When used without a compatible kernel (eg, on Ubuntu Touch for a few weeks or with upstream kernels), signal and ptrace rules are skipped (ie, you can use this userspace with other kernels without issue). Testing: * 14.04 system with current kernel (Touch, kernel doesn't have signal and ptrace mediation yet): * https://wiki.ubuntu.com/Process/Merges/TestPlans/AppArmor: PASS (includes click-apparmor, apparmor-easyprof-ubuntu, exploratory manual testing, etc) * 14.04 system with previous kernel lacking signal and ptrace mediation (non-Touch): * https://wiki.ubuntu.com/Process/Merges/TestPlans/AppArmor: PASS (exploratory manual testing, lxc, libvirt (3 failures unrelated to apparmor), etc) * test-apparmor.py: PASS * lightdm guest
[Desktop-packages] [Bug 1302374] Re: No sound after upgrade packages and dist
When loading pulseaudio from a terminal, i get: E: [pulseaudio] main.c: pa_pid_file_create() failed. (but it might be due to the missed real sound hardware (#2)) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1302374 Title: No sound after upgrade packages and dist Status in “pulseaudio” package in Ubuntu: Confirmed Bug description: Hi. I upgrade packages in the morning, next upgrade kernel (dist-upgrade) and after restart i have no sound, no tray sound icon. Below history what I'm done: Start-Date: 2014-04-04 08:02:30 Commandline: apt-get upgrade Upgrade: apt:amd64 (0.9.15.4ubuntu2, 0.9.15.4ubuntu3), kerneloops-daemon:amd64 (0.12+git20090217-3ubuntu7, 0.12+git20090217-3ubuntu8), libfontembed1:amd64 (1.0.50-0ubuntu1, 1.0.51-0ubuntu1), libgdiplus:amd64 (2.11+git20131008.9732566-4ubuntu1, 2.11+git20131008.9732566-5ubuntu1), libgail-3-0:amd64 (3.10.7-0ubuntu4, 3.10.7-0ubuntu5), python-samba:amd64 (4.1.3+dfsg-2ubuntu5, 4.1.6+dfsg-1ubuntu1), apt-transport-https:amd64 (0.9.15.4ubuntu2, 0.9.15.4ubuntu3), libindicator3-7:amd64 (12.10.2+14.04.20140304-0ubuntu1, 12.10.2+14.04.20140402-0ubuntu1), libphonon4:amd64 (4.7.1-0ubuntu7, 4.7.1-0ubuntu8), language-pack-pl:amd64 (14.04+20140321, 14.04+20140401), gsettings-ubuntu-schemas:amd64 (0.0.1+14.04.20140224-0ubuntu1, 0.0.1+14.04.20140401-0ubuntu1), phonon:amd64 (4.7.1-0ubuntu7, 4.7.1-0ubuntu8), gir1.2-packagekitglib-1.0:amd64 (0.8.12-1ubuntu4, 0.8.12-1ubuntu5), gir1.2-gtk-3.0:amd64 (3.10.7-0ubuntu4, 3.10.7-0ubuntu5), apt-utils:amd64 (0.9.15.4ubuntu2, 0.9.15.4ubuntu3), ubuntu-minimal:amd64 (1.322, 1.324), plymouth-theme-ubuntu-text:amd64 (0.8.8-0ubuntu15, 0.8.8-0ubuntu16), parted:amd64 (2.3-17, 2.3-18), libgudev-1.0-0:amd64 (204-5ubuntu13, 204-5ubuntu16), python-apt:amd64 (0.9.3.4build1, 0.9.3.5), command-not-found:amd64 (0.3ubuntu10, 0.3ubuntu12), tzdata-java:amd64 (2014a-1, 2014b-1), file:amd64 (5.14-2ubuntu2, 5.14-2ubuntu3), libmagic1:amd64 (5.14-2ubuntu2, 5.14-2ubuntu3), python3-commandnotfound:amd64 (0.3ubuntu10, 0.3ubuntu12), libglib2.0-0:amd64 (2.40.0-1ubuntu1, 2.40.0-2), libapt-inst1.5:amd64 (0.9.15.4ubuntu2, 0.9.15.4ubuntu3), libnss3-1d:amd64 (3.15.4-1ubuntu6, 3.15.4-1ubuntu7), libgtk-3-bin:amd64 (3.10.7-0ubuntu4, 3.10.7-0ubuntu5), libbluetooth3:amd64 (4.101-0ubuntu10, 4.101-0ubuntu11), bluez-cups:amd64 (4.101-0ubuntu10, 4.101-0ubuntu11), plymouth:amd64 (0.8.8-0ubuntu15, 0.8.8-0ubuntu16), libnss3-nssdb:amd64 (3.15.4-1ubuntu6, 3.15.4-1ubuntu7), ubuntu-standard:amd64 (1.322, 1.324), libglib2.0-data:amd64 (2.40.0-1ubuntu1, 2.40.0-2), bluez-alsa:amd64 (4.101-0ubuntu10, 4.101-0ubuntu11), gir1.2-gudev-1.0:amd64 (204-5ubuntu13, 204-5ubuntu16), indicator-application:amd64 (12.10.1+14.04.20140324-0ubuntu1, 12.10.1+14.04.20140402-0ubuntu1), samba-common-bin:amd64 (4.1.3+dfsg-2ubuntu5, 4.1.6+dfsg-1ubuntu1), cups-browsed:amd64 (1.0.50-0ubuntu1, 1.0.51-0ubuntu1), libparted0debian1:amd64 (2.3-17, 2.3-18), python-commandnotfound:amd64 (0.3ubuntu10, 0.3ubuntu12), cups-filters-core-drivers:amd64 (1.0.50-0ubuntu1, 1.0.51-0ubuntu1), language-pack-gnome-en:amd64 (14.04+20140321, 14.04+20140401), xfdesktop4-data:amd64 (4.11.4-1ubuntu2, 4.11.5-0ubuntu1), acpid:amd64 (2.0.21-1ubuntu1, 2.0.21-1ubuntu2), ubuntu-sso-client:amd64 (13.10-0ubuntu4, 13.10-0ubuntu5), command-not-found-data:amd64 (0.3ubuntu10, 0.3ubuntu12), samba-libs:amd64 (4.1.3+dfsg-2ubuntu5, 4.1.6+dfsg-1ubuntu1), libapt-pkg4.12:amd64 (0.9.15.4ubuntu2, 0.9.15.4ubuntu3), python3-apt:amd64 (0.9.3.4build1, 0.9.3.5), libgtk-3-0:amd64 (3.10.7-0ubuntu4, 3.10.7-0ubuntu5), bluez:amd64 (4.101-0ubuntu10, 4.101-0ubuntu11), libnss3:amd64 (3.15.4-1ubuntu6, 3.15.4-1ubuntu7), indicator-sound:amd64 (12.10.2+14.04.20140324.is.12.10.2+14.04.20140320-0ubuntu1, 12.10.2+14.04.20140401-0ubuntu1), apache2-data:amd64 (2.4.7-1ubuntu3, 2.4.7-1ubuntu4), python-smbc:amd64 (1.0.13-0ubuntu6, 1.0.14.1-0ubuntu2), cups-filters:amd64 (1.0.50-0ubuntu1, 1.0.51-0ubuntu1), libplymouth2:amd64 (0.8.8-0ubuntu15, 0.8.8-0ubuntu16), unity-settings-daemon:amd64 (14.04.0+14.04.20140310-0ubuntu2, 14.04.0+14.04.20140402-0ubuntu1), smbclient:amd64 (4.1.3+dfsg-2ubuntu5, 4.1.6+dfsg-1ubuntu1), lightdm:amd64 (1.9.13-0ubuntu1, 1.9.14-0ubuntu1), libgtk-3-common:amd64 (3.10.7-0ubuntu4, 3.10.7-0ubuntu5), language-pack-gnome-pl:amd64 (14.04+20140321, 14.04+20140401), python-ubuntu-sso-client:amd64 (13.10-0ubuntu4, 13.10-0ubuntu5), liblightdm-gobject-1-0:amd64 (1.9.13-0ubuntu1, 1.9.14-0ubuntu1), xfdesktop4:amd64 (4.11.4-1ubuntu2, 4.11.5-0ubuntu1), xserver-xorg-video-sis:amd64 (0.10.7-0ubuntu5, 0.10.7-0ubuntu6), apache2:amd64 (2.4.7-1ubuntu3, 2.4.7-1ubuntu4), tzdata:amd64 (2014a-1, 2014b-1), libglib2.0-bin:amd64 (2.40.0-1ubuntu1, 2.40.0-2), apache2-bin:amd64 (2.4.7-1ubuntu3, 2.4.7-1ubuntu4), libwbclient0:amd64 (4.1.3+dfsg-2ubuntu5, 4.1.6+dfsg-1ubuntu1), linux-libc-dev:amd64 (3.13.0-20.42,
[Desktop-packages] [Bug 1302353] Re: regression: ibus ignores keyboard layout
Here's a hack I learned about in #ibus that gets things working as they should (until the next time the ibus-anthy package is updated, I guess) First, add 'de' to 'keyboard_layouts' in /usr/share/ibus-anthy/setup/anthyprefs.py Second, run /usr/lib/ibus/ibus-setup-anthy and really, really force anthy to use the German layout in Typing Methods - Keyboard layout No hack or workaround is currently known for ibus-mozc or any of the other input engines. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1302353 Title: regression: ibus ignores keyboard layout Status in “ibus” package in Ubuntu: New Status in “unity” package in Ubuntu: New Bug description: The recent update of unity packages introduced a bad regression for ibus users. I assume the fault lies with unity since ibus hasn't been updated for several weeks and my machine was fine until about two days ago around which time some unity updates rolled in. I have a German keyboard layout (QWERTZ not QWERTY as in the US case). I use anthy and mozc for Japanese input. Since two days ago the default layout with the Japanese IME are a US layout throwing me off when blind-typing. To look into the matter, I opened ibus-setup and there are three Input methods listed there: English - English (US), Japanese - Anthy and Japanese -Mozc. German was conspicuously absent . I eventually managed to add a German layout to it and delete the US layout. I then restart ibus with ibus restart only to find the US keyboard layout not only back but it's default again. Argh! In other words, the explicit choice I'm trying to force doesn't stick. There are four keyboard layouts currently defined in System Settings - Text Entry - Input sources to use, none of them have anything to do with a US-layout; de1, de2, anthy and mozc. I cycle through them via Super+Space. Anthy is set to use the system default layout. The regression is that it currently inists on US layout with no way to even override this silly choice. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1302353/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1302374] Re: No sound after upgrade packages and dist
[7.430462] snd_hda_intel :00:1b.0: irq 46 for MSI/MSI-X [7.443450] ppdev: user-space parallel port driver [7.462455] SKU: Nid=0x1d sku_cfg=0x4045e601 [7.462457] SKU: port_connectivity=0x1 [7.462458] SKU: enable_pcbeep=0x0 [7.462458] SKU: check_sum=0x0005 [7.462459] SKU: customization=0x00e6 [7.462460] SKU: external_amp=0x0 [7.462460] SKU: platform_type=0x0 [7.462461] SKU: swap=0x0 [7.462461] SKU: override=0x1 [7.462867] autoconfig: line_outs=4 (0x14/0x15/0x16/0x17/0x0) type:line [7.462868]speaker_outs=0 (0x0/0x0/0x0/0x0/0x0) [7.462869]hp_outs=1 (0x1b/0x0/0x0/0x0/0x0) [7.462870]mono: mono_out=0x0 [7.462870]dig-out=0x11/0x0 [7.462871]inputs: [7.462872] Front Mic=0x19 [7.462873] Rear Mic=0x18 [7.462874] Line=0x1a [7.462875] realtek: No valid SSID, checking pincfg 0x4045e601 for NID 0x1d [7.462876] realtek: Enabling init ASM_ID=0xe601 CODEC_ID=10ec0892 [7.474069] input: HDA Intel PCH Front Headphone as /devices/pci:00/:00:1b.0/sound/card0/input11 [7.474144] input: HDA Intel PCH Line Out Side as /devices/pci:00/:00:1b.0/sound/card0/input10 [7.474209] input: HDA Intel PCH Line Out CLFE as /devices/pci:00/:00:1b.0/sound/card0/input9 [7.474269] input: HDA Intel PCH Line Out Surround as /devices/pci:00/:00:1b.0/sound/card0/input8 [7.474324] input: HDA Intel PCH Line Out Front as /devices/pci:00/:00:1b.0/sound/card0/input7 [7.474378] input: HDA Intel PCH Line as /devices/pci:00/:00:1b.0/sound/card0/input6 [7.474422] input: HDA Intel PCH Rear Mic as /devices/pci:00/:00:1b.0/sound/card0/input5 [7.474452] input: HDA Intel PCH Front Mic as /devices/pci:00/:00:1b.0/sound/card0/input4 [7.477595] systemd-udevd[412]: failed to execute '/usr/sbin/alsactl' '/usr/sbin/alsactl -E HOME=/var/run/alsa restore 0': No such file or directory [7.655896] set resolution quirk: cval-res = 384 [7.656004] usbcore: registered new interface driver snd-usb-audio -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1302374 Title: No sound after upgrade packages and dist Status in “pulseaudio” package in Ubuntu: Confirmed Bug description: Hi. I upgrade packages in the morning, next upgrade kernel (dist-upgrade) and after restart i have no sound, no tray sound icon. Below history what I'm done: Start-Date: 2014-04-04 08:02:30 Commandline: apt-get upgrade Upgrade: apt:amd64 (0.9.15.4ubuntu2, 0.9.15.4ubuntu3), kerneloops-daemon:amd64 (0.12+git20090217-3ubuntu7, 0.12+git20090217-3ubuntu8), libfontembed1:amd64 (1.0.50-0ubuntu1, 1.0.51-0ubuntu1), libgdiplus:amd64 (2.11+git20131008.9732566-4ubuntu1, 2.11+git20131008.9732566-5ubuntu1), libgail-3-0:amd64 (3.10.7-0ubuntu4, 3.10.7-0ubuntu5), python-samba:amd64 (4.1.3+dfsg-2ubuntu5, 4.1.6+dfsg-1ubuntu1), apt-transport-https:amd64 (0.9.15.4ubuntu2, 0.9.15.4ubuntu3), libindicator3-7:amd64 (12.10.2+14.04.20140304-0ubuntu1, 12.10.2+14.04.20140402-0ubuntu1), libphonon4:amd64 (4.7.1-0ubuntu7, 4.7.1-0ubuntu8), language-pack-pl:amd64 (14.04+20140321, 14.04+20140401), gsettings-ubuntu-schemas:amd64 (0.0.1+14.04.20140224-0ubuntu1, 0.0.1+14.04.20140401-0ubuntu1), phonon:amd64 (4.7.1-0ubuntu7, 4.7.1-0ubuntu8), gir1.2-packagekitglib-1.0:amd64 (0.8.12-1ubuntu4, 0.8.12-1ubuntu5), gir1.2-gtk-3.0:amd64 (3.10.7-0ubuntu4, 3.10.7-0ubuntu5), apt-utils:amd64 (0.9.15.4ubuntu2, 0.9.15.4ubuntu3), ubuntu-minimal:amd64 (1.322, 1.324), plymouth-theme-ubuntu-text:amd64 (0.8.8-0ubuntu15, 0.8.8-0ubuntu16), parted:amd64 (2.3-17, 2.3-18), libgudev-1.0-0:amd64 (204-5ubuntu13, 204-5ubuntu16), python-apt:amd64 (0.9.3.4build1, 0.9.3.5), command-not-found:amd64 (0.3ubuntu10, 0.3ubuntu12), tzdata-java:amd64 (2014a-1, 2014b-1), file:amd64 (5.14-2ubuntu2, 5.14-2ubuntu3), libmagic1:amd64 (5.14-2ubuntu2, 5.14-2ubuntu3), python3-commandnotfound:amd64 (0.3ubuntu10, 0.3ubuntu12), libglib2.0-0:amd64 (2.40.0-1ubuntu1, 2.40.0-2), libapt-inst1.5:amd64 (0.9.15.4ubuntu2, 0.9.15.4ubuntu3), libnss3-1d:amd64 (3.15.4-1ubuntu6, 3.15.4-1ubuntu7), libgtk-3-bin:amd64 (3.10.7-0ubuntu4, 3.10.7-0ubuntu5), libbluetooth3:amd64 (4.101-0ubuntu10, 4.101-0ubuntu11), bluez-cups:amd64 (4.101-0ubuntu10, 4.101-0ubuntu11), plymouth:amd64 (0.8.8-0ubuntu15, 0.8.8-0ubuntu16), libnss3-nssdb:amd64 (3.15.4-1ubuntu6, 3.15.4-1ubuntu7), ubuntu-standard:amd64 (1.322, 1.324), libglib2.0-data:amd64 (2.40.0-1ubuntu1, 2.40.0-2), bluez-alsa:amd64 (4.101-0ubuntu10, 4.101-0ubuntu11), gir1.2-gudev-1.0:amd64 (204-5ubuntu13, 204-5ubuntu16), indicator-application:amd64 (12.10.1+14.04.20140324-0ubuntu1, 12.10.1+14.04.20140402-0ubuntu1), samba-common-bin:amd64 (4.1.3+dfsg-2ubuntu5, 4.1.6+dfsg-1ubuntu1), cups-browsed:amd64 (1.0.50-0ubuntu1, 1.0.51-0ubuntu1), libparted0debian1:amd64 (2.3-17,
[Desktop-packages] [Bug 1302386] [NEW] NM-APPLET does not allow to connect to wifi
Public bug reported: after updates today in 14.04 I reboot the system. Then I tried connected to local wifi network It gave an error saying you are not authorised to use the applet. edit connection is not enabled. all dial up / mobile network configured previously are not shown. network tab in system setting is also not allowing to connect to any network. mobile network creation also failed saying user not allowed to access this applet. tried to run nm-applet as super user but it did not work. ** Affects: network-manager-applet (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-applet in Ubuntu. https://bugs.launchpad.net/bugs/1302386 Title: NM-APPLET does not allow to connect to wifi Status in “network-manager-applet” package in Ubuntu: New Bug description: after updates today in 14.04 I reboot the system. Then I tried connected to local wifi network It gave an error saying you are not authorised to use the applet. edit connection is not enabled. all dial up / mobile network configured previously are not shown. network tab in system setting is also not allowing to connect to any network. mobile network creation also failed saying user not allowed to access this applet. tried to run nm-applet as super user but it did not work. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1302386/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1302105] Re: Highlight glitch while scrolling the services list
** Bug watch added: GNOME Bug Tracker #727585 https://bugzilla.gnome.org/show_bug.cgi?id=727585 ** Also affects: gtk via https://bugzilla.gnome.org/show_bug.cgi?id=727585 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center-signon in Ubuntu. https://bugs.launchpad.net/bugs/1302105 Title: Highlight glitch while scrolling the services list Status in Online Accounts: GNOME Control Center: Confirmed Status in GTK+ GUI Toolkit: Unknown Status in “gnome-control-center-signon” package in Ubuntu: Confirmed Bug description: On the Online Accounts panel, if I scroll the list of services (on the right side) the highlight is repeated. That is, say I have the mouse over Twitter, when I scroll the list with the mouse wheel the highlighting is drawn over Twitter and newly hovered items. I've added a screenshot. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity-control-center-signon 0.1.7~+14.04.20140211.2-0ubuntu4 ProcVersionSignature: Ubuntu 3.13.0-20.42-generic 3.13.7 Uname: Linux 3.13.0-20-generic x86_64 ApportVersion: 2.14-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Thu Apr 3 14:19:56 2014 InstallationDate: Installed on 2014-03-16 (18 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140316) SourcePackage: gnome-control-center-signon UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center-signon/+bug/1302105/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1301839] Re: AMD Radeon HD 8670A/8670M/8690M[1002:6660] Low-graphic mode with Trusty dailylive
Po-Hsu: please boot without the nomodeset parameter and upload your /var/log/gpu-manager.log -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-ati in Ubuntu. https://bugs.launchpad.net/bugs/1301839 Title: AMD Radeon HD 8670A/8670M/8690M[1002:6660] Low-graphic mode with Trusty dailylive Status in “xserver-xorg-video-ati” package in Ubuntu: New Status in “xserver-xorg-video-intel” package in Ubuntu: New Bug description: CID: 201305-13624 This system cannot boot to desktop by Try Ubuntu option with liveUSB, it will ask you to run on low-graphic mode. Steps: 1. Try to boot to the desktop with 14.04 dailylive (2-Apr-2014) Expected result * Desktop works fine Actual result: * You will be ask to run on low-graphic mode, or you will need to add nomodeset parameter into grub to boot normally. This bug exists in 12.04.4, and it's fixed in Trusty dailylive 11-Mar-2014 07:51, also the Trusty beta 2 image, but it's now broken again. You can refer to bug 1290745 0a:00.0 Display controller [0380]: Advanced Micro Devices, Inc. [AMD/ATI] Sun XT [Radeon HD 8670A/8670M/8690M] [1002:6660] ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xserver-xorg-video-radeon 1:7.3.0-1ubuntu3 ProcVersionSignature: Ubuntu 3.13.0-20.42-generic 3.13.7 Uname: Linux 3.13.0-20-generic x86_64 .tmp.unity.support.test.1: ApportVersion: 2.14-0ubuntu1 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: Thu Apr 3 05:44:12 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: fwts-efi-runtime-dkms, 14.03.01, 3.13.0-20-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:2162] Subsystem: Hewlett-Packard Company Device [103c:2162] InstallationDate: Installed on 2014-04-03 (0 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Daily amd64 (20140401) MachineType: Hewlett-Packard HP Pavilion TS 14 Notebook PC ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-20-generic root=UUID=8fdb7584-0c55-43ae-923f-b24b1286a592 ro rootdelay=60 quiet splash nomodeset initcall_debug Renderer: Software SourcePackage: xserver-xorg-video-ati UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/27/2013 dmi.bios.vendor: Insyde dmi.bios.version: B.09 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 2162 dmi.board.vendor: Hewlett-Packard dmi.board.version: 29.0A dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrB.09:bd05/27/2013:svnHewlett-Packard:pnHPPavilionTS14NotebookPC:pvr089C101630100:rvnHewlett-Packard:rn2162:rvr29.0A:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.name: HP Pavilion TS 14 Notebook PC dmi.product.version: 089C101630100 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.11+14.04.20140328-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-1ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.15.0-1ubuntu7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Thu Apr 3 05:36:25 2014 xserver.configfile: default xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.15.0-1ubuntu7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/1301839/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1302383] Re: Selecting Reboot leads to a Log out question
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-session (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1302383 Title: Selecting Reboot leads to a Log out question Status in “gnome-session” package in Ubuntu: Confirmed Bug description: Steps to reproduce: Execute gnome-session-quit --reboot and notice a Log out dialog. Expected a Reboot dialog. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: gnome-session-bin 3.9.90-0ubuntu12 ProcVersionSignature: Ubuntu 3.13.0-22.44-generic 3.13.8 Uname: Linux 3.13.0-22-generic x86_64 ApportVersion: 2.14-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Fri Apr 4 09:24:18 2014 InstallationDate: Installed on 2013-11-04 (150 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20131103) ProcEnviron: LANGUAGE=sv TERM=xterm PATH=(custom, no user) LANG=sv_SE.UTF-8 SHELL=/bin/bash SourcePackage: gnome-session UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1302383/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1302353] Re: regression: ibus ignores keyboard layout
Rolf-san, Probably, #1298740 go some way towards? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1302353 Title: regression: ibus ignores keyboard layout Status in “ibus” package in Ubuntu: New Status in “unity” package in Ubuntu: New Bug description: The recent update of unity packages introduced a bad regression for ibus users. I assume the fault lies with unity since ibus hasn't been updated for several weeks and my machine was fine until about two days ago around which time some unity updates rolled in. I have a German keyboard layout (QWERTZ not QWERTY as in the US case). I use anthy and mozc for Japanese input. Since two days ago the default layout with the Japanese IME are a US layout throwing me off when blind-typing. To look into the matter, I opened ibus-setup and there are three Input methods listed there: English - English (US), Japanese - Anthy and Japanese -Mozc. German was conspicuously absent . I eventually managed to add a German layout to it and delete the US layout. I then restart ibus with ibus restart only to find the US keyboard layout not only back but it's default again. Argh! In other words, the explicit choice I'm trying to force doesn't stick. There are four keyboard layouts currently defined in System Settings - Text Entry - Input sources to use, none of them have anything to do with a US-layout; de1, de2, anthy and mozc. I cycle through them via Super+Space. Anthy is set to use the system default layout. The regression is that it currently inists on US layout with no way to even override this silly choice. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1302353/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1301839] Re: AMD Radeon HD 8670A/8670M/8690M[1002:6660] Low-graphic mode with Trusty dailylive
BTW, this seems to me like a problem with the intel driver. ** Also affects: xserver-xorg-video-intel (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-ati in Ubuntu. https://bugs.launchpad.net/bugs/1301839 Title: AMD Radeon HD 8670A/8670M/8690M[1002:6660] Low-graphic mode with Trusty dailylive Status in “xserver-xorg-video-ati” package in Ubuntu: New Status in “xserver-xorg-video-intel” package in Ubuntu: New Bug description: CID: 201305-13624 This system cannot boot to desktop by Try Ubuntu option with liveUSB, it will ask you to run on low-graphic mode. Steps: 1. Try to boot to the desktop with 14.04 dailylive (2-Apr-2014) Expected result * Desktop works fine Actual result: * You will be ask to run on low-graphic mode, or you will need to add nomodeset parameter into grub to boot normally. This bug exists in 12.04.4, and it's fixed in Trusty dailylive 11-Mar-2014 07:51, also the Trusty beta 2 image, but it's now broken again. You can refer to bug 1290745 0a:00.0 Display controller [0380]: Advanced Micro Devices, Inc. [AMD/ATI] Sun XT [Radeon HD 8670A/8670M/8690M] [1002:6660] ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xserver-xorg-video-radeon 1:7.3.0-1ubuntu3 ProcVersionSignature: Ubuntu 3.13.0-20.42-generic 3.13.7 Uname: Linux 3.13.0-20-generic x86_64 .tmp.unity.support.test.1: ApportVersion: 2.14-0ubuntu1 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: Thu Apr 3 05:44:12 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: fwts-efi-runtime-dkms, 14.03.01, 3.13.0-20-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:2162] Subsystem: Hewlett-Packard Company Device [103c:2162] InstallationDate: Installed on 2014-04-03 (0 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Daily amd64 (20140401) MachineType: Hewlett-Packard HP Pavilion TS 14 Notebook PC ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-20-generic root=UUID=8fdb7584-0c55-43ae-923f-b24b1286a592 ro rootdelay=60 quiet splash nomodeset initcall_debug Renderer: Software SourcePackage: xserver-xorg-video-ati UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/27/2013 dmi.bios.vendor: Insyde dmi.bios.version: B.09 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 2162 dmi.board.vendor: Hewlett-Packard dmi.board.version: 29.0A dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrB.09:bd05/27/2013:svnHewlett-Packard:pnHPPavilionTS14NotebookPC:pvr089C101630100:rvnHewlett-Packard:rn2162:rvr29.0A:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.name: HP Pavilion TS 14 Notebook PC dmi.product.version: 089C101630100 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.11+14.04.20140328-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-1ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.15.0-1ubuntu7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Thu Apr 3 05:36:25 2014 xserver.configfile: default xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.15.0-1ubuntu7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/1301839/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1285179] Re: pulseaudio does not remember the audio level for usb audio devices
** Changed in: pulseaudio (Ubuntu) Status: Incomplete = In Progress -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1285179 Title: pulseaudio does not remember the audio level for usb audio devices Status in “pulseaudio” package in Ubuntu: In Progress Bug description: When I plug in my Audioengine D1, output is switched to it, but the volume level is set to 100%. I then have to open the sound settings, switch the output device to it before I can adjust the volume level. Once the level has been adjusted, if I unplug the device and then plug it back it, the volume will be reset to 100% for it and I'll have to repeat the steps all over again to adjust it. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: pulseaudio 1:4.0-0ubuntu7 ProcVersionSignature: Ubuntu 3.13.0-12.32-generic 3.13.4 Uname: Linux 3.13.0-12-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.13.2-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: valdiyen 3325 F pulseaudio /dev/snd/pcmC1D0p: valdiyen 3325 F...m pulseaudio /dev/snd/controlC2: valdiyen 3325 F pulseaudio /dev/snd/controlC0: valdiyen 3325 F pulseaudio CurrentDesktop: Unity Date: Wed Feb 26 09:00:53 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2014-02-14 (11 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140211) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/29/2013 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP111.88Z.0138.B03.1310291227 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-189A3D4F975D5FFC dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro11,1 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-189A3D4F975D5FFC dmi.modalias: dmi:bvnAppleInc.:bvrMBP111.88Z.0138.B03.1310291227:bd10/29/2013:svnAppleInc.:pnMacBookPro11,1:pvr1.0:rvnAppleInc.:rnMac-189A3D4F975D5FFC:rvrMacBookPro11,1:cvnAppleInc.:ct10:cvrMac-189A3D4F975D5FFC: dmi.product.name: MacBookPro11,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1285179/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1301839] Re: AMD Radeon HD 8670A/8670M/8690M[1002:6660] Low-graphic mode with Trusty dailylive
and please also attach the output of dmesg without the nomodeset parameter -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu. https://bugs.launchpad.net/bugs/1301839 Title: AMD Radeon HD 8670A/8670M/8690M[1002:6660] Low-graphic mode with Trusty dailylive Status in “xserver-xorg-video-ati” package in Ubuntu: New Status in “xserver-xorg-video-intel” package in Ubuntu: New Bug description: CID: 201305-13624 This system cannot boot to desktop by Try Ubuntu option with liveUSB, it will ask you to run on low-graphic mode. Steps: 1. Try to boot to the desktop with 14.04 dailylive (2-Apr-2014) Expected result * Desktop works fine Actual result: * You will be ask to run on low-graphic mode, or you will need to add nomodeset parameter into grub to boot normally. This bug exists in 12.04.4, and it's fixed in Trusty dailylive 11-Mar-2014 07:51, also the Trusty beta 2 image, but it's now broken again. You can refer to bug 1290745 0a:00.0 Display controller [0380]: Advanced Micro Devices, Inc. [AMD/ATI] Sun XT [Radeon HD 8670A/8670M/8690M] [1002:6660] ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xserver-xorg-video-radeon 1:7.3.0-1ubuntu3 ProcVersionSignature: Ubuntu 3.13.0-20.42-generic 3.13.7 Uname: Linux 3.13.0-20-generic x86_64 .tmp.unity.support.test.1: ApportVersion: 2.14-0ubuntu1 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: Thu Apr 3 05:44:12 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: fwts-efi-runtime-dkms, 14.03.01, 3.13.0-20-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:2162] Subsystem: Hewlett-Packard Company Device [103c:2162] InstallationDate: Installed on 2014-04-03 (0 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Daily amd64 (20140401) MachineType: Hewlett-Packard HP Pavilion TS 14 Notebook PC ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-20-generic root=UUID=8fdb7584-0c55-43ae-923f-b24b1286a592 ro rootdelay=60 quiet splash nomodeset initcall_debug Renderer: Software SourcePackage: xserver-xorg-video-ati UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/27/2013 dmi.bios.vendor: Insyde dmi.bios.version: B.09 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 2162 dmi.board.vendor: Hewlett-Packard dmi.board.version: 29.0A dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrB.09:bd05/27/2013:svnHewlett-Packard:pnHPPavilionTS14NotebookPC:pvr089C101630100:rvnHewlett-Packard:rn2162:rvr29.0A:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.name: HP Pavilion TS 14 Notebook PC dmi.product.version: 089C101630100 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.11+14.04.20140328-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-1ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.15.0-1ubuntu7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Thu Apr 3 05:36:25 2014 xserver.configfile: default xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.15.0-1ubuntu7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/1301839/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1302348] Re: after today's Trusty updates/restart, NM will not connect to wifi
It could also be related to this: https://www.kubuntuforums.net/showthread.php?65082-systemd-update-screwed-up-policy-kit-network-manager-and-muon-qapt since I was also unable to mount any external drives (ntfs or otherwise) or restart/shutdown the pc. Everything (wireless and permissions) seems to have fixed after I installed the `cgmanager` and `qdbus-qt5` packages. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1302348 Title: after today's Trusty updates/restart, NM will not connect to wifi Status in “network-manager” package in Ubuntu: New Bug description: I see all the wireless signals in the neighborhood, but the connect button does not connect my laptop to the internet. Also, history seems lost, as it reports that my wifi has never been used, when it was in use a few minutes before. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: network-manager 0.9.8.8-0ubuntu5 ProcVersionSignature: Ubuntu 3.13.0-22.44-generic 3.13.8 Uname: Linux 3.13.0-22-generic x86_64 ApportVersion: 2.14-0ubuntu1 Architecture: amd64 CurrentDesktop: KDE Date: Thu Apr 3 22:43:11 2014 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2013-06-18 (289 days ago) InstallationMedia: Kubuntu 13.04 Raring Ringtail - Release amd64 (20130424) IpRoute: default via 192.168.15.1 dev eth0 proto static 192.168.15.0/24 dev eth0 proto kernel scope link src 192.168.15.3 metric 1 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: network-manager UpgradeStatus: Upgraded to trusty on 2014-03-04 (30 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1302348/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1267150] Re: Broken colors after suspend/resume (ATI Mobility Radeon HD 2600)
I have exactly the same problem as Redge. Let me know if I can provide any further information about the bug. ** Changed in: xorg (Ubuntu) Status: Expired = Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1267150 Title: Broken colors after suspend/resume (ATI Mobility Radeon HD 2600) Status in “xorg” package in Ubuntu: Confirmed Bug description: In continuation on https://bugs.launchpad.net/xserver-xorg-driver- ati/+bug/510001/ After suspending and then resuming on my iMac, I get a weird distortion of colors that renders the screen unreadable. For an example see http://askubuntu.com/questions/310161/broken-graphics- after-suspend-resume I have had this issue ever since changing from the closed source fglrx driver to the open source driver in 12.04, and it's still present in 13.10. I've also reported the issue with the xf86-video-ati maintainers, but I haven't been able to solve the problem yet. https://bugs.freedesktop.org/show_bug.cgi?id=70735 My version of package xserver-xorg-video-ati is 1:7.2.0-0ubuntu10 ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: xorg 1:7.7+1ubuntu6 ProcVersionSignature: Ubuntu 3.11.0-14.21-generic 3.11.7 Uname: Linux 3.11.0-14-generic x86_64 NonfreeKernelModules: wl .tmp.unity.support.test.0: ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Wed Jan 8 14:23:09 2014 DistUpgraded: Fresh install DistroCodename: saucy DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.141+bdcom, 3.11.0-12-generic, x86_64: installed bcmwl, 6.30.223.141+bdcom, 3.11.0-13-generic, x86_64: installed bcmwl, 6.30.223.141+bdcom, 3.11.0-14-generic, x86_64: installed virtualbox, 4.2.16, 3.11.0-14-generic, x86_64: installed DpkgLog: ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] RV630/M76 [Mobility Radeon HD 2600 XT/2700] [1002:9583] (prog-if 00 [VGA controller]) Subsystem: Apple Inc. iMac 7,1 [106b:0083] InstallationDate: Installed on 2013-10-21 (78 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) MachineType: Apple Inc. iMac7,1 MarkForUpload: True ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-14-generic.efi.signed root=UUID=c4671189-da5c-40fc-a962-4702d5aa0767 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/05/08 dmi.bios.vendor: Apple Inc. dmi.bios.version: IM71.88Z.007A.B03.0803051705 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Mac-F42386C8 dmi.board.vendor: Apple Inc. dmi.board.version: PVT dmi.chassis.asset.tag: Asset Tag# dmi.chassis.type: 13 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-F42386C8 dmi.modalias: dmi:bvnAppleInc.:bvrIM71.88Z.007A.B03.0803051705:bd03/05/08:svnAppleInc.:pniMac7,1:pvr1.0:rvnAppleInc.:rnMac-F42386C8:rvrPVT:cvnAppleInc.:ct13:cvrMac-F42386C8: dmi.product.name: iMac7,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. version.compiz: compiz 1:0.9.10+13.10.20131011-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.46-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.2.1-1ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.2.1-1ubuntu3 version.xserver-xorg-core: xserver-xorg-core 2:1.14.3-3ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu3.1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.2.0-0ubuntu10 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.904-0ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.9-2ubuntu1 xserver.bootTime: Wed Jan 8 11:41:27 2014 xserver.configfile: default xserver.errors: evdev: HID 05ac:1000: Unable to open evdev device /dev/input/event3. PreInit returned 2 for HID 05ac:1000 xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.14.3-3ubuntu2 xserver.video_driver: radeon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1267150/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1302353] Re: regression: ibus ignores keyboard layout
OK, here's the workaround for mozc. Replace default by de in the layout key in /usr/share/ibus/component/mozc.xml. Just like the change for anthy, this will be probably be overridden the next time you update the ibus-mozc package. And in both cases you need to restart ibus or your computer for the change to take effect. Many thanks to Fujiwarat from #ibus who helped me figure all this out. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1302353 Title: regression: ibus ignores keyboard layout Status in “ibus” package in Ubuntu: New Status in “unity” package in Ubuntu: New Bug description: The recent update of unity packages introduced a bad regression for ibus users. I assume the fault lies with unity since ibus hasn't been updated for several weeks and my machine was fine until about two days ago around which time some unity updates rolled in. I have a German keyboard layout (QWERTZ not QWERTY as in the US case). I use anthy and mozc for Japanese input. Since two days ago the default layout with the Japanese IME are a US layout throwing me off when blind-typing. To look into the matter, I opened ibus-setup and there are three Input methods listed there: English - English (US), Japanese - Anthy and Japanese -Mozc. German was conspicuously absent . I eventually managed to add a German layout to it and delete the US layout. I then restart ibus with ibus restart only to find the US keyboard layout not only back but it's default again. Argh! In other words, the explicit choice I'm trying to force doesn't stick. There are four keyboard layouts currently defined in System Settings - Text Entry - Input sources to use, none of them have anything to do with a US-layout; de1, de2, anthy and mozc. I cycle through them via Super+Space. Anthy is set to use the system default layout. The regression is that it currently inists on US layout with no way to even override this silly choice. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1302353/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1302393] [NEW] gvfsd-metadata freez and load IO
Public bug reported: Sometimes in a week I see blinking IO-indicator on my PC. Look iotop and see that gvfsd-metadata write something on disk while jbd2 load IO up to 100% Earlier I wait for some minutes than use killall gvfsd-metada. And now use killall immediately after see that my PC start work slowly and check iotop. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: gvfs 1.19.90-1ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-20.42-generic 3.13.7 Uname: Linux 3.13.0-20-generic x86_64 ApportVersion: 2.14-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Fri Apr 4 17:33:39 2014 InstallationDate: Installed on 2014-01-20 (74 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140115) SourcePackage: gvfs UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gvfs (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty ** Attachment added: terminal's screenshot of iotop https://bugs.launchpad.net/bugs/1302393/+attachment/4064889/+files/gvfs-metadata.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1302393 Title: gvfsd-metadata freez and load IO Status in “gvfs” package in Ubuntu: New Bug description: Sometimes in a week I see blinking IO-indicator on my PC. Look iotop and see that gvfsd-metadata write something on disk while jbd2 load IO up to 100% Earlier I wait for some minutes than use killall gvfsd-metada. And now use killall immediately after see that my PC start work slowly and check iotop. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: gvfs 1.19.90-1ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-20.42-generic 3.13.7 Uname: Linux 3.13.0-20-generic x86_64 ApportVersion: 2.14-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Fri Apr 4 17:33:39 2014 InstallationDate: Installed on 2014-01-20 (74 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140115) SourcePackage: gvfs UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1302393/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1301625] Re: Guest session emits AppArmor denials about reading /proc/PID/stat
This bug was fixed in the package lightdm - 1.9.14-0ubuntu2
---
lightdm (1.9.14-0ubuntu2) trusty; urgency=medium
* debian/patches/06_guest_signal_and_ptrace_aa_rules.patch: Grant
permission for guest session processes to signal and ptrace each
other (LP: #1298611)
* debian/patches/07_guest_proc_pid_stat_aa_rule.patch: Grant permission for
guest session processes to read /proc/PID/stat. This prevents AppArmor
denial messages caused by bamfdaemon and common utilities such as ps and
killall. (LP: #1301625)
-- Tyler Hicks tyhi...@canonical.com Thu, 03 Apr 2014 02:48:51 -0500
** Changed in: lightdm (Ubuntu)
Status: In Progress = Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1301625
Title:
Guest session emits AppArmor denials about reading /proc/PID/stat
Status in “lightdm” package in Ubuntu:
Fix Released
Bug description:
When the guest session launches, bamfdaemon triggers denials on
reading /proc/PID/stat:
apparmor=DENIED operation=open profile=/usr/lib/lightdm/lightdm-
guest-session name=/proc/863/stat pid=1816 comm=bamfdaemon
requested_mask=r denied_mask=r fsuid=117 ouid=0
and common utilities, such as ps and killall, trigger the same types
of denials:
apparmor=DENIED operation=open
profile=/usr/lib/lightdm/lightdm-guest-session name=/proc/11/stat pid=2827
comm=ps requested_mask=r denied_mask=r fsuid=117 ouid=0
apparmor=DENIED operation=open
profile=/usr/lib/lightdm/lightdm-guest-session name=/proc/12/stat pid=2813
comm=killall requested_mask=r denied_mask=r fsuid=117 ouid=0
We already grant some read permissions on /proc/ PID/*:
owner @{PROC}/** rm,
# needed for gnome-keyring-daemon
@{PROC}/*/status r,
but non-owned /proc/PID/stat files are not covered.
We should either grant the permission to read the files or quiet the
denials, as they can generate quite a few log entries. Since we
already grant read permissions on /proc/PID/status, it seems like
adding read permissions on /proc/PID/stat is appropriate.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1301625/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1298611] Re: [FFe] apparmor signal and ptrace mediation
This bug was fixed in the package lightdm - 1.9.14-0ubuntu2 --- lightdm (1.9.14-0ubuntu2) trusty; urgency=medium * debian/patches/06_guest_signal_and_ptrace_aa_rules.patch: Grant permission for guest session processes to signal and ptrace each other (LP: #1298611) * debian/patches/07_guest_proc_pid_stat_aa_rule.patch: Grant permission for guest session processes to read /proc/PID/stat. This prevents AppArmor denial messages caused by bamfdaemon and common utilities such as ps and killall. (LP: #1301625) -- Tyler Hicks tyhi...@canonical.com Thu, 03 Apr 2014 02:48:51 -0500 ** Changed in: lightdm (Ubuntu) Status: New = Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1298611 Title: [FFe] apparmor signal and ptrace mediation Status in “apparmor” package in Ubuntu: Confirmed Status in “apparmor-easyprof-ubuntu” package in Ubuntu: New Status in “libvirt” package in Ubuntu: New Status in “lightdm” package in Ubuntu: Fix Released Status in “linux” package in Ubuntu: Fix Released Status in “lxc” package in Ubuntu: New Bug description: Background: kernel and apparmor userspace updates to support signal and ptrace mediation. These packages are listed in one bug because they are related, but the FFes may be granted and the uploads may happen at different times. = linux = Summary: This feature freeze exception is requested for signal and ptrace mediation via apparmor in the kernel. When used with a compatible apparmor userspace, signals and ptrace rules are supported. When used without a compatible apparmor userspace (eg, on a precise system with a trusty backport kernel), signal and ptrace mediation is not enforced (ie, you can use this kernel with an old userspace without any issues). The fine grained mediation of signals and ptraces also incorporates improved versioning support that allows this kernel to better support older and newer userspaces. This allows for this version of the kernel to work as a backport kernel unmodified (currently a patch and config are used to provide backport kernels). The kernel patch is available at git://kernel.ubuntu.com/jj/ubuntu-trusty.git in the trusty-alpha6 branch apparmor-alpha6-sync Testing: * 12.04 system with backported kernel: DONE * test-apparmor.py: PASS (runs extensive tests (upstream and distro)) * exploratory manual testing: PASS (networking, aa-enforce with firefox, firefox works, apparmor blocks access, etc) * aa-status: PASS * lxc: PASS (containers can be created, started, shutdown) * libvirt: PASS (VMs started via openstack, and test-libvirt.py from QRT passes all tests) * 14.04 system (non-Touch) with current apparmor userspace: DONE (relevant parts of https://wiki.ubuntu.com/Process/Merges/TestPlans/AppArmor) * test-apparmor.py: PASS (runs extensive tests (upstream and distro)) * exploratory manual testing: PASS (networking, aa-enforce with firefox, firefox works, apparmor blocks access, etc) * aa-status: PASS * lxc: PASS (containers can be created, started, shutdown) * libvirt: PASS (QRT/script/test-libvirt.py (though there are 3 failures unrelated to apparmor)) * click-apparmor QRT touch image tests: PASS * apparmor-easyprof-ubuntu QRT touch image tests: PASS * 14.04 system (non-Touch) with updated apparmor userspace capable of supporting signal and ptrace mediation: DONE (relevant parts of https://wiki.ubuntu.com/Process/Merges/TestPlans/AppArmor. Note: this is marked 'done' from the kernel perspective-- the apparmor userspace upload is being prepared and tests assume userspace is using latest patches on the list) * test-apparmor.py: PASS (runs extensive tests (upstream and distro)) * exploratory manual testing: PASS (networking, aa-enforce with firefox, firefox works, apparmor blocks access, etc) * aa-status: PASS * lxc: PASS (containers can be created, started, shutdown) * libvirt: PASS (QRT/script/test-libvirt.py (though there are 3 failures unrelated to apparmor)) * click-apparmor QRT touch image tests: PASS * apparmor-easyprof-ubuntu QRT touch image tests: PASS Justification: This feature is required to support comprehensive application confinement on Ubuntu Touch. This feature adds a significant security benefit to libvirt's qemu guest isolation which is fundamental to Ubuntu on Server/Cloud. This feature also adds a welcome improvement to administrators wishing to further protect their systems. = apparmor userspace = Summary: This feature freeze exception is requested for signal and ptrace mediation for apparmor userspace. When used with a compatible kernel, signals and ptrace rules are supported. When used without a compatible kernel (eg, on Ubuntu Touch for a few weeks or with upstream kernels), signal and ptrace rules are skipped (ie,
[Desktop-packages] [Bug 1302353] Re: regression: ibus ignores keyboard layout
Yoshida-san, thank you. That's spot on! This regression was introduced by http://paste.debian.net/91595/ unity-settings-daemon (14.04.0+14.04.20140402-0ubuntu1) trusty; urgency=low [...] [ William Hua ] * Treat IBus engines with 'default' layouts as 'us'. (LP: #1298740) -- Ubuntu daily release ps-jenk...@lists.canonical.com Wed, 02 Apr 2014 11:06:42 + ** Changed in: ibus (Ubuntu) Status: New = Incomplete ** Package changed: unity (Ubuntu) = unity-settings-daemon (Ubuntu) ** Changed in: unity-settings-daemon (Ubuntu) Importance: Undecided = High ** Changed in: unity-settings-daemon (Ubuntu) Status: New = Triaged ** Changed in: unity-settings-daemon (Ubuntu) Milestone: None = ubuntu-14.04 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ibus in Ubuntu. Matching subscriptions: dp-unity https://bugs.launchpad.net/bugs/1302353 Title: regression: ibus ignores keyboard layout Status in “ibus” package in Ubuntu: Incomplete Status in “unity-settings-daemon” package in Ubuntu: Triaged Bug description: The recent update of unity packages introduced a bad regression for ibus users. I assume the fault lies with unity since ibus hasn't been updated for several weeks and my machine was fine until about two days ago around which time some unity updates rolled in. I have a German keyboard layout (QWERTZ not QWERTY as in the US case). I use anthy and mozc for Japanese input. Since two days ago the default layout with the Japanese IME are a US layout throwing me off when blind-typing. To look into the matter, I opened ibus-setup and there are three Input methods listed there: English - English (US), Japanese - Anthy and Japanese -Mozc. German was conspicuously absent . I eventually managed to add a German layout to it and delete the US layout. I then restart ibus with ibus restart only to find the US keyboard layout not only back but it's default again. Argh! In other words, the explicit choice I'm trying to force doesn't stick. There are four keyboard layouts currently defined in System Settings - Text Entry - Input sources to use, none of them have anything to do with a US-layout; de1, de2, anthy and mozc. I cycle through them via Super+Space. Anthy is set to use the system default layout. The regression is that it currently inists on US layout with no way to even override this silly choice. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1302353/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1298740] Re: unity-settings-daemon warns when IBus engine layout is default
Yes, this is a really stupid idea and a severe regression - bug 1302353 [ William Hua ] * Treat IBus engines with 'default' layouts as 'us'. (LP: #1298740) I'm really surprised how this wouldn't strike anyone as boneheaded immediately. ** Changed in: unity-settings-daemon (Ubuntu) Status: Fix Released = Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1298740 Title: unity-settings-daemon warns when IBus engine layout is default Status in Unity Settings Daemon: In Progress Status in “unity-settings-daemon” package in Ubuntu: Confirmed Bug description: To reproduce: Add Russian keyboard layout and Chinese (Pinyin or Intelligent Pinyin) input method. Switch to Russian layout. Switch to Chinese IM. Try to input pinyin, result is still Cyrillic characters. unity-settings-daemon emits the following warning: (unity-settings-daemon:14828): keyboard-plugin-WARNING **: Couldn't upload new XKB keyboard description Some IBus engines were updated to have a layout of default rather than us, and xkb doesn't accept it as a possible layout from /usr/share/X11/xkb/rules/evdev. To manage notifications about this bug go to: https://bugs.launchpad.net/unity-settings-daemon/+bug/1298740/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1299499] Re: kwin crashes on desktop startup with wobbly windows enabled
** Changed in: mesa (Ubuntu) Status: Confirmed = Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1299499 Title: kwin crashes on desktop startup with wobbly windows enabled Status in Mesa: Confirmed Status in “mesa” package in Ubuntu: Incomplete Bug description: kwin reports a crash while starting up, and desktop effects are not enabled for the session. ProblemType: Crash DistroRelease: Ubuntu 14.04 Package: kde-window-manager 4:4.11.8-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-20.42-generic 3.13.7 Uname: Linux 3.13.0-20-generic x86_64 ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 AssertionMessage: kwin: ../../../../../../../src/mesa/drivers/dri/i965/brw_reset.c:43: brw_get_graphics_reset_status: Assertion `brw-hw_ctx != ((void *)0)' failed. CrashCounter: 1 CurrentDesktop: KDE Date: Sat Mar 29 11:11:04 2014 ExecutablePath: /usr/bin/kwin InstallationDate: Installed on 2014-02-03 (53 days ago) InstallationMedia: Ubuntu-Server 13.10 Saucy Salamander - Release amd64 (20131016) ProcCmdline: /usr/bin/kwin --crashes 2 ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash Signal: 6 SourcePackage: kde-workspace StacktraceTop: __GI_raise (sig=sig@entry=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:56 __GI_abort () at abort.c:89 __assert_fail_base (fmt=0x7f7a0d7c2718 %s%s%s:%u: %s%sAssertion `%s' failed.\n%n, assertion=assertion@entry=0x7f79edba7a63 brw-hw_ctx != ((void *)0), file=file@entry=0x7f79edba7a28 ../../../../../../../src/mesa/drivers/dri/i965/brw_reset.c, line=line@entry=43, function=function@entry=0x7f79edba7a80 brw_get_graphics_reset_status) at assert.c:92 __GI___assert_fail (assertion=0x7f79edba7a63 brw-hw_ctx != ((void *)0), file=0x7f79edba7a28 ../../../../../../../src/mesa/drivers/dri/i965/brw_reset.c, line=43, function=0x7f79edba7a80 brw_get_graphics_reset_status) at assert.c:101 ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so Title: kwin assert failure: kwin: ../../../../../../../src/mesa/drivers/dri/i965/brw_reset.c:43: brw_get_graphics_reset_status: Assertion `brw-hw_ctx != ((void *)0)' failed. UpgradeStatus: Upgraded to trusty on 2014-03-03 (26 days ago) UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1299499/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1302397] [NEW] Pause button from quicklist not working
Public bug reported: When i'm playing radio stream pause button is not working from quickist ** Affects: rhythmbox (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to rhythmbox in Ubuntu. https://bugs.launchpad.net/bugs/1302397 Title: Pause button from quicklist not working Status in “rhythmbox” package in Ubuntu: New Bug description: When i'm playing radio stream pause button is not working from quickist To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1302397/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1302374] Re: No sound after upgrade packages and dist
That issue is confirmed by many users: http://ubuntuforums.org/showthread.php?t=2211608page=2 and as sound was working well a few hours back ( 24 h) and nothing about sound have changed while upgrading, some people are thinking about a possible systemd packages upgrade having broken the sound rights. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1302374 Title: No sound after upgrade packages and dist Status in “pulseaudio” package in Ubuntu: Confirmed Bug description: Hi. I upgrade packages in the morning, next upgrade kernel (dist-upgrade) and after restart i have no sound, no tray sound icon. Below history what I'm done: Start-Date: 2014-04-04 08:02:30 Commandline: apt-get upgrade Upgrade: apt:amd64 (0.9.15.4ubuntu2, 0.9.15.4ubuntu3), kerneloops-daemon:amd64 (0.12+git20090217-3ubuntu7, 0.12+git20090217-3ubuntu8), libfontembed1:amd64 (1.0.50-0ubuntu1, 1.0.51-0ubuntu1), libgdiplus:amd64 (2.11+git20131008.9732566-4ubuntu1, 2.11+git20131008.9732566-5ubuntu1), libgail-3-0:amd64 (3.10.7-0ubuntu4, 3.10.7-0ubuntu5), python-samba:amd64 (4.1.3+dfsg-2ubuntu5, 4.1.6+dfsg-1ubuntu1), apt-transport-https:amd64 (0.9.15.4ubuntu2, 0.9.15.4ubuntu3), libindicator3-7:amd64 (12.10.2+14.04.20140304-0ubuntu1, 12.10.2+14.04.20140402-0ubuntu1), libphonon4:amd64 (4.7.1-0ubuntu7, 4.7.1-0ubuntu8), language-pack-pl:amd64 (14.04+20140321, 14.04+20140401), gsettings-ubuntu-schemas:amd64 (0.0.1+14.04.20140224-0ubuntu1, 0.0.1+14.04.20140401-0ubuntu1), phonon:amd64 (4.7.1-0ubuntu7, 4.7.1-0ubuntu8), gir1.2-packagekitglib-1.0:amd64 (0.8.12-1ubuntu4, 0.8.12-1ubuntu5), gir1.2-gtk-3.0:amd64 (3.10.7-0ubuntu4, 3.10.7-0ubuntu5), apt-utils:amd64 (0.9.15.4ubuntu2, 0.9.15.4ubuntu3), ubuntu-minimal:amd64 (1.322, 1.324), plymouth-theme-ubuntu-text:amd64 (0.8.8-0ubuntu15, 0.8.8-0ubuntu16), parted:amd64 (2.3-17, 2.3-18), libgudev-1.0-0:amd64 (204-5ubuntu13, 204-5ubuntu16), python-apt:amd64 (0.9.3.4build1, 0.9.3.5), command-not-found:amd64 (0.3ubuntu10, 0.3ubuntu12), tzdata-java:amd64 (2014a-1, 2014b-1), file:amd64 (5.14-2ubuntu2, 5.14-2ubuntu3), libmagic1:amd64 (5.14-2ubuntu2, 5.14-2ubuntu3), python3-commandnotfound:amd64 (0.3ubuntu10, 0.3ubuntu12), libglib2.0-0:amd64 (2.40.0-1ubuntu1, 2.40.0-2), libapt-inst1.5:amd64 (0.9.15.4ubuntu2, 0.9.15.4ubuntu3), libnss3-1d:amd64 (3.15.4-1ubuntu6, 3.15.4-1ubuntu7), libgtk-3-bin:amd64 (3.10.7-0ubuntu4, 3.10.7-0ubuntu5), libbluetooth3:amd64 (4.101-0ubuntu10, 4.101-0ubuntu11), bluez-cups:amd64 (4.101-0ubuntu10, 4.101-0ubuntu11), plymouth:amd64 (0.8.8-0ubuntu15, 0.8.8-0ubuntu16), libnss3-nssdb:amd64 (3.15.4-1ubuntu6, 3.15.4-1ubuntu7), ubuntu-standard:amd64 (1.322, 1.324), libglib2.0-data:amd64 (2.40.0-1ubuntu1, 2.40.0-2), bluez-alsa:amd64 (4.101-0ubuntu10, 4.101-0ubuntu11), gir1.2-gudev-1.0:amd64 (204-5ubuntu13, 204-5ubuntu16), indicator-application:amd64 (12.10.1+14.04.20140324-0ubuntu1, 12.10.1+14.04.20140402-0ubuntu1), samba-common-bin:amd64 (4.1.3+dfsg-2ubuntu5, 4.1.6+dfsg-1ubuntu1), cups-browsed:amd64 (1.0.50-0ubuntu1, 1.0.51-0ubuntu1), libparted0debian1:amd64 (2.3-17, 2.3-18), python-commandnotfound:amd64 (0.3ubuntu10, 0.3ubuntu12), cups-filters-core-drivers:amd64 (1.0.50-0ubuntu1, 1.0.51-0ubuntu1), language-pack-gnome-en:amd64 (14.04+20140321, 14.04+20140401), xfdesktop4-data:amd64 (4.11.4-1ubuntu2, 4.11.5-0ubuntu1), acpid:amd64 (2.0.21-1ubuntu1, 2.0.21-1ubuntu2), ubuntu-sso-client:amd64 (13.10-0ubuntu4, 13.10-0ubuntu5), command-not-found-data:amd64 (0.3ubuntu10, 0.3ubuntu12), samba-libs:amd64 (4.1.3+dfsg-2ubuntu5, 4.1.6+dfsg-1ubuntu1), libapt-pkg4.12:amd64 (0.9.15.4ubuntu2, 0.9.15.4ubuntu3), python3-apt:amd64 (0.9.3.4build1, 0.9.3.5), libgtk-3-0:amd64 (3.10.7-0ubuntu4, 3.10.7-0ubuntu5), bluez:amd64 (4.101-0ubuntu10, 4.101-0ubuntu11), libnss3:amd64 (3.15.4-1ubuntu6, 3.15.4-1ubuntu7), indicator-sound:amd64 (12.10.2+14.04.20140324.is.12.10.2+14.04.20140320-0ubuntu1, 12.10.2+14.04.20140401-0ubuntu1), apache2-data:amd64 (2.4.7-1ubuntu3, 2.4.7-1ubuntu4), python-smbc:amd64 (1.0.13-0ubuntu6, 1.0.14.1-0ubuntu2), cups-filters:amd64 (1.0.50-0ubuntu1, 1.0.51-0ubuntu1), libplymouth2:amd64 (0.8.8-0ubuntu15, 0.8.8-0ubuntu16), unity-settings-daemon:amd64 (14.04.0+14.04.20140310-0ubuntu2, 14.04.0+14.04.20140402-0ubuntu1), smbclient:amd64 (4.1.3+dfsg-2ubuntu5, 4.1.6+dfsg-1ubuntu1), lightdm:amd64 (1.9.13-0ubuntu1, 1.9.14-0ubuntu1), libgtk-3-common:amd64 (3.10.7-0ubuntu4, 3.10.7-0ubuntu5), language-pack-gnome-pl:amd64 (14.04+20140321, 14.04+20140401), python-ubuntu-sso-client:amd64 (13.10-0ubuntu4, 13.10-0ubuntu5), liblightdm-gobject-1-0:amd64 (1.9.13-0ubuntu1, 1.9.14-0ubuntu1), xfdesktop4:amd64 (4.11.4-1ubuntu2, 4.11.5-0ubuntu1), xserver-xorg-video-sis:amd64 (0.10.7-0ubuntu5, 0.10.7-0ubuntu6), apache2:amd64 (2.4.7-1ubuntu3, 2.4.7-1ubuntu4), tzdata:amd64 (2014a-1, 2014b-1), libglib2.0-bin:amd64 (2.40.0-1ubuntu1, 2.40.0-2),
[Desktop-packages] [Bug 1302353] Re: regression: ibus ignores keyboard layout
Nevermind the paste.debian.net URL in above comment, that got in there accidentally -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1302353 Title: regression: ibus ignores keyboard layout Status in “ibus” package in Ubuntu: Incomplete Status in “unity-settings-daemon” package in Ubuntu: Triaged Bug description: The recent update of unity packages introduced a bad regression for ibus users. I assume the fault lies with unity since ibus hasn't been updated for several weeks and my machine was fine until about two days ago around which time some unity updates rolled in. I have a German keyboard layout (QWERTZ not QWERTY as in the US case). I use anthy and mozc for Japanese input. Since two days ago the default layout with the Japanese IME are a US layout throwing me off when blind-typing. To look into the matter, I opened ibus-setup and there are three Input methods listed there: English - English (US), Japanese - Anthy and Japanese -Mozc. German was conspicuously absent . I eventually managed to add a German layout to it and delete the US layout. I then restart ibus with ibus restart only to find the US keyboard layout not only back but it's default again. Argh! In other words, the explicit choice I'm trying to force doesn't stick. There are four keyboard layouts currently defined in System Settings - Text Entry - Input sources to use, none of them have anything to do with a US-layout; de1, de2, anthy and mozc. I cycle through them via Super+Space. Anthy is set to use the system default layout. The regression is that it currently inists on US layout with no way to even override this silly choice. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1302353/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1301839] Re: AMD Radeon HD 8670A/8670M/8690M[1002:6660] Low-graphic mode with Trusty dailylive
Marking as Incomplete, as we are waiting for some debug logs ** Changed in: xserver-xorg-video-ati (Ubuntu) Status: New = Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu. https://bugs.launchpad.net/bugs/1301839 Title: AMD Radeon HD 8670A/8670M/8690M[1002:6660] Low-graphic mode with Trusty dailylive Status in “xserver-xorg-video-ati” package in Ubuntu: Incomplete Status in “xserver-xorg-video-intel” package in Ubuntu: New Bug description: CID: 201305-13624 This system cannot boot to desktop by Try Ubuntu option with liveUSB, it will ask you to run on low-graphic mode. Steps: 1. Try to boot to the desktop with 14.04 dailylive (2-Apr-2014) Expected result * Desktop works fine Actual result: * You will be ask to run on low-graphic mode, or you will need to add nomodeset parameter into grub to boot normally. This bug exists in 12.04.4, and it's fixed in Trusty dailylive 11-Mar-2014 07:51, also the Trusty beta 2 image, but it's now broken again. You can refer to bug 1290745 0a:00.0 Display controller [0380]: Advanced Micro Devices, Inc. [AMD/ATI] Sun XT [Radeon HD 8670A/8670M/8690M] [1002:6660] ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xserver-xorg-video-radeon 1:7.3.0-1ubuntu3 ProcVersionSignature: Ubuntu 3.13.0-20.42-generic 3.13.7 Uname: Linux 3.13.0-20-generic x86_64 .tmp.unity.support.test.1: ApportVersion: 2.14-0ubuntu1 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: Thu Apr 3 05:44:12 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: fwts-efi-runtime-dkms, 14.03.01, 3.13.0-20-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:2162] Subsystem: Hewlett-Packard Company Device [103c:2162] InstallationDate: Installed on 2014-04-03 (0 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Daily amd64 (20140401) MachineType: Hewlett-Packard HP Pavilion TS 14 Notebook PC ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-20-generic root=UUID=8fdb7584-0c55-43ae-923f-b24b1286a592 ro rootdelay=60 quiet splash nomodeset initcall_debug Renderer: Software SourcePackage: xserver-xorg-video-ati UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/27/2013 dmi.bios.vendor: Insyde dmi.bios.version: B.09 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 2162 dmi.board.vendor: Hewlett-Packard dmi.board.version: 29.0A dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrB.09:bd05/27/2013:svnHewlett-Packard:pnHPPavilionTS14NotebookPC:pvr089C101630100:rvnHewlett-Packard:rn2162:rvr29.0A:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.name: HP Pavilion TS 14 Notebook PC dmi.product.version: 089C101630100 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.11+14.04.20140328-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-1ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.15.0-1ubuntu7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Thu Apr 3 05:36:25 2014 xserver.configfile: default xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.15.0-1ubuntu7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/1301839/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1302402] [NEW] Radio stream stops when buffer level reach 0%.
Public bug reported: It should try to restart stream and reconnect. Description:Ubuntu Trusty Tahr (development branch) Release:14.04 rhythmbox: Installed: 3.0.2-0ubuntu1 Candidate: 3.0.2-0ubuntu1 Version table: *** 3.0.2-0ubuntu1 0 500 http://pl.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages 100 /var/lib/dpkg/status ** Affects: rhythmbox (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to rhythmbox in Ubuntu. https://bugs.launchpad.net/bugs/1302402 Title: Radio stream stops when buffer level reach 0%. Status in “rhythmbox” package in Ubuntu: New Bug description: It should try to restart stream and reconnect. Description: Ubuntu Trusty Tahr (development branch) Release: 14.04 rhythmbox: Installed: 3.0.2-0ubuntu1 Candidate: 3.0.2-0ubuntu1 Version table: *** 3.0.2-0ubuntu1 0 500 http://pl.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1302402/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1302397] Re: Pause button from quicklist not working
Description:Ubuntu Trusty Tahr (development branch) Release:14.04 rhythmbox: Installed: 3.0.2-0ubuntu1 Candidate: 3.0.2-0ubuntu1 Version table: *** 3.0.2-0ubuntu1 0 500 http://pl.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages 100 /var/lib/dpkg/status -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to rhythmbox in Ubuntu. https://bugs.launchpad.net/bugs/1302397 Title: Pause button from quicklist not working Status in “rhythmbox” package in Ubuntu: New Bug description: When i'm playing radio stream pause button is not working from quickist To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1302397/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1041790]
*** Bug 77043 has been marked as a duplicate of this bug. *** -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu. https://bugs.launchpad.net/bugs/1041790 Title: [snb] GPU lockup IPEHR: 0x0b160001 IPEHR: 0x0b140001, workaround i915.semaphores=0 Status in X.org xf86-video-intel: In Progress Status in “linux” package in Ubuntu: Incomplete Status in “sandybridge-meta” package in Ubuntu: Confirmed Status in “xserver-xorg-video-intel” package in Ubuntu: Triaged Bug description: X locks up periodically for a 2 to ten seconds at a time and this crash log gets generated. It's significantly more than several times a day but not quite continuous. If you indeed have this bug, that should stop the lockups from happening. Irrespective, please file a new bug report so your hardware may be tracked. WORKAROUND: Edit your /etc/default/grub from: GRUB_CMDLINE_LINUX_DEFAULT=quiet splash to: GRUB_CMDLINE_LINUX_DEFAULT=quiet splash i915.semaphores=0 run the following and reboot: sudo update-grub The side effects of this is rendering throughput is dropped by 10% with SNA, or as much as 3x with UXA. OpenGL performance is likely to be reduced by about 30%. More CPU time is spent waiting for the GPU with rc6 disabled, so increased power consumption. ProblemType: Crash DistroRelease: Ubuntu 12.10 Package: xserver-xorg-video-intel 2:2.20.3-0ubuntu1 Uname: Linux 3.6.0-rc3-git-20120826.1015 x86_64 ApportVersion: 2.5.1-0ubuntu2 Architecture: amd64 Chipset: sandybridge-m-gt2 Date: Sun Aug 26 16:06:32 2012 DistroCodename: quantal DistroVariant: ubuntu DuplicateSignature: [sandybridge-m-gt2] GPU lockup IPEHR: 0x0b160001 IPEHR: 0x0b140001 Ubuntu 12.10 EcryptfsInUse: Yes ExecutablePath: /usr/share/apport/apport-gpu-error-intel.py GpuHangFrequency: Continuously InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Alpha amd64 (20120724.2) InterpreterPath: /usr/bin/python3.2mu MachineType: Dell Inc. Dell System XPS L502X ProcCmdline: /usr/bin/python3 /usr/share/apport/apport-gpu-error-intel.py ProcEnviron: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.6.0-rc3-git-20120826.1015 root=UUID=135c8090-427c-460a-909d-eff262cd44b6 ro quiet splash vt.handoff=7 RelatedPackageVersions: xserver-xorg 1:7.7+1ubuntu3 libdrm2 2.4.38-0ubuntu2 xserver-xorg-video-intel 2:2.20.3-0ubuntu1 SourcePackage: xserver-xorg-video-intel Title: [sandybridge-m-gt2] GPU lockup IPEHR: 0x0b160001 IPEHR: 0x0b140001 UdevDb: Error: [Errno 2] No such file or directory: 'udevadm' UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 05/29/2012 dmi.bios.vendor: Dell Inc. dmi.bios.version: A11 dmi.board.name: 0NJT03 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA11:bd05/29/2012:svnDellInc.:pnDellSystemXPSL502X:pvr:rvnDellInc.:rn0NJT03:rvrA00:cvnDellInc.:ct8:cvr0.1: dmi.product.name: Dell System XPS L502X dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/xserver-xorg-video-intel/+bug/1041790/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 359361] Re: ALSA SPDIF Digital output clipping / crackling during playback
I have this problem with Lubuntu 14.04 64bit.
I have Radeon HD 7760
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/359361
Title:
ALSA SPDIF Digital output clipping / crackling during playback
Status in “alsa-driver” package in Ubuntu:
Confirmed
Bug description:
When playing sound in Jaunty out of my HDA Intel SPDIF out, loud
sounds clip. This is audible because from the strong distortion it
produces, which I have seen some people characterize as crackling.
For example, if I go to system-preferences-sound and play the test
sound, the sinusoid is audibly clipping. I have all of my sliders in
alsamixer zeroed except for master (@100) and IEC958 (@100). Note that
if I turn down the volume of the master and/or the IEC958, the
clipping is still present---I've gone as low as -21dB (64/100) on both
sliders simultaneously, and the clipping is still there.
I looked around for solutions, this sounds similar to my problem:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/285866
However, as I noted, I've tried reducing my levels, and my PCM mixer
level is all the way at 0 (-58.50 dB) anyway. Not to mention that
these are digital outputs, so having them at the 0dB gain position
(100% for the master and IEC958 sliders) should be fine...
Yes I am certain it's not my speakers clipping.
Oddly enough, at one point I was able to get it not to clip in the
gnome sound settings control by going through some sequence of trying
different backends (various options for ALSA, for OSS, etc.). I have
not been able to reliably reproduce the non-clipping, but I will keep
trying.
For some reason, I hear the clipping when I listen to music using
gnome-listen, but not when using Amarok using Xine as the backend.
Please help me stop the clipping.
ProblemType: Bug
Architecture: amd64
ArecordDevices:
List of CAPTURE Hardware Devices
card 0: Intel [HDA Intel], device 0: AD198x Analog [AD198x Analog]
Subdevices: 2/2
Subdevice #0: subdevice #0
Subdevice #1: subdevice #1
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/dsp',
'/dev/snd/controlC0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p',
'/dev/snd/pcmC0D1p', '/dev/snd/seq', '/dev/snd/timer', '/dev/sequencer2',
'/dev/sequencer'] failed with exit code 1:
Card0.Amixer.info:
Card hw:0 'Intel'/'HDA Intel at 0xfe02 irq 17'
Mixer name : 'Analog Devices AD1984'
Components : 'HDA:11d41984,17aa20d7,00100400'
Controls : 30
Simple ctrls : 19
DistroRelease: Ubuntu 9.04
Package: alsa-base 1.0.18.dfsg-1ubuntu8
PackageArchitecture: all
ProcEnviron:
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: alsa-driver
Uname: Linux 2.6.28-11-generic x86_64
---
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21.
Architecture: amd64
ArecordDevices:
List of CAPTURE Hardware Devices
card 0: Intel [HDA Intel], device 0: AD198x Analog [AD198x Analog]
Subdevices: 2/2
Subdevice #0: subdevice #0
Subdevice #1: subdevice #1
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: edlarson 1435 F pulseaudio
Card0.Amixer.info:
Card hw:0 'Intel'/'HDA Intel at 0xfe02 irq 17'
Mixer name : 'Analog Devices AD1984'
Components : 'HDA:11d41984,17aa20d7,00100400'
Controls : 29
Simple ctrls : 18
Card29.Amixer.info:
Card hw:29 'ThinkPadEC'/'ThinkPad Console Audio Control at EC reg 0x30, fw
7KHT24WW-1.08'
Mixer name : 'ThinkPad EC 7KHT24WW-1.08'
Components : ''
Controls : 1
Simple ctrls : 1
Card29.Amixer.values:
Simple mixer control 'Console',0
Capabilities: pswitch pswitch-joined penum
Playback channels: Mono
Mono: Playback [on]
DistroRelease: Ubuntu 10.04
InstallationMedia: Ubuntu 10.04 Lucid Lynx - Beta amd64 (20100318)
Package: alsa-driver (not installed)
ProcEnviron:
LANG=en_US.utf8
SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.32-21.32-generic 2.6.32.11+drm33.2
Tags: lucid
Uname: Linux 2.6.32-21-generic x86_64
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
dmi.bios.date: 11/14/2008
dmi.bios.vendor: LENOVO
dmi.bios.version: 7LETC5WW (2.25 )
dmi.board.name: 7732CTO
dmi.board.vendor: LENOVO
dmi.board.version: Not Available
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias:
dmi:bvnLENOVO:bvr7LETC5WW(2.25):bd11/14/2008:svnLENOVO:pn7732CTO:pvrThinkPadR61:rvnLENOVO:rn7732CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 7732CTO
dmi.product.version: ThinkPad R61
dmi.sys.vendor: LENOVO
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/359361/+subscriptions
--
[Desktop-packages] [Bug 1302105] Re: Highlight glitch while scrolling the services list
** Changed in: gtk Status: Unknown = New ** Changed in: gtk Importance: Unknown = Medium -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center-signon in Ubuntu. https://bugs.launchpad.net/bugs/1302105 Title: Highlight glitch while scrolling the services list Status in Online Accounts: GNOME Control Center: Confirmed Status in GTK+ GUI Toolkit: New Status in “gnome-control-center-signon” package in Ubuntu: Confirmed Bug description: On the Online Accounts panel, if I scroll the list of services (on the right side) the highlight is repeated. That is, say I have the mouse over Twitter, when I scroll the list with the mouse wheel the highlighting is drawn over Twitter and newly hovered items. I've added a screenshot. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity-control-center-signon 0.1.7~+14.04.20140211.2-0ubuntu4 ProcVersionSignature: Ubuntu 3.13.0-20.42-generic 3.13.7 Uname: Linux 3.13.0-20-generic x86_64 ApportVersion: 2.14-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Thu Apr 3 14:19:56 2014 InstallationDate: Installed on 2014-03-16 (18 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140316) SourcePackage: gnome-control-center-signon UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center-signon/+bug/1302105/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1298611] Re: [FFe] apparmor signal and ptrace mediation
This bug was fixed in the package libvirt - 1.2.2-0ubuntu9 --- libvirt (1.2.2-0ubuntu9) trusty; urgency=medium [ Jamie Strandboge ] * updates for AppArmor signals and ptrace mediation (LP: #1298611) - debian/apparmor/libvirt-qemu: allow guests to receive signals from and be tracedby libvirtd (additional signal and ptrace rules come from the AppArmor base abstraction) - debian/apparmor/usr.sbin.libvirtd: + grant bare signal and ptrace rule + grant dbus on the system bus (should have been added in 13.10) -- Tyler Hicks tyhi...@canonical.com Thu, 03 Apr 2014 02:09:53 -0500 ** Changed in: libvirt (Ubuntu) Status: New = Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1298611 Title: [FFe] apparmor signal and ptrace mediation Status in “apparmor” package in Ubuntu: Confirmed Status in “apparmor-easyprof-ubuntu” package in Ubuntu: New Status in “libvirt” package in Ubuntu: Fix Released Status in “lightdm” package in Ubuntu: Fix Released Status in “linux” package in Ubuntu: Fix Released Status in “lxc” package in Ubuntu: New Bug description: Background: kernel and apparmor userspace updates to support signal and ptrace mediation. These packages are listed in one bug because they are related, but the FFes may be granted and the uploads may happen at different times. = linux = Summary: This feature freeze exception is requested for signal and ptrace mediation via apparmor in the kernel. When used with a compatible apparmor userspace, signals and ptrace rules are supported. When used without a compatible apparmor userspace (eg, on a precise system with a trusty backport kernel), signal and ptrace mediation is not enforced (ie, you can use this kernel with an old userspace without any issues). The fine grained mediation of signals and ptraces also incorporates improved versioning support that allows this kernel to better support older and newer userspaces. This allows for this version of the kernel to work as a backport kernel unmodified (currently a patch and config are used to provide backport kernels). The kernel patch is available at git://kernel.ubuntu.com/jj/ubuntu-trusty.git in the trusty-alpha6 branch apparmor-alpha6-sync Testing: * 12.04 system with backported kernel: DONE * test-apparmor.py: PASS (runs extensive tests (upstream and distro)) * exploratory manual testing: PASS (networking, aa-enforce with firefox, firefox works, apparmor blocks access, etc) * aa-status: PASS * lxc: PASS (containers can be created, started, shutdown) * libvirt: PASS (VMs started via openstack, and test-libvirt.py from QRT passes all tests) * 14.04 system (non-Touch) with current apparmor userspace: DONE (relevant parts of https://wiki.ubuntu.com/Process/Merges/TestPlans/AppArmor) * test-apparmor.py: PASS (runs extensive tests (upstream and distro)) * exploratory manual testing: PASS (networking, aa-enforce with firefox, firefox works, apparmor blocks access, etc) * aa-status: PASS * lxc: PASS (containers can be created, started, shutdown) * libvirt: PASS (QRT/script/test-libvirt.py (though there are 3 failures unrelated to apparmor)) * click-apparmor QRT touch image tests: PASS * apparmor-easyprof-ubuntu QRT touch image tests: PASS * 14.04 system (non-Touch) with updated apparmor userspace capable of supporting signal and ptrace mediation: DONE (relevant parts of https://wiki.ubuntu.com/Process/Merges/TestPlans/AppArmor. Note: this is marked 'done' from the kernel perspective-- the apparmor userspace upload is being prepared and tests assume userspace is using latest patches on the list) * test-apparmor.py: PASS (runs extensive tests (upstream and distro)) * exploratory manual testing: PASS (networking, aa-enforce with firefox, firefox works, apparmor blocks access, etc) * aa-status: PASS * lxc: PASS (containers can be created, started, shutdown) * libvirt: PASS (QRT/script/test-libvirt.py (though there are 3 failures unrelated to apparmor)) * click-apparmor QRT touch image tests: PASS * apparmor-easyprof-ubuntu QRT touch image tests: PASS Justification: This feature is required to support comprehensive application confinement on Ubuntu Touch. This feature adds a significant security benefit to libvirt's qemu guest isolation which is fundamental to Ubuntu on Server/Cloud. This feature also adds a welcome improvement to administrators wishing to further protect their systems. = apparmor userspace = Summary: This feature freeze exception is requested for signal and ptrace mediation for apparmor userspace. When used with a compatible kernel, signals and ptrace rules are supported. When used without a compatible kernel (eg, on Ubuntu Touch for a few weeks or with upstream kernels), signal and ptrace
[Desktop-packages] [Bug 1302348] Re: after today's Trusty updates/restart, NM will not connect to wifi
After adding cgmanager, qt4-default, and qdbus-qt5, all is back to normal with wifi. I am also once again able to mount my phone with Dolphin, and my soundcard is again correctly detected. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1302348 Title: after today's Trusty updates/restart, NM will not connect to wifi Status in “network-manager” package in Ubuntu: New Bug description: I see all the wireless signals in the neighborhood, but the connect button does not connect my laptop to the internet. Also, history seems lost, as it reports that my wifi has never been used, when it was in use a few minutes before. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: network-manager 0.9.8.8-0ubuntu5 ProcVersionSignature: Ubuntu 3.13.0-22.44-generic 3.13.8 Uname: Linux 3.13.0-22-generic x86_64 ApportVersion: 2.14-0ubuntu1 Architecture: amd64 CurrentDesktop: KDE Date: Thu Apr 3 22:43:11 2014 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2013-06-18 (289 days ago) InstallationMedia: Kubuntu 13.04 Raring Ringtail - Release amd64 (20130424) IpRoute: default via 192.168.15.1 dev eth0 proto static 192.168.15.0/24 dev eth0 proto kernel scope link src 192.168.15.3 metric 1 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: network-manager UpgradeStatus: Upgraded to trusty on 2014-03-04 (30 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1302348/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1285179] Re: pulseaudio does not remember the audio level for usb audio devices
state.D1 {
control.1 {
iface PCM
name 'Playback Channel Map'
value.0 3
value.1 4
comment {
access read
type INTEGER
count 2
range '0 - 36'
}
}
control.2 {
iface MIXER
name 'PCM Playback Switch'
value true
comment {
access 'read write'
type BOOLEAN
count 1
}
}
}
you have to post output of
lsusb -
if your usb audio device have no volume control,
you have to add a softvol plugin
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1285179
Title:
pulseaudio does not remember the audio level for usb audio devices
Status in “pulseaudio” package in Ubuntu:
In Progress
Bug description:
When I plug in my Audioengine D1, output is switched to it, but the
volume level is set to 100%. I then have to open the sound settings,
switch the output device to it before I can adjust the volume level.
Once the level has been adjusted, if I unplug the device and then plug
it back it, the volume will be reset to 100% for it and I'll have to
repeat the steps all over again to adjust it.
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: pulseaudio 1:4.0-0ubuntu7
ProcVersionSignature: Ubuntu 3.13.0-12.32-generic 3.13.4
Uname: Linux 3.13.0-12-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.13.2-0ubuntu5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: valdiyen 3325 F pulseaudio
/dev/snd/pcmC1D0p: valdiyen 3325 F...m pulseaudio
/dev/snd/controlC2: valdiyen 3325 F pulseaudio
/dev/snd/controlC0: valdiyen 3325 F pulseaudio
CurrentDesktop: Unity
Date: Wed Feb 26 09:00:53 2014
EcryptfsInUse: Yes
InstallationDate: Installed on 2014-02-14 (11 days ago)
InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140211)
SourcePackage: pulseaudio
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/29/2013
dmi.bios.vendor: Apple Inc.
dmi.bios.version: MBP111.88Z.0138.B03.1310291227
dmi.board.asset.tag: Base Board Asset Tag#
dmi.board.name: Mac-189A3D4F975D5FFC
dmi.board.vendor: Apple Inc.
dmi.board.version: MacBookPro11,1
dmi.chassis.type: 10
dmi.chassis.vendor: Apple Inc.
dmi.chassis.version: Mac-189A3D4F975D5FFC
dmi.modalias:
dmi:bvnAppleInc.:bvrMBP111.88Z.0138.B03.1310291227:bd10/29/2013:svnAppleInc.:pnMacBookPro11,1:pvr1.0:rvnAppleInc.:rnMac-189A3D4F975D5FFC:rvrMacBookPro11,1:cvnAppleInc.:ct10:cvrMac-189A3D4F975D5FFC:
dmi.product.name: MacBookPro11,1
dmi.product.version: 1.0
dmi.sys.vendor: Apple Inc.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1285179/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1302414] [NEW] Xubuntu can't restart, power off after upgrade packages, dist
Public bug reported: After upgrade packages, and restart computer I can't restart, power off(shut down) computer using menu panel. When i choose restart or shut down it logout me, and I have login panel/menu again. Packages thata i upgrade: Start-Date: 2014-04-04 08:02:30 Commandline: apt-get upgrade Upgrade: apt:amd64 (0.9.15.4ubuntu2, 0.9.15.4ubuntu3), kerneloops-daemon:amd64 (0.12+git20090217-3ubuntu7, 0.12+git20090217-3ubuntu8), libfontembed1:amd64 (1.0.50-0ubuntu1, 1.0.51-0ubuntu1), libgdiplus:amd64 (2.11+git20131008.9732566-4ubuntu1, 2.11+git20131008.9732566-5ubuntu1), libgail-3-0:amd64 (3.10.7-0ubuntu4, 3.10.7-0ubuntu5), python-samba:amd64 (4.1.3+dfsg-2ubuntu5, 4.1.6+dfsg-1ubuntu1), apt-transport-https:amd64 (0.9.15.4ubuntu2, 0.9.15.4ubuntu3), libindicator3-7:amd64 (12.10.2+14.04.20140304-0ubuntu1, 12.10.2+14.04.20140402-0ubuntu1), libphonon4:amd64 (4.7.1-0ubuntu7, 4.7.1-0ubuntu8), language-pack-pl:amd64 (14.04+20140321, 14.04+20140401), gsettings-ubuntu-schemas:amd64 (0.0.1+14.04.20140224-0ubuntu1, 0.0.1+14.04.20140401-0ubuntu1), phonon:amd64 (4.7.1-0ubuntu7, 4.7.1-0ubuntu8), gir1.2-packagekitglib-1.0:amd64 (0.8.12-1ubuntu4, 0.8.12-1ubuntu5), gir1.2-gtk-3.0:amd64 (3.10.7-0ubuntu4, 3.10.7-0ubuntu5), apt-utils:amd64 (0.9.15.4ubuntu2, 0.9.15.4ubuntu3), ubuntu-minimal:amd64 (1.322, 1.324), plymouth-theme-ubuntu-text:amd64 (0.8.8-0ubuntu15, 0.8.8-0ubuntu16), parted:amd64 (2.3-17, 2.3-18), libgudev-1.0-0:amd64 (204-5ubuntu13, 204-5ubuntu16), python-apt:amd64 (0.9.3.4build1, 0.9.3.5), command-not-found:amd64 (0.3ubuntu10, 0.3ubuntu12), tzdata-java:amd64 (2014a-1, 2014b-1), file:amd64 (5.14-2ubuntu2, 5.14-2ubuntu3), libmagic1:amd64 (5.14-2ubuntu2, 5.14-2ubuntu3), python3-commandnotfound:amd64 (0.3ubuntu10, 0.3ubuntu12), libglib2.0-0:amd64 (2.40.0-1ubuntu1, 2.40.0-2), libapt-inst1.5:amd64 (0.9.15.4ubuntu2, 0.9.15.4ubuntu3), libnss3-1d:amd64 (3.15.4-1ubuntu6, 3.15.4-1ubuntu7), libgtk-3-bin:amd64 (3.10.7-0ubuntu4, 3.10.7-0ubuntu5), libbluetooth3:amd64 (4.101-0ubuntu10, 4.101-0ubuntu11), bluez-cups:amd64 (4.101-0ubuntu10, 4.101-0ubuntu11), plymouth:amd64 (0.8.8-0ubuntu15, 0.8.8-0ubuntu16), libnss3-nssdb:amd64 (3.15.4-1ubuntu6, 3.15.4-1ubuntu7), ubuntu-standard:amd64 (1.322, 1.324), libglib2.0-data:amd64 (2.40.0-1ubuntu1, 2.40.0-2), bluez-alsa:amd64 (4.101-0ubuntu10, 4.101-0ubuntu11), gir1.2-gudev-1.0:amd64 (204-5ubuntu13, 204-5ubuntu16), indicator-application:amd64 (12.10.1+14.04.20140324-0ubuntu1, 12.10.1+14.04.20140402-0ubuntu1), samba-common-bin:amd64 (4.1.3+dfsg-2ubuntu5, 4.1.6+dfsg-1ubuntu1), cups-browsed:amd64 (1.0.50-0ubuntu1, 1.0.51-0ubuntu1), libparted0debian1:amd64 (2.3-17, 2.3-18), python-commandnotfound:amd64 (0.3ubuntu10, 0.3ubuntu12), cups-filters-core-drivers:amd64 (1.0.50-0ubuntu1, 1.0.51-0ubuntu1), language-pack-gnome-en:amd64 (14.04+20140321, 14.04+20140401), xfdesktop4-data:amd64 (4.11.4-1ubuntu2, 4.11.5-0ubuntu1), acpid:amd64 (2.0.21-1ubuntu1, 2.0.21-1ubuntu2), ubuntu-sso-client:amd64 (13.10-0ubuntu4, 13.10-0ubuntu5), command-not-found-data:amd64 (0.3ubuntu10, 0.3ubuntu12), samba-libs:amd64 (4.1.3+dfsg-2ubuntu5, 4.1.6+dfsg-1ubuntu1), libapt-pkg4.12:amd64 (0.9.15.4ubuntu2, 0.9.15.4ubuntu3), python3-apt:amd64 (0.9.3.4build1, 0.9.3.5), libgtk-3-0:amd64 (3.10.7-0ubuntu4, 3.10.7-0ubuntu5), bluez:amd64 (4.101-0ubuntu10, 4.101-0ubuntu11), libnss3:amd64 (3.15.4-1ubuntu6, 3.15.4-1ubuntu7), indicator-sound:amd64 (12.10.2+14.04.20140324.is.12.10.2+14.04.20140320-0ubuntu1, 12.10.2+14.04.20140401-0ubuntu1), apache2-data:amd64 (2.4.7-1ubuntu3, 2.4.7-1ubuntu4), python-smbc:amd64 (1.0.13-0ubuntu6, 1.0.14.1-0ubuntu2), cups-filters:amd64 (1.0.50-0ubuntu1, 1.0.51-0ubuntu1), libplymouth2:amd64 (0.8.8-0ubuntu15, 0.8.8-0ubuntu16), unity-settings-daemon:amd64 (14.04.0+14.04.20140310-0ubuntu2, 14.04.0+14.04.20140402-0ubuntu1), smbclient:amd64 (4.1.3+dfsg-2ubuntu5, 4.1.6+dfsg-1ubuntu1), lightdm:amd64 (1.9.13-0ubuntu1, 1.9.14-0ubuntu1), libgtk-3-common:amd64 (3.10.7-0ubuntu4, 3.10.7-0ubuntu5), language-pack-gnome-pl:amd64 (14.04+20140321, 14.04+20140401), python-ubuntu-sso-client:amd64 (13.10-0ubuntu4, 13.10-0ubuntu5), liblightdm-gobject-1-0:amd64 (1.9.13-0ubuntu1, 1.9.14-0ubuntu1), xfdesktop4:amd64 (4.11.4-1ubuntu2, 4.11.5-0ubuntu1), xserver-xorg-video-sis:amd64 (0.10.7-0ubuntu5, 0.10.7-0ubuntu6), apache2:amd64 (2.4.7-1ubuntu3, 2.4.7-1ubuntu4), tzdata:amd64 (2014a-1, 2014b-1), libglib2.0-bin:amd64 (2.40.0-1ubuntu1, 2.40.0-2), apache2-bin:amd64 (2.4.7-1ubuntu3, 2.4.7-1ubuntu4), libwbclient0:amd64 (4.1.3+dfsg-2ubuntu5, 4.1.6+dfsg-1ubuntu1), linux-libc-dev:amd64 (3.13.0-20.42, 3.13.0-22.44), python-apt-common:amd64 (0.9.3.4build1, 0.9.3.5), samba-common:amd64 (4.1.3+dfsg-2ubuntu5, 4.1.6+dfsg-1ubuntu1), language-pack-en:amd64 (14.04+20140321, 14.04+20140401), plymouth-label:amd64 (0.8.8-0ubuntu15, 0.8.8-0ubuntu16), libpackagekit-glib2-16:amd64 (0.8.12-1ubuntu4, 0.8.12-1ubuntu5), libsmbclient:amd64 (4.1.3+dfsg-2ubuntu5, 4.1.6+dfsg-1ubuntu1),
[Desktop-packages] [Bug 1209031] Re: no way to add lpd/lpr printers on saucy
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: system-config-printer (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to system-config-printer in Ubuntu. https://bugs.launchpad.net/bugs/1209031 Title: no way to add lpd/lpr printers on saucy Status in “system-config-printer” package in Ubuntu: Confirmed Bug description: In previous versions it was possible to add an lpd/lpr host and queue. The new version in saucy does not give any such option. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: printer-applet (not installed) ProcVersionSignature: Ubuntu 3.10.0-6.17-generic 3.10.3 Uname: Linux 3.10.0-6-generic x86_64 ApportVersion: 2.12-0ubuntu3 Architecture: amd64 Date: Wed Aug 7 09:31:41 2013 InstallationDate: Installed on 2013-07-28 (9 days ago) InstallationMedia: Ubuntu-GNOME 13.10 Saucy Salamander - Alpha amd64 (20130724) MarkForUpload: True SourcePackage: printer-applet UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/system-config-printer/+bug/1209031/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 512220] Re: cupsd crash Closing on unknown HTTP state 0
Hi, just a short update: neither our production server nor the testing environment have exhibited any crashes lately. We still have the java printing api application (the one using BIRT) configured to access the testing system. So that explains why the production system does not crash any more. The testing system hardly gets any print jobs at all. So I guess for the server to crash we need both at least a moderate load of regular print jobs and an application accessing the printer list or details (such as Firefox or BIRT). I haven't had much time in the last couple of weeks to look into this, and I'll be out of the office for most of the next months, so I won't be able to work on this for the next couple of weeks. Regards Johannes -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/512220 Title: cupsd crash Closing on unknown HTTP state 0 Status in “cups” package in Ubuntu: Confirmed Bug description: Binary package hint: cups I often get trouble with cupsd crashing and Apport saying the following: The problem cannot be reported: The program crashed on an assertion failure, but the message could not be retrieved. Apport does not support reporting these crashes. I think the crash is due to my having a saved Firefox session with Cups' administration window (http://localhost:631/admin) in it. The crash seems to occur when this session is restored as part of the session restore when I log in to my desktop environment. I have turned on debug-logging and can see the following: D [25/Jan/2010:08:57:16 +0100] cupsdReadClient: 11 GET /images/cups-icon.png HTTP/1.1 D [25/Jan/2010:08:57:16 +0100] cupsdSetBusyState: Active clients D [25/Jan/2010:08:57:16 +0100] cupsdAuthorize: No authentication data provided. D [25/Jan/2010:08:57:16 +0100] cupsdReadClient: 11 Closing on EOF D [25/Jan/2010:08:57:16 +0100] cupsdCloseClient: 11 D [25/Jan/2010:08:57:16 +0100] cupsdSetBusyState: Not busy D [25/Jan/2010:08:57:16 +0100] cupsdWriteClient: 1354538648 Closing on unknown HTTP state 0 D [25/Jan/2010:08:57:16 +0100] cupsdCloseClient: 1354538648 How to reproduce: 0) Make sure you have session restore activated. Make sure your favorite browser is set to restore the last session on reload. 1) Load http://localhost:631/admin in your favorite browser. 2) Restart your computer. 3) Log in to your desktop environment. Expected result: The CUPS administration window should be loaded in your browser. Actual result: The CUPS administration window fails to load. The browser says: The connection to the server was reset while the page was loading. It is not consistently reproducible, but I would say I see a failure rate of 80 %. It happens on both of my test machines. ProblemType: Bug Architecture: amd64 Date: Mon Jan 25 09:00:30 2010 DistroRelease: Ubuntu 10.04 EcryptfsInUse: Yes InstallationMedia: Ubuntu 9.10 Karmic Koala - Release amd64 (20091027) Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No destinations added. MachineType: LG Electronics P300-T.APE4V NonfreeKernelModules: nvidia Package: cups 1.4.2-6 Papersize: letter ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-11-generic root=UUID=01ebab7a-379c-48c8-87d6-a2800f6dccfd ro quiet splash ProcVersionSignature: Ubuntu 2.6.32-11.15-generic SourcePackage: cups Uname: Linux 2.6.32-11-generic x86_64 dmi.bios.date: 06/30/2008 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: ELGNSF18 dmi.board.name: ELGON dmi.board.vendor: LG Electronics dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LG Electronics dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvrELGNSF18:bd06/30/2008:svnLGElectronics:pnP300-T.APE4V:pvrNotApplicable:rvnLGElectronics:rnELGON:rvrNotApplicable:cvnLGElectronics:ct10:cvrN/A: dmi.product.name: P300-T.APE4V dmi.product.version: Not Applicable dmi.sys.vendor: LG Electronics To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/512220/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1302416] [NEW] deja-dup monitor was taking 6GB of memory
Public bug reported: Booted fresh, computer started to be slow and after a while i realized deja-dup monitor was taking 6GB of memory. Haven't tried rebooted again. Will do so in a moment. Sorry can't provide more info :/ ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: deja-dup 30.0-0ubuntu4 ProcVersionSignature: Ubuntu 3.13.0-22.44-generic 3.13.8 Uname: Linux 3.13.0-22-generic x86_64 ApportVersion: 2.14-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Fri Apr 4 09:40:07 2014 InstallationDate: Installed on 2011-11-21 (864 days ago) InstallationMedia: Kubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012) ProcEnviron: LANGUAGE=ca_ES TERM=xterm PATH=(custom, no user) LANG=ca_ES.UTF-8 SHELL=/bin/bash SourcePackage: deja-dup UpgradeStatus: Upgraded to trusty on 2012-02-27 (766 days ago) ** Affects: deja-dup (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to deja-dup in Ubuntu. https://bugs.launchpad.net/bugs/1302416 Title: deja-dup monitor was taking 6GB of memory Status in “deja-dup” package in Ubuntu: New Bug description: Booted fresh, computer started to be slow and after a while i realized deja-dup monitor was taking 6GB of memory. Haven't tried rebooted again. Will do so in a moment. Sorry can't provide more info :/ ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: deja-dup 30.0-0ubuntu4 ProcVersionSignature: Ubuntu 3.13.0-22.44-generic 3.13.8 Uname: Linux 3.13.0-22-generic x86_64 ApportVersion: 2.14-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Fri Apr 4 09:40:07 2014 InstallationDate: Installed on 2011-11-21 (864 days ago) InstallationMedia: Kubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012) ProcEnviron: LANGUAGE=ca_ES TERM=xterm PATH=(custom, no user) LANG=ca_ES.UTF-8 SHELL=/bin/bash SourcePackage: deja-dup UpgradeStatus: Upgraded to trusty on 2012-02-27 (766 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/deja-dup/+bug/1302416/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1302374] Re: No sound after upgrade packages and dist
Yup, got that too. It's fixed in systemd 204-5ubuntu17. ** Changed in: pulseaudio (Ubuntu) Status: Confirmed = Fix Released ** Package changed: pulseaudio (Ubuntu) = systemd (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1302374 Title: No sound after upgrade packages and dist Status in “systemd” package in Ubuntu: Fix Released Bug description: Hi. I upgrade packages in the morning, next upgrade kernel (dist-upgrade) and after restart i have no sound, no tray sound icon. Below history what I'm done: Start-Date: 2014-04-04 08:02:30 Commandline: apt-get upgrade Upgrade: apt:amd64 (0.9.15.4ubuntu2, 0.9.15.4ubuntu3), kerneloops-daemon:amd64 (0.12+git20090217-3ubuntu7, 0.12+git20090217-3ubuntu8), libfontembed1:amd64 (1.0.50-0ubuntu1, 1.0.51-0ubuntu1), libgdiplus:amd64 (2.11+git20131008.9732566-4ubuntu1, 2.11+git20131008.9732566-5ubuntu1), libgail-3-0:amd64 (3.10.7-0ubuntu4, 3.10.7-0ubuntu5), python-samba:amd64 (4.1.3+dfsg-2ubuntu5, 4.1.6+dfsg-1ubuntu1), apt-transport-https:amd64 (0.9.15.4ubuntu2, 0.9.15.4ubuntu3), libindicator3-7:amd64 (12.10.2+14.04.20140304-0ubuntu1, 12.10.2+14.04.20140402-0ubuntu1), libphonon4:amd64 (4.7.1-0ubuntu7, 4.7.1-0ubuntu8), language-pack-pl:amd64 (14.04+20140321, 14.04+20140401), gsettings-ubuntu-schemas:amd64 (0.0.1+14.04.20140224-0ubuntu1, 0.0.1+14.04.20140401-0ubuntu1), phonon:amd64 (4.7.1-0ubuntu7, 4.7.1-0ubuntu8), gir1.2-packagekitglib-1.0:amd64 (0.8.12-1ubuntu4, 0.8.12-1ubuntu5), gir1.2-gtk-3.0:amd64 (3.10.7-0ubuntu4, 3.10.7-0ubuntu5), apt-utils:amd64 (0.9.15.4ubuntu2, 0.9.15.4ubuntu3), ubuntu-minimal:amd64 (1.322, 1.324), plymouth-theme-ubuntu-text:amd64 (0.8.8-0ubuntu15, 0.8.8-0ubuntu16), parted:amd64 (2.3-17, 2.3-18), libgudev-1.0-0:amd64 (204-5ubuntu13, 204-5ubuntu16), python-apt:amd64 (0.9.3.4build1, 0.9.3.5), command-not-found:amd64 (0.3ubuntu10, 0.3ubuntu12), tzdata-java:amd64 (2014a-1, 2014b-1), file:amd64 (5.14-2ubuntu2, 5.14-2ubuntu3), libmagic1:amd64 (5.14-2ubuntu2, 5.14-2ubuntu3), python3-commandnotfound:amd64 (0.3ubuntu10, 0.3ubuntu12), libglib2.0-0:amd64 (2.40.0-1ubuntu1, 2.40.0-2), libapt-inst1.5:amd64 (0.9.15.4ubuntu2, 0.9.15.4ubuntu3), libnss3-1d:amd64 (3.15.4-1ubuntu6, 3.15.4-1ubuntu7), libgtk-3-bin:amd64 (3.10.7-0ubuntu4, 3.10.7-0ubuntu5), libbluetooth3:amd64 (4.101-0ubuntu10, 4.101-0ubuntu11), bluez-cups:amd64 (4.101-0ubuntu10, 4.101-0ubuntu11), plymouth:amd64 (0.8.8-0ubuntu15, 0.8.8-0ubuntu16), libnss3-nssdb:amd64 (3.15.4-1ubuntu6, 3.15.4-1ubuntu7), ubuntu-standard:amd64 (1.322, 1.324), libglib2.0-data:amd64 (2.40.0-1ubuntu1, 2.40.0-2), bluez-alsa:amd64 (4.101-0ubuntu10, 4.101-0ubuntu11), gir1.2-gudev-1.0:amd64 (204-5ubuntu13, 204-5ubuntu16), indicator-application:amd64 (12.10.1+14.04.20140324-0ubuntu1, 12.10.1+14.04.20140402-0ubuntu1), samba-common-bin:amd64 (4.1.3+dfsg-2ubuntu5, 4.1.6+dfsg-1ubuntu1), cups-browsed:amd64 (1.0.50-0ubuntu1, 1.0.51-0ubuntu1), libparted0debian1:amd64 (2.3-17, 2.3-18), python-commandnotfound:amd64 (0.3ubuntu10, 0.3ubuntu12), cups-filters-core-drivers:amd64 (1.0.50-0ubuntu1, 1.0.51-0ubuntu1), language-pack-gnome-en:amd64 (14.04+20140321, 14.04+20140401), xfdesktop4-data:amd64 (4.11.4-1ubuntu2, 4.11.5-0ubuntu1), acpid:amd64 (2.0.21-1ubuntu1, 2.0.21-1ubuntu2), ubuntu-sso-client:amd64 (13.10-0ubuntu4, 13.10-0ubuntu5), command-not-found-data:amd64 (0.3ubuntu10, 0.3ubuntu12), samba-libs:amd64 (4.1.3+dfsg-2ubuntu5, 4.1.6+dfsg-1ubuntu1), libapt-pkg4.12:amd64 (0.9.15.4ubuntu2, 0.9.15.4ubuntu3), python3-apt:amd64 (0.9.3.4build1, 0.9.3.5), libgtk-3-0:amd64 (3.10.7-0ubuntu4, 3.10.7-0ubuntu5), bluez:amd64 (4.101-0ubuntu10, 4.101-0ubuntu11), libnss3:amd64 (3.15.4-1ubuntu6, 3.15.4-1ubuntu7), indicator-sound:amd64 (12.10.2+14.04.20140324.is.12.10.2+14.04.20140320-0ubuntu1, 12.10.2+14.04.20140401-0ubuntu1), apache2-data:amd64 (2.4.7-1ubuntu3, 2.4.7-1ubuntu4), python-smbc:amd64 (1.0.13-0ubuntu6, 1.0.14.1-0ubuntu2), cups-filters:amd64 (1.0.50-0ubuntu1, 1.0.51-0ubuntu1), libplymouth2:amd64 (0.8.8-0ubuntu15, 0.8.8-0ubuntu16), unity-settings-daemon:amd64 (14.04.0+14.04.20140310-0ubuntu2, 14.04.0+14.04.20140402-0ubuntu1), smbclient:amd64 (4.1.3+dfsg-2ubuntu5, 4.1.6+dfsg-1ubuntu1), lightdm:amd64 (1.9.13-0ubuntu1, 1.9.14-0ubuntu1), libgtk-3-common:amd64 (3.10.7-0ubuntu4, 3.10.7-0ubuntu5), language-pack-gnome-pl:amd64 (14.04+20140321, 14.04+20140401), python-ubuntu-sso-client:amd64 (13.10-0ubuntu4, 13.10-0ubuntu5), liblightdm-gobject-1-0:amd64 (1.9.13-0ubuntu1, 1.9.14-0ubuntu1), xfdesktop4:amd64 (4.11.4-1ubuntu2, 4.11.5-0ubuntu1), xserver-xorg-video-sis:amd64 (0.10.7-0ubuntu5, 0.10.7-0ubuntu6), apache2:amd64 (2.4.7-1ubuntu3, 2.4.7-1ubuntu4), tzdata:amd64 (2014a-1, 2014b-1), libglib2.0-bin:amd64 (2.40.0-1ubuntu1, 2.40.0-2), apache2-bin:amd64 (2.4.7-1ubuntu3, 2.4.7-1ubuntu4), libwbclient0:amd64 (4.1.3+dfsg-2ubuntu5, 4.1.6+dfsg-1ubuntu1),
[Desktop-packages] [Bug 1298740] Re: unity-settings-daemon warns when IBus engine layout is default
Rolf, Calm down. No living man all things can. And IM/I18N are enough complicated, there's no need to haggle. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1298740 Title: unity-settings-daemon warns when IBus engine layout is default Status in Unity Settings Daemon: In Progress Status in “unity-settings-daemon” package in Ubuntu: Confirmed Bug description: To reproduce: Add Russian keyboard layout and Chinese (Pinyin or Intelligent Pinyin) input method. Switch to Russian layout. Switch to Chinese IM. Try to input pinyin, result is still Cyrillic characters. unity-settings-daemon emits the following warning: (unity-settings-daemon:14828): keyboard-plugin-WARNING **: Couldn't upload new XKB keyboard description Some IBus engines were updated to have a layout of default rather than us, and xkb doesn't accept it as a possible layout from /usr/share/X11/xkb/rules/evdev. To manage notifications about this bug go to: https://bugs.launchpad.net/unity-settings-daemon/+bug/1298740/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1218322] Re: Can't set keyboard layout change to alt+shift, ctrl+shift, etc.
Ubuntu 14.04, 64 bit, upgrade from 13.10. After latest update network manager and hotkeys stopped working but layout is switching correctly! :-) Alt+Shift is working and NumLock indicator does not turn off every time i'm pressing these buttons. But one new thing appeared: when i'm pressing Alt+Shift or Tab buttons, there is a pause, i think, 2 seconds, before layout is switching. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1218322 Title: Can't set keyboard layout change to alt+shift, ctrl+shift, etc. Status in Gnome Settings Daemon: Invalid Status in Ubuntu GNOME: Confirmed Status in “gnome-control-center” package in Ubuntu: Fix Released Status in “gnome-settings-daemon” package in Ubuntu: Triaged Status in “gnome-settings-daemon” source package in Saucy: Triaged Status in “gnome-control-center” package in ALT Linux: Unknown Status in “gnome-control-center” package in Baltix: Confirmed Status in “gnome-control-center” package in Gentoo Linux: Invalid Status in “gnome-control-center” package in Mandriva: Invalid Bug description: *** The old PPA, ppa:attente/1218322 is superceded by the following one. You can remove the old repository using ppa-purge. *** A PPA which should provide some relief for this issue is available at https://launchpad.net/~attente/+archive/modifier-only-input-switch. To install: sudo add-apt-repository ppa:attente/modifier-only-input-switch sudo apt-get update sudo apt-get upgrade (log out, log in) If the packages improve the situation for you, you can pin them using: sudo apt-mark hold compiz sudo apt-mark hold gnome-settings-daemon sudo apt-mark hold unity If the packages don't work for you, you can purge them using: sudo ppa-purge ppa:attente/modifier-only-input-switch === compiz === Impact: modifier-only key bindings need to be independent of key-press order, there's no support for double tapping two modifier keys of the same type Test case: - add at least two input sources through gnome-control-center's text entry settings - use gsettings to set the input switching shortcut to ctrl+left shift: gsettings set org.gnome.desktop.wm.keybindings switch-input-source ['PrimaryShift_L'] - holding left shift, press and release ctrl - the current input source should change Regression potential: possible, but highly unlikely, that some key bindings may be triggered due to the removal of some code that would normally prevent a possible tap from occurring. === unity === Impact: gnome-settings-daemon eats modifier-only shortcuts preventing them from propagating down to applications Test case: - open gnome-control-center's text input settings - set the next input source key binding to ctrl+left shift - open gnome-terminal - press ctrl+shift+t - gnome-terminal should open a new tab Regression potential: the additional input switch key bindings could collide with other functionality such as opening the dash or hud === gnome-control-center === Impact: the UI to change the layout switching keys doesn't work Test case: - open gnome-control-center's text input settings - click on the next layout key entry - try entering a key combinaison (e.g ctrl-space) - the UI should reflect the new keys Regression potential: that UI was not working before, it should only be an improvement (some key combos are not working as expected, that's another issue and shouldn't be mixed with this one) === gnome-settings-daemon === Impact: attempting to change keyboard layouts using only modifier keys doesn't work Test case: - add at least two input sources through gnome-control-center's text entry settings - use gsettings to set the input switching shortcut to ctrl+left shift: gsettings set org.gnome.desktop.wm.keybindings switch-input-source ['PrimaryShift_L'] - press and release ctrl+left shift - the current input source should change Regression potential: The input switching shortcut might capture other non-modifier shortcuts, but users will need to consider this when choosing their switching shortcut anyways. For users this bug affects, this represents a working solution for a critical bug. -- Test results for different keyboard layout change hotkeys may be viewed and added in the Google Docs table, created by Norbert (https://docs.google.com/spreadsheet/ccc?key=0Ao5e713Ig9g_dEJrX2NRYlpLWWVzSWxsVXU4ck9HYVEusp=sharing). -- Recent discovered bugs related to keyboard layouts: * keyboard layout settings must be consistent between gnome-control-center keyboard, indicator-keyboard and gnome-tweak-tool and /etc/default/keyboard (bug 1270574) * Ubuntu 14.04 should have gnome-tweak-tool installed by default because of many settings that are missed
[Desktop-packages] [Bug 1302353] Re: regression: ibus ignores keyboard layout
** Changed in: unity-settings-daemon (Ubuntu) Assignee: (unassigned) = William Hua (attente) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1302353 Title: regression: ibus ignores keyboard layout Status in “ibus” package in Ubuntu: Incomplete Status in “unity-settings-daemon” package in Ubuntu: Triaged Bug description: The recent update of unity packages introduced a bad regression for ibus users. I assume the fault lies with unity since ibus hasn't been updated for several weeks and my machine was fine until about two days ago around which time some unity updates rolled in. I have a German keyboard layout (QWERTZ not QWERTY as in the US case). I use anthy and mozc for Japanese input. Since two days ago the default layout with the Japanese IME are a US layout throwing me off when blind-typing. To look into the matter, I opened ibus-setup and there are three Input methods listed there: English - English (US), Japanese - Anthy and Japanese -Mozc. German was conspicuously absent . I eventually managed to add a German layout to it and delete the US layout. I then restart ibus with ibus restart only to find the US keyboard layout not only back but it's default again. Argh! In other words, the explicit choice I'm trying to force doesn't stick. There are four keyboard layouts currently defined in System Settings - Text Entry - Input sources to use, none of them have anything to do with a US-layout; de1, de2, anthy and mozc. I cycle through them via Super+Space. Anthy is set to use the system default layout. The regression is that it currently inists on US layout with no way to even override this silly choice. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1302353/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1294311] Re: Compiz process continuously uses too much cpu.
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: compiz (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to compiz in Ubuntu. https://bugs.launchpad.net/bugs/1294311 Title: Compiz process continuously uses too much cpu. Status in “compiz” package in Ubuntu: Confirmed Bug description: cpu = AMD Athlon(tm) 64 X2 Dual Core Processor 4600+ ram = 6GB uname -r Linux 3.13.0-17-generic #37-Ubuntu SMP Mon Mar 10 21:44:01 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux lsb_release -rd Description: Ubuntu Trusty Tahr (development branch) Release: 14.04 apt-cache policy compiz compiz: Instaŀlat: 1:0.9.11+14.04.20140310-0ubuntu1 Candidat: 1:0.9.11+14.04.20140310-0ubuntu1 Taula de versió: *** 1:0.9.11+14.04.20140310-0ubuntu1 0 500 http://es.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages 100 /var/lib/dpkg/status Compiz proces is always using too much cpu. Some examples: - When I use ALT+F2 and I type something compiz uses 170% cpu. - When I use ALT+TAB compiz uses 120% cpu. - While I'm writing this text compiz is using 30% cpu - My system running only a terminal with top but compiz using 12% cpu ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: compiz-core 1:0.9.11+14.04.20140310-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-17.37-generic 3.13.6 Uname: Linux 3.13.0-17-generic x86_64 .tmp.unity.support.test.1: ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Tue Mar 18 20:01:47 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu EcryptfsInUse: Yes ExecutablePath: /usr/bin/compiz GraphicsCard: NVIDIA Corporation G72 [GeForce 7200 GS / 7300 SE] [10de:01d3] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ZOTAC International (MCO) Ltd. Device [19da:5001] InstallationDate: Installed on 2014-03-17 (1 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140317) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: MSI MS-7369 ProcEnviron: LANGUAGE=ca PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=ca_ES.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-17-generic root=UUID=65b6b4ee-5d53-4762-8b40-e5d13e0035c3 ro quiet splash vt.handoff=7 SourcePackage: compiz UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/17/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V2.9 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: MS-7369 dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV2.9:bd03/17/2009:svnMSI:pnMS-7369:pvr1.0:rvnMSI:rnMS-7369:rvr1.0:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: MS-7369 dmi.product.version: 1.0 dmi.sys.vendor: MSI version.compiz: compiz 1:0.9.11+14.04.20140310-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-1ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.15.0-1ubuntu7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Tue Mar 18 19:55:32 2014 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputAT Translated Set 2 keyboard KEYBOARD, id 8 inputImPS/2 Generic Wheel Mouse MOUSE, id 9 xserver.errors: Failed to load module nvidia (module does not exist, 0) Failed to load module nvidia (module does not exist, 0) xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.15.0-1ubuntu7 xserver.video_driver: nouveau To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/1294311/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe :
[Desktop-packages] [Bug 883319]
For well over a week I've been first testing the success of panning for various combinations of gfxcard, monitor and fb size in servers prior to the changes resulting in this bug report and then same for installations to which I've updated using the 94929 patch applied by Tobias Klausmann in the openSUSE build-service. Initially the only recording I did of my testing I reported here. After while I began recording in the form of screenshots accompanied by the Xorg.#.log associated with each one. These are available for perusal at http://fm.no-ip.com/SS/Xorg/ . Among them is one instance of a scaling test, 1.2x1.2 applied to a 1440x900 screen. The largest fb size I tested was 3840x2400. The newest gfxchip used was a Intel 4000 series (G41). Others used are nv11, G84, rv200, rv250, rv380, i865G, i915G i945G. The highest resolution used was 1920x1080. Total success pairs there currently is 31, of which 14 are pre-bug and 17 are server 1.16rc1. KDE3 KDE4 dominate the DEs represented. A few are IceWM and Lxde. The only outright failure so far was on i945G and 1.16rc1 on both openSUSE 13.1 13.2, but after another system/xorg updates round those inexplicable failures apparently solved themselves. Among the overwhelming number of successes are many instances of various forms of painting and mouse pointer trouble among the configurations with the largest panning areas that always goes away if panning is disabled. However, such problems are common to both old servers and DEs as well as current ones. The painting problems don't show up in any of the screenshots. Except for the comment 44 reported failure of xorg.conf* to produce expected results, WRT to bounds and sizes at least, the 94929 patch seems to be doing what it needs to do. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/883319 Title: xrandr --scale restricts area in which mouse moves Status in X.Org X server: Confirmed Status in “xorg-server” package in Ubuntu: Fix Released Status in “xorg-server” source package in Precise: Fix Released Status in “xorg-server” source package in Quantal: Fix Released Status in “xorg-server” source package in Raring: Fix Released Bug description: SRU Request: [IMPACT] A bug in the version of xorg-server in precise prevents users from scaling screen resolution. When attempting to do so, as was possible in Natty and earlier, and which is possible in Quantal+, the mouse pointer remains locked inside the old resolution. This prevents users of small screens such as netbooks from scaling to a greater screen resolution. [Test Case] - On a netbook with intel chipset, such as a Dell Mini 9 or 10, scale the display by using the following command: xrandr --output LVDS1 --panning 1280x750 --scale 1.25x1.25 See if the mouse moves correctly to all screen extremities, and is not confined by a transparent border at 1024x600 [Regression Potential] This is fixed with a patch backported from the xorg-server version in Quantal. In theory it should just affect screen which are scaled and panned, which is uncommon. If so, the patch can be backed out. Original Bug Description: in kubuntu (and ubuntu) 11.04 i used to enlarge my laptop screen like so xrandr --output LVDS1 --scale 1.2x1.2 this worked fine: the desktop scaled to larger size correctly . After upgrading to 11.10, in kde the desktop still resizes correctly, but the movement of the mouse is restricted to an area equal to the screen size *before* issuing the scaling command. .. Ie let's say the mode is 1366x768 and I do xrandr --output LVDS1 --scale 1.2x1.2 the screen size changes to 1640x922 but the mouse moves in an area the size of 1366x768 in the top left of the screen and then 'hits a wall' preventing it to move. I also tried ubuntu 11.10 with gnome: here the screen also resizes, but I have the same issue with the mouse, and the extended area of the desktop is black... Some time ago there was a similar issue, which was resolved later. Now it seems to be back... jos@samsungsucks:~$ lsb_release -rd Description:Ubuntu 11.10 Release:11.10 jos@samsungsucks:~$ xrandr --version xrandr program version 1.3.5 Server reports RandR version 1.3 To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/883319/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 881046]
For well over a week I've been first testing the success of panning for various combinations of gfxcard, monitor and fb size in servers prior to the changes resulting in this bug report and then same for installations to which I've updated using the 94929 patch applied by Tobias Klausmann in the openSUSE build-service. Initially the only recording I did of my testing I reported here. After while I began recording in the form of screenshots accompanied by the Xorg.#.log associated with each one. These are available for perusal at http://fm.no-ip.com/SS/Xorg/ . Among them is one instance of a scaling test, 1.2x1.2 applied to a 1440x900 screen. The largest fb size I tested was 3840x2400. The newest gfxchip used was a Intel 4000 series (G41). Others used are nv11, G84, rv200, rv250, rv380, i865G, i915G i945G. The highest resolution used was 1920x1080. Total success pairs there currently is 31, of which 14 are pre-bug and 17 are server 1.16rc1. KDE3 KDE4 dominate the DEs represented. A few are IceWM and Lxde. The only outright failure so far was on i945G and 1.16rc1 on both openSUSE 13.1 13.2, but after another system/xorg updates round those inexplicable failures apparently solved themselves. Among the overwhelming number of successes are many instances of various forms of painting and mouse pointer trouble among the configurations with the largest panning areas that always goes away if panning is disabled. However, such problems are common to both old servers and DEs as well as current ones. The painting problems don't show up in any of the screenshots. Except for the comment 44 reported failure of xorg.conf* to produce expected results, WRT to bounds and sizes at least, the 94929 patch seems to be doing what it needs to do. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/881046 Title: Panning in a virtual monitor is not possible after upgrade to Ubuntu 11.10 Status in X.Org X server: Confirmed Status in “xorg-server” package in Ubuntu: Triaged Status in “xorg-server” source package in Precise: Triaged Bug description: When I go for a virtual monitor by issuing command xrandr --output LVDS1 --fb 1600x1200 --panning 1600x1200 on a monitor working at resolution 1024x768 (as I did before upgrading from Ubuntu 11.04 to Ubuntu 11.10), the WM bars on top and left side of the screen (in Unity) look like extending to the new area, but I cannot move the pointer to the new extra area and so I cannot pan. As far as I understood by reading around, this *could* be a bug in package xorg- server rather than in xrandr and *could* be related to the boundaries set for cursor position. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: xorg 1:7.6+7ubuntu7 ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4 Uname: Linux 3.0.0-12-generic i686 .tmp.unity.support.test.0: ApportVersion: 1.23-0ubuntu3 Architecture: i386 CompizPlugins: [core,bailer,detection,composite,opengl,decor,mousepoll,vpswitch,regex,animation,snap,expo,move,compiztoolbox,place,grid,imgpng,gnomecompat,wall,ezoom,workarounds,staticswitcher,resize,fade,unitymtgrabhandles,scale,session,unityshell] CompositorRunning: compiz Date: Mon Oct 24 20:40:14 2011 DistUpgraded: Log time: 2011-10-22 12:17:44.515205 DistroCodename: oneiric DistroVariant: ubuntu DkmsStatus: dahdi, 2.4.1+dfsg-1ubuntu2, 2.6.38-11-generic, i686: installed (WARNING! Diff between built and installed module!) dahdi, 2.4.1+dfsg-1ubuntu2, 3.0.0-12-generic, i686: installed (WARNING! Diff between built and installed module!) dahdi, 2.4.1+dfsg-1ubuntu2, 3.0.0-12-virtual, i686: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Mobile 915GM/GMS/910GML Express Graphics Controller [8086:2592] (rev 03) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0182] Subsystem: Dell Device [1028:0182] MachineType: Dell Inc. Latitude D610 PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: 3.3V 32-bit PC Card ProcEnviron: SHELL=/bin/bash PATH=(custom, no user) LANG=it_IT.UTF-8 LANGUAGE=it_IT:it:en_GB:en ProcKernelCmdLine: root=UUID=35d17829-2597-405b-afdd-6b1d94a4dedd ro quiet splash rootdelay=15 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to oneiric on 2011-10-22 (2 days ago) dmi.bios.date: 03/02/2005 dmi.bios.vendor: Dell Inc. dmi.bios.version: A03 dmi.board.name: 0D4571 dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA03:bd03/02/2005:svnDellInc.:pnLatitudeD610:pvr:rvnDellInc.:rn0D4571:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: Latitude D610 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.6+bzr20110929-0ubuntu3 version.libdrm2: libdrm2 2.4.26-1ubuntu1
[Desktop-packages] [Bug 1298611] Re: [FFe] apparmor signal and ptrace mediation
This bug was fixed in the package apparmor-easyprof-ubuntu - 1.1.14 --- apparmor-easyprof-ubuntu (1.1.14) trusty; urgency=medium * 1.1/webview: update for ptrace and signal mediation (LP: #1298611) * debian/control: Depends on apparmor = 2.8.95~2430-0ubuntu4 -- Jamie Strandboge ja...@ubuntu.com Thu, 03 Apr 2014 15:19:23 -0500 ** Changed in: apparmor-easyprof-ubuntu (Ubuntu) Status: New = Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1298611 Title: [FFe] apparmor signal and ptrace mediation Status in “apparmor” package in Ubuntu: Fix Released Status in “apparmor-easyprof-ubuntu” package in Ubuntu: Fix Released Status in “libvirt” package in Ubuntu: Fix Released Status in “lightdm” package in Ubuntu: Fix Released Status in “linux” package in Ubuntu: Fix Released Status in “lxc” package in Ubuntu: Fix Released Bug description: Background: kernel and apparmor userspace updates to support signal and ptrace mediation. These packages are listed in one bug because they are related, but the FFes may be granted and the uploads may happen at different times. = linux = Summary: This feature freeze exception is requested for signal and ptrace mediation via apparmor in the kernel. When used with a compatible apparmor userspace, signals and ptrace rules are supported. When used without a compatible apparmor userspace (eg, on a precise system with a trusty backport kernel), signal and ptrace mediation is not enforced (ie, you can use this kernel with an old userspace without any issues). The fine grained mediation of signals and ptraces also incorporates improved versioning support that allows this kernel to better support older and newer userspaces. This allows for this version of the kernel to work as a backport kernel unmodified (currently a patch and config are used to provide backport kernels). The kernel patch is available at git://kernel.ubuntu.com/jj/ubuntu-trusty.git in the trusty-alpha6 branch apparmor-alpha6-sync Testing: * 12.04 system with backported kernel: DONE * test-apparmor.py: PASS (runs extensive tests (upstream and distro)) * exploratory manual testing: PASS (networking, aa-enforce with firefox, firefox works, apparmor blocks access, etc) * aa-status: PASS * lxc: PASS (containers can be created, started, shutdown) * libvirt: PASS (VMs started via openstack, and test-libvirt.py from QRT passes all tests) * 14.04 system (non-Touch) with current apparmor userspace: DONE (relevant parts of https://wiki.ubuntu.com/Process/Merges/TestPlans/AppArmor) * test-apparmor.py: PASS (runs extensive tests (upstream and distro)) * exploratory manual testing: PASS (networking, aa-enforce with firefox, firefox works, apparmor blocks access, etc) * aa-status: PASS * lxc: PASS (containers can be created, started, shutdown) * libvirt: PASS (QRT/script/test-libvirt.py (though there are 3 failures unrelated to apparmor)) * click-apparmor QRT touch image tests: PASS * apparmor-easyprof-ubuntu QRT touch image tests: PASS * 14.04 system (non-Touch) with updated apparmor userspace capable of supporting signal and ptrace mediation: DONE (relevant parts of https://wiki.ubuntu.com/Process/Merges/TestPlans/AppArmor. Note: this is marked 'done' from the kernel perspective-- the apparmor userspace upload is being prepared and tests assume userspace is using latest patches on the list) * test-apparmor.py: PASS (runs extensive tests (upstream and distro)) * exploratory manual testing: PASS (networking, aa-enforce with firefox, firefox works, apparmor blocks access, etc) * aa-status: PASS * lxc: PASS (containers can be created, started, shutdown) * libvirt: PASS (QRT/script/test-libvirt.py (though there are 3 failures unrelated to apparmor)) * click-apparmor QRT touch image tests: PASS * apparmor-easyprof-ubuntu QRT touch image tests: PASS Justification: This feature is required to support comprehensive application confinement on Ubuntu Touch. This feature adds a significant security benefit to libvirt's qemu guest isolation which is fundamental to Ubuntu on Server/Cloud. This feature also adds a welcome improvement to administrators wishing to further protect their systems. = apparmor userspace = Summary: This feature freeze exception is requested for signal and ptrace mediation for apparmor userspace. When used with a compatible kernel, signals and ptrace rules are supported. When used without a compatible kernel (eg, on Ubuntu Touch for a few weeks or with upstream kernels), signal and ptrace rules are skipped (ie, you can use this userspace with other kernels without issue). Testing: * 14.04 system with current kernel (Touch, kernel doesn't have signal and ptrace mediation yet): *
[Desktop-packages] [Bug 1298611] Re: [FFe] apparmor signal and ptrace mediation
This bug was fixed in the package lxc - 1.0.2-0ubuntu2 --- lxc (1.0.2-0ubuntu2) trusty; urgency=medium * updates for AppArmor signal and ptrace mediation (LP: #1298611) - debian/patches/apparmor-signal-ptrace.patch: add signal and ptrace rules to abstractions/container-base and abstractions/start-container - debian/rules: remove signal and ptrace rules for Ubuntu releases earlier than 14.04 LTS -- Jamie Strandboge ja...@ubuntu.com Thu, 03 Apr 2014 07:06:56 -0500 ** Changed in: lxc (Ubuntu) Status: New = Fix Released ** Changed in: apparmor (Ubuntu) Status: Confirmed = Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1298611 Title: [FFe] apparmor signal and ptrace mediation Status in “apparmor” package in Ubuntu: Fix Released Status in “apparmor-easyprof-ubuntu” package in Ubuntu: Fix Released Status in “libvirt” package in Ubuntu: Fix Released Status in “lightdm” package in Ubuntu: Fix Released Status in “linux” package in Ubuntu: Fix Released Status in “lxc” package in Ubuntu: Fix Released Bug description: Background: kernel and apparmor userspace updates to support signal and ptrace mediation. These packages are listed in one bug because they are related, but the FFes may be granted and the uploads may happen at different times. = linux = Summary: This feature freeze exception is requested for signal and ptrace mediation via apparmor in the kernel. When used with a compatible apparmor userspace, signals and ptrace rules are supported. When used without a compatible apparmor userspace (eg, on a precise system with a trusty backport kernel), signal and ptrace mediation is not enforced (ie, you can use this kernel with an old userspace without any issues). The fine grained mediation of signals and ptraces also incorporates improved versioning support that allows this kernel to better support older and newer userspaces. This allows for this version of the kernel to work as a backport kernel unmodified (currently a patch and config are used to provide backport kernels). The kernel patch is available at git://kernel.ubuntu.com/jj/ubuntu-trusty.git in the trusty-alpha6 branch apparmor-alpha6-sync Testing: * 12.04 system with backported kernel: DONE * test-apparmor.py: PASS (runs extensive tests (upstream and distro)) * exploratory manual testing: PASS (networking, aa-enforce with firefox, firefox works, apparmor blocks access, etc) * aa-status: PASS * lxc: PASS (containers can be created, started, shutdown) * libvirt: PASS (VMs started via openstack, and test-libvirt.py from QRT passes all tests) * 14.04 system (non-Touch) with current apparmor userspace: DONE (relevant parts of https://wiki.ubuntu.com/Process/Merges/TestPlans/AppArmor) * test-apparmor.py: PASS (runs extensive tests (upstream and distro)) * exploratory manual testing: PASS (networking, aa-enforce with firefox, firefox works, apparmor blocks access, etc) * aa-status: PASS * lxc: PASS (containers can be created, started, shutdown) * libvirt: PASS (QRT/script/test-libvirt.py (though there are 3 failures unrelated to apparmor)) * click-apparmor QRT touch image tests: PASS * apparmor-easyprof-ubuntu QRT touch image tests: PASS * 14.04 system (non-Touch) with updated apparmor userspace capable of supporting signal and ptrace mediation: DONE (relevant parts of https://wiki.ubuntu.com/Process/Merges/TestPlans/AppArmor. Note: this is marked 'done' from the kernel perspective-- the apparmor userspace upload is being prepared and tests assume userspace is using latest patches on the list) * test-apparmor.py: PASS (runs extensive tests (upstream and distro)) * exploratory manual testing: PASS (networking, aa-enforce with firefox, firefox works, apparmor blocks access, etc) * aa-status: PASS * lxc: PASS (containers can be created, started, shutdown) * libvirt: PASS (QRT/script/test-libvirt.py (though there are 3 failures unrelated to apparmor)) * click-apparmor QRT touch image tests: PASS * apparmor-easyprof-ubuntu QRT touch image tests: PASS Justification: This feature is required to support comprehensive application confinement on Ubuntu Touch. This feature adds a significant security benefit to libvirt's qemu guest isolation which is fundamental to Ubuntu on Server/Cloud. This feature also adds a welcome improvement to administrators wishing to further protect their systems. = apparmor userspace = Summary: This feature freeze exception is requested for signal and ptrace mediation for apparmor userspace. When used with a compatible kernel, signals and ptrace rules are supported. When used without a compatible kernel (eg, on Ubuntu Touch for a few weeks or with upstream kernels), signal and ptrace rules are skipped (ie, you can use
[Desktop-packages] [Bug 1298611] Re: [FFe] apparmor signal and ptrace mediation
This bug was fixed in the package apparmor - 2.8.95~2430-0ubuntu5
---
apparmor (2.8.95~2430-0ubuntu5) trusty; urgency=medium
* debian/control: add versioned Breaks to apparmor for lxc, libvirt-bin,
lightdm and apparmor-easyprof-ubuntu
apparmor (2.8.95~2430-0ubuntu4) trusty; urgency=medium
[ John Johansen, Steve Beattie ]
* Add userspace support for AppArmor signals and ptrace mediation
(LP: #1298611)
+ debian/patches/mediate-signals.patch,
debian/patches/change-signal-syntax.patch: Parse signal rules with
apparmor_parser. See the apparmor.d(5) man page for syntax details.
+ debian/patches/change-ptrace-syntax.patch,
debian/patches/mediate-ptrace.patch: Parse ptrace rules with
apparmor_parser. See the apparmor.d(5) man page for syntax details.
+ debian/patches/test-signal-rules.patch,
debian/patches/test-ptrace-rules.patch,
debian/patches/update-tests-for-new-semantics.patch: Update existing
tests and add new tests for signal and ptrace mediation
+ debian/patches/fix-garbage-in-preprocessor-output.patch: Fix bug causing
apparmor_parser preprocessor output to contain garbage after include
statements
+ debian/patches/fix-double-comma-in-preprocessor-output.patch: Fix bug
causing apparmor_parser preprocessor output to contain double commas
after some rules
+ debian/patches/symtab-tests-and-seenlist-bug.patch,
debian/patches/add-profile-name-variable.patch: Add ${profile_name}
variable for use in profiles when rules need to specify the current
profile's name. This is useful for signal and ptrace rules that specify
+ debian/patches/fix-names-treated-as-condlistid.patch: Fix
apparmor_parser bug that caused mount and dbus rules to fail for sets of
values
[ Jamie Strandboge ]
* debian/patches/update-base-abstraction-for-signals-and-ptrace.patch:
Adjust the base abstraction for signals and ptrace mediation. Profiles
that use the base abstraction can deny any of the granted permissions to
achieve tighter confinement.
* debian/patches/manpage-signal-ptrace.patch: Update the apparmor.d man
page to document signal rules, ptrace rules, and variables for use in
AppArmor profiles
* debian/patches/dnsmasq-libvirtd-signal-ptrace.patch: Update the dnsmasq
profile to allow libvirtd to send signals to and ptrace read the dnsmasq
process
* debian/patches/update-chromium-browser.patch: Adjust the chromium-browser
profile for permissions needed in newer chromium-browser versions and add
the rules needed for AppArmor ptrace mediation
[ Tyler Hicks ]
* Add new rule type support to aa.py to fix tracebacks when using the Python
utilities in apparmor-utils on systems with AppArmor profiles containing
previously unsupported rule types
- debian/patches/python-utils-file-support.patch: Support path rules
containing the file prefix (LP: #1295346)
- debian/patches/python-utils-signal-support.patch: Parse and write signal
rules (LP: #1300316)
- debian/patches/python-utils-ptrace-support.patch: Parse and write ptrace
rules (LP: #1300317)
- debian/patches/python-utils-pivot_root-support.patch: Parse and write
pivot_root rules (LP: #1298678)
-- Jamie Strandboge ja...@ubuntu.com Fri, 04 Apr 2014 01:07:24 -0500
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1298611
Title:
[FFe] apparmor signal and ptrace mediation
Status in “apparmor” package in Ubuntu:
Fix Released
Status in “apparmor-easyprof-ubuntu” package in Ubuntu:
Fix Released
Status in “libvirt” package in Ubuntu:
Fix Released
Status in “lightdm” package in Ubuntu:
Fix Released
Status in “linux” package in Ubuntu:
Fix Released
Status in “lxc” package in Ubuntu:
Fix Released
Bug description:
Background: kernel and apparmor userspace updates to support signal
and ptrace mediation. These packages are listed in one bug because
they are related, but the FFes may be granted and the uploads may
happen at different times.
= linux =
Summary:
This feature freeze exception is requested for signal and ptrace mediation
via apparmor in the kernel. When used with a compatible apparmor userspace,
signals and ptrace rules are supported. When used without a compatible apparmor
userspace (eg, on a precise system with a trusty backport kernel), signal and
ptrace mediation is not enforced (ie, you can use this kernel with an old
userspace without any issues).
The fine grained mediation of signals and ptraces also incorporates improved
versioning support that allows this kernel to better support older and newer
userspaces. This allows for this version of the kernel to work as a backport
kernel unmodified (currently a patch and config are used to provide backport
kernels).
The kernel patch is
[Desktop-packages] [Bug 1301720] Re: [Text Entry] There is no English input in Traditional Chinese default enviroment
Hi again! When installing Ubuntu, I usually select a Swedish keyboard layout in the installer. At first login I can instantly switch between Swedish and English (US) using Super+Space or the input source indicator. Are you saying that it does not work that way for Chinese? So if you select a Chinese input source in the installer, the English (US) option is *not* available by default at first login? In other words, you need to first go to Text Entry and select English (US) there? Btw, are you using standard Ubuntu or Ubuntu Kylin? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1301720 Title: [Text Entry] There is no English input in Traditional Chinese default enviroment Status in “unity-control-center” package in Ubuntu: Incomplete Bug description: Default settings should provie english input method even when using Traditional Chinese, since most of commands still requires to input ascii charaters. Found this issue on 14.04 beta2 with locale: LANG=zh_TW.UTF-8 LANGUAGE= LC_CTYPE=zh_TW.UTF-8 LC_NUMERIC=zh_TW.UTF-8 LC_TIME=zh_TW.UTF-8 LC_COLLATE=zh_TW.UTF-8 LC_MONETARY=zh_TW.UTF-8 LC_MESSAGES=zh_TW.UTF-8 LC_PAPER=zh_TW.UTF-8 LC_NAME=zh_TW.UTF-8 LC_ADDRESS=zh_TW.UTF-8 LC_TELEPHONE=zh_TW.UTF-8 LC_MEASUREMENT=zh_TW.UTF-8 LC_IDENTIFICATION=zh_TW.UTF-8 LC_ALL= ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity-control-center 14.04.3+14.04.20140324-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-19.40-generic 3.13.6 Uname: Linux 3.13.0-19-generic x86_64 ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 CasperVersion: 1.339 CurrentDesktop: Unity Date: Thu Apr 3 03:50:26 2014 ExecutablePath: /usr/bin/unity-control-center LiveMediaBuild: Ubuntu 14.04 LTS Trusty Tahr - Beta amd64 (20140326) ProcEnviron: TERM=xterm SHELL=/bin/bash PATH=(custom, no user) LANG=zh_TW.UTF-8 XDG_RUNTIME_DIR=set SourcePackage: unity-control-center UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_unity-control-center: activity-log-manager 0.9.7-0ubuntu12 deja-dup 29.5-0ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-control-center/+bug/1301720/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1266687] Re: Super+Space can not be used for switching keyboard layouts
Same here, though it doesn't not work in the logout screen. So if you've been logged-out while using Hebrew, you can't switch back to English (to type credentials), unles using the mouse/menu. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1266687 Title: Super+Space can not be used for switching keyboard layouts Status in “ibus” package in Ubuntu: New Bug description: Keyboard indicator does not respond to Super+Space, the default shortcut for switching to next source. Release: 13.10 Package indicator-keyboard version 0.0.0+13.10.20131010.1-0ubuntu1 I have two layouts: English (Macintosh) and Hebrew. When pressing Super+Space, I was expecting to switch back and forth between the two. Super+Space is the default short cut. When I press Super+Space, the Dash is inovked (as I guess Super itself will trigger in any case). When I change the setting for Switch to previous source as Alt+Super+Space, I can switch layouts. This is not set by default, AFAIK. NOTES: It is significantly more difficult for users to work out where to setup keyboard options now. AFAIK, i-bus is responsible for layout switching, though xkb is set for anything else? Though some of the old options are availabe now under Shortcuts setting, ie Compose etc., not everything is available. For example, remaping Caps-Lock etc. Also, there's a duplication in setting switch to next source, which can be mapped in Settings - Text Entry, and Settings - Keyboard - Shortcuts To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1266687/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1296315] Re: Displaylink and ASUS MB168B+ not working
Hi, I don't have any xorg.conf file in /etc/ and its sub dirs. So far, I didn't manage to get any positive result... Regards. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1296315 Title: Displaylink and ASUS MB168B+ not working Status in “xorg” package in Ubuntu: New Bug description: Hi, I'm trying to use an USB3 external monitor Asus MB168B+ with displaylink technology. The monitor is detected by the kernel upon plug, but no driver seems to be loaded... My notebook is an ASUS G75VW sudo dmidecode -s bios-version sudo dmidecode -s bios-release-date G75VW.223 01/07/2013 lsb_release -rd Description: Ubuntu Trusty Tahr (development branch) Release: 14.04 apt-cache policy xorg xorg: Installé : 1:7.7+1ubuntu8 Candidat : 1:7.7+1ubuntu8 Table de version : *** 1:7.7+1ubuntu8 0 500 http://ubuntu-archive.mirrors.free.org/ubuntu/ trusty/main amd64 Packages 100 /var/lib/dpkg/status uname -a Linux g75vw 3.13.0-18-generic #38-Ubuntu SMP Mon Mar 17 21:40:06 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux Mar 23 16:15:31 g75vw kernel: [13264.796466] usb 4-3: new SuperSpeed USB device number 6 using xhci_hcd Mar 23 16:15:31 g75vw kernel: [13264.812773] usb 4-3: New USB device found, idVendor=17e9, idProduct=ff03 Mar 23 16:15:31 g75vw kernel: [13264.812780] usb 4-3: New USB device strings: Mfr=1, Product=2, SerialNumber=3 Mar 23 16:15:31 g75vw kernel: [13264.812784] usb 4-3: Product: MB168B+ Mar 23 16:15:31 g75vw kernel: [13264.812787] usb 4-3: Manufacturer: DisplayLink Mar 23 16:15:31 g75vw kernel: [13264.812790] usb 4-3: SerialNumber: DALMTF151588 Mar 23 16:15:31 g75vw mtp-probe: checking bus 4, device 6: /sys/devices/pci:00/:00:14.0/usb4/4-3 Mar 23 16:15:31 g75vw mtp-probe: bus: 4, device: 6 was not an MTP device xrandr Screen 0: minimum 320 x 200, current 1920 x 1080, maximum 8192 x 8192 LVDS-1 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 382mm x 215mm 1920x1080 60.0*+ 60.0 40.0 ... VGA-1 disconnected (normal left inverted right x axis y axis) HDMI-1 disconnected (normal left inverted right x axis y axis) DP-1 disconnected (normal left inverted right x axis y axis) xrandr --listproviders Providers: number : 1 Provider 0: id: 0x65 cap: 0x1, Source Output crtcs: 2 outputs: 4 associated providers: 0 name:nouveau ls -l /dev/fb* crw-rw 1 root video 29, 0 mars 23 12:34 /dev/fb0 regards ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-18.38-generic 3.13.6 Uname: Linux 3.13.0-18-generic x86_64 ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: GNOME Date: Sun Mar 23 16:48:28 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GF114M [GeForce GTX 670M] [10de:1213] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:2119] InstallationDate: Installed on 2014-03-21 (1 days ago) InstallationMedia: Ubuntu-GNOME 14.04 Trusty Tahr - Alpha amd64 (20140226) MachineType: ASUSTeK COMPUTER INC. G75VW ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-18-generic.efi.signed root=UUID=696d83ec-abd2-47e6-bf30-ce6bd4eb1514 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/07/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: G75VW.223 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: G75VW dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrG75VW.223:bd01/07/2013:svnASUSTeKCOMPUTERINC.:pnG75VW:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG75VW:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: G75VW dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-1ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.15.0-1ubuntu7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati
[Desktop-packages] [Bug 408903] Re: Does not handle microphone mute button (KEY_MICMUTE)
** Changed in: oem-priority/precise Status: Confirmed = Won't Fix ** Changed in: oem-priority Status: Triaged = Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to x11proto-core in Ubuntu. https://bugs.launchpad.net/bugs/408903 Title: Does not handle microphone mute button (KEY_MICMUTE) Status in OEM Priority Project: Won't Fix Status in OEM Priority Project precise series: Won't Fix Status in OEM Priority Project raring series: Won't Fix Status in central project for keyboard configuration: Fix Released Status in “gnome-settings-daemon” package in Ubuntu: Triaged Status in “libx11” package in Ubuntu: Confirmed Status in “udev” package in Ubuntu: Fix Released Status in “x11proto-core” package in Ubuntu: New Status in “xkeyboard-config” package in Ubuntu: New Status in “xserver-xorg-input-evdev” package in Ubuntu: Won't Fix Status in “gnome-settings-daemon” source package in Precise: Fix Released Status in “libx11” source package in Precise: Fix Released Status in “udev” source package in Precise: Fix Released Status in “x11proto-core” source package in Precise: Fix Released Status in “xkeyboard-config” source package in Precise: Fix Released Status in “xserver-xorg-input-evdev” source package in Precise: Won't Fix Status in “gnome-settings-daemon” source package in Raring: Triaged Status in “libx11” source package in Raring: New Status in “udev” source package in Raring: Triaged Status in “x11proto-core” source package in Raring: New Status in “xkeyboard-config” source package in Raring: New Status in “xserver-xorg-input-evdev” source package in Raring: Won't Fix Bug description: [Impact] * People buying thinkpad hardware are not able to use a mic mute key, that comes with their machine [Test Case] * Press mic mute key * Observe that nothing happens [Regression Potential] * Very low. This is very isolated code. All it does is add functionality. In fact there are very few deletions in the diffs. * There is an existing acpi solution, that's already been mentioned in this bug. I'm not sure how these users would be affected once the upgrade hits, but it was never released as an official fix. [Original Report] Pressing the new microphone mute button does not do anything. It should toggle the mute on the current capture device and toggle an led that is part of the button. acpi_listen output: ibm/hotkey HKEY 0080 101b xev output: MappingNotify event, serial 34, synthetic NO, window 0x0, request MappingKeyboard, first_keycode 8, count 248 MappingNotify event, serial 34, synthetic NO, window 0x0, request MappingKeyboard, first_keycode 8, count 247 KeyPress event, serial 34, synthetic NO, window 0x341, root 0x118, subw 0x0, time 10334714, (317,-162), root:(322,207), state 0x0, keycode 248 (keysym 0x0, NoSymbol), same_screen YES, XLookupString gives 0 bytes: XmbLookupString gives 0 bytes: XFilterEvent returns: False KeyRelease event, serial 34, synthetic NO, window 0x341, root 0x118, subw 0x0, time 10334714, (317,-162), root:(322,207), state 0x0, keycode 248 (keysym 0x0, NoSymbol), same_screen YES, XLookupString gives 0 bytes: XFilterEvent returns: False To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/408903/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1298224] Re: Xorg crashed with SIGABRT in amd_xs113_int10_x_inb()
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: fglrx-installer (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fglrx-installer in Ubuntu. https://bugs.launchpad.net/bugs/1298224 Title: Xorg crashed with SIGABRT in amd_xs113_int10_x_inb() Status in “fglrx-installer” package in Ubuntu: Confirmed Bug description: started machine and all programms i need/use and left for some minutes. after coming back the screen saver was active (i deactivated it), i had to enter my password and had this crash report. Hardware: Gigabyte GA-MA790GP-UD4H AMD Phenom II X4 810 Gigabyte Radeon HD 6670 - GV-R667D3-2GI with fglrx-updates installed . ProblemType: Crash DistroRelease: Ubuntu 14.04 Package: xserver-xorg-core 2:1.15.0-1ubuntu7 ProcVersionSignature: Ubuntu 3.13.0-19.40-generic 3.13.6 Uname: Linux 3.13.0-19-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 Date: Thu Mar 27 08:47:30 2014 ExecutablePath: /usr/bin/Xorg InstallationDate: Installed on 2014-03-16 (10 days ago) InstallationMedia: Xubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140225) ProcCmdline: /usr/bin/X -core :1 -seat seat0 -auth /var/run/lightdm/root/:1 -nolisten tcp vt8 -novtswitch ProcEnviron: Signal: 6 SourcePackage: xorg-server StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libpciaccess.so.0 amd_xs113_int10_x_inb () from /usr/lib/x86_64-linux-gnu/xorg/extra-modules/modules/drivers/fglrx_drv.so ?? () from /usr/lib/x86_64-linux-gnu/xorg/extra-modules/modules/drivers/fglrx_drv.so X86EMU_exec () from /usr/lib/x86_64-linux-gnu/xorg/extra-modules/modules/drivers/fglrx_drv.so amd_xs113_int10_xf86ExecX86int10 () from /usr/lib/x86_64-linux-gnu/xorg/extra-modules/modules/drivers/fglrx_drv.so Title: Xorg crashed with SIGABRT in amd_xs113_int10_x_inb() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/1298224/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1302448] [NEW] nasty writes/removes huge number of files
Public bug reported: nasty writes/removes huge number of .#lk0xNN.$HOSTNAME.M files in ~/.gnupg that will overwear a SSD. ** Affects: nasty (Ubuntu) Importance: Undecided Status: New ** Package changed: fglrx-installer (Ubuntu) = nasty (Ubuntu) ** Description changed: - nasty writes/removes huge number of files in ~/.gnupg that will overwear - a SSD. + nasty writes/removes huge number of .# files in ~/.gnupg that will + overwear a SSD. ** Description changed: - nasty writes/removes huge number of .# files in ~/.gnupg that will - overwear a SSD. + nasty writes/removes huge number of .#lk0xNN.host.M files in + ~/.gnupg that will overwear a SSD. ** Description changed: - nasty writes/removes huge number of .#lk0xNN.host.M files in - ~/.gnupg that will overwear a SSD. + nasty writes/removes huge number of .#lk0xNN.$HOSTNAME.M files + in ~/.gnupg that will overwear a SSD. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fglrx-installer in Ubuntu. https://bugs.launchpad.net/bugs/1302448 Title: nasty writes/removes huge number of files Status in “nasty” package in Ubuntu: New Bug description: nasty writes/removes huge number of .#lk0xNN.$HOSTNAME.M files in ~/.gnupg that will overwear a SSD. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nasty/+bug/1302448/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1302241] Re: libcdio should be 0.92
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: libcdio (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libcdio in Ubuntu. https://bugs.launchpad.net/bugs/1302241 Title: libcdio should be 0.92 Status in “libcdio” package in Ubuntu: Confirmed Bug description: Description of problem: Relevant to virtualization / devops / automation, libcdio from 0.83 to 0.90 it cannot read Linux .iso files that use Rock Ridge for file name encoding. With libcdio up to 0.90 iso-read gives bad results for .iso files 4GB. Relevant to virtualization / devops / automation, some Linux distro images are that large. Steps to reproduce problem: 1. From bug report https://savannah.gnu.org/bugs/index.php?39373 get most recent file iso-read-test.sh at https://savannah.gnu.org/bugs/download.php?file_id=30554 2. Run that file either plain or with a single parameter 5000, such as ./iso-read-test.sh ./iso-read-test.sh 5000 3. At the end of output see a lot of read DEFECT where you should see nothing but read back OK. Actual results: At the end of output see a lot of read DEFECT. Expected results: You should see nothing but read back OK. Additional info: There were more than one problems in libcdio 0.90, not just the 4G limit. E.g. Rock Ridge support (often needed for Linux) wasn't compiled in by default. libcdio 0.92 fixes a lot of problems, and has been out for several months, and has been working well so far. Relevant fixes cannot be isolated for patching 0.83. There also is a discussion in docs files at https://github.com/srguiwiz/nrvr-commander/blob/master/docs/which- version-iso-read.txt One example use at https://github.com/srguiwiz/nrvr-commander but this affects any attempt to make virtual machines from distro image .iso files as plain user. An Ubuntu LTS should release with a healthy libcdio 0.92. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libcdio/+bug/1302241/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1289440] Re: nvidia-331-updates 331.38-0ubuntu3: nvidia-331-updates kernel module failed to build [error: variable ‘nv_acpi_driver_template’ has initializer but incomplete type
** Branch linked: lp:ubuntu/trusty-proposed/nvidia-graphics-drivers-331 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-331 in Ubuntu. https://bugs.launchpad.net/bugs/1289440 Title: nvidia-331-updates 331.38-0ubuntu3: nvidia-331-updates kernel module failed to build [error: variable ‘nv_acpi_driver_template’ has initializer but incomplete type] Status in “nvidia-graphics-drivers-331” package in Ubuntu: Confirmed Status in “nvidia-graphics-drivers-331-updates” package in Ubuntu: Confirmed Bug description: Setting up linux-headers-3.14.0-031400rc5-generic (3.14.0-031400rc5.201403022235) ... Examining /etc/kernel/header_postinst.d. run-parts: executing /etc/kernel/header_postinst.d/dkms 3.14.0-031400rc5-generic /boot/vmlinuz-3.14.0-031400rc5-generic Error! Bad return status for module build on kernel: 3.14.0-031400rc5-generic (x86_64) Consult /var/lib/dkms/nvidia-331-updates/331.38/build/make.log for more information. ProblemType: Package DistroRelease: Ubuntu 14.04 Package: nvidia-331-updates 331.38-0ubuntu3 ProcVersionSignature: Ubuntu 3.13.0-16.36-generic 3.13.5 Uname: Linux 3.13.0-16-generic x86_64 ApportVersion: 2.13.2-0ubuntu5 Architecture: amd64 DKMSKernelVersion: 3.14.0-031400rc5-generic Date: Fri Mar 7 23:59:12 2014 DuplicateSignature: dkms:nvidia-331-updates:331.38-0ubuntu3:/var/lib/dkms/nvidia-331-updates/331.38/build/nv-acpi.c:64:21: error: variable ‘nv_acpi_driver_template’ has initializer but incomplete type InstallationDate: Installed on 2012-09-30 (523 days ago) InstallationMedia: Ubuntu 12.04.1 LTS Precise Pangolin - Release amd64 (20120817.1) PackageVersion: 331.38-0ubuntu3 SourcePackage: nvidia-graphics-drivers-331-updates Title: nvidia-331-updates 331.38-0ubuntu3: nvidia-331-updates kernel module failed to build UpgradeStatus: Upgraded to trusty on 2013-11-10 (116 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1289440/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1302453] [NEW] Mic mute key is not working
Public bug reported: The mic mute key key stopped working in trusty. Trusty has gnome-settings-daemon 3.8.6. Support for XF86AudioMicMute was added in gnome-settings-daemon 3.9.2: https://github.com/GNOME/gnome-settings-daemon/commit/3a8beaaf380a483ce33363031d8d276c371d7af1 Can we patch trusty to accept this keycode? ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity-settings-daemon 14.04.0+14.04.20140310-0ubuntu2 ProcVersionSignature: Ubuntu 3.13.0-20.42-generic 3.13.7 Uname: Linux 3.13.0-20-generic x86_64 ApportVersion: 2.14-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Fri Apr 4 11:48:08 2014 InstallationDate: Installed on 2013-06-17 (290 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) SourcePackage: unity-settings-daemon UpgradeStatus: Upgraded to trusty on 2014-01-20 (73 days ago) upstart.unity-settings-daemon.log: (unity-settings-daemon:2465): color-plugin-WARNING **: failed to connect to device: Failed to connect to missing device /org/freedesktop/ColorManager/devices/cups_HP_LaserJet_Professional_P1102w_2 ** Affects: oem-priority Importance: Undecided Status: Invalid ** Affects: unity-settings-daemon (Ubuntu) Importance: Undecided Status: Invalid ** Tags: amd64 apport-bug trusty ** Description changed: The mic mute key key stopped working in trusty. Trusty has gnome-settings-daemon 3.8.6. Support for XF86AudioMicMute was added in gnome-settings-daemon 3.9.2: https://github.com/GNOME/gnome-settings-daemon/commit/3a8beaaf380a483ce33363031d8d276c371d7af1 - I believe gnome-settings-daemon (and unity-settings-daemon) need to - backport that patch for XF86AudioMicMute support. + Can we patch trusty to accept this keycode? ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity-settings-daemon 14.04.0+14.04.20140310-0ubuntu2 ProcVersionSignature: Ubuntu 3.13.0-20.42-generic 3.13.7 Uname: Linux 3.13.0-20-generic x86_64 ApportVersion: 2.14-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Fri Apr 4 11:48:08 2014 InstallationDate: Installed on 2013-06-17 (290 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) SourcePackage: unity-settings-daemon UpgradeStatus: Upgraded to trusty on 2014-01-20 (73 days ago) upstart.unity-settings-daemon.log: (unity-settings-daemon:2465): color-plugin-WARNING **: failed to connect to device: Failed to connect to missing device /org/freedesktop/ColorManager/devices/cups_HP_LaserJet_Professional_P1102w_2 ** Also affects: oem-priority Importance: Undecided Status: New ** Changed in: oem-priority Status: New = Invalid ** Changed in: unity-settings-daemon (Ubuntu) Status: New = Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1302453 Title: Mic mute key is not working Status in OEM Priority Project: Invalid Status in “unity-settings-daemon” package in Ubuntu: Invalid Bug description: The mic mute key key stopped working in trusty. Trusty has gnome-settings-daemon 3.8.6. Support for XF86AudioMicMute was added in gnome-settings-daemon 3.9.2: https://github.com/GNOME/gnome-settings-daemon/commit/3a8beaaf380a483ce33363031d8d276c371d7af1 Can we patch trusty to accept this keycode? ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity-settings-daemon 14.04.0+14.04.20140310-0ubuntu2 ProcVersionSignature: Ubuntu 3.13.0-20.42-generic 3.13.7 Uname: Linux 3.13.0-20-generic x86_64 ApportVersion: 2.14-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Fri Apr 4 11:48:08 2014 InstallationDate: Installed on 2013-06-17 (290 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) SourcePackage: unity-settings-daemon UpgradeStatus: Upgraded to trusty on 2014-01-20 (73 days ago) upstart.unity-settings-daemon.log: (unity-settings-daemon:2465): color-plugin-WARNING **: failed to connect to device: Failed to connect to missing device /org/freedesktop/ColorManager/devices/cups_HP_LaserJet_Professional_P1102w_2 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1302453/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1302451] [NEW] Minimap Goto Anything panel
Public bug reported: Implement a minimap or Goto Anything panel like http://www.sublimetext.com/ ** Affects: brackets Importance: Undecided Status: New ** Affects: eclipse Importance: Undecided Status: New ** Affects: emacs Importance: Undecided Status: New ** Affects: gedit Importance: Undecided Status: New ** Affects: kdevelop4 Importance: Undecided Status: New ** Affects: gedit (Ubuntu) Importance: Undecided Status: New ** Also affects: gedit Importance: Undecided Status: New ** Also affects: emacs Importance: Undecided Status: New ** Summary changed: - Goto Anything panel + Minimap Goto Anything panel ** Description changed: - Implement a Goto Anything panel like http://www.sublimetext.com/ + Implement a minimap or Goto Anything panel like + http://www.sublimetext.com/ ** Also affects: brackets Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gedit in Ubuntu. https://bugs.launchpad.net/bugs/1302451 Title: Minimap Goto Anything panel Status in Brackets: New Status in Eclipse: New Status in GNU Emacs: New Status in Light-Weight Text Editor for Gnome: New Status in KDevelop: New Status in “gedit” package in Ubuntu: New Bug description: Implement a minimap or Goto Anything panel like http://www.sublimetext.com/ To manage notifications about this bug go to: https://bugs.launchpad.net/brackets/+bug/1302451/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1302437] Re: hplip cups backends crash constantly
** Also affects: hplip Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to hplip in Ubuntu. https://bugs.launchpad.net/bugs/1302437 Title: hplip cups backends crash constantly Status in HP Linux Imaging and Printing: New Status in “hplip” package in Ubuntu: New Bug description: Easily provoked by e.g. lpinfo -v. ProblemType: Crash DistroRelease: Ubuntu 14.04 Package: hplip 3.14.3-0ubuntu2 ProcVersionSignature: Ubuntu 3.13.0-22.44-generic 3.13.8 Uname: Linux 3.13.0-22-generic x86_64 ApportVersion: 2.14-0ubuntu1 Architecture: amd64 CupsErrorLog: E [04/Apr/2014:02:04:30 -0700] Unable to bind socket for address [v1.::1]:631 - Cannot assign requested address. E [04/Apr/2014:02:10:40 -0700] [CGI] Failed to initialize libusb (-99) E [04/Apr/2014:02:10:40 -0700] [cups-deviced] PID 3148 (hp) crashed on signal 11! E [04/Apr/2014:02:10:40 -0700] [cups-deviced] PID 3157 (hpfax) crashed on signal 11! E [04/Apr/2014:02:10:41 -0700] [cups-deviced] PID 3142 (gutenprint52+usb) stopped with status 4! Date: Fri Apr 4 02:10:40 2014 ExecutablePath: /usr/lib/cups/backend/hp InstallationDate: Installed on 2014-03-28 (6 days ago) InstallationMedia: Ubuntu-Server 14.04 LTS Trusty Tahr - Beta amd64 (20140326) Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No destinations added. Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize libusb: -99 MachineType: VMware, Inc. VMware Virtual Platform Papersize: letter ProcCmdline: hp ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF8 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-22-generic root=UUID=82a9f05f-32d0-45f7-b302-894b3fdfe56e ro find_preseed=/preseed.cfg noprompt quiet SegvAnalysis: Segfault happened at: 0x7f4e43472414 __GI___pthread_mutex_lock+4: mov 0x10(%rdi),%esi PC (0x7f4e43472414) ok source 0x10(%rdi) (0x0030) not located in a known VMA region (needed readable region)! destination %esi ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: hplip StacktraceTop: __GI___pthread_mutex_lock (mutex=0x0) at ../nptl/pthread_mutex_lock.c:66 libusb_get_device_list () from /lib/x86_64-linux-gnu/libusb-1.0.so.0 ?? () from /usr/lib/libhpmud.so.0 hpmud_probe_devices () from /usr/lib/libhpmud.so.0 ?? () Title: hp crashed with SIGSEGV in __GI___pthread_mutex_lock() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 07/02/2012 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd07/02/2012:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/hplip/+bug/1302437/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1302456] [NEW] missing librelogo localizations
Public bug reported: I have got some bug reports, that libreoffice-librelogo package of Ubuntu contains only English localization of LibreLogo. The official binary LibreOffice builds of documentfoundation.org are shipped with them (see *.properties files in /opt/libreoffice4.2/share/Scripts/python/LibreLogo in Linux). Bug reporter István Blahota has written that this is a regression in Ubuntu 14.04. Thanks in advance for your help! To check it: 1. search LibreLogo_en_US.properties 2. and LibreLogo_hu.properties in the same directory To test it: 1. Start a new document in LibreOffice 2. write xyz in the document 2. change the language of the document to Hungarian (or other non-English language with LibreLogo localization) 3. Click on the Start icon of the (View-Toolbars...-)Logo toolbar. The error message has to be localized to the language of the document. ** Affects: libreoffice (Ubuntu) Importance: Undecided Status: New ** Tags: regression-release -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1302456 Title: missing librelogo localizations Status in “libreoffice” package in Ubuntu: New Bug description: I have got some bug reports, that libreoffice-librelogo package of Ubuntu contains only English localization of LibreLogo. The official binary LibreOffice builds of documentfoundation.org are shipped with them (see *.properties files in /opt/libreoffice4.2/share/Scripts/python/LibreLogo in Linux). Bug reporter István Blahota has written that this is a regression in Ubuntu 14.04. Thanks in advance for your help! To check it: 1. search LibreLogo_en_US.properties 2. and LibreLogo_hu.properties in the same directory To test it: 1. Start a new document in LibreOffice 2. write xyz in the document 2. change the language of the document to Hungarian (or other non-English language with LibreLogo localization) 3. Click on the Start icon of the (View-Toolbars...-)Logo toolbar. The error message has to be localized to the language of the document. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1302456/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1289440] Re: nvidia-331-updates 331.38-0ubuntu3: nvidia-331-updates kernel module failed to build [error: variable ‘nv_acpi_driver_template’ has initializer but incomplete type
This bug was fixed in the package nvidia-graphics-drivers-331 - 331.38-0ubuntu7 --- nvidia-graphics-drivers-331 (331.38-0ubuntu7) trusty; urgency=medium [ Tim O'Shea ] * debian/templates/dkms_nvidia.conf.in, debian/dkms_nvidia/patches/buildfix_kernel_3.14.patch: - Add support for Linux 3.14 (LP: #1289440). -- Alberto Milone alberto.mil...@canonical.com Thu, 03 Apr 2014 17:26:48 +0200 ** Changed in: nvidia-graphics-drivers-331 (Ubuntu) Status: Confirmed = Fix Released ** Branch linked: lp:ubuntu/trusty-proposed/nvidia-graphics- drivers-331-updates ** Changed in: nvidia-graphics-drivers-331-updates (Ubuntu) Status: Confirmed = Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-331 in Ubuntu. https://bugs.launchpad.net/bugs/1289440 Title: nvidia-331-updates 331.38-0ubuntu3: nvidia-331-updates kernel module failed to build [error: variable ‘nv_acpi_driver_template’ has initializer but incomplete type] Status in “nvidia-graphics-drivers-331” package in Ubuntu: Fix Released Status in “nvidia-graphics-drivers-331-updates” package in Ubuntu: Fix Released Bug description: Setting up linux-headers-3.14.0-031400rc5-generic (3.14.0-031400rc5.201403022235) ... Examining /etc/kernel/header_postinst.d. run-parts: executing /etc/kernel/header_postinst.d/dkms 3.14.0-031400rc5-generic /boot/vmlinuz-3.14.0-031400rc5-generic Error! Bad return status for module build on kernel: 3.14.0-031400rc5-generic (x86_64) Consult /var/lib/dkms/nvidia-331-updates/331.38/build/make.log for more information. ProblemType: Package DistroRelease: Ubuntu 14.04 Package: nvidia-331-updates 331.38-0ubuntu3 ProcVersionSignature: Ubuntu 3.13.0-16.36-generic 3.13.5 Uname: Linux 3.13.0-16-generic x86_64 ApportVersion: 2.13.2-0ubuntu5 Architecture: amd64 DKMSKernelVersion: 3.14.0-031400rc5-generic Date: Fri Mar 7 23:59:12 2014 DuplicateSignature: dkms:nvidia-331-updates:331.38-0ubuntu3:/var/lib/dkms/nvidia-331-updates/331.38/build/nv-acpi.c:64:21: error: variable ‘nv_acpi_driver_template’ has initializer but incomplete type InstallationDate: Installed on 2012-09-30 (523 days ago) InstallationMedia: Ubuntu 12.04.1 LTS Precise Pangolin - Release amd64 (20120817.1) PackageVersion: 331.38-0ubuntu3 SourcePackage: nvidia-graphics-drivers-331-updates Title: nvidia-331-updates 331.38-0ubuntu3: nvidia-331-updates kernel module failed to build UpgradeStatus: Upgraded to trusty on 2013-11-10 (116 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1289440/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
