[Desktop-packages] [Bug 1364077] Re: rhythmbox crashes when updating "all feeds"
[Expired for rhythmbox (Ubuntu) because there has been no activity for 60 days.] ** Changed in: rhythmbox (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to rhythmbox in Ubuntu. https://bugs.launchpad.net/bugs/1364077 Title: rhythmbox crashes when updating "all feeds" Status in rhythmbox package in Ubuntu: Expired Bug description: I have three podcast streams. Sometimes rhythmbox crashes on startup. I believe this is tied to a specific crash that occurs consistently, here's dmesg (several crashes in a row trying to update "all streams"): [112404.531570] rhythmbox[23277]: segfault at c ip b72cec74 sp ad27fffc error 4 in libpthread-2.15.so[b72c6000+17000] [112455.524158] rhythmbox[23771]: segfault at c ip b7323c74 sp ab8afffc error 4 in libpthread-2.15.so[b731b000+17000] [112491.331146] rhythmbox[24293]: segfault at c ip b7307c74 sp aa5feffc error 4 in libpthread-2.15.so[b72ff000+17000] [112582.580377] rhythmbox[24501]: segfault at c ip b735ac74 sp a90f0ffc error 4 in libpthread-2.15.so[b7352000+17000] To reproduce it, I 1. Open rhythmbox (assuming it doesn't crash on startup) 2. Click on the "podcasts" menu item 3. Ensure htat "all feeds" is highlighted 4. click on the "update" button $ lsb_release -rd Description: Ubuntu 12.04.5 LTS Release: 12.04 $ apt-cache policy rhythmbox rhythmbox: Installed: 2.96-0ubuntu4.3 Candidate: 2.96-0ubuntu4.3 Version table: *** 2.96-0ubuntu4.3 0 500 http://ubuntu.osuosl.org/ubuntu/ precise-updates/main i386 Packages 100 /var/lib/dpkg/status 2.96-0ubuntu4.1 0 500 http://ubuntu.osuosl.org/ubuntu/ precise-security/main i386 Packages 2.96-0ubuntu4 0 500 http://ubuntu.osuosl.org/ubuntu/ precise/main i386 Packages ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: rhythmbox 2.96-0ubuntu4.3 ProcVersionSignature: Ubuntu 3.2.0-67.70-lowlatency-pae 3.2.60 Uname: Linux 3.2.0-67-lowlatency-pae i686 ApportVersion: 2.0.1-0ubuntu17.7 Architecture: i386 Date: Mon Sep 1 08:51:48 2014 InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release i386 (20120423) MarkForUpload: True SourcePackage: rhythmbox UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1364077/+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 1300777] Re: deleting files from inside rhythmbox is not working
[Expired for rhythmbox (Ubuntu) because there has been no activity for 60 days.] ** Changed in: rhythmbox (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to rhythmbox in Ubuntu. https://bugs.launchpad.net/bugs/1300777 Title: deleting files from inside rhythmbox is not working Status in rhythmbox package in Ubuntu: Expired Bug description: Hi, I could not delete files inside rhythmbox. right klick -> move to trash does nothing. Only a circle with a horizontal line showing at the track beginning and no error message. Xubuntu 13.10 64 Bit Version: ii rhythmbox2.99.1-0ubuntu1 amd64 music player and organizer for GNOME some messages I receive via from rhythmbox during startup, if I run via terminal: (rhythmbox:11431): Gtk-WARNING **: Failed to register client: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.gnome.SessionManager was not provided by any .service files (rhythmbox:11431): Gtk-CRITICAL **: gtk_css_provider_load_from_path: assertion 'path != NULL' failed (rhythmbox:11431): Rhythmbox-WARNING **: Unable to grab media player keys: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.gnome.SettingsDaemon was not provided by any .service files (rhythmbox:11431): Gtk-WARNING **: GtkMenuBar 0x2c324b0 is mapped but visible=1 child_visible=1 parent GtkApplicationWindow 0x23f4260 mapped=0 --- ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 CurrentDesktop: XFCE DistroRelease: Ubuntu 14.04 EcryptfsInUse: Yes InstallationDate: Installed on 2013-05-17 (352 days ago) InstallationMedia: Xubuntu 13.04 "Raring Ringtail" - Release amd64 (20130423.1) Package: rhythmbox 3.0.2-0ubuntu2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Tags: trusty package-from-proposed Uname: Linux 3.13.0-24-generic x86_64 UpgradeStatus: Upgraded to trusty on 2014-04-18 (15 days ago) UserGroups: adm cdrom davfs2 dip lpadmin netdev plugdev sambashare sudo vboxusers _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1300777/+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 1061448] Re: rhythmbox crashed with SIGSEGV
[Expired for rhythmbox (Ubuntu) because there has been no activity for 60 days.] ** Changed in: rhythmbox (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to rhythmbox in Ubuntu. https://bugs.launchpad.net/bugs/1061448 Title: rhythmbox crashed with SIGSEGV Status in rhythmbox package in Ubuntu: Expired Bug description: Description: Ubuntu quantal (development branch) Release: 12.10 rhythmbox: Installed: 2.97-1ubuntu5 Candidate: 2.97-1ubuntu5 Version table: *** 2.97-1ubuntu5 0 500 http://archive.ubuntu.com/ubuntu/ quantal/main amd64 Packages 100 /var/lib/dpkg/status rhythbox is expected to work but crashes with SIGSEGV ProblemType: Crash DistroRelease: Ubuntu 12.10 Package: rhythmbox 2.97-1ubuntu5 ProcVersionSignature: Ubuntu 3.5.0-16.24-generic 3.5.4 Uname: Linux 3.5.0-16-generic x86_64 ApportVersion: 2.6.1-0ubuntu1 Architecture: amd64 CrashCounter: 1 Date: Thu Oct 4 11:58:13 2012 ExecutablePath: /usr/bin/rhythmbox InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Alpha amd64 (20110531.1) ProcCmdline: rhythmbox ProcEnviron: PATH=(custom, user) LANG=en_GB.UTF-8 SHELL=/bin/bash SegvAnalysis: Failure: 'dx' Signal: 11 SourcePackage: rhythmbox StacktraceTop: ?? () ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /usr/lib/librhythmbox-core.so.6 ?? () from /usr/lib/librhythmbox-core.so.6 ?? () from /usr/lib/librhythmbox-core.so.6 Title: rhythmbox crashed with SIGSEGV UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare vboxusers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1061448/+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 1499740] Re: rhythmbox freezes on startup
[Expired for rhythmbox (Ubuntu) because there has been no activity for 60 days.] ** Changed in: rhythmbox (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to rhythmbox in Ubuntu. https://bugs.launchpad.net/bugs/1499740 Title: rhythmbox freezes on startup Status in rhythmbox package in Ubuntu: Expired Bug description: Hello, For some reasons, the network file server that I usually use was unavailable when I launched rhythmbox and it freezed at startup. I am using Ubuntu 14.04.3 LTS with the 3.0.2-0ubuntu2+grilo version of rhythmbox. I attached the error report and as you can see, the program freezed after it was unable to find the device on the IP 192.168.123.20. I do not know why rhythmbox wanted to scan that directory. I have no audio files on that device and have never used it with rhythmbox. Regards, To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1499740/+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 1383632] Re: Rhythmbox freezes sometimes when playing music files
[Expired for rhythmbox (Ubuntu) because there has been no activity for 60 days.] ** Changed in: rhythmbox (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to rhythmbox in Ubuntu. https://bugs.launchpad.net/bugs/1383632 Title: Rhythmbox freezes sometimes when playing music files Status in rhythmbox package in Ubuntu: Expired Bug description: I can't to supply additional information. Simply Rhythmbox hangs sometimes when playing mp3 audio files. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: rhythmbox 3.0.2-0ubuntu2 Uname: Linux 3.17.1-031701-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 CurrentDesktop: Unity Date: Tue Oct 21 11:26:30 2014 InstallationDate: Installed on 2014-07-18 (94 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) SourcePackage: rhythmbox UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1383632/+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 1311389] Re: RhythemBox wants to _Initialize_ a perfectly healthy iPhone.
[Expired for rhythmbox (Ubuntu) because there has been no activity for 60 days.] ** Changed in: rhythmbox (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to rhythmbox in Ubuntu. https://bugs.launchpad.net/bugs/1311389 Title: RhythemBox wants to _Initialize_ a perfectly healthy iPhone. Status in rhythmbox package in Ubuntu: Expired Bug description: When I connect my iPhone to the Usb port RhythmBox launches and presents the dialog asking to Initialize my iPhone. This is not just wrong it is evil. I have to stop working until I can carefully dismiss this unwanted dialog. Give me a preference to NEVER show this dialog and set it checked by default. Or a manual only setting or completely strip the function out of RhythmBox. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: rhythmbox 3.0.2-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 CurrentDesktop: Unity Date: Tue Apr 22 16:29:48 2014 ExecutablePath: /usr/bin/rhythmbox InstallationDate: Installed on 2014-03-28 (25 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) SourcePackage: rhythmbox UpgradeStatus: Upgraded to trusty on 2014-04-13 (9 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1311389/+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 1854733] Re: Canon LPB 6030
[Expired for cups (Ubuntu) because there has been no activity for 60 days.] ** Changed in: cups (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1854733 Title: Canon LPB 6030 Status in cups package in Ubuntu: Expired Bug description: printter driwer das not work. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3.1 ProcVersionSignature: Ubuntu 4.15.0-70.79~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-70-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.21 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Mon Dec 2 14:09:33 2019 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu DpkgLog: 2019-12-02 10:56:18 startup archives install 2019-12-02 10:57:25 startup archives install ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Core Processor Integrated Graphics Controller [103c:172a] InstallationDate: Installed on 2019-01-21 (315 days ago) InstallationMedia: Ubuntu-GNOME 16.04.5 LTS "Xenial Xerus" - Release amd64 (20180731) MachineType: Hewlett-Packard HP EliteBook 8440p PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcEnviron: PATH=(custom, no user) LANG=fi_FI.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-70-generic root=UUID=d23c244f-cbd5-450e-a02a-2772583abebf ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/25/2010 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68CCU Ver. F.11 dmi.board.name: 172A dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 30.31 dmi.chassis.asset.tag: CZC10542JV dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68CCUVer.F.11:bd11/25/2010:svnHewlett-Packard:pnHPEliteBook8440p:pvr:rvnHewlett-Packard:rn172A:rvrKBCVersion30.31:cvnHewlett-Packard:ct10:cvr: dmi.product.family: 103C_5336AN dmi.product.name: HP EliteBook 8440p dmi.sys.vendor: Hewlett-Packard version.compiz: compiz N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.91-2~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1 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/cups/+bug/1854733/+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 1706188] Re: I can play .mp3 and .wav files from harddisk, but no audio from youtube via firefox
[Expired for rhythmbox (Ubuntu) because there has been no activity for 60 days.] ** Changed in: rhythmbox (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to rhythmbox in Ubuntu. https://bugs.launchpad.net/bugs/1706188 Title: I can play .mp3 and .wav files from harddisk, but no audio from youtube via firefox Status in rhythmbox package in Ubuntu: Expired Bug description: 1) ubuntu 14.04 with current updates (like you auto-gathered) 2) rhythmbox 3.0.2 3) expected audio when click on song in youtube (like it worked a week ago, and has worked since Oct2014) 4) no audio from youtube (.mp3 files on hard disk play OK) I've read that youtube uses flash, but I don't know what the name of the opensource version for Ubuntu is. OR is that capability included in rhythmbox? ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: rhythmbox 3.0.2-0ubuntu2 ProcVersionSignature: Ubuntu 3.13.0-123.172-generic 3.13.11-ckt39 Uname: Linux 3.13.0-123-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.24 Architecture: amd64 CurrentDesktop: Unity Date: Mon Jul 24 14:56:05 2017 InstallationDate: Installed on 2014-10-14 (1014 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: rhythmbox UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1706188/+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 1861538] Re: Intel Graphic Card not working
** 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/1861538
Title:
Intel Graphic Card not working
Status in xorg package in Ubuntu:
New
Bug description:
When I try to use the Intel GPU, I get an error : Error creating
authentification agent : Error opening current controlling terminal
for the process ('/dev/tty'): No such device or address.
In the additional drivers section of Ubuntu, it says : Intel
corporation :Unknown, indicating the GPU is not recognised.
I also have an Nvidia MX250.
I am using an IdeaPad S540 (Lenovo).
ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: xorg 1:7.7+19ubuntu12
ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13
Uname: Linux 5.3.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 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
Date: Fri Jan 31 19:20:55 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-29-generic, x86_64: installed
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
Intel Corporation Device [8086:9b41] (rev 02) (prog-if 00 [VGA controller])
Subsystem: Lenovo Device [17aa:3fec]
Subsystem: Lenovo GP108M [GeForce MX250] [17aa:3fec]
InstallationDate: Installed on 2020-01-31 (0 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
MachineType: LENOVO 81V0
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-29-generic
root=UUID=d99c97c8-389d-482a-ad51-724da1184054 ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/19/2019
dmi.bios.vendor: LENOVO
dmi.bios.version: CKCN11WW(V1.01)
dmi.board.asset.tag: NO Asset Tag
dmi.board.name: LNVNB161216
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40709 WIN
dmi.chassis.asset.tag: NO Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Lenovo IdeaPad S540-14IML Touch
dmi.modalias:
dmi:bvnLENOVO:bvrCKCN11WW(V1.01):bd07/19/2019:svnLENOVO:pn81V0:pvrLenovoIdeaPadS540-14IMLTouch:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoIdeaPadS540-14IMLTouch:
dmi.product.family: IdeaPad S540-14IML Touch
dmi.product.name: 81V0
dmi.product.sku: LENOVO_MT_81V0_BU_idea_FM_IdeaPad S540-14IML Touch
dmi.product.version: Lenovo IdeaPad S540-14IML Touch
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.99-1ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~19.10.1
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
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1861538/+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 1861538] [NEW] Intel Graphic Card not working
You have been subscribed to a public bug:
When I try to use the Intel GPU, I get an error : Error creating
authentification agent : Error opening current controlling terminal for
the process ('/dev/tty'): No such device or address.
In the additional drivers section of Ubuntu, it says : Intel corporation
:Unknown, indicating the GPU is not recognised.
I also have an Nvidia MX250.
I am using an IdeaPad S540 (Lenovo).
ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: xorg 1:7.7+19ubuntu12
ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13
Uname: Linux 5.3.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 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
Date: Fri Jan 31 19:20:55 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-29-generic, x86_64: installed
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
Intel Corporation Device [8086:9b41] (rev 02) (prog-if 00 [VGA controller])
Subsystem: Lenovo Device [17aa:3fec]
Subsystem: Lenovo GP108M [GeForce MX250] [17aa:3fec]
InstallationDate: Installed on 2020-01-31 (0 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
MachineType: LENOVO 81V0
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-29-generic
root=UUID=d99c97c8-389d-482a-ad51-724da1184054 ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/19/2019
dmi.bios.vendor: LENOVO
dmi.bios.version: CKCN11WW(V1.01)
dmi.board.asset.tag: NO Asset Tag
dmi.board.name: LNVNB161216
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40709 WIN
dmi.chassis.asset.tag: NO Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Lenovo IdeaPad S540-14IML Touch
dmi.modalias:
dmi:bvnLENOVO:bvrCKCN11WW(V1.01):bd07/19/2019:svnLENOVO:pn81V0:pvrLenovoIdeaPadS540-14IMLTouch:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoIdeaPadS540-14IMLTouch:
dmi.product.family: IdeaPad S540-14IML Touch
dmi.product.name: 81V0
dmi.product.sku: LENOVO_MT_81V0_BU_idea_FM_IdeaPad S540-14IML Touch
dmi.product.version: Lenovo IdeaPad S540-14IML Touch
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.99-1ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~19.10.1
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 eoan third-party-packages ubuntu
--
Intel Graphic Card not working
https://bugs.launchpad.net/bugs/1861538
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 1856160] Re: Bar between bread crumbs and search icon.
** Changed in: nautilus (Ubuntu) Status: Opinion => Invalid ** Changed in: nautilus (Ubuntu) Status: Invalid => Confirmed -- 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/1856160 Title: Bar between bread crumbs and search icon. Status in nautilus package in Ubuntu: Confirmed Bug description: 1) Ubuntu 19.10 2) 1:3.34.1-1ubuntu1 3) There should be no bar between bread crumbs and the search icon. If I remember correctly. 4) There is a bar between bread crumbs and search icon. 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: Thu Dec 12 03:00:41 2019 ExecutablePath: /usr/bin/nautilus GsettingsChanges: b'org.gnome.nautilus.window-state' b'sidebar-width' b'244' b'org.gnome.nautilus.window-state' b'initial-size' b'(1216, 604)' 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-10-28 (45 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) ProcEnviron: SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, no user) LANG=en_US.UTF-8 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/1856160/+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 1856160] Re: Bar between bread crumbs and search icon.
** Attachment added: "files_minimized.png" https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1856160/+attachment/5324599/+files/files_minimized.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1856160 Title: Bar between bread crumbs and search icon. Status in nautilus package in Ubuntu: Opinion Bug description: 1) Ubuntu 19.10 2) 1:3.34.1-1ubuntu1 3) There should be no bar between bread crumbs and the search icon. If I remember correctly. 4) There is a bar between bread crumbs and search icon. 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: Thu Dec 12 03:00:41 2019 ExecutablePath: /usr/bin/nautilus GsettingsChanges: b'org.gnome.nautilus.window-state' b'sidebar-width' b'244' b'org.gnome.nautilus.window-state' b'initial-size' b'(1216, 604)' 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-10-28 (45 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) ProcEnviron: SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, no user) LANG=en_US.UTF-8 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/1856160/+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 1856160] Re: Bar between bread crumbs and search icon.
** Attachment added: "files_maximized.png" https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1856160/+attachment/5324598/+files/files_maximized.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1856160 Title: Bar between bread crumbs and search icon. Status in nautilus package in Ubuntu: Opinion Bug description: 1) Ubuntu 19.10 2) 1:3.34.1-1ubuntu1 3) There should be no bar between bread crumbs and the search icon. If I remember correctly. 4) There is a bar between bread crumbs and search icon. 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: Thu Dec 12 03:00:41 2019 ExecutablePath: /usr/bin/nautilus GsettingsChanges: b'org.gnome.nautilus.window-state' b'sidebar-width' b'244' b'org.gnome.nautilus.window-state' b'initial-size' b'(1216, 604)' 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-10-28 (45 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) ProcEnviron: SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, no user) LANG=en_US.UTF-8 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/1856160/+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 1856160] Re: Bar between bread crumbs and search icon.
I think the bar is a bug. If I maximize Nautilus, the bar disappears. If I minimize Nautilus, the bar reappears. -- 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/1856160 Title: Bar between bread crumbs and search icon. Status in nautilus package in Ubuntu: Opinion Bug description: 1) Ubuntu 19.10 2) 1:3.34.1-1ubuntu1 3) There should be no bar between bread crumbs and the search icon. If I remember correctly. 4) There is a bar between bread crumbs and search icon. 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: Thu Dec 12 03:00:41 2019 ExecutablePath: /usr/bin/nautilus GsettingsChanges: b'org.gnome.nautilus.window-state' b'sidebar-width' b'244' b'org.gnome.nautilus.window-state' b'initial-size' b'(1216, 604)' 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-10-28 (45 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) ProcEnviron: SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, no user) LANG=en_US.UTF-8 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/1856160/+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 1860907] Re: gnome-shell crashes when using touchscreen
I reproduced the issue again, and sent the info per the instructions, it is here: https://bugs.launchpad.net/ubuntu/+source/gnome- shell/+bug/1861542 Sorry about not reading the instructions properly the first time, and thanks for your patience :) -- 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/1860907 Title: gnome-shell crashes when using touchscreen Status in gnome-shell package in Ubuntu: Incomplete Bug description: The crash isn't immediate, but reliably reproducible when using the touchscreen to interact with multiple full-screen native steam games. Typically happens within 30-120 minutes of normal use. (Same games don't crash at all if the touchscreen is not used.) I've reproduced the issue many times. Also seems to affect other full-screen applications such as the default video player (reproduced once). Typically right before the crash the reaction to touch input will become somewhat strange (touches seem to register, but the full-screen application doesn't respond as expected, for example moving the cursor but not actually performing the "tap" action). # lsb_release -rd Description: Ubuntu 19.10 Release: 19.10 # apt-cache policy gnome-shell gnome-shell: Installed: 3.34.1+git20191024-1ubuntu1~19.10.1 Candidate: 3.34.1+git20191024-1ubuntu1~19.10.1 Version table: *** 3.34.1+git20191024-1ubuntu1~19.10.1 500 500 http://archive.ubuntu.com/ubuntu eoan-updates/main amd64 Packages 100 /var/lib/dpkg/status 3.34.1-1ubuntu1 500 500 http://archive.ubuntu.com/ubuntu eoan/main amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.34.1+git20191024-1ubuntu1~19.10.1 ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13 Uname: Linux 5.3.0-26-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Jan 26 12:36:19 2020 DisplayManager: gdm3 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.34.1+git20191107-1ubuntu1~19.10.1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.apport.crashdb.conf: 2020-01-25T22:33:07.611081 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1860907/+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 1752860] Re: hp laserjet 1020 not working
** Changed in: hplip (Ubuntu) Assignee: (unassigned) => Clinton H (49studebaker) ** Changed in: hplip (Ubuntu) Status: Confirmed => Invalid ** Changed in: hplip (Ubuntu) Status: Invalid => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to hplip in Ubuntu. https://bugs.launchpad.net/bugs/1752860 Title: hp laserjet 1020 not working Status in hplip package in Ubuntu: Fix Released Bug description: my hp laserjet 1020 is not printing when im trying to prit a test page ubuntu says that job printed but in my printer nothing happens To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hplip/+bug/1752860/+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 1861532] [NEW] brightness control not working
Public bug reported: after selecting nvidia-driver-435 in livepatch- additional drivers the brightness control stops working after the first reboot. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.3.0-28.30~18.04.1-generic 5.3.13 Uname: Linux 5.3.0-28-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: ubuntu:GNOME Date: Fri Jan 31 22:00:02 2020 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: nvidia, 435.21, 4.15.0-76-generic, x86_64: installed nvidia, 435.21, 5.3.0-28-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation Device [10de:2191] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:3ffc] InstallationDate: Installed on 2020-01-31 (0 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) MachineType: LENOVO 81Q4 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-28-generic root=UUID=084301b5-fdae-4c92-811e-0536a3b7555b ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/23/2019 dmi.bios.vendor: LENOVO dmi.bios.version: BHCN35WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Legion Y540-17IRH dmi.modalias: dmi:bvnLENOVO:bvrBHCN35WW:bd11/23/2019:svnLENOVO:pn81Q4:pvrLegionY540-17IRH:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLegionY540-17IRH: dmi.product.family: Legion Y540-17IRH dmi.product.name: 81Q4 dmi.product.sku: LENOVO_MT_81Q4_BU_idea_FM_Legion Y540-17IRH dmi.product.version: Legion Y540-17IRH dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.2-1ubuntu1.1~18.04.2 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1861532 Title: brightness control not working Status in xorg package in Ubuntu: New Bug description: after selecting nvidia-driver-435 in livepatch- additional drivers the brightness control stops working after the first reboot. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.3.0-28.30~18.04.1-generic 5.3.13 Uname: Linux 5.3.0-28-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: ubuntu:GNOME Date: Fri Jan 31 22:00:02 2020 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: nvidia, 435.21, 4.15.0-76-generic, x86_64: installed nvidia, 435.21, 5.3.0-28-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation Device [10de:2191] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:3ffc] InstallationDate: Installed on 2020-01-31 (0 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) MachineType: LENOVO 81Q4 ProcKernelCmdLine: BOOT_IMAGE=/boo
[Desktop-packages] [Bug 1853638] Re: BCM57416 NetXtreme-E Dual-Media 10G RDMA Ethernet device seems to be dropping data
I don't think bnxt_en exposes the disable_tpa parameter. Be that as it may, I think the tpa_aborts may be a red herring. TPA aggregates TCP flows and you are seeing the issue with ICMP. In which direction(s) of traffic flow do you see the losses? -- 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/1853638 Title: BCM57416 NetXtreme-E Dual-Media 10G RDMA Ethernet device seems to be dropping data Status in linux package in Ubuntu: Confirmed Status in network-manager package in Ubuntu: Confirmed Bug description: The issue appears to be with the BCM57416 NetXtreme-E Dual-Media 10G RDMA Ethernet device seems to be dropping data Basically, we are dropping data, as you can see from the benchmark tool as follows: tcdforge@x310a:/usr/local/lib/lib/uhd/examples$ ./benchmark_rate --rx_rate 10e6 --tx_rate 10e6 --duration 300 [INFO] [UHD] linux; GNU C++ version 5.4.0 20160609; Boost_105800; UHD_3.14.1.1-0-g98c7c986 [WARNING] [UHD] Unable to set the thread priority. Performance may be negatively affected. Please see the general application notes in the manual for instructions. EnvironmentError: OSError: error in pthread_setschedparam [00:00:00.07] Creating the usrp device with: ... [INFO] [X300] X300 initialization sequence... [INFO] [X300] Maximum frame size: 1472 bytes. [INFO] [X300] Radio 1x clock: 200 MHz [INFO] [GPS] Found an internal GPSDO: LC_XO, Firmware Rev 0.929a [INFO] [0/DmaFIFO_0] Initializing block control (NOC ID: 0xF1F0D000) [INFO] [0/DmaFIFO_0] BIST passed (Throughput: 1308 MB/s) [INFO] [0/DmaFIFO_0] BIST passed (Throughput: 1316 MB/s) [INFO] [0/Radio_0] Initializing block control (NOC ID: 0x12AD1001) [INFO] [0/Radio_1] Initializing block control (NOC ID: 0x12AD1001) [INFO] [0/DDC_0] Initializing block control (NOC ID: 0xDDC0) [INFO] [0/DDC_1] Initializing block control (NOC ID: 0xDDC0) [INFO] [0/DUC_0] Initializing block control (NOC ID: 0xD0C0) [INFO] [0/DUC_1] Initializing block control (NOC ID: 0xD0C0) Using Device: Single USRP: Device: X-Series Device Mboard 0: X310 RX Channel: 0 RX DSP: 0 RX Dboard: A RX Subdev: SBX-120 RX RX Channel: 1 RX DSP: 0 RX Dboard: B RX Subdev: SBX-120 RX TX Channel: 0 TX DSP: 0 TX Dboard: A TX Subdev: SBX-120 TX TX Channel: 1 TX DSP: 0 TX Dboard: B TX Subdev: SBX-120 TX [00:00:04.305374] Setting device timestamp to 0... [WARNING] [UHD] Unable to set the thread priority. Performance may be negatively affected. Please see the general application notes in the manual for instructions. EnvironmentError: OSError: error in pthread_setschedparam [00:00:04.310990] Testing receive rate 10.00 Msps on 1 channels [WARNING] [UHD] Unable to set the thread priority. Performance may be negatively affected. Please see the general application notes in the manual for instructions. EnvironmentError: OSError: error in pthread_setschedparam [00:00:04.318356] Testing transmit rate 10.00 Msps on 1 channels [00:00:06.693119] Detected Rx sequence error. D[00:00:09.402843] Detected Rx sequence error. DD[00:00:40.927978] Detected Rx sequence error. D[00:01:44.982243] Detected Rx sequence error. D[00:02:11.400692] Detected Rx sequence error. D[00:02:14.805292] Detected Rx sequence error. D[00:02:41.875596] Detected Rx sequence error. D[00:03:06.927743] Detected Rx sequence error. D[00:03:47.967891] Detected Rx sequence error. D[00:03:58.233659] Detected Rx sequence error. D[00:03:58.876588] Detected Rx sequence error. D[00:04:03.139770] Detected Rx sequence error. D[00:04:45.287465] Detected Rx sequence error. D[00:04:56.425845] Detected Rx sequence error. D[00:04:57.929209] Detected Rx sequence error. [00:05:04.529548] Benchmark complete. Benchmark rate summary: Num received samples: 2995435936 Num dropped samples: 4622800 Num overruns detected:0 Num transmitted samples: 3008276544 Num sequence errors (Tx): 0 Num sequence errors (Rx): 15 Num underruns detected: 0 Num late commands:0 Num timeouts (Tx):0 Num timeouts (Rx):0 Done! tcdforge@x310a:/usr/local/lib/lib/uhd/examples$ In this particular case description, the nodes are USRP x310s. However, we have the same issue with N210 nodes dropping samples connected to the BCM57416 NetXtreme-E Dual-Media 10G RDMA Ethernet device. There is no problem with the USRPs themselves, as we have tested them with normal 1G network cards and have no dropped samples. Personally I think its something to do with the 10G network card, possibly on a ubuntu driver??? Note, Dell have said there is no hardware problem with the 10G interfaces I have followed
[Desktop-packages] [Bug 1852474] Re: cups not printing if authentication required by server
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: cups (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1852474 Title: cups not printing if authentication required by server Status in cups package in Ubuntu: Confirmed Bug description: cups does not print if servers require authenticated users to print. No login-dialog is shown. Print jobs are on hold, waiting for legitimization. But no legitimization dialog will be shown. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: cups 2.2.12-2ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-22.24-generic 5.3.7 Uname: Linux 5.3.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: XFCE Date: Wed Nov 13 19:23:18 2019 InstallationDate: Installed on 2019-09-09 (65 days ago) InstallationMedia: Xubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Lpstat: device for KONICA-MINOLTA-C364Series-OpenOffice-PPD: smb://srvmfg02-muc.bfs.de/drucker-muc device for Lexmark_MX310dn: implicitclass://Lexmark_MX310dn/ Lsusb: Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: VMware, Inc. VMware Virtual Platform Papersize: letter PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/KONICA-MINOLTA-C364Series-OpenOffice-PPD.ppd', '/etc/cups/ppd/Lexmark_MX310dn.ppd'] failed with exit code 2: grep: /etc/cups/ppd/KONICA-MINOLTA-C364Series-OpenOffice-PPD.ppd: Permission denied grep: /etc/cups/ppd/Lexmark_MX310dn.ppd: Permission denied ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.3.0-22-generic root=UUID=f99c1b40-4de7-4f4c-9d3f-c32918aa952c ro rootflags=subvol=@ quiet splash SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/29/2019 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd07/29/2019:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1852474/+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 1861528] [NEW] screen corruption/UI glitching
Public bug reported: The user interface in ubuntu 19.10-20.04 is having glitches. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu13 ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3 Uname: Linux 5.4.0-9-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperVersion: 1.438 CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Jan 31 19:48:11 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation C61 [GeForce 6150SE nForce 430] [10de:03d0] (rev a2) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company C61 [GeForce 6150SE nForce 430] [103c:2a6c] LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200124) MachineType: HP-Pavilion KE568AA-ABA m8357c ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: file=/cdrom/preseed/username.seed initrd=/casper/initrd quiet splash --- maybe-ubiquity SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/12/2007 dmi.bios.vendor: Phoenix Technologies, LTD dmi.bios.version: 5.04 dmi.board.name: NARRA3 dmi.board.vendor: ASUSTek Computer INC. dmi.board.version: 3.02 dmi.chassis.type: 3 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvr5.04:bd12/12/2007:svnHP-Pavilion:pnKE568AA-ABAm8357c:pvr:rvnASUSTekComputerINC.:rnNARRA3:rvr3.02:cvnHewlett-Packard:ct3:cvrChassisVersion: dmi.product.family: 103C_53316J dmi.product.name: KE568AA-ABA m8357c dmi.product.sku: KE568AA#ABA dmi.sys.vendor: HP-Pavilion version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.100-4 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.4-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.6-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug corruption focal 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/1861528 Title: screen corruption/UI glitching Status in xorg package in Ubuntu: New Bug description: The user interface in ubuntu 19.10-20.04 is having glitches. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu13 ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3 Uname: Linux 5.4.0-9-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperVersion: 1.438 CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Jan 31 19:48:11 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation C61 [GeForce 6150SE nForce 430] [10de:03d0] (rev a2) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company C61 [GeForce 6150SE nForce 430] [103c:2a6c] LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200124) MachineType: HP-Pavilion KE568AA-ABA m8357c ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: file=/cdrom/preseed/username.seed initrd=/casper/initrd quiet splash --- maybe-ubiquity SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/12/2007 dmi.bios.vendor: Phoenix Technologies, LTD dmi.bios.version: 5.04 dmi.board.name: NARRA3 dmi.board.vendor: ASUSTek Computer INC. dmi.board.version: 3.02 dmi.chassis.type: 3 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvr5.04:bd12/12/2007:svnHP-Pavilion:pnKE568AA-ABAm8357c:pvr:rvnASUSTekComputerINC.:rnNARRA3:rvr3.02:cvnHewlett-Packard:ct3:cvrChassisVersion: dmi.product.family: 103C_53316J dmi.product.name: KE568AA-ABA m8357c dmi.product.sku: KE568AA#ABA dmi.sys.vendor: HP-Pavilion version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.100-4 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.4-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.6-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A vers
[Desktop-packages] [Bug 1861340] Re: All bitmap fonts no longer visible after upgrade 19.10 -> Focal (development)
I'm speculating that pango 1.44 dropping support for bitmap fonts might be a cause: https://gitlab.gnome.org/GNOME/pango/issues/386 ** Package changed: fontconfig (Ubuntu) => pango1.0 (Ubuntu) ** Bug watch added: gitlab.gnome.org/GNOME/pango/issues #386 https://gitlab.gnome.org/GNOME/pango/issues/386 ** Description changed: For years I've installed a bitmap font for my terminals, but since I upgraded to Focal (development branch) today, it (and other bitmap fonts) no longer work. The font is 'Dina', from here: http://www.dcmembers.com/jibsen/download/61/?unapproved=504&moderation-hash=f1abb9d89caafa881dcfc05cd32372e7 I have always installed it using a script: # install dina sudo mkdir -p /usr/share/fonts/Dina cd /usr/share/fonts/Dina sudo unzip ~/Downloads/Dina.zip # enable bitmap fonts sudo rm -f /etc/fonts/conf.d/70-no-bitmaps.conf # rebuild the cache fc-cache -f -v # Set as default mono font gsettings set org.gnome.desktop.interface monospace-font-name "Dina 8" This has always worked in the past, through many versions of Ubuntu, including 19.10. I installed Focal today, using `sudo do-release-upgrade -d`. Now the above script does not make Dina visible in font selectors such as that produced by the Tweaks / Fonts / [Monospace Text] button. Terminals that were previously configured to use that font now display the "box of hex digits" characters (what are they called?) - I cannot run 'gnome-font-viewer' to check things out, presumably due to some variant of: + ~~I cannot run 'gnome-font-viewer' to check things out, presumably due to some variant of: https://bugs.launchpad.net/ubuntu/+source/gnome-font-viewer/+bug/1375819 - (the window displays but immediately locks up.) + (the window displays but immediately locks up.)~~ + UPDATE: gnome-font-viewer runs fine today. All bitmap fonts are not present. While trying to find a fix, I tried a few changes to the above script, which did not help: * Unzip to "$HOME/.fonts" instead * Trying other symlinks in the fonts config.d: ( cd /etc/fonts/conf.d sudo rm -f 70-no-bitmaps.conf sudo ln -sf ../conf.avail/70-yes-bitmaps.conf ) (tried with both 'yes-bitmaps' and 'force-bitmaps') * fc-cache -r # "really" force cache re-creation ** Description changed: For years I've installed a bitmap font for my terminals, but since I upgraded to Focal (development branch) today, it (and other bitmap fonts) no longer work. The font is 'Dina', from here: http://www.dcmembers.com/jibsen/download/61/?unapproved=504&moderation-hash=f1abb9d89caafa881dcfc05cd32372e7 I have always installed it using a script: # install dina sudo mkdir -p /usr/share/fonts/Dina cd /usr/share/fonts/Dina sudo unzip ~/Downloads/Dina.zip # enable bitmap fonts sudo rm -f /etc/fonts/conf.d/70-no-bitmaps.conf # rebuild the cache fc-cache -f -v # Set as default mono font gsettings set org.gnome.desktop.interface monospace-font-name "Dina 8" This has always worked in the past, through many versions of Ubuntu, including 19.10. I installed Focal today, using `sudo do-release-upgrade -d`. Now the above script does not make Dina visible in font selectors such as that produced by the Tweaks / Fonts / [Monospace Text] button. Terminals that were previously configured to use that font now display the "box of hex digits" characters (what are they called?) - ~~I cannot run 'gnome-font-viewer' to check things out, presumably due to some variant of: - https://bugs.launchpad.net/ubuntu/+source/gnome-font-viewer/+bug/1375819 - (the window displays but immediately locks up.)~~ - UPDATE: gnome-font-viewer runs fine today. All bitmap fonts are not present. + gnome-font-viewer does not list any of the installed bitmap fonts. While trying to find a fix, I tried a few changes to the above script, which did not help: * Unzip to "$HOME/.fonts" instead * Trying other symlinks in the fonts config.d: ( cd /etc/fonts/conf.d sudo rm -f 70-no-bitmaps.conf sudo ln -sf ../conf.avail/70-yes-bitmaps.conf ) (tried with both 'yes-bitmaps' and 'force-bitmaps') * fc-cache -r # "really" force cache re-creation -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pango1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1861340 Title: All bitmap fonts no longer visible after upgrade 19.10 -> Focal (development) Status in pango1.0 package in Ubuntu: New Bug description: For years I've installed a bitmap font for my terminals, but since I upgraded to Focal (development branch) today, it (and other bitmap fonts) no longer work. The font is 'Dina', from here: http://www.dcmembers.com/jibsen/download/61/?unapprov
[Desktop-packages] [Bug 1861043] Re: GUI frozen when memory was exhausted (by non-GUI processes)
I was able to trigger this again with a sizeable Firefox webpage. This time I was able to CTRL+ALT+F4 to a different VT and even enter my username but was not able to login. I had to Hard Boot to recover the system. Similar messages in there about memory pressure. Thanks again for looking into this! ** Attachment added: "Second Triggering" https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1861043/+attachment/5324477/+files/ff_prevboot.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1861043 Title: GUI frozen when memory was exhausted (by non-GUI processes) Status in gnome-shell package in Ubuntu: New Status in xorg-server package in Ubuntu: New Bug description: So under high load I can generally cause a freeze in Gnome/Ubuntu. This is somewhat expected and likely should be fixed by some sort of OOM killer. However that's only part of the problem. Virtual Consoles are disabled (`/etc/systemd/logind.conf` `NAutoVTs` by default) and I believe that too to be a bug. In the past I could have Switched VT's logged in and killed of a high memory/cpu process or two. Now I have to hard kill the box and risk loosing in progress work which is ungainly. If there's a worry about "what will new users do if they accidentally hit CTRL+ALT+F\d" maybe instead of disabling it we could change the default login message to have a "Don't know how you got here? Hit CTLR+ALT+F1 to go back." Also because I have to hard restart apport never get's called to show exactly why the system is hanging. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu13 ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8 Uname: Linux 5.4.0-12-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia .proc.driver.nvidia.gpus..03.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:03: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 440.44 Sun Dec 8 03:38:56 UTC 2019 GCC version: gcc version 9.2.1 20200123 (Ubuntu 9.2.1-25ubuntu1) ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Jan 27 15:13:07 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 440.44, 5.4.0-12-generic, x86_64: installed nvidia, 440.44, 5.4.0-9-generic, x86_64: installed ExtraDebuggingInterest: Yes GpuHangFrequency: Several times a week GpuHangReproducibility: Occurs more often under certain circumstances GpuHangStarted: Since before I upgraded GraphicsCard: Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell HD Graphics 5500 [1028:062b] Subsystem: Dell GM108M [GeForce 840M] [1028:062b] InstallationDate: Installed on 2020-01-14 (13 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200106) MachineType: Dell Inc. Latitude E5450 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-12-generic root=UUID=37b7ed5e-16a1-4e03-ad70-e85dfec9bf53 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/30/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.name: 0MVKK7 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA08:bd07/30/2015:svnDellInc.:pnLatitudeE5450:pvr:rvnDellInc.:rn0MVKK7:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E5450 dmi.product.sku: 062B dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.100-4 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.4-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.4-1ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.6-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1861043/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packag
[Desktop-packages] [Bug 1861340] Re: All bitmap fonts no longer visible after upgrade 19.10 -> Focal (development)
I semi-guessed at package 'fontconfig' to associate. Advice welcome. ** Package changed: ubuntu => fontconfig (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fontconfig in Ubuntu. https://bugs.launchpad.net/bugs/1861340 Title: All bitmap fonts no longer visible after upgrade 19.10 -> Focal (development) Status in fontconfig package in Ubuntu: New Bug description: For years I've installed a bitmap font for my terminals, but since I upgraded to Focal (development branch) today, it (and other bitmap fonts) no longer work. The font is 'Dina', from here: http://www.dcmembers.com/jibsen/download/61/?unapproved=504&moderation-hash=f1abb9d89caafa881dcfc05cd32372e7 I have always installed it using a script: # install dina sudo mkdir -p /usr/share/fonts/Dina cd /usr/share/fonts/Dina sudo unzip ~/Downloads/Dina.zip # enable bitmap fonts sudo rm -f /etc/fonts/conf.d/70-no-bitmaps.conf # rebuild the cache fc-cache -f -v # Set as default mono font gsettings set org.gnome.desktop.interface monospace-font-name "Dina 8" This has always worked in the past, through many versions of Ubuntu, including 19.10. I installed Focal today, using `sudo do-release-upgrade -d`. Now the above script does not make Dina visible in font selectors such as that produced by the Tweaks / Fonts / [Monospace Text] button. Terminals that were previously configured to use that font now display the "box of hex digits" characters (what are they called?) I cannot run 'gnome-font-viewer' to check things out, presumably due to some variant of: https://bugs.launchpad.net/ubuntu/+source/gnome-font-viewer/+bug/1375819 (the window displays but immediately locks up.) While trying to find a fix, I tried a few changes to the above script, which did not help: * Unzip to "$HOME/.fonts" instead * Trying other symlinks in the fonts config.d: ( cd /etc/fonts/conf.d sudo rm -f 70-no-bitmaps.conf sudo ln -sf ../conf.avail/70-yes-bitmaps.conf ) (tried with both 'yes-bitmaps' and 'force-bitmaps') * fc-cache -r # "really" force cache re-creation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/1861340/+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 1861340] [NEW] All bitmap fonts no longer visible after upgrade 19.10 -> Focal (development)
You have been subscribed to a public bug: For years I've installed a bitmap font for my terminals, but since I upgraded to Focal (development branch) today, it (and other bitmap fonts) no longer work. The font is 'Dina', from here: http://www.dcmembers.com/jibsen/download/61/?unapproved=504&moderation-hash=f1abb9d89caafa881dcfc05cd32372e7 I have always installed it using a script: # install dina sudo mkdir -p /usr/share/fonts/Dina cd /usr/share/fonts/Dina sudo unzip ~/Downloads/Dina.zip # enable bitmap fonts sudo rm -f /etc/fonts/conf.d/70-no-bitmaps.conf # rebuild the cache fc-cache -f -v # Set as default mono font gsettings set org.gnome.desktop.interface monospace-font-name "Dina 8" This has always worked in the past, through many versions of Ubuntu, including 19.10. I installed Focal today, using `sudo do-release-upgrade -d`. Now the above script does not make Dina visible in font selectors such as that produced by the Tweaks / Fonts / [Monospace Text] button. Terminals that were previously configured to use that font now display the "box of hex digits" characters (what are they called?) I cannot run 'gnome-font-viewer' to check things out, presumably due to some variant of: https://bugs.launchpad.net/ubuntu/+source/gnome-font-viewer/+bug/1375819 (the window displays but immediately locks up.) While trying to find a fix, I tried a few changes to the above script, which did not help: * Unzip to "$HOME/.fonts" instead * Trying other symlinks in the fonts config.d: ( cd /etc/fonts/conf.d sudo rm -f 70-no-bitmaps.conf sudo ln -sf ../conf.avail/70-yes-bitmaps.conf ) (tried with both 'yes-bitmaps' and 'force-bitmaps') * fc-cache -r # "really" force cache re-creation ** Affects: fontconfig (Ubuntu) Importance: Undecided Status: New ** Tags: bot-comment -- All bitmap fonts no longer visible after upgrade 19.10 -> Focal (development) https://bugs.launchpad.net/bugs/1861340 You received this bug notification because you are a member of Desktop Packages, which is subscribed to fontconfig 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 1860907] Re: gnome-shell crashes when using touchscreen
ubuntu-bug is telling me some packages were not the newest versions, I'm trying to reproduce again after upgrading my packages ** Attachment removed: "_usr_bin_gnome-shell.1000.crash" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1860907/+attachment/5324291/+files/_usr_bin_gnome-shell.1000.crash -- 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/1860907 Title: gnome-shell crashes when using touchscreen Status in gnome-shell package in Ubuntu: Incomplete Bug description: The crash isn't immediate, but reliably reproducible when using the touchscreen to interact with multiple full-screen native steam games. Typically happens within 30-120 minutes of normal use. (Same games don't crash at all if the touchscreen is not used.) I've reproduced the issue many times. Also seems to affect other full-screen applications such as the default video player (reproduced once). Typically right before the crash the reaction to touch input will become somewhat strange (touches seem to register, but the full-screen application doesn't respond as expected, for example moving the cursor but not actually performing the "tap" action). # lsb_release -rd Description: Ubuntu 19.10 Release: 19.10 # apt-cache policy gnome-shell gnome-shell: Installed: 3.34.1+git20191024-1ubuntu1~19.10.1 Candidate: 3.34.1+git20191024-1ubuntu1~19.10.1 Version table: *** 3.34.1+git20191024-1ubuntu1~19.10.1 500 500 http://archive.ubuntu.com/ubuntu eoan-updates/main amd64 Packages 100 /var/lib/dpkg/status 3.34.1-1ubuntu1 500 500 http://archive.ubuntu.com/ubuntu eoan/main amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.34.1+git20191024-1ubuntu1~19.10.1 ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13 Uname: Linux 5.3.0-26-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Jan 26 12:36:19 2020 DisplayManager: gdm3 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.34.1+git20191107-1ubuntu1~19.10.1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.apport.crashdb.conf: 2020-01-25T22:33:07.611081 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1860907/+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 1860540] Re: Password entry has no way of displaying what you type
** Changed in: gnome-shell Status: Unknown => Fix Released -- 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/1860540 Title: Password entry has no way of displaying what you type Status in GNOME Shell: Fix Released Status in gnome-shell package in Ubuntu: Triaged Bug description: In Focal the network password / passphrase entry form has no way of displaying what is being typed. I'd expect a checkbox or something... ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-desktop 1.442 ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3 Uname: Linux 5.4.0-9-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 CasperVersion: 1.438 CurrentDesktop: ubuntu:GNOME Date: Wed Jan 22 11:13:41 2020 LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200117) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-meta UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1860540/+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 1853357] Re: display (whole computer?) hangs when I attempt to use DisplayLink with Wayland
Sorry, I meant 19.10 in my last comment, not 19.04. When I use the evdi module and library shipped with Ubuntu in 20.04, then DisplayLink works in Xorg, but it's very glitchy, with cursor artifacts showing up constantly all over the place on all screens, both DisplayLink and non-DisplayLink. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1853357 Title: display (whole computer?) hangs when I attempt to use DisplayLink with Wayland Status in Mutter: New Status in mutter package in Ubuntu: Incomplete Status in mutter source package in Eoan: Confirmed Status in mutter source package in Focal: Incomplete Bug description: [ Impact ] I am using the DisplayLink driver for Ubuntu provided at https://www.displaylink.com/downloads/ubuntu DisplayLink is working under Xorg, but when I try to use it under Wayland my whole display hangs and I can't even switch to a different VT with Ctrl-Alt-F3 so I think maybe the whole computer is hung? Not certain. [ Test case ] - Install DisplayLink drivers - Start GNOME Shell in wayland mode - Connect to a display-link dock - Expect the shell to work properly and be visible in the external device [ Regression potential ] Wayland session won't work even for standard drm devices I am using the DisplayLink driver for Ubuntu provided at https://www.displaylink.com/downloads/ubuntu, which I think is the only way to get DisplayLink fully working under Ubuntu? That is, DisplayLink didn't work when I installed the evdi-dkms and libevdi0 Ubuntu packages, and I couldn't find any other packages that might be relevant (did I miss something?) so as far as I can tell the only way to get everything that's needed is from displaylink.com. I'm reporting this issue while logged in under Xorg because I can't report it when logged in with my DisplayLink monitors plugged in under Wayland, for obvious reasons. :-/ ProblemType: BugDistroRelease: Ubuntu 19.10 Package: mutter 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: Wed Nov 20 14:08:21 2019 InstallationDate: Installed on 2019-09-12 (69 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)SourcePackage: mutter UpgradeStatus: Upgraded to eoan on 2019-09-20 (61 days ago) modified.conffile..etc.apport.crashdb.conf: [modified] mtime.conffile..etc.apport.crashdb.conf: 2019-10-23T16:51:18.143596 To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1853357/+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 1853357] Re: display (whole computer?) hangs when I attempt to use DisplayLink with Wayland
Learning more about this as I go: * I'm no longer convinced that I was correct above when I claimed that the version of the evdi kernel module and library shipped with Ubuntu are newer than the version shipped with the installer available on displaylink.com. I might be wrong about that. * When I use the versions shipped with Ubuntu instead of the displaylink.com installer, on Ubuntu 19.04, then I can only use DisplayLink monitors under Wayland, i.e., they aren't detected under Xorg. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1853357 Title: display (whole computer?) hangs when I attempt to use DisplayLink with Wayland Status in Mutter: New Status in mutter package in Ubuntu: Incomplete Status in mutter source package in Eoan: Confirmed Status in mutter source package in Focal: Incomplete Bug description: [ Impact ] I am using the DisplayLink driver for Ubuntu provided at https://www.displaylink.com/downloads/ubuntu DisplayLink is working under Xorg, but when I try to use it under Wayland my whole display hangs and I can't even switch to a different VT with Ctrl-Alt-F3 so I think maybe the whole computer is hung? Not certain. [ Test case ] - Install DisplayLink drivers - Start GNOME Shell in wayland mode - Connect to a display-link dock - Expect the shell to work properly and be visible in the external device [ Regression potential ] Wayland session won't work even for standard drm devices I am using the DisplayLink driver for Ubuntu provided at https://www.displaylink.com/downloads/ubuntu, which I think is the only way to get DisplayLink fully working under Ubuntu? That is, DisplayLink didn't work when I installed the evdi-dkms and libevdi0 Ubuntu packages, and I couldn't find any other packages that might be relevant (did I miss something?) so as far as I can tell the only way to get everything that's needed is from displaylink.com. I'm reporting this issue while logged in under Xorg because I can't report it when logged in with my DisplayLink monitors plugged in under Wayland, for obvious reasons. :-/ ProblemType: BugDistroRelease: Ubuntu 19.10 Package: mutter 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: Wed Nov 20 14:08:21 2019 InstallationDate: Installed on 2019-09-12 (69 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)SourcePackage: mutter UpgradeStatus: Upgraded to eoan on 2019-09-20 (61 days ago) modified.conffile..etc.apport.crashdb.conf: [modified] mtime.conffile..etc.apport.crashdb.conf: 2019-10-23T16:51:18.143596 To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1853357/+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 1853357] Re: display (whole computer?) hangs when I attempt to use DisplayLink with Wayland
With Ubuntu 19.10: I am not able to reproduce the issue with a single monitor of a different brand plugged into the DisplayLink adapter. There are three differences here and I don't have the equipment available where I am right now to narrow down which of them is relevant: * one monitor instead of two; * different brand and dimensions of monitor; and * I'm only using the HDMI plug on the DisplayLink adapter, not the DVI plug. However, one thing I do observe with this configuration -- which again, doesn't crash -- is that screen updates to the DisplayLink monitor are Extremely Slow. Like I am typing in a terminal window and it sometimes takes a second or two between when I type something and when the results of the typing show up in the terminal. If I move the same terminal window onto the built-in laptop display the lag goes away. The update lag does not occur when I use Xorg instead of Wayland. Attempting to test Ubuntu 20.04 on same laptop booting from Thumb drive: Live CD user doesn't support Wayland. Tried creating new user, Wayland wasn't available for that user either. Of course DisplayLink stuff isn't installed either, so the laptop doesn't actually notice the DisplayLink display when I plug it in. So to make this test work I would have to figure out how to install Wayland in the running live image and install the DisplayLink stuff too. The DisplayLink stuff I can figure out, but not sure about how to enable Wayland sessions in the live image. Attempting to test Ubuntu 20.04 on a slightly different laptop: I upgraded a spare laptop to Ubuntu 20.04, managed to get DisplayLink installed onto it (I had to tweak the installer package not to compile and install the dkms modules and to use the ones that ship with Ubuntu instead), and tested it. Again, keep in mind that in my current setup I'm unable to reproduce the hanging issue, but I did reproduce the display lag. Next steps: 1. On the laptop where I encountered the hanging issue, I am using the evdi kernel module and library that are shipped with the DisplayLink reference implementation release from last July, rather than the newer module and library that are included in Ubuntu. I need to reinstall evdi on that laptop using the tweak I mentioned above for 20.04, so that I am using the Ubuntu version of the module and library with 19.10, to see if the problem persists. I.e., the crashing issue may resolve if I use the evdi kernel module and library that ship with Ubuntu. 2. If not, then test various configurations and try to identify which of the factors above triggers the issue (one monitor vs. two; brand and dimensions of monitor; HDMI vs. DVI plug in adapter). 3. Test whether I am able to reproduce the issue in 20.04 on the spare laptop with the monitor configuration with which I encountered the issue in 19.10. 4. Try to figure out how to install and enable both Wayland and the DisplayLink manager in a running Live CD session so that I can test with the laptop that I know has encountered this issue in the past. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1853357 Title: display (whole computer?) hangs when I attempt to use DisplayLink with Wayland Status in Mutter: New Status in mutter package in Ubuntu: Incomplete Status in mutter source package in Eoan: Confirmed Status in mutter source package in Focal: Incomplete Bug description: [ Impact ] I am using the DisplayLink driver for Ubuntu provided at https://www.displaylink.com/downloads/ubuntu DisplayLink is working under Xorg, but when I try to use it under Wayland my whole display hangs and I can't even switch to a different VT with Ctrl-Alt-F3 so I think maybe the whole computer is hung? Not certain. [ Test case ] - Install DisplayLink drivers - Start GNOME Shell in wayland mode - Connect to a display-link dock - Expect the shell to work properly and be visible in the external device [ Regression potential ] Wayland session won't work even for standard drm devices I am using the DisplayLink driver for Ubuntu provided at https://www.displaylink.com/downloads/ubuntu, which I think is the only way to get DisplayLink fully working under Ubuntu? That is, DisplayLink didn't work when I installed the evdi-dkms and libevdi0 Ubuntu packages, and I couldn't find any other packages that might be relevant (did I miss something?) so as far as I can tell the only way to get everything that's needed is from displaylink.com. I'm reporting this issue while logged in under Xorg because I can't report it when logged in with my DisplayLink monitors plugged in under Wayland, for obvious reasons. :-/ ProblemType: BugDistroRelease: Ubuntu 19.10 Package: mutter 3.34.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7 Uname: Linux 5.3.0-23-generi
[Desktop-packages] [Bug 1860930] Re: [Asus GX531GX] Internal speakers are sometimes noisy - bad audio
I couldn't load kernel 5.5 because secure boot was turned on. My bad, sorry. I was able to test the sound with kernel 5.5 after disable secure boot but there is no improvement. The audio is still bad. I'm attaching another file. It sounds like it's a cassette player running out of battery. ** Attachment added: "bad-sound2.m4a" https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1860930/+attachment/5324432/+files/bad-sound2.m4a -- 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/1860930 Title: [Asus GX531GX] Internal speakers are sometimes noisy - bad audio Status in alsa-driver package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: New Bug description: I have an Asus Zephyrus S GX531GX laptop and a pair of Asus Delta USB headphones. When the headphones are plugged in during boot the internal speakers won't work. There is only crackling sound coming from them. It doesn't help in I unplug the headphones. There is no problem if they are not plugged in during boot. I'm using Ubuntu 19.10. Please let me know if you need more information. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: pulseaudio 1:13.0-1ubuntu1.1 ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13 Uname: Linux 5.3.0-26-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 Date: Sun Jan 26 19:26:35 2020 InstallationDate: Installed on 2019-12-19 (38 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=hu_HU.UTF-8 SHELL=/bin/bash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/28/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: GX531GXR.304 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: GX531GXR 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.:bvrGX531GXR.304:bd06/28/2019:svnASUSTeKCOMPUTERINC.:pnZephyrusSGX531GXR_GX531GXR:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGX531GXR:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: Zephyrus S dmi.product.name: Zephyrus S GX531GXR_GX531GXR dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1860930/+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 1861507] Re: Wacom Tablet not recognized in Settings/by System
** Package changed: ubuntu => gnome-control-center (Ubuntu)
--
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/1861507
Title:
Wacom Tablet not recognized in Settings/by System
Status in gnome-control-center package in Ubuntu:
New
Bug description:
I bought a Wacom Intuos CTL-6100Wl and the System does not find the
pad
{{~$ xsetwacom --list devices
Wacom Co.,Ltd. Intuos BT M stylus id: 9 type: STYLUS
Wacom Co.,Ltd. Intuos BT M eraser id: 15 type: ERASER
$ xsetwacom --get 15 area
0 0 21600 13500
$ modinfo wacom | grep version
version:v2.00
srcversion: 82B641C2AB050D7AC9F9757
$ sudo -s 'apt-get update && apt-get install xserver-xorg-input-wacom'
/bin/bash: apt-get update && apt-get install xserver-xorg-input-wacom: Befehl
nicht gefunden
$
}}
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: gnome-control-center 1:3.28.2-0ubuntu0.18.04.6
ProcVersionSignature: Ubuntu 4.15.0-76.86-generic 4.15.18
Uname: Linux 4.15.0-76-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.9
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Fri Jan 31 16:30:09 2020
ExecutablePath: /usr/bin/gnome-control-center
InstallationDate: Installed on 2018-07-17 (562 days ago)
InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64
(20180228)
ProcEnviron:
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=de_DE.UTF-8
SHELL=/bin/bash
SourcePackage: gnome-control-center
UpgradeStatus: Upgraded to bionic on 2018-07-18 (562 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1861507/+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 1861507] [NEW] Wacom Tablet not recognized in Settings/by System
You have been subscribed to a public bug:
I bought a Wacom Intuos CTL-6100Wl and the System does not find the pad
{{~$ xsetwacom --list devices
Wacom Co.,Ltd. Intuos BT M stylus id: 9 type: STYLUS
Wacom Co.,Ltd. Intuos BT M eraser id: 15 type: ERASER
$ xsetwacom --get 15 area
0 0 21600 13500
$ modinfo wacom | grep version
version:v2.00
srcversion: 82B641C2AB050D7AC9F9757
$ sudo -s 'apt-get update && apt-get install xserver-xorg-input-wacom'
/bin/bash: apt-get update && apt-get install xserver-xorg-input-wacom: Befehl
nicht gefunden
$
}}
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: gnome-control-center 1:3.28.2-0ubuntu0.18.04.6
ProcVersionSignature: Ubuntu 4.15.0-76.86-generic 4.15.18
Uname: Linux 4.15.0-76-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.9
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Fri Jan 31 16:30:09 2020
ExecutablePath: /usr/bin/gnome-control-center
InstallationDate: Installed on 2018-07-17 (562 days ago)
InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228)
ProcEnviron:
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=de_DE.UTF-8
SHELL=/bin/bash
SourcePackage: gnome-control-center
UpgradeStatus: Upgraded to bionic on 2018-07-18 (562 days ago)
** Affects: gnome-control-center (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug bionic
--
Wacom Tablet not recognized in Settings/by System
https://bugs.launchpad.net/bugs/1861507
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-control-center 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 1861481] Re: language-options causes live CD sessions to be untranslated
Well, the point with the language-options script is to only list languages where the language-packs are present. It has been that way for many cycles, and AFAIK nothing special happened in this respect in 19.10. @Alkis: Are you claiming that it worked otherwise in e.g. 18.04? With that said, I understand that it's not an optimal approach wrt the live session for a flavor. If we are going to change this somehow (I have no idea how ATM), it should reasonably be done without changing the language-options script. The latter was written with a real install in mind at first hand. ** Changed in: accountsservice (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to accountsservice in Ubuntu. https://bugs.launchpad.net/bugs/1861481 Title: language-options causes live CD sessions to be untranslated Status in accountsservice package in Ubuntu: Incomplete Bug description: Since Ubuntu 19.10, for all Ubuntu live CDs that use LightDM (e.g. MATE and Xubuntu), if a user selects a language in syslinux other than those with an included langpack, the session is then untranslated. For example, if one boots Ubuntu MATE 20.04 and selects Greek in syslinux, he ends up with LANGUAGE=en in the session. The chain of events is: LightDM has an Ubuntu-specific patch that makes it call /usr/share/language-tools/language-options instead of the upstream `locale -a`. `locale -a` does list el_GR as a supported locale because casper correctly updated the locales. But language-options doesn't list el_GR, so it fools LightDM into thinking that Greek aren't supported; while they're all there, since e.g. MATE doesn't rely on langpacks; mate-panel.mo and mate-calc.mo etc are all there. I believe the correct fix would be for language-options to list el_GR on live CDs (to merge the output of locale -a in its output). Thanks! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1861481/+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 1861503] [NEW] libappindicator won't compile because "g_type_class_add_private" deprecated
Public bug reported: Attempting to compile libappindicator 12.10.0 from source fails for me on Artix: app-indicator.c: In function 'app_indicator_init': app-indicator.c:584:13: error: G_ADD_PRIVATE [-Werror] 584 | AppIndicatorPrivate * priv = APP_INDICATOR_GET_PRIVATE(self); | ^~~ cc1: all warnings being treated as errors Research suggests that this is may be because "g_type_class_add_private", which is used in app-indicator.c at line 212, is deprecated by glib2, see: https://blog.gtk.org/2018/07/11/news- from-glib-2-58/ Further research suggests that this may be "solvable" by replacing -werror with -wno-error, but that seems like an untidy band-aid at best. ** Affects: libappindicator (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libappindicator in Ubuntu. https://bugs.launchpad.net/bugs/1861503 Title: libappindicator won't compile because "g_type_class_add_private" deprecated Status in libappindicator package in Ubuntu: New Bug description: Attempting to compile libappindicator 12.10.0 from source fails for me on Artix: app-indicator.c: In function 'app_indicator_init': app-indicator.c:584:13: error: G_ADD_PRIVATE [-Werror] 584 | AppIndicatorPrivate * priv = APP_INDICATOR_GET_PRIVATE(self); | ^~~ cc1: all warnings being treated as errors Research suggests that this is may be because "g_type_class_add_private", which is used in app-indicator.c at line 212, is deprecated by glib2, see: https://blog.gtk.org/2018/07/11 /news-from-glib-2-58/ Further research suggests that this may be "solvable" by replacing -werror with -wno-error, but that seems like an untidy band-aid at best. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libappindicator/+bug/1861503/+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 1861499] [NEW] simple-scan will not load on ubuntu 19.10
Public bug reported: simple-scan will not load after upgrade from 19.04 to 19.10 Error message : simple-scan fstat() failed: Bad file descriptor Failed to create permanent mapping for memfd region with ID = 3372521494 Assertion 'pa_close(ancil->fds[i]) == 0' failed at pulsecore/pstream.c:225, function pa_cmsg_ancil_data_close_fds(). Aborting. Aborted (core dumped) ** Affects: simple-scan (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to simple-scan in Ubuntu. https://bugs.launchpad.net/bugs/1861499 Title: simple-scan will not load on ubuntu 19.10 Status in simple-scan package in Ubuntu: New Bug description: simple-scan will not load after upgrade from 19.04 to 19.10 Error message : simple-scan fstat() failed: Bad file descriptor Failed to create permanent mapping for memfd region with ID = 3372521494 Assertion 'pa_close(ancil->fds[i]) == 0' failed at pulsecore/pstream.c:225, function pa_cmsg_ancil_data_close_fds(). Aborting. Aborted (core dumped) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/simple-scan/+bug/1861499/+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 1741768] Re: U2F FIDO authentication doesn't work
That does imply AppArmor is the issue with that denial; `authenticator-
rs` requires hidraw access to the relevant devices.
https://github.com/amluto/u2f-hidraw-policy is the package used by other
linuxes, I don't know the equivalent for Debian.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
https://bugs.launchpad.net/bugs/1741768
Title:
U2F FIDO authentication doesn't work
Status in firefox package in Ubuntu:
Confirmed
Bug description:
I have a Yubico U2F security key. If I download the upstream Firefox
binary for 57.0.4 and go to https://demo.yubico.com/u2f?tab=register,
the test page works fine: I can register with a username/password, my
key starts blinking and I can touch it to validate.
If I go to the same page using the official Ubuntu package of Firefox,
the U2F device is not recognized and the page displays the following
error:
"""
Registration failed!
Make sure you have a U2F device connected, and try again.
Traceback (most recent call last):
File "/root/python-u2flib-server-demo/examples/yubiauth_server.py", line
161, in __call__
raise Exception("FIDO Client error: %s" % error)
Exception: FIDO Client error: 1 (OTHER ERROR)
"""
Note that in both cases, I did enable the required options in
"about:config" (as outlined in e.g. https://www.yubico.com/2017/11
/how-to-navigate-fido-u2f-in-firefox-quantum/).
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: firefox 57.0.4+build1-0ubuntu0.16.04.1
ProcVersionSignature: Ubuntu 4.13.0-21.24~16.04.1-generic 4.13.13
Uname: Linux 4.13.0-21-generic x86_64
NonfreeKernelModules: zfs zunicode zavl zcommon znvpair nvidia_uvm nvidia_drm
nvidia_modeset nvidia
AddonCompatCheckDisabled: False
ApportVersion: 2.20.1-0ubuntu2.15
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: antoine3844 F pulseaudio
/dev/snd/controlC1: antoine3844 F pulseaudio
BuildID: 20180104112904
Channel: Unavailable
CurrentDesktop: XFCE
Date: Sun Jan 7 17:32:38 2018
DefaultProfileIncompatibleExtensions: Default -
{972ce4c6-7e08-4474-a285-3208198ce6fd}
DefaultProfilePrefErrors: 'utf-8' codec can't decode byte 0xe9 in position
2410: invalid continuation byte
ForcedLayersAccel: False
IfupdownConfig:
# interfaces(5) file used by ifup(8) and ifdown(8)
auto lo
iface lo inet loopback
InstallationDate: Installed on 2013-04-12 (1730 days ago)
InstallationMedia: Xubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130409)
MostRecentCrashID: bp-eb109c63-e3b5-4c21-a920-d262b2150407
Profile1Extensions: extensions.sqlite corrupt or missing
Profile1IncompatibleExtensions: Unavailable (corrupt or non-existant
compatibility.ini or extensions.sqlite)
Profile1Locales: extensions.sqlite corrupt or missing
Profile1PrefSources: prefs.js
Profile1Themes: extensions.sqlite corrupt or missing
Profile2Extensions: extensions.sqlite corrupt or missing
Profile2IncompatibleExtensions: Unavailable (corrupt or non-existant
compatibility.ini or extensions.sqlite)
Profile2Locales: extensions.sqlite corrupt or missing
Profile2PrefSources: prefs.js
Profile2Themes: extensions.sqlite corrupt or missing
Profile3Extensions: extensions.sqlite corrupt or missing
Profile3IncompatibleExtensions: Unavailable (corrupt or non-existant
compatibility.ini or extensions.sqlite)
Profile3Locales: extensions.sqlite corrupt or missing
Profile3PrefSources: prefs.js
Profile3Themes: extensions.sqlite corrupt or missing
Profile4Extensions: extensions.sqlite corrupt or missing
Profile4IncompatibleExtensions: Unavailable (corrupt or non-existant
compatibility.ini or extensions.sqlite)
Profile4Locales: extensions.sqlite corrupt or missing
Profile4PrefSources: prefs.js
Profile4Themes: extensions.sqlite corrupt or missing
Profiles:
Profile0 (Default) - LastVersion=57.0.4/20180104112904 (In use)
Profile1 - LastVersion=57.0.4/20180104112904
Profile2 - LastVersion=57.0.4/20180104112904
Profile3 - LastVersion=57.0.3/20171227151400 (Out of date)
Profile4 - LastVersion=57.0.4/20180104112904 (In use)
RfKill:
RunningIncompatibleAddons: True
SourcePackage: firefox
UpgradeStatus: Upgraded to xenial on 2015-07-27 (894 days ago)
dmi.bios.date: 06/22/2011
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1801
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: P8H67-M EVO
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvr1801:bd06/22/2011:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP8H67-MEVO:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.famil
[Desktop-packages] [Bug 121853] Re: Opening gparted causes Rhythmbox to stop playing
Further to comment #5, no response but report won't expire due to bug watch. Closing as Invalid. ** Changed in: rhythmbox (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to rhythmbox in Ubuntu. https://bugs.launchpad.net/bugs/121853 Title: Opening gparted causes Rhythmbox to stop playing Status in Rhythmbox: Expired Status in rhythmbox package in Ubuntu: Invalid Bug description: Binary package hint: rhythmbox If Rhythmbox is playing a song, opening gparted (System -> Administration -> GNOME Partition Editor) causes Rhythmbox to stop playing and change to the 'Not Playing' status. This occurs during the period when gparted is showing the 'Scanning all devices...' label. Rhythmbox remains 'Not Playing' until the user presses play again. rhythmbox 0.10.0-0ubuntu2 (feisty) gparted 0.2.5-2ubuntu2 (feisty) To manage notifications about this bug go to: https://bugs.launchpad.net/rhythmbox/+bug/121853/+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 1784473] Re: [radeon] Ubuntu boots to a black screen
In my case, the error was caused by a full /home filesystem. I switched to a text terminal (Ctrl Alt F1-7) deleted some files, and after rebooting, it was working. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1784473 Title: [radeon] Ubuntu boots to a black screen Status in linux package in Ubuntu: Confirmed Status in mutter package in Ubuntu: New Bug description: After a fresh install of ubuntu 18.04LTS(dual booted with windows 7) when I selected ubuntu from the grub menu to boot into the OS. But I got a black screen I waited for few seconds but I was still at black screen. So, I forced shutdown the laptop. Again in second attempt to login I got black screen this time I waited for more than a minute and pressed power button once which suspended the pc then I pressed enter and I was presented with login screen. To solve the problem I followed this guide https://askubuntu.com/questions/1029624/ubuntu-18-04-live- boot-leads-to-blank-screen and changed quiet splash to nomodeset quiet splash. After applying this fix there was no black screen at the time of login, but the laptop started to freeze randomly even when left idle for more than 30 mins it would freeze. I had force shutdown each time and this happened very frequently. I again changed nomodeset quiet splash to quiet splash, which again leads to black screen after selecting ubuntu from the grub menu. I also did RAM test using Memtest86 from GRUB and everything was fine systemd-analyze time Startup finished in 6.015s (kernel) + 1min 26.820s (userspace) = 1min 32.836s graphical.target reached after 1min 25.472s in userspace ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Jul 31 00:17:48 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: virtualbox, 5.2.10, 4.15.0-29-generic, x86_64: installed ExtraDebuggingInterest: Yes GpuHangFrequency: Several times a day GpuHangReproducibility: Seems to happen randomly GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Sumo [Radeon HD 6480G] [1002:9648] (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Sumo [Radeon HD 6480G] [103c:3564] InstallationDate: Installed on 2018-07-26 (4 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Hewlett-Packard HP Pavilion g4 Notebook PC ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-29-generic root=UUID=007c6619-ca84-4c0f-8b16-7fa740dc0c3e ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/24/2014 dmi.bios.vendor: Insyde dmi.bios.version: F.6D dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 3564 dmi.board.vendor: Hewlett-Packard dmi.board.version: 21.47 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.6D:bd01/24/2014:svnHewlett-Packard:pnHPPaviliong4NotebookPC:pvr06911320461610100:rvnHewlett-Packard:rn3564:rvr21.47:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV dmi.product.name: HP Pavilion g4 Notebook PC dmi.product.version: 06911320461610100 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 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 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: amit 2479 F pulseaudio /dev/snd/controlC0: amit 2479 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-07-26 (4 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Hewlett-Packard HP Pav
[Desktop-packages] [Bug 1861173] Re: many events with "Failed to get application states: GDBus.Error:org.freedesktop.portal.Error.Failed: Could not get window list: GDBus.Error:org.freedesktop.DBus.Er
*** This bug is a duplicate of bug 1851807 *** https://bugs.launchpad.net/bugs/1851807 Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: xdg-desktop-portal (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xdg-desktop-portal in Ubuntu. https://bugs.launchpad.net/bugs/1861173 Title: many events with "Failed to get application states: GDBus.Error:org.freedesktop.portal.Error.Failed: Could not get window list: GDBus.Error:org.freedesktop.DBus.Error.AccessDenied: App introspection not allowed" in logs Status in xdg-desktop-portal package in Ubuntu: Confirmed Bug description: logs spammed with events: "Failed to get application states: GDBus.Error:org.freedesktop.portal.Error.Failed: Could not get window list: GDBus.Error:org.freedesktop.DBus.Error.AccessDenied: App introspection not allowed" ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xdg-desktop-portal 1.4.2-2 ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13 Uname: Linux 5.3.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Jan 28 19:07:15 2020 InstallationDate: Installed on 2020-01-26 (2 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: xdg-desktop-portal UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal/+bug/1861173/+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 1853638] Re: BCM57416 NetXtreme-E Dual-Media 10G RDMA Ethernet device seems to be dropping data
> NICs between systems? Are OS / kernel and driver > versions the same on both systems? Yes, identical distro release, kernel, and most of the software stack (I have not obtained and examined the full sw stack). Configuration of networking settings is also the same. -- 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/1853638 Title: BCM57416 NetXtreme-E Dual-Media 10G RDMA Ethernet device seems to be dropping data Status in linux package in Ubuntu: Confirmed Status in network-manager package in Ubuntu: Confirmed Bug description: The issue appears to be with the BCM57416 NetXtreme-E Dual-Media 10G RDMA Ethernet device seems to be dropping data Basically, we are dropping data, as you can see from the benchmark tool as follows: tcdforge@x310a:/usr/local/lib/lib/uhd/examples$ ./benchmark_rate --rx_rate 10e6 --tx_rate 10e6 --duration 300 [INFO] [UHD] linux; GNU C++ version 5.4.0 20160609; Boost_105800; UHD_3.14.1.1-0-g98c7c986 [WARNING] [UHD] Unable to set the thread priority. Performance may be negatively affected. Please see the general application notes in the manual for instructions. EnvironmentError: OSError: error in pthread_setschedparam [00:00:00.07] Creating the usrp device with: ... [INFO] [X300] X300 initialization sequence... [INFO] [X300] Maximum frame size: 1472 bytes. [INFO] [X300] Radio 1x clock: 200 MHz [INFO] [GPS] Found an internal GPSDO: LC_XO, Firmware Rev 0.929a [INFO] [0/DmaFIFO_0] Initializing block control (NOC ID: 0xF1F0D000) [INFO] [0/DmaFIFO_0] BIST passed (Throughput: 1308 MB/s) [INFO] [0/DmaFIFO_0] BIST passed (Throughput: 1316 MB/s) [INFO] [0/Radio_0] Initializing block control (NOC ID: 0x12AD1001) [INFO] [0/Radio_1] Initializing block control (NOC ID: 0x12AD1001) [INFO] [0/DDC_0] Initializing block control (NOC ID: 0xDDC0) [INFO] [0/DDC_1] Initializing block control (NOC ID: 0xDDC0) [INFO] [0/DUC_0] Initializing block control (NOC ID: 0xD0C0) [INFO] [0/DUC_1] Initializing block control (NOC ID: 0xD0C0) Using Device: Single USRP: Device: X-Series Device Mboard 0: X310 RX Channel: 0 RX DSP: 0 RX Dboard: A RX Subdev: SBX-120 RX RX Channel: 1 RX DSP: 0 RX Dboard: B RX Subdev: SBX-120 RX TX Channel: 0 TX DSP: 0 TX Dboard: A TX Subdev: SBX-120 TX TX Channel: 1 TX DSP: 0 TX Dboard: B TX Subdev: SBX-120 TX [00:00:04.305374] Setting device timestamp to 0... [WARNING] [UHD] Unable to set the thread priority. Performance may be negatively affected. Please see the general application notes in the manual for instructions. EnvironmentError: OSError: error in pthread_setschedparam [00:00:04.310990] Testing receive rate 10.00 Msps on 1 channels [WARNING] [UHD] Unable to set the thread priority. Performance may be negatively affected. Please see the general application notes in the manual for instructions. EnvironmentError: OSError: error in pthread_setschedparam [00:00:04.318356] Testing transmit rate 10.00 Msps on 1 channels [00:00:06.693119] Detected Rx sequence error. D[00:00:09.402843] Detected Rx sequence error. DD[00:00:40.927978] Detected Rx sequence error. D[00:01:44.982243] Detected Rx sequence error. D[00:02:11.400692] Detected Rx sequence error. D[00:02:14.805292] Detected Rx sequence error. D[00:02:41.875596] Detected Rx sequence error. D[00:03:06.927743] Detected Rx sequence error. D[00:03:47.967891] Detected Rx sequence error. D[00:03:58.233659] Detected Rx sequence error. D[00:03:58.876588] Detected Rx sequence error. D[00:04:03.139770] Detected Rx sequence error. D[00:04:45.287465] Detected Rx sequence error. D[00:04:56.425845] Detected Rx sequence error. D[00:04:57.929209] Detected Rx sequence error. [00:05:04.529548] Benchmark complete. Benchmark rate summary: Num received samples: 2995435936 Num dropped samples: 4622800 Num overruns detected:0 Num transmitted samples: 3008276544 Num sequence errors (Tx): 0 Num sequence errors (Rx): 15 Num underruns detected: 0 Num late commands:0 Num timeouts (Tx):0 Num timeouts (Rx):0 Done! tcdforge@x310a:/usr/local/lib/lib/uhd/examples$ In this particular case description, the nodes are USRP x310s. However, we have the same issue with N210 nodes dropping samples connected to the BCM57416 NetXtreme-E Dual-Media 10G RDMA Ethernet device. There is no problem with the USRPs themselves, as we have tested them with normal 1G network cards and have no dropped samples. Personally I think its something to do with the 10G network card, possibly on a ubuntu driver??? Note, Dell have said there is no hardware problem with the 10G interf
[Desktop-packages] [Bug 1851936] Re: User profile won't load after upgrade - prompt to create new profile
This bug was fixed in the package thunderbird - 1:68.4.2+build2-0ubuntu1
---
thunderbird (1:68.4.2+build2-0ubuntu1) focal; urgency=medium
* New upstream stable release (68.4.2build2)
* Use the upstream Build ID, to ensure it is the same across Ubuntu releases
for a given thunderbird version (LP: #1851936)
- debian/build/create-tarball.py
- debian/build/rules.mk
- debian/config/mozconfig.in
-- Olivier Tilloy Fri, 24 Jan 2020
15:05:19 +0100
** Changed in: thunderbird (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to thunderbird in Ubuntu.
https://bugs.launchpad.net/bugs/1851936
Title:
User profile won't load after upgrade - prompt to create new profile
Status in firefox package in Ubuntu:
Fix Released
Status in thunderbird package in Ubuntu:
Fix Released
Bug description:
Did upgrade to focal fossa from standard Ubuntu 19.10. Existing
firefox profile won't load on starting, instead application wants new
default profile.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: firefox 70.0.1+build1-0ubuntu2
Uname: Linux 5.3.9-050309-generic x86_64
AddonCompatCheckDisabled: False
ApportVersion: 2.20.11-0ubuntu9
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: stefan 1861 F pulseaudio
/dev/snd/controlC0: stefan 1861 F pulseaudio
BuildID: 20191031000133
Channel: Unavailable
CurrentDesktop: ubuntu:GNOME
Date: Sat Nov 9 14:49:28 2019
DefaultProfileIncompatibleExtensions:
Deutsch (DE) Language Pack - langpack...@firefox.mozilla.org
English (GB) Language Pack - langpack-en...@firefox.mozilla.org
English (South Africa) Language Pack - langpack-en...@firefox.mozilla.org
Default - {972ce4c6-7e08-4474-a285-3208198ce6fd}
DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @
/usr/lib/firefox/omni.ja:greprefs.js:930
DefaultProfilePrefSources: prefs.js
ForcedLayersAccel: False
IfupdownConfig:
# interfaces(5) file used by ifup(8) and ifdown(8)
auto lo
iface lo inet loopback
InstallationDate: Installed on 2019-05-02 (190 days ago)
InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64
(20190210)
IpRoute:
default via 192.168.178.1 dev enp30s0 proto dhcp metric 100
169.254.0.0/16 dev enp30s0 scope link metric 1000
192.168.178.0/24 dev enp30s0 proto kernel scope link src 192.168.178.44
metric 100
MostRecentCrashID: bp-926e6dc8-5f4b-4cfe-9446-ace131180317
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=de_DE.UTF-8
SHELL=/bin/bash
Profile1Extensions: extensions.sqlite corrupt or missing
Profile1IncompatibleExtensions: Unavailable (corrupt or non-existant
compatibility.ini or extensions.sqlite)
Profile1Locales: extensions.sqlite corrupt or missing
Profile1PrefErrors: Unexpected character ',' before close parenthesis @
/usr/lib/firefox/omni.ja:greprefs.js:930
Profile1PrefSources: prefs.js
Profile1Themes: extensions.sqlite corrupt or missing
Profiles:
Profile1 - LastVersion=70.0.1/20191031000133 (In use)
Profile0 (Default) - LastVersion=70.0.1/20191031091608 (Out of date)
RunningIncompatibleAddons: True
SourcePackage: firefox
SubmittedCrashIDs: bp-926e6dc8-5f4b-4cfe-9446-ace131180317
UpgradeStatus: Upgraded to focal on 2019-11-09 (0 days ago)
dmi.bios.date: 04/23/2019
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P5.80
dmi.board.name: AB350M-HDV
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.:bvrP5.80:bd04/23/2019:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnAB350M-HDV: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.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1851936/+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 1853638] Re: BCM57416 NetXtreme-E Dual-Media 10G RDMA Ethernet device seems to be dropping data
Thanks very much for helping on this, Edwin! Please let me know if there's anything specific you need. I'm asking them to disable any IPv6, LLDP traffic in their environment, and retest and collect information again. Also, I'd like to disable tpa, would this be at all useful: modprobe bnx disable_tpa=1 ?? -- 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/1853638 Title: BCM57416 NetXtreme-E Dual-Media 10G RDMA Ethernet device seems to be dropping data Status in linux package in Ubuntu: Confirmed Status in network-manager package in Ubuntu: Confirmed Bug description: The issue appears to be with the BCM57416 NetXtreme-E Dual-Media 10G RDMA Ethernet device seems to be dropping data Basically, we are dropping data, as you can see from the benchmark tool as follows: tcdforge@x310a:/usr/local/lib/lib/uhd/examples$ ./benchmark_rate --rx_rate 10e6 --tx_rate 10e6 --duration 300 [INFO] [UHD] linux; GNU C++ version 5.4.0 20160609; Boost_105800; UHD_3.14.1.1-0-g98c7c986 [WARNING] [UHD] Unable to set the thread priority. Performance may be negatively affected. Please see the general application notes in the manual for instructions. EnvironmentError: OSError: error in pthread_setschedparam [00:00:00.07] Creating the usrp device with: ... [INFO] [X300] X300 initialization sequence... [INFO] [X300] Maximum frame size: 1472 bytes. [INFO] [X300] Radio 1x clock: 200 MHz [INFO] [GPS] Found an internal GPSDO: LC_XO, Firmware Rev 0.929a [INFO] [0/DmaFIFO_0] Initializing block control (NOC ID: 0xF1F0D000) [INFO] [0/DmaFIFO_0] BIST passed (Throughput: 1308 MB/s) [INFO] [0/DmaFIFO_0] BIST passed (Throughput: 1316 MB/s) [INFO] [0/Radio_0] Initializing block control (NOC ID: 0x12AD1001) [INFO] [0/Radio_1] Initializing block control (NOC ID: 0x12AD1001) [INFO] [0/DDC_0] Initializing block control (NOC ID: 0xDDC0) [INFO] [0/DDC_1] Initializing block control (NOC ID: 0xDDC0) [INFO] [0/DUC_0] Initializing block control (NOC ID: 0xD0C0) [INFO] [0/DUC_1] Initializing block control (NOC ID: 0xD0C0) Using Device: Single USRP: Device: X-Series Device Mboard 0: X310 RX Channel: 0 RX DSP: 0 RX Dboard: A RX Subdev: SBX-120 RX RX Channel: 1 RX DSP: 0 RX Dboard: B RX Subdev: SBX-120 RX TX Channel: 0 TX DSP: 0 TX Dboard: A TX Subdev: SBX-120 TX TX Channel: 1 TX DSP: 0 TX Dboard: B TX Subdev: SBX-120 TX [00:00:04.305374] Setting device timestamp to 0... [WARNING] [UHD] Unable to set the thread priority. Performance may be negatively affected. Please see the general application notes in the manual for instructions. EnvironmentError: OSError: error in pthread_setschedparam [00:00:04.310990] Testing receive rate 10.00 Msps on 1 channels [WARNING] [UHD] Unable to set the thread priority. Performance may be negatively affected. Please see the general application notes in the manual for instructions. EnvironmentError: OSError: error in pthread_setschedparam [00:00:04.318356] Testing transmit rate 10.00 Msps on 1 channels [00:00:06.693119] Detected Rx sequence error. D[00:00:09.402843] Detected Rx sequence error. DD[00:00:40.927978] Detected Rx sequence error. D[00:01:44.982243] Detected Rx sequence error. D[00:02:11.400692] Detected Rx sequence error. D[00:02:14.805292] Detected Rx sequence error. D[00:02:41.875596] Detected Rx sequence error. D[00:03:06.927743] Detected Rx sequence error. D[00:03:47.967891] Detected Rx sequence error. D[00:03:58.233659] Detected Rx sequence error. D[00:03:58.876588] Detected Rx sequence error. D[00:04:03.139770] Detected Rx sequence error. D[00:04:45.287465] Detected Rx sequence error. D[00:04:56.425845] Detected Rx sequence error. D[00:04:57.929209] Detected Rx sequence error. [00:05:04.529548] Benchmark complete. Benchmark rate summary: Num received samples: 2995435936 Num dropped samples: 4622800 Num overruns detected:0 Num transmitted samples: 3008276544 Num sequence errors (Tx): 0 Num sequence errors (Rx): 15 Num underruns detected: 0 Num late commands:0 Num timeouts (Tx):0 Num timeouts (Rx):0 Done! tcdforge@x310a:/usr/local/lib/lib/uhd/examples$ In this particular case description, the nodes are USRP x310s. However, we have the same issue with N210 nodes dropping samples connected to the BCM57416 NetXtreme-E Dual-Media 10G RDMA Ethernet device. There is no problem with the USRPs themselves, as we have tested them with normal 1G network cards and have no dropped samples. Personally I think its something to do with the 10G network card, possibly on a ubuntu driver??? Note, Dell have said there is
[Desktop-packages] [Bug 1853638] Re: BCM57416 NetXtreme-E Dual-Media 10G RDMA Ethernet device seems to be dropping data
> There are more than one variable at play here. > Does the problem follow the NIC if you swap the > NICs between systems? Are OS / kernel and driver > versions the same on both systems? Unfortunately, I've not been able to get them to try permutations or switches, as yet, as this is still a production system/environment. I'll try and obtain more information about it. -- 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/1853638 Title: BCM57416 NetXtreme-E Dual-Media 10G RDMA Ethernet device seems to be dropping data Status in linux package in Ubuntu: Confirmed Status in network-manager package in Ubuntu: Confirmed Bug description: The issue appears to be with the BCM57416 NetXtreme-E Dual-Media 10G RDMA Ethernet device seems to be dropping data Basically, we are dropping data, as you can see from the benchmark tool as follows: tcdforge@x310a:/usr/local/lib/lib/uhd/examples$ ./benchmark_rate --rx_rate 10e6 --tx_rate 10e6 --duration 300 [INFO] [UHD] linux; GNU C++ version 5.4.0 20160609; Boost_105800; UHD_3.14.1.1-0-g98c7c986 [WARNING] [UHD] Unable to set the thread priority. Performance may be negatively affected. Please see the general application notes in the manual for instructions. EnvironmentError: OSError: error in pthread_setschedparam [00:00:00.07] Creating the usrp device with: ... [INFO] [X300] X300 initialization sequence... [INFO] [X300] Maximum frame size: 1472 bytes. [INFO] [X300] Radio 1x clock: 200 MHz [INFO] [GPS] Found an internal GPSDO: LC_XO, Firmware Rev 0.929a [INFO] [0/DmaFIFO_0] Initializing block control (NOC ID: 0xF1F0D000) [INFO] [0/DmaFIFO_0] BIST passed (Throughput: 1308 MB/s) [INFO] [0/DmaFIFO_0] BIST passed (Throughput: 1316 MB/s) [INFO] [0/Radio_0] Initializing block control (NOC ID: 0x12AD1001) [INFO] [0/Radio_1] Initializing block control (NOC ID: 0x12AD1001) [INFO] [0/DDC_0] Initializing block control (NOC ID: 0xDDC0) [INFO] [0/DDC_1] Initializing block control (NOC ID: 0xDDC0) [INFO] [0/DUC_0] Initializing block control (NOC ID: 0xD0C0) [INFO] [0/DUC_1] Initializing block control (NOC ID: 0xD0C0) Using Device: Single USRP: Device: X-Series Device Mboard 0: X310 RX Channel: 0 RX DSP: 0 RX Dboard: A RX Subdev: SBX-120 RX RX Channel: 1 RX DSP: 0 RX Dboard: B RX Subdev: SBX-120 RX TX Channel: 0 TX DSP: 0 TX Dboard: A TX Subdev: SBX-120 TX TX Channel: 1 TX DSP: 0 TX Dboard: B TX Subdev: SBX-120 TX [00:00:04.305374] Setting device timestamp to 0... [WARNING] [UHD] Unable to set the thread priority. Performance may be negatively affected. Please see the general application notes in the manual for instructions. EnvironmentError: OSError: error in pthread_setschedparam [00:00:04.310990] Testing receive rate 10.00 Msps on 1 channels [WARNING] [UHD] Unable to set the thread priority. Performance may be negatively affected. Please see the general application notes in the manual for instructions. EnvironmentError: OSError: error in pthread_setschedparam [00:00:04.318356] Testing transmit rate 10.00 Msps on 1 channels [00:00:06.693119] Detected Rx sequence error. D[00:00:09.402843] Detected Rx sequence error. DD[00:00:40.927978] Detected Rx sequence error. D[00:01:44.982243] Detected Rx sequence error. D[00:02:11.400692] Detected Rx sequence error. D[00:02:14.805292] Detected Rx sequence error. D[00:02:41.875596] Detected Rx sequence error. D[00:03:06.927743] Detected Rx sequence error. D[00:03:47.967891] Detected Rx sequence error. D[00:03:58.233659] Detected Rx sequence error. D[00:03:58.876588] Detected Rx sequence error. D[00:04:03.139770] Detected Rx sequence error. D[00:04:45.287465] Detected Rx sequence error. D[00:04:56.425845] Detected Rx sequence error. D[00:04:57.929209] Detected Rx sequence error. [00:05:04.529548] Benchmark complete. Benchmark rate summary: Num received samples: 2995435936 Num dropped samples: 4622800 Num overruns detected:0 Num transmitted samples: 3008276544 Num sequence errors (Tx): 0 Num sequence errors (Rx): 15 Num underruns detected: 0 Num late commands:0 Num timeouts (Tx):0 Num timeouts (Rx):0 Done! tcdforge@x310a:/usr/local/lib/lib/uhd/examples$ In this particular case description, the nodes are USRP x310s. However, we have the same issue with N210 nodes dropping samples connected to the BCM57416 NetXtreme-E Dual-Media 10G RDMA Ethernet device. There is no problem with the USRPs themselves, as we have tested them with normal 1G network cards and have no dropped samples. Personally I think its something to do with the 10G network card,
[Desktop-packages] [Bug 1853638] Re: BCM57416 NetXtreme-E Dual-Media 10G RDMA Ethernet device seems to be dropping data
> The mtr packet loss is an interesting result. What mtr options did you use? Is this a UDP or ICMP test? The mtr command was: mtr --no-dns --report --report-cycles 60 $IP_ADDR so ICMP was going out. -- 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/1853638 Title: BCM57416 NetXtreme-E Dual-Media 10G RDMA Ethernet device seems to be dropping data Status in linux package in Ubuntu: Confirmed Status in network-manager package in Ubuntu: Confirmed Bug description: The issue appears to be with the BCM57416 NetXtreme-E Dual-Media 10G RDMA Ethernet device seems to be dropping data Basically, we are dropping data, as you can see from the benchmark tool as follows: tcdforge@x310a:/usr/local/lib/lib/uhd/examples$ ./benchmark_rate --rx_rate 10e6 --tx_rate 10e6 --duration 300 [INFO] [UHD] linux; GNU C++ version 5.4.0 20160609; Boost_105800; UHD_3.14.1.1-0-g98c7c986 [WARNING] [UHD] Unable to set the thread priority. Performance may be negatively affected. Please see the general application notes in the manual for instructions. EnvironmentError: OSError: error in pthread_setschedparam [00:00:00.07] Creating the usrp device with: ... [INFO] [X300] X300 initialization sequence... [INFO] [X300] Maximum frame size: 1472 bytes. [INFO] [X300] Radio 1x clock: 200 MHz [INFO] [GPS] Found an internal GPSDO: LC_XO, Firmware Rev 0.929a [INFO] [0/DmaFIFO_0] Initializing block control (NOC ID: 0xF1F0D000) [INFO] [0/DmaFIFO_0] BIST passed (Throughput: 1308 MB/s) [INFO] [0/DmaFIFO_0] BIST passed (Throughput: 1316 MB/s) [INFO] [0/Radio_0] Initializing block control (NOC ID: 0x12AD1001) [INFO] [0/Radio_1] Initializing block control (NOC ID: 0x12AD1001) [INFO] [0/DDC_0] Initializing block control (NOC ID: 0xDDC0) [INFO] [0/DDC_1] Initializing block control (NOC ID: 0xDDC0) [INFO] [0/DUC_0] Initializing block control (NOC ID: 0xD0C0) [INFO] [0/DUC_1] Initializing block control (NOC ID: 0xD0C0) Using Device: Single USRP: Device: X-Series Device Mboard 0: X310 RX Channel: 0 RX DSP: 0 RX Dboard: A RX Subdev: SBX-120 RX RX Channel: 1 RX DSP: 0 RX Dboard: B RX Subdev: SBX-120 RX TX Channel: 0 TX DSP: 0 TX Dboard: A TX Subdev: SBX-120 TX TX Channel: 1 TX DSP: 0 TX Dboard: B TX Subdev: SBX-120 TX [00:00:04.305374] Setting device timestamp to 0... [WARNING] [UHD] Unable to set the thread priority. Performance may be negatively affected. Please see the general application notes in the manual for instructions. EnvironmentError: OSError: error in pthread_setschedparam [00:00:04.310990] Testing receive rate 10.00 Msps on 1 channels [WARNING] [UHD] Unable to set the thread priority. Performance may be negatively affected. Please see the general application notes in the manual for instructions. EnvironmentError: OSError: error in pthread_setschedparam [00:00:04.318356] Testing transmit rate 10.00 Msps on 1 channels [00:00:06.693119] Detected Rx sequence error. D[00:00:09.402843] Detected Rx sequence error. DD[00:00:40.927978] Detected Rx sequence error. D[00:01:44.982243] Detected Rx sequence error. D[00:02:11.400692] Detected Rx sequence error. D[00:02:14.805292] Detected Rx sequence error. D[00:02:41.875596] Detected Rx sequence error. D[00:03:06.927743] Detected Rx sequence error. D[00:03:47.967891] Detected Rx sequence error. D[00:03:58.233659] Detected Rx sequence error. D[00:03:58.876588] Detected Rx sequence error. D[00:04:03.139770] Detected Rx sequence error. D[00:04:45.287465] Detected Rx sequence error. D[00:04:56.425845] Detected Rx sequence error. D[00:04:57.929209] Detected Rx sequence error. [00:05:04.529548] Benchmark complete. Benchmark rate summary: Num received samples: 2995435936 Num dropped samples: 4622800 Num overruns detected:0 Num transmitted samples: 3008276544 Num sequence errors (Tx): 0 Num sequence errors (Rx): 15 Num underruns detected: 0 Num late commands:0 Num timeouts (Tx):0 Num timeouts (Rx):0 Done! tcdforge@x310a:/usr/local/lib/lib/uhd/examples$ In this particular case description, the nodes are USRP x310s. However, we have the same issue with N210 nodes dropping samples connected to the BCM57416 NetXtreme-E Dual-Media 10G RDMA Ethernet device. There is no problem with the USRPs themselves, as we have tested them with normal 1G network cards and have no dropped samples. Personally I think its something to do with the 10G network card, possibly on a ubuntu driver??? Note, Dell have said there is no hardware problem with the 10G interfaces I have followed the troubleshooting information on this lin
[Desktop-packages] [Bug 1098050] Re: Default Xv output is tearing without compositing
*** This bug is a duplicate of bug 1754284 *** https://bugs.launchpad.net/bugs/1754284 ** This bug has been marked a duplicate of bug 1754284 Fullscreen windows are tearing in Xorg sessions -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu. https://bugs.launchpad.net/bugs/1098050 Title: Default Xv output is tearing without compositing Status in fglrx-installer package in Ubuntu: New Status in xserver-xorg-video-intel package in Ubuntu: Fix Released Bug description: This is to record the fact that the default Xv output on Intel and fglrx [add if more such drivers] is tearing, if no compositing is used. The open radeon driver is tear-free. Compositing would be disabled with the help of the new unredirect fullscreen windows feature in Compiz to improve performance, but is currently not for various video players because of this bug. On older Intel hardware, setting the default of XvPreferOverlay to true in xorg.conf should fix the issue, but it does not help with newer hardware like Sandy Bridge or Ivy Bridge. On fglrx, the enabling the "tear free" setting does fix tearing in fullscreen videos, the vsync option alone does not. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/1098050/+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 1861481] Re: language-options causes live CD sessions to be untranslated
Gunnar, you know probably that script best, could you maybe have a look to what changed in 19.10 to create the issue? ** Changed in: accountsservice (Ubuntu) Importance: Undecided => High ** Tags added: rls-ff-incoming -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to accountsservice in Ubuntu. https://bugs.launchpad.net/bugs/1861481 Title: language-options causes live CD sessions to be untranslated Status in accountsservice package in Ubuntu: New Bug description: Since Ubuntu 19.10, for all Ubuntu live CDs that use LightDM (e.g. MATE and Xubuntu), if a user selects a language in syslinux other than those with an included langpack, the session is then untranslated. For example, if one boots Ubuntu MATE 20.04 and selects Greek in syslinux, he ends up with LANGUAGE=en in the session. The chain of events is: LightDM has an Ubuntu-specific patch that makes it call /usr/share/language-tools/language-options instead of the upstream `locale -a`. `locale -a` does list el_GR as a supported locale because casper correctly updated the locales. But language-options doesn't list el_GR, so it fools LightDM into thinking that Greek aren't supported; while they're all there, since e.g. MATE doesn't rely on langpacks; mate-panel.mo and mate-calc.mo etc are all there. I believe the correct fix would be for language-options to list el_GR on live CDs (to merge the output of locale -a in its output). Thanks! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1861481/+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 1754284] Re: Fullscreen windows (like Totem) are tearing in Xorg sessions
I've moved some old tearing bugs in here since I now understand it's
just a bug in the Xorg modesetting driver, which is the one that most
machines use:
https://gitlab.freedesktop.org/xorg/xserver/issues/244
** Summary changed:
- Fullscreen windows (like Totem) are tearing in gnome-shell Xorg sessions
+ Fullscreen windows (like Totem) are tearing in Xorg sessions
** Summary changed:
- Fullscreen windows (like Totem) are tearing in Xorg sessions
+ Fullscreen windows are tearing in Xorg sessions
--
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/1754284
Title:
Fullscreen windows are tearing in Xorg sessions
Status in X.Org X server:
New
Status in xorg-server package in Ubuntu:
Triaged
Bug description:
Fullscreen windows (like Totem) are tearing in gnome-shell Xorg
sessions.
This is probably to do with composite unredirecting... In compiz we
have a workaround to avoid this tearing by disallowing unredirect
("bypass") in known problematic video players. But I'm not sure if
mutter has such a workaround/whitelist/blacklist we can use.
To manage notifications about this bug go to:
https://bugs.launchpad.net/xorg-server/+bug/1754284/+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 1861481] [NEW] language-options causes live CD sessions to be untranslated
Public bug reported: Since Ubuntu 19.10, for all Ubuntu live CDs that use LightDM (e.g. MATE and Xubuntu), if a user selects a language in syslinux other than those with an included langpack, the session is then untranslated. For example, if one boots Ubuntu MATE 20.04 and selects Greek in syslinux, he ends up with LANGUAGE=en in the session. The chain of events is: LightDM has an Ubuntu-specific patch that makes it call /usr/share/language-tools/language-options instead of the upstream `locale -a`. `locale -a` does list el_GR as a supported locale because casper correctly updated the locales. But language-options doesn't list el_GR, so it fools LightDM into thinking that Greek aren't supported; while they're all there, since e.g. MATE doesn't rely on langpacks; mate-panel.mo and mate-calc.mo etc are all there. I believe the correct fix would be for language-options to list el_GR on live CDs (to merge the output of locale -a in its output). Thanks! ** Affects: accountsservice (Ubuntu) Importance: High Status: New ** Tags: rls-ff-incoming -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to accountsservice in Ubuntu. https://bugs.launchpad.net/bugs/1861481 Title: language-options causes live CD sessions to be untranslated Status in accountsservice package in Ubuntu: New Bug description: Since Ubuntu 19.10, for all Ubuntu live CDs that use LightDM (e.g. MATE and Xubuntu), if a user selects a language in syslinux other than those with an included langpack, the session is then untranslated. For example, if one boots Ubuntu MATE 20.04 and selects Greek in syslinux, he ends up with LANGUAGE=en in the session. The chain of events is: LightDM has an Ubuntu-specific patch that makes it call /usr/share/language-tools/language-options instead of the upstream `locale -a`. `locale -a` does list el_GR as a supported locale because casper correctly updated the locales. But language-options doesn't list el_GR, so it fools LightDM into thinking that Greek aren't supported; while they're all there, since e.g. MATE doesn't rely on langpacks; mate-panel.mo and mate-calc.mo etc are all there. I believe the correct fix would be for language-options to list el_GR on live CDs (to merge the output of locale -a in its output). Thanks! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1861481/+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 1860522] Re: Mesa 19.2.8 stable release
This bug was fixed in the package mesa - 19.2.8-0ubuntu0~18.04.1 --- mesa (19.2.8-0ubuntu0~18.04.1) bionic; urgency=medium * New bugfix release. (LP: #1860522) * Revert-meson-fix-logic-for-generating-.pc-files-with.patch: Dropped, fixed upstream. * rules: GLESv2 libs aren't built anymore, drop removing them. * mesa-common-dev: Drop mangled GL/GLX headers, they're not generated anymore. -- Timo Aaltonen Wed, 22 Jan 2020 11:57:11 +0200 ** Changed in: mesa (Ubuntu Bionic) Status: Fix Committed => Fix Released -- 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/1860522 Title: Mesa 19.2.8 stable release Status in mesa package in Ubuntu: Invalid Status in mesa source package in Bionic: Fix Released Status in mesa source package in Eoan: Fix Released Bug description: [Impact] 19.10 released with mesa 19.2.1. We need the last point release of the 19.2.x series in eoan and backported for bionic. [Test case] Check on intel/radeon hw that things still work fine. [Regression potential] This is the last update of the series, all regressions should be shaken off at this point by upstream CI/community To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1860522/+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 1861391] Re: Full-screen window flickers once when switching to it
Thanks and sorry for the trouble... I think this is either a bug in Mutter's fullscreen unredirect feature (which exists for Xorg sessions only), or it could be another instance of bug 561370 which is very intermittent. To prove the issue is NOT bug 561370 we would probably need to see the same flickering in a non-GTK app. ** Package changed: gnome-shell (Ubuntu) => mutter (Ubuntu) ** Changed in: mutter (Ubuntu) Importance: Undecided => Low ** Changed in: mutter (Ubuntu) Status: Incomplete => 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/1861391 Title: Full-screen window flickers once when switching to it Status in mutter package in Ubuntu: New Bug description: When using *some* applications (I observed it with Emacs and gnome- terminal) in full-screen mode, they flicker once shortly after switching to them with e.g. Alt-Tab. To reproduce it: 1. Open Emacs in full-screen mode and one other application (e.g. Chromium). 2. Switch to the other app with Alt-Tab. 3. Switch back to Emacs. Then I observe: 1. Emacs becomes visible. 2. After a fraction of a second, the Emacs windows is transparent for a very very short time (flicker). 3. Then, the windows is stable and usable. Usually, I do not observe this behaviour right from the start. I have to work with the computer for a couple of minutes to see it. I have been unable to find out whether a certain action triggers the problem. However, when it occurs, it does not go away again until the next restart of the X server. This is regression that I observe since Ubuntu 19.10. Changes of the graphics driver does not change anything, however, switching to Wayland solves the problem. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2019-11-16 (75 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Package: mutter 3.34.1+git20191107-1ubuntu1~19.10.1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13 Tags: eoan Uname: Linux 5.3.0-29-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1861391/+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 1861391] Re: Full-screen window flickers once when switching to it
** Attachment added: "dpkgs.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1861391/+attachment/5324387/+files/dpkgs.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/1861391 Title: Full-screen window flickers once when switching to it Status in gnome-shell package in Ubuntu: Incomplete Bug description: When using *some* applications (I observed it with Emacs and gnome- terminal) in full-screen mode, they flicker once shortly after switching to them with e.g. Alt-Tab. To reproduce it: 1. Open Emacs in full-screen mode and one other application (e.g. Chromium). 2. Switch to the other app with Alt-Tab. 3. Switch back to Emacs. Then I observe: 1. Emacs becomes visible. 2. After a fraction of a second, the Emacs windows is transparent for a very very short time (flicker). 3. Then, the windows is stable and usable. Usually, I do not observe this behaviour right from the start. I have to work with the computer for a couple of minutes to see it. I have been unable to find out whether a certain action triggers the problem. However, when it occurs, it does not go away again until the next restart of the X server. This is regression that I observe since Ubuntu 19.10. Changes of the graphics driver does not change anything, however, switching to Wayland solves the problem. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2019-11-16 (75 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Package: mutter 3.34.1+git20191107-1ubuntu1~19.10.1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13 Tags: eoan Uname: Linux 5.3.0-29-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1861391/+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 1861391] Re: Full-screen window flickers once when switching to it
** Attachment added: "journal.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1861391/+attachment/5324388/+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/1861391 Title: Full-screen window flickers once when switching to it Status in gnome-shell package in Ubuntu: Incomplete Bug description: When using *some* applications (I observed it with Emacs and gnome- terminal) in full-screen mode, they flicker once shortly after switching to them with e.g. Alt-Tab. To reproduce it: 1. Open Emacs in full-screen mode and one other application (e.g. Chromium). 2. Switch to the other app with Alt-Tab. 3. Switch back to Emacs. Then I observe: 1. Emacs becomes visible. 2. After a fraction of a second, the Emacs windows is transparent for a very very short time (flicker). 3. Then, the windows is stable and usable. Usually, I do not observe this behaviour right from the start. I have to work with the computer for a couple of minutes to see it. I have been unable to find out whether a certain action triggers the problem. However, when it occurs, it does not go away again until the next restart of the X server. This is regression that I observe since Ubuntu 19.10. Changes of the graphics driver does not change anything, however, switching to Wayland solves the problem. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2019-11-16 (75 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Package: mutter 3.34.1+git20191107-1ubuntu1~19.10.1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13 Tags: eoan Uname: Linux 5.3.0-29-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1861391/+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 1861391] Re: Full-screen window flickers once when switching to it
** Attachment added: "lspcik.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1861391/+attachment/5324389/+files/lspcik.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/1861391 Title: Full-screen window flickers once when switching to it Status in gnome-shell package in Ubuntu: Incomplete Bug description: When using *some* applications (I observed it with Emacs and gnome- terminal) in full-screen mode, they flicker once shortly after switching to them with e.g. Alt-Tab. To reproduce it: 1. Open Emacs in full-screen mode and one other application (e.g. Chromium). 2. Switch to the other app with Alt-Tab. 3. Switch back to Emacs. Then I observe: 1. Emacs becomes visible. 2. After a fraction of a second, the Emacs windows is transparent for a very very short time (flicker). 3. Then, the windows is stable and usable. Usually, I do not observe this behaviour right from the start. I have to work with the computer for a couple of minutes to see it. I have been unable to find out whether a certain action triggers the problem. However, when it occurs, it does not go away again until the next restart of the X server. This is regression that I observe since Ubuntu 19.10. Changes of the graphics driver does not change anything, however, switching to Wayland solves the problem. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2019-11-16 (75 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Package: mutter 3.34.1+git20191107-1ubuntu1~19.10.1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13 Tags: eoan Uname: Linux 5.3.0-29-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1861391/+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 1861391] Re: Full-screen window flickers once when switching to it
** Attachment added: "dmesg.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1861391/+attachment/5324386/+files/dmesg.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/1861391 Title: Full-screen window flickers once when switching to it Status in gnome-shell package in Ubuntu: Incomplete Bug description: When using *some* applications (I observed it with Emacs and gnome- terminal) in full-screen mode, they flicker once shortly after switching to them with e.g. Alt-Tab. To reproduce it: 1. Open Emacs in full-screen mode and one other application (e.g. Chromium). 2. Switch to the other app with Alt-Tab. 3. Switch back to Emacs. Then I observe: 1. Emacs becomes visible. 2. After a fraction of a second, the Emacs windows is transparent for a very very short time (flicker). 3. Then, the windows is stable and usable. Usually, I do not observe this behaviour right from the start. I have to work with the computer for a couple of minutes to see it. I have been unable to find out whether a certain action triggers the problem. However, when it occurs, it does not go away again until the next restart of the X server. This is regression that I observe since Ubuntu 19.10. Changes of the graphics driver does not change anything, however, switching to Wayland solves the problem. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2019-11-16 (75 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Package: mutter 3.34.1+git20191107-1ubuntu1~19.10.1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13 Tags: eoan Uname: Linux 5.3.0-29-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1861391/+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
