SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
mmm..
I was trying something else before I read this last post and I found that disabling the messagebus daemon the result is similar: thunar finally works but no automount..
That's expected behavior without messagebus or gdu running.
gdu is what Xfce uses to monitor volumes.
Messagebus is the d-bus monitor. Notifies of system events (plugging of USB devices for example).
You can also disable the side pane in Thunar with CTRL-B. That should speed up loading.
I do wonder what is causing the slow loading for people. Do you have a properly formatted ~/.gtk-bookmarks?
Currently, there are 3 local SATA hard drives (8 partitions), a single SD flash card plugged into my multi-reader, and a usb flash drive plugged in. There is a 2 second delay in launching Thunar cold. Warm launches are instant.
Does Gnome Disk Utility work as expected? System -> Disk Utility.
--edit--
Grabbing at sticks
Are you using fstab entries for non-persistent (hotplugged) devices? Try commented those out. My fstab only has entries for permently mounted devices. I allow the necessary tools to handle removable devices
Last edited by disturbed1; 06-02-2011 at 05:04 PM.
Click here to see the post LQ members have rated as the most helpful post in this thread.
Mon Jan 31 05:31:20 UTC 2011
Rebuilt xfce (BUILD=3_rlw)
Included latest point releases of several components
Upgraded Terminal to 0.4.6
Removed mousepad
this is broken (no print function) and unmaintained for 4.8
I switched a long time ago to leafpad because mousepad had lots of bugs related to find and find & replace.
Distribution: Slackware64-current with "True Multilib" and KDE4Town.
Posts: 9,101
Rep:
Quote:
Originally Posted by rmjohnso
I'm glad you didn't have any damage and that you and your family are ok.
So I was doing some more researching of this mixer problem that some of us seem to be having. I tried this solution, comment #4 of the xfce4-mixer bug filed, and it seemed to work for me.
Quote:
Hmm,
After open & close the mixer plugin's property dialog, it works fine on my system.
Adjusting volume by mouse wheel is available and tooltip appears now.
Well, I've tried this in the past and it didn't work, but I only looked at the properties and as they were correct, closed the window.
Yeah, even though I said I wouldn't, I've tried 4.8, again, but this time before moving the mouse wheel over the icon and having the mixer fail, I opened the properties window, changed the properties, changed them back to the correct settings, and then closed the window. Now it works. Go figure???!!!
Last edited by cwizardone; 06-11-2011 at 11:55 PM.
Distribution: Slackware64-current with "True Multilib" and KDE4Town.
Posts: 9,101
Rep:
Latest Fun and Games with 4.8.
As mentioned just above the mixer problem is solved so I've been running 4.8.
Then one day last week I booted up and there was no mouse. I played around with the settings and it once again became visible. A day or so later I booted up and there was no window manager, so I deleted on the Xfce configurations files and started over.
Everything was fine until yesterday morning when I booted up and, again, the mouse was not visible.
This time I said, "enough" and started using KDE. However, I've come to prefer Xfce so yesterday afternoon I, once again, deleted the configuration files and started over. Everything was fine for the rest of the day.
This morning I booted up and, again, everything was fine. As I was going out for a few hours I shut the machine down and when I came back almost 4 hours later and booted it up, once again the window manager was missing and the mouse was represented by a simple "X", so I'm now back to using KDE.
Regarding the auto-mounting issue, I think I've found the solution on Arch Linux forums.
You need to create an ~/.xinitrc file (or modify it if it exists) and add the following line:
Code:
exec ck-launch-session dbus-launch xfce4-session
According to the user who posted the solution:
Quote:
Originally Posted by 7x1x from Arch Linux Forums
dbus needs to be after consolekit to fix the authorization problems.
Hope this solve your problem. I use startx on a Debian Sid system to log into Xfce. No Login Managers in the way, just startx, and it solved the authorization issue.
Distribution: Slackware64-current with "True Multilib" and KDE4Town.
Posts: 9,101
Rep:
Quote:
Originally Posted by yuuko
cwizardone,
I used to have a similar problem with a custom cursor theme under Xfce 4.6. I simply changed to another cursor theme and it's solved. Hope it helps.
Thanks for your reply.
I've found from trial and error that if one stays with the default settings there are few problems. However, pick a different theme for the desktop or mouse and the problems will follow shortly.
I've, finally, I hope given up on 4.8x and have switched to KDE 4.6.5 (minus the evil triplets).
With all the additional baggage that came with Xfce 4.8, it is using almost as much memory as KDE, so why bother with it.
Last edited by cwizardone; 07-22-2011 at 07:04 AM.
Distribution: Slackware64-current with "True Multilib" and KDE4Town.
Posts: 9,101
Rep:
Gone back to Xfce 4.6.2. It just "feels" and looks (with a little tweaking) better, imho, and 4.8x is not ready for prime time.
Even if it were it doesn't bring anything new to the table that I use and the additional baggage that comes with it is hardy worth the "price" for what little there is in "improvement."
Last edited by cwizardone; 07-22-2011 at 01:30 PM.
I installed xfce 4.8 from Robby and it is working fine.
Just a question how to setup avahi? In the botting process gives a warning with a missing name and the daemon don't start :x
Other question, I can mount usb disks and pens, but i can't create files or folders?
I installed xfce 4.8 from Robby and it is working fine.
Just a question how to setup avahi? In the botting process gives a warning with a missing name and the daemon don't start :x
Other question, I can mount usb disks and pens, but i can't create files or folders?
/etc/passwd:avahi:x:85:85:User for Avahi:/dev/null:/bin/false
/etc/group:avahi:x:85:
I guess rc.M is the place for this:
# Start avahidaemon
if [ -x /etc/rc.d/rc.avahidaemon ]; then
/etc/rc.d/rc.avahidaemon start
fi
# Start avahidnsconfd
if [ -x /etc/rc.d/rc.avahidnsconfd ]; then
/etc/rc.d/rc.avahidnsconfd start
fi
and then rc.K ??
# Stop avahidnsconfd
if [ -x /etc/rc.d/rc.avahidnsconfd ]; then
/etc/rc.d/rc.avahidnsconfd stop
fi
# Stop avahidaemon
if [ -x /etc/rc.d/rc.avahidaemon ]; then
/etc/rc.d/rc.avahidaemon stop
fi
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.