Public bug reported:
On my laptop running Jammy the gvfd-smb process is consuming close to 100% CPU:
PID UTIL. PR NIVIRTRESSHR S %CPU %MEMTEMPS+ COM.
** Attachment added: "strace of pulseaudio when using 100% CPU"
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1396848/+attachment/4269461/+files/strace_pulseaudio
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio
Public bug reported:
Pulse audio was running at 100% CPU.
#1 0x7f555f872882 in pa_semaphore_wait () from
/usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-4.0.so
#2 0x7f555faabf97 in pa_asyncmsgq_send () from /usr/lib/libpulsecore-4.0.so
#3 0x7f555fadc79f in ?? () from /usr/lib/
Public bug reported:
The bug is similar to the one reported in
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1314095 (Unity Lockscreen
in 14.04 can't unlock when using LDAP account)
The difference is that I don't have an LDAP account just a local one, the box
was working well in 14.04 a
This is by using the beta2 of Trusty Tahr
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1306785
Title:
closing window leaves a peristant box
Status in “xorg-server” package in U
** Attachment added: "Same symptoms with gnome-terminal"
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1306785/+attachment/4081413/+files/Screenshot%20from%202014-03-24%2010%3A52%3A29.png
--
You received this bug notification because you are a member of Desktop
Packages, which is
Public bug reported:
I have this issue with gnome-terminal or apport when closing the window.
In order to reproduce I have to switch from docked to undocked on my
laptop (with an external screen connected to the dock)
** Affects: xorg-server (Ubuntu)
Importance: Undecided
Status: N
** Attachment added: "screenshot, box left after closing the apport window"
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1306785/+attachment/4081412/+files/Screenshot%20from%202014-04-11%2012%3A15%3A34.png
--
You received this bug notification because you are a member of Desktop
In dmesg, I keep having this message:
[32877.013692] wlan0: waiting for beacon from 00:02:6f:4d:62:db
[32877.019523] wlan0: beacon received
[32877.060109] wlan0: associate with 00:02:6f:4d:62:db (try 1)
[32877.063714] wlan0: RX AssocResp from 00:02:6f:4d:62:db (capab=0x401 status=0
aid=4)
[32877.
--
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/859105
Title:
After some time I'm unable to get associated with access point
Status in “network-manager” package in Ubuntu:
Ne
Public bug reported:
After a fresh boot I'm able for some time to associate with wifi access
point using the network-manager applet. But after a number of
suspend/resume cycle I got to the point where I'm not able to connect
anymore with access point that I used to be able to connect with.
Restar
11 matches
Mail list logo
