[Desktop-packages] [Bug 1752091] Re: gvfsd-metadata[1703]: g_udev_device_has_property: assertion 'G_UDEV_IS_DEVICE (device)' failed
Still observed here. This floods systemd's log, around 10 messages per second. At first glance, the commit mentioned above seem relevant. Even if a proper fix takes time to be incorporated, I'd be happy with a workaround, but am clueless where to start man gvfds-metadata offers no relevant option. Killing gvfsd-metadata only yields another one. Parent process is systemd. Disabling /usr/lib/systemd/user/gvfs- metadata.service will probably break file managers, filesystem mounts and the like. Any hint appreciated. Thanks. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1752091 Title: gvfsd-metadata[1703]: g_udev_device_has_property: assertion 'G_UDEV_IS_DEVICE (device)' failed Status in gvfs: Fix Released Status in gvfs package in Ubuntu: Confirmed Bug description: I have no idea about the package to blame: gvfs/udev/kernel ? This is now logged: gvfsd-metadata[1703]: g_udev_device_has_property: assertion 'G_UDEV_IS_DEVICE (device)' failed ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gvfs 1.35.91-1ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-11.12-generic 4.15.5 Uname: Linux 4.15.0-11-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: GNOME Date: Tue Feb 27 14:21:10 2018 EcryptfsInUse: Yes ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gvfs UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gvfs/+bug/1752091/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-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 Desktop 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/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 979959] Re: "gnome-control-center display" crashes if no RANDR extension
Makes sense. Besides, I've been using XFCE for a long time now, so have not had any visibility whether this bug still occurs with Gnome. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/979959 Title: "gnome-control-center display" crashes if no RANDR extension Status in gnome-control-center package in Ubuntu: Invalid Bug description: The problem can be reproduced at will by clicking on display settings icon, but also by typing this : gnome-control-center display A window appears, complains "Could not get screen information" "RANDR extension is not present". $ LC_ALL=C gnome-control-center display (gnome-control-center:13078): Gtk-WARNING **: GtkTable does not have a property called expand (gnome-control-center:13078): Gtk-WARNING **: GtkTable does not have a property called fill (gnome-control-center:13078): Gtk-WARNING **: GtkTable does not have a property called position (gnome-control-center:13078): GLib-GObject-WARNING **: invalid (NULL) pointer instance (gnome-control-center:13078): GLib-GObject-CRITICAL **: g_signal_connect_data: assertion `G_TYPE_CHECK_INSTANCE (instance)' failed Erreur de segmentation (core dumped) ProblemType: Crash DistroRelease: Ubuntu 12.04 Package: gnome-control-center 1:3.4.0-0ubuntu6 ProcVersionSignature: Ubuntu 3.2.0-23.36-generic 3.2.14 Uname: Linux 3.2.0-23-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.0.1-0ubuntu2 Architecture: amd64 Date: Thu Apr 12 16:41:38 2012 ExecutablePath: /usr/bin/gnome-control-center InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta amd64 (20120410) ProcCmdline: gnome-control-center --overview ProcEnviron: PATH=(custom, user) LANG=fr_FR.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7fb28dcb7c07 : mov 0x18(%rdi),%rbp PC (0x7fb28dcb7c07) ok source "0x18(%rdi)" (0x0018) not located in a known VMA region (needed readable region)! destination "%rbp" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: gnome-control-center StacktraceTop: gtk_widget_size_allocate () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /usr/lib/libgnome-control-center.so.1 g_cclosure_marshal_VOID__BOXEDv () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: gnome-control-center crashed with SIGSEGV in gtk_widget_size_allocate() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo usr_lib_gnome-control-center: activity-log-manager-control-center 0.9.4-0ubuntu3 deja-dup22.0-0ubuntu2 gnome-bluetooth 3.2.2-0ubuntu5 indicator-datetime 0.3.94-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/979959/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-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 Desktop 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/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-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 Desktop 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/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-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 Desktop 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/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-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 Desktop 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/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-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 Desktop 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/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-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
[Desktop-packages] [Bug 1405209] Re: Thunderbird crashes on IMAP search for folder in NS_MsgHashIfNecessary.
Hello gf. Yes you can close the ticket.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to thunderbird in Ubuntu.
https://bugs.launchpad.net/bugs/1405209
Title:
Thunderbird crashes on IMAP search for folder in
NS_MsgHashIfNecessary.
Status in thunderbird package in Ubuntu:
Incomplete
Bug description:
# Context
On a Ubuntu 12.04 machine used by several users (two main users),
Thunderbird has been used for years on various WiFi networks. Each
user has his Unix account, one thunderbird profile, using IMAP server.
Users don't connect to same e-mail provider.
Yesterday evening, we moved to a usual alternate location with its own
wifi.
# Observed behavior
Now one user has thunderbird crashing whenever it searches for folders, and
that happens at startup, before user has a change to click anywhere. Thundebird
only shows a window, in status bar a message like "looking for folders" with a
progress bar at about 10-15%, then crashes.
The user can access their mailbox normally via a webmail supplied by the IMAP
provider. Folder names look normal there.
Other user is totally unaffected by the problem.
Reproducible: always.
Expected behavior it obvious: no crash, user can browse their folders.
# Additional information
* Safe mode does not change anything, whatever the boxes checked
(addons, toolbars).
* Cutting off internet access allows to start thunderbird without
immediate crash.
* Changing these settings to false (they were true) is not enough to prevent
crashes on startup with network access.
user_pref("mail.server.server1.login_at_startup", false);
user_pref("mail.startup.enabledMailCheckOnce", false);
* In preference, unticking "sync messages for this account" does not
prevent crash on startup.
# Debug information
Thunderbird crash reporter worked. I clicked yes when offered and typed a
short sentence. This way I have submitted 21 crash reports today.
Following https://wiki.ubuntu.com/MozillaTeam/Bugs I got stack traces that I
can attach.
package is 1:31.3.0+build1-0ubuntu0.12.04.1
I don't know if source matches http://dxr.mozilla.org/comm-
central/source/mailnews/base/util/nsMsgUtils.cpp, but from the top of
the stack tracs it looks like MsgHashIfNecessary() was supplied with
an empty string, which may be the cause of crash.
#0 NS_MsgHashIfNecessary (name=...) at
/build/buildd/thunderbird-31.3.0+build1/mailnews/base/util/nsMsgUtils.cpp:446
lastIndex = -1
illegalCharacterIndex =
hashedname = "\000`\271\377\377\377\177\000"
keptLength =
Crash ID: bp-0744c6e8-13b6-4ff1-85ea-083022141223
Crash ID: bp-0f5ff99f-ae29-4300-b14c-5d3ec2141223
Crash ID: bp-1bc04187-d16c-428c-b226-02fa42141223
Crash ID: bp-1f928c7d-822b-43ad-9893-96c4f2141223
Crash ID: bp-2cb3dc60-f364-4836-82a1-1a86f2141223
Crash ID: bp-2e400b3c-aeac-48ec-8f18-33fbe2141223
Crash ID: bp-33c39df8-2565-4af4-bc57-d2ced2141223
Crash ID: bp-3e9b7666-1a2f-409e-beff-996e62141223
Crash ID: bp-68e88235-dc96-4b01-a803-9808f2141223
Crash ID: bp-71e10918-f8c5-41a6-a41f-91eca2141223
Crash ID: bp-9ee0e84a-217a-417e-b78c-501d82141223
Crash ID: bp-a173490f-5d76-4303-9e74-e72812141223
Crash ID: bp-b4f12af0-eb61-43d2-9939-ac11a2141223
Crash ID: bp-b5e9cf00-7da8-4dda-b172-964082141223
Crash ID: bp-b96e3d2c-dbaf-473e-b628-ba4f12141223
Crash ID: bp-bb1815ce-bd07-4809-9971-614ee2141223
Crash ID: bp-c42a1d6c-102e-4eee-abc6-08f0d2141223
Crash ID: bp-c9aa9ffc-183e-437d-b534-1a9c12141223
Crash ID: bp-d916ad64-68ae-4823-8d38-4f3912141223
Crash ID: bp-dc99e352-05ba-4819-95bc-0bd502141223
Crash ID: bp-e2d83623-5d39-4480-add2-ea8d72141223
lsb_release -rd
Description: Ubuntu 12.04.5 LTS
Release: 12.04
LC_ALL=C apt-cache policy thunderbird
thunderbird:
Installed: 1:31.3.0+build1-0ubuntu0.12.04.1
Candidate: 1:31.3.0+build1-0ubuntu0.12.04.1
Version table:
*** 1:31.3.0+build1-0ubuntu0.12.04.1 0
500 http://fr.archive.ubuntu.com/ubuntu/ precise-updates/main amd64
Packages
500 http://security.ubuntu.com/ubuntu/ precise-security/main amd64
Packages
100 /var/lib/dpkg/status
11.0.1+build1-0ubuntu2 0
500 http://fr.archive.ubuntu.com/ubuntu/ precise/main amd64 Packages
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: thunderbird 1:31.3.0+build1-0ubuntu0.12.04.1
ProcVersionSignature: Ubuntu 3.2.0-74.109-generic 3.2.64
Uname: Linux 3.2.0-74-generic x86_64
NonfreeKernelModules: nvidia
AddonCompatCheckDisabled: False
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
ApportVersion: 2.0.1-0ubuntu17.8
Architecture: amd64
ArecordDevices:
List of CAPTURE Hardware Devices
card 0: Intel [HDA Intel], device 0: ALC663 Analog [ALC663 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
BuildID: 20141128200729
CRDA:
[Desktop-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 Desktop 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/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-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 Desktop 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/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-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 Desktop 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/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-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 Desktop 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
[Desktop-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 Desktop 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: BOOT_IMAGE=/boot/vmlinuz-4.4.0-7-generic.efi.signed
[Desktop-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 Desktop 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/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-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 Desktop 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/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-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 Desktop 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
[Desktop-packages] [Bug 1568604] Re: Mouse cursor lost when unlocking with Intel graphics
Bug observed on Asus n551jk using nouveau driver with latest updates applied. Suspend not needed, locking is enough. Ctrl-Alt-F1 then Ctrl-Alt-F7 works around, until next lock. Thank you for your attention. LC_ALL=C lshw -c video 2>/dev/null | grep configuration configuration: driver=nouveau latency=0 configuration: driver=i915 latency=0 lspci -nn | egrep -i '(vga|3d)' 00:02.0 VGA compatible controller [0300]: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06) 01:00.0 3D controller [0302]: NVIDIA Corporation GM107M [GeForce GTX 850M] [10de:1391] (rev a2) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu. https://bugs.launchpad.net/bugs/1568604 Title: Mouse cursor lost when unlocking with Intel graphics Status in elementary OS: Confirmed Status in xf86-video-intel: Confirmed Status in xserver-xorg-video-intel package in Ubuntu: Fix Released Status in xserver-xorg-video-intel source package in Xenial: Confirmed Status in xserver-xorg-video-intel package in Debian: Fix Released Bug description: [SRU for Ubuntu 16.04] Package (yakkety): xserver-xorg-video-intel 2:2.99.917+git20160706-1ubuntu1 Current (xenial): xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1 [Impact] Mouse cursor is no longer visible after VT-switch for systems with Intel graphics. Switching VTs again may cause the cursor to become visible again. - Changing to vt1 then back to vt7 (ctrl+alt+f1 then ctrl+alt+f7) This is often observed in systems that lock the session and return to the greeter (including at least Xubuntu, Ubuntu Mate, and elementary OS). [Test Case] (Requires a lightdm-based screen locking solution) 1. Start a new session. 2. Lock your screen. 2a. You are redirected to the lightdm greeter. 3. Login/Unlock your session. 4. Cursor is no longer visible. [Debian Changelog (since 2:2.99.917+git20160325-1ubuntu1)] xserver-xorg-video-intel (2:2.99.917+git20160706-1ubuntu1) yakkety; urgency=medium * Merge from Debian. xserver-xorg-video-intel (2:2.99.917+git20160706-1) unstable; urgency=medium * New upstream snapshot. * fix-fd-leak-when-intel-scrn-create-fails.diff, sna-let-modesetting- handle-gen9+.diff: Dropped as the fallback to modesetting will be fully handled in the xserver. * .docs: Include a minimal xorg.conf. xserver-xorg-video-intel (2:2.99.917+git20160522-1ubuntu1) yakkety; urgency=medium * Merge from Debian. * install-dri3info.diff: Install dri3info with the driver, add libxcomposite-dev to build-depends. xserver-xorg-video-intel (2:2.99.917+git20160522-1) unstable; urgency=medium * New upstream snapshot. (Closes: #823116) * fix-fd-leak-when-intel-scrn-create-fails.diff: Fix a failure falling back on another driver when scrn create fails. [Regression Potential] Regression potential here seems minimal. However, as seen in the above Debian changelog, we have a new snapshot which includes several changes since March 25. === [Original Report] Cursor is visible at unlock screen either after returning from suspend or just locking. After unlocking screen cursor is invisible. Changing to vt1 then back to vt7 (ctrl+alt+f1 then ctrl+alt+f7) cursor returns no matter if you suspend or sleep, to swap or disk when you return from it, the mouse cursor is missing.you can still move the mouse and you can see (because it highlights the window) as you move it around. But the cursor is not displayed on the screen. i am using a lenovo W540 laptop. I downloaded the latest beta on april 8 2016. this is xubuntu using the xfce window manager. the cursor does return if i log off and log back in, but that actually defeats the purpose of going to sleep. --- ApportVersion: 2.20.1-0ubuntu1 Architecture: amd64 DistroRelease: Ubuntu 16.04 InstallationDate: Installed on 2016-04-08 (2 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160323) NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia Package: light-locker 1.7.0-2ubuntu1 PackageArchitecture: amd64 ProcEnviron: LANGUAGE=en_US TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6 Tags: xenial Uname: Linux 4.4.0-18-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/elementaryos/+bug/1568604/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-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 Desktop 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,
[Desktop-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 Desktop 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.
[Desktop-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 Desktop 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, includi
[Desktop-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 Desktop 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:
[Desktop-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 Desktop 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 version.libgl1-mesa-glx:
[Desktop-packages] [Bug 1556960] Re: Cannot install nvidia driver using software-properties-gtk. package nvidia-361 361.28-0ubuntu1 failed to install/upgrade: subprocess installed post-installation sc
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 Desktop Packages, which is subscribed to nvidia-graphics-drivers-361 in Ubuntu. https://bugs.launchpad.net/bugs/1556960 Title: Cannot install nvidia driver using software-properties-gtk. package nvidia-361 361.28-0ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 255 Status in nvidia-graphics-drivers-361 package in Ubuntu: New Bug description: In trying a workaround for https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1547077 tried once again to install nVidia proprietary driver using software-properties- gtk. Observed: crash report window appears, software-properties-gtk appears to cancel the installation and rollback. This is at least the third time and bug report in a few weeks (not trying to complain, just reporting), details in https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1547077. especially https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1547077/comments/41 https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1547077/comments/42 The glyph bug impact the very process of reporting this as the semi- workaround I use does not work for everything. For example, there's currently no workaround for the context menu in firefox. Thank you for your attention. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: nvidia-361 361.28-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-12.28-generic 4.4.4 Uname: Linux 4.4.0-12-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 Date: Mon Mar 14 14:48:59 2016 ErrorMessage: subprocess installed post-installation script returned error exit status 255 InstallationDate: Installed on 2016-02-03 (39 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160203) RelatedPackageVersions: dpkg 1.18.4ubuntu1 apt 1.2.4 SourcePackage: nvidia-graphics-drivers-361 Title: package nvidia-361 361.28-0ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 255 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-361/+bug/1556960/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1553554] Re: Selecting nvidia driver using software-properties-gtk yields package nvidia-361 361.28-0ubuntu1 failed to install/upgrade: subprocess installed post-installation s
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 Desktop Packages, which is subscribed to nvidia-graphics-drivers-361 in Ubuntu. https://bugs.launchpad.net/bugs/1553554 Title: Selecting nvidia driver using software-properties-gtk yields package nvidia-361 361.28-0ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 30 Status in nvidia-graphics-drivers-361 package in Ubuntu: Triaged Bug description: Similar to https://bugs.launchpad.net/ubuntu/+source/bbswitch/+bug/1552108 https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-352/+bug/1552109 This happened when trying a workaround to https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1547077 ProblemType: Package DistroRelease: Ubuntu 16.04 Package: nvidia-361 361.28-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-9.24-generic 4.4.3 Uname: Linux 4.4.0-9-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 Date: Sat Mar 5 19:23:21 2016 ErrorMessage: subprocess installed post-installation script returned error exit status 30 InstallationDate: Installed on 2016-02-03 (30 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160203) RelatedPackageVersions: dpkg 1.18.4ubuntu1 apt 1.2.4 SourcePackage: nvidia-graphics-drivers-361 Title: package nvidia-361 361.28-0ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 30 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-361/+bug/1553554/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-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 Desktop 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 PackageArchitecture:
[Desktop-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 Desktop 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
[Desktop-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 libjpe
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 Desktop 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/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-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 libj
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 Desktop 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/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-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 libjpe
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 Desktop 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
[Desktop-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 Desktop 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
[Desktop-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 Desktop 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
[Desktop-packages] [Bug 1557393] Re: Runaway emacs24 process (100% of one CPU core).
Sent SIGTERM (15). Observed: no effect. Sent SIGHUP (1). Observed: process disappeared. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to emacs24 in Ubuntu. https://bugs.launchpad.net/bugs/1557393 Title: Runaway emacs24 process (100% of one CPU core). Status in emacs24 package in Ubuntu: New Bug description: Context: Use emacs. Close graphical session. Reproducible? Not tried. Observed: emacs process eating as much as one CPU core as it could. Expected: when session is closed, emacs process quits. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: emacs24 24.5+1-1ubuntu7 ProcVersionSignature: Ubuntu 4.4.0-12.28-generic 4.4.4 Uname: Linux 4.4.0-12-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 CurrentDesktop: XFCE Date: Tue Mar 15 10:21:20 2016 ExecutablePath: /usr/bin/emacs24-x InstallationDate: Installed on 2016-02-03 (40 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160203) SourcePackage: emacs24 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/emacs24/+bug/1557393/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1557393] [NEW] Runaway emacs24 process (100% of one CPU core).
Public bug reported: Context: Use emacs. Close graphical session. Reproducible? Not tried. Observed: emacs process eating as much as one CPU core as it could. Expected: when session is closed, emacs process quits. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: emacs24 24.5+1-1ubuntu7 ProcVersionSignature: Ubuntu 4.4.0-12.28-generic 4.4.4 Uname: Linux 4.4.0-12-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 CurrentDesktop: XFCE Date: Tue Mar 15 10:21:20 2016 ExecutablePath: /usr/bin/emacs24-x InstallationDate: Installed on 2016-02-03 (40 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160203) SourcePackage: emacs24 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: emacs24 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to emacs24 in Ubuntu. https://bugs.launchpad.net/bugs/1557393 Title: Runaway emacs24 process (100% of one CPU core). Status in emacs24 package in Ubuntu: New Bug description: Context: Use emacs. Close graphical session. Reproducible? Not tried. Observed: emacs process eating as much as one CPU core as it could. Expected: when session is closed, emacs process quits. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: emacs24 24.5+1-1ubuntu7 ProcVersionSignature: Ubuntu 4.4.0-12.28-generic 4.4.4 Uname: Linux 4.4.0-12-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 CurrentDesktop: XFCE Date: Tue Mar 15 10:21:20 2016 ExecutablePath: /usr/bin/emacs24-x InstallationDate: Installed on 2016-02-03 (40 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160203) SourcePackage: emacs24 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/emacs24/+bug/1557393/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-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 Desktop 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
[Desktop-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 Desktop 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
[Desktop-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 Desktop 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
[Desktop-packages] [Bug 1307176] Re: Resolution limited to 1024x768
> gouri, Invalid fits better over Won't Fix as defined in https://wiki.ubuntu.com/Bugs/Status . Okay because of > "What is the appropriate status if the original reporter later says the issue > no longer exists but the related changelog does not note a fix? > >See the first point under "Invalid", the report does not have sufficient > information. " -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-ati in Ubuntu. https://bugs.launchpad.net/bugs/1307176 Title: Resolution limited to 1024x768 Status in xserver-xorg-video-ati package in Ubuntu: Invalid Bug description: Bug reported with xdiagnose. # Summary On installing Ubuntu 13.10 or 14.04 on a NTA3500 nettop with a VGA monitor HP vs19e (native resolution 1280x1024), a resolution of 1024x768 is obtained. The bug is not that the correct resolution cannot be obtained at all (there's a workaround below with xrandr) but about the fact that is is not automatically selected despite good EDID data available from monitor. # Details Machine has two video output ports: HDMI and DVI. No monitor is plugged on HDMI. Monitor used is plugged on DVI with a DVI-to-VGA passive adapter. The open-source driver is used. xrandr and graphical tools don't offer more than 1024x768 on this screen. xrandr output: Screen 0: minimum 320 x 200, current 1024 x 768, maximum 8192 x 8192 DVI-0 connected 1024x768+0+0 (normal left inverted right x axis y axis) 376mm x 301mm 1280x1024 60.0 + 75.0 1152x864 75.0 1024x768 75.1 70.1 60.0* 832x62474.6 800x60072.2 75.0 60.3 640x48075.0 72.8 60.0 720x40070.1 HDMI-0 disconnected (normal left inverted right x axis y axis) VGA-0 connected 1024x768+0+0 (normal left inverted right x axis y axis) 0mm x 0mm 1024x768 60.0* 800x60060.3 56.2 848x48060.0 640x48059.9 # EDID information sudo get-edid | parse-edid This is read-edid version 3.0.1. Prepare for some fun. Attempting to use i2c interface Looks like no busses have an EDID. Sorry! Attempting to use the classical VBE interface Performing real mode VBE call Interrupt 0x10 ax=0x4f00 bx=0x0 cx=0x0 Function supported Call successful VBE version 300 VBE string at 0xc01cc "AMD ATOMBIOS" VBE/DDC service about to be called Report DDC capabilities Performing real mode VBE call Interrupt 0x10 ax=0x4f15 bx=0x0 cx=0x0 Function supported Call successful Monitor and video card combination does not support DDC1 transfers Monitor and video card combination supports DDC2 transfers 0 seconds per 128 byte EDID block transfer Screen is not blanked during DDC transfer Reading next EDID block VBE/DDC service about to be called Read EDID Performing real mode VBE call Interrupt 0x10 ax=0x4f15 bx=0x1 cx=0x0 Function supported Call successful Checksum Correct Section "Monitor" Identifier "HP vs19e" ModelName "HP vs19e" VendorName "HWP" # Monitor Manufactured week 23 of 2006 # EDID version 1.3 # Analog Display DisplaySize 380 300 Gamma 2.20 Option "DPMS" "true" Horizsync 30-83 VertRefresh 50-76 # Maximum pixel clock is 140MHz #Not giving standard mode: 1280x1024, 60Hz Modeline"Mode 0" 108.00 1280 1328 1440 1688 1024 1025 1028 1066 +hsync +vsync EndSection Looks like VBE was successful. Have a good day. # Additional information, comparison Same monitor was used on various machines, bug only happens on this machine. With no change to hardware, when using ATI proprietary driver, 1280x1024 is available by default (no need for a workaround). # Workaround A similar problem was reported on http://askubuntu.com/questions/207716/ubuntu-12-10-resolution-stuck- at-1024x768-using-open-source-radeon-driver . The following sequence allows to get a proper resolution with open- source driver once. cvt 1280 1024 60 xrandr --newmode "1280x1024_60.00" 109.00 1280 1368 1496 1712 1024 1027 1034 1063 -hsync +vsync xrandr --addmode VGA-0 1280x1024_60.00 xrandr --output DVI-0 --off --output VGA-0 --mode 1280x1024_60.00 # Offer for help What can I do to improve Ubuntu so that other users (including me when I do a clean Ubuntu install in the future) automatically get correct resolution ? How to diagnose the reason why the correct resolution as reported by the monitor is not used by open-source driver ? Thank you for your at
[Desktop-packages] [Bug 1307176] Re: Resolution limited to 1024x768
Hello Christopher @penalvch, you're the Jon Skeet of launchpad :-). Honestly, I don't care about a backport. The machine is currently running Debian actually. Had I needed Ubuntu, I would have used 16.04 anyway. So, I'll mark this as invalid as you request (I would not have considered "invalid", rather "wontfix"). What's the rationale for "invalid" here? Thanks. ** Changed in: xserver-xorg-video-ati (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-ati in Ubuntu. https://bugs.launchpad.net/bugs/1307176 Title: Resolution limited to 1024x768 Status in xserver-xorg-video-ati package in Ubuntu: Invalid Bug description: Bug reported with xdiagnose. # Summary On installing Ubuntu 13.10 or 14.04 on a NTA3500 nettop with a VGA monitor HP vs19e (native resolution 1280x1024), a resolution of 1024x768 is obtained. The bug is not that the correct resolution cannot be obtained at all (there's a workaround below with xrandr) but about the fact that is is not automatically selected despite good EDID data available from monitor. # Details Machine has two video output ports: HDMI and DVI. No monitor is plugged on HDMI. Monitor used is plugged on DVI with a DVI-to-VGA passive adapter. The open-source driver is used. xrandr and graphical tools don't offer more than 1024x768 on this screen. xrandr output: Screen 0: minimum 320 x 200, current 1024 x 768, maximum 8192 x 8192 DVI-0 connected 1024x768+0+0 (normal left inverted right x axis y axis) 376mm x 301mm 1280x1024 60.0 + 75.0 1152x864 75.0 1024x768 75.1 70.1 60.0* 832x62474.6 800x60072.2 75.0 60.3 640x48075.0 72.8 60.0 720x40070.1 HDMI-0 disconnected (normal left inverted right x axis y axis) VGA-0 connected 1024x768+0+0 (normal left inverted right x axis y axis) 0mm x 0mm 1024x768 60.0* 800x60060.3 56.2 848x48060.0 640x48059.9 # EDID information sudo get-edid | parse-edid This is read-edid version 3.0.1. Prepare for some fun. Attempting to use i2c interface Looks like no busses have an EDID. Sorry! Attempting to use the classical VBE interface Performing real mode VBE call Interrupt 0x10 ax=0x4f00 bx=0x0 cx=0x0 Function supported Call successful VBE version 300 VBE string at 0xc01cc "AMD ATOMBIOS" VBE/DDC service about to be called Report DDC capabilities Performing real mode VBE call Interrupt 0x10 ax=0x4f15 bx=0x0 cx=0x0 Function supported Call successful Monitor and video card combination does not support DDC1 transfers Monitor and video card combination supports DDC2 transfers 0 seconds per 128 byte EDID block transfer Screen is not blanked during DDC transfer Reading next EDID block VBE/DDC service about to be called Read EDID Performing real mode VBE call Interrupt 0x10 ax=0x4f15 bx=0x1 cx=0x0 Function supported Call successful Checksum Correct Section "Monitor" Identifier "HP vs19e" ModelName "HP vs19e" VendorName "HWP" # Monitor Manufactured week 23 of 2006 # EDID version 1.3 # Analog Display DisplaySize 380 300 Gamma 2.20 Option "DPMS" "true" Horizsync 30-83 VertRefresh 50-76 # Maximum pixel clock is 140MHz #Not giving standard mode: 1280x1024, 60Hz Modeline"Mode 0" 108.00 1280 1328 1440 1688 1024 1025 1028 1066 +hsync +vsync EndSection Looks like VBE was successful. Have a good day. # Additional information, comparison Same monitor was used on various machines, bug only happens on this machine. With no change to hardware, when using ATI proprietary driver, 1280x1024 is available by default (no need for a workaround). # Workaround A similar problem was reported on http://askubuntu.com/questions/207716/ubuntu-12-10-resolution-stuck- at-1024x768-using-open-source-radeon-driver . The following sequence allows to get a proper resolution with open- source driver once. cvt 1280 1024 60 xrandr --newmode "1280x1024_60.00" 109.00 1280 1368 1496 1712 1024 1027 1034 1063 -hsync +vsync xrandr --addmode VGA-0 1280x1024_60.00 xrandr --output DVI-0 --off --output VGA-0 --mode 1280x1024_60.00 # Offer for help What can I do to improve Ubuntu so that other users (including me when I do a clean Ubuntu install in the future) automatically get correct resolution ? How to diagnose the reason why the correct resolution as reported by the monitor is not used by open-source driver ? Thank you for your attention lsb_release -rd
[Desktop-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 Desktop 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
[Desktop-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 Desktop 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: BOOT_IMAGE=/boot/vmlinuz-4.4.0-7-generic.efi.signed
[Desktop-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
[Desktop-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 Desktop 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
[Desktop-packages] [Bug 1307176] Re: Resolution limited to 1024x768
As requested by @penalvch, tested exact same hardware (nta3500 computer, hp vs19e display) with today's daily live image downloaded from at http://cdimage.ubuntu.com/daily-live/current/xenial-desktop-amd64.iso displayed as "xenial-desktop-amd64.iso 04-Mar-2016 08:29 1.5G" with md5sum 497d36d2b35c8db1c246af281acb36cc and sha1sum e036ed8aa1deedbbbc32bf5b8df0f01ac23e8286 Result: native resolution is correctly automatically detected and selected, no need for any manual workaround (no need for xrandr). So, this bug does not affect 16.04 daily live on this hardware combination. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-ati in Ubuntu. https://bugs.launchpad.net/bugs/1307176 Title: Resolution limited to 1024x768 Status in xserver-xorg-video-ati package in Ubuntu: Incomplete Bug description: Bug reported with xdiagnose. # Summary On installing Ubuntu 13.10 or 14.04 on a NTA3500 nettop with a VGA monitor HP vs19e (native resolution 1280x1024), a resolution of 1024x768 is obtained. The bug is not that the correct resolution cannot be obtained at all (there's a workaround below with xrandr) but about the fact that is is not automatically selected despite good EDID data available from monitor. # Details Machine has two video output ports: HDMI and DVI. No monitor is plugged on HDMI. Monitor used is plugged on DVI with a DVI-to-VGA passive adapter. The open-source driver is used. xrandr and graphical tools don't offer more than 1024x768 on this screen. xrandr output: Screen 0: minimum 320 x 200, current 1024 x 768, maximum 8192 x 8192 DVI-0 connected 1024x768+0+0 (normal left inverted right x axis y axis) 376mm x 301mm 1280x1024 60.0 + 75.0 1152x864 75.0 1024x768 75.1 70.1 60.0* 832x62474.6 800x60072.2 75.0 60.3 640x48075.0 72.8 60.0 720x40070.1 HDMI-0 disconnected (normal left inverted right x axis y axis) VGA-0 connected 1024x768+0+0 (normal left inverted right x axis y axis) 0mm x 0mm 1024x768 60.0* 800x60060.3 56.2 848x48060.0 640x48059.9 # EDID information sudo get-edid | parse-edid This is read-edid version 3.0.1. Prepare for some fun. Attempting to use i2c interface Looks like no busses have an EDID. Sorry! Attempting to use the classical VBE interface Performing real mode VBE call Interrupt 0x10 ax=0x4f00 bx=0x0 cx=0x0 Function supported Call successful VBE version 300 VBE string at 0xc01cc "AMD ATOMBIOS" VBE/DDC service about to be called Report DDC capabilities Performing real mode VBE call Interrupt 0x10 ax=0x4f15 bx=0x0 cx=0x0 Function supported Call successful Monitor and video card combination does not support DDC1 transfers Monitor and video card combination supports DDC2 transfers 0 seconds per 128 byte EDID block transfer Screen is not blanked during DDC transfer Reading next EDID block VBE/DDC service about to be called Read EDID Performing real mode VBE call Interrupt 0x10 ax=0x4f15 bx=0x1 cx=0x0 Function supported Call successful Checksum Correct Section "Monitor" Identifier "HP vs19e" ModelName "HP vs19e" VendorName "HWP" # Monitor Manufactured week 23 of 2006 # EDID version 1.3 # Analog Display DisplaySize 380 300 Gamma 2.20 Option "DPMS" "true" Horizsync 30-83 VertRefresh 50-76 # Maximum pixel clock is 140MHz #Not giving standard mode: 1280x1024, 60Hz Modeline"Mode 0" 108.00 1280 1328 1440 1688 1024 1025 1028 1066 +hsync +vsync EndSection Looks like VBE was successful. Have a good day. # Additional information, comparison Same monitor was used on various machines, bug only happens on this machine. With no change to hardware, when using ATI proprietary driver, 1280x1024 is available by default (no need for a workaround). # Workaround A similar problem was reported on http://askubuntu.com/questions/207716/ubuntu-12-10-resolution-stuck- at-1024x768-using-open-source-radeon-driver . The following sequence allows to get a proper resolution with open- source driver once. cvt 1280 1024 60 xrandr --newmode "1280x1024_60.00" 109.00 1280 1368 1496 1712 1024 1027 1034 1063 -hsync +vsync xrandr --addmode VGA-0 1280x1024_60.00 xrandr --output DVI-0 --off --output VGA-0 --mode 1280x1024_60.00 # Offer for help What can I do to improve Ubuntu so that other users (including me when I do a clean Ubuntu install in the future) automatically get correct resolution ? How to diagnose the reason why the correct
[Desktop-packages] [Bug 1552108] Re: package bbswitch-dkms 0.8-3ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 30
# Analysis: currently running kernel is actually purged >From message in DpkgTerminalLog.txt: > WARNING: missing /lib/modules/4.4.0-7-generic I notice that I'm running uname -a Linux n551jk 4.4.0-7-generic #22-Ubuntu SMP Thu Feb 18 20:50:38 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux Which packages have been removed in between (several days ago). # Summary So, it looks like the problem is: installing nVidia driver seemed to fail because running kernel has its packages purged. # Is it a suitable reason for failure? If driver requires a reboot to work, its install script should target the kernel that will be booted, not the currently running kernel, right? # Good practice? I regularly do: sudo apt-get update ; sudo aptitude upgrade Is is okay or is that a cause of trouble? Should I do something different? Thank you for your attention. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to bbswitch in Ubuntu. https://bugs.launchpad.net/bugs/1552108 Title: package bbswitch-dkms 0.8-3ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 30 Status in bbswitch package in Ubuntu: New Bug description: Installation of package was requested through Ubuntu driver selection GUI. Installation of package was motivated by investigation of bug 1547077. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: bbswitch-dkms 0.8-3ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-7.22-generic 4.4.2 Uname: Linux 4.4.0-7-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 Date: Wed Mar 2 08:14:21 2016 ErrorMessage: subprocess installed post-installation script returned error exit status 30 InstallationDate: Installed on 2016-02-03 (27 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160203) RelatedPackageVersions: dpkg 1.18.4ubuntu1 apt 1.2.4 SourcePackage: bbswitch Title: package bbswitch-dkms 0.8-3ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 30 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bbswitch/+bug/1552108/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-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 Desktop 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 1:7.7+13ubuntu1
[Desktop-packages] [Bug 1552108] [NEW] package bbswitch-dkms 0.8-3ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 30
Public bug reported: Installation of package was requested through Ubuntu driver selection GUI. Installation of package was motivated by investigation of bug 1547077. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: bbswitch-dkms 0.8-3ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-7.22-generic 4.4.2 Uname: Linux 4.4.0-7-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 Date: Wed Mar 2 08:14:21 2016 ErrorMessage: subprocess installed post-installation script returned error exit status 30 InstallationDate: Installed on 2016-02-03 (27 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160203) RelatedPackageVersions: dpkg 1.18.4ubuntu1 apt 1.2.4 SourcePackage: bbswitch Title: package bbswitch-dkms 0.8-3ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 30 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: bbswitch (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package xenial -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to bbswitch in Ubuntu. https://bugs.launchpad.net/bugs/1552108 Title: package bbswitch-dkms 0.8-3ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 30 Status in bbswitch package in Ubuntu: New Bug description: Installation of package was requested through Ubuntu driver selection GUI. Installation of package was motivated by investigation of bug 1547077. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: bbswitch-dkms 0.8-3ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-7.22-generic 4.4.2 Uname: Linux 4.4.0-7-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 Date: Wed Mar 2 08:14:21 2016 ErrorMessage: subprocess installed post-installation script returned error exit status 30 InstallationDate: Installed on 2016-02-03 (27 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160203) RelatedPackageVersions: dpkg 1.18.4ubuntu1 apt 1.2.4 SourcePackage: bbswitch Title: package bbswitch-dkms 0.8-3ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 30 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bbswitch/+bug/1552108/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-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 Desktop 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:
[Desktop-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 Desktop 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
[Desktop-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 Desktop 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
[Desktop-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 Desktop 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
[Desktop-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 Desktop 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
[Desktop-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 Desktop 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
[Desktop-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 Desktop 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
[Desktop-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 Desktop 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
[Desktop-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 Desktop 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
[Desktop-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 Desktop 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
[Desktop-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 Desktop 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
[Desktop-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 Desktop 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:
[Desktop-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 Desktop 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
[Desktop-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 Desktop 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
[Desktop-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 Desktop 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
[Desktop-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 Desktop 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
[Desktop-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 Desktop 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
[Desktop-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 Desktop 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
[Desktop-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 Desktop 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
[Desktop-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 Desktop 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:
[Desktop-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 Desktop 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
[Desktop-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 +
[Desktop-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
[Desktop-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 Desktop 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/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help :
[Desktop-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 Desktop 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/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help :
[Desktop-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 Desktop 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/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help :
[Desktop-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 Desktop 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/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help :
[Desktop-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 Desktop 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/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help :
[Desktop-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 Desktop 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/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help :
[Desktop-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 Desktop 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/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages
[Desktop-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 Desktop 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/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help :
[Desktop-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 Desktop 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/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help :
[Desktop-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 Desktop 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/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help :
[Desktop-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 Desktop 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
[Desktop-packages] [Bug 1512002] Re: Annoying dialog "Authentication is required to change your own user data"
Observed this bug on Xubuntu 16.04 (installed yesterday from http://cdimage.ubuntu.com/xubuntu/daily-live/current/xenial-desktop- amd64.iso.zsync ). New account, quickly customized. Observed after locking screen for the first time with 16.04. Never observed before (on 15.10, 15.04, 14.10 with same hardware), but on those I used xscreensaver because of a bug with lightdm. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to policykit-1-gnome in Ubuntu. https://bugs.launchpad.net/bugs/1512002 Title: Annoying dialog "Authentication is required to change your own user data" Status in policykit-1-gnome package in Ubuntu: Confirmed Bug description: Every few days a dialog pops up saying "Authentication is required to change your own user data" with an entry field for a password. If I type my user's password the dialog will reappear with an empty entry field. If I click on the cross to close the window many times it will be gone, but reappear a few days later. I don't know what this window is for and it makes no difference whether I close it or leave it. I don't use the gnome keyring. This started with Ubuntu 15.04 or maybe with an earlier release, and is still there in Ubuntu 15.10, also on machines I did a fresh install. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/policykit-1-gnome/+bug/1512002/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-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 Desktop 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:
[Desktop-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
[Desktop-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
[Desktop-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 Desktop 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/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-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 Desktop 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/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-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 Desktop 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
[Desktop-packages] [Bug 1428474] [NEW] package nvidia-331 fails to uninstall because nvidia-persistenced is still running
Public bug reported: While trying to get a proper display without high heat on an Optimus laptop, I installed then uninstalled nvidia driver. On uninstalling, apt complained about nvidia-persistenced that was running, and indeed it was true. Manually killing the process allowed to finally uninstall the package. ProblemType: Package DistroRelease: Ubuntu 14.10 Package: nvidia-331 (not installed) ProcVersionSignature: Ubuntu 3.16.0-31.41-generic 3.16.7-ckt5 Uname: Linux 3.16.0-31-generic x86_64 ApportVersion: 2.14.7-0ubuntu8.2 AptOrdering: bumblebee-nvidia: Purge nvidia-331-uvm: Purge nvidia-331: Purge nvidia-opencl-icd-331: Purge Architecture: amd64 Date: Thu Mar 5 06:39:47 2015 DuplicateSignature: package:nvidia-331:(not installed):le sous-processus script post-removal installé a retourné une erreur de sortie d'état 8 ErrorMessage: le sous-processus script post-removal installé a retourné une erreur de sortie d'état 8 InstallationDate: Installed on 2015-03-04 (0 days ago) InstallationMedia: Xubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1) SourcePackage: nvidia-graphics-drivers-331 Title: package nvidia-331 (not installed) failed to install/upgrade: le sous-processus script post-removal installé a retourné une erreur de sortie d'état 8 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: nvidia-graphics-drivers-331 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package utopic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-331 in Ubuntu. https://bugs.launchpad.net/bugs/1428474 Title: package nvidia-331 fails to uninstall because nvidia-persistenced is still running Status in nvidia-graphics-drivers-331 package in Ubuntu: New Bug description: While trying to get a proper display without high heat on an Optimus laptop, I installed then uninstalled nvidia driver. On uninstalling, apt complained about nvidia-persistenced that was running, and indeed it was true. Manually killing the process allowed to finally uninstall the package. ProblemType: Package DistroRelease: Ubuntu 14.10 Package: nvidia-331 (not installed) ProcVersionSignature: Ubuntu 3.16.0-31.41-generic 3.16.7-ckt5 Uname: Linux 3.16.0-31-generic x86_64 ApportVersion: 2.14.7-0ubuntu8.2 AptOrdering: bumblebee-nvidia: Purge nvidia-331-uvm: Purge nvidia-331: Purge nvidia-opencl-icd-331: Purge Architecture: amd64 Date: Thu Mar 5 06:39:47 2015 DuplicateSignature: package:nvidia-331:(not installed):le sous-processus script post-removal installé a retourné une erreur de sortie d'état 8 ErrorMessage: le sous-processus script post-removal installé a retourné une erreur de sortie d'état 8 InstallationDate: Installed on 2015-03-04 (0 days ago) InstallationMedia: Xubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1) SourcePackage: nvidia-graphics-drivers-331 Title: package nvidia-331 (not installed) failed to install/upgrade: le sous-processus script post-removal installé a retourné une erreur de sortie d'état 8 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1428474/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1405209] Re: Thunderbird crashes on IMAP search for folder in NS_MsgHashIfNecessary.
Hello, The user requested to get back their parameters, like identities, local mail folders, etc. I diffed the pref.js between old and new account and was surprised to see that mail.root.imap references a non-existent directory. It should have been user_pref(mail.root.imap, /home/affectedusername/.thunderbird/someaccountname.default/ImapMail); It was instead user_pref(mail.root.imap, /home/someotherusername/.thunderbird/someaccountname.default/ImapMail); The first directory mentioned existed, the second not. That might explain the crash. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1405209 Title: Thunderbird crashes on IMAP search for folder in NS_MsgHashIfNecessary. Status in thunderbird package in Ubuntu: New Bug description: # Context On a Ubuntu 12.04 machine used by several users (two main users), Thunderbird has been used for years on various WiFi networks. Each user has his Unix account, one thunderbird profile, using IMAP server. Users don't connect to same e-mail provider. Yesterday evening, we moved to a usual alternate location with its own wifi. # Observed behavior Now one user has thunderbird crashing whenever it searches for folders, and that happens at startup, before user has a change to click anywhere. Thundebird only shows a window, in status bar a message like looking for folders with a progress bar at about 10-15%, then crashes. The user can access their mailbox normally via a webmail supplied by the IMAP provider. Folder names look normal there. Other user is totally unaffected by the problem. Reproducible: always. Expected behavior it obvious: no crash, user can browse their folders. # Additional information * Safe mode does not change anything, whatever the boxes checked (addons, toolbars). * Cutting off internet access allows to start thunderbird without immediate crash. * Changing these settings to false (they were true) is not enough to prevent crashes on startup with network access. user_pref(mail.server.server1.login_at_startup, false); user_pref(mail.startup.enabledMailCheckOnce, false); * In preference, unticking sync messages for this account does not prevent crash on startup. # Debug information Thunderbird crash reporter worked. I clicked yes when offered and typed a short sentence. This way I have submitted 21 crash reports today. Following https://wiki.ubuntu.com/MozillaTeam/Bugs I got stack traces that I can attach. package is 1:31.3.0+build1-0ubuntu0.12.04.1 I don't know if source matches http://dxr.mozilla.org/comm- central/source/mailnews/base/util/nsMsgUtils.cpp, but from the top of the stack tracs it looks like MsgHashIfNecessary() was supplied with an empty string, which may be the cause of crash. #0 NS_MsgHashIfNecessary (name=...) at /build/buildd/thunderbird-31.3.0+build1/mailnews/base/util/nsMsgUtils.cpp:446 lastIndex = -1 illegalCharacterIndex = optimized out hashedname = \000`\271\377\377\377\177\000 keptLength = optimized out Crash ID: bp-0744c6e8-13b6-4ff1-85ea-083022141223 Crash ID: bp-0f5ff99f-ae29-4300-b14c-5d3ec2141223 Crash ID: bp-1bc04187-d16c-428c-b226-02fa42141223 Crash ID: bp-1f928c7d-822b-43ad-9893-96c4f2141223 Crash ID: bp-2cb3dc60-f364-4836-82a1-1a86f2141223 Crash ID: bp-2e400b3c-aeac-48ec-8f18-33fbe2141223 Crash ID: bp-33c39df8-2565-4af4-bc57-d2ced2141223 Crash ID: bp-3e9b7666-1a2f-409e-beff-996e62141223 Crash ID: bp-68e88235-dc96-4b01-a803-9808f2141223 Crash ID: bp-71e10918-f8c5-41a6-a41f-91eca2141223 Crash ID: bp-9ee0e84a-217a-417e-b78c-501d82141223 Crash ID: bp-a173490f-5d76-4303-9e74-e72812141223 Crash ID: bp-b4f12af0-eb61-43d2-9939-ac11a2141223 Crash ID: bp-b5e9cf00-7da8-4dda-b172-964082141223 Crash ID: bp-b96e3d2c-dbaf-473e-b628-ba4f12141223 Crash ID: bp-bb1815ce-bd07-4809-9971-614ee2141223 Crash ID: bp-c42a1d6c-102e-4eee-abc6-08f0d2141223 Crash ID: bp-c9aa9ffc-183e-437d-b534-1a9c12141223 Crash ID: bp-d916ad64-68ae-4823-8d38-4f3912141223 Crash ID: bp-dc99e352-05ba-4819-95bc-0bd502141223 Crash ID: bp-e2d83623-5d39-4480-add2-ea8d72141223 lsb_release -rd Description: Ubuntu 12.04.5 LTS Release: 12.04 LC_ALL=C apt-cache policy thunderbird thunderbird: Installed: 1:31.3.0+build1-0ubuntu0.12.04.1 Candidate: 1:31.3.0+build1-0ubuntu0.12.04.1 Version table: *** 1:31.3.0+build1-0ubuntu0.12.04.1 0 500 http://fr.archive.ubuntu.com/ubuntu/ precise-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu/ precise-security/main amd64 Packages 100 /var/lib/dpkg/status 11.0.1+build1-0ubuntu2 0 500 http://fr.archive.ubuntu.com/ubuntu/ precise/main amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: thunderbird
[Desktop-packages] [Bug 1405209] [NEW] Thunderbird crashes on IMAP search for folder in NS_MsgHashIfNecessary.
Public bug reported: # Context On a Ubuntu 12.04 machine used by several users (two main users), Thunderbird has been used for years on various WiFi networks. Each user has his Unix account, one thunderbird profile, using IMAP server. Users don't connect to same e-mail provider. Yesterday evening, we moved to a usual alternate location with its own wifi. # Observed behavior Now one user has thunderbird crashing whenever it searches for folders, and that happens at startup, before user has a change to click anywhere. Thundebird only shows a window, in status bar a message like looking for folders with a progress bar at about 10-15%, then crashes. The user can access their mailbox normally via a webmail supplied by the IMAP provider. Folder names look normal there. Other user is totally unaffected by the problem. Reproducible: always. Expected behavior it obvious: no crash, user can browse their folders. # Additional information * Safe mode does not change anything, whatever the boxes checked (addons, toolbars). * Cutting off internet access allows to start thunderbird without immediate crash. * Changing these settings to false (they were true) is not enough to prevent crashes on startup with network access. user_pref(mail.server.server1.login_at_startup, false); user_pref(mail.startup.enabledMailCheckOnce, false); * In preference, unticking sync messages for this account does not prevent crash on startup. # Debug information Thunderbird crash reporter worked. I clicked yes when offered and typed a short sentence. This way I have submitted 21 crash reports today. Following https://wiki.ubuntu.com/MozillaTeam/Bugs I got stack traces that I can attach. package is 1:31.3.0+build1-0ubuntu0.12.04.1 I don't know if source matches http://dxr.mozilla.org/comm- central/source/mailnews/base/util/nsMsgUtils.cpp, but from the top of the stack tracs it looks like MsgHashIfNecessary() was supplied with an empty string, which may be the cause of crash. #0 NS_MsgHashIfNecessary (name=...) at /build/buildd/thunderbird-31.3.0+build1/mailnews/base/util/nsMsgUtils.cpp:446 lastIndex = -1 illegalCharacterIndex = optimized out hashedname = \000`\271\377\377\377\177\000 keptLength = optimized out Crash ID: bp-0744c6e8-13b6-4ff1-85ea-083022141223 Crash ID: bp-0f5ff99f-ae29-4300-b14c-5d3ec2141223 Crash ID: bp-1bc04187-d16c-428c-b226-02fa42141223 Crash ID: bp-1f928c7d-822b-43ad-9893-96c4f2141223 Crash ID: bp-2cb3dc60-f364-4836-82a1-1a86f2141223 Crash ID: bp-2e400b3c-aeac-48ec-8f18-33fbe2141223 Crash ID: bp-33c39df8-2565-4af4-bc57-d2ced2141223 Crash ID: bp-3e9b7666-1a2f-409e-beff-996e62141223 Crash ID: bp-68e88235-dc96-4b01-a803-9808f2141223 Crash ID: bp-71e10918-f8c5-41a6-a41f-91eca2141223 Crash ID: bp-9ee0e84a-217a-417e-b78c-501d82141223 Crash ID: bp-a173490f-5d76-4303-9e74-e72812141223 Crash ID: bp-b4f12af0-eb61-43d2-9939-ac11a2141223 Crash ID: bp-b5e9cf00-7da8-4dda-b172-964082141223 Crash ID: bp-b96e3d2c-dbaf-473e-b628-ba4f12141223 Crash ID: bp-bb1815ce-bd07-4809-9971-614ee2141223 Crash ID: bp-c42a1d6c-102e-4eee-abc6-08f0d2141223 Crash ID: bp-c9aa9ffc-183e-437d-b534-1a9c12141223 Crash ID: bp-d916ad64-68ae-4823-8d38-4f3912141223 Crash ID: bp-dc99e352-05ba-4819-95bc-0bd502141223 Crash ID: bp-e2d83623-5d39-4480-add2-ea8d72141223 lsb_release -rd Description:Ubuntu 12.04.5 LTS Release:12.04 LC_ALL=C apt-cache policy thunderbird thunderbird: Installed: 1:31.3.0+build1-0ubuntu0.12.04.1 Candidate: 1:31.3.0+build1-0ubuntu0.12.04.1 Version table: *** 1:31.3.0+build1-0ubuntu0.12.04.1 0 500 http://fr.archive.ubuntu.com/ubuntu/ precise-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu/ precise-security/main amd64 Packages 100 /var/lib/dpkg/status 11.0.1+build1-0ubuntu2 0 500 http://fr.archive.ubuntu.com/ubuntu/ precise/main amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: thunderbird 1:31.3.0+build1-0ubuntu0.12.04.1 ProcVersionSignature: Ubuntu 3.2.0-74.109-generic 3.2.64 Uname: Linux 3.2.0-74-generic x86_64 NonfreeKernelModules: nvidia AddonCompatCheckDisabled: False AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. ApportVersion: 2.0.1-0ubuntu17.8 Architecture: amd64 ArecordDevices: List of CAPTURE Hardware Devices card 0: Intel [HDA Intel], device 0: ALC663 Analog [ALC663 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 BuildID: 20141128200729 CRDA: country FR: (2402 - 2482 @ 40), (N/A, 20) (5170 - 5250 @ 40), (N/A, 20) (5250 - 5330 @ 40), (N/A, 20), DFS (5490 - 5710 @ 40), (N/A, 27), DFS Card0.Amixer.info: Card hw:0 'Intel'/'HDA Intel at 0xfbff8000 irq 48' Mixer name : 'Realtek ALC663' Components : 'HDA:10ec0663,10431463,0011' Controls : 29 Simple ctrls : 15 Card1.Amixer.info: Card hw:1 'NVidia'/'HDA NVidia at 0xfde7c000 irq 16' Mixer name : 'Nvidia GPU 0a HDMI/DP'
[Desktop-packages] [Bug 1405209] Re: Thunderbird crashes on IMAP search for folder in NS_MsgHashIfNecessary.
When debugging it's sometime useful to have two similar situations, one that works and one that fails. We have that here. Two machines : * same brand (Asus) but not same model * affected one is Ubuntu 12.04, working one is Ubuntu 14.04 * same WiFi network * same Thunderbird version (from their regular Ubuntu packages, details below) * accessing same IMAP provider, same IMAP account * nothing changed recently on either (only location and thus wifi changed yesterday) * working one has a thundebird profile with 9 mail servers, failing one has 2 (including local folders). * one crashes when connecting to IMAP, one works. Any hint appreciated. Thank you for your attention. Working machine: LC_ALL=C apt-cache policy thunderbird thunderbird: Installed: 1:31.3.0+build1-0ubuntu0.14.04.1 Candidate: 1:31.3.0+build1-0ubuntu0.14.04.1 Version table: *** 1:31.3.0+build1-0ubuntu0.14.04.1 0 500 http://fr.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu/ trusty-security/main amd64 Packages 100 /var/lib/dpkg/status 1:24.4.0+build1-0ubuntu1 0 500 http://fr.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1405209 Title: Thunderbird crashes on IMAP search for folder in NS_MsgHashIfNecessary. Status in thunderbird package in Ubuntu: New Bug description: # Context On a Ubuntu 12.04 machine used by several users (two main users), Thunderbird has been used for years on various WiFi networks. Each user has his Unix account, one thunderbird profile, using IMAP server. Users don't connect to same e-mail provider. Yesterday evening, we moved to a usual alternate location with its own wifi. # Observed behavior Now one user has thunderbird crashing whenever it searches for folders, and that happens at startup, before user has a change to click anywhere. Thundebird only shows a window, in status bar a message like looking for folders with a progress bar at about 10-15%, then crashes. The user can access their mailbox normally via a webmail supplied by the IMAP provider. Folder names look normal there. Other user is totally unaffected by the problem. Reproducible: always. Expected behavior it obvious: no crash, user can browse their folders. # Additional information * Safe mode does not change anything, whatever the boxes checked (addons, toolbars). * Cutting off internet access allows to start thunderbird without immediate crash. * Changing these settings to false (they were true) is not enough to prevent crashes on startup with network access. user_pref(mail.server.server1.login_at_startup, false); user_pref(mail.startup.enabledMailCheckOnce, false); * In preference, unticking sync messages for this account does not prevent crash on startup. # Debug information Thunderbird crash reporter worked. I clicked yes when offered and typed a short sentence. This way I have submitted 21 crash reports today. Following https://wiki.ubuntu.com/MozillaTeam/Bugs I got stack traces that I can attach. package is 1:31.3.0+build1-0ubuntu0.12.04.1 I don't know if source matches http://dxr.mozilla.org/comm- central/source/mailnews/base/util/nsMsgUtils.cpp, but from the top of the stack tracs it looks like MsgHashIfNecessary() was supplied with an empty string, which may be the cause of crash. #0 NS_MsgHashIfNecessary (name=...) at /build/buildd/thunderbird-31.3.0+build1/mailnews/base/util/nsMsgUtils.cpp:446 lastIndex = -1 illegalCharacterIndex = optimized out hashedname = \000`\271\377\377\377\177\000 keptLength = optimized out Crash ID: bp-0744c6e8-13b6-4ff1-85ea-083022141223 Crash ID: bp-0f5ff99f-ae29-4300-b14c-5d3ec2141223 Crash ID: bp-1bc04187-d16c-428c-b226-02fa42141223 Crash ID: bp-1f928c7d-822b-43ad-9893-96c4f2141223 Crash ID: bp-2cb3dc60-f364-4836-82a1-1a86f2141223 Crash ID: bp-2e400b3c-aeac-48ec-8f18-33fbe2141223 Crash ID: bp-33c39df8-2565-4af4-bc57-d2ced2141223 Crash ID: bp-3e9b7666-1a2f-409e-beff-996e62141223 Crash ID: bp-68e88235-dc96-4b01-a803-9808f2141223 Crash ID: bp-71e10918-f8c5-41a6-a41f-91eca2141223 Crash ID: bp-9ee0e84a-217a-417e-b78c-501d82141223 Crash ID: bp-a173490f-5d76-4303-9e74-e72812141223 Crash ID: bp-b4f12af0-eb61-43d2-9939-ac11a2141223 Crash ID: bp-b5e9cf00-7da8-4dda-b172-964082141223 Crash ID: bp-b96e3d2c-dbaf-473e-b628-ba4f12141223 Crash ID: bp-bb1815ce-bd07-4809-9971-614ee2141223 Crash ID: bp-c42a1d6c-102e-4eee-abc6-08f0d2141223 Crash ID: bp-c9aa9ffc-183e-437d-b534-1a9c12141223 Crash ID: bp-d916ad64-68ae-4823-8d38-4f3912141223 Crash ID: bp-dc99e352-05ba-4819-95bc-0bd502141223 Crash ID: bp-e2d83623-5d39-4480-add2-ea8d72141223 lsb_release -rd Description: Ubuntu
[Desktop-packages] [Bug 1405209] Re: Thunderbird crashes on IMAP search for folder in NS_MsgHashIfNecessary.
It was simple enough to create a new profile from scratch for the affected user. Now thunderbird works. So, something was broken in that user's profile. If that can be two cents to encourage Mozilla to make a reset profile feature like they did for Firefox, that would probably make things up. Thank you for your attention. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1405209 Title: Thunderbird crashes on IMAP search for folder in NS_MsgHashIfNecessary. Status in thunderbird package in Ubuntu: New Bug description: # Context On a Ubuntu 12.04 machine used by several users (two main users), Thunderbird has been used for years on various WiFi networks. Each user has his Unix account, one thunderbird profile, using IMAP server. Users don't connect to same e-mail provider. Yesterday evening, we moved to a usual alternate location with its own wifi. # Observed behavior Now one user has thunderbird crashing whenever it searches for folders, and that happens at startup, before user has a change to click anywhere. Thundebird only shows a window, in status bar a message like looking for folders with a progress bar at about 10-15%, then crashes. The user can access their mailbox normally via a webmail supplied by the IMAP provider. Folder names look normal there. Other user is totally unaffected by the problem. Reproducible: always. Expected behavior it obvious: no crash, user can browse their folders. # Additional information * Safe mode does not change anything, whatever the boxes checked (addons, toolbars). * Cutting off internet access allows to start thunderbird without immediate crash. * Changing these settings to false (they were true) is not enough to prevent crashes on startup with network access. user_pref(mail.server.server1.login_at_startup, false); user_pref(mail.startup.enabledMailCheckOnce, false); * In preference, unticking sync messages for this account does not prevent crash on startup. # Debug information Thunderbird crash reporter worked. I clicked yes when offered and typed a short sentence. This way I have submitted 21 crash reports today. Following https://wiki.ubuntu.com/MozillaTeam/Bugs I got stack traces that I can attach. package is 1:31.3.0+build1-0ubuntu0.12.04.1 I don't know if source matches http://dxr.mozilla.org/comm- central/source/mailnews/base/util/nsMsgUtils.cpp, but from the top of the stack tracs it looks like MsgHashIfNecessary() was supplied with an empty string, which may be the cause of crash. #0 NS_MsgHashIfNecessary (name=...) at /build/buildd/thunderbird-31.3.0+build1/mailnews/base/util/nsMsgUtils.cpp:446 lastIndex = -1 illegalCharacterIndex = optimized out hashedname = \000`\271\377\377\377\177\000 keptLength = optimized out Crash ID: bp-0744c6e8-13b6-4ff1-85ea-083022141223 Crash ID: bp-0f5ff99f-ae29-4300-b14c-5d3ec2141223 Crash ID: bp-1bc04187-d16c-428c-b226-02fa42141223 Crash ID: bp-1f928c7d-822b-43ad-9893-96c4f2141223 Crash ID: bp-2cb3dc60-f364-4836-82a1-1a86f2141223 Crash ID: bp-2e400b3c-aeac-48ec-8f18-33fbe2141223 Crash ID: bp-33c39df8-2565-4af4-bc57-d2ced2141223 Crash ID: bp-3e9b7666-1a2f-409e-beff-996e62141223 Crash ID: bp-68e88235-dc96-4b01-a803-9808f2141223 Crash ID: bp-71e10918-f8c5-41a6-a41f-91eca2141223 Crash ID: bp-9ee0e84a-217a-417e-b78c-501d82141223 Crash ID: bp-a173490f-5d76-4303-9e74-e72812141223 Crash ID: bp-b4f12af0-eb61-43d2-9939-ac11a2141223 Crash ID: bp-b5e9cf00-7da8-4dda-b172-964082141223 Crash ID: bp-b96e3d2c-dbaf-473e-b628-ba4f12141223 Crash ID: bp-bb1815ce-bd07-4809-9971-614ee2141223 Crash ID: bp-c42a1d6c-102e-4eee-abc6-08f0d2141223 Crash ID: bp-c9aa9ffc-183e-437d-b534-1a9c12141223 Crash ID: bp-d916ad64-68ae-4823-8d38-4f3912141223 Crash ID: bp-dc99e352-05ba-4819-95bc-0bd502141223 Crash ID: bp-e2d83623-5d39-4480-add2-ea8d72141223 lsb_release -rd Description: Ubuntu 12.04.5 LTS Release: 12.04 LC_ALL=C apt-cache policy thunderbird thunderbird: Installed: 1:31.3.0+build1-0ubuntu0.12.04.1 Candidate: 1:31.3.0+build1-0ubuntu0.12.04.1 Version table: *** 1:31.3.0+build1-0ubuntu0.12.04.1 0 500 http://fr.archive.ubuntu.com/ubuntu/ precise-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu/ precise-security/main amd64 Packages 100 /var/lib/dpkg/status 11.0.1+build1-0ubuntu2 0 500 http://fr.archive.ubuntu.com/ubuntu/ precise/main amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: thunderbird 1:31.3.0+build1-0ubuntu0.12.04.1 ProcVersionSignature: Ubuntu 3.2.0-74.109-generic 3.2.64 Uname: Linux 3.2.0-74-generic x86_64 NonfreeKernelModules: nvidia AddonCompatCheckDisabled: False AlsaVersion: Advanced Linux Sound Architecture
[Desktop-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 Desktop 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/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-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 Desktop 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/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-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 Desktop 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/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-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 Desktop 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/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1042359] Re: Brightness hotkeys not seen by kernel on Asus n55s, other hotkeys ok.
@Christopher, yes, you're right to ask Jaime to make a separate bug report. One reason is hardware is different. Another reason is this bug report was for an older release. Christopher M. Penalver (penalvch) wrote on 2014-01-09: #7 gouri, this bug was reported a while ago and there hasn't been any activity gouri (stephane-gourichon-lpad) wrote on 2013-11-02: On xubuntu 13.10, things that worked still work (hotkeys, etc), things that were unusual did as on 12.10 (e.g. Fn-F7). The good news is that Fn-F5 and Fn-F6 changed. Now there *is* an on-screen notification. The notification shows that the OS is aware, and indeed xbacklight reports new values. AFAIK this bug on this specific hardware (Asus N55S) is solved in Ubuntu 13.10, and 14.04. It's good to close it, right ? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-evdev in Ubuntu. https://bugs.launchpad.net/bugs/1042359 Title: Brightness hotkeys not seen by kernel on Asus n55s, other hotkeys ok. Status in “xserver-xorg-input-evdev” package in Ubuntu: Incomplete Bug description: On an Asus n55sf, there is an issue with the handling of brightness adjust keys. ## Severity: consistent annoyance for the target human user Rationale: * On this laptop, the most natural way to set LCD brightness (hotkeys) *seems* to work at first. * But the user's choice is consistently overriden. * More precisely: it is overriden whenever, on batteries, there is a pause in keyboard/mouse activity (e.g. when the user reads text on-screen, or comes back to the laptop after a minute). * Caveat: the problem is *not* the laptop dimming the brightness to save power, this is expected behavior. The problem is, when user provides events again, brightness is not reverted to value set by hotkeys. ## Context * X session, it can be Unity or other (e.g. xfce), scenario is the same. * Bug noticeable when running on batteries (due to automatic brightness change on idle). ## Expected behavior * pressing Fn-F5 and Fn-F6 changes the brightness * pressing Fn-F5 and Fn-F6 show on-screen notification * on battery after 30 seconds without key/mouse event, backlight is dimmed. Then, pressing any key or moving mouse restores brigthness at the value set using keys ## Observed behavior * pressing Fn-F5 and Fn-F6 changes the brightness - OK * pressing Fn-F5 and Fn-F6 *does not* show on-screen notification - minor * on battery after 30 seconds without key/mouse event, backlight is dimmed. Then, pressing any key or moving mouse restores brigthness at the last value set using software (gnome-control-center, xbacklight, whatever, but *not* the brightness set using keys) - bad ## Steps to reproduce * set backlight to 100% (using gnome-control-center or xbacklight =100 (usage scenario : on AC, need bright display) * unplug AC power to run on battery * change brightness using Fn-F5, e.g. some value halfway (usage scenario : now on the move, need to save power) * count a little more than 30 seconds without touching keyboard/touchpad/mouse, see brightness reduces to minimum * press e.g. shift, or move mouse or touchpad * expected : brightness jumps to halfway (set using hotkeys) * observed : brightness jumps to maximum (set using software) ## Additional information * Other keys work: sound volume, wifi toggle, touchpad toggle, sound play/pause/previous/next/stop * Some working keys *do* display OSD feedback (at least volume up/down/mute, touchpad toggle, sound play/pause/previous/next/stop) * Some working keys do not display OSD feedback (wifi toggle, supend, LCD toggle, LCD/external display toggle) * On a different laptop, Asus X77VN, brightness keys do show on-screen notification with percentage bar, and the bug is never experienced. Laptop is different model but same brand and software, same packages, same system and user settings (Unity or xfce, same behaviour). ## Interpretation * Everything seems consistent with the interpretation that although brightness hotkeys do work, Ubuntu is never aware of that. So when Ubuntu changes the brightness, it can not do better than use the value set using software. ## Workaround * In gnome control center, uncheck Dim screen to save power. A quick test shows that Ubuntu does not change brightness, so user preference set by hotkey is preserved. ## Other $ lsb_release -rd Description: Ubuntu 12.04.1 LTS Release: 12.04 ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: xorg 1:7.6+12ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-30.48-generic 3.2.27 Uname: Linux 3.2.0-30-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.0.1-0ubuntu12 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat
[Desktop-packages] [Bug 1284635] Re: IBus does not support certain keyboard layouts
Hello all, Similar problem here. ## Problem description Lubuntu 14.04 installed from beta (or daily). Selected french keyboard. Keyboard ok before login, every time (after boot or logout). Logging in using lubuntu-notebook session. After login, us keyboard is active instead of french. ## Workaround In the menus I found a session-specific tool that allows to set french keyboard. It displayed a flag or country indicator in the notification area. That worked for days then suddenly the tool was no longer to be found and the us layout went back. Then found this bug report. Applied sudo apt-get remove ibus. Log out, then log in. Now have system-wide french keyboard work correctly after login. ## Warning It appears tha -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1284635 Title: IBus does not support certain keyboard layouts Status in “ibus” package in Ubuntu: Triaged Status in “ibus” source package in Trusty: Triaged Bug description: installed trusty beta1 with keyboard layout set correctly during install install completes, login to new install - layout as set during install once logged in - layout set to US and keyboard layout set during install is missing from list ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: keyboard-configuration 1.70ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-12.32-generic 3.13.4 Uname: Linux 3.13.0-12-generic i686 ApportVersion: 2.13.2-0ubuntu5 Architecture: i386 CurrentDesktop: XFCE Date: Tue Feb 25 12:55:56 2014 InstallationDate: Installed on 2014-02-25 (0 days ago) InstallationMedia: Xubuntu 14.04 LTS Trusty Tahr - Alpha i386 (20140225) PackageArchitecture: all SourcePackage: console-setup UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1284635/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
