[Desktop-packages] [Bug 1985057] Re: Camera output freeze when using pipewiresrc
** Changed in: oem-priority Status: Fix Released => New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pipewire in Ubuntu. https://bugs.launchpad.net/bugs/1985057 Title: Camera output freeze when using pipewiresrc Status in OEM Priority Project: New Status in pipewire package in Ubuntu: Fix Released Status in pipewire source package in Jammy: Triaged Bug description: [Impact] On Dell platform with Microdia Integrated webcam, the Cheese preview is stuck on jammy. The gst-launch-1.0 command suggested by gst-device-monitor-1.0 can reproduce it too. [Test Plan] 1. Install Jammy on the hardware issue reported, and hardware didn't report the issue to avoid the regression hardware list: a. 0bda:58ff Realtek Semiconductor Corp. Integrated_Webcam_HD b. 0c45:6747 Microdia Integrated_Webcam_HD c. 0c45:6a14 Microdia Integrated_Webcam_HD d. 1bcf:28d0 Sunplus Innovation Technology Inc. Integrated_Webcam_5M e. 04f2:b76b Chicony Electronics Co., Ltd HP HD Camera f. 0408:545a Quanta Computer, Inc. HP 5MP Camera g. 0408:5483 Quanta Computer, Inc. HP HD Camera h. 174f:2459 Syntek Integrated Camera (ThinkBook 14 Gen 4) i. 5986:116d Acer, Inc Integrated Camera (ThinkCentre Neo 50a) j. 0bda:5556 Realtek Semiconductor Corp. Integrated_Webcam_FHD 2. try to install the updated pipewire packages (= 0.3.48-1ubuntu2) 3. $ sudo reboot 4. Check if gst-launch-1.0 work a. $ gst-device-monitor-1.0 Video/Source to get caps and suggest gst-launch-1.0 command b. $ gst-launch-1.0 pipewiresrc path= ! ! decodebin ! videoconvert ! glimagesink c. Check if the result ok 5. Check the screencast function by pressing 'prt sc' a. the screenshot of all screen/selected region should work good b. the screenrecord of all screen/selected region should work good 6. Check that video recording in gnome-shell works - use Ctrl+Shift+Alt+R to start a recording, stop it from the indicator, verify that there is a new entry in ~/Video 7. Check that screen sharing is working - go to settings, screen sharing and enable the feature - try to connect using rdp/vnc from another client do those steps under wayland and unset X [Where problems could occur] The patches try to dequeue the shared buffer, instead of pool buffer to prevent the pool buffer being corrupted. it might cause some camera preview failed if shared buffer is corrupted. It is in upstream from 0.3.52 to 0.3.56, and there is no regression found, so the risk is low. [Other Info] Upstream commits: https://gitlab.freedesktop.org/pipewire/pipewire/-/commit/7cc509b117a6db66c395fb56ac4f17fb8cbd0c92 https://gitlab.freedesktop.org/pipewire/pipewire/-/commit/a1f33a99df5756c3dedd68f5ba2690819098d14f To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1985057/+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 1999299] Re: filename cannot be changed in the "save" dialogue
accidentally posted on texlive, so I changed it to the correct package. ** Package changed: texlive-base (Ubuntu) => nautilus (Ubuntu) -- 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/1999299 Title: filename cannot be changed in the "save" dialogue Status in nautilus package in Ubuntu: New Bug description: Minimum required condition for recreation. Ubuntu 20.04 kernel 5.15.0-53-generic Model XPS-13 Chrome 07.0.5304.121 (Official Build) (64-bit) NOTE: that this occurs not just in chrome, but any application that uses the system's default save dialogue. For example, in Google Chrome, I press Control-S to save a webpage. When doing so, a save dialogue appears for specifying the name and directory of the file. When I press any key to modify the name of a file, a letter is inserted into a search window instead of the filename section. It occurs in any web browsers or software which use this system's default save dialogue for specifying a filename and directory. I thought it is a bug in the filesystem (Nautilus). I'm reporting it here. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1999299/+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 1999299] Re: filename cannot be changed in the "save" dialogue
-- You received this bug notification because you are a member of Desktop Packages, which is subscribed to texlive-base in Ubuntu. https://bugs.launchpad.net/bugs/1999299 Title: filename cannot be changed in the "save" dialogue Status in nautilus package in Ubuntu: New Bug description: Minimum required condition for recreation. Ubuntu 20.04 kernel 5.15.0-53-generic Model XPS-13 Chrome 07.0.5304.121 (Official Build) (64-bit) NOTE: that this occurs not just in chrome, but any application that uses the system's default save dialogue. For example, in Google Chrome, I press Control-S to save a webpage. When doing so, a save dialogue appears for specifying the name and directory of the file. When I press any key to modify the name of a file, a letter is inserted into a search window instead of the filename section. It occurs in any web browsers or software which use this system's default save dialogue for specifying a filename and directory. I thought it is a bug in the filesystem (Nautilus). I'm reporting it here. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1999299/+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 2000487] [NEW] Monitor não puxa a resolução padrão e Gravação de Tela sem Vídeo
Public bug reported: Olá, gostaria de relatar alguns problemas que estou sofrendo nesta versão (Ubuntu 22.04) e sofria na versão anterior (Ubuntu 20.04). Na versão anterior não consegui por padrão fazer uso da resolução padrão, mais consegui através de um script que criei pesquisando no Google logo usava a resolução padrão desta forma. Mais infelizmente nessa atual não consigo fazer uso do mesmo script e estou sofrendo as consequencias. Sobre a gravação de Tela sempre que faço uso do software Kazam as gravações saem com a tela preta sem vídeo ou som. Esses são meus problemas e pelo que pesquisei pelo Google de outros usuários, infelizmente. (Pt-Br) Hello, I would like to report some problems that I am suffering from in this version (Ubuntu 22.04) and suffered from in the previous version (Ubuntu 20.04). In the previous version, I was not able to make use of the default resolution by default, but I managed through a script that I created by searching Google, so it used the default resolution in this way. More unfortunately in this current one I can't make use of the same script and I'm suffering the consequences. About Screen recording whenever I use the Kazam software the recordings come out with a black screen without video or sound. Those are my issues and from what I've googled from other users, unfortunately. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-56.62-generic 5.15.64 Uname: Linux 5.15.0-56-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 BootLog: Error: [Errno 13] Permissão negada: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Dec 26 19:51:46 2022 DistUpgraded: 2022-11-21 13:11:29,776 DEBUG icon theme changed, re-reading DistroCodename: jammy DistroVariant: ubuntu GraphicsCard: Intel Corporation 4 Series Chipset Integrated Graphics Controller [8086:2e32] (rev 03) (prog-if 00 [VGA controller]) InstallationDate: Installed on 2022-11-19 (37 days ago) InstallationMedia: Ubuntu 20.04.5 LTS "Focal Fossa" - Release amd64 (20220831) MachineType: OEM To Be Filled By O.E.M. ProcEnviron: LANGUAGE=pt_BR:pt:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pt_BR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-56-generic root=UUID=22e65828-ac26-41d7-9a63-906dfc5b772b ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to jammy on 2022-11-21 (35 days ago) dmi.bios.date: 10/12/2019 dmi.bios.release: 1.20 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: G4177L0D dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: OEM G41 775 ICH7 8712 dmi.board.vendor: OEM dmi.board.version: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: OEM dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrG4177L0D:bd10/12/2019:br1.20:svnOEM:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnOEM:rnOEMG41775ICH78712:rvrTobefilledbyO.E.M.:cvnOEM:ct3:cvrToBeFilledByO.E.M.:skuToBeFilledByO.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: OEM version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.5-0ubuntu0.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.5 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug corruption jammy ubuntu wayland-session -- 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/2000487 Title: Monitor não puxa a resolução padrão e Gravação de Tela sem Vídeo Status in xorg package in Ubuntu: New Bug description: Olá, gostaria de relatar alguns problemas que estou sofrendo nesta versão (Ubuntu 22.04) e sofria na versão anterior (Ubuntu 20.04). Na versão anterior não consegui por padrão fazer uso da resolução padrão, mais consegui através de um script que criei pesquisando no Google logo usava a resolução padrão desta forma. Mais infelizmente nessa atual não consigo fazer uso do mesmo script e estou sofrendo as consequencias. Sobre a gravação de Tela sempre que faço uso do software Kazam as gravações saem com a tela preta sem vídeo ou som. Esses são meus problemas e pelo que pesquisei pelo Google de outros usuários, infelizmente. (Pt-Br) Hello, I would like to report some problems
[Desktop-packages] [Bug 1210316] Re: xf86-video-ati XMir acceleration detection broken: x crashes with radeon hd7850 video card with error /usr/bin/X: symbol lookup error: /usr/lib/xorg/modules/driver
Keep up the good work. https://breakfasthourguide.com/ -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-ati in Ubuntu. https://bugs.launchpad.net/bugs/1210316 Title: xf86-video-ati XMir acceleration detection broken: x crashes with radeon hd7850 video card with error /usr/bin/X: symbol lookup error: /usr/lib/xorg/modules/drivers/radeon_drv.so: undefined symbol: exaGetPixmapDriverPrivate Status in xserver-xorg-video-ati package in Ubuntu: Confirmed Bug description: Description: x crashes with radeon hd7850 video card with error /usr/bin/X: symbol lookup error: /usr/lib/xorg/modules/drivers/radeon_drv.so: undefined symbol: exaGetPixmapDriverPrivate steps: 1. install saucy 2. sudo apt-get update 3. sudo apt-get install unity-system-compositor 4. reboot expected results: xmir is running actual results: xmir crashes then runs in failback mode additional info: robotfuel: Well, that would be because it hasn't loaded the EXA module, which is perfectly reasonable robotfuel: What's not reasonable is that it's trying to resolve EXA symbols. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: xserver-xorg-video-ati 1:7.2.0-0ubuntu2 ProcVersionSignature: Ubuntu 3.10.0-6.17-generic 3.10.3 Uname: Linux 3.10.0-6-generic x86_64 ApportVersion: 2.12-0ubuntu3 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDmesg: [ 10.764013] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready [ 13.869816] init: lightdm main process (967) terminated with status 1 Date: Thu Aug 8 22:18:55 2013 DistUpgraded: Fresh install DistroCodename: saucy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Pitcairn PRO [Radeon HD 7850] [1002:6819] (prog-if 00 [VGA controller]) Subsystem: Hightech Information System Ltd. Device [1787:2320] InstallationDate: Installed on 2013-08-08 (0 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130802) MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.10.0-6-generic root=UUID=69ca392e-047d-4815-a27f-7ec25932fc2e ro quiet splash vt.handoff=7 Renderer: Software SourcePackage: xserver-xorg-video-ati UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/08/2012 dmi.bios.vendor: Intel Corp. dmi.bios.version: BHZ7710H.86A.0057.2012.0208.1904 dmi.board.name: DZ77BH-55K dmi.board.vendor: Intel Corporation dmi.board.version: AAG39008-400 dmi.chassis.type: 3 dmi.modalias: dmi:bvnIntelCorp.:bvrBHZ7710H.86A.0057.2012.0208.1904:bd02/08/2012:svn:pn:pvr:rvnIntelCorporation:rnDZ77BH-55K:rvrAAG39008-400:cvn:ct3:cvr: version.compiz: compiz 1:0.9.9~daily13.04.18.1~13.04-0ubuntu3 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.46-1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.1.4-0ubuntu8 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.1.4-0ubuntu8 version.xserver-xorg-core: xserver-xorg-core 2:1.14.2-0ubuntu9 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu3.1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.2.0-0ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.21.12-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.8-0ubuntu3 xserver.bootTime: Thu Aug 8 21:55:43 2013 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputRaritan D2CIM-DVUSB KEYBOARD, id 8 inputRaritan D2CIM-DVUSB MOUSE, id 9 xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.14.2-0ubuntu9 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/1210316/+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 1861408] Re: firefox apparmor messages
for firefox 107.0.1 in linux mint 20.3 based on Ubuntu 20.04, when task
manager is opened, this rule is needed:
owner @{PROC}/[0-9]*/task/[0-9]*/comm r,
--
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/1861408
Title:
firefox apparmor messages
Status in apparmor package in Ubuntu:
Confirmed
Status in firefox package in Ubuntu:
Fix Released
Bug description:
firefox version 72.0.1 64 bit, 72.0.1+linuxmint1+tricia , linux mint
19.3.
i see there is newer ubuntu version in
https://www.ubuntuupdates.org/package/ubuntu_mozilla_security/bionic/main/base/firefox
, 72.0.2+build1-0ubuntu0.18.04.1 , but its changes are not for
apparmor.
i have not found a page for firefox bugs in linux mint sites, so i
belive i should report here. but i have also asked about that in linux
mint's irc and then github.
i have enabled apparmor for firefox and see these types of messages in
syslog:
Jan 28 18:43:33 dinar-HP-Pavilion-g7-Notebook-PC dbus-daemon[735]:
[system] Activating via systemd: service
name='org.freedesktop.hostname1' unit='dbus-
org.freedesktop.hostname1.service' requested by ':1.111' (uid=1000
pid=1922 comm="/usr/lib/firefox/firefox " label="unconfined")
Jan 28 18:44:36 dinar-HP-Pavilion-g7-Notebook-PC kernel: [
5525.077960] audit: type=1400 audit(1580226276.440:27):
apparmor="DENIED" operation="capable"
profile="/usr/lib/firefox/firefox{,*[^s][^h]}" pid=15948
comm="firefox" capability=21 capname="sys_admin"
Jan 28 18:44:37 dinar-HP-Pavilion-g7-Notebook-PC kernel: [
5526.471731] audit: type=1107 audit(1580226277.832:28): pid=735
uid=103 auid=4294967295 ses=4294967295 msg='apparmor="DENIED"
operation="dbus_method_call" bus="system"
path="/org/freedesktop/RealtimeKit1"
interface="org.freedesktop.DBus.Properties" member="Get" mask="send"
name="org.freedesktop.RealtimeKit1" pid=15948
label="/usr/lib/firefox/firefox{,*[^s][^h]}" peer_pid=1320
peer_label="unconfined"
Jan 28 18:44:47 dinar-HP-Pavilion-g7-Notebook-PC dbus-daemon[1181]:
apparmor="DENIED" operation="dbus_method_call" bus="session"
path="/org/gtk/vfs/Daemon" interface="org.gtk.vfs.Daemon"
member="ListMonitorImplementations" mask="send" name=":1.10" pid=15948
label="/usr/lib/firefox/firefox{,*[^s][^h]}" peer_pid=1262
peer_label="unconfined"
Jan 28 18:44:47 dinar-HP-Pavilion-g7-Notebook-PC dbus-daemon[1181]:
apparmor="DENIED" operation="dbus_method_call" bus="session"
path="/org/gtk/Private/RemoteVolumeMonitor"
interface="org.gtk.Private.RemoteVolumeMonitor" member="IsSupported"
mask="send" name=":1.35" pid=15948
label="/usr/lib/firefox/firefox{,*[^s][^h]}" peer_pid=1385
peer_label="unconfined"
Jan 28 18:44:47 dinar-HP-Pavilion-g7-Notebook-PC dbus-daemon[1181]:
apparmor="DENIED" operation="dbus_method_call" bus="session"
path="/org/gtk/vfs/mounttracker" interface="org.gtk.vfs.MountTracker"
member="ListMounts2" mask="send" name=":1.10" pid=15948
label="/usr/lib/firefox/firefox{,*[^s][^h]}" peer_pid=1262
peer_label="unconfined"
Jan 28 18:44:47 dinar-HP-Pavilion-g7-Notebook-PC dbus-daemon[1181]:
apparmor="DENIED" operation="dbus_method_call" bus="session"
path="/org/gtk/vfs/mounttracker" interface="org.gtk.vfs.MountTracker"
member="LookupMount" mask="send" name=":1.10" pid=15948
label="/usr/lib/firefox/firefox{,*[^s][^h]}" peer_pid=1262
peer_label="unconfined"
Jan 28 18:44:48 dinar-HP-Pavilion-g7-Notebook-PC dbus-daemon[735]:
[system] Activating via systemd: service
name='org.freedesktop.hostname1' unit='dbus-
org.freedesktop.hostname1.service' requested by ':1.119' (uid=1000
pid=15948 comm="/usr/lib/firefox/firefox "
label="/usr/lib/firefox/firefox{,*[^s][^h]} (enforce)")
Jan 28 18:44:48 dinar-HP-Pavilion-g7-Notebook-PC kernel: [
5536.783313] audit: type=1107 audit(1580226288.143:34): pid=735
uid=103 auid=4294967295 ses=4294967295 msg='apparmor="DENIED"
operation="dbus_method_call" bus="system"
path="/org/freedesktop/hostname1"
interface="org.freedesktop.DBus.Properties" member="GetAll"
mask="send" name=":1.120" pid=15948
label="/usr/lib/firefox/firefox{,*[^s][^h]}" peer_pid=16177
peer_label="unconfined"
Jan 28 18:45:02 dinar-HP-Pavilion-g7-Notebook-PC dbus-daemon[1181]:
apparmor="DENIED" operation="dbus_method_call" bus="session"
path="/ca/desrt/dconf/Writer/user" interface="ca.desrt.dconf.Writer"
member="Change" mask="send" name="ca.desrt.dconf" pid=15948
label="/usr/lib/firefox/firefox{,*[^s][^h]}" peer_pid=1370
peer_label="unconfined"
Jan 28 21:51:30 dinar-HP-Pavilion-g7-Notebook-PC kernel:
[10131.880788] audit: type=1400 audit(1580237490.777:123):
apparmor="DENIED" operation="open"
profile="/usr/lib/firefox/firefox{,*[^s][^h]}"
name="/home/dinar/.cache/mesa_shader_cache/index" pid=19720
comm="firefox" requested_mask="wrc" denied_mask="wrc" fsuid=1000
[Desktop-packages] [Bug 2000173] Re: Xorg freeze
I would also like to add that this issue also manifests when the display goes to sleep. Moving the mouse or touching the keyboard (which should wake the display up) produces no effect and requires turning the monitor off and on again. -- 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/2000173 Title: Xorg freeze Status in xorg package in Ubuntu: New Bug description: Hello, I have a persistent issue where my freshly installed Ubuntu sleeps the monitor after booting. The solution is to turn the monitor off and on again. After turning it on the login screen is displayed. Note that when the screen is off even the combination CTRL+ALT+F2 to switch to a console TTY will not work. Rarely the system will boot to the login sleep without the screen going to sleep. There is the following message on dmesg: [ 63.052273] amdgpu :0a:00.0: [drm] *ERROR* mstb d9e48d98 port 1: DPCD read on addr 0x4b0 for 1 bytes NAKed System: Ubuntu 22.04.1 LTS CPU: AMD Ryzen 5 5600x 6-core processor × 12 GPU: AMD Radeon rx 6900 xt Monitor: DELL Ultrasharp U3415W connected with a Display Port <-> mini-Display Port cable. Using the default Ubuntu graphical drivers. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-56.62-generic 5.15.64 Uname: Linux 5.15.0-56-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Dec 20 18:21:07 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Navi 21 [Radeon RX 6800/6800 XT / 6900 XT] [1002:73bf] (rev c0) (prog-if 00 [VGA controller]) Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Radeon RX 6900 XT [1002:0e3a] InstallationDate: Installed on 2022-12-05 (14 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: ASUS System Product Name ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-56-generic root=UUID=08da7c47-3c82-4be1-8f1e-3546fd436ec5 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/11/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2423 dmi.board.asset.tag: Default string dmi.board.name: ROG STRIX B550-I GAMING dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2423:bd08/11/2021:br5.17:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGSTRIXB550-IGAMING:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: ASUS version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.5-0ubuntu0.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.5 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/2000173/+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
