Bug 419496 - Missing plasma panel when Wayland session is started with multi-monitor mode set to "Unify outputs". Possibly related kded5 crash.
Summary: Missing plasma panel when Wayland session is started with multi-monitor mode ...
Status: RESOLVED DUPLICATE of bug 419492
Alias: None
Product: plasmashell
Classification: Plasma
Component: generic-wayland (show other bugs)
Version: master
Platform: Other Linux
: NOR normal
Target Milestone: 1.0
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-04-01 14:22 UTC by Patrick Silva
Modified: 2021-03-04 19:41 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Patrick Silva 2020-04-01 14:22:51 UTC
STEPS TO REPRODUCE
1. connect an external monitor to hdmi port
2. start Wayland session
3. set multi-monitor mode to "Unify outputs"
4. restart Wayland session

OBSERVED RESULT
no plasma panel

EXPECTED RESULT
plasma panel should be loaded

SOFTWARE/OS VERSIONS
Operating System: KDE neon Unstable Edition
KDE Plasma Version: 5.18.80
KDE Frameworks Version: 5.69.0
Qt Version: 5.14.1
Kernel Version: 5.3.0-45-generic
OS Type: 64-bit
Processors: 4 × Intel® Core™ i3-3110M CPU @ 2.40GHz
Memory: 7,7 GiB of RAM
Graphics Processor: Mesa DRI Intel® Ivybridge Mobile

ADDITIONAL INFORMATION
I'm not sure if this is related, but I noticed that kded5 crashes after the last step above.


Thread 1 (Thread 0x7f22c17a5800 (LWP 3588)):
#0  __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:51
#1  0x00007f22be77f801 in __GI_abort () at abort.c:79
#2  0x00007f22bef4759b in qt_message_fatal (context=..., message=<synthetic pointer>...)
    at global/qlogging.cpp:1894
#3  QMessageLogger::fatal (this=this@entry=0x7ffe36e59370, msg=msg@entry=0x7f22c0392840 "%s")
    at global/qlogging.cpp:893
#4  0x00007f22bfee5194 in init_platform (argv=<optimized out>, argc=<optimized out>, 
    platformThemeName=..., platformPluginPath=..., pluginNamesWithArguments=...)
    at kernel/qguiapplication.cpp:1249
#5  QGuiApplicationPrivate::createPlatformIntegration (this=0x55a3a85f94d0)
    at kernel/qguiapplication.cpp:1476
#6  0x00007f22bfee565d in QGuiApplicationPrivate::createEventDispatcher (this=<optimized out>)
    at kernel/qguiapplication.cpp:1493
#7  0x00007f22bf162ba5 in QCoreApplicationPrivate::init (this=this@entry=0x55a3a85f94d0)
    at kernel/qcoreapplication.cpp:865
#8  0x00007f22bfee744f in QGuiApplicationPrivate::init (this=this@entry=0x55a3a85f94d0)
    at kernel/qguiapplication.cpp:1522
#9  0x00007f22c0ea430e in QApplicationPrivate::init (this=0x55a3a85f94d0)
    at kernel/qapplication.cpp:539
#10 0x000055a3a79a3579 in main (argc=<optimized out>, argv=0x7ffe36e597c8) at ./src/kded.cpp:743

Thread 1 (Thread 0x7f22c17a5800 (LWP 3588)):
#0  __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:51
#1  0x00007f22be77f801 in __GI_abort () at abort.c:79
#2  0x00007f22bef4759b in qt_message_fatal (context=..., message=<synthetic pointer>...)
    at global/qlogging.cpp:1894
#3  QMessageLogger::fatal (this=this@entry=0x7ffe36e59370, msg=msg@entry=0x7f22c0392840 "%s")
    at global/qlogging.cpp:893
#4  0x00007f22bfee5194 in init_platform (argv=<optimized out>, argc=<optimized out>, 
    platformThemeName=..., platformPluginPath=..., pluginNamesWithArguments=...)
    at kernel/qguiapplication.cpp:1249
#5  QGuiApplicationPrivate::createPlatformIntegration (this=0x55a3a85f94d0)
    at kernel/qguiapplication.cpp:1476
#6  0x00007f22bfee565d in QGuiApplicationPrivate::createEventDispatcher (this=<optimized out>)
    at kernel/qguiapplication.cpp:1493
#7  0x00007f22bf162ba5 in QCoreApplicationPrivate::init (this=this@entry=0x55a3a85f94d0)
    at kernel/qcoreapplication.cpp:865
#8  0x00007f22bfee744f in QGuiApplicationPrivate::init (this=this@entry=0x55a3a85f94d0)
    at kernel/qguiapplication.cpp:1522
#9  0x00007f22c0ea430e in QApplicationPrivate::init (this=0x55a3a85f94d0)
    at kernel/qapplication.cpp:539
#10 0x000055a3a79a3579 in main (argc=<optimized out>, argv=0x7ffe36e597c8) at ./src/kded.cpp:743
Error detected on fd 0
error detected on stdin
Exception ignored in: <gdb.GdbOutputFile object at 0x7f0c9ac4fc50>
Traceback (most recent call last):
  File "/usr/share/gdb/python/gdb/__init__.py", line 43, in flush
    def flush(self):
KeyboardInterrupt
Comment 1 David Edmundson 2020-04-01 14:45:55 UTC
>#3  QMessageLogger::fatal (this=this@entry=0x7ffe36e59370, msg=msg@entry=0x7f22c0392840 "%s")

Do you have the error message here.

From the trace I suspect it's going to say that the wayland QPA couldn't connect.



---


Is it missing a desktop background too?
Comment 2 Patrick Silva 2020-04-01 14:51:08 UTC
No. Wallpaper and icons are present on desktop.
Comment 3 Bug Janitor Service 2020-04-16 04:33:11 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 4 Patrick Silva 2020-04-16 09:59:54 UTC
Requested information was provided.
Comment 5 Nate Graham 2021-02-26 17:04:47 UTC
*** Bug 430739 has been marked as a duplicate of this bug. ***
Comment 6 Nate Graham 2021-03-04 19:41:14 UTC

*** This bug has been marked as a duplicate of bug 419492 ***