** Tags removed: verification-needed-bionic
** Tags added: verification-done-bionic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1809843
Title:
sky2 ethernet card link not up after suspend
To
l your concerns? Can we close this bug?
Mike
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1830987
Title:
Cannot change directory owner or group
To manage notifications about this bug go to:
I just realised that removing chrome remote desktop config isn't enough.
Like I mentioned on my PC i had the same issue. I had to remove
.config/pulse too and restart to make it work
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Thanks Daniel, I have reported another bug with the same issue this time
with alsa running.
https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1815526
solution is exactly the same
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
I reviewed zope.i18nmessageid 4.0.3-2build6 as checked into eoan. This
shouldn't be
considered a full audit but rather a quick gauge of maintainability.
- CVE History:
- There have been CVEs against zope, but none seem to affect this package in
specific
- Build-Depends?
- Requires no
** Tags removed: verification-needed-bionic
** Tags added: verification-done-bionic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1827755
Title:
nx842 - CRB request time out (-110) when uninstall
I tested it and it looks good:
root@ltc-boston25:/home/ubuntu/comp_selftest# insmod comp_selftest.ko
root@ltc-boston25:/home/ubuntu/comp_selftest# ./testit
root@ltc-boston25:/home/ubuntu/comp_selftest# dmesg |tail
[ 10.561010] audit: type=1400 audit(1561358069.720:8): apparmor="STATUS"
I performed the firmware update as advised by Kai-Heng Feng and that has
fixed the problem with 5.0.0-17.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1832091
Title:
Kernel 5.0.0-16 & 5.0.0-17
Setting to invalid as firmware update fixed the problem
** Changed in: linux (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1832091
Title:
Kernel
** Bug watch added: Linux Kernel Bug Tracker #203945
https://bugzilla.kernel.org/show_bug.cgi?id=203945
** Also affects: linux via
https://bugzilla.kernel.org/show_bug.cgi?id=203945
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a
This isn't a kernel issue - I don't have an answer on the why for being
forced offline but it's the not a kernel bug.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1827335
Title:
Unable to put
Ok I managed to fix it
rm -rf ~/.config/chrome-remote-desktop/pulse*
Looks like chrome remote desktop app (which i was using) took over my
sound card in gnome settings, weird :/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Ok I managed to fix it
rm -rf ~/.config/chrome-remote-desktop/pulse*
Looks like chrome remote desktop app (which i was using) took over my
sound card in gnome settings, weird :/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
i only see chrome device as output device after manually running
pulseaudio -D and pulseaudio --check
** Attachment added: "Screenshot from 2019-06-20 12-58-29.png"
Public bug reported:
in gnome settings audio section does not see any sound card. if i run
alsamixer it can detect the sound card and all works fine. in gnome
sound settings everything seems to be disabled.
I have excatly same problem on PC where configuration is completely
different than my
More info after i run pulseaudio --check i can see an output device but
its not my sound card, another screenshot attached
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1833527
Title:
in gnome
** Attachment added: "after run pulseaudio -D and pulseaudio --check"
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1833527/+attachment/5271788/+files/Screenshot%20from%202019-06-20%2012-58-29.png
--
You received this bug notification because you are a member of Ubuntu
Bugs,
** Attachment added: "Screenshot from 2019-06-20 12-46-32.png"
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1833527/+attachment/5271783/+files/Screenshot%20from%202019-06-20%2012-46-32.png
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Public bug reported:
in gnome settings audio section does not see any sound card. if i run
alsamixer it can detect the sound card and all works fine. in gnome
sound settings everything seems to be disabled.
I have excatly same problem on PC where configuration is completely
different than my
I finally found 1st commit (not connected with USB problem) which prevents
booting, but it is corrected much later in 4.10-rc8.I don't know how to locate
correction commit for the one below
$ git bisect bad
174cc7187e6f088942c8e74daa7baff7b44b33c9 is the first bad commit
commit
The problem persists in 5.0.0-17 so I have updated the title
accordingly.
** Summary changed:
- Kernel 5.0.0-16 USB-2 keyboard on USB-C dock malfunction
+ Kernel 5.0.0-16 & 5.0.0-17 USB-2 keyboard on USB-C dock malfunction
--
You received this bug notification because you are a member of
That's correct on DD 2.3 - still not very available - and is ok. Will
still post test results.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1832622
Title:
QEMU - count cache flush Spectre v2
I tried some test fw for the boston:
ubuntu@ltc-boston25:~$ sudo /sbin/hwclock --set --date "2019/06/10 12:55:00";
sudo /sbin/hwclock --verbose
[sudo] password for ubuntu:
hwclock from util-linux 2.33.1
System Time: 1560377530.955292
Trying to open: /dev/rtc0
Using the rtc interface to the
Public bug reported:
Because usb-creator performs privileged actions, it should require
authentication prior to starting. policykit-desktop-privileges should be
modified so that usb-creator requires password authentication prior to
starting.
While it was a deliberate design decision to allow
related (or even identical) bugs:
https://bugs.launchpad.net/ubuntu/+source/plasma-workspace/+bug/1770044
https://bugs.launchpad.net/ubuntu/+source/print-manager/+bug/1794526
This bug is crucial. It is annoying. As it still persists.
Please harden plasma-shell not to depend on crashing plugins.
I've set to confirmed as per the Ubuntu Kernel Bot's advice. Let me know
if I need to provide anything else.
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
** Summary changed:
- Kernel 5.0.0-16 keyboard malfunction
+ Kernel 5.0.0-16 USB-2 keyboard on USB-C dock malfunction
Opened issue 1423 on this - unfortunately the boston openpower is
closed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1802233
Title:
hwclock test failed on Power9 due to 0.x sec differences /
Robert,
What kind of filesystem is on /media/robert/Shared? It is likely that
/media/robert/Shared is a fat32, exfat, or NTFS filesystem. These
filesystems do not support posix permissions and therefore any attempt
to change the permissions/ownership will fail.
You stated that, "I know that the
** Information type changed from Private Security to Public Security
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1830987
Title:
Cannot change directory owner or group
To manage notifications
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1832091/+attachment/5269744/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "AlsaInfo.txt"
https://bugs.launchpad.net/bugs/1832091/+attachment/5269742/+files/AlsaInfo.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1832091
** Attachment added: "apport.linux._i66ha6d.apport"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1832091/+attachment/5269741/+files/apport.linux._i66ha6d.apport
** Tags added: apport-collected tessa
** Description changed:
Upgrading to kernel package linux-image-5.0.0-16-generic
apport information
** Attachment added: "CRDA.txt"
https://bugs.launchpad.net/bugs/1832091/+attachment/5269743/+files/CRDA.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1832091
Title:
Steve, thanks for your response. Using the latest build, I was not able
to reproduce your reported bug. If you are able, please share any other
specific information you may have associated with this issue.
Best regards,
Mike
** Changed in: debian-installer (Ubuntu)
Status: New
Public bug reported:
Upgrading to kernel package linux-image-5.0.0-16-generic causes the
keyboard which is a USB 2 device connected to a USB C hub on my Dell XPS
13 to behave erratically. The previous kernel (linux-
image-5.0.0-15-generic) doesn't have this problem. (The keyboard is fine
when
Hi Steve, is this still a problem for you or has this been resolved with
use of the latest build?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1820527
Title:
Ubuntu 19.04 Server edition: Cannot
Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug. I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross
Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug. I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross
Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug. I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross
Public bug reported:
VIM has recently added support for validating gnome desktop files and
this is reporting errors due to invalid UTF-8 sequences produced by
msgfmt.
Steps to reproduce:
1. Checkout rev 1253704 from the VIM git repo on GitHub -
https://github.com/vim/vim
2. Run ./configure in
wanted to touch base with you.
Best regards,
Mike Dombrowski
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/301481
Title:
would not install
To manage notifications about this bug go to:
https://bugs.
CVE-2019-12210
CVE-2019-12209
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2019-12209
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2019-12210
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug. I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross
Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug. I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross
Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug. I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross
Hello Jullian!
Would you please clarify what part of the video card installation "broke
the installation"? Do you still possess any of the logs that would
indicate a specific problem?
Has this issue been solved with a later release of Ubuntu?
Best regards,
Mike
--
You receive
Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug. I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross
Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug. I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross
** Changed in: debian-installer (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/301481
Title:
would not install
To manage notifications about this bug go
Is groff installed?
apt install groff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1778684
Title:
man: command exited with status 4
To manage notifications about this bug go to:
I have this bug (and some other related ones) on a Lenovo ThinkPad L540
running Ubuntu 18.04.2. I switched to using lightdm which works around
the issues, but I don't like lightdm as much.
I see it's marked "Fix Released" above; excuse the ignorant question,
but does this mean I will soon be
Another detail that might be worth mentioning...
Running "aptitude update" to create the /var/lib/aptitude/pkgstates file
seems to ONLY work from a tty. From a connection with no tty (such as
one initiated via ansible), it does not seem to create the file.
I had to work around things by making
Since it's still not working on 19.04, guess that answers my question as
to whether to upgrade or not. I've confirmed that the acpid isn't
seeing the plug in event by running:
netcat -U /var/run/acpid.socket
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
@modiford
http://cdimage.ubuntu.com/releases/18.04.2/release/ubuntu-18.04.2
-server-amd64.iso
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1816954
Title:
Unable to show Info nor Set static IP
This is still a problem in 2019? I've attached my Ubuntu 18.04.2
desktop to an Active Directory using:
https://help.ubuntu.com/lts/serverguide/sssd-ad.html.en
Everything appears to work perfectly until some sort of failure - I can
reproduce it under high load, or just waiting..., I'll try
This bug also affects me on 19.04.
Moreover, I am able to reproduce the bug no matter where I try to save:
Unable to open X config file '/home/mkasberg/Desktop/mike-nvidia-
xconfig.conf' for writing.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
> The timeout is there mainly for people who select the action,
> and then forget to confirm the action and walk away.
The timeout as a feature has an extremely bad ratio of befuddleness vs.
usefulness to the user.
When a feature is only marginally useful, and yet it is bound to confuse
people
*** This bug is a duplicate of bug 1576559 ***
https://bugs.launchpad.net/bugs/1576559
Also experiencing this issue and the "headset" profile is not missing
for me, either:
Device 28:11:A5:78:66:9A
Name: Bose QC35 II
Alias: Bose QC35 II
Class: 0x240418
Icon:
Also the lockscreen image is affected as well. Sometimes other parts of
the UI are as well like browser windows.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1826616
Title:
After resuming from
Public bug reported:
As stated in the title of the bug, every time I resume from suspend, the
wallpaper turns into a static picture. This can be somewhat alleviated
by switching the wallpaper, but the previous wallpaper is unusable until
reboot.
ProblemType: Bug
DistroRelease: Ubuntu 19.04
** Attachment added: "Static wallpaper"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1826616/+attachment/5259404/+files/Screenshot%20from%202019-04-26%2020-16-08.png
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I reviewed python-django-gravatar2 version 1.4.2-3 as checked into
disco. This should not be considered a full security audit, but rather a
quick gauge of maintainability.
- There are no prior CVEs against the package
- Build depends:
debhelper (>= 11),
dh-python,
I confirmed with a django developer that django does, indeed, catch exceptions
in the views.
https://github.com/django/django/blob/master/django/core/handlers/exception.py#L18
Hyperkitty should be safe from any crash, however, it may still be wise
to catch any TypeErrors raised by is_robot().
Public bug reported:
If the user reboots or shuts down (uncertain about logging off and back
on), they will be signed out from Ubuntu One. Previously, Ubuntu
Software on 18.10 and earlier, the user would be signed out of Ubuntu
One after closing the Software Store, but now it takes a reboot or
Public bug reported:
info was uploaded using ubuntu-bug ubuntu-release-upgrader-core from a
terminal
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: ubuntu-release-upgrader-core 1:16.04.25
ProcVersionSignature: Ubuntu 4.4.0-145.171-generic 4.4.176
Uname: Linux 4.4.0-145-generic i686
I reviewed robot-detection version 0.4.0-1 as checked into disco. This
should not be considered a full security audit, but rather a quick gauge
of maintainability.
- There are no prior CVEs against robot-detection
- Build depends:
debhelper (>= 9),
dh-python,
Please ignore the previous comment. I pasted that into the wrong window.
Sorry!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1783317
Title:
[MIR] sshfs-fuse
To manage notifications about this bug
I reviewed robot-detection version 0.4.0-1 as checked into disco. This should
not be considered a full security audit, but rather a quick gauge of
maintainability.
- There are no prior CVEs against robot-detection
- Build depends:
debhelper (>= 9),
dh-python,
Upstream bug: https://gitlab.gnome.org/World/ShellExtensions/desktop-
icons/issues/111
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1825396
Title:
"Open in Terminal" returns "Text ended before
** Description changed:
Curretly, this feature simply does not exist, unless you count the buggy
keyboard implementation. Please add the feature to snap windows to the
bottom left and right and upper left and right corners via the mouse
alone. Currently, if you manually install compiz
** Also affects: gnome-shell (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1825756
Title:
Window snapping to corners via mouse
To manage
** Package changed: compiz (Ubuntu) => ubuntu
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1825756
Title:
Window snapping to corners via mouse
To manage notifications about this bug go to:
Public bug reported:
Curretly, this feature simply does not exist, unless you count the buggy
keyboard implementation. Please add the feature to snap windows to the
bottom left and right and upper left and right corners via the mouse
alone. Currently, if you manually install compiz settings, you
1. I understand that it is done by command "git bisect reset"
2. If I understand You well I am already on first regression commit (blank
screen issue) becouse I can't boot on 4.10-rc2+3 but on 4.9.0+-2 it was
possible.
--
You received this bug notification because you are a member of Ubuntu
Marking this as security since the following directory name proves
command execution is possible:
aaa -e bash -c 'firefox'
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1825396
Title:
"Open in
Version 4.15 works well. Now I have installed Debian 9 with a kernel 4.9
on this device, it works well.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1824886
Title:
Battery level stuck at 100% and
** This bug is no longer a duplicate of bug 1810571
Update to ffmpeg 3.4.6 in Bionic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1823786
Title:
[SRU] ffmpeg 3.4.6 for bionic
To manage
*** This bug is a duplicate of bug 1823786 ***
https://bugs.launchpad.net/bugs/1823786
** This bug has been marked a duplicate of bug 1823786
[SRU] ffmpeg 3.4.6 for bionic
** This bug is no longer a duplicate of bug 1823786
[SRU] ffmpeg 3.4.6 for bionic
** This bug has been marked a
I booted from the LiveCD 19.04. Although charging status is indicated
the other way round, percentages are correct and decrease with battery
discharge.
How tired I am of this...
Ubuntu does not work normally on any of the last ten computers...
--
You received this bug notification because you
** Attachment added: "Снимок экрана от 2019-04-17 13-58-05.png"
https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/1824886/+attachment/5256526/+files/%D0%A1%D0%BD%D0%B8%D0%BC%D0%BE%D0%BA%20%D1%8D%D0%BA%D1%80%D0%B0%D0%BD%D0%B0%20%D0%BE%D1%82%202019-04-17%2013-58-05.png
--
You
** Attachment added: "Снимок экрана от 2019-04-17 13-57-22.png"
https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/1824886/+attachment/5256525/+files/%D0%A1%D0%BD%D0%B8%D0%BC%D0%BE%D0%BA%20%D1%8D%D0%BA%D1%80%D0%B0%D0%BD%D0%B0%20%D0%BE%D1%82%202019-04-17%2013-57-22.png
--
You
** Attachment added: "Снимок экрана от 2019-04-17 13-58-31.png"
https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/1824886/+attachment/5256527/+files/%D0%A1%D0%BD%D0%B8%D0%BC%D0%BE%D0%BA%20%D1%8D%D0%BA%D1%80%D0%B0%D0%BD%D0%B0%20%D0%BE%D1%82%202019-04-17%2013-58-31.png
--
You
** Attachment added: "Снимок экрана от 2019-04-17 13-56-17.png"
https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/1824886/+attachment/5256524/+files/%D0%A1%D0%BD%D0%B8%D0%BC%D0%BE%D0%BA%20%D1%8D%D0%BA%D1%80%D0%B0%D0%BD%D0%B0%20%D0%BE%D1%82%202019-04-17%2013-56-17.png
--
You
** Attachment added: "Снимок экрана от 2019-04-17 13-59-02.png"
https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/1824886/+attachment/5256528/+files/%D0%A1%D0%BD%D0%B8%D0%BC%D0%BE%D0%BA%20%D1%8D%D0%BA%D1%80%D0%B0%D0%BD%D0%B0%20%D0%BE%D1%82%202019-04-17%2013-59-02.png
--
You
** Attachment added: "Снимок экрана от 2019-04-17 13-55-42.png"
https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/1824886/+attachment/5256523/+files/%D0%A1%D0%BD%D0%B8%D0%BC%D0%BE%D0%BA%20%D1%8D%D0%BA%D1%80%D0%B0%D0%BD%D0%B0%20%D0%BE%D1%82%202019-04-17%2013-55-42.png
--
You
$ cat /sys/class/power_supply/BAT0/charge*
420
430
420
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1824886
Title:
Battery level stuck at 100% and Estimating...
To manage
I disconnected the power adapter and worked ~30 minutes.
upower -d
Device: /org/freedesktop/UPower/devices/line_power_AC0
native-path: AC0
power supply: yes
updated: Ср 17 апр 2019 13:31:34 (959 seconds ago)
has history: no
has statistics: no
** Package changed: gnome-control-center (Ubuntu) => gnome-power-manager
(Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1824886
Title:
Battery level stuck at 100% and Estimating...
To
** Summary changed:
- Battery applet does not display battery charge.
+ Battery charge is 100% stuck and Estimating...
** Summary changed:
- Battery charge is 100% stuck and Estimating...
+ Battery level stuck at 100% and Estimating...
--
You received this bug notification because you are a
I attached journalctl from Ubuntu in the Ubuntu_debug.log file. If this is not
what you need - teach me how to do it.
Screenshots made in Linux Mint. gnome-control-center shows the correct status
only Linux Mint (and Windows).
--
You received this bug notification because you are a member of
I was looking for a solution in Google. Many people have a problem with
the charge indicator in Ubuntu. And basically they all gave up without
finding any solution to this problem. If we now find a solution to this
problem, it will help many people and make ubuntu even better.
--
You received
Screenshot 1:
** Attachment added: "Screenshot from 2019-04-16 16-16-30.png"
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1824886/+attachment/5256310/+files/Screenshot%20from%202019-04-16%2016-16-30.png
--
You received this bug notification because you are a member of
Screenshot 3:
** Attachment added: "Screenshot from 2019-04-16 16-19-42.png"
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1824886/+attachment/5256312/+files/Screenshot%20from%202019-04-16%2016-19-42.png
--
You received this bug notification because you are a member of
Screenshot 2:
** Attachment added: "Screenshot from 2019-04-16 16-19-07.png"
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1824886/+attachment/5256311/+files/Screenshot%20from%202019-04-16%2016-19-07.png
--
You received this bug notification because you are a member of
Ubuntu log.
** Attachment added: "Ubuntu_debug.log"
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1824886/+attachment/5256308/+files/Ubuntu_debug.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
How it works in Linux Mint:
** Attachment added: "Mint_debug.log"
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1824886/+attachment/5256309/+files/Mint_debug.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
If I unplug the charger and reboot, the command issues the following
(100% always):
upower -d
Device: /org/freedesktop/UPower/devices/line_power_AC0
native-path: AC0
power supply: yes
updated: Вт 16 апр 2019 18:06:47 (313 seconds ago)
has history: no
** Attachment added: "2.png"
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1824886/+attachment/5256253/+files/2.png
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1824886
Sebastien,
importance: Undecided → High! :)
This error does not allow you to use Ubuntu on a laptop :(
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1824886
Title:
Battery applet does not
Hello Sebastien!
In an attempt to figure out the cause, I did the following:
1.) Launched from a Linux Mint flash drive - the applet works there.
2.) And in Windows also works.
3.) Launched Ubuntu from a flash drive - does not work.
upower -d
Device:
601 - 700 of 11877 matches
Mail list logo
