[Desktop-packages] [Bug 2048792] Re: Firefox utilizing 100% of station CPU
@Nick, if the issue is easy to trigger in your setup would it be possible to at least test on a machine if installing a recent version of firefox would fix the issue? as for your question about flag/profiler I don't have any suggestion offhand and would need to investigate but again you might have more eyes on the question if it's asked upstream so I would recommend adding a comment to the report Amin referenced -- 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/2048792 Title: Firefox utilizing 100% of station CPU Status in firefox package in Ubuntu: New Bug description: At a high level, in certain instances we’re experiencing sustained abnormally high (100%) CPU utilization from Firefox. This utilization is competing with other critical application processes on the systems, starving them of resources, causing issues in the application processing. This happens, at times, when the browser should be idle, even. We have not isolated this issue to be a bug with firefox itself or an issue with the webpage content being provided to the browser. Regardless, here are the symptoms: * CPU usage is extremely high for the FireFox process (>100% on average vs <10% average for healthy stations) even while the screen is sitting idle (no animations, user interactions, etc.) * We have isolated the thread within FireFox causing the most CPU usage to the Renderer thread with the SwComposite threads also consuming abnormally high CPU. * In the FireFox Task and Process Managers, we have validated there is no single tab or window consuming abnormally high CPU, just the FireFox master process. * Additionally, we have confirmed that the FireFox browser history (taken from the places.sqlite file) does not have any webpages being loaded during the times when CPU consumption experiences a step function change up or down. * We also have linux perf logs for the FireFox process on healthy stations and impacted stations while sitting idle on the login screen, which can provide some stack traces for the Renderer and other threads which may be more useful to someone with FireFox expertise. * The biggest difference is that the impacted workcells have the Renderer and Compositor 'tracks' very active while the healthy workcells see no usage of these tracks at all. * These 2 tracks also have supporting tracks such as SwComposite and WRRendererBackend#X. There were 2 of each of these, which may indicate the issue is happening across both FireFox windows. For reference, the stations always have 2 windows open: one for the screen UI and one for the projector on the pod face. * (Using the term 'track' here as defined by the open source FireFox profiler: https://profiler.firefox.com/. Basically a thread within the FireFox main process) * There are many memory copy and SW interrupt calls being made in these tracks. * This validates that FireFox is contributing to increased software interrupt load * Additionally, we found an interesting pair of calls occurring periodically in the Renderer track. We have not deep dived these yet, but on the off chance it matters, we're including it in this report: * viaduct_log_error - every 50 - 500ms * wgpu_render_pass_end_pipeline_statistics_query - every 50 - 1000ms To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/2048792/+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 2048792] Re: Firefox utilizing 100% of station CPU
Hi All, I'm a developer with Steve's group. Thank you for taking a look at this and linking to that other bug! I took a look through the profiler summaries linked in the thread and it appears very similar to what we are observing. We also captured performance profiles for the current version of Firefox we're using (100.0.2), and we observed similar behavior from the Renderer, Compositor, and SwComposite tracks. Since we are unable to change Firefox version quickly in our use case, we would like to understand if there are any mitigations or settings we could modify to prevent these symptoms. The last comment in the linked bug thread mentions that disabling and re-enabling the Compositor resolved symptoms, so we will try this out tomorrow. Longer term though, upgrading the version is absolutely something we're looking at. In addition to testing changes with the Compositor settings, are there any parameters we could change in the about:config page? In our initial testing, we have observed CPU usage vary roughly proportionately with the layout.frame_rate parameter when these CPU throttling symptoms are present (default was -1, and when we set to 30 or 15 for example, we see the CPU usage decrease). We can also collect additional Firefox profiler results or other logs if they would help clarify the issue/symptoms. -- 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/2048792 Title: Firefox utilizing 100% of station CPU Status in firefox package in Ubuntu: New Bug description: At a high level, in certain instances we’re experiencing sustained abnormally high (100%) CPU utilization from Firefox. This utilization is competing with other critical application processes on the systems, starving them of resources, causing issues in the application processing. This happens, at times, when the browser should be idle, even. We have not isolated this issue to be a bug with firefox itself or an issue with the webpage content being provided to the browser. Regardless, here are the symptoms: * CPU usage is extremely high for the FireFox process (>100% on average vs <10% average for healthy stations) even while the screen is sitting idle (no animations, user interactions, etc.) * We have isolated the thread within FireFox causing the most CPU usage to the Renderer thread with the SwComposite threads also consuming abnormally high CPU. * In the FireFox Task and Process Managers, we have validated there is no single tab or window consuming abnormally high CPU, just the FireFox master process. * Additionally, we have confirmed that the FireFox browser history (taken from the places.sqlite file) does not have any webpages being loaded during the times when CPU consumption experiences a step function change up or down. * We also have linux perf logs for the FireFox process on healthy stations and impacted stations while sitting idle on the login screen, which can provide some stack traces for the Renderer and other threads which may be more useful to someone with FireFox expertise. * The biggest difference is that the impacted workcells have the Renderer and Compositor 'tracks' very active while the healthy workcells see no usage of these tracks at all. * These 2 tracks also have supporting tracks such as SwComposite and WRRendererBackend#X. There were 2 of each of these, which may indicate the issue is happening across both FireFox windows. For reference, the stations always have 2 windows open: one for the screen UI and one for the projector on the pod face. * (Using the term 'track' here as defined by the open source FireFox profiler: https://profiler.firefox.com/. Basically a thread within the FireFox main process) * There are many memory copy and SW interrupt calls being made in these tracks. * This validates that FireFox is contributing to increased software interrupt load * Additionally, we found an interesting pair of calls occurring periodically in the Renderer track. We have not deep dived these yet, but on the off chance it matters, we're including it in this report: * viaduct_log_error - every 50 - 500ms * wgpu_render_pass_end_pipeline_statistics_query - every 50 - 1000ms To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/2048792/+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 2048827] [NEW] yaru mouse cursor theme is grey instead of black
Public bug reported: - this is a fresh install of the latest Ubuntu 24.04 - I have fully updated the debs and snaps - my mouse cursor is grey when it should be black - the strange thing is the cursor looks normal when I boot off the USB and then looks grey on first boot - even more strange is when I went to screenshot the cursor for this bug report, it looked normal in the screenshot - For graphics I have AMD 6600XT - I will try in X11 as well to see if this is a Wayland-only issue ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: yaru-theme-gtk 22.04.5 ProcVersionSignature: Ubuntu 6.2.0-39.40~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-39-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Jan 9 21:57:08 2024 InstallationDate: Installed on 2024-01-10 (0 days ago) InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.2) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: yaru-theme UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: yaru-theme (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy wayland-session -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to yaru-theme in Ubuntu. https://bugs.launchpad.net/bugs/2048827 Title: yaru mouse cursor theme is grey instead of black Status in yaru-theme package in Ubuntu: New Bug description: - this is a fresh install of the latest Ubuntu 24.04 - I have fully updated the debs and snaps - my mouse cursor is grey when it should be black - the strange thing is the cursor looks normal when I boot off the USB and then looks grey on first boot - even more strange is when I went to screenshot the cursor for this bug report, it looked normal in the screenshot - For graphics I have AMD 6600XT - I will try in X11 as well to see if this is a Wayland-only issue ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: yaru-theme-gtk 22.04.5 ProcVersionSignature: Ubuntu 6.2.0-39.40~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-39-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Jan 9 21:57:08 2024 InstallationDate: Installed on 2024-01-10 (0 days ago) InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.2) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: yaru-theme UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/yaru-theme/+bug/2048827/+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 2030947] Re: gnome-shell spams journal with `g_closure_add_invalidate_notifier: assertion 'closure->n_inotifiers < CLOSURE_MAX_N_INOTIFIERS' failed` when 'Zoom' a11y feature en
** Tags added: noble -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gjs in Ubuntu. https://bugs.launchpad.net/bugs/2030947 Title: gnome-shell spams journal with `g_closure_add_invalidate_notifier: assertion 'closure->n_inotifiers < CLOSURE_MAX_N_INOTIFIERS' failed` when 'Zoom' a11y feature enabled Status in GNOME Shell: New Status in gjs package in Ubuntu: New Bug description: gnome-shell logs gnome-shell[4537]: g_closure_add_invalidate_notifier: assertion 'closure->n_inotifiers < CLOSURE_MAX_N_INOTIFIERS' failed multiple times per second for weeks now. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: gnome-shell 44.3-1ubuntu1 ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5 Uname: Linux 6.3.0-7-generic x86_64 ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: GNOME Date: Thu Aug 10 10:38:23 2023 DisplayManager: gdm3 InstallationDate: Installed on 2022-11-26 (256 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20221126) RelatedPackageVersions: mutter-common 44.3-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/2030947/+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 2016925] Re: [amdgpu] Firefox window is visually corrupted after upgrading to Ubuntu 23.04
Let's let it close automatically... if there are no more comments in two months. ** Changed in: firefox (Ubuntu) Status: Confirmed => Incomplete -- 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/2016925 Title: [amdgpu] Firefox window is visually corrupted after upgrading to Ubuntu 23.04 Status in firefox package in Ubuntu: Incomplete Bug description: After upgrading from Ubuntu 22.10 to Ubuntu 23.04, every time I open firefox the windows is heavily visually corrupted. It seems to work fine under the corruption, but it is completely unusuable. The tar version of Firefox works fine. In the attached screenshot you can see the snap version of Firefox (corrupted) and the tar version of Firefox (working fine). I tried uninstalling (with --purge) and reinstalling and refreshing firefox to no avail. All other applications, including 3D games, are working fine. I am using an AMD RX5500 with default mesa drivers. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: firefox 1:1snap1-0ubuntu3 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Apr 18 18:04:26 2023 InstallationDate: Installed on 2020-11-04 (895 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) SnapChanges: IDEstado Generado Listo Resumen 1215 Done2023-04-18T17:42:17-03:00 2023-04-18T17:44:05-03:00 Eliminar snap "firefox" 1216 Done2023-04-18T17:45:37-03:00 2023-04-18T17:47:25-03:00 Instalar snap "firefox" 1217 Done2023-04-18T17:48:16-03:00 2023-04-18T17:48:30-03:00 Eliminar snap "firefox" 1218 Done2023-04-18T17:48:39-03:00 2023-04-18T17:48:49-03:00 Instalar snap "firefox" SourcePackage: firefox UpgradeStatus: Upgraded to lunar on 2023-04-18 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/2016925/+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 2048807] [NEW] upgrade 23.04 to 23.10 fails
Public bug reported: sudo apt-get install -f [sudo] password for gord: Reading package lists... Done Building dependency tree... Done Reading state information... Done Correcting dependencies... Done The following packages were automatically installed and are no longer required: i965-va-driver intel-media-va-driver libaom3 libavcodec59 libavutil57 libcodec2-1.0 libdav1d6 libgsm1 libhwy1 libigdgmm12 libjxl0.7 libmfx1 librav1e0 libshine3 libsnappy1v5 libsoxr0 libspeexdsp1 libsvtav1enc1 libswresample4 libva-drm2 libva-x11-2 libva2 libvdpau1 libx264-164 libx265-199 libxvidcore4 libzvbi0 mesa-va-drivers mesa-vdpau-drivers va-driver-all vdpau-driver-all Use 'sudo apt autoremove' to remove them. The following additional packages will be installed: libvdpau1 The following NEW packages will be installed: libvdpau1 0 upgraded, 1 newly installed, 0 to remove and 17 not upgraded. 242 not fully installed or removed. Need to get 0 B/27.8 kB of archives. After this operation, 110 kB of additional disk space will be used. Do you want to continue? [Y/n] y (Reading database ... 267468 files and directories currently installed.) Preparing to unpack .../libvdpau1_1.5-2_amd64.deb ... Unpacking libvdpau1:amd64 (1.5-2) ... dpkg: error processing archive /var/cache/apt/archives/libvdpau1_1.5-2_amd64.deb (--unpack): trying to overwrite shared '/etc/vdpau_wrapper.cfg', which is different from other instances of package libvdpau1:amd64 Errors were encountered while processing: /var/cache/apt/archives/libvdpau1_1.5-2_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) I ran autoremove and fix-broken many times ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: libvdpau1 (not installed) ProcVersionSignature: Ubuntu 6.2.0-39.40-generic 6.2.16 Uname: Linux 6.2.0-39-generic x86_64 ApportVersion: 2.26.1-0ubuntu2.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Jan 9 19:36:46 2024 DistUpgraded: 2024-01-02 20:20:31,903 DEBUG /openCache(), new cache size 76413 DistroCodename: lunar DistroVariant: ubuntu GraphicsCard: Intel Corporation Atom Processor Z36xxx/Z37xxx Series Graphics & Display [8086:0f31] (rev 0e) (prog-if 00 [VGA controller]) Subsystem: ASRock Incorporation Atom Processor Z36xxx/Z37xxx Series Graphics & Display [1849:0f31] InstallationDate: Installed on 2023-07-24 (169 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-39-generic root=UUID=fdc37e2b-a361-4507-8f3f-5a111640986f ro quiet splash vt.handoff=7 SourcePackage: libvdpau UpgradeStatus: Upgraded to lunar on 2024-01-03 (6 days ago) dmi.bios.date: 10/24/2014 dmi.bios.release: 5.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.30 dmi.board.name: IMB-150 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.30:bd10/24/2014:br5.6:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnIMB-150: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. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.114-1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.4-0ubuntu1~23.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-1ubuntu3.4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 ** Affects: libvdpau (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug lunar ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libvdpau in Ubuntu. https://bugs.launchpad.net/bugs/2048807 Title: upgrade 23.04 to 23.10 fails Status in libvdpau package in Ubuntu: New Bug description: sudo apt-get install -f [sudo] password for gord: Reading package lists... Done Building dependency tree... Done Reading state information... Done Correcting dependencies... Done The following packages were automatically installed and are no longer required: i965-va-driver intel-media-va-driver libaom3 libavcodec59 libavutil57 libcodec2-1.0 libdav1d6 libgsm1 libhwy1 libigdgmm12 libjxl0.7 libmfx1 librav1e0 libshine3 libsnappy1v5 libsoxr0
[Desktop-packages] [Bug 2043177] Re: gnome-shell crashed with SIGSEGV in wl_resource_post_error_vargs from wl_resource_post_error "destroyed popup not top most popup"
** Changed in: mutter Status: Unknown => New -- 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/2043177 Title: gnome-shell crashed with SIGSEGV in wl_resource_post_error_vargs from wl_resource_post_error "destroyed popup not top most popup" Status in Mutter: New Status in mutter package in Ubuntu: Confirmed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 45.0-1ubuntu2, the problem page at https://errors.ubuntu.com/problem/53aea76c746a4e6657e752b77398505921f13491 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/2043177/+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 2047256] Re: Ubuntu 24.04 Some image thumbnails no longer displayed
This bug has been reported on the Ubuntu ISO testing tracker. A list of all reports related to this bug can be found here: http://iso.qa.ubuntu.com/qatracker/reports/bugs/2047256 ** Tags added: iso-testing -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/2047256 Title: Ubuntu 24.04 Some image thumbnails no longer displayed Status in nautilus package in Ubuntu: Confirmed Bug description: After recent updates on my Ubuntu Noble 24.04 nautilus does not show thumbnails of PDF files. On a different partition same PC Ubuntu Noble 24.04 not recently updated PDF thumbnails are correctly displayed ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: nautilus 1:45~rc-1ubuntu1 ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3 Uname: Linux 6.5.0-9-generic x86_64 ApportVersion: 2.27.0-0ubuntu6 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Dec 22 16:15:59 2023 GsettingsChanges: b'org.gnome.nautilus.preferences' b'migrated-gtk-settings' b'true' b'org.gnome.nautilus.window-state' b'initial-size' b'(879, 943)' InstallationDate: Installed on 2023-12-10 (12 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20231210) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: file-roller 43.1-1 nautilus-extension-gnome-terminal 3.49.92-2ubuntu1 nautilus-image-converter 0.4.0-2 nautilus-share0.7.5-0.3 python3-nautilus 4.0-1build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2047256/+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 2048792] Re: Firefox utilizing 100% of station CPU
Hello, The reported version of Firefox (100.0.2) is rather old at this point, and could be a potential security risk: to my knowledge, Mozilla don't backport bug fixes to older versions of Firefox (except for the current Firefox ESR series), and many security and non-security related issues have since been reported and fixed in later Firefox versions. Thus, I would highly recommend considering updating your system packages, including Firefox, to latest versions and then try again - your issue may already have been fixed in a newer version of Firefox. If the issue still persists with up-to-date Firefox and system packages, I would echo Seb's recommendation of reporting the bug upstream at https://bugzilla.mozilla.org, and include a performance profile per https://profiler.firefox.com as well. Searching through Bugzilla, https://bugzilla.mozilla.org/1733377 came up, but I'm not sure whether or not it's the same issue. Please feel free to comment on that and/or open a new issue. -- 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/2048792 Title: Firefox utilizing 100% of station CPU Status in firefox package in Ubuntu: New Bug description: At a high level, in certain instances we’re experiencing sustained abnormally high (100%) CPU utilization from Firefox. This utilization is competing with other critical application processes on the systems, starving them of resources, causing issues in the application processing. This happens, at times, when the browser should be idle, even. We have not isolated this issue to be a bug with firefox itself or an issue with the webpage content being provided to the browser. Regardless, here are the symptoms: * CPU usage is extremely high for the FireFox process (>100% on average vs <10% average for healthy stations) even while the screen is sitting idle (no animations, user interactions, etc.) * We have isolated the thread within FireFox causing the most CPU usage to the Renderer thread with the SwComposite threads also consuming abnormally high CPU. * In the FireFox Task and Process Managers, we have validated there is no single tab or window consuming abnormally high CPU, just the FireFox master process. * Additionally, we have confirmed that the FireFox browser history (taken from the places.sqlite file) does not have any webpages being loaded during the times when CPU consumption experiences a step function change up or down. * We also have linux perf logs for the FireFox process on healthy stations and impacted stations while sitting idle on the login screen, which can provide some stack traces for the Renderer and other threads which may be more useful to someone with FireFox expertise. * The biggest difference is that the impacted workcells have the Renderer and Compositor 'tracks' very active while the healthy workcells see no usage of these tracks at all. * These 2 tracks also have supporting tracks such as SwComposite and WRRendererBackend#X. There were 2 of each of these, which may indicate the issue is happening across both FireFox windows. For reference, the stations always have 2 windows open: one for the screen UI and one for the projector on the pod face. * (Using the term 'track' here as defined by the open source FireFox profiler: https://profiler.firefox.com/. Basically a thread within the FireFox main process) * There are many memory copy and SW interrupt calls being made in these tracks. * This validates that FireFox is contributing to increased software interrupt load * Additionally, we found an interesting pair of calls occurring periodically in the Renderer track. We have not deep dived these yet, but on the off chance it matters, we're including it in this report: * viaduct_log_error - every 50 - 500ms * wgpu_render_pass_end_pipeline_statistics_query - every 50 - 1000ms To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/2048792/+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 2048792] Re: Firefox utilizing 100% of station CPU
** Summary changed: - Firefox utilizins 100% of station CPU + Firefox utilizing 100% of station CPU -- 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/2048792 Title: Firefox utilizing 100% of station CPU Status in firefox package in Ubuntu: New Bug description: At a high level, in certain instances we’re experiencing sustained abnormally high (100%) CPU utilization from Firefox. This utilization is competing with other critical application processes on the systems, starving them of resources, causing issues in the application processing. This happens, at times, when the browser should be idle, even. We have not isolated this issue to be a bug with firefox itself or an issue with the webpage content being provided to the browser. Regardless, here are the symptoms: * CPU usage is extremely high for the FireFox process (>100% on average vs <10% average for healthy stations) even while the screen is sitting idle (no animations, user interactions, etc.) * We have isolated the thread within FireFox causing the most CPU usage to the Renderer thread with the SwComposite threads also consuming abnormally high CPU. * In the FireFox Task and Process Managers, we have validated there is no single tab or window consuming abnormally high CPU, just the FireFox master process. * Additionally, we have confirmed that the FireFox browser history (taken from the places.sqlite file) does not have any webpages being loaded during the times when CPU consumption experiences a step function change up or down. * We also have linux perf logs for the FireFox process on healthy stations and impacted stations while sitting idle on the login screen, which can provide some stack traces for the Renderer and other threads which may be more useful to someone with FireFox expertise. * The biggest difference is that the impacted workcells have the Renderer and Compositor 'tracks' very active while the healthy workcells see no usage of these tracks at all. * These 2 tracks also have supporting tracks such as SwComposite and WRRendererBackend#X. There were 2 of each of these, which may indicate the issue is happening across both FireFox windows. For reference, the stations always have 2 windows open: one for the screen UI and one for the projector on the pod face. * (Using the term 'track' here as defined by the open source FireFox profiler: https://profiler.firefox.com/. Basically a thread within the FireFox main process) * There are many memory copy and SW interrupt calls being made in these tracks. * This validates that FireFox is contributing to increased software interrupt load * Additionally, we found an interesting pair of calls occurring periodically in the Renderer track. We have not deep dived these yet, but on the off chance it matters, we're including it in this report: * viaduct_log_error - every 50 - 500ms * wgpu_render_pass_end_pipeline_statistics_query - every 50 - 1000ms To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/2048792/+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 2048792] Re: Firefox utilizins 100% of station CPU
Thank you for your bug report. We don't really change the code over upstream and have limited resources and knowledge of the project compared to them, it would be a good idea to check if there is a similar issue reported on https://bugzilla.mozilla.org/ already and if not to open also there. We might pick up the issue/work on it when our team capacity allows for it but upstream might help getting it resolved sooner. -- 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/2048792 Title: Firefox utilizins 100% of station CPU Status in firefox package in Ubuntu: New Bug description: At a high level, in certain instances we’re experiencing sustained abnormally high (100%) CPU utilization from Firefox. This utilization is competing with other critical application processes on the systems, starving them of resources, causing issues in the application processing. This happens, at times, when the browser should be idle, even. We have not isolated this issue to be a bug with firefox itself or an issue with the webpage content being provided to the browser. Regardless, here are the symptoms: * CPU usage is extremely high for the FireFox process (>100% on average vs <10% average for healthy stations) even while the screen is sitting idle (no animations, user interactions, etc.) * We have isolated the thread within FireFox causing the most CPU usage to the Renderer thread with the SwComposite threads also consuming abnormally high CPU. * In the FireFox Task and Process Managers, we have validated there is no single tab or window consuming abnormally high CPU, just the FireFox master process. * Additionally, we have confirmed that the FireFox browser history (taken from the places.sqlite file) does not have any webpages being loaded during the times when CPU consumption experiences a step function change up or down. * We also have linux perf logs for the FireFox process on healthy stations and impacted stations while sitting idle on the login screen, which can provide some stack traces for the Renderer and other threads which may be more useful to someone with FireFox expertise. * The biggest difference is that the impacted workcells have the Renderer and Compositor 'tracks' very active while the healthy workcells see no usage of these tracks at all. * These 2 tracks also have supporting tracks such as SwComposite and WRRendererBackend#X. There were 2 of each of these, which may indicate the issue is happening across both FireFox windows. For reference, the stations always have 2 windows open: one for the screen UI and one for the projector on the pod face. * (Using the term 'track' here as defined by the open source FireFox profiler: https://profiler.firefox.com/. Basically a thread within the FireFox main process) * There are many memory copy and SW interrupt calls being made in these tracks. * This validates that FireFox is contributing to increased software interrupt load * Additionally, we found an interesting pair of calls occurring periodically in the Renderer track. We have not deep dived these yet, but on the off chance it matters, we're including it in this report: * viaduct_log_error - every 50 - 500ms * wgpu_render_pass_end_pipeline_statistics_query - every 50 - 1000ms To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/2048792/+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 1928867] Re: System freeze on bulk rename
There is a fix proposed on https://gitlab.gnome.org/GNOME/nautilus/-/merge_requests/575 ** Changed in: nautilus (Ubuntu) Importance: Undecided => High ** Changed in: nautilus (Ubuntu) Status: Confirmed => Triaged ** Also affects: gnome-shell via https://gitlab.gnome.org/GNOME/nautilus/-/issues/1443 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1928867 Title: System freeze on bulk rename Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: Invalid Status in nautilus package in Ubuntu: Triaged Bug description: Ubuntu 20.04 Nautilus 1:3.36.3-0ubuntu1 Bug: I have 8 files named as file-1.jpg, file-2.jpg, ... file-8.jpg When I select them all and rename using template as 'file-[1, 2, 3]' in descending order, the system freezes. Perhaps because the files already exist with same name? I was expecting the files to be renamed in descending series - file-1.jpg as file-8.jpg, file-2.jpg as file-7.jpg and so on.. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: nautilus 1:3.36.3-0ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-53.60~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-53-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.17 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed May 19 00:44:49 2021 GsettingsChanges: b'org.gnome.nautilus.window-state' b'sidebar-width' b'161' b'org.gnome.nautilus.window-state' b'initial-size' b'(891, 546)' InstallationDate: Installed on 2020-04-24 (389 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1928867/+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 1928867] Re: System freeze on bulk rename
There is a fix proposed on https://gitlab.gnome.org/GNOME/nautilus/-/merge_requests/575 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1928867 Title: System freeze on bulk rename Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: Invalid Status in nautilus package in Ubuntu: Triaged Bug description: Ubuntu 20.04 Nautilus 1:3.36.3-0ubuntu1 Bug: I have 8 files named as file-1.jpg, file-2.jpg, ... file-8.jpg When I select them all and rename using template as 'file-[1, 2, 3]' in descending order, the system freezes. Perhaps because the files already exist with same name? I was expecting the files to be renamed in descending series - file-1.jpg as file-8.jpg, file-2.jpg as file-7.jpg and so on.. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: nautilus 1:3.36.3-0ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-53.60~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-53-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.17 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed May 19 00:44:49 2021 GsettingsChanges: b'org.gnome.nautilus.window-state' b'sidebar-width' b'161' b'org.gnome.nautilus.window-state' b'initial-size' b'(891, 546)' InstallationDate: Installed on 2020-04-24 (389 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1928867/+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 2037528] Re: every tab with touchscreen on a folder gives the context menu.
** Changed in: nautilus (Ubuntu) Importance: Undecided => Low ** Changed in: nautilus (Ubuntu) Status: Confirmed => Triaged ** Also affects: nautilus via https://gitlab.gnome.org/GNOME/nautilus/-/issues/2872 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/2037528 Title: every tab with touchscreen on a folder gives the context menu. Status in Nautilus: Unknown Status in nautilus package in Ubuntu: Triaged Bug description: Ubuntu installed on Chuwi u-book x pro (13 inch). CPU: Intel® Core™ i7-7Y75 × 4 GPU: Intel® HD Graphics 615 (KBL GT2) Tapping a folder in Nautilus always gives the context menu. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: nautilus 1:44.2.1-0ubuntu1 ProcVersionSignature: Ubuntu 6.2.0-33.33-generic 6.2.16 Uname: Linux 6.2.0-33-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Sep 27 12:08:40 2023 GsettingsChanges: b'org.gnome.nautilus.preferences' b'click-policy' b"'single'" b'org.gnome.nautilus.preferences' b'migrated-gtk-settings' b'true' b'org.gnome.nautilus.window-state' b'maximized' b'true' InstallationDate: Installed on 2023-09-19 (7 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: file-roller 43.0-1 nautilus-extension-gnome-terminal 3.48.0-1ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/2037528/+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 2048792] Re: Firefox utilizins 100% of station CPU
Additional info: Firefox is at version 100.0.2 It is installed as a deb package We're running Ubuntu 20.04 -- 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/2048792 Title: Firefox utilizins 100% of station CPU Status in firefox package in Ubuntu: New Bug description: At a high level, in certain instances we’re experiencing sustained abnormally high (100%) CPU utilization from Firefox. This utilization is competing with other critical application processes on the systems, starving them of resources, causing issues in the application processing. This happens, at times, when the browser should be idle, even. We have not isolated this issue to be a bug with firefox itself or an issue with the webpage content being provided to the browser. Regardless, here are the symptoms: * CPU usage is extremely high for the FireFox process (>100% on average vs <10% average for healthy stations) even while the screen is sitting idle (no animations, user interactions, etc.) * We have isolated the thread within FireFox causing the most CPU usage to the Renderer thread with the SwComposite threads also consuming abnormally high CPU. * In the FireFox Task and Process Managers, we have validated there is no single tab or window consuming abnormally high CPU, just the FireFox master process. * Additionally, we have confirmed that the FireFox browser history (taken from the places.sqlite file) does not have any webpages being loaded during the times when CPU consumption experiences a step function change up or down. * We also have linux perf logs for the FireFox process on healthy stations and impacted stations while sitting idle on the login screen, which can provide some stack traces for the Renderer and other threads which may be more useful to someone with FireFox expertise. * The biggest difference is that the impacted workcells have the Renderer and Compositor 'tracks' very active while the healthy workcells see no usage of these tracks at all. * These 2 tracks also have supporting tracks such as SwComposite and WRRendererBackend#X. There were 2 of each of these, which may indicate the issue is happening across both FireFox windows. For reference, the stations always have 2 windows open: one for the screen UI and one for the projector on the pod face. * (Using the term 'track' here as defined by the open source FireFox profiler: https://profiler.firefox.com/. Basically a thread within the FireFox main process) * There are many memory copy and SW interrupt calls being made in these tracks. * This validates that FireFox is contributing to increased software interrupt load * Additionally, we found an interesting pair of calls occurring periodically in the Renderer track. We have not deep dived these yet, but on the off chance it matters, we're including it in this report: * viaduct_log_error - every 50 - 500ms * wgpu_render_pass_end_pipeline_statistics_query - every 50 - 1000ms To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/2048792/+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 2048797] [NEW] Screen Sharing no longer works with nouveau driver
Public bug reported: Hi Since the end of last november, screen sharing no longer works, i get a black screen. here is the log i get nouveau :01:00.0: gr: DATA_ERROR 009c [] ch 1 [02ffd8c000 gnome- shell[1369]] subc 0 class c797 mthd 17e0 data 0030 if i install NVIDIA proprietary driver (nvidia-driver-535) the screen sharing work again, back to nouveau it fails. i'm on Ubuntu 22.04.3 LTS with latest update Linux touco-System-Product-Name 6.2.0-39-generic #40~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Thu Nov 16 10:53:04 UTC 2 x86_64 x86_64 x86_64 GNU/Linux my graphics card is [GeForce RTX 3060 Lite Hash Rate] (rev a1) i have a laptop with exact Ubuntu version and updates, screen sharing works with nouveau driver but the graphic card is NVIDIA® GeForce RTX™ 3070 Laptop GPU I made the test with chrome on this site https://www.webrtc- experiment.com/Pluginfree-Screen-Sharing ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xserver-xorg-video-nouveau 1:1.0.17-2build1 ProcVersionSignature: Ubuntu 6.2.0-39.40~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-39-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Jan 9 19:23:06 2024 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GA106 [GeForce RTX 3060 Lite Hash Rate] [10de:2504] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd GA106 [GeForce RTX 3060 Lite Hash Rate] [1458:4096] InstallationDate: Installed on 2022-07-12 (546 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: ASUS System Product Name ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-39-generic root=UUID=c179fd07-f21e-43e9-856b-eeaeb54b2ebb ro quiet splash vt.handoff=7 SourcePackage: xserver-xorg-video-nouveau UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/11/2023 dmi.bios.release: 30.10 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3010 dmi.board.asset.tag: Default string dmi.board.name: PRIME Z690M-PLUS D4 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3010:bd12/11/2023:br30.10:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEZ690M-PLUSD4:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: ASUS version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.4-0ubuntu1~22.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.5 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 ** Affects: xserver-xorg-video-nouveau (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy ubuntu wayland-session -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-nouveau in Ubuntu. https://bugs.launchpad.net/bugs/2048797 Title: Screen Sharing no longer works with nouveau driver Status in xserver-xorg-video-nouveau package in Ubuntu: New Bug description: Hi Since the end of last november, screen sharing no longer works, i get a black screen. here is the log i get nouveau :01:00.0: gr: DATA_ERROR 009c [] ch 1 [02ffd8c000 gnome-shell[1369]] subc 0 class c797 mthd 17e0 data 0030 if i install NVIDIA proprietary driver (nvidia-driver-535) the screen sharing work again, back to nouveau it fails. i'm on Ubuntu 22.04.3 LTS with latest update Linux touco-System-Product-Name 6.2.0-39-generic #40~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Thu Nov 16 10:53:04 UTC 2 x86_64 x86_64 x86_64 GNU/Linux my graphics card is [GeForce RTX 3060 Lite Hash Rate] (rev a1) i have a laptop with exact Ubuntu version and updates, screen sharing works with nouveau driver but the graphic card is NVIDIA® GeForce RTX™ 3070 Laptop GPU I made the test with chrome on this site https://www.webrtc- experiment.com/Pluginfree-Screen-Sharing ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xserver-xorg-video-nouveau
[Desktop-packages] [Bug 1951075] Re: Nautilus doesn't load and gives GVFS-WARNING
Same on Ubuntu 22.04.3 LTS, I've Keybase installed. I've killed nautilus
(as "nautilus -q" didn't help), killed all keybase processes (one stuck
at [keybase] ), but didn't help either. nautilus still doesn't
start.
$ strace -f nautilus
execve("/usr/bin/nautilus", ["nautilus"], 0x7ffe661c58b8 /* 83 vars */) = 0
...
[pid 20669] poll([{fd=6, events=POLLIN}], 1, 0) = 1 ([{fd=6, revents=POLLIN}])
[pid 20667] write(2, "\n(org.gnome.Nautilus:20667): GVFS-\33[1;33mWARNING\33[0m
**: \33[34m18:17:13.047\33[0m: The peer-to-peer connection failed: Timeout was
reached. Falling back to the session bus. Your application is probably missing
--filesystem=xdg-run/gvfsd privileges.\n", 246
(org.gnome.Nautilus:20667): GVFS-WARNING **: 18:17:13.047: The peer-to-peer
connection failed: Timeout was reached. Falling back to the session bus. Your
application is probably missing --filesystem=xdg-run/gvfsd privileges.
[pid 20669] read(6,
...
[pid 20669] write(6, "\1\0\0\0\0\0\0\0", 8) = 8
[pid 20669] sendmsg(5, {msg_name=NULL, msg_namelen=0,
msg_iov=[{iov_base="l\1\0\1\f\0\0\0\20\0\0\0z\0\0\0\1\1o\0\24\0\0\0/org/gtk/vfs/mount/1\0\0\0\0\2\1s\0\21\0\0\0org.gtk.vfs.Mount\0\0\0\0\0\0\0\6\1s\0\5\0\0\0:1.51\0\0\0\10\1g\0\3ayu\0\0\0\0\0\0\0\0\3\1s\0\21\0\0\0CreateFileMonitor\0\0\0\0\0\0\0\2\0\0\0/\0\0\0\0\0\0\0",
iov_len=156}], msg_iovlen=1, msg_controllen=0, msg_flags=0}, MSG_NOSIGNAL) =
156
[pid 20669] poll([{fd=5, events=POLLIN}, {fd=6, events=POLLIN}], 2, 0) = 1
([{fd=6, revents=POLLIN}])
[pid 20669] read(6, "\1\0\0\0\0\0\0\0", 16) = 8
[pid 20669] poll([{fd=5, events=POLLIN}, {fd=6, events=POLLIN}], 2, -1
[pid 20667] <... poll resumed>) = ? ERESTART_RESTARTBLOCK (Interrupted
by signal)
It's not starting at all, only restart helps. It happens very often.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nautilus in Ubuntu.
https://bugs.launchpad.net/bugs/1951075
Title:
Nautilus doesn't load and gives GVFS-WARNING
Status in nautilus package in Ubuntu:
Confirmed
Bug description:
After loading a cifs network drive on the command line, nautilus no
longer loads and shows
(org.gnome.Nautilus:17319): GVFS-WARNING **: 20:32:43.301: The peer-
to-peer connection failed: Timeout was reached. Falling back to the
session bus. Your application is probably missing --filesystem=xdg-
run/gvfsd privileges.
when run from the command line. This is not the same as
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1935734 as I'm
not trying to open as root but as a non-privileged user.
This only started happening after upgrading to 21.10 recently. I tried
upgrading gvfs to 1.48.x though a ppa and the update didn't resolve
the issue. It was working in 21.04, so I assume downgrading gvfs
$ lsb_release -rd
Description: Ubuntu 21.10
Release: 21.10
$ apt-cache policy nautilus gvfs
nautilus:
Installed: 1:40.2-1ubuntu1
Candidate: 1:40.2-1ubuntu1
Version table:
*** 1:40.2-1ubuntu1 500
500 http://au.archive.ubuntu.com/ubuntu impish/main amd64 Packages
100 /var/lib/dpkg/status
gvfs:
Installed: 1.47.91-1ubuntu1
Candidate: 1.47.91-1ubuntu1
Version table:
*** 1.47.91-1ubuntu1 500
500 http://au.archive.ubuntu.com/ubuntu impish/main amd64 Packages
100 /var/lib/dpkg/status
ProblemType: Bug
DistroRelease: Ubuntu 21.10
Package: nautilus 1:40.2-1ubuntu1
ProcVersionSignature: Ubuntu 5.13.0-21.21-generic 5.13.18
Uname: Linux 5.13.0-21-generic x86_64
ApportVersion: 2.20.11-0ubuntu71
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Tue Nov 16 20:35:33 2021
InstallationDate: Installed on 2019-01-27 (1024 days ago)
InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64
(20181017.3)
SourcePackage: nautilus
UpgradeStatus: Upgraded to impish on 2021-11-12 (4 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1951075/+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 2030947] Re: gnome-shell spams journal with `g_closure_add_invalidate_notifier: assertion 'closure->n_inotifiers < CLOSURE_MAX_N_INOTIFIERS' failed` when 'Zoom' a11y feature en
Same on Ubuntu 24.04 corrado@corrado-n9-nn-1210:~$ apt policy gnome-shell gnome-shell: Installed: 45.2-1ubuntu1 Candidate: 45.2-1ubuntu1 Version table: *** 45.2-1ubuntu1 500 500 http://archive.ubuntu.com/ubuntu noble/main amd64 Packages 100 /var/lib/dpkg/status corrado@corrado-n9-nn-1210:~$ Jan 09 18:38:02 corrado-n9-nn-1210 gnome-shell[2134]: g_closure_add_invalidate_notifier: assertion 'closure->n_inotifiers < CLOSURE_MAX_N_INOTIFIERS' failed Jan 09 18:38:02 corrado-n9-nn-1210 gnome-shell[2134]: g_closure_add_invalidate_notifier: assertion 'closure->n_inotifiers < CLOSURE_MAX_N_INOTIFIERS' failed Jan 09 18:38:02 corrado-n9-nn-1210 gnome-shell[2134]: g_closure_add_invalidate_notifier: assertion 'closure->n_inotifiers < CLOSURE_MAX_N_INOTIFIERS' failed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gjs in Ubuntu. https://bugs.launchpad.net/bugs/2030947 Title: gnome-shell spams journal with `g_closure_add_invalidate_notifier: assertion 'closure->n_inotifiers < CLOSURE_MAX_N_INOTIFIERS' failed` when 'Zoom' a11y feature enabled Status in GNOME Shell: New Status in gjs package in Ubuntu: New Bug description: gnome-shell logs gnome-shell[4537]: g_closure_add_invalidate_notifier: assertion 'closure->n_inotifiers < CLOSURE_MAX_N_INOTIFIERS' failed multiple times per second for weeks now. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: gnome-shell 44.3-1ubuntu1 ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5 Uname: Linux 6.3.0-7-generic x86_64 ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: GNOME Date: Thu Aug 10 10:38:23 2023 DisplayManager: gdm3 InstallationDate: Installed on 2022-11-26 (256 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20221126) RelatedPackageVersions: mutter-common 44.3-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/2030947/+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 2048759] Re: After reformatting USB many times why is there a large /media/norvel/UbuntuFilesXE on computer?
By burnout or overload of USB I mean I like stored more than that 2.1TB stick could hold and if it helps it is now a drive not recognized as being there to an extent of being usable but recognized as existing maybe or maybe not, maybe. -- 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/2048759 Title: After reformatting USB many times why is there a large /media/norvel/UbuntuFilesXE on computer? Status in gnome-disk-utility package in Ubuntu: Opinion Bug description: I reformatted to NTFS on another computer, I then reformatted to ext4, could not write, then reformatted some and some took ownership, almost always "read only". After all that and always naming it "UbuntuFilesXE" I have a large /media/norvel/UbuntuFilesXE part of like my system. It is root owned and grouped and is over 228GB and rest of like my system is near 40GB now. It is like it is a mounted USB but it is entirely ON like my computer. I was formatting between ext4 and NTFS only on like my Ubuntu 22.04.3 LTS desktop on a Lenovo Thinkpad T460. I would like to remove this large storage hog but do not know if it is safe to remove. I have had a freshly formatted AND owned USB named like I mentioned be like "read only" with this. I have a 64 bit OS. I expected to have only USB formatted or changed with minimal computer storage impact, not this. gnome-disk-utility: Installed: 42.0-1ubuntu1 Candidate: 42.0-1ubuntu1 Version table: *** 42.0-1ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 Packages 100 /var/lib/dpkg/status All as per one might be maybe or might not be maybe, maybe or maybe not, maybe. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-disk-utility 42.0-1ubuntu1 ProcVersionSignature: Ubuntu 6.2.0-39.40~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-39-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckMismatches: ./boot/grub/grub.cfg ./boot/grub/loopback.cfg CasperMD5CheckResult: fail CurrentDesktop: ubuntu:GNOME Date: Tue Jan 9 03:53:54 2024 InstallationDate: Installed on 2023-12-20 (20 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-disk-utility UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-disk-utility/+bug/2048759/+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 2048792] [NEW] Firefox utilizins 100% of station CPU
Public bug reported: At a high level, in certain instances we’re experiencing sustained abnormally high (100%) CPU utilization from Firefox. This utilization is competing with other critical application processes on the systems, starving them of resources, causing issues in the application processing. This happens, at times, when the browser should be idle, even. We have not isolated this issue to be a bug with firefox itself or an issue with the webpage content being provided to the browser. Regardless, here are the symptoms: * CPU usage is extremely high for the FireFox process (>100% on average vs <10% average for healthy stations) even while the screen is sitting idle (no animations, user interactions, etc.) * We have isolated the thread within FireFox causing the most CPU usage to the Renderer thread with the SwComposite threads also consuming abnormally high CPU. * In the FireFox Task and Process Managers, we have validated there is no single tab or window consuming abnormally high CPU, just the FireFox master process. * Additionally, we have confirmed that the FireFox browser history (taken from the places.sqlite file) does not have any webpages being loaded during the times when CPU consumption experiences a step function change up or down. * We also have linux perf logs for the FireFox process on healthy stations and impacted stations while sitting idle on the login screen, which can provide some stack traces for the Renderer and other threads which may be more useful to someone with FireFox expertise. * The biggest difference is that the impacted workcells have the Renderer and Compositor 'tracks' very active while the healthy workcells see no usage of these tracks at all. * These 2 tracks also have supporting tracks such as SwComposite and WRRendererBackend#X. There were 2 of each of these, which may indicate the issue is happening across both FireFox windows. For reference, the stations always have 2 windows open: one for the screen UI and one for the projector on the pod face. * (Using the term 'track' here as defined by the open source FireFox profiler: https://profiler.firefox.com/. Basically a thread within the FireFox main process) * There are many memory copy and SW interrupt calls being made in these tracks. * This validates that FireFox is contributing to increased software interrupt load * Additionally, we found an interesting pair of calls occurring periodically in the Renderer track. We have not deep dived these yet, but on the off chance it matters, we're including it in this report: * viaduct_log_error - every 50 - 500ms * wgpu_render_pass_end_pipeline_statistics_query - every 50 - 1000ms ** Affects: firefox (Ubuntu) Importance: Undecided Status: New -- 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/2048792 Title: Firefox utilizins 100% of station CPU Status in firefox package in Ubuntu: New Bug description: At a high level, in certain instances we’re experiencing sustained abnormally high (100%) CPU utilization from Firefox. This utilization is competing with other critical application processes on the systems, starving them of resources, causing issues in the application processing. This happens, at times, when the browser should be idle, even. We have not isolated this issue to be a bug with firefox itself or an issue with the webpage content being provided to the browser. Regardless, here are the symptoms: * CPU usage is extremely high for the FireFox process (>100% on average vs <10% average for healthy stations) even while the screen is sitting idle (no animations, user interactions, etc.) * We have isolated the thread within FireFox causing the most CPU usage to the Renderer thread with the SwComposite threads also consuming abnormally high CPU. * In the FireFox Task and Process Managers, we have validated there is no single tab or window consuming abnormally high CPU, just the FireFox master process. * Additionally, we have confirmed that the FireFox browser history (taken from the places.sqlite file) does not have any webpages being loaded during the times when CPU consumption experiences a step function change up or down. * We also have linux perf logs for the FireFox process on healthy stations and impacted stations while sitting idle on the login screen, which can provide some stack traces for the Renderer and other threads which may be more useful to someone with FireFox expertise. * The biggest difference is that the impacted workcells have the Renderer and Compositor 'tracks' very active while the healthy workcells see no usage of these tracks at all. * These 2 tracks also have supporting tracks such as SwComposite and WRRendererBackend#X. There were 2 of each of these, which may indicate the issue
[Desktop-packages] [Bug 2016925] Re: [amdgpu] Firefox window is visually corrupted after upgrading to Ubuntu 23.04
This issue was fixed a couple of months later in a regular update. I'm on 23.10 now on the same machine and haven't had any problems with snaps since. The issue can be closed as far as I am concerned. -- 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/2016925 Title: [amdgpu] Firefox window is visually corrupted after upgrading to Ubuntu 23.04 Status in firefox package in Ubuntu: Confirmed Bug description: After upgrading from Ubuntu 22.10 to Ubuntu 23.04, every time I open firefox the windows is heavily visually corrupted. It seems to work fine under the corruption, but it is completely unusuable. The tar version of Firefox works fine. In the attached screenshot you can see the snap version of Firefox (corrupted) and the tar version of Firefox (working fine). I tried uninstalling (with --purge) and reinstalling and refreshing firefox to no avail. All other applications, including 3D games, are working fine. I am using an AMD RX5500 with default mesa drivers. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: firefox 1:1snap1-0ubuntu3 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Apr 18 18:04:26 2023 InstallationDate: Installed on 2020-11-04 (895 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) SnapChanges: IDEstado Generado Listo Resumen 1215 Done2023-04-18T17:42:17-03:00 2023-04-18T17:44:05-03:00 Eliminar snap "firefox" 1216 Done2023-04-18T17:45:37-03:00 2023-04-18T17:47:25-03:00 Instalar snap "firefox" 1217 Done2023-04-18T17:48:16-03:00 2023-04-18T17:48:30-03:00 Eliminar snap "firefox" 1218 Done2023-04-18T17:48:39-03:00 2023-04-18T17:48:49-03:00 Instalar snap "firefox" SourcePackage: firefox UpgradeStatus: Upgraded to lunar on 2023-04-18 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/2016925/+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 2048759] Re: After reformatting USB many times why is there a large /media/norvel/UbuntuFilesXE on computer?
I now remember I got USBs at time of reinstalling OS. That means that all USB operations were after reinstalling. I now think order was reinstall OS, check size, reformat USB, rsync to USB and burn out, then reformatting another USB and checking. Feel free to check like my logs on this but I think nothing to see here except like my own stupidity and lack of memory. All as per one might be maybe or might not be maybe, maybe or maybe not, maybe. ** Changed in: gnome-disk-utility (Ubuntu) Status: New => Opinion -- 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/2048759 Title: After reformatting USB many times why is there a large /media/norvel/UbuntuFilesXE on computer? Status in gnome-disk-utility package in Ubuntu: Opinion Bug description: I reformatted to NTFS on another computer, I then reformatted to ext4, could not write, then reformatted some and some took ownership, almost always "read only". After all that and always naming it "UbuntuFilesXE" I have a large /media/norvel/UbuntuFilesXE part of like my system. It is root owned and grouped and is over 228GB and rest of like my system is near 40GB now. It is like it is a mounted USB but it is entirely ON like my computer. I was formatting between ext4 and NTFS only on like my Ubuntu 22.04.3 LTS desktop on a Lenovo Thinkpad T460. I would like to remove this large storage hog but do not know if it is safe to remove. I have had a freshly formatted AND owned USB named like I mentioned be like "read only" with this. I have a 64 bit OS. I expected to have only USB formatted or changed with minimal computer storage impact, not this. gnome-disk-utility: Installed: 42.0-1ubuntu1 Candidate: 42.0-1ubuntu1 Version table: *** 42.0-1ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 Packages 100 /var/lib/dpkg/status All as per one might be maybe or might not be maybe, maybe or maybe not, maybe. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-disk-utility 42.0-1ubuntu1 ProcVersionSignature: Ubuntu 6.2.0-39.40~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-39-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckMismatches: ./boot/grub/grub.cfg ./boot/grub/loopback.cfg CasperMD5CheckResult: fail CurrentDesktop: ubuntu:GNOME Date: Tue Jan 9 03:53:54 2024 InstallationDate: Installed on 2023-12-20 (20 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-disk-utility UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-disk-utility/+bug/2048759/+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 2035076] Re: Can't enter capital accented letters with Caps Lock on Wayland
@lastexile7gr The package doesn't come automatically with the updates, you have to pass "-t mantic-proposed" when using apt. This is the command I've used to update the mutter package in my system: sudo apt install mutter-common -t mantic-proposed -- 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/2035076 Title: Can't enter capital accented letters with Caps Lock on Wayland Status in Mutter: Fix Released Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Mantic: Fix Committed Status in mutter package in Fedora: Unknown Bug description: Impact -- Capital accented letters can't be entered using CAPS LOCK in the Wayland session Test Case - Open a terminal and install basic French support: sudo apt install language-pack-gnome-fr Open the Settings app. In the sidebar, click Keyboard Click +, choose French (France), then choose the French (AZERTY) keyboard Close the Settings app In the top right of the screen, click en and switch the keyboard layout to French (AZERTY) In the text editor, type é (this is the number 2 key on a US English keyboard). Now, press the Caps Lock key to enable Caps Lock. Press the same key. You should get É What Could Go Wrong --- This fix is included in mutter 45.2 so see the master bug for this upstream update: LP: #2043000 Original bug report --- Most programs don't recognize Italian accented capital letters. When "Caps Lock" is on àèìòù should be written as ÀÈÌÒÙ... but for some reasons they are not capitalized. I've noticed that everything works fine using the Live session which still uses X11 session. It looks there's no problem with programs that use xwayland like Gimp and MarkText. WORKAROUND === In "Settings -> Keyboard" it's possible to set a "compose key". For example I've selected the [Super left] key. If I want to compose È I press and immediately release each key: [Super left] + [E] + [Alt Gr] + ['] If you want É: [Super left] + [E] + ['] Do the same for the other vowels. === ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: gnome-text-editor 45~beta-1 ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5 Uname: Linux 6.3.0-7-generic x86_64 ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Sep 11 11:48:41 2023 InstallationDate: Installed on 2023-09-07 (4 days ago) InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230906.3) ProcEnviron: LANG=it_IT.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: gnome-text-editor UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/2035076/+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 2037604] Re: Backport packages for 22.04.4 HWE stack
i guess rebuilding gnome snaps with proposed on arm64 and testing that new gnome snap on mantic for pi5 & x1s would help. -- 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/2037604 Title: Backport packages for 22.04.4 HWE stack Status in directx-headers package in Ubuntu: Invalid Status in mesa package in Ubuntu: Invalid Status in rust-bindgen package in Ubuntu: Invalid Status in rust-clang-sys package in Ubuntu: Invalid Status in directx-headers source package in Jammy: Fix Committed Status in mesa source package in Jammy: Fix Committed Status in rust-bindgen source package in Jammy: Invalid Status in rust-clang-sys source package in Jammy: Invalid Bug description: [Impact] The graphics HWE stack from mantic needs to be backported for 22.04.4 directx-headers - build-dep of the new Mesa mesa - new major release (23.2.x) - new HW support, Meteor Lake.. [Test case] We want to cover at least 2-3 different, widely used and already previously supported GPU generations from both AMD and Intel which are supported by this release, as those are the ones that cover most bases; nouveau users tend to switch to the NVIDIA blob after installation. No need to test ancient GPU's supported by mesa-amber. And best to focus on the newer generations (~5y and newer) as the older ones are less likely to break at this point. - AMD: Vega, Navi1x (RX5000*), Navi2x (RX6000*), Navi3x (RX7000*) - Intel: gen9 (SKL/APL/KBL/CFL/WHL/CML), gen11 (ICL), gen12 (TGL/RKL/RPL/DG2) Install the new packages and run some tests: - check that the desktop is still using hw acceleration and hasn't fallen back to swrast/llvmpipe - run freely available benchmarks that torture the GPU (Unigine Heaven/Valley/Superposition) - run some games from Steam if possible and in each case check that there is no gfx corruption happening or worse. Note that upstream releases have already been tested for OpenGL and Vulkan conformance by their CI. [Where things could go wrong] This is a major update of Mesa, there could be regressions but we'll try to catch any with testing. And since it shares bugs with mantic, we'd already know if there are serious issues. We will backport the final 23.2.x at a later stage, the first backport is needed for enabling Intel Meteor Lake. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/directx-headers/+bug/2037604/+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 2047579] Re: gnome-software unuable to install updates (Prepared update not found)
Thanks for the idea, however I give up with this 'bug', I will upgrade this laptop to Xubuntu 23.10 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/2047579 Title: gnome-software unuable to install updates (Prepared update not found) Status in gnome-software package in Ubuntu: New Bug description: Click on 'Software' then 'Updates' then on 'Download' then 'Restart & Update' I have a error message: 'Unable to install updates: Prepared update not found:/var/lib/PackageKit/prepared-update' lsb_release -a : 'Ubuntu 22.04.3 LTS' (however this is Xubuntu 22.04.3). apt-cache policy gnome-software: installed 41.5-2ubuntu2 Note: My bug report seems very similar to bug #1900167 opened in october 2020 by a other user (on Ubuntu 20.10). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-software 41.5-2ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-39.40~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-39-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: XFCE Date: Wed Dec 27 17:36:48 2023 InstallationDate: Installed on 2023-03-27 (275 days ago) InstallationMedia: Xubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) InstalledPlugins: gnome-software-plugin-flatpak N/A gnome-software-plugin-snap41.5-2ubuntu2 SourcePackage: gnome-software UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/2047579/+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 2037604] Re: Backport packages for 22.04.4 HWE stack
unigine tests take no parameters, just launch and run -- 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/2037604 Title: Backport packages for 22.04.4 HWE stack Status in directx-headers package in Ubuntu: Invalid Status in mesa package in Ubuntu: Invalid Status in rust-bindgen package in Ubuntu: Invalid Status in rust-clang-sys package in Ubuntu: Invalid Status in directx-headers source package in Jammy: Fix Committed Status in mesa source package in Jammy: Fix Committed Status in rust-bindgen source package in Jammy: Invalid Status in rust-clang-sys source package in Jammy: Invalid Bug description: [Impact] The graphics HWE stack from mantic needs to be backported for 22.04.4 directx-headers - build-dep of the new Mesa mesa - new major release (23.2.x) - new HW support, Meteor Lake.. [Test case] We want to cover at least 2-3 different, widely used and already previously supported GPU generations from both AMD and Intel which are supported by this release, as those are the ones that cover most bases; nouveau users tend to switch to the NVIDIA blob after installation. No need to test ancient GPU's supported by mesa-amber. And best to focus on the newer generations (~5y and newer) as the older ones are less likely to break at this point. - AMD: Vega, Navi1x (RX5000*), Navi2x (RX6000*), Navi3x (RX7000*) - Intel: gen9 (SKL/APL/KBL/CFL/WHL/CML), gen11 (ICL), gen12 (TGL/RKL/RPL/DG2) Install the new packages and run some tests: - check that the desktop is still using hw acceleration and hasn't fallen back to swrast/llvmpipe - run freely available benchmarks that torture the GPU (Unigine Heaven/Valley/Superposition) - run some games from Steam if possible and in each case check that there is no gfx corruption happening or worse. Note that upstream releases have already been tested for OpenGL and Vulkan conformance by their CI. [Where things could go wrong] This is a major update of Mesa, there could be regressions but we'll try to catch any with testing. And since it shares bugs with mantic, we'd already know if there are serious issues. We will backport the final 23.2.x at a later stage, the first backport is needed for enabling Intel Meteor Lake. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/directx-headers/+bug/2037604/+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 2043027] Re: Wacom Intuos S stop working after upgrading to Ubuntu 23.10
I agree that there is an issue with making it difficult for people to
easily and fully test -proposed updates.
I wrote a blog post about the way I install packages from -proposed.
Steps 0-3
https://jeremy.bicha.net/2022/03/29/how-to-install-a-bunch-of-debs/
--
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/2043027
Title:
Wacom Intuos S stop working after upgrading to Ubuntu 23.10
Status in mutter package in Ubuntu:
Fix Released
Status in mutter source package in Mantic:
Fix Committed
Bug description:
Impact
--
Clicking does not work correctly with Wacom tablets in the Ubuntu/GNOME X11
sessions
Test Case
-
One of the people affected by this issue will verify whether their Wacom
tablet is working noticably better with the upgraded Mutter packages
What Could Go Wrong
---
The fix for this issue is included in upstream's mutter 45.2 release so
please see bug 2043000 as the master bug for this upgrade
Original Bug Report
---
Tablet seems to work until I open Krita (as I could read on Internet, it may
be related with Qt Apps).
When Krita is open, mouse movement works ok with the tablet, but when
it comes to click action it doesn't work and any further action with
mouse is not captured (even outside Krita!).
To regain control of the mouse I have to Alt+Tab and then I can click
again.
Some details that may be handy:
- I've got two monitors
- Maybe Qt apps related
- My graphic card is nVidia GTX 1060 6Gb, driver used nvidia-driver-535
Thanks for your effort. I love Ubuntu!
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
Uname: Linux 6.5.0-10-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
.proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
.proc.driver.nvidia.gpus..06.00.0: Error: path was not a regular file.
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.suspend: suspend hibernate resume
.proc.driver.nvidia.suspend_depth: default modeset uvm
.proc.driver.nvidia.version:
NVRM version: NVIDIA UNIX x86_64 Kernel Module 535.129.03 Thu Oct 19
18:56:32 UTC 2023
GCC version:
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
BootLog: Error: [Errno 13] Permiso denegado: '/var/log/boot.log'
CasperMD5CheckResult: unknown
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Wed Nov 8 17:20:34 2023
DistUpgraded: 2023-11-08 00:54:28,961 DEBUG Running PostInstallScript:
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
DistroCodename: mantic
DistroVariant: ubuntu
DkmsStatus:
nvidia/535.129.03, 6.2.0-36-generic, x86_64: installed (WARNING! Diff
between built and installed module!) (WARNING! Diff between built and installed
module!) (WARNING! Diff between built and installed module!) (WARNING! Diff
between built and installed module!) (WARNING! Diff between built and installed
module!)
nvidia/535.129.03, 6.5.0-10-generic, x86_64: installed (WARNING! Diff
between built and installed module!) (WARNING! Diff between built and installed
module!) (WARNING! Diff between built and installed module!) (WARNING! Diff
between built and installed module!) (WARNING! Diff between built and installed
module!)
virtualbox/7.0.10, 6.2.0-36-generic, x86_64: installed
virtualbox/7.0.10, 6.5.0-10-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
NVIDIA Corporation GP106 [GeForce GTX 1060 6GB] [10de:1c03] (rev a1)
(prog-if 00 [VGA controller])
Subsystem: ZOTAC International (MCO) Ltd. GP106 [GeForce GTX 1060 6GB]
[19da:1438]
InstallationDate: Installed on 2022-04-09 (578 days ago)
InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcEnviron:
LANG=es_ES.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
XDG_RUNTIME_DIR=
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-10-generic
root=UUID=9dd904a0-11bb-40fa-9fe8-2f10449a416c ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to mantic on 2023-11-07 (1 days ago)
dmi.bios.date: 06/15/2020
dmi.bios.release: 5.17
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0608
dmi.board.asset.tag: Default string
dmi.board.name: TUF GAMING B550-PLUS
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev X.0x
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias:
[Desktop-packages] [Bug 2037604] Re: Backport packages for 22.04.4 HWE stack
Can somebody modify the description to specify exactly how to do those tests, please? (which commands/parameters, and expected results). -- 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/2037604 Title: Backport packages for 22.04.4 HWE stack Status in directx-headers package in Ubuntu: Invalid Status in mesa package in Ubuntu: Invalid Status in rust-bindgen package in Ubuntu: Invalid Status in rust-clang-sys package in Ubuntu: Invalid Status in directx-headers source package in Jammy: Fix Committed Status in mesa source package in Jammy: Fix Committed Status in rust-bindgen source package in Jammy: Invalid Status in rust-clang-sys source package in Jammy: Invalid Bug description: [Impact] The graphics HWE stack from mantic needs to be backported for 22.04.4 directx-headers - build-dep of the new Mesa mesa - new major release (23.2.x) - new HW support, Meteor Lake.. [Test case] We want to cover at least 2-3 different, widely used and already previously supported GPU generations from both AMD and Intel which are supported by this release, as those are the ones that cover most bases; nouveau users tend to switch to the NVIDIA blob after installation. No need to test ancient GPU's supported by mesa-amber. And best to focus on the newer generations (~5y and newer) as the older ones are less likely to break at this point. - AMD: Vega, Navi1x (RX5000*), Navi2x (RX6000*), Navi3x (RX7000*) - Intel: gen9 (SKL/APL/KBL/CFL/WHL/CML), gen11 (ICL), gen12 (TGL/RKL/RPL/DG2) Install the new packages and run some tests: - check that the desktop is still using hw acceleration and hasn't fallen back to swrast/llvmpipe - run freely available benchmarks that torture the GPU (Unigine Heaven/Valley/Superposition) - run some games from Steam if possible and in each case check that there is no gfx corruption happening or worse. Note that upstream releases have already been tested for OpenGL and Vulkan conformance by their CI. [Where things could go wrong] This is a major update of Mesa, there could be regressions but we'll try to catch any with testing. And since it shares bugs with mantic, we'd already know if there are serious issues. We will backport the final 23.2.x at a later stage, the first backport is needed for enabling Intel Meteor Lake. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/directx-headers/+bug/2037604/+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 1993127] Re: /usr/bin/nautilus:11:g_list_store_find_with_equal_func_full:g_list_store_find_with_equal_func:g_list_store_find:nautilus_view_model_get_index:scroll_to_file_on_idl
** Changed in: nautilus (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1993127 Title: /usr/bin/nautilus:11:g_list_store_find_with_equal_func_full:g_list_store_find_with_equal_func:g_list_store_find:nautilus_view_model_get_index:scroll_to_file_on_idle Status in Nautilus: Fix Released Status in nautilus package in Ubuntu: Fix Released Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding nautilus. This problem was most recently seen with package version 1:43.0-1ubuntu1, the problem page at https://errors.ubuntu.com/problem/32454f0bde038596049406d7ad99e47263fb8bf7 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1993127/+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 2037528] Re: every tab with touchscreen on a folder gives the context menu.
Upstream: https://gitlab.gnome.org/GNOME/nautilus/-/issues/2872 ** Bug watch added: gitlab.gnome.org/GNOME/nautilus/-/issues #2872 https://gitlab.gnome.org/GNOME/nautilus/-/issues/2872 ** Changed in: nautilus (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/2037528 Title: every tab with touchscreen on a folder gives the context menu. Status in nautilus package in Ubuntu: Confirmed Bug description: Ubuntu installed on Chuwi u-book x pro (13 inch). CPU: Intel® Core™ i7-7Y75 × 4 GPU: Intel® HD Graphics 615 (KBL GT2) Tapping a folder in Nautilus always gives the context menu. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: nautilus 1:44.2.1-0ubuntu1 ProcVersionSignature: Ubuntu 6.2.0-33.33-generic 6.2.16 Uname: Linux 6.2.0-33-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Sep 27 12:08:40 2023 GsettingsChanges: b'org.gnome.nautilus.preferences' b'click-policy' b"'single'" b'org.gnome.nautilus.preferences' b'migrated-gtk-settings' b'true' b'org.gnome.nautilus.window-state' b'maximized' b'true' InstallationDate: Installed on 2023-09-19 (7 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: file-roller 43.0-1 nautilus-extension-gnome-terminal 3.48.0-1ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2037528/+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 2048569] Re: rightclick->open link doesn't work on file://full/path/filename.cpp:linenumber links
What we _could_ perhaps do (because detecting a URI in a text flow is undefined territory, with already quite a few quirks in place, such as stripping off the trailing dot) is to strip off the trailing ":linenumber". That is, the trailing ":" if it's followed by numbers only. That way you could easily and quickly open the desired file "filename.cpp". Not at the desired position, though. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/2048569 Title: rightclick->open link doesn't work on file://full/path/filename.cpp:linenumber links Status in gnome-terminal package in Ubuntu: New Bug description: TLDR: I want to be able to open links like file:///full/path/to/filename.cpp:linenumber with rightclick open link video explanation: https://youtu.be/PmQAx7HF7_c ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-terminal 3.44.0-1ubuntu1 ProcVersionSignature: Ubuntu 6.2.0-39.40~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-39-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Jan 8 14:05:15 2024 InstallationDate: Installed on 2022-05-05 (612 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) SourcePackage: gnome-terminal UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/2048569/+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 1685484] Re: DHCP exit hook for setting systemd-timesyncd NTP servers doesn't work
To ubuntu 22.04, I refer to
https://roll.urown.net/desktop/network/time-sync.html.
Using NM's dispatch scripts, NetworkManager can talk with timesyncd when
configuring to use internal dhcp client.
If want to use dhclient's hook, I think you should configure NetworkManager to
use dhclient.
[main]
dhcp=dhclient
I don't test it, just for your reference.
--
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/1685484
Title:
DHCP exit hook for setting systemd-timesyncd NTP servers doesn't work
Status in network-manager package in Ubuntu:
Confirmed
Status in systemd package in Ubuntu:
Won't Fix
Status in systemd package in Debian:
Fix Released
Bug description:
I think it's regression for
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1578663 in
zesty.
1. NTP servers are send via DHCP and seen by NM:
$ nmcli con show connection1 | grep ntp
DHCP4.OPTION[30]: requested_ntp_servers = 1
DHCP4.OPTION[31]: ntp_servers = 80.50.231.226
217.96.29.26 212.160.106.226
2. timesyncd is using hardcoded default NTP server:
$ systemctl -n 200 status systemd-timesyncd.service
* systemd-timesyncd.service - Network Time Synchronization
Loaded: loaded (/lib/systemd/system/systemd-timesyncd.service; enabled;
vendor preset: enabled)
Drop-In: /lib/systemd/system/systemd-timesyncd.service.d
`-disable-with-time-daemon.conf
Active: active (running) since Sat 2017-04-22 13:12:23 CEST; 16min ago
Docs: man:systemd-timesyncd.service(8)
Main PID: 576 (systemd-timesyn)
Status: "Synchronized to time server 91.189.89.199:123 (ntp.ubuntu.com)."
Tasks: 2 (limit: 4915)
Memory: 1.5M
CPU: 20ms
CGroup: /system.slice/systemd-timesyncd.service
`-576 /lib/systemd/systemd-timesyncd
Apr 22 13:12:23 slodki systemd[1]: Starting Network Time Synchronization...
Apr 22 13:12:23 slodki systemd[1]: Started Network Time Synchronization.
Apr 22 13:12:53 slodki systemd-timesyncd[576]: Synchronized to time server
91.189.89.199:123 (ntp.ubuntu.com).
3. There are not other time sync deamons installed:
$ cat
/lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf
[Unit]
# don't run timesyncd if we have another NTP daemon installed
ConditionFileIsExecutable=!/usr/sbin/ntpd
ConditionFileIsExecutable=!/usr/sbin/openntpd
ConditionFileIsExecutable=!/usr/sbin/chronyd
ConditionFileIsExecutable=!/usr/sbin/VBoxService
$ ls -l /usr/sbin/{ntpd,openntpd,chronyd,VBoxService}
ls: cannot access '/usr/sbin/ntpd': No such file or directory
ls: cannot access '/usr/sbin/openntpd': No such file or directory
ls: cannot access '/usr/sbin/chronyd': No such file or directory
ls: cannot access '/usr/sbin/VBoxService': No such file or directory
4. There is only one default timesyncd.conf file with default values:
$ sudo find / -iname \*timesync\*
/etc/systemd/timesyncd.conf
/etc/systemd/system/sysinit.target.wants/systemd-timesyncd.service
/etc/dhcp/dhclient-exit-hooks.d/timesyncd
/usr/share/man/man5/timesyncd.conf.d.5.gz
/usr/share/man/man5/timesyncd.conf.5.gz
/usr/share/man/man8/systemd-timesyncd.8.gz
/usr/share/man/man8/systemd-timesyncd.service.8.gz
/tmp/systemd-private-d029f63116924e99b9fc44caf622e299-systemd-timesyncd.service-6NwdRT
/lib/systemd/systemd-timesyncd
/lib/systemd/system/systemd-timesyncd.service
/lib/systemd/system/systemd-timesyncd.service.d
/var/tmp/systemd-private-d029f63116924e99b9fc44caf622e299-systemd-timesyncd.service-jz0q47
$ cat /etc/systemd/timesyncd.conf
# This file is part of systemd.
#
# systemd is free software; you can redistribute it and/or modify it
# under the terms of the GNU Lesser General Public License as published by
# the Free Software Foundation; either version 2.1 of the License, or
# (at your option) any later version.
#
# Entries in this file show the compile time defaults.
# You can change settings by editing this file.
# Defaults can be restored by simply deleting this file.
#
# See timesyncd.conf(5) for details.
[Time]
#NTP=
#FallbackNTP=ntp.ubuntu.com
5. DHCP hook installed as /etc/dhcp/dhclient-exit-hooks.d/timesyncd is
not working,
TIMESYNCD_CONF=/run/systemd/timesyncd.conf.d/01-dhclient.conf is not
created.
6. After manually executing steps from hook all works as expected:
$ sudo mkdir -p /run/systemd/timesyncd.conf.d/
$ sudo cat [Time]
> NTP=80.50.231.226 217.96.29.26 212.160.106.226
> EOF
$ sudo systemctl try-restart systemd-timesyncd.service
$ sudo systemctl status systemd-timesyncd.service
* systemd-timesyncd.service - Network Time Synchronization
Loaded: loaded (/lib/systemd/system/systemd-timesyncd.service; enabled;
vendor preset: enabled)
[Desktop-packages] [Bug 2048569] Re: rightclick->open link doesn't work on file://full/path/filename.cpp:linenumber links
The problem is: according to the URI specification, there is no way to denote the line number. In fact, the URI "file:///full/path/to/filename.cpp:linenumber" refers to a file whose name is literally "filename.cpp:linenumber". Correspondingly, the entire stack that handles the opening of a URI (the gtk_show_uri() method and anything that's underneath it) doesn't know the concept of line number either. Think of all the .desktop and similar files shipped by text editors and similar software, currently they are unable to specify how to pass on the line number to them. Getting it modified to support line numbers would require to modify GTK, modify the .desktop file specification, and _all_ the software out there that ship such a .desktop file, that is, practically all the text viewers/editors out there, to conform to a nonstandard (and backwards incompatible!) extension of the URI specification. This is clearly not going to happen. In order to move forward, first the URI specification would have to be modified to introduce the concept of line number. In a backwards compatible way, that is, the ':' character is out of question, it would need to go to '?query' or '#fragment', probably the latter. Also figure out what to do if the file is in any other format than plain text (what would the given field mean for pdf (page number?), png, music/video (time offset?) etc.) How to distinguish opening an html file as a rendered page (when '#fragment' jumps to the corresponding 'a name' or 'id') vs. opening an html file as raw text (and then jumping to the given line number)? Then the remaining software components would one by one need to be updated to this spec. This was also discussed in the user comments in the gist page of the explicit hyperlink feature for terminals, and was similarly inconclusive. Unfortunately, it's practically a WONTFIX. You can probably use the nonstandard wrapper that you created for Qt Creator for GNOME Terminal as well. Just have a wrapper script that opens your file that handles this ':' and translates to the line number command line parameter of your preferred text viewer/editor. Unfortunately the world is not ready to standardize this personal hack into a mainstream solution, and such a change cannot begin at GNOME Terminal. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/2048569 Title: rightclick->open link doesn't work on file://full/path/filename.cpp:linenumber links Status in gnome-terminal package in Ubuntu: New Bug description: TLDR: I want to be able to open links like file:///full/path/to/filename.cpp:linenumber with rightclick open link video explanation: https://youtu.be/PmQAx7HF7_c ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-terminal 3.44.0-1ubuntu1 ProcVersionSignature: Ubuntu 6.2.0-39.40~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-39-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Jan 8 14:05:15 2024 InstallationDate: Installed on 2022-05-05 (612 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) SourcePackage: gnome-terminal UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/2048569/+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 2043027] Re: Wacom Intuos S stop working after upgrading to Ubuntu 23.10
First, thank you to Jeremy Bicha and Steve Langasek, and anyone else involved in bringing the update to mutter. I've been trying for the past few days to install the update. I enabled -proposed, but every time I try to install the newer version of mutter (whether directly by the version name, or by "mantic-proposed", I get this message: The following packages have unmet dependencies: mutter : Depends: mutter-common (>= 45.2-0ubuntu3) but 45.2-0ubuntu2~really45.0 is installed The set of fixes does not include updating mutter-common; when I check versions in aptitude, it does not list that version. I've tried uninstalling both mutter and mutter-common, but when I go to reinstall, it all defaults back to the 45.2-0ubuntu2~really45.0 versions. While I do see 45.2-0ubuntu3 in the list of versions for mutter, mutter-common only lists the version I have installed. All that said, I know that the seven-day window will soon pass, and maybe this will just become part of the regular updates; however, if this problem has prevented others from testing, my guess is that it will hold things up until there's been direct verification. I realize this thread is not for support for this type of problem -- i.e., there may just be some command I'm not familiar with that would resolve this whole thing, and so there may be no larger issue at all other than my own lack of experience -- but I wanted to mention this in case it isn't just me. I would be happy to install and test the new package, but until either mutter-common is also updated, or I can find out what I'm doing wrong, I can't provide any more feedback. -- 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/2043027 Title: Wacom Intuos S stop working after upgrading to Ubuntu 23.10 Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Mantic: Fix Committed Bug description: Impact -- Clicking does not work correctly with Wacom tablets in the Ubuntu/GNOME X11 sessions Test Case - One of the people affected by this issue will verify whether their Wacom tablet is working noticably better with the upgraded Mutter packages What Could Go Wrong --- The fix for this issue is included in upstream's mutter 45.2 release so please see bug 2043000 as the master bug for this upgrade Original Bug Report --- Tablet seems to work until I open Krita (as I could read on Internet, it may be related with Qt Apps). When Krita is open, mouse movement works ok with the tablet, but when it comes to click action it doesn't work and any further action with mouse is not captured (even outside Krita!). To regain control of the mouse I have to Alt+Tab and then I can click again. Some details that may be handy: - I've got two monitors - Maybe Qt apps related - My graphic card is nVidia GTX 1060 6Gb, driver used nvidia-driver-535 Thanks for your effort. I love Ubuntu! ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3 Uname: Linux 6.5.0-10-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..06.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 535.129.03 Thu Oct 19 18:56:32 UTC 2023 GCC version: ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 BootLog: Error: [Errno 13] Permiso denegado: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Nov 8 17:20:34 2023 DistUpgraded: 2023-11-08 00:54:28,961 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: mantic DistroVariant: ubuntu DkmsStatus: nvidia/535.129.03, 6.2.0-36-generic, x86_64: installed (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) nvidia/535.129.03, 6.5.0-10-generic, x86_64: installed (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) virtualbox/7.0.10, 6.2.0-36-generic, x86_64: installed virtualbox/7.0.10, 6.5.0-10-generic,
[Desktop-packages] [Bug 1928867] Re: System freeze on bulk rename
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 nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1928867 Title: System freeze on bulk rename Status in gnome-shell package in Ubuntu: Invalid Status in nautilus package in Ubuntu: Confirmed Bug description: Ubuntu 20.04 Nautilus 1:3.36.3-0ubuntu1 Bug: I have 8 files named as file-1.jpg, file-2.jpg, ... file-8.jpg When I select them all and rename using template as 'file-[1, 2, 3]' in descending order, the system freezes. Perhaps because the files already exist with same name? I was expecting the files to be renamed in descending series - file-1.jpg as file-8.jpg, file-2.jpg as file-7.jpg and so on.. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: nautilus 1:3.36.3-0ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-53.60~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-53-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.17 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed May 19 00:44:49 2021 GsettingsChanges: b'org.gnome.nautilus.window-state' b'sidebar-width' b'161' b'org.gnome.nautilus.window-state' b'initial-size' b'(891, 546)' InstallationDate: Installed on 2020-04-24 (389 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1928867/+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 1928867] Re: System freeze on bulk rename
** Changed in: gnome-shell (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1928867 Title: System freeze on bulk rename Status in gnome-shell package in Ubuntu: Invalid Status in nautilus package in Ubuntu: Confirmed Bug description: Ubuntu 20.04 Nautilus 1:3.36.3-0ubuntu1 Bug: I have 8 files named as file-1.jpg, file-2.jpg, ... file-8.jpg When I select them all and rename using template as 'file-[1, 2, 3]' in descending order, the system freezes. Perhaps because the files already exist with same name? I was expecting the files to be renamed in descending series - file-1.jpg as file-8.jpg, file-2.jpg as file-7.jpg and so on.. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: nautilus 1:3.36.3-0ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-53.60~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-53-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.17 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed May 19 00:44:49 2021 GsettingsChanges: b'org.gnome.nautilus.window-state' b'sidebar-width' b'161' b'org.gnome.nautilus.window-state' b'initial-size' b'(891, 546)' InstallationDate: Installed on 2020-04-24 (389 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1928867/+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 1928867] Re: System freeze on bulk rename
This is a known upstream bug: https://gitlab.gnome.org/GNOME/nautilus/-/issues/1443 ** Bug watch added: gitlab.gnome.org/GNOME/nautilus/-/issues #1443 https://gitlab.gnome.org/GNOME/nautilus/-/issues/1443 ** Changed in: nautilus (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1928867 Title: System freeze on bulk rename Status in gnome-shell package in Ubuntu: Invalid Status in nautilus package in Ubuntu: Confirmed Bug description: Ubuntu 20.04 Nautilus 1:3.36.3-0ubuntu1 Bug: I have 8 files named as file-1.jpg, file-2.jpg, ... file-8.jpg When I select them all and rename using template as 'file-[1, 2, 3]' in descending order, the system freezes. Perhaps because the files already exist with same name? I was expecting the files to be renamed in descending series - file-1.jpg as file-8.jpg, file-2.jpg as file-7.jpg and so on.. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: nautilus 1:3.36.3-0ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-53.60~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-53-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.17 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed May 19 00:44:49 2021 GsettingsChanges: b'org.gnome.nautilus.window-state' b'sidebar-width' b'161' b'org.gnome.nautilus.window-state' b'initial-size' b'(891, 546)' InstallationDate: Installed on 2020-04-24 (389 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1928867/+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 2047737] Re: Nautilus crashes when opening folders that contain files with js or json extensions
Could you perhaps attach an example of file showing the issue? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/2047737 Title: Nautilus crashes when opening folders that contain files with js or json extensions Status in nautilus package in Ubuntu: Incomplete Bug description: After attempting to open a folder that contains js or json files the app crashes. when testing from terminal I get a segmentation fault and no other error info. even enabling G_MESSAGES_DEBUG=all did not provide additional info. removing nautilus extensions, resetting xdg-mime for js/json, and disabling nautilus features (search, file count, etc ...) did not fix the problem either. additional info $ lsb_release -rd Description:Ubuntu 22.04.3 LTS Release:22.04 $ apt-cache policy nautilus nautilus: Installed: 1:42.6-0ubuntu1 Candidate: 1:42.6-0ubuntu1 Version table: *** 1:42.6-0ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:42.2-0ubuntu2.1 500 500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 Packages 1:42.0-1ubuntu2 500 500 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: nautilus 1:42.6-0ubuntu1 ProcVersionSignature: Ubuntu 6.2.0-39.40~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-39-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Dec 30 14:50:09 2023 InstallationDate: Installed on 2023-02-14 (319 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: evince42.3-0ubuntu3.1 file-roller 3.42.0-1 nautilus-extension-gnome-terminal 3.44.0-1ubuntu1 nautilus-share0.7.3-2ubuntu6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2047737/+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 2047737] Re: Nautilus crashes when opening folders that contain files with js or json extensions
Thank you for taking the time to report this bug and helping to make Ubuntu better. It sounds like some part of the system has crashed. To help us find the cause of the crash please follow these steps: 1. Run these commands: journalctl -b0 > journal.txt journalctl -b-1 > prevjournal.txt and attach the resulting text files here. 2. Look in /var/crash for crash files and if found run: ubuntu-bug YOURFILE.crash Then tell us the ID of the newly-created bug. 3. If step 2 failed then look at https://errors.ubuntu.com/user/ID where ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine. Do you find any links to recent problems on that page? If so then please send the links to us. Please take care to avoid attaching .crash files to bugs as we are unable to process them as file attachments. It would also be a security risk for yourself. ** Changed in: nautilus (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/2047737 Title: Nautilus crashes when opening folders that contain files with js or json extensions Status in nautilus package in Ubuntu: Incomplete Bug description: After attempting to open a folder that contains js or json files the app crashes. when testing from terminal I get a segmentation fault and no other error info. even enabling G_MESSAGES_DEBUG=all did not provide additional info. removing nautilus extensions, resetting xdg-mime for js/json, and disabling nautilus features (search, file count, etc ...) did not fix the problem either. additional info $ lsb_release -rd Description:Ubuntu 22.04.3 LTS Release:22.04 $ apt-cache policy nautilus nautilus: Installed: 1:42.6-0ubuntu1 Candidate: 1:42.6-0ubuntu1 Version table: *** 1:42.6-0ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:42.2-0ubuntu2.1 500 500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 Packages 1:42.0-1ubuntu2 500 500 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: nautilus 1:42.6-0ubuntu1 ProcVersionSignature: Ubuntu 6.2.0-39.40~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-39-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Dec 30 14:50:09 2023 InstallationDate: Installed on 2023-02-14 (319 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: evince42.3-0ubuntu3.1 file-roller 3.42.0-1 nautilus-extension-gnome-terminal 3.44.0-1ubuntu1 nautilus-share0.7.3-2ubuntu6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2047737/+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 2048759] Re: After reformatting USB many times why is there a large /media/norvel/UbuntuFilesXE on computer?
By memory I know I overloaded a 2.1TB USB some time. I had a previous OS by same USB bootable thing and almost same setup. I know I used rsync with no exclude or -x or --one-file-system to overload that USB. I think I overloaded it BEFORE reinstalling OS. I think order was overload USB, reinstall OS, check that OS is 31GB, it was, reformat another USB some and set ownership of that USB some, check size of usage, 251GB, done. I am unsure if overload was after reformat but I am almost certain that I checked and found 251GB BEFORE overload if that happened. Also, with reinstalling I had a bootable USB and another 2.1TB USB plugged in and only one USB option which I took to boot. All as per one might be maybe or might not be maybe, maybe or maybe not, maybe. -- 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/2048759 Title: After reformatting USB many times why is there a large /media/norvel/UbuntuFilesXE on computer? Status in gnome-disk-utility package in Ubuntu: New Bug description: I reformatted to NTFS on another computer, I then reformatted to ext4, could not write, then reformatted some and some took ownership, almost always "read only". After all that and always naming it "UbuntuFilesXE" I have a large /media/norvel/UbuntuFilesXE part of like my system. It is root owned and grouped and is over 228GB and rest of like my system is near 40GB now. It is like it is a mounted USB but it is entirely ON like my computer. I was formatting between ext4 and NTFS only on like my Ubuntu 22.04.3 LTS desktop on a Lenovo Thinkpad T460. I would like to remove this large storage hog but do not know if it is safe to remove. I have had a freshly formatted AND owned USB named like I mentioned be like "read only" with this. I have a 64 bit OS. I expected to have only USB formatted or changed with minimal computer storage impact, not this. gnome-disk-utility: Installed: 42.0-1ubuntu1 Candidate: 42.0-1ubuntu1 Version table: *** 42.0-1ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 Packages 100 /var/lib/dpkg/status All as per one might be maybe or might not be maybe, maybe or maybe not, maybe. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-disk-utility 42.0-1ubuntu1 ProcVersionSignature: Ubuntu 6.2.0-39.40~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-39-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckMismatches: ./boot/grub/grub.cfg ./boot/grub/loopback.cfg CasperMD5CheckResult: fail CurrentDesktop: ubuntu:GNOME Date: Tue Jan 9 03:53:54 2024 InstallationDate: Installed on 2023-12-20 (20 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-disk-utility UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-disk-utility/+bug/2048759/+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 2048759] [NEW] After reformatting USB many times why is there a large /media/norvel/UbuntuFilesXE on computer?
Public bug reported: I reformatted to NTFS on another computer, I then reformatted to ext4, could not write, then reformatted some and some took ownership, almost always "read only". After all that and always naming it "UbuntuFilesXE" I have a large /media/norvel/UbuntuFilesXE part of like my system. It is root owned and grouped and is over 228GB and rest of like my system is near 40GB now. It is like it is a mounted USB but it is entirely ON like my computer. I was formatting between ext4 and NTFS only on like my Ubuntu 22.04.3 LTS desktop on a Lenovo Thinkpad T460. I would like to remove this large storage hog but do not know if it is safe to remove. I have had a freshly formatted AND owned USB named like I mentioned be like "read only" with this. I have a 64 bit OS. I expected to have only USB formatted or changed with minimal computer storage impact, not this. gnome-disk-utility: Installed: 42.0-1ubuntu1 Candidate: 42.0-1ubuntu1 Version table: *** 42.0-1ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 Packages 100 /var/lib/dpkg/status All as per one might be maybe or might not be maybe, maybe or maybe not, maybe. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-disk-utility 42.0-1ubuntu1 ProcVersionSignature: Ubuntu 6.2.0-39.40~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-39-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckMismatches: ./boot/grub/grub.cfg ./boot/grub/loopback.cfg CasperMD5CheckResult: fail CurrentDesktop: ubuntu:GNOME Date: Tue Jan 9 03:53:54 2024 InstallationDate: Installed on 2023-12-20 (20 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-disk-utility UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-disk-utility (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy wayland-session -- 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/2048759 Title: After reformatting USB many times why is there a large /media/norvel/UbuntuFilesXE on computer? Status in gnome-disk-utility package in Ubuntu: New Bug description: I reformatted to NTFS on another computer, I then reformatted to ext4, could not write, then reformatted some and some took ownership, almost always "read only". After all that and always naming it "UbuntuFilesXE" I have a large /media/norvel/UbuntuFilesXE part of like my system. It is root owned and grouped and is over 228GB and rest of like my system is near 40GB now. It is like it is a mounted USB but it is entirely ON like my computer. I was formatting between ext4 and NTFS only on like my Ubuntu 22.04.3 LTS desktop on a Lenovo Thinkpad T460. I would like to remove this large storage hog but do not know if it is safe to remove. I have had a freshly formatted AND owned USB named like I mentioned be like "read only" with this. I have a 64 bit OS. I expected to have only USB formatted or changed with minimal computer storage impact, not this. gnome-disk-utility: Installed: 42.0-1ubuntu1 Candidate: 42.0-1ubuntu1 Version table: *** 42.0-1ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 Packages 100 /var/lib/dpkg/status All as per one might be maybe or might not be maybe, maybe or maybe not, maybe. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-disk-utility 42.0-1ubuntu1 ProcVersionSignature: Ubuntu 6.2.0-39.40~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-39-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckMismatches: ./boot/grub/grub.cfg ./boot/grub/loopback.cfg CasperMD5CheckResult: fail CurrentDesktop: ubuntu:GNOME Date: Tue Jan 9 03:53:54 2024 InstallationDate: Installed on 2023-12-20 (20 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-disk-utility UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-disk-utility/+bug/2048759/+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
