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 sy
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 noti
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 t
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/bug
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 th
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
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
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
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
Bu
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 somewher
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://b
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
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.
--
ubunt
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 q
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.
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
Yo
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
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 usin
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
applic
19 matches
Mail list logo
