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.
I`m having one of those feelings that tomorrow or the day after tomorrow I`ll see an entry in the changelog telling that firefox and thunderbird were upgraded and that Slackware 14 left the RC state.
I have installed current into a Vbox session and upon starting the Xfce session the first time, I had nothing, so I ran xfce4-panel and now it's as expected.
LOL, we've taken so long with this release cycle that EMACS has updated to 24.2 on Sunday! Wonder if Pat will include it--it says it's "primarily a bugfix release", but at the same time includes some neat upgrades related to compiling support for a bunch of libraries.
just got out today but I'm testing it at work (I used the provided SlackBuild): the most notable change, in my opinion, seems the introduction of the directive
Code:
UsePrivilegeSeparation sandbox # Default for new installations.
Did you remember to put your user in the plugdev group?
My apologies for taking a while to respond properly. To recap, a fresh install of Slackware 14 - RC3, XFCE selected. KDE not installed. User group flags are: users disk lp floppy audio video cdrom plugdev power netdev.
The window manager is XDM. Default settings for XDM. In XFCE, mount settings in Removable Drives And Media flags set (mount removable when hot plugged, mount removable when inserted).
Automount does not work for removable CD-roms and USB. Dmesg shows the devices inserted and detected. I can manually mount the drives and umount via the terminal.
However, my local .Xsession-errors has an interesting log of DBus and Glib errors. And add a thunar-vol error message when inserting a CD. Attaching .txt file.
Code:
xsession-error
** (nm-applet:1799): CRITICAL **: dbus_set_g_error: assertion `gerror == NULL || *gerror == NULL' failed
** (process:1801): WARNING **: Trying to register gtype 'GMountMountFlags' as enum when in fact it is of type 'GFlags'
** (process:1801): WARNING **: Trying to register gtype 'GDriveStartFlags' as enum when in fact it is of type 'GFlags'
** (process:1801): WARNING **: Trying to register gtype 'GSocketMsgFlags' as enum when in fact it is of type 'GFlags'
(xfdesktop:1786): GLib-GIO-CRITICAL **: g_file_get_path: assertion `G_IS_FILE (file)' failed
(xfdesktop:1786): GLib-GIO-CRITICAL **: g_file_get_path: assertion `G_IS_FILE (file)' failed
(xfdesktop:1786): GLib-GIO-CRITICAL **: g_file_get_path: assertion `G_IS_FILE (file)' failed
(xfdesktop:1786): GLib-GIO-CRITICAL **: g_file_get_path: assertion `G_IS_FILE (file)' failed
(xfdesktop:1786): GLib-GIO-CRITICAL **: g_file_get_path: assertion `G_IS_FILE (file)' failed
(xfdesktop:1786): GLib-GIO-CRITICAL **: g_file_get_path: assertion `G_IS_FILE (file)' failed
(xfdesktop:1786): GLib-GIO-CRITICAL **: g_file_get_path: assertion `G_IS_FILE (file)' failed
thunar-volman: Could not detect the volume corresponding to the device.
Is XDM properly initializing XFCE or Dbus and glib errors from recent updates interfering with XFCE automount?
Yep, looks like the removable media handling is still a bit iffy.
I normally use the semi-automatic mounting from the thunar side-panel and don't have the auto-mounting in the volume manager turned on, so I hadn't noticed, but I just repeated what you did above and I also see this behaviour.
Interestingly, only 1 of my 3 USB sticks seems to not auto-mount. An inserted CD also failed to mount automatically (though an icon on the desktop did present).
As the USB stick that fails to auto-mount can be mounted semi-automatically from the thunar side panel I am wondering whether this is some sort of timing issue when the device is first inserted (it takes significantly longer for it's icon to present than for my other usb sticks).
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.