I have the same or very similar problem, with Fujitsu Lifebook E557,
Ubuntu 16.04,18.04 and 18.10.
After resume from suspend, touchpad doesn't work at all. Keyboard works
somewhat, but some keys are randomly "repete". Reboot doesn't
help, but need to to turn the machine off and on again.
Public bug reported:
Touchpad does not work most of the time. I think it randomly started
working once, but on several other tries/reboots, it does not work.
The device in question:
cat /proc/bus/input/devices
I: Bus=0011 Vendor=0002 Product=000e Version=
N: Name="ETPS/2 Elantech Touchpad"
P
Public bug reported:
After upgrading from 13.04 to 13.10 brightness control on unity no
longer works. When pressing the brightness control keys, the brightness
"progress bar" is shown, but the change has usually no effect.
Sometimes it does change to from 100% brightness to very dim (0%?), but
do
I have the same (or very similar) issue with my system. For me the high
CPU usage is related especially to resuming from suspend. After resuming
the system is very unresponsive for around 1-2 minutes, with gnome-shell
taking 80-100% cpu. After that the cpu usage slowly decreases, but stays
around 2
Public bug reported:
Many times (this has happened to me at least 20 times) when I resume from
suspend the system is very unresponsive and 'sudo iotop' shows kswapd0 taking
99% IO. Only rebooting the machine fixes the problem. (I have tried logging
off. It doesn't help).
After rebooting the
Please close this bug. The problem either has been fixed with a kernel update
or was caused by a memory hog process..
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1127913
Title:
kswapd (kswapd0) t
Disregard my last comment.
For 21 days my system run fine, but now I ran into this bug again.
At the time this problem occurred, I ran the following commands to produce
debug info:
free > free.txt
cp /var/log/syslog .
sudo iotop -b -n 20 > iotop.txt
sudo iotop -b -n 20 > iotop2.txt
For example
Public bug reported:
The problem appears after upgrading 10.04 to 11.10.
Enclosed are pulseaudio syslog entries produced by running:
grep -E '(pulseaudio|alsa-sink)' /var/log/syslog > pulseaudio.log
To reproduce the bug, create io load spike by running:
cat medium_size_file_not_in_filecache > /d
** Attachment added: "syslog"
https://bugs.launchpad.net/bugs/876457/+attachment/2553674/+files/pulseaudio.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/876457
Title:
sound skips under io lo
I also checked that pulseaudio is running as realtime:
sjs@zen:[~] $ ionice -p $(pidof pulseaudio)
realtime: prio 4
I temporarily disabled pulseaudio by running:
echo "autospawn = no" > ~/.pulse/client.conf
pkill pulseaudio
And then I run mplayer while also creating i/o load by cat:ing an 8Gb fi
I run the command:
LANG=C pulseaudio - --log-time=1 > ~/pulseverbose.log 2>&1
It seems to complain about real time priorities:
( 0.000| 0.000) I: [pulseaudio] main.c: setrlimit(RLIMIT_NICE, (31, 31))
failed: Operation not permitted
( 0.000| 0.000) I: [pulseaudio] main.c: setrlimit(RLI
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/877547
Title:
dash "run a command" feature runs wrong command if command is typen
too fast
To manage notifications about this bug go to:
https://bugs.
Public bug reported:
I opened the unity "run a command" feature with keyboard shortcut
(binded to " r", instead of normal alt-f2). Then I typed skype
and hit enter (quite fast). Instead of running skype, it run xkill,
which was the first command to show in the history. Before i hit enter,
the wor
Public bug reported:
See the attached screenshot. The icon of chromium is visible in the
dock, but not in the task switcher.
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: unity 5.4.0-0ubuntu2
ProcVersionSignature: Ubuntu 3.2.0-18.29-generic 3.2.9
Uname: Linux 3.2.0-18-generic x86_64
Appor
** Attachment added: "Screenshot from 2012-03-11 22:09:28.png"
https://bugs.launchpad.net/bugs/952512/+attachment/2852864/+files/Screenshot%20from%202012-03-11%2022%3A09%3A28.png
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
http
Public bug reported:
TO REPRODUCE:
1. Open mouse and touchpad settings in System Settings
2. Put sensitivity and acceleration to max.
3. Doubleclick on the face
RESULT: Trackpoint is as slow as it was before. This leads to me having
to use more pressure on the trackpoint, which causes my fingers
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/952524
Title:
changing mouse sensitivity in system settings has no effect on
trackpoint (lenovo e325)
To manage notifications about this bug go to:
ht
Public bug reported:
TO REPRODUCE:
1. write the following into .emacs in order to disable toolbar and menubar:
(menu-bar-mode -1)
(tool-bar-mode -1)
2. run emacs23
RESULT: Window is slowly resized into containing only one row. It cannot
be manually resized to larger size.
EXPECTED RESULT: A no
** Attachment added: "Screenshot from 2012-03-11 23:07:06.png"
https://bugs.launchpad.net/bugs/952538/+attachment/2852999/+files/Screenshot%20from%202012-03-11%2023%3A07%3A06.png
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
http
Unfortunately I am unable to test this because the chrome icon
reappeared on the task switcher after using the system for a while
(around 10-30 minutes). I didn't use the workspace switcher at all.
I'm not sure if this issue is related, but if I move a terminal window
from one workspace to another
According to the specs, Thinkpad 410s does have a bluetooth device:
http://www.notebookreview.com/default.asp?newsID=5827&review=lenovo+thinkpad+t410s
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/9137
If a user chooses "quit", but the program doesn't quit, it is clearly a
usability problem. I don't know if it's a bug in Unity or Rhythmbox,
but it's a bug nevertheless.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.lau
Public bug reported:
I get these error messages when I run rhythmbox from console:
sjs@zen:[~] $ rhythmbox
Sense key: 0x70 0x00 0x05 0x00 0x00 0x00 0x00 0x0a 0x00 0x00 0x00 0x00 0x30
0x02 0x00 0x00 0x00 0x00 0x00
(rhythmbox:8903): Gtk-CRITICAL **: gtk_builder_get_object: assertion
`GTK_IS_BUI
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/874958
Title:
rhythmbox crashes when clicking Properties for mp3 player sansa clip
To manage notifications about this bug go to:
https://bugs.launchpad.
Public bug reported:
syncropated seems to require hal although its not in the dependency list:
Depends: python (>= 2.4), python-support (>= 0.7.1), gazpacho, python-id3,
python-pysqlite2
This is the log message I get:
sjs@zen:[~] $ syncropated
15:36:17 environ No en_GB translation
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/874992
Title:
syncropated won't start. depends on hal.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/syncropat
Public bug reported:
To reproduce: Start rhythmbox. Start playing a song. Left click
rhythmbox icon in unity launcher. Choose Quit.
Application doesn't quit, music keeps playing, only the window closes.
To really quit the application, put the song on pause and then choose
quit.
ProblemType: Bug
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/875002
Title:
choosing quit from unity launcher doesn't close rhythmbox if music is
playing
To manage notifications about this bug go to:
https://bugs
Public bug reported:
Sticky keys accessibility feature breaks after pressing control key
twice
Steps to reproduce:
1. Open gnome-control-center
2. Navigate to Accessibility => Typing
3. Enable "Sticky keys"
4. Open text editor
5. Press control key twice
Result:
The system stops accepting some ke
On second thoughts, this might be a feature, to keep control key locked.
It seems that pressing control key twice again gets one back to normal
state. But the bug is that this feature is not documented in the help
page and I didn't find instructions for this anywhere. And the same
thing doesn't wor
30 matches
Mail list logo
