[Desktop-packages] [Bug 1979053] Re: UI glitches (coloured squares) in GTK application with AMDGPU
** No longer affects: linux (Ubuntu) ** Changed in: mesa (Ubuntu) Status: Confirmed => Triaged ** Changed in: mesa (Ubuntu) Importance: Undecided => Medium ** Tags added: fixed-in-22.2.0 fixed-upstream ** Changed in: mesa (Ubuntu) Status: Triaged => Fix Released ** Tags added: rls-jj-incoming -- 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/1979053 Title: UI glitches (coloured squares) in GTK application with AMDGPU Status in Linux: Fix Released Status in Mesa: Fix Released Status in mesa package in Ubuntu: Fix Released Bug description: After updating to (K)ubuntu 22.04, I see user interface glitches in GTK application. Most obviously affected is Gimp, but Evolution and Eclipse IDE are affected, too. The glitches don't appear on a notebook with Intel graphics, so maybe the problem is caused by a weird interaction between the AMDGPU X.Org driver (I use a Radeon RX5600XT) and GTK. But as the KDE desktop itself isn't affected and only GTK application show these glitches, I think it's not a general problem with AMDGPU. I also booted both Kubunutu and Ubuntu live images and installed Gimp: The effect shows up there, too. So it's not only a problem of my current installation. I will upload some Gimp screenshots, so you can see what I mean... I'm not sure, but I tried to find the library used by all affected application: Maybe it's libcairo2, maybe not... ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: libcairo2 1.16.0-5ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-39.42-generic 5.15.35 Uname: Linux 5.15.0-39-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Fri Jun 17 12:36:26 2022 InstallationDate: Installed on 2022-04-27 (50 days ago) InstallationMedia: Kubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) SourcePackage: cairo UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: stieler1622 F pulseaudio /dev/snd/pcmC3D0p: stieler1622 F...m pulseaudio /dev/snd/controlC2: stieler1622 F pulseaudio /dev/snd/controlC1: stieler1622 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None DistUpgraded: Fresh install DistroCodename: jammy DistroRelease: Ubuntu 22.04 DistroVariant: ubuntu ExtraDebuggingInterest: No GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Navi 10 [Radeon RX 5600 OEM/5600 XT / 5700/5700 XT] [1002:731f] (rev ca) (prog-if 00 [VGA controller]) Subsystem: Tul Corporation / PowerColor Navi 10 [Radeon RX 5600 OEM/5600 XT / 5700/5700 XT] [148c:2402] InstallationDate: Installed on 2022-04-27 (55 days ago) InstallationMedia: Kubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: Micro-Star International Co., Ltd. MS-7B98 Package: mesa (not installed) ProcEnviron: LANGUAGE= TERM=xterm-256color PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-39-generic root=UUID=2186bb5d-f2f0-4775-97ef-066ee5c2d05d ro quiet splash nosgx vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-39.42-generic 5.15.35 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.15.0-39-generic N/A linux-backports-modules-5.15.0-39-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.2 RfKill: Tags: jammy ubuntu Uname: Linux 5.15.0-39-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 11/17/2021 dmi.bios.release: 5.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.E1 dmi.board.asset.tag: Default string dmi.board.name: Z390-A PRO (MS-7B98) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.E1:bd11/17/2021:br5.13:svnMicro-StarInternationalCo.,Ltd.:pnMS-7B98:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnZ390-APRO(MS-7B98):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:skuDefaultstring: dmi.product.family: Default string dmi.product.name: MS-7B98 dmi.product.sku: Default string dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co.,
[Desktop-packages] [Bug 1979053] Re: UI glitches (coloured squares) in GTK application with AMDGPU
** Changed in: mesa Status: New => 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/1979053 Title: UI glitches (coloured squares) in GTK application with AMDGPU Status in Linux: Fix Released Status in Mesa: Fix Released Status in linux package in Ubuntu: Confirmed Status in mesa package in Ubuntu: Confirmed Bug description: After updating to (K)ubuntu 22.04, I see user interface glitches in GTK application. Most obviously affected is Gimp, but Evolution and Eclipse IDE are affected, too. The glitches don't appear on a notebook with Intel graphics, so maybe the problem is caused by a weird interaction between the AMDGPU X.Org driver (I use a Radeon RX5600XT) and GTK. But as the KDE desktop itself isn't affected and only GTK application show these glitches, I think it's not a general problem with AMDGPU. I also booted both Kubunutu and Ubuntu live images and installed Gimp: The effect shows up there, too. So it's not only a problem of my current installation. I will upload some Gimp screenshots, so you can see what I mean... I'm not sure, but I tried to find the library used by all affected application: Maybe it's libcairo2, maybe not... ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: libcairo2 1.16.0-5ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-39.42-generic 5.15.35 Uname: Linux 5.15.0-39-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Fri Jun 17 12:36:26 2022 InstallationDate: Installed on 2022-04-27 (50 days ago) InstallationMedia: Kubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) SourcePackage: cairo UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: stieler1622 F pulseaudio /dev/snd/pcmC3D0p: stieler1622 F...m pulseaudio /dev/snd/controlC2: stieler1622 F pulseaudio /dev/snd/controlC1: stieler1622 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None DistUpgraded: Fresh install DistroCodename: jammy DistroRelease: Ubuntu 22.04 DistroVariant: ubuntu ExtraDebuggingInterest: No GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Navi 10 [Radeon RX 5600 OEM/5600 XT / 5700/5700 XT] [1002:731f] (rev ca) (prog-if 00 [VGA controller]) Subsystem: Tul Corporation / PowerColor Navi 10 [Radeon RX 5600 OEM/5600 XT / 5700/5700 XT] [148c:2402] InstallationDate: Installed on 2022-04-27 (55 days ago) InstallationMedia: Kubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: Micro-Star International Co., Ltd. MS-7B98 Package: mesa (not installed) ProcEnviron: LANGUAGE= TERM=xterm-256color PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-39-generic root=UUID=2186bb5d-f2f0-4775-97ef-066ee5c2d05d ro quiet splash nosgx vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-39.42-generic 5.15.35 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.15.0-39-generic N/A linux-backports-modules-5.15.0-39-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.2 RfKill: Tags: jammy ubuntu Uname: Linux 5.15.0-39-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 11/17/2021 dmi.bios.release: 5.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.E1 dmi.board.asset.tag: Default string dmi.board.name: Z390-A PRO (MS-7B98) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.E1:bd11/17/2021:br5.13:svnMicro-StarInternationalCo.,Ltd.:pnMS-7B98:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnZ390-APRO(MS-7B98):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:skuDefaultstring: dmi.product.family: Default string dmi.product.name: MS-7B98 dmi.product.sku: Default string dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: x
[Desktop-packages] [Bug 1991159] [NEW] [snap] libEGL warning: DRI2: failed to authenticate
Public bug reported: On a fresh kinetic live usb, I installed the snap of gnome-text-editor 42.2 (from stable or candidate), it installs fine but then crashes when running: $ snap run gnome-text-editor libEGL warning: DRI2: failed to authenticate Failed to register: GDBus.Error:org.freedesktop.DBus.Error.AccessDenied: An AppArmor policy prevents this sender from sending this message to this recipient; type="method_call", sender=":1.249" (uid=999 pid=11735 comm="/snap/gnome-text-editor/6/usr/bin/gnome-text-edito" label="snap.gnome-text-editor.gnome-text-editor (enforce)") interface="org.gtk.Actions" member="DescribeAll" error name="(unset)" requested_reply="0" destination="org.gnome.TextEditor" (uid=999 pid=9706 comm="gnome-text-editor" label="unconfined") On Jammy, this is not a problem and it runs fine. ** Affects: gnome-text-editor (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-text-editor in Ubuntu. https://bugs.launchpad.net/bugs/1991159 Title: [snap] libEGL warning: DRI2: failed to authenticate Status in gnome-text-editor package in Ubuntu: New Bug description: On a fresh kinetic live usb, I installed the snap of gnome-text-editor 42.2 (from stable or candidate), it installs fine but then crashes when running: $ snap run gnome-text-editor libEGL warning: DRI2: failed to authenticate Failed to register: GDBus.Error:org.freedesktop.DBus.Error.AccessDenied: An AppArmor policy prevents this sender from sending this message to this recipient; type="method_call", sender=":1.249" (uid=999 pid=11735 comm="/snap/gnome-text-editor/6/usr/bin/gnome-text-edito" label="snap.gnome-text-editor.gnome-text-editor (enforce)") interface="org.gtk.Actions" member="DescribeAll" error name="(unset)" requested_reply="0" destination="org.gnome.TextEditor" (uid=999 pid=9706 comm="gnome-text-editor" label="unconfined") On Jammy, this is not a problem and it runs fine. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-text-editor/+bug/1991159/+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 1781810] Re: Plank dock is not showing an indicator when a certain application is open anymore and when an application that is open is clicked on the dock, a new instance of it
Hi kenn I've got: bamfdaemon/jammy,now 0.5.6+22.04.20220217-0ubuntu1 amd64. So that seems to be the same version as yours. But - and this may be the difference that makes the difference - you are on Mate and I am on Cinnamon. (Also, though, you're on Ubuntu and I'm on Mint. Ah, fragmentation! The joy, and despair, of Linux.) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to bamf in Ubuntu. https://bugs.launchpad.net/bugs/1781810 Title: Plank dock is not showing an indicator when a certain application is open anymore and when an application that is open is clicked on the dock, a new instance of it is opened Status in BAMF: Expired Status in Plank: Expired Status in bamf package in Ubuntu: Expired Status in plank package in Ubuntu: Expired Bug description: Plank version: 0.11.4 Distribution: Ubuntu MATE 18.04 DE: MATE Desktop Window manager: Marco Video card: Intel HD Graphics 4000 Plank comes installed with the system by default When i used Ubuntu MATE 16.04 it didn't happen. I had an indicator that the application i was clicking on was open and when i clicked it, it would be restored if it was minimized and it will be minimized if it was maximized or just being shown on the screen but on this version, even if the application is minimized or maximized, when i click on its icon, first of all, i can't see that "application open" indicator below its icon anymore(Only below the Plank icon) and second of all, Plank will open a new instance of that same application. I recorded a video showing you what i am talking about. And also, sometimes when i click on the icons on the dock, i won't have that visual feedback, that "little jump" of the icon i click. That's very important as well otherwise, i think nothing happened. That's all. I really like Plank and it is a great application. Thanks for it. Best wishes To manage notifications about this bug go to: https://bugs.launchpad.net/bamf/+bug/1781810/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
Re: [Desktop-packages] [Bug 1990010] Re: VA error: resource allocation failed
I get this both on dev, and edge-hwacc, and snaps I build myself. It consistently gives me a VA error on wayland, but works on X11. On Wed, Sep 28, 2022 at 2:30 PM Nathan Teodosio <1990...@bugs.launchpad.net> wrote: > > Which build guide did you follow to build your chromium browser? Could > > you please provide us the version of your chromium browser and vainfo > > output information? Thank you! > > Qinling, the snap against which we have been testing is built from [1]. > (Please correct me, Bram, if you tested a different build.) > > [1]: https://git.launchpad.net/~nteodosio/chromium-browser/tree/?h=dev > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1990010 > > Title: > VA error: resource allocation failed > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1990010/+subscriptions > > -- Owner/Director of Game Studio Abraham Stolk Inc. Vancouver BC, Canada b.st...@gmail.com -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1990010 Title: VA error: resource allocation failed Status in chromium-browser package in Ubuntu: In Progress Bug description: https://github.com/intel/media-driver/issues/1498 --- When I play a H264/AAC video with HW decoding enabled on Alderlake 12600k, using Wayland I get the error: vaCreateSurfaces (import mode) failed, VA error: resource allocation failed After which, chromium will proceed to play the video without HW acceleration using ffmpeg. This is both with using the pre-built snap from channel beta/hwacc and a snap built from source. (NOTE: HW decoding does work with same browser on X11 desktop, using VDAVideoDecoder.) To get more information on this VA error, I built the snap with debug versions of gmmlib and media-driver (latest git) using the latest git from valib as well. The log output from chromium now mentions why the allocation fails: [390012:14:0916/112615.428584:INFO:decoder.cc(41)] DecryptingVideoDecoder [389969:390095:0916/112615.445970:INFO:decoder.cc(65)] VDAVideoDecoder [390012:14:0916/112615.449426:INFO:decoder.cc(65)] VDAVideoDecoder [390012:14:0916/112615.449500:INFO:decoder.cc(65)] VDAVideoDecoder [LIBVA]:CRITICAL - DdiMediaUtil_AllocateSurface:378: Unsupported modifier. [389969:389969:0916/112615.467062:ERROR:vaapi_wrapper.cc(2389)] vaCreateSurfaces (import mode) failed, VA error: resource allocation failed [389969:389969:0916/112615.467212:ERROR:vaapi_picture_native_pixmap_ozone.cc(66)] Failed creating VASurface for NativePixmap [LIBVA]:CRITICAL - DdiMediaUtil_AllocateSurface:378: Unsupported modifier. [389969:389969:0916/112615.468871:ERROR:vaapi_wrapper.cc(2389)] vaCreateSurfaces (import mode) failed, VA error: resource allocation failed [389969:389969:0916/112615.468987:ERROR:vaapi_picture_native_pixmap_ozone.cc(66)] Failed creating VASurface for NativePixmap [389969:389969:0916/112615.469140:ERROR:vaapi_video_decode_accelerator.cc(129)] {"code":6,"data":{},"group":"VaapiStatusCode","message":"","stack":[{"file":"media/gpu/vaapi/vaapi_picture_native_pixmap_ozone.cc","line":67}]} [390012:14:0916/112615.469740:INFO:decoder.cc(32)] VpxVideoDecoder [390012:14:0916/112615.470169:INFO:decoder.cc(44)] Dav1dVideoDecoder [390012:14:0916/112615.471713:INFO:decoder.cc(29)] FFmpegVideoDecoder [390012:14:0916/112615.471819:INFO:decoder.cc(29)] FFmpegVideoDecoder Note the message: "DdiMediaUtil_AllocateSurface:378: Unsupported modifier." I am on wayland, and use these chromium flags: export CHROMIUM_FLAGS="--enable-logging=stderr --use-gl=egl --enable- features=VaapiVideoDecoder,VaapiVideoEncoder --disable- features=UseChromeOSDirectVideoDecoder --ignore-gpu-blocklist --disable-gpu-driver-bug-workaround --ozone-platform=wayland" The video that fails: the 1080p/60 version downloaded from here: https://github.com/chthomos/video-media-samples/ I will figure out which is the "unsupported modifier" and report back, here. Note: currently gmmlib and media-driver have failing debug builds, but I have created pull requests to both: https://github.com/intel/media-driver/pull/1491 https://github.com/intel/gmmlib/pull/97 CPU: 12600k GPU: Intel Alderlake_s (Gen12) Snap built with: core20 Host OS: Ubuntu Kinetic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1990010/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
Re: [Desktop-packages] [Bug 1990010] Re: VA error: resource allocation failed
> Which build guide did you follow to build your chromium browser? Could > you please provide us the version of your chromium browser and vainfo > output information? Thank you! Qinling, the snap against which we have been testing is built from [1]. (Please correct me, Bram, if you tested a different build.) [1]: https://git.launchpad.net/~nteodosio/chromium-browser/tree/?h=dev -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1990010 Title: VA error: resource allocation failed Status in chromium-browser package in Ubuntu: In Progress Bug description: https://github.com/intel/media-driver/issues/1498 --- When I play a H264/AAC video with HW decoding enabled on Alderlake 12600k, using Wayland I get the error: vaCreateSurfaces (import mode) failed, VA error: resource allocation failed After which, chromium will proceed to play the video without HW acceleration using ffmpeg. This is both with using the pre-built snap from channel beta/hwacc and a snap built from source. (NOTE: HW decoding does work with same browser on X11 desktop, using VDAVideoDecoder.) To get more information on this VA error, I built the snap with debug versions of gmmlib and media-driver (latest git) using the latest git from valib as well. The log output from chromium now mentions why the allocation fails: [390012:14:0916/112615.428584:INFO:decoder.cc(41)] DecryptingVideoDecoder [389969:390095:0916/112615.445970:INFO:decoder.cc(65)] VDAVideoDecoder [390012:14:0916/112615.449426:INFO:decoder.cc(65)] VDAVideoDecoder [390012:14:0916/112615.449500:INFO:decoder.cc(65)] VDAVideoDecoder [LIBVA]:CRITICAL - DdiMediaUtil_AllocateSurface:378: Unsupported modifier. [389969:389969:0916/112615.467062:ERROR:vaapi_wrapper.cc(2389)] vaCreateSurfaces (import mode) failed, VA error: resource allocation failed [389969:389969:0916/112615.467212:ERROR:vaapi_picture_native_pixmap_ozone.cc(66)] Failed creating VASurface for NativePixmap [LIBVA]:CRITICAL - DdiMediaUtil_AllocateSurface:378: Unsupported modifier. [389969:389969:0916/112615.468871:ERROR:vaapi_wrapper.cc(2389)] vaCreateSurfaces (import mode) failed, VA error: resource allocation failed [389969:389969:0916/112615.468987:ERROR:vaapi_picture_native_pixmap_ozone.cc(66)] Failed creating VASurface for NativePixmap [389969:389969:0916/112615.469140:ERROR:vaapi_video_decode_accelerator.cc(129)] {"code":6,"data":{},"group":"VaapiStatusCode","message":"","stack":[{"file":"media/gpu/vaapi/vaapi_picture_native_pixmap_ozone.cc","line":67}]} [390012:14:0916/112615.469740:INFO:decoder.cc(32)] VpxVideoDecoder [390012:14:0916/112615.470169:INFO:decoder.cc(44)] Dav1dVideoDecoder [390012:14:0916/112615.471713:INFO:decoder.cc(29)] FFmpegVideoDecoder [390012:14:0916/112615.471819:INFO:decoder.cc(29)] FFmpegVideoDecoder Note the message: "DdiMediaUtil_AllocateSurface:378: Unsupported modifier." I am on wayland, and use these chromium flags: export CHROMIUM_FLAGS="--enable-logging=stderr --use-gl=egl --enable- features=VaapiVideoDecoder,VaapiVideoEncoder --disable- features=UseChromeOSDirectVideoDecoder --ignore-gpu-blocklist --disable-gpu-driver-bug-workaround --ozone-platform=wayland" The video that fails: the 1080p/60 version downloaded from here: https://github.com/chthomos/video-media-samples/ I will figure out which is the "unsupported modifier" and report back, here. Note: currently gmmlib and media-driver have failing debug builds, but I have created pull requests to both: https://github.com/intel/media-driver/pull/1491 https://github.com/intel/gmmlib/pull/97 CPU: 12600k GPU: Intel Alderlake_s (Gen12) Snap built with: core20 Host OS: Ubuntu Kinetic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1990010/+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 1990010] Re: VA error: resource allocation failed
The chromium version and vainfo output are in the upstream issue: https://github.com/intel/media-driver/issues/1498 The chromium build is via our snap, that integrates your patches. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1990010 Title: VA error: resource allocation failed Status in chromium-browser package in Ubuntu: In Progress Bug description: https://github.com/intel/media-driver/issues/1498 --- When I play a H264/AAC video with HW decoding enabled on Alderlake 12600k, using Wayland I get the error: vaCreateSurfaces (import mode) failed, VA error: resource allocation failed After which, chromium will proceed to play the video without HW acceleration using ffmpeg. This is both with using the pre-built snap from channel beta/hwacc and a snap built from source. (NOTE: HW decoding does work with same browser on X11 desktop, using VDAVideoDecoder.) To get more information on this VA error, I built the snap with debug versions of gmmlib and media-driver (latest git) using the latest git from valib as well. The log output from chromium now mentions why the allocation fails: [390012:14:0916/112615.428584:INFO:decoder.cc(41)] DecryptingVideoDecoder [389969:390095:0916/112615.445970:INFO:decoder.cc(65)] VDAVideoDecoder [390012:14:0916/112615.449426:INFO:decoder.cc(65)] VDAVideoDecoder [390012:14:0916/112615.449500:INFO:decoder.cc(65)] VDAVideoDecoder [LIBVA]:CRITICAL - DdiMediaUtil_AllocateSurface:378: Unsupported modifier. [389969:389969:0916/112615.467062:ERROR:vaapi_wrapper.cc(2389)] vaCreateSurfaces (import mode) failed, VA error: resource allocation failed [389969:389969:0916/112615.467212:ERROR:vaapi_picture_native_pixmap_ozone.cc(66)] Failed creating VASurface for NativePixmap [LIBVA]:CRITICAL - DdiMediaUtil_AllocateSurface:378: Unsupported modifier. [389969:389969:0916/112615.468871:ERROR:vaapi_wrapper.cc(2389)] vaCreateSurfaces (import mode) failed, VA error: resource allocation failed [389969:389969:0916/112615.468987:ERROR:vaapi_picture_native_pixmap_ozone.cc(66)] Failed creating VASurface for NativePixmap [389969:389969:0916/112615.469140:ERROR:vaapi_video_decode_accelerator.cc(129)] {"code":6,"data":{},"group":"VaapiStatusCode","message":"","stack":[{"file":"media/gpu/vaapi/vaapi_picture_native_pixmap_ozone.cc","line":67}]} [390012:14:0916/112615.469740:INFO:decoder.cc(32)] VpxVideoDecoder [390012:14:0916/112615.470169:INFO:decoder.cc(44)] Dav1dVideoDecoder [390012:14:0916/112615.471713:INFO:decoder.cc(29)] FFmpegVideoDecoder [390012:14:0916/112615.471819:INFO:decoder.cc(29)] FFmpegVideoDecoder Note the message: "DdiMediaUtil_AllocateSurface:378: Unsupported modifier." I am on wayland, and use these chromium flags: export CHROMIUM_FLAGS="--enable-logging=stderr --use-gl=egl --enable- features=VaapiVideoDecoder,VaapiVideoEncoder --disable- features=UseChromeOSDirectVideoDecoder --ignore-gpu-blocklist --disable-gpu-driver-bug-workaround --ozone-platform=wayland" The video that fails: the 1080p/60 version downloaded from here: https://github.com/chthomos/video-media-samples/ I will figure out which is the "unsupported modifier" and report back, here. Note: currently gmmlib and media-driver have failing debug builds, but I have created pull requests to both: https://github.com/intel/media-driver/pull/1491 https://github.com/intel/gmmlib/pull/97 CPU: 12600k GPU: Intel Alderlake_s (Gen12) Snap built with: core20 Host OS: Ubuntu Kinetic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1990010/+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 1990010] Re: VA error: resource allocation failed
Which build guide did you follow to build your chromium browser? Could you please provide us the version of your chromium browser and vainfo output information? Thank you! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1990010 Title: VA error: resource allocation failed Status in chromium-browser package in Ubuntu: In Progress Bug description: https://github.com/intel/media-driver/issues/1498 --- When I play a H264/AAC video with HW decoding enabled on Alderlake 12600k, using Wayland I get the error: vaCreateSurfaces (import mode) failed, VA error: resource allocation failed After which, chromium will proceed to play the video without HW acceleration using ffmpeg. This is both with using the pre-built snap from channel beta/hwacc and a snap built from source. (NOTE: HW decoding does work with same browser on X11 desktop, using VDAVideoDecoder.) To get more information on this VA error, I built the snap with debug versions of gmmlib and media-driver (latest git) using the latest git from valib as well. The log output from chromium now mentions why the allocation fails: [390012:14:0916/112615.428584:INFO:decoder.cc(41)] DecryptingVideoDecoder [389969:390095:0916/112615.445970:INFO:decoder.cc(65)] VDAVideoDecoder [390012:14:0916/112615.449426:INFO:decoder.cc(65)] VDAVideoDecoder [390012:14:0916/112615.449500:INFO:decoder.cc(65)] VDAVideoDecoder [LIBVA]:CRITICAL - DdiMediaUtil_AllocateSurface:378: Unsupported modifier. [389969:389969:0916/112615.467062:ERROR:vaapi_wrapper.cc(2389)] vaCreateSurfaces (import mode) failed, VA error: resource allocation failed [389969:389969:0916/112615.467212:ERROR:vaapi_picture_native_pixmap_ozone.cc(66)] Failed creating VASurface for NativePixmap [LIBVA]:CRITICAL - DdiMediaUtil_AllocateSurface:378: Unsupported modifier. [389969:389969:0916/112615.468871:ERROR:vaapi_wrapper.cc(2389)] vaCreateSurfaces (import mode) failed, VA error: resource allocation failed [389969:389969:0916/112615.468987:ERROR:vaapi_picture_native_pixmap_ozone.cc(66)] Failed creating VASurface for NativePixmap [389969:389969:0916/112615.469140:ERROR:vaapi_video_decode_accelerator.cc(129)] {"code":6,"data":{},"group":"VaapiStatusCode","message":"","stack":[{"file":"media/gpu/vaapi/vaapi_picture_native_pixmap_ozone.cc","line":67}]} [390012:14:0916/112615.469740:INFO:decoder.cc(32)] VpxVideoDecoder [390012:14:0916/112615.470169:INFO:decoder.cc(44)] Dav1dVideoDecoder [390012:14:0916/112615.471713:INFO:decoder.cc(29)] FFmpegVideoDecoder [390012:14:0916/112615.471819:INFO:decoder.cc(29)] FFmpegVideoDecoder Note the message: "DdiMediaUtil_AllocateSurface:378: Unsupported modifier." I am on wayland, and use these chromium flags: export CHROMIUM_FLAGS="--enable-logging=stderr --use-gl=egl --enable- features=VaapiVideoDecoder,VaapiVideoEncoder --disable- features=UseChromeOSDirectVideoDecoder --ignore-gpu-blocklist --disable-gpu-driver-bug-workaround --ozone-platform=wayland" The video that fails: the 1080p/60 version downloaded from here: https://github.com/chthomos/video-media-samples/ I will figure out which is the "unsupported modifier" and report back, here. Note: currently gmmlib and media-driver have failing debug builds, but I have created pull requests to both: https://github.com/intel/media-driver/pull/1491 https://github.com/intel/gmmlib/pull/97 CPU: 12600k GPU: Intel Alderlake_s (Gen12) Snap built with: core20 Host OS: Ubuntu Kinetic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1990010/+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 1976554] Re: [Lenovo X1 Yoga 5th Gen] Screen auto rotates randomly after suspend
I can confirm the same happening on a Dell Latitude 7390 2-in-1 with Ubuntu 22.04.1, gnome version 42.4, windowing system: X11, kernel: 5.15.0-48-generic. Details: I have screen rotation locked, but after resuming from suspend the screen is rotated randomly. Then I first have to unlock screen rotation (by trying to move the mouse in the wrong orientation), and then rotate the laptop until the screen rotation is triggered and restored to the actual orientation of the laptop. Finally I need to lock screen rotation again. -- 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/1976554 Title: [Lenovo X1 Yoga 5th Gen] Screen auto rotates randomly after suspend Status in mutter package in Ubuntu: New Bug description: Description: Ubuntu 22.04 LTS Release: 22.04 iio-sensor-proxy: 3.3-0ubuntu6 mutter: 42.0-3ubuntu2 Since update to Ubuntu 22.04: If i leave screen rotation in GNOME enabled and come back form suspend mode (open/close Laptop) the screen is rotated wrong. Mostly 90 degrees left from normal view axis. Expected behaviour: The screen should not rotate until logged in again or there should be a delay before choosing an new rotation whilst laptop is opened. Same problem seems to be present in older iio-sensor-proxy versions. Mabye affected to Mutter and or iio-sensor-proxy --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2020-06-30 (707 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Package: mutter 42.0-3ubuntu2 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/usr/bin/zsh ProcVersionSignature: Ubuntu 5.15.0-33.34-generic 5.15.30 Tags: jammy Uname: Linux 5.15.0-33-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-04-22 (46 days ago) UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo vboxusers _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1976554/+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 1991146] Re: ibus-daemon crashed with SIGABRT
** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1991146/+attachment/5619840/+files/CoreDump.gz ** Information type changed from Private to Public -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1991146 Title: ibus-daemon crashed with SIGABRT Status in ibus package in Ubuntu: New Bug description: Was logged on to user1 and did a Power off>Switch User to user2. Logged off user2 and signed in to user1. This crash was waiting. ProblemType: Crash DistroRelease: Ubuntu 22.10 Package: ibus 1.5.27-2 ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0 Uname: Linux 5.19.0-15-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.23.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass Date: Wed Sep 28 14:22:49 2022 ExecutablePath: /usr/bin/ibus-daemon InstallationDate: Installed on 2022-09-17 (11 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220917) ProcCmdline: ibus-daemon --panel disable --xim ProcEnviron: LANG=en_US.UTF-8 Signal: 6 SourcePackage: ibus StacktraceTop: () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_assertion_message_expr () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 () () at /lib/x86_64-linux-gnu/libgio-2.0.so.0 () at /lib/x86_64-linux-gnu/libgio-2.0.so.0 Title: ibus-daemon crashed with SIGABRT UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1991146/+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 1991148] Re: Error message upon startup, no bug apparent in UI user experience
*** This bug is a duplicate of bug 1990200 *** https://bugs.launchpad.net/bugs/1990200 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1990200, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1991148/+attachment/5619851/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1991148/+attachment/5619853/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1991148/+attachment/5619857/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1991148/+attachment/5619858/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1991148/+attachment/5619859/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1991148/+attachment/5619860/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1991148/+attachment/5619861/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 1990200 ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/1991148 Title: Error message upon startup, no bug apparent in UI user experience Status in gnome-online-accounts package in Ubuntu: New Bug description: 22.10 First start up after upgrading to 22.10 Beta. Unknown why error message was displayed. Hope this is helpful at all. ProblemType: Crash DistroRelease: Ubuntu 22.10 Package: gnome-online-accounts 3.46.0-1 ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0 Uname: Linux 5.19.0-15-generic x86_64 ApportVersion: 2.23.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass Date: Wed Sep 28 20:38:33 2022 ExecutablePath: /usr/libexec/goa-daemon InstallationDate: Installed on 2021-12-04 (297 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) ProcCmdline: /usr/libexec/goa-daemon Signal: 6 SourcePackage: gnome-online-accounts StacktraceTop: ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/librest-1.0.so.0 rest_proxy_call_sync () from /lib/x86_64-linux-gnu/librest-1.0.so.0 ?? () from /lib/x86_64-linux-gnu/libgoa-backend-1.0.so.1 Title: goa-daemon crashed with SIGABRT in g_assertion_message_expr() UpgradeStatus: Upgraded to kinetic on 2022-09-28 (0 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/1991148/+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 1958019]
I've managed to get my Lenovo Legion 7 16ACHg6 speakers working on kernel 5.18.x by setting the following kernel configuration CONFIG_SND_SOC_CS35L41_I2C=m CONFIG_SERIAL_MULTI_INSTANTIATE=m However, kernel 5.19.x seems to break it as with the same kernel config, the modules are loaded by do not work. Apart from the speaker, I'm having the same issue with the touchpad (works on 5.18, but not on 5.19). Any ideas why it would work on 5.18, but not on 5.19? -- 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/1958019 Title: [Lenovo Legion7 16ACHg6 82N6, Realtek ALC287, Speaker, Internal] No sound at all Status in sound-2.6 (alsa-kernel): Confirmed Status in alsa-driver package in Ubuntu: Confirmed Bug description: On my Lenovo Legion-7-16ACHg6 laptop I can't hear any sound by internal speakers, but it work by headphones connected to standard jack aux. uname -r 5.11.0-44-generic ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.11.0-44.48~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-44-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: i3draven 1266 F pulseaudio /dev/snd/controlC0: i3draven 1266 F pulseaudio /dev/snd/controlC1: i3draven 1266 F pulseaudio /dev/snd/pcmC1D0p: i3draven 1266 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Jan 15 15:10:53 2022 InstallationDate: Installed on 2021-10-11 (96 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic failed Symptom_Card: Family 17h (Models 10h-1fh) HD Audio Controller - HD-Audio Generic Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: i3draven 1266 F pulseaudio /dev/snd/controlC0: i3draven 1266 F pulseaudio /dev/snd/controlC1: i3draven 1266 F pulseaudio /dev/snd/pcmC1D0p: i3draven 1266 F...m pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [82N6, Realtek ALC287, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/08/2021 dmi.bios.release: 1.49 dmi.bios.vendor: LENOVO dmi.bios.version: GKCN49WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0R32862 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Legion 7 16ACHg6 dmi.ec.firmware.release: 1.49 dmi.modalias: dmi:bvnLENOVO:bvrGKCN49WW:bd11/08/2021:br1.49:efr1.49:svnLENOVO:pn82N6:pvrLegion716ACHg6:skuLENOVO_MT_82N6_BU_idea_FM_Legion716ACHg6:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrLegion716ACHg6: dmi.product.family: Legion 7 16ACHg6 dmi.product.name: 82N6 dmi.product.sku: LENOVO_MT_82N6_BU_idea_FM_Legion 7 16ACHg6 dmi.product.version: Legion 7 16ACHg6 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/sound-2.6/+bug/1958019/+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 1958019]
(In reply to Gergo K from comment #689) > The TAS2563 works without the firmware (tuning file). > Documentation: > https://www.ti.com/product/TAS2553 > > However there is an android driver with firmware loading support. > https://git.ti.com/cgit/tas256xsw-android/tas2563-android-driver/ > Or a mainline RFC: > https://lkml.org/lkml/2020/6/9/800 > > > The bass speakers can be enabled with: > i2cset 3 0x4c 0x2 0 > i2cset 3 0x4d 0x2 0 > > they are listening on 0x48 too, so in one turn: > i2cset 3 0x48 0x2 0 > > I don't know how safe it is to use it this way. > > They have to be enabled after suspend, and if you plug in-out the headphone > (only if auto mute is enabled). OK, that works! But what can I do to make this register (3 0x38 0x02 0) set automatically? Does that have something to do with the power settings under /sys/bus/i2c/devices/i2c-3/device/power/*? -- 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/1958019 Title: [Lenovo Legion7 16ACHg6 82N6, Realtek ALC287, Speaker, Internal] No sound at all Status in sound-2.6 (alsa-kernel): Confirmed Status in alsa-driver package in Ubuntu: Confirmed Bug description: On my Lenovo Legion-7-16ACHg6 laptop I can't hear any sound by internal speakers, but it work by headphones connected to standard jack aux. uname -r 5.11.0-44-generic ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.11.0-44.48~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-44-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: i3draven 1266 F pulseaudio /dev/snd/controlC0: i3draven 1266 F pulseaudio /dev/snd/controlC1: i3draven 1266 F pulseaudio /dev/snd/pcmC1D0p: i3draven 1266 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Jan 15 15:10:53 2022 InstallationDate: Installed on 2021-10-11 (96 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic failed Symptom_Card: Family 17h (Models 10h-1fh) HD Audio Controller - HD-Audio Generic Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: i3draven 1266 F pulseaudio /dev/snd/controlC0: i3draven 1266 F pulseaudio /dev/snd/controlC1: i3draven 1266 F pulseaudio /dev/snd/pcmC1D0p: i3draven 1266 F...m pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [82N6, Realtek ALC287, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/08/2021 dmi.bios.release: 1.49 dmi.bios.vendor: LENOVO dmi.bios.version: GKCN49WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0R32862 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Legion 7 16ACHg6 dmi.ec.firmware.release: 1.49 dmi.modalias: dmi:bvnLENOVO:bvrGKCN49WW:bd11/08/2021:br1.49:efr1.49:svnLENOVO:pn82N6:pvrLegion716ACHg6:skuLENOVO_MT_82N6_BU_idea_FM_Legion716ACHg6:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrLegion716ACHg6: dmi.product.family: Legion 7 16ACHg6 dmi.product.name: 82N6 dmi.product.sku: LENOVO_MT_82N6_BU_idea_FM_Legion 7 16ACHg6 dmi.product.version: Legion 7 16ACHg6 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/sound-2.6/+bug/1958019/+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 1990891] Re: after today's Kinetic updates, WiFi no longer working, so laptop basically useless
Thank you very much @Jonathan. I can confirm removing the iwd.conf did the trick on my end. -- 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/1990891 Title: after today's Kinetic updates, WiFi no longer working, so laptop basically useless Status in network-manager package in Ubuntu: Confirmed Bug description: ThinkPad X1 Carbon 6th Gen WiFi was working fine. Installed today's batch of Kinetic updates. Laptop can no longer see any WiFi networks (had to dig out my old ThinkPad USB dongle and plug into my router to be able to submit this bug report). ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: network-manager 1.40.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0 Uname: Linux 5.19.0-15-generic x86_64 ApportVersion: 2.23.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Sep 26 17:09:25 2022 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2019-08-16 (1137 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) IpRoute: default via 192.168.4.1 dev enp0s31f6 proto dhcp src 192.168.4.158 metric 100 169.254.0.0/16 dev docker0 scope link metric 1000 linkdown 172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown 192.168.4.0/24 dev enp0s31f6 proto kernel scope link src 192.168.4.158 metric 100 SourcePackage: network-manager UpgradeStatus: Upgraded to kinetic on 2022-09-24 (2 days ago) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.40.0 connected started full enabled enabled enabled missing enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1990891/+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 1894090] Re: Consolidate thunderbird Ubuntu packaging with Debian for versions >= 78
What is now happening, in any case, is Ubuntu LTS Thunderbird packaging is lagging behind on important security updates. I think a consideration of sharing packaging could help this, in my opinion, unless there is a problem with the arrangement .. may be key differences in using separate vs. included libnss and so-on -- 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/1894090 Title: Consolidate thunderbird Ubuntu packaging with Debian for versions >= 78 Status in thunderbird package in Ubuntu: Confirmed Bug description: I suggest consolidating the thunderbird Ubuntu packaging with Debian for versions >= 78. Now that the lightning calendar extension is part of thunderbird, the thunderbird packaging between Ubuntu and Debian is getting closer except for the naming of the locale packages. The latest thunderbird version always gets updated in Debian 10 stable-security and Debian 9 oldstable-security since thunderbird follows the Firefox ESR versioning and Debian follows that. Ubuntu does a similar thing with its stable LTS releases, and hence could benefit from the Debian packaging. And when a new major release of Thunderbird is out, it gets updated in Debian unstable/experimental then backported to stable and oldstable. A similar thing happens in Ubuntu development and stable LTS releases. So I suggest a plan like this: 1. Transition the thunderbird locale packages in Ubuntu to the Debian naming 2. Merge the latest thunderbird with Debian unstable/experimental to Ubuntu development If the Debian maintainer agrees, the Ubuntu packaging could also happen in Debian salsa similar to what is already happening with GNOME packaging. I think sharing the thunderbird packaging between Ubuntu and Debian is beneficial to both sides going forward in the future, and especially if thunderbird packaging gets more complicated to backport to stable releases. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1894090/+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 1990986] Re: With iwd, doesn't connect to WPA2 Enterprise network (e.g. eduroam)
Todays updates included network-manager 1.40.0-1ubuntu2, and after `apt autopurge` iwd was removed. This wi-fi network connection is working again normally since. ** Changed in: iwd (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to iwd in Ubuntu. https://bugs.launchpad.net/bugs/1990986 Title: With iwd, doesn't connect to WPA2 Enterprise network (e.g. eduroam) Status in iwd package in Ubuntu: Fix Released Bug description: I believe my Kinetic system installed iwd with updates today, and now I am unable to my University's WPA2 Enterprise network eduroam. There is a no graphical error message, it just never connects. I tried forgetting the network and re-adding, and again there's no error, but no connection is established. Looking in the Logs app, I see messages like "Failed to add new connection: (5) 802.1x connections must have IWD provisioning files". ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: iwd 1.30-1ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0 Uname: Linux 5.19.0-15-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.23.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Sep 27 09:32:38 2022 InstallationDate: Installed on 2022-08-25 (32 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220825) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: iwd UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iwd/+bug/1990986/+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 1991138] [NEW] 16.04.1+18.10.20180917-0ubuntu8 fails to build from source
Public bug reported: [Log] https://launchpadlibrarian.net/625439356/buildlog_ubuntu-kinetic-armhf.libdbusmenu_16.04.1+18.10.20180917-0ubuntu8_BUILDING.txt.gz ** Affects: libdbusmenu (Ubuntu) Importance: Undecided Status: New ** Tags: patch -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libdbusmenu in Ubuntu. https://bugs.launchpad.net/bugs/1991138 Title: 16.04.1+18.10.20180917-0ubuntu8 fails to build from source Status in libdbusmenu package in Ubuntu: New Bug description: [Log] https://launchpadlibrarian.net/625439356/buildlog_ubuntu-kinetic-armhf.libdbusmenu_16.04.1+18.10.20180917-0ubuntu8_BUILDING.txt.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdbusmenu/+bug/1991138/+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 510625] Re: Bad parsing of GnuPG output, expecting english output, which doesn't work if locales different than english.
** Changed in: duplicity Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to duplicity in Ubuntu. https://bugs.launchpad.net/bugs/510625 Title: Bad parsing of GnuPG output, expecting english output, which doesn't work if locales different than english. Status in Duplicity: Fix Released Status in duplicity package in Ubuntu: Confirmed Status in duplicity package in Debian: Confirmed Bug description: this is a forward/extract of debian bug #565398, which lives over there: http://bugs.debian.org/565398 summary: when using gpg and --encrypt-key, and only if LANG is set to de_AT and LC_CTYPE is set to de_AT (or POSIX or C, but not iso-8859-1 or utf-8), then incremental backups fail completely. somehow or other duplicity mis-interprets gnupg output and errors out: i assume it would be the 8-bit nature of certain phrases like "Schlüssel" (german for "key") which causes the mess, but i can't identify the code in question. reproducible: always. needs only an empty backup dir (source), an empty target dir (target), a gpg key and locale de_AT available. duplicity --encrypt-key KEYID source file://target works fine, creates a (minuscule) full backup running it again, with LANG unset (or to something purely 7bit like en_US) works perfect again, no problems. but running it with LANG=de_AT and LC_CTYPE=de_AT causes duplicity to attempt some gnupg decryption (of what? the cache and archive are in sync), and it dies with a gpg failure (with the gpg message being the german equivalent of "encryption failed: bad passphrase", not surprising as no passphrase was given, nor should one be necessary). i'm attaching the relevant -v9 logs, first of the successful full run, then of a failed inc run (LANG and LC_CTYPE=de_AT) and then of the successful inc run (LANG="", LC_CTYPE=de_AT). no changes were made to the source dir between runs. regards, az To manage notifications about this bug go to: https://bugs.launchpad.net/duplicity/+bug/510625/+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 1991136] [NEW] Delays when starting alacritty with version 22.0.0-1ubuntu0.1
Public bug reported: With version 22.0.0-1ubuntu0.1 there's a delay of up to 2 seconds when starting alacritty [1], downgrading to version 22.0.0-1build1 fixes the issue. I'm using a Thinkpad E14 Gen3 with a Ryzen 7 5700U with integrated graphics. [1] https://github.com/alacritty/alacritty ** Affects: xserver-xorg-video-amdgpu (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-amdgpu in Ubuntu. https://bugs.launchpad.net/bugs/1991136 Title: Delays when starting alacritty with version 22.0.0-1ubuntu0.1 Status in xserver-xorg-video-amdgpu package in Ubuntu: New Bug description: With version 22.0.0-1ubuntu0.1 there's a delay of up to 2 seconds when starting alacritty [1], downgrading to version 22.0.0-1build1 fixes the issue. I'm using a Thinkpad E14 Gen3 with a Ryzen 7 5700U with integrated graphics. [1] https://github.com/alacritty/alacritty To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-amdgpu/+bug/1991136/+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 1991079] Re: There was an error playing video from the webcam
I have just a black window with 'There was an error playing video from the webcam' ** Attachment added: "Screenshot from 2022-09-28 10-51-33.png" https://bugs.launchpad.net/ubuntu/+source/cheese/+bug/1991079/+attachment/5619811/+files/Screenshot%20from%202022-09-28%2010-51-33.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cheese in Ubuntu. https://bugs.launchpad.net/bugs/1991079 Title: There was an error playing video from the webcam Status in cheese package in Ubuntu: New Bug description: On Ubuntu 22.10 starting cheese takes many seconds ant then I have a vindow with message: 'There was an error playing video from the webcam' corrado@corrado-n3-kk-0908:~$ date && time cheese && date mer 28 set 2022, 10:50:49, CEST (cheese:2674): Gdk-WARNING **: 10:50:49.761: Native Windows taller than 65535 pixels are not supported (cheese:2674): cheese-WARNING **: 10:51:20.114: Internal data stream error.: ../libs/gst/base/gstbasesrc.c(3127): gst_base_src_loop (): /GstCameraBin:camerabin/GstWrapperCameraBinSrc:camera_source/GstBin:bin18/GstPipeWireSrc:pipewiresrc1: streaming stopped, reason not-negotiated (-4) (cheese:2674): Clutter-CRITICAL **: 10:51:36.870: Unable to create dummy onscreen: No foreign surface, and wl_shell unsupported by the compositor real 0m47,359s user 0m0,442s sys 0m0,109s mer 28 set 2022, 10:51:36, CEST corrado@corrado-n3-kk-0908:~$ apt policy cheese cheese: Installed: 43~alpha-1 Candidate: 43~alpha-1 Version table: *** 43~alpha-1 500 500 http://archive.ubuntu.com/ubuntu kinetic/main amd64 Packages 100 /var/lib/dpkg/status corrado@corrado-n3-kk-0908:~$ If I try to open the problem with 'ubuntu-bug cheese' cheese captures the command and produces an unusable bug. atthaching journal --- ProblemType: Bug ApportVersion: 2.23.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.10 InstallationDate: Installed on 2022-09-08 (19 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220908) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. Package: cheese 43~alpha-1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0 RelatedPackageVersions: cheese43~alpha-1 cheese-common 43~alpha-1 Tags: kinetic wayland-session gstreamer-error Uname: Linux 5.19.0-15-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/11/2017 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.10 dmi.board.name: H110M-G/M.2 dmi.board.vendor: ASRock dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.10:bd05/11/2017:br5.12:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH110M-G/M.2:rvr:cvnToBeFilledByO.E.M.: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: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cheese/+bug/1991079/+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 1991117] Re: 13.3.0-3build1 fails to build from source
** Patch added: "xorg-vmware.diff" https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-vmware/+bug/1991117/+attachment/5619810/+files/xorg-vmware.diff -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-vmware in Ubuntu. https://bugs.launchpad.net/bugs/1991117 Title: 13.3.0-3build1 fails to build from source Status in xserver-xorg-video-vmware package in Ubuntu: New Bug description: [Log] https://launchpadlibrarian.net/625441992/buildlog_ubuntu-kinetic-amd64.xserver-xorg-video-vmware_1%3A13.3.0-3build1_BUILDING.txt.gz [Error] ../../vmwgfx/vmwgfx_tex_video.c: In function ‘stop_video’: ../../vmwgfx/vmwgfx_tex_video.c:240:20: error: the comparison will always evaluate as ‘true’ for the address of ‘yuv’ will never be NULL [-Werror=address] 240 |if (priv->yuv[i]) { |^~~~ ../../vmwgfx/vmwgfx_tex_video.c:125:24: note: ‘yuv’ declared here 125 | struct xa_surface *yuv[2][3]; |^~~ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-vmware/+bug/1991117/+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 1991117] [NEW] 13.3.0-3build1 fails to build from source
Public bug reported: [Log] https://launchpadlibrarian.net/625441992/buildlog_ubuntu-kinetic-amd64.xserver-xorg-video-vmware_1%3A13.3.0-3build1_BUILDING.txt.gz [Error] ../../vmwgfx/vmwgfx_tex_video.c: In function ‘stop_video’: ../../vmwgfx/vmwgfx_tex_video.c:240:20: error: the comparison will always evaluate as ‘true’ for the address of ‘yuv’ will never be NULL [-Werror=address] 240 |if (priv->yuv[i]) { |^~~~ ../../vmwgfx/vmwgfx_tex_video.c:125:24: note: ‘yuv’ declared here 125 | struct xa_surface *yuv[2][3]; |^~~ ** Affects: xserver-xorg-video-vmware (Ubuntu) Importance: Undecided Status: New ** Tags: patch -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-vmware in Ubuntu. https://bugs.launchpad.net/bugs/1991117 Title: 13.3.0-3build1 fails to build from source Status in xserver-xorg-video-vmware package in Ubuntu: New Bug description: [Log] https://launchpadlibrarian.net/625441992/buildlog_ubuntu-kinetic-amd64.xserver-xorg-video-vmware_1%3A13.3.0-3build1_BUILDING.txt.gz [Error] ../../vmwgfx/vmwgfx_tex_video.c: In function ‘stop_video’: ../../vmwgfx/vmwgfx_tex_video.c:240:20: error: the comparison will always evaluate as ‘true’ for the address of ‘yuv’ will never be NULL [-Werror=address] 240 |if (priv->yuv[i]) { |^~~~ ../../vmwgfx/vmwgfx_tex_video.c:125:24: note: ‘yuv’ declared here 125 | struct xa_surface *yuv[2][3]; |^~~ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-vmware/+bug/1991117/+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 1991100] Re: 2.3.3.4+dfsg-1ubuntu5 fails to build from source
** Patch added: "clucene.diff" https://bugs.launchpad.net/ubuntu/+source/clucene-core/+bug/1991100/+attachment/5619789/+files/clucene.diff ** Tags added: patch -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to clucene-core in Ubuntu. https://bugs.launchpad.net/bugs/1991100 Title: 2.3.3.4+dfsg-1ubuntu5 fails to build from source Status in clucene-core package in Ubuntu: New Bug description: Log: https://launchpadlibrarian.net/625441502/buildlog_ubuntu-kinetic- amd64.clucene-core_2.3.3.4+dfsg-1ubuntu5_BUILDING.txt.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/clucene-core/+bug/1991100/+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 1991079] Re: There was an error playing video from the webcam
please check bug : https://bugs.launchpad.net/ubuntu/+source/cheese/+bug/1949183 and see if you have the same symptons as possible dupe -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cheese in Ubuntu. https://bugs.launchpad.net/bugs/1991079 Title: There was an error playing video from the webcam Status in cheese package in Ubuntu: New Bug description: On Ubuntu 22.10 starting cheese takes many seconds ant then I have a vindow with message: 'There was an error playing video from the webcam' corrado@corrado-n3-kk-0908:~$ date && time cheese && date mer 28 set 2022, 10:50:49, CEST (cheese:2674): Gdk-WARNING **: 10:50:49.761: Native Windows taller than 65535 pixels are not supported (cheese:2674): cheese-WARNING **: 10:51:20.114: Internal data stream error.: ../libs/gst/base/gstbasesrc.c(3127): gst_base_src_loop (): /GstCameraBin:camerabin/GstWrapperCameraBinSrc:camera_source/GstBin:bin18/GstPipeWireSrc:pipewiresrc1: streaming stopped, reason not-negotiated (-4) (cheese:2674): Clutter-CRITICAL **: 10:51:36.870: Unable to create dummy onscreen: No foreign surface, and wl_shell unsupported by the compositor real 0m47,359s user 0m0,442s sys 0m0,109s mer 28 set 2022, 10:51:36, CEST corrado@corrado-n3-kk-0908:~$ apt policy cheese cheese: Installed: 43~alpha-1 Candidate: 43~alpha-1 Version table: *** 43~alpha-1 500 500 http://archive.ubuntu.com/ubuntu kinetic/main amd64 Packages 100 /var/lib/dpkg/status corrado@corrado-n3-kk-0908:~$ If I try to open the problem with 'ubuntu-bug cheese' cheese captures the command and produces an unusable bug. atthaching journal --- ProblemType: Bug ApportVersion: 2.23.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.10 InstallationDate: Installed on 2022-09-08 (19 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220908) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. Package: cheese 43~alpha-1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0 RelatedPackageVersions: cheese43~alpha-1 cheese-common 43~alpha-1 Tags: kinetic wayland-session gstreamer-error Uname: Linux 5.19.0-15-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/11/2017 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.10 dmi.board.name: H110M-G/M.2 dmi.board.vendor: ASRock dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.10:bd05/11/2017:br5.12:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH110M-G/M.2:rvr:cvnToBeFilledByO.E.M.: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: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cheese/+bug/1991079/+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 1991100] [NEW] 2.3.3.4+dfsg-1ubuntu5 fails to build from source
Public bug reported: Log: https://launchpadlibrarian.net/625441502/buildlog_ubuntu-kinetic- amd64.clucene-core_2.3.3.4+dfsg-1ubuntu5_BUILDING.txt.gz ** Affects: clucene-core (Ubuntu) Importance: Undecided Status: New ** Tags: patch -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to clucene-core in Ubuntu. https://bugs.launchpad.net/bugs/1991100 Title: 2.3.3.4+dfsg-1ubuntu5 fails to build from source Status in clucene-core package in Ubuntu: New Bug description: Log: https://launchpadlibrarian.net/625441502/buildlog_ubuntu-kinetic- amd64.clucene-core_2.3.3.4+dfsg-1ubuntu5_BUILDING.txt.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/clucene-core/+bug/1991100/+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 1988836] Re: Enable the open NVIDIA kernel modules
Hi Chris, I had missed one commit, which caused a FTBFS. I have uploaded a new revision (515.65.01-0ubuntu0.20.04.3) for Focal. The fix is also in Jammy (515.65.01-0ubuntu0.22.04.3). I would be grateful if you could approve both. Thanks. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1988836 Title: Enable the open NVIDIA kernel modules Status in linux-restricted-modules package in Ubuntu: In Progress Status in nvidia-graphics-drivers-515 package in Ubuntu: Fix Released Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in linux-restricted-modules source package in Focal: In Progress Status in nvidia-graphics-drivers-515 source package in Focal: Fix Committed Status in ubuntu-drivers-common source package in Focal: In Progress Status in linux-restricted-modules source package in Jammy: In Progress Status in nvidia-graphics-drivers-515 source package in Jammy: In Progress Status in ubuntu-drivers-common source package in Jammy: In Progress Bug description: [ Impact ] * The 515 series introduced open kernel modules for the NVIDIA driver. They come with an open source licence, and should be provided as an option for datacenter GPUs: https://developer.nvidia.com/blog/nvidia-releases-open-source-gpu-kernel-modules/ Currently, this is only production-ready (and enabled) on datacenter GPUs. * We should enable signed modules for the 515-open drivers, giving users the option to try the drivers. * The ubuntu-drivers tool should set a lower priority for the -open flavour, so that we do not end up recommending it over the plain 515 flavour. [ Test Plan ] * [ubuntu-drivers-common]: "sudo ubuntu-drivers install (to make sure the driver is not installed by default)" * [nvidia driver] "sudo ubuntu-drivers install nvidia:515-open" to make sure that the driver can be installed manually. Please make sure that this installs the correct linux-restricted- modules. Note: support for GeForce and Workstation GPUs is alpha-quality, and is disabled by default. This means that desktop testing is not needed at the moment. [ Where problems could occur ] * This adds a new driver combination, which is not meant to be default, and is only enabled for a limited amount of devices (datacenter GPUs). * We need to be sure that the driver is not recommended over the other drivers. [ Other Info ] - To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules/+bug/1988836/+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 1990456] Autopkgtest regression report (xorg-server/2:21.1.3-2ubuntu2.2)
All autopkgtests for the newly accepted xorg-server (2:21.1.3-2ubuntu2.2) for jammy have finished running. The following regressions have been reported in tests triggered by the package: mpv-mpris/0.6-2 (arm64) jsurf-alggeo/0.4.1+ds-3 (s390x) ktimetracker/4:5.0.1-3 (armhf) sfepy/2021.4-1ubuntu1 (armhf) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/jammy/update_excuses.html#xorg-server [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- 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/1990456 Title: xorg reports bogus 1600x1024 resolution Status in OEM Priority Project: New Status in xorg-server package in Ubuntu: Fix Released Status in xorg-server source package in Jammy: Fix Committed Bug description: xorg reports 1600x1024 bogus resolution [ Impact ] * User of NVIDIA GPU is able to switch to 1600x1024 resolution but cannot display anything under the resolution [ Fix ] Drop 001_fedora_extramodes.patch which was dropped from Fedora since xserver 1.5.0. [ Test Plan ] 1. Find a test unit with NVIDIA GPU, or anything but use Xorg mode to enter the desktop 2. Type `xrandr` in terminal Expected: The resolution 1600x1024 should not appear if the display does not support it. Actual: The resolution 1600x1024 appears. [ Where problems could occur ] * Lack of extra modes that the display might actually support. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1990456/+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 1991022] Re: Feature freeze exception: Socket activation
** Description changed: [Description] Systemd socket activation for Speech Dispatcher. - - - Creates the speech-dispatcher.socket; - - Modifies the server so that it can detect it was automatically launched by that socket activation; and - - Modifies the Autotools files accordingly. + + - Creates the speech-dispatcher.socket; + - Modifies the server so that it can detect it was automatically launched by that socket activation; and + - Modifies the Autotools files accordingly. [Rationale] It's relevance is described in [1], of which I quote the essential parts [my notes in brackets]: > Sandboxed applications [snaps] that use Speech Dispatcher currently bundle it inside of the sandbox, so that each application has its own "private" instance of Speech Dispatcher running. This works more or less, but it has the downside that speech dispatcher cannot coordinate simultaneous messages from multiple apps. When multiple sandboxed apps use Speech Dispatcher at the same time, the text reading overlaps. > > In order to solve this issue, I would really like to give sandboxed apps access to the Speech Dispatcher instance of the host. And then, > The only issue I see is having it auto launch. I think it would probably be a good step forward for speech-dispatcher to be auto launched by a systemd socket like other daemons already do on demand. That way the host speech-dispatcher with it's configuration would be used by all snaps, [Additional information] - The change was already proposed upstream[2], but it is on hold because - the build with undefined sanitizer CI failed two times out of four. In - the words of the maintainer, - - > That's not systematic, but that's often enough that it'll be a pain in - the CI, and is a sign of some subtle bug creeping in there. - - I then opened my own fork with debugging enabled[3] to track down the - problem, but the CI succeeded all the six times I executed it[4], so at - this point I'd assume it was a transient issue more than a subtle bug. + The changes are already merged upstream[2], but still not released. I have built and installed the package in Kinetic and verified that spd- say still causes the dispatcher spawn and emits sound. Upstream test can also confirm this. [1]: https://github.com/brailcom/speechd/issues/335 [2]: https://github.com/brailcom/speechd/pull/763 - [3]: https://github.com/brailcom/speechd/commit/a63a5f7fe187edd5bf60c12a9c8e078cd2234e73 - [4]: https://github.com/nteodosio/speechd/actions/runs/3129483607 ** Patch added: "0.11.3-1--0.11.3-1ubuntu1.diff" https://bugs.launchpad.net/bugs/1991022/+attachment/5619783/+files/0.11.3-1--0.11.3-1ubuntu1.diff ** Attachment added: "speechd-apt-install-log" https://bugs.launchpad.net/bugs/1991022/+attachment/5619784/+files/speechd-apt-install-log ** Tags removed: wip -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to speech-dispatcher in Ubuntu. https://bugs.launchpad.net/bugs/1991022 Title: Feature freeze exception: Socket activation Status in speech-dispatcher package in Ubuntu: New Bug description: [Description] Systemd socket activation for Speech Dispatcher. - Creates the speech-dispatcher.socket; - Modifies the server so that it can detect it was automatically launched by that socket activation; and - Modifies the Autotools files accordingly. [Rationale] It's relevance is described in [1], of which I quote the essential parts [my notes in brackets]: > Sandboxed applications [snaps] that use Speech Dispatcher currently bundle it inside of the sandbox, so that each application has its own "private" instance of Speech Dispatcher running. This works more or less, but it has the downside that speech dispatcher cannot coordinate simultaneous messages from multiple apps. When multiple sandboxed apps use Speech Dispatcher at the same time, the text reading overlaps. > > In order to solve this issue, I would really like to give sandboxed apps access to the Speech Dispatcher instance of the host. And then, > The only issue I see is having it auto launch. I think it would probably be a good step forward for speech-dispatcher to be auto launched by a systemd socket like other daemons already do on demand. That way the host speech-dispatcher with it's configuration would be used by all snaps, [Additional information] The changes are already merged upstream[2], but still not released. I have built and installed the package in Kinetic and verified that spd-say still causes the dispatcher spawn and emits sound. Upstream test can also confirm this. [1]: https://github.com/brailcom/speechd/issues/335 [2]: https://github.com/brailcom/speechd/pull/763 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/speech-dispatcher/+bug/1991022/+subscriptions -- Maili
[Desktop-packages] [Bug 1989964] Re: Segmentation fault crocus_dri.so (X server dies)
[335842.604] (WW) glamor: Failed to allocate 128x88 FBO due to GL_OUT_OF_MEMORY. [335842.604] (WW) glamor: Expect reduced performance. [335844.555] (EE) glamor0: GL error: GL_OUT_OF_MEMORY in glMapBuffer(map failed) followed by [335844.561] (EE) glamor0: GL error: GL_INVALID_OPERATION in glUnmapBuffer(buffer is not mapped) It looks like a failed allocation is not detected, and an illegal unmap follows. >From a distant it looks like an application is exhausting the Xserver memory, en the Xserver is not robust enough to report these problems to the application program and stay unaffected. When it is followed by a segmentation error later it sure looks like memory corruption, due to not detecting the failure return from glMapBuffer. -- 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/1989964 Title: Segmentation fault crocus_dri.so (X server dies) Status in mesa package in Ubuntu: New Bug description: The desktop session is running for 0 or more days. Suddenly the X server dies, and login screen reappears. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: libgl1-mesa-dri 22.0.5-0ubuntu0.1 ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46 Uname: Linux 5.15.0-47-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: MATE Date: Fri Sep 16 14:45:54 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [103c:18e4] MachineType: Hewlett-Packard HP EliteDesk 800 G1 TWR ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-47-generic root=/dev/mapper/sun--vg-root ro SourcePackage: mesa UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/16/2015 dmi.bios.release: 2.59 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: L01 v02.59 dmi.board.name: 18E4 dmi.board.vendor: Hewlett-Packard dmi.chassis.type: 6 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvrL01v02.59:bd03/16/2015:br2.59:svnHewlett-Packard:pnHPEliteDesk800G1TWR:pvr:rvnHewlett-Packard:rn18E4:rvr:cvnHewlett-Packard:ct6:cvr:skuC8N27AV: dmi.product.family: 103C_53307F G=D dmi.product.name: HP EliteDesk 800 G1 TWR dmi.product.sku: C8N27AV dmi.sys.vendor: Hewlett-Packard 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 22.0.5-0ubuntu0.1 version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-2build1 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/mesa/+bug/1989964/+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 1991079] lsusb.txt
apport information ** Attachment added: "lsusb.txt" https://bugs.launchpad.net/bugs/1991079/+attachment/5619760/+files/lsusb.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cheese in Ubuntu. https://bugs.launchpad.net/bugs/1991079 Title: There was an error playing video from the webcam Status in cheese package in Ubuntu: New Bug description: On Ubuntu 22.10 starting cheese takes many seconds ant then I have a vindow with message: 'There was an error playing video from the webcam' corrado@corrado-n3-kk-0908:~$ date && time cheese && date mer 28 set 2022, 10:50:49, CEST (cheese:2674): Gdk-WARNING **: 10:50:49.761: Native Windows taller than 65535 pixels are not supported (cheese:2674): cheese-WARNING **: 10:51:20.114: Internal data stream error.: ../libs/gst/base/gstbasesrc.c(3127): gst_base_src_loop (): /GstCameraBin:camerabin/GstWrapperCameraBinSrc:camera_source/GstBin:bin18/GstPipeWireSrc:pipewiresrc1: streaming stopped, reason not-negotiated (-4) (cheese:2674): Clutter-CRITICAL **: 10:51:36.870: Unable to create dummy onscreen: No foreign surface, and wl_shell unsupported by the compositor real 0m47,359s user 0m0,442s sys 0m0,109s mer 28 set 2022, 10:51:36, CEST corrado@corrado-n3-kk-0908:~$ apt policy cheese cheese: Installed: 43~alpha-1 Candidate: 43~alpha-1 Version table: *** 43~alpha-1 500 500 http://archive.ubuntu.com/ubuntu kinetic/main amd64 Packages 100 /var/lib/dpkg/status corrado@corrado-n3-kk-0908:~$ If I try to open the problem with 'ubuntu-bug cheese' cheese captures the command and produces an unusable bug. atthaching journal --- ProblemType: Bug ApportVersion: 2.23.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.10 InstallationDate: Installed on 2022-09-08 (19 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220908) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. Package: cheese 43~alpha-1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0 RelatedPackageVersions: cheese43~alpha-1 cheese-common 43~alpha-1 Tags: kinetic wayland-session gstreamer-error Uname: Linux 5.19.0-15-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/11/2017 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.10 dmi.board.name: H110M-G/M.2 dmi.board.vendor: ASRock dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.10:bd05/11/2017:br5.12:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH110M-G/M.2:rvr:cvnToBeFilledByO.E.M.: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: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cheese/+bug/1991079/+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 1991079] Dependencies.txt
apport information ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1991079/+attachment/5619755/+files/Dependencies.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cheese in Ubuntu. https://bugs.launchpad.net/bugs/1991079 Title: There was an error playing video from the webcam Status in cheese package in Ubuntu: New Bug description: On Ubuntu 22.10 starting cheese takes many seconds ant then I have a vindow with message: 'There was an error playing video from the webcam' corrado@corrado-n3-kk-0908:~$ date && time cheese && date mer 28 set 2022, 10:50:49, CEST (cheese:2674): Gdk-WARNING **: 10:50:49.761: Native Windows taller than 65535 pixels are not supported (cheese:2674): cheese-WARNING **: 10:51:20.114: Internal data stream error.: ../libs/gst/base/gstbasesrc.c(3127): gst_base_src_loop (): /GstCameraBin:camerabin/GstWrapperCameraBinSrc:camera_source/GstBin:bin18/GstPipeWireSrc:pipewiresrc1: streaming stopped, reason not-negotiated (-4) (cheese:2674): Clutter-CRITICAL **: 10:51:36.870: Unable to create dummy onscreen: No foreign surface, and wl_shell unsupported by the compositor real 0m47,359s user 0m0,442s sys 0m0,109s mer 28 set 2022, 10:51:36, CEST corrado@corrado-n3-kk-0908:~$ apt policy cheese cheese: Installed: 43~alpha-1 Candidate: 43~alpha-1 Version table: *** 43~alpha-1 500 500 http://archive.ubuntu.com/ubuntu kinetic/main amd64 Packages 100 /var/lib/dpkg/status corrado@corrado-n3-kk-0908:~$ If I try to open the problem with 'ubuntu-bug cheese' cheese captures the command and produces an unusable bug. atthaching journal --- ProblemType: Bug ApportVersion: 2.23.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.10 InstallationDate: Installed on 2022-09-08 (19 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220908) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. Package: cheese 43~alpha-1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0 RelatedPackageVersions: cheese43~alpha-1 cheese-common 43~alpha-1 Tags: kinetic wayland-session gstreamer-error Uname: Linux 5.19.0-15-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/11/2017 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.10 dmi.board.name: H110M-G/M.2 dmi.board.vendor: ASRock dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.10:bd05/11/2017:br5.12:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH110M-G/M.2:rvr:cvnToBeFilledByO.E.M.: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: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cheese/+bug/1991079/+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 1991079] lspci.txt
apport information ** Attachment added: "lspci.txt" https://bugs.launchpad.net/bugs/1991079/+attachment/5619759/+files/lspci.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cheese in Ubuntu. https://bugs.launchpad.net/bugs/1991079 Title: There was an error playing video from the webcam Status in cheese package in Ubuntu: New Bug description: On Ubuntu 22.10 starting cheese takes many seconds ant then I have a vindow with message: 'There was an error playing video from the webcam' corrado@corrado-n3-kk-0908:~$ date && time cheese && date mer 28 set 2022, 10:50:49, CEST (cheese:2674): Gdk-WARNING **: 10:50:49.761: Native Windows taller than 65535 pixels are not supported (cheese:2674): cheese-WARNING **: 10:51:20.114: Internal data stream error.: ../libs/gst/base/gstbasesrc.c(3127): gst_base_src_loop (): /GstCameraBin:camerabin/GstWrapperCameraBinSrc:camera_source/GstBin:bin18/GstPipeWireSrc:pipewiresrc1: streaming stopped, reason not-negotiated (-4) (cheese:2674): Clutter-CRITICAL **: 10:51:36.870: Unable to create dummy onscreen: No foreign surface, and wl_shell unsupported by the compositor real 0m47,359s user 0m0,442s sys 0m0,109s mer 28 set 2022, 10:51:36, CEST corrado@corrado-n3-kk-0908:~$ apt policy cheese cheese: Installed: 43~alpha-1 Candidate: 43~alpha-1 Version table: *** 43~alpha-1 500 500 http://archive.ubuntu.com/ubuntu kinetic/main amd64 Packages 100 /var/lib/dpkg/status corrado@corrado-n3-kk-0908:~$ If I try to open the problem with 'ubuntu-bug cheese' cheese captures the command and produces an unusable bug. atthaching journal --- ProblemType: Bug ApportVersion: 2.23.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.10 InstallationDate: Installed on 2022-09-08 (19 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220908) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. Package: cheese 43~alpha-1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0 RelatedPackageVersions: cheese43~alpha-1 cheese-common 43~alpha-1 Tags: kinetic wayland-session gstreamer-error Uname: Linux 5.19.0-15-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/11/2017 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.10 dmi.board.name: H110M-G/M.2 dmi.board.vendor: ASRock dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.10:bd05/11/2017:br5.12:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH110M-G/M.2:rvr:cvnToBeFilledByO.E.M.: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: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cheese/+bug/1991079/+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 1991079] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1991079/+attachment/5619758/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cheese in Ubuntu. https://bugs.launchpad.net/bugs/1991079 Title: There was an error playing video from the webcam Status in cheese package in Ubuntu: New Bug description: On Ubuntu 22.10 starting cheese takes many seconds ant then I have a vindow with message: 'There was an error playing video from the webcam' corrado@corrado-n3-kk-0908:~$ date && time cheese && date mer 28 set 2022, 10:50:49, CEST (cheese:2674): Gdk-WARNING **: 10:50:49.761: Native Windows taller than 65535 pixels are not supported (cheese:2674): cheese-WARNING **: 10:51:20.114: Internal data stream error.: ../libs/gst/base/gstbasesrc.c(3127): gst_base_src_loop (): /GstCameraBin:camerabin/GstWrapperCameraBinSrc:camera_source/GstBin:bin18/GstPipeWireSrc:pipewiresrc1: streaming stopped, reason not-negotiated (-4) (cheese:2674): Clutter-CRITICAL **: 10:51:36.870: Unable to create dummy onscreen: No foreign surface, and wl_shell unsupported by the compositor real 0m47,359s user 0m0,442s sys 0m0,109s mer 28 set 2022, 10:51:36, CEST corrado@corrado-n3-kk-0908:~$ apt policy cheese cheese: Installed: 43~alpha-1 Candidate: 43~alpha-1 Version table: *** 43~alpha-1 500 500 http://archive.ubuntu.com/ubuntu kinetic/main amd64 Packages 100 /var/lib/dpkg/status corrado@corrado-n3-kk-0908:~$ If I try to open the problem with 'ubuntu-bug cheese' cheese captures the command and produces an unusable bug. atthaching journal --- ProblemType: Bug ApportVersion: 2.23.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.10 InstallationDate: Installed on 2022-09-08 (19 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220908) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. Package: cheese 43~alpha-1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0 RelatedPackageVersions: cheese43~alpha-1 cheese-common 43~alpha-1 Tags: kinetic wayland-session gstreamer-error Uname: Linux 5.19.0-15-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/11/2017 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.10 dmi.board.name: H110M-G/M.2 dmi.board.vendor: ASRock dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.10:bd05/11/2017:br5.12:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH110M-G/M.2:rvr:cvnToBeFilledByO.E.M.: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: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cheese/+bug/1991079/+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 1991079] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1991079/+attachment/5619757/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cheese in Ubuntu. https://bugs.launchpad.net/bugs/1991079 Title: There was an error playing video from the webcam Status in cheese package in Ubuntu: New Bug description: On Ubuntu 22.10 starting cheese takes many seconds ant then I have a vindow with message: 'There was an error playing video from the webcam' corrado@corrado-n3-kk-0908:~$ date && time cheese && date mer 28 set 2022, 10:50:49, CEST (cheese:2674): Gdk-WARNING **: 10:50:49.761: Native Windows taller than 65535 pixels are not supported (cheese:2674): cheese-WARNING **: 10:51:20.114: Internal data stream error.: ../libs/gst/base/gstbasesrc.c(3127): gst_base_src_loop (): /GstCameraBin:camerabin/GstWrapperCameraBinSrc:camera_source/GstBin:bin18/GstPipeWireSrc:pipewiresrc1: streaming stopped, reason not-negotiated (-4) (cheese:2674): Clutter-CRITICAL **: 10:51:36.870: Unable to create dummy onscreen: No foreign surface, and wl_shell unsupported by the compositor real 0m47,359s user 0m0,442s sys 0m0,109s mer 28 set 2022, 10:51:36, CEST corrado@corrado-n3-kk-0908:~$ apt policy cheese cheese: Installed: 43~alpha-1 Candidate: 43~alpha-1 Version table: *** 43~alpha-1 500 500 http://archive.ubuntu.com/ubuntu kinetic/main amd64 Packages 100 /var/lib/dpkg/status corrado@corrado-n3-kk-0908:~$ If I try to open the problem with 'ubuntu-bug cheese' cheese captures the command and produces an unusable bug. atthaching journal --- ProblemType: Bug ApportVersion: 2.23.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.10 InstallationDate: Installed on 2022-09-08 (19 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220908) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. Package: cheese 43~alpha-1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0 RelatedPackageVersions: cheese43~alpha-1 cheese-common 43~alpha-1 Tags: kinetic wayland-session gstreamer-error Uname: Linux 5.19.0-15-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/11/2017 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.10 dmi.board.name: H110M-G/M.2 dmi.board.vendor: ASRock dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.10:bd05/11/2017:br5.12:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH110M-G/M.2:rvr:cvnToBeFilledByO.E.M.: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: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cheese/+bug/1991079/+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 1991079] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1991079/+attachment/5619756/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cheese in Ubuntu. https://bugs.launchpad.net/bugs/1991079 Title: There was an error playing video from the webcam Status in cheese package in Ubuntu: New Bug description: On Ubuntu 22.10 starting cheese takes many seconds ant then I have a vindow with message: 'There was an error playing video from the webcam' corrado@corrado-n3-kk-0908:~$ date && time cheese && date mer 28 set 2022, 10:50:49, CEST (cheese:2674): Gdk-WARNING **: 10:50:49.761: Native Windows taller than 65535 pixels are not supported (cheese:2674): cheese-WARNING **: 10:51:20.114: Internal data stream error.: ../libs/gst/base/gstbasesrc.c(3127): gst_base_src_loop (): /GstCameraBin:camerabin/GstWrapperCameraBinSrc:camera_source/GstBin:bin18/GstPipeWireSrc:pipewiresrc1: streaming stopped, reason not-negotiated (-4) (cheese:2674): Clutter-CRITICAL **: 10:51:36.870: Unable to create dummy onscreen: No foreign surface, and wl_shell unsupported by the compositor real 0m47,359s user 0m0,442s sys 0m0,109s mer 28 set 2022, 10:51:36, CEST corrado@corrado-n3-kk-0908:~$ apt policy cheese cheese: Installed: 43~alpha-1 Candidate: 43~alpha-1 Version table: *** 43~alpha-1 500 500 http://archive.ubuntu.com/ubuntu kinetic/main amd64 Packages 100 /var/lib/dpkg/status corrado@corrado-n3-kk-0908:~$ If I try to open the problem with 'ubuntu-bug cheese' cheese captures the command and produces an unusable bug. atthaching journal --- ProblemType: Bug ApportVersion: 2.23.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.10 InstallationDate: Installed on 2022-09-08 (19 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220908) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. Package: cheese 43~alpha-1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0 RelatedPackageVersions: cheese43~alpha-1 cheese-common 43~alpha-1 Tags: kinetic wayland-session gstreamer-error Uname: Linux 5.19.0-15-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/11/2017 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.10 dmi.board.name: H110M-G/M.2 dmi.board.vendor: ASRock dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.10:bd05/11/2017:br5.12:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH110M-G/M.2:rvr:cvnToBeFilledByO.E.M.: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: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cheese/+bug/1991079/+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 1991079] Re: There was an error playing video from the webcam
apport information ** Tags added: apport-collected gstreamer-error kinetic wayland-session ** Description changed: On Ubuntu 22.10 starting cheese takes many seconds ant then I have a vindow with message: 'There was an error playing video from the webcam' corrado@corrado-n3-kk-0908:~$ date && time cheese && date mer 28 set 2022, 10:50:49, CEST (cheese:2674): Gdk-WARNING **: 10:50:49.761: Native Windows taller than 65535 pixels are not supported (cheese:2674): cheese-WARNING **: 10:51:20.114: Internal data stream error.: ../libs/gst/base/gstbasesrc.c(3127): gst_base_src_loop (): /GstCameraBin:camerabin/GstWrapperCameraBinSrc:camera_source/GstBin:bin18/GstPipeWireSrc:pipewiresrc1: streaming stopped, reason not-negotiated (-4) (cheese:2674): Clutter-CRITICAL **: 10:51:36.870: Unable to create dummy onscreen: No foreign surface, and wl_shell unsupported by the compositor real 0m47,359s user 0m0,442s sys 0m0,109s mer 28 set 2022, 10:51:36, CEST corrado@corrado-n3-kk-0908:~$ apt policy cheese cheese: Installed: 43~alpha-1 Candidate: 43~alpha-1 Version table: *** 43~alpha-1 500 500 http://archive.ubuntu.com/ubuntu kinetic/main amd64 Packages 100 /var/lib/dpkg/status corrado@corrado-n3-kk-0908:~$ If I try to open the problem with 'ubuntu-bug cheese' cheese captures the command and produces an unusable bug. atthaching journal + --- + ProblemType: Bug + ApportVersion: 2.23.0-0ubuntu2 + Architecture: amd64 + CasperMD5CheckResult: pass + CurrentDesktop: ubuntu:GNOME + DistroRelease: Ubuntu 22.10 + InstallationDate: Installed on 2022-09-08 (19 days ago) + InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220908) + MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. + Package: cheese 43~alpha-1 + PackageArchitecture: amd64 + ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0 + RelatedPackageVersions: + cheese43~alpha-1 + cheese-common 43~alpha-1 + Tags: kinetic wayland-session gstreamer-error + Uname: Linux 5.19.0-15-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo + _MarkForUpload: True + dmi.bios.date: 05/11/2017 + dmi.bios.release: 5.12 + dmi.bios.vendor: American Megatrends Inc. + dmi.bios.version: P1.10 + dmi.board.name: H110M-G/M.2 + dmi.board.vendor: ASRock + dmi.chassis.type: 3 + dmi.chassis.vendor: To Be Filled By O.E.M. + dmi.chassis.version: To Be Filled By O.E.M. + dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.10:bd05/11/2017:br5.12:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH110M-G/M.2:rvr:cvnToBeFilledByO.E.M.: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: To Be Filled By O.E.M. ** Attachment added: "CheeseDebug.txt.gz" https://bugs.launchpad.net/bugs/1991079/+attachment/5619754/+files/CheeseDebug.txt.gz -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cheese in Ubuntu. https://bugs.launchpad.net/bugs/1991079 Title: There was an error playing video from the webcam Status in cheese package in Ubuntu: New Bug description: On Ubuntu 22.10 starting cheese takes many seconds ant then I have a vindow with message: 'There was an error playing video from the webcam' corrado@corrado-n3-kk-0908:~$ date && time cheese && date mer 28 set 2022, 10:50:49, CEST (cheese:2674): Gdk-WARNING **: 10:50:49.761: Native Windows taller than 65535 pixels are not supported (cheese:2674): cheese-WARNING **: 10:51:20.114: Internal data stream error.: ../libs/gst/base/gstbasesrc.c(3127): gst_base_src_loop (): /GstCameraBin:camerabin/GstWrapperCameraBinSrc:camera_source/GstBin:bin18/GstPipeWireSrc:pipewiresrc1: streaming stopped, reason not-negotiated (-4) (cheese:2674): Clutter-CRITICAL **: 10:51:36.870: Unable to create dummy onscreen: No foreign surface, and wl_shell unsupported by the compositor real 0m47,359s user 0m0,442s sys 0m0,109s mer 28 set 2022, 10:51:36, CEST corrado@corrado-n3-kk-0908:~$ apt policy cheese cheese: Installed: 43~alpha-1 Candidate: 43~alpha-1 Version table: *** 43~alpha-1 500 500 http://archive.ubuntu.com/ubuntu kinetic/main amd64 Packages 100 /var/lib/dpkg/status corrado@corrado-n3-kk-0908:~$ If I try to open the problem with 'ubuntu-bug cheese' cheese captures the command and produces an unusable bug. atthaching journal --- ProblemType: Bug ApportVersion: 2.23.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.10 InstallationDate: Installed on 2022-09-08 (19 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kud
[Desktop-packages] [Bug 1990456] Re: xorg reports bogus 1600x1024 resolution
With new packages,this issue is fixed on ThinkPad P16. Commandline: apt install xserver-common xserver-xephyr xserver-xorg-core xserver-xorg-legacy Requested-By: u (1001) Upgrade: xserver-xorg-core:amd64 (2:21.1.3-2ubuntu2.1, 2:21.1.3-2ubuntu2.2), xserver-xorg-legacy:amd64 (2:21.1.3-2ubuntu2.1, 2:21.1.3-2ubuntu2.2), xserver-common:amd64 (2:21.1.3-2ubuntu2.1, 2:21.1.3-2ubuntu2.2), xserver-xephyr:amd64 (2:21.1.3-2ubuntu2.1, 2:21.1.3-2ubuntu2.2) End-Date: 2022-09-28 05:15:30 -- 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/1990456 Title: xorg reports bogus 1600x1024 resolution Status in OEM Priority Project: New Status in xorg-server package in Ubuntu: Fix Released Status in xorg-server source package in Jammy: Fix Committed Bug description: xorg reports 1600x1024 bogus resolution [ Impact ] * User of NVIDIA GPU is able to switch to 1600x1024 resolution but cannot display anything under the resolution [ Fix ] Drop 001_fedora_extramodes.patch which was dropped from Fedora since xserver 1.5.0. [ Test Plan ] 1. Find a test unit with NVIDIA GPU, or anything but use Xorg mode to enter the desktop 2. Type `xrandr` in terminal Expected: The resolution 1600x1024 should not appear if the display does not support it. Actual: The resolution 1600x1024 appears. [ Where problems could occur ] * Lack of extra modes that the display might actually support. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1990456/+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 1781810] Re: Plank dock is not showing an indicator when a certain application is open anymore and when an application that is open is clicked on the dock, a new instance of it
@ALinuxUser Thank you for the feedback. Would you please post version of your bamfdaemon? Mine is Version: 0.5.6+22.04.20220217-0ubuntu1 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to bamf in Ubuntu. https://bugs.launchpad.net/bugs/1781810 Title: Plank dock is not showing an indicator when a certain application is open anymore and when an application that is open is clicked on the dock, a new instance of it is opened Status in BAMF: Expired Status in Plank: Expired Status in bamf package in Ubuntu: Expired Status in plank package in Ubuntu: Expired Bug description: Plank version: 0.11.4 Distribution: Ubuntu MATE 18.04 DE: MATE Desktop Window manager: Marco Video card: Intel HD Graphics 4000 Plank comes installed with the system by default When i used Ubuntu MATE 16.04 it didn't happen. I had an indicator that the application i was clicking on was open and when i clicked it, it would be restored if it was minimized and it will be minimized if it was maximized or just being shown on the screen but on this version, even if the application is minimized or maximized, when i click on its icon, first of all, i can't see that "application open" indicator below its icon anymore(Only below the Plank icon) and second of all, Plank will open a new instance of that same application. I recorded a video showing you what i am talking about. And also, sometimes when i click on the icons on the dock, i won't have that visual feedback, that "little jump" of the icon i click. That's very important as well otherwise, i think nothing happened. That's all. I really like Plank and it is a great application. Thanks for it. Best wishes To manage notifications about this bug go to: https://bugs.launchpad.net/bamf/+bug/1781810/+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 1990521] Re: Open gnome-terminal window not shown in favorite list
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-shell (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1990521 Title: Open gnome-terminal window not shown in favorite list Status in gnome-shell package in Ubuntu: Confirmed Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Confirmed Bug description: I have gnome-terminal pinned as favorite . But when I open a window, gnome-terminal is shown at the bottom instead of adding a red dot to the pinned icon. That only happens with gnome-terminal. Other applications (eg. Thunderbird, hexchat, emacs) do have the dot beside the pinned icon. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: gnome-shell-extension-ubuntu-dock 72ubuntu6 ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0 Uname: Linux 5.19.0-15-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.23.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Sep 22 13:41:38 2022 InstallationDate: Installed on 2022-03-21 (184 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) PackageArchitecture: all SourcePackage: gnome-shell-extension-ubuntu-dock UpgradeStatus: Upgraded to kinetic on 2022-09-18 (3 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1990521/+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 1990521] Re: Open gnome-terminal window not shown in favorite list
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1990521 Title: Open gnome-terminal window not shown in favorite list Status in gnome-shell package in Ubuntu: Confirmed Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Confirmed Bug description: I have gnome-terminal pinned as favorite . But when I open a window, gnome-terminal is shown at the bottom instead of adding a red dot to the pinned icon. That only happens with gnome-terminal. Other applications (eg. Thunderbird, hexchat, emacs) do have the dot beside the pinned icon. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: gnome-shell-extension-ubuntu-dock 72ubuntu6 ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0 Uname: Linux 5.19.0-15-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.23.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Sep 22 13:41:38 2022 InstallationDate: Installed on 2022-03-21 (184 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) PackageArchitecture: all SourcePackage: gnome-shell-extension-ubuntu-dock UpgradeStatus: Upgraded to kinetic on 2022-09-18 (3 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1990521/+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 1990521] Re: Open gnome-terminal window not shown in favorite list
Same issue in vanilla gnome-shell (built from main) without extensions. So this probably is not an ubuntu-dock bug. ** Also affects: gnome-shell (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1990521 Title: Open gnome-terminal window not shown in favorite list Status in gnome-shell package in Ubuntu: Confirmed Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Confirmed Bug description: I have gnome-terminal pinned as favorite . But when I open a window, gnome-terminal is shown at the bottom instead of adding a red dot to the pinned icon. That only happens with gnome-terminal. Other applications (eg. Thunderbird, hexchat, emacs) do have the dot beside the pinned icon. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: gnome-shell-extension-ubuntu-dock 72ubuntu6 ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0 Uname: Linux 5.19.0-15-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.23.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Sep 22 13:41:38 2022 InstallationDate: Installed on 2022-03-21 (184 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) PackageArchitecture: all SourcePackage: gnome-shell-extension-ubuntu-dock UpgradeStatus: Upgraded to kinetic on 2022-09-18 (3 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1990521/+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 1991079] [NEW] There was an error playing video from the webcam
Public bug reported: On Ubuntu 22.10 starting cheese takes many seconds ant then I have a vindow with message: 'There was an error playing video from the webcam' corrado@corrado-n3-kk-0908:~$ date && time cheese && date mer 28 set 2022, 10:50:49, CEST (cheese:2674): Gdk-WARNING **: 10:50:49.761: Native Windows taller than 65535 pixels are not supported (cheese:2674): cheese-WARNING **: 10:51:20.114: Internal data stream error.: ../libs/gst/base/gstbasesrc.c(3127): gst_base_src_loop (): /GstCameraBin:camerabin/GstWrapperCameraBinSrc:camera_source/GstBin:bin18/GstPipeWireSrc:pipewiresrc1: streaming stopped, reason not-negotiated (-4) (cheese:2674): Clutter-CRITICAL **: 10:51:36.870: Unable to create dummy onscreen: No foreign surface, and wl_shell unsupported by the compositor real0m47,359s user0m0,442s sys 0m0,109s mer 28 set 2022, 10:51:36, CEST corrado@corrado-n3-kk-0908:~$ apt policy cheese cheese: Installed: 43~alpha-1 Candidate: 43~alpha-1 Version table: *** 43~alpha-1 500 500 http://archive.ubuntu.com/ubuntu kinetic/main amd64 Packages 100 /var/lib/dpkg/status corrado@corrado-n3-kk-0908:~$ If I try to open the problem with 'ubuntu-bug cheese' cheese captures the command and produces an unusable bug. atthaching journal ** Affects: cheese (Ubuntu) Importance: Undecided Status: New ** Attachment added: "journal.txt" https://bugs.launchpad.net/bugs/1991079/+attachment/5619742/+files/journal.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cheese in Ubuntu. https://bugs.launchpad.net/bugs/1991079 Title: There was an error playing video from the webcam Status in cheese package in Ubuntu: New Bug description: On Ubuntu 22.10 starting cheese takes many seconds ant then I have a vindow with message: 'There was an error playing video from the webcam' corrado@corrado-n3-kk-0908:~$ date && time cheese && date mer 28 set 2022, 10:50:49, CEST (cheese:2674): Gdk-WARNING **: 10:50:49.761: Native Windows taller than 65535 pixels are not supported (cheese:2674): cheese-WARNING **: 10:51:20.114: Internal data stream error.: ../libs/gst/base/gstbasesrc.c(3127): gst_base_src_loop (): /GstCameraBin:camerabin/GstWrapperCameraBinSrc:camera_source/GstBin:bin18/GstPipeWireSrc:pipewiresrc1: streaming stopped, reason not-negotiated (-4) (cheese:2674): Clutter-CRITICAL **: 10:51:36.870: Unable to create dummy onscreen: No foreign surface, and wl_shell unsupported by the compositor real 0m47,359s user 0m0,442s sys 0m0,109s mer 28 set 2022, 10:51:36, CEST corrado@corrado-n3-kk-0908:~$ apt policy cheese cheese: Installed: 43~alpha-1 Candidate: 43~alpha-1 Version table: *** 43~alpha-1 500 500 http://archive.ubuntu.com/ubuntu kinetic/main amd64 Packages 100 /var/lib/dpkg/status corrado@corrado-n3-kk-0908:~$ If I try to open the problem with 'ubuntu-bug cheese' cheese captures the command and produces an unusable bug. atthaching journal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cheese/+bug/1991079/+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 1034050] Re: Lame generate invalid filenames
This patch is included in lame 3.100 and therefore in Ubuntu >= 18.04. Therefore I am closing this bug as "Fix Released". ** Changed in: lame (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lame in Ubuntu. https://bugs.launchpad.net/bugs/1034050 Title: Lame generate invalid filenames Status in lame package in Ubuntu: Fix Released Bug description: When lame generate a .mp3 file it replaces the ".wav" in the extension to ".mp3" but generates an invalid filename when the original file has a colon in it, because under Windows the colon is the drive letter separator. The colon character should be handled differently under Windows and Unix OSes. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lame/+bug/1034050/+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 1071611] Re: package libmp3lame0 3.99.5+repack1-3 failed to install/upgrade: no package named `libmp3lame0' is installed, cannot configure
Thank you for taking the time to report this bug and helping to make Ubuntu better. The reported Ubuntu version is end of life and the current Ubuntu release seem to be unaffected. Therefore I am closing this bug as Won't Fix. In case you experience this issue with a recent Ubuntu version, don't hesitate to file another bug report. ** Changed in: lame (Ubuntu) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lame in Ubuntu. https://bugs.launchpad.net/bugs/1071611 Title: package libmp3lame0 3.99.5+repack1-3 failed to install/upgrade: no package named `libmp3lame0' is installed, cannot configure Status in lame package in Ubuntu: Won't Fix Bug description: Ubuntu 12.10 Fresh installation ProblemType: Package DistroRelease: Ubuntu 12.10 Package: libmp3lame0 3.99.5+repack1-3 ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5 Uname: Linux 3.5.0-17-generic x86_64 ApportVersion: 2.6.1-0ubuntu3 Architecture: amd64 Date: Fri Oct 26 09:50:08 2012 ErrorMessage: no package named `libmp3lame0' is installed, cannot configure InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) SourcePackage: lame Title: package libmp3lame0 3.99.5+repack1-3 failed to install/upgrade: no package named `libmp3lame0' is installed, cannot configure UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lame/+bug/1071611/+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 1071611] Re: package libmp3lame0 3.99.5+repack1-3 failed to install/upgrade: no package named `libmp3lame0' is installed, cannot configure
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: lame (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lame in Ubuntu. https://bugs.launchpad.net/bugs/1071611 Title: package libmp3lame0 3.99.5+repack1-3 failed to install/upgrade: no package named `libmp3lame0' is installed, cannot configure Status in lame package in Ubuntu: Won't Fix Bug description: Ubuntu 12.10 Fresh installation ProblemType: Package DistroRelease: Ubuntu 12.10 Package: libmp3lame0 3.99.5+repack1-3 ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5 Uname: Linux 3.5.0-17-generic x86_64 ApportVersion: 2.6.1-0ubuntu3 Architecture: amd64 Date: Fri Oct 26 09:50:08 2012 ErrorMessage: no package named `libmp3lame0' is installed, cannot configure InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) SourcePackage: lame Title: package libmp3lame0 3.99.5+repack1-3 failed to install/upgrade: no package named `libmp3lame0' is installed, cannot configure UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lame/+bug/1071611/+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 1078083] Re: package libmp3lame0 3.99.5+repack1-3 failed to install/upgrade: pakiet "libmp3lame0" nie jest zainstalowany, nie można go skonfigurować
*** This bug is a duplicate of bug 1071611 *** https://bugs.launchpad.net/bugs/1071611 ** This bug has been marked a duplicate of bug 1071611 package libmp3lame0 3.99.5+repack1-3 failed to install/upgrade: no package named `libmp3lame0' is installed, cannot configure -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lame in Ubuntu. https://bugs.launchpad.net/bugs/1078083 Title: package libmp3lame0 3.99.5+repack1-3 failed to install/upgrade: pakiet "libmp3lame0" nie jest zainstalowany, nie można go skonfigurować Status in lame package in Ubuntu: New Bug description: Error ocured after I tried: sudo apt-get install ubuntu-restricted- extras ProblemType: Package DistroRelease: Ubuntu 12.10 Package: libmp3lame0 3.99.5+repack1-3 ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5 Uname: Linux 3.5.0-17-generic x86_64 ApportVersion: 2.6.1-0ubuntu6 Architecture: amd64 Date: Mon Nov 12 21:23:57 2012 ErrorMessage: pakiet "libmp3lame0" nie jest zainstalowany, nie można go skonfigurować InstallationDate: Installed on 2012-10-30 (13 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) MarkForUpload: True SourcePackage: lame Title: package libmp3lame0 3.99.5+repack1-3 failed to install/upgrade: pakiet "libmp3lame0" nie jest zainstalowany, nie można go skonfigurować UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lame/+bug/1078083/+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 1649604] Re: package libmp3lame0:amd64 3.99.5+repack1-9build1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting
Thank you for taking the time to report this bug and helping to make Ubuntu better. Have you tried to reinstall the library? sudo apt-get install --reinstall libmp3lame0 ** Changed in: lame (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lame in Ubuntu. https://bugs.launchpad.net/bugs/1649604 Title: package libmp3lame0:amd64 3.99.5+repack1-9build1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in lame package in Ubuntu: Incomplete Bug description: audio package error ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libmp3lame0:amd64 3.99.5+repack1-9build1 ProcVersionSignature: Ubuntu 4.4.0-53.74-generic 4.4.30 Uname: Linux 4.4.0-53-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.2 Architecture: amd64 Date: Tue Dec 13 20:14:44 2016 Dependencies: gcc-6-base 6.0.1-0ubuntu1 libc6 2.23-0ubuntu5 libgcc1 1:6.0.1-0ubuntu1 DuplicateSignature: package:libmp3lame0:amd64:3.99.5+repack1-9build1 Processing triggers for desktop-file-utils (0.22-1ubuntu5) ... dpkg: error processing package libmp3lame0:amd64 (--configure): package is in a very bad inconsistent state; you should ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2016-12-03 (10 days ago) InstallationMedia: Ubuntu-GNOME 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160720) RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.15 SourcePackage: lame Title: package libmp3lame0:amd64 3.99.5+repack1-9build1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lame/+bug/1649604/+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 1983199] Re: Unable to connect to Ubuntu running RDP based remote desktop
https://serverfault.com/questions/982679/rdp-session-is-closed-when- loggin-in-locally pointed me here. There seems to be some problem with the username/password handling when trying to run an rdp session out of the box. I am using a brand new Ubuntu 22.04 and different rdp clients (Microsoft Desktop Mobile, Free RDP, Mocha RDP) all fail to connect. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-remote-desktop in Ubuntu. https://bugs.launchpad.net/bugs/1983199 Title: Unable to connect to Ubuntu running RDP based remote desktop Status in gnome-remote-desktop package in Ubuntu: Incomplete Bug description: Initial setup: machine was headless, set up TLS using openssl, set key location using grdctl. Windows RDP client was unable to connect - journalctl showed that the username was unable to be retreived (from dbus?). Set password using grdctl / https://gitlab.gnome.org/-/snippets/1778#note_1515700 Plugged a monitor and keyboard in, checked Settings and the password was garbage. Reset the password, re-enabled RDP and the Windows client was still unable to connect: ``` Jul 31 17:34:06 optiplex gnome-remote-de[2585]: RDP server started Jul 31 17:35:08 optiplex gnome-remote-desktop-daemon[2585]: [17:35:08:914] [2585:2622] [ERROR][com.freerdp.core.transport] - BIO_read returned a system error 0: Success Jul 31 17:35:08 optiplex gnome-remote-desktop-daemon[2585]: [17:35:08:914] [2585:2622] [ERROR][com.freerdp.core] - transport_read_layer:freerdp_set_last_error_ex ERRCONNECT_CONNECT_TRANSPORT_FAILED [0x0002000D] Jul 31 17:35:08 optiplex gnome-remote-de[2585]: Unable to check file descriptor, closing connection Jul 31 17:35:13 optiplex gnome-remote-desktop-daemon[2585]: [17:35:13:572] [2585:2612] [WARN][com.winpr.negotiate] - AcceptSecurityContext status SEC_I_CONTINUE_NEEDED [0x00090312] Jul 31 17:35:13 optiplex gnome-remote-desktop-daemon[2585]: [17:35:13:573] [2585:2612] [WARN][com.winpr.negotiate] - AcceptSecurityContext status SEC_I_COMPLETE_NEEDED [0x00090313] Jul 31 17:35:13 optiplex gnome-remote-desktop-daemon[2585]: [17:35:13:574] [2585:2612] [ERROR][com.freerdp.core.transport] - BIO_read returned a system error 104: Connection reset by peer Jul 31 17:35:13 optiplex gnome-remote-desktop-daemon[2585]: [17:35:13:574] [2585:2612] [ERROR][com.freerdp.core] - transport_read_layer:freerdp_set_last_error_ex ERRCONNECT_CONNECT_TRANSPORT_FAILED [0x0002000D] Jul 31 17:35:13 optiplex gnome-remote-desktop-daemon[2585]: [17:35:13:574] [2585:2612] [ERROR][com.freerdp.core.nla] - [nla_recv] error: -1 Jul 31 17:35:13 optiplex gnome-remote-desktop-daemon[2585]: [17:35:13:574] [2585:2612] [ERROR][com.freerdp.core.transport] - client authentication failure Jul 31 17:35:13 optiplex gnome-remote-desktop-daemon[2585]: [17:35:13:574] [2585:2612] [ERROR][com.freerdp.core.peer] - peer_recv_callback: CONNECTION_STATE_INITIAL - rdp_server_accept_nego() fail Jul 31 17:35:13 optiplex gnome-remote-desktop-daemon[2585]: [17:35:13:574] [2585:2612] [ERROR][com.freerdp.core.transport] - transport_check_fds: transport->ReceiveCallback() - -1 Jul 31 17:35:13 optiplex gnome-remote-desktop-daemon[2585]: [17:35:13:574] [2585:2585] [ERROR][com.freerdp.core.transport] - BIO_should_retry returned a system error 32: Broken pipe Jul 31 17:35:13 optiplex gnome-remote-de[2585]: Unable to check file descriptor, closing connection Jul 31 17:35:14 optiplex gnome-remote-desktop-daemon[2585]: [17:35:14:568] [2585:2642] [ERROR][com.freerdp.core.transport] - BIO_read returned a system error 0: Success Jul 31 17:35:14 optiplex gnome-remote-desktop-daemon[2585]: [17:35:14:568] [2585:2642] [ERROR][com.freerdp.core] - transport_read_layer:freerdp_set_last_error_ex ERRCONNECT_CONNECT_TRANSPORT_FAILED [0x0002000D] Jul 31 17:35:14 optiplex gnome-remote-de[2585]: Unable to check file descriptor, closing connection Jul 31 17:35:14 optiplex gnome-remote-desktop-daemon[2585]: [17:35:14:569] [2585:2632] [ERROR][com.freerdp.crypto] - invalid private key Jul 31 17:35:14 optiplex gnome-remote-desktop-daemon[2585]: [17:35:14:569] [2585:2632] [ERROR][com.freerdp.core.peer] - peer_recv_callback: CONNECTION_STATE_INITIAL - rdp_server_accept_nego() fail Jul 31 17:35:14 optiplex gnome-remote-desktop-daemon[2585]: [17:35:14:569] [2585:2632] [ERROR][com.freerdp.core.transport] - transport_check_fds: transport->ReceiveCallback() - -1 Jul 31 17:35:14 optiplex gnome-remote-de[2585]: Unable to check file descriptor, closing connection Jul 31 17:35:14 optiplex gnome-remote-desktop-daemon[2585]: [17:35:14:575] [2585:2652] [WARN][com.freerdp.core.connection] - server supports only NLA Security Jul 31 17:35:14 optiplex gnome-remote-desktop-daemon[2585]: [17:35:14:575] [2585:2652] [ERROR][com.freerdp.core.connection] - Protocol security negotiation failure Jul 31 17:35:14 optiplex gnome-remote-desktop-daemon[2
[Desktop-packages] [Bug 1990456] Re: xorg reports bogus 1600x1024 resolution
Before installing xorg-server 2:21.1.3-2ubuntu2.2, xrandr gives 1600x1024 resolution which was not able to use on the test unit. After upgrading to xorg-server 2:21.1.3-2ubuntu2.2 from jammy-proposed, that resolution is removed from xrandr. ubuntu@ubuntu:~$ DISPLAY=:0 xrandr Screen 0: minimum 320 x 200, current 1920 x 1200, maximum 16384 x 16384 eDP-1 connected primary 1920x1200+0+0 (normal left inverted right x axis y axis) 344mm x 215mm 1920x1200 60.03*+ 59.8859.95 1920x1080 60.0159.9759.9659.93 1600x1200 60.00 1680x1050 59.9559.88 1400x1050 59.98 1600x900 59.9959.9459.9559.82 1280x1024 60.02 1400x900 59.9659.88 1280x960 60.00 1440x810 60.0059.97 1368x768 59.8859.85 1280x800 59.9959.9759.8159.91 1280x720 60.0059.9959.8659.74 1024x768 60.0460.00 960x720 60.00 928x696 60.05 896x672 60.01 1024x576 59.9559.9659.9059.82 960x600 59.9360.00 960x540 59.9659.9959.6359.82 800x600 60.0060.3256.25 840x525 60.0159.88 864x486 59.9259.57 700x525 59.98 800x450 59.9559.82 640x512 60.02 700x450 59.9659.88 640x480 60.0059.94 720x405 59.5158.99 684x384 59.8859.85 640x400 59.8859.98 640x360 59.8659.8359.8459.32 512x384 60.00 512x288 60.0059.92 480x270 59.6359.82 400x300 60.3256.34 432x243 59.9259.57 320x240 60.05 360x202 59.5159.13 320x180 59.8459.32 HDMI-1 disconnected (normal left inverted right x axis y axis) DP-1 disconnected (normal left inverted right x axis y axis) DP-2 disconnected (normal left inverted right x axis y axis) ** Tags removed: verification-needed verification-needed-jammy ** Tags added: verification-done verification-done-jammy -- 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/1990456 Title: xorg reports bogus 1600x1024 resolution Status in OEM Priority Project: New Status in xorg-server package in Ubuntu: Fix Released Status in xorg-server source package in Jammy: Fix Committed Bug description: xorg reports 1600x1024 bogus resolution [ Impact ] * User of NVIDIA GPU is able to switch to 1600x1024 resolution but cannot display anything under the resolution [ Fix ] Drop 001_fedora_extramodes.patch which was dropped from Fedora since xserver 1.5.0. [ Test Plan ] 1. Find a test unit with NVIDIA GPU, or anything but use Xorg mode to enter the desktop 2. Type `xrandr` in terminal Expected: The resolution 1600x1024 should not appear if the display does not support it. Actual: The resolution 1600x1024 appears. [ Where problems could occur ] * Lack of extra modes that the display might actually support. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1990456/+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