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
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
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
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:
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.
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.
@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 fi
** Summary changed:
- Some glyphs drawn consistently wrong, bug comes and go
+ Suspend to ram causes some glyphs to draw consistently wrong or even appear
blank in gtk/gdk/pango/cairo apps. xterm/xmessage unaffected.
--
You received this bug notification because you are a member of Ubuntu-X,
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.
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
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
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
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
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
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
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
> 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 t
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
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
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
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
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
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
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
@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
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
apport information
** Attachment added: "xdpyinfo.txt"
https://bugs.launchpad.net/bugs/1547077/+attachment/4585300/+files/xdpyinfo.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1547077
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1547077/+attachment/4585294/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
apport information
** Attachment added: "XorgLog.txt"
https://bugs.launchpad.net/bugs/1547077/+attachment/4585297/+files/XorgLog.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1547077
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1547077/+attachment/4585295/+files/ProcModules.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
apport information
** Attachment added: "Xrandr.txt"
https://bugs.launchpad.net/bugs/1547077/+attachment/4585299/+files/Xrandr.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1547077
apport information
** Attachment added: "XorgLogOld.txt"
https://bugs.launchpad.net/bugs/1547077/+attachment/4585298/+files/XorgLogOld.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1547077/+attachment/4585296/+files/UdevDb.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1547077
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1547077/+attachment/4585293/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1547077/+attachment/4585292/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
apport information
** Attachment added: "NonfreeKernelModules.txt"
https://bugs.launchpad.net/bugs/1547077/+attachment/4585291/+files/NonfreeKernelModules.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1547077/+attachment/4585289/+files/Lspci.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1547077
Title:
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/1547077/+attachment/4585290/+files/Lsusb.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1547077
Title:
apport information
** Attachment added: "LightdmGreeterLog.txt"
https://bugs.launchpad.net/bugs/1547077/+attachment/4585287/+files/LightdmGreeterLog.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
apport information
** Attachment added: "LightdmLog.txt"
https://bugs.launchpad.net/bugs/1547077/+attachment/4585288/+files/LightdmLog.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
apport information
** Attachment added: "JournalErrors.txt"
https://bugs.launchpad.net/bugs/1547077/+attachment/4585285/+files/JournalErrors.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
apport information
** Attachment added: "LightdmDisplayLog.txt"
https://bugs.launchpad.net/bugs/1547077/+attachment/4585286/+files/LightdmDisplayLog.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
apport information
** Attachment added: "Dependencies.txt"
https://bugs.launchpad.net/bugs/1547077/+attachment/4585283/+files/Dependencies.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
apport information
** Attachment added: "DpkgLog.txt"
https://bugs.launchpad.net/bugs/1547077/+attachment/4585284/+files/DpkgLog.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1547077
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.
#
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1547077/+attachment/4585282/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in 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:
Oops, it looks like putting a short description obscures the attachment
names. You can hover the links with your mouse to see file names.
I'm willing to run other apps, but bug only appears after a while.
Logging out then in cures the bug.
The bug sometimes disappears on its own (it has
** Attachment added: "see main text"
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1547077/+attachment/4574630/+files/2016y02m18d_16h14m25s_0100Z_glyph-redrawn-bug.mp4
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
** Attachment added: "see main text"
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1547077/+attachment/4574628/+files/2016y02m16d_21h28m35s_0100Z_x_bug_affects_thunderbird_terminal.png
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to
** Attachment added: "see main text"
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1547077/+attachment/4574629/+files/2016y02m17d_18h08m27s_0100Z_x_bug_glyph_firefox_gnome_org.png
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in
** Attachment added: "see main text"
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1547077/+attachment/4574626/+files/2016y02m18d_16h05m35s_0100Z_same_corruption_on_different_windows.png
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to
** Attachment added: "see main text"
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1547077/+attachment/4574627/+files/2016y02m15d_13h16m33s_0100Z_bug_affects_superswitcher_terminal_and_more.png
--
You received this bug notification because you are a member of Ubuntu-X,
which is
** 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
** Attachment added: "see main text"
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1547077/+attachment/4574625/+files/2016y02m16d_21h41m14s_0100Z_whisker_menu_missing_glyphs.mp4
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in
** Attachment added: "see main text"
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1547077/+attachment/4574621/+files/2016y02m10d_18h42m34s_0100Z_wow_screen_flickers_and_most_glyphs_wrong_02.png
--
You received this bug notification because you are a member of Ubuntu-X,
which is
** Attachment added: "see main text"
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1547077/+attachment/4574616/+files/2016y02m10d_18h41m49s_0100Z_wow_screen_flickers_and_most_glyphs_wrong_00.png
--
You received this bug notification because you are a member of Ubuntu-X,
which is
** Attachment added: "see main text"
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1547077/+attachment/4574617/+files/2016y02m16d_21h31m52s_0100Z_x_bug_disabling_antialias_immediately_cures_problem.png
--
You received this bug notification because you are a member of Ubuntu-X,
which is
** Attachment added: "see main text"
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1547077/+attachment/4574615/+files/2016y02m05d_15h50m04s_0100Z_firefox_display_bug_major_stackoverflow.png
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed
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
** Attachment added: "see main text"
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1547077/+attachment/4574618/+files/2016y02m10d_18h42m18s_0100Z_wow_screen_flickers_and_most_glyphs_wrong_01.png
--
You received this bug notification because you are a member of Ubuntu-X,
which is
** Attachment added: "see main text"
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1547077/+attachment/4574619/+files/2016y02m10d_18h43m35s_0100Z_wow_screen_flickers_and_most_glyphs_wrong_03.png
--
You received this bug notification because you are a member of Ubuntu-X,
which is
@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
Public bug reported:
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
Just tried xubuntu 13.10 on the same laptop, keeping 12.10 on its partition to
boot on one or another as will.
Xubuntu 13.10 is freshly installed, not much customized but updates applied and
rebooted.
Kernel is 3.11.0-12-generic .
lsb_release -rd
Description:Ubuntu 13.10
Release:
Summary : interestingly, in a bare X session, xev does not react to
those hotkeys, while it reacts to other. Does it mean the problem lies
at X level ?
## General test
To isolate the problem, I logged in with an empty account running
OpenBox only (no full desktop environment) and ran xev.
Here
One more specific information : in bare OpenBox X session, none of these
keys have a visible effect handled by Ubuntu, except XF86WLAN.
Also, this laptop was sold with Windows, and there all function keys
work, including the brightness keys.
## kernel-level showkey test
I've tried
** Summary changed:
- Partially broken brightness hotkey handling.
+ Brightness hotkeys not seen by kernel on Asus n55s, other hotkeys ok.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-input-evdev in Ubuntu.
Public bug reported:
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
--
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/1042359
Title:
Partially broken brightness hotkey handling.
To manage notifications about this bug go to:
As written above, I had enabled X Updates as part of investigating
#987056 Suspend always hangs on Asus N55S, becomes really hot
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/987056
Issuing the following command:
sudo ppa-purge ppa:ubuntu-x-swat/x-updates
downgraded the packages to
* Reproducible : within minutes with external monitor, within weeks
without external monitor
Confirmed this happens a few times per month, exactly as stated in
comment 2.
Thus, this is definitely not *specific* to dual-head setup, but happens
much more often in that case.
Let's see this
** Description changed:
- Used Precise for weeks, with external monitor sometimes plugged, everything
ok.
- (Small drawback: boot fails with external monitor attached. Another issue.)
+ After batch software update on 2011-05-21, X started to freeze (as
+ defined on
The machine is running an nvidia optimus hardware, that is Intel + nVidia.
Bumblebee is installed on the machine, and works when used, but I don't use it.
As per https://wiki.ubuntu.com/X/Troubleshooting/Freeze
Problem: Freeze began after a system update
No kernel package update near the time
Since the beginning of the week, I have been working every day without
external monitor to avoid that bug.
It occurred again, still without external monitor. Exact same symptoms.
* Ctrl-Alt-F1 still does not switch to text console
* From another machine, ssh still works.
* From other machine
Public bug reported:
Used Precise for weeks, with external monitor sometimes plugged, everything ok.
(Small drawback: boot fails with external monitor attached. Another issue.)
Today I applied system update.
Now, whenever I plug in external monitor, desktop extends correctly on it.
After a
--
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/1002542
Title:
Xorg freeze minutes after plugging external monitor.
To manage notifications about this bug go to:
77 matches
Mail list logo
