| View previous topic :: View next topic |
| Author |
Message |
irony
Tux's lil' helper
Joined: 10 Jul 2002
Posts: 129
Location: CT
|
 Posted: Tue Nov 05, 2002 12:26 am Post subject: Fluxbox backgrounds and Eterm Error |
 |
|
I've tried adding the suggested theme override file to the init file in my ~/.fluxbox directory, but aftermodifying the file, it reorders things, putting the command to change the background above the command to set the theme, resulting in no background. Any way around this?
I'm also getting an odd permission error with Eterm, I suspect that it's symptomatic of a larger problem, as I got similar errors with bsetbg. Transperancy doesn't work, and whenever I open a new Eterm, I get the following messages:
| Code: |
Eterm: Error: Unable to create unique temporary file for "cat pixmaps.list" -- Permission denied
Eterm: Error: Parse error in file theme.cfg, line 54: Missing filename
Eterm: Warning: ASSERT failed in parse_image() at options.c:1885: state != NULL
Eterm: Warning: ASSERT failed in parse_image at options.c:1885: state != NULL
|
Any help is appreciated...
_________________
"and if rain brings winds of change, let it rain on us forever..." |
|
| Back to top |
|
 |
reves
Apprentice
Joined: 25 Jun 2002
Posts: 215
Location: South Florida
|
| Posted: Tue Nov 05, 2002 2:16 am Post subject: |
|
|
| Quote: | | I've tried adding the suggested theme override file to the init file in my ~/.fluxbox directory, but aftermodifying the file, it reorders things, putting the command to change the background above the command to set the theme, resulting in no background. Any way around this? |
I don't believe the order should affect it. The rootCommand should override the theme setting. I had problems with that command when I was using selectwm. If I started Fluxbox through the .xinitrc file it would set the background correctly but if I started it through selectwm it would use the theme's background. I never did figure that one out. Perhaps it's related to the errors you are getting with bsetbg and Eterm. Do you have write access to the tmp folder?
_________________
Robert |
|
| Back to top |
|
|
irony
Tux's lil' helper
Joined: 10 Jul 2002
Posts: 129
Location: CT
|
| Posted: Tue Nov 05, 2002 4:44 am Post subject: |
|
|
the command:
| Code: | | session.screen0.rootcommand: Esetroot -c /path/to/image |
is above
| Code: | | session.styleFile: /path/to/style |
which contains the line
| Code: | | rootCommand: bsetbg -solid #color |
Hence the rootcommand is being reset by the theme. I've solved that problem by commenting out the rootcommand in the theme file, but it remains that the fix suggested on the fluxbox site won't work for the above reason.
As to the second problem, no, it seems that only root has access to /tmp. Should I change this? Should I allow write access to everyone? To just a select group?
Thanks again for any help.
_________________
"and if rain brings winds of change, let it rain on us forever..." |
|
| Back to top |
|
|
irony
Tux's lil' helper
Joined: 10 Jul 2002
Posts: 129
Location: CT
|
| Posted: Tue Nov 05, 2002 5:07 am Post subject: I take that back... |
|
|
It seemed to have fixed the problem by commenting it out of theme, when in reality it just sets no background when I startx again.
_________________
"and if rain brings winds of change, let it rain on us forever..." |
|
| Back to top |
|
|
charlieg
Advocate
Joined: 30 Jul 2002
Posts: 2149
Location: Manchester UK
|
| Posted: Tue Nov 05, 2002 11:56 am Post subject: Me too! |
|
|
I too suffered from this error. But I use Gnome2 mostly so I haven't tried to fix it yet.
_________________
Want Free games?
Free Gamer - open source games list & commentary
Open source web-enabled rich UI platform: Vexi |
|
| Back to top |
|
|
reves
Apprentice
Joined: 25 Jun 2002
Posts: 215
Location: South Florida
|
| Posted: Tue Nov 05, 2002 9:11 pm Post subject: |
|
|
| Quote: | | As to the second problem, no, it seems that only root has access to /tmp. Should I change this? Should I allow write access to everyone? To just a select group? |
Everyone should have access to the /tmp directory. Run to do this. This will mean that everyone can write to the tmp folder but can only modify/delete files they own, not other user's files.[/code]
_________________
Robert |
|
| Back to top |
|
|
irony
Tux's lil' helper
Joined: 10 Jul 2002
Posts: 129
Location: CT
|
| Posted: Wed Nov 06, 2002 4:12 am Post subject: |
|
|
Adding write to /tmp solved the Eterm problem, but now I'm getting a different message.
| Code: | | Eterm: Error: Unable to locate desktop window. If you are running Enlighenment, please restart. If not, please set your background image with Esetroot, then try again. |
The background problem persists, though Eterm seems to be setting its background fine (at least in the initial random configuration).
The /tmp permissions change allows me to place the Esetroot command in a modified style configuration file which fixes the background problem, at least temporarily.
Thanks for all the help.
_________________
"and if rain brings winds of change, let it rain on us forever..." |
|
| Back to top |
|
|
|
Desktop Environments
