Downgrading popt from 1.19+dfsg-1 to 1.18-3build1 shows that the
problem is not in imageinfo but in popt.
** Package changed: imageinfo (Ubuntu) => popt (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to popt in
systemd 246.6-1ubuntu1 and apport 2.20.11-0ubuntu48 fix this issue for
me.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1891657
Title:
systemd 100% cpu usage
I'm still seeing this bug with apport 2.20.11-0ubuntu48 and systemd
246.5-1ubuntu1. Do we need systemd 246.6 before it is fixed?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
Also, if you want to reduce the massive size of the journal logs that
this bug creates, do something like this:
sudo journalctl --rotate
sudo journalctl --vacuum-size=100M
That second command reduces it to 100 MB, but you can specify larger or
smaller sizes.
--
You received this bug
Trying again... After reading the linked systemd bug report, I changed
/usr/lib/systemd/system/apport-autoreport.path from having
PathExistsGlob to PathChangedGlob and ran sudo systemctl daemon-reload,
and this seemed to fix the problem:
[Unit]
Description=Process error reports when automatic
I changed
[Path]
PathChangedGlob=/var/crash/*.crash
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1891657
Title:
systemd 100% cpu usage apport-autoreport.service:
Doesn't systemd normally stop trying to start a service if it fails too
often? That's clearly not happening here, though.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
I ran into this and applied the workaround of deleting all the files in
/var/crash to stop the journalctl spam and 100% CPU usage.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
My Ubuntu 20.04 installation just did this - something changed the
org.gnome.desktop.lockdown disable-lock-screen to true and also the
blank screen to never (did an update do this?).
But there's nothing I can see in gnome-control-center to modify this
value, making this bug pretty obscure when it
This is still present in 19.04.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/1308169
Title:
apport-bug on .crash file for a stable release doesn't notify crash
was
Marking as fix released because it looks like this was resolved by this
morning's update (by a reconfiguration of systemd? dpkg.log says that it
installed version 240-6ubuntu2, but it also says that this version has
been installed since the 13th of March).
/etc/resolv.conf now contains
The problem seems to occur because the wireless network connects before
my user logs in. If I do a reboot and login cycle with the wireless
router turned off, when I turn it back on and the computer connects,
/run/resolvconf/resolv.conf is updated correctly with the DNS nameserver
information, as
Public bug reported:
Relatively recently, after I reboot Ubuntu 19.04, the wireless network
connects but DNS is not working. This is because the /etc/resolv.conf
file, which is a symlink to ../run/resolvconf/resolv.conf, has no
nameserver entries:
# Dynamic resolv.conf(5) file for glibc
Oops, it was either acpi_osi=! or acpi_osi='Windows 2009' that was
causing the problem. I had copied them in to try and get the nvidia card
working after resume, but it turns out they aren't needed for the nvidia
card to work anyway.
Sorry for the noise.
** Changed in: upower (Ubuntu)
Public bug reported:
When I press the screen backlight up/down buttons, gnome-shell pops up
the backlight control window saying that the backlight is being
adjusted, but the actual screen brightness does not change.
The problem is that gnome is adjusting
It's still an issue in Ubuntu 18.04 and 18.10. g-c-c should really
prompt the user to install gnome-online-accounts if it is not installed
instead of pretending to work and then failing.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
I had this problem, too. journalctl -b|grep glamor showed this:
/usr/lib/gdm3/gdm-x-session[2205]: (EE) modeset(0): glamor
initialization failed
which is why gnome-shell was falling back to llvmpipe. However, there
was some funny business going on with my libGL installation, because ldd
@Brian: just FYI, the /etc/X11/Xsession.d/50_check_unity_support file is
actually checking for ubuntu, not xubuntu: if [ "x$DESKTOP_SESSION" =
"xubuntu" ] will be true if $DESKTOP_SESSION is "ubuntu", because it's
prepending "x" to $DESKTOP_SESSION.
My unity_support_check was failing (it returns
I sometimes need to reboot a server that I'm logged into. In this case,
I got the wrong gnome-terminal tab by mistake and rebooted my laptop
instead, losing all my current work, which was an extremely suboptimal
outcome.
I checked rebooting from another user when my first user logged in, and
it
Doesn't the shutdown icon warn you if there are other users logged in
who might lose work? So shouldn't the reboot command do the same thing
if you are not root?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in
(And pulling the power cord on my laptop doesn't reboot or even shutdown
the computer, so I don't think it's a good comparison. Holding the power
button down for ten seconds is a better comparison, but it's still not a
good one because reboot acts immediately, not after you confirm it by
typing it
Thanks, removing the packages makes the errors go away.
Do you think the error message is misleading? Instead of saying "Failed
to start AppArmor initialization", perhaps it should say, "Failed to
load some profiles"?
--
You received this bug notification because you are a member of Ubuntu
I get this:
$ sudo apparmor_parser --replace /etc/apparmor.d/usr.bin.webbrowser-app
AppArmor parser error for /etc/apparmor.d/usr.bin.webbrowser-app in
/etc/apparmor.d/usr.bin.webbrowser-app at line 26: Could not open
'/usr/share/apparmor/hardware/graphics.d'
$ sudo apparmor_parser --replace
Another user reported what sounds like the same issue at
https://ubuntuforums.org/showthread.php?t=2386129=13749658#post13749658
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
Public bug reported:
AppArmor in Ubuntu 18.04 fails to start every time:
$ systemctl status apparmor.service
● apparmor.service - AppArmor initialization
Loaded: loaded (/lib/systemd/system/apparmor.service; enabled; vendor
preset: enabled)
Active: failed (Result: exit-code) since Mon
@Maarten: Maybe spotify will install and work from its flatpak? It's the
second flatpak app listed here: https://www.omgubuntu.co.uk/2017/07/7
-flatpak-apps-can-install-right-now-flathub
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
FWIW, I got opera-stable and viber to install with libcurl4 by
extracting their debs, manually editing their control file to say
libcurl3|libcurl4, recreating the deb using the "ar -r" command, and
then using dpkg -i to reinstall. They run fine but of course I haven't
been able to test all their
@Brian Murray: I think that it is incorrect to mark this bug as invalid
- at the very least it should be kept as confirmed against the 18.04
release notes so they can include a warning against upgrading to Ubuntu
18.04 because it may not be compatible with a number of popular third-
party
Public bug reported:
Open a gnome-terminal as your normal user and type 'reboot' and ENTER.
The PC reboots immediately, losing all unsaved work for all users (this
is the case on both my VM and laptop running Ubuntu 18.04, so I don't
think it's a weird configuration issue).
In the old days,
If it helps anyone, I've got 4.14-rc5 and apparmor working. I've posted
a patch at the duplicate bug
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1724450.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in
Public bug reported:
Several critical systems are broken with the default Ubuntu 17.10
apparmor profile when booting in kernel 4.14, eg DHCP/networking and
mysql-server.
I got it working by applying the attached patch from the /etc directory.
The patch is mostly based on the patch provided in
I also have this issue in Ubuntu 17.10 (running gdm/gnome-shell).
Uninstalling dbus-user-session isn't really an option, because tons of
apps depend on it.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lightdm in Ubuntu.
I have noticed that doing a "sudo service network-manager restart"
usually fixes things, but not always and not for everything. For
instance, on my laptop at the moment firefox can't find any webpages
("Server not found"), but Chrome is working fine; ntpd is complaining
twice a minute in the log
Is this a modesetting driver issue? I believe I've seen this happen when
hotplugging an external monitor. It only happens for me with the modeset
driver, though, not the intel driver. The modesetting driver is
excellent for some things (eg it doesn't tear on the external monitor
like the intel
No, the issue didn't occur in Xenial, which defaults to the intel
driver. (The intel driver doesn't have these issues.)
Just to be clear - it is possible that the issue is resolved with the
later BIOS, but I won't know until I can test the known bad
configuration again. (Unfortunately, I can't
The output of those commands are: 1.2.13 and 08/08/2016.
I can't test the same configuration that I originally tested for another
week, but on another 1680x1050 monitor it did work, eventually. I had to
restart lightdm several times because things happened like the mouse
click no longer working,
Public bug reported:
I have an external 1920x1080 monitor attached to my laptop, which has a
3840x2160 display. When I run them both at their native resolutions, the
laptop display only works in the top quarter of the desktop, except for
the unity launcher and unity top bar. Anything that leaves
Another use case for allowing connections from lightdm is where Ubuntu
won't boot into a desktop (it happens!) and you want to switch to a tty
console and access the internet (eg to run upgrades) but you have no
ethernet card. In this case it's a huge pain if you can't connect to the
wireless
Ok, so after today's updates dpms and screen lock are now working with
systemd 231-4, so marking as fixed again.
** Changed in: systemd (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed
I've confirmed that the screen lock also does not come on in a VM
running yakkety with systemd 231-4.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1615184
Title:
Reading the associated Debian bug (http://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=834367), it's a different one from this bug. That
bugs refers to issues after running systemctl daemon-reexec (which
happens when systemd is upgraded) caused by keypresses being sent to a
tty console as well as to
No, that's *exactly* what I did. I upgraded from 231-1 to 231-4 and
rebooted and things broke. I did it three times just to be sure.
** Changed in: systemd (Ubuntu)
Status: Fix Released => New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages,
Luckily I had a snapshot from earlier. Bisecting upgrades shows that the
problem is in one of these packages:
libpam-systemd/yakkety 231-4 amd64 [upgradable from: 231-1]
libsystemd-dev/yakkety 231-4 amd64 [upgradable from: 231-1]
libsystemd0/yakkety 231-4 amd64 [upgradable from: 231-1]
Public bug reported:
Whenever I reboot, if there are drivers mounted with corresponding
folders in /media (whether internal or external, btfrs, ntfs, or ext4),
after the reboot the original folder is still present and the drives re-
mount in a new folder. (Note that I mount drives in /media
Alt-F8 triggers resizing windows in compiz/Unity as well! That's good to
know.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity in Ubuntu.
https://bugs.launchpad.net/bugs/160311
Title:
Resizing windows by grabbing
@madbiologist: thanks for looking into it. I haven't upgraded to the A12
BIOS because the list of fixes and enhancements was very small and only
mentioned it was a fix for some issues when upgrading to Windows 8.
(Additionally, Dell doesn't provide a way to update the BIOS from Linux
for this
Seems to be fixed for me now - at least, the geeqie icon is shown
correctly now.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity in Ubuntu.
https://bugs.launchpad.net/bugs/1407192
Title:
firefox icon frequently
geeqie still displays the placeholder icon with bamfdaemon
0.5.1+14.10.20140925-0ubuntu2, though, so I suspect it isn't fixed.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity in Ubuntu.
And I just had my permanently-locked firefox icon in the launcher
replaced with the placeholder, so it's definitely not fixed in that
version of bamf.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity in Ubuntu.
I find the launchbar always displays the grey question mark icon for
geeqie so long as it's not already locked to the launchbar.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity in Ubuntu.
Jan 5 11:03:29 2015
ExecutablePath: /usr/bin/unity8
ExecutableTimestamp: 1418728702
InstallationDate: Installed on 2015-01-03 (1 days ago)
InstallationMedia: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20141220)
ProcCmdline: unity8
ProcCwd: /home/rocko
ProcEnviron:
LANGUAGE=en_US
I ran into this issue in the unstable Vivid release, and I had to
comment out the 'problem_types': ['Bug', 'Package'], line in
/etc/apport/crashdb.conf to get apport-bug working again.
https://help.ubuntu.com/community/ReportingBugs suggests that you only
need to do this for stable releases,
*** This bug is a duplicate of bug 1118903 ***
https://bugs.launchpad.net/bugs/1118903
Actually, I don't think this should be a duplicate of #1118903. Why
should we be forced to use (dreadfully slow) software rendering for
unity8 in a VM when we don't need to do so for unity7? Wouldn't it be
This bug is still present in the latest Ubuntu 14.10 as of 2014-12-29.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity in Ubuntu.
https://bugs.launchpad.net/bugs/1284981
Title:
Locally-integrated menus stop working
I just suspended a second time before restoring one of the windows to
the primary workspace, and when I resumed it was neither on the primary
nor the secondary workspace. I disabled workspaces and it reappeared on
the primary one. My guess is that unity restored the window to its
workspace+1 each
** This bug is no longer a duplicate of bug 1246013
Would be nice for libgl1-mesa-dev to be multiarched
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/949606
Title:
64
Public bug reported:
When I suspend and resume my latop, my windows, which were originally
all in one workspace, are restored to different workspaces (apparently
at random).
For windows not in the current workspace after resume, the unity
launcher indicates that they are running, but clicking on
Public bug reported:
In Ubuntu 14.10 (upgraded from 14.04), the screen does not lock or turn
off after the designated time in System Settings / Brightness and Lock.
The screen lock can still be activated manually from the System menu or
keyboard shortcut (although I notice that the default has
+1 for what Guillaume F said in comment #45. Sometimes the dash takes so
long to populate that it tells me Sorry, there is nothing that matches
your search, even though I know there are matches. And at random times
it resets the search filters to include Files and Folders - I turn this
off as soon
59 matches
Mail list logo
