[Desktop-packages] [Bug 1532508] Re: Screen contents revealed briefly on resume, before even unlocking
** Changed in: gnome-shell Status: Unknown => New -- 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/1532508 Title: Screen contents revealed briefly on resume, before even unlocking Status in GNOME Shell: New Status in Ubuntu GNOME: Confirmed Status in gdm3 package in Ubuntu: Confirmed Status in gnome-shell package in Ubuntu: Confirmed Status in unity package in Ubuntu: Fix Released Status in unity source package in Xenial: Fix Released Status in gnome-shell package in Debian: Confirmed Bug description: [Impact] When lock is enabled, the screen doesn't get blank/covered by lockscreen before suspending, thus on early resume the content might be shown. Video showing the bug: https://youtu.be/dDOgtK1MldI Reproduced on Ubuntu 2015.10, Ubuntu 2014.04 [Test case] 1. Work on highly secret files 2. Close the lid of your laptop and go have a break 3. Anyone who opens the lid of the laptop can see the secret files for a half second before the lock screen appears [Possible Regression] Content on screen isn't painted anymore and screen stays black. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1532508/+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 1576559] Re: Refused to switch profile to headset_head_unit: Not connected
I was read official pulseaudio gitlab bugs. Seems like bluetooth module problem. https://www.freedesktop.org/wiki/Software/PulseAudio/Documentation/User/Bluetooth/#index7h2 They recommend use separate usb bluetooth. -- 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/1576559 Title: Refused to switch profile to headset_head_unit: Not connected Status in pulseaudio package in Ubuntu: Confirmed Bug description: I'm trying to connect a bluetooth-speaker-with-microphone (Mi Bluetooth Speaker) to Ubuntu. It works well as an A2DP sync, but can't use it as a headset with microphone. The device doesn't list in the "Input Devices" by default, and using the sound settings to change the profile of the device to HSP/HFP results in this log message: W: [pulseaudio] module-bluez5-device.c: Refused to switch profile to headset_head_unit: Not connected I'm running Ubuntu 16.04 LTS. I did an upgrade from Ubuntu 15.10. pulseaudio: Installed: 1:8.0-0ubuntu3 bluez: Installed: 5.37-0ubuntu5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1576559/+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 1532508] Re: Screen contents revealed briefly on resume, before even unlocking
Watch existing bug on GNOME Gitlab. Previously, this was https://bugzilla.gnome.org/show_bug.cgi?id=753678 ** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/issues #332 https://gitlab.gnome.org/GNOME/gnome-shell/issues/332 ** Bug watch added: bugzilla.gnome.org/ #753678 https://bugzilla.gnome.org/show_bug.cgi?id=753678 ** Changed in: gnome-shell Importance: Medium => Unknown ** Changed in: gnome-shell Status: In Progress => Unknown ** Changed in: gnome-shell Remote watch: GNOME Bug Tracker #753678 => gitlab.gnome.org/GNOME/gnome-shell/issues #332 -- 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/1532508 Title: Screen contents revealed briefly on resume, before even unlocking Status in GNOME Shell: Unknown Status in Ubuntu GNOME: Confirmed Status in gdm3 package in Ubuntu: Confirmed Status in gnome-shell package in Ubuntu: Confirmed Status in unity package in Ubuntu: Fix Released Status in unity source package in Xenial: Fix Released Status in gnome-shell package in Debian: Confirmed Bug description: [Impact] When lock is enabled, the screen doesn't get blank/covered by lockscreen before suspending, thus on early resume the content might be shown. Video showing the bug: https://youtu.be/dDOgtK1MldI Reproduced on Ubuntu 2015.10, Ubuntu 2014.04 [Test case] 1. Work on highly secret files 2. Close the lid of your laptop and go have a break 3. Anyone who opens the lid of the laptop can see the secret files for a half second before the lock screen appears [Possible Regression] Content on screen isn't painted anymore and screen stays black. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1532508/+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 1849942] Re: 19.10 Gnome Settings and Tweak Tools Window Bar Bug
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-tweak-tool (Ubuntu) Status: New => Confirmed -- 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/1849942 Title: 19.10 Gnome Settings and Tweak Tools Window Bar Bug Status in gnome-control-center package in Ubuntu: Incomplete Status in gnome-tweak-tool package in Ubuntu: Confirmed Bug description: I upgraded from 19.04 to 19.10 and now there are some strange bugs with the Gnome Settings and the Tweak Tool: https://drive.google.com/file/d/1PpxTRKOqrrPfNLC_0fLSXNZTrsOIWDxg/view?usp=sharing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1849942/+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 1852890] Re: Nautilus freezes when trying to delete an item from the desktop
[Expired for nautilus (Ubuntu) because there has been no activity for 60 days.] ** Changed in: nautilus (Ubuntu) Status: Incomplete => Expired -- 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/1852890 Title: Nautilus freezes when trying to delete an item from the desktop Status in nautilus package in Ubuntu: Expired Bug description: When hitting the delete key on an item on the desktop, a beep is emitted, and nothing happens. When launching a separate Nautilus window, navigating to ~/Desktop, and trying to delete items from this folder, the Nautilus window freezes. At this point, no new Nautilus windows can be launched, and the window eventually emits a ""Files" is not responding" dialog. (When trying to reproduce this bug for this report, the whole screen froze and I had to escape with Alt+F2 - not sure if this is a separate bug). When launching nautilus from a terminal, and repeating the procedure above, no error message or other output is printed to the terminal. The file in question was steam.desktop, and I then deleted it using rm without any issue. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: nautilus 1:3.34.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7 Uname: Linux 5.3.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Nov 17 08:05:39 2019 GsettingsChanges: b'org.gnome.nautilus.compression' b'default-compression-format' b"'tar.xz'" b'org.gnome.nautilus.window-state' b'initial-size' b'(1245, 746)' b'org.gnome.nautilus.preferences' b'default-folder-viewer' b"'list-view'" b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 'type', 'owner', 'group', 'permissions', 'where', 'date_modified', 'date_modified_with_time', 'date_accessed', 'recency', 'starred', 'detailed_type']" InstallationDate: Installed on 2019-11-07 (9 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: dropbox 2019.02.14 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1852890/+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 1853126] Re: Go To Line... causes text cursor to disappear
[Expired for gedit (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gedit (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gedit in Ubuntu. https://bugs.launchpad.net/bugs/1853126 Title: Go To Line... causes text cursor to disappear Status in gedit package in Ubuntu: Expired Bug description: 1) I open an CMakeLists.txt (from llvm project) 2) cursor is in line 1 3) I Go To... 123 4) editor moves to some location, status shows Ln 123 Col 1 5) but cursor (keyboard's) is not visible (making me wonder *which* line on the screen is indeed 123?!) It is subtle GUI error. I never seen any editor make editing keyboard cursor disappear, which is why I thought to report it. I attached the screencast (the file is already open). gedit --version Version 3.28.1 gnome 3.28.2 Ubuntu 18.04.3 LTS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1853126/+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 1853117] Re: after update to 19.10 I am notified about new updates available even when there is none available
[Expired for gnome-software (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gnome-software (Ubuntu) Status: Incomplete => Expired -- 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/1853117 Title: after update to 19.10 I am notified about new updates available even when there is none available Status in gnome-software package in Ubuntu: Expired Bug description: after update to ubuntu 19.10 I am notified about new updates available even when there is none available. It happens on daily basis. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-software 3.30.6-2ubuntu10 ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7 Uname: Linux 5.3.0-23-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Nov 19 09:52:18 2019 ExecutablePath: /usr/bin/gnome-software InstallationDate: Installed on 2019-07-11 (130 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) InstalledPlugins: gnome-software-plugin-flatpak 3.30.6-2ubuntu10 gnome-software-plugin-snap3.30.6-2ubuntu10 SourcePackage: gnome-software UpgradeStatus: Upgraded to eoan on 2019-11-03 (15 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1853117/+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 1848841] Re: Chromium/Chrome looks tiny in hidpi after gnome shell restart
Done in https://bugs.chromium.org/p/chromium/issues/detail?id=1043494, should I also report this to Gnome Gitlab? Btw, the problem also happens with VSCode, which is not surprising given that it's an Electron based app. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1848841 Title: Chromium/Chrome looks tiny in hidpi after gnome shell restart Status in chromium-browser package in Ubuntu: New Bug description: My screen is 3000x2000. I use a scaling factor of 2x. Today I upgraded to 19.10 and chromium became a snap package. It launches at the right scaling factor, but if I restart gnome shell (Alt-F2 r) it rescales to 1x (I believe) and everything becomes absurdly tiny. Restarting chromium afterwards restores the right scaling factor. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: chromium-browser 77.0.3865.120-0ubuntu1~snap1 ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1 Uname: Linux 5.3.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DRM.card0-DP-1: enabled: disabled dpms: Off status: disconnected edid-base64: modes: DRM.card0-DP-2: enabled: disabled dpms: Off status: disconnected edid-base64: modes: DRM.card0-HDMI-A-1: enabled: disabled dpms: Off status: disconnected edid-base64: modes: DRM.card0-eDP-1: enabled: enabled dpms: On status: connected edid-base64: AP///wBRmIgTACobAQSlHRR4Asr8pFZPnicOT1UBAQEBAQEBAQEBAQEBAQEBuJi4oLDQPnAwIDUAJcQQAAAaAAAY/gBUSUFOTUEgWE0g/wBUTDEzOUdEWFAwMQAAAF8= modes: 3000x2000 Date: Sat Oct 19 05:11:37 2019 DiskUsage: Filesystem Type Size Used Avail Use% Mounted on /dev/nvme0n1p2 ext4 331G 62G 255G 20% / tmpfs tmpfs 7,8G 75M 7,7G 1% /dev/shm /dev/nvme0n1p2 ext4 331G 62G 255G 20% / InstallationDate: Installed on 2019-06-13 (127 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 05c8:03c0 Cheng Uei Precision Industry Co., Ltd (Foxlink) HD Camera Bus 001 Device 002: ID 8087:0a2b Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HUAWEI MACH-WX9 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-18-generic root=UUID=08b323c0-f1a9-46a9-8d2c-694dff8193f6 ro quiet splash vt.handoff=7 Snap.ChromeDriverVersion: ChromeDriver 77.0.3865.120 (416d6d8013e9adb6dd33b0c12e7614ff403d1a94-refs/branch-heads/3865@{#884}) Snap.ChromiumVersion: Chromium 77.0.3865.120 snap SourcePackage: chromium-browser UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/28/2018 dmi.bios.vendor: HUAWEI dmi.bios.version: 1.17 dmi.board.name: MACH-WX9-PCB dmi.board.vendor: HUAWEI dmi.board.version: M14 dmi.chassis.type: 10 dmi.chassis.vendor: HUAWEI dmi.chassis.version: M14 dmi.modalias: dmi:bvnHUAWEI:bvr1.17:bd07/28/2018:svnHUAWEI:pnMACH-WX9:pvrM14:rvnHUAWEI:rnMACH-WX9-PCB:rvrM14:cvnHUAWEI:ct10:cvrM14: dmi.product.family: HUAWEI MateBook X dmi.product.name: MACH-WX9 dmi.product.sku: C128 dmi.product.version: M14 dmi.sys.vendor: HUAWEI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1848841/+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 1860243] [NEW] wifi not detected. nm-applet error when trying to run
Public bug reported: There is a problem with this kernel I have reported this problem to Debian as well. The kernel is not able to load the firmware for the wifi hardware so the network managers are not detecting wifi at all. I tryed to run the nm-applet and got the following error: (nm-applet:30837): Gtk-WARNING **: 18:26:47.538: Can't set a parent on widget which has a parent The correct firmware files for my system are installed and in the correct place.When I run a dmesg command it gives the following error: 9.453407] b43-phy0: Broadcom 4312 WLAN found (core revision 15) [9.496761] b43-phy0: Found PHY: Analog 6, Type 5 (LP), Revision 1 [9.496777] b43-phy0: Found Radio: Manuf 0x17F, ID 0x2062, Revision 2, Version 0 [9.512936] b43 ssb0:0: Direct firmware load for b43/ucode15.fw failed with error -2 [9.512976] b43 ssb0:0: Direct firmware load for b43/ucode15.fw failed with error -2 [9.513063] b43 ssb0:0: Direct firmware load for b43-open/ucode15.fw failed with error -2 [9.513100] b43 ssb0:0: Direct firmware load for b43-open/ucode15.fw failed with error -2 [9.513104] b43-phy0 ERROR: Firmware file "b43/ucode15.fw" not found [9.513108] b43-phy0 ERROR: Firmware file "b43-open/ucode15.fw" not found [9.513111] b43-phy0 ERROR: You must go to http://wireless.kernel.org/en/users/Drivers/b43#devicefirmware and download the correct firmware for this driver version. Please carefully read all instructions on this website. [9.513200] Broadcom 43xx driver loaded [ Features: PNL ] ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: network-manager-gnome 1.8.22-2ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1 Uname: Linux 5.3.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: LXQt Date: Sat Jan 18 18:43:15 2020 InstallationDate: Installed on 2020-01-18 (0 days ago) InstallationMedia: Lubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017.1) IpRoute: default via 192.168.1.1 dev enp9s0 proto dhcp metric 100 192.168.1.0/24 dev enp9s0 proto kernel scope link src 192.168.1.16 metric 100 IwConfig: enp9s0no wireless extensions. lono wireless extensions. RfKill: SourcePackage: network-manager-applet UpgradeStatus: No upgrade log present (probably fresh install) nmcli-con: NAMEUUID TYPE TIMESTAMP TIMESTAMP-REAL AUTOCONNECT AUTOCONNECT-PRIORITY READONLY DBUS-PATH ACTIVE DEVICE STATE ACTIVE-PATH SLAVE FILENAME Wired connection 1 2951c15c-9995-3f31-915c-79716865ac23 ethernet 1579390965 Sat 18 Jan 2020 06:42:45 PM EST yes -999 no /org/freedesktop/NetworkManager/Settings/1 yes enp9s0 activated /org/freedesktop/NetworkManager/ActiveConnection/2 -- /run/NetworkManager/system-connections/Wired connection 1.nmconnection nmcli-dev: DEVICE TYPE STATE IP4-CONNECTIVITY IP6-CONNECTIVITY DBUS-PATH CONNECTION CON-UUID CON-PATH enp9s0 ethernet connected full full /org/freedesktop/NetworkManager/Devices/2 Wired connection 1 2951c15c-9995-3f31-915c-79716865ac23 /org/freedesktop/NetworkManager/ActiveConnection/2 lo loopback unmanaged unknown unknown /org/freedesktop/NetworkManager/Devices/1 -- -- -- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.20.4 connected started full enabled enabled enabled enabled enabled ** Affects: network-manager-applet (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-applet in Ubuntu. https://bugs.launchpad.net/bugs/1860243 Title: wifi not detected. nm-applet error when trying to run Status in network-manager-applet package in Ubuntu: New Bug description: There is a problem with this kernel I have reported this problem to Debian as well. The kernel is not able to load the firmware for the wifi hardware so the network managers are not detecting wifi at all. I tryed to run the nm-applet and got the following error: (nm-applet:30837): Gtk-WARNING **: 18:26:47.538: Can't set a parent on widget which has a parent The correct firmware files for my system are installed and in the correct place.When I run a dmesg command it gives the following error: 9.453407] b43-phy0: Broadcom 4312 WLAN found (core revision 15) [9.496761] b43-phy0: Found PHY: Analog 6, Type 5 (LP),
[Desktop-packages] [Bug 1860244] [NEW] Gdm3 - infinite login
Public bug reported: This is a strange issue that only appeared to happen after a failed resume from suspend state. Now each time I log in the is a flash of activity and I'm presented with the login screen again. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gdm3 3.34.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13 Uname: Linux 5.3.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 Date: Sun Jan 19 10:54:08 2020 InstallationDate: Installed on 2018-05-06 (622 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: TERM=linux PATH=(custom, no user) LANG=en_AU.UTF-8 SHELL=/bin/bash SourcePackage: gdm3 UpgradeStatus: Upgraded to eoan on 2019-10-27 (83 days ago) mtime.conffile..etc.gdm3.custom.conf: 2020-01-19T10:19:08.087127 ** Affects: gdm3 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1860244 Title: Gdm3 - infinite login Status in gdm3 package in Ubuntu: New Bug description: This is a strange issue that only appeared to happen after a failed resume from suspend state. Now each time I log in the is a flash of activity and I'm presented with the login screen again. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gdm3 3.34.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13 Uname: Linux 5.3.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 Date: Sun Jan 19 10:54:08 2020 InstallationDate: Installed on 2018-05-06 (622 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: TERM=linux PATH=(custom, no user) LANG=en_AU.UTF-8 SHELL=/bin/bash SourcePackage: gdm3 UpgradeStatus: Upgraded to eoan on 2019-10-27 (83 days ago) mtime.conffile..etc.gdm3.custom.conf: 2020-01-19T10:19:08.087127 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1860244/+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 1840725] Re: Microphone not working in Ubuntu 18.04.3 LTS on new hp-spectre-x360-convertible-15 laptop
I believe I'm having the same issue on a Dell 7591 15" 2-in-1 running Ubuntu 19.10. With no headset plugged in nothing shows up under Sound->Input. If I 1) plug in headset (select Headset in the pop-up) 2) Open Sound 3) Select Microphone Built-in Audio under Input 4) Select Headset Microphone under Built-in Audio...then input audio is picked up but is scratchy as OP mentioned. -- 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/1840725 Title: Microphone not working in Ubuntu 18.04.3 LTS on new hp- spectre-x360-convertible-15 laptop Status in alsa-driver package in Ubuntu: Confirmed Bug description: Internal Microphone does not work in Ubuntu 18.04.3 LTS in a new hp- spectre-x360-convertible-15 laptop. The microphone works perfectly on Windows 10 (present in Dual boot mode). Initially, Internal Microphone was not even detected but installing alsa-tools-gui and overriding pin 0x12 to the Internal Microphone fixed that issue. [Pin 0x13 does not work and causes static in a headphone if it is plugged in.] Microphone is not able to pick up any sound. I changed levels/settings in alsamixer, pavucontrol without any success: In alsamixer: Experimented with levels ranging from very low to very high for Internal Mic, Capture, etc. In pavucontrol: Set the Internal Mic as a fallback device, unlocked the channels for the mic, experimented with reducing the level for one of the channels (reduced right mic level to Silence while keeping the left mic level normal/high and vice versa). alsa-info: http://alsa-project.org/db/?f=cf6d3ccc6372f955da7d99df07afbcb31d5a6c7f arecord -l List of CAPTURE Hardware Devices card 0: PCH [HDA Intel PCH], device 0: ALC285 Analog [ALC285 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1840725/+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 1860235] Re: totem crashed with SIGSEGV in g_mount_spec_get()
** Changed in: totem Status: Unknown => New -- 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/1860235 Title: totem crashed with SIGSEGV in g_mount_spec_get() Status in Totem: New Status in totem package in Ubuntu: New Bug description: https://gitlab.gnome.org/GNOME/totem/issues/390 --- I don't know what happened. ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: totem 3.34.1-2ubuntu1 Uname: Linux 5.4.12-050412-generic x86_64 ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Jan 17 19:08:13 2020 ExecutablePath: /usr/bin/totem InstallationDate: Installed on 2018-12-02 (412 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcCmdline: /usr/bin/totem --gapplication-service ProcEnviron: SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, no user) LANGUAGE=es_CL:es LANG=es_CL.UTF-8 SegvAnalysis: Segfault happened at: 0x7ff6dc45dd09 : mov (%rbx),%rdi PC (0x7ff6dc45dd09) ok source "(%rbx)" (0x7000600070007) not located in a known VMA region (needed readable region)! destination "%rdi" ok Stack memory exhausted (SP below stack segment) SegvReason: reading unknown VMA Signal: 11 SourcePackage: totem StacktraceTop: g_mount_spec_get () at /usr/lib/x86_64-linux-gnu/gvfs/libgvfscommon.so () at /usr/lib/x86_64-linux-gnu/gio/modules/libgvfsdbus.so () at /usr/lib/x86_64-linux-gnu/gio/modules/libgvfsdbus.so () at /usr/lib/x86_64-linux-gnu/libtotem-plparser.so.18 () at /usr/lib/x86_64-linux-gnu/libtotem-plparser.so.18 Title: totem crashed with SIGSEGV in g_mount_spec_get() UpgradeStatus: Upgraded to focal on 2018-12-02 (412 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/totem/+bug/1860235/+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 1860235] Re: totem crashed with SIGSEGV in g_mount_spec_get()
https://gitlab.gnome.org/GNOME/totem/issues/390 ** Information type changed from Private to Public ** Bug watch added: gitlab.gnome.org/GNOME/totem/issues #390 https://gitlab.gnome.org/GNOME/totem/issues/390 ** Also affects: totem via https://gitlab.gnome.org/GNOME/totem/issues/390 Importance: Unknown Status: Unknown ** Description changed: + https://gitlab.gnome.org/GNOME/totem/issues/390 + + --- + I don't know what happened. ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: totem 3.34.1-2ubuntu1 Uname: Linux 5.4.12-050412-generic x86_64 ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Jan 17 19:08:13 2020 ExecutablePath: /usr/bin/totem InstallationDate: Installed on 2018-12-02 (412 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcCmdline: /usr/bin/totem --gapplication-service ProcEnviron: - SHELL=/bin/bash - XDG_RUNTIME_DIR= - PATH=(custom, no user) - LANGUAGE=es_CL:es - LANG=es_CL.UTF-8 + SHELL=/bin/bash + XDG_RUNTIME_DIR= + PATH=(custom, no user) + LANGUAGE=es_CL:es + LANG=es_CL.UTF-8 SegvAnalysis: - Segfault happened at: 0x7ff6dc45dd09 : mov (%rbx),%rdi - PC (0x7ff6dc45dd09) ok - source "(%rbx)" (0x7000600070007) not located in a known VMA region (needed readable region)! - destination "%rdi" ok - Stack memory exhausted (SP below stack segment) + Segfault happened at: 0x7ff6dc45dd09 : mov (%rbx),%rdi + PC (0x7ff6dc45dd09) ok + source "(%rbx)" (0x7000600070007) not located in a known VMA region (needed readable region)! + destination "%rdi" ok + Stack memory exhausted (SP below stack segment) SegvReason: reading unknown VMA Signal: 11 SourcePackage: totem StacktraceTop: - g_mount_spec_get () at /usr/lib/x86_64-linux-gnu/gvfs/libgvfscommon.so - () at /usr/lib/x86_64-linux-gnu/gio/modules/libgvfsdbus.so - () at /usr/lib/x86_64-linux-gnu/gio/modules/libgvfsdbus.so - () at /usr/lib/x86_64-linux-gnu/libtotem-plparser.so.18 - () at /usr/lib/x86_64-linux-gnu/libtotem-plparser.so.18 + g_mount_spec_get () at /usr/lib/x86_64-linux-gnu/gvfs/libgvfscommon.so + () at /usr/lib/x86_64-linux-gnu/gio/modules/libgvfsdbus.so + () at /usr/lib/x86_64-linux-gnu/gio/modules/libgvfsdbus.so + () at /usr/lib/x86_64-linux-gnu/libtotem-plparser.so.18 + () at /usr/lib/x86_64-linux-gnu/libtotem-plparser.so.18 Title: totem crashed with SIGSEGV in g_mount_spec_get() UpgradeStatus: Upgraded to focal on 2018-12-02 (412 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo separator: -- 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/1860235 Title: totem crashed with SIGSEGV in g_mount_spec_get() Status in Totem: New Status in totem package in Ubuntu: New Bug description: https://gitlab.gnome.org/GNOME/totem/issues/390 --- I don't know what happened. ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: totem 3.34.1-2ubuntu1 Uname: Linux 5.4.12-050412-generic x86_64 ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Jan 17 19:08:13 2020 ExecutablePath: /usr/bin/totem InstallationDate: Installed on 2018-12-02 (412 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcCmdline: /usr/bin/totem --gapplication-service ProcEnviron: SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, no user) LANGUAGE=es_CL:es LANG=es_CL.UTF-8 SegvAnalysis: Segfault happened at: 0x7ff6dc45dd09 : mov (%rbx),%rdi PC (0x7ff6dc45dd09) ok source "(%rbx)" (0x7000600070007) not located in a known VMA region (needed readable region)! destination "%rdi" ok Stack memory exhausted (SP below stack segment) SegvReason: reading unknown VMA Signal: 11 SourcePackage: totem StacktraceTop: g_mount_spec_get () at /usr/lib/x86_64-linux-gnu/gvfs/libgvfscommon.so () at /usr/lib/x86_64-linux-gnu/gio/modules/libgvfsdbus.so () at /usr/lib/x86_64-linux-gnu/gio/modules/libgvfsdbus.so () at /usr/lib/x86_64-linux-gnu/libtotem-plparser.so.18 () at /usr/lib/x86_64-linux-gnu/libtotem-plparser.so.18 Title: totem crashed with SIGSEGV in g_mount_spec_get() UpgradeStatus: Upgraded to focal on 2018-12-02 (412 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/totem/+bug/1860235/+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 1860230] Re: Resolution incorrect after updating kernel to 5.3
Bug also affects me: VGA compatible controller: NVIDIA Corporation GF106GL [Quadro 2000] (rev a1) I was running dual monitors. After reboot second monitor is not recognized. Primary monitor displays as 'Default'. Only one resolution setting is available I have Driver nvidia-driver-390 (proprietary tested) selected -- 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/1860230 Title: Resolution incorrect after updating kernel to 5.3 Status in xorg package in Ubuntu: Confirmed Bug description: Updated kernel from 5.0 to 5.3. After reboot, resolution appears to be something like 640 x 480. Accessed (with difficulty) display settings. Monitor is shown as unknown device. Tried reinstalling kernel, problem remains. Can still boot successfully into previous kernel. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.3.0-26.28~18.04.1-generic 5.3.13 Uname: Linux 5.3.0-26-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,staticswitcher,workarounds,scale,expo,ezoom,dbus] CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Jan 18 18:56:45 2020 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GconfCompiz: /apps/compiz-1/general: /apps/compiz-1/general/screen0: /apps/compiz-1/general/screen0/options: active_plugins = [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,staticswitcher,workarounds,scale,expo,ezoom,dbus] GraphicsCard: NVIDIA Corporation GK208B [GeForce GT 710] [10de:128b] (rev a1) (prog-if 00 [VGA controller]) Subsystem: eVga.com. Corp. GK208B [GeForce GT 710] [3842:2710] InstallationDate: Installed on 2018-08-02 (533 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Lsusb: Bus 001 Device 004: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 003: ID 050d:0234 Belkin Components F5U234 USB 2.0 4-Port Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 002: ID 046d:c316 Logitech, Inc. HID-Compliant Keyboard Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-26-generic root=UUID=b6d36306-de29-4163-9a21-ced3e7dfe6dc ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/19/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.60 dmi.board.name: N68C-S UCC dmi.board.vendor: ASRock 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.:bvrP1.60:bd09/19/2011:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnN68C-SUCC:rvr: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.sku: 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.99-1ubuntu1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.1-1ubuntu1~18.04.1 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1860230/+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 1767541] Re: Transparent background of calculator in ubuntu 18.04 using communitheme
I want to add further comment. I am not sure I have the authority to change the status from invalid to confirmed but it is clear several people are affected by this and this bug is also reported elsewhere where the transparent background is affecting gedit/text editor and system monitor. This bug is very old and needs to be addressed. In desperation I have found that going into gnome tweaks and changing appearance to something other than Ambience or Radiance fixes it but gives you a very stark working environment. I am using adwaita (default) and that works but hurts the eyes. Also noticeable is that in text editor and calculator (and maybe other affected programs) the 'X' button at the top right has a bell-like symbol superimposed on it when this workaround is used. ** Attachment added: "Settings that work for me" https://bugs.launchpad.net/ubuntu/+source/gnome-calculator/+bug/1767541/+attachment/5321429/+files/Screenshot%20from%202020-01-18%2015-39-12.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-calculator in Ubuntu. https://bugs.launchpad.net/bugs/1767541 Title: Transparent background of calculator in ubuntu 18.04 using communitheme Status in gnome-calculator package in Ubuntu: Confirmed Bug description: It also happen in system monitor ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-calculator (not installed) 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: communitheme:ubuntu:GNOME Date: Sat Apr 28 08:34:55 2018 InstallationDate: Installed on 2018-04-27 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_PH.UTF-8 SHELL=/bin/bash SourcePackage: gnome-calculator UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-calculator/+bug/1767541/+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 1767541] Re: Transparent background of calculator in ubuntu 18.04 using communitheme
This one shows the strange 'X' in Text Editor. ** Attachment added: "Seems to have a bell attached to the X" https://bugs.launchpad.net/ubuntu/+source/gnome-calculator/+bug/1767541/+attachment/5321430/+files/Screenshot%20from%202020-01-18%2015-39-50.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-calculator in Ubuntu. https://bugs.launchpad.net/bugs/1767541 Title: Transparent background of calculator in ubuntu 18.04 using communitheme Status in gnome-calculator package in Ubuntu: Confirmed Bug description: It also happen in system monitor ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-calculator (not installed) 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: communitheme:ubuntu:GNOME Date: Sat Apr 28 08:34:55 2018 InstallationDate: Installed on 2018-04-27 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_PH.UTF-8 SHELL=/bin/bash SourcePackage: gnome-calculator UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-calculator/+bug/1767541/+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 1860230] Re: Resolution incorrect after updating kernel to 5.3
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: xorg (Ubuntu) Status: New => Confirmed -- 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/1860230 Title: Resolution incorrect after updating kernel to 5.3 Status in xorg package in Ubuntu: Confirmed Bug description: Updated kernel from 5.0 to 5.3. After reboot, resolution appears to be something like 640 x 480. Accessed (with difficulty) display settings. Monitor is shown as unknown device. Tried reinstalling kernel, problem remains. Can still boot successfully into previous kernel. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.3.0-26.28~18.04.1-generic 5.3.13 Uname: Linux 5.3.0-26-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,staticswitcher,workarounds,scale,expo,ezoom,dbus] CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Jan 18 18:56:45 2020 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GconfCompiz: /apps/compiz-1/general: /apps/compiz-1/general/screen0: /apps/compiz-1/general/screen0/options: active_plugins = [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,staticswitcher,workarounds,scale,expo,ezoom,dbus] GraphicsCard: NVIDIA Corporation GK208B [GeForce GT 710] [10de:128b] (rev a1) (prog-if 00 [VGA controller]) Subsystem: eVga.com. Corp. GK208B [GeForce GT 710] [3842:2710] InstallationDate: Installed on 2018-08-02 (533 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Lsusb: Bus 001 Device 004: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 003: ID 050d:0234 Belkin Components F5U234 USB 2.0 4-Port Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 002: ID 046d:c316 Logitech, Inc. HID-Compliant Keyboard Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-26-generic root=UUID=b6d36306-de29-4163-9a21-ced3e7dfe6dc ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/19/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.60 dmi.board.name: N68C-S UCC dmi.board.vendor: ASRock 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.:bvrP1.60:bd09/19/2011:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnN68C-SUCC:rvr: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.sku: 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.99-1ubuntu1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.1-1ubuntu1~18.04.1 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1860230/+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 1859390] Re: Blurred texts, icons and character typed on login screen after logout or switching user
It happened again. So, I should expect that ocassionally it will happen again till to be fixed. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1859390 Title: Blurred texts, icons and character typed on login screen after logout or switching user Status in lightdm package in Ubuntu: New Bug description: I login to my account normally. But, when I click on "switch user" from app indicator, the clock in login screen will be completely blurred, impossible even to perceive it is a clock/time, except if I wait one minute so that the last number will update and it will show correctly (only the last number). If I press enter or click-up, I see the login form with the same problem: I can see that there are two users but they are completely indistinguishable and blurred. If I click on it, I can type my password but still blurred, even the chars I type are blurred. The app indicator icons are blurred too, but when I put the cursor over them, instantly they are fixed. PS: I have two enabled monitors and two users, but the second user is not logged in. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: lightdm (not installed) ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3 Uname: Linux 5.4.0-9-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Jan 13 00:13:45 2020 InstallationDate: Installed on 2019-12-31 (13 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20191230) SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1859390/+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 1767541] Re: Transparent background of calculator in ubuntu 18.04 using communitheme
** Changed in: gnome-calculator (Ubuntu) Status: Invalid => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-calculator in Ubuntu. https://bugs.launchpad.net/bugs/1767541 Title: Transparent background of calculator in ubuntu 18.04 using communitheme Status in gnome-calculator package in Ubuntu: Confirmed Bug description: It also happen in system monitor ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-calculator (not installed) 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: communitheme:ubuntu:GNOME Date: Sat Apr 28 08:34:55 2018 InstallationDate: Installed on 2018-04-27 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_PH.UTF-8 SHELL=/bin/bash SourcePackage: gnome-calculator UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-calculator/+bug/1767541/+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 1851007] Re: Login option 'GNOME + Remmina' not working
Problem disappeared after recent update -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to remmina in Ubuntu. https://bugs.launchpad.net/bugs/1851007 Title: Login option 'GNOME + Remmina' not working Status in remmina package in Ubuntu: Confirmed Bug description: Selecting Login option 'GNOME + Remmina' I'm just returned to login panel with no message. corrado@corrado-p13-ff-1101:~$ inxi -Fx System:Host: corrado-p13-ff-1101 Kernel: 5.3.0-18-generic x86_64 bits: 64 compiler: gcc v: 9.2.1 Desktop: Gnome 3.34.1 Distro: Ubuntu 20.04 LTS (Focal Fossa) Machine: Type: Desktop Mobo: ASRock model: H110M-G/M.2 serial: UEFI: American Megatrends v: P1.10 date: 05/11/2017 CPU: Topology: Dual Core model: Intel Core i3-7100 bits: 64 type: MT MCP arch: Kaby Lake rev: 9 L2 cache: 3072 KiB flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 31199 Speed: 800 MHz min/max: 800/3900 MHz Core speeds (MHz): 1: 800 2: 800 3: 801 4: 800 Graphics: Device-1: Intel HD Graphics 630 vendor: ASRock driver: i915 v: kernel bus ID: 00:02.0 Display: wayland server: X.Org 1.20.5 driver: i915 resolution: 1920x1080~60Hz OpenGL: renderer: Mesa DRI Intel HD Graphics 630 (Kaby Lake GT2) v: 4.5 Mesa 19.2.1 direct render: Yes Audio: Device-1: Intel 100 Series/C230 Series Family HD Audio vendor: ASRock driver: snd_hda_intel v: kernel bus ID: 00:1f.3 Sound Server: ALSA v: k5.3.0-18-generic Network: Device-1: Intel Ethernet I219-V vendor: ASRock driver: e1000e v: 3.2.6-k port: f040 bus ID: 00:1f.6 IF: enp0s31f6 state: up speed: 100 Mbps duplex: full mac: 70:85:c2:44:7b:86 Drives:Local Storage: total: 931.51 GiB used: 5.30 GiB (0.6%) ID-1: /dev/sda vendor: Toshiba model: DT01ACA100 size: 931.51 GiB Partition: ID-1: / size: 15.62 GiB used: 5.30 GiB (33.9%) fs: ext4 dev: /dev/sda13 ID-2: swap-1 size: 8.00 GiB used: 0 KiB (0.0%) fs: swap dev: /dev/sda2 Sensors: System Temperatures: cpu: 37.5 C mobo: N/A Fan Speeds (RPM): N/A Info: Processes: 197 Uptime: 7m Memory: 7.49 GiB used: 1.00 GiB (13.4%) Init: systemd runlevel: 5 Compilers: gcc: 9.2.1 Shell: bash v: 5.0.3 inxi: 3.0.36 corrado@corrado-p13-ff-1101:~$ ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1 Uname: Linux 5.3.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu9 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Nov 2 08:17:56 2019 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation HD Graphics 630 [8086:5912] (rev 04) (prog-if 00 [VGA controller]) Subsystem: ASRock Incorporation HD Graphics 630 [1849:5912] InstallationDate: Installed on 2019-11-01 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20191101) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 046d:c016 Logitech, Inc. Optical Wheel Mouse Bus 001 Device 002: ID 058f:6377 Alcor Micro Corp. AU6375 4-LUN card reader Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-18-generic root=UUID=062c7ec4-2948-49df-934f-d054f397e4c4 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/11/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.10 dmi.board.name: H110M-G/M.2 dmi.board.vendor: ASRock 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.:bvrP1.10:bd05/11/2017:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH110M-G/M.2:rvr: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.sku: 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 N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
[Desktop-packages] [Bug 1860230] Re: Resolution incorrect after updating kernel to 5.3
** Package changed: ubuntu => xorg (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1860230 Title: Resolution incorrect after updating kernel to 5.3 Status in xorg package in Ubuntu: New Bug description: Updated kernel from 5.0 to 5.3. After reboot, resolution appears to be something like 640 x 480. Accessed (with difficulty) display settings. Monitor is shown as unknown device. Tried reinstalling kernel, problem remains. Can still boot successfully into previous kernel. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.3.0-26.28~18.04.1-generic 5.3.13 Uname: Linux 5.3.0-26-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,staticswitcher,workarounds,scale,expo,ezoom,dbus] CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Jan 18 18:56:45 2020 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GconfCompiz: /apps/compiz-1/general: /apps/compiz-1/general/screen0: /apps/compiz-1/general/screen0/options: active_plugins = [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,staticswitcher,workarounds,scale,expo,ezoom,dbus] GraphicsCard: NVIDIA Corporation GK208B [GeForce GT 710] [10de:128b] (rev a1) (prog-if 00 [VGA controller]) Subsystem: eVga.com. Corp. GK208B [GeForce GT 710] [3842:2710] InstallationDate: Installed on 2018-08-02 (533 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Lsusb: Bus 001 Device 004: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 003: ID 050d:0234 Belkin Components F5U234 USB 2.0 4-Port Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 002: ID 046d:c316 Logitech, Inc. HID-Compliant Keyboard Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-26-generic root=UUID=b6d36306-de29-4163-9a21-ced3e7dfe6dc ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/19/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.60 dmi.board.name: N68C-S UCC dmi.board.vendor: ASRock 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.:bvrP1.60:bd09/19/2011:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnN68C-SUCC:rvr: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.sku: 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.99-1ubuntu1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.1-1ubuntu1~18.04.1 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1860230/+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 1767541] Re: Transparent background of calculator in ubuntu 18.04 using communitheme
I had already reported this for transparent background in gedit and in some windows on other programs (gramps), but I noticed that Calculator is also showing the transparent background and that led me to this bug. This bug is broader than Calculator by far including system monitor. All I see as responses are work-arounds when what is required is a software update on Ubuntu 18.04 itself. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-calculator in Ubuntu. https://bugs.launchpad.net/bugs/1767541 Title: Transparent background of calculator in ubuntu 18.04 using communitheme Status in gnome-calculator package in Ubuntu: Invalid Bug description: It also happen in system monitor ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-calculator (not installed) 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: communitheme:ubuntu:GNOME Date: Sat Apr 28 08:34:55 2018 InstallationDate: Installed on 2018-04-27 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_PH.UTF-8 SHELL=/bin/bash SourcePackage: gnome-calculator UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-calculator/+bug/1767541/+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 1860230] [NEW] Resolution incorrect after updating kernel to 5.3
You have been subscribed to a public bug: Updated kernel from 5.0 to 5.3. After reboot, resolution appears to be something like 640 x 480. Accessed (with difficulty) display settings. Monitor is shown as unknown device. Tried reinstalling kernel, problem remains. Can still boot successfully into previous kernel. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.3.0-26.28~18.04.1-generic 5.3.13 Uname: Linux 5.3.0-26-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,staticswitcher,workarounds,scale,expo,ezoom,dbus] CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Jan 18 18:56:45 2020 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GconfCompiz: /apps/compiz-1/general: /apps/compiz-1/general/screen0: /apps/compiz-1/general/screen0/options: active_plugins = [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,staticswitcher,workarounds,scale,expo,ezoom,dbus] GraphicsCard: NVIDIA Corporation GK208B [GeForce GT 710] [10de:128b] (rev a1) (prog-if 00 [VGA controller]) Subsystem: eVga.com. Corp. GK208B [GeForce GT 710] [3842:2710] InstallationDate: Installed on 2018-08-02 (533 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Lsusb: Bus 001 Device 004: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 003: ID 050d:0234 Belkin Components F5U234 USB 2.0 4-Port Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 002: ID 046d:c316 Logitech, Inc. HID-Compliant Keyboard Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-26-generic root=UUID=b6d36306-de29-4163-9a21-ced3e7dfe6dc ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/19/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.60 dmi.board.name: N68C-S UCC dmi.board.vendor: ASRock 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.:bvrP1.60:bd09/19/2011:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnN68C-SUCC:rvr: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.sku: 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.99-1ubuntu1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.1-1ubuntu1~18.04.1 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic resolution third-party-packages ubuntu -- Resolution incorrect after updating kernel to 5.3 https://bugs.launchpad.net/bugs/1860230 You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg 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 1794213] Re: Crash on Upgrade preparation from 18.04 to 18.10 in APT::Update::Post-Invoke-Success
This is resolved in `appstream >= 0.12.7` (since the code doesn't exist there anymore). The original issue was likely caused by AppStream not handling broken metadata correctly, which is an area that has also been improved greatly. ** Changed in: appstream (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to appstream in Ubuntu. https://bugs.launchpad.net/bugs/1794213 Title: Crash on Upgrade preparation from 18.04 to 18.10 in APT::Update::Post- Invoke-Success Status in appstream package in Ubuntu: Fix Released Bug description: E:Problem executing scripts APT::Update::Post-Invoke-Success 'if /usr/bin/test -w /var/cache/app-info -a -e /usr/bin/appstreamcli; then appstreamcli refresh-cache > /dev/null; fi', E:Sub-process returned an error code The above error is in the small box. The information below is in the terminal window that I thought might give clues on what happened on disto upgrade to 18.10 from command line. QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-root' kdeinit5: Got EXEC_NEW '/usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/kio/http.so' from launcher. kdeinit5: preparing to launch '/usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/kio/http.so' QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-root' kdeinit5: Got EXT_EXEC '/usr/bin/firefox' from launcher. kdeinit5: preparing to launch '/usr/bin/firefox' kdeinit5: PID 5799 terminated. (appstreamcli:6926): GLib-CRITICAL **: 21:59:50.626: g_variant_builder_end: assertion '!GVSB(builder)->uniform_item_types || GVSB(builder)->prev_item_type != NULL || g_variant_type_is_definite (GVSB(builder)->type)' failed (appstreamcli:6926): GLib-CRITICAL **: 21:59:50.626: g_variant_new_variant: assertion 'value != NULL' failed (appstreamcli:6926): GLib-ERROR **: 21:59:50.626: g_variant_new_parsed: 11-13:invalid GVariant format string Trace/breakpoint trap (core dumped) QXcbConnection: XCB error: 3 (BadWindow), sequence: 792, resource id: 39845978, major code: 40 (TranslateCoords), minor code: 0 (appstreamcli:8091): GLib-CRITICAL **: 22:00:11.961: g_variant_builder_end: assertion '!GVSB(builder)->uniform_item_types || GVSB(builder)->prev_item_type != NULL || g_variant_type_is_definite (GVSB(builder)->type)' failed (appstreamcli:8091): GLib-CRITICAL **: 22:00:11.961: g_variant_new_variant: assertion 'value != NULL' failed (appstreamcli:8091): GLib-ERROR **: 22:00:11.961: g_variant_new_parsed: 11-13:invalid GVariant format string Trace/breakpoint trap (core dumped) (appstreamcli:8899): GLib-CRITICAL **: 22:00:17.376: g_variant_builder_end: assertion '!GVSB(builder)->uniform_item_types || GVSB(builder)->prev_item_type != NULL || g_variant_type_is_definite (GVSB(builder)->type)' failed (appstreamcli:8899): GLib-CRITICAL **: 22:00:17.376: g_variant_new_variant: assertion 'value != NULL' failed (appstreamcli:8899): GLib-ERROR **: 22:00:17.376: g_variant_new_parsed: 11-13:invalid GVariant format string Trace/breakpoint trap (core dumped) (appstreamcli:9701): GLib-CRITICAL **: 22:00:21.530: g_variant_builder_end: assertion '!GVSB(builder)->uniform_item_types || GVSB(builder)->prev_item_type != NULL || g_variant_type_is_definite (GVSB(builder)->type)' failed (appstreamcli:9701): GLib-CRITICAL **: 22:00:21.530: g_variant_new_variant: assertion 'value != NULL' failed (appstreamcli:9701): GLib-ERROR **: 22:00:21.530: g_variant_new_parsed: 11-13:invalid GVariant format string Trace/breakpoint trap (core dumped) kdeinit5: PID 6868 terminated. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/appstream/+bug/1794213/+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 1848387] Re: dpkg error when triggers are activated
This is resolved in appstream >= 0.12.10-1 ** Changed in: appstream (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to appstream in Ubuntu. https://bugs.launchpad.net/bugs/1848387 Title: dpkg error when triggers are activated Status in appstream package in Ubuntu: Fix Released Bug description: The following message, or something like it, is output when an update to appstream is done on 19.10: dpkg: error: version '/usr/share/app-info/yaml /usr/share/app-info/icons' has ba d syntax: version string has embedded spaces This appears to be caused by this line in the appstream.postinst: if dpkg --compare-versions "$2" ge-nl "0.12.8"; then This gets called when the registered triggers are activated: interest-noawait /usr/share/app-info/icons interest-noawait /usr/share/app-info/yaml interest-noawait /usr/share/app-info/xml I recommend checking in the postinst if we are handling a trigger and avoiding the dpkg version comparison To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/appstream/+bug/1848387/+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 1796437] Re: X11 crashed when attempting to open Budgie and MATE Welcome
I found the real reason for the crashes. The problematic package is the `gstreamer1.0-vaapi` (see https://packages.ubuntu.com/focal/gstreamer1.0-vaapi). It is a dependency of `ubuntu-restricted-addons` (see https://packages.ubuntu.com/focal/ubuntu-restricted-addons). So ubuntu-mate-welcome and for example Cheese may be fixed by removing this package with ``` sudo apt-get purge gstreamer1.0-vaapi sudo apt-get autoremove --purge # to remove libgstreamer-plugins-bad1.0-0 (is not a problem) ``` So please carefully analyze the crash dumps for errors in `gstreamer1.0-vaapi` and fix this package. -- 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/1796437 Title: X11 crashed when attempting to open Budgie and MATE Welcome Status in gstreamer-vaapi package in Ubuntu: New Status in linux package in Ubuntu: Invalid Status in ubuntu-mate-meta package in Ubuntu: Invalid Status in ubuntu-mate-welcome package in Ubuntu: Invalid Status in xorg-server package in Ubuntu: Won't Fix Bug description: Went to the menu button in upper left corner. Attempted to open Budgie Welcome and the X11 session crashed. About 4 lines of error code were displayed for a few seconds then the login screen appeared. Description: Ubuntu Cosmic Cuttlefish (development branch) Release: 18.10 budgie-welcome: Installed: (none) Candidate: 0.6.1 Version table: 0.6.1 500 500 http://us.archive.ubuntu.com/ubuntu cosmic/universe amd64 Packages 500 http://us.archive.ubuntu.com/ubuntu cosmic/universe i386 Packages Seems to not be installed on a fresh install. So solved but needs fixing? ProblemType: Crash DistroRelease: Ubuntu 18.10 Package: xserver-xorg-core 2:1.20.1-3ubuntu2 ProcVersionSignature: Ubuntu 4.18.0-8.9-generic 4.18.7 Uname: Linux 4.18.0-8-generic x86_64 ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 AssertionMessage: Xorg: ../../../../../../include/privates.h:121: dixGetPrivateAddr: Assertion `key->initialized' failed. BootLog: [[0;32m OK [0m] Stopped Snappy daemon. Starting Snappy daemon... CompositorRunning: None CrashCounter: 1 Date: Fri Oct 5 20:36:30 2018 DistUpgraded: Fresh install DistroCodename: cosmic DistroVariant: ubuntu ExecutablePath: /usr/lib/xorg/Xorg ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GP102 [GeForce GTX 1080 Ti] [10de:1b06] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GP102 [GeForce GTX 1080 Ti] [1043:85e4] InstallationDate: Installed on 2018-10-06 (0 days ago) InstallationMedia: Ubuntu-Budgie 18.10 "Cosmic Cuttlefish" - Beta amd64 (20181005) MachineType: System manufacturer System Product Name ProcCmdline: /usr/lib/xorg/Xorg -core :0 -seat seat0 -auth /var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch ProcEnviron: PATH=(custom, no user) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-8-generic root=UUID=21545d40-8bcb-45b5-b710-8521590b95a5 ro quiet splash vt.handoff=1 Signal: 6 SourcePackage: xorg-server StacktraceTop: __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50 __GI_abort () at abort.c:79 __assert_fail_base (fmt=0x7f29afb85858 "%s%s%s:%u: %s%sAssertion `%s' failed.\n%n", assertion=0x55c50dca64bb "key->initialized", file=0x55c50dcaa9b0 "../../../../../../include/privates.h", line=121, function=) at assert.c:92 __GI___assert_fail (assertion=0x55c50dca64bb "key->initialized", file=0x55c50dcaa9b0 "../../../../../../include/privates.h", line=121, function=0x55c50dccc0c0 "dixGetPrivateAddr") at assert.c:101 ?? () Title: Xorg assert failure: Xorg: ../../../../../../include/privates.h:121: dixGetPrivateAddr: Assertion `key->initialized' failed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 03/14/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1301 dmi.board.asset.tag: Default string dmi.board.name: MAXIMUS IX FORMULA 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.:bvr1301:bd03/14/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnMAXIMUSIXFORMULA: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.94-1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.1-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2
[Desktop-packages] [Bug 1796437] Re: X11 crashed when attempting to open Budgie and MATE Welcome
** Changed in: ubuntu-mate-meta (Ubuntu) Status: Confirmed => Invalid ** Changed in: ubuntu-mate-welcome (Ubuntu) Status: Confirmed => Invalid ** Changed in: linux (Ubuntu) Status: Confirmed => Invalid ** Also affects: gstreamer-vaapi (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1796437 Title: X11 crashed when attempting to open Budgie and MATE Welcome Status in gstreamer-vaapi package in Ubuntu: New Status in linux package in Ubuntu: Invalid Status in ubuntu-mate-meta package in Ubuntu: Invalid Status in ubuntu-mate-welcome package in Ubuntu: Invalid Status in xorg-server package in Ubuntu: Won't Fix Bug description: Went to the menu button in upper left corner. Attempted to open Budgie Welcome and the X11 session crashed. About 4 lines of error code were displayed for a few seconds then the login screen appeared. Description: Ubuntu Cosmic Cuttlefish (development branch) Release: 18.10 budgie-welcome: Installed: (none) Candidate: 0.6.1 Version table: 0.6.1 500 500 http://us.archive.ubuntu.com/ubuntu cosmic/universe amd64 Packages 500 http://us.archive.ubuntu.com/ubuntu cosmic/universe i386 Packages Seems to not be installed on a fresh install. So solved but needs fixing? ProblemType: Crash DistroRelease: Ubuntu 18.10 Package: xserver-xorg-core 2:1.20.1-3ubuntu2 ProcVersionSignature: Ubuntu 4.18.0-8.9-generic 4.18.7 Uname: Linux 4.18.0-8-generic x86_64 ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 AssertionMessage: Xorg: ../../../../../../include/privates.h:121: dixGetPrivateAddr: Assertion `key->initialized' failed. BootLog: [[0;32m OK [0m] Stopped Snappy daemon. Starting Snappy daemon... CompositorRunning: None CrashCounter: 1 Date: Fri Oct 5 20:36:30 2018 DistUpgraded: Fresh install DistroCodename: cosmic DistroVariant: ubuntu ExecutablePath: /usr/lib/xorg/Xorg ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GP102 [GeForce GTX 1080 Ti] [10de:1b06] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GP102 [GeForce GTX 1080 Ti] [1043:85e4] InstallationDate: Installed on 2018-10-06 (0 days ago) InstallationMedia: Ubuntu-Budgie 18.10 "Cosmic Cuttlefish" - Beta amd64 (20181005) MachineType: System manufacturer System Product Name ProcCmdline: /usr/lib/xorg/Xorg -core :0 -seat seat0 -auth /var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch ProcEnviron: PATH=(custom, no user) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-8-generic root=UUID=21545d40-8bcb-45b5-b710-8521590b95a5 ro quiet splash vt.handoff=1 Signal: 6 SourcePackage: xorg-server StacktraceTop: __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50 __GI_abort () at abort.c:79 __assert_fail_base (fmt=0x7f29afb85858 "%s%s%s:%u: %s%sAssertion `%s' failed.\n%n", assertion=0x55c50dca64bb "key->initialized", file=0x55c50dcaa9b0 "../../../../../../include/privates.h", line=121, function=) at assert.c:92 __GI___assert_fail (assertion=0x55c50dca64bb "key->initialized", file=0x55c50dcaa9b0 "../../../../../../include/privates.h", line=121, function=0x55c50dccc0c0 "dixGetPrivateAddr") at assert.c:101 ?? () Title: Xorg assert failure: Xorg: ../../../../../../include/privates.h:121: dixGetPrivateAddr: Assertion `key->initialized' failed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 03/14/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1301 dmi.board.asset.tag: Default string dmi.board.name: MAXIMUS IX FORMULA 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.:bvr1301:bd03/14/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnMAXIMUSIXFORMULA: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.94-1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.1-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2 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-1build1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau
[Desktop-packages] [Bug 1796437] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1796437 Title: X11 crashed when attempting to open Budgie and MATE Welcome Status in linux package in Ubuntu: Confirmed Status in ubuntu-mate-meta package in Ubuntu: Confirmed Status in ubuntu-mate-welcome package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: Won't Fix Bug description: Went to the menu button in upper left corner. Attempted to open Budgie Welcome and the X11 session crashed. About 4 lines of error code were displayed for a few seconds then the login screen appeared. Description: Ubuntu Cosmic Cuttlefish (development branch) Release: 18.10 budgie-welcome: Installed: (none) Candidate: 0.6.1 Version table: 0.6.1 500 500 http://us.archive.ubuntu.com/ubuntu cosmic/universe amd64 Packages 500 http://us.archive.ubuntu.com/ubuntu cosmic/universe i386 Packages Seems to not be installed on a fresh install. So solved but needs fixing? ProblemType: Crash DistroRelease: Ubuntu 18.10 Package: xserver-xorg-core 2:1.20.1-3ubuntu2 ProcVersionSignature: Ubuntu 4.18.0-8.9-generic 4.18.7 Uname: Linux 4.18.0-8-generic x86_64 ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 AssertionMessage: Xorg: ../../../../../../include/privates.h:121: dixGetPrivateAddr: Assertion `key->initialized' failed. BootLog: [[0;32m OK [0m] Stopped Snappy daemon. Starting Snappy daemon... CompositorRunning: None CrashCounter: 1 Date: Fri Oct 5 20:36:30 2018 DistUpgraded: Fresh install DistroCodename: cosmic DistroVariant: ubuntu ExecutablePath: /usr/lib/xorg/Xorg ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GP102 [GeForce GTX 1080 Ti] [10de:1b06] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GP102 [GeForce GTX 1080 Ti] [1043:85e4] InstallationDate: Installed on 2018-10-06 (0 days ago) InstallationMedia: Ubuntu-Budgie 18.10 "Cosmic Cuttlefish" - Beta amd64 (20181005) MachineType: System manufacturer System Product Name ProcCmdline: /usr/lib/xorg/Xorg -core :0 -seat seat0 -auth /var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch ProcEnviron: PATH=(custom, no user) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-8-generic root=UUID=21545d40-8bcb-45b5-b710-8521590b95a5 ro quiet splash vt.handoff=1 Signal: 6 SourcePackage: xorg-server StacktraceTop: __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50 __GI_abort () at abort.c:79 __assert_fail_base (fmt=0x7f29afb85858 "%s%s%s:%u: %s%sAssertion `%s' failed.\n%n", assertion=0x55c50dca64bb "key->initialized", file=0x55c50dcaa9b0 "../../../../../../include/privates.h", line=121, function=) at assert.c:92 __GI___assert_fail (assertion=0x55c50dca64bb "key->initialized", file=0x55c50dcaa9b0 "../../../../../../include/privates.h", line=121, function=0x55c50dccc0c0 "dixGetPrivateAddr") at assert.c:101 ?? () Title: Xorg assert failure: Xorg: ../../../../../../include/privates.h:121: dixGetPrivateAddr: Assertion `key->initialized' failed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 03/14/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1301 dmi.board.asset.tag: Default string dmi.board.name: MAXIMUS IX FORMULA 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.:bvr1301:bd03/14/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnMAXIMUSIXFORMULA: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.94-1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.1-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2 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-1build1 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/linux/+bug/1796437/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe :
[Desktop-packages] [Bug 1859730] Re: [comet lake] Gnome freezes, icons missing, graphics corruption
Hi everyone, Thank you very much Daniel for your attention and recommendations but ..; 1. I installed ubuntu 20.04, everything started fine, but it failed again in the same way as in ubuntu 18, before this I was testing fedora 31 and the same errors were presented for both ubuntu 18, 20 and fedora 31, (screen crash, black screen with the message [2658.28 ...] systemd-journald [378]: failed to write entry (22 items, 749 bytes), ignoring: read-only file system). 2. Thinking that it may be a hardware error especially of the micron m2 SSD, contact dell technical service and just have an answer from them I will comment on it by this means. 3. I also cannot get the id of the .crash file, but when I select to report the error, an error window appears indicating the following: "The problem cannot be reported: It has some packages installed with obsolete versions bsdutils, libblkid1, libmount1, libsmartcols1, libuuid1, mount, utillinux, uuid-runtime " Any advice to fix those versions of the packages? Thank you very much to all! ** Attachment added: "crash.txt" https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1859730/+attachment/5321393/+files/crash.txt -- 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/1859730 Title: [comet lake] Gnome freezes, icons missing, graphics corruption Status in linux package in Ubuntu: Incomplete Status in mesa package in Ubuntu: Incomplete Bug description: ack please.. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 Uname: Linux 5.4.11-050411-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CompositorRunning: None Date: Tue Jan 14 20:17:26 2020 DistUpgraded: Fresh install DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20180608-47+beaver-three-eyed-raven+X92 DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: backport-iwlwifi, 8286, 4.15.0-1042-oem, x86_64: installed backport-iwlwifi, 8286, 4.15.0-1066-oem, x86_64: installed ExtraDebuggingInterest: Yes GpuHangFrequency: Very infrequently GraphicsCard: Intel Corporation Device [8086:9bca] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0962] InstallationDate: Installed on 2020-01-13 (1 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 Lsusb: Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 8087:0029 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 13 7390 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=es_CL.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.11-050411-generic root=UUID=8fd25548-00af-4395-92f0-5d7d27a54deb ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/25/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.4.0 dmi.board.name: 0377MH dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.4.0:bd11/25/2019:svnDellInc.:pnXPS137390:pvr:rvnDellInc.:rn0377MH:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 7390 dmi.product.sku: 0962 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~18.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.8-0ubuntu0~18.04.3 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1859730/+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 1796437] Re: X11 crashed when attempting to open Budgie and MATE Welcome
With virt-manager the crashes occur with Cirrus, QXL, VGA video drivers. But does not occur with VMVGA video driver. Possibly kernel (drm) issue. ** Also affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1796437 Title: X11 crashed when attempting to open Budgie and MATE Welcome Status in linux package in Ubuntu: New Status in ubuntu-mate-meta package in Ubuntu: Confirmed Status in ubuntu-mate-welcome package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: Won't Fix Bug description: Went to the menu button in upper left corner. Attempted to open Budgie Welcome and the X11 session crashed. About 4 lines of error code were displayed for a few seconds then the login screen appeared. Description: Ubuntu Cosmic Cuttlefish (development branch) Release: 18.10 budgie-welcome: Installed: (none) Candidate: 0.6.1 Version table: 0.6.1 500 500 http://us.archive.ubuntu.com/ubuntu cosmic/universe amd64 Packages 500 http://us.archive.ubuntu.com/ubuntu cosmic/universe i386 Packages Seems to not be installed on a fresh install. So solved but needs fixing? ProblemType: Crash DistroRelease: Ubuntu 18.10 Package: xserver-xorg-core 2:1.20.1-3ubuntu2 ProcVersionSignature: Ubuntu 4.18.0-8.9-generic 4.18.7 Uname: Linux 4.18.0-8-generic x86_64 ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 AssertionMessage: Xorg: ../../../../../../include/privates.h:121: dixGetPrivateAddr: Assertion `key->initialized' failed. BootLog: [[0;32m OK [0m] Stopped Snappy daemon. Starting Snappy daemon... CompositorRunning: None CrashCounter: 1 Date: Fri Oct 5 20:36:30 2018 DistUpgraded: Fresh install DistroCodename: cosmic DistroVariant: ubuntu ExecutablePath: /usr/lib/xorg/Xorg ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GP102 [GeForce GTX 1080 Ti] [10de:1b06] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GP102 [GeForce GTX 1080 Ti] [1043:85e4] InstallationDate: Installed on 2018-10-06 (0 days ago) InstallationMedia: Ubuntu-Budgie 18.10 "Cosmic Cuttlefish" - Beta amd64 (20181005) MachineType: System manufacturer System Product Name ProcCmdline: /usr/lib/xorg/Xorg -core :0 -seat seat0 -auth /var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch ProcEnviron: PATH=(custom, no user) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-8-generic root=UUID=21545d40-8bcb-45b5-b710-8521590b95a5 ro quiet splash vt.handoff=1 Signal: 6 SourcePackage: xorg-server StacktraceTop: __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50 __GI_abort () at abort.c:79 __assert_fail_base (fmt=0x7f29afb85858 "%s%s%s:%u: %s%sAssertion `%s' failed.\n%n", assertion=0x55c50dca64bb "key->initialized", file=0x55c50dcaa9b0 "../../../../../../include/privates.h", line=121, function=) at assert.c:92 __GI___assert_fail (assertion=0x55c50dca64bb "key->initialized", file=0x55c50dcaa9b0 "../../../../../../include/privates.h", line=121, function=0x55c50dccc0c0 "dixGetPrivateAddr") at assert.c:101 ?? () Title: Xorg assert failure: Xorg: ../../../../../../include/privates.h:121: dixGetPrivateAddr: Assertion `key->initialized' failed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 03/14/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1301 dmi.board.asset.tag: Default string dmi.board.name: MAXIMUS IX FORMULA 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.:bvr1301:bd03/14/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnMAXIMUSIXFORMULA: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.94-1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.1-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2 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-1build1 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/linux/+bug/1796437/+subscriptions --
[Desktop-packages] [Bug 1860042] Re: openCL application gives error after update
** Package changed: llvm-toolchain-9 (Ubuntu) => mesa (Ubuntu) -- 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/1860042 Title: openCL application gives error after update Status in mesa package in Ubuntu: New Bug description: My OpenCL program was working normally until a software update. The log file (/var/log/apt/history.log) contains: Start-Date: 2020-01-16 12:48:13 Commandline: aptdaemon role='role-commit-packages' sender=':1.131' Install: libllvm9:amd64 (1:9-2~ubuntu18.04.1, automatic), libclang-common-9-dev: amd64 (1:9-2~ubuntu18.04.1, automatic) Upgrade: libdrm-nouveau2:amd64 (2.4.97-1ubuntu1~18.04.1, 2.4.99-1ubuntu1~18.04.1 ), libclc-amdgcn:amd64 (0.2.0+git20190306-1~ubuntu18.04.1, 0.2.0+git20190827-1~u buntu18.04.1), libclc-dev:amd64 (0.2.0+git20190306-1~ubuntu18.04.1, 0.2.0+git201 90827-1~ubuntu18.04.1), libclc-r600:amd64 (0.2.0+git20190306-1~ubuntu18.04.1, 0. 2.0+git20190827-1~ubuntu18.04.1), libdrm-amdgpu1:amd64 (2.4.97-1ubuntu1~18.04.1, 2.4.99-1ubuntu1~18.04.1), libdrm2:amd64 (2.4.97-1ubuntu1~18.04.1, 2.4.99-1ubunt u1~18.04.1), libdrm-intel1:amd64 (2.4.97-1ubuntu1~18.04.1, 2.4.99-1ubuntu1~18.04 .1), libdrm-radeon1:amd64 (2.4.97-1ubuntu1~18.04.1, 2.4.99-1ubuntu1~18.04.1), li bdrm-dev:amd64 (2.4.97-1ubuntu1~18.04.1, 2.4.99-1ubuntu1~18.04.1), libdrm-common :amd64 (2.4.97-1ubuntu1~18.04.1, 2.4.99-1ubuntu1~18.04.1) End-Date: 2020-01-16 12:48:35 The program prints out: ac_rtld error: !s->is_rx LLVM failed to upload shader when clEnqueueNDRangeKernel is called. It could be in any one of the packages that were upgraded or installed. I chose libllvm9 because of the error message. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: libllvm9 1:9-2~ubuntu18.04.1 ProcVersionSignature: Ubuntu 4.15.0-74.84-lowlatency 4.15.18 Uname: Linux 4.15.0-74-lowlatency x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Jan 16 14:35:15 2020 InstallationDate: Installed on 2018-04-28 (628 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: llvm-toolchain-9 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1860042/+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 1860042] [NEW] openCL application gives error after update
You have been subscribed to a public bug: My OpenCL program was working normally until a software update. The log file (/var/log/apt/history.log) contains: Start-Date: 2020-01-16 12:48:13 Commandline: aptdaemon role='role-commit-packages' sender=':1.131' Install: libllvm9:amd64 (1:9-2~ubuntu18.04.1, automatic), libclang-common-9-dev: amd64 (1:9-2~ubuntu18.04.1, automatic) Upgrade: libdrm-nouveau2:amd64 (2.4.97-1ubuntu1~18.04.1, 2.4.99-1ubuntu1~18.04.1 ), libclc-amdgcn:amd64 (0.2.0+git20190306-1~ubuntu18.04.1, 0.2.0+git20190827-1~u buntu18.04.1), libclc-dev:amd64 (0.2.0+git20190306-1~ubuntu18.04.1, 0.2.0+git201 90827-1~ubuntu18.04.1), libclc-r600:amd64 (0.2.0+git20190306-1~ubuntu18.04.1, 0. 2.0+git20190827-1~ubuntu18.04.1), libdrm-amdgpu1:amd64 (2.4.97-1ubuntu1~18.04.1, 2.4.99-1ubuntu1~18.04.1), libdrm2:amd64 (2.4.97-1ubuntu1~18.04.1, 2.4.99-1ubunt u1~18.04.1), libdrm-intel1:amd64 (2.4.97-1ubuntu1~18.04.1, 2.4.99-1ubuntu1~18.04 .1), libdrm-radeon1:amd64 (2.4.97-1ubuntu1~18.04.1, 2.4.99-1ubuntu1~18.04.1), li bdrm-dev:amd64 (2.4.97-1ubuntu1~18.04.1, 2.4.99-1ubuntu1~18.04.1), libdrm-common :amd64 (2.4.97-1ubuntu1~18.04.1, 2.4.99-1ubuntu1~18.04.1) End-Date: 2020-01-16 12:48:35 The program prints out: ac_rtld error: !s->is_rx LLVM failed to upload shader when clEnqueueNDRangeKernel is called. It could be in any one of the packages that were upgraded or installed. I chose libllvm9 because of the error message. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: libllvm9 1:9-2~ubuntu18.04.1 ProcVersionSignature: Ubuntu 4.15.0-74.84-lowlatency 4.15.18 Uname: Linux 4.15.0-74-lowlatency x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Jan 16 14:35:15 2020 InstallationDate: Installed on 2018-04-28 (628 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: llvm-toolchain-9 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: mesa (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- openCL application gives error after update https://bugs.launchpad.net/bugs/1860042 You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa 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 1853199] Re: Ctrl + c (copy) anywhere some times crashes gnome session
attached the output ** Attachment added: "journal.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1853199/+attachment/5321345/+files/journal.txt -- 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/1853199 Title: Ctrl + c (copy) anywhere some times crashes gnome session Status in gnome-shell package in Ubuntu: Incomplete Bug description: Copy text anwyhere (browser, terminal) crashes user session and shows login screen. It may take few login attempts to actually login back. I have HDMI Tv attached to a Shuttle pc with Intel graphics. Box is always ON but tv is ON amd OFF as needed. Every time I turn tv ON and try to do something and use ctrl + c it would restart gnome session. After login it seem to work fine and ctrl+c does not break anything. Then the next day the similar thing happens. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7 Uname: Linux 5.3.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Nov 19 20:55:37 2019 DistUpgraded: 2019-10-26 19:58:25,451 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process “./xorg_fix_proprietary.py” (No such file or directory) (8)) DistroCodename: eoan DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 630 [8086:5912] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Holco Enterprise Co, Ltd/Shuttle Computer HD Graphics 630 [1297:4057] InstallationDate: Installed on 2019-07-21 (121 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 006: ID 05e3:0718 Genesys Logic, Inc. IDE/SATA Adapter Bus 001 Device 002: ID 413c:2107 Dell Computer Corp. Dell USB Entry Keyboard Bus 001 Device 003: ID 25a7:2402 2.4G 2.4G Wireless Device Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Shuttle Inc. XH270 ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-23-generic root=UUID=381b92c2-4c86-47ab-a37b-6e1f7a708bf7 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: Upgraded to eoan on 2019-10-26 (24 days ago) dmi.bios.date: 01/09/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.02 dmi.board.asset.tag: Default string dmi.board.name: FH270 dmi.board.vendor: Shuttle Inc. dmi.board.version: 1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.02:bd01/09/2018:svnShuttleInc.:pnXH270:pvr1.0:rvnShuttleInc.:rnFH270:rvr1.0:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: X dmi.product.name: XH270 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: Shuttle Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1853199/+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 991004] Re: Replace libusb-0.1 with libusb-compat-0.1
IMO this should be above "wishlist" importance, because the lcdproc project had to disable a lot of display drivers (such as hd44780-lcd2usb) still relying on libusb 0.1 API, while libusb- compat-0.1 probably would've solved their issues easily. An LCD that worked perfectly with Ubuntu 16.04 is now dead in 18.04. I fail to see why Debian maintainers are so worried about introducing some corner case bugs while things are breaking completely without the compatibility wrapper. Apparently it's just a matter of packaging libusb-compat-0.1 and making it conflict with libusb-0.1 so that only either one can be used. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libusb in Ubuntu. https://bugs.launchpad.net/bugs/991004 Title: Replace libusb-0.1 with libusb-compat-0.1 Status in libusb package in Ubuntu: Confirmed Status in libusb package in Debian: New Bug description: See http://www.libusb.org/wiki/libusb-compat-0.1 From http://www.libusb.org/: "However, if you have installed libusb-1.0 then we strongly recommend to use libusb-compat-0.1 instead of the ancient libusb-0.1 code, so that programs which use both the 0.1 API and the 1.0 API in different parts of the program, or in different libraries used by the program, will both end up using libusb-1.0 for actual device access. This is important to avoid potential conflicts between libusb-1.0 and libusb-0.1 being used by the same process." ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: libusb-0.1-4 2:0.1.12-20 ProcVersionSignature: Ubuntu 3.2.0-24.37-generic-pae 3.2.14 Uname: Linux 3.2.0-24-generic-pae i686 ApportVersion: 2.0.1-0ubuntu7 Architecture: i386 Date: Sun Apr 29 12:23:48 2012 EcryptfsInUse: Yes ProcEnviron: LANGUAGE=nb_NO:nb:no_NO:no:nn_NO:nn:en TERM=xterm PATH=(custom, user) LANG=nb_NO.UTF-8 SHELL=/bin/bash SourcePackage: libusb UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libusb/+bug/991004/+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 1850201] Re: Memory usage grows when locking/unlocking the screen
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-shell (Ubuntu) Status: New => Confirmed -- 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/1850201 Title: Memory usage grows when locking/unlocking the screen Status in gnome-shell package in Ubuntu: Confirmed Bug description: Many times after logging in gnome-shell uses 600-800MB of memory, and also slows down quite a bit (e.g., 20-30 seconds waiting for login). Only after multiple resets (Alt+F2 r) drops the memory usage below 200MB. I use my computer mainly for work, and the above phenomenon is quite disturbing. After a couple of hours of work memory usage is growing over 400MB again, and sometimes the reset (Alt+F2 r) doesn't help either. My system is Ubuntu 18.04.3 Gnome 3.28.2, but the newest Ubuntu also behaves similarly. This is an old issue, it was present in 18.04, 18.10, 19.04 and now in 19.10. I use three computers, and all of them suffer with this problem. Anyone can check this with the "gnome-shell memory monitor" gnome-shell extension. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.4-0ubuntu18.04.2 ProcVersionSignature: Ubuntu 5.0.0-32.34~18.04.2-generic 5.0.21 Uname: Linux 5.0.0-32-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CurrentDesktop: communitheme:ubuntu:GNOME Date: Mon Oct 28 20:28:38 2019 DisplayManager: gdm3 InstallationDate: Installed on 2019-01-04 (297 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/gnome-shell/+bug/1850201/+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 1439771] Re: wpa_supplicant[874]: dbus: Failed to construct signal after 'suspend'
dbus: failed to construct signal -- 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/1439771 Title: wpa_supplicant[874]: dbus: Failed to construct signal after 'suspend' Status in network-manager package in Ubuntu: Confirmed Bug description: The Wifi network can't connect after the wake up from suspend. Xubuntu 15.04 I'll post more useful details (journalctl log) as a comment to this bug report. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: dbus 1.8.12-1ubuntu5 Uname: Linux 4.0.0-04rc5-generic x86_64 ApportVersion: 2.17-0ubuntu1 Architecture: amd64 CurrentDesktop: XFCE Date: Thu Apr 2 18:18:56 2015 InstallationDate: Installed on 2015-03-27 (5 days ago) InstallationMedia: Xubuntu 15.04 "Vivid Vervet" - Beta amd64 (20150326) SourcePackage: dbus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1439771/+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
Re: [Desktop-packages] [Bug 1859515] Re: device no longer recognized after activating Tethering USB
Yes, I'm sure: I changed nothing on my device. Il 14/01/20 15:07, Sebastien Bacher ha scritto: > Thank you for your bug report. Can you try with the phone on another > computer/OS? Are you sure it's not a change on the phone side? > > ** Changed in: nautilus (Ubuntu) > Importance: Undecided => Low > > ** Changed in: nautilus (Ubuntu) > Status: New => Incomplete > -- 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/1859515 Title: device no longer recognized after activating Tethering USB Status in nautilus package in Ubuntu: Incomplete Bug description: I connect my Android device to the PC with a USB cable. It appears in the devices section in nautilus and I can read its data. If I activate Tethering USB on the device, I can use the internet connection but immediately the device being no longer available in nautilus, nemo, and every other program that read the smartphone data. If I deactivate USB tethering, the device reappear in the "devices" section. This problem weren't present in the 18.04 version... I'm using the same computer with the same USB cable with the same smartphone, so the problem is sure due to something other. The problem occurs only since when I installed Ubuntu 19.10, until some days ago with the 18.04 all was working fine. lsb_release -rd: Description: Ubuntu 19.10 Release: 19.10 apt-cache policy nautilus: nautilus: Installed: 1:3.34.1-1ubuntu1 Candidate: 1:3.34.1-1ubuntu1 Version table: *** 1:3.34.1-1ubuntu1 500 500 http://it.archive.ubuntu.com/ubuntu eoan/main amd64 Packages 100 /var/lib/dpkg/status apt-cache policy nemo: nemo: Installed: 4.0.6-1 Candidate: 4.0.6-1 Version table: *** 4.0.6-1 500 500 http://it.archive.ubuntu.com/ubuntu eoan/universe amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: nautilus 1:3.34.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13 Uname: Linux 5.3.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Jan 13 20:14:02 2020 GsettingsChanges: b'org.gnome.nautilus.window-state' b'maximized' b'true' b'org.gnome.nautilus.preferences' b'default-folder-viewer' b"'list-view'" b'org.gnome.nautilus.list-view' b'default-zoom-level' b"'small'" b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 'type', 'owner', 'group', 'permissions', 'where', 'date_modified', 'date_modified_with_time', 'date_accessed', 'recency', 'starred', 'detailed_type']" InstallationDate: Installed on 2020-01-09 (4 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash 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/1859515/+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 1856366] Re: PCI/internal sound card not detected on a Swift SF314-57
A Fedora user reported the same issue in https://bugzilla.redhat.com/show_bug.cgi?id=1772498#c16, and the created an upstream GitHub issue https://github.com/thesofproject/sof/issues/2126. Please update the meta-information of this bug accordingly. -- 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/1856366 Title: PCI/internal sound card not detected on a Swift SF314-57 Status in alsa-driver package in Ubuntu: New Bug description: No sound card detected with kernel 5.5.0-050500rc1-generic 1. Description: Ubuntu 19.10 Release: 19.10 2. linux-image- unsigned-5.5.0-050500rc1-generic_5.5.0-050500rc1.201912081930_amd64.deb 3. have at least one soundcard 4. cat /proc/asound/cards reports: --- no soundcards --- ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 Uname: Linux 5.5.0-050500rc1-generic x86_64 NonfreeKernelModules: hda_intel ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: ubuntu:GNOME Date: Fri Dec 13 22:09:17 2019 InstallationDate: Installed on 2019-12-13 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/05/2019 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.07 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Floris_IL dmi.board.vendor: IL dmi.board.version: V1.07 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.07:bd09/05/2019:svnAcer:pnSwiftSF314-57:pvrV1.07:rvnIL:rnFloris_IL:rvrV1.07:cvnAcer:ct10:cvrChassisVersion: dmi.product.family: Swift 3 dmi.product.name: Swift SF314-57 dmi.product.sku: dmi.product.version: V1.07 dmi.sys.vendor: Acer mtime.conffile..etc.modprobe.d.alsa-base.conf: 2019-12-13T20:34:57.551680 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1856366/+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 1856366] Re: PCI/internal sound card not detected on a Swift SF314-57
[Sorry, I wasn’t subscribed to the notifications.] @hui.wang, your attached firmware, what version is that? $ md5sum sof-icl.ri 2ca373e6254b0e9b37439f7a31984973 /dev/shm/sof-icl.ri @adamfubuntu, do you still have the problem *without* `dsp_driver=0` on an up-to-date Ubuntu 19.10 with Linux 5.5-rc6? ** Bug watch added: Red Hat Bugzilla #1772498 https://bugzilla.redhat.com/show_bug.cgi?id=1772498 ** Bug watch added: github.com/thesofproject/sof/issues #2126 https://github.com/thesofproject/sof/issues/2126 -- 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/1856366 Title: PCI/internal sound card not detected on a Swift SF314-57 Status in alsa-driver package in Ubuntu: New Bug description: No sound card detected with kernel 5.5.0-050500rc1-generic 1. Description: Ubuntu 19.10 Release: 19.10 2. linux-image- unsigned-5.5.0-050500rc1-generic_5.5.0-050500rc1.201912081930_amd64.deb 3. have at least one soundcard 4. cat /proc/asound/cards reports: --- no soundcards --- ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 Uname: Linux 5.5.0-050500rc1-generic x86_64 NonfreeKernelModules: hda_intel ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: ubuntu:GNOME Date: Fri Dec 13 22:09:17 2019 InstallationDate: Installed on 2019-12-13 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/05/2019 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.07 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Floris_IL dmi.board.vendor: IL dmi.board.version: V1.07 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.07:bd09/05/2019:svnAcer:pnSwiftSF314-57:pvrV1.07:rvnIL:rnFloris_IL:rvrV1.07:cvnAcer:ct10:cvrChassisVersion: dmi.product.family: Swift 3 dmi.product.name: Swift SF314-57 dmi.product.sku: dmi.product.version: V1.07 dmi.sys.vendor: Acer mtime.conffile..etc.modprobe.d.alsa-base.conf: 2019-12-13T20:34:57.551680 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1856366/+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 1856366] Re: PCI/internal sound card not detected on a Swift SF314-57
And in Clear Linux: https://community.clearlinux.org/t/new-installation- no-sound-swift-5-i7-1065gt-iris-plus/2407/14 -- 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/1856366 Title: PCI/internal sound card not detected on a Swift SF314-57 Status in alsa-driver package in Ubuntu: New Bug description: No sound card detected with kernel 5.5.0-050500rc1-generic 1. Description: Ubuntu 19.10 Release: 19.10 2. linux-image- unsigned-5.5.0-050500rc1-generic_5.5.0-050500rc1.201912081930_amd64.deb 3. have at least one soundcard 4. cat /proc/asound/cards reports: --- no soundcards --- ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 Uname: Linux 5.5.0-050500rc1-generic x86_64 NonfreeKernelModules: hda_intel ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: ubuntu:GNOME Date: Fri Dec 13 22:09:17 2019 InstallationDate: Installed on 2019-12-13 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/05/2019 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.07 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Floris_IL dmi.board.vendor: IL dmi.board.version: V1.07 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.07:bd09/05/2019:svnAcer:pnSwiftSF314-57:pvrV1.07:rvnIL:rnFloris_IL:rvrV1.07:cvnAcer:ct10:cvrChassisVersion: dmi.product.family: Swift 3 dmi.product.name: Swift SF314-57 dmi.product.sku: dmi.product.version: V1.07 dmi.sys.vendor: Acer mtime.conffile..etc.modprobe.d.alsa-base.conf: 2019-12-13T20:34:57.551680 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1856366/+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 1738774] Re: Pixeled icons with LibreOffice 5.1.6.2 on HiDPI/4K display
This is still an issue, and due to HiDPI getting more and more common, Ubuntu should really look into this to give users a good experience with the setups. -- 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/1738774 Title: Pixeled icons with LibreOffice 5.1.6.2 on HiDPI/4K display Status in libreoffice package in Ubuntu: Confirmed Bug description: LibreOffice 5.1.6.2 shipped with Ubuntu 16.04.3 LTS shows pixeled icons on a HiDPI/4K monitor like used in the Dell XPS 13 9360. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1738774/+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 1860204] [NEW] GNOME3 notification background layer paints over notification text if mouse is moved in notification area
Public bug reported: Hello, I do not know if it is a problem of the current proprietary driver or xorg or GNOME. I tried my best to include all the info you might need. Problem: When I receive a notification in the notification centre of GNOME, it shows up in the notification bubble. If the text in the notification bubble is longer than the amount of text can be shown at once, the it needs to be opened. If I click on the bubble, it opens, but if I move my mouse pointer inside the said notification the light greyish background color of the notification area paints over the text rendering it to be unreadable. If I wait some seconds then this 'layer' disappears partly or completely. Since my VGA works fine under heavy load (GPU intensive applications and games) I guess it is a software related bug --- Release:19.10 xorg: Installed: 1:7.7+19ubuntu12 Candidate: 1:7.7+19ubuntu12 NVIDIA Driver Version: 435.21 VGA: GTX 960 4GB ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13 Uname: Linux 5.3.0-26-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..07.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:07:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 435.21 Sun Aug 25 08:17:57 CDT 2019 GCC version: gcc version 9.2.1 20191008 (Ubuntu 9.2.1-9ubuntu2) ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Jan 18 11:21:51 2020 DistUpgraded: Fresh install DistroCodename: eoan DistroVariant: ubuntu DkmsStatus: nvidia, 435.21, 5.3.0-18-generic, x86_64: installed nvidia, 435.21, 5.3.0-26-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GM206 [GeForce GTX 960] [10de:1401] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd GM206 [GeForce GTX 960] [1458:36c2] InstallationDate: Installed on 2020-01-17 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: Gigabyte Technology Co., Ltd. X570 AORUS ELITE ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-26-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/06/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F11 dmi.board.asset.tag: Default string dmi.board.name: X570 AORUS ELITE 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.:bvrF11:bd12/06/2019:svnGigabyteTechnologyCo.,Ltd.:pnX570AORUSELITE:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnX570AORUSELITE:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: X570 AORUS ELITE dmi.product.sku: Default string dmi.product.version: -CF dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug corruption eoan ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1860204 Title: GNOME3 notification background layer paints over notification text if mouse is moved in notification area Status in xorg package in Ubuntu: New Bug description: Hello, I do not know if it is a problem of the current proprietary driver or xorg or GNOME. I tried my best to include all the info you might need. Problem: When I receive a notification in the notification centre of GNOME, it shows up in the notification bubble. If the text in the notification bubble is longer than the amount of text can be shown at once, the it needs to be opened. If I click on the bubble, it opens, but if I move my mouse pointer inside the said notification the light greyish background color of the
[Desktop-packages] [Bug 1846090] Re: Asus UX580GD (GDX1505:00 27C6:01F1) Touchpad (LCD) screen support
Taha, Did the screenpad work out of the box or did you have to download/setup additional drivers ? -- 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/1846090 Title: Asus UX580GD (GDX1505:00 27C6:01F1) Touchpad (LCD) screen support Status in linux package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-435 package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: Confirmed Bug description: Ubuntu does not support asus zenbook pro UX580GD screenpad (touchpad and screen - all in one) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.0.0-29.31~18.04.1-generic 5.0.21 Uname: Linux 5.0.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 435.21 Sun Aug 25 08:17:57 CDT 2019 GCC version: gcc version 7.4.0 (Ubuntu 7.4.0-1ubuntu1~18.04.1) ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: XFCE Date: Tue Oct 1 00:53:26 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: nvidia, 435.21, 5.0.0-29-generic, x86_64: installed virtualbox, 5.2.32, 5.0.0-29-generic, x86_64: installed DpkgLog: ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Device [8086:3e9b] (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:1021] Subsystem: ASUSTeK Computer Inc. GP107M [GeForce GTX 1050 Mobile] [1043:180e] InstallationDate: Installed on 2019-09-27 (3 days ago) InstallationMedia: Xubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 13d3:5755 IMC Networks Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bus 001 Device 003: ID 04f3:2544 Elan Microelectronics Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. ZenBook Pro 15 UX550GDX_UX580GD ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-29-generic root=UUID=4fba8275-1f29-4ddc-8a1c-e239d3b76c14 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/09/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX550GDX.302 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX550GDX 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.:bvrUX550GDX.302:bd10/09/2018:svnASUSTeKCOMPUTERINC.:pnZenBookPro15UX550GDX_UX580GD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX550GDX:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook Pro dmi.product.name: ZenBook Pro 15 UX550GDX_UX580GD dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.8-0ubuntu0~18.04.2 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1846090/+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