** Changed in: xorg-server (Ubuntu)
Importance: Undecided => Critical
** Changed in: xorg-server (Ubuntu)
Importance: Critical => Low
** Changed in: xorg-server (Ubuntu)
Status: New => Triaged
--
You received this bug notification because you are a member of Ubuntu-X,
which is subs
** Also affects: xorg-server via
https://gitlab.freedesktop.org/xorg/xserver/-/issues/1008
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/187
Reported, issue ID 1008:
https://gitlab.freedesktop.org/xorg/xserver/-/issues/1008
** Bug watch added: gitlab.freedesktop.org/xorg/xserver/-/issues #1008
https://gitlab.freedesktop.org/xorg/xserver/-/issues/1008
--
You received this bug notification because you are a member of Ubuntu-X,
which
Please describe in more detail what kind of problem you are
experiencing.
** Package changed: xorg (Ubuntu) => ubuntu
** Changed in: ubuntu
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
https:/
** Summary changed:
- [nouveau] Xorg crashed with SIGABRT in disk_cache_has_key()
+ [nouveau] Xorg crashed with SIGABRT in disk_cache_has_key() from
can_skip_compile.part()
** Summary changed:
- [nouveau] Xorg crashed with SIGABRT in disk_cache_has_key() from
can_skip_compile.part()
+ [nouveau
[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 Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
https://bugs.launc
[+Subscribed Hans]
Hans, I think the issue is caused by:
[drm:intel_dsi_vbt_gpio_init [i915]] *ERROR* Failed to own gpio for panel
control
Would be appreciated if you can take a look.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in Ubu
Also, please attach the files from:
~/.local/share/xorg/
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1871112
Title:
[vboxvideo] VirtualBox not starting
To manage notifications abou
Sounds like either bug 1870726 or bug 1849883. Do you think either of
those describe the problem you are facing?
** Summary changed:
- VirtualBox not starting
+ [vboxvideo] VirtualBox not starting
** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu)
** Changed in: xorg-server (Ubuntu)
Possibly related: bug 1870740
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1870637
Title:
20.04beta: Cannot set 3840x2160
To manage notifications about this bug go to:
https://bugs.lau
Possibly related: bug 1870637
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1870740
Title:
Refresh Rate
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+
Can you please attach a photo showing where your HDMI cable is plugged
into the computer?
As far as I can tell, if it's plugged into the motherboard then this
would not be a bug. It looks like that model of motherboard does not
support 4K at 60Hz, but is limited to 24Hz or 30Hz.
** Changed in: nv
Maybe repeat the problem a few times and then attach here all your most
recent Xorg log files from:
~/.local/share/xorg/
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1870779
Title:
[
Weird. The XorgLog shows that HDMI is talking to the wrong driver so I
assumed that meant it is plugged into the wrong GPU...
Does your computer not have multiple HDMI ports? If not then it looks
like there's a problem with how the Nvidia driver is installed here.
- or -
The modeset driver might
Marking the bug as Invalid since apparently that readme file only
applies to Windows.
Even the Linux driver 440 does in fact support support Kepler cards.
** Changed in: nvidia-graphics-drivers-418 (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a me
** Information type changed from Private Security to Public
--
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/1869868
Title:
bug
To manage notifications about this bug go to:
https://bugs.launchpa
So although everything is working fine in windows and ubuntu 19.10;
i swapped my onkyo receiver for a newer Denon hdmi 2.0 receiver - the
AVR-X1400H; same issue.
i connected to pc directly to the screen; same issue
i switched to a different brand of premium hdmi 2.0 cable; same issue.
i've also
This bug was fixed in the package linux - 4.15.0-96.97
---
linux (4.15.0-96.97) bionic; urgency=medium
* CVE-2020-8834
- KVM: PPC: Book3S HV: Factor fake-suspend handling out of
kvmppc_save/restore_tm
- KVM: PPC: Book3S PR: Move kvmppc_save_tm/kvmppc_restore_tm to sepa
This bug was fixed in the package linux-restricted-modules -
4.15.0-96.97
---
linux-restricted-modules (4.15.0-96.97) bionic; urgency=medium
* Master version: 4.15.0-96.97
-- Thadeu Lima de Souza Cascardo Tue, 31 Mar
2020 23:28:45 -0300
--
You received this bug notification be
Hi,
On the videocard a premium hdmi2.0 is plugged in which connects to my
hdmi2.0 Onkyo TX-NR646 amp, which acts as a switch for my windows pc and
my ubuntu pc's.
The Onkyo hdmi2.0 out is connected to my Philips 49inch 4K TV.
I will try to connect ubuntu 20.04 to my tv directly and report back he
I just hit another GPU HANG, this time with the "intel" driver instead
of the "modesetting" driver. The kernel log file (/var/log/kern.log)
shows:
Apr 6 08:59:36 tower kernel: [44387.837794]
[drm] GPU HANG: ecode 9:0:0x85da, in Xorg [1751],
rea
Public bug reported:
Focal Fossa beta release does not booting correctly to the desktop.
Machine: VirtualBox 6.0.18 r136238, Graphics Controller: VBoxSVGA or VBoxsVGA
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.2
Hi Daniel,
thanks for your support.
1) The /var/crash directory is empty.
2) The last whoopsie problem was reported on March 27th and is most likely from
the Ubuntu 19.10 system on the same machine.
3) The /etc/apport/crashdb.conf for focal fossa does not include the
"problem_types" statement.
** Changed in: xserver
Status: Unknown => New
--
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/1863874
Title:
Backport GetFB2 ioctl, re-enable CCS compression for intel
To manage notificat
Good. Just to emphasize, Geode doesn't make sense on distros where the
base level for i386 is 686-PAE, since none of the Geodes have PAE (most
Geodes are i586, except for Geode LX which is 686 without PAE).
--
You received this bug notification because you are a member of Ubuntu-X,
which is subsc
Hmm, realized that since this happens on intel gen9 only and with i965
dri driver, it doesn't affect focal anymore since it uses iris dri
driver by default. So the patch to disable CCS compression could just be
dropped anyway.
** Bug watch added: gitlab.freedesktop.org/xorg/xserver/issues #33
h
Please start by running 'top' to see if any processes are using high
CPU. Please let us know what you find.
Also, your kernel seems to be crashing a lot in the nouveau driver so it
might be a good idea to try the proprietary Nvidia driver instead. Look
in 'Additional Drivers' which you might find
*** This bug is a duplicate of bug 1870758 ***
https://bugs.launchpad.net/bugs/1870758
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 1870758, so it is being marked as such. Please look
libdrm 2.4.101 synced, not accepted yet
** Also affects: mesa (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: libdrm (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: xorg-server (Ubuntu Focal)
Importance: Undecided
Status: New
**
** Summary changed:
- Ubuntu 20.04 Top bar - white residual arrows
+ [vmwgfx] Ubuntu 20.04 Top bar - white residual arrows
** Summary changed:
- [vmwgfx] Ubuntu 20.04 Top bar - white residual arrows
+ [vmwgfx] [vmware] Ubuntu 20.04 Top bar - white residual arrows
** Also affects: xserver-xorg-v
Possibly related: https://gitlab.gnome.org/GNOME/mutter/-/issues/774
** Package changed: xorg-server (Ubuntu) => mutter (Ubuntu)
** Bug watch added: gitlab.gnome.org/GNOME/mutter/-/issues #774
https://gitlab.gnome.org/GNOME/mutter/-/issues/774
--
You received this bug notification because yo
Debian dropped what was on their list.
** Changed in: xf86-input-mtrack (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-trident in Ubuntu.
https://bugs.launchpad.net/bugs/1772588
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
Can you please try some older kernels to see if the problem really is
new in 5.3?
https://kernel.ubuntu.com/~kernel-ppa/mainline/?C=M;O=D
** Package changed: xorg (Ubuntu) => linux (Ubuntu)
** Changed in: linux (Ubuntu)
Status: New => Incomplete
--
You received this bug notification bec
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
Is something really crashing or just nothing is appearing on screen?
I can see two problems here:
1. You have the Nvidia driver installed but Xorg is not using it; and
2. It sounds like some modes are out of range:
[64.220] (--) modeset(0): HDMI max TMDS frequency 30KHz
[64.220] (II
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
Please don't use the 'intel' driver. It is old and unsupported.
** Package changed: xorg (Ubuntu) => xserver-xorg-video-intel (Ubuntu)
** Changed in: xserver-xorg-video-intel (Ubuntu)
Status: New => Won't Fix
** No longer affects: gnome-shell (Ubuntu)
--
You received this bug notificati
I can see two issues:
1. The 4K monitor is not plugged into the Nvidia card. Is that right?
2. The Radeon GPU it is plugged into is refusing some modes (because
they're out of range?):
[18.036] (--) modeset(0): HDMI max TMDS frequency 30KHz
[18.036] (II) modeset(0): Not using default
[18.036] (II) modeset(0): Not using default mode "3840x2160" (bad
mode clock/interlace/doublescan)
** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
https://bugs.launch
*** This bug is a duplicate of bug 1867613 ***
https://bugs.launchpad.net/bugs/1867613
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 1867613, so it is being marked as such. Please look
** Package changed: ubuntu => xorg (Ubuntu)
--
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/1871029
Title:
Ubuntu on ASUS Zenbook UX334F very bad battery performance
To manage notifications abou
You have been subscribed to a public bug:
(I didn't install the nvidia display drivers to avoid this bug
(https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1850439), but I
have very bad battery performance. From full charge my pc takes two
hours to discharge.
ProblemType: Bug
DistroRelease: Ub
** Attachment added: "Logfile created with sudo journalctl -b 0 after login
attempt"
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1870779/+attachment/5347536/+files/journal_1870779.log
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to x
Please report it upstream:
https://gitlab.freedesktop.org/groups/xorg/-/issues
and then tell us the new bug ID.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1870524
Title:
fallback
** Summary changed:
- Xorg crashed with SIGABRT
+ [nouveau] Xorg crashed with SIGABRT
** Summary changed:
- [nouveau] Xorg crashed with SIGABRT
+ [nouveau] Xorg crashed with SIGABRT in disk_cache_has_key()
--
You received this bug notification because you are a member of Ubuntu-X,
which is sub
** Also affects: nvidia-graphics-drivers-390 (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers-390 in Ubuntu.
https://bugs.launchpad.net/bugs/1866936
Title:
kernel pack
Public bug reported:
In xserver-xorg-video-ati the suggested firmware-amd-graphics was
dropped because the firmware is part of the linux-firmware package in
Ubuntu and since I just ran up on it I thought I would report it so that
people are not searching for firmware-amd-graphics for no reason at
48 matches
Mail list logo
