[Touch-packages] [Bug 1149495] Re: Dash home application icon is different from app-lens icon
** Changed in: unity-asset-pool Milestone: None => 0.8.25 ** Also affects: unity-asset-pool/trusty Importance: Undecided Status: New ** Changed in: unity-asset-pool/trusty Importance: Undecided => Low ** Changed in: unity-asset-pool/trusty Status: New => Triaged ** Changed in: unity-asset-pool (Ubuntu) Importance: Undecided => Low -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1149495 Title: Dash home application icon is different from app-lens icon Status in Ayatana Design: Fix Committed Status in Unity Asset Pool: In Progress Status in Unity Asset Pool trusty series: Triaged Status in unity package in Ubuntu: Invalid Status in unity-asset-pool package in Ubuntu: In Progress Bug description: In Ubuntu 13.04 daily builds, application icon in "dash home" which shows recently used applications is the old app icon while app-lens icon is updated to a new one, an A with a progressbar (see the screenshot attached). The home application icon should be the same. - Desired resolution: - The icon should be the "A" version in both places To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/1149495/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1241757] Re: Unity Launcher always assumes default background is active for a couple of seconds
** Changed in: unity Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1241757 Title: Unity Launcher always assumes default background is active for a couple of seconds Status in Unity: Fix Committed Status in Unity 7.2 series: Triaged Status in unity package in Ubuntu: Fix Released Bug description: This happened for the first time after upgrading to Ubuntu 13.10 (64-bit) and it won't just go... Every time the computer boots and autologins to my desktop, I see the default background only behind the Unity Launcher for a couple of seconds, and then it is replaced with the current wallpaper. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1241757/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1384242] Re: Lockscreen messages might overlap the user prompt view.
** Changed in: unity Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1384242 Title: Lockscreen messages might overlap the user prompt view. Status in Unity: Fix Committed Status in Unity 7.2 series: Triaged Status in unity package in Ubuntu: Fix Released Bug description: Lockscreen messages might overlap the user prompt view. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1384242/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1397006] Re: AP test failures caused by newer pygobject
** Changed in: unity Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1397006 Title: AP test failures caused by newer pygobject Status in Unity: Fix Committed Status in unity package in Ubuntu: Fix Released Bug description: A handful of new AP test failures in the Unity suite started appearing recently after a pygobject upgrade because that library now raises an exception if both static glib and gi Glib are used in the same program. The following tests fail and need to be modified to use gi instead of static glib. unity.tests.test_gnome_key_grabber.GnomeKeyGrabberTests.test_grab_accelerator unity.tests.test_gnome_key_grabber.GnomeKeyGrabberTests.test_grab_accelerators unity.tests.test_gnome_key_grabber.GnomeKeyGrabberTests.test_grab_same_accelerator To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1397006/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1402707] Re: AP tests fail because of upstream .desktop file rename
** Changed in: unity Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1402707 Title: AP tests fail because of upstream .desktop file rename Status in Unity: Fix Committed Status in unity package in Ubuntu: Fix Released Bug description: Some autopilot tests have started failing because the rely on upstream .desktop file names and those names have been changed by upstream. In particular, the Unity AP tests use file-roller.desktop which has been renamed by upstream to org.gnome.FileRoller.desktop. Failing tests are as follows. unity.tests.launcher.test_scroll.LauncherScrollTests.test_autoscrolling_from_top(Single Monitor) unity.tests.launcher.test_scroll.LauncherScrollTests.test_autoscrolling_from_bottom(Single Monitor) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1402707/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1398287] Re: Unity 14.04 Lock button sometimes takes 30~60s to enter lock screen
** Also affects: unity/7.2 Importance: Undecided Status: New ** Changed in: unity/7.2 Importance: Undecided => Medium ** Changed in: unity/7.2 Milestone: None => 7.2.4 ** Changed in: unity/7.2 Status: New => Triaged -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1398287 Title: Unity 14.04 Lock button sometimes takes 30~60s to enter lock screen Status in Unity: In Progress Status in Unity 7.2 series: Triaged Status in unity package in Ubuntu: Fix Released Bug description: When the power button is pressed, the shutdown dialog will be displayed. Then clicks the 'Lock' button on the HUD and it sometimes takes about 30~60s to lock screen. This happens on many Intel-only platforms. PS: If user moves the cursor out of the dialog window after clicking the 'Lock' button, it will switch to lock screen immediately. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1398287/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1383468] Re: Windows in non-focused workspaces have not decorations in expo
** Also affects: unity/7.2 Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1383468 Title: Windows in non-focused workspaces have not decorations in expo Status in Unity: Fix Committed Status in Unity 7.2 series: New Status in unity package in Ubuntu: Fix Released Bug description: 1. Open multiple windows and put them in different workspaces 2. Hit Super+S to open the expo 3. Notice that windows that are not in the focused workspaces have no decorations To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1383468/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1375271] Re: desktop or other past screen contents visible before lockscreen on resume
** Also affects: unity/7.2 Importance: Undecided Status: New ** Changed in: unity/7.2 Importance: Undecided => Medium ** Changed in: unity/7.2 Status: New => In Progress ** Changed in: unity/7.2 Milestone: None => 7.2.4 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1375271 Title: desktop or other past screen contents visible before lockscreen on resume Status in GNOME Screensaver: New Status in Unity: Fix Committed Status in Unity 7.2 series: In Progress Status in unity package in Ubuntu: Fix Released Bug description: This appears to be a regression in 14.10 sometime in September 2014. The behavior appears similar to this bug from 2011: https://bugs.launchpad.net/unity-2d/+bug/830348 On resume from suspend, screen contents are displayed for a brief time (perhaps 0.5 to 1 sec) before the lock dialog appears. These screen contents are not always the desktop or open application beneath the lock screen. On at least one occasion, the screen showed content from a full-screen video that had been playing in Firefox some time before the computer had been suspended: neither the video nor its underlying tab were open anymore, so the image(s) was likely part of a buffer somewhere. (Needless to say, if the wrong full-screen video had been watched, depending on the setting, this could be a quite serious issue for some users). I have not exhaustively tested conditions in which this appears. However, just now, the bug did not appear when keeping the lid open, suspending, and then resuming with the power button. But when suspending from menu, closing the lid, then opening the lid and moving the mouse, the screen displayed contents before showing the lock dialog. The image displayed was of the desktop (with this bug reporting window) and showed the "suspend" item in the power menu being highlighted/clicked. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: unity 7.3.1+14.10.20140915-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-18.25-generic 3.16.3 Uname: Linux 3.16.0-18-generic x86_64 ApportVersion: 2.14.7-0ubuntu2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Mon Sep 29 08:38:57 2014 InstallationDate: Installed on 2014-08-10 (50 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) SourcePackage: unity UpgradeStatus: Upgraded to utopic on 2014-08-10 (50 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-screensaver/+bug/1375271/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1313446] Re: window disappears on toggle shade
@abierbaum Changing the importance to "Mediaum" merely indicates that's where the importance of the bug lies on the Importance spectrum. It does not mean it will not be fixed. Generally marking a bug as "Critical" means it is a crash preventing basic functionality or causing data loss. The fact that this problem is not related to a crash or data loss and does not affect regular functionality (ie. functionality available without installing and running third-party applications) means that the bug does not qualify as "Critical" or "High" importance. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1313446 Title: window disappears on toggle shade Status in Unity: Confirmed Status in unity package in Ubuntu: Confirmed Bug description: I used Unity Tweak Tool to enable Toggle Shade using middle click. When I click to top of the window, it rolls up and disappears. A "ghost" outline of the window appears and the only way to get the window back is by using Alt-tab. Sometimes, when reselecting the window using Alt-tab, Ubuntu freezes (crashes) and an internal error is generated. It seems to be related to Compiz but I'm not sure. An error report was generated and sent. Description: Ubuntu 14.04 LTS (64-bit) Release: 14.04 unity-tweak-tool 0.0.6ubuntu1 I expected the window would "roll up" and I'd be left with the window's top bar like with previous versions of Ubuntu. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1313446/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1241757] Re: Unity Launcher always assumes default background is active for a couple of seconds
** Also affects: unity/7.2 Importance: Undecided Status: New ** Changed in: unity/7.2 Status: New => Triaged ** Changed in: unity/7.2 Importance: Undecided => Low ** Changed in: unity/7.2 Milestone: None => 7.2.4 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1241757 Title: Unity Launcher always assumes default background is active for a couple of seconds Status in Unity: In Progress Status in Unity 7.2 series: Triaged Status in unity package in Ubuntu: In Progress Bug description: This happened for the first time after upgrading to Ubuntu 13.10 (64-bit) and it won't just go... Every time the computer boots and autologins to my desktop, I see the default background only behind the Unity Launcher for a couple of seconds, and then it is replaced with the current wallpaper. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1241757/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1384242] Re: Lockscreen messages might overlap the user prompt view.
** Changed in: unity Milestone: None => 7.3.1 ** Also affects: unity/7.2 Importance: Undecided Status: New ** Changed in: unity/7.2 Status: New => Triaged ** Changed in: unity/7.2 Importance: Undecided => Low ** Changed in: unity/7.2 Milestone: None => 7.2.4 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1384242 Title: Lockscreen messages might overlap the user prompt view. Status in Unity: In Progress Status in Unity 7.2 series: Triaged Status in unity package in Ubuntu: In Progress Bug description: Lockscreen messages might overlap the user prompt view. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1384242/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1398287] Re: Unity 14.04 Lock button sometimes takes 30~60s to enter lock screen
** Changed in: unity Milestone: None => 7.3.1 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1398287 Title: Unity 14.04 Lock button sometimes takes 30~60s to enter lock screen Status in Unity: In Progress Status in unity package in Ubuntu: In Progress Bug description: When the power button is pressed, the shutdown dialog will be displayed. Then clicks the 'Lock' button on the HUD and it sometimes takes about 30~60s to lock screen. This happens on many Intel-only platforms. PS: If user moves the cursor out of the dialog window after clicking the 'Lock' button, it will switch to lock screen immediately. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1398287/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1401911] Re: When the screen is locked edge barriers should be deactivated.
** Also affects: unity/7.2 Importance: Undecided Status: New ** Changed in: unity/7.2 Status: New => Triaged ** Changed in: unity/7.2 Importance: Undecided => Low ** Changed in: unity/7.2 Milestone: None => 7.2.4 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1401911 Title: When the screen is locked edge barriers should be deactivated. Status in Unity: In Progress Status in Unity 7.2 series: Triaged Status in unity package in Ubuntu: In Progress Bug description: If the screen is locked, launcher/panel edge barriers at the moment are active. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1401911/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1361751] Re: Launcher Icon shortcut labels don't honor text scaling
** Changed in: unity Status: In Progress => Fix Committed ** Changed in: unity (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1361751 Title: Launcher Icon shortcut labels don't honor text scaling Status in Unity: Fix Committed Status in Unity 7.2 series: In Progress Status in unity package in Ubuntu: Fix Released Bug description: Text scaling value is ignored by icons overlay text. - From u-c-c → accessibility → enable "Big Text" option Icons overlay text should honor that setting. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1361751/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1276177] Re: Applications using client-side decorations are not resizable in Unity
** Also affects: unity/7.2 Importance: Undecided Status: New ** Changed in: unity/7.2 Status: New => In Progress ** Changed in: unity/7.2 Importance: Undecided => Medium ** Changed in: unity/7.2 Milestone: None => 7.2.4 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1276177 Title: Applications using client-side decorations are not resizable in Unity Status in Themes for Ubuntu: In Progress Status in Unity: Fix Committed Status in Unity 7.2 series: In Progress Status in unity package in Ubuntu: Fix Released Status in gtk+3.0 package in Debian: Confirmed Bug description: GNOME applications that use client-side decorations can't be resized on Unity. I think it's because the frame extents hint is not supported. gnome-clocks and gnome-tweak-tool are two apps in the archive that have this problem. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-themes/+bug/1276177/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1237132] Re: Change "Show Desktop" icon option label when this option is in the state where it will reverse the prior show desktop action.
** Changed in: unity/7.2 Status: Triaged => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1237132 Title: Change "Show Desktop" icon option label when this option is in the state where it will reverse the prior show desktop action. Status in Ayatana Design: Fix Committed Status in Unity: Fix Committed Status in Unity 7.2 series: In Progress Status in unity package in Ubuntu: Fix Released Bug description: If I were to sit next to you at your computer, put my arm around your shoulder and ask you: "Show me the Desktop" What would you do? Load up a Firefox window? What if I asked you again "Show me the Desktop" Would you do something different than, say, show the desktop? Thusly, when one selects "Show Desktop" with ALT+TAB I propose either: 1) Show the Desktop and only the desktop, no matter the state. Or: 2) Change the state from "Show Desktop" to "Show Open Windows." Thank you for your consideration. -- Desired solution: - First see the description of bug #966030 - When the user is in the 3rd state described in the description of the aforementioned bug (e.g. they have just used the 'Show Desktop' function to minimise all their windows, and have not opened or restored any new windows after doing this), if the user goes to the 'Show Desktop' option in Alt-Tab, the title should be changed to 'Restore Windows'. The action that is performed when this option is selected should not change, the only thing that should change is the label in this state. - If possible, it would also be good to change the tooltip of the Launcher Show Desktop icon when in this state if possible, but if not no worries. To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/1237132/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1324104] Re: Ctrl + Super + D hides windows but still resizable when cursor over border
** Changed in: unity/7.2 Milestone: None => 7.2.4 ** Changed in: unity/7.2 Status: Triaged => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1324104 Title: Ctrl + Super + D hides windows but still resizable when cursor over border Status in Unity: Fix Committed Status in Unity 7.2 series: In Progress Status in unity package in Ubuntu: Fix Released Bug description: If You Press Ctrl + Super + D Shortcut To minimize all windows it works but when you move the cursor you will see it change to an arrow for resizing the hidden windows when the cursor is in the location of the border of the hidden windows Description: Ubuntu 14.04 LTS Release: 14.04 unity: Installed: 7.2.0+14.04.20140423-0ubuntu1.2 Candidate: 7.2.0+14.04.20140423-0ubuntu1.2 Version table: *** 7.2.0+14.04.20140423-0ubuntu1.2 0 500 http://security.ubuntu.com/ubuntu/ trusty-security/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages 500 http://lb.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages 100 /var/lib/dpkg/status 7.2.0+14.04.20140416-0ubuntu1 0 500 http://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages 500 http://lb.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1324104/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1400190] Re: Error transferring track
** Changed in: unity Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gstreamer1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1400190 Title: Error transferring track Status in Decibel Audio Ripper: New Status in Gstreamer: New Status in The Linux Mint Distribution: New Status in Unity: Invalid Status in gstreamer1.0 package in Ubuntu: New Bug description: Error transferring track Could not open CD device for reading. Could not read CD. Rhythmbox was doing just fine as I was extracting a CD until it got almost done, now it's stuck as it seems. I have cancelled the extraction, ejected and remounted the disc and now the problem is worse! I cannot extract ANYTHING this time, even track one! ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: libgstreamer1.0-0 1.4.3-1 ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4 Uname: Linux 3.16.0-24-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity Date: Sun Dec 7 21:27:57 2014 InstallationDate: Installed on 2014-11-08 (30 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gstreamer1.0 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/decibel-audio-ripper/+bug/1400190/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1311316] Re: After locking screen there is no input field to type password for unlock
> But a password field should always be shown by the unlock screen, regardless of the authentication backend. No. For example, if smart card authentication is in use, the PIN entry field should not be shown until and unless the smart card is inserted in the reader. If challenge-response authentication is in use, it would incorrect to display the response field until the user ID has been entered and a challenge presented. There are a number of scenarios in which it is just wrong to present a password field. It is correct for the Unity lock screen to not always displaying a password entry field when it has not been instructed to do so by the underlying auth mech. Any authentication dialog that does so, and actually authenticates the user as a result, possibly has a critical security vulnerability. It would be a good idea to audit your local authentication setup if you are seeing this bug. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1311316 Title: After locking screen there is no input field to type password for unlock Status in Unity: Confirmed Status in Unity 7.2 series: Confirmed Status in unity package in Ubuntu: Fix Released Bug description: Sometimes (but not always) after locking the screen there is the situation not having any input field where I can type the password to unlock the session again. The shaded gray area simply does not have the input field. I can't do anything, I have to switch to text console and stop/start lightdm service to cure the problem loosing all of my session :( ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.0+14.04.20140416-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic i686 ApportVersion: 2.14.1-0ubuntu3 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Tue Apr 22 22:17:57 2014 InstallationDate: Installed on 2012-03-03 (780 days ago) InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1) SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2013-10-18 (186 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1311316/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1398222] Re: add scroll bars for instance/window switcher of application icon
** Changed in: unity (Ubuntu) Importance: Undecided => Medium ** Changed in: unity (Ubuntu) Status: New => Triaged ** Also affects: unity Importance: Undecided Status: New ** Changed in: unity Status: New => Triaged ** Changed in: unity Importance: Undecided => Medium -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1398222 Title: add scroll bars for instance/window switcher of application icon Status in Unity: Triaged Status in unity package in Ubuntu: Triaged Bug description: When multiple instance of the same program and/or multiple windows of one program are opened, the icon in the starter offers a list of the instances and windows which allows to switch between them when the user right clicks on the icon. When more instances are opened than the maximum of entries in this list, the list just expands off the screen instead of offering scrollbars. This is a common issue when using `auto-apt` without privileges which opens a separate window for each invocation of `apt-get install` (running `auto-apt run ./configure` for gcc 4.6.4 easily makes `auto-apt` open > 50 terminals). ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: unity 7.3.1+14.10.20141016-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-25.33-generic 3.16.7 Uname: Linux 3.16.0-25-generic x86_64 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Tue Dec 2 01:09:56 2014 SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1398222/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1109805] Re: Spread - Window glow is incorrectly painted in the screen when switching spreaded application
Closing Compiz 0.9.9 task (0.9.9 series is obsolete) ** Changed in: compiz/0.9.9 Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1109805 Title: Spread - Window glow is incorrectly painted in the screen when switching spreaded application Status in Compiz: Fix Released Status in Compiz 0.9.9 series: Fix Released Status in Unity: Fix Released Status in “compiz” package in Ubuntu: Fix Released Status in “unity” package in Ubuntu: Fix Released Bug description: 1) Open 2 or more windows of an app (i.e. gedit) 2) Open 2 or more windows of an app (i.e. gnome-terminal) 3) Select a gedit window and press on its launcher icon to fire the spread 4) On spread, move the mouse over a window, so that the glow is shown 5) Select the terminal icon on the launcher. Expected behavior: 6) The terminal windows are now spreaded and no glow is shown as on the attached screenshot. To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/1109805/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1034616] Re: [Regression] Lowering window by middle click doesn't switch focus to raised window
Closing Compiz 0.9.9 task (0.9.9 series is obsolete) ** Changed in: compiz/0.9.9 Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1034616 Title: [Regression] Lowering window by middle click doesn't switch focus to raised window Status in Compiz: Fix Released Status in Compiz 0.9.9 series: Fix Released Status in Unity: Fix Released Status in “compiz” package in Ubuntu: Fix Released Status in “unity” package in Ubuntu: Fix Released Bug description: Middle mouse click on title bar will lower window; but it does not switch the focus to the window which was raised above it. 1) Open a gedit app window 2) Open a calc app 3) Middle click the mouse on the calculator title bar. It should lower the calculator and raise the gedit window as well as switch the focus to gedit. But it doesnt switch the focus. See also: autopilot run unity.tests.test_panel.PanelGrabAreaTests.test_lower_the_maximized_window_works To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/1034616/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1075207] Re: [regression] Shortcut overlay does not hide when modifier key is pressed
Closing Compiz 0.9.9 task (0.9.9 series is obsolete) ** Changed in: compiz/0.9.9 Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1075207 Title: [regression] Shortcut overlay does not hide when modifier key is pressed Status in Ayatana Design: Fix Committed Status in Compiz: Fix Released Status in Compiz 0.9.9 series: Fix Released Status in Unity: Fix Released Status in “compiz” package in Ubuntu: Fix Released Status in “unity” package in Ubuntu: Fix Released Bug description: On trunk, the autopilot test case unity.tests.test_shortcut_hint.ShortcutHintInteractionsTests.test_shortcut_hint_hide_pressing_modifiers fails as a regression. [Test Case] 1. Press and hold Super to show the Shortcut overlay screen 2. Press any modifier key -> Make sure the overlay badges on the launcher icons disappear -- Desired solution: - When the SUPER key is pressed, all keys with the exception of the "P" key should be grabbed by Unity. - This should allow the "Shortcut overlay does not hide when modifier key is pressed" while enabling the laptop SUPER+P presentation mode to still work. To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/1075207/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 906231] Re: Unity rendered behind windows
Closing Compiz 0.9.9 task (0.9.9 series is obsolete) ** Changed in: compiz/0.9.9 Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/906231 Title: Unity rendered behind windows Status in Compiz: Fix Released Status in Compiz 0.9.9 series: Fix Released Status in Unity: Invalid Status in Unity 5.0 series: Invalid Status in Unity 6.0 series: Invalid Status in “compiz” package in Ubuntu: Fix Released Status in “unity” package in Ubuntu: Invalid Bug description: Confirmed in Ubuntu 11.10, 12.04 and 12.10... Unity randomly goes behind other windows, which should never happen. ORIGINAL DESCRIPTION: Unity's Dock disappears behind all other windows, as you can see from the attached screenshot (making the dock just visible through the shortcut Command+W). Once it has disappeared, the only workaround is to close all applications/restart the desktop to be able to access dock icons or launch any applications through text search, since everything has disappeared to an inaccessible layer. To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/906231/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1174495] Re: Window Managers instability with r600 radeon and high monitor resolutions
Closing 0.9.9 task (0.9.9 series is obsolete) ** Changed in: compiz/0.9.9 Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1174495 Title: Window Managers instability with r600 radeon and high monitor resolutions Status in Compiz: Fix Released Status in Compiz 0.9.9 series: Fix Released Status in Mesa: Fix Released Status in “cogl” package in Ubuntu: Confirmed Status in “compiz” package in Ubuntu: Fix Released Status in “kde-workspace” package in Ubuntu: Fix Released Status in “mesa” package in Ubuntu: Confirmed Status in “cogl” source package in Raring: Confirmed Status in “compiz” source package in Raring: Fix Released Status in “kde-workspace” source package in Raring: Fix Released Status in “cogl” source package in Saucy: Confirmed Status in “compiz” source package in Saucy: Fix Released Status in “kde-workspace” source package in Saucy: Fix Released Bug description: [Impact] KWin 4.10.2 and Compiz 0.9.9 are using MSAA visuals with 13.04's mesa. This is unintended and leads to resource exhaustion which eventually crashes the WM. This affects all users on the r600 with sufficiently sized displays. [Test Case] Run Kwin or Unity with an r600 card, if it does not crash after a while we are happy. [Regression Potential] None, the fix was done by an upstream KWin and Mesa developer plus it has been incorporated into Fedora for a while plus it was used elsewhere in KWin already but not in this specific code path. [Other Info] None. -- I think the version of kwin included in 13.04 contains a known bug as described here: https://bugs.kde.org/show_bug.cgi?id=315089 https://bugs.freedesktop.org/show_bug.cgi?id=61182 My understanding of the problem is as follows: * The Mesa radeon r600 driver recently added support for MSAA GLX visuals * Kwin isn't aware of MSAA properties and happens to (incorrectly) pick MSAA visuals for everything * These visuals occupy a large amount of memory when running at high monitor resolutions * Mesa is "only" capable of mapping 256MB of visuals into CPU address space at once * Kwin's oversize visuals exceeds this limit, resulting in constant crashes The two radeon systems I have both crash immediately after logging in, when running with at a resolution of 2560x1440 and desktop effects enabled. After restarting kwin, a crash can be induced by performing actions that triggers desktop effects/animations. The resulting callstack is attached. ProblemType: BugDistroRelease: Ubuntu 13.04 Package: kde-window-manager 4:4.10.2-0ubuntu2 ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8 Uname: Linux 3.8.0-19-generic x86_64 ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 Date: Mon Apr 29 19:53:57 2013 InstallationDate: Installed on 2013-04-27 (2 days ago) InstallationMedia: Kubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MarkForUpload: TrueSourcePackage: kde-workspace UpgradeStatus: No upgrade log present (probably fresh install) -- Compiz (unity) is affected by the same issue as shown in this stacktrace: http://paste.ubuntu.com/5661055/ To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/1174495/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 992697] Re: Window management - 'Ctrl-Alt-Numpad 4' and 'Ctrl-Alt-Numpad 6' window placement shortcuts are broken
marking as closed (0.9.10 series is obsolete) ** Changed in: compiz/0.9.10 Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/992697 Title: Window management - 'Ctrl-Alt-Numpad 4' and 'Ctrl-Alt-Numpad 6' window placement shortcuts are broken Status in Autopilot: Fix Released Status in Ayatana Design: Fix Committed Status in Compiz: Fix Released Status in Compiz 0.9.10 series: Fix Released Status in Unity: Fix Released Status in “autopilot” package in Ubuntu: Fix Released Status in “compiz” package in Ubuntu: Fix Released Status in “unity” package in Ubuntu: Fix Released Bug description: The "Ctrl + Alt + numpad 4" and "Ctrl + Alt + numpad 6" keyboard shortcuts are not working in 13.04. See bug #878820 for the full specification of the numpad window placement shortcuts. Quoting from this bug: "Ctrl-Alt-Numpad 4 - Place window on the left side of the screen in *semi-maximised* state (it is important that the window is actually semi-maximised, not just the same size and position as a semi- maximised window) Pressing a second time does nothing. Ctrl-Alt-Numpad 6 - Place window on the right side of the screen (it is important that the window is actually semi-maximised, not just the same size and position as a semi-maximised window). Pressing a second time does nothing." HOWTO: The solution we want here are additional shortcuts to semi-maximize windows vertically and move them to left/right half of the screen... The best way to achieve that: 1. Remove the changing of the standard shortcuts by debian/patches/ubuntu-config.patch, so the original ones will work again. 2. Add 2 quasi-duplicated shortcuts with the functions to semi-maximize windows vertically and move them to left/right half of the screen to Grid and make those functions use "Ctrl + Super + Cursor Left or Right" on Ubuntu. To manage notifications about this bug go to: https://bugs.launchpad.net/autopilot/+bug/992697/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1201071] Re: No windows dekoration with GNOME-Fallback
** Changed in: unity Status: New => Invalid ** Changed in: unity (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1201071 Title: No windows dekoration with GNOME-Fallback Status in Compiz: New Status in Unity: Invalid Status in “compiz” package in Ubuntu: New Status in “unity” package in Ubuntu: Invalid Bug description: Ubuntu 13.04 with GNOME-Fallback in VirtualBox has no windows dekoration and 'fusion-icon' is in error. :~$ fusion-icon --no-start * Detected Session: gnome * Searching for installed applications... Speicherzugriffsfehler (Speicherabzug geschrieben) ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: unity 7.0.0daily13.04.18~13.04-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-26.38-generic 3.8.13.2 Uname: Linux 3.8.0-26-generic i686 .tmp.unity.support.test.0: ApportVersion: 2.9.2-0ubuntu8.1 Architecture: i386 CompizPlugins: [core,composite,opengl,imgjpeg,compiztoolbox,decor,gnomecompat,move,mousepoll,text,place,wallpaper,vpswitch,imgpng,imgsvg,regex,animation,grid,resize,wobbly,session,workarounds,kdecompat,fade,cube,rotate,unitymtgrabhandles,expo,scale,ezoom,unityshell] CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Sun Jul 14 10:17:00 2013 DistUpgraded: 2013-04-27 12:39:26,807 DEBUG enabling apt cron job DistroCodename: raring DistroVariant: ubuntu DkmsStatus: vboxguest, 4.2.16, 3.8.0-26-generic, i686: installed GraphicsCard: InnoTek Systemberatung GmbH VirtualBox Graphics Adapter [80ee:beef] (prog-if 00 [VGA controller]) InstallationDate: Installed on 2012-01-17 (543 days ago) InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111012) Lsusb: Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: innotek GmbH VirtualBox MarkForUpload: True ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-26-generic root=UUID=a74fe42d-7eb8-4664-a50f-6478696b72fc ro quiet splash vt.handoff=7 Renderer: Software SourcePackage: unity UpgradeStatus: Upgraded to raring on 2013-04-27 (77 days ago) dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH version.compiz: compiz 1:0.9.9~daily13.06.19~13.04-0ubuntu1 version.libdrm2: libdrm2 2.4.43-0ubuntu1.1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.1.3-0ubuntu0.3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.1.3-0ubuntu0.3 version.xserver-xorg-core: xserver-xorg-core 2:1.13.3-0ubuntu6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2b2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.1.0-0ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.21.6-0ubuntu4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.7-0ubuntu1 xserver.bootTime: Sun Jul 14 10:16:05 2013 xserver.configfile: default xserver.errors: AIGLX error: vboxvideo does not export required DRI extension AIGLX: reverting to software rendering xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.13.3-0ubuntu6 xserver.video_driver: vboxvideo To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/1201071/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 776824] Re: No panel and sidebar after enabling compiz cube
This problem no longer appears to occur with Compiz 0.9.12 or later and Unity 7.2.0 or later. Assuming it got fixed somewhere along the way over the last 4 years. ** Changed in: compiz Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/776824 Title: No panel and sidebar after enabling compiz cube Status in Compiz: Fix Released Status in “unity” package in Ubuntu: Invalid Bug description: I just finished installing 11.04 on my desktop. After installing the applications i need from the software center, including the CCSM, then i opened the CCSM and enabled the Desktop Cube, after i clicked it it ask if i want to disable the Desktop Wall, which i acknowledged. Then it ask if i want to enable the OpenGL or something, i also acknowledged it. Then suddenly the Panel, sidebar, and all the window menu just disappeared, i tried to restart but the menus, are still missing.. My hardware: MoBo: ECS GeForce6100PM-M2 GPU: NVIDIA Geforce 9400GT CPU: AMD Athlon 64 X2 Dual Core 4000+ 2.1Ghz DIMM: 1 Gig 2X 512Mb 667 DDR2 ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: gnome-system-monitor 2.28.2-0ubuntu1 ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2 Uname: Linux 2.6.38-8-generic i686 NonfreeKernelModules: nvidia Architecture: i386 Date: Wed May 4 09:02:18 2011 ExecutablePath: /usr/bin/gnome-system-monitor InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1) ProcEnviron: LANGUAGE=en_PH:en LANG=en_PH.UTF-8 SHELL=/bin/bash SourcePackage: gnome-system-monitor UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/776824/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1301699] Re: Indicators do not show in Pantheon
** Description changed: + [Impact] + It looks like "OnlyShowIn=Unity;GNOME;" has been added to indicator- datetime, indicator-session, and indicator-sound We should provide a patch to add "Pantheon" to that list. + + [Test Case] + + (1) install the Pantheon desktop sesssion (eg. Elementary OS) and log in + (2) verify the appropriate indicator (for this case, session indicator) appears + (3) install the Unity 7 desktop session and log in + (4) verify the indicator still appears + + [Regression Potential] + + A typo in the modified .desktop file could cause the indicator to not + appear in a Ubuntu session such as Unity 7 or Gnome Flashback. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-datetime in Ubuntu. https://bugs.launchpad.net/bugs/1301699 Title: Indicators do not show in Pantheon Status in elementary OS: Fix Released Status in Application Indicators: New Status in The Date and Time Indicator: New Status in Network Menu: New Status in The Session Menu: New Status in Sound Menu: New Status in “indicator-datetime” package in Ubuntu: Fix Released Status in “indicator-sound” package in Ubuntu: Fix Released Status in “indicator-session” source package in Trusty: In Progress Bug description: [Impact] It looks like "OnlyShowIn=Unity;GNOME;" has been added to indicator- datetime, indicator-session, and indicator-sound We should provide a patch to add "Pantheon" to that list. [Test Case] (1) install the Pantheon desktop sesssion (eg. Elementary OS) and log in (2) verify the appropriate indicator (for this case, session indicator) appears (3) install the Unity 7 desktop session and log in (4) verify the indicator still appears [Regression Potential] A typo in the modified .desktop file could cause the indicator to not appear in a Ubuntu session such as Unity 7 or Gnome Flashback. To manage notifications about this bug go to: https://bugs.launchpad.net/elementaryos/+bug/1301699/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1318980] Re: Translations are not shipped
** Description changed: + [Impact] + The current indicator-location package does not seem to ship the built translations (.mo files) from the translation sources (.po files) it contains in the source tree. As such, its messages appear in English regardless of the locale selected. It seems that the installation does not correctly build them and does not put them in $LOCALE_DIR/LC_MESSAGES/$LANG/$INDICATOR_NAME.mo Where $LOCALE_DIR is /usr/share/locale and $LANG is the ISO-639 language code for each locale. Instead, it installs a single .mo file in the wrong location: $ dpkg -L indicator-location [...] /usr/share/locale /usr/share/locale/LC_MESSAGES /usr/share/locale/LC_MESSAGES/indicator-location.mo + + [Test Case] + + Change the session locale to a non-English one through System Settings + -> Lanuage Support. Log in to a Unity 7 session and pull down the + System Indicator. The entries should be translated. + + [Regression Potential] + + It's possible this fix may not fix the translations. + + Some locales may have difficulty with the default character rendering + engines and subsequently crash the Session Indicator. + + [Other Info] + + The translations already exist for this package, but are being installed incorrectly. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-location in Ubuntu. https://bugs.launchpad.net/bugs/1318980 Title: Translations are not shipped Status in “indicator-location” package in Ubuntu: Fix Released Status in “indicator-session” package in Ubuntu: Fix Released Status in “indicator-session” source package in Trusty: In Progress Bug description: [Impact] The current indicator-location package does not seem to ship the built translations (.mo files) from the translation sources (.po files) it contains in the source tree. As such, its messages appear in English regardless of the locale selected. It seems that the installation does not correctly build them and does not put them in $LOCALE_DIR/LC_MESSAGES/$LANG/$INDICATOR_NAME.mo Where $LOCALE_DIR is /usr/share/locale and $LANG is the ISO-639 language code for each locale. Instead, it installs a single .mo file in the wrong location: $ dpkg -L indicator-location [...] /usr/share/locale /usr/share/locale/LC_MESSAGES /usr/share/locale/LC_MESSAGES/indicator-location.mo [Test Case] Change the session locale to a non-English one through System Settings -> Lanuage Support. Log in to a Unity 7 session and pull down the System Indicator. The entries should be translated. [Regression Potential] It's possible this fix may not fix the translations. Some locales may have difficulty with the default character rendering engines and subsequently crash the Session Indicator. [Other Info] The translations already exist for this package, but are being installed incorrectly. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-location/+bug/1318980/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1296814] Re: When Unity.Session is available, use its API for logging out
** Description changed: + [Impact] + The session indicator always uses gnome-session to end the session (log out), but gnome-session is not guaranteed to be available under, for example, a Unity8 desktop preview session. It should use Upstart where available. + + [Test Case] + + Install unity8-desktop-session and choose to log in to that session from + the LightDM login screen. You should be able to select "log out" from + the session-indicator indicator and have it bring you back to the login + screen. + + [Regression Potential] + + In the worst case this change could affect log out operations from + regular Unity 7 sessions and potentially other sessions that use the + session indicator. In such a case, the log out operation would fail + necessitating a reboot or manual session kill. + + [Other Info] + + This change has been in production use on later releases of Ubuntu (14.10 and later) without problems. + + Later version of the Unity 8 desktop session do not exit to the LightDM + login screen but instead restart Unity 8 and present the Unity 8 login + screen. This is a bug in Unity 8 and not related to indicator-session. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1296814 Title: When Unity.Session is available, use its API for logging out Status in The Session Menu: Fix Released Status in Unity: New Status in “indicator-session” package in Ubuntu: Fix Released Status in “unity” package in Ubuntu: New Status in “unity8-desktop-session” package in Ubuntu: Fix Released Status in “indicator-session” source package in Trusty: In Progress Bug description: [Impact] The session indicator always uses gnome-session to end the session (log out), but gnome-session is not guaranteed to be available under, for example, a Unity8 desktop preview session. It should use Upstart where available. [Test Case] Install unity8-desktop-session and choose to log in to that session from the LightDM login screen. You should be able to select "log out" from the session-indicator indicator and have it bring you back to the login screen. [Regression Potential] In the worst case this change could affect log out operations from regular Unity 7 sessions and potentially other sessions that use the session indicator. In such a case, the log out operation would fail necessitating a reboot or manual session kill. [Other Info] This change has been in production use on later releases of Ubuntu (14.10 and later) without problems. Later version of the Unity 8 desktop session do not exit to the LightDM login screen but instead restart Unity 8 and present the Unity 8 login screen. This is a bug in Unity 8 and not related to indicator-session. To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-session/+bug/1296814/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1301699] Re: Indicators do not show in Pantheon
** Changed in: indicator-session (Ubuntu Trusty) Status: New => In Progress ** Changed in: indicator-session (Ubuntu Trusty) Importance: Undecided => Medium -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-datetime in Ubuntu. https://bugs.launchpad.net/bugs/1301699 Title: Indicators do not show in Pantheon Status in elementary OS: Fix Released Status in Application Indicators: New Status in The Date and Time Indicator: New Status in Network Menu: New Status in The Session Menu: New Status in Sound Menu: New Status in “indicator-datetime” package in Ubuntu: Fix Released Status in “indicator-sound” package in Ubuntu: Fix Released Status in “indicator-session” source package in Trusty: In Progress Bug description: It looks like "OnlyShowIn=Unity;GNOME;" has been added to indicator- datetime, indicator-session, and indicator-sound We should provide a patch to add "Pantheon" to that list. To manage notifications about this bug go to: https://bugs.launchpad.net/elementaryos/+bug/1301699/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1318980] Re: Translations are not shipped
** Changed in: indicator-session (Ubuntu Trusty) Status: New => In Progress ** Changed in: indicator-session (Ubuntu Trusty) Importance: Undecided => Medium -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-location in Ubuntu. https://bugs.launchpad.net/bugs/1318980 Title: Translations are not shipped Status in “indicator-location” package in Ubuntu: Fix Released Status in “indicator-session” package in Ubuntu: Fix Released Status in “indicator-session” source package in Trusty: In Progress Bug description: The current indicator-location package does not seem to ship the built translations (.mo files) from the translation sources (.po files) it contains in the source tree. As such, its messages appear in English regardless of the locale selected. It seems that the installation does not correctly build them and does not put them in $LOCALE_DIR/LC_MESSAGES/$LANG/$INDICATOR_NAME.mo Where $LOCALE_DIR is /usr/share/locale and $LANG is the ISO-639 language code for each locale. Instead, it installs a single .mo file in the wrong location: $ dpkg -L indicator-location [...] /usr/share/locale /usr/share/locale/LC_MESSAGES /usr/share/locale/LC_MESSAGES/indicator-location.mo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-location/+bug/1318980/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1296814] Re: When Unity.Session is available, use its API for logging out
** Changed in: indicator-session (Ubuntu Trusty) Status: New => In Progress ** Changed in: indicator-session (Ubuntu Trusty) Importance: Undecided => Medium -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1296814 Title: When Unity.Session is available, use its API for logging out Status in The Session Menu: Fix Released Status in Unity: New Status in “indicator-session” package in Ubuntu: Fix Released Status in “unity” package in Ubuntu: New Status in “unity8-desktop-session” package in Ubuntu: Fix Released Status in “indicator-session” source package in Trusty: In Progress Bug description: The session indicator always uses gnome-session to end the session (log out), but gnome-session is not guaranteed to be available under, for example, a Unity8 desktop preview session. It should use Upstart where available. To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-session/+bug/1296814/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 668987] Re: New sound indicator only restores Rhythmbox on the desktop it was closed on.
Definitely not happening in Ubuntu 14.04 or later. ** Changed in: compiz Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-sound in Ubuntu. https://bugs.launchpad.net/bugs/668987 Title: New sound indicator only restores Rhythmbox on the desktop it was closed on. Status in Compiz: Invalid Status in “indicator-sound” package in Ubuntu: Invalid Bug description: Binary package hint: rhythmbox Rhythmbox just got functionality back of minimizing to indicator on close (kind of) but restoring on the currently used desktop is broken. It restores on the same desktop it was closed on, forcing the user to switch back to that desktop again in order to use it. See the video for an example. ProblemType: Bug DistroRelease: Ubuntu 10.10 Package: rhythmbox 0.13.1-0ubuntu5 ProcVersionSignature: Ubuntu 2.6.35-22.35-generic 2.6.35.4 Uname: Linux 2.6.35-22-generic x86_64 NonfreeKernelModules: nvidia Architecture: amd64 Date: Sun Oct 31 00:19:17 2010 InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007) ProcEnviron: LANG=en_US.utf8 SHELL=/bin/bash SourcePackage: rhythmbox To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/668987/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1070817] Re: make test fails in CompizConfigPython.test_* (OTHER_FAULT)
** Changed in: compiz/0.9.8 Status: Triaged => Won't Fix ** Changed in: compiz/0.9.8 Milestone: 0.9.8.8 => None -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1070817 Title: make test fails in CompizConfigPython.test_* (OTHER_FAULT) Status in Compiz: Fix Released Status in Compiz 0.9.8 series: Won't Fix Status in “compiz” package in Ubuntu: Fix Released Status in “glib2.0” package in Ubuntu: New Bug description: make test ... 99% tests passed, 4 tests failed out of 928 Total Test time (real) = 24.32 sec The following tests FAILED: 1 - CompizConfigPython.test_backend (OTHER_FAULT) 2 - CompizConfigPython.test_plugin (OTHER_FAULT) 3 - CompizConfigPython.test_profile (OTHER_FAULT) 4 - CompizConfigPython.test_setting (OTHER_FAULT) Errors while running CTest make: *** [test] Error 8 To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/1070817/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1363959] Re: compiz crashed with SIGSEGV in nux::WindowCompositor::DndEventCycle()
debdiff between the version in trusty-updates and the proposed SRU containing the fix ** Attachment added: "debdiff between nux_4.0.6%2B14.04.20140930-0ubuntu1 and nux_4.0.6%2B14.04.20141107-0ubuntu1" https://bugs.launchpad.net/nux/+bug/1363959/+attachment/4263134/+files/debdiff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to nux in Ubuntu. https://bugs.launchpad.net/bugs/1363959 Title: compiz crashed with SIGSEGV in nux::WindowCompositor::DndEventCycle() Status in Nux: Fix Committed Status in Nux trusty series: In Progress Status in “nux” package in Ubuntu: Fix Released Status in “nux” source package in Trusty: In Progress Bug description: [Impact] An occasional unpredictable crash in the Unity shell occurs during a drag-and-drop operation. [Test Case] Unfortunately it is not possible to reproduce this bug at will. Apparently is is caused by an uninitialized pointer dereference that only occurs in a timing-dependent manner. Running a full autopilot test suite against the Unity desktop shell reveals no new regressions. [Regression Potential] The code change effectively adds a test for a null pointer. It is possible that this might introduce a regression in drag-and-drop functionality that previously relied on undefined behaviour to work when it didn't crash. [Other Info] Fix was released with Ubuntu 14.10 and no new regressions have been reported. To manage notifications about this bug go to: https://bugs.launchpad.net/nux/+bug/1363959/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1363959] Re: compiz crashed with SIGSEGV in nux::WindowCompositor::DndEventCycle()
** Description changed: - Description: Ubuntu Utopic Unicorn (development branch) - Release: 14.10 + [Impact] - compiz: - Geïnstalleerd: 1:0.9.12+14.10.20140812-0ubuntu1 - Kandidaat: 1:0.9.12+14.10.20140812-0ubuntu1 - Versietabel: - *** 1:0.9.12+14.10.20140812-0ubuntu1 0 - 500 http://nl.archive.ubuntu.com/ubuntu/ utopic/main i386 Packages - 100 /var/lib/dpkg/status + An occasional unpredictable crash in the Unity shell occurs during a + drag-and-drop operation. - ProblemType: Crash - DistroRelease: Ubuntu 14.10 - Package: compiz-core 1:0.9.12+14.10.20140812-0ubuntu1 - ProcVersionSignature: Ubuntu 3.16.0-11.16-generic 3.16.1 - Uname: Linux 3.16.0-11-generic i686 - .tmp.unity.support.test.0: - - ApportVersion: 2.14.7-0ubuntu1 - Architecture: i386 - CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' - CompositorRunning: compiz - CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' - CompositorUnredirectFSW: true - CurrentDesktop: Unity - Date: Mon Sep 1 12:30:05 2014 - DistUpgraded: Fresh install - DistroCodename: utopic - DistroVariant: ubuntu - ExecutablePath: /usr/bin/compiz - GraphicsCard: - Intel Corporation Atom Processor D4xx/D5xx/N4xx/N5xx Integrated Graphics Controller [8086:a011] (prog-if 00 [VGA controller]) -Subsystem: ASUSTeK Computer Inc. Device [1043:83ac] -Subsystem: ASUSTeK Computer Inc. Device [1043:83ac] - InstallationDate: Installed on 2014-08-29 (2 days ago) - InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha i386 (20140826) - MachineType: ASUSTeK Computer INC. 1001PX - ProcCmdline: compiz - ProcEnviron: - PATH=(custom, no user) - LANGUAGE=nl_NL - XDG_RUNTIME_DIR= - LANG=nl_NL.UTF-8 - SHELL=/bin/bash - ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.16.0-11-generic root=UUID=e2155ee3-e907-44c0-b6e7-f0608f136055 ro quiet splash vt.handoff=7 - SegvAnalysis: - Segfault happened at: 0xb0d08ed1 <_ZN3nux16WindowCompositor13DndEventCycleERNS_5EventE+257>: mov(%edx),%ecx - PC (0xb0d08ed1) ok - source "(%edx)" (0x) not located in a known VMA region (needed readable region)! - destination "%ecx" ok - SegvReason: reading NULL VMA - Signal: 11 - SourcePackage: compiz - StacktraceTop: - nux::WindowCompositor::DndEventCycle(nux::Event&) () from /usr/lib/i386-linux-gnu/libnux-4.0.so.0 - nux::WindowCompositor::ProcessEvent(nux::Event&) () from /usr/lib/i386-linux-gnu/libnux-4.0.so.0 - nux::WindowThread::DoProcessEvent(nux::Event&) () from /usr/lib/i386-linux-gnu/libnux-4.0.so.0 - nux::WindowThread::ProcessEvent(nux::Event&) () from /usr/lib/i386-linux-gnu/libnux-4.0.so.0 - nux::nux_event_dispatch(_GSource*, int (*)(void*), void*) () from /usr/lib/i386-linux-gnu/libnux-4.0.so.0 - Title: compiz crashed with SIGSEGV in nux::WindowCompositor::DndEventCycle() - UpgradeStatus: No upgrade log present (probably fresh install) - UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo - dmi.bios.date: 02/18/2011 - dmi.bios.vendor: American Megatrends Inc. - dmi.bios.version: 1201 - dmi.board.asset.tag: To Be Filled By O.E.M. - dmi.board.name: 1001PX - dmi.board.vendor: ASUSTeK Computer INC. - dmi.board.version: x.xx - dmi.chassis.asset.tag: 0x - dmi.chassis.type: 10 - dmi.chassis.vendor: ASUSTeK Computer INC. - dmi.chassis.version: x.x - dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1201:bd02/18/2011:svnASUSTeKComputerINC.:pn1001PX:pvrx.x:rvnASUSTeKComputerINC.:rn1001PX:rvrx.xx:cvnASUSTeKComputerINC.:ct10:cvrx.x: - dmi.product.name: 1001PX - dmi.product.version: x.x - dmi.sys.vendor: ASUSTeK Computer INC. - version.compiz: compiz 1:0.9.12+14.10.20140812-0ubuntu1 - version.libdrm2: libdrm2 2.4.56-1 - version.libgl1-mesa-dri: libgl1-mesa-dri 10.2.6-1ubuntu3 - version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A - version.libgl1-mesa-glx: libgl1-mesa-glx 10.2.6-1ubuntu3 - version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu9 - version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu1 - version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu1 - version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.914-1~exp1ubuntu1 - version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 - xserver.bootTime: Mon Sep 1 09:21:40 2014 - xserver.configfile: default - xserver.errors: - intel: Failed to load module "dri3" (module does not exist, 0) - intel: Failed to load module "present" (module does not exist, 0) - xserver.logfile: /var/log/Xorg.0.log - xserver.outputs: - product id1001 - vendor HSD - xserver.version: 2:1.15.1-0ubuntu9 + [Test Case] + + Unfortunately it is not possible to reproduce this bug at will. + Apparently is is caused by an uninitialized pointer dereference that + only occurs in a timing-dependent manner. + + Running a full autopilot test suite against the Unity desktop shell + reveals no new regr
[Touch-packages] [Bug 1363698] Re: unity-panel-service crashed with SIGSEGV in gtk_menu_tracker_remove_items()
*** This bug is a duplicate of bug 1300713 *** https://bugs.launchpad.net/bugs/1300713 ** Information type changed from Private to Public ** This bug has been marked a duplicate of bug 1300713 unity-panel-service crashed with SIGSEGV in gtk_menu_tracker_remove_items() -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1363698 Title: unity-panel-service crashed with SIGSEGV in gtk_menu_tracker_remove_items() Status in Unity: New Status in “unity” package in Ubuntu: New Bug description: The crash report showed up after working on the new installation of eclipse luna. I had already created a workspace and added projects to the new workspace. The menu of Eclipse was showing. Then I started a Run Configuration in Eclipse containing the imported projects. It took some time, but the started Eclipse+My Projects showed up. The central menu was not working. However, that might have had a different cause. Nevertheless, the crash report showed up. So this might have to do with running Eclipse or it might have other causes. For example, I have four Eclipse instance running at the moment. On a 2 GB netbook + 2 GB swap, this might have had some effect on some services where unity-panel-service depends on. I did not see any problems during my excerise, like missing menus or blinking/dissapearing and reappearing apps. However, I was kinda distracted looking at Eclipse logs and messages. So I might have missed it. ProblemType: Crash DistroRelease: Ubuntu 14.10 Package: unity-services 7.3.1+14.10.20140811-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-11.16-lowlatency 3.16.1 Uname: Linux 3.16.0-11-lowlatency i686 ApportVersion: 2.14.7-0ubuntu1 Architecture: i386 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,workarounds,scale,expo,ezoom] CrashCounter: 1 CurrentDesktop: Unity Date: Sun Aug 31 18:47:52 2014 ExecutablePath: /usr/lib/unity/unity-panel-service InstallationDate: Installed on 2013-04-18 (499 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release i386 (20121017.2) ProcCmdline: /usr/lib/unity/unity-panel-service SegvAnalysis: Segfault happened at: 0xb70d0119:mov(%eax),%esi PC (0xb70d0119) ok source "(%eax)" (0x) not located in a known VMA region (needed readable region)! destination "%esi" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: unity StacktraceTop: ?? () from /usr/lib/i386-linux-gnu/libgtk-3.so.0 ffi_call_SYSV () from /usr/lib/i386-linux-gnu/libffi.so.6 ffi_call () from /usr/lib/i386-linux-gnu/libffi.so.6 g_cclosure_marshal_generic () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0 g_closure_invoke () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0 SystemImageInfo: Error: [Errno 2] No such file or directory: 'system-image-cli' Title: unity-panel-service crashed with SIGSEGV in ffi_call_SYSV() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm autopilot cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1363698/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1300713] Re: unity-panel-service crashed with SIGSEGV in gtk_menu_tracker_remove_items()
** Information type changed from Private to Public -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1300713 Title: unity-panel-service crashed with SIGSEGV in gtk_menu_tracker_remove_items() Status in Unity: Confirmed Status in “unity” package in Ubuntu: Confirmed Bug description: starting vitualbox and evolution ProblemType: Crash DistroRelease: Ubuntu 14.04 Package: unity-services 7.1.2+14.04.20140328.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-20.42-generic 3.13.7 Uname: Linux 3.13.0-20-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Tue Apr 1 13:03:29 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu ExecutablePath: /usr/lib/unity/unity-panel-service InstallationDate: Installed on 2014-03-27 (4 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Beta amd64 (20140325.1) MachineType: MEDION X761X ProcCmdline: /usr/lib/unity/unity-panel-service ProcEnviron: PATH=(custom, no user) LANGUAGE=de_DE XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-20-generic.efi.signed root=UUID=f8dca303-39ef-4b95-b466-d28268e7dcf4 ro quiet splash vt.handoff=7 SegvAnalysis: Segfault happened at: 0x7f82a8bdfffc:mov(%rdi),%rbx PC (0x7f82a8bdfffc) 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: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo dmi.bios.date: 10/23/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E1771IM7.500 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: X761X dmi.board.vendor: MEDION dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To be filled by O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE1771IM7.500:bd10/23/2013:svnMEDION:pnX761X:pvrTobefilledbyO.E.M.:rvnMEDION:rnX761X:rvrTobefilledbyO.E.M.:cvnToBeFilledByO.E.M.:ct10:cvrTobefilledbyO.E.M.: dmi.product.name: X761X dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: MEDION version.compiz: compiz 1:0.9.11+14.04.20140328-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-1ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.15.0-1ubuntu7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Tue Apr 1 07:30:04 2014 xserver.configfile: /etc/X11/xorg.conf xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.15.0-1ubuntu7 To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1300713/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1037330] Re: unity-panel-service crashed with SIGSEGV in panel_indicator_entry_accessible_get_n_children() from append_children() from add_pending_items()
*** This bug is a duplicate of bug 1024871 *** https://bugs.launchpad.net/bugs/1024871 ** This bug has been marked a duplicate of bug 1024871 unity-panel-service crashed with SIGSEGV in panel_indicator_entry_accessible_get_n_children() -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1037330 Title: unity-panel-service crashed with SIGSEGV in panel_indicator_entry_accessible_get_n_children() from append_children() from add_pending_items() Status in Unity: Confirmed Status in “unity” package in Ubuntu: Confirmed Bug description: resume ProblemType: Crash DistroRelease: Ubuntu 12.10 Package: unity-services 6.2.0-0ubuntu2 ProcVersionSignature: Ubuntu 3.5.0-10.10-generic 3.5.1 Uname: Linux 3.5.0-10-generic x86_64 ApportVersion: 2.4-0ubuntu6 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] CrashCounter: 1 Date: Thu Aug 16 00:31:07 2012 ExecutablePath: /usr/lib/unity/unity-panel-service InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta amd64 (20120331) ProcCmdline: /usr/lib/unity/unity-panel-service ProcEnviron: SHELL=/bin/bash PATH=(custom, user) LANG=de_DE.UTF-8 SegvAnalysis: Segfault happened at: 0x4063bd: mov(%rbx),%rdx PC (0x004063bd) ok source "(%rbx)" (0x) not located in a known VMA region (needed readable region)! destination "%rdx" ok SegvReason: reading unknown VMA Signal: 11 SourcePackage: unity StacktraceTop: ?? () ?? () from /usr/lib/x86_64-linux-gnu/libatk-bridge-2.0.so.0 g_main_dispatch (context=0x1c27cd0) at /build/buildd/glib2.0-2.33.8/./glib/gmain.c:2707 g_main_context_dispatch (context=context@entry=0x1c27cd0) at /build/buildd/glib2.0-2.33.8/./glib/gmain.c:3211 g_main_context_iterate (context=0x1c27cd0, block=block@entry=1, dispatch=dispatch@entry=1, self=) at /build/buildd/glib2.0-2.33.8/./glib/gmain.c:3282 Title: unity-panel-service crashed with SIGSEGV in g_main_dispatch() UpgradeStatus: Upgraded to quantal on 2012-08-02 (12 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1037330/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1047738] Re: unity-panel-service crashed with SIGSEGV in g_main_context_dispatch()
*** This bug is a duplicate of bug 1024871 *** https://bugs.launchpad.net/bugs/1024871 ** This bug is no longer a duplicate of bug 1037330 unity-panel-service crashed with SIGSEGV in panel_indicator_entry_accessible_get_n_children() from append_children() from add_pending_items() ** This bug has been marked a duplicate of bug 1024871 unity-panel-service crashed with SIGSEGV in panel_indicator_entry_accessible_get_n_children() -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1047738 Title: unity-panel-service crashed with SIGSEGV in g_main_context_dispatch() Status in “unity” package in Ubuntu: New Bug description: I found similar bug reports but are all marked as invalid. I don't know if mine contains enough information. ProblemType: Crash DistroRelease: Ubuntu 12.10 Package: unity-services 6.4.0-0ubuntu5 ProcVersionSignature: Ubuntu 3.5.0-13.14-generic 3.5.3 Uname: Linux 3.5.0-13-generic x86_64 ApportVersion: 2.5.1-0ubuntu7 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' Date: Sat Sep 8 13:30:00 2012 ExecutablePath: /usr/lib/unity/unity-panel-service InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 (20120823.1) ProcCmdline: /usr/lib/unity/unity-panel-service SegvAnalysis: Segfault happened at: 0x40626d: mov(%rbx),%rdx PC (0x0040626d) ok source "(%rbx)" (0x) not located in a known VMA region (needed readable region)! destination "%rdx" ok SegvReason: reading unknown VMA Signal: 11 SourcePackage: unity StacktraceTop: ?? () ?? () from /usr/lib/x86_64-linux-gnu/libatk-bridge-2.0.so.0 g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_main_loop_run () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: unity-panel-service 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/1047738/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1393624] Re: Lock screen rejects password on Ubuntu 14.04
Do you have multiple monitors? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1393624 Title: Lock screen rejects password on Ubuntu 14.04 Status in “unity” package in Ubuntu: New Bug description: Password is systematically rejected on the lock screen. However, if I click Switch account, the *greeter* does accept the same password. This issue is reproducible either by hitting the Ctrl+Alt+L shortcut key or by runnibg `gnome-screensaver-command -l` This happens after I upgraded from Ubuntu 12.04 to 14.04. I had ATI Radeon HD 3870 with open source drivers, now I have GeForce GTX 750 Ti with NVIDIA proprietary drivers. Same thing. Ubuntu 14.04.1 LTS Linux 3.13.0-39-generic x86_64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1393624/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1330041] Re: Bad / incorrect display accented letters in Window title bar [ast]
@ivarela I looked at the Asturian keyboard layout chart and can't see a way to add the accented characters unless it uses dead keys (the keyboard layout chart doesn't illustrate those), so I haven't verified that problem. I had no problem creating a folder named /tmp/áéíóúü using my English (multilingual) keyboard in Gnome-Terminal even using the ast_ES.UTF-8 locale, and it shows correctly in the Gnome-Terminal window title in other locales. I strongly suspect they are two separate problems, although the origin of both may be errors in the locale definition. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1330041 Title: Bad / incorrect display accented letters in Window title bar [ast] Status in Unity: Triaged Status in Unity 7.2 series: Triaged Status in “unity” package in Ubuntu: Triaged Bug description: In Unity desktop, the accented letters (á , é, í, ó, ú..) aren't displayed correctly in the Window title bar when using Asturian language The bug is only reproduced in Unity. If you change to Gnome desktop (sudo apt-get install gnome-panel), window title bars are displayed correctly. In the same way, I have tested the problem and is not present in another languages like [es, ca..] To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1330041/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1330041] Re: Bad / incorrect display accented letters in Window title bar [ast]
I can confirm the UTF-8 text is rendered incorrectly in window title bars when LANG=ast_ES.UTF-8. The very same text (eg. working directory pathname in titlebar of Gnome-Terminal) renders correctly in other locales. It's unclear if this is a problem in the text rendering or in the local definition. ** Changed in: unity Importance: Undecided => Medium ** Changed in: unity Status: Confirmed => Triaged ** Changed in: unity/7.2 Status: Confirmed => Triaged ** Changed in: unity (Ubuntu) Importance: Undecided => Medium ** Changed in: unity (Ubuntu) Status: Confirmed => Triaged ** Changed in: unity/7.2 Importance: Undecided => Medium -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1330041 Title: Bad / incorrect display accented letters in Window title bar [ast] Status in Unity: Triaged Status in Unity 7.2 series: Triaged Status in “unity” package in Ubuntu: Triaged Bug description: In Unity desktop, the accented letters (á , é, í, ó, ú..) aren't displayed correctly in the Window title bar when using Asturian language The bug is only reproduced in Unity. If you change to Gnome desktop (sudo apt-get install gnome-panel), window title bars are displayed correctly. In the same way, I have tested the problem and is not present in another languages like [es, ca..] To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1330041/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1363959] Re: compiz crashed with SIGSEGV in nux::WindowCompositor::DndEventCycle()
** Changed in: nux (Ubuntu Trusty) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to nux in Ubuntu. https://bugs.launchpad.net/bugs/1363959 Title: compiz crashed with SIGSEGV in nux::WindowCompositor::DndEventCycle() Status in Nux: Fix Committed Status in Nux trusty series: In Progress Status in “nux” package in Ubuntu: Fix Released Status in “nux” source package in Trusty: In Progress Bug description: Description: Ubuntu Utopic Unicorn (development branch) Release: 14.10 compiz: Geïnstalleerd: 1:0.9.12+14.10.20140812-0ubuntu1 Kandidaat: 1:0.9.12+14.10.20140812-0ubuntu1 Versietabel: *** 1:0.9.12+14.10.20140812-0ubuntu1 0 500 http://nl.archive.ubuntu.com/ubuntu/ utopic/main i386 Packages 100 /var/lib/dpkg/status ProblemType: Crash DistroRelease: Ubuntu 14.10 Package: compiz-core 1:0.9.12+14.10.20140812-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-11.16-generic 3.16.1 Uname: Linux 3.16.0-11-generic i686 .tmp.unity.support.test.0: ApportVersion: 2.14.7-0ubuntu1 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Mon Sep 1 12:30:05 2014 DistUpgraded: Fresh install DistroCodename: utopic DistroVariant: ubuntu ExecutablePath: /usr/bin/compiz GraphicsCard: Intel Corporation Atom Processor D4xx/D5xx/N4xx/N5xx Integrated Graphics Controller [8086:a011] (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:83ac] Subsystem: ASUSTeK Computer Inc. Device [1043:83ac] InstallationDate: Installed on 2014-08-29 (2 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha i386 (20140826) MachineType: ASUSTeK Computer INC. 1001PX ProcCmdline: compiz ProcEnviron: PATH=(custom, no user) LANGUAGE=nl_NL XDG_RUNTIME_DIR= LANG=nl_NL.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.16.0-11-generic root=UUID=e2155ee3-e907-44c0-b6e7-f0608f136055 ro quiet splash vt.handoff=7 SegvAnalysis: Segfault happened at: 0xb0d08ed1 <_ZN3nux16WindowCompositor13DndEventCycleERNS_5EventE+257>: mov(%edx),%ecx PC (0xb0d08ed1) ok source "(%edx)" (0x) not located in a known VMA region (needed readable region)! destination "%ecx" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: compiz StacktraceTop: nux::WindowCompositor::DndEventCycle(nux::Event&) () from /usr/lib/i386-linux-gnu/libnux-4.0.so.0 nux::WindowCompositor::ProcessEvent(nux::Event&) () from /usr/lib/i386-linux-gnu/libnux-4.0.so.0 nux::WindowThread::DoProcessEvent(nux::Event&) () from /usr/lib/i386-linux-gnu/libnux-4.0.so.0 nux::WindowThread::ProcessEvent(nux::Event&) () from /usr/lib/i386-linux-gnu/libnux-4.0.so.0 nux::nux_event_dispatch(_GSource*, int (*)(void*), void*) () from /usr/lib/i386-linux-gnu/libnux-4.0.so.0 Title: compiz crashed with SIGSEGV in nux::WindowCompositor::DndEventCycle() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo dmi.bios.date: 02/18/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1201 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: 1001PX dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: x.xx dmi.chassis.asset.tag: 0x dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK Computer INC. dmi.chassis.version: x.x dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1201:bd02/18/2011:svnASUSTeKComputerINC.:pn1001PX:pvrx.x:rvnASUSTeKComputerINC.:rn1001PX:rvrx.xx:cvnASUSTeKComputerINC.:ct10:cvrx.x: dmi.product.name: 1001PX dmi.product.version: x.x dmi.sys.vendor: ASUSTeK Computer INC. version.compiz: compiz 1:0.9.12+14.10.20140812-0ubuntu1 version.libdrm2: libdrm2 2.4.56-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.2.6-1ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.2.6-1ubuntu3 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu9 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.914-1~exp1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Mon Sep 1 09:21:40 2014 xserver.configfile: default xserver.errors: intel: Failed to load module "dri3" (module does not exist, 0) intel: Failed to load module "present" (module does not exist, 0) xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id
[Touch-packages] [Bug 1390619] Re: Can't add launcher icon for git gui
I can confirm the "git gui" icon problem. A utility to create a custom icon is an ideal small project for someone looking for something to do. It's not a part of what a desktop shell does, though, and since Unity just follows the Free Desktop standards on .desktop files, useful as a standalone utility without reference to Unity. ** Changed in: unity (Ubuntu) Importance: Undecided => Medium ** Changed in: unity (Ubuntu) Status: Confirmed => Triaged -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1390619 Title: Can't add launcher icon for git gui Status in “unity” package in Ubuntu: Triaged Bug description: This is a usability issue in 2 parts: 1. I would like to add a Launcher icon for git-gui, however when I use the 'Lock to Launcher' option and close the GUI, the launcher icon disappears. 2. There is no easy way to create a custom launcher icon (Creating a .desktop file in a non-obvious location is not an easy way! Not least because I have no idea what icon to use, and the default icon is gly!) I'm assuming my system info is filed with this bug via apport, but just in case, I am on Ubuntu 14.04 (Unity 7) ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.2+14.04.20140714-0ubuntu1.1 ProcVersionSignature: Ubuntu 3.13.0-32.57-lowlatency 3.13.11.4 Uname: Linux 3.13.0-32-lowlatency x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Fri Nov 7 20:47:27 2014 InstallationDate: Installed on 2013-11-03 (368 days ago) InstallationMedia: Ubuntu-Studio 13.10 "Saucy Salamander" - Release amd64 (20131016.1) ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2014-04-26 (195 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1390619/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1187896] Re: Launcher cannot be reached in 'auto-hide' mode with Touchscreen
The gesture for opening the hidden launcher in Unity 7 is a four-finger horizontal swipe (see https://wiki.ubuntu.com/Multitouch for more gestures). This works well on all of my test hardware. We have no plans to retrofit Unity 8 UI designs onto Unity 7. ** Changed in: unity (Ubuntu) Status: Confirmed => Won't Fix ** Changed in: unity Status: New => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1187896 Title: Launcher cannot be reached in 'auto-hide' mode with Touchscreen Status in Unity: Won't Fix Status in “unity” package in Ubuntu: Won't Fix Bug description: Ubuntu 13.04, 3.8.0-24-generic When launcher is in 'auto-hide' mode, it appears to be inaccessible when solely using Touchscreen input to slide, or even tap, the farthest edge of the screen (whether left, or top-left is selected). I've adjusted the sensitivity all the way down to the Highest, but it still does not appear. Instead, it appears to hold focus on whatever application is currently on top. In the situation where no apps are open/near the hotspot, it is assumed I am either simply tapping the desktop, or attempting to drag-highlight a group selection instead. It should be noted that the cursor appears on the far edge, as I would expect typical mouse behavior to emulate bringing the Launcher into view. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1187896/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 750386] Re: compiz crashed with SIGABRT in raise() from abort() from __libc_message() from malloc_printerr() from _int_free()
** Changed in: compiz (Ubuntu) Status: Confirmed => Fix Released ** Changed in: compiz (Ubuntu Quantal) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/750386 Title: compiz crashed with SIGABRT in raise() from abort() from __libc_message() from malloc_printerr() from _int_free() Status in Unity: Fix Released Status in “compiz” package in Ubuntu: Fix Released Status in “unity” package in Ubuntu: Fix Released Status in “compiz” source package in Oneiric: Fix Released Status in “unity” source package in Oneiric: Fix Released Status in “compiz” source package in Quantal: Fix Released Status in “unity” source package in Quantal: Fix Released Bug description: You have landed here because you encountered some heap corruption causing your compiz to crash. Arguably your bug is different to this one, however as most heap corruption is untraceable with regular crash reports and stack traces, it is probably better to leave you bug as a duplicate of this. We will endeavour to fix all possible sources of such heap corruption leading to such a crash over time. Thanks for you understanding. ORIGINAL DESCRIPTION: Binary package hint: compiz Here's an image link: http://img543.imageshack.us/i/screenshotdeesktop.png/ If I deactivate the driver it goes back to normal. ProblemType: Crash DistroRelease: Ubuntu 11.04 Package: compiz-core 1:0.9.4git20110322-0ubuntu5 ProcVersionSignature: Ubuntu 2.6.38-7.39-generic 2.6.38 Uname: Linux 2.6.38-7-generic x86_64 NonfreeKernelModules: wl fglrx Architecture: amd64 Date: Mon Apr 4 11:26:19 2011 DistroCodename: natty DistroVariant: ubuntu ExecutablePath: /usr/bin/compiz InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Alpha amd64 (20110329.1) InstallationMedia_: Ubuntu 11.04 "Natty Narwhal" - Alpha amd64 (20110329.1) ProcCmdline: compiz ProcEnviron: LANGUAGE=en_CA:en LANG=en_CA.UTF-8 SHELL=/bin/bash ProcVersionSignature_: Ubuntu 2.6.38-7.39-generic 2.6.38 Signal: 6 SourcePackage: compiz StacktraceTop: raise () from /lib/x86_64-linux-gnu/libc.so.6 abort () from /lib/x86_64-linux-gnu/libc.so.6 ?? () from /lib/x86_64-linux-gnu/libc.so.6 ?? () from /lib/x86_64-linux-gnu/libc.so.6 free () from /lib/x86_64-linux-gnu/libc.so.6 Title: compiz crashed with SIGABRT in raise() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare XsessionErrors: (:1537): libindicator-WARNING **: Shortcut Group does not have key 'TargetEnvironment' falling back to deprecated use of 'OnlyShowIn' and 'NotShowIn'. (nautilus:1546): GConf-CRITICAL **: gconf_value_free: assertion `value != NULL' failed (:2026): libindicator-WARNING **: Shortcut Group does not have key 'TargetEnvironment' falling back to deprecated use of 'OnlyShowIn' and 'NotShowIn'. version.libgl1-mesa-glx: libgl1-mesa-glx 7.10.1-0ubuntu3 version.xserver-xorg: xserver-xorg 1:7.6+4ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/750386/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1022743] Re: Hardcoded Unity shortcuts responsible for several problems
** Changed in: compiz Milestone: 0.9.11.0 => None -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1022743 Title: Hardcoded Unity shortcuts responsible for several problems Status in Compiz: Opinion Status in Unity: Opinion Status in “unity” package in Ubuntu: Opinion Bug description: 1. All the hardcoded Unity shortcuts (like Alt+Space, Ctrl+Tab or Super+Tab for example) are not shared with Compiz and the CCSM, so it is possible to double-bind the same keycombinations already used by Unity to other functions without CCSM even showing a warning about it... 2. There are conflicts with hardcoded Unity keycombinations, which are still adjustable via CCSM. Example: You are unable to change the shortcut for the Window Menu (Alt+Space), although the option is there (CCSM->General->Key Bindings->Window Menu) Changing the shortcut to anything else makes it snap back to Alt+Space. It is not possible to change the Mouse-shortcut, nor to use Alt+Button3 (Alt+rightMouseButton) for anything else than showing the window menu. Disabling the shortcut is also not possible. 3. If one can not assign hardcoded keybindings/key-mousebindings to anything else and is not able to disable them either, and one wants to use any program that utilizes the same keycombinations/key-mousecombinations (e.g. a game), it would not be possible to play it, because it would always bring up the hardcoded functions, no matter what... Examples: Alt+Space will always bring up the window menu (window accessibility), Alt+Button3 (RMB) also To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/1022743/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1176078] Re: Cannot send file by email using unity dash
I use the System Settings to change my default email client and it works fine, even using the command-line MUA 'mutt'. How were you configuring your default email client? ** Also affects: unity-lens-files Importance: Undecided Status: New ** Changed in: unity Status: New => Invalid ** Also affects: unity-lens-files (Ubuntu) Importance: Undecided Status: New ** Changed in: unity (Ubuntu) Status: Confirmed => Invalid ** Changed in: unity-lens-files Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1176078 Title: Cannot send file by email using unity dash Status in Unity: Invalid Status in Unity Files Lens: Incomplete Status in “unity” package in Ubuntu: Invalid Status in “unity-lens-files” package in Ubuntu: New Bug description: When searching for file using unity dash, and after finding the file, and clicking with the right button of the mouse and select email, nothing happens. This occurs when setting other email client as default other than thunderbird in system settings. Using the thunderbird as default email software, and proceding like described, behaves like expected. i installed the evolution email client and configured as default email client. It sould send email using other email client like evolution other than thunderbird. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: unity 7.0.0daily13.04.18~13.04-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-19.30-generic 3.8.8 Uname: Linux 3.8.0-19-generic x86_64 ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' Date: Fri May 3 17:01:37 2013 InstallationDate: Installed on 2013-05-03 (0 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MarkForUpload: True ProcEnviron: LANGUAGE=pt:pt_BR:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pt_PT.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/1176078/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1332968] Re: unity-panel-service crashed with SIGSEGV in strrchr()
** Information type changed from Private to Public -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1332968 Title: unity-panel-service crashed with SIGSEGV in strrchr() Status in Unity: New Status in “unity” package in Ubuntu: Confirmed Bug description: happens randomly ProblemType: Crash DistroRelease: Ubuntu 14.10 Package: unity-services 7.3.0+14.10.20140619-0ubuntu1 ProcVersionSignature: Ubuntu 3.15.0-6.11-generic 3.15.0 Uname: Linux 3.15.0-6-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.3-0ubuntu2 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,mousepoll,imgpng,grid,snap,gnomecompat,place,move,wall,resize,regex,vpswitch,commands,unitymtgrabhandles,animation,session,expo,ezoom,workarounds,fade,scale,unityshell] CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CrashCounter: 1 CurrentDesktop: Unity Date: Sun Jun 22 14:25:58 2014 DistUpgraded: Fresh install DistroCodename: utopic DistroVariant: ubuntu ExecutablePath: /usr/lib/unity/unity-panel-service GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Madison [Mobility Radeon HD 5650/5750 / 6530M/6550M] [1002:68c1] (prog-if 00 [VGA controller]) Subsystem: Sony Corporation Mobility Radeon HD 5650 [104d:9071] InstallationDate: Installed on 2014-06-01 (20 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140510) Lsusb: Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 0c45:6409 Microdia Webcam Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Sony Corporation VPCEB2C5E ProcCmdline: /usr/lib/unity/unity-panel-service ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.15.0-6-generic root=UUID=c72ec9e3-fe9d-4672-8784-3117789d48f3 ro persistent quiet splash vt.handoff=7 SegvAnalysis: Segfault happened at: 0x7facdfcfe625 : movdqu (%rdi),%xmm0 PC (0x7facdfcfe625) ok source "(%rdi)" (0x) not located in a known VMA region (needed readable region)! destination "%xmm0" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: unity StacktraceTop: strrchr () at ../sysdeps/x86_64/strrchr.S:32 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 ffi_call_unix64 () from /usr/lib/x86_64-linux-gnu/libffi.so.6 Title: unity-panel-service crashed with SIGSEGV in strrchr() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo dmi.bios.date: 07/20/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: R0300Y8 dmi.board.asset.tag: N/A dmi.board.name: VAIO dmi.board.vendor: Sony Corporation dmi.board.version: N/A dmi.chassis.asset.tag: N/A dmi.chassis.type: 10 dmi.chassis.vendor: Sony Corporation dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrR0300Y8:bd07/20/2010:svnSonyCorporation:pnVPCEB2C5E:pvrC605XTV0:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A: dmi.product.name: VPCEB2C5E dmi.product.version: C605XTV0 dmi.sys.vendor: Sony Corporation version.compiz: compiz 1:0.9.11+14.10.20140606-0ubuntu2 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.54-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu5 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-1ubuntu4 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: Sat Jun 21 05:15:14 2014 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: Output HDMI-0 LVDS VGA-0 xserver.version: 2:1.15.1-0ubuntu5 xserver.video_driver: radeon To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1332968/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 984099] Re: compiz crashed with SIGSEGV in g_object_newv() from g_object_new() from g_volume_monitor_get() from unity::launcher::DeviceLauncherSection::DeviceLauncherSection() fr
** Changed in: unity/6.0 Status: New => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/984099 Title: compiz crashed with SIGSEGV in g_object_newv() from g_object_new() from g_volume_monitor_get() from unity::launcher::DeviceLauncherSection::DeviceLauncherSection() from unity::launcher::Controller::Impl::Impl() Status in Unity: Confirmed Status in Unity 5.0 series: New Status in Unity 6.0 series: Won't Fix Status in “unity” package in Ubuntu: Triaged Bug description: I was trying to log in to Unity 3D. I've crashed this way a number of times before -- it's repeatable. I've reported it several times. I've applied all updates to 12.04 as of 12 hours ago. Now, I'm logged in to KDE, since all Unity and all Gnome shells keep crashing. ProblemType: Crash DistroRelease: Ubuntu 12.04 Package: libnux-2.0-0 2.10.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-23.36-generic 3.2.14 Uname: Linux 3.2.0-23-generic x86_64 NonfreeKernelModules: wl fglrx ApportVersion: 2.0.1-0ubuntu4 Architecture: amd64 CrashCounter: 1 Date: Tue Apr 17 05:48:15 2012 ExecutablePath: /usr/bin/compiz InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 (20120201.2) ProcCmdline: compiz ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash Signal: 11 SourcePackage: nux StacktraceTop: ?? () from /usr/lib/gio/modules/libgioremote-volume-monitor.so g_object_newv () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_object_new () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_volume_monitor_get () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 unity::launcher::DeviceLauncherSection::DeviceLauncherSection() () from /usr/lib/compiz/libunityshell.so Title: compiz crashed with SIGSEGV in g_object_newv() 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/unity/+bug/984099/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 981821] Re: compiz crashed with signal 7 in g_settings_get_value() from g_settings_get_strv() from unity::dash::HomeLens::Impl::FindLensPriority() from unity::dash::HomeLens::Imp
** Changed in: unity/6.0 Status: New => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/981821 Title: compiz crashed with signal 7 in g_settings_get_value() from g_settings_get_strv() from unity::dash::HomeLens::Impl::FindLensPriority() from unity::dash::HomeLens::Impl::EnsureCategoryAnnotation() Status in Unity: Confirmed Status in Unity 5.0 series: New Status in Unity 6.0 series: Won't Fix Status in “d-conf” package in Ubuntu: Confirmed Status in “unity” package in Ubuntu: Confirmed Bug description: Running the latest Precise development build with all the updates. I expected no random error, but apport happened to pop up with this one. ProblemType: Crash DistroRelease: Ubuntu 12.04 Package: libunity-core-5.0-5 5.10.0-0ubuntu3 ProcVersionSignature: Ubuntu 3.2.0-23.36-generic 3.2.14 Uname: Linux 3.2.0-23-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.0.1-0ubuntu3 Architecture: amd64 CrashCounter: 1 Date: Sat Apr 14 10:59:33 2012 ExecutablePath: /usr/bin/compiz InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 (20120321) ProcCmdline: compiz ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash Signal: 7 SourcePackage: unity StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/gio/modules/libdconfsettings.so ?? () from /usr/lib/x86_64-linux-gnu/gio/modules/libdconfsettings.so ?? () from /usr/lib/x86_64-linux-gnu/gio/modules/libdconfsettings.so ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 Title: compiz crashed with signal 7 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm lpadmin sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/981821/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1388278] Re: WiFi randomly disconnects and won't connect again
** Changed in: unity Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wireless-tools in Ubuntu. https://bugs.launchpad.net/bugs/1388278 Title: WiFi randomly disconnects and won't connect again Status in Broadcom 802.11 Linux STA driver: New Status in The Linux Kernel: New Status in The Linux Mint Distribution: Confirmed Status in LinuxMint Control Center: New Status in Unity: Invalid Status in Additional Linux Wireless Drivers: Confirmed Status in Wireless Tools - Tools for manipulating Linux Wireless Extensions: New Status in “wireless-tools” package in Ubuntu: Confirmed Bug description: Something odd that I have only seen in Ubuntu, Debian, and derivatives thereof affects something that most of us use every day, and can be a real hassle to beginners from what I've noticed: Many USB WiFi drivers will connect to an access point like usual and after long periods of inactivity on the network combined with user inactivity on the PC alone is when this problem appears to arise: The WiFi disconnects and does not connect again to the same hotspot using the same USB WiFi dongle unless the computer is restarted or reset, and a lot of the time, that doesn't immediately stop this error and even if so, the computer will disconnect yet again not too long from then. And why does this happen? It puzzles me. Maybe it's the USB chipset inside the WiFi dongle, or maybe it's a communication error between the Linux kernel and the automated firewall systems integrated in most routers and base stations today, it's hard to say. What I know is that this doesn't just happen on my computer, testing done by myself on several other computers in different locations using different WiFi hardware on Ubuntu, Debian, Linux Mint, or derivatives thereof gets the exact same result as I am experiencing now. I have gone digging through Debian, Ubuntu, and Linux Mint forums to try and find the "cure" patch for my computer or router and the answer as to why this is happening, and the best answer I could find is that within my system's WiFi Settings, I need to set the BSSID of the hotspot I am current using as the MAC address of the router which that hotspot is transmitting. Upon setting my BSSID to a clone of the Router's MAC address followed by a system restart, I noticed instant improvement when it comes to connection reliability, speed, and time to connect, yet after days of having that MAC as the BSSID, things went back to the usual chaos of an unreliable connection that no other device within the household has encountered, not even Android telephones and tablets that use much of the same underlying Linux code. I performed restarts, updates, more updates, resets, and even more derivatives of Debian or Ubuntu and this is still more of an issue than ever. Via further digging and through a process of trial-and-error, I enabled the "IPv4 is required for this connection" check box along with changing the BSSID to a clone of the router's MAC address in hopes it was a compatibility issue with the "newer" IPv6 Internet Protocol architecture in an attempt to basically 'force' the machine to get that digital handshake with the router in a more 'legacy' mode with IPv4, at least to get some connection. That worked for a bit as well, but didn't hold up just like before. I am now sitting here at my computer, still experiencing this issue on and off, currently having the issue stabilized and stalled at the moment with the "IPv4 is required for this connection" check box on, NO BSSID set, NO cloned MAC address, and NO "Restrict to Device" settings opted-in, hoping this time around this combination of settings will work, but it's a game of trial-and-error for me at this point now, like mentioned before. Has anyone else experienced such terrible connectivity issues only in Debian-based distributions recently? I have been using Linux for ages now and I feel as if this issue is now just arising within the past year, 2014. A HardInfo report generated from my computer is attached to this bug report. I hope we can figure out a solution soon to get pushed to all Debian and Debian-like distros soon! Nobody wants a bad connection. Current OS: Linux Mint 17 "Qiana" Kernel: Linux 3.13.0-24-generic (x86_64) Processor: AMD Phenom II X4 (850) RAM: 8GB DDR3 IWLIST OUTPUT: jeb@MINT-PARTITION:~ > sudo iwlist wlan0 scan [sudo] password for jeb: wlan0 Scan completed : Cell 01 - Address: F8:7B:8C:06:57:8D Channel:6 Frequency:2.437 GHz (Channel 6) Quality=60/70 Signal level=-50 dBm Encryption key:on ESSID:"Belkin-EXT" Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 6 Mb/s
[Touch-packages] [Bug 123920] Re: Bluetooth Logitech Dinovo Keyboard/Mouse don't work
** Changed in: unity Status: Confirmed => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/123920 Title: Bluetooth Logitech Dinovo Keyboard/Mouse don't work Status in Bluez Utilities: New Status in Bluez-utils - bluez-bcm203x, bluez-pcmcia-support, bluez-cups, bluez-utils: New Status in The Linux Mint Distribution: New Status in Unity: Invalid Status in “bluez” package in Ubuntu: Triaged Status in “linux” package in Ubuntu: Invalid Status in “linux-source-2.6.22” package in Ubuntu: Won't Fix Status in “udev” package in Ubuntu: Invalid Bug description: Testing Gutsy Gibbon Tribe 2 LiveCD and bluetooth keyboard and mouse will work until Nautilus starts. After Nautilus starts the keyboard and mouse are unresponsive and do not work. I tried reconnecting the keyboard and mouse by using the discovery buttons on both the Bluetooth Dongle and Input device. The problem still persists. Using Intel P4 2.8 Ghz Processor, 3 GB ddr400 ram, Intel D875PBZ motherboard. Logitech Dinovo media keyboard and mx1000 laser bluetooth mouse, with logitech mini bluetooth receiver. To manage notifications about this bug go to: https://bugs.launchpad.net/bluez/+bug/123920/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1386114] Re: compiz crashed with SIGABRT in __libc_message()
** Information type changed from Private to Public -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1386114 Title: compiz crashed with SIGABRT in __libc_message() Status in Unity: Confirmed Status in “unity” package in Ubuntu: Confirmed Bug description: apparently random crash soon after logging in ProblemType: Crash 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 CurrentDesktop: Unity Date: Mon Oct 27 09:58:31 2014 ExecutablePath: /usr/bin/compiz ProcCmdline: compiz ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash Signal: 6 SourcePackage: unity StacktraceTop: __libc_message (do_abort=do_abort@entry=1, fmt=fmt@entry=0x7fc9f533a668 "*** Error in `%s': %s: 0x%s ***\n") at ../sysdeps/posix/libc_fatal.c:175 malloc_printerr (ptr=, str=0x7fc9f533a830 "double free or corruption (fasttop)", action=1) at malloc.c:4996 _int_free (av=, p=, have_lock=0) at malloc.c:3840 ft_glyphslot_free_bitmap () 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 SIGABRT in __libc_message() UpgradeStatus: Upgraded to trusty on 2014-05-07 (172 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo wireshark www-data To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1386114/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1386114] Re: compiz crashed with SIGABRT in __libc_message()
** Changed in: unity Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1386114 Title: compiz crashed with SIGABRT in __libc_message() Status in Unity: Confirmed Status in “unity” package in Ubuntu: Confirmed Bug description: apparently random crash soon after logging in ProblemType: Crash 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 CurrentDesktop: Unity Date: Mon Oct 27 09:58:31 2014 ExecutablePath: /usr/bin/compiz ProcCmdline: compiz ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash Signal: 6 SourcePackage: unity StacktraceTop: __libc_message (do_abort=do_abort@entry=1, fmt=fmt@entry=0x7fc9f533a668 "*** Error in `%s': %s: 0x%s ***\n") at ../sysdeps/posix/libc_fatal.c:175 malloc_printerr (ptr=, str=0x7fc9f533a830 "double free or corruption (fasttop)", action=1) at malloc.c:4996 _int_free (av=, p=, have_lock=0) at malloc.c:3840 ft_glyphslot_free_bitmap () 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 SIGABRT in __libc_message() UpgradeStatus: Upgraded to trusty on 2014-05-07 (172 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo wireshark www-data To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1386114/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1385413] Re: unity_support_test has stopped unexpectedly
Stacktrace shows a crash in the VirtualBox video driver. I strongly suspect a problem in the VirtualBox video driver. ** Changed in: unity Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1385413 Title: unity_support_test has stopped unexpectedly Status in Unity: Confirmed Status in “unity” package in Ubuntu: Confirmed Status in “virtualbox” package in Ubuntu: Confirmed Bug description: Performed the upgrade from Trusty to Utopic, after the required restart of the computer the 'Report a problem' dialog poped up saying that unity_support_test has stopped unexpectedly. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: unity 7.3.1+14.10.20141016-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-23.31-generic 3.16.4 Uname: Linux 3.16.0-23-generic i686 .tmp.unity.support.test.1: ApportVersion: 2.14.7-0ubuntu8 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Fri Oct 24 18:27:07 2014 DistUpgraded: 2014-10-24 17:54:14,577 DEBUG enabling apt cron job DistroCodename: utopic DistroVariant: ubuntu DkmsStatus: virtualbox-guest, 4.3.18, 3.16.0-23-generic, i686: installed GraphicsCard: InnoTek Systemberatung GmbH VirtualBox Graphics Adapter [80ee:beef] (prog-if 00 [VGA controller]) InstallationDate: Installed on 2014-09-25 (29 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release i386 (20140722.2) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: innotek GmbH VirtualBox ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-23-generic root=UUID=664043af-2956-48b2-baca-3609d1ee45c3 ro quiet splash vt.handoff=7 Renderer: Software SourcePackage: unity UnitySupportTest: Error: command ['/usr/lib/nux/unity_support_test', '-p', '-f'] failed with exit code -11: libGL error: pci id for fd 4: 80ee:beef, driver (null) OpenGL Warning: Assertion failed: thread && thread->netServer.conn && thread->netServer.conn->type==CR_VBOXHGCM && thread->bInjectThread, file /mnt/tinderbox/add-4.3/src/VBox/Additions/common/crOpenGL/pack/packspu_misc.c, line 562 UpgradeStatus: Upgraded to utopic on 2014-10-24 (0 days ago) dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH version.compiz: compiz 1:0.9.12+14.10.20140918-0ubuntu1 version.libdrm2: libdrm2 2.4.56-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.0-0ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.3.0-0ubuntu3 version.xserver-xorg-core: xserver-xorg-core 2:1.16.0-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.914-1~exp1ubuntu4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2 xserver.bootTime: Fri Oct 24 18:18:10 2014 xserver.configfile: default xserver.errors: AIGLX error: vboxvideo does not export required DRI extension AIGLX: reverting to software rendering xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.16.0-1ubuntu1 xserver.video_driver: vboxvideo To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1385413/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1184159] Re: [saucy] scrolling with a touchpad is jerky with bindings set in compiz for Desktop-based Viewport Switching
** Changed in: compiz Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1184159 Title: [saucy] scrolling with a touchpad is jerky with bindings set in compiz for Desktop-based Viewport Switching Status in Compiz: Fix Released Status in GTK+ GUI Toolkit: Fix Released Status in X.Org X server: Confirmed Status in “compiz” package in Ubuntu: Fix Released Status in “gtk+3.0” package in Ubuntu: Fix Released Status in “xorg-server” package in Ubuntu: Won't Fix Bug description: Hello, Scrolling with a touchpad is now a bit jerky. It's exactly the same bug than bug #1171156 introduced in Raring by an upstream's patch in order to fix bug #1046988 (which was tracked by upstream there: https://bugzilla.gnome.org/show_bug.cgi?id=690275 ) * Impact: Up & down scrolling with a touchpad is now a bit jerky, seen best with gedit in large files though also seems to affect nautilus & in general. * Testcase: Set any bindings in Viewport Switcher > Desktop-based Viewport switching try scrolling in long documents in gedit using a touchpad, is scrolling "jerky"? * Videos: Before: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1171156/+attachment/3650661/+files/gtk_scroll_1171156_without_patch.ogv After: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1171156/+attachment/3650662/+files/gtk_scroll_1171156_with_patch.ogv * Note: It seems this bug doesn't affect Gnome-Shell session: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1171156/comments/10 ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: libgtk-3-0 3.8.2-0ubuntu1 ProcVersionSignature: Ubuntu 3.9.0-2.7-generic 3.9.3 Uname: Linux 3.9.0-2-generic x86_64 ApportVersion: 2.10.2-0ubuntu1 Architecture: amd64 Date: Sat May 25 17:44:01 2013 InstallationDate: Installed on 2011-08-10 (653 days ago) InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Alpha amd64 (20110803.1) MarkForUpload: True SourcePackage: gtk+3.0 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/1184159/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1280616] Re: When launcher is in autohide mode the launcher icons are not clickable
** Changed in: compiz Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1280616 Title: When launcher is in autohide mode the launcher icons are not clickable Status in Compiz: Fix Released Status in Unity: Fix Released Status in “compiz” package in Ubuntu: Fix Released Status in “unity” package in Ubuntu: Fix Released Bug description: Setting the launcher in autohide, then it's not possible to click on launcher items when the spread is open (it's terminated instead). Also the spreaded windows doesn't take in consideration the size of launcher as x offset. To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/1280616/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 727904] Re: Launcher, Window management - Switching between spreads when dragging a file over the Launcher is broken
** Changed in: compiz/0.9.11 Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/727904 Title: Launcher, Window management - Switching between spreads when dragging a file over the Launcher is broken Status in Ayatana Design: Fix Committed Status in Compiz: Fix Released Status in Compiz 0.9.11 series: Fix Released Status in Unity: Invalid Status in “compiz” package in Ubuntu: Fix Released Status in “unity” package in Ubuntu: Invalid Status in “compiz” source package in Trusty: Fix Released Status in “unity” source package in Trusty: Invalid Bug description: To reproduce: Open two Chrome windows and two Firefox windows. Drag a .html file over the Chrome icon in the Launcher. A spread of the two Chrome windows should appear. Then continue the same drag, and drag the file over the Firefox icon in the Launcher. Nothing happens, the Chrome spread is still displayed. Desired behaviour; After a spread appears as a result of the user dragging a file over a application icon in the Launcher, if the user then drags the file over a different application icon (where the application is also a valid drop receptacle for the file type) the spread should switch to the newly selected application. To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/727904/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 607796] Re: Launcher, Window management - Dragging and holding a selection over an entry in the Launcher should spread out windows belonging to that application
** Changed in: compiz/0.9.11 Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/607796 Title: Launcher, Window management - Dragging and holding a selection over an entry in the Launcher should spread out windows belonging to that application Status in Ayatana Design: Fix Committed Status in Compiz: Fix Released Status in Compiz 0.9.11 series: Fix Released Status in One Hundred Papercuts: Fix Released Status in Unity: Fix Released Status in Unity 7.2 series: Fix Released Status in “compiz” package in Ubuntu: Fix Released Status in “unity” package in Ubuntu: Fix Released Status in “compiz” source package in Trusty: Fix Released Status in “unity” source package in Trusty: Fix Released Bug description: [Impact] If the user drags and hold a file over a running application in the Launcher, all the windows of that application should be shown with the spread. The user should then be able to drag and drop the file in a windows in the spread to load the file into that specific window. [Test Case] 1) Open two windows instances of the same application (say firefox) 2) Drag a file from the file-manager or the desktop and hover the firefox icon 3) After one second the firefox icon is hovered, the spread will occur 4) You should be able to hover one of the firefox windows and it should show a spinner, after 750ms (by default) the hovered windows should be focused and raised 5) You should now be able to drop the content you're dragging (if the selected application supports that content). [Regression Potential] This codepath was mostly disabled in the current compiz and unity code because it was buggy, so the regression potential is very low, although it might happen that, if some race-condition happens, when closing the scale the launcher might be still painted as if it would be in scale mode (desaturated) even if it's not the case anymore. *** SRU debdiff links *** The Unity SRU debdiff for this can be found at https://launchpadlibrarian.net/180013321/unity-7.2.2-trusty-sru.debdiff. The Compiz SRU debdiff for this can be found at https://launchpadlibrarian.net/180013356/compiz-0.9.11.2-trusty- sru.debdiff ### Bug #727903 needs to be fixed at the same time. --- History: This bug had been previously fixed as "buggybutclosed" for Unity on 2011-04-18, leaving this function with other bugs: https://bugs.launchpad.net/ayatana-design/+bug/727903 https://bugs.launchpad.net/ayatana-design/+bug/727904 https://bugs.launchpad.net/ayatana-design/+bug/727902 https://bugs.launchpad.net/ayatana-design/+bug/764424 https://bugs.launchpad.net/ayatana-design/+bug/832988 On 2011-10-18, it was reopened for regression in Oneiric. To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/607796/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 766191] Re: Spread causes Compiz's 'scale' plugin to inaccurately pad the right/left edges of the screen
** Changed in: compiz Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/766191 Title: Spread causes Compiz's 'scale' plugin to inaccurately pad the right/left edges of the screen Status in Ayatana Design: Fix Committed Status in Compiz: Fix Released Status in Unity: Fix Released Status in “compiz” package in Ubuntu: Fix Released Status in “unity” package in Ubuntu: Fix Released Bug description: When using Unity with two windows of the same size open, activating compiz's 'scale' causes inconsistent padding at either sides of the screen. This is because the scale plugin does not factor the Unity launcher's width into the calculations; therefore, the left edge of the screen has less padding than the right edge. The problem detailed with measurement: https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/766191/+attachment/2457195/+files/pic1.png I think scaling should be done considering the screen width minus the dock width. This may seem very tricky to pull out since scale is a compiz plugin and so on, but, again, like it is and when windows get under the dock, it feels strange. Cheers. To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/766191/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 992697] Re: Window management - 'Ctrl-Alt-Numpad 4' and 'Ctrl-Alt-Numpad 6' window placement shortcuts are broken
** Changed in: compiz Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/992697 Title: Window management - 'Ctrl-Alt-Numpad 4' and 'Ctrl-Alt-Numpad 6' window placement shortcuts are broken Status in Autopilot: Fix Released Status in Ayatana Design: Fix Committed Status in Compiz: Fix Released Status in Compiz 0.9.10 series: Fix Committed Status in Unity: Fix Released Status in “autopilot” package in Ubuntu: Fix Released Status in “compiz” package in Ubuntu: Fix Released Status in “unity” package in Ubuntu: Fix Released Bug description: The "Ctrl + Alt + numpad 4" and "Ctrl + Alt + numpad 6" keyboard shortcuts are not working in 13.04. See bug #878820 for the full specification of the numpad window placement shortcuts. Quoting from this bug: "Ctrl-Alt-Numpad 4 - Place window on the left side of the screen in *semi-maximised* state (it is important that the window is actually semi-maximised, not just the same size and position as a semi- maximised window) Pressing a second time does nothing. Ctrl-Alt-Numpad 6 - Place window on the right side of the screen (it is important that the window is actually semi-maximised, not just the same size and position as a semi-maximised window). Pressing a second time does nothing." HOWTO: The solution we want here are additional shortcuts to semi-maximize windows vertically and move them to left/right half of the screen... The best way to achieve that: 1. Remove the changing of the standard shortcuts by debian/patches/ubuntu-config.patch, so the original ones will work again. 2. Add 2 quasi-duplicated shortcuts with the functions to semi-maximize windows vertically and move them to left/right half of the screen to Grid and make those functions use "Ctrl + Super + Cursor Left or Right" on Ubuntu. To manage notifications about this bug go to: https://bugs.launchpad.net/autopilot/+bug/992697/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1104236] Re: [regression] Unity show desktop fade out makes them invisible in spread.
** Changed in: compiz Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1104236 Title: [regression] Unity show desktop fade out makes them invisible in spread. Status in Compiz: Fix Released Status in Unity: Fix Released 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/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1171342] Re: mouse scroll wheel not working in gedit & System Monitor
** Changed in: compiz Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1171342 Title: mouse scroll wheel not working in gedit & System Monitor Status in Compiz: Fix Released Status in GTK+ GUI Toolkit: Fix Released Status in X.Org X server: Confirmed Status in “compiz” package in Ubuntu: Fix Released Status in “gtk+3.0” package in Ubuntu: Fix Released Status in “xorg-server” package in Ubuntu: Won't Fix Bug description: Open System Monitor Using mouse wheel button - scroll up or down - list does not move. If Press the wheel button and then scroll up or down the list will move. This also occurs in Gedit. Firefox and Terminal work as expected. IE do not need to press the wheel and then scroll Linux kylea-hpxt 3.8.0-19-generic #29-Ubuntu SMP Wed Apr 17 18:16:28 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux Description: Ubuntu 13.04 Release: 13.04 To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/1171342/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1200829] Re: Regression: Enabling typical bindings in "Desktop-based Viewport Switching" breaks scrollwheel scrolling in some windows with a usb mouse on a laptop
** Changed in: compiz Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1200829 Title: Regression: Enabling typical bindings in "Desktop-based Viewport Switching" breaks scrollwheel scrolling in some windows with a usb mouse on a laptop Status in Compiz: Fix Released Status in GTK+ GUI Toolkit: Fix Released Status in X.Org X server: Confirmed Status in “compiz” package in Ubuntu: Fix Released Status in “gtk+3.0” package in Ubuntu: Fix Released Status in “xorg-server” package in Ubuntu: Won't Fix Bug description: Test Case: On a laptop connect a usb mouse (using a logitech wireless "Anywhere mouse mx" here Enable theses Desktop-based Viewport Switching binding's Set prev & next to typical settings, (next = button 5, prev = button 4 Try to scroll in any of these windows using the mouse scroll-wheel - nautilus gedit synaptic dconf-editor help (Ubuntu Desktop guide Software-updater > details 'Open files' window sidebar windows in RB & totem preferences in audacious There could be a few more On the other hand many others work ok, short list - Dash Scroll on Desktop gnome-terminal libreoffice-writer ccsm all browsers preferences & playlist in vlc Note all of the no scroll apps work fine with touchpad scrolling Have tried disabling the touchpad, ect. to no avail Related to this bug, same workaround to alleviate https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1184159 Commit reverted packages for 13.10 are here https://launchpad.net/~mc3man/+archive/test-scroll ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: compiz 1:0.9.9~daily13.04.18.1~13.04-0ubuntu1 ProcVersionSignature: Ubuntu 3.10.0-2.10-generic 3.10.0 Uname: Linux 3.10.0-2-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.10.2-0ubuntu4 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 Date: Fri Jul 12 23:46:16 2013 DistUpgraded: Fresh install DistroCodename: saucy DistroVariant: ubuntu GraphicsCard: NVIDIA Corporation G86M [GeForce 8400M GS] [10de:0427] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0209] InstallationDate: Installed on 2013-06-23 (20 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130621) MachineType: Dell Inc. XPS M1330 MarkForUpload: True PackageArchitecture: all ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.10.0-2-generic root=UUID=c6ab7418-5252-48e1-b7ab-cc21291285f4 ro quiet splash SourcePackage: compiz UpgradeStatus: No upgrade log present (probably fresh install) XorgConf: Section "Device" Identifier "My Graphics" Driver "nouveau" Option "GLXVBlank" "on" EndSection dmi.bios.date: 12/26/2008 dmi.bios.vendor: Dell Inc. dmi.bios.version: A15 dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA15:bd12/26/2008:svnDellInc.:pnXPSM1330:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: XPS M1330 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.9~daily13.04.18.1~13.04-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.45-2ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.1.4-0ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.1.4-0ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.14.1-0ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu3.1 version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.8-0ubuntu1.1 To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/1200829/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1240957] Re: Scrolling behaviour and window focus has changed and is inconsistent
** Changed in: compiz Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1240957 Title: Scrolling behaviour and window focus has changed and is inconsistent Status in Compiz: Fix Released Status in GTK+ GUI Toolkit: Fix Released Status in X.Org X server: Confirmed Status in “compiz” package in Ubuntu: Fix Released Status in “gtk+3.0” package in Ubuntu: Fix Released Status in “xorg-server” package in Ubuntu: Won't Fix Bug description: I wasn't sure which package to file this bug against, but seeing as it's a general desktop usability/consistency bug, the top level desktop environment seemed like a good target. On Ubuntu 13.10, AMD64, everything default (Unity 7 on X.org etc), except for installing nvidia-319-updates, all current packages as of now (2013-10-17; unity 7.1.2+13.10.20131014.1-0ubuntu1), I now have this behaviour which is different from Ubuntu versions up to 13.04, and, is also inconsistent within itself. Here's what I've found: The scrolling behaviour has changed, and seems to be different per application in Ubuntu 13.10. The old behaviour (up to 13.04): mouse pointer above window would allow scrolling, regardless of focus Apps that use the old behaviour: libreoffice, firefox, gnome-terminal The new behaviour (13.10): window must be focused, and pointer hovered above to allow scrolling Apps that use the new behaviour: nautilus, gedit, ubuntu-bug, software-updater STEPS TO REPRODUCE 1. Open gEdit, press enter until the window is scrollable. 2. Open Firefox, go to a webpage that's scrollable. 3. Place gEdit above Firefox but off to the right side so gEdit's scrollbar is still visible, have gEdit focused. 4. Position mouse pointer above gEdit, observe scrollwheel causes gEdit window to scroll. 5. Move mouse pointer above Firefox but do not focus Firefox, observe scrollwheel causes Firefox window to scroll. 6. Focus Firefox, leave pointer above Firefox, observe scrollwheel causes Firefox window to scroll 7. Move mouse pointer above gEdit but do not focus gEdit, observe scrollwheel FAILS to cause gEdit window to scroll. This behaviour is the same with any combination of the above apps (libreoffice, firefox, gnome-terminal all scrollable as long as pointer is above them; nautilus, gedit, software-updater, ubunut-bug will not scroll unless focused *and* have pointer above them) What *SHOULD* happen, is that any window will scroll as long as the pointer is above it. That's how it's always been in Ubuntu. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: unity 7.1.2+13.10.20131014.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.12.5-0ubuntu2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' Date: Thu Oct 17 22:12:18 2013 InstallationDate: Installed on 2013-09-30 (17 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Beta amd64 (20130925.1) MarkForUpload: True SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/1240957/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1281370] Re: Unity should use "Normal" resize mode by default
** Changed in: compiz Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1281370 Title: Unity should use "Normal" resize mode by default Status in Compiz: Fix Released Status in Unity: Fix Released Status in “compiz” package in Ubuntu: Fix Released Status in “unity” package in Ubuntu: Fix Released Bug description: Unity resize mode should be use "live" resizing mode by default, as said by designers after testing it with new unity decorations: 16:38:04 I just tested the live resizing 16:38:12 it works great! 16:38:19 at long, long last, great to have it back 16:38:28 +1 to switch on by default To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/1281370/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 607796] Re: Launcher, Window management - Dragging and holding a selection over an entry in the Launcher should spread out windows belonging to that application
** Changed in: compiz Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/607796 Title: Launcher, Window management - Dragging and holding a selection over an entry in the Launcher should spread out windows belonging to that application Status in Ayatana Design: Fix Committed Status in Compiz: Fix Released Status in Compiz 0.9.11 series: Fix Committed Status in One Hundred Papercuts: Fix Released Status in Unity: Fix Released Status in Unity 7.2 series: Fix Released Status in “compiz” package in Ubuntu: Fix Released Status in “unity” package in Ubuntu: Fix Released Status in “compiz” source package in Trusty: Fix Released Status in “unity” source package in Trusty: Fix Released Bug description: [Impact] If the user drags and hold a file over a running application in the Launcher, all the windows of that application should be shown with the spread. The user should then be able to drag and drop the file in a windows in the spread to load the file into that specific window. [Test Case] 1) Open two windows instances of the same application (say firefox) 2) Drag a file from the file-manager or the desktop and hover the firefox icon 3) After one second the firefox icon is hovered, the spread will occur 4) You should be able to hover one of the firefox windows and it should show a spinner, after 750ms (by default) the hovered windows should be focused and raised 5) You should now be able to drop the content you're dragging (if the selected application supports that content). [Regression Potential] This codepath was mostly disabled in the current compiz and unity code because it was buggy, so the regression potential is very low, although it might happen that, if some race-condition happens, when closing the scale the launcher might be still painted as if it would be in scale mode (desaturated) even if it's not the case anymore. *** SRU debdiff links *** The Unity SRU debdiff for this can be found at https://launchpadlibrarian.net/180013321/unity-7.2.2-trusty-sru.debdiff. The Compiz SRU debdiff for this can be found at https://launchpadlibrarian.net/180013356/compiz-0.9.11.2-trusty- sru.debdiff ### Bug #727903 needs to be fixed at the same time. --- History: This bug had been previously fixed as "buggybutclosed" for Unity on 2011-04-18, leaving this function with other bugs: https://bugs.launchpad.net/ayatana-design/+bug/727903 https://bugs.launchpad.net/ayatana-design/+bug/727904 https://bugs.launchpad.net/ayatana-design/+bug/727902 https://bugs.launchpad.net/ayatana-design/+bug/764424 https://bugs.launchpad.net/ayatana-design/+bug/832988 On 2011-10-18, it was reopened for regression in Oneiric. To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/607796/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 727904] Re: Launcher, Window management - Switching between spreads when dragging a file over the Launcher is broken
** Changed in: compiz Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/727904 Title: Launcher, Window management - Switching between spreads when dragging a file over the Launcher is broken Status in Ayatana Design: Fix Committed Status in Compiz: Fix Released Status in Compiz 0.9.11 series: Fix Committed Status in Unity: Invalid Status in “compiz” package in Ubuntu: Fix Released Status in “unity” package in Ubuntu: Invalid Status in “compiz” source package in Trusty: Fix Released Status in “unity” source package in Trusty: Invalid Bug description: To reproduce: Open two Chrome windows and two Firefox windows. Drag a .html file over the Chrome icon in the Launcher. A spread of the two Chrome windows should appear. Then continue the same drag, and drag the file over the Firefox icon in the Launcher. Nothing happens, the Chrome spread is still displayed. Desired behaviour; After a spread appears as a result of the user dragging a file over a application icon in the Launcher, if the user then drags the file over a different application icon (where the application is also a valid drop receptacle for the file type) the spread should switch to the newly selected application. To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/727904/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1305586] Re: Lock screen is unusable when some windows have a keyboard/mouse grab
** Changed in: compiz Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1305586 Title: Lock screen is unusable when some windows have a keyboard/mouse grab Status in Compiz: Fix Released Status in Compiz 0.9.11 series: Fix Released Status in Unity: Fix Released Status in Unity 7.2 series: Fix Released Status in “compiz” package in Ubuntu: Fix Released Status in “unity” package in Ubuntu: Fix Released Status in “compiz” source package in Trusty: Fix Released Status in “unity” source package in Trusty: Fix Released Bug description: [Impact] Some windows will grab the keyboard/mouse and when the lockscreen kicks in, this window will still have the grab and thusly, you can't enter your password in the lockscreen. [Test case] This will work only in the case that your lockscreen is set (from unity control center, lock pane) to lock immediately (when screen turns off). 1. Open a window that will hold the grab, such as the ssh password dialog or a virtual machine (such as virtualbox in fullscreen). 2. Wait for the lock screen to activate [1]. 3. The screen won't be locked, since it's not possible to steal drag to another window. [Regression potential] For the same reason of lp:49579, we can't lock the screen (yet) if something takes the grab in X, or we won't able to get input back. This is not a regression because it has never been possible in Ubuntu before, while when we tried that, it caused this bug. A possible source of regression might be that we now try to grab/ungrab the screen (the only X reliable way for grab checking), when showing the dash/hud or the lockscreen itself, and this might slow things down a little, but from measurements done this slow down is generally about 2ms, so nothing to worry about. * Compiz Debdiff is found at https://launchpadlibrarian.net/178439518/compiz-trusty-sru-2.debdiff * [1] You can use this to reduce the locking delay: gsettings set org.gnome.desktop.session idle-delay 5 and resetting it with: gsettings reset org.gnome.desktop.session idle-delay --- Original Description: My screen just timed out and locked when a password prompt which had a grab was displaying. I couldn't type my password or interact with the indicators. gnome-screensaver just refuses to lock in this situation, perhaps unity could do the same unless it's possible to remove and readd the grabs yourself, but I don't think XLib lets you do that (you can only remove your own grabs AFAIK). TEMPORARY WORKAROUND TO LOGIN AGAIN: Click on the guest session Once the guest session is started log out This takes you back to the lightdm session screen you can then login to your user session and it be in the same state ProblemType: BugDistroRelease: Ubuntu 14.04 Package: unity 7.2.0+14.04.20140409-0ubuntu1 [origin: unknown] 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' CrashDB: unity CurrentDesktop: Unity Date: Thu Apr 10 09:39:45 2014 InstallationDate: Installed on 2012-10-07 (549 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Beta amd64 (20121007)SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2013-05-07 (338 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/1305586/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1243233] Re: Holding Super key doesn't bring up shortcut overlay.
Yes, please file a new bug about the shortcuts screen not displaying on localized installations due to display size limitations. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1243233 Title: Holding Super key doesn't bring up shortcut overlay. Status in Unity: Fix Released Status in “unity” package in Ubuntu: Fix Released Bug description: After upgrading from 13.04 to 13.10, holding Super no longer brings up the help overlay. Holding Super worked before upgrading. Tapping the Super key still brings up the HUD, and holding it down still brings up the Launcher and after a second or so shows the numbers on the applications. In Compiz Config Manager, under Ubuntu Unity Plugin -> Launcher, the Key to show the Dash, Launcher and Help Overlay is set to Super. Under Ubuntu Unity Plugin -> General, Enable Shortcut Hints Overlay is checked. This is also known to affect 14.04 (without compiz) when workspaces are enabled and screen resolution is 1024x768. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1243233/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1299054] Re: resizing loop on high-dpi screen
I get this every time I click on the "show details" button of the "application has crashed" dialog that pops up when I log in. If you need an example. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1299054 Title: resizing loop on high-dpi screen Status in Unity: New Status in “unity” package in Ubuntu: Confirmed Bug description: When the global scaling factor is set to 2, some dialogs occasionally start changing their window size causing very high CPU activity. This occurs for example in dconf-editor while searching: It appears dconf-editor tries to adjust the window dimensions to the size of the content and reduces the window size until it is unusable. This causes very high CPU activity and freezes the window content. It also happens when (then) resizing the window width (→) or height (↓) afterwards, it tries to revert to the previous window size. However, the only way to resize the window back so that it doesn't reduce its size is by dragging the window corner (↓→). This issue happens also in other applications, for example in apport- dialogs when expanding the collapsed details view. This does not happen when the global scaling factor is set to 1. It could be related to the new window resizing method that updates the window content. org.gnome.desktop.interface.scaling-factor = 2 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.1.2+14.04.20140321-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-17.37-generic 3.13.6 Uname: Linux 3.13.0-17-generic x86_64 ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Fri Mar 28 16:07:47 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2014-02-02 (53 days ago) InstallationMedia: Ubuntu-GNOME 14.04 "Trusty Tahr" - Alpha amd64 (20140201) SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1299054/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1299054] Re: resizing loop on high-dpi screen
Oh, and my scaling is set to 1.88, so it's not related to the GTK scaling >= 2 problems. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1299054 Title: resizing loop on high-dpi screen Status in Unity: New Status in “unity” package in Ubuntu: Confirmed Bug description: When the global scaling factor is set to 2, some dialogs occasionally start changing their window size causing very high CPU activity. This occurs for example in dconf-editor while searching: It appears dconf-editor tries to adjust the window dimensions to the size of the content and reduces the window size until it is unusable. This causes very high CPU activity and freezes the window content. It also happens when (then) resizing the window width (→) or height (↓) afterwards, it tries to revert to the previous window size. However, the only way to resize the window back so that it doesn't reduce its size is by dragging the window corner (↓→). This issue happens also in other applications, for example in apport- dialogs when expanding the collapsed details view. This does not happen when the global scaling factor is set to 1. It could be related to the new window resizing method that updates the window content. org.gnome.desktop.interface.scaling-factor = 2 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.1.2+14.04.20140321-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-17.37-generic 3.13.6 Uname: Linux 3.13.0-17-generic x86_64 ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Fri Mar 28 16:07:47 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2014-02-02 (53 days ago) InstallationMedia: Ubuntu-GNOME 14.04 "Trusty Tahr" - Alpha amd64 (20140201) SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1299054/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1055166] Re: compiz crashed with SIGSEGV in memmove() from drisw_update_tex_buffer() from dri_set_tex_buffer2() from operator() from compiz::opengl::bindTexImageGLX() from ... fr
** Changed in: compiz Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1055166 Title: compiz crashed with SIGSEGV in memmove() from drisw_update_tex_buffer() from dri_set_tex_buffer2() from operator() from compiz::opengl::bindTexImageGLX() from ... from unity::UnityWindow::DrawWindowDecoration Status in Compiz: Fix Released Status in Mesa: Invalid Status in Unity: Invalid Status in Unity 6.0 series: Won't Fix Status in “compiz” package in Ubuntu: Fix Released Status in “mesa” package in Ubuntu: Invalid Status in “unity” package in Ubuntu: Invalid Bug description: See also bug 927168, which was resolved recently. Compiz crashed after installed something via Synaptic and just it installed that i want it crashed coz i want to see the black installition screen ProblemType: Crash DistroRelease: Ubuntu 12.10 Package: unity 6.6.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.5.0-15.22-generic 3.5.4 Uname: Linux 3.5.0-15-generic x86_64 ApportVersion: 2.5.2-0ubuntu4 Architecture: amd64 Date: Sun Sep 23 21:36:37 2012 ExecutablePath: /usr/bin/compiz InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha amd64 (20120905.2) ProcCmdline: compiz ProcEnviron: PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7f031d57d73c:movntdq %xmm1,-0x10(%rdi) PC (0x7f031d57d73c) ok source "%xmm1" ok destination "-0x10(%rdi)" (0x108d5b170) not located in a known VMA region (needed writable region)! SegvReason: writing unknown VMA Signal: 11 SourcePackage: unity StacktraceTop: ?? () from /lib/x86_64-linux-gnu/libc.so.6 ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so compiz::opengl::bindTexImageGLX(ServerGrabInterface*, unsigned long, unsigned long, boost::function const&, boost::function const&, boost::function const&, compiz::opengl::_PixmapSource) () from /usr/lib/compiz/libopengl.so TfpTexture::bindTexImage(unsigned long const&) () from /usr/lib/compiz/libopengl.so Title: compiz crashed with SIGSEGV in compiz::opengl::bindTexImageGLX() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo XsessionErrors: gnome-session[1561]: WARNING: Application 'compiz.desktop' killed by signal 11 gnome-session[1561]: WARNING: App 'compiz.desktop' respawning too quickly gnome-session[1561]: CRITICAL: We failed, but the fail whale is dead. Sorry To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/1055166/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1204664] Re: control+super+d works just the first time running Ubuntu Unity.
** Changed in: compiz Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1204664 Title: control+super+d works just the first time running Ubuntu Unity. Status in Compiz: Fix Released Status in Unity: Fix Released Status in “compiz” package in Ubuntu: Fix Released Status in “unity” package in Ubuntu: Fix Released Status in “compiz” source package in Raring: New Bug description: Control+Super+D works just the first time cauisng 9/10 failures in AP. To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/1204664/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1234624] Re: Spread - In the spread view, clicking on an empty space should perform the same action as pressing the ESC key
** Changed in: compiz Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1234624 Title: Spread - In the spread view, clicking on an empty space should perform the same action as pressing the ESC key Status in Ayatana Design: Fix Committed Status in Compiz: Fix Released Status in Unity: Invalid Status in “compiz” package in Ubuntu: Fix Released Status in “unity” package in Ubuntu: Invalid Bug description: In the spread view, clicking on an empty space (e.g. anywhere that is not a window or the launcher) should perform the same action as pressing the ESC key and should exit the spread. To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/1234624/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 742028] Re: compiz crashed with SIGSEGV in CompWindow::id()
** Changed in: compiz Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/742028 Title: compiz crashed with SIGSEGV in CompWindow::id() Status in Compiz: Fix Released Status in Unity: Fix Released Status in “unity” package in Ubuntu: Fix Released Bug description: Binary package hint: unity compiz crashes every time "SAOImage DS9" is called directly from a terminal or indirectly by other programs. Window content stays in place, icons, program bars disappear. Keyboard shortcuts no longer work. Compiz restarts within 45-60 seconds. Issue started with the update on wednesday 23rd March 0800 GMT. ProblemType: Crash DistroRelease: Ubuntu 11.04 Package: unity 3.6.8-0ubuntu1 ProcVersionSignature: Ubuntu 2.6.38-7.38-generic 2.6.38 Uname: Linux 2.6.38-7-generic i686 Architecture: i386 CrashCounter: 1 Date: Thu Mar 24 21:10:38 2011 ExecutablePath: /usr/bin/compiz InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007) ProcCmdline: compiz ProcEnviron: LANGUAGE=ro_RO:en LANG=ro_RO.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x807ffe7 <_ZN10CompWindow2idEv+7>:mov 0x2c(%eax),%eax PC (0x0807ffe7) ok source "0x2c(%eax)" (0x002c) not located in a known VMA region (needed readable region)! destination "%eax" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: unity StacktraceTop: CompWindow::id() () CompScreen::handleEvent(_XEvent*) () PrivateCompositeScreen::handleEvent(_XEvent*) () from /usr/lib/compiz/libcomposite.so CompScreen::handleEvent(_XEvent*) () PrivateGLScreen::handleEvent(_XEvent*) () from /usr/lib/compiz/libopengl.so Title: compiz crashed with SIGSEGV in CompWindow::id() UpgradeStatus: Upgraded to natty on 2011-03-21 (3 days ago) UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/742028/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 670364] Re: compiz / g_main_loop integration test application
** Changed in: unity (Ubuntu) Status: Triaged => Won't Fix ** Changed in: unity Status: Triaged => Won't Fix ** Changed in: compiz Status: Triaged => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/670364 Title: compiz / g_main_loop integration test application Status in Compiz: Won't Fix Status in Unity: Won't Fix Status in “unity” package in Ubuntu: Won't Fix Bug description: The new integration of g_main_loop into compiz may impact the rest of its core, or plugins. This task captures the need to develop a test application to exercise that integration and help identify potential regressions. To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/670364/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1388558] Re: [packaging]Missing dependency to libxpathselect1.4 in Ubuntu 14.04
Thank you for trying to make Unity better. The xpathselect library is dynamically loaded at runtime to provide an exported automated testing and debug interface over D-Bus. It is not a normal part of the functioning of the Unity shell and making it a package dependency of Unity itself would be the wrong thing to do. A recent change downgraded the associated message from an error to a warning. Unless you're running the automated test suite (unity- autopilot, which _does_ have a package dependency on libxpathselect1.4) this message can be safely ignored. ** Changed in: unity (Ubuntu) Status: New => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1388558 Title: [packaging]Missing dependency to libxpathselect1.4 in Ubuntu 14.04 Status in “unity” package in Ubuntu: Won't Fix Bug description: The following message printed when I run '$ compiz --replace' in the terminal: ` ERROR unity.debug.interface DebugDBusInterface.cpp:216 Unable to load entry point in libxpathselect: libxpathselect.so.1.4: Can't open shared object file: File not found ` It seems that Unity(or it's component) depends on this library but however, not installed with unity package. Manually install libxpathselect1.4 package removes that error message. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.3+14.04.20140826-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-22.29-lowlatency 3.16.4 Uname: Linux 3.16.0-22-lowlatency i686 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.5 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: KDE Date: Sun Nov 2 21:16:26 2014 InstallationDate: Installed on 2013-03-08 (603 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release i386 (20121017.2) SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2014-04-19 (197 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1388558/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1020051] Re: Xorg freeze
** Changed in: compiz Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1020051 Title: Xorg freeze Status in Compiz: Invalid Status in “xorg” package in Ubuntu: Invalid Bug description: My screen hangs randomly. The only thing that is responsive is the touchpad. I can mve the mouse pointer across the screen but cannot click anything. The system cannot be soft-restarted too. The only resort is to press the power button long enough to do shutdown the system. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: xorg 1:7.6+12ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-25.40-generic 3.2.18 Uname: Linux 3.2.0-25-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.0.1-0ubuntu8 Architecture: amd64 Date: Mon Jul 2 16:53:48 2012 DistroCodename: precise DistroVariant: ubuntu InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) ProcEnviron: LANGUAGE=en_IN:en TERM=xterm PATH=(custom, no user) LANG=en_IN SHELL=/bin/bash SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/1020051/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1386011] Re: Wrong time is shown after switch to daylight savings time
** Package changed: unity (Ubuntu) => indicator-datetime (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-datetime in Ubuntu. https://bugs.launchpad.net/bugs/1386011 Title: Wrong time is shown after switch to daylight savings time Status in “indicator-datetime” package in Ubuntu: New Bug description: After switch to daylight savings time, the time at top right corner is not updated. However it is shown correct elsewhere. see the screenshot https://dl.dropboxusercontent.com/u/13590393/ubuntu-bug.png at the corner the old time is shown, at the dropdown window - updated time. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1386011/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1385413] Re: unity_support_test has stopped unexpectedly
** Also affects: virtualbox (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1385413 Title: unity_support_test has stopped unexpectedly Status in “unity” package in Ubuntu: New Status in “virtualbox” package in Ubuntu: New Bug description: Performed the upgrade from Trusty to Utopic, after the required restart of the computer the 'Report a problem' dialog poped up saying that unity_support_test has stopped unexpectedly. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: unity 7.3.1+14.10.20141016-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-23.31-generic 3.16.4 Uname: Linux 3.16.0-23-generic i686 .tmp.unity.support.test.1: ApportVersion: 2.14.7-0ubuntu8 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Fri Oct 24 18:27:07 2014 DistUpgraded: 2014-10-24 17:54:14,577 DEBUG enabling apt cron job DistroCodename: utopic DistroVariant: ubuntu DkmsStatus: virtualbox-guest, 4.3.18, 3.16.0-23-generic, i686: installed GraphicsCard: InnoTek Systemberatung GmbH VirtualBox Graphics Adapter [80ee:beef] (prog-if 00 [VGA controller]) InstallationDate: Installed on 2014-09-25 (29 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release i386 (20140722.2) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: innotek GmbH VirtualBox ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-23-generic root=UUID=664043af-2956-48b2-baca-3609d1ee45c3 ro quiet splash vt.handoff=7 Renderer: Software SourcePackage: unity UnitySupportTest: Error: command ['/usr/lib/nux/unity_support_test', '-p', '-f'] failed with exit code -11: libGL error: pci id for fd 4: 80ee:beef, driver (null) OpenGL Warning: Assertion failed: thread && thread->netServer.conn && thread->netServer.conn->type==CR_VBOXHGCM && thread->bInjectThread, file /mnt/tinderbox/add-4.3/src/VBox/Additions/common/crOpenGL/pack/packspu_misc.c, line 562 UpgradeStatus: Upgraded to utopic on 2014-10-24 (0 days ago) dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH version.compiz: compiz 1:0.9.12+14.10.20140918-0ubuntu1 version.libdrm2: libdrm2 2.4.56-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.0-0ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.3.0-0ubuntu3 version.xserver-xorg-core: xserver-xorg-core 2:1.16.0-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.914-1~exp1ubuntu4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2 xserver.bootTime: Fri Oct 24 18:18:10 2014 xserver.configfile: default xserver.errors: AIGLX error: vboxvideo does not export required DRI extension AIGLX: reverting to software rendering xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.16.0-1ubuntu1 xserver.video_driver: vboxvideo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1385413/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1243233] Re: Holding Super key doesn't bring up shortcut overlay.
** Changed in: unity Status: Confirmed => Fix Released ** Changed in: unity (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1243233 Title: Holding Super key doesn't bring up shortcut overlay. Status in Unity: Fix Released Status in “unity” package in Ubuntu: Fix Released Bug description: After upgrading from 13.04 to 13.10, holding Super no longer brings up the help overlay. Holding Super worked before upgrading. Tapping the Super key still brings up the HUD, and holding it down still brings up the Launcher and after a second or so shows the numbers on the applications. In Compiz Config Manager, under Ubuntu Unity Plugin -> Launcher, the Key to show the Dash, Launcher and Help Overlay is set to Super. Under Ubuntu Unity Plugin -> General, Enable Shortcut Hints Overlay is checked. This is also known to affect 14.04 (without compiz) when workspaces are enabled and screen resolution is 1024x768. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1243233/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 764424] Re: Launcher - dropping a file on a launcher app icon should open that file in the app
Bug does not meet the definition of "critical". ** Changed in: unity Importance: Critical => High -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/764424 Title: Launcher - dropping a file on a launcher app icon should open that file in the app Status in Ayatana Design: Fix Committed Status in Unity: Triaged Status in “unity” package in Ubuntu: Triaged Bug description: If a user drags and drops a file on top of a Launcher app icon, the application should open the file if it is a file type it supports. If the application does not support the file type nothing should happen. Also at the moment many Launcher icons do not highlight when the user starts dragging, even if the application supports opening the file type being dragged. For example, if the user starts dragging a text file firefox and libreoffice writer should illuminate in addition to gedit. Another example is dragging a tarball; thunderbird should illuminate and if the tarball is dropped on the thunderbird icon it should open a new message with it as an attachment. UPDATE : Compiz screws up the handling when a drop happens at about the same time as the scale timeout goes off. It doesn't freeze so much as grab the mouse forever. - Desired resolution: - create a new desktop key that details all file types that can be imported into an application. See Robert Carr's comments #1 and #4 for details. - For the following applications, ensure the information about which file types can be opened by a drag and drop operation is updated: LibreOffice, Thunderbird, Chormium, Firefox, Gedit, Image viewer, Shotwell, GIMP, Transmission, Terminal, Brasero Disk Burner, Archive Manager, Evolution, Rhythembox, VLC To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/764424/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 846407] Re: xrdp is not able to transmitt unity desktop correct - different clients
** Changed in: unity Milestone: None => 7.3.2 ** Changed in: unity Importance: Undecided => Medium ** Changed in: unity (Ubuntu) Importance: Undecided => Medium -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/846407 Title: xrdp is not able to transmitt unity desktop correct - different clients Status in Posix RDP server: Unknown Status in Unity: Confirmed Status in “unity” package in Ubuntu: Confirmed Status in “x2goclient” package in Ubuntu: New Status in “xrdp” package in Ubuntu: Confirmed Bug description: After login nothing is shown except desktop wallpaper Steps to repeat 1. sudo apt-get install xrdp 2. Install CoRD http://sourceforge.net/projects/cord/files/cord/0.5.5/CoRD_0.5.5.zip/download 3. Login to the server using CoRD Expected result: Unity desktop with menus, taskbars, etc. Actual result: Unity desktop wallpaper To manage notifications about this bug go to: https://bugs.launchpad.net/posixrdp/+bug/846407/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1371590] Re: Global menu bar snatches defeat from the jaws of victory, à la Windows 95 Start button
This sounds remarkably like an X11 configuration issue. The only time I've ever seen anything like it is when a monitor gives incorrect EDID information or physical screens are explicitly placed incorrectly within the X11 virtual screen using xrandr. Could this possibly be a themeing issue? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1371590 Title: Global menu bar snatches defeat from the jaws of victory, à la Windows 95 Start button Status in Unity: Incomplete Status in “unity” package in Ubuntu: Incomplete Bug description: There is a really old usability bug relating to mouse accuracy, which Ubuntu 14.04 has rediscovered in its global menu. Basically, it's super easy to move your pointer fast and hard to the extreme edge and corners of the screen, so you can hit targets placed there quickly. But the global menu only activates if the cursor is a pixel or two from the top of the screen. This is a massive usability bug. The example from the 90s (yes, 20 years ago) is that Win 95's start button was offset from the bottom left corner by a couple of pixels. That made it hard for people to hit, and if they'd only put it flush with the bottom left it would have been way way easier to click. Hence "snatching defeat from the jaws of victory" - e.g. in this post from 2000 http://www.joelonsoftware.com/uibook/chapters/fog63.html Hopefully this is an easy fix: extend the mouseover activation area for the global menu to the top of the screen. Right to the top zeroth row of pixels. Please? To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1371590/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1344102] Re: Odd behavior with workspaces - Firefox gets moved to other monitors when it shouldn't.
** Changed in: unity (Ubuntu) Importance: Undecided => Medium ** Changed in: unity Status: New => Confirmed ** Changed in: unity Importance: Undecided => Medium -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1344102 Title: Odd behavior with workspaces - Firefox gets moved to other monitors when it shouldn't. Status in Unity: Confirmed Status in “unity” package in Ubuntu: Confirmed Bug description: This one seems easy to duplicate. In a dual screen setup, do the following. Place an instant message (Pidgin, etc) on monitor 1, workspace 3. Place Firefox on monitor 2, workspace 1. Have the user in the message send you a link. When you click the link, it opens in Firefox in workspace 1 as expected, but Firefox is moved from monitor 2 to monitor 1. This type of behavior should not take place as windows in other workspaces should not be shuffled around. Users place certain windows in certain workspaces for a multitude of reasons. While workspaces are great to have, behavior like this tends to be a bit of a buzzkill when users must place everything back to where it should have been in the first place. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.1+14.04.20140513-0ubuntu2 ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 Uname: Linux 3.13.0-32-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-19ubuntu1) .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.2 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: Fri Jul 18 11:50:37 2014 DistUpgraded: 2014-04-17 17:35:16,276 DEBUG enabling apt cron job DistroCodename: trusty DistroVariant: ubuntu GraphicsCard: NVIDIA Corporation G94 [GeForce 9600 GT] [10de:0622] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Device [196e:0545] InstallationDate: Installed on 2014-02-03 (164 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-32-generic root=UUID=e0b59d9e-7632-4d75-9d1e-bbf60635a168 ro quiet splash nomdmonddf nomdmonisw SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2014-04-17 (91 days ago) dmi.bios.date: 08/31/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.30 dmi.board.name: H61M/U3S3 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.30:bd08/31/2011:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH61M/U3S3:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. version.compiz: compiz 1:0.9.11.1+14.04.20140701-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1 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: Fri Jul 18 10:39:01 2014 xserver.configfile: default xserver.errors: open /dev/fb0: No such file or directory xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.15.1-0ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1344102/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1366351] Re: compiz crashed with SIGSEGV in g_closure_invoke() if unity-settings-daemon goes away
Note: this is likely triggered by bug #1380278 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1366351 Title: compiz crashed with SIGSEGV in g_closure_invoke() if unity-settings- daemon goes away Status in Compiz: Invalid Status in Unity: In Progress Status in “compiz” package in Ubuntu: Invalid Status in “unity” package in Ubuntu: In Progress Bug description: Compiz crashes when unity-settings-daemon goes away. Simple reproducer: "killall -SEGV unity-settings-daemon". ProblemType: Crash DistroRelease: Ubuntu 14.10 Package: compiz-core 1:0.9.12+14.10.20140812-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-13.19-generic 3.16.1 Uname: Linux 3.16.0-13-generic x86_64 NonfreeKernelModules: fglrx .tmp.unity.support.test.0: ApportVersion: 2.14.7-0ubuntu2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Sat Sep 6 10:48:43 2014 Disassembly: => 0x0: Cannot access memory at address 0x0 DistUpgraded: 2014-09-01 18:03:23,330 DEBUG enabling apt cron job DistroCodename: utopic DistroVariant: ubuntu ExecutablePath: /usr/bin/compiz GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Curacao XT [Radeon R9 270X] [1002:6810] (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:04a1] InstallationDate: Installed on 2014-03-24 (166 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MachineType: MSI MS-7640 ProcCmdline: compiz ProcEnviron: PATH=(custom, no user) SHELL=/bin/bash LD_LIBRARY_PATH= LANG=en_US.UTF-8 XDG_RUNTIME_DIR= ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-13-generic root=UUID=2696ea28-d88b-431c-a1fa-1e0f297ee664 ro quiet splash vt.handoff=7 SegvAnalysis: Segfault happened at: 0x0: Cannot access memory at address 0x0 PC (0x) not located in a known VMA region (needed executable region)! SegvReason: executing NULL VMA Signal: 11 SourcePackage: compiz StacktraceTop: ?? () g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_signal_emit () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: compiz crashed with SIGSEGV in g_closure_invoke() UpgradeStatus: Upgraded to utopic on 2014-09-01 (4 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo dmi.bios.date: 10/31/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V1.15 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: 890FXA-GD70 (MS-7640) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV1.15:bd10/31/2012:svnMSI:pnMS-7640:pvr1.0:rvnMSI:rn890FXA-GD70(MS-7640):rvr1.0:cvnMSI:ct3:cvr1.0: dmi.product.name: MS-7640 dmi.product.version: 1.0 dmi.sys.vendor: MSI version.compiz: compiz 1:0.9.12+14.10.20140812-0ubuntu1 version.fglrx-installer: fglrx-installer N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.56-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.2.6-1ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.2.6-1ubuntu3 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu9 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.914-1~exp1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Sat Sep 6 10:48:05 2014 xserver.configfile: default xserver.errors: open /dev/dri/card0: No such file or directory AIGLX error: failed to open /usr/X11R6/lib64/modules/dri/fglrx_dri.so, error[/usr/X11R6/lib64/modules/dri/fglrx_dri.so: cannot open shared object file: No such file or directory] AIGLX error: failed to open /usr/lib64/dri/fglrx_dri.so, error[/usr/lib64/dri/fglrx_dri.so: cannot open shared object file: No such file or directory] AIGLX error: failed to open /usr/X11R6/lib/modules/dri/fglrx_dri.so, error[/usr/X11R6/lib/modules/dri/fglrx_dri.so: cannot open shared object file: No such file or directory] xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.15.1-0ubuntu9 xserver.video_driver: fglrx To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/1366351/+subscriptio
[Touch-packages] [Bug 1366351] Re: compiz crashed with SIGSEGV in g_closure_invoke() if unity-settings-daemon goes away
** Also affects: unity (Ubuntu) Importance: Undecided Status: New ** Also affects: unity Importance: Undecided Status: New ** Changed in: unity Importance: Undecided => Critical ** Changed in: unity Status: New => In Progress ** Changed in: unity (Ubuntu) Importance: Undecided => Critical ** Changed in: unity (Ubuntu) Status: New => In Progress ** Changed in: compiz Status: Confirmed => Invalid ** Changed in: compiz (Ubuntu) Status: Triaged => Invalid ** Changed in: unity Assignee: (unassigned) => Brandon Schaefer (brandontschaefer) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1366351 Title: compiz crashed with SIGSEGV in g_closure_invoke() if unity-settings- daemon goes away Status in Compiz: Invalid Status in Unity: In Progress Status in “compiz” package in Ubuntu: Invalid Status in “unity” package in Ubuntu: In Progress Bug description: Compiz crashes when unity-settings-daemon goes away. Simple reproducer: "killall -SEGV unity-settings-daemon". ProblemType: Crash DistroRelease: Ubuntu 14.10 Package: compiz-core 1:0.9.12+14.10.20140812-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-13.19-generic 3.16.1 Uname: Linux 3.16.0-13-generic x86_64 NonfreeKernelModules: fglrx .tmp.unity.support.test.0: ApportVersion: 2.14.7-0ubuntu2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Sat Sep 6 10:48:43 2014 Disassembly: => 0x0: Cannot access memory at address 0x0 DistUpgraded: 2014-09-01 18:03:23,330 DEBUG enabling apt cron job DistroCodename: utopic DistroVariant: ubuntu ExecutablePath: /usr/bin/compiz GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Curacao XT [Radeon R9 270X] [1002:6810] (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:04a1] InstallationDate: Installed on 2014-03-24 (166 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MachineType: MSI MS-7640 ProcCmdline: compiz ProcEnviron: PATH=(custom, no user) SHELL=/bin/bash LD_LIBRARY_PATH= LANG=en_US.UTF-8 XDG_RUNTIME_DIR= ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-13-generic root=UUID=2696ea28-d88b-431c-a1fa-1e0f297ee664 ro quiet splash vt.handoff=7 SegvAnalysis: Segfault happened at: 0x0: Cannot access memory at address 0x0 PC (0x) not located in a known VMA region (needed executable region)! SegvReason: executing NULL VMA Signal: 11 SourcePackage: compiz StacktraceTop: ?? () g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_signal_emit () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: compiz crashed with SIGSEGV in g_closure_invoke() UpgradeStatus: Upgraded to utopic on 2014-09-01 (4 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo dmi.bios.date: 10/31/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V1.15 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: 890FXA-GD70 (MS-7640) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV1.15:bd10/31/2012:svnMSI:pnMS-7640:pvr1.0:rvnMSI:rn890FXA-GD70(MS-7640):rvr1.0:cvnMSI:ct3:cvr1.0: dmi.product.name: MS-7640 dmi.product.version: 1.0 dmi.sys.vendor: MSI version.compiz: compiz 1:0.9.12+14.10.20140812-0ubuntu1 version.fglrx-installer: fglrx-installer N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.56-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.2.6-1ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.2.6-1ubuntu3 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu9 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.914-1~exp1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Sat Sep 6 10:48:05 2014 xserver.configfile: default xserver.errors: open /dev/dri/card0: No such file or directory AIGLX error: failed to open /usr/X11R6/lib64/modules/dri/fglrx_dri.so, error[/usr/X11R6/lib64/modules/dri/fglrx_dri.so: cannot open shared object file: No such file or
[Touch-packages] [Bug 1354092] Re: Location service needs internationalization
** Tags removed: touch-2014-09-25 ** Tags added: touch-2014-10-09 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to location-service in Ubuntu. https://bugs.launchpad.net/bugs/1354092 Title: Location service needs internationalization Status in Ubuntu Translations: In Progress Status in “location-service” package in Ubuntu: In Progress Bug description: The location dialog is displayed untranslated. Test case. - Switch the phone to Spanish. - Open webbrowser-app. - Go to maps.google.com - Accept to use location in the app. - Dialog appears. Expected result. - The dialog should be displayed in Spanish. Actual result. - The dialog appears untranslated: "unconfined: An unconfined application wants to access your current location. Deny, Allow". To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-translations/+bug/1354092/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1375276] Re: Menus get in the way of maximization
** Changed in: unity (Ubuntu) Status: New => Confirmed ** Changed in: unity (Ubuntu) Importance: Undecided => Medium ** Also affects: unity Importance: Undecided Status: New ** Changed in: unity Importance: Undecided => Medium ** Changed in: unity Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1375276 Title: Menus get in the way of maximization Status in Unity: Confirmed Status in “unity” package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1. Set the following configuration: In "Appearance" settings, under "Behavior" tab, where it asks "Show the menus for a window", select "In the window's title bar". 2. Open any unmaximized window with menus, say gvim. The menus of the application are hidden on the top bar which looks nice and clean. Now try to absent-mindedly maximize the window by double clicking the top bar. 3. Usually unamximized windows are small and each program usually has at least 5~6 menu items. Therefore more than half of the top bar is occupied by the menu items. Double clicking on that range opens and immediately closes a menu item. I doubt this is ever anyone's intention! On the contrary, if I double click on the top bar I expect the window to maximize. If suddenly menu items appear under my cursor, I wouldn't care; I would still expect double click to maximize the window. Suggested solution: If a menu item is double clicked, (un)maximize the window. This works also when the menus are in the menu bar, which is the desired behavior for unmaximizing if the window is already maximized. The side effect is that if the menus are in the window's title bar and the menu bar is double-clicked, the window gets maximized. If this is not a desired side effect, it can be guarded against. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.2+14.04.20140714-0ubuntu1.1 ProcVersionSignature: Ubuntu 3.13.0-36.63-generic 3.13.11.6 Uname: Linux 3.13.0-36-generic i686 ApportVersion: 2.14.1-0ubuntu3.4 Architecture: i386 CompizPlugins: [core,bailer,detection,composite,opengl,decor,mousepoll,vpswitch,regex,animation,snap,expo,move,compiztoolbox,place,grid,imgpng,gnomecompat,wall,ezoom,workarounds,staticswitcher,resize,fade,unitymtgrabhandles,scale,session,unityshell] CurrentDesktop: Unity Date: Mon Sep 29 15:52:08 2014 ExecutablePath: /usr/bin/compiz InstallationDate: Installed on 2014-07-04 (87 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140417) SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) P.S. This is NOT a fresh install. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1375276/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1363421] Re: Unity Doesn't Start on 14.10 System
This is looking like a duplicate of bug #1357746. Could you please attach a copy of your /var/log/dmesg to this bug? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1363421 Title: Unity Doesn't Start on 14.10 System Status in Unity: Incomplete Status in “unity” package in Ubuntu: Incomplete Bug description: Been having problems getting any 14.10 build (Gnome and Unity) to boot on this desktop. Submitting problem report on Unity since seems easist to document. I downloaded the Ubuntu 14.10 daily build dated 8/29/14 and went through the install process without any problem. After completion of the install, doing the first boot of the system, and the login screen my desktop background is displayed with desktop ICONs. There is no Ubuntu banner at the top of the screen or any Unity launch bar on the left. My only option was to ctl-alt-f1 and build/save a bug report which I using to report under the working 14.04 system on this same desktop. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: unity 7.3.1+14.10.20140811-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-11.16-generic 3.16.1 Uname: Linux 3.16.0-11-generic x86_64 ApportVersion: 2.14.6-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: Sat Aug 30 08:28:02 2014 InstallationDate: Installed on 2014-08-29 (0 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140829) ProcEnviron: TERM=linux PATH=(custom, no user) XDG_RUNTIME_DIR= 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/1363421/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1363421] Re: Unity Doesn't Start on 14.10 System
The symptom you're describing is of Compiz not running. There isn't enough additional information reported to tell us why, though. Let's start with this: try running '/usr/lib/nux/unity_support_test --print --display :0' and attach the output to this bug. That program determines if there is appropriate hardware support for running Unity (and some driver updates have been known to cause problems by misreporting their capabilities recently). Another thing is to look for the Unity log file. If the file ~/.cache/upstart/unity7.log exists, could you please also attach that to this bug. ** Changed in: unity (Ubuntu) Status: New => Incomplete ** Changed in: unity Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1363421 Title: Unity Doesn't Start on 14.10 System Status in Unity: Incomplete Status in “unity” package in Ubuntu: Incomplete Bug description: Been having problems getting any 14.10 build (Gnome and Unity) to boot on this desktop. Submitting problem report on Unity since seems easist to document. I downloaded the Ubuntu 14.10 daily build dated 8/29/14 and went through the install process without any problem. After completion of the install, doing the first boot of the system, and the login screen my desktop background is displayed with desktop ICONs. There is no Ubuntu banner at the top of the screen or any Unity launch bar on the left. My only option was to ctl-alt-f1 and build/save a bug report which I using to report under the working 14.04 system on this same desktop. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: unity 7.3.1+14.10.20140811-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-11.16-generic 3.16.1 Uname: Linux 3.16.0-11-generic x86_64 ApportVersion: 2.14.6-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: Sat Aug 30 08:28:02 2014 InstallationDate: Installed on 2014-08-29 (0 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140829) ProcEnviron: TERM=linux PATH=(custom, no user) XDG_RUNTIME_DIR= 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/1363421/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1366897] Re: No way to add a puk code to a phone where your sim pin is entered badly 3 times
*** This bug is a duplicate of bug 1359280 *** https://bugs.launchpad.net/bugs/1359280 ** Tags removed: touch-2014-09-25 ** Tags added: touch-2014-10-09 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-network in Ubuntu. https://bugs.launchpad.net/bugs/1366897 Title: No way to add a puk code to a phone where your sim pin is entered badly 3 times Status in “indicator-network” package in Ubuntu: Confirmed Bug description: STEPS: Prerequisites: a phone that is on android 1. Click on settings 2. Click on security 3. Enable sim pin lock 4. Reboot 5. Enter the sim pin incorrectly 3 times 6. 1 locked sim 7. Put the sim in your android phone 8. Notice you are now asked for the puk code to unlock the sim. EXPECTATION: I expect the same behaviour from our phone. If I accidentally lock my sim I have no way to unlock it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1366897/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1372834] Re: SmartScopesProxy needs to send version numbers to the server
** Changed in: unity-scopes-api (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-scopes-api in Ubuntu. https://bugs.launchpad.net/bugs/1372834 Title: SmartScopesProxy needs to send version numbers to the server Status in QML plugin for Scopes: In Progress Status in “unity-scopes-api” package in Ubuntu: In Progress Bug description: Shell plugin needs to report versions of important components (scopes- api, shell-plugin and unity8) with search and preview request, and they need to be passed to from SmartScopesProxy to Smart Scopes Server via UserAgent string. To manage notifications about this bug go to: https://bugs.launchpad.net/unity-scopes-shell/+bug/1372834/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1362150] Re: [Greeter] SIM PIN unlock usability needs improving
** Changed in: indicator-network Importance: Undecided => High ** Changed in: indicator-network (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1362150 Title: [Greeter] SIM PIN unlock usability needs improving Status in Network Menu: New Status in Ubuntu UX bugs: Fix Released Status in “indicator-network” package in Ubuntu: Confirmed Status in “unity8” package in Ubuntu: Confirmed Bug description: Several bugs have been reported related to using the PIN unlock Grouping here for review Add feedback on failed attempts - The dialog tells you how many attempts you have remaining before a PUK code will be required - Entering the wrong PIN will result in a clear message to user of the failure and an update of the attempts remaining count After cancelling SIM unlock, how to unlock is not obvious: 1.Insert this SIM card 2.Power on device 3. Popup SIM PIN unlock interface after power on device 4. cancel this dialog 5. Go to phone app to make a call It is not obvious that the next step should be to drag down the indicator and use the unlock button. the phone and messaging apps should have a shorthand button clearly visible to unlock the relevant SIM so that the user does not have to "know" to go to the indicator-network first to be able to make phonecalls or send SMS To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-network/+bug/1362150/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1338430] Re: Slow loading/showing of images in the dash
** Tags removed: touch-2014-09-25 ** Tags added: touch-2014-10-09 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1338430 Title: Slow loading/showing of images in the dash Status in “unity8” package in Ubuntu: In Progress Bug description: Installed app icons (when expanding the category) show very slowly after reboot. It actually makes the impression that those are being downloaded. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1338430/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
