Public bug reported:
Could have been in the connection with removing a PTP source from the
system.
ProblemType: Crash
DistroRelease: Ubuntu 18.10
Package: gvfs-backends 1.38.0-2ubuntu2
ProcVersionSignature: Ubuntu 4.18.0-8.9-lowlatency 4.18.7
Uname: Linux 4.18.0-8-lowlatency x86_64
ApportVersion:
Public bug reported:
Don't think I changed the configuration file manually ever.
ProblemType: Package
DistroRelease: Ubuntu 18.10
Package: libgtk-3-0 3.23.2-1ubuntu1
ProcVersionSignature: Ubuntu 4.17.0-9.10-lowlatency 4.17.17
Uname: Linux 4.17.0-9-lowlatency x86_64
ApportVersion: 2.20.10-0ubuntu9
Pretty sure at least I did at several points in the past. Not sure they
were active at the time of the report, though.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-keyring in Ubuntu.
https://bugs.launchpad.net/bugs/1768541
T
Public bug reported:
I think this occured during a large package update.
ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: libp11-kit-gnome-keyring 3.27.4-1ubuntu1
ProcVersionSignature: Ubuntu 4.13.0-32.35-lowlatency 4.13.13
Uname: Linux 4.13.0-32-lowlatency x86_64
ApportVersion: 2.20.8-0
I'm pretty sure by now that this issue has been video-driver or
compositor related. After upgrading to Wily and a different NVidea
driver, it seems to have disappeared. Prior to that, I noticed lag for
several other operations, like scolling in browser windows, with the
result being unconsistent
y to
trigger it. Sometimes the cursor blinking causes a refresh, so it's
also more likely with the cursor off-screen.
--
David Kastrup
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-terminal in Ubuntu.
https://bugs.l
Public bug reported:
I am often using Scrollback in GNOME-Terminal. The current version
forgets to refresh the screen timely afterwards. For one thing, it
means that one is wildly pressing Shift-PageUp Shift-PageDown too often
and it is hard to find things.
For another, when trying to highlight
** Visibility changed to: Public
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-session in Ubuntu.
https://bugs.launchpad.net/bugs/823738
Title:
gnome-session-check-accelerated-helper crashed with SIGSEGV in
XF86DRIQueryExt
** Visibility changed to: Public
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-panel in Ubuntu.
https://bugs.launchpad.net/bugs/820178
Title:
gnome-panel crashed with signal 5 in _XError()
To manage notifications about this
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to yelp in Ubuntu.
https://bugs.launchpad.net/bugs/810392
Title:
package libyelp0 3.1.1-0ubuntu1 failed to install/upgrade: trying to
overwrite '/usr/lib/libyelp.so.0.0.0', which is also
Public bug reported:
Problem after last update
ProblemType: Package
DistroRelease: Ubuntu 11.10
Package: libyelp0 3.1.1-0ubuntu1
ProcVersionSignature: Ubuntu 3.0.0-5.6-generic 3.0.0-rc7
Uname: Linux 3.0.0-5-generic i686
Architecture: i386
Date: Thu Jul 14 11:33:01 2011
ErrorMessage: trying to ove
** Attachment added: "Output from /var/log/gdm/:0-greeter.log"
https://bugs.launchpad.net/bugs/693863/+attachment/1774778/+files/%3A0-greeter.log
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm in ubuntu.
https://bugs.launchpa
Public bug reported:
Binary package hint: gdm
It is no longer possible to log in as the gdm-simple-greeter window
dies, respawns, dies, and so on in quick succession
ProblemType: Bug
DistroRelease: Ubuntu 11.04
Package: gdm 2.32.0-0ubuntu2
ProcVersionSignature: Ubuntu 2.6.37-11.25~ppa1-lowlatenc
No, there is no current_now. Sorry, I should have mentioned that I am
using natty currently and thus am in the wrong place to report the bug.
Anyway, I get
ls /sys/class/power_supply/BAT0/
alarmenergy_full_design power status uevent
cycle_count energy_now power_no
I think one problem is that the kernel does not propagate the discharge
information to the /sys architecture. If I look at
/proc/acpi/battery/BAT0/state
I can read
present: yes
capacity state: ok
charging state: charging
present rate:26018 mW
remaini
15 matches
Mail list logo