https://bugs.kde.org/show_bug.cgi?id=512991

            Bug ID: 512991
           Summary: Plasma Shell crashed upon boot after latest update
    Classification: Plasma
           Product: plasmashell
      Version First 6.5.3
       Reported In:
          Platform: unspecified
                OS: Linux
            Status: REPORTED
          Keywords: drkonqi
          Severity: crash
          Priority: NOR
         Component: generic-crash
          Assignee: [email protected]
          Reporter: [email protected]
  Target Milestone: 1.0

Application: plasmashell (6.5.3)

ApplicationNotResponding [ANR]: false
Qt Version: 6.10.1
Frameworks Version: 6.20.0
Operating System: Linux 6.14.0-36-generic x86_64
Windowing System: Wayland
Distribution: KDE neon User Edition
DrKonqi: 6.5.3 [CoredumpBackend]

-- Information about the crash:
After using Discover to install all the latest updates and then rebooting the
system my plasma shell crashed. Although it crashed the desktop environment
still remains and works fine. I attempted to use the trash option on a file and
it said trash process failed or something like that. The ram used up on boot is
usually 2.8 GiB however after the crash it took up somthing like 6.8 GiB. It
seems to have reduced now to 3.3. GiB I used timeshift to revert back to the
last version and then tried updating again. Things are more stable this time
however the crash still happens everytime I boot, so I will likely roll back
again. Until the next update.

The crash can be reproduced every time.

-- Backtrace (Reduced):
#6  QtWebEngineCore::ContentClientQt::SetGpuInfo () at
/workspace/build/src/core/content_client_qt.cpp:528
#7  0x000076dd0c78465d in content::GpuDataManagerImplPrivate::UpdateGpuInfo ()
at
../../../../../src/3rdparty/chromium/content/browser/gpu/gpu_data_manager_impl_private.cc:1051
#8  0x000076dd0c77c8bf in content::GpuDataManagerImpl::UpdateGpuInfo () at
../../../../../src/3rdparty/chromium/content/browser/gpu/gpu_data_manager_impl.cc:168
#9  0x000076dd0c79237c in content::GpuProcessHost::DidInitialize () at
../../../../../src/3rdparty/chromium/content/browser/gpu/gpu_process_host.cc:988
#10 0x000076dd101bb51c in viz::GpuHostImpl::DidInitialize () at
./../../../../../src/3rdparty/chromium/components/viz/host/gpu_host_impl.cc:498
#11 0x000076dd0abfa052 in viz::mojom::GpuHostStubDispatch::Accept () at
./gen/services/viz/privileged/mojom/gl/gpu_host.mojom.cc:1297
#12 0x000076dd0ec6adeb in mojo::InterfaceEndpointClient::HandleValidatedMessage
() at
../../../../../src/3rdparty/chromium/mojo/public/cpp/bindings/lib/interface_endpoint_client.cc:1052
#13 0x000076dd0ec6c7a6 in mojo::MessageDispatcher::Accept () at
../../../../../src/3rdparty/chromium/mojo/public/cpp/bindings/lib/message_dispatcher.cc:43
#14 0x000076dd0ec6aaa2 in mojo::InterfaceEndpointClient::HandleIncomingMessage
() at
../../../../../src/3rdparty/chromium/mojo/public/cpp/bindings/lib/interface_endpoint_client.cc:724
#15 0x000076dd0ec6fff0 in
mojo::internal::MultiplexRouter::ProcessIncomingMessage () at
../../../../../src/3rdparty/chromium/mojo/public/cpp/bindings/lib/multiplex_router.cc:1121
#16 0x000076dd0ec73754 in mojo::internal::MultiplexRouter::Accept () at
../../../../../src/3rdparty/chromium/mojo/public/cpp/bindings/lib/multiplex_router.cc:734
#17 0x000076dd0ec6c7a6 in mojo::MessageDispatcher::Accept () at
../../../../../src/3rdparty/chromium/mojo/public/cpp/bindings/lib/message_dispatcher.cc:43
#18 0x000076dd0ec6225e in mojo::Connector::DispatchMessage () at
../../../../../src/3rdparty/chromium/mojo/public/cpp/bindings/lib/connector.cc:562
#19 0x000076dd0ec62e86 in mojo::Connector::ReadAllAvailableMessages () at
../../../../../src/3rdparty/chromium/mojo/public/cpp/bindings/lib/connector.cc:620
#20 0x000076dd0ec62fe2 in mojo::Connector::OnHandleReadyInternal () at
../../../../../src/3rdparty/chromium/mojo/public/cpp/bindings/lib/connector.cc:452
#21 mojo::Connector::OnWatcherHandleReady () at
../../../../../src/3rdparty/chromium/mojo/public/cpp/bindings/lib/connector.cc:418


Reported using DrKonqi

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to