hitting the same issue once and a while.
it happened again yesterday. i could record some traffic on dbus:
this pastebin shows the log with high performance impact.
at the end of the log things are getting normal again:
http://pastebin.com/v55umuBF
this pastebin in comparison shows the traffic af
gtk-greeter:1246): WARNING **: Failed to load user image: Failed
to open file '/home/ingo/.face': No such file or directory
upstart: indicator-application main process (1271) terminated with status 1
LightdmGreeterLogOld:
** (lightdm-gtk-greeter:2077): WARNING **: Failed to load
apport information
** Attachment added: "JournalErrors.txt"
https://bugs.launchpad.net/bugs/1486174/+attachment/4474896/+files/JournalErrors.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs
apport information
** Tags added: apport-collected
** Description changed:
When waking up from sleep (either called through pm-hibernate or
occasionally also pm-suspend), there are not fonts at all anymore. This
won't happen every time but more like every third or fourth time. Yet,
it pr
Sorry for the late reply, I just added the apport data. Downgrading
libfreetype6 as suggested by Arnaud doesn't work for me. The problem persists
although
apt-cache show libfreetype6 shows package version 2.5.2-2ubuntu3 (rather than
the most recent version 2.5.2-2ubuntu3.1).
Best, Ingo
--
+ InstallationMedia: Xubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422.1)
+ LightdmGreeterLog:
+ ** (lightdm-gtk-greeter:1246): WARNING **: Failed to load user image: Failed
to open file '/home/ingo/.face': No such file or directory
+ upstart: indicator-a
ystem: ASUSTeK Computer Inc. Device [1043:181d]
InstallationDate: Installed on 2015-08-13 (44 days ago)
InstallationMedia: Xubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422.1)
LightdmGreeterLog:
** (lightdm-gtk-greeter:1246): WARNING **: Failed to load user image: Failed
to
ystem: ASUSTeK Computer Inc. Device [1043:181d]
InstallationDate: Installed on 2015-08-13 (44 days ago)
InstallationMedia: Xubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422.1)
LightdmGreeterLog:
** (lightdm-gtk-greeter:1246): WARNING **: Failed to load user image: Failed
to
Subsystem: ASUSTeK Computer Inc. Device [1043:181d]
InstallationDate: Installed on 2015-08-13 (44 days ago)
InstallationMedia: Xubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422.1)
LightdmGreeterLog:
** (lightdm-gtk-greeter:1246): WARNING **: Failed to load user image: Failed
ASUSTeK Computer Inc. Device [1043:181d]
InstallationDate: Installed on 2015-08-13 (44 days ago)
InstallationMedia: Xubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422.1)
LightdmGreeterLog:
** (lightdm-gtk-greeter:1246): WARNING **: Failed to load user image: Failed
to open file
ystem: ASUSTeK Computer Inc. Device [1043:181d]
InstallationDate: Installed on 2015-08-13 (44 days ago)
InstallationMedia: Xubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422.1)
LightdmGreeterLog:
** (lightdm-gtk-greeter:1246): WARNING **: Failed to load user image: Failed
to
])
Subsystem: ASUSTeK Computer Inc. Device [1043:181d]
InstallationDate: Installed on 2015-08-13 (44 days ago)
InstallationMedia: Xubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422.1)
LightdmGreeterLog:
** (lightdm-gtk-greeter:1246): WARNING **: Failed to load user image
ystem: ASUSTeK Computer Inc. Device [1043:181d]
InstallationDate: Installed on 2015-08-13 (44 days ago)
InstallationMedia: Xubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422.1)
LightdmGreeterLog:
** (lightdm-gtk-greeter:1246): WARNING **: Failed to load user image: Failed
to
ASUSTeK Computer Inc. Device [1043:181d]
InstallationDate: Installed on 2015-08-13 (44 days ago)
InstallationMedia: Xubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422.1)
LightdmGreeterLog:
** (lightdm-gtk-greeter:1246): WARNING **: Failed to load user image: Failed
to
TeK Computer Inc. Device [1043:181d]
InstallationDate: Installed on 2015-08-13 (44 days ago)
InstallationMedia: Xubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422.1)
LightdmGreeterLog:
** (lightdm-gtk-greeter:1246): WARNING **: Failed to load user image: Failed
to open file
TeK Computer Inc. Device [1043:181d]
InstallationDate: Installed on 2015-08-13 (44 days ago)
InstallationMedia: Xubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422.1)
LightdmGreeterLog:
** (lightdm-gtk-greeter:1246): WARNING **: Failed to load user image: Failed
to open file
ASUSTeK Computer Inc. Device [1043:181d]
InstallationDate: Installed on 2015-08-13 (44 days ago)
InstallationMedia: Xubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422.1)
LightdmGreeterLog:
** (lightdm-gtk-greeter:1246): WARNING **: Failed to load user image: Failed
to open file
ystem: ASUSTeK Computer Inc. Device [1043:181d]
InstallationDate: Installed on 2015-08-13 (44 days ago)
InstallationMedia: Xubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422.1)
LightdmGreeterLog:
** (lightdm-gtk-greeter:1246): WARNING **: Failed to load user image: Failed
to
Subsystem: ASUSTeK Computer Inc. Device [1043:181d]
InstallationDate: Installed on 2015-08-13 (44 days ago)
InstallationMedia: Xubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422.1)
LightdmGreeterLog:
** (lightdm-gtk-greeter:1246): WARNING **: Failed to load user image: Fai
Subsystem: ASUSTeK Computer Inc. Device [1043:181d]
InstallationDate: Installed on 2015-08-13 (44 days ago)
InstallationMedia: Xubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422.1)
LightdmGreeterLog:
** (lightdm-gtk-greeter:1246): WARNING **: Failed to load user image: Fai
ystem: ASUSTeK Computer Inc. Device [1043:181d]
InstallationDate: Installed on 2015-08-13 (44 days ago)
InstallationMedia: Xubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422.1)
LightdmGreeterLog:
** (lightdm-gtk-greeter:1246): WARNING **: Failed to load user image: Failed
to
TeK Computer Inc. Device [1043:181d]
InstallationDate: Installed on 2015-08-13 (44 days ago)
InstallationMedia: Xubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422.1)
LightdmGreeterLog:
** (lightdm-gtk-greeter:1246): WARNING **: Failed to load user image: Failed
to open file
** (lightdm-gtk-greeter:1246): WARNING **: Failed to load user image: Failed
to open file '/home/ingo/.face': No such file or directory
upstart: indicator-application main process (1271) terminated with status 1
LightdmGreeterLogOld:
** (lightdm-gtk-greeter:2077): WARNING **: Fail
I also have this problem and it is stupid to have watchdog started
manually using systemd after each (re)boot to work.
I have removed all blacklist-entries for iTCO_wdt and also rebuild
initramfs ... but it still says at boot that module is blacklisted ...
:-(
--
You received this bug notificati
I tried that but I had no success.
I now have the /etc/init.d/watchdog start in /etc/rc.local (systemctl
did not worked that way) and so start using that
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
http
Public bug reported:
when powering down the system systemd cannot unmount /
systemd-shutdown[1]: Could not detach DM /dev/dm-0: Device or resource busy
systemd-shutdown[1]: Failed to finalize DM devices, ignoring
reboot: Power down
as a result at each startup the filesystem is checked:
Press C
A friend of mine has a Carbon 7th-gen and did the following update this
morning:
```
Start-Date: 2020-03-29 09:23:18
Commandline: apt-get upgrade
@Hui Wang
Thanks for the quick reply. If I understand correctly, 5.3.0-43 is not
yet in the bionic repository, but in bionic-proposed. I'm a bit hesitant
to install this after having just gotten the system back to boot again.
Is it intentional that there is this incompatibility but libasound is
al
Thanks so much for your help. It seems to work again now after adding
those options and switching the device once in pavucontrol. Really
appreciate your fast responses!
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-lib
Public bug reported:
When waking up from sleep (either called through pm-hibernate or
occasionally also pm-suspend), there are not fonts at all anymore. This
won't happen every time but more like every third or fourth time. Yet,
it practically means that sleep can not be used. I don't quite know h
Thank you for your fast feedback.
I was not able to execute
dconf reset -f /org/compiz/
at tty7 because i was not able to open a shell and on tty1 i got the error
"cannot autolaunch d-bus without x11 display".
So I did the work myself as good as i could on tty1.
sudo rm -rf ~/.c
** Changed in: unity
Status: New => Fix Released
** Changed in: unity (Ubuntu)
Status: New => Fix Released
--
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/1389888
** Changed in: xorg (Ubuntu)
Status: Expired => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1281019
Title:
10de:0dda [HP EliteBook 8560w] Brightness contr
Why not just close this bug? It's not a problem anymore.
--
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/742671
Title:
Expo scaling far from optimal, wastes a lot of space
S
34 matches
Mail list logo
