LinuxQuestions.org
Review your favorite Linux distribution.
Home Forums Tutorials Articles Register
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Software
User Name
Password
Linux - Software This forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.

Notices


Reply
  Search this Thread
Old 07-05-2013, 10:03 PM   #1
Quija
LQ Newbie
 
Registered: Jan 2010
Location: SoCal
Distribution: openSuSE, Ubuntu
Posts: 7

Rep: Reputation: 0
Unison crashes when selecting a source or destination location


Hello All,

I've search the web as well as LQ forums and could not find a solution. When I attempt to select a source or destination folder in Unison the application simply disappears. I've tried running this as the root account as well with the same results. I'm running openSuSE 12.3 x64

Thanks for your assistance with this matter,

Quija
 
Old 08-26-2013, 03:04 PM   #2
jsthale
LQ Newbie
 
Registered: Aug 2010
Location: Deerfield, IL
Distribution: SuSE 11.3_64
Posts: 3

Rep: Reputation: 1
Unison

I have had similar experiences with Unison. As soon as I select a destination and choose a filesystem it closes and shuts down.
I have checked the log with dmesg and get the result that there is a library issue. Segmentation fault.

[456847.728616] unison[18125]: segfault at 30 ip 00007fedd1873958 sp 00007fff521330d0 error 4 in libgtk-x11-2.0.so.0.2400.18[7fedd1658000+42c000]

I am also running 64-bit opensuse 12.3. The problem began with the upgrade. I'm thinking maybe of trying to downgrade the library to see if that fixes the problem. It ws flawless before that.
 
1 members found this post helpful.
Old 08-26-2013, 05:08 PM   #3
Habitual
LQ Veteran
 
Registered: Jan 2011
Location: Abingdon, VA
Distribution: Catalina
Posts: 9,374
Blog Entries: 37

Rep: Reputation: Disabled
are there any files in ~/.unison?

You may be able to mv it to a ~/.unison.org and restart the unison and see what's what?

version?
http://www.cis.upenn.edu/~bcpierce/u...l#afterinstall
 
Old 08-27-2013, 08:10 AM   #4
jsthale
LQ Newbie
 
Registered: Aug 2010
Location: Deerfield, IL
Distribution: SuSE 11.3_64
Posts: 3

Rep: Reputation: 1
unison segmentation fault

I have tried moving the original .unison directory to ~/.unison.org with no joy. I still get the same segmentation error 4 in libgtk-x11:

unison[4384]: segfault at 30 ip 00007f1ce06d3958 sp 00007fffbc933c80 error 4 in libgtk-x11-2.0.so.0.2400.18[7f1ce04b8000+42c000]

could you suggest a method of back-revving the library? How might I go about contacting the developers to remedy this issue? I really like Unison and want to continue using it.
 
Old 11-25-2013, 07:34 PM   #5
rsmits
LQ Newbie
 
Registered: Jan 2008
Posts: 5

Rep: Reputation: 0
Problem caused by KDE4 designers moving USB location

I think I've discovered my unison problem. I've been trying to sync files with a USB drive. In their wisdom, the KDE4 people moved the location of where to find USB Media between 12.2 and 12.3 in OpenSuse.

On 12.2 the default policy was to mount external drives in /media, and on 12.3
> > it is different.

Check Bug 809837 - udisks ignores UDISKS_FILESYSTEM_SHARED flag
Bug List:
<<First (This bug is not in your last search results) Last>> Show last search results
Bug #809837 Overview
Opened: 2013-03-17 08:08 UTC Last modified: 2013-07-20 08:57:52 UTC
Classification Product Component Found in Version
openSUSE openSUSE 12.3 Basesystem Final
Severity Priority Status Target Milestone for Fix
Major P5 - None VERIFIED ---
Hardware OS Resolution Keywords
All Other FIXED

View Bug Activity — Format For Printing

Summary: udisks ignores UDISKS_FILESYSTEM_SHARED flag
Collapse All Comments - Expand All Comments
[reply] [-] Description Aekold Helbrass 2013-03-17 08:08:48 UTC

User-Agent: Opera/9.80 (X11; Linux x86_64; U; en) Presto/2.10.289
Version/12.00

OpenSUSE 12.2 mounts external storages in /media/LABEL.
OpenSUSE 12.3 changed this policy to mount everything in user-specific folders
in /var/run/USERNAME.

This change makes impossible to have user home folder on external storage,
symlinked to /home.

udisks2 has special udev flag to make it configurable, UDISKS_FILESYSTEM_SHARED
(http://udisks.freedesktop.org/docs/latest/udisks.8.html), but it appeared in
version 2.0.91 and is not supported in 2.0.0 version, included with OpenSUSE
12.3.

Please update udisks2 version to current version.

Reproducible: Always

Steps to Reproduce:
1. add a rule line to your udev configuration:
ENV{ID_FS_USAGE}=="filesystem|other|crypto", ENV{UDISKS_FILESYSTEM_SHARED}="1",
ATTR{UDISKS_FILESYSTEM_SHARED}="1", ATTRS{UDISKS_FILESYSTEM_SHARED}="1"
2. insert external storage device
3. see the mount point of device
Actual Results:
device is mounted in user-specific folder in /var/run

Expected Results:
as per documentation (and backward compatibility) device is expected to be
mounted in /media folder.

[reply] [-] Comment 1 Andrey Borzenkov 2013-03-17 12:39:19 UTC

Could you test updated package that includes support for
UDISKS_FILESYSTEM_SHARED.

zypper ar obs://home:arvidjaar:bnc:809837/standard bnc809837
zypper refresh bnc809837
zypper dup -r bnc809837

(In reply to comment #0)
> ENV{ID_FS_USAGE}=="filesystem|other|crypto", ENV{UDISKS_FILESYSTEM_SHARED}="1"

This is enough, other assignments do not do anything. Also make sure it is the
last rule (name it 99-something).

[reply] [-] Comment 2 Aekold Helbrass 2013-03-18 11:50:48 UTC

Ok, here's what I've done:

1. forked Factory udisks2, updated to version 2.1.0 (build services)
2. installed into my system.
3. checked if yast2 can see that version is 2.1.0.
4. changed the rule as suggested, renamed it from 71 to 99.
5. restarted the system.
6. mounted USB storage from KDE.

Result: it is still mounted into /var/run/media instead of /media.

Is there anything wrong with what I've done? udisks source code clearly checks
for that flag with g_udev_device_get_property_as_boolean method, but I cannot
hack deep enough to check if that method reads from
ENV{UDISKS_FILESYSTEM_SHARED} or that property should be set in some other
manner...

[reply] [-] Comment 3 Andrey Borzenkov 2013-03-18 12:23:16 UTC

Is UDISKS_FILESYSTEM_SHARED present in device properties?

udevadm info --query all --name sda1

or whatever name your partition has.

[reply] [-] Comment 4 Aekold Helbrass 2013-03-18 13:15:05 UTC

Nope. Here is the output:

book:~ # udevadm info --query all --name sde1
P:
/devices/pci0000:00/0000:00:14.0/usb3/3-2/3-2:1.0/host9/target9:0:0/9:0:0:0/block/sde/sde1
N: sde1
S: disk/by-id/usb-LaCie_LaCie_iamaKey_AA1431TTD86BRI6O-0:0-part1
S: disk/by-label/KEY
S: disk/by-path/pci-0000:00:14.0-usb-0:2:1.0-scsi-0:0:0:0-part1
S: disk/by-uuid/5556-1F46
E: DEVLINKS=/dev/disk/by-id/usb-LaCie_LaCie_iamaKey_AA1431TTD86BRI6O-0:0-part1
/dev/disk/by-label/KEY
/dev/disk/by-path/pci-0000:00:14.0-usb-0:2:1.0-scsi-0:0:0:0-part1
/dev/disk/by-uuid/5556-1F46
E: DEVNAME=/dev/sde1
E:
DEVPATH=/devices/pci0000:00/0000:00:14.0/usb3/3-2/3-2:1.0/host9/target9:0:0/9:0:0:0/block/sde/sde1
E: DEVTYPE=partition
E: ID_BUS=usb
E: ID_FS_LABEL=KEY
E: ID_FS_LABEL_ENC=KEY
E: ID_FS_TYPE=vfat
E: ID_FS_USAGE=filesystem
E: ID_FS_UUID=5556-1F46
E: ID_FS_UUID_ENC=5556-1F46
E: ID_FS_VERSION=FAT32
E: ID_INSTANCE=0:0
E: ID_MODEL=LaCie_iamaKey
E: ID_MODEL_ENC=LaCie\x20iamaKey\x20\x20\x20
E: ID_MODEL_ID=1027
E: ID_PART_ENTRY_DISK=8:64
E: ID_PART_ENTRY_FLAGS=0x80
E: ID_PART_ENTRY_NUMBER=1
E: ID_PART_ENTRY_OFFSET=2048
E: ID_PART_ENTRY_SCHEME=dos
E: ID_PART_ENTRY_SIZE=7911424
E: ID_PART_ENTRY_TYPE=0xc
E: ID_PART_TABLE_TYPE=dos
E: ID_PATH=pci-0000:00:14.0-usb-0:2:1.0-scsi-0:0:0:0
E: ID_PATH_TAG=pci-0000_00_14_0-usb-0_2_1_0-scsi-0_0_0_0
E: ID_REVISION=1100
E: ID_SERIAL=LaCie_LaCie_iamaKey_AA1431TTD86BRI6O-0:0
E: ID_SERIAL_SHORT=AA1431TTD86BRI6O
E: ID_TYPE=disk
E: ID_USB_DRIVER=usb-storage
E: ID_USB_INTERFACES=:080650:
E: ID_USB_INTERFACE_NUM=00
E: ID_VENDOR=LaCie
E: ID_VENDOR_ENC=LaCie\x20\x20\x20
E: ID_VENDOR_ID=059f
E: MAJOR=8
E: MINOR=65
E: SUBSYSTEM=block
E: TAGS=:systemd:
E: USEC_INITIALIZED=10667167

[reply] [-] Comment 5 Andrey Borzenkov 2013-03-18 16:53:14 UTC

(In reply to comment #4)
> Nope.

Did you reboot after adding rule? Alternatively "udevadm control --reload"
should be enough too.

This rule definitely works for me.

[reply] [-] Comment 6 Aekold Helbrass 2013-03-18 20:50:59 UTC

Yes, it works! Thanx.

The problem was this: I copied my local rules from 70-kpartx.rules and left the
same checks on top (see below), and that was a bad idea. Tell me please, does
leaving anything of those makes any sense, or simple single line will be fine?

KERNEL!="dm-*", GOTO="local_end"
ACTION=="remove", GOTO="local_end"

ENV{DM_TABLE_STATE}!="LIVE", GOTO="local_end"
ENV{DM_ACTION}=="PATH_FAILED|PATH_REINSTATED", GOTO="local_end"
ENV{DM_DEPS}=="0", GOTO="local_end"

[reply] [-] Comment 7 Andrey Borzenkov 2013-03-19 02:38:52 UTC

(In reply to comment #6)
> Yes, it works!

Good. May I ask you to test update RPM from comment 1?

[reply] [-] Comment 8 Rainer Klier 2013-03-21 08:36:05 UTC

(In reply to comment #7)
> (In reply to comment #6)
> > Yes, it works!
>
> Good. May I ask you to test update RPM from comment 1?

i tried the packages from
obs://build.opensuse.org/home:arvidjaar:bnc:809837/standard.

an they work!
without the packages from your repo it did not work!

thanks!

it was annoying to have lost the feature of mounting external drives in /media!

this fix (incl. the required rule with the UDISKS_FILESYSTEM_SHARED switch)
should go into the update-repo.

i think nearly every user want's it that way.

[reply] [-] Comment 9 Andrey Borzenkov 2013-03-21 16:23:53 UTC

(In reply to comment #8)
> i tried the packages from
> obs://build.opensuse.org/home:arvidjaar:bnc:809837/standard.
>
> an they work!
> without the packages from your repo it did not work!
>
> thanks!
>

OK, I'll submit maintenance update.

> the required rule with the UDISKS_FILESYSTEM_SHARED switch)
> should go into the update-repo.
>
No. Providing better configuration possibility is one thing, changing
distribution wide default policy is another. You are welcome to discuss it on
factory list if you think it is required.

@maintenance team: please review SR 160482. The patch is already in factory as
part of udisks2 2.1.0.

[reply] [-] Comment 10 Bernhard Wiedemann 2013-03-21 17:00:26 UTC

This is an autogenerated message for OBS integration:
This bug (809837) was mentioned in
https://build.opensuse.org/request/show/160482 Maintenance /

[reply] [-] Comment 11 Rainer Klier 2013-03-22 07:18:26 UTC

(In reply to comment #9)
> (In reply to comment #8)
> > i tried the packages from
> > obs://build.opensuse.org/home:arvidjaar:bnc:809837/standard.
> >
> OK, I'll submit maintenance update.

thanks.

> > the required rule with the UDISKS_FILESYSTEM_SHARED switch)
> > should go into the update-repo.
> >
> No. Providing better configuration possibility is one thing, changing
> distribution wide default policy is another. You are welcome to discuss it on

but exactly this has been done already!

on 12.2 the default policy was to mount external drives in /media, and on 12.3
it is different.

so, the distribution wide default policy has already been changed.
this fix/change would only revert/correct this to the distribution wide default
policy it was.

anyway, i am happy that i am able now to correct this on my own to the old
behaviour, even if it will not be default now.

> factory list if you think it is required.

i will.

[reply] [-] Comment 12 Andrey Borzenkov 2013-03-22 07:56:57 UTC

(In reply to comment #11)
> on 12.2 the default policy was to mount external drives in /media, and on 12.3
> it is different.

it depends whether udisks or udisks2 were used. On 12.2 KDE used udisks(1) and
GNOME used udisks2 so KDE mounted under /media and GNOME under
/run/media/<user>

[reply] [-] Comment 13 Benjamin Brunner 2013-03-22 11:37:02 UTC

Andrey, thanks for your submission. I started an update see
openSUSE:Maintenance:1477.

[reply] [-] Comment 14 Rainer Klier 2013-03-25 09:20:27 UTC

(In reply to comment #12)
> (In reply to comment #11)
> > on 12.2 the default policy was to mount external drives in /media, and on 12.3
> > it is different.
>
> it depends whether udisks or udisks2 were used. On 12.2 KDE used udisks(1) and
> GNOME used udisks2 so KDE mounted under /media and GNOME under
> /run/media/<user>

ok, thanks for explanation.

understood.

[reply] [-] Comment 15 Benjamin Brunner 2013-03-27 14:15:22 UTC

Update released for openSUSE 12.3. Resolved fixed.

[reply] [-] Comment 16 Swamp Workflow Management 2013-03-27 16:05:01 UTC

openSUSE-RU-2013:0550-1: An update that has one recommended fix can now be
installed.

Category: recommended (low)
Bug References: 809837
CVE References:
Sources used:
openSUSE 12.3 (src): udisks2-2.0.0-5.4.1

[reply] [-] Comment 17 Greg Freemyer 2013-04-01 19:49:08 UTC

For clarity, something like this is still needed by the user to manually
perform:

sudo echo 'ENV{ID_FS_USAGE}=="filesystem|other|crypto",
ENV{UDISKS_FILESYSTEM_SHARED}="1"' >
/etc/udev/rules.d/99-correct-media-mount-point.rules

udevadm control --reload

Make sure the echo command is all on one line.

Also, the user should verify they don't already have a file
/etc/udev/rules.d/99-correct-media-mount-point.rules

[reply] [-] Comment 18 Ruediger Meier 2013-07-20 08:57:52 UTC

(In reply to comment #12)
> (In reply to comment #11)
> > on 12.2 the default policy was to mount external drives in /media, and on 12.3
> > it is different.
>
> it depends whether udisks or udisks2 were used. On 12.2 KDE used udisks(1) and
> GNOME used udisks2 so KDE mounted under /media and GNOME under
> /run/media/<user>

I do not understand why the mount point depend on the used window manager at
all. Now we have random mount points and non-root users can't set what they
want.

For me it happend that I got a media mounted in /var/run/user allthough I was
working on kde3 (udisks-1). Probably because I had also some kde4 or gnome
stuff running. So it's a race where it will be mounted. Introducing this random
mount points was a bug which should be fixed.

BTW I find it really confusing to have udisks 1 and 2 running in parallel by
default. As if the automounting wouldn't be complicated enough ...
 
Old 01-15-2014, 09:38 AM   #6
dbbd
LQ Newbie
 
Registered: Jan 2014
Posts: 1

Rep: Reputation: Disabled
I have the same problem with Unison, latest version: crash after attempt of 1st file selection. I am running Suse 12.3 (Dartmouth) (x86_64).
The problem seems to be with the GTK library. If I run it from a shell, I get :

Gtk-CRITICAL **: gtk_tree_model_filter_get_value: assertion `GTK_TREE_MODEL_FILTER (model)->priv->stamp == iter->stamp' failed

(unison:18687): GLib-GObject-WARNING **: gtype.c:4204: type id `0' is invalid

(unison:18687): GLib-GObject-WARNING **: can't peek value table for type `<invalid>' which is not currently referenced
Segmentation fault

In my case I don't think it has to do with mounted media. I get the same behavior when no media are mounted and I try to select a folder under \home.
Does anybody know how to solve the problem?
Thanks.
 
Old 05-11-2014, 12:06 PM   #7
melb01
LQ Newbie
 
Registered: Apr 2006
Posts: 1

Rep: Reputation: 0
Hi

Same problem after upgrade to Kubuntu 14.04 (32bit) - it ran OK with Kubuntu 12.04

Fails at 'First Directory' selection, irrespective of selection 'File System', mounted partitions and USB devices.

11/05/2014 17:42:39 jeanne2 kernel [37813.974880] unison-2.40.102[4125]: segfault at 18 ip b754c6d3 sp bfeec030 error 4 in libgtk-x11-2.0.so.0.2400.23[b7332000+467000]
11/05/2014 17:54:19 jeanne2 kernel [38513.439149] unison-2.40.102[4267]: segfault at 18 ip b75016d3 sp bfbf6fc0 error 4 in libgtk-x11-2.0.so.0.2400.23[b72e7000+467000]
11/05/2014 17:56:17 jeanne2 kernel [38631.217618] unison-2.40.102[4278]: segfault at 18 ip b754a6d3 sp bffe9f70 error 4 in libgtk-x11-2.0.so.0.2400.23[b7330000+467000]

Mel
 
Old 04-25-2015, 04:37 PM   #8
FSHero
LQ Newbie
 
Registered: Jul 2007
Distribution: Kubuntu Feisty Fawn
Posts: 13

Rep: Reputation: 0
gtk theme issue

I had the same issue as described in the original post when I switched from using kubuntu 12.04 to 14.04.

I ran unison-gtk in a console and noticed the following error message:

Code:
(unison-gtk:4680): Gtk-CRITICAL **: gtk_tree_model_filter_get_value: assertion 'GTK_TREE_MODEL_FILTER (model)->priv->stamp == iter->stamp' failed

(unison-gtk:4680): GLib-GObject-WARNING **: /build/buildd/glib2.0-2.40.2/./gobject/gtype.c:4210: type id '0' is invalid

(unison-gtk:4680): GLib-GObject-WARNING **: can't peek value table for type '<invalid>' which is not currently referenced
Segmentation fault (core dumped)
Googling the first line led me to this bug report, and suggested to change the gtk theme to something other than oxygen-gtk.

This solution worked for me; I hope it helps others too.
 
Old 03-03-2016, 03:43 AM   #9
azzamsa
LQ Newbie
 
Registered: Mar 2016
Posts: 1

Rep: Reputation: Disabled
it works

thanks it works foe me
 
  


Reply



Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
Putty crashes when selecting text to copy m.collingwood Linux - Software 4 03-12-2013 11:17 PM
[SOLVED] Duplicity Backups Do Not Appear in Destination Location scorchgeek Linux - Server 1 05-03-2012 05:38 PM
Downloading files from linux and selecting a samba location on windows buzzer112 Linux - Newbie 3 03-22-2011 07:33 PM
Fedora Installer Crashes after selecting where to install GRUB simonpcook Fedora 2 05-18-2008 07:09 PM
install crashes shen selecting monitor slawdawg Linux - Newbie 5 07-04-2004 02:16 PM

LinuxQuestions.org > Forums > Linux Forums > Linux - Software

All times are GMT -5. The time now is 06:21 AM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration