Re: [Ubuntu-x-swat] [Bug 549256] Re: [GeForce 7025 / nForce 630a] video flicker on any I/O activity with nouveau; OK with nv driver
Christopher, Am 21.05.2018 um 15:58 schrieb Christopher M. Penalver: > Michael Schmitz: > > 1) To clarify, you tested the 64-bit variant (not 32-bit)? Correct. > 2) Is using the nv driver still a usable WORKAROUND? > Sorry, didn't try that (is it even possible without installing from that image?). Cheers, Michael > ** Description changed: > > Binary package hint: xserver-xorg-video-nouveau > > Expectation: Default Xorg driver should work with no video artifacts. > > Observation: Bad screen flicker with default Xorg driver. > > Details: I installed the 10.04 beta from CD on Wednesday (incidentially, > compliments for the smooth install). Already upon installation, the > display did flicker badly whenever the CD was read or even the mouse > moved. Flicker did already start at the initial splash screen. The > system was fully responsive otherwise. On reboot post-installation, gdm > came up OK but with the same flicker problems. The 'Monitors' control > panel only offered the 2048x1536 resolution at 80 Hz with no other > options. Tried to install and use one of the non-free nvidia drivers, > this failed because the nouveau kernel module was loaded always and > could not be unloaded (drm loads nouveau before framebuffer console > init. as near as I can make out). With nvidia-current unable to load, > - the X server could not use the 'nvidia' driver. Switching xorg.conf to > - use the 'nv' driver results in a much better screen display (only > - occasional flicker) although the driver only supports 2048x1536 at 60 > - Hz. 1600x1200@85 Hz is useable. > + the X server could not use the 'nvidia' driver. > > Kernel message buffer excerpt: > [4.777915] [drm] Initialized drm 1.1.0 20060810 > [4.807773] ACPI: PCI Interrupt Link [LMC9] enabled at IRQ 22 > [4.807779] nouveau :00:0d.0: PCI INT A -> Link[LMC9] -> GSI 22 > (level, low) -> IRQ 22 > [4.807783] nouveau :00:0d.0: setting latency timer to 64 > [4.809992] [drm] nouveau :00:0d.0: failed to evaluate _DSM: 5 > [4.810217] [drm] nouveau :00:0d.0: Detected an NV40 generation card > (0x04c000a2) > [4.810513] [drm] nouveau :00:0d.0: Attempting to load BIOS image > from PROM > [4.810519] [drm] nouveau :00:0d.0: ... BIOS signature not found > [4.810520] [drm] nouveau :00:0d.0: Attempting to load BIOS image > from PRAMIN > [4.854556] [drm] nouveau :00:0d.0: ... appears to be valid > [4.854559] [drm] nouveau :00:0d.0: BIT BIOS found > [4.854561] [drm] nouveau :00:0d.0: Bios version 05.61.32.28 > [4.854563] [drm] nouveau :00:0d.0: BIT table 'd' not found > [4.854565] [drm] nouveau :00:0d.0: Found Display Configuration > Block version 3.0 > [4.854568] [drm] nouveau :00:0d.0: DCB connector table: VHER 0x30 5 > 10 2 > [4.854571] [drm] nouveau :00:0d.0: 0: 0x: type 0x00 idx 0 > tag 0xff > [4.854573] [drm] nouveau :00:0d.0: 1: 0x1131: type 0x31 idx 1 > tag 0x07 > [4.854575] [drm] nouveau :00:0d.0: 2: 0x0110: type 0x10 idx 1 > tag 0xff > [4.854577] [drm] nouveau :00:0d.0: 3: 0x0111: type 0x11 idx 1 > tag 0xff > [4.854579] [drm] nouveau :00:0d.0: 4: 0x0113: type 0x13 idx 1 > tag 0xff > [4.854581] [drm] nouveau :00:0d.0: Raw DCB entry 0: 01000310 > 0023 > [4.854583] [drm] nouveau :00:0d.0: Raw DCB entry 1: 00110204 > 942b0003 > [4.854588] [drm] nouveau :00:0d.0: Parsing VBIOS init table 0 at > offset 0xD9C9 > [4.854591] [drm] nouveau :00:0d.0: === misaligned reg > 0x0060081D === > [4.854648] [drm] nouveau :00:0d.0: === misaligned reg > 0x0060081D === > [4.854748] [drm] nouveau :00:0d.0: Parsing VBIOS init table 1 at > offset 0xDB17 > [4.854749] [drm] nouveau :00:0d.0: Parsing VBIOS init table 2 at > offset 0xDB18 > [4.854799] [drm] nouveau :00:0d.0: Parsing VBIOS init table 3 at > offset 0xDC9A > [4.854803] [drm] nouveau :00:0d.0: Parsing VBIOS init table 4 at > offset 0xDCE3 > [4.861274] lp0: using parport0 (interrupt-driven). > [4.865006] [TTM] Zone kernel: Available graphics memory: 444292 kiB. > [4.865009] [TTM] Zone highmem: Available graphics memory: 448232 kiB. > [4.865018] [drm] nouveau :00:0d.0: 128 MiB VRAM > [4.865912] [drm] nouveau :00:0d.0: 64 MiB GART (aperture) > [4.868624] [drm] nouveau :00:0d.0: Allocating FIFO number 0 > [4.868891] [drm] nouveau :00:0d.0: nouveau_channel_alloc: > initialised FIFO 0 > [4.868896] [drm] nouveau :00:0d.0: Initial CRTC_OWNER is 0 > [4.868901] [drm] nouveau :00:0d.0: Saving VGA fonts > [4.908706] [drm] nouveau :00:0d.0: DCB type 4 not known > [4.908710] [drm] nouveau :00:0d.0: Detected a VGA connector > [4.909936] [drm]
[Ubuntu-x-swat] [Bug 1727541] Re: After suspend, three fingers needed for two-finger scroll
[Expired for libinput (Ubuntu) because there has been no activity for 60 days.] ** Changed in: libinput (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to libinput in Ubuntu. https://bugs.launchpad.net/bugs/1727541 Title: After suspend, three fingers needed for two-finger scroll To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/1727541/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 549256] Re: [GeForce 7025 / nForce 630a] video flicker on any I/O activity with nouveau; OK with nv driver
Michael Schmitz: 1) To clarify, you tested the 64-bit variant (not 32-bit)? 2) Is using the nv driver still a usable WORKAROUND? ** Description changed: Binary package hint: xserver-xorg-video-nouveau Expectation: Default Xorg driver should work with no video artifacts. Observation: Bad screen flicker with default Xorg driver. Details: I installed the 10.04 beta from CD on Wednesday (incidentially, compliments for the smooth install). Already upon installation, the display did flicker badly whenever the CD was read or even the mouse moved. Flicker did already start at the initial splash screen. The system was fully responsive otherwise. On reboot post-installation, gdm came up OK but with the same flicker problems. The 'Monitors' control panel only offered the 2048x1536 resolution at 80 Hz with no other options. Tried to install and use one of the non-free nvidia drivers, this failed because the nouveau kernel module was loaded always and could not be unloaded (drm loads nouveau before framebuffer console init. as near as I can make out). With nvidia-current unable to load, - the X server could not use the 'nvidia' driver. Switching xorg.conf to - use the 'nv' driver results in a much better screen display (only - occasional flicker) although the driver only supports 2048x1536 at 60 - Hz. 1600x1200@85 Hz is useable. + the X server could not use the 'nvidia' driver. Kernel message buffer excerpt: [4.777915] [drm] Initialized drm 1.1.0 20060810 [4.807773] ACPI: PCI Interrupt Link [LMC9] enabled at IRQ 22 [4.807779] nouveau :00:0d.0: PCI INT A -> Link[LMC9] -> GSI 22 (level, low) -> IRQ 22 [4.807783] nouveau :00:0d.0: setting latency timer to 64 [4.809992] [drm] nouveau :00:0d.0: failed to evaluate _DSM: 5 [4.810217] [drm] nouveau :00:0d.0: Detected an NV40 generation card (0x04c000a2) [4.810513] [drm] nouveau :00:0d.0: Attempting to load BIOS image from PROM [4.810519] [drm] nouveau :00:0d.0: ... BIOS signature not found [4.810520] [drm] nouveau :00:0d.0: Attempting to load BIOS image from PRAMIN [4.854556] [drm] nouveau :00:0d.0: ... appears to be valid [4.854559] [drm] nouveau :00:0d.0: BIT BIOS found [4.854561] [drm] nouveau :00:0d.0: Bios version 05.61.32.28 [4.854563] [drm] nouveau :00:0d.0: BIT table 'd' not found [4.854565] [drm] nouveau :00:0d.0: Found Display Configuration Block version 3.0 [4.854568] [drm] nouveau :00:0d.0: DCB connector table: VHER 0x30 5 10 2 [4.854571] [drm] nouveau :00:0d.0: 0: 0x: type 0x00 idx 0 tag 0xff [4.854573] [drm] nouveau :00:0d.0: 1: 0x1131: type 0x31 idx 1 tag 0x07 [4.854575] [drm] nouveau :00:0d.0: 2: 0x0110: type 0x10 idx 1 tag 0xff [4.854577] [drm] nouveau :00:0d.0: 3: 0x0111: type 0x11 idx 1 tag 0xff [4.854579] [drm] nouveau :00:0d.0: 4: 0x0113: type 0x13 idx 1 tag 0xff [4.854581] [drm] nouveau :00:0d.0: Raw DCB entry 0: 01000310 0023 [4.854583] [drm] nouveau :00:0d.0: Raw DCB entry 1: 00110204 942b0003 [4.854588] [drm] nouveau :00:0d.0: Parsing VBIOS init table 0 at offset 0xD9C9 [4.854591] [drm] nouveau :00:0d.0: === misaligned reg 0x0060081D === [4.854648] [drm] nouveau :00:0d.0: === misaligned reg 0x0060081D === [4.854748] [drm] nouveau :00:0d.0: Parsing VBIOS init table 1 at offset 0xDB17 [4.854749] [drm] nouveau :00:0d.0: Parsing VBIOS init table 2 at offset 0xDB18 [4.854799] [drm] nouveau :00:0d.0: Parsing VBIOS init table 3 at offset 0xDC9A [4.854803] [drm] nouveau :00:0d.0: Parsing VBIOS init table 4 at offset 0xDCE3 [4.861274] lp0: using parport0 (interrupt-driven). [4.865006] [TTM] Zone kernel: Available graphics memory: 444292 kiB. [4.865009] [TTM] Zone highmem: Available graphics memory: 448232 kiB. [4.865018] [drm] nouveau :00:0d.0: 128 MiB VRAM [4.865912] [drm] nouveau :00:0d.0: 64 MiB GART (aperture) [4.868624] [drm] nouveau :00:0d.0: Allocating FIFO number 0 [4.868891] [drm] nouveau :00:0d.0: nouveau_channel_alloc: initialised FIFO 0 [4.868896] [drm] nouveau :00:0d.0: Initial CRTC_OWNER is 0 [4.868901] [drm] nouveau :00:0d.0: Saving VGA fonts [4.908706] [drm] nouveau :00:0d.0: DCB type 4 not known [4.908710] [drm] nouveau :00:0d.0: Detected a VGA connector [4.909936] [drm] nouveau :00:0d.0: Setting dpms mode 3 on vga encoder (output 0) [5.037394] [drm] nouveau :00:0d.0: allocated 2048x1536 fb: 0x49000, bo f67bb400 [5.037515] fb0: nouveaufb frame buffer device [5.037517] registered panic notifier [5.037523] [drm] Initialized nouveau 0.0.15 20090420 for :00:0d.0 on minor 0 [5.037985] ACPI: PCI Interrupt
Re: [Ubuntu-x-swat] [Bug 549256] Re: [GeForce 7025 / nForce 630a] video flicker on any I/O activity with nouveau; OK with nv driver
Hi Christopher, still the same problem as before. Cheers, Michael Am 18.05.2018 um 16:58 schrieb Christopher M. Penalver: > Michael Schmitz, to confirm this is still a problem in Ubuntu, could you > please test http://cdimage.ubuntu.com/daily-live/current/ and advise to > the results? > > ** Project changed: nouveau => xserver-xorg-video-nouveau (Ubuntu) > > ** Changed in: xserver-xorg-video-nouveau (Ubuntu) >Status: New => Incomplete > > ** Changed in: xserver-xorg-video-nouveau (Ubuntu) >Importance: Undecided => Low > > ** Tags removed: needs-apport-collect > -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-nouveau in Ubuntu. https://bugs.launchpad.net/bugs/549256 Title: [GeForce 7025 / nForce 630a] video flicker on any I/O activity with nouveau; OK with nv driver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/549256/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1770913] Re: Software rendering is forced after 18.04 upgrade (Intel Core 2 Duo P8600 / GMA 4500MHD)
How can I switch to Wayland? Contrary to the articles those tell otherwise, I have no option to select it on the login screen. Anyway, 17.10 worked fine with Wayland, so switching back to Wayland might probably help. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1770913 Title: Software rendering is forced after 18.04 upgrade (Intel Core 2 Duo P8600 / GMA 4500MHD) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1770913/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1767559] Re: Provide libinput 1.10.6 in bionic-updates to fix specific touchpad and keyboard issues
Is that fixed in 1.10.7? :) https://lists.freedesktop.org/archives/wayland- devel/2018-May/038187.html -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to libinput in Ubuntu. https://bugs.launchpad.net/bugs/1767559 Title: Provide libinput 1.10.6 in bionic-updates to fix specific touchpad and keyboard issues To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/1767559/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1772083] Re: eGalax touchscreen is identified as tablet. Doesn't work
Please help us to progress this issue by reporting it to the libinput developers here: https://bugs.freedesktop.org/enter_bug.cgi?product=wayland=libinput and then let us know the ID of the new bug. ** Changed in: libinput (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to libinput in Ubuntu. https://bugs.launchpad.net/bugs/1772083 Title: eGalax touchscreen is identified as tablet. Doesn't work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/1772083/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1770913] Re: Software rendering is forced after 18.04 upgrade (Intel Core 2 Duo P8600 / GMA 4500MHD)
This looks relevant. Xorg is saying: [ 2402.232] (II) AIGLX: Screen 0 is not DRI2 capable [ 2402.232] (EE) AIGLX: reverting to software rendering Are you able to log into Wayland sessions? ** Summary changed: - Software rendering is forced after 18.04 upgrade + Software rendering is forced after 18.04 upgrade (Intel Core 2 Duo P8600 / GMA 4500MHD) ** No longer affects: xorg (Ubuntu) ** No longer affects: xserver-xorg-video-intel (Ubuntu) ** Also affects: mesa (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-intel in Ubuntu. https://bugs.launchpad.net/bugs/1770913 Title: Software rendering is forced after 18.04 upgrade (Intel Core 2 Duo P8600 / GMA 4500MHD) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1770913/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1753663] Re: [Mesa 18.0 + nvidia-390] No 3D acceleration, using llvmpipe
This bug is closed. If you continue to experience any problems then please open a new bug by running: ubuntu-bug mesa or ubuntu-bug nvidia-graphics-drivers-390 -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1753663 Title: [Mesa 18.0 + nvidia-390] No 3D acceleration, using llvmpipe To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libglvnd/+bug/1753663/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1752938] Re: Upgrading Ubuntu 18.04 disables GPU hardware acceleration
Fix from #1767468 also doers not work for me. Intel HD 520 -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1752938 Title: Upgrading Ubuntu 18.04 disables GPU hardware acceleration To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1752938/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1753663] Re: [Mesa 18.0 + nvidia-390] No 3D acceleration, using llvmpipe
I have the same as @shankao. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1753663 Title: [Mesa 18.0 + nvidia-390] No 3D acceleration, using llvmpipe To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libglvnd/+bug/1753663/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1772317] [NEW] Missing dependency libgtkmm for gparted
Public bug reported: I did a minimal install of Ubuntu 18.04. Initially, although apt claimed that gparted was already installed, the binary didn't seem to exist. I removed it and reinstalled it, but it seems to be missing dependencies: Running "sudo gparted": /usr/sbin/gpartedbin: error while loading shared libraries: libgtkmm-2.4.so.1: cannot open shared object file: No such file or directory Running "sudo apt-get install -f": 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. I had to remove libgtkmm-2.4-1v5, which also removed gparted, and then reinstall gparted, which seems to have correctly installed the libgtkmm-2.4-1v5 library. I had to do something similar with libatkmm-1.6-1v5, libpangomm-1.4-1v5, libglibmm-2.4-1v5. Doing this seems to fix it: sudo apt-get install --reinstall libcairomm-1.0-1v5 libglibmm-2.4-1v5 libsigc++-2.0-0v5 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1772317 Title: Missing dependency libgtkmm for gparted To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1772317/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [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.
** 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. - - 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. + Using the nvidia proprietary driver 361.42 isn't a WORKAROUND as it causes black screen on boot as per: + https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1575907 + --- 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 splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-7.22-generic 4.4.2 Tags: xenial ubuntu regression reproducible has-workaround Uname: Linux 4.4.0-7-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev
[Ubuntu-x-swat] [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.
gouri, to see if this is resolved in your release, could you please update your HWE stack as per https://wiki.ubuntu.com/Kernel/LTSEnablementStack and advise to the results? ** Attachment removed: "panel-corrupted.png" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1547077/+attachment/4690163/+files/panel-corrupted.png ** Attachment removed: "What the panel should look like." https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1547077/+attachment/4690186/+files/panel.png ** Attachment removed: "CurrentDmesg.txt" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1547077/+attachment/4690187/+files/CurrentDmesg.txt ** Attachment removed: "Dependencies.txt" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1547077/+attachment/4690188/+files/Dependencies.txt ** Attachment removed: "DpkgLog.txt" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1547077/+attachment/4690189/+files/DpkgLog.txt ** Attachment removed: "GconfCompiz.txt" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1547077/+attachment/4690190/+files/GconfCompiz.txt ** Attachment removed: "JournalErrors.txt" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1547077/+attachment/4690191/+files/JournalErrors.txt ** Attachment removed: "Lspci.txt" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1547077/+attachment/4690192/+files/Lspci.txt ** Attachment removed: "MonitorsUser.xml.txt" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1547077/+attachment/4690194/+files/MonitorsUser.xml.txt ** Attachment removed: "Lsusb.txt" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1547077/+attachment/4690193/+files/Lsusb.txt ** Attachment removed: "ProcCpuinfo.txt" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1547077/+attachment/4690195/+files/ProcCpuinfo.txt ** Attachment removed: "ProcEnviron.txt" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1547077/+attachment/4690196/+files/ProcEnviron.txt ** Attachment removed: "ProcInterrupts.txt" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1547077/+attachment/4690197/+files/ProcInterrupts.txt ** Attachment removed: "ProcModules.txt" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1547077/+attachment/4690198/+files/ProcModules.txt ** Attachment removed: "UdevDb.txt" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1547077/+attachment/4690199/+files/UdevDb.txt ** Attachment removed: "XorgLog.txt" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1547077/+attachment/4690200/+files/XorgLog.txt ** Attachment removed: "XorgLogOld.txt" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1547077/+attachment/4690201/+files/XorgLogOld.txt ** Attachment removed: "Xrandr.txt" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1547077/+attachment/4690202/+files/Xrandr.txt ** Attachment removed: "xdpyinfo.txt" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1547077/+attachment/4690203/+files/xdpyinfo.txt ** Changed in: xorg (Ubuntu) Status: Triaged => Incomplete -- You received this bug notification because you are a member of Ubuntu-X, 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. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1547077/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1761834] Re: Right-click doesn't work
I just wanted to add two new notes to this bug report: 1. When I reported it, I was using a beta of 18.04, right-click didn't work either by clicking on the area of the trackpad that is supposed to be reserved for right-click or by using two-finger click. The former is still true in the full released version, but the later seems to be fixed, albeit, it is quite difficult and requires very precise timing and finger spacing to achieve a right-click (I get a successful right- click with two fingers about 20% of the time). 2. I have done a clean install on a different laptop with completely different hardware, and I am seeing exactly the same problem. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1761834 Title: Right-click doesn't work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1761834/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1547077] Re: Suspend to ram causes some glyphs to draw consistently wrong or even appear blank in gtk/gdk/pango/cairo apps. xterm/xmessage unaffected.
To add to my latest comment where I report that problem reappeared a few times in recent days: same hardware, same usage pattern, on the very re- installation of 16.04 that had the problem disappear (cf. #comment:77). Software updates applied regularly since the last near-2-years. Nothing salient would explain that, besides maybe a regression that came with a software update? -- You received this bug notification because you are a member of Ubuntu-X, 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. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1547077/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1547077] Re: Suspend to ram causes some glyphs to draw consistently wrong or even appear blank in gtk/gdk/pango/cairo apps. xterm/xmessage unaffected.
Interestingly, thus bug started to reappear in its extreme form: a few times in the past days, all letters disappeared in my xfce4-terminals. Workaround was to close and reopen session. -- You received this bug notification because you are a member of Ubuntu-X, 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. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1547077/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1768169] Re: touchscreen doesn't work properly after stylus detection
oups sorry wrong place... -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xinput in Ubuntu. https://bugs.launchpad.net/bugs/1768169 Title: touchscreen doesn't work properly after stylus detection To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xinput/+bug/1768169/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1768169] Re: touchscreen doesn't work properly after stylus detection
By disabling the Gesture parameter for my touchscreen multitouch is working. But no more pinch to zoom or to finger to scroll ... no more Gestures ! Both should be able to work together. Should I open an issue ? -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xinput in Ubuntu. https://bugs.launchpad.net/bugs/1768169 Title: touchscreen doesn't work properly after stylus detection To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xinput/+bug/1768169/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1761549] Re: [HP ENVY Notebook - 15-ae008tx] Screen flickering after screen lock timeout
Anupam Datta, to advise, one may test for this in a live environment to see if this is reproducible. ** Summary changed: - Screen flickering, whenever went to lock, waking up creates problem. + [HP ENVY Notebook - 15-ae008tx] Screen flickering after screen lock timeout ** Tags added: bios-outdated-f.49 ** Tags added: regression-release -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1761549 Title: [HP ENVY Notebook - 15-ae008tx] Screen flickering after screen lock timeout To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1761549/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1755097] Re: LIBGL_ALWAYS_SOFTWARE=1 renderer used instead of Intel on Xorg sessions because of unity leftover file /etc/X11/Xsession.d/50_check_unity_support
(on wayland I do get the intel drivers, but wayland has other problems) -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1755097 Title: LIBGL_ALWAYS_SOFTWARE=1 renderer used instead of Intel on Xorg sessions because of unity leftover file /etc/X11/Xsession.d/50_check_unity_support To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1755097/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1755097] Re: LIBGL_ALWAYS_SOFTWARE=1 renderer used instead of Intel on Xorg sessions because of unity leftover file /etc/X11/Xsession.d/50_check_unity_support
I've purged nux-tools, and /etc/X11/Xsession.d/50_check_unity_support is gone, but after a reboot, I still get $ glxinfo | grep renderer GLX_MESA_multithread_makecurrent, GLX_MESA_query_renderer, GLX_MESA_multithread_makecurrent, GLX_MESA_query_renderer, Extended renderer info (GLX_MESA_query_renderer): OpenGL renderer string: llvmpipe (LLVM 6.0, 256 bits) $ LIBGL_ALWAYS_SOFTWARE=0 glxinfo | grep -i opengl OpenGL vendor string: VMware, Inc. OpenGL renderer string: llvmpipe (LLVM 6.0, 256 bits) OpenGL core profile version string: 3.3 (Core Profile) Mesa 18.0.0-rc5 OpenGL core profile shading language version string: 3.30 OpenGL core profile context flags: (none) OpenGL core profile profile mask: core profile OpenGL core profile extensions: OpenGL version string: 3.0 Mesa 18.0.0-rc5 OpenGL shading language version string: 1.30 OpenGL context flags: (none) OpenGL extensions: OpenGL ES profile version string: OpenGL ES 3.0 Mesa 18.0.0-rc5 OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.00 OpenGL ES profile extensions: -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1755097 Title: LIBGL_ALWAYS_SOFTWARE=1 renderer used instead of Intel on Xorg sessions because of unity leftover file /etc/X11/Xsession.d/50_check_unity_support To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1755097/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1761549] Re: Screen flickering, whenever went to lock, waking up creates problem.
After 16.04 this happened. Also there is no such issue with Windows 10 I can't install a new image. I need to take whole lot of back up. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1761549 Title: Screen flickering, whenever went to lock, waking up creates problem. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1761549/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1761549] Re: Screen flickering, whenever went to lock, waking up creates problem.
product: HP ENVY Notebook (M9V81PA#ACJ) product: 80DD product: Intel(R) Core(TM) i7-5500U CPU @ 2.40GHz product: 16KTF1G64HZ-1G6N1 product: 16KTF1G64HZ-1G6N1 product: Broadwell-U Host Bridge -OPI product: HD Graphics 5500 product: Broadwell-U Audio Controller product: Broadwell-U Processor Thermal Subsystem product: Wildcat Point-LP USB xHCI Controller product: xHCI Host Controller product: USB Optical Mouse product: HP Truevision HD product: xHCI Host Controller product: Wildcat Point-LP MEI Controller #1 product: Wildcat Point-LP High Definition Audio Controller product: Wildcat Point-LP PCI Express Root Port #1 product: Wildcat Point-LP PCI Express Root Port #3 product: RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller product: Wildcat Point-LP PCI Express Root Port #4 product: RTS522A PCI Express Card Reader product: Wildcat Point-LP PCI Express Root Port #5 product: GM107M [GeForce GTX 950M] product: Wildcat Point-LP PCI Express Root Port #6 product: Wireless 3160 product: Wildcat Point-LP LPC Controller product: Wildcat Point-LP SATA Controller [AHCI Mode] product: Wildcat Point-LP SMBus Controller product: Wildcat Point-LP Thermal Management Controller product: ST2000LM003 HN-M product: LP03055 -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1761549 Title: Screen flickering, whenever went to lock, waking up creates problem. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1761549/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1761549] Re: Screen flickering, whenever went to lock, waking up creates problem.
SMBIOS 2.8 present. 55 structures occupying 2932 bytes. Table at 0x9BE7E000. Handle 0x, DMI type 0, 24 bytes BIOS Information Vendor: Insyde Version: F.45 Release Date: 05/23/2017 Address: 0xE Runtime Size: 128 kB ROM Size: 6144 kB Characteristics: PCI is supported BIOS is upgradeable BIOS shadowing is allowed Boot from CD is supported Selectable boot is supported EDD is supported Japanese floppy for NEC 9800 1.2 MB is supported (int 13h) Japanese floppy for Toshiba 1.2 MB is supported (int 13h) 5.25"/360 kB floppy services are supported (int 13h) 5.25"/1.2 MB floppy services are supported (int 13h) 3.5"/720 kB floppy services are supported (int 13h) 3.5"/2.88 MB floppy services are supported (int 13h) 8042 keyboard services are supported (int 9h) CGA/mono video services are supported (int 10h) ACPI is supported USB legacy is supported BIOS boot specification is supported Targeted content distribution is supported UEFI is supported BIOS Revision: 15.69 Firmware Revision: 64.39 Handle 0x0001, DMI type 1, 27 bytes System Information Manufacturer: Hewlett-Packard Product Name: HP ENVY Notebook Version: Type1ProductConfigId Serial Number: CND5285KXS UUID: 87CD7F2E-081E-E511-A26A-5820B1690656 Wake-up Type: Power Switch SKU Number: M9V81PA#ACJ Family: 103C_5335KV G=N L=CON B=HP S=ENV Handle 0x0002, DMI type 2, 17 bytes Base Board Information Manufacturer: Hewlett-Packard Product Name: 80DD Version: 64.39 Serial Number: PFFFPC21W8WVZY Asset Tag: Type2 - Board Asset Tag Features: Board is a hosting board Board is replaceable Location In Chassis: Type2 - Board Chassis Location Chassis Handle: 0x0003 Type: Motherboard Contained Object Handles: 0 Handle 0x0003, DMI type 3, 24 bytes Chassis Information Manufacturer: Hewlett-Packard Type: Notebook Lock: Not Present Version: Chassis Version Serial Number: Chassis Serial Number Asset Tag: Chassis Asset Tag Boot-up State: Safe Power Supply State: Safe Thermal State: Safe Security Status: None OEM Information: 0x010E Height: Unspecified Number Of Power Cords: 1 Contained Elements: 0 SKU Number: Handle 0x0004, DMI type 4, 42 bytes Processor Information Socket Designation: U3E1 Type: Central Processor Family: Core i7 Manufacturer: Intel(R) Corporation ID: D4 06 03 00 FF FB EB BF Signature: Type 0, Family 6, Model 61, Stepping 4 Flags: FPU (Floating-point unit on-chip) VME (Virtual mode extension) DE (Debugging extension) PSE (Page size extension) TSC (Time stamp counter) MSR (Model specific registers) PAE (Physical address extension) MCE (Machine check exception) CX8 (CMPXCHG8 instruction supported) APIC (On-chip APIC hardware supported) SEP (Fast system call) MTRR (Memory type range registers) PGE (Page global enable) MCA (Machine check architecture) CMOV (Conditional move instruction supported) PAT (Page attribute table) PSE-36 (36-bit page size extension) CLFSH (CLFLUSH instruction supported) DS (Debug store) ACPI (ACPI supported) MMX (MMX technology supported) FXSR (FXSAVE and FXSTOR instructions supported) SSE (Streaming SIMD extensions) SSE2 (Streaming SIMD extensions 2) SS (Self-snoop) HTT (Multi-threading) TM (Thermal monitor supported) PBE (Pending break enabled) Version: Intel(R) Core(TM) i7-5500U CPU @ 2.40GHz Voltage: 1.0 V External Clock: 100 MHz Max Speed: 3000 MHz Current Speed: 2900 MHz Status: Populated, Enabled Upgrade: Socket BGA1168 L1 Cache Handle: 0x0006 L2 Cache Handle: 0x0007 L3 Cache Handle: 0x0008 Serial Number: To Be Filled By O.E.M. Asset Tag: To Be Filled By O.E.M. Part Number: To Be Filled By O.E.M. Core Count: 2 Core Enabled: 2 Thread Count: 4 Characteristics: 64-bit capable Multi-Core
