Sorry for the spam, but there happens to be a new kernel available just now.
The problem persists with 5.3.0-22.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1848847
Title:
Suspend and resume stopp
For me, the problem persists with 5.3.0-19.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1848847
Title:
Suspend and resume stopped working with nouveau driver after upgrade
to 19.10
To manage no
Same thing here, it is really useful feature lost! It is really
frustrating.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1826266
Title:
Nautilus no longer copies file path when a file is marked th
I have the same bug for many releases already, I just could never find the
rightful solution till few days ago. I am running 17.04 and the problem is
still there... Maybe it will be gone once I update to 17.10, I will report back.
It is frustrating and occurs a lot to me as I never reboot my mach
Now on Ubuntu 16.10, same desktop hardware, nothing changed... Same
problem. I forgot that cutting the power completely is the only way, I
was struggling for couple of hours, again.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https
Now on Ubuntu 16.10, same desktop hardware, nothing changed... Same
problem. I forgot that cutting the power completely is the only way, I
was struggling for couple of hours, again.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https
Simple poweroff and bit of waiting is not sufficient. I have to power
off, disconnect the PSU and try to start the computer (to empty
capacitors). Then after restarting the bluetooth works again.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed t
Ok, I managed to get it to crash and not wanting to restart. For now hciconfig
does see it:
hci0: Type: BR/EDR Bus: USB
BD Address: 00:26:83:33:58:D5 ACL MTU: 1022:8 SCO MTU: 121:3
DOWN INIT RUNNING
RX bytes:395790 acl:133 sco:0 events:55401 errors:0
TX bytes:
Ok, I managed to get it to crash and not wanting to restart. For now hciconfig
does see it:
hci0: Type: BR/EDR Bus: USB
BD Address: 00:26:83:33:58:D5 ACL MTU: 1022:8 SCO MTU: 121:3
DOWN INIT RUNNING
RX bytes:395790 acl:133 sco:0 events:55401 errors:0
TX bytes:
Just rebooted:
$ sudo hciconfig -a
hci0: Type: BR/EDR Bus: USB
BD Address: 00:00:00:00:00:00 ACL MTU: 0:0 SCO MTU: 0:0
DOWN
RX bytes:0 acl:0 sco:0 events:0 errors:0
TX bytes:6 acl:0 sco:0 commands:2 errors:0
Features: 0x00 0x00 0x00 0x00 0x00 0x00 0x00
Just rebooted:
$ sudo hciconfig -a
hci0: Type: BR/EDR Bus: USB
BD Address: 00:00:00:00:00:00 ACL MTU: 0:0 SCO MTU: 0:0
DOWN
RX bytes:0 acl:0 sco:0 events:0 errors:0
TX bytes:6 acl:0 sco:0 commands:2 errors:0
Features: 0x00 0x00 0x00 0x00 0x00 0x00 0x00
Simple poweroff and bit of waiting is not sufficient. I have to power
off, disconnect the PSU and try to start the computer (to empty
capacitors). Then after restarting the bluetooth works again.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed t
Public bug reported:
kernel : 4.2.0-27
onboard bluetooth controller : AR3011
The Bluetooth was working great. I deactivated the bluetooth via the indicator,
and then, impossible to start it. Neither from the settings bluetooth
interface, neither via hciconfig. The service was of course started w
Great,
I had similar problem a while ago. Now that I wanted to upgrade it was
bothering me with most of my PPAs.
Fortunately that solved my problem. I tried methods from here
http://ubuntuforums.org/showthread.php?t=2257304 but nothing worked...
Not it is fully repaired.
--
You received this b
Great,
I had similar problem a while ago. Now that I wanted to upgrade it was
bothering me with most of my PPAs.
Fortunately that solved my problem. I tried methods from here
http://ubuntuforums.org/showthread.php?t=2257304 but nothing worked...
Not it is fully repaired.
--
You received this b
I am running version 1:0.196.12, and I had the bug from this afternoon only. I
upgraded from 13.10 two weeks ago. I did not do any partial upgrades, and
"policykit-1-gnome" is installed.
Is this a new bug?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is s
16 matches
Mail list logo
