[systemsettings] [Bug 470964] New: if a monitor is no longer available, the panel disappears / crashes. no restart / reset possible
https://bugs.kde.org/show_bug.cgi?id=470964 Bug ID: 470964 Summary: if a monitor is no longer available, the panel disappears / crashes. no restart / reset possible Classification: Applications Product: systemsettings Version: 5.24.4 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: rens.groenewe...@xs4all.nl Target Milestone: --- SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. start with 2 monitors active 2. suspend (e.g. close laptop lid, or put to sleep with KDE logout/suspend 3. resume system in normal way ( open laptop lid, or whatever it is) OBSERVED RESULT desktop restores as normal, but in a few seconds the menu/ panel crashes and does not recover. EXPECTED RESULT panel/menu should not crash. should optionally launch systemsettings so we can configure monitors to new situation if wanted. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.24.4 KDE Frameworks Version: 5.90 Qt Version: 5 ADDITIONAL INFORMATION none -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 392841] grouped icon in taskmanager does not respond on click after a while.
https://bugs.kde.org/show_bug.cgi?id=392841 --- Comment #6 from rens --- sorry for being late with responding. The issue is gone, cannot reproduce it anymore. best -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 386585] konsole crashes, when selecting part of text with mouse
https://bugs.kde.org/show_bug.cgi?id=386585 rens changed: What|Removed |Added Status|NEEDSINFO |RESOLVED --- Comment #2 from rens --- hi I cannot reproduce I was on konsole v 16.x , now on 18.x and suse now on 15.x this is 3 years old. did not even remember... -- You are receiving this mail because: You are watching all bug changes.
[kdelibs] [Bug 154936] konqueror cannot mount usb connected camera as a filesystem. nautilus when using gnome desktop has no problems.
https://bugs.kde.org/show_bug.cgi?id=154936 rens changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- --- Comment #4 from rens --- that was 10 years ago. my FZ50 is still there, although hardly. however. new kit is available: i7 laptop, asus. a plethora of digital camera's. my galaxy EK GC100 android camera does not connect. it is recognized, but fails. my sony experia XA1 is not even seen or recognized (usb connects, but digikam does not) my old sony xperia z3 compact is recognized, but does not respond usb sees no errors (dmesg -w ) , but digikam is baffled or blind. honestly, why not dump this feature ? it is anyway a lot faster to put one's sd card into the laptop itself. oh ok, for phones thats a different story, of course.. Digikam Version 4.13.0 Using KDE Development Platform 4.14.33 I am using opensuse 42.3 -- You are receiving this mail because: You are watching all bug changes.
[kdelibs] [Bug 154936] konqueror cannot mount usb connected camera as a filesystem. nautilus when using gnome desktop has no problems.
https://bugs.kde.org/show_bug.cgi?id=154936 --- Comment #5 from rens --- for samsung android kamera: konqueror mtp mode fails. ptp mode attempts, but also fails with unknown error 150 camera:/USB%2520PTP%2520Class%2520Camera@usb:001,020/ -- You are receiving this mail because: You are watching all bug changes.
[kdelibs] [Bug 154936] konqueror cannot mount usb connected camera as a filesystem. nautilus when using gnome desktop has no problems.
https://bugs.kde.org/show_bug.cgi?id=154936 --- Comment #6 from rens --- (In reply to rens from comment #5) > for samsung android kamera: > > konqueror MTP mode fails. for one entry (open with filemanager) there is two entries, identical. one works, the other does not. opening with gwenview is extremely ** slow, and finally fails GIMP can open it eye of mate can open it. showfoto cannot open it. this is the URI : (from konqueror adress ) camera:/Samsung%2520Galaxy%2520models%2520(MTP)@usb:001,022/store_00020002/DCIM/Camera/ > ptp mode attempts, but fails with unknown error 150 > > camera:/USB%2520PTP%2520Class%2520Camera@usb:001,020/ -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 373352] file open / save / save as dialog is slow if automounted filesystems are not available (nfs, smb, etc )
https://bugs.kde.org/show_bug.cgi?id=373352 rens changed: What|Removed |Added Status|RESOLVED|CLOSED --- Comment #10 from rens --- 4 years of inaction. and now we start saying we fixed it ?? lolol -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 391060] New: crashes on undo of very large tif
https://bugs.kde.org/show_bug.cgi?id=391060 Bug ID: 391060 Summary: crashes on undo of very large tif Product: kde Version: unspecified Platform: unspecified OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: rens.groenewe...@xs4all.nl Target Milestone: --- Application: showfoto (5.2.0) Qt Version: 5.6.1 Frameworks Version: 5.26.0 Operating System: Linux 4.4.92-18.36-default x86_64 Distribution: "openSUSE Leap 42.2" -- Information about the crash: 750 mbyte tif cropped a part of it. saved it under different name. all ok. then tried to undo crop (in order to crop another part and save that) showfoto crashed. The crash can be reproduced every time. -- Backtrace: Application: Showfoto (showfoto), signal: Aborted Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7fb2f7dbb9c0 (LWP 8242))] Thread 5 (Thread 0x7fb2a700 (LWP 8273)): #0 0x7fb2f34cc0bf in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fb2f431565b in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib64/libQt5Core.so.5 #2 0x7fb2f5403211 in () at /usr/lib64/libQt5Widgets.so.5 #3 0x7fb2f43149e9 in () at /usr/lib64/libQt5Core.so.5 #4 0x7fb2f34c7744 in start_thread () at /lib64/libpthread.so.0 #5 0x7fb2f3a0baad in clone () at /lib64/libc.so.6 Thread 4 (Thread 0x7fb2be031700 (LWP 8245)): #0 0x7fb2f34cc0bf in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fb2f431565b in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib64/libQt5Core.so.5 #2 0x7fb2f71d33c9 in () at /usr/lib64/libdigikamcore.so.5.2.0 #3 0x7fb2f43149e9 in () at /usr/lib64/libQt5Core.so.5 #4 0x7fb2f34c7744 in start_thread () at /lib64/libpthread.so.0 #5 0x7fb2f3a0baad in clone () at /lib64/libc.so.6 Thread 3 (Thread 0x7fb2c6e70700 (LWP 8244)): #0 0x7fb2f39ff28d in read () at /lib64/libc.so.6 #1 0x7fb2eaf5e670 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7fb2eaf1de49 in g_main_context_check () at /usr/lib64/libglib-2.0.so.0 #3 0x7fb2eaf1e2a8 in () at /usr/lib64/libglib-2.0.so.0 #4 0x7fb2eaf1e42c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #5 0x7fb2f452733b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #6 0x7fb2f44d4feb in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #7 0x7fb2f430ff1a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #8 0x7fb2f5903295 in () at /usr/lib64/libQt5DBus.so.5 #9 0x7fb2f43149e9 in () at /usr/lib64/libQt5Core.so.5 #10 0x7fb2f34c7744 in start_thread () at /lib64/libpthread.so.0 #11 0x7fb2f3a0baad in clone () at /lib64/libc.so.6 Thread 2 (Thread 0x7fb2ceb30700 (LWP 8243)): #0 0x7fb2f3a0320d in poll () at /lib64/libc.so.6 #1 0x7fb2e56d43e2 in () at /usr/lib64/libxcb.so.1 #2 0x7fb2e56d5fcf in xcb_wait_for_event () at /usr/lib64/libxcb.so.1 #3 0x7fb2d0612839 in () at /usr/lib64/libQt5XcbQpa.so.5 #4 0x7fb2f43149e9 in () at /usr/lib64/libQt5Core.so.5 #5 0x7fb2f34c7744 in start_thread () at /lib64/libpthread.so.0 #6 0x7fb2f3a0baad in clone () at /lib64/libc.so.6 Thread 1 (Thread 0x7fb2f7dbb9c0 (LWP 8242)): [KCrash Handler] #6 0x7fb2f39568d7 in raise () at /lib64/libc.so.6 #7 0x7fb2f3957caa in abort () at /lib64/libc.so.6 #8 0x7fb2f3f7472d in __gnu_cxx::__verbose_terminate_handler() () at /usr/lib64/libstdc++.so.6 #9 0x7fb2f3f72706 in () at /usr/lib64/libstdc++.so.6 #10 0x7fb2f3f72751 in () at /usr/lib64/libstdc++.so.6 #11 0x7fb2f3f72968 in () at /usr/lib64/libstdc++.so.6 #12 0x7fb2f42fbaa2 in () at /usr/lib64/libQt5Core.so.5 #13 0x7fb2f4317b15 in QByteArray::reallocData(unsigned int, QFlags) () at /usr/lib64/libQt5Core.so.5 #14 0x7fb2f4317cdf in QByteArray::resize(int) () at /usr/lib64/libQt5Core.so.5 #15 0x7fb2f431a1dc in operator>>(QDataStream&, QByteArray&) () at /usr/lib64/libQt5Core.so.5 #16 0x7fb2f73343cb in Digikam::UndoCache::getData(int) const () at /usr/lib64/libdigikamcore.so.5.2.0 #17 0x7fb2f7334f65 in Digikam::UndoManager::restoreSnapshot(int, Digikam::UndoMetadataContainer const&) () at /usr/lib64/libdigikamcore.so.5.2.0 #18 0x7fb2f7336265 in Digikam::UndoManager::undoStep(bool, bool, bool) () at /usr/lib64/libdigikamcore.so.5.2.0 #19 0x7fb2f7336513 in Digikam::UndoManager::undo() () at /usr/lib64/libdigikamcore.so.5.2.0 #20 0x7fb2f7338c62 in Digikam::EditorCore::undo() () at /usr/lib64/libdigikamcore.so.5.2.0 #21 0x7fb2f7388a25 in Digikam::Canvas::slotUndo(int) () at /usr/lib64/libdigikamcore.so.5.2.0 #22 0x7fb2f4500bc1 in QMetaObject::activate(QObject*, int, int, void**) () at /usr/lib64/libQt5Core.so.5 #23 0x7fb2f45
[digikam] [Bug 391060] crashes on undo of very large tif
https://bugs.kde.org/show_bug.cgi?id=391060 --- Comment #2 from rens --- I do not know about what happens under the hood. 750 mbyte is on disk. and it is a compressed TIFF. no idea how big it is in real memory. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 392841] New: grouped icon in taskmanager does not respond on click after a while.
https://bugs.kde.org/show_bug.cgi?id=392841 Bug ID: 392841 Summary: grouped icon in taskmanager does not respond on click after a while. Product: plasmashell Version: 5.8.7 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Task Manager Assignee: h...@kde.org Reporter: rens.groenewe...@xs4all.nl CC: plasma-b...@kde.org Target Milestone: 1.0 grouped icon in taskmanager does not respond on click after a while, i.e, it does not show the active windows and therefore they cant be activaterd. workaround : - killall plasmashell && kstart plasmashell this restores functionality.for a while; some minutes or hours, it varies. this is a repeat of an old bug in plasma4 ? -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 390290] New: trying to use "red eyes" reduction function make showfoto crash
https://bugs.kde.org/show_bug.cgi?id=390290 Bug ID: 390290 Summary: trying to use "red eyes" reduction function make showfoto crash Product: kde Version: unspecified Platform: unspecified OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: rens.groenewe...@xs4all.nl Target Milestone: --- Application: showfoto (5.2.0) Qt Version: 5.6.1 Frameworks Version: 5.26.0 Operating System: Linux 4.4.92-18.36-default x86_64 Distribution: "openSUSE Leap 42.2" -- Information about the crash: - What I was doing when the application crashed: wanted to use the "red eyes" feature. from the menu, selected the item. it then crashed at once. this happened a few times, with different files. The crash can be reproduced every time. -- Backtrace: Application: Showfoto (showfoto), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7fdd03f1c9c0 (LWP 15048))] Thread 5 (Thread 0x7fdcc13c7700 (LWP 20545)): [KCrash Handler] #6 0x7fdd0322bfc8 in Digikam::RedEyeCorrectionFilter::filterImage() () at /usr/lib64/libdigikamcore.so.5.2.0 #7 0x7fdd03100908 in Digikam::DImgThreadedFilter::startFilterDirectly() () at /usr/lib64/libdigikamcore.so.5.2.0 #8 0x7fdd0333593e in Digikam::DynamicThread::DynamicThreadPriv::run() () at /usr/lib64/libdigikamcore.so.5.2.0 #9 0x7fdd0047281e in () at /usr/lib64/libQt5Core.so.5 #10 0x7fdd004759e9 in () at /usr/lib64/libQt5Core.so.5 #11 0x7fdcff628744 in start_thread () at /lib64/libpthread.so.0 #12 0x7fdcffb6caad in clone () at /lib64/libc.so.6 Thread 4 (Thread 0x7fdcca0c7700 (LWP 15051)): #0 0x7fdcff62d0bf in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fdd0047665b in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib64/libQt5Core.so.5 #2 0x7fdd033343c9 in () at /usr/lib64/libdigikamcore.so.5.2.0 #3 0x7fdd004759e9 in () at /usr/lib64/libQt5Core.so.5 #4 0x7fdcff628744 in start_thread () at /lib64/libpthread.so.0 #5 0x7fdcffb6caad in clone () at /lib64/libc.so.6 Thread 3 (Thread 0x7fdcd2e70700 (LWP 15050)): #0 0x7fdcffb6420d in poll () at /lib64/libc.so.6 #1 0x7fdcf707f314 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7fdcf707f42c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7fdd0068833b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7fdd00635feb in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7fdd00470f1a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #6 0x7fdd01a64295 in () at /usr/lib64/libQt5DBus.so.5 #7 0x7fdd004759e9 in () at /usr/lib64/libQt5Core.so.5 #8 0x7fdcff628744 in start_thread () at /lib64/libpthread.so.0 #9 0x7fdcffb6caad in clone () at /lib64/libc.so.6 Thread 2 (Thread 0x7fdcdac91700 (LWP 15049)): #0 0x7fdcffb6420d in poll () at /lib64/libc.so.6 #1 0x7fdcf18353e2 in () at /usr/lib64/libxcb.so.1 #2 0x7fdcf1836fcf in xcb_wait_for_event () at /usr/lib64/libxcb.so.1 #3 0x7fdcdc773839 in () at /usr/lib64/libQt5XcbQpa.so.5 #4 0x7fdd004759e9 in () at /usr/lib64/libQt5Core.so.5 #5 0x7fdcff628744 in start_thread () at /lib64/libpthread.so.0 #6 0x7fdcffb6caad in clone () at /lib64/libc.so.6 Thread 1 (Thread 0x7fdd03f1c9c0 (LWP 15048)): #0 0x7fdcff62d0bf in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fdcf1835629 in () at /usr/lib64/libxcb.so.1 #2 0x7fdcf1836d1f in () at /usr/lib64/libxcb.so.1 #3 0x7fdcf1836e32 in xcb_wait_for_reply () at /usr/lib64/libxcb.so.1 #4 0x7fdcdc78fc0d in () at /usr/lib64/libQt5XcbQpa.so.5 #5 0x7fdcdc78fdd3 in () at /usr/lib64/libQt5XcbQpa.so.5 #6 0x7fdd00b98174 in QCursor::pos(QScreen const*) () at /usr/lib64/libQt5Gui.so.5 #7 0x7fdd00b98331 in QCursor::pos() () at /usr/lib64/libQt5Gui.so.5 #8 0x0044ee5f in () #9 0x7fdd006621d3 in QMetaObject::activate(QObject*, int, int, void**) () at /usr/lib64/libQt5Core.so.5 #10 0x7fdd0066f122 in QTimer::timerEvent(QTimerEvent*) () at /usr/lib64/libQt5Core.so.5 #11 0x7fdd00662f44 in QObject::event(QEvent*) () at /usr/lib64/libQt5Core.so.5 #12 0x7fdd0133ee3c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib64/libQt5Widgets.so.5 #13 0x7fdd0134349a in QApplication::notify(QObject*, QEvent*) () at /usr/lib64/libQt5Widgets.so.5 #14 0x7fdd00637fd5 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib64/libQt5Core.so.5 #15 0x7fdd00687c8e in QTimerInfoList::activateTimers() () at /usr/lib64/libQt5Core.so.5 #16 0x7fdd00688051 in () at /usr/lib64/libQt5Core.so.5 #17 0x7fdcf707f134 in g_main_context_dispatch () at /us
[plasma4] [Bug 324256] waking from suspend (on resume) stops Keyboard and Mouse _clicks_ response
https://bugs.kde.org/show_bug.cgi?id=324256 --- Comment #20 from rens --- Hello, It seems to be plasmashell, which is hanging / blocked / looses track of input from pointing device and keyboard Workaround: the way to restart is (for me) alt - spacebar, so I can do killall plasmashell and then plasmashell after which everything is working again. which at least saves me from loosing work, concept emails and the works. hope this helps. Rens -- You are receiving this mail because: You are watching all bug changes.
[plasma4] [Bug 324256] waking from suspend (on resume) stops Keyboard and Mouse _clicks_ response
https://bugs.kde.org/show_bug.cgi?id=324256 --- Comment #21 from rens --- actually, I start a Konsole, and then do killall plasmashell plasmashell -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 359465] plasmashell unresponsive/freezes after resuming from suspend to RAM
https://bugs.kde.org/show_bug.cgi?id=359465 rens changed: What|Removed |Added CC||rens.groenewe...@xs4all.nl -- You are receiving this mail because: You are watching all bug changes.
[plasma4] [Bug 324256] waking from suspend (on resume) stops Keyboard and Mouse _clicks_ response
https://bugs.kde.org/show_bug.cgi?id=324256 --- Comment #22 from rens --- in addition : I changed the settings for powersaving: I disallow turning the display off. (it dims, but is not turned off, kde powermgmt for both on AC, battery, low battery ) since then ( 4 days) , I havent had the issue it used to happens once or twice a day minimum. apparently restoring focus to the proper window gets lost ( and it is fatal when the screenlocker does not get the focus back from X because then you cannot orderly shutdown your open apps.. ) hope this helps -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 386585] New: konsole crashes, when selecting part of text with mouse
https://bugs.kde.org/show_bug.cgi?id=386585 Bug ID: 386585 Summary: konsole crashes, when selecting part of text with mouse Product: konsole Version: 16.08.2 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: konsole-de...@kde.org Reporter: rens.groenewe...@xs4all.nl Target Milestone: --- Application: konsole (16.08.2) Qt Version: 5.6.1 Frameworks Version: 5.26.0 Operating System: Linux 4.4.92-18.36-default x86_64 Distribution: "openSUSE Leap 42.2" -- Information about the crash: running konsole, nothing special about it. runs opensuse leap 42.2 first occurence AFTER I updated regular platform security fixes etc. The crash can be reproduced sometimes. -- Backtrace: Application: Konsole (konsole), signal: Aborted Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7fcaae7098c0 (LWP 23186))] Thread 7 (Thread 0x7fca84c0c700 (LWP 23193)): #0 0x7fcaa5fa80bf in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fca917a8413 in () at /usr/lib64/dri/swrast_dri.so #2 0x7fca917a7f87 in () at /usr/lib64/dri/swrast_dri.so #3 0x7fcaa5fa3744 in start_thread () at /lib64/libpthread.so.0 #4 0x7fcaae051aad in clone () at /lib64/libc.so.6 Thread 6 (Thread 0x7fca8540d700 (LWP 23192)): #0 0x7fcaa5fa80bf in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fca917a8413 in () at /usr/lib64/dri/swrast_dri.so #2 0x7fca917a7f87 in () at /usr/lib64/dri/swrast_dri.so #3 0x7fcaa5fa3744 in start_thread () at /lib64/libpthread.so.0 #4 0x7fcaae051aad in clone () at /lib64/libc.so.6 Thread 5 (Thread 0x7fca85c0e700 (LWP 23191)): #0 0x7fcaa5fa80bf in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fca917a8413 in () at /usr/lib64/dri/swrast_dri.so #2 0x7fca917a7f87 in () at /usr/lib64/dri/swrast_dri.so #3 0x7fcaa5fa3744 in start_thread () at /lib64/libpthread.so.0 #4 0x7fcaae051aad in clone () at /lib64/libc.so.6 Thread 4 (Thread 0x7fca8640f700 (LWP 23190)): #0 0x7fcaa5fa80bf in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fca917a8413 in () at /usr/lib64/dri/swrast_dri.so #2 0x7fca917a7f87 in () at /usr/lib64/dri/swrast_dri.so #3 0x7fcaa5fa3744 in start_thread () at /lib64/libpthread.so.0 #4 0x7fcaae051aad in clone () at /lib64/libc.so.6 Thread 3 (Thread 0x7fca9326c700 (LWP 23189)): #0 0x7fcaae04920d in poll () at /lib64/libc.so.6 #1 0x7fcaa5a86314 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7fcaa5a8642c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7fcaaa65c33b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7fcaaa609feb in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7fcaaa444f1a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #6 0x7fcaa8814295 in () at /usr/lib64/libQt5DBus.so.5 #7 0x7fcaaa4499e9 in () at /usr/lib64/libQt5Core.so.5 #8 0x7fcaa5fa3744 in start_thread () at /lib64/libpthread.so.0 #9 0x7fcaae051aad in clone () at /lib64/libc.so.6 Thread 2 (Thread 0x7fca99610700 (LWP 23188)): #0 0x7fcaae04920d in poll () at /lib64/libc.so.6 #1 0x7fcaa63c63e2 in () at /usr/lib64/libxcb.so.1 #2 0x7fcaa63c7fcf in xcb_wait_for_event () at /usr/lib64/libxcb.so.1 #3 0x7fca9bb6a839 in () at /usr/lib64/libQt5XcbQpa.so.5 #4 0x7fcaaa4499e9 in () at /usr/lib64/libQt5Core.so.5 #5 0x7fcaa5fa3744 in start_thread () at /lib64/libpthread.so.0 #6 0x7fcaae051aad in clone () at /lib64/libc.so.6 Thread 1 (Thread 0x7fcaae7098c0 (LWP 23186)): [KCrash Handler] #6 0x7fcaadf9c8d7 in raise () at /lib64/libc.so.6 #7 0x7fcaadf9dcaa in abort () at /lib64/libc.so.6 #8 0x7fcaadfda1b4 in () at /lib64/libc.so.6 #9 0x7fcaadfdf706 in malloc_printerr () at /lib64/libc.so.6 #10 0x7fcaaa4a7774 in QHashData::free_helper(void (*)(QHashData::Node*)) () at /usr/lib64/libQt5Core.so.5 #11 0x7fcaadca3601 in () at /usr/lib64/libkonsoleprivate.so.16 #12 0x7fcaadca411b in () at /usr/lib64/libkonsoleprivate.so.16 #13 0x7fcaadcf8b38 in Konsole::TerminalDisplay::processFilters() () at /usr/lib64/libkonsoleprivate.so.16 #14 0x7fcaadcf8ca5 in Konsole::TerminalDisplay::mouseMoveEvent(QMouseEvent*) () at /usr/lib64/libkonsoleprivate.so.16 #15 0x7fcaab5e784e in QWidget::event(QEvent*) () at /usr/lib64/libQt5Widgets.so.5 #16 0x7fcaadcff52a in Konsole::TerminalDisplay::event(QEvent*) () at /usr/lib64/libkonsoleprivate.so.16 #17 0x7fcaab5a5e3c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib64/libQt5Widgets.so.5 #18 0x7fcaab5aad14 in QApplication::notify(QObject*, QEvent*) () at /usr/lib64/l
[kde] [Bug 373352] New: file open / save / save as dialog is slow if automounted filesystems are not available (nfs, smb, etc )
https://bugs.kde.org/show_bug.cgi?id=373352 Bug ID: 373352 Summary: file open / save / save as dialog is slow if automounted filesystems are not available (nfs, smb, etc ) Product: kde Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: rens.groenewe...@xs4all.nl Target Milestone: --- file open / save / save as dialog is slow if automounted filesystems are not available (nfs, smb, etc ) disabling automount makes the problem go away... -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 378394] New: baloo daemon crashed
https://bugs.kde.org/show_bug.cgi?id=378394 Bug ID: 378394 Summary: baloo daemon crashed Product: kde Version: unspecified Platform: unspecified OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: rens.groenewe...@xs4all.nl Target Milestone: --- Application: baloo_file (5.21.0) Qt Version: 5.5.1 Operating System: Linux 4.1.38-50-default x86_64 Distribution: "openSUSE Leap 42.1 (x86_64)" -- Information about the crash: - What I was doing when the application crashed: nothing particular. I was typing in a konsole window, when I got the crash popup. -- Backtrace: Application: Baloo File Indexing Daemon (baloo_file), signal: Aborted Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7fa570afd780 (LWP 11869))] Thread 2 (Thread 0x7fa425b09700 (LWP 15962)): [KCrash Handler] #6 0x7fa56e5720c7 in raise () at /lib64/libc.so.6 #7 0x7fa56e573478 in abort () at /lib64/libc.so.6 #8 0x7fa56c3432a9 in () at /usr/lib64/liblmdb-0.9.14.so #9 0x7fa56c3436b5 in () at /usr/lib64/liblmdb-0.9.14.so #10 0x7fa56c344dd2 in () at /usr/lib64/liblmdb-0.9.14.so #11 0x7fa56c344ff9 in () at /usr/lib64/liblmdb-0.9.14.so #12 0x7fa56c346b14 in () at /usr/lib64/liblmdb-0.9.14.so #13 0x7fa56c349643 in mdb_cursor_put () at /usr/lib64/liblmdb-0.9.14.so #14 0x7fa56c34bd27 in mdb_put () at /usr/lib64/liblmdb-0.9.14.so #15 0x7fa56f8df47c in Baloo::DocumentDB::put(unsigned long long, QVector const&) () at /usr/lib64/libKF5BalooEngine.so.5 #16 0x7fa56f8f8a4d in Baloo::WriteTransaction::addDocument(Baloo::Document const&) () at /usr/lib64/libKF5BalooEngine.so.5 #17 0x00410f27 in () #18 0x7fa56f012382 in () at /usr/lib64/libQt5Core.so.5 #19 0x7fa56f01532f in () at /usr/lib64/libQt5Core.so.5 #20 0x7fa56d6560a4 in start_thread () at /lib64/libpthread.so.0 #21 0x7fa56e62202d in clone () at /lib64/libc.so.6 Thread 1 (Thread 0x7fa570afd780 (LWP 11869)): #0 0x7fa56d65c8fc in __lll_robust_lock_wait () at /lib64/libpthread.so.0 #1 0x7fa56d653f68 in _L_robust_lock_199 () at /lib64/libpthread.so.0 #2 0x7fa56d653b42 in __pthread_mutex_lock_full () at /lib64/libpthread.so.0 #3 0x7fa56c343b66 in () at /usr/lib64/liblmdb-0.9.14.so #4 0x7fa56c344501 in mdb_txn_begin () at /usr/lib64/liblmdb-0.9.14.so #5 0x7fa56f8f1d4b in Baloo::Transaction::Transaction(Baloo::Database const&, Baloo::Transaction::TransactionType) () at /usr/lib64/libKF5BalooEngine.so.5 #6 0x0041ddf4 in () #7 0x7fa56f22073f in QMetaObject::activate(QObject*, int, int, void**) () at /usr/lib64/libQt5Core.so.5 #8 0x0041e75a in () #9 0x004228f9 in () #10 0x7fa56f22073f in QMetaObject::activate(QObject*, int, int, void**) () at /usr/lib64/libQt5Core.so.5 #11 0x7fa56f2a28ee in QSocketNotifier::activated(int, QSocketNotifier::QPrivateSignal) () at /usr/lib64/libQt5Core.so.5 #12 0x7fa56f22da89 in QSocketNotifier::event(QEvent*) () at /usr/lib64/libQt5Core.so.5 #13 0x7fa56f1f118d in QCoreApplication::notify(QObject*, QEvent*) () at /usr/lib64/libQt5Core.so.5 #14 0x7fa56f1f0e95 in QCoreApplication::notifyInternal(QObject*, QEvent*) () at /usr/lib64/libQt5Core.so.5 #15 0x7fa56f248ca5 in () at /usr/lib64/libQt5Core.so.5 #16 0x7fa56b051c84 in g_main_context_dispatch () at /usr/lib64/libglib-2.0.so.0 #17 0x7fa56b051ed8 in () at /usr/lib64/libglib-2.0.so.0 #18 0x7fa56b051f7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #19 0x7fa56f247d6c in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #20 0x7fa56f1eed53 in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #21 0x7fa56f1f68f6 in QCoreApplication::exec() () at /usr/lib64/libQt5Core.so.5 #22 0x0040a832 in () #23 0x7fa56e55eb25 in __libc_start_main () at /lib64/libc.so.6 #24 0x0040a9a8 in _start () Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[plasma4] [Bug 324256] waking from suspend (on resume) stops Keyboard and Mouse _clicks_ response
https://bugs.kde.org/show_bug.cgi?id=324256 rens changed: What|Removed |Added CC||rens.groenewe...@xs4all.nl --- Comment #17 from rens --- Hello. I seem to have similar issues. opensuse leap42.1 kde plasma 5 & kde4 its the launcher panel that becomes unresponsive the mouse / keyboard + running apps still work and react. hovering over the launcher or clicking on it has zero response. It usually happens when coming out of suspend ( suspended by having closed the lid or just suspended after the time configured (5 min in my case)) I do not have a screen lock, but do use the manual screen lock when at work (ctrl+alt+L ) I tried kdm instead of ssdm, but made no difference. I tried kde instead of kdeplasma to start with, made no difference. I tried different kernels, made no difference. hardware : core i7, 5xxx generation, 8 GB RAM, 256 GB ssd asus ux301L zenbook 13" let me know if I can do/test something. I havent seen this behaviour before updating to kde5 (plasma etc) -- You are receiving this mail because: You are watching all bug changes.
[plasma4] [Bug 324256] waking from suspend (on resume) stops Keyboard and Mouse _clicks_ response
https://bugs.kde.org/show_bug.cgi?id=324256 --- Comment #18 from rens --- Today launcher froze up again. I had manually locked the screen with ctrl+alt+L Suspend did not activate, since the laptop was on power. hovering over, clicking on it had no result. I opened a console with ctrl+alt+F1 I started kwin_x11 --replace went back to desktop with ctrl+alt+F8 I noticed that one window had lost it's window manager frame: as if there was no kwin_x11 running and managing it. >From an open konsole, I started xkill and killed the unmanaged window. This resulted in a restart of the launcher, and everything is working as normal again. btw, the app in the window was Dolphin. apparently: - suspend apparently has nothing to do with it. - I am not sure if I could have done this without the kwin_x11 --replace. I will check next time :-) - kwin_x11 gets stuck on a window that grabs the mouse/keyboard for unknown reasons. I didnt plug or unplug any devices or whatever (Dolphin is sensitive to that, e.g. with failing nfs mounts after resuming from suspend etc ) -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 501503] search cannot find files if starting path has a symbolic link in itself.
https://bugs.kde.org/show_bug.cgi?id=501503 --- Comment #11 from rens --- (In reply to Avraham Hollander from comment #6) > (In reply to rens from comment #4) > > (In reply to Avraham Hollander from comment #2) > > > I cannot reproduce this on Fedora 41. > > > > fedora 41 doesnt have dolphin / kde by default. did you install it ? > > Fedora KDE. Same difference. I got 41 downloaded. live workstation, installed from that. (excruciating slow in a KVM, unusable, really ) anyway, it doesnt have KDE. I assume you have different download image from somewhere ? could you point me at it ?? Tried installing dolphin, on this workstation stuff, but that fails to run. some missing symbol in some library. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 463830] Summary: Differences between Dolphin's filenamesearch and baloosearch
https://bugs.kde.org/show_bug.cgi?id=463830 rens changed: What|Removed |Added CC||rens.groenewe...@xs4all.nl --- Comment #8 from rens --- drop baloo and all this other bs gimmicks. find works fine, get the output and parse it. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 501503] search cannot find files if starting path has a symbolic link in itself.
https://bugs.kde.org/show_bug.cgi?id=501503 --- Comment #3 from rens --- Created attachment 179474 --> https://bugs.kde.org/attachment.cgi?id=179474&action=edit ubuntu dolphin also does not detect files in a linked directory Ubuntu dolphin shows same bug as in suse. I installed Ubuntu for this in a 10 min. I am trying to install fedora 41, and see if I can reproduce there. it is extremely slow (as always) -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 501503] search cannot find files if starting path has a symbolic link in itself.
https://bugs.kde.org/show_bug.cgi?id=501503 --- Comment #5 from rens --- Comment on attachment 179474 --> https://bugs.kde.org/attachment.cgi?id=179474 ubuntu dolphin also does not detect files in a linked directory dl is a link to Downloads in the homedir. a file called "afile" was created there. however, Dolphin is not able to find it. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 501503] search cannot find files if starting path has a symbolic link in itself.
https://bugs.kde.org/show_bug.cgi?id=501503 --- Comment #4 from rens --- (In reply to Avraham Hollander from comment #2) > I cannot reproduce this on Fedora 41. fedora 41 doesnt have dolphin / kde by default. did you install it ? -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 501503] search cannot find files if starting path has a symbolic link in itself.
https://bugs.kde.org/show_bug.cgi?id=501503 --- Comment #1 from rens --- removed that comment... forgot ... sorry > > SUMMARY > if one searches for a file when dolphin is in a path containing a link, > nothing can be found. > > STEPS TO REPRODUCE > 1. open dolphin, go to home dir, and hit f4 for a terminal window in > dolphin. you are in your home dir > 2. ln -s /tmp alink # link /tmp to a dir in your homedir > 3. alink shows in file/dir panel, > 4. double click. you will see all files in /tmp. plasma* will be all over > the place > 5. do ctrl-F for searching. > 6. type plasma as search > 7. nothing is found ...the result : "No items matching the search" > OBSERVED RESULT > dolphin cannot find files from this linked directory > > EXPECTED RESULT > finds files in linked directory > > SOFTWARE/OS VERSIONS > Windows: > macOS: > (available in the Info Center app, or by running `kinfo` in a terminal > window) > Linux/KDE Plasma: all since the start of the common era ( 0 BC ) > KDE Plasma Version: all current > KDE Frameworks Version: all current > Qt Version: all current > > ADDITIONAL INFORMATION > this bug has been there for years. nobody ever noticed ?? thats hilarious... -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 501503] New: search cannot find files if starting path has a symbolic link in itself.
https://bugs.kde.org/show_bug.cgi?id=501503 Bug ID: 501503 Summary: search cannot find files if starting path has a symbolic link in itself. Classification: Applications Product: dolphin Version: 22.12.3 Platform: openSUSE OS: Linux Status: REPORTED Severity: critical Priority: NOR Component: search Assignee: dolphin-bugs-n...@kde.org Reporter: rens.groenewe...@xs4all.nl CC: kfm-de...@kde.org Target Milestone: --- *** If you're not sure this is actually a bug, instead post about it at https://discuss.kde.org If you're reporting a crash, attach a backtrace with debug symbols; see https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports Please remove this comment after reading and before submitting - thanks! *** SUMMARY if one searches for a file when dolphin is in a path containing a link, nothing can be found. STEPS TO REPRODUCE 1. open dolphin, go to home dir, and hit f4 for a terminal window in dolphin. you are in your home dir 2. ln -s /tmp alink # link /tmp to a dir in your homedir 3. alink shows in file/dir panel, 4. double click. you will see all files in /tmp. plasma* will be all over the place 5. do ctrl-F for searching. 6. type plasma as search 7. nothing is found ...the result : "No items matching the search" OBSERVED RESULT dolphin cannot find files from this linked directory EXPECTED RESULT finds files in linked directory SOFTWARE/OS VERSIONS Windows: macOS: (available in the Info Center app, or by running `kinfo` in a terminal window) Linux/KDE Plasma: all since the start of the common era ( 0 BC ) KDE Plasma Version: all current KDE Frameworks Version: all current Qt Version: all current ADDITIONAL INFORMATION this bug has been there for years. nobody ever noticed ?? thats hilarious... -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 501503] search cannot find files if starting path has a symbolic link in itself.
https://bugs.kde.org/show_bug.cgi?id=501503 --- Comment #10 from rens --- (In reply to Avraham Hollander from comment #6) > (In reply to rens from comment #4) > > (In reply to Avraham Hollander from comment #2) > > > I cannot reproduce this on Fedora 41. > > > > fedora 41 doesnt have dolphin / kde by default. did you install it ? > > Fedora KDE. Same difference. I got 41 downloaded. live workstation, installed from that. (excruciating slow in a KVM, unusable, really ) anyway, it doesnt have KDE. I assume you have different download image from somewhere ? could you point me at it ?? Tried installing dolphin, on this workstation stuff, but that fails to run. some missing symbol in some library. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 366284] Compositor crashes after using dashboard until icon in systray is closed
https://bugs.kde.org/show_bug.cgi?id=366284 --- Comment #8 from Hugo Rens --- (In reply to Alexander Mentyu from comment #7) > @Hugo Rens is this bug still relevant for you after updates? Sorry for my lack of feedback, I didn't actually encountered the bug after a few updates (as far as I can remember) and I'm afraid I can't tell you exactly what update solved the issue. So no, the bug isn't relevant for me anymore. Can I (and should I) do something to close/delete the issue ? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 367946] New: plasma crashes when extra monitor is plugged in (mini display port )
https://bugs.kde.org/show_bug.cgi?id=367946 Bug ID: 367946 Summary: plasma crashes when extra monitor is plugged in (mini display port ) 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: rens.groenewe...@xs4all.nl CC: bhus...@gmail.com, plasma-b...@kde.org Application: plasmashell (5.5.5) Qt Version: 5.5.1 Operating System: Linux 4.1.31-1.gde9ddf8-default x86_64 Distribution: "openSUSE Leap 42.1 (x86_64)" -- Information about the crash: - What I was doing when the application crashed: I plugged in a HD monitor, system already up and running. I am using a mini display => HDMI converter The monitor has been plugged in before, many times ( is at the job ) Sometimes this happens. The crash can be reproduced sometimes. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f4e60dc07c0 (LWP 23526))] Thread 8 (Thread 0x7f4da1fff700 (LWP 23702)): #0 0x7f4e569a16f8 in g_main_context_query () at /usr/lib64/libglib-2.0.so.0 #1 0x7f4e569a1dcf in () at /usr/lib64/libglib-2.0.so.0 #2 0x7f4e569a1f7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7f4e5abf1d8b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7f4e5ab98d53 in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7f4e5a9ba61a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #6 0x7f4d94225cf7 in KCupsConnection::run() () at /usr/lib64/libkcupslib.so #7 0x7f4e5a9bf32f in () at /usr/lib64/libQt5Core.so.5 #8 0x7f4e59ace0a4 in start_thread () at /lib64/libpthread.so.0 #9 0x7f4e5a2cd02d in clone () at /lib64/libc.so.6 Thread 7 (Thread 0x7f4e2c985700 (LWP 23641)): #0 0x7f4e5a2c4bfd in poll () at /lib64/libc.so.6 #1 0x7f4e569a1e64 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7f4e569a1f7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7f4e5abf1d8b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7f4e5ab98d53 in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7f4e5a9ba61a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #6 0x7f4e5e86a282 in () at /usr/lib64/libQt5Quick.so.5 #7 0x7f4e5a9bf32f in () at /usr/lib64/libQt5Core.so.5 #8 0x7f4e59ace0a4 in start_thread () at /lib64/libpthread.so.0 #9 0x7f4e5a2cd02d in clone () at /lib64/libc.so.6 Thread 6 (Thread 0x7f4e2f7ba700 (LWP 23635)): #0 0x7f4e59ad203f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f4e6049d86b in () at /usr/lib64/libQt5Script.so.5 #2 0x7f4e6049d899 in () at /usr/lib64/libQt5Script.so.5 #3 0x7f4e59ace0a4 in start_thread () at /lib64/libpthread.so.0 #4 0x7f4e5a2cd02d in clone () at /lib64/libc.so.6 Thread 5 (Thread 0x7f4e3514e700 (LWP 23603)): #0 0x7f4e5a9b7ccf in QMutex::unlock() () at /usr/lib64/libQt5Core.so.5 #1 0x7f4e5abf1cc5 in () at /usr/lib64/libQt5Core.so.5 #2 0x7f4e569a14ad in g_main_context_prepare () at /usr/lib64/libglib-2.0.so.0 #3 0x7f4e569a1d80 in () at /usr/lib64/libglib-2.0.so.0 #4 0x7f4e569a1f7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #5 0x7f4e5abf1d8b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #6 0x7f4e5ab98d53 in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #7 0x7f4e5a9ba61a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #8 0x7f4e5dccee18 in () at /usr/lib64/libQt5Qml.so.5 #9 0x7f4e5a9bf32f in () at /usr/lib64/libQt5Core.so.5 #10 0x7f4e59ace0a4 in start_thread () at /lib64/libpthread.so.0 #11 0x7f4e5a2cd02d in clone () at /lib64/libc.so.6 Thread 4 (Thread 0x7f4e3695e700 (LWP 23590)): #0 0x7f4e5a2c4bfd in poll () at /lib64/libc.so.6 #1 0x7f4e569a1e64 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7f4e569a1f7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7f4e5abf1d8b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7f4e5ab98d53 in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7f4e5a9ba61a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #6 0x7f4e5dccee18 in () at /usr/lib64/libQt5Qml.so.5 #7 0x7f4e5a9bf32f in () at /usr/lib64/libQt5Core.so.5 #8 0x7f4e59ace0a4 in start_thread () at /lib64/libpthread.so.0 #9 0x7f4e5a2cd02d in clone () at /lib64/libc.so.6 Thread 3 (Thread 0x7f4e43bda700 (LWP 23535)): #0 0x7f4e5a9b7ccf in QMutex::unlock() () at /usr/lib64/libQt5Core.so.5 #1 0x7f4e5abf
[kaffeine] [Bug 364041] New: video does not display when using kaffeine in a vncserver desktop KDE environment, viewed with vncviewer
https://bugs.kde.org/show_bug.cgi?id=364041 Bug ID: 364041 Summary: video does not display when using kaffeine in a vncserver desktop KDE environment, viewed with vncviewer Product: kaffeine Version: 1.2.2 Platform: Other OS: Linux Status: UNCONFIRMED Severity: major Priority: NOR Component: general Assignee: mche...@osg.samsung.com Reporter: rens.groenewe...@xs4all.nl I have a USB dvb S2 receiver. I use kaffeine to record films from Astra 1, 2 and 3, FTA as well as encoded. The system is on the attic, I start a desktop with e.g, vncserver :10 I then connect remotely with vncviewer from tigervnc package. the vncserver runs a kde4 desktop. I start kaffeine, which works fine. However, Kaffeine does not display any video when started on this virtual desktop. Not from live TV, but also not from mpg or avi from disk. If using x11vnc, serving the actual hardware desktop, everything works fine. Reproducible: Always Steps to Reproduce: 1. start vncserver 2. connect with vncviewer from remote system 3. start kaffeine from konsole window and try to watch a video 4. kaffeine is not displaying any video. it suggests it does (play button pressed, stop button active) but the indicator does not progress, and nothing happens. text output from kaffeine in konsole window : X windows bad parameter 3 Actual Results: no video displaying Expected Results: should have seen a video playing Qt :4.8.6 KDE dev platform : 4.14.10 Kaffeine 1.2.2 linux opensuse LEAP 42.1 -- You are receiving this mail because: You are watching all bug changes.
[kaffeine] [Bug 364041] video does not display when using kaffeine in a vncserver desktop KDE environment, viewed with vncviewer
https://bugs.kde.org/show_bug.cgi?id=364041 --- Comment #3 from rens --- Hello, disabling hardware accel : this would be an option of kaffeine, I guess ? best regards, rens On 06/08/16 19:05, Mauro Carvalho Chehab via KDE Bugzilla wrote: > https://bugs.kde.org/show_bug.cgi?id=364041 > > --- Comment #2 from Mauro Carvalho Chehab --- > By default, libVLC (present on Kaffeine versions 1.3.x and 2.0.x) will try to > use the DRI acceleration at the local machine. This doesn't work when the > display windows is on another machine. There are a number of libVLC options > that could help to disable such behavior, like --no-xlib and --vout. > > I just added a patch adding support for it. Maybe with that you could find a > setup that would work with vncviewer. > -- You are receiving this mail because: You are watching all bug changes.
[kaffeine] [Bug 364041] video does not display when using kaffeine in a vncserver desktop KDE environment, viewed with vncviewer
https://bugs.kde.org/show_bug.cgi?id=364041 --- Comment #8 from rens --- Created attachment 99426 --> https://bugs.kde.org/attachment.cgi?id=99426&action=edit rensQR128x128.jpg -- You are receiving this mail because: You are watching all bug changes.
[kaffeine] [Bug 364041] video does not display when using kaffeine in a vncserver desktop KDE environment, viewed with vncviewer
https://bugs.kde.org/show_bug.cgi?id=364041 --- Comment #7 from rens --- ok thanks. meanwhile, on 1.2.2, I worked around it by using x11vnc (=using the active xserver on the actual hardware) might be of interest to other users. btw, I am seeing that (on suse, at least) the scanfile.dvb file in the distributed package (rpm) is of better content than what kaffeine gets from the internet update as far as europe satellite info is concerned. For example Astra3 is completely missing S2 entries in that file, while the distro version does have them, although they are outdated. the missing S2 entries of course mean there is no way of tuning (most) HD channels. Allmost all of Canal Digital HD (M7) channels will be missing, which means most of europe is missing them, M7 group being quite dominant. would you be interested in having this fixed ? I will fix it for my own uses, but I am quite willing to share it. best, Rens On 06/09/16 16:14, Mauro Carvalho Chehab via KDE Bugzilla wrote: > https://bugs.kde.org/show_bug.cgi?id=364041 > > Mauro Carvalho Chehab changed: > >What|Removed |Added > > Resolution|--- |FIXED > Status|UNCONFIRMED |RESOLVED > > --- Comment #6 from Mauro Carvalho Chehab --- > I did some tests of calling Kaffeine via ssh, setting the new libVLC arguments > at: > "Settings" -> "Configure Kaffeine" -> "libVLC", changing the libVLC > arguments to: > --no-video-title-show -V xcb_glx > or > --no-video-title-show -V xcb_xv > and re-starting Kaffeine. > > both options worked for me, with vlc 2.2.3 and Kaffeine 2.0.2-git. > > PS.: due to a bug with DRI3 support on Fedora 23, I actually had to start > Kaffeine with: >LIBGL_DRI3_DISABLE=1 kaffeine > as newer versions of mesa-LibGL have troubles with X11, as documented at: >https://bugzilla.redhat.com/show_bug.cgi?id=1174257 > > I'm documenting the above at the Kaffeine's README. > > This also worked for tightvncserver (and no need to explicitly disable DRI3 on > such case). > > As we now have a way to run Kaffeine remotely, I'm closing this bug. > -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 366284] New: Compositor crashes after using dashboard until icon in systray is closed
https://bugs.kde.org/show_bug.cgi?id=366284 Bug ID: 366284 Summary: Compositor crashes after using dashboard until icon in systray is closed Product: plasmashell Version: 5.7.2 Platform: Archlinux Packages URL: https://drive.google.com/open?id=0B0aDRLQv6ztAc1A0XzUz d0NtSVU OS: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: System Tray Assignee: plasma-b...@kde.org Reporter: zhugoz.r...@gmail.com Use of application dashboard seemingly brings the cowpositor (GLX 3.1 on ATI with catalyst) to crash. A black square appears on the menu icon in the panel and there is no more transparency or whatever. FTW, panel is **located on top of the screen**, so the menu icon is on the upper-left corner. Any attempt to restart the compositor (eg killall plasmashell && kstart plasmashell) will fail until every 3rd party apps' icons (telegram, skype, ...) is clicked once. When the latter is done, the black square disappears and a killall-kstart brings the compositor back to life. The figure shows in 1) where the black square appears and 2) what to click Reproducible: Couldn't Reproduce Steps to Reproduce: 1. Open Applications Dashboard 2. Click an icon 3. Crash ? Expected Results: Open the application dashboard and launch the clicked icon. This could be a GL problem, probably caused by the driver. The system is an arch linux with the catalyst driver installed, xorg version freezed to 1.6. It may be important to notice that the bug 362531 (https://bugs.kde.org/show_bug.cgi?id=362531) is also present, I issue killall and kstart at each login. I'm aware this is certainly a niche problem, and that the bug is unreproducible exept randomly, I just hope this bug will help undertand others. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 366284] Compositor crashes after using dashboard until icon in systray is closed
https://bugs.kde.org/show_bug.cgi?id=366284 --- Comment #2 from Hugo Rens --- No, both kwin and plasmashell remain usable. Only the compositor, as far as I know, crashes. The systemtray and dashboard are buggy but running. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 366284] Compositor crashes after using dashboard until icon in systray is closed
https://bugs.kde.org/show_bug.cgi?id=366284 --- Comment #4 from Hugo Rens --- Oh, my bad... Actually the windows remain usable (draggable, etc...) but there is no more transparency effects (blurry panel, console background...), and this black square on the top of the screen. I haven't still been able to reproduce this bug, though. -- You are receiving this mail because: You are watching all bug changes.
