[kwin] [Bug 427799] Conflict between autohide panel and switch desktop on edge
https://bugs.kde.org/show_bug.cgi?id=427799 Arjan changed: What|Removed |Added CC||iafil...@xs4all.nl Ever confirmed|0 |1 Status|REPORTED|CONFIRMED --- Comment #1 from Arjan --- Hi, a me too report, some additional info Using Ubuntu 20.10, amd64, included by distribution: plasma 5.19 Configured 3 virtual desktops in a row, and having 2 "Activities" Having a panel (from default) on the bottom, and another panel (form empty) on top. Setting those to autohide as described by reporter, the panels (auto)hide, but never unhide by any mouse action. The bottom panel (from default) can be tricked to show using the -key because has a shortcust to the menu in panel. The workaround as suggested by reporter: 5. Set Switch desktop on edge to Disabled, panel hides and unhides as expected. works for me too! thanks you for a proper workaround for this annoying bug. Just by diving in i found a way to set the unhide back to normal, when panel is in hiding state. this might help others: List desktop/and panel config, and extract index of panel you need to change: qdbus org.kde.plasmashell /PlasmaShell org.kde.PlasmaShell.dumpCurrentLayoutJS set panel back to normal, using the index starting from 0 in panel list from above output, demo is with '0' but adjust to your needs: qdbus org.kde.plasmashell /PlasmaShell evaluateScript "p = panelById(panelIds[0]); p.hiding = \"normal\" ;" -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 427799] Conflict between autohide panel and switch desktop on edge
https://bugs.kde.org/show_bug.cgi?id=427799 Arjan changed: What|Removed |Added Version|5.20.0 |5.21.1 Platform|Other |Manjaro --- Comment #2 from Arjan --- Hi, just tested issue with manjaro kde/plasma with plasma 5.21.1 and also there same issue. updated version and platform to manjaro (as with ubuntu I can't impossible test latest version without mucking up the whole system) not sure if product kwin is the right category shouldn't is be plasma ?? having this bug assign to kwin-bugs-n...@kde.org looks like it's totally ignored right? can someone shed a light on that? Thanks -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 464892] Multi-monitor issues under X11
https://bugs.kde.org/show_bug.cgi?id=464892 --- Comment #8 from Arjan Asadi --- (In reply to kenny.mh.hui from comment #7) > Hm, Fedora 36 Live session (Plasma 5.24.5) doesn't have this issue either. > > A short recap: > - This is an X11 only bug, Wayland works fine. > - Nouveau and NVIDIA Proprietary driver does not make a difference > - This is not Distro dependent as far as I can tell. > - This is probably introduced in Plasma 5.26 as the version before > (<=5.25.5) works fine. > - The 5.27 multi-monitor refactoring unfortunately does not seems to resolve > this issue. > - It affects Window title (gone), Context menu (extremely oversized), > Desktop icon/panel/panel widgets (Basically the entirety of plasmashell does > not have any icon showing up) and Latte Dock (Again no icon, though I no > longer use it) > - The application icon on the Window Title (Top left by default) & the > button (Top right by default) still renders > correctly with no issue. > - I am currently on a Desktop with 2 monitors connected. > - This bug happens as long as there's 2 monitor connected, no matter the > order/which one is the primary. > - If I only activate either one monitor this bug won't occur. (But bug will > persist until I restart the affected component/restart PC) > > My Main monitor is "HDMI-1" (BenQ G2412HD). [Connected to my integrated GPU] > My 2nd monitor is "DVI-D-1-1" (LG Electronics-W2261-255252). [Connected to > my NVIDIA card] > No other monitors are connected. > > -- > kscreen-doctor -o: > -- > > 65 HDMI-1 enabled connected priority 1 HDMI Modes: 100:720x400@70 > 70:1920x1080@60*! 71:1920x1080@60 72:1920x1080@50 73:1920x1080@60 > 74:1920x1080@60 75:1920x1080@50 76:1920x1080@60 77:1680x1050@60 > 78:1600x900@60 79:1280x1024@75 80:1280x1024@60 81:1280x960@60 82:1152x864@75 > 83:1280x720@60 84:1280x720@50 85:1280x720@60 86:1024x768@75 87:1024x768@60 > 88:832x624@75 89:800x600@75 90:800x600@60 91:720x576@50 92:720x576@50 > 93:720x480@60 94:720x480@60 95:720x480@60 96:720x480@60 97:640x480@75 > 98:640x480@60 99:640x480@60 Geometry: 0,0 1920x1080 Scale: 1 Rotation: 1 > Overscan: 0 Vrr: incapable RgbRange: unknown > Output: 66 HDMI-2 disabled disconnected priority 0 HDMI Modes: Geometry: 0,0 > 0x0 Scale: 1 Rotation: 1 Overscan: 0 Vrr: incapable RgbRange: unknown > Output: 67 DP-1 disabled disconnected priority 0 DisplayPort Modes: > Geometry: 0,0 0x0 Scale: 1 Rotation: 1 Overscan: 0 Vrr: incapable RgbRange: > unknown > Output: 68 HDMI-3 disabled disconnected priority 0 HDMI Modes: Geometry: 0,0 > 0x0 Scale: 1 Rotation: 1 Overscan: 0 Vrr: incapable RgbRange: unknown > Output: 151 DVI-I-1-1 disabled disconnected priority 0 DVI Modes: Geometry: > 0,0 0x0 Scale: 1 Rotation: 1 Overscan: 0 Vrr: incapable RgbRange: unknown > Output: 152 HDMI-1-4 disabled disconnected priority 0 HDMI Modes: Geometry: > 0,0 0x0 Scale: 1 Rotation: 1 Overscan: 0 Vrr: incapable RgbRange: unknown > Output: 153 DP-1-2 disabled disconnected priority 0 DisplayPort Modes: > Geometry: 0,0 0x0 Scale: 1 Rotation: 1 Overscan: 0 Vrr: incapable RgbRange: > unknown > Output: 154 DVI-D-1-1 enabled connected priority 2 DVI Modes: 100:720x400@70 > 156:1920x1080@60*! 157:1680x1050@60 158:1400x1050@60 159:1600x900@60 > 160:1280x1024@60 161:1400x900@60 162:1280x960@60 163:1440x810@60 > 164:1368x768@60 165:1280x800@60 166:1152x864@60 167:1280x720@60 > 168:1024x768@60 169:960x720@60 170:928x696@60 171:896x672@60 172:1024x576@60 > 173:960x600@60 174:832x624@60 175:960x540@60 176:800x600@60 177:800x600@56 > 178:840x525@60 179:864x486@60 180:700x525@60 181:800x450@60 182:640x512@60 > 183:700x450@60 184:640x480@60 185:720x405@60 186:684x384@60 187:576x432@60 > 188:640x360@60 189:512x384@60 190:512x288@60 191:416x312@60 192:480x270@60 > 193:400x300@60 194:432x243@60 195:320x240@60 196:360x202@60 197:320x180@60 > 71:1920x1080@60 77:1680x1050@60 79:1280x1024@75 80:1280x1024@60 > 81:1280x960@60 82:1152x864@75 86:1024x768@75 87:1024x768@60 88:832x624@75 > 89:800x600@75 90:800x600@60 97:640x480@75 99:640x480@60 Geometry: 1920,0 > 1920x1080 Scale: 1 Rotation: 1 Overscan: 0 Vrr: incapable RgbRange: unknown > > -- > kscreen-console: > -- > > START: Requesting Config > Received config. Took 19 milliseconds > Screen: > maxSize: QSize(16384, 16384) > minSize: QSize(320, 200) > currentSize: QSize(3840, 1080) > > - > > Id: 65 > Name: "HDMI-1" > Type: "HDMI" > Connected: true > Enabled: true > Priority: 1 > Rotation: KScreen::Output::None > Pos: QPoint(0,0) > MMSize
[kwin] [Bug 464892] Multi-monitor issues under X11
https://bugs.kde.org/show_bug.cgi?id=464892 --- Comment #10 from Arjan Asadi --- (In reply to kenny.mh.hui from comment #9) > (In reply to Arjan Asadi from comment #8) > > did you select TaskManager Settings > Behavior > Show only Tasks you select > > From current screen as I mentioned? > > If I don't select this my task manager works fine if I select it, it > > disappears > > Nope, it happens regardless. Swapping the monitor doesn't do anything as well > We might be hitting a different bug, does anything above occurs to you apart > from the task manager icon not showing? the only thing I encounter is the task manager disappearing. I click on the "From current screen" and it disappears, click on it again and apply and it appears again. very strange -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 464892] Multi-monitor issues under X11
https://bugs.kde.org/show_bug.cgi?id=464892 --- Comment #11 from Arjan Asadi --- (In reply to Arjan Asadi from comment #10) > (In reply to kenny.mh.hui from comment #9) > > (In reply to Arjan Asadi from comment #8) > > > did you select TaskManager Settings > Behavior > Show only Tasks you > > > select > > > From current screen as I mentioned? > > > If I don't select this my task manager works fine if I select it, it > > > disappears > > > > Nope, it happens regardless. Swapping the monitor doesn't do anything as > > well > > We might be hitting a different bug, does anything above occurs to you apart > > from the task manager icon not showing? > > the only thing I encounter is the task manager disappearing. I click on the > "From current screen" and it disappears, click on it again and apply and it > appears again. very strange 5.26.90 kde doesn't have this problem, 5.26.5-1 had it. so I enabled unstable-kde repos and my kde got more stable. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 464892] Multi-monitor issues under X11
https://bugs.kde.org/show_bug.cgi?id=464892 --- Comment #13 from Arjan Asadi --- (In reply to Nate Graham from comment #12) > Makes sense, because we did a ton of multiscreen stability fork for Plasma > 5.27! now I upgraded to 5.27 and the bug is back! 5.26.90 KDE doesn't have this problem, 5.26.5-1 had it. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 464892] Multi-monitor issues under X11
https://bugs.kde.org/show_bug.cgi?id=464892 --- Comment #14 from Arjan Asadi --- (In reply to Arjan Asadi from comment #13) > (In reply to Nate Graham from comment #12) > > Makes sense, because we did a ton of multiscreen stability fork for Plasma > > 5.27! > > now I upgraded to 5.27 and the bug is back! > 5.26.90 KDE doesn't have this problem, 5.26.5-1 had it. after restarting it seems to be fixed -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 464892] Multi-monitor issues under X11
https://bugs.kde.org/show_bug.cgi?id=464892 --- Comment #17 from Arjan Asadi --- (In reply to kenny.mh.hui from comment #15) > The task manager issue (Probably a separate bug) might be fixed, but the > issue reported still persists as of the official 5.27.0 release. > On the other hand Plasma Wayland support have gotten more mature esp in > 5.27, and I'll stay on Wayland for the time-being. > But the issue reported is still is an (atm unresolved) bug on X11, and those > who relies on X11 may also encounter this issue. > > I am happy to provide any further information when requested for this bug to > be resolved. there was a co-occuring bug that is also fixed on 5.27 for me, Global Menu was also empty which now isn't anymore -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 436197] New: Discover closed unexpectedly after clicking update button to update packages
https://bugs.kde.org/show_bug.cgi?id=436197 Bug ID: 436197 Summary: Discover closed unexpectedly after clicking update button to update packages Product: Discover Version: 5.12.8 Platform: Ubuntu Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: discover Assignee: lei...@leinir.dk Reporter: i...@boltj.es CC: aleix...@kde.org Target Milestone: --- Application: plasma-discover (5.12.8) Qt Version: 5.9.5 Frameworks Version: 5.47.0 Operating System: Linux 5.4.0-72-generic x86_64 Distribution: Ubuntu 18.04.5 LTS -- Information about the crash: - What I was doing when the application crashed: Starting Rstudio for data analysis, playing music from QuodLibet, Dolphin open - Unusual behavior I noticed: Rstudio crashed while opening .Rmd file from analysis folder in Dolphin The crash can be reproduced every time. -- Backtrace: Application: Discover (plasma-discover), signal: Aborted Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f0a12232800 (LWP 25482))] Thread 10 (Thread 0x7f09c7fff700 (LWP 25544)): #0 0x7f0a0d802639 in syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38 #1 0x7f0a0df04775 in QBasicMutex::lockInternal() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #2 0x7f0a0b774f96 in () at /usr/lib/x86_64-linux-gnu/libQt5Network.so.5 #3 0x7f0a0b775835 in () at /usr/lib/x86_64-linux-gnu/libQt5Network.so.5 #4 0x7f0a0b7518cc in QSslSocket::startClientEncryption() () at /usr/lib/x86_64-linux-gnu/libQt5Network.so.5 #5 0x7f0a0b752578 in () at /usr/lib/x86_64-linux-gnu/libQt5Network.so.5 #6 0x7f0a0b75a379 in () at /usr/lib/x86_64-linux-gnu/libQt5Network.so.5 #7 0x7f0a0e11a555 in QMetaObject::activate(QObject*, int, int, void**) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f0a0b724f09 in () at /usr/lib/x86_64-linux-gnu/libQt5Network.so.5 #9 0x7f0a0b727e78 in () at /usr/lib/x86_64-linux-gnu/libQt5Network.so.5 #10 0x7f0a0b7387ed in () at /usr/lib/x86_64-linux-gnu/libQt5Network.so.5 #11 0x7f0a0f6f883c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #12 0x7f0a0f700104 in QApplication::notify(QObject*, QEvent*) () at /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #13 0x7f0a0e0eb8d8 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #14 0x7f0a0e1454ed in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #15 0x7f0a07ff2537 in g_main_context_dispatch () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #16 0x7f0a07ff2770 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #17 0x7f0a07ff27fc in g_main_context_iteration () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #18 0x7f0a0e1448ab in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #19 0x7f0a0e0e990a in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #20 0x7f0a0df0823a in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #21 0x7f0a0df0d17d in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #22 0x7f0a09f196db in start_thread (arg=0x7f09c7fff700) at pthread_create.c:463 #23 0x7f0a0d80871f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 9 (Thread 0x7f09d5051700 (LWP 25492)): #0 0x7f0a0d7fbcb9 in __GI___poll (fds=0x555bff7d7610, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f0a07ff26e9 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f0a07ff2a82 in g_main_loop_run () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f09fcca22d6 in () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 #4 0x7f0a0801a2a5 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f0a09f196db in start_thread (arg=0x7f09d5051700) at pthread_create.c:463 #6 0x7f0a0d80871f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 8 (Thread 0x7f09d5852700 (LWP 25491)): #0 0x7f0a08038854 in g_mutex_unlock () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7f0a07ff2806 in g_main_context_iteration () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f0a07ff2841 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f0a0801a2a5 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f0a09f196db in start_thread (arg=0x7f09d5852700) at pthread_create.c:463 #5 0x7f0a0d80871f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 7 (Thread 0x7f09e4dd4700 (LWP 25488)): #0 0x7f0a09f1fad3 in futex_wait_cancelable (private=, expected=0, futex_word=0x7f09dc042030) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 0x7f0a09f1fad3 in __pthread_cond_wait_common
[amarok] [Bug 440801] Crash after search or during typing of search criterea [CollectionTreeItem::row()]
https://bugs.kde.org/show_bug.cgi?id=440801 --- Comment #2 from Arjan ten Hoopen --- Comment on attachment 141272 --> https://bugs.kde.org/attachment.cgi?id=141272 New crash information added by DrKonqi L.S. I haven't experienced this behaviour anymore for over a week. Don't know what has changed on my system but you can close this bug. I cannot reproduce it anymore. If there is still something you would like to know ... happy to help. -- You are receiving this mail because: You are watching all bug changes.
[amarok] [Bug 440801] New: Crash after search or during typing of search criterea
https://bugs.kde.org/show_bug.cgi?id=440801 Bug ID: 440801 Summary: Crash after search or during typing of search criterea Product: amarok Version: 2.9.71 Platform: openSUSE RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: amarok-bugs-d...@kde.org Reporter: arjan.ten.hoo...@gmail.com Target Milestone: kf5 Application: amarok (2.9.71) Qt Version: 5.15.2 Frameworks Version: 5.84.0 Operating System: Linux 5.3.18-59.16-default x86_64 Windowing System: X11 Drkonqi Version: 5.22.4 Distribution: "openSUSE Leap 15.3" -- Information about the crash: - What I was doing when the application crashed: I selected a search for format:flac. However I have several issues with searching. It almost always crashes. The best change of not crashing is when I type a character, wait 2 sec, type next character etc. - Custom settings of the application: I don't know if it is related, I use a mariadb database and have a collection of 70.000+ mp3 and flac tracks If there is anything I can do ... happy to help The crash can be reproduced every time. -- Backtrace: Application: Amarok (amarok), signal: Segmentation fault [KCrash Handler] #4 CollectionTreeItem::row() const (this=this@entry=0x76007200650073) at /usr/src/debug/amarok-2.9.75git.20210626T134054~59b22189f6-lp153.147.2.x86_64/src/browsers/CollectionTreeItem.cpp:224 #5 0x7f8734238420 in CollectionTreeItemModelBase::itemIndex(CollectionTreeItem*) const (this=0x55fd73514bf0, item=0x76007200650073) at /usr/src/debug/amarok-2.9.75git.20210626T134054~59b22189f6-lp153.147.2.x86_64/src/browsers/CollectionTreeItemModelBase.cpp:581 #6 0x7f87342384a0 in CollectionTreeItemModelBase::parent(QModelIndex const&) const (this=, index=) at /usr/src/debug/amarok-2.9.75git.20210626T134054~59b22189f6-lp153.147.2.x86_64/src/browsers/CollectionTreeItemModelBase.cpp:446 #7 0x7f8731a97f89 in QModelIndex::parent() const (this=0x55fd75024380) at ../../include/QtCore/../../src/corelib/itemmodels/qabstractitemmodel.h:443 #8 QSortFilterProxyModelPrivate::_q_sourceDataChanged(QModelIndex const&, QModelIndex const&, QVector const&) (this=0x55fd73770510, source_top_left=, source_bottom_right=, roles=...) at itemmodels/qsortfilterproxymodel.cpp:1433 #9 0x7f8731a9ad98 in QSortFilterProxyModel::qt_static_metacall(QObject*, QMetaObject::Call, int, void**) (_o=, _c=, _id=, _a=) at .moc/moc_qsortfilterproxymodel.cpp:275 #10 0x7f8731b07ca9 in doActivate(QObject*, int, void**) (sender=0x55fd73514bf0, signal_index=3, argv=0x7ffe30f1b920) at kernel/qobject.cpp:3898 #11 0x7f8731b01372 in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) (sender=sender@entry=0x55fd73514bf0, m=m@entry=0x7f8731faaf80 , local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7ffe30f1b920) at kernel/qobject.cpp:3946 #12 0x7f8731a64ddc in QAbstractItemModel::dataChanged(QModelIndex const&, QModelIndex const&, QVector const&) (this=this@entry=0x55fd73514bf0, _t1=..., _t2=..., _t3=...) at .moc/moc_qabstractitemmodel.cpp:557 #13 0x7f873423bf85 in CollectionTreeItemModelBase::tracksLoaded(AmarokSharedPointer const&, QModelIndex const&, QList > const&) (this=0x55fd73514bf0, album=, index=..., tracks=) at /usr/src/debug/amarok-2.9.75git.20210626T134054~59b22189f6-lp153.147.2.x86_64/src/browsers/CollectionTreeItemModelBase.cpp:724 #14 0x7f8731afe9ab in QObject::event(QEvent*) (this=0x55fd73514bf0, e=0x7f86b0004750) at kernel/qobject.cpp:1314 #15 0x7f8732a703ac in QApplicationPrivate::notify_helper(QObject*, QEvent*) (this=this@entry=0x55fd725f2e50, receiver=receiver@entry=0x55fd73514bf0, e=e@entry=0x7f86b0004750) at kernel/qapplication.cpp:3632 #16 0x7f8732a771a0 in QApplication::notify(QObject*, QEvent*) (this=0x7ffe30f1c100, receiver=0x55fd73514bf0, e=0x7f86b0004750) at kernel/qapplication.cpp:3156 #17 0x7f8731aca7b3 in QCoreApplication::notifyInternal2(QObject*, QEvent*) (receiver=0x55fd73514bf0, event=0x7f86b0004750) at kernel/qcoreapplication.cpp:1064 #18 0x7f8731aca98e in QCoreApplication::sendEvent(QObject*, QEvent*) (receiver=receiver@entry=0x55fd73514bf0, event=event@entry=0x7f86b0004750) at kernel/qcoreapplication.cpp:1462 #19 0x7f8731acd1d1 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) (receiver=receiver@entry=0x0, event_type=event_type@entry=0, data=0x55fd72563480) at kernel/qcoreapplication.cpp:1821 #20 0x7f8731acd758 in QCoreApplication::sendPostedEvents(QObject*, int) (receiver=receiver@entry=0x0, event_type=event_type@entry=0) at kernel/qcoreapplication.cpp:1680 #21 0x7f8731b2d6e3 in postEventSourceDispatch(GSource*, GSourceFunc, gpointer) (s=0x55fd72720630) at kernel/qeventdispatcher_glib.cpp:277 #22 0x7f871d2a1694 in g_main_context_dispatch () at /usr/lib64/libglib-2.0.so.0 #23 0x7f871d2a1a30 in
[kwin] [Bug 355920] plasma wayland session doesn't clear tty it uses.
https://bugs.kde.org/show_bug.cgi?id=355920 Arjan van Olphen changed: What|Removed |Added CC||ar...@scanframe.nl --- Comment #8 from Arjan van Olphen --- Same here but for some reason a lot of processes keep file descriptors open to multiple terminals at the same time. What is shown here is the result of Wayland Plasma after 2 logouts en 3 loggins Where tty4 is the current wayland terminal. I'm using Kubuntu 20.04 KDE Plasma 5.18.5. But maybe it is not KDE Plasma but a Kubuntu integration problem. -- user@adelaide:~$ who -la system boot Jun 10 17:33 run-level 5 Jun 10 17:33 tty2 Jun 10 17:42 1569 id= term=0 exit=0 user+ pts/0Jun 10 17:44 00:013605 (:1) tty3 Jun 10 17:44 2544 id= term=0 exit=0 user- pts/1Jun 10 17:45 . 4094 (:1) user+ tty4 Jun 10 17:44 00:123479 user@adelaide:~$ lsof /dev/tty3 COMMANDPID USER FD TYPE DEVICE SIZE/OFF NODE NAME dbus-run- 3479 user 25u CHR4,3 0t0 24 /dev/tty3 dbus-daem 3487 user 25u CHR4,3 0t0 24 /dev/tty3 startplas 3488 user 25u CHR4,3 0t0 24 /dev/tty3 Xwayland 3522 user 25u CHR4,3 0t0 24 /dev/tty3 startplas 3581 user 25u CHR4,3 0t0 24 /dev/tty3 plasma_se 3682 user 25u CHR4,3 0t0 24 /dev/tty3 ksmserver 3688 user 25u CHR4,3 0t0 24 /dev/tty3 baloo_fil 3712 user 25u CHR4,3 0t0 24 /dev/tty3 plasmashe 3715 user 25u CHR4,3 0t0 24 /dev/tty3 xembedsni 3717 user 25u CHR4,3 0t0 24 /dev/tty3 gmenudbus 3755 user 25u CHR4,3 0t0 24 /dev/tty3 DiscoverN 3757 user 25u CHR4,3 0t0 24 /dev/tty3 kdeconnec 3790 user 25u CHR4,3 0t0 24 /dev/tty3 agent 3796 user 25u CHR4,3 0t0 24 /dev/tty3 org_kde_p 3807 user 25u CHR4,3 0t0 24 /dev/tty3 at-spi-bu 3817 user 25u CHR4,3 0t0 24 /dev/tty3 kmix 3827 user 25u CHR4,3 0t0 24 /dev/tty3 ksysguard 3897 user 25u CHR4,3 0t0 24 /dev/tty3 konsole 4070 user 25u CHR4,3 0t0 24 /dev/tty3 bash 4094 user 25u CHR4,3 0t0 24 /dev/tty3 user@adelaide:~$ lsof /dev/tty2 COMMANDPID USER FD TYPE DEVICE SIZE/OFF NODE NAME baloo_fil 2784 user 28u CHR4,2 0t0 23 /dev/tty2 agent 2868 user 28u CHR4,2 0t0 23 /dev/tty2 dbus-run- 3479 user 28u CHR4,2 0t0 23 /dev/tty2 dbus-daem 3487 user 28u CHR4,2 0t0 23 /dev/tty2 startplas 3488 user 28u CHR4,2 0t0 23 /dev/tty2 Xwayland 3522 user 28u CHR4,2 0t0 23 /dev/tty2 startplas 3581 user 28u CHR4,2 0t0 23 /dev/tty2 plasma_se 3682 user 28u CHR4,2 0t0 23 /dev/tty2 ksmserver 3688 user 28u CHR4,2 0t0 23 /dev/tty2 baloo_fil 3712 user 28u CHR4,2 0t0 23 /dev/tty2 plasmashe 3715 user 28u CHR4,2 0t0 23 /dev/tty2 xembedsni 3717 user 28u CHR4,2 0t0 23 /dev/tty2 gmenudbus 3755 user 28u CHR4,2 0t0 23 /dev/tty2 DiscoverN 3757 user 28u CHR4,2 0t0 23 /dev/tty2 kdeconnec 3790 user 28u CHR4,2 0t0 23 /dev/tty2 agent 3796 user 28u CHR4,2 0t0 23 /dev/tty2 org_kde_p 3807 user 28u CHR4,2 0t0 23 /dev/tty2 at-spi-bu 3817 user 28u CHR4,2 0t0 23 /dev/tty2 kmix 3827 user 28u CHR4,2 0t0 23 /dev/tty2 ksysguard 3897 user 28u CHR4,2 0t0 23 /dev/tty2 konsole 4070 user 28u CHR4,2 0t0 23 /dev/tty2 bash 4094 user 28u CHR4,2 0t0 23 /dev/tty2 user@adelaide:~$ lsof /dev/tty4 COMMANDPID USER FD TYPE DEVICE SIZE/OFF NODE NAME dbus-run- 3479 user0u CHR4,4 0t0 25 /dev/tty4 startplas 3488 user0u CHR4,4 0t0 25 /dev/tty4 user@adelaide:~$ -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 368261] Plasma crashes after booting/login
https://bugs.kde.org/show_bug.cgi?id=368261 Arjan ten Hoopen changed: What|Removed |Added Status|NEEDSINFO |RESOLVED --- Comment #3 from Arjan ten Hoopen --- Cannot be reproduces in leap 15.1 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 368261] Plasma crashes after booting/login
https://bugs.kde.org/show_bug.cgi?id=368261 Arjan ten Hoopen changed: What|Removed |Added Resolution|BACKTRACE |FIXED -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 368261] New: Plasma crashes after booting/login
https://bugs.kde.org/show_bug.cgi?id=368261 Bug ID: 368261 Summary: Plasma crashes after booting/login Product: plasmashell Version: 5.5.5 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: arjan.ten.hoo...@zonnet.nl CC: bhus...@gmail.com, plasma-b...@kde.org Application: plasmashell (5.5.5) Qt Version: 5.5.1 Operating System: Linux 4.1.27-27-default x86_64 Distribution: "openSUSE Leap 42.1 (x86_64)" -- Information about the crash: - What I was doing when the application crashed: Just switched on the machine and logged in. System is within network where homedir is mounted via automounter. The crash can be reproduced every time. -- Backtrace: Application: Plasma (plasmashell), signal: Aborted Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7efd8f5677c0 (LWP 1721))] Thread 7 (Thread 0x7efccfdf9700 (LWP 1928)): #0 0x7efd85144460 in g_main_context_prepare () at /usr/lib64/libglib-2.0.so.0 #1 0x7efd85144d80 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7efd85144f7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7efd89394d8b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7efd8933bd53 in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7efd8915d61a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #6 0x7efd8d00d282 in () at /usr/lib64/libQt5Quick.so.5 #7 0x7efd8916232f in () at /usr/lib64/libQt5Core.so.5 #8 0x7efd882710a4 in start_thread () at /lib64/libpthread.so.0 #9 0x7efd88a7002d in clone () at /lib64/libc.so.6 Thread 6 (Thread 0x7efd5b3ef700 (LWP 1784)): #0 0x7efd8827503f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7efd8ec4086b in () at /usr/lib64/libQt5Script.so.5 #2 0x7efd8ec40899 in () at /usr/lib64/libQt5Script.so.5 #3 0x7efd882710a4 in start_thread () at /lib64/libpthread.so.0 #4 0x7efd88a7002d in clone () at /lib64/libc.so.6 Thread 5 (Thread 0x7efd60ee8700 (LWP 1757)): #0 0x7efd8827783a in __lll_unlock_wake () at /lib64/libpthread.so.0 #1 0x7efd882745b9 in _L_unlock_554 () at /lib64/libpthread.so.0 #2 0x7efd882744f6 in __pthread_mutex_unlock_usercnt () at /lib64/libpthread.so.0 #3 0x7efd84574525 in () at /usr/X11R6/lib64/libGL.so.1 #4 0x7efd84579beb in () at /usr/X11R6/lib64/libGL.so.1 #5 0x7efd80c060f1 in () at /usr/lib64/tls/libnvidia-tls.so.367.35 #6 0x7efd85185b60 in () at /usr/lib64/libglib-2.0.so.0 #7 0x7efd85144999 in g_main_context_check () at /usr/lib64/libglib-2.0.so.0 #8 0x7efd85144df8 in () at /usr/lib64/libglib-2.0.so.0 #9 0x7efd85144f7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #10 0x7efd89394d8b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #11 0x7efd8933bd53 in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #12 0x7efd8915d61a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #13 0x7efd8c471e18 in () at /usr/lib64/libQt5Qml.so.5 #14 0x7efd8916232f in () at /usr/lib64/libQt5Core.so.5 #15 0x7efd882710a4 in start_thread () at /lib64/libpthread.so.0 #16 0x7efd88a7002d in clone () at /lib64/libc.so.6 Thread 4 (Thread 0x7efd62683700 (LWP 1749)): #0 0x7efd85186cf9 in g_mutex_lock () at /usr/lib64/libglib-2.0.so.0 #1 0x7efd851448fc in g_main_context_check () at /usr/lib64/libglib-2.0.so.0 #2 0x7efd85144df8 in () at /usr/lib64/libglib-2.0.so.0 #3 0x7efd85144f7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #4 0x7efd89394d8b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7efd8933bd53 in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #6 0x7efd8915d61a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #7 0x7efd8c471e18 in () at /usr/lib64/libQt5Qml.so.5 #8 0x7efd8916232f in () at /usr/lib64/libQt5Core.so.5 #9 0x7efd882710a4 in start_thread () at /lib64/libpthread.so.0 #10 0x7efd88a7002d in clone () at /lib64/libc.so.6 Thread 3 (Thread 0x7efd6e20e700 (LWP 1740)): #0 0x7efd8827779c in __lll_lock_wait () at /lib64/libpthread.so.0 #1 0x7efd882734a4 in _L_lock_986 () at /lib64/libpthread.so.0 #2 0x7efd88273306 in pthread_mutex_lock () at /lib64/libpthread.so.0 #3 0x7efd8457480c in () at /usr/X11R6/lib64/libGL.so.1 #4 0x7efd84579731 in () at /usr/X11R6/lib64/libGL.so.1 #5 0x7efd84579beb in () at /usr/X11R6/lib64/libGL.so.1 #6 0x7efd80c060f1 in () at /usr/lib64/tls/libnvidia-tls.so.367.35 #7 0x7efd85185b60 in () at /usr/lib64/libglib-2.0.so.0 #8 0x7efd85144999 in g_main_context_check () at /usr
[amarok] [Bug 363992] New: Playlist shows next to each playlist item an empty playlist item
https://bugs.kde.org/show_bug.cgi?id=363992 Bug ID: 363992 Summary: Playlist shows next to each playlist item an empty playlist item Product: amarok Version: 2.8.0 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Playlists/Saved Playlists Assignee: amarok-bugs-d...@kde.org Reporter: arjan.ten.hoo...@zonnet.nl CC: bart.cerne...@kde.org Playlist shows twice the amount of items which are in the playlist. Every item is displayed but also an empty item (next to each "real" item). Reproducible: Always Steps to Reproduce: 1.Goto Playlist 2.Goto saved playlists (mine are all on disk, NOT in the db) 3.A playlist of 2 mp3s will show 4 items, two real mp3s and two empty slots. You cannot select such an empty slot, or right-click Actual Results: display of playlist which is for half empty Expected Results: display of playlist with only the "real" items Amarok 2.9.0 KDE 4.14.9 uname -a : inux arjanpc 3.16.7-35-desktop #1 SMP PREEMPT Sun Feb 7 17:32:21 UTC 2016 (832c776) x86_64 x86_64 x86_64 GNU/Linux rpm -qa | grep amarok: amarok-2.8.0-57.2.x86_64 -- You are receiving this mail because: You are watching all bug changes.
[amarok] [Bug 363992] Playlist shows next to each playlist item an empty playlist item
https://bugs.kde.org/show_bug.cgi?id=363992 Arjan ten Hoopen changed: What|Removed |Added CC||arjan.ten.hoo...@zonnet.nl --- Comment #1 from Arjan ten Hoopen --- Created attachment 99383 --> https://bugs.kde.org/attachment.cgi?id=99383&action=edit screenshot of "faulty" playlist this screenshot shows the described behaviour in the "saved Playlist" screen -- You are receiving this mail because: You are watching all bug changes.
[amarok] [Bug 323667] Too much lines in the playlist browser ....
https://bugs.kde.org/show_bug.cgi?id=323667 --- Comment #12 from Arjan ten Hoopen --- All, If you save a playlist to the amarok db then this behavior is *NOT* reproducible. However, if you save a playlist to disk this behavior *IS* reproducible. At least this is what I can reproduce on my machines. Hope this helps in reproducing the bug in various different environments. Kind regards, Arjan -- You are receiving this mail because: You are watching all bug changes.
