Archive for the ‘Uncategorized’ Category.
Here’s what I did to fix auto-mounting, trash and authorization problems:
Install gvfs-afc (which added: gvfs, libsoup-gnome, libsoup, libproxy, gconf, orbit2, libcdio, libcddb, gnome-disk-utility, libunique, libgnome-keyring).
exec ck-launch-session dbus-launch openbox-session
dbus needs to be after consolekit to fix the authorization problems.
I installed Gnome-globalmenu. This litte gem acts like the top panel in OS X. So the menubar of the window that is active is showed in the top panel. But when you have a light colored panel, the white tekst is difficult to read.
Change the text color in Gnome-globalmenu:
GlobalMenu’s text is determined by your desktop theme. If you want to change it do the following:
- add this code to ~/.gtk-2.0
(note: ”~” is your home directory, and to be able to see .gtk-2.0 there you’ll need to press ctrl-h or select View -> Show Hidden Files)
fg[NORMAL] = "#000000"
widget_class "**" style "menu_item"
fg[NORMAL] = "#FFFFFF"
widget_class "**" style "menubar"
#FFFFFF is white, and is the colour that will be used for ”File Edit View…”
#000000 is black, and is what will be used in the drop down menus, eg. ”New Open Close Save…”
Change the colours to whatever you want. Just use 6 characters, where each character is one of ”0123456789ABCDEF”
The first pair of characters is for red, the second for green, and the third for blue.
Note: this will also change the menu clour in Firefox (which is not compatible with GlobalMenu) so you may want to change your firefox theme to suit (Tools -> Addons -> Themes in Firefox)
Thanks to Ayoli http://ubuntuforums.org/member.php?u=122327
for showing me how to do this
If anyone finds this helpful please thank him, not me.
I did a fresh install of Arch. Then installed several windowmanagers / DE’s. But it didnt’ matter which I choose, everytime I tried to mount a external storage device i.e. USB drive, hardrive, MMC card that horrible error popped up: Error mounting the device: Not authorized….
After hours digging in the forums I found the solution:
First, remove your “dbus-launch” and “ck-launch-session” calls in your .xinitrc. Then, in /etc/slim.conf, change “login_cmd” to this:
“login_cmd exec ck-launch-session /bin/bash -login ~/.xinitrc %session”
This circumvents the need for dbus-launch, and also makes sure that everything in .xinitrc is automatically in a ConsoleKit session. This is documented here. (https://wiki.archlinux.org/index.php/Slim#PolicyKit)
Install udisk and udiskie:
#yaourt -S udisk
#yaourt -S udiskie
A lot off times reading the forums, it get’s mentioned…. add [xxxx] to your daemons. Huh… daemons, what’s that?
Daemons are programs that are started and run in the background after you (re)boot your machine.
Where do i find daemons?
Edit the file “rc.conf” located in /etc :
# sudo nano /etc/rc.conf
Well, be gentile here with me please…This is my first post ever on a blog
I recently started out using Arch Linux. Coming from Ubuntu I have some experience with the CLS but not that much. Reasons for using Arch for me are speed, flexibility, VERY well documented, good forums, and it runs very smooth on my old Dell C640 laptop.
I’ll be sharing my experiences here, as I hope to make some progress during my time using Arch.
Specs of the machinery are…:
Pentium IV 2.0 Mhz (wooohooo!)
512 MB RAM DDRI
1024 * 768 screen
1 USB I port