Thunar, Tumbler and (un)mounting

Hello everyone,
I have the following problem, and I suspect it's a bug of some sort.
If I insert a USB stick, memory card or any other sort of removable media, and I access a folder which contains images that can be thumbnailed by Tumbler, it will run tumblerd, which is its daemon, and won't stop even if I try to unmount. It will thus keep the drive busy (possibly for a very long time). I don't even want stuff on removable drives to have thumbnails.
I can unmount by killing tumblerd, but that is hardly a user friendly solution. I suppose the logical thing would be for Thunar to do that itself. What do you think? Are there solutions? Can I disable thumbnailing for removable devices?
Thanks,
Nanthiel

I searched for documentation for tumbler but couldn't find anything. It seems that there is no configuration available either, and the only option in Thunar is the boolean "MiscShowThumbnails". Maybe a quick hack would be to patch Thunar to call "system("pkill tumbler")" or something similar when unmount or eject are clicked...
From the gnome doc about dbus thumbnailing:
Cancel/Dequeue thumbnail requests
<method name="Dequeue">
<arg type="u" name="handle" direction="in" />
</method>
The Dequeue method removes thumbnail requests from the queue. A service implementation is only guaranteed to cancel requests that have not started processing yet when it receives the Dequeue request. A service implementation may cancel an in-progress request if possible, but clients should not depend on this behavior being available.
... which seems to indicate that there is no "good" way of stopping the thumbnailer...

Similar Messages

Thunar dont show (and dont mount) removable devices and ntfs drives

hi.this my first topic
im using arch+openbox+thunar
and thunar dont show (and dont mount) removable devices and ntfs drives
more info:
i'v installed :
gvfs , gvfs-smb , gvfs-afp , thunar-volman , polkit , gnome-polkit , ntfs-3g
thunar-volman output for CD/DVD:
thunar-volman: Could not detect the volume corresponding to the device.
thunar-volman output for USB:
thunar-volman: Unsupported USB device type.
thunar-volman: Unsupported USB device type.
thunar-volman: Unknown block device type.
thunar-volman: Could not detect the volume corresponding to the device
~/.xinitrc:
openbox-session
~/.config/openbox/autostart:
thunar --daemon &
sleep 1 && /usr/lib/polkit-gnome/polkit-gnome-authentication-agent-1 &
tint2 &
sh ~/.fehbg &
conky &
pstree output:
[hamon@dhcppc0 ~]$ pstree
systemd─┬─agetty
├─at-spi-bus-laun─┬─dbus-daemon
│ └─3*[{at-spi-bus-laun}]
├─at-spi2-registr───{at-spi2-registr}
├─conky───3*[{conky}]
├─2*[dbus-daemon]
├─dbus-launch
├─dhcpcd
├─polkitd───5*[{polkitd}]
├─sh───polkit-gnome-au───{polkit-gnome-au}
├─slim─┬─X
│ └─bash───openbox───opera───3*[{opera}]
├─systemd───(sd-pam)
├─systemd-journal
├─systemd-logind
├─systemd-udevd
├─terminator─┬─bash───pstree
│ ├─gnome-pty-helpe
│ └─{terminator}
├─tint2
└─xfconfd
please help me
Last edited by hamon (2013-11-05 09:17:21)

Please use code tags. If you don't know how to do this, click the 'BBCode' link on the bottom of the page for instructions (there are all kinds of neat formatting tricks included as well).

Xfce - thunar - gconf - dconf - usb mounting - why - how - bah

Hello,
I have disabled all automounting.
I need to know what file I need to edit to change the options that xfce uses to mount. Or whatever it uses to mount when you right click and hit mount.
I am trying to mount a usb stick.
I have tried looking in dconf and gconf.
How does it work?
A few people mentioned gvfs and udisks.
I think it uses udev. I know it does not any longer use hal.
What am I missing here? What do I need to read?
Thanks,
Web...

Sorry for posting this link but I do not have time to write it again. This is my opinion and what I ended up doing.
http://wiki.hackspherelabs.com/index.ph … disks-GVFS
If I am correct kernal passes to udisks which passes to gvfs or udev or something right?
I gave up on Thunar.
I would really like to figure out how to configure the gvfs/thunar default mounting rules.
Thanks,
Web...
I also found this link: https://bbs.archlinux.org/viewtopic.php?id=112846
The entire reason I started this.
Last edited by webdawg (2011-11-15 19:22:35)

Thunar doesn't automatically mount removable devices

This is a newbie question, but I cannot find how Thunar automatically mounts removable devices. I've read the wiki and it says that I don't have to do anything else besides installing Thunar. Once I plug in my removable device, it can be seen in lsblk, but I need to manually mount it using the terminal. Thunar doesn't do anything to make it appear in the file system. Did I miss something?

karol wrote:
https://wiki.archlinux.org/index.php/Th … me_Manager says
While Thunar can support automatic mounting and unmounting of removable media, the Thunar Volume Manager allows extended functionality, such as automatically running commands or automatically opening a Thunar window for mounted media.
so thunar-volman shouldn't be required.
Exactly. However, I tried to install the volume manager, but it didn't help. It should work without it.
karol wrote:Do you have gvfs installed?
I didn't (judging from the fact that writing gvfs in the terminal didn't find anything). I installed it, but nothing changed. How to configure it?
Last edited by decas (2014-02-16 14:43:16)

I used a partitioned HDD for time machine, using a partition already containing other data files. I am now no longer able to view that partition in Finder. Disk Utility shows it in grey and "not mounted". Any suggestions of how to access the files?

I used a partitioned HDD for time machine, using a partition already containing other data files. I am now no longer able to view that partition in Finder. Disk Utility shows it in grey and "not mounted". Any suggestions of how to access the files? Does using time machine mean that that partition is no longer able to be used as it used to be?
HDD is a Toshiba 1TB, partitioned into two 500GB partitions.
OS X version 10.9.2

Yes, sharing a TM disk is a bad idea, and disks are cheap enough so that you don't need to.
Now
Have you tried to repair the disk yet

Verizon Wirless 4GLTE for Tarboro, North Carolina Edgecombe and Rocky Mount NC Nash/Edgecombe

Hello Verizon Wireless!
Could you please tell me when the release date for 4GLTE for Tarboro and Rocky Mount which is in Edgecombe and Nash County in North Carolina? Because, 4GLTE has service in Pitt County which is the next county from us which is Greenville, North Carolina and it seems like to me that Verizon should be working on our towers to upgrade to 4GLTE since Greenville has all their towers upgraded to 4GLTE. I am really serious about this, I think Verizon should ahead and upgrade our cell towers to 4GLTE since the next county from us has been upgraded. If anyone reads this message please share your comments on what you think about this, because we need more people that's even near this area to let Verizon Wireless know how much we need 4GLTE in our area this month or next month. Thanks so much for your time.
Jeremy!

This is a customer peer to peer forum here so no one knows what expansion plans are in store for your area.
That being said, Verizon Wireless has stated that they plan to complete the the 4G LTE build-out by the end of 2012. So sometime between now and then is when you should get upgraded to the 4G LTE network.

How can i format and finaly mount??

Hi guys,
i'm trying to create an image bootable from scratch, but i fell in error right at the beginning .
I've created an image filled by zero with
dd if=/dev/zero of=deb.iso bs=1M count=2048
after that i've partitioning this file with
cfdisk deb.iso
and the resultant partition table is
Disk ../deb.iso: 2 GiB, 2147483648 bytes, 4194304 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x114cf359
Device Boot Start End Sectors Size Id Type
../deb.iso1 * 2048 718847 716800 350M 83 Linux
../deb.iso2 718848 4194303 3475456 1,7G 83 Linux
At this point i've create a block devices for each partition, so
losetup -o $((2048*512)) /dev/loop0 ../deb.iso
losetup -o $((718848*512)) /dev/loop1 ../deb.iso
then i formatted it in ext4
mkfs.ext4 /dev/loop0
mkfs.ext4 /dev/loop1
and until here everything goes right.
Now i decided to mount my formatted loop devices, so
mkdir root
mount /dev/loop1 root
cd root
mkdir boot
but when i give the command for mount the /dev/loop0, this give me back an error
mount /dev/loop0 boot
mount: wrong fs type, bad option, bad superblock on /dev/loop0,
missing codepage or helper program, or other error
In some cases useful info is found in syslog - try
dmesg | tail or so.
The permission of directory and the privilege for mount devices it's ok.
I also tried mount the partition without use losetup, directly from
mount -o loop,offset=$((2048*512)) -t ext4 ../deb.iso boot/
or format directly the partition with
mkfs.ext4 -E offset=$((2048*512)) deb.iso
but always is the same.
My dmesg said:
[ 3123.395788] JBD2: no valid journal superblock found
[ 3123.395796] EXT4-fs (loop0): error loading journal
Can someone help me with this damn trouble?? Thanks you very much
Last edited by Gianlucode (2014-12-01 12:17:26)

How we are used to hear in computer science, Divide et impera!
I divided my deb.iso in 3 pices using dd. Remebering the partitions table
Gianlucode wrote:Disk ../deb.iso: 2 GiB, 2147483648 bytes, 4194304 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x114cf359
Device Boot Start End Sectors Size Id Type
../deb.iso1 * 2048 718847 716800 350M 83 Linux
../deb.iso2 718848 4194303 3475456 1,7G 83 Linux
I use dd in this way
dd if=deb.img of=deb.img.mbr bs=512 skip=0 count=2048
dd if=deb.img of=deb.img.0 bs=512 skip=2048 count=716800
dd if=deb.img of=deb.img.1 bs=512 skip=718848
To be sure that i haven't corrupted something i've calculeted the md5 hash of this file and the original
cat deb.img.mbr deb.img.0 deb.img.1 | md5sum
f33fed42eb63666d325e4fff796bfef9
md5sum deb.img
f33fed42eb63666d325e4fff796bfef9
So i was able to format my partitions and then mount them
mkfs.ext4 deb.iso.0
mkfs.ext4 deb.iso.1
mkdir root
mount deb.iso.1 root
cd root
mkdir boot
mount ../deb.iso.0 boot
touch boot/test
cd ..
umount root/boot
umount root
I've reassembled the image
cat deb.img.mbr deb.img.0 deb.img.1 > deb_final.img
and obviously if i recalculate the md5 is different then the initaly deb.img because i formatted and wrote some file in these partitions.
md5sum deb.img
f33fed42eb63666d325e4fff796bfef9
md5sum deb_final.img
b1b5656781b28803759d46ee67c428d5
To be sure, i've done the ultimately proof
sudo mount -o loop,offset=$((2048*512)) deb_final.img root
ls root
test lost+found
Et voilà there is the file test as i aspected.
Now do not forget to umont the partition
sudo umount root
I hope that this post will be useful for someone in future. If you have other solution to the initial problem, write it below.
Last edited by Gianlucode (2014-12-02 14:48:39)

[SOLVED] kde 4.6 and Udisks mounting problems with Dolphin

Hello,
I have a problem with Dolphin in KDE 4.6 where it displays my non-Arch partitions (a / and /home used for Opensuse) as well as a CD-Rom or usb if inserted, but registers an error when I click on the device/partition icon. Specifically, I get the following error displayed at the bottom of Dolphin:
An error occurred while accessing Hard Drive, the system responded: org.freedesktop.UDisks.Error.Failed: Error creating mount point: No such file or directory.
Because of this error, I am unable to mount usb pendrives, access CDs, or access the non-Arch partitions. I'm not sure if this is a KDE error or if it related to Arch as I never encountered this error running KDE 4.6 in Opensuse.
My daemons running in /etc/rc.conf
DAEMONS=(syslog-ng dbus networkmanager netfs crond alsa kdm)
My /etc/fstab
#/dev/cdrom /media/cd auto ro,user,noauto,unhide 0 0
#/dev/dvd /media/dvd auto ro,user,noauto,unhide 0 0
#/dev/fd0 /media/fl auto user,noauto 0 0
/dev/sda1 / ext4 defaults,noatime 0 1
/dev/sda5 swap swap defaults 0 0
/dev/sda6 /home ext4 defaults,noatime 0 1
tmpfs /tmp tmpfs defaults,nodev,nosuid,mode=1777 0 0
tmpfs /var/lock tmpfs defaults,nodev,nosuid,noexec,mode=1777,size=10M 0 0
tmpfs /var/run tmpfs defaults,nodev,nosuid,noexec,mode=0755,size=10M 0 0
Now, I don't have hal running as a daemon as I have read that it is no longer needed in KDE 4.6. Similarly, I don't have my CD-Rom drive mounted as I read in the udev wiki that Udisks automatically mounts devices and partitions. The wiki also indicates that Udisks is supposed to require little configuration.
I've searched the forum and Google, and I have not been able to find any information documenting a Dolphin and UDisks mounting error in KDE 4.6.
I installed KDE through the # pacman -S kde command, but is there some other package that I need to install in order to get Udisks working properly?
Thanks.
Last edited by Bordee (2011-03-24 16:09:25)

When I enter $ groups in a terminal I get the following
sys adm disk lp wheel games video audio optical storage power users
So I'm definitely part of the storage group.
I think I found a solution. I created a /data mountpoint in fstab and a /data folder in my root directory. Now, I'm able to mount and access the contents of the /home partition from Opensuse. The reason I wanted to do this was to access music and photos and transfer them onto my Arch /home partition.
I uncommented the cdrom, dvd, and fd0 devices in fstab and I created /media/cd, /media/dvd, and /media/fl. After inputting a # mount -a, my CDROM drive reads properly as does my USB.
So once again, thank, you for pointing me in the right direction.
One final thought. I was under the impression from reading the UDisks information that it automatically detected and mounted other partitions and devices without them being explicitly mounted in fstab. Was the assumption wrong? In other words, for UDisks and Dolphin to work together properly in KDE 4.6, do all of the devices that appear have to first be mounted in fstab?

Missing loopback interface and modules, and isofs mounting [SOLVED!]

In my new archlinux istallation, isofs and loopback facilities are not present and when installed by hand do not seem to work. [See FINAL SOLUTION below. Thanks for the suggestions I got].
Now, I was under the impression that such facilities should be automatically available at the end of a normal installation.
For instance, in an installation I made last fall, I can mount .iso filesystem through the loopback interface with no problems (and that even without using -t, with just 'mount image.iso /mnt/iso'). In that installation, lsmod shows the modules
loop 18526 2
isofs 32946 1
(also, a module isofs is present in /lib/modules, though I cannot find a loop module there)
and eight loopback devices are available as /dev/loop0 ... /dev/loop7
On the other hand, in the new installation no /dev/loop devices are present, and no loop and isofs modules show up either
as installed (as reported by lsmod) or at least in the libraries. Has something changed recently? Do I need to install a package that will set up my installation for loopack mounting and mounting of .iso filesystems?
INTERIM SOLUTION
I mentioned above that in my older Linux box, on an Arch Linux installed months ago but not upgraded for many weeks, I had loopback devices running and isofs and loop modules installed, and all working well by itself. Today I did an upgrade, and noticed that it came with a new kernel (3.3?), probably the same I had on the new machine. So I rebooted after that---and found the exact problem as on the new machine: /dev/loop* missing, no modules isofs or loop appearing in lsmod. So I installed by hand a loopback interface, with 'mknod /dev/loop0 b 7 0'. Then I made sure I had the isofs package installed, and installed the isofs module with modprob; this time isofs showed on lsmod, but loop didn't yet. Finally I mounted a data DVD (note that the incantation -t iso9660 is no longer necessary), and as a last thing I mounted an .iso file; both worked. Only after this did a module loop show up in lsmod.
So probably something subtle changed in the dependencies between installed packages, installed modules, and installed loopback devices, so that something is out of sync and has to be nursed manually. Better experts than I may throw
some light on this problem and hopefully fix it.
FINAL AND SATISFACTORY SOLUTION
Whatever may have happened before, the following works like a charm:
I upgrade Arch; it installs 3.3.1-1-ARCH as a kernel in /boot.
I reboot to let the new kernel "take".
No loop0,...,loop7 devices show up in /dev; no isofs or loop show up with lsmod; isofs (but no loop) present in /lib/modules
I do 'mount /dev/sr0 /iso' (NOTE: no -t iso9660' option) with a CD in the sr0 drive; the CD filesystem shows up in /iso.
After this, isofs shows up in 'lsmod|grep isofs', but no loop device yet.
I unmount /iso and do 'mount ~tt/ markov.iso /iso' (NOTE: no -t iso9660' option); the markov filesystem shows up in /iso.
After this, loop0,...,loop7 devices show up in /dev, and a loop module (wherever that camefrom) appears in lsmod.
In other words, everything required for isofs automounts as necessary and remains mounted until new reboot.
The '-t iso9660' option is not necessary. As noted by an other Arch post, this option may be detrimental and might have been the culprit; this is an issue I will explore on the next reboot.
Last edited by rugantino (2012-04-11 20:11:55)

When /etc/rc.sysinit is invoked during the bootprocess; it should automatically start a loopback interface (unless you've specifically disabled it in /etc/rc.d/network or so).
Check your logs to see if your find any related errors.

Interested in buying an old 35mm prime lens for my film camera that would fit and EF mount.

Interested in buying an old 35mm prime lens for my film camera that would fit and EF mount. I've found plenty of FD mounts and plenty of newer EF lenses around $200-300. Would like somethign in between if anyone has something. Does not have to be Canon brand.

I would not buy Canon FD or Minolta MD lenses as they will need a very expensive modification on order to work with any Canon EOS camera. (film or digital) There are cheap adapters available, but they have cheap glass optics that ruin the image quality.
Old Manual Focus lenses from Nikon, Pentax, and Olympus can use a very inexpensive adapter with Canon EOS cameras and still give great results.
More info here: Using Manual Focus Lenses on Canon EOS bodies
Mike Sowsun
S110, SL1, 5D Mk III

Best iPad 2 Stand and Car Mount?

I don't know whether this has been discussed, but that's the best iPad 2 stand and car mount?

This is my favorite stand.
http://www.arkon.com/iPad_accessories/iPad_stand.html
What I like about it is the way it folds up. With practice you can snap it from fully open to fully shut, and stuff it in a shoulder-bag (or whatever you're using to carry your iPad in), in a flash, with just one hand. It's light, clicks to hold the iPad at nearly any angle from vertical to around 50 degrees off vertical, and has very soft padding on all the right spots so that you don't have to worry about it scratching the iPad or somebody's expensive table top.
The downside is it's plastic. So it's not going to last forever, or win points for adding a touch of elegance to the room, but for twenty bucks a pop I'm happy with it.
Can't vouch for any of the other stands they make, like the ones for the car, haven't tried any of them yet.

IMac intel core, 10.6.8 - isn't mounting my partioned iomega drive. How do i get it to mount and stay mounted?

iMac intel core, 10.6.8 - isn't mounting my partitioned iomega drive. It was mounting one of the partitions, but not the other one for a while. Then they both stopped showing up. I can not select the drive in Time Machine. I verified and repaired the iMac hard drive with Disk Utility. Then tried to verify and repair iomega drive in Disk Utility. It appears briefly but then disappears. One partition might be bad, what do i do? Then name of the partition changed to something like disk1:3 when it was called MAC. I want to see what's on it and ideally continue to use it as our backup in Time Machine. How do I get it to mount and stay mounted?

The usage figure reported by the activity monitor is likely to include only the core progam, the APIs that are being called and space for variables. FCP moves huge amounts of data around the system but, in general, I would imagine these are handled by the OS so would not (except maybe momentarily) be included in the acitivity monitor total.
If you have very little memory and it "runs out" so to speak, the OS will start swapping files on and off the disc which will slow the system down to a crawl if you have a standard hard drive. So with 16GB you have loads of room for the data transfers to take place quickly and efficiently. So, I would say you had not wasted your money! A very wise investment.

Thunar, xfce4 and polkit-gnome

I've spent 3 hours this morning trying to understand mount permissions in Thunar and, thus, how polkit controls user access. I'm pleased to say it hasn't been a total waste of time because I have a much better understanding of what polkit does and why.
However, in my investigations I have seen countless forum threads by people trying to fix their Thunar mount problems. The simple answer to almost all of these threads is "install polkit-gnome and restart".
Arch uses auth_admin_keep for internal mounting permissions - for that to work you MUST have a PolicyKit Authentication Agent installed (right?) - polkit-gnome is exactly that. Without polkit-gnome there is no application to pop-up and ask you for your password, which is exactly what the auth_admin option wants to do.
So, how is it an optional depend for thunar?

.:edit:.
Whether automounting is or isn't an "optional" feature is largely irrelevant.
My main point is that policykit requires a User Authenication Agent to function correctly - gnome-session and kdelibs pull in polkit-gnome and polkit-kde respectively by default. Why is XFCE different just because they don't ship their own User Authentication Agent?
anonymous_user wrote:It is optional because Thunar will still work without it. Mounting may not work, but file manager duties like moving and deleting files do work. At least that is my understanding of optional dependencies.
Yes, that was my understanding too... 5 years ago.
Udev and PolicyKit exist to make mounting disks, amongst other things, "as standard" across multiple environments, this functionality has been incorporated in Thunar. Mounting in Thunar is as much a feature as moving and deleting files.
It's also worth mentioning that I didn't set out to make automounting work in Thunar - I just had these Drives appearing in my sidebar but when I clicked on them I got an error.
That's the definition of broken from a users perspective.
Last edited by dtw (2012-04-09 13:58:33)

Thunar crashes with samba mount

Thunar (and some other stuff probably) seems to crash sometimes when I play an mp3 with VLC from a samba share which has been auto mounted from thunar by browsing 'network'.
dmesg:
[ 659.966753] Thunar[338]: segfault at 18 ip 00000000004548a9 sp 00007fffe604c0f0 error 4 in thunar[400000+98000]
After the crash I am unable to mount the samba share again from within thunar.
Similar dmesg output in this thread:
https://bbs.archlinux.org/viewtopic.php?id=154103
*Edit
journal:
Jun 15 12:32:52 jason-pc udisks-daemon[371]: **** UPDATING /sys/devices/pci0000:00/0000:00:1a.7/usb1/1-5/1-5:1.0/host8/target8:0:0/8:0:0:0/block/sdb
Jun 15 12:32:52 jason-pc udisks-daemon[371]: **** CHANGED /sys/devices/pci0000:00/0000:00:1a.7/usb1/1-5/1-5:1.0/host8/target8:0:0/8:0:0:0/block/sdb
Jun 15 12:32:52 jason-pc udisks-daemon[371]: (udisks-daemon:371): udisks-daemon-WARNING **: Error launching hdparm: Failed to execute child process "hdparm" (No such file or directory)
Jun 15 12:32:52 jason-pc udisks-daemon[371]: helper(pid 385): completed with exit code 0
Jun 15 12:32:52 jason-pc udisks-daemon[371]: **** EMITTING CHANGED for /sys/devices/pci0000:00/0000:00:1f.2/ata3/host2/target2:0:0/2:0:0:0/block/sda
Jun 15 12:32:53 jason-pc kernel: fuse init (API version 7.21)
Jun 15 12:32:53 jason-pc systemd[1]: Mounting FUSE Control File System...
Jun 15 12:32:53 jason-pc udisks-daemon[371]: **** /proc/self/mountinfo changed
Jun 15 12:32:53 jason-pc systemd[1]: Mounted FUSE Control File System.
Jun 15 12:32:53 jason-pc dhcpcd[208]: enp5s0: sending IPv6 Router Solicitation
Jun 15 12:32:53 jason-pc dhcpcd[208]: enp5s0: no IPv6 Routers available
Jun 15 12:32:53 jason-pc udisks-daemon[371]: **** /proc/self/mountinfo changed
Jun 15 12:32:54 jason-pc dbus-daemon[141]: dbus[141]: [system] Activating via systemd: service name='org.freedesktop.UDisks2' unit='udisks2.service'
Jun 15 12:32:54 jason-pc dbus[141]: [system] Activating via systemd: service name='org.freedesktop.UDisks2' unit='udisks2.service'
Jun 15 12:32:54 jason-pc systemd[1]: Starting Disk Manager...
Jun 15 12:32:55 jason-pc udisksd[432]: udisks daemon version 2.1.0 starting
Jun 15 12:32:55 jason-pc systemd[1]: Starting CUPS Printing Service...
Jun 15 12:32:55 jason-pc systemd[1]: Started CUPS Printing Service.
Jun 15 12:32:55 jason-pc systemd[1]: Started Disk Manager.
Jun 15 12:32:55 jason-pc dbus-daemon[141]: dbus[141]: [system] Successfully activated service 'org.freedesktop.UDisks2'
Jun 15 12:32:55 jason-pc dbus[141]: [system] Successfully activated service 'org.freedesktop.UDisks2'
Jun 15 12:32:55 jason-pc udisksd[432]: Acquired the name org.freedesktop.UDisks2 on the system message bus
Jun 15 12:33:02 jason-pc NetworkManager[137]: <info> (enp5s0): IP6 addrconf timed out or failed.
Jun 15 12:33:02 jason-pc NetworkManager[137]: <info> Activation (enp5s0) Stage 4 of 5 (IPv6 Configure Timeout) scheduled...
Jun 15 12:33:02 jason-pc NetworkManager[137]: <info> Activation (enp5s0) Stage 4 of 5 (IPv6 Configure Timeout) started...
Jun 15 12:33:02 jason-pc NetworkManager[137]: <info> Activation (enp5s0) Stage 4 of 5 (IPv6 Configure Timeout) complete.
Jun 15 12:33:11 jason-pc sudo[469]: jason : TTY=pts/0 ; PWD=/home/jason ; USER=root ; COMMAND=/usr/bin/vim /etc/fstab
Jun 15 12:33:11 jason-pc sudo[469]: pam_unix(sudo:session): session opened for user root by jason(uid=0)
Jun 15 12:33:17 jason-pc sudo[469]: pam_unix(sudo:session): session closed for user root
Jun 15 12:36:07 jason-pc systemd[1]: Time has been changed
Jun 15 12:42:31 jason-pc sudo[861]: jason : TTY=pts/0 ; PWD=/home/jason ; USER=root ; COMMAND=/usr/bin/dd bs=4M if=archlinux-2013.06.01-dual.iso of=/dev/sdb
Jun 15 12:42:31 jason-pc sudo[861]: pam_unix(sudo:session): session opened for user root by jason(uid=0)
Jun 15 12:43:24 jason-pc sudo[861]: pam_unix(sudo:session): session closed for user root
Jun 15 12:43:24 jason-pc udisks-daemon[371]: **** CHANGING /sys/devices/pci0000:00/0000:00:1a.7/usb1/1-5/1-5:1.0/host8/target8:0:0/8:0:0:0/block/sdb
Jun 15 12:43:24 jason-pc udisks-daemon[371]: **** UPDATING /sys/devices/pci0000:00/0000:00:1a.7/usb1/1-5/1-5:1.0/host8/target8:0:0/8:0:0:0/block/sdb
Jun 15 12:43:24 jason-pc udisks-daemon[371]: **** EMITTING CHANGED for /sys/devices/pci0000:00/0000:00:1a.7/usb1/1-5/1-5:1.0/host8/target8:0:0/8:0:0:0/block/sdb
Jun 15 12:43:24 jason-pc udisks-daemon[371]: **** CHANGED /sys/devices/pci0000:00/0000:00:1a.7/usb1/1-5/1-5:1.0/host8/target8:0:0/8:0:0:0/block/sdb
Jun 15 12:43:26 jason-pc kernel: Thunar[338]: segfault at 18 ip 00000000004548a9 sp 00007fffe604c0f0 error 4 in thunar[400000+98000]
Jun 15 12:43:27 jason-pc systemd-coredump[882]: Process 338 (Thunar) dumped core.
Jun 15 12:43:38 jason-pc kernel: usb 1-5: USB disconnect, device number 2
Jun 15 12:43:38 jason-pc udisks-daemon[371]: **** scsi_host IGNORING REMOVE /sys/devices/pci0000:00/0000:00:1a.7/usb1/1-5/1-5:1.0/host8/scsi_host/host8
Jun 15 12:43:38 jason-pc udisks-daemon[371]: **** REMOVING /sys/devices/pci0000:00/0000:00:1a.7/usb1/1-5/1-5:1.0/host8/target8:0:0/8:0:0:0/block/sdb
Jun 15 12:43:38 jason-pc udisks-daemon[371]: **** EMITTING REMOVED for /sys/devices/pci0000:00/0000:00:1a.7/usb1/1-5/1-5:1.0/host8/target8:0:0/8:0:0:0/block/sdb
Jun 15 12:47:27 jason-pc systemd[1]: Starting Cleanup of Temporary Directories...
Jun 15 12:47:27 jason-pc systemd-tmpfiles[954]: stat(/run/user/1000/gvfs) failed: Permission denied
Jun 15 12:47:27 jason-pc systemd[1]: Started Cleanup of Temporary Directories.
Jun 15 12:58:10 jason-pc sudo[1182]: jason : TTY=pts/1 ; PWD=/home/jason ; USER=root ; COMMAND=/usr/bin/journalctl -b
Jun 15 12:58:10 jason-pc sudo[1182]: pam_unix(sudo:session): session opened for user root by jason(uid=0)
Also, I see two instances of the same windows share sometimes in the 'browse network' panel of thunar, but this is probably unrelated
Last edited by jrussell (2013-06-15 11:04:48)

Just to close this out: the answer was it wasn't the Xserve at all. It turns out the Windows clients were running an anti-virus program that was scanning the network drives on login. So, when they all logged in simultaneously they hit the Xserve with 50 scans and it was so busy dealing with the load that it couldn't process the logins for the others.
Unfortunately we didn't find this out until the Teacher was completely feed up with the Apple unit and removed it from the school (to put it politely). When the new (Linux based) unit exhibited the same slowdown, we figured it must be with the Windows clients. After we turned off the anti-virus network drive scan, everything got much better.
So, while this does have a happy ending (the network works) it did involve an Apple casualty. I tried my best, but maybe this post will help someone else that find themselves in the same predicament.
Later...
Richard

Word 2008 for Mac and NFS mounted home directories "Save File" issues

Greetings everyone,
(Long time lurker, first time poster here)
I admin a small network (under 20 workstaitons) with a centralized NFS server, with user home directories mounted via NFS upon login. Users are authenticated via LDAP. This is all working fine, there is no problem here. The problem lies when my users use Microsoft Word 2008 for Mac. When they attempt to save a file to thier Desktop (or Documents or any folder under thier home dir) they are met with the following message:
(dialog box popup)
"Word cannot save or create this file. The disk maybe be full or write-protected. Try one or more of the following: * Free more memory. * Make sure the disk you want to save the file on is not full, write-protected or damaged. (document-name.ext)"
This happens regardless of file format (Doc, Docx, Txt) and regardless of saved location under the network mounted dir. I've noticed that when saving Word creates a .tmp file in the target directory, which only further confuses me to the underlying cause of the issue.
When users logon to a local machine account and attempt the save, there is no issue.
I have found many posts in other commuity forums, including this one, indicating that the issue is a .TempoaryItems folder in the root of the mounted directory. This folder already exists and is populated with entries such as "folder.2112" (where 2112 is the uid of the LDAP user). I find other posts indicating that this is an issue with Word:2008 and OSX10.8, with finger pointing in either direction, but no real solution.
I have installed all Office for Mac updates from Microsoft (latest version 12.3.6).
I have verified permissions of the user's home dir.
I have also ensured that this issue effects ONLY Microsoft Office 2008 for Mac apps, LibreOffice and other applications have no issue.
Does *ANYONE* have a solution or workaround for this issue? While we're trying to phase Microsoft products out, getting users to ditch Word and Excel is difficult without removing them from systems completely. So any pointers or help would be greatly appreciated.
Thanks.
~k

I can't tell you how to fix bugs in an obsolete version of Office, but a possible workaround is to use mobile home directories under OS X Server. The home directories are hosted locally and synced with the server.

Thunar, Tumbler and (un)mounting

Similar Messages

Maybe you are looking for