| Summary: | windowmaker-0.91.0-r1 Fatal Error message with invalid RgbPath setting | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Paul Varner (RETIRED) <fuzzyray> |
| Component: | Current packages | Assignee: | Luis Medinas (RETIRED) <metalgod> |
| Status: | RESOLVED WONTFIX | ||
| Severity: | normal | CC: | x11 |
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Attachments: | Log file from VNC server | ||
|
Description
Paul Varner (RETIRED)
2004-12-07 14:47:50 UTC
Created attachment 45470 [details]
Log file from VNC server
Since I had this working previously, I did some more testing. The 0.80* series of Window Maker work just fine under VNC, The 0.90 and 0.91 versions do not and give the segmentation faults. I didn't do enough testing. While the 0.80 versions start, if I try to actually do anything, I get the same fatal error dialog box. The problem also occurs under vnc-4.0 I fixed the problem by downgrading xorg-x11-6.8.0-r4 to xorg-x11-6.8.0-r3. I know that xorg-x11-6.8.0-r4 has major changes in moving binaries and libraries from /usr/X11R6/ to /usr. I suspect the problems are somehow a result of that change. I found the problem. The issue is the rgb path. When I installed xorg-x11-6.8.0-r4, the rgb database was moved from /usr/X11R6/lib/X11/rgb to /usr/lib/rgb. Apparently both vnc and tightvnc are looking for the database in the old location. When I reinstalled xorg-6.8.0-r3, the file was moved back to its original location. For now my workaround is to install a symbolic link in /usr/X11R6/lib/X11 I see a couple of bugs here that were exposed as the result of installing xorg-x11-6.8.0-r4: 1. Window Maker segmentation faults if it is unable to allocate colors 2. vnc/tightvnc apparently hardcode the rgb database path as I see no documented option to change it. I'd guess it gets the RgbPath from whatever it's set to in xorg.conf. Incidentally, this shouldn't be a problem with current -r4 for a couple of reasons -- the location it's installed to has changed, and is symlinked properly now. Also, not sure whether raker's active anymore. Reassigning to last windowmaker bumper. If he's not, please update metadata.xml. Yup, I'm the windowmaker ebuild maintainer these days. Would this be more appropriate as a vnc or xorg bug? If WindowMaker can't allocate colors, then the current X setup is misconfigured (though WindowMaker should likely politely bail out somehow, rather than segfault). I'll take a look at this, to see if I can help WindowMaker not explode on error. Not sure what else I can do; may have to punt this to the vnc ebuild maintainer after I'm done. Looks like there's not much I can do atm -- xorg-0.6.8 series is pretty much unstable for ppc atm (my dev box is ppc). However, looks like the WindowMaker automake files could use some love too. Leaving this bug as is for now. If you feel up to compiling X + Mesa from CVS, things should work. Else, I'm hoping the new mesa gets merged in for 6.8.2 so ppc works properly. Would it help to know that Window Maker does the same thing under xorg-X11-6.7.0 if the RgbPath doesn't point to the correct database? Well here's the thing: <snip: windowmaker sources> WINGs/Makefile.in:520: $(COMPILE) -c -DRGBTXT="\"@X_LIBRARY_PATH@/X11/rgb.txt\"" $< </snip> So, assuming the X_LIBRARY_PATH from WindowMaker's configure works when X libraries aren't in the "classic" location (but the "more correct" /usr/lib), then if WindowMaker builds against X in that fashion, WindowMaker shouldn't crash. I'd be curious to know if WindowMaker builds against that X, and if it starts correctly then afterwards. I would suggest creating a temporary user and running "wmaker.isnt" in that users's home directory, and trying to start X. WM's config files are quite good at breaking things when stuff moves out from behind them. Also, The RgbPath option in XF86Config / xorg.conf is optional (AFAIK), so explicitly misconfiguring X isn't really a bug. I would definitely try rebuilding WindowMaker and seeing if it even works (I would hope things still compile if the X libraries moved into the "more correct" locations, but I honestly, can't say without testing). I will also look into backing up my current X and testing out 6.8.2-cvs to see if I can get things working on ppc, so I can test further, but this will likely take time. Armando: A week ago, I submitted 3 bug reports for windowmaker which have also been wrongly assigned to raker. There are a few others around too. Oh -- I just read this post from the 14th -- I'll look into the mis-assigned bugs as reassign them to myself soon. any news on this ? Reopen if you still have the same issue. If I break my rgbpath setting, windowmaker-0.92.0-r2 errors with the Fatal Error dialog box as described. Personally, I view this as a low priority bug since in order to cause the error, X has to be misconfigured. However, from a user perspective, it is difficult to track down the source of the error due to the fact that X appears to be working correctly even with the RgbPath setting misconfigured. Paul i don't understand... what do you need us to do ? Marking as wontfix since the error is always caused by a misconfiguration of X. If anyone gets this error, they need to double check that RgbPath is set correctly. |