[Desktop-packages] [Bug 1967283] [NEW] Icon that doesn't exist is requested when no Wi-Fi is connected and Wireguard is enabled
Public bug reported: When there is a Wireguard connection enabled and Wi-Fi is disconnected, an icon that does not exist is being requested. On the attached screenshot, nm-applet can be seen in two places: on top it is the Tray Icon, it shows as an invalid icon. On the bottom it is the AppIndicator, it is the empty space on the left of the Bluetooth icon. Even with this icon issues, I'm still able to interact with the nm- applet. I tried changing the theme to both GNOME and Adwaita (the screenshot shows Elementary Xfce Darker), and the bug still persists setting either icon theme. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: network-manager-gnome 1.24.0-1ubuntu3 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: XFCE Date: Thu Mar 31 08:45:21 2022 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2017-06-13 (1751 days ago) InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) IpRoute: default via 192.168.35.110 dev wlp2s0 proto dhcp metric 600 10.72.201.0/24 dev lxdbr0 proto kernel scope link src 10.72.201.1 linkdown 169.254.0.0/16 dev wlp2s0 scope link metric 1000 172.16.0.0/24 dev wg0 scope link 192.168.35.0/24 dev wlp2s0 proto kernel scope link src 192.168.35.153 metric 600 NetworkManager.conf: [main] plugins=ifupdown,keyfile [ifupdown] managed=false SourcePackage: network-manager-applet UpgradeStatus: Upgraded to jammy on 2019-12-22 (829 days ago) modified.conffile..etc.cron.daily.apport: [deleted] nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.36.4 connected started full enabled enabled enabled enabled enabled ** Affects: network-manager-applet (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy third-party-packages ** Attachment added: "Screenshot showing the problem on xfce4-panel (it's both the error icon and the empty space on bottom)" https://bugs.launchpad.net/bugs/1967283/+attachment/5575199/+files/Captura%20de%20tela_2022-03-31_08-35-34.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-applet in Ubuntu. https://bugs.launchpad.net/bugs/1967283 Title: Icon that doesn't exist is requested when no Wi-Fi is connected and Wireguard is enabled Status in network-manager-applet package in Ubuntu: New Bug description: When there is a Wireguard connection enabled and Wi-Fi is disconnected, an icon that does not exist is being requested. On the attached screenshot, nm-applet can be seen in two places: on top it is the Tray Icon, it shows as an invalid icon. On the bottom it is the AppIndicator, it is the empty space on the left of the Bluetooth icon. Even with this icon issues, I'm still able to interact with the nm- applet. I tried changing the theme to both GNOME and Adwaita (the screenshot shows Elementary Xfce Darker), and the bug still persists setting either icon theme. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: network-manager-gnome 1.24.0-1ubuntu3 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: XFCE Date: Thu Mar 31 08:45:21 2022 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2017-06-13 (1751 days ago) InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) IpRoute: default via 192.168.35.110 dev wlp2s0 proto dhcp metric 600 10.72.201.0/24 dev lxdbr0 proto kernel scope link src 10.72.201.1 linkdown 169.254.0.0/16 dev wlp2s0 scope link metric 1000 172.16.0.0/24 dev wg0 scope link 192.168.35.0/24 dev wlp2s0 proto kernel scope link src 192.168.35.153 metric 600 NetworkManager.conf: [main] plugins=ifupdown,keyfile [ifupdown] managed=false SourcePackage: network-manager-applet UpgradeStatus: Upgraded to jammy on 2019-12-22 (829 days ago) modified.conffile..etc.cron.daily.apport: [deleted] nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.36.4 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1967283/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@
[Desktop-packages] [Bug 1962403] Re: Gamepads are no longer detected
I added the plug to Firefox using the command. Once the command finished, it crashed. When Firefox restarted, the theme was messed up and it was using the wrong cursor theme, reminiscent from the early days of snapd. After sending the crash report to Mozilla, closing that messed up Firefox and opening it again, it worked normally and the gamepads were detected. Is there a reason the joystick plug isn't enabled by default? I believe it would be better for the users to have it enabled by default, as they could believe gamepads don't work on Firefox. Especially if the snap becomes the default for Jammy. Also, the kernel bug on the Redragon Seymur 2 is back! 😭️ Even using usbhid.quirks=0x0079:0x0006:0x10 there is an extra analog axis which messes controls, making it nearly unusable. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1962403 Title: Gamepads are no longer detected Status in firefox package in Ubuntu: Incomplete Bug description: After the upgrade from Firefox deb to Firefox snap, my gamepad is no longer being detected. One gamepad is a Feitun FM0013, a gamepad with at least 5 operation modes I've found so far: Nintendo Switch Pro Controller, X-Box wired controller, PS3 wired controller, PS3 wireless controller and generic Bluetooth controller. From these 5 operation modes, X-Box wired controller, PS3 wired controller and generic Bluetooth controller work on my computer, while Nintendo Switch Pro Controller mode is found but doesn't detect any buttons while using PS3 wireless controller mode isn't found. When using on my notebook and smartphone, I normally use this gamepad in generic Bluetooth controller mode, as I want to use it wirelessly more often. I have noticed that any of the modes that worked with Firefox deb (X-Box wired controller, PS3 wired controller and generic Bluetooth controller) stopped working with the snap. Steps to reproduce: 1) Have Firefox installed as a snap; 2) Connect gamepad with one of its compatible modes; 3) Access page/game to test the gamepad (https://hacks.mozilla.org/2013/12/the-gamepad-api/ or https://luser.github.io/gamepadtest/ or http://www.cross-code.com/en/start for example); 4) Notice how the gamepad isn't detected. I have a Redragon Seymur 2 too, and it also isn't detected. Using the Firefox from the Mozilla page, the gamepads are found and appear as follow in the luser's page: gamepad: 0079-0006-DragonRise Inc. Generic USB Joystick gamepad: 045e-028e-Microsoft X-Box 360 pad The X-Box 360 one is the Feitun. Using Bluetooth, the Feitun appear as: gamepad: 1949-0402-Gamepad So, unfortunately, Firefox snap is unusable to play games while using gamepads. For example, I can play CrossCode on the Chromium snap, but am unable to play it on Firefox snap. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: firefox 1:1snap1-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19 Uname: Linux 5.15.0-22-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: XFCE Date: Sun Feb 27 11:25:06 2022 InstallationDate: Installed on 2017-06-13 (1719 days ago) InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) Snap.Changes: não foram encontradas alterações SourcePackage: firefox UpgradeStatus: Upgraded to jammy on 2019-12-22 (797 days ago) modified.conffile..etc.cron.daily.apport: [deleted] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1962403/+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 1962403] [NEW] Gamepads are no longer detected
Public bug reported: After the upgrade from Firefox deb to Firefox snap, my gamepad is no longer being detected. One gamepad is a Feitun FM0013, a gamepad with at least 5 operation modes I've found so far: Nintendo Switch Pro Controller, X-Box wired controller, PS3 wired controller, PS3 wireless controller and generic Bluetooth controller. From these 5 operation modes, X-Box wired controller, PS3 wired controller and generic Bluetooth controller work on my computer, while Nintendo Switch Pro Controller mode is found but doesn't detect any buttons while using PS3 wireless controller mode isn't found. When using on my notebook and smartphone, I normally use this gamepad in generic Bluetooth controller mode, as I want to use it wirelessly more often. I have noticed that any of the modes that worked with Firefox deb (X-Box wired controller, PS3 wired controller and generic Bluetooth controller) stopped working with the snap. Steps to reproduce: 1) Have Firefox installed as a snap; 2) Connect gamepad with one of its compatible modes; 3) Access page/game to test the gamepad (https://hacks.mozilla.org/2013/12/the-gamepad-api/ or https://luser.github.io/gamepadtest/ or http://www.cross-code.com/en/start for example); 4) Notice how the gamepad isn't detected. I have a Redragon Seymur 2 too, and it also isn't detected. Using the Firefox from the Mozilla page, the gamepads are found and appear as follow in the luser's page: gamepad: 0079-0006-DragonRise Inc. Generic USB Joystick gamepad: 045e-028e-Microsoft X-Box 360 pad The X-Box 360 one is the Feitun. Using Bluetooth, the Feitun appear as: gamepad: 1949-0402-Gamepad So, unfortunately, Firefox snap is unusable to play games while using gamepads. For example, I can play CrossCode on the Chromium snap, but am unable to play it on Firefox snap. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: firefox 1:1snap1-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19 Uname: Linux 5.15.0-22-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: XFCE Date: Sun Feb 27 11:25:06 2022 InstallationDate: Installed on 2017-06-13 (1719 days ago) InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) Snap.Changes: não foram encontradas alterações SourcePackage: firefox UpgradeStatus: Upgraded to jammy on 2019-12-22 (797 days ago) modified.conffile..etc.cron.daily.apport: [deleted] ** Affects: firefox (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy package-from-proposed third-party-packages -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1962403 Title: Gamepads are no longer detected Status in firefox package in Ubuntu: New Bug description: After the upgrade from Firefox deb to Firefox snap, my gamepad is no longer being detected. One gamepad is a Feitun FM0013, a gamepad with at least 5 operation modes I've found so far: Nintendo Switch Pro Controller, X-Box wired controller, PS3 wired controller, PS3 wireless controller and generic Bluetooth controller. From these 5 operation modes, X-Box wired controller, PS3 wired controller and generic Bluetooth controller work on my computer, while Nintendo Switch Pro Controller mode is found but doesn't detect any buttons while using PS3 wireless controller mode isn't found. When using on my notebook and smartphone, I normally use this gamepad in generic Bluetooth controller mode, as I want to use it wirelessly more often. I have noticed that any of the modes that worked with Firefox deb (X-Box wired controller, PS3 wired controller and generic Bluetooth controller) stopped working with the snap. Steps to reproduce: 1) Have Firefox installed as a snap; 2) Connect gamepad with one of its compatible modes; 3) Access page/game to test the gamepad (https://hacks.mozilla.org/2013/12/the-gamepad-api/ or https://luser.github.io/gamepadtest/ or http://www.cross-code.com/en/start for example); 4) Notice how the gamepad isn't detected. I have a Redragon Seymur 2 too, and it also isn't detected. Using the Firefox from the Mozilla page, the gamepads are found and appear as follow in the luser's page: gamepad: 0079-0006-DragonRise Inc. Generic USB Joystick gamepad: 045e-028e-Microsoft X-Box 360 pad The X-Box 360 one is the Feitun. Using Bluetooth, the Feitun appear as: gamepad: 1949-0402-Gamepad So, unfortunately, Firefox snap is unusable to play games while using gamepads. For example, I can play CrossCode on the Chromium snap, but am unable to play it on Firefox snap. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: firefox 1:1snap1-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19 Uname: Linux 5.15.0-22-generic x86_64 N
[Desktop-packages] [Bug 1953376] Re: Severe graphical glitches when restoring the window
Recently, I have no longer observed this problem, and after Firefox updated from deb to snap, it hasn't reappeared, so it seems fixed to me now. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1953376 Title: Severe graphical glitches when restoring the window Status in firefox package in Ubuntu: Incomplete Bug description: When restoring the Firefox window, sometimes graphical glitches occur before the window content appears properly. Sometimes it is just a tiny bit of the previous content on the Firefox window that was rendered correctly, sometimes it's a severely corrupted screen. The attached screenshot shows the second case. Steps to reproduce: 1) Have a Firefox window open; 2) Minimize all Firefox windows; 3) Try to restore and minimize one window repeatedly; 4) Notice graphical corruption. I still haven't figured out what is causing this issue, but sometimes it will stop happening, and later it starts again. It seems to be retaining some content that was open before. I'm reporting this against Firefox because it is the only program where I have noticed this particular problem, but this may a problem with something else (it could be xfwm4, for example). While the attached files have more details, here are some system specifications. OS: Xubuntu 22.04; CPU: Intel Core i3-6100U; GPU: Intel HD Graphics 520; Mesa: 21.2.6; Xorg: intel 2.99.917; RAM: 20 GB. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: firefox 95.0+build1-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-13.13-generic 5.15.5 Uname: Linux 5.15.0-13-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu74 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: usuario2024 F pipewire usuario2025 F wireplumber /dev/snd/pcmC0D0p: usuario2024 F...m pipewire /dev/snd/seq:usuario2024 F pipewire BuildID: 20211129150630 CasperMD5CheckResult: unknown Channel: Unavailable CurrentDesktop: XFCE Date: Mon Dec 6 13:44:43 2021 DefaultProfileExtensions: extensions.sqlite corrupt or missing DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) DefaultProfileLocales: extensions.sqlite corrupt or missing DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:363 DefaultProfilePrefSources: prefs.js DefaultProfileThemes: extensions.sqlite corrupt or missing ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2017-06-13 (1636 days ago) InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) IpRoute: default via 192.168.0.1 dev wlp2s0 proto dhcp metric 600 169.254.0.0/16 dev wg0 scope link metric 1000 172.16.0.0/24 dev wg0 proto kernel scope link src 172.16.0.5 192.168.0.0/24 dev wlp2s0 proto kernel scope link src 192.168.0.50 metric 600 MostRecentCrashID: bp-503ae7fd-820e-46e7-b595-808330180209 Profile1Extensions: extensions.sqlite corrupt or missing Profile1IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) Profile1Locales: extensions.sqlite corrupt or missing Profile1PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:363 Profile1PrefSources: prefs.js Profile1Themes: extensions.sqlite corrupt or missing Profiles: Profile1 - LastVersion=76.0a1/20200312215313 (Out of date) Profile0 (Default) - LastVersion=95.0/20211129150630 (In use) PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RunningIncompatibleAddons: False SourcePackage: firefox SubmittedCrashIDs: bp-503ae7fd-820e-46e7-b595-808330180209 UpgradeStatus: Upgraded to jammy on 2019-12-22 (714 days ago) dmi.bios.date: 08/09/2018 dmi.bios.release: 1.45 dmi.bios.vendor: LENOVO dmi.bios.version: 0XCN45WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: Toronto 4A2 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40679 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 310-14ISK dmi.ec.firmware.release: 1.45 dmi.modalias: dmi:bvnLENOVO:bvr0XCN45WW:bd08/09/2018:br1.45:efr1.45:svnLENOVO:pn80UG:pvrLenovoideapad310-14ISK:rvnLENOVO:rnToronto4A2:rvrSDK0J40679WIN:cvnLENOVO:ct10:cvrLenovoideapad310-14ISK:skuLENOVO_MT_80UG_BU_idea_FM_Lenovoideapad310-14ISK: dmi.product.family: IDEAPAD dmi.product.name: 80UG dmi.product.sku: LENOVO_MT_80UG_BU_idea_FM_Lenovo ideapad 310-14ISK dmi.product.ve
[Desktop-packages] [Bug 1955745] Re: Sending file to GCP using SSH window from Google Cloud Platform freezes and corrupts both local and remote systems
I did this test twice now, using Chromium 98.0.4758.102 snap, firstly with a VM and then with the host system. Gladly, everything worked correctly: no system crash on the host and the file was uploaded successfully to the GCP instance (sha256 matched). -- 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/1955745 Title: Sending file to GCP using SSH window from Google Cloud Platform freezes and corrupts both local and remote systems Status in chromium-browser package in Ubuntu: Incomplete Bug description: I started setting a Factorio server on Google Cloud Platform. I opened a SSH session using the button on the Google Cloud Platform page, the page opened, the session started and then I chose the save file to upload (choosing the gear on top right and then upload file). It's a 64 MB save. After 2% upload, the local system freezes entirely. Nothing responds, even REISUB don't work any more. After forcefully shutting down the local computer, on the next boot, the local computer's root file system is corrupted. On the remote machine, the file was partially send but it was also corrupted. ProblemType: Bug DistroRelease: Ubuntu 22.04 ProcVersionSignature: Ubuntu 5.15.0-13.13-generic 5.15.5 Uname: Linux 5.15.0-13-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu74 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: XFCE Date: Sat Dec 25 17:41:41 2021 InstallationDate: Installed on 2017-06-13 (1655 days ago) InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) Snap: chromium 96.0.4664.110 (latest/candidate) SnapSource: ubuntu/+source/chromium-browser UpgradeStatus: Upgraded to jammy on 2019-12-22 (733 days ago) modified.conffile..etc.cron.daily.apport: [deleted] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1955745/+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 1958074] [NEW] NTFS created by gnome-disk-utility does not work on Windows
Public bug reported: NTFS partitions created using gnome-disk-utility don't work on Windows. Steps to reproduce: 1) Open gnome-disk-utility; 2) Choose to create a NTFS partition; 3) Insert the media with the NTFS partition on Windows; 4) Notice how it will hang forever and never load the data. I suspect this is happening because it's using the ntfs kernel driver instead of ntfs-3g. One noticeable difference when creating the partition using Linux is that there are some messages on dmesg: [ 2845.877068] ntfs3: Max link count 4000 [ 2845.877073] ntfs3: Enabled Linux POSIX ACLs support [ 2845.877074] ntfs3: Read-only LZX/Xpress compression included I believe the best would be that the default NTFS partitions create on GNOME Disks are compatible with Windows. At least the interface still claims it would be compatible with Windows, even when it isn't. Tested Xubuntu 22.04 Daily and with Windows 10. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-disk-utility 41.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-16.16-generic 5.15.12 Uname: Linux 5.15.0-16-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu75 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: XFCE Date: Sun Jan 16 11:18:33 2022 InstallationDate: Installed on 2017-06-13 (1677 days ago) InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: gnome-disk-utility UpgradeStatus: Upgraded to jammy on 2019-12-22 (755 days ago) modified.conffile..etc.cron.daily.apport: [deleted] ** Affects: gnome-disk-utility (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-disk-utility in Ubuntu. https://bugs.launchpad.net/bugs/1958074 Title: NTFS created by gnome-disk-utility does not work on Windows Status in gnome-disk-utility package in Ubuntu: New Bug description: NTFS partitions created using gnome-disk-utility don't work on Windows. Steps to reproduce: 1) Open gnome-disk-utility; 2) Choose to create a NTFS partition; 3) Insert the media with the NTFS partition on Windows; 4) Notice how it will hang forever and never load the data. I suspect this is happening because it's using the ntfs kernel driver instead of ntfs-3g. One noticeable difference when creating the partition using Linux is that there are some messages on dmesg: [ 2845.877068] ntfs3: Max link count 4000 [ 2845.877073] ntfs3: Enabled Linux POSIX ACLs support [ 2845.877074] ntfs3: Read-only LZX/Xpress compression included I believe the best would be that the default NTFS partitions create on GNOME Disks are compatible with Windows. At least the interface still claims it would be compatible with Windows, even when it isn't. Tested Xubuntu 22.04 Daily and with Windows 10. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-disk-utility 41.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-16.16-generic 5.15.12 Uname: Linux 5.15.0-16-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu75 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: XFCE Date: Sun Jan 16 11:18:33 2022 InstallationDate: Installed on 2017-06-13 (1677 days ago) InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: gnome-disk-utility UpgradeStatus: Upgraded to jammy on 2019-12-22 (755 days ago) modified.conffile..etc.cron.daily.apport: [deleted] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-disk-utility/+bug/1958074/+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 1955745] [NEW] Sending file to GCP using SSH window from Google Cloud Platform freezes and corrupts both local and remote systems
Public bug reported: I started setting a Factorio server on Google Cloud Platform. I opened a SSH session using the button on the Google Cloud Platform page, the page opened, the session started and then I chose the save file to upload (choosing the gear on top right and then upload file). It's a 64 MB save. After 2% upload, the local system freezes entirely. Nothing responds, even REISUB don't work any more. After forcefully shutting down the local computer, on the next boot, the local computer's root file system is corrupted. On the remote machine, the file was partially send but it was also corrupted. ProblemType: Bug DistroRelease: Ubuntu 22.04 ProcVersionSignature: Ubuntu 5.15.0-13.13-generic 5.15.5 Uname: Linux 5.15.0-13-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu74 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: XFCE Date: Sat Dec 25 17:41:41 2021 InstallationDate: Installed on 2017-06-13 (1655 days ago) InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) Snap: chromium 96.0.4664.110 (latest/candidate) SnapSource: ubuntu/+source/chromium-browser UpgradeStatus: Upgraded to jammy on 2019-12-22 (733 days ago) modified.conffile..etc.cron.daily.apport: [deleted] ** Affects: chromium-browser (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy snap -- 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/1955745 Title: Sending file to GCP using SSH window from Google Cloud Platform freezes and corrupts both local and remote systems Status in chromium-browser package in Ubuntu: New Bug description: I started setting a Factorio server on Google Cloud Platform. I opened a SSH session using the button on the Google Cloud Platform page, the page opened, the session started and then I chose the save file to upload (choosing the gear on top right and then upload file). It's a 64 MB save. After 2% upload, the local system freezes entirely. Nothing responds, even REISUB don't work any more. After forcefully shutting down the local computer, on the next boot, the local computer's root file system is corrupted. On the remote machine, the file was partially send but it was also corrupted. ProblemType: Bug DistroRelease: Ubuntu 22.04 ProcVersionSignature: Ubuntu 5.15.0-13.13-generic 5.15.5 Uname: Linux 5.15.0-13-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu74 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: XFCE Date: Sat Dec 25 17:41:41 2021 InstallationDate: Installed on 2017-06-13 (1655 days ago) InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) Snap: chromium 96.0.4664.110 (latest/candidate) SnapSource: ubuntu/+source/chromium-browser UpgradeStatus: Upgraded to jammy on 2019-12-22 (733 days ago) modified.conffile..etc.cron.daily.apport: [deleted] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1955745/+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 1953389] [NEW] Remmina segfault when trying to connect using RDP
Public bug reported: After the SSL rebuild, Remmina is crashing with a segmentation fault when trying to connect to a Windows Server 2019 machine using RDP. I tried removing the sensitive data from this backtrace (#7 has TERMSRV/XXX.XXX.XXX.XXX), hopefully everything sensitive was removed. The full backtrace is: (gdb) bt f #0 0x76d192e8 in EVP_CIPHER_CTX_set_key_length (c=c@entry=0x7fffe03310e0, keylen=keylen@entry=16) at ../crypto/evp/evp_enc.c:979 __func__ = "EVP_CIPHER_CTX_set_key_length" #1 0x71b2c4a8 in winpr_RC4_New_Internal (key=0x7fffe0373998 "\223\234\376O`\245$\225\223\343\303\370\020\256\225\374\032N\317P\345\207K\320KX\231\307fb\314\307\032N\317P\345\207K\320KX\231\307fb\314", , keylen=16, override_fips=0) at ./winpr/libwinpr/crypto/cipher.c:75 ctx = 0x7fffe03310e0 evp = 0x76f7b240 #2 0x71b59ddd in ntlm_rc4k (length=16, ciphertext=0x7fffe03739c8 "", plaintext=0x7fffe03739a8 "\032N\317P\345\207K\320KX\231\307fb\314\307\032N\317P\345\207K\320KX\231\307fb\314", , key=0x7fffe0373998 "\223\234\376O`\245$\225\223\343\303\370\020\256\225\374\032N\317P\345\207K\320KX\231\307fb\314\307\032N\317P\345\207K\320KX\231\307fb\314", ) at ./winpr/libwinpr/sspi/NTLM/ntlm_compute.c:491 rc4 = status = -2146893052 s = 0x7fffe03723b0 length = StartOffset = PayloadOffset = AvTimestamp = message = 0x7fffe0373780 context = 0x7fffe0373600 credentials = input_buffer = output_buffer = 0x0 channel_bindings = #3 ntlm_encrypt_random_session_key (context=0x7fffe0373600) at ./winpr/libwinpr/sspi/NTLM/ntlm_compute.c:566 status = -2146893052 s = 0x7fffe03723b0 length = StartOffset = PayloadOffset = AvTimestamp = message = 0x7fffe0373780 context = 0x7fffe0373600 credentials = input_buffer = output_buffer = 0x0 channel_bindings = #4 ntlm_read_ChallengeMessage (buffer=, context=0x7fffe0373600) at ./winpr/libwinpr/sspi/NTLM/ntlm_message.c:513 status = -2146893052 s = 0x7fffe03723b0 length = StartOffset = PayloadOffset = AvTimestamp = message = 0x7fffe0373780 context = 0x7fffe0373600 credentials = input_buffer = output_buffer = 0x0 channel_bindings = #5 ntlm_InitializeSecurityContextW (phCredential=phCredential@entry=0x7fffe0372e70, phContext=phContext@entry=0x7fffe0374230, pszTargetName=, fContextReq=fContextReq@entry=50, Reserved1=Reserved1@entry=0, TargetDataRep=TargetDataRep--Type for more, q to quit, c to continue without paging--c @entry=16, pInput=, Reserved2=, phNewContext=, pOutput=, pfContextAttr=, ptsExpiry=) at ./winpr/libwinpr/sspi/NTLM/ntlm.c:590 context = 0x7fffe0373600 credentials = input_buffer = output_buffer = 0x0 channel_bindings = #6 0x71b5ac25 in ntlm_InitializeSecurityContextA (phCredential=0x7fffe0372e70, phContext=0x7fffe0374230, pszTargetName=, fContextReq=50, Reserved1=0, TargetDataRep=16, pInput=0x7fffe0372eb0, Reserved2=0, phNewContext=0x7fffe0374230, pOutput=0x7fffe0372ec0, pfContextAttr=0x7fffe0372e58, ptsExpiry=0x7fffe0372e80) at ./winpr/libwinpr/sspi/NTLM/ntlm.c:633 status = pszTargetNameW = 0x7fffe0373cc0 #7 0x71b6543f in winpr_InitializeSecurityContextA (phCredential=0x7fffe0372e70, phContext=0x7fffe0372e08, pszTargetName=0x7fffe0385fd0 "TERMSRV/XXX.XXX.XXX.XXX", fContextReq=50, Reserved1=0, TargetDataRep=16, pInput=0x7fffe0372eb0, Reserved2=0, phNewContext=0x7fffe0372e08, pOutput=0x7fffe0372ec0, pfContextAttr=0x7fffe0372e58, ptsExpiry=0x7fffe0372e80) at ./winpr/libwinpr/sspi/sspi_winpr.c:1284 Name = 0x71b9e684 "Negotiate" status = table = 0x71bd72c0 _log_cached_ptr = 0x0 __FUNCTION__ = "winpr_InitializeSecurityContextA" _log_cached_ptr = 0x0 #8 0x71d0301c in nla_client_recv (nla=0x7fffe0372df0) at ./libfreerdp/core/nla.c:557 status = -1 _log_cached_ptr = 0x0 __FUNCTION__ = "nla_recv_pdu" #9 nla_recv_pdu (nla=0x7fffe0372df0, s=) at ./libfreerdp/core/nla.c:2192 _log_cached_ptr = 0x0 __FUNCTION__ = "nla_recv_pdu" #10 0x71d3be99 in rdp_recv_callback (transport=, s=0x55bad760, extra=0x55e68000) at ./libfreerdp/core/rdp.c:1515 status = 0 rdp = 0x55e68000 _log_cached_ptr = 0x0 __FUNCTION__ = "rdp_recv_callback" _log_cached_ptr = 0x0 _log_cached_ptr = 0x0 _log_cached_ptr = 0x0 _log_cached_ptr = 0x0 _log_cached_ptr = 0x0 _log_cached_ptr = 0x0 _log_cached_ptr = 0x0 _log_cached_ptr = 0x0 _log_cached_ptr = 0x0 _log_cached_ptr = 0x0 _log_cached_ptr = 0x0 _log_cached_p
[Desktop-packages] [Bug 1953376] [NEW] Severe graphical glitches when restoring the window
Public bug reported: When restoring the Firefox window, sometimes graphical glitches occur before the window content appears properly. Sometimes it is just a tiny bit of the previous content on the Firefox window that was rendered correctly, sometimes it's a severely corrupted screen. The attached screenshot shows the second case. Steps to reproduce: 1) Have a Firefox window open; 2) Minimize all Firefox windows; 3) Try to restore and minimize one window repeatedly; 4) Notice graphical corruption. I still haven't figured out what is causing this issue, but sometimes it will stop happening, and later it starts again. It seems to be retaining some content that was open before. I'm reporting this against Firefox because it is the only program where I have noticed this particular problem, but this may a problem with something else (it could be xfwm4, for example). While the attached files have more details, here are some system specifications. OS: Xubuntu 22.04; CPU: Intel Core i3-6100U; GPU: Intel HD Graphics 520; Mesa: 21.2.6; Xorg: intel 2.99.917; RAM: 20 GB. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: firefox 95.0+build1-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-13.13-generic 5.15.5 Uname: Linux 5.15.0-13-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu74 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: usuario2024 F pipewire usuario2025 F wireplumber /dev/snd/pcmC0D0p: usuario2024 F...m pipewire /dev/snd/seq:usuario2024 F pipewire BuildID: 20211129150630 CasperMD5CheckResult: unknown Channel: Unavailable CurrentDesktop: XFCE Date: Mon Dec 6 13:44:43 2021 DefaultProfileExtensions: extensions.sqlite corrupt or missing DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) DefaultProfileLocales: extensions.sqlite corrupt or missing DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:363 DefaultProfilePrefSources: prefs.js DefaultProfileThemes: extensions.sqlite corrupt or missing ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2017-06-13 (1636 days ago) InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) IpRoute: default via 192.168.0.1 dev wlp2s0 proto dhcp metric 600 169.254.0.0/16 dev wg0 scope link metric 1000 172.16.0.0/24 dev wg0 proto kernel scope link src 172.16.0.5 192.168.0.0/24 dev wlp2s0 proto kernel scope link src 192.168.0.50 metric 600 MostRecentCrashID: bp-503ae7fd-820e-46e7-b595-808330180209 Profile1Extensions: extensions.sqlite corrupt or missing Profile1IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) Profile1Locales: extensions.sqlite corrupt or missing Profile1PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:363 Profile1PrefSources: prefs.js Profile1Themes: extensions.sqlite corrupt or missing Profiles: Profile1 - LastVersion=76.0a1/20200312215313 (Out of date) Profile0 (Default) - LastVersion=95.0/20211129150630 (In use) PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RunningIncompatibleAddons: False SourcePackage: firefox SubmittedCrashIDs: bp-503ae7fd-820e-46e7-b595-808330180209 UpgradeStatus: Upgraded to jammy on 2019-12-22 (714 days ago) dmi.bios.date: 08/09/2018 dmi.bios.release: 1.45 dmi.bios.vendor: LENOVO dmi.bios.version: 0XCN45WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: Toronto 4A2 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40679 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 310-14ISK dmi.ec.firmware.release: 1.45 dmi.modalias: dmi:bvnLENOVO:bvr0XCN45WW:bd08/09/2018:br1.45:efr1.45:svnLENOVO:pn80UG:pvrLenovoideapad310-14ISK:rvnLENOVO:rnToronto4A2:rvrSDK0J40679WIN:cvnLENOVO:ct10:cvrLenovoideapad310-14ISK:skuLENOVO_MT_80UG_BU_idea_FM_Lenovoideapad310-14ISK: dmi.product.family: IDEAPAD dmi.product.name: 80UG dmi.product.sku: LENOVO_MT_80UG_BU_idea_FM_Lenovo ideapad 310-14ISK dmi.product.version: Lenovo ideapad 310-14ISK dmi.sys.vendor: LENOVO modified.conffile..etc.cron.daily.apport: [deleted] ** Affects: firefox (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy third-party-packages ** Attachment added: "Screenshot showing the issue" https://bugs.launchpad.net/bugs/1953376/+attachment/5545778/+files/Captura%20de%20tela_2021-12-06_13-43-20.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1953376 Title: Severe graphical glitche
[Desktop-packages] [Bug 1942364] Re: sonixb camera is unusable on Chromium
Here is the output of the commands: $ cat /run/udev/data/b43:0 W:122 I:5238867 E:ID_FS_TYPE= E:SYSTEMD_READY=0 G:systemd Q:systemd V:1 $ cat /run/udev/data/b43:128 W:123 I:5238868 E:ID_FS_TYPE= E:SYSTEMD_READY=0 G:systemd Q:systemd V:1 ** Changed in: chromium-browser (Ubuntu) Status: Incomplete => New -- 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/1942364 Title: sonixb camera is unusable on Chromium Status in chromium-browser package in Ubuntu: New Bug description: I'm trying to use an USB camera on Chromium, however it is not being detected. lsusb shows it as: Bus 001 Device 076: ID 0c45:6001 Microdia Genius VideoCAM NB While this camera isn't the best I've ever seen, it works properly when using ffplay and guvcview. The following is the output of some utilities related to the camera: $ v4l2-ctl --info Driver Info: Driver name : sonixb Card type: USB camera Bus info : usb-:00:14.0-1 Driver version : 5.11.22 Capabilities : 0x8521 Video Capture Read/Write Streaming Extended Pix Format Device Capabilities Device Caps : 0x0521 Video Capture Read/Write Streaming Extended Pix Format $ v4l2-ctl --list-formats-ext ioctl: VIDIOC_ENUM_FMT Type: Video Capture [0]: 'S910' (GSPCA SN9C10X, compressed) Size: Discrete 160x120 Size: Discrete 176x144 Size: Discrete 320x240 Size: Discrete 352x288 [1]: 'BA81' (8-bit Bayer BGBG/GRGR) Size: Discrete 160x120 Size: Discrete 176x144 ProblemType: Bug DistroRelease: Ubuntu 20.04 ProcVersionSignature: Ubuntu 5.11.0-27.29~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Wed Sep 1 15:12:28 2021 InstallationDate: Installed on 2017-06-13 (1540 days ago) InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) Snap: chromium 92.0.4515.159 (latest/candidate) SnapSource: ubuntu/+source/chromium-browser UpgradeStatus: Upgraded to focal on 2019-12-22 (618 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1942364/+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 1942364] Re: sonixb camera is unusable on Chromium
Hi, here is the output of `journalctl -f | grep DEN` I started the command, then connected the USB camera, then opened Chromium. I tried accessing Google Meet and then the WebRTC test page. In neither, the USB camera was available to choose. I tested with another USB camera, and that other camera worked. Here is the lsusb and output of the same commands for this second camera: Bus 001 Device 013: ID 1908:2311 GEMBIRD USB2.0 PC CAMERA $ v4l2-ctl --info -d /dev/video2 Driver Info: Driver name : uvcvideo Card type: USB2.0 PC CAMERA: USB2.0 PC CAM Bus info : usb-:00:14.0-2 Driver version : 5.11.22 Capabilities : 0x84a1 Video Capture Metadata Capture Streaming Extended Pix Format Device Capabilities Device Caps : 0x0421 Video Capture Streaming Extended Pix Format $ v4l2-ctl --list-formats-ext -d /dev/video2 ioctl: VIDIOC_ENUM_FMT Type: Video Capture [0]: 'YUYV' (YUYV 4:2:2) Size: Discrete 640x480 Interval: Discrete 0.033s (30.000 fps) Interval: Discrete 0.067s (15.000 fps) Size: Discrete 352x288 Interval: Discrete 0.033s (30.000 fps) Interval: Discrete 0.067s (15.000 fps) Size: Discrete 320x240 Interval: Discrete 0.033s (30.000 fps) Interval: Discrete 0.067s (15.000 fps) Size: Discrete 176x144 Interval: Discrete 0.033s (30.000 fps) Interval: Discrete 0.067s (15.000 fps) Size: Discrete 160x120 Interval: Discrete 0.033s (30.000 fps) Interval: Discrete 0.067s (15.000 fps) The output of the v4l2-ctl --list-formats-ext seem different. I'm suspecting this could be a colorspace issue ** Attachment added: "journalctl_sonixb_camera.txt" https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1942364/+attachment/5523932/+files/journalctl_sonixb_camera.txt -- 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/1942364 Title: sonixb camera is unusable on Chromium Status in chromium-browser package in Ubuntu: Incomplete Bug description: I'm trying to use an USB camera on Chromium, however it is not being detected. lsusb shows it as: Bus 001 Device 076: ID 0c45:6001 Microdia Genius VideoCAM NB While this camera isn't the best I've ever seen, it works properly when using ffplay and guvcview. The following is the output of some utilities related to the camera: $ v4l2-ctl --info Driver Info: Driver name : sonixb Card type: USB camera Bus info : usb-:00:14.0-1 Driver version : 5.11.22 Capabilities : 0x8521 Video Capture Read/Write Streaming Extended Pix Format Device Capabilities Device Caps : 0x0521 Video Capture Read/Write Streaming Extended Pix Format $ v4l2-ctl --list-formats-ext ioctl: VIDIOC_ENUM_FMT Type: Video Capture [0]: 'S910' (GSPCA SN9C10X, compressed) Size: Discrete 160x120 Size: Discrete 176x144 Size: Discrete 320x240 Size: Discrete 352x288 [1]: 'BA81' (8-bit Bayer BGBG/GRGR) Size: Discrete 160x120 Size: Discrete 176x144 ProblemType: Bug DistroRelease: Ubuntu 20.04 ProcVersionSignature: Ubuntu 5.11.0-27.29~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Wed Sep 1 15:12:28 2021 InstallationDate: Installed on 2017-06-13 (1540 days ago) InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) Snap: chromium 92.0.4515.159 (latest/candidate) SnapSource: ubuntu/+source/chromium-browser UpgradeStatus: Upgraded to focal on 2019-12-22 (618 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1942364/+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 1942364] Re: sonixb camera is unusable on Chromium
Hi, here is the output: $ snap connections chromium 2021/09/02 15:46:16.299701 main.go:176: description of prepare-image's "" is lowercase in locale "pt_BR": "o directório de destino" Interface PlugSlot Notas audio-playbackchromium:audio-playback :audio-playback - audio-record chromium:audio-record :audio-record - bluez chromium:bluez :bluez - browser-support chromium:browser-sandbox :browser-support - camerachromium:camera :camera - content[gnome-3-28-1804] chromium:gnome-3-28-1804 gnome-3-28-1804:gnome-3-28-1804 - content[gtk-3-themes] chromium:gtk-3-themes gtk-common-themes:gtk-3-themes - content[icon-themes] chromium:icon-themes gtk-common-themes:icon-themes- content[sound-themes] chromium:sound-themes gtk-common-themes:sound-themes - cups-control chromium:cups-control :cups-control - desktop chromium:desktop:desktop - desktop-legacychromium:desktop-legacy :desktop-legacy - gsettings chromium:gsettings :gsettings - home chromium:home :home - joystick chromium:joystick :joystick - mount-observe chromium:mount-observe - - mpris - chromium:mpris - network chromium:network:network - network-bind chromium:network-bind :network-bind - network-manager chromium:network-manager- - openglchromium:opengl :opengl - password-manager-service chromium:password-manager-service :password-manager-servicemanual personal-fileschromium:chromium-config :personal-files - pulseaudiochromium:pulseaudio - - raw-usb chromium:raw-usb:raw-usb manual removable-media chromium:removable-media :removable-media - screen-inhibit-controlchromium:screen-inhibit-control :screen-inhibit-control - system-files chromium:etc-chromium-browser-policies :system-files - system-packages-doc chromium:system-packages-doc :system-packages-doc - u2f-devices chromium:u2f-devices:u2f-devices - unity7chromium:unity7 :unity7 - upower-observechromium:upower-observe :upower-observe - wayland chromium:wayland:wayland - x11 chromium:x11:x11 - -- 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/1942364 Title: sonixb camera is unusable on Chromium Status in chromium-browser package in Ubuntu: Incomplete Bug description: I'm trying to use an USB camera on Chromium, however it is not being detected. lsusb shows it as: Bus 001 Device 076: ID 0c45:6001 Microdia Genius VideoCAM NB While this camera isn't the best I've ever seen, it works properly when using ffplay and guvcview. The following is the output of some utilities related to the camera: $ v4l2-ctl --info Driver Info: Driver name : sonixb Card type: USB camera Bus info : usb-:00:14.0-1 Driver version : 5.11.22 Capabilities : 0x8521 Video Capture Read/Write Streaming Extended Pix Format Device Capabilities Device Caps : 0x0521 Video Capture Read/Write Streaming Extended Pix Format $ v4l2-ctl --list-formats-ext ioctl:
[Desktop-packages] [Bug 1942364] [NEW] sonixb camera is unusable on Chromium
Public bug reported: I'm trying to use an USB camera on Chromium, however it is not being detected. lsusb shows it as: Bus 001 Device 076: ID 0c45:6001 Microdia Genius VideoCAM NB While this camera isn't the best I've ever seen, it works properly when using ffplay and guvcview. The following is the output of some utilities related to the camera: $ v4l2-ctl --info Driver Info: Driver name : sonixb Card type: USB camera Bus info : usb-:00:14.0-1 Driver version : 5.11.22 Capabilities : 0x8521 Video Capture Read/Write Streaming Extended Pix Format Device Capabilities Device Caps : 0x0521 Video Capture Read/Write Streaming Extended Pix Format $ v4l2-ctl --list-formats-ext ioctl: VIDIOC_ENUM_FMT Type: Video Capture [0]: 'S910' (GSPCA SN9C10X, compressed) Size: Discrete 160x120 Size: Discrete 176x144 Size: Discrete 320x240 Size: Discrete 352x288 [1]: 'BA81' (8-bit Bayer BGBG/GRGR) Size: Discrete 160x120 Size: Discrete 176x144 ProblemType: Bug DistroRelease: Ubuntu 20.04 ProcVersionSignature: Ubuntu 5.11.0-27.29~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Wed Sep 1 15:12:28 2021 InstallationDate: Installed on 2017-06-13 (1540 days ago) InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) Snap: chromium 92.0.4515.159 (latest/candidate) SnapSource: ubuntu/+source/chromium-browser UpgradeStatus: Upgraded to focal on 2019-12-22 (618 days ago) ** Affects: chromium-browser (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal snap -- 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/1942364 Title: sonixb camera is unusable on Chromium Status in chromium-browser package in Ubuntu: New Bug description: I'm trying to use an USB camera on Chromium, however it is not being detected. lsusb shows it as: Bus 001 Device 076: ID 0c45:6001 Microdia Genius VideoCAM NB While this camera isn't the best I've ever seen, it works properly when using ffplay and guvcview. The following is the output of some utilities related to the camera: $ v4l2-ctl --info Driver Info: Driver name : sonixb Card type: USB camera Bus info : usb-:00:14.0-1 Driver version : 5.11.22 Capabilities : 0x8521 Video Capture Read/Write Streaming Extended Pix Format Device Capabilities Device Caps : 0x0521 Video Capture Read/Write Streaming Extended Pix Format $ v4l2-ctl --list-formats-ext ioctl: VIDIOC_ENUM_FMT Type: Video Capture [0]: 'S910' (GSPCA SN9C10X, compressed) Size: Discrete 160x120 Size: Discrete 176x144 Size: Discrete 320x240 Size: Discrete 352x288 [1]: 'BA81' (8-bit Bayer BGBG/GRGR) Size: Discrete 160x120 Size: Discrete 176x144 ProblemType: Bug DistroRelease: Ubuntu 20.04 ProcVersionSignature: Ubuntu 5.11.0-27.29~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Wed Sep 1 15:12:28 2021 InstallationDate: Installed on 2017-06-13 (1540 days ago) InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) Snap: chromium 92.0.4515.159 (latest/candidate) SnapSource: ubuntu/+source/chromium-browser UpgradeStatus: Upgraded to focal on 2019-12-22 (618 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1942364/+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 1920940] [NEW] Serial ports aren't detected on Chromium snap
Public bug reported:
When using the Chromium snap, navigator.serial is unable to detect any
serial device.
Steps to reproduce:
1) open Chromium;
2) open the console;
3) run the following code in the console:
port = await navigator.serial.requestPort({});
4) Notice how no serial devices appear (on my computer, all the ttyS and ttyUSB
devices appeared on Google Chrome deb).
It was noticed that an errir message appears on the terminal when the command
is used on Chromium:
[37343:37576:0323/120756.847197:ERROR:udev_watcher.cc(97)] Failed to begin udev
enumeration.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
ProcVersionSignature: Ubuntu 5.8.0-45.51~20.04.1-generic 5.8.18
Uname: Linux 5.8.0-45-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu27.16
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: XFCE
Date: Tue Mar 23 11:59:20 2021
InstallationDate: Installed on 2017-06-13 (1378 days ago)
InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
Snap: chromium 89.0.4389.90 (latest/candidate)
SnapSource: ubuntu/+source/chromium-browser
UpgradeStatus: Upgraded to focal on 2019-12-22 (456 days ago)
** Affects: chromium-browser (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug focal snap
--
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/1920940
Title:
Serial ports aren't detected on Chromium snap
Status in chromium-browser package in Ubuntu:
New
Bug description:
When using the Chromium snap, navigator.serial is unable to detect any
serial device.
Steps to reproduce:
1) open Chromium;
2) open the console;
3) run the following code in the console:
port = await navigator.serial.requestPort({});
4) Notice how no serial devices appear (on my computer, all the ttyS and
ttyUSB devices appeared on Google Chrome deb).
It was noticed that an errir message appears on the terminal when the command
is used on Chromium:
[37343:37576:0323/120756.847197:ERROR:udev_watcher.cc(97)] Failed to begin
udev enumeration.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
ProcVersionSignature: Ubuntu 5.8.0-45.51~20.04.1-generic 5.8.18
Uname: Linux 5.8.0-45-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu27.16
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: XFCE
Date: Tue Mar 23 11:59:20 2021
InstallationDate: Installed on 2017-06-13 (1378 days ago)
InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
Snap: chromium 89.0.4389.90 (latest/candidate)
SnapSource: ubuntu/+source/chromium-browser
UpgradeStatus: Upgraded to focal on 2019-12-22 (456 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1920940/+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
