I have Ubuntu 14.04 on two Samsung notebooks: a Series 9, model
NP900X4B-A02US ,and an ATIV Book 9 2014 Edition, model NP940X5J-K02US.
In the NP940X5J, Ubuntu is running with UEFI enabled. I confirm that
Kieran Clancy's solution works on that notebook.
In the NP900X4B, Ubuntu is running with UEF
Keyboard backlight does not work in my Samsung NP900X4B as well. I am
running Ubuntu 14.04 LTS with UEFI disabled.
The strange thing is that I had it working on my first installation of
Ubuntu on this notebook. I was running Ubuntu 12.04 at that time. Later
on, when I upgraded Ubuntu to 13.04, key
Same thing here, I ran into this bug when attempting to burn an audio
CD. I also had only MP3 files in the list of files to burn.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to brasero in Ubuntu.
https://bugs.launchpad.net/bugs/1200876
After I replaced network-manager with wicd on 12.10 everything works
perfectly. Now shutdown is much faster -- no delays at all. And I got
rid of the hacked init scripts that I was using to circumvent the bug.
Thanks for mentioning wicd, Russell.
--
You received this bug notification because you
Thanks again Russell. I'm upgrading to 3.5.0-26. It's good to know that
the upgrade won't break the workarounds.
And of course I agree with Ernest that a proper fix for this bug would
be very much appreciated.
--
You received this bug notification because you are a member of Desktop
Packages, wh
Does anybody know if the workarounds posted here remain effective after
a kernel upgrade to 3.5.0-26?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1073433
Title:
Ext4 corrup
Thanks Russel. I will upgrade to 3.5.0-25.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1073433
Title:
Ext4 corruption associated with shutdown of Ubuntu 12.10
Status in Up
Does anybody know if the workarounds at #10 and #13 (or the suggestion
at #57 and #61, or the one at #60) remain effective after a kernel
upgrade to 3.5.0-25?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
http
Hi Russel,
With Sandor's hack (see #57 and #61, or, alternatively, #60) you do not
even need to uncheck "Available to all users", as the shutdown and
startup scripts take care of disabling and enabling the NM.
--
You received this bug notification because you are a member of Desktop
Packages, wh
For people who need to live with this bug, it might be good to stress
that Sandor' s suggestion (#57 and #61) and my little hack (#60) rely on
the workaround at #13, which is effective with kernel 3.5.0-23-generic
(the current kernel in Ubuntu 12.10), but not with kernel
3.5.0-22-generic (the previ
Thanks Sandor. I did something similar, but in /etc/init. (See #60.)
Your comment (at #57) was very helpful!
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1073433
Title:
Ext
Today I' ve seen an improvement in Quantal: the workaround suggested at
#13 resumed working after I got a kernel update from 3.5.0-22-generic to
3.5.0-23-generic.
Per Sandor' s suggestion, I have added to /etc/init two files that
relieve me from the burden of manually disabling/enabling the netwo
Hi Sandor,
Where exactly did you add the calls to nmcli?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1073433
Title:
Ext4 corruption associated with shutdown of Ubuntu 12.1
Clint,
Here is the file last-shutdown-lsof I obtained per your instructions. It
was generated on Quantal, with "Enable Networking" unchecked before
shutdown.
My list of open files looks different from Russell's one. I do not have
entries for dhcp, but I do have entries for modem-manager.
** Att
The thing actually got worse in Quantal, as the workaround become ineffective
after a recently update. Now fsck runs on each and every boot, even if "Enable
Networking" is unchecked before shutdown.
Is anybody else seeing this behavior?
This is the Quantal kernel I am currently running:
$ una
I ran into this bug and confirm it that the suggested workaround is
effective. The problem does not show up if I uncheck "Enable Networking"
before shutting the system down.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager
16 matches
Mail list logo
