beesea

i don't know if this'll make a difference, but i compile my kernels with: make dep && make clean bzImage modules modules_install maybe you need to run make clean first? i dunno, i'm just spitting out ideas here....

i just checked, and texstar's stuff is back up so apt should work now

in gconf-editor, goto /apps/metacity/global_keybindings. edit the values in run_command_1, run_command_2, etc to the shortcut keys you wanna use. then goto apps/metacity/keybinding_commands and fill in the execution comands for what you want command_1, command_2, etc. to be.

you should have the libgtk2-devel (or something similar) installed

i don't think this is a windows-related problem. when i upgraded to 9.1 (as opposed to a clean install) i started getting this error message only when i started using 9.1's kernel. if go back to using the old 2.4.19 kernel from 9.0 then i don't get that message anymore.

Sincerely, no. The forum.gentoo.org board is frequented by LOTS of gentoo users and when I have a question I go there and most of the time I don't have to ask, the question has already been asked and answered. Also, we are not much Gentoo users here on this board so I think the 'Other Linux Distributions' section is enough. Just my 2 cents.. MOttS i agree. i also use gentoo and forums.gentoo.org is THE place to get all your gentoo questions answered. just like motts said, most of the time you'll find that someone there's already had that problem and that there was a solution for it.

i have the same problem, but i only see it once. i know you get that error if there's no disk in the zip drive. its annoying, but it doesn't seem to be anything to worry about.

my ~/.rpmrc looks like: optflags: i586 -march=pentium3 -O3 -fomit-frame-pointer -pipe buildarchtranslate: i386: i586 buildarchtranslate: i486: i586 buildarchtranslate: i586: i586 buildarchtranslate: i686: i586 for an athlon (i think) it should look something like: optflags: athlon -march=athlon -O3 -fomit-frame-pointer -pipe buildarchtranslate: i386: athlon buildarchtranslate: i486: athlon buildarchtranslate: i586: athlon buildarchtranslate: i686: athlon

so what exactly is the problem? do rpms not rebuild at all, do they not build with your specified optflags, or something else? i haven't tried using optflags in my .rpmrc, but i have no problem building rpms. check the mandrake rpm howto to verify that your .rpmrc and .rpmmacros files are good

well, setting the modeline didn't work so i guess i'm stuck with it

i'd like to not have my screen ****ed up like that whenever i go away for awhile. although i've had dpms disabled since i've had this problem, ideally i'd like to have it turned on. by the way, thanks for that link. i'll check it out and see if that helps

first off, here's a screenshot of my problem. this only occurs when i move the mouse or press a key to turn my monitor back on after i've been away from my machine for a long time (ie. overnight, while i'm sleeping). this also means that my power saving settings have been in affect for a long time. this only happens with xfree 4.3 and fluxbox. i can reproduce this problem in gentoo (X 4.3 also), which runs on this same machine. anyone know how to fix this? could this be harmful to my monitor?

its a menu option, under file (i think)

you should definitely try the upgrade. i did it yesterday afternoon and so far everything seems ok

you could just press the print screen button for screenshots.

i haven't installed xfree 4.3 in mandrake yet, but i dual-boot with gentoo where i do have xfree 4.3. there's a way to make the cursor smaller, but i don't know how much of the quality you'll lose (i haven't checked out that cursor). you have to create a file called ~/.Xdefaults and put in it: Xcursor.size: 16 <-- the default is 24 i think Xcursor.theme: whiteglass <--theme name

that's because gtk2 isn't compatible with gtk1.2. you'll need the 1.2 devel package and i'm positive its on one of your cds. just keep looking and you'll find it

mdk 9 has both versions also, so you should be able to use both versions just fine. however, they're not compatible with one another. a program made specifically for gtk2 won't work with gtk1. a gtk1.2 theme won't work for a gtk2 program (some will work, but you'll have to work for it). bvc has a post in tips and trick on using gtk1 themes with gtk2 apps.

you need the gtk-devel (or libgtk-devel, i can't remember) packages in order to compile with gtk.

on my machine, action is just a symlink to one of the action.* files. i just changed the link to point to the one i wanted to use. i can't think of a good way to explain it so maybe i can help you see it. go into another window manager (that uses a click-to-focus model) and open up a browser window and some other window. move things around so that you can easily see both windows and make sure the browser is the window that's not focused. now if you click on a link in the unfocused browser window, the browser will become active and follow the link. in waimea, however, i'd have to click twice; once to focus the browser, and again to follow the link. this is what i mean by the program not receiving the click. does that make more sense? does anyone else even have that problem?

i wasn't aware that you could do it paul's way. i've been doing it like this: startx KDE startx Fluxbox but the argument i pass to startx is case sensitive and must match the spelling of the files in /etc/X11/wmsession.d (minus the two leading digits). also, the wm specified in ~/.xinitrc overrides the argument passed to startx so only do it one way or the other. wouldn't that mean that startx would get called everytime you started an xterm? i think that startx should get called from .bash_profile

i'm pretty sure the file to edit is /etc/X11/Xftconfig. as Ixthusdan said, you have to list the 100dpi first. i'm not sure if gdm has anything to do with it, but either way that's a really odd problem

yeah, i have those action files but the problem still remains. i used the action.click-to-focus and another click-to-focus action file i got from the waimea web page. the click to focus part works fine, but the click still doesn't get received by the program.

i prefer a click-to-focus system, so that doesn't apply to my problem. of course! :wink: that's where to go to find out how to edit your action files in the first place. however, the man page doesn't explain how to do specific things like that; it just says what does what but doesn't tell you how put it all together.

is there a way to set my action file so that an unfocused window receives a mouse click? is it even possible? for example, if i click over a link in an unfocused browser window, the window becomes focused but the browser doesn't recognize the click. in this case i would need two clicks, one to focus the window and one to follow the link. i'll have edited my action file exactly to my liking, pending this one little problem