[Bug 1675698] Re: Cannot access anything under a subdirectory if symlinks are disallowed
Fixes for this have been uploaded to: https://bugzilla.samba.org/show_bug.cgi?id=12721 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1675698 Title: Cannot access anything under a subdirectory if symlinks are disallowed To manage notifications about this bug go to: https://bugs.launchpad.net/samba/+bug/1675698/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 222734] Re: Samba usershares in lower-case
I have fixed this in the upstream tree (see the patch added to Samba bug #7240). Please test the Samba master git branch (as this will become 3.6.0) to ensure it works with nautilus share. Jeremy. -- Samba usershares in lower-case https://bugs.launchpad.net/bugs/222734 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 222734] Re: Samba usershares in lower-case
I have fixed this in the upstream tree (see the patch added to Samba bug #7240). Please test the Samba master git branch (as this will become 3.6.0) to ensure it works with nautilus share. Jeremy. -- Samba usershares in lower-case https://bugs.launchpad.net/bugs/222734 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 198351] Re: fusesmb/smbnetfs SIGABORT in getattr() because libsmbclient is not thread safe
Actually Samba upstream does consider the non-threadsafeness of libsmbclient as a bug, it's just that it's going to take a while to fix it :-). We're slowly but surely moving towards getting a thread safe libsmbclient, Can't promise when it will be done, but it is our intent to get there. So at the moment, libsmbclient is not thread safe. So using separate processes in SMBNetFS is the *only* way to safely use libsmbclient, so I'd argue that libsmbclient in this case isn't exactly buggy, but just not working in the way you want :-). When we finally announce libsmbclient is thread-safe, and your threaded code using it breaks, *then* you can call it buggy :-). But not before please - unless you have specific single-threaded bugs you know about and need fixing. But if that is the case please report them to bugzilla.samba.org and we'll fix them ! Jeremy. -- fusesmb/smbnetfs SIGABORT in getattr() because libsmbclient is not thread safe https://bugs.launchpad.net/bugs/198351 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 198351] Re: fusesmb/smbnetfs SIGABORT in getattr() because libsmbclient is not thread safe
Actually Samba upstream does consider the non-threadsafeness of libsmbclient as a bug, it's just that it's going to take a while to fix it :-). We're slowly but surely moving towards getting a thread safe libsmbclient, Can't promise when it will be done, but it is our intent to get there. So at the moment, libsmbclient is not thread safe. So using separate processes in SMBNetFS is the *only* way to safely use libsmbclient, so I'd argue that libsmbclient in this case isn't exactly buggy, but just not working in the way you want :-). When we finally announce libsmbclient is thread-safe, and your threaded code using it breaks, *then* you can call it buggy :-). But not before please - unless you have specific single-threaded bugs you know about and need fixing. But if that is the case please report them to bugzilla.samba.org and we'll fix them ! Jeremy. -- fusesmb/smbnetfs SIGABORT in getattr() because libsmbclient is not thread safe https://bugs.launchpad.net/bugs/198351 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 222734] Re: Samba usershares in lower-case
I have a fix for this I'm planning to add into 3.6.0. Can't go in earlier as it's going to need an upgrade to the on-disk format of the share security tdb. I'll update this bug once the new code has been tested. Thanks ! Jeremy. -- Samba usershares in lower-case https://bugs.launchpad.net/bugs/222734 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 222734] Re: Samba usershares in lower-case
I have a fix for this I'm planning to add into 3.6.0. Can't go in earlier as it's going to need an upgrade to the on-disk format of the share security tdb. I'll update this bug once the new code has been tested. Thanks ! Jeremy. -- Samba usershares in lower-case https://bugs.launchpad.net/bugs/222734 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 525435] Re: utf-8 characters cause permission denied error
Actually, what we need is a debug level 10 from smbclient (9 isn't good enough) and a wireshark trace of the smbclient connection to the Windows server. Attach them to the samba bug: https://bugzilla.samba.org/show_bug.cgi?id=7241 Jeremy. -- utf-8 characters cause permission denied error https://bugs.launchpad.net/bugs/525435 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 222734] Re: Samba usershares in lower-case
The reason the sharename is lowercased is so we can tell immediately if another usershare exists using a case-variant of the same name (SMB shares are case insensitive). In order to fix this (it's not an issue in the server code as far as I can see) the usershare creation code would have to scan the entire directory to look for case-differing versions of the new sharename, and replace them if needed. Jeremy. -- Samba usershares in lower-case https://bugs.launchpad.net/bugs/222734 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 525435] Re: utf-8 characters cause permission denied error
Actually, what we need is a debug level 10 from smbclient (9 isn't good enough) and a wireshark trace of the smbclient connection to the Windows server. Attach them to the samba bug: https://bugzilla.samba.org/show_bug.cgi?id=7241 Jeremy. -- utf-8 characters cause permission denied error https://bugs.launchpad.net/bugs/525435 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 222734] Re: Samba usershares in lower-case
The reason the sharename is lowercased is so we can tell immediately if another usershare exists using a case-variant of the same name (SMB shares are case insensitive). In order to fix this (it's not an issue in the server code as far as I can see) the usershare creation code would have to scan the entire directory to look for case-differing versions of the new sharename, and replace them if needed. Jeremy. -- Samba usershares in lower-case https://bugs.launchpad.net/bugs/222734 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 294344] Re: Firefox 3.0.3: Program received signal SIGABRT, Aborted.
Try this patch for Samba 3.2.x. If it works I'll commit to all git-trees. Thanks, Jeremy. ** Attachment added: Try this patch for Samba 3.2.x. http://launchpadlibrarian.net/19743629/look -- Firefox 3.0.3: Program received signal SIGABRT, Aborted. https://bugs.launchpad.net/bugs/294344 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 224291] Re: f-spot hangs on exit.
I just tested by removing gnupg-agent, no difference. f-spot still hangs. As I've said before, this looks like a pthread problem in the mono exit code. Jeremy. -- f-spot hangs on exit. https://bugs.launchpad.net/bugs/224291 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 224291] Re: f-spot hangs on exit.
Real-time signals work fine on this system, I use it for developing Samba (which uses RT-signals for file lease notification). ./a.out SIGRTMIN: 34 sigismember(): 0 SIGRT_1 received SIGRT_2 received SIGQUIT received FYI: I hate signal handlers with printf(). Not sig-safe :-). Jeremy. -- f-spot hangs on exit. https://bugs.launchpad.net/bugs/224291 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 224291] Re: f-spot hangs on exit.
Well then you shipped a *completely broken* package as your default photo manager in a long term supported release then (and that isn't even mentioning the printing bug where trying to print via f-spot to any other size than the default just emits the default paper size - yes, this is also somewhere in launchpad). Let's face it, you did *NO* testing on your default photo management package for a long term release. You must fix your QA processes if you want to be taken seriously in the long term. I don't care about your no upstream changes to major frameworks policy - if you're shipping default broken components then your policy needs an update. Jeremy. -- f-spot hangs on exit. https://bugs.launchpad.net/bugs/224291 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 224291] Re: f-spot hangs on exit.
Do *NOT* close this bug. This bug is active on all my 8.04 (fully updated) systems. It is a mono issue connected with pthread termination (I got a confirmation of this from Miguel) and will not be fixed in 8.04 until the mono version in 8.04 is updated. Jeremy. -- f-spot hangs on exit. https://bugs.launchpad.net/bugs/224291 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 248358] Re: Paper size setting for HP Photosmart D7200 doesn't work
This wasted an afternoon for me I should have spent working on Samba ! I'm irritated. f-spot is my primary photo management application and the 8.04 release has *two* critical bugs. The mono bug w.r.t. freezing on exit on multicore machines: https://bugs.launchpad.net/ubuntu/+bug/224291 and now this ! I set up multiple print queues, one for each paper size and it took me a long time to work out that f-spot printing was always emitting letter size (or A4, I'm guessing it's the default paper size defined on the system). A default photo application that won't print photos is worse than useless. Who does the QA on this before release ? This is a long-term supported release - I think the solution is to upgrade the f-spot version in Hardy asap to one that will correctly set the paper size. Who do I annoy to get this done ? Or is this another subject I should pass onto the Linux-hater's blog :-). I can't recommend Ubuntu for new Linux users until bugs like this are caught *before* release. I could understand if f-spot were a secondary photo package, but this is the *default* photo management app, and it's normally a damn good one. Please fix this asap. Jeremy. -- Paper size setting for HP Photosmart D7200 doesn't work https://bugs.launchpad.net/bugs/248358 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 224291] Re: f-spot hangs on exit.
Just upgraded to mono 1.9.1 from the .deb package at the mono site. Still hangs in f-spot exit, no change. Jeremy. -- f-spot hangs on exit. https://bugs.launchpad.net/bugs/224291 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 224291] Re: f-spot hangs on exit.
Interestingly enough this doesn't now look f-spot related. If I try and quit the mdb session this also hangs in the same way. Looks to me that mono isn't terminating processes containing threads correctly on this system. Jeremy. -- f-spot hangs on exit. https://bugs.launchpad.net/bugs/224291 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 224291] Re: f-spot hangs on exit.
Here is a (long) gdb backtrace of attaching to the mono binary once f-spot is in this hung state. It's hanging on a pthread_cond_timedwait syscall. Hopefully this helps. Mono debugger output to follow. Jeremy. --- gdb /usr/bin/mono GNU gdb 6.8-debian Copyright (C) 2008 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later http://gnu.org/licenses/gpl.html This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type show copying and show warranty for details. This GDB was configured as i486-linux-gnu... (no debugging symbols found) (gdb) attach 4011 Attaching to program: /usr/bin/mono, process 4011 Reading symbols from /usr/lib/libgthread-2.0.so.0...(no debugging symbols found)...done. Loaded symbols for /usr/lib/libgthread-2.0.so.0 Reading symbols from /lib/tls/i686/cmov/librt.so.1...Reading symbols from /usr/lib/debug/lib/tls/i686/cmov/librt-2.7.so...(no debugging symbols found)...done. (no debugging symbols found)...done. Loaded symbols for /lib/tls/i686/cmov/librt.so.1 Reading symbols from /usr/lib/libglib-2.0.so.0... (no debugging symbols found)...done. Loaded symbols for /usr/lib/libglib-2.0.so.0 Reading symbols from /lib/tls/i686/cmov/libdl.so.2...Reading symbols from /usr/lib/debug/lib/tls/i686/cmov/libdl-2.7.so...(no debugging symbols found)...done. (no debugging symbols found)...done. Loaded symbols for /lib/tls/i686/cmov/libdl.so.2 Reading symbols from /lib/tls/i686/cmov/libpthread.so.0...Reading symbols from /usr/lib/debug/lib/tls/i686/cmov/libpthread-2.7.so... (no debugging symbols found)...done. [Thread debugging using libthread_db enabled] [New Thread 0xb7c50940 (LWP 4011)] [New Thread 0xb2770b90 (LWP 4034)] [New Thread 0xb2875b90 (LWP 4033)] [New Thread 0xb3ea6b90 (LWP 4014)] [New Thread 0xb71f8b90 (LWP 4013)] [New Thread 0xb777bb90 (LWP 4012)] (no debugging symbols found)...done. Loaded symbols for /lib/tls/i686/cmov/libpthread.so.0 Reading symbols from /lib/tls/i686/cmov/libm.so.6...Reading symbols from /usr/lib/debug/lib/tls/i686/cmov/libm-2.7.so...(no debugging symbols found)...done. (no debugging symbols found)...done. Loaded symbols for /lib/tls/i686/cmov/libm.so.6 Reading symbols from /lib/tls/i686/cmov/libc.so.6...Reading symbols from /usr/lib/debug/lib/tls/i686/cmov/libc-2.7.so...(no debugging symbols found)...done. (no debugging symbols found)...done. Loaded symbols for /lib/tls/i686/cmov/libc.so.6 Reading symbols from /lib/libselinux.so.1... (no debugging symbols found)...done. Loaded symbols for /lib/libselinux.so.1 Reading symbols from /lib/ld-linux.so.2...Reading symbols from /usr/lib/debug/lib/ld-2.7.so...(no debugging symbols found)...done. (no debugging symbols found)...done. Loaded symbols for /lib/ld-linux.so.2 Reading symbols from /usr/lib/libpcre.so.3... (no debugging symbols found)...done. Loaded symbols for /usr/lib/libpcre.so.3 Reading symbols from /lib/tls/i686/cmov/libnss_compat.so.2...Reading symbols from /usr/lib/debug/lib/tls/i686/cmov/libnss_compat-2.7.so...(no debugging symbols found)...done. (no debugging symbols found)...done. Loaded symbols for /lib/tls/i686/cmov/libnss_compat.so.2 Reading symbols from /lib/tls/i686/cmov/libnsl.so.1...Reading symbols from /usr/lib/debug/lib/tls/i686/cmov/libnsl-2.7.so... (no debugging symbols found)...done. (no debugging symbols found)...done. Loaded symbols for /lib/tls/i686/cmov/libnsl.so.1 Reading symbols from /lib/tls/i686/cmov/libnss_nis.so.2...Reading symbols from /usr/lib/debug/lib/tls/i686/cmov/libnss_nis-2.7.so...(no debugging symbols found)...done. (no debugging symbols found)...done. Loaded symbols for /lib/tls/i686/cmov/libnss_nis.so.2 Reading symbols from /lib/tls/i686/cmov/libnss_files.so.2...Reading symbols from /usr/lib/debug/lib/tls/i686/cmov/libnss_files-2.7.so...(no debugging symbols found)...done. (no debugging symbols found)...done. Loaded symbols for /lib/tls/i686/cmov/libnss_files.so.2 Reading symbols from /usr/lib/libgconf-2.so.4... (no debugging symbols found)...done. Loaded symbols for /usr/lib/libgconf-2.so.4 Reading symbols from /usr/lib/libgmodule-2.0.so.0...(no debugging symbols found)...done. Loaded symbols for /usr/lib/libgmodule-2.0.so.0 Reading symbols from /usr/lib/libORBit-2.so.0...(no debugging symbols found)...done. Loaded symbols for /usr/lib/libORBit-2.so.0 Reading symbols from /usr/lib/libgobject-2.0.so.0... (no debugging symbols found)...done. Loaded symbols for /usr/lib/libgobject-2.0.so.0 Reading symbols from /usr/lib/mono/gtk-sharp-2.0/libglibsharpglue-2.so...(no debugging symbols found)...done. Loaded symbols for /usr/lib/mono/gtk-sharp-2.0/libglibsharpglue-2.so Reading symbols from /usr/lib/libMonoPosixHelper.so...(no debugging symbols found)...done. Loaded symbols for /usr/lib/libMonoPosixHelper.so Reading symbols from /usr/lib/libz.so.1... (no debugging symbols found)...done.
[Bug 224291] Re: f-spot hangs on exit.
And here is f-spot being run under the mono debugger. Once it hung on exit I ^C'ed the debugger and got a backtrace. Hope this helps. Looks like the damn thing is in the final stages of exit cleaning up the pthreads it created for itself (which is consistent with the gdb trace above). Now, the question is *why*... Jeremy. mdb /usr/lib/f-spot/f-spot.exe Mono Debugger (mdb) run Starting program: /usr/lib/f-spot/f-spot.exe Cannot load symbol file `/usr/lib/f-spot/f-spot.exe.mdb': Could not find file /usr/lib/f-spot/f-spot.exe.mdb. Cannot load symbol file `/usr/lib/f-spot/f-spot.exe.mdb' Cannot load symbol file `/usr/lib/mono/gac/glib-sharp/2.12.0.0__35e10195dab3c99f/glib-sharp.dll.mdb': Could not find file /usr/lib/mono/gac/glib-sharp/2.12.0.0__35e10195dab3c99f/glib-sharp.dll.mdb. Cannot load symbol file `/usr/lib/mono/gac/glib-sharp/2.12.0.0__35e10195dab3c99f/glib-sharp.dll.mdb' Cannot load symbol file `/usr/lib/mono/gac/gnome-sharp/2.20.0.0__35e10195dab3c99f/gnome-sharp.dll.mdb': Could not find file /usr/lib/mono/gac/gnome-sharp/2.20.0.0__35e10195dab3c99f/gnome-sharp.dll.mdb. Cannot load symbol file `/usr/lib/mono/gac/gnome-sharp/2.20.0.0__35e10195dab3c99f/gnome-sharp.dll.mdb' Cannot load symbol file `/usr/lib/mono/gac/Mono.Addins.Setup/0.3.0.0__0738eb9f132ed756/Mono.Addins.Setup.dll.mdb': Could not find file /usr/lib/mono/gac/Mono.Addins.Setup/0.3.0.0__0738eb9f132ed756/Mono.Addins.Setup.dll.mdb. Cannot load symbol file `/usr/lib/mono/gac/Mono.Addins.Setup/0.3.0.0__0738eb9f132ed756/Mono.Addins.Setup.dll.mdb' Cannot load symbol file `/usr/lib/mono/gac/gtk-sharp/2.12.0.0__35e10195dab3c99f/gtk-sharp.dll.mdb': Could not find file /usr/lib/mono/gac/gtk-sharp/2.12.0.0__35e10195dab3c99f/gtk-sharp.dll.mdb. Cannot load symbol file `/usr/lib/mono/gac/gtk-sharp/2.12.0.0__35e10195dab3c99f/gtk-sharp.dll.mdb' Cannot load symbol file `/usr/lib/mono/gac/atk-sharp/2.12.0.0__35e10195dab3c99f/atk-sharp.dll.mdb': Could not find file /usr/lib/mono/gac/atk-sharp/2.12.0.0__35e10195dab3c99f/atk-sharp.dll.mdb. Cannot load symbol file `/usr/lib/mono/gac/atk-sharp/2.12.0.0__35e10195dab3c99f/atk-sharp.dll.mdb' Cannot load symbol file `/usr/lib/f-spot/FSpot.Core.dll.mdb': Could not find file /usr/lib/f-spot/FSpot.Core.dll.mdb. Cannot load symbol file `/usr/lib/f-spot/FSpot.Core.dll.mdb' Cannot load symbol file `/usr/lib/f-spot/Cms.dll.mdb': Could not find file /usr/lib/f-spot/Cms.dll.mdb. Cannot load symbol file `/usr/lib/f-spot/Cms.dll.mdb' Cannot load symbol file `/usr/lib/mono/gac/Mono.Addins/0.3.0.0__0738eb9f132ed756/Mono.Addins.dll.mdb': Could not find file /usr/lib/mono/gac/Mono.Addins/0.3.0.0__0738eb9f132ed756/Mono.Addins.dll.mdb. Cannot load symbol file `/usr/lib/mono/gac/Mono.Addins/0.3.0.0__0738eb9f132ed756/Mono.Addins.dll.mdb' Cannot load symbol file `/usr/lib/mono/gac/gnome-vfs-sharp/2.20.0.0__35e10195dab3c99f/gnome-vfs-sharp.dll.mdb': Could not find file /usr/lib/mono/gac/gnome-vfs-sharp/2.20.0.0__35e10195dab3c99f/gnome-vfs-sharp.dll.mdb. Cannot load symbol file `/usr/lib/mono/gac/gnome-vfs-sharp/2.20.0.0__35e10195dab3c99f/gnome-vfs-sharp.dll.mdb' Cannot load symbol file `/usr/lib/mono/gac/gdk-sharp/2.12.0.0__35e10195dab3c99f/gdk-sharp.dll.mdb': Could not find file /usr/lib/mono/gac/gdk-sharp/2.12.0.0__35e10195dab3c99f/gdk-sharp.dll.mdb. Cannot load symbol file `/usr/lib/mono/gac/gdk-sharp/2.12.0.0__35e10195dab3c99f/gdk-sharp.dll.mdb' Cannot load symbol file `/usr/lib/f-spot/FSpot.Utils.dll.mdb': Could not find file /usr/lib/f-spot/FSpot.Utils.dll.mdb. Cannot load symbol file `/usr/lib/f-spot/FSpot.Utils.dll.mdb' Cannot load symbol file `/usr/lib/mono/gac/gconf-sharp/2.20.0.0__35e10195dab3c99f/gconf-sharp.dll.mdb': Could not find file /usr/lib/mono/gac/gconf-sharp/2.20.0.0__35e10195dab3c99f/gconf-sharp.dll.mdb. Cannot load symbol file `/usr/lib/mono/gac/gconf-sharp/2.20.0.0__35e10195dab3c99f/gconf-sharp.dll.mdb' Thread @1 caught exception at #0: 0xb75c9faf in FSpot.Driver:Main (string[])+0x7af at 347. 347 IL_0409: pop (mdb) c Starting new FSpot server Process #1 created new thread @4. Process #1 created new thread @5. Thread @5 exited normally. Thread @5 exited. Process #1 created new thread @6. Thread @6 exited normally. Thread @6 exited. Cannot load symbol file `/usr/lib/mono/gac/gtkhtml-sharp/3.16.0.0__35e10195dab3c99f/gtkhtml-sharp.dll.mdb': Could not find file /usr/lib/mono/gac/gtkhtml-sharp/3.16.0.0__35e10195dab3c99f/gtkhtml-sharp.dll.mdb. Cannot load symbol file `/usr/lib/mono/gac/gtkhtml-sharp/3.16.0.0__35e10195dab3c99f/gtkhtml-sharp.dll.mdb' Cannot load symbol file `/usr/lib/mono/gac/glade-sharp/2.12.0.0__35e10195dab3c99f/glade-sharp.dll.mdb': Could not find file /usr/lib/mono/gac/glade-sharp/2.12.0.0__35e10195dab3c99f/glade-sharp.dll.mdb. Cannot load symbol file `/usr/lib/mono/gac/glade-sharp/2.12.0.0__35e10195dab3c99f/glade-sharp.dll.mdb' Cannot load symbol file
[Bug 224291] Re: f-spot hangs on exit.
Yes I meant File - Quit. I tried with a .gnome2/f-spot directory and also after removing the directory - same problem. This is with an upgrade from 7.10, not a fresh install. It's 100% reproducible for me. How do I get mono to give me debug information on the lock states inside it. I tried using f-spot --debug but got no extra output. Jeremy. -- f-spot hangs on exit. https://bugs.launchpad.net/bugs/224291 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 224291] Re: f-spot hangs on exit.
Crap, just checked with [EMAIL PROTECTED] and he can't reproduce the problem either. Means I'll have to track this thing down myself. Ok - how do I debug mono apps ? Can you give me any clues on how to find a deadlock ? Jeremy. -- f-spot hangs on exit. https://bugs.launchpad.net/bugs/224291 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 224291] [NEW] f-spot hangs on exit.
Public bug reported:
Binary package hint: mono
Description:Ubuntu 8.04
Release:8.04
Package: f-spot: /usr/bin/f-spot
To reproduce. Upgraded installation. Start f-spot (either from the command line
or a menu). Wait for the initial window to appear. Click on File - Exit. The
application hangs. stracing it shows it stuck in a futex wait. Looks like a
mono locking issue to me.
100% reproducible. This is a blocker bug for me to upgrade all my
desktop machines (f-spot is my primary photo manager).
strace output when in hung state (endlessly loops):
gettimeofday({1209483989, 221562}, NULL) = 0
clock_gettime(CLOCK_REALTIME, {1209483989, 221663850}) = 0
futex(0x8207aa4, 0x80 /* FUTEX_??? */, 51) = -1 ETIMEDOUT (Connection timed out)
futex(0x8207a80, 0x81 /* FUTEX_??? */, 1) = 0
semop(131074, 0xbf835a66, 1)= 0
time(NULL) = 1209483989
time(NULL) = 1209483989
time(NULL) = 1209483989
time(NULL) = 1209483989
time(NULL) = 1209483989
time(NULL) = 1209483989
semop(131074, 0xbf835a76, 1)= 0
semop(131074, 0xbf835a66, 1)= 0
time(NULL) = 1209483989
time(NULL) = 1209483989
time(NULL) = 1209483989
time(NULL) = 1209483989
time(NULL) = 1209483989
time(NULL) = 1209483989
semop(131074, 0xbf835a76, 1)= 0
gettimeofday({1209483989, 322863}, NULL) = 0
clock_gettime(CLOCK_REALTIME, {1209483989, 322973699}) = 0
futex(0x8207aa4, 0x80 /* FUTEX_??? */, 53 unfinished ...
Let me know what more you need to track this down. Note this is *NOT*
the same as the previously reported f-spot crashes on exit segv bugs
reported, this is a hang.
Jeremy.
** Affects: mono (Ubuntu)
Importance: Undecided
Status: New
--
f-spot hangs on exit.
https://bugs.launchpad.net/bugs/224291
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
