The sources are mostly same, so the problems are the same.
I submit this bug for debian as well.
Actually this bug present in ubuntu as well. Normally it is low
priority, but it becomes critical if we are using our own grub or any
other efi loader (like refind) with shim.
--
You received this bu
> > This is a low priority bug for ubuntu, cause it has grub2-signed
> > package. But in debian case it becomes problematic as debian has no
> > grub2-signed package.
>
> It doesn't have one *yet*. This is planned.
Yeah, I know. That's why this bug is quite significant.
Currently we should do th
This is a low priority bug for ubuntu, cause it has grub2-signed
package. But in debian case it becomes problematic as debian has no
grub2-signed package. Thus users must use self-compiled monolith grub2
package. Evidently this package is not signed with Debian key, and hence
it can't be loaded.
-
Public bug reported:
[see debian bug #860716 as well]
I test shim-signed with qemu in secure boot environment. Here is the steps
to reproduce a problem:
1) install shim, shim-signed, qemu and ovmf packages
2) get EnrollDefaultKeys.efi from
https://dl.fedoraproject.org/pub/fedora/linux/devel
Hello, smbnetfs delay might be related to libsmbclient name resolution
procedure.
By default libsmbclient tries to resolve names via lmhosts file, dns, wins and
broadcast.
libsmbclient tries each resolution method for each configured network
interface. So the
network name resolution may takes a
ggy libsmbclient code from the
rest of smbnetfs). It was done to get better performance and
stability.
Mikhail Kshevetskiy
> --
> fusesmb/smbnetfs SIGABORT in getattr() because libsmbclient is not thread safe
> https://bugs.launchpad.net/bugs/198351
> You received this bug notification
On Wed, 10 Mar 2010 21:09:58 -
Robert Garshaw wrote:
> Smbnetfs has been fine for me since I upgraded to karmic. But I'm not
> sure if I still have any fixes in place. As far as I'm aware it's all
> stock.
This problem was fixed in smbnetfs-0.5.x.
Use smbnetfs-0.5.
please update SMBNetFS package to latest git version. It does not
contain the bug described here due to libsmbclient isolation in separate
process.
--
fusesmb - Not working properly - SIGABORT in getattr() - libsmbclient not
thread safe
https://bugs.launchpad.net/bugs/198351
You received this bu
*** This bug is a duplicate of bug 198351 ***
https://bugs.launchpad.net/bugs/198351
Please update SMBNetFS to latest git/debian version.
--
crashing with SIGABRT while scanning network or reading some files
https://bugs.launchpad.net/bugs/293233
You received this bug notification because yo
