This is preventing updating the firmware for Logitech's unifying
receiver which has a number of outstanding CVEs that have either been
fixed, or are due to be fixed in August of this year.
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2016-10761
** CVE added: https://cve.mitre.org/
Interesting link about both problems I currently have with log out
functionality including this one.
http://np237.livejournal.com/22014.html
--
[intrepid] no prompt to save open work on shutdown/restart
https://bugs.launchpad.net/bugs/276134
You received this bug notification because you are a m
I can only add my support to the people who think this bug should be of
high importance, nay critical!
I cannot conceive of how anyone can believe that just killing open
processes without any prompt to save outstanding data on shutdown could
ever be acceptable to end users. Spending 2 hours worki
I can confirm the fix too. Doesn't work without nodfs, does with.
--
Access to samba 3.0.24-3.0.25 shares using CIFS is broken on 8.10
https://bugs.launchpad.net/bugs/286828
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bug
@Skokie
Thanks very much for this tip. That's sorted me out nicely.
I've contacted D-Link regarding a firmware fix for this issue and
received the following reply:
"A firmware is being develop, we don't have an ETA or upgrades that it
will have, i invite you to go to forums.dlink.com, you can po
ting. How
does one find out when the release will be.
Regards,
mipper
2008/12/1 Thierry Carrez <[EMAIL PROTECTED]>
> mipper:
> This is a bug about servers claiming they support something that they
> don't. If client stuff makes use of that "something" and trust se
nderstand why fixing this doesn't seem
to be an urgent issue. It wasn't the introduction of anything new on
the server side that caused this problem to arise, it was an update to
the client - or am I still missing something?
Regards,
mipper
> Just to summarize again:
> 1) A fe
Forgive my ignorance here, but I can see that there appears to have been
a fix committed for this bug, but I can't see when or how it's going to
be released. This is an absolute show stopper bug as far as I can see,
so how and when can I get a fix for it?
--
Access to samba 3.0.24-3.0.25 shares
