Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in
Dual-Head & Xinerama Question [SOLVED]
View unanswered posts
View posts from last 24 hours
View posts from last 7 days

 
Reply to topic    Gentoo Forums Forum Index Desktop Environments
View previous topic :: View next topic  
Author Message
Bob P
Advocate
Advocate


Joined: 20 Oct 2004
Posts: 3355
Location: Jackass! Development Labs

PostPosted: Wed Dec 08, 2004 6:32 pm    Post subject: Dual-Head & Xinerama Question [SOLVED] Reply with quote

I've been beating on my new Gentoo install to get dual monitor support working. (This involved alot of beating my head against the wall because the i810 chipset driver will not coexist peacefully with other video drivers, but that's another story.)

Now that I have the dual-head system up and running in X11 with KDE 3.3.x, there are some odd behaviors that I want to ask about.

1. I'm getting a taskbar at the bottom of both displays. Each taskbar has its own Start menu, and interestingly, the "Most Used Applications" section of the menu is different for each screen. Each screen maintains its own list of the most commonly used apps that have been deployed in that screen, instead of sharing a common list. Is this normal? If so, see #4 below.

2. I cannot drag an open window from one screen to the other. When I try to drag a window from one monitor to the other, instead of traversing the displays, the window wraps around on one display. Interestingly, the mouse moves back and forth with no problems. Is this normal?

3. When I am opening a program, I get the bouncing cursor replicated in the same position on both screens. Obviously, the ghost cursor is not normal.

4. Taskbar items can exist on one display, but not on the other. For example, the "Screen Resize and Rotate" icon will only exist on one of the taskbars. Even if I attempt to open the program on the other display via the start menu, it won't go to that display's taskbar. Is there any way to get the taskbar icons to appear on both screens?

thanks.
_________________
.
Stage 1/3 | Jackass! | Rockhopper! | Thanks | Google Sucks


Last edited by Bob P on Fri Dec 10, 2004 11:30 pm; edited 1 time in total
Back to top
View user's profile Send private message
Infamy
Tux's lil' helper
Tux's lil' helper


Joined: 26 Nov 2003
Posts: 92

PostPosted: Wed Dec 08, 2004 7:18 pm    Post subject: Reply with quote

1. yep, this is normal. I find that it is actually handy since I use each screen differently

2. Yes, this is normal, and sounds just like my setup. Sounds like your xinerama is not enabled/functioning.

3. This is a bug, at least in my mind. I believe there are bug reports (http://bugs.kde.org/show_bug.cgi?id=71779) that say it is resolved, but they may need to be resubmitted. Matter of fact, I believe I put one in myself a while back, I will check. This is not normal, and it is annoying.

4. It is quite possible to have different icons on each screen. For example, here are screens of my left screen:
http://pubpages.unh.edu/~gbabbin/Orangeblocks.png

and my right screen:
http://pubpages.unh.edu/~gbabbin/rightscreen.png

I do notice that when I start an app on the second screen, that there are entries on each task bar, but then the entry on the first screen disappears and the final result is desirable.
Back to top
View user's profile Send private message
Bob P
Advocate
Advocate


Joined: 20 Oct 2004
Posts: 3355
Location: Jackass! Development Labs

PostPosted: Wed Dec 08, 2004 9:30 pm    Post subject: Reply with quote

thanks for the reply! :wink:

1. having two separate taskbars is actually pretty useful at times. i have to admit, is very different from the dual-head setups i've used in the past (win), where you have one taskbar in the primary display and no taskbar on the other displays. the X implementation of a taskbar on each screen actually is a bit more convenient, in that you don't have to move so far with the mouse to get to the taskbar. i still think it would be more convenient, though, to have one universal startup menu on both screens. i wish that i knew of a way to make that happen.

2. xinerama. i'm not sure how xinerama is supposed to function. i understand that its supposed to keep a maximized window from sprawling out across two screens. in that respect, its working, as when i maximize its keeping the window limited to a single monitor.

i don't know how its supposed to function with regard to dragging a window from one screen to another. shouldn't you be able to move a window from one screen to the next (as you can in Windows dual head setups), or is this something that's NOT supposed to happen? i have to admit, there are some times when one display gets a bit crowded and it would be very handy to be able to move an app from one screen to the other while keeping it open.

when i try to move an app from the monitor on the right to the monitor on the left, i don't really like to see the app disappear from the left edge of the right monitor, only to reappear on the right edge of the right monitor, instead of moving to the right edge of the left monitor. i really wish that i knew of a way to change this behavior.

BTW, where does Xinerama come from? i coudn't find it in portage, and i don't know if its part of X11 or some other package.

4. i understand that its possible to have different icons on each screen. that can actually be pretty useful. but is it possible to have the same icons on both screens at the same time? i'd really like to be able to have a resolution adjusting icon in the system tray on both displays, as that is a function that i need to use frequently. as it is now, i can get it to appear on my left screen, but i can never make it appear on my right screen. i can't even execute the resolution changing program from the Start menu on the right screen -- after a couple seconds of the bouncing icon, the program seemingly collapses as the icon automatically disappears. when i want to resize the right screen's resolution, i have to jump through a bunch of hoops by going through the start menu and the Control Center, navigating through a bunch of menus and submenus. this is a real PITA.

Quote:
I do notice that when I start an app on the second screen, that there are entries on each task bar, but then the entry on the first screen disappears and the final result is desirable.

i had not noticed that before, but i do see it happening now.

5. i've noticed what appears to be another bug. when i right click on the taskbar on Screen 2 and select "Configure Panel", a new window opens with layout information. on the right side of the window is the Screen section, and under the drawing of a display it says "Xinerama screen: 2". When I press on the "Identify" button, a dialog box pops up with a "2" in it. so far so good.

when i do this on the taskbar on Screen 1, a similar window opens up, and the display information says "Xinerama screen: 1". but when i click on the "identify" button, the dialog box that pops up says "2".

in addition to being confused by what appears to be a bug in the "Identify" routine, I'm confused by the "All Screens" option. what does that do?

thanks!
_________________
.
Stage 1/3 | Jackass! | Rockhopper! | Thanks | Google Sucks
Back to top
View user's profile Send private message
Infamy
Tux's lil' helper
Tux's lil' helper


Joined: 26 Nov 2003
Posts: 92

PostPosted: Thu Dec 09, 2004 2:20 am    Post subject: Reply with quote

1. To save hassle trying to edit both menus, you can look in ~/.kde3.3/share/config. I have two config files there, one for each kicker. They are kickerrc, and kicker-screen-1rc. If you want the exact same thing on both screens, (though I have not done this myself) it would seem that you would be able to copy one over the other. If you just want the same K-menu, you can copy the appropriate section from the correct config file and put it in the other.

2.1xinerama allows you to copy a window from screen 0 to screen 1. It would be desirable if it prevented one window from stretching across the entire desktop, but there have been exceptions. Personally, the thought of it seem like a waste of resources to me. I have not ever been in dire need of moving a window from the left screen to the right :P.

2.2 Xinerama provides this function. I think over time you will get used to have certain things on certain screens, and on top of that, fully utilizing your virtual desktops.

2.3 To stop that desktop window wrapping, try this; KDE Control Center->Desktop->Window behaviour->"Focus" tab-> uncheck desktop navigation wraps around.

Also see the advanced tab about active window borders.

2.4 Xinerama is part of xorg-x11/XFree86. Check in the 'x' section in the following link for xinerama.

http://www.gentoo.org/dyn/use-index.xml

If it is something that you want, I suggest adding it to your make.conf.

3. .....Looks like we are skipping to 4 :P

4. Check your xorg.conf to be sure that you have a variety of resolutions set for the second screen. If you don't have them, you will see it switch to the same res. You can also use the keyboard shortcut - ctrl+alt+ + or ctrl+alt+ -

5. I have never used xinerama, so I am going to make take a stab in the dark about it. I don't think that you have xinerama enabled, so it could be possible that once it is enabled, the identify button will actually tell you useful information.

Maybe someone else will see this post and know :)
Back to top
View user's profile Send private message
Bob P
Advocate
Advocate


Joined: 20 Oct 2004
Posts: 3355
Location: Jackass! Development Labs

PostPosted: Thu Dec 09, 2004 12:50 pm    Post subject: Reply with quote

Infamy wrote:
1. To save hassle trying to edit both menus, you can look in ~/.kde3.3/share/config. I have two config files there, one for each kicker. They are kickerrc, and kicker-screen-1rc. If you want the exact same thing on both screens, (though I have not done this myself) it would seem that you would be able to copy one over the other. If you just want the same K-menu, you can copy the appropriate section from the correct config file and put it in the other.

well, i learned something new today. i had no idea that there was a ~/.kde3.3 directory there. is that a hidden directory? i couldn't find it when using the "ls" command in the ~ directory. without your tip, i never would have found it!

am i correct in assuming that "kickerrc" is for Screen 0 and "kicker-screen-1rc" is the equivalent file for Screen 1? (i have to admit that I know NOTHING about the inner workings of KDE.) If that's the case it seems that it would be easy enough to edit them. But the downside seems that if you ever made a configuration change to one screen, you'd have to repeat the process. I was hoping that there would be a way to tie the menus together dynamically. :idea:

Quote:
2.1xinerama allows you to copy a window from screen 0 to screen 1. It would be desirable if it prevented one window from stretching across the entire desktop, but there have been exceptions. Personally, the thought of it seem like a waste of resources to me. I have not ever been in dire need of moving a window from the left screen to the right :P.

in my case, the system does prevent a maximized display from sprawling across both screens. i just don't know if this is default X behavior, or if the default X behavior is to limit maximization to one screen. not knowing the default behavior of X and KDE, i have no frame of reference to determine whether xinerama is working the way its supposed to or not. i am assuming that it is present on my system, as the KDE screen setup menus do make reference to it.

when you say xinerama allows you to "copy" a window from Screen 0 to Screen 1, do you mean cut and paste, or dragging? FWIW, I can cut from one screen and paste to the other, though I'm not sure that this is what you're referring to.


Quote:
2.2 Xinerama provides this function. I think over time you will get used to have certain things on certain screens, and on top of that, fully utilizing your virtual desktops.

well, i have to admit, i have been under utilizing my virtual desktops. they are one area in which X/KDE is so much better than Windows, and being a long time duel-head Windows user, I haven't gotten into the groove of fully utilizing them. in fact, i had decreased the number of virtual desktops from the default value of 4 per screen to 2 per screen. i admit, i have to start using them more, as they are a powerful tool that i haven't been taking advantage of.

Quote:
2.3 To stop that desktop window wrapping, try this; KDE Control Center->Desktop->Window behaviour->"Focus" tab-> uncheck desktop navigation wraps around.

Also see the advanced tab about active window borders.

well, i've tried that. the results are a bit odd. when moving to the outside borders of the two displays "active window borders" will stop me from dragging them off of the screen. when moving to the adjacent borders of the screens, i still get wrap around when first traversing the screen, but on the second pass the active border stops the window from being dragged any farther. its as if KDE thinks that i have dragged the app window across both displays and is stopping it at the far side of the other display, even though it is actually wrapping. :?:


Quote:
4. Check your xorg.conf to be sure that you have a variety of resolutions set for the second screen. If you don't have them, you will see it switch to the same res. You can also use the keyboard shortcut - ctrl+alt+ + or ctrl+alt+ -

yes, xorg.conf has all of the display resolutions configured. the problem is that the "Screen Resize_Rotate" button only works on one of the displays. The workaround that you've suggested -- using the keyboard shortcuts -- works great. I feel stupid for not thinking of that! :oops: even though they keyboard shortcut works, i'd like to take advantage of the additional functionality of the "resize/rotate" button, such as the manipulation of color depths.

Quote:
5. I have never used xinerama, so I am going to make take a stab in the dark about it. I don't think that you have xinerama enabled, so it could be possible that once it is enabled, the identify button will actually tell you useful information.

well, even though you don't know, you obviously know more than i do about this, and i appreciate your help. maybe its not enabled, maybe its a bug. i just need to dig a little deeper and i appreciate your recommendations on where to start.

thanks again!
_________________
.
Stage 1/3 | Jackass! | Rockhopper! | Thanks | Google Sucks
Back to top
View user's profile Send private message
Bob P
Advocate
Advocate


Joined: 20 Oct 2004
Posts: 3355
Location: Jackass! Development Labs

PostPosted: Thu Dec 09, 2004 2:05 pm    Post subject: Reply with quote

Infamy wrote:
2.3 To stop that desktop window wrapping, try this; KDE Control Center->Desktop->Window behaviour->"Focus" tab-> uncheck desktop navigation wraps around.

Also see the advanced tab about active window borders.

maybe i've got something broken on my box. i've tried changing the setting on both tabs you've recommended, and i don't see any change in behavior, even after restarting X. i've even tried checking the box entitled "Traverse windows on all desktops." no dice - the window behavior is not chaning. something is definitely wrong here. :x
_________________
.
Stage 1/3 | Jackass! | Rockhopper! | Thanks | Google Sucks
Back to top
View user's profile Send private message
Infamy
Tux's lil' helper
Tux's lil' helper


Joined: 26 Nov 2003
Posts: 92

PostPosted: Thu Dec 09, 2004 3:27 pm    Post subject: Reply with quote

ls -a will show everything.

kickerrc is for the primary display. If you are confused, you can look inside and see that the various icons in your kicker match within the file. This is a shot in the dark, but you could probably move kicker-screen-1rc to another location, and in it's place, put a symlink to kickerrc.

Quote:
in my case, the system does prevent a maximized display from sprawling across both screens. i just don't know if this is default X behavior, or if the default X behavior is to limit maximization to one screen. not knowing the default behavior of X and KDE, i have no frame of reference to determine whether xinerama is working the way its supposed to or not. i am assuming that it is present on my system, as the KDE screen setup menus do make reference to it.

when you say xinerama allows you to "copy" a window from Screen 0 to Screen 1, do you mean cut and paste, or dragging? FWIW, I can cut from one screen and paste to the other, though I'm not sure that this is what you're referring to.


From what you have told me, I am under the assumption that you do not have xinerama active or installed, so no, the system is not preventing it from sprawling across two screens, it simple does not have the capability. you have two desktops, that is it. If xinerama were active, you would effectivly have one desktop.

By copy, I mean dragging.

As far as the active borders, I have not had time to play with them, I will do that soon and see what my results are, as well as a resize/rotate button.
Back to top
View user's profile Send private message
jschellhaass
Guru
Guru


Joined: 20 Jan 2004
Posts: 341

PostPosted: Thu Dec 09, 2004 3:53 pm    Post subject: Reply with quote

There are two different modes for dual head.

The traditional way treats each display as seperate. This allows for things like independent color depths, screen savers etc. on each display. It does not allow for dragging windows between displays. If you are using a dual head system like this and have compiled with the xinerama USE flag I would recommend changing USE flags to -xinerama and do an emerge --newuse world. This will recompile qt and some of the kde apps without xinerama support.

If you are using a dual head setup with xinerama and have not compiled with the xinerama USE flag I would recommend changing USE flags to +xinerama and doing an emerge --newuse world. Again this compiles apps to take advantage of xinerama support.

jeff
Back to top
View user's profile Send private message
Bob P
Advocate
Advocate


Joined: 20 Oct 2004
Posts: 3355
Location: Jackass! Development Labs

PostPosted: Thu Dec 09, 2004 4:15 pm    Post subject: Reply with quote

thanks, guys. my system is the "traditional way" as mentioned above.

just so that i'm sure that i'm on the right page -- i do not see that xinerama is in the portage tree. is xinerama something that i have to install/emerge separately, or is it something that i merely enable by recompiling with a new USE flag?
_________________
.
Stage 1/3 | Jackass! | Rockhopper! | Thanks | Google Sucks
Back to top
View user's profile Send private message
jschellhaass
Guru
Guru


Joined: 20 Jan 2004
Posts: 341

PostPosted: Thu Dec 09, 2004 4:34 pm    Post subject: Reply with quote

xinerama is a USE flag. Disabled by default.

jeff
Back to top
View user's profile Send private message
Bob P
Advocate
Advocate


Joined: 20 Oct 2004
Posts: 3355
Location: Jackass! Development Labs

PostPosted: Thu Dec 09, 2004 5:22 pm    Post subject: Reply with quote

thanks. i checked on that, and the "emerge --newuse world" is gonna completely recompile kde-base, thunderbird, and a couple of other fat apps. that's gonna take a while...

so tell me, do i have to take down the X server to do this, or can i get away with doing this in a root console window?
_________________
.
Stage 1/3 | Jackass! | Rockhopper! | Thanks | Google Sucks
Back to top
View user's profile Send private message
jschellhaass
Guru
Guru


Joined: 20 Jan 2004
Posts: 341

PostPosted: Thu Dec 09, 2004 5:49 pm    Post subject: Reply with quote

If you are using dual head with separate xsessions (the more traditional way as mentioned in my previous post) you DO NOT want to recompile with xinerama USE flag.

That said, you should be able to compile in a root console. Restart X when it's complete.

jeff
Back to top
View user's profile Send private message
Bob P
Advocate
Advocate


Joined: 20 Oct 2004
Posts: 3355
Location: Jackass! Development Labs

PostPosted: Thu Dec 09, 2004 6:36 pm    Post subject: Reply with quote

thanks. i'm currently using the traditional setup, but i want to try the non-traditional setup, so i've added "xinerama" to my USE flags and i'll go ahead and recompile. if i don't like it, i can always remove the USE flag and recomile again to go back.
_________________
.
Stage 1/3 | Jackass! | Rockhopper! | Thanks | Google Sucks
Back to top
View user's profile Send private message
Bob P
Advocate
Advocate


Joined: 20 Oct 2004
Posts: 3355
Location: Jackass! Development Labs

PostPosted: Fri Dec 10, 2004 3:26 pm    Post subject: Reply with quote

jschellhaass wrote:
If you are using a dual head setup with xinerama and have not compiled with the xinerama USE flag I would recommend changing USE flags to +xinerama and doing an emerge --newuse world. Again this compiles apps to take advantage of xinerama support.


Thanks for the help, Jeff. I tried recompiling to enable xinerama, and it didn't work. :cry: I have to have made a mistake somewhere.

I added "xinerama" to my USE flags in /etc/make.conf and performed an "emerge --newuse world". the effected packager were nano, k3b, KDE, and thunderbird. much to my surprise, upon restarting the X server my environment appears not to have changed in any way -- I still cannot drag apps across monitors and I'm still getting the numeric errors on the "identify" button -- every screen is always reported as xinerama screen "2". its as if nothing happened as a result of the recompile.

insofar as none of my screen behaviors have changed, i'm thinking that something in the re-compilation did not work properly.

just so that i have this right, is "xinerama" the correct USE flag, so that make.conf should contain a line the the following (excerpt):

Code:
USE="... xscreensaver xinerama xsl xvid xv"

or am i using the wrong flag. should "xinerama" be replaced with "+xinerama"?

just for the sake of completeness, here's the output of /var/log/emerge.log. everything appears to have emerged fine:
Code:
1102611818: Started emerge on: Dec 09, 2004 17:03:38
1102611818:  *** emerge --newuse nano
1102611818:  >>> emerge (1 of 1) app-editors/nano-1.3.5 to /
1102611818:  === (1 of 1) Cleaning (app-editors/nano-1.3.5::/usr/portage/app-editors/nano/nano-1.3.5.ebuild)
1102611820:  === (1 of 1) Compiling/Merging (app-editors/nano-1.3.5::/usr/portage/app-editors/nano/nano-1.3.5.ebuild)
1102611921:  === (1 of 1) Post-Build Cleaning (app-editors/nano-1.3.5::/usr/portage/app-editors/nano/nano-1.3.5.ebuild)
1102611924:  >>> AUTOCLEAN: app-editors/nano
1102611924:  --- AUTOCLEAN: Nothing unmerged.
1102611924:  ::: completed emerge (1 of 1) app-editors/nano-1.3.5 to /
1102611924:  *** Finished. Cleaning up...
1102611928:  *** exiting successfully.
1102611934:  *** terminating.
1102611995: Started emerge on: Dec 09, 2004 17:06:35
1102611995:  *** emerge --newuse k3b
1102611995:  >>> emerge (1 of 1) app-cdr/k3b-0.11.17 to /
1102611995:  === (1 of 1) Cleaning (app-cdr/k3b-0.11.17::/usr/portage/app-cdr/k3b/k3b-0.11.17.ebuild)
1102611997:  === (1 of 1) Compiling/Merging (app-cdr/k3b-0.11.17::/usr/portage/app-cdr/k3b/k3b-0.11.17.ebuild)
1102614918:  === (1 of 1) Post-Build Cleaning (app-cdr/k3b-0.11.17::/usr/portage/app-cdr/k3b/k3b-0.11.17.ebuild)
1102614920:  >>> AUTOCLEAN: app-cdr/k3b
1102614920:  --- AUTOCLEAN: Nothing unmerged.
1102614920:  ::: completed emerge (1 of 1) app-cdr/k3b-0.11.17 to /
1102614920:  *** Finished. Cleaning up...
1102614925:  *** exiting successfully.
1102614925:  *** terminating.
1102617451: Started emerge on: Dec 09, 2004 18:37:31
1102617451:  *** emerge --newuse world
1102617455:  >>> emerge (1 of 9) kde-base/kdemultimedia-3.3.1 to /
1102617455:  === (1 of 9) Cleaning (kde-base/kdemultimedia-3.3.1::/usr/portage/kde-base/kdemultimedia/kdemultimedia-3.3.1.ebuild)
1102617458:  === (1 of 9) Compiling/Merging (kde-base/kdemultimedia-3.3.1::/usr/portage/kde-base/kdemultimedia/kdemultimedia-3.3.1.ebuild)
1102624984:  === (1 of 9) Post-Build Cleaning (kde-base/kdemultimedia-3.3.1::/usr/portage/kde-base/kdemultimedia/kdemultimedia-3.3.1.ebuild)
1102624989:  >>> AUTOCLEAN: kde-base/kdemultimedia
1102624989:  --- AUTOCLEAN: Nothing unmerged.
1102624989:  ::: completed emerge (1 of 9) kde-base/kdemultimedia-3.3.1 to /
1102624989:  >>> emerge (2 of 9) kde-base/kdegraphics-3.3.1-r2 to /
1102624989:  === (2 of 9) Cleaning (kde-base/kdegraphics-3.3.1-r2::/usr/portage/kde-base/kdegraphics/kdegraphics-3.3.1-r2.ebuild)
1102624991:  === (2 of 9) Compiling/Merging (kde-base/kdegraphics-3.3.1-r2::/usr/portage/kde-base/kdegraphics/kdegraphics-3.3.1-r2.ebuild)
1102632172:  === (2 of 9) Post-Build Cleaning (kde-base/kdegraphics-3.3.1-r2::/usr/portage/kde-base/kdegraphics/kdegraphics-3.3.1-r2.ebuild)
1102632180:  >>> AUTOCLEAN: kde-base/kdegraphics
1102632180:  --- AUTOCLEAN: Nothing unmerged.
1102632180:  ::: completed emerge (2 of 9) kde-base/kdegraphics-3.3.1-r2 to /
1102632180:  >>> emerge (3 of 9) kde-base/kdenetwork-3.3.1-r1 to /
1102632180:  === (3 of 9) Cleaning (kde-base/kdenetwork-3.3.1-r1::/usr/portage/kde-base/kdenetwork/kdenetwork-3.3.1-r1.ebuild)
1102632182:  === (3 of 9) Compiling/Merging (kde-base/kdenetwork-3.3.1-r1::/usr/portage/kde-base/kdenetwork/kdenetwork-3.3.1-r1.ebuild)
1102639634:  === (3 of 9) Post-Build Cleaning (kde-base/kdenetwork-3.3.1-r1::/usr/portage/kde-base/kdenetwork/kdenetwork-3.3.1-r1.ebuild)
1102639639:  >>> AUTOCLEAN: kde-base/kdenetwork
1102639639:  --- AUTOCLEAN: Nothing unmerged.
1102639639:  ::: completed emerge (3 of 9) kde-base/kdenetwork-3.3.1-r1 to /
1102639639:  >>> emerge (4 of 9) mail-client/mozilla-thunderbird-1.0 to /
1102639639:  === (4 of 9) Cleaning (mail-client/mozilla-thunderbird-1.0::/usr/portage/mail-client/mozilla-thunderbird/mozilla-thunderbird-1.0.ebuild)
1102639642:  === (4 of 9) Compiling/Merging (mail-client/mozilla-thunderbird-1.0::/usr/portage/mail-client/mozilla-thunderbird/mozilla-thunderbird-1.0.ebuild)
1102647896:  === (4 of 9) Post-Build Cleaning (mail-client/mozilla-thunderbird-1.0::/usr/portage/mail-client/mozilla-thunderbird/mozilla-thunderbird-1.0.ebuild)
1102647916:  >>> AUTOCLEAN: mail-client/mozilla-thunderbird
1102647916:  --- AUTOCLEAN: Nothing unmerged.
1102647916:  ::: completed emerge (4 of 9) mail-client/mozilla-thunderbird-1.0 to /
1102647916:  >>> emerge (5 of 9) x11-misc/superkaramba-0.35 to /
1102647916:  === (5 of 9) Cleaning (x11-misc/superkaramba-0.35::/usr/portage/x11-misc/superkaramba/superkaramba-0.35.ebuild)
1102647919:  === (5 of 9) Compiling/Merging (x11-misc/superkaramba-0.35::/usr/portage/x11-misc/superkaramba/superkaramba-0.35.ebuild)
1102648710:  === (5 of 9) Post-Build Cleaning (x11-misc/superkaramba-0.35::/usr/portage/x11-misc/superkaramba/superkaramba-0.35.ebuild)
1102648712:  >>> AUTOCLEAN: x11-misc/superkaramba
1102648713:  --- AUTOCLEAN: Nothing unmerged.
1102648713:  ::: completed emerge (5 of 9) x11-misc/superkaramba-0.35 to /
1102648713:  >>> emerge (6 of 9) kde-base/kdeutils-3.3.1 to /
1102648713:  === (6 of 9) Cleaning (kde-base/kdeutils-3.3.1::/usr/portage/kde-base/kdeutils/kdeutils-3.3.1.ebuild)
1102648715:  === (6 of 9) Compiling/Merging (kde-base/kdeutils-3.3.1::/usr/portage/kde-base/kdeutils/kdeutils-3.3.1.ebuild)
1102652081:  === (6 of 9) Post-Build Cleaning (kde-base/kdeutils-3.3.1::/usr/portage/kde-base/kdeutils/kdeutils-3.3.1.ebuild)
1102652083:  >>> AUTOCLEAN: kde-base/kdeutils
1102652084:  --- AUTOCLEAN: Nothing unmerged.
1102652084:  ::: completed emerge (6 of 9) kde-base/kdeutils-3.3.1 to /
1102652084:  >>> emerge (7 of 9) kde-base/kdeartwork-3.3.1 to /
1102652084:  === (7 of 9) Cleaning (kde-base/kdeartwork-3.3.1::/usr/portage/kde-base/kdeartwork/kdeartwork-3.3.1.ebuild)
1102652086:  === (7 of 9) Compiling/Merging (kde-base/kdeartwork-3.3.1::/usr/portage/kde-base/kdeartwork/kdeartwork-3.3.1.ebuild)
1102653288:  === (7 of 9) Post-Build Cleaning (kde-base/kdeartwork-3.3.1::/usr/portage/kde-base/kdeartwork/kdeartwork-3.3.1.ebuild)
1102653293:  >>> AUTOCLEAN: kde-base/kdeartwork
1102653293:  --- AUTOCLEAN: Nothing unmerged.
1102653293:  ::: completed emerge (7 of 9) kde-base/kdeartwork-3.3.1 to /
1102653293:  >>> emerge (8 of 9) kde-base/kdebase-3.3.1 to /
1102653293:  === (8 of 9) Cleaning (kde-base/kdebase-3.3.1::/usr/portage/kde-base/kdebase/kdebase-3.3.1.ebuild)
1102653296:  === (8 of 9) Compiling/Merging (kde-base/kdebase-3.3.1::/usr/portage/kde-base/kdebase/kdebase-3.3.1.ebuild)
1102664814:  === (8 of 9) Post-Build Cleaning (kde-base/kdebase-3.3.1::/usr/portage/kde-base/kdebase/kdebase-3.3.1.ebuild)
1102664821:  >>> AUTOCLEAN: kde-base/kdebase
1102664822:  --- AUTOCLEAN: Nothing unmerged.
1102664822:  ::: completed emerge (8 of 9) kde-base/kdebase-3.3.1 to /
1102664822:  >>> emerge (9 of 9) kde-base/kdeadmin-3.3.1 to /
1102664822:  === (9 of 9) Cleaning (kde-base/kdeadmin-3.3.1::/usr/portage/kde-base/kdeadmin/kdeadmin-3.3.1.ebuild)
1102664824:  === (9 of 9) Compiling/Merging (kde-base/kdeadmin-3.3.1::/usr/portage/kde-base/kdeadmin/kdeadmin-3.3.1.ebuild)
1102666555:  === (9 of 9) Post-Build Cleaning (kde-base/kdeadmin-3.3.1::/usr/portage/kde-base/kdeadmin/kdeadmin-3.3.1.ebuild)
1102666557:  >>> AUTOCLEAN: kde-base/kdeadmin
1102666557:  --- AUTOCLEAN: Nothing unmerged.
1102666557:  ::: completed emerge (9 of 9) kde-base/kdeadmin-3.3.1 to /
1102666557:  *** Finished. Cleaning up...
1102666563:  *** exiting successfully.
1102666564:  *** terminating.

_________________
.
Stage 1/3 | Jackass! | Rockhopper! | Thanks | Google Sucks
Back to top
View user's profile Send private message
jub0r
n00b
n00b


Joined: 01 Feb 2003
Posts: 73
Location: Denver, Colorado

PostPosted: Fri Dec 10, 2004 7:00 pm    Post subject: Reply with quote

the option you're looking for is in your /etc/X11/xorg.conf (or XF86Config)

In your ServerFlags section, you need:
Code:
Option  "Xinerama"


Then, in your ServerLayout section you need:
Code:

Screen      0  "Screen0" 0 0
Screen      1  "Screen1" RightOf "Screen0"

Edit that to fit your situation. "Screen0/1" should match the Identifier entry in each of your "Screen" sections.

That should get your desktop to span monitors if you have xinerama compiled into xorg or xfree86
Back to top
View user's profile Send private message
Bob P
Advocate
Advocate


Joined: 20 Oct 2004
Posts: 3355
Location: Jackass! Development Labs

PostPosted: Fri Dec 10, 2004 11:30 pm    Post subject: Reply with quote

[SOLVED!]

if anyone's found this thread while searching for help, consider the following:

"emerge --newuse world -p" will list a number of programs that will be recompiled, but "emerge --newuse world" may miss some dependencies.

some have recommended "emerge --newuse world -vaD"

"equery h xinerama" revealed some additional programs that needed to be recompiled to be xinerama compliant. equery is part of the gentoolkit.

Thanks everyone!
_________________
.
Stage 1/3 | Jackass! | Rockhopper! | Thanks | Google Sucks
Back to top
View user's profile Send private message
Display posts from previous:   
Reply to topic    Gentoo Forums Forum Index Desktop Environments All times are GMT
Page 1 of 1

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum