[SOLVED] xfce4-powermanager-svn/kdemod-powermanager!

Hello dear Archers! - Sorry for my bad English!
I have some problem with Arch x86_64 - 2.6.28-ARCH + xfce4-svn on a Toshiba laptop (dual core/4 gb ram/video intel GMA):
1. Xfce4-powermanager-svn wich don't change display brightness/change cpufreq policy when I plug/unplug AC cable.
Same problem with kdemod4+powerdevil and gnome-powermanager.
I have installed acpid; cpufrequtils; laptop-mode-tools; pm-utils -
In rc.conf i have: MODULES=(acpi-cpufreq cpufreq_ondemand cpufreq_powersave cpufreq_userspace etc) DAEMONS=(syslog-ng hal laptop-mode wicd gdm)
I can.t modprobe toshiba_acpi modules
FATAL: Error inserting toshiba_acpi (/lib/modules/2.6.28-ARCH/kernel/drivers/acpi/toshiba_acpi.ko): No such device
-Xfce4-powermanager-svn is notify me about power state/change: charging/discharging/fully charged etc., kdemod-powermanager doesn't.
2. When I "suspend", I got a black screen, but I don't know how to wake up again my laptop.
my pm-suspend.log
Initial commandline parameters: --quirk-s3-bios
--quirk-s3-mode
Wed Jan 28 23:23:16 EET 2009: Running hooks for hibernate.
/usr/lib/pm-utils/sleep.d/00auto-quirk hibernate hibernate: success.
/usr/lib/pm-utils/sleep.d/00logging hibernate hibernate: Linux toshiba 2.6.28-ARCH #1 SMP PREEMPT Sun Jan 25 09:43:53 UTC 2009 x86_64 Intel(R) Pentium(R) Dual CPU T3200 @ 2.00GHz GenuineIntel GNU/Linux
Module Size Used by
i915 67208 2
drm 108768 3 i915
arc4 4096 2
ecb 5248 2
joydev 14208 0
rtl8187 47232 0
mac80211 183088 1 rtl8187
eeprom_93cx6 4352 1 rtl8187
cfg80211 36896 2 rtl8187,mac80211
uvcvideo 62344 0
compat_ioctl32 11520 1 uvcvideo
videodev 37888 2 uvcvideo,compat_ioctl32
v4l1_compat 17284 2 uvcvideo,videodev
uhci_hcd 27552 0
ehci_hcd 41356 0
i2c_i801 12444 0
psmouse 57116 0
sg 31840 0
rfkill 13904 0
snd_pcsp 13052 1
iTCO_wdt 15184 0
video 22164 0
output 5248 1 video
i2c_core 26144 1 i2c_i801
serio_raw 8196 0
iTCO_vendor_support 5636 1 iTCO_wdt
intel_agp 32880 1
usbcore 160560 5 rtl8187,uvcvideo,uhci_hcd,ehci_hcd
input_polldev 6032 0
evdev 13984 10
thermal 20896 0
fan 7304 0
button 9504 0
battery 14600 0
ac 7176 0
snd_seq_oss 35584 0
snd_seq_midi_event 9344 1 snd_seq_oss
snd_seq 58336 4 snd_seq_oss,snd_seq_midi_event
snd_seq_device 9364 2 snd_seq_oss,snd_seq
snd_hda_intel 531124 4
snd_hwdep 10632 1 snd_hda_intel
snd_pcm_oss 45440 0
snd_pcm 82952 4 snd_pcsp,snd_hda_intel,snd_pcm_oss
snd_timer 24720 3 snd_seq,snd_pcm
snd_page_alloc 11792 2 snd_hda_intel,snd_pcm
snd_mixer_oss 18944 1 snd_pcm_oss
snd 65096 18 snd_pcsp,snd_seq_oss,snd_seq,snd_seq_device,snd_hda_intel,snd_hwdep,snd_pcm_oss,snd_pcm,snd_timer,snd_mixer_oss
soundcore 9632 1 snd
r8169 39428 0
mii 7296 1 r8169
cpufreq_userspace 5892 0
cpufreq_powersave 3840 0
cpufreq_ondemand 10512 1
acpi_cpufreq 10896 1
freq_table 6272 2 cpufreq_ondemand,acpi_cpufreq
processor 46776 4 thermal,acpi_cpufreq
rtc_cmos 14040 0
rtc_core 21060 1 rtc_cmos
rtc_lib 4992 1 rtc_core
jfs 182096 2
sr_mod 18884 0
cdrom 39080 1 sr_mod
sd_mod 29096 3
ahci 36876 2
libata 176352 1 ahci
scsi_mod 119256 4 sg,sr_mod,sd_mod,libata
total used free shared buffers cached
Mem: 3909868 389220 3520648 0 700 149400
-/+ buffers/cache: 239120 3670748
Swap: 0 0 0
success.
/usr/lib/pm-utils/sleep.d/00powersave hibernate hibernate: success.
/usr/lib/pm-utils/sleep.d/01grub hibernate hibernate: not applicable.
/usr/lib/pm-utils/sleep.d/11netcfg hibernate hibernate: success.
/usr/lib/pm-utils/sleep.d/49bluetooth hibernate hibernate: not applicable.
/etc/pm/sleep.d/50-hdparm_pm hibernate hibernate: not executable.
/usr/lib/pm-utils/sleep.d/55NetworkManager hibernate hibernate: success.
/usr/lib/pm-utils/sleep.d/55wicd hibernate hibernate: success.
/usr/lib/pm-utils/sleep.d/75modules hibernate hibernate: not applicable.
/usr/lib/pm-utils/sleep.d/90chvt hibernate hibernate: success.
/usr/lib/pm-utils/sleep.d/90clock hibernate hibernate: not applicable.
/usr/lib/pm-utils/sleep.d/94cpufreq hibernate hibernate: success.
/usr/lib/pm-utils/sleep.d/95led hibernate hibernate: not applicable.
/usr/lib/pm-utils/sleep.d/98smart-kernel-video hibernate hibernate: success.
/usr/lib/pm-utils/sleep.d/99video hibernate hibernate: success.
Wed Jan 28 23:23:49 EET 2009: performing hibernate
Thanks!
Last edited by mits (2009-06-11 17:43:01)

I taught if I go in suspend to ram mode, my laptop will wake up in same mode without turning of/restart.
Correct
Actualy I don't know how suspend to ram act.
The current state is saved to your RAM, when you wake up your system that state will come up again. What is Suspend to Ram
When I suspend my system screen goes black (as if it is powered of) and the powerbutton blinks. When I push the powerbutton again, my system wakes up and returns to the state before the suspend. I don't know this for sure, but in my opinion this is general for all systems.
Last edited by NeoXP (2009-01-29 15:55:12)

Similar Messages

[solved] xfce4-mailwatch-plugin svn not able to compile

After todays update my xfce4-mailwatch-plugin stopped working. I am using the svn version and trying to compile it again gives:
checking command to parse /usr/bin/nm -B output from gcc object... ok
checking for dlfcn.h... yes
checking for objdir... .libs
checking if gcc supports -fno-rtti -fno-exceptions... no
checking for gcc option to produce PIC... -fPIC -DPIC
checking if gcc PIC flag -fPIC -DPIC works... yes
checking if gcc static flag -static works... yes
checking if gcc supports -c -o file.o... yes
checking if gcc supports -c -o file.o... (cached) yes
checking whether the gcc linker (/usr/bin/ld -m elf_x86_64) supports shared libraries... yes
checking whether -lc should be explicitly linked in... no
checking dynamic linker characteristics... GNU/Linux ld.so
checking how to hardcode library paths into programs... immediate
checking whether stripping libraries is possible... yes
checking if libtool supports shared libraries... yes
checking whether to build shared libraries... yes
checking whether to build static libraries... yes
checking for intltool >= 0.31... 0.40.3 found
checking for intltool-update... /usr/bin/intltool-update
checking for intltool-merge... /usr/bin/intltool-merge
checking for intltool-extract... /usr/bin/intltool-extract
checking for xgettext... /usr/bin/xgettext
checking for msgmerge... /usr/bin/msgmerge
checking for msgfmt... /usr/bin/msgfmt
configure: error: GNU gettext tools not found; required for intltool
gettext is installed though - what is going on here?
Last edited by mykey (2008-08-16 06:49:28)

bump
The before mentioned app is not the only one that does not build properly - I tried gnubiff and audio-convert-mod with just the same error message
configure: error: GNU gettext tools not found; required for intltool
What can I do? Would filing a bug-report help?

[Solved] Xfce4 crashing at start

Hi, I did recently install Xfce4-svn from the unstable repos, and it worked, initially. The second time i tried to log in to the Xfce-session, it instantly kicked me out to the GDM, and it has done this ever since. I've tried uninstalling/reinstalling Xfce, and searching the forum, but haven't succeded on getting rid of this.
Any tips on how i might solve this?
EDIT: If someone knows the locations of any logfiles that might connected to this, that might help as well.
Thanks

I had a similar problem a few weeks back. Since I installed my own cursor theme, I altered the default index.theme file and stopped it from being upgraded in <code>/etc/pacman.conf</code>:
NoUpgrade = usr/X11R6/lib/X11/icons/default/index.theme
I ran across the problem of Xfce instantly kicking me out when I tried to change the icon theme to default and it obviously didn't find what it was expecting. From then on, I couldn't log into X at all...it would kick me out as soon as Xfce had loaded. To solve the problem, I had to edit <code>~/.config/xfce4/mcs_settings/gtk.xml</code> and change the <code>Net/IconThemeName</code> back to a different icon theme. Hopefully that helps if someone else runs across the same thing. :oops:

[Solved] xfce4+compiz: conky can only been seen if I miminzed windows?

I have xfce4 and compiz-xfce4 installed with my Arch Linux?
I added conky in my auto start-up setting. It turns out conky can only be seen if I minimize all windows.
When I clicked the "show desktop" button in my xfce4-pannel, conky just cannot show up.
Thanks,
(pls kindly see my another question about xfce4+compiz as well: https://bbs.archlinux.org/viewtopic.php?id=177106)
Last edited by hellolj (2014-02-13 23:12:16)

Solved
It turns out I have to uncheck the "Hide Skip Taskbar Windows" option under "General Options" in Compiz configuration settings manager.

[solved] Xfce4 unwanted autostarting programs

I have developed a small irritation with what i believe to be Xfce4. Upon every reboot (or cold start) of my machine. When i log into Xfce4, Chromium and a Terminal window both autostart. Chromium starts minimised and the terminal starts visable in the centre of my screen. Some information that may be relevant: Xfce 4.10, Xfwm4, Kernel 3.8.11-1-ARCH, SLiM, Xorg server 1.14.1.
I am not aware of making any changes this problem appeared out of the blue. I have checked the Session and Startup settings and the only autostart programs enabled are Power Manager and Xfsettingsd. I have checked in .config/xfce4 for an autostart folder and there isnt one. There is nothing in .xinitrc
Any help on this would be great thank you.
Last edited by thekore (2013-05-05 17:33:54)

Krarl wrote:Try enabling "Automatically save session on logout" in session and startup and then close all windows. Restart xfce. Hopefully this should clear the saved session, and now you can disable it again.
I feel like such an idiot, I was looking for the most complex solution and forgot about the most obvious. This has solved the problem, thanks Krarl
ewaller wrote:You might also try cleaning out ~/,config/xfce4-sessions
I had checked this already and the folder was empty.

[solved] xfce4-terminal spam after update to util-linux 2.25-3

I use the setterm command inside a file in /etc/profile.d so that I can prevent the screen from blanking when using a console, along with a couple of other things.
After the latest update to util-linux (2.25-3), whenever I open xfce4-terminal these lines show up:
setterm: terminal xterm does not support --blength
setterm: terminal xterm does not support --bfreq
setterm: terminal xterm does not support --blank
[gilmoreja@JamesPC ~]$
Is there a better way to handle making sure setterm runs when a console is used, but not necessarily when a terminal is opened? Or is there some other way to solve this issue? There doesn't seem to be a switch for setterm for any kind of "quiet mode."
Last edited by gilmoreja (2014-08-06 18:36:28)

I think that the shell started in a console is a login shell, and it is not the case in a graphical terminal.
A login shell has a '-' at the start of $0; so you can test that and condition the execution of the setterm commands:
if [[ $0 == '-bash' ]]; then
setterm ...
setterm ...
fi

[SOLVED] xfce4 / Thunar problems moving files between folders

In XFCE4 I open THUNAR file manager, I am browsing DOCUMENTS. If I move one file from DOCUMENTS, to ../PICTURES (by dragging it),
it will move it. However, when I now browse PICTURES, I don't see the file I moved. Unless I click the REFRESH Icon in Thunar.
This started happening with very recent updates.
[UPDATE:] Solved after upgrading thunar (1.6.6-2 -> 1.6.7-1)
Last edited by Kilzool (2015-04-21 11:16:50)

You should report this at the upstream bug tracker. The Xfce developers are likely not reading this forum.
I could reproduce this bug with these steps:
1. Open two Thunar windows (Documents and Pictures folder)
2. Move a file from one folder to the other by using drag'n'drop
The result is that the file is moved but it is still shown in Thunar until a manual refresh.
EDIT: This is already fixed by this commit so Thunar 1.6.7 should work fine.
Last edited by Radioactiveman (2015-03-23 13:46:53)

[solved] xfce4, fails to install....

Trying to: pacman -S xfce4
Proceed with upgrade? [Y/n] y
checking package integrity... done.
loading package data... done.
checking for file conflicts...
error: the following file conflicts were found:
opt/xfce4/bin/xfce4-iconbox: exists in "xfce4-panel" (target) and "xfce4-iconbox" (target)
opt/xfce4/share/icons/hicolor/48x48/apps/xfce4-iconbox.png: exists in "xfce4-panel" (target) and "xfce4-iconbox" (target)
opt/xfce4/lib/xfce4/panel-plugins/libsystray.so: exists in "xfce4-panel" (target) and "xfce4-systray" (target)
opt/xfce4/bin/xfce4-tips: exists in "xfce4-session" (target) and "xfce4-toys" (target)
opt/xfce4/share/xfce4/tips/tips: exists in "xfce4-session" (target) and "xfce4-toys" (target)
opt/xfce4/share/xfce4/tips/tips.dat: exists in "xfce4-session" (target) and "xfce4-toys" (target)
errors occurred, no packages were upgraded.
How can i reslove this?

I assume you're trying to install from the testing repo.
I bypassed the conflicts with:
pacman -Sf xfce4
Everything seemed to work fine except for the systray, though I presume that's unrelated to these errors (haven't checked if this is a reported bug yet). Unfortunately with xfce-svn broken, the rc2 in testing not having a working systray, and the version from extra being a bit dated I have been missing out on Xfce so far.

[SOLVED] Xfce4 Lock after suspend

Hello everyone,
I know that there was it already asked, but in my question is something different. Is there any option to lock screen with LightDM in Xfce4 when is system going to suspend ? I already edited /usr/bin/xflock4 and it locks screen when is executed from terminal or simply locked from xfce panel, but it doesn't lock screen when i suspend computer. In power manager and in session settings is option already ticked to lock the screen after suspend.
PS: I know that "dm-tool lock" doesn't really lock the screen only redirect you to tty2.
EDIT: Now it works so here is solution:
1. Install light-locker
pacman -S light-locker
2. Create systemd service
nano /etc/systemd/system/lock.service
[Unit]
Description=Lock X session
Before=suspend.target
[Service]
Type=oneshot
ExecStart=/usr/bin/xflock4
[Install]
WantedBy=suspend.target
3. Enable systemd service
systemctl enable lock
4. Add light-locker to xflock4 script
nano /usr/bin/xflock4
#!/bin/sh
light-locker-command -l
Last edited by mako2580 (2014-05-07 16:46:26)

You should place [SOLVED] in the Title.

[Solved] Xfce4.8: App shortcuts not working after update

Hello,
since pacman upgraded my Xfce to 4.8, my application shortcuts are no longer working. I especially need them to emulate a third button with Super_L and bind the netbook function keys for audio volume/muting to amixer calls. I already tried to rebind all shortcuts, but that didn't help. Any ideas?
Edit: I already tried https://wiki.archlinux.org/index.php/Xf … 7t_working, but this didn't help
Edit2: Solved it. Apparently I lost xfce4-settings-helper during the migration from 4.6. So I restarted it manually and then saved my session.
Jan
Last edited by Slowhand_47 (2011-01-23 09:27:00)

I am not bothering with windows 10 my friend, it is too much of an newbe baby at the moment and there are just too many bug fixes need doing in my opinion. I did manage to get my dolby home theatre to work again in windows 10, but it was an awful dulled down version with only half the features of the original that came with the version that was on my pc. My plan is to stick to windows 8.1 until it's death. When they withdrawl all the security patches for windows 8.1 and it becomes obsolete, then I will be forced to trash my pc again and go to windows 10, was not much fun mind spending 3.5 days putting everything back to its former state. Hope they do make windows 10 more stable and fix a lot of the bugs. I tried opening videos and pictures in windows 10.... result = missing element errors.... and error, error, error,,, So I think I will wait until 28 July 16 to when the last day of my free upgrade and reservation to windows 10 becomes mandatory. (This is I day before my year to upgrade expires). Thanks for your post. Will

(SOLVED) xfce4-appfinder Segmentation fault

Hi all,
I just discovered yesterday that xfce4-appfinder ins't working on my desktop (it works fine on my laptop though). Running it from xfce it just does nothing but if I run it from the terminal I just get this message: Segmentation fault.
I'm pretty sure it worked like two months ago. I installed some apps and did some upgrades from that time on. Already tried to downgrade xfce4-appfinder to the previous version but I still got the same error.
Does anyone have/had this problem?
Thanks in advance.
Last edited by harroxelas (2012-05-01 10:09:53)

Please mark your thread title as [solved] to avoid confusion .

[SOLVED] xfce4-panel/workspace with compiz/xfwm4

Its the weird problem:
in compiz (ccsm/general option Desktop Size)
* Horizontal Virtual Size = 4
* Vertical Virtual Size = 1
* Number of Desktops =1
in xfce (setting/workspace)
* No of Workspace=1
# Problem 1
It seem `xfce's no workspace` == `compiz's no of Desktop` is hard linked
compiz ==> xfce4 : no of workspace changes from 1 to 4
xfce4 ==> compiz : no of workspace changes from 4 to 1
# Problem 2
if you change compiz's
* Number of Desktops = 4
The Problem 1 is solved BUT
.. xfce4-panel starts acting weird!
showing all the workspace windows in one panel
Last edited by rhoit (2013-01-18 16:34:13)

GOT # reply form IRC
(10:13:36 PM) soreau:
Number of Desktops should always be one. Compiz is unique from other window managers in that it uses (GL) viewports instead of desktops. (multiple desktop functionality was never actually implemented). Most DE components only support desktops, not viewports, even though it's part of the EWMH spec.

[solved] xfce4-panel 4.8.0-1 only on one desktop

Hello,
xfce4-panel got updated today to version 4.8.0-1. Now I have the problem, that the panel appears only on the desktop it was started, but does not remain sticky as expected. I'm using plain openbox without xfce stuff. I also removed the old configs, same problem.
Any hints?
Vlad
PS: Set the openbox internal application settings to sticky in rc.xml:
<application name="xfce4-panel">
<desktop>all</desktop>
</application>
Now it appears on all desktops, but it should work without this. It's definitely a bug...
Last edited by DonVla (2011-01-19 13:22:55)

I figured out a way of solving this one .
It seems that the problem dissappears once you run xfwm4, even if you run openbox --replace afterwards
To fix it, I edited the file /etc/xdg/xfce4/xfconf/xfce-perchannel-xml/xfce4-session.xml
My old xfce4-sessions.xml:
<?xml version="1.0" encoding="UTF-8"?>
<channel name="xfce4-session" version="1.0">
<property name="general" type="empty">
<property name="FailsafeSessionName" type="string" value="Failsafe"/>
</property>
<property name="sessions" type="empty">
<property name="Failsafe" type="empty">
<property name="IsFailsafe" type="bool" value="true"/>
<property name="Count" type="int" value="5"/>
<property name="Client0_Command" type="array">
<value type="string" value="openbox"/>
</property>
<property name="Client0_PerScreen" type="bool" value="false"/>
<property name="Client1_Command" type="array">
<value type="string" value="xfce4-panel"/>
</property>
<property name="Client1_PerScreen" type="bool" value="false"/>
<property name="Client2_Command" type="array">
<value type="string" value="Thunar"/>
<value type="string" value="--daemon"/>
</property>
<property name="Client2_PerScreen" type="bool" value="false"/>
<property name="Client3_Command" type="array">
<value type="string" value="xfdesktop"/>
</property>
<property name="Client3_PerScreen" type="bool" value="false"/>
<property name="Client4_Command" type="array">
<value type="string" value="xfce4-settings-helper"/>
</property>
<property name="Client4_PerScreen" type="bool" value="false"/>
</property>
</property>
<property name="splash" type="empty">
<property name="Engine" type="string" value=""/>
</property>
</channel>
My new one:
<?xml version="1.0" encoding="UTF-8"?>
<channel name="xfce4-session" version="1.0">
<property name="general" type="empty">
<property name="FailsafeSessionName" type="string" value="Failsafe"/>
</property>
<property name="sessions" type="empty">
<property name="Failsafe" type="empty">
<property name="IsFailsafe" type="bool" value="true"/>
<property name="Count" type="int" value="6"/>
<property name="Client0_Command" type="array">
<value type="string" value="xfwm4"/>
</property>
<property name="Client0_PerScreen" type="bool" value="false"/>
<property name="Client1_Command" type="array">
<value type="string" value="xfce4-panel"/>
</property>
<property name="Client1_PerScreen" type="bool" value="false"/>
<property name="Client2_Command" type="array">
<value type="string" value="Thunar"/>
<value type="string" value="--daemon"/>
</property>
<property name="Client2_PerScreen" type="bool" value="false"/>
<property name="Client3_Command" type="array">
<value type="string" value="xfdesktop"/>
</property>
<property name="Client3_PerScreen" type="bool" value="false"/>
<property name="Client4_Command" type="array">
<value type="string" value="xfce4-settings-helper"/>
</property>
<property name="Client4_PerScreen" type="bool" value="false"/>
<property name="Client5_Command" type="array">
<value type="string" value="openbox"/>
<value type="string" value="--replace"/>
</property>
<property name="Client5_PerScreen" type="bool" value="false"/>
</property>
</property>
<property name="splash" type="empty">
<property name="Engine" type="string" value=""/>
</property>
</channel>
What I did was change the window manager back to xfwm4 here:
<property name="Client0_Command" type="array">
<value type="string" value="xfwm4"/>
</property>
Then make openbox --replace run after that (to kill xfwm and start openbox) by adding this:
<property name="Client5_Command" type="array">
<value type="string" value="openbox"/>
<value type="string" value="--replace"/>
</property>
<property name="Client5_PerScreen" type="bool" value="false"/>
And lastly, make xfce recognize that last entry by changing this:
<property name="Count" type="int" value="5"/>
for this:
<property name="Count" type="int" value="6"/>
Relog after that and there you go
Last edited by Ideka (2011-01-19 02:54:24)

[SOLVED] XFCE4 Will Not Open When Logged On as Regular User

Please excuse me if I am being a noob, but I only installed ArchLinux yesterday. Whenever I run
startxfce4
as a regular user, the screen goes dark, flashes the Nvidia logo, then exits to a dialog box that reads:
Unable to load a failsafe session Unable to determine failsafe session name. Possible causes: xfconfd isn't running (D-bus setup problem); environment variable $XDG_CONFIG_DIRS is set incorrectly (msut include "/etc"), or xfce4-session is installed incorrectly."
When I check the output after I click "Quit" on the dialog box, the output at the end reads
gpg-agent[1538]:error creating '/home/mordecai/.cache/gpg-agent-info' : Permission denied (xfce4-session:1515): Pango-WARNING **:error opening config file '/home/mordecai/.config/pango/pangorc' : Permission denied
However, when I run
startxfce4
logged on as root, everything opens fine. Thanks for any help and/or pointers.
Last edited by mordecaifeilbach (2012-11-03 21:51:33)

Also, when I try to start xfconfd it gives me this:
$ /usr/lib/xfce4/xfconf/xfconfd
(xfconfd:20910: xfconfd-CRITICAL **: Xfconfd failed to start: Unable to autolaunch a dbus-daemon without a $DISPLAY for X11
I also checked the environment variable $XDG-CONFIG-DIRS and it is set correctly, and the xfce4-session installation did not return any error messages.

[SOLVED]Xfce4/Xorg - Fonts messed up

Hey
Beside dwm I'm actually trying out if Xfce4 fits for my needs so I installed it using 'pacman -S xfce4 xfce4-goodies'. I'm already used to it since my time with Debian so I like this DE pretty much.
Everything installed just fine and apparently works, but the fonts are really ugly.
I tried to change them in the Settings-Manager and in Xfce4-Terminal/Mousepad, but I can choose one font or another, they're all the same. There's no difference between Monospace, Newspaper, Sans, Serif, Clean, ClearlyPUA etc.. They all have the same style, same size and same uglyness.
What works is, that I can change the size of these fonts and I can select other fonts, but beside the size everything stays unchanged.
# File generated by xorgconfig.
# Copyright 2004 The X.Org Foundation
# Permission is hereby granted, free of charge, to any person obtaining a
# copy of this software and associated documentation files (the "Software"),
# to deal in the Software without restriction, including without limitation
# the rights to use, copy, modify, merge, publish, distribute, sublicense,
# and/or sell copies of the Software, and to permit persons to whom the
# Software is furnished to do so, subject to the following conditions:
# The above copyright notice and this permission notice shall be included in
# all copies or substantial portions of the Software.
# THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
# IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
# FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL
# The X.Org Foundation BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY,
# WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF
# OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
# SOFTWARE.
# Except as contained in this notice, the name of The X.Org Foundation shall
# not be used in advertising or otherwise to promote the sale, use or other
# dealings in this Software without prior written authorization from
# The X.Org Foundation.
# Refer to the xorg.conf(5) man page for details about the format of
# this file.
# Module section -- this section is used to specify
# which dynamically loadable modules to load.
Section "Module"
# This loads the DBE extension module.
Load "dbe" # Double buffer extension
# This loads the miscellaneous extensions module, and disables
# initialisation of the XFree86-DGA extension within that module.
SubSection "extmod"
Option "omit xfree86-dga" # don't initialise the DGA extension
EndSubSection
# This loads the font modules
# Load "type1"
Load "freetype"
# Load "xtt"
# This loads the GLX module
# Load "glx"
# This loads the DRI module
# Load "dri"
EndSection
# Files section. This allows default font and rgb paths to be set
Section "Files"
# The location of the RGB database. Note, this is the name of the
# file minus the extension (like ".txt" or ".db"). There is normally
# no need to change the default.
# RgbPath "/usr/share/X11/rgb"
# Multiple FontPath entries are allowed (which are concatenated together),
# as well as specifying multiple comma-separated entries in one FontPath
# command (or a combination of both methods)
FontPath "/usr/share/fonts/misc"
FontPath "/usr/share/fonts/100dpi:unscaled"
FontPath "/usr/share/fonts/75dpi:unscaled"
# FontPath "/usr/share/fonts/TTF"
# FontPath "/usr/share/fonts/Type1"
# FontPath "/usr/lib/X11/fonts/local/"
# FontPath "/usr/lib/X11/fonts/misc/"
# FontPath "/usr/lib/X11/fonts/75dpi/:unscaled"
# FontPath "/usr/lib/X11/fonts/100dpi/:unscaled"
# FontPath "/usr/lib/X11/fonts/Speedo/"
# FontPath "/usr/lib/X11/fonts/Type1/"
# FontPath "/usr/lib/X11/fonts/TrueType/"
# FontPath "/usr/lib/X11/fonts/freefont/"
# FontPath "/usr/lib/X11/fonts/75dpi/"
# FontPath "/usr/lib/X11/fonts/100dpi/"
# The module search path. The default path is shown here.
# ModulePath "/usr/lib/modules"
EndSection
# Server flags section.
Section "ServerFlags"
# Uncomment this to cause a core dump at the spot where a signal is
# received. This may leave the console in an unusable state, but may
# provide a better stack trace in the core dump to aid in debugging
# Option "NoTrapSignals"
# Uncomment this to disable the <Ctrl><Alt><Fn> VT switch sequence
# (where n is 1 through 12). This allows clients to receive these key
# events.
# Option "DontVTSwitch"
# Uncomment this to disable the <Ctrl><Alt><BS> server abort sequence
# This allows clients to receive this key event.
# Option "DontZap"
# Uncomment this to disable the <Ctrl><Alt><KP_+>/<KP_-> mode switching
# sequences. This allows clients to receive these key events.
# Option "Dont Zoom"
# Uncomment this to disable tuning with the xvidtune client. With
# it the client can still run and fetch card and monitor attributes,
# but it will not be allowed to change them. If it tries it will
# receive a protocol error.
# Option "DisableVidModeExtension"
# Uncomment this to enable the use of a non-local xvidtune client.
# Option "AllowNonLocalXvidtune"
# Uncomment this to disable dynamically modifying the input device
# (mouse and keyboard) settings.
# Option "DisableModInDev"
# Uncomment this to enable the use of a non-local client to
# change the keyboard or mouse settings (currently only xset).
# Option "AllowNonLocalModInDev"
EndSection
# Input devices
# Core keyboard's InputDevice section
Section "InputDevice"
Identifier "Keyboard1"
Driver "kbd"
# For most OSs the protocol can be omitted (it defaults to "Standard").
# When using XQUEUE (only for SVR3 and SVR4, but not Solaris),
# uncomment the following line.
# Option "Protocol" "Xqueue"
Option "AutoRepeat" "500 30"
# Specify which keyboard LEDs can be user-controlled (eg, with xset(1))
# Option "Xleds" "1 2 3"
# Option "LeftAlt" "Meta"
# Option "RightAlt" "ModeShift"
# To customise the XKB settings to suit your keyboard, modify the
# lines below (which are the defaults). For example, for a non-U.S.
# keyboard, you will probably want to use:
# Option "XkbModel" "pc105"
# If you have a US Microsoft Natural keyboard, you can use:
# Option "XkbModel" "microsoft"
# Then to change the language, change the Layout setting.
# For example, a german layout can be obtained with:
# Option "XkbLayout" "de"
# or:
# Option "XkbLayout" "de"
# Option "XkbVariant" "nodeadkeys"
# If you'd like to switch the positions of your capslock and
# control keys, use:
# Option "XkbOptions" "ctrl:swapcaps"
# These are the default XKB settings for Xorg
# Option "XkbRules" "xorg"
# Option "XkbModel" "pc105"
# Option "XkbLayout" "us"
# Option "XkbVariant" ""
# Option "XkbOptions" ""
# Option "XkbDisable"
Option "XkbRules" "xorg"
Option "XkbModel" "pc101"
Option "XkbLayout" "de"
EndSection
# Core Pointer's InputDevice section
Section "InputDevice"
# Identifier and driver
Identifier "Mouse1"
Driver "mouse"
Option "Protocol" "Auto" # Auto detect
Option "Device" "/dev/input/mice"
# When using XQUEUE, comment out the above two lines, and uncomment
# the following line.
# Option "Protocol" "Xqueue"
# Mouse-speed setting for PS/2 mouse.
# Option "Resolution" "256"
# Baudrate and SampleRate are only for some Logitech mice. In
# almost every case these lines should be omitted.
# Option "BaudRate" "9600"
# Option "SampleRate" "150"
# Mouse wheel mapping. Default is to map vertical wheel to buttons 4 & 5,
# horizontal wheel to buttons 6 & 7. Change if your mouse has more than
# 3 buttons and you need to map the wheel to different button ids to avoid
# conflicts.
Option "ZAxisMapping" "4 5 6 7"
# Emulate3Buttons is an option for 2-button mice
# Emulate3Timeout is the timeout in milliseconds (default is 50ms)
# Option "Emulate3Buttons"
# Option "Emulate3Timeout" "50"
# ChordMiddle is an option for some 3-button Logitech mice
# Option "ChordMiddle"
EndSection
# Other input device sections
# this is optional and is required only if you
# are using extended input devices. This is for example only. Refer
# to the xorg.conf man page for a description of the options.
# Section "InputDevice"
# Identifier "Mouse2"
# Driver "mouse"
# Option "Protocol" "MouseMan"
# Option "Device" "/dev/mouse2"
# EndSection
# Section "InputDevice"
# Identifier "spaceball"
# Driver "magellan"
# Option "Device" "/dev/cua0"
# EndSection
# Section "InputDevice"
# Identifier "spaceball2"
# Driver "spaceorb"
# Option "Device" "/dev/cua0"
# EndSection
# Section "InputDevice"
# Identifier "touchscreen0"
# Driver "microtouch"
# Option "Device" "/dev/ttyS0"
# Option "MinX" "1412"
# Option "MaxX" "15184"
# Option "MinY" "15372"
# Option "MaxY" "1230"
# Option "ScreenNumber" "0"
# Option "ReportingMode" "Scaled"
# Option "ButtonNumber" "1"
# Option "SendCoreEvents"
# EndSection
# Section "InputDevice"
# Identifier "touchscreen1"
# Driver "elo2300"
# Option "Device" "/dev/ttyS0"
# Option "MinX" "231"
# Option "MaxX" "3868"
# Option "MinY" "3858"
# Option "MaxY" "272"
# Option "ScreenNumber" "0"
# Option "ReportingMode" "Scaled"
# Option "ButtonThreshold" "17"
# Option "ButtonNumber" "1"
# Option "SendCoreEvents"
# EndSection
# Monitor section
# Any number of monitor sections may be present
Section "Monitor"
Identifier "My Monitor"
# HorizSync is in kHz unless units are specified.
# HorizSync may be a comma separated list of discrete values, or a
# comma separated list of ranges of values.
# NOTE: THE VALUES HERE ARE EXAMPLES ONLY. REFER TO YOUR MONITOR'S
# USER MANUAL FOR THE CORRECT NUMBERS.
HorizSync 31.5 - 57.0
# HorizSync 30-64 # multisync
# HorizSync 31.5, 35.2 # multiple fixed sync frequencies
# HorizSync 15-25, 30-50 # multiple ranges of sync frequencies
# VertRefresh is in Hz unless units are specified.
# VertRefresh may be a comma separated list of discrete values, or a
# comma separated list of ranges of values.
# NOTE: THE VALUES HERE ARE EXAMPLES ONLY. REFER TO YOUR MONITOR'S
# USER MANUAL FOR THE CORRECT NUMBERS.
VertRefresh 50-100
EndSection
# Graphics device section
# Any number of graphics device sections may be present
# Standard VGA Device:
Section "Device"
Identifier "Standard VGA"
VendorName "Unknown"
BoardName "Unknown"
# The chipset line is optional in most cases. It can be used to override
# the driver's chipset detection, and should not normally be specified.
# Chipset "generic"
# The Driver line must be present. When using run-time loadable driver
# modules, this line instructs the server to load the specified driver
# module. Even when not using loadable driver modules, this line
# indicates which driver should interpret the information in this section.
Driver "vga"
# The BusID line is used to specify which of possibly multiple devices
# this section is intended for. When this line isn't present, a device
# section can only match up with the primary video device. For PCI
# devices a line like the following could be used. This line should not
# normally be included unless there is more than one video device
# intalled.
# BusID "PCI:0:10:0"
# VideoRam 256
# Clocks 25.2 28.3
EndSection
# Device configured by xorgconfig:
Section "Device"
Identifier "* Generic VESA compatible"
Driver "vesa"
#VideoRam 262144
# Insert Clocks lines here if appropriate
EndSection
# Screen sections
# Any number of screen sections may be present. Each describes
# the configuration of a single screen. A single specific screen section
# may be specified from the X server command line with the "-screen"
# option.
Section "Screen"
Identifier "Screen 1"
Device "* Generic VESA compatible"
Monitor "My Monitor"
DefaultDepth 24
Subsection "Display"
Depth 8
Modes "1024x768" "800x600" "640x480"
ViewPort 0 0
EndSubsection
Subsection "Display"
Depth 16
Modes "1024x768" "800x600" "640x480"
ViewPort 0 0
EndSubsection
Subsection "Display"
Depth 24
Modes "1024x768" "800x600" "640x480"
ViewPort 0 0
EndSubsection
EndSection
# ServerLayout sections.
# Any number of ServerLayout sections may be present. Each describes
# the way multiple screens are organised. A specific ServerLayout
# section may be specified from the X server command line with the
# "-layout" option. In the absence of this, the first section is used.
# When now ServerLayout section is present, the first Screen section
# is used alone.
Section "ServerLayout"
# The Identifier line must be present
Identifier "Simple Layout"
# Each Screen line specifies a Screen section name, and optionally
# the relative position of other screens. The four names after
# primary screen name are the screens to the top, bottom, left and right
# of the primary screen. In this example, screen 2 is located to the
# right of screen 1.
Screen "Screen 1"
# Each InputDevice line specifies an InputDevice section name and
# optionally some options to specify the way the device is to be
# used. Those options include "CorePointer", "CoreKeyboard" and
# "SendCoreEvents".
InputDevice "Mouse1" "CorePointer"
InputDevice "Keyboard1" "CoreKeyboard"
EndSection
# Section "DRI"
# Mode 0666
# EndSection
$HOME/.xinitrc
exec xfce4-session
Last edited by azerty (2007-08-23 22:14:46)

Ok maybe it's a bit difficult to explain my problem.
Another try
I want Xfce' fonts to look like this
but currently it looks like this.
As I already know from my Xfce experiences with Debian, using a font like Monospace normally gives me a nice smooth font as in the first link/image. But currently I can chose Monospace or whatever, the font stays the same, even if I select Monospace the font stay as small and awkward as before. But as I said before Monospace should give me another font which, as stated above, would be very smooth.
Hopefully my problem is easier to understand know.
Thanks in advance.

[SOLVED] xfce4-powermanager-svn/kdemod-powermanager!

Similar Messages

Maybe you are looking for