[Desktop-packages] [Bug 1819406] [NEW] Found broken a feature for fingerprint image obfuscation
Public bug reported: Dear all, In this package, a random seed is used for generation key for obfuscating a fingerprint image in uru4000 driver. Unfortunately, it seems that the seed always exhibits the same sequence of numbers each time since it is generated from rand() in libc by default. Then I reported this issue to the upstream with the patch. However, the maintainer insists that the obfuscation-feature can be broken since the key for encryption is composed of just 4-bytes length. Thus, there is no need to patch about random seed anyway. It's pretty weird to say that. Would it be all right if I leave this as it is? Many thanks!! ** Affects: libfprint (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libfprint in Ubuntu. https://bugs.launchpad.net/bugs/1819406 Title: Found broken a feature for fingerprint image obfuscation Status in libfprint package in Ubuntu: New Bug description: Dear all, In this package, a random seed is used for generation key for obfuscating a fingerprint image in uru4000 driver. Unfortunately, it seems that the seed always exhibits the same sequence of numbers each time since it is generated from rand() in libc by default. Then I reported this issue to the upstream with the patch. However, the maintainer insists that the obfuscation-feature can be broken since the key for encryption is composed of just 4-bytes length. Thus, there is no need to patch about random seed anyway. It's pretty weird to say that. Would it be all right if I leave this as it is? Many thanks!! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libfprint/+bug/1819406/+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 1811096] Re: gnome-shell[2843]: The offending signal was destroy on StBoxLayout 0x5606a3267650.
[Expired for gnome-shell (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => Expired -- 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/1811096 Title: gnome-shell[2843]: The offending signal was destroy on StBoxLayout 0x5606a3267650. Status in gnome-shell package in Ubuntu: Expired Bug description: https://gitlab.gnome.org/GNOME/gnome-shell/issues/896 --- Hello, I'm working with vlc and frezze gnome-shell (attached log file). $ journalctl -b-1 ene 09 10:47:16 romanescu org.gnome.Shell.desktop[2843]: == Stack trace for context 0x5606981781b0 == ene 09 10:47:16 romanescu org.gnome.Shell.desktop[2843]: #0 7ffde02d1690 I resource:///org/gnome/shell/ui/popupMenu.js:221 (7f116b91dee0 @ 22) ene 09 10:47:16 romanescu org.gnome.Shell.desktop[2843]: #1 7ffde02d1750 b resource:///org/gnome/gjs/modules/_legacy.js:82 (7f116bbb0b80 @ 71) ene 09 10:47:16 romanescu org.gnome.Shell.desktop[2843]: #2 7ffde02d17d0 I /usr/share/gnome-shell/extensions/ubuntu-appindicat...@ubuntu.com/dbusMenu.js:736 (7f11499c3a60 @ 30) ene 09 10:47:16 romanescu org.gnome.Shell.desktop[2843]: #3 7ffde02d17d0 I self-hosted:261 (7f116bbc1dc0 @ 223) ene 09 10:47:16 romanescu org.gnome.Shell.desktop[2843]: #4 7ffde02d17d0 I /usr/share/gnome-shell/extensions/ubuntu-appindicat...@ubuntu.com/dbusMenu.js:734 (7f11499c39d0 @ 37) ene 09 10:47:16 romanescu org.gnome.Shell.desktop[2843]: #5 7ffde02d18a0 b resource:///org/gnome/gjs/modules/_legacy.js:82 (7f116bbb0b80 @ 71) ene 09 10:47:16 romanescu org.gnome.Shell.desktop[2843]: #6 7ffde02d1920 I self-hosted:979 (7f116bbf0280 @ 440) ene 09 10:47:16 romanescu org.gnome.Shell.desktop[2843]: #7 7ffde02d19a0 I self-hosted:979 (7f116bbf0280 @ 440) ene 09 10:47:16 romanescu org.gnome.Shell.desktop[2843]: #8 7ffde02d1a30 I resource:///org/gnome/gjs/modules/signals.js:128 (7f116bbc18b0 @ 386) ene 09 10:47:16 romanescu org.gnome.Shell.desktop[2843]: #9 7ffde02d1a90 I /usr/share/gnome-shell/extensions/ubuntu-appindicat...@ubuntu.com/dbusMenu.js:154 (7f11499beaf0 @ 224) ene 09 10:47:16 romanescu org.gnome.Shell.desktop[2843]: #10 7ffde02d1b60 b resource:///org/gnome/gjs/modules/_legacy.js:82 (7f116bbb0b80 @ 71) ene 09 10:47:16 romanescu org.gnome.Shell.desktop[2843]: #11 7ffde02d1ba0 I /usr/share/gnome-shell/extensions/ubuntu-appindicat...@ubuntu.com/dbusMenu.js:352 (7f11499c1700 @ 36) ene 09 10:47:16 romanescu org.gnome.Shell.desktop[2843]: #12 7ffde02d1c70 I self-hosted:261 (7f116bbc1dc0 @ 223) ene 09 10:47:16 romanescu org.gnome.Shell.desktop[2843]: #13 7ffde02d1c70 I /usr/share/gnome-shell/extensions/ubuntu-appindicat...@ubuntu.com/dbusMenu.js:352 (7f11499c1550 @ 808) ene 09 10:47:16 romanescu org.gnome.Shell.desktop[2843]: #14 7ffde02d1d40 b resource:///org/gnome/gjs/modules/_legacy.js:82 (7f116bbb0b80 @ 71) ene 09 10:47:16 romanescu org.gnome.Shell.desktop[2843]: #15 7ffde02d1e00 b /usr/share/gnome-shell/extensions/ubuntu-appindicat...@ubuntu.com/dbusMenu.js:305 (7f11499c14c0 @ 274) ene 09 10:47:16 romanescu org.gnome.Shell.desktop[2843]: #16 7ffde02d1ed0 b resource:///org/gnome/gjs/modules/_legacy.js:82 (7f116bbb0b80 @ 71) ene 09 10:47:16 romanescu org.gnome.Shell.desktop[2843]: #17 7ffde02d1f50 I self-hosted:979 (7f116bbf0280 @ 440) ene 09 10:47:16 romanescu org.gnome.Shell.desktop[2843]: #18 7ffde02d2020 b resource:///org/gnome/gjs/modules/overrides/Gio.js:78 (7f116bbb89d0 @ 113) Best regards, -- Cristian Aravena Romero (caravena) ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-shell 3.30.1-2ubuntu3 Uname: Linux 4.20.0-042000-generic x86_64 ApportVersion: 2.20.10-0ubuntu14 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Jan 9 10:56:00 2019 DisplayManager: gdm3 GsettingsChanges: b'org.gnome.shell' b'enabled-extensions' b"['mediapla...@patapon.info', 'ubuntu-d...@ubuntu.com', 'system-moni...@paradoxxx.zero.gmail.com']" b'org.gnome.shell' b'had-bluetooth-devices-setup' b'true' b'org.gnome.shell' b'app-picker-view' b'uint32 1' b'org.gnome.shell' b'favorite-apps' redacted by apport b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2018-12-02 (37 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: gnome-shell UpgradeStatus: Upgraded to disco on 2018-12-02 (37 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1811096/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help :
[Desktop-packages] [Bug 1799266] Re: gnome-shell uses high CPU when simply moving windows
I think it's too early for this to be a release bug. A bunch of fixes are still awaiting upstream review, some require more upstream work by me, and the final one needs to be rewritten completely after so re- profiling. Lots of upstream work to do before considering this for distro. ** No longer affects: gnome-shell (Ubuntu Bionic) ** No longer affects: gnome-shell (Ubuntu Cosmic) ** No longer affects: gnome-shell (Ubuntu Disco) ** No longer affects: mutter (Ubuntu Bionic) ** No longer affects: mutter (Ubuntu Cosmic) ** No longer affects: mutter (Ubuntu Disco) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gjs in Ubuntu. https://bugs.launchpad.net/bugs/1799266 Title: gnome-shell uses high CPU when simply moving windows Status in gjs package in Ubuntu: Fix Released Status in gnome-shell package in Ubuntu: In Progress Status in mutter package in Ubuntu: In Progress Status in gjs source package in Bionic: Fix Released Status in gjs source package in Cosmic: Fix Released Status in gjs source package in Disco: Fix Released Bug description: After doing a stock install Ubuntu 18.04.1 LTS on an imac 27" 2010 8G ram, Intel® Core™ i7 CPU 870 @ 2.93GHz × 8 Simply moving a window around on the screen increases the cpu usage by gnome-shell to 44%. When displaying a movie, totem takes 10%, gnome-shell takes 22%. etc etc System:Host: oldie Kernel: 4.15.0-36-generic x86_64 bits: 64 Desktop: Gnome 3.28.3 Distro: Ubuntu 18.04.1 LTS Machine: Device: desktop System: Apple product: iMac11 3 v: 1.0 serial: N/A Mobo: Apple model: Mac-F2238BAE v: iMac11 3 serial: N/A UEFI: Apple v: IM112.88Z.0057.B01.1112090906 date: 12/09/11 CPU: Quad core Intel Core i7 870 (-MT-MCP-) cache: 8192 KB clock speeds: max: 2927 MHz 1: 1271 MHz 2: 1206 MHz 3: 1374 MHz 4: 1271 MHz 5: 1377 MHz 6: 1266 MHz 7: 1693 MHz 8: 1279 MHz Graphics: Card: Advanced Micro Devices [AMD/ATI] Broadway PRO [Mobility Radeon HD 5850] Display Server: x11 (X.Org 1.19.6 ) driver: radeon Resolution: 2560x1440@59.95hz OpenGL: renderer: AMD JUNIPER (DRM 2.50.0 / 4.15.0-36-generic, LLVM 6.0.0) version: 3.3 Mesa 18.0.5 Audio: Card-1 Intel 5 Series/3400 Series High Definition Audio driver: snd_hda_intel Card-2 Advanced Micro Devices [AMD/ATI] Juniper HDMI Audio [Radeon HD 5700 Series] driver: snd_hda_intel Sound: Advanced Linux Sound Architecture v: k4.15.0-36-generic Network: Card-1: Broadcom Limited NetXtreme BCM5764M Gigabit Ethernet PCIe driver: tg3 IF: enp2s0 state: up speed: 1000 Mbps duplex: full mac: c4:2c:03:30:ce:8e Card-2: Qualcomm Atheros AR928X Wireless Network Adapter (PCI-Express) driver: ath9k IF: wls1 state: down mac: d8:30:62:67:2a:19 Drives:HDD Total Size: 2500.5GB (38.0% used) ID-1: /dev/sda model: WDC_WD1001FALS size: 1000.2GB ID-2: USB /dev/sdb model: MK1059GSM size: 1000.2GB ID-3: USB /dev/sdd model: Elements_10B8 size: 500.1GB Partition: ID-1: / size: 226G used: 125G (58%) fs: ext4 dev: /dev/sda2 ID-2: /home size: 701G used: 876M (1%) fs: btrfs dev: /dev/sda4 RAID: No RAID devices: /proc/mdstat, md_mod kernel module present Sensors: System Temperatures: cpu: 56.0C mobo: N/A Fan Speeds (in rpm): cpu: 936 Info: Processes: 342 Uptime: 3:07 Memory: 2087.3/7967.4MB Client: Shell (bash) inxi: 2.3.56 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.3-0ubuntu0.18.04.2 ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Uname: Linux 4.15.0-36-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Oct 22 19:09:59 2018 DisplayManager: gdm3 GsettingsChanges: b'org.gnome.shell' b'disable-user-extensions' b'true' b'org.gnome.shell' b'app-picker-view' b'uint32 1' b'org.gnome.shell' b'favorite-apps' redacted by apport b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2018-10-22 (0 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=sv_SE.UTF-8 SHELL=/bin/bash SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/1799266/+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 1818972] Re: [regression] GLX is missing. gnome-shell visible latency is very high with Xorg 2:1.20.4-1ubuntu1
** Changed in: xorg-server (Ubuntu)
Status: Fix Committed => Fix Released
--
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/1818972
Title:
[regression] GLX is missing. gnome-shell visible latency is very high
with Xorg 2:1.20.4-1ubuntu1
Status in xorg-server package in Ubuntu:
Fix Released
Bug description:
[Impact]
GLX is missing. gnome-shell visible latency is very high with Xorg
2:1.20.4-1ubuntu1. And reinstalling the previous version
(2:1.20.3-1ubuntu1) seems to fix it.
[Test Case]
$ glxinfo
Expected: Lots of information
Observed: An error
- or -
1. Log into a gnome-shell Xorg session ("Ubuntu").
2. Drag a window around in circles by its titlebar.
Expected: The mouse pointer to be somewhere near the titlebar
Observed: The mouse pointer is a long way away.
[Other Info]
Crucially, my patches to mutter's clutter-stage-cogl.c no longer have
any effect when this Xorg regression is present. So I can tell the
problem is related to some missing/broken X11 feature that is causing
the mutter master clock to fall back to its secondary vsync method (no
sync at all, just swapbuffers till they're all full, so typically
quad-buffering).
[Workarounds]
* Install Xorg 2:1.20.3-1ubuntu1 instead; or
* Use Wayland sessions only.
[Original description]
ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: xserver-xorg-core 2:1.20.4-1ubuntu1
ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0
Uname: Linux 5.0.0-7-generic x86_64
ApportVersion: 2.20.10-0ubuntu23
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'
Date: Thu Mar 7 16:24:50 2019
DistUpgraded: Fresh install
DistroCodename: disco
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
Intel Corporation HD Graphics 630 [8086:5912] (rev 04) (prog-if 00 [VGA
controller])
Subsystem: Lenovo HD Graphics 630 [17aa:3102]
InstallationDate: Installed on 2018-12-04 (93 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20181203)
MachineType: LENOVO 10M7CTO1WW
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-7-generic
root=UUID=052b7096-9b82-4712-b596-7629d5f6498c ro quiet splash vt.handoff=1
SourcePackage: xorg-server
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/06/2018
dmi.bios.vendor: LENOVO
dmi.bios.version: M16KT47A
dmi.board.name: 3102
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40709 WIN 3259627060530
dmi.chassis.type: 3
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias:
dmi:bvnLENOVO:bvrM16KT47A:bd02/06/2018:svnLENOVO:pn10M7CTO1WW:pvrThinkCentreM710s:rvnLENOVO:rn3102:rvrSDK0J40709WIN3259627060530:cvnLENOVO:ct3:cvrNone:
dmi.product.family: ThinkCentre M710s
dmi.product.name: 10M7CTO1WW
dmi.product.sku: LENOVO_MT_10M7_BU_Think_FM_ThinkCentre M710s
dmi.product.version: ThinkCentre M710s
dmi.sys.vendor: LENOVO
version.compiz: compiz 1:0.9.14.0+19.04.20190223.1-0ubuntu1
version.libdrm2: libdrm2 2.4.97-1
version.libgl1-mesa-dri: libgl1-mesa-dri 18.3.4-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 18.3.4-1ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.99+git20190207-1
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-server/+bug/1818972/+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 1818829] XorgLogOld.txt
apport information ** Attachment added: "XorgLogOld.txt" https://bugs.launchpad.net/bugs/1818829/+attachment/5245310/+files/XorgLogOld.txt -- 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/1818829 Title: Disconnected monitors act as present Status in xorg-server package in Ubuntu: Incomplete Bug description: I add a custom mode for my monitor using xrandr at boot. It looks like this: xrandr --newmode "2560x1440R" 241.50 2560 2608 2640 2720 1440 1443 1448 1481 +hsync -vsync xrandr --addmode HDMI-1 "2560x1440R" xrandr --output HDMI-1 --mode "2560x1440R" xrandr --output HDMI-1 --pos 0x0 xrandr --output eDP-1 --pos 2560x360 Starting recently, since I installed Ubuntu 18.04.2 (was using .1 before), even though the monitor isn't connected, that "space" is still there. I can move my mouse out of my laptop screen and it goes over where the monitor would be and gets lost. And screenshots (Print Screen) captures a large blank space as if the monitor were connected. As I said, this just started happening recently but I don't remember exactly what update caused it. All I know is before I installed 18.04.2, this didn't happen. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME DistUpgraded: Fresh install DistroCodename: bionic DistroRelease: Ubuntu 18.04 DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 620 [1028:0804] InstallationDate: Installed on 2019-02-16 (22 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: Dell Inc. Inspiron 5379 Package: xorg-server (not installed) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-16-generic root=UUID=a0583427-a9f8-49aa-89d2-bb8e77de9a58 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.18.0-16.17~18.04.1-generic 4.18.20 Tags: bionic ubuntu Uname: Linux 4.18.0-16-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/19/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.10.0 dmi.board.name: 05G60G dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.10.0:bd07/19/2018:svnDellInc.:pnInspiron5379:pvr:rvnDellInc.:rn05G60G:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 5379 dmi.product.sku: 0804 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.96-0~b~padoka0 version.libgl1-mesa-dri: libgl1-mesa-dri 18.3.3-1~b~padoka0 version.libgl1-mesa-glx: libgl1-mesa-glx 18.3.3-1~b~padoka0 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-server/+bug/1818829/+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 1818829] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1818829/+attachment/5245306/+files/ProcInterrupts.txt -- 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/1818829 Title: Disconnected monitors act as present Status in xorg-server package in Ubuntu: Incomplete Bug description: I add a custom mode for my monitor using xrandr at boot. It looks like this: xrandr --newmode "2560x1440R" 241.50 2560 2608 2640 2720 1440 1443 1448 1481 +hsync -vsync xrandr --addmode HDMI-1 "2560x1440R" xrandr --output HDMI-1 --mode "2560x1440R" xrandr --output HDMI-1 --pos 0x0 xrandr --output eDP-1 --pos 2560x360 Starting recently, since I installed Ubuntu 18.04.2 (was using .1 before), even though the monitor isn't connected, that "space" is still there. I can move my mouse out of my laptop screen and it goes over where the monitor would be and gets lost. And screenshots (Print Screen) captures a large blank space as if the monitor were connected. As I said, this just started happening recently but I don't remember exactly what update caused it. All I know is before I installed 18.04.2, this didn't happen. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME DistUpgraded: Fresh install DistroCodename: bionic DistroRelease: Ubuntu 18.04 DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 620 [1028:0804] InstallationDate: Installed on 2019-02-16 (22 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: Dell Inc. Inspiron 5379 Package: xorg-server (not installed) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-16-generic root=UUID=a0583427-a9f8-49aa-89d2-bb8e77de9a58 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.18.0-16.17~18.04.1-generic 4.18.20 Tags: bionic ubuntu Uname: Linux 4.18.0-16-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/19/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.10.0 dmi.board.name: 05G60G dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.10.0:bd07/19/2018:svnDellInc.:pnInspiron5379:pvr:rvnDellInc.:rn05G60G:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 5379 dmi.product.sku: 0804 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.96-0~b~padoka0 version.libgl1-mesa-dri: libgl1-mesa-dri 18.3.3-1~b~padoka0 version.libgl1-mesa-glx: libgl1-mesa-glx 18.3.3-1~b~padoka0 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-server/+bug/1818829/+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 1818829] Re: Disconnected monitors act as present
Done. I changed a couple things since reporting this though. I stopped setting the screen positions in the initial commands I posted. I booted with no monitor attached, without running the script, then connected the monitor and ran it (again, without settings positions) and sent the report while the laptop display was disabled (only using external monitor.) If you need me to run it some other way let me know. -- 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/1818829 Title: Disconnected monitors act as present Status in xorg-server package in Ubuntu: Incomplete Bug description: I add a custom mode for my monitor using xrandr at boot. It looks like this: xrandr --newmode "2560x1440R" 241.50 2560 2608 2640 2720 1440 1443 1448 1481 +hsync -vsync xrandr --addmode HDMI-1 "2560x1440R" xrandr --output HDMI-1 --mode "2560x1440R" xrandr --output HDMI-1 --pos 0x0 xrandr --output eDP-1 --pos 2560x360 Starting recently, since I installed Ubuntu 18.04.2 (was using .1 before), even though the monitor isn't connected, that "space" is still there. I can move my mouse out of my laptop screen and it goes over where the monitor would be and gets lost. And screenshots (Print Screen) captures a large blank space as if the monitor were connected. As I said, this just started happening recently but I don't remember exactly what update caused it. All I know is before I installed 18.04.2, this didn't happen. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME DistUpgraded: Fresh install DistroCodename: bionic DistroRelease: Ubuntu 18.04 DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 620 [1028:0804] InstallationDate: Installed on 2019-02-16 (22 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: Dell Inc. Inspiron 5379 Package: xorg-server (not installed) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-16-generic root=UUID=a0583427-a9f8-49aa-89d2-bb8e77de9a58 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.18.0-16.17~18.04.1-generic 4.18.20 Tags: bionic ubuntu Uname: Linux 4.18.0-16-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/19/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.10.0 dmi.board.name: 05G60G dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.10.0:bd07/19/2018:svnDellInc.:pnInspiron5379:pvr:rvnDellInc.:rn05G60G:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 5379 dmi.product.sku: 0804 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.96-0~b~padoka0 version.libgl1-mesa-dri: libgl1-mesa-dri 18.3.3-1~b~padoka0 version.libgl1-mesa-glx: libgl1-mesa-glx 18.3.3-1~b~padoka0 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-server/+bug/1818829/+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 1818829] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1818829/+attachment/5245305/+files/ProcEnviron.txt -- 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/1818829 Title: Disconnected monitors act as present Status in xorg-server package in Ubuntu: Incomplete Bug description: I add a custom mode for my monitor using xrandr at boot. It looks like this: xrandr --newmode "2560x1440R" 241.50 2560 2608 2640 2720 1440 1443 1448 1481 +hsync -vsync xrandr --addmode HDMI-1 "2560x1440R" xrandr --output HDMI-1 --mode "2560x1440R" xrandr --output HDMI-1 --pos 0x0 xrandr --output eDP-1 --pos 2560x360 Starting recently, since I installed Ubuntu 18.04.2 (was using .1 before), even though the monitor isn't connected, that "space" is still there. I can move my mouse out of my laptop screen and it goes over where the monitor would be and gets lost. And screenshots (Print Screen) captures a large blank space as if the monitor were connected. As I said, this just started happening recently but I don't remember exactly what update caused it. All I know is before I installed 18.04.2, this didn't happen. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME DistUpgraded: Fresh install DistroCodename: bionic DistroRelease: Ubuntu 18.04 DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 620 [1028:0804] InstallationDate: Installed on 2019-02-16 (22 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: Dell Inc. Inspiron 5379 Package: xorg-server (not installed) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-16-generic root=UUID=a0583427-a9f8-49aa-89d2-bb8e77de9a58 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.18.0-16.17~18.04.1-generic 4.18.20 Tags: bionic ubuntu Uname: Linux 4.18.0-16-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/19/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.10.0 dmi.board.name: 05G60G dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.10.0:bd07/19/2018:svnDellInc.:pnInspiron5379:pvr:rvnDellInc.:rn05G60G:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 5379 dmi.product.sku: 0804 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.96-0~b~padoka0 version.libgl1-mesa-dri: libgl1-mesa-dri 18.3.3-1~b~padoka0 version.libgl1-mesa-glx: libgl1-mesa-glx 18.3.3-1~b~padoka0 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-server/+bug/1818829/+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 1818829] Xrandr.txt
apport information ** Attachment added: "Xrandr.txt" https://bugs.launchpad.net/bugs/1818829/+attachment/5245311/+files/Xrandr.txt -- 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/1818829 Title: Disconnected monitors act as present Status in xorg-server package in Ubuntu: Incomplete Bug description: I add a custom mode for my monitor using xrandr at boot. It looks like this: xrandr --newmode "2560x1440R" 241.50 2560 2608 2640 2720 1440 1443 1448 1481 +hsync -vsync xrandr --addmode HDMI-1 "2560x1440R" xrandr --output HDMI-1 --mode "2560x1440R" xrandr --output HDMI-1 --pos 0x0 xrandr --output eDP-1 --pos 2560x360 Starting recently, since I installed Ubuntu 18.04.2 (was using .1 before), even though the monitor isn't connected, that "space" is still there. I can move my mouse out of my laptop screen and it goes over where the monitor would be and gets lost. And screenshots (Print Screen) captures a large blank space as if the monitor were connected. As I said, this just started happening recently but I don't remember exactly what update caused it. All I know is before I installed 18.04.2, this didn't happen. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME DistUpgraded: Fresh install DistroCodename: bionic DistroRelease: Ubuntu 18.04 DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 620 [1028:0804] InstallationDate: Installed on 2019-02-16 (22 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: Dell Inc. Inspiron 5379 Package: xorg-server (not installed) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-16-generic root=UUID=a0583427-a9f8-49aa-89d2-bb8e77de9a58 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.18.0-16.17~18.04.1-generic 4.18.20 Tags: bionic ubuntu Uname: Linux 4.18.0-16-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/19/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.10.0 dmi.board.name: 05G60G dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.10.0:bd07/19/2018:svnDellInc.:pnInspiron5379:pvr:rvnDellInc.:rn05G60G:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 5379 dmi.product.sku: 0804 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.96-0~b~padoka0 version.libgl1-mesa-dri: libgl1-mesa-dri 18.3.3-1~b~padoka0 version.libgl1-mesa-glx: libgl1-mesa-glx 18.3.3-1~b~padoka0 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-server/+bug/1818829/+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 1818829] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1818829/+attachment/5245307/+files/ProcModules.txt -- 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/1818829 Title: Disconnected monitors act as present Status in xorg-server package in Ubuntu: Incomplete Bug description: I add a custom mode for my monitor using xrandr at boot. It looks like this: xrandr --newmode "2560x1440R" 241.50 2560 2608 2640 2720 1440 1443 1448 1481 +hsync -vsync xrandr --addmode HDMI-1 "2560x1440R" xrandr --output HDMI-1 --mode "2560x1440R" xrandr --output HDMI-1 --pos 0x0 xrandr --output eDP-1 --pos 2560x360 Starting recently, since I installed Ubuntu 18.04.2 (was using .1 before), even though the monitor isn't connected, that "space" is still there. I can move my mouse out of my laptop screen and it goes over where the monitor would be and gets lost. And screenshots (Print Screen) captures a large blank space as if the monitor were connected. As I said, this just started happening recently but I don't remember exactly what update caused it. All I know is before I installed 18.04.2, this didn't happen. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME DistUpgraded: Fresh install DistroCodename: bionic DistroRelease: Ubuntu 18.04 DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 620 [1028:0804] InstallationDate: Installed on 2019-02-16 (22 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: Dell Inc. Inspiron 5379 Package: xorg-server (not installed) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-16-generic root=UUID=a0583427-a9f8-49aa-89d2-bb8e77de9a58 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.18.0-16.17~18.04.1-generic 4.18.20 Tags: bionic ubuntu Uname: Linux 4.18.0-16-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/19/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.10.0 dmi.board.name: 05G60G dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.10.0:bd07/19/2018:svnDellInc.:pnInspiron5379:pvr:rvnDellInc.:rn05G60G:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 5379 dmi.product.sku: 0804 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.96-0~b~padoka0 version.libgl1-mesa-dri: libgl1-mesa-dri 18.3.3-1~b~padoka0 version.libgl1-mesa-glx: libgl1-mesa-glx 18.3.3-1~b~padoka0 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-server/+bug/1818829/+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 1818829] xdpyinfo.txt
apport information ** Attachment added: "xdpyinfo.txt" https://bugs.launchpad.net/bugs/1818829/+attachment/5245312/+files/xdpyinfo.txt -- 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/1818829 Title: Disconnected monitors act as present Status in xorg-server package in Ubuntu: Incomplete Bug description: I add a custom mode for my monitor using xrandr at boot. It looks like this: xrandr --newmode "2560x1440R" 241.50 2560 2608 2640 2720 1440 1443 1448 1481 +hsync -vsync xrandr --addmode HDMI-1 "2560x1440R" xrandr --output HDMI-1 --mode "2560x1440R" xrandr --output HDMI-1 --pos 0x0 xrandr --output eDP-1 --pos 2560x360 Starting recently, since I installed Ubuntu 18.04.2 (was using .1 before), even though the monitor isn't connected, that "space" is still there. I can move my mouse out of my laptop screen and it goes over where the monitor would be and gets lost. And screenshots (Print Screen) captures a large blank space as if the monitor were connected. As I said, this just started happening recently but I don't remember exactly what update caused it. All I know is before I installed 18.04.2, this didn't happen. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME DistUpgraded: Fresh install DistroCodename: bionic DistroRelease: Ubuntu 18.04 DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 620 [1028:0804] InstallationDate: Installed on 2019-02-16 (22 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: Dell Inc. Inspiron 5379 Package: xorg-server (not installed) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-16-generic root=UUID=a0583427-a9f8-49aa-89d2-bb8e77de9a58 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.18.0-16.17~18.04.1-generic 4.18.20 Tags: bionic ubuntu Uname: Linux 4.18.0-16-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/19/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.10.0 dmi.board.name: 05G60G dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.10.0:bd07/19/2018:svnDellInc.:pnInspiron5379:pvr:rvnDellInc.:rn05G60G:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 5379 dmi.product.sku: 0804 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.96-0~b~padoka0 version.libgl1-mesa-dri: libgl1-mesa-dri 18.3.3-1~b~padoka0 version.libgl1-mesa-glx: libgl1-mesa-glx 18.3.3-1~b~padoka0 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-server/+bug/1818829/+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 1818829] Re: Disconnected monitors act as present
apport information ** Tags added: apport-collected bionic ubuntu ** Description changed: I add a custom mode for my monitor using xrandr at boot. It looks like this: xrandr --newmode "2560x1440R" 241.50 2560 2608 2640 2720 1440 1443 1448 1481 +hsync -vsync xrandr --addmode HDMI-1 "2560x1440R" xrandr --output HDMI-1 --mode "2560x1440R" xrandr --output HDMI-1 --pos 0x0 xrandr --output eDP-1 --pos 2560x360 Starting recently, since I installed Ubuntu 18.04.2 (was using .1 before), even though the monitor isn't connected, that "space" is still there. I can move my mouse out of my laptop screen and it goes over where the monitor would be and gets lost. And screenshots (Print Screen) captures a large blank space as if the monitor were connected. - As I said, this just started happening recently but I don't remember - exactly what update caused it. All I know is before I installed 18.04.2, - this didn't happen. + As I said, this just started happening recently but I don't remember exactly what update caused it. All I know is before I installed 18.04.2, this didn't happen. + --- + ProblemType: Bug + ApportVersion: 2.20.9-0ubuntu7.5 + Architecture: amd64 + BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' + CompositorRunning: None + CurrentDesktop: ubuntu:GNOME + DistUpgraded: Fresh install + DistroCodename: bionic + DistroRelease: Ubuntu 18.04 + DistroVariant: ubuntu + ExtraDebuggingInterest: Yes, including running git bisection searches + GraphicsCard: + Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) +Subsystem: Dell UHD Graphics 620 [1028:0804] + InstallationDate: Installed on 2019-02-16 (22 days ago) + InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) + MachineType: Dell Inc. Inspiron 5379 + Package: xorg-server (not installed) + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-16-generic root=UUID=a0583427-a9f8-49aa-89d2-bb8e77de9a58 ro quiet splash vt.handoff=1 + ProcVersionSignature: Ubuntu 4.18.0-16.17~18.04.1-generic 4.18.20 + Tags: bionic ubuntu + Uname: Linux 4.18.0-16-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo + _MarkForUpload: True + dmi.bios.date: 07/19/2018 + dmi.bios.vendor: Dell Inc. + dmi.bios.version: 1.10.0 + dmi.board.name: 05G60G + dmi.board.vendor: Dell Inc. + dmi.board.version: A00 + dmi.chassis.type: 10 + dmi.chassis.vendor: Dell Inc. + dmi.modalias: dmi:bvnDellInc.:bvr1.10.0:bd07/19/2018:svnDellInc.:pnInspiron5379:pvr:rvnDellInc.:rn05G60G:rvrA00:cvnDellInc.:ct10:cvr: + dmi.product.family: Inspiron + dmi.product.name: Inspiron 5379 + dmi.product.sku: 0804 + dmi.sys.vendor: Dell Inc. + version.compiz: compiz N/A + version.libdrm2: libdrm2 2.4.96-0~b~padoka0 + version.libgl1-mesa-dri: libgl1-mesa-dri 18.3.3-1~b~padoka0 + version.libgl1-mesa-glx: libgl1-mesa-glx 18.3.3-1~b~padoka0 + 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 ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1818829/+attachment/5245298/+files/CurrentDmesg.txt -- 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/1818829 Title: Disconnected monitors act as present Status in xorg-server package in Ubuntu: Incomplete Bug description: I add a custom mode for my monitor using xrandr at boot. It looks like this: xrandr --newmode "2560x1440R" 241.50 2560 2608 2640 2720 1440 1443 1448 1481 +hsync -vsync xrandr --addmode HDMI-1 "2560x1440R" xrandr --output HDMI-1 --mode "2560x1440R" xrandr --output HDMI-1 --pos 0x0 xrandr --output eDP-1 --pos 2560x360 Starting recently, since I installed Ubuntu 18.04.2 (was using .1 before), even though the monitor isn't connected, that "space" is still there. I can move my mouse out of my laptop screen and it goes over where the monitor would be and gets lost. And screenshots (Print Screen) captures a large blank space as if the monitor were connected. As I said, this just started happening recently but I don't remember exactly what update caused it. All I know is before I installed 18.04.2, this didn't happen. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME DistUpgraded: Fresh install DistroCodename: bionic DistroRelease: Ubuntu 18.04 DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation UHD
[Desktop-packages] [Bug 1818829] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1818829/+attachment/5245308/+files/UdevDb.txt -- 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/1818829 Title: Disconnected monitors act as present Status in xorg-server package in Ubuntu: Incomplete Bug description: I add a custom mode for my monitor using xrandr at boot. It looks like this: xrandr --newmode "2560x1440R" 241.50 2560 2608 2640 2720 1440 1443 1448 1481 +hsync -vsync xrandr --addmode HDMI-1 "2560x1440R" xrandr --output HDMI-1 --mode "2560x1440R" xrandr --output HDMI-1 --pos 0x0 xrandr --output eDP-1 --pos 2560x360 Starting recently, since I installed Ubuntu 18.04.2 (was using .1 before), even though the monitor isn't connected, that "space" is still there. I can move my mouse out of my laptop screen and it goes over where the monitor would be and gets lost. And screenshots (Print Screen) captures a large blank space as if the monitor were connected. As I said, this just started happening recently but I don't remember exactly what update caused it. All I know is before I installed 18.04.2, this didn't happen. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME DistUpgraded: Fresh install DistroCodename: bionic DistroRelease: Ubuntu 18.04 DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 620 [1028:0804] InstallationDate: Installed on 2019-02-16 (22 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: Dell Inc. Inspiron 5379 Package: xorg-server (not installed) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-16-generic root=UUID=a0583427-a9f8-49aa-89d2-bb8e77de9a58 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.18.0-16.17~18.04.1-generic 4.18.20 Tags: bionic ubuntu Uname: Linux 4.18.0-16-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/19/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.10.0 dmi.board.name: 05G60G dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.10.0:bd07/19/2018:svnDellInc.:pnInspiron5379:pvr:rvnDellInc.:rn05G60G:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 5379 dmi.product.sku: 0804 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.96-0~b~padoka0 version.libgl1-mesa-dri: libgl1-mesa-dri 18.3.3-1~b~padoka0 version.libgl1-mesa-glx: libgl1-mesa-glx 18.3.3-1~b~padoka0 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-server/+bug/1818829/+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 1818829] XorgLog.txt
apport information ** Attachment added: "XorgLog.txt" https://bugs.launchpad.net/bugs/1818829/+attachment/5245309/+files/XorgLog.txt -- 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/1818829 Title: Disconnected monitors act as present Status in xorg-server package in Ubuntu: Incomplete Bug description: I add a custom mode for my monitor using xrandr at boot. It looks like this: xrandr --newmode "2560x1440R" 241.50 2560 2608 2640 2720 1440 1443 1448 1481 +hsync -vsync xrandr --addmode HDMI-1 "2560x1440R" xrandr --output HDMI-1 --mode "2560x1440R" xrandr --output HDMI-1 --pos 0x0 xrandr --output eDP-1 --pos 2560x360 Starting recently, since I installed Ubuntu 18.04.2 (was using .1 before), even though the monitor isn't connected, that "space" is still there. I can move my mouse out of my laptop screen and it goes over where the monitor would be and gets lost. And screenshots (Print Screen) captures a large blank space as if the monitor were connected. As I said, this just started happening recently but I don't remember exactly what update caused it. All I know is before I installed 18.04.2, this didn't happen. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME DistUpgraded: Fresh install DistroCodename: bionic DistroRelease: Ubuntu 18.04 DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 620 [1028:0804] InstallationDate: Installed on 2019-02-16 (22 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: Dell Inc. Inspiron 5379 Package: xorg-server (not installed) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-16-generic root=UUID=a0583427-a9f8-49aa-89d2-bb8e77de9a58 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.18.0-16.17~18.04.1-generic 4.18.20 Tags: bionic ubuntu Uname: Linux 4.18.0-16-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/19/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.10.0 dmi.board.name: 05G60G dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.10.0:bd07/19/2018:svnDellInc.:pnInspiron5379:pvr:rvnDellInc.:rn05G60G:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 5379 dmi.product.sku: 0804 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.96-0~b~padoka0 version.libgl1-mesa-dri: libgl1-mesa-dri 18.3.3-1~b~padoka0 version.libgl1-mesa-glx: libgl1-mesa-glx 18.3.3-1~b~padoka0 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-server/+bug/1818829/+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 1818829] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1818829/+attachment/5245304/+files/ProcCpuinfoMinimal.txt -- 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/1818829 Title: Disconnected monitors act as present Status in xorg-server package in Ubuntu: Incomplete Bug description: I add a custom mode for my monitor using xrandr at boot. It looks like this: xrandr --newmode "2560x1440R" 241.50 2560 2608 2640 2720 1440 1443 1448 1481 +hsync -vsync xrandr --addmode HDMI-1 "2560x1440R" xrandr --output HDMI-1 --mode "2560x1440R" xrandr --output HDMI-1 --pos 0x0 xrandr --output eDP-1 --pos 2560x360 Starting recently, since I installed Ubuntu 18.04.2 (was using .1 before), even though the monitor isn't connected, that "space" is still there. I can move my mouse out of my laptop screen and it goes over where the monitor would be and gets lost. And screenshots (Print Screen) captures a large blank space as if the monitor were connected. As I said, this just started happening recently but I don't remember exactly what update caused it. All I know is before I installed 18.04.2, this didn't happen. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME DistUpgraded: Fresh install DistroCodename: bionic DistroRelease: Ubuntu 18.04 DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 620 [1028:0804] InstallationDate: Installed on 2019-02-16 (22 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: Dell Inc. Inspiron 5379 Package: xorg-server (not installed) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-16-generic root=UUID=a0583427-a9f8-49aa-89d2-bb8e77de9a58 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.18.0-16.17~18.04.1-generic 4.18.20 Tags: bionic ubuntu Uname: Linux 4.18.0-16-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/19/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.10.0 dmi.board.name: 05G60G dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.10.0:bd07/19/2018:svnDellInc.:pnInspiron5379:pvr:rvnDellInc.:rn05G60G:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 5379 dmi.product.sku: 0804 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.96-0~b~padoka0 version.libgl1-mesa-dri: libgl1-mesa-dri 18.3.3-1~b~padoka0 version.libgl1-mesa-glx: libgl1-mesa-glx 18.3.3-1~b~padoka0 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-server/+bug/1818829/+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 1818829] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1818829/+attachment/5245301/+files/Lsusb.txt -- 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/1818829 Title: Disconnected monitors act as present Status in xorg-server package in Ubuntu: Incomplete Bug description: I add a custom mode for my monitor using xrandr at boot. It looks like this: xrandr --newmode "2560x1440R" 241.50 2560 2608 2640 2720 1440 1443 1448 1481 +hsync -vsync xrandr --addmode HDMI-1 "2560x1440R" xrandr --output HDMI-1 --mode "2560x1440R" xrandr --output HDMI-1 --pos 0x0 xrandr --output eDP-1 --pos 2560x360 Starting recently, since I installed Ubuntu 18.04.2 (was using .1 before), even though the monitor isn't connected, that "space" is still there. I can move my mouse out of my laptop screen and it goes over where the monitor would be and gets lost. And screenshots (Print Screen) captures a large blank space as if the monitor were connected. As I said, this just started happening recently but I don't remember exactly what update caused it. All I know is before I installed 18.04.2, this didn't happen. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME DistUpgraded: Fresh install DistroCodename: bionic DistroRelease: Ubuntu 18.04 DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 620 [1028:0804] InstallationDate: Installed on 2019-02-16 (22 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: Dell Inc. Inspiron 5379 Package: xorg-server (not installed) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-16-generic root=UUID=a0583427-a9f8-49aa-89d2-bb8e77de9a58 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.18.0-16.17~18.04.1-generic 4.18.20 Tags: bionic ubuntu Uname: Linux 4.18.0-16-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/19/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.10.0 dmi.board.name: 05G60G dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.10.0:bd07/19/2018:svnDellInc.:pnInspiron5379:pvr:rvnDellInc.:rn05G60G:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 5379 dmi.product.sku: 0804 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.96-0~b~padoka0 version.libgl1-mesa-dri: libgl1-mesa-dri 18.3.3-1~b~padoka0 version.libgl1-mesa-glx: libgl1-mesa-glx 18.3.3-1~b~padoka0 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-server/+bug/1818829/+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 1818829] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1818829/+attachment/5245303/+files/ProcCpuinfo.txt -- 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/1818829 Title: Disconnected monitors act as present Status in xorg-server package in Ubuntu: Incomplete Bug description: I add a custom mode for my monitor using xrandr at boot. It looks like this: xrandr --newmode "2560x1440R" 241.50 2560 2608 2640 2720 1440 1443 1448 1481 +hsync -vsync xrandr --addmode HDMI-1 "2560x1440R" xrandr --output HDMI-1 --mode "2560x1440R" xrandr --output HDMI-1 --pos 0x0 xrandr --output eDP-1 --pos 2560x360 Starting recently, since I installed Ubuntu 18.04.2 (was using .1 before), even though the monitor isn't connected, that "space" is still there. I can move my mouse out of my laptop screen and it goes over where the monitor would be and gets lost. And screenshots (Print Screen) captures a large blank space as if the monitor were connected. As I said, this just started happening recently but I don't remember exactly what update caused it. All I know is before I installed 18.04.2, this didn't happen. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME DistUpgraded: Fresh install DistroCodename: bionic DistroRelease: Ubuntu 18.04 DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 620 [1028:0804] InstallationDate: Installed on 2019-02-16 (22 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: Dell Inc. Inspiron 5379 Package: xorg-server (not installed) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-16-generic root=UUID=a0583427-a9f8-49aa-89d2-bb8e77de9a58 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.18.0-16.17~18.04.1-generic 4.18.20 Tags: bionic ubuntu Uname: Linux 4.18.0-16-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/19/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.10.0 dmi.board.name: 05G60G dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.10.0:bd07/19/2018:svnDellInc.:pnInspiron5379:pvr:rvnDellInc.:rn05G60G:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 5379 dmi.product.sku: 0804 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.96-0~b~padoka0 version.libgl1-mesa-dri: libgl1-mesa-dri 18.3.3-1~b~padoka0 version.libgl1-mesa-glx: libgl1-mesa-glx 18.3.3-1~b~padoka0 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-server/+bug/1818829/+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 1818829] MonitorsUser.xml.txt
apport information ** Attachment added: "MonitorsUser.xml.txt" https://bugs.launchpad.net/bugs/1818829/+attachment/5245302/+files/MonitorsUser.xml.txt -- 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/1818829 Title: Disconnected monitors act as present Status in xorg-server package in Ubuntu: Incomplete Bug description: I add a custom mode for my monitor using xrandr at boot. It looks like this: xrandr --newmode "2560x1440R" 241.50 2560 2608 2640 2720 1440 1443 1448 1481 +hsync -vsync xrandr --addmode HDMI-1 "2560x1440R" xrandr --output HDMI-1 --mode "2560x1440R" xrandr --output HDMI-1 --pos 0x0 xrandr --output eDP-1 --pos 2560x360 Starting recently, since I installed Ubuntu 18.04.2 (was using .1 before), even though the monitor isn't connected, that "space" is still there. I can move my mouse out of my laptop screen and it goes over where the monitor would be and gets lost. And screenshots (Print Screen) captures a large blank space as if the monitor were connected. As I said, this just started happening recently but I don't remember exactly what update caused it. All I know is before I installed 18.04.2, this didn't happen. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME DistUpgraded: Fresh install DistroCodename: bionic DistroRelease: Ubuntu 18.04 DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 620 [1028:0804] InstallationDate: Installed on 2019-02-16 (22 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: Dell Inc. Inspiron 5379 Package: xorg-server (not installed) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-16-generic root=UUID=a0583427-a9f8-49aa-89d2-bb8e77de9a58 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.18.0-16.17~18.04.1-generic 4.18.20 Tags: bionic ubuntu Uname: Linux 4.18.0-16-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/19/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.10.0 dmi.board.name: 05G60G dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.10.0:bd07/19/2018:svnDellInc.:pnInspiron5379:pvr:rvnDellInc.:rn05G60G:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 5379 dmi.product.sku: 0804 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.96-0~b~padoka0 version.libgl1-mesa-dri: libgl1-mesa-dri 18.3.3-1~b~padoka0 version.libgl1-mesa-glx: libgl1-mesa-glx 18.3.3-1~b~padoka0 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-server/+bug/1818829/+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 1818829] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1818829/+attachment/5245300/+files/Lspci.txt -- 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/1818829 Title: Disconnected monitors act as present Status in xorg-server package in Ubuntu: Incomplete Bug description: I add a custom mode for my monitor using xrandr at boot. It looks like this: xrandr --newmode "2560x1440R" 241.50 2560 2608 2640 2720 1440 1443 1448 1481 +hsync -vsync xrandr --addmode HDMI-1 "2560x1440R" xrandr --output HDMI-1 --mode "2560x1440R" xrandr --output HDMI-1 --pos 0x0 xrandr --output eDP-1 --pos 2560x360 Starting recently, since I installed Ubuntu 18.04.2 (was using .1 before), even though the monitor isn't connected, that "space" is still there. I can move my mouse out of my laptop screen and it goes over where the monitor would be and gets lost. And screenshots (Print Screen) captures a large blank space as if the monitor were connected. As I said, this just started happening recently but I don't remember exactly what update caused it. All I know is before I installed 18.04.2, this didn't happen. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME DistUpgraded: Fresh install DistroCodename: bionic DistroRelease: Ubuntu 18.04 DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 620 [1028:0804] InstallationDate: Installed on 2019-02-16 (22 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: Dell Inc. Inspiron 5379 Package: xorg-server (not installed) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-16-generic root=UUID=a0583427-a9f8-49aa-89d2-bb8e77de9a58 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.18.0-16.17~18.04.1-generic 4.18.20 Tags: bionic ubuntu Uname: Linux 4.18.0-16-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/19/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.10.0 dmi.board.name: 05G60G dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.10.0:bd07/19/2018:svnDellInc.:pnInspiron5379:pvr:rvnDellInc.:rn05G60G:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 5379 dmi.product.sku: 0804 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.96-0~b~padoka0 version.libgl1-mesa-dri: libgl1-mesa-dri 18.3.3-1~b~padoka0 version.libgl1-mesa-glx: libgl1-mesa-glx 18.3.3-1~b~padoka0 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-server/+bug/1818829/+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 1818829] DpkgLog.txt
apport information ** Attachment added: "DpkgLog.txt" https://bugs.launchpad.net/bugs/1818829/+attachment/5245299/+files/DpkgLog.txt -- 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/1818829 Title: Disconnected monitors act as present Status in xorg-server package in Ubuntu: Incomplete Bug description: I add a custom mode for my monitor using xrandr at boot. It looks like this: xrandr --newmode "2560x1440R" 241.50 2560 2608 2640 2720 1440 1443 1448 1481 +hsync -vsync xrandr --addmode HDMI-1 "2560x1440R" xrandr --output HDMI-1 --mode "2560x1440R" xrandr --output HDMI-1 --pos 0x0 xrandr --output eDP-1 --pos 2560x360 Starting recently, since I installed Ubuntu 18.04.2 (was using .1 before), even though the monitor isn't connected, that "space" is still there. I can move my mouse out of my laptop screen and it goes over where the monitor would be and gets lost. And screenshots (Print Screen) captures a large blank space as if the monitor were connected. As I said, this just started happening recently but I don't remember exactly what update caused it. All I know is before I installed 18.04.2, this didn't happen. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME DistUpgraded: Fresh install DistroCodename: bionic DistroRelease: Ubuntu 18.04 DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 620 [1028:0804] InstallationDate: Installed on 2019-02-16 (22 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: Dell Inc. Inspiron 5379 Package: xorg-server (not installed) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-16-generic root=UUID=a0583427-a9f8-49aa-89d2-bb8e77de9a58 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.18.0-16.17~18.04.1-generic 4.18.20 Tags: bionic ubuntu Uname: Linux 4.18.0-16-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/19/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.10.0 dmi.board.name: 05G60G dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.10.0:bd07/19/2018:svnDellInc.:pnInspiron5379:pvr:rvnDellInc.:rn05G60G:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 5379 dmi.product.sku: 0804 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.96-0~b~padoka0 version.libgl1-mesa-dri: libgl1-mesa-dri 18.3.3-1~b~padoka0 version.libgl1-mesa-glx: libgl1-mesa-glx 18.3.3-1~b~padoka0 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-server/+bug/1818829/+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 1818972] Re: [regression] GLX is missing. gnome-shell visible latency is very high with Xorg 2:1.20.4-1ubuntu1
xorg-server (2:1.20.4-1ubuntu2) disco; urgency=medium
* Rebuild against fixed dri.pc. (LP: #1818972)
-- Timo Aaltonen Fri, 08 Mar 2019 10:31:56 +0200
** Changed in: xorg-server (Ubuntu)
Status: In Progress => Fix Committed
--
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/1818972
Title:
[regression] GLX is missing. gnome-shell visible latency is very high
with Xorg 2:1.20.4-1ubuntu1
Status in xorg-server package in Ubuntu:
Fix Committed
Bug description:
[Impact]
GLX is missing. gnome-shell visible latency is very high with Xorg
2:1.20.4-1ubuntu1. And reinstalling the previous version
(2:1.20.3-1ubuntu1) seems to fix it.
[Test Case]
$ glxinfo
Expected: Lots of information
Observed: An error
- or -
1. Log into a gnome-shell Xorg session ("Ubuntu").
2. Drag a window around in circles by its titlebar.
Expected: The mouse pointer to be somewhere near the titlebar
Observed: The mouse pointer is a long way away.
[Other Info]
Crucially, my patches to mutter's clutter-stage-cogl.c no longer have
any effect when this Xorg regression is present. So I can tell the
problem is related to some missing/broken X11 feature that is causing
the mutter master clock to fall back to its secondary vsync method (no
sync at all, just swapbuffers till they're all full, so typically
quad-buffering).
[Workarounds]
* Install Xorg 2:1.20.3-1ubuntu1 instead; or
* Use Wayland sessions only.
[Original description]
ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: xserver-xorg-core 2:1.20.4-1ubuntu1
ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0
Uname: Linux 5.0.0-7-generic x86_64
ApportVersion: 2.20.10-0ubuntu23
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'
Date: Thu Mar 7 16:24:50 2019
DistUpgraded: Fresh install
DistroCodename: disco
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
Intel Corporation HD Graphics 630 [8086:5912] (rev 04) (prog-if 00 [VGA
controller])
Subsystem: Lenovo HD Graphics 630 [17aa:3102]
InstallationDate: Installed on 2018-12-04 (93 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20181203)
MachineType: LENOVO 10M7CTO1WW
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-7-generic
root=UUID=052b7096-9b82-4712-b596-7629d5f6498c ro quiet splash vt.handoff=1
SourcePackage: xorg-server
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/06/2018
dmi.bios.vendor: LENOVO
dmi.bios.version: M16KT47A
dmi.board.name: 3102
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40709 WIN 3259627060530
dmi.chassis.type: 3
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias:
dmi:bvnLENOVO:bvrM16KT47A:bd02/06/2018:svnLENOVO:pn10M7CTO1WW:pvrThinkCentreM710s:rvnLENOVO:rn3102:rvrSDK0J40709WIN3259627060530:cvnLENOVO:ct3:cvrNone:
dmi.product.family: ThinkCentre M710s
dmi.product.name: 10M7CTO1WW
dmi.product.sku: LENOVO_MT_10M7_BU_Think_FM_ThinkCentre M710s
dmi.product.version: ThinkCentre M710s
dmi.sys.vendor: LENOVO
version.compiz: compiz 1:0.9.14.0+19.04.20190223.1-0ubuntu1
version.libdrm2: libdrm2 2.4.97-1
version.libgl1-mesa-dri: libgl1-mesa-dri 18.3.4-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 18.3.4-1ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.99+git20190207-1
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-server/+bug/1818972/+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 1003039] Re: No sound in headphones on imac 2011[workaround]
** Tags removed: precise ** Tags added: bionic xenial -- 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/1003039 Title: No sound in headphones on imac 2011[workaround] Status in alsa-driver package in Ubuntu: Confirmed Bug description: Using ubuntu 12.04 mac specific amd64 in a 2011 imac 21,5. Sound works on the built-in speakers if no headphone is connected. This is not a audio devide switch mute issue; the sound is activated, but no sound is coming from a regular headphone when it is connected. System is updated and no changes had been made to it. It also looks to be an ancient bug, which affect macbooks also for example. Let me know which information you need to fix that, and how to obtain that information. --- AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. ApportVersion: 2.0.1-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: lunarts1804 F pulseaudio /dev/snd/controlC0: lunarts1804 F pulseaudio Card0.Amixer.info: Card hw:0 'PCH'/'HDA Intel PCH at 0xa890 irq 49' Mixer name : 'Cirrus Logic CS4206' Components : 'HDA:10134206,106b0900,00100302' Controls : 24 Simple ctrls : 10 Card1.Amixer.info: Card hw:1 'Generic'/'HD-Audio Generic at 0xa884 irq 50' Mixer name : 'ATI R6xx HDMI' Components : 'HDA:1002aa01,00aa0100,00100200' Controls : 6 Simple ctrls : 1 Card1.Amixer.values: Simple mixer control 'IEC958',0 Capabilities: pswitch pswitch-joined penum Playback channels: Mono Mono: Playback [on] DistroRelease: Ubuntu 12.04 HibernationDevice: RESUME=UUID=9f77fbde-008f-4cdf-9e13-d1512cbd6abf InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64+mac (20120425.1) MachineType: Apple Inc. iMac12,1 NonfreeKernelModules: fglrx Package: linux (not installed) ProcEnviron: LANGUAGE=pt_BR:pt:en TERM=xterm PATH=(custom, no user) LANG=pt_BR.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-24-generic root=UUID=c816adec-8dcc-4344-a56e-2fdc23f632b7 ro quiet splash ProcVersionSignature: Ubuntu 3.2.0-24.38-generic 3.2.16 RelatedPackageVersions: linux-restricted-modules-3.2.0-24-generic N/A linux-backports-modules-3.2.0-24-generic N/A linux-firmware1.79 SourcePackage: linux StagingDrivers: mei Tags: precise staging precise staging Uname: Linux 3.2.0-24-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo dmi.bios.date: 01/24/12 dmi.bios.vendor: Apple Inc. dmi.bios.version: IM121.88Z.0047.B1F.1201241648 dmi.board.name: Mac-942B5BF58194151B dmi.board.vendor: Apple Inc. dmi.chassis.type: 13 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-942B5BF58194151B dmi.modalias: dmi:bvnAppleInc.:bvrIM121.88Z.0047.B1F.1201241648:bd01/24/12:svnAppleInc.:pniMac12,1:pvr1.0:rvnAppleInc.:rnMac-942B5BF58194151B:rvr:cvnAppleInc.:ct13:cvrMac-942B5BF58194151B: dmi.product.name: iMac12,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1003039/+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 1754933] Re: Headphones no audio output at all
*** This bug is a duplicate of bug 1003039 *** https://bugs.launchpad.net/bugs/1003039 ** This bug has been marked a duplicate of bug 1003039 No sound in headphones on imac 2011[workaround] -- 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/1754933 Title: Headphones no audio output at all Status in alsa-driver package in Ubuntu: Confirmed Bug description: Went to use headphones for the first time and got no audio output. I use Ubuntu on an iMac and the speakers work ok and the headphones work when in osx. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.13.0-36.40~16.04.1-generic 4.13.13 Uname: Linux 4.13.0-36-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0c: brent 2112 F...m pulseaudio /dev/snd/controlC0: brent 2112 F pulseaudio /dev/snd/controlC1: brent 2112 F pulseaudio CurrentDesktop: Unity Date: Sun Mar 11 18:20:29 2018 InstallationDate: Installed on 2018-03-07 (3 days ago) InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0c: brent 2112 F...m pulseaudio /dev/snd/controlC0: brent 2112 F pulseaudio /dev/snd/controlC1: brent 2112 F pulseaudio Symptom_Jack: Green Headphone Out, N/A Symptom_Type: No sound at all Title: [iMac12,1, Cirrus Logic CS4206, Green Headphone Out, N/A] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/08/17 dmi.bios.vendor: Apple Inc. dmi.bios.version: IM121.88Z.004D.B00.1708080012 dmi.board.name: Mac-942B5BF58194151B dmi.board.vendor: Apple Inc. dmi.chassis.type: 13 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-942B5BF58194151B dmi.modalias: dmi:bvnAppleInc.:bvrIM121.88Z.004D.B00.1708080012:bd08/08/17:svnAppleInc.:pniMac12,1:pvr1.0:rvnAppleInc.:rnMac-942B5BF58194151B:rvr:cvnAppleInc.:ct13:cvrMac-942B5BF58194151B: dmi.product.family: iMac dmi.product.name: iMac12,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1754933/+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 1819358] Re: [iMac12, 1, Cirrus Logic CS4206] Internal speakers work, only having trouble with the headphone output
*** This bug is a duplicate of bug 1003039 *** https://bugs.launchpad.net/bugs/1003039 ** Summary changed: - [iMac12,1, Cirrus Logic CS4206, Green Headphone Out, N/A] No sound at all + [iMac12,1, Cirrus Logic CS4206] Internal speakers work, only having trouble with the headphone output ** This bug has been marked a duplicate of bug 1003039 No sound in headphones on imac 2011[workaround] -- 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/1819358 Title: [iMac12,1, Cirrus Logic CS4206] Internal speakers work, only having trouble with the headphone output Status in alsa-driver package in Ubuntu: New Bug description: Internal speakers work, only having trouble with the headphone output, (I have had this problem in every distrobution I´ve tried) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18 Uname: Linux 4.15.0-46-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC2D0c: yoyo 1917 F...m pulseaudio /dev/snd/pcmC0D1p: yoyo 1917 F...m pulseaudio /dev/snd/controlC0: yoyo 1917 F pulseaudio /dev/snd/controlC1: yoyo 1917 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sun Mar 10 18:44:38 2019 EcryptfsInUse: Yes InstallationDate: Installed on 2019-03-10 (0 days ago) InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64+mac (20160803) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Green Headphone Out, N/A Symptom_Type: No sound at all Title: [iMac12,1, Cirrus Logic CS4206, Green Headphone Out, N/A] No sound at all UpgradeStatus: Upgraded to bionic on 2019-03-10 (0 days ago) dmi.bios.date: 09/25/2018 dmi.bios.vendor: Apple Inc. dmi.bios.version: 82.0.0.0.0 dmi.board.name: Mac-942B5BF58194151B dmi.board.vendor: Apple Inc. dmi.chassis.type: 13 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-942B5BF58194151B dmi.modalias: dmi:bvnAppleInc.:bvr82.0.0.0.0:bd09/25/2018:svnAppleInc.:pniMac12,1:pvr1.0:rvnAppleInc.:rnMac-942B5BF58194151B:rvr:cvnAppleInc.:ct13:cvrMac-942B5BF58194151B: dmi.product.family: iMac dmi.product.name: iMac12,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1819358/+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 1819359] Re: [iMac12, 1, Cirrus Logic CS4206, Green Headphone Out, N/A] No sound at all
*** This bug is a duplicate of bug 1003039 *** https://bugs.launchpad.net/bugs/1003039 ** This bug is no longer a duplicate of bug 1819358 [iMac12,1, Cirrus Logic CS4206] Internal speakers work, only having trouble with the headphone output ** This bug has been marked a duplicate of bug 1003039 No sound in headphones on imac 2011[workaround] -- 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/1819359 Title: [iMac12,1, Cirrus Logic CS4206, Green Headphone Out, N/A] No sound at all Status in alsa-driver package in Ubuntu: Incomplete Bug description: Internal speakers work, only having trouble with the headphone output, (I have had this problem in every distrobution I´ve tried) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18 Uname: Linux 4.15.0-46-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC2D0c: yoyo 1917 F...m pulseaudio /dev/snd/pcmC0D1p: yoyo 1917 F...m pulseaudio /dev/snd/controlC0: yoyo 1917 F pulseaudio /dev/snd/controlC1: yoyo 1917 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sun Mar 10 18:44:38 2019 EcryptfsInUse: Yes InstallationDate: Installed on 2019-03-10 (0 days ago) InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64+mac (20160803) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Green Headphone Out, N/A Symptom_Type: No sound at all Title: [iMac12,1, Cirrus Logic CS4206, Green Headphone Out, N/A] No sound at all UpgradeStatus: Upgraded to bionic on 2019-03-10 (0 days ago) dmi.bios.date: 09/25/2018 dmi.bios.vendor: Apple Inc. dmi.bios.version: 82.0.0.0.0 dmi.board.name: Mac-942B5BF58194151B dmi.board.vendor: Apple Inc. dmi.chassis.type: 13 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-942B5BF58194151B dmi.modalias: dmi:bvnAppleInc.:bvr82.0.0.0.0:bd09/25/2018:svnAppleInc.:pniMac12,1:pvr1.0:rvnAppleInc.:rnMac-942B5BF58194151B:rvr:cvnAppleInc.:ct13:cvrMac-942B5BF58194151B: dmi.product.family: iMac dmi.product.name: iMac12,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1819359/+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 1819264] Re: Graphis problem
You already have the right graphics driver built-in and working. What problem are you trying to solve? ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Incomplete -- 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/1819264 Title: Graphis problem Status in Ubuntu: Incomplete Bug description: How can i install graphis in dell inspiron 3442. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.18.0-16.17~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-16-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Mar 9 18:33:36 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 0b) (prog-if 00 [VGA controller]) Subsystem: Dell Haswell-ULT Integrated Graphics Controller [1028:0651] InstallationDate: Installed on 2019-03-08 (0 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: Dell Inc. Inspiron 3442 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.18.0-16-generic root=UUID=950331ed-5458-421a-be4b-05d38ca12e30 ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/23/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: A14 dmi.board.name: 0486K1 dmi.board.vendor: Dell Inc. dmi.board.version: A14 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA14:bd05/23/2018:svnDellInc.:pnInspiron3442:pvrNotSpecified:rvnDellInc.:rn0486K1:rvrA14:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Inspiron 3442 dmi.product.sku: 0651 dmi.product.version: Not Specified 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.2-0ubuntu1~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1~18.04.2 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/+bug/1819264/+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 1819277] Re: I see stripes plomas in full screen mode
Fixed upstream in Mesa: https://gitlab.freedesktop.org/mesa/mesa/merge_requests/252 ** Changed in: mesa (Ubuntu) Importance: Undecided => Medium ** Changed in: mesa (Ubuntu) Status: Confirmed => Triaged ** Description changed: - https://gitlab.gnome.org/GNOME/totem/issues/307 + https://gitlab.freedesktop.org/mesa/mesa/merge_requests/252 --- When I open a movie in totem, it looks like a window. But then I enlarge it to full screen. It is seen in the lower part, a strip of lead. Attached screenshot image. The problem occurs with wayland, in Xorg it looks good. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: totem 3.32.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0 Uname: Linux 5.0.0-7-generic x86_64 ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Mar 9 12:12:52 2019 InstallationDate: Installed on 2018-12-02 (96 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: totem UpgradeStatus: Upgraded to disco on 2018-12-02 (96 days ago) ** Description changed: - https://gitlab.freedesktop.org/mesa/mesa/merge_requests/252 - - --- - When I open a movie in totem, it looks like a window. But then I enlarge it to full screen. It is seen in the lower part, a strip of lead. Attached screenshot image. The problem occurs with wayland, in Xorg it looks good. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: totem 3.32.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0 Uname: Linux 5.0.0-7-generic x86_64 ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Mar 9 12:12:52 2019 InstallationDate: Installed on 2018-12-02 (96 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: totem UpgradeStatus: Upgraded to disco on 2018-12-02 (96 days ago) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1819277 Title: I see stripes plomas in full screen mode Status in mesa package in Ubuntu: Triaged Status in totem package in Ubuntu: Invalid Bug description: When I open a movie in totem, it looks like a window. But then I enlarge it to full screen. It is seen in the lower part, a strip of lead. Attached screenshot image. The problem occurs with wayland, in Xorg it looks good. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: totem 3.32.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0 Uname: Linux 5.0.0-7-generic x86_64 ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Mar 9 12:12:52 2019 InstallationDate: Installed on 2018-12-02 (96 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: totem UpgradeStatus: Upgraded to disco on 2018-12-02 (96 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1819277/+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 1819193] Re: Document search does not work
Maybe related to bug 1713931?
--
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/1819193
Title:
Document search does not work
Status in gnome-shell package in Ubuntu:
New
Bug description:
1. Description: Ubuntu 18.04.2 LTS
2. 3.28.3-0ubuntu0.18.04.4
3. I expect to be able to search document by content from the gnome shell
("Type to search..."). The option is enabled from settings.
4. Nothing happens. No documents are retrieved.
I get the following error message in logs repeatedly:
"Wrong number of result metas returned by search provider
org.gnome.Documents.desktop: expected 5 but got 0"
gnome-documents also gives this:
"JS ERROR: GLib.Error g-invoke-error-quark: Could not locate
gd_filename_strip_extension: (null)"
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1819193/+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 1819383] Re: VEGA 64 config for 1680x1050 is incorrect
Actually, the Vega 64 uses the radeon driver $ apt-cache policy xserver-xorg-video-radeon xserver-xorg-video-radeon: Installed: 1:18.0.1-1 Candidate: 1:18.0.1-1 Version table: *** 1:18.0.1-1 500 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status -- 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/1819383 Title: VEGA 64 config for 1680x1050 is incorrect Status in xserver-xorg-video-amdgpu package in Ubuntu: Confirmed Bug description: I have two AMD GPU cards in my system connected to an identical pair of older SAMSUNG monitors with native resolution of 1680x1050. $ lspci -d ::300 0a:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Vega 10 XT [Radeon RX Vega 64] (rev c1) 42:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] RV770 [Radeon HD 4850] The RV770 has successfully been connected to these two monitors for many years. Recently upgraded the motherboard and added the Vega 64 video card. Connecting DisplayPort from the Vega 64 to one monitor and the RV770 to the other, The Vega 64 monitor display is corrupted. See attached picture. I tried all the other supported modes for the monitor and the others all work fine (1024x768, 1280x1024, etc.) Although, it is perhaps interesting that 1680x1050 is the only 1.6:1 aspect ratio. The majority are 4:3 with 1280x1024 (5:4) and 720x400 (9:5) the exceptions. And all the other modes seem to display in a 4:3 subset of the pixels on the screen. I'll upload the /var/log/Xorg.0.log next. Other info: $ lsb_release -rd Description: Linux Mint 19.1 Tessa Release: 19.1 $ apt-cache policy xserver-xorg-video-amdgpu xserver-xorg-video-amdgpu: Installed: 18.0.1-1 Candidate: 18.0.1-1 Version table: *** 18.0.1-1 500 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status EXPECTATION: Correct display output ACTUAL RESULT: "Torn" display. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC1D0p: philip 2211 F...m pulseaudio /dev/snd/controlC1: philip 2211 F pulseaudio /dev/snd/controlC0: philip 2211 F pulseaudio /dev/snd/controlC2: philip 2211 F pulseaudio CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 19.1 InstallationDate: Installed on 2019-03-10 (0 days ago) InstallationMedia: Linux Mint 19.1 "Tessa" - Release amd64 20181217 IwConfig: lono wireless extensions. enp4s0no wireless extensions. MachineType: Gigabyte Technology Co., Ltd. X399 AORUS PRO Package: linux (not installed) ProcFB: 0 radeondrmfb 1 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-46-generic root=UUID=14bde5f7-3295-4e41-bc36-8d22c00349f9 ro rootflags=subvol=@ quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-46-generic N/A linux-backports-modules-4.15.0-46-generic N/A linux-firmware 1.173.3 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: tessa Uname: Linux 4.15.0-46-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/01/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F1 dmi.board.asset.tag: Default string dmi.board.name: X399 AORUS PRO-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF1:bd10/01/2018:svnGigabyteTechnologyCo.,Ltd.:pnX399AORUSPRO:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnX399AORUSPRO-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: X399 AORUS PRO dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-amdgpu/+bug/1819383/+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 1819383] Re: VEGA 64 config for 1680x1050 is incorrect
No. I was right the first time ** Package changed: xserver-xorg-video-radeonhd (Ubuntu) => xserver- xorg-video-amdgpu (Ubuntu) -- 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/1819383 Title: VEGA 64 config for 1680x1050 is incorrect Status in xserver-xorg-video-amdgpu package in Ubuntu: Confirmed Bug description: I have two AMD GPU cards in my system connected to an identical pair of older SAMSUNG monitors with native resolution of 1680x1050. $ lspci -d ::300 0a:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Vega 10 XT [Radeon RX Vega 64] (rev c1) 42:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] RV770 [Radeon HD 4850] The RV770 has successfully been connected to these two monitors for many years. Recently upgraded the motherboard and added the Vega 64 video card. Connecting DisplayPort from the Vega 64 to one monitor and the RV770 to the other, The Vega 64 monitor display is corrupted. See attached picture. I tried all the other supported modes for the monitor and the others all work fine (1024x768, 1280x1024, etc.) Although, it is perhaps interesting that 1680x1050 is the only 1.6:1 aspect ratio. The majority are 4:3 with 1280x1024 (5:4) and 720x400 (9:5) the exceptions. And all the other modes seem to display in a 4:3 subset of the pixels on the screen. I'll upload the /var/log/Xorg.0.log next. Other info: $ lsb_release -rd Description: Linux Mint 19.1 Tessa Release: 19.1 $ apt-cache policy xserver-xorg-video-amdgpu xserver-xorg-video-amdgpu: Installed: 18.0.1-1 Candidate: 18.0.1-1 Version table: *** 18.0.1-1 500 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status EXPECTATION: Correct display output ACTUAL RESULT: "Torn" display. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC1D0p: philip 2211 F...m pulseaudio /dev/snd/controlC1: philip 2211 F pulseaudio /dev/snd/controlC0: philip 2211 F pulseaudio /dev/snd/controlC2: philip 2211 F pulseaudio CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 19.1 InstallationDate: Installed on 2019-03-10 (0 days ago) InstallationMedia: Linux Mint 19.1 "Tessa" - Release amd64 20181217 IwConfig: lono wireless extensions. enp4s0no wireless extensions. MachineType: Gigabyte Technology Co., Ltd. X399 AORUS PRO Package: linux (not installed) ProcFB: 0 radeondrmfb 1 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-46-generic root=UUID=14bde5f7-3295-4e41-bc36-8d22c00349f9 ro rootflags=subvol=@ quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-46-generic N/A linux-backports-modules-4.15.0-46-generic N/A linux-firmware 1.173.3 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: tessa Uname: Linux 4.15.0-46-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/01/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F1 dmi.board.asset.tag: Default string dmi.board.name: X399 AORUS PRO-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF1:bd10/01/2018:svnGigabyteTechnologyCo.,Ltd.:pnX399AORUSPRO:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnX399AORUSPRO-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: X399 AORUS PRO dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-amdgpu/+bug/1819383/+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 1819383] Re: VEGA 64 config for 1680x1050 is incorrect
$ apt-cache policy xserver-xorg-video-radeon xserver-xorg-video-radeon: Installed: 1:18.0.1-1 Candidate: 1:18.0.1-1 Version table: *** 1:18.0.1-1 500 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status ** Package changed: xserver-xorg-video-amdgpu (Ubuntu) => xserver-xorg-video-radeonhd (Ubuntu) -- 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/1819383 Title: VEGA 64 config for 1680x1050 is incorrect Status in xserver-xorg-video-amdgpu package in Ubuntu: Confirmed Bug description: I have two AMD GPU cards in my system connected to an identical pair of older SAMSUNG monitors with native resolution of 1680x1050. $ lspci -d ::300 0a:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Vega 10 XT [Radeon RX Vega 64] (rev c1) 42:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] RV770 [Radeon HD 4850] The RV770 has successfully been connected to these two monitors for many years. Recently upgraded the motherboard and added the Vega 64 video card. Connecting DisplayPort from the Vega 64 to one monitor and the RV770 to the other, The Vega 64 monitor display is corrupted. See attached picture. I tried all the other supported modes for the monitor and the others all work fine (1024x768, 1280x1024, etc.) Although, it is perhaps interesting that 1680x1050 is the only 1.6:1 aspect ratio. The majority are 4:3 with 1280x1024 (5:4) and 720x400 (9:5) the exceptions. And all the other modes seem to display in a 4:3 subset of the pixels on the screen. I'll upload the /var/log/Xorg.0.log next. Other info: $ lsb_release -rd Description: Linux Mint 19.1 Tessa Release: 19.1 $ apt-cache policy xserver-xorg-video-amdgpu xserver-xorg-video-amdgpu: Installed: 18.0.1-1 Candidate: 18.0.1-1 Version table: *** 18.0.1-1 500 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status EXPECTATION: Correct display output ACTUAL RESULT: "Torn" display. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC1D0p: philip 2211 F...m pulseaudio /dev/snd/controlC1: philip 2211 F pulseaudio /dev/snd/controlC0: philip 2211 F pulseaudio /dev/snd/controlC2: philip 2211 F pulseaudio CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 19.1 InstallationDate: Installed on 2019-03-10 (0 days ago) InstallationMedia: Linux Mint 19.1 "Tessa" - Release amd64 20181217 IwConfig: lono wireless extensions. enp4s0no wireless extensions. MachineType: Gigabyte Technology Co., Ltd. X399 AORUS PRO Package: linux (not installed) ProcFB: 0 radeondrmfb 1 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-46-generic root=UUID=14bde5f7-3295-4e41-bc36-8d22c00349f9 ro rootflags=subvol=@ quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-46-generic N/A linux-backports-modules-4.15.0-46-generic N/A linux-firmware 1.173.3 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: tessa Uname: Linux 4.15.0-46-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/01/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F1 dmi.board.asset.tag: Default string dmi.board.name: X399 AORUS PRO-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF1:bd10/01/2018:svnGigabyteTechnologyCo.,Ltd.:pnX399AORUSPRO:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnX399AORUSPRO-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: X399 AORUS PRO dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-amdgpu/+bug/1819383/+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 1819126] Re: gnome-shell crashed with SIGABRT [St:ERROR:../src/st/st-image-content.c:155:st_image_content_get_preferred_size: assertion failed (priv->width > -1): (-1 > -1)]
** Tags added: fixed-upstream ** Changed in: gnome-shell (Ubuntu) Status: Confirmed => Triaged -- 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/1819126 Title: gnome-shell crashed with SIGABRT [St:ERROR:../src/st/st-image- content.c:155:st_image_content_get_preferred_size: assertion failed (priv->width > -1): (-1 > -1)] Status in gnome-shell package in Ubuntu: Triaged Bug description: https://gitlab.gnome.org/GNOME/gnome-shell/issues/1027 https://errors.ubuntu.com/problem/40bb6815b23393e7dfa95f5895de4b0603ac431b --- The crash happened when a new application or system crash report window from update-notifier showed up. Reproducer: 1. sleep 1000 on one terminal 2. kill -SIGSEGV $(pidof sleep) -> wait for update-notifier to try showing up apport (application crash) or update-notifier (system crash) windows. This can take up to 180s. - ProblemType: Crash DistroRelease: Ubuntu 19.04 Package: gnome-shell 3.31.92-1ubuntu1 ProcVersionSignature: Ubuntu 4.19.0-13.14-generic 4.19.20 Uname: Linux 4.19.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Mar 8 09:32:41 2019 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2018-05-24 (287 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcCmdline: /usr/bin/gnome-shell Signal: 6 SourcePackage: gnome-shell StacktraceTop: () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 g_assertion_message_cmpnum () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 () at /usr/lib/gnome-shell/libst-1.0.so clutter_actor_get_preferred_size () at /usr/lib/x86_64-linux-gnu/mutter-4/libmutter-clutter-4.so.0 clutter_actor_get_transformed_size () at /usr/lib/x86_64-linux-gnu/mutter-4/libmutter-clutter-4.so.0 Title: gnome-shell crashed with SIGABRT UpgradeStatus: Upgraded to disco on 2019-01-08 (58 days ago) UserGroups: adm cdrom dip docker kvm libvirt lpadmin plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1819126/+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 1817338] Re: HDMI sound output not selectable in 19.04 (but works in 18.10)
I had the same issue a few weeks ago, now however with 3.31.92 (on Disco) I do get the configuration dropdown when selecting my HDMI Audio device. It came up blank initially, but appears to have saved the correct setting since. -- 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/1817338 Title: HDMI sound output not selectable in 19.04 (but works in 18.10) Status in gnome-control-center package in Ubuntu: New Status in pulseaudio package in Ubuntu: Invalid Bug description: In 19.04, HDMI sound stopped working after some upgrade. The sink is somehow availalbe, but cannot be selected. In gnome-control-center, HDMI output device is listed, but if I choose it, no configuration list appears (see screen capture attached). aplay -l gives me: ~$ aplay -l Liste des Périphériques Matériels PLAYBACK carte 0: PCH [HDA Intel PCH], périphérique 0: ALC269VC Analog [ALC269VC Analog] Sous-périphériques: 0/1 Sous-périphérique #0: subdevice #0 carte 0: PCH [HDA Intel PCH], périphérique 3: HDMI 0 [HDMI 0] Sous-périphériques: 1/1 Sous-périphérique #0: subdevice #0 carte 0: PCH [HDA Intel PCH], périphérique 7: HDMI 1 [HDMI 1] Sous-périphériques: 1/1 Sous-périphérique #0: subdevice #0 carte 0: PCH [HDA Intel PCH], périphérique 8: HDMI 2 [HDMI 2] Sous-périphériques: 1/1 Sous-périphérique #0: subdevice #0 pavucontrol shows HDMI as unplugged. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: pulseaudio 1:12.2-2ubuntu1 ProcVersionSignature: Ubuntu 4.19.0-13.14-generic 4.19.20 Uname: Linux 4.19.0-13-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.10-0ubuntu21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: franck 5998 F pulseaudio /dev/snd/pcmC1D0c: franck 5998 F...m pulseaudio /dev/snd/controlC0: franck 5998 F pulseaudio CurrentDesktop: GNOME Date: Fri Feb 22 16:16:56 2019 EcryptfsInUse: Yes ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/27/2017 dmi.bios.vendor: LENOVO dmi.bios.version: G7ETA9WW (2.69 ) dmi.board.asset.tag: Not Available dmi.board.name: 2353CTO 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: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG7ETA9WW(2.69):bd09/27/2017:svnLENOVO:pn2353CTO:pvrThinkPadT430s:rvnLENOVO:rn2353CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad T430s dmi.product.name: 2353CTO dmi.product.sku: LENOVO_MT_2353 dmi.product.version: ThinkPad T430s dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1817338/+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 1819383] [NEW] VEGA 64 config for 1680x1050 is incorrect
You have been subscribed to a public bug: I have two AMD GPU cards in my system connected to an identical pair of older SAMSUNG monitors with native resolution of 1680x1050. $ lspci -d ::300 0a:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Vega 10 XT [Radeon RX Vega 64] (rev c1) 42:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] RV770 [Radeon HD 4850] The RV770 has successfully been connected to these two monitors for many years. Recently upgraded the motherboard and added the Vega 64 video card. Connecting DisplayPort from the Vega 64 to one monitor and the RV770 to the other, The Vega 64 monitor display is corrupted. See attached picture. I tried all the other supported modes for the monitor and the others all work fine (1024x768, 1280x1024, etc.) Although, it is perhaps interesting that 1680x1050 is the only 1.6:1 aspect ratio. The majority are 4:3 with 1280x1024 (5:4) and 720x400 (9:5) the exceptions. And all the other modes seem to display in a 4:3 subset of the pixels on the screen. I'll upload the /var/log/Xorg.0.log next. Other info: $ lsb_release -rd Description:Linux Mint 19.1 Tessa Release:19.1 $ apt-cache policy xserver-xorg-video-amdgpu xserver-xorg-video-amdgpu: Installed: 18.0.1-1 Candidate: 18.0.1-1 Version table: *** 18.0.1-1 500 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status EXPECTATION: Correct display output ACTUAL RESULT: "Torn" display. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC1D0p: philip 2211 F...m pulseaudio /dev/snd/controlC1: philip 2211 F pulseaudio /dev/snd/controlC0: philip 2211 F pulseaudio /dev/snd/controlC2: philip 2211 F pulseaudio CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 19.1 InstallationDate: Installed on 2019-03-10 (0 days ago) InstallationMedia: Linux Mint 19.1 "Tessa" - Release amd64 20181217 IwConfig: lono wireless extensions. enp4s0no wireless extensions. MachineType: Gigabyte Technology Co., Ltd. X399 AORUS PRO Package: linux (not installed) ProcFB: 0 radeondrmfb 1 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-46-generic root=UUID=14bde5f7-3295-4e41-bc36-8d22c00349f9 ro rootflags=subvol=@ quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-46-generic N/A linux-backports-modules-4.15.0-46-generic N/A linux-firmware 1.173.3 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: tessa Uname: Linux 4.15.0-46-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/01/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F1 dmi.board.asset.tag: Default string dmi.board.name: X399 AORUS PRO-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF1:bd10/01/2018:svnGigabyteTechnologyCo.,Ltd.:pnX399AORUSPRO:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnX399AORUSPRO-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: X399 AORUS PRO dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. ** Affects: xserver-xorg-video-amdgpu (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: apport-collected tessa -- VEGA 64 config for 1680x1050 is incorrect https://bugs.launchpad.net/bugs/1819383 You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-amdgpu 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 1812527] Re: [bionic][regression] gnome-shell crashes with SIGSEGV in meta_window_actor_is_destroyed(self=NULL) called from _switchWorkspaceDone() [windowManager.js:1787]
** Information type changed from Public to Public Security ** Information type changed from Public Security to Private Security -- 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/1812527 Title: [bionic][regression] gnome-shell crashes with SIGSEGV in meta_window_actor_is_destroyed(self=NULL) called from _switchWorkspaceDone() [windowManager.js:1787] Status in gjs package in Ubuntu: Confirmed Status in gnome-shell package in Ubuntu: Confirmed Status in gjs source package in Bionic: Confirmed Status in gnome-shell source package in Bionic: Confirmed Bug description: https://errors.ubuntu.com/problem/cb400a6f83ed57af8bb117cf84d5ed6d7e2ffcee https://gitlab.gnome.org/GNOME/gnome-shell/issues/927 Switching workspace with the Android Emulator running will blink the screen as if gnome restarted, if I switch workspace one more time, it will completely crash and I will need to log in again. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.3-0ubuntu0.18.04.4 Uname: Linux 4.20.3-acso x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Jan 19 20:05:34 2019 DisplayManager: gdm3 GsettingsChanges: b'org.gnome.shell' b'favorite-apps' redacted by apport b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2019-01-15 (4 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/1812527/+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 1818862] Re: Totem player hangs when seeking video
Can you clarify what "did not do anything" means? Because if you have uninstalled package i965-va-driver then it should be impossible to encounter the crash mentioned above. If not doing anything means that totem still hangs then the cause of the hang is likely something different again. P.S. Please report the crash (assertion failure) at: https://github.com/intel/intel-vaapi-driver/issues ** Changed in: intel-vaapi-driver (Ubuntu) Status: New => Incomplete ** Changed in: totem (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/1818862 Title: Totem player hangs when seeking video Status in intel-vaapi-driver package in Ubuntu: Incomplete Status in totem package in Ubuntu: Incomplete Bug description: Totem player hangs as soon as I click on the bar at the bottom to seek to a specific time in an mp4 video. Video in question can be found here: https://cdn.media.ccc.de/congress/2018/h264-hd/35c3-9370-eng-deu- Hacking_how_we_see_hd.mp4 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: totem 3.26.0-0ubuntu6.2 ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18 Uname: Linux 4.15.0-45-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Mar 6 16:10:11 2019 EcryptfsInUse: Yes InstallationDate: Installed on 2017-12-08 (453 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) SourcePackage: totem UpgradeStatus: Upgraded to bionic on 2018-05-02 (308 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-vaapi-driver/+bug/1818862/+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 1818944] Re: unable to remove or add apps
No problem. Sometimes the installed packages can get into a tangle during updates if there's a problem with one of them. It sounds like that is fixed. ** Changed in: gnome-software (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1818944 Title: unable to remove or add apps Status in gnome-software package in Ubuntu: Invalid Bug description: unable to remove or add apps. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18 Uname: Linux 4.15.0-45-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CompositorRunning: None Date: Wed Mar 6 19:04:29 2019 DistUpgraded: 2018-09-05 18:27:31,982 DEBUG icon theme changed, re-reading DistroCodename: bionic DistroVariant: ubuntu DpkgLog: ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation GT218 [GeForce 8400 GS Rev. 3] [10de:10c3] (rev a2) (prog-if 00 [VGA controller]) Subsystem: eVga.com. Corp. GT218 [GeForce 8400 GS Rev. 3] [3842:1302] InstallationDate: Installed on 2017-08-04 (579 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: To be filled by O.E.M. To be filled by O.E.M. ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-45-generic root=UUID=50cfe61f-c8b2-425d-8e49-ebb4f48f5173 ro quiet splash SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2018-09-06 (182 days ago) dmi.bios.date: 03/24/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2701 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: M5A97 LE R2.0 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2701:bd03/24/2016:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnM5A97LER2.0:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: To be filled by O.E.M. 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.2-0ubuntu1~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 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 xserver.bootTime: Wed Sep 5 16:21:29 2018 xserver.configfile: default xserver.errors: Failed to load module "nvidia" (module does not exist, 0) Failed to load module "nvidia" (module does not exist, 0) Logitech Rechargeable Touchpad T650: Read error 19 Logitech Rechargeable Touchpad T650: Read error 19 xserver.logfile: /var/log/Xorg.0.log xserver.outputs: Output DVI-I-1 HDMI-1 VGA-1 xserver.version: 2:1.18.4-0ubuntu0.8 xserver.video_driver: nouveau To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1818944/+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 1818829] Re: Disconnected monitors act as present
OK. Please run this command to send us more information about the system: apport-collect 1818829 ** Changed in: xorg-server (Ubuntu) Status: New => Incomplete -- 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/1818829 Title: Disconnected monitors act as present Status in xorg-server package in Ubuntu: Incomplete Bug description: I add a custom mode for my monitor using xrandr at boot. It looks like this: xrandr --newmode "2560x1440R" 241.50 2560 2608 2640 2720 1440 1443 1448 1481 +hsync -vsync xrandr --addmode HDMI-1 "2560x1440R" xrandr --output HDMI-1 --mode "2560x1440R" xrandr --output HDMI-1 --pos 0x0 xrandr --output eDP-1 --pos 2560x360 Starting recently, since I installed Ubuntu 18.04.2 (was using .1 before), even though the monitor isn't connected, that "space" is still there. I can move my mouse out of my laptop screen and it goes over where the monitor would be and gets lost. And screenshots (Print Screen) captures a large blank space as if the monitor were connected. As I said, this just started happening recently but I don't remember exactly what update caused it. All I know is before I installed 18.04.2, this didn't happen. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1818829/+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 1818802] Re: [ZenBook UX433FN_UX433FN] Audio only works when the laptop is plugged in or the battery % is above 20 - 40%
I wonder if 'tlp' or similar is at play... Can you please run this command: dpkg -l > allpackages.txt and then send us the resulting file 'allpackages.txt'? ** Summary changed: - [ZenBook UX433FN_UX433FN, Realtek ALC294, Speaker, Internal] fails after a while + [ZenBook UX433FN_UX433FN] Audio only works when the laptop is plugged in or the battery % is above 20 - 40% ** Package changed: alsa-driver (Ubuntu) => linux (Ubuntu) -- 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/1818802 Title: [ZenBook UX433FN_UX433FN] Audio only works when the laptop is plugged in or the battery % is above 20 - 40% Status in linux package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: Incomplete Bug description: Audio dies after few seconds, returns after few minutes and dies again filip@ux433:~$ lsb_release -rd Description: Ubuntu 18.10 Release: 18.10 ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 Uname: Linux 4.20.14-042014-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: filip 8566 F pulseaudio /dev/snd/pcmC0D0p: filip 8566 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed Mar 6 10:11:01 2019 InstallationDate: Installed on 2019-01-05 (59 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Speaker, Internal Symptom_PulseAudioLog: mar 06 10:04:08 ux433 dbus-daemon[3008]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' requested by ':1.37' (uid=121 pid=6142 comm="/usr/bin/pulseaudio --daemonize=no ") Symptom_Type: Sound works for a while, then breaks Title: [ZenBook UX433FN_UX433FN, Realtek ALC294, Speaker, Internal] fails after a while UpgradeStatus: Upgraded to cosmic on 2019-01-28 (36 days ago) dmi.bios.date: 11/21/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX433FN.301 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX433FN 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.:bvrUX433FN.301:bd11/21/2018:svnASUSTeKCOMPUTERINC.:pnZenBookUX433FN_UX433FN:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX433FN:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook dmi.product.name: ZenBook UX433FN_UX433FN dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818802/+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 1819383] Re: VEGA 64 config for 1680x1050 is incorrect
I don't think this is a kernel issue. More likely Xorg ** Package changed: linux (Ubuntu) => xserver-xorg-video-amdgpu (Ubuntu) -- 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/1819383 Title: VEGA 64 config for 1680x1050 is incorrect Status in xserver-xorg-video-amdgpu package in Ubuntu: Confirmed Bug description: I have two AMD GPU cards in my system connected to an identical pair of older SAMSUNG monitors with native resolution of 1680x1050. $ lspci -d ::300 0a:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Vega 10 XT [Radeon RX Vega 64] (rev c1) 42:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] RV770 [Radeon HD 4850] The RV770 has successfully been connected to these two monitors for many years. Recently upgraded the motherboard and added the Vega 64 video card. Connecting DisplayPort from the Vega 64 to one monitor and the RV770 to the other, The Vega 64 monitor display is corrupted. See attached picture. I tried all the other supported modes for the monitor and the others all work fine (1024x768, 1280x1024, etc.) Although, it is perhaps interesting that 1680x1050 is the only 1.6:1 aspect ratio. The majority are 4:3 with 1280x1024 (5:4) and 720x400 (9:5) the exceptions. And all the other modes seem to display in a 4:3 subset of the pixels on the screen. I'll upload the /var/log/Xorg.0.log next. Other info: $ lsb_release -rd Description: Linux Mint 19.1 Tessa Release: 19.1 $ apt-cache policy xserver-xorg-video-amdgpu xserver-xorg-video-amdgpu: Installed: 18.0.1-1 Candidate: 18.0.1-1 Version table: *** 18.0.1-1 500 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status EXPECTATION: Correct display output ACTUAL RESULT: "Torn" display. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC1D0p: philip 2211 F...m pulseaudio /dev/snd/controlC1: philip 2211 F pulseaudio /dev/snd/controlC0: philip 2211 F pulseaudio /dev/snd/controlC2: philip 2211 F pulseaudio CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 19.1 InstallationDate: Installed on 2019-03-10 (0 days ago) InstallationMedia: Linux Mint 19.1 "Tessa" - Release amd64 20181217 IwConfig: lono wireless extensions. enp4s0no wireless extensions. MachineType: Gigabyte Technology Co., Ltd. X399 AORUS PRO Package: linux (not installed) ProcFB: 0 radeondrmfb 1 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-46-generic root=UUID=14bde5f7-3295-4e41-bc36-8d22c00349f9 ro rootflags=subvol=@ quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-46-generic N/A linux-backports-modules-4.15.0-46-generic N/A linux-firmware 1.173.3 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: tessa Uname: Linux 4.15.0-46-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/01/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F1 dmi.board.asset.tag: Default string dmi.board.name: X399 AORUS PRO-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF1:bd10/01/2018:svnGigabyteTechnologyCo.,Ltd.:pnX399AORUSPRO:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnX399AORUSPRO-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: X399 AORUS PRO dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-amdgpu/+bug/1819383/+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 1817338] Re: HDMI sound output not selectable in 19.04 (but works in 18.10)
** Changed in: gnome-control-center (Ubuntu) Assignee: (unassigned) => Robert Ancell (robert-ancell) ** Changed in: gnome-control-center (Ubuntu) Importance: Undecided => High -- 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/1817338 Title: HDMI sound output not selectable in 19.04 (but works in 18.10) Status in gnome-control-center package in Ubuntu: New Status in pulseaudio package in Ubuntu: Invalid Bug description: In 19.04, HDMI sound stopped working after some upgrade. The sink is somehow availalbe, but cannot be selected. In gnome-control-center, HDMI output device is listed, but if I choose it, no configuration list appears (see screen capture attached). aplay -l gives me: ~$ aplay -l Liste des Périphériques Matériels PLAYBACK carte 0: PCH [HDA Intel PCH], périphérique 0: ALC269VC Analog [ALC269VC Analog] Sous-périphériques: 0/1 Sous-périphérique #0: subdevice #0 carte 0: PCH [HDA Intel PCH], périphérique 3: HDMI 0 [HDMI 0] Sous-périphériques: 1/1 Sous-périphérique #0: subdevice #0 carte 0: PCH [HDA Intel PCH], périphérique 7: HDMI 1 [HDMI 1] Sous-périphériques: 1/1 Sous-périphérique #0: subdevice #0 carte 0: PCH [HDA Intel PCH], périphérique 8: HDMI 2 [HDMI 2] Sous-périphériques: 1/1 Sous-périphérique #0: subdevice #0 pavucontrol shows HDMI as unplugged. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: pulseaudio 1:12.2-2ubuntu1 ProcVersionSignature: Ubuntu 4.19.0-13.14-generic 4.19.20 Uname: Linux 4.19.0-13-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.10-0ubuntu21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: franck 5998 F pulseaudio /dev/snd/pcmC1D0c: franck 5998 F...m pulseaudio /dev/snd/controlC0: franck 5998 F pulseaudio CurrentDesktop: GNOME Date: Fri Feb 22 16:16:56 2019 EcryptfsInUse: Yes ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/27/2017 dmi.bios.vendor: LENOVO dmi.bios.version: G7ETA9WW (2.69 ) dmi.board.asset.tag: Not Available dmi.board.name: 2353CTO 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: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG7ETA9WW(2.69):bd09/27/2017:svnLENOVO:pn2353CTO:pvrThinkPadT430s:rvnLENOVO:rn2353CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad T430s dmi.product.name: 2353CTO dmi.product.sku: LENOVO_MT_2353 dmi.product.version: ThinkPad T430s dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1817338/+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 1817338] Re: HDMI sound output not available in 19.04 (but works in 18.10)
Thanks. This bug has been reassigned to gnome-control-center. ** Summary changed: - HDMI sound output not available + HDMI sound output not available in 19.04 (but works in 18.10) ** Summary changed: - HDMI sound output not available in 19.04 (but works in 18.10) + HDMI sound output not selectable in 19.04 (but works in 18.10) ** Also affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Changed in: pulseaudio (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1817338 Title: HDMI sound output not selectable in 19.04 (but works in 18.10) Status in gnome-control-center package in Ubuntu: New Status in pulseaudio package in Ubuntu: Invalid Bug description: In 19.04, HDMI sound stopped working after some upgrade. The sink is somehow availalbe, but cannot be selected. In gnome-control-center, HDMI output device is listed, but if I choose it, no configuration list appears (see screen capture attached). aplay -l gives me: ~$ aplay -l Liste des Périphériques Matériels PLAYBACK carte 0: PCH [HDA Intel PCH], périphérique 0: ALC269VC Analog [ALC269VC Analog] Sous-périphériques: 0/1 Sous-périphérique #0: subdevice #0 carte 0: PCH [HDA Intel PCH], périphérique 3: HDMI 0 [HDMI 0] Sous-périphériques: 1/1 Sous-périphérique #0: subdevice #0 carte 0: PCH [HDA Intel PCH], périphérique 7: HDMI 1 [HDMI 1] Sous-périphériques: 1/1 Sous-périphérique #0: subdevice #0 carte 0: PCH [HDA Intel PCH], périphérique 8: HDMI 2 [HDMI 2] Sous-périphériques: 1/1 Sous-périphérique #0: subdevice #0 pavucontrol shows HDMI as unplugged. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: pulseaudio 1:12.2-2ubuntu1 ProcVersionSignature: Ubuntu 4.19.0-13.14-generic 4.19.20 Uname: Linux 4.19.0-13-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.10-0ubuntu21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: franck 5998 F pulseaudio /dev/snd/pcmC1D0c: franck 5998 F...m pulseaudio /dev/snd/controlC0: franck 5998 F pulseaudio CurrentDesktop: GNOME Date: Fri Feb 22 16:16:56 2019 EcryptfsInUse: Yes ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/27/2017 dmi.bios.vendor: LENOVO dmi.bios.version: G7ETA9WW (2.69 ) dmi.board.asset.tag: Not Available dmi.board.name: 2353CTO 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: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG7ETA9WW(2.69):bd09/27/2017:svnLENOVO:pn2353CTO:pvrThinkPadT430s:rvnLENOVO:rn2353CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad T430s dmi.product.name: 2353CTO dmi.product.sku: LENOVO_MT_2353 dmi.product.version: ThinkPad T430s dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1817338/+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 1819383] [NEW] VEGA 64 config for 1680x1050 is incorrect
You have been subscribed to a public bug: I have two AMD GPU cards in my system connected to an identical pair of older SAMSUNG monitors with native resolution of 1680x1050. $ lspci -d ::300 0a:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Vega 10 XT [Radeon RX Vega 64] (rev c1) 42:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] RV770 [Radeon HD 4850] The RV770 has successfully been connected to these two monitors for many years. Recently upgraded the motherboard and added the Vega 64 video card. Connecting DisplayPort from the Vega 64 to one monitor and the RV770 to the other, The Vega 64 monitor display is corrupted. See attached picture. I tried all the other supported modes for the monitor and the others all work fine (1024x768, 1280x1024, etc.) Although, it is perhaps interesting that 1680x1050 is the only 1.6:1 aspect ratio. The majority are 4:3 with 1280x1024 (5:4) and 720x400 (9:5) the exceptions. And all the other modes seem to display in a 4:3 subset of the pixels on the screen. I'll upload the /var/log/Xorg.0.log next. Other info: $ lsb_release -rd Description:Linux Mint 19.1 Tessa Release:19.1 $ apt-cache policy xserver-xorg-video-amdgpu xserver-xorg-video-amdgpu: Installed: 18.0.1-1 Candidate: 18.0.1-1 Version table: *** 18.0.1-1 500 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status EXPECTATION: Correct display output ACTUAL RESULT: "Torn" display. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC1D0p: philip 2211 F...m pulseaudio /dev/snd/controlC1: philip 2211 F pulseaudio /dev/snd/controlC0: philip 2211 F pulseaudio /dev/snd/controlC2: philip 2211 F pulseaudio CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 19.1 InstallationDate: Installed on 2019-03-10 (0 days ago) InstallationMedia: Linux Mint 19.1 "Tessa" - Release amd64 20181217 IwConfig: lono wireless extensions. enp4s0no wireless extensions. MachineType: Gigabyte Technology Co., Ltd. X399 AORUS PRO Package: linux (not installed) ProcFB: 0 radeondrmfb 1 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-46-generic root=UUID=14bde5f7-3295-4e41-bc36-8d22c00349f9 ro rootflags=subvol=@ quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-46-generic N/A linux-backports-modules-4.15.0-46-generic N/A linux-firmware 1.173.3 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: tessa Uname: Linux 4.15.0-46-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/01/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F1 dmi.board.asset.tag: Default string dmi.board.name: X399 AORUS PRO-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF1:bd10/01/2018:svnGigabyteTechnologyCo.,Ltd.:pnX399AORUSPRO:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnX399AORUSPRO-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: X399 AORUS PRO dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. ** Affects: xserver-xorg-video-amdgpu (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: apport-collected tessa -- VEGA 64 config for 1680x1050 is incorrect https://bugs.launchpad.net/bugs/1819383 You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-amdgpu 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 1809423] Re: General Performance Is "slow" including stuttering when dragging windows around etc (nvidia-390 is installed but modesetting in use)
It appears the problem is most likely this: [ 989.990] (WW) modeset(0): flip queue failed: Device or resource busy [ 989.990] (WW) modeset(0): Page flip failed: Device or resource busy [ 989.990] (EE) modeset(0): present flip failed [ 990.106] (WW) modeset(0): flip queue failed: Device or resource busy [ 990.106] (WW) modeset(0): Page flip failed: Device or resource busy [ 990.106] (EE) modeset(0): present flip failed [ 990.122] (WW) modeset(0): flip queue failed: Device or resource busy [ 990.122] (WW) modeset(0): Page flip failed: Device or resource busy [ 990.122] (EE) modeset(0): present flip failed [ 990.147] (WW) modeset(0): flip queue failed: Device or resource busy [ 990.147] (WW) modeset(0): Page flip failed: Device or resource busy where the Xorg 'modeset' driver is trying to talk to the kernel 'nouveau' driver. ** Package changed: nvidia-graphics-drivers-390 (Ubuntu) => xorg-server (Ubuntu) ** Changed in: xorg-server (Ubuntu) Status: Fix Released => New ** Summary changed: - General Performance Is "slow" including stuttering when dragging windows around etc (nvidia-390 is installed but modesetting in use) + [nouveau] General Performance Is "slow" including stuttering when dragging windows around etc -- 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/1809423 Title: [nouveau] General Performance Is "slow" including stuttering when dragging windows around etc Status in xorg-server package in Ubuntu: New Bug description: System information included in debug log. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: xorg 1:7.7+19ubuntu8 ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17 Uname: Linux 4.18.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Dec 21 19:43:06 2018 DistUpgraded: Fresh install DistroCodename: cosmic DistroVariant: ubuntu DkmsStatus: nvidia, 390.87, 4.18.0-13-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GP104 [GeForce GTX 1080] [10de:1b80] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd GP104 [GeForce GTX 1080] [1458:3717] InstallationDate: Installed on 2018-12-21 (0 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: System manufacturer System Product Name ProcEnviron: LANGUAGE=en_AU:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_AU.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-13-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/27/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3703 dmi.board.asset.tag: Default string dmi.board.name: Z170-AR dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3703:bd12/27/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ170-AR:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.95-1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1809423/+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 1809552] Re: Ubuntu sees duplicate display for each graphics card on Macbook Pro
** Changed in: xorg-server (Ubuntu) Status: Expired => 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/1809552 Title: Ubuntu sees duplicate display for each graphics card on Macbook Pro Status in xorg-server package in Ubuntu: New Bug description: After booting Ubuntu in BIOS mode on my machine for years, I just switched over to EFI boot. The reason for which I switched is that, on this machine, Ubuntu cannot detect the integrated GPU under BIOS boot. Ubuntu now recognizes both integrated and discrete GPU on my machine, but it also seems to think I have two monitors. Expected Behavior: Ubuntu properly recognizes that both graphics cards are in fact controlling the same display Actual Behavior: Ubuntu thinks I have two displays (each being controlled by a separate card?). If I navigate to the "Devices > Displays" section of the settings app, then Ubuntu lists two "Built in Displays," and offers options to "Join Displays," mirror them, etc. I have created a question on AskUbuntu (https://askubuntu.com/questions/1103696/ubuntu-duplicates-display- for-each-graphics-card-fresh-install) detailing this issue; it presents much of the same information in this bug report, along with several images. I have also discovered a similar thread from three years ago (https://askubuntu.com/questions/582574/my-macbook-has-two-built-in- displays) suggesting that I am not the only Macbook user to suffer from this issue. The user in said thread worked around this issue by powering off his iGPU. I would like to set up graphics switching in the future, so this is not an option for me. In any case, I have tested his "solution" and it DOES NOT work on my machine (I also don't have a /sys/kernel/debug/vgaswitcheroo folder like he apparently does) SYSTEM INFORMATION OS Version: Ubuntu (64-bit) 18.04.1 Kernel: 4.15.0-43-generic GRAPHICS CARD INFORMATION == $ lshw -c video *-display description: VGA compatible controller product: GK107M [GeForce GT 650M Mac Edition] vendor: NVIDIA Corporation physical id: 0 bus info: pci@:01:00.0 version: a1 width: 64 bits clock: 33MHz capabilities: pm msi pciexpress vga_controller bus_master cap_list rom configuration: driver=nouveau latency=0 resources: irq:45 memory:c000-c0ff memory:9000-9fff memory:a000-a1ff ioport:2000(size=128) memory:c100-c107 *-display description: VGA compatible controller product: 3rd Gen Core processor Graphics Controller vendor: Intel Corporation physical id: 2 bus info: pci@:00:02.0 version: 09 width: 64 bits clock: 33MHz capabilities: msi pm vga_controller bus_master cap_list configuration: driver=i915 latency=0 resources: irq:47 memory:c140-c17f memory:b000-bfff ioport:3000(size=64) MORE GRAPHICS CARD INFORMATION == $ lspci | grep VGA 00:02.0 VGA compatible controller: Intel Corporation 3rd Gen Core processor Graphics Controller (rev 09) 01:00.0 VGA compatible controller: NVIDIA Corporation GK107M [GeForce GT 650M Mac Edition] (rev a1) DISPLAY CONFIGURATION INFO (1) == NOTE: In this diagnostic, I have chosen the "Single Display" option via the System Settings app. Only one of the two "built-in displays" is actually usable, selecting the other just gives me a black screen until my changes are auto-reverted $ xrandr - q Screen 0: minimum 320 x 200, current 1440 x 900, maximum 16384 x 16384 LVDS-1 connected primary 1440x900+0+0 (normal left inverted right x axis y axis) 331mm x 207mm 1440x900 59.90*+ 1152x864 59.97 1024x768 59.95 800x600 59.96 640x480 59.94 720x400 59.97 640x400 59.96 640x350 59.84 DP-1 disconnected (normal left inverted right x axis y axis) DP-2 disconnected (normal left inverted right x axis y axis) DP-3 disconnected (normal left inverted right x axis y axis) LVDS-1-2 connected (normal left inverted right x axis y axis) 1440x900 59.90 + 59.89 1400x900 59.9659.88 1440x810 60.0059.97 1368x768 59.8859.85 1360x768 59.8059.96 1280x800 59.9959.9759.8159.91 1152x864 60.00 1280x720 60.0059.9959.8659.74 1024x768 60.0460.00 960x720 60.00 928x696 60.05 896x672 60.01 1024x576 59.9559.9659.9059.82 960x600 59.9360.00 960x540 59.9659.9959.6359.82 800x600 60.0060.3256.25 840x525 60.01
[Desktop-packages] [Bug 1712122] Re: Desktop keyboard shortcuts autorepeat (probably shouldn't)
Yeah I thought so. Can you point to where? -- 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/1712122 Title: Desktop keyboard shortcuts autorepeat (probably shouldn't) Status in gnome-shell package in Ubuntu: Triaged Bug description: "Please hold down CTRL+ALT and press T" sometimes results in (novice) users holding down all three keys at once. Desired behaviour:- One terminal opens, keyboard combination does not repeat. Actual behaviour:- Bazillions of terminals launch On my Ubuntu 16.04 system running Unity, the keyboard shortcut does not repeat. On 17.10 GNOME Shell it does. I believe it should not. See screenshot. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.24.3-0ubuntu4 ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5 Uname: Linux 4.12.0-11-generic x86_64 ApportVersion: 2.20.6-0ubuntu6 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Aug 21 18:12:51 2017 DisplayManager: gdm3 GsettingsChanges: b'org.gnome.shell' b'command-history' b"['gnome-control-center', 'bin/telegram', '~/bin/Telegram', '~/bin/telegram', '/home/alan/bin/telegram', '/home/alan/bin/Telegram', 'brackets', '/snap/bin/brackets']" b'org.gnome.shell' b'had-bluetooth-devices-setup' b'true' b'org.gnome.shell' b'app-picker-view' b'uint32 1' b'org.gnome.shell' b'favorite-apps' b"['firefox.desktop', 'rhythmbox.desktop', 'org.gnome.Nautilus.desktop', 'org.gnome.Software.desktop', 'yelp.desktop', 'ubuntu-amazon-default.desktop']" b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2017-08-02 (19 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170712) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1712122/+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 1796606] Re: gnome-shell crashed with SIGSEGV in st_widget_get_theme_node → ffi_call_unix64 → ffi_call → gjs_invoke_c_function → function_call
Are you sure it's "fixed-upstream"? Both the upstream bugs in comment #10 are still open. -- 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/1796606 Title: gnome-shell crashed with SIGSEGV in st_widget_get_theme_node → ffi_call_unix64 → ffi_call → gjs_invoke_c_function → function_call Status in gnome-shell package in Ubuntu: Confirmed Bug description: https://gitlab.gnome.org/GNOME/gnome-shell/issues/1018 https://gitlab.gnome.org/GNOME/gnome-shell/issues/804 --- The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 3.30.0-3ubuntu1, the problem page at https://errors.ubuntu.com/problem/b693e6165eedd2cd0390c2e800ccb28aaca4cd0d 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/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1796606/+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 1809423] [NEW] General Performance Is "slow" including stuttering when dragging windows around etc (nvidia-390 is installed but modesetting in use)
You have been subscribed to a public bug: System information included in debug log. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: xorg 1:7.7+19ubuntu8 ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17 Uname: Linux 4.18.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Dec 21 19:43:06 2018 DistUpgraded: Fresh install DistroCodename: cosmic DistroVariant: ubuntu DkmsStatus: nvidia, 390.87, 4.18.0-13-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GP104 [GeForce GTX 1080] [10de:1b80] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd GP104 [GeForce GTX 1080] [1458:3717] InstallationDate: Installed on 2018-12-21 (0 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: System manufacturer System Product Name ProcEnviron: LANGUAGE=en_AU:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_AU.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-13-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/27/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3703 dmi.board.asset.tag: Default string dmi.board.name: Z170-AR dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3703:bd12/27/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ170-AR:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.95-1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3 ** Affects: xorg-server (Ubuntu) Importance: Medium Status: New ** Tags: amd64 apport-bug cosmic nouveau performance ubuntu -- General Performance Is "slow" including stuttering when dragging windows around etc (nvidia-390 is installed but modesetting in use) https://bugs.launchpad.net/bugs/1809423 You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server 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 1775999] Re: Cannot set vino preferences in Lubuntu 18.04
Same to Lubuntu and Mint -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to vino in Ubuntu. https://bugs.launchpad.net/bugs/1775999 Title: Cannot set vino preferences in Lubuntu 18.04 Status in vino package in Ubuntu: Confirmed Bug description: Apparently the functionality of vino-preferences was merged into gnome-control-center for 18.04. But since Lubuntu does not include gnome-control-center, there is no way to set up vino., ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: vino 3.22.0-3ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic i686 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: i386 CurrentDesktop: LXDE Date: Sat Jun 9 08:40:31 2018 InstallationDate: Installed on 2018-03-09 (91 days ago) InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Alpha i386 (20180306.1) SourcePackage: vino UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vino/+bug/1775999/+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 1819183] Re: FFe: Update pygobject to 3.32
** Tags added: upgrade-software-version -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pygobject in Ubuntu. https://bugs.launchpad.net/bugs/1819183 Title: FFe: Update pygobject to 3.32 Status in pygobject package in Ubuntu: New Bug description: Feature Freeze exception request Since we're updating the rest of GNOME to 3.32 (including glib and gobject-introspection), it seems like it would be a good idea to update pygobject also. 3.32.0-1 is in Debian experimental ready to be synced over once this FFe is approved. https://gitlab.gnome.org/GNOME/pygobject/blob/master/NEWS https://gitlab.gnome.org/GNOME/pygobject/compare/3.30.4...3.32.0 (includes several commits that were already included in the current 3.30.4 version) Justification for lateness -- Sorry, we've been a bit busy and this wasn't a high priority. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pygobject/+bug/1819183/+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 1819359] Re: [iMac12, 1, Cirrus Logic CS4206, Green Headphone Out, N/A] No sound at all
*** This bug is a duplicate of bug 1819358 *** https://bugs.launchpad.net/bugs/1819358 ** This bug has been marked a duplicate of bug 1819358 [iMac12,1, Cirrus Logic CS4206, Green Headphone Out, N/A] No sound at all -- 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/1819359 Title: [iMac12,1, Cirrus Logic CS4206, Green Headphone Out, N/A] No sound at all Status in alsa-driver package in Ubuntu: Incomplete Bug description: Internal speakers work, only having trouble with the headphone output, (I have had this problem in every distrobution I´ve tried) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18 Uname: Linux 4.15.0-46-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC2D0c: yoyo 1917 F...m pulseaudio /dev/snd/pcmC0D1p: yoyo 1917 F...m pulseaudio /dev/snd/controlC0: yoyo 1917 F pulseaudio /dev/snd/controlC1: yoyo 1917 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sun Mar 10 18:44:38 2019 EcryptfsInUse: Yes InstallationDate: Installed on 2019-03-10 (0 days ago) InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64+mac (20160803) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Green Headphone Out, N/A Symptom_Type: No sound at all Title: [iMac12,1, Cirrus Logic CS4206, Green Headphone Out, N/A] No sound at all UpgradeStatus: Upgraded to bionic on 2019-03-10 (0 days ago) dmi.bios.date: 09/25/2018 dmi.bios.vendor: Apple Inc. dmi.bios.version: 82.0.0.0.0 dmi.board.name: Mac-942B5BF58194151B dmi.board.vendor: Apple Inc. dmi.chassis.type: 13 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-942B5BF58194151B dmi.modalias: dmi:bvnAppleInc.:bvr82.0.0.0.0:bd09/25/2018:svnAppleInc.:pniMac12,1:pvr1.0:rvnAppleInc.:rnMac-942B5BF58194151B:rvr:cvnAppleInc.:ct13:cvrMac-942B5BF58194151B: dmi.product.family: iMac dmi.product.name: iMac12,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1819359/+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 1819183] Re: FFe: Update pygobject to 3.32
** Description changed: Feature Freeze exception request Since we're updating the rest of GNOME to 3.32 (including glib and gobject-introspection), it seems like it would be a good idea to update pygobject also. - 3.31.4-1 is in Debian experimental ready to be synced over once this FFe - is approved. 3.32.0 is expected next week. + 3.32.0-1 is in Debian experimental ready to be synced over once this FFe + is approved. https://gitlab.gnome.org/GNOME/pygobject/blob/master/NEWS - https://gitlab.gnome.org/GNOME/pygobject/compare/3.30.4...3.31.4 (includes several commits that were already included in the current 3.30.4 version) + https://gitlab.gnome.org/GNOME/pygobject/compare/3.30.4...3.32.0 (includes several commits that were already included in the current 3.30.4 version) Justification for lateness -- Sorry, we've been a bit busy and this wasn't a high priority. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pygobject in Ubuntu. https://bugs.launchpad.net/bugs/1819183 Title: FFe: Update pygobject to 3.32 Status in pygobject package in Ubuntu: New Bug description: Feature Freeze exception request Since we're updating the rest of GNOME to 3.32 (including glib and gobject-introspection), it seems like it would be a good idea to update pygobject also. 3.32.0-1 is in Debian experimental ready to be synced over once this FFe is approved. https://gitlab.gnome.org/GNOME/pygobject/blob/master/NEWS https://gitlab.gnome.org/GNOME/pygobject/compare/3.30.4...3.32.0 (includes several commits that were already included in the current 3.30.4 version) Justification for lateness -- Sorry, we've been a bit busy and this wasn't a high priority. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pygobject/+bug/1819183/+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 1770929] Re: Duplicity fails with UnicodeDecodeError in uexc function
The 0.8-series was affected by this (as I mentioned above, fixing the
underlying problem avoids this error and a number of these have been
fixed, so it is harder to trigger).
I have just proposed a fix for it be merged into the 0.8-series:
https://code.launchpad.net/~aaron-whitehouse/duplicity/08-uexc-fix
I would still appreciate any feedback on the 0.7-series branch above. I
am more nervous about making changes in our stable branch without
feedback.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to duplicity in Ubuntu.
https://bugs.launchpad.net/bugs/1770929
Title:
Duplicity fails with UnicodeDecodeError in uexc function
Status in Duplicity:
In Progress
Status in duplicity package in Ubuntu:
Confirmed
Bug description:
backup worked under Ubuntu 17.10
It also worked on Ubuntu 18.4 before last week's update (run on Friday 11.5)
my drive is encrypted
this is the error message in the error frame
Traceback (innermost last):
File "/usr/bin/duplicity", line 1555, in
with_tempdir(main)
File "/usr/bin/duplicity", line 1541, in with_tempdir
fn()
File "/usr/bin/duplicity", line 1393, in main
do_backup(action)
File "/usr/bin/duplicity", line 1523, in do_backup
incremental_backup(sig_chain)
File "/usr/bin/duplicity", line 668, in incremental_backup
globals.backend)
File "/usr/bin/duplicity", line 454, in write_multivol
(tdp, dest_filename, vol_num)))
File "/usr/lib/python2.7/dist-packages/duplicity/asyncscheduler.py", line
146, in schedule_task
return self.__run_synchronously(fn, params)
File "/usr/lib/python2.7/dist-packages/duplicity/asyncscheduler.py", line
172, in __run_synchronously
ret = fn(*params)
File "/usr/bin/duplicity", line 453, in
vol_num: put(tdp, dest_filename, vol_num),
File "/usr/bin/duplicity", line 342, in put
backend.put(tdp, dest_filename)
File "/usr/lib/python2.7/dist-packages/duplicity/backend.py", line 395, in
inner_retry
% (n, e.__class__.__name__, util.uexc(e)))
File "/usr/lib/python2.7/dist-packages/duplicity/util.py", line 79, in uexc
return ufn(unicode(e).encode('utf-8'))
UnicodeDecodeError: 'ascii' codec can't decode byte 0xe2 in position 37:
ordinal not in range(128)
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: duplicity 0.7.17-0ubuntu1
ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
Uname: Linux 4.15.0-20-generic x86_64
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Sun May 13 09:55:00 2018
InstallationDate: Installed on 2018-05-01 (11 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
SourcePackage: duplicity
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/duplicity/+bug/1770929/+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 1812527] Re: [bionic][regression] gnome-shell crashes with SIGSEGV in meta_window_actor_is_destroyed(self=NULL) called from _switchWorkspaceDone() [windowManager.js:1787]
I faced this problem first when I was using skype and zoom. Both in shared screen mode. Using Android Emulator, my Ubuntu are crashing too. Just only when I change the Workspace. -- 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/1812527 Title: [bionic][regression] gnome-shell crashes with SIGSEGV in meta_window_actor_is_destroyed(self=NULL) called from _switchWorkspaceDone() [windowManager.js:1787] Status in gjs package in Ubuntu: Confirmed Status in gnome-shell package in Ubuntu: Confirmed Status in gjs source package in Bionic: Confirmed Status in gnome-shell source package in Bionic: Confirmed Bug description: https://errors.ubuntu.com/problem/cb400a6f83ed57af8bb117cf84d5ed6d7e2ffcee https://gitlab.gnome.org/GNOME/gnome-shell/issues/927 Switching workspace with the Android Emulator running will blink the screen as if gnome restarted, if I switch workspace one more time, it will completely crash and I will need to log in again. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.3-0ubuntu0.18.04.4 Uname: Linux 4.20.3-acso x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Jan 19 20:05:34 2019 DisplayManager: gdm3 GsettingsChanges: b'org.gnome.shell' b'favorite-apps' redacted by apport b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2019-01-15 (4 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/1812527/+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 1770929] Re: Duplicity fails with UnicodeDecodeError in uexc function
** Branch linked: lp:~aaron-whitehouse/duplicity/08-uexc-fix
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to duplicity in Ubuntu.
https://bugs.launchpad.net/bugs/1770929
Title:
Duplicity fails with UnicodeDecodeError in uexc function
Status in Duplicity:
In Progress
Status in duplicity package in Ubuntu:
Confirmed
Bug description:
backup worked under Ubuntu 17.10
It also worked on Ubuntu 18.4 before last week's update (run on Friday 11.5)
my drive is encrypted
this is the error message in the error frame
Traceback (innermost last):
File "/usr/bin/duplicity", line 1555, in
with_tempdir(main)
File "/usr/bin/duplicity", line 1541, in with_tempdir
fn()
File "/usr/bin/duplicity", line 1393, in main
do_backup(action)
File "/usr/bin/duplicity", line 1523, in do_backup
incremental_backup(sig_chain)
File "/usr/bin/duplicity", line 668, in incremental_backup
globals.backend)
File "/usr/bin/duplicity", line 454, in write_multivol
(tdp, dest_filename, vol_num)))
File "/usr/lib/python2.7/dist-packages/duplicity/asyncscheduler.py", line
146, in schedule_task
return self.__run_synchronously(fn, params)
File "/usr/lib/python2.7/dist-packages/duplicity/asyncscheduler.py", line
172, in __run_synchronously
ret = fn(*params)
File "/usr/bin/duplicity", line 453, in
vol_num: put(tdp, dest_filename, vol_num),
File "/usr/bin/duplicity", line 342, in put
backend.put(tdp, dest_filename)
File "/usr/lib/python2.7/dist-packages/duplicity/backend.py", line 395, in
inner_retry
% (n, e.__class__.__name__, util.uexc(e)))
File "/usr/lib/python2.7/dist-packages/duplicity/util.py", line 79, in uexc
return ufn(unicode(e).encode('utf-8'))
UnicodeDecodeError: 'ascii' codec can't decode byte 0xe2 in position 37:
ordinal not in range(128)
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: duplicity 0.7.17-0ubuntu1
ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
Uname: Linux 4.15.0-20-generic x86_64
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Sun May 13 09:55:00 2018
InstallationDate: Installed on 2018-05-01 (11 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
SourcePackage: duplicity
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/duplicity/+bug/1770929/+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 1819368] Re: unity-control-center crashed with SIGSEGV in free()
** Information type changed from Private to Public -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1819368 Title: unity-control-center crashed with SIGSEGV in free() Status in unity-control-center package in Ubuntu: New Bug description: Happens when trying to open the info (details) panel ProblemType: Crash DistroRelease: Ubuntu 19.04 Package: unity-control-center 15.04.0+19.04.20190209-0ubuntu2 ProcVersionSignature: Ubuntu 4.19.0-13.14-generic 4.19.20 Uname: Linux 4.19.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 CurrentDesktop: Unity:Unity7:ubuntu Date: Sun Mar 10 15:09:20 2019 ExecutablePath: /usr/bin/unity-control-center ExecutableTimestamp: 1551456572 InstallationDate: Installed on 2019-03-09 (1 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190305.1) ProcCmdline: unity-control-center info --verbose ProcCwd: /home/doug SegvAnalysis: Segfault happened at: 0x7f17f1c1f25d <__GI___libc_free+29>: mov -0x8(%rdi),%rax PC (0x7f17f1c1f25d) ok source "-0x8(%rdi)" (0xfff8) not located in a known VMA region (needed readable region)! destination "%rax" ok SegvReason: reading unknown VMA Signal: 11 SourcePackage: unity-control-center StacktraceTop: __GI___libc_free (mem=0x1) at malloc.c:3109 g_unix_mount_free () at /lib/x86_64-linux-gnu/libgio-2.0.so.0 () at /usr/lib/x86_64-linux-gnu/unity-control-center-1/panels/libinfo.so () at /usr/lib/x86_64-linux-gnu/unity-control-center-1/panels/libinfo.so g_type_create_instance () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: unity-control-center crashed with SIGSEGV in __GI___libc_free() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-control-center/+bug/1819368/+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 1819375] [NEW] Unable to launch applications from Nautilus by visiting /usr/share/applications and clicking on icon of application
Public bug reported: Steps to reproduce: 1. Install Ubuntu 19.04 2. Open Nautilus 3. Navigate to /usr/share/applications 4. Try to click on some application icon to launch it Expected results: 1. Application icons are shown 2. User can launch application by clicking on its icon Actual results: 1. Application icons are not shown 2. The *.desktop file is opened in Gedit instead of launching. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: nautilus 1:3.31.90-1ubuntu2 ProcVersionSignature: Ubuntu 4.19.0-13.14-generic 4.19.20 Uname: Linux 4.19.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 CurrentDesktop: Unity:Unity7:ubuntu Date: Sun Mar 10 23:22:33 2019 GsettingsChanges: SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug disco ** Attachment added: "The /usr/share/applications folder is opened in Nautilus" https://bugs.launchpad.net/bugs/1819375/+attachment/5245253/+files/nautilus_usr-share-applications.png -- 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/1819375 Title: Unable to launch applications from Nautilus by visiting /usr/share/applications and clicking on icon of application Status in nautilus package in Ubuntu: New Bug description: Steps to reproduce: 1. Install Ubuntu 19.04 2. Open Nautilus 3. Navigate to /usr/share/applications 4. Try to click on some application icon to launch it Expected results: 1. Application icons are shown 2. User can launch application by clicking on its icon Actual results: 1. Application icons are not shown 2. The *.desktop file is opened in Gedit instead of launching. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: nautilus 1:3.31.90-1ubuntu2 ProcVersionSignature: Ubuntu 4.19.0-13.14-generic 4.19.20 Uname: Linux 4.19.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 CurrentDesktop: Unity:Unity7:ubuntu Date: Sun Mar 10 23:22:33 2019 GsettingsChanges: SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1819375/+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 1767454] Re: "Other Locations" does not automatically find Samba servers in Ubuntu 18.04
What's described in comment #32 is being tracked in bug https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1778322 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1767454 Title: "Other Locations" does not automatically find Samba servers in Ubuntu 18.04 Status in dolphin: Unknown Status in gvfs: Fix Released Status in OEM Priority Project: New Status in samba: Unknown Status in gvfs package in Ubuntu: Fix Released Status in samba package in Ubuntu: Invalid Bug description: Ubuntu: 18.04 clean install Nautilus: 1:3.26.3-0ubuntu4 The actions taken to produce the problem: Click on “Other Locations” in Nautilus. The expected result of these actions: Samba servers to automatically show up under “Networks”. This is the behavior in Ubuntu 17.10 using Nautilus 1:3.26.0-0ub. Also, clicking on “”Windows Network” immediately shows "Folder is Empty". The actual result of these actions: The Samba servers never show up under “Networks” and clicking on "Windows Network" always immediately comes up with "Folder is Empty". Further information: This happens on both machines with a clean Ubuntu 18.04 install. My Ubuntu 17.10 machines still work like expected. I can still manually type in the Samba information in "Connect to Server" and the 18.04 machines connect just fine. From syslog: Apr 27 13:49:34 david-HP-ProBook-440-G2 dbus-daemon[1333]: [session uid=1000 pid=1333] Activating service name='org.gnome.Nautilus' requested by ':1.13' (uid=1000 pid=1468 comm="/usr/bin/gnome-shell " label="unconfined") Apr 27 13:49:34 david-HP-ProBook-440-G2 dbus-daemon[1333]: [session uid=1000 pid=1333] Successfully activated service 'org.gnome.Nautilus' Apr 27 13:49:35 david-HP-ProBook-440-G2 dbus-daemon[754]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostname1.service' requested by ':1.131' (uid=1000 pid=4857 comm="/usr/bin/nautilus --gapplication-service " label="unconfined") Apr 27 13:49:35 david-HP-ProBook-440-G2 systemd[1]: Starting Hostname Service... Apr 27 13:49:35 david-HP-ProBook-440-G2 nautilus[4857]: Called "net usershare info" but it failed: Failed to execute child process “net” (No such file or directory) Apr 27 13:49:35 david-HP-ProBook-440-G2 dbus-daemon[754]: [system] Successfully activated service 'org.freedesktop.hostname1' Apr 27 13:49:35 david-HP-ProBook-440-G2 systemd[1]: Started Hostname Service. Apr 27 13:49:40 david-HP-ProBook-440-G2 gvfsd[1432]: mkdir failed on directory /var/cache/samba: Permission denied To manage notifications about this bug go to: https://bugs.launchpad.net/dolphin/+bug/1767454/+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 1778322] Re: gvfs-smb-browse can't browse samba/smb tree
Looking at this next. ** Changed in: samba (Ubuntu) Assignee: (unassigned) => Andreas Hasenack (ahasenack) ** Changed in: samba (Ubuntu) Status: Triaged => In Progress -- 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/1778322 Title: gvfs-smb-browse can't browse samba/smb tree Status in gvfs package in Ubuntu: Triaged Status in nautilus package in Ubuntu: Invalid Status in samba package in Ubuntu: In Progress Status in gvfs source package in Bionic: Triaged Status in gvfs source package in Cosmic: Triaged Bug description: * Impact On Bionic Beaver 18.04.1 gvfs-smb-browse can't browse smbtree because of that Nautilus displays "Empty Folder" when clicking "Windows Network" * Test case Try to browse a smb share from a bionic client * Regression potential Check that smb browsing/mounts still work as they should --- Nautilus should show smbtree nad host on the smb network. When inputing this command: killall gvfsd-smb-browse && GVFS_DEBUG=1 /usr/lib/gvfs/gvfsd-smb-browse You can see the error: smb-network: Queued new job 0x55b19a2c9f40 (GVfsJobCreateMonitor) smb-network: send_reply(0x55b19a2c9f40), failed=1 (Action not supported by the processing engine) smb-network: backend_dbus_handler org.gtk.vfs.Mount:QueryFilesystemInfo (pid=5708) smb-network: Queued new job 0x55b19a2e7820 (GVfsJobQueryFsInfo) smb-network: send_reply(0x55b19a2e7820), failed=0 () smb-network: backend_dbus_handler org.gtk.vfs.Mount:Enumerate (pid=5708) smb-network: Queued new job 0x55b19a2c30c0 (GVfsJobEnumerate) smb-network: send_reply(0x55b19a2c30c0), failed=0 () Proposed solution: Add gvfsbackendbrowse-switch-to-NT1.patch disscused on RedHat Bugzilla [link]https://bugzilla.redhat.com/show_bug.cgi?id=1513394 which implements "change to NT1" in gvfs-smb-browse to browse smbtree to aviod adding "max client protocol" = NT1" to smb.conf to switch all samba to unsafe NT1 which most users are doing to correct this bug. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1778322/+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 1814133] Re: update to openjdk 11 in 18.04 LTS
jabref works in disco/19.04. -- 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/1814133 Title: update to openjdk 11 in 18.04 LTS Status in ca-certificates-java package in Ubuntu: New Status in fonts-liberation2 package in Ubuntu: New Status in gatk-native-bindings package in Ubuntu: New Status in gkl package in Ubuntu: New Status in htsjdk package in Ubuntu: New Status in jameica package in Ubuntu: New Status in jameica-datasource package in Ubuntu: New Status in jameica-util package in Ubuntu: New Status in jasperreports package in Ubuntu: New Status in jaxws-api package in Ubuntu: New Status in jws-api package in Ubuntu: New Status in libjogl2-java package in Ubuntu: New Status in libreoffice package in Ubuntu: New Status in libreoffice-l10n package in Ubuntu: New Status in metro-policy package in Ubuntu: New Status in octave package in Ubuntu: New Status in saaj package in Ubuntu: New Status in activemq source package in Bionic: Fix Committed Status in afterburner.fx source package in Bionic: Fix Committed Status in annotation-indexer source package in Bionic: Fix Committed Status in apache-directory-server source package in Bionic: Fix Committed Status in aspectj source package in Bionic: Fix Committed Status in aspectj-maven-plugin source package in Bionic: Fix Committed Status in batik source package in Bionic: Fix Committed Status in bindex source package in Bionic: Fix Committed Status in bridge-method-injector source package in Bionic: Fix Committed Status in carrotsearch-hppc source package in Bionic: Fix Committed Status in clojure source package in Bionic: Fix Committed Status in clojure1.8 source package in Bionic: Fix Committed Status in commons-httpclient source package in Bionic: Fix Committed Status in dd-plist source package in Bionic: Fix Committed Status in ecj source package in Bionic: Fix Committed Status in eclipselink source package in Bionic: Fix Committed Status in elki source package in Bionic: Fix Committed Status in figtree source package in Bionic: Fix Committed Status in fontawesomefx source package in Bionic: Fix Committed Status in gettext source package in Bionic: Fix Committed Status in gluegen2 source package in Bionic: Fix Committed Status in gradle source package in Bionic: Fix Committed Status in gradle-debian-helper source package in Bionic: Fix Committed Status in groovy source package in Bionic: Fix Committed Status in hikaricp source package in Bionic: Fix Committed Status in hsqldb source package in Bionic: Fix Committed Status in hsqldb1.8.0 source package in Bionic: Fix Committed Status in insubstantial source package in Bionic: Fix Committed Status in jabref source package in Bionic: Fix Committed Status in jackson-core source package in Bionic: Fix Committed Status in jackson-databind source package in Bionic: Fix Committed Status in jackson-dataformat-xml source package in Bionic: Fix Committed Status in jackson-module-jaxb-annotations source package in Bionic: Fix Committed Status in java-common source package in Bionic: Fix Committed Status in javafxsvg source package in Bionic: Fix Committed Status in javamail source package in Bionic: Fix Committed Status in javatools source package in Bionic: Fix Committed Status in jboss-classfilewriter source package in Bionic: Fix Committed Status in jboss-jdeparser2 source package in Bionic: Fix Committed Status in jboss-modules source package in Bionic: Fix Committed Status in jcommander source package in Bionic: Fix Committed Status in jersey1 source package in Bionic: Fix Committed Status in jftp source package in Bionic: Fix Committed Status in jhove source package in Bionic: Fix Committed Status in jmdns source package in Bionic: Fix Committed Status in jnr-posix source package in Bionic: Fix Committed Status in jruby source package in Bionic: Fix Committed Status in jruby-openssl source package in Bionic: Fix Committed Status in jtreg source package in Bionic: Fix Committed Status in jts source package in Bionic: Fix Committed Status in junit4 source package in Bionic: Fix Committed Status in jxgrabkey source package in Bionic: Fix Committed Status in jython source package in Bionic: Fix Committed Status in libapache-poi-java source package in Bionic: Fix Committed Status in libbtm-java source package in Bionic: Fix Committed Status in libcommons-collections3-java source package in Bionic: Fix Committed Status in libcommons-collections4-java source package in Bionic: Fix Committed Status in libcommons-compress-java source package in Bionic: Fix Committed Status in libcommons-lang3-java source package in Bionic: Fix Committed Status in libgpars-groovy-java source package in Bionic: Fix Committed Status in libhibernate-validator-java source
[Desktop-packages] [Bug 1795703] Re: Ubuntu Dock gets replaced with a standard GNOME one after a while
Ok, happened again :( After such a long time, I was hoping it's gone. Sorry for spamming. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1795703 Title: Ubuntu Dock gets replaced with a standard GNOME one after a while Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Confirmed Bug description: I don't reboot my desktop and don't hibernate it, it just works for multiple days in a row without a reboot. I only turn off the monitor when I go out. Sometimes, after a while, when I turn on the monitor, Ubuntu's Dock is no longer there and what I get is the GNOME Dock which is hidden and can be seen by pressing "Super" (which shows all windows as well). This is annoying. Not sure if related, but here's what I've found in the journalctl logs: https://gist.github.com/k-bx/3a11b3ae34531a0dd2eb9cdaac97cf6c > JS ERROR: TypeError: this._workspaceIsolation is undefined ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell-extension-ubuntu-dock 0.9.1ubuntu18.04.1 ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18 Uname: Linux 4.15.0-34-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Oct 2 19:32:07 2018 InstallationDate: Installed on 2018-08-30 (32 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) PackageArchitecture: all SourcePackage: gnome-shell-extension-ubuntu-dock UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1795703/+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 1819255] Re: Ubuntu 18.04 suspends intermittently
** Package changed: pm-utils (Ubuntu) => linux (Ubuntu) ** Attachment added: "dmesg log file" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1819255/+attachment/5245200/+files/dmesg.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pm-utils in Ubuntu. https://bugs.launchpad.net/bugs/1819255 Title: Ubuntu 18.04 suspends intermittently Status in linux package in Ubuntu: New Bug description: I am using Lenovo Thinkpad E450 with Ubuntu 18.04.2 and kernel version is Linux 4.14.105-0414105-generic. I am currently not able to suspend my laptop properly. I first experienced this when I was using the kernel 4.15.46. Expected behavior when commanded to suspend: Display goes black, the CPU fan is switched off, the power LED pulsates showing that the computer is in suspend mode. This should happen whenever the PC is suspended using the command 'sudo systemctl suspend' or closing the lid or choosing suspend in the menu options by long-pressing the power button. What actually happens: If any of the above methods is used to suspend the PC, the display goes black, the PC goes to suspend state after a few seconds, but remains in suspend only for a maximum of 7-10 seconds. After that it automatically resumes, with the display trying to show the lockscreen if lid is not closed. If lid is closed, then I know it has resumed as the power LED stays on and the fan runs. As time goes, it intermittently goes to suspend for a few seconds and resumes back. There is no unnatural behavior according to 'journalctl' or 'dmesg'. The system supposedly goes to suspend "only for a few seconds" and resumes back. To resolve this issue I tried using 4.18 kernel and still the issue persisted.(Original kernel version was 4.15) In another forum, I was suggested to use 4.14 kernel and even now the issue persists. I don't know if this information would be helpful but during boot, I got these errors: ACPI Error: Needed type [Reference], found [Integer] (ptrval) (20180531/exresop-69) ACPI Error: AE_AML_OPERAND_TYPE, While resolving operands for [Store] (20180531/dswexec-427) ACPI Error: Method parse/execution failed \_PR.CPU0._PDC, AE_AML_OPERAND_TYPE (20180531/psparse-516) I also did a 'cat /sys/kernel/debug/suspend_stats' which returned 5 successes and 0 failures of any type. PS: I don't think this is a bug based on a particular application/package, so I didn't include any. Thanks in advance To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1819255/+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 1819359] Re: [iMac12, 1, Cirrus Logic CS4206, Green Headphone Out, N/A] No sound at all
Thanks for helping build a better Ubuntu. Could you run the following command in the terminal? $ sudo apt-get install --install-recommends linux-generic-hwe-18.04 xserver-xorg-hwe-18.04 Restart your computer, and tell us if it works now. Thanks. ** Changed in: alsa-driver (Ubuntu) Status: New => Incomplete -- 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/1819359 Title: [iMac12,1, Cirrus Logic CS4206, Green Headphone Out, N/A] No sound at all Status in alsa-driver package in Ubuntu: Incomplete Bug description: Internal speakers work, only having trouble with the headphone output, (I have had this problem in every distrobution I´ve tried) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18 Uname: Linux 4.15.0-46-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC2D0c: yoyo 1917 F...m pulseaudio /dev/snd/pcmC0D1p: yoyo 1917 F...m pulseaudio /dev/snd/controlC0: yoyo 1917 F pulseaudio /dev/snd/controlC1: yoyo 1917 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sun Mar 10 18:44:38 2019 EcryptfsInUse: Yes InstallationDate: Installed on 2019-03-10 (0 days ago) InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64+mac (20160803) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Green Headphone Out, N/A Symptom_Type: No sound at all Title: [iMac12,1, Cirrus Logic CS4206, Green Headphone Out, N/A] No sound at all UpgradeStatus: Upgraded to bionic on 2019-03-10 (0 days ago) dmi.bios.date: 09/25/2018 dmi.bios.vendor: Apple Inc. dmi.bios.version: 82.0.0.0.0 dmi.board.name: Mac-942B5BF58194151B dmi.board.vendor: Apple Inc. dmi.chassis.type: 13 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-942B5BF58194151B dmi.modalias: dmi:bvnAppleInc.:bvr82.0.0.0.0:bd09/25/2018:svnAppleInc.:pniMac12,1:pvr1.0:rvnAppleInc.:rnMac-942B5BF58194151B:rvr:cvnAppleInc.:ct13:cvrMac-942B5BF58194151B: dmi.product.family: iMac dmi.product.name: iMac12,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1819359/+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 1819358] [NEW] [iMac12, 1, Cirrus Logic CS4206, Green Headphone Out, N/A] No sound at all
Public bug reported: Internal speakers work, only having trouble with the headphone output, (I have had this problem in every distrobution I´ve tried) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18 Uname: Linux 4.15.0-46-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC2D0c: yoyo 1917 F...m pulseaudio /dev/snd/pcmC0D1p: yoyo 1917 F...m pulseaudio /dev/snd/controlC0: yoyo 1917 F pulseaudio /dev/snd/controlC1: yoyo 1917 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sun Mar 10 18:44:38 2019 EcryptfsInUse: Yes InstallationDate: Installed on 2019-03-10 (0 days ago) InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64+mac (20160803) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Green Headphone Out, N/A Symptom_Type: No sound at all Title: [iMac12,1, Cirrus Logic CS4206, Green Headphone Out, N/A] No sound at all UpgradeStatus: Upgraded to bionic on 2019-03-10 (0 days ago) dmi.bios.date: 09/25/2018 dmi.bios.vendor: Apple Inc. dmi.bios.version: 82.0.0.0.0 dmi.board.name: Mac-942B5BF58194151B dmi.board.vendor: Apple Inc. dmi.chassis.type: 13 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-942B5BF58194151B dmi.modalias: dmi:bvnAppleInc.:bvr82.0.0.0.0:bd09/25/2018:svnAppleInc.:pniMac12,1:pvr1.0:rvnAppleInc.:rnMac-942B5BF58194151B:rvr:cvnAppleInc.:ct13:cvrMac-942B5BF58194151B: dmi.product.family: iMac dmi.product.name: iMac12,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- 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/1819358 Title: [iMac12,1, Cirrus Logic CS4206, Green Headphone Out, N/A] No sound at all Status in alsa-driver package in Ubuntu: New Bug description: Internal speakers work, only having trouble with the headphone output, (I have had this problem in every distrobution I´ve tried) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18 Uname: Linux 4.15.0-46-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC2D0c: yoyo 1917 F...m pulseaudio /dev/snd/pcmC0D1p: yoyo 1917 F...m pulseaudio /dev/snd/controlC0: yoyo 1917 F pulseaudio /dev/snd/controlC1: yoyo 1917 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sun Mar 10 18:44:38 2019 EcryptfsInUse: Yes InstallationDate: Installed on 2019-03-10 (0 days ago) InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64+mac (20160803) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Green Headphone Out, N/A Symptom_Type: No sound at all Title: [iMac12,1, Cirrus Logic CS4206, Green Headphone Out, N/A] No sound at all UpgradeStatus: Upgraded to bionic on 2019-03-10 (0 days ago) dmi.bios.date: 09/25/2018 dmi.bios.vendor: Apple Inc. dmi.bios.version: 82.0.0.0.0 dmi.board.name: Mac-942B5BF58194151B dmi.board.vendor: Apple Inc. dmi.chassis.type: 13 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-942B5BF58194151B dmi.modalias: dmi:bvnAppleInc.:bvr82.0.0.0.0:bd09/25/2018:svnAppleInc.:pniMac12,1:pvr1.0:rvnAppleInc.:rnMac-942B5BF58194151B:rvr:cvnAppleInc.:ct13:cvrMac-942B5BF58194151B: dmi.product.family: iMac dmi.product.name: iMac12,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1819358/+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 1819359] [NEW] [iMac12, 1, Cirrus Logic CS4206, Green Headphone Out, N/A] No sound at all
Public bug reported: Internal speakers work, only having trouble with the headphone output, (I have had this problem in every distrobution I´ve tried) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18 Uname: Linux 4.15.0-46-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC2D0c: yoyo 1917 F...m pulseaudio /dev/snd/pcmC0D1p: yoyo 1917 F...m pulseaudio /dev/snd/controlC0: yoyo 1917 F pulseaudio /dev/snd/controlC1: yoyo 1917 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sun Mar 10 18:44:38 2019 EcryptfsInUse: Yes InstallationDate: Installed on 2019-03-10 (0 days ago) InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64+mac (20160803) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Green Headphone Out, N/A Symptom_Type: No sound at all Title: [iMac12,1, Cirrus Logic CS4206, Green Headphone Out, N/A] No sound at all UpgradeStatus: Upgraded to bionic on 2019-03-10 (0 days ago) dmi.bios.date: 09/25/2018 dmi.bios.vendor: Apple Inc. dmi.bios.version: 82.0.0.0.0 dmi.board.name: Mac-942B5BF58194151B dmi.board.vendor: Apple Inc. dmi.chassis.type: 13 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-942B5BF58194151B dmi.modalias: dmi:bvnAppleInc.:bvr82.0.0.0.0:bd09/25/2018:svnAppleInc.:pniMac12,1:pvr1.0:rvnAppleInc.:rnMac-942B5BF58194151B:rvr:cvnAppleInc.:ct13:cvrMac-942B5BF58194151B: dmi.product.family: iMac dmi.product.name: iMac12,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- 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/1819359 Title: [iMac12,1, Cirrus Logic CS4206, Green Headphone Out, N/A] No sound at all Status in alsa-driver package in Ubuntu: New Bug description: Internal speakers work, only having trouble with the headphone output, (I have had this problem in every distrobution I´ve tried) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18 Uname: Linux 4.15.0-46-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC2D0c: yoyo 1917 F...m pulseaudio /dev/snd/pcmC0D1p: yoyo 1917 F...m pulseaudio /dev/snd/controlC0: yoyo 1917 F pulseaudio /dev/snd/controlC1: yoyo 1917 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sun Mar 10 18:44:38 2019 EcryptfsInUse: Yes InstallationDate: Installed on 2019-03-10 (0 days ago) InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64+mac (20160803) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Green Headphone Out, N/A Symptom_Type: No sound at all Title: [iMac12,1, Cirrus Logic CS4206, Green Headphone Out, N/A] No sound at all UpgradeStatus: Upgraded to bionic on 2019-03-10 (0 days ago) dmi.bios.date: 09/25/2018 dmi.bios.vendor: Apple Inc. dmi.bios.version: 82.0.0.0.0 dmi.board.name: Mac-942B5BF58194151B dmi.board.vendor: Apple Inc. dmi.chassis.type: 13 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-942B5BF58194151B dmi.modalias: dmi:bvnAppleInc.:bvr82.0.0.0.0:bd09/25/2018:svnAppleInc.:pniMac12,1:pvr1.0:rvnAppleInc.:rnMac-942B5BF58194151B:rvr:cvnAppleInc.:ct13:cvrMac-942B5BF58194151B: dmi.product.family: iMac dmi.product.name: iMac12,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1819359/+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 1767454] Re: "Other Locations" does not automatically find Samba servers in Ubuntu 18.04
I have to say that this bug is a dissapointment. The whole samba support in Ubuntu since 18.04 is abysmal. Prior to this, I was able to access shares with no problems, now there is a problem. The bug has been posted one year ago. After changing the protoocol, I discovered I needed to change the interface too, because samba somehow insists on using virtbr0. Why? These things are a dealbreaker. My wife uses a NAS drive on our network. Each time I tried to show her the advantages of linux, some _basic_ function like using a NAS without configuring a f.. FTP client for her, just coming to the box and finding that it works, prevented her from switching. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1767454 Title: "Other Locations" does not automatically find Samba servers in Ubuntu 18.04 Status in dolphin: Unknown Status in gvfs: Fix Released Status in OEM Priority Project: New Status in samba: Unknown Status in gvfs package in Ubuntu: Fix Released Status in samba package in Ubuntu: Invalid Bug description: Ubuntu: 18.04 clean install Nautilus: 1:3.26.3-0ubuntu4 The actions taken to produce the problem: Click on “Other Locations” in Nautilus. The expected result of these actions: Samba servers to automatically show up under “Networks”. This is the behavior in Ubuntu 17.10 using Nautilus 1:3.26.0-0ub. Also, clicking on “”Windows Network” immediately shows "Folder is Empty". The actual result of these actions: The Samba servers never show up under “Networks” and clicking on "Windows Network" always immediately comes up with "Folder is Empty". Further information: This happens on both machines with a clean Ubuntu 18.04 install. My Ubuntu 17.10 machines still work like expected. I can still manually type in the Samba information in "Connect to Server" and the 18.04 machines connect just fine. From syslog: Apr 27 13:49:34 david-HP-ProBook-440-G2 dbus-daemon[1333]: [session uid=1000 pid=1333] Activating service name='org.gnome.Nautilus' requested by ':1.13' (uid=1000 pid=1468 comm="/usr/bin/gnome-shell " label="unconfined") Apr 27 13:49:34 david-HP-ProBook-440-G2 dbus-daemon[1333]: [session uid=1000 pid=1333] Successfully activated service 'org.gnome.Nautilus' Apr 27 13:49:35 david-HP-ProBook-440-G2 dbus-daemon[754]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostname1.service' requested by ':1.131' (uid=1000 pid=4857 comm="/usr/bin/nautilus --gapplication-service " label="unconfined") Apr 27 13:49:35 david-HP-ProBook-440-G2 systemd[1]: Starting Hostname Service... Apr 27 13:49:35 david-HP-ProBook-440-G2 nautilus[4857]: Called "net usershare info" but it failed: Failed to execute child process “net” (No such file or directory) Apr 27 13:49:35 david-HP-ProBook-440-G2 dbus-daemon[754]: [system] Successfully activated service 'org.freedesktop.hostname1' Apr 27 13:49:35 david-HP-ProBook-440-G2 systemd[1]: Started Hostname Service. Apr 27 13:49:40 david-HP-ProBook-440-G2 gvfsd[1432]: mkdir failed on directory /var/cache/samba: Permission denied To manage notifications about this bug go to: https://bugs.launchpad.net/dolphin/+bug/1767454/+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 1717951] Re: UIFe: Drop imagemagick-display from the default install
amano, please open a new bug for new issues instead of commenting on old closed bugs. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/1717951 Title: UIFe: Drop imagemagick-display from the default install Status in ubuntu-settings package in Ubuntu: Fix Released Status in imagemagick package in Debian: New Bug description: Impact == I'm proposing to drop the ImageMagick app from the default Ubuntu 17.10. It is visible in the Show Applications view of the Activities Overview so this could impact screenshots. Justification = imagemagick is a collection of commandline utilities for working with images, photos, etc. It is a required dependency for many things and will still be installed by default. Bundled with imagemagick is the "display" app, which is an app with an unusual, difficult-to-use UI. It was not intentionally included in the default Ubuntu install but was only there because it was packaged together. I am proposing splitting the display app to a separate binary package so that it is available for install for the few who do want to use the app. I tried proposing this to Debian. See comment #60 on the attached Debian bug but the Debian maintainer doesn't seem interested in accepting my proposal any time soon. (I emailed him directly a few months ago too.) List Notifications == https://lists.ubuntu.com/archives/ubuntu-doc/2017-September/020534.html https://lists.ubuntu.com/archives/ubuntu-translators/2017-September/007403.html Other Info == I will be attaching a patch for review by the Desktop Team here soon. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/1717951/+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 1292041] Re: Lockscreen doesn't turn off the screen
Maybe lock screen should always happen before the screen turns off? Or, anytime lock screen happens it should also turn off the monitors? Is there any work around that I can apply? My cron job trick no longer works: https://unix.stackexchange.com/questions/505488/ubuntu-16-04-5-ruining-monitors-by-never-turning-them-off -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-screensaver in Ubuntu. https://bugs.launchpad.net/bugs/1292041 Title: Lockscreen doesn't turn off the screen Status in OEM Priority Project: Fix Released Status in OEM Priority Project trusty series: Fix Released Status in Unity: Fix Released Status in gnome-screensaver package in Ubuntu: Invalid Status in unity package in Ubuntu: Fix Released Bug description: [ATTENTION] This bug report is strictly for lockscreen. When user activates lockscreen with Ctrl+Alt+L or Super+L shortcut or from indicator-session the screen should blank off after a couple seconds. The new Unity lock screen doesn't turn off the monitor screen. I can wait as long as 10 minutes after activating the lock screen and the monitor still doesn't turn off. Then when I unlock the screen and don't use mouse or keyboard monitor will turn off (it's about 5 seconds after unlocking). To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1292041/+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 1292041] Re: Lockscreen doesn't turn off the screen
Please open this bug back up. It is not fixed! All monitors go off initially, but as soon as the lock-screen happens, my laptop's built-in monitor comes back on and stays on forever. This is an expensive 4K monitor and this bug is burning it up. The only work-around I've found is to turn off screen-lock, which is not acceptable from a security perspective. Please help! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-screensaver in Ubuntu. https://bugs.launchpad.net/bugs/1292041 Title: Lockscreen doesn't turn off the screen Status in OEM Priority Project: Fix Released Status in OEM Priority Project trusty series: Fix Released Status in Unity: Fix Released Status in gnome-screensaver package in Ubuntu: Invalid Status in unity package in Ubuntu: Fix Released Bug description: [ATTENTION] This bug report is strictly for lockscreen. When user activates lockscreen with Ctrl+Alt+L or Super+L shortcut or from indicator-session the screen should blank off after a couple seconds. The new Unity lock screen doesn't turn off the monitor screen. I can wait as long as 10 minutes after activating the lock screen and the monitor still doesn't turn off. Then when I unlock the screen and don't use mouse or keyboard monitor will turn off (it's about 5 seconds after unlocking). To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1292041/+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 1814133] Re: update to openjdk 11 in 18.04 LTS
I have tested jabref (3.8.2+ds-12~18.04) from bionic-proposed. It cannot open Options → Preferences. Here is the terminal output after selecting Options → Preferences: ~$ jabref [warning] /usr/bin/jabref: Unable to locate mariadb-java-client in /usr/share/java [warning] /usr/bin/jabref: Unable to locate postgresql in /usr/share/java 17:32:50.639 [AWT-EventQueue-0] WARN net.sf.jabref.JabRefGUI - There seem to be problems with OpenJDK and the default GTK Look Using Metal L instead. Change to another L with caution. 17:32:50.722 [AWT-EventQueue-0] INFO net.sf.jabref.logic.importer.OpenDatabase - Opening: /home/amr/Documents/Masterarbeit/Literature/Bibliography.bib 17:33:02.714 [AWT-EventQueue-0] ERROR net.sf.jabref.FallbackExceptionHandler - Uncaught exception Occurred in Thread[AWT-EventQueue-0,6,main] java.lang.NoClassDefFoundError: com/sun/java/swing/plaf/windows/WindowsLookAndFeel at java.lang.ClassLoader.defineClass1(Native Method) ~[?:?] at java.lang.ClassLoader.defineClass(ClassLoader.java:1016) ~[?:?] at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:174) ~[?:?] at jdk.internal.loader.BuiltinClassLoader.defineClass(BuiltinClassLoader.java:802) ~[?:?] at jdk.internal.loader.BuiltinClassLoader.findClassOnClassPathOrNull(BuiltinClassLoader.java:700) ~[?:?] at jdk.internal.loader.BuiltinClassLoader.loadClassOrNull(BuiltinClassLoader.java:623) ~[?:?] at jdk.internal.loader.BuiltinClassLoader.loadClass(BuiltinClassLoader.java:581) ~[?:?] at jdk.internal.loader.ClassLoaders$AppClassLoader.loadClass(ClassLoaders.java:178) ~[?:?] at java.lang.ClassLoader.loadClass(ClassLoader.java:521) ~[?:?] at java.lang.Class.forName0(Native Method) ~[?:?] at java.lang.Class.forName(Class.java:315) ~[?:?] at net.sf.jabref.gui.preftabs.AppearancePrefsTab$LookAndFeel.getAvailableLookAndFeels(AppearancePrefsTab.java:64) ~[JabRef-3.8.2.jar:?] at net.sf.jabref.gui.preftabs.AppearancePrefsTab.(AppearancePrefsTab.java:104) ~[JabRef-3.8.2.jar:?] at net.sf.jabref.gui.preftabs.PreferencesDialog.(PreferencesDialog.java:91) ~[JabRef-3.8.2.jar:?] at net.sf.jabref.gui.JabRefFrame.showPreferencesDialog(JabRefFrame.java:740) ~[JabRef-3.8.2.jar:?] at net.sf.jabref.gui.JabRefFrame$ShowPrefsAction.actionPerformed(JabRefFrame.java:1788) ~[JabRef-3.8.2.jar:?] at javax.swing.AbstractButton.fireActionPerformed(AbstractButton.java:1967) ~[?:?] at javax.swing.AbstractButton$Handler.actionPerformed(AbstractButton.java:2308) ~[?:?] at javax.swing.DefaultButtonModel.fireActionPerformed(DefaultButtonModel.java:405) ~[?:?] at javax.swing.DefaultButtonModel.setPressed(DefaultButtonModel.java:262) ~[?:?] at javax.swing.AbstractButton.doClick(AbstractButton.java:369) ~[?:?] at javax.swing.plaf.basic.BasicMenuItemUI.doClick(BasicMenuItemUI.java:1020) ~[?:?] at javax.swing.plaf.basic.BasicMenuItemUI$Handler.mouseReleased(BasicMenuItemUI.java:1064) ~[?:?] at java.awt.AWTEventMulticaster.mouseReleased(AWTEventMulticaster.java:297) ~[?:?] at java.awt.Component.processMouseEvent(Component.java:6632) ~[?:?] at javax.swing.JComponent.processMouseEvent(JComponent.java:3342) ~[?:?] at java.awt.Component.processEvent(Component.java:6397) ~[?:?] at java.awt.Container.processEvent(Container.java:2263) ~[?:?] at java.awt.Component.dispatchEventImpl(Component.java:5008) ~[?:?] at java.awt.Container.dispatchEventImpl(Container.java:2321) ~[?:?] at java.awt.Component.dispatchEvent(Component.java:4840) ~[?:?] at java.awt.LightweightDispatcher.retargetMouseEvent(Container.java:4918) ~[?:?] at java.awt.LightweightDispatcher.processMouseEvent(Container.java:4547) ~[?:?] at java.awt.LightweightDispatcher.dispatchEvent(Container.java:4488) ~[?:?] at java.awt.Container.dispatchEventImpl(Container.java:2307) ~[?:?] at java.awt.Window.dispatchEventImpl(Window.java:2772) ~[?:?] at java.awt.Component.dispatchEvent(Component.java:4840) ~[?:?] at java.awt.EventQueue.dispatchEventImpl(EventQueue.java:772) ~[?:?] at java.awt.EventQueue$4.run(EventQueue.java:721) ~[?:?] at java.awt.EventQueue$4.run(EventQueue.java:715) ~[?:?] at java.security.AccessController.doPrivileged(Native Method) ~[?:?] at java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(ProtectionDomain.java:85) ~[?:?] at java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(ProtectionDomain.java:95) ~[?:?] at java.awt.EventQueue$5.run(EventQueue.java:745) ~[?:?] at java.awt.EventQueue$5.run(EventQueue.java:743) ~[?:?] at java.security.AccessController.doPrivileged(Native Method) ~[?:?] at
[Desktop-packages] [Bug 1440381] Re: please build bindings for Python3
This bug was fixed in the package samba - 2:4.10.0~rc4+dfsg-0ubuntu1
---
samba (2:4.10.0~rc4+dfsg-0ubuntu1) disco; urgency=medium
* New upstream version 4.10.0rc4 (LP: #1818518):
- Removed patches already applied upstream:
+ d/p/nsswitch-Add-try_authtok-option-to-pam_winbind.patch
+ d/p/s3-auth-ignore-create_builtin_guests-failing-without.patch
- d/p/add-so-version-to-private-libraries: refreshed to remove fuzz
- d/control: Updated build dependencies:
+ tdb >= 1.3.17
+ talloc >= 2.1.15
+ tevent >= 0.9.38
+ ldb >= 1.5.3
- d/samba-common.docs: README is now README.md
- d/libsmbclient.symbols: update symbols for this version
- d/libwbclient0.symbols: update symbols for this version
- d/ctdb.install: new binary ctdb_local_daemons
- d/samba-dev.install: use globbing for the header files with
exceptions for wbclient.h and libsmbclient.h, which belong in
other packages.
- d/rules: fix globbing used to move the dckeytab python module to the
samba package, and add a comment explaining why this is being done.
* Switch to python3:
- d/rules: calculate the ldb version using python3, and drop the
"really" bit since the real 1.5.x series is being used now.
- d/rules: make sure python3 is used for the build
- d/rules: adjust globbing to remove the python3 version of tevent.so
- d/rules: drop PYVERS, unused
- d/control: adjust dependencies (build and runtime) for python3
- d/python3-samba.install, d/control: new python3-samba package
(LP: #1440381)
- d/control, d/python-samba.install: get rid of python-samba, which is py2
- d/python3-samba.lintian-overrides: use the same overrides we had for
python-samba, now deleted.
- d/samba-dev.install, d/samba-libs.install: update file list
- d/t/control, d/t/python-smoke: use python3
- d/control: use ${python3:Depends} now instead of the python 2
counterpart for samba and samba-common-bin.
* d/control: drop suggests for python-gpgme, it's no longer available.
-- Andreas Hasenack Sat, 09 Mar 2019 12:45:25
+
** Changed in: samba (Ubuntu)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to tdb in Ubuntu.
https://bugs.launchpad.net/bugs/1440381
Title:
please build bindings for Python3
Status in ldb package in Ubuntu:
Fix Released
Status in samba package in Ubuntu:
Fix Released
Status in talloc package in Ubuntu:
Fix Released
Status in tdb package in Ubuntu:
Fix Released
Status in samba package in Debian:
New
Bug description:
There is still the goal to remove Python2 from the desktop images, and
to use Python3 only. please build bindings for Python3
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ldb/+bug/1440381/+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 1589401] Re: cannot view wifi networks after re-enabling wifi
** Information type changed from Public to Public Security -- 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/1589401 Title: cannot view wifi networks after re-enabling wifi Status in NetworkManager: Confirmed Status in network-manager package in Ubuntu: Confirmed Bug description: after re enabling wifi, up-down arrows just like wired network. cannot see any wifi ssid. To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1589401/+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 1440381] Re: please build bindings for Python3
This bug was fixed in the package ldb - 2:1.5.4-0ubuntu1
---
ldb (2:1.5.4-0ubuntu1) disco; urgency=medium
* New upstream version: 1.5.4 (LP: #1818525):
- d/libldb1.symbols: update for this version
- d/p/00_Enable-make-test-even-without-lmdb.patch: refreshed
- Removed patches, applied upstream:
+ d/p/03_EBADE
+ d/p/CVE-2019-3824-*.patch
- d/control: bump build-deps:
+ require talloc >= 2.1.16
+ require tdb >= 1.3.18
+ require tevent >= 0.9.39
- d/libldb1.install: added libldb-tdb-{err-map,int}.so
* d/rules: use Makefile targets instead of direct WAF calls
* Add python3 packages (LP: #1440381):
- d/control: add python3 packages
- d/rules: clean extra paths in the clean target
- d/python3-ldb*.install: install files for the new python3 packages.
- d/control, d/python3-ldb-dev.install, d/rules: use dh-exec and
install the python header file in a version-dependent include dir.
- d/python3-ldb.symbols.*: add per-architecture symbols files
- d/rules: dh_makeshlibs for python3-ldb
- d/rules: exclude "ldb." from symbols check/generation, as to match
the python3 extension name.
- d/rules: fix tevent globbing used in its removal
* d/control, d/python-ldb*, d/rules: drop python2 packages and support
-- Andreas Hasenack Fri, 08 Mar 2019 16:41:11
+
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to tdb in Ubuntu.
https://bugs.launchpad.net/bugs/1440381
Title:
please build bindings for Python3
Status in ldb package in Ubuntu:
Fix Released
Status in samba package in Ubuntu:
Fix Released
Status in talloc package in Ubuntu:
Fix Released
Status in tdb package in Ubuntu:
Fix Released
Status in samba package in Debian:
New
Bug description:
There is still the goal to remove Python2 from the desktop images, and
to use Python3 only. please build bindings for Python3
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ldb/+bug/1440381/+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 1440381] Re: please build bindings for Python3
This bug was fixed in the package talloc - 2.1.16-0ubuntu1
---
talloc (2.1.16-0ubuntu1) disco; urgency=medium
* New upstream version: 2.1.16 (LP: #1818522):
- d/rules: cleanup more directories and pyc files waf is leaving behind
- d/rules: fix globbing for talloc static library creation
- d/libtalloc2.symbols: updated symbols for 2.1.16
- d/control, d/rules, d/python3-talloc{,-dev}.install: new python3 packages
(LP: #1440381)
- d/s/lintian-overrides: change old PY2 variable override to the PY3
one we are using.
- d/python3-talloc.symbols.{common,amd64,armhf,arm64,s390x,ppc64el,
i386}: use per-arch symbols file
- d/rules: check python3-talloc symbols
- d/rules: remove change to keep python2 from desktop images, no longer
needed
- d/control, d/python-talloc*, d/rules: remove python2 packages
-- Andreas Hasenack Sat, 09 Mar 2019 16:40:52
+
** Changed in: talloc (Ubuntu)
Status: In Progress => Fix Released
** Changed in: ldb (Ubuntu)
Status: In Progress => Fix Released
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2019-3824
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to tdb in Ubuntu.
https://bugs.launchpad.net/bugs/1440381
Title:
please build bindings for Python3
Status in ldb package in Ubuntu:
Fix Released
Status in samba package in Ubuntu:
Fix Released
Status in talloc package in Ubuntu:
Fix Released
Status in tdb package in Ubuntu:
Fix Released
Status in samba package in Debian:
New
Bug description:
There is still the goal to remove Python2 from the desktop images, and
to use Python3 only. please build bindings for Python3
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ldb/+bug/1440381/+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 1717951] Re: UIFe: Drop imagemagick-display from the default install
Hmm. I upgraded to Disco today and the icon is back. Is that expected? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/1717951 Title: UIFe: Drop imagemagick-display from the default install Status in ubuntu-settings package in Ubuntu: Fix Released Status in imagemagick package in Debian: New Bug description: Impact == I'm proposing to drop the ImageMagick app from the default Ubuntu 17.10. It is visible in the Show Applications view of the Activities Overview so this could impact screenshots. Justification = imagemagick is a collection of commandline utilities for working with images, photos, etc. It is a required dependency for many things and will still be installed by default. Bundled with imagemagick is the "display" app, which is an app with an unusual, difficult-to-use UI. It was not intentionally included in the default Ubuntu install but was only there because it was packaged together. I am proposing splitting the display app to a separate binary package so that it is available for install for the few who do want to use the app. I tried proposing this to Debian. See comment #60 on the attached Debian bug but the Debian maintainer doesn't seem interested in accepting my proposal any time soon. (I emailed him directly a few months ago too.) List Notifications == https://lists.ubuntu.com/archives/ubuntu-doc/2017-September/020534.html https://lists.ubuntu.com/archives/ubuntu-translators/2017-September/007403.html Other Info == I will be attaching a patch for review by the Desktop Team here soon. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/1717951/+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 1778011] Re: SRU: PRIME Power Saving mode draws too much power
With kernel 4.18 and 410.104 drivers, it seems to work properly for me. Ubuntu 18.04.2 LTS on a Dell Inspiron Gaming 7000 with nvidia GeForce GTX 1050 Ti, Gnome. I am here because a couple patches ago, I lost ability to resume from sleep. Opening the lid, it would just hang in black screen, requiring hold of power button +5 sec to turn off. I tried the blacklist-nouveau and bbswitch-dkms tricks, no difference. On top of that configuration, I upgraded to kernel 4.18, still no difference. I found a repo for drivers > 390, http://ppa.launchpad.net/graphics- drivers/ppa/ubuntu I reverted previous changes, uninstalled bbswitch-dkms, and eventually got drivers, libs and nvidia-* packages for version 410.104 installed properly. Fixed. I can once again close the lid, the laptop sleeps; open the lid, the laptop wakes and gives the beaver login screen. Awesome. Thanks Alberto and other devs for your work. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-prime in Ubuntu. https://bugs.launchpad.net/bugs/1778011 Title: SRU: PRIME Power Saving mode draws too much power Status in HWE Next: New Status in gdm3 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-390 package in Ubuntu: Fix Released Status in nvidia-prime package in Ubuntu: Fix Released Status in nvidia-settings package in Ubuntu: Fix Released Status in sddm package in Ubuntu: Confirmed Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in gdm3 source package in Bionic: Fix Released Status in nvidia-graphics-drivers-390 source package in Bionic: Fix Released Status in nvidia-prime source package in Bionic: Fix Released Status in nvidia-settings source package in Bionic: Fix Released Status in sddm source package in Bionic: Confirmed Status in ubuntu-drivers-common source package in Bionic: Fix Released Bug description: SRU Request: [Impact] Relying on the nouveau driver and on the vga switcheroo (to get around a change in systemd LP: #1777099) caused increased power consumption, and slowed down the switching process. Furthermore, if the main X/Xwayland session was started by Gdm when the nvidia driver was loaded, the session will keep the nvidia module loaded, and prevent the system from switching off the dGPU. Also, the nouveau driver will be loaded, if nvidia is not, and this can cause problems to unsupported NVIDIA GPUs. The solution involves the following changes: 1) Solving the problem in systemd (LP: #1777099) 2) Adding code in gpu-manager and in nvidia-prime to unload the nvidia modules, and to allow the PCI device to sleep. 3) Making a slight change to the current patch in Gdm, used to call the PRIME scripts before and after a Gdm session (so that gpu-manager gets actually called on log out) 4) Adding code in gpu-manager to kill the main X/Xwayland session on log out, if the session is preventing us from unloading the nvidia driver. A new X/Xwayland session will be created after unload the module. 5) Removing the systemd service that loads nouveau from the nvidia packages. [Test Case] 1) Enable the -proposed repository, and install the new "ubuntu-drivers-common", nvidia drivers, nvidia-prime, and gdm3 * 2) Make sure the nvidia packages are installed, and enable performance mode (if it is already enabled, call "sudo prime-select intel" first): sudo prime-select nvidia 3) Restart your computer and attach your /var/log/gpu-manager.log. see if the system boots correctly. If unsure, please attach your /var/log /gpu-manager.log and /var/log/Xorg.0.log 4) Select power saving mode: sudo prime-select intel 5) Log out and log back in 6) Check if the nvidia driver is still loaded: lsmod | grep nvidia [Regression Potential] Low, as hybrid graphics support does not work correctly, and the changes only affect this use case. _ * Steps to test the updates: 1) Enable the bionic-proposed repositories 2) Create /etc/apt/preferences.d/proposed-updates with the following content: Package: * Pin: release a=bionic-proposed Pin-Priority: 400 3) Update the list of packages: sudo apt-get update 4) Install the packages from -proposed using the following command: sudo apt install nvidia-driver-390/bionic-proposed gdm3/bionic- proposed ubuntu-drivers-common/bionic-proposed nvidia-prime/bionic- proposed nvidia-settings/bionic-proposed libnvidia-gl-390/bionic- proposed libnvidia-compute-390/bionic-proposed libnvidia-decode-390 /bionic-proposed libnvidia-encode-390/bionic-proposed libnvidia- ifr1-390/bionic-proposed libnvidia-fbc1-390/bionic-proposed To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1778011/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net
[Desktop-packages] [Bug 1795774] Re: gnome-shell crashed with SIGSEGV in cogl_texture_get_height(texture=0x0) from clutter_offscreen_effect_real_paint_target() from clutter_offscreen_effect_paint_text
Verification succeeded. Problem solved ** Tags removed: verification-needed-bionic ** Tags added: verification-done-bionic -- 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/1795774 Title: gnome-shell crashed with SIGSEGV in cogl_texture_get_height(texture=0x0) from clutter_offscreen_effect_real_paint_target() from clutter_offscreen_effect_paint_texture() from clutter_offscreen_effect_paint() from clutter_actor_continue_paint() Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Bionic: Fix Committed Status in mutter source package in Cosmic: Fix Released Bug description: [ Impact ] Gnome shell crashes on cogl_texture_get_height [ Test case ] No clear reproducer is know for such issue, crashes should be monitored in e.u.c checking that this is not happening anymore for the version in proposed. [ Regression potential ] Low, the proposed fix is part of the current stable branch upstream and not changed in further revisions. -- The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 3.30.0-1ubuntu2, the problem page at https://errors.ubuntu.com/problem/e5b2dcb04552882a76f1daa6b9f18ba864269d26 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/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1795774/+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 1790525] Re: gnome-shell assert failure: double free or corruption (fasttop) in g_free() from g_error_free() from cogl_error_free() from cogl_texture_new_with_size() from clutt
Verification succeeded. Problem solved. ** Tags removed: verification-needed-bionic ** Tags added: verification-done-bionic -- 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/1790525 Title: gnome-shell assert failure: double free or corruption (fasttop) in g_free() from g_error_free() from cogl_error_free() from cogl_texture_new_with_size() from clutter_offscreen_effect_real_create_texture() Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Bionic: Fix Committed Status in mutter source package in Cosmic: Fix Released Bug description: [ Impact ] Gnome shell crashes on double free Problem is occurring if dual monitor is used. Second monitor is repeatingly blank and activated again. At the bottom it probably contains the upper part of the first monitor. I had the same problem at 18.04 when using gdm3 without wayland during logon. [ Test case ] - Run gnome-shell with multimonitor - No flashing should happen on gdm initialization Also we should monitor crashes in e.u.c [ Regression potential ] Low, the proposed fix is part of the current stable branch upstream and not changed in further revisions. -- ProblemType: CrashDistroRelease: Ubuntu 18.10 Package: gnome-shell 3.29.90-2ubuntu1 ProcVersionSignature: Ubuntu 4.17.0-9.10-generic 4.17.17 Uname: Linux 4.17.0-9-generic i686 ApportVersion: 2.20.10-0ubuntu9 Architecture: i386 AssertionMessage: double free or corruption (fasttop) CurrentDesktop: ubuntu:GNOME Date: Mon Sep 3 21:02:58 2018 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell GsettingsChanges: b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" ProcCmdline: /usr/bin/gnome-shell ProcEnviron: LANGUAGE=en_US:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash Signal: 6SourcePackage: gnome-shell StacktraceTop: __libc_signal_restore_set (set=0xbfcd5e9c) at ../sysdeps/unix/sysv/linux/nptl-signals.h:80 __GI_raise (sig=6) at ../sysdeps/unix/sysv/linux/raise.c:48 __GI_abort () at abort.c:79 __libc_message (action=do_abort, fmt=) at ../sysdeps/posix/libc_fatal.c:181 malloc_printerr (str=str@entry=0xb6b437e8 "double free or corruption (fasttop)") at malloc.c:5350 Title: gnome-shell assert failure: double free or corruption (fasttop) UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1790525/+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 1021375] Re: Nautilus says the USB stick is read only when it is not
After a recent update to my Ubuntu 16.04 LTS, this error pops in. The solution was to use the similar "killall nautilus" and it fixes it. -- 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/1021375 Title: Nautilus says the USB stick is read only when it is not Status in Nautilus: Unknown Status in nautilus package in Ubuntu: Confirmed Status in nemo package in Ubuntu: Confirmed Status in thunar package in Ubuntu: Confirmed Bug description: First time I use an USB drive since I updated to 12.04 and I found a really annoying bug on Nautilus. Nautilus claims that the destination drive is read-only when in fact it is not. How to reproduce: 1. Connect a USB stick drive to your competer. 2. The USB will appear in the desktop. 3. Open two Nautilus windows one in your home folder, other in the USB stick drive. 4. Select any file from your home folder (small enough to fit the free space in the USB drive) 5. Drag the file and drop it in the USB drive window. -- Nautilus will say that it cannot copy the file because the destination is read ony -- If you try the copy the same file with the terminal you will see that the file is copied without problem, other programs like gedit or LibreOffice can write in the usb stick drive just fine. It is not a problem with the USB stick, as shown here: [ 6232.288064] usb 2-1: new high-speed USB device number 6 using ehci_hcd [ 6232.426378] scsi8 : usb-storage 2-1:1.0 [ 6233.468489] scsi 8:0:0:0: Direct-Access Kingston DT 101 IIPMAP PQ: 0 ANSI: 0 CCS [ 6233.469862] sd 8:0:0:0: Attached scsi generic sg2 type 0 [ 6234.178262] sd 8:0:0:0: [sdb] 3909632 512-byte logical blocks: (2.00 GB/1.86 GiB) [ 6234.178735] sd 8:0:0:0: [sdb] Write Protect is off [ 6234.178740] sd 8:0:0:0: [sdb] Mode Sense: 23 00 00 00 [ 6234.179251] sd 8:0:0:0: [sdb] No Caching mode page present [ 6234.179256] sd 8:0:0:0: [sdb] Assuming drive cache: write through [ 6234.183369] sd 8:0:0:0: [sdb] No Caching mode page present [ 6234.183376] sd 8:0:0:0: [sdb] Assuming drive cache: write through [ 6234.210138] sdb: sdb1 [ 6234.212732] sd 8:0:0:0: [sdb] No Caching mode page present [ 6234.212736] sd 8:0:0:0: [sdb] Assuming drive cache: write through [ 6234.212740] sd 8:0:0:0: [sdb] Attached SCSI removable disk The permisions on the removable drive are set correctly: sergio@shana:/media$ ls -lah total 12K drwxr-xr-x 3 root root 4,0K jul 5 10:20 . drwxr-xr-x 23 root root 4,0K jul 3 11:01 .. drwx-- 5 sergio sergio 4,0K dic 31 1969 DESIGNPLUS There is enough free space in the drive: sergio@shana:/media/DESIGNPLUS$ df -h S.ficheros Tamaño Usado Disp Uso% Montado en /dev/sda2 50G 5,5G 42G 12% / udev 1,5G 4,0K 1,5G 1% /dev tmpfs579M 872K 579M 1% /run none 5,0M 0 5,0M 0% /run/lock none 1,5G 1,1M 1,5G 1% /run/shm /dev/sda1497M 113M 360M 24% /boot /dev/sda5245G 111G 122G 48% /home /dev/sdb11,9G 681M 1,2G 36% /media/DESIGNPLUS A file can be copied to the USB stick using the cp command for example. sergio@shana:~/Trash$ cp wireless.txt /media/DESIGNPLUS sergio@shana:~/Trash$ cd /media/DESIGNPLUS sergio@shana:/media/DESIGNPLUS$ ls -lah total 204K drwx-- 5 sergio sergio 4,0K jul 5 10:38 . drwxr-xr-x 3 root root 4,0K jul 5 10:20 .. -rw-r--r-- 1 sergio sergio 117K jul 5 10:14 ._Screen Shot 2012-06-30 at 8.50.37 AM.png -rw-r--r-- 1 sergio sergio 55K jun 30 08:51 Screen Shot 2012-06-30 at 8.50.37 AM.png drwx-- 4 sergio sergio 4,0K jul 5 10:05 .Spotlight-V100 drwx-- 2 sergio sergio 4,0K jul 5 10:05 .Trashes -rw-r--r-- 1 sergio sergio 4,0K jul 5 10:05 ._.Trashes -rw-r--r-- 1 sergio sergio 73 jul 5 10:38 wireless.txt But nautilus just dennies to copy the file claming that the destination is read only, when it is not. I tested it with two different USB sticks in two different computers running Ubuntu 12.04 and the same result. To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1021375/+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 1819077] Re: SRU Request: nvidia-340 340.107-0ubuntu0.16.04.1: nvidia-340 kernel module failed to build (nvidia_uvm_lite.c:857:14: error: initialization from incompatible point
** Changed in: nvidia-graphics-drivers-340 (Ubuntu) Status: New => Fix Released ** Changed in: nvidia-graphics-drivers-340 (Ubuntu) Importance: Undecided => High ** Changed in: nvidia-graphics-drivers-340 (Ubuntu Xenial) Status: In Progress => Fix Released ** Tags added: regression-proposed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/1819077 Title: SRU Request: nvidia-340 340.107-0ubuntu0.16.04.1: nvidia-340 kernel module failed to build (nvidia_uvm_lite.c:857:14: error: initialization from incompatible pointer type [-Werror=incompatible- pointer-types]) Status in nvidia-graphics-drivers-340 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-340 source package in Xenial: Fix Released Bug description: SRU Request: [Impact] nvidia-340 (from xenial-proposed) breaks compatibility with linux-generic-hwe-16.04. [Test Case] 1) Enable the -proposed repository, and install the new 340 NVIDIA driver (340.107-0ubuntu0.16.04.2). 2) Check that the kernel module can be built against the new kernel. 3) Restart your computer, and see if everything works correctly when accessing the desktop. [Regression Potential] Low. The update simply re-enables a patch that had been disabled in 340.107-0ubuntu0.16.04.1 _ ProblemType: Package DistroRelease: Ubuntu 16.04 Package: nvidia-340 340.107-0ubuntu0.16.04.1 ProcVersionSignature: Ubuntu 4.4.0-142.168-generic 4.4.167 Uname: Linux 4.4.0-142-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.104 Thu Sep 14 17:13:13 PDT 2017 GCC version: gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.11) ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 BootLog: root: clean, 221224/1281120 files, 2095043/512 blocks CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None DKMSKernelVersion: 4.15.0-46-generic Date: Fri Mar 8 01:23:53 2019 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu DkmsStatus: bbswitch, 0.8, 4.15.0-46-generic, x86_64: installed bbswitch, 0.8, 4.4.0-142-generic, x86_64: installed nvidia-340, 340.107, 4.4.0-142-generic, x86_64: installed DuplicateSignature: dkms:nvidia-340:340.107-0ubuntu0.16.04.1:/var/lib/dkms/nvidia-340/340.107/build/uvm/nvidia_uvm_lite.c:857:14: error: initialization from incompatible pointer type [-Werror=incompatible-pointer-types] GraphicsCard: NVIDIA Corporation G84GLM [Quadro FX 570M] [10de:040c] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company G84GLM [Quadro FX 570M] [103c:30c5] InstallationDate: Installed on 2015-11-21 (1202 days ago) InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) LightdmGreeterLogOld: ** Message: Starting lightdm-gtk-greeter 2.0.1 (Aug 7 2015, 01:24:18) ** Message: [Configuration] Reading file: /etc/lightdm/lightdm-gtk-greeter.conf.d/01_ubuntu.conf ** Message: [Configuration] Reading file: /etc/lightdm/lightdm-gtk-greeter.conf.d/30_xubuntu.conf ** Message: [Configuration] Reading file: /etc/lightdm/lightdm-gtk-greeter.conf upstart: indicator-application main process (970) killed by TERM signal PackageVersion: 340.107-0ubuntu0.16.04.1 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-142-generic root=UUID=bdc3be24-dee9-4ead-bca0-c9b1e45a87e5 ro persistent quiet splash RelatedPackageVersions: dpkg 1.18.4ubuntu1.5 apt 1.2.29ubuntu0.1 SourcePackage: nvidia-graphics-drivers-340 Title: nvidia-340 340.107-0ubuntu0.16.04.1: nvidia-340 kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2011 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68MVD Ver. F.20 dmi.board.name: 30C5 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 71.36 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68MVDVer.F.20:bd12/01/2011:svnHewlett-Packard:pn:pvrF.20:rvnHewlett-Packard:rn30C5:rvrKBCVersion71.36:cvnHewlett-Packard:ct10:cvr: dmi.product.version: F.20 dmi.sys.vendor: Hewlett-Packard modified.conffile..etc.modprobe.d.nvidia-340_hybrid.conf: [deleted] version.compiz: compiz N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.91-2~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1
[Desktop-packages] [Bug 1813268] Re: connection issues with Kopano IMAP servers
** Changed in: evolution-data-server (Ubuntu Cosmic) Importance: Undecided => Low -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evolution-data-server in Ubuntu. https://bugs.launchpad.net/bugs/1813268 Title: connection issues with Kopano IMAP servers Status in evolution-data-server package in Ubuntu: Fix Released Status in evolution-data-server source package in Cosmic: Fix Committed Bug description: * Impact Evolution doesn't work with Kopano IMAP servers: * Test case Configure an account on a Kopano IMAP server and try to use it from evolution * Regression potential The change is in the imap handling code so it would be good to test on a few different type of server that things still work correctly - 3.30.1-1 has the following issue with Kopano IMAP servers: Disable request of BODYSTRUCTURE when its response is broken https://gitlab.gnome.org/GNOME/evolution-data-server/issues/37 In 3.30.4-1 it's fixed, so a backport to cosmic would be great. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1813268/+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 1815882] Re: Update evolution-data-server to 3.30.5
** Changed in: evolution-data-server (Ubuntu Cosmic) Importance: Undecided => High ** Tags added: upgrade-software-version -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evolution-data-server in Ubuntu. https://bugs.launchpad.net/bugs/1815882 Title: Update evolution-data-server to 3.30.5 Status in evolution-data-server package in Ubuntu: Fix Released Status in evolution-data-server source package in Cosmic: Fix Committed Bug description: * Impact That's a new bug-fix only update from GNOME There is a micro-release exception for GNOME: https://wiki.ubuntu.com/StableReleaseUpdates#GNOME https://gitlab.gnome.org/GNOME/evolution-data-server/blob/gnome-3-30/NEWS https://gitlab.gnome.org/GNOME/evolution-data-server/commits/gnome-3-30 * Test Case After installing the update, restart your computer. Run several eds-using apps like Evolution, GNOME Calendar and verify that they continue to run at least as well as before this update. * Regression Potential It's a new version with a bug of changes and fixes including in imap, calendar and gpg signing code so those features need to be well tested. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1815882/+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
