Public bug reported:
I have Ubuntu 22.04 LTS and i have problems to shutdown the Desktop PC,
it tooks very long. The same is if i make a newstart. My log writes
this:
Oct 28 18:16:14 bka gnome-shell[2876]: The offending callback was
set_container(), a vfunc.
Oct 28 18:16:14 bka gnome-shell[2876]: Attempting to call back into JSAPI
during the sweeping phase of GC. This is most likely caused by not destroying a
Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be
caused by using the destroy(), dispose(), or remove() vfuncs. Because it would
crash the application, it has been blocked and the JS callback not invoked.
Oct 28 18:16:14 bka gnome-shell[2876]: The offending signal was destroy on
Gjs_ui_appDisplay_FolderGrid 0x5c4600f79b10.
Oct 28 18:16:14 bka gnome-shell[2876]: Attempting to call back into JSAPI
during the sweeping phase of GC. This is most likely caused by not destroying a
Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be
caused by using the destroy(), dispose(), or remove() vfuncs. Because it would
crash the application, it has been blocked and the JS callback not invoked.
Oct 28 18:16:14 bka gnome-shell[2876]: The offending signal was destroy on
Gjs_ui_appDisplay_FolderGrid 0x5c4600f79b10.
Oct 28 18:16:14 bka gnome-shell[2876]: Attempting to call back into JSAPI
during the sweeping phase of GC. This is most likely caused by not destroying a
Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be
caused by using the destroy(), dispose(), or remove() vfuncs. Because it would
crash the application, it has been blocked and the JS callback not invoked.
Oct 28 18:16:14 bka gnome-shell[2876]: The offending signal was destroy on
Gjs_ui_appDisplay_FolderGrid 0x5c4600f79b10.
Oct 28 18:16:14 bka gnome-shell[2876]: Attempting to call back into JSAPI
during the sweeping phase of GC. This is most likely caused by not destroying a
Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be
caused by using the destroy(), dispose(), or remove() vfuncs. Because it would
crash the application, it has been blocked and the JS callback not invoked.
Oct 28 18:16:14 bka gnome-shell[2876]: The offending signal was destroy on
Gjs_ui_appDisplay_AppIcon 0x5c45fcf85960.
Oct 28 18:16:14 bka gnome-shell[2876]: Attempting to call back into JSAPI
during the sweeping phase of GC. This is most likely caused by not destroying a
Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be
caused by using the destroy(), dispose(), or remove() vfuncs. Because it would
crash the application, it has been blocked and the JS callback not invoked.
Oct 28 18:16:14 bka ModemManager[1503]: <info> ModemManager is shut down
Oct 28 18:16:14 bka gnome-shell[2876]: The offending signal was destroy on
Gjs_ui_appDisplay_AppIcon 0x5c45fcf85960.
Oct 28 18:16:14 bka gnome-shell[2876]: Attempting to call back into JSAPI
during the sweeping phase of GC. This is most likely caused by not destroying a
Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be
caused by using the destroy(), dispose(), or remove() vfuncs. Because it would
crash the application, it has been blocked and the JS callback not invoked.
Oct 28 18:16:14 bka gnome-shell[2876]: The offending signal was destroy on
Gjs_ui_appDisplay_AppIcon 0x5c45fcf85960.
Oct 28 18:16:14 bka gnome-shell[2876]: Attempting to call back into JSAPI
during the sweeping phase of GC. This is most likely caused by not destroying a
Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be
caused by using the destroy(), dispose(), or remove() vfuncs. Because it would
crash the application, it has been blocked and the JS callback not invoked.
Oct 28 18:16:14 bka gnome-shell[2876]: The offending signal was destroy on
Gjs_ui_appDisplay_AppIcon 0x5c45fcf85960.
Oct 28 18:16:14 bka systemd[2667]:
org.gnome.SettingsDaemon.Housekeeping.service: Consumed 1.141s CPU time.
Oct 28 18:16:14 bka systemd[1]: Stopping Session 2 of User herweck...
Oct 28 18:16:14 bka systemd[1]: Removed slice Slice /system/getty.
Oct 28 18:16:14 bka systemd[1]: Removed slice Slice /system/modprobe.
Oct 28 18:16:14 bka systemd[1]: Stopped target Preparation for Logins.
Oct 28 18:16:14 bka systemd[1]: Stopped target Graphical Interface.
Oct 28 18:16:14 bka systemd[1]: Stopped target Multi-User System.
Oct 28 18:16:14 bka systemd[1]: Stopped target Login Prompts.
Oct 28 18:16:14 bka systemd[1]: Stopped target Sound Card.
Oct 28 18:16:14 bka systemd[1]: Stopped target Timer Units.
Oct 28 18:16:14 bka systemd[1]: anacron.timer: Deactivated successfully.
Oct 28 18:16:14 bka systemd[1]: Stopped Trigger anacron every hour.
Oct 28 18:16:14 bka systemd[1]: apport-autoreport.timer: Deactivated
successfully.
Oct 28 18:16:14 bka systemd[1]: Stopped Process error reports when automatic
reporting is enabled (timer based).
Oct 28 18:16:14 bka systemd[1]: apt-daily-upgrade.timer: Deactivated
successfully.
Oct 28 18:16:14 bka systemd[1]: Stopped Daily apt upgrade and clean activities.
Oct 28 18:16:14 bka systemd[1]: apt-daily.timer: Deactivated successfully.
Oct 28 18:16:14 bka systemd[1]: Stopped Daily apt download activities.
Oct 28 18:16:14 bka systemd[1]: dpkg-db-backup.timer: Deactivated successfully.
Oct 28 18:16:14 bka systemd[1]: Stopped Daily dpkg database backup timer.
Oct 28 18:16:14 bka systemd[1]: e2scrub_all.timer: Deactivated successfully.
Oct 28 18:16:14 bka systemd[1]: Stopped Periodic ext4 Online Metadata Check for
All Filesystems.
Oct 28 18:16:14 bka systemd[1]: fstrim.timer: Deactivated successfully.
Oct 28 18:16:14 bka systemd[1]: Stopped Discard unused blocks once a week.
Oct 28 18:16:14 bka systemd[1]: fwupd-refresh.timer: Deactivated successfully.
Oct 28 18:16:14 bka systemd[1]: Stopped Refresh fwupd metadata regularly.
Oct 28 18:16:14 bka systemd[1]: logrotate.timer: Deactivated successfully.
Oct 28 18:16:14 bka systemd[1]: Stopped Daily rotation of log files.
Oct 28 18:16:14 bka systemd[1]: man-db.timer: Deactivated successfully.
Oct 28 18:16:14 bka systemd[1]: Stopped Daily man-db regeneration.
Oct 28 18:16:14 bka systemd[1]: motd-news.timer: Deactivated successfully.
Oct 28 18:16:14 bka systemd[1]: Stopped Message of the Day.
Oct 28 18:16:14 bka systemd[1]: systemd-tmpfiles-clean.timer: Deactivated
successfully.
Oct 28 18:16:14 bka systemd[1]: Stopped Daily Cleanup of Temporary Directories.
Oct 28 18:16:14 bka systemd[1]: update-notifier-download.timer: Deactivated
successfully.
Oct 28 18:16:14 bka systemd[1]: Stopped Download data for packages that failed
at package install time.
Oct 28 18:16:14 bka systemd[1]: update-notifier-motd.timer: Deactivated
successfully.
Oct 28 18:16:14 bka systemd[1]: Stopped Check to see whether there is a new
version of Ubuntu available.
Oct 28 18:16:14 bka systemd[1]: systemd-rfkill.socket: Deactivated successfully.
Oct 28 18:16:14 bka systemd[1]: Closed Load/Save RF Kill Switch Status
/dev/rfkill Watch.
Oct 28 18:16:14 bka systemd[2667]: Stopped target GNOME Wayland Session
(session: ubuntu).
Oct 28 18:16:14 bka systemd[2667]: Stopped target Current graphical user
session.
Oct 28 18:16:14 bka systemd[1]: Unmounting /mnt/045D60C13F584D47...
Oct 28 18:16:14 bka systemd[1]: Stopping Modem Manager...
Oct 28 18:16:14 bka systemd[1]: Stopping Accounts Service...
Oct 28 18:16:14 bka systemd[1]: Stopping ACPI event daemon...
Oct 28 18:16:14 bka gnome-shell[2876]: Attempting to call back into JSAPI
during the sweeping phase of GC. This is most likely caused by not destroying a
Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be
caused by using the destroy(), dispose(), or remove() vfuncs. Because it would
crash the application, it has been blocked and the JS callback not invoked.
Oct 28 18:16:14 bka gnome-shell[2876]: The offending signal was destroy on
Gjs_ui_iconGrid_BaseIcon 0x5c4601042480.
Oct 28 18:16:14 bka gnome-shell[2876]: Attempting to call back into JSAPI
during the sweeping phase of GC. This is most likely caused by not destroying a
Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be
caused by using the destroy(), dispose(), or remove() vfuncs. Because it would
crash the application, it has been blocked and the JS callback not invoked.
Oct 28 18:16:14 bka gnome-shell[2876]: The offending signal was actor-removed
on Gjs_ui_appDisplay_FolderGrid 0x5c4600f79b10.
Oct 28 18:16:14 bka gnome-shell[2876]: Attempting to call back into JSAPI
during the sweeping phase of GC. This is most likely caused by not destroying a
Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be
caused by using the destroy(), dispose(), or remove() vfuncs. Because it would
crash the application, it has been blocked and the JS callback not invoked.
Oct 28 18:16:14 bka gnome-shell[2876]: The offending signal was destroy on
Gjs_ui_appDisplay_AppIcon 0x5c4600f9fce0.
Oct 28 18:16:14 bka gnome-shell[2876]: Attempting to call back into JSAPI
during the sweeping phase of GC. This is most likely caused by not destroying a
Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be
caused by using the destroy(), dispose(), or remove() vfuncs. Because it would
crash the application, it has been blocked and the JS callback not invoked.
Oct 28 19:27:06 bka kernel: [ 0.000000] Linux version 6.8.0-47-generic
(buildd@lcy02-amd64-019) (x86_64-linux-gnu-gcc-12 (Ubuntu
12.3.0-1ubuntu1~22.04) 12.3.0, GNU ld (GNU Binutils for Ubuntu) 2.38)
#47~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Wed Oct 2 16:16:55 UTC 2 (Ubuntu
6.8.0-47.47~22.04.1-generic 6.8.12)
Oct 28 19:27:06 bka kernel: [ 0.000000] Command line:
BOOT_IMAGE=/vmlinuz-6.8.0-47-generic
root=UUID=ff08e846-1de6-49de-9fbf-8fc7394f740d ro quiet splash vt.handoff=7
Oct 28 19:27:06 bka kernel: [ 0.000000] KERNEL supported cpus:
Oct 28 19:27:06 bka kernel: [ 0.000000] Intel GenuineIntel
Oct 28 19:27:06 bka kernel: [ 0.000000] AMD AuthenticAMD
Oct 28 19:27:06 bka kernel: [ 0.000000] Hygon HygonGenuine
Oct 28 19:27:06 bka kernel: [ 0.000000] Centaur CentaurHauls
Oct 28 19:27:06 bka kernel: [ 0.000000] zhaoxin Shanghai
Oct 28 19:27:06 bka kernel: [ 0.000000] BIOS-provided physical RAM map:
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: ubiquity (not installed)
ProcVersionSignature: Ubuntu 6.8.0-47.47~22.04.1-generic 6.8.12
Uname: Linux 6.8.0-47-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.6
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Mon Oct 28 19:39:58 2024
InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed
maybe-ubiquity quiet splash ---
InstallationDate: Installed on 2022-10-22 (737 days ago)
InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64
(20220809.1)
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=<set>
LANG=de_DE.UTF-8
SHELL=/bin/bash
SourcePackage: ubiquity
Symptom: installation
UpgradeStatus: No upgrade log present (probably fresh install)
** Affects: ubiquity (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug jammy ubiquity-22.04.17 wayland-session
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2085792
Title:
Ubuntu is verry slow by shutdown or newstart
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/2085792/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
