[systemsettings] [Bug 428907] Window Decorations config crashes
https://bugs.kde.org/show_bug.cgi?id=428907 Werner changed: What|Removed |Added CC||u4speed...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 465834] New: Kate crashes opening same file on different locations
https://bugs.kde.org/show_bug.cgi?id=465834 Bug ID: 465834 Summary: Kate crashes opening same file on different locations Classification: Applications Product: kate Version: 21.12.3 Platform: Ubuntu OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: general Assignee: kwrite-bugs-n...@kde.org Reporter: back.wer...@gmail.com Target Milestone: --- SUMMARY I have to edit files which are located in the same location (say /var/www/folder/foo.txt and sftp://some_server/var/www/folder/foo.txt). If I open one file and then the other one, Kate hangs forever. The second file doesn't show. STEPS TO REPRODUCE 1. Open File /var/www/folder/foo.txt 2. Create file sftp://some_server/var/www/folder/foo.txt 3. Try to open the remote file while letting the local file open OBSERVED RESULT Kate doesn't react anymore, the remote file does not show. If I open a file with a different filename on the server, it works. EXPECTED RESULT Opening both the remote and the local file. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Kubuntu Linux 22.04 KDE Plasma Version: 5.24.7 KDE Frameworks Version: 5.92.0 Qt Version: 5.15.3 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 413659] Option "Open folders during drag operations" has no effect on folders panel
https://bugs.kde.org/show_bug.cgi?id=413659 --- Comment #6 from Werner Lehmann --- (In reply to guimarcalsilva from comment #5) > This bug is not present with Plasma 5.26.5 and Dolphin 22.12.2. With the > option on, folders on the sidebar get opened as expected, while when it's > off, they do not. I tested with multiple views, folders, and file types. I'm I just tested it again, on Dolphin 22.12.1. Behaviour is unchanged on this version. The configuration option has an effect when dragging files over folders inside the file pane. Behaviour depends on the option then. But it does not when dragging files from the file pane to the folder pane. Anyway, maybe it was fixed with 22.12.2. I will test it again as soon as I get that version. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 413659] Option "Open folders during drag operations" has no effect on folders panel
https://bugs.kde.org/show_bug.cgi?id=413659
Werner Lehmann changed:
What|Removed |Added
Ever confirmed|1 |0
Resolution|FIXED |---
Status|RESOLVED|REPORTED
--- Comment #7 from Werner Lehmann ---
guimarcalsilva, I am changing status to REPORTED as per your suggestion because
on Dolphin 22.12.2, currently on Fedora 37, the issue is reproducible
unchanged. I am not sure which additional information I could provide over the
issue description. I already tried to keep it as succinct as possible.
However, I did the next best thing and looked at the Dolphin source code on
Github. The navigation option is bound to GeneralSettings::autoExpandFolders().
It affects two things:
1. The auto-activation delay in views/dolphinview.cpp:
const int delay = GeneralSettings::autoExpandFolders() ? 750 : -1;
m_container->controller()->setAutoActivationDelay(delay);
2. Same thing in panels/places/placespanel.cpp:
if (GeneralSettings::autoExpandFolders()) {
setDragAutoActivationDelay(750);
} else {
setDragAutoActivationDelay(0);
}
And that's it for references to this option. Note how it uses -1 versus 0
between both code locations. Not sure if that is intended. On the other hand,
panels/folders/folderspanel.cpp has this hardcoded:
m_controller->setAutoActivationDelay(750);
So there you have it. The folders pane does not respect this setting as far as
I can tell.
--
You are receiving this mail because:
You are watching all bug changes.
[krdc] [Bug 482950] KRDC RDP BLUE SCREEN SHOWS NOTHING
https://bugs.kde.org/show_bug.cgi?id=482950 Werner Llacer changed: What|Removed |Added CC||wlla...@gmail.com --- Comment #1 from Werner Llacer --- I'm having more or less the same problem. An already defined connection ends with a "not able to connect" dialog, but a new connection ends at a bluescreen . wlfreerdp & remmina can connect with no issues I'd see this bug as very serious Environment Archlinux , krdc 24.02.0, freerdp 2:2.11.4-1 This is what krdc shows : 1) On an already existing session ``` 10:19:28:059] [14791:14791] [WARN][com.freerdp.crypto] - Certificate verification failure 'self-signed certificate (18)' at stack position 0 [10:19:28:059] [14791:14791] [WARN][com.freerdp.crypto] - CN = sistemasremoto6.*** [10:19:28:366] [14791:14791] [ERROR][com.freerdp.core.transport] - BIO_read returned a system error 104: Conexión reinicializada por la máquina remota [10:19:28:366] [14791:14791] [ERROR][com.freerdp.core] - transport_read_layer:freerdp_set_last_error_ex ERRCONNECT_CONNECT_TRANSPORT_FAILED [0x0002000D] [10:19:28:796] [14791:14791] [ERROR][com.freerdp.core.transport] - BIO_read returned a system error 104: Conexión reinicializada por la máquina remota [10:19:28:796] [14791:14791] [ERROR][com.freerdp.core] - transport_read_layer:freerdp_set_last_error_ex ERRCONNECT_CONNECT_TRANSPORT_FAILED [0x0002000D] [10:19:28:797] [14791:14791] [ERROR][com.freerdp.core] - freerdp_post_connect failed KRDC: Unable to connect KRDC: ERRCONNECT_CONNECT_TRANSPORT_FAILED The connection transport layer failed. ``` For a new connection forget about certificate error ... ``` [10:20:19:999] [14791:14791] [WARN][com.freerdp.crypto] - Certificate verification failure 'self-signed certificate (18)' at stack position 0 [10:20:19:999] [14791:14791] [WARN][com.freerdp.crypto] - CN = sistemasremoto2.* [10:20:19:001] [14791:14791] [ERROR][com.freerdp.crypto] - @@@ [10:20:19:001] [14791:14791] [ERROR][com.freerdp.crypto] - @ WARNING: CERTIFICATE NAME MISMATCH! @ [10:20:19:001] [14791:14791] [ERROR][com.freerdp.crypto] - @@@ [10:20:19:001] [14791:14791] [ERROR][com.freerdp.crypto] - The hostname used for this connection (***.***.***.162:3389) [10:20:19:001] [14791:14791] [ERROR][com.freerdp.crypto] - does not match the name given in the certificate: [10:20:19:001] [14791:14791] [ERROR][com.freerdp.crypto] - Common Name (CN): [10:20:19:001] [14791:14791] [ERROR][com.freerdp.crypto] - sistemasremoto2.***.***.*** [10:20:19:001] [14791:14791] [ERROR][com.freerdp.crypto] - A valid certificate for the wrong name should NOT be trusted! [10:20:38:006] [14791:14791] [INFO][com.freerdp.gdi] - Local framebuffer format PIXEL_FORMAT_RGBA32 [10:20:38:006] [14791:14791] [INFO][com.freerdp.gdi] - Remote framebuffer format PIXEL_FORMAT_BGRA32 [10:20:38:017] [14791:14791] [INFO][com.freerdp.channels.rdpsnd.client] - [static] Loaded pulse backend for rdpsnd [10:20:38:018] [14791:14791] [INFO][com.freerdp.channels.drdynvc.client] - Loading Dynamic Virtual Channel rdpsnd [10:20:38:018] [14791:14791] [INFO][com.freerdp.channels.drdynvc.client] - Loading Dynamic Virtual Channel audin [10:20:38:021] [14791:14791] [INFO][com.freerdp.channels.audin.client] - Loaded pulse backend for audin [10:20:38:021] [14791:14791] [INFO][com.freerdp.channels.drdynvc.client] - Loading Dynamic Virtual Channel rdpgfx [10:20:39:247] [14791:14851] [INFO][com.freerdp.channels.rdpsnd.client] - [dynamic] Loaded pulse backend for rdpsnd ``` -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 434039] Memory details are missing
https://bugs.kde.org/show_bug.cgi?id=434039 --- Comment #4 from Nicolas Werner --- I'm sorry that I didn't reply originally. I had my email set to an old address and forgot about it. I'm very happy to see, that the memory view was kept though! So I think my reply is not really necessary, but I'll add it anyway: I do agree, that a dedicated application would probably make more sense, but I haven't found one yet, that displays that information in such a concise and easy to access manner. I usually use it to quickly figure out, where an application is using memory, since I have a lot of applications, that memory map files and seeing what is dirty, what are libraries, etc is very useful to me. It is also very useful, that one can see what files an application has loaded into memory, which can be used to figure out what libraries an application has still loaded into memory, what database it has open and more. It mostly became a habit to look there, because I am used to that view existing. I know, there are other ways to do that, but they are either not as convenient or I don't have the muscle memory for it. Thank you very much for keeping it around, I hope it isn't too big of a burden to maintain! -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 440126] Always requests system restart, often unnecessarily
https://bugs.kde.org/show_bug.cgi?id=440126 Werner Lehmann changed: What|Removed |Added CC||w...@dm17.com -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 435574] Unattended updates should only be used for packages that actually require a reboot
https://bugs.kde.org/show_bug.cgi?id=435574 Werner Lehmann changed: What|Removed |Added CC||w...@dm17.com -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 435770] New: Crash when loging out
https://bugs.kde.org/show_bug.cgi?id=435770 Bug ID: 435770 Summary: Crash when loging out Product: krunner Version: 5.19.5 Platform: Ubuntu Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: alexander.loh...@gmx.de Reporter: jwerne...@gmail.com CC: plasma-b...@kde.org Target Milestone: --- Application: krunner (5.19.5) Qt Version: 5.14.2 Frameworks Version: 5.74.0 Operating System: Linux 5.8.0-49-lowlatency x86_64 Windowing system: X11 Distribution: Ubuntu 20.10 -- Information about the crash: - What I was doing when the application crashed: Logging out of KDE session 1. clicked KDE's "start menu" button 2. selected "Leave" 3. selected "Log Out" 4. crash. This was tried 3 times in the same session with the same result. - Unusual behavior I noticed: Open GL drivers disappeared. May be related to recent 'apt dist-upgrade'. The crash can be reproduced sometimes. -- Backtrace: Application: krunner (krunner), signal: Aborted [KCrash Handler] #4 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:49 #5 0x7fb8920a8864 in __GI_abort () at abort.c:79 #6 0x7fb8924dbba3 in QMessageLogger::fatal(char const*, ...) const () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7fb89403eade in QSGRenderLoop::handleContextCreationFailure(QQuickWindow*, bool) () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #8 0x7fb89404098e in ?? () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #9 0x7fb89404177b in ?? () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #10 0x7fb892ad77c5 in QWindow::event(QEvent*) () from /lib/x86_64-linux-gnu/libQt5Gui.so.5 #11 0x55c06c41e253 in ?? () #12 0x7fb89323a013 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #13 0x7fb8926f81ca in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #14 0x7fb892acc9a1 in QGuiApplicationPrivate::processExposeEvent(QWindowSystemInterfacePrivate::ExposeEvent*) () from /lib/x86_64-linux-gnu/libQt5Gui.so.5 #15 0x7fb892aa12bb in QWindowSystemInterface::sendWindowSystemEvents(QFlags) () from /lib/x86_64-linux-gnu/libQt5Gui.so.5 #16 0x7fb88dda235e in ?? () from /lib/x86_64-linux-gnu/libQt5XcbQpa.so.5 #17 0x7fb890cc962b in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #18 0x7fb890cc98d8 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #19 0x7fb890cc99a3 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #20 0x7fb89274f843 in QEventDispatcherGlib::processEvents(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #21 0x7fb8926f6a4b in QEventLoop::exec(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #22 0x7fb8926fefc6 in QCoreApplication::exec() () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #23 0x55c06c41ca70 in ?? () #24 0x7fb8920aacb2 in __libc_start_main (main=0x55c06c41c4a0, argc=1, argv=0x7ffe7d504f38, init=, fini=, rtld_fini=, stack_end=0x7ffe7d504f28) at ../csu/libc-start.c:314 #25 0x55c06c41cbce in _start () [Inferior 1 (process 214026) detached] Possible duplicates by query: bug 430419, bug 429344, bug 427384, bug 426250, bug 425662. Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 429472] New: Crash when right clicking on empty area
https://bugs.kde.org/show_bug.cgi?id=429472 Bug ID: 429472 Summary: Crash when right clicking on empty area Product: systemsettings Version: 5.19.5 Platform: Fedora RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: w...@dm17.com Target Milestone: --- Application: systemsettings5 (5.19.5) Qt Version: 5.15.1 Frameworks Version: 5.75.0 Operating System: Linux 5.9.8-200.fc33.x86_64 x86_64 Windowing system: X11 Distribution: Fedora 33 (KDE Plasma) -- Information about the crash: In the systemd plasmoid a crash can always be reproduced as follows: 1. Filter units to show only timers. 2. Right click on an empty space in the list (without a list item under the mouse cursor). The crash can be reproduced every time. -- Backtrace: Application: System Settings (systemsettings5), signal: Segmentation fault [KCrash Handler] #4 0x7f7b34a24080 in kcmsystemd::slotUnitContextMenu(QPoint const&) () from /usr/lib64/qt5/plugins/kcm_systemd.so #5 0x7f7b6e743290 in void doActivate(QObject*, int, void**) () from /lib64/libQt5Core.so.5 #6 0x7f7b6f131f85 in QWidget::customContextMenuRequested(QPoint const&) () from /lib64/libQt5Widgets.so.5 #7 0x7f7b6f14cd45 in QWidget::event(QEvent*) () from /lib64/libQt5Widgets.so.5 #8 0x7f7b6f1f425e in QFrame::event(QEvent*) () from /lib64/libQt5Widgets.so.5 #9 0x7f7b6e7149a5 in QCoreApplicationPrivate::sendThroughObjectEventFilters(QObject*, QEvent*) () from /lib64/libQt5Core.so.5 #10 0x7f7b6f10c14e in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib64/libQt5Widgets.so.5 #11 0x7f7b6f113cc3 in QApplication::notify(QObject*, QEvent*) () from /lib64/libQt5Widgets.so.5 #12 0x7f7b6e714be8 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib64/libQt5Core.so.5 #13 0x7f7b6f164b46 in QWidgetWindow::handleMouseEvent(QMouseEvent*) () from /lib64/libQt5Widgets.so.5 #14 0x7f7b6f16734e in QWidgetWindow::event(QEvent*) () from /lib64/libQt5Widgets.so.5 #15 0x7f7b6f10c15f in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib64/libQt5Widgets.so.5 #16 0x7f7b6e714be8 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib64/libQt5Core.so.5 #17 0x7f7b6eb088f0 in QGuiApplicationPrivate::processMouseEvent(QWindowSystemInterfacePrivate::MouseEvent*) () from /lib64/libQt5Gui.so.5 #18 0x7f7b6eaea94b in QWindowSystemInterface::sendWindowSystemEvents(QFlags) () from /lib64/libQt5Gui.so.5 #19 0x7f7b5c6d82aa in xcbSourceDispatch(_GSource*, int (*)(void*), void*) () from /lib64/libQt5XcbQpa.so.5 #20 0x7f7b6c584fd7 in g_main_context_dispatch () from /lib64/libglib-2.0.so.0 #21 0x7f7b6c5d5d88 in g_main_context_iterate.constprop () from /lib64/libglib-2.0.so.0 #22 0x7f7b6c58241f in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #23 0x7f7b6e75fa2f in QEventDispatcherGlib::processEvents(QFlags) () from /lib64/libQt5Core.so.5 #24 0x7f7b6e71364b in QEventLoop::exec(QFlags) () from /lib64/libQt5Core.so.5 #25 0x7f7b6e71b010 in QCoreApplication::exec() () from /lib64/libQt5Core.so.5 #26 0x55d695991fa8 in main () [Inferior 1 (process 16756) detached] Possible duplicates by query: bug 429412, bug 429376, bug 429344, bug 429267, bug 429183. Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 462269] "Show Target" on relative symlinks does not work anymore since 22.0X
https://bugs.kde.org/show_bug.cgi?id=462269 Werner Lehmann changed: What|Removed |Added CC||w...@dm17.com -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 462269] "Show Target" on relative symlinks does not work anymore since 22.0X
https://bugs.kde.org/show_bug.cgi?id=462269 --- Comment #1 from Werner Lehmann --- I can confirm this bug on Fedora 37, same version of Dolphin. Plus related other issues with symlink handling: mkdir -p linktargets touch 'linktargets/file' 'linktargets/file # file' for x in linktargets/* ; do ln -s "$x"; done This produces $ tree . ├── file -> linktargets/file ├── file # file -> linktargets/file # file └── linktargets ├── file └── file # file For the link named "file": 1) "Show Target" does not work on any of the links. As reported with this ticket. 2) The status bar shows issue #456198. When selecting this link, the status bar reads: file (empty document, Link to file:///home/wl/var/test/file) It should be file (empty document, Link to file:///home/wl/var/test/linktarget/file) For the link named "file # file": 3) The status bar reads: file # file (empty document, Link to file:///home/wl/var/test/file %23 file) It should be file (empty document, Link to file:///home/wl/var/test/linktarget/file # file) 4) The properties dialog, button ">.", does not resolve the link but shows a warning: The file or folder /home/wl/var/test/linktargets/file does not exist. It should resolve and jump to the link instead. Apparently it cuts everything off after the hash symbol. Note that column "Link Destination" in the file list always shows the correct value. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 456198] Targets of relative symbolic links are resolved is incorrectly
https://bugs.kde.org/show_bug.cgi?id=456198 Werner Lehmann changed: What|Removed |Added CC||w...@dm17.com -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 406775] Add "Show Target in New Window" and "Show Target in New Tab" options for symlink context menus
https://bugs.kde.org/show_bug.cgi?id=406775 Werner Lehmann changed: What|Removed |Added CC||w...@dm17.com -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 462269] "Show Target" on relative symlinks does not work anymore since 22.0X
https://bugs.kde.org/show_bug.cgi?id=462269 Werner Lehmann changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=456198 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 456198] Targets of relative symbolic links are resolved is incorrectly
https://bugs.kde.org/show_bug.cgi?id=456198 Werner Lehmann changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=462269 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 456198] Targets of relative symbolic links are resolved is incorrectly
https://bugs.kde.org/show_bug.cgi?id=456198 Werner Lehmann changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=461672 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 461672] On a folder symlink, "Link to" shows the name of the link, not where it points
https://bugs.kde.org/show_bug.cgi?id=461672 Werner Lehmann changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=456198 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 460126] Previews are not cached (remote fs)
https://bugs.kde.org/show_bug.cgi?id=460126 Werner Lehmann changed: What|Removed |Added CC||w...@dm17.com -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 462269] "Show Target" on relative symlinks does not work anymore since 22.0X
https://bugs.kde.org/show_bug.cgi?id=462269 Werner Lehmann changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=459154 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 459154] Dolphin doesn't reliably show a symlink original
https://bugs.kde.org/show_bug.cgi?id=459154 Werner Lehmann changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=462269 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 462269] "Show Target" on relative symlinks does not work anymore since 22.0X
https://bugs.kde.org/show_bug.cgi?id=462269 --- Comment #4 from Werner Lehmann --- I am now also on Dolphin 22.12.0 (Fedora 37). "Show Target" in the link's context menu opens a new Dolphin window with the expected location for me now. I don't see more than one window. However, this used to be a new tab, not a new window. This sort of resolves the originally reported issue for me, although I'd really prefer to get a new tab. Issues 2, 3, 4 reported in comment 1 remain though. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 462269] "Show Target" on relative symlinks does not work anymore since 22.0X
https://bugs.kde.org/show_bug.cgi?id=462269 --- Comment #5 from Werner Lehmann --- I did not realize it before but actually this also depends on whether the link points to a directory or to a file. For file links everything is as described before including the remaining issues. "Show Target" opens a new window with the containing directory of the link target. I guess this has not been different before. A new tab would be nice. For directory links there is more control. A (double)click opens the link target in the same tab. The context menu allows to open it in a new tab or a new window. And "Show Target" opens a new window with the link target location (the parent directory). -- You are receiving this mail because: You are watching all bug changes.
[marble] [Bug 376626] View does not recenter after loading of file
https://bugs.kde.org/show_bug.cgi?id=376626 Werner Stille changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- --- Comment #2 from Werner Stille --- Thank you for noticing my bug report. The issue can be reproduced with the current version 22.08.2 of marble, and again can be cured by the suggested patch, i. e. by changing the call FileManager::addFile() in MarbleWidget::model()->addGeoDataFile() (in MarbleModel.cpp) to: d->m_fileManager.addFile( filename, filename, GeoDataStyle::Ptr(), UserDocument, 0, true ); -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 446549] Digital signature feature confusing for new users
https://bugs.kde.org/show_bug.cgi?id=446549 Nicolas Werner changed: What|Removed |Added CC||nicolas.wer...@ymail.com --- Comment #11 from Nicolas Werner --- I agree. Just replacing digital signatures with a drawing does not sound like a good approach to me. As a user I would much prefer having an easy way to create a certificate, even if it is untrusted. The current docs are sadly not helpful enough to get me started. I would instead prefer getting a dialog box, that allows me to setup a cert, if I don't have one and use that. That is actually what I am looking for when pressing the "Digitally sign" button, I just can't get past the certificate creation step. -- You are receiving this mail because: You are watching all bug changes.
[kde-cli-tools] [Bug 431864] New: matrix: scheme tries to open kio slave
https://bugs.kde.org/show_bug.cgi?id=431864
Bug ID: 431864
Summary: matrix: scheme tries to open kio slave
Product: kde-cli-tools
Version: 5.20.4
Platform: Gentoo Packages
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: general
Assignee: aleix...@kde.org
Reporter: nicolas.wer...@ymail.com
Target Milestone: ---
SUMMARY
I registered a my application as a handler for the matrix: scheme, see here:
https://github.com/Nheko-Reborn/nheko/blob/f47bedff23400e3b0788891f0ab0257dfc03a447/resources/nheko.desktop#L11
When installed globally, xdg-open works if I set the desktop platform to
generic like this:
XDG_CURRENT_DESKTOP="X-Generic" xdg-open
'matrix:user/test:neko.dev?action=chat'
But if I use the default or kde-open5, it fails to open my application and
complains about matrix: being an unknown protocol. It seems to know about my
application though.
STEPS TO REPRODUCE
1. Install Nheko 0.8.0
2. xdg-open a matrix URI, like matrix:user/test:neko.dev?action=chat
3. Watch it not open Nheko but instead open an error message box.
OBSERVED RESULT
# LANG=C kde-open5 --interactive matrix:user/asdfhajsdf
command= "nheko" args= ("nheko", "matrix:user/asdfhajsdf")
kf.kio.core: Protocol Class of url QUrl("matrix:user/asdfhajsdf") , isn't
':local', cancelling job.
Copying QUrl("matrix:user/asdfhajsdf") to
QUrl("file:///home/nicolas/.cache/kioexec/krun/18898_0/asdfhajsdf")
kf.kio.core: couldn't create slave: "klauncher said: Unbekanntes Protokoll
?matrix?.\n"
All files downloaded, will call slotRunApp shortly
No files downloaded -> exiting
EXPECTED RESULT
It opens Nheko.
SOFTWARE/OS VERSIONS
Windows:
macOS:
Linux/KDE Plasma: 5.20.4
(available in About System)
KDE Plasma Version: 5.20.4
KDE Frameworks Version: 5.77.0
Qt Version: 5.15.2
ADDITIONAL INFORMATION
(No idea, if this is the right component)
--
You are receiving this mail because:
You are watching all bug changes.
[plasma-systemmonitor] [Bug 437651] New: System Monitor crash on quit
https://bugs.kde.org/show_bug.cgi?id=437651 Bug ID: 437651 Summary: System Monitor crash on quit Product: plasma-systemmonitor Version: 5.21.5 Platform: Fedora RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: ksysguard-b...@kde.org Reporter: w...@dm17.com CC: ahiems...@heimr.nl, plasma-b...@kde.org Target Milestone: --- Application: plasma-systemmonitor (5.21.5) Qt Version: 5.15.2 Frameworks Version: 5.81.0 Operating System: Linux 5.11.19-300.fc34.x86_64 x86_64 Windowing System: X11 Drkonqi Version: 5.21.5 Distribution: Fedora 34 (KDE Plasma) -- Information about the crash: - What I was doing when the application crashed: System monitor was on the history page when I closed it. Crash occurred immediately afterwards. The reporter is unsure if this crash is reproducible. -- Backtrace: Application: System Monitor (plasma-systemmonitor), signal: Segmentation fault [KCrash Handler] #4 0x7f220eb7506f in QQuickItem::setVisible(bool) () from /lib64/libQt5Quick.so.5 #5 0x7f21ffaf686a in ToolBarLayoutDelegate::ensureItemVisibility() () from /usr/lib64/qt5/qml/org/kde/kirigami.2/libkirigamiplugin.so #6 0x7f22214724b0 in void doActivate(QObject*, int, void**) () from /lib64/libQt5Core.so.5 #7 0x7f220eb778cb in QQuickItemPrivate::setEffectiveVisibleRecur(bool) () from /lib64/libQt5Quick.so.5 #8 0x7f220eb7b119 in QQuickItem::setParentItem(QQuickItem*) () from /lib64/libQt5Quick.so.5 #9 0x7f220eb6fa5a in QQuickItem::~QQuickItem() () from /lib64/libQt5Quick.so.5 #10 0x7f21ff4dd242 in QQmlPrivate::QQmlElement::~QQmlElement() () from /usr/lib64/qt5/qml/QtQuick/Templates.2/libqtquicktemplates2plugin.so #11 0x7f21ffaf75fa in ToolBarLayoutDelegate::~ToolBarLayoutDelegate() () from /usr/lib64/qt5/qml/org/kde/kirigami.2/libkirigamiplugin.so #12 0x7f21ffaf769a in std::_Hashtable > >, std::allocator > > >, std::__detail::_Select1st, std::equal_to, std::hash, std::__detail::_Mod_range_hashing, std::__detail::_Default_ranged_hash, std::__detail::_Prime_rehash_policy, std::__detail::_Hashtable_traits >::_M_erase(unsigned long, std::__detail::_Hash_node_base*, std::__detail::_Hash_node > >, false>*) () from /usr/lib64/qt5/qml/org/kde/kirigami.2/libkirigamiplugin.so #13 0x7f21ffaf7a40 in QtPrivate::QFunctorSlotObject, void>::impl(int, QtPrivate::QSlotObjectBase*, QObject*, void**, bool*) () from /usr/lib64/qt5/qml/org/kde/kirigami.2/libkirigamiplugin.so #14 0x7f22214724b0 in void doActivate(QObject*, int, void**) () from /lib64/libQt5Core.so.5 #15 0x7f222146caa3 in QObject::destroyed(QObject*) () from /lib64/libQt5Core.so.5 #16 0x7f222146f10a in QObject::~QObject() () from /lib64/libQt5Core.so.5 #17 0x7f21ff4de89f in QQmlPrivate::QQmlElement::~QQmlElement() () from /usr/lib64/qt5/qml/QtQuick/Templates.2/libqtquicktemplates2plugin.so #18 0x7f2221468eda in QObjectPrivate::deleteChildren() () from /lib64/libQt5Core.so.5 #19 0x7f222146f184 in QObject::~QObject() () from /lib64/libQt5Core.so.5 #20 0x7f21fbad89d9 in QQmlPrivate::QQmlElement::~QQmlElement() () from /usr/lib64/qt5/qml/org/kde/ksysguard/faces/libFacesPlugin.so #21 0x7f2221468eda in QObjectPrivate::deleteChildren() () from /lib64/libQt5Core.so.5 #22 0x7f222146f184 in QObject::~QObject() () from /lib64/libQt5Core.so.5 #23 0x7f21ff948fdd in KSysGuard::SensorFaceController::~SensorFaceController() () from /lib64/libKSysGuardSensorFaces.so.1 #24 0x7f2221468eda in QObjectPrivate::deleteChildren() () from /lib64/libQt5Core.so.5 #25 0x7f222146f184 in QObject::~QObject() () from /lib64/libQt5Core.so.5 #26 0x5634ab347999 in main () [Inferior 1 (process 2506894) detached] Possible duplicates by query: bug 436863, bug 435427, bug 432084, bug 431077, bug 429973. Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 434037] New: Application page should be hidden on unsupported systems
https://bugs.kde.org/show_bug.cgi?id=434037 Bug ID: 434037 Summary: Application page should be hidden on unsupported systems Product: plasma-systemmonitor Version: 5.21.2 Platform: Gentoo Packages OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: general Assignee: ksysguard-b...@kde.org Reporter: nicolas.wer...@ymail.com CC: ahiems...@heimr.nl, plasma-b...@kde.org Target Milestone: --- Created attachment 136421 --> https://bugs.kde.org/attachment.cgi?id=136421&action=edit Screenshot of the empty application page SUMMARY On systems without systemd, the application page is just empty. That is pretty confusing. Either show, that it is unsupported or hide the page alltogether. STEPS TO REPRODUCE 1. Install a distro without systemd 2. Open system monitor 3. Navigate to applications page OBSERVED RESULT Empty application page. EXPECTED RESULT No page or a hint, why it is empty. SOFTWARE/OS VERSIONS Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.21.2 KDE Frameworks Version: 5.79.0 Qt Version: 5.15.2 -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 434039] New: Memory details are missing
https://bugs.kde.org/show_bug.cgi?id=434039 Bug ID: 434039 Summary: Memory details are missing Product: plasma-systemmonitor Version: 5.21.2 Platform: Gentoo Packages OS: Linux Status: REPORTED Severity: major Priority: NOR Component: general Assignee: ksysguard-b...@kde.org Reporter: nicolas.wer...@ymail.com CC: ahiems...@heimr.nl, plasma-b...@kde.org Target Milestone: --- Created attachment 136422 --> https://bugs.kde.org/attachment.cgi?id=136422&action=edit Memory details view in Ksysguard SUMMARY KSysguard used to provide detailed memory information about where and what memory is used. While it is unfortunate, that this was rendered in a WebView, this view alone is my primary reason for using KSysguard. Since KSysguard is going to be replaced (I'm told), systemmonitor should provide the same or an equivalent view. You can find the view in Ksysguard by going to the process view and right clicking on a process. OBSERVED RESULT No memory detail view in the replacement for KSysguard. EXPECTED RESULT A memory detail view, that is at least as powerful as the tool, that it is intended to replace. SOFTWARE/OS VERSIONS Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.21.2 KDE Frameworks Version: 5.79.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION KSysguard is always the first KDE tool I install on a new system, specifically, because the memory overview is much more powerful than tools like htop provide. I really don't want to use one of my most used features, just to make a nicer looking tool. -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 434040] New: Default CPU usage graph scales badly to 16+ cores
https://bugs.kde.org/show_bug.cgi?id=434040 Bug ID: 434040 Summary: Default CPU usage graph scales badly to 16+ cores Product: plasma-systemmonitor Version: 5.21.2 Platform: Gentoo Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: ksysguard-b...@kde.org Reporter: nicolas.wer...@ymail.com CC: ahiems...@heimr.nl, plasma-b...@kde.org Target Milestone: --- Created attachment 136423 --> https://bugs.kde.org/attachment.cgi?id=136423&action=edit Comparison of the old and new graphs with different settings and sizes SUMMARY There are multiple issues here. In the default size, the percentages below the CPU graph are unreadable. This should be partially fixed by https://invent.kde.org/frameworks/kquickcharts/-/merge_requests/28 But KSysguard solved that more nicely, by first shrinking the legend to just colored percentages. You should still wrap them at some point, because otherwise 48 threads will fit on pretty much no screen, but having a colored line next to it is not very useful at that size. Secondly, the default of using a stacked chart leads to a chart going to 1600%, but because only one core is pinned, that one sits at 1/16th of the chart. This does not provide much useful information about why an application hangs, since it looks like it is hanging in IO instead of in a CPU loop. Third, there is no actual unstacked line graph mode. The only option is a line mode with everything below it filled, which is very hard to read and to recognize patterns in (i.e. everything spiked to 100% but with some drops here and there to 0). KSysguard solved that by having the area below the line half transparent, which allowed you to see all the lines in any case. STEPS TO REPRODUCE 1. Open CPU widget on a system with 16 cores or more OBSERVED RESULT Badly scaled CPU graph, that hides half the information. EXPECTED RESULT CPU graph that shows information of all CPU cores at a glance. SOFTWARE/OS VERSIONS Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.21.2 KDE Frameworks Version: 5.79.0 Qt Version: 5.15.2 -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 434041] New: Labels in memory overview overlap and curve is wrong at the start
https://bugs.kde.org/show_bug.cgi?id=434041 Bug ID: 434041 Summary: Labels in memory overview overlap and curve is wrong at the start Product: plasma-systemmonitor Version: 5.21.2 Platform: Gentoo Packages OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: general Assignee: ksysguard-b...@kde.org Reporter: nicolas.wer...@ymail.com CC: ahiems...@heimr.nl, plasma-b...@kde.org Target Milestone: --- Created attachment 136424 --> https://bugs.kde.org/attachment.cgi?id=136424&action=edit Screenshot of graph SUMMARY When opening the memory use history initially, it for some reason overlapped the labels of swap and memory use? Also the line starts out very weirdly. The memory usage profile was flat for the last 10 hours, but the widgets shows a few weird jumps in the beginning. This is probably related to the smoothing? All of that fixes itself after waiting for a bit and/or switching tabs. STEPS TO REPRODUCE 1. Open system monitor 2. Go to history tab OBSERVED RESULT See intro EXPECTED RESULT Labels don't overlap and curve goes smoothly or sharply from 0 to 53 instead of wiggling at the start and end. SOFTWARE/OS VERSIONS Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.21.2 KDE Frameworks Version: 5.79.0 Qt Version: 5.15.2 -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 434041] Labels in memory overview overlap and curve is wrong at the start
https://bugs.kde.org/show_bug.cgi?id=434041 --- Comment #1 from Nicolas Werner --- Woops, this is probably a duplicate of https://bugs.kde.org/show_bug.cgi?id=429156 -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 434042] New: Sensor browser is hard to navigate with a mouse
https://bugs.kde.org/show_bug.cgi?id=434042 Bug ID: 434042 Summary: Sensor browser is hard to navigate with a mouse Product: plasma-systemmonitor Version: 5.21.2 Platform: Gentoo Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: ksysguard-b...@kde.org Reporter: nicolas.wer...@ymail.com CC: ahiems...@heimr.nl, plasma-b...@kde.org Target Milestone: --- Created attachment 136425 --> https://bugs.kde.org/attachment.cgi?id=136425&action=edit Sensor browser using half the screen height and sorting cores wrong as well as missing information what is being added and where you are. SUMMARY When selecting sensors, you are always presented with a new list with almost no context or hinting if you are currently adding a sensor or just opening another nested list. There is also no context of how deep you currently are and where you can go back to as well as no easy (or no intuitive) way to go back to the top. Also the view sometimes doesn't fill all the available vertical space and leaves a blank space. The lists are also sorted wrong, where core 11 will come after core 2. I feel like this would be much easier to navigate, if this was a tree view, that you could collapse and uncollapse as needed. SOFTWARE/OS VERSIONS Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.21.2 KDE Frameworks Version: 5.79.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION The attached screenshot shows me trying to temperature sensors for my CPUs. I have no idea, what menu I clicked on to get there. I have no idea, what clicking any of those things does and when I click on "all" something completely different happens than clicking on an individual core. It took me 2 minutes to get to the same menu again by accident and then figuring out that there ARE temperature sensors for the individual cores, just not for all cores and I need to click them manually each time. I however did not do that in the end, since I do not want to navigate to the same menu 16 times, which needs 16*3 + 2 = 50 clicks, more if you ever click out of that screen by accident. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 413659] New: Option "Open folders during drag operations" has no effect on folders panel
https://bugs.kde.org/show_bug.cgi?id=413659 Bug ID: 413659 Summary: Option "Open folders during drag operations" has no effect on folders panel Product: dolphin Version: 19.04.3 Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: panels: folders Assignee: dolphin-bugs-n...@kde.org Reporter: w...@dm17.com CC: kfm-de...@kde.org Target Milestone: --- During drag operation into the folders pane the folders always expand automatically even though option "Open folders during drag operations" is off. STEPS TO REPRODUCE 1. Switch off optio "Open folders during drag operations" 2. Drag a file into a folder on the folder pane. OBSERVED RESULT If folder has subfolders, it is expanded automatically. EXPECTED RESULT Drag target folder not expanded while option "Open folders during drag operations" is off. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Kubuntu 19.10 with Plasma backports KDE Plasma Version: 5.17.2 KDE Frameworks Version: 5.62.0 Qt Version: 5.12.4 ADDITIONAL INFORMATION It appears as if the option is used only during drags inside of the details view mode with expandable folders. In this case it would be more logical to make this a suboption of this view mode. Currently the option is located in the "navigation" area of the preferences dialog. However, I would much prefer to have it working with the folders panel, too. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 413660] New: Natural sorting not working as documented
https://bugs.kde.org/show_bug.cgi?id=413660 Bug ID: 413660 Summary: Natural sorting not working as documented Product: dolphin Version: 19.04.3 Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: view-engine: general Assignee: dolphin-bugs-n...@kde.org Reporter: w...@dm17.com CC: kfm-de...@kde.org Target Milestone: --- SUMMARY Natural sorting does not sort numbers in filenames (anymore?). The example in the Dolphin manual does not work like documented. STEPS TO REPRODUCE 1. Enable natural sorting. 2. In a test folder, create test files: "touch File1 File2 File10" OBSERVED RESULT Regardless of selected sort order in Dolphin preferences, files are always sorted like this: File1 File10 File2 EXPECTED RESULT In natural sort order, files are sorted like this: File1 File2 File10 SOFTWARE/OS VERSIONS Linux/KDE Plasma: Kubuntu 19.10 with Plasma backports KDE Plasma Version: 5.17.2 KDE Frameworks Version: 5.62.0 Qt Version: 5.12.4 ADDITIONAL INFORMATION The reproducible example is taken from the Dolphin manual, see https://docs.kde.org/stable5/en/applications/dolphin/configuring-dolphin.html See also the result of ls with -v option: $ ls -v File1 File2 File10 $ ls File1 File10 File2 Reading other bugs I realize that this may be related to locale. This is my locale info: LANG=en_US.UTF-8 LANGUAGE=en_US:de LC_CTYPE="en_US.UTF-8" LC_NUMERIC=de_DE.UTF-8 LC_TIME=de_DE.UTF-8 LC_COLLATE="en_US.UTF-8" LC_MONETARY=de_DE.UTF-8 LC_MESSAGES=POSIX LC_PAPER=de_DE.UTF-8 LC_NAME=de_DE.UTF-8 LC_ADDRESS=de_DE.UTF-8 LC_TELEPHONE=de_DE.UTF-8 LC_MEASUREMENT=de_DE.UTF-8 LC_IDENTIFICATION=de_DE.UTF-8 LC_ALL= -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 407313] New: Deadlock when syscall is handled in other thread
https://bugs.kde.org/show_bug.cgi?id=407313 Bug ID: 407313 Summary: Deadlock when syscall is handled in other thread Product: valgrind Version: 3.13.0 Platform: unspecified OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: memcheck Assignee: jsew...@acm.org Reporter: falk.wer...@gmx.net Target Milestone: --- Created attachment 119899 --> https://bugs.kde.org/attachment.cgi?id=119899&action=edit strace and stacks of test application SUMMARY I use libfuse to write a simple filesystem. In order to test it, I created a simple application with two threads: - one is driving the fuse filesystem (e.g. responding to syscalls like read) - the other uses normal filesystem operations, such as stat, to test the filesystem When executing this with Valgrind/Memcheck a deadlock occurs as soon as stat is called. STEPS TO REPRODUCE 1. minimal example code can be optained here: https://github.com/falk-werner/libfuse-valgrind-deadlock 2. use `make run` to create and execute a docker container 3 valgrind ./libfuse-test OBSERVED RESULT The application will deadlock (see attached files for stack traces). EXPECTED RESULT No deadlock should appear. SOFTWARE/OS VERSIONS Linux: Ubuntu 18.04 ADDITIONAL INFORMATION When the deadlock appears, fuse is trying to send the filesystem request, but the other thread is blocked in a read(1028, "A", 1) operation originated from Valgrind. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 407313] Deadlock when syscall is handled in other thread
https://bugs.kde.org/show_bug.cgi?id=407313 --- Comment #5 from Falk Werner --- Thanks a lot, --sim-hints=fuse-compatible solves the issue. I was not aware, that such a flag exists. I will spend more effort in investigation next time. Sorry for inconvience. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 413659] Option "Open folders during drag operations" has no effect on folders panel
https://bugs.kde.org/show_bug.cgi?id=413659 Werner Lehmann changed: What|Removed |Added CC||w...@dm17.com -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 413659] Option "Open folders during drag operations" has no effect on folders panel
https://bugs.kde.org/show_bug.cgi?id=413659 --- Comment #3 from Werner Lehmann --- Yes, it is still present with 19.12.1. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 413660] Natural sorting not working as documented
https://bugs.kde.org/show_bug.cgi?id=413660 Werner Lehmann changed: What|Removed |Added CC||w...@dm17.com -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 413660] Natural sorting not working as documented
https://bugs.kde.org/show_bug.cgi?id=413660 --- Comment #2 from Werner Lehmann --- Still present with 19.12.1. Here is a screenshot: https://i.imgur.com/3anjuXt.png -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 413660] Natural sorting not working as documented
https://bugs.kde.org/show_bug.cgi?id=413660 --- Comment #4 from Werner Lehmann --- (In reply to Méven Car from comment #3) > Have tried changing the setting (leave on natural) quit dolphin, launch it > again and see if the behavior has changed ? I have the setting on natural all the time anyway and had many Dolphin starts in the few months since reporting this. But I tried it and there is no difference. There is a minor other bug (I would say): after changing the sort order and closing the options dialog the file list is not resorted right away. Seems to be cached. On reopening the options dialog it is resorted, before changing any option. Keeping this in mind I can confirm that alphabetical order with or without case sensitivity works as expected. Natural seems to work exactly like alphabetical, case insensitive. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 413660] Natural sorting not working as documented
https://bugs.kde.org/show_bug.cgi?id=413660 --- Comment #6 from Werner Lehmann --- (In reply to Christoph Feck from comment #5) > Fixed with the commit for bug 406296. Doesn't look fixed to me: https://i.imgur.com/xpex4OR.png - still sorted File1, File10, File2, not File1, File2, File10. Or is there a misunderstanding? -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 413660] Natural sorting not working as documented
https://bugs.kde.org/show_bug.cgi?id=413660 --- Comment #8 from Werner Lehmann --- Thanks. Looking forward to it :-) -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 384620] Broken ncurses box() rendering with new terminfo for TERM=xterm (no rep?)
https://bugs.kde.org/show_bug.cgi?id=384620 Werner Fink changed: What|Removed |Added CC||lbeltr...@kde.org, ||wer...@suse.de -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 384620] Broken ncurses box() rendering with new terminfo for TERM=xterm (no rep?)
https://bugs.kde.org/show_bug.cgi?id=384620 --- Comment #7 from Werner Fink --- Are there any plans to add the rep feature for a better XTerm emulation of the konsole terminal emluator? -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 387711] New: Sudden crash of Konsole while scrolling
https://bugs.kde.org/show_bug.cgi?id=387711 Bug ID: 387711 Summary: Sudden crash of Konsole while scrolling 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: w...@gnu.org 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: I've never experienced this before, so I don't know whether this is repeatable at all. -- Backtrace: Application: Konsole (konsole), signal: Aborted Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f942ae208c0 (LWP 2997))] Thread 3 (Thread 0x7f940fde3700 (LWP 3019)): #0 0x7f942a55e28d in read () at /lib64/libc.so.6 #1 0x7f9421ddb670 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7f9421d9ae49 in g_main_context_check () at /usr/lib64/libglib-2.0.so.0 #3 0x7f9421d9b2a8 in () at /usr/lib64/libglib-2.0.so.0 #4 0x7f9421d9b42c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #5 0x7f942697133b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #6 0x7f942691efeb in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #7 0x7f9426759f1a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #8 0x7f9424b29295 in () at /usr/lib64/libQt5DBus.so.5 #9 0x7f942675e9e9 in () at /usr/lib64/libQt5Core.so.5 #10 0x7f94222b8744 in start_thread () at /lib64/libpthread.so.0 #11 0x7f942a56aaad in clone () at /lib64/libc.so.6 Thread 2 (Thread 0x7f9415d29700 (LWP 3016)): #0 0x7f942a56220d in poll () at /lib64/libc.so.6 #1 0x7f94226db3e2 in () at /usr/lib64/libxcb.so.1 #2 0x7f94226dcfcf in xcb_wait_for_event () at /usr/lib64/libxcb.so.1 #3 0x7f9418288839 in () at /usr/lib64/libQt5XcbQpa.so.5 #4 0x7f942675e9e9 in () at /usr/lib64/libQt5Core.so.5 #5 0x7f94222b8744 in start_thread () at /lib64/libpthread.so.0 #6 0x7f942a56aaad in clone () at /lib64/libc.so.6 Thread 1 (Thread 0x7f942ae208c0 (LWP 2997)): [KCrash Handler] #6 0x7f942a4b58d7 in raise () at /lib64/libc.so.6 #7 0x7f942a4b6caa in abort () at /lib64/libc.so.6 #8 0x7f942a4f31b4 in () at /lib64/libc.so.6 #9 0x7f942a4f8706 in malloc_printerr () at /lib64/libc.so.6 #10 0x7f942a4fabd5 in _int_malloc () at /lib64/libc.so.6 #11 0x7f942a4fc420 in malloc () at /lib64/libc.so.6 #12 0x7f94263bce38 in operator new(unsigned long) () at /usr/lib64/libstdc++.so.6 #13 0x7f942a01120a in Konsole::TerminalDisplay::updateImage() () at /usr/lib64/libkonsoleprivate.so.16 #14 0x7f942694b1d3 in QMetaObject::activate(QObject*, int, int, void**) () at /usr/lib64/libQt5Core.so.5 #15 0x7f942694b1d3 in QMetaObject::activate(QObject*, int, int, void**) () at /usr/lib64/libQt5Core.so.5 #16 0x7f9429fb57fe in Konsole::Emulation::showBulk() () at /usr/lib64/libkonsoleprivate.so.16 #17 0x7f942694b1d3 in QMetaObject::activate(QObject*, int, int, void**) () at /usr/lib64/libQt5Core.so.5 #18 0x7f9426958122 in QTimer::timerEvent(QTimerEvent*) () at /usr/lib64/libQt5Core.so.5 #19 0x7f942694bf44 in QObject::event(QEvent*) () at /usr/lib64/libQt5Core.so.5 #20 0x7f94278bae3c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib64/libQt5Widgets.so.5 #21 0x7f94278bf49a in QApplication::notify(QObject*, QEvent*) () at /usr/lib64/libQt5Widgets.so.5 #22 0x7f9426920fd5 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib64/libQt5Core.so.5 #23 0x7f9426970c8e in QTimerInfoList::activateTimers() () at /usr/lib64/libQt5Core.so.5 #24 0x7f9426971051 in () at /usr/lib64/libQt5Core.so.5 #25 0x7f9421d9b134 in g_main_context_dispatch () at /usr/lib64/libglib-2.0.so.0 #26 0x7f9421d9b388 in () at /usr/lib64/libglib-2.0.so.0 #27 0x7f9421d9b42c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #28 0x7f942697131c in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #29 0x7f942691efeb in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #30 0x7f9426926ed6 in QCoreApplication::exec() () at /usr/lib64/libQt5Core.so.5 #31 0x7f942a84cc87 in kdemain () at /usr/lib64/libkdeinit5_konsole.so #32 0x7f942a4a16e5 in __libc_start_main () at /lib64/libc.so.6 #33 0x00400789 in _start () Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 403007] KMail crashes by selecting freshly arrived unread mails
https://bugs.kde.org/show_bug.cgi?id=403007 --- Comment #5 from Werner Bernhard --- I am using Arch Linux, so i have alwais the newest Version of KDE -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 403007] KMail crashes by selecting freshly arrived unread mails
https://bugs.kde.org/show_bug.cgi?id=403007 Werner Bernhard changed: What|Removed |Added CC||wrbernh...@gmail.com --- Comment #6 from Werner Bernhard --- How can I change the status? Christophe Giboudeaux has posted what I get sometimes as response from the software. In the majority of the cases however I just get 'A fatal error occured'. Sorry I have not more. Werner -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 403007] KMail crashes by selecting freshly arrived unread mails
https://bugs.kde.org/show_bug.cgi?id=403007 --- Comment #7 from Werner Bernhard --- The correct Errormessage that mostly is reportet is: Application: Kontact (kontact), signal: Segmentation fault. The posted one occors i one of about 10 times. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 403007] KMail crashes by selecting freshly arrived unread mails
https://bugs.kde.org/show_bug.cgi?id=403007 --- Comment #8 from Werner Bernhard --- Right now, afte a crash, opening a new mail, I received a new error message. Application: Kontact (kontact), signal: Aborted Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7f7e2be53b00 (LWP 9170))] Thread 31 (Thread 0x7f7d0d1ee700 (LWP 9265)): #0 0x7f7e3eff8ef6 in pthread_cond_timedwait@@GLIBC_2.3.2 () from /usr/lib/libpthread.so.0 #1 0x7f7e389d0447 in ?? () from /usr/lib/libQt5WebEngineCore.so.5 #2 0x7f7e389d116a in ?? () from /usr/lib/libQt5WebEngineCore.so.5 #3 0x7f7e389d1252 in ?? () from /usr/lib/libQt5WebEngineCore.so.5 #4 0x7f7e38990301 in ?? () from /usr/lib/libQt5WebEngineCore.so.5 #5 0x7f7e389924d7 in ?? () from /usr/lib/libQt5WebEngineCore.so.5 #6 0x7f7e38992ac4 in ?? () from /usr/lib/libQt5WebEngineCore.so.5 #7 0x7f7e389d3361 in ?? () from /usr/lib/libQt5WebEngineCore.so.5 #8 0x7f7e3eff2a9d in start_thread () from /usr/lib/libpthread.so.0 #9 0x7f7e401a3b23 in clone () from /usr/lib/libc.so.6 Thread 30 (Thread 0x7f7d0d9ef700 (LWP 9264)): #0 0x7f7e3eff8ef6 in pthread_cond_timedwait@@GLIBC_2.3.2 () from /usr/lib/libpthread.so.0 #1 0x7f7e389d0447 in ?? () from /usr/lib/libQt5WebEngineCore.so.5 #2 0x7f7e389d116a in ?? () from /usr/lib/libQt5WebEngineCore.so.5 #3 0x7f7e389d1252 in ?? () from /usr/lib/libQt5WebEngineCore.so.5 #4 0x7f7e38990301 in ?? () from /usr/lib/libQt5WebEngineCore.so.5 #5 0x7f7e38992806 in ?? () from /usr/lib/libQt5WebEngineCore.so.5 #6 0x7f7e38992ac4 in ?? () from /usr/lib/libQt5WebEngineCore.so.5 #7 0x7f7e389d3361 in ?? () from /usr/lib/libQt5WebEngineCore.so.5 #8 0x7f7e3eff2a9d in start_thread () from /usr/lib/libpthread.so.0 #9 0x7f7e401a3b23 in clone () from /usr/lib/libc.so.6 Thread 29 (Thread 0x7f7d0e1f0700 (LWP 9263)): #0 0x7f7e3eff8ef6 in pthread_cond_timedwait@@GLIBC_2.3.2 () from /usr/lib/libpthread.so.0 #1 0x7f7e389d0447 in ?? () from /usr/lib/libQt5WebEngineCore.so.5 #2 0x7f7e389d116a in ?? () from /usr/lib/libQt5WebEngineCore.so.5 #3 0x7f7e389d1252 in ?? () from /usr/lib/libQt5WebEngineCore.so.5 #4 0x7f7e38990301 in ?? () from /usr/lib/libQt5WebEngineCore.so.5 #5 0x7f7e389924d7 in ?? () from /usr/lib/libQt5WebEngineCore.so.5 #6 0x7f7e38992ac4 in ?? () from /usr/lib/libQt5WebEngineCore.so.5 #7 0x7f7e389d3361 in ?? () from /usr/lib/libQt5WebEngineCore.so.5 #8 0x7f7e3eff2a9d in start_thread () from /usr/lib/libpthread.so.0 #9 0x7f7e401a3b23 in clone () from /usr/lib/libc.so.6 Thread 28 (Thread 0x7f7d34930700 (LWP 9250)): #0 0x7f7e40198c21 in poll () from /usr/lib/libc.so.6 #1 0x7f7e3e3e4540 in ?? () from /usr/lib/libglib-2.0.so.0 #2 0x7f7e3e3e462e in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #3 0x7f7e406e75c4 in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/libQt5Core.so.5 #4 0x7f7e4069058c in QEventLoop::exec(QFlags) () from /usr/lib/libQt5Core.so.5 #5 0x7f7e404d45c9 in QThread::exec() () from /usr/lib/libQt5Core.so.5 #6 0x7f7e404d59cc in ?? () from /usr/lib/libQt5Core.so.5 #7 0x7f7e3eff2a9d in start_thread () from /usr/lib/libpthread.so.0 #8 0x7f7e401a3b23 in clone () from /usr/lib/libc.so.6 Thread 27 (Thread 0x7f7d36097700 (LWP 9218)): #0 0x7f7e40198c21 in poll () from /usr/lib/libc.so.6 #1 0x7f7e3e3e4540 in ?? () from /usr/lib/libglib-2.0.so.0 #2 0x7f7e3e3e462e in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #3 0x7f7e406e75c4 in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/libQt5Core.so.5 #4 0x7f7e4069058c in QEventLoop::exec(QFlags) () from /usr/lib/libQt5Core.so.5 #5 0x7f7e404d45c9 in QThread::exec() () from /usr/lib/libQt5Core.so.5 #6 0x7f7e404d59cc in ?? () from /usr/lib/libQt5Core.so.5 #7 0x7f7e3eff2a9d in start_thread () from /usr/lib/libpthread.so.0 #8 0x7f7e401a3b23 in clone () from /usr/lib/libc.so.6 Thread 26 (Thread 0x7f7d36a6e700 (LWP 9210)): #0 0x7f7e40198c21 in poll () from /usr/lib/libc.so.6 #1 0x7f7e3e3e4540 in ?? () from /usr/lib/libglib-2.0.so.0 #2 0x7f7e3e3e462e in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #3 0x7f7e406e75c4 in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/libQt5Core.so.5 #4 0x7f7e4069058c in QEventLoop::exec(QFlags) () from /usr/lib/libQt5Core.so.5 #5 0x7f7e404d45c9 in QThread::exec() () from /usr/lib/libQt5Core.so.5 #6 0x7f7e404d59cc in ?? () from /usr/lib/libQt5Core.so.5 #7 0x7f7e3eff2a9d in start_thread () from /usr/lib/libpthread.so.0 #8 0x7f7e401a3b23 in clone () from /usr/lib/libc.so.6 Thread 25 (Thread 0x7f7d3726f700 (LWP 9209)): #0 0x7f7e401947a4 in read () from /usr/lib/libc.so.6 #1 0x7f7e3e392971 in ?? () from /usr/lib/libglib-2.0.so.0 #2 0x7f7e3e3e30b0 in g_main_context_check () fro
[kmail2] [Bug 403007] KMail crashes by selecting freshly arrived unread mails
https://bugs.kde.org/show_bug.cgi?id=403007 --- Comment #10 from Werner Bernhard --- Hi The last comment fron Christoph Feck is rather strange. All applicationons rar running fine, just not KMail. This makes it rather difficult to search the error in the driver. I do not understand this comment. good luck W. Bernhard -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 403007] New: K-Mail crashes by selecting freshly arrived unread mails
https://bugs.kde.org/show_bug.cgi?id=403007 Bug ID: 403007 Summary: K-Mail crashes by selecting freshly arrived unread mails Product: kmail2 Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: UI Assignee: kdepim-b...@kde.org Reporter: wrbernh...@gmail.com Target Milestone: --- SUMMARY K-Mail crashes by selecting freshly arrived unread Mails STEPS TO REPRODUCE 1. see summary OBSERVED RESULT My email provider is bluewin.ch (Swisscom) an I cannot exclude, That it is not independent of this provider. But it worked with it for several years and the problem started last fall with an update. If a newly arrived mail is selected, the application crashes not allways but in the majority of the cases. If the mail is selectable without crash, it is not deletable or access to any other way of handling, this also leads to a crash. Is the application started again, the mail becomes accessable. Sometimes it needs several restarts. In some cases even the operating system crashes. Old mails are accessible to any handling. SOFTWARE/OS VERSIONS I am using Arch Linux with KDE desktop and the newest version of KDE-Plasma. As I am preparing myself to contribute to KDE, I also have the newest versions of the QT frameworks installed. Linux/KDE Plasma: newest available Version (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: newest Version ADDITIONAL INFORMATION As a retired software developer and lover of Linux/KDE this behavior looks to me like a typical no reference exception, which might be closely linked to the OS. There must have been done some work on this bug allready as it changed its behaviour somewhat, but it got not really fixed. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 381533] Square box behind mouse cursor/pointer blocks and corrupts zones at which it's pointing
https://bugs.kde.org/show_bug.cgi?id=381533 Werner Mollentze changed: What|Removed |Added CC||li...@mollentze.co.za --- Comment #8 from Werner Mollentze --- I started to experience this problem today, after running apt-get upgrade, which upgraded to 4.10.0-28-generic on Kubuntu 16.04.2. Before the update everything was fine, I have NVIDIA GeForce GTX 860M. -- You are receiving this mail because: You are watching all bug changes.
[marble] [Bug 376626] New: View does not recenter after loading of file
https://bugs.kde.org/show_bug.cgi?id=376626 Bug ID: 376626 Summary: View does not recenter after loading of file Product: marble Version: 2.1 (KDE Applications 16.12) Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: marble-b...@kde.org Reporter: w...@werner-stille.de Target Milestone: --- Created attachment 104101 --> https://bugs.kde.org/attachment.cgi?id=104101&action=edit Patch for automatic recentering after loading files When using MarbleWidget::model()->addGeoDataFile() to load a file, the view is not recentered any more according to the content, in contrast to the previous Marble version (2.0). It seems that after inserting the new parameter "renderOrder" in FileManager::addFile(), the call of that function in MarbleModel::addGeoDataFile() was not updated correctly to pass the value "true" for the parameter "recenter". The attached patch seems to cure the problem. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 373705] Allow different panel configuration for activities
https://bugs.kde.org/show_bug.cgi?id=373705 Nicolas Werner changed: What|Removed |Added CC||nicolas.wer...@ymail.com --- Comment #3 from Nicolas Werner --- (In reply to David Edmundson from comment #1) > Thanks for the comment > > > or the favorite programs on application menu can be quite different for > > workflows, which is not possible at the moment. > > This now exists in 5.9, integrated into the launcher itself. > If you have any other specific ideas of activity specific configurations > within an applet, we can look into that on a case-by-case basis. > > Having completely different panel configurations I think would just be too > complicated to show in the UI, and involve the user doing a lot of duplicate > reconfiguring for global actions that exist above activities. I agree, that configuration would be harder, so there is a case to be made, that by default panels are synced between activities. Still, there are cases, where you want completely different layouts of your panels between activities. If you have a separate activity for drawing, you may want to have a unity like task switcher on the side of your desktop. This would require a bigger panel on a different edge of the screen. While programming this may be wasted space, so you'd switch to a standard windows-like layout. Maybe you'd even want to set the task switcher to autohide, which would be annoying to activate with a graphics tablet, but with a mouse it is much easier. This can't be done with an automatic transition based on input devices present like with a virtual keyboard as I don't usually disconnect my graphics tablet when I'm not using it. The panel layout I need simply depends on the activity I'm doing. There are also other possible use cases. You may not want to see notifications as well as the current time when you are studying. You may want a different application launcher when you are playing games and you may want to have your panels on different screens while editing a video. Configuring your activities like that may be some work, but at the same time activities would provide much more value as you could tailor each activity to exactly one workflow instead of having to compromise. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 374589] New: search in Postbank bank statement document partly works
https://bugs.kde.org/show_bug.cgi?id=374589 Bug ID: 374589 Summary: search in Postbank bank statement document partly works Product: okular Version: 0.24.0 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: general Assignee: okular-de...@kde.org Reporter: werner.lamp...@freenet.de Target Milestone: --- hello , search for strings in Postbank monthly bank statements document does not work properly. To open the document is fine and looks OK . But when I search for a string which is obviously there OKULAR does not find it . This problem does not occur with Adobe Reader under Windows. EVINCE seemed to be the same problem and was already discussed in a Ubuntu forum ( see link below) there you can also find addition information . many thanks BR /werner https://forum.ubuntuusers.de/topic/problem-beim-suchen-mit-dem-evince-pdf-reader/ -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 374589] search in Postbank bank statement document partly works
https://bugs.kde.org/show_bug.cgi?id=374589 --- Comment #2 from Werner Lamping --- bugreport also send to poppler . br /werner https://bugs.freedesktop.org/show_bug.cgi?id=99284 -- You are receiving this mail because: You are watching all bug changes.
[Skanpage] [Bug 495125] New: Skanpage fails with ADF on HP Laserjet MFP
https://bugs.kde.org/show_bug.cgi?id=495125 Bug ID: 495125 Summary: Skanpage fails with ADF on HP Laserjet MFP Classification: Applications Product: Skanpage Version: 24.08.1 Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: a.stipp...@gmx.net Reporter: chatnick-spi...@gmx.de Target Milestone: --- SUMMARY When trying to scan by the automatic document feeder (ADF), the scanner starts running but Skanpage shows error "Document feeder empty" on the end of the scan and no result is shown. Scanning from flatbed is OK. STEPS TO REPRODUCE 1. Set source to ADF 2. Start scan OBSERVED RESULT Error message "Document feeder empty" (or similar, soory I'm on german language settings) No scan shown EXPECTED RESULT Scanned document SOFTWARE/OS VERSIONS Linux/KDE Plasma: Manjaro Linux KDE Plasma Version: 6.1.5 KDE Frameworks Version: 6.6.0 Qt Version: 6.7.2 Scanning device: HP Color LaserJet MFP M183 fw, connected via Wlan -- You are receiving this mail because: You are watching all bug changes.
[Skanpage] [Bug 495125] Skanpage fails with ADF on HP Laserjet MFP
https://bugs.kde.org/show_bug.cgi?id=495125 --- Comment #1 from Werner Back --- Seems to be Manjaro-related. Works in Neon (in a VM). -- You are receiving this mail because: You are watching all bug changes.
[ark] [Bug 441964] Problem with -c (--add) option
https://bugs.kde.org/show_bug.cgi?id=441964 --- Comment #3 from Werner Kroneman --- I see two ways out of this: - easiest: change the text of the help to just say it's to specify the files to add to the archive - harder, unclear if we want that: actually prompt the user for a filename with a dialog of some sort The easy option requires just one change in main.cpp and it's more or less what I'd expect a command line tool to behave like. The line to be changed is here: https://invent.kde.org/utilities/ark/-/blob/master/app/main.cpp?ref_type=heads#L126 (and in all the i18n files) -- You are receiving this mail because: You are watching all bug changes.
[ark] [Bug 441964] Problem with -c (--add) option
https://bugs.kde.org/show_bug.cgi?id=441964 --- Comment #4 from Werner Kroneman --- Alternatively, could swap this error in https://invent.kde.org/utilities/ark/-/blob/master/kerfuffle/addtoarchive.cpp?ref_type=heads#L139 for an input prompt of some sort. -- You are receiving this mail because: You are watching all bug changes.
[ark] [Bug 441964] Problem with -c (--add) option
https://bugs.kde.org/show_bug.cgi?id=441964 --- Comment #5 from Werner Kroneman --- Working on a fix here: https://invent.kde.org/wkroneman/ark/-/commits/issue-441964 It goes the "prompt the user" roue -- You are receiving this mail because: You are watching all bug changes.
[ark] [Bug 441964] Problem with -c (--add) option
https://bugs.kde.org/show_bug.cgi?id=441964 Werner Kroneman changed: What|Removed |Added CC||wer...@wernerkroneman.nl Ever confirmed|0 |1 Status|REPORTED|CONFIRMED --- Comment #2 from Werner Kroneman --- Behavior is immediately reproducible over here, just use -c with any file name. Not sure if it's a bug? At the very least the help message is incorrect, as it states "Query the user for an archive filename and add specified files to it. Quit when finished." Ark does not at any point query anything, it just fails with the screenshotted error message. -- You are receiving this mail because: You are watching all bug changes.
[ark] [Bug 441964] Problem with -c (--add) option
https://bugs.kde.org/show_bug.cgi?id=441964 Werner Kroneman changed: What|Removed |Added Keywords||junior-jobs -- You are receiving this mail because: You are watching all bug changes.
[ark] [Bug 138685] ark should recognize self-extracting zip files
https://bugs.kde.org/show_bug.cgi?id=138685 Werner Kroneman changed: What|Removed |Added CC||wer...@wernerkroneman.nl --- Comment #7 from Werner Kroneman --- It appears that the link is dead; it now redirects to some unrelated stuff about playing media in Windows. Anyone got a file to test with? (I don't have access to a Windows machine right now) -- You are receiving this mail because: You are watching all bug changes.
[Skanpage] [Bug 495125] Skanpage fails with ADF on HP Laserjet MFP
https://bugs.kde.org/show_bug.cgi?id=495125 Werner Back changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #3 from Werner Back --- Thank you, the backend sane-airscan works. -- You are receiving this mail because: You are watching all bug changes.
[parley] [Bug 365675] New: Beim Schreiben in die Datei „ *.kvtml“ ist ein Fehler aufgetreten: Die Sperrdatei kann nicht angelegt werden.
https://bugs.kde.org/show_bug.cgi?id=365675 Bug ID: 365675 Summary: Beim Schreiben in die Datei „ *.kvtml“ ist ein Fehler aufgetreten: Die Sperrdatei kann nicht angelegt werden. Product: parley Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: parley-bugs-n...@kde.org Reporter: simba...@email.de nach Beendigung einer Übung zurück auf die Übersichtsseite, oder nach Arbeit mit dem Editor wenn die Eintragungen abgespeichert werden sollen. Dann tritt dieser Fehler auf. Beim Schreiben in die Datei „ *.kvtml“ ist ein Fehler aufgetreten: Die Sperrdatei kann nicht angelegt werden. Wobei es egal ist welche Sprachdatei benutzt wurde (deshalb schreibe ich auch *) Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[kdelibs] [Bug 297003] Newly created text files are not empty
https://bugs.kde.org/show_bug.cgi?id=297003 Werner Loureiro changed: What|Removed |Added CC|werne...@gmail.com | -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 332512] Plasma Popups aren't resizable
https://bugs.kde.org/show_bug.cgi?id=332512 Nicolas Werner changed: What|Removed |Added CC||nicolas.wer...@ymail.com -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 350731] [4.81 beta1] akregator in kontact: read messages are removed from unread filter immediately
https://bugs.kde.org/show_bug.cgi?id=350731 Werner Mahr changed: What|Removed |Added CC||k...@vollstreckernet.de -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 366504] New: Help | About menu doesn't exist
https://bugs.kde.org/show_bug.cgi?id=366504 Bug ID: 366504 Summary: Help | About menu doesn't exist Product: akregator Version: unspecified Platform: Debian testing OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: k...@vollstreckernet.de Hi, I just wanted to report another problem and was asked for the version. I didn't test when running as standalone app, but from within Kontact this menu ist just not there. Reproducible: Always Steps to Reproduce: 1. Open Konatct 2. Go to feeds 3. Click on help Actual Results: Just the menu for Kontact-Overview Expected Results: About menu, the bugtracker asks for. Kontact overview gives version 5.2.3 Version of deb says: 4:16.04.3-1 -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 366504] Help | About menu doesn't exist
https://bugs.kde.org/show_bug.cgi?id=366504 Werner Mahr changed: What|Removed |Added CC||k...@vollstreckernet.de -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 366505] New: Filter is reset when "Reset Quicksearch on Feed-Change" setting is aktivated
https://bugs.kde.org/show_bug.cgi?id=366505 Bug ID: 366505 Summary: Filter is reset when "Reset Quicksearch on Feed-Change" setting is aktivated Product: akregator Version: unspecified Platform: Debian testing OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: k...@vollstreckernet.de Hi, while trying to set the time for automarking an article as read to a value where I get the chance to read it, before it disappears, I saw the option to reset the quicksearch when changing feeds. I wanted to activate this feature for ages, and this time I really did. Since that time, not only the quicksearch is reset, the filter always jumps back to all, too. Reproducible: Always Steps to Reproduce: 1. Aktivate "Reset Quicksearch in feed-change" on Advanced-Settings-Tab 2. set filter to something different than all 3. change feed Actual Results: Filter is reset to all Expected Results: Filter shouldn't be touched Kontact reports itself as 5.2. deb-version is 4:16.04.3-1 -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 366506] New: No contextmenu from keyboard
https://bugs.kde.org/show_bug.cgi?id=366506 Bug ID: 366506 Summary: No contextmenu from keyboard Product: kmail2 Version: unspecified Platform: Debian testing OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: message list Assignee: kdepim-b...@kde.org Reporter: k...@vollstreckernet.de Hi, I didn't specify a version, as 5.2.3 wasn't an option. As (I don't know why), the context menu disappears in 90% right after opening it with the mouse, I always used to open it with keyboard for i.e. moving a message to spam-folder. While everything works as expected in all other parts, on the messagelist the menu isn't shown when using the keyboard. Reproducible: Always Steps to Reproduce: 1. Go to message-list 2. Hit the contextmenu-button on your keyboard 3. Actual Results: Nothing happens Expected Results: The context-menu should be opened -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 366506] No contextmenu from keyboard
https://bugs.kde.org/show_bug.cgi?id=366506 Werner Mahr changed: What|Removed |Added CC||k...@vollstreckernet.de -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 366505] Filter is reset when "Reset Quicksearch on Feed-Change" setting is aktivated
https://bugs.kde.org/show_bug.cgi?id=366505 Werner Mahr changed: What|Removed |Added CC||k...@vollstreckernet.de -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 366508] Next unread folder not working
https://bugs.kde.org/show_bug.cgi?id=366508 Werner Mahr changed: What|Removed |Added CC||k...@vollstreckernet.de -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 366508] New: Next unread folder not working
https://bugs.kde.org/show_bug.cgi?id=366508 Bug ID: 366508 Summary: Next unread folder not working Product: kmail2 Version: unspecified Platform: Debian testing OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: message list Assignee: kdepim-b...@kde.org Reporter: k...@vollstreckernet.de Hi, I didn't set a version, because 5.2.3 wasn't an option. When reading new mails, it was in the old version possible, that hitting + for next unread message went to the next folder that has unread messages. I don't know if it was an option I selected or default, but I can't get this function in the new version. I think this has been a really usefull feature and really miss it. Reproducible: Always Kmail Version 5.2.3 deb-version: 4:16.04.3-1 I choose normal severity, because Wishlist doesn't seem to fit, because it isn't a new feature, and minor didn't fit, because it is indeed a loss of functionality, but I don't know any workaround -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 366508] Next unread folder not working
https://bugs.kde.org/show_bug.cgi?id=366508 Werner Mahr changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |INVALID --- Comment #1 from Werner Mahr --- Interesting, after 2 annoying days, and on right the next usage after this report, it asked me if it should go to the next folder and offered to rember, so this one is closed. -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 366504] Help | About menu doesn't exist
https://bugs.kde.org/show_bug.cgi?id=366504 --- Comment #2 from Werner Mahr --- I don't think so, as KMail has (as only part of the ones I use) this menu, it seems to be a problem of the separate apps. -- You are receiving this mail because: You are watching all bug changes.
[kdevplatform] [Bug 354706] comitting single file change first tries to commit all changed files
https://bugs.kde.org/show_bug.cgi?id=354706 Nicolas Werner changed: What|Removed |Added Resolution|INVALID |FIXED --- Comment #5 from Nicolas Werner --- Can't reproduce it any more. Seems to be fixed and work as intended now. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 357007] kscreenlocker_greet unresponsive when using compositor
https://bugs.kde.org/show_bug.cgi?id=357007 Stefan Werner changed: What|Removed |Added CC||dust...@gmx.de -- You are receiving this mail because: You are watching all bug changes.
[Baloo] [Bug 358258] Baloo indexing crash
https://bugs.kde.org/show_bug.cgi?id=358258 Werner Lemberg changed: What|Removed |Added CC||w...@gnu.org --- Comment #1 from Werner Lemberg --- [KDE Frameworks 5.16.0, Qt 5.5.1, xcb windowing system] [openSuSE Leap 42.1] Well, the Crash Reporting Assistant doesn't handle the `Suggest this crash is related' button (which is another bug), so I just wanted to say that I get the same crash every time after KDE is started, without doing something special. -- You are receiving this mail because: You are watching all bug changes.
[drkonqi] [Bug 356722] Useless dialog after "Suggest this crash is related" button pressing
https://bugs.kde.org/show_bug.cgi?id=356722 Werner Lemberg changed: What|Removed |Added CC||w...@gnu.org --- Comment #1 from Werner Lemberg --- I get the same with KDE Frameworks 5.16.0 and Qt 5.5.1 on an openSuSE Leap 42.1 x86_64 box. -- You are receiving this mail because: You are watching all bug changes.
