FluxBox Problems

So guys I took the big step, after trying all the DE's (XFCE was my favourite), to go wm. I had big problems with OpenBox so I just trying FluxBox, no problem at all... (to get into, in openbox I couldn't even get in)
I am stuck into some problems. But first of all lets see my preffered setup:
Firefox= The GTK theme works partially, for navigation bar and then it gets the grey that the Raleigh theme had...
Sonata= ^same thing
pcmanfm= same thing...
Nitrogen= works but after reboot it resets the wallpaper to plain black
gimp=same gtk problem, but works
openoffice= I just dont know how to put in the menu Calc,Write ... it just has the main manager which from there you can open a presentation... Same problem with GTK
LXappearance=gtk themes,icons
and last, for now problem, is that when I installed an fluxbox theme the fonts looks huge... probably my fault...
It is run by ArchLinux on netbook Samsung nc10.
Any help is welcome.
Thanks in advance,
George
edit:
Last edited by ArchMan (2009-08-01 15:25:05)

Did you look at this?
http://wiki.archlinux.org/index.php/How … _look_nice
If you want to add openoffice to your Fluxbox Menu just edit ~/.fluxbox/menu
To get the right commands for openoffice just type in a terminal
soffice -h

Similar Messages

Pacman -Su - X fonts / fluxbox problem

Dang, I'm sorry to pile in with a ton of problems, but this one has really knocked me out.
I just did pacman -Sy and then pacman -Su and I seem to have completely hosed the X font server. I seem to remember reading something somewhere about this recently, but now i can't find it.
The upgrade didn't go smoothly and I've probably screwed something up.
First it crashed in the download complaining of xemacs-sumo from unofficial. I removed this package and then it completed the download and moved to dependency check.
Then the dependency check kept complaining about a ton of stuff in:
/usr/share/cups/model/... and
/usr/share/locale/de/LC_MESSAGES/ something.mo
as well as the same file in a few other languages ja, and two or three others.
Here I probably did a bad thing,I deleted these directories and files.
This let the upgrade proceed to completion but it wasn't good afterward.
At first I tried to fire up mozilla and I just get Exit 1. Then I exited X and rebooted but afterward, when I startx, fluxbox has these microscopic menus and slot. I exit X and find messages complaining about missing fonts.
Any advice (other than Hit the Road 8-) is very much appreciated.
Thank You...
John E. A.

if you really want to have the 1.4a version of mozilla then:
as root run :
abs
then:
cd /usr/abs/network/mozilla
<youreditor> PKGBUILD
change the pkver line to 1.4a then edit the source=() to the prper url to the 1.4a source.
then issue:
makepkg
sit back and wait while it compiles. when it is done
pacman -U mozilla-1.4a-1.pkg.tar.gz
you do not need to install the lib or include packages that are also built.
the whole process will take about an hour if you are using about a 1.53 GHz chip.

Annoying fluxbox problems

Hello, I am trying to switch to fluxbox and I have two problems.
1) I have this problem where, no matter how many times I right click, the fluxbox menu will not appear. How can I fix this?
2) I have fbsetbg -c path/of/wallpaper/ set in ~/.fluxbox/init. fbsetbg starts, but the wallpaper is displayed, and then it goes away (covered completely by some gray color)
Last edited by NoOneImportant (2007-09-14 08:24:22)

... can't say anything about your first question, but this link might help with the second one:
http://gentoo-wiki.com/HOWTO_Fluxbox#Se … ng_fbsetbg

Fluxbox problem

Hey,
When i open fluxbox, my menu comes up when i click and everything, but the only thing that opens when i click on it in the menu is gaim, and the configuration stuff, but none of the programs load except for gaim. I Can't even bring up a terminal, because when i go to Terminal > terminal-name, nothing happens. Does anyone know why this is? And on the side, whats the hot key fluxbox to bring up a terminal? Just so that i can use the forums from my linux box.
thanks

He's not being an ass... When I first loaded fluxbox I had nothing on my computer besides xorg. But the menu came fully loaded down.
You can always access your virtual terminals via Ctrl+alt+F2 thru F5 and come back to the X session via Ctrl+alt+F7
I manually set up my FBmenu but I believe there is a package to auto generate your menus for you.
if you want to manually do it the menu is in ~/.fluxbox/menu
Last edited by heathen (2007-02-22 02:01:51)

Fluxbox browser window resize

When I go to a site that opens an image in a new window, then resizes that window to fit the image, fluxbox is resizing the window so the title bar is outside of the workspace. This means I can not close, move, maximize or minimize the window without first holding down the Alt key and dragging it down some.
Anyone know how to keep Fluxbox from resizing a window outside of the actual workspace?
If it matters, this behaviour is not happening in Gnome.

dp wrote:
this is not a fluxbox problem, but a bad webmaster :-)
i would suggest you to use a browser that can override javascript from resizing windows larger than the screen (i use konqueror and all new windows open in new tags and are not allowed to resize the master window)
EDIT: ion does not allow windows to be bigger than the screen
Well this problem does not happen with Mozilla in either GNOME or KDE, but does happen with Mozilla in Fluxbox. This would suggest to me that Fluxbox is handling the popup differently than other window managers.
I looked at the HTML and it seems to me that the webmaster is simply telling the browser to open a new window and passing along a size with no window placement information. Mozilla is then opening up the window with the titlebar off the screen. I would say it is Mozilla's problem except Fluxbox is the only window manager I have that is exhibiting the problem.
Here is an extremely simple page that exhibits this problem:
http://www.sitepoint.com/examples/jscri … picfit.htm
The window is first opened correctly in the top left corner. The the Javascript resizes the window and the titlebar goes off the top. Again, this does not happen in GNOME or KDE, so my original questions remains. Is it possible to get Fluxbox to behave like GNOME and KDE and not run a portion of the window off the page?

Arch keeps freezing

I'm on a fresh arch install and for some reason X keeps freezing. At first I thought it was a firefox problem until arch froze without firefox running. Then I thought it was a fluxbox problem so I switched to openbox and it still froze. So I ran an xterm and everything froze...again.
I followed the wiki and set it up without an xorg.conf. HAL seems to handle everything.
Here's the output of lspci | grep VGA:
00:02.0 VGA compatible controller: Intel Corporation 82845G/GL[Brookdale-G]/GE Chipset Integrated Graphics Device (rev 01)
(I know...its shitty).
This computer's a Dell Dimension 2400. It has 2GB of RAM so it handles lightweight desktop environments just fine. Its 5 years old at most and I take quite good care of it. I don't think that its time to retire my old box....yet. I'm hoping that this is just a software problem. Thanks in advance.
Here's my Xorg.0.log
This is a pre-release version of the X server from The X.Org Foundation.
It is not supported in any way.
Bugs may be filed in the bugzilla at http://bugs.freedesktop.org/.
Select the "xorg" product for bugs you find in this release.
Before reporting bugs in pre-release versions please check the
latest version in the X.Org Foundation git repository.
See http://wiki.x.org/wiki/GitPage for git access instructions.
X.Org X Server 1.6.3.901 (1.6.4 RC 1)
Release Date: 2009-8-25
X Protocol Version 11, Revision 0
Build Operating System: Linux 2.6.30-ARCH i686
Current Operating System: Linux satori 2.6.30-ARCH #1 SMP PREEMPT Wed Sep 9 12:37:32 UTC 2009 i686
Build Date: 04 September 2009 03:37:03PM
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Thu Sep 17 12:42:50 2009
(II) Loader magic: 0xec0
(II) Module ABI versions:
X.Org ANSI C Emulation: 0.4
X.Org Video Driver: 5.0
X.Org XInput driver : 4.0
X.Org Server Extension : 2.0
(II) Loader running on linux
(--) using VT number 7
(--) PCI:*(0:0:2:0) 8086:2562:1028:0160 Intel Corporation 82845G/GL[Brookdale-G]/GE Chipset Integrated Graphics Device rev 1, Mem @ 0xf0000000/134217728, 0xfeb80000/524288
(==) Using default built-in configuration (39 lines)
(==) --- Start of built-in configuration ---
Section "Device"
Identifier "Builtin Default intel Device 0"
Driver "intel"
EndSection
Section "Screen"
Identifier "Builtin Default intel Screen 0"
Device "Builtin Default intel Device 0"
EndSection
Section "Device"
Identifier "Builtin Default i810 Device 0"
Driver "i810"
EndSection
Section "Screen"
Identifier "Builtin Default i810 Screen 0"
Device "Builtin Default i810 Device 0"
EndSection
Section "Device"
Identifier "Builtin Default vesa Device 0"
Driver "vesa"
EndSection
Section "Screen"
Identifier "Builtin Default vesa Screen 0"
Device "Builtin Default vesa Device 0"
EndSection
Section "Device"
Identifier "Builtin Default fbdev Device 0"
Driver "fbdev"
EndSection
Section "Screen"
Identifier "Builtin Default fbdev Screen 0"
Device "Builtin Default fbdev Device 0"
EndSection
Section "ServerLayout"
Identifier "Builtin Default Layout"
Screen "Builtin Default intel Screen 0"
Screen "Builtin Default i810 Screen 0"
Screen "Builtin Default vesa Screen 0"
Screen "Builtin Default fbdev Screen 0"
EndSection
(==) --- End of built-in configuration ---
(==) ServerLayout "Builtin Default Layout"
(**) |-->Screen "Builtin Default intel Screen 0" (0)
(**) | |-->Monitor "<default monitor>"
(**) | |-->Device "Builtin Default intel Device 0"
(==) No monitor specified for screen "Builtin Default intel Screen 0".
Using a default monitor configuration.
(**) |-->Screen "Builtin Default i810 Screen 0" (1)
(**) | |-->Monitor "<default monitor>"
(**) | |-->Device "Builtin Default i810 Device 0"
(==) No monitor specified for screen "Builtin Default i810 Screen 0".
Using a default monitor configuration.
(**) |-->Screen "Builtin Default vesa Screen 0" (2)
(**) | |-->Monitor "<default monitor>"
(**) | |-->Device "Builtin Default vesa Device 0"
(==) No monitor specified for screen "Builtin Default vesa Screen 0".
Using a default monitor configuration.
(**) |-->Screen "Builtin Default fbdev Screen 0" (3)
(**) | |-->Monitor "<default monitor>"
(**) | |-->Device "Builtin Default fbdev Device 0"
(==) No monitor specified for screen "Builtin Default fbdev Screen 0".
Using a default monitor configuration.
(==) Automatically adding devices
(==) Automatically enabling devices
(WW) The directory "/usr/share/fonts/Type1" does not exist.
Entry deleted from font path.
(==) FontPath set to:
/usr/share/fonts/misc,
/usr/share/fonts/100dpi:unscaled,
/usr/share/fonts/75dpi:unscaled,
/usr/share/fonts/TTF,
built-ins
(==) ModulePath set to "/usr/lib/xorg/modules"
(II) Cannot locate a core pointer device.
(II) Cannot locate a core keyboard device.
(II) The server relies on HAL to provide the list of input devices.
If no devices become available, reconfigure HAL or disable AllowEmptyInput.
(WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory)
(II) No APM support in BIOS or kernel
(II) System resource ranges:
[0] -1 0 0xffffffff - 0xffffffff (0x1) MX[b]
[1] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[b]
[2] -1 0 0x000c0000 - 0x000effff (0x30000) MX[b]
[3] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[b]
[4] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[b]
[5] -1 0 0x00000000 - 0x00000000 (0x1) IX[b]
(II) LoadModule: "extmod"
(II) Loading /usr/lib/xorg/modules/extensions//libextmod.so
(II) Module extmod: vendor="X.Org Foundation"
compiled for 1.6.3.901, module version = 1.0.0
Module class: X.Org Server Extension
ABI class: X.Org Server Extension, version 2.0
(II) Loading extension MIT-SCREEN-SAVER
(II) Loading extension XFree86-VidModeExtension
(II) Loading extension XFree86-DGA
(II) Loading extension DPMS
(II) Loading extension XVideo
(II) Loading extension XVideo-MotionCompensation
(II) Loading extension X-Resource
(II) LoadModule: "dbe"
(II) Loading /usr/lib/xorg/modules/extensions//libdbe.so
(II) Module dbe: vendor="X.Org Foundation"
compiled for 1.6.3.901, module version = 1.0.0
Module class: X.Org Server Extension
ABI class: X.Org Server Extension, version 2.0
(II) Loading extension DOUBLE-BUFFER
(II) LoadModule: "glx"
(II) Loading /usr/lib/xorg/modules/extensions//libglx.so
(II) Module glx: vendor="X.Org Foundation"
compiled for 1.6.3.901, module version = 1.0.0
ABI class: X.Org Server Extension, version 2.0
(==) AIGLX enabled
(II) Loading extension GLX
(II) LoadModule: "record"
(II) Loading /usr/lib/xorg/modules/extensions//librecord.so
(II) Module record: vendor="X.Org Foundation"
compiled for 1.6.3.901, module version = 1.13.0
Module class: X.Org Server Extension
ABI class: X.Org Server Extension, version 2.0
(II) Loading extension RECORD
(II) LoadModule: "dri"
(II) Loading /usr/lib/xorg/modules/extensions//libdri.so
(II) Module dri: vendor="X.Org Foundation"
compiled for 1.6.3.901, module version = 1.0.0
ABI class: X.Org Server Extension, version 2.0
(II) Loading extension XFree86-DRI
(II) LoadModule: "dri2"
(II) Loading /usr/lib/xorg/modules/extensions//libdri2.so
(II) Module dri2: vendor="X.Org Foundation"
compiled for 1.6.3.901, module version = 1.1.0
ABI class: X.Org Server Extension, version 2.0
(II) Loading extension DRI2
(II) LoadModule: "intel"
(II) Loading /usr/lib/xorg/modules/drivers//intel_drv.so
(II) Module intel: vendor="X.Org Foundation"
compiled for 1.6.3.901, module version = 2.8.1
Module class: X.Org Video Driver
ABI class: X.Org Video Driver, version 5.0
(II) LoadModule: "i810"
(WW) Warning, couldn't open module i810
(II) UnloadModule: "i810"
(EE) Failed to load module "i810" (module does not exist, 0)
(II) LoadModule: "vesa"
(II) Loading /usr/lib/xorg/modules/drivers//vesa_drv.so
(II) Module vesa: vendor="X.Org Foundation"
compiled for 1.6.0, module version = 2.2.0
Module class: X.Org Video Driver
ABI class: X.Org Video Driver, version 5.0
(II) LoadModule: "fbdev"
(WW) Warning, couldn't open module fbdev
(II) UnloadModule: "fbdev"
(EE) Failed to load module "fbdev" (module does not exist, 0)
(II) intel: Driver for Intel Integrated Graphics Chipsets: i810,
i810-dc100, i810e, i815, i830M, 845G, 852GM/855GM, 865G, 915G,
E7221 (i915), 915GM, 945G, 945GM, 945GME, IGD_GM, IGD_G, 965G, G35,
965Q, 946GZ, 965GM, 965GME/GLE, G33, Q35, Q33,
Mobile Intel® GM45 Express Chipset,
Intel Integrated Graphics Device, G45/G43, Q45/Q43, G41, IGDNG_D,
IGDNG_M
(II) VESA: driver for VESA chipsets: vesa
(II) Primary Device is: PCI 00@00:02:0
(II) resource ranges after xf86ClaimFixedResources() call:
[0] -1 0 0xffffffff - 0xffffffff (0x1) MX[b]
[1] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[b]
[2] -1 0 0x000c0000 - 0x000effff (0x30000) MX[b]
[3] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[b]
[4] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[b]
[5] -1 0 0x00000000 - 0x00000000 (0x1) IX[b]
(WW) Falling back to old probe method for vesa
(II) resource ranges after probing:
[0] -1 0 0xffffffff - 0xffffffff (0x1) MX[b]
[1] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[b]
[2] -1 0 0x000c0000 - 0x000effff (0x30000) MX[b]
[3] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[b]
[4] 0 0 0x000a0000 - 0x000affff (0x10000) MS[b]
[5] 0 0 0x000b0000 - 0x000b7fff (0x8000) MS[b]
[6] 0 0 0x000b8000 - 0x000bffff (0x8000) MS[b]
[7] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[b]
[8] -1 0 0x00000000 - 0x00000000 (0x1) IX[b]
[9] 0 0 0x000003b0 - 0x000003bb (0xc) IS[b]
[10] 0 0 0x000003c0 - 0x000003df (0x20) IS[b]
(II) Loading sub module "vgahw"
(II) LoadModule: "vgahw"
(II) Loading /usr/lib/xorg/modules//libvgahw.so
(II) Module vgahw: vendor="X.Org Foundation"
compiled for 1.6.3.901, module version = 0.1.0
ABI class: X.Org Video Driver, version 5.0
(II) Loading sub module "ramdac"
(II) LoadModule: "ramdac"
(II) Module "ramdac" already built-in
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is 9, (OK)
drmOpenByBusid: Searching for BusID pci:0000:00:02.0
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is 9, (OK)
drmOpenByBusid: drmOpenMinor returns 9
drmOpenByBusid: drmGetBusid reports pci:0000:00:02.0
(II) intel(0): Creating default Display subsection in Screen section
"Builtin Default intel Screen 0" for depth/fbbpp 24/32
(==) intel(0): Depth 24, (--) framebuffer bpp 32
(==) intel(0): RGB weight 888
(==) intel(0): Default visual is TrueColor
(II) intel(0): Integrated Graphics Chipset: Intel(R) 845G
(--) intel(0): Chipset: "845G"
(--) intel(0): Linear framebuffer at 0xF0000000
(--) intel(0): IO registers at addr 0xFEB80000 size 524288
(WW) intel(0): libpciaccess reported 0 rom size, guessing 64kB
(II) intel(0): No SDVO device is found in VBT
(II) intel(0): 1 display pipe available.
(II) Loading sub module "ddc"
(II) LoadModule: "ddc"
(II) Module "ddc" already built-in
(II) Loading sub module "i2c"
(II) LoadModule: "i2c"
(II) Module "i2c" already built-in
(II) intel(0): Output VGA has no monitor section
(II) intel(0): I2C bus "DVODDC_D" initialized.
(II) Loading sub module "sil164"
(II) LoadModule: "sil164"
(II) Loading /usr/lib/xorg/modules/drivers//sil164.so
(II) Module sil164: vendor="X.Org Foundation"
compiled for 1.6.3.901, module version = 1.0.0
ABI class: X.Org Video Driver, version 5.0
(II) intel(0): I2C bus "DVOI2C_E" initialized.
(II) Loading sub module "ch7xxx"
(II) LoadModule: "ch7xxx"
(II) Loading /usr/lib/xorg/modules/drivers//ch7xxx.so
(II) Module ch7xxx: vendor="X.Org Foundation"
compiled for 1.6.3.901, module version = 1.0.0
ABI class: X.Org Video Driver, version 5.0
(II) intel(0): I2C bus "DVOI2C_E" removed.
(II) intel(0): I2C bus "DVOI2C_E" initialized.
(II) Loading sub module "ivch"
(II) LoadModule: "ivch"
(II) Loading /usr/lib/xorg/modules/drivers//ivch.so
(II) Module ivch: vendor="X.Org Foundation"
compiled for 1.6.3.901, module version = 1.0.0
ABI class: X.Org Video Driver, version 5.0
(II) intel(0): I2C bus "DVOI2C_E" removed.
(II) intel(0): I2C bus "DVOI2C_B" initialized.
(II) Loading sub module "tfp410"
(II) LoadModule: "tfp410"
(II) Loading /usr/lib/xorg/modules/drivers//tfp410.so
(II) Module tfp410: vendor="X.Org Foundation"
compiled for 1.6.3.901, module version = 1.0.0
ABI class: X.Org Video Driver, version 5.0
(II) intel(0): I2C bus "DVOI2C_B" removed.
(II) intel(0): I2C bus "DVOI2C_E" initialized.
(II) Loading sub module "ch7017"
(II) LoadModule: "ch7017"
(II) Loading /usr/lib/xorg/modules/drivers//ch7017.so
(II) Module ch7017: vendor="X.Org Foundation"
compiled for 1.6.3.901, module version = 1.0.0
ABI class: X.Org Video Driver, version 5.0
(II) intel(0): I2C bus "DVOI2C_E" removed.
(II) intel(0): I2C bus "DVOI2C_E" initialized.
(II) intel(0): I2C bus "DVOI2C_E" removed.
(II) intel(0): I2C bus "DVODDC_D" removed.
(II) intel(0): I2C bus "CRTDDC_A" initialized.
(II) intel(0): I2C bus "CRTDDC_A" removed.
(II) intel(0): I2C bus "CRTDDC_A" initialized.
(II) intel(0): I2C device "CRTDDC_A:E-EDID segment register" registered at address 0x60.
(II) intel(0): I2C device "CRTDDC_A:ddc2" registered at address 0xA0.
(II) intel(0): I2C device "CRTDDC_A:ddc2" removed.
(II) intel(0): I2C device "CRTDDC_A:E-EDID segment register" removed.
(II) intel(0): I2C bus "CRTDDC_A" removed.
(II) intel(0): EDID vendor "DEL", prod id 40971
(II) intel(0): Using EDID range info for horizontal sync
(II) intel(0): Using EDID range info for vertical refresh
(II) intel(0): Printing DDC gathered Modelines:
(II) intel(0): Modeline "1280x1024"x0.0 108.00 1280 1328 1440 1688 1024 1025 1028 1066 +hsync +vsync (64.0 kHz)
(II) intel(0): Modeline "800x600"x0.0 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz)
(II) intel(0): Modeline "640x480"x0.0 31.50 640 656 720 840 480 481 484 500 -hsync -vsync (37.5 kHz)
(II) intel(0): Modeline "640x480"x0.0 25.18 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz)
(II) intel(0): Modeline "720x400"x0.0 28.32 720 738 846 900 400 412 414 449 -hsync +vsync (31.5 kHz)
(II) intel(0): Modeline "1280x1024"x0.0 135.00 1280 1296 1440 1688 1024 1025 1028 1066 +hsync +vsync (80.0 kHz)
(II) intel(0): Modeline "1024x768"x0.0 78.75 1024 1040 1136 1312 768 769 772 800 +hsync +vsync (60.0 kHz)
(II) intel(0): Modeline "1024x768"x0.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz)
(II) intel(0): Modeline "800x600"x0.0 49.50 800 816 896 1056 600 601 604 625 +hsync +vsync (46.9 kHz)
(II) intel(0): Modeline "1152x864"x0.0 108.00 1152 1216 1344 1600 864 865 868 900 +hsync +vsync (67.5 kHz)
(II) intel(0): Modeline "1280x1024"x0.0 108.00 1280 1328 1440 1688 1024 1025 1028 1066 +hsync +vsync (64.0 kHz)
(II) intel(0): EDID vendor "DEL", prod id 40971
(II) intel(0): Output VGA connected
(II) intel(0): Using exact sizes for initial modes
(II) intel(0): Output VGA using initial mode 1280x1024
(II) intel(0): detected 128 kB GTT.
(II) intel(0): detected 892 kB stolen memory.
(==) intel(0): video overlay key set to 0x101fe
(==) intel(0): Using gamma correction (1.0, 1.0, 1.0)
(**) intel(0): Display dimensions: (340, 270) mm
(**) intel(0): DPI set to (95, 96)
(II) Loading sub module "fb"
(II) LoadModule: "fb"
(II) Loading /usr/lib/xorg/modules//libfb.so
(II) Module fb: vendor="X.Org Foundation"
compiled for 1.6.3.901, module version = 1.0.0
ABI class: X.Org ANSI C Emulation, version 0.4
(II) intel(0): Comparing regs from server start up to After PreInit
(WW) intel(0): Register 0x70024 (PIPEASTAT) changed from 0x80000203 to 0x80000207
(WW) intel(0): PIPEASTAT before: status: FIFO_UNDERRUN VSYNC_INT_STATUS VBLANK_INT_STATUS OREG_UPDATE_STATUS
(WW) intel(0): PIPEASTAT after: status: FIFO_UNDERRUN VSYNC_INT_STATUS SVBLANK_INT_STATUS VBLANK_INT_STATUS OREG_UPDATE_STATUS
(II) UnloadModule: "vesa"
(II) Unloading /usr/lib/xorg/modules/drivers//vesa_drv.so
(==) Depth 24 pixmap format is 32 bpp
(II) do I need RAC? No, I don't.
(II) resource ranges after preInit:
[0] -1 0 0xffffffff - 0xffffffff (0x1) MX[b]
[1] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[b]
[2] -1 0 0x000c0000 - 0x000effff (0x30000) MX[b]
[3] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[b]
[4] 0 0 0x000a0000 - 0x000affff (0x10000) MS[b](OprD)
[5] 0 0 0x000b0000 - 0x000b7fff (0x8000) MS[b](OprD)
[6] 0 0 0x000b8000 - 0x000bffff (0x8000) MS[b](OprD)
[7] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[b]
[8] -1 0 0x00000000 - 0x00000000 (0x1) IX[b]
[9] 0 0 0x000003b0 - 0x000003bb (0xc) IS[b](OprU)
[10] 0 0 0x000003c0 - 0x000003df (0x20) IS[b](OprU)
(II) intel(0): Kernel reported 489216 total, 1 used
(II) intel(0): I830CheckAvailableMemory: 1956860 kB available
(II) intel(0): [DRI2] Setup complete
(**) intel(0): Framebuffer compression disabled
(**) intel(0): Tiling enabled
(**) intel(0): SwapBuffers wait enabled
(==) intel(0): VideoRam: 131072 KB
(II) intel(0): Attempting memory allocation with tiled buffers.
(II) intel(0): Tiled allocation successful.
(II) intel(0): vgaHWGetIOBase: hwp->IOBase is 0x03d0, hwp->PIOOffset is 0x0000
(II) UXA(0): Driver registered support for the following operations:
(II) solid
(II) copy
(II) composite (RENDER acceleration)
(==) intel(0): Backing store disabled
(==) intel(0): Silken mouse enabled
(II) intel(0): Initializing HW Cursor
(II) intel(0): xf86BindGARTMemory: bind key 0 at 0x07fff000 (pgoffset 32767)
(II) intel(0): Fixed memory allocation layout:
(II) intel(0): 0x000df000: end of stolen memory
(II) intel(0): 0x000df000-0x07ffefff: DRI memory manager (130176 kB)
(II) intel(0): 0x07fff000-0x07ffffff: overlay registers (4 kB, 0x000000003695f000 physical
(II) intel(0): 0x08000000: end of aperture
(II) intel(0): BO memory allocation layout:
(II) intel(0): 0x000df000: start of memory manager
(II) intel(0): 0x00800000-0x00ffffff: front buffer (8192 kB) X tiled
(II) intel(0): 0x00100000-0x00104fff: HW cursors (20 kB)
(II) intel(0): 0x07fff000: end of memory manager
(II) intel(0): Output configuration:
(II) intel(0): Pipe A is on
(II) intel(0): Display plane A is now enabled and connected to pipe A.
(II) intel(0): Output VGA is connected to pipe A
(II) intel(0): RandR 1.2 enabled, ignore the following RandR disabled message.
(II) intel(0): DPMS enabled
(==) intel(0): Intel XvMC decoder disabled
(II) intel(0): Set up overlay video
(II) intel(0): direct rendering: DRI2 Enabled
(--) RandR disabled
(II) Initializing built-in extension Generic Event Extension
(II) Initializing built-in extension SHAPE
(II) Initializing built-in extension MIT-SHM
(II) Initializing built-in extension XInputExtension
(II) Initializing built-in extension XTEST
(II) Initializing built-in extension BIG-REQUESTS
(II) Initializing built-in extension SYNC
(II) Initializing built-in extension XKEYBOARD
(II) Initializing built-in extension XC-MISC
(II) Initializing built-in extension SECURITY
(II) Initializing built-in extension XINERAMA
(II) Initializing built-in extension XFIXES
(II) Initializing built-in extension RENDER
(II) Initializing built-in extension RANDR
(II) Initializing built-in extension COMPOSITE
(II) Initializing built-in extension DAMAGE
(II) AIGLX: enabled GLX_MESA_copy_sub_buffer
(II) AIGLX: enabled GLX_SGI_swap_control and GLX_MESA_swap_control
(II) AIGLX: GLX_EXT_texture_from_pixmap backed by buffer objects
(II) AIGLX: Loaded and initialized /usr/lib/xorg/modules/dri/i915_dri.so
(II) GLX: Initialized DRI2 GL provider for screen 0
(II) intel(0): Setting screen physical size to 338 x 270
(II) config/hal: Adding input device Macintosh mouse button emulation
(II) LoadModule: "evdev"
(II) Loading /usr/lib/xorg/modules/input//evdev_drv.so
(II) Module evdev: vendor="X.Org Foundation"
compiled for 1.6.3, module version = 2.2.5
Module class: X.Org XInput Driver
ABI class: X.Org XInput driver, version 4.0
(**) Macintosh mouse button emulation: always reports core events
(**) Macintosh mouse button emulation: Device: "/dev/input/event0"
(II) Macintosh mouse button emulation: Found 3 mouse buttons
(II) Macintosh mouse button emulation: Found x and y relative axes
(II) Macintosh mouse button emulation: Configuring as mouse
(**) Macintosh mouse button emulation: YAxisMapping: buttons 4 and 5
(**) Macintosh mouse button emulation: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
(II) XINPUT: Adding extended input device "Macintosh mouse button emulation" (type: MOUSE)
(**) Macintosh mouse button emulation: (accel) keeping acceleration scheme 1
(**) Macintosh mouse button emulation: (accel) filter chain progression: 2.00
(**) Macintosh mouse button emulation: (accel) filter stage 0: 20.00 ms
(**) Macintosh mouse button emulation: (accel) set acceleration profile 0
(II) Macintosh mouse button emulation: initialized for relative axes.
(II) config/hal: Adding input device Dell Dell USB Mouse
(**) Dell Dell USB Mouse: always reports core events
(**) Dell Dell USB Mouse: Device: "/dev/input/event5"
(II) Dell Dell USB Mouse: Found 3 mouse buttons
(II) Dell Dell USB Mouse: Found x and y relative axes
(II) Dell Dell USB Mouse: Found scroll wheel(s)
(II) Dell Dell USB Mouse: Configuring as mouse
(**) Dell Dell USB Mouse: YAxisMapping: buttons 4 and 5
(**) Dell Dell USB Mouse: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
(II) XINPUT: Adding extended input device "Dell Dell USB Mouse" (type: MOUSE)
(**) Dell Dell USB Mouse: (accel) keeping acceleration scheme 1
(**) Dell Dell USB Mouse: (accel) filter chain progression: 2.00
(**) Dell Dell USB Mouse: (accel) filter stage 0: 20.00 ms
(**) Dell Dell USB Mouse: (accel) set acceleration profile 0
(II) Dell Dell USB Mouse: initialized for relative axes.
(II) config/hal: Adding input device AT Translated Set 2 keyboard
(**) AT Translated Set 2 keyboard: always reports core events
(**) AT Translated Set 2 keyboard: Device: "/dev/input/event1"
(II) AT Translated Set 2 keyboard: Found keys
(II) AT Translated Set 2 keyboard: Configuring as keyboard
(II) XINPUT: Adding extended input device "AT Translated Set 2 keyboard" (type: KEYBOARD)
(**) Option "xkb_rules" "evdev"
(**) Option "xkb_model" "evdev"
(**) Option "xkb_layout" "us"
(II) config/hal: Adding input device Power Button
(**) Power Button: always reports core events
(**) Power Button: Device: "/dev/input/event3"
(II) Power Button: Found keys
(II) Power Button: Configuring as keyboard
(II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD)
(**) Option "xkb_rules" "evdev"
(**) Option "xkb_model" "evdev"
(**) Option "xkb_layout" "us"
(II) config/hal: Adding input device Power Button
(**) Power Button: always reports core events
(**) Power Button: Device: "/dev/input/event2"
(II) Power Button: Found keys
(II) Power Button: Configuring as keyboard
(II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD)
(**) Option "xkb_rules" "evdev"
(**) Option "xkb_model" "evdev"
(**) Option "xkb_layout" "us"
(II) Macintosh mouse button emulation: Close
(II) UnloadModule: "evdev"
(II) Dell Dell USB Mouse: Close
(II) UnloadModule: "evdev"
(II) AT Translated Set 2 keyboard: Close
(II) UnloadModule: "evdev"
(II) Power Button: Close
(II) UnloadModule: "evdev"
(II) Power Button: Close
(II) UnloadModule: "evdev"
(II) intel(0): xf86UnbindGARTMemory: unbind key 0

loafer wrote:If creating a new user solves it then surely one of the configs in the home directory is at fault. It couldn't be anything else in that case. However, as Dheart points out there are some issues with the driver itself so creating a new user would not affect that at all. The only thing creating a new user would do is give you a new set of configs in a clean home dir. So it would be much better to just fix the config files.
no, its not easy as you think. since linux 2.6.30 kernel my system acts strange sometimes. for example about that konqueror problem. when i tried to open www.ubuntu.lt then konqueror crashed. running from konsole konqueror and entering same address i see memory access errors. and when i renamed ~/kdemod folder, my kdemod reset to default settings, but konqueror still crashed on that website. i tried reinstalling kdemod metapackage, but it didnt help, and my permissions were fine. so ive created new user, and used same home folder as the previous user, and konqueror started to dont crash on that website. how could you explain that?

Trayer Transparency Doesn't Work

I changed this from a fluxbox problem to a trayer problem, but they could be related. I am trying to get trayer to be transparent but it is just starting as a white box. I issue the command
trayer --edge top --align right --widthtype pixel --width 200 --transparent true --alpha 255 &
Any ideas
Thanks
Last edited by cu3edweb (2007-11-11 02:44:12)

sure. I edited the current pkgbuild and installed 0.74. You can do the same if you like. You can set the location / size very easily in the config, and also other settings.
here is my config:
# vim:filetype=config:tw=80:et
# This is sample ~/.stalonetrayrc, resembling default configuration.
# Remember: command line parameters take precedence.
# Directives introduced in 0.7.4 are marked with "NEW in 0.7.4"
# stalonetray understands following directives
# background <color> # color can be specified as an HTML hex triplet or
# as a name from rgb.txt, note that '#' must be quoted
background "#777777"
# decorations <decspec> # set trays window decorations; possible values for
# decspec are: all, title, border, none
decorations none
# display <display name> # as usual
# dbg_level <int> # controls the amount of debug info (for this setting to
# have effect, stalonetray sources must have been
# configured and compiled with --enable-debug)
# dbg_level 2
# fuzzy_edges [<level>] # enable fuzzy edges and set fuzziness level. level
# can be from 0 (disabled) to 3; this setting works
# with tinting and/or transparent and/or pixmap
# backgrounds (NEW in 0.7)
fuzzy_edges 0
# geometry <geometry> # tray's geometry in standard X notation
geometry 140x64-50-14
# grow_gravity <gravity> # one of N, S, E, W, NW, NE, SW, SE; tray will grow
# in the direction opposite to one specified by
# grow_gravity; if horizontal or vertical
# direction is not specified, tray will not grow in
# that direction
grow_gravity NW
# icon_gravity <gravity> # icon placement gravity, one of NW, NE, SW, SE
icon_gravity NW
# icon_size <int> # specifies dimensions of typical icon slot
icon_size 34
# ignore_icon_resize [<bool>] # ignore icon attempts to resize their windows
# (NEW in 0.7)
ignore_icon_resize false
# max_width <int> # specifies maximal tray's width (0 = no limit)
max_width 0
# max_height <int> # specifies maximal tray's height (0 = no limit)
max_height 0
# no_shrink [<bool>] # disables shrink-back mode (NEW in 0.7)
no_shrink false
# parent_bg [<bool>] # whether to use pseudo-transparency
# (looks better when reparented into smth like FvwmButtons)
parent_bg false
# pixmap_bg <path_to_xpm> # use pixmap from specified xpm file for (tiled) background
# pixmap_bg /home/user/.stalonetraybg.xpm
# respect_icon_hints [<bool>] # try to respect icon hints (NEW in 0.7)
respect_icon_hints false
# skip_taskbar [<bool>] # hide tray`s window from the taskbar
skip_taskbar true
# sticky [<bool>] # make a tray`s window sticky across the
# desktops/pages
sticky true
# tint_color <color> # set tinting color (NEW in 0.7)
tint_color white
# tint_level <level> # set tinting level; level ranges from 0 (disabled)
# to 255 (NEW in 0.7)
tint_level 85
# transparent [<bool>] # whether to use root-transparency (background
# image must be set with Esetroot or compatible utility)
transparent true
# vertical [<bool>] # whether to use vertical layout (horisontal layout
# is used by default)
vertical false
# window_layer <layer> # set the EWMH-compatible window layer; one of:
# bootom, normal, top
window_layer normal
# window_type <type> # set the EWMH-compatible window type; one of:
# dock, normal, toolbar, utility
window_type dock
# withdrawn [<bool>] # start withdrawn (NEW in 0.7, prior to that
# withdrawn mode was default!)
withdrawn false
# xsync [<bool>] # whether to operate on X server synchronously (SLOOOOW)
xsync false

Irritating problem with Fluxbox and pressing Ctrl + F3

I've used the Ctrl + F1, F2, F3 or F4 keys to switch between workspaces in Fluxbox but occasionally I'll press Ctrl + F3 and it will just log me out. This is highly annoying. Is there some way I can disable this functionality at all? I switch between workspaces regularly and it is highly annoying to have to reopen everything again after being logged out and it means I lose my train of thought with my work.
Can anyone offer a solution to this problem at all? Thanks.
Last edited by Cromulent (2012-11-30 22:58:50)

It just happened again when I was using Spotify.
I had the following apps open:
Chromium - Workspace 1
Thunderbird - Workspace 2
KVirc - Workspace 3
Spotify - Workspace 4
When in Workspace 4 I pressed Ctrl + F3 as normal and it logged me out. So I logged back in and opened Spotify in Workspace 4 again and tried to get it to log out again and no matter what combination of keys and Workspace changes I did I couldn't get it to log me out again. I'm stumped.
Edit: I think the problem is KVirc. Everytime I use it this happens. I'll see if it happens again without it running for a couple of days (it just happened when using the arrows on the tool bar as well so it has nothing to do with the key combination). It would be annoying if this was the case as I quite like KVirc as a my IRC client.
Edit 2: Switched over to XChat. Will see if the problem persists.
Last edited by Cromulent (2012-11-30 14:10:55)

Problem with going through Fluxbox menus

Hello!
http://i.imgur.com/AHTii.jpg
I have a problem. Right-click to open the menu, then I go until the "choose a style" or somewhere deeper. When I come back to something like "File utils" and still the cursor, it doesn't open further menu automatically like those from the beginning to "choose a style". I have to click to open it. When I was going down to "choose a style" - menus were opening automatically with some delay, as it's supposed to be. But it always stops to behave like this after few menus I go through until I close the whole menu and open it again with right-click. I have the latest Fluxbox and everything up to date. Help me to fix this please.

Yea I noticed the same problem...
I haven't used fluxbox in quite a while..I just installed it recently because I couldn't get awesome-wm to build properly after reinstalling arch due to hard-drive failure..

[SOLVED] Fluxbox won't work and mirror problem

Hello all, I recently tried to make the switch to Arch again from Ubuntu. Ran into some trouble though. Obviously I was using the 64 bit version. It installed just fine, but once I booted into it I couldn't use pacman to install anything or even refresh. After a bit of playing I found the file where the mirrors hide. The one I set in installation was uncommented as it should be but not working so up above I uncommented the same one (ibilio) and that fixed that. Is that a normal problem? Anyhow no biggie so I moved on. I go for straight Fluxbox. So I installed xorg and fluxbox. But for the life of me I can not get it to boot to fluxbox. Keeps going to twm. I tried everything in the fluxbox guide from the Arch wiki to get it going with no luck. Finally gave up and went back to Ubuntu. Now I used the 32 bit a time or two on an old computer and fluxbox worked fine. Here like I say startx would bring up twm. And startfluxbox (think thats the right command) would get a cannot connect to xserver error. Any ideas? I sure would love to use Arch. Sorry I can't be more precise on how it went but I no longer have it installed. If someone thinks they can help me with this though I would love to try again. Thanks.
Last edited by The Avatar of Time (2008-02-16 07:32:36)

Ah, sorry, I should have specified that you add it to your ~/.xinitrc file, and you will most likely have to make then edit that file (as I did) yourself.
touch ~/.xinitrc
and then, with your text editor of choice add this line to that file
exec startfluxbox
and save. If that still doesn't work let me know
You will always get kicked back to the command line, as X cannot find any login manager, and you had no user-specified fallback file that it would look for instead, so it fell back finally on the system-wide fallback, which is TWM.
So you have to rely on writing your own way to start x, which is the ~/.xinitrc file. Otherwise it will always find twm.
If you really don't want twm, you can easily remove it (I don't have it installed at all) with a simple 'pacman -R xorg-twm'.
HTH
Last edited by wyvern (2008-02-15 18:45:07)

Fluxbox transparency problem

Hello
I set 60-70% transparency for my xfce terminal in fluxbox, transparency works, i see pulpit, but when some items are "under" terminal i should see him but i see only puplit...
And i dont se animation of moving wallpaper under my terminal , they changes when i "drop" terminal to some place
i have hope for answers, greetings

Yes i configure it, and its works, shadows,transparency etc, its my compton.conf file:
# Shadow
shadow = true;
no-dnd-shadow = true;
no-dock-shadow = true;
#clear-shadow = true;
#shadow-radius = 7;
#shadow-offset-x = -7;
#shadow-offset-y = -7;
shadow-opacity = 0.4;
# shadow-red = 0.0;
# shadow-green = 0.0;
# shadow-blue = 0.0;
shadow-exclude = [ "n:e:xfce4-notifyd" ];
#shadow-ignore-shaped = false;
# Opacity
menu-opacity = 0.9;
#inactive-opacity = 0.8;
#frame-opacity = 0.7;
inactive-opacity-override = false;
alpha-step = 0.06;
# Fading
fading = false;
# fade-delta = 30;
fade-in-step = 0.03;
fade-out-step = 0.03;
# no-fading-openclose = true;
# Other
mark-wmwin-focused = true;
mark-ovredir-focused = true;
detect-rounded-corners = true;
detect-client-opacity = true;
#refresh-rate = 0;
#vsync = "none";
dbe = false;
paint-on-overlay = false;
sw-opti = false;
# Window type settings
wintypes:
tooltip = { fade = true; shadow = false; opacity =
0.85; };
Any ideas how to fix problem ?

Opera && Fluxbox && Fonts problem

I use Opera installed with Fluxbox and X all installed via pacman. But there is a strange problem with opera. The transfer manager ... has white on white fonts or no fonts at all. So I cant see a damn!
Anyone has any ideas?

When I open it ... I always get this error!
ERROR: ld.so: object 'libjvm.so' from LD_PRELOAD cannot be preloaded: ignored.
ERROR: ld.so: object 'libawt.so' from LD_PRELOAD cannot be preloaded: ignored.
Where do I get this libraries from?

Fluxbox docky problem

I got problem with docky, I want to use it isntead of default fluxbox panel but... look at this image
http://oi42.tinypic.com/2mr5q1k.jpg
how to remove this black blocks ?
#edit
xcompmgr with shadows setting did it !
Last edited by chosen (2013-06-09 19:03:33)

Chosen,
That picture is larger than permitted by our policy, but it is central to your thread. I will leave it for now, but we may change it to url tags from img tags in the future. When this thread is solved, please consider making that edit yourself.
Thanks.

Fluxbox + Xinerama = fglrx problems

Hi everyone,
I'm new to Arch Linux, I have two years experience using (X)Ubuntu.
I've installed fluxbox as my WM and wanted to use two screens! I've got it all working via the aticonfig, which gave me a dual screen setup (amdccle calls it Single). After that I've enabled Xinerama in my xorg.conf which in turn gave some other troubles.
First fglrxinfo gives a blank line. glxgears shows an error:
$ glxgears
XIO: fatal IO error 11 (Resource temporarily unavailable) on X server ":0.0"
after 2359 requests (2358 known processed) with 0 events remaining.
* From the top of my head
Why googling the problem I've only found that fluxbox needs to be build with Xinerama support! Is this the done with the package in pacman? Probably yes as Xinerama works partly!
Thanks in advance for any help and pointers!
Grtz,
Arjan Gelderblom

Fade wrote:If you post it here then maybe someone more knowledgeable will be able to point you in the right direction.
Here it is... Thanks for any help,
Arjan Gelderblom
xorg.conf
# Auto-generated by Archie mkxcfg
# Auto-generated by Archie mkxcfg
Section "ServerLayout"
# Serial Mouse not detected
# USB Mouse not detected
Identifier "Xorg Configured"
Screen 0 "aticonfig-Screen[0]-0" 0 0
Screen "aticonfig-Screen[0]-1" RightOf "aticonfig-Screen[0]-0"
InputDevice "Keyboard0" "CoreKeyboard"
InputDevice "PS/2 Mouse" "CorePointer"
EndSection
Section "Files"
# Additional fonts: Locale, Gimp, TTF...
# FontPath "/usr/share/lib/X11/fonts/latin2/75dpi"
# FontPath "/usr/share/lib/X11/fonts/latin2/100dpi"
# True type and type1 fonts are also handled via xftlib, see /etc/X11/XftConfig!
RgbPath "/usr/share/X11/rgb"
ModulePath "/usr/lib/xorg/modules"
FontPath "/usr/share/fonts/misc:unscaled"
FontPath "/usr/share/fonts/misc"
FontPath "/usr/share/fonts/75dpi:unscaled"
FontPath "/usr/share/fonts/75dpi"
FontPath "/usr/share/fonts/100dpi:unscaled"
FontPath "/usr/share/fonts/100dpi"
FontPath "/usr/share/fonts/PEX"
FontPath "/usr/share/fonts/cyrillic"
FontPath "/usr/share/fonts/Type1"
FontPath "/usr/share/fonts/ttf/western"
FontPath "/usr/share/fonts/ttf/decoratives"
FontPath "/usr/share/fonts/truetype"
FontPath "/usr/share/fonts/truetype/openoffice"
FontPath "/usr/share/fonts/truetype/ttf-bitstream-vera"
FontPath "/usr/share/fonts/latex-ttf-fonts"
FontPath "/usr/share/fonts/defoma/CID"
FontPath "/usr/share/fonts/defoma/TrueType"
EndSection
Section "Module"
Load "ddc" # ddc probing of monitor
Load "dbe"
Load "dri"
Load "extmod"
Load "glx"
Load "bitmap" # bitmap-fonts
# Load "type1"
Load "freetype"
Load "record"
# Load "synaptics"
EndSection
Section "ServerFlags"
Option "AllowMouseOpenFail" "true"
# Option "Xinerama" "true"
EndSection
Section "InputDevice"
Identifier "Keyboard0"
Driver "keyboard"
Option "CoreKeyboard"
Option "XkbRules" "xorg"
Option "XkbModel" "pc105"
Option "XkbLayout" "us"
Option "XkbVariant" ""
EndSection
Section "InputDevice"
Identifier "Serial Mouse"
Driver "mouse"
Option "Protocol" "Microsoft"
Option "Device" "/dev/ttyS0"
Option "Emulate3Buttons" "true"
Option "Emulate3Timeout" "70"
Option "SendCoreEvents" "true"
EndSection
Section "InputDevice"
Identifier "PS/2 Mouse"
Driver "mouse"
Option "Protocol" "auto"
Option "ZAxisMapping" "4 5"
Option "Device" "/dev/psaux"
Option "Emulate3Buttons" "true"
Option "Emulate3Timeout" "70"
Option "SendCoreEvents" "true"
EndSection
Section "InputDevice"
Identifier "USB Mouse"
Driver "mouse"
Option "Device" "/dev/input/mice"
Option "SendCoreEvents" "true"
Option "Protocol" "IMPS/2"
Option "ZAxisMapping" "4 5"
Option "Buttons" "5"
EndSection
Section "Monitor"
# Warning: This may fry old Monitors
# Very conservative. May flicker.
# VertRefresh 50.0 - 62.0 # Extreme conservative. Will flicker. TFT default.
# Default modes distilled from
# "VESA and Industry Standards and Guide for Computer Display Monitor
# Timing", version 1.0, revision 0.8, adopted September 17, 1998.
# $XFree86: xc/programs/Xserver/hw/xfree86/etc/vesamodes,v 1.4 1999/11/18 16:52:17 tsi Exp $
# 640x350 @ 85Hz (VESA) hsync: 37.9kHz
Identifier "Monitor0"
HorizSync 28.0 - 96.0
VertRefresh 50.0 - 75.0
ModeLine "640x350" 31.5 640 672 736 832 350 382 385 445 +hsync -vsync
ModeLine "640x400" 31.5 640 672 736 832 400 401 404 445 -hsync +vsync
ModeLine "720x400" 35.5 720 756 828 936 400 401 404 446 -hsync +vsync
ModeLine "640x480" 25.2 640 656 752 800 480 490 492 525 -hsync -vsync
ModeLine "640x480" 31.5 640 664 704 832 480 489 491 520 -hsync -vsync
ModeLine "640x480" 31.5 640 656 720 840 480 481 484 500 -hsync -vsync
ModeLine "640x480" 36.0 640 696 752 832 480 481 484 509 -hsync -vsync
ModeLine "800x600" 36.0 800 824 896 1024 600 601 603 625 +hsync +vsync
ModeLine "800x600" 40.0 800 840 968 1056 600 601 605 628 +hsync +vsync
ModeLine "800x600" 50.0 800 856 976 1040 600 637 643 666 +hsync +vsync
ModeLine "800x600" 49.5 800 816 896 1056 600 601 604 625 +hsync +vsync
ModeLine "800x600" 56.3 800 832 896 1048 600 601 604 631 +hsync +vsync
ModeLine "1024x768" 44.9 1024 1032 1208 1264 768 768 776 817 +hsync +vsync interlace
ModeLine "1024x768" 65.0 1024 1048 1184 1344 768 771 777 806 -hsync -vsync
ModeLine "1024x768" 75.0 1024 1048 1184 1328 768 771 777 806 -hsync -vsync
ModeLine "1024x768" 78.8 1024 1040 1136 1312 768 769 772 800 +hsync +vsync
ModeLine "1024x768" 94.5 1024 1072 1168 1376 768 769 772 808 +hsync +vsync
ModeLine "1152x864" 108.0 1152 1216 1344 1600 864 865 868 900 +hsync +vsync
ModeLine "1280x960" 108.0 1280 1376 1488 1800 960 961 964 1000 +hsync +vsync
ModeLine "1280x960" 148.5 1280 1344 1504 1728 960 961 964 1011 +hsync +vsync
ModeLine "1280x1024" 108.0 1280 1328 1440 1688 1024 1025 1028 1066 +hsync +vsync
ModeLine "1280x1024" 135.0 1280 1296 1440 1688 1024 1025 1028 1066 +hsync +vsync
ModeLine "1280x1024" 157.5 1280 1344 1504 1728 1024 1025 1028 1072 +hsync +vsync
ModeLine "1600x1200" 162.0 1600 1664 1856 2160 1200 1201 1204 1250 +hsync +vsync
ModeLine "1600x1200" 175.5 1600 1664 1856 2160 1200 1201 1204 1250 +hsync +vsync
ModeLine "1600x1200" 189.0 1600 1664 1856 2160 1200 1201 1204 1250 +hsync +vsync
ModeLine "1600x1200" 202.5 1600 1664 1856 2160 1200 1201 1204 1250 +hsync +vsync
ModeLine "1600x1200" 229.5 1600 1664 1856 2160 1200 1201 1204 1250 +hsync +vsync
ModeLine "1792x1344" 204.8 1792 1920 2120 2448 1344 1345 1348 1394 -hsync +vsync
ModeLine "1792x1344" 261.0 1792 1888 2104 2456 1344 1345 1348 1417 -hsync +vsync
ModeLine "1856x1392" 218.3 1856 1952 2176 2528 1392 1393 1396 1439 -hsync +vsync
ModeLine "1856x1392" 288.0 1856 1984 2208 2560 1392 1393 1396 1500 -hsync +vsync
ModeLine "1920x1440" 234.0 1920 2048 2256 2600 1440 1441 1444 1500 -hsync +vsync
ModeLine "1920x1440" 297.0 1920 2064 2288 2640 1440 1441 1444 1500 -hsync +vsync
ModeLine "1800x1440" 230.0 1800 1896 2088 2392 1440 1441 1444 1490 +hsync +vsync
ModeLine "1800x1440" 250.0 1800 1896 2088 2392 1440 1441 1444 1490 +hsync +vsync
ModeLine "640x480" 43.2 640 680 744 848 480 481 484 509 -hsync +vsync
ModeLine "768x576" 35.0 768 792 872 976 576 577 580 597 -hsync +vsync
ModeLine "768x576" 42.9 768 800 880 992 576 577 580 601 -hsync +vsync
ModeLine "768x576" 45.5 768 808 888 1008 576 577 580 602 -hsync +vsync
ModeLine "768x576" 51.8 768 808 888 1008 576 577 580 605 -hsync +vsync
ModeLine "768x576" 62.6 768 816 896 1024 576 577 580 611 -hsync +vsync
ModeLine "800x600" 68.2 800 848 936 1072 600 601 604 636 -hsync +vsync
ModeLine "1024x768" 113.3 1024 1096 1208 1392 768 769 772 814 -hsync +vsync
ModeLine "1152x864" 81.6 1152 1216 1336 1520 864 865 868 895 -hsync +vsync
ModeLine "1152x864" 119.7 1152 1224 1352 1552 864 865 868 907 -hsync +vsync
ModeLine "1152x864" 143.5 1152 1232 1360 1568 864 865 868 915 -hsync +vsync
ModeLine "1280x960" 124.5 1280 1368 1504 1728 960 961 964 1001 -hsync +vsync
ModeLine "1280x960" 129.9 1280 1368 1504 1728 960 961 964 1002 -hsync +vsync
ModeLine "1280x960" 179.0 1280 1376 1520 1760 960 961 964 1017 -hsync +vsync
ModeLine "1280x1024" 191.0 1280 1376 1520 1760 1024 1025 1028 1085 -hsync +vsync
ModeLine "1400x1050" 122.6 1400 1488 1640 1880 1050 1051 1054 1087 -hsync +vsync
ModeLine "1400x1050" 149.3 1400 1496 1648 1896 1050 1051 1054 1094 -hsync +vsync
ModeLine "1400x1050" 155.8 1400 1496 1648 1896 1050 1051 1054 1096 -hsync +vsync
ModeLine "1400x1050" 179.3 1400 1504 1656 1912 1050 1051 1054 1103 -hsync +vsync
ModeLine "1400x1050" 214.4 1400 1512 1664 1928 1050 1051 1054 1112 -hsync +vsync
ModeLine "1600x1200" 280.6 1600 1728 1904 2208 1200 1201 1204 1271 -hsync +vsync
Option "DPMS" "true"
# HorizSync 28.0 - 78.0 # Warning: This may fry very old Monitors
EndSection
Section "Monitor"
Identifier "aticonfig-Monitor[0]-0"
Option "VendorName" "ATI Proprietary Driver"
Option "ModelName" "Generic Autodetecting Monitor"
Option "DPMS" "true"
EndSection
Section "Monitor"
Identifier "aticonfig-Monitor[0]-1"
Option "VendorName" "ATI Proprietary Driver"
Option "ModelName" "Generic Autodetecting Monitor"
Option "DPMS" "true"
EndSection
Section "Device"
Identifier "Card0"
Driver "vesa"
VendorName "All"
BoardName "All"
EndSection
Section "Device"
Identifier "aticonfig-Device[0]-0"
Driver "fglrx"
BusID "PCI:1:0:0"
EndSection
Section "Device"
Identifier "aticonfig-Device[0]-1"
Driver "fglrx"
BusID "PCI:1:0:0"
Screen 1
EndSection
Section "Screen"
Identifier "Screen0"
Device "Card0"
Monitor "Monitor0"
DefaultDepth 16
SubSection "Display"
Depth 1
Modes "1024x768" "800x600" "640x480"
EndSubSection
SubSection "Display"
Depth 4
Modes "1024x768" "800x600" "640x480"
EndSubSection
SubSection "Display"
Depth 8
Modes "1024x768" "800x600" "640x480"
EndSubSection
SubSection "Display"
Depth 15
Modes "1024x768" "800x600" "640x480"
EndSubSection
SubSection "Display"
Depth 16
Modes "1024x768" "800x600" "640x480"
EndSubSection
SubSection "Display"
Depth 24
Modes "1024x768" "800x600" "640x480"
EndSubSection
SubSection "Display"
Depth 32
Modes "1024x768" "800x600" "640x480"
EndSubSection
EndSection
Section "Screen"
Identifier "aticonfig-Screen[0]-0"
Device "aticonfig-Device[0]-0"
Monitor "aticonfig-Monitor[0]-0"
DefaultDepth 24
SubSection "Display"
Viewport 0 0
Depth 24
EndSubSection
EndSection
Section "Screen"
Identifier "aticonfig-Screen[0]-1"
Device "aticonfig-Device[0]-1"
Monitor "aticonfig-Monitor[0]-1"
DefaultDepth 24
SubSection "Display"
Viewport 0 0
Depth 24
EndSubSection
EndSection
Section "DRI"
Mode 0666
EndSection
Section "Extensions"
Option "Composite" "Enable"
EndSection
Last edited by Bloged (2008-11-13 09:23:03)

SOLVED Fluxbox and Nitrogen problem

Ok so I've tried many ways to set my background in Fluxbox. I try not to ask for help but this is really frustrating me. So I installed nitrogen, went to the directory my background is at, and hit apply, and it worked. So then I went to my ~/.fluxbox/startup file and added in "nitrogen --restore &" like below. However it didn't work. I really want this to work, I spent a large amount of time earlier today trying to get fbsetbg to work, then trying to get feh to work, none of it worked for me.
# Applications you want to run with fluxbox.
# MAKE SURE THAT APPS THAT KEEP RUNNING HAVE AN ''&'' AT THE END.
# unclutter -idle 2 &
# wmnd &
# wmsmixer -w &
# idesk &
nitrogen --restore &
# And last but not least we start fluxbox.
# Because it is the last app you have to run it with ''exec'' before it.
Last edited by Spheres (2012-08-05 23:09:15)

Not necessarily.
Do any other apps you put in ~/.fluxbox/startup run?
Check /usr/share/xsessions/fluxbox.desktop and make sure it says "exec startfluxbox" and not just "exec fluxbox"
I'm starting fluxbox from .xinitrc with "exec startfluxbox" and if I set wallpaper with feh, this works in my ~/.fluxbox/startup file:
eval $(cat ~/.fehbg)
and if I set wallpaper with nitrogen, this works:
nitrogen --restore
(edit) -- as ewaller says, have you set a wallpaper with nitrogen? "nitrogen --restore" won't work unless you do...
Last edited by 2ManyDogs (2012-08-05 19:35:47)

FluxBox Problems

Similar Messages

Maybe you are looking for