[Dx-packages] [Bug 1191551] Re: launcher no longer shows the number of open windows of each icon
I think it's fixed ** Changed in: unity (Ubuntu) Status: Incomplete => Fix Released -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1191551 Title: launcher no longer shows the number of open windows of each icon Status in “unity” package in Ubuntu: Fix Released Bug description: Until recently, when you clicked on the launcher icon of an application of which you had more than one window open, you used to be able to know how many open window you had because there were N small white arrows on the left side of the icon, N being the number of open widnow. Since recently, there is always only one white arrow (which by the way is thinner than before), no matter how many open widnows the application has. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: unity 6.12.0-0ubuntu0.2 ProcVersionSignature: Ubuntu 3.5.0-34.55-generic 3.5.7.13 Uname: Linux 3.5.0-34-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.6.1-0ubuntu11 Architecture: i386 CompizPlugins: [core,composite,opengl,decor,vpswitch,mousepoll,compiztoolbox,snap,commands,place,resize,session,regex,grid,wall,move,gnomecompat,imgpng,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] Date: Sun Jun 16 19:19:47 2013 InstallationDate: Installed on 2010-06-23 (1089 days ago) InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429) MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: unity UpgradeStatus: Upgraded to quantal on 2013-01-13 (154 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1191551/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1296909] Re: What you lock to launcher is not what you get locked to launcher
If the system is generating .desktop files automatically, then it should generate different desktop files for different binaries that are in different locations. What if I run two programs that have absolutely nothing to do with each other but whose executable file happens to have the same name?!? Generating automatically a .desktop file based on a binary name, and reusing that for another binary of the same name, is a wrong design and should be fixed (and the fix is easy). Also, if I download an executable, place it in an arbitrary place, and run it, and then delete it, I don't expect it to leave any trash around the system that will potentially affect other programs. If _it_ does, then it's that executable's author's responsibility, but if the system does, and doesn't warn me, then the system is doing somnething wrong. At least it should show a notice (with a "don't show again" option) indicating that a desktop file has been created and showing its location, so I know that I may need to delete it later. Consider at least that. And another thing: apparently the .desktop files that are automatically generated for any executable you run, not always work. I downloaded Processing (http://processing.org). It's a .tgz that you extract to a folder and then you run an executable in it. When I run it, an icon appears on the Launcher. Right-clicking and selecting "lock to launcher" locks the icon lock to the launcher, but when I later click on the icon nothing happens. So the mechanism that creates .desktop files automatically does not always work. > I'm marking this bug as invalid because the system is actually working > completely as designed. The design is seriously wrong then, and the bug should be reopened until the design is fixed. > In this case the problem can be resolved by manually fixing the > configuration (.desktop) files that are reserved for the user, > probably by removing them. Yes, given that the user figures out that a .desktop file has been created and where. Now I know that, but I had to come here to figure out. That's ridiculous. -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1296909 Title: What you lock to launcher is not what you get locked to launcher Status in “unity” package in Ubuntu: Invalid Bug description: I downloaded Eclipse from here: https://www.eclipse.org/downloads/download.php?file=/technology/epp/downloads/release/kepler/SR2/eclipse-standard-kepler-SR2-linux-gtk-x86_64.tar.gz which is a tar.gz, which I untarred into a custom folder, namely ~/Documents/programmi/eclipse, by placing the .tar.gz in ~/Documents/programmi and right clicking on it with Nautilus and doing "extract here". (~/Documents/programmi is not set up to be any special or privileged folder for programs, it's just a folder that I created inside Documents). Then I realized that was not the version of Eclipse I wanted, so I installed Eclipsed by running in a terminal: sudo apt-get install eclipse This created, among other things, a /usr/share/applications/eclipse.desktop file "which eclipse" outputs "/usr/bin/eclipse" When I type "eclipse" into a terminal, the one installed with apt-get will run, as expected. I slightly modified /usr/share/applications/eclipse.desktop so that UBUNTU_MENUPROXY would be used (to work around the menus-not-working bug), and when I run "eclipse" from a terminal, I can see the menu is affected by the change I made to the .desktop file, so the /usr/share/applications/eclipse.desktop file somehow "relates" to the executable that is run by writing just "eclipse" from a command line. When I wrote "eclipse" into the Dash, the one I had manually downloaded and unzipped would run, which is somewhat funny in itself, because I wonder how it "finds" the one that I have installed in an arbitrary folder and it doesn't find the one that has been installed with the package manager. Then I did the following: - run "eclipse" from a terminal (this would run the apt-get installed one) - right click on the icon on the launcher and choose "lock to launcher". - exit eclipse - click on the icon that has been created on the launcher Expected: should run the same thing that was running when I locked it to the launcher, which is what I run from a terminal typing "eclipse" Observed: it runs the one that I had manually downloaded and unzipped. Whatever is going on, there is an inconsistency here. If I run some program, whatever I run it from, and then lock its icon to the launcher, then clicking on that icon must load the program that was running when I locked that icon on the launcher, whatever that is. Not some other version that is installed somewhere else. Then I deleted the folder ~/Documents/programmi/eclipse altogether. Now the icon on the launcher does nothing. Eve
[Dx-packages] [Bug 1296909] Re: What you lock to launcher is not what you get locked to launcher
Oh, yes, there it is. It doesn't show up with "sudo find / -name eclipse.desktop", that's why I couldn't find it. One mistery is how it got created (but maybe Eclipse itself, the one I unzipped manually, created it when run the first time). Anyway, if you run some executable, then you right-click on its icon and lock it to the launcher, and the result is that the icon locked to the launcher calls some unrelated .desktop file somewhere else, that's a wrong behavior. -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1296909 Title: What you lock to launcher is not what you get locked to launcher Status in “unity” package in Ubuntu: New Bug description: I downloaded Eclipse from here: https://www.eclipse.org/downloads/download.php?file=/technology/epp/downloads/release/kepler/SR2/eclipse-standard-kepler-SR2-linux-gtk-x86_64.tar.gz which is a tar.gz, which I untarred into a custom folder, namely ~/Documents/programmi/eclipse, by placing the .tar.gz in ~/Documents/programmi and right clicking on it with Nautilus and doing "extract here". (~/Documents/programmi is not set up to be any special or privileged folder for programs, it's just a folder that I created inside Documents). Then I realized that was not the version of Eclipse I wanted, so I installed Eclipsed by running in a terminal: sudo apt-get install eclipse This created, among other things, a /usr/share/applications/eclipse.desktop file "which eclipse" outputs "/usr/bin/eclipse" When I type "eclipse" into a terminal, the one installed with apt-get will run, as expected. I slightly modified /usr/share/applications/eclipse.desktop so that UBUNTU_MENUPROXY would be used (to work around the menus-not-working bug), and when I run "eclipse" from a terminal, I can see the menu is affected by the change I made to the .desktop file, so the /usr/share/applications/eclipse.desktop file somehow "relates" to the executable that is run by writing just "eclipse" from a command line. When I wrote "eclipse" into the Dash, the one I had manually downloaded and unzipped would run, which is somewhat funny in itself, because I wonder how it "finds" the one that I have installed in an arbitrary folder and it doesn't find the one that has been installed with the package manager. Then I did the following: - run "eclipse" from a terminal (this would run the apt-get installed one) - right click on the icon on the launcher and choose "lock to launcher". - exit eclipse - click on the icon that has been created on the launcher Expected: should run the same thing that was running when I locked it to the launcher, which is what I run from a terminal typing "eclipse" Observed: it runs the one that I had manually downloaded and unzipped. Whatever is going on, there is an inconsistency here. If I run some program, whatever I run it from, and then lock its icon to the launcher, then clicking on that icon must load the program that was running when I locked that icon on the launcher, whatever that is. Not some other version that is installed somewhere else. Then I deleted the folder ~/Documents/programmi/eclipse altogether. Now the icon on the launcher does nothing. Even if I remove it (unlock from launcher), start "eclipse" again from a terminal (which runs /usr/bin/eclipse), lock it to the launcher again, exit it, even so when I later click on the launcher icon it will launch nothing (as if "looking for" the one that I deleted). And surprisingly, when I type "eclipse" into the Dash, it still "finds" the old one, or at least, it finds something that won't run if I click on it. Even after restarting the computer. The only file named eclipse.desktop in the entire filesystem is the one under /usr/share/applications/eclipse.desktop It's as if by merely unzipping the .tar.gz file into an arbitrary non-standard folder, some kind of shortcut to it has been installed somewhere that allows it to be found when typing "Eclipse" into the Dash; even if I didn't install any package, just unzipped a .tar.gz file. Even after deleting the unzipped folder, that "link" somehow persists somewhere. It's crazy. And it even takes the place of the icon that I lock to Launcher when running /usr/bin/eclipse. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: unity 7.1.2+13.10.20131014.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-18.32-generic 3.11.10.4 Uname: Linux 3.11.0-18-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' Date: Mon Mar 24 20:08:39 2014 InstallationDate: Installed on 2013-10-11 (164 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MarkForUpload: True SourcePackage: unit
[Dx-packages] [Bug 1296909] [NEW] What you lock to launcher is not what you get locked to launcher
Public bug reported: I downloaded Eclipse from here: https://www.eclipse.org/downloads/download.php?file=/technology/epp/downloads/release/kepler/SR2/eclipse-standard-kepler-SR2-linux-gtk-x86_64.tar.gz which is a tar.gz, which I untarred into a custom folder, namely ~/Documents/programmi/eclipse, by placing the .tar.gz in ~/Documents/programmi and right clicking on it with Nautilus and doing "extract here". (~/Documents/programmi is not set up to be any special or privileged folder for programs, it's just a folder that I created inside Documents). Then I realized that was not the version of Eclipse I wanted, so I installed Eclipsed by running in a terminal: sudo apt-get install eclipse This created, among other things, a /usr/share/applications/eclipse.desktop file "which eclipse" outputs "/usr/bin/eclipse" When I type "eclipse" into a terminal, the one installed with apt-get will run, as expected. I slightly modified /usr/share/applications/eclipse.desktop so that UBUNTU_MENUPROXY would be used (to work around the menus-not-working bug), and when I run "eclipse" from a terminal, I can see the menu is affected by the change I made to the .desktop file, so the /usr/share/applications/eclipse.desktop file somehow "relates" to the executable that is run by writing just "eclipse" from a command line. When I wrote "eclipse" into the Dash, the one I had manually downloaded and unzipped would run, which is somewhat funny in itself, because I wonder how it "finds" the one that I have installed in an arbitrary folder and it doesn't find the one that has been installed with the package manager. Then I did the following: - run "eclipse" from a terminal (this would run the apt-get installed one) - right click on the icon on the launcher and choose "lock to launcher". - exit eclipse - click on the icon that has been created on the launcher Expected: should run the same thing that was running when I locked it to the launcher, which is what I run from a terminal typing "eclipse" Observed: it runs the one that I had manually downloaded and unzipped. Whatever is going on, there is an inconsistency here. If I run some program, whatever I run it from, and then lock its icon to the launcher, then clicking on that icon must load the program that was running when I locked that icon on the launcher, whatever that is. Not some other version that is installed somewhere else. Then I deleted the folder ~/Documents/programmi/eclipse altogether. Now the icon on the launcher does nothing. Even if I remove it (unlock from launcher), start "eclipse" again from a terminal (which runs /usr/bin/eclipse), lock it to the launcher again, exit it, even so when I later click on the launcher icon it will launch nothing (as if "looking for" the one that I deleted). And surprisingly, when I type "eclipse" into the Dash, it still "finds" the old one, or at least, it finds something that won't run if I click on it. Even after restarting the computer. The only file named eclipse.desktop in the entire filesystem is the one under /usr/share/applications/eclipse.desktop It's as if by merely unzipping the .tar.gz file into an arbitrary non-standard folder, some kind of shortcut to it has been installed somewhere that allows it to be found when typing "Eclipse" into the Dash; even if I didn't install any package, just unzipped a .tar.gz file. Even after deleting the unzipped folder, that "link" somehow persists somewhere. It's crazy. And it even takes the place of the icon that I lock to Launcher when running /usr/bin/eclipse. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: unity 7.1.2+13.10.20131014.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-18.32-generic 3.11.10.4 Uname: Linux 3.11.0-18-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' Date: Mon Mar 24 20:08:39 2014 InstallationDate: Installed on 2013-10-11 (164 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MarkForUpload: True SourcePackage: unity UpgradeStatus: Upgraded to saucy on 2014-02-23 (29 days ago) ** Affects: unity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug saucy -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1296909 Title: What you lock to launcher is not what you get locked to launcher Status in “unity” package in Ubuntu: New Bug description: I downloaded Eclipse from here: https://www.eclipse.org/downloads/download.php?file=/technology/epp/downloads/release/kepler/SR2/eclipse-standard-kepler-SR2-linux-gtk-x86_64.tar.gz which is a tar.gz, which I untarred into a custom folder, namely ~/Documents/programmi/eclipse, by placing the .tar.gz in ~/Documents/programmi and right clicking on it with Nautilus and doing "ex
[Dx-packages] [Bug 1296909] Re: What you lock to launcher is not what you get locked to launcher
Well, I'm noticing one more general thing that I didn't expect: if I run some arbitrary executable and then right-click on its icon on the launcher and do "lock to launcher", it does lock the icon to launcher but that icon is completely useless!!! The "lock to launcher" function seems to be ill-conceived: it is available for any icon of any running executable, but apparently only works with programs that have been "installed" in some way. If it is only supposed to work in that case, then this option should not be available at all in other cases. -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1296909 Title: What you lock to launcher is not what you get locked to launcher Status in “unity” package in Ubuntu: New Bug description: I downloaded Eclipse from here: https://www.eclipse.org/downloads/download.php?file=/technology/epp/downloads/release/kepler/SR2/eclipse-standard-kepler-SR2-linux-gtk-x86_64.tar.gz which is a tar.gz, which I untarred into a custom folder, namely ~/Documents/programmi/eclipse, by placing the .tar.gz in ~/Documents/programmi and right clicking on it with Nautilus and doing "extract here". (~/Documents/programmi is not set up to be any special or privileged folder for programs, it's just a folder that I created inside Documents). Then I realized that was not the version of Eclipse I wanted, so I installed Eclipsed by running in a terminal: sudo apt-get install eclipse This created, among other things, a /usr/share/applications/eclipse.desktop file "which eclipse" outputs "/usr/bin/eclipse" When I type "eclipse" into a terminal, the one installed with apt-get will run, as expected. I slightly modified /usr/share/applications/eclipse.desktop so that UBUNTU_MENUPROXY would be used (to work around the menus-not-working bug), and when I run "eclipse" from a terminal, I can see the menu is affected by the change I made to the .desktop file, so the /usr/share/applications/eclipse.desktop file somehow "relates" to the executable that is run by writing just "eclipse" from a command line. When I wrote "eclipse" into the Dash, the one I had manually downloaded and unzipped would run, which is somewhat funny in itself, because I wonder how it "finds" the one that I have installed in an arbitrary folder and it doesn't find the one that has been installed with the package manager. Then I did the following: - run "eclipse" from a terminal (this would run the apt-get installed one) - right click on the icon on the launcher and choose "lock to launcher". - exit eclipse - click on the icon that has been created on the launcher Expected: should run the same thing that was running when I locked it to the launcher, which is what I run from a terminal typing "eclipse" Observed: it runs the one that I had manually downloaded and unzipped. Whatever is going on, there is an inconsistency here. If I run some program, whatever I run it from, and then lock its icon to the launcher, then clicking on that icon must load the program that was running when I locked that icon on the launcher, whatever that is. Not some other version that is installed somewhere else. Then I deleted the folder ~/Documents/programmi/eclipse altogether. Now the icon on the launcher does nothing. Even if I remove it (unlock from launcher), start "eclipse" again from a terminal (which runs /usr/bin/eclipse), lock it to the launcher again, exit it, even so when I later click on the launcher icon it will launch nothing (as if "looking for" the one that I deleted). And surprisingly, when I type "eclipse" into the Dash, it still "finds" the old one, or at least, it finds something that won't run if I click on it. Even after restarting the computer. The only file named eclipse.desktop in the entire filesystem is the one under /usr/share/applications/eclipse.desktop It's as if by merely unzipping the .tar.gz file into an arbitrary non-standard folder, some kind of shortcut to it has been installed somewhere that allows it to be found when typing "Eclipse" into the Dash; even if I didn't install any package, just unzipped a .tar.gz file. Even after deleting the unzipped folder, that "link" somehow persists somewhere. It's crazy. And it even takes the place of the icon that I lock to Launcher when running /usr/bin/eclipse. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: unity 7.1.2+13.10.20131014.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-18.32-generic 3.11.10.4 Uname: Linux 3.11.0-18-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' Date: Mon Mar 24 20:08:39 2014 InstallationDate: Installed on 2013-10-11 (164 days ago) InstallationMedia: Ubuntu 13.04 "Ra
[Dx-packages] [Bug 1296253] [NEW] At random times, Launcher does not respond to clicks too close to the left border of the screen
Public bug reported: I have Launcher set up to not automatically hide (because it's buggy and it would stop showing up too often). Usually, you can click on a launcher icon even on the leftmost column of pixels and it will respond to clicks. Sometimes however, randomly, if you click on the very leftmost region, i.e. just next to the left border of the screen, it will not respond to click; you then have to click a little bit more to the right, inside the rounded rectangle that surrounds the icon, for it to work. Then, after doing some random things with the mouse (switching focus between different windows, closing some), it behaves normally again ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: unity 7.1.2+13.10.20131014.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-18.32-generic 3.11.10.4 Uname: Linux 3.11.0-18-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' Date: Sun Mar 23 12:19:12 2014 InstallationDate: Installed on 2013-10-11 (162 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MarkForUpload: True SourcePackage: unity UpgradeStatus: Upgraded to saucy on 2014-02-23 (28 days ago) ** Affects: unity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug saucy -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1296253 Title: At random times, Launcher does not respond to clicks too close to the left border of the screen Status in “unity” package in Ubuntu: New Bug description: I have Launcher set up to not automatically hide (because it's buggy and it would stop showing up too often). Usually, you can click on a launcher icon even on the leftmost column of pixels and it will respond to clicks. Sometimes however, randomly, if you click on the very leftmost region, i.e. just next to the left border of the screen, it will not respond to click; you then have to click a little bit more to the right, inside the rounded rectangle that surrounds the icon, for it to work. Then, after doing some random things with the mouse (switching focus between different windows, closing some), it behaves normally again ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: unity 7.1.2+13.10.20131014.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-18.32-generic 3.11.10.4 Uname: Linux 3.11.0-18-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' Date: Sun Mar 23 12:19:12 2014 InstallationDate: Installed on 2013-10-11 (162 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MarkForUpload: True SourcePackage: unity UpgradeStatus: Upgraded to saucy on 2014-02-23 (28 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1296253/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1277888] Re: In most apps all menu items are gray / unclickable
For god's sake, this is huge. Any workaround? -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1277888 Title: In most apps all menu items are gray / unclickable Status in Ubuntu GNOME: New Status in Unity: Invalid Status in “unity” package in Ubuntu: Invalid Bug description: In Libreoffice write for example all menu items in the gloal menu are gray and unclickable. Even stuff like "quit" or "about libreoffice". Using the keyboard shortcuts to access the items works though and it's possible to open sub-menus but nothing in them is clickable. This happens with several other apps like Gnome Terminal, Sublime Text (3 party package) and shotwell. The imagage viewer has the first menu working but not the other. Firefox seems to work. The single menu of nautilius works too. I found a smiliar bug against Libreoffice but maybe it's a different problem. https://bugs.freedesktop.org/show_bug.cgi?id=73794 See the attatched screenshot. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: unity-services 7.1.2+13.10.20131014.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-15.25-generic 3.11.10 Uname: Linux 3.11.0-15-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus.0: Error: [Errno 21] Är en katalog: '/proc/driver/nvidia/gpus/0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 331.20 Wed Oct 30 17:43:35 PDT 2013 GCC version: gcc version 4.8.1 (Ubuntu/Linaro 4.8.1-10ubuntu9) .proc.driver.nvidia.warnings.fbdev: Your system is not currently configured to drive a VGA console on the primary VGA device. The NVIDIA Linux graphics driver requires the use of a text-mode VGA console. Use of other console drivers including, but not limited to, vesafb, may result in corruption and stability problems, and is not supported. .tmp.unity.support.test.0: ApportVersion: 2.12.5-0ubuntu2.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 Date: Sat Feb 8 15:49:47 2014 DistUpgraded: Fresh install DistroCodename: saucy DistroVariant: ubuntu DkmsStatus: nvidia-331, 331.20, 3.11.0-15-generic, x86_64: installed GraphicsCard: NVIDIA Corporation GF100 [GeForce GTX 465] [10de:06c4] (rev a3) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:834c] InstallationDate: Installed on 2013-12-20 (49 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MachineType: ASUS All Series MarkForUpload: True ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-15-generic.efi.signed root=UUID=fbdd2a1c-8021-4dff-a5e6-2dd1a4173bfa ro quiet splash vt.handoff=7 SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/29/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1602 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z87-PRO dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1602:bd10/29/2013:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ87-PRO:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: All Series dmi.product.version: System Version dmi.sys.vendor: ASUS version.compiz: compiz 1:0.9.10+13.10.20131011-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.46-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.2.1-1ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.2.1-1ubuntu3 version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A version.xserver-xorg-core: xserver-xorg-core 2:1.14.5-1ubuntu2~saucy1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu3.1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.2.0-0ubuntu10 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.904-0ubuntu2.1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.9-2ubuntu1 xserver.bootTime: Sat Feb 8 14:57:11 2014 xserver.configfile: /etc/X11/xorg.conf xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.14.5-1ubuntu2~saucy1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-gnome/+bug/1277888/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@list
[Dx-packages] [Bug 1277888] Re: In most apps all menu items are gray / unclickable
Oh, ok, this one works for me: https://bugs.launchpad.net/ubuntu/+source/unity-gtk-module/+bug/1263205/comments/7 -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1277888 Title: In most apps all menu items are gray / unclickable Status in Ubuntu GNOME: New Status in Unity: Invalid Status in “unity” package in Ubuntu: Invalid Bug description: In Libreoffice write for example all menu items in the gloal menu are gray and unclickable. Even stuff like "quit" or "about libreoffice". Using the keyboard shortcuts to access the items works though and it's possible to open sub-menus but nothing in them is clickable. This happens with several other apps like Gnome Terminal, Sublime Text (3 party package) and shotwell. The imagage viewer has the first menu working but not the other. Firefox seems to work. The single menu of nautilius works too. I found a smiliar bug against Libreoffice but maybe it's a different problem. https://bugs.freedesktop.org/show_bug.cgi?id=73794 See the attatched screenshot. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: unity-services 7.1.2+13.10.20131014.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-15.25-generic 3.11.10 Uname: Linux 3.11.0-15-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus.0: Error: [Errno 21] Är en katalog: '/proc/driver/nvidia/gpus/0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 331.20 Wed Oct 30 17:43:35 PDT 2013 GCC version: gcc version 4.8.1 (Ubuntu/Linaro 4.8.1-10ubuntu9) .proc.driver.nvidia.warnings.fbdev: Your system is not currently configured to drive a VGA console on the primary VGA device. The NVIDIA Linux graphics driver requires the use of a text-mode VGA console. Use of other console drivers including, but not limited to, vesafb, may result in corruption and stability problems, and is not supported. .tmp.unity.support.test.0: ApportVersion: 2.12.5-0ubuntu2.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 Date: Sat Feb 8 15:49:47 2014 DistUpgraded: Fresh install DistroCodename: saucy DistroVariant: ubuntu DkmsStatus: nvidia-331, 331.20, 3.11.0-15-generic, x86_64: installed GraphicsCard: NVIDIA Corporation GF100 [GeForce GTX 465] [10de:06c4] (rev a3) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:834c] InstallationDate: Installed on 2013-12-20 (49 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MachineType: ASUS All Series MarkForUpload: True ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-15-generic.efi.signed root=UUID=fbdd2a1c-8021-4dff-a5e6-2dd1a4173bfa ro quiet splash vt.handoff=7 SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/29/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1602 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z87-PRO dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1602:bd10/29/2013:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ87-PRO:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: All Series dmi.product.version: System Version dmi.sys.vendor: ASUS version.compiz: compiz 1:0.9.10+13.10.20131011-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.46-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.2.1-1ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.2.1-1ubuntu3 version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A version.xserver-xorg-core: xserver-xorg-core 2:1.14.5-1ubuntu2~saucy1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu3.1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.2.0-0ubuntu10 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.904-0ubuntu2.1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.9-2ubuntu1 xserver.bootTime: Sat Feb 8 14:57:11 2014 xserver.configfile: /etc/X11/xorg.conf xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.14.5-1ubuntu2~saucy1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-gnome/+bug/1277888/+subscriptions -- Mailing lis
[Dx-packages] [Bug 1286856] [NEW] [13.10 Regression] External screen configuration wrong in login screen
Public bug reported: I have an external monitor that I usually connect to my laptop. It's configured to be the only screen, so when I plug it in, the laptop's builtin screen automagically turns off and the external screen becomes the primary and only screen, and when I unplug it, the builtin screen turns on and becomes the only screen. So far so good. In 13.04, this used to apply also to the Ubuntu login screen, that is for example, if I turned on the computer with the external monitor already connected, I would see the login screen on the external monitor only. Since I upgraded to 13.10, when the login screen appears and the external monitor is connected, the screen shows as an extended screen, so that the login box is only visible on the builtin screen and the external monitor is "empty" (with a background image). After logging in, it switches to the correct configuration (i.e. the builtin screen turns off and the external screen becomes the primary one). ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: unity 7.1.2+13.10.20131014.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-17.31-generic 3.11.10.3 Uname: Linux 3.11.0-17-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' Date: Sun Mar 2 18:18:00 2014 InstallationDate: Installed on 2013-10-11 (141 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MarkForUpload: True SourcePackage: unity UpgradeStatus: Upgraded to saucy on 2014-02-23 (7 days ago) ** Affects: unity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug saucy -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1286856 Title: [13.10 Regression] External screen configuration wrong in login screen Status in “unity” package in Ubuntu: New Bug description: I have an external monitor that I usually connect to my laptop. It's configured to be the only screen, so when I plug it in, the laptop's builtin screen automagically turns off and the external screen becomes the primary and only screen, and when I unplug it, the builtin screen turns on and becomes the only screen. So far so good. In 13.04, this used to apply also to the Ubuntu login screen, that is for example, if I turned on the computer with the external monitor already connected, I would see the login screen on the external monitor only. Since I upgraded to 13.10, when the login screen appears and the external monitor is connected, the screen shows as an extended screen, so that the login box is only visible on the builtin screen and the external monitor is "empty" (with a background image). After logging in, it switches to the correct configuration (i.e. the builtin screen turns off and the external screen becomes the primary one). ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: unity 7.1.2+13.10.20131014.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-17.31-generic 3.11.10.3 Uname: Linux 3.11.0-17-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' Date: Sun Mar 2 18:18:00 2014 InstallationDate: Installed on 2013-10-11 (141 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MarkForUpload: True SourcePackage: unity UpgradeStatus: Upgraded to saucy on 2014-02-23 (7 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1286856/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1283822] Re: clock disappeared from notification area
No, it isn't. It simply happened. ** Changed in: indicator-datetime Status: Incomplete => New -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1283822 Title: clock disappeared from notification area Status in The Date and Time Indicator: New Status in “unity” package in Ubuntu: Invalid Bug description: Suddenly I realized the clock was not there, where it usally is, on the top-right corner of the screen. I dono't know how long it was since it had disappeared; however I had restarted the computer no more than a few minutes earlier. After reboot, the clock is there again as expected. Maybe the clock widget crashed? ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: unity 7.1.2+13.10.20131014.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-17.31-generic 3.11.10.3 Uname: Linux 3.11.0-17-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' Date: Sun Feb 23 22:05:17 2014 InstallationDate: Installed on 2013-10-11 (135 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MarkForUpload: True SourcePackage: unity UpgradeStatus: Upgraded to saucy on 2014-02-23 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-datetime/+bug/1283822/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1283822] [NEW] clock disappeared from notification area
Public bug reported: Suddenly I realized the clock was not there, where it usally is, on the top-right corner of the screen. I dono't know how long it was since it had disappeared; however I had restarted the computer no more than a few minutes earlier. After reboot, the clock is there again as expected. Maybe the clock widget crashed? ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: unity 7.1.2+13.10.20131014.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-17.31-generic 3.11.10.3 Uname: Linux 3.11.0-17-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' Date: Sun Feb 23 22:05:17 2014 InstallationDate: Installed on 2013-10-11 (135 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MarkForUpload: True SourcePackage: unity UpgradeStatus: Upgraded to saucy on 2014-02-23 (0 days ago) ** Affects: unity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug saucy -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1283822 Title: clock disappeared from notification area Status in “unity” package in Ubuntu: New Bug description: Suddenly I realized the clock was not there, where it usally is, on the top-right corner of the screen. I dono't know how long it was since it had disappeared; however I had restarted the computer no more than a few minutes earlier. After reboot, the clock is there again as expected. Maybe the clock widget crashed? ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: unity 7.1.2+13.10.20131014.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-17.31-generic 3.11.10.3 Uname: Linux 3.11.0-17-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' Date: Sun Feb 23 22:05:17 2014 InstallationDate: Installed on 2013-10-11 (135 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MarkForUpload: True SourcePackage: unity UpgradeStatus: Upgraded to saucy on 2014-02-23 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1283822/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1263786] Re: Nonsense behavior of scrollwheel over Launcher
And when you know it's intentional it is annoying as well as surprising :) -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1263786 Title: Nonsense behavior of scrollwheel over Launcher Status in Unity: Fix Committed Status in “unity” package in Ubuntu: Fix Released Bug description: Steps to reproduce: - move the mouse cursor over the launcher - move it over the icon of an application that has one and only one window open that is not on front - move the scrollwheel of the mouse in any direction Expected behavior: NOTHING. Ovserved behavior: the window, corresponding to the icon over which the mouse cursor is, is brought to front; and this cannot be reversed easily. Trying it with an icon of an application that has two or more windows open reveals "why" this happens: - move the mouse cursor over the Launcher over an icon of an application that has two or more windows open - move the scrollwheel This will switch between windows of that application, so scrolling up or down will bring one or another window (of that same application) to front. This is already annoying, like many other abuses of the scrollwheel that unfortunately have become widespread (such as: moving the scrollwheel while keeping the cursor over a tab will switch among tabs in applications that use tabs). But even if we accept the annoying use-the-scrollwheel-for-everything-at-all-costs fashion, only two behaviors would make sense in this case: Option A: - similar to current behavior (switch between windows of an application) but ONLY IF there are more than one window of that application open AND one of those window is already focused. Or option B: - whenever the scrollwheel is on the launcher, scrolling would switch among ALL existing windows Both option A and B would be consistent with the widespread scrollwheel abuse, but would at least make sense, and an unintentional movement of the scrollwheel causing an undesired window switching could always be reverted by a countermovement of the scrollwheel in the opposite direction. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: unity 7.0.0daily13.06.19~13.04-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-34.49-generic 3.8.13.12 Uname: Linux 3.8.0-34-generic x86_64 ApportVersion: 2.9.2-0ubuntu8.5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' Date: Mon Dec 23 22:45:54 2013 InstallationDate: Installed on 2013-10-11 (73 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MarkForUpload: True SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1263786/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1278938] [NEW] system became unusable after resume from hibernation
Public bug reported: I resumed from hibernation. All the windows would respond to some kinds of interaction, but not others. For example: + I could bring a window to front by clicking on its launcher icon + I could unmaximize the frontmost maximized window by clicking on the top of the screen and dragging it downwards, - however I could not move around a window by dragging its title bar, - nor by alt-clicking inside the window and dragging - nor could I close a window by clicking on its close button, + I could switch window with alt+tab - but not by clicking on any window + I could "initiate" quitting a program by using its File menu -> quit, or by right-clicking on its launcher icon and choosing "quit" - but once the popup window appeared asking me whether to save or discard changes or cancel, none of the buttons would respond to clicks No process was consuming a relative amount of cpu. This got fixed only by rebooting. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: unity 7.0.0daily13.06.19~13.04-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-35.50-generic 3.8.13.13 Uname: Linux 3.8.0-35-generic x86_64 ApportVersion: 2.9.2-0ubuntu8.5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' Date: Tue Feb 11 16:28:42 2014 InstallationDate: Installed on 2013-10-11 (122 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MarkForUpload: True SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: unity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug raring -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1278938 Title: system became unusable after resume from hibernation Status in “unity” package in Ubuntu: New Bug description: I resumed from hibernation. All the windows would respond to some kinds of interaction, but not others. For example: + I could bring a window to front by clicking on its launcher icon + I could unmaximize the frontmost maximized window by clicking on the top of the screen and dragging it downwards, - however I could not move around a window by dragging its title bar, - nor by alt-clicking inside the window and dragging - nor could I close a window by clicking on its close button, + I could switch window with alt+tab - but not by clicking on any window + I could "initiate" quitting a program by using its File menu -> quit, or by right-clicking on its launcher icon and choosing "quit" - but once the popup window appeared asking me whether to save or discard changes or cancel, none of the buttons would respond to clicks No process was consuming a relative amount of cpu. This got fixed only by rebooting. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: unity 7.0.0daily13.06.19~13.04-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-35.50-generic 3.8.13.13 Uname: Linux 3.8.0-35-generic x86_64 ApportVersion: 2.9.2-0ubuntu8.5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' Date: Tue Feb 11 16:28:42 2014 InstallationDate: Installed on 2013-10-11 (122 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MarkForUpload: True SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1278938/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1263786] Re: Nonsense behavior of scrollwheel over Launcher
By the way, this is not really accurate: > your bug here only describes the case about one and only one window open, -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1263786 Title: Nonsense behavior of scrollwheel over Launcher Status in Unity: In Progress Status in “unity” package in Ubuntu: In Progress Bug description: Steps to reproduce: - move the mouse cursor over the launcher - move it over the icon of an application that has one and only one window open that is not on front - move the scrollwheel of the mouse in any direction Expected behavior: NOTHING. Ovserved behavior: the window, corresponding to the icon over which the mouse cursor is, is brought to front; and this cannot be reversed easily. Trying it with an icon of an application that has two or more windows open reveals "why" this happens: - move the mouse cursor over the Launcher over an icon of an application that has two or more windows open - move the scrollwheel This will switch between windows of that application, so scrolling up or down will bring one or another window (of that same application) to front. This is already annoying, like many other abuses of the scrollwheel that unfortunately have become widespread (such as: moving the scrollwheel while keeping the cursor over a tab will switch among tabs in applications that use tabs). But even if we accept the annoying use-the-scrollwheel-for-everything-at-all-costs fashion, only two behaviors would make sense in this case: Option A: - similar to current behavior (switch between windows of an application) but ONLY IF there are more than one window of that application open AND one of those window is already focused. Or option B: - whenever the scrollwheel is on the launcher, scrolling would switch among ALL existing windows Both option A and B would be consistent with the widespread scrollwheel abuse, but would at least make sense, and an unintentional movement of the scrollwheel causing an undesired window switching could always be reverted by a countermovement of the scrollwheel in the opposite direction. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: unity 7.0.0daily13.06.19~13.04-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-34.49-generic 3.8.13.12 Uname: Linux 3.8.0-34-generic x86_64 ApportVersion: 2.9.2-0ubuntu8.5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' Date: Mon Dec 23 22:45:54 2013 InstallationDate: Installed on 2013-10-11 (73 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MarkForUpload: True SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1263786/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1081843] Re: [FFe] Launcher, Window Management - More Effective window switching for apps with multiple windows using the Launcher
Oh my god, point (1) was by design! """If the application *is not* in focus when the user moves their pointer over the Launcher app icon, the first mouse wheel click towards or away from the user should focus the application, and bring the top most window in the application's z stack to the front of the global z stack. Subsequent clicks of the mouse wheel the operate exactly as described above""" For god's sake, this part needs to be reconsidered. There is a basic principle in the way mouse wheel interaction has ALWAYS worked EVERYWHERE and you're breaking it here, and it's not a good innovation. The mousewheel is used to move "something" forward and backward, and if you move it forwards and then backwards (or viceversa) of an equal amount, you go back to the original status. Think about the way it is used for scrolling a page, or zooming in and out in an image editor, or (I hate it but unfortunately it's become widespread) switching between tabs in a browser, or between choices in a dropdown menu (even without unfolding it, regrettably, but again that's become popular). In all cases, the rule is never broken: if you move one step too much in one direction, either intentionally or accidentally (the latter being very common) you can always go back by moving the wheel one step in the following direction. Now even if point 2 gets fixed , which is clearly a bug and contraddicts the "requirements" stated in this request (see #1263786), you are still breaking the "reversibility" of mouse wheel movements. -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1081843 Title: [FFe] Launcher, Window Management - More Effective window switching for apps with multiple windows using the Launcher Status in Ayatana Design: Fix Released Status in Unity: Fix Released Status in “unity” package in Ubuntu: Fix Released Bug description: It would be very useful if you could simply hover over an icon of an open app and scroll with the mouse wheel to switch and highlight between the windows of that app, if it has more. - Desired resolution: Try implementing the following as an experiment. Before the change described below lands in Ubuntu *it must first be user tested, and reviewed by the design team* If the pointer is positioned over the Launcher icon of an application that is in focus which has multiple windows open in the following order A,B,C,D,E: - Scrolling the mouse wheel 'one click towards the user' should display the next window (B) of the application in the Z stack. e.g. Starting Z stack order: A,B,C,D,E Output Z stack order: B,A,C,D,E - Scrolling the mouse wheel 'one click away from the user' should display the bottom window (E) in the application in the Z stack Starting Z stack order: A,B,C,D,E Output Z stack order: E,A,B,C,D - Scrolling the mouse wheel 'two clicks towards the user' should first briefly display the next window of the application in the Z stack (window B) after the first mousewheel click, and then on the second mousewheel click return window B to it's previous position in the z-stack and display window C. Starting Z stack order: A,B,C,D,E Output Z stack order: C,A,B,D,E - Scrolling the mouse wheel 'two clicks away from the user' should first briefly display the bottom window of the application in the Z stack (window E) after the first mousewheel click, and then on the second mousewheel click return window E to it's previous position in the z-stack and display the next most bottom window, window D. Starting Z stack order: A,B,C,D,E Output Z stack order: D,A,B,C,E - Scrolling the mouse wheel 'three clicks towards the user' should first briefly display the next window of the application in the Z stack (window B) after the first mousewheel click, and then return window B to it's previous position in the z-stack and briefly display the next window of the application in the Z stack (window C) after the second mousewheel click, and then on the third mousewheel click return window C to it's previous position in the z-stack and display window D. Starting Z stack order: A,B,C,D,E Output Z stack order: D,A,B,C,E - etc, etc... for more windows and more mouse wheel clicks in either direction. If the application *is not* in focus when the user moves their pointer over the Launcher app icon, the first mouse wheel click towards or away from the user should focus the application, and bring the top most window in the application's z stack to the front of the global z stack. Subsequent clicks of the mouse wheel the operate exactly as described above. If the application is not running, or has only one open window mouse wheel cl
[Dx-packages] [Bug 1263786] Re: Nonsense behavior of scrollwheel over Launcher
> "If the application *is not* in focus when the user moves their pointer over the Launcher app icon, the first mouse wheel click towards or away from the user should focus the application, and bring the top most window in the application's z stack to the front of the global z stack. " OMFG, I can't believe that was by design. That's simply demential. -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1263786 Title: Nonsense behavior of scrollwheel over Launcher Status in Unity: In Progress Status in “unity” package in Ubuntu: In Progress Bug description: Steps to reproduce: - move the mouse cursor over the launcher - move it over the icon of an application that has one and only one window open that is not on front - move the scrollwheel of the mouse in any direction Expected behavior: NOTHING. Ovserved behavior: the window, corresponding to the icon over which the mouse cursor is, is brought to front; and this cannot be reversed easily. Trying it with an icon of an application that has two or more windows open reveals "why" this happens: - move the mouse cursor over the Launcher over an icon of an application that has two or more windows open - move the scrollwheel This will switch between windows of that application, so scrolling up or down will bring one or another window (of that same application) to front. This is already annoying, like many other abuses of the scrollwheel that unfortunately have become widespread (such as: moving the scrollwheel while keeping the cursor over a tab will switch among tabs in applications that use tabs). But even if we accept the annoying use-the-scrollwheel-for-everything-at-all-costs fashion, only two behaviors would make sense in this case: Option A: - similar to current behavior (switch between windows of an application) but ONLY IF there are more than one window of that application open AND one of those window is already focused. Or option B: - whenever the scrollwheel is on the launcher, scrolling would switch among ALL existing windows Both option A and B would be consistent with the widespread scrollwheel abuse, but would at least make sense, and an unintentional movement of the scrollwheel causing an undesired window switching could always be reverted by a countermovement of the scrollwheel in the opposite direction. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: unity 7.0.0daily13.06.19~13.04-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-34.49-generic 3.8.13.12 Uname: Linux 3.8.0-34-generic x86_64 ApportVersion: 2.9.2-0ubuntu8.5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' Date: Mon Dec 23 22:45:54 2013 InstallationDate: Installed on 2013-10-11 (73 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MarkForUpload: True SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1263786/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1263786] Re: Nonsense behavior of scrollwheel over Launcher
That requirement is not complete. It should be changed to: "If the application is not running, or has only one open window, OR IS NOT FOCUSED, mouse wheel clicking towards or away from the user when the pointer is over the application's launcher icon should do nothing." Mouse wheel should only allow switching windows between an already focused app. Or, a completely different acceptable alternative to the current behavior, would be that mouse wheel over the launcher (regardless of which icon the cursor is on) would switch among _all_ open windows, of all apps. What is definitely wrong is that: - you move the cursor over an app that doesn't have focus (whether or not it has more than one window) - you move the mouse wheel => some window of that app gets focus stealing focus from the current app. Then the wheel will only allow you to switch between windows of that newly focused app but you won't be able to go back to the previously focused app by reversing your mouse wheel movement. All this can is even implicit in the words "switch between". "Switching between open windows of an app" means "switch from an open window of that app to another open window of that app". So, if focus is not on any window of that app in the first place, moving the mouse wheel while the cursor is over its icon should do nothing. -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1263786 Title: Nonsense behavior of scrollwheel over Launcher Status in Unity: In Progress Status in “unity” package in Ubuntu: In Progress Bug description: Steps to reproduce: - move the mouse cursor over the launcher - move it over the icon of an application that has one and only one window open that is not on front - move the scrollwheel of the mouse in any direction Expected behavior: NOTHING. Ovserved behavior: the window, corresponding to the icon over which the mouse cursor is, is brought to front; and this cannot be reversed easily. Trying it with an icon of an application that has two or more windows open reveals "why" this happens: - move the mouse cursor over the Launcher over an icon of an application that has two or more windows open - move the scrollwheel This will switch between windows of that application, so scrolling up or down will bring one or another window (of that same application) to front. This is already annoying, like many other abuses of the scrollwheel that unfortunately have become widespread (such as: moving the scrollwheel while keeping the cursor over a tab will switch among tabs in applications that use tabs). But even if we accept the annoying use-the-scrollwheel-for-everything-at-all-costs fashion, only two behaviors would make sense in this case: Option A: - similar to current behavior (switch between windows of an application) but ONLY IF there are more than one window of that application open AND one of those window is already focused. Or option B: - whenever the scrollwheel is on the launcher, scrolling would switch among ALL existing windows Both option A and B would be consistent with the widespread scrollwheel abuse, but would at least make sense, and an unintentional movement of the scrollwheel causing an undesired window switching could always be reverted by a countermovement of the scrollwheel in the opposite direction. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: unity 7.0.0daily13.06.19~13.04-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-34.49-generic 3.8.13.12 Uname: Linux 3.8.0-34-generic x86_64 ApportVersion: 2.9.2-0ubuntu8.5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' Date: Mon Dec 23 22:45:54 2013 InstallationDate: Installed on 2013-10-11 (73 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MarkForUpload: True SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1263786/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1081843] Re: [FFe] Launcher, Window Management - More Effective window switching for apps with multiple windows using the Launcher
It's broken in that: 1 - if you hover the icon of an app OTHER THAN THE ONE CURRENTLY FOCUSED and move the scrollwheel, you'll steal focus from the currently focused app and give it to another. And that is not reversible by moving back the scrollwheel. In other words, this should only work on the icon of the app that currently has focus. . And as a special case particularly annoying: 2 - this even happens if you hover on an icon of an app that HAS ONLY ONE WINDOW and move the scrollwheel. -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1081843 Title: [FFe] Launcher, Window Management - More Effective window switching for apps with multiple windows using the Launcher Status in Ayatana Design: Fix Released Status in Unity: Fix Released Status in “unity” package in Ubuntu: Fix Released Bug description: It would be very useful if you could simply hover over an icon of an open app and scroll with the mouse wheel to switch and highlight between the windows of that app, if it has more. - Desired resolution: Try implementing the following as an experiment. Before the change described below lands in Ubuntu *it must first be user tested, and reviewed by the design team* If the pointer is positioned over the Launcher icon of an application that is in focus which has multiple windows open in the following order A,B,C,D,E: - Scrolling the mouse wheel 'one click towards the user' should display the next window (B) of the application in the Z stack. e.g. Starting Z stack order: A,B,C,D,E Output Z stack order: B,A,C,D,E - Scrolling the mouse wheel 'one click away from the user' should display the bottom window (E) in the application in the Z stack Starting Z stack order: A,B,C,D,E Output Z stack order: E,A,B,C,D - Scrolling the mouse wheel 'two clicks towards the user' should first briefly display the next window of the application in the Z stack (window B) after the first mousewheel click, and then on the second mousewheel click return window B to it's previous position in the z-stack and display window C. Starting Z stack order: A,B,C,D,E Output Z stack order: C,A,B,D,E - Scrolling the mouse wheel 'two clicks away from the user' should first briefly display the bottom window of the application in the Z stack (window E) after the first mousewheel click, and then on the second mousewheel click return window E to it's previous position in the z-stack and display the next most bottom window, window D. Starting Z stack order: A,B,C,D,E Output Z stack order: D,A,B,C,E - Scrolling the mouse wheel 'three clicks towards the user' should first briefly display the next window of the application in the Z stack (window B) after the first mousewheel click, and then return window B to it's previous position in the z-stack and briefly display the next window of the application in the Z stack (window C) after the second mousewheel click, and then on the third mousewheel click return window C to it's previous position in the z-stack and display window D. Starting Z stack order: A,B,C,D,E Output Z stack order: D,A,B,C,E - etc, etc... for more windows and more mouse wheel clicks in either direction. If the application *is not* in focus when the user moves their pointer over the Launcher app icon, the first mouse wheel click towards or away from the user should focus the application, and bring the top most window in the application's z stack to the front of the global z stack. Subsequent clicks of the mouse wheel the operate exactly as described above. If the application is not running, or has only one open window mouse wheel clicking towards or away from the user when the pointer is over the application's launcher icon should do nothing. Because this behaviour will conflict with the current use of the mouse wheel to scroll the launcher, the mouse wheel launcher scroll should be changed to only work when the ALT key is held down. e.g. to scroll the launcher with the mouse wheel the user will have to press ALT + MOUSEWHEEL UP or press ALT + MOUSEWHEEL DOWN - Additional test case defining the interaction with minimised windows: hyia, minimised windows should be at the back of the stack. So if App 1 has have windows A, B, and C (stacking order) and you minimise window A, and then focus App 2, when you move your pointer over the launcher icon of App 2 and scroll the mousewheel one click, window B should appear. Moving the mouse wheel one more click should then show window C. Moving the mouse wheel one more click should then show window A. Moving the mouse wheel one more click should th
[Dx-packages] [Bug 1081843] Re: [FFe] Launcher, Window Management - More Effective window switching for apps with multiple windows using the Launcher
Note that the implementation of this feature is broken. See https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1263786 -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1081843 Title: [FFe] Launcher, Window Management - More Effective window switching for apps with multiple windows using the Launcher Status in Ayatana Design: Fix Released Status in Unity: Fix Released Status in “unity” package in Ubuntu: Fix Released Bug description: It would be very useful if you could simply hover over an icon of an open app and scroll with the mouse wheel to switch and highlight between the windows of that app, if it has more. - Desired resolution: Try implementing the following as an experiment. Before the change described below lands in Ubuntu *it must first be user tested, and reviewed by the design team* If the pointer is positioned over the Launcher icon of an application that is in focus which has multiple windows open in the following order A,B,C,D,E: - Scrolling the mouse wheel 'one click towards the user' should display the next window (B) of the application in the Z stack. e.g. Starting Z stack order: A,B,C,D,E Output Z stack order: B,A,C,D,E - Scrolling the mouse wheel 'one click away from the user' should display the bottom window (E) in the application in the Z stack Starting Z stack order: A,B,C,D,E Output Z stack order: E,A,B,C,D - Scrolling the mouse wheel 'two clicks towards the user' should first briefly display the next window of the application in the Z stack (window B) after the first mousewheel click, and then on the second mousewheel click return window B to it's previous position in the z-stack and display window C. Starting Z stack order: A,B,C,D,E Output Z stack order: C,A,B,D,E - Scrolling the mouse wheel 'two clicks away from the user' should first briefly display the bottom window of the application in the Z stack (window E) after the first mousewheel click, and then on the second mousewheel click return window E to it's previous position in the z-stack and display the next most bottom window, window D. Starting Z stack order: A,B,C,D,E Output Z stack order: D,A,B,C,E - Scrolling the mouse wheel 'three clicks towards the user' should first briefly display the next window of the application in the Z stack (window B) after the first mousewheel click, and then return window B to it's previous position in the z-stack and briefly display the next window of the application in the Z stack (window C) after the second mousewheel click, and then on the third mousewheel click return window C to it's previous position in the z-stack and display window D. Starting Z stack order: A,B,C,D,E Output Z stack order: D,A,B,C,E - etc, etc... for more windows and more mouse wheel clicks in either direction. If the application *is not* in focus when the user moves their pointer over the Launcher app icon, the first mouse wheel click towards or away from the user should focus the application, and bring the top most window in the application's z stack to the front of the global z stack. Subsequent clicks of the mouse wheel the operate exactly as described above. If the application is not running, or has only one open window mouse wheel clicking towards or away from the user when the pointer is over the application's launcher icon should do nothing. Because this behaviour will conflict with the current use of the mouse wheel to scroll the launcher, the mouse wheel launcher scroll should be changed to only work when the ALT key is held down. e.g. to scroll the launcher with the mouse wheel the user will have to press ALT + MOUSEWHEEL UP or press ALT + MOUSEWHEEL DOWN - Additional test case defining the interaction with minimised windows: hyia, minimised windows should be at the back of the stack. So if App 1 has have windows A, B, and C (stacking order) and you minimise window A, and then focus App 2, when you move your pointer over the launcher icon of App 2 and scroll the mousewheel one click, window B should appear. Moving the mouse wheel one more click should then show window C. Moving the mouse wheel one more click should then show window A. Moving the mouse wheel one more click should then show window B. Moving the pointer so that it is no longer over the launcher icon of app A at this point should focus window B. Window A should remain minimised. To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/1081843/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.lau
[Dx-packages] [Bug 1263786] Re: Nonsense behavior of scrollwheel over Launcher
No, this is not the opposite of that at all. Please read the description of that request more carefully: (emphasys added) Title: "Launcher, Window Management - More Effective window switching FOR APPS WITH MULTIPLE WINDOWS using the Launcher" Description: "It would be very useful if you could simply hover over an icon of an open app and scroll with the mouse wheel to switch and highlight BETWEEN THE WINDOWS OF THAT APP, *IF IT HAS MORE*". -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1263786 Title: Nonsense behavior of scrollwheel over Launcher Status in “unity” package in Ubuntu: Opinion Bug description: Steps to reproduce: - move the mouse cursor over the launcher - move it over the icon of an application that has one and only one window open that is not on front - move the scrollwheel of the mouse in any direction Expected behavior: NOTHING. Ovserved behavior: the window, corresponding to the icon over which the mouse cursor is, is brought to front; and this cannot be reversed easily. Trying it with an icon of an application that has two or more windows open reveals "why" this happens: - move the mouse cursor over the Launcher over an icon of an application that has two or more windows open - move the scrollwheel This will switch between windows of that application, so scrolling up or down will bring one or another window (of that same application) to front. This is already annoying, like many other abuses of the scrollwheel that unfortunately have become widespread (such as: moving the scrollwheel while keeping the cursor over a tab will switch among tabs in applications that use tabs). But even if we accept the annoying use-the-scrollwheel-for-everything-at-all-costs fashion, only two behaviors would make sense in this case: Option A: - similar to current behavior (switch between windows of an application) but ONLY IF there are more than one window of that application open AND one of those window is already focused. Or option B: - whenever the scrollwheel is on the launcher, scrolling would switch among ALL existing windows Both option A and B would be consistent with the widespread scrollwheel abuse, but would at least make sense, and an unintentional movement of the scrollwheel causing an undesired window switching could always be reverted by a countermovement of the scrollwheel in the opposite direction. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: unity 7.0.0daily13.06.19~13.04-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-34.49-generic 3.8.13.12 Uname: Linux 3.8.0-34-generic x86_64 ApportVersion: 2.9.2-0ubuntu8.5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' Date: Mon Dec 23 22:45:54 2013 InstallationDate: Installed on 2013-10-11 (73 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MarkForUpload: True SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1263786/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1263786] Re: Nonsense behavior of scrollwheel over Launcher
According to your reasoning, and as I already mentioned in my report, the current behavior makes perfect sense WHEN THE ICON HAS MORE THAN ONE WINDOW and one of them is already the one with focus. That is: put the mouse cursor on an icon that has more than one window, one of which has already focus. Move the scrollwheel. It switches windows. Ok, makes sense (given the "use the mouse wheel to switch between multiple-data display element in a GUI", which is a shitty way of using the mouse wheel that regretfully has become widespread, but if we accept that, it's consistent). Now put the mouse cursor on a random icon on the launcher which has only one window (there's no data elements to switch between at all). Move the mouse wheel => that window gets focus, and you can't give focus back to the window that previously had it unless you look for it and click on it. That does not make sense and it is an annoyance. You don't expect the current application to be switched without a positive click: well that's exactly what happens: current application is switched with just a movement of the mouse wheel over the icon of another application. Having the mousewheel cycle through icons in the whole launcher would make as much sense as it makes to cycle through tabs within a window when you place the mouse cursor over any tab of e.g. Google Chrome or Ubuntu's Terminal and move the scrollwheel: something that I hate and I would happily get rid of, but it is kind of consistent in that, if you do that by accident, you can "go back" by moving the wheel back. -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1263786 Title: Nonsense behavior of scrollwheel over Launcher Status in “unity” package in Ubuntu: New Bug description: Steps to reproduce: - move the mouse cursor over the launcher - move it over the icon of an application that has one and only one window open that is not on front - move the scrollwheel of the mouse in any direction Expected behavior: NOTHING. Ovserved behavior: the window, corresponding to the icon over which the mouse cursor is, is brought to front; and this cannot be reversed easily. Trying it with an icon of an application that has two or more windows open reveals "why" this happens: - move the mouse cursor over the Launcher over an icon of an application that has two or more windows open - move the scrollwheel This will switch between windows of that application, so scrolling up or down will bring one or another window (of that same application) to front. This is already annoying, like many other abuses of the scrollwheel that unfortunately have become widespread (such as: moving the scrollwheel while keeping the cursor over a tab will switch among tabs in applications that use tabs). But even if we accept the annoying use-the-scrollwheel-for-everything-at-all-costs fashion, only two behaviors would make sense in this case: Option A: - similar to current behavior (switch between windows of an application) but ONLY IF there are more than one window of that application open AND one of those window is already focused. Or option B: - whenever the scrollwheel is on the launcher, scrolling would switch among ALL existing windows Both option A and B would be consistent with the widespread scrollwheel abuse, but would at least make sense, and an unintentional movement of the scrollwheel causing an undesired window switching could always be reverted by a countermovement of the scrollwheel in the opposite direction. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: unity 7.0.0daily13.06.19~13.04-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-34.49-generic 3.8.13.12 Uname: Linux 3.8.0-34-generic x86_64 ApportVersion: 2.9.2-0ubuntu8.5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' Date: Mon Dec 23 22:45:54 2013 InstallationDate: Installed on 2013-10-11 (73 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MarkForUpload: True SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1263786/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1263786] [NEW] Nonsense behavior of scrollwheel over Launcher
Public bug reported: Steps to reproduce: - move the mouse cursor over the launcher - move it over the icon of an application that has one and only one window open that is not on front - move the scrollwheel of the mouse in any direction Expected behavior: NOTHING. Ovserved behavior: the window, corresponding to the icon over which the mouse cursor is, is brought to front; and this cannot be reversed easily. Trying it with an icon of an application that has two or more windows open reveals "why" this happens: - move the mouse cursor over the Launcher over an icon of an application that has two or more windows open - move the scrollwheel This will switch between windows of that application, so scrolling up or down will bring one or another window (of that same application) to front. This is already annoying, like many other abuses of the scrollwheel that unfortunately have become widespread (such as: moving the scrollwheel while keeping the cursor over a tab will switch among tabs in applications that use tabs). But even if we accept the annoying use-the-scrollwheel-for-everything-at-all-costs fashion, only two behaviors would make sense in this case: Option A: - similar to current behavior (switch between windows of an application) but ONLY IF there are more than one window of that application open AND one of those window is already focused. Or option B: - whenever the scrollwheel is on the launcher, scrolling would switch among ALL existing windows Both option A and B would be consistent with the widespread scrollwheel abuse, but would at least make sense, and an unintentional movement of the scrollwheel causing an undesired window switching could always be reverted by a countermovement of the scrollwheel in the opposite direction. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: unity 7.0.0daily13.06.19~13.04-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-34.49-generic 3.8.13.12 Uname: Linux 3.8.0-34-generic x86_64 ApportVersion: 2.9.2-0ubuntu8.5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' Date: Mon Dec 23 22:45:54 2013 InstallationDate: Installed on 2013-10-11 (73 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MarkForUpload: True SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: unity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug raring -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1263786 Title: Nonsense behavior of scrollwheel over Launcher Status in “unity” package in Ubuntu: New Bug description: Steps to reproduce: - move the mouse cursor over the launcher - move it over the icon of an application that has one and only one window open that is not on front - move the scrollwheel of the mouse in any direction Expected behavior: NOTHING. Ovserved behavior: the window, corresponding to the icon over which the mouse cursor is, is brought to front; and this cannot be reversed easily. Trying it with an icon of an application that has two or more windows open reveals "why" this happens: - move the mouse cursor over the Launcher over an icon of an application that has two or more windows open - move the scrollwheel This will switch between windows of that application, so scrolling up or down will bring one or another window (of that same application) to front. This is already annoying, like many other abuses of the scrollwheel that unfortunately have become widespread (such as: moving the scrollwheel while keeping the cursor over a tab will switch among tabs in applications that use tabs). But even if we accept the annoying use-the-scrollwheel-for-everything-at-all-costs fashion, only two behaviors would make sense in this case: Option A: - similar to current behavior (switch between windows of an application) but ONLY IF there are more than one window of that application open AND one of those window is already focused. Or option B: - whenever the scrollwheel is on the launcher, scrolling would switch among ALL existing windows Both option A and B would be consistent with the widespread scrollwheel abuse, but would at least make sense, and an unintentional movement of the scrollwheel causing an undesired window switching could always be reverted by a countermovement of the scrollwheel in the opposite direction. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: unity 7.0.0daily13.06.19~13.04-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-34.49-generic 3.8.13.12 Uname: Linux 3.8.0-34-generic x86_64 ApportVersion: 2.9.2-0ubuntu8.5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' Date: Mon Dec 23 22:45:54 2013
[Dx-packages] [Bug 1263197] [NEW] bluetooth turned off without a reason
Public bug reported: I turned on my computer and the bluetooth icon in the notification area was not present. It usually is. So I launched "Bluetooth" from the dash, and Bluetooth was turned off. I turned on, so the icon on the notification area appeared. The question is why it got turned off if it used to be always turned on by default ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: indicator-bluetooth 0.0.6daily13.02.19-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-34.49-generic 3.8.13.12 Uname: Linux 3.8.0-34-generic x86_64 ApportVersion: 2.9.2-0ubuntu8.5 Architecture: amd64 Date: Fri Dec 20 19:02:08 2013 InstallationDate: Installed on 2013-10-11 (70 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MarkForUpload: True SourcePackage: indicator-bluetooth UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: indicator-bluetooth (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug raring -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-bluetooth in Ubuntu. https://bugs.launchpad.net/bugs/1263197 Title: bluetooth turned off without a reason Status in “indicator-bluetooth” package in Ubuntu: New Bug description: I turned on my computer and the bluetooth icon in the notification area was not present. It usually is. So I launched "Bluetooth" from the dash, and Bluetooth was turned off. I turned on, so the icon on the notification area appeared. The question is why it got turned off if it used to be always turned on by default ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: indicator-bluetooth 0.0.6daily13.02.19-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-34.49-generic 3.8.13.12 Uname: Linux 3.8.0-34-generic x86_64 ApportVersion: 2.9.2-0ubuntu8.5 Architecture: amd64 Date: Fri Dec 20 19:02:08 2013 InstallationDate: Installed on 2013-10-11 (70 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MarkForUpload: True SourcePackage: indicator-bluetooth UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-bluetooth/+bug/1263197/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1254106] Re: "browse files" on device does nothing
(the hcidump itself confirms it) ** Changed in: nautilus (Ubuntu) Status: New => Confirmed ** Package changed: nautilus (Ubuntu) => indicator-bluetooth (Ubuntu) -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-bluetooth in Ubuntu. https://bugs.launchpad.net/bugs/1254106 Title: "browse files" on device does nothing Status in “indicator-bluetooth” package in Ubuntu: Confirmed Bug description: I click on the Bluetooth icon on the top-right corner of the screen next to the battery icon My mobile phone is listed in the drop down. I select it and I click on "Browse files" Expected: a Nautilus window should appear showing the browsable contents of the device. Maybe the device should prompt me whether to allow browsing before Observed: ABSOLUTELY NOTHING happens. The computer doesn't even try to connect to the phone. Nothing happens on the phone, nothing happens on the computer; no error message is shown anywhere, it's just as if I had done nothing. I've done an hcidump while trying this, and it's empty. This HAD WORKED BEFORE on the same machine and with the same device. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: bluetooth (not installed) ProcVersionSignature: Ubuntu 3.8.0-33.48-generic 3.8.13.11 Uname: Linux 3.8.0-33-generic x86_64 ApportVersion: 2.9.2-0ubuntu8.5 Architecture: amd64 Date: Fri Nov 22 17:53:08 2013 InstallationDate: Installed on 2013-10-11 (41 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) InterestingModules: bnep rfcomm btusb bluetooth MachineType: Acer Aspire V3-571G MarkForUpload: True ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-33-generic root=UUID=5830b30e-69e8-4bb4-8a2b-bc2b43c7414a ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/15/2012 dmi.bios.vendor: Acer dmi.bios.version: V2.07 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: VA50_HC_CR dmi.board.vendor: Acer dmi.board.version: Type2 - Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V2.07 dmi.modalias: dmi:bvnAcer:bvrV2.07:bd10/15/2012:svnAcer:pnAspireV3-571G:pvrV2.07:rvnAcer:rnVA50_HC_CR:rvrType2-BoardVersion:cvnAcer:ct10:cvrV2.07: dmi.product.name: Aspire V3-571G dmi.product.version: V2.07 dmi.sys.vendor: Acer hciconfig: hci0:Type: BR/EDR Bus: USB BD Address: A4:17:31:0D:4A:70 ACL MTU: 1022:8 SCO MTU: 183:5 UP RUNNING PSCAN ISCAN RX bytes:549 acl:0 sco:0 events:31 errors:0 TX bytes:1168 acl:0 sco:0 commands:31 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-bluetooth/+bug/1254106/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1261217] Re: screen gets full of small horizontal black segments at random times
To apport's question "Is the issue purely graphical? (it will be reported against Compiz" I answered "yes", so I don't understand why it has been reported against Unity allthesame -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1261217 Title: screen gets full of small horizontal black segments at random times Status in “unity” package in Ubuntu: New Bug description: Since the last reboot, from time to time, randomly, the screen gets filled of short vertical black lines (segments), for a fraction of a second or few seconds, then gets back to normal. Now a few minutes have passed and apparently it has stopped doing it. Prior to this last reboot some updates had been installed (that's why I had to reboot), and I had never ever seen this happen before, so this may be a regression in some recent update. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: unity 7.0.0daily13.06.19~13.04-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-34.49-generic 3.8.13.12 Uname: Linux 3.8.0-34-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.9.2-0ubuntu8.5 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: Sun Dec 15 21:37:06 2013 DistUpgraded: Fresh install DistroCodename: raring DistroVariant: ubuntu DkmsStatus: vboxhost, 4.3.2, 3.8.0-32-generic, x86_64: installed vboxhost, 4.3.2, 3.8.0-33-generic, x86_64: installed vboxhost, 4.3.2, 3.8.0-34-generic, x86_64: installed GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Device [1025:0647] NVIDIA Corporation GF117M [GeForce 610M/710M / GT 620M/625M/630M/720M] [10de:1140] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] GeForce 710M [1025:0691] InstallationDate: Installed on 2013-10-11 (65 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MachineType: Acer Aspire V3-571G MarkForUpload: True ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-34-generic root=UUID=5830b30e-69e8-4bb4-8a2b-bc2b43c7414a ro quiet splash vt.handoff=7 SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/15/2012 dmi.bios.vendor: Acer dmi.bios.version: V2.07 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: VA50_HC_CR dmi.board.vendor: Acer dmi.board.version: Type2 - Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V2.07 dmi.modalias: dmi:bvnAcer:bvrV2.07:bd10/15/2012:svnAcer:pnAspireV3-571G:pvrV2.07:rvnAcer:rnVA50_HC_CR:rvrType2-BoardVersion:cvnAcer:ct10:cvrV2.07: dmi.product.name: Aspire V3-571G dmi.product.version: V2.07 dmi.sys.vendor: Acer version.compiz: compiz 1:0.9.9~daily13.06.19~13.04-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.43-0ubuntu1.1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.1.7-1ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.1.7-1ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.13.3-0ubuntu6.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2b2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.1.0-0ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.21.6-0ubuntu4.3 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.7-0ubuntu1 xserver.bootTime: Sun Dec 15 21:10:19 2013 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.13.3-0ubuntu6.2 xserver.video_driver: intel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1261217/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1261217] [NEW] screen gets full of small horizontal black segments at random times
Public bug reported: Since the last reboot, from time to time, randomly, the screen gets filled of short vertical black lines (segments), for a fraction of a second or few seconds, then gets back to normal. Now a few minutes have passed and apparently it has stopped doing it. Prior to this last reboot some updates had been installed (that's why I had to reboot), and I had never ever seen this happen before, so this may be a regression in some recent update. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: unity 7.0.0daily13.06.19~13.04-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-34.49-generic 3.8.13.12 Uname: Linux 3.8.0-34-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.9.2-0ubuntu8.5 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: Sun Dec 15 21:37:06 2013 DistUpgraded: Fresh install DistroCodename: raring DistroVariant: ubuntu DkmsStatus: vboxhost, 4.3.2, 3.8.0-32-generic, x86_64: installed vboxhost, 4.3.2, 3.8.0-33-generic, x86_64: installed vboxhost, 4.3.2, 3.8.0-34-generic, x86_64: installed GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Device [1025:0647] NVIDIA Corporation GF117M [GeForce 610M/710M / GT 620M/625M/630M/720M] [10de:1140] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] GeForce 710M [1025:0691] InstallationDate: Installed on 2013-10-11 (65 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MachineType: Acer Aspire V3-571G MarkForUpload: True ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-34-generic root=UUID=5830b30e-69e8-4bb4-8a2b-bc2b43c7414a ro quiet splash vt.handoff=7 SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/15/2012 dmi.bios.vendor: Acer dmi.bios.version: V2.07 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: VA50_HC_CR dmi.board.vendor: Acer dmi.board.version: Type2 - Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V2.07 dmi.modalias: dmi:bvnAcer:bvrV2.07:bd10/15/2012:svnAcer:pnAspireV3-571G:pvrV2.07:rvnAcer:rnVA50_HC_CR:rvrType2-BoardVersion:cvnAcer:ct10:cvrV2.07: dmi.product.name: Aspire V3-571G dmi.product.version: V2.07 dmi.sys.vendor: Acer version.compiz: compiz 1:0.9.9~daily13.06.19~13.04-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.43-0ubuntu1.1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.1.7-1ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.1.7-1ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.13.3-0ubuntu6.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2b2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.1.0-0ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.21.6-0ubuntu4.3 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.7-0ubuntu1 xserver.bootTime: Sun Dec 15 21:10:19 2013 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.13.3-0ubuntu6.2 xserver.video_driver: intel ** Affects: unity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 raring ubuntu -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1261217 Title: screen gets full of small horizontal black segments at random times Status in “unity” package in Ubuntu: New Bug description: Since the last reboot, from time to time, randomly, the screen gets filled of short vertical black lines (segments), for a fraction of a second or few seconds, then gets back to normal. Now a few minutes have passed and apparently it has stopped doing it. Prior to this last reboot some updates had been installed (that's why I had to reboot), and I had never ever seen this happen before, so this may be a regression in some recent update. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: unity 7.0.0daily13.06.19~13.04-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-34.49-generic 3.8.13.12 Uname: Linux 3.8.0-34-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.9.2-0ubuntu8.5 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: Sun Dec 15 21:37:06 2013 DistUpgraded: Fresh install DistroCodename: raring DistroVariant: ubuntu DkmsStatus: vboxhost, 4.3.2, 3.8.0-32-generic, x86_6
[Dx-packages] [Bug 1259625] [NEW] Whole system stops responding because of a single buggy application
Public bug reported: As per this bug report: https://bugs.freedesktop.org/show_bug.cgi?id=72569 there's a bug in LibreOffice that causes it to stop responding in certain reproducible situations. The relevant thing here is that the WHOLE SYSTEM stops responding and you can't even switch window, open a terminal, or close the offending application, in this case Libre OFfice. If a single buggy (or even malicious) application can cause the whole system to become unusable, there is a bug in the system itself. I can switch to a virtual console with ctrl+alt+f1 and kill the offending libreOffice process in this case, so I guess the issue is somewhere between Unity and X, rather than in linux. But this is only a guess. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: unity 7.0.0daily13.06.19~13.04-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-33.48-generic 3.8.13.11 Uname: Linux 3.8.0-33-generic x86_64 ApportVersion: 2.9.2-0ubuntu8.5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' Date: Tue Dec 10 17:38:35 2013 InstallationDate: Installed on 2013-10-11 (59 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MarkForUpload: True SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: unity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug raring -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1259625 Title: Whole system stops responding because of a single buggy application Status in “unity” package in Ubuntu: New Bug description: As per this bug report: https://bugs.freedesktop.org/show_bug.cgi?id=72569 there's a bug in LibreOffice that causes it to stop responding in certain reproducible situations. The relevant thing here is that the WHOLE SYSTEM stops responding and you can't even switch window, open a terminal, or close the offending application, in this case Libre OFfice. If a single buggy (or even malicious) application can cause the whole system to become unusable, there is a bug in the system itself. I can switch to a virtual console with ctrl+alt+f1 and kill the offending libreOffice process in this case, so I guess the issue is somewhere between Unity and X, rather than in linux. But this is only a guess. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: unity 7.0.0daily13.06.19~13.04-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-33.48-generic 3.8.13.11 Uname: Linux 3.8.0-33-generic x86_64 ApportVersion: 2.9.2-0ubuntu8.5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' Date: Tue Dec 10 17:38:35 2013 InstallationDate: Installed on 2013-10-11 (59 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MarkForUpload: True SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1259625/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1244366] Re: no easy way to disable screensaver on 12.04 without installing additional tools
Even after uninstalling gnome-screensaver, the screen still turns off!!! (or blanks to black, can't tell). THIS IS DAMN ANNOYING. How many layers of screen-saving are necessary? Must they be hidden to normal users so one has to google around and figure out awkward commands to write in a terminal until one manages to disable all existing damn screensavers? For god's sake! -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1244366 Title: no easy way to disable screensaver on 12.04 without installing additional tools Status in “unity” package in Ubuntu: New Bug description: I think this got fixed in some later version, but 12.04 is supposed to be LTS, right? So unless I misunderstand the meaning of the S in the acronym, the fix needs to be made available to 12.04 via updates. Here's the issue: have a fresh install of 12.04. After a given time of inactivity, the screen turns off; then screen locks when you wake it up, it asks for the password. I've done BOTH these: - System Settings > Brightness and Lock > * Turn off screen when inactive for: Never * Lock: off * Lock screen after: screen turns off (this should be irrelevant given "Lock: off"; actually, this should be greyed out. Fail.) * I've deselected the checkbox "ask for password when waking from suspend" (btw, why is this here?? These settings are supposed to be about screen locking, not suspend, so either this option description is misleading or this is in the wrong place and should be in Settings > Power wher the option whether to suspend is. What a chaos!) - System Settings > Power (btw, it's stupid that this and the above are separate. I think this got fixed too in more recent versions. Why the hell don't these fix get backported to the current LTS version? Anyway) * Suspend when inactive for: Never Yet, screen STILL TURNS OFF after some time of inactivity. The only thing that has changed is that it doesn't ask me for the password now (I guess it doesn't lock screen any more). But it still turns off screen. There are a number of answers on AskUbuntu suggesting to install configuration tools that will allow you to disable the turning off of screen, but it's simply RIDICULOUS that (a) there are two separate settings for the same thing and (b) you need to install extra packages just tu disable such a basic trivial system setting. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: unity 5.20.0-0ubuntu2 ProcVersionSignature: Ubuntu 3.8.0-32.47~precise1-generic 3.8.13.10 Uname: Linux 3.8.0-32-generic i686 ApportVersion: 2.0.1-0ubuntu17.5 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' Date: Thu Oct 24 20:20:03 2013 InstallationMedia: Ubuntu 12.04.3 LTS "Precise Pangolin" - Release i386 (20130820.1) MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) 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/ubuntu/+source/unity/+bug/1244366/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1244366] Re: no easy way to disable screensaver on 12.04 without installing additional tools
I think I've figured out there's a "gnome screensaver daemon" running, which acts as a screensaver that blanks the screen (without really turning it off). The issue is there is no way to access its settings in System Settings to disable it. If I write "screensaver" in dash I can run an application called "Screensaver", which seems to have the settings to disable the screensaver. However, when I run it, it gives me (twice!!) a warning that says that there is already a gnome screenserver daemon running and that it must be stopped before. All this is ridiculous. If there is a screensaver, its settings should be easily accessible from System Settings. -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1244366 Title: no easy way to disable screensaver on 12.04 without installing additional tools Status in “unity” package in Ubuntu: New Bug description: I think this got fixed in some later version, but 12.04 is supposed to be LTS, right? So unless I misunderstand the meaning of the S in the acronym, the fix needs to be made available to 12.04 via updates. Here's the issue: have a fresh install of 12.04. After a given time of inactivity, the screen turns off; then screen locks when you wake it up, it asks for the password. I've done BOTH these: - System Settings > Brightness and Lock > * Turn off screen when inactive for: Never * Lock: off * Lock screen after: screen turns off (this should be irrelevant given "Lock: off"; actually, this should be greyed out. Fail.) * I've deselected the checkbox "ask for password when waking from suspend" (btw, why is this here?? These settings are supposed to be about screen locking, not suspend, so either this option description is misleading or this is in the wrong place and should be in Settings > Power wher the option whether to suspend is. What a chaos!) - System Settings > Power (btw, it's stupid that this and the above are separate. I think this got fixed too in more recent versions. Why the hell don't these fix get backported to the current LTS version? Anyway) * Suspend when inactive for: Never Yet, screen STILL TURNS OFF after some time of inactivity. The only thing that has changed is that it doesn't ask me for the password now (I guess it doesn't lock screen any more). But it still turns off screen. There are a number of answers on AskUbuntu suggesting to install configuration tools that will allow you to disable the turning off of screen, but it's simply RIDICULOUS that (a) there are two separate settings for the same thing and (b) you need to install extra packages just tu disable such a basic trivial system setting. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: unity 5.20.0-0ubuntu2 ProcVersionSignature: Ubuntu 3.8.0-32.47~precise1-generic 3.8.13.10 Uname: Linux 3.8.0-32-generic i686 ApportVersion: 2.0.1-0ubuntu17.5 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' Date: Thu Oct 24 20:20:03 2013 InstallationMedia: Ubuntu 12.04.3 LTS "Precise Pangolin" - Release i386 (20130820.1) MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) 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/ubuntu/+source/unity/+bug/1244366/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1244366] [NEW] no easy way to disable screensaver on 12.04 without installing additional tools
Public bug reported: I think this got fixed in some later version, but 12.04 is supposed to be LTS, right? So unless I misunderstand the meaning of the S in the acronym, the fix needs to be made available to 12.04 via updates. Here's the issue: have a fresh install of 12.04. After a given time of inactivity, the screen turns off; then screen locks when you wake it up, it asks for the password. I've done BOTH these: - System Settings > Brightness and Lock > * Turn off screen when inactive for: Never * Lock: off * Lock screen after: screen turns off (this should be irrelevant given "Lock: off"; actually, this should be greyed out. Fail.) * I've deselected the checkbox "ask for password when waking from suspend" (btw, why is this here?? These settings are supposed to be about screen locking, not suspend, so either this option description is misleading or this is in the wrong place and should be in Settings > Power wher the option whether to suspend is. What a chaos!) - System Settings > Power (btw, it's stupid that this and the above are separate. I think this got fixed too in more recent versions. Why the hell don't these fix get backported to the current LTS version? Anyway) * Suspend when inactive for: Never Yet, screen STILL TURNS OFF after some time of inactivity. The only thing that has changed is that it doesn't ask me for the password now (I guess it doesn't lock screen any more). But it still turns off screen. There are a number of answers on AskUbuntu suggesting to install configuration tools that will allow you to disable the turning off of screen, but it's simply RIDICULOUS that (a) there are two separate settings for the same thing and (b) you need to install extra packages just tu disable such a basic trivial system setting. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: unity 5.20.0-0ubuntu2 ProcVersionSignature: Ubuntu 3.8.0-32.47~precise1-generic 3.8.13.10 Uname: Linux 3.8.0-32-generic i686 ApportVersion: 2.0.1-0ubuntu17.5 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' Date: Thu Oct 24 20:20:03 2013 InstallationMedia: Ubuntu 12.04.3 LTS "Precise Pangolin" - Release i386 (20130820.1) MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: unity (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 precise running-unity -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1244366 Title: no easy way to disable screensaver on 12.04 without installing additional tools Status in “unity” package in Ubuntu: New Bug description: I think this got fixed in some later version, but 12.04 is supposed to be LTS, right? So unless I misunderstand the meaning of the S in the acronym, the fix needs to be made available to 12.04 via updates. Here's the issue: have a fresh install of 12.04. After a given time of inactivity, the screen turns off; then screen locks when you wake it up, it asks for the password. I've done BOTH these: - System Settings > Brightness and Lock > * Turn off screen when inactive for: Never * Lock: off * Lock screen after: screen turns off (this should be irrelevant given "Lock: off"; actually, this should be greyed out. Fail.) * I've deselected the checkbox "ask for password when waking from suspend" (btw, why is this here?? These settings are supposed to be about screen locking, not suspend, so either this option description is misleading or this is in the wrong place and should be in Settings > Power wher the option whether to suspend is. What a chaos!) - System Settings > Power (btw, it's stupid that this and the above are separate. I think this got fixed too in more recent versions. Why the hell don't these fix get backported to the current LTS version? Anyway) * Suspend when inactive for: Never Yet, screen STILL TURNS OFF after some time of inactivity. The only thing that has changed is that it doesn't ask me for the password now (I guess it doesn't lock screen any more). But it still turns off screen. There are a number of answers on AskUbuntu suggesting to install configuration tools that will allow you to disable the turning off of screen, but it's simply RIDICULOUS that (a) there are two separate settings for the same thing and (b) you need to install extra packages just tu disable such a basic trivial system setting. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: unity 5.20.0-0ubuntu2 ProcVersionSignature: Ubuntu 3.8.0-32.47~precise1-generic 3.8.13.10 Uname: Linux 3.8.0-32-generic i686 ApportVersion: 2.0.1-0ubuntu17.5 Architecture: i386 CompizPlugins: No value set for `/apps
[Dx-packages] [Bug 1243369] [NEW] Mouse cursor movement became jerky, then system stopped responding
Public bug reported: Just after the failure described in https://bugs.launchpad.net/ubuntu/+source/usb-creator/+bug/1243365 and after removing the usb pendrive, mouse cursor movements became jerky, meaning that from time to time the mouse cursor would freeze even though I was moving the mouse. Then, the system stopped responding to clicks and I couldn't do anything useful. Apparently there wasn't high CPU or disk activity. Only thing I could do was a hard power off. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: unity 7.0.0daily13.06.19~13.04-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-31.46-generic 3.8.13.8 Uname: Linux 3.8.0-31-generic x86_64 ApportVersion: 2.9.2-0ubuntu8.3 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' Date: Tue Oct 22 21:22:15 2013 InstallationDate: Installed on 2013-10-11 (11 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MarkForUpload: True SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: unity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug raring -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1243369 Title: Mouse cursor movement became jerky, then system stopped responding Status in “unity” package in Ubuntu: New Bug description: Just after the failure described in https://bugs.launchpad.net/ubuntu/+source/usb-creator/+bug/1243365 and after removing the usb pendrive, mouse cursor movements became jerky, meaning that from time to time the mouse cursor would freeze even though I was moving the mouse. Then, the system stopped responding to clicks and I couldn't do anything useful. Apparently there wasn't high CPU or disk activity. Only thing I could do was a hard power off. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: unity 7.0.0daily13.06.19~13.04-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-31.46-generic 3.8.13.8 Uname: Linux 3.8.0-31-generic x86_64 ApportVersion: 2.9.2-0ubuntu8.3 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' Date: Tue Oct 22 21:22:15 2013 InstallationDate: Installed on 2013-10-11 (11 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MarkForUpload: True SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1243369/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1239486] [NEW] screen turns off even when watching fullscreen media
Public bug reported: Since I installed a clean 13.04 ubuntu on a new computer, I've got the screen set up to automatically turn off after 10 minutes of inactivity, which is the default setting. However, that shouldn't apply when some application is showing media content in the foreground (e.g. whatching a youtube video), especially when in fullscreen (though actually fullscreen or not shouldn't even matter, provided the application playing media content is on the foreground). I'm not sure whether this is a regression or has always been sure (i used to have the screen set up to never turn off anyway), but all other operating systems have this right (Windows, Mac OS, Android), at least for the fullscreen case. Applications playing visual media must inhibit the turning off of the screen (basically playing media should not be considered "inactivity"). Basing the detection of inactivity merely on mouse and keyboard input is ridiculously obsolete. I don't know whether this is the OS's fault in not allowing applications to inhibit the "idle" state, or if it's the application that is failing to do so. If the latter, then one that doesn't is certainly Google Chrome when playing video. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: unity 7.0.0daily13.06.19~13.04-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-31.46-generic 3.8.13.8 Uname: Linux 3.8.0-31-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.9.2-0ubuntu8.3 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Mon Oct 14 03:47:53 2013 DistUpgraded: Fresh install DistroCodename: raring DistroVariant: ubuntu GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Device [1025:0647] NVIDIA Corporation GF117M [GeForce 610M/710M / GT 620M/625M/630M/720M] [10de:1140] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] GeForce 710M [1025:0691] InstallationDate: Installed on 2013-10-11 (2 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MachineType: Acer Aspire V3-571G MarkForUpload: True ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-31-generic root=UUID=5830b30e-69e8-4bb4-8a2b-bc2b43c7414a ro quiet splash vt.handoff=7 SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/15/2012 dmi.bios.vendor: Acer dmi.bios.version: V2.07 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: VA50_HC_CR dmi.board.vendor: Acer dmi.board.version: Type2 - Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V2.07 dmi.modalias: dmi:bvnAcer:bvrV2.07:bd10/15/2012:svnAcer:pnAspireV3-571G:pvrV2.07:rvnAcer:rnVA50_HC_CR:rvrType2-BoardVersion:cvnAcer:ct10:cvrV2.07: dmi.product.name: Aspire V3-571G dmi.product.version: V2.07 dmi.sys.vendor: Acer version.compiz: compiz 1:0.9.9~daily13.06.19~13.04-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.43-0ubuntu1.1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.1.4-0ubuntu0.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.1.4-0ubuntu0.1 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.1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.7-0ubuntu1 xserver.bootTime: Mon Oct 14 01:15:32 2013 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.13.3-0ubuntu6 xserver.video_driver: intel ** Affects: unity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 raring ubuntu -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1239486 Title: screen turns off even when watching fullscreen media Status in “unity” package in Ubuntu: New Bug description: Since I installed a clean 13.04 ubuntu on a new computer, I've got the screen set up to automatically turn off after 10 minutes of inactivity, which is the default setting. However, that shouldn't apply when some application is showing media content in the foreground (e.g. whatching a youtube video), especially when in fullscreen (though actually fullscreen or not shouldn't even matter, provided the application playing media content is on the foreground). I'm not sure whether this is a regression or has always been sure (i used to have the screen set up to n
[Dx-packages] [Bug 1239434] Re: whole system completely unusable after a reboot
*** This bug is a duplicate of bug 1239472 *** https://bugs.launchpad.net/bugs/1239472 By the way, see https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1239475 which prevents me from running apport-collect -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1239434 Title: whole system completely unusable after a reboot Status in “unity” package in Ubuntu: Incomplete Bug description: After a reboot, my almost newly installed Ubuntu 13.04 has become completely unusable, in that after booting and logging in, there is no launcher, and no system bar on the top of the screen. There's no way I can run any program. Since I have a .odt file on the desktop (it's the only thing I had on my desktop), I have tried double clicking it, and it correctly opens in OpenOffice Writer, but the windows have no borders or titlebar. Something got badly broken without an apparent reason. The last things I had done before the first boot that showed the issue was to install virtualbox and run it once (just to create a vm that I didn't run yet), and install the nvidia-current package via sudo apt- get install nvidia-current. Then I rebooted and the issue appeared. Since then, I have run sudo apt-get remove virtualbox-x.xx (don't remember the version) and sudo apt-get remove nvidia-current, but neither has fixed the issue. I'm writing the report from another computer. Then we get surprised that most people still use Windows. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1239434/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1239434] Re: whole system completely unusable after a reboot
*** This bug is a duplicate of bug 1239472 *** https://bugs.launchpad.net/bugs/1239472 This was caused by installing nvidia-current, and wasn't fixed by uninstalling it. Better report: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-304/+bug/1239472 ** Summary changed: - whose system completely unusable after a reboot + whole system completely unusable after a reboot ** This bug has been marked a duplicate of bug 1239472 nvidia driver breaks ubuntu irreversibly (uninstalling the package doesn't fix it) -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1239434 Title: whole system completely unusable after a reboot Status in “unity” package in Ubuntu: Incomplete Bug description: After a reboot, my almost newly installed Ubuntu 13.04 has become completely unusable, in that after booting and logging in, there is no launcher, and no system bar on the top of the screen. There's no way I can run any program. Since I have a .odt file on the desktop (it's the only thing I had on my desktop), I have tried double clicking it, and it correctly opens in OpenOffice Writer, but the windows have no borders or titlebar. Something got badly broken without an apparent reason. The last things I had done before the first boot that showed the issue was to install virtualbox and run it once (just to create a vm that I didn't run yet), and install the nvidia-current package via sudo apt- get install nvidia-current. Then I rebooted and the issue appeared. Since then, I have run sudo apt-get remove virtualbox-x.xx (don't remember the version) and sudo apt-get remove nvidia-current, but neither has fixed the issue. I'm writing the report from another computer. Then we get surprised that most people still use Windows. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1239434/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1212987] Re: Unity not starting after boot
I have the same issue (Unity disappeared after a reboot without a reason) but I can't work around it in any way. None of the workarounds mentioned in this report work for me. I still have no Unity launcher nor system bar, and hence my system is completely unusable. For god's sake how can this be getting so little attention? This is HUGE. ** Changed in: unity (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1212987 Title: Unity not starting after boot Status in “unity” package in Ubuntu: Confirmed Bug description: After boot today. Unity was missing. Empty desktop. In ccsm is seems the unity plugin was disabled somehow, I re-enabled it. Unity came back but coudn't set launcher icon size in settings -> appearance -> look. I tried: (http://askubuntu.com/questions/17381/unity-doesnt-load-no-launcher-no-dash-appears/) dconf reset -f /org/compiz/ unity --reset-icons &disown Unity did reset Still can set icon size in settings -> appearance -> look. Have to use Unity Tweak Tool for that to set icon size on 32. Then started Chromium and Unity crashed again. Restart and still can't set icon size or launcher to autohide. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: unity 7.0.0daily13.06.19~13.04-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-27.40-generic 3.8.13.4 Uname: Linux 3.8.0-27-generic x86_64 ApportVersion: 2.9.2-0ubuntu8.3 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' Date: Fri Aug 16 10:24:51 2013 InstallationDate: Installed on 2013-04-26 (111 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MarkForUpload: True SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1212987/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1239434] [NEW] whose system completely unusable after a reboot
Public bug reported: After a reboot, my almost newly installed Ubuntu 13.04 has become completely unusable, in that after booting and logging in, there is no launcher, and no system bar on the top of the screen. There's no way I can run any program. Since I have a .odt file on the desktop (it's the only thing I had on my desktop), I have tried double clicking it, and it correctly opens in OpenOffice Writer, but the windows have no borders or titlebar. Something got badly broken without an apparent reason. The last things I had done before the first boot that showed the issue was to install virtualbox and run it once (just to create a vm that I didn't run yet), and install the nvidia-current package via sudo apt-get install nvidia-current. Then I rebooted and the issue appeared. Since then, I have run sudo apt-get remove virtualbox-x.xx (don't remember the version) and sudo apt-get remove nvidia-current, but neither has fixed the issue. I'm writing the report from another computer. Then we get surprised that most people still use Windows. ** Affects: unity (Ubuntu) Importance: Undecided Status: New ** Description changed: After a reboot, my almost newly installed Ubuntu 13.04 has become completely unusable, in that after booting and logging in, there is no launcher, and no system bar on the top of the screen. There's no way I can run any program. Since I have a .odt file on the desktop (it's the only thing I had on my desktop), I have tried double clicking it, and it correctly opens in OpenOffice Writer, but the windows have no borders or titlebar. Something got badly broken without an apparent reason. The last things I had done before the first boot that showed the issue was to install virtualbox and run it once (just to create a vm that I didn't run yet), and install the nvidia-current package via sudo apt-get install nvidia-current. Then I rebooted and the issue appeared. Since then, I have run sudo apt-get remove virtualbox-x.xx (don't remember the version) and sudo apt-get remove nvidia-current, but neither has fixed the issue. I'm writing the report from another computer. - Then we get surprised that most people still uses Windows. + Then we get surprised that most people still use Windows. -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1239434 Title: whose system completely unusable after a reboot Status in “unity” package in Ubuntu: New Bug description: After a reboot, my almost newly installed Ubuntu 13.04 has become completely unusable, in that after booting and logging in, there is no launcher, and no system bar on the top of the screen. There's no way I can run any program. Since I have a .odt file on the desktop (it's the only thing I had on my desktop), I have tried double clicking it, and it correctly opens in OpenOffice Writer, but the windows have no borders or titlebar. Something got badly broken without an apparent reason. The last things I had done before the first boot that showed the issue was to install virtualbox and run it once (just to create a vm that I didn't run yet), and install the nvidia-current package via sudo apt- get install nvidia-current. Then I rebooted and the issue appeared. Since then, I have run sudo apt-get remove virtualbox-x.xx (don't remember the version) and sudo apt-get remove nvidia-current, but neither has fixed the issue. I'm writing the report from another computer. Then we get surprised that most people still use Windows. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1239434/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1236467] [NEW] A single misbehaving application using too much memory can hang the whole system into unrecoverable unresponsiveness, forcing you to turn power off
Public bug reported: It is too easy to put the whole system into an unusable state. Just try the following: - figure aout a webpage which is a little heavy to render in Google Chrome (just a page with a few hundred images will do) - open that same page in several tabs in Google Chrome, e.g. by ctrl+clicking the same link a few times. (I guess any other browser will do) Even though there is an issue in Chrome not detecting and preventing such a sudden explosion of memory usage (warning the user and letting him cancel or continue), the window manager MUST always maintain the responsiveness to mouse and keyboard. No matter how disastrous a sudden increase in cpu or memory consumption an application may have, it must never compromise the whole system stability. You should always be able to: - click on the offending application's window's close icon, so as to close the application (and if it doesn't respond, be prompted whether to kill it) - open a terminal to kill the offending process Not only I couldn't do any of those as the system would not respond to keyboard nor mouse (while it was probably swapping huge amounts of memory, which I infer from high disk activity and relatively low cpu activity) but I couldn't even hit ctrl+alt+f1 to open a virtual terminal and kill some process, because most keystrokes wouldn't be caught. It can't be accepted that a single misbehaving application can put the whole system in such a state that the only thing you can do is a hardware power off. I don't know whether this is an issue in the kernel, X.org, the window manager, or all of them. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: unity 7.0.0daily13.06.19~13.04-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-31.46-generic 3.8.13.8 Uname: Linux 3.8.0-31-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.9.2-0ubuntu8.4 Architecture: i386 CompizPlugins: [core,composite,opengl,decor,vpswitch,mousepoll,compiztoolbox,snap,commands,place,resize,session,regex,grid,wall,move,gnomecompat,imgpng,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] Date: Mon Oct 7 18:41:10 2013 InstallationDate: Installed on 2010-06-23 (1202 days ago) InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429) MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: unity UpgradeStatus: Upgraded to raring on 2013-08-10 (58 days ago) ** Affects: unity (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 raring third-party-packages -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1236467 Title: A single misbehaving application using too much memory can hang the whole system into unrecoverable unresponsiveness, forcing you to turn power off Status in “unity” package in Ubuntu: New Bug description: It is too easy to put the whole system into an unusable state. Just try the following: - figure aout a webpage which is a little heavy to render in Google Chrome (just a page with a few hundred images will do) - open that same page in several tabs in Google Chrome, e.g. by ctrl+clicking the same link a few times. (I guess any other browser will do) Even though there is an issue in Chrome not detecting and preventing such a sudden explosion of memory usage (warning the user and letting him cancel or continue), the window manager MUST always maintain the responsiveness to mouse and keyboard. No matter how disastrous a sudden increase in cpu or memory consumption an application may have, it must never compromise the whole system stability. You should always be able to: - click on the offending application's window's close icon, so as to close the application (and if it doesn't respond, be prompted whether to kill it) - open a terminal to kill the offending process Not only I couldn't do any of those as the system would not respond to keyboard nor mouse (while it was probably swapping huge amounts of memory, which I infer from high disk activity and relatively low cpu activity) but I couldn't even hit ctrl+alt+f1 to open a virtual terminal and kill some process, because most keystrokes wouldn't be caught. It can't be accepted that a single misbehaving application can put the whole system in such a state that the only thing you can do is a hardware power off. I don't know whether this is an issue in the kernel, X.org, the window manager, or all of them. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: unity 7.0.0daily13.06.19~13.04-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-31.46-generic 3.8.13.8 Uname: Linux 3.8.0-31-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.9.2-0ubuntu8.4 Architecture: i386 CompizPlugins: [core,composite,opengl,decor,vpswitch,mous
[Dx-packages] [Bug 1225774] [NEW] Launcher randomly stops showing up when you move the mouse to the left of the screen. Randomly clicking on some window's title bar almost always fixes it
Public bug reported: At random times, and very, very often (I haven't found out what triggers it), the Launcher stops showing up. That is, you move the mouse all the way to the left of the screen and the Launcher doesn't show up. You retry and retry but it won't show up. Clicking randomly on some window's titlebar and retrying usually fixes it. Most of the times, clicking on some other part of a window other than the title bar won't do the trick. I'm not sure this is always the case, but I'm under the impression it's necessary to click on a window's titlebar, or at least that is far far more likely to do the trick. This looks to me unrelated to #1225769, but I'm not sure; there may be some nontrivial relation. What I can say is that the steps described in 1225769 don't systematically reproduce this one, which is more random, but I can't tell for example whether or not having used Show Desktop is a necessary condition to observe this issue. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: unity 7.0.0daily13.06.19~13.04-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-30.44-generic 3.8.13.6 Uname: Linux 3.8.0-30-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.9.2-0ubuntu8.4 Architecture: i386 CompizPlugins: [core,composite,opengl,decor,vpswitch,mousepoll,compiztoolbox,snap,commands,place,resize,session,regex,grid,wall,move,gnomecompat,imgpng,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] Date: Sun Sep 15 22:25:37 2013 InstallationDate: Installed on 2010-06-23 (1180 days ago) InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429) MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: unity UpgradeStatus: Upgraded to raring on 2013-08-10 (36 days ago) ** Affects: unity (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 raring third-party-packages ** Description changed: At random times, and very, very often (I haven't found out what triggers it), the Launcher stops showing up. That is, you move the mouse all the way to the left of the screen and the Launcher doesn't show up. You retry and retry but it won't show up. Clicking randomly on some window's titlebar and retrying usually fixes it. Most of the times, clicking on some other part of a window other than the title bar won't do the trick. I'm not sure this is always the case, but I'm under the impression it's necessary to click on a window's titlebar, or at least that is far far more likely to do the trick. This looks to me unrelated to #1225769, but I'm not sure; there may be some nontrivial relation. What I can say is that the steps described in 1225769 don't systematically reproduce this one, which is more random, but I can't tell for example whether or not having used Show Desktop is a necessary condition to observe this issue. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: unity 7.0.0daily13.06.19~13.04-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-30.44-generic 3.8.13.6 Uname: Linux 3.8.0-30-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.9.2-0ubuntu8.4 Architecture: i386 CompizPlugins: [core,composite,opengl,decor,vpswitch,mousepoll,compiztoolbox,snap,commands,place,resize,session,regex,grid,wall,move,gnomecompat,imgpng,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] Date: Sun Sep 15 22:25:37 2013 InstallationDate: Installed on 2010-06-23 (1180 days ago) InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429) MarkForUpload: True ProcEnviron: - TERM=xterm - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=en_US.UTF-8 - SHELL=/bin/bash + TERM=xterm + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/bin/bash SourcePackage: unity UpgradeStatus: Upgraded to raring on 2013-08-10 (36 days ago) -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1225774 Title: Launcher randomly stops showing up when you move the mouse to the left of the screen. Randomly clicking on some window's title bar almost always fixes it Status in “unity” package in Ubuntu: New Bug description: At random times, and very, very often (I haven't found out what triggers it), the Launcher stops showing up. That is, you move the mouse all the way to the left of the screen and the Launcher doesn't show up. You retry and retry but it won't show up. Clicking randomly on some window's titlebar and retrying usually fixes it. Most of the times, clicking on some other part of a window other than the title bar won't do the trick. I'm not sure this is always the case, but I'm under the impression it's necessary to click on a window's titlebar, or at least that is far far more likely to do the tr
[Dx-packages] [Bug 1225769] [NEW] Using Show Desktop (Ctrl+Super+D) twice irreversibly makes Launcher and window switcher (Alt+Tab) completely unusable if one window is maximized
Public bug reported: Steps to reproduce (don't know if will 100% systematically reproduce or not): - show desktop with Ctrl+Super+D - go back to normal with Ctrl+Super+D again - Maximize a window - Move the cursor to the left of the screen => 1st glitch: launcher should show up. It doesn't. Hence launcher is unusable as long as you have a maximize window now. - Now unmaximize the maximized window(s), so you don't have any. - try Alt+Tab => 2nd glictch: the application switcher (the horizontal bar in the center of the screen with a square for every open application) is BEHIND ALL WINDOWS!!! Oh my god! Unusable too (whether or not you have maximized windows - Now hit Ctrl+Super+D again. So now the system is in the "show desktop" kind of state (this two-state thing is a nonsense design in the very first place btw, but that's another bug) - Restore some of the minimized windows, or even all of them, so you still are in the nonsense "show desktop" state but you have a few windows open. - Make sure none is maximized - Try Alt+Tab, try the Launcher => Both work, so this is the only workaround to both glitches: you have to always make sure the total number of times you have hit Ctrl+Super+D is odd, and then unminimize all the windows you need always manually. But this will still not solve a third glitch: - now maximize a window - try the Launcher (i.e. move the mouse all the way to the left) => 3rd glitch: the launcher shows up, but it is broken: as soon as you move the mouse cursor one pixel to the right it will hide again, so you'll never be able to click on any of its icons. The show-desktop think is completely screwed up and if you use it, the whole desktop becomes an unusable mess where most basic functionality (window switching and the launcher) become inaccessible (until you figure out the intricated way to access them when you discover exactly the pattern of behavior of this bug). ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: unity 7.0.0daily13.06.19~13.04-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-30.44-generic 3.8.13.6 Uname: Linux 3.8.0-30-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.9.2-0ubuntu8.4 Architecture: i386 CompizPlugins: [core,composite,opengl,decor,vpswitch,mousepoll,compiztoolbox,snap,commands,place,resize,session,regex,grid,wall,move,gnomecompat,imgpng,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] Date: Sun Sep 15 22:05:46 2013 InstallationDate: Installed on 2010-06-23 (1180 days ago) InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429) MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: unity UpgradeStatus: Upgraded to raring on 2013-08-10 (36 days ago) ** Affects: unity (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 raring third-party-packages -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1225769 Title: Using Show Desktop (Ctrl+Super+D) twice irreversibly makes Launcher and window switcher (Alt+Tab) completely unusable if one window is maximized Status in “unity” package in Ubuntu: New Bug description: Steps to reproduce (don't know if will 100% systematically reproduce or not): - show desktop with Ctrl+Super+D - go back to normal with Ctrl+Super+D again - Maximize a window - Move the cursor to the left of the screen => 1st glitch: launcher should show up. It doesn't. Hence launcher is unusable as long as you have a maximize window now. - Now unmaximize the maximized window(s), so you don't have any. - try Alt+Tab => 2nd glictch: the application switcher (the horizontal bar in the center of the screen with a square for every open application) is BEHIND ALL WINDOWS!!! Oh my god! Unusable too (whether or not you have maximized windows - Now hit Ctrl+Super+D again. So now the system is in the "show desktop" kind of state (this two-state thing is a nonsense design in the very first place btw, but that's another bug) - Restore some of the minimized windows, or even all of them, so you still are in the nonsense "show desktop" state but you have a few windows open. - Make sure none is maximized - Try Alt+Tab, try the Launcher => Both work, so this is the only workaround to both glitches: you have to always make sure the total number of times you have hit Ctrl+Super+D is odd, and then unminimize all the windows you need always manually. But this will still not solve a third glitch: - now maximize a window - try the Launcher (i.e. move the mouse all the way to the left) => 3rd glitch: the launcher shows up, but it is broken: as soon as you move the mouse cursor one pixel to the right it will hide again, so you'll never be able to click on any of its icons. The show
[Dx-packages] [Bug 1073494] Re: The "waiting" cursor won't go away
Not reproducible. It happened to me just that one time, as far as I remember. Again, if it is even just _possible_ that an application can happen to "leak" cursor state and affect the behavior of the cursor for the whole system, something is either buggy or badly designed at the system level (don't know whether it's Unity or Xorg or what, but not just the application that triggers it). -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1073494 Title: The "waiting" cursor won't go away Status in Unity: New Status in “unity” package in Ubuntu: Incomplete Bug description: The mouse cursor has remained trapped in the rotating-circle animated "waiting-for-something-to-complete" status. I have closed all programs that I had opened, I have opened and used some, closed them again and it's still there rotating as if there was some operation in progress. It's been more than half an hour. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: unity 5.16.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-33.52-generic 3.2.31 Uname: Linux 3.2.0-33-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.0.1-0ubuntu14 Architecture: i386 CompizPlugins: [core,composite,opengl,decor,vpswitch,mousepoll,compiztoolbox,snap,commands,place,resize,session,regex,grid,wall,move,gnomecompat,imgpng,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] Date: Wed Oct 31 10:37:18 2012 InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429) ProcEnviron: TERM=xterm PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: unity UpgradeStatus: Upgraded to precise on 2012-05-17 (166 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1073494/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 853784] Re: Opacity of notify-osd bubbles doesn't decrease correctly on hover in metacity
In my case, I think this bug disappeared when I changed from Unity2D to Unity3D. So either it has been fixed (which I doubt) or it only affects Unity2D. -- You received this bug notification because you are a member of DX Packages, which is subscribed to notify-osd in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/853784 Title: Opacity of notify-osd bubbles doesn't decrease correctly on hover in metacity Status in Unity 2D: Confirmed Status in “notify-osd” package in Ubuntu: Confirmed Bug description: Hovering the pointer over notify-osd bubbles whilst running the unity- 2d session (metacity + compositing) doesn't cause the opacity to decrease correctly anymore, although they do seem to blur on hover. I've attached a screencast of the issue, which shows the opacity beginning to decrease as the pointer approaches the bubble, but then it appears to reverse again and the opacity returns to normal by the time the pointer is positioned over the notification. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: notify-osd 0.9.32-0ubuntu2 ProcVersionSignature: Ubuntu 3.0.0-11.18-generic 3.0.4 Uname: Linux 3.0.0-11-generic x86_64 ApportVersion: 1.23-0ubuntu1 Architecture: amd64 Date: Mon Sep 19 12:06:37 2011 GtkTheme: Ambiance IconTheme: ubuntu-mono-dark InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Beta amd64 (20110901) MachineType: Dell Inc. Latitude E6410 PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.0.0-11-generic root=UUID=b2e419c9-361b-45c5-8964-3ee8ca387122 ro quiet splash vt.handoff=7 RelatedPackageVersions: xserver-xorg 1:7.6+7ubuntu7 libgl1-mesa-glx 7.11-0ubuntu3 libdrm2 2.4.26-1ubuntu1 xserver-xorg-video-intel 2:2.15.901-1ubuntu2 xserver-xorg-video-ati 1:6.14.99~git20110811.g93fc084-0ubuntu1 SourcePackage: notify-osd UpgradeStatus: No upgrade log present (probably fresh install) WindowManager: No value set for `/desktop/gnome/session/required_components/windowmanager' dmi.bios.date: 02/15/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A07 dmi.board.name: 04373Y dmi.board.vendor: Dell Inc. dmi.board.version: A03 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA07:bd02/15/2011:svnDellInc.:pnLatitudeE6410:pvr0001:rvnDellInc.:rn04373Y:rvrA03:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E6410 dmi.product.version: 0001 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/unity-2d/+bug/853784/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
