[Dx-packages] [Bug 798102] Re: compiz crashed with signal 5 in g_type_create_instance()
Apparently the same bug (at least, the same error message), but with Ubuntu 14.10. -- You received this bug notification because you are a member of DX Packages, which is subscribed to nux in Ubuntu. Matching subscriptions: dx-packages, dx-packages https://bugs.launchpad.net/bugs/798102 Title: compiz crashed with signal 5 in g_type_create_instance() Status in Nux: Fix Released Status in Unity: Fix Released Status in Unity Foundations: Fix Released Status in “nux” package in Ubuntu: Fix Released Status in “unity” package in Ubuntu: Fix Released Bug description: This happened while I was testing the oneiric daily live-cd. ProblemType: Crash DistroRelease: Ubuntu 11.10 Package: libnux-0.9-0 0.9.48-0ubuntu4 ProcVersionSignature: Ubuntu 3.0-0.1-generic 3.0.0-rc2 Uname: Linux 3.0-0-generic i686 Architecture: i386 CrashCounter: 1 Date: Thu Jun 16 09:30:39 2011 ExecutablePath: /usr/bin/compiz LiveMediaBuild: Ubuntu 11.10 Oneiric Ocelot - Alpha i386 (20110615) ProcCmdline: compiz --replace ProcEnviron: PATH=(custom, no user) LANG=ru_RU.UTF-8 SHELL=/bin/bash Signal: 5 SourcePackage: nux StacktraceTop: ?? () from /usr/lib/i386-linux-gnu/libbamf.so.0 g_type_create_instance () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0 ?? () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0 g_object_newv () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0 g_object_new () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0 Title: compiz crashed with signal 5 in g_type_create_instance() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare To manage notifications about this bug go to: https://bugs.launchpad.net/nux/+bug/798102/+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 1378821] Re: today/yesterday label on sms and calls is incorrect
** Changed in: indicator-messages (Ubuntu) Importance: Undecided = High -- 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/1378821 Title: today/yesterday label on sms and calls is incorrect Status in “indicator-messages” package in Ubuntu: New Bug description: rtm image on krillin, build 88 I'm in timzone UTC -4 If I have a missed call or sms that shows up in the indicator, it will sometimes incorrect be displayed as Yesterday time even though it happened today. This happens if the missed call is anytime after 8pm local time. I believe it's because the determination for that label is using UTC time rather than converting to the local timezone. It should be changed to use local time zone. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-messages/+bug/1378821/+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 1332947] Re: HDPI: unity randomly turns on large text in universal access
I get this behaviour almost every time Unity crashes for some reason - or I manually kill gnome-session. It does not happen on re-boot for me. (Although it did do that a couple of months 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/1332947 Title: HDPI: unity randomly turns on large text in universal access Status in OEM Priority Project: In Progress Status in OEM Priority Project trusty series: New Status in Unity: Fix Committed Status in Unity 7.2 series: In Progress Status in “unity” package in Ubuntu: Fix Released Status in “unity” source package in Trusty: In Progress Bug description: I have a macbook pro with retina display. In Ubuntu 14.04 64bit, every couple of reboots, the 'large text' option in Universal Access gets switched on upon login. It happens in roughly 1 out of 5 reboots for 1 or more users on the computer. It appears to happen to people with small HighDPI screens. In my case, it's 13 inch at 2560x1600. Another example is 13 inch at 1080p - http://askubuntu.com/questions/453785/large-text-button-in-universal-access-turns-itself-on-after-reboot-ubuntu-14-0 unity: Installed: 7.2.1+14.04.20140513-0ubuntu2 Candidate: 7.2.1+14.04.20140513-0ubuntu2 Version table: *** 7.2.1+14.04.20140513-0ubuntu2 0 500 http://sk.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages 100 /var/lib/dpkg/status 7.2.0+14.04.20140423-0ubuntu1.2 0 500 http://security.ubuntu.com/ubuntu/ trusty-security/main amd64 Packages 7.2.0+14.04.20140416-0ubuntu1 0 500 http://sk.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages unity-control-center: Installed: 14.04.3+14.04.20140410-0ubuntu1 Candidate: 14.04.3+14.04.20140410-0ubuntu1 Version table: *** 14.04.3+14.04.20140410-0ubuntu1 0 500 http://sk.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages 100 /var/lib/dpkg/status intel iris pro graphics (lspci -vvv): 00:02.0 VGA compatible controller: Intel Corporation Device 0a2e (rev 09) (prog-if 00 [VGA controller]) Subsystem: Apple Inc. Device 011a Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast TAbort- TAbort- MAbort- SERR- PERR- INTx- Latency: 0 Interrupt: pin A routed to IRQ 66 Region 0: Memory at b000 (64-bit, non-prefetchable) [size=4M] Region 2: Memory at a000 (64-bit, prefetchable) [size=256M] Region 4: I/O ports at 1000 [size=64] Expansion ROM at unassigned [disabled] Capabilities: [90] MSI: Enable+ Count=1/1 Maskable- 64bit- Address: fee00018 Data: Capabilities: [d0] Power Management version 2 Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-) Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME- Capabilities: [a4] PCI Advanced Features AFCap: TP+ FLR+ AFCtrl: FLR- AFStatus: TP- Kernel driver in use: i915 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1332947/+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 1372061] Re: SMS notification: time format not translatable
** Also affects: unity8 (Ubuntu) Importance: Undecided Status: New -- 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/1372061 Title: SMS notification: time format not translatable Status in Ubuntu Translations: Triaged Status in “indicator-messages” package in Ubuntu: New Status in “telephony-service” package in Ubuntu: New Status in “unity8” package in Ubuntu: New Bug description: See the attached screenshot. The time for the notification seems to be hardcoded to hh:mm - mm, d. This works well for the US, but it's not a format that is used in all other countries. In Spain, for example, the date would rather be d mm. The time format needs to be marked for translation. Not sure from which project the notifications come from, for some reason I seem to remember they were moved to u-s-s, but if it's the wrong project/package, please reassign. Thanks! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-translations/+bug/1372061/+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 1324114] Re: Unity kills running compiz, even if it belongs to a different Unity session
Could somebody help verifying the fix so that version can move to utopic-updates? -- 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/1324114 Title: Unity kills running compiz, even if it belongs to a different Unity session Status in Unity: Fix Committed Status in Unity 7.2 series: In Progress Status in “unity” package in Ubuntu: Fix Released Status in “unity” source package in Trusty: Fix Committed Bug description: I'm trying to get a setup with two different Unity desktop sessions running at the same time. One for the local desktop, one for a remote desktop. This almost works, except that when starting the second Unity session, the compiz process that belongs to the first one is killed because of this code in /usr/bin/unity: # kill a previous compiz if was there (this is a hack as compiz can # sometimes get stuck and not exit on --replace) subprocess.call ([pkill, -9, compiz]) Commenting this line makes both desktop sessions work fine. This kill is far too harsh. If you want to kill compiz, you should make sure that you are killing it in the same DISPLAY as the session that you are about to start, and not just every possible compiz process that is running. Please consider either removing the kill or making it apply only to processes in the same DISPLAY. [Impact] Running unity script will kill the unity processes in different displays [Test case] - Run unity in DISPLAY=:0 and in DISPLAY=:1 - Launch the unity script in DISPLAY=:1, it should kill and restart only the unity instance running in DISPLAY=:1 To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1324114/+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 1347735] Re: Lockscreen capslock detection doesn't work well with remapped capslocks
Could somebody help verifying the fix so that version can move to
utopic-updates?
--
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/1347735
Title:
Lockscreen capslock detection doesn't work well with remapped
capslocks
Status in Unity:
Fix Committed
Status in Unity 7.2 series:
In Progress
Status in “unity” package in Ubuntu:
Fix Released
Status in “unity” source package in Trusty:
Fix Committed
Bug description:
[Impact]
Remapped keys to activate the caps-lock are not correctly detected by the
unity lockscreen
[Test case]
1. Configure the keyboard so that Both shifts together toggles CapsLock
2. Lock the screen using Super+L or menus
3. Press both shifts together to turn the capslock on
4. The lockscreen input field should show a warning
5. Press the shifts again, and the warning should be hidden
[Regression potential]
None
-
Version: 7.2.2+14.04.20140714-0ubuntu1 (trusty)
Some users like to remap the way the activate capslock. For example,
using gnome-tweak-tool it's possible to set the CapsLock key to behave
as an extra Ctrl, or an extra Alt (or several other extras) and then
set Both shifts together toggle CapsLock.
This works perfectly well inside Unity, the hardware keyboard led
indicator shows up, etc. However, the lockscreen detector doesn't
correctly warn or not warn when this setup is used.
* If the lockscreen was activated with capslock on, then the double-shift
makes capslock go away, but not the warning.
* If the lockscreen was activated with capslock off, then the double-shift
makes capslock on, but no warning shows up.
I believe the problem is in this piece of code in unity-
shared/TextInput.cpp:
void TextInput::OnKeyUp(unsigned keysym,
unsigned long keycode,
unsigned long state)
{
if (!caps_lock_on keysym == NUX_VK_CAPITAL)
caps_lock_on = true;
else if (caps_lock_on keysym == NUX_VK_CAPITAL)
caps_lock_on = false;
}
This is checking for specific key, instead of the fact that CapsLock
was activated or not.
To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1347735/+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 1378821] Re: today/yesterday label on sms and calls is incorrect
** Also affects: unity8 (Ubuntu) Importance: Undecided Status: New ** Changed in: unity8 (Ubuntu) Importance: Undecided = High -- 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/1378821 Title: today/yesterday label on sms and calls is incorrect Status in “indicator-messages” package in Ubuntu: New Status in “unity8” package in Ubuntu: New Bug description: rtm image on krillin, build 88 I'm in timzone UTC -4 If I have a missed call or sms that shows up in the indicator, it will sometimes incorrect be displayed as Yesterday time even though it happened today. This happens if the missed call is anytime after 8pm local time. I believe it's because the determination for that label is using UTC time rather than converting to the local timezone. It should be changed to use local time zone. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-messages/+bug/1378821/+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 1373404] Re: No warning of high volume level
** Also affects: unity8 (Ubuntu RTM) Importance: Undecided Status: New ** Changed in: unity8 (Ubuntu RTM) Status: New = In Progress ** Changed in: unity8 (Ubuntu RTM) Assignee: (unassigned) = Mirco Müller (macslow) ** Also affects: unity-notifications (Ubuntu) Importance: Undecided Status: New ** Changed in: unity-notifications (Ubuntu) Status: New = In Progress ** Changed in: unity-notifications (Ubuntu) Assignee: (unassigned) = Mirco Müller (macslow) ** Also affects: unity-notifications (Ubuntu RTM) Importance: Undecided Status: New ** Changed in: unity-notifications (Ubuntu RTM) Status: New = In Progress ** Changed in: unity-notifications (Ubuntu RTM) Assignee: (unassigned) = Mirco Müller (macslow) -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-sound in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1373404 Title: No warning of high volume level Status in Sound Menu: Triaged Status in Ubuntu UX bugs: Fix Committed Status in “indicator-sound” package in Ubuntu: Triaged Status in “pulseaudio” package in Ubuntu: Invalid Status in “ubuntu-system-settings” package in Ubuntu: Invalid Status in “unity-notifications” package in Ubuntu: In Progress Status in “unity8” package in Ubuntu: In Progress Status in “unity-notifications” package in Ubuntu RTM: In Progress Status in “unity8” package in Ubuntu RTM: In Progress Bug description: The EU has a legal requirement for personal music players to prevent hearing damage. http://eur-lex.europa.eu/legal-content/EN/TXT/HTML/?uri=CELEX:32009D0490rid=1 Desired resolution: - For RTM the design spec'ed in the following section of the Sound wiki page should be implemented https://wiki.ubuntu.com/Sound#Warnings_.28note:_This_section_should_be_implemented_for_RTM.29 To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-sound/+bug/1373404/+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 1241101] Re: Java crash in libglib-2.0 after upgrade from 13.04 to 13.10
This bug in GTK causes Eclipse to crash *constantly* (several times per day) on Ubuntu 14.04. I've attached an error log that gets left behind after the crash. The incriminating frame is: C [libglib-2.0.so.0+0x38fe0] g_str_hash+0x0 I really hope this gets fixed! Stability bugs are the worst. ** Attachment added: Example crash log showing GTK crashing Eclipse https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1241101/+attachment/4234122/+files/hs_err_pid12077.log -- 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/1241101 Title: Java crash in libglib-2.0 after upgrade from 13.04 to 13.10 Status in Eclipse: Confirmed Status in “gtk+2.0” package in Ubuntu: Triaged Status in “unity” package in Ubuntu: Invalid Status in “gtk+2.0” package in Suse: New Bug description: Running smartgit 4.6.4 on 13.10 64 bits. After registering the product, smartgit crash when trying to open a new repository. Java error log : # A fatal error has been detected by the Java Runtime Environment: # # SIGSEGV (0xb) at pc=0x7fa59061f9c0, pid=12494, tid=140349308167936 # # JRE version: 7.0_25-b30 # Java VM: OpenJDK 64-Bit Server VM (23.7-b01 mixed mode linux-amd64 compressed oops) # Problematic frame: # C [libglib-2.0.so.0+0x389c0] g_str_hash+0x0 I tried different version of Java (Oracle v7 and v6 jre) with same result. Also, Eclipse display blank menus so there's a general java problem with displays. To manage notifications about this bug go to: https://bugs.launchpad.net/eclipse/+bug/1241101/+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 1241101]
Created attachment 247831 Additional crash log Eclipse 4.3.2 crashes *constantly* (several times per day) with this problem on Ubuntu 14.04. The UI goes grey and unresponsive, and after force-quitting the application I get an error log with a stack trace about a seg fault in native code invoked from org.eclipse.swt.internal.gtk.OS._gtk_widget_show(). I've heard rumors that GTK on Ubuntu is not entirely sound. Eclipse may actually be a victim here rather than the culprit. -- 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/1241101 Title: Java crash in libglib-2.0 after upgrade from 13.04 to 13.10 Status in Eclipse: Confirmed Status in “gtk+2.0” package in Ubuntu: Triaged Status in “unity” package in Ubuntu: Invalid Status in “gtk+2.0” package in Suse: New Bug description: Running smartgit 4.6.4 on 13.10 64 bits. After registering the product, smartgit crash when trying to open a new repository. Java error log : # A fatal error has been detected by the Java Runtime Environment: # # SIGSEGV (0xb) at pc=0x7fa59061f9c0, pid=12494, tid=140349308167936 # # JRE version: 7.0_25-b30 # Java VM: OpenJDK 64-Bit Server VM (23.7-b01 mixed mode linux-amd64 compressed oops) # Problematic frame: # C [libglib-2.0.so.0+0x389c0] g_str_hash+0x0 I tried different version of Java (Oracle v7 and v6 jre) with same result. Also, Eclipse display blank menus so there's a general java problem with displays. To manage notifications about this bug go to: https://bugs.launchpad.net/eclipse/+bug/1241101/+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
Re: [Dx-packages] [Bug 1241101] Re: Java crash in libglib-2.0 after upgrade from 13.04 to 13.10
-- 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/1241101 Title: Java crash in libglib-2.0 after upgrade from 13.04 to 13.10 Status in Eclipse: Confirmed Status in “gtk+2.0” package in Ubuntu: Triaged Status in “unity” package in Ubuntu: Invalid Status in “gtk+2.0” package in Suse: New Bug description: Running smartgit 4.6.4 on 13.10 64 bits. After registering the product, smartgit crash when trying to open a new repository. Java error log : # A fatal error has been detected by the Java Runtime Environment: # # SIGSEGV (0xb) at pc=0x7fa59061f9c0, pid=12494, tid=140349308167936 # # JRE version: 7.0_25-b30 # Java VM: OpenJDK 64-Bit Server VM (23.7-b01 mixed mode linux-amd64 compressed oops) # Problematic frame: # C [libglib-2.0.so.0+0x389c0] g_str_hash+0x0 I tried different version of Java (Oracle v7 and v6 jre) with same result. Also, Eclipse display blank menus so there's a general java problem with displays. To manage notifications about this bug go to: https://bugs.launchpad.net/eclipse/+bug/1241101/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1379152] Re: Needs building dependency on libmtdev-dev (or making QPlatformSupport public)
** Description changed: Because of packaging changes in Qt Base in Qt 5.3.2, packages using qplatformsupport from private headers will need to add an additional dependency to compile against it. From Debian bug report: --- - This comes from QPlatformSupport stuff which creates a static library that - needs this linking. + This comes from QPlatformSupport stuff which creates a static library that needs this linking. - It also happens that QPlatformSupport is private stuff, so there is really no - way to solve this but either stop using private stuff or helping upstream to - make QPlatformSupport public (which would be really helpful). This will in - turn mean that it will become a dynamic lib and this bug can be fixed. + It also happens that QPlatformSupport is private stuff, so there is really no way to solve this but either stop using private stuff or helping upstream to make QPlatformSupport public (which would be really helpful). This will in turn mean that it will become a dynamic lib and this bug can be fixed. --- So: A) someone works in qtbase upstream to make the QPlatformSupport public, or B) workaround with adding libmtdev-dev build dependencies This bug refers more to the B) option to get Qt 5.3.2 packages move forward. -- You received this bug notification because you are a member of DX Packages, which is subscribed to appmenu-qt5 in Ubuntu. https://bugs.launchpad.net/bugs/1379152 Title: Needs building dependency on libmtdev-dev (or making QPlatformSupport public) Status in Application menu for Qt5: New Status in Qt integration with the Mir display server: New Status in QT Ubuntu: New Status in “appmenu-qt5” package in Ubuntu: New Status in “maliit-framework” package in Ubuntu: New Status in “qtmir” package in Ubuntu: New Status in “qtubuntu” package in Ubuntu: New Status in Debian GNU/Linux: Won't Fix Bug description: Because of packaging changes in Qt Base in Qt 5.3.2, packages using qplatformsupport from private headers will need to add an additional dependency to compile against it. From Debian bug report: --- This comes from QPlatformSupport stuff which creates a static library that needs this linking. It also happens that QPlatformSupport is private stuff, so there is really no way to solve this but either stop using private stuff or helping upstream to make QPlatformSupport public (which would be really helpful). This will in turn mean that it will become a dynamic lib and this bug can be fixed. --- So: A) someone works in qtbase upstream to make the QPlatformSupport public, or B) workaround with adding libmtdev-dev build dependencies This bug refers more to the B) option to get Qt 5.3.2 packages move forward. To manage notifications about this bug go to: https://bugs.launchpad.net/appmenu-qt5/+bug/1379152/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 815996] Re: Desktop occasionally freezes/locks up when switching workspaces
** Also affects: compiz (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of DX Packages, which is subscribed to compiz-plugins-main in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/815996 Title: Desktop occasionally freezes/locks up when switching workspaces Status in Compiz: Confirmed Status in Compiz Main Plugins: Confirmed Status in Compiz Desktop Wall Plugin: Confirmed Status in “compiz” package in Ubuntu: New Status in “compiz-plugins-main” package in Ubuntu: Confirmed Bug description: I'm assuming the issue is related to Compiz, but I'm not 100% sure. When I'm switching workspaces, it occasionally locks up (becoming more frequent). Most of the time, I'm going from the current one down (Ctrl+Alt+Down Arrow), and it freezes mid slide. Typically, I'm able to correct things by backing out to a terminal then returning (Ctrl+Alt+F1, pause, Alt+F7), but sometimes when I return the dual screen setup acts as one large screen (windows are stretched to the full width of both screens) and many of the windows collect on the first workspace. Ubuntu 11.04 (Classic) All packages up-to-date. If there are any logs/etc that would be helpful, let me know. --- Architecture: amd64 CompizPlugins: [core,bailer,detection,composite,opengl,decor,grid,imgpng,snap,compiztoolbox,resize,place,regex,move,gnomecompat,animation,vpswitch,mousepoll,workarounds,session,expo,wall,ezoom,fade,switcher,scale] DistroCodename: natty DistroRelease: Ubuntu 11.04 DistroVariant: ubuntu InstallationMedia: Ubuntu 10.04 LTS Lucid Lynx - Release amd64 (20100429) InstallationMedia_: Ubuntu 10.04 LTS Lucid Lynx - Release amd64 (20100429) NonfreeKernelModules: nvidia Package: compiz 1:0.9.4+bzr20110606-0ubuntu1~natty2 PackageArchitecture: all ProcEnviron: LANGUAGE=en_US:en PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.38-10.46-generic 2.6.38.7 ProcVersionSignature_: Ubuntu 2.6.38-10.46-generic 2.6.38.7 Tags: natty natty ubuntu Uname: Linux 2.6.38-10-generic x86_64 UnreportableReason: Please work this issue through technical support channels first. UpgradeStatus: Upgraded to natty on 2011-05-02 (84 days ago) UserGroups: adm admin audio cdrom dialout dip fuse lpadmin netdev plugdev sambashare To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/815996/+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 1373404] Re: No warning of high volume level
** Changed in: indicator-sound (Ubuntu) Status: Triaged = In Progress ** Changed in: indicator-sound Status: Triaged = In Progress -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-sound in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1373404 Title: No warning of high volume level Status in Sound Menu: In Progress Status in Ubuntu UX bugs: Fix Committed Status in “indicator-sound” package in Ubuntu: In Progress Status in “pulseaudio” package in Ubuntu: Invalid Status in “ubuntu-system-settings” package in Ubuntu: Invalid Status in “unity-notifications” package in Ubuntu: In Progress Status in “unity8” package in Ubuntu: In Progress Status in “unity-notifications” package in Ubuntu RTM: In Progress Status in “unity8” package in Ubuntu RTM: In Progress Bug description: The EU has a legal requirement for personal music players to prevent hearing damage. http://eur-lex.europa.eu/legal-content/EN/TXT/HTML/?uri=CELEX:32009D0490rid=1 Desired resolution: - For RTM the design spec'ed in the following section of the Sound wiki page should be implemented https://wiki.ubuntu.com/Sound#Warnings_.28note:_This_section_should_be_implemented_for_RTM.29 To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-sound/+bug/1373404/+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 1373404] Re: No warning of high volume level
** Branch linked: lp:~ted/indicator-sound/extreme-volume-warning -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-sound in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1373404 Title: No warning of high volume level Status in Sound Menu: In Progress Status in Ubuntu UX bugs: Fix Committed Status in “indicator-sound” package in Ubuntu: In Progress Status in “pulseaudio” package in Ubuntu: Invalid Status in “ubuntu-system-settings” package in Ubuntu: Invalid Status in “unity-notifications” package in Ubuntu: In Progress Status in “unity8” package in Ubuntu: In Progress Status in “unity-notifications” package in Ubuntu RTM: In Progress Status in “unity8” package in Ubuntu RTM: In Progress Bug description: The EU has a legal requirement for personal music players to prevent hearing damage. http://eur-lex.europa.eu/legal-content/EN/TXT/HTML/?uri=CELEX:32009D0490rid=1 Desired resolution: - For RTM the design spec'ed in the following section of the Sound wiki page should be implemented https://wiki.ubuntu.com/Sound#Warnings_.28note:_This_section_should_be_implemented_for_RTM.29 To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-sound/+bug/1373404/+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 1378821] Re: today/yesterday label on sms and calls is incorrect
** Changed in: indicator-messages (Ubuntu) Assignee: (unassigned) = Nick Dedekind (nick-dedekind) ** Changed in: unity8 (Ubuntu) Assignee: (unassigned) = Nick Dedekind (nick-dedekind) ** Changed in: indicator-messages (Ubuntu) Status: New = Invalid -- 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/1378821 Title: today/yesterday label on sms and calls is incorrect Status in “indicator-messages” package in Ubuntu: Invalid Status in “unity8” package in Ubuntu: New Bug description: rtm image on krillin, build 88 I'm in timzone UTC -4 If I have a missed call or sms that shows up in the indicator, it will sometimes incorrect be displayed as Yesterday time even though it happened today. This happens if the missed call is anytime after 8pm local time. I believe it's because the determination for that label is using UTC time rather than converting to the local timezone. It should be changed to use local time zone. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-messages/+bug/1378821/+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 1372061] Re: SMS notification: time format not translatable
** No longer affects: indicator-messages (Ubuntu) ** Changed in: unity8 (Ubuntu) Assignee: (unassigned) = Nick Dedekind (nick-dedekind) -- 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/1372061 Title: SMS notification: time format not translatable Status in Ubuntu Translations: Triaged Status in “telephony-service” package in Ubuntu: New Status in “unity8” package in Ubuntu: New Bug description: See the attached screenshot. The time for the notification seems to be hardcoded to hh:mm - mm, d. This works well for the US, but it's not a format that is used in all other countries. In Spain, for example, the date would rather be d mm. The time format needs to be marked for translation. Not sure from which project the notifications come from, for some reason I seem to remember they were moved to u-s-s, but if it's the wrong project/package, please reassign. Thanks! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-translations/+bug/1372061/+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 1373404] Re: No warning of high volume level
** Branch linked: lp:~macslow/unity-settings-daemon/max-volume- notification-warning -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-sound in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1373404 Title: No warning of high volume level Status in Sound Menu: In Progress Status in Ubuntu UX bugs: Fix Committed Status in “indicator-sound” package in Ubuntu: In Progress Status in “pulseaudio” package in Ubuntu: Invalid Status in “ubuntu-system-settings” package in Ubuntu: Invalid Status in “unity-notifications” package in Ubuntu: In Progress Status in “unity8” package in Ubuntu: In Progress Status in “unity-notifications” package in Ubuntu RTM: In Progress Status in “unity8” package in Ubuntu RTM: In Progress Bug description: The EU has a legal requirement for personal music players to prevent hearing damage. http://eur-lex.europa.eu/legal-content/EN/TXT/HTML/?uri=CELEX:32009D0490rid=1 Desired resolution: - For RTM the design spec'ed in the following section of the Sound wiki page should be implemented https://wiki.ubuntu.com/Sound#Warnings_.28note:_This_section_should_be_implemented_for_RTM.29 To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-sound/+bug/1373404/+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 1380739] Re: unity-scope-loader crashed with SIGSEGV in g_file_monitor_emit_event()
*** This bug is a duplicate of bug 1358815 *** https://bugs.launchpad.net/bugs/1358815 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 #1358815, 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/1380739/+attachment/4234702/+files/CoreDump.gz ** Attachment removed: Disassembly.txt https://bugs.launchpad.net/bugs/1380739/+attachment/4234704/+files/Disassembly.txt ** Attachment removed: ProcMaps.txt https://bugs.launchpad.net/bugs/1380739/+attachment/4234706/+files/ProcMaps.txt ** Attachment removed: ProcStatus.txt https://bugs.launchpad.net/bugs/1380739/+attachment/4234707/+files/ProcStatus.txt ** Attachment removed: Registers.txt https://bugs.launchpad.net/bugs/1380739/+attachment/4234708/+files/Registers.txt ** Attachment removed: Stacktrace.txt https://bugs.launchpad.net/bugs/1380739/+attachment/4234709/+files/Stacktrace.txt ** Attachment removed: ThreadStacktrace.txt https://bugs.launchpad.net/bugs/1380739/+attachment/4234710/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 1358815 ** 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 libunity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1380739 Title: unity-scope-loader crashed with SIGSEGV in g_file_monitor_emit_event() Status in “libunity” package in Ubuntu: New Bug description: ... ProblemType: Crash DistroRelease: Ubuntu 14.10 Package: libunity9 7.1.4+14.10.20140808-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-22.29-generic 3.16.4 Uname: Linux 3.16.0-22-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.14.7-0ubuntu5 Architecture: amd64 CurrentDesktop: Unity Date: Mon Oct 13 21:38:51 2014 ExecutablePath: /usr/bin/unity-scope-loader InstallationDate: Installed on 2014-09-18 (24 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Alpha amd64 (20140918) ProcCmdline: /usr/bin/unity-scope-loader applications/applications.scope applications/scopes.scope commands.scope SegvAnalysis: Segfault happened at: 0x7fe64616f0f4:mov(%rdi),%rdi PC (0x7fe64616f0f4) ok source (%rdi) (0x) not located in a known VMA region (needed readable region)! destination %rdi ok Stack memory exhausted (SP below stack segment) SegvReason: reading NULL VMA Signal: 11 SourcePackage: libunity StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 g_file_monitor_emit_event () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 Title: unity-scope-loader crashed with SIGSEGV in g_file_monitor_emit_event() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm bumblebee cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libunity/+bug/1380739/+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 1380320] Re: [REGRESSION] touchpad behavior broken: left button press delayed if finger is on touchpad
For god's sake, the impact of this is huge. Because of this bugs I have moved messages in Thunderbird from a random folder to another, which is equivalent to loosing them (impossible to figure out what I moved where), moved entire folders; the same with files in Nautilus. I have devastated Android Studio projects. All because a mouse press even is registered at a random point in space and time (it actually follows a strict logic as described in the report, but that is unrelated with the real behavior of the hand on the touchpad). This is like having a cat walking on your keyboard. Well, actually it's worse; the probability of doing serious damages is higher. This needs urgen attention. -- 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/1380320 Title: [REGRESSION] touchpad behavior broken: left button press delayed if finger is on touchpad Status in “unity” package in Ubuntu: New Bug description: This is a REGRESSION. This used to work fine. I don't know when exactly it broke. Steps to reproduce: Test 1 and Test 2 should both behave the same as test 2, but test 1 gives nonsense and dangerous results. --Test 1-- - place finger 1 on the touchpad - move the finger around while keeping it in contact with the touchpad = the mouse cursor moves around as expected - with another finger 2, press the left button and hold it, while finger 1 is still on the touchpad, at point A - (*) move finger 1 around on the touchpad to some other point B, then stop moving it - move finger 1 around again, to point C - only then, release the left button -- Test 2 -- - place finger 1 on the touchpad - move the finger around as in test 1 - take finger 1 away from the touchpad, leaving the cursor at point A - with another finger 2, press the left button and hold it - place finger 1 on the touchpad again and move it around, then stop at point B. - Move finger 1 a bit more, to point C - release the left button Expected result: OBVIOUSLY, in both cases, the behavior should be the same. A left button press should be registered at point A, then a drag movement to B and then C, and then a button release. If, for example, at point A you hit something draggable, the result is that you drag it and drop to point C Observed result: Test 2 behaves as expected However, in test 1, nothing happens when you actually press the button. Instead, a button press is registered when finger 1 pauses at point B. That is, everything behaves as if you had pressed the mouse button at a completely different place and time than you did. The result is dragging from point B to point C. The consequences can be disastrous. This can lead to data loss, because a click may be registered on a button that delete things, or the drag-and-move operation that is executed (completely unrelated to the real action of the user) may be that of moving an object to a place where you're not supposed to move it (e.g. moving a file to the trash or whatever). This can literally result in formatting your hard drive. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.2+14.04.20140714-0ubuntu1.1 ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7 Uname: Linux 3.13.0-37-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Sun Oct 12 17:17:03 2014 InstallationDate: Installed on 2013-10-11 (365 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2014-05-24 (140 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1380320/+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 1380320] Re: [REGRESSION] touchpad behavior broken: left button press delayed if finger is on touchpad
Oh, I forgot, among the disasters that happened to me because of this bug, I also accidentally sent emails that I hadn't finished writing. -- 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/1380320 Title: [REGRESSION] touchpad behavior broken: left button press delayed if finger is on touchpad Status in “unity” package in Ubuntu: New Bug description: This is a REGRESSION. This used to work fine. I don't know when exactly it broke. Steps to reproduce: Test 1 and Test 2 should both behave the same as test 2, but test 1 gives nonsense and dangerous results. --Test 1-- - place finger 1 on the touchpad - move the finger around while keeping it in contact with the touchpad = the mouse cursor moves around as expected - with another finger 2, press the left button and hold it, while finger 1 is still on the touchpad, at point A - (*) move finger 1 around on the touchpad to some other point B, then stop moving it - move finger 1 around again, to point C - only then, release the left button -- Test 2 -- - place finger 1 on the touchpad - move the finger around as in test 1 - take finger 1 away from the touchpad, leaving the cursor at point A - with another finger 2, press the left button and hold it - place finger 1 on the touchpad again and move it around, then stop at point B. - Move finger 1 a bit more, to point C - release the left button Expected result: OBVIOUSLY, in both cases, the behavior should be the same. A left button press should be registered at point A, then a drag movement to B and then C, and then a button release. If, for example, at point A you hit something draggable, the result is that you drag it and drop to point C Observed result: Test 2 behaves as expected However, in test 1, nothing happens when you actually press the button. Instead, a button press is registered when finger 1 pauses at point B. That is, everything behaves as if you had pressed the mouse button at a completely different place and time than you did. The result is dragging from point B to point C. The consequences can be disastrous. This can lead to data loss, because a click may be registered on a button that delete things, or the drag-and-move operation that is executed (completely unrelated to the real action of the user) may be that of moving an object to a place where you're not supposed to move it (e.g. moving a file to the trash or whatever). This can literally result in formatting your hard drive. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.2+14.04.20140714-0ubuntu1.1 ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7 Uname: Linux 3.13.0-37-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Sun Oct 12 17:17:03 2014 InstallationDate: Installed on 2013-10-11 (365 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2014-05-24 (140 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1380320/+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 1380320] Re: [REGRESSION] touchpad behavior broken: left button press delayed if finger is on touchpad
There seems to be also another (dangerous and annoying) glitch of which I can't find the exact pattern. Often I click with the touchpad button and TWO consecutive clicks are registered (not necessarily a double click). -- 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/1380320 Title: [REGRESSION] touchpad behavior broken: left button press delayed if finger is on touchpad Status in “unity” package in Ubuntu: New Bug description: This is a REGRESSION. This used to work fine. I don't know when exactly it broke. Steps to reproduce: Test 1 and Test 2 should both behave the same as test 2, but test 1 gives nonsense and dangerous results. --Test 1-- - place finger 1 on the touchpad - move the finger around while keeping it in contact with the touchpad = the mouse cursor moves around as expected - with another finger 2, press the left button and hold it, while finger 1 is still on the touchpad, at point A - (*) move finger 1 around on the touchpad to some other point B, then stop moving it - move finger 1 around again, to point C - only then, release the left button -- Test 2 -- - place finger 1 on the touchpad - move the finger around as in test 1 - take finger 1 away from the touchpad, leaving the cursor at point A - with another finger 2, press the left button and hold it - place finger 1 on the touchpad again and move it around, then stop at point B. - Move finger 1 a bit more, to point C - release the left button Expected result: OBVIOUSLY, in both cases, the behavior should be the same. A left button press should be registered at point A, then a drag movement to B and then C, and then a button release. If, for example, at point A you hit something draggable, the result is that you drag it and drop to point C Observed result: Test 2 behaves as expected However, in test 1, nothing happens when you actually press the button. Instead, a button press is registered when finger 1 pauses at point B. That is, everything behaves as if you had pressed the mouse button at a completely different place and time than you did. The result is dragging from point B to point C. The consequences can be disastrous. This can lead to data loss, because a click may be registered on a button that delete things, or the drag-and-move operation that is executed (completely unrelated to the real action of the user) may be that of moving an object to a place where you're not supposed to move it (e.g. moving a file to the trash or whatever). This can literally result in formatting your hard drive. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.2+14.04.20140714-0ubuntu1.1 ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7 Uname: Linux 3.13.0-37-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Sun Oct 12 17:17:03 2014 InstallationDate: Installed on 2013-10-11 (365 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2014-05-24 (140 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1380320/+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 1301623] Re: unity freezes when moving windows among workspaces
*** This bug is a duplicate of bug 815996 *** https://bugs.launchpad.net/bugs/815996 I can confirm that Unity gets stuck in Expo mode when I try to move a window from one screen to another (I have a dual monitor setup). I have 14.04 64bit on a desktop machine. Every time in last couple of years when I installed a new version of Ubuntu, I gave a chance to Unity to be my main desktop. Although I like how they imagined for it to work, it's the bugs like these that eventually, after a week or couple of weeks, made me switch to something else, less attractive but also less buggy (you can find my error reports for Unity since first versions of it as default desktop and see how long it took to fix some of these). When I start to swear at the computer for repeating things like this for n-th time, it's time to try something else again... -- 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/1301623 Title: unity freezes when moving windows among workspaces Status in Unity: Incomplete Status in “unity” package in Ubuntu: Incomplete Bug description: Sometimes In Ubuntu 14.04, when I move windows from one workspace to another, Unity freezes, letting me with this 4 workspaces overview. I have to use terminal and restart Unity to resolve it. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.1.2+14.04.20140328.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-18.32~precise1-generic 3.11.10.4 Uname: Linux 3.11.0-18-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell,dbus] CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Wed Apr 2 23:26:06 2014 DistUpgraded: 2014-03-18 07:46:56,695 DEBUG enabling apt cron job DistroCodename: trusty DistroVariant: ubuntu GraphicsCard: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller [8086:0152] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:365e] InstallationDate: Installed on 2014-02-10 (51 days ago) InstallationMedia: Ubuntu 12.04.4 LTS Precise Pangolin - Release amd64 (20140204) MachineType: LENOVO 10104 ProcEnviron: LANGUAGE=cs PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=cs_CZ.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-18-generic root=UUID=3a918684-e656-4e86-9b7b-22e0fd6b2135 ro quiet splash vt.handoff=7 SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2014-03-18 (15 days ago) dmi.bios.date: 03/21/2013 dmi.bios.vendor: LENOVO dmi.bios.version: ELKT31AUS dmi.board.name: MAHOBAY dmi.board.vendor: LENOVO dmi.board.version: 3193 STD dmi.chassis.type: 13 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnLENOVO:bvrELKT31AUS:bd03/21/2013:svnLENOVO:pn10104:pvrLenovoC440:rvnLENOVO:rnMAHOBAY:rvr3193STD:cvnToBeFilledByO.E.M.:ct13:cvrToBeFilledByO.E.M.: dmi.product.name: 10104 dmi.product.version: Lenovo C440 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.11+14.04.20140328-0ubuntu1 version.ia32-libs: ia32-libs 20090808ubuntu36 version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-1ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.15.0-1ubuntu7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Mon Mar 31 16:48:50 2014 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id8192 vendor LEN xserver.version: 2:1.15.0-1ubuntu7 To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1301623/+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
