This is my lspci and in my case if i switch from wl to brcmsmac i
haven't any other problem.
** Attachment added: lspci
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1062077/+attachment/3422260/+files/lspci
--
You received this bug notification because you are a member of Ubuntu
I have the same issue.
Steps to reproduce:
1. Starting up to Unity
2. Switch to tty1 (Strg + Alt + F1)
3. Switching back to Unity
or
1. Starting up to Unity
2. Suspend computer
3. Resume computer
In both cases i have to wait about 2 minutes, because video is freeze.
But I have noticed that if
** Attachment added: kern.log_freeze
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1062077/+attachment/3419004/+files/kern.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1062077
Title:
** Attachment added: dmesg_logout
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1062077/+attachment/3419005/+files/dmesg_logout
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1062077
Title:
** Attachment added: kern.log_logout
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1062077/+attachment/3419006/+files/kern_logout.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1062077
After looking a bit more into this, it seems the issue in
https://lists.gnu.org/archive/html/bug-bash/2017-12/msg00065.html is
maybe not a real security concern, since rbash was wrongly configured.
Having . in PATH is not good with rbash and that makes the whole thing
flawed. So, we could say
Is this about https://lists.gnu.org/archive/html/bug-
bash/2017-03/msg00077.html ? Or about https://lists.gnu.org/archive/html
/bug-bash/2017-12/msg00065.html ?
Apparently, both are very old flaws.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
I don't think they are the same issue. Or, at least, the first issue was
only partially fixed. I can see both Fedora 29 and Ubuntu 18.10 being
still affected by the issue outlined in
https://lists.gnu.org/archive/html/bug-bash/2017-12/msg00065.html,
though they are not affected by
