[Dx-packages] [Bug 1379152] Re: Needs building dependency on libmtdev-dev (or making QPlatformSupport public)
This bug was fixed in the package appmenu-qt5 - 0.3.0+15.04.2014-0ubuntu1 --- appmenu-qt5 (0.3.0+15.04.2014-0ubuntu1) vivid; urgency=low [ Ubuntu daily release ] * New rebuild forced [ Timo Jyrinki ] * Add libmtdev-dev build dependency (LP: #1379152) (LP: #1379152) -- Ubuntu daily release ps-jenk...@lists.canonical.com Tue, 11 Nov 2014 06:03:20 + ** Changed in: appmenu-qt5 (Ubuntu) Status: New = Fix Released ** Changed in: maliit-framework (Ubuntu) Status: New = Fix Released -- You received this bug notification because you are a member of DX Packages, which is subscribed to appmenu-qt5 in Ubuntu. https://bugs.launchpad.net/bugs/1379152 Title: Needs building dependency on libmtdev-dev (or making QPlatformSupport public) Status in Application menu for Qt5: New Status in Qt integration with the Mir display server: Fix Released Status in QT Ubuntu: New Status in “appmenu-qt5” package in Ubuntu: Fix Released Status in “maliit-framework” package in Ubuntu: Fix Released Status in “qtmir” package in Ubuntu: Fix Released Status in “qtubuntu” package in Ubuntu: Fix Released Status in Debian GNU/Linux: Won't Fix Status in “qtmir” package in Ubuntu RTM: Fix Released Bug description: Because of packaging changes in Qt Base in Qt 5.3.2, packages using qplatformsupport from private headers will need to add an additional dependency to compile against it. From Debian bug report: --- This comes from QPlatformSupport stuff which creates a static library that needs this linking. It also happens that QPlatformSupport is private stuff, so there is really no way to solve this but either stop using private stuff or helping upstream to make QPlatformSupport public (which would be really helpful). This will in turn mean that it will become a dynamic lib and this bug can be fixed. --- So: A) someone works in qtbase upstream to make the QPlatformSupport public, or B) workaround with adding libmtdev-dev build dependencies This bug refers more to the B) option to get Qt 5.3.2 packages move forward. To manage notifications about this bug go to: https://bugs.launchpad.net/appmenu-qt5/+bug/1379152/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1379152] Re: Needs building dependency on libmtdev-dev (or making QPlatformSupport public)
This bug was fixed in the package maliit-framework - 0.99.0+git20130923+17fdf86-0ubuntu4 --- maliit-framework (0.99.0+git20130923+17fdf86-0ubuntu4) vivid; urgency=medium * Depend on libmtdev-dev for building. (LP: #1379152) -- Timo Jyrinki timo-jyri...@ubuntu.com Thu, 06 Nov 2014 12:12:17 +0200 ** Changed in: qtubuntu (Ubuntu) Status: New = Fix Released -- You received this bug notification because you are a member of DX Packages, which is subscribed to appmenu-qt5 in Ubuntu. https://bugs.launchpad.net/bugs/1379152 Title: Needs building dependency on libmtdev-dev (or making QPlatformSupport public) Status in Application menu for Qt5: New Status in Qt integration with the Mir display server: Fix Released Status in QT Ubuntu: New Status in “appmenu-qt5” package in Ubuntu: Fix Released Status in “maliit-framework” package in Ubuntu: Fix Released Status in “qtmir” package in Ubuntu: Fix Released Status in “qtubuntu” package in Ubuntu: Fix Released Status in Debian GNU/Linux: Won't Fix Status in “qtmir” package in Ubuntu RTM: Fix Released Bug description: Because of packaging changes in Qt Base in Qt 5.3.2, packages using qplatformsupport from private headers will need to add an additional dependency to compile against it. From Debian bug report: --- This comes from QPlatformSupport stuff which creates a static library that needs this linking. It also happens that QPlatformSupport is private stuff, so there is really no way to solve this but either stop using private stuff or helping upstream to make QPlatformSupport public (which would be really helpful). This will in turn mean that it will become a dynamic lib and this bug can be fixed. --- So: A) someone works in qtbase upstream to make the QPlatformSupport public, or B) workaround with adding libmtdev-dev build dependencies This bug refers more to the B) option to get Qt 5.3.2 packages move forward. To manage notifications about this bug go to: https://bugs.launchpad.net/appmenu-qt5/+bug/1379152/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1379152] Re: Needs building dependency on libmtdev-dev (or making QPlatformSupport public)
This bug was fixed in the package qtubuntu - 0.60+15.04.2014-0ubuntu1 --- qtubuntu (0.60+15.04.2014-0ubuntu1) vivid; urgency=low [ Ubuntu daily release ] * New rebuild forced [ Timo Jyrinki ] * Add libmtdev-dev build dependency (LP: #1379152) (LP: #1379152) -- Ubuntu daily release ps-jenk...@lists.canonical.com Tue, 11 Nov 2014 06:11:03 + -- You received this bug notification because you are a member of DX Packages, which is subscribed to appmenu-qt5 in Ubuntu. https://bugs.launchpad.net/bugs/1379152 Title: Needs building dependency on libmtdev-dev (or making QPlatformSupport public) Status in Application menu for Qt5: New Status in Qt integration with the Mir display server: Fix Released Status in QT Ubuntu: New Status in “appmenu-qt5” package in Ubuntu: Fix Released Status in “maliit-framework” package in Ubuntu: Fix Released Status in “qtmir” package in Ubuntu: Fix Released Status in “qtubuntu” package in Ubuntu: Fix Released Status in Debian GNU/Linux: Won't Fix Status in “qtmir” package in Ubuntu RTM: Fix Released Bug description: Because of packaging changes in Qt Base in Qt 5.3.2, packages using qplatformsupport from private headers will need to add an additional dependency to compile against it. From Debian bug report: --- This comes from QPlatformSupport stuff which creates a static library that needs this linking. It also happens that QPlatformSupport is private stuff, so there is really no way to solve this but either stop using private stuff or helping upstream to make QPlatformSupport public (which would be really helpful). This will in turn mean that it will become a dynamic lib and this bug can be fixed. --- So: A) someone works in qtbase upstream to make the QPlatformSupport public, or B) workaround with adding libmtdev-dev build dependencies This bug refers more to the B) option to get Qt 5.3.2 packages move forward. To manage notifications about this bug go to: https://bugs.launchpad.net/appmenu-qt5/+bug/1379152/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1391800] Re: compiz crashed with SIGSEGV in FT_Load_Glyph()
*** This bug is a duplicate of bug 1199571 *** https://bugs.launchpad.net/bugs/1199571 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 #1199571, 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/1391800/+attachment/4258988/+files/CoreDump.gz ** Attachment removed: Disassembly.txt https://bugs.launchpad.net/bugs/1391800/+attachment/4258990/+files/Disassembly.txt ** Attachment removed: ProcMaps.txt https://bugs.launchpad.net/bugs/1391800/+attachment/4258992/+files/ProcMaps.txt ** Attachment removed: ProcStatus.txt https://bugs.launchpad.net/bugs/1391800/+attachment/4258993/+files/ProcStatus.txt ** Attachment removed: Registers.txt https://bugs.launchpad.net/bugs/1391800/+attachment/4258994/+files/Registers.txt ** Attachment removed: Stacktrace.txt https://bugs.launchpad.net/bugs/1391800/+attachment/4258995/+files/Stacktrace.txt ** Attachment removed: ThreadStacktrace.txt https://bugs.launchpad.net/bugs/1391800/+attachment/4258996/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of bug 1199571 Huge multi-threading violations in cairo ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1391800 Title: compiz crashed with SIGSEGV in FT_Load_Glyph() Status in “unity” package in Ubuntu: New Bug description: I was searching for firefox in the dash, had got as far as fi ProblemType: Crash DistroRelease: Ubuntu 15.04 Package: unity 7.3.1+14.10.20141016-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4 Uname: Linux 3.16.0-24-generic x86_64 ApportVersion: 2.14.7-0ubuntu10 Architecture: amd64 CurrentDesktop: Unity Date: Wed Nov 12 09:38:43 2014 ExecutablePath: /usr/bin/compiz InstallationDate: Installed on 2012-10-07 (765 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Beta amd64 (20121007) ProcCmdline: compiz SegvAnalysis: Segfault happened at: 0x7fe93161c540:mov%rdx,0x10(%rax) PC (0x7fe93161c540) ok source %rdx ok destination 0x10(%rax) (0x0010) not located in a known VMA region (needed writable region)! Stack memory exhausted (SP below stack segment) SegvReason: writing NULL VMA Signal: 11 SourcePackage: unity StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libfreetype.so.6 ?? () from /usr/lib/x86_64-linux-gnu/libfreetype.so.6 ?? () from /usr/lib/x86_64-linux-gnu/libfreetype.so.6 ?? () from /usr/lib/x86_64-linux-gnu/libfreetype.so.6 FT_Load_Glyph () from /usr/lib/x86_64-linux-gnu/libfreetype.so.6 Title: compiz crashed with SIGSEGV in FT_Load_Glyph() UpgradeStatus: Upgraded to vivid on 2013-05-07 (554 days ago) UserGroups: adm autopilot cdrom dip kvm libvirtd lpadmin plugdev sambashare sudo vboxusers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1391800/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1379152] Re: Needs building dependency on libmtdev-dev (or making QPlatformSupport public)
** Changed in: maliit-framework (Ubuntu) Assignee: (unassigned) = Timo Jyrinki (timo-jyrinki) ** Changed in: appmenu-qt5 (Ubuntu) Assignee: (unassigned) = Timo Jyrinki (timo-jyrinki) ** Changed in: qtubuntu (Ubuntu) Assignee: (unassigned) = Timo Jyrinki (timo-jyrinki) ** Changed in: qtubuntu Status: New = Fix Released ** Changed in: appmenu-qt5 Status: New = Fix Released -- You received this bug notification because you are a member of DX Packages, which is subscribed to appmenu-qt5 in Ubuntu. https://bugs.launchpad.net/bugs/1379152 Title: Needs building dependency on libmtdev-dev (or making QPlatformSupport public) Status in Application menu for Qt5: Fix Released Status in Qt integration with the Mir display server: Fix Released Status in QT Ubuntu: Fix Released Status in “appmenu-qt5” package in Ubuntu: Fix Released Status in “maliit-framework” package in Ubuntu: Fix Released Status in “qtmir” package in Ubuntu: Fix Released Status in “qtubuntu” package in Ubuntu: Fix Released Status in Debian GNU/Linux: Won't Fix Status in “qtmir” package in Ubuntu RTM: Fix Released Bug description: Because of packaging changes in Qt Base in Qt 5.3.2, packages using qplatformsupport from private headers will need to add an additional dependency to compile against it. From Debian bug report: --- This comes from QPlatformSupport stuff which creates a static library that needs this linking. It also happens that QPlatformSupport is private stuff, so there is really no way to solve this but either stop using private stuff or helping upstream to make QPlatformSupport public (which would be really helpful). This will in turn mean that it will become a dynamic lib and this bug can be fixed. --- So: A) someone works in qtbase upstream to make the QPlatformSupport public, or B) workaround with adding libmtdev-dev build dependencies This bug refers more to the B) option to get Qt 5.3.2 packages move forward. To manage notifications about this bug go to: https://bugs.launchpad.net/appmenu-qt5/+bug/1379152/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1351555] Re: Webapps don't integrating in Unity
Also there many of webapps don't work, as in 13.10, even in webbrowser-app. Were tested: vkcom YouTube GMail There was broken integration in indicators and launcher panel. All of this looks like compatibility break in api layer. -- You received this bug notification because you are a member of DX Packages, which is subscribed to libunity-webapps in Ubuntu. https://bugs.launchpad.net/bugs/1351555 Title: Webapps don't integrating in Unity Status in WebApps: libunity: Confirmed Status in “libunity-webapps” package in Ubuntu: Confirmed Bug description: Such list of tested webapps aren't making any Unity integration since 14.04: YouTube; vkcom; YandexMusic; GMail; lastfm Althoug they are working in 13.10 as expected. They no more openning in default browser, but they do in webbrowser-app, even when installed by default browser. It's both correct for firefox, chromium and opera(other user says) Distributor ID: Ubuntu Description: Ubuntu 14.04.1 LTS Release: 14.04 Codename: trusty Firefox version: 31.0 Chromium version: Chromium 34.0.1847.116 Ubuntu 14.04 aura Opera: ??? ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity-webapps-service 2.5.0~+14.04.20140409-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-29.53-generic 3.13.11.2 Uname: Linux 3.13.0-29-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CurrentDesktop: Unity Date: Sat Aug 2 10:58:47 2014 ExecutablePath: /usr/lib/libunity-webapps/unity-webapps-service SourcePackage: libunity-webapps UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/libunity-webapps/+bug/1351555/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1351555] Re: Webapps don't integrating in Unity
** Changed in: libunity-webapps Assignee: (unassigned) = Alexandre Abreu (abreu-alexandre) ** Changed in: libunity-webapps (Ubuntu) Assignee: (unassigned) = Alexandre Abreu (abreu-alexandre) -- You received this bug notification because you are a member of DX Packages, which is subscribed to libunity-webapps in Ubuntu. https://bugs.launchpad.net/bugs/1351555 Title: Webapps don't integrating in Unity Status in WebApps: libunity: Confirmed Status in “libunity-webapps” package in Ubuntu: Confirmed Bug description: Such list of tested webapps aren't making any Unity integration since 14.04: YouTube; vkcom; YandexMusic; GMail; lastfm Althoug they are working in 13.10 as expected. They no more openning in default browser, but they do in webbrowser-app, even when installed by default browser. It's both correct for firefox, chromium and opera(other user says) Distributor ID: Ubuntu Description: Ubuntu 14.04.1 LTS Release: 14.04 Codename: trusty Firefox version: 31.0 Chromium version: Chromium 34.0.1847.116 Ubuntu 14.04 aura Opera: ??? ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity-webapps-service 2.5.0~+14.04.20140409-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-29.53-generic 3.13.11.2 Uname: Linux 3.13.0-29-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CurrentDesktop: Unity Date: Sat Aug 2 10:58:47 2014 ExecutablePath: /usr/lib/libunity-webapps/unity-webapps-service SourcePackage: libunity-webapps UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/libunity-webapps/+bug/1351555/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1389008] Re: Often fails to connect to Pulseaudio and unity-notifications (results in missing volume notifications and improper volume control)
This bug was fixed in the package ubuntu-touch-session - 0.108+15.04.2014~rtm-0ubuntu1 --- ubuntu-touch-session (0.108+15.04.2014~rtm-0ubuntu1) 14.09; urgency=low [ Ted Gould ] * Override indicator-sound to wait for pulse audio (LP: #1389008) -- Ubuntu daily release ps-jenk...@lists.canonical.com Tue, 11 Nov 2014 21:44:44 + ** Changed in: ubuntu-touch-session (Ubuntu RTM) Status: New = Fix Released -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-sound in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1389008 Title: Often fails to connect to Pulseaudio and unity-notifications (results in missing volume notifications and improper volume control) Status in “indicator-sound” package in Ubuntu: Invalid Status in “ubuntu-touch-session” package in Ubuntu: Fix Released Status in “unity8” package in Ubuntu: Confirmed Status in “indicator-sound” package in Ubuntu RTM: Invalid Status in “ubuntu-touch-session” package in Ubuntu RTM: Fix Released Status in “unity8” package in Ubuntu RTM: New Bug description: Often after boot indicator-sound fails to connect to Pulseaudio and to unity-notifications using libnotify. Therefore, volume notifications aren't shown and changes to the volume role go unnoticed, which then results in improper volume control. As already mentioned in the original bug description, running restart indicator-sound resolves the issue. Original description: Happens often after phone boot where changing volume by touch or by phone buttons. Volume correctly changes, but the org.freedesktop.Notifications popup isn't displayed. The problem seems fixes itself if you run restart indicator-sound, so maybe there's an issue with i-sound and unity-notifications starting at the same time, with the former querying the latter's capabilities before it's ready for business? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-sound/+bug/1389008/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1329089] Re: g++-4.9 binary incompatibilities with libraries built with g++-4.8
** Changed in: qtbase-opensource-src (Ubuntu) Status: New = Fix Released -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1329089 Title: g++-4.9 binary incompatibilities with libraries built with g++-4.8 Status in Mir: Fix Released Status in Mir 0.4 series: Won't Fix Status in Unity: New Status in “dbus-cpp” package in Ubuntu: Fix Released Status in “firefox” package in Ubuntu: New Status in “gcc-4.9” package in Ubuntu: Fix Released Status in “gcc-defaults” package in Ubuntu: Fix Released Status in “location-service” package in Ubuntu: Invalid Status in “mir” package in Ubuntu: Fix Released Status in “process-cpp” package in Ubuntu: Invalid Status in “qtbase-opensource-src” package in Ubuntu: Fix Released Status in “unity” package in Ubuntu: New Status in “unity-scope-click” package in Ubuntu: Fix Released Status in “unity-scopes-api” package in Ubuntu: Fix Released Status in “unity-scopes-shell” package in Ubuntu: New Status in Debian GNU/Linux: New Bug description: The location-service 0.0.3+14.10.20140512-0ubuntu1 package in utopic, when rebuilt against libdbus-cpp3 3.0.0+14.10.20140604-0ubuntu1 (built with gcc-4.8) and with current gcc-defaults (which makes g++-4.9 the default), fails the package build in its test suite. 2/14 Test #2: acceptance_tests ..***Failed 30.54 sec DBus daemon: unix:abstract=/tmp/dbus-HdW1T5UHNB,guid=188551aa5d797b663dade1425398d71b task-0: Started with PID: 13031 task-0: [==] Running 2 tests from 1 test case. task-0: [--] Global test environment set-up. task-0: [--] 2 tests from LocationServiceStandalone task-0: [ RUN ] LocationServiceStandalone.SessionsReceiveUpdatesViaDBus ** (dbus-test-runner:13025): WARNING **: Timing out at maximum wait of 30 seconds. (dbus-test-runner:13025): libdbustest-CRITICAL **: dbus_test_service_run: assertion 'all_tasks(service, all_tasks_finished_helper)' failed task-0: Shutting down DBus daemon: Shutdown This test suite does *not* fail if either dbus-cpp is rebuilt with g++-4.9, or if location-service is built with g++-4.8. This implies a binary compatibility problem for C++ libraries in g++ 4.9, which is critical to resolve. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1329089/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1391876] [NEW] silent control mode in indicators does not match settings app
Public bug reported: At some point the toggle in the sound indicator for silent mode stop matching the real state of the phone. Mainly the indicator things the silent mode is on, while the settings app (and the phone) thinks is on. At this point, if you try to turn silent mode on from the indicator is fails and the toggle always returns to off. The only way to reset this is to turn silent mode off from the settings app. This has been repodroduce by me and silbs. ** Affects: indicator-sound (Ubuntu) Importance: Critical Status: Confirmed ** Tags: rtm14 ** Changed in: indicator-sound (Ubuntu) Status: New = Confirmed ** Changed in: indicator-sound (Ubuntu) Importance: Undecided = Critical ** Tags added: rtm14 -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-sound in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1391876 Title: silent control mode in indicators does not match settings app Status in “indicator-sound” package in Ubuntu: Confirmed Bug description: At some point the toggle in the sound indicator for silent mode stop matching the real state of the phone. Mainly the indicator things the silent mode is on, while the settings app (and the phone) thinks is on. At this point, if you try to turn silent mode on from the indicator is fails and the toggle always returns to off. The only way to reset this is to turn silent mode off from the settings app. This has been repodroduce by me and silbs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-sound/+bug/1391876/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1391876] Re: silent control mode in indicators does not match settings app
*** This bug is a duplicate of bug 1388804 *** https://bugs.launchpad.net/bugs/1388804 ** Changed in: indicator-sound (Ubuntu) Assignee: (unassigned) = Ted Gould (ted) -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-sound in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1391876 Title: silent control mode in indicators does not match settings app Status in “indicator-sound” package in Ubuntu: Confirmed Bug description: At some point the toggle in the sound indicator for silent mode stop matching the real state of the phone. Mainly the indicator things the silent mode is on, while the settings app (and the phone) thinks is on. At this point, if you try to turn silent mode on from the indicator is fails and the toggle always returns to off. The only way to reset this is to turn silent mode off from the settings app. This has been repodroduce by me and silbs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-sound/+bug/1391876/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1391876] Re: silent control mode in indicators does not match settings app
*** This bug is a duplicate of bug 1388804 *** https://bugs.launchpad.net/bugs/1388804 ** This bug has been marked a duplicate of bug 1388804 Silent mode status and message out of sync -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-sound in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1391876 Title: silent control mode in indicators does not match settings app Status in “indicator-sound” package in Ubuntu: Confirmed Bug description: At some point the toggle in the sound indicator for silent mode stop matching the real state of the phone. Mainly the indicator things the silent mode is on, while the settings app (and the phone) thinks is on. At this point, if you try to turn silent mode on from the indicator is fails and the toggle always returns to off. The only way to reset this is to turn silent mode off from the settings app. This has been repodroduce by me and silbs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-sound/+bug/1391876/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1391909] [NEW] Caller number not loaded in Dialler when Call Back or phone icon is clicked in missed call notification and the device is locked
Public bug reported: Steps to reproduce: 1. Place a call to the device and hang up on the other end (to generate a missed call notification) 2. Ensure the greeter is locked 3. Swipe down on the notifications indicator (message icon) 4. Tap on the missed call 5. Tap on Calll Back 6. Unlock the screen Expected result: Dialler application opens with the number loaded ready to call Actual result: Dialler application opens but the number is not loaded N.B. At step 4 we can tap on the phone icon in the missed call notification to get the same effect, it appears to be functionally equivalent to the Call Back button ProblemType: Bug DistroRelease: Ubuntu RTM 14.09 Package: indicator-messages 13.10.1+14.10.20141007-0ubuntu1 Uname: Linux 3.4.67 armv7l ApportVersion: 2.14.7-0ubuntu8 Architecture: armhf Date: Wed Nov 12 14:50:42 2014 InstallationDate: Installed on 2014-11-12 (0 days ago) InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20141112-030205) SourcePackage: indicator-messages UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: indicator-messages (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug armhf qa-manual-testing utopic -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-messages in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1391909 Title: Caller number not loaded in Dialler when Call Back or phone icon is clicked in missed call notification and the device is locked Status in “indicator-messages” package in Ubuntu: New Bug description: Steps to reproduce: 1. Place a call to the device and hang up on the other end (to generate a missed call notification) 2. Ensure the greeter is locked 3. Swipe down on the notifications indicator (message icon) 4. Tap on the missed call 5. Tap on Calll Back 6. Unlock the screen Expected result: Dialler application opens with the number loaded ready to call Actual result: Dialler application opens but the number is not loaded N.B. At step 4 we can tap on the phone icon in the missed call notification to get the same effect, it appears to be functionally equivalent to the Call Back button ProblemType: Bug DistroRelease: Ubuntu RTM 14.09 Package: indicator-messages 13.10.1+14.10.20141007-0ubuntu1 Uname: Linux 3.4.67 armv7l ApportVersion: 2.14.7-0ubuntu8 Architecture: armhf Date: Wed Nov 12 14:50:42 2014 InstallationDate: Installed on 2014-11-12 (0 days ago) InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20141112-030205) SourcePackage: indicator-messages UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-messages/+bug/1391909/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1391909] Re: Caller number not loaded in Dialler when Call Back or phone icon is clicked in missed call notification and the device is locked
** Description changed: Steps to reproduce: 1. Place a call to the device and hang up on the other end (to generate a missed call notification) 2. Ensure the greeter is locked 3. Swipe down on the notifications indicator (message icon) 4. Tap on the missed call - 5. Tap on Calll Back + 5. Tap on Call Back 6. Unlock the screen Expected result: Dialler application opens with the number loaded ready to call Actual result: - Dialler application opens but the number is not loaded N.B. At step 4 we can tap on the phone icon in the missed call notification to get the same effect, it appears to be functionally equivalent to the Call Back button ProblemType: Bug DistroRelease: Ubuntu RTM 14.09 Package: indicator-messages 13.10.1+14.10.20141007-0ubuntu1 Uname: Linux 3.4.67 armv7l ApportVersion: 2.14.7-0ubuntu8 Architecture: armhf Date: Wed Nov 12 14:50:42 2014 InstallationDate: Installed on 2014-11-12 (0 days ago) InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20141112-030205) SourcePackage: indicator-messages UpgradeStatus: No upgrade log present (probably fresh install) ** Also affects: dialer-app (Ubuntu) Importance: Undecided Status: New ** Summary changed: - Caller number not loaded in Dialler when Call Back or phone icon is clicked in missed call notification and the device is locked + Caller number not loaded in Dialer when Call Back or phone icon is clicked in missed call notification and the device is locked ** Summary changed: - Caller number not loaded in Dialer when Call Back or phone icon is clicked in missed call notification and the device is locked + Caller number not loaded in dialler when Call Back or phone icon is clicked in missed call notification and the device is locked -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-messages in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1391909 Title: Caller number not loaded in dialler when Call Back or phone icon is clicked in missed call notification and the device is locked Status in “dialer-app” package in Ubuntu: New Status in “indicator-messages” package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1. Place a call to the device and hang up on the other end (to generate a missed call notification) 2. Ensure the greeter is locked 3. Swipe down on the notifications indicator (message icon) 4. Tap on the missed call 5. Tap on Call Back 6. Unlock the screen Expected result: Dialler application opens with the number loaded ready to call Actual result: Dialler application opens but the number is not loaded N.B. At step 4 we can tap on the phone icon in the missed call notification to get the same effect, it appears to be functionally equivalent to the Call Back button ProblemType: Bug DistroRelease: Ubuntu RTM 14.09 Package: indicator-messages 13.10.1+14.10.20141007-0ubuntu1 Uname: Linux 3.4.67 armv7l ApportVersion: 2.14.7-0ubuntu8 Architecture: armhf Date: Wed Nov 12 14:50:42 2014 InstallationDate: Installed on 2014-11-12 (0 days ago) InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20141112-030205) SourcePackage: indicator-messages UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dialer-app/+bug/1391909/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1391909] Re: Caller number not loaded in dialler when Call Back or phone icon is clicked in missed call notification and the device is locked
Reproduced with the steps in the description. ** Changed in: indicator-messages (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-messages in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1391909 Title: Caller number not loaded in dialler when Call Back or phone icon is clicked in missed call notification and the device is locked Status in “dialer-app” package in Ubuntu: New Status in “indicator-messages” package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1. Place a call to the device and hang up on the other end (to generate a missed call notification) 2. Ensure the greeter is locked 3. Swipe down on the notifications indicator (message icon) 4. Tap on the missed call 5. Tap on Call Back 6. Unlock the screen Expected result: Dialler application opens with the number loaded ready to call Actual result: Dialler application opens but the number is not loaded N.B. At step 4 we can tap on the phone icon in the missed call notification to get the same effect, it appears to be functionally equivalent to the Call Back button ProblemType: Bug DistroRelease: Ubuntu RTM 14.09 Package: indicator-messages 13.10.1+14.10.20141007-0ubuntu1 Uname: Linux 3.4.67 armv7l ApportVersion: 2.14.7-0ubuntu8 Architecture: armhf Date: Wed Nov 12 14:50:42 2014 InstallationDate: Installed on 2014-11-12 (0 days ago) InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20141112-030205) SourcePackage: indicator-messages UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dialer-app/+bug/1391909/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1301125] Re: Lock screen after idle time freezes unity
This started to happen for me occasionally after the upgrade to 14.10 (so it did not happen for me in 14.04). Either the lockscreen does not yet appear (and it shows a frozen buffer of the last view of the desktop), or it shows the lockscreen, but doesn't respond to keyboard (password input) or mouse clicks. Closing the laptop lid does not go back to stand-by but keeps the frozen screen on. I have to do ctrl+alt+f1 and restart the session. -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1301125 Title: Lock screen after idle time freezes unity Status in Unity: Confirmed Status in “unity” package in Ubuntu: Confirmed Bug description: Hello, I recently upgrade to 14.04. My system uses fglrx provided by 14.04. When I lock manually the screen, I get no problem. I can even sleep the system without problem. However, when the screen is locked by idle time, I cannot unlock it. At this point, I can see the screen but with some kind of translucent panel over it. Mouse also works. I tried to type blink the password but I had no luck. I only get a working system by going text mode (ctrl+alt+f1) and restarting lightdm. No dmesg or Xorg logs seems to indicate any error. The only strange log was in .xsession-errors.old: init: processos unity-settings-daemon main (2495) terminados com status 1 init: processos gnome-session (Unity) main (2539) terminados com status 1 init: processos unity-panel-service main (2572) terminados com status 1 init: processos hud main (2536) terminados com status 1 init: processo indicator-powermain (2740) morto pelo sinal TERM init: processo indicator-datetimemain (2741) morto pelo sinal TERM init: processo indicator-soundmain (2747) morto pelo sinal TERM init: processo indicator-printersmain (2748) morto pelo sinal TERM init: processo indicator-sessionmain (2768) morto pelo sinal TERM init: processo indicator-syncmain (2795) morto pelo sinal TERM init: processo update-notifier-crash (/var/crash/_usr_bin_istanbul.1000.crash)main (4987) morto pelo sinal TERM init: processos unity-panel-service-lockscreen main (7447) terminados com status 1 init: Disconnected from notified D-Bus bus init: processos at-spi2-registryd main (2538) terminados com status 1 But as it has no time info, I cannot tell when they happened. At least another user faces the same problem: http://ubuntuforums.org/showthread.php?t=2214421 And this seems to be different from bug 1283938 as pm sleep/wake works as expected. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.1.2+14.04.20140328.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-20.42-generic 3.13.7 Uname: Linux 3.13.0-20-generic x86_64 NonfreeKernelModules: fglrx .tmp.unity.support.test.0: ApportVersion: 2.14-0ubuntu1 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 CurrentDesktop: Unity Date: Wed Apr 2 00:01:05 2014 DistUpgraded: 2014-03-31 21:24:46,145 DEBUG enabling apt cron job DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: fglrx-updates, 13.350.1, 3.11.0-18-generic, x86_64: installed fglrx-updates, 13.350.1, 3.13.0-20-generic, x86_64: installed vboxhost, 4.3.10, 3.11.0-18-generic, x86_64: installed vboxhost, 4.3.10, 3.13.0-20-generic, x86_64: installed GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Turks XT [Radeon HD 6670/7670] [1002:6758] (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0012] InstallationDate: Installed on 2012-10-19 (529 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5) JockeyStatus: kmod:wl - Broadcom STA wireless driver (Proprietário, Desativado, Não está em uso) [auto-install] kmod:fglrx - Video driver for the AMD graphics accelerators (Proprietário, Desativado, Não está em uso) kmod:fglrx_updates - ATI Fire GL (Proprietário, Habilitado, Não está em uso) MachineType: Dell Inc. XPS 8300 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-20-generic root=UUID=6633d579-d782-47ec-ad5a-22abac1412a0 ro quiet splash vt.handoff=7 SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2014-04-01 (1 days ago) dmi.bios.date: 10/17/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A06 dmi.board.name: 0Y2MRG dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA06:bd10/17/2011:svnDellInc.:pnXPS8300:pvr:rvnDellInc.:rn0Y2MRG:rvrA01:cvnDellInc.:ct3:cvr: dmi.product.name: XPS
[Dx-packages] [Bug 1391954] [NEW] indicator-sound not running on first boot
Public bug reported: Steps to reproduce: 1. Boot the device after a fresh flash with --wipe or --bootstrap 2. Complete the wizard steps 3. Check the indicators for the presence of the sound indicator Expected result: Sound indicator is present and running Actual result: Indicator is not present. There is a placeholder for it on the menu as shown in http://people.canonical.com/~brendan-donegan/indicator- sound.png Running 'status indicator-sound' shows it is stopped ProblemType: Bug DistroRelease: Ubuntu RTM 14.09 Package: indicator-sound 12.10.2+14.10.20141021~rtm-0ubuntu1 Uname: Linux 3.4.67 armv7l ApportVersion: 2.14.7-0ubuntu8 Architecture: armhf Date: Wed Nov 12 16:26:28 2014 InstallationDate: Installed on 2014-11-12 (0 days ago) InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20141112-135345) SourcePackage: indicator-sound UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: indicator-sound (Ubuntu) Importance: Critical Status: New ** Tags: apport-bug armhf qa-sanity utopic ** Changed in: indicator-sound (Ubuntu) Importance: Undecided = Critical -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-sound in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1391954 Title: indicator-sound not running on first boot Status in “indicator-sound” package in Ubuntu: New Bug description: Steps to reproduce: 1. Boot the device after a fresh flash with --wipe or --bootstrap 2. Complete the wizard steps 3. Check the indicators for the presence of the sound indicator Expected result: Sound indicator is present and running Actual result: Indicator is not present. There is a placeholder for it on the menu as shown in http://people.canonical.com/~brendan-donegan/indicator- sound.png Running 'status indicator-sound' shows it is stopped ProblemType: Bug DistroRelease: Ubuntu RTM 14.09 Package: indicator-sound 12.10.2+14.10.20141021~rtm-0ubuntu1 Uname: Linux 3.4.67 armv7l ApportVersion: 2.14.7-0ubuntu8 Architecture: armhf Date: Wed Nov 12 16:26:28 2014 InstallationDate: Installed on 2014-11-12 (0 days ago) InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20141112-135345) SourcePackage: indicator-sound UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-sound/+bug/1391954/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1391954] Re: indicator-sound not running on first boot
Actually no, just reproduced it, ignore my previous comment. -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-sound in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1391954 Title: indicator-sound not running on first boot Status in “indicator-sound” package in Ubuntu: New Bug description: Steps to reproduce: 1. Boot the device after a fresh flash with --wipe or --bootstrap 2. Complete the wizard steps 3. Check the indicators for the presence of the sound indicator Expected result: Sound indicator is present and running Actual result: Indicator is not present. There is a placeholder for it on the menu as shown in http://people.canonical.com/~brendan-donegan/indicator- sound.png Running 'status indicator-sound' shows it is stopped ProblemType: Bug DistroRelease: Ubuntu RTM 14.09 Package: indicator-sound 12.10.2+14.10.20141021~rtm-0ubuntu1 Uname: Linux 3.4.67 armv7l ApportVersion: 2.14.7-0ubuntu8 Architecture: armhf Date: Wed Nov 12 16:26:28 2014 InstallationDate: Installed on 2014-11-12 (0 days ago) InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20141112-135345) SourcePackage: indicator-sound UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-sound/+bug/1391954/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1391954] Re: indicator-sound not running on first boot
Can't reproduce this with mako, running the same image. -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-sound in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1391954 Title: indicator-sound not running on first boot Status in “indicator-sound” package in Ubuntu: New Bug description: Steps to reproduce: 1. Boot the device after a fresh flash with --wipe or --bootstrap 2. Complete the wizard steps 3. Check the indicators for the presence of the sound indicator Expected result: Sound indicator is present and running Actual result: Indicator is not present. There is a placeholder for it on the menu as shown in http://people.canonical.com/~brendan-donegan/indicator- sound.png Running 'status indicator-sound' shows it is stopped ProblemType: Bug DistroRelease: Ubuntu RTM 14.09 Package: indicator-sound 12.10.2+14.10.20141021~rtm-0ubuntu1 Uname: Linux 3.4.67 armv7l ApportVersion: 2.14.7-0ubuntu8 Architecture: armhf Date: Wed Nov 12 16:26:28 2014 InstallationDate: Installed on 2014-11-12 (0 days ago) InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20141112-135345) SourcePackage: indicator-sound UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-sound/+bug/1391954/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1301125] Re: Lock screen after idle time freezes unity
When this happens, can you move to tty1, attach to compiz process (sudo gdb `pidof compiz`) and do bt full on it? You also need to have unity/compiz debug symbols installed¹ [1] https://wiki.ubuntu.com/DebuggingProgramCrash#Debug_Symbol_Packages -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1301125 Title: Lock screen after idle time freezes unity Status in Unity: Confirmed Status in “unity” package in Ubuntu: Confirmed Bug description: Hello, I recently upgrade to 14.04. My system uses fglrx provided by 14.04. When I lock manually the screen, I get no problem. I can even sleep the system without problem. However, when the screen is locked by idle time, I cannot unlock it. At this point, I can see the screen but with some kind of translucent panel over it. Mouse also works. I tried to type blink the password but I had no luck. I only get a working system by going text mode (ctrl+alt+f1) and restarting lightdm. No dmesg or Xorg logs seems to indicate any error. The only strange log was in .xsession-errors.old: init: processos unity-settings-daemon main (2495) terminados com status 1 init: processos gnome-session (Unity) main (2539) terminados com status 1 init: processos unity-panel-service main (2572) terminados com status 1 init: processos hud main (2536) terminados com status 1 init: processo indicator-powermain (2740) morto pelo sinal TERM init: processo indicator-datetimemain (2741) morto pelo sinal TERM init: processo indicator-soundmain (2747) morto pelo sinal TERM init: processo indicator-printersmain (2748) morto pelo sinal TERM init: processo indicator-sessionmain (2768) morto pelo sinal TERM init: processo indicator-syncmain (2795) morto pelo sinal TERM init: processo update-notifier-crash (/var/crash/_usr_bin_istanbul.1000.crash)main (4987) morto pelo sinal TERM init: processos unity-panel-service-lockscreen main (7447) terminados com status 1 init: Disconnected from notified D-Bus bus init: processos at-spi2-registryd main (2538) terminados com status 1 But as it has no time info, I cannot tell when they happened. At least another user faces the same problem: http://ubuntuforums.org/showthread.php?t=2214421 And this seems to be different from bug 1283938 as pm sleep/wake works as expected. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.1.2+14.04.20140328.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-20.42-generic 3.13.7 Uname: Linux 3.13.0-20-generic x86_64 NonfreeKernelModules: fglrx .tmp.unity.support.test.0: ApportVersion: 2.14-0ubuntu1 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 CurrentDesktop: Unity Date: Wed Apr 2 00:01:05 2014 DistUpgraded: 2014-03-31 21:24:46,145 DEBUG enabling apt cron job DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: fglrx-updates, 13.350.1, 3.11.0-18-generic, x86_64: installed fglrx-updates, 13.350.1, 3.13.0-20-generic, x86_64: installed vboxhost, 4.3.10, 3.11.0-18-generic, x86_64: installed vboxhost, 4.3.10, 3.13.0-20-generic, x86_64: installed GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Turks XT [Radeon HD 6670/7670] [1002:6758] (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0012] InstallationDate: Installed on 2012-10-19 (529 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5) JockeyStatus: kmod:wl - Broadcom STA wireless driver (Proprietário, Desativado, Não está em uso) [auto-install] kmod:fglrx - Video driver for the AMD graphics accelerators (Proprietário, Desativado, Não está em uso) kmod:fglrx_updates - ATI Fire GL (Proprietário, Habilitado, Não está em uso) MachineType: Dell Inc. XPS 8300 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-20-generic root=UUID=6633d579-d782-47ec-ad5a-22abac1412a0 ro quiet splash vt.handoff=7 SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2014-04-01 (1 days ago) dmi.bios.date: 10/17/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A06 dmi.board.name: 0Y2MRG dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA06:bd10/17/2011:svnDellInc.:pnXPS8300:pvr:rvnDellInc.:rn0Y2MRG:rvrA01:cvnDellInc.:ct3:cvr: dmi.product.name: XPS 8300 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.11+14.04.20140328-0ubuntu1 version.fglrx-installer: fglrx-installer N/A version.ia32-libs: ia32-libs N/A version.libdrm2:
[Dx-packages] [Bug 1310101] Re: bluetooth icon doesnt dim when disabled in xubuntu 14.04
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: indicator-bluetooth (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-bluetooth in Ubuntu. https://bugs.launchpad.net/bugs/1310101 Title: bluetooth icon doesnt dim when disabled in xubuntu 14.04 Status in “indicator-bluetooth” package in Ubuntu: Confirmed Bug description: During the live cd and after the installation, when i disable bluetooth, the bluetooth icon in the panel doesnt dim as it does with other distros, including ubuntu 14.04. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-bluetooth/+bug/1310101/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1310101] Re: bluetooth icon doesnt dim when disabled in xubuntu 14.04
with Xubuntu 14.04 installed, no change at the bluetooth icon with status enabled or disabled. It doesn't seem related to the icon style. -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-bluetooth in Ubuntu. https://bugs.launchpad.net/bugs/1310101 Title: bluetooth icon doesnt dim when disabled in xubuntu 14.04 Status in “indicator-bluetooth” package in Ubuntu: Confirmed Bug description: During the live cd and after the installation, when i disable bluetooth, the bluetooth icon in the panel doesnt dim as it does with other distros, including ubuntu 14.04. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-bluetooth/+bug/1310101/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1391981] [NEW] package libunity9 7.1.4+14.10.20140808-0ubuntu1 failed to install/upgrade: покушавам да препишем дељени „/usr/bin/unity-scope-loader“, који се разликује од других при
Public bug reported: Random crash on startup ProblemType: Package DistroRelease: Ubuntu 14.10 Package: libunity9 7.1.4+14.10.20140808-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-23.31-generic 3.16.4 Uname: Linux 3.16.0-23-generic x86_64 ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 Date: Wed Nov 12 18:45:13 2014 DuplicateSignature: package:libunity9:7.1.4+14.10.20140808-0ubuntu1:покушавам да препишем дељени „/usr/bin/unity-scope-loader“, који се разликује од других примерака пакета „libunity9:i386“ ErrorMessage: покушавам да препишем дељени „/usr/bin/unity-scope-loader“, који се разликује од других примерака пакета „libunity9:i386“ InstallationDate: Installed on 2014-11-12 (0 days ago) InstallationMedia: Xubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1) SourcePackage: libunity Title: package libunity9 7.1.4+14.10.20140808-0ubuntu1 failed to install/upgrade: покушавам да препишем дељени „/usr/bin/unity-scope-loader“, који се разликује од других примерака пакета „libunity9:i386“ UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: libunity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package utopic -- You received this bug notification because you are a member of DX Packages, which is subscribed to libunity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1391981 Title: package libunity9 7.1.4+14.10.20140808-0ubuntu1 failed to install/upgrade: покушавам да препишем дељени „/usr/bin/unity-scope- loader“, који се разликује од других примерака пакета „libunity9:i386“ Status in “libunity” package in Ubuntu: New Bug description: Random crash on startup ProblemType: Package DistroRelease: Ubuntu 14.10 Package: libunity9 7.1.4+14.10.20140808-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-23.31-generic 3.16.4 Uname: Linux 3.16.0-23-generic x86_64 ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 Date: Wed Nov 12 18:45:13 2014 DuplicateSignature: package:libunity9:7.1.4+14.10.20140808-0ubuntu1:покушавам да препишем дељени „/usr/bin/unity-scope-loader“, који се разликује од других примерака пакета „libunity9:i386“ ErrorMessage: покушавам да препишем дељени „/usr/bin/unity-scope-loader“, који се разликује од других примерака пакета „libunity9:i386“ InstallationDate: Installed on 2014-11-12 (0 days ago) InstallationMedia: Xubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1) SourcePackage: libunity Title: package libunity9 7.1.4+14.10.20140808-0ubuntu1 failed to install/upgrade: покушавам да препишем дељени „/usr/bin/unity-scope-loader“, који се разликује од других примерака пакета „libunity9:i386“ UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libunity/+bug/1391981/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1391981] Re: package libunity9 7.1.4+14.10.20140808-0ubuntu1 failed to install/upgrade: покушавам да препишем дељени „/usr/bin/unity-scope-loader“, који се разликује од других приме
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of DX Packages, which is subscribed to libunity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1391981 Title: package libunity9 7.1.4+14.10.20140808-0ubuntu1 failed to install/upgrade: покушавам да препишем дељени „/usr/bin/unity-scope- loader“, који се разликује од других примерака пакета „libunity9:i386“ Status in “libunity” package in Ubuntu: New Bug description: Random crash on startup ProblemType: Package DistroRelease: Ubuntu 14.10 Package: libunity9 7.1.4+14.10.20140808-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-23.31-generic 3.16.4 Uname: Linux 3.16.0-23-generic x86_64 ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 Date: Wed Nov 12 18:45:13 2014 DuplicateSignature: package:libunity9:7.1.4+14.10.20140808-0ubuntu1:покушавам да препишем дељени „/usr/bin/unity-scope-loader“, који се разликује од других примерака пакета „libunity9:i386“ ErrorMessage: покушавам да препишем дељени „/usr/bin/unity-scope-loader“, који се разликује од других примерака пакета „libunity9:i386“ InstallationDate: Installed on 2014-11-12 (0 days ago) InstallationMedia: Xubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1) SourcePackage: libunity Title: package libunity9 7.1.4+14.10.20140808-0ubuntu1 failed to install/upgrade: покушавам да препишем дељени „/usr/bin/unity-scope-loader“, који се разликује од других примерака пакета „libunity9:i386“ UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libunity/+bug/1391981/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1355463] Re: Unity launcher crash after click second open window
This may be the same Bug as Bug #1284898 -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1355463 Title: Unity launcher crash after click second open window Status in Unity: New Status in “unity” package in Ubuntu: New Bug description: When there are more than one window opened from the same program, let's say gedit and you click on the application launcher expecting a kind of previsualizators to choose one of the opened windows, X system keeps blocked and I need to open a shell session and kill it. Release: Ubuntu 14.04.1 LTS To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1355463/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1355463] Re: Unity launcher crash after click second open window
I also had this problem, as well as when using super+w. I could solve it by playing around with some settings but because I can not reproduce the problem, I'm not able to narrow it down. Anyway, maybe someone else can do it using the steps I've done – up to that point, where I realised, that the problem was gone: 1) moving 'unityshell' to the last entry in /org/compiz/profiles/unity/plugins/core (with dconf-editor), as described in https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1284898/comments/10 2) changed the following settings using ccsm: 2.1) OpenGL - General - Texture Filter: switched from Good to Fast 2.2) Scale-Plugin - Appearance - Darken Background: switched from true to false 2.3) Scale-Plugin - Appearance - X Offset: Increased from 0 to 1 2.4) Scale-Plugin - Appearance - Y Offset: Increased from 0 to 1 2.5) Scale-Plugin - Bindings - Key Bindings Toggle Scale Mode: switched from true to false As stated before, I could not reproduce the problem. That means, I also turned back all the described settings back to their previous values, but it still works. -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1355463 Title: Unity launcher crash after click second open window Status in Unity: New Status in “unity” package in Ubuntu: New Bug description: When there are more than one window opened from the same program, let's say gedit and you click on the application launcher expecting a kind of previsualizators to choose one of the opened windows, X system keeps blocked and I need to open a shell session and kill it. Release: Ubuntu 14.04.1 LTS To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1355463/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1391702] Re: Low battery notification not localized
Moving to RTM, this is already fixed in Vivid. ** Package changed: indicator-power (Ubuntu) = indicator-power (Ubuntu RTM) ** Changed in: indicator-power (Ubuntu RTM) Status: New = Triaged -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-power in Ubuntu. https://bugs.launchpad.net/bugs/1391702 Title: Low battery notification not localized Status in “indicator-power” package in Ubuntu RTM: Triaged Bug description: The low battery warning dialog appears untranslated. See attached screenshot (krillin device with Spanish setup). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-rtm/+source/indicator-power/+bug/1391702/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1374301] Re: osd notifications blurry
It is possible to start notify-osd with GDK_SCALE=1 and to get high quality notifications. The notifications are not blurry this way and they are scaled correctly in any way. It could be a solution to disable GDK_SCALE for notify-osd, because it is not needed. It looks better without this integer scaling. -- You received this bug notification because you are a member of DX Packages, which is subscribed to notify-osd in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1374301 Title: osd notifications blurry Status in “notify-osd” package in Ubuntu: Confirmed Bug description: Recently clean installed Ubuntu 14.04.1 Trusty Tahr. With hidpi scale set to 2, and text scale set to .75, all on screen notifications have been blurry to the point of being unreadable. Any ideas on what could cause this? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/notify-osd/+bug/1374301/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1374301] Re: osd notifications blurry
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: notify-osd (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of DX Packages, which is subscribed to notify-osd in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1374301 Title: osd notifications blurry Status in “notify-osd” package in Ubuntu: Confirmed Bug description: Recently clean installed Ubuntu 14.04.1 Trusty Tahr. With hidpi scale set to 2, and text scale set to .75, all on screen notifications have been blurry to the point of being unreadable. Any ideas on what could cause this? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/notify-osd/+bug/1374301/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1389008] Re: Often fails to connect to Pulseaudio and unity-notifications (results in missing volume notifications and improper volume control)
reverted in RTM due to issues with first boot ... ubuntu-touch-session (0.108+15.04.2014-0ubuntu2) 14.09; urgency=medium * revert the former override change since it was found to be not working on first boot on fresh installs during milestone testing. ubuntu-touch-session (0.108+15.04.2014-0ubuntu1) vivid; urgency=low [ Ted Gould ] * Override indicator-sound to wait for pulse audio (LP: #1389008) Date: 2014-11-12 17:47:09.485214+00:00 ** Changed in: ubuntu-touch-session (Ubuntu RTM) Status: Fix Released = Confirmed -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-sound in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1389008 Title: Often fails to connect to Pulseaudio and unity-notifications (results in missing volume notifications and improper volume control) Status in “indicator-sound” package in Ubuntu: Invalid Status in “ubuntu-touch-session” package in Ubuntu: Fix Released Status in “unity8” package in Ubuntu: Confirmed Status in “indicator-sound” package in Ubuntu RTM: Invalid Status in “ubuntu-touch-session” package in Ubuntu RTM: Confirmed Status in “unity8” package in Ubuntu RTM: New Bug description: Often after boot indicator-sound fails to connect to Pulseaudio and to unity-notifications using libnotify. Therefore, volume notifications aren't shown and changes to the volume role go unnoticed, which then results in improper volume control. As already mentioned in the original bug description, running restart indicator-sound resolves the issue. Original description: Happens often after phone boot where changing volume by touch or by phone buttons. Volume correctly changes, but the org.freedesktop.Notifications popup isn't displayed. The problem seems fixes itself if you run restart indicator-sound, so maybe there's an issue with i-sound and unity-notifications starting at the same time, with the former querying the latter's capabilities before it's ready for business? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-sound/+bug/1389008/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 879218] Re: some users prefer the old grid behaviour (dividing each time the keybinding are used)
So is there a fix for making ctrl + alt + numpad 4 and numpad 6 cycle between the various widths for multiple keypresses instead of just being half? Because my compiz grid still does not work. I am on Ubuntu 12.04 LTS. -- You received this bug notification because you are a member of DX Packages, which is subscribed to compiz-plugins-main in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/879218 Title: some users prefer the old grid behaviour (dividing each time the keybinding are used) Status in Compiz: Fix Released Status in Compiz Grid Plugin: Fix Committed Status in Compiz Main Plugins: Fix Committed Status in Unity: Won't Fix Status in “compiz” package in Ubuntu: Fix Released Status in “compiz-plugins-main” package in Ubuntu: Fix Committed Bug description: I've used the Compiz Grid function for a long time and I generally use it to set my browser to the right 2/3 or 3/4 of the screen and have other apps on the top or bottom half of the remaining part. Now when I press ctrl + alt numpad 4 or numpad 6 it only does half and when pressing it a second or third time it does nothing. The options for different sizes work for all the corners and top and bottom. When I press ctrl + alt numpad 9 it does the same thing as pressing ctrl + alt numpat 8. Here's a video that may illustrate the problem better than my description. http://www.youtube.com/watch?v=i3WC0BnXe5E ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: unity 4.22.0-0ubuntu3 ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4 Uname: Linux 3.0.0-12-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 1.23-0ubuntu3 Architecture: amd64 CompizPlugins: [core,bailer,detection,composite,opengl,compiztoolbox,decor,move,gnomecompat,mousepoll,imgpng,unitymtgrabhandles,regex,animation,grid,snap,expo,workarounds,ezoom,resize,vpswitch,place,wall,staticswitcher,fade,session,scale,unityshell] Date: Thu Oct 20 23:03:00 2011 InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012) ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) A video of the latest Grid version (also showing this fix in action): https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/745159/+attachment/3660185/+files/GridAllFunctionalityFullyFixed.mp4 To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/879218/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1309942] Re: Window Controls not functioning.
Unfortunatly I really miss this feature. The best is: if buttons position is not customiszble anymore please remove the layout option in Ubuntu Tweak asap. -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1309942 Title: Window Controls not functioning. Status in Unity: Won't Fix Status in Unity Tweak Tool: Won't Fix Status in “unity” package in Ubuntu: Won't Fix Bug description: As mentioned earlier the two key functions of Unity Tweak Tool are not working . 1.Windows Control/ Allignment from left to right . 2.Show menu button. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1309942/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1223699] Re: klipper hangs after launch in Unity
** Changed in: unity (Ubuntu) Importance: Undecided = High -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1223699 Title: klipper hangs after launch in Unity Status in Unity: Confirmed Status in “unity” package in Ubuntu: Confirmed Bug description: Still actual for Ubuntu 14.10 x64 klipper hangs after launch in Unity. I am getting this output in terminal: klipper QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave. QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave. klipper(20151) Klipper::loadHistory: Failed to load history resource. Clipboard history cannot be read. : History file does not exist ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: klipper 4:4.11.1-0ubuntu2 ProcVersionSignature: Ubuntu 3.11.0-6.12-generic 3.11.0 Uname: Linux 3.11.0-6-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.12.1-0ubuntu3 Architecture: amd64 Date: Wed Sep 11 10:31:02 2013 InstallationDate: Installed on 2013-07-31 (41 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Alpha amd64 (20130730) MarkForUpload: True SourcePackage: kde-workspace UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1223699/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1104632] Re: Application spread view (Compiz scale) doesn't work properly after using Show Desktop
** Changed in: unity (Ubuntu) Importance: Undecided = High -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1104632 Title: Application spread view (Compiz scale) doesn't work properly after using Show Desktop Status in Unity: Confirmed Status in “unity” package in Ubuntu: Confirmed Bug description: What steps will reproduce the problem? 1. Open two or more windows of an application like Nautilus so that all are visible on the screen 2. Use the Show Desktop button to hide the windows 3. Activate the window spread by clicking at the icon of the application you launched two times What is the expected output? - all windows of the application (from current workspace) are shown in the spread, represented by a thumbnail What do you see instead? - all windows are technically shown but only the window activated by the first click at the icon has a working thumbnail - the area where the other window-thumbnails should be located is functional but the thumbnails are missing ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: unity 6.12.0daily13.01.21-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-1.5-generic 3.8.0-rc4 Uname: Linux 3.8.0-1-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus.0: Error: [Errno 21] Ist ein Verzeichnis: '/proc/driver/nvidia/gpus/0' .proc.driver.nvidia.registry: Binary: .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 310.19 Thu Nov 8 00:52:03 PST 2012 GCC version: gcc-Version 4.7.2 (Ubuntu/Linaro 4.7.2-19ubuntu1) .proc.driver.nvidia.warnings.fbdev: Your system is not currently configured to drive a VGA console on the primary VGA device. The NVIDIA Linux graphics driver requires the use of a text-mode VGA console. Use of other console drivers including, but not limited to, vesafb, may result in corruption and stability problems, and is not supported. .tmp.unity.support.test.0: ApportVersion: 2.8-0ubuntu2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz Date: Fri Jan 25 02:19:52 2013 DistUpgraded: Fresh install DistroCodename: raring DistroVariant: ubuntu DkmsStatus: nvidia-310, 310.19, 3.8.0-1-generic, x86_64: installed GraphicsCard: NVIDIA Corporation GF114 [GeForce GTX 560 Ti] [10de:1200] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:8390] InstallationDate: Installed on 2013-01-22 (2 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Alpha amd64 (20130122) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-1-generic root=UUID=db108b5c-1f1d-4fe4-99bd-234f619ae6cf ro quiet splash nomodeset video=uvesafb:mode_option=1280x1024-24,mtrr=3,scroll=ywrap vt.handoff=7 SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/11/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.20 dmi.board.name: P67 Extreme4 Gen3 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.20:bd05/11/2012:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnP67Extreme4Gen3:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. version.compiz: compiz 1:0.9.9~daily13.01.21-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.41-0ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.0.1-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.0.1-0ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A version.xserver-xorg-core: xserver-xorg-core 2:1.13.1.901-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.0.0-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.20.19-0ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.6-0ubuntu1 xserver.bootTime: Thu Jan 24 15:13:16 2013 xserver.configfile: default xserver.errors: open /dev/dri/card0: No such file or directory open /dev/dri/card0: No such file or directory xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version:
[Dx-packages] [Bug 1391521] Re: can't type accented letters in ubuntu 14.10 [ast]
** Changed in: unity (Ubuntu) Importance: Undecided = High -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1391521 Title: can't type accented letters in ubuntu 14.10 [ast] Status in “unity” package in Ubuntu: Confirmed Bug description: Hi, after a fresh install of Ubuntu 14.10, ( and repositories proposed, and backports enabled ) , and a full update, it's impossible to use/type/write accented letters in Asturian languages. I've tested in other languages and this issue is not present. If user choose Asturian language, and Asturian keyboard, it's impossible to type á,é,í,ó,ú, ü, ñ. Steps to reproduce it: 1- Change language to Asturian 2- Change keyboard (Launcher--System settings--Text entry--Asturian (Spain, with bottom-dot H and bottom-dot L). 3- Add it. 4- In the top panel, clic and select the text entry: Asturian 5- Open a .txt file, and try to type á,é,í, ó,ú, ü,ñ (it will doesn't work) (if language system is another one, all keyboards works. If we choose Asturian, no one keyboard works, and is not possible to use accents) I thought this bug was related to: https://bugs.launchpad.net/unity/+bug/1330041 but we think they are different issues. Anyway, this bug has high importance for Asturian users, because they can't write a document, search in browser or write an email properly. More information: lsb_release -rd Description: Ubuntu 14.10 Release: 14.10 ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: unity 7.3.1+14.10.20141016-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-25.33-generic 3.16.7 Uname: Linux 3.16.0-25-generic x86_64 ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Tue Nov 11 14:39:13 2014 InstallationDate: Installed on 2014-11-10 (0 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1) SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1391521/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1172649] Re: Spotify icon is displayed twice in Unity Launcher
** Changed in: unity (Ubuntu) Importance: Undecided = Medium -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1172649 Title: Spotify icon is displayed twice in Unity Launcher Status in Unity: Confirmed Status in “unity” package in Ubuntu: Confirmed Bug description: I'm using Ubuntu 13.04 and latest Spotify version. The spotify icon (when the application is not running) it's sticked on the launcher, and this is ok. When I click on it, another icon appears (see the attached picture). This happened also in older versions of Unity. Could someone please fix this? To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1172649/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1310101] Re: bluetooth icon doesnt dim when disabled in xubuntu 14.04
It seems also that this particular problem was seen since the introduction of blueman-applet 1.23, which is the current in xubuntu 14.04. http://kissmyarch.blogspot.it/2011/10/blueman-applet-with- missing-icon.html -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-bluetooth in Ubuntu. https://bugs.launchpad.net/bugs/1310101 Title: bluetooth icon doesnt dim when disabled in xubuntu 14.04 Status in “indicator-bluetooth” package in Ubuntu: Confirmed Bug description: During the live cd and after the installation, when i disable bluetooth, the bluetooth icon in the panel doesnt dim as it does with other distros, including ubuntu 14.04. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-bluetooth/+bug/1310101/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 864037] Re: workspace switcher zoom failure with multiple monitors
** Changed in: unity (Ubuntu) Status: In Progress = Fix Released -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/864037 Title: workspace switcher zoom failure with multiple monitors Status in Unity: Fix Released Status in “unity” package in Ubuntu: Fix Released Status in “unity” source package in Oneiric: Fix Released Bug description: SRU TEST CASE: 1. connect an external display to your system 2. click workspace switcher 3. notice all the graphical problems on the screen 4. now install Unity from oneiric-proposed 5. Notice everything is working as it with single display =Original Report= When my laptop is not connected to an external monitor and I click the Workspace Switcher, the zoom out effect to show all workspaces works properly. When I connect a monitor to my DisplayPort output and click Workspace Switcher, the laptop's built-in monitor shows a messed-up background (see attachment) and the external monitor shows no background. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: unity 4.20.0-0ubuntu2 ProcVersionSignature: Ubuntu 3.0.0-12.19-generic 3.0.4 Uname: Linux 3.0.0-12-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 1.23-0ubuntu2 Architecture: amd64 CompizPlugins: [core,bailer,detection,composite,opengl,decor,snap,grid,mousepoll,compiztoolbox,resize,imgpng,wall,unitymtgrabhandles,regex,gnomecompat,place,vpswitch,move,animation,workarounds,expo,session,ezoom,fade,scale,unityshell] CompositorRunning: compiz Date: Sat Oct 1 07:38:07 2011 DistUpgraded: Fresh install DistroCodename: oneiric DistroVariant: ubuntu GraphicsCard: Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] (rev 12) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:172a] InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Beta amd64+mac (20110921.2) MachineType: Hewlett-Packard HP EliteBook 8440p PccardctlIdent: Socket 0: product info: RICOH, Bay8Controller, , manfid: 0x, 0x function: 254 (unknown) PccardctlStatus: Socket 0: 3.3V 16-bit PC Card Subdevice 0 (function 0) bound to driver pata_pcmcia ProcEnviron: LANGUAGE=en_CA:en LANG=en_CA.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.0.0-12-generic root=UUID=26780926-1f18-4056-ae79-bf1656287393 ro quiet splash vt.handoff=7 SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/22/2009 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68CCU Ver. F.02 dmi.board.name: 172A dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 30.29 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68CCUVer.F.02:bd12/22/2009:svnHewlett-Packard:pnHPEliteBook8440p:pvr:rvnHewlett-Packard:rn172A:rvrKBCVersion30.29:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP EliteBook 8440p dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.6+bzr20110929-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.26-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 7.11-0ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 7.11-0ubuntu3 version.xserver-xorg: xserver-xorg 1:7.6+7ubuntu7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.6.0-1ubuntu13 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.14.99~git20110811.g93fc084-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.15.901-1ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:0.0.16+git20110411+8378443-1 To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/864037/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1283453] Re: window spread with too narrow titlebars on hig-dpi screen
** Changed in: unity (Ubuntu) Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1283453 Title: window spread with too narrow titlebars on hig-dpi screen Status in Unity: Fix Released Status in “unity” package in Ubuntu: Fix Released Bug description: Titlebars are currently cropped and don't completely display the text in spread mode, if the global scaling factor is set to 2. org.gnome.desktop.interface.scaling-factor = 2 org.gnome.desktop.interface.text-scaling-factor = 1.0 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.1.2+14.04.20140220-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-11.31-generic 3.13.3 Uname: Linux 3.13.0-11-generic x86_64 ApportVersion: 2.13.2-0ubuntu5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Sat Feb 22 15:04:07 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2014-02-02 (19 days ago) InstallationMedia: Ubuntu-GNOME 14.04 Trusty Tahr - Alpha amd64 (20140201) SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1283453/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1162886] Re: test-gtest [ FAILED ] TestIconLoader.TestGetManyIcons - segfaults at times.
** Changed in: unity (Ubuntu) Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1162886 Title: test-gtest [ FAILED ] TestIconLoader.TestGetManyIcons - segfaults at times. Status in Unity: Fix Released Status in “unity” package in Ubuntu: Fix Released Bug description: Stack trace: http://paste.ubuntu.com/5668678/ Full stack trace: http://paste.ubuntu.com/5668696/ Run: ./test-gtest --gtest_filter=*GetManyIcons* It also passes at times as well. *Update* I also just got this while restarting unity...so this seems a bit more serious then a failing unit test: http://paste.ubuntu.com/5667999/ I got it after doing a compiz --replace ccp, then opening the dash...though I can't reproduce it :(. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1162886/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1207669] Re: [MIR] Need binary package included in main.
** Changed in: unity (Ubuntu) Status: Fix Committed = Fix Released ** Changed in: unity Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1207669 Title: [MIR] Need binary package included in main. Status in Unity: Fix Released Status in “unity” package in Ubuntu: Fix Released Bug description: This source package is already in main, but in preparation for https://bugs.launchpad.net/bugs/1206268 I will need binary package unity-autopilot included in main as well. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1207669/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1097991] Re: Port to new barrier event API
** Changed in: unity (Ubuntu) Status: Fix Committed = Fix Released ** Changed in: unity (Ubuntu Raring) Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1097991 Title: Port to new barrier event API Status in Unity: Fix Released Status in “unity” package in Ubuntu: Fix Released Status in “unity” source package in Raring: Fix Released Bug description: The pointer barrier event API we've patched in to libXfixes has moved upstream in Xserver 1.14. However, the API has changed. The barrier events and pointer release API is now in the input lib, libXi as of version 1.6.99.1 . It should be reasonably easy to port to the new API: Peter Hutterer's blog post¹ describes how to use it. The main differences are that you need to add the barrier event mask to the XI event mask, rather than window event mask, and that it now uses generic events, so you need to allocate the event data before using it and free the event data after using it XGetEventData/XFreeEventData. ¹: http://who-t.blogspot.com.au/2012/12/whats-new-in-xi-23-pointer- barrier.html To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1097991/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1046125] Re: Decoration in spread windows should use the system font
** Changed in: unity (Ubuntu) Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1046125 Title: Decoration in spread windows should use the system font Status in Unity: Fix Released Status in “unity” package in Ubuntu: Fix Released Bug description: As title says. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1046125/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1117500] Re: test-unit needs to be ported to gtest
** Changed in: unity (Ubuntu) Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1117500 Title: test-unit needs to be ported to gtest Status in Unity: Fix Released Status in “unity” package in Ubuntu: Fix Released Bug description: Test-unit uses glib testing framework. It needs to be ported to gtest (google test). To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1117500/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1181367] Re: Alt+Tab switches between incorrect windows after some time of activity
** Changed in: unity (Ubuntu) Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1181367 Title: Alt+Tab switches between incorrect windows after some time of activity Status in Unity: Fix Released Status in Unity 7.0 series: Fix Committed Status in “unity” package in Ubuntu: Fix Released Status in “unity” source package in Raring: Fix Released Bug description: [Impact] Due to overflow, alt+tab between the same application becomes impossible] [Test Case] 1) Keep two windows of an app (say terminal) opened for some time, and another window of a different app 2) Focus one window terminal keeping the other terminal window below it 3) Press Alt+Tab Expected behavior 4) The other terminal window is focused Actual behavior: 4) Other opened application is selected instead. [Regression Potential] Low, types extended from int to long long. The code affected is the alt tab functionality. Due to an overflow, after some time of activity it's impossible to alt+tab between two windows of the same application. 1) Keep two windows of an app (say terminal) opened for some time, and another window of a different app 2) Focus one window terminal keeping the other terminal window below it 3) Press Alt+Tab Expected behavior 4) The other terminal window is focused Actual behavior: 4) Other opened application is selected instead. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1181367/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1059601] Re: [dash] Rendering flaw of ghost icons when a preview is open.
** Changed in: unity (Ubuntu) Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1059601 Title: [dash] Rendering flaw of ghost icons when a preview is open. Status in Unity: Fix Released Status in Unity 6.0 series: Triaged Status in “unity” package in Ubuntu: Fix Released Bug description: See the icon in the top-left corner of the attached screenshot. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1059601/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1059759] Re: Clicking on Workspace Switcher icon when the expo is showing, not always closes it
** Changed in: unity (Ubuntu) Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1059759 Title: Clicking on Workspace Switcher icon when the expo is showing, not always closes it Status in Unity: Fix Released Status in Unity 6.0 series: Fix Released Status in “unity” package in Ubuntu: Fix Released Bug description: Especially in multimonitor: 1) Click on the workspace switcher icon 2) The expo is shown 3) Click again on the workspace switcher icon Expected result: 4) The expo is hidden Actual result: 4) Expo is not hidden always (repeat this for all the monitors) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1059759/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1062316] Re: Glow border for selected window in scale mode does not draw correctly on the top corners
** Changed in: unity (Ubuntu) Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1062316 Title: Glow border for selected window in scale mode does not draw correctly on the top corners Status in Unity: Fix Released Status in “unity” package in Ubuntu: Fix Released Bug description: See the attached screenshot: the glow is not correctly applied to the top corners To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1062316/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1034616] Re: [Regression] Lowering window by middle click doesn't switch focus to raised window
** Changed in: unity (Ubuntu) Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1034616 Title: [Regression] Lowering window by middle click doesn't switch focus to raised window Status in Compiz: Fix Released Status in Compiz 0.9.9 series: Fix Committed Status in Unity: Fix Released Status in “compiz” package in Ubuntu: Fix Released Status in “unity” package in Ubuntu: Fix Released Bug description: Middle mouse click on title bar will lower window; but it does not switch the focus to the window which was raised above it. 1) Open a gedit app window 2) Open a calc app 3) Middle click the mouse on the calculator title bar. It should lower the calculator and raise the gedit window as well as switch the focus to gedit. But it doesnt switch the focus. See also: autopilot run unity.tests.test_panel.PanelGrabAreaTests.test_lower_the_maximized_window_works To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/1034616/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1011120] Re: Desktop Cube: Unity's top panel shadow gets deformed also and rendered on the desktop cube instead of sticking with the top panel when the cube gets activated
** Changed in: unity (Ubuntu) Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1011120 Title: Desktop Cube: Unity's top panel shadow gets deformed also and rendered on the desktop cube instead of sticking with the top panel when the cube gets activated Status in Unity: Fix Released Status in “unity” package in Ubuntu: Fix Released Bug description: The shadow of the main Unity panel on top should stay untouched, like the panel does, when using the desktop cube, instead of being rendered onto the cube. The situation gets even worse visually when Cube Reflection and Deformation is used additionally, because now the shadow does not deform with the cube, but stays in the same position of the original cube. Ubuntu 12.04, Compiz 0.9.7.8-0ubuntu1vvpreproposed2 To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1011120/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1043627] Re: [SRU] Add XIM Support to Nux
** Changed in: unity (Ubuntu) Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of DX Packages, which is subscribed to nux in Ubuntu. Matching subscriptions: dx-packages, dx-packages https://bugs.launchpad.net/bugs/1043627 Title: [SRU] Add XIM Support to Nux Status in Nux: Fix Released Status in Nux 2.0 series: Fix Committed Status in Unity: Fix Released Status in Unity 5.0 series: Fix Committed Status in “nux” package in Ubuntu: Confirmed Status in “unity” package in Ubuntu: Fix Released Status in “nux” source package in Quantal: Won't Fix Status in “unity” source package in Quantal: Won't Fix Status in “nux” source package in Raring: Confirmed Status in “unity” source package in Raring: Fix Committed Bug description: [Impact] As 12.04 is an LTS, many users decide to stay with that version until the next LTS version is available. Many of those users require different input methods to comfortably input characters in their language. We do support IBus for some of the languages, but others are still using XIM as the input framework. Those users cannot input in their language using their standard input methods. This means using the Dash and HUD is much more troublesome or even impossible in normal cases. We think that even though it is essentially a new feature, it can be thought that the lack of support for non-IBus additional input methods is a bug in a way. It is a big change, but with proper testing, we would ensure that the addition does not introduce any new regressions. This addition would make many MANY users happy, which can be seen at least by the number of affected people in LP: #983254. Also, the change is needed by OEM. It is a big change, but it's crucial for CJK - Kyrlin has voiced the proposition to use fctix as the default input method, which _needs_ XIM support in Nux and Unity. [Test Case] 1. Install fctix-pinyin 2. Run im-config and enable fctix as the default IM 3. Reboot your machine 4. Open the dash and input non-latin characters using fctix - Non latin characters (Chinese in this case) should appear on screen. [Regression Potential] In an impossible scenariu, broken IBus input or input in overall in Nux input fields. The good thing about the XIM support is that it's rather isolated, so potential breakage of the XIM code won't impact normal Nux workflow. Just XIM input might not work. The author of the code, Brandon, also mentions that new regression potential is low as the XIM code is not being used by default. As XIM is not the default, when IBus is present - without explicitly setting XIM in im-config, the XIM parts are not even accessed. [Other Info] The same functionality is already available in the newer Unity releases. Original description: Right now the only input method (IM) that works with Unity/Nux is IBus. This means anyone who uses a different IM would have to switch to IBus in order to type in their language. This is something that needs to be fixed and will make Unity/Nux friendlier to those who use different IMs. If you do not use an IM then this will not affect you. XIM was the very first IM framework for the X window system, which means most IMs are supported by it. A List of IMs that will be supported by this branch (There could be more): http://en.wikipedia.org/wiki/List_of_input_methods_for_UNIX_platforms All of those under XIM will now work in Unity and Nux with this branch. To manage notifications about this bug go to: https://bugs.launchpad.net/nux/+bug/1043627/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1240848] Re: ~/.cache/upstart takes up around 70GB of space due to unity and mediascanner
Ok, before rebooting, I just removed the offending file. It is growing at a rate of 1Gb every 10s or so. I will try logging out and in, and see if the log is still growing continuously ... -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1240848 Title: ~/.cache/upstart takes up around 70GB of space due to unity and mediascanner Status in Unity: New Status in “mediascanner” package in Ubuntu: Confirmed Status in “unity” package in Ubuntu: Confirmed Bug description: I just noticed that ~/.cache/upstart/ folder on my computer is taking up 69GB of space. Upon further investigation, I found out that mediascanner.log and unity-panel-service.log take 12GB and 54GB of space respectively. I'm not entirely sure if this is related to upstart as I had removed logrotate package because of a conflict. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1240848/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1240848] Re: ~/.cache/upstart takes up around 70GB of space due to unity and mediascanner
It just happened here. I will need to clean up and reboot. This is how it looks like lmilano@grisell:upstart$ ls -lh unity7.log -rw-r- 1 lmilano users 53G Nov 12 16:03 unity7.log lmilano@grisell:upstart$ tail unity7.log _xgeWireToEvent: Unknown extension 148, this should never happen. _xgeWireToEvent: Unknown extension 148, this should never happen. _xgeWireToEvent: Unknown extension 148, this should never happen. _xgeWireToEvent: Unknown extension 148, this should never happen. _xgeWireToEvent: Unknown extension 148, this should never happen. _xgeWireToEvent: Unknown extension 148, this should never happen. _xgeWireToEvent: Unknown extension 148, this should never happen. _xgeWireToEvent: Unknown extension 148, this should never happen. _xgeWireToEvent: Unknown extension 148, this should never happen. _xgeWireToEvent: Unknown extension 1lmilano@grisell:upstart$ -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1240848 Title: ~/.cache/upstart takes up around 70GB of space due to unity and mediascanner Status in Unity: New Status in “mediascanner” package in Ubuntu: Confirmed Status in “unity” package in Ubuntu: Confirmed Bug description: I just noticed that ~/.cache/upstart/ folder on my computer is taking up 69GB of space. Upon further investigation, I found out that mediascanner.log and unity-panel-service.log take 12GB and 54GB of space respectively. I'm not entirely sure if this is related to upstart as I had removed logrotate package because of a conflict. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1240848/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1317253] Re: UI scaling and font scaling sometime get confused/change at random.
*** This bug is a duplicate of bug 1310316 *** https://bugs.launchpad.net/bugs/1310316 Ditto what ~james-fsck says. The problem is that the adjustment above or below 1.0 is incremented each time unity resets, so if someone chose smaller, it keeps getting smaller, or if someone chooses bigger, the font keeps getting bigger. The tweak tool is a temporarily workaround, but the problem is in the way the display preferences interacts with the font sizes - i.e. it keeps re-applying the change. -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1317253 Title: UI scaling and font scaling sometime get confused/change at random. Status in Unity: New Status in Unity Tweak Tool: Invalid Status in “unity” package in Ubuntu: Confirmed Bug description: I have a Lenovo Yoga 2 Pro, with a 13.3 screen running at 3200x1800 pixels... I bought this partly to test out the UI scaling in Unity!... and I have to say it's very awesome (both the screen and the UI scaling)... however I have encountered a strange problem. Seemingly at random, I have so far 3 times in 10 days had the font size (not UI size) suddenly jump to something much too large. UI scaling for the display is set at 1.38x and this is quite perfect for me, it sure means no one will be able to read my screen over my shoulder, but I that's fine! I had to install a Firefox plugin to apply scaling there, but I realise why that is. Anyway... I installed ubuntu-tweak and discovered that the large fonts were due to the Text Scaling Factor having jumped up to a number above 2.5... I also discovered that I could not move the slider because every time I moved it the fonts re-scaled the slider moved and lost mouse focus... and the slider reset to where it was to begin with... I clicked the button on the right to return to 1.0, and it returned to 1.4, which I assume is representative of the 1.38 I set in the screen scaling... but I have no explanation for why it suddenly jumped (when I logged out and back in) from 1.4 to something like 2.5.).. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.0+14.04.20140423-0ubuntu1.2 ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Wed May 7 20:55:53 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2014-04-28 (8 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1317253/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1317253] Re: UI scaling and font scaling sometime get confused/change at random.
*** This bug is a duplicate of bug 1310316 *** https://bugs.launchpad.net/bugs/1310316 To reproduce this issue, simply type setsid unity from the command line to see the font size keep deviating from the desired size. Running, gsettings set com.canonical.Unity.Interface text-scale-factor 1.25 will restore the size to 1.25, for example, if that is the desired size. -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1317253 Title: UI scaling and font scaling sometime get confused/change at random. Status in Unity: New Status in Unity Tweak Tool: Invalid Status in “unity” package in Ubuntu: Confirmed Bug description: I have a Lenovo Yoga 2 Pro, with a 13.3 screen running at 3200x1800 pixels... I bought this partly to test out the UI scaling in Unity!... and I have to say it's very awesome (both the screen and the UI scaling)... however I have encountered a strange problem. Seemingly at random, I have so far 3 times in 10 days had the font size (not UI size) suddenly jump to something much too large. UI scaling for the display is set at 1.38x and this is quite perfect for me, it sure means no one will be able to read my screen over my shoulder, but I that's fine! I had to install a Firefox plugin to apply scaling there, but I realise why that is. Anyway... I installed ubuntu-tweak and discovered that the large fonts were due to the Text Scaling Factor having jumped up to a number above 2.5... I also discovered that I could not move the slider because every time I moved it the fonts re-scaled the slider moved and lost mouse focus... and the slider reset to where it was to begin with... I clicked the button on the right to return to 1.0, and it returned to 1.4, which I assume is representative of the 1.38 I set in the screen scaling... but I have no explanation for why it suddenly jumped (when I logged out and back in) from 1.4 to something like 2.5.).. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.0+14.04.20140423-0ubuntu1.2 ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Wed May 7 20:55:53 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2014-04-28 (8 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1317253/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1310316] Re: Text scaling factor changing unexpectedly
I don't have the tweak tool installed. I'm using HiDPI hardware. I set
the scale to 1.12 in the display preferences option, and each time I
start unity (or run setsid unity) the font increases in size. It seems
that in the display preferences, it needs to be set to 1.0 for the
constant font size changing to not occur. I've therefore set this back
to 1.0, and instead set up a start-up script to gsettings set
com.ubuntu.user-interface scale-factor {'eDP1': 10} instead.
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to unity in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1310316
Title:
Text scaling factor changing unexpectedly
Status in Unity:
Confirmed
Status in “unity” package in Ubuntu:
Incomplete
Bug description:
I have a MacBook pro with a Retina display. I have set the Scale for
menu and title bars setting (into Settings Displays) to 1.5 to
make the UI looks good on my screen. That works very well. But
sometimes, usually after logging, all the fonts of the UI become much
bigger.
When that happen I open unity tweat tool and notice that the text
scaling factor changed to 2.25. If I reset it to 1 the all the fonts
go back to normal.
The problem does not happen all the time. I would say it happen one
time out of three logging. It may also happen when installing
applications from the software center. I have yet to find a procedure
to reproduce it all the times.
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: unity 7.2.0+14.04.20140416-0ubuntu1
ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
Uname: Linux 3.13.0-24-generic x86_64
NonfreeKernelModules: wl nvidia
.proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory:
'/proc/driver/nvidia/gpus/0'
.proc.driver.nvidia.registry: Binary:
.proc.driver.nvidia.version:
NVRM version: NVIDIA UNIX x86_64 Kernel Module 331.38 Wed Jan 8 19:32:30
PST 2014
GCC version: gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1)
.tmp.unity.support.test.0:
ApportVersion: 2.14.1-0ubuntu3
Architecture: amd64
CompizPlugins: No value set for
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CurrentDesktop: Unity
Date: Sun Apr 20 18:21:02 2014
DistUpgraded: Fresh install
DistroCodename: trusty
DistroVariant: ubuntu
DkmsStatus:
bbswitch, 0.7, 3.13.0-24-generic, x86_64: installed
bcmwl, 6.30.223.141+bdcom, 3.13.0-24-generic, x86_64: installed
nvidia-331, 331.38, 3.13.0-24-generic, x86_64: installed
GraphicsCard:
NVIDIA Corporation GK107M [GeForce GT 650M Mac Edition] [10de:0fd5] (rev a1)
(prog-if 00 [VGA controller])
Subsystem: Apple Inc. Device [106b:00f2]
InstallationDate: Installed on 2014-04-19 (1 days ago)
InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64+mac
(20140417)
MachineType: Apple Inc. MacBookPro10,1
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic
root=UUID=3d5a4115-5e15-4eca-bd1c-0bee2543a1cb ro quiet splash
SourcePackage: unity
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/21/2012
dmi.bios.vendor: Apple Inc.
dmi.bios.version: MBP101.88Z.00EE.B03.1212211437
dmi.board.asset.tag: Base Board Asset Tag#
dmi.board.name: Mac-C3EC7CD22292981F
dmi.board.vendor: Apple Inc.
dmi.board.version: MacBookPro10,1
dmi.chassis.type: 10
dmi.chassis.vendor: Apple Inc.
dmi.chassis.version: Mac-C3EC7CD22292981F
dmi.modalias:
dmi:bvnAppleInc.:bvrMBP101.88Z.00EE.B03.1212211437:bd12/21/2012:svnAppleInc.:pnMacBookPro10,1:pvr1.0:rvnAppleInc.:rnMac-C3EC7CD22292981F:rvrMacBookPro10,1:cvnAppleInc.:ct10:cvrMac-C3EC7CD22292981F:
dmi.product.name: MacBookPro10,1
dmi.product.version: 1.0
dmi.sys.vendor: Apple Inc.
version.compiz: compiz 1:0.9.11+14.04.20140409-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-4ubuntu5
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-4ubuntu5
version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3
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: Sun Apr 20 18:04:05 2014
xserver.configfile: default
xserver.errors: open /dev/fb0: No such file or directory
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
xserver.version: 2:1.15.1-0ubuntu2
To manage notifications about this bug go to:
[Dx-packages] [Bug 1240848] Re: ~/.cache/upstart takes up around 70GB of space due to unity and mediascanner
To be clear: I removed the file before rebooting, but it got regenerated and refilled at a furious pace, with the same message: _xgeWireToEvent: Unknown extension 148, this should never happen. At that time, top was reporting upstart as the most process, obviously caught in an infinite loop throwing this erroor about the extension 148. It seems like this is the bug: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1369113 And it seems that the spamming, at least, would be removed with an upgrade of libXext to 1.3.3. Or at least, it would be nice to backport the relevant patch http://patchwork.freedesktop.org/patch/22124/ -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1240848 Title: ~/.cache/upstart takes up around 70GB of space due to unity and mediascanner Status in Unity: New Status in “mediascanner” package in Ubuntu: Confirmed Status in “unity” package in Ubuntu: Confirmed Bug description: I just noticed that ~/.cache/upstart/ folder on my computer is taking up 69GB of space. Upon further investigation, I found out that mediascanner.log and unity-panel-service.log take 12GB and 54GB of space respectively. I'm not entirely sure if this is related to upstart as I had removed logrotate package because of a conflict. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1240848/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1391954] Re: indicator-sound not running on first boot
** Package changed: indicator-sound (Ubuntu) = ubuntu-touch-session (Ubuntu) ** Changed in: ubuntu-touch-session (Ubuntu) Assignee: (unassigned) = Ted Gould (ted) ** Changed in: ubuntu-touch-session (Ubuntu) Status: New = In Progress -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-sound in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1391954 Title: indicator-sound not running on first boot Status in “ubuntu-touch-session” package in Ubuntu: In Progress Bug description: Steps to reproduce: 1. Boot the device after a fresh flash with --wipe or --bootstrap 2. Complete the wizard steps 3. Check the indicators for the presence of the sound indicator Expected result: Sound indicator is present and running Actual result: Indicator is not present. There is a placeholder for it on the menu as shown in http://people.canonical.com/~brendan-donegan/indicator- sound.png Running 'status indicator-sound' shows it is stopped ProblemType: Bug DistroRelease: Ubuntu RTM 14.09 Package: indicator-sound 12.10.2+14.10.20141021~rtm-0ubuntu1 Uname: Linux 3.4.67 armv7l ApportVersion: 2.14.7-0ubuntu8 Architecture: armhf Date: Wed Nov 12 16:26:28 2014 InstallationDate: Installed on 2014-11-12 (0 days ago) InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20141112-135345) SourcePackage: indicator-sound UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-touch-session/+bug/1391954/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1391954] Re: indicator-sound not running on first boot
** Branch linked: lp:~ted/ubuntu-touch-session/indicator-sound- override-v2 -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-sound in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1391954 Title: indicator-sound not running on first boot Status in “ubuntu-touch-session” package in Ubuntu: In Progress Bug description: Steps to reproduce: 1. Boot the device after a fresh flash with --wipe or --bootstrap 2. Complete the wizard steps 3. Check the indicators for the presence of the sound indicator Expected result: Sound indicator is present and running Actual result: Indicator is not present. There is a placeholder for it on the menu as shown in http://people.canonical.com/~brendan-donegan/indicator- sound.png Running 'status indicator-sound' shows it is stopped ProblemType: Bug DistroRelease: Ubuntu RTM 14.09 Package: indicator-sound 12.10.2+14.10.20141021~rtm-0ubuntu1 Uname: Linux 3.4.67 armv7l ApportVersion: 2.14.7-0ubuntu8 Architecture: armhf Date: Wed Nov 12 16:26:28 2014 InstallationDate: Installed on 2014-11-12 (0 days ago) InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20141112-135345) SourcePackage: indicator-sound UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-touch-session/+bug/1391954/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1389008] Re: Often fails to connect to Pulseaudio and unity-notifications (results in missing volume notifications and improper volume control)
** Branch linked: lp:~ted/ubuntu-touch-session/indicator-sound- override-v2 -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-sound in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1389008 Title: Often fails to connect to Pulseaudio and unity-notifications (results in missing volume notifications and improper volume control) Status in “indicator-sound” package in Ubuntu: Invalid Status in “ubuntu-touch-session” package in Ubuntu: Fix Released Status in “unity8” package in Ubuntu: Confirmed Status in “indicator-sound” package in Ubuntu RTM: Invalid Status in “ubuntu-touch-session” package in Ubuntu RTM: Confirmed Status in “unity8” package in Ubuntu RTM: New Bug description: Often after boot indicator-sound fails to connect to Pulseaudio and to unity-notifications using libnotify. Therefore, volume notifications aren't shown and changes to the volume role go unnoticed, which then results in improper volume control. As already mentioned in the original bug description, running restart indicator-sound resolves the issue. Original description: Happens often after phone boot where changing volume by touch or by phone buttons. Volume correctly changes, but the org.freedesktop.Notifications popup isn't displayed. The problem seems fixes itself if you run restart indicator-sound, so maybe there's an issue with i-sound and unity-notifications starting at the same time, with the former querying the latter's capabilities before it's ready for business? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-sound/+bug/1389008/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1357681] Re: System tray icons for Owncloud, Insync and Dropbox disapear after reboot
[Expired for unity (Ubuntu) because there has been no activity for 60 days.] ** Changed in: unity (Ubuntu) Status: Incomplete = Expired -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1357681 Title: System tray icons for Owncloud, Insync and Dropbox disapear after reboot Status in Unity: Expired Status in “unity” package in Ubuntu: Expired Bug description: I have used 3 clients for file synchronization: Owncloud Client, Dropbox and Insync. Apparently the bug applies to all of the applications. Within the last 2-3 months the icons for the the applications have started to disappear from the system tray after a reboot. The icons doesn't reappear when (re)launching the applications from dash or terminal. However if I run killall owncloud; owncloud the icon for owncloud (re)appears. The icons for Dropbox and Insync also (re)appears when using killall before launching. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.2+14.04.20140714-0ubuntu1.1 ProcVersionSignature: Ubuntu 3.13.0-34.60-generic 3.13.11.4 Uname: Linux 3.13.0-34-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.3 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Sat Aug 16 11:33:31 2014 DistUpgraded: 2014-02-21 20:58:31,099 DEBUG enabling apt cron job DistroCodename: trusty DistroVariant: ubuntu GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:060a] InstallationDate: Installed on 2014-01-15 (212 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) MachineType: Dell Inc. XPS13 9333 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-34-generic root=UUID=0a466d6e-f0bc-4c34-bcc1-9649cb723803 ro quiet splash vt.handoff=7 SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2014-02-21 (175 days ago) dmi.bios.date: 12/11/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A02 dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA02:bd12/11/2013:svnDellInc.:pnXPS139333:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct8:cvr0.1: dmi.product.name: XPS13 9333 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.11.2+14.04.20140714-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.54-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.2.2-0intel1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.2.2-0intel1 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.911-0intel1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Sat Aug 16 09:12:00 2014 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id4933 vendor CMN xserver.version: 2:1.15.1-0ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1357681/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1357681] Re: System tray icons for Owncloud, Insync and Dropbox disapear after reboot
[Expired for Unity because there has been no activity for 60 days.] ** Changed in: unity Status: Incomplete = Expired -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1357681 Title: System tray icons for Owncloud, Insync and Dropbox disapear after reboot Status in Unity: Expired Status in “unity” package in Ubuntu: Expired Bug description: I have used 3 clients for file synchronization: Owncloud Client, Dropbox and Insync. Apparently the bug applies to all of the applications. Within the last 2-3 months the icons for the the applications have started to disappear from the system tray after a reboot. The icons doesn't reappear when (re)launching the applications from dash or terminal. However if I run killall owncloud; owncloud the icon for owncloud (re)appears. The icons for Dropbox and Insync also (re)appears when using killall before launching. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.2+14.04.20140714-0ubuntu1.1 ProcVersionSignature: Ubuntu 3.13.0-34.60-generic 3.13.11.4 Uname: Linux 3.13.0-34-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.3 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Sat Aug 16 11:33:31 2014 DistUpgraded: 2014-02-21 20:58:31,099 DEBUG enabling apt cron job DistroCodename: trusty DistroVariant: ubuntu GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:060a] InstallationDate: Installed on 2014-01-15 (212 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) MachineType: Dell Inc. XPS13 9333 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-34-generic root=UUID=0a466d6e-f0bc-4c34-bcc1-9649cb723803 ro quiet splash vt.handoff=7 SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2014-02-21 (175 days ago) dmi.bios.date: 12/11/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A02 dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA02:bd12/11/2013:svnDellInc.:pnXPS139333:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct8:cvr0.1: dmi.product.name: XPS13 9333 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.11.2+14.04.20140714-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.54-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.2.2-0intel1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.2.2-0intel1 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.911-0intel1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Sat Aug 16 09:12:00 2014 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id4933 vendor CMN xserver.version: 2:1.15.1-0ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1357681/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
