[Desktop-packages] [Bug 1705369] Re: Ubuntu boots to blank screen when using Nvidia (on a desktop with an unused Intel GPU)

2019-06-23 Thread Daniel van Vugt
Upstream is against changing mutter for this, so "Won't Fix" to mutter.
But the fix for gdm3 has landed and that's enough to resolve the bug.

** Changed in: gdm3 (Ubuntu)
   Status: In Progress => Fix Committed

** Changed in: mutter (Ubuntu)
   Status: In Progress => Won't Fix

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

Title:
  Ubuntu boots to blank screen when using Nvidia (on a desktop with an
  unused Intel GPU)

Status in GNOME Shell:
  Fix Released
Status in gdm3 package in Ubuntu:
  Fix Committed
Status in gnome-shell package in Ubuntu:
  Invalid
Status in mutter package in Ubuntu:
  Won't Fix
Status in nvidia-graphics-drivers-375 package in Ubuntu:
  Invalid
Status in nvidia-graphics-drivers-384 package in Ubuntu:
  Invalid

Bug description:
  Ubuntu boots to blank screen when using Nvidia drivers (on a desktop
  with an unused Intel GPU).

  WORKAROUNDS (you only need one):

  * Uncomment #WaylandEnable=false in /etc/gdm3/custom.conf

  * Disable integrated graphics/GPU in your BIOS

  * Add 'nomodeset' to your kernel cmdline in /etc/default/grub and then
    run:  sudo update-initramfs
    and reboot.

  * Add a line to /usr/lib/udev/rules.d/61-gdm.rules:
DRIVER=="nvidia", RUN+="/usr/lib/gdm3/gdm-disable-wayland"

  ORIGINAL DESCRIPTION:

  This bug is very similar to
  https://bugs.launchpad.net/ubuntu-gnome/+bug/1559576
  which is closed. I have been asked to open a new bug report.

  The issue is on Ubuntu 17.10 with gdm3 fully updated as of July 20,
  2017. I upgraded to 17.10 from a freshly installed Ubuntu 17.04.

  - Lightdm works
  - Nouveau driver works
  - Nvidia driver 375.66 (proprietary) does not work
  - Nvidia driver 384.47 (open source) does not work (from 
https://launchpad.net/~graphics-drivers/+archive/ubuntu/ppa)
  - Nvidia drivers work with Ubuntu Gnome 17.04

  I am using Nvidia GTX 1080 and Intel i7-4790K

  lsb_release -rd:
  Description:  Ubuntu Artful Aardvark (development branch)
  Release:  17.10

  apt-cache policy gnome-shell:
  gnome-shell:
    Installed: 3.24.2-0ubuntu7
    Candidate: 3.24.2-0ubuntu7
    Version table:
   *** 3.24.2-0ubuntu7 500
  500 http://sa.archive.ubuntu.com/ubuntu artful/main amd64 Packages
  100 /var/lib/dpkg/status

  uname -s -r -v -p -i -o:
  Linux 4.11.0-11-generic #16-Ubuntu SMP Wed Jul 12 20:40:19 UTC 2017 x86_64 
x86_64 GNU/Linux

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1705369/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1833899] nautilus crashed with SIGSEGV

2019-06-23 Thread Apport retracing service
Stacktrace: No stack.
StacktraceSource:
 
StacktraceTop:
 
ThreadStacktrace:
 


** Tags added: apport-failed-retrace

** Tags removed: need-amd64-retrace

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nautilus in Ubuntu.
https://bugs.launchpad.net/bugs/1833899

Title:
  nautilus crashed with SIGSEGV

Status in nautilus package in Ubuntu:
  New

Bug description:
  just logged in. no apps started.
  corrado@corrado-HP-p4-ee-0618:~$ inxi -Fx
  System:Host: corrado-HP-p4-ee-0618 Kernel: 5.0.0-17-generic x86_64 bits: 
64 compiler: gcc v: 8.3.0 
 Desktop: Gnome 3.32.2 Distro: Ubuntu 19.10 (Eoan Ermine) 
  Machine:   Type: Laptop System: Hewlett-Packard product: HP 250 G3 Notebook 
PC v: 0991100600087 
 serial:  
 Mobo: Hewlett-Packard model: 2211 v: 86.49 serial:  
UEFI: Insyde v: F.36 
 date: 12/18/2014 
  Battery:   ID-1: BAT1 charge: 11.3 Wh condition: 19.9/19.5 Wh (102%) model: 
13-42 OA03031 
 status: Discharging 
  CPU:   Topology: Dual Core model: Intel Core i5-4210U bits: 64 type: MT 
MCP arch: Haswell rev: 1 
 L2 cache: 3072 KiB 
 flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx 
bogomips: 19156 
 Speed: 898 MHz min/max: 800/2700 MHz Core speeds (MHz): 1: 898 2: 
898 3: 898 4: 898 
  Graphics:  Device-1: Intel Haswell-ULT Integrated Graphics vendor: 
Hewlett-Packard driver: i915 v: kernel 
 bus ID: 00:02.0 
 Display: x11 server: X.Org 1.20.4 driver: i915 resolution: 
1366x768~60Hz 
 OpenGL: renderer: Mesa DRI Intel Haswell Mobile v: 4.5 Mesa 19.0.5 
direct render: Yes 
  Audio: Device-1: Intel Haswell-ULT HD Audio vendor: Hewlett-Packard 
driver: snd_hda_intel v: kernel 
 bus ID: 00:03.0 
 Device-2: Intel 8 Series HD Audio vendor: Hewlett-Packard driver: 
snd_hda_intel v: kernel 
 bus ID: 00:1b.0 
 Sound Server: ALSA v: k5.0.0-17-generic 
  Network:   Device-1: Realtek RTL810xE PCI Express Fast Ethernet vendor: 
Hewlett-Packard driver: r8169 
 v: kernel port: 3000 bus ID: 08:00.0 
 IF: enp8s0 state: down mac: 5c:b9:01:06:ba:ce 
 Device-2: Ralink RT3290 Wireless 802.11n 1T/1R PCIe vendor: 
Hewlett-Packard driver: rt2800pci 
 v: 2.3.0 port: 3000 bus ID: 09:00.0 
 IF: wlp9s0f0 state: up mac: ac:d1:b8:82:03:5d 
  Drives:Local Storage: total: 465.76 GiB used: 6.89 GiB (1.5%) 
 ID-1: /dev/sda vendor: Seagate model: ST500LT012-1DG142 size: 
465.76 GiB 
  Partition: ID-1: / size: 31.25 GiB used: 6.88 GiB (22.0%) fs: ext4 dev: 
/dev/sda4 
 ID-2: swap-1 size: 4.00 GiB used: 0 KiB (0.0%) fs: swap dev: 
/dev/sda2 
  Sensors:   System Temperatures: cpu: 30.0 C mobo: N/A 
 Fan Speeds (RPM): N/A 
  Info:  Processes: 207 Uptime: 7m Memory: 3.78 GiB used: 1.01 GiB (26.7%) 
Init: systemd runlevel: 5 
 Compilers: gcc: 8.3.0 Shell: bash v: 5.0.3 inxi: 3.0.34 
  corrado@corrado-HP-p4-ee-0618:~$

  ProblemType: Crash
  DistroRelease: Ubuntu 19.10
  Package: nautilus 1:3.32.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-17.18-generic 5.0.8
  Uname: Linux 5.0.0-17-generic x86_64
  ApportVersion: 2.20.11-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jun 23 20:57:41 2019
  Disassembly: No registers.
  ExecutablePath: /usr/bin/nautilus
  GsettingsChanges:
   
  InstallationDate: Installed on 2019-06-23 (0 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190618)
  ProcCmdline: /usr/bin/nautilus --gapplication-service
  Registers: The program has no registers now.
  SegvAnalysis: Failure: invalid literal for int() with base 16: 'program'
  Signal: 11
  SourcePackage: nautilus
  Stacktrace: No stack.
  StacktraceTop:
   
  ThreadStacktrace:
   
  Title: nautilus crashed with SIGSEGV
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  separator:
   
  usr_lib_nautilus:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1833899/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1833899] [NEW] nautilus crashed with SIGSEGV

2019-06-23 Thread corrado venturini
Public bug reported:

just logged in. no apps started.
corrado@corrado-HP-p4-ee-0618:~$ inxi -Fx
System:Host: corrado-HP-p4-ee-0618 Kernel: 5.0.0-17-generic x86_64 bits: 64 
compiler: gcc v: 8.3.0 
   Desktop: Gnome 3.32.2 Distro: Ubuntu 19.10 (Eoan Ermine) 
Machine:   Type: Laptop System: Hewlett-Packard product: HP 250 G3 Notebook PC 
v: 0991100600087 
   serial:  
   Mobo: Hewlett-Packard model: 2211 v: 86.49 serial:  
UEFI: Insyde v: F.36 
   date: 12/18/2014 
Battery:   ID-1: BAT1 charge: 11.3 Wh condition: 19.9/19.5 Wh (102%) model: 
13-42 OA03031 
   status: Discharging 
CPU:   Topology: Dual Core model: Intel Core i5-4210U bits: 64 type: MT MCP 
arch: Haswell rev: 1 
   L2 cache: 3072 KiB 
   flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx 
bogomips: 19156 
   Speed: 898 MHz min/max: 800/2700 MHz Core speeds (MHz): 1: 898 2: 
898 3: 898 4: 898 
Graphics:  Device-1: Intel Haswell-ULT Integrated Graphics vendor: 
Hewlett-Packard driver: i915 v: kernel 
   bus ID: 00:02.0 
   Display: x11 server: X.Org 1.20.4 driver: i915 resolution: 
1366x768~60Hz 
   OpenGL: renderer: Mesa DRI Intel Haswell Mobile v: 4.5 Mesa 19.0.5 
direct render: Yes 
Audio: Device-1: Intel Haswell-ULT HD Audio vendor: Hewlett-Packard driver: 
snd_hda_intel v: kernel 
   bus ID: 00:03.0 
   Device-2: Intel 8 Series HD Audio vendor: Hewlett-Packard driver: 
snd_hda_intel v: kernel 
   bus ID: 00:1b.0 
   Sound Server: ALSA v: k5.0.0-17-generic 
Network:   Device-1: Realtek RTL810xE PCI Express Fast Ethernet vendor: 
Hewlett-Packard driver: r8169 
   v: kernel port: 3000 bus ID: 08:00.0 
   IF: enp8s0 state: down mac: 5c:b9:01:06:ba:ce 
   Device-2: Ralink RT3290 Wireless 802.11n 1T/1R PCIe vendor: 
Hewlett-Packard driver: rt2800pci 
   v: 2.3.0 port: 3000 bus ID: 09:00.0 
   IF: wlp9s0f0 state: up mac: ac:d1:b8:82:03:5d 
Drives:Local Storage: total: 465.76 GiB used: 6.89 GiB (1.5%) 
   ID-1: /dev/sda vendor: Seagate model: ST500LT012-1DG142 size: 465.76 
GiB 
Partition: ID-1: / size: 31.25 GiB used: 6.88 GiB (22.0%) fs: ext4 dev: 
/dev/sda4 
   ID-2: swap-1 size: 4.00 GiB used: 0 KiB (0.0%) fs: swap dev: 
/dev/sda2 
Sensors:   System Temperatures: cpu: 30.0 C mobo: N/A 
   Fan Speeds (RPM): N/A 
Info:  Processes: 207 Uptime: 7m Memory: 3.78 GiB used: 1.01 GiB (26.7%) 
Init: systemd runlevel: 5 
   Compilers: gcc: 8.3.0 Shell: bash v: 5.0.3 inxi: 3.0.34 
corrado@corrado-HP-p4-ee-0618:~$

ProblemType: Crash
DistroRelease: Ubuntu 19.10
Package: nautilus 1:3.32.1-1ubuntu1
ProcVersionSignature: Ubuntu 5.0.0-17.18-generic 5.0.8
Uname: Linux 5.0.0-17-generic x86_64
ApportVersion: 2.20.11-0ubuntu3
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Sun Jun 23 20:57:41 2019
Disassembly: No registers.
ExecutablePath: /usr/bin/nautilus
GsettingsChanges:
 
InstallationDate: Installed on 2019-06-23 (0 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190618)
ProcCmdline: /usr/bin/nautilus --gapplication-service
Registers: The program has no registers now.
SegvAnalysis: Failure: invalid literal for int() with base 16: 'program'
Signal: 11
SourcePackage: nautilus
Stacktrace: No stack.
StacktraceTop:
 
ThreadStacktrace:
 
Title: nautilus crashed with SIGSEGV
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
separator:
 
usr_lib_nautilus:

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


** Tags: amd64 apport-crash eoan need-amd64-retrace

** Information type changed from Private to Public

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nautilus in Ubuntu.
https://bugs.launchpad.net/bugs/1833899

Title:
  nautilus crashed with SIGSEGV

Status in nautilus package in Ubuntu:
  New

Bug description:
  just logged in. no apps started.
  corrado@corrado-HP-p4-ee-0618:~$ inxi -Fx
  System:Host: corrado-HP-p4-ee-0618 Kernel: 5.0.0-17-generic x86_64 bits: 
64 compiler: gcc v: 8.3.0 
 Desktop: Gnome 3.32.2 Distro: Ubuntu 19.10 (Eoan Ermine) 
  Machine:   Type: Laptop System: Hewlett-Packard product: HP 250 G3 Notebook 
PC v: 0991100600087 
 serial:  
 Mobo: Hewlett-Packard model: 2211 v: 86.49 serial:  
UEFI: Insyde v: F.36 
 date: 12/18/2014 
  Battery:   ID-1: BAT1 charge: 11.3 Wh condition: 19.9/19.5 Wh (102%) model: 
13-42 OA03031 
 status: Discharging 
  CPU:   Topology: Dual Core model: Intel Core i5-4210U bits: 64 type: MT 
MCP arch: Haswell rev: 1 
 L2 cache: 3072 KiB 
 flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx 
bogomips: 19156 
 Speed: 898 MHz min/max: 800/2700 MHz Core speeds (MHz): 1: 898 2

[Desktop-packages] [Bug 1833855] Re: video card

2019-06-23 Thread Daniel van Vugt
There is a slight chance this is a kernel bug, so I am assigning it
there.

I've seen a few reports of people having trouble with analogue VGA
connections not detecting EDIDs, resulting in low resolution.

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

** Changed in: linux (Ubuntu)
   Status: Invalid => New

** Summary changed:

- video card
+ i915: EDID not detected on VGA resulting in low resolution

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

Title:
  i915: EDID not detected on VGA resulting in low resolution

Status in linux package in Ubuntu:
  New

Bug description:
  hi!  some problem.  i have an video intel graphic card Q965 but i dont
  have any hi-resolution like 1080.  i'm in vga mode only.  Can you help
  me?

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.18.0-22.23~18.04.1-generic 4.18.20
  Uname: Linux 4.18.0-22-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jun 23 09:58:42 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 82Q963/Q965 Integrated Graphics Controller [8086:2992] 
(rev 02) (prog-if 00 [VGA controller])
 Subsystem: Dell 82Q963/Q965 Integrated Graphics Controller [1028:01da]
 Subsystem: Dell 82Q963/Q965 Integrated Graphics Controller [1028:01da]
  InstallationDate: Installed on 2019-06-18 (5 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  MachineType: Dell Inc. OptiPlex 745
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-22-generic 
root=UUID=017d360b-c7a7-47e3-8d37-669b93a45647 ro quiet splash 
video=hyperv_fb:1280x720 vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/01/2010
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.6.4
  dmi.board.name: 0GW726
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 16
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.6.4:bd03/01/2010:svnDellInc.:pnOptiPlex745:pvr:rvnDellInc.:rn0GW726:rvr:cvnDellInc.:ct16:cvr:
  dmi.product.name: OptiPlex 745
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.98+git1906111830.5db0f7~oibaf~b
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2~git1906191930.9c19d0~oibaf~b
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.2~git1906191930.9c19d0~oibaf~b
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1833855/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1722096] Re: AisleRiot card theme is not branded

2019-06-23 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: branding-ubuntu (Ubuntu)
   Status: New => Confirmed

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to branding-ubuntu in Ubuntu.
https://bugs.launchpad.net/bugs/1722096

Title:
  AisleRiot card theme  is not branded

Status in branding-ubuntu package in Ubuntu:
  Confirmed

Bug description:
  Description:  Ubuntu 16.04.3 LTS
  Release:  16.04
  
  branding-ubuntu: 0.8
  

  AisleRiot uses .svgz file for card theme. bonded.svg in this package
  is not used.

  Expected
  branding-ubuntu should include a file bonded.svgz, and get bonded.svgz in 
package aisleriot diverted.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/branding-ubuntu/+bug/1722096/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1721661] Re: Aisleriot does not use Ubuntu branding

2019-06-23 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: aisleriot (Ubuntu)
   Status: New => Confirmed

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to aisleriot in Ubuntu.
https://bugs.launchpad.net/bugs/1721661

Title:
  Aisleriot does not use Ubuntu branding

Status in aisleriot package in Ubuntu:
  Confirmed

Bug description:
  Aisleriot uses the default Gnome branding (Gnome foot).
  The Ubuntu branding is in the folder /usr/share/branding/aisleriot/cards but 
isn't utilized.

  bonded.svg
  baize.png

  Also, you can't switch cardbacks

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/aisleriot/+bug/1721661/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1827879] Re: Killer Wireless 1525 firmware crashes on suspend

2019-06-23 Thread Kai-Heng Feng
Does the issue still happen?

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1827879

Title:
  Killer Wireless 1525 firmware crashes on suspend

Status in Ubuntu:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in network-manager package in Ubuntu:
  New

Bug description:
  Problem: 
  Ubuntu running on Alienware 17 R2 system hangs on suspend. The Keyboard LED's 
stay on and FAN keeps running. Strangely this does not happen in Fedora 29 
(Kernel 4.18 & same board firmware)

  System:
  Ubuntu 19.04 
  Kernel 5.0.0-13-generic
  Wireless chipset Killer Wireless 1525 (Atheros QCA6174, hw2.1)
  Wireless info:
 description: Wireless interface
 product: QCA6174 802.11ac Wireless Network Adapter
 vendor: Qualcomm Atheros
 physical id: 0
 bus info: pci@:03:00.0
 logical name: wlp3s0
 version: 20
 serial: 40:b8:9a:ca:2b:99
 width: 64 bits
 clock: 33MHz
 capabilities: pm msi pciexpress bus_master cap_list ethernet physical 
wireless
 configuration: broadcast=yes driver=ath10k_pci 
driverversion=5.0.0-13-generic firmware=SW_RM.1.1.1-00157-QCARMSWPZ-1 
ip=192.168.55.161 latency=0 link=yes multicast=yes wireless=IEEE 802.11
 resources: irq:32 memory:f680-f69f

  
  My attempts:
  1. Tried other kernels:
  5.0.12, 4.20.17, 4.19.7, 4.18.16, 4.18.0, 4.16.0, 4.14.114

  2. Tried several distro's based on ubuntu -> all have the same issue

  3. Checked firmware from Fedora 29 (md5sum was equal) and updated
  firmware (not available, using latest)

  4. Created systemd scripts for disabling & enabling the driver, this causes 
the same crashes in /var/log/syslog
  See: https://forum.manjaro.org/t/solved-qca6174-freez-after-suspend/66232/11

  5. Physically replaced Killer 1525 with Intel 8260 --> problem is
  gone, standby works perfectly

  Of course i want to be able to use the 1525, so please help me solve the 
issue.
  Happy to perform additional debugging if required.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  sander 1527 F pulseaudio
   /dev/snd/controlC0:  sander 1527 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 19.04
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IpRoute:
   default via 192.168.55.1 dev wlp3s0 proto dhcp metric 600 
   169.254.0.0/16 dev wlp3s0 scope link metric 1000 
   192.168.55.0/24 dev wlp3s0 proto kernel scope link src 192.168.55.58 metric 
600
  MachineType: Alienware Alienware 17 R2
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: network-manager 1.16.0-0ubuntu2
  PackageArchitecture: amd64
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-15-generic 
root=UUID=9f06fd28-fdb2-4ada-986f-1e7eb1b87882 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.0.0-15.16-generic 5.0.6
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-15-generic N/A
   linux-backports-modules-5.0.0-15-generic  N/A
   linux-firmware1.178.1
  Tags:  disco
  Uname: Linux 5.0.0-15-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 03/31/2017
  dmi.bios.vendor: Alienware
  dmi.bios.version: A08
  dmi.board.name: Alienware 17 R2
  dmi.board.vendor: Alienware
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Alienware
  dmi.chassis.version: A08
  dmi.modalias: 
dmi:bvnAlienware:bvrA08:bd03/31/2017:svnAlienware:pnAlienware17R2:pvrA08:rvnAlienware:rnAlienware17R2:rvrA00:cvnAlienware:ct8:cvrA08:
  dmi.product.family: Alienware 17 R2
  dmi.product.name: Alienware 17 R2
  dmi.product.sku: Alienware 15
  dmi.product.version: A08
  dmi.sys.vendor: Alienware
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.16.0   connected  started  full  enabled enabled  
enabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/1827879/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1832693] Re: System auto suspend again during resuming

2019-06-23 Thread cktenn
** Attachment added: "workaround.log"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1832693/+attachment/5272634/+files/workaround.log

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-settings-daemon in Ubuntu.
https://bugs.launchpad.net/bugs/1832693

Title:
  System auto suspend again during resuming

Status in gnome-settings-daemon package in Ubuntu:
  Incomplete

Bug description:
  ## Issue
  In certain case, system wake-up from suspend will suspend again automatically.

  The issue comes from a target machine turning auto-suspend on and
  suspends after the idle time-out. Manually suspend, e.g., click
  suspend icon or execute "systemctl suspend" won't reproduce the issue.

  When waking up from this situation, the monitor keeps blank, although
  the monitor has exited low power mode, then suspend again immediately.
  Can successfully waking up the system after that, but once the system
  reaches the idle time again, the issue appears repeatedly. From the
  system log, a sleep request is following the wake request.

  Hardware configuration also counts. It is hard to reproduce the issue
  with the system installed on SSD or with a lower resolution monitor;
  graphics card may also affect. It's likely to be a timing issue.

  ## Environment
  Machine: Dell Precision 7920 Tower.
  Monitor: Philips 288P6L
  DistroRelease: Ubuntu 18.04.2
  Graphics card: Nvidia Quadro P2200
  Nvidia driver version: 418.74
  CPU: Intel(R) Xeon(R) Platinum 8276 CPU @ 2.20GHz

  ## Steps to reproduce:
  Turn on automatic suspend in Settings->Power
  Wait for the system to suspend
  Wake up the system via pressing power button or keyboard.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1832693/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1832693] Re: System auto suspend again during resuming

2019-06-23 Thread cktenn
My workaround prints

gsd-power[3124]: temporary_unidle_done_cb is trying to do inhibited job

** Attachment added: "workaround.log"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1832693/+attachment/5272635/+files/workaround.log

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-settings-daemon in Ubuntu.
https://bugs.launchpad.net/bugs/1832693

Title:
  System auto suspend again during resuming

Status in gnome-settings-daemon package in Ubuntu:
  Incomplete

Bug description:
  ## Issue
  In certain case, system wake-up from suspend will suspend again automatically.

  The issue comes from a target machine turning auto-suspend on and
  suspends after the idle time-out. Manually suspend, e.g., click
  suspend icon or execute "systemctl suspend" won't reproduce the issue.

  When waking up from this situation, the monitor keeps blank, although
  the monitor has exited low power mode, then suspend again immediately.
  Can successfully waking up the system after that, but once the system
  reaches the idle time again, the issue appears repeatedly. From the
  system log, a sleep request is following the wake request.

  Hardware configuration also counts. It is hard to reproduce the issue
  with the system installed on SSD or with a lower resolution monitor;
  graphics card may also affect. It's likely to be a timing issue.

  ## Environment
  Machine: Dell Precision 7920 Tower.
  Monitor: Philips 288P6L
  DistroRelease: Ubuntu 18.04.2
  Graphics card: Nvidia Quadro P2200
  Nvidia driver version: 418.74
  CPU: Intel(R) Xeon(R) Platinum 8276 CPU @ 2.20GHz

  ## Steps to reproduce:
  Turn on automatic suspend in Settings->Power
  Wait for the system to suspend
  Wake up the system via pressing power button or keyboard.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1832693/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1832693] Re: System auto suspend again during resuming

2019-06-23 Thread cktenn
@Sebastien

Thank you for your response. It is "Ubuntu 18.04.2".

I've found the root cause of this problem last week. In plugins/power
/gsd-power-manager.c, handle_wake_up_screen enables
temporary_unidle_done_cb to run after 15 seconds before system enters
suspend. In most cases, temporary_unidle_done_cb will be removed by
idle_became_active_cb right after resuming so it won't cause any
trouble.

In my case, after resuming, somehow temporary_unidle_done_cb is
triggered before idle_became_active_cb meanwhile previous_idle_mode is
still sleep mode, so it calls idle_set_mode to sleep again although has
been inhibited.

I've tried to put a workaround, letting temporary_unidle_done_cb to
check if inhibit_suspend_taken to be true and not to execute
idle_set_mode. It does solve this problem but seems not the right way to
fix it.

I added some wrapper to log the caller, hope it is easy to understand.


** Attachment added: "faillog7.log"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1832693/+attachment/5272633/+files/faillog7.log

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-settings-daemon in Ubuntu.
https://bugs.launchpad.net/bugs/1832693

Title:
  System auto suspend again during resuming

Status in gnome-settings-daemon package in Ubuntu:
  Incomplete

Bug description:
  ## Issue
  In certain case, system wake-up from suspend will suspend again automatically.

  The issue comes from a target machine turning auto-suspend on and
  suspends after the idle time-out. Manually suspend, e.g., click
  suspend icon or execute "systemctl suspend" won't reproduce the issue.

  When waking up from this situation, the monitor keeps blank, although
  the monitor has exited low power mode, then suspend again immediately.
  Can successfully waking up the system after that, but once the system
  reaches the idle time again, the issue appears repeatedly. From the
  system log, a sleep request is following the wake request.

  Hardware configuration also counts. It is hard to reproduce the issue
  with the system installed on SSD or with a lower resolution monitor;
  graphics card may also affect. It's likely to be a timing issue.

  ## Environment
  Machine: Dell Precision 7920 Tower.
  Monitor: Philips 288P6L
  DistroRelease: Ubuntu 18.04.2
  Graphics card: Nvidia Quadro P2200
  Nvidia driver version: 418.74
  CPU: Intel(R) Xeon(R) Platinum 8276 CPU @ 2.20GHz

  ## Steps to reproduce:
  Turn on automatic suspend in Settings->Power
  Wait for the system to suspend
  Wake up the system via pressing power button or keyboard.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1832693/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1833617] Status changed to Confirmed

2019-06-23 Thread Ubuntu Kernel Bot
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 xserver-xorg-video-amdgpu in Ubuntu.
https://bugs.launchpad.net/bugs/1833617

Title:
  [amdgpu] screen freeze after suspend

Status in linux package in Ubuntu:
  Confirmed
Status in xserver-xorg-video-amdgpu package in Ubuntu:
  New

Bug description:
  It's most likely amdgup driver needs an upgrade. Problem occurs since
  kernel upgrade to 5.0

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.0.0-18.19-generic 5.0.12
  Uname: Linux 5.0.0-18-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CompositorRunning: None
  Date: Thu Jun 20 13:46:46 2019
  DistUpgraded: Fresh install
  DistroCodename: disco
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Stoney [Radeon R2/R3/R4/R5 Graphics] 
[1002:98e4] (rev eb) (prog-if 00 [VGA controller])
 Subsystem: Dell Stoney [Radeon R2/R3/R4/R5 Graphics] [1028:087e]
  InstallationDate: Installed on 2019-06-06 (14 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  MachineType: Dell Inc. Inspiron 3180
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-18-generic 
root=UUID=a16bd163-e82f-4ec1-9c5f-c9bd32e225fa ro
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/09/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.3.0
  dmi.board.name: 0918N8
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 1.3.0
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.3.0:bd03/09/2018:svnDellInc.:pnInspiron3180:pvr1.3.0:rvnDellInc.:rn0918N8:rvrA00:cvnDellInc.:ct10:cvr1.3.0:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 3180
  dmi.product.sku: 087E
  dmi.product.version: 1.3.0
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1833617/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1833867] Re: graphics turn sowy then black screen

2019-06-23 Thread Daniel van Vugt
Does the problem happen when you suspend/resume the machine?

If so then I think I know what the problem is. If not then please attach
photos or a video of the problem.

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

** Changed in: ubuntu
   Status: New => Incomplete

** Package changed: ubuntu => nvidia-graphics-drivers-340 (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/1833867

Title:
  graphics turn sowy then black screen

Status in nvidia-graphics-drivers-340 package in Ubuntu:
  Incomplete

Bug description:
  bad graphcis

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-52.56-generic 4.15.18
  Uname: Linux 4.15.0-52-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  340.107  Thu May 24 21:54:01 
PDT 2018
   GCC version:  gcc version 7.4.0 (Ubuntu 7.4.0-1ubuntu1~18.04.1)
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jun 23 13:50:05 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   xpad, 0.4, 4.15.0-52-generic, x86_64: installed
   xpad, 0.4, 4.18.0-21-generic, x86_64: installed
   xpad, 0.4, 4.18.0-22-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation G80 [GeForce 8800 GTX] [10de:0191] (rev a2) (prog-if 00 
[VGA controller])
 Subsystem: NVIDIA Corporation G80 [GeForce 8800 GTX] [10de:039c]
  InstallationDate: Installed on 2018-01-28 (511 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 003: ID 413c:2113 Dell Computer Corp. 
   Bus 002 Device 002: ID 1bcf:053e Sunplus Innovation Technology Inc. 
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: Dell Inc. Dell XPS720
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-52-generic 
root=UUID=f61c2552-e2fd-436d-85a5-9fde323a4908 ro recovery nomodeset nomodeset
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  XorgLogOld:
   
  dmi.bios.date: 08/23/2007
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A03
  dmi.board.name: 0YU822
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 7
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA03:bd08/23/2007:svnDellInc.:pnDellXPS720:pvr:rvnDellInc.:rn0YU822:rvrA00:cvnDellInc.:ct7:cvr:
  dmi.product.name: Dell XPS720
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.95-1~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1833867/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1833855] Re: video card

2019-06-23 Thread Daniel van Vugt
It appears Xorg (or the kernel) can't detect the EDID of your monitor
via the VGA connection:

[55.901] (II) modeset(0): EDID for output VGA-1
[55.901] (II) modeset(0): Printing probed modes for output VGA-1
[55.901] (II) modeset(0): Modeline "1024x768"x60.0   65.00  1024 1048 1184 
1344  768 771 777 806 -hsync -vsync (48.4 kHz e)
[55.901] (II) modeset(0): Modeline "800x600"x60.3   40.00  800 840 968 1056 
 600 601 605 628 +hsync +vsync (37.9 kHz e)
[55.901] (II) modeset(0): Modeline "800x600"x56.2   36.00  800 824 896 1024 
 600 601 603 625 +hsync +vsync (35.2 kHz e)
[55.901] (II) modeset(0): Modeline "848x480"x60.0   33.75  848 864 976 1088 
 480 486 494 517 +hsync +vsync (31.0 kHz e)
[55.901] (II) modeset(0): Modeline "640x480"x59.9   25.18  640 656 752 800  
480 490 492 525 -hsync -vsync (31.5 kHz e)

So only standard modes are provided in order to avoid guessing and
damaging the monitor.

In order to allow the system to detect your monitor properly, please use
the DVI port instead. If you can't do that then try a different VGA
cable. But a monitor connected via your digital port (DVI) would be
best.

P.S. You also seem to be using the 'oibaf' PPA which is not supported by
Ubuntu.

** Changed in: xorg (Ubuntu)
   Status: New => Invalid

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

Title:
  video card

Status in xorg package in Ubuntu:
  Invalid

Bug description:
  hi!  some problem.  i have an video intel graphic card Q965 but i dont
  have any hi-resolution like 1080.  i'm in vga mode only.  Can you help
  me?

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.18.0-22.23~18.04.1-generic 4.18.20
  Uname: Linux 4.18.0-22-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jun 23 09:58:42 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 82Q963/Q965 Integrated Graphics Controller [8086:2992] 
(rev 02) (prog-if 00 [VGA controller])
 Subsystem: Dell 82Q963/Q965 Integrated Graphics Controller [1028:01da]
 Subsystem: Dell 82Q963/Q965 Integrated Graphics Controller [1028:01da]
  InstallationDate: Installed on 2019-06-18 (5 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  MachineType: Dell Inc. OptiPlex 745
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-22-generic 
root=UUID=017d360b-c7a7-47e3-8d37-669b93a45647 ro quiet splash 
video=hyperv_fb:1280x720 vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/01/2010
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.6.4
  dmi.board.name: 0GW726
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 16
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.6.4:bd03/01/2010:svnDellInc.:pnOptiPlex745:pvr:rvnDellInc.:rn0GW726:rvr:cvnDellInc.:ct16:cvr:
  dmi.product.name: OptiPlex 745
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.98+git1906111830.5db0f7~oibaf~b
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2~git1906191930.9c19d0~oibaf~b
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.2~git1906191930.9c19d0~oibaf~b
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1833855/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1833867] [NEW] graphics turn sowy then black screen

2019-06-23 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

bad graphcis

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 4.15.0-52.56-generic 4.15.18
Uname: Linux 4.15.0-52-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia
.proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  340.107  Thu May 24 21:54:01 
PDT 2018
 GCC version:  gcc version 7.4.0 (Ubuntu 7.4.0-1ubuntu1~18.04.1)
ApportVersion: 2.20.9-0ubuntu7.6
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Sun Jun 23 13:50:05 2019
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
DkmsStatus:
 xpad, 0.4, 4.15.0-52-generic, x86_64: installed
 xpad, 0.4, 4.18.0-21-generic, x86_64: installed
 xpad, 0.4, 4.18.0-22-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
 NVIDIA Corporation G80 [GeForce 8800 GTX] [10de:0191] (rev a2) (prog-if 00 
[VGA controller])
   Subsystem: NVIDIA Corporation G80 [GeForce 8800 GTX] [10de:039c]
InstallationDate: Installed on 2018-01-28 (511 days ago)
InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210)
Lsusb:
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 002 Device 003: ID 413c:2113 Dell Computer Corp. 
 Bus 002 Device 002: ID 1bcf:053e Sunplus Innovation Technology Inc. 
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: Dell Inc. Dell XPS720
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-52-generic 
root=UUID=f61c2552-e2fd-436d-85a5-9fde323a4908 ro recovery nomodeset nomodeset
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
XorgLogOld:
 
dmi.bios.date: 08/23/2007
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A03
dmi.board.name: 0YU822
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 7
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvrA03:bd08/23/2007:svnDellInc.:pnDellXPS720:pvr:rvnDellInc.:rn0YU822:rvrA00:cvnDellInc.:ct7:cvr:
dmi.product.name: Dell XPS720
dmi.sys.vendor: Dell Inc.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.95-1~18.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2
version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core N/A
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

** Affects: nvidia-graphics-drivers-340 (Ubuntu)
 Importance: Undecided
 Status: Incomplete


** Tags: amd64 apport-bug bionic ubuntu
-- 
graphics turn sowy then black screen
https://bugs.launchpad.net/bugs/1833867
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu.

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1833832] Re: NVIDIA kernel module fails with KMS on optimus hardware

2019-06-23 Thread Daniel van Vugt
*** This bug is a duplicate of bug 1716857 ***
https://bugs.launchpad.net/bugs/1716857

The errors in the attached journal log show this is the same as what I
recently described in:

https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-
drivers-418/+bug/1716857/comments/36

** This bug has been marked a duplicate of bug 1716857
   nvidia-drm.modeset=1 results in no monitors detected by Xorg

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gdm3 in Ubuntu.
https://bugs.launchpad.net/bugs/1833832

Title:
  NVIDIA kernel module fails with KMS on optimus hardware

Status in gdm3 package in Ubuntu:
  New

Bug description:
  Test case;
  An optimus laptop
  fresh 19.10 install, updated.
  Install nvidia-driver-430
  Enable nvidia-drm.modeset ( done here thru a .conf /etc/modprobe.d
  Reboot

  What happens:
  Boots to login screen, all attempts to log into a ubuntu session loop back to 
log in screen

  Attached log from journalctl

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gdm3 3.32.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-17.18-generic 5.0.8
  Uname: Linux 5.0.0-17-generic x86_64
  ApportVersion: 2.20.11-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jun 22 21:13:04 2019
  InstallationDate: Installed on 2019-06-22 (0 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190606)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gdm3
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.gdm3.custom.conf: [modified]
  mtime.conffile..etc.gdm3.custom.conf: 2019-06-22T20:52:09.277952

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1833832/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 561370] Re: gnome-terminal transparency no longer works reliably (usually opaque, but sometimes shows transparency)

2019-06-23 Thread Daniel van Vugt
** Tags added: disco

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-terminal in Ubuntu.
https://bugs.launchpad.net/bugs/561370

Title:
  gnome-terminal transparency no longer works reliably (usually opaque,
  but sometimes shows transparency)

Status in gnome-terminal package in Ubuntu:
  Confirmed

Bug description:
  gnome-terminal transparency no longer works reliably (usually opaque,
  but sometimes shows transparency)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/561370/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1833823] Re: Text box appeared on the main screen of desktop and no way to get rid of it.

2019-06-23 Thread Daniel van Vugt
** Changed in: xorg (Ubuntu)
   Status: New => Invalid

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

Title:
  Text box appeared on the main screen of desktop and no way to get rid
  of it.

Status in xorg package in Ubuntu:
  Invalid

Bug description:
  I'm not sure what happened here. I just downloaded phpbb to work on my
  own forum and now this text box appeared on my main screen of my
  laptop and I can't make it go away, even after a restart and complete
  shutdown and startup. Not sure if it's a problem with xorg/wayland or
  whatever.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.18.0-23.24~18.04.1-generic 4.18.20
  Uname: Linux 4.18.0-23-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CompositorRunning: None
  Date: Sat Jun 22 11:47:58 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA 
controller])
 Subsystem: ASUSTeK Computer Inc. UHD Graphics 620 [1043:1d30]
  InstallationDate: Installed on 2019-06-19 (3 days ago)
  InstallationMedia: Kubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 003: ID 13d3:5a07 IMC Networks 
   Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. X510UAR
  ProcEnviron:
   LANGUAGE=
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-23-generic 
root=UUID=fee9ef1f-d467-48de-8ddd-824920256181 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/24/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X510UAR.309
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X510UAR
  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.:bvrX510UAR.309:bd07/24/2018:svnASUSTeKCOMPUTERINC.:pnX510UAR:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX510UAR:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: VivoBook
  dmi.product.name: X510UAR
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1.1~18.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.2-1ubuntu1.1~18.04.1
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1833823/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1833829] Re: High memory usage by Xorg with Kubuntu 18.04, plasma-desktop, nvidia 390

2019-06-23 Thread Daniel van Vugt
** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu)

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

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

Title:
  High memory usage by Xorg with Kubuntu 18.04, plasma-desktop, nvidia
  390

Status in nvidia-graphics-drivers-390 package in Ubuntu:
  New
Status in xorg-server package in Ubuntu:
  New

Bug description:
  After some continued use of the system (Kubuntu (18.04)) Xorg
  accumulates a lot of RAM space. From that the space only increments
  and doesn't decrease.

  Hardware Specs :

  1. Intel core-i5 6300 HQ
  2. Nvidia GTX 960M

  Software Specs :

  1. Kubuntu 18.04
  2. KDE Plasma shell version 5.12.7

  Something interesting to note is that I have not experienced the same
  behavior from Xorg when I switch the GPU to Intel's Integrated
  graphics. It is entirely possible that I might not have been able to
  trigger those situation with Intel, because after seeing logs I
  couldn't make out why this was happening.

  Also for the timeline I have used the system for over an year without
  any such issue arising. It was the second week of June 2019 to present
  day I have seen this problem.

  Xorg log : http://paste.ubuntu.com/p/nc3pMF4xsb/

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.18.0-22.23~18.04.1-generic 4.18.20
  Uname: Linux 4.18.0-22-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..02.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:02:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  390.116  Sun Jan 27 07:21:36 
PST 2019
   GCC version:  gcc version 7.4.0 (Ubuntu 7.4.0-1ubuntu1~18.04.1)
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: KDE
  Date: Sun Jun 23 05:06:48 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus: nvidia, 390.116, 4.18.0-22-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation HD Graphics 530 [8086:191b] (rev 06) (prog-if 00 [VGA 
controller])
 Subsystem: Dell HD Graphics 530 [1028:0706]
 Subsystem: Dell GM107M [GeForce GTX 960M] [1028:0706]
  InstallationDate: Installed on 2019-06-21 (1 days ago)
  InstallationMedia: Kubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 003: ID 1bcf:28b0 Sunplus Innovation Technology Inc. 
   Bus 001 Device 002: ID 413c:301a Dell Computer Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 7559
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-22-generic 
root=UUID=f046965f-7377-42b2-86ba-febdbcabfc9b ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/13/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.7
  dmi.board.name: 0H87XC
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.7:bd12/13/2017:svnDellInc.:pnInspiron7559:pvr1.2.7:rvnDellInc.:rn0H87XC:rvrA00:cvnDellInc.:ct10:cvrNotSpecified:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 7559
  dmi.product.sku: 0706
  dmi.product.version: 1.2.7
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.95-1~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1833829/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1833749] Re: unfocused terminal window blinking because of transparency unreasonably changing

2019-06-23 Thread Daniel van Vugt
*** This bug is a duplicate of bug 561370 ***
https://bugs.launchpad.net/bugs/561370

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 561370, 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.


** This bug has been marked a duplicate of bug 561370
   gnome-terminal transparency no longer works reliably (usually opaque, but 
sometimes shows transparency)

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

Title:
  unfocused terminal window blinking because of transparency
  unreasonably changing

Status in xorg package in Ubuntu:
  New

Bug description:
  unfocused terminal window blinking because of transparency
  unreasonably changing without any action on keyboard nor mouse

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.0.0-17.18-generic 5.0.8
  Uname: Linux 5.0.0-17-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  418.56  Fri Mar 15 12:59:26 
CDT 2019
   GCC version:  gcc version 8.3.0 (Ubuntu 8.3.0-6ubuntu1)
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jun 21 20:01:45 2019
  DistUpgraded: 2019-04-19 17:34:11,213 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
“./xorg_fix_proprietary.py” (No such file or directory) (8))
  DistroCodename: disco
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 418.56, 5.0.0-16-generic, x86_64: installed
   nvidia, 418.56, 5.0.0-17-generic, x86_64: installed
   virtualbox, 6.0.6, 5.0.0-16-generic, x86_64: installed
   virtualbox, 6.0.6, 5.0.0-17-generic, x86_64: installed
  ExtraDebuggingInterest: No
  GraphicsCard:
   NVIDIA Corporation GM107GLM [Quadro M2000M] [10de:13b0] (rev a2) (prog-if 00 
[VGA controller])
 Subsystem: Lenovo GM107GLM [Quadro M2000M] [17aa:2230]
  InstallationDate: Installed on 2018-04-27 (420 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: LENOVO 20EN0008XS
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-17-generic 
root=UUID=9ba5bcf6-c098-48cd-b443-cbb9ab3b0f03 ro quiet splash acpi_sleep=nonvs 
vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to disco on 2019-04-19 (63 days ago)
  dmi.bios.date: 02/21/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1EET83W (1.56 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20EN0008XS
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1EET83W(1.56):bd02/21/2019:svnLENOVO:pn20EN0008XS:pvrThinkPadP50:rvnLENOVO:rn20EN0008XS:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad P50
  dmi.product.name: 20EN0008XS
  dmi.product.sku: LENOVO_MT_20EN_BU_Think_FM_ThinkPad P50
  dmi.product.version: ThinkPad P50
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.2-1ubuntu1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20180925-2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1833749/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1833508] Re: the system woke up and has not proper desktop image

2019-06-23 Thread Daniel van Vugt
If you are using Nvidia then this is bug 1809407.

Also...

Thank you for taking the time to report this bug and helping to make
Ubuntu better. Please execute the following command only once, as it
will automatically gather debugging information, in a terminal:

apport-collect 1833508

When reporting bugs in the future please use apport by using 'ubuntu-
bug' and the name of the package affected. You can learn more about this
functionality at https://wiki.ubuntu.com/ReportingBugs.

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

Title:
  the system woke up and has not proper desktop image

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  i have ubuntu 19.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1833508/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1833617] Re: [amdgpu] screen freeze after suspend

2019-06-23 Thread Daniel van Vugt
Thanks. That kernel log seems to show the machine never wakes up!

Jun 21 08:44:15 meiradmin-Inspiron-3180 systemd[1]: Reached target Sleep.
Jun 21 08:44:15 meiradmin-Inspiron-3180 systemd[1]: Starting Suspend...
Jun 21 08:44:15 meiradmin-Inspiron-3180 systemd-sleep[2384]: Suspending 
system...
Jun 21 08:44:15 meiradmin-Inspiron-3180 kernel: PM: suspend entry (deep)

So I will assign this to the kernel too.

** Changed in: xserver-xorg-video-amdgpu (Ubuntu)
   Status: Incomplete => New

** Also affects: linux (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  [amdgpu] screen freeze after suspend

Status in linux package in Ubuntu:
  New
Status in xserver-xorg-video-amdgpu package in Ubuntu:
  New

Bug description:
  It's most likely amdgup driver needs an upgrade. Problem occurs since
  kernel upgrade to 5.0

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.0.0-18.19-generic 5.0.12
  Uname: Linux 5.0.0-18-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CompositorRunning: None
  Date: Thu Jun 20 13:46:46 2019
  DistUpgraded: Fresh install
  DistroCodename: disco
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Stoney [Radeon R2/R3/R4/R5 Graphics] 
[1002:98e4] (rev eb) (prog-if 00 [VGA controller])
 Subsystem: Dell Stoney [Radeon R2/R3/R4/R5 Graphics] [1028:087e]
  InstallationDate: Installed on 2019-06-06 (14 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  MachineType: Dell Inc. Inspiron 3180
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-18-generic 
root=UUID=a16bd163-e82f-4ec1-9c5f-c9bd32e225fa ro
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/09/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.3.0
  dmi.board.name: 0918N8
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 1.3.0
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.3.0:bd03/09/2018:svnDellInc.:pnInspiron3180:pvr1.3.0:rvnDellInc.:rn0918N8:rvrA00:cvnDellInc.:ct10:cvr1.3.0:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 3180
  dmi.product.sku: 087E
  dmi.product.version: 1.3.0
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1833617/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1832869] Re: gnome-shell crashed with SIGSEGV in g_hash_table_iter_next → meta_display_list_windows → meta_workspace_list_windows → ffi_call_SYSV → ffi_call()

2019-06-23 Thread Daniel van Vugt
Yes that theming.js around like 479 (on bionic) looks like a candidate
for calling the offending `meta_workspace_list_windows`:

_dockIsNear: function() {
if (this._dockActor.has_style_pseudo_class('overview'))
return false;
/* Get all the windows in the active workspace that are in the primary 
monitor and visible */
let activeWorkspace = global.screen.get_active_workspace();
let dash = this._dash;
let windows = 
activeWorkspace.list_windows().filter(function(metaWindow) {
return metaWindow.get_monitor() === dash._monitorIndex &&
   metaWindow.showing_on_its_workspace() &&
   metaWindow.get_window_type() != Meta.WindowType.DESKTOP;
});

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

Title:
  gnome-shell crashed with SIGSEGV in g_hash_table_iter_next →
  meta_display_list_windows → meta_workspace_list_windows →
  ffi_call_SYSV → ffi_call()

Status in gnome-shell package in Ubuntu:
  Confirmed
Status in gnome-shell-extension-dashtodock package in Ubuntu:
  Triaged

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
gnome-shell.  This problem was most recently seen with package version 
3.28.4-0ubuntu18.04.1, the problem page at 
https://errors.ubuntu.com/problem/d3f9725b7fae2763643521acfc58c734f829dd64 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

  https://errors.ubuntu.com/problem/ac8df0b1e2d67e423c634fde1a3acecd3c381d58
  https://errors.ubuntu.com/problem/d3f9725b7fae2763643521acfc58c734f829dd64
  https://errors.ubuntu.com/problem/1e69eadeb69f4e2b8aa933205d2be3a8db4af36c
  https://errors.ubuntu.com/problem/6f7810166a3ae02cc8025514d6ffbbde10063e76
  https://errors.ubuntu.com/problem/1bfbc00c70cfe6f4f2b66b4efc86f5c089c28680

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1832869/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1832792] Re: App-switcher icons too small with hidpi (3000x2000) monitor

2019-06-23 Thread Daniel van Vugt
*** This bug is a duplicate of bug 1831161 ***
https://bugs.launchpad.net/bugs/1831161

** This bug has been marked a duplicate of bug 1831161
   App-switcher icons too small with hidpi monitor and 1.25 scaling

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

Title:
  App-switcher icons too small with hidpi (3000x2000) monitor

Status in GNOME Shell:
  Fix Released
Status in gnome-shell package in Ubuntu:
  Triaged

Bug description:
  I've reported this upstream (https://gitlab.gnome.org/GNOME/gnome-
  shell/issues/1370), but given that this is an important part of the
  Ubuntu desktop and that you're providing some patches for improving
  the X11 experience with hidpi monitors, I'm notifying about the issue
  here too.

  It could be related to my previous similar report for fractional
  scaling resolutions: https://bugs.launchpad.net/ubuntu/+source/gnome-
  shell/+bug/1831161. But I'm not sure. Besides, fractional scaling is
  an experimental feature while 2x is not.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1832792/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1832436] Re: login page first appears sideways for Lenovo miix 510 ubuntu 18.04 and 18.10

2019-06-23 Thread Daniel van Vugt
** Package changed: gdm3 (Ubuntu) => linux (Ubuntu)

** No longer affects: ubuntu

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gdm3 in Ubuntu.
https://bugs.launchpad.net/bugs/1832436

Title:
  login page first appears sideways  for Lenovo miix 510 ubuntu 18.04
  and 18.10

Status in linux package in Ubuntu:
  New

Bug description:
  I have experienced this for ubuntu 18.04 and 18.10 on a Lenovo Miix
  510 laptop. This problem is fixed on ubuntu 19.04

  The login page appears sideways (the mouse orientation is sideways
  also). After logging in the screen is corrected. I believe the issue
  lies with the detection of the accelerometer or perhaps the driver of
  the accelerometer.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1832436/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1822515] Re: Touchscreen input doesn't rotate with the screen

2019-06-23 Thread Daniel van Vugt
It's true that commit f9d6627fe03f68a132501a488f73e08080018115 is
released in mutter version 3.32.2 already. Which is also fix released in
eoan already.

** Changed in: mutter (Ubuntu)
   Status: Fix Committed => Fix Released

** Also affects: mutter via
   https://gitlab.gnome.org/GNOME/mutter/issues/581
   Importance: Unknown
   Status: Unknown

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

Title:
  Touchscreen input doesn't rotate with the screen

Status in Mutter:
  Unknown
Status in mutter package in Ubuntu:
  Fix Released
Status in xorg-server package in Ubuntu:
  Invalid

Bug description:
  When a touch screen is rotated, touch input is not mapped correctly.

  I'm testing 19.04 on an Acer-One S1003 where the default orientation
  is portrait.

  Ubuntu 19.04 support automatic screen rotation out of the box. But,
  when the tablet is in landscape, the touchscreen doesn't behave
  correctly. Moving a finger horizontally cause a vertical movement and
  vice versa.

  The same happens in both X11 and Wayland.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.04
  Package: xorg-server
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Tags:  disco
  Uname: Linux 5.0.0-13-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/1822515/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1825785] Re: lightdm: screen does not wake up on mouse/keyboard events

2019-06-23 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: xfce (Ubuntu)
   Status: New => Confirmed

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1825785

Title:
  lightdm: screen does not wake up on mouse/keyboard events

Status in lightdm package in Ubuntu:
  Confirmed
Status in xfce package in Ubuntu:
  Confirmed

Bug description:
  Description: When session is locked either using dm-tool or light-
  locker, lightdm greeter is functional (you can type your password and
  press Enter to unlock the session) but screen is not turned on, and
  remains turned off even when you move the mouse or press any key.

  Although, it doesn't occur when you close your session instead locking
  it.

  Additional info:
  * xorg: 1:7.7+19ubuntu12
  * lightdm 1.28.0-0ubuntu1
  * xfce4-session: 4.12.1-6ubuntu1

  From lsb_release:
  Description:  Ubuntu 19.04
  Release:  19.04

  * Reproducible on other distributions as well. See here: 
https://bugs.archlinux.org/task/59750
  * Reproducible on both Intel UHD Graphics and AMDGPU Graphics.

  Steps to reproduce:
  * Lock the running session using lightdm
  * Screen is turned off, but it won't turn back on when you move the mouse or 
use the keyboard
  * You can type the password and press Enter to unlock the session. It the 
password is correct, the screen will finally turn on and you will be at your 
desktop.

  Note: switching out and then switching back to tty7 restores
  visibility of the lock screen.

  On Arch Linux, downgrading to xorg-server{,-common} 1.20.0-9 makes the
  screen behave as expected.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Permissão negada: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: XFCE
  Date: Mon Apr 22 02:06:42 2019
  DistUpgraded: Fresh install
  DistroCodename: disco
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx 
Integrated Graphics Controller [8086:22b1] (rev 21) (prog-if 00 [VGA 
controller])
     Subsystem: Dell Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx 
Integrated Graphics Controller [1028:0725]
  InstallationDate: Installed on 2019-04-22 (0 days ago)
  InstallationMedia: Xubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 1bcf:28c0 Sunplus Innovation Technology Inc.
   Bus 001 Device 002: ID 8087:07dc Intel Corp.
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 11-3162
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-13-generic 
root=/dev/mapper/xubuntu--vg-root ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/31/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.4.0
  dmi.board.name: 0NM68T
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.4.0:bd01/31/2018:svnDellInc.:pnInspiron11-3162:pvr2.4.0:rvnDellInc.:rn0NM68T:rvrA00:cvnDellInc.:ct8:cvrNotSpecified:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: Inspiron 11-3162
  dmi.product.sku: 0725
  dmi.product.version: 2.4.0
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20180925-2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1825785/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1825785] Re: lightdm: screen does not wake up on mouse/keyboard events

2019-06-23 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: lightdm (Ubuntu)
   Status: New => Confirmed

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1825785

Title:
  lightdm: screen does not wake up on mouse/keyboard events

Status in lightdm package in Ubuntu:
  Confirmed
Status in xfce package in Ubuntu:
  Confirmed

Bug description:
  Description: When session is locked either using dm-tool or light-
  locker, lightdm greeter is functional (you can type your password and
  press Enter to unlock the session) but screen is not turned on, and
  remains turned off even when you move the mouse or press any key.

  Although, it doesn't occur when you close your session instead locking
  it.

  Additional info:
  * xorg: 1:7.7+19ubuntu12
  * lightdm 1.28.0-0ubuntu1
  * xfce4-session: 4.12.1-6ubuntu1

  From lsb_release:
  Description:  Ubuntu 19.04
  Release:  19.04

  * Reproducible on other distributions as well. See here: 
https://bugs.archlinux.org/task/59750
  * Reproducible on both Intel UHD Graphics and AMDGPU Graphics.

  Steps to reproduce:
  * Lock the running session using lightdm
  * Screen is turned off, but it won't turn back on when you move the mouse or 
use the keyboard
  * You can type the password and press Enter to unlock the session. It the 
password is correct, the screen will finally turn on and you will be at your 
desktop.

  Note: switching out and then switching back to tty7 restores
  visibility of the lock screen.

  On Arch Linux, downgrading to xorg-server{,-common} 1.20.0-9 makes the
  screen behave as expected.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Permissão negada: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: XFCE
  Date: Mon Apr 22 02:06:42 2019
  DistUpgraded: Fresh install
  DistroCodename: disco
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx 
Integrated Graphics Controller [8086:22b1] (rev 21) (prog-if 00 [VGA 
controller])
     Subsystem: Dell Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx 
Integrated Graphics Controller [1028:0725]
  InstallationDate: Installed on 2019-04-22 (0 days ago)
  InstallationMedia: Xubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 1bcf:28c0 Sunplus Innovation Technology Inc.
   Bus 001 Device 002: ID 8087:07dc Intel Corp.
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 11-3162
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-13-generic 
root=/dev/mapper/xubuntu--vg-root ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/31/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.4.0
  dmi.board.name: 0NM68T
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.4.0:bd01/31/2018:svnDellInc.:pnInspiron11-3162:pvr2.4.0:rvnDellInc.:rn0NM68T:rvrA00:cvnDellInc.:ct8:cvrNotSpecified:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: Inspiron 11-3162
  dmi.product.sku: 0725
  dmi.product.version: 2.4.0
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20180925-2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1825785/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 25830] Re: Option to display file in browser, treat as text/plain

2019-06-23 Thread Bug Watch Updater
** Changed in: firefox
   Status: In Progress => Confirmed

** Changed in: firefox
   Importance: Wishlist => Medium

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
https://bugs.launchpad.net/bugs/25830

Title:
  Option to display file in browser, treat as text/plain

Status in Mozilla Firefox:
  Confirmed
Status in firefox package in Ubuntu:
  Triaged

Bug description:
  A suggestion:

  When you click certain files, like .py or .pl files, for example, Firefox 
brings
  up a dialog that offers you the ability to:
  1. Open with a certain application
  2. Save to disk
  What would be nice is a third option:
  3. Treat as text/plain

  The wording could be altered... "Display as text in browser" or
  something.

  Sometimes you just want to quickly visit a file on the web and look for
  something in it, and the fact that you *could* open it in a more customized
  application is true but not really easier for you at that moment. If you just
  want to look a Python script for a version number at the top it is not 
necessary
  to open it in your IDE or save it to disk; you just want to open it in the
  normal viewing window as plain text and quickly find what you need to look at.

To manage notifications about this bug go to:
https://bugs.launchpad.net/firefox/+bug/25830/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 25830]

2019-06-23 Thread Jonathan Watt
Mass bug change to replace various 'parity' whiteboard flags with the
new canonical keywords. (See bug 1443764 comment 13.)

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
https://bugs.launchpad.net/bugs/25830

Title:
  Option to display file in browser, treat as text/plain

Status in Mozilla Firefox:
  Confirmed
Status in firefox package in Ubuntu:
  Triaged

Bug description:
  A suggestion:

  When you click certain files, like .py or .pl files, for example, Firefox 
brings
  up a dialog that offers you the ability to:
  1. Open with a certain application
  2. Save to disk
  What would be nice is a third option:
  3. Treat as text/plain

  The wording could be altered... "Display as text in browser" or
  something.

  Sometimes you just want to quickly visit a file on the web and look for
  something in it, and the fact that you *could* open it in a more customized
  application is true but not really easier for you at that moment. If you just
  want to look a Python script for a version number at the top it is not 
necessary
  to open it in your IDE or save it to disk; you just want to open it in the
  normal viewing window as plain text and quickly find what you need to look at.

To manage notifications about this bug go to:
https://bugs.launchpad.net/firefox/+bug/25830/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 25830]

2019-06-23 Thread Michael Lippert
Addressing this issue would help a lot of power users. I think all
that's needed is the capability to set somewhere (even about:config)
that all unknown text/* types should be handled as internally as
text/plain.

Currently I have to use Chrome w/ an extension to render a markdown file
from my local filesystem. It is loaded w/ the appropriate mime type:
text/markdown which according to this stackoverflow
(https://stackoverflow.com/questions/10701983/what-is-the-mime-type-for-
markdown) was registered as RFC7763 in March of 2016.

There is at least one firefox extension which will render a markdown
file. but it never gets that far, firefox only gives the options to
download or to specify an external application for the file.

There are other text/* types that it would be really nice if they were
just viewable in the browser rendered as text/plain, such as those for
source files (text/x-c, text/x-java-source, ...). On my system the mime
type is also associated w/ the list of applications I select from in the
file manager to open those files, so I want to be able to distinguish
them from one another (I want to open markdown files with different
applications than js source files or script files for example). I
mention this because one workaround suggested was just to tag markdown
files as text/plain, but I'd rather continue to use Chrome than lose the
ability to distinguish the files in the file manager.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
https://bugs.launchpad.net/bugs/25830

Title:
  Option to display file in browser, treat as text/plain

Status in Mozilla Firefox:
  Confirmed
Status in firefox package in Ubuntu:
  Triaged

Bug description:
  A suggestion:

  When you click certain files, like .py or .pl files, for example, Firefox 
brings
  up a dialog that offers you the ability to:
  1. Open with a certain application
  2. Save to disk
  What would be nice is a third option:
  3. Treat as text/plain

  The wording could be altered... "Display as text in browser" or
  something.

  Sometimes you just want to quickly visit a file on the web and look for
  something in it, and the fact that you *could* open it in a more customized
  application is true but not really easier for you at that moment. If you just
  want to look a Python script for a version number at the top it is not 
necessary
  to open it in your IDE or save it to disk; you just want to open it in the
  normal viewing window as plain text and quickly find what you need to look at.

To manage notifications about this bug go to:
https://bugs.launchpad.net/firefox/+bug/25830/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1833793] Re: Updating to 19.04 audio keeps clicking when nothing is playing audio

2019-06-23 Thread Avamander
This is seriously infuriating, why do I have to keep something playing
at 1% volume just for stuff to stay quiet.

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

Title:
  Updating to 19.04 audio keeps clicking when nothing is playing audio

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  My Ubuntu version: Ubuntu 19.04
  My sound card: Intel Corporation 82801H (ICH8 Family) HD Audio Controller 
(rev 02)

  What I expect to happen:
  Sound is absolutely quiet when no audio is playing

  What happens now:
  Audio output starts clicking every second incredibly annoyingly and loud.

  What previously happened on Ubuntu 18.10:
  I heard the click twice during boot and then it worked properly (without 
clicking during the time it should have been silent)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1833793/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1036236] Re: hpcups and hpijs driver use different rasterization

2019-06-23 Thread J T
# Hello J T,

Hi Rüdiger,

# I just resigned and kept using the HPIJS driver, which produces much better 
# (in terms of visually accurate) output.

Exactly the same situation here.

# However, Till Kamppeter says that Ubuntu is actively phasing out the HPIJS 
# driver. This means that the HPCUPS driver needs to be improved/fixed.

I have the same opinion too. It is precisely *because* I read that hpijs 
was being "deprecated" that made me write in and post a comment to your bug 
report. (The hpijs driver produces good prints with my HP1100 - the hpcups 
driver, on the other hand, produces images that are completely unacceptable).

I have spent an hour reading random HPLIP bug reports and their "resolutions" 
and as a result, I unfortunately do not hold out much hope that this bug will 
ever be resolved. While I would love to see the hpcups driver "fixed", I'll 
continue to use the hpijs driver in the meantime, and if nothing changes 
before the hpijs driver is "removed", I'll have to go and buy a non-HP 
printer.

Fingers crossed...

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to hplip in Ubuntu.
https://bugs.launchpad.net/bugs/1036236

Title:
  hpcups and hpijs driver use different rasterization

Status in HPLIP:
  Confirmed
Status in hplip package in Ubuntu:
  Won't Fix

Bug description:
  HPLIP provides two drivers for the Laserjet 1515n: hpcups and hpijs:
  - hp-color_laserjet_cp1515n-hpijs-pcl3.ppd
  - hp-color_laserjet_cp1515n-pcl3.ppd

  The new hpcups shall replace the old hpijs, however, it produces very
  different rasterization results, resulting in a radically different
  visual impression. Differences are especially prominent for greyscale
  prints.

  Hpcups produces "amplitude modulation" halftones (dots of different
  sizes at fixed locations). When resolution is set to "Normal", the
  size of these dots is so large that contours cannot be reproduced with
  reasonable detail. Heavy aliasing  can be easily seen in the circle
  contours on the Ubuntu Printer test page. Printing photographs in
  greyscale mode yields badly rasterized images like those known from
  low-quality newspaper prints (dot pattern is so prominent it dominates
  image contours). Artifacts are reduced, but still visible at
  resolution "Best".

  In contrast, hpijs produces "frequency modulation" halftones with
  stochastic dithering (small-sized dots placed at varying densities).
  At resolution "Normal", it produces evenly colored areas with
  reasonably sharp edges. Circle contours on the Ubuntu Printer test
  page appear continuous. Photographs are reproduced at a a much higher
  fidelity as with the hpcups driver.

  Questions:
  1. Why do the two drivers use different rasterization?
  2. Why is the result of rasterization so bad in the hpcups driver, set at 
resolution "Normal, Greyscale"?

  Note:
  Both drivers produce acceptable color prints with much fewer artifacts 
visible, even at resolution "Normal".

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: hplip 3.12.2-1ubuntu3.1
  ProcVersionSignature: Ubuntu 3.2.0-29.46-generic 3.2.24
  Uname: Linux 3.2.0-29-generic i686
  ApportVersion: 2.0.1-0ubuntu12
  Architecture: i386
  CurrentDmesg: [   63.368304] init: plymouth-stop pre-start process (1700) 
terminated with status 1
  Date: Mon Aug 13 16:38:16 2012
  Lpstat: device for Farblaser: hp:/net/HP_Color_LaserJet_CP1515n?zc=NPIE56824
  MachineType: exone D156200
  Papersize: letter
  PpdFiles: Farblaser: HP Color LaserJet cp1515n pcl3, hpcups 3.12.2
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-29-generic 
root=/dev/mapper/lvmvg-Root ro quiet splash vt.handoff=7
  SourcePackage: hplip
  UpgradeStatus: Upgraded to precise on 2012-04-26 (108 days ago)
  dmi.bios.date: 04/23/2004
  dmi.bios.vendor: FUJITSU SIEMENS // Phoenix Technologies Ltd.
  dmi.bios.version: 4.06  Rev. 1.09.1562
  dmi.board.name: D1562
  dmi.board.vendor: FUJITSU SIEMENS
  dmi.board.version: S26361-D1562
  dmi.chassis.type: 6
  dmi.chassis.vendor: exone
  dmi.modalias: 
dmi:bvnFUJITSUSIEMENS//PhoenixTechnologiesLtd.:bvr4.06Rev.1.09.1562:bd04/23/2004:svnexone:pnD156200:pvr:rvnFUJITSUSIEMENS:rnD1562:rvrS26361-D1562:cvnexone:ct6:cvr:
  dmi.product.name: D156200
  dmi.sys.vendor: exone

To manage notifications about this bug go to:
https://bugs.launchpad.net/hplip/+bug/1036236/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1802039] Re: Firefox without titlebar has visual glitches when maximizing/unmaximizing

2019-06-23 Thread Arshpreet
Did this bug get fixed?

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
https://bugs.launchpad.net/bugs/1802039

Title:
  Firefox without titlebar has visual glitches when
  maximizing/unmaximizing

Status in Mozilla Firefox:
  New
Status in firefox package in Ubuntu:
  Confirmed

Bug description:
  There is a relatively new feature in Firefox that allows you to hide
  the title bar (I'm running Firefox 63.0), which is very helpful when
  you have a low resolution screen.  However, when changing the
  maximization state, some visual gitches occur.  I didn't notice this
  glitching when running Kubuntu or Ubuntu Budgie on two separate
  systems.

  To try this, go to your Firefox Menu, click Customize, and uncheck
  "Title Bar" at the bottom left.  Then unmaximize the window and then
  remaximize it.

  What it's supposed to look like: https://pasteboard.co/HM0h8oB.png
  Unmaximized (note the large transparent section): 
https://pasteboard.co/HM0hpud.png
  Remaximized (note the duplicate set of close buttons): 
https://pasteboard.co/HM0hCf5.png

  Also another interesting bug I noticed...if you try to use Firefox in
  the no titlebar state with the global menu enabled (e.g. Contemporary,
  Cupertino, or Mutiny panel layouts), the window buttons are not placed
  correctly, being on the window border.

  Systems tried on:

  Laptop, Dell Latitude E5430 - Intel Core i3-3120M dual core with 
hyperthreading, 12 GB DDR3 Memory, Intel 4000 Graphics, Built-in LCD at 
1366x768 (screenshots from this system)
  Desktop, Lenovo ThinkCentre M79 - AMD A4-6300B 3.7 GHz dual core, 8 GB DDR3 
Memory, AMD 8370D Graphics, HP 2009f Monitor at 1600x900

To manage notifications about this bug go to:
https://bugs.launchpad.net/firefox/+bug/1802039/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1833479] Re: libjack-jackd2-0 double close on a failure to connect to jackd which causes crashes in multithreaded programs

2019-06-23 Thread Mathew Hodson
** Changed in: jackd2 (Ubuntu)
   Importance: Undecided => High

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to jackd2 in Ubuntu.
https://bugs.launchpad.net/bugs/1833479

Title:
  libjack-jackd2-0 double close on a failure to connect to jackd which
  causes crashes in multithreaded programs

Status in jackd2 package in Ubuntu:
  New
Status in jackd2 package in Debian:
  New

Bug description:
  After upgrading to Ubuntu 19.04, I started experiencing sporadic
  crashes in kodi when turning my AV receiver on. Ubuntu 19.04 upgraded
  alsa-plugins to 1.1.8. For alsa-plugins >= 1.1.7, the ALSA jack plugin
  is enabled by default in /etc/alsa/conf.d/50-jack.conf.

  The crashes are caused by a race condition when kodi's audio engine
  thread is enumerating the ALSA sound devices, and the udev thread is
  enumerating the udev devices triggered by the sound device add from
  turning the AVR on.

  When enumerating the ALSA jack plugin device, it tries to connect to
  connect to jackd. Since I don't have jackd installed, it fails to
  connect. libjack closes the socket on error, and then closes it again
  in it's cleanup code. Since it's closing the same file descriptor
  twice, it interacts with other threads that have potentially opened
  file descriptors, and causes the crash.

  This same bug could potentially affect other multi-threaded programs
  that enumerate ALSA devices.

  Fix committed upstream:
  
https://github.com/jackaudio/jack2/commit/dad4b5702782eef3bd66e3c3f4fefaaae3571208

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/jackd2/+bug/1833479/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1831144] Re: GNOME control center UI does not update dconf setting for magnifier mouse tracking m ode

2019-06-23 Thread Mathew Hodson
** Bug watch removed: gitlab.gnome.org/GNOME/gnome-shell/issues #865
   https://gitlab.gnome.org/GNOME/gnome-shell/issues/865

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/1831144

Title:
  GNOME control center UI does not update dconf setting for magnifier
  mouse tracking m ode

Status in gnome-control-center:
  Fix Released
Status in gnome-control-center package in Ubuntu:
  Fix Committed
Status in gnome-control-center source package in Disco:
  In Progress

Bug description:
  [Impact]

  If you attempt to change the mouse cursor tracking mode in the gnome
  control centre UI for the gnome magnifier the radio buttons have no
  effect. If yous use dconf-editor to manual change the option at:
  org.gnome.desktop.a11y.magnifier.mouse-tracking the setting will have
  an effect.

  [Test Case]

  To reproduce
  * Open gnome control centre and select universal access.
  * Click on Zoom.
  * Toggle between "Keep the mouse cursor centred" and the other two options 
(proportional and push).
  * If you enable Zoom and change these settings they have no effect.
  * Open dconf-editor.
  * Navigate to:

  org/gnome/desktop/a11y/magnifier/

  * Select the mouse tracking entry and change the setting to different
  values while the Zoom is enabled. The setting will change the way the
  mouse tracking behaves.

  Then install gnome-control-center{,-data,-faces} from disco-proposed
  and find that the UI now successfully changes the dconf values and the
  mouse tracking behavior.

  [Regression Potential]

  The code changes are specific to the Zoom Options window, where some
  of the options are currently broken. Low regression risk.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-control-center/+bug/1831144/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1833867] [NEW] graphics turn sowy then black screen

2019-06-23 Thread andrew meany
Public bug reported:

bad graphcis

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 4.15.0-52.56-generic 4.15.18
Uname: Linux 4.15.0-52-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia
.proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  340.107  Thu May 24 21:54:01 
PDT 2018
 GCC version:  gcc version 7.4.0 (Ubuntu 7.4.0-1ubuntu1~18.04.1)
ApportVersion: 2.20.9-0ubuntu7.6
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Sun Jun 23 13:50:05 2019
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
DkmsStatus:
 xpad, 0.4, 4.15.0-52-generic, x86_64: installed
 xpad, 0.4, 4.18.0-21-generic, x86_64: installed
 xpad, 0.4, 4.18.0-22-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
 NVIDIA Corporation G80 [GeForce 8800 GTX] [10de:0191] (rev a2) (prog-if 00 
[VGA controller])
   Subsystem: NVIDIA Corporation G80 [GeForce 8800 GTX] [10de:039c]
InstallationDate: Installed on 2018-01-28 (511 days ago)
InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210)
Lsusb:
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 002 Device 003: ID 413c:2113 Dell Computer Corp. 
 Bus 002 Device 002: ID 1bcf:053e Sunplus Innovation Technology Inc. 
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: Dell Inc. Dell XPS720
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-52-generic 
root=UUID=f61c2552-e2fd-436d-85a5-9fde323a4908 ro recovery nomodeset nomodeset
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
XorgLogOld:
 
dmi.bios.date: 08/23/2007
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A03
dmi.board.name: 0YU822
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 7
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvrA03:bd08/23/2007:svnDellInc.:pnDellXPS720:pvr:rvnDellInc.:rn0YU822:rvrA00:cvnDellInc.:ct7:cvr:
dmi.product.name: Dell XPS720
dmi.sys.vendor: Dell Inc.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.95-1~18.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2
version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core N/A
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

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


** Tags: amd64 apport-bug bionic 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/1833867

Title:
  graphics turn sowy then black screen

Status in xorg package in Ubuntu:
  New

Bug description:
  bad graphcis

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-52.56-generic 4.15.18
  Uname: Linux 4.15.0-52-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  340.107  Thu May 24 21:54:01 
PDT 2018
   GCC version:  gcc version 7.4.0 (Ubuntu 7.4.0-1ubuntu1~18.04.1)
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jun 23 13:50:05 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   xpad, 0.4, 4.15.0-52-generic, x86_64: installed
   xpad, 0.4, 4.18.0-21-generic, x86_64: installed
   xpad, 0.4, 4.18.0-22-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation G80 [GeForce 8800 GTX] [10de:0191] (rev a2) (prog-if 00 
[VGA controller])
 Subsystem: NVIDIA Corporation G80 [GeForce 8800 GTX] [10de:039c]
  InstallationDate: Installed on 2018-01-28 (511 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 003: ID 413c:2113 Dell Computer Corp. 
   Bus 002 Device 002: ID 1bcf:053e Sunplus Innovation Technology Inc. 
   Bus 002 Device 001: ID 1d6b:0001 Linux Foun

[Desktop-packages] [Bug 1777285] Re: Batch libreoffice --convert-to offers no way to wait for document completion

2019-06-23 Thread Richard Elkins
Done today: https://ask.libreoffice.org/en/question/198713/executed-
from-linux-command-line-convert-to-is-unexpectedly-asynchronous/

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libreoffice in Ubuntu.
https://bugs.launchpad.net/bugs/1777285

Title:
  Batch libreoffice --convert-to offers no way to wait for document
  completion

Status in libreoffice package in Ubuntu:
  Confirmed

Bug description:
  Command-line: libreoffice --convert-to odt:writer8 myfile.txt

  The returned status code ($?) is zero.  So far, so good.  But, when I
  try to access the ODT file (E.g. copy it), it doesn't yet exist.

  Adding `sync; sync; sync` right after the libreoffice batch execution did not 
help.
  Adding --headless as an option did not help.

  If I sleep for a few seconds immediately after the libreoffice batch
  execution, then the file finally gets completed before a subsequent
  command references the ODT file.

  Sample script:

  ### Create somehow a file called myfile.txt
  rm myfile.odt somewhere-else.odt
  libreoffice --headless --convert-to odt:writer8 myfile.txt
  RC=$?
  if [ $RC -ne 0 ]; then 
echo '*** libreoffice conversion failed for myfile.txt'
exit 86
  fi
  #sleep 3
  ls *.odt

  Result: ls: cannot access '*.odt': No such file or directory

  If one changes the above script so that the sleep is executed, then
  the ODT file is available.

  Observation: It appears that executing libreoffice in batch mode is
  somehow kicking off a separate process to finish the ODT file.  The
  exit to the shell and the availability of the ODT file should be
  synchronized.

  Before 18.04, I never saw this behavior.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libreoffice 1:6.0.3-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  Uname: Linux 4.15.0-23-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Sat Jun 16 17:07:02 2018
  InstallationDate: Installed on 2017-10-13 (246 days ago)
  InstallationMedia: Xubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  SourcePackage: libreoffice
  UpgradeStatus: Upgraded to bionic on 2018-05-18 (29 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1777285/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1833745] Re: [MIR] required new dependency of appstream

2019-06-23 Thread Rik Mills
** Description changed:

+ Availability
+ 
+ Built for all supported architectures. One upstream release ahead of Debian.
+ 
+ Rationale
+ =
+ Now a required build and runtime dependency of appstream in -proposed in Eoan
+ 
  
https://github.com/ximion/appstream/commit/358e9394631b87797f56dcb7e09e459b4044e631#commitcomment-33995178
  
  Quote "Compiling AppStream without LMDB is not really possible."
  
- appstream/0.12.7-1 currently in -proposed now depends on liblmdb0 (>=
- 0.9.7)
+ Security
+ 
+ No known CVEs.
+ https://security-tracker.debian.org/tracker/source-package/lmdb
+ 
+ Quality assurance
+ =
+ - dh_auto_test run at build time for supported architectures.
+ - No functional outstanding bugs in Ubuntu or Debian. Upstream 'issue' 
tracker is active.
+ https://bugs.launchpad.net/ubuntu/+source/libnfs
+ https://bugs.debian.org/cgi-bin/pkgreport.cgi?src=lmdb
+ 
https://www.openldap.org/its/index.cgi/Software%20Bugs?page=1;expression=lmdb;page=1
+ 
+ Dependencies
+ 
+ No universe binary dependencies
+ 
+ Standards compliance
+ 
+ 4.1.5.0 , debhelper compat 9
+ 
+ Maintenance
+ ===
+ Actively maintained:
+ 
http://www.openldap.org/devel/gitweb.cgi?p=openldap.git;a=history;f=libraries/liblmdb;hb=HEAD
+ 
+ Not team maintained in Debian.
+ https://tracker.debian.org/pkg/lmdb

** Description changed:

  Availability
  
  Built for all supported architectures. One upstream release ahead of Debian.
  
  Rationale
  =
  Now a required build and runtime dependency of appstream in -proposed in Eoan
  
  
https://github.com/ximion/appstream/commit/358e9394631b87797f56dcb7e09e459b4044e631#commitcomment-33995178
  
  Quote "Compiling AppStream without LMDB is not really possible."
  
  Security
  
  No known CVEs.
  https://security-tracker.debian.org/tracker/source-package/lmdb
  
  Quality assurance
  =
  - dh_auto_test run at build time for supported architectures.
  - No functional outstanding bugs in Ubuntu or Debian. Upstream 'issue' 
tracker is active.
- https://bugs.launchpad.net/ubuntu/+source/libnfs
+ https://bugs.launchpad.net/ubuntu/+source/lmdb
  https://bugs.debian.org/cgi-bin/pkgreport.cgi?src=lmdb
  
https://www.openldap.org/its/index.cgi/Software%20Bugs?page=1;expression=lmdb;page=1
  
  Dependencies
  
  No universe binary dependencies
  
  Standards compliance
  
  4.1.5.0 , debhelper compat 9
  
  Maintenance
  ===
  Actively maintained:
  
http://www.openldap.org/devel/gitweb.cgi?p=openldap.git;a=history;f=libraries/liblmdb;hb=HEAD
  
  Not team maintained in Debian.
  https://tracker.debian.org/pkg/lmdb

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lmdb in Ubuntu.
https://bugs.launchpad.net/bugs/1833745

Title:
  [MIR] required new dependency of appstream

Status in lmdb package in Ubuntu:
  New

Bug description:
  Availability
  
  Built for all supported architectures. One upstream release ahead of Debian.

  Rationale
  =
  Now a required build and runtime dependency of appstream in -proposed in Eoan

  
https://github.com/ximion/appstream/commit/358e9394631b87797f56dcb7e09e459b4044e631#commitcomment-33995178

  Quote "Compiling AppStream without LMDB is not really possible."

  Security
  
  No known CVEs.
  https://security-tracker.debian.org/tracker/source-package/lmdb

  Quality assurance
  =
  - dh_auto_test run at build time for supported architectures.
  - No functional outstanding bugs in Ubuntu or Debian. Upstream 'issue' 
tracker is active.
  https://bugs.launchpad.net/ubuntu/+source/lmdb
  https://bugs.debian.org/cgi-bin/pkgreport.cgi?src=lmdb
  
https://www.openldap.org/its/index.cgi/Software%20Bugs?page=1;expression=lmdb;page=1

  Dependencies
  
  No universe binary dependencies

  Standards compliance
  
  4.1.5.0 , debhelper compat 9

  Maintenance
  ===
  Actively maintained:
  
http://www.openldap.org/devel/gitweb.cgi?p=openldap.git;a=history;f=libraries/liblmdb;hb=HEAD

  Not team maintained in Debian.
  https://tracker.debian.org/pkg/lmdb

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lmdb/+bug/1833745/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1833858] Re: nautilus crashed with SIGSEGV

2019-06-23 Thread Apport retracing service
*** This bug is a duplicate of bug 1822195 ***
https://bugs.launchpad.net/bugs/1822195

Thank you for taking the time to report this crash and helping to make
this software better.  This particular crash has already been reported
and is a duplicate of bug #1822195, so 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.  Please continue to report any other bugs you may
find.

** Attachment removed: "CoreDump.gz"
   
https://bugs.launchpad.net/bugs/1833858/+attachment/5272511/+files/CoreDump.gz

** Attachment removed: "Disassembly.txt"
   
https://bugs.launchpad.net/bugs/1833858/+attachment/5272513/+files/Disassembly.txt

** Attachment removed: "ProcMaps.txt"
   
https://bugs.launchpad.net/bugs/1833858/+attachment/5272516/+files/ProcMaps.txt

** Attachment removed: "ProcStatus.txt"
   
https://bugs.launchpad.net/bugs/1833858/+attachment/5272517/+files/ProcStatus.txt

** Attachment removed: "Registers.txt"
   
https://bugs.launchpad.net/bugs/1833858/+attachment/5272518/+files/Registers.txt

** Attachment removed: "Stacktrace.txt"
   
https://bugs.launchpad.net/bugs/1833858/+attachment/5272519/+files/Stacktrace.txt

** Attachment removed: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1833858/+attachment/5272520/+files/ThreadStacktrace.txt

** This bug has been marked a duplicate of bug 1822195
   nautilus crashed with SIGSEGV

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nautilus in Ubuntu.
https://bugs.launchpad.net/bugs/1833858

Title:
  nautilus crashed with SIGSEGV

Status in nautilus package in Ubuntu:
  New

Bug description:
  something to do with chrome and the grafics

  ProblemType: Crash
  DistroRelease: Ubuntu 19.10
  Package: nautilus 1:3.32.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-17.18-generic 5.0.8
  Uname: Linux 5.0.0-16-generic x86_64
  ApportVersion: 2.20.11-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jun 23 17:38:41 2019
  ExecutablePath: /usr/bin/nautilus
  GsettingsChanges: b'org.gnome.nautilus.window-state' b'initial-size' b'(890, 
792)'
  InstallationDate: Installed on 2018-12-25 (180 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  ProcCmdline: /usr/bin/nautilus --gapplication-service
  ProcEnviron:
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
   PATH=(custom, no user)
   LANG=sv_SE.UTF-8
  SegvAnalysis:
   Segfault happened at: 0x7f75e5bd0eb8:mov0x380(%rax),%rax
   PC (0x7f75e5bd0eb8) ok
   source "0x380(%rax)" (0x0380) not located in a known VMA region (needed 
readable region)!
   destination "%rax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: nautilus
  StacktraceTop:
   () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
  Title: nautilus crashed with SIGSEGV
  UpgradeStatus: Upgraded to eoan on 2019-06-09 (13 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  separator:
   
  usr_lib_nautilus:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1833858/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1827843] Re: App grid is missing pages of icons

2019-06-23 Thread gmagoon
Hi any idea what could be causing this problem?
The problem still persists by the way.. Thanks.

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

Title:
  App grid is missing pages of icons

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Hi
  I am using Ubuntu 18.04. The App Menu Drawer doesn't show up always fully 
with all the icons. Sometimes one page shows up while the rest of the pages are 
empty. Not sure what caused this Thanks!

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-48.51-generic 4.15.18
  Uname: Linux 4.15.0-48-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon May  6 14:07:50 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: No
  GraphicsCard:
   Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA 
controller])
 Subsystem: Dell HD Graphics 5500 [1028:06b0]
  InstallationDate: Installed on 2019-02-10 (85 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: Dell Inc. Inspiron 3558
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-48-generic 
root=UUID=11c430c4-0277-4837-abc2-5daafb4e3cd5 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/27/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A17
  dmi.board.name: 0PNFDX
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA17:bd08/27/2018:svnDellInc.:pnInspiron3558:pvr:rvnDellInc.:rn0PNFDX:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Inspiron 3558
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.95-1~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1827843/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1833855] [NEW] video card

2019-06-23 Thread Alain Guay
Public bug reported:

hi!  some problem.  i have an video intel graphic card Q965 but i dont
have any hi-resolution like 1080.  i'm in vga mode only.  Can you help
me?

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 4.18.0-22.23~18.04.1-generic 4.18.20
Uname: Linux 4.18.0-22-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.6
Architecture: amd64
BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Sun Jun 23 09:58:42 2019
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation 82Q963/Q965 Integrated Graphics Controller [8086:2992] (rev 
02) (prog-if 00 [VGA controller])
   Subsystem: Dell 82Q963/Q965 Integrated Graphics Controller [1028:01da]
   Subsystem: Dell 82Q963/Q965 Integrated Graphics Controller [1028:01da]
InstallationDate: Installed on 2019-06-18 (5 days ago)
InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210)
MachineType: Dell Inc. OptiPlex 745
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-22-generic 
root=UUID=017d360b-c7a7-47e3-8d37-669b93a45647 ro quiet splash 
video=hyperv_fb:1280x720 vt.handoff=1
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/01/2010
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 2.6.4
dmi.board.name: 0GW726
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 16
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr2.6.4:bd03/01/2010:svnDellInc.:pnOptiPlex745:pvr:rvnDellInc.:rn0GW726:rvr:cvnDellInc.:ct16:cvr:
dmi.product.name: OptiPlex 745
dmi.sys.vendor: Dell Inc.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.98+git1906111830.5db0f7~oibaf~b
version.libgl1-mesa-dri: libgl1-mesa-dri 19.2~git1906191930.9c19d0~oibaf~b
version.libgl1-mesa-glx: libgl1-mesa-glx 19.2~git1906191930.9c19d0~oibaf~b
version.xserver-xorg-core: xserver-xorg-core N/A
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

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


** Tags: amd64 apport-bug bionic third-party-packages 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/1833855

Title:
  video card

Status in xorg package in Ubuntu:
  New

Bug description:
  hi!  some problem.  i have an video intel graphic card Q965 but i dont
  have any hi-resolution like 1080.  i'm in vga mode only.  Can you help
  me?

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.18.0-22.23~18.04.1-generic 4.18.20
  Uname: Linux 4.18.0-22-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jun 23 09:58:42 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 82Q963/Q965 Integrated Graphics Controller [8086:2992] 
(rev 02) (prog-if 00 [VGA controller])
 Subsystem: Dell 82Q963/Q965 Integrated Graphics Controller [1028:01da]
 Subsystem: Dell 82Q963/Q965 Integrated Graphics Controller [1028:01da]
  InstallationDate: Installed on 2019-06-18 (5 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  MachineType: Dell Inc. OptiPlex 745
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-22-generic 
root=UUID=017d360b-c7a7-47e3-8d37-669b93a45647 ro quiet splash 
video=hyperv_fb:1280x720 vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/01/2010
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.6.4
  dmi.board.name: 0GW726
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 16
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.6.4:bd03/01/2010:svnDellInc.:pnOptiPlex745:pvr:rvnDellInc.:rn0GW726:rvr:cvnDellInc.:ct16:cvr:
  dmi.product.name: OptiPlex 745
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.98+git1906111830.5db0f7~oibaf~b
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2~git1906191930.9c19d0~oibaf~b
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.2~git1906191930.9c19d0~oibaf~b
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

To manage notificati