[Ubuntu-x-swat] [Bug 1870524] Re: fallback to SW cursor on GPU hotplug

2020-04-06 Thread Aleksander Miera
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 is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1870524

Title:
  fallback to SW cursor on GPU hotplug

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1870524/+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 1869868] Re: bug

2020-04-06 Thread Daniel van Vugt
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://bugs.launchpad.net/bugs/1869868

Title:
  bug

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/1869868/+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 1870988] Re: [nouveau] Xorg crashed with SIGABRT in disk_cache_has_key() from can_skip_compile.part()

2020-04-06 Thread Daniel van Vugt
** 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] Xorg crashed with SIGABRT in disk_cache_has_key() from 
can_skip_compile.part() from _mesa_glsl_compile_shader()

** 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 xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1870988

Title:
  [nouveau] Xorg crashed with SIGABRT in disk_cache_has_key() from
  can_skip_compile.part() from _mesa_glsl_compile_shader()

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1870988/+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 1862225] Re: the laptop freeze

2020-04-06 Thread Launchpad Bug Tracker
[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.launchpad.net/bugs/1862225

Title:
  the laptop freeze

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1862225/+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 1860754] Re: ASUS T100HAN boots to a blank screen with a cursor [i965: Failed to submit batchbuffer: Input/output error]

2020-04-06 Thread Kai-Heng Feng
[+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 Ubuntu.
https://bugs.launchpad.net/bugs/1860754

Title:
  ASUS T100HAN boots to a blank screen with a cursor [i965: Failed to
  submit batchbuffer: Input/output error]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1860754/+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 1871112] Re: [vboxvideo] VirtualBox not starting

2020-04-06 Thread Daniel van Vugt
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 about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1871112/+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 1871112] Re: [vboxvideo] VirtualBox not starting

2020-04-06 Thread Daniel van Vugt
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)
   Status: New => 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/1871112

Title:
  [vboxvideo] VirtualBox not starting

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1871112/+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 1870637] Re: 20.04beta: Cannot set 3840x2160

2020-04-06 Thread Daniel van Vugt
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.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-435/+bug/1870637/+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 1870740] Re: Refresh Rate

2020-04-06 Thread Daniel van Vugt
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/+source/nvidia-graphics-drivers-440/+bug/1870740/+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 1870637] Re: 20.04beta: Cannot set 3840x2160

2020-04-06 Thread Daniel van Vugt
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: nvidia-graphics-drivers-435 (Ubuntu)
   Status: New => Incomplete

** Changed in: xorg-server (Ubuntu)
   Status: New => Incomplete

-- 
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.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-435/+bug/1870637/+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 1870779] Re: [nvidia] Ubuntu 20.04 beta: Blank/black screen after login

2020-04-06 Thread Daniel van Vugt
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:
  [nvidia] Ubuntu 20.04 beta: Blank/black screen after login

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-440/+bug/1870779/+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 1870637] Re: 20.04beta: Cannot set 3840x2160

2020-04-06 Thread Daniel van Vugt
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 be refusing high bandwidth modes prematurely?

[18.036] (--) modeset(0): HDMI max TMDS frequency 30KHz
[18.036] (II) modeset(0): Not using default mode "3840x2160" (bad mode 
clock/interlace/doublescan)
[18.036] (II) modeset(0): Not using default mode "2560x1440" (bad mode 
clock/interlace/doublescan)

** Also affects: nvidia-graphics-drivers-435 (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: xorg-server (Ubuntu)
   Status: Incomplete => New

-- 
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.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-435/+bug/1870637/+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 1870915] Re: Nvidia driver 418 for Focal doesn't support Kepler cards

2020-04-06 Thread Jose Gómez
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 member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers-418 in Ubuntu.
https://bugs.launchpad.net/bugs/1870915

Title:
  Nvidia driver 418 for Focal doesn't support Kepler cards

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-418/+bug/1870915/+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 1869868] Re: bug

2020-04-06 Thread Seth Arnold
** 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.launchpad.net/ubuntu/+source/xorg/+bug/1869868/+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 1870637] Re: 20.04beta: Cannot set 3840x2160

2020-04-06 Thread Paul Berkx
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 installed the ubuntu budgie flavor beta; same issue.

I think it's pretty safe to say, this not a local hardware issue at this
point.

-- 
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.launchpad.net/ubuntu/+source/xorg-server/+bug/1870637/+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 1854485] Re: Introduce the new NVIDIA 440 series, and add 5.4 Linux compatibility to the 340 and 390 series

2020-04-06 Thread Launchpad Bug Tracker
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 separate 
file
- KVM: PPC: Book3S PR: Add guest MSR parameter for
  kvmppc_save_tm()/kvmppc_restore_tm()

linux (4.15.0-94.95) bionic; urgency=medium

  * bionic/linux: 4.15.0-94.95 -proposed tracker (LP: #1868984)

  * Missing wireless network interface after kernel 5.3.0-43 upgrade with eoan
(LP: #1868442)
- iwlwifi: mvm: Do not require PHY_SKU NVM section for 3168 devices

linux (4.15.0-93.94) bionic; urgency=medium

  * bionic/linux: 4.15.0-93.94 -proposed tracker (LP: #1868764)

  * quotactl04 from ubuntu_ltp_syscalls failed with B (LP: #1868665)
- ext4: fix mount failure with quota configured as module

linux (4.15.0-92.93) bionic; urgency=medium

  * bionic/linux: 4.15.0-92.93 -proposed tracker (LP: #1867272)

  * Packaging resync (LP: #1786013)
- [Packaging] resync getabis
- [Packaging] update helper scripts

  * Introduce the new NVIDIA 440 series, and add 5.4 Linux compatibility to the
340 and 390 series (LP: #1854485)
- [Packaging] NVIDIA -- add support for the 435 and the 440 series

  * Stop using get_scalar_status command in Dell AIO uart backlight driver
(LP: #1865402)
- SAUCE: platform/x86: dell-uart-backlight: add get_display_mode command

  * Bionic update: upstream stable patchset 2020-03-12 (LP: #1867194)
- RDMA/core: Fix locking in ib_uverbs_event_read
- gpio: zynq: Report gpio direction at boot
- arm64: ptrace: nofpsimd: Fail FP/SIMD regset operations
- KVM: arm: Fix DFSR setting for non-LPAE aarch32 guests
- KVM: arm: Make inject_abt32() inject an external abort instead
- mtd: onenand_base: Adjust indentation in onenand_read_ops_nolock
- mtd: sharpslpart: Fix unsigned comparison to zero
- padata: fix null pointer deref of pd->pinst
- Input: synaptics - switch T470s to RMI4 by default
- Input: synaptics - enable SMBus on ThinkPad L470
- Input: synaptics - remove the LEN0049 dmi id from topbuttonpad list
- ALSA: hda/realtek - Fix silent output on MSI-GL73
- ALSA: usb-audio: Apply sample rate quirk for Audioengine D1
- arm64: cpufeature: Set the FP/SIMD compat HWCAP bits properly
- ALSA: usb-audio: sound: usb: usb true/false for bool return type
- ext4: don't assume that mmp_nodename/bdevname have NUL
- ext4: fix support for inode sizes > 1024 bytes
- ext4: fix checksum errors with indexed dirs
- ext4: add cond_resched() to ext4_protect_reserved_inode
- ext4: improve explanation of a mount failure caused by a misconfigured
  kernel
- Btrfs: fix race between using extent maps and merging them
- btrfs: ref-verify: fix memory leaks
- btrfs: print message when tree-log replay starts
- btrfs: log message when rw remount is attempted with unclean tree-log
- arm64: ssbs: Fix context-switch when SSBS is present on all CPUs
- perf/x86/amd: Add missing L2 misses event spec to AMD Family 17h's event 
map
- IB/hfi1: Close window for pq and request coliding
- IB/rdmavt: Reset all QPs when the device is shut down
- RDMA/rxe: Fix soft lockup problem due to using tasklets in softirq
- RDMA/core: Fix protection fault in get_pkey_idx_qp_list
- s390/time: Fix clk type in get_tod_clock
- perf/x86/intel: Fix inaccurate period in context switch for auto-reload
- hwmon: (pmbus/ltc2978) Fix PMBus polling of MFR_COMMON definitions.
- jbd2: move the clearing of b_modified flag to the journal_unmap_buffer()
- jbd2: do not clear the BH_Mapped flag when forgetting a metadata buffer
- KVM: x86/mmu: Fix struct guest_walker arrays for 5-level paging

  * Bionic update: upstream stable patchset 2020-03-09 (LP: #1866678)
- kernel/module: Fix memleak in module_add_modinfo_attrs()
- media: iguanair: fix endpoint sanity check
- x86/cpu: Update cached HLE state on write to TSX_CTRL_CPUID_CLEAR
- iwlwifi: mvm: fix NVM check for 3168 devices
- sparc32: fix struct ipc64_perm type definition
- cls_rsvp: fix rsvp_policy
- gtp: use __GFP_NOWARN to avoid memalloc warning
- l2tp: Allow duplicate session creation with UDP
- net: hsr: fix possible NULL deref in hsr_handle_frame()
- net_sched: fix an OOB access in cls_tcindex
- bnxt_en: Fix TC queue mapping.
- tcp: clear tp->total_retrans in tcp_disconnect()
- tcp: clear tp->delivered in tcp_disconnect()
- tcp: clear tp->data_segs{in|out} in tcp_disconnect()
- tcp: clear tp->segs_{in|out} in tcp_disconnect()
- rxrpc: Fix insufficient receive notification generation
- rxrpc: Fix NULL pointer deref due to call->conn being cleared on 
disconnect
- media: uvcvideo: Avoid cyclic entity chains due to malformed USB 
descriptors
- mfd: 

[Ubuntu-x-swat] [Bug 1854485] Re: Introduce the new NVIDIA 440 series, and add 5.4 Linux compatibility to the 340 and 390 series

2020-04-06 Thread Launchpad Bug Tracker
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 because you are a member of Ubuntu-X,
which is subscribed to nvidia-settings in Ubuntu.
https://bugs.launchpad.net/bugs/1854485

Title:
  Introduce the new NVIDIA 440 series, and add 5.4 Linux compatibility
  to the 340 and 390 series

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1854485/+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 1870637] Re: 20.04beta: Cannot set 3840x2160

2020-04-06 Thread Paul Berkx
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 here this 
evening.
This however is no solution for me since i have 1 4K screen and two pc's and 
want my amp to act as the switch for both pc's

-- 
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.launchpad.net/ubuntu/+source/xorg-server/+bug/1870637/+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 1724047] Re: xserver terminates frequently, journal says drm/i915: Resetting chip after gpu hang

2020-04-06 Thread John Neffenger
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],
reason: Hang on rcs0, action: reset
i915 :00:02.0: Resetting rcs0 after gpu hang
[drm:gen8_reset_engines [i915]] *ERROR* rcs0: reset request timeout
i915 :00:02.0: Resetting chip after gpu hang
asynchronous wait on fence i915:compiz[3304]/1:56366 timed out
[drm:gen8_reset_engines [i915]] *ERROR* rcs0: reset request timeout
[drm:i915_reset [i915]] *ERROR* Failed to reset chip: -5

Now I will try with the hardware acceleration disabled, still using the
"intel" driver, as follows (/etc/X11/xorg.conf):

---
# Tries "intel" instead of "modesetting" driver to fix GPU HANG
# https://bugs.launchpad.net/ubuntu/+source/xorg-server-hwe-16.04/+bug/1724047
Section "Device"
Identifier "Intel Graphics"
Driver "intel"
# Disables acceleration
Option "NoAccel" "True"
# Disables only 3D acceleration (Direct Rendering Infrastructure)
# Option "DRI" "False"
EndSection
---

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server-hwe-16.04 in Ubuntu.
https://bugs.launchpad.net/bugs/1724047

Title:
  xserver terminates frequently, journal says drm/i915: Resetting chip
  after gpu hang

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server-hwe-16.04/+bug/1724047/+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 1871112] [NEW] VirtualBox not starting

2020-04-06 Thread Marcin
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.27
Uname: Linux 5.4.0-21-generic x86_64
ApportVersion: 2.20.11-0ubuntu22
Architecture: amd64
CasperVersion: 1.442
Date: Mon Apr  6 13:07:07 2020
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 InnoTek Systemberatung GmbH VirtualBox Graphics Adapter [80ee:beef] (prog-if 
00 [VGA controller])
   Subsystem: VMware VirtualBox Graphics Adapter [15ad:0405]
LiveMediaBuild:
 
Lsusb:
 Bus 002 Device 002: ID 80ee:0031 VirtualBox USB CD-ROM
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Lsusb-t:
 /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 5000M
 |__ Port 1: Dev 2, If 0, Class=Mass Storage, Driver=usb-storage, 5000M
 /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/8p, 480M
 |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M
MachineType: innotek GmbH VirtualBox
ProcEnviron:
 TERM=linux
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz boot=casper noprompt splash -- 
locale=en_US
SourcePackage: xorg
Symptom: display
Title: Xorg crash
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/01/2006
dmi.bios.vendor: innotek GmbH
dmi.bios.version: VirtualBox
dmi.board.name: VirtualBox
dmi.board.vendor: Oracle Corporation
dmi.board.version: 1.2
dmi.chassis.type: 1
dmi.chassis.vendor: Oracle Corporation
dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
dmi.product.family: Virtual Machine
dmi.product.name: VirtualBox
dmi.product.version: 1.2
dmi.sys.vendor: innotek GmbH
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.100-4
version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.2-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

** Affects: xorg (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug crash focal 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/1871112

Title:
  VirtualBox not starting

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1871112/+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 1870779] Re: [nvidia] Ubuntu 20.04 beta: Blank/black screen after login

2020-04-06 Thread Michael
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. So there's nothing I can comment out.

Any other things I can do? I have some spare time these days, so I'm
willing to do, whatever it takes.

Regards
Michael

-- 
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:
  [nvidia] Ubuntu 20.04 beta: Blank/black screen after login

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-440/+bug/1870779/+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 1863874] Re: Backport GetFB2 ioctl, re-enable CCS compression for intel

2020-04-06 Thread Bug Watch Updater
** 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 notifications about this bug go to:
https://bugs.launchpad.net/xserver/+bug/1863874/+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 1772588] Re: Remove obsolete X11 drivers from the archive

2020-04-06 Thread Martin-Éric Racine
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 subscribed to xserver-xorg-video-trident in Ubuntu.
https://bugs.launchpad.net/bugs/1772588

Title:
  Remove obsolete X11 drivers from the archive

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xf86-input-mtrack/+bug/1772588/+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 1863874] Re: Backport GetFB2 ioctl, re-enable CCS compression for intel

2020-04-06 Thread Timo Aaltonen
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
   https://gitlab.freedesktop.org/xorg/xserver/issues/33

** Also affects: xserver via
   https://gitlab.freedesktop.org/xorg/xserver/issues/33
   Importance: Unknown
   Status: Unknown

-- 
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 notifications about this bug go to:
https://bugs.launchpad.net/xserver/+bug/1863874/+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 1871029] Re: Ubuntu on ASUS Zenbook UX334F very bad battery performance

2020-04-06 Thread Daniel van Vugt
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 in the main app list, or
under 'Software & Updates'.

** Package changed: xorg (Ubuntu) => linux (Ubuntu)

** Summary changed:

- Ubuntu on ASUS Zenbook UX334F very bad battery performance
+ [nouveau] Ubuntu on ASUS Zenbook UX334F very bad battery performance

** Tags added: nouveau

-- 
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:
  [nouveau] Ubuntu on ASUS Zenbook UX334F very bad battery performance

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1871029/+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 1870929] Re: [nvidia] Display Scaling causes monitors to sleep

2020-04-06 Thread Daniel van Vugt
*** 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 at
the other bug report to see if there is any missing information that you
can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report. Feel free to continue to report any other bugs you may
find.


** Summary changed:

- Display Scaling causes monitors to sleep
+ [nvidia] Display Scaling causes monitors to sleep

** Tags added: nvidia

** Package changed: xorg (Ubuntu) => mutter (Ubuntu)

** Also affects: nvidia-graphics-drivers-440 (Ubuntu)
   Importance: Undecided
   Status: New

** This bug has been marked a duplicate of bug 1870758
   [nvidia] Screen scaling results in monitor power save state

-- 
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/1870929

Title:
  [nvidia] Display Scaling causes monitors to sleep

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1870929/+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 1863874] Re: Backport GetFB2 ioctl

2020-04-06 Thread Timo Aaltonen
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

** Also affects: linux (Ubuntu Focal)
   Importance: Undecided
 Assignee: Timo Aaltonen (tjaalton)
   Status: Fix Released

** Changed in: mesa (Ubuntu Focal)
 Assignee: (unassigned) => Timo Aaltonen (tjaalton)

** Changed in: libdrm (Ubuntu Focal)
 Assignee: (unassigned) => Timo Aaltonen (tjaalton)

** Changed in: xorg-server (Ubuntu Focal)
 Assignee: (unassigned) => Timo Aaltonen (tjaalton)

** Changed in: libdrm (Ubuntu Focal)
   Status: New => In Progress

** Summary changed:

- Backport GetFB2 ioctl
+ Backport GetFB2 ioctl, re-enable CCS compression for intel

-- 
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 notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/1863874/+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 1870523] Re: [vmwgfx] Ubuntu 20.04 Top bar - white residual arrows

2020-04-06 Thread Daniel van Vugt
** 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-video-vmware (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: gnome-shell (Ubuntu)
   Status: Incomplete => New

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-vmware in Ubuntu.
https://bugs.launchpad.net/bugs/1870523

Title:
  [vmwgfx] [vmware] Ubuntu 20.04 Top bar - white residual arrows

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1870523/+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 1870823] Re: temporary mouse freeze on sticky edge between displays

2020-04-06 Thread Daniel van Vugt
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 you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1870823

Title:
  temporary mouse freeze on sticky edge between displays

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1870823/+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 1772588] Re: Remove obsolete X11 drivers from the archive

2020-04-06 Thread Timo Aaltonen
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

Title:
  Remove obsolete X11 drivers from the archive

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xf86-input-mtrack/+bug/1772588/+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 1870779] Re: Ubuntu 20.04 beta: Blank/black screen after login

2020-04-06 Thread Daniel van Vugt
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 us the ID of the newly-created bug.

2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where
ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine.
Do you find any links to recent problems on that page? If so then please
send the links to us.

3. If step 2 also failed then apply the workaround from bug 994921,
reboot, reproduce the crash, and retry step 1.

Please take care to avoid attaching .crash files to bugs as we are
unable to process them as file attachments. It would also be a security
risk for yourself.

** Tags added: nvidia

** Summary changed:

- Ubuntu 20.04 beta: Blank/black screen after login 
+ [nvidia] Ubuntu 20.04 beta: Blank/black screen after login

** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu)

** Also affects: nvidia-graphics-drivers-440 (Ubuntu)
   Importance: Undecided
   Status: New

** Tags added: black-screen

** Changed in: nvidia-graphics-drivers-440 (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://bugs.launchpad.net/bugs/1870779

Title:
  [nvidia] Ubuntu 20.04 beta: Blank/black screen after login

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-440/+bug/1870779/+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 1870746] Re: System froze during suspension since Linux kernel v5.3.0-42.

2020-04-06 Thread Daniel van Vugt
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 because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1870746

Title:
  System froze during suspension since Linux kernel v5.3.0-42.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1870746/+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 1870740] Re: Refresh Rate

2020-04-06 Thread Daniel van Vugt
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 us the ID of the newly-created bug.

2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where
ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine.
Do you find any links to recent problems on that page? If so then please
send the links to us.

3. If step 2 also failed then apply the workaround from bug 994921,
reboot, reproduce the crash, and retry step 1.

Please take care to avoid attaching .crash files to bugs as we are
unable to process them as file attachments. It would also be a security
risk for yourself.


** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu)

** Changed in: xorg-server (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://bugs.launchpad.net/bugs/1870740

Title:
  Refresh Rate

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-440/+bug/1870740/+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 1870740] Re: Refresh Rate

2020-04-06 Thread Daniel van Vugt
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) modeset(0): Not using default mode "2048x1536" (bad mode 
clock/interlace/doublescan)
[64.220] (II) modeset(0): Not using default mode "2560x1440" (bad mode 
clock/interlace/doublescan)
[64.220] (II) modeset(0): Not using default mode "2880x1620" (bad mode 
clock/interlace/doublescan)
[64.220] (II) modeset(0): Not using default mode "3200x1800" (bad mode 
clock/interlace/doublescan)
[64.220] (II) modeset(0): Not using default mode "3200x1800" (bad mode 
clock/interlace/doublescan)
[64.220] (II) modeset(0): Not using default mode "1920x1080" (bad mode 
clock/interlace/doublescan)
[64.220] (II) modeset(0): Not using default mode "2048x1152" (bad mode 
clock/interlace/doublescan)
[64.220] (II) modeset(0): Not using default mode "2560x1440" (bad mode 
clock/interlace/doublescan)
[64.220] (II) modeset(0): Not using default mode "2560x1440" (bad mode 
clock/interlace/doublescan)
[64.220] (II) modeset(0): Not using default mode "2560x1600" (bad mode 
clock/interlace/doublescan)
[64.220] (II) modeset(0): Printing probed modes for output HDMI-1

So please also try a different HDMI cable. It must support HDMI 2.0.

** Also affects: nvidia-graphics-drivers-440 (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: nvidia-graphics-drivers-440 (Ubuntu)
   Status: New => Incomplete

-- 
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/+source/nvidia-graphics-drivers-440/+bug/1870740/+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 1870726] Re: [vboxvideo] Ubuntu Login Screen Loop

2020-04-06 Thread Daniel van Vugt
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 us the ID of the newly-created bug.

2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where
ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine.
Do you find any links to recent problems on that page? If so then please
send the links to us.

3. If step 2 also failed then apply the workaround from bug 994921,
reboot, reproduce the crash, and retry step 1.

Please take care to avoid attaching .crash files to bugs as we are
unable to process them as file attachments. It would also be a security
risk for yourself.

** Summary changed:

- Ubuntu Login Screen Loop
+ [vboxvideo] Ubuntu Login Screen Loop

** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu)

** Changed in: xorg-server (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://bugs.launchpad.net/bugs/1870726

Title:
  [vboxvideo] Ubuntu Login Screen Loop

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1870726/+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 1870725] Re: artifacts appearing on gnome shell

2020-04-06 Thread Daniel van Vugt
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 notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1870725

Title:
  artifacts appearing on gnome shell

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1870725/+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 1870637] Re: 20.04beta: Cannot set 3840x2160

2020-04-06 Thread Daniel van Vugt
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 mode "3840x2160" (bad mode 
clock/interlace/doublescan)
[18.036] (II) modeset(0): Not using default mode "2560x1440" (bad mode 
clock/interlace/doublescan)

So make sure the monitor is plugged into the correct HDMI port. And if
it still doesn't work then please try a different HDMI cable. You will
need an HDMI 2.0 cable to achieve those modes.

** Changed in: xorg-server (Ubuntu)
   Status: New => Incomplete

-- 
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.launchpad.net/ubuntu/+source/xorg-server/+bug/1870637/+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 1870637] Re: 20.04beta: Cannot set 3840x2160

2020-04-06 Thread Daniel van Vugt
[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.launchpad.net/bugs/1870637

Title:
  20.04beta: Cannot set 3840x2160

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1870637/+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 1870638] Re: When taskbar is set to bottom icons cannot be re-arranged

2020-04-06 Thread Daniel van Vugt
*** 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 at
the other bug report to see if there is any missing information that you
can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report. Feel free to continue to report any other bugs you may
find.


** Package changed: xorg (Ubuntu) => gnome-shell-extension-ubuntu-dock
(Ubuntu)

** This bug has been marked a duplicate of bug 1867613
   Ubuntu dock does not allow drag and move icons at bottom of screen

-- 
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/1870638

Title:
  When taskbar is set to bottom icons cannot be re-arranged

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1870638/+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 1871029] Re: Ubuntu on ASUS Zenbook UX334F very bad battery performance

2020-04-06 Thread Ubuntu Foundations Team Bug Bot
** 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 about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1871029/+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 1871029] [NEW] Ubuntu on ASUS Zenbook UX334F very bad battery performance

2020-04-06 Thread Launchpad Bug Tracker
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: Ubuntu 19.10
Package: xorg 1:7.7+19ubuntu12
ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13
Uname: Linux 5.3.0-26-generic x86_64
ApportVersion: 2.20.11-0ubuntu8.8
Architecture: amd64
BootLog: Error: [Errno 13] Permesso negato: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Mon Apr  6 08:56:33 2020
DistUpgraded: Fresh install
DistroCodename: eoan
DistroVariant: ubuntu
GraphicsCard:
 Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (rev 02) 
(prog-if 00 [VGA controller])
   Subsystem: ASUSTeK Computer Inc. UHD Graphics 620 (Whiskey Lake) [1043:12bf]
   Subsystem: ASUSTeK Computer Inc. GP108BM [GeForce MX250] [1043:12bf]
InstallationDate: Installed on 2019-12-20 (107 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
MachineType: ASUSTeK COMPUTER INC. ZenBook UX334FL_UX334FL
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=it_IT.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-26-generic 
root=UUID=55b300bd-1469-45d5-84cc-22164774d432 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/18/2019
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: UX334FL.303
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: UX334FL
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX334FL.303:bd12/18/2019:svnASUSTeKCOMPUTERINC.:pnZenBookUX334FL_UX334FL:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX334FL:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.family: ZenBook
dmi.product.name: ZenBook UX334FL_UX334FL
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.99-1ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~19.10.3
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

** Affects: xorg (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug eoan performance third-party-packages ubuntu
-- 
Ubuntu on ASUS Zenbook UX334F very bad battery performance
https://bugs.launchpad.net/bugs/1871029
You received this bug notification because you are a member of Ubuntu-X, which 
is subscribed to xorg in Ubuntu.

___
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 1870779] Re: Ubuntu 20.04 beta: Blank/black screen after login

2020-04-06 Thread Michael
** 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 xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1870779

Title:
  Ubuntu 20.04 beta: Blank/black screen after login

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1870779/+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 1870524] Re: fallback to SW cursor on GPU hotplug

2020-04-06 Thread Daniel van Vugt
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 to SW cursor on GPU hotplug

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1870524/+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 1870988] Re: [nouveau] Xorg crashed with SIGABRT

2020-04-06 Thread Sebastien Bacher
** 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 subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1870988

Title:
  [nouveau] Xorg crashed with SIGABRT in disk_cache_has_key()

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1870988/+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 1866936] Re: kernel package linux-headers-5.4.0-4-amd64 is not supported

2020-04-06 Thread Daniel van Vugt
** 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 package linux-headers-5.4.0-4-amd64 is not supported

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1866936/+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 1871027] [NEW] xserver-xorg-video-amdgpu list firmware-amd-graphics as a suggested package

2020-04-06 Thread Josh Freeno
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 all.

** Affects: xserver-xorg-video-amdgpu (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-amdgpu in Ubuntu.
https://bugs.launchpad.net/bugs/1871027

Title:
   xserver-xorg-video-amdgpu list firmware-amd-graphics as a suggested
  package

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-amdgpu/+bug/1871027/+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