Public bug reported:
Description:
this feature tracks the updates of mesa 3d for TGL support.
We will update the commitid list as necessary
Target Release: 20.10
Target version: TBD
** Affects: intel
Importance: Undecided
Status: New
** Affects: mesa (Ubuntu)
Importance:
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1852634/+attachment/5310165/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
apport information
** Tags added: apport-collected
** Description changed:
Ubuntu 19.10 with gnome-desktop
After upgrading from Ubuntu 19.04 to 19.10, window dialogs take a long
time to display. Sample dialogs include "Are you sure you want to delete
this file?" or "Do you want to
apport information
** Attachment added: "ShellJournal.txt"
https://bugs.launchpad.net/bugs/1852634/+attachment/5310166/+files/ShellJournal.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
Now I see the root cause of problem:
https://www.fujitsu.com/pl/products/computing/peripheral/scanners/scansnap/ix500/
Your scanner doesn't have FlatBed.
To workaround it you could use ADF feeder.
** Changed in: simple-scan (Ubuntu)
Status: Invalid => New
--
You received this bug
Thank you for the response Daniel. Attached is `journalctl -f` collected
while I reproduced the issue. It's worth noting that no log lines were
recorded at the times that the issue occurred.
** Attachment added: "journalctl-f.log"
apport information
** Attachment added: "GsettingsChanges.txt"
https://bugs.launchpad.net/bugs/1852634/+attachment/5310164/+files/GsettingsChanges.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
Launchpad has imported 24 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=1648475.
If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
** Tags added: eoan
--
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/1853374
Title:
pulseaudio disables GP107GL output every so often
Status in pulseaudio package in Ubuntu:
New
** Package changed: gdm3 (Ubuntu) => xorg-server (Ubuntu)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1853328
Title:
gdm-x-session loops printing its mode lines to syslog
Your Xorg logs are showing:
[ 4864.686] (WW) modeset(0): hotplug event: connector 93's link-state
is BAD, tried resetting the current mode. You may be leftwith a black
screen if this fails...
where connector 93 is the DisplayPort. Please try a different monitor
cable, or just replugging it.
**
Your kernel log also mentions problems with the same hardware:
[ 1723.813855] [drm:intel_dp_start_link_train [i915]] *ERROR* failed to enable
link training
[ 2612.326756] [drm:intel_dp_start_link_train [i915]] *ERROR* failed to enable
link training
--
You received this bug notification
** Tags added: wayland wayland-session
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1853357
Title:
display (whole computer?) hangs when I attempt to use DisplayLink with
Wayland
If a different monitor cable does not work then please try a different
monitor if you can. There is some kind of hardware fault here.
** Changed in: xorg-server (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Desktop
Packages,
[775834.395] (EE) glamor0: GL error: GL_OUT_OF_MEMORY in glTexSubImage
[775834.395] (WW) glamor: Failed to allocate 5x5 FBO due to GL_OUT_OF_MEMORY.
[775834.395] (WW) glamor: Expect reduced performance.
[776320.877] (EE) glamor0: GL error: GL_OUT_OF_MEMORY in glTexSubImage
[776320.877] (EE)
Tracking in:
https://errors.ubuntu.com/problem/af88d9cd45acf4632e47789e4661be6a47b4dbf1
** Tags added: bionic disco xenial
** Description changed:
+ https://errors.ubuntu.com/problem/af88d9cd45acf4632e47789e4661be6a47b4dbf1
+
+ ---
+
I'm using a Dell XPS 9380 ("developer edition") connected
*** This bug is a duplicate of bug 1853120 ***
https://bugs.launchpad.net/bugs/1853120
** This bug has been marked a duplicate of bug 1853120
Xorg crashes with SIGBUS in drmmode_load_cursor_argb_check
--
You received this bug notification because you are a member of Desktop
Packages,
Thank you for taking the time to report this bug and helping to make
Ubuntu better. It sounds like some part of the system has crashed. To
help us find the cause of the crash please follow these steps:
1. Look in /var/crash for crash files and if found run:
ubuntu-bug YOURFILE.crash
Then tell
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: xorg-server (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
Thank you for taking the time to report this bug and helping to make
Ubuntu better. It sounds like some part of the system has crashed. To
help us find the cause of the crash please follow these steps:
1. Look in /var/crash for crash files and if found run:
ubuntu-bug YOURFILE.crash
Then tell
*** This bug is a duplicate of bug 1853120 ***
https://bugs.launchpad.net/bugs/1853120
Public bug reported:
The Ubuntu Error Tracker has been receiving reports about a problem regarding
xorg-server. This problem was most recently seen with package version
2:1.20.5+git20191008-0ubuntu1,
** Summary changed:
- Fractional scaling has significant visible tearing on a 4k display in Xorg
sessions
+ Fractional scaling has significant visible tearing in Xorg sessions
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server
This change was made by a bot.
** Changed in: linux (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1852752
Title:
DPMS does not switch
** Tags added: xrandr-scaling
** Changed in: gnome-shell (Ubuntu)
Importance: Low => Medium
** Changed in: gnome-shell (Ubuntu)
Status: New => Confirmed
** Also affects: mutter (Ubuntu)
Importance: Undecided
Status: New
** Changed in: mutter (Ubuntu)
Status: New =>
** Tags added: eoan
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1852922
Title:
Internal microphone not being detected - Ubuntu 19.10, Kernel 5.3,
Laptop HP Envy 13, Realtek
** Summary changed:
- Xorg crashes with a bus error in OsLookupColor when using a second display
+ Xorg crashes with SIGBUS in drmmode_load_cursor_argb_check
** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu)
--
You received this bug notification because you are a member of Desktop
*** This bug is a duplicate of bug 1846398 ***
https://bugs.launchpad.net/bugs/1846398
Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1846398, so it is being marked as such. Please
Also, you won't get working graphics while 'nomodeset' is on your kernel
command line. Unless you need it as a workaround that word 'nomodeset'
should be removed.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
Please run:
apport-collect 1852864
to send us more information about the machine.
** Summary changed:
- Fractional Scaling shows a black bar
+ Fractional Scaling shows a black bar on secondary monitor
** Tags added: multimonitor
** Also affects: mutter (Ubuntu)
Importance: Undecided
Sounds like you're not getting a login screen, is that right?
It wouldn't be surprising given it's a rare and not well tested:
Intel(R) Core(TM) i5 CPU M 460 @ 2.53GHz
Please try editing /etc/gdm3/custom.conf and uncomment:
#WaylandEnable=false
then reboot.
** Package changed:
Please report the problem to the Gnome Shell developers here:
https://gitlab.gnome.org/GNOME/gnome-shell/issues
and then tell us the new bug ID.
** Also affects: mutter (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of
Since Xorg is using the modeset driver here I think this might be an
issue with the Raspberry Pi kernel driver(s)
** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu)
** Summary changed:
- DPMS does not switch off the monitor back light
+ DPMS does not switch off the monitor back light on
Also, have you tried rebooting since the problem started?
If the problem still persists then please attach your
/var/log/apt/history* file which contains the time period of 11-12
November.
** Package changed: gnome-shell (Ubuntu) => ubuntu
--
You received this bug notification because you are
Please also run:
apport-collect 1852634
to automatically attach system information.
** Changed in: gnome-shell (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
Does the problem affect Wayland sessions, Xorg sessions or both?
** Tags added: bionic
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1852173
Title:
GUI applications with root
Please open a Terminal window and run:
journalctl -f
Now with that window still visible, reproduce the bug again. What if any
new messages appear in the Terminal window during the pause?
** Tags added: eoan
** Tags added: regression-release
** Package changed: gnome-desktop (Ubuntu) =>
You have been subscribed to a public bug:
Ubuntu 19.10 with gnome-desktop
After upgrading from Ubuntu 19.04 to 19.10, window dialogs take a long
time to display. Sample dialogs include "Are you sure you want to delete
this file?" or "Do you want to save this file before quitting?". I can
I can see a couple of pixel-layout-related settings here:
dithering depth: auto
supported: auto, 6 bpc, 8 bpc
dithering mode: auto
supported: auto, off, static 2x2, dynamic 2x2, temporal
The nouveau kernel driver provides them regardless of the
*** This bug is a duplicate of bug 1849787 ***
https://bugs.launchpad.net/bugs/1849787
Xscreensaver is just a fullscreen window so I think this is probably
still bug 1849787.
** Package changed: gnome-shell (Ubuntu) => gnome-shell-extension-
ubuntu-dock (Ubuntu)
** This bug has been marked
Does the problem occur if you log into 'Ubuntu on Wayland' ?
** Also affects: xorg-server (Ubuntu)
Importance: Undecided
Status: New
** Changed in: xorg-server (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Desktop
One interesting observation is that your logs are saying that 60Hz is
the preferred native mode of the monitor:
[ 1165.229] (II) modeset(0): First detailed timing is preferred mode
[ 1165.229] (II) modeset(0): Preferred mode is native pixel format and refresh
rate
...
[ 1165.229] (II)
** Attachment added: "Comparison image"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1852166/+attachment/5310145/+files/comparison.png
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
I don't feel that a non-close-up photo could help, but here is one. From
a normal viewing distance, when higher than 60hz, the image seems to
have decreased brightness. Only on close up one can tell that it does
not appear to be brightness, but a wrong pixel pattern.
--
You received this bug
** Summary changed:
- Touchpad not working
+ Dell Inspiron 3558 touchpad stopped working in kernel 4.15.0-72 (but
4.15.0-70 is OK)
** Package changed: xorg (Ubuntu) => linux (Ubuntu)
** Tags added: regression-update
--
You received this bug notification because you are a member of Desktop
Public bug reported:
The touchpad is not detected by my Dell Inspiron 3000 series laptop,
this happened after my kernel was updated from 4.15.0-70 to 4.15.0-72.
If I enter Ubuntu Advanced Options to my previous kernel (4.15.0-70) my
touchpad works correctly.
ProblemType: Bug
DistroRelease:
[Expired for xorg-server (Ubuntu) because there has been no activity for
60 days.]
** Changed in: xorg-server (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
*** This bug is a duplicate of bug 1848741 ***
https://bugs.launchpad.net/bugs/1848741
Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1848741, so it is being marked as such. Please
** Tags added: eoan
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1852118
Title:
Notifications don't have sound
Status in GNOME Shell:
New
Status in gnome-shell package in
Sorry I can't see a problem in that screenshot. Can you provide more?
** Tags added: nouveai
** Tags removed: nouveai
** Tags added: nouveau
** Summary changed:
- Pixel pattern error in over
+ [nouveau] Pixel pattern error in over
** Package changed: xorg (Ubuntu) => gnome-shell (Ubuntu)
**
** Summary changed:
- [Aspire A315-21, Realtek ALC255, Black Headphone Out, Front] No sound at all
+ [Aspire A315-21, Realtek ALC255, Black Headphone Out, Front] No sound through
headphones
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed
** Package changed: xorg (Ubuntu) => ubuntu
--
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/1852117
Title:
non appare nessuna applicazione
Status in Ubuntu:
Incomplete
Bug
*** This bug is a duplicate of bug 1421808 ***
https://bugs.launchpad.net/bugs/1421808
Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1421808 / bug 1787332 / bug 1787338, so it is
I think most likely the cause here is an event from a mouse or keyboard
-- even if you're not touching them. Please try:
1. Unplug all mice and keyboards.
2. Wait for the screen to turn off.
3. Does it turn back on?
Similarly spurious wakeups could come from apps (please test with no
apps
** Package changed: xorg (Ubuntu) => linux (Ubuntu)
--
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/1852071
Title:
[HP ZBook Studio G5, Ubuntu 18.04.3 LTS] Brightness function keys
** Package changed: xorg (Ubuntu) => linux (Ubuntu)
--
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/1852083
Title:
[HP ZBook Studio G5, Ubuntu 18.04.3 LTS, bluetooth mouse] Choppy/laggy
Public bug reported:
If PC on (not in suspend), plugging in the power does not fail.
If PC in suspend, plugging in the power causes PC to shutdown.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: evince 3.28.4-0ubuntu1.2
ProcVersionSignature: Ubuntu 5.0.0-37.40~18.04.1-generic 5.0.21
*** This bug is a duplicate of bug 1697281 ***
https://bugs.launchpad.net/bugs/1697281
** This bug has been marked a duplicate of bug 1697281
[TOSHIBA NB515, Intel CedarTrail HDMI, Digital Out, HDMI] No sound at all
--
You received this bug notification because you are a member of
** Tags added: eoan
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1697281
Title:
[TOSHIBA NB515, Intel CedarTrail HDMI, Digital Out, HDMI] No sound at
all
Status in
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: alsa-driver (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alsa-driver in Ubuntu.
Although you are complete right about "I guess an udev rule to disable
Wayland for GMA500 is all that is needed."
--
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/1852023
Title:
Wayland
If you can write and test a udev rule that works then we can get it into
a future version of Mutter. So please open an upstream bug for that at:
https://gitlab.gnome.org/GNOME/mutter/issues
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed
Although you are completely right about "I guess an udev rule to disable
Wayland for GMA500 is all that is needed."
** Package changed: xorg (Ubuntu) => mutter (Ubuntu)
** Changed in: mutter (Ubuntu)
Importance: Undecided => Low
** Changed in: mutter (Ubuntu)
Status: New => Triaged
It appears GMA500 is the infamous Poulsbo with PowerVR GPU:
https://en.wikipedia.org/wiki/Intel_GMA#GMA_500
This means it is closed source and we can't support it :(
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
I think the more relevant thing to investigate here is the GUI used to
empty the trash... Are you doing it via the desktop icon or via a
Nautilus "Files" window?
Probably both gnome-shell and nautilus are pulseaudio clients one way or
the other.
** Tags added: eoan
** Changed in: pulseaudio
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: appstream (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to appstream in Ubuntu.
-- GitLab Migration Automatic Message --
This bug has been migrated to freedesktop.org's GitLab instance and has
been closed from further activity.
You can subscribe and participate further through the new bug through
this link to our GitLab instance:
(In reply to comment #63)
> For the first two options I think it could be useful to grep through all
> those dumps collected over the years and check which cards have this set.
Yeah, I'll try to have a look later on.
>
> Option 3 could definately tell if it's only used for a particular memory
>
Even more interesting, your trace actually has
[0] 1012.956817 MMIO32 R 0x100080 0xe100 PFB+0x80 => 0xe100
[0] 1012.956820 MMIO32 W 0x100080 0xe100 PFB+0x80 <= 0xe100
Which means that it _starts out_ at 0xe100. Was this trace done on a
clean boot, or had the nvidia module
For the first two options I think it could be useful to grep through all
those dumps collected over the years and check which cards have this
set.
Option 3 could definately tell if it's only used for a particular memory
configuration of this chip, or it's more general (e.g. first 2 options).
By
(In reply to comment #55)
> So something is initialized by the nvidia driver, which is not touched by
> nouveau but is required for correct operation.
>
> Is there a way I could help? Like dumping register states with/without the
> nvidia init?
You could do a mmiotrace of the nvidia driver. It's
I've wasted a lot of time with the mmio registers to find out why things
go slow. But it seems it's something else.
Just loading the nvidia kernel module without starting X is enough to
make nouveau go fast after kexec.
I did an mmio trace while loading the module, but it only wrote 140 to
0,
I've e-mailed the dump file.
I've put in 3 markers, one before starting xinit /usr/bin/urxvt, one in
urxvt before quiting, and one after xinit returned.
I hope it's useful. Thanks! I can try to repeat the same thing using the
nouveau driver, if needed.
--
You received this bug notification
I had the feeling that there's not much chance that the dump alone will
help. So I did some debugging on my own, after all it can't be that hard
if I have the hardware at hand to play with ;)
First I've collected all writes locations out from the dump, and ignored
the part which looked like a
The default Debian kernel is not very debug friendly, so I've dumped the ROMs
with nvagetbios. There are two versions, as I made a firmware update later to
see if it helps. (e-mailed)
The MMIO dumps are comming soon, tomorrow or so. This is a slow machine
and the kernel compile takes a while
BTW, interesting. In your VBIOS, it tells us to do
0xcbf2: 7a 80 00 10 00 00 00 00 e0 ZM_REG
R[0x100080] = 0xe000
Which is why that bit gets lost on resume (but not on kexec, since init
scripts don't run, since the adapter is already init'd). Good to know,
that means that
(In reply to comment #61)
> At the end I got what I wanted. The winner is:
> nvapoke 00100080 e100
>
> This register is e000 after suspend or after clean boot. So all this
> trouble only because of a single bit was not set ;(
Fantastic! I was secretly hoping that by ignoring the issue
I ignore if it's related, but my Dell D800 with nv28 burts many-many-many beeps
on boot until the grub menu displays. Feel free to ask any thing.
Regards
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-video-nouveau in
(In reply to Emil Velikov from comment #77)
> agpmode and modeset are not even remotely related I'm afraid. With 4.3
> onward one should be using nouveau.config="NvAGP=0" as documented [1]
>
> [1] http://nouveau.freedesktop.org/wiki/KernelModuleParameters/#config
Yes. The syntax given seems to
On Lubuntu 14.04.3 (I think it's Kernel 3.19.x) "nouveau.agpmode=0" also works,
although standby still doesn't seem to work.
What I want to note though, is, that activating the Shadow Framebuffer in
/etc/X11/xorg.conf.d/20-nouveau.conf results in a substantial performance
increase regarding
agpmode and modeset are not even remotely related I'm afraid. With 4.3
onward one should be using nouveau.config="NvAGP=0" as documented [1]
[1] http://nouveau.freedesktop.org/wiki/KernelModuleParameters/#config
--
You received this bug notification because you are a member of Desktop
Packages,
I reached to retreive my video bios version*:
cat /proc/driver/nvidia/cards/0
Model: GeForce4 4200 Go
IRQ: 11
Video BIOS: 04.28.20.31.c1
Card Type: AGP
DMA Size: 32 bits
DMA Mask: 0x
Maybe you will like to check against your own and tell me you need
something else from me.
* not that
(In reply to Ilia Mirkin from comment #64)
> (In reply to comment #63)
> >
> > Option 3 could definately tell if it's only used for a particular memory
> > configuration of this chip, or it's more general (e.g. first 2 options).
>
> I've fired off a question to NVIDIA, hopefully they'll
(In reply to Ilia Mirkin from comment #75)
> (In reply to AndrewK from comment #73)
> > (In reply to nv28m from comment #71)
> > > nouveau.agpmode=0 seems to work here too, also after comming back from
> > > suspend.
> > >
> > The parameter name seems to be changed. nouveau.modeset=0 is what
(In reply to nv28m from comment #71)
> nouveau.agpmode=0 seems to work here too, also after comming back from
> suspend.
>
> Still I think I'm stuck with the modesetting driver with the bit 24 hack in
> boot/suspend scripts. The scrolling and rxvt performance is just better.
The parameter name
(In reply to AndrewK from comment #73)
> (In reply to nv28m from comment #71)
> > nouveau.agpmode=0 seems to work here too, also after comming back from
> > suspend.
> >
> > Still I think I'm stuck with the modesetting driver with the bit 24 hack in
> > boot/suspend scripts. The scrolling and
Guys, if I can help in any maneer I'd be glad. I want you to know my
video adapter is flashed with a bios update I found long time ago on
dell's site (in my memory, this was a bios update for Windows).
--
You received this bug notification because you are a member of Desktop
Packages, which is
nouveau.agpmode=0 seems to work here too, also after comming back from
suspend.
Still I think I'm stuck with the modesetting driver with the bit 24 hack
in boot/suspend scripts. The scrolling and rxvt performance is just
better.
--
You received this bug notification because you are a member of
Hi, I do not know if it may be still relevant after nv28m dicoveries but
here's some quick info (with a debian testing fully updated a month
ago).
Booting with plain nouveau (agp v2 4x): distorted mouse, nothing new
here :(
I tried to boot the following kernel command lines:
*
Yes, it was taken after several attempts, that's why it was already set.
I've made a better dump and sent it in e-mail now. According to this
it's set the first time it's written to.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
I just discovered this bug as I acquired a Dell Inspiron 8500 a few
weeks back and ran into the same problem. In fact, on my machine (same
nVidia graphics), the problem even seems worse: Any attempt at using the
nouveau driver so far has not only produced the distortions described by
the original
I ended in Ubuntu 12.04 with latest nvidia-96(-updates maybe). The
Laptop sleeps now for weeks and I won't wake it up. I Just can say that
once I admitted that vino won't work with desktop effects, I decided to
use this laptop with gnome-shell no-effects only, and with the latest
drivers state
Doing a suspend to RAM restores the original trashing behaviour. I'm not
sure, but maybe the screen update is slower as well now.
This is a Dell D800:
01:00.0 VGA compatible controller: NVIDIA Corporation NV28M [GeForce4 Ti 4200
Go AGP 8x] (rev a1)
X.Org X Server 1.15.1
Release Date: 2014-04-13
I also have this problem. Everything unaccelerated comes up as trash,
even on the kernel framebuffer (if acceleration was switched off). Or
for example I can see most of the graphics ok, but if I use ShadowFB
then the whole screen is unusable. And the cursor is garbage too most of
the time.
This
** Changed in: nouveau
Status: Confirmed => Unknown
** Bug watch added:
gitlab.freedesktop.org/xorg/driver/xf86-video-nouveau/issues #29
https://gitlab.freedesktop.org/xorg/driver/xf86-video-nouveau/issues/29
--
You received this bug notification because you are a member of Desktop
** Summary changed:
- Screen brightness adjustment delay
+ Screen brightness adjustment delay in Xorg sessions only
** Package changed: linux (Ubuntu) => mutter (Ubuntu)
** Changed in: mutter (Ubuntu)
Status: Confirmed => New
** Also affects: xorg-server (Ubuntu)
Importance:
** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu)
** Changed in: xorg-server (Ubuntu)
Status: Incomplete => Won't Fix
** Changed in: unity (Ubuntu)
Status: Incomplete => Won't Fix
--
You received this bug notification because you are a member of Desktop
Packages, which is
I can also confirm that on another laptop that I upgraded from Ubuntu
18.04 -> 18.10 -> 19.04 -> 19.10 with the following versions that the
username was stored (at some point) successfully, and I do not need to
enter it when joining the vpn.
network-manager-openconnect:
Installed: 1.2.4-2ubuntu
You have been subscribed to a public bug:
Every time I adjust my laptop's screen brightness using the dedicated
brightness keys, there is a substantial delay between when I press the
button and the screen adjusts. Sometimes it even "twitches" and
decreasing the brightness by tapping the button
... and if so then please try logging into "Ubuntu on Wayland" instead.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1853412
Title:
Poor performance with fractional scaling factors
Please avoid reporting multiple issues in a single bug.
The tearing issue is bug 1846398 already so the remaining issues are
"Ubuntu operates slow with system apps and 3rd party apps; system hangs
and crashes; and more". Are you saying Ubuntu is only slow when you are
using fractional scaling?
1 - 100 of 212 matches
Mail list logo
