Thanks for explaining the larger problem here. It's a bit frustrating
that this bug has existed for more than 9 years, (it seems the original
fix was put in in 2011), but it's taken this long to finally swat it.
Sounds like we're finally on the right path to getting this fixed.
Thanks again.
--
Is there something I can do to expedite this? I submitted a bug that
wound up being a duplicate of this one, and even created and tested a
patch to the config. The config change is pretty trivial, and worked
perfectly in my testing. I'm not sure why this wouldn't be considered a
permanent fix ra
*** This bug is a duplicate of bug 1532264 ***
https://bugs.launchpad.net/bugs/1532264
odd, I didn't notice anything broken. It appears to work just fine.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to the bug report.
https://bugs.launc
A little research reveals that this _was_ actually fixed in 2011, but a
config option needs to be added to enable it.
I've tested the config change, and it works perfectly on 20.04.1 LTS
This is as simple as setting:
auth_self_keep
inside the auth_self_keep section.
(or see patch)
Can this be
This is sad. Thanks for finding that initial bug trace.
Tracing this back (it seems to go back further than just gnome 2 years
ago), it's a known problem going back 9 years, and the meta-issue seems
to be a combination of finger-pointing, and "Well THAT'S not a real
security bug because."
I'
Thanks Christopher.
It still seems to me that Ubuntu should simply remove all unsupported
PPAs as a matter of maintaining stability. I don't recall installing
Jupiter a year ago, but I suppose I must have at some point.
At the very least it'd be nice to have the option of simply doing a
fresh in
Jupter seems to be no longer maintained, but yet it wasn't removed when
I upgraded. Christopher, do you know how I'd go about contacting
someone so this package is automatically removed when a user upgrades
from 12.04 to 14.04? It's caused quite a few people quite a lot of
headaches, and hasn't b
After further testing, I still had the same bug under my original 12.04
PP kernel. I then discovered everything worked fine when I close the
laptop without being logged in. That meant a userland program was
responsible likely involved. I removed a program (I believed installed
be default) called
I've tested 3.17.0-031700rc2.201408251935 and confirmed it still exists
on this kernel.
** Tags added: kernel-bug-exists-upstream kernel-bug-exists-
upstream-3.17-rc2
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a mem
Public bug reported:
After suspending, my x230 laptop only occasionally restarts the wifi
card. The wifi light on the laptop fails to come on. Reboot fixes
this, as does closing the laptop and trying again to resume.
I've also tried the following kernel with the same results:
3.14.0-031400.201
Oh, I should mention this worked perfectly on the 12.04
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1363577
Title:
Resume didn't start wifi card on Lenovo x230 Thinkpad
To manage notifications ab
Running the -40 kernel right now with no issues. Previously in locked
up right away. I turned off the wireless and turned it back on again
with no issues.
Looks like this is fixed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
htt
Is anything going to happen on this bug? The x230 is supposed to be
"certified" on Ubuntu, which is the reason I bought it. Now it's
crashing on the latest kernel release but I've heard nothing for 2
weeks.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
I should also add if I turn off the wireless, the machine boots. As
soon as I turn on the wireless, kernel panic. I managed a screenshot
taken with my phone. It's mostly legible.
** Attachment added: "kernel panic of x230 from wireless card on kernel
2.8.0-38"
https://bugs.launchpad.net/ub
I'm having this same problem with the same symptoms on the x230. Also
crashes on 3.8.0-38. Going back to 3.8.0-36 works.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1289429
Title:
rtl8192ce kern
I had a very similar error after cloning a machine and trying restart
either one of them. My problem seemed to be related to sharing the CD-
ROM drive. I noticed any new machine I created would boot, but the
original and its clone would not.
Here's what I did to fix my problem:
Go into the hard
16 matches
Mail list logo
