[systemsettings] [Bug 466409] New: system settings crashes on module systemd
https://bugs.kde.org/show_bug.cgi?id=466409 Bug ID: 466409 Summary: system settings crashes on module systemd Classification: Applications Product: systemsettings Version: 5.25.5 Platform: Kubuntu OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: nospam.fos...@web.de Target Milestone: --- Application: systemsettings (5.25.5) Qt Version: 5.15.3 Frameworks Version: 5.98.0 Operating System: Linux 6.1.0-1006-oem x86_64 Windowing System: Wayland Distribution: Ubuntu 22.04.2 LTS DrKonqi: 5.25.5 [KCrashBackend] -- Information about the crash: KDE backports are used with wayland and kernel 6.1, so it is not a standard setup The reporter is unsure if this crash is reproducible. -- Backtrace: Application: Systemeinstellungen (systemsettings), signal: Aborted [KCrash Handler] #4 __pthread_kill_implementation (no_tid=0, signo=6, threadid=140699559549376) at ./nptl/pthread_kill.c:44 #5 __pthread_kill_internal (signo=6, threadid=140699559549376) at ./nptl/pthread_kill.c:78 #6 __GI___pthread_kill (threadid=140699559549376, signo=signo@entry=6) at ./nptl/pthread_kill.c:89 #7 0x7ff72f642476 in __GI_raise (sig=sig@entry=6) at ../sysdeps/posix/raise.c:26 #8 0x7ff72f6287f3 in __GI_abort () at ./stdlib/abort.c:79 #9 0x7ff72fe90ba3 in () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #10 0x7ff72d975e45 in () at /lib/x86_64-linux-gnu/libQt5WaylandClient.so.5 #11 0x7ff72d98611a in QtWaylandClient::QWaylandDisplay::flushRequests() () at /lib/x86_64-linux-gnu/libQt5WaylandClient.so.5 #12 0x7ff7300f17c8 in () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #13 0x7ff730113092 in QEventDispatcherGlib::processEvents(QFlags) () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #14 0x7ff7300b875b in QEventLoop::exec(QFlags) () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #15 0x7ff730ef879a in () at /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #16 0x7ff730ef88d4 in QMenu::exec(QPoint const&, QAction*) () at /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #17 0x7ff7011a1efc in () at /usr/lib/x86_64-linux-gnu/qt5/plugins/kcm_systemd.so #18 0x7ff7300f17c8 in () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #19 0x7ff730d94289 in QWidget::customContextMenuRequested(QPoint const&) () at /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #20 0x7ff730db0344 in QWidget::event(QEvent*) () at /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #21 0x7ff730e5d422 in QFrame::event(QEvent*) () at /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #22 0x7ff7300b9b9a in QCoreApplicationPrivate::sendThroughObjectEventFilters(QObject*, QEvent*) () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #23 0x7ff730d6c702 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #24 0x7ff730d73ca4 in QApplication::notify(QObject*, QEvent*) () at /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #25 0x7ff7300b9e3a in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #26 0x7ff730dc94a4 in () at /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #27 0x7ff730dcbfd5 in () at /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #28 0x7ff730d6c713 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #29 0x7ff7300b9e3a in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #30 0x7ff730541307 in QGuiApplicationPrivate::processMouseEvent(QWindowSystemInterfacePrivate::MouseEvent*) () at /lib/x86_64-linux-gnu/libQt5Gui.so.5 #31 0x7ff730516a2c in QWindowSystemInterface::sendWindowSystemEvents(QFlags) () at /lib/x86_64-linux-gnu/libQt5Gui.so.5 #32 0x7ff72d9bf174 in () at /lib/x86_64-linux-gnu/libQt5WaylandClient.so.5 #33 0x7ff72e851d3b in g_main_context_dispatch () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #34 0x7ff72e8a66c8 in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #35 0x7ff72e84f3e3 in g_main_context_iteration () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #36 0x7ff7301130b8 in QEventDispatcherGlib::processEvents(QFlags) () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #37 0x7ff7300b875b in QEventLoop::exec(QFlags) () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #38 0x7ff7300c0cf4 in QCoreApplication::exec() () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #39 0x563fb8ac50fd in () #40 0x7ff72f629d90 in __libc_start_call_main (main=main@entry=0x563fb8ac4610, argc=argc@entry=1, argv=argv@entry=0x7ffc06bc5f28) at ../sysdeps/nptl/libc_start_call_main.h:58 #41 0x7ff72f629e40 in __libc_start_main_impl (main=0x563fb8ac4610, argc=1, argv=0x7ffc06bc5f28, init=, fini=, rtld_fini=, stack_end=0x7ffc06bc5f18) at ../csu/libc-start.c:392 #42 0x563fb8ac5a65 in () [Inferior 1 (process 11523) detached] Reported using DrKonqi -- Yo
[dolphin] [Bug 466490] New: Crash when moving files to a mounted ŃFS share
https://bugs.kde.org/show_bug.cgi?id=466490 Bug ID: 466490 Summary: Crash when moving files to a mounted ŃFS share Classification: Applications Product: dolphin Version: 22.04.3 Platform: Kubuntu OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: nospam.fos...@web.de CC: kfm-de...@kde.org Target Milestone: --- Application: dolphin (22.04.3) Qt Version: 5.15.3 Frameworks Version: 5.98.0 Operating System: Linux 6.1.0-1006-oem x86_64 Windowing System: Wayland Distribution: Ubuntu 22.04.2 LTS DrKonqi: 5.25.5 [KCrashBackend] -- Information about the crash: Maybe related to KDE Backports packages in Kubuntu 22.04 and/or Kernel 6.1. Dolphin is not often affected by issues, mostly others which seem to result out of wayland instabilities on Kubuntu Plasma The reporter is unsure if this crash is reproducible. -- Backtrace: Application: Dolphin (dolphin), signal: Aborted [KCrash Handler] #4 __pthread_kill_implementation (no_tid=0, signo=6, threadid=140109058962880) at ./nptl/pthread_kill.c:44 #5 __pthread_kill_internal (signo=6, threadid=140109058962880) at ./nptl/pthread_kill.c:78 #6 __GI___pthread_kill (threadid=140109058962880, signo=signo@entry=6) at ./nptl/pthread_kill.c:89 #7 0x7f6db3242476 in __GI_raise (sig=sig@entry=6) at ../sysdeps/posix/raise.c:26 #8 0x7f6db32287f3 in __GI_abort () at ./stdlib/abort.c:79 #9 0x7f6db3a90ba3 in () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #10 0x7f6db199de45 in () at /lib/x86_64-linux-gnu/libQt5WaylandClient.so.5 #11 0x7f6db19ae11a in QtWaylandClient::QWaylandDisplay::flushRequests() () at /lib/x86_64-linux-gnu/libQt5WaylandClient.so.5 #12 0x7f6db19b748a in () at /lib/x86_64-linux-gnu/libQt5WaylandClient.so.5 #13 0x7f6db414d16b in QWindowPrivate::setVisible(bool) () at /lib/x86_64-linux-gnu/libQt5Gui.so.5 #14 0x7f6db418223c in QBasicDrag::startDrag() () at /lib/x86_64-linux-gnu/libQt5Gui.so.5 #15 0x7f6db19cf300 in QtWaylandClient::QWaylandDrag::startDrag() () at /lib/x86_64-linux-gnu/libQt5WaylandClient.so.5 #16 0x7f6db4180f92 in QBasicDrag::drag(QDrag*) () at /lib/x86_64-linux-gnu/libQt5Gui.so.5 #17 0x7f6db417e3e9 in QDragManager::drag(QDrag*) () at /lib/x86_64-linux-gnu/libQt5Gui.so.5 #18 0x7f6db417e73f in QDrag::exec(QFlags, Qt::DropAction) () at /lib/x86_64-linux-gnu/libQt5Gui.so.5 #19 0x7f6db6026b3d in KItemListController::startDragging() () at /lib/x86_64-linux-gnu/libdolphinprivate.so.5 #20 0x7f6db6028bf8 in KItemListController::mouseMoveEvent(QGraphicsSceneMouseEvent*, QTransform const&) () at /lib/x86_64-linux-gnu/libdolphinprivate.so.5 #21 0x7f6db602c629 in KItemListController::processEvent(QEvent*, QTransform const&) () at /lib/x86_64-linux-gnu/libdolphinprivate.so.5 #22 0x7f6db602f521 in KItemListView::event(QEvent*) () at /lib/x86_64-linux-gnu/libdolphinprivate.so.5 #23 0x7f6db496c713 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #24 0x7f6db3cb9e3a in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #25 0x7f6db4cabeb5 in () at /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #26 0x7f6db4cac271 in () at /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #27 0x7f6db4cb1dea in QGraphicsScene::mouseMoveEvent(QGraphicsSceneMouseEvent*) () at /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #28 0x7f6db4cbeac5 in QGraphicsScene::event(QEvent*) () at /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #29 0x7f6db496c713 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #30 0x7f6db3cb9e3a in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #31 0x7f6db4cdad0a in QGraphicsViewPrivate::mouseMoveEventHandler(QMouseEvent*) () at /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #32 0x7f6db49af4ee in QWidget::event(QEvent*) () at /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #33 0x7f6db4a5d422 in QFrame::event(QEvent*) () at /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #34 0x7f6db3cb9b9a in QCoreApplicationPrivate::sendThroughObjectEventFilters(QObject*, QEvent*) () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #35 0x7f6db496c702 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #36 0x7f6db4974364 in QApplication::notify(QObject*, QEvent*) () at /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #37 0x7f6db3cb9e3a in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #38 0x7f6db4972e47 in QApplicationPrivate::sendMouseEvent(QWidget*, QMouseEvent*, QWidget*, QWidget*, QWidget**, QPointer&, bool, bool) () at /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #39 0x00
[ktorrent] [Bug 473407] New: ktorrent doen't start anymore without almost immediately crashing
https://bugs.kde.org/show_bug.cgi?id=473407 Bug ID: 473407 Summary: ktorrent doen't start anymore without almost immediately crashing Classification: Applications Product: ktorrent Version: 22.04.3 Platform: Kubuntu OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: joris.guis...@gmail.com Reporter: nospam.fos...@web.de Target Milestone: --- Application: ktorrent (22.04.3) Qt Version: 5.15.3 Frameworks Version: 5.98.0 Operating System: Linux 6.1.0-1019-oem x86_64 Windowing System: X11 Distribution: Ubuntu 22.04.3 LTS DrKonqi: 5.25.5 [KCrashBackend] -- Information about the crash: Maybe related to a invlid certificate that is asked to confirm (meanwhile accepted permanently), ktorrent always crashes some seconds after start. Started from a shell: $ ktorrent KCrash: crashing... crashRecursionCounter = 2 KCrash: Application Name = ktorrent path = /usr/bin pid = 51907 KCrash: Arguments: /usr/bin/ktorrent KCrash: Attempting to start /usr/lib/x86_64-linux-gnu/libexec/drkonqi The crash can be reproduced every time. -- Backtrace: Application: KTorrent (ktorrent), signal: Segmentation fault [KCrash Handler] #4 0x7f0f4c0c194c in kt::MagnetManager::update() () at /lib/x86_64-linux-gnu/libktcore.so.16 #5 0x558ab74fbfdc in () #6 0x7f0f49ef1793 in () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f0f49ef57fe in QTimer::timeout(QTimer::QPrivateSignal) () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f0f49ee733f in QObject::event(QEvent*) () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #9 0x7f0f4ab6c713 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #10 0x7f0f49eb9e3a in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #11 0x7f0f49f123eb in QTimerInfoList::activateTimers() () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #12 0x7f0f49f12d34 in () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #13 0x7f0f48651d3b in g_main_context_dispatch () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #14 0x7f0f486a7258 in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #15 0x7f0f4864f3e3 in g_main_context_iteration () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #16 0x7f0f49f130b8 in QEventDispatcherGlib::processEvents(QFlags) () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #17 0x7f0f49eb875b in QEventLoop::exec(QFlags) () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #18 0x7f0f49ec0cf4 in QCoreApplication::exec() () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #19 0x558ab74eed8a in () #20 0x7f0f49429d90 in __libc_start_call_main (main=main@entry=0x558ab74e9bd0, argc=argc@entry=1, argv=argv@entry=0x7fffe79082d8) at ../sysdeps/nptl/libc_start_call_main.h:58 #21 0x7f0f49429e40 in __libc_start_main_impl (main=0x558ab74e9bd0, argc=1, argv=0x7fffe79082d8, init=, fini=, rtld_fini=, stack_end=0x7fffe79082c8) at ../csu/libc-start.c:392 #22 0x558ab74f0d75 in () [Inferior 1 (process 9191) detached] The reporter indicates this bug may be a duplicate of or related to bug 449120, bug 449121, bug 459271, bug 456207. Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[ktorrent] [Bug 473407] ktorrent doen't start anymore without almost immediately crashing
https://bugs.kde.org/show_bug.cgi?id=473407 Nikolai Försterling changed: What|Removed |Added CC||nospam.fos...@web.de -- You are receiving this mail because: You are watching all bug changes.
[ktorrent] [Bug 473407] ktorrent doen't start anymore without almost immediately crashing
https://bugs.kde.org/show_bug.cgi?id=473407 --- Comment #1 from Nikolai Försterling --- Created attachment 160978 --> https://bugs.kde.org/attachment.cgi?id=160978&action=edit New crash information added by DrKonqi ktorrent (22.04.3) using Qt 5.15.3 The last console output is: [warn] epoll_wait: Ungültiger Dateideskriptor [warn] epoll_wait: Ungültiger Dateideskriptor [warn] epoll_wait: Ungültiger Dateideskriptor (invalid file descriptor) The filesystem the torrents are written to/read from has no errors -- Backtrace (Reduced): #4 0x7f95ff5ab94c in kt::MagnetManager::update() () at /lib/x86_64-linux-gnu/libktcore.so.16 [...] #7 0x7f95fd4f57fe in QTimer::timeout(QTimer::QPrivateSignal) () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f95fd4e733f in QObject::event(QEvent*) () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #9 0x7f95fe16c713 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #10 0x7f95fd4b9e3a in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /lib/x86_64-linux-gnu/libQt5Core.so.5 -- You are receiving this mail because: You are watching all bug changes.
[ktorrent] [Bug 458057] Crash when a magnet torrent starts
https://bugs.kde.org/show_bug.cgi?id=458057 Nikolai Försterling changed: What|Removed |Added Platform|openSUSE|Kubuntu -- You are receiving this mail because: You are watching all bug changes.
[kresources] [Bug 180564] Inconsistant contact fields in eGroupware/KDE kresource
https://bugs.kde.org/show_bug.cgi?id=180564 --- Comment #9 from Nikolai Försterling --- (In reply to Justin Zobel from comment #8) > Thank you for reporting this issue in KDE software. As it has been a while > since this issue was reported, can we please ask you to see if you can > reproduce the issue with a recent software version? > > If you can reproduce the issue, please change the status to "REPORTED" when > replying. Thank you! Sorry for not having replied in 2018. Around 2011 i decided to no longer use EGW as i found it too elaborate to maintain my contact data there. And fiddling around with data inconsistencies and partial data loss in combination with SyncML and Akonadi and several clients almost froze my efforts to gain a reliable contact backend. Now for around 6 years i'm using CardDAV and CalDAV which work ok-ish for my needs, after some reformatting/cleanup and renounced info fields, it is finally ok for me on all my different clients and client programs. So this may be closed, even if unresolved. If it is important enough for other people, they may open own bugs, unfortunately i haven't got enough time to install/setup/test/verify that Nevertheless: thanks for supporting! -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 463539] New: Rotate digitizer input scheme together with screen (x11/wayland)
https://bugs.kde.org/show_bug.cgi?id=463539 Bug ID: 463539 Summary: Rotate digitizer input scheme together with screen (x11/wayland) Classification: Applications Product: systemsettings Version: 5.25.5 Platform: Kubuntu OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: nospam.fos...@web.de Target Milestone: --- SUMMARY *** If you have a laptop, which has a proper sensor to detect orientation (therefore screen rotation works here with wayland), it would be an advantage/nice/desirable/logical/needed/etc., if the builtin digitizer (Wacom HID) would rotate as well as the display does if you turn your laptop. *** STEPS TO REPRODUCE 1. login to x11 session you can specify rotation of the tablet, but not of the screen and vice versa OBSERVED RESULT Automatic screen rotation works, but the digitizer doesn't do as well, so that all apps (e.g. Xournal++) relying on tablet input can't be used as intended. EXPECTED RESULT Digitizer input layout should rotate together with the screen so that it fits together. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Kubuntu 22.04 (with kubuntu-backports enabled), Kernel 5.15.0-56-generic KDE Plasma Version: Plasma 5.25.5 KDE Frameworks Version: 5.98 Qt Version: 5.15.3 ADDITIONAL INFORMATION iio_sensor_proxy is active on Acer Spin SP313-51N In Wayland sessions, the settings-tab for the tablet says it's just for X11 sessions, whereas screen rotation for the display in the corresponding settings-tab isn't available. In X11 sessions, there's no option for screen rotation in display setting, but the tablet can be configured to rotate. $ xsetwacom --version 1.0.0 $ xsetwacom --list Wacom HID 49AF Pen stylus id: 9 type: STYLUS Wacom HID 49AF Finger touch id: 10 type: TOUCH Wacom HID 49AF Pen eraser id: 17 type: ERASER -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 463539] Rotate digitizer input scheme together with screen (x11/wayland)
https://bugs.kde.org/show_bug.cgi?id=463539 Nikolai Försterling changed: What|Removed |Added Keywords||wayland -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 463539] Rotate digitizer input scheme together with screen (x11/wayland)
https://bugs.kde.org/show_bug.cgi?id=463539 --- Comment #2 from Nikolai Försterling --- (In reply to Bug Janitor Service from comment #1) > Please note that Plasma 5.25.5 is not supported for much longer by KDE; > supported versions are 5.24, and 5.26 or newer. This issue has been present with 5.24, too. > If at all possible please upgrade to a supported version and verify that the > bug is still happening there. 5.26 would currently only be available with a development version of Kubuntu or eventually will be upgraded via Backports. > If you're unsure how to do this, contact your distributor about it. I'd really like to stay on an LTS version of Kubuntu (for obvious reasons) -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 463539] Rotate digitizer input scheme together with screen (x11/wayland)
https://bugs.kde.org/show_bug.cgi?id=463539
--- Comment #3 from Nikolai Försterling ---
I just double-checked some things.
On original Jammy (now on 5.24.7 with updates) there wasn't even a change of
the display resolution possible under wayland and due to some compatibility
issues with e.g syncthing-gtk and claws-mail i decided to go with x11 instead
of wayland.
After some time i added the backports and backports-extra ppa, but forgot to
activate the first one.
When I made up for it, there's a new item ("digitizer tablet") beside "graphics
tablet" (which still says "just under x11") under input devices that seems to
care about rotating like the screen.
And that really works (under wayland plasma 5.25.5).
So just left to do/fix seems to be activating rotating in the screen settings
under x11 (change bug to component kcm_kscreen?)
--
You are receiving this mail because:
You are watching all bug changes.
[Bluedevil] [Bug 306632] kde bluetooth wizard should bind rfcomm serial devices
https://bugs.kde.org/show_bug.cgi?id=306632 Nikolai Försterling changed: What|Removed |Added CC||nospam.fos...@web.de --- Comment #11 from Nikolai Försterling --- Here (Kubuntu 22.04, Plasma 5.25.5) the issue still persists, the common bluetooth stack can't connect to my device (Columbus V900 GPS Data Logger) even before i'm able to manually use rfcomm to connect a serial port. [bluetooth]# connect 00:18:E4:1F:5E:1F Attempting to connect to 00:18:E4:1F:5E:1F [CHG] Device 00:18:E4:1F:5E:1F Connected: yes [CHG] Device 00:18:E4:1F:5E:1F ServicesResolved: yes Failed to connect: org.bluez.Error.NotAvailable br-connection-profile-unavailable [CHG] Device 00:18:E4:1F:5E:1F ServicesResolved: no [CHG] Device 00:18:E4:1F:5E:1F Connected: no [bluetooth]# info 00:18:E4:1F:5E:1F Device 00:18:E4:1F:5E:1F (public) Name: GPS Data Logger Alias: GPS Data Logger Class: 0x1f00 Paired: yes Trusted: yes Blocked: no Connected: no LegacyPairing: no UUID: Serial Port (1101--1000-8000-00805f9b34fb) I tried blueman which can connect the serial port (under X11), but unfortunately segfaults under wayland. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 463539] Rotate digitizer input scheme together with screen (x11/wayland)
https://bugs.kde.org/show_bug.cgi?id=463539 --- Comment #5 from Nikolai Försterling --- (In reply to Nate Graham from comment #4) > Unfortunately this can't work on X11 for technical reasons. Could you point me to some detailed reason? As X11 can rotate manually, i assumed that it would be possible automatically as well. > It already works on Wayland in version 5.26 and later. So for the next few years, i'll have to decide at login screen choosing a session type if i want to use rotating on my tablet (and accept flaws in several programs with wayland) or use anything else without the ability to rotate. Not ideal, but i could deal with that. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 91943] sync with SyncML-Server (like www.mobical.net)
https://bugs.kde.org/show_bug.cgi?id=91943 --- Comment #8 from Nikolai Försterling --- Hi, for quite some time i use syncthing on my Linux desktops as well as my Android phone and additionally KDE Connect for data exchange. I gave up finding a proper solution for syncing addresses, phone numbers and calendar events, thus no longer wish for a solution via SyncML BR Am Dienstag, 9. März 2021, 06:46:48 CET schrieb Justin Zobel: > https://bugs.kde.org/show_bug.cgi?id=91943 > > --- Comment #7 from Justin Zobel --- > Thank you for the bug report. > > As this report hasn't seen any changes in 5 years or more, we ask if you can > please confirm that the issue still persists. > > If this bug is no longer persisting or relevant please change the status to > resolved. -- You are receiving this mail because: You are watching all bug changes.
[Elisa] [Bug 492353] New: Display only genres that are present in music library
https://bugs.kde.org/show_bug.cgi?id=492353 Bug ID: 492353 Summary: Display only genres that are present in music library Classification: Applications Product: Elisa Version: 23.08.5 Platform: Kubuntu OS: Linux Status: REPORTED Keywords: usability Severity: wishlist Priority: NOR Component: general Assignee: matthieu_gall...@yahoo.fr Reporter: nospam.fos...@web.de Target Milestone: --- Created attachment 173079 --> https://bugs.kde.org/attachment.cgi?id=173079&action=edit example for an empty genre that doesn't need to be shown in the genre list This is a feature request, not really a bug. While you can select (in the settings for left sidebar) to display the genre, it is a bit annoying, not particularly clear and effective, that there are all genres being shown and not just the genres that are present in my library So i suggest to display (or make that configurable) only genres that are set for at least one file in the music collection. That would even be helpful to get rid of wrong genres when you see them STEPS TO REPRODUCE 1. go to settings in the first drop-down menu (category to embed in the sidebar) 2. select "genres", apply and click "ok" 3. see the list of genres on the left side and click on some of them, many will show no result OBSERVED RESULT Many genres do not have files associated because they are not set im my library EXPECTED RESULT that overview should just display the genres i use SOFTWARE/OS VERSIONS Linux/KDE Plasma: Kubuntu 24.04 KDE Plasma Version: 5.27.11 KDE Frameworks Version: 5.115.0 Qt Version: 5.15.13 Similar to #150510 for amarok https://bugs.kde.org/show_bug.cgi?id=150510 -- You are receiving this mail because: You are watching all bug changes.
[Elisa] [Bug 492353] Display only genres that are present in music library
https://bugs.kde.org/show_bug.cgi?id=492353 --- Comment #1 from Nikolai Försterling --- Right now i'm not sure whether that request is valid. I have to clear all previous databases of Eliza and scan my collection again, it is possible that those empty genres are remains from former parts of my music. -- You are receiving this mail because: You are watching all bug changes.
[Elisa] [Bug 492353] Display only genres that are present in music library
https://bugs.kde.org/show_bug.cgi?id=492353 --- Comment #2 from Nikolai Försterling --- Ok, confirmed (test database from scratch) that every genre that is ever discovered in a collection is listet, regardless if currently used. Shouldn't they be hidden anyway when there're no songs related to them anymore? -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 477673] KDEConnect - sshfs finished with exit code 1 when attempting to browse
https://bugs.kde.org/show_bug.cgi?id=477673 Nikolai Försterling changed: What|Removed |Added CC||nospam.fos...@web.de --- Comment #14 from Nikolai Försterling --- The "debuild" hint for sshfs from here (https://bugs.kde.org/show_bug.cgi?id=477673#c11) together with an upgrade of kdeconnect app was the solution on my Kubuntu 24.04. Haven't checked whether that version of sshfs might be in backports repo to avoid building it. ii kdeconnect 23.08.5-0ubuntu5 amd64connect smartphones to your desktop devices ii sshfs 3.7.3-1.1build3 amd64filesystem client based on SSH File Transfer Protocol I had to install version 1.31 of the app from f-droid, in playstore it is still on 1.30 -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 419897] Error when accessing filesystem. sshfs finished with exit code 1
https://bugs.kde.org/show_bug.cgi?id=419897 Nikolai Försterling changed: What|Removed |Added CC||nospam.fos...@web.de --- Comment #38 from Nikolai Försterling --- Maybe it helps to see a solution on Kubuntu 24.04 from a parallel thread: The "debuild" hint for sshfs from here (https://bugs.kde.org/show_bug.cgi?id=477673#c11) together with an upgrade of kdeconnect app was the solution on my Kubuntu 24.04. Haven't checked whether that version of sshfs might be in backports repo to avoid building it. ii kdeconnect 23.08.5-0ubuntu5 amd64connect smartphones to your desktop devices ii sshfs 3.7.3-1.1build3 amd64filesystem client based on SSH File Transfer Protocol I had to install version 1.31 of the app from f-droid, in playstore it is still on 1.30 -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 443155] kdeconnect breaks when openssh is upgraded to version 8.8p1-1
https://bugs.kde.org/show_bug.cgi?id=443155 Nikolai Försterling changed: What|Removed |Added CC||nospam.fos...@web.de --- Comment #62 from Nikolai Försterling --- As people still seem to read this thread maybe it is helpful that there's a solution for Kubuntu 24.04 (just confirmed), maybe the solution for Arch is similar: The "debuild" hint for sshfs from here (https://bugs.kde.org/show_bug.cgi?id=477673#c11) together with an upgrade of kdeconnect app was the solution on my Kubuntu 24.04. Haven't checked whether that version of sshfs might be in backports repo to avoid building it. ii kdeconnect 23.08.5-0ubuntu5 amd64connect smartphones to your desktop devices ii sshfs 3.7.3-1.1build3 amd64filesystem client based on SSH File Transfer Protocol I had to install version 1.31 of the app from f-droid, in playstore it is still on 1.30 -- You are receiving this mail because: You are watching all bug changes.
[Oxygen] [Bug 378113] New: Continuation on package gtk3-engines-oxygen for current KDE5
https://bugs.kde.org/show_bug.cgi?id=378113 Bug ID: 378113 Summary: Continuation on package gtk3-engines-oxygen for current KDE5 Product: Oxygen Version: unspecified Platform: Kubuntu Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: gtk3-engine Assignee: hugo.pereira.da.co...@gmail.com Reporter: nospam.fos...@web.de CC: b7.10110...@gmail.com, hugo.pereira.da.co...@gmail.com, w...@adishatz.org Target Milestone: --- After migration to Kubuntu 16.10 (old 14.04 still running) i encountered that the package "gtk3-engines-oxygen" won't install anymore in KDE5 (Kubuntu Yakkety and KDE Backports) because of unresolved/broken dependencies to likgtk3. What i've read so far, the major issue should be that "engines" are no longer allowed within GTK3 themes and that all themes have to be pure css. Is there a chance to get the package gtk3-engines-oxygen continued for current KDE releases? I'd really like to get this back as it it the only theme beside Breeze (which i don't like) that lets the user keep QT and GTK3 applications have a consistent look and willing to spend time on this if there'd be a solution. -- You are receiving this mail because: You are watching all bug changes.
[Oxygen] [Bug 378113] Continuation on package gtk3-engines-oxygen for current KDE5
https://bugs.kde.org/show_bug.cgi?id=378113 --- Comment #1 from Nikolai Försterling --- It seems this bug is basically close to Bug 340288. I just set up a KDE dev account and do have some knowledge in CSS, but unfortunately none in creating theme engines or reverse-engineer and convert the to CSS. I do have the same opinion as Hussam (Oxygen was the face of KDE applications for long years) and would like to try to keep this alive even with the damaged relationship to GTK developers. If Darktable and Firefox were QT, who'd use GNOME? -- You are receiving this mail because: You are watching all bug changes.
[Oxygen] [Bug 378113] Continuation on package gtk3-engines-oxygen for current KDE5
https://bugs.kde.org/show_bug.cgi?id=378113 Nikolai Försterling changed: What|Removed |Added Resolution|--- |WONTFIX Status|UNCONFIRMED |RESOLVED --- Comment #3 from Nikolai Försterling --- Thank you very much Ruslan for your very detailed explanation! Sounds like huge effort, it really plunged me ... -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 378842] New: kate doesn't apply system theme/style for tabs (Kubuntu yakkety)
https://bugs.kde.org/show_bug.cgi?id=378842 Bug ID: 378842 Summary: kate doesn't apply system theme/style for tabs (Kubuntu yakkety) Product: kate Version: 16.08 Platform: Kubuntu Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: kwrite-bugs-n...@kde.org Reporter: devel2...@fosternet.de Target Milestone: --- Created attachment 105046 --> https://bugs.kde.org/attachment.cgi?id=105046&action=edit Style applied (background window), new kate session (middle) and screenshot of kate in Trusty with applied tab style kate: tabs' style stay at the default style "breeze" regardless what style i apply systemwide in system settings' style/appeareance (design and style "oxygen"). It is the only program within kubuntu 16.10 i recognized so far with this behaviour. When showing version in kate, it says 16.04 (rather than 16.10), is this just not being fully ported? -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 378842] kate doesn't apply system theme/style for tabs (Kubuntu yakkety)
https://bugs.kde.org/show_bug.cgi?id=378842 Nikolai Försterling changed: What|Removed |Added Keywords||reproducible -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 501040] KDE Connect - Half second display recognition of other Android Devices show up underneath 'KDE Connect Devices' heading for half a second then disappear:
https://bugs.kde.org/show_bug.cgi?id=501040 Nikolai Försterling changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE CC||nospam.fos...@web.de --- Comment #3 from Nikolai Försterling --- I think this glimpse of other devices is just another symptom of the same issue in https://bugs.kde.org/show_bug.cgi?id=501635 *** This bug has been marked as a duplicate of bug 501635 *** -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 501635] KDE Connect: Android 13 and Android 14 cannot search for each other, nor can they be added to the list by IP
https://bugs.kde.org/show_bug.cgi?id=501635 Nikolai Försterling changed: What|Removed |Added CC||globalun...@disroot.org --- Comment #2 from Nikolai Försterling --- *** Bug 501040 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 500960] Keine Geräte werden angezeigt
https://bugs.kde.org/show_bug.cgi?id=500960 Nikolai Försterling changed: What|Removed |Added CC||nospam.fos...@web.de Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED --- Comment #1 from Nikolai Försterling --- IMHO just one symptom of the bug https://bugs.kde.org/show_bug.cgi?id=501635 *** This bug has been marked as a duplicate of bug 501635 *** -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 500789] Can't see devices
https://bugs.kde.org/show_bug.cgi?id=500789 Nikolai Försterling changed: What|Removed |Added CC||nospam.fos...@web.de --- Comment #1 from Nikolai Försterling --- Maybe just a symptom of https://bugs.kde.org/show_bug.cgi?id=501635 -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 501742] Not all devices were found
https://bugs.kde.org/show_bug.cgi?id=501742 Nikolai Försterling changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |DUPLICATE --- Comment #3 from Nikolai Försterling --- Sounds like the same symptoms in the android app as in https://bugs.kde.org/show_bug.cgi?id=501635 *** This bug has been marked as a duplicate of bug 501635 *** -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 501635] KDE Connect: Android 13 and Android 14 cannot search for each other, nor can they be added to the list by IP
https://bugs.kde.org/show_bug.cgi?id=501635 Nikolai Försterling changed: What|Removed |Added CC||sp657yje...@mailbox.org --- Comment #4 from Nikolai Försterling --- *** Bug 501742 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 501635] KDE Connect: Android 13 and Android 14 cannot search for each other, nor can they be added to the list by IP
https://bugs.kde.org/show_bug.cgi?id=501635 --- Comment #6 from Nikolai Försterling --- Confirmed that switching back from v1.33.2 to v1.33.1 is a workaround, tested with 4 Android devices -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 433969] Unable to add ufw firewall rules with port ranges
https://bugs.kde.org/show_bug.cgi?id=433969 Nikolai Försterling changed: What|Removed |Added CC||devel2...@fosternet.de -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 501635] KDE Connect: Android 13 and Android 14 cannot search for each other, nor can they be added to the list by IP
https://bugs.kde.org/show_bug.cgi?id=501635 Nikolai Försterling changed: What|Removed |Added CC||nikolausri...@gmail.com --- Comment #3 from Nikolai Försterling --- *** Bug 500960 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 501635] KDE Connect: Android 13 and Android 14 cannot search for each other, nor can they be added to the list by IP
https://bugs.kde.org/show_bug.cgi?id=501635 Nikolai Försterling changed: What|Removed |Added Status|REPORTED|CONFIRMED CC||nospam.fos...@web.de Ever confirmed|0 |1 --- Comment #5 from Nikolai Försterling --- Confirmed here. this issue is still or again present in v1.33.2 of the Android app, although some reported this to be fixed in 1.33.1. Between v1.32 and the current v1.33.2 of the Android app there seems to be a new bug (or by intention?) introduced, Android devices (tested/verified with 5 devices Huawei,Xiaomi,Samsung), can't discover/connect each other anymore, regardless if successfully paired before or not. Completely bypassing/disabling Blockada and AFWall+ doesn't have an effect on this either. Interestingly the desktop app (in KDE, Kubuntu 22.04 and 24.04 and 25.04) is still able to connect and even see the filesystems and battery status and so on (likely all modules) from all Android devices and from Android the modules for remote input work as well. So "just" the Androids (10-14) don't see each other anymore, which is weird. I often used that for sharing the clipboard between mobile and pad :-/ Most of the times i use access to the Android's filesystem from the Laptop or Desktop, which still works, so to me it currently is not a major issue, but i think others may see a large impact to functionality. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 501742] Not all devices were found
https://bugs.kde.org/show_bug.cgi?id=501742 Nikolai Försterling changed: What|Removed |Added CC||nospam.fos...@web.de --- Comment #1 from Nikolai Försterling --- Confirmed here. this issue is still or again present in v1.33.2 of the Android app, although some reported this to be fixed in 1.33.1. Between v1.32 and the current v1.33.2 of the Android app there seems to be a new bug (or by intention?) introduced, Android devices (tested/verified with 5 devices Huawei,Xiaomi,Samsung), can't discover/connect each other anymore, regardless if successfully paired before or not. Completely bypassing/disabling Blockada and AFWall+ doesn't have an effect on this either. Interestingly the desktop app (in KDE, Kubuntu 22.04 and 24.04 and 25.04) is still able to connect and even see the filesystems and battery status and so on (likely all modules) from all Android devices and from Android the modules for remote input work as well. So "just" the Androids (10-14) don't see each other anymore, which is weird. I often used that for sharing the clipboard between mobile and pad :-/ Most of the times i use access to the Android's filesystem from the Laptop or Desktop, which still works, so to me it currently is not a major issue, but i think others may see a large impact to functionality. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 501742] Not all devices were found
https://bugs.kde.org/show_bug.cgi?id=501742 Nikolai Försterling changed: What|Removed |Added Component|common |android-application --- Comment #2 from Nikolai Försterling --- "component" should be changed to "android-application" as the desktop components (at least on Linux/Kubuntu) are not affected and can communicate between each other. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 501742] Not all devices were found
https://bugs.kde.org/show_bug.cgi?id=501742 Nikolai Försterling changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|CONFIRMED -- You are receiving this mail because: You are watching all bug changes.
