[Dx-packages] [Bug 1303377] 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/1303377/+attachment/4069741/+files/CoreDump.gz ** Attachment removed: Disassembly.txt https://bugs.launchpad.net/bugs/1303377/+attachment/4069743/+files/Disassembly.txt ** Attachment removed: ProcMaps.txt https://bugs.launchpad.net/bugs/1303377/+attachment/4069744/+files/ProcMaps.txt ** Attachment removed: ProcStatus.txt https://bugs.launchpad.net/bugs/1303377/+attachment/4069745/+files/ProcStatus.txt ** Attachment removed: Registers.txt https://bugs.launchpad.net/bugs/1303377/+attachment/4069746/+files/Registers.txt ** Attachment removed: Stacktrace.txt https://bugs.launchpad.net/bugs/1303377/+attachment/4069747/+files/Stacktrace.txt ** Attachment removed: ThreadStacktrace.txt https://bugs.launchpad.net/bugs/1303377/+attachment/4069748/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of bug 1199571 compiz crashed with SIGSEGV in af_latin_hints_compute_edges() ** Information type changed from Private to Public ** Tags removed: need-i386-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/1303377 Title: compiz crashed with SIGSEGV in FT_Load_Glyph() Status in “unity” package in Ubuntu: New Bug description: 14.04 compiz crashes repeatedly when viewing list of programs. ProblemType: Crash DistroRelease: Ubuntu 14.04 Package: unity 7.2.0+14.04.20140403-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-23.45-generic 3.13.8 Uname: Linux 3.13.0-23-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu1 Architecture: i386 CrashCounter: 1 CurrentDesktop: Unity Date: Sun Apr 6 11:13:26 2014 ExecutablePath: /usr/bin/compiz InstallationDate: Installed on 2012-08-14 (600 days ago) InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release i386 (20111012) ProcCmdline: compiz ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0xb19f70e8:mov%edx,0xc(%eax) PC (0xb19f70e8) ok source %edx ok destination 0xc(%eax) (0x000c) 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/i386-linux-gnu/libfreetype.so.6 ?? () from /usr/lib/i386-linux-gnu/libfreetype.so.6 ?? () from /usr/lib/i386-linux-gnu/libfreetype.so.6 ?? () from /usr/lib/i386-linux-gnu/libfreetype.so.6 FT_Load_Glyph () from /usr/lib/i386-linux-gnu/libfreetype.so.6 Title: compiz crashed with SIGSEGV in FT_Load_Glyph() UpgradeStatus: Upgraded to trusty on 2014-04-03 (3 days ago) UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1303377/+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 1303327] 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/1303327/+attachment/4069414/+files/CoreDump.gz ** Attachment removed: Disassembly.txt https://bugs.launchpad.net/bugs/1303327/+attachment/4069416/+files/Disassembly.txt ** Attachment removed: ProcMaps.txt https://bugs.launchpad.net/bugs/1303327/+attachment/4069417/+files/ProcMaps.txt ** Attachment removed: ProcStatus.txt https://bugs.launchpad.net/bugs/1303327/+attachment/4069418/+files/ProcStatus.txt ** Attachment removed: Registers.txt https://bugs.launchpad.net/bugs/1303327/+attachment/4069419/+files/Registers.txt ** Attachment removed: Stacktrace.txt https://bugs.launchpad.net/bugs/1303327/+attachment/4069420/+files/Stacktrace.txt ** Attachment removed: ThreadStacktrace.txt https://bugs.launchpad.net/bugs/1303327/+attachment/4069421/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of bug 1199571 compiz crashed with SIGSEGV in af_latin_hints_compute_edges() ** 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/1303327 Title: compiz crashed with SIGSEGV in FT_Load_Glyph() Status in “unity” package in Ubuntu: New Bug description: Clicked on the HUB button, and compiz reset. ProblemType: Crash DistroRelease: Ubuntu 14.04 Package: unity 7.2.0+14.04.20140403-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-23.45-generic 3.13.8 Uname: Linux 3.13.0-23-generic x86_64 ApportVersion: 2.14.1-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Sun Apr 6 13:01:50 2014 ExecutablePath: /usr/bin/compiz ProcCmdline: compiz ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, user) XDG_RUNTIME_DIR=set LANG=en_GB.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7f2def3869ec:mov%rbx,0x18(%rdx) PC (0x7f2def3869ec) ok source %rbx ok destination 0x18(%rdx) (0x0018) not located in a known VMA region (needed writable region)! 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: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1303327/+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 1303441] Re: compiz crashed with SIGSEGV in g_mount_spec_to_dbus_with_path()
*** This bug is a duplicate of bug 1047517 *** https://bugs.launchpad.net/bugs/1047517 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 #1047517, 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/1303441/+attachment/4070165/+files/CoreDump.gz ** Attachment removed: Disassembly.txt https://bugs.launchpad.net/bugs/1303441/+attachment/4070167/+files/Disassembly.txt ** Attachment removed: ProcMaps.txt https://bugs.launchpad.net/bugs/1303441/+attachment/4070168/+files/ProcMaps.txt ** Attachment removed: ProcStatus.txt https://bugs.launchpad.net/bugs/1303441/+attachment/4070169/+files/ProcStatus.txt ** Attachment removed: Registers.txt https://bugs.launchpad.net/bugs/1303441/+attachment/4070170/+files/Registers.txt ** Attachment removed: Stacktrace.txt https://bugs.launchpad.net/bugs/1303441/+attachment/4070171/+files/Stacktrace.txt ** Attachment removed: ThreadStacktrace.txt https://bugs.launchpad.net/bugs/1303441/+attachment/4070172/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of bug 1047517 compiz crashed with SIGSEGV in g_mount_spec_to_dbus_with_path() ... from unity::IconLoader::Impl::IconLoaderTask::LoaderJobFunc() ** 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/1303441 Title: compiz crashed with SIGSEGV in g_mount_spec_to_dbus_with_path() Status in “unity” package in Ubuntu: New Bug description: This Crash Report showed up in Ubuntu 14.04 .. ProblemType: Crash DistroRelease: Ubuntu 14.04 Package: unity 7.2.0+14.04.20140403-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-23.45-generic 3.13.8 Uname: Linux 3.13.0-23-generic x86_64 ApportVersion: 2.14.1-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Sun Apr 6 11:47:29 2014 ExecutablePath: /usr/bin/compiz InstallationDate: Installed on 2014-04-04 (2 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Daily amd64 (20140403) ProcCmdline: compiz ProcEnviron: LANGUAGE=en_CA:en PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_CA.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7f7735cc0341 g_mount_spec_to_dbus_with_path+49: mov0x8(%rax),%edx PC (0x7f7735cc0341) ok source 0x8(%rax) (0x0008) not located in a known VMA region (needed readable region)! destination %edx ok Stack memory exhausted (SP below stack segment) SegvReason: reading NULL VMA Signal: 11 SourcePackage: unity StacktraceTop: g_mount_spec_to_dbus_with_path () from /usr/lib/x86_64-linux-gnu/gvfs/libgvfscommon.so ?? () from /usr/lib/x86_64-linux-gnu/gio/modules/libgvfsdbus.so ?? () from /usr/lib/x86_64-linux-gnu/gio/modules/libgvfsdbus.so ?? () from /usr/lib/x86_64-linux-gnu/gio/modules/libgvfsdbus.so g_file_load_contents () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 Title: compiz crashed with SIGSEGV in g_mount_spec_to_dbus_with_path() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1303441/+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 1303362] Re: compiz crashed with SIGSEGV in FT_Outline_Decompose()
*** This bug is a duplicate of bug 1284844 *** https://bugs.launchpad.net/bugs/1284844 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 #1284844, 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/1303362/+attachment/4069619/+files/CoreDump.gz ** Attachment removed: Disassembly.txt https://bugs.launchpad.net/bugs/1303362/+attachment/4069621/+files/Disassembly.txt ** Attachment removed: ProcMaps.txt https://bugs.launchpad.net/bugs/1303362/+attachment/4069623/+files/ProcMaps.txt ** Attachment removed: ProcStatus.txt https://bugs.launchpad.net/bugs/1303362/+attachment/4069624/+files/ProcStatus.txt ** Attachment removed: Registers.txt https://bugs.launchpad.net/bugs/1303362/+attachment/4069625/+files/Registers.txt ** Attachment removed: Stacktrace.txt https://bugs.launchpad.net/bugs/1303362/+attachment/4069626/+files/Stacktrace.txt ** Attachment removed: ThreadStacktrace.txt https://bugs.launchpad.net/bugs/1303362/+attachment/4069627/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 1284844 ** 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/1303362 Title: compiz crashed with SIGSEGV in FT_Outline_Decompose() Status in “unity” package in Ubuntu: New Bug description: Using unity to search for an application, and the screen became unresonsive ProblemType: Crash DistroRelease: Ubuntu 14.04 Package: unity 7.2.0+14.04.20140403-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-23.45-generic 3.13.8 Uname: Linux 3.13.0-23-generic x86_64 ApportVersion: 2.14.1-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Sun Apr 6 14:06:41 2014 ExecutablePath: /usr/bin/compiz ProcCmdline: compiz SegvAnalysis: Segfault happened at: 0x7f8ce05a03af:cmp%rcx,(%rax) PC (0x7f8ce05a03af) ok source %rcx ok destination (%rax) (0x0100) 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_Outline_Decompose () from /usr/lib/x86_64-linux-gnu/libfreetype.so.6 Title: compiz crashed with SIGSEGV in FT_Outline_Decompose() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1303362/+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 1303393] Re: x11vnc + open Dash in VNC session = compiz crash
*** This bug is a duplicate of bug 1022203 *** https://bugs.launchpad.net/bugs/1022203 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 #1022203, 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/1303393/+attachment/4069888/+files/CoreDump.gz ** Attachment removed: Disassembly.txt https://bugs.launchpad.net/bugs/1303393/+attachment/4069890/+files/Disassembly.txt ** Attachment removed: ProcMaps.txt https://bugs.launchpad.net/bugs/1303393/+attachment/4069892/+files/ProcMaps.txt ** Attachment removed: ProcStatus.txt https://bugs.launchpad.net/bugs/1303393/+attachment/4069893/+files/ProcStatus.txt ** Attachment removed: Registers.txt https://bugs.launchpad.net/bugs/1303393/+attachment/4069894/+files/Registers.txt ** Attachment removed: Stacktrace.txt https://bugs.launchpad.net/bugs/1303393/+attachment/4069895/+files/Stacktrace.txt ** Attachment removed: ThreadStacktrace.txt https://bugs.launchpad.net/bugs/1303393/+attachment/4069896/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 1022203 ** 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/1303393 Title: x11vnc + open Dash in VNC session = compiz crash Status in “unity” package in Ubuntu: New Bug description: I installed X11VNC server, started it with default settings (except disabled SSL and enabled Accept connections, then connected from VNC Viewer Android application, after several minutes tied to open Dash menu - no reaction. Then I used Win key - no reaction. And as result compiz crashed. Ubuntu 14.04 Unity 7.2.0 Compiz 0.9.11 x11vnc 0.9.13 Sorry for my English ProblemType: Crash DistroRelease: Ubuntu 14.04 Package: unity 7.2.0+14.04.20140403-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-19.40-generic 3.13.6 Uname: Linux 3.13.0-19-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Sun Apr 6 18:38:33 2014 ExecutablePath: /usr/bin/compiz InstallationDate: Installed on 2014-01-02 (94 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140101) ProcCmdline: compiz SegvAnalysis: Segfault happened at: 0x7f3586bcb677 _ZNK10CompWindow2idEv+7: mov 0x30(%rax),%rax PC (0x7f3586bcb677) ok source 0x30(%rax) (0x0031) not located in a known VMA region (needed readable region)! destination %rax ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: unity StacktraceTop: CompWindow::id() const () from /usr/lib/libcompiz_core.so.ABI-20140123 unity::UnityWindow::glPaint(GLWindowPaintAttrib const, GLMatrix const, CompRegion const, unsigned int) () from /usr/lib/compiz/libunityshell.so GLWindow::glPaint(GLWindowPaintAttrib const, GLMatrix const, CompRegion const, unsigned int) () from /usr/lib/compiz/libopengl.so PrivateGLScreen::paintOutputRegion(GLMatrix const, CompRegion const, CompOutput*, unsigned int) () from /usr/lib/compiz/libopengl.so GLScreen::glPaintOutput(GLScreenPaintAttrib const, GLMatrix const, CompRegion const, CompOutput*, unsigned int) () from /usr/lib/compiz/libopengl.so Title: compiz crashed with SIGSEGV in CompWindow::id() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1303393/+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 1283236] Re: Alarms are triggered in UTC tz despite saving in local tz
Yes, Charles, I'm giving the date to qtorganizer-eds transformed into UTC (i.e. 3pm Local time === 3pm UTC). Now, all tasks.ics entries are in UTC. But I guess we agreed that it is OK to have that. If not, eds plugin must do sthing with the time. -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-datetime in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1283236 Title: Alarms are triggered in UTC tz despite saving in local tz Status in The Date and Time Indicator: In Progress Status in Clock application for Ubuntu devices: Invalid Status in Ubuntu UI Toolkit: In Progress Status in “indicator-datetime” package in Ubuntu: Confirmed Status in “qtorganizer5-eds” package in Ubuntu: Confirmed Status in “ubuntu-ui-toolkit” package in Ubuntu: New Bug description: Setting an alarm in the local timezone is not respected by the system since the alarms is triggered in the equivalent UTC timezone. Mako build 200, 205 Steps to reproduce: 1. Ensure that phone timezone is something other than UTC. For instance eastern tz (UTC-5) 2. Set an alarm for 3:00 PM in the ubuntu clock app. 3. Indicator shows a pending alarm for 3:00 PM 4. Check a minute or so later, indicator shows an alarm pending for 8:00 PM What happens: The alarm does not go off at 3:00 PM. Instead it triggers at 8:00 PM What should happen: The alarm is triggered at 3:00 PM To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-datetime/+bug/1283236/+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 1303598] 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/1303598/+attachment/4071092/+files/CoreDump.gz ** Attachment removed: Disassembly.txt https://bugs.launchpad.net/bugs/1303598/+attachment/4071094/+files/Disassembly.txt ** Attachment removed: ProcMaps.txt https://bugs.launchpad.net/bugs/1303598/+attachment/4071095/+files/ProcMaps.txt ** Attachment removed: ProcStatus.txt https://bugs.launchpad.net/bugs/1303598/+attachment/4071096/+files/ProcStatus.txt ** Attachment removed: Registers.txt https://bugs.launchpad.net/bugs/1303598/+attachment/4071097/+files/Registers.txt ** Attachment removed: Stacktrace.txt https://bugs.launchpad.net/bugs/1303598/+attachment/4071098/+files/Stacktrace.txt ** Attachment removed: ThreadStacktrace.txt https://bugs.launchpad.net/bugs/1303598/+attachment/4071099/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of bug 1199571 compiz crashed with SIGSEGV in af_latin_hints_compute_edges() ** 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/1303598 Title: compiz crashed with SIGSEGV in FT_Load_Glyph() Status in “unity” package in Ubuntu: New Bug description: Opened dash and typed subl trying to type sublime but it froze half way through. I did nothing and the dash crashed by itself and unity totally disappeared and restarted. sayth:~$ lsb_release -rd Description: Ubuntu Trusty Tahr (development branch) Release: 14.04 ProblemType: Crash DistroRelease: Ubuntu 14.04 Package: unity 7.2.0+14.04.20140403-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-23.45-generic 3.13.8 Uname: Linux 3.13.0-23-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.14.1-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Mon Apr 7 16:14:01 2014 ExecutablePath: /usr/bin/compiz InstallationDate: Installed on 2014-04-03 (3 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Daily amd64 (20140403) ProcCmdline: compiz ProcEnviron: LANGUAGE=en_AU:en PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_AU.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7fb16a0a2860:mov%rdx,0x10(%rax) PC (0x7fb16a0a2860) 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: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1303598/+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 1303317] [NEW] dots not lined up on lock screen
You have been subscribed to a public bug: I understand a similar bug was fixed a week or two ago involving the login screen, whereby the dots pattern did not line up properly with the new default wallpaper. Now when locking the screen I have noticed that the dots pattern is in the wrong place, if the right place is where they are on the login screen. They also go through the Ubuntu 14.04 LTS logo in the bottom left rather than around it, and the central dot on the screen is slightly below the central point of the default wallpaper, as opposed to rows above and below the centre as in the login screen. I am running through an NVIDEA GTX 650 with screen resolution 1920x1080. This doesn't seem to be limited to me though, as you can see the same thing in the video http://www.youtube.com/watch?feature=player_detailpagev=ZAREcpd6_eE#t=100 by Joey Sneddon (1:40) Finally, I'm reporting this against lightdm as it seems the most appropriate package; please advise if it is not! ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: lightdm 1.9.14-0ubuntu2 ProcVersionSignature: Ubuntu 3.11.0-19.33-generic 3.11.10.5 Uname: Linux 3.11.0-19-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Sun Apr 6 12:24:02 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2014-01-11 (84 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) SourcePackage: lightdm UpgradeStatus: Upgraded to trusty on 2014-04-01 (4 days ago) ** Affects: unity (Ubuntu) Importance: Low Status: New ** Tags: amd64 apport-bug trusty -- dots not lined up on lock screen https://bugs.launchpad.net/bugs/1303317 You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. -- 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 1295981] Re: unity-panel-service crashed with SIGSEGV in gtk_menu_tracker_remove_items()
** Changed in: unity Milestone: None = 7.2.1 -- 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/1295981 Title: unity-panel-service crashed with SIGSEGV in gtk_menu_tracker_remove_items() Status in Unity: New Status in “unity” package in Ubuntu: Confirmed Bug description: 1. get an app to stop responding (ie the window gets dimmed) 2. wait for it to recover 3. notice that it has no menus now (is there a bug somewhere for that?) 4. close the app 5. crash (Note: I think this is chain of events, I haven't been able to reproduce) ProblemType: Crash DistroRelease: Ubuntu 14.04 Package: unity-services 7.1.2+14.04.20140320.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-18.38-generic 3.13.6 Uname: Linux 3.13.0-18-generic x86_64 ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Sat Mar 22 19:09:26 2014 ExecutablePath: /usr/lib/unity/unity-panel-service InstallationDate: Installed on 2013-06-22 (273 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Alpha amd64 (20130621) ProcCmdline: /usr/lib/unity/unity-panel-service ProcEnviron: PATH=(custom, no user) LANGUAGE=en_AU:en XDG_RUNTIME_DIR=set LANG=en_AU.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7ff2bf1b3ffc:mov(%rdi),%rbx PC (0x7ff2bf1b3ffc) ok source (%rdi) (0x) not located in a known VMA region (needed readable region)! destination %rbx ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: unity StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 ffi_call_unix64 () from /usr/lib/x86_64-linux-gnu/libffi.so.6 ffi_call () from /usr/lib/x86_64-linux-gnu/libffi.so.6 g_cclosure_marshal_generic () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: unity-panel-service crashed with SIGSEGV in ffi_call_unix64() UpgradeStatus: Upgraded to trusty on 2013-12-05 (106 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1295981/+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 1303317] Re: dots not lined up on lock screen
Thank you for your bug report. The lock screen is provided by unity and not lightdm, reassigning there ** Package changed: lightdm (Ubuntu) = unity (Ubuntu) ** Changed in: unity (Ubuntu) Importance: Undecided = Low ** Also affects: unity Importance: Undecided Status: New ** Changed in: unity Importance: Undecided = Low ** Tags added: lockscreen -- 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/1303317 Title: dots not lined up on lock screen Status in Unity: New Status in “unity” package in Ubuntu: New Bug description: I understand a similar bug was fixed a week or two ago involving the login screen, whereby the dots pattern did not line up properly with the new default wallpaper. Now when locking the screen I have noticed that the dots pattern is in the wrong place, if the right place is where they are on the login screen. They also go through the Ubuntu 14.04 LTS logo in the bottom left rather than around it, and the central dot on the screen is slightly below the central point of the default wallpaper, as opposed to rows above and below the centre as in the login screen. I am running through an NVIDEA GTX 650 with screen resolution 1920x1080. This doesn't seem to be limited to me though, as you can see the same thing in the video http://www.youtube.com/watch?feature=player_detailpagev=ZAREcpd6_eE#t=100 by Joey Sneddon (1:40) Finally, I'm reporting this against lightdm as it seems the most appropriate package; please advise if it is not! ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: lightdm 1.9.14-0ubuntu2 ProcVersionSignature: Ubuntu 3.11.0-19.33-generic 3.11.10.5 Uname: Linux 3.11.0-19-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Sun Apr 6 12:24:02 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2014-01-11 (84 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) SourcePackage: lightdm UpgradeStatus: Upgraded to trusty on 2014-04-01 (4 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1303317/+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 1297254] Re: Unity Top-Menu Bar Not Showing Window Control Buttons
I have the same problem with gtaphic card intel (Intel Ivybridge Mobile) and writer. ** Attachment added: Schermata da 2014-04-07 10:46:13.png https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1297254/+attachment/4071373/+files/Schermata%20da%202014-04-07%2010%3A46%3A13.png -- 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/1297254 Title: Unity Top-Menu Bar Not Showing Window Control Buttons Status in Unity: New Status in “unity” package in Ubuntu: Triaged Bug description: Fresh Install This is similar to Bug #842566, but with an additional issue. When openinf LibreOffice, Window Controls do not appear on mouse-over in the Unity Top-Menu Bar. Also the LibreOffice window header is lost beneath the Unity Bar (See attached screenshots) ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.1.2+14.04.20140320.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-19.39-generic 3.13.6 Uname: Linux 3.13.0-19-generic x86_64 ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 CasperVersion: 1.339 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Tue Mar 25 12:24:51 2014 LiveMediaBuild: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140323) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1297254/+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 971462] Re: When HUD is enabled, AltGr/Compose still causes focus stealing from the widget
This popped up again today on my system (Ubuntu 13.10), in the middle of a session, without having just installed any updates or anything. I was able to (temporarily) fix it by running compiz --replace (i.e. I didn't have to change any settings anywhere, just restart the window manager). However, I forgot to add at the end of the command, and followed up with ^C to get rid of all the console output. Naturally, after that I was screwed... :P But compiz --replace in the terminal should be a functioning workaround until a fix is provided. (And a real fix is really needed - this bug makes lots of features of lots of systems, and some entire systems, practically unusable...!) -- 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/971462 Title: When HUD is enabled, AltGr/Compose still causes focus stealing from the widget Status in Compiz: Confirmed Status in Unity: Confirmed Status in “unity” package in Ubuntu: Confirmed Bug description: STR: 1. Make sure that HUD is enabled 2. Make sure you are using a keyboard layout that uses a Compose key (e.g. English (UK)) 3. Open http://people.canonical.com/~roman.yepishev/blur.html in firefox or chromium 4. Put the cursor in the field and press AltGr/Compose key 5. Observe that Blurred is appended on the page Expected results: Compose sends nothing (as it happens when HUD is disabled) Actual results: Widget loses focus for a fraction of the second. Impact: This is most noticeable in the web pages that make use of 'blur' event handler, such as PicasaWeb, where the image title is updated once the focus leaves the field, thus making it impossible to properly change the title of the picture. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: unity 5.8.0-0ubuntu2 ProcVersionSignature: Ubuntu 3.2.0-21.34-generic 3.2.13 Uname: Linux 3.2.0-21-generic x86_64 ApportVersion: 2.0-0ubuntu2 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] Date: Mon Apr 2 11:28:58 2012 InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Alpha amd64 (20120225) SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/971462/+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 1303698] [NEW] curiosity killed the trusty tahr
Public bug reported: I went to the vet with cat #2, while cat #1 was at home. Being a responsible user, I locked my screen with Ctrl-Alt-L before leaving. When I returned from the vet, cat #1 was sitting on the keyboard of my Thinkpad x201, and the keyboard buffer of the screensaver's password entry field was full. Even after removing the cat, the password entry field was unresponsive. It was impossible to delete the garbage characters entered by cat #1, even trying to get the focus to that dialog using the mouse was unsuccessful. My only option was to go to a text console using Ctrl- Alt-F1 and reboot (I know, I could have killed the screensaver, but for ordinary users this is probably too complex.) I consider that a bug in unity or the screensaver. Curious cats should not kill the trusty tahr or its screensaver. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.0+14.04.20140403-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-23.45-generic 3.13.8 Uname: Linux 3.13.0-23-generic x86_64 ApportVersion: 2.14.1-0ubuntu1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Mon Apr 7 17:51:23 2014 InstallationDate: Installed on 2013-03-19 (384 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Alpha amd64 (20130318) SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2014-03-04 (34 days ago) ** Affects: unity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty ** Description changed: I went to the vet with cat #2, while cat #1 was at home. Being a responsible user, I locked my screen with Ctrl-Alt-L before leaving. When I returned from the vet, cat #1 was sitting on the keyboard of my Thinkpad x201, and the keyboard buffer of the screensaver's password - entry buffer was full. + entry field was full. Even after removing the cat, the password entry field was unresponsive. It was impossible to delete the garbage characters entered by cat #1, even trying to get the focus to that dialog using the mouse was unsuccessful. My only option was to go to a text console using Ctrl- Alt-F1 and reboot (I know, I could have killed the screensaver, but for ordinary users this is probably too complex.) I consider that a bug in unity or the screensaver. Curious cats should not kill the trusty tahr or its screensaver. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.0+14.04.20140403-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-23.45-generic 3.13.8 Uname: Linux 3.13.0-23-generic x86_64 ApportVersion: 2.14.1-0ubuntu1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Mon Apr 7 17:51:23 2014 InstallationDate: Installed on 2013-03-19 (384 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Alpha amd64 (20130318) SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2014-03-04 (34 days ago) -- 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/1303698 Title: curiosity killed the trusty tahr Status in “unity” package in Ubuntu: New Bug description: I went to the vet with cat #2, while cat #1 was at home. Being a responsible user, I locked my screen with Ctrl-Alt-L before leaving. When I returned from the vet, cat #1 was sitting on the keyboard of my Thinkpad x201, and the keyboard buffer of the screensaver's password entry field was full. Even after removing the cat, the password entry field was unresponsive. It was impossible to delete the garbage characters entered by cat #1, even trying to get the focus to that dialog using the mouse was unsuccessful. My only option was to go to a text console using Ctrl-Alt-F1 and reboot (I know, I could have killed the screensaver, but for ordinary users this is probably too complex.) I consider that a bug in unity or the screensaver. Curious cats should not kill the trusty tahr or its screensaver. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.0+14.04.20140403-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-23.45-generic 3.13.8 Uname: Linux 3.13.0-23-generic x86_64 ApportVersion: 2.14.1-0ubuntu1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Mon Apr 7 17:51:23 2014 InstallationDate: Installed on 2013-03-19 (384 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Alpha amd64 (20130318) SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2014-03-04 (34 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1303698/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to :
[Dx-packages] [Bug 1225063] Re: cannot remove/uninstall online/offline indicator
** Branch linked: lp:~larsu/indicator-messages/menu-visibility -- 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, dx-packages https://bugs.launchpad.net/bugs/1225063 Title: cannot remove/uninstall online/offline indicator Status in The Messaging Menu: In Progress Status in “indicator-messages” package in Ubuntu: Triaged Bug description: I'd like to remove and uninstall the package which provides this: http://i.imgur.com/6zcx7Jq.png Since there is no About/settings, I don't know which app this is. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: unity-services 7.1.0+13.10.20130903.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-5.11-generic 3.11.0 Uname: Linux 3.11.0-5-generic x86_64 ApportVersion: 2.12.1-0ubuntu3 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' Date: Fri Sep 13 19:06:04 2013 InstallationDate: Installed on 2013-09-09 (3 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Alpha amd64 (20130909) MarkForUpload: True SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-messages/+bug/1225063/+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 1225063] Re: cannot remove/uninstall online/offline indicator
There are actually two bugs in the original screenshot: the chat section should not be shown when no applications support that and the whole messaging menu should not be shown when it doesn't contain any applications. ** Changed in: indicator-messages Status: Triaged = In Progress ** No longer affects: unity (Ubuntu) -- 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, dx-packages https://bugs.launchpad.net/bugs/1225063 Title: cannot remove/uninstall online/offline indicator Status in The Messaging Menu: In Progress Status in “indicator-messages” package in Ubuntu: Triaged Bug description: I'd like to remove and uninstall the package which provides this: http://i.imgur.com/6zcx7Jq.png Since there is no About/settings, I don't know which app this is. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: unity-services 7.1.0+13.10.20130903.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-5.11-generic 3.11.0 Uname: Linux 3.11.0-5-generic x86_64 ApportVersion: 2.12.1-0ubuntu3 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' Date: Fri Sep 13 19:06:04 2013 InstallationDate: Installed on 2013-09-09 (3 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Alpha amd64 (20130909) MarkForUpload: True SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-messages/+bug/1225063/+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 1303712] [NEW] [FFe] Remove gnome screensaver with unity installation
Public bug reported: Unity is now handling the gnome screensaver dbus API completely, so we can get rid g-s from default ubuntu installation. ** Affects: unity Importance: Undecided Assignee: Andrea Azzarone (andyrock) Status: New ** Affects: unity (Ubuntu) Importance: Undecided Status: New ** Branch linked: lp:~unity-team/unity/gs-dbus-interface ** Summary changed: - [FFe] Remove gnome screensaver from unity installation + [FFe] Remove gnome screensaver with unity installation ** Also affects: unity Importance: Undecided Status: New ** Changed in: unity Assignee: (unassigned) = Andrea Azzarone (andyrock) -- 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/1303712 Title: [FFe] Remove gnome screensaver with unity installation Status in Unity: New Status in “unity” package in Ubuntu: New Bug description: Unity is now handling the gnome screensaver dbus API completely, so we can get rid g-s from default ubuntu installation. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1303712/+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 1104236] Re: [regression] Unity show desktop fade out makes them invisible in spread.
This bug was fixed in the package compiz - 1:0.9.11+14.04.20140404-0ubuntu1 --- compiz (1:0.9.11+14.04.20140404-0ubuntu1) trusty; urgency=low [ Chris Townsend ] * Fix issue where Compiz passively grabs all mouse buttons which severely affects scrolling in Gtk apps. Now only unconditionally grab buttons 1-3 for all windows except the desktop window and only grab other buttons when there is a modifier attached to it. (LP: #1171342) * Only fade in and fade out a window when it's hidden if it's not in Show Desktop mode. This allows for a good fade out effect in Unity when exiting Spread while in Show Desktop mode. (LP: #1104236) -- Ubuntu daily release ps-jenk...@lists.canonical.com Fri, 04 Apr 2014 21:41:53 + ** Changed in: compiz (Ubuntu) Status: In Progress = Fix Released ** 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/1104236 Title: [regression] Unity show desktop fade out makes them invisible in spread. Status in Compiz: Fix Committed Status in Unity: Fix Committed Status in “compiz” package in Ubuntu: Fix Released Status in “unity” package in Ubuntu: Fix Released Bug description: This looks like a regression. Bug 88 describes what we now have in current trunk again. STR: 1. Open 2 application windows, e.g. gnome-terminal 2. Alt-tab to show desktop 3. Click on gnome-terminal icon with 2 pips on the launcher Expected results: Two windows are displayed in spread. Actual results: One window is displayed in spread with another one still being there, the outline appears on hover but the window itself is not displayed. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: unity 6.12.0daily13.01.21bzr3064pkg0raring147 [origin: LP-PPA-unity-team-staging] ProcVersionSignature: Ubuntu 3.8.0-1.5-generic 3.8.0-rc4 Uname: Linux 3.8.0-1-generic x86_64 ApportVersion: 2.8-0ubuntu2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CrashDB: unity Date: Thu Jan 24 19:08:09 2013 InstallationDate: Installed on 2013-01-04 (20 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Alpha amd64 (20130104) MarkForUpload: True SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) ADDITION: Furthermore Show desktop shows desktop on all workspaces which is not desired behavior. This makes the issue even worse, because you can only use the launcher and alt-tab to navigate between the windows which results in a big usability bug. The following video demonstrates this: http://ubuntuone.com/4zt3CfDbgOZmanRGBCrbeE To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/1104236/+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 698031] Re: Update the 'Force Quit' dialogue to use sheet style dialogues
This bug was fixed in the package unity - 7.2.0+14.04.20140404-0ubuntu1 --- unity (7.2.0+14.04.20140404-0ubuntu1) trusty; urgency=low [ Chris Townsend ] * Fix issue where windows that are in Show Desktop mode are selected for spread have a blank preview. This fix will Fade Out the window for Spread and Fade In the window again when Spread exits if that window is not chosen. (LP: #1104236) [ Marco Trevisan (Treviño) ] * ForceQuitDialog: add a new sheet style dialog that is shown when a window hangs Listen to compiz toolkit events and prompt a dialog that allows to force-quit an hanging application. (LP: #698031) -- Ubuntu daily release ps-jenk...@lists.canonical.com Fri, 04 Apr 2014 21:35:41 + ** Changed in: unity (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/698031 Title: Update the 'Force Quit' dialogue to use sheet style dialogues Status in Ayatana Design: Confirmed Status in Unity: In Progress Status in “unity” package in Ubuntu: Fix Released Bug description: Update the 'Force Quit' dialogue to use sheet style dialogues. Description: This change has been inspired by the following posting: http://www.omgubuntu.co.uk/2011/01/force-quit-with-style-yo/ However instead of blacking out the program window we should use a 'sheet style' dialogue for this design. See https://chinstrap.canonical.com/~johnlea/sheet_style_dialogue.png. Required deliverables: A visual design showing the use of 'sheet style' dialogues in this context To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/698031/+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 1104236] Re: [regression] Unity show desktop fade out makes them invisible in spread.
This bug was fixed in the package unity - 7.2.0+14.04.20140404-0ubuntu1 --- unity (7.2.0+14.04.20140404-0ubuntu1) trusty; urgency=low [ Chris Townsend ] * Fix issue where windows that are in Show Desktop mode are selected for spread have a blank preview. This fix will Fade Out the window for Spread and Fade In the window again when Spread exits if that window is not chosen. (LP: #1104236) [ Marco Trevisan (Treviño) ] * ForceQuitDialog: add a new sheet style dialog that is shown when a window hangs Listen to compiz toolkit events and prompt a dialog that allows to force-quit an hanging application. (LP: #698031) -- Ubuntu daily release ps-jenk...@lists.canonical.com Fri, 04 Apr 2014 21:35:41 + -- 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/1104236 Title: [regression] Unity show desktop fade out makes them invisible in spread. Status in Compiz: Fix Committed Status in Unity: Fix Committed Status in “compiz” package in Ubuntu: Fix Released Status in “unity” package in Ubuntu: Fix Released Bug description: This looks like a regression. Bug 88 describes what we now have in current trunk again. STR: 1. Open 2 application windows, e.g. gnome-terminal 2. Alt-tab to show desktop 3. Click on gnome-terminal icon with 2 pips on the launcher Expected results: Two windows are displayed in spread. Actual results: One window is displayed in spread with another one still being there, the outline appears on hover but the window itself is not displayed. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: unity 6.12.0daily13.01.21bzr3064pkg0raring147 [origin: LP-PPA-unity-team-staging] ProcVersionSignature: Ubuntu 3.8.0-1.5-generic 3.8.0-rc4 Uname: Linux 3.8.0-1-generic x86_64 ApportVersion: 2.8-0ubuntu2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CrashDB: unity Date: Thu Jan 24 19:08:09 2013 InstallationDate: Installed on 2013-01-04 (20 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Alpha amd64 (20130104) MarkForUpload: True SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) ADDITION: Furthermore Show desktop shows desktop on all workspaces which is not desired behavior. This makes the issue even worse, because you can only use the launcher and alt-tab to navigate between the windows which results in a big usability bug. The following video demonstrates this: http://ubuntuone.com/4zt3CfDbgOZmanRGBCrbeE To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/1104236/+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 1300936] Re: HUD widget sometimes breaks when shrinking to show a single result
** Changed in: unity Status: New = Confirmed ** Changed in: unity Importance: Undecided = Medium -- You received this bug notification because you are a member of DX Packages, which is subscribed to hud in Ubuntu. https://bugs.launchpad.net/bugs/1300936 Title: HUD widget sometimes breaks when shrinking to show a single result Status in Unity: Confirmed Status in “hud” package in Ubuntu: Invalid Bug description: close all open application windows. tap alt. type enter =there are no results. There should be results. Why does enter have no results but ente or enter do have results? hit spacebar select Enter Location... (Go) Nothing happens - it should have opened theLocation window ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: hud 13.10.1+14.04.20140326-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-20.42-generic 3.13.7 Uname: Linux 3.13.0-20-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.14-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Tue Apr 1 19:22:55 2014 InstallationDate: Installed on 2014-03-27 (5 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Beta amd64 (20140326) SourcePackage: hud UpgradeStatus: No upgrade log present (probably fresh install) upstart.hud.log: hud-service: Fatal IO error 11 (Resource temporarily unavailable) on X server :0. hud-service: Fatal IO error 0 (Success) on X server :0. upstart.window-stack-bridge.log: QDBusConnection: name 'org.ayatana.bamf' had owner '' but we thought it was ':1.5' QDBusConnection: name 'org.ayatana.bamf' had owner '' but we thought it was ':1.10' To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1300936/+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 1281058] Re: The system shutdowns when multiple accounts are open
Is there anyone working on this? -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-session in Ubuntu. Matching subscriptions: dx-packages, dx-packages https://bugs.launchpad.net/bugs/1281058 Title: The system shutdowns when multiple accounts are open Status in Ayatana Design: Fix Committed Status in OEM Priority Project: In Progress Status in OEM Priority Project trusty series: In Progress Status in “indicator-session” package in Ubuntu: Triaged Status in “systemd” package in Ubuntu: Triaged Status in “unity” package in Ubuntu: Triaged Status in “unity-greeter” package in Ubuntu: Fix Released Bug description: Steps to reproduce: 1) Create a second account in the system 2) While the first account is open, open a session with the second one 3) Try to shutdown the system Expected results: The system logs out instead of shutting down (ideally with a warning on why it did that) Actual results: The system shutdowns and unsaved data on session1 is lost -- Desired resolution: - Add a warning message informing the user that other users are logged in and then shutting down will also close their sessions as proposed in the mockup attached to comment #12 - The warning message should be Other users are currently logged in to this computer, shutting down now will also close these other sessions To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/1281058/+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 1259564] Re: GPG_AGENT_INFO not being passed to thunderbird
Status changed to 'Confirmed' because the bug affects multiple users. ** 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/1259564 Title: GPG_AGENT_INFO not being passed to thunderbird Status in “indicator-messages” package in Ubuntu: Confirmed Bug description: On Trusty, if I launch thunderbird from the terminal or from the Dash, then thunderbird is able to use enigmail. If I launch via indicator- messages, it is not. Steps to reproduce: 1. adjust /usr/lib/thunderbird/thunderbird.sh to have: echo TEST: $GPG_AGENT_INFO /tmp/tbird.gpg 2. Launch from a terminal: $ rm -f /tmp/tbird.gpg ; thunderbird $ cat /tmp/tbird.gpg # separate terminal TEST: /run/user/1000/keyring-bzAKyI/gpg:0:1 (It worked!) 3. Launch from the Dash: $ rm -f /tmp/tbird.gpg launch from Dash $ cat /tmp/tbird.gpg # separate terminal TEST: /run/user/1000/keyring-bzAKyI/gpg:0:1 (It worked!) 4. Launch from indicator-messages: $ rm -f /tmp/tbird.gpg select Thunderbird Mail from indicator-messages $ cat /tmp/tbird.gpg # separate terminal TEST: (It did not work) ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: indicator-messages 13.10.1+14.04.20131125-0ubuntu1 ProcVersionSignature: Ubuntu 3.12.0-5.13-generic 3.12.2 Uname: Linux 3.12.0-5-generic x86_64 ApportVersion: 2.12.7-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Tue Dec 10 07:59:07 2013 InstallationDate: Installed on 2011-06-28 (895 days ago) InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release amd64 (20110425.2) SourcePackage: indicator-messages UpgradeStatus: Upgraded to trusty on 2013-11-04 (35 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-messages/+bug/1259564/+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 1303310] [NEW] Screensaver isn't triggered right after the first boot
You have been subscribed to a public bug: Hi all, as previously posted on Ubuntu-Bugsquad ML: I noticed that on a fresh boot the screensaver will not be triggered, may be because no user is already logged so there's no such policy enabled.[0] Now, the downside of this behaviour is that computers turned on and awaiting for users to be logged in will stay indefinitely with their monitors/screens on, wasting energy and degrading the hardware. Nowadays it's a common practice in public institutions and companies to shut down every device that's not running any critical service mostly for two big reasons: a. security measures and b. to cut energy and hardware waste to save money. The problem is that on next morning when staff turns on the systems again the machines will keep their screens on all the time until coworkers or general public - like on a public library - arrives. I could think of several workarounds like adding a cron job or even something simpler, an 'at' command to every /etc/rc.local to instruct to `xset -display :0 dpms force off' at a given time to ensure the monitors will be properly off after system boot until users arrive, but I would prefer to stay away from any non-necessary hack if there's an official, supported way to do this. Thank you very much! [0] I'm guessing here, I'm not familiarized with Ubuntu's internals... ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-23.45-generic 3.13.8 Uname: Linux 3.13.0-23-generic x86_64 NonfreeKernelModules: wl .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Sun Apr 6 07:48:35 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:163d] Advanced Micro Devices, Inc. [AMD/ATI] Madison [Mobility Radeon HD 5650/5750 / 6530M/6550M] [1002:68c1] (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:163d] InstallationDate: Installed on 2014-03-17 (20 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140315) MachineType: Hewlett-Packard HP Pavilion dv7 Notebook PC ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-23-generic root=UUID=14188451-0e78-4324-aa27-474fd4351293 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/07/2011 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: F.29 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 163D dmi.board.vendor: Hewlett-Packard dmi.board.version: 65.38 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: N/A dmi.modalias: dmi:bvnHewlett-Packard:bvrF.29:bd11/07/2011:svnHewlett-Packard:pnHPPaviliondv7NotebookPC:pvr058812242B20010020100:rvnHewlett-Packard:rn163D:rvr65.38:cvnHewlett-Packard:ct10:cvrN/A: dmi.product.name: HP Pavilion dv7 Notebook PC dmi.product.version: 058812242B20010020100 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.11+14.04.20140328-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-4ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-4ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.15.0-1ubuntu7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Sun Apr 6 05:54:41 2014 xserver.configfile: default xserver.errors: RADEON(G0): [XvMC] Failed to initialize extension. xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 634 vendor LGD xserver.version: 2:1.15.0-1ubuntu7 ** Affects: unity (Ubuntu) Importance: High Status: Confirmed ** Tags: amd64 apport-bug compiz-0.9 trusty ubuntu -- Screensaver isn't triggered right after the first boot https://bugs.launchpad.net/bugs/1303310 You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. -- 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 1300916] Re: Shutting down Ubuntu One file services
This bug was fixed in the package ubiquity - 2.17.12 --- ubiquity (2.17.12) trusty; urgency=medium * Drop ubiquity-plugin-ubuntuone from adt tests dependencies, it's been removed. * Automatic update of included source packages: netcfg 1.116ubuntu1. -- Dimitri John Ledkov x...@ubuntu.com Mon, 07 Apr 2014 09:50:35 +0100 ** Changed in: ubiquity (Ubuntu Trusty) Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-applet in Ubuntu. Matching subscriptions: dx-packages, dx-packages https://bugs.launchpad.net/bugs/1300916 Title: Shutting down Ubuntu One file services Status in “deja-dup” package in Ubuntu: Fix Released Status in “indicator-applet” package in Ubuntu: Fix Released Status in “thunderbird” package in Ubuntu: New Status in “ubiquity” package in Ubuntu: Fix Released Status in “ubiquity-slideshow-ubuntu” package in Ubuntu: Fix Released Status in “ubuntu-docs” package in Ubuntu: Fix Committed Status in “ubuntu-gnome-meta” package in Ubuntu: Fix Released Status in “ubuntu-meta” package in Ubuntu: Fix Released Status in “ubuntu-sso-client” package in Ubuntu: Fix Released Status in “unity” package in Ubuntu: Fix Released Status in “webapps-applications” package in Ubuntu: Fix Released Status in “deja-dup” source package in Precise: New Status in “indicator-applet” source package in Precise: New Status in “thunderbird” source package in Precise: New Status in “ubiquity” source package in Precise: Invalid Status in “ubiquity-slideshow-ubuntu” source package in Precise: New Status in “ubuntu-docs” source package in Precise: New Status in “ubuntu-gnome-meta” source package in Precise: New Status in “ubuntu-meta” source package in Precise: New Status in “ubuntu-sso-client” source package in Precise: New Status in “unity” source package in Precise: New Status in “webapps-applications” source package in Precise: New Status in “deja-dup” source package in Trusty: Fix Released Status in “indicator-applet” source package in Trusty: Fix Released Status in “thunderbird” source package in Trusty: New Status in “ubiquity” source package in Trusty: Fix Released Status in “ubiquity-slideshow-ubuntu” source package in Trusty: Fix Released Status in “ubuntu-docs” source package in Trusty: Fix Committed Status in “ubuntu-gnome-meta” source package in Trusty: Fix Released Status in “ubuntu-meta” source package in Trusty: Fix Released Status in “ubuntu-sso-client” source package in Trusty: Fix Released Status in “unity” source package in Trusty: Fix Released Status in “webapps-applications” source package in Trusty: Fix Released Bug description: Shutting down Ubuntu One file services http://blog.canonical.com/2014/04/02/shutting-down-ubuntu-one-file- services/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/deja-dup/+bug/1300916/+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 1303702] 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/1303702/+attachment/4071474/+files/CoreDump.gz ** Attachment removed: Disassembly.txt https://bugs.launchpad.net/bugs/1303702/+attachment/4071476/+files/Disassembly.txt ** Attachment removed: ProcMaps.txt https://bugs.launchpad.net/bugs/1303702/+attachment/4071477/+files/ProcMaps.txt ** Attachment removed: ProcStatus.txt https://bugs.launchpad.net/bugs/1303702/+attachment/4071478/+files/ProcStatus.txt ** Attachment removed: Registers.txt https://bugs.launchpad.net/bugs/1303702/+attachment/4071479/+files/Registers.txt ** Attachment removed: Stacktrace.txt https://bugs.launchpad.net/bugs/1303702/+attachment/4071480/+files/Stacktrace.txt ** Attachment removed: ThreadStacktrace.txt https://bugs.launchpad.net/bugs/1303702/+attachment/4071481/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of bug 1199571 compiz crashed with SIGSEGV in af_latin_hints_compute_edges() ** 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/1303702 Title: compiz crashed with SIGSEGV in FT_Load_Glyph() Status in “unity” package in Ubuntu: New Bug description: While starting up the system, hit Super key and started typing ProblemType: Crash DistroRelease: Ubuntu 14.04 Package: unity 7.2.0+14.04.20140403-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-23.45-generic 3.13.8 Uname: Linux 3.13.0-23-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu1 Architecture: amd64 CrashCounter: 1 CurrentDesktop: Unity Date: Mon Apr 7 11:59:00 2014 ExecutablePath: /usr/bin/compiz InstallationDate: Installed on 2013-12-11 (116 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20131211) ProcCmdline: compiz ProcEnviron: LANGUAGE=de_DE PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=de_DE.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7fba0f4a393c:testb $0x1,(%rax) PC (0x7fba0f4a393c) ok source $0x1 ok destination (%rax) (0x) 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: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1303702/+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 1300916] Re: Shutting down Ubuntu One file services
Setting this to Invalid in ubuntu-sso-client, as it is not specifically related to the file sync services. ** Changed in: ubuntu-sso-client (Ubuntu Precise) Status: New = Invalid ** Changed in: ubuntu-sso-client (Ubuntu Trusty) Status: Fix Released = Invalid -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-applet in Ubuntu. Matching subscriptions: dx-packages, dx-packages https://bugs.launchpad.net/bugs/1300916 Title: Shutting down Ubuntu One file services Status in “deja-dup” package in Ubuntu: Fix Released Status in “indicator-applet” package in Ubuntu: Fix Released Status in “thunderbird” package in Ubuntu: New Status in “ubiquity” package in Ubuntu: Fix Released Status in “ubiquity-slideshow-ubuntu” package in Ubuntu: Fix Released Status in “ubuntu-docs” package in Ubuntu: Fix Committed Status in “ubuntu-gnome-meta” package in Ubuntu: Fix Released Status in “ubuntu-meta” package in Ubuntu: Fix Released Status in “ubuntu-sso-client” package in Ubuntu: Invalid Status in “unity” package in Ubuntu: Fix Released Status in “webapps-applications” package in Ubuntu: Fix Released Status in “deja-dup” source package in Precise: New Status in “indicator-applet” source package in Precise: New Status in “thunderbird” source package in Precise: New Status in “ubiquity” source package in Precise: Invalid Status in “ubiquity-slideshow-ubuntu” source package in Precise: New Status in “ubuntu-docs” source package in Precise: New Status in “ubuntu-gnome-meta” source package in Precise: New Status in “ubuntu-meta” source package in Precise: New Status in “ubuntu-sso-client” source package in Precise: Invalid Status in “unity” source package in Precise: New Status in “webapps-applications” source package in Precise: New Status in “deja-dup” source package in Trusty: Fix Released Status in “indicator-applet” source package in Trusty: Fix Released Status in “thunderbird” source package in Trusty: New Status in “ubiquity” source package in Trusty: Fix Released Status in “ubiquity-slideshow-ubuntu” source package in Trusty: Fix Released Status in “ubuntu-docs” source package in Trusty: Fix Committed Status in “ubuntu-gnome-meta” source package in Trusty: Fix Released Status in “ubuntu-meta” source package in Trusty: Fix Released Status in “ubuntu-sso-client” source package in Trusty: Invalid Status in “unity” source package in Trusty: Fix Released Status in “webapps-applications” source package in Trusty: Fix Released Bug description: Shutting down Ubuntu One file services http://blog.canonical.com/2014/04/02/shutting-down-ubuntu-one-file- services/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/deja-dup/+bug/1300916/+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 711672] Re: compiz crashed with SIGSEGV in free()
** Changed in: unity Status: Invalid = 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 https://bugs.launchpad.net/bugs/711672 Title: compiz crashed with SIGSEGV in free() Status in Nux: Invalid Status in Unity: Fix Released Status in “nux” package in Ubuntu: Invalid Bug description: Binary package hint: compiz Bonjour, le unity --reset ne fais pas ré apparaitre le tableau de bord, le raccourcis terminal ( ctrl/alt/t ) ne fonctionne pas. version natty narwhal mis à jour à 7h00 am ProblemType: Crash DistroRelease: Ubuntu 11.04 Package: compiz-core 1:0.9.2.1+glibmainloop4-0ubuntu8 ProcVersionSignature: Ubuntu 2.6.38-1.28-generic 2.6.38-rc2 Uname: Linux 2.6.38-1-generic x86_64 Architecture: amd64 CompisitorRunning: None CompizPlugins: [core,bailer,detection,composite,opengl,decor,mousepoll,vpswitch,regex,animation,snap,expo,move,compiztoolbox,place,grid,gnomecompat,wall,ezoom,workarounds,staticswitcher,resize,fade,scale,session,unityshell] CrashCounter: 1 DRM.card0.LVDS.1: status: connected enabled: enabled dpms: On modes: 1280x800 1280x720 1152x768 1024x768 800x600 848x480 720x480 640x480 edid-base64: AP///wANr1IVAQOAIRV4CgagmldOhyYeUFQBAQEBAQEBAQEBAQEBAQEBvBsAoFAgFzAwIDYAS88QAAAY/gBOMTU0STItTDA1CiAg/gBDTU8KICAgICAgICAg/gBOMTU0STItTDA1CiAgADQ= DRM.card0.VGA.1: status: disconnected enabled: disabled dpms: On modes: edid-base64: Date: Wed Feb 2 07:10:08 2011 DistUpgraded: Fresh install DistroCodename: natty DistroVariant: ubuntu ExecutablePath: /usr/bin/compiz GraphicsCard: Subsystem: Micro-Star International Co., Ltd. Device [1462:3fb7] InstallationMedia: Ubuntu 11.04 Natty Narwhal - Alpha amd64 (20101222) MachineType: Micro-Star International MSI Notebook VR610 ProcCmdline: compiz ProcEnviron: LANGUAGE=fr_FR:fr:en_GB:en PATH=(custom, user) LANG=fr_FR.UTF-8 LC_MESSAGES=fr_FR.utf8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.38-1-generic root=UUID=0158f208-5f7a-4090-8092-0ab3974b51cc ro quiet splash vt.handoff=7 Renderer: Hardware acceleration SegvAnalysis: Segfault happened at: 0x7f07a3ac745f:mov0x10(%rbx),%rax PC (0x7f07a3ac745f) ok source 0x10(%rbx) (0xfff5fc28) not located in a known VMA region (needed readable region)! destination %rax ok SegvReason: reading unknown VMA Signal: 11 SourcePackage: compiz StacktraceTop: ?? () from /lib/libc.so.6 ?? () from /lib/libc.so.6 free () from /lib/libc.so.6 nux::ImageSurface::~ImageSurface() () from /usr/lib/libnux-image-0.9.so.0 nux::NTextureData::ClearData() () from /usr/lib/libnux-image-0.9.so.0 Title: compiz crashed with SIGSEGV in free() UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare XsessionErrors: (nautilus:1276): GConf-CRITICAL **: gconf_value_free: assertion `value != NULL' failed (unknown:1266): dee-CRITICAL **: dee_model_get_first_iter: assertion `DEE_IS_MODEL (self)' failed (unknown:1266): dee-CRITICAL **: dee_model_get_last_iter: assertion `DEE_IS_MODEL (self)' failed (unknown:1266): dee-WARNING **: Transaction from com.canonical.Unity.ApplicationsPlace.SectionsModel is in the past. Ignoring transaction. (unknown:1266): dee-WARNING **: Transaction from com.canonical.Unity.ApplicationsPlace.GroupsModel is in the past. Ignoring transaction. dmi.bios.date: 12/18/2007 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: A163BAMS V1.0B dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: MS-163B dmi.board.vendor: MSI dmi.board.version: Ver 1.000 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.:bvrA163BAMSV1.0B:bd12/18/2007:svnMicro-StarInternational:pnMSINotebookVR610:pvrVer1.000:rvnMSI:rnMS-163B:rvrVer1.000:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: MSI Notebook VR610 dmi.product.version: Ver 1.000 dmi.sys.vendor: Micro-Star International version.libdrm2: libdrm2 2.4.23-1ubuntu3 version.libgl1-mesa-glx: libgl1-mesa-glx 7.10-1ubuntu1 version.xserver-xorg: xserver-xorg 1:7.6~3ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.13.2+git20110124.fadee040-0ubuntu4 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.14.0-1ubuntu5 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:0.0.16+git20110107+b795ca6e-0ubuntu4 To manage notifications about this bug go to: https://bugs.launchpad.net/nux/+bug/711672/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help :
[Dx-packages] [Bug 1303796] [NEW] Display scaling is not applied runtime
Public bug reported: I changed my scaling to a value and back to 1, I think notify-osd got triggered at that time, and all subsequent notifications were scaled incorrectly. It looks like notify-osd doesn't update the scaling value runtime. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: notify-osd 0.9.35+14.04.20140213-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-23.45-generic 3.13.8 Uname: Linux 3.13.0-23-generic x86_64 NonfreeKernelModules: wl nvidia ApportVersion: 2.14.1-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Mon Apr 7 13:59:10 2014 MachineType: Dell Inc. Latitude E6420 ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-3.13.0-23-generic root=UUID=e11751da-d20f-4832-9530-c41e15f1e05c ro rootflags=subvol=@ splash quiet vt.handoff=7 RelatedPackageVersions: xserver-xorg 1:7.7+1ubuntu8 libgl1-mesa-glx 10.1.0-4ubuntu1 libdrm2 2.4.52-1 xserver-xorg-video-intel 2:2.99.910-0ubuntu1 xserver-xorg-video-ati 1:7.3.0-1ubuntu3 SourcePackage: notify-osd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/11/2012 dmi.bios.vendor: Dell Inc. dmi.bios.version: A14 dmi.board.vendor: Dell Inc. dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA14:bd07/11/2012:svnDellInc.:pnLatitudeE6420:pvr01:rvnDellInc.:rn:rvr:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E6420 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. ** Affects: notify-osd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty -- 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/1303796 Title: Display scaling is not applied runtime Status in “notify-osd” package in Ubuntu: New Bug description: I changed my scaling to a value and back to 1, I think notify-osd got triggered at that time, and all subsequent notifications were scaled incorrectly. It looks like notify-osd doesn't update the scaling value runtime. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: notify-osd 0.9.35+14.04.20140213-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-23.45-generic 3.13.8 Uname: Linux 3.13.0-23-generic x86_64 NonfreeKernelModules: wl nvidia ApportVersion: 2.14.1-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Mon Apr 7 13:59:10 2014 MachineType: Dell Inc. Latitude E6420 ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-3.13.0-23-generic root=UUID=e11751da-d20f-4832-9530-c41e15f1e05c ro rootflags=subvol=@ splash quiet vt.handoff=7 RelatedPackageVersions: xserver-xorg 1:7.7+1ubuntu8 libgl1-mesa-glx 10.1.0-4ubuntu1 libdrm2 2.4.52-1 xserver-xorg-video-intel 2:2.99.910-0ubuntu1 xserver-xorg-video-ati 1:7.3.0-1ubuntu3 SourcePackage: notify-osd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/11/2012 dmi.bios.vendor: Dell Inc. dmi.bios.version: A14 dmi.board.vendor: Dell Inc. dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA14:bd07/11/2012:svnDellInc.:pnLatitudeE6420:pvr01:rvnDellInc.:rn:rvr:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E6420 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/notify-osd/+bug/1303796/+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 1303789] Re: compiz crashed with SIGSEGV
*** This bug is a duplicate of bug 931389 *** https://bugs.launchpad.net/bugs/931389 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 #931389, 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/1303789/+attachment/4071780/+files/CoreDump.gz ** Attachment removed: Disassembly.txt https://bugs.launchpad.net/bugs/1303789/+attachment/4071782/+files/Disassembly.txt ** Attachment removed: ProcMaps.txt https://bugs.launchpad.net/bugs/1303789/+attachment/4071784/+files/ProcMaps.txt ** Attachment removed: ProcStatus.txt https://bugs.launchpad.net/bugs/1303789/+attachment/4071785/+files/ProcStatus.txt ** Attachment removed: Registers.txt https://bugs.launchpad.net/bugs/1303789/+attachment/4071786/+files/Registers.txt ** Attachment removed: Stacktrace.txt https://bugs.launchpad.net/bugs/1303789/+attachment/4071787/+files/Stacktrace.txt ** Attachment removed: ThreadStacktrace.txt https://bugs.launchpad.net/bugs/1303789/+attachment/4071788/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of bug 931389 compiz crashed with SIGSEGV in af_latin_hints_compute_segments() ** Information type changed from Private to Public ** Tags removed: need-i386-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/1303789 Title: compiz crashed with SIGSEGV Status in “unity” package in Ubuntu: New Bug description: it crashed while I scroll the dash by scroll mouse wheel ProblemType: Crash DistroRelease: Ubuntu 14.04 Package: unity 7.2.0+14.04.20140403-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-23.45-generic 3.13.8 Uname: Linux 3.13.0-23-generic i686 ApportVersion: 2.14.1-0ubuntu1 Architecture: i386 CrashCounter: 1 CurrentDesktop: Unity Date: Mon Apr 7 19:52:08 2014 ExecutablePath: /usr/bin/compiz InstallationDate: Installed on 2014-04-06 (0 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Beta i386 (20140326) ProcCmdline: compiz SegvAnalysis: Segfault happened at: 0xb22d6652:or (%eax),%dx PC (0xb22d6652) ok source (%eax) (0x) not located in a known VMA region (needed readable region)! destination %dx ok Stack memory exhausted (SP below stack segment) SegvReason: reading NULL VMA Signal: 11 SourcePackage: unity StacktraceTop: ?? () from /usr/lib/i386-linux-gnu/libfreetype.so.6 ?? () from /usr/lib/i386-linux-gnu/libfreetype.so.6 ?? () from /usr/lib/i386-linux-gnu/libfreetype.so.6 ?? () from /usr/lib/i386-linux-gnu/libfreetype.so.6 ?? () from /usr/lib/i386-linux-gnu/libfreetype.so.6 Title: compiz crashed with SIGSEGV UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1303789/+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 1303712] Re: [FFe] Remove gnome screensaver with unity installation
Thanks for the work, some thoughts on the changes: First, having Unity doing the handling rather than relying on g-s makes sense, good work in that direction ;-) Some issues/things to consider though - it's late in the cycle, gnome-screensaver interfaces with other components for e.g idle count. We need to make sure we don't regress anything if we change that - it's possible to install several desktops on the same machine, we can't really make Unity to uninstall gnome-screensaver when it's still used in e.g gnome-panel sessions - Luke did that change https://launchpad.net/ubuntu/+source/gnome- screensaver/3.6.1-0ubuntu11 it seems like he didn't open a bug/give specifics on the issues with the screenreader (Marco said it should be working). Luke could you open a bug about the issues you had and provide details? -- 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/1303712 Title: [FFe] Remove gnome screensaver with unity installation Status in Unity: New Status in “unity” package in Ubuntu: New Bug description: Unity is now handling the gnome screensaver dbus API completely, so we can get rid g-s from default ubuntu installation. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1303712/+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 1303796] Re: Display scaling is not applied runtime
** Description changed: - I changed my scaling to a value and back to 1, I think notify-osd got - triggered at that time, and all subsequent notifications were scaled - incorrectly. - - It looks like notify-osd doesn't update the scaling value runtime. - - ProblemType: Bug - DistroRelease: Ubuntu 14.04 - Package: notify-osd 0.9.35+14.04.20140213-0ubuntu1 - ProcVersionSignature: Ubuntu 3.13.0-23.45-generic 3.13.8 - Uname: Linux 3.13.0-23-generic x86_64 - NonfreeKernelModules: wl nvidia - ApportVersion: 2.14.1-0ubuntu1 - Architecture: amd64 - CurrentDesktop: Unity - Date: Mon Apr 7 13:59:10 2014 - MachineType: Dell Inc. Latitude E6420 - ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-3.13.0-23-generic root=UUID=e11751da-d20f-4832-9530-c41e15f1e05c ro rootflags=subvol=@ splash quiet vt.handoff=7 - RelatedPackageVersions: - xserver-xorg 1:7.7+1ubuntu8 - libgl1-mesa-glx 10.1.0-4ubuntu1 - libdrm2 2.4.52-1 - xserver-xorg-video-intel 2:2.99.910-0ubuntu1 - xserver-xorg-video-ati 1:7.3.0-1ubuntu3 - SourcePackage: notify-osd - UpgradeStatus: No upgrade log present (probably fresh install) - dmi.bios.date: 07/11/2012 - dmi.bios.vendor: Dell Inc. - dmi.bios.version: A14 - dmi.board.vendor: Dell Inc. - dmi.chassis.type: 9 - dmi.chassis.vendor: Dell Inc. - dmi.modalias: dmi:bvnDellInc.:bvrA14:bd07/11/2012:svnDellInc.:pnLatitudeE6420:pvr01:rvnDellInc.:rn:rvr:cvnDellInc.:ct9:cvr: - dmi.product.name: Latitude E6420 - dmi.product.version: 01 - dmi.sys.vendor: Dell Inc. + Effectively whilst it may seem to be to be the extremely tough imagination of a aliveness movement, all you deprivation is many guidelines to get skinny legs. The moment you obey with these, your ideate cook would no soul unsnarl your dreams but would get you ingratiating compliments. + For those of us who hit bulky thighs and legs, the serve lies in a two way operation. Basic you require to remark your diet so that you can stay including flab to your body. Later you status to borrow an unwearying fashion that will aid you fuse inaccurate the flab that is currently accumulated. + When we handle of diet mean moderate we require not get worried most privation on the lettuce leafage. All that is necessary is dwindling the number of reserve calories in our routine foods phthisis. If you actually desire to get thin legs, produce a radical fasting mean performance that consists of much solon fruits, vegetables, entire form meals, flex meat, and nuts. Cut behind on vulcanized meals as they lie of augmented sum of fattening oil and dulcorate. + Succeeding permit any physiological study equal strolling, jogging, swim or cycling to your representative function. Any of these exercises testament aid you pain off embody fat, and ton the yobo tissues of your legs to get them in influence. Shaft! Before you sough at these ideas to get skinny legs, investigate on. + Doing exercises essential not be a slow and offensive chore. It is vindicatory active a such statesman bouncing way of time. So you could move to the nearby mart distributor to select up your product kinda of obtaining it delivered at your threshold. Think the stairs at impact, as an disjunctive of the elevator. Sphere a bike for abstract indifference errands. + http://garciniumreview.com/ -- 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/1303796 Title: Display scaling is not applied runtime Status in “notify-osd” package in Ubuntu: New Bug description: Effectively whilst it may seem to be to be the extremely tough imagination of a aliveness movement, all you deprivation is many guidelines to get skinny legs. The moment you obey with these, your ideate cook would no soul unsnarl your dreams but would get you ingratiating compliments. For those of us who hit bulky thighs and legs, the serve lies in a two way operation. Basic you require to remark your diet so that you can stay including flab to your body. Later you status to borrow an unwearying fashion that will aid you fuse inaccurate the flab that is currently accumulated. When we handle of diet mean moderate we require not get worried most privation on the lettuce leafage. All that is necessary is dwindling the number of reserve calories in our routine foods phthisis. If you actually desire to get thin legs, produce a radical fasting mean performance that consists of much solon fruits, vegetables, entire form meals, flex meat, and nuts. Cut behind on vulcanized meals as they lie of augmented sum of fattening oil and dulcorate. Succeeding permit any physiological study equal strolling, jogging, swim or cycling to your representative function. Any of these exercises testament aid you pain off embody fat, and ton the yobo tissues of your legs to get them in influence. Shaft! Before you sough at these ideas to get skinny
[Dx-packages] [Bug 1216833] Re: sorting is wrong with the converged indicator codebase
** Branch linked: lp:~larsu/indicator-messages/lp1216833 -- 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/1216833 Title: sorting is wrong with the converged indicator codebase Status in The Messaging Menu: In Progress Status in “indicator-messages” package in Ubuntu: Triaged Bug description: The design (https://wiki.ubuntu.com/MessagingMenu#Presentation) states that the default chat and email clients should be first, the new codebase has sources alphabetically sorted though To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-messages/+bug/1216833/+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 1216833] Re: sorting is wrong with the converged indicator codebase
** Changed in: indicator-messages Status: Triaged = In Progress -- 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/1216833 Title: sorting is wrong with the converged indicator codebase Status in The Messaging Menu: In Progress Status in “indicator-messages” package in Ubuntu: Triaged Bug description: The design (https://wiki.ubuntu.com/MessagingMenu#Presentation) states that the default chat and email clients should be first, the new codebase has sources alphabetically sorted though To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-messages/+bug/1216833/+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 1303812] Re: Options in sidebar not aligned properly with reduced display scaling
** Also affects: unity (Ubuntu) Importance: Undecided Status: New -- 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/1303812 Title: Options in sidebar not aligned properly with reduced display scaling Status in Unity: New Status in “unity” package in Ubuntu: Confirmed Bug description: When I change my scaling in Settings Display from 1 to anything less than that, some parts of unity's alignment gets messed up. For instance, when I right click on Firefox, instead of Open New Window, I get Open New Window Open. I've attached a screenshot for clarification. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1303812/+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 1303812] Re: Options in sidebar not aligned properly with reduced display scaling
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: unity (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1303812 Title: Options in sidebar not aligned properly with reduced display scaling Status in Unity: New Status in “unity” package in Ubuntu: Confirmed Bug description: When I change my scaling in Settings Display from 1 to anything less than that, some parts of unity's alignment gets messed up. For instance, when I right click on Firefox, instead of Open New Window, I get Open New Window Open. I've attached a screenshot for clarification. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1303812/+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 1303317] Re: dots not lined up on lock screen
the lining up issue was with the wallpaper itself, rather than the grid pattern in the unity-greeter. The issue here is that the grid pattern is overlayed/calculated differently from the unity-greeter and discrepancies are visible between the two. (Mostly the starting offset of the grid. -- 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/1303317 Title: dots not lined up on lock screen Status in Unity: New Status in “unity” package in Ubuntu: New Bug description: I understand a similar bug was fixed a week or two ago involving the login screen, whereby the dots pattern did not line up properly with the new default wallpaper. Now when locking the screen I have noticed that the dots pattern is in the wrong place, if the right place is where they are on the login screen. They also go through the Ubuntu 14.04 LTS logo in the bottom left rather than around it, and the central dot on the screen is slightly below the central point of the default wallpaper, as opposed to rows above and below the centre as in the login screen. I am running through an NVIDEA GTX 650 with screen resolution 1920x1080. This doesn't seem to be limited to me though, as you can see the same thing in the video http://www.youtube.com/watch?feature=player_detailpagev=ZAREcpd6_eE#t=100 by Joey Sneddon (1:40) Finally, I'm reporting this against lightdm as it seems the most appropriate package; please advise if it is not! ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: lightdm 1.9.14-0ubuntu2 ProcVersionSignature: Ubuntu 3.11.0-19.33-generic 3.11.10.5 Uname: Linux 3.11.0-19-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Sun Apr 6 12:24:02 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2014-01-11 (84 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) SourcePackage: lightdm UpgradeStatus: Upgraded to trusty on 2014-04-01 (4 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1303317/+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 1303796] Re: Display scaling is not applied runtime
** Changed in: notify-osd (Ubuntu) Status: New = Opinion -- 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/1303796 Title: Display scaling is not applied runtime Status in “notify-osd” package in Ubuntu: Opinion Bug description: Effectively whilst it may seem to be to be the extremely tough imagination of a aliveness movement, all you deprivation is many guidelines to get skinny legs. The moment you obey with these, your ideate cook would no soul unsnarl your dreams but would get you ingratiating compliments. For those of us who hit bulky thighs and legs, the serve lies in a two way operation. Basic you require to remark your diet so that you can stay including flab to your body. Later you status to borrow an unwearying fashion that will aid you fuse inaccurate the flab that is currently accumulated. When we handle of diet mean moderate we require not get worried most privation on the lettuce leafage. All that is necessary is dwindling the number of reserve calories in our routine foods phthisis. If you actually desire to get thin legs, produce a radical fasting mean performance that consists of much solon fruits, vegetables, entire form meals, flex meat, and nuts. Cut behind on vulcanized meals as they lie of augmented sum of fattening oil and dulcorate. Succeeding permit any physiological study equal strolling, jogging, swim or cycling to your representative function. Any of these exercises testament aid you pain off embody fat, and ton the yobo tissues of your legs to get them in influence. Shaft! Before you sough at these ideas to get skinny legs, investigate on. Doing exercises essential not be a slow and offensive chore. It is vindicatory active a such statesman bouncing way of time. So you could move to the nearby mart distributor to select up your product kinda of obtaining it delivered at your threshold. Think the stairs at impact, as an disjunctive of the elevator. Sphere a bike for abstract indifference errands. http://garciniumreview.com/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/notify-osd/+bug/1303796/+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 1303846] Re: compiz crashed with SIGSEGV in _int_malloc()
*** This bug is a duplicate of bug 1283564 *** https://bugs.launchpad.net/bugs/1283564 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 #1283564, 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/1303846/+attachment/4072042/+files/CoreDump.gz ** Attachment removed: Disassembly.txt https://bugs.launchpad.net/bugs/1303846/+attachment/4072044/+files/Disassembly.txt ** Attachment removed: ProcMaps.txt https://bugs.launchpad.net/bugs/1303846/+attachment/4072045/+files/ProcMaps.txt ** Attachment removed: ProcStatus.txt https://bugs.launchpad.net/bugs/1303846/+attachment/4072046/+files/ProcStatus.txt ** Attachment removed: Registers.txt https://bugs.launchpad.net/bugs/1303846/+attachment/4072047/+files/Registers.txt ** Attachment removed: Stacktrace.txt https://bugs.launchpad.net/bugs/1303846/+attachment/4072048/+files/Stacktrace.txt ** Attachment removed: ThreadStacktrace.txt https://bugs.launchpad.net/bugs/1303846/+attachment/4072049/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 1283564 ** 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/1303846 Title: compiz crashed with SIGSEGV in _int_malloc() Status in “unity” package in Ubuntu: New Bug description: stopped right after I ran Bleach(not as root) and search your computer and online sources. Just made the box with nothing in it. ProblemType: Crash DistroRelease: Ubuntu 14.04 Package: unity 7.2.0+14.04.20140404-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-23.45-generic 3.13.8 Uname: Linux 3.13.0-23-generic x86_64 ApportVersion: 2.14.1-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Mon Apr 7 10:00:14 2014 ExecutablePath: /usr/bin/compiz InstallationDate: Installed on 2014-04-06 (0 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Beta amd64 (20140326) ProcCmdline: compiz ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7ff7debbcd71 _int_malloc+689: mov %r14,0x10(%r9) PC (0x7ff7debbcd71) ok source %r14 ok destination 0x10(%r9) (0xf8a337efb7c8) not located in a known VMA region (needed writable region)! SegvReason: writing unknown VMA Signal: 11 SourcePackage: unity StacktraceTop: _int_malloc (av=0x7ff7deefb760 main_arena, bytes=256) at malloc.c:3489 __GI___libc_malloc (bytes=256) at malloc.c:2891 ?? () from /usr/lib/x86_64-linux-gnu/libpixman-1.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libpixman-1.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libcairo.so.2 Title: compiz crashed with SIGSEGV in _int_malloc() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1303846/+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 1302123] Re: Won't respawn when restarting unity-panel-service
** Branch linked: lp:ubuntu/trusty-proposed/indicator-application -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-application in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1302123 Title: Won't respawn when restarting unity-panel-service Status in “indicator-application” package in Ubuntu: In Progress Bug description: If I run `restart unity-panel-service` or `killall unity-panel- service`, indicator-application is not respawned and I need to start it manually with `start indicator-application`. The other indicators are restarted normally. As a consequence, Network Manager's applet is not drawn (nor other custom appindicators). ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: indicator-application 12.10.1+14.04.20140402-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-20.42-generic 3.13.7 Uname: Linux 3.13.0-20-generic x86_64 ApportVersion: 2.14-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Thu Apr 3 14:54:16 2014 InstallationDate: Installed on 2014-03-16 (18 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140316) SourcePackage: indicator-application UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-application/+bug/1302123/+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 1303796] Re: Display scaling is not applied runtime
** Description changed: - Effectively whilst it may seem to be to be the extremely tough imagination of a aliveness movement, all you deprivation is many guidelines to get skinny legs. The moment you obey with these, your ideate cook would no soul unsnarl your dreams but would get you ingratiating compliments. - For those of us who hit bulky thighs and legs, the serve lies in a two way operation. Basic you require to remark your diet so that you can stay including flab to your body. Later you status to borrow an unwearying fashion that will aid you fuse inaccurate the flab that is currently accumulated. - When we handle of diet mean moderate we require not get worried most privation on the lettuce leafage. All that is necessary is dwindling the number of reserve calories in our routine foods phthisis. If you actually desire to get thin legs, produce a radical fasting mean performance that consists of much solon fruits, vegetables, entire form meals, flex meat, and nuts. Cut behind on vulcanized meals as they lie of augmented sum of fattening oil and dulcorate. - Succeeding permit any physiological study equal strolling, jogging, swim or cycling to your representative function. Any of these exercises testament aid you pain off embody fat, and ton the yobo tissues of your legs to get them in influence. Shaft! Before you sough at these ideas to get skinny legs, investigate on. - Doing exercises essential not be a slow and offensive chore. It is vindicatory active a such statesman bouncing way of time. So you could move to the nearby mart distributor to select up your product kinda of obtaining it delivered at your threshold. Think the stairs at impact, as an disjunctive of the elevator. Sphere a bike for abstract indifference errands. - http://garciniumreview.com/ + I changed my scaling to a value and back to 1, I think notify-osd got + triggered at that time, and all subsequent notifications were scaled + incorrectly. + + It looks like notify-osd doesn't update the scaling value runtime. + + ProblemType: Bug + DistroRelease: Ubuntu 14.04 + Package: notify-osd 0.9.35+14.04.20140213-0ubuntu1 + ProcVersionSignature: Ubuntu 3.13.0-23.45-generic 3.13.8 + Uname: Linux 3.13.0-23-generic x86_64 + NonfreeKernelModules: wl nvidia + ApportVersion: 2.14.1-0ubuntu1 + Architecture: amd64 + CurrentDesktop: Unity + Date: Mon Apr 7 13:59:10 2014 + MachineType: Dell Inc. Latitude E6420 + ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-3.13.0-23-generic root=UUID=e11751da-d20f-4832-9530-c41e15f1e05c ro rootflags=subvol=@ splash quiet vt.handoff=7 + RelatedPackageVersions: + xserver-xorg 1:7.7+1ubuntu8 + libgl1-mesa-glx 10.1.0-4ubuntu1 + libdrm2 2.4.52-1 + xserver-xorg-video-intel 2:2.99.910-0ubuntu1 + xserver-xorg-video-ati 1:7.3.0-1ubuntu3 + SourcePackage: notify-osd + UpgradeStatus: No upgrade log present (probably fresh install) + dmi.bios.date: 07/11/2012 + dmi.bios.vendor: Dell Inc. + dmi.bios.version: A14 + dmi.board.vendor: Dell Inc. + dmi.chassis.type: 9 + dmi.chassis.vendor: Dell Inc. + dmi.modalias: dmi:bvnDellInc.:bvrA14:bd07/11/2012:svnDellInc.:pnLatitudeE6420:pvr01:rvnDellInc.:rn:rvr:cvnDellInc.:ct9:cvr: + dmi.product.name: Latitude E6420 + dmi.product.version: 01 + dmi.sys.vendor: Dell Inc. ** Changed in: notify-osd (Ubuntu) Status: Opinion = New -- 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/1303796 Title: Display scaling is not applied runtime Status in “notify-osd” package in Ubuntu: New Bug description: I changed my scaling to a value and back to 1, I think notify-osd got triggered at that time, and all subsequent notifications were scaled incorrectly. It looks like notify-osd doesn't update the scaling value runtime. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: notify-osd 0.9.35+14.04.20140213-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-23.45-generic 3.13.8 Uname: Linux 3.13.0-23-generic x86_64 NonfreeKernelModules: wl nvidia ApportVersion: 2.14.1-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Mon Apr 7 13:59:10 2014 MachineType: Dell Inc. Latitude E6420 ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-3.13.0-23-generic root=UUID=e11751da-d20f-4832-9530-c41e15f1e05c ro rootflags=subvol=@ splash quiet vt.handoff=7 RelatedPackageVersions: xserver-xorg 1:7.7+1ubuntu8 libgl1-mesa-glx 10.1.0-4ubuntu1 libdrm2 2.4.52-1 xserver-xorg-video-intel 2:2.99.910-0ubuntu1 xserver-xorg-video-ati 1:7.3.0-1ubuntu3 SourcePackage: notify-osd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/11/2012 dmi.bios.vendor: Dell Inc. dmi.bios.version: A14 dmi.board.vendor: Dell Inc. dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias:
[Dx-packages] [Bug 1302123] Re: Won't respawn when restarting unity-panel-service
This bug was fixed in the package indicator-application - 12.10.1+14.04.20140407-0ubuntu1 --- indicator-application (12.10.1+14.04.20140407-0ubuntu1) trusty; urgency=low [ Ted Gould ] * Fix the upstart job and desktop config for GNOME2 (LP: #1302123) -- Ubuntu daily release ps-jenk...@lists.canonical.com Mon, 07 Apr 2014 13:39:45 + ** Changed in: indicator-application (Ubuntu) Status: In Progress = Fix Released -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-application in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1302123 Title: Won't respawn when restarting unity-panel-service Status in “indicator-application” package in Ubuntu: Fix Released Bug description: If I run `restart unity-panel-service` or `killall unity-panel- service`, indicator-application is not respawned and I need to start it manually with `start indicator-application`. The other indicators are restarted normally. As a consequence, Network Manager's applet is not drawn (nor other custom appindicators). ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: indicator-application 12.10.1+14.04.20140402-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-20.42-generic 3.13.7 Uname: Linux 3.13.0-20-generic x86_64 ApportVersion: 2.14-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Thu Apr 3 14:54:16 2014 InstallationDate: Installed on 2014-03-16 (18 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140316) SourcePackage: indicator-application UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-application/+bug/1302123/+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 1303870] Re: notify-osd crashed with signal 5 in _XReply()
*** This bug is a duplicate of bug 1283681 *** https://bugs.launchpad.net/bugs/1283681 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 #1283681, 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/1303870/+attachment/4072155/+files/CoreDump.gz ** Attachment removed: Disassembly.txt https://bugs.launchpad.net/bugs/1303870/+attachment/4072158/+files/Disassembly.txt ** Attachment removed: ProcMaps.txt https://bugs.launchpad.net/bugs/1303870/+attachment/4072164/+files/ProcMaps.txt ** Attachment removed: ProcStatus.txt https://bugs.launchpad.net/bugs/1303870/+attachment/4072166/+files/ProcStatus.txt ** Attachment removed: Registers.txt https://bugs.launchpad.net/bugs/1303870/+attachment/4072167/+files/Registers.txt ** Attachment removed: Stacktrace.txt https://bugs.launchpad.net/bugs/1303870/+attachment/4072168/+files/Stacktrace.txt ** Attachment removed: ThreadStacktrace.txt https://bugs.launchpad.net/bugs/1303870/+attachment/4072169/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 1283681 ** Information type changed from Private to Public ** Tags removed: need-i386-retrace -- 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/1303870 Title: notify-osd crashed with signal 5 in _XReply() Status in “notify-osd” package in Ubuntu: New Bug description: just an error, after login ProblemType: Crash DistroRelease: Ubuntu 14.04 Package: notify-osd 0.9.35+14.04.20140213-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-23.45-generic 3.13.8 Uname: Linux 3.13.0-23-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu1 Architecture: i386 CrashCounter: 1 CurrentDesktop: Unity Date: Mon Apr 7 16:57:10 2014 DesktopSession: 'ubuntu' ExecutablePath: /usr/lib/i386-linux-gnu/notify-osd GtkTheme: 'Ambiance' IconTheme: 'ubuntu-mono-dark' InstallationDate: Installed on 2014-01-03 (94 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release i386 (20131016.1) MachineType: Gigabyte Technology Co., Ltd. M52L-S3 ProcCmdline: /usr/lib/i386-linux-gnu/notify-osd ProcEnviron: XDG_RUNTIME_DIR=set SHELL=/bin/bash LANGUAGE=hu_HU PATH=(custom, no user) LANG=hu_HU.UTF-8 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-23-generic root=UUID=8293fe70-32d0-48c6-80a4-88e06cb9df99 ro quiet splash vt.handoff=7 RelatedPackageVersions: xserver-xorg 1:7.7+1ubuntu8 libgl1-mesa-glx 10.1.0-4ubuntu1 libdrm2 2.4.52-1 xserver-xorg-video-intel 2:2.99.910-0ubuntu1 xserver-xorg-video-ati 1:7.3.0-1ubuntu3 Signal: 5 SourcePackage: notify-osd StacktraceTop: ?? () from /usr/lib/i386-linux-gnu/libX11.so.6 _XReply () from /usr/lib/i386-linux-gnu/libX11.so.6 XGetGeometry () from /usr/lib/i386-linux-gnu/libX11.so.6 ?? () from /usr/lib/i386-linux-gnu/libgdk-3.so.0 gdk_window_get_geometry () from /usr/lib/i386-linux-gnu/libgdk-3.so.0 Title: notify-osd crashed with signal 5 in _XReply() UpgradeStatus: Upgraded to trusty on 2014-03-13 (24 days ago) UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo vboxusers dmi.bios.date: 08/11/2009 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F9a dmi.board.name: M52L-S3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF9a:bd08/11/2009:svnGigabyteTechnologyCo.,Ltd.:pnM52L-S3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnM52L-S3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: M52L-S3 dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/notify-osd/+bug/1303870/+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 1303310] Re: Screensaver isn't triggered right after the first boot
*** This bug is a duplicate of bug 1245474 *** https://bugs.launchpad.net/bugs/1245474 ** This bug has been marked a duplicate of bug 1245474 [regression] on login screen, monitor stays on forever -- 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/1303310 Title: Screensaver isn't triggered right after the first boot Status in Unity: New Status in “unity” package in Ubuntu: Triaged Bug description: Hi all, as previously posted on Ubuntu-Bugsquad ML: I noticed that on a fresh boot the screensaver will not be triggered, may be because no user is already logged so there's no such policy enabled.[0] Now, the downside of this behaviour is that computers turned on and awaiting for users to be logged in will stay indefinitely with their monitors/screens on, wasting energy and degrading the hardware. Nowadays it's a common practice in public institutions and companies to shut down every device that's not running any critical service mostly for two big reasons: a. security measures and b. to cut energy and hardware waste to save money. The problem is that on next morning when staff turns on the systems again the machines will keep their screens on all the time until coworkers or general public - like on a public library - arrives. I could think of several workarounds like adding a cron job or even something simpler, an 'at' command to every /etc/rc.local to instruct to `xset -display :0 dpms force off' at a given time to ensure the monitors will be properly off after system boot until users arrive, but I would prefer to stay away from any non-necessary hack if there's an official, supported way to do this. Thank you very much! [0] I'm guessing here, I'm not familiarized with Ubuntu's internals... ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-23.45-generic 3.13.8 Uname: Linux 3.13.0-23-generic x86_64 NonfreeKernelModules: wl .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Sun Apr 6 07:48:35 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:163d] Advanced Micro Devices, Inc. [AMD/ATI] Madison [Mobility Radeon HD 5650/5750 / 6530M/6550M] [1002:68c1] (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:163d] InstallationDate: Installed on 2014-03-17 (20 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140315) MachineType: Hewlett-Packard HP Pavilion dv7 Notebook PC ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-23-generic root=UUID=14188451-0e78-4324-aa27-474fd4351293 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/07/2011 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: F.29 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 163D dmi.board.vendor: Hewlett-Packard dmi.board.version: 65.38 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: N/A dmi.modalias: dmi:bvnHewlett-Packard:bvrF.29:bd11/07/2011:svnHewlett-Packard:pnHPPaviliondv7NotebookPC:pvr058812242B20010020100:rvnHewlett-Packard:rn163D:rvr65.38:cvnHewlett-Packard:ct10:cvrN/A: dmi.product.name: HP Pavilion dv7 Notebook PC dmi.product.version: 058812242B20010020100 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.11+14.04.20140328-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-4ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-4ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.15.0-1ubuntu7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Sun Apr 6 05:54:41 2014 xserver.configfile: default xserver.errors: RADEON(G0): [XvMC] Failed to initialize extension. xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id
[Dx-packages] [Bug 993397] Re: vdpau not working (well) with Ubuntu12.04 Unity
I even tried nvidia 331 on 14.04 still the same problem goes in the loop after login and nothing on the screen iand vdpau hardware acceleration cant be enabled -- 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/993397 Title: vdpau not working (well) with Ubuntu12.04 Unity Status in Compiz: Fix Released Status in Compiz Core: Fix Released Status in NVIDIA Drivers Ubuntu: Fix Released Status in Unity: Invalid Status in “compiz” package in Ubuntu: Fix Released Status in “unity” package in Ubuntu: Invalid Bug description: vdpau works very poorly in Ubuntu 12.04 LTS on Unity3d. Same 1080p movies use around 6-10% of cpu in 11.04 and 11.10 shoots up to 50-60% of cpu usage in 12.04 with vdpau and mplayer (all under Unity 3d) . I have tried several nvidia drivers and the results are the same (Nvidia current 295.40, 295.20 and 295.33 32 bits) Videocard is Nvidia G105M This seems to be a Unity rather than a Nvidia bug as cpu usage drops back to around 6 -10% for same movies in Gnome shell. To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/993397/+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 1303812] Re: Options in sidebar not aligned properly with reduced display scaling
Thanks, I can confirm that ** Changed in: unity Status: New = Confirmed -- 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/1303812 Title: Tooltips incorrectly handle reduced display scaling Status in Unity: Confirmed Status in “unity” package in Ubuntu: Confirmed Bug description: When I change my scaling in Settings Display from 1 to anything less than that, some parts of unity's alignment gets messed up. For instance, when I right click on Firefox, instead of Open New Window, I get Open New Window Open. I've attached a screenshot for clarification. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1303812/+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 1303812] Re: Tooltips incorrectly handle reduced display scaling
** Summary changed: - Options in sidebar not aligned properly with reduced display scaling + Tooltips incorrectly handle reduced display scaling -- 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/1303812 Title: Tooltips incorrectly handle reduced display scaling Status in Unity: Confirmed Status in “unity” package in Ubuntu: Confirmed Bug description: When I change my scaling in Settings Display from 1 to anything less than that, some parts of unity's alignment gets messed up. For instance, when I right click on Firefox, instead of Open New Window, I get Open New Window Open. I've attached a screenshot for clarification. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1303812/+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 1303395] Re: HUD search works incorrectly
** Package changed: unity (Ubuntu) = hud (Ubuntu) ** Also affects: hud Importance: Undecided Status: New -- You received this bug notification because you are a member of DX Packages, which is subscribed to hud in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1303395 Title: HUD search works incorrectly Status in Unity HUD: New Status in “hud” package in Ubuntu: New Bug description: my app (sublime text3) have menu item Tools-Build I open HUD (pressing Alt key) and begin type build. But when I have typed bu, i expect to see my wished menu build. Unfortunately i see list of strange menus (see incorrect_search1.png from attachement) And just when i type FULL name of wished menu build, i see what i want to see (see incorrect_search2.png from attachement) ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.0+14.04.20140403-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-19.40-generic 3.13.6 Uname: Linux 3.13.0-19-generic x86_64 To manage notifications about this bug go to: https://bugs.launchpad.net/hud/+bug/1303395/+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 1134202] Re: Removing overlay-scrollbar causes lots of noise
It affects me on Ubuntu 13.10 -- You received this bug notification because you are a member of DX Packages, which is subscribed to overlay-scrollbar in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1134202 Title: Removing overlay-scrollbar causes lots of noise Status in “overlay-scrollbar” package in Ubuntu: Confirmed Bug description: The overlay-scrollbar package can be removed to disable the modified scrollbar, reverting to classic scrollbars. If this is done, nearly every GTK application will emit the following error when started: Gtk-Message: Failed to load module overlay-scrollbar ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: overlay-scrollbar (not installed) ProcVersionSignature: Ubuntu 3.8.0-7.15-generic 3.8.0 Uname: Linux 3.8.0-7-generic x86_64 ApportVersion: 2.8-0ubuntu4 Architecture: amd64 Date: Wed Feb 27 17:44:39 2013 EcryptfsInUse: Yes InstallationDate: Installed on 2013-02-26 (1 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Alpha amd64 (20130225) MarkForUpload: True SourcePackage: overlay-scrollbar UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/overlay-scrollbar/+bug/1134202/+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 1303912] Re: compiz crashed with SIGSEGV in g_main_context_dispatch()
*** This bug is a duplicate of bug 962581 *** https://bugs.launchpad.net/bugs/962581 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 #962581, 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/1303912/+attachment/4072337/+files/CoreDump.gz ** Attachment removed: Disassembly.txt https://bugs.launchpad.net/bugs/1303912/+attachment/4072339/+files/Disassembly.txt ** Attachment removed: ProcMaps.txt https://bugs.launchpad.net/bugs/1303912/+attachment/4072341/+files/ProcMaps.txt ** Attachment removed: ProcStatus.txt https://bugs.launchpad.net/bugs/1303912/+attachment/4072342/+files/ProcStatus.txt ** Attachment removed: Registers.txt https://bugs.launchpad.net/bugs/1303912/+attachment/4072343/+files/Registers.txt ** Attachment removed: Stacktrace.txt https://bugs.launchpad.net/bugs/1303912/+attachment/4072344/+files/Stacktrace.txt ** Attachment removed: ThreadStacktrace.txt https://bugs.launchpad.net/bugs/1303912/+attachment/4072345/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of bug 962581 compiz crashed with SIGSEGV in empty() from check_selection() [unity-rvgrid-accessible.cpp:171] ** Information type changed from Private to Public ** Tags removed: need-i386-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/1303912 Title: compiz crashed with SIGSEGV in g_main_context_dispatch() Status in “unity” package in Ubuntu: New Bug description: This bug occurred when I was using Dash Home to search for Rhythmbox. ProblemType: Crash DistroRelease: Ubuntu 12.04 Package: unity 5.20.0-0ubuntu3 ProcVersionSignature: Ubuntu 3.2.0-60.91-generic-pae 3.2.55 Uname: Linux 3.2.0-60-generic-pae i686 ApportVersion: 2.0.1-0ubuntu17.6 Architecture: i386 CrashCounter: 1 Date: Mon Apr 7 22:20:48 2014 ExecutablePath: /usr/bin/compiz InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release i386 (20120423) MarkForUpload: True ProcCmdline: compiz SegvAnalysis: Segfault happened at: 0xb47a772f:mov0x4(%ecx),%edx PC (0xb47a772f) ok source 0x4(%ecx) (0x0074) not located in a known VMA region (needed readable region)! destination %edx ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: unity StacktraceTop: ?? () from /usr/lib/compiz/libunityshell.so ?? () from /usr/lib/compiz/libunityshell.so ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0 g_main_context_dispatch () from /lib/i386-linux-gnu/libglib-2.0.so.0 ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0 Title: compiz crashed with SIGSEGV in g_main_context_dispatch() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1303912/+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 1250262] Re: Calling EndSessionDialog.Open(Restart) opens the dialog with a focused 'Shutdown' button
Trusty 14.04 is set to release April 26th and this is still an issue. Perhaps the easiest solution would be to remove the restart option from that menu and rename Shutdown... to Restart/Shutdown... or Power Off While this is not a security issue or performance drain, it is something every user will notice right away. I feel that an LTS release should have these sorts of things very polished and clear. -- 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/1250262 Title: Calling EndSessionDialog.Open(Restart) opens the dialog with a focused 'Shutdown' button Status in The Session Menu: Invalid Status in Unity: Triaged Status in “unity” package in Ubuntu: Triaged Bug description: Ubuntu 13.10. Selecting the power-cog restart should result in the popup highlighting/pre-selecting Restart so users only have to hit Enter. Presently users who select Restart from the power-cog menu have to then use the cursor keys to actually select Restart else a shutdown will occur. It makes no sense to put Restart in the power-cog menu only to have the popup that appears highlight Shutdown To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-session/+bug/1250262/+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 1235754] Re: quassel-* entry missing from indicator plugin (envelope), and tray icon doesn't work.
This is still an issue on all of my 14.04 installs right now. -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-application in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1235754 Title: quassel-* entry missing from indicator plugin (envelope), and tray icon doesn't work. Status in Application Indicators: New Status in “indicator-application” package in Ubuntu: Confirmed Bug description: in 13.04 (Raring), Quassel doesn't have an entry in the messaging applet anymore (The Envelope), and the tray icon does not work. To duplicate, install either of the quassel, quassel-client applications, and launch. In 12.04 there is an entry in the messaging menu, but in 13.04 there is not. Also enabling the tray icon in quassel has no effect. There is simply no tray icon. To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-application/+bug/1235754/+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 1235754] Re: quassel-* entry missing from indicator plugin (envelope), and tray icon doesn't work.
** Also affects: indicator-application Importance: Undecided Status: New -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-application in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1235754 Title: quassel-* entry missing from indicator plugin (envelope), and tray icon doesn't work. Status in Application Indicators: New Status in “indicator-application” package in Ubuntu: Confirmed Bug description: in 13.04 (Raring), Quassel doesn't have an entry in the messaging applet anymore (The Envelope), and the tray icon does not work. To duplicate, install either of the quassel, quassel-client applications, and launch. In 12.04 there is an entry in the messaging menu, but in 13.04 there is not. Also enabling the tray icon in quassel has no effect. There is simply no tray icon. To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-application/+bug/1235754/+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 1303060] Re: Unity Gestures don't honor alt_tab_bias_viewport setting
** Branch linked: lp:~beidl/unity/unity -- 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/1303060 Title: Unity Gestures don't honor alt_tab_bias_viewport setting Status in Unity: New Status in “unity” package in Ubuntu: New Bug description: My new Elantech touchpad supports Unitys multitouch gestures, but I've noticed one inconsistency. I like seeing running applications from all workspaces in my Alt-Tab view, but by using the three-finger gestures on my touchpad I can only see applications on the current workspace. When I uncheck alt_tab_bias_viewport in CCSM, I expect Alt-Tab as well as Unity Gestures to behave the same way. The problem: The switcher only shows applications running on the current workspace when using Unity Gestures, even though I've unchecked Bias alt-tab to prefer windows on the current viewport. The fix: Show all windows if alt_tab_bias_viewport is unchecked. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.0+14.04.20140403-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-23.45-generic 3.13.8 Uname: Linux 3.13.0-23-generic x86_64 ApportVersion: 2.14.1-0ubuntu1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Sat Apr 5 16:25:24 2014 InstallationDate: Installed on 2014-04-04 (0 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Daily amd64 (20140404) SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1303060/+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 1235754] Re: quassel-* entry missing from indicator plugin (envelope), and tray icon doesn't work.
If I correctly recall, this particularly affects GTK+-based desktops. But I reckon we'll need to have someone confirm that it works in Kubuntu (and/or LXDE-Qt by extension), as per the now-closed Quassel bug #1234, reported by the same filer: http://bugs.quassel-irc.org/issues/1234 -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-application in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1235754 Title: quassel-* entry missing from indicator plugin (envelope), and tray icon doesn't work. Status in Application Indicators: New Status in “indicator-application” package in Ubuntu: Confirmed Bug description: in 13.04 (Raring), Quassel doesn't have an entry in the messaging applet anymore (The Envelope), and the tray icon does not work. To duplicate, install either of the quassel, quassel-client applications, and launch. In 12.04 there is an entry in the messaging menu, but in 13.04 there is not. Also enabling the tray icon in quassel has no effect. There is simply no tray icon. To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-application/+bug/1235754/+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 1235754] Re: quassel-* entry missing from indicator plugin (envelope), and tray icon doesn't work.
Caleb, also, this is not an issue in Kubuntu as they do not use any of the indicator-* stuff that I am aware of. ** Description changed: in 13.04 (Raring), Quassel doesn't have an entry in the messaging applet anymore (The Envelope), and the tray icon does not work. To duplicate, install either of the quassel, quassel-client applications, and launch. In 12.04 there is an entry in the messaging menu, but in 13.04 there is not. Also enabling the tray icon in quassel has no effect. There is simply no tray icon. + + EDIT: This has been an issue since 12.10, and it is still broken in + 14.04 -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-application in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1235754 Title: quassel-* entry missing from indicator plugin (envelope), and tray icon doesn't work. Status in Application Indicators: New Status in “indicator-application” package in Ubuntu: Confirmed Bug description: in 13.04 (Raring), Quassel doesn't have an entry in the messaging applet anymore (The Envelope), and the tray icon does not work. To duplicate, install either of the quassel, quassel-client applications, and launch. In 12.04 there is an entry in the messaging menu, but in 13.04 there is not. Also enabling the tray icon in quassel has no effect. There is simply no tray icon. EDIT: This has been an issue since 12.10, and it is still broken in 14.04 To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-application/+bug/1235754/+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 1235754] Re: quassel-* entry missing from indicator plugin (envelope), and tray icon doesn't work.
Very well. I was going to tag as Also affects project, but Launchpad does not recognize the URL at the new bug tracker page... let me try a quick workaround. -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-application in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1235754 Title: quassel-* entry missing from indicator plugin (envelope), and tray icon doesn't work. Status in Application Indicators: New Status in “indicator-application” package in Ubuntu: Confirmed Bug description: in 13.04 (Raring), Quassel doesn't have an entry in the messaging applet anymore (The Envelope), and the tray icon does not work. To duplicate, install either of the quassel, quassel-client applications, and launch. In 12.04 there is an entry in the messaging menu, but in 13.04 there is not. Also enabling the tray icon in quassel has no effect. There is simply no tray icon. EDIT: This has been an issue since 12.10, and it is still broken in 14.04 To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-application/+bug/1235754/+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 1235754] Re: quassel-* entry missing from indicator plugin (envelope), and tray icon doesn't work.
Also see this bug: http://bugs.quassel-irc.org/issues/1269 -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-application in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1235754 Title: quassel-* entry missing from indicator plugin (envelope), and tray icon doesn't work. Status in Application Indicators: New Status in “indicator-application” package in Ubuntu: Confirmed Bug description: in 13.04 (Raring), Quassel doesn't have an entry in the messaging applet anymore (The Envelope), and the tray icon does not work. To duplicate, install either of the quassel, quassel-client applications, and launch. In 12.04 there is an entry in the messaging menu, but in 13.04 there is not. Also enabling the tray icon in quassel has no effect. There is simply no tray icon. EDIT: This has been an issue since 12.10, and it is still broken in 14.04 To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-application/+bug/1235754/+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 1304012] [NEW] Can't see launcher and panel when i minimize all windows and HoN is running
Public bug reported: When i minimize all windows(Ctrl+super+D) while i'm running HoN(Heroes of Newerth game) i can't see launcher and panel at all, just blank desktop and when i try rigt click on empty desktop they appear and when right menu is close then they are again gone. Just to mention when i point mouse in direction where suppose to be icons in launcher they are running ok just when app is full window again, i cant see launcher and top panel. When i'm not running HoN and try to minimize everything is ok. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.0+14.04.20140404-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-23.45-generic 3.13.8 Uname: Linux 3.13.0-23-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/0' .proc.driver.nvidia.registry: Binary: .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 331.38 Wed Jan 8 19:32:30 PST 2014 GCC version: gcc version 4.8.2 (Ubuntu 4.8.2-17ubuntu2) .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Mon Apr 7 22:09:43 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: bbswitch, 0.7, 3.13.0-20-generic, x86_64: installed bbswitch, 0.7, 3.13.0-23-generic, x86_64: installed nvidia-331, 331.38, 3.13.0-23-generic, x86_64: installed GraphicsCard: NVIDIA Corporation C79 [GeForce G102M] [10de:0873] (rev b1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GeForce G102M [1043:19b4] InstallationDate: Installed on 2014-03-28 (9 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Beta amd64 (20140326) Lsusb: Bus 001 Device 004: ID 04f2:b071 Chicony Electronics Co., Ltd 2.0M UVC Webcam / CNF7129 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 003: ID 09da:0260 A4 Tech Co., Ltd KV-300H Isolation Keyboard Bus 002 Device 002: ID 046d:c52f Logitech, Inc. Unifying Receiver Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: ASUSTeK Computer Inc. K50IN ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-23-generic root=UUID=b12e284a-6f61-47bb-a399-c0fab3d5cf59 ro quiet splash SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/08/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 207 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: K50IN dmi.board.vendor: ASUSTeK Computer Inc. dmi.board.version: 1.0 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK Computer Inc. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr207:bd05/08/2009:svnASUSTeKComputerInc.:pnK50IN:pvr1.0:rvnASUSTeKComputerInc.:rnK50IN:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr: dmi.product.name: K50IN dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK Computer Inc. version.compiz: compiz 1:0.9.11+14.04.20140404-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-4ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-4ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A version.xserver-xorg-core: xserver-xorg-core 2:1.15.0-1ubuntu7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Mon Apr 7 18:16:02 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.0-1ubuntu7 ** Affects: unity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 trusty ubuntu ** Description changed: - When i minimize all windows while i'm running HoN(Heroes of Newerth game) i can't see launcher and panel at all, just blank desktop and when i try rigt click on empty desktop they appear and when right menu is close then they are again gone. + When i minimize all windows(Ctrl+super+D) while i'm running HoN(Heroes of Newerth game) i can't see launcher and panel at all, just blank desktop and when i try rigt click on empty desktop they appear and when right menu is close then they are again gone. Just to mention when i point mouse in direction where suppose to be icons in launcher they are running ok just when app is full window again, i cant see launcher and top panel. When i'm not running HoN and try to minimize everything is ok. ProblemType: Bug DistroRelease:
[Dx-packages] [Bug 1303317] Re: dots not lined up on lock screen
Ah, yes. That's what I meant - thank you! -- 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/1303317 Title: dots not lined up on lock screen Status in Unity: New Status in “unity” package in Ubuntu: New Bug description: I understand a similar bug was fixed a week or two ago involving the login screen, whereby the dots pattern did not line up properly with the new default wallpaper. Now when locking the screen I have noticed that the dots pattern is in the wrong place, if the right place is where they are on the login screen. They also go through the Ubuntu 14.04 LTS logo in the bottom left rather than around it, and the central dot on the screen is slightly below the central point of the default wallpaper, as opposed to rows above and below the centre as in the login screen. I am running through an NVIDEA GTX 650 with screen resolution 1920x1080. This doesn't seem to be limited to me though, as you can see the same thing in the video http://www.youtube.com/watch?feature=player_detailpagev=ZAREcpd6_eE#t=100 by Joey Sneddon (1:40) Finally, I'm reporting this against lightdm as it seems the most appropriate package; please advise if it is not! ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: lightdm 1.9.14-0ubuntu2 ProcVersionSignature: Ubuntu 3.11.0-19.33-generic 3.11.10.5 Uname: Linux 3.11.0-19-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Sun Apr 6 12:24:02 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2014-01-11 (84 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) SourcePackage: lightdm UpgradeStatus: Upgraded to trusty on 2014-04-01 (4 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1303317/+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 1280337] Re: Dependency on webbrowser-app seems ill-advised
The dependency chain here looks like this: unity - bamfdaemon - libunity-webapps0 - unity-webapps-service - webapp-container - webbrowser-app. My initial feeling was that bamfdaemon just shouldn't depend on libunity-webapps0, because we dropped a bunch of webapps code from bamf following the switch to the container, however upon looking at the code there it seems bamf and libunity-webapps are tightly integrated, so that seemed like a nontrivial task to split. Then I started looking at the chain and it wasn't clear to me whether unity-webapp-service should stop depending on webapp-container, or whether webapp-container stop depending on webbrowser-app. -- 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/1280337 Title: Dependency on webbrowser-app seems ill-advised Status in “libunity-webapps” package in Ubuntu: Confirmed Bug description: So if a user decides to uninstall webbrowser-app then they will basically destroy their install. If done thru software-center there is no real indication of what is about to happen. (Bug 1278869 ) If done thru the Dash even a bit worse as the uninstall(s) are done silently in the background ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity-webapps-service 2.5.0~+14.04.20140205-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-8.28-generic 3.13.2 Uname: Linux 3.13.0-8-generic x86_64 ApportVersion: 2.13.2-0ubuntu3 Architecture: amd64 CurrentDesktop: Unity Date: Fri Feb 14 10:12:33 2014 SourcePackage: libunity-webapps UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libunity-webapps/+bug/1280337/+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 1235754] Re: quassel-* entry missing from indicator plugin (envelope), and tray icon doesn't work.
Nope, no avail. I filed against Launchpad itself for that, but the link in comment #9 needs to be linked to that bug. ** Also affects: quassel Importance: Undecided Status: New -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-application in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1235754 Title: quassel-* entry missing from indicator plugin (envelope), and tray icon doesn't work. Status in Application Indicators: New Status in Quassel Irc Client: New Status in “indicator-application” package in Ubuntu: Confirmed Bug description: in 13.04 (Raring), Quassel doesn't have an entry in the messaging applet anymore (The Envelope), and the tray icon does not work. To duplicate, install either of the quassel, quassel-client applications, and launch. In 12.04 there is an entry in the messaging menu, but in 13.04 there is not. Also enabling the tray icon in quassel has no effect. There is simply no tray icon. EDIT: This has been an issue since 12.10, and it is still broken in 14.04 To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-application/+bug/1235754/+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 1304026] [NEW] When apps are started some have the close button and such under the upper bar
Public bug reported: The window from an opened app, for example virt-manager , the close and minimize button are under the upper bar in the screen. To reach it, I can use the alt key to drag the window down, but for a lot of new users this might be difficult, not knowing this. I noticed this with other apps to. Seems to be some windowing issue thus I reported it against unity. I have this on multiple systems with various video cards. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.0+14.04.20140404-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-23.45-generic 3.13.8 Uname: Linux 3.13.0-23-generic x86_64 ApportVersion: 2.14.1-0ubuntu1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Mon Apr 7 22:40:19 2014 InstallationDate: Installed on 2014-04-06 (1 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140303) SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: unity (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug trusty -- 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/1304026 Title: When apps are started some have the close button and such under the upper bar Status in “unity” package in Ubuntu: Confirmed Bug description: The window from an opened app, for example virt-manager , the close and minimize button are under the upper bar in the screen. To reach it, I can use the alt key to drag the window down, but for a lot of new users this might be difficult, not knowing this. I noticed this with other apps to. Seems to be some windowing issue thus I reported it against unity. I have this on multiple systems with various video cards. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.0+14.04.20140404-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-23.45-generic 3.13.8 Uname: Linux 3.13.0-23-generic x86_64 ApportVersion: 2.14.1-0ubuntu1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Mon Apr 7 22:40:19 2014 InstallationDate: Installed on 2014-04-06 (1 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140303) 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/1304026/+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 1280337] Re: Dependency on webbrowser-app seems ill-advised
** Also affects: libunity-webapps Importance: Undecided Status: New ** Also affects: bamf Importance: Undecided Status: New ** Branch linked: lp:~abreu-alexandre/bamf/remove-webapps-deps -- 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/1280337 Title: Dependency on webbrowser-app seems ill-advised Status in BAMF Application Matching Framework: New Status in WebApps: libunity: New Status in “libunity-webapps” package in Ubuntu: Confirmed Bug description: So if a user decides to uninstall webbrowser-app then they will basically destroy their install. If done thru software-center there is no real indication of what is about to happen. (Bug 1278869 ) If done thru the Dash even a bit worse as the uninstall(s) are done silently in the background ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity-webapps-service 2.5.0~+14.04.20140205-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-8.28-generic 3.13.2 Uname: Linux 3.13.0-8-generic x86_64 ApportVersion: 2.13.2-0ubuntu3 Architecture: amd64 CurrentDesktop: Unity Date: Fri Feb 14 10:12:33 2014 SourcePackage: libunity-webapps UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/bamf/+bug/1280337/+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 1304073] [NEW] 14.04 Unity pips (white dots in bar) are now too small.
Public bug reported: On all 14.04 installs I've tinkered with so far they've all exhibited this behavior. The pips (white dots) next to the icons in the Unity bar are too small. I never noticed this before, so I went back to a 13.10 install to compare. The pips on 14.04 are so small that they, quite frankly, feel useless. They need to be of adequate size in an effort to be easily seen by the user, regardless of the actual icon size. Take note of the size of the white pips on the Unity launcher in the following screenshots. https://www.dropbox.com/sh/mc4k4yyjm5nbbzk/4t6SgqVN8H Here's an alternative 'direct download' link to the images just in case: http://skynetcore.org/shared/pips.tar.gz In an effort to present an accurate comparison I included the following screenshots (note that 48 px on both 13.10 and 14.04 seem identical, it's just the smaller sizes that down-scale too far) 13.10 - 32 px 14.04 - 32 px 13.10 - 48 px 14.04 - 48 px I also included a 5th screenshot of 26 px in 14.04 in case it helps further show what I'm referencing. While scaling the size of the pips makes sense to a certain degree, the current behavior scales them far too small. I feel as though they should have (at minimal) a 13.10 oriented type of scaling so they are more easily viewable, and therefore, more useful. If they could be adjusted in size, that would be a monumental bonus as well, but I have a feeling that might be a stretch for the given time frame. :) Thank you for your time! ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.0+14.04.20140403-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-23.45-generic 3.13.8 Uname: Linux 3.13.0-23-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Mon Apr 7 17:41:39 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Toshiba America Info Systems Device [1179:0009] InstallationDate: Installed on 2014-04-01 (6 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Daily amd64 (20140330) MachineType: TOSHIBA PORTEGE Z835 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-23-generic root=UUID=5d7f7158-1b5b-4946-9916-b8a0c2f59525 ro quiet splash vt.handoff=7 SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/08/2012 dmi.bios.vendor: TOSHIBA dmi.bios.version: Version 1.60 dmi.board.asset.tag: 00 dmi.board.name: Portable PC dmi.board.vendor: TOSHIBA dmi.board.version: Version A0 dmi.chassis.asset.tag: 00 dmi.chassis.type: 10 dmi.chassis.vendor: TOSHIBA dmi.chassis.version: Version 1.0 dmi.modalias: dmi:bvnTOSHIBA:bvrVersion1.60:bd02/08/2012:svnTOSHIBA:pnPORTEGEZ835:pvrPT224U-013021:rvnTOSHIBA:rnPortablePC:rvrVersionA0:cvnTOSHIBA:ct10:cvrVersion1.0: dmi.product.name: PORTEGE Z835 dmi.product.version: PT224U-013021 dmi.sys.vendor: TOSHIBA version.compiz: compiz 1:0.9.11+14.04.20140328-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-4ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-4ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.15.0-1ubuntu7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Mon Apr 7 17:24:40 2014 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.15.0-1ubuntu7 ** Affects: unity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 trusty ubuntu -- 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/1304073 Title: 14.04 Unity pips (white dots in bar) are now too small. Status in “unity” package in Ubuntu: New Bug description: On all 14.04 installs I've tinkered with so far they've all exhibited this behavior. The pips (white dots) next to the icons in the Unity bar are too small. I never noticed this before, so I went back to a 13.10 install to compare. The pips on 14.04 are so small that they, quite frankly, feel useless. They need to be of adequate size in an effort to be easily seen by the user, regardless of the actual
[Dx-packages] [Bug 1303731] Re: Status-Notifier plugin of Cairo-Dock is broken when using indicator-application-12.10.1+14.04.20140324 and newer
Hello Indicator Application devs, On a Cairo-Dock session ($XDG_CURRENT_DESKTOP == Unity ; $DESKTOP_SESSION == cairo-dock), the Status-Notifier plugin of Cairo- Dock is broken when using the version 12.10.1+14.04.20140324 (or newer) of Indicator Application. Do you have any idea why Cairo-Dock's plugin is broken now? It seems that 'nm-applet' and 'indicator-application-service' are correctly launched. Is it possible that Indicator Application is now restricted to some sessions? Or did you change some DBus signals? (sorry, we are currently very busy... any help to fix this bug is welcome ;-) ) -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-application in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1303731 Title: Status-Notifier plugin of Cairo-Dock is broken when using indicator- application-12.10.1+14.04.20140324 and newer Status in “cairo-dock-plug-ins” package in Ubuntu: New Status in “indicator-application” package in Ubuntu: New Bug description: Hello, When using indicator-application-12.10.1+14.04.20140324 (or newer), Status-Notifier plugin seems broken: I can't no longer see applications like nm-applet and dropbox. I'll try to provide some debug log ASAP! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cairo-dock-plug-ins/+bug/1303731/+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 1163041] Re: Inconsistent behaviour with minimized Trash windows
*Note* this only happens when Nautilus is locked to the launcher! -- 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/1163041 Title: Inconsistent behaviour with minimized Trash windows Status in Ayatana Design: Confirmed Status in One Hundred Papercuts: Triaged Status in Unity: Confirmed Status in “unity” package in Ubuntu: Triaged Bug description: Now with a fix for LP: #753938 being merged into raring, this presents a new usability challenge to users. The issue: When you open a trash window from the launcher and minimize it, it gets minimized into the Nautilus icon. However, a user would then expect to get the window back by clicking the icon where the window minimized into in the first place, in this case, the Nautilus icon in the launcher. Instead, it opens a new Nautilus window. The issue here is that trash windows and every other Nautilus window are only seperated logically from each other, but not visually. The fix: When minimizing the trash window, instead of minimizing into the Nautilus icon, it should minimize the window into the trash icon in the launcher. I'm purely talking about the minimize animation and triangle next to the trash icon here. Description: Ubuntu Raring Ringtail (development branch) Release: 13.04 unity: Installiert: 6.12.0daily13.04.01-0ubuntu1 Installationskandidat: 6.12.0daily13.04.01-0ubuntu1 Versionstabelle: *** 6.12.0daily13.04.01-0ubuntu1 0 500 http://archive.ubuntu.com/ubuntu/ raring/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: unity 6.12.0daily13.04.01-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-15.25-generic 3.8.4 Uname: Linux 3.8.0-15-generic x86_64 ApportVersion: 2.9.2-0ubuntu5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' Date: Tue Apr 2 00:23:51 2013 MarkForUpload: True SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/1163041/+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 1292647] Re: Esc does not clear the password input field in the unity lock screen
** Changed in: unity 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/1292647 Title: Esc does not clear the password input field in the unity lock screen Status in Unity: Fix Released Status in “unity” package in Ubuntu: Fix Released Bug description: When hitting the escape key in the Unity lock screen password prompt, the password prompt is not cleared, whereas it used to be cleared in the old gnome-screensaver, as well as the lightdm login screen. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.1.2+14.04.20140312-0ubuntu1 Uname: Linux 3.13.4-hyper1 x86_64 ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 CompizPlugins: [core,composite,opengl,copytex,compiztoolbox,decor,vpswitch,extrawm,text,resize,ring,screenshot,place,commands,put,mousepoll,move,gnomecompat,annotate,blur,clone,widget,regex,imgpng,animation,obs,workarounds,neg,bicubic,resizeinfo,grid,expo,session,wall,showmouse,ezoom,unitymtgrabhandles,fade,scale,scalefilter,showdesktop,scaleaddon,unityshell] CurrentDesktop: Unity Date: Fri Mar 14 22:29:30 2014 SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2014-03-03 (11 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1292647/+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 1304095] [NEW] notify-osd crashed with signal 5 in _XReply()
Public bug reported: a crash when exiting to play a game on wine... all suddely goes black and returned after some seconds. Ubuntu 14.04 32bit daily iso ProblemType: Crash DistroRelease: Ubuntu 14.04 Package: notify-osd 0.9.35+14.04.20140213-0ubuntu1 Uname: Linux 3.14.0-031400-generic i686 ApportVersion: 2.14.1-0ubuntu1 Architecture: i386 CurrentDesktop: Unity Date: Tue Apr 8 01:18:53 2014 DesktopSession: 'ubuntu' ExecutablePath: /usr/lib/i386-linux-gnu/notify-osd GtkTheme: 'Ambiance' IconTheme: 'ubuntu-mono-dark' InstallationDate: Installed on 2014-04-07 (0 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Daily i386 (20140407) MachineType: TOSHIBA Satellite L500 ProcCmdline: /usr/lib/i386-linux-gnu/notify-osd ProcEnviron: XDG_RUNTIME_DIR=set SHELL=/bin/bash LANGUAGE=it PATH=(custom, no user) LANG=it_IT.UTF-8 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.14.0-031400-generic root=UUID=0ea301d0-8e87-4e24-ab0e-f14f0b26c277 ro quiet splash vt.handoff=7 RelatedPackageVersions: xserver-xorg 1:7.7+1ubuntu8 libgl1-mesa-glx 10.1.0-4ubuntu1 libdrm2 2.4.52-1 xserver-xorg-video-intel 2:2.99.910-0ubuntu1 xserver-xorg-video-ati 1:7.3.0-1ubuntu3 Signal: 5 SourcePackage: notify-osd StacktraceTop: ?? () from /usr/lib/i386-linux-gnu/libX11.so.6 _XReply () from /usr/lib/i386-linux-gnu/libX11.so.6 XGetGeometry () from /usr/lib/i386-linux-gnu/libX11.so.6 ?? () from /usr/lib/i386-linux-gnu/libgdk-3.so.0 gdk_window_get_geometry () from /usr/lib/i386-linux-gnu/libgdk-3.so.0 Title: notify-osd crashed with signal 5 in _XReply() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo dmi.bios.date: 05/06/2010 dmi.bios.vendor: TOSHIBA dmi.bios.version: V2.10 dmi.board.name: KSWAA dmi.board.vendor: TOSHIBA dmi.board.version: 1.00 dmi.chassis.asset.tag: * dmi.chassis.type: 10 dmi.chassis.vendor: TOSHIBA dmi.chassis.version: N/A dmi.modalias: dmi:bvnTOSHIBA:bvrV2.10:bd05/06/2010:svnTOSHIBA:pnSatelliteL500:pvrPSLS3E-03W01RIT:rvnTOSHIBA:rnKSWAA:rvr1.00:cvnTOSHIBA:ct10:cvrN/A: dmi.product.name: Satellite L500 dmi.product.version: PSLS3E-03W01RIT dmi.sys.vendor: TOSHIBA glxinfo: Error: [Errno 2] File o directory non esistente: 'glxinfo' ** Affects: notify-osd (Ubuntu) Importance: Undecided Status: New ** Tags: apport-crash i386 need-i386-retrace trusty ** Information type changed from Private to Public -- 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/1304095 Title: notify-osd crashed with signal 5 in _XReply() Status in “notify-osd” package in Ubuntu: New Bug description: a crash when exiting to play a game on wine... all suddely goes black and returned after some seconds. Ubuntu 14.04 32bit daily iso ProblemType: Crash DistroRelease: Ubuntu 14.04 Package: notify-osd 0.9.35+14.04.20140213-0ubuntu1 Uname: Linux 3.14.0-031400-generic i686 ApportVersion: 2.14.1-0ubuntu1 Architecture: i386 CurrentDesktop: Unity Date: Tue Apr 8 01:18:53 2014 DesktopSession: 'ubuntu' ExecutablePath: /usr/lib/i386-linux-gnu/notify-osd GtkTheme: 'Ambiance' IconTheme: 'ubuntu-mono-dark' InstallationDate: Installed on 2014-04-07 (0 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Daily i386 (20140407) MachineType: TOSHIBA Satellite L500 ProcCmdline: /usr/lib/i386-linux-gnu/notify-osd ProcEnviron: XDG_RUNTIME_DIR=set SHELL=/bin/bash LANGUAGE=it PATH=(custom, no user) LANG=it_IT.UTF-8 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.14.0-031400-generic root=UUID=0ea301d0-8e87-4e24-ab0e-f14f0b26c277 ro quiet splash vt.handoff=7 RelatedPackageVersions: xserver-xorg 1:7.7+1ubuntu8 libgl1-mesa-glx 10.1.0-4ubuntu1 libdrm2 2.4.52-1 xserver-xorg-video-intel 2:2.99.910-0ubuntu1 xserver-xorg-video-ati 1:7.3.0-1ubuntu3 Signal: 5 SourcePackage: notify-osd StacktraceTop: ?? () from /usr/lib/i386-linux-gnu/libX11.so.6 _XReply () from /usr/lib/i386-linux-gnu/libX11.so.6 XGetGeometry () from /usr/lib/i386-linux-gnu/libX11.so.6 ?? () from /usr/lib/i386-linux-gnu/libgdk-3.so.0 gdk_window_get_geometry () from /usr/lib/i386-linux-gnu/libgdk-3.so.0 Title: notify-osd crashed with signal 5 in _XReply() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo dmi.bios.date: 05/06/2010 dmi.bios.vendor: TOSHIBA dmi.bios.version: V2.10 dmi.board.name: KSWAA dmi.board.vendor: TOSHIBA dmi.board.version: 1.00 dmi.chassis.asset.tag: * dmi.chassis.type: 10 dmi.chassis.vendor: TOSHIBA dmi.chassis.version: N/A dmi.modalias: dmi:bvnTOSHIBA:bvrV2.10:bd05/06/2010:svnTOSHIBA:pnSatelliteL500:pvrPSLS3E-03W01RIT:rvnTOSHIBA:rnKSWAA:rvr1.00:cvnTOSHIBA:ct10:cvrN
[Dx-packages] [Bug 1304095] Re: notify-osd crashed with signal 5 in _XReply()
*** This bug is a duplicate of bug 1283681 *** https://bugs.launchpad.net/bugs/1283681 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 #1283681, 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/1304095/+attachment/4073303/+files/CoreDump.gz ** Attachment removed: Disassembly.txt https://bugs.launchpad.net/bugs/1304095/+attachment/4073306/+files/Disassembly.txt ** Attachment removed: ProcMaps.txt https://bugs.launchpad.net/bugs/1304095/+attachment/4073312/+files/ProcMaps.txt ** Attachment removed: ProcStatus.txt https://bugs.launchpad.net/bugs/1304095/+attachment/4073314/+files/ProcStatus.txt ** Attachment removed: Registers.txt https://bugs.launchpad.net/bugs/1304095/+attachment/4073315/+files/Registers.txt ** Attachment removed: Stacktrace.txt https://bugs.launchpad.net/bugs/1304095/+attachment/4073316/+files/Stacktrace.txt ** Attachment removed: ThreadStacktrace.txt https://bugs.launchpad.net/bugs/1304095/+attachment/4073317/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 1283681 ** Tags removed: need-i386-retrace -- 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/1304095 Title: notify-osd crashed with signal 5 in _XReply() Status in “notify-osd” package in Ubuntu: New Bug description: a crash when exiting to play a game on wine... all suddely goes black and returned after some seconds. Ubuntu 14.04 32bit daily iso ProblemType: Crash DistroRelease: Ubuntu 14.04 Package: notify-osd 0.9.35+14.04.20140213-0ubuntu1 Uname: Linux 3.14.0-031400-generic i686 ApportVersion: 2.14.1-0ubuntu1 Architecture: i386 CurrentDesktop: Unity Date: Tue Apr 8 01:18:53 2014 DesktopSession: 'ubuntu' ExecutablePath: /usr/lib/i386-linux-gnu/notify-osd GtkTheme: 'Ambiance' IconTheme: 'ubuntu-mono-dark' InstallationDate: Installed on 2014-04-07 (0 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Daily i386 (20140407) MachineType: TOSHIBA Satellite L500 ProcCmdline: /usr/lib/i386-linux-gnu/notify-osd ProcEnviron: XDG_RUNTIME_DIR=set SHELL=/bin/bash LANGUAGE=it PATH=(custom, no user) LANG=it_IT.UTF-8 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.14.0-031400-generic root=UUID=0ea301d0-8e87-4e24-ab0e-f14f0b26c277 ro quiet splash vt.handoff=7 RelatedPackageVersions: xserver-xorg 1:7.7+1ubuntu8 libgl1-mesa-glx 10.1.0-4ubuntu1 libdrm2 2.4.52-1 xserver-xorg-video-intel 2:2.99.910-0ubuntu1 xserver-xorg-video-ati 1:7.3.0-1ubuntu3 Signal: 5 SourcePackage: notify-osd StacktraceTop: ?? () from /usr/lib/i386-linux-gnu/libX11.so.6 _XReply () from /usr/lib/i386-linux-gnu/libX11.so.6 XGetGeometry () from /usr/lib/i386-linux-gnu/libX11.so.6 ?? () from /usr/lib/i386-linux-gnu/libgdk-3.so.0 gdk_window_get_geometry () from /usr/lib/i386-linux-gnu/libgdk-3.so.0 Title: notify-osd crashed with signal 5 in _XReply() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo dmi.bios.date: 05/06/2010 dmi.bios.vendor: TOSHIBA dmi.bios.version: V2.10 dmi.board.name: KSWAA dmi.board.vendor: TOSHIBA dmi.board.version: 1.00 dmi.chassis.asset.tag: * dmi.chassis.type: 10 dmi.chassis.vendor: TOSHIBA dmi.chassis.version: N/A dmi.modalias: dmi:bvnTOSHIBA:bvrV2.10:bd05/06/2010:svnTOSHIBA:pnSatelliteL500:pvrPSLS3E-03W01RIT:rvnTOSHIBA:rnKSWAA:rvr1.00:cvnTOSHIBA:ct10:cvrN/A: dmi.product.name: Satellite L500 dmi.product.version: PSLS3E-03W01RIT dmi.sys.vendor: TOSHIBA glxinfo: Error: [Errno 2] File o directory non esistente: 'glxinfo' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/notify-osd/+bug/1304095/+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 1304073] Re: 14.04 Unity pips (white dots in bar) are now too small.
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: unity (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1304073 Title: 14.04 Unity pips (white dots in bar) are now too small. Status in “unity” package in Ubuntu: Confirmed Bug description: On all 14.04 installs I've tinkered with so far they've all exhibited this behavior. The pips (white dots) next to the icons in the Unity bar are too small. I never noticed this before, so I went back to a 13.10 install to compare. The pips on 14.04 are so small that they, quite frankly, feel useless. They need to be of adequate size in an effort to be easily seen by the user, regardless of the actual icon size. Take note of the size of the white pips on the Unity launcher in the following screenshots. https://www.dropbox.com/sh/mc4k4yyjm5nbbzk/4t6SgqVN8H Here's an alternative 'direct download' link to the images just in case: http://skynetcore.org/shared/pips.tar.gz In an effort to present an accurate comparison I included the following screenshots (note that 48 px on both 13.10 and 14.04 seem identical, it's just the smaller sizes that down-scale too far) 13.10 - 32 px 14.04 - 32 px 13.10 - 48 px 14.04 - 48 px I also included a 5th screenshot of 26 px in 14.04 in case it helps further show what I'm referencing. While scaling the size of the pips makes sense to a certain degree, the current behavior scales them far too small. I feel as though they should have (at minimal) a 13.10 oriented type of scaling so they are more easily viewable, and therefore, more useful. If they could be adjusted in size, that would be a monumental bonus as well, but I have a feeling that might be a stretch for the given time frame. :) Thank you for your time! ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.0+14.04.20140403-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-23.45-generic 3.13.8 Uname: Linux 3.13.0-23-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Mon Apr 7 17:41:39 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Toshiba America Info Systems Device [1179:0009] InstallationDate: Installed on 2014-04-01 (6 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Daily amd64 (20140330) MachineType: TOSHIBA PORTEGE Z835 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-23-generic root=UUID=5d7f7158-1b5b-4946-9916-b8a0c2f59525 ro quiet splash vt.handoff=7 SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/08/2012 dmi.bios.vendor: TOSHIBA dmi.bios.version: Version 1.60 dmi.board.asset.tag: 00 dmi.board.name: Portable PC dmi.board.vendor: TOSHIBA dmi.board.version: Version A0 dmi.chassis.asset.tag: 00 dmi.chassis.type: 10 dmi.chassis.vendor: TOSHIBA dmi.chassis.version: Version 1.0 dmi.modalias: dmi:bvnTOSHIBA:bvrVersion1.60:bd02/08/2012:svnTOSHIBA:pnPORTEGEZ835:pvrPT224U-013021:rvnTOSHIBA:rnPortablePC:rvrVersionA0:cvnTOSHIBA:ct10:cvrVersion1.0: dmi.product.name: PORTEGE Z835 dmi.product.version: PT224U-013021 dmi.sys.vendor: TOSHIBA version.compiz: compiz 1:0.9.11+14.04.20140328-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-4ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-4ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.15.0-1ubuntu7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Mon Apr 7 17:24:40 2014 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.15.0-1ubuntu7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1304073/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe :
Re: [Dx-packages] [Bug 1303712] Re: [FFe] Remove gnome screensaver with unity installation
Bug #1304111 is for what is needed for the unity lock screen. accessibility wise. I initially looked at this, and decided post feature freeze that introducing so much new code was too risky and could introduce more bugs, hense patching gnome-screensaver to use the original lock screen when the screen reader is in use. -- 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/1303712 Title: [FFe] Remove gnome screensaver with unity installation Status in Unity: New Status in “unity” package in Ubuntu: New Bug description: Unity is now handling the gnome screensaver dbus API completely, so we can get rid g-s from default ubuntu installation. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1303712/+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 1301607] Re: Ambiance Combo box - black highlighted text and scroll arrows
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: unity (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1301607 Title: Ambiance Combo box - black highlighted text and scroll arrows Status in One Hundred Papercuts: New Status in “unity” package in Ubuntu: Confirmed Bug description: To reproduce: Open files Right-click on any file or folder and select properties On permissions, open any combobox The highlighted item has black text over orange background, but I'm pretty sure should be white over orange. Also, scroll arrows (when the box reaches the top or bottom of the screen) are black over dark gray, barely visibles. I'm pretty sure this is not by design, and also could be an usability issue due to the lack of contrast. Screenshot attached. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.1.2+14.04.20140321-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-19.40-generic 3.13.6 Uname: Linux 3.13.0-19-generic i686 ApportVersion: 2.13.3-0ubuntu1 Architecture: i386 CasperVersion: 1.339 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Wed Apr 2 20:33:10 2014 LiveMediaBuild: Ubuntu 14.04 LTS Trusty Tahr - Beta i386 (20140326) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1301607/+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 1301607] Re: Ambiance Combo box - black highlighted text and scroll arrows
I can confirm this see screenshot! we need to fix before release, I am looking for a fix as well... This is a real issue with theme, I am not sure if they had to do this becuase it breaks something else otherwise but please show it Andrew Cimi and Makers of the GTK Theme. Any Dropdown box in GTK 3 , File Type, Options , Has Black text in the drop down menu See Picture. ** Attachment added: Picture of the described bug https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1301607/+attachment/4073517/+files/Screenshot%20from%202014-04-07%2019%3A55%3A17.png -- 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/1301607 Title: Ambiance Combo box - black highlighted text and scroll arrows Status in One Hundred Papercuts: New Status in “unity” package in Ubuntu: Confirmed Bug description: To reproduce: Open files Right-click on any file or folder and select properties On permissions, open any combobox The highlighted item has black text over orange background, but I'm pretty sure should be white over orange. Also, scroll arrows (when the box reaches the top or bottom of the screen) are black over dark gray, barely visibles. I'm pretty sure this is not by design, and also could be an usability issue due to the lack of contrast. Screenshot attached. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.1.2+14.04.20140321-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-19.40-generic 3.13.6 Uname: Linux 3.13.0-19-generic i686 ApportVersion: 2.13.3-0ubuntu1 Architecture: i386 CasperVersion: 1.339 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Wed Apr 2 20:33:10 2014 LiveMediaBuild: Ubuntu 14.04 LTS Trusty Tahr - Beta i386 (20140326) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1301607/+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 1303712] Re: [FFe] Remove gnome screensaver with unity installation
I think that could have been done by trying to fix unity first, by the way in terms of screen readers the unity lockscreen seems to tell more here than gs. As per this workaround, it can be done also unity side: by falling back to GS if a11y options are on, and this is what lp:~3v1n0/unity /lockscreen-disable-with-osk does. So, we can still have both things, but making unity to control what's best to do. -- 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/1303712 Title: [FFe] Remove gnome screensaver with unity installation Status in Unity: New Status in “unity” package in Ubuntu: New Bug description: Unity is now handling the gnome screensaver dbus API completely, so we can get rid g-s from default ubuntu installation. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1303712/+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 1303712] Re: Gnome screensaver should not run automatically in an unity session
** Summary changed: - [FFe] Remove gnome screensaver with unity installation + Gnome screensaver should not run automatically in an unity session ** Description changed: Unity is now handling the gnome screensaver dbus API completely, so we - can get rid g-s from default ubuntu installation. + don't need anymore to run GS in an unity session. ** Also affects: gnome-screensaver (Ubuntu) Importance: Undecided Status: New ** Changed in: gnome-screensaver (Ubuntu) Status: New = In Progress ** Changed in: gnome-screensaver (Ubuntu) Assignee: (unassigned) = Marco Trevisan (Treviño) (3v1n0) ** Changed in: unity (Ubuntu) Status: New = In Progress ** Changed in: unity Status: New = In Progress ** Changed in: unity Milestone: None = 7.2.1 ** Branch linked: lp:~3v1n0/gnome-screensaver/not-autostart-in-unity -- 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/1303712 Title: Gnome screensaver should not run automatically in an unity session Status in Unity: In Progress Status in “gnome-screensaver” package in Ubuntu: In Progress Status in “unity” package in Ubuntu: In Progress Bug description: Unity is now handling the gnome screensaver dbus API completely, so we don't need anymore to run GS in an unity session. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1303712/+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 1304171] Re: compiz crashed with SIGABRT in __gnu_cxx::__verbose_terminate_handler()
*** This bug is a duplicate of bug 1300219 *** https://bugs.launchpad.net/bugs/1300219 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 #1300219, 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/1304171/+attachment/4073674/+files/CoreDump.gz ** Attachment removed: Disassembly.txt https://bugs.launchpad.net/bugs/1304171/+attachment/4073676/+files/Disassembly.txt ** Attachment removed: ProcMaps.txt https://bugs.launchpad.net/bugs/1304171/+attachment/4073678/+files/ProcMaps.txt ** Attachment removed: ProcStatus.txt https://bugs.launchpad.net/bugs/1304171/+attachment/4073679/+files/ProcStatus.txt ** Attachment removed: Registers.txt https://bugs.launchpad.net/bugs/1304171/+attachment/4073680/+files/Registers.txt ** Attachment removed: Stacktrace.txt https://bugs.launchpad.net/bugs/1304171/+attachment/4073681/+files/Stacktrace.txt ** Attachment removed: ThreadStacktrace.txt https://bugs.launchpad.net/bugs/1304171/+attachment/4073682/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 1300219 ** Information type changed from Private to Public ** Tags removed: need-i386-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/1304171 Title: compiz crashed with SIGABRT in __gnu_cxx::__verbose_terminate_handler() Status in “unity” package in Ubuntu: New Bug description: Changed resolution VGA monitor ProblemType: Crash DistroRelease: Ubuntu 14.04 Package: unity 7.2.0+14.04.20140404-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-23.45-generic 3.13.8 Uname: Linux 3.13.0-23-generic i686 ApportVersion: 2.14.1-0ubuntu1 Architecture: i386 CurrentDesktop: Unity Date: Tue Apr 8 08:41:13 2014 ExecutablePath: /usr/bin/compiz InstallationDate: Installed on 2012-05-03 (704 days ago) InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release i386 (20120423) ProcCmdline: compiz Signal: 6 SourcePackage: unity StacktraceTop: __gnu_cxx::__verbose_terminate_handler() () from /usr/lib/i386-linux-gnu/libstdc++.so.6 ?? () from /usr/lib/i386-linux-gnu/libstdc++.so.6 std::terminate() () from /usr/lib/i386-linux-gnu/libstdc++.so.6 __cxa_throw () from /usr/lib/i386-linux-gnu/libstdc++.so.6 std::__throw_bad_function_call() () from /usr/lib/i386-linux-gnu/libstdc++.so.6 Title: compiz crashed with SIGABRT in __gnu_cxx::__verbose_terminate_handler() UpgradeStatus: Upgraded to trusty on 2013-12-23 (105 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1304171/+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 1304186] [NEW] 14.04 Unity integration with messaging applications not fully working.
Public bug reported: On the three 14.04 installs I've done, I've noticed this same situation come up. As seen in the screenshot below, when you receive an instant message you get a number on top of the messaging application in the Unity bar. This isn't the case in 14.04. http://www.omgubuntu.co.uk/wp- content/uploads/2011/04/screenshotae_thumb.png With both Pidgin and Empathy (using Google Talk), I do not receive the number on the icon to indicate how many new messages I have. With Empathy in particular I did notice that brand new conversations do list a 1 there, but once I engage in conversation and later background Empathy, new messages do not put a number on the icon to indicate that I have unread messages. In prior releases of Ubuntu, this seemed to always work. Thank you for your time! ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.0+14.04.20140404-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-23.45-generic 3.13.8 Uname: Linux 3.13.0-23-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Tue Apr 8 01:40:10 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:5000] InstallationDate: Installed on 2014-04-04 (3 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Daily amd64 (20140330) MachineType: LENOVO 3254CTO ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-23-generic root=UUID=58de4412-6390-4ffc-abeb-3d7978795c18 ro quiet splash vt.handoff=7 SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/15/2012 dmi.bios.vendor: LENOVO dmi.bios.version: H0ET32WW (1.14 ) dmi.board.asset.tag: Not Available dmi.board.name: 3254CTO dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrH0ET32WW(1.14):bd06/15/2012:svnLENOVO:pn3254CTO:pvrThinkPadEdgeE430:rvnLENOVO:rn3254CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 3254CTO dmi.product.version: ThinkPad Edge E430 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.11+14.04.20140404-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-4ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-4ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.15.0-1ubuntu7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Mon Apr 7 20:54:34 2014 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id5225 vendor CMN xserver.version: 2:1.15.0-1ubuntu7 ** Affects: unity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 trusty ubuntu -- 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/1304186 Title: 14.04 Unity integration with messaging applications not fully working. Status in “unity” package in Ubuntu: New Bug description: On the three 14.04 installs I've done, I've noticed this same situation come up. As seen in the screenshot below, when you receive an instant message you get a number on top of the messaging application in the Unity bar. This isn't the case in 14.04. http://www.omgubuntu.co.uk/wp- content/uploads/2011/04/screenshotae_thumb.png With both Pidgin and Empathy (using Google Talk), I do not receive the number on the icon to indicate how many new messages I have. With Empathy in particular I did notice that brand new conversations do list a 1 there, but once I engage in conversation and later background Empathy, new messages do not put a number on the icon to indicate that I have unread messages. In prior releases of Ubuntu, this seemed to always work. Thank you for your time! ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.0+14.04.20140404-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-23.45-generic 3.13.8 Uname: Linux 3.13.0-23-generic x86_64
