[Touch-packages] [Bug 1776475] Re: Unlocking existing session often requires several attempts.
## Thanks @vdrok > automatically lock the session - when the screensaver is activated > delay locking after screensaver for - 5 seconds > lock screen when system is going to sleep - checked Hmm, on my system the delay was set to something small (perhaps even 0). ## Thanks @mag3sh > From further investigation, I noticed that chrome-remote-desktop was starting Xsession and this was causing issues. I removed that package and it fixed the issue. I have no such thing as `chrome-remote-desktop` on my machine. ## Workaround (works for me) This workaround was suggested by the fact that logs say everyting is fine. Perhaps the session happens to be locked again before even displaying? * open xfce4-settings-manager, * click icon "power manager", * click tab "security", Set like this : * automatically lock the session - when the screensaver is activated * delay locking after screensaver for - **15** seconds * lock screen when system is going to sleep - checked Thank you for your attention. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1776475 Title: Unlocking existing session often requires several attempts. Status in lightdm package in Ubuntu: Confirmed Bug description: # Context * Computer with several X sessions opened. * Users switching from one opened session to another. * Lightdm opens new greeter, wait for typing password. * User types password. * Password is accepted. * System closes the current greeter (screen gets black for an instant). # Expected * User gets back to their already opened session. # Observed * System immediately opens another greeter. * User has to type password again. # Reproducible * Not always. At times, often, at other times, rare. # Additional information Users switch session via dm-tool switch-to-user $OTHERUSER but I guess bug appears with other means (like menu item like "lock screen", etc). # Information requested lsb_release -rd Description: Ubuntu 18.04 LTS Release: 18.04 LC_ALL=C apt-cache policy lightdm lightdm: Installed: 1.26.0-0ubuntu1 Candidate: 1.26.0-0ubuntu1 Version table: *** 1.26.0-0ubuntu1 500 500 http://fr.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: lightdm 1.26.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Tue Jun 12 14:14:52 2018 ExecutablePath: /usr/sbin/lightdm InstallationDate: Installed on 2018-05-25 (18 days ago) InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: LANG=fr_FR.UTF-8 PATH=(custom, no user) SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.logrotate.d.lightdm: [modified] mtime.conffile..etc.logrotate.d.lightdm: 2018-05-25T06:19:22.081830 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1776475/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1776475] Re: Unlocking existing session often requires several attempts.
I have a question for people experiencing this bug (yes, you included :-). Please: * open xfce4-settings-manager, * click icon "power manager", * click tab "security", * report what settings are there for when to "automatically lock the session", "delay locking after screensaver for...", "lock screen when system is going to sleep" * if the bug affects you, * and your exact distribution version. Also, since you have to login to launchpad to comment here, please answer to "does this bug affect you?" question on top of this page. This will help me figure out a proper fix. Thanks! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1776475 Title: Unlocking existing session often requires several attempts. Status in lightdm package in Ubuntu: Confirmed Bug description: # Context * Computer with several X sessions opened. * Users switching from one opened session to another. * Lightdm opens new greeter, wait for typing password. * User types password. * Password is accepted. * System closes the current greeter (screen gets black for an instant). # Expected * User gets back to their already opened session. # Observed * System immediately opens another greeter. * User has to type password again. # Reproducible * Not always. At times, often, at other times, rare. # Additional information Users switch session via dm-tool switch-to-user $OTHERUSER but I guess bug appears with other means (like menu item like "lock screen", etc). # Information requested lsb_release -rd Description: Ubuntu 18.04 LTS Release: 18.04 LC_ALL=C apt-cache policy lightdm lightdm: Installed: 1.26.0-0ubuntu1 Candidate: 1.26.0-0ubuntu1 Version table: *** 1.26.0-0ubuntu1 500 500 http://fr.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: lightdm 1.26.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Tue Jun 12 14:14:52 2018 ExecutablePath: /usr/sbin/lightdm InstallationDate: Installed on 2018-05-25 (18 days ago) InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: LANG=fr_FR.UTF-8 PATH=(custom, no user) SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.logrotate.d.lightdm: [modified] mtime.conffile..etc.logrotate.d.lightdm: 2018-05-25T06:19:22.081830 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1776475/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1776475] Re: Unlocking existing session often requires several attempts.
So far, the logs basically show that lightdm does its job, and just does it again when bug happens. I have the feeling that the actual reason of the bug does not appear in the log. Perhaps something triggers a lock behavior, causing lightdm to just do what it's supposed to do. The problem might lie in light-locker or something else. Will continue investigating. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1776475 Title: Unlocking existing session often requires several attempts. Status in lightdm package in Ubuntu: New Bug description: # Context * Computer with several X sessions opened. * Users switching from one opened session to another. * Lightdm opens new greeter, wait for typing password. * User types password. * Password is accepted. * System closes the current greeter (screen gets black for an instant). # Expected * User gets back to their already opened session. # Observed * System immediately opens another greeter. * User has to type password again. # Reproducible * Not always. At times, often, at other times, rare. # Additional information Users switch session via dm-tool switch-to-user $OTHERUSER but I guess bug appears with other means (like menu item like "lock screen", etc). # Information requested lsb_release -rd Description: Ubuntu 18.04 LTS Release: 18.04 LC_ALL=C apt-cache policy lightdm lightdm: Installed: 1.26.0-0ubuntu1 Candidate: 1.26.0-0ubuntu1 Version table: *** 1.26.0-0ubuntu1 500 500 http://fr.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: lightdm 1.26.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Tue Jun 12 14:14:52 2018 ExecutablePath: /usr/sbin/lightdm InstallationDate: Installed on 2018-05-25 (18 days ago) InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: LANG=fr_FR.UTF-8 PATH=(custom, no user) SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.logrotate.d.lightdm: [modified] mtime.conffile..etc.logrotate.d.lightdm: 2018-05-25T06:19:22.081830 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1776475/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1776475] Re: Unlocking existing session often requires several attempts.
Sometimes a variant of the bug happens: after typing password, the expected session does not happen. Instead, a black screen with a white message on center, saying that session is locked and I have to wait for a moment. About 20 seconds later, a lightdm login greeter appears and only after typing the correct password *again*, I can access my session. I just experienced that variant and captured logs (journalctl) of it. I compared with journalctl logs when unlocking. Again, I don't see anything really salient in logs. I can post them here if useful. Any hint appreciated. Thanks. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1776475 Title: Unlocking existing session often requires several attempts. Status in lightdm package in Ubuntu: New Bug description: # Context * Computer with several X sessions opened. * Users switching from one opened session to another. * Lightdm opens new greeter, wait for typing password. * User types password. * Password is accepted. * System closes the current greeter (screen gets black for an instant). # Expected * User gets back to their already opened session. # Observed * System immediately opens another greeter. * User has to type password again. # Reproducible * Not always. At times, often, at other times, rare. # Additional information Users switch session via dm-tool switch-to-user $OTHERUSER but I guess bug appears with other means (like menu item like "lock screen", etc). # Information requested lsb_release -rd Description: Ubuntu 18.04 LTS Release: 18.04 LC_ALL=C apt-cache policy lightdm lightdm: Installed: 1.26.0-0ubuntu1 Candidate: 1.26.0-0ubuntu1 Version table: *** 1.26.0-0ubuntu1 500 500 http://fr.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: lightdm 1.26.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Tue Jun 12 14:14:52 2018 ExecutablePath: /usr/sbin/lightdm InstallationDate: Installed on 2018-05-25 (18 days ago) InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: LANG=fr_FR.UTF-8 PATH=(custom, no user) SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.logrotate.d.lightdm: [modified] mtime.conffile..etc.logrotate.d.lightdm: 2018-05-25T06:19:22.081830 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1776475/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1776475] Re: Unlocking existing session often requires several attempts.
Summary: twice, bug happened when service org.gtk.vfs.Daemon is activating *after* org.a11y.atspi.Registry is activated. Details below. Bug just happened again on unlocking session (versus switching users). I compared the output of journalctl. ## Around unlock time: nothing to see Around unlock time, journalctl only shows lightdm cleanup activity. Then, only when bug happens, lightdm starts again the whole sequence : systemd[somepid]: Starting User Manager for UID 110... systemd-logind[749]: New session c9 of user lightdm. systemd[somepid]: Started Session c9 of user lightdm. ... ## Around lock time: same correlation between log order and bug occurrence Again Indeed, bug happens when log is in this order: at-spi-bus-launcher[25560]: dbus-daemon[25565]: Activating service name='org.a11y.atspi.Registry' requested by ':1.0' (uid=110 pid=25557 comm="/usr/sbin/lightdm-gtk-greeter " label="unconfined") at-spi-bus-launcher[25560]: dbus-daemon[25565]: Successfully activated service 'org.a11y.atspi.Registry' at-spi-bus-launcher[25560]: SpiRegistry daemon is running with well-known name - org.a11y.atspi.Registry dbus-daemon[25559]: [session uid=110 pid=25559] Activating via systemd: service name='org.gtk.vfs.Daemon' unit='gvfs-daemon.service' requested by ':1.4' (uid=110 pid=25557 comm="/usr/sbin/lightdm-gtk-greeter " label="unconfined") and things go smoothly when log is in this order: at-spi-bus-launcher[15685]: dbus-daemon[15690]: Activating service name='org.a11y.atspi.Registry' requested by ':1.0' (uid=110 pid=15682 comm="/usr/sbin/lightdm-gtk-greeter " label="unconfined") dbus-daemon[15684]: [session uid=110 pid=15684] Activating via systemd: service name='org.gtk.vfs.Daemon' unit='gvfs-daemon.service' requested by ':1.3' (uid=110 pid=15682 comm="/usr/sbin/lightdm-gtk-greeter " label="unconfined") at-spi-bus-launcher[15685]: dbus-daemon[15690]: Successfully activated service 'org.a11y.atspi.Registry' at-spi-bus-launcher[15685]: SpiRegistry daemon is running with well-known name - org.a11y.atspi.Registry Summary: twice, bug happened when service org.gtk.vfs.Daemon is activating *after* org.a11y.atspi.Registry is activated. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1776475 Title: Unlocking existing session often requires several attempts. Status in lightdm package in Ubuntu: New Bug description: # Context * Computer with several X sessions opened. * Users switching from one opened session to another. * Lightdm opens new greeter, wait for typing password. * User types password. * Password is accepted. * System closes the current greeter (screen gets black for an instant). # Expected * User gets back to their already opened session. # Observed * System immediately opens another greeter. * User has to type password again. # Reproducible * Not always. At times, often, at other times, rare. # Additional information Users switch session via dm-tool switch-to-user $OTHERUSER but I guess bug appears with other means (like menu item like "lock screen", etc). # Information requested lsb_release -rd Description: Ubuntu 18.04 LTS Release: 18.04 LC_ALL=C apt-cache policy lightdm lightdm: Installed: 1.26.0-0ubuntu1 Candidate: 1.26.0-0ubuntu1 Version table: *** 1.26.0-0ubuntu1 500 500 http://fr.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: lightdm 1.26.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Tue Jun 12 14:14:52 2018 ExecutablePath: /usr/sbin/lightdm InstallationDate: Installed on 2018-05-25 (18 days ago) InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: LANG=fr_FR.UTF-8 PATH=(custom, no user) SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.logrotate.d.lightdm: [modified] mtime.conffile..etc.logrotate.d.lightdm: 2018-05-25T06:19:22.081830 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1776475/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1776475] Re: Unlocking existing session often requires several attempts.
** Attachment added: "Example log when things fail (bug happens)." https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1776475/+attachment/5167261/+files/2018y07m24d-16h34m12s_activite_repro_1776475_je_passe_sur_session_stephane_avec_export_xdg_seat_path__org_freedesktop_displaymanager_seat0___dm_tool_switch_to_user_stephaneexit.timestamped.log.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1776475 Title: Unlocking existing session often requires several attempts. Status in lightdm package in Ubuntu: New Bug description: # Context * Computer with several X sessions opened. * Users switching from one opened session to another. * Lightdm opens new greeter, wait for typing password. * User types password. * Password is accepted. * System closes the current greeter (screen gets black for an instant). # Expected * User gets back to their already opened session. # Observed * System immediately opens another greeter. * User has to type password again. # Reproducible * Not always. At times, often, at other times, rare. # Additional information Users switch session via dm-tool switch-to-user $OTHERUSER but I guess bug appears with other means (like menu item like "lock screen", etc). # Information requested lsb_release -rd Description: Ubuntu 18.04 LTS Release: 18.04 LC_ALL=C apt-cache policy lightdm lightdm: Installed: 1.26.0-0ubuntu1 Candidate: 1.26.0-0ubuntu1 Version table: *** 1.26.0-0ubuntu1 500 500 http://fr.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: lightdm 1.26.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Tue Jun 12 14:14:52 2018 ExecutablePath: /usr/sbin/lightdm InstallationDate: Installed on 2018-05-25 (18 days ago) InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: LANG=fr_FR.UTF-8 PATH=(custom, no user) SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.logrotate.d.lightdm: [modified] mtime.conffile..etc.logrotate.d.lightdm: 2018-05-25T06:19:22.081830 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1776475/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1776475] Re: Unlocking existing session often requires several attempts.
In order to investigate this bug, I started to write down each time I switch user and whether it works. The time information allowed to obtain time-bounded log extracts that focus on relevant parts using journalctl --since ... --until ... . After 3 "work" and one "fail" case, I observed a correlation, which might or might not be relevant. ## Logs when no bug, things work The following log sequence happens all 3 times things work okay: 2018-07-24T13:00:38.327651+0200 n551jk systemd[16387]: Startup finished in 26ms. 2018-07-24T13:00:38.327693+0200 n551jk systemd[1]: Started User Manager for UID 110. 2018-07-24T13:00:38.360247+0200 n551jk systemd[16387]: Started D-Bus User Message Bus. 2018-07-24T13:00:38.363237+0200 n551jk dbus-daemon[16407]: [session uid=110 pid=16407] AppArmor D-Bus mediation is enabled 2018-07-24T13:00:38.363739+0200 n551jk dbus-daemon[16407]: [session uid=110 pid=16407] Activating via systemd: service name='org.a11y.Bus' unit='at-spi-dbus-bus.service' requested by ':1.1' (uid=110 pid=16405 comm="/usr/sbin/lightdm-gtk-greeter " label="unconfined") 2018-07-24T13:00:38.364556+0200 n551jk systemd[16387]: Starting Accessibility services bus... 2018-07-24T13:00:38.368461+0200 n551jk dbus-daemon[16407]: [session uid=110 pid=16407] Successfully activated service 'org.a11y.Bus' 2018-07-24T13:00:38.368546+0200 n551jk systemd[16387]: Started Accessibility services bus. 2018-07-24T13:00:38.371337+0200 n551jk at-spi-bus-launcher[16408]: dbus-daemon[16413]: Activating service name='org.a11y.atspi.Registry' requested by ':1.0' (uid=110 pid=16405 comm="/usr/sbin/lightdm-gtk-greeter " label="unconfined") 2018-07-24T13:00:38.373982+0200 n551jk dbus-daemon[16407]: [session uid=110 pid=16407] Activating via systemd: service name='org.gtk.vfs.Daemon' unit='gvfs-daemon.service' requested by ':1.3' (uid=110 pid=16405 comm="/usr/sbin/lightdm-gtk-greeter " label="unconfined") 2018-07-24T13:00:38.374774+0200 n551jk at-spi-bus-launcher[16408]: dbus-daemon[16413]: Successfully activated service 'org.a11y.atspi.Registry' 2018-07-24T13:00:38.374918+0200 n551jk at-spi-bus-launcher[16408]: SpiRegistry daemon is running with well-known name - org.a11y.atspi.Registry 2018-07-24T13:00:38.375082+0200 n551jk systemd[16387]: Starting Virtual filesystem service... ## Logs when bug happens, things fail The bug happened once since I started to write down each operation, and it shows a difference: 2018-07-24T16:34:15.777621+0200 n551jk systemd[23296]: Startup finished in 23ms. 2018-07-24T16:34:15.777665+0200 n551jk systemd[1]: Started User Manager for UID 110. 2018-07-24T16:34:15.820108+0200 n551jk systemd[23296]: Started D-Bus User Message Bus. 2018-07-24T16:34:15.822959+0200 n551jk dbus-daemon[23316]: [session uid=110 pid=23316] AppArmor D-Bus mediation is enabled 2018-07-24T16:34:15.823499+0200 n551jk dbus-daemon[23316]: [session uid=110 pid=23316] Activating via systemd: service name='org.a11y.Bus' unit='at-spi-dbus-bus.service' requested by ':1.1' (uid=110 pid=23314 comm="/usr/sbin/lightdm-gtk-greeter " label="unconfined") 2018-07-24T16:34:15.824373+0200 n551jk systemd[23296]: Starting Accessibility services bus... 2018-07-24T16:34:15.828552+0200 n551jk dbus-daemon[23316]: [session uid=110 pid=23316] Successfully activated service 'org.a11y.Bus' 2018-07-24T16:34:15.828659+0200 n551jk systemd[23296]: Started Accessibility services bus. 2018-07-24T16:34:15.831689+0200 n551jk at-spi-bus-launcher[23317]: dbus-daemon[23322]: Activating service name='org.a11y.atspi.Registry' requested by ':1.0' (uid=110 pid=23314 comm="/usr/sbin/lightdm-gtk-greeter " label="unconfined") 2018-07-24T16:34:15.835154+0200 n551jk at-spi-bus-launcher[23317]: dbus-daemon[23322]: Successfully activated service 'org.a11y.atspi.Registry' 2018-07-24T16:34:15.835289+0200 n551jk at-spi-bus-launcher[23317]: SpiRegistry daemon is running with well-known name - org.a11y.atspi.Registry 2018-07-24T16:34:15.835578+0200 n551jk dbus-daemon[23316]: [session uid=110 pid=23316] Activating via systemd: service name='org.gtk.vfs.Daemon' unit='gvfs-daemon.service' requested by ':1.4' (uid=110 pid=23314 comm="/usr/sbin/lightdm-gtk-greeter " label="unconfined") 2018-07-24T16:34:15.836417+0200 n551jk systemd[23296]: Starting Virtual filesystem service... ## Difference between "work" and "fail" All 3 lines mentioning at-spi-bus-launcher come *before* : dbus-daemon ... Activating via systemd: service name='org.gtk.vfs.Daemon'. I don't know it this is relevant at this point in time. No other salient difference in logs. Logs attached. ** Attachment added: "Example log when things work." https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1776475/+attachment/5167260/+files/2018y07m24d-12h42m24s_activite_je_passe_sur_session_stephane_avec_export_xdg_seat_path__org_freedesktop_displaymanager_seat0___dm_tool_switch_to_user_stephaneexit.timestamped.log.txt -- You received this bug notification because you are a member
[Touch-packages] [Bug 1779667] Re: Unlocking existing session yields black screen. Closing session does not help as affected user cannot open a successful X session until next reboot. Other users are
## Log: soon Thanks @smcv for your feedback. I believe ubuntu-bug used to automatically attach a number of log files automatically, it appears it did not this time. Bug happens several times a week. I have captured a log. ## Workaround! I wanted to test if running another X session would work. One session type available in lightdm greeter is "xterm". So I chose that. Session opens okay and shows xterm. So, X itself is not affected. I then typed "startxfce4" in the xterm. * xfce session started quickly but something was different in the appearance, as if the screen DPI was slightly changed. * xfce4-terminal showed slightly different font. Still "Envy Code R", but different rendering, off-grid. Checking in xfce4-appearance-settings, font hinting parameter was turned off, which was not the usual settings. Setting it back using xfce4-appearance-settings got usual font back in xfce4-terminal. * thunderbird shows slightly bigger fonts than usual. I cannot compensate this exactly with xfce4-appearance-settings. dbus-daemon now runs for the user. # Conclusion (1) affected user can still run XFCE, but through a xterm session first. (2) changing title, because affected user *can* run an X session, just not XFCE session from regular lightdm. ** Summary changed: - Unlocking existing session yields black screen. Closing session does not help as affected user cannot open a successful X session until next reboot. Other users are ok. + Unlocking existing session yields black screen. Closing then reopening XFCE session shows dbus error, xterm session can run startxfce4. Other users are ok. ** Summary changed: - Unlocking existing session yields black screen. Closing then reopening XFCE session shows dbus error, xterm session can run startxfce4. Other users are ok. + Unlocking existing session yields black screen. Closing then reopening XFCE session fails with dbus error. xterm X session + startxfce4 works. Other users are ok. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dbus in Ubuntu. https://bugs.launchpad.net/bugs/1779667 Title: Unlocking existing session yields black screen. Closing then reopening XFCE session fails with dbus error. xterm X session + startxfce4 works. Other users are ok. Status in dbus package in Ubuntu: New Bug description: # Context * Xubuntu 18.04 using lightdm, no specific customization, no xscreensaver/gnome-screensaver. * Problem observed two machines: ** one machine with several users often swapping sessions, ** one machine with just one regular user who just locks/unlocks session often # Action * Open a XFCE session. * Lock it. * On greeter, type password to unlock. # Expected * Get back to opened session. # Observed * After typing password, screen turns to black. All pixels are fully black. * Not even a mouse pointer is visible. # Reproducible * Seems random. * Perhaps one time out of 20-50 unlock operations. * Never occurred in 16.04 14.04 # Detailed information From start: * On unlocking an already opened session, after typing password screen turns to full black. ## Investigation: is machine still okay? * As a sanity check, switching to text VT works, login on text VT works. ## Investigation: problem does not affect all sessions at once * Bug observed both in one system with one user at a time, and on another system with two users alternating X sessions. * From tty1, using "dm-tool switch-to-greeter" with proper environment works, allows to select other user's session, type password and return to that other user's opened session. Any attempt to return to affected user session yields black screen. ## Investigation: problem affects user even after closing all their programs * Manually killing affected user processes allows to close faulty session and see lightdm greeter come back. * Trying to reopen a session (as usual with lightdm) as affected user shows an error dialog: "Unable to contact settings server Failed to connect to socket /run/user/1000/bus: Connection refused" and a "Close" button. Clicking on it yields a second dialog : "Unable to load failsafe session Unable to determine a failsafe session name. Possible causes: xfconfd isn't running (D-Bus setup problem); environment variable $XDG_CONFIG_DIRS is set incorrectly (must include "/etc"), or xfce4-session is installed incorrectly." and a "Quit" button. Clicking "quit" button goes back to lightdm greeter. ## Investigation: reboot solves the problem * Rebooting the machine solves the problem (but closes all user sessions and processes). * Problem reappears after a few days. ## Investigation: startx affected, too * From text VT, startx has same behavior as running from lightdm and thus also cannot reach a working XFCE desktop. ## Investigation:
[Touch-packages] [Bug 1779667] Re: Unlocking existing session yields black screen. Closing session does not help as affected user cannot open a successful X session until next reboot. Other users are
Also, the problem is not specific to any user. It randomly affects any of the users of the machine. At that moment only that user is affected. Next time it may affect the same user or another. We believe that it may affect several users at a time, if we keep the machine running until problem affects a second user. In practice, however, users have some work to do, so we reboot the machine to let them continue their work. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dbus in Ubuntu. https://bugs.launchpad.net/bugs/1779667 Title: Unlocking existing session yields black screen. Closing session does not help as affected user cannot open a successful X session until next reboot. Other users are ok. Status in dbus package in Ubuntu: New Bug description: # Context * Xubuntu 18.04 using lightdm, no specific customization, no xscreensaver/gnome-screensaver. * Problem observed two machines: ** one machine with several users often swapping sessions, ** one machine with just one regular user who just locks/unlocks session often # Action * Open a XFCE session. * Lock it. * On greeter, type password to unlock. # Expected * Get back to opened session. # Observed * After typing password, screen turns to black. All pixels are fully black. * Not even a mouse pointer is visible. # Reproducible * Seems random. * Perhaps one time out of 20-50 unlock operations. * Never occurred in 16.04 14.04 # Detailed information From start: * On unlocking an already opened session, after typing password screen turns to full black. ## Investigation: is machine still okay? * As a sanity check, switching to text VT works, login on text VT works. ## Investigation: problem does not affect all sessions at once * Bug observed both in one system with one user at a time, and on another system with two users alternating X sessions. * From tty1, using "dm-tool switch-to-greeter" with proper environment works, allows to select other user's session, type password and return to that other user's opened session. Any attempt to return to affected user session yields black screen. ## Investigation: problem affects user even after closing all their programs * Manually killing affected user processes allows to close faulty session and see lightdm greeter come back. * Trying to reopen a session (as usual with lightdm) as affected user shows an error dialog: "Unable to contact settings server Failed to connect to socket /run/user/1000/bus: Connection refused" and a "Close" button. Clicking on it yields a second dialog : "Unable to load failsafe session Unable to determine a failsafe session name. Possible causes: xfconfd isn't running (D-Bus setup problem); environment variable $XDG_CONFIG_DIRS is set incorrectly (must include "/etc"), or xfce4-session is installed incorrectly." and a "Quit" button. Clicking "quit" button goes back to lightdm greeter. ## Investigation: reboot solves the problem * Rebooting the machine solves the problem (but closes all user sessions and processes). * Problem reappears after a few days. ## Investigation: startx affected, too * From text VT, startx has same behavior as running from lightdm and thus also cannot reach a working XFCE desktop. ## Investigation: affected user has no dbus-daemon running. * No "/usr/bin/dbus-daemon" runs as affected user while it runs as other users. ## Additional information * It is believed that the multi-user system makes the bug more salient than usual workflow because users switch more often from one session to another. * It is believed that the single-user system makes the bug more salient than usual workflow because users often locks and unlocks their session. 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu Description: Ubuntu 18.04 LTS Release: 18.04 Actually Xubuntu 18.04. 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center export LC_ALL=C ; apt-cache policy dbus dbus: Installed: 1.12.2-1ubuntu1 Candidate: 1.12.2-1ubuntu1 Version table: *** 1.12.2-1ubuntu1 500 500 http://fr.archive.ubuntu.com/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status 3) What you expected to happen 4) What happened instead Described above. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: dbus 1.12.2-1ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Mon Jul 2 13:43:08 2018 InstallationDate: Installed on 2018-05-25 (38 days ago) InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron:
[Touch-packages] [Bug 1779667] [NEW] Unlocking existing session yields black screen. Closing session does not help as affected user cannot open a successful X session until next reboot. Other users ar
Public bug reported: # Context * Xubuntu 18.04 using lightdm, no specific customization, no xscreensaver/gnome-screensaver. * Problem observed two machines: ** one machine with several users often swapping sessions, ** one machine with just one regular user who just locks/unlocks session often # Action * Open a XFCE session. * Lock it. * On greeter, type password to unlock. # Expected * Get back to opened session. # Observed * After typing password, screen turns to black. All pixels are fully black. * Not even a mouse pointer is visible. # Reproducible * Seems random. * Perhaps one time out of 20-50 unlock operations. * Never occurred in 16.04 14.04 # Detailed information >From start: * On unlocking an already opened session, after typing password screen turns to full black. ## Investigation: is machine still okay? * As a sanity check, switching to text VT works, login on text VT works. ## Investigation: problem does not affect all sessions at once * Bug observed both in one system with one user at a time, and on another system with two users alternating X sessions. * From tty1, using "dm-tool switch-to-greeter" with proper environment works, allows to select other user's session, type password and return to that other user's opened session. Any attempt to return to affected user session yields black screen. ## Investigation: problem affects user even after closing all their programs * Manually killing affected user processes allows to close faulty session and see lightdm greeter come back. * Trying to reopen a session (as usual with lightdm) as affected user shows an error dialog: "Unable to contact settings server Failed to connect to socket /run/user/1000/bus: Connection refused" and a "Close" button. Clicking on it yields a second dialog : "Unable to load failsafe session Unable to determine a failsafe session name. Possible causes: xfconfd isn't running (D-Bus setup problem); environment variable $XDG_CONFIG_DIRS is set incorrectly (must include "/etc"), or xfce4-session is installed incorrectly." and a "Quit" button. Clicking "quit" button goes back to lightdm greeter. ## Investigation: reboot solves the problem * Rebooting the machine solves the problem (but closes all user sessions and processes). * Problem reappears after a few days. ## Investigation: startx affected, too * From text VT, startx has same behavior as running from lightdm and thus also cannot reach a working XFCE desktop. ## Investigation: affected user has no dbus-daemon running. * No "/usr/bin/dbus-daemon" runs as affected user while it runs as other users. ## Additional information * It is believed that the multi-user system makes the bug more salient than usual workflow because users switch more often from one session to another. * It is believed that the single-user system makes the bug more salient than usual workflow because users often locks and unlocks their session. 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu Description:Ubuntu 18.04 LTS Release:18.04 Actually Xubuntu 18.04. 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center export LC_ALL=C ; apt-cache policy dbus dbus: Installed: 1.12.2-1ubuntu1 Candidate: 1.12.2-1ubuntu1 Version table: *** 1.12.2-1ubuntu1 500 500 http://fr.archive.ubuntu.com/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status 3) What you expected to happen 4) What happened instead Described above. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: dbus 1.12.2-1ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Mon Jul 2 13:43:08 2018 InstallationDate: Installed on 2018-05-25 (38 days ago) InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: dbus UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: dbus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dbus in Ubuntu. https://bugs.launchpad.net/bugs/1779667 Title: Unlocking existing session yields black screen. Closing session does not help as affected user cannot open a successful X session until next reboot. Other users are ok. Status in dbus package in Ubuntu: New Bug description: # Context * Xubuntu 18.04 using lightdm, no specific customization, no xscreensaver/gnome-screensaver. * Problem observed two machines: ** one machine with several users often swapping sessions, ** one machine with just one regular user who just locks/unlocks session often # Action * Open a XFCE session. *
[Touch-packages] [Bug 1776475] Re: Unlocking existing session often requires several attempts.
Bug still regularly observed. This is not the same bug as #1656399 though it share some characteristics. In particular, the fact that both bugs do not always occur (but somehow randomly) suggests that both are linked to a race condition somewhere in lightdm logic. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1776475 Title: Unlocking existing session often requires several attempts. Status in lightdm package in Ubuntu: New Bug description: # Context * Computer with several X sessions opened. * Users switching from one opened session to another. * Lightdm opens new greeter, wait for typing password. * User types password. * Password is accepted. * System closes the current greeter (screen gets black for an instant). # Expected * User gets back to their already opened session. # Observed * System immediately opens another greeter. * User has to type password again. # Reproducible * Not always. At times, often, at other times, rare. # Additional information Users switch session via dm-tool switch-to-user $OTHERUSER but I guess bug appears with other means (like menu item like "lock screen", etc). # Information requested lsb_release -rd Description: Ubuntu 18.04 LTS Release: 18.04 LC_ALL=C apt-cache policy lightdm lightdm: Installed: 1.26.0-0ubuntu1 Candidate: 1.26.0-0ubuntu1 Version table: *** 1.26.0-0ubuntu1 500 500 http://fr.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: lightdm 1.26.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Tue Jun 12 14:14:52 2018 ExecutablePath: /usr/sbin/lightdm InstallationDate: Installed on 2018-05-25 (18 days ago) InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: LANG=fr_FR.UTF-8 PATH=(custom, no user) SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.logrotate.d.lightdm: [modified] mtime.conffile..etc.logrotate.d.lightdm: 2018-05-25T06:19:22.081830 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1776475/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1776475] Re: Unlocking existing session often requires several attempts.
As seen in attached files, this is Xubuntu 18.04, where lightdm is default, no significant local customization. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1776475 Title: Unlocking existing session often requires several attempts. Status in lightdm package in Ubuntu: New Bug description: # Context * Computer with several X sessions opened. * Users switching from one opened session to another. * Lightdm opens new greeter, wait for typing password. * User types password. * Password is accepted. * System closes the current greeter (screen gets black for an instant). # Expected * User gets back to their already opened session. # Observed * System immediately opens another greeter. * User has to type password again. # Reproducible * Not always. At times, often, at other times, rare. # Additional information Users switch session via dm-tool switch-to-user $OTHERUSER but I guess bug appears with other means (like menu item like "lock screen", etc). # Information requested lsb_release -rd Description: Ubuntu 18.04 LTS Release: 18.04 LC_ALL=C apt-cache policy lightdm lightdm: Installed: 1.26.0-0ubuntu1 Candidate: 1.26.0-0ubuntu1 Version table: *** 1.26.0-0ubuntu1 500 500 http://fr.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: lightdm 1.26.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Tue Jun 12 14:14:52 2018 ExecutablePath: /usr/sbin/lightdm InstallationDate: Installed on 2018-05-25 (18 days ago) InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: LANG=fr_FR.UTF-8 PATH=(custom, no user) SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.logrotate.d.lightdm: [modified] mtime.conffile..etc.logrotate.d.lightdm: 2018-05-25T06:19:22.081830 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1776475/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1776475] [NEW] Unlocking existing session often requires several attempts.
Public bug reported: # Context * Computer with several X sessions opened. * Users switching from one opened session to another. * Lightdm opens new greeter, wait for typing password. * User types password. * Password is accepted. * System closes the current greeter (screen gets black for an instant). # Expected * User gets back to their already opened session. # Observed * System immediately opens another greeter. * User has to type password again. # Reproducible * Not always. At times, often, at other times, rare. # Additional information Users switch session via dm-tool switch-to-user $OTHERUSER but I guess bug appears with other means (like menu item like "lock screen", etc). # Information requested lsb_release -rd Description:Ubuntu 18.04 LTS Release:18.04 LC_ALL=C apt-cache policy lightdm lightdm: Installed: 1.26.0-0ubuntu1 Candidate: 1.26.0-0ubuntu1 Version table: *** 1.26.0-0ubuntu1 500 500 http://fr.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: lightdm 1.26.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Tue Jun 12 14:14:52 2018 ExecutablePath: /usr/sbin/lightdm InstallationDate: Installed on 2018-05-25 (18 days ago) InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: LANG=fr_FR.UTF-8 PATH=(custom, no user) SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.logrotate.d.lightdm: [modified] mtime.conffile..etc.logrotate.d.lightdm: 2018-05-25T06:19:22.081830 ** Affects: lightdm (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1776475 Title: Unlocking existing session often requires several attempts. Status in lightdm package in Ubuntu: New Bug description: # Context * Computer with several X sessions opened. * Users switching from one opened session to another. * Lightdm opens new greeter, wait for typing password. * User types password. * Password is accepted. * System closes the current greeter (screen gets black for an instant). # Expected * User gets back to their already opened session. # Observed * System immediately opens another greeter. * User has to type password again. # Reproducible * Not always. At times, often, at other times, rare. # Additional information Users switch session via dm-tool switch-to-user $OTHERUSER but I guess bug appears with other means (like menu item like "lock screen", etc). # Information requested lsb_release -rd Description: Ubuntu 18.04 LTS Release: 18.04 LC_ALL=C apt-cache policy lightdm lightdm: Installed: 1.26.0-0ubuntu1 Candidate: 1.26.0-0ubuntu1 Version table: *** 1.26.0-0ubuntu1 500 500 http://fr.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: lightdm 1.26.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Tue Jun 12 14:14:52 2018 ExecutablePath: /usr/sbin/lightdm InstallationDate: Installed on 2018-05-25 (18 days ago) InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: LANG=fr_FR.UTF-8 PATH=(custom, no user) SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.logrotate.d.lightdm: [modified] mtime.conffile..etc.logrotate.d.lightdm: 2018-05-25T06:19:22.081830 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1776475/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1547077] Re: Suspend to ram causes some glyphs to draw consistently wrong or even appear blank in gtk/gdk/pango/cairo apps. xterm/xmessage unaffected.
To add to my latest comment where I report that problem reappeared a few times in recent days: same hardware, same usage pattern, on the very re- installation of 16.04 that had the problem disappear (cf. #comment:77). Software updates applied regularly since the last near-2-years. Nothing salient would explain that, besides maybe a regression that came with a software update? -- 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/1547077 Title: Suspend to ram causes some glyphs to draw consistently wrong or even appear blank in gtk/gdk/pango/cairo apps. xterm/xmessage unaffected. Status in xorg package in Ubuntu: Triaged Bug description: # Summary * Some glyphs badly drawn at some moments. * When happens, same glyph drawn on various windows shows same corruption. * Problem comes and go. Cannot use nvidia proprietary driver as a workaround (does not work at all). # Context Laptop, using "intel" (or "nouveau" ?) driver. Expected: all glyphs rendered correctly. Observed: some glyphs not rendered correctly * reproducible: sometimes, eventually. Problem comes and go, severity varies from one glyph (see 2016y02m17d_18h08m27s_0100Z_x_bug_glyph_firefox_gnome_org.png ) to all text on screen fully unreadable (see 2016y02m10d_18h42m18s_0100Z_wow_screen_flickers_and_most_glyphs_wrong_01.png ) * *some* glyphs are affected. For example, letter 'a' of a certain size will be replaced by colored garbage at many places where it appears (see 2016y02m18d_16h05m35s_0100Z_same_corruption_on_different_windows.png ), but other 'a' with different size, italic, bold, etc will be unaffected. * in some applications (e.g. xfce whisker menu), some glyphs are rendered correctly or not depending on the direction of mouse hovering. See video 2016y02m16d_21h41m14s_0100Z_whisker_menu_missing_glyphs.mp4 . * in menu of gtk application, some glyphs are "fixed" by opening the menu, but not all. For example, in xfce4-terminal, letter A of "Affichage" and its menu content as well as "Aide" is affected. Opening "Affichage" menu does not fix anything. Opening "Aide" menu fixes the "A" of "Aide". Changing window size reactivates the bug on "A" or "Aide". See video 2016y02m18d_16h14m25s_0100Z_glyph-redrawn- bug.mp4 . * text under icons on desktop is affected, but shadows are not. See 2016y02m16d_21h32m11s_0100Z_x_bug_reenabling_antialias_reactivates_problem_shadow_unaffected.png # Affected applications * xfce whisker menu, * xfce4-terminal (nealy all screenshots) * firefox (see 2016y02m17d_18h08m27s_0100Z_x_bug_glyph_firefox_gnome_org.png 2016y02m16d_21h32m11s_0100Z_x_bug_reenabling_antialias_reactivates_problem_shadow_unaffected.png ), * thunderbird (see 2016y02m16d_21h28m35s_0100Z_x_bug_affects_thunderbird_terminal.png ), * emacs (see 2016y02m10d_18h41m49s_0100Z_wow_screen_flickers_and_most_glyphs_wrong_00.png and subsequent ), * superswitcher ( a gtk/gdk app) * *NOT* affected: xterm, xmessage. Perhaps only gtk/gdk/pango/cairo apps are affected. # Additional information This looks like a cache corruption somewhere. On IRC #pango, someone suggested a bug in Intel driver. Running `xfce4-appearance-settings` and there changing any of: * antialiasing enable/disable, * hinting strength, * subpixel alignment * or dpi immediately cures the bug (see 2016y02m16d_21h31m52s_0100Z_x_bug_disabling_antialias_immediately_cures_problem.png ) Setting back the exact same parameters immediately reactivates the bug (see 2016y02m16d_21h32m11s_0100Z_x_bug_reenabling_antialias_reactivates_problem_shadow_unaffected.png). It is believed that keeping any new settings for a while will have the bug reoccur. It is not like bug 1536751. That one affects rendering quality of *all* glyphs, at all times, depending on dpi. This is not the case here: *some* glyphs (randomly chosen) are drawn corrupted (replaced by garbage or absent), not always. --- ApportVersion: 2.20-0ubuntu3 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: XFCE DistUpgraded: Fresh install DistroCodename: xenial DistroRelease: Ubuntu 16.04 DistroVariant: ubuntu DkmsStatus: virtualbox, 5.0.14, 4.4.0-8-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. 4th Gen Core Processor Integrated Graphics Controller [1043:177d] Subsystem: ASUSTeK Computer Inc. GM107M [GeForce GTX 850M] [1043:177d] InstallationDate: Installed on 2016-02-03 (26 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial
[Touch-packages] [Bug 1547077] Re: Suspend to ram causes some glyphs to draw consistently wrong or even appear blank in gtk/gdk/pango/cairo apps. xterm/xmessage unaffected.
Interestingly, thus bug started to reappear in its extreme form: a few times in the past days, all letters disappeared in my xfce4-terminals. Workaround was to close and reopen session. -- 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/1547077 Title: Suspend to ram causes some glyphs to draw consistently wrong or even appear blank in gtk/gdk/pango/cairo apps. xterm/xmessage unaffected. Status in xorg package in Ubuntu: Triaged Bug description: # Summary * Some glyphs badly drawn at some moments. * When happens, same glyph drawn on various windows shows same corruption. * Problem comes and go. Cannot use nvidia proprietary driver as a workaround (does not work at all). # Context Laptop, using "intel" (or "nouveau" ?) driver. Expected: all glyphs rendered correctly. Observed: some glyphs not rendered correctly * reproducible: sometimes, eventually. Problem comes and go, severity varies from one glyph (see 2016y02m17d_18h08m27s_0100Z_x_bug_glyph_firefox_gnome_org.png ) to all text on screen fully unreadable (see 2016y02m10d_18h42m18s_0100Z_wow_screen_flickers_and_most_glyphs_wrong_01.png ) * *some* glyphs are affected. For example, letter 'a' of a certain size will be replaced by colored garbage at many places where it appears (see 2016y02m18d_16h05m35s_0100Z_same_corruption_on_different_windows.png ), but other 'a' with different size, italic, bold, etc will be unaffected. * in some applications (e.g. xfce whisker menu), some glyphs are rendered correctly or not depending on the direction of mouse hovering. See video 2016y02m16d_21h41m14s_0100Z_whisker_menu_missing_glyphs.mp4 . * in menu of gtk application, some glyphs are "fixed" by opening the menu, but not all. For example, in xfce4-terminal, letter A of "Affichage" and its menu content as well as "Aide" is affected. Opening "Affichage" menu does not fix anything. Opening "Aide" menu fixes the "A" of "Aide". Changing window size reactivates the bug on "A" or "Aide". See video 2016y02m18d_16h14m25s_0100Z_glyph-redrawn- bug.mp4 . * text under icons on desktop is affected, but shadows are not. See 2016y02m16d_21h32m11s_0100Z_x_bug_reenabling_antialias_reactivates_problem_shadow_unaffected.png # Affected applications * xfce whisker menu, * xfce4-terminal (nealy all screenshots) * firefox (see 2016y02m17d_18h08m27s_0100Z_x_bug_glyph_firefox_gnome_org.png 2016y02m16d_21h32m11s_0100Z_x_bug_reenabling_antialias_reactivates_problem_shadow_unaffected.png ), * thunderbird (see 2016y02m16d_21h28m35s_0100Z_x_bug_affects_thunderbird_terminal.png ), * emacs (see 2016y02m10d_18h41m49s_0100Z_wow_screen_flickers_and_most_glyphs_wrong_00.png and subsequent ), * superswitcher ( a gtk/gdk app) * *NOT* affected: xterm, xmessage. Perhaps only gtk/gdk/pango/cairo apps are affected. # Additional information This looks like a cache corruption somewhere. On IRC #pango, someone suggested a bug in Intel driver. Running `xfce4-appearance-settings` and there changing any of: * antialiasing enable/disable, * hinting strength, * subpixel alignment * or dpi immediately cures the bug (see 2016y02m16d_21h31m52s_0100Z_x_bug_disabling_antialias_immediately_cures_problem.png ) Setting back the exact same parameters immediately reactivates the bug (see 2016y02m16d_21h32m11s_0100Z_x_bug_reenabling_antialias_reactivates_problem_shadow_unaffected.png). It is believed that keeping any new settings for a while will have the bug reoccur. It is not like bug 1536751. That one affects rendering quality of *all* glyphs, at all times, depending on dpi. This is not the case here: *some* glyphs (randomly chosen) are drawn corrupted (replaced by garbage or absent), not always. --- ApportVersion: 2.20-0ubuntu3 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: XFCE DistUpgraded: Fresh install DistroCodename: xenial DistroRelease: Ubuntu 16.04 DistroVariant: ubuntu DkmsStatus: virtualbox, 5.0.14, 4.4.0-8-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. 4th Gen Core Processor Integrated Graphics Controller [1043:177d] Subsystem: ASUSTeK Computer Inc. GM107M [GeForce GTX 850M] [1043:177d] InstallationDate: Installed on 2016-02-03 (26 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160203) MachineType: ASUSTeK COMPUTER INC. N551JK Package: xorg 1:7.7+13ubuntu1 PackageArchitecture: amd64 ProcKernelCmdLine:
[Touch-packages] [Bug 1052360] Re: unattended-upgrade crashed with SystemError: E:Sub-process /usr/bin/dpkg returned an error code (2) for an unknown reason
Hello. Seen a crash report window appear on Ubuntu 16.04, mentioning DuplicateOf https://bugs.launchpad.net/bugs/1052360 . Also received the "unattended-upgrade" mail as usual. It said: > Écriture du journal de dpkg dans « > /var/log/unattended-upgrades/unattended-upgrades-dpkg.log » > Échec de l'installation des mises à niveau ! > message d'erreur : « installArchives() failed » > Dpkg a retourné une erreur ! Voir « > /var/log/unattended-upgrades/unattended-upgrades-dpkg.log » pour les détails Besides, /var/log/unattended-upgrades/unattended-upgrades-dpkg.log was > Log started: 2017-09-02 06:34:22 > Error in function: install > Log ended: 2017-09-02 06:34:22 > > Log started: 2017-09-04 06:08:45 > Error in function: install > Log ended: 2017-09-04 06:08:45 So, no real clue here either. Seen comment #24. Hard to open a new bug with so few information. Perhaps the *real* bug is that code paths don't propagate errors with enough details to allow proper tracing of what happends when things fail? My 2 cents. :-) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1052360 Title: unattended-upgrade crashed with SystemError: E:Sub-process /usr/bin/dpkg returned an error code (2) for an unknown reason Status in unattended-upgrades package in Ubuntu: Invalid Bug description: Happens by itself ProblemType: Crash DistroRelease: Ubuntu 11.10 Package: unattended-upgrades 0.73ubuntu1.1 ProcVersionSignature: Ubuntu 3.0.0-26.42-generic 3.0.42 Uname: Linux 3.0.0-26-generic i686 ApportVersion: 1.23-0ubuntu4 Architecture: i386 Date: Tue Sep 18 09:24:15 2012 ExecutablePath: /usr/bin/unattended-upgrade InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111012) InterpreterPath: /usr/bin/python2.7 PackageArchitecture: all ProcCmdline: /usr/bin/python /usr/bin/unattended-upgrade ProcEnviron: LANGUAGE=en_US:en PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/sh PythonArgs: ['/usr/bin/unattended-upgrade'] SourcePackage: unattended-upgrades Title: unattended-upgrade crashed with SystemError: E:Sub-process /usr/bin/dpkg returned an error code (2) Traceback: SystemError: E:Sub-process /usr/bin/dpkg returned an error code (2) UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: mtime.conffile..etc.apt.apt.conf.d.50unattended.upgrades: 2012-08-24T13:58:31.952771 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1052360/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 223133] Re: wrong volume interactions
On re-reading the original post (which is not very clear), I'm wondering if it's same problem. My problem is not on VLC-specific volume in pulseaudio (or any other app), rather on the master volume (hardware-specific). So, perhaps it's not the same problem. Anyway, many things have probably changed since Karmic and this bug report. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/223133 Title: wrong volume interactions Status in pulseaudio package in Ubuntu: Won't Fix Bug description: Binary package hint: pulseaudio I have the front slider at maximum volume. I have the PCM slider at 72% volume. I have the VLC internal slider at maximum volume. In PulseAudio Volume Control when I put a volume for VLC to 27% it's to loud, than I put a volume at 26% an I don't have any sound !! The volume will be probably added instance of multiply. And it will be grate to have volumes in dB ;-) For example we can have a fader from -80 dB to 0 dB with a linear part for to first "8.68588963806504 dB" to don't have any angle. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/223133/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 223133] Re: wrong volume interactions
On a USB audio adapter 0d8c:000c "C-Media Electronics, Inc. Audio Adapter", I experience same problem as original report and comment #2. Links at comment #3 no longer exist. I can't correlate with comment #4 and #5. To me, original report and comment #2 only mention an annoyance on a specific volume slider, nothing related to unifying volume or whatever. What can we do? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/223133 Title: wrong volume interactions Status in pulseaudio package in Ubuntu: Won't Fix Bug description: Binary package hint: pulseaudio I have the front slider at maximum volume. I have the PCM slider at 72% volume. I have the VLC internal slider at maximum volume. In PulseAudio Volume Control when I put a volume for VLC to 27% it's to loud, than I put a volume at 26% an I don't have any sound !! The volume will be probably added instance of multiply. And it will be grate to have volumes in dB ;-) For example we can have a fader from -80 dB to 0 dB with a linear part for to first "8.68588963806504 dB" to don't have any angle. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/223133/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 759394] Re: can not umount rbind mounts
Hi. Same problem here. Some partitions still appear in `mount` output and `/proc/mounts` but can't be unmounted via either device name or mount point. Repeatedly trying `umount -l` with device names and mount points finally managed to get the partitions unmounted. Yet it feels awkward, like a worn out door lock that locks okay but you have to shake for a while to have it unlock. This is very likely not Ubuntu specific, e.g. http://unix.stackexchange.com/questions/120827/recursive-umount-after-rbind-mount -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/759394 Title: can not umount rbind mounts Status in util-linux package in Ubuntu: Confirmed Bug description: Binary package hint: util-linux mkdir /mnt/dev mount --rbind /dev /mnt/dev umount /mnt/dev The umount fails because of the sub mounts that the recursive bind also bind mounted under /mnt/dev, which you have to remove manually first. When you mount with --rbind, umount should be able to reverse the process, unmounting all recursively bound mounts. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/759394/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1547077] Re: Suspend to ram causes some glyphs to draw consistently wrong or even appear blank in gtk/gdk/pango/cairo apps. xterm/xmessage unaffected.
Regarding new bug, subscribed to https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video- intel/+bug/1568604 . Will notify if I still observed this bug (1547077). I don't understand why this bug no longer happens (which is good anyway). xserver-xorg-video-nouveau is still 1:1.0.12-1build2 Perhaps bug is actually in another package and was fixed? @gr-ubuntu-0 are you still affected? -- 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/1547077 Title: Suspend to ram causes some glyphs to draw consistently wrong or even appear blank in gtk/gdk/pango/cairo apps. xterm/xmessage unaffected. Status in xorg package in Ubuntu: Triaged Bug description: # Summary * Some glyphs badly drawn at some moments. * When happens, same glyph drawn on various windows shows same corruption. * Problem comes and go. Cannot use nvidia proprietary driver as a workaround (does not work at all). # Context Laptop, using "intel" (or "nouveau" ?) driver. Expected: all glyphs rendered correctly. Observed: some glyphs not rendered correctly * reproducible: sometimes, eventually. Problem comes and go, severity varies from one glyph (see 2016y02m17d_18h08m27s_0100Z_x_bug_glyph_firefox_gnome_org.png ) to all text on screen fully unreadable (see 2016y02m10d_18h42m18s_0100Z_wow_screen_flickers_and_most_glyphs_wrong_01.png ) * *some* glyphs are affected. For example, letter 'a' of a certain size will be replaced by colored garbage at many places where it appears (see 2016y02m18d_16h05m35s_0100Z_same_corruption_on_different_windows.png ), but other 'a' with different size, italic, bold, etc will be unaffected. * in some applications (e.g. xfce whisker menu), some glyphs are rendered correctly or not depending on the direction of mouse hovering. See video 2016y02m16d_21h41m14s_0100Z_whisker_menu_missing_glyphs.mp4 . * in menu of gtk application, some glyphs are "fixed" by opening the menu, but not all. For example, in xfce4-terminal, letter A of "Affichage" and its menu content as well as "Aide" is affected. Opening "Affichage" menu does not fix anything. Opening "Aide" menu fixes the "A" of "Aide". Changing window size reactivates the bug on "A" or "Aide". See video 2016y02m18d_16h14m25s_0100Z_glyph-redrawn- bug.mp4 . * text under icons on desktop is affected, but shadows are not. See 2016y02m16d_21h32m11s_0100Z_x_bug_reenabling_antialias_reactivates_problem_shadow_unaffected.png # Affected applications * xfce whisker menu, * xfce4-terminal (nealy all screenshots) * firefox (see 2016y02m17d_18h08m27s_0100Z_x_bug_glyph_firefox_gnome_org.png 2016y02m16d_21h32m11s_0100Z_x_bug_reenabling_antialias_reactivates_problem_shadow_unaffected.png ), * thunderbird (see 2016y02m16d_21h28m35s_0100Z_x_bug_affects_thunderbird_terminal.png ), * emacs (see 2016y02m10d_18h41m49s_0100Z_wow_screen_flickers_and_most_glyphs_wrong_00.png and subsequent ), * superswitcher ( a gtk/gdk app) * *NOT* affected: xterm, xmessage. Perhaps only gtk/gdk/pango/cairo apps are affected. # Additional information This looks like a cache corruption somewhere. On IRC #pango, someone suggested a bug in Intel driver. Running `xfce4-appearance-settings` and there changing any of: * antialiasing enable/disable, * hinting strength, * subpixel alignment * or dpi immediately cures the bug (see 2016y02m16d_21h31m52s_0100Z_x_bug_disabling_antialias_immediately_cures_problem.png ) Setting back the exact same parameters immediately reactivates the bug (see 2016y02m16d_21h32m11s_0100Z_x_bug_reenabling_antialias_reactivates_problem_shadow_unaffected.png). It is believed that keeping any new settings for a while will have the bug reoccur. It is not like bug 1536751. That one affects rendering quality of *all* glyphs, at all times, depending on dpi. This is not the case here: *some* glyphs (randomly chosen) are drawn corrupted (replaced by garbage or absent), not always. --- ApportVersion: 2.20-0ubuntu3 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: XFCE DistUpgraded: Fresh install DistroCodename: xenial DistroRelease: Ubuntu 16.04 DistroVariant: ubuntu DkmsStatus: virtualbox, 5.0.14, 4.4.0-8-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. 4th Gen Core Processor Integrated Graphics Controller [1043:177d] Subsystem: ASUSTeK Computer Inc. GM107M [GeForce GTX 850M] [1043:177d] InstallationDate: Installed on 2016-02-03 (26 days ago) InstallationMedia: Xubuntu 16.04
[Touch-packages] [Bug 1547077] Re: Suspend to ram causes some glyphs to draw consistently wrong or even appear blank in gtk/gdk/pango/cairo apps. xterm/xmessage unaffected.
Summary: on reinstall on same CPU/motherboard/etc (only storage changed), bug no longer observed. Hello, After observing problems on the main storage of the laptop where the bug was observed, I bought a new storage and installed Ubuntu 16.04 from scratch on the new storage but the same laptop. Surprisingly, this bug **no longer happens**, but another one happens instead, which is much less of a problem. The new bug symptom is: after lock/unlock, the mouse pointer no longer appears. Mouse features actually work, as one can see hover effects on buttons and menu items, semi-blindly click, etc. An efficient workaround is to press Ctrl- Alt-F1 then Ctrl-Alt-F7, and voilà mouse pointer is back again. LC_ALL=C lshw -c video 2>/dev/null | grep configuration configuration: driver=nouveau latency=0 configuration: driver=i915 latency=0 -- 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/1547077 Title: Suspend to ram causes some glyphs to draw consistently wrong or even appear blank in gtk/gdk/pango/cairo apps. xterm/xmessage unaffected. Status in xorg package in Ubuntu: Triaged Bug description: # Summary * Some glyphs badly drawn at some moments. * When happens, same glyph drawn on various windows shows same corruption. * Problem comes and go. Cannot use nvidia proprietary driver as a workaround (does not work at all). # Context Laptop, using "intel" (or "nouveau" ?) driver. Expected: all glyphs rendered correctly. Observed: some glyphs not rendered correctly * reproducible: sometimes, eventually. Problem comes and go, severity varies from one glyph (see 2016y02m17d_18h08m27s_0100Z_x_bug_glyph_firefox_gnome_org.png ) to all text on screen fully unreadable (see 2016y02m10d_18h42m18s_0100Z_wow_screen_flickers_and_most_glyphs_wrong_01.png ) * *some* glyphs are affected. For example, letter 'a' of a certain size will be replaced by colored garbage at many places where it appears (see 2016y02m18d_16h05m35s_0100Z_same_corruption_on_different_windows.png ), but other 'a' with different size, italic, bold, etc will be unaffected. * in some applications (e.g. xfce whisker menu), some glyphs are rendered correctly or not depending on the direction of mouse hovering. See video 2016y02m16d_21h41m14s_0100Z_whisker_menu_missing_glyphs.mp4 . * in menu of gtk application, some glyphs are "fixed" by opening the menu, but not all. For example, in xfce4-terminal, letter A of "Affichage" and its menu content as well as "Aide" is affected. Opening "Affichage" menu does not fix anything. Opening "Aide" menu fixes the "A" of "Aide". Changing window size reactivates the bug on "A" or "Aide". See video 2016y02m18d_16h14m25s_0100Z_glyph-redrawn- bug.mp4 . * text under icons on desktop is affected, but shadows are not. See 2016y02m16d_21h32m11s_0100Z_x_bug_reenabling_antialias_reactivates_problem_shadow_unaffected.png # Affected applications * xfce whisker menu, * xfce4-terminal (nealy all screenshots) * firefox (see 2016y02m17d_18h08m27s_0100Z_x_bug_glyph_firefox_gnome_org.png 2016y02m16d_21h32m11s_0100Z_x_bug_reenabling_antialias_reactivates_problem_shadow_unaffected.png ), * thunderbird (see 2016y02m16d_21h28m35s_0100Z_x_bug_affects_thunderbird_terminal.png ), * emacs (see 2016y02m10d_18h41m49s_0100Z_wow_screen_flickers_and_most_glyphs_wrong_00.png and subsequent ), * superswitcher ( a gtk/gdk app) * *NOT* affected: xterm, xmessage. Perhaps only gtk/gdk/pango/cairo apps are affected. # Additional information This looks like a cache corruption somewhere. On IRC #pango, someone suggested a bug in Intel driver. Running `xfce4-appearance-settings` and there changing any of: * antialiasing enable/disable, * hinting strength, * subpixel alignment * or dpi immediately cures the bug (see 2016y02m16d_21h31m52s_0100Z_x_bug_disabling_antialias_immediately_cures_problem.png ) Setting back the exact same parameters immediately reactivates the bug (see 2016y02m16d_21h32m11s_0100Z_x_bug_reenabling_antialias_reactivates_problem_shadow_unaffected.png). It is believed that keeping any new settings for a while will have the bug reoccur. It is not like bug 1536751. That one affects rendering quality of *all* glyphs, at all times, depending on dpi. This is not the case here: *some* glyphs (randomly chosen) are drawn corrupted (replaced by garbage or absent), not always. --- ApportVersion: 2.20-0ubuntu3 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: XFCE DistUpgraded: Fresh install DistroCodename: xenial DistroRelease: Ubuntu 16.04 DistroVariant: ubuntu DkmsStatus: virtualbox, 5.0.14, 4.4.0-8-generic, x86_64: installed ExtraDebuggingInterest:
[Touch-packages] [Bug 1547077] Re: Suspend to ram causes some glyphs to draw consistently wrong or even appear blank in gtk/gdk/pango/cairo apps. xterm/xmessage unaffected.
Thanks again @gr-ubuntu-0 . This is interesting. Indeed your XorgLog.txt does not mention nouveau, only Intel. My xorg.log mentions both. Following https://askubuntu.com/questions/23238/how-can-i-find-what- video-driver-is-in-use-on-my-system it looks like I'm really using nouveau driver. LC_ALL=C lshw -c video 2>/dev/null | grep configuration configuration: driver=nouveau latency=0 configuration: driver=i915 latency=0 @penalvch does this tell something about where the bug is? May it not be in nouveau, after all? -- 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/1547077 Title: Suspend to ram causes some glyphs to draw consistently wrong or even appear blank in gtk/gdk/pango/cairo apps. xterm/xmessage unaffected. Status in xorg package in Ubuntu: Triaged Bug description: # Summary * Some glyphs badly drawn at some moments. * When happens, same glyph drawn on various windows shows same corruption. * Problem comes and go. Cannot use nvidia proprietary driver as a workaround (does not work at all). # Context Laptop, using "intel" (or "nouveau" ?) driver. Expected: all glyphs rendered correctly. Observed: some glyphs not rendered correctly * reproducible: sometimes, eventually. Problem comes and go, severity varies from one glyph (see 2016y02m17d_18h08m27s_0100Z_x_bug_glyph_firefox_gnome_org.png ) to all text on screen fully unreadable (see 2016y02m10d_18h42m18s_0100Z_wow_screen_flickers_and_most_glyphs_wrong_01.png ) * *some* glyphs are affected. For example, letter 'a' of a certain size will be replaced by colored garbage at many places where it appears (see 2016y02m18d_16h05m35s_0100Z_same_corruption_on_different_windows.png ), but other 'a' with different size, italic, bold, etc will be unaffected. * in some applications (e.g. xfce whisker menu), some glyphs are rendered correctly or not depending on the direction of mouse hovering. See video 2016y02m16d_21h41m14s_0100Z_whisker_menu_missing_glyphs.mp4 . * in menu of gtk application, some glyphs are "fixed" by opening the menu, but not all. For example, in xfce4-terminal, letter A of "Affichage" and its menu content as well as "Aide" is affected. Opening "Affichage" menu does not fix anything. Opening "Aide" menu fixes the "A" of "Aide". Changing window size reactivates the bug on "A" or "Aide". See video 2016y02m18d_16h14m25s_0100Z_glyph-redrawn- bug.mp4 . * text under icons on desktop is affected, but shadows are not. See 2016y02m16d_21h32m11s_0100Z_x_bug_reenabling_antialias_reactivates_problem_shadow_unaffected.png # Affected applications * xfce whisker menu, * xfce4-terminal (nealy all screenshots) * firefox (see 2016y02m17d_18h08m27s_0100Z_x_bug_glyph_firefox_gnome_org.png 2016y02m16d_21h32m11s_0100Z_x_bug_reenabling_antialias_reactivates_problem_shadow_unaffected.png ), * thunderbird (see 2016y02m16d_21h28m35s_0100Z_x_bug_affects_thunderbird_terminal.png ), * emacs (see 2016y02m10d_18h41m49s_0100Z_wow_screen_flickers_and_most_glyphs_wrong_00.png and subsequent ), * superswitcher ( a gtk/gdk app) * *NOT* affected: xterm, xmessage. Perhaps only gtk/gdk/pango/cairo apps are affected. # Additional information This looks like a cache corruption somewhere. On IRC #pango, someone suggested a bug in Intel driver. Running `xfce4-appearance-settings` and there changing any of: * antialiasing enable/disable, * hinting strength, * subpixel alignment * or dpi immediately cures the bug (see 2016y02m16d_21h31m52s_0100Z_x_bug_disabling_antialias_immediately_cures_problem.png ) Setting back the exact same parameters immediately reactivates the bug (see 2016y02m16d_21h32m11s_0100Z_x_bug_reenabling_antialias_reactivates_problem_shadow_unaffected.png). It is believed that keeping any new settings for a while will have the bug reoccur. It is not like bug 1536751. That one affects rendering quality of *all* glyphs, at all times, depending on dpi. This is not the case here: *some* glyphs (randomly chosen) are drawn corrupted (replaced by garbage or absent), not always. --- ApportVersion: 2.20-0ubuntu3 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: XFCE DistUpgraded: Fresh install DistroCodename: xenial DistroRelease: Ubuntu 16.04 DistroVariant: ubuntu DkmsStatus: virtualbox, 5.0.14, 4.4.0-8-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. 4th Gen Core Processor Integrated Graphics Controller [1043:177d] Subsystem: ASUSTeK
[Touch-packages] [Bug 1547077] Re: Suspend to ram causes some glyphs to draw consistently wrong or even appear blank in gtk/gdk/pango/cairo apps. xterm/xmessage unaffected.
@gr-ubuntu-0 thanks for reporting, it looks like it's the same issue indeed. @gr-ubuntu-0 can you mark the bug as affecting you? It is important for confirmation and prioritization. Christopher wrote: > #53 gouri, could you please provide the bugzilla number for the report you filed? @penalvch I have not completed the steps to reporting the bug upstream. I agree it would be the next best step but I cannot do it at the moment (drowned under other tasks). If anyone can do it, it would certainly help. Instructions are on comments 49 and steps done so far are on comment 50. https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1547077/comments/49 https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1547077/comments/50 Regards. -- 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/1547077 Title: Suspend to ram causes some glyphs to draw consistently wrong or even appear blank in gtk/gdk/pango/cairo apps. xterm/xmessage unaffected. Status in xorg package in Ubuntu: Triaged Bug description: # Summary * Some glyphs badly drawn at some moments. * When happens, same glyph drawn on various windows shows same corruption. * Problem comes and go. Cannot use nvidia proprietary driver as a workaround (does not work at all). # Context Laptop, using "intel" (or "nouveau" ?) driver. Expected: all glyphs rendered correctly. Observed: some glyphs not rendered correctly * reproducible: sometimes, eventually. Problem comes and go, severity varies from one glyph (see 2016y02m17d_18h08m27s_0100Z_x_bug_glyph_firefox_gnome_org.png ) to all text on screen fully unreadable (see 2016y02m10d_18h42m18s_0100Z_wow_screen_flickers_and_most_glyphs_wrong_01.png ) * *some* glyphs are affected. For example, letter 'a' of a certain size will be replaced by colored garbage at many places where it appears (see 2016y02m18d_16h05m35s_0100Z_same_corruption_on_different_windows.png ), but other 'a' with different size, italic, bold, etc will be unaffected. * in some applications (e.g. xfce whisker menu), some glyphs are rendered correctly or not depending on the direction of mouse hovering. See video 2016y02m16d_21h41m14s_0100Z_whisker_menu_missing_glyphs.mp4 . * in menu of gtk application, some glyphs are "fixed" by opening the menu, but not all. For example, in xfce4-terminal, letter A of "Affichage" and its menu content as well as "Aide" is affected. Opening "Affichage" menu does not fix anything. Opening "Aide" menu fixes the "A" of "Aide". Changing window size reactivates the bug on "A" or "Aide". See video 2016y02m18d_16h14m25s_0100Z_glyph-redrawn- bug.mp4 . * text under icons on desktop is affected, but shadows are not. See 2016y02m16d_21h32m11s_0100Z_x_bug_reenabling_antialias_reactivates_problem_shadow_unaffected.png # Affected applications * xfce whisker menu, * xfce4-terminal (nealy all screenshots) * firefox (see 2016y02m17d_18h08m27s_0100Z_x_bug_glyph_firefox_gnome_org.png 2016y02m16d_21h32m11s_0100Z_x_bug_reenabling_antialias_reactivates_problem_shadow_unaffected.png ), * thunderbird (see 2016y02m16d_21h28m35s_0100Z_x_bug_affects_thunderbird_terminal.png ), * emacs (see 2016y02m10d_18h41m49s_0100Z_wow_screen_flickers_and_most_glyphs_wrong_00.png and subsequent ), * superswitcher ( a gtk/gdk app) * *NOT* affected: xterm, xmessage. Perhaps only gtk/gdk/pango/cairo apps are affected. # Additional information This looks like a cache corruption somewhere. On IRC #pango, someone suggested a bug in Intel driver. Running `xfce4-appearance-settings` and there changing any of: * antialiasing enable/disable, * hinting strength, * subpixel alignment * or dpi immediately cures the bug (see 2016y02m16d_21h31m52s_0100Z_x_bug_disabling_antialias_immediately_cures_problem.png ) Setting back the exact same parameters immediately reactivates the bug (see 2016y02m16d_21h32m11s_0100Z_x_bug_reenabling_antialias_reactivates_problem_shadow_unaffected.png). It is believed that keeping any new settings for a while will have the bug reoccur. It is not like bug 1536751. That one affects rendering quality of *all* glyphs, at all times, depending on dpi. This is not the case here: *some* glyphs (randomly chosen) are drawn corrupted (replaced by garbage or absent), not always. --- ApportVersion: 2.20-0ubuntu3 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: XFCE DistUpgraded: Fresh install DistroCodename: xenial DistroRelease: Ubuntu 16.04 DistroVariant: ubuntu DkmsStatus: virtualbox, 5.0.14, 4.4.0-8-generic, x86_64: installed ExtraDebuggingInterest: Yes
[Touch-packages] [Bug 1547077] Re: Suspend to ram causes some glyphs to draw consistently wrong or even appear blank in gtk/gdk/pango/cairo apps. xterm/xmessage unaffected.
** Summary changed: - Some glyphs drawn consistently wrong, bug comes and go + Suspend to ram causes some glyphs to draw consistently wrong or even appear blank in gtk/gdk/pango/cairo apps. xterm/xmessage unaffected. -- 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/1547077 Title: Suspend to ram causes some glyphs to draw consistently wrong or even appear blank in gtk/gdk/pango/cairo apps. xterm/xmessage unaffected. Status in xorg package in Ubuntu: Triaged Bug description: # Summary * Some glyphs badly drawn at some moments. * When happens, same glyph drawn on various windows shows same corruption. * Problem comes and go. Cannot use nvidia proprietary driver as a workaround (does not work at all). # Context Laptop, using "intel" (or "nouveau" ?) driver. Expected: all glyphs rendered correctly. Observed: some glyphs not rendered correctly * reproducible: sometimes, eventually. Problem comes and go, severity varies from one glyph (see 2016y02m17d_18h08m27s_0100Z_x_bug_glyph_firefox_gnome_org.png ) to all text on screen fully unreadable (see 2016y02m10d_18h42m18s_0100Z_wow_screen_flickers_and_most_glyphs_wrong_01.png ) * *some* glyphs are affected. For example, letter 'a' of a certain size will be replaced by colored garbage at many places where it appears (see 2016y02m18d_16h05m35s_0100Z_same_corruption_on_different_windows.png ), but other 'a' with different size, italic, bold, etc will be unaffected. * in some applications (e.g. xfce whisker menu), some glyphs are rendered correctly or not depending on the direction of mouse hovering. See video 2016y02m16d_21h41m14s_0100Z_whisker_menu_missing_glyphs.mp4 . * in menu of gtk application, some glyphs are "fixed" by opening the menu, but not all. For example, in xfce4-terminal, letter A of "Affichage" and its menu content as well as "Aide" is affected. Opening "Affichage" menu does not fix anything. Opening "Aide" menu fixes the "A" of "Aide". Changing window size reactivates the bug on "A" or "Aide". See video 2016y02m18d_16h14m25s_0100Z_glyph-redrawn- bug.mp4 . * text under icons on desktop is affected, but shadows are not. See 2016y02m16d_21h32m11s_0100Z_x_bug_reenabling_antialias_reactivates_problem_shadow_unaffected.png # Affected applications * xfce whisker menu, * xfce4-terminal (nealy all screenshots) * firefox (see 2016y02m17d_18h08m27s_0100Z_x_bug_glyph_firefox_gnome_org.png 2016y02m16d_21h32m11s_0100Z_x_bug_reenabling_antialias_reactivates_problem_shadow_unaffected.png ), * thunderbird (see 2016y02m16d_21h28m35s_0100Z_x_bug_affects_thunderbird_terminal.png ), * emacs (see 2016y02m10d_18h41m49s_0100Z_wow_screen_flickers_and_most_glyphs_wrong_00.png and subsequent ), * superswitcher ( a gtk/gdk app) * *NOT* affected: xterm, xmessage. Perhaps only gtk/gdk/pango/cairo apps are affected. # Additional information This looks like a cache corruption somewhere. On IRC #pango, someone suggested a bug in Intel driver. Running `xfce4-appearance-settings` and there changing any of: * antialiasing enable/disable, * hinting strength, * subpixel alignment * or dpi immediately cures the bug (see 2016y02m16d_21h31m52s_0100Z_x_bug_disabling_antialias_immediately_cures_problem.png ) Setting back the exact same parameters immediately reactivates the bug (see 2016y02m16d_21h32m11s_0100Z_x_bug_reenabling_antialias_reactivates_problem_shadow_unaffected.png). It is believed that keeping any new settings for a while will have the bug reoccur. It is not like bug 1536751. That one affects rendering quality of *all* glyphs, at all times, depending on dpi. This is not the case here: *some* glyphs (randomly chosen) are drawn corrupted (replaced by garbage or absent), not always. --- ApportVersion: 2.20-0ubuntu3 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: XFCE DistUpgraded: Fresh install DistroCodename: xenial DistroRelease: Ubuntu 16.04 DistroVariant: ubuntu DkmsStatus: virtualbox, 5.0.14, 4.4.0-8-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. 4th Gen Core Processor Integrated Graphics Controller [1043:177d] Subsystem: ASUSTeK Computer Inc. GM107M [GeForce GTX 850M] [1043:177d] InstallationDate: Installed on 2016-02-03 (26 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160203) MachineType: ASUSTeK COMPUTER INC. N551JK Package: xorg 1:7.7+13ubuntu1 PackageArchitecture: amd64 ProcKernelCmdLine:
[Touch-packages] [Bug 1575907] Re: Using nVidia proprietary driver 361.42 yields black screen
Thank you Nuno for reporting the trouble you observed. I'm the one who posted this very bug report where you added your comment. I can understand your frustration. I'm frustrated too. I'm using open- source nouveau driver instead and it has problems, too cf. https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1547077 , and on top of that all these are regressions from older Ubuntu releases. In any case, in any open-source and unpaid context, please refrain from using several question marks or writing some words in all capital letters, as its main effect is to turn people away. Thank you for your attention. -- 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/1575907 Title: Using nVidia proprietary driver 361.42 yields black screen Status in xorg package in Ubuntu: New Bug description: # Context Selecting nvidia driver using software-properties-gtk. Install goes ok. No longer observing bug https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-361/+bug/1553554 Hardware is Asus n551jk laptop. nvidia driver worked on same hardware with Ubuntu 14.04. # Expected Correct display with better performance and 3D support. # Observed. No immediate effect, although GUI says driver is used. On next boot, no graphical login was observed. Screen was just black. Normal boot again yields same result. Waiting half an hour did not yield any more result. I logged in on a text console and ran "ubuntu-bug" to generate a bug report that I kept until I had a working X again. Booting in rescue mode I finally managed to get to a X session (which is not the usual nouveau setup, for example xbacklight does not work, full brightness hurts my eyes, output is no longer named "eDP1" but "default"). # Additional information Will try to switch to proprietary driver 340.96 as suggested by software-properties-gtk. I guess all other needed information is included in bug report (generated by ubuntu-bug). ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 361.42 Tue Mar 22 18:10:58 PDT 2016 GCC version: gcc version 5.3.1 20160413 (Ubuntu 5.3.1-14ubuntu2) ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' Date: Wed Apr 27 21:31:20 2016 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu DkmsStatus: bbswitch, 0.8, 4.4.0-21-generic, x86_64: installed nvidia-361, 361.42, 4.4.0-21-generic, x86_64: installed virtualbox, 5.0.18, 4.4.0-18-generic, x86_64: installed virtualbox, 5.0.18, 4.4.0-21-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. 4th Gen Core Processor Integrated Graphics Controller [1043:177d] Subsystem: ASUSTeK Computer Inc. GM107M [GeForce GTX 850M] [1043:177d] InstallationDate: Installed on 2016-02-03 (84 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160203) MachineType: ASUSTeK COMPUTER INC. N551JK ProcEnviron: TERM=linux PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic.efi.signed root=UUID=1a4f1bb3-67a8-4e9e-ba71-e9a2741c04a8 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/06/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: N551JK.203 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: N551JK dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrN551JK.203:bd10/06/2014:svnASUSTeKCOMPUTERINC.:pnN551JK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnN551JK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: N551JK dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1 version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
[Touch-packages] [Bug 1547077] Re: Some glyphs drawn consistently wrong, bug comes and go
The bug is still triggered (not always) by suspend-to-ram then wake-up. This make a frustrating user experience since the most affordable workaround is to close the session the reopen it when bug occurs. Since many applications are defaced (see screenshots), the user cannot properly check if their work is saved. Thank you for your attention. -- 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/1547077 Title: Some glyphs drawn consistently wrong, bug comes and go Status in xorg package in Ubuntu: Triaged Bug description: # Summary * Some glyphs badly drawn at some moments. * When happens, same glyph drawn on various windows shows same corruption. * Problem comes and go. Cannot use nvidia proprietary driver as a workaround (does not work at all). # Context Laptop, using "intel" (or "nouveau" ?) driver. Expected: all glyphs rendered correctly. Observed: some glyphs not rendered correctly * reproducible: sometimes, eventually. Problem comes and go, severity varies from one glyph (see 2016y02m17d_18h08m27s_0100Z_x_bug_glyph_firefox_gnome_org.png ) to all text on screen fully unreadable (see 2016y02m10d_18h42m18s_0100Z_wow_screen_flickers_and_most_glyphs_wrong_01.png ) * *some* glyphs are affected. For example, letter 'a' of a certain size will be replaced by colored garbage at many places where it appears (see 2016y02m18d_16h05m35s_0100Z_same_corruption_on_different_windows.png ), but other 'a' with different size, italic, bold, etc will be unaffected. * in some applications (e.g. xfce whisker menu), some glyphs are rendered correctly or not depending on the direction of mouse hovering. See video 2016y02m16d_21h41m14s_0100Z_whisker_menu_missing_glyphs.mp4 . * in menu of gtk application, some glyphs are "fixed" by opening the menu, but not all. For example, in xfce4-terminal, letter A of "Affichage" and its menu content as well as "Aide" is affected. Opening "Affichage" menu does not fix anything. Opening "Aide" menu fixes the "A" of "Aide". Changing window size reactivates the bug on "A" or "Aide". See video 2016y02m18d_16h14m25s_0100Z_glyph-redrawn- bug.mp4 . * text under icons on desktop is affected, but shadows are not. See 2016y02m16d_21h32m11s_0100Z_x_bug_reenabling_antialias_reactivates_problem_shadow_unaffected.png # Affected applications * xfce whisker menu, * xfce4-terminal (nealy all screenshots) * firefox (see 2016y02m17d_18h08m27s_0100Z_x_bug_glyph_firefox_gnome_org.png 2016y02m16d_21h32m11s_0100Z_x_bug_reenabling_antialias_reactivates_problem_shadow_unaffected.png ), * thunderbird (see 2016y02m16d_21h28m35s_0100Z_x_bug_affects_thunderbird_terminal.png ), * emacs (see 2016y02m10d_18h41m49s_0100Z_wow_screen_flickers_and_most_glyphs_wrong_00.png and subsequent ), * superswitcher ( a gtk/gdk app) * *NOT* affected: xterm, xmessage. Perhaps only gtk/gdk/pango/cairo apps are affected. # Additional information This looks like a cache corruption somewhere. On IRC #pango, someone suggested a bug in Intel driver. Running `xfce4-appearance-settings` and there changing any of: * antialiasing enable/disable, * hinting strength, * subpixel alignment * or dpi immediately cures the bug (see 2016y02m16d_21h31m52s_0100Z_x_bug_disabling_antialias_immediately_cures_problem.png ) Setting back the exact same parameters immediately reactivates the bug (see 2016y02m16d_21h32m11s_0100Z_x_bug_reenabling_antialias_reactivates_problem_shadow_unaffected.png). It is believed that keeping any new settings for a while will have the bug reoccur. It is not like bug 1536751. That one affects rendering quality of *all* glyphs, at all times, depending on dpi. This is not the case here: *some* glyphs (randomly chosen) are drawn corrupted (replaced by garbage or absent), not always. --- ApportVersion: 2.20-0ubuntu3 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: XFCE DistUpgraded: Fresh install DistroCodename: xenial DistroRelease: Ubuntu 16.04 DistroVariant: ubuntu DkmsStatus: virtualbox, 5.0.14, 4.4.0-8-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. 4th Gen Core Processor Integrated Graphics Controller [1043:177d] Subsystem: ASUSTeK Computer Inc. GM107M [GeForce GTX 850M] [1043:177d] InstallationDate: Installed on 2016-02-03 (26 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160203) MachineType: ASUSTeK COMPUTER INC. N551JK Package: xorg 1:7.7+13ubuntu1
[Touch-packages] [Bug 1575907] [NEW] Using nVidia proprietary driver 361.42 yields black screen
Public bug reported: # Context Selecting nvidia driver using software-properties-gtk. Install goes ok. No longer observing bug https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-361/+bug/1553554 Hardware is Asus n551jk laptop. nvidia driver worked on same hardware with Ubuntu 14.04. # Expected Correct display with better performance and 3D support. # Observed. No immediate effect, although GUI says driver is used. On next boot, no graphical login was observed. Screen was just black. Normal boot again yields same result. Waiting half an hour did not yield any more result. I logged in on a text console and ran "ubuntu-bug" to generate a bug report that I kept until I had a working X again. Booting in rescue mode I finally managed to get to a X session (which is not the usual nouveau setup, for example xbacklight does not work, full brightness hurts my eyes, output is no longer named "eDP1" but "default"). # Additional information Will try to switch to proprietary driver 340.96 as suggested by software-properties-gtk. I guess all other needed information is included in bug report (generated by ubuntu-bug). ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 361.42 Tue Mar 22 18:10:58 PDT 2016 GCC version: gcc version 5.3.1 20160413 (Ubuntu 5.3.1-14ubuntu2) ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' Date: Wed Apr 27 21:31:20 2016 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu DkmsStatus: bbswitch, 0.8, 4.4.0-21-generic, x86_64: installed nvidia-361, 361.42, 4.4.0-21-generic, x86_64: installed virtualbox, 5.0.18, 4.4.0-18-generic, x86_64: installed virtualbox, 5.0.18, 4.4.0-21-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. 4th Gen Core Processor Integrated Graphics Controller [1043:177d] Subsystem: ASUSTeK Computer Inc. GM107M [GeForce GTX 850M] [1043:177d] InstallationDate: Installed on 2016-02-03 (84 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160203) MachineType: ASUSTeK COMPUTER INC. N551JK ProcEnviron: TERM=linux PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic.efi.signed root=UUID=1a4f1bb3-67a8-4e9e-ba71-e9a2741c04a8 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/06/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: N551JK.203 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: N551JK dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrN551JK.203:bd10/06/2014:svnASUSTeKCOMPUTERINC.:pnN551JK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnN551JK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: N551JK dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1 version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Wed Apr 27 20:31:46 2016 xserver.configfile: /etc/X11/xorg.conf xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.3-1ubuntu2 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug ubuntu xenial -- 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/1575907 Title: Using nVidia proprietary driver 361.42 yields black screen Status in xorg package in Ubuntu: New Bug description:
[Touch-packages] [Bug 1570105] Re: package libjpeg-turbo8-dev (not installed) failed to install/upgrade: tentative de remplacement de « /usr/include/jerror.h », qui appartient aussi au paquet libjpeg9
I tried this: dpkg --purge libjpeg9-dev:amd64 (Reading database ... 255624 files and directories currently installed.) Removing libjpeg9-dev:amd64 (1:9b-1) ... but it did not completely fixed. By making sure both libjpeg-turbo8-dev:amd64 and libjpeg8-dev:amd64 were selected, then it seemed to fix the problem. Terminal logs availab!e. ** Tags added: has-workaround -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libjpeg-turbo in Ubuntu. https://bugs.launchpad.net/bugs/1570105 Title: package libjpeg-turbo8-dev (not installed) failed to install/upgrade: tentative de remplacement de « /usr/include/jerror.h », qui appartient aussi au paquet libjpeg9-dev:amd64 1:9b-1 Status in libjpeg-turbo package in Ubuntu: New Bug description: Was installing opencv-dev with aptitude. Aptitude offered to resolve a conflict between libjpeg packages. I accepted the offered solution. Next time I opened aptitude, it sad opencv-dev packaged were not fully installed. Seems like error is permanent (i.e. will not resolve itself just with upgrade instructions Dépaquetage de libjpeg-turbo8-dev:amd64 (1.4.2-0ubuntu3) ... dpkg: erreur de traitement de l'archive /var/cache/apt/archives/libjpeg-turbo8-dev_1.4.2-0ubuntu3_amd64.deb (--unpack) : tentative de remplacement de « /usr/include/jerror.h », qui appartient aussi au paquet libjpeg9-dev:amd64 1:9b-1 dpkg-deb : erreur : le sous-processus coller a été tué par le signal (Relais brisé (pipe)) Des erreurs ont été rencontrées pendant l'exécution : /var/cache/apt/archives/libjpeg-turbo8-dev_1.4.2-0ubuntu3_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) Impossible d'effectuer l'opération demandée sur le paquet. Essai de récupération : ... ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libjpeg-turbo8-dev (not installed) ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6 Uname: Linux 4.4.0-18-generic x86_64 ApportVersion: 2.20.1-0ubuntu1 Architecture: amd64 Date: Wed Apr 13 23:20:56 2016 ErrorMessage: tentative de remplacement de « /usr/include/jerror.h », qui appartient aussi au paquet libjpeg9-dev:amd64 1:9b-1 InstallationDate: Installed on 2016-02-03 (70 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160203) RelatedPackageVersions: dpkg 1.18.4ubuntu1 apt 1.2.10 SourcePackage: libjpeg-turbo Title: package libjpeg-turbo8-dev (not installed) failed to install/upgrade: tentative de remplacement de « /usr/include/jerror.h », qui appartient aussi au paquet libjpeg9-dev:amd64 1:9b-1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libjpeg-turbo/+bug/1570105/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1570105] Re: package libjpeg-turbo8-dev (not installed) failed to install/upgrade: tentative de remplacement de « /usr/include/jerror.h », qui appartient aussi au paquet libjpeg9
apt-get dist-upgrade Reading package lists... Done Building dependency tree Reading state information... Done You might want to run 'apt-get -f install' to correct these. The following packages have unmet dependencies: libopencv-highgui-dev : Depends: libjpeg-dev libtiff5-dev : Depends: libjpeg-dev E: Unmet dependencies. Try using -f. apt-get dist-upgrade -f Reading package lists... Done Building dependency tree Reading state information... Done Correcting dependencies... Done Calculating upgrade... Done The following NEW packages will be installed: libjpeg-turbo8-dev The following packages will be upgraded: apparmor console-setup console-setup-linux isc-dhcp-client isc-dhcp-common keyboard-configuration libapparmor-perl libapparmor1 libpam-systemd libqt5core5a libqt5dbus5 libqt5gui5 libqt5network5 libqt5widgets5 libsmbclient libsystemd-dev libsystemd0 libudev-dev libudev1 libwbclient0 python-samba samba-common samba-common-bin samba-libs systemd systemd-sysv ubuntu-minimal ubuntu-standard udev 29 upgraded, 1 newly installed, 0 to remove and 0 not upgraded. 12 not fully installed or removed. Need to get 0 B/22.2 MB of archives. After this operation, 1604 kB of additional disk space will be used. Do you want to continue? [Y/n] Reading changelogs... Done Preconfiguring packages ... (Reading database ... 255625 files and directories currently installed.) Preparing to unpack .../libjpeg-turbo8-dev_1.4.2-0ubuntu3_amd64.deb ... Unpacking libjpeg-turbo8-dev:amd64 (1.4.2-0ubuntu3) ... dpkg: error processing archive /var/cache/apt/archives/libjpeg-turbo8-dev_1.4.2-0ubuntu3_amd64.deb (--unpack): trying to overwrite '/usr/include/jerror.h', which is also in package libjpeg9-dev:amd64 1:9b-1 dpkg-deb: error: subprocess paste was killed by signal (Broken pipe) Preparing to unpack .../libsystemd-dev_229-4ubuntu4_amd64.deb ... Unpacking libsystemd-dev:amd64 (229-4ubuntu4) over (229-4ubuntu1) ... Preparing to unpack .../libudev-dev_229-4ubuntu4_amd64.deb ... Unpacking libudev-dev:amd64 (229-4ubuntu4) over (229-4ubuntu1) ... Preparing to unpack .../libsystemd0_229-4ubuntu4_amd64.deb ... Unpacking libsystemd0:amd64 (229-4ubuntu4) over (229-4ubuntu1) ... Processing triggers for man-db (2.7.5-1) ... Processing triggers for libc-bin (2.23-0ubuntu2) ... Errors were encountered while processing: /var/cache/apt/archives/libjpeg-turbo8-dev_1.4.2-0ubuntu3_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) ... ... ... apt-get dist-upgrade -f Reading package lists... Done Building dependency tree Reading state information... Done Correcting dependencies... Done Calculating upgrade... Done The following NEW packages will be installed: libjpeg-turbo8-dev 0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded. 36 not fully installed or removed. Need to get 0 B/254 kB of archives. After this operation, 1418 kB of additional disk space will be used. Do you want to continue? [Y/n] (Reading database ... 255626 files and directories currently installed.) Preparing to unpack .../libjpeg-turbo8-dev_1.4.2-0ubuntu3_amd64.deb ... Unpacking libjpeg-turbo8-dev:amd64 (1.4.2-0ubuntu3) ... dpkg: error processing archive /var/cache/apt/archives/libjpeg-turbo8-dev_1.4.2-0ubuntu3_amd64.deb (--unpack): trying to overwrite '/usr/include/jerror.h', which is also in package libjpeg9-dev:amd64 1:9b-1 dpkg-deb: error: subprocess paste was killed by signal (Broken pipe) Errors were encountered while processing: /var/cache/apt/archives/libjpeg-turbo8-dev_1.4.2-0ubuntu3_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libjpeg-turbo in Ubuntu. https://bugs.launchpad.net/bugs/1570105 Title: package libjpeg-turbo8-dev (not installed) failed to install/upgrade: tentative de remplacement de « /usr/include/jerror.h », qui appartient aussi au paquet libjpeg9-dev:amd64 1:9b-1 Status in libjpeg-turbo package in Ubuntu: New Bug description: Was installing opencv-dev with aptitude. Aptitude offered to resolve a conflict between libjpeg packages. I accepted the offered solution. Next time I opened aptitude, it sad opencv-dev packaged were not fully installed. Seems like error is permanent (i.e. will not resolve itself just with upgrade instructions Dépaquetage de libjpeg-turbo8-dev:amd64 (1.4.2-0ubuntu3) ... dpkg: erreur de traitement de l'archive /var/cache/apt/archives/libjpeg-turbo8-dev_1.4.2-0ubuntu3_amd64.deb (--unpack) : tentative de remplacement de « /usr/include/jerror.h », qui appartient aussi au paquet libjpeg9-dev:amd64 1:9b-1 dpkg-deb : erreur : le sous-processus coller a été tué par le signal (Relais brisé (pipe)) Des erreurs ont été rencontrées pendant l'exécution : /var/cache/apt/archives/libjpeg-turbo8-dev_1.4.2-0ubuntu3_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1)
[Touch-packages] [Bug 1570105] [NEW] package libjpeg-turbo8-dev (not installed) failed to install/upgrade: tentative de remplacement de « /usr/include/jerror.h », qui appartient aussi au paquet libjpe
Public bug reported: Was installing opencv-dev with aptitude. Aptitude offered to resolve a conflict between libjpeg packages. I accepted the offered solution. Next time I opened aptitude, it sad opencv-dev packaged were not fully installed. Seems like error is permanent (i.e. will not resolve itself just with upgrade instructions Dépaquetage de libjpeg-turbo8-dev:amd64 (1.4.2-0ubuntu3) ... dpkg: erreur de traitement de l'archive /var/cache/apt/archives/libjpeg-turbo8-dev_1.4.2-0ubuntu3_amd64.deb (--unpack) : tentative de remplacement de « /usr/include/jerror.h », qui appartient aussi au paquet libjpeg9-dev:amd64 1:9b-1 dpkg-deb : erreur : le sous-processus coller a été tué par le signal (Relais brisé (pipe)) Des erreurs ont été rencontrées pendant l'exécution : /var/cache/apt/archives/libjpeg-turbo8-dev_1.4.2-0ubuntu3_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) Impossible d'effectuer l'opération demandée sur le paquet. Essai de récupération : ... ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libjpeg-turbo8-dev (not installed) ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6 Uname: Linux 4.4.0-18-generic x86_64 ApportVersion: 2.20.1-0ubuntu1 Architecture: amd64 Date: Wed Apr 13 23:20:56 2016 ErrorMessage: tentative de remplacement de « /usr/include/jerror.h », qui appartient aussi au paquet libjpeg9-dev:amd64 1:9b-1 InstallationDate: Installed on 2016-02-03 (70 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160203) RelatedPackageVersions: dpkg 1.18.4ubuntu1 apt 1.2.10 SourcePackage: libjpeg-turbo Title: package libjpeg-turbo8-dev (not installed) failed to install/upgrade: tentative de remplacement de « /usr/include/jerror.h », qui appartient aussi au paquet libjpeg9-dev:amd64 1:9b-1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: libjpeg-turbo (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libjpeg-turbo in Ubuntu. https://bugs.launchpad.net/bugs/1570105 Title: package libjpeg-turbo8-dev (not installed) failed to install/upgrade: tentative de remplacement de « /usr/include/jerror.h », qui appartient aussi au paquet libjpeg9-dev:amd64 1:9b-1 Status in libjpeg-turbo package in Ubuntu: New Bug description: Was installing opencv-dev with aptitude. Aptitude offered to resolve a conflict between libjpeg packages. I accepted the offered solution. Next time I opened aptitude, it sad opencv-dev packaged were not fully installed. Seems like error is permanent (i.e. will not resolve itself just with upgrade instructions Dépaquetage de libjpeg-turbo8-dev:amd64 (1.4.2-0ubuntu3) ... dpkg: erreur de traitement de l'archive /var/cache/apt/archives/libjpeg-turbo8-dev_1.4.2-0ubuntu3_amd64.deb (--unpack) : tentative de remplacement de « /usr/include/jerror.h », qui appartient aussi au paquet libjpeg9-dev:amd64 1:9b-1 dpkg-deb : erreur : le sous-processus coller a été tué par le signal (Relais brisé (pipe)) Des erreurs ont été rencontrées pendant l'exécution : /var/cache/apt/archives/libjpeg-turbo8-dev_1.4.2-0ubuntu3_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) Impossible d'effectuer l'opération demandée sur le paquet. Essai de récupération : ... ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libjpeg-turbo8-dev (not installed) ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6 Uname: Linux 4.4.0-18-generic x86_64 ApportVersion: 2.20.1-0ubuntu1 Architecture: amd64 Date: Wed Apr 13 23:20:56 2016 ErrorMessage: tentative de remplacement de « /usr/include/jerror.h », qui appartient aussi au paquet libjpeg9-dev:amd64 1:9b-1 InstallationDate: Installed on 2016-02-03 (70 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160203) RelatedPackageVersions: dpkg 1.18.4ubuntu1 apt 1.2.10 SourcePackage: libjpeg-turbo Title: package libjpeg-turbo8-dev (not installed) failed to install/upgrade: tentative de remplacement de « /usr/include/jerror.h », qui appartient aussi au paquet libjpeg9-dev:amd64 1:9b-1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libjpeg-turbo/+bug/1570105/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1558236] Re: /usr/bin/script freezes and eats all CPU, has to be killed, which kills shell and programs inside
TL;DR: Bug happened again, workaround works.
Have not tried dd yet, but whenever the bug happen I open a shell, use
bash Ctrl-R to find the one-liner below, press enter and expect that it
works around the bug.
for PROCESSLINE in $( grep -a ^script /proc/*/cmdline -l ) ; do cd
$(dirname $PROCESSLINE) ; pwd ; ls -al fd ; strace head -n 1 fd/4 & echo
voila ; done
It did.
Here's a relevant part of strace output:
open("fd/4", O_RDONLY) = 3
read(3, "\n", 8192) = 1
lseek(3, 0, SEEK_CUR) = -1 ESPIPE (Illegal seek)
fstat(3, {st_mode=S_IFCHR|0620, st_rdev=makedev(136, 9), ...}) = 0
fstat(1, {st_mode=S_IFCHR|0620, st_rdev=makedev(136, 12), ...}) = 0
write(1, "\n", 1
) = 1
close(3)= 0
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to util-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1558236
Title:
/usr/bin/script freezes and eats all CPU, has to be killed, which
kills shell and programs inside
Status in util-linux package in Ubuntu:
New
Bug description:
# Context
I've been using /usr/bin/script quite a lot for about 4 years (since
about Ubuntu 12.04, maybe before). It always worked without problem.
I'm using several script instance most of the time, in several
terminals.
Reproducible: randomly, once every few days.
Problem happens since Ubuntu 16.04. Never seen before (12.04 12.10
13.04 13.10 14.04 14.10 15.04 15.10).
# Expected
Continued operation, terminal running programs normally, little CPU
used.
# Observed
Suddenly, terminal freezes.
Other tabs of same terminal window not affected.
Top shows script consumes 100% CPU.
Strace shows an endless stream of this line:
poll([{fd=4, events=POLLIN}], 1, 10)= 1 ([{fd=4, revents=POLLIN}])
/proc/*/fd shows what file descriptor it is:
total 0
dr-x-- 2 stephane stephane 0 mars 16 20:03 .
dr-xr-xr-x 9 stephane stephane 0 mars 16 20:03 ..
lrwx-- 1 stephane stephane 64 mars 16 20:15 0 -> /dev/pts/17 (deleted)
lrwx-- 1 stephane stephane 64 mars 16 20:15 1 -> /dev/pts/17 (deleted)
lrwx-- 1 stephane stephane 64 mars 16 20:03 2 -> /dev/pts/17 (deleted)
lrwx-- 1 stephane stephane 64 mars 16 20:15 3 -> /dev/ptmx
lrwx-- 1 stephane stephane 64 mars 16 20:15 4 -> /dev/pts/21
lrwx-- 1 stephane stephane 64 mars 16 20:15 5 -> anon_inode:[signalfd]
l-wx-- 1 stephane stephane 64 mars 16 20:15 6 -> /somewhere/mylogfile.txt
l-wx-- 1 stephane stephane 64 mars 16 20:15 7 ->
/somewhere/mylogfile_timings.txt
What can we do?
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: bsdutils 1:2.27.1-6ubuntu1
ProcVersionSignature: Ubuntu 4.4.0-13.29-generic 4.4.5
Uname: Linux 4.4.0-13-generic x86_64
ApportVersion: 2.20-0ubuntu3
Architecture: amd64
CurrentDesktop: XFCE
Date: Wed Mar 16 20:04:02 2016
ExecutablePath: /usr/bin/script
InstallationDate: Installed on 2016-02-03 (41 days ago)
InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160203)
SourcePackage: util-linux
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1558236/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1558236] Re: /usr/bin/script freezes and eats all CPU, has to be killed, which kills shell and programs inside
# Summary
Bug hit again, workaround works again, this time with a strace.
I suspect the workaround has a drawback: the characters it eats are lost for
the script.
Next time I'll try dd to "lose" only one character.
Thank you for your attention.
# Details
The bug has hit again.
Here is a selected portion of
strace head /proc/7514/fd/4
open("/proc/7514/fd/4", O_RDONLY) = 3
read(3, "\n", 8192) = 1
fstat(1, {st_mode=S_IFCHR|0620, st_rdev=makedev(136, 14), ...}) = 0
write(1, "\n", 1
) = 1
read(3, "a", 8192) = 1
read(3, "a", 8192) = 1
read(3, "*", 8192) = 1
read(3, "\177", 8192) = 1
read(3, "e", 8192) = 1
read(3, "e", 8192) = 1
read(3, "\r", 8192) = 1
read(3, ^Cstrace: Process 14679 detached
The characters return by read() are what I typed on the terminal hosting
the stuck /usr/bin/script.
I think that script unlocked itself (i.e. the bug went away) as soon as
the first read() returned, but I'm not sure.
Thank you for your attention.
strace head /proc/7514/fd/4
execve("/usr/bin/head", ["head", "/proc/7514/fd/4"], [/* 31 vars */]) = 0
brk(NULL) = 0x18a8000
access("/etc/ld.so.nohwcap", F_OK) = -1 ENOENT (No such file or directory)
mmap(NULL, 8192, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) =
0x7ff26a1f6000
access("/etc/ld.so.preload", R_OK) = -1 ENOENT (No such file or directory)
open("/etc/ld.so.cache", O_RDONLY|O_CLOEXEC) = 3
fstat(3, {st_mode=S_IFREG|0644, st_size=123250, ...}) = 0
mmap(NULL, 123250, PROT_READ, MAP_PRIVATE, 3, 0) = 0x7ff26a1d7000
close(3)= 0
access("/etc/ld.so.nohwcap", F_OK) = -1 ENOENT (No such file or directory)
open("/lib/x86_64-linux-gnu/libc.so.6", O_RDONLY|O_CLOEXEC) = 3
read(3, "\177ELF\2\1\1\3\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0`\t\2\0\0\0\0\0"...,
832) = 832
fstat(3, {st_mode=S_IFREG|0755, st_size=1868984, ...}) = 0
mmap(NULL, 3971584, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) =
0x7ff269c09000
mprotect(0x7ff269dc9000, 2097152, PROT_NONE) = 0
mmap(0x7ff269fc9000, 24576, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x1c) = 0x7ff269fc9000
mmap(0x7ff269fcf000, 14848, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0x7ff269fcf000
close(3)= 0
mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) =
0x7ff26a1d6000
mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) =
0x7ff26a1d5000
mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) =
0x7ff26a1d4000
arch_prctl(ARCH_SET_FS, 0x7ff26a1d5700) = 0
mprotect(0x7ff269fc9000, 16384, PROT_READ) = 0
mprotect(0x608000, 4096, PROT_READ) = 0
mprotect(0x7ff26a1f8000, 4096, PROT_READ) = 0
munmap(0x7ff26a1d7000, 123250) = 0
brk(NULL) = 0x18a8000
brk(0x18c9000) = 0x18c9000
open("/usr/lib/locale/locale-archive", O_RDONLY|O_CLOEXEC) = 3
fstat(3, {st_mode=S_IFREG|0644, st_size=3001856, ...}) = 0
mmap(NULL, 3001856, PROT_READ, MAP_PRIVATE, 3, 0) = 0x7ff26992c000
close(3)= 0
open("/proc/7514/fd/4", O_RDONLY) = 3
read(3, "\n", 8192) = 1
fstat(1, {st_mode=S_IFCHR|0620, st_rdev=makedev(136, 14), ...}) = 0
write(1, "\n", 1
) = 1
read(3, "a", 8192) = 1
read(3, "a", 8192) = 1
read(3, "*", 8192) = 1
read(3, "\177", 8192) = 1
read(3, "e", 8192) = 1
read(3, "e", 8192) = 1
read(3, "\r", 8192) = 1
read(3, ^Cstrace: Process 14679 detached
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to util-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1558236
Title:
/usr/bin/script freezes and eats all CPU, has to be killed, which
kills shell and programs inside
Status in util-linux package in Ubuntu:
New
Bug description:
# Context
I've been using /usr/bin/script quite a lot for about 4 years (since
about Ubuntu 12.04, maybe before). It always worked without problem.
I'm using several script instance most of the time, in several
terminals.
Reproducible: randomly, once every few days.
Problem happens since Ubuntu 16.04. Never seen before (12.04 12.10
13.04 13.10 14.04 14.10 15.04 15.10).
# Expected
Continued operation, terminal running programs normally, little CPU
used.
# Observed
Suddenly, terminal freezes.
Other tabs of same terminal window not affected.
Top shows script consumes 100% CPU.
Strace shows an endless stream of this line:
poll([{fd=4, events=POLLIN}], 1, 10)= 1 ([{fd=4, revents=POLLIN}])
/proc/*/fd shows what file
[Touch-packages] [Bug 1558236] Re: /usr/bin/script freezes and eats all CPU, has to be killed, which kills shell and programs inside
# Summary
Bug hit again, workaround works again, this time with a strace.
I suspect the workaround has a drawback: the characters it eats are lost for
the script.
Next time I'll try dd to "lose" only one character.
Thank you for your attention.
# Details
The bug has hit again.
Here is a selected portion of
strace head /proc/7514/fd/4
open("/proc/7514/fd/4", O_RDONLY) = 3
read(3, "\n", 8192) = 1
fstat(1, {st_mode=S_IFCHR|0620, st_rdev=makedev(136, 14), ...}) = 0
write(1, "\n", 1
) = 1
read(3, "a", 8192) = 1
read(3, "a", 8192) = 1
read(3, "*", 8192) = 1
read(3, "\177", 8192) = 1
read(3, "e", 8192) = 1
read(3, "e", 8192) = 1
read(3, "\r", 8192) = 1
read(3, ^Cstrace: Process 14679 detached
The characters return by read() are what I typed on the terminal hosting
the stuck /usr/bin/script.
I think that script unlocked itself (i.e. the bug went away) as soon as
the first read() returned, but I'm not sure.
Thank you for your attention.
strace head /proc/7514/fd/4
execve("/usr/bin/head", ["head", "/proc/7514/fd/4"], [/* 31 vars */]) = 0
brk(NULL) = 0x18a8000
access("/etc/ld.so.nohwcap", F_OK) = -1 ENOENT (No such file or directory)
mmap(NULL, 8192, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) =
0x7ff26a1f6000
access("/etc/ld.so.preload", R_OK) = -1 ENOENT (No such file or directory)
open("/etc/ld.so.cache", O_RDONLY|O_CLOEXEC) = 3
fstat(3, {st_mode=S_IFREG|0644, st_size=123250, ...}) = 0
mmap(NULL, 123250, PROT_READ, MAP_PRIVATE, 3, 0) = 0x7ff26a1d7000
close(3)= 0
access("/etc/ld.so.nohwcap", F_OK) = -1 ENOENT (No such file or directory)
open("/lib/x86_64-linux-gnu/libc.so.6", O_RDONLY|O_CLOEXEC) = 3
read(3, "\177ELF\2\1\1\3\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0`\t\2\0\0\0\0\0"...,
832) = 832
fstat(3, {st_mode=S_IFREG|0755, st_size=1868984, ...}) = 0
mmap(NULL, 3971584, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) =
0x7ff269c09000
mprotect(0x7ff269dc9000, 2097152, PROT_NONE) = 0
mmap(0x7ff269fc9000, 24576, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x1c) = 0x7ff269fc9000
mmap(0x7ff269fcf000, 14848, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0x7ff269fcf000
close(3)= 0
mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) =
0x7ff26a1d6000
mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) =
0x7ff26a1d5000
mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) =
0x7ff26a1d4000
arch_prctl(ARCH_SET_FS, 0x7ff26a1d5700) = 0
mprotect(0x7ff269fc9000, 16384, PROT_READ) = 0
mprotect(0x608000, 4096, PROT_READ) = 0
mprotect(0x7ff26a1f8000, 4096, PROT_READ) = 0
munmap(0x7ff26a1d7000, 123250) = 0
brk(NULL) = 0x18a8000
brk(0x18c9000) = 0x18c9000
open("/usr/lib/locale/locale-archive", O_RDONLY|O_CLOEXEC) = 3
fstat(3, {st_mode=S_IFREG|0644, st_size=3001856, ...}) = 0
mmap(NULL, 3001856, PROT_READ, MAP_PRIVATE, 3, 0) = 0x7ff26992c000
close(3)= 0
open("/proc/7514/fd/4", O_RDONLY) = 3
read(3, "\n", 8192) = 1
fstat(1, {st_mode=S_IFCHR|0620, st_rdev=makedev(136, 14), ...}) = 0
write(1, "\n", 1
) = 1
read(3, "a", 8192) = 1
read(3, "a", 8192) = 1
read(3, "*", 8192) = 1
read(3, "\177", 8192) = 1
read(3, "e", 8192) = 1
read(3, "e", 8192) = 1
read(3, "\r", 8192) = 1
read(3, ^Cstrace: Process 14679 detached
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to util-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1558236
Title:
/usr/bin/script freezes and eats all CPU, has to be killed, which
kills shell and programs inside
Status in util-linux package in Ubuntu:
New
Bug description:
# Context
I've been using /usr/bin/script quite a lot for about 4 years (since
about Ubuntu 12.04, maybe before). It always worked without problem.
I'm using several script instance most of the time, in several
terminals.
Reproducible: randomly, once every few days.
Problem happens since Ubuntu 16.04. Never seen before (12.04 12.10
13.04 13.10 14.04 14.10 15.04 15.10).
# Expected
Continued operation, terminal running programs normally, little CPU
used.
# Observed
Suddenly, terminal freezes.
Other tabs of same terminal window not affected.
Top shows script consumes 100% CPU.
Strace shows an endless stream of this line:
poll([{fd=4, events=POLLIN}], 1, 10)= 1 ([{fd=4, revents=POLLIN}])
/proc/*/fd shows what file
[Touch-packages] [Bug 1558236] Re: /usr/bin/script freezes and eats all CPU, has to be killed, which kills shell and programs inside
# Confirmed that the workaround works in practice.
I had a hang, figured out which /usr/bin/script process was eating the
CPU, then issued:
head -n 1 /proc/7514/fd/4
and it continued working.
# Try to figure out what happens.
Below is after the problem was fixed (things worked well again, the
terminal running /usr/bin/script has some text flowing at all times).
In another terminal I typed the commands below
{ while sleep 1 ; do date ; done } & # First, get some timestamps to see where
program pauses
strace head -n 1 /proc/7514/fd/4
And observed the output below (shortened):
open("/proc/7514/fd/4", O_RDONLY) = 3
read(3, jeudi 7 avril 2016, 14:30:02 (UTC+0200)
jeudi 7 avril 2016, 14:30:03 (UTC+0200)
jeudi 7 avril 2016, 14:30:04 (UTC+0200)
"head" sat waiting until I typed something in the terminal running
/usr/bin/script.
jeudi 7 avril 2016, 14:30:05 (UTC+0200)
jeudi 7 avril 2016, 14:30:06 (UTC+0200)
"\n", 8192) = 1
lseek(3, 0, SEEK_CUR) = -1 ESPIPE (Illegal seek)
fstat(3, {st_mode=S_IFCHR|0620, st_rdev=makedev(136, 12), ...}) = 0
fstat(1, {st_mode=S_IFCHR|0620, st_rdev=makedev(136, 4), ...}) = 0
write(1, "\n", 1
) = 1
close(3)= 0
close(1)= 0
close(2)= 0
exit_group(0) = ?
I'll compare with what happens next time /usr/bin/script hangs.
Full output
execve("/usr/bin/head", ["head", "-n", "1", "/proc/7514/fd/4"], [/* 72 vars
*/]) = 0
brk(NULL) = 0xde4000
access("/etc/ld.so.nohwcap", F_OK) = -1 ENOENT (No such file or directory)
mmap(NULL, 8192, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) =
0x7f35d956c000
access("/etc/ld.so.preload", R_OK) = -1 ENOENT (No such file or directory)
open("/etc/ld.so.cache", O_RDONLY|O_CLOEXEC) = 3
fstat(3, {st_mode=S_IFREG|0644, st_size=123250, ...}) = 0
mmap(NULL, 123250, PROT_READ, MAP_PRIVATE, 3, 0) = 0x7f35d954d000
close(3)= 0
access("/etc/ld.so.nohwcap", F_OK) = -1 ENOENT (No such file or directory)
open("/lib/x86_64-linux-gnu/libc.so.6", O_RDONLY|O_CLOEXEC) = 3
read(3, "\177ELF\2\1\1\3\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0`\t\2\0\0\0\0\0"...,
832) = 832
fstat(3, {st_mode=S_IFREG|0755, st_size=1868984, ...}) = 0
mmap(NULL, 3971584, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) =
0x7f35d8f7f000
mprotect(0x7f35d913f000, 2097152, PROT_NONE) = 0
mmap(0x7f35d933f000, 24576, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x1c) = 0x7f35d933f000
mmap(0x7f35d9345000, 14848, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0x7f35d9345000
close(3)= 0
mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) =
0x7f35d954c000
mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) =
0x7f35d954b000
mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) =
0x7f35d954a000
arch_prctl(ARCH_SET_FS, 0x7f35d954b700) = 0
mprotect(0x7f35d933f000, 16384, PROT_READ) = 0
mprotect(0x608000, 4096, PROT_READ) = 0
mprotect(0x7f35d956e000, 4096, PROT_READ) = 0
munmap(0x7f35d954d000, 123250) = 0
brk(NULL) = 0xde4000
brk(0xe05000) = 0xe05000
open("/usr/lib/locale/locale-archive", O_RDONLY|O_CLOEXEC) = 3
fstat(3, {st_mode=S_IFREG|0644, st_size=3001856, ...}) = 0
mmap(NULL, 3001856, PROT_READ, MAP_PRIVATE, 3, 0) = 0x7f35d8ca2000
close(3)= 0
open("/usr/share/locale/locale.alias", O_RDONLY|O_CLOEXEC) = 3
fstat(3, {st_mode=S_IFREG|0644, st_size=2995, ...}) = 0
read(3, "# Locale name alias data base.\n#"..., 4096) = 2995
read(3, "", 4096) = 0
close(3)= 0
open("/usr/share/locale/fr_FR/LC_MESSAGES/coreutils.mo", O_RDONLY) = -1 ENOENT
(No such file or directory)
open("/usr/share/locale/fr/LC_MESSAGES/coreutils.mo", O_RDONLY) = -1 ENOENT (No
such file or directory)
open("/usr/share/locale-langpack/fr_FR/LC_MESSAGES/coreutils.mo", O_RDONLY) =
-1 ENOENT (No such file or directory)
open("/usr/share/locale-langpack/fr/LC_MESSAGES/coreutils.mo", O_RDONLY) = 3
fstat(3, {st_mode=S_IFREG|0644, st_size=297935, ...}) = 0
mmap(NULL, 297935, PROT_READ, MAP_PRIVATE, 3, 0) = 0x7f35d9501000
close(3)= 0
open("/usr/lib/x86_64-linux-gnu/gconv/gconv-modules.cache", O_RDONLY) = 3
fstat(3, {st_mode=S_IFREG|0644, st_size=26258, ...}) = 0
mmap(NULL, 26258, PROT_READ, MAP_SHARED, 3, 0) = 0x7f35d9565000
close(3)= 0
open("/proc/7514/fd/4", O_RDONLY) = 3
read(3, jeudi 7 avril 2016, 14:30:02 (UTC+0200)
jeudi 7 avril 2016, 14:30:03 (UTC+0200)
jeudi 7 avril 2016, 14:30:04 (UTC+0200)
jeudi 7 avril 2016, 14:30:05 (UTC+0200)
jeudi 7 avril 2016, 14:30:06 (UTC+0200)
"\n", 8192) = 1
lseek(3, 0,
[Touch-packages] [Bug 1558236] Re: /usr/bin/script freezes and eats all CPU, has to be killed, which kills shell and programs inside
# Workaround? Tried once, works.
TL;DR: reading the slave pts from another process unfreezes and allows
continued operation
cd /proc/24621/fd
ls -al
total 0
dr-x-- 2 stephane stephane 0 avril 5 16:39 .
dr-xr-xr-x 9 stephane stephane 0 avril 5 15:13 ..
lrwx-- 1 stephane stephane 64 avril 5 16:56 0 -> /dev/pts/8
lrwx-- 1 stephane stephane 64 avril 5 16:56 1 -> /dev/pts/8
lrwx-- 1 stephane stephane 64 avril 5 16:39 2 -> /dev/pts/8
lrwx-- 1 stephane stephane 64 avril 5 16:56 3 -> /dev/ptmx
lrwx-- 1 stephane stephane 64 avril 5 16:56 4 -> /dev/pts/20
lrwx-- 1 stephane stephane 64 avril 5 16:56 5 -> anon_inode:[signalfd]
l-wx-- 1 stephane stephane 64 avril 5 16:56 6 -> /home/stephane/typescript
(deleted)
So, pts/8 is the master, pts/20 is the slave.
echo foo >/dev/pts/8
-> This shows "foo" in the terminal window.
head -n 1 /dev/pts/8
^C
This blocks my shell, so I do Ctrl-C to regain.
echo foo >/dev/pts/20
This blocks my shell, so I do Ctrl-C to regain.
^Cbash: echo: erreur d'écriture : Appel système interrompu
This one is interesting:
head -n 1 /dev/pts/20
It does not block, and works around the bug immediately.
I'll try again.
** Tags added: has-workaround regression-release reproducible
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to util-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1558236
Title:
/usr/bin/script freezes and eats all CPU, has to be killed, which
kills shell and programs inside
Status in util-linux package in Ubuntu:
New
Bug description:
# Context
I've been using /usr/bin/script quite a lot for about 4 years (since
about Ubuntu 12.04, maybe before). It always worked without problem.
I'm using several script instance most of the time, in several
terminals.
Reproducible: randomly, once every few days.
Problem happens since Ubuntu 16.04. Never seen before (12.04 12.10
13.04 13.10 14.04 14.10 15.04 15.10).
# Expected
Continued operation, terminal running programs normally, little CPU
used.
# Observed
Suddenly, terminal freezes.
Other tabs of same terminal window not affected.
Top shows script consumes 100% CPU.
Strace shows an endless stream of this line:
poll([{fd=4, events=POLLIN}], 1, 10)= 1 ([{fd=4, revents=POLLIN}])
/proc/*/fd shows what file descriptor it is:
total 0
dr-x-- 2 stephane stephane 0 mars 16 20:03 .
dr-xr-xr-x 9 stephane stephane 0 mars 16 20:03 ..
lrwx-- 1 stephane stephane 64 mars 16 20:15 0 -> /dev/pts/17 (deleted)
lrwx-- 1 stephane stephane 64 mars 16 20:15 1 -> /dev/pts/17 (deleted)
lrwx-- 1 stephane stephane 64 mars 16 20:03 2 -> /dev/pts/17 (deleted)
lrwx-- 1 stephane stephane 64 mars 16 20:15 3 -> /dev/ptmx
lrwx-- 1 stephane stephane 64 mars 16 20:15 4 -> /dev/pts/21
lrwx-- 1 stephane stephane 64 mars 16 20:15 5 -> anon_inode:[signalfd]
l-wx-- 1 stephane stephane 64 mars 16 20:15 6 -> /somewhere/mylogfile.txt
l-wx-- 1 stephane stephane 64 mars 16 20:15 7 ->
/somewhere/mylogfile_timings.txt
What can we do?
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: bsdutils 1:2.27.1-6ubuntu1
ProcVersionSignature: Ubuntu 4.4.0-13.29-generic 4.4.5
Uname: Linux 4.4.0-13-generic x86_64
ApportVersion: 2.20-0ubuntu3
Architecture: amd64
CurrentDesktop: XFCE
Date: Wed Mar 16 20:04:02 2016
ExecutablePath: /usr/bin/script
InstallationDate: Installed on 2016-02-03 (41 days ago)
InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160203)
SourcePackage: util-linux
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1558236/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1558236] Re: /usr/bin/script freezes and eats all CPU, has to be killed, which kills shell and programs inside
# Reproducible? Tried once, takes about an hour.
This was enough to reproduce the bug once within about one hour :
open a terminal, type:
script
then on the shell prompt type:
yes
The 'yes' command produces as intended an infinite stream of lines with
the character 'y'.
After about one hour, the bug happened.
Only tried once so far.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to util-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1558236
Title:
/usr/bin/script freezes and eats all CPU, has to be killed, which
kills shell and programs inside
Status in util-linux package in Ubuntu:
New
Bug description:
# Context
I've been using /usr/bin/script quite a lot for about 4 years (since
about Ubuntu 12.04, maybe before). It always worked without problem.
I'm using several script instance most of the time, in several
terminals.
Reproducible: randomly, once every few days.
Problem happens since Ubuntu 16.04. Never seen before (12.04 12.10
13.04 13.10 14.04 14.10 15.04 15.10).
# Expected
Continued operation, terminal running programs normally, little CPU
used.
# Observed
Suddenly, terminal freezes.
Other tabs of same terminal window not affected.
Top shows script consumes 100% CPU.
Strace shows an endless stream of this line:
poll([{fd=4, events=POLLIN}], 1, 10)= 1 ([{fd=4, revents=POLLIN}])
/proc/*/fd shows what file descriptor it is:
total 0
dr-x-- 2 stephane stephane 0 mars 16 20:03 .
dr-xr-xr-x 9 stephane stephane 0 mars 16 20:03 ..
lrwx-- 1 stephane stephane 64 mars 16 20:15 0 -> /dev/pts/17 (deleted)
lrwx-- 1 stephane stephane 64 mars 16 20:15 1 -> /dev/pts/17 (deleted)
lrwx-- 1 stephane stephane 64 mars 16 20:03 2 -> /dev/pts/17 (deleted)
lrwx-- 1 stephane stephane 64 mars 16 20:15 3 -> /dev/ptmx
lrwx-- 1 stephane stephane 64 mars 16 20:15 4 -> /dev/pts/21
lrwx-- 1 stephane stephane 64 mars 16 20:15 5 -> anon_inode:[signalfd]
l-wx-- 1 stephane stephane 64 mars 16 20:15 6 -> /somewhere/mylogfile.txt
l-wx-- 1 stephane stephane 64 mars 16 20:15 7 ->
/somewhere/mylogfile_timings.txt
What can we do?
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: bsdutils 1:2.27.1-6ubuntu1
ProcVersionSignature: Ubuntu 4.4.0-13.29-generic 4.4.5
Uname: Linux 4.4.0-13-generic x86_64
ApportVersion: 2.20-0ubuntu3
Architecture: amd64
CurrentDesktop: XFCE
Date: Wed Mar 16 20:04:02 2016
ExecutablePath: /usr/bin/script
InstallationDate: Installed on 2016-02-03 (41 days ago)
InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160203)
SourcePackage: util-linux
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1558236/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1558236] Re: /usr/bin/script freezes and eats all CPU, has to be killed, which kills shell and programs inside
## Status
Bug still occurs every few days, when I use Ubuntu 16.04, not when using
others.
## Trying to get more precise info
### Location in source code
Following https://wiki.ubuntu.com/DebuggingProgramCrash I could get an
interactive gdb prompt showing that it's blocked in the while loop
below:
term-utils/script.c lines 278-287:
static void wait_for_empty_fd(int fd)
{
struct pollfd fds[] = {
{ .fd = fd, .events = POLLIN }
};
while (poll(fds, 1, 10) == 1) {
DBG(IO, ul_debug(" data to read"));
}
}
### Activity at debugger level
Here's the gdb log of the loop when pressing return key at each prompt
repeats "step" gdb command:
wait_for_empty_fd (fd=) at term-utils/script.c:284
284 while (poll(fds, 1, 10) == 1) {
(gdb)
285 DBG(IO, ul_debug(" data to read"));
(gdb)
284 while (poll(fds, 1, 10) == 1) {
(gdb)
poll (__timeout=10, __nfds=1, __fds=0x7fffd0eff840) at
/usr/include/x86_64-linux-gnu/bits/poll2.h:46
46return __poll_alias (__fds, __nfds, __timeout);
(gdb)
poll () at ../sysdeps/unix/syscall-template.S:84
84 ../sysdeps/unix/syscall-template.S: Aucun fichier ou dossier de ce type.
(gdb)
(gdb) bt
#0 poll (__timeout=10, __nfds=1, __fds=0x7fffd0eff840) at
/usr/include/x86_64-linux-gnu/bits/poll2.h:46
#1 wait_for_empty_fd (fd=) at term-utils/script.c:284
#2 write_to_shell (ctl=ctl@entry=0x7fffd0f019c0, buf=buf@entry=0x7fffd0eff890
"sometext"..., bufsz=bufsz@entry=1) at term-utils/script.c:303
#3 0x00402e6d in handle_io (ctl=ctl@entry=0x7fffd0f019c0, fd=0,
eof=eof@entry=0x7fffd0f01904) at term-utils/script.c:346
#4 0x004023fb in do_io (ctl=0x7fffd0f019c0) at term-utils/script.c:475
#5 main (argc=, argv=) at term-utils/script.c:781
(gdb) print __fds
$1 = (struct pollfd *) 0x7fffd0eff840
(gdb) print *__fds
$2 = {fd = 4, events = 1, revents = 1}
lrwx-- 1 stephane stephane 64 Apr 5 16:38 0 -> /dev/pts/6
lrwx-- 1 stephane stephane 64 Apr 5 16:38 1 -> /dev/pts/6
lrwx-- 1 stephane stephane 64 Apr 5 16:38 2 -> /dev/pts/6
lrwx-- 1 stephane stephane 64 Apr 5 16:38 3 -> /dev/ptmx
lrwx-- 1 stephane stephane 64 Apr 5 16:38 4 -> /dev/pts/21
lrwx-- 1 stephane stephane 64 Apr 5 16:38 5 -> anon_inode:[signalfd]
l-wx-- 1 stephane stephane 64 Apr 5 16:38 6 -> /tmp/myscriptfile.txt
l-wx-- 1 stephane stephane 64 Apr 5 16:38 7 -> /tmp/myscriptfile.timings
## Summary
* "script" polls slave pts at high speed consuming 100% CPU, assuming this
won't last. But sometimes it does last forever.
* Polling code was introduced in commit below:
commit 54c6611d6f7b73609a5331f4d0bcf63c4af6429e
Author: Karel Zak
Date: Wed Jun 17 15:48:50 2015 +0200
script: fix EOF problems
* remove STDIN from poll() if:
* STDIN already closed -- poll returns POLLHUP, for example:
echo "date" | script
* detect EOF as returned by read(), for example:
script -c "echo Hello" < /dev/null
* don't write to master when there is still something to read from
slave (it means shell is not initialized yet or busy)
Signed-off-by: Karel Zak
## Now what ?
What should be changed?
It script to blame or is is the shell? Additional info: exact same
operation (shell, etc) have been performed for years, no problem. Even
on this distro (Ubuntu 16.04) it usually works. It *always* works on
Ubuntu <=15.10, Debian 8.3, Fedora 23.
How to debug further?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to util-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1558236
Title:
/usr/bin/script freezes and eats all CPU, has to be killed, which
kills shell and programs inside
Status in util-linux package in Ubuntu:
New
Bug description:
# Context
I've been using /usr/bin/script quite a lot for about 4 years (since
about Ubuntu 12.04, maybe before). It always worked without problem.
I'm using several script instance most of the time, in several
terminals.
Reproducible: randomly, once every few days.
Problem happens since Ubuntu 16.04. Never seen before (12.04 12.10
13.04 13.10 14.04 14.10 15.04 15.10).
# Expected
Continued operation, terminal running programs normally, little CPU
used.
# Observed
Suddenly, terminal freezes.
Other tabs of same terminal window not affected.
Top shows script consumes 100% CPU.
Strace shows an endless stream of this line:
poll([{fd=4, events=POLLIN}], 1, 10)= 1 ([{fd=4, revents=POLLIN}])
/proc/*/fd shows what file descriptor it is:
total 0
dr-x-- 2 stephane stephane 0 mars 16 20:03 .
dr-xr-xr-x 9 stephane stephane 0 mars 16 20:03 ..
lrwx-- 1 stephane stephane 64 mars 16 20:15 0 -> /dev/pts/17 (deleted)
lrwx-- 1 stephane stephane 64 mars 16 20:15 1 -> /dev/pts/17
[Touch-packages] [Bug 1558236] Re: script freezes and eats all CPU, has to be killed, which kills shell and programs inside
Confirmed that bug only happens on Ubuntu 16.04, not on previous Ubuntu
releases and not on Debian 8.3.
Machine has these OSes and can boot any at will, in case it helps:
Debian stable (8.3), Xubuntu 16.04, Xubuntu 15.04, Linux Mint 17.2
(based on Ubuntu 14.04), Fedora 23 XFCE Edition.
** Summary changed:
- script freezes and eats all CPU, has to be killed, which kills shell and
programs inside
+ /usr/bin/script freezes and eats all CPU, has to be killed, which kills shell
and programs inside
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to util-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1558236
Title:
/usr/bin/script freezes and eats all CPU, has to be killed, which
kills shell and programs inside
Status in util-linux package in Ubuntu:
New
Bug description:
# Context
I've been using /usr/bin/script quite a lot for about 4 years (since
about Ubuntu 12.04, maybe before). It always worked without problem.
I'm using several script instance most of the time, in several
terminals.
Reproducible: randomly, once every few days.
Problem happens since Ubuntu 16.04. Never seen before (12.04 12.10
13.04 13.10 14.04 14.10 15.04 15.10).
# Expected
Continued operation, terminal running programs normally, little CPU
used.
# Observed
Suddenly, terminal freezes.
Other tabs of same terminal window not affected.
Top shows script consumes 100% CPU.
Strace shows an endless stream of this line:
poll([{fd=4, events=POLLIN}], 1, 10)= 1 ([{fd=4, revents=POLLIN}])
/proc/*/fd shows what file descriptor it is:
total 0
dr-x-- 2 stephane stephane 0 mars 16 20:03 .
dr-xr-xr-x 9 stephane stephane 0 mars 16 20:03 ..
lrwx-- 1 stephane stephane 64 mars 16 20:15 0 -> /dev/pts/17 (deleted)
lrwx-- 1 stephane stephane 64 mars 16 20:15 1 -> /dev/pts/17 (deleted)
lrwx-- 1 stephane stephane 64 mars 16 20:03 2 -> /dev/pts/17 (deleted)
lrwx-- 1 stephane stephane 64 mars 16 20:15 3 -> /dev/ptmx
lrwx-- 1 stephane stephane 64 mars 16 20:15 4 -> /dev/pts/21
lrwx-- 1 stephane stephane 64 mars 16 20:15 5 -> anon_inode:[signalfd]
l-wx-- 1 stephane stephane 64 mars 16 20:15 6 -> /somewhere/mylogfile.txt
l-wx-- 1 stephane stephane 64 mars 16 20:15 7 ->
/somewhere/mylogfile_timings.txt
What can we do?
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: bsdutils 1:2.27.1-6ubuntu1
ProcVersionSignature: Ubuntu 4.4.0-13.29-generic 4.4.5
Uname: Linux 4.4.0-13-generic x86_64
ApportVersion: 2.20-0ubuntu3
Architecture: amd64
CurrentDesktop: XFCE
Date: Wed Mar 16 20:04:02 2016
ExecutablePath: /usr/bin/script
InstallationDate: Installed on 2016-02-03 (41 days ago)
InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160203)
SourcePackage: util-linux
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1558236/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1558236] Re: script freezes and eats all CPU, has to be killed, which kills shell and programs inside
kill -TERM does not affect runaway /usr/bin/script
kill -HUP stops it instantly
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to util-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1558236
Title:
script freezes and eats all CPU, has to be killed, which kills shell
and programs inside
Status in util-linux package in Ubuntu:
New
Bug description:
# Context
I've been using /usr/bin/script quite a lot for about 4 years (since
about Ubuntu 12.04, maybe before). It always worked without problem.
I'm using several script instance most of the time, in several
terminals.
Reproducible: randomly, once every few days.
Problem happens since Ubuntu 16.04. Never seen before (12.04 12.10
13.04 13.10 14.04 14.10 15.04 15.10).
# Expected
Continued operation, terminal running programs normally, little CPU
used.
# Observed
Suddenly, terminal freezes.
Other tabs of same terminal window not affected.
Top shows script consumes 100% CPU.
Strace shows an endless stream of this line:
poll([{fd=4, events=POLLIN}], 1, 10)= 1 ([{fd=4, revents=POLLIN}])
/proc/*/fd shows what file descriptor it is:
total 0
dr-x-- 2 stephane stephane 0 mars 16 20:03 .
dr-xr-xr-x 9 stephane stephane 0 mars 16 20:03 ..
lrwx-- 1 stephane stephane 64 mars 16 20:15 0 -> /dev/pts/17 (deleted)
lrwx-- 1 stephane stephane 64 mars 16 20:15 1 -> /dev/pts/17 (deleted)
lrwx-- 1 stephane stephane 64 mars 16 20:03 2 -> /dev/pts/17 (deleted)
lrwx-- 1 stephane stephane 64 mars 16 20:15 3 -> /dev/ptmx
lrwx-- 1 stephane stephane 64 mars 16 20:15 4 -> /dev/pts/21
lrwx-- 1 stephane stephane 64 mars 16 20:15 5 -> anon_inode:[signalfd]
l-wx-- 1 stephane stephane 64 mars 16 20:15 6 -> /somewhere/mylogfile.txt
l-wx-- 1 stephane stephane 64 mars 16 20:15 7 ->
/somewhere/mylogfile_timings.txt
What can we do?
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: bsdutils 1:2.27.1-6ubuntu1
ProcVersionSignature: Ubuntu 4.4.0-13.29-generic 4.4.5
Uname: Linux 4.4.0-13-generic x86_64
ApportVersion: 2.20-0ubuntu3
Architecture: amd64
CurrentDesktop: XFCE
Date: Wed Mar 16 20:04:02 2016
ExecutablePath: /usr/bin/script
InstallationDate: Installed on 2016-02-03 (41 days ago)
InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160203)
SourcePackage: util-linux
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1558236/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1547077] Re: Some glyphs drawn consistently wrong, bug comes and go
Unfortunately, the bug occurred again a few minutes ago. This means that uninstalling light-locker and using xscreensaver instead is not enough to prevent the bug from occurring. AFAIK, doing so avoids light-locker creating possibly short-lived X servers (for the purpose of asking password for unlocking screen while allowing to open a new session). Thus I believe that the bug is not triggered by running several X servers. Still, I've noticed that the bug is not active for the whole machine at a time, but can be active on an X server (for example, while typing password to unlock) and inactive on another (main session) or vice versa. All in all, this and bug https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1558236 make (for our usage pattern at least) two important regressions that 16.04 introduces. Thank you for your attention. -- 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/1547077 Title: Some glyphs drawn consistently wrong, bug comes and go Status in xorg package in Ubuntu: Triaged Bug description: # Summary * Some glyphs badly drawn at some moments. * When happens, same glyph drawn on various windows shows same corruption. * Problem comes and go. Cannot use nvidia proprietary driver as a workaround (does not work at all). # Context Laptop, using "intel" (or "nouveau" ?) driver. Expected: all glyphs rendered correctly. Observed: some glyphs not rendered correctly * reproducible: sometimes, eventually. Problem comes and go, severity varies from one glyph (see 2016y02m17d_18h08m27s_0100Z_x_bug_glyph_firefox_gnome_org.png ) to all text on screen fully unreadable (see 2016y02m10d_18h42m18s_0100Z_wow_screen_flickers_and_most_glyphs_wrong_01.png ) * *some* glyphs are affected. For example, letter 'a' of a certain size will be replaced by colored garbage at many places where it appears (see 2016y02m18d_16h05m35s_0100Z_same_corruption_on_different_windows.png ), but other 'a' with different size, italic, bold, etc will be unaffected. * in some applications (e.g. xfce whisker menu), some glyphs are rendered correctly or not depending on the direction of mouse hovering. See video 2016y02m16d_21h41m14s_0100Z_whisker_menu_missing_glyphs.mp4 . * in menu of gtk application, some glyphs are "fixed" by opening the menu, but not all. For example, in xfce4-terminal, letter A of "Affichage" and its menu content as well as "Aide" is affected. Opening "Affichage" menu does not fix anything. Opening "Aide" menu fixes the "A" of "Aide". Changing window size reactivates the bug on "A" or "Aide". See video 2016y02m18d_16h14m25s_0100Z_glyph-redrawn- bug.mp4 . * text under icons on desktop is affected, but shadows are not. See 2016y02m16d_21h32m11s_0100Z_x_bug_reenabling_antialias_reactivates_problem_shadow_unaffected.png # Affected applications * xfce whisker menu, * xfce4-terminal (nealy all screenshots) * firefox (see 2016y02m17d_18h08m27s_0100Z_x_bug_glyph_firefox_gnome_org.png 2016y02m16d_21h32m11s_0100Z_x_bug_reenabling_antialias_reactivates_problem_shadow_unaffected.png ), * thunderbird (see 2016y02m16d_21h28m35s_0100Z_x_bug_affects_thunderbird_terminal.png ), * emacs (see 2016y02m10d_18h41m49s_0100Z_wow_screen_flickers_and_most_glyphs_wrong_00.png and subsequent ), * superswitcher ( a gtk/gdk app) * *NOT* affected: xterm, xmessage. Perhaps only gtk/gdk/pango/cairo apps are affected. # Additional information This looks like a cache corruption somewhere. On IRC #pango, someone suggested a bug in Intel driver. Running `xfce4-appearance-settings` and there changing any of: * antialiasing enable/disable, * hinting strength, * subpixel alignment * or dpi immediately cures the bug (see 2016y02m16d_21h31m52s_0100Z_x_bug_disabling_antialias_immediately_cures_problem.png ) Setting back the exact same parameters immediately reactivates the bug (see 2016y02m16d_21h32m11s_0100Z_x_bug_reenabling_antialias_reactivates_problem_shadow_unaffected.png). It is believed that keeping any new settings for a while will have the bug reoccur. It is not like bug 1536751. That one affects rendering quality of *all* glyphs, at all times, depending on dpi. This is not the case here: *some* glyphs (randomly chosen) are drawn corrupted (replaced by garbage or absent), not always. --- ApportVersion: 2.20-0ubuntu3 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: XFCE DistUpgraded: Fresh install DistroCodename: xenial DistroRelease: Ubuntu 16.04 DistroVariant: ubuntu DkmsStatus: virtualbox, 5.0.14, 4.4.0-8-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation 4th
[Touch-packages] [Bug 1558236] [NEW] script freezes and eats all CPU, has to be killed, which kills shell and programs inside
Public bug reported:
# Context
I've been using /usr/bin/script quite a lot for about 4 years (since
about Ubuntu 12.04, maybe before). It always worked without problem.
I'm using several script instance most of the time, in several
terminals.
Reproducible: randomly, once every few days.
Problem happens since Ubuntu 16.04. Never seen before (12.04 12.10 13.04
13.10 14.04 14.10 15.04 15.10).
# Expected
Continued operation, terminal running programs normally, little CPU
used.
# Observed
Suddenly, terminal freezes.
Other tabs of same terminal window not affected.
Top shows script consumes 100% CPU.
Strace shows an endless stream of this line:
poll([{fd=4, events=POLLIN}], 1, 10)= 1 ([{fd=4, revents=POLLIN}])
/proc/*/fd shows what file descriptor it is:
total 0
dr-x-- 2 stephane stephane 0 mars 16 20:03 .
dr-xr-xr-x 9 stephane stephane 0 mars 16 20:03 ..
lrwx-- 1 stephane stephane 64 mars 16 20:15 0 -> /dev/pts/17 (deleted)
lrwx-- 1 stephane stephane 64 mars 16 20:15 1 -> /dev/pts/17 (deleted)
lrwx-- 1 stephane stephane 64 mars 16 20:03 2 -> /dev/pts/17 (deleted)
lrwx-- 1 stephane stephane 64 mars 16 20:15 3 -> /dev/ptmx
lrwx-- 1 stephane stephane 64 mars 16 20:15 4 -> /dev/pts/21
lrwx-- 1 stephane stephane 64 mars 16 20:15 5 -> anon_inode:[signalfd]
l-wx-- 1 stephane stephane 64 mars 16 20:15 6 -> /somewhere/mylogfile.txt
l-wx-- 1 stephane stephane 64 mars 16 20:15 7 ->
/somewhere/mylogfile_timings.txt
What can we do?
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: bsdutils 1:2.27.1-6ubuntu1
ProcVersionSignature: Ubuntu 4.4.0-13.29-generic 4.4.5
Uname: Linux 4.4.0-13-generic x86_64
ApportVersion: 2.20-0ubuntu3
Architecture: amd64
CurrentDesktop: XFCE
Date: Wed Mar 16 20:04:02 2016
ExecutablePath: /usr/bin/script
InstallationDate: Installed on 2016-02-03 (41 days ago)
InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160203)
SourcePackage: util-linux
UpgradeStatus: No upgrade log present (probably fresh install)
** Affects: util-linux (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug xenial
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to util-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1558236
Title:
script freezes and eats all CPU, has to be killed, which kills shell
and programs inside
Status in util-linux package in Ubuntu:
New
Bug description:
# Context
I've been using /usr/bin/script quite a lot for about 4 years (since
about Ubuntu 12.04, maybe before). It always worked without problem.
I'm using several script instance most of the time, in several
terminals.
Reproducible: randomly, once every few days.
Problem happens since Ubuntu 16.04. Never seen before (12.04 12.10
13.04 13.10 14.04 14.10 15.04 15.10).
# Expected
Continued operation, terminal running programs normally, little CPU
used.
# Observed
Suddenly, terminal freezes.
Other tabs of same terminal window not affected.
Top shows script consumes 100% CPU.
Strace shows an endless stream of this line:
poll([{fd=4, events=POLLIN}], 1, 10)= 1 ([{fd=4, revents=POLLIN}])
/proc/*/fd shows what file descriptor it is:
total 0
dr-x-- 2 stephane stephane 0 mars 16 20:03 .
dr-xr-xr-x 9 stephane stephane 0 mars 16 20:03 ..
lrwx-- 1 stephane stephane 64 mars 16 20:15 0 -> /dev/pts/17 (deleted)
lrwx-- 1 stephane stephane 64 mars 16 20:15 1 -> /dev/pts/17 (deleted)
lrwx-- 1 stephane stephane 64 mars 16 20:03 2 -> /dev/pts/17 (deleted)
lrwx-- 1 stephane stephane 64 mars 16 20:15 3 -> /dev/ptmx
lrwx-- 1 stephane stephane 64 mars 16 20:15 4 -> /dev/pts/21
lrwx-- 1 stephane stephane 64 mars 16 20:15 5 -> anon_inode:[signalfd]
l-wx-- 1 stephane stephane 64 mars 16 20:15 6 -> /somewhere/mylogfile.txt
l-wx-- 1 stephane stephane 64 mars 16 20:15 7 ->
/somewhere/mylogfile_timings.txt
What can we do?
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: bsdutils 1:2.27.1-6ubuntu1
ProcVersionSignature: Ubuntu 4.4.0-13.29-generic 4.4.5
Uname: Linux 4.4.0-13-generic x86_64
ApportVersion: 2.20-0ubuntu3
Architecture: amd64
CurrentDesktop: XFCE
Date: Wed Mar 16 20:04:02 2016
ExecutablePath: /usr/bin/script
InstallationDate: Installed on 2016-02-03 (41 days ago)
InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160203)
SourcePackage: util-linux
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1558236/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1547077] Re: Some glyphs drawn consistently wrong, bug comes and go
Hello Christopher @penalvch. > Could you please report this problem through the appropriate channel by following the instructions verbatim at http://nouveau.freedesktop.org/wiki/Bugs/ ? I performed part of it. The situation passed the "TroubleShooting" step. I checked on the bugzilla, visited #nouveau to see if the issue was known. Found nothing really close. I'll try to invest more time. In the meantime I used 15.04 and 15.10 (that I kept on separate partitions on same machine) and observed that there I had uninstalled light-locker and replaced it with xscreensaver to work around a freeze- with-black-screen-on-wakeup issue. Those used nouveau 1.0.11. So, I went back to 16.04 (which uses nouveau 1.0.12), uninstalled light- locker and replaced it with xscreensaver. If there is no more activity on this bug report for a long time, then it probably means that it is an effective workaround. -- 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/1547077 Title: Some glyphs drawn consistently wrong, bug comes and go Status in xorg package in Ubuntu: Triaged Bug description: # Summary * Some glyphs badly drawn at some moments. * When happens, same glyph drawn on various windows shows same corruption. * Problem comes and go. Cannot use nvidia proprietary driver as a workaround (does not work at all). # Context Laptop, using "intel" (or "nouveau" ?) driver. Expected: all glyphs rendered correctly. Observed: some glyphs not rendered correctly * reproducible: sometimes, eventually. Problem comes and go, severity varies from one glyph (see 2016y02m17d_18h08m27s_0100Z_x_bug_glyph_firefox_gnome_org.png ) to all text on screen fully unreadable (see 2016y02m10d_18h42m18s_0100Z_wow_screen_flickers_and_most_glyphs_wrong_01.png ) * *some* glyphs are affected. For example, letter 'a' of a certain size will be replaced by colored garbage at many places where it appears (see 2016y02m18d_16h05m35s_0100Z_same_corruption_on_different_windows.png ), but other 'a' with different size, italic, bold, etc will be unaffected. * in some applications (e.g. xfce whisker menu), some glyphs are rendered correctly or not depending on the direction of mouse hovering. See video 2016y02m16d_21h41m14s_0100Z_whisker_menu_missing_glyphs.mp4 . * in menu of gtk application, some glyphs are "fixed" by opening the menu, but not all. For example, in xfce4-terminal, letter A of "Affichage" and its menu content as well as "Aide" is affected. Opening "Affichage" menu does not fix anything. Opening "Aide" menu fixes the "A" of "Aide". Changing window size reactivates the bug on "A" or "Aide". See video 2016y02m18d_16h14m25s_0100Z_glyph-redrawn- bug.mp4 . * text under icons on desktop is affected, but shadows are not. See 2016y02m16d_21h32m11s_0100Z_x_bug_reenabling_antialias_reactivates_problem_shadow_unaffected.png # Affected applications * xfce whisker menu, * xfce4-terminal (nealy all screenshots) * firefox (see 2016y02m17d_18h08m27s_0100Z_x_bug_glyph_firefox_gnome_org.png 2016y02m16d_21h32m11s_0100Z_x_bug_reenabling_antialias_reactivates_problem_shadow_unaffected.png ), * thunderbird (see 2016y02m16d_21h28m35s_0100Z_x_bug_affects_thunderbird_terminal.png ), * emacs (see 2016y02m10d_18h41m49s_0100Z_wow_screen_flickers_and_most_glyphs_wrong_00.png and subsequent ), * superswitcher ( a gtk/gdk app) * *NOT* affected: xterm, xmessage. Perhaps only gtk/gdk/pango/cairo apps are affected. # Additional information This looks like a cache corruption somewhere. On IRC #pango, someone suggested a bug in Intel driver. Running `xfce4-appearance-settings` and there changing any of: * antialiasing enable/disable, * hinting strength, * subpixel alignment * or dpi immediately cures the bug (see 2016y02m16d_21h31m52s_0100Z_x_bug_disabling_antialias_immediately_cures_problem.png ) Setting back the exact same parameters immediately reactivates the bug (see 2016y02m16d_21h32m11s_0100Z_x_bug_reenabling_antialias_reactivates_problem_shadow_unaffected.png). It is believed that keeping any new settings for a while will have the bug reoccur. It is not like bug 1536751. That one affects rendering quality of *all* glyphs, at all times, depending on dpi. This is not the case here: *some* glyphs (randomly chosen) are drawn corrupted (replaced by garbage or absent), not always. --- ApportVersion: 2.20-0ubuntu3 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: XFCE DistUpgraded: Fresh install DistroCodename: xenial DistroRelease: Ubuntu 16.04 DistroVariant: ubuntu DkmsStatus: virtualbox, 5.0.14, 4.4.0-8-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection
[Touch-packages] [Bug 1547077] Re: Some glyphs drawn consistently wrong, bug comes and go
After another failed attempt at installing nVidia driver through software-properties-gtk here is another bug report https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-361/+bug/1556960 So bugs happens every few days. Hypothesis: bug happens when another X server is run. This happens with needing to unlock session, either after plain lock or after resume from syspens. That might be why it did not happen on older Xubuntu where I used xscreensaver instead of light-locker. -- 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/1547077 Title: Some glyphs drawn consistently wrong, bug comes and go Status in xorg package in Ubuntu: Triaged Bug description: # Summary * Some glyphs badly drawn at some moments. * When happens, same glyph drawn on various windows shows same corruption. * Problem comes and go. Cannot use nvidia proprietary driver as a workaround (does not work at all). # Context Laptop, using "intel" (or "nouveau" ?) driver. Expected: all glyphs rendered correctly. Observed: some glyphs not rendered correctly * reproducible: sometimes, eventually. Problem comes and go, severity varies from one glyph (see 2016y02m17d_18h08m27s_0100Z_x_bug_glyph_firefox_gnome_org.png ) to all text on screen fully unreadable (see 2016y02m10d_18h42m18s_0100Z_wow_screen_flickers_and_most_glyphs_wrong_01.png ) * *some* glyphs are affected. For example, letter 'a' of a certain size will be replaced by colored garbage at many places where it appears (see 2016y02m18d_16h05m35s_0100Z_same_corruption_on_different_windows.png ), but other 'a' with different size, italic, bold, etc will be unaffected. * in some applications (e.g. xfce whisker menu), some glyphs are rendered correctly or not depending on the direction of mouse hovering. See video 2016y02m16d_21h41m14s_0100Z_whisker_menu_missing_glyphs.mp4 . * in menu of gtk application, some glyphs are "fixed" by opening the menu, but not all. For example, in xfce4-terminal, letter A of "Affichage" and its menu content as well as "Aide" is affected. Opening "Affichage" menu does not fix anything. Opening "Aide" menu fixes the "A" of "Aide". Changing window size reactivates the bug on "A" or "Aide". See video 2016y02m18d_16h14m25s_0100Z_glyph-redrawn- bug.mp4 . * text under icons on desktop is affected, but shadows are not. See 2016y02m16d_21h32m11s_0100Z_x_bug_reenabling_antialias_reactivates_problem_shadow_unaffected.png # Affected applications * xfce whisker menu, * xfce4-terminal (nealy all screenshots) * firefox (see 2016y02m17d_18h08m27s_0100Z_x_bug_glyph_firefox_gnome_org.png 2016y02m16d_21h32m11s_0100Z_x_bug_reenabling_antialias_reactivates_problem_shadow_unaffected.png ), * thunderbird (see 2016y02m16d_21h28m35s_0100Z_x_bug_affects_thunderbird_terminal.png ), * emacs (see 2016y02m10d_18h41m49s_0100Z_wow_screen_flickers_and_most_glyphs_wrong_00.png and subsequent ), * superswitcher ( a gtk/gdk app) * *NOT* affected: xterm, xmessage. Perhaps only gtk/gdk/pango/cairo apps are affected. # Additional information This looks like a cache corruption somewhere. On IRC #pango, someone suggested a bug in Intel driver. Running `xfce4-appearance-settings` and there changing any of: * antialiasing enable/disable, * hinting strength, * subpixel alignment * or dpi immediately cures the bug (see 2016y02m16d_21h31m52s_0100Z_x_bug_disabling_antialias_immediately_cures_problem.png ) Setting back the exact same parameters immediately reactivates the bug (see 2016y02m16d_21h32m11s_0100Z_x_bug_reenabling_antialias_reactivates_problem_shadow_unaffected.png). It is believed that keeping any new settings for a while will have the bug reoccur. It is not like bug 1536751. That one affects rendering quality of *all* glyphs, at all times, depending on dpi. This is not the case here: *some* glyphs (randomly chosen) are drawn corrupted (replaced by garbage or absent), not always. --- ApportVersion: 2.20-0ubuntu3 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: XFCE DistUpgraded: Fresh install DistroCodename: xenial DistroRelease: Ubuntu 16.04 DistroVariant: ubuntu DkmsStatus: virtualbox, 5.0.14, 4.4.0-8-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. 4th Gen Core Processor Integrated Graphics Controller [1043:177d] Subsystem: ASUSTeK Computer Inc. GM107M [GeForce GTX 850M] [1043:177d] InstallationDate: Installed on 2016-02-03 (26 days ago) InstallationMedia:
[Touch-packages] [Bug 1547077] Re: Some glyphs drawn consistently wrong, bug comes and go
Still occurs with latest build xserver-xorg-video-nouveau 1:1.0.12-1build2 *Bug is severely impacting for daily work.* Strangely enough, video worked rather well with 14.10 and 15.04, we mainly had trouble with NetworkManager there. After using Ubuntu more than 10 years now (first was probably 5.04, on different hardware obviously), we're considering switching to Fedora or Debian. We have actually on same machine a copy of Fedora that works without those video or network problems. Thank you for your attention. For additional information ii xserver-xorg-video-all 1:7.7+13ubuntu3 amd64 X.Org X server -- output driver metapackage ii xserver-xorg-video-amdgpu 1.0.1-1build2 amd64 X.Org X server -- AMDGPU display driver ii xserver-xorg-video-ati 1:7.6.1-1ubuntu2amd64 X.Org X server -- AMD/ATI display driver wrapper ii xserver-xorg-video-fbdev 1:0.4.4-1build5 amd64 X.Org X server -- fbdev display driver ii xserver-xorg-video-intel 2:2.99.917+git20160218-1ubuntu3 amd64 X.Org X server -- Intel i8xx, i9xx display driver ii xserver-xorg-video-nouveau 1:1.0.12-1build2amd64 X.Org X server -- Nouveau display driver ii xserver-xorg-video-qxl 0.1.4-3ubuntu3 amd64 X.Org X server -- QXL display driver ii xserver-xorg-video-radeon 1:7.6.1-1ubuntu2amd64 X.Org X server -- AMD/ATI Radeon display driver ii xserver-xorg-video-vesa1:2.3.4-1build2 amd64 X.Org X server -- VESA display driver ii xserver-xorg-video-vmware 1:13.1.0-2ubuntu3 amd64 X.Org X server -- VMware display driver -- 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/1547077 Title: Some glyphs drawn consistently wrong, bug comes and go Status in xorg package in Ubuntu: Triaged Bug description: # Summary * Some glyphs badly drawn at some moments. * When happens, same glyph drawn on various windows shows same corruption. * Problem comes and go. Cannot use nvidia proprietary driver as a workaround (does not work at all). # Context Laptop, using "intel" (or "nouveau" ?) driver. Expected: all glyphs rendered correctly. Observed: some glyphs not rendered correctly * reproducible: sometimes, eventually. Problem comes and go, severity varies from one glyph (see 2016y02m17d_18h08m27s_0100Z_x_bug_glyph_firefox_gnome_org.png ) to all text on screen fully unreadable (see 2016y02m10d_18h42m18s_0100Z_wow_screen_flickers_and_most_glyphs_wrong_01.png ) * *some* glyphs are affected. For example, letter 'a' of a certain size will be replaced by colored garbage at many places where it appears (see 2016y02m18d_16h05m35s_0100Z_same_corruption_on_different_windows.png ), but other 'a' with different size, italic, bold, etc will be unaffected. * in some applications (e.g. xfce whisker menu), some glyphs are rendered correctly or not depending on the direction of mouse hovering. See video 2016y02m16d_21h41m14s_0100Z_whisker_menu_missing_glyphs.mp4 . * in menu of gtk application, some glyphs are "fixed" by opening the menu, but not all. For example, in xfce4-terminal, letter A of "Affichage" and its menu content as well as "Aide" is affected. Opening "Affichage" menu does not fix anything. Opening "Aide" menu fixes the "A" of "Aide". Changing window size reactivates the bug on "A" or "Aide". See video 2016y02m18d_16h14m25s_0100Z_glyph-redrawn- bug.mp4 . * text under icons on desktop is affected, but shadows are not. See 2016y02m16d_21h32m11s_0100Z_x_bug_reenabling_antialias_reactivates_problem_shadow_unaffected.png # Affected applications * xfce whisker menu, * xfce4-terminal (nealy all screenshots) * firefox (see 2016y02m17d_18h08m27s_0100Z_x_bug_glyph_firefox_gnome_org.png 2016y02m16d_21h32m11s_0100Z_x_bug_reenabling_antialias_reactivates_problem_shadow_unaffected.png ), * thunderbird (see 2016y02m16d_21h28m35s_0100Z_x_bug_affects_thunderbird_terminal.png ), * emacs (see 2016y02m10d_18h41m49s_0100Z_wow_screen_flickers_and_most_glyphs_wrong_00.png and subsequent ), * superswitcher ( a gtk/gdk app) * *NOT* affected: xterm, xmessage. Perhaps only gtk/gdk/pango/cairo apps are affected. # Additional information This looks like a cache corruption somewhere. On IRC #pango, someone suggested a bug in Intel driver. Running `xfce4-appearance-settings` and there changing any of: * antialiasing enable/disable, * hinting strength, * subpixel alignment * or dpi immediately cures the bug (see 2016y02m16d_21h31m52s_0100Z_x_bug_disabling_antialias_immediately_cures_problem.png ) Setting back the exact same parameters immediately reactivates the
[Touch-packages] [Bug 1547077] Re: Some glyphs drawn consistently wrong, bug comes and go
Nouveau driver seems active according to dmesg. [0.721176] nouveau :01:00.0: NVIDIA GM107 (117110a2) [0.747014] nouveau :01:00.0: bios: version 82.07.2a.00.17 [0.856760] nouveau :01:00.0: fb: 4096 MiB DDR3 [0.856814] nouveau :01:00.0: priv: HUB0: 10ecc0 (1b40822c) [2.157776] nouveau :01:00.0: DRM: VRAM: 4096 MiB [2.15] nouveau :01:00.0: DRM: GART: 1048576 MiB [2.157780] nouveau :01:00.0: DRM: Pointer to TMDS table invalid [2.157781] nouveau :01:00.0: DRM: DCB version 4.0 [2.157783] nouveau :01:00.0: DRM: Pointer to flat panel table invalid [2.258859] nouveau :01:00.0: DRM: MM: using COPY for buffer copies [2.258863] [drm] Initialized nouveau 1.3.1 20120801 for :01:00.0 on minor 1 [7.741938] nouveau :01:00.0: DRM: evicting buffers... [7.741940] nouveau :01:00.0: DRM: waiting for kernel channels to go idle... [7.741954] nouveau :01:00.0: DRM: suspending client object trees... [7.743296] nouveau :01:00.0: DRM: suspending kernel object tree... [ 12.178092] nouveau :01:00.0: DRM: resuming kernel object tree... [ 12.261441] nouveau :01:00.0: priv: HUB0: 10ecc0 (1c40822c) [ 12.305638] nouveau :01:00.0: DRM: resuming client object trees... [ 25.821544] nouveau :01:00.0: DRM: evicting buffers... [ 25.821547] nouveau :01:00.0: DRM: waiting for kernel channels to go idle... [ 25.821562] nouveau :01:00.0: DRM: suspending client object trees... [ 25.822919] nouveau :01:00.0: DRM: suspending kernel object tree... -- 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/1547077 Title: Some glyphs drawn consistently wrong, bug comes and go Status in xorg package in Ubuntu: Triaged Bug description: # Summary * Some glyphs badly drawn at some moments. * When happens, same glyph drawn on various windows shows same corruption. * Problem comes and go. Cannot use nvidia proprietary driver as a workaround (does not work at all). # Context Laptop, using "intel" (or "nouveau" ?) driver. Expected: all glyphs rendered correctly. Observed: some glyphs not rendered correctly * reproducible: sometimes, eventually. Problem comes and go, severity varies from one glyph (see 2016y02m17d_18h08m27s_0100Z_x_bug_glyph_firefox_gnome_org.png ) to all text on screen fully unreadable (see 2016y02m10d_18h42m18s_0100Z_wow_screen_flickers_and_most_glyphs_wrong_01.png ) * *some* glyphs are affected. For example, letter 'a' of a certain size will be replaced by colored garbage at many places where it appears (see 2016y02m18d_16h05m35s_0100Z_same_corruption_on_different_windows.png ), but other 'a' with different size, italic, bold, etc will be unaffected. * in some applications (e.g. xfce whisker menu), some glyphs are rendered correctly or not depending on the direction of mouse hovering. See video 2016y02m16d_21h41m14s_0100Z_whisker_menu_missing_glyphs.mp4 . * in menu of gtk application, some glyphs are "fixed" by opening the menu, but not all. For example, in xfce4-terminal, letter A of "Affichage" and its menu content as well as "Aide" is affected. Opening "Affichage" menu does not fix anything. Opening "Aide" menu fixes the "A" of "Aide". Changing window size reactivates the bug on "A" or "Aide". See video 2016y02m18d_16h14m25s_0100Z_glyph-redrawn- bug.mp4 . * text under icons on desktop is affected, but shadows are not. See 2016y02m16d_21h32m11s_0100Z_x_bug_reenabling_antialias_reactivates_problem_shadow_unaffected.png # Affected applications * xfce whisker menu, * xfce4-terminal (nealy all screenshots) * firefox (see 2016y02m17d_18h08m27s_0100Z_x_bug_glyph_firefox_gnome_org.png 2016y02m16d_21h32m11s_0100Z_x_bug_reenabling_antialias_reactivates_problem_shadow_unaffected.png ), * thunderbird (see 2016y02m16d_21h28m35s_0100Z_x_bug_affects_thunderbird_terminal.png ), * emacs (see 2016y02m10d_18h41m49s_0100Z_wow_screen_flickers_and_most_glyphs_wrong_00.png and subsequent ), * superswitcher ( a gtk/gdk app) * *NOT* affected: xterm, xmessage. Perhaps only gtk/gdk/pango/cairo apps are affected. # Additional information This looks like a cache corruption somewhere. On IRC #pango, someone suggested a bug in Intel driver. Running `xfce4-appearance-settings` and there changing any of: * antialiasing enable/disable, * hinting strength, * subpixel alignment * or dpi immediately cures the bug (see 2016y02m16d_21h31m52s_0100Z_x_bug_disabling_antialias_immediately_cures_problem.png ) Setting back the exact same parameters immediately reactivates the bug (see 2016y02m16d_21h32m11s_0100Z_x_bug_reenabling_antialias_reactivates_problem_shadow_unaffected.png). It is believed that keeping any new settings for a while will have
[Touch-packages] [Bug 1547077] Re: Some glyphs drawn consistently wrong, bug comes and go
As requested by @penalvch, checked what the BIOS offers. Answer: the BIOS does not offer to disable any intel or nividia chip. In "Graphics Configuration", the BIOS only offers "DVMT Pre-Allocated" with values 64M 128M 256M 512M, currently set to default 64M. -- 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/1547077 Title: Some glyphs drawn consistently wrong, bug comes and go Status in xorg package in Ubuntu: Incomplete Bug description: # Summary * Some glyphs badly drawn at some moments. * When happens, same glyph drawn on various windows shows same corruption. * Problem comes and go. Cannot use nvidia proprietary driver as a workaround (does not work at all). # Context Laptop, using "intel" (or "nouveau" ?) driver. Expected: all glyphs rendered correctly. Observed: some glyphs not rendered correctly * reproducible: sometimes, eventually. Problem comes and go, severity varies from one glyph (see 2016y02m17d_18h08m27s_0100Z_x_bug_glyph_firefox_gnome_org.png ) to all text on screen fully unreadable (see 2016y02m10d_18h42m18s_0100Z_wow_screen_flickers_and_most_glyphs_wrong_01.png ) * *some* glyphs are affected. For example, letter 'a' of a certain size will be replaced by colored garbage at many places where it appears (see 2016y02m18d_16h05m35s_0100Z_same_corruption_on_different_windows.png ), but other 'a' with different size, italic, bold, etc will be unaffected. * in some applications (e.g. xfce whisker menu), some glyphs are rendered correctly or not depending on the direction of mouse hovering. See video 2016y02m16d_21h41m14s_0100Z_whisker_menu_missing_glyphs.mp4 . * in menu of gtk application, some glyphs are "fixed" by opening the menu, but not all. For example, in xfce4-terminal, letter A of "Affichage" and its menu content as well as "Aide" is affected. Opening "Affichage" menu does not fix anything. Opening "Aide" menu fixes the "A" of "Aide". Changing window size reactivates the bug on "A" or "Aide". See video 2016y02m18d_16h14m25s_0100Z_glyph-redrawn- bug.mp4 . * text under icons on desktop is affected, but shadows are not. See 2016y02m16d_21h32m11s_0100Z_x_bug_reenabling_antialias_reactivates_problem_shadow_unaffected.png # Affected applications * xfce whisker menu, * xfce4-terminal (nealy all screenshots) * firefox (see 2016y02m17d_18h08m27s_0100Z_x_bug_glyph_firefox_gnome_org.png 2016y02m16d_21h32m11s_0100Z_x_bug_reenabling_antialias_reactivates_problem_shadow_unaffected.png ), * thunderbird (see 2016y02m16d_21h28m35s_0100Z_x_bug_affects_thunderbird_terminal.png ), * emacs (see 2016y02m10d_18h41m49s_0100Z_wow_screen_flickers_and_most_glyphs_wrong_00.png and subsequent ), * superswitcher ( a gtk/gdk app) * *NOT* affected: xterm, xmessage. Perhaps only gtk/gdk/pango/cairo apps are affected. # Additional information This looks like a cache corruption somewhere. On IRC #pango, someone suggested a bug in Intel driver. Running `xfce4-appearance-settings` and there changing any of: * antialiasing enable/disable, * hinting strength, * subpixel alignment * or dpi immediately cures the bug (see 2016y02m16d_21h31m52s_0100Z_x_bug_disabling_antialias_immediately_cures_problem.png ) Setting back the exact same parameters immediately reactivates the bug (see 2016y02m16d_21h32m11s_0100Z_x_bug_reenabling_antialias_reactivates_problem_shadow_unaffected.png). It is believed that keeping any new settings for a while will have the bug reoccur. It is not like bug 1536751. That one affects rendering quality of *all* glyphs, at all times, depending on dpi. This is not the case here: *some* glyphs (randomly chosen) are drawn corrupted (replaced by garbage or absent), not always. --- ApportVersion: 2.20-0ubuntu3 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: XFCE DistUpgraded: Fresh install DistroCodename: xenial DistroRelease: Ubuntu 16.04 DistroVariant: ubuntu DkmsStatus: virtualbox, 5.0.14, 4.4.0-8-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. 4th Gen Core Processor Integrated Graphics Controller [1043:177d] Subsystem: ASUSTeK Computer Inc. GM107M [GeForce GTX 850M] [1043:177d] InstallationDate: Installed on 2016-02-03 (26 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160203) MachineType: ASUSTeK COMPUTER INC. N551JK Package: xorg 1:7.7+13ubuntu1 PackageArchitecture: amd64 ProcKernelCmdLine:
[Touch-packages] [Bug 1547077] Re: Some glyphs drawn consistently wrong, bug comes and go
Summary: trying proprietary nVidia driver as a workaround does not work. I tried again to switch to nvidia-driver using GUI tool software- properties-gtk This caused again nvidia driver installation failure. https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-361/+bug/1553554 Last time I had to boot to console as root and purge nvidia-related packages to recover a working X. ** Description changed: # Summary * Some glyphs badly drawn at some moments. * When happens, same glyph drawn on various windows shows same corruption. * Problem comes and go. - WORKAROUND: Use nvidia drivers. + Cannot use nvidia proprietary driver as a workaround (does not work at + all). # Context - Laptop, using Intel driver. + Laptop, using "intel" (or "nouveau" ?) driver. Expected: all glyphs rendered correctly. Observed: some glyphs not rendered correctly * reproducible: sometimes, eventually. Problem comes and go, severity varies from one glyph (see 2016y02m17d_18h08m27s_0100Z_x_bug_glyph_firefox_gnome_org.png ) to all text on screen fully unreadable (see 2016y02m10d_18h42m18s_0100Z_wow_screen_flickers_and_most_glyphs_wrong_01.png ) * *some* glyphs are affected. For example, letter 'a' of a certain size will be replaced by colored garbage at many places where it appears (see 2016y02m18d_16h05m35s_0100Z_same_corruption_on_different_windows.png ), but other 'a' with different size, italic, bold, etc will be unaffected. * in some applications (e.g. xfce whisker menu), some glyphs are rendered correctly or not depending on the direction of mouse hovering. See video 2016y02m16d_21h41m14s_0100Z_whisker_menu_missing_glyphs.mp4 . * in menu of gtk application, some glyphs are "fixed" by opening the menu, but not all. For example, in xfce4-terminal, letter A of "Affichage" and its menu content as well as "Aide" is affected. Opening "Affichage" menu does not fix anything. Opening "Aide" menu fixes the "A" of "Aide". Changing window size reactivates the bug on "A" or "Aide". See video 2016y02m18d_16h14m25s_0100Z_glyph-redrawn-bug.mp4 . * text under icons on desktop is affected, but shadows are not. See 2016y02m16d_21h32m11s_0100Z_x_bug_reenabling_antialias_reactivates_problem_shadow_unaffected.png # Affected applications * xfce whisker menu, * xfce4-terminal (nealy all screenshots) * firefox (see 2016y02m17d_18h08m27s_0100Z_x_bug_glyph_firefox_gnome_org.png 2016y02m16d_21h32m11s_0100Z_x_bug_reenabling_antialias_reactivates_problem_shadow_unaffected.png ), * thunderbird (see 2016y02m16d_21h28m35s_0100Z_x_bug_affects_thunderbird_terminal.png ), * emacs (see 2016y02m10d_18h41m49s_0100Z_wow_screen_flickers_and_most_glyphs_wrong_00.png and subsequent ), * superswitcher ( a gtk/gdk app) * *NOT* affected: xterm, xmessage. Perhaps only gtk/gdk/pango/cairo apps are affected. # Additional information This looks like a cache corruption somewhere. On IRC #pango, someone suggested a bug in Intel driver. Running `xfce4-appearance-settings` and there changing any of: * antialiasing enable/disable, * hinting strength, * subpixel alignment * or dpi immediately cures the bug (see 2016y02m16d_21h31m52s_0100Z_x_bug_disabling_antialias_immediately_cures_problem.png ) Setting back the exact same parameters immediately reactivates the bug (see 2016y02m16d_21h32m11s_0100Z_x_bug_reenabling_antialias_reactivates_problem_shadow_unaffected.png). It is believed that keeping any new settings for a while will have the bug reoccur. It is not like bug 1536751. That one affects rendering quality of *all* glyphs, at all times, depending on dpi. This is not the case here: *some* glyphs (randomly chosen) are drawn corrupted (replaced by garbage or absent), not always. --- ApportVersion: 2.20-0ubuntu3 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: XFCE DistUpgraded: Fresh install DistroCodename: xenial DistroRelease: Ubuntu 16.04 DistroVariant: ubuntu DkmsStatus: virtualbox, 5.0.14, 4.4.0-8-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. 4th Gen Core Processor Integrated Graphics Controller [1043:177d] Subsystem: ASUSTeK Computer Inc. GM107M [GeForce GTX 850M] [1043:177d] InstallationDate: Installed on 2016-02-03 (26 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160203) MachineType: ASUSTeK COMPUTER INC. N551JK Package: xorg 1:7.7+13ubuntu1 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-7-generic.efi.signed root=UUID=1a4f1bb3-67a8-4e9e-ba71-e9a2741c04a8 ro quiet
[Touch-packages] [Bug 1547077] Re: Some glyphs drawn consistently wrong, bug comes and go
Laptop stickers show: nVidia GeForce GTX 850M and lspci shows both nVidia and Intel graphics. I'm not quite sure if nouveau or intel driver is used. egrep '(intel|nouveau)' -i Xorg.0.log -o | sort | uniq -c 62 intel 9 Intel 1 INTEL 12 nouveau 2 NOUVEAU Can anyone tell http://askubuntu.com/questions/671973/how-can-i-switch- between-nouveau-and-intel-video-driver ? -- 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/1547077 Title: Some glyphs drawn consistently wrong, bug comes and go Status in xorg package in Ubuntu: Incomplete Bug description: # Summary * Some glyphs badly drawn at some moments. * When happens, same glyph drawn on various windows shows same corruption. * Problem comes and go. Cannot use nvidia proprietary driver as a workaround (does not work at all). # Context Laptop, using "intel" (or "nouveau" ?) driver. Expected: all glyphs rendered correctly. Observed: some glyphs not rendered correctly * reproducible: sometimes, eventually. Problem comes and go, severity varies from one glyph (see 2016y02m17d_18h08m27s_0100Z_x_bug_glyph_firefox_gnome_org.png ) to all text on screen fully unreadable (see 2016y02m10d_18h42m18s_0100Z_wow_screen_flickers_and_most_glyphs_wrong_01.png ) * *some* glyphs are affected. For example, letter 'a' of a certain size will be replaced by colored garbage at many places where it appears (see 2016y02m18d_16h05m35s_0100Z_same_corruption_on_different_windows.png ), but other 'a' with different size, italic, bold, etc will be unaffected. * in some applications (e.g. xfce whisker menu), some glyphs are rendered correctly or not depending on the direction of mouse hovering. See video 2016y02m16d_21h41m14s_0100Z_whisker_menu_missing_glyphs.mp4 . * in menu of gtk application, some glyphs are "fixed" by opening the menu, but not all. For example, in xfce4-terminal, letter A of "Affichage" and its menu content as well as "Aide" is affected. Opening "Affichage" menu does not fix anything. Opening "Aide" menu fixes the "A" of "Aide". Changing window size reactivates the bug on "A" or "Aide". See video 2016y02m18d_16h14m25s_0100Z_glyph-redrawn- bug.mp4 . * text under icons on desktop is affected, but shadows are not. See 2016y02m16d_21h32m11s_0100Z_x_bug_reenabling_antialias_reactivates_problem_shadow_unaffected.png # Affected applications * xfce whisker menu, * xfce4-terminal (nealy all screenshots) * firefox (see 2016y02m17d_18h08m27s_0100Z_x_bug_glyph_firefox_gnome_org.png 2016y02m16d_21h32m11s_0100Z_x_bug_reenabling_antialias_reactivates_problem_shadow_unaffected.png ), * thunderbird (see 2016y02m16d_21h28m35s_0100Z_x_bug_affects_thunderbird_terminal.png ), * emacs (see 2016y02m10d_18h41m49s_0100Z_wow_screen_flickers_and_most_glyphs_wrong_00.png and subsequent ), * superswitcher ( a gtk/gdk app) * *NOT* affected: xterm, xmessage. Perhaps only gtk/gdk/pango/cairo apps are affected. # Additional information This looks like a cache corruption somewhere. On IRC #pango, someone suggested a bug in Intel driver. Running `xfce4-appearance-settings` and there changing any of: * antialiasing enable/disable, * hinting strength, * subpixel alignment * or dpi immediately cures the bug (see 2016y02m16d_21h31m52s_0100Z_x_bug_disabling_antialias_immediately_cures_problem.png ) Setting back the exact same parameters immediately reactivates the bug (see 2016y02m16d_21h32m11s_0100Z_x_bug_reenabling_antialias_reactivates_problem_shadow_unaffected.png). It is believed that keeping any new settings for a while will have the bug reoccur. It is not like bug 1536751. That one affects rendering quality of *all* glyphs, at all times, depending on dpi. This is not the case here: *some* glyphs (randomly chosen) are drawn corrupted (replaced by garbage or absent), not always. --- ApportVersion: 2.20-0ubuntu3 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: XFCE DistUpgraded: Fresh install DistroCodename: xenial DistroRelease: Ubuntu 16.04 DistroVariant: ubuntu DkmsStatus: virtualbox, 5.0.14, 4.4.0-8-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. 4th Gen Core Processor Integrated Graphics Controller [1043:177d] Subsystem: ASUSTeK Computer Inc. GM107M [GeForce GTX 850M] [1043:177d] InstallationDate: Installed on 2016-02-03 (26 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160203) MachineType: ASUSTeK COMPUTER INC.
[Touch-packages] [Bug 1547077] Re: Some glyphs drawn consistently wrong, bug comes and go
Summary: trying proprietary nVidia driver as a workaround does not work. I tried again to switch to nvidia-driver using GUI tool software- properties-gtk This caused again nvidia driver installation failure. https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-361/+bug/1553554 Last time I had to boot to console as root and purge nvidia-related packages to recover a working X. I'll check what the BIOS offers, as requested by @penalvch. -- 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/1547077 Title: Some glyphs drawn consistently wrong, bug comes and go Status in xorg package in Ubuntu: Incomplete Bug description: # Summary * Some glyphs badly drawn at some moments. * When happens, same glyph drawn on various windows shows same corruption. * Problem comes and go. Cannot use nvidia proprietary driver as a workaround (does not work at all). # Context Laptop, using "intel" (or "nouveau" ?) driver. Expected: all glyphs rendered correctly. Observed: some glyphs not rendered correctly * reproducible: sometimes, eventually. Problem comes and go, severity varies from one glyph (see 2016y02m17d_18h08m27s_0100Z_x_bug_glyph_firefox_gnome_org.png ) to all text on screen fully unreadable (see 2016y02m10d_18h42m18s_0100Z_wow_screen_flickers_and_most_glyphs_wrong_01.png ) * *some* glyphs are affected. For example, letter 'a' of a certain size will be replaced by colored garbage at many places where it appears (see 2016y02m18d_16h05m35s_0100Z_same_corruption_on_different_windows.png ), but other 'a' with different size, italic, bold, etc will be unaffected. * in some applications (e.g. xfce whisker menu), some glyphs are rendered correctly or not depending on the direction of mouse hovering. See video 2016y02m16d_21h41m14s_0100Z_whisker_menu_missing_glyphs.mp4 . * in menu of gtk application, some glyphs are "fixed" by opening the menu, but not all. For example, in xfce4-terminal, letter A of "Affichage" and its menu content as well as "Aide" is affected. Opening "Affichage" menu does not fix anything. Opening "Aide" menu fixes the "A" of "Aide". Changing window size reactivates the bug on "A" or "Aide". See video 2016y02m18d_16h14m25s_0100Z_glyph-redrawn- bug.mp4 . * text under icons on desktop is affected, but shadows are not. See 2016y02m16d_21h32m11s_0100Z_x_bug_reenabling_antialias_reactivates_problem_shadow_unaffected.png # Affected applications * xfce whisker menu, * xfce4-terminal (nealy all screenshots) * firefox (see 2016y02m17d_18h08m27s_0100Z_x_bug_glyph_firefox_gnome_org.png 2016y02m16d_21h32m11s_0100Z_x_bug_reenabling_antialias_reactivates_problem_shadow_unaffected.png ), * thunderbird (see 2016y02m16d_21h28m35s_0100Z_x_bug_affects_thunderbird_terminal.png ), * emacs (see 2016y02m10d_18h41m49s_0100Z_wow_screen_flickers_and_most_glyphs_wrong_00.png and subsequent ), * superswitcher ( a gtk/gdk app) * *NOT* affected: xterm, xmessage. Perhaps only gtk/gdk/pango/cairo apps are affected. # Additional information This looks like a cache corruption somewhere. On IRC #pango, someone suggested a bug in Intel driver. Running `xfce4-appearance-settings` and there changing any of: * antialiasing enable/disable, * hinting strength, * subpixel alignment * or dpi immediately cures the bug (see 2016y02m16d_21h31m52s_0100Z_x_bug_disabling_antialias_immediately_cures_problem.png ) Setting back the exact same parameters immediately reactivates the bug (see 2016y02m16d_21h32m11s_0100Z_x_bug_reenabling_antialias_reactivates_problem_shadow_unaffected.png). It is believed that keeping any new settings for a while will have the bug reoccur. It is not like bug 1536751. That one affects rendering quality of *all* glyphs, at all times, depending on dpi. This is not the case here: *some* glyphs (randomly chosen) are drawn corrupted (replaced by garbage or absent), not always. --- ApportVersion: 2.20-0ubuntu3 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: XFCE DistUpgraded: Fresh install DistroCodename: xenial DistroRelease: Ubuntu 16.04 DistroVariant: ubuntu DkmsStatus: virtualbox, 5.0.14, 4.4.0-8-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. 4th Gen Core Processor Integrated Graphics Controller [1043:177d] Subsystem: ASUSTeK Computer Inc. GM107M [GeForce GTX 850M] [1043:177d] InstallationDate: Installed on 2016-02-03 (26 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" -
[Touch-packages] [Bug 1547077] Re: Some glyphs drawn consistently wrong, bug comes and go
I'll try that BIOS test. In the meantime I thought I'd try again nVidia proprietary driver. Installation of package was requested through Ubuntu driver selection GUI. Resulted in 2 new bugs automatically notified and reported: https://bugs.launchpad.net/ubuntu/+source/bbswitch/+bug/1552108 https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-352/+bug/1552109 Have not rebooted yet. Thank you for your attention. -- 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/1547077 Title: Some glyphs drawn consistently wrong, bug comes and go Status in xorg package in Ubuntu: Incomplete Bug description: # Summary * Some glyphs badly drawn at some moments. * When happens, same glyph drawn on various windows shows same corruption. * Problem comes and go. WORKAROUND: Use nvidia drivers. # Context Laptop, using Intel driver. Expected: all glyphs rendered correctly. Observed: some glyphs not rendered correctly * reproducible: sometimes, eventually. Problem comes and go, severity varies from one glyph (see 2016y02m17d_18h08m27s_0100Z_x_bug_glyph_firefox_gnome_org.png ) to all text on screen fully unreadable (see 2016y02m10d_18h42m18s_0100Z_wow_screen_flickers_and_most_glyphs_wrong_01.png ) * *some* glyphs are affected. For example, letter 'a' of a certain size will be replaced by colored garbage at many places where it appears (see 2016y02m18d_16h05m35s_0100Z_same_corruption_on_different_windows.png ), but other 'a' with different size, italic, bold, etc will be unaffected. * in some applications (e.g. xfce whisker menu), some glyphs are rendered correctly or not depending on the direction of mouse hovering. See video 2016y02m16d_21h41m14s_0100Z_whisker_menu_missing_glyphs.mp4 . * in menu of gtk application, some glyphs are "fixed" by opening the menu, but not all. For example, in xfce4-terminal, letter A of "Affichage" and its menu content as well as "Aide" is affected. Opening "Affichage" menu does not fix anything. Opening "Aide" menu fixes the "A" of "Aide". Changing window size reactivates the bug on "A" or "Aide". See video 2016y02m18d_16h14m25s_0100Z_glyph-redrawn- bug.mp4 . * text under icons on desktop is affected, but shadows are not. See 2016y02m16d_21h32m11s_0100Z_x_bug_reenabling_antialias_reactivates_problem_shadow_unaffected.png # Affected applications * xfce whisker menu, * xfce4-terminal (nealy all screenshots) * firefox (see 2016y02m17d_18h08m27s_0100Z_x_bug_glyph_firefox_gnome_org.png 2016y02m16d_21h32m11s_0100Z_x_bug_reenabling_antialias_reactivates_problem_shadow_unaffected.png ), * thunderbird (see 2016y02m16d_21h28m35s_0100Z_x_bug_affects_thunderbird_terminal.png ), * emacs (see 2016y02m10d_18h41m49s_0100Z_wow_screen_flickers_and_most_glyphs_wrong_00.png and subsequent ), * superswitcher ( a gtk/gdk app) * *NOT* affected: xterm, xmessage. Perhaps only gtk/gdk/pango/cairo apps are affected. # Additional information This looks like a cache corruption somewhere. On IRC #pango, someone suggested a bug in Intel driver. Running `xfce4-appearance-settings` and there changing any of: * antialiasing enable/disable, * hinting strength, * subpixel alignment * or dpi immediately cures the bug (see 2016y02m16d_21h31m52s_0100Z_x_bug_disabling_antialias_immediately_cures_problem.png ) Setting back the exact same parameters immediately reactivates the bug (see 2016y02m16d_21h32m11s_0100Z_x_bug_reenabling_antialias_reactivates_problem_shadow_unaffected.png). It is believed that keeping any new settings for a while will have the bug reoccur. It is not like bug 1536751. That one affects rendering quality of *all* glyphs, at all times, depending on dpi. This is not the case here: *some* glyphs (randomly chosen) are drawn corrupted (replaced by garbage or absent), not always. --- ApportVersion: 2.20-0ubuntu3 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: XFCE DistUpgraded: Fresh install DistroCodename: xenial DistroRelease: Ubuntu 16.04 DistroVariant: ubuntu DkmsStatus: virtualbox, 5.0.14, 4.4.0-8-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. 4th Gen Core Processor Integrated Graphics Controller [1043:177d] Subsystem: ASUSTeK Computer Inc. GM107M [GeForce GTX 850M] [1043:177d] InstallationDate: Installed on 2016-02-03 (26 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160203) MachineType: ASUSTeK COMPUTER INC. N551JK Package: xorg
[Touch-packages] [Bug 1547077] Re: Some glyphs drawn consistently wrong, bug comes and go
@penalvch this goes into complications. Actually, I've been using 16.04 and Intel driver because in 14.10, 15.04 and 15.10, all solutions (open-source nouveau driver, open-source intel driver and proprietary nVidia driver) have had different problems (but not this problem). -- 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/1547077 Title: Some glyphs drawn consistently wrong, bug comes and go Status in xorg package in Ubuntu: Incomplete Bug description: # Summary * Some glyphs badly drawn at some moments. * When happens, same glyph drawn on various windows shows same corruption. * Problem comes and go. # Context Laptop, using Intel driver. Expected: all glyphs rendered correctly. Observed: some glyphs not rendered correctly * reproducible: sometimes, eventually. Problem comes and go, severity varies from one glyph (see 2016y02m17d_18h08m27s_0100Z_x_bug_glyph_firefox_gnome_org.png ) to all text on screen fully unreadable (see 2016y02m10d_18h42m18s_0100Z_wow_screen_flickers_and_most_glyphs_wrong_01.png ) * *some* glyphs are affected. For example, letter 'a' of a certain size will be replaced by colored garbage at many places where it appears (see 2016y02m18d_16h05m35s_0100Z_same_corruption_on_different_windows.png ), but other 'a' with different size, italic, bold, etc will be unaffected. * in some applications (e.g. xfce whisker menu), some glyphs are rendered correctly or not depending on the direction of mouse hovering. See video 2016y02m16d_21h41m14s_0100Z_whisker_menu_missing_glyphs.mp4 . * in menu of gtk application, some glyphs are "fixed" by opening the menu, but not all. For example, in xfce4-terminal, letter A of "Affichage" and its menu content as well as "Aide" is affected. Opening "Affichage" menu does not fix anything. Opening "Aide" menu fixes the "A" of "Aide". Changing window size reactivates the bug on "A" or "Aide". See video 2016y02m18d_16h14m25s_0100Z_glyph-redrawn- bug.mp4 . * text under icons on desktop is affected, but shadows are not. See 2016y02m16d_21h32m11s_0100Z_x_bug_reenabling_antialias_reactivates_problem_shadow_unaffected.png # Affected applications Affected applications include: * xfce whisker menu, * xfce4-terminal (nealy all screenshots) * firefox (see 2016y02m17d_18h08m27s_0100Z_x_bug_glyph_firefox_gnome_org.png 2016y02m16d_21h32m11s_0100Z_x_bug_reenabling_antialias_reactivates_problem_shadow_unaffected.png ), * thunderbird (see 2016y02m16d_21h28m35s_0100Z_x_bug_affects_thunderbird_terminal.png ), * emacs (see 2016y02m10d_18h41m49s_0100Z_wow_screen_flickers_and_most_glyphs_wrong_00.png and subsequent ), * superswitcher ( a gtk/gdk app) * *NOT* affected: xterm, xmessage. Perhaps only gtk/gdk/pango/cairo apps are affected. # Additional information This looks like a cache corruption somewhere. On IRC #pango, someone suggested a bug in Intel driver. Running `xfce4-appearance-settings` and there changing any of: * antialiasing enable/disable, * hinting strength, * subpixel alignment * or dpi immediately cures the bug (see 2016y02m16d_21h31m52s_0100Z_x_bug_disabling_antialias_immediately_cures_problem.png ) Setting back the exact same parameters immediately reactivates the bug (see 2016y02m16d_21h32m11s_0100Z_x_bug_reenabling_antialias_reactivates_problem_shadow_unaffected.png). It is believed that keeping any new settings for a while will have the bug reoccur. It is not like bug 1536751. That one affects rendering quality of *all* glyphs, at all times, depending on dpi. This is not the case here: *some* glyphs (randomly chosen) are drawn corrupted (replaced by garbage or absent), not always. # Other 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu export LC_ALL=C ; lsb_release -rd Description: Ubuntu Xenial Xerus (development branch) Release: 16.04 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center apt-cache policy xorg xorg: Installed: 1:7.7+13ubuntu1 Candidate: 1:7.7+13ubuntu1 Version table: *** 1:7.7+13ubuntu1 500 500 http://fr.archive.ubuntu.com/ubuntu xenial/main amd64 Packages 100 /var/lib/dpkg/status 3) What you expected to happen 4) What happened instead Written above. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-4.19-generic 4.4.1 Uname: Linux 4.4.0-4-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 CurrentDesktop: XFCE Date: Thu Feb 18 16:03:55 2016 InstallationDate: Installed on 2016-02-03 (14 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160203) SourcePackage: xorg
[Touch-packages] [Bug 1547077] Re: Some glyphs drawn consistently wrong, bug comes and go
Hello. Suspending then resuming system seems to have some effect. This morning, after resume from suspend (with session still open), all text glyphs appeared blank on the lightdm screen. I expected the session to be fully unusable, but surprisingly, the session itself has had no problem at all since unlocking it (one hour ago). Contrary to first times the bug appeared, I'm not currently using an external screen (and have rebooted since the last time an external screen was used), so the bug does not need that to appear. I would consider the bug severe since it make the whole desktop look awfully broken. :-) -- 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/1547077 Title: Some glyphs drawn consistently wrong, bug comes and go Status in xorg package in Ubuntu: Incomplete Bug description: # Summary * Some glyphs badly drawn at some moments. * When happens, same glyph drawn on various windows shows same corruption. * Problem comes and go. # Context Laptop, using Intel driver. Expected: all glyphs rendered correctly. Observed: some glyphs not rendered correctly * reproducible: sometimes, eventually. Problem comes and go, severity varies from one glyph (see 2016y02m17d_18h08m27s_0100Z_x_bug_glyph_firefox_gnome_org.png ) to all text on screen fully unreadable (see 2016y02m10d_18h42m18s_0100Z_wow_screen_flickers_and_most_glyphs_wrong_01.png ) * *some* glyphs are affected. For example, letter 'a' of a certain size will be replaced by colored garbage at many places where it appears (see 2016y02m18d_16h05m35s_0100Z_same_corruption_on_different_windows.png ), but other 'a' with different size, italic, bold, etc will be unaffected. * in some applications (e.g. xfce whisker menu), some glyphs are rendered correctly or not depending on the direction of mouse hovering. See video 2016y02m16d_21h41m14s_0100Z_whisker_menu_missing_glyphs.mp4 . * in menu of gtk application, some glyphs are "fixed" by opening the menu, but not all. For example, in xfce4-terminal, letter A of "Affichage" and its menu content as well as "Aide" is affected. Opening "Affichage" menu does not fix anything. Opening "Aide" menu fixes the "A" of "Aide". Changing window size reactivates the bug on "A" or "Aide". See video 2016y02m18d_16h14m25s_0100Z_glyph-redrawn- bug.mp4 . * text under icons on desktop is affected, but shadows are not. See 2016y02m16d_21h32m11s_0100Z_x_bug_reenabling_antialias_reactivates_problem_shadow_unaffected.png # Affected applications Affected applications include: * xfce whisker menu, * xfce4-terminal (nealy all screenshots) * firefox (see 2016y02m17d_18h08m27s_0100Z_x_bug_glyph_firefox_gnome_org.png 2016y02m16d_21h32m11s_0100Z_x_bug_reenabling_antialias_reactivates_problem_shadow_unaffected.png ), * thunderbird (see 2016y02m16d_21h28m35s_0100Z_x_bug_affects_thunderbird_terminal.png ), * emacs (see 2016y02m10d_18h41m49s_0100Z_wow_screen_flickers_and_most_glyphs_wrong_00.png and subsequent ), * superswitcher ( a gtk/gdk app) * *NOT* affected: xterm, xmessage. Perhaps only gtk/gdk/pango/cairo apps are affected. # Additional information This looks like a cache corruption somewhere. On IRC #pango, someone suggested a bug in Intel driver. Running `xfce4-appearance-settings` and there changing any of: * antialiasing enable/disable, * hinting strength, * subpixel alignment * or dpi immediately cures the bug (see 2016y02m16d_21h31m52s_0100Z_x_bug_disabling_antialias_immediately_cures_problem.png ) Setting back the exact same parameters immediately reactivates the bug (see 2016y02m16d_21h32m11s_0100Z_x_bug_reenabling_antialias_reactivates_problem_shadow_unaffected.png). It is believed that keeping any new settings for a while will have the bug reoccur. It is not like bug 1536751. That one affects rendering quality of *all* glyphs, at all times, depending on dpi. This is not the case here: *some* glyphs (randomly chosen) are drawn corrupted (replaced by garbage or absent), not always. # Other 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu export LC_ALL=C ; lsb_release -rd Description: Ubuntu Xenial Xerus (development branch) Release: 16.04 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center apt-cache policy xorg xorg: Installed: 1:7.7+13ubuntu1 Candidate: 1:7.7+13ubuntu1 Version table: *** 1:7.7+13ubuntu1 500 500 http://fr.archive.ubuntu.com/ubuntu xenial/main amd64 Packages 100 /var/lib/dpkg/status 3) What you expected to happen 4) What happened instead Written above. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu1
[Touch-packages] [Bug 1547077] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1547077/+attachment/4585292/+files/ProcCpuinfo.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.launchpad.net/bugs/1547077 Title: Some glyphs drawn consistently wrong, bug comes and go Status in xorg package in Ubuntu: Incomplete Bug description: # Summary * Some glyphs badly drawn at some moments. * When happens, same glyph drawn on various windows shows same corruption. * Problem comes and go. # Context Laptop, using Intel driver. Expected: all glyphs rendered correctly. Observed: some glyphs not rendered correctly * reproducible: sometimes, eventually. Problem comes and go, severity varies from one glyph (see 2016y02m17d_18h08m27s_0100Z_x_bug_glyph_firefox_gnome_org.png ) to all text on screen fully unreadable (see 2016y02m10d_18h42m18s_0100Z_wow_screen_flickers_and_most_glyphs_wrong_01.png ) * *some* glyphs are affected. For example, letter 'a' of a certain size will be replaced by colored garbage at many places where it appears (see 2016y02m18d_16h05m35s_0100Z_same_corruption_on_different_windows.png ), but other 'a' with different size, italic, bold, etc will be unaffected. * in some applications (e.g. xfce whisker menu), some glyphs are rendered correctly or not depending on the direction of mouse hovering. See video 2016y02m16d_21h41m14s_0100Z_whisker_menu_missing_glyphs.mp4 . * in menu of gtk application, some glyphs are "fixed" by opening the menu, but not all. For example, in xfce4-terminal, letter A of "Affichage" and its menu content as well as "Aide" is affected. Opening "Affichage" menu does not fix anything. Opening "Aide" menu fixes the "A" of "Aide". Changing window size reactivates the bug on "A" or "Aide". See video 2016y02m18d_16h14m25s_0100Z_glyph-redrawn- bug.mp4 . * text under icons on desktop is affected, but shadows are not. See 2016y02m16d_21h32m11s_0100Z_x_bug_reenabling_antialias_reactivates_problem_shadow_unaffected.png # Affected applications Affected applications include: * xfce whisker menu, * xfce4-terminal (nealy all screenshots) * firefox (see 2016y02m17d_18h08m27s_0100Z_x_bug_glyph_firefox_gnome_org.png 2016y02m16d_21h32m11s_0100Z_x_bug_reenabling_antialias_reactivates_problem_shadow_unaffected.png ), * thunderbird (see 2016y02m16d_21h28m35s_0100Z_x_bug_affects_thunderbird_terminal.png ), * emacs (see 2016y02m10d_18h41m49s_0100Z_wow_screen_flickers_and_most_glyphs_wrong_00.png and subsequent ), * superswitcher ( a gtk/gdk app) * *NOT* affected: xterm, xmessage. Perhaps only gtk/gdk/pango/cairo apps are affected. # Additional information This looks like a cache corruption somewhere. On IRC #pango, someone suggested a bug in Intel driver. Running `xfce4-appearance-settings` and there changing any of: * antialiasing enable/disable, * hinting strength, * subpixel alignment * or dpi immediately cures the bug (see 2016y02m16d_21h31m52s_0100Z_x_bug_disabling_antialias_immediately_cures_problem.png ) Setting back the exact same parameters immediately reactivates the bug (see 2016y02m16d_21h32m11s_0100Z_x_bug_reenabling_antialias_reactivates_problem_shadow_unaffected.png). It is believed that keeping any new settings for a while will have the bug reoccur. It is not like bug 1536751. That one affects rendering quality of *all* glyphs, at all times, depending on dpi. This is not the case here: *some* glyphs (randomly chosen) are drawn corrupted (replaced by garbage or absent), not always. # Other 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu export LC_ALL=C ; lsb_release -rd Description: Ubuntu Xenial Xerus (development branch) Release: 16.04 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center apt-cache policy xorg xorg: Installed: 1:7.7+13ubuntu1 Candidate: 1:7.7+13ubuntu1 Version table: *** 1:7.7+13ubuntu1 500 500 http://fr.archive.ubuntu.com/ubuntu xenial/main amd64 Packages 100 /var/lib/dpkg/status 3) What you expected to happen 4) What happened instead Written above. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-4.19-generic 4.4.1 Uname: Linux 4.4.0-4-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 CurrentDesktop: XFCE Date: Thu Feb 18 16:03:55 2016 InstallationDate: Installed on 2016-02-03 (14 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160203) SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.20-0ubuntu3
[Touch-packages] [Bug 1547077] XorgLogOld.txt
apport information ** Attachment added: "XorgLogOld.txt" https://bugs.launchpad.net/bugs/1547077/+attachment/4585298/+files/XorgLogOld.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.launchpad.net/bugs/1547077 Title: Some glyphs drawn consistently wrong, bug comes and go Status in xorg package in Ubuntu: Incomplete Bug description: # Summary * Some glyphs badly drawn at some moments. * When happens, same glyph drawn on various windows shows same corruption. * Problem comes and go. # Context Laptop, using Intel driver. Expected: all glyphs rendered correctly. Observed: some glyphs not rendered correctly * reproducible: sometimes, eventually. Problem comes and go, severity varies from one glyph (see 2016y02m17d_18h08m27s_0100Z_x_bug_glyph_firefox_gnome_org.png ) to all text on screen fully unreadable (see 2016y02m10d_18h42m18s_0100Z_wow_screen_flickers_and_most_glyphs_wrong_01.png ) * *some* glyphs are affected. For example, letter 'a' of a certain size will be replaced by colored garbage at many places where it appears (see 2016y02m18d_16h05m35s_0100Z_same_corruption_on_different_windows.png ), but other 'a' with different size, italic, bold, etc will be unaffected. * in some applications (e.g. xfce whisker menu), some glyphs are rendered correctly or not depending on the direction of mouse hovering. See video 2016y02m16d_21h41m14s_0100Z_whisker_menu_missing_glyphs.mp4 . * in menu of gtk application, some glyphs are "fixed" by opening the menu, but not all. For example, in xfce4-terminal, letter A of "Affichage" and its menu content as well as "Aide" is affected. Opening "Affichage" menu does not fix anything. Opening "Aide" menu fixes the "A" of "Aide". Changing window size reactivates the bug on "A" or "Aide". See video 2016y02m18d_16h14m25s_0100Z_glyph-redrawn- bug.mp4 . * text under icons on desktop is affected, but shadows are not. See 2016y02m16d_21h32m11s_0100Z_x_bug_reenabling_antialias_reactivates_problem_shadow_unaffected.png # Affected applications Affected applications include: * xfce whisker menu, * xfce4-terminal (nealy all screenshots) * firefox (see 2016y02m17d_18h08m27s_0100Z_x_bug_glyph_firefox_gnome_org.png 2016y02m16d_21h32m11s_0100Z_x_bug_reenabling_antialias_reactivates_problem_shadow_unaffected.png ), * thunderbird (see 2016y02m16d_21h28m35s_0100Z_x_bug_affects_thunderbird_terminal.png ), * emacs (see 2016y02m10d_18h41m49s_0100Z_wow_screen_flickers_and_most_glyphs_wrong_00.png and subsequent ), * superswitcher ( a gtk/gdk app) * *NOT* affected: xterm, xmessage. Perhaps only gtk/gdk/pango/cairo apps are affected. # Additional information This looks like a cache corruption somewhere. On IRC #pango, someone suggested a bug in Intel driver. Running `xfce4-appearance-settings` and there changing any of: * antialiasing enable/disable, * hinting strength, * subpixel alignment * or dpi immediately cures the bug (see 2016y02m16d_21h31m52s_0100Z_x_bug_disabling_antialias_immediately_cures_problem.png ) Setting back the exact same parameters immediately reactivates the bug (see 2016y02m16d_21h32m11s_0100Z_x_bug_reenabling_antialias_reactivates_problem_shadow_unaffected.png). It is believed that keeping any new settings for a while will have the bug reoccur. It is not like bug 1536751. That one affects rendering quality of *all* glyphs, at all times, depending on dpi. This is not the case here: *some* glyphs (randomly chosen) are drawn corrupted (replaced by garbage or absent), not always. # Other 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu export LC_ALL=C ; lsb_release -rd Description: Ubuntu Xenial Xerus (development branch) Release: 16.04 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center apt-cache policy xorg xorg: Installed: 1:7.7+13ubuntu1 Candidate: 1:7.7+13ubuntu1 Version table: *** 1:7.7+13ubuntu1 500 500 http://fr.archive.ubuntu.com/ubuntu xenial/main amd64 Packages 100 /var/lib/dpkg/status 3) What you expected to happen 4) What happened instead Written above. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-4.19-generic 4.4.1 Uname: Linux 4.4.0-4-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 CurrentDesktop: XFCE Date: Thu Feb 18 16:03:55 2016 InstallationDate: Installed on 2016-02-03 (14 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160203) SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.20-0ubuntu3
[Touch-packages] [Bug 1547077] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1547077/+attachment/4585290/+files/Lsusb.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.launchpad.net/bugs/1547077 Title: Some glyphs drawn consistently wrong, bug comes and go Status in xorg package in Ubuntu: Incomplete Bug description: # Summary * Some glyphs badly drawn at some moments. * When happens, same glyph drawn on various windows shows same corruption. * Problem comes and go. # Context Laptop, using Intel driver. Expected: all glyphs rendered correctly. Observed: some glyphs not rendered correctly * reproducible: sometimes, eventually. Problem comes and go, severity varies from one glyph (see 2016y02m17d_18h08m27s_0100Z_x_bug_glyph_firefox_gnome_org.png ) to all text on screen fully unreadable (see 2016y02m10d_18h42m18s_0100Z_wow_screen_flickers_and_most_glyphs_wrong_01.png ) * *some* glyphs are affected. For example, letter 'a' of a certain size will be replaced by colored garbage at many places where it appears (see 2016y02m18d_16h05m35s_0100Z_same_corruption_on_different_windows.png ), but other 'a' with different size, italic, bold, etc will be unaffected. * in some applications (e.g. xfce whisker menu), some glyphs are rendered correctly or not depending on the direction of mouse hovering. See video 2016y02m16d_21h41m14s_0100Z_whisker_menu_missing_glyphs.mp4 . * in menu of gtk application, some glyphs are "fixed" by opening the menu, but not all. For example, in xfce4-terminal, letter A of "Affichage" and its menu content as well as "Aide" is affected. Opening "Affichage" menu does not fix anything. Opening "Aide" menu fixes the "A" of "Aide". Changing window size reactivates the bug on "A" or "Aide". See video 2016y02m18d_16h14m25s_0100Z_glyph-redrawn- bug.mp4 . * text under icons on desktop is affected, but shadows are not. See 2016y02m16d_21h32m11s_0100Z_x_bug_reenabling_antialias_reactivates_problem_shadow_unaffected.png # Affected applications Affected applications include: * xfce whisker menu, * xfce4-terminal (nealy all screenshots) * firefox (see 2016y02m17d_18h08m27s_0100Z_x_bug_glyph_firefox_gnome_org.png 2016y02m16d_21h32m11s_0100Z_x_bug_reenabling_antialias_reactivates_problem_shadow_unaffected.png ), * thunderbird (see 2016y02m16d_21h28m35s_0100Z_x_bug_affects_thunderbird_terminal.png ), * emacs (see 2016y02m10d_18h41m49s_0100Z_wow_screen_flickers_and_most_glyphs_wrong_00.png and subsequent ), * superswitcher ( a gtk/gdk app) * *NOT* affected: xterm, xmessage. Perhaps only gtk/gdk/pango/cairo apps are affected. # Additional information This looks like a cache corruption somewhere. On IRC #pango, someone suggested a bug in Intel driver. Running `xfce4-appearance-settings` and there changing any of: * antialiasing enable/disable, * hinting strength, * subpixel alignment * or dpi immediately cures the bug (see 2016y02m16d_21h31m52s_0100Z_x_bug_disabling_antialias_immediately_cures_problem.png ) Setting back the exact same parameters immediately reactivates the bug (see 2016y02m16d_21h32m11s_0100Z_x_bug_reenabling_antialias_reactivates_problem_shadow_unaffected.png). It is believed that keeping any new settings for a while will have the bug reoccur. It is not like bug 1536751. That one affects rendering quality of *all* glyphs, at all times, depending on dpi. This is not the case here: *some* glyphs (randomly chosen) are drawn corrupted (replaced by garbage or absent), not always. # Other 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu export LC_ALL=C ; lsb_release -rd Description: Ubuntu Xenial Xerus (development branch) Release: 16.04 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center apt-cache policy xorg xorg: Installed: 1:7.7+13ubuntu1 Candidate: 1:7.7+13ubuntu1 Version table: *** 1:7.7+13ubuntu1 500 500 http://fr.archive.ubuntu.com/ubuntu xenial/main amd64 Packages 100 /var/lib/dpkg/status 3) What you expected to happen 4) What happened instead Written above. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-4.19-generic 4.4.1 Uname: Linux 4.4.0-4-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 CurrentDesktop: XFCE Date: Thu Feb 18 16:03:55 2016 InstallationDate: Installed on 2016-02-03 (14 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160203) SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.20-0ubuntu3 Architecture: amd64
[Touch-packages] [Bug 1547077] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1547077/+attachment/4585293/+files/ProcEnviron.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.launchpad.net/bugs/1547077 Title: Some glyphs drawn consistently wrong, bug comes and go Status in xorg package in Ubuntu: Incomplete Bug description: # Summary * Some glyphs badly drawn at some moments. * When happens, same glyph drawn on various windows shows same corruption. * Problem comes and go. # Context Laptop, using Intel driver. Expected: all glyphs rendered correctly. Observed: some glyphs not rendered correctly * reproducible: sometimes, eventually. Problem comes and go, severity varies from one glyph (see 2016y02m17d_18h08m27s_0100Z_x_bug_glyph_firefox_gnome_org.png ) to all text on screen fully unreadable (see 2016y02m10d_18h42m18s_0100Z_wow_screen_flickers_and_most_glyphs_wrong_01.png ) * *some* glyphs are affected. For example, letter 'a' of a certain size will be replaced by colored garbage at many places where it appears (see 2016y02m18d_16h05m35s_0100Z_same_corruption_on_different_windows.png ), but other 'a' with different size, italic, bold, etc will be unaffected. * in some applications (e.g. xfce whisker menu), some glyphs are rendered correctly or not depending on the direction of mouse hovering. See video 2016y02m16d_21h41m14s_0100Z_whisker_menu_missing_glyphs.mp4 . * in menu of gtk application, some glyphs are "fixed" by opening the menu, but not all. For example, in xfce4-terminal, letter A of "Affichage" and its menu content as well as "Aide" is affected. Opening "Affichage" menu does not fix anything. Opening "Aide" menu fixes the "A" of "Aide". Changing window size reactivates the bug on "A" or "Aide". See video 2016y02m18d_16h14m25s_0100Z_glyph-redrawn- bug.mp4 . * text under icons on desktop is affected, but shadows are not. See 2016y02m16d_21h32m11s_0100Z_x_bug_reenabling_antialias_reactivates_problem_shadow_unaffected.png # Affected applications Affected applications include: * xfce whisker menu, * xfce4-terminal (nealy all screenshots) * firefox (see 2016y02m17d_18h08m27s_0100Z_x_bug_glyph_firefox_gnome_org.png 2016y02m16d_21h32m11s_0100Z_x_bug_reenabling_antialias_reactivates_problem_shadow_unaffected.png ), * thunderbird (see 2016y02m16d_21h28m35s_0100Z_x_bug_affects_thunderbird_terminal.png ), * emacs (see 2016y02m10d_18h41m49s_0100Z_wow_screen_flickers_and_most_glyphs_wrong_00.png and subsequent ), * superswitcher ( a gtk/gdk app) * *NOT* affected: xterm, xmessage. Perhaps only gtk/gdk/pango/cairo apps are affected. # Additional information This looks like a cache corruption somewhere. On IRC #pango, someone suggested a bug in Intel driver. Running `xfce4-appearance-settings` and there changing any of: * antialiasing enable/disable, * hinting strength, * subpixel alignment * or dpi immediately cures the bug (see 2016y02m16d_21h31m52s_0100Z_x_bug_disabling_antialias_immediately_cures_problem.png ) Setting back the exact same parameters immediately reactivates the bug (see 2016y02m16d_21h32m11s_0100Z_x_bug_reenabling_antialias_reactivates_problem_shadow_unaffected.png). It is believed that keeping any new settings for a while will have the bug reoccur. It is not like bug 1536751. That one affects rendering quality of *all* glyphs, at all times, depending on dpi. This is not the case here: *some* glyphs (randomly chosen) are drawn corrupted (replaced by garbage or absent), not always. # Other 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu export LC_ALL=C ; lsb_release -rd Description: Ubuntu Xenial Xerus (development branch) Release: 16.04 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center apt-cache policy xorg xorg: Installed: 1:7.7+13ubuntu1 Candidate: 1:7.7+13ubuntu1 Version table: *** 1:7.7+13ubuntu1 500 500 http://fr.archive.ubuntu.com/ubuntu xenial/main amd64 Packages 100 /var/lib/dpkg/status 3) What you expected to happen 4) What happened instead Written above. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-4.19-generic 4.4.1 Uname: Linux 4.4.0-4-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 CurrentDesktop: XFCE Date: Thu Feb 18 16:03:55 2016 InstallationDate: Installed on 2016-02-03 (14 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160203) SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.20-0ubuntu3
[Touch-packages] [Bug 1547077] xdpyinfo.txt
apport information ** Attachment added: "xdpyinfo.txt" https://bugs.launchpad.net/bugs/1547077/+attachment/4585300/+files/xdpyinfo.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.launchpad.net/bugs/1547077 Title: Some glyphs drawn consistently wrong, bug comes and go Status in xorg package in Ubuntu: Incomplete Bug description: # Summary * Some glyphs badly drawn at some moments. * When happens, same glyph drawn on various windows shows same corruption. * Problem comes and go. # Context Laptop, using Intel driver. Expected: all glyphs rendered correctly. Observed: some glyphs not rendered correctly * reproducible: sometimes, eventually. Problem comes and go, severity varies from one glyph (see 2016y02m17d_18h08m27s_0100Z_x_bug_glyph_firefox_gnome_org.png ) to all text on screen fully unreadable (see 2016y02m10d_18h42m18s_0100Z_wow_screen_flickers_and_most_glyphs_wrong_01.png ) * *some* glyphs are affected. For example, letter 'a' of a certain size will be replaced by colored garbage at many places where it appears (see 2016y02m18d_16h05m35s_0100Z_same_corruption_on_different_windows.png ), but other 'a' with different size, italic, bold, etc will be unaffected. * in some applications (e.g. xfce whisker menu), some glyphs are rendered correctly or not depending on the direction of mouse hovering. See video 2016y02m16d_21h41m14s_0100Z_whisker_menu_missing_glyphs.mp4 . * in menu of gtk application, some glyphs are "fixed" by opening the menu, but not all. For example, in xfce4-terminal, letter A of "Affichage" and its menu content as well as "Aide" is affected. Opening "Affichage" menu does not fix anything. Opening "Aide" menu fixes the "A" of "Aide". Changing window size reactivates the bug on "A" or "Aide". See video 2016y02m18d_16h14m25s_0100Z_glyph-redrawn- bug.mp4 . * text under icons on desktop is affected, but shadows are not. See 2016y02m16d_21h32m11s_0100Z_x_bug_reenabling_antialias_reactivates_problem_shadow_unaffected.png # Affected applications Affected applications include: * xfce whisker menu, * xfce4-terminal (nealy all screenshots) * firefox (see 2016y02m17d_18h08m27s_0100Z_x_bug_glyph_firefox_gnome_org.png 2016y02m16d_21h32m11s_0100Z_x_bug_reenabling_antialias_reactivates_problem_shadow_unaffected.png ), * thunderbird (see 2016y02m16d_21h28m35s_0100Z_x_bug_affects_thunderbird_terminal.png ), * emacs (see 2016y02m10d_18h41m49s_0100Z_wow_screen_flickers_and_most_glyphs_wrong_00.png and subsequent ), * superswitcher ( a gtk/gdk app) * *NOT* affected: xterm, xmessage. Perhaps only gtk/gdk/pango/cairo apps are affected. # Additional information This looks like a cache corruption somewhere. On IRC #pango, someone suggested a bug in Intel driver. Running `xfce4-appearance-settings` and there changing any of: * antialiasing enable/disable, * hinting strength, * subpixel alignment * or dpi immediately cures the bug (see 2016y02m16d_21h31m52s_0100Z_x_bug_disabling_antialias_immediately_cures_problem.png ) Setting back the exact same parameters immediately reactivates the bug (see 2016y02m16d_21h32m11s_0100Z_x_bug_reenabling_antialias_reactivates_problem_shadow_unaffected.png). It is believed that keeping any new settings for a while will have the bug reoccur. It is not like bug 1536751. That one affects rendering quality of *all* glyphs, at all times, depending on dpi. This is not the case here: *some* glyphs (randomly chosen) are drawn corrupted (replaced by garbage or absent), not always. # Other 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu export LC_ALL=C ; lsb_release -rd Description: Ubuntu Xenial Xerus (development branch) Release: 16.04 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center apt-cache policy xorg xorg: Installed: 1:7.7+13ubuntu1 Candidate: 1:7.7+13ubuntu1 Version table: *** 1:7.7+13ubuntu1 500 500 http://fr.archive.ubuntu.com/ubuntu xenial/main amd64 Packages 100 /var/lib/dpkg/status 3) What you expected to happen 4) What happened instead Written above. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-4.19-generic 4.4.1 Uname: Linux 4.4.0-4-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 CurrentDesktop: XFCE Date: Thu Feb 18 16:03:55 2016 InstallationDate: Installed on 2016-02-03 (14 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160203) SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.20-0ubuntu3 Architecture:
[Touch-packages] [Bug 1547077] NonfreeKernelModules.txt
apport information ** Attachment added: "NonfreeKernelModules.txt" https://bugs.launchpad.net/bugs/1547077/+attachment/4585291/+files/NonfreeKernelModules.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.launchpad.net/bugs/1547077 Title: Some glyphs drawn consistently wrong, bug comes and go Status in xorg package in Ubuntu: Incomplete Bug description: # Summary * Some glyphs badly drawn at some moments. * When happens, same glyph drawn on various windows shows same corruption. * Problem comes and go. # Context Laptop, using Intel driver. Expected: all glyphs rendered correctly. Observed: some glyphs not rendered correctly * reproducible: sometimes, eventually. Problem comes and go, severity varies from one glyph (see 2016y02m17d_18h08m27s_0100Z_x_bug_glyph_firefox_gnome_org.png ) to all text on screen fully unreadable (see 2016y02m10d_18h42m18s_0100Z_wow_screen_flickers_and_most_glyphs_wrong_01.png ) * *some* glyphs are affected. For example, letter 'a' of a certain size will be replaced by colored garbage at many places where it appears (see 2016y02m18d_16h05m35s_0100Z_same_corruption_on_different_windows.png ), but other 'a' with different size, italic, bold, etc will be unaffected. * in some applications (e.g. xfce whisker menu), some glyphs are rendered correctly or not depending on the direction of mouse hovering. See video 2016y02m16d_21h41m14s_0100Z_whisker_menu_missing_glyphs.mp4 . * in menu of gtk application, some glyphs are "fixed" by opening the menu, but not all. For example, in xfce4-terminal, letter A of "Affichage" and its menu content as well as "Aide" is affected. Opening "Affichage" menu does not fix anything. Opening "Aide" menu fixes the "A" of "Aide". Changing window size reactivates the bug on "A" or "Aide". See video 2016y02m18d_16h14m25s_0100Z_glyph-redrawn- bug.mp4 . * text under icons on desktop is affected, but shadows are not. See 2016y02m16d_21h32m11s_0100Z_x_bug_reenabling_antialias_reactivates_problem_shadow_unaffected.png # Affected applications Affected applications include: * xfce whisker menu, * xfce4-terminal (nealy all screenshots) * firefox (see 2016y02m17d_18h08m27s_0100Z_x_bug_glyph_firefox_gnome_org.png 2016y02m16d_21h32m11s_0100Z_x_bug_reenabling_antialias_reactivates_problem_shadow_unaffected.png ), * thunderbird (see 2016y02m16d_21h28m35s_0100Z_x_bug_affects_thunderbird_terminal.png ), * emacs (see 2016y02m10d_18h41m49s_0100Z_wow_screen_flickers_and_most_glyphs_wrong_00.png and subsequent ), * superswitcher ( a gtk/gdk app) * *NOT* affected: xterm, xmessage. Perhaps only gtk/gdk/pango/cairo apps are affected. # Additional information This looks like a cache corruption somewhere. On IRC #pango, someone suggested a bug in Intel driver. Running `xfce4-appearance-settings` and there changing any of: * antialiasing enable/disable, * hinting strength, * subpixel alignment * or dpi immediately cures the bug (see 2016y02m16d_21h31m52s_0100Z_x_bug_disabling_antialias_immediately_cures_problem.png ) Setting back the exact same parameters immediately reactivates the bug (see 2016y02m16d_21h32m11s_0100Z_x_bug_reenabling_antialias_reactivates_problem_shadow_unaffected.png). It is believed that keeping any new settings for a while will have the bug reoccur. It is not like bug 1536751. That one affects rendering quality of *all* glyphs, at all times, depending on dpi. This is not the case here: *some* glyphs (randomly chosen) are drawn corrupted (replaced by garbage or absent), not always. # Other 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu export LC_ALL=C ; lsb_release -rd Description: Ubuntu Xenial Xerus (development branch) Release: 16.04 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center apt-cache policy xorg xorg: Installed: 1:7.7+13ubuntu1 Candidate: 1:7.7+13ubuntu1 Version table: *** 1:7.7+13ubuntu1 500 500 http://fr.archive.ubuntu.com/ubuntu xenial/main amd64 Packages 100 /var/lib/dpkg/status 3) What you expected to happen 4) What happened instead Written above. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-4.19-generic 4.4.1 Uname: Linux 4.4.0-4-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 CurrentDesktop: XFCE Date: Thu Feb 18 16:03:55 2016 InstallationDate: Installed on 2016-02-03 (14 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160203) SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion:
[Touch-packages] [Bug 1547077] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1547077/+attachment/4585289/+files/Lspci.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.launchpad.net/bugs/1547077 Title: Some glyphs drawn consistently wrong, bug comes and go Status in xorg package in Ubuntu: Incomplete Bug description: # Summary * Some glyphs badly drawn at some moments. * When happens, same glyph drawn on various windows shows same corruption. * Problem comes and go. # Context Laptop, using Intel driver. Expected: all glyphs rendered correctly. Observed: some glyphs not rendered correctly * reproducible: sometimes, eventually. Problem comes and go, severity varies from one glyph (see 2016y02m17d_18h08m27s_0100Z_x_bug_glyph_firefox_gnome_org.png ) to all text on screen fully unreadable (see 2016y02m10d_18h42m18s_0100Z_wow_screen_flickers_and_most_glyphs_wrong_01.png ) * *some* glyphs are affected. For example, letter 'a' of a certain size will be replaced by colored garbage at many places where it appears (see 2016y02m18d_16h05m35s_0100Z_same_corruption_on_different_windows.png ), but other 'a' with different size, italic, bold, etc will be unaffected. * in some applications (e.g. xfce whisker menu), some glyphs are rendered correctly or not depending on the direction of mouse hovering. See video 2016y02m16d_21h41m14s_0100Z_whisker_menu_missing_glyphs.mp4 . * in menu of gtk application, some glyphs are "fixed" by opening the menu, but not all. For example, in xfce4-terminal, letter A of "Affichage" and its menu content as well as "Aide" is affected. Opening "Affichage" menu does not fix anything. Opening "Aide" menu fixes the "A" of "Aide". Changing window size reactivates the bug on "A" or "Aide". See video 2016y02m18d_16h14m25s_0100Z_glyph-redrawn- bug.mp4 . * text under icons on desktop is affected, but shadows are not. See 2016y02m16d_21h32m11s_0100Z_x_bug_reenabling_antialias_reactivates_problem_shadow_unaffected.png # Affected applications Affected applications include: * xfce whisker menu, * xfce4-terminal (nealy all screenshots) * firefox (see 2016y02m17d_18h08m27s_0100Z_x_bug_glyph_firefox_gnome_org.png 2016y02m16d_21h32m11s_0100Z_x_bug_reenabling_antialias_reactivates_problem_shadow_unaffected.png ), * thunderbird (see 2016y02m16d_21h28m35s_0100Z_x_bug_affects_thunderbird_terminal.png ), * emacs (see 2016y02m10d_18h41m49s_0100Z_wow_screen_flickers_and_most_glyphs_wrong_00.png and subsequent ), * superswitcher ( a gtk/gdk app) * *NOT* affected: xterm, xmessage. Perhaps only gtk/gdk/pango/cairo apps are affected. # Additional information This looks like a cache corruption somewhere. On IRC #pango, someone suggested a bug in Intel driver. Running `xfce4-appearance-settings` and there changing any of: * antialiasing enable/disable, * hinting strength, * subpixel alignment * or dpi immediately cures the bug (see 2016y02m16d_21h31m52s_0100Z_x_bug_disabling_antialias_immediately_cures_problem.png ) Setting back the exact same parameters immediately reactivates the bug (see 2016y02m16d_21h32m11s_0100Z_x_bug_reenabling_antialias_reactivates_problem_shadow_unaffected.png). It is believed that keeping any new settings for a while will have the bug reoccur. It is not like bug 1536751. That one affects rendering quality of *all* glyphs, at all times, depending on dpi. This is not the case here: *some* glyphs (randomly chosen) are drawn corrupted (replaced by garbage or absent), not always. # Other 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu export LC_ALL=C ; lsb_release -rd Description: Ubuntu Xenial Xerus (development branch) Release: 16.04 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center apt-cache policy xorg xorg: Installed: 1:7.7+13ubuntu1 Candidate: 1:7.7+13ubuntu1 Version table: *** 1:7.7+13ubuntu1 500 500 http://fr.archive.ubuntu.com/ubuntu xenial/main amd64 Packages 100 /var/lib/dpkg/status 3) What you expected to happen 4) What happened instead Written above. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-4.19-generic 4.4.1 Uname: Linux 4.4.0-4-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 CurrentDesktop: XFCE Date: Thu Feb 18 16:03:55 2016 InstallationDate: Installed on 2016-02-03 (14 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160203) SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.20-0ubuntu3 Architecture: amd64
[Touch-packages] [Bug 1547077] XorgLog.txt
apport information ** Attachment added: "XorgLog.txt" https://bugs.launchpad.net/bugs/1547077/+attachment/4585297/+files/XorgLog.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.launchpad.net/bugs/1547077 Title: Some glyphs drawn consistently wrong, bug comes and go Status in xorg package in Ubuntu: Incomplete Bug description: # Summary * Some glyphs badly drawn at some moments. * When happens, same glyph drawn on various windows shows same corruption. * Problem comes and go. # Context Laptop, using Intel driver. Expected: all glyphs rendered correctly. Observed: some glyphs not rendered correctly * reproducible: sometimes, eventually. Problem comes and go, severity varies from one glyph (see 2016y02m17d_18h08m27s_0100Z_x_bug_glyph_firefox_gnome_org.png ) to all text on screen fully unreadable (see 2016y02m10d_18h42m18s_0100Z_wow_screen_flickers_and_most_glyphs_wrong_01.png ) * *some* glyphs are affected. For example, letter 'a' of a certain size will be replaced by colored garbage at many places where it appears (see 2016y02m18d_16h05m35s_0100Z_same_corruption_on_different_windows.png ), but other 'a' with different size, italic, bold, etc will be unaffected. * in some applications (e.g. xfce whisker menu), some glyphs are rendered correctly or not depending on the direction of mouse hovering. See video 2016y02m16d_21h41m14s_0100Z_whisker_menu_missing_glyphs.mp4 . * in menu of gtk application, some glyphs are "fixed" by opening the menu, but not all. For example, in xfce4-terminal, letter A of "Affichage" and its menu content as well as "Aide" is affected. Opening "Affichage" menu does not fix anything. Opening "Aide" menu fixes the "A" of "Aide". Changing window size reactivates the bug on "A" or "Aide". See video 2016y02m18d_16h14m25s_0100Z_glyph-redrawn- bug.mp4 . * text under icons on desktop is affected, but shadows are not. See 2016y02m16d_21h32m11s_0100Z_x_bug_reenabling_antialias_reactivates_problem_shadow_unaffected.png # Affected applications Affected applications include: * xfce whisker menu, * xfce4-terminal (nealy all screenshots) * firefox (see 2016y02m17d_18h08m27s_0100Z_x_bug_glyph_firefox_gnome_org.png 2016y02m16d_21h32m11s_0100Z_x_bug_reenabling_antialias_reactivates_problem_shadow_unaffected.png ), * thunderbird (see 2016y02m16d_21h28m35s_0100Z_x_bug_affects_thunderbird_terminal.png ), * emacs (see 2016y02m10d_18h41m49s_0100Z_wow_screen_flickers_and_most_glyphs_wrong_00.png and subsequent ), * superswitcher ( a gtk/gdk app) * *NOT* affected: xterm, xmessage. Perhaps only gtk/gdk/pango/cairo apps are affected. # Additional information This looks like a cache corruption somewhere. On IRC #pango, someone suggested a bug in Intel driver. Running `xfce4-appearance-settings` and there changing any of: * antialiasing enable/disable, * hinting strength, * subpixel alignment * or dpi immediately cures the bug (see 2016y02m16d_21h31m52s_0100Z_x_bug_disabling_antialias_immediately_cures_problem.png ) Setting back the exact same parameters immediately reactivates the bug (see 2016y02m16d_21h32m11s_0100Z_x_bug_reenabling_antialias_reactivates_problem_shadow_unaffected.png). It is believed that keeping any new settings for a while will have the bug reoccur. It is not like bug 1536751. That one affects rendering quality of *all* glyphs, at all times, depending on dpi. This is not the case here: *some* glyphs (randomly chosen) are drawn corrupted (replaced by garbage or absent), not always. # Other 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu export LC_ALL=C ; lsb_release -rd Description: Ubuntu Xenial Xerus (development branch) Release: 16.04 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center apt-cache policy xorg xorg: Installed: 1:7.7+13ubuntu1 Candidate: 1:7.7+13ubuntu1 Version table: *** 1:7.7+13ubuntu1 500 500 http://fr.archive.ubuntu.com/ubuntu xenial/main amd64 Packages 100 /var/lib/dpkg/status 3) What you expected to happen 4) What happened instead Written above. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-4.19-generic 4.4.1 Uname: Linux 4.4.0-4-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 CurrentDesktop: XFCE Date: Thu Feb 18 16:03:55 2016 InstallationDate: Installed on 2016-02-03 (14 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160203) SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.20-0ubuntu3 Architecture:
[Touch-packages] [Bug 1547077] Xrandr.txt
apport information ** Attachment added: "Xrandr.txt" https://bugs.launchpad.net/bugs/1547077/+attachment/4585299/+files/Xrandr.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.launchpad.net/bugs/1547077 Title: Some glyphs drawn consistently wrong, bug comes and go Status in xorg package in Ubuntu: Incomplete Bug description: # Summary * Some glyphs badly drawn at some moments. * When happens, same glyph drawn on various windows shows same corruption. * Problem comes and go. # Context Laptop, using Intel driver. Expected: all glyphs rendered correctly. Observed: some glyphs not rendered correctly * reproducible: sometimes, eventually. Problem comes and go, severity varies from one glyph (see 2016y02m17d_18h08m27s_0100Z_x_bug_glyph_firefox_gnome_org.png ) to all text on screen fully unreadable (see 2016y02m10d_18h42m18s_0100Z_wow_screen_flickers_and_most_glyphs_wrong_01.png ) * *some* glyphs are affected. For example, letter 'a' of a certain size will be replaced by colored garbage at many places where it appears (see 2016y02m18d_16h05m35s_0100Z_same_corruption_on_different_windows.png ), but other 'a' with different size, italic, bold, etc will be unaffected. * in some applications (e.g. xfce whisker menu), some glyphs are rendered correctly or not depending on the direction of mouse hovering. See video 2016y02m16d_21h41m14s_0100Z_whisker_menu_missing_glyphs.mp4 . * in menu of gtk application, some glyphs are "fixed" by opening the menu, but not all. For example, in xfce4-terminal, letter A of "Affichage" and its menu content as well as "Aide" is affected. Opening "Affichage" menu does not fix anything. Opening "Aide" menu fixes the "A" of "Aide". Changing window size reactivates the bug on "A" or "Aide". See video 2016y02m18d_16h14m25s_0100Z_glyph-redrawn- bug.mp4 . * text under icons on desktop is affected, but shadows are not. See 2016y02m16d_21h32m11s_0100Z_x_bug_reenabling_antialias_reactivates_problem_shadow_unaffected.png # Affected applications Affected applications include: * xfce whisker menu, * xfce4-terminal (nealy all screenshots) * firefox (see 2016y02m17d_18h08m27s_0100Z_x_bug_glyph_firefox_gnome_org.png 2016y02m16d_21h32m11s_0100Z_x_bug_reenabling_antialias_reactivates_problem_shadow_unaffected.png ), * thunderbird (see 2016y02m16d_21h28m35s_0100Z_x_bug_affects_thunderbird_terminal.png ), * emacs (see 2016y02m10d_18h41m49s_0100Z_wow_screen_flickers_and_most_glyphs_wrong_00.png and subsequent ), * superswitcher ( a gtk/gdk app) * *NOT* affected: xterm, xmessage. Perhaps only gtk/gdk/pango/cairo apps are affected. # Additional information This looks like a cache corruption somewhere. On IRC #pango, someone suggested a bug in Intel driver. Running `xfce4-appearance-settings` and there changing any of: * antialiasing enable/disable, * hinting strength, * subpixel alignment * or dpi immediately cures the bug (see 2016y02m16d_21h31m52s_0100Z_x_bug_disabling_antialias_immediately_cures_problem.png ) Setting back the exact same parameters immediately reactivates the bug (see 2016y02m16d_21h32m11s_0100Z_x_bug_reenabling_antialias_reactivates_problem_shadow_unaffected.png). It is believed that keeping any new settings for a while will have the bug reoccur. It is not like bug 1536751. That one affects rendering quality of *all* glyphs, at all times, depending on dpi. This is not the case here: *some* glyphs (randomly chosen) are drawn corrupted (replaced by garbage or absent), not always. # Other 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu export LC_ALL=C ; lsb_release -rd Description: Ubuntu Xenial Xerus (development branch) Release: 16.04 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center apt-cache policy xorg xorg: Installed: 1:7.7+13ubuntu1 Candidate: 1:7.7+13ubuntu1 Version table: *** 1:7.7+13ubuntu1 500 500 http://fr.archive.ubuntu.com/ubuntu xenial/main amd64 Packages 100 /var/lib/dpkg/status 3) What you expected to happen 4) What happened instead Written above. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-4.19-generic 4.4.1 Uname: Linux 4.4.0-4-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 CurrentDesktop: XFCE Date: Thu Feb 18 16:03:55 2016 InstallationDate: Installed on 2016-02-03 (14 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160203) SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.20-0ubuntu3 Architecture: amd64
[Touch-packages] [Bug 1547077] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1547077/+attachment/4585296/+files/UdevDb.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.launchpad.net/bugs/1547077 Title: Some glyphs drawn consistently wrong, bug comes and go Status in xorg package in Ubuntu: Incomplete Bug description: # Summary * Some glyphs badly drawn at some moments. * When happens, same glyph drawn on various windows shows same corruption. * Problem comes and go. # Context Laptop, using Intel driver. Expected: all glyphs rendered correctly. Observed: some glyphs not rendered correctly * reproducible: sometimes, eventually. Problem comes and go, severity varies from one glyph (see 2016y02m17d_18h08m27s_0100Z_x_bug_glyph_firefox_gnome_org.png ) to all text on screen fully unreadable (see 2016y02m10d_18h42m18s_0100Z_wow_screen_flickers_and_most_glyphs_wrong_01.png ) * *some* glyphs are affected. For example, letter 'a' of a certain size will be replaced by colored garbage at many places where it appears (see 2016y02m18d_16h05m35s_0100Z_same_corruption_on_different_windows.png ), but other 'a' with different size, italic, bold, etc will be unaffected. * in some applications (e.g. xfce whisker menu), some glyphs are rendered correctly or not depending on the direction of mouse hovering. See video 2016y02m16d_21h41m14s_0100Z_whisker_menu_missing_glyphs.mp4 . * in menu of gtk application, some glyphs are "fixed" by opening the menu, but not all. For example, in xfce4-terminal, letter A of "Affichage" and its menu content as well as "Aide" is affected. Opening "Affichage" menu does not fix anything. Opening "Aide" menu fixes the "A" of "Aide". Changing window size reactivates the bug on "A" or "Aide". See video 2016y02m18d_16h14m25s_0100Z_glyph-redrawn- bug.mp4 . * text under icons on desktop is affected, but shadows are not. See 2016y02m16d_21h32m11s_0100Z_x_bug_reenabling_antialias_reactivates_problem_shadow_unaffected.png # Affected applications Affected applications include: * xfce whisker menu, * xfce4-terminal (nealy all screenshots) * firefox (see 2016y02m17d_18h08m27s_0100Z_x_bug_glyph_firefox_gnome_org.png 2016y02m16d_21h32m11s_0100Z_x_bug_reenabling_antialias_reactivates_problem_shadow_unaffected.png ), * thunderbird (see 2016y02m16d_21h28m35s_0100Z_x_bug_affects_thunderbird_terminal.png ), * emacs (see 2016y02m10d_18h41m49s_0100Z_wow_screen_flickers_and_most_glyphs_wrong_00.png and subsequent ), * superswitcher ( a gtk/gdk app) * *NOT* affected: xterm, xmessage. Perhaps only gtk/gdk/pango/cairo apps are affected. # Additional information This looks like a cache corruption somewhere. On IRC #pango, someone suggested a bug in Intel driver. Running `xfce4-appearance-settings` and there changing any of: * antialiasing enable/disable, * hinting strength, * subpixel alignment * or dpi immediately cures the bug (see 2016y02m16d_21h31m52s_0100Z_x_bug_disabling_antialias_immediately_cures_problem.png ) Setting back the exact same parameters immediately reactivates the bug (see 2016y02m16d_21h32m11s_0100Z_x_bug_reenabling_antialias_reactivates_problem_shadow_unaffected.png). It is believed that keeping any new settings for a while will have the bug reoccur. It is not like bug 1536751. That one affects rendering quality of *all* glyphs, at all times, depending on dpi. This is not the case here: *some* glyphs (randomly chosen) are drawn corrupted (replaced by garbage or absent), not always. # Other 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu export LC_ALL=C ; lsb_release -rd Description: Ubuntu Xenial Xerus (development branch) Release: 16.04 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center apt-cache policy xorg xorg: Installed: 1:7.7+13ubuntu1 Candidate: 1:7.7+13ubuntu1 Version table: *** 1:7.7+13ubuntu1 500 500 http://fr.archive.ubuntu.com/ubuntu xenial/main amd64 Packages 100 /var/lib/dpkg/status 3) What you expected to happen 4) What happened instead Written above. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-4.19-generic 4.4.1 Uname: Linux 4.4.0-4-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 CurrentDesktop: XFCE Date: Thu Feb 18 16:03:55 2016 InstallationDate: Installed on 2016-02-03 (14 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160203) SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.20-0ubuntu3 Architecture: amd64
[Touch-packages] [Bug 1547077] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1547077/+attachment/4585294/+files/ProcInterrupts.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.launchpad.net/bugs/1547077 Title: Some glyphs drawn consistently wrong, bug comes and go Status in xorg package in Ubuntu: Incomplete Bug description: # Summary * Some glyphs badly drawn at some moments. * When happens, same glyph drawn on various windows shows same corruption. * Problem comes and go. # Context Laptop, using Intel driver. Expected: all glyphs rendered correctly. Observed: some glyphs not rendered correctly * reproducible: sometimes, eventually. Problem comes and go, severity varies from one glyph (see 2016y02m17d_18h08m27s_0100Z_x_bug_glyph_firefox_gnome_org.png ) to all text on screen fully unreadable (see 2016y02m10d_18h42m18s_0100Z_wow_screen_flickers_and_most_glyphs_wrong_01.png ) * *some* glyphs are affected. For example, letter 'a' of a certain size will be replaced by colored garbage at many places where it appears (see 2016y02m18d_16h05m35s_0100Z_same_corruption_on_different_windows.png ), but other 'a' with different size, italic, bold, etc will be unaffected. * in some applications (e.g. xfce whisker menu), some glyphs are rendered correctly or not depending on the direction of mouse hovering. See video 2016y02m16d_21h41m14s_0100Z_whisker_menu_missing_glyphs.mp4 . * in menu of gtk application, some glyphs are "fixed" by opening the menu, but not all. For example, in xfce4-terminal, letter A of "Affichage" and its menu content as well as "Aide" is affected. Opening "Affichage" menu does not fix anything. Opening "Aide" menu fixes the "A" of "Aide". Changing window size reactivates the bug on "A" or "Aide". See video 2016y02m18d_16h14m25s_0100Z_glyph-redrawn- bug.mp4 . * text under icons on desktop is affected, but shadows are not. See 2016y02m16d_21h32m11s_0100Z_x_bug_reenabling_antialias_reactivates_problem_shadow_unaffected.png # Affected applications Affected applications include: * xfce whisker menu, * xfce4-terminal (nealy all screenshots) * firefox (see 2016y02m17d_18h08m27s_0100Z_x_bug_glyph_firefox_gnome_org.png 2016y02m16d_21h32m11s_0100Z_x_bug_reenabling_antialias_reactivates_problem_shadow_unaffected.png ), * thunderbird (see 2016y02m16d_21h28m35s_0100Z_x_bug_affects_thunderbird_terminal.png ), * emacs (see 2016y02m10d_18h41m49s_0100Z_wow_screen_flickers_and_most_glyphs_wrong_00.png and subsequent ), * superswitcher ( a gtk/gdk app) * *NOT* affected: xterm, xmessage. Perhaps only gtk/gdk/pango/cairo apps are affected. # Additional information This looks like a cache corruption somewhere. On IRC #pango, someone suggested a bug in Intel driver. Running `xfce4-appearance-settings` and there changing any of: * antialiasing enable/disable, * hinting strength, * subpixel alignment * or dpi immediately cures the bug (see 2016y02m16d_21h31m52s_0100Z_x_bug_disabling_antialias_immediately_cures_problem.png ) Setting back the exact same parameters immediately reactivates the bug (see 2016y02m16d_21h32m11s_0100Z_x_bug_reenabling_antialias_reactivates_problem_shadow_unaffected.png). It is believed that keeping any new settings for a while will have the bug reoccur. It is not like bug 1536751. That one affects rendering quality of *all* glyphs, at all times, depending on dpi. This is not the case here: *some* glyphs (randomly chosen) are drawn corrupted (replaced by garbage or absent), not always. # Other 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu export LC_ALL=C ; lsb_release -rd Description: Ubuntu Xenial Xerus (development branch) Release: 16.04 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center apt-cache policy xorg xorg: Installed: 1:7.7+13ubuntu1 Candidate: 1:7.7+13ubuntu1 Version table: *** 1:7.7+13ubuntu1 500 500 http://fr.archive.ubuntu.com/ubuntu xenial/main amd64 Packages 100 /var/lib/dpkg/status 3) What you expected to happen 4) What happened instead Written above. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-4.19-generic 4.4.1 Uname: Linux 4.4.0-4-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 CurrentDesktop: XFCE Date: Thu Feb 18 16:03:55 2016 InstallationDate: Installed on 2016-02-03 (14 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160203) SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.20-0ubuntu3
[Touch-packages] [Bug 1547077] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1547077/+attachment/4585295/+files/ProcModules.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.launchpad.net/bugs/1547077 Title: Some glyphs drawn consistently wrong, bug comes and go Status in xorg package in Ubuntu: Incomplete Bug description: # Summary * Some glyphs badly drawn at some moments. * When happens, same glyph drawn on various windows shows same corruption. * Problem comes and go. # Context Laptop, using Intel driver. Expected: all glyphs rendered correctly. Observed: some glyphs not rendered correctly * reproducible: sometimes, eventually. Problem comes and go, severity varies from one glyph (see 2016y02m17d_18h08m27s_0100Z_x_bug_glyph_firefox_gnome_org.png ) to all text on screen fully unreadable (see 2016y02m10d_18h42m18s_0100Z_wow_screen_flickers_and_most_glyphs_wrong_01.png ) * *some* glyphs are affected. For example, letter 'a' of a certain size will be replaced by colored garbage at many places where it appears (see 2016y02m18d_16h05m35s_0100Z_same_corruption_on_different_windows.png ), but other 'a' with different size, italic, bold, etc will be unaffected. * in some applications (e.g. xfce whisker menu), some glyphs are rendered correctly or not depending on the direction of mouse hovering. See video 2016y02m16d_21h41m14s_0100Z_whisker_menu_missing_glyphs.mp4 . * in menu of gtk application, some glyphs are "fixed" by opening the menu, but not all. For example, in xfce4-terminal, letter A of "Affichage" and its menu content as well as "Aide" is affected. Opening "Affichage" menu does not fix anything. Opening "Aide" menu fixes the "A" of "Aide". Changing window size reactivates the bug on "A" or "Aide". See video 2016y02m18d_16h14m25s_0100Z_glyph-redrawn- bug.mp4 . * text under icons on desktop is affected, but shadows are not. See 2016y02m16d_21h32m11s_0100Z_x_bug_reenabling_antialias_reactivates_problem_shadow_unaffected.png # Affected applications Affected applications include: * xfce whisker menu, * xfce4-terminal (nealy all screenshots) * firefox (see 2016y02m17d_18h08m27s_0100Z_x_bug_glyph_firefox_gnome_org.png 2016y02m16d_21h32m11s_0100Z_x_bug_reenabling_antialias_reactivates_problem_shadow_unaffected.png ), * thunderbird (see 2016y02m16d_21h28m35s_0100Z_x_bug_affects_thunderbird_terminal.png ), * emacs (see 2016y02m10d_18h41m49s_0100Z_wow_screen_flickers_and_most_glyphs_wrong_00.png and subsequent ), * superswitcher ( a gtk/gdk app) * *NOT* affected: xterm, xmessage. Perhaps only gtk/gdk/pango/cairo apps are affected. # Additional information This looks like a cache corruption somewhere. On IRC #pango, someone suggested a bug in Intel driver. Running `xfce4-appearance-settings` and there changing any of: * antialiasing enable/disable, * hinting strength, * subpixel alignment * or dpi immediately cures the bug (see 2016y02m16d_21h31m52s_0100Z_x_bug_disabling_antialias_immediately_cures_problem.png ) Setting back the exact same parameters immediately reactivates the bug (see 2016y02m16d_21h32m11s_0100Z_x_bug_reenabling_antialias_reactivates_problem_shadow_unaffected.png). It is believed that keeping any new settings for a while will have the bug reoccur. It is not like bug 1536751. That one affects rendering quality of *all* glyphs, at all times, depending on dpi. This is not the case here: *some* glyphs (randomly chosen) are drawn corrupted (replaced by garbage or absent), not always. # Other 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu export LC_ALL=C ; lsb_release -rd Description: Ubuntu Xenial Xerus (development branch) Release: 16.04 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center apt-cache policy xorg xorg: Installed: 1:7.7+13ubuntu1 Candidate: 1:7.7+13ubuntu1 Version table: *** 1:7.7+13ubuntu1 500 500 http://fr.archive.ubuntu.com/ubuntu xenial/main amd64 Packages 100 /var/lib/dpkg/status 3) What you expected to happen 4) What happened instead Written above. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-4.19-generic 4.4.1 Uname: Linux 4.4.0-4-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 CurrentDesktop: XFCE Date: Thu Feb 18 16:03:55 2016 InstallationDate: Installed on 2016-02-03 (14 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160203) SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.20-0ubuntu3
[Touch-packages] [Bug 1547077] LightdmLog.txt
apport information ** Attachment added: "LightdmLog.txt" https://bugs.launchpad.net/bugs/1547077/+attachment/4585288/+files/LightdmLog.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.launchpad.net/bugs/1547077 Title: Some glyphs drawn consistently wrong, bug comes and go Status in xorg package in Ubuntu: Incomplete Bug description: # Summary * Some glyphs badly drawn at some moments. * When happens, same glyph drawn on various windows shows same corruption. * Problem comes and go. # Context Laptop, using Intel driver. Expected: all glyphs rendered correctly. Observed: some glyphs not rendered correctly * reproducible: sometimes, eventually. Problem comes and go, severity varies from one glyph (see 2016y02m17d_18h08m27s_0100Z_x_bug_glyph_firefox_gnome_org.png ) to all text on screen fully unreadable (see 2016y02m10d_18h42m18s_0100Z_wow_screen_flickers_and_most_glyphs_wrong_01.png ) * *some* glyphs are affected. For example, letter 'a' of a certain size will be replaced by colored garbage at many places where it appears (see 2016y02m18d_16h05m35s_0100Z_same_corruption_on_different_windows.png ), but other 'a' with different size, italic, bold, etc will be unaffected. * in some applications (e.g. xfce whisker menu), some glyphs are rendered correctly or not depending on the direction of mouse hovering. See video 2016y02m16d_21h41m14s_0100Z_whisker_menu_missing_glyphs.mp4 . * in menu of gtk application, some glyphs are "fixed" by opening the menu, but not all. For example, in xfce4-terminal, letter A of "Affichage" and its menu content as well as "Aide" is affected. Opening "Affichage" menu does not fix anything. Opening "Aide" menu fixes the "A" of "Aide". Changing window size reactivates the bug on "A" or "Aide". See video 2016y02m18d_16h14m25s_0100Z_glyph-redrawn- bug.mp4 . * text under icons on desktop is affected, but shadows are not. See 2016y02m16d_21h32m11s_0100Z_x_bug_reenabling_antialias_reactivates_problem_shadow_unaffected.png # Affected applications Affected applications include: * xfce whisker menu, * xfce4-terminal (nealy all screenshots) * firefox (see 2016y02m17d_18h08m27s_0100Z_x_bug_glyph_firefox_gnome_org.png 2016y02m16d_21h32m11s_0100Z_x_bug_reenabling_antialias_reactivates_problem_shadow_unaffected.png ), * thunderbird (see 2016y02m16d_21h28m35s_0100Z_x_bug_affects_thunderbird_terminal.png ), * emacs (see 2016y02m10d_18h41m49s_0100Z_wow_screen_flickers_and_most_glyphs_wrong_00.png and subsequent ), * superswitcher ( a gtk/gdk app) * *NOT* affected: xterm, xmessage. Perhaps only gtk/gdk/pango/cairo apps are affected. # Additional information This looks like a cache corruption somewhere. On IRC #pango, someone suggested a bug in Intel driver. Running `xfce4-appearance-settings` and there changing any of: * antialiasing enable/disable, * hinting strength, * subpixel alignment * or dpi immediately cures the bug (see 2016y02m16d_21h31m52s_0100Z_x_bug_disabling_antialias_immediately_cures_problem.png ) Setting back the exact same parameters immediately reactivates the bug (see 2016y02m16d_21h32m11s_0100Z_x_bug_reenabling_antialias_reactivates_problem_shadow_unaffected.png). It is believed that keeping any new settings for a while will have the bug reoccur. It is not like bug 1536751. That one affects rendering quality of *all* glyphs, at all times, depending on dpi. This is not the case here: *some* glyphs (randomly chosen) are drawn corrupted (replaced by garbage or absent), not always. # Other 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu export LC_ALL=C ; lsb_release -rd Description: Ubuntu Xenial Xerus (development branch) Release: 16.04 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center apt-cache policy xorg xorg: Installed: 1:7.7+13ubuntu1 Candidate: 1:7.7+13ubuntu1 Version table: *** 1:7.7+13ubuntu1 500 500 http://fr.archive.ubuntu.com/ubuntu xenial/main amd64 Packages 100 /var/lib/dpkg/status 3) What you expected to happen 4) What happened instead Written above. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-4.19-generic 4.4.1 Uname: Linux 4.4.0-4-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 CurrentDesktop: XFCE Date: Thu Feb 18 16:03:55 2016 InstallationDate: Installed on 2016-02-03 (14 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160203) SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.20-0ubuntu3
[Touch-packages] [Bug 1547077] DpkgLog.txt
apport information ** Attachment added: "DpkgLog.txt" https://bugs.launchpad.net/bugs/1547077/+attachment/4585284/+files/DpkgLog.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.launchpad.net/bugs/1547077 Title: Some glyphs drawn consistently wrong, bug comes and go Status in xorg package in Ubuntu: Incomplete Bug description: # Summary * Some glyphs badly drawn at some moments. * When happens, same glyph drawn on various windows shows same corruption. * Problem comes and go. # Context Laptop, using Intel driver. Expected: all glyphs rendered correctly. Observed: some glyphs not rendered correctly * reproducible: sometimes, eventually. Problem comes and go, severity varies from one glyph (see 2016y02m17d_18h08m27s_0100Z_x_bug_glyph_firefox_gnome_org.png ) to all text on screen fully unreadable (see 2016y02m10d_18h42m18s_0100Z_wow_screen_flickers_and_most_glyphs_wrong_01.png ) * *some* glyphs are affected. For example, letter 'a' of a certain size will be replaced by colored garbage at many places where it appears (see 2016y02m18d_16h05m35s_0100Z_same_corruption_on_different_windows.png ), but other 'a' with different size, italic, bold, etc will be unaffected. * in some applications (e.g. xfce whisker menu), some glyphs are rendered correctly or not depending on the direction of mouse hovering. See video 2016y02m16d_21h41m14s_0100Z_whisker_menu_missing_glyphs.mp4 . * in menu of gtk application, some glyphs are "fixed" by opening the menu, but not all. For example, in xfce4-terminal, letter A of "Affichage" and its menu content as well as "Aide" is affected. Opening "Affichage" menu does not fix anything. Opening "Aide" menu fixes the "A" of "Aide". Changing window size reactivates the bug on "A" or "Aide". See video 2016y02m18d_16h14m25s_0100Z_glyph-redrawn- bug.mp4 . * text under icons on desktop is affected, but shadows are not. See 2016y02m16d_21h32m11s_0100Z_x_bug_reenabling_antialias_reactivates_problem_shadow_unaffected.png # Affected applications Affected applications include: * xfce whisker menu, * xfce4-terminal (nealy all screenshots) * firefox (see 2016y02m17d_18h08m27s_0100Z_x_bug_glyph_firefox_gnome_org.png 2016y02m16d_21h32m11s_0100Z_x_bug_reenabling_antialias_reactivates_problem_shadow_unaffected.png ), * thunderbird (see 2016y02m16d_21h28m35s_0100Z_x_bug_affects_thunderbird_terminal.png ), * emacs (see 2016y02m10d_18h41m49s_0100Z_wow_screen_flickers_and_most_glyphs_wrong_00.png and subsequent ), * superswitcher ( a gtk/gdk app) * *NOT* affected: xterm, xmessage. Perhaps only gtk/gdk/pango/cairo apps are affected. # Additional information This looks like a cache corruption somewhere. On IRC #pango, someone suggested a bug in Intel driver. Running `xfce4-appearance-settings` and there changing any of: * antialiasing enable/disable, * hinting strength, * subpixel alignment * or dpi immediately cures the bug (see 2016y02m16d_21h31m52s_0100Z_x_bug_disabling_antialias_immediately_cures_problem.png ) Setting back the exact same parameters immediately reactivates the bug (see 2016y02m16d_21h32m11s_0100Z_x_bug_reenabling_antialias_reactivates_problem_shadow_unaffected.png). It is believed that keeping any new settings for a while will have the bug reoccur. It is not like bug 1536751. That one affects rendering quality of *all* glyphs, at all times, depending on dpi. This is not the case here: *some* glyphs (randomly chosen) are drawn corrupted (replaced by garbage or absent), not always. # Other 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu export LC_ALL=C ; lsb_release -rd Description: Ubuntu Xenial Xerus (development branch) Release: 16.04 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center apt-cache policy xorg xorg: Installed: 1:7.7+13ubuntu1 Candidate: 1:7.7+13ubuntu1 Version table: *** 1:7.7+13ubuntu1 500 500 http://fr.archive.ubuntu.com/ubuntu xenial/main amd64 Packages 100 /var/lib/dpkg/status 3) What you expected to happen 4) What happened instead Written above. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-4.19-generic 4.4.1 Uname: Linux 4.4.0-4-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 CurrentDesktop: XFCE Date: Thu Feb 18 16:03:55 2016 InstallationDate: Installed on 2016-02-03 (14 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160203) SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.20-0ubuntu3 Architecture:
[Touch-packages] [Bug 1547077] LightdmDisplayLog.txt
apport information ** Attachment added: "LightdmDisplayLog.txt" https://bugs.launchpad.net/bugs/1547077/+attachment/4585286/+files/LightdmDisplayLog.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.launchpad.net/bugs/1547077 Title: Some glyphs drawn consistently wrong, bug comes and go Status in xorg package in Ubuntu: Incomplete Bug description: # Summary * Some glyphs badly drawn at some moments. * When happens, same glyph drawn on various windows shows same corruption. * Problem comes and go. # Context Laptop, using Intel driver. Expected: all glyphs rendered correctly. Observed: some glyphs not rendered correctly * reproducible: sometimes, eventually. Problem comes and go, severity varies from one glyph (see 2016y02m17d_18h08m27s_0100Z_x_bug_glyph_firefox_gnome_org.png ) to all text on screen fully unreadable (see 2016y02m10d_18h42m18s_0100Z_wow_screen_flickers_and_most_glyphs_wrong_01.png ) * *some* glyphs are affected. For example, letter 'a' of a certain size will be replaced by colored garbage at many places where it appears (see 2016y02m18d_16h05m35s_0100Z_same_corruption_on_different_windows.png ), but other 'a' with different size, italic, bold, etc will be unaffected. * in some applications (e.g. xfce whisker menu), some glyphs are rendered correctly or not depending on the direction of mouse hovering. See video 2016y02m16d_21h41m14s_0100Z_whisker_menu_missing_glyphs.mp4 . * in menu of gtk application, some glyphs are "fixed" by opening the menu, but not all. For example, in xfce4-terminal, letter A of "Affichage" and its menu content as well as "Aide" is affected. Opening "Affichage" menu does not fix anything. Opening "Aide" menu fixes the "A" of "Aide". Changing window size reactivates the bug on "A" or "Aide". See video 2016y02m18d_16h14m25s_0100Z_glyph-redrawn- bug.mp4 . * text under icons on desktop is affected, but shadows are not. See 2016y02m16d_21h32m11s_0100Z_x_bug_reenabling_antialias_reactivates_problem_shadow_unaffected.png # Affected applications Affected applications include: * xfce whisker menu, * xfce4-terminal (nealy all screenshots) * firefox (see 2016y02m17d_18h08m27s_0100Z_x_bug_glyph_firefox_gnome_org.png 2016y02m16d_21h32m11s_0100Z_x_bug_reenabling_antialias_reactivates_problem_shadow_unaffected.png ), * thunderbird (see 2016y02m16d_21h28m35s_0100Z_x_bug_affects_thunderbird_terminal.png ), * emacs (see 2016y02m10d_18h41m49s_0100Z_wow_screen_flickers_and_most_glyphs_wrong_00.png and subsequent ), * superswitcher ( a gtk/gdk app) * *NOT* affected: xterm, xmessage. Perhaps only gtk/gdk/pango/cairo apps are affected. # Additional information This looks like a cache corruption somewhere. On IRC #pango, someone suggested a bug in Intel driver. Running `xfce4-appearance-settings` and there changing any of: * antialiasing enable/disable, * hinting strength, * subpixel alignment * or dpi immediately cures the bug (see 2016y02m16d_21h31m52s_0100Z_x_bug_disabling_antialias_immediately_cures_problem.png ) Setting back the exact same parameters immediately reactivates the bug (see 2016y02m16d_21h32m11s_0100Z_x_bug_reenabling_antialias_reactivates_problem_shadow_unaffected.png). It is believed that keeping any new settings for a while will have the bug reoccur. It is not like bug 1536751. That one affects rendering quality of *all* glyphs, at all times, depending on dpi. This is not the case here: *some* glyphs (randomly chosen) are drawn corrupted (replaced by garbage or absent), not always. # Other 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu export LC_ALL=C ; lsb_release -rd Description: Ubuntu Xenial Xerus (development branch) Release: 16.04 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center apt-cache policy xorg xorg: Installed: 1:7.7+13ubuntu1 Candidate: 1:7.7+13ubuntu1 Version table: *** 1:7.7+13ubuntu1 500 500 http://fr.archive.ubuntu.com/ubuntu xenial/main amd64 Packages 100 /var/lib/dpkg/status 3) What you expected to happen 4) What happened instead Written above. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-4.19-generic 4.4.1 Uname: Linux 4.4.0-4-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 CurrentDesktop: XFCE Date: Thu Feb 18 16:03:55 2016 InstallationDate: Installed on 2016-02-03 (14 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160203) SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.20-0ubuntu3
[Touch-packages] [Bug 1547077] Re: Some glyphs drawn consistently wrong, bug comes and go
apport information ** Tags added: apport-collected has-workaround regression reproducible ubuntu ** Description changed: # Summary * Some glyphs badly drawn at some moments. * When happens, same glyph drawn on various windows shows same corruption. * Problem comes and go. # Context Laptop, using Intel driver. Expected: all glyphs rendered correctly. Observed: some glyphs not rendered correctly * reproducible: sometimes, eventually. Problem comes and go, severity varies from one glyph (see 2016y02m17d_18h08m27s_0100Z_x_bug_glyph_firefox_gnome_org.png ) to all text on screen fully unreadable (see 2016y02m10d_18h42m18s_0100Z_wow_screen_flickers_and_most_glyphs_wrong_01.png ) * *some* glyphs are affected. For example, letter 'a' of a certain size will be replaced by colored garbage at many places where it appears (see 2016y02m18d_16h05m35s_0100Z_same_corruption_on_different_windows.png ), but other 'a' with different size, italic, bold, etc will be unaffected. * in some applications (e.g. xfce whisker menu), some glyphs are rendered correctly or not depending on the direction of mouse hovering. See video 2016y02m16d_21h41m14s_0100Z_whisker_menu_missing_glyphs.mp4 . * in menu of gtk application, some glyphs are "fixed" by opening the menu, but not all. For example, in xfce4-terminal, letter A of "Affichage" and its menu content as well as "Aide" is affected. Opening "Affichage" menu does not fix anything. Opening "Aide" menu fixes the "A" of "Aide". Changing window size reactivates the bug on "A" or "Aide". See video 2016y02m18d_16h14m25s_0100Z_glyph-redrawn-bug.mp4 . * text under icons on desktop is affected, but shadows are not. See 2016y02m16d_21h32m11s_0100Z_x_bug_reenabling_antialias_reactivates_problem_shadow_unaffected.png # Affected applications Affected applications include: * xfce whisker menu, * xfce4-terminal (nealy all screenshots) * firefox (see 2016y02m17d_18h08m27s_0100Z_x_bug_glyph_firefox_gnome_org.png 2016y02m16d_21h32m11s_0100Z_x_bug_reenabling_antialias_reactivates_problem_shadow_unaffected.png ), * thunderbird (see 2016y02m16d_21h28m35s_0100Z_x_bug_affects_thunderbird_terminal.png ), * emacs (see 2016y02m10d_18h41m49s_0100Z_wow_screen_flickers_and_most_glyphs_wrong_00.png and subsequent ), * superswitcher ( a gtk/gdk app) * *NOT* affected: xterm, xmessage. Perhaps only gtk/gdk/pango/cairo apps are affected. # Additional information This looks like a cache corruption somewhere. On IRC #pango, someone suggested a bug in Intel driver. Running `xfce4-appearance-settings` and there changing any of: * antialiasing enable/disable, * hinting strength, * subpixel alignment * or dpi immediately cures the bug (see 2016y02m16d_21h31m52s_0100Z_x_bug_disabling_antialias_immediately_cures_problem.png ) Setting back the exact same parameters immediately reactivates the bug (see 2016y02m16d_21h32m11s_0100Z_x_bug_reenabling_antialias_reactivates_problem_shadow_unaffected.png). It is believed that keeping any new settings for a while will have the bug reoccur. It is not like bug 1536751. That one affects rendering quality of *all* glyphs, at all times, depending on dpi. This is not the case here: *some* glyphs (randomly chosen) are drawn corrupted (replaced by garbage or absent), not always. # Other 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu export LC_ALL=C ; lsb_release -rd Description: Ubuntu Xenial Xerus (development branch) Release: 16.04 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center apt-cache policy xorg xorg: Installed: 1:7.7+13ubuntu1 Candidate: 1:7.7+13ubuntu1 Version table: *** 1:7.7+13ubuntu1 500 500 http://fr.archive.ubuntu.com/ubuntu xenial/main amd64 Packages 100 /var/lib/dpkg/status 3) What you expected to happen 4) What happened instead Written above. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-4.19-generic 4.4.1 Uname: Linux 4.4.0-4-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 CurrentDesktop: XFCE Date: Thu Feb 18 16:03:55 2016 InstallationDate: Installed on 2016-02-03 (14 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160203) SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) + --- + ApportVersion: 2.20-0ubuntu3 + Architecture: amd64 + CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' + CompositorRunning: None + CurrentDesktop: XFCE + DistUpgraded: Fresh install + DistroCodename: xenial + DistroRelease: Ubuntu 16.04 + DistroVariant: ubuntu +
[Touch-packages] [Bug 1547077] JournalErrors.txt
apport information ** Attachment added: "JournalErrors.txt" https://bugs.launchpad.net/bugs/1547077/+attachment/4585285/+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.launchpad.net/bugs/1547077 Title: Some glyphs drawn consistently wrong, bug comes and go Status in xorg package in Ubuntu: Incomplete Bug description: # Summary * Some glyphs badly drawn at some moments. * When happens, same glyph drawn on various windows shows same corruption. * Problem comes and go. # Context Laptop, using Intel driver. Expected: all glyphs rendered correctly. Observed: some glyphs not rendered correctly * reproducible: sometimes, eventually. Problem comes and go, severity varies from one glyph (see 2016y02m17d_18h08m27s_0100Z_x_bug_glyph_firefox_gnome_org.png ) to all text on screen fully unreadable (see 2016y02m10d_18h42m18s_0100Z_wow_screen_flickers_and_most_glyphs_wrong_01.png ) * *some* glyphs are affected. For example, letter 'a' of a certain size will be replaced by colored garbage at many places where it appears (see 2016y02m18d_16h05m35s_0100Z_same_corruption_on_different_windows.png ), but other 'a' with different size, italic, bold, etc will be unaffected. * in some applications (e.g. xfce whisker menu), some glyphs are rendered correctly or not depending on the direction of mouse hovering. See video 2016y02m16d_21h41m14s_0100Z_whisker_menu_missing_glyphs.mp4 . * in menu of gtk application, some glyphs are "fixed" by opening the menu, but not all. For example, in xfce4-terminal, letter A of "Affichage" and its menu content as well as "Aide" is affected. Opening "Affichage" menu does not fix anything. Opening "Aide" menu fixes the "A" of "Aide". Changing window size reactivates the bug on "A" or "Aide". See video 2016y02m18d_16h14m25s_0100Z_glyph-redrawn- bug.mp4 . * text under icons on desktop is affected, but shadows are not. See 2016y02m16d_21h32m11s_0100Z_x_bug_reenabling_antialias_reactivates_problem_shadow_unaffected.png # Affected applications Affected applications include: * xfce whisker menu, * xfce4-terminal (nealy all screenshots) * firefox (see 2016y02m17d_18h08m27s_0100Z_x_bug_glyph_firefox_gnome_org.png 2016y02m16d_21h32m11s_0100Z_x_bug_reenabling_antialias_reactivates_problem_shadow_unaffected.png ), * thunderbird (see 2016y02m16d_21h28m35s_0100Z_x_bug_affects_thunderbird_terminal.png ), * emacs (see 2016y02m10d_18h41m49s_0100Z_wow_screen_flickers_and_most_glyphs_wrong_00.png and subsequent ), * superswitcher ( a gtk/gdk app) * *NOT* affected: xterm, xmessage. Perhaps only gtk/gdk/pango/cairo apps are affected. # Additional information This looks like a cache corruption somewhere. On IRC #pango, someone suggested a bug in Intel driver. Running `xfce4-appearance-settings` and there changing any of: * antialiasing enable/disable, * hinting strength, * subpixel alignment * or dpi immediately cures the bug (see 2016y02m16d_21h31m52s_0100Z_x_bug_disabling_antialias_immediately_cures_problem.png ) Setting back the exact same parameters immediately reactivates the bug (see 2016y02m16d_21h32m11s_0100Z_x_bug_reenabling_antialias_reactivates_problem_shadow_unaffected.png). It is believed that keeping any new settings for a while will have the bug reoccur. It is not like bug 1536751. That one affects rendering quality of *all* glyphs, at all times, depending on dpi. This is not the case here: *some* glyphs (randomly chosen) are drawn corrupted (replaced by garbage or absent), not always. # Other 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu export LC_ALL=C ; lsb_release -rd Description: Ubuntu Xenial Xerus (development branch) Release: 16.04 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center apt-cache policy xorg xorg: Installed: 1:7.7+13ubuntu1 Candidate: 1:7.7+13ubuntu1 Version table: *** 1:7.7+13ubuntu1 500 500 http://fr.archive.ubuntu.com/ubuntu xenial/main amd64 Packages 100 /var/lib/dpkg/status 3) What you expected to happen 4) What happened instead Written above. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-4.19-generic 4.4.1 Uname: Linux 4.4.0-4-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 CurrentDesktop: XFCE Date: Thu Feb 18 16:03:55 2016 InstallationDate: Installed on 2016-02-03 (14 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160203) SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.20-0ubuntu3
[Touch-packages] [Bug 1547077] LightdmGreeterLog.txt
apport information ** Attachment added: "LightdmGreeterLog.txt" https://bugs.launchpad.net/bugs/1547077/+attachment/4585287/+files/LightdmGreeterLog.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.launchpad.net/bugs/1547077 Title: Some glyphs drawn consistently wrong, bug comes and go Status in xorg package in Ubuntu: Incomplete Bug description: # Summary * Some glyphs badly drawn at some moments. * When happens, same glyph drawn on various windows shows same corruption. * Problem comes and go. # Context Laptop, using Intel driver. Expected: all glyphs rendered correctly. Observed: some glyphs not rendered correctly * reproducible: sometimes, eventually. Problem comes and go, severity varies from one glyph (see 2016y02m17d_18h08m27s_0100Z_x_bug_glyph_firefox_gnome_org.png ) to all text on screen fully unreadable (see 2016y02m10d_18h42m18s_0100Z_wow_screen_flickers_and_most_glyphs_wrong_01.png ) * *some* glyphs are affected. For example, letter 'a' of a certain size will be replaced by colored garbage at many places where it appears (see 2016y02m18d_16h05m35s_0100Z_same_corruption_on_different_windows.png ), but other 'a' with different size, italic, bold, etc will be unaffected. * in some applications (e.g. xfce whisker menu), some glyphs are rendered correctly or not depending on the direction of mouse hovering. See video 2016y02m16d_21h41m14s_0100Z_whisker_menu_missing_glyphs.mp4 . * in menu of gtk application, some glyphs are "fixed" by opening the menu, but not all. For example, in xfce4-terminal, letter A of "Affichage" and its menu content as well as "Aide" is affected. Opening "Affichage" menu does not fix anything. Opening "Aide" menu fixes the "A" of "Aide". Changing window size reactivates the bug on "A" or "Aide". See video 2016y02m18d_16h14m25s_0100Z_glyph-redrawn- bug.mp4 . * text under icons on desktop is affected, but shadows are not. See 2016y02m16d_21h32m11s_0100Z_x_bug_reenabling_antialias_reactivates_problem_shadow_unaffected.png # Affected applications Affected applications include: * xfce whisker menu, * xfce4-terminal (nealy all screenshots) * firefox (see 2016y02m17d_18h08m27s_0100Z_x_bug_glyph_firefox_gnome_org.png 2016y02m16d_21h32m11s_0100Z_x_bug_reenabling_antialias_reactivates_problem_shadow_unaffected.png ), * thunderbird (see 2016y02m16d_21h28m35s_0100Z_x_bug_affects_thunderbird_terminal.png ), * emacs (see 2016y02m10d_18h41m49s_0100Z_wow_screen_flickers_and_most_glyphs_wrong_00.png and subsequent ), * superswitcher ( a gtk/gdk app) * *NOT* affected: xterm, xmessage. Perhaps only gtk/gdk/pango/cairo apps are affected. # Additional information This looks like a cache corruption somewhere. On IRC #pango, someone suggested a bug in Intel driver. Running `xfce4-appearance-settings` and there changing any of: * antialiasing enable/disable, * hinting strength, * subpixel alignment * or dpi immediately cures the bug (see 2016y02m16d_21h31m52s_0100Z_x_bug_disabling_antialias_immediately_cures_problem.png ) Setting back the exact same parameters immediately reactivates the bug (see 2016y02m16d_21h32m11s_0100Z_x_bug_reenabling_antialias_reactivates_problem_shadow_unaffected.png). It is believed that keeping any new settings for a while will have the bug reoccur. It is not like bug 1536751. That one affects rendering quality of *all* glyphs, at all times, depending on dpi. This is not the case here: *some* glyphs (randomly chosen) are drawn corrupted (replaced by garbage or absent), not always. # Other 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu export LC_ALL=C ; lsb_release -rd Description: Ubuntu Xenial Xerus (development branch) Release: 16.04 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center apt-cache policy xorg xorg: Installed: 1:7.7+13ubuntu1 Candidate: 1:7.7+13ubuntu1 Version table: *** 1:7.7+13ubuntu1 500 500 http://fr.archive.ubuntu.com/ubuntu xenial/main amd64 Packages 100 /var/lib/dpkg/status 3) What you expected to happen 4) What happened instead Written above. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-4.19-generic 4.4.1 Uname: Linux 4.4.0-4-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 CurrentDesktop: XFCE Date: Thu Feb 18 16:03:55 2016 InstallationDate: Installed on 2016-02-03 (14 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160203) SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.20-0ubuntu3
[Touch-packages] [Bug 1547077] Dependencies.txt
apport information ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1547077/+attachment/4585283/+files/Dependencies.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.launchpad.net/bugs/1547077 Title: Some glyphs drawn consistently wrong, bug comes and go Status in xorg package in Ubuntu: Incomplete Bug description: # Summary * Some glyphs badly drawn at some moments. * When happens, same glyph drawn on various windows shows same corruption. * Problem comes and go. # Context Laptop, using Intel driver. Expected: all glyphs rendered correctly. Observed: some glyphs not rendered correctly * reproducible: sometimes, eventually. Problem comes and go, severity varies from one glyph (see 2016y02m17d_18h08m27s_0100Z_x_bug_glyph_firefox_gnome_org.png ) to all text on screen fully unreadable (see 2016y02m10d_18h42m18s_0100Z_wow_screen_flickers_and_most_glyphs_wrong_01.png ) * *some* glyphs are affected. For example, letter 'a' of a certain size will be replaced by colored garbage at many places where it appears (see 2016y02m18d_16h05m35s_0100Z_same_corruption_on_different_windows.png ), but other 'a' with different size, italic, bold, etc will be unaffected. * in some applications (e.g. xfce whisker menu), some glyphs are rendered correctly or not depending on the direction of mouse hovering. See video 2016y02m16d_21h41m14s_0100Z_whisker_menu_missing_glyphs.mp4 . * in menu of gtk application, some glyphs are "fixed" by opening the menu, but not all. For example, in xfce4-terminal, letter A of "Affichage" and its menu content as well as "Aide" is affected. Opening "Affichage" menu does not fix anything. Opening "Aide" menu fixes the "A" of "Aide". Changing window size reactivates the bug on "A" or "Aide". See video 2016y02m18d_16h14m25s_0100Z_glyph-redrawn- bug.mp4 . * text under icons on desktop is affected, but shadows are not. See 2016y02m16d_21h32m11s_0100Z_x_bug_reenabling_antialias_reactivates_problem_shadow_unaffected.png # Affected applications Affected applications include: * xfce whisker menu, * xfce4-terminal (nealy all screenshots) * firefox (see 2016y02m17d_18h08m27s_0100Z_x_bug_glyph_firefox_gnome_org.png 2016y02m16d_21h32m11s_0100Z_x_bug_reenabling_antialias_reactivates_problem_shadow_unaffected.png ), * thunderbird (see 2016y02m16d_21h28m35s_0100Z_x_bug_affects_thunderbird_terminal.png ), * emacs (see 2016y02m10d_18h41m49s_0100Z_wow_screen_flickers_and_most_glyphs_wrong_00.png and subsequent ), * superswitcher ( a gtk/gdk app) * *NOT* affected: xterm, xmessage. Perhaps only gtk/gdk/pango/cairo apps are affected. # Additional information This looks like a cache corruption somewhere. On IRC #pango, someone suggested a bug in Intel driver. Running `xfce4-appearance-settings` and there changing any of: * antialiasing enable/disable, * hinting strength, * subpixel alignment * or dpi immediately cures the bug (see 2016y02m16d_21h31m52s_0100Z_x_bug_disabling_antialias_immediately_cures_problem.png ) Setting back the exact same parameters immediately reactivates the bug (see 2016y02m16d_21h32m11s_0100Z_x_bug_reenabling_antialias_reactivates_problem_shadow_unaffected.png). It is believed that keeping any new settings for a while will have the bug reoccur. It is not like bug 1536751. That one affects rendering quality of *all* glyphs, at all times, depending on dpi. This is not the case here: *some* glyphs (randomly chosen) are drawn corrupted (replaced by garbage or absent), not always. # Other 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu export LC_ALL=C ; lsb_release -rd Description: Ubuntu Xenial Xerus (development branch) Release: 16.04 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center apt-cache policy xorg xorg: Installed: 1:7.7+13ubuntu1 Candidate: 1:7.7+13ubuntu1 Version table: *** 1:7.7+13ubuntu1 500 500 http://fr.archive.ubuntu.com/ubuntu xenial/main amd64 Packages 100 /var/lib/dpkg/status 3) What you expected to happen 4) What happened instead Written above. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-4.19-generic 4.4.1 Uname: Linux 4.4.0-4-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 CurrentDesktop: XFCE Date: Thu Feb 18 16:03:55 2016 InstallationDate: Installed on 2016-02-03 (14 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160203) SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.20-0ubuntu3
[Touch-packages] [Bug 1547077] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1547077/+attachment/4585282/+files/CurrentDmesg.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.launchpad.net/bugs/1547077 Title: Some glyphs drawn consistently wrong, bug comes and go Status in xorg package in Ubuntu: Incomplete Bug description: # Summary * Some glyphs badly drawn at some moments. * When happens, same glyph drawn on various windows shows same corruption. * Problem comes and go. # Context Laptop, using Intel driver. Expected: all glyphs rendered correctly. Observed: some glyphs not rendered correctly * reproducible: sometimes, eventually. Problem comes and go, severity varies from one glyph (see 2016y02m17d_18h08m27s_0100Z_x_bug_glyph_firefox_gnome_org.png ) to all text on screen fully unreadable (see 2016y02m10d_18h42m18s_0100Z_wow_screen_flickers_and_most_glyphs_wrong_01.png ) * *some* glyphs are affected. For example, letter 'a' of a certain size will be replaced by colored garbage at many places where it appears (see 2016y02m18d_16h05m35s_0100Z_same_corruption_on_different_windows.png ), but other 'a' with different size, italic, bold, etc will be unaffected. * in some applications (e.g. xfce whisker menu), some glyphs are rendered correctly or not depending on the direction of mouse hovering. See video 2016y02m16d_21h41m14s_0100Z_whisker_menu_missing_glyphs.mp4 . * in menu of gtk application, some glyphs are "fixed" by opening the menu, but not all. For example, in xfce4-terminal, letter A of "Affichage" and its menu content as well as "Aide" is affected. Opening "Affichage" menu does not fix anything. Opening "Aide" menu fixes the "A" of "Aide". Changing window size reactivates the bug on "A" or "Aide". See video 2016y02m18d_16h14m25s_0100Z_glyph-redrawn- bug.mp4 . * text under icons on desktop is affected, but shadows are not. See 2016y02m16d_21h32m11s_0100Z_x_bug_reenabling_antialias_reactivates_problem_shadow_unaffected.png # Affected applications Affected applications include: * xfce whisker menu, * xfce4-terminal (nealy all screenshots) * firefox (see 2016y02m17d_18h08m27s_0100Z_x_bug_glyph_firefox_gnome_org.png 2016y02m16d_21h32m11s_0100Z_x_bug_reenabling_antialias_reactivates_problem_shadow_unaffected.png ), * thunderbird (see 2016y02m16d_21h28m35s_0100Z_x_bug_affects_thunderbird_terminal.png ), * emacs (see 2016y02m10d_18h41m49s_0100Z_wow_screen_flickers_and_most_glyphs_wrong_00.png and subsequent ), * superswitcher ( a gtk/gdk app) * *NOT* affected: xterm, xmessage. Perhaps only gtk/gdk/pango/cairo apps are affected. # Additional information This looks like a cache corruption somewhere. On IRC #pango, someone suggested a bug in Intel driver. Running `xfce4-appearance-settings` and there changing any of: * antialiasing enable/disable, * hinting strength, * subpixel alignment * or dpi immediately cures the bug (see 2016y02m16d_21h31m52s_0100Z_x_bug_disabling_antialias_immediately_cures_problem.png ) Setting back the exact same parameters immediately reactivates the bug (see 2016y02m16d_21h32m11s_0100Z_x_bug_reenabling_antialias_reactivates_problem_shadow_unaffected.png). It is believed that keeping any new settings for a while will have the bug reoccur. It is not like bug 1536751. That one affects rendering quality of *all* glyphs, at all times, depending on dpi. This is not the case here: *some* glyphs (randomly chosen) are drawn corrupted (replaced by garbage or absent), not always. # Other 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu export LC_ALL=C ; lsb_release -rd Description: Ubuntu Xenial Xerus (development branch) Release: 16.04 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center apt-cache policy xorg xorg: Installed: 1:7.7+13ubuntu1 Candidate: 1:7.7+13ubuntu1 Version table: *** 1:7.7+13ubuntu1 500 500 http://fr.archive.ubuntu.com/ubuntu xenial/main amd64 Packages 100 /var/lib/dpkg/status 3) What you expected to happen 4) What happened instead Written above. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-4.19-generic 4.4.1 Uname: Linux 4.4.0-4-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 CurrentDesktop: XFCE Date: Thu Feb 18 16:03:55 2016 InstallationDate: Installed on 2016-02-03 (14 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160203) SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.20-0ubuntu3
[Touch-packages] [Bug 1547077] Re: Some glyphs drawn consistently wrong, bug comes and go
** Description changed: # Summary * Some glyphs badly drawn at some moments. * When happens, same glyph drawn on various windows shows same corruption. * Problem comes and go. # Context Laptop, using Intel driver. Expected: all glyphs rendered correctly. Observed: some glyphs not rendered correctly - * sometimes (problem comes and go, severity varies) - * *some* glyphs are affected. For example, letter 'a' of a certain size will be replaced by colored garbage at many places where it appears (see 2016y02m18d_16h05m35s_0100Z_same_corruption_on_different_windows.png ), but other 'a' with different size, italic, bold, etc will be unaffected - * in some applications (e.g. xfce whisker menu), some glyphs are rendered correctly or not depending on the direction of mouse hovering. See video 2016y02m16d_21h41m14s_0100Z_whisker_menu_missing_glyphs.mp4 . - * in menu of gtk application, some glyphs are "fixed" by opening the menu, but not all. For example, in xfce4-terminal, letter A of "Affichage" and its menu content as well as "Aide" is affected. Opening "Affichage" menu does not fix anything. Opening "Aide" menu fixes the "A" of "Aide". Changing window size reactivates the bug on "A" or "Aide". See video 2016y02m18d_16h14m25s_0100Z_glyph-redrawn-bug.mp4 . - * text under icons on desktop is affected, but shadows are not. See 2016y02m16d_21h32m11s_0100Z_x_bug_reenabling_antialias_reactivates_problem_shadow_unaffected.png + + * reproducible: sometimes, eventually. Problem comes and go, severity + varies from one glyph (see + 2016y02m17d_18h08m27s_0100Z_x_bug_glyph_firefox_gnome_org.png ) to all + text on screen fully unreadable (see + 2016y02m10d_18h42m18s_0100Z_wow_screen_flickers_and_most_glyphs_wrong_01.png + ) + + * *some* glyphs are affected. For example, letter 'a' of a certain size + will be replaced by colored garbage at many places where it appears (see + 2016y02m18d_16h05m35s_0100Z_same_corruption_on_different_windows.png ), + but other 'a' with different size, italic, bold, etc will be unaffected. + + * in some applications (e.g. xfce whisker menu), some glyphs are + rendered correctly or not depending on the direction of mouse hovering. + See video 2016y02m16d_21h41m14s_0100Z_whisker_menu_missing_glyphs.mp4 . + + * in menu of gtk application, some glyphs are "fixed" by opening the + menu, but not all. For example, in xfce4-terminal, letter A of + "Affichage" and its menu content as well as "Aide" is affected. Opening + "Affichage" menu does not fix anything. Opening "Aide" menu fixes the + "A" of "Aide". Changing window size reactivates the bug on "A" or + "Aide". See video 2016y02m18d_16h14m25s_0100Z_glyph-redrawn-bug.mp4 . + + * text under icons on desktop is affected, but shadows are not. See + 2016y02m16d_21h32m11s_0100Z_x_bug_reenabling_antialias_reactivates_problem_shadow_unaffected.png # Affected applications Affected applications include: + * xfce whisker menu, - * xfce4-terminal, - * firefox (see 2016y02m17d_18h08m27s_0100Z_x_bug_glyph_firefox_gnome_org.png 2016y02m16d_21h32m11s_0100Z_x_bug_reenabling_antialias_reactivates_problem_shadow_unaffected.png ), - * thunderbird (see 2016y02m16d_21h28m35s_0100Z_x_bug_affects_thunderbird_terminal.png ), + + * xfce4-terminal (nealy all screenshots) + + * firefox (see + 2016y02m17d_18h08m27s_0100Z_x_bug_glyph_firefox_gnome_org.png + 2016y02m16d_21h32m11s_0100Z_x_bug_reenabling_antialias_reactivates_problem_shadow_unaffected.png + ), + + * thunderbird (see + 2016y02m16d_21h28m35s_0100Z_x_bug_affects_thunderbird_terminal.png ), + * emacs (see 2016y02m10d_18h41m49s_0100Z_wow_screen_flickers_and_most_glyphs_wrong_00.png and subsequent ), * superswitcher ( a gtk/gdk app) - * *NOT* affected: xterm, xmessage. Perhaps only gtk/gdk/pango/cairo are - affected. + * *NOT* affected: xterm, xmessage. Perhaps only gtk/gdk/pango/cairo apps + are affected. # Additional information This looks like a cache corruption somewhere. - On IRC #ubuntu+1, someone suggested a bug in Intel driver. + On IRC #pango, someone suggested a bug in Intel driver. Running `xfce4-appearance-settings` and there changing any of: * antialiasing enable/disable, * hinting strength, * subpixel alignment * or dpi immediately cures the bug (see 2016y02m16d_21h31m52s_0100Z_x_bug_disabling_antialias_immediately_cures_problem.png ) Setting back the exact same parameters immediately reactivates the bug (see 2016y02m16d_21h32m11s_0100Z_x_bug_reenabling_antialias_reactivates_problem_shadow_unaffected.png). It is believed that keeping any new settings for a while will have the bug reoccur. - - It is not like bug 1536751. That one affects rendering quality of *all* glyphs, at all times, depending on dpi. This is not the case here: *some* glyphs (randomly chosen) are drawn corrupted (replaced by garbage or absent), not always. - + It is not like bug 1536751. That one
[Touch-packages] [Bug 1547077] Re: Some glyphs drawn consistently wrong, bug comes and go
Oops, it looks like putting a short description obscures the attachment names. You can hover the links with your mouse to see file names. I'm willing to run other apps, but bug only appears after a while. Logging out then in cures the bug. The bug sometimes disappears on its own (it has currently disappeared). Observed after closing a number of windows, but don't know if actually correlated. -- 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/1547077 Title: Some glyphs drawn consistently wrong, bug comes and go Status in xorg package in Ubuntu: New Bug description: # Summary * Some glyphs badly drawn at some moments. * When happens, same glyph drawn on various windows shows same corruption. * Problem comes and go. # Context Laptop, using Intel driver. Expected: all glyphs rendered correctly. Observed: some glyphs not rendered correctly * sometimes (problem comes and go, severity varies) * *some* glyphs are affected. For example, letter 'a' of a certain size will be replaced by colored garbage at many places where it appears (see 2016y02m18d_16h05m35s_0100Z_same_corruption_on_different_windows.png ), but other 'a' with different size, italic, bold, etc will be unaffected * in some applications (e.g. xfce whisker menu), some glyphs are rendered correctly or not depending on the direction of mouse hovering. See video 2016y02m16d_21h41m14s_0100Z_whisker_menu_missing_glyphs.mp4 . * in menu of gtk application, some glyphs are "fixed" by opening the menu, but not all. For example, in xfce4-terminal, letter A of "Affichage" and its menu content as well as "Aide" is affected. Opening "Affichage" menu does not fix anything. Opening "Aide" menu fixes the "A" of "Aide". Changing window size reactivates the bug on "A" or "Aide". See video 2016y02m18d_16h14m25s_0100Z_glyph-redrawn-bug.mp4 . * text under icons on desktop is affected, but shadows are not. See 2016y02m16d_21h32m11s_0100Z_x_bug_reenabling_antialias_reactivates_problem_shadow_unaffected.png # Affected applications Affected applications include: * xfce whisker menu, * xfce4-terminal, * firefox (see 2016y02m17d_18h08m27s_0100Z_x_bug_glyph_firefox_gnome_org.png 2016y02m16d_21h32m11s_0100Z_x_bug_reenabling_antialias_reactivates_problem_shadow_unaffected.png ), * thunderbird (see 2016y02m16d_21h28m35s_0100Z_x_bug_affects_thunderbird_terminal.png ), * emacs (see 2016y02m10d_18h41m49s_0100Z_wow_screen_flickers_and_most_glyphs_wrong_00.png and subsequent ), * superswitcher ( a gtk/gdk app) * *NOT* affected: xterm, xmessage. Perhaps only gtk/gdk/pango/cairo are affected. # Additional information This looks like a cache corruption somewhere. On IRC #ubuntu+1, someone suggested a bug in Intel driver. Running `xfce4-appearance-settings` and there changing any of: * antialiasing enable/disable, * hinting strength, * subpixel alignment * or dpi immediately cures the bug (see 2016y02m16d_21h31m52s_0100Z_x_bug_disabling_antialias_immediately_cures_problem.png ) Setting back the exact same parameters immediately reactivates the bug (see 2016y02m16d_21h32m11s_0100Z_x_bug_reenabling_antialias_reactivates_problem_shadow_unaffected.png). It is believed that keeping any new settings for a while will have the bug reoccur. It is not like bug 1536751. That one affects rendering quality of *all* glyphs, at all times, depending on dpi. This is not the case here: *some* glyphs (randomly chosen) are drawn corrupted (replaced by garbage or absent), not always. # Other 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu export LC_ALL=C ; lsb_release -rd Description: Ubuntu Xenial Xerus (development branch) Release: 16.04 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center apt-cache policy xorg xorg: Installed: 1:7.7+13ubuntu1 Candidate: 1:7.7+13ubuntu1 Version table: *** 1:7.7+13ubuntu1 500 500 http://fr.archive.ubuntu.com/ubuntu xenial/main amd64 Packages 100 /var/lib/dpkg/status 3) What you expected to happen 4) What happened instead Written above. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-4.19-generic 4.4.1 Uname: Linux 4.4.0-4-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 CurrentDesktop: XFCE Date: Thu Feb 18 16:03:55 2016 InstallationDate: Installed on 2016-02-03 (14 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160203) SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to:
[Touch-packages] [Bug 1547077] Re: Some glyphs drawn consistently wrong, bug comes and go
** Attachment added: "see main text" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1547077/+attachment/4574630/+files/2016y02m18d_16h14m25s_0100Z_glyph-redrawn-bug.mp4 -- 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/1547077 Title: Some glyphs drawn consistently wrong, bug comes and go Status in xorg package in Ubuntu: New Bug description: # Summary * Some glyphs badly drawn at some moments. * When happens, same glyph drawn on various windows shows same corruption. * Problem comes and go. # Context Laptop, using Intel driver. Expected: all glyphs rendered correctly. Observed: some glyphs not rendered correctly * sometimes (problem comes and go, severity varies) * *some* glyphs are affected. For example, letter 'a' of a certain size will be replaced by colored garbage at many places where it appears (see 2016y02m18d_16h05m35s_0100Z_same_corruption_on_different_windows.png ), but other 'a' with different size, italic, bold, etc will be unaffected * in some applications (e.g. xfce whisker menu), some glyphs are rendered correctly or not depending on the direction of mouse hovering. See video 2016y02m16d_21h41m14s_0100Z_whisker_menu_missing_glyphs.mp4 . * in menu of gtk application, some glyphs are "fixed" by opening the menu, but not all. For example, in xfce4-terminal, letter A of "Affichage" and its menu content as well as "Aide" is affected. Opening "Affichage" menu does not fix anything. Opening "Aide" menu fixes the "A" of "Aide". Changing window size reactivates the bug on "A" or "Aide". See video 2016y02m18d_16h14m25s_0100Z_glyph-redrawn-bug.mp4 . * text under icons on desktop is affected, but shadows are not. See 2016y02m16d_21h32m11s_0100Z_x_bug_reenabling_antialias_reactivates_problem_shadow_unaffected.png # Affected applications Affected applications include: * xfce whisker menu, * xfce4-terminal, * firefox (see 2016y02m17d_18h08m27s_0100Z_x_bug_glyph_firefox_gnome_org.png 2016y02m16d_21h32m11s_0100Z_x_bug_reenabling_antialias_reactivates_problem_shadow_unaffected.png ), * thunderbird (see 2016y02m16d_21h28m35s_0100Z_x_bug_affects_thunderbird_terminal.png ), * emacs (see 2016y02m10d_18h41m49s_0100Z_wow_screen_flickers_and_most_glyphs_wrong_00.png and subsequent ), * superswitcher ( a gtk/gdk app) * *NOT* affected: xterm, xmessage. Perhaps only gtk/gdk/pango/cairo are affected. # Additional information This looks like a cache corruption somewhere. On IRC #ubuntu+1, someone suggested a bug in Intel driver. Running `xfce4-appearance-settings` and there changing any of: * antialiasing enable/disable, * hinting strength, * subpixel alignment * or dpi immediately cures the bug (see 2016y02m16d_21h31m52s_0100Z_x_bug_disabling_antialias_immediately_cures_problem.png ) Setting back the exact same parameters immediately reactivates the bug (see 2016y02m16d_21h32m11s_0100Z_x_bug_reenabling_antialias_reactivates_problem_shadow_unaffected.png). It is believed that keeping any new settings for a while will have the bug reoccur. It is not like bug 1536751. That one affects rendering quality of *all* glyphs, at all times, depending on dpi. This is not the case here: *some* glyphs (randomly chosen) are drawn corrupted (replaced by garbage or absent), not always. # Other 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu export LC_ALL=C ; lsb_release -rd Description: Ubuntu Xenial Xerus (development branch) Release: 16.04 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center apt-cache policy xorg xorg: Installed: 1:7.7+13ubuntu1 Candidate: 1:7.7+13ubuntu1 Version table: *** 1:7.7+13ubuntu1 500 500 http://fr.archive.ubuntu.com/ubuntu xenial/main amd64 Packages 100 /var/lib/dpkg/status 3) What you expected to happen 4) What happened instead Written above. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-4.19-generic 4.4.1 Uname: Linux 4.4.0-4-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 CurrentDesktop: XFCE Date: Thu Feb 18 16:03:55 2016 InstallationDate: Installed on 2016-02-03 (14 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160203) SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1547077/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help :
[Touch-packages] [Bug 1547077] Re: Some glyphs drawn consistently wrong, bug comes and go
** Attachment added: "see main text" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1547077/+attachment/4574628/+files/2016y02m16d_21h28m35s_0100Z_x_bug_affects_thunderbird_terminal.png -- 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/1547077 Title: Some glyphs drawn consistently wrong, bug comes and go Status in xorg package in Ubuntu: New Bug description: # Summary * Some glyphs badly drawn at some moments. * When happens, same glyph drawn on various windows shows same corruption. * Problem comes and go. # Context Laptop, using Intel driver. Expected: all glyphs rendered correctly. Observed: some glyphs not rendered correctly * sometimes (problem comes and go, severity varies) * *some* glyphs are affected. For example, letter 'a' of a certain size will be replaced by colored garbage at many places where it appears (see 2016y02m18d_16h05m35s_0100Z_same_corruption_on_different_windows.png ), but other 'a' with different size, italic, bold, etc will be unaffected * in some applications (e.g. xfce whisker menu), some glyphs are rendered correctly or not depending on the direction of mouse hovering. See video 2016y02m16d_21h41m14s_0100Z_whisker_menu_missing_glyphs.mp4 . * in menu of gtk application, some glyphs are "fixed" by opening the menu, but not all. For example, in xfce4-terminal, letter A of "Affichage" and its menu content as well as "Aide" is affected. Opening "Affichage" menu does not fix anything. Opening "Aide" menu fixes the "A" of "Aide". Changing window size reactivates the bug on "A" or "Aide". See video 2016y02m18d_16h14m25s_0100Z_glyph-redrawn-bug.mp4 . * text under icons on desktop is affected, but shadows are not. See 2016y02m16d_21h32m11s_0100Z_x_bug_reenabling_antialias_reactivates_problem_shadow_unaffected.png # Affected applications Affected applications include: * xfce whisker menu, * xfce4-terminal, * firefox (see 2016y02m17d_18h08m27s_0100Z_x_bug_glyph_firefox_gnome_org.png 2016y02m16d_21h32m11s_0100Z_x_bug_reenabling_antialias_reactivates_problem_shadow_unaffected.png ), * thunderbird (see 2016y02m16d_21h28m35s_0100Z_x_bug_affects_thunderbird_terminal.png ), * emacs (see 2016y02m10d_18h41m49s_0100Z_wow_screen_flickers_and_most_glyphs_wrong_00.png and subsequent ), * superswitcher ( a gtk/gdk app) * *NOT* affected: xterm, xmessage. Perhaps only gtk/gdk/pango/cairo are affected. # Additional information This looks like a cache corruption somewhere. On IRC #ubuntu+1, someone suggested a bug in Intel driver. Running `xfce4-appearance-settings` and there changing any of: * antialiasing enable/disable, * hinting strength, * subpixel alignment * or dpi immediately cures the bug (see 2016y02m16d_21h31m52s_0100Z_x_bug_disabling_antialias_immediately_cures_problem.png ) Setting back the exact same parameters immediately reactivates the bug (see 2016y02m16d_21h32m11s_0100Z_x_bug_reenabling_antialias_reactivates_problem_shadow_unaffected.png). It is believed that keeping any new settings for a while will have the bug reoccur. It is not like bug 1536751. That one affects rendering quality of *all* glyphs, at all times, depending on dpi. This is not the case here: *some* glyphs (randomly chosen) are drawn corrupted (replaced by garbage or absent), not always. # Other 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu export LC_ALL=C ; lsb_release -rd Description: Ubuntu Xenial Xerus (development branch) Release: 16.04 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center apt-cache policy xorg xorg: Installed: 1:7.7+13ubuntu1 Candidate: 1:7.7+13ubuntu1 Version table: *** 1:7.7+13ubuntu1 500 500 http://fr.archive.ubuntu.com/ubuntu xenial/main amd64 Packages 100 /var/lib/dpkg/status 3) What you expected to happen 4) What happened instead Written above. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-4.19-generic 4.4.1 Uname: Linux 4.4.0-4-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 CurrentDesktop: XFCE Date: Thu Feb 18 16:03:55 2016 InstallationDate: Installed on 2016-02-03 (14 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160203) SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1547077/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help :
[Touch-packages] [Bug 1547077] Re: Some glyphs drawn consistently wrong, bug comes and go
** Attachment added: "see main text" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1547077/+attachment/4574629/+files/2016y02m17d_18h08m27s_0100Z_x_bug_glyph_firefox_gnome_org.png -- 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/1547077 Title: Some glyphs drawn consistently wrong, bug comes and go Status in xorg package in Ubuntu: New Bug description: # Summary * Some glyphs badly drawn at some moments. * When happens, same glyph drawn on various windows shows same corruption. * Problem comes and go. # Context Laptop, using Intel driver. Expected: all glyphs rendered correctly. Observed: some glyphs not rendered correctly * sometimes (problem comes and go, severity varies) * *some* glyphs are affected. For example, letter 'a' of a certain size will be replaced by colored garbage at many places where it appears (see 2016y02m18d_16h05m35s_0100Z_same_corruption_on_different_windows.png ), but other 'a' with different size, italic, bold, etc will be unaffected * in some applications (e.g. xfce whisker menu), some glyphs are rendered correctly or not depending on the direction of mouse hovering. See video 2016y02m16d_21h41m14s_0100Z_whisker_menu_missing_glyphs.mp4 . * in menu of gtk application, some glyphs are "fixed" by opening the menu, but not all. For example, in xfce4-terminal, letter A of "Affichage" and its menu content as well as "Aide" is affected. Opening "Affichage" menu does not fix anything. Opening "Aide" menu fixes the "A" of "Aide". Changing window size reactivates the bug on "A" or "Aide". See video 2016y02m18d_16h14m25s_0100Z_glyph-redrawn-bug.mp4 . * text under icons on desktop is affected, but shadows are not. See 2016y02m16d_21h32m11s_0100Z_x_bug_reenabling_antialias_reactivates_problem_shadow_unaffected.png # Affected applications Affected applications include: * xfce whisker menu, * xfce4-terminal, * firefox (see 2016y02m17d_18h08m27s_0100Z_x_bug_glyph_firefox_gnome_org.png 2016y02m16d_21h32m11s_0100Z_x_bug_reenabling_antialias_reactivates_problem_shadow_unaffected.png ), * thunderbird (see 2016y02m16d_21h28m35s_0100Z_x_bug_affects_thunderbird_terminal.png ), * emacs (see 2016y02m10d_18h41m49s_0100Z_wow_screen_flickers_and_most_glyphs_wrong_00.png and subsequent ), * superswitcher ( a gtk/gdk app) * *NOT* affected: xterm, xmessage. Perhaps only gtk/gdk/pango/cairo are affected. # Additional information This looks like a cache corruption somewhere. On IRC #ubuntu+1, someone suggested a bug in Intel driver. Running `xfce4-appearance-settings` and there changing any of: * antialiasing enable/disable, * hinting strength, * subpixel alignment * or dpi immediately cures the bug (see 2016y02m16d_21h31m52s_0100Z_x_bug_disabling_antialias_immediately_cures_problem.png ) Setting back the exact same parameters immediately reactivates the bug (see 2016y02m16d_21h32m11s_0100Z_x_bug_reenabling_antialias_reactivates_problem_shadow_unaffected.png). It is believed that keeping any new settings for a while will have the bug reoccur. It is not like bug 1536751. That one affects rendering quality of *all* glyphs, at all times, depending on dpi. This is not the case here: *some* glyphs (randomly chosen) are drawn corrupted (replaced by garbage or absent), not always. # Other 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu export LC_ALL=C ; lsb_release -rd Description: Ubuntu Xenial Xerus (development branch) Release: 16.04 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center apt-cache policy xorg xorg: Installed: 1:7.7+13ubuntu1 Candidate: 1:7.7+13ubuntu1 Version table: *** 1:7.7+13ubuntu1 500 500 http://fr.archive.ubuntu.com/ubuntu xenial/main amd64 Packages 100 /var/lib/dpkg/status 3) What you expected to happen 4) What happened instead Written above. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-4.19-generic 4.4.1 Uname: Linux 4.4.0-4-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 CurrentDesktop: XFCE Date: Thu Feb 18 16:03:55 2016 InstallationDate: Installed on 2016-02-03 (14 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160203) SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1547077/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help :
[Touch-packages] [Bug 1547077] Re: Some glyphs drawn consistently wrong, bug comes and go
** Attachment added: "see main text" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1547077/+attachment/4574625/+files/2016y02m16d_21h41m14s_0100Z_whisker_menu_missing_glyphs.mp4 -- 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/1547077 Title: Some glyphs drawn consistently wrong, bug comes and go Status in xorg package in Ubuntu: New Bug description: # Summary * Some glyphs badly drawn at some moments. * When happens, same glyph drawn on various windows shows same corruption. * Problem comes and go. # Context Laptop, using Intel driver. Expected: all glyphs rendered correctly. Observed: some glyphs not rendered correctly * sometimes (problem comes and go, severity varies) * *some* glyphs are affected. For example, letter 'a' of a certain size will be replaced by colored garbage at many places where it appears (see 2016y02m18d_16h05m35s_0100Z_same_corruption_on_different_windows.png ), but other 'a' with different size, italic, bold, etc will be unaffected * in some applications (e.g. xfce whisker menu), some glyphs are rendered correctly or not depending on the direction of mouse hovering. See video 2016y02m16d_21h41m14s_0100Z_whisker_menu_missing_glyphs.mp4 . * in menu of gtk application, some glyphs are "fixed" by opening the menu, but not all. For example, in xfce4-terminal, letter A of "Affichage" and its menu content as well as "Aide" is affected. Opening "Affichage" menu does not fix anything. Opening "Aide" menu fixes the "A" of "Aide". Changing window size reactivates the bug on "A" or "Aide". See video 2016y02m18d_16h14m25s_0100Z_glyph-redrawn-bug.mp4 . * text under icons on desktop is affected, but shadows are not. See 2016y02m16d_21h32m11s_0100Z_x_bug_reenabling_antialias_reactivates_problem_shadow_unaffected.png # Affected applications Affected applications include: * xfce whisker menu, * xfce4-terminal, * firefox (see 2016y02m17d_18h08m27s_0100Z_x_bug_glyph_firefox_gnome_org.png 2016y02m16d_21h32m11s_0100Z_x_bug_reenabling_antialias_reactivates_problem_shadow_unaffected.png ), * thunderbird (see 2016y02m16d_21h28m35s_0100Z_x_bug_affects_thunderbird_terminal.png ), * emacs (see 2016y02m10d_18h41m49s_0100Z_wow_screen_flickers_and_most_glyphs_wrong_00.png and subsequent ), * superswitcher ( a gtk/gdk app) * *NOT* affected: xterm, xmessage. Perhaps only gtk/gdk/pango/cairo are affected. # Additional information This looks like a cache corruption somewhere. On IRC #ubuntu+1, someone suggested a bug in Intel driver. Running `xfce4-appearance-settings` and there changing any of: * antialiasing enable/disable, * hinting strength, * subpixel alignment * or dpi immediately cures the bug (see 2016y02m16d_21h31m52s_0100Z_x_bug_disabling_antialias_immediately_cures_problem.png ) Setting back the exact same parameters immediately reactivates the bug (see 2016y02m16d_21h32m11s_0100Z_x_bug_reenabling_antialias_reactivates_problem_shadow_unaffected.png). It is believed that keeping any new settings for a while will have the bug reoccur. It is not like bug 1536751. That one affects rendering quality of *all* glyphs, at all times, depending on dpi. This is not the case here: *some* glyphs (randomly chosen) are drawn corrupted (replaced by garbage or absent), not always. # Other 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu export LC_ALL=C ; lsb_release -rd Description: Ubuntu Xenial Xerus (development branch) Release: 16.04 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center apt-cache policy xorg xorg: Installed: 1:7.7+13ubuntu1 Candidate: 1:7.7+13ubuntu1 Version table: *** 1:7.7+13ubuntu1 500 500 http://fr.archive.ubuntu.com/ubuntu xenial/main amd64 Packages 100 /var/lib/dpkg/status 3) What you expected to happen 4) What happened instead Written above. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-4.19-generic 4.4.1 Uname: Linux 4.4.0-4-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 CurrentDesktop: XFCE Date: Thu Feb 18 16:03:55 2016 InstallationDate: Installed on 2016-02-03 (14 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160203) SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1547077/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help :
[Touch-packages] [Bug 1547077] Re: Some glyphs drawn consistently wrong, bug comes and go
** Attachment added: "see main text" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1547077/+attachment/4574627/+files/2016y02m15d_13h16m33s_0100Z_bug_affects_superswitcher_terminal_and_more.png -- 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/1547077 Title: Some glyphs drawn consistently wrong, bug comes and go Status in xorg package in Ubuntu: New Bug description: # Summary * Some glyphs badly drawn at some moments. * When happens, same glyph drawn on various windows shows same corruption. * Problem comes and go. # Context Laptop, using Intel driver. Expected: all glyphs rendered correctly. Observed: some glyphs not rendered correctly * sometimes (problem comes and go, severity varies) * *some* glyphs are affected. For example, letter 'a' of a certain size will be replaced by colored garbage at many places where it appears (see 2016y02m18d_16h05m35s_0100Z_same_corruption_on_different_windows.png ), but other 'a' with different size, italic, bold, etc will be unaffected * in some applications (e.g. xfce whisker menu), some glyphs are rendered correctly or not depending on the direction of mouse hovering. See video 2016y02m16d_21h41m14s_0100Z_whisker_menu_missing_glyphs.mp4 . * in menu of gtk application, some glyphs are "fixed" by opening the menu, but not all. For example, in xfce4-terminal, letter A of "Affichage" and its menu content as well as "Aide" is affected. Opening "Affichage" menu does not fix anything. Opening "Aide" menu fixes the "A" of "Aide". Changing window size reactivates the bug on "A" or "Aide". See video 2016y02m18d_16h14m25s_0100Z_glyph-redrawn-bug.mp4 . * text under icons on desktop is affected, but shadows are not. See 2016y02m16d_21h32m11s_0100Z_x_bug_reenabling_antialias_reactivates_problem_shadow_unaffected.png # Affected applications Affected applications include: * xfce whisker menu, * xfce4-terminal, * firefox (see 2016y02m17d_18h08m27s_0100Z_x_bug_glyph_firefox_gnome_org.png 2016y02m16d_21h32m11s_0100Z_x_bug_reenabling_antialias_reactivates_problem_shadow_unaffected.png ), * thunderbird (see 2016y02m16d_21h28m35s_0100Z_x_bug_affects_thunderbird_terminal.png ), * emacs (see 2016y02m10d_18h41m49s_0100Z_wow_screen_flickers_and_most_glyphs_wrong_00.png and subsequent ), * superswitcher ( a gtk/gdk app) * *NOT* affected: xterm, xmessage. Perhaps only gtk/gdk/pango/cairo are affected. # Additional information This looks like a cache corruption somewhere. On IRC #ubuntu+1, someone suggested a bug in Intel driver. Running `xfce4-appearance-settings` and there changing any of: * antialiasing enable/disable, * hinting strength, * subpixel alignment * or dpi immediately cures the bug (see 2016y02m16d_21h31m52s_0100Z_x_bug_disabling_antialias_immediately_cures_problem.png ) Setting back the exact same parameters immediately reactivates the bug (see 2016y02m16d_21h32m11s_0100Z_x_bug_reenabling_antialias_reactivates_problem_shadow_unaffected.png). It is believed that keeping any new settings for a while will have the bug reoccur. It is not like bug 1536751. That one affects rendering quality of *all* glyphs, at all times, depending on dpi. This is not the case here: *some* glyphs (randomly chosen) are drawn corrupted (replaced by garbage or absent), not always. # Other 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu export LC_ALL=C ; lsb_release -rd Description: Ubuntu Xenial Xerus (development branch) Release: 16.04 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center apt-cache policy xorg xorg: Installed: 1:7.7+13ubuntu1 Candidate: 1:7.7+13ubuntu1 Version table: *** 1:7.7+13ubuntu1 500 500 http://fr.archive.ubuntu.com/ubuntu xenial/main amd64 Packages 100 /var/lib/dpkg/status 3) What you expected to happen 4) What happened instead Written above. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-4.19-generic 4.4.1 Uname: Linux 4.4.0-4-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 CurrentDesktop: XFCE Date: Thu Feb 18 16:03:55 2016 InstallationDate: Installed on 2016-02-03 (14 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160203) SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1547077/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help :
[Touch-packages] [Bug 1547077] Re: Some glyphs drawn consistently wrong, bug comes and go
** Attachment added: "see main text" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1547077/+attachment/4574626/+files/2016y02m18d_16h05m35s_0100Z_same_corruption_on_different_windows.png -- 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/1547077 Title: Some glyphs drawn consistently wrong, bug comes and go Status in xorg package in Ubuntu: New Bug description: # Summary * Some glyphs badly drawn at some moments. * When happens, same glyph drawn on various windows shows same corruption. * Problem comes and go. # Context Laptop, using Intel driver. Expected: all glyphs rendered correctly. Observed: some glyphs not rendered correctly * sometimes (problem comes and go, severity varies) * *some* glyphs are affected. For example, letter 'a' of a certain size will be replaced by colored garbage at many places where it appears (see 2016y02m18d_16h05m35s_0100Z_same_corruption_on_different_windows.png ), but other 'a' with different size, italic, bold, etc will be unaffected * in some applications (e.g. xfce whisker menu), some glyphs are rendered correctly or not depending on the direction of mouse hovering. See video 2016y02m16d_21h41m14s_0100Z_whisker_menu_missing_glyphs.mp4 . * in menu of gtk application, some glyphs are "fixed" by opening the menu, but not all. For example, in xfce4-terminal, letter A of "Affichage" and its menu content as well as "Aide" is affected. Opening "Affichage" menu does not fix anything. Opening "Aide" menu fixes the "A" of "Aide". Changing window size reactivates the bug on "A" or "Aide". See video 2016y02m18d_16h14m25s_0100Z_glyph-redrawn-bug.mp4 . * text under icons on desktop is affected, but shadows are not. See 2016y02m16d_21h32m11s_0100Z_x_bug_reenabling_antialias_reactivates_problem_shadow_unaffected.png # Affected applications Affected applications include: * xfce whisker menu, * xfce4-terminal, * firefox (see 2016y02m17d_18h08m27s_0100Z_x_bug_glyph_firefox_gnome_org.png 2016y02m16d_21h32m11s_0100Z_x_bug_reenabling_antialias_reactivates_problem_shadow_unaffected.png ), * thunderbird (see 2016y02m16d_21h28m35s_0100Z_x_bug_affects_thunderbird_terminal.png ), * emacs (see 2016y02m10d_18h41m49s_0100Z_wow_screen_flickers_and_most_glyphs_wrong_00.png and subsequent ), * superswitcher ( a gtk/gdk app) * *NOT* affected: xterm, xmessage. Perhaps only gtk/gdk/pango/cairo are affected. # Additional information This looks like a cache corruption somewhere. On IRC #ubuntu+1, someone suggested a bug in Intel driver. Running `xfce4-appearance-settings` and there changing any of: * antialiasing enable/disable, * hinting strength, * subpixel alignment * or dpi immediately cures the bug (see 2016y02m16d_21h31m52s_0100Z_x_bug_disabling_antialias_immediately_cures_problem.png ) Setting back the exact same parameters immediately reactivates the bug (see 2016y02m16d_21h32m11s_0100Z_x_bug_reenabling_antialias_reactivates_problem_shadow_unaffected.png). It is believed that keeping any new settings for a while will have the bug reoccur. It is not like bug 1536751. That one affects rendering quality of *all* glyphs, at all times, depending on dpi. This is not the case here: *some* glyphs (randomly chosen) are drawn corrupted (replaced by garbage or absent), not always. # Other 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu export LC_ALL=C ; lsb_release -rd Description: Ubuntu Xenial Xerus (development branch) Release: 16.04 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center apt-cache policy xorg xorg: Installed: 1:7.7+13ubuntu1 Candidate: 1:7.7+13ubuntu1 Version table: *** 1:7.7+13ubuntu1 500 500 http://fr.archive.ubuntu.com/ubuntu xenial/main amd64 Packages 100 /var/lib/dpkg/status 3) What you expected to happen 4) What happened instead Written above. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-4.19-generic 4.4.1 Uname: Linux 4.4.0-4-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 CurrentDesktop: XFCE Date: Thu Feb 18 16:03:55 2016 InstallationDate: Installed on 2016-02-03 (14 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160203) SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1547077/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help :
[Touch-packages] [Bug 1547077] Re: Some glyphs drawn consistently wrong, bug comes and go
** Attachment added: "see main text" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1547077/+attachment/4574624/+files/2016y02m16d_21h32m11s_0100Z_x_bug_reenabling_antialias_reactivates_problem_shadow_unaffected.png -- 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/1547077 Title: Some glyphs drawn consistently wrong, bug comes and go Status in xorg package in Ubuntu: New Bug description: # Summary * Some glyphs badly drawn at some moments. * When happens, same glyph drawn on various windows shows same corruption. * Problem comes and go. # Context Laptop, using Intel driver. Expected: all glyphs rendered correctly. Observed: some glyphs not rendered correctly * sometimes (problem comes and go, severity varies) * *some* glyphs are affected. For example, letter 'a' of a certain size will be replaced by colored garbage at many places where it appears (see 2016y02m18d_16h05m35s_0100Z_same_corruption_on_different_windows.png ), but other 'a' with different size, italic, bold, etc will be unaffected * in some applications (e.g. xfce whisker menu), some glyphs are rendered correctly or not depending on the direction of mouse hovering. See video 2016y02m16d_21h41m14s_0100Z_whisker_menu_missing_glyphs.mp4 . * in menu of gtk application, some glyphs are "fixed" by opening the menu, but not all. For example, in xfce4-terminal, letter A of "Affichage" and its menu content as well as "Aide" is affected. Opening "Affichage" menu does not fix anything. Opening "Aide" menu fixes the "A" of "Aide". Changing window size reactivates the bug on "A" or "Aide". See video 2016y02m18d_16h14m25s_0100Z_glyph-redrawn-bug.mp4 . * text under icons on desktop is affected, but shadows are not. See 2016y02m16d_21h32m11s_0100Z_x_bug_reenabling_antialias_reactivates_problem_shadow_unaffected.png # Affected applications Affected applications include: * xfce whisker menu, * xfce4-terminal, * firefox (see 2016y02m17d_18h08m27s_0100Z_x_bug_glyph_firefox_gnome_org.png 2016y02m16d_21h32m11s_0100Z_x_bug_reenabling_antialias_reactivates_problem_shadow_unaffected.png ), * thunderbird (see 2016y02m16d_21h28m35s_0100Z_x_bug_affects_thunderbird_terminal.png ), * emacs (see 2016y02m10d_18h41m49s_0100Z_wow_screen_flickers_and_most_glyphs_wrong_00.png and subsequent ), * superswitcher ( a gtk/gdk app) * *NOT* affected: xterm, xmessage. Perhaps only gtk/gdk/pango/cairo are affected. # Additional information This looks like a cache corruption somewhere. On IRC #ubuntu+1, someone suggested a bug in Intel driver. Running `xfce4-appearance-settings` and there changing any of: * antialiasing enable/disable, * hinting strength, * subpixel alignment * or dpi immediately cures the bug (see 2016y02m16d_21h31m52s_0100Z_x_bug_disabling_antialias_immediately_cures_problem.png ) Setting back the exact same parameters immediately reactivates the bug (see 2016y02m16d_21h32m11s_0100Z_x_bug_reenabling_antialias_reactivates_problem_shadow_unaffected.png). It is believed that keeping any new settings for a while will have the bug reoccur. It is not like bug 1536751. That one affects rendering quality of *all* glyphs, at all times, depending on dpi. This is not the case here: *some* glyphs (randomly chosen) are drawn corrupted (replaced by garbage or absent), not always. # Other 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu export LC_ALL=C ; lsb_release -rd Description: Ubuntu Xenial Xerus (development branch) Release: 16.04 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center apt-cache policy xorg xorg: Installed: 1:7.7+13ubuntu1 Candidate: 1:7.7+13ubuntu1 Version table: *** 1:7.7+13ubuntu1 500 500 http://fr.archive.ubuntu.com/ubuntu xenial/main amd64 Packages 100 /var/lib/dpkg/status 3) What you expected to happen 4) What happened instead Written above. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-4.19-generic 4.4.1 Uname: Linux 4.4.0-4-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 CurrentDesktop: XFCE Date: Thu Feb 18 16:03:55 2016 InstallationDate: Installed on 2016-02-03 (14 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160203) SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1547077/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe :
[Touch-packages] [Bug 1547077] Re: Some glyphs drawn consistently wrong, bug comes and go
** Attachment added: "see main text" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1547077/+attachment/4574621/+files/2016y02m10d_18h42m34s_0100Z_wow_screen_flickers_and_most_glyphs_wrong_02.png -- 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/1547077 Title: Some glyphs drawn consistently wrong, bug comes and go Status in xorg package in Ubuntu: New Bug description: # Summary * Some glyphs badly drawn at some moments. * When happens, same glyph drawn on various windows shows same corruption. * Problem comes and go. # Context Laptop, using Intel driver. Expected: all glyphs rendered correctly. Observed: some glyphs not rendered correctly * sometimes (problem comes and go, severity varies) * *some* glyphs are affected. For example, letter 'a' of a certain size will be replaced by colored garbage at many places where it appears (see 2016y02m18d_16h05m35s_0100Z_same_corruption_on_different_windows.png ), but other 'a' with different size, italic, bold, etc will be unaffected * in some applications (e.g. xfce whisker menu), some glyphs are rendered correctly or not depending on the direction of mouse hovering. See video 2016y02m16d_21h41m14s_0100Z_whisker_menu_missing_glyphs.mp4 . * in menu of gtk application, some glyphs are "fixed" by opening the menu, but not all. For example, in xfce4-terminal, letter A of "Affichage" and its menu content as well as "Aide" is affected. Opening "Affichage" menu does not fix anything. Opening "Aide" menu fixes the "A" of "Aide". Changing window size reactivates the bug on "A" or "Aide". See video 2016y02m18d_16h14m25s_0100Z_glyph-redrawn-bug.mp4 . * text under icons on desktop is affected, but shadows are not. See 2016y02m16d_21h32m11s_0100Z_x_bug_reenabling_antialias_reactivates_problem_shadow_unaffected.png # Affected applications Affected applications include: * xfce whisker menu, * xfce4-terminal, * firefox (see 2016y02m17d_18h08m27s_0100Z_x_bug_glyph_firefox_gnome_org.png 2016y02m16d_21h32m11s_0100Z_x_bug_reenabling_antialias_reactivates_problem_shadow_unaffected.png ), * thunderbird (see 2016y02m16d_21h28m35s_0100Z_x_bug_affects_thunderbird_terminal.png ), * emacs (see 2016y02m10d_18h41m49s_0100Z_wow_screen_flickers_and_most_glyphs_wrong_00.png and subsequent ), * superswitcher ( a gtk/gdk app) * *NOT* affected: xterm, xmessage. Perhaps only gtk/gdk/pango/cairo are affected. # Additional information This looks like a cache corruption somewhere. On IRC #ubuntu+1, someone suggested a bug in Intel driver. Running `xfce4-appearance-settings` and there changing any of: * antialiasing enable/disable, * hinting strength, * subpixel alignment * or dpi immediately cures the bug (see 2016y02m16d_21h31m52s_0100Z_x_bug_disabling_antialias_immediately_cures_problem.png ) Setting back the exact same parameters immediately reactivates the bug (see 2016y02m16d_21h32m11s_0100Z_x_bug_reenabling_antialias_reactivates_problem_shadow_unaffected.png). It is believed that keeping any new settings for a while will have the bug reoccur. It is not like bug 1536751. That one affects rendering quality of *all* glyphs, at all times, depending on dpi. This is not the case here: *some* glyphs (randomly chosen) are drawn corrupted (replaced by garbage or absent), not always. # Other 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu export LC_ALL=C ; lsb_release -rd Description: Ubuntu Xenial Xerus (development branch) Release: 16.04 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center apt-cache policy xorg xorg: Installed: 1:7.7+13ubuntu1 Candidate: 1:7.7+13ubuntu1 Version table: *** 1:7.7+13ubuntu1 500 500 http://fr.archive.ubuntu.com/ubuntu xenial/main amd64 Packages 100 /var/lib/dpkg/status 3) What you expected to happen 4) What happened instead Written above. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-4.19-generic 4.4.1 Uname: Linux 4.4.0-4-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 CurrentDesktop: XFCE Date: Thu Feb 18 16:03:55 2016 InstallationDate: Installed on 2016-02-03 (14 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160203) SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1547077/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help :
[Touch-packages] [Bug 1547077] Re: Some glyphs drawn consistently wrong, bug comes and go
** Attachment added: "see main text" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1547077/+attachment/4574618/+files/2016y02m10d_18h42m18s_0100Z_wow_screen_flickers_and_most_glyphs_wrong_01.png -- 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/1547077 Title: Some glyphs drawn consistently wrong, bug comes and go Status in xorg package in Ubuntu: New Bug description: # Summary * Some glyphs badly drawn at some moments. * When happens, same glyph drawn on various windows shows same corruption. * Problem comes and go. # Context Laptop, using Intel driver. Expected: all glyphs rendered correctly. Observed: some glyphs not rendered correctly * sometimes (problem comes and go, severity varies) * *some* glyphs are affected. For example, letter 'a' of a certain size will be replaced by colored garbage at many places where it appears (see 2016y02m18d_16h05m35s_0100Z_same_corruption_on_different_windows.png ), but other 'a' with different size, italic, bold, etc will be unaffected * in some applications (e.g. xfce whisker menu), some glyphs are rendered correctly or not depending on the direction of mouse hovering. See video 2016y02m16d_21h41m14s_0100Z_whisker_menu_missing_glyphs.mp4 . * in menu of gtk application, some glyphs are "fixed" by opening the menu, but not all. For example, in xfce4-terminal, letter A of "Affichage" and its menu content as well as "Aide" is affected. Opening "Affichage" menu does not fix anything. Opening "Aide" menu fixes the "A" of "Aide". Changing window size reactivates the bug on "A" or "Aide". See video 2016y02m18d_16h14m25s_0100Z_glyph-redrawn-bug.mp4 . * text under icons on desktop is affected, but shadows are not. See 2016y02m16d_21h32m11s_0100Z_x_bug_reenabling_antialias_reactivates_problem_shadow_unaffected.png # Affected applications Affected applications include: * xfce whisker menu, * xfce4-terminal, * firefox (see 2016y02m17d_18h08m27s_0100Z_x_bug_glyph_firefox_gnome_org.png 2016y02m16d_21h32m11s_0100Z_x_bug_reenabling_antialias_reactivates_problem_shadow_unaffected.png ), * thunderbird (see 2016y02m16d_21h28m35s_0100Z_x_bug_affects_thunderbird_terminal.png ), * emacs (see 2016y02m10d_18h41m49s_0100Z_wow_screen_flickers_and_most_glyphs_wrong_00.png and subsequent ), * superswitcher ( a gtk/gdk app) * *NOT* affected: xterm, xmessage. Perhaps only gtk/gdk/pango/cairo are affected. # Additional information This looks like a cache corruption somewhere. On IRC #ubuntu+1, someone suggested a bug in Intel driver. Running `xfce4-appearance-settings` and there changing any of: * antialiasing enable/disable, * hinting strength, * subpixel alignment * or dpi immediately cures the bug (see 2016y02m16d_21h31m52s_0100Z_x_bug_disabling_antialias_immediately_cures_problem.png ) Setting back the exact same parameters immediately reactivates the bug (see 2016y02m16d_21h32m11s_0100Z_x_bug_reenabling_antialias_reactivates_problem_shadow_unaffected.png). It is believed that keeping any new settings for a while will have the bug reoccur. It is not like bug 1536751. That one affects rendering quality of *all* glyphs, at all times, depending on dpi. This is not the case here: *some* glyphs (randomly chosen) are drawn corrupted (replaced by garbage or absent), not always. # Other 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu export LC_ALL=C ; lsb_release -rd Description: Ubuntu Xenial Xerus (development branch) Release: 16.04 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center apt-cache policy xorg xorg: Installed: 1:7.7+13ubuntu1 Candidate: 1:7.7+13ubuntu1 Version table: *** 1:7.7+13ubuntu1 500 500 http://fr.archive.ubuntu.com/ubuntu xenial/main amd64 Packages 100 /var/lib/dpkg/status 3) What you expected to happen 4) What happened instead Written above. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-4.19-generic 4.4.1 Uname: Linux 4.4.0-4-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 CurrentDesktop: XFCE Date: Thu Feb 18 16:03:55 2016 InstallationDate: Installed on 2016-02-03 (14 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160203) SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1547077/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help :
[Touch-packages] [Bug 1547077] Re: Some glyphs drawn consistently wrong, bug comes and go
** Attachment added: "see main text" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1547077/+attachment/4574616/+files/2016y02m10d_18h41m49s_0100Z_wow_screen_flickers_and_most_glyphs_wrong_00.png -- 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/1547077 Title: Some glyphs drawn consistently wrong, bug comes and go Status in xorg package in Ubuntu: New Bug description: # Summary * Some glyphs badly drawn at some moments. * When happens, same glyph drawn on various windows shows same corruption. * Problem comes and go. # Context Laptop, using Intel driver. Expected: all glyphs rendered correctly. Observed: some glyphs not rendered correctly * sometimes (problem comes and go, severity varies) * *some* glyphs are affected. For example, letter 'a' of a certain size will be replaced by colored garbage at many places where it appears (see 2016y02m18d_16h05m35s_0100Z_same_corruption_on_different_windows.png ), but other 'a' with different size, italic, bold, etc will be unaffected * in some applications (e.g. xfce whisker menu), some glyphs are rendered correctly or not depending on the direction of mouse hovering. See video 2016y02m16d_21h41m14s_0100Z_whisker_menu_missing_glyphs.mp4 . * in menu of gtk application, some glyphs are "fixed" by opening the menu, but not all. For example, in xfce4-terminal, letter A of "Affichage" and its menu content as well as "Aide" is affected. Opening "Affichage" menu does not fix anything. Opening "Aide" menu fixes the "A" of "Aide". Changing window size reactivates the bug on "A" or "Aide". See video 2016y02m18d_16h14m25s_0100Z_glyph-redrawn-bug.mp4 . * text under icons on desktop is affected, but shadows are not. See 2016y02m16d_21h32m11s_0100Z_x_bug_reenabling_antialias_reactivates_problem_shadow_unaffected.png # Affected applications Affected applications include: * xfce whisker menu, * xfce4-terminal, * firefox (see 2016y02m17d_18h08m27s_0100Z_x_bug_glyph_firefox_gnome_org.png 2016y02m16d_21h32m11s_0100Z_x_bug_reenabling_antialias_reactivates_problem_shadow_unaffected.png ), * thunderbird (see 2016y02m16d_21h28m35s_0100Z_x_bug_affects_thunderbird_terminal.png ), * emacs (see 2016y02m10d_18h41m49s_0100Z_wow_screen_flickers_and_most_glyphs_wrong_00.png and subsequent ), * superswitcher ( a gtk/gdk app) * *NOT* affected: xterm, xmessage. Perhaps only gtk/gdk/pango/cairo are affected. # Additional information This looks like a cache corruption somewhere. On IRC #ubuntu+1, someone suggested a bug in Intel driver. Running `xfce4-appearance-settings` and there changing any of: * antialiasing enable/disable, * hinting strength, * subpixel alignment * or dpi immediately cures the bug (see 2016y02m16d_21h31m52s_0100Z_x_bug_disabling_antialias_immediately_cures_problem.png ) Setting back the exact same parameters immediately reactivates the bug (see 2016y02m16d_21h32m11s_0100Z_x_bug_reenabling_antialias_reactivates_problem_shadow_unaffected.png). It is believed that keeping any new settings for a while will have the bug reoccur. It is not like bug 1536751. That one affects rendering quality of *all* glyphs, at all times, depending on dpi. This is not the case here: *some* glyphs (randomly chosen) are drawn corrupted (replaced by garbage or absent), not always. # Other 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu export LC_ALL=C ; lsb_release -rd Description: Ubuntu Xenial Xerus (development branch) Release: 16.04 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center apt-cache policy xorg xorg: Installed: 1:7.7+13ubuntu1 Candidate: 1:7.7+13ubuntu1 Version table: *** 1:7.7+13ubuntu1 500 500 http://fr.archive.ubuntu.com/ubuntu xenial/main amd64 Packages 100 /var/lib/dpkg/status 3) What you expected to happen 4) What happened instead Written above. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-4.19-generic 4.4.1 Uname: Linux 4.4.0-4-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 CurrentDesktop: XFCE Date: Thu Feb 18 16:03:55 2016 InstallationDate: Installed on 2016-02-03 (14 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160203) SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1547077/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help :
[Touch-packages] [Bug 1547077] Re: Some glyphs drawn consistently wrong, bug comes and go
** Attachment added: "see main text" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1547077/+attachment/4574617/+files/2016y02m16d_21h31m52s_0100Z_x_bug_disabling_antialias_immediately_cures_problem.png -- 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/1547077 Title: Some glyphs drawn consistently wrong, bug comes and go Status in xorg package in Ubuntu: New Bug description: # Summary * Some glyphs badly drawn at some moments. * When happens, same glyph drawn on various windows shows same corruption. * Problem comes and go. # Context Laptop, using Intel driver. Expected: all glyphs rendered correctly. Observed: some glyphs not rendered correctly * sometimes (problem comes and go, severity varies) * *some* glyphs are affected. For example, letter 'a' of a certain size will be replaced by colored garbage at many places where it appears (see 2016y02m18d_16h05m35s_0100Z_same_corruption_on_different_windows.png ), but other 'a' with different size, italic, bold, etc will be unaffected * in some applications (e.g. xfce whisker menu), some glyphs are rendered correctly or not depending on the direction of mouse hovering. See video 2016y02m16d_21h41m14s_0100Z_whisker_menu_missing_glyphs.mp4 . * in menu of gtk application, some glyphs are "fixed" by opening the menu, but not all. For example, in xfce4-terminal, letter A of "Affichage" and its menu content as well as "Aide" is affected. Opening "Affichage" menu does not fix anything. Opening "Aide" menu fixes the "A" of "Aide". Changing window size reactivates the bug on "A" or "Aide". See video 2016y02m18d_16h14m25s_0100Z_glyph-redrawn-bug.mp4 . * text under icons on desktop is affected, but shadows are not. See 2016y02m16d_21h32m11s_0100Z_x_bug_reenabling_antialias_reactivates_problem_shadow_unaffected.png # Affected applications Affected applications include: * xfce whisker menu, * xfce4-terminal, * firefox (see 2016y02m17d_18h08m27s_0100Z_x_bug_glyph_firefox_gnome_org.png 2016y02m16d_21h32m11s_0100Z_x_bug_reenabling_antialias_reactivates_problem_shadow_unaffected.png ), * thunderbird (see 2016y02m16d_21h28m35s_0100Z_x_bug_affects_thunderbird_terminal.png ), * emacs (see 2016y02m10d_18h41m49s_0100Z_wow_screen_flickers_and_most_glyphs_wrong_00.png and subsequent ), * superswitcher ( a gtk/gdk app) * *NOT* affected: xterm, xmessage. Perhaps only gtk/gdk/pango/cairo are affected. # Additional information This looks like a cache corruption somewhere. On IRC #ubuntu+1, someone suggested a bug in Intel driver. Running `xfce4-appearance-settings` and there changing any of: * antialiasing enable/disable, * hinting strength, * subpixel alignment * or dpi immediately cures the bug (see 2016y02m16d_21h31m52s_0100Z_x_bug_disabling_antialias_immediately_cures_problem.png ) Setting back the exact same parameters immediately reactivates the bug (see 2016y02m16d_21h32m11s_0100Z_x_bug_reenabling_antialias_reactivates_problem_shadow_unaffected.png). It is believed that keeping any new settings for a while will have the bug reoccur. It is not like bug 1536751. That one affects rendering quality of *all* glyphs, at all times, depending on dpi. This is not the case here: *some* glyphs (randomly chosen) are drawn corrupted (replaced by garbage or absent), not always. # Other 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu export LC_ALL=C ; lsb_release -rd Description: Ubuntu Xenial Xerus (development branch) Release: 16.04 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center apt-cache policy xorg xorg: Installed: 1:7.7+13ubuntu1 Candidate: 1:7.7+13ubuntu1 Version table: *** 1:7.7+13ubuntu1 500 500 http://fr.archive.ubuntu.com/ubuntu xenial/main amd64 Packages 100 /var/lib/dpkg/status 3) What you expected to happen 4) What happened instead Written above. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-4.19-generic 4.4.1 Uname: Linux 4.4.0-4-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 CurrentDesktop: XFCE Date: Thu Feb 18 16:03:55 2016 InstallationDate: Installed on 2016-02-03 (14 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160203) SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1547077/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help
[Touch-packages] [Bug 1547077] Re: Some glyphs drawn consistently wrong, bug comes and go
** Attachment added: "see main text" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1547077/+attachment/4574619/+files/2016y02m10d_18h43m35s_0100Z_wow_screen_flickers_and_most_glyphs_wrong_03.png -- 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/1547077 Title: Some glyphs drawn consistently wrong, bug comes and go Status in xorg package in Ubuntu: New Bug description: # Summary * Some glyphs badly drawn at some moments. * When happens, same glyph drawn on various windows shows same corruption. * Problem comes and go. # Context Laptop, using Intel driver. Expected: all glyphs rendered correctly. Observed: some glyphs not rendered correctly * sometimes (problem comes and go, severity varies) * *some* glyphs are affected. For example, letter 'a' of a certain size will be replaced by colored garbage at many places where it appears (see 2016y02m18d_16h05m35s_0100Z_same_corruption_on_different_windows.png ), but other 'a' with different size, italic, bold, etc will be unaffected * in some applications (e.g. xfce whisker menu), some glyphs are rendered correctly or not depending on the direction of mouse hovering. See video 2016y02m16d_21h41m14s_0100Z_whisker_menu_missing_glyphs.mp4 . * in menu of gtk application, some glyphs are "fixed" by opening the menu, but not all. For example, in xfce4-terminal, letter A of "Affichage" and its menu content as well as "Aide" is affected. Opening "Affichage" menu does not fix anything. Opening "Aide" menu fixes the "A" of "Aide". Changing window size reactivates the bug on "A" or "Aide". See video 2016y02m18d_16h14m25s_0100Z_glyph-redrawn-bug.mp4 . * text under icons on desktop is affected, but shadows are not. See 2016y02m16d_21h32m11s_0100Z_x_bug_reenabling_antialias_reactivates_problem_shadow_unaffected.png # Affected applications Affected applications include: * xfce whisker menu, * xfce4-terminal, * firefox (see 2016y02m17d_18h08m27s_0100Z_x_bug_glyph_firefox_gnome_org.png 2016y02m16d_21h32m11s_0100Z_x_bug_reenabling_antialias_reactivates_problem_shadow_unaffected.png ), * thunderbird (see 2016y02m16d_21h28m35s_0100Z_x_bug_affects_thunderbird_terminal.png ), * emacs (see 2016y02m10d_18h41m49s_0100Z_wow_screen_flickers_and_most_glyphs_wrong_00.png and subsequent ), * superswitcher ( a gtk/gdk app) * *NOT* affected: xterm, xmessage. Perhaps only gtk/gdk/pango/cairo are affected. # Additional information This looks like a cache corruption somewhere. On IRC #ubuntu+1, someone suggested a bug in Intel driver. Running `xfce4-appearance-settings` and there changing any of: * antialiasing enable/disable, * hinting strength, * subpixel alignment * or dpi immediately cures the bug (see 2016y02m16d_21h31m52s_0100Z_x_bug_disabling_antialias_immediately_cures_problem.png ) Setting back the exact same parameters immediately reactivates the bug (see 2016y02m16d_21h32m11s_0100Z_x_bug_reenabling_antialias_reactivates_problem_shadow_unaffected.png). It is believed that keeping any new settings for a while will have the bug reoccur. It is not like bug 1536751. That one affects rendering quality of *all* glyphs, at all times, depending on dpi. This is not the case here: *some* glyphs (randomly chosen) are drawn corrupted (replaced by garbage or absent), not always. # Other 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu export LC_ALL=C ; lsb_release -rd Description: Ubuntu Xenial Xerus (development branch) Release: 16.04 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center apt-cache policy xorg xorg: Installed: 1:7.7+13ubuntu1 Candidate: 1:7.7+13ubuntu1 Version table: *** 1:7.7+13ubuntu1 500 500 http://fr.archive.ubuntu.com/ubuntu xenial/main amd64 Packages 100 /var/lib/dpkg/status 3) What you expected to happen 4) What happened instead Written above. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-4.19-generic 4.4.1 Uname: Linux 4.4.0-4-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 CurrentDesktop: XFCE Date: Thu Feb 18 16:03:55 2016 InstallationDate: Installed on 2016-02-03 (14 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160203) SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1547077/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help :
[Touch-packages] [Bug 1547077] [NEW] Some glyphs drawn consistently wrong, bug comes and go
Public bug reported: # Summary * Some glyphs badly drawn at some moments. * When happens, same glyph drawn on various windows shows same corruption. * Problem comes and go. # Context Laptop, using Intel driver. Expected: all glyphs rendered correctly. Observed: some glyphs not rendered correctly * sometimes (problem comes and go, severity varies) * *some* glyphs are affected. For example, letter 'a' of a certain size will be replaced by colored garbage at many places where it appears (see 2016y02m18d_16h05m35s_0100Z_same_corruption_on_different_windows.png ), but other 'a' with different size, italic, bold, etc will be unaffected * in some applications (e.g. xfce whisker menu), some glyphs are rendered correctly or not depending on the direction of mouse hovering. See video 2016y02m16d_21h41m14s_0100Z_whisker_menu_missing_glyphs.mp4 . * in menu of gtk application, some glyphs are "fixed" by opening the menu, but not all. For example, in xfce4-terminal, letter A of "Affichage" and its menu content as well as "Aide" is affected. Opening "Affichage" menu does not fix anything. Opening "Aide" menu fixes the "A" of "Aide". Changing window size reactivates the bug on "A" or "Aide". See video 2016y02m18d_16h14m25s_0100Z_glyph-redrawn-bug.mp4 . * text under icons on desktop is affected, but shadows are not. See 2016y02m16d_21h32m11s_0100Z_x_bug_reenabling_antialias_reactivates_problem_shadow_unaffected.png # Affected applications Affected applications include: * xfce whisker menu, * xfce4-terminal, * firefox (see 2016y02m17d_18h08m27s_0100Z_x_bug_glyph_firefox_gnome_org.png 2016y02m16d_21h32m11s_0100Z_x_bug_reenabling_antialias_reactivates_problem_shadow_unaffected.png ), * thunderbird (see 2016y02m16d_21h28m35s_0100Z_x_bug_affects_thunderbird_terminal.png ), * emacs (see 2016y02m10d_18h41m49s_0100Z_wow_screen_flickers_and_most_glyphs_wrong_00.png and subsequent ), * superswitcher ( a gtk/gdk app) * *NOT* affected: xterm, xmessage. Perhaps only gtk/gdk/pango/cairo are affected. # Additional information This looks like a cache corruption somewhere. On IRC #ubuntu+1, someone suggested a bug in Intel driver. Running `xfce4-appearance-settings` and there changing any of: * antialiasing enable/disable, * hinting strength, * subpixel alignment * or dpi immediately cures the bug (see 2016y02m16d_21h31m52s_0100Z_x_bug_disabling_antialias_immediately_cures_problem.png ) Setting back the exact same parameters immediately reactivates the bug (see 2016y02m16d_21h32m11s_0100Z_x_bug_reenabling_antialias_reactivates_problem_shadow_unaffected.png). It is believed that keeping any new settings for a while will have the bug reoccur. It is not like bug 1536751. That one affects rendering quality of *all* glyphs, at all times, depending on dpi. This is not the case here: *some* glyphs (randomly chosen) are drawn corrupted (replaced by garbage or absent), not always. # Other 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu export LC_ALL=C ; lsb_release -rd Description:Ubuntu Xenial Xerus (development branch) Release:16.04 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center apt-cache policy xorg xorg: Installed: 1:7.7+13ubuntu1 Candidate: 1:7.7+13ubuntu1 Version table: *** 1:7.7+13ubuntu1 500 500 http://fr.archive.ubuntu.com/ubuntu xenial/main amd64 Packages 100 /var/lib/dpkg/status 3) What you expected to happen 4) What happened instead Written above. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-4.19-generic 4.4.1 Uname: Linux 4.4.0-4-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 CurrentDesktop: XFCE Date: Thu Feb 18 16:03:55 2016 InstallationDate: Installed on 2016-02-03 (14 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160203) SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug corruption xenial -- 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/1547077 Title: Some glyphs drawn consistently wrong, bug comes and go Status in xorg package in Ubuntu: New Bug description: # Summary * Some glyphs badly drawn at some moments. * When happens, same glyph drawn on various windows shows same corruption. * Problem comes and go. # Context Laptop, using Intel driver. Expected: all glyphs rendered correctly. Observed: some glyphs not rendered correctly * sometimes (problem comes and go, severity varies) * *some* glyphs are affected. For example, letter 'a' of a certain size will be replaced by colored garbage at many places where it appears (see
[Touch-packages] [Bug 1547077] Re: Some glyphs drawn consistently wrong, bug comes and go
** Attachment added: "see main text" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1547077/+attachment/4574615/+files/2016y02m05d_15h50m04s_0100Z_firefox_display_bug_major_stackoverflow.png -- 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/1547077 Title: Some glyphs drawn consistently wrong, bug comes and go Status in xorg package in Ubuntu: New Bug description: # Summary * Some glyphs badly drawn at some moments. * When happens, same glyph drawn on various windows shows same corruption. * Problem comes and go. # Context Laptop, using Intel driver. Expected: all glyphs rendered correctly. Observed: some glyphs not rendered correctly * sometimes (problem comes and go, severity varies) * *some* glyphs are affected. For example, letter 'a' of a certain size will be replaced by colored garbage at many places where it appears (see 2016y02m18d_16h05m35s_0100Z_same_corruption_on_different_windows.png ), but other 'a' with different size, italic, bold, etc will be unaffected * in some applications (e.g. xfce whisker menu), some glyphs are rendered correctly or not depending on the direction of mouse hovering. See video 2016y02m16d_21h41m14s_0100Z_whisker_menu_missing_glyphs.mp4 . * in menu of gtk application, some glyphs are "fixed" by opening the menu, but not all. For example, in xfce4-terminal, letter A of "Affichage" and its menu content as well as "Aide" is affected. Opening "Affichage" menu does not fix anything. Opening "Aide" menu fixes the "A" of "Aide". Changing window size reactivates the bug on "A" or "Aide". See video 2016y02m18d_16h14m25s_0100Z_glyph-redrawn-bug.mp4 . * text under icons on desktop is affected, but shadows are not. See 2016y02m16d_21h32m11s_0100Z_x_bug_reenabling_antialias_reactivates_problem_shadow_unaffected.png # Affected applications Affected applications include: * xfce whisker menu, * xfce4-terminal, * firefox (see 2016y02m17d_18h08m27s_0100Z_x_bug_glyph_firefox_gnome_org.png 2016y02m16d_21h32m11s_0100Z_x_bug_reenabling_antialias_reactivates_problem_shadow_unaffected.png ), * thunderbird (see 2016y02m16d_21h28m35s_0100Z_x_bug_affects_thunderbird_terminal.png ), * emacs (see 2016y02m10d_18h41m49s_0100Z_wow_screen_flickers_and_most_glyphs_wrong_00.png and subsequent ), * superswitcher ( a gtk/gdk app) * *NOT* affected: xterm, xmessage. Perhaps only gtk/gdk/pango/cairo are affected. # Additional information This looks like a cache corruption somewhere. On IRC #ubuntu+1, someone suggested a bug in Intel driver. Running `xfce4-appearance-settings` and there changing any of: * antialiasing enable/disable, * hinting strength, * subpixel alignment * or dpi immediately cures the bug (see 2016y02m16d_21h31m52s_0100Z_x_bug_disabling_antialias_immediately_cures_problem.png ) Setting back the exact same parameters immediately reactivates the bug (see 2016y02m16d_21h32m11s_0100Z_x_bug_reenabling_antialias_reactivates_problem_shadow_unaffected.png). It is believed that keeping any new settings for a while will have the bug reoccur. It is not like bug 1536751. That one affects rendering quality of *all* glyphs, at all times, depending on dpi. This is not the case here: *some* glyphs (randomly chosen) are drawn corrupted (replaced by garbage or absent), not always. # Other 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu export LC_ALL=C ; lsb_release -rd Description: Ubuntu Xenial Xerus (development branch) Release: 16.04 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center apt-cache policy xorg xorg: Installed: 1:7.7+13ubuntu1 Candidate: 1:7.7+13ubuntu1 Version table: *** 1:7.7+13ubuntu1 500 500 http://fr.archive.ubuntu.com/ubuntu xenial/main amd64 Packages 100 /var/lib/dpkg/status 3) What you expected to happen 4) What happened instead Written above. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-4.19-generic 4.4.1 Uname: Linux 4.4.0-4-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 CurrentDesktop: XFCE Date: Thu Feb 18 16:03:55 2016 InstallationDate: Installed on 2016-02-03 (14 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160203) SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1547077/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help :
[Touch-packages] [Bug 1485558] Re: NetworkManager breaks vboxnet* connections since 15.04, worked in 14.04 and 14.10
Summary: more trouble, nm-applet menu starts to fill with irrelevant vboxnet0 entries. Details Now nm-applet shows 5 vboxnet0 ethernet connections, though I've not created any of them. 4 of them show ipv4 parameters disabled, ipv6 parameters ignore. Only the currently auto-activated one shows ipv4 manual with correct IP address. Suspending then resuming the Ubuntu machine still breaks the vboxnet0 connection to the VM. Asking virtualbox to suspend the guest VM then resuming it still reconfigures the connection which then works. And that causes *another extra* vboxnet0 entry in nm-applet list of connections. I can suppress it manually but they should not be there in the first place. Note: /etc/NetworkManager/system-connections/ now contains entries for the real connections I've created, but none of these vboxnet0 connections. Thank you for your attention. ** Summary changed: - NetworkManager breaks vboxnet* connections since 15.04, worked in 14.04 and 14.10 + NetworkManager breaks vboxnet* connections since 15.04, worked in 14.04 and 14.10, nm-applet fills with irrelevant entries. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1485558 Title: NetworkManager breaks vboxnet* connections since 15.04, worked in 14.04 and 14.10, nm-applet fills with irrelevant entries. Status in network-manager package in Ubuntu: Confirmed Bug description: On an Asus laptop running a freshly installed Ubuntu 15.04 64-bit, nm- applet shows that NetworkManager wants to manage vboxnet0 and vboxnet1. These are created by virtualbox which runs some guest OS inside a VM. On previous Ubuntu releases, network-manager did not try to manage them and there was no problem. # Observed behavior * nm-applet shows spinning animation for a long time, while it is not relevant. Clicking on disconnect in the menu unconfigures the interface which breaks it. * after suspend-resume of the host, vboxnet* lose their correct configurations. vboxnet0 (a host-only interface where virtualbox runs a private dhcp server) gets a different IP address. Looks like https://bugs.launchpad.net/ubuntu/+source/virtualbox/+bug/1460750 but does not feel like a bug in virtualbox. # Expected behavior * Just like in 14.04 and 14.10, these interfaces are just ignored by network-manager and they just work. # Additional information * After reading http://superuser.com/questions/9720/disabling- networkmanager-for-a-specific-interface tried to add these lines to /etc/network/interfaces. Even after restarting network-manager, it has no effect. iface vboxnet0 inet manual iface vboxnet1 inet manual So, reverted the change. * Tried from https://blogs.gnome.org/dcbw/2015/02/16/networkmanager- for-administrators-part-1/ to add in /etc/NetworkManager/conf.d/ a file 50-virtualbox.conf containing the following lines. Even after restarting network-manager, it is ignored. [keyfile] unmanaged-devices=vboxnet0,vboxnet1 * This is not eactly like https://www.virtualbox.org/ticket/13873, I'm not using Vagrant. * Booting to 14.04 or 14.10 (that have been kept intact on the same machine) things just work as expected. * /usr/share/doc/network-manager/NEWS.gz states that 'veth' interfaces are now unmanaged by default to cooperate better with external tools. Should vboxnet* be treated the same ? * This seems on the topic but unclear to me: https://bugzilla.gnome.org/show_bug.cgi?id=731014 Thank you for your attention. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: network-manager 0.9.10.0-4ubuntu15.1 ProcVersionSignature: Ubuntu 3.19.0-25.26-generic 3.19.8-ckt2 Uname: Linux 3.19.0-25-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.2 Architecture: amd64 Date: Mon Aug 17 13:13:04 2015 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2015-08-15 (1 days ago) InstallationMedia: Xubuntu 15.04 Vivid Vervet - Release amd64 (20150422.1) IpRoute: default via 192.168.47.1 dev wlan0 proto static metric 1024 169.254.0.0/16 dev vboxnet0 scope link metric 1000 192.168.47.0/24 dev wlan0 proto kernel scope link src 192.168.47.6 192.168.56.0/24 dev vboxnet0 proto kernel scope link src 192.168.56.102 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true ProcEnviron: LANGUAGE=fr_FR TERM=xterm PATH=(custom, no user) LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: Error: Object 'nm' is unknown, try 'nmcli help'. To manage notifications about this bug go to:
[Touch-packages] [Bug 1485558] Re: NetworkManager breaks vboxnet* connections since 15.04, worked in 14.04 and 14.10
I tried this variant to tell NetworkManager to ignore the virtual devices: [keyfile] unmanaged-devices=mac:xx:xx:xx:xx:xx:xx (using the real MAC address of course) It still does not change anything. But I noticed this in the log, which happen whether or not the unmanaged-devices option is set: Aug 19 18:52:04 n55sf-l NetworkManager[6399]: nm_device_get_device_type: assertion 'NM_IS_DEVICE (self)' failed Aug 19 18:52:04 n55sf-l NetworkManager[6399]: info (vboxnet0): driver 'unknown' does not support carrier detection. Aug 19 18:52:04 n55sf-l NetworkManager[6399]: info (vboxnet0): device is virtual, marking as unmanaged Aug 19 18:52:04 n55sf-l NetworkManager[6399]: info (vboxnet0): new Ethernet device (driver: 'unknown' ifindex: 4) Aug 19 18:52:04 n55sf-l NetworkManager[6399]: info (vboxnet0): exported as /org/freedesktop/NetworkManager/Devices/3 Aug 19 18:52:04 n55sf-l NetworkManager[6399]: nm_device_get_device_type: assertion 'NM_IS_DEVICE (self)' failed Aug 19 18:52:04 n55sf-l NetworkManager[6399]: info (vboxnet1): driver 'unknown' does not support carrier detection. Aug 19 18:52:04 n55sf-l NetworkManager[6399]: info (vboxnet1): device is virtual, marking as unmanaged Aug 19 18:52:04 n55sf-l NetworkManager[6399]: info (vboxnet1): new Ethernet device (driver: 'unknown' ifindex: 5) Aug 19 18:52:04 n55sf-l NetworkManager[6399]: info (vboxnet1): exported as /org/freedesktop/NetworkManager/Devices/4 So, basically it seems that the devices is correctly seen as virtual and unmanaged by Network-Manager but still it finally manages it. More details obtained using command below confirm that NetworkManager does DHCP on vboxnet0 which is definitely wrong. grep -i network.*manag.*vbox /var/log/syslog -C 3 Aug 19 18:59:43 n55sf-l NetworkManager[8151]: info (wlan0): device state change: unmanaged - unavailable (reason 'managed') [10 20 2] Aug 19 18:59:43 n55sf-l NetworkManager[8151]: info (wlan0): preparing device Aug 19 18:59:43 n55sf-l NetworkManager[8151]: nm_device_get_device_type: assertion 'NM_IS_DEVICE (self)' failed Aug 19 18:59:43 n55sf-l NetworkManager[8151]: info (vboxnet0): driver 'unknown' does not support carrier detection. Aug 19 18:59:43 n55sf-l NetworkManager[8151]: info (vboxnet0): device is virtual, marking as unmanaged Aug 19 18:59:43 n55sf-l NetworkManager[8151]: info (vboxnet0): new Ethernet device (driver: 'unknown' ifindex: 4) Aug 19 18:59:43 n55sf-l NetworkManager[8151]: info (vboxnet0): exported as /org/freedesktop/NetworkManager/Devices/3 Aug 19 18:59:43 n55sf-l NetworkManager[8151]: nm_device_get_device_type: assertion 'NM_IS_DEVICE (self)' failed Aug 19 18:59:43 n55sf-l NetworkManager[8151]: info (vboxnet1): driver 'unknown' does not support carrier detection. Aug 19 18:59:43 n55sf-l NetworkManager[8151]: info (vboxnet1): device is virtual, marking as unmanaged Aug 19 18:59:43 n55sf-l NetworkManager[8151]: info (vboxnet1): new Ethernet device (driver: 'unknown' ifindex: 5) Aug 19 18:59:43 n55sf-l NetworkManager[8151]: info (vboxnet1): exported as /org/freedesktop/NetworkManager/Devices/4 Aug 19 18:59:43 n55sf-l NetworkManager[8151]: info urfkill disappeared from the bus Aug 19 18:59:43 n55sf-l NetworkManager[8151]: info use BlueZ version 4 Aug 19 18:59:43 n55sf-l wpa_supplicant[893]: dbus: wpa_dbus_get_object_properties: failed to get object properties: (none) none -- Aug 19 18:59:43 n55sf-l wpa_supplicant[893]: wlan0: CTRL-EVENT-SCAN-STARTED Aug 19 18:59:43 n55sf-l NetworkManager[8151]: info ModemManager available in the bus Aug 19 18:59:43 n55sf-l NetworkManager[8151]: info Auto-activating connection 'Auto SG IP auto'. Aug 19 18:59:43 n55sf-l NetworkManager[8151]: info Activation (vboxnet0) starting connection 'Auto SG IP auto' Aug 19 18:59:43 n55sf-l NetworkManager[8151]: info (vboxnet0): device state change: unmanaged - disconnected (reason 'managed') [10 30 2] Aug 19 18:59:43 n55sf-l NetworkManager[8151]: info Activation (vboxnet0) Stage 1 of 5 (Device Prepare) scheduled... Aug 19 18:59:43 n55sf-l NetworkManager[8151]: info Activation (vboxnet0) Stage 1 of 5 (Device Prepare) started... Aug 19 18:59:43 n55sf-l NetworkManager[8151]: info (vboxnet0): device state change: disconnected - prepare (reason 'none') [30 40 0] Aug 19 18:59:43 n55sf-l NetworkManager[8151]: info NetworkManager state is now CONNECTING Aug 19 18:59:43 n55sf-l NetworkManager[8151]: info Activation (vboxnet0) Stage 2 of 5 (Device Configure) scheduled... Aug 19 18:59:43 n55sf-l NetworkManager[8151]: info Activation (vboxnet0) Stage 1 of 5 (Device Prepare) complete. Aug 19 18:59:43 n55sf-l NetworkManager[8151]: info Activation (vboxnet0) Stage 2 of 5 (Device Configure) starting... Aug 19 18:59:43 n55sf-l NetworkManager[8151]: info (vboxnet0): device state change: prepare - config (reason 'none') [40 50 0] Aug 19 18:59:43 n55sf-l NetworkManager[8151]: info Activation (vboxnet0) Stage 2 of 5 (Device Configure) successful. Aug 19 18:59:43 n55sf-l NetworkManager[8151]: info
[Touch-packages] [Bug 1485558] Re: NetworkManager breaks vboxnet* connections since 15.04, worked in 14.04 and 14.10
I unchecked the auto-connect option on connection 'Auto SG IP auto' to see if it changes anything. The behavior is different but satisfying. Again, on suspend of the host, NetworkManager disables vboxnet0. It just does not do DHCP on it. Again, suspending the resuming the virtual machine repairs the connection. Summary: still broken and still a regression. On Ubuntu 14.04 and 14.10, suspending and resuming the host did not interfere with the vboxnet* interfaces. Thank you for your attention. Aug 19 19:04:32 n55sf-l NetworkManager[9431]: info (vboxnet0): device state change: unmanaged - unavailable (reason 'connection-assumed') [10 20 41] Aug 19 19:04:32 n55sf-l NetworkManager[9431]: info (vboxnet0): device state change: unavailable - disconnected (reason 'connection-assumed') [20 30 41] Aug 19 19:04:32 n55sf-l NetworkManager[9431]: info Activation (vboxnet0) starting connection 'vboxnet0' Aug 19 19:04:32 n55sf-l NetworkManager[9431]: info Activation (vboxnet0) Stage 1 of 5 (Device Prepare) scheduled... Aug 19 19:04:32 n55sf-l NetworkManager[9431]: info Activation (vboxnet0) Stage 1 of 5 (Device Prepare) started... Aug 19 19:04:32 n55sf-l NetworkManager[9431]: info (vboxnet0): device state change: disconnected - prepare (reason 'none') [30 40 0] Aug 19 19:04:32 n55sf-l NetworkManager[9431]: info Activation (vboxnet0) Stage 2 of 5 (Device Configure) scheduled... Aug 19 19:04:32 n55sf-l NetworkManager[9431]: info Activation (vboxnet0) Stage 1 of 5 (Device Prepare) complete. Aug 19 19:04:32 n55sf-l NetworkManager[9431]: info Activation (vboxnet0) Stage 2 of 5 (Device Configure) starting... Aug 19 19:04:32 n55sf-l NetworkManager[9431]: info (vboxnet0): device state change: prepare - config (reason 'none') [40 50 0] Aug 19 19:04:32 n55sf-l NetworkManager[9431]: info Activation (vboxnet0) Stage 2 of 5 (Device Configure) successful. Aug 19 19:04:32 n55sf-l NetworkManager[9431]: info Activation (vboxnet0) Stage 3 of 5 (IP Configure Start) scheduled. Aug 19 19:04:32 n55sf-l NetworkManager[9431]: info Activation (vboxnet0) Stage 2 of 5 (Device Configure) complete. Aug 19 19:04:32 n55sf-l NetworkManager[9431]: info Activation (vboxnet0) Stage 3 of 5 (IP Configure Start) started... Aug 19 19:04:32 n55sf-l NetworkManager[9431]: info (vboxnet0): device state change: config - ip-config (reason 'none') [50 70 0] Aug 19 19:04:32 n55sf-l NetworkManager[9431]: info Activation (vboxnet0) Stage 5 of 5 (IPv4 Configure Commit) scheduled... Aug 19 19:04:32 n55sf-l NetworkManager[9431]: info Activation (vboxnet0) Stage 3 of 5 (IP Configure Start) complete. Aug 19 19:04:32 n55sf-l NetworkManager[9431]: info Activation (vboxnet0) Stage 5 of 5 (IPv4 Commit) started... Aug 19 19:04:32 n55sf-l NetworkManager[9431]: info (vboxnet0): device state change: ip-config - ip-check (reason 'none') [70 80 0] Aug 19 19:04:32 n55sf-l NetworkManager[9431]: info Activation (vboxnet0) Stage 5 of 5 (IPv4 Commit) complete. Aug 19 19:04:32 n55sf-l NetworkManager[9431]: info (vboxnet0): device state change: ip-check - secondaries (reason 'none') [80 90 0] Aug 19 19:04:32 n55sf-l NetworkManager[9431]: info (vboxnet0): device state change: secondaries - activated (reason 'none') [90 100 0] Aug 19 19:04:32 n55sf-l NetworkManager[9431]: info Activation (vboxnet0) successful, device activated. Aug 19 19:09:42 n55sf-l NetworkManager[9431]: info (vboxnet0): device state change: unmanaged - unavailable (reason 'connection-assumed') [10 20 41] Aug 19 19:09:42 n55sf-l NetworkManager[9431]: info (vboxnet0): device state change: unavailable - disconnected (reason 'connection-assumed') [20 30 41] Aug 19 19:09:42 n55sf-l NetworkManager[9431]: info Activation (vboxnet0) starting connection 'vboxnet0' Aug 19 19:09:42 n55sf-l NetworkManager[9431]: info Activation (vboxnet0) Stage 1 of 5 (Device Prepare) scheduled... Aug 19 19:09:42 n55sf-l NetworkManager[9431]: info Activation (vboxnet0) Stage 1 of 5 (Device Prepare) started... Aug 19 19:09:42 n55sf-l NetworkManager[9431]: info (vboxnet0): device state change: disconnected - prepare (reason 'none') [30 40 0] Aug 19 19:09:42 n55sf-l NetworkManager[9431]: info Activation (vboxnet0) Stage 2 of 5 (Device Configure) scheduled... Aug 19 19:09:42 n55sf-l NetworkManager[9431]: info Activation (vboxnet0) Stage 1 of 5 (Device Prepare) complete. Aug 19 19:09:42 n55sf-l NetworkManager[9431]: info Activation (vboxnet0) Stage 2 of 5 (Device Configure) starting... Aug 19 19:09:42 n55sf-l NetworkManager[9431]: info (vboxnet0): device state change: prepare - config (reason 'none') [40 50 0] Aug 19 19:09:42 n55sf-l NetworkManager[9431]: info Activation (vboxnet0) Stage 2 of 5 (Device Configure) successful. Aug 19 19:09:42 n55sf-l NetworkManager[9431]: info Activation (vboxnet0) Stage 3 of 5 (IP Configure Start) scheduled. Aug 19 19:09:42 n55sf-l NetworkManager[9431]: info Activation (vboxnet0) Stage 2 of 5 (Device Configure) complete. Aug 19 19:09:42 n55sf-l NetworkManager[9431]: info Activation
[Touch-packages] [Bug 1485558] Re: NetworkManager breaks vboxnet* connections since 15.04, worked in 14.04 and 14.10
Oops I sent The behavior is different but satisfying. It meant: The behavior is different but not satisfying. Summary: somehow NetworkManager has very well understood (as shown in log) that vboxnet* interfaces should be ignored, but somehow it still manages them. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1485558 Title: NetworkManager breaks vboxnet* connections since 15.04, worked in 14.04 and 14.10 Status in network-manager package in Ubuntu: New Bug description: On an Asus laptop running a freshly installed Ubuntu 15.04 64-bit, nm- applet shows that NetworkManager wants to manage vboxnet0 and vboxnet1. These are created by virtualbox which runs some guest OS inside a VM. On previous Ubuntu releases, network-manager did not try to manage them and there was no problem. # Observed behavior * nm-applet shows spinning animation for a long time, while it is not relevant. Clicking on disconnect in the menu unconfigures the interface which breaks it. * after suspend-resume of the host, vboxnet* lose their correct configurations. vboxnet0 (a host-only interface where virtualbox runs a private dhcp server) gets a different IP address. Looks like https://bugs.launchpad.net/ubuntu/+source/virtualbox/+bug/1460750 but does not feel like a bug in virtualbox. # Expected behavior * Just like in 14.04 and 14.10, these interfaces are just ignored by network-manager and they just work. # Additional information * After reading http://superuser.com/questions/9720/disabling- networkmanager-for-a-specific-interface tried to add these lines to /etc/network/interfaces. Even after restarting network-manager, it has no effect. iface vboxnet0 inet manual iface vboxnet1 inet manual So, reverted the change. * Tried from https://blogs.gnome.org/dcbw/2015/02/16/networkmanager- for-administrators-part-1/ to add in /etc/NetworkManager/conf.d/ a file 50-virtualbox.conf containing the following lines. Even after restarting network-manager, it is ignored. [keyfile] unmanaged-devices=vboxnet0,vboxnet1 * This is not eactly like https://www.virtualbox.org/ticket/13873, I'm not using Vagrant. * Booting to 14.04 or 14.10 (that have been kept intact on the same machine) things just work as expected. * /usr/share/doc/network-manager/NEWS.gz states that 'veth' interfaces are now unmanaged by default to cooperate better with external tools. Should vboxnet* be treated the same ? * This seems on the topic but unclear to me: https://bugzilla.gnome.org/show_bug.cgi?id=731014 Thank you for your attention. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: network-manager 0.9.10.0-4ubuntu15.1 ProcVersionSignature: Ubuntu 3.19.0-25.26-generic 3.19.8-ckt2 Uname: Linux 3.19.0-25-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.2 Architecture: amd64 Date: Mon Aug 17 13:13:04 2015 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2015-08-15 (1 days ago) InstallationMedia: Xubuntu 15.04 Vivid Vervet - Release amd64 (20150422.1) IpRoute: default via 192.168.47.1 dev wlan0 proto static metric 1024 169.254.0.0/16 dev vboxnet0 scope link metric 1000 192.168.47.0/24 dev wlan0 proto kernel scope link src 192.168.47.6 192.168.56.0/24 dev vboxnet0 proto kernel scope link src 192.168.56.102 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true ProcEnviron: LANGUAGE=fr_FR TERM=xterm PATH=(custom, no user) LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: Error: Object 'nm' is unknown, try 'nmcli help'. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1485558/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1485558] Re: NetworkManager breaks vboxnet* connections since 15.04, worked in 14.04 and 14.10
I tried to move away all connections in /etc/NetworkManager/system-connections/ then restart network-manager, just in case configuration somehow confused it. Problem still happens. Thank you for your attention. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1485558 Title: NetworkManager breaks vboxnet* connections since 15.04, worked in 14.04 and 14.10 Status in network-manager package in Ubuntu: New Bug description: On an Asus laptop running a freshly installed Ubuntu 15.04 64-bit, nm- applet shows that NetworkManager wants to manage vboxnet0 and vboxnet1. These are created by virtualbox which runs some guest OS inside a VM. On previous Ubuntu releases, network-manager did not try to manage them and there was no problem. # Observed behavior * nm-applet shows spinning animation for a long time, while it is not relevant. Clicking on disconnect in the menu unconfigures the interface which breaks it. * after suspend-resume of the host, vboxnet* lose their correct configurations. vboxnet0 (a host-only interface where virtualbox runs a private dhcp server) gets a different IP address. Looks like https://bugs.launchpad.net/ubuntu/+source/virtualbox/+bug/1460750 but does not feel like a bug in virtualbox. # Expected behavior * Just like in 14.04 and 14.10, these interfaces are just ignored by network-manager and they just work. # Additional information * After reading http://superuser.com/questions/9720/disabling- networkmanager-for-a-specific-interface tried to add these lines to /etc/network/interfaces. Even after restarting network-manager, it has no effect. iface vboxnet0 inet manual iface vboxnet1 inet manual So, reverted the change. * Tried from https://blogs.gnome.org/dcbw/2015/02/16/networkmanager- for-administrators-part-1/ to add in /etc/NetworkManager/conf.d/ a file 50-virtualbox.conf containing the following lines. Even after restarting network-manager, it is ignored. [keyfile] unmanaged-devices=vboxnet0,vboxnet1 * This is not eactly like https://www.virtualbox.org/ticket/13873, I'm not using Vagrant. * Booting to 14.04 or 14.10 (that have been kept intact on the same machine) things just work as expected. * /usr/share/doc/network-manager/NEWS.gz states that 'veth' interfaces are now unmanaged by default to cooperate better with external tools. Should vboxnet* be treated the same ? * This seems on the topic but unclear to me: https://bugzilla.gnome.org/show_bug.cgi?id=731014 Thank you for your attention. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: network-manager 0.9.10.0-4ubuntu15.1 ProcVersionSignature: Ubuntu 3.19.0-25.26-generic 3.19.8-ckt2 Uname: Linux 3.19.0-25-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.2 Architecture: amd64 Date: Mon Aug 17 13:13:04 2015 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2015-08-15 (1 days ago) InstallationMedia: Xubuntu 15.04 Vivid Vervet - Release amd64 (20150422.1) IpRoute: default via 192.168.47.1 dev wlan0 proto static metric 1024 169.254.0.0/16 dev vboxnet0 scope link metric 1000 192.168.47.0/24 dev wlan0 proto kernel scope link src 192.168.47.6 192.168.56.0/24 dev vboxnet0 proto kernel scope link src 192.168.56.102 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true ProcEnviron: LANGUAGE=fr_FR TERM=xterm PATH=(custom, no user) LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: Error: Object 'nm' is unknown, try 'nmcli help'. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1485558/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1485558] [NEW] NetworkManager breaks vboxnet* connections since 15.04, worked in 14.04 and 14.10
Public bug reported: On an Asus laptop running a freshly installed Ubuntu 15.04 64-bit, nm- applet shows that NetworkManager wants to manage vboxnet0 and vboxnet1. These are created by virtualbox which runs some guest OS inside a VM. On previous Ubuntu releases, network-manager did not try to manage them and there was no problem. # Observed behavior * nm-applet shows spinning animation for a long time, while it is not relevant. Clicking on disconnect in the menu unconfigures the interface which breaks it. * after suspend-resume of the host, vboxnet* lose their correct configurations. vboxnet0 (a host-only interface where virtualbox runs a private dhcp server) gets a different IP address. Looks like https://bugs.launchpad.net/ubuntu/+source/virtualbox/+bug/1460750 but does not feel like a bug in virtualbox. # Expected behavior * Just like in 14.04 and 14.10, these interfaces are just ignored by network-manager and they just work. # Additional information * After reading http://superuser.com/questions/9720/disabling- networkmanager-for-a-specific-interface tried to add these lines to /etc/network/interfaces. Even after restarting network-manager, it has no effect. iface vboxnet0 inet manual iface vboxnet1 inet manual So, reverted the change. * Tried from https://blogs.gnome.org/dcbw/2015/02/16/networkmanager-for- administrators-part-1/ to add in /etc/NetworkManager/conf.d/ a file 50-virtualbox.conf containing the following lines. Even after restarting network-manager, it is ignored. [keyfile] unmanaged-devices=vboxnet0,vboxnet1 * This is not eactly like https://www.virtualbox.org/ticket/13873, I'm not using Vagrant. * Booting to 14.04 or 14.10 (that have been kept intact on the same machine) things just work as expected. * /usr/share/doc/network-manager/NEWS.gz states that 'veth' interfaces are now unmanaged by default to cooperate better with external tools. Should vboxnet* be treated the same ? * This seems on the topic but unclear to me: https://bugzilla.gnome.org/show_bug.cgi?id=731014 Thank you for your attention. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: network-manager 0.9.10.0-4ubuntu15.1 ProcVersionSignature: Ubuntu 3.19.0-25.26-generic 3.19.8-ckt2 Uname: Linux 3.19.0-25-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.2 Architecture: amd64 Date: Mon Aug 17 13:13:04 2015 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2015-08-15 (1 days ago) InstallationMedia: Xubuntu 15.04 Vivid Vervet - Release amd64 (20150422.1) IpRoute: default via 192.168.47.1 dev wlan0 proto static metric 1024 169.254.0.0/16 dev vboxnet0 scope link metric 1000 192.168.47.0/24 dev wlan0 proto kernel scope link src 192.168.47.6 192.168.56.0/24 dev vboxnet0 proto kernel scope link src 192.168.56.102 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true ProcEnviron: LANGUAGE=fr_FR TERM=xterm PATH=(custom, no user) LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: Error: Object 'nm' is unknown, try 'nmcli help'. ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug vivid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1485558 Title: NetworkManager breaks vboxnet* connections since 15.04, worked in 14.04 and 14.10 Status in network-manager package in Ubuntu: New Bug description: On an Asus laptop running a freshly installed Ubuntu 15.04 64-bit, nm- applet shows that NetworkManager wants to manage vboxnet0 and vboxnet1. These are created by virtualbox which runs some guest OS inside a VM. On previous Ubuntu releases, network-manager did not try to manage them and there was no problem. # Observed behavior * nm-applet shows spinning animation for a long time, while it is not relevant. Clicking on disconnect in the menu unconfigures the interface which breaks it. * after suspend-resume of the host, vboxnet* lose their correct configurations. vboxnet0 (a host-only interface where virtualbox runs a private dhcp server) gets a different IP address. Looks like https://bugs.launchpad.net/ubuntu/+source/virtualbox/+bug/1460750 but does not feel like a bug in virtualbox. # Expected behavior * Just like in 14.04 and 14.10, these interfaces are just ignored by network-manager and they just work. # Additional information * After reading http://superuser.com/questions/9720/disabling- networkmanager-for-a-specific-interface tried to add these lines to /etc/network/interfaces. Even after restarting network-manager, it has no effect. iface vboxnet0 inet
[Touch-packages] [Bug 387692] Re: ext4 - data loss after power failure, and unable to recover
Had the same problem as imperia777 : data intact, error message and unable to fix it, (though no actual power failure). Here's fsck output: e2fsck 1.42.9 (4-Feb-2014) myfsname: recovering journal Superblock needs_recovery flag is clear, but journal has data. Run journal anyway? yes fsck.ext4: unable to set superblock flags on myfsname Final verdict was: defective storage. Data was transferred to a new storage medium with a new filesystem. Problem solved. As additional check, we made a copy from the defective medium to another and observed that fsck could run flawlessly on the sane medium. Looks like fsck is extra cautious and checks if every operations indeed happened, which allowed it to spot the trouble. Anyway, to say it again: fsck.ext4: unable to set superblock flags on myfsname meant (at least in my case): change your storage medium. Thank you for your attention. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to e2fsprogs in Ubuntu. https://bugs.launchpad.net/bugs/387692 Title: ext4 - data loss after power failure, and unable to recover Status in e2fsprogs package in Ubuntu: Confirmed Bug description: Ubuntu 9.04 , system is (was) up to date, home partition is encrypted with ecryptfs After a power failure I am unable to access the Ubuntu system, booting drops to busybox. From a live CD : [quote]root@ubuntu:~# fsck -y /dev/sda1 fsck 1.41.4 (27-Jan-2009) e2fsck 1.41.4 (27-Jan-2009) /dev/sda1: recovering journal Superblock needs_recovery flag is clear, but journal has data. Run journal anyway? yes fsck.ext4: unable to set superblock flags on /dev/sda1 [/quote][quote]root@ubuntu:~# fsck /dev/sda1 fsck 1.41.4 (27-Jan-2009) e2fsck 1.41.4 (27-Jan-2009) /dev/sda1: recovering journal Superblock needs_recovery flag is clear, but journal has data. Run journal anywayy? yes fsck.ext4: unable to set superblock flags on /dev/sda1[/quote][quote]root@ubuntu:~# fsck /dev/sda1 fsck 1.41.4 (27-Jan-2009) e2fsck 1.41.4 (27-Jan-2009) /dev/sda1: recovering journal Superblock needs_recovery flag is clear, but journal has data. Run journal anywayy? no Clear journaly? no /dev/sda1: clean, 138871/373152 files, 681246/1492029 blocks root@ubuntu:~# fsck -y /dev/sda1 fsck 1.41.4 (27-Jan-2009) e2fsck 1.41.4 (27-Jan-2009) /dev/sda1: recovering journal Superblock needs_recovery flag is clear, but journal has data. Run journal anyway? yes fsck.ext4: unable to set superblock flags on /dev/sda1[/quote][quote]root@ubuntu:~# fsck /dev/sda1 fsck 1.41.4 (27-Jan-2009) e2fsck 1.41.4 (27-Jan-2009) /dev/sda1: recovering journal Superblock needs_recovery flag is clear, but journal has data. Run journal anywayy? no Clear journaly? yes /dev/sda1 was not cleanly unmounted, check forced. Pass 1: Checking inodes, blocks, and sizes Pass 2: Checking directory structure Pass 3: Checking directory connectivity Pass 4: Checking reference counts Pass 5: Checking group summary information /dev/sda1: * FILE SYSTEM WAS MODIFIED * /dev/sda1: 138871/373152 files (0.2% non-contiguous), 681246/1492029 blocks[/quote][quote]root@ubuntu:~# mount -t ext4 /dev/sda1 /mnt mount: wrong fs type, bad option, bad superblock on /dev/sda1, missing codepage or helper program, or other error In some cases useful info is found in syslog - try dmesg | tail or so root@ubuntu:~# dmesg | tail [ 1894.643462] JBD: recovery failed [ 1894.643468] EXT4-fs: error loading journal. [ 1894.645367] sd 0:0:0:0: [sda] 12582912 512-byte hardware sectors: (6.44 GB/6.00 GiB) [ 1894.645385] sd 0:0:0:0: [sda] Write Protect is off [ 1894.645387] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00 [ 1894.645404] sd 0:0:0:0: [sda] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA [ 1894.645422] sd 0:0:0:0: [sda] 12582912 512-byte hardware sectors: (6.44 GB/6.00 GiB) [ 1894.645432] sd 0:0:0:0: [sda] Write Protect is off [ 1894.645434] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00 [ 1894.645450] sd 0:0:0:0: [sda] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA[/quote][quote]root@ubuntu:~# mke2fs -n /dev/sda1 mke2fs 1.41.4 (27-Jan-2009) Filesystem label= OS type: Linux Block size=4096 (log=2) Fragment size=4096 (log=2) 373152 inodes, 1492029 blocks 74601 blocks (5.00%) reserved for the super user First data block=0 Maximum filesystem blocks=1530920960 46 block groups 32768 blocks per group, 32768 fragments per group 8112 inodes per group Superblock backups stored on blocks: 32768, 98304, 163840, 229376, 294912, 819200, 884736 root@ubuntu:~# e2fsck -b 32768 /dev/sda1 e2fsck 1.41.4 (27-Jan-2009) Superblock needs_recovery flag is clear, but journal has data. Recovery flag not set in backup superblock, so running journal anyway. /dev/sda1: recovering journal Superblock needs_recovery flag is clear, but
[Touch-packages] [Bug 967232] Re: unable to load desktop session in xubuntu precise
Sorry for not answering again. Are there any news on this issue? No news. As written above, I provided users a workaround with a .xsession. That workaround was so effective that I even forgot this bug. Did you already upgrade to 14.04 or do you plan to do so? It is planned and we already know some other improvements it will bring. But we lack time so far. :-) It would be interesting to know if this problem persists or not. I could disable the workaround to see if anything changed. Do you want me to do so ? Not sure I can do it in the following days. Thank you for your attention. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/967232 Title: unable to load desktop session in xubuntu precise Status in “lightdm” package in Ubuntu: Incomplete Status in “xfce4-session” package in Ubuntu: Incomplete Bug description: Installed Xubuntu Precise beta 1(amd64) in this PC AMD FX 8120 8-core processor 16GB of RAM ATI HD 5450 ASUS M5A99X-EVO 500 GB HDD TrendNet Atheros Wireless PCI Card And fully updated Xubuntu and for the very first time when i fill in my password it starts to load the desktop and it stops at the point that the only thing i see is the desktop background and the mouse i can move all over the place What i do is hit Ctrl+F1 and export DISPLAY=:0.0 and then some commands like xfce4-session xfce4-panel and then Ctrl+F7 and the desktops started to load with panels and stuff. This bug is very important because it won't let me access my desktop. I cannot take a screenshot btw, maybe with my cellphone ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: xfce4-session 4.8.3-0ubuntu2 ProcVersionSignature: Ubuntu 3.2.0-20.32-generic 3.2.12 Uname: Linux 3.2.0-20-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 1.95-0ubuntu1 Architecture: amd64 Date: Wed Mar 28 12:30:55 2012 EcryptfsInUse: Yes InstallationMedia: Xubuntu 12.04 Precise Pangolin - Beta amd64 (20120228) ProcEnviron: TERM=xterm LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: xfce4-session UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 1.95-0ubuntu1 Architecture: amd64 DistroRelease: Ubuntu 12.04 EcryptfsInUse: Yes InstallationMedia: Xubuntu 12.04 Precise Pangolin - Beta amd64 (20120228) NonfreeKernelModules: fglrx Package: xfce4-session 4.8.3-0ubuntu2 PackageArchitecture: amd64 ProcEnviron: TERM=xterm LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 3.2.0-20.32-generic 3.2.12 Tags: precise Uname: Linux 3.2.0-20-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/967232/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 594674] Re: Trash is not shown on --bind mounted filesystems
Hello simionbcn. Thank you for your participation. Can you elaborate ? Several setups were discussed, we can't guess what is yours. What is your filesystem setup ? Your version of Ubuntu, of involved packages ? What steps have you performed ? Such information helps a lot. Thanks. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/594674 Title: Trash is not shown on --bind mounted filesystems Status in The G Library - GLib: Confirmed Status in Nautilus: Invalid Status in “glib2.0” package in Ubuntu: Triaged Status in “nautilus” package in Ubuntu: Triaged Bug description: Binary package hint: nautilus I have a secondary partition, mounted at /media/data, from which I --bind mount a directory to be my ~/Videos using fstab. When I use Nautilus to navigate into ~/Videos and move a file into trash (either using Delete or by dragging or whatever), the file vanishes, but does not show up when I open Trash from the side panel. If I press Ctrl+H to see hidden files I find a ~/Videos/.Trash-1000 directory, under which the file has been moved. Navigating to /media/data/path/Videos and removing the file from there moves it under /media/data/.Trash-1000, from where it correctly shows up in the trash can. ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: nautilus 1:2.30.1-0ubuntu1 ProcVersionSignature: Ubuntu 2.6.32-22.36-generic 2.6.32.11+drm33.2 Uname: Linux 2.6.32-22-generic x86_64 Architecture: amd64 Date: Tue Jun 15 19:03:29 2010 InstallationMedia: Ubuntu 10.04 Lucid Lynx - Release Candidate amd64 (20100419.1) ProcEnviron: LANG=en_US.utf8 SHELL=/bin/bash SourcePackage: nautilus To manage notifications about this bug go to: https://bugs.launchpad.net/glib/+bug/594674/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 594674] Re: Trash is not shown on --bind mounted filesystems
Thank you simonbcn for these interesting additions (not saying I can do anything about it, but a nautilus developer may pick that as valuable hints about what's wrong). -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/594674 Title: Trash is not shown on --bind mounted filesystems Status in The G Library - GLib: Confirmed Status in Nautilus: Invalid Status in “glib2.0” package in Ubuntu: Triaged Status in “nautilus” package in Ubuntu: Triaged Bug description: Binary package hint: nautilus I have a secondary partition, mounted at /media/data, from which I --bind mount a directory to be my ~/Videos using fstab. When I use Nautilus to navigate into ~/Videos and move a file into trash (either using Delete or by dragging or whatever), the file vanishes, but does not show up when I open Trash from the side panel. If I press Ctrl+H to see hidden files I find a ~/Videos/.Trash-1000 directory, under which the file has been moved. Navigating to /media/data/path/Videos and removing the file from there moves it under /media/data/.Trash-1000, from where it correctly shows up in the trash can. ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: nautilus 1:2.30.1-0ubuntu1 ProcVersionSignature: Ubuntu 2.6.32-22.36-generic 2.6.32.11+drm33.2 Uname: Linux 2.6.32-22-generic x86_64 Architecture: amd64 Date: Tue Jun 15 19:03:29 2010 InstallationMedia: Ubuntu 10.04 Lucid Lynx - Release Candidate amd64 (20100419.1) ProcEnviron: LANG=en_US.utf8 SHELL=/bin/bash SourcePackage: nautilus To manage notifications about this bug go to: https://bugs.launchpad.net/glib/+bug/594674/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1193236] Re: Couldn't connect to accessibility bus: Failed to connect to socket /tmp/dbus-*
The error message: * is reproducible always, * on trusty * with zenity, abiword, gitg, gnome-calculator, probably with other or even all gtk3-apps, too. I have tested only a handful and all exhibit this behavior. Zenity is mentioned in bug #1326099 . For example: ** (zenity:10455): WARNING **: Couldn't connect to accessibility bus: Failed to connect to socket /tmp/dbus-isvBHBGV9Q: Connexion refusée It seems to have no other side effect as the applications work fine. But this noise in stderr causes troubles, for example in cron jobs. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to at-spi2-core in Ubuntu. https://bugs.launchpad.net/bugs/1193236 Title: Couldn't connect to accessibility bus: Failed to connect to socket /tmp/dbus-* Status in Assistive Technology Service Provider Interface: New Status in “at-spi2-core” package in Ubuntu: Confirmed Status in “at-spi2-core” package in Debian: Confirmed Bug description: Since a few days, xsession-errors is fullfilled by that kind of errors: ** (nautilus:22621): WARNING **: Couldn't connect to accessibility bus: Failed to connect to socket /tmp/dbus-uUkE07qdBK: Connection refused ** (gedit:22640): WARNING **: Couldn't connect to accessibility bus: Failed to connect to socket /tmp/dbus-uUkE07qdBK: Connection refused Similar errors are reported all over the net, but Debian have tried to fix it already: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=702517 But some other devs seems to blame an atk-bridge: https://groups.google.com/forum/#!topic/yad-common/nYP0RutlxNA And some others suggest a dbus/gdbus race; the good thing is that seems not disturbing that much the system. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: libgdk-pixbuf2.0-0 2.28.1-1ubuntu2 ProcVersionSignature: Ubuntu 3.9.0-6.14-generic 3.9.6 Uname: Linux 3.9.0-6-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.10.2-0ubuntu1 Architecture: i386 Date: Fri Jun 21 08:35:40 2013 MarkForUpload: True SourcePackage: gdk-pixbuf UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/at-spi/+bug/1193236/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
