f-spot crashes when started in guest session mode

Getting this instead of starting f-spot in guest session mode:

guest@phoenix49-emu:~$ f-spot

** (/usr/lib/f-spot/f-spot.exe:9534): CRITICAL **: _wapi_shm_attach: mmap error: Permission denied
**
ERROR:shared.c:346:shm_semaphores_init: assertion failed: (tmp_shared != NULL)

** (/usr/lib/f-spot/f-spot.exe:9534): WARNING **: Thread (nil) may have been prematurely finalized
Stacktrace:

** (/usr/lib/f-spot/f-spot.exe:9534): WARNING **: Thread (nil) may have been prematurely finalized

** (/usr/lib/f-spot/f-spot.exe:9534): WARNING **: Thread (nil) may have been prematurely finalized

Native stacktrace:

f-spot [0x817b4ae]
[0xb7f14410]
/lib/tls/i686/cmov/libc.so.6(abort+0x188) [0xb7cb0248]
/usr/lib/libglib-2.0.so.0(g_assertion_message+0x123) [0xb7e84b73]
/usr/lib/libglib-2.0.so.0 [0xb7e8509d]
f-spot [0x8123b44]
f-spot [0x8115563]
f-spot(mono_once+0x6b) [0x811e58b]
f-spot [0x8115298]
f-spot [0x8122710]
f-spot [0x80d9aa3]
f-spot(mono_runtime_init+0x2d) [0x80e0c1d]
f-spot [0x8142c8d]
f-spot(mono_main+0x345) [0x805ac65]
f-spot [0x805a432]
/lib/tls/i686/cmov/libc.so.6(__libc_start_main+0xe5) [0xb7c99685]
f-spot [0x805a371]

Debug info from gdb:

(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0xb7c576d0 (LWP 9534)]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
0xb7f14422 in __kernel_vsyscall ()
  1 Thread 0xb7c576d0 (LWP 9534) 0xb7f14422 in __kernel_vsyscall ()

Thread 1 (Thread 0xb7c576d0 (LWP 9534)):
#0 0xb7f14422 in __kernel_vsyscall ()
#1 0xb7d5cbcd in select () from /lib/tls/i686/cmov/libc.so.6
#2 0xb7e9698b in g_spawn_sync () from /usr/lib/libglib-2.0.so.0
#3 0xb7e96d3c in g_spawn_command_line_sync () from /usr/lib/libglib-2.0.so.0
#4 0x0817b565 in ?? ()
#5 <signal handler called>
#6 0xb7f14422 in __kernel_vsyscall ()
#7 0xb7cae880 in raise () from /lib/tls/i686/cmov/libc.so.6
#8 0xb7cb0248 in abort () from /lib/tls/i686/cmov/libc.so.6
#9 0xb7e84b73 in g_assertion_message () from /usr/lib/libglib-2.0.so.0
#10 0xb7e8509d in g_assertion_message_expr () from /usr/lib/libglib-2.0.so.0
#11 0x08123b44 in ?? ()
#12 0x08115563 in ?? ()
#13 0x0811e58b in mono_once ()
#14 0x08115298 in ?? ()
#15 0x08122710 in ?? ()
#16 0x080d9aa3 in ?? ()
#17 0x080e0c1d in mono_runtime_init ()
#18 0x08142c8d in ?? ()
#19 0x0805ac65 in mono_main ()
#20 0x0805a432 in ?? ()
#21 0xb7c99685 in __libc_start_main () from /lib/tls/i686/cmov/libc.so.6
#22 0x0805a371 in ?? ()
#0 0xb7f14422 in __kernel_vsyscall ()

=================================================================
Got a SIGABRT while executing native code. This usually indicates
a fatal error in the mono runtime or one of the native libraries
used by your application.
=================================================================

Aborted (core dumped)
guest@phoenix49-emu:~$

Same with tomboy application. Looks like mono related problem

Thank you for the bug report. I was able to confirm this issue on intrepid. It does indeed seem to be triggered with all mono related applications.

Ok, bug must be reassigned to apparmor or gdm-guest-session

/etc/apparmor.d/gdm-guest-session - this blocks f-spot and all other mono apps from running properly

The file /etc/apparmor.d/gdm-guest-session is provided by the package gdm-guest-session so I've added gdm-guest-session as an affected package.

Fixed in trunk and intrepid branches:

  http://bazaar.launchpad.net/~pitti/%2Bjunk/gdm-guest-session/revision/20

I uploaded a fix to intrepid-proposed, will be accepted after Intrepid releases.

I can confirm, that this issue is fixed in trunk. Thank you!

Accepted into intrepid-proposed, please test and give feedback here. Please see https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you in advance!

I can confirm that this update fixes the issue, however, it would be better to reload apparmor, to re-read config data, or ask user to restart the system.

Copied intrepid-proposed version to jaunty.

F-spot is able to start in a guest session now, but I cannot import any pictures. The Import button is greyed out. Could this be a policy issue??

Tux, works fine for me. It is only greyed out while there is no import source selected. Maybe that's what happened for you? Did you actually plug in a camera?

I did not plugin a camera, but selected the directory "Pictures" which
contained pictures. When selecting that directory, the import button
stayed greyed out. So I could not import pictures into f-spot.

2008/11/4 Martin Pitt <email address hidden>:
> Tux, works fine for me. It is only greyed out while there is no import
> source selected. Maybe that's what happened for you? Did you actually
> plug in a camera?
>
> --
> f-spot crashes when started in guest session mode
> https://bugs.launchpad.net/bugs/288682
> You received this bug notification because you are a direct subscriber
> of the bug.
>

I can confirm, that Import is greyed out. Also tried adding sample picture to folder, but still, couldn't import anything.

Actually, f-spot first loads folder contents of selected directory, and after that Import button is being activated. The problem may be related to listing and loading directory contents, and may relate to apparmor.

P.S. Under usual account, subj works correctly.

Right, the import button will stay grayed out until you actually
select a folder with some photos in it, and select photos to import.
Otherwise there isn't anything to import :) This behaves exactly the
same way for me under my normal user and the guest account.

I again tried to import some photos into f-spot under the guest
account, and it worked fine.

Where did you try to import from? If you still have troubles, please
send /var/log/kern.log after a failed attempt.

Said Babayev [2008-11-05 6:19 -0000]:
> Actually, f-spot first loads folder contents of selected directory, and
> after that Import button is being activated. The problem may be related
> to listing and loading directory contents, and may relate to apparmor.

That would be the case if the directory is not under /media or /tmp/,
but for example under /home/. In this case the default profile
doesn't allow access, which is deliberate.

Copied to intrepid-updates.

Assuming that guest sessions "home folder" is under /tmp, then this case is
technically normal, but practically, guest still can't use f-spot importing
features, e.g. just to insert his camera, import and view his pictures.

Regards,
Said
Spike Milligan - "My Father had a profound influence on me, he was a
lunatic."

On Wed, Nov 5, 2008 at 11:15 AM, Martin Pitt <email address hidden> wrote:

> Said Babayev [2008-11-05 6:19 -0000]:
> > Actually, f-spot first loads folder contents of selected directory, and
> > after that Import button is being activated. The problem may be related
> > to listing and loading directory contents, and may relate to apparmor.
>
> That would be the case if the directory is not under /media or /tmp/,
> but for example under /home/. In this case the default profile
> doesn't allow access, which is deliberate.
>
> --
> f-spot crashes when started in guest session mode
> https://bugs.launchpad.net/bugs/288682
> You received this bug notification because you are a direct subscriber
> of the bug.
>

My bad. Memory sticks,flash drives,cameras are usually mounted under
/media,so f-spot should be able to import them :-)
thanks!

On 11/5/08, Said <email address hidden> wrote:
> Assuming that guest sessions "home folder" is under /tmp, then this case is
> technically normal, but practically, guest still can't use f-spot importing
> features, e.g. just to insert his camera, import and view his pictures.
>
> Regards,
> Said
> Spike Milligan - "My Father had a profound influence on me, he was a
> lunatic."
>
> On Wed, Nov 5, 2008 at 11:15 AM, Martin Pitt <email address hidden> wrote:
>
>> Said Babayev [2008-11-05 6:19 -0000]:
>> > Actually, f-spot first loads folder contents of selected directory, and
>> > after that Import button is being activated. The problem may be related
>> > to listing and loading directory contents, and may relate to apparmor.
>>
>> That would be the case if the directory is not under /media or /tmp/,
>> but for example under /home/. In this case the default profile
>> doesn't allow access, which is deliberate.
>>
>> --
>> f-spot crashes when started in guest session mode
>> https://bugs.launchpad.net/bugs/288682
>> You received this bug notification because you are a direct subscriber
>> of the bug.
>>
>

--
Sent from my mobile device

Regards,
Said

Ok, it works for me now. If I select a folder with pictures in it,
then I don't have to select anything. The "Import" button changes from
greyed out to clickable when fspot finds pictures which I can import
into fspot.

Tux

2008/11/5 Said Babayev <email address hidden>:
> My bad. Memory sticks,flash drives,cameras are usually mounted under
> /media,so f-spot should be able to import them :-)
> thanks!
>
> On 11/5/08, Said <email address hidden> wrote:
>> Assuming that guest sessions "home folder" is under /tmp, then this case is
>> technically normal, but practically, guest still can't use f-spot importing
>> features, e.g. just to insert his camera, import and view his pictures.
>>
>> Regards,
>> Said
>> Spike Milligan - "My Father had a profound influence on me, he was a
>> lunatic."
>>
>> On Wed, Nov 5, 2008 at 11:15 AM, Martin Pitt <email address hidden> wrote:
>>
>>> Said Babayev [2008-11-05 6:19 -0000]:
>>> > Actually, f-spot first loads folder contents of selected directory, and
>>> > after that Import button is being activated. The problem may be related
>>> > to listing and loading directory contents, and may relate to apparmor.
>>>
>>> That would be the case if the directory is not under /media or /tmp/,
>>> but for example under /home/. In this case the default profile
>>> doesn't allow access, which is deliberate.
>>>
>>> --
>>> f-spot crashes when started in guest session mode
>>> https://bugs.launchpad.net/bugs/288682
>>> You received this bug notification because you are a direct subscriber
>>> of the bug.
>>>
>>
>
> --
> Sent from my mobile device
>
> Regards,
> Said
>
> --
> f-spot crashes when started in guest session mode
> https://bugs.launchpad.net/bugs/288682
> You received this bug notification because you are a direct subscriber
> of the bug.
>

Also affects me on Ubuntu 10.04. Maybe this is caused by the switch to GDM2, because the fix for intrepid doesn't work in lucid.