Ubuntu 12.04 sports some significant improvements to multi-monitor support – both under and above the hood. But one aspect of how the final implementation will work is still being considered, as John ...
I voted. I'd prefer an auto-hide launcher on both so that whichever I'm currently on I have easy access. It's not a real big deal though since I most commonly use the keyboard to bring up the launcher.
The only way dual-monitor will work on my computer is if I chose not to install nvidia drivers as it seems to have some sort of incompatibility. Works perfect without it, however (as you can imagine) if I attempt to run anything that requires 3D acceleration it simply won't work.
I know it is unrelated to the topic but I would love to see that fixed. Even though I believe it is not much of an Ubuntu problem, but Nvidia's...
Since before beta one use multi monitor just freezes Ubuntu on my notebook with an Intel integrated videocard. The bug was reported, but I didn't get any answer or anything so, whatever for me, multimonitor just don't work anyways...
I use dual-monitor setup and would prefer auto-hiding launcher on the display where the cursor currently is. So focus = cursor hovering, dual auto hiding launchers, and epic responsibility. :] Voted too.
IDK... to me the launchers seems in the way, or sort of annoying when dual-viewing. Never tried Unity with dualview so I wouldnt know from personal experience though. But it was my first though popping up.
+Paulo Silva , certain upgrades that affect the kernel run an update-grub. That shouldn't be an issue unless the OS prober in grub can't find your crunchbang partition. Look at your partition configuration.
well +Jim Scholfield, the fact is Crunchbang (wheezy) upgrades finds both Ubuntu and Crunchbang, and Ubuntu (12.04 beta) only finds Ubuntu - this is really weird... - i'd ask everyone to check this as well and confirm...
I have to say this. Blocking wifi and disabiling network adapters has been a problem since 10.04 LTS. 11.10 now, and still Canonical hasn't learned. Be sure that 12.04 doesn't have this issue!! It's absolutely nonsense.
I think it should be on every screen. I use the "autohide" function, so it doesn't get in the way and the launcher should be quick and never far away from where you work. It would actually bother me if i had to turn my head to another monitor just to start or switch to another application using the launcher.
+Paulo Silva , I have ubuntu 11.10, fedora, openSuse, bodhi, debian and test partitions that are all found by the Ubuntu grub. I haven't tried crunchbang. What I described is correct as to how updates change grub. On those occasions when grub is changed, first grub-install and then update-grub are run. Ubuntu uses Grub 2 and you can research from that what it looks for that it isn't finding in your case. The os prober is the grub script that does the find. That script is in your grub.d folder.
There are user agent switchers for Chromium/Chrome as well from the Chrome web store. Whether using Chromium/Chrome or Firefox these have always allowed me to appear to be IE to someone's old site that is a mess.
I use Multimonitors setup everyday. I prefer the launcher to be present in both monitors (All monitors for more than Two monitors setups).
- When I click an application launcher, the app should appear on the focused monitor where the mouse cursor is.
- The launcher sensitivity will allow me not to reveal it accidentally when crossing the mouse from monitor to another.
Imagine you have Four large wide screens staffed horizontally and you move the mouse to the fourth one to manipulate one application, then you want to open Gedit in the same monitor. Isn't it pissing to go back one mile again to the primary monitor just to pick the launcher and drag Gedit to the fourth screen back again? :(
so a BIG YES for "LAUNCHER ON ALL MONITORS"
Yet, in 12.10, why not adding an enhancement to this feature : --> Allowing the user to Enable/DIsable revealing the Launcher in all monitors.
+Jim Scholfield Thanks for the confirmation. Indeed Firefox 10 works just fine. I am using Firefox 11 on Ubuntu 12.04. So I wanted to confirm if it was an issue of the beta version of Firefox or something wrong in my system.