[Smb4k] [Bug 486474] Smb4k does not support alternatives to KDE Wallet
https://bugs.kde.org/show_bug.cgi?id=486474 --- Comment #17 from Alexander Reinholdt --- It basically looks like this: org.kde.smb4k |-> URL 1: username:password |-> URL 2: username:password |-> URL 3: username:password |-> ... -- You are receiving this mail because: You are watching all bug changes.
[Smb4k] [Bug 486474] Smb4k does not support alternatives to KDE Wallet
https://bugs.kde.org/show_bug.cgi?id=486474 --- Comment #16 from Alexander Reinholdt --- (In reply to Odin Vex from comment #15) > > No. Everything will be saved in a secure storage (KWallet, Gnome Keyring, > > etc.). > How are credentials for multiple servers stored in a single key:value then > without serialization? I already had the feeling that there might be a misunderstanding. Maybe on my side. The credentials are stored in such a way that, first of all, a secure storage (KWallet, etc.) is used as stated above. Smb4K will create a folder in the secure storage named 'org.kde.smb4k', where the credentials are stored for each network item. The URL is used as 'key', so Smb4K can retrieve the credentials from the secure storage. The username and the password are then stored as the associated value. It is basically the same as with the KWallet-only approach, but with the difference that QtKeychain does not allow me to access the list of all entries in the folder like KWallet did. So, the ability to edit the credentials via the configuration dialog is lost, but everyhing else works as before. -- You are receiving this mail because: You are watching all bug changes.
[Smb4k] [Bug 486474] Smb4k does not support alternatives to KDE Wallet
https://bugs.kde.org/show_bug.cgi?id=486474 --- Comment #14 from Alexander Reinholdt --- (In reply to Odin Vex from comment #12) > (In reply to Alexander Reinholdt from comment #11) > > Another way would be to store the username and password for each server or > > share separately, but have a list of all network items in the secure > > storage. After starting to implement this, I did not like it and also > > decided against it. > So it's back to storing everything in a file? No. Everything will be saved in a secure storage (KWallet, Gnome Keyring, etc.). > > I implemented to possibility to edit the authentication information long > > time ago. Looking back, I almost never used it except defining the default > > login credentials. If the username or password for a server or share need to > > be changed, you can do this with/in the password dialog withou even opening > > the configuration dialog. The default credentials can still be defined > > there. And when you want to clean up, you can do this with the GUI of the > > password manager. > You might not have used it but others may very well have (myself, for > example). Okay. -- You are receiving this mail because: You are watching all bug changes.
[Smb4k] [Bug 486474] Smb4k does not support alternatives to KDE Wallet
https://bugs.kde.org/show_bug.cgi?id=486474 --- Comment #11 from Alexander Reinholdt --- I thought about the serialized approach and possible alternatives. I don't like serialized one, because you squeeze all login credentials into one entry and you either have to read it once and store all credentials in memory (i.e. in a hash or map) or you have to read everything each time the program asks for credentials. In any case you have to implement some search logic to pick the right credentials. Similar things are true for writing/saving. This is too much overhead for me. Another way would be to store the username and password for each server or share separately, but have a list of all network items in the secure storage. After starting to implement this, I did not like it and also decided against it. I implemented to possibility to edit the authentication information long time ago. Looking back, I almost never used it except defining the default login credentials. If the username or password for a server or share need to be changed, you can do this with/in the password dialog withou even opening the configuration dialog. The default credentials can still be defined there. And when you want to clean up, you can do this with the GUI of the password manager. So, for the time being, I will leave the code as it is now. If QtKeychains API allows for accessing the list of all login credentials in the future, I will maybe reimplement the functionality. -- You are receiving this mail because: You are watching all bug changes.
[Smb4k] [Bug 486474] Smb4k does not support alternatives to KDE Wallet
https://bugs.kde.org/show_bug.cgi?id=486474 --- Comment #9 from Alexander Reinholdt --- (In reply to Odin Vex from comment #7) > Key: "smb4k", Value: "SerializedArray" would work. One key, "smb4k" (since > this is per user already). The value is a serialized array. Okay, that's better than the solution I thought about. However, this solution is still quite awkward. -- You are receiving this mail because: You are watching all bug changes.
[Smb4k] [Bug 486474] Smb4k does not support alternatives to KDE Wallet
https://bugs.kde.org/show_bug.cgi?id=486474 --- Comment #6 from Alexander Reinholdt --- (In reply to Odin Vex from comment #4) > Would libsecret have been a better option for enumeration or could the way > secrets are stored be a collection of all top provide a workaround for > QtKeychain? Actually, it also annoys me a bit that QtKeychain cannot provide the list of all login credentials Smb4K saved. However, since QtKeychain is commonly used in KDE applications and has a very simple API, I decided to use it instead of any other solution. I don't know whether libsecret would have been the better option. I only had a short glimpse at it. If I understand correctly, you suggest to save the login credentials as one data object (collection) into the secret storage. As far as I can see that won't work, because QtKeychain only allows saving key/value pairs (strings). -- You are receiving this mail because: You are watching all bug changes.
[Smb4k] [Bug 486474] Smb4k does not support alternatives to KDE Wallet
https://bugs.kde.org/show_bug.cgi?id=486474 Alexander Reinholdt changed: What|Removed |Added Resolution|--- |FIXED Latest Commit||https://invent.kde.org/netw ||ork/smb4k/-/commit/9ce91398 ||edbe5501a9f6e49fcdac9b0c5d0 ||86692 Status|REPORTED|RESOLVED --- Comment #3 from Alexander Reinholdt --- Git commit 9ce91398edbe5501a9f6e49fcdac9b0c5d086692 by Alexander Reinholdt. Committed on 30/05/2024 at 08:54. Pushed by areinholdt into branch 'master'. The login credentials are now stored using QtKeychain. This allows the usage of other secure storage solutions apart from KWallet. Since QtKeychain does not provide access to all login credentials Smb4K stored, we lost the capability to edit the login credentials in the configuration dialog. You need to use the respective editor program (i.e. kwalletmanager, KeePassXC, ...) to edit or remove the login credentials. The default login now has become profile-dependent. It can be defined directly in the configuration dialog and is automatically changed when the user changed the active profile. M +5-0CMakeLists.txt M +2-2core/CMakeLists.txt M +0-15 core/smb4k.kcfg M +7-150 core/smb4k.notifyrc D +0-158 core/smb4kauthinfo.cpp D +0-125 core/smb4kauthinfo.h M +2-2core/smb4kclient.cpp M +5-5core/smb4kclient_p.cpp A +399 -0core/smb4kcredentialsmanager.cpp [License: GPL(v2.0+)] A +158 -0core/smb4kcredentialsmanager.h [License: GPL(v2.0+)] M +2-1core/smb4khost.cpp M +4-5core/smb4kmounter.cpp M +1-1core/smb4kmounter.h M +13 -28 core/smb4knotification.cpp M +8-13 core/smb4knotification.h M +2-1core/smb4kshare.cpp D +0-386 core/smb4kwalletmanager.cpp D +0-165 core/smb4kwalletmanager.h M +6-6smb4k/smb4kconfigdialog.cpp M +57 -331 smb4k/smb4kconfigpageauthentication.cpp M +24 -115 smb4k/smb4kconfigpageauthentication.h M +0-31 smb4k/smb4kmainwindow.cpp M +0-8smb4k/smb4kmainwindow.h M +1-2smb4k/smb4knetworkbrowserdockwidget.cpp M +6-6smb4k/smb4kpassworddialog.cpp M +1-1smb4k/smb4kpassworddialog.h https://invent.kde.org/network/smb4k/-/commit/9ce91398edbe5501a9f6e49fcdac9b0c5d086692 -- You are receiving this mail because: You are watching all bug changes.
[Smb4k] [Bug 486474] Smb4k does not support alternatives to KDE Wallet
https://bugs.kde.org/show_bug.cgi?id=486474 --- Comment #2 from Alexander Reinholdt --- Thank you for reporting this. Actually, this is on my TODO list. I wanted to implement this in version 4.1. But now I think I will do it in 4.0 that is due this year. (There is already preliminary work present in the repo.) -- You are receiving this mail because: You are watching all bug changes.
[Smb4k] [Bug 484712] SMB4K crashed when iPhone is connected on Fedora 40
https://bugs.kde.org/show_bug.cgi?id=484712 --- Comment #4 from Alexander Reinholdt --- Thank you very much for the backtrace. It indicates that the crash seems to happen when QNetworkInterface::allInterfaces() is called in Smb4KHardwareManager::checkOnlineState(). Also, the backtrace points indeed to usbmuxd as the route cause. So, I think the problem is located outside of Smb4K. At the moment I'm wondering whether I can do anything about the crash on the Smb4K side... -- You are receiving this mail because: You are watching all bug changes.
[Smb4k] [Bug 484712] SMB4K crashed when iPhone is connected on Fedora 40
https://bugs.kde.org/show_bug.cgi?id=484712 --- Comment #1 from Alexander Reinholdt --- Thank you for reporting this issue! I tried to reproduce this by plugging in my Android based phone via USB-C, but Smb4K did not crash. Could you please shortly explain, how you connect your iPhone? Also, is it possible to get a backtrace of the crash? That would be very helpful for finding the problem. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 480652] Regression when closing/hiding the main window
https://bugs.kde.org/show_bug.cgi?id=480652 --- Comment #8 from Alexander Reinholdt --- Okay, thanks! -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 480652] Regression when closing/hiding the main window
https://bugs.kde.org/show_bug.cgi?id=480652 --- Comment #6 from Alexander Reinholdt --- Just for my information: Is the second regression then also connected with that issue in Qt? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 480652] Regression when closing/hiding the main window
https://bugs.kde.org/show_bug.cgi?id=480652 --- Comment #4 from Alexander Reinholdt --- Created attachment 165446 --> https://bugs.kde.org/attachment.cgi?id=165446=edit Wayland debug output This is the requested debug output. Smb4K started docked to the system tray, i.e. the main window was hidden. I restored it and pressed the close button. After that I killed Smb4K with CTRL+C in the terminal (regression 2 is still there). -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 480652] New: Regression when closing/hiding the main window
https://bugs.kde.org/show_bug.cgi?id=480652
Bug ID: 480652
Summary: Regression when closing/hiding the main window
Classification: Plasma
Product: kwin
Version: master
Platform: Neon
OS: Linux
Status: REPORTED
Severity: major
Priority: NOR
Component: general
Assignee: kwin-bugs-n...@kde.org
Reporter: alexander.reinho...@kdemail.net
Target Milestone: ---
Hello,
I am the developer of Smb4K and I am currently testing my application under
Plasma 6 / KWin 6 on KDE neon unstable. I found some regressions compared to
Plasma 5 / KWin 5 regarding the closing of the main window. I use KWin with
Wayland, the default on KDE neon unstable.
SUMMARY
There are two things that do not work as expected anymore and which worked fine
before:
(1) Closing the main window through the close button of the window. This should
result in hiding the main window to the system tray.
(2) Closing the main window through the Quit action. This should result in
exiting the application.
The main window has a queryClose() function that currently looks like this:
bool Smb4KMainWindow::queryClose()
{
if (!m_quitting && !qApp->isSavingSession() && isVisible()) {
// This part has been copied from JuK application.
KMessageBox::information(this,
i18n("Closing the main window will keep
Smb4K running in the system tray."
"Use Quit from the File
menu to quit the application."),
i18n("Docking"),
QStringLiteral("DockToSystemTrayInfo"));
setVisible(false);
return false;
}
return true;
}
There is also a slot connected to the Quit action:
void Smb4KMainWindow::slotQuit()
{
m_quitting = true;
// saveSettings();
close();
QCoreApplication::quit();
}
Regression 1:
When queryClose() is called and the application is not supposed to be exited,
it returns false as it should in that case. However, after the message box is
shown, the main window won't hide. That worked under KWin 5 perfectly.
Regression 2:
When queryClose() is called through the Quit action, the main window will
eventually be closed, but Smb4K is still running and seem to enter an infinite
loop. When running Smb4K in gdb and killing it when it is in the loop, I get
this output:
Thread 1 "smb4k" received signal SIGINT, Interrupt.
0x773e9934 in QApplication::topLevelWidgets() () from
/lib/x86_64-linux-gnu/libQt6Widgets.so.6
I am not that familiar with gdb. If I can provide more info using it, please
give me a hint.
STEPS TO REPRODUCE
Try to quit Smb4K (from master) using either the "Close" button of the main
window (triggering Regression 1) or the "Quit" action (triggering Regression
2).
OBSERVED RESULT
The main window does not hide (Regression 1) or does not exit, but instead
enters an infinite loop (Regression 2).
EXPECTED RESULT
The main window either hides or the application exits.
SOFTWARE/OS VERSIONS
Linux/KDE Plasma: KDE neon Unstable Edition (updated 01-02-2024)
(available in About System)
KDE Plasma Version: 6.0.80
KDE Frameworks Version: 5.249
Qt Version: 6.6.1
ADDITIONAL INFORMATION
Graphics platform is Wayland.
--
You are receiving this mail because:
You are watching all bug changes.
[Smb4k] [Bug 461895] New Feature: Pass the hash
https://bugs.kde.org/show_bug.cgi?id=461895 --- Comment #1 from Alexander Reinholdt --- (In reply to rednaker from comment #0) > Currently, smb4k does not have hash authentication. I want it to have a > passthehash feature similar to smbclient. Thank you for this feature request and please excuse the very long waiting time. I am planning to implement this feature, but since I never have used it personally, I have got a question: Are you using the NT password hash for every server you connect to or only for specified ones? I wonder if it would be a global setting, a setting for specified servers or if it could be both. -- You are receiving this mail because: You are watching all bug changes.
[Smb4k] [Bug 472467] SMB4K Crash saving bookmarks
https://bugs.kde.org/show_bug.cgi?id=472467 Alexander Reinholdt changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED Latest Commit||https://invent.kde.org/netw ||ork/smb4k/-/commit/5d43e3e8 ||adb545651325dff7b77b5dee992 ||a1a9f --- Comment #8 from Alexander Reinholdt --- Git commit 5d43e3e8adb545651325dff7b77b5dee992a1a9f by Alexander Reinholdt. Committed on 28/07/2023 at 07:06. Pushed by areinholdt into branch '3.2'. Fix crash in the bookmark menu and remove unnecessary/dysfunctional code. M +1-89 smb4k/smb4kbookmarkmenu.cpp M +0-15 smb4k/smb4kbookmarkmenu.h https://invent.kde.org/network/smb4k/-/commit/5d43e3e8adb545651325dff7b77b5dee992a1a9f -- You are receiving this mail because: You are watching all bug changes.
[Smb4k] [Bug 472467] SMB4K Crash saving bookmarks
https://bugs.kde.org/show_bug.cgi?id=472467 --- Comment #7 from Alexander Reinholdt --- I found the place where the crash happens. It's in the bookmark menu. At the moment I am investigating why it happens. I hope I can come up with a fix soon. -- You are receiving this mail because: You are watching all bug changes.
[Smb4k] [Bug 472467] SMB4K Crash saving bookmarks
https://bugs.kde.org/show_bug.cgi?id=472467 --- Comment #3 from Alexander Reinholdt --- (In reply to Alexander Reinholdt from comment #2) > Thank you for reporting this issue and please excuse my late response. Right > now my time is limited to work on Smb4K and follow the bug tracker. > > I will try to reproduce the bug and come up with a fix. Meanwhile, if > possible, could you please try the latest version (3.2.1) of Smb4K and check > if the problem is present there as well? To avoid data loss (I am very sorry > for the data loss that happened to your co-worker!), please back up the file > ~/.local/share/smb4k/bookmarks.xml before doing the tests. You can download the latest version from here (it also includes WS Discovery Support): https://software.opensuse.org//download.html?project=home%3Aareinholdt=smb4k -- You are receiving this mail because: You are watching all bug changes.
[Smb4k] [Bug 472467] SMB4K Crash saving bookmarks
https://bugs.kde.org/show_bug.cgi?id=472467 --- Comment #2 from Alexander Reinholdt --- Thank you for reporting this issue and please excuse my late response. Right now my time is limited to work on Smb4K and follow the bug tracker. I will try to reproduce the bug and come up with a fix. Meanwhile, if possible, could you please try the latest version (3.2.1) of Smb4K and check if the problem is present there as well? To avoid data loss (I am very sorry for the data loss that happened to your co-worker!), please back up the file ~/.local/share/smb4k/bookmarks.xml before doing the tests. -- You are receiving this mail because: You are watching all bug changes.
[Smb4k] [Bug 465392] Just flat doesn't work on Zorin 16.2
https://bugs.kde.org/show_bug.cgi?id=465392 --- Comment #6 from Alexander Reinholdt --- (In reply to pjd...@netzero.com from comment #5) > the following packages have unmet dependencies when I try to install > current version for Ubuntu 20.4 (zorin 16) Could you please provide some information which version of Smb4K you were trying to install? The one from build.opensuse.org? Which packages were missing or could not be installed? -- You are receiving this mail because: You are watching all bug changes.
[Smb4k] [Bug 465392] Just flat doesn't work on Zorin 16.2
https://bugs.kde.org/show_bug.cgi?id=465392 Alexander Reinholdt changed: What|Removed |Added Status|REPORTED|NEEDSINFO Resolution|--- |WAITINGFORINFO --- Comment #1 from Alexander Reinholdt --- Thank you for reporting this issue. Since the version you are using is already quite old, your problem has most likely already been fixed. Could you please try the latest version (e. g. from here: https://software.opensuse.org//download.html?project=home%3Aareinholdt=smb4k) and check if the problem persists? Thanks. -- You are receiving this mail because: You are watching all bug changes.
[Smb4k] [Bug 462988] The network communication failed
https://bugs.kde.org/show_bug.cgi?id=462988 Alexander Reinholdt changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #1 from Alexander Reinholdt --- This bus has been already fix. Please use the latest version. Closing bug report. -- You are receiving this mail because: You are watching all bug changes.
[Smb4k] [Bug 463637] Unknown parameter 'nolock'
https://bugs.kde.org/show_bug.cgi?id=463637 Alexander Reinholdt changed: What|Removed |Added Latest Commit|https://invent.kde.org/netw |https://invent.kde.org/netw |ork/smb4k/commit/1089ec4d39 |ork/smb4k/commit/c7b2619048 |e6025aa33447434ad02af074d48 |205d6e9424d46cfe42054e3f4d8 |4be |485 --- Comment #2 from Alexander Reinholdt --- Git commit c7b2619048205d6e9424d46cfe42054e3f4d8485 by Alexander Reinholdt. Committed on 04/01/2023 at 09:37. Pushed by areinholdt into branch '3.1'. Fix problems with the 'nolock' option for mount.cifs. M +1-1core/smb4kmounter.cpp https://invent.kde.org/network/smb4k/commit/c7b2619048205d6e9424d46cfe42054e3f4d8485 -- You are receiving this mail because: You are watching all bug changes.
[Smb4k] [Bug 463637] Unknown parameter 'nolock'
https://bugs.kde.org/show_bug.cgi?id=463637 Alexander Reinholdt changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED Latest Commit||https://invent.kde.org/netw ||ork/smb4k/commit/1089ec4d39 ||e6025aa33447434ad02af074d48 ||4be --- Comment #1 from Alexander Reinholdt --- Git commit 1089ec4d39e6025aa33447434ad02af074d484be by Alexander Reinholdt. Committed on 04/01/2023 at 09:36. Pushed by areinholdt into branch 'master'. Fix problems with using 'nolock' option with mount.cifs. M +1-1core/smb4kmounter.cpp M +2-2core/smb4kmountsettings_linux.kcfg M +2-2doc/index.docbook https://invent.kde.org/network/smb4k/commit/1089ec4d39e6025aa33447434ad02af074d484be -- You are receiving this mail because: You are watching all bug changes.
[Smb4k] [Bug 462798] Smb4K mount functionality is broken after Kubuntu upgrade from 20.04 to 22.04
https://bugs.kde.org/show_bug.cgi?id=462798 Alexander Reinholdt changed: What|Removed |Added Latest Commit|https://invent.kde.org/netw |https://invent.kde.org/netw |ork/smb4k/commit/5811556c6f |ork/smb4k/commit/c4c9b72ecd |4df76c8be287d5e1f022862c4df |5f207adeab50b31f334ecae204b |ab9 |57b --- Comment #14 from Alexander Reinholdt --- Git commit c4c9b72ecd5f207adeab50b31f334ecae204b57b by Alexander Reinholdt. Committed on 11/12/2022 at 07:25. Pushed by areinholdt into branch '3.1'. Forgot to fix FreeBSD code. M +1-1core/smb4kmounter.cpp https://invent.kde.org/network/smb4k/commit/c4c9b72ecd5f207adeab50b31f334ecae204b57b -- You are receiving this mail because: You are watching all bug changes.
[Smb4k] [Bug 462798] Smb4K mount functionality is broken after Kubuntu upgrade from 20.04 to 22.04
https://bugs.kde.org/show_bug.cgi?id=462798 Alexander Reinholdt changed: What|Removed |Added Latest Commit|https://invent.kde.org/netw |https://invent.kde.org/netw |ork/smb4k/commit/6a02c8ee62 |ork/smb4k/commit/5811556c6f |31e5f001dda3c8fa3ea8c76ab50 |4df76c8be287d5e1f022862c4df |8f4 |ab9 --- Comment #13 from Alexander Reinholdt --- Git commit 5811556c6f4df76c8be287d5e1f022862c4dfab9 by Alexander Reinholdt. Committed on 11/12/2022 at 07:24. Pushed by areinholdt into branch 'master'. Forgot to fix FreeBSD code. M +1-1core/smb4kmounter.cpp https://invent.kde.org/network/smb4k/commit/5811556c6f4df76c8be287d5e1f022862c4dfab9 -- You are receiving this mail because: You are watching all bug changes.
[Smb4k] [Bug 462798] Smb4K mount functionality is broken after Kubuntu upgrade from 20.04 to 22.04
https://bugs.kde.org/show_bug.cgi?id=462798 Alexander Reinholdt changed: What|Removed |Added Latest Commit|https://invent.kde.org/netw |https://invent.kde.org/netw |ork/smb4k/commit/3423493d97 |ork/smb4k/commit/6a02c8ee62 |bb916da083f781271ddd18fb402 |31e5f001dda3c8fa3ea8c76ab50 |6f6 |8f4 --- Comment #12 from Alexander Reinholdt --- Git commit 6a02c8ee6231e5f001dda3c8fa3ea8c76ab508f4 by Alexander Reinholdt. Committed on 11/12/2022 at 05:56. Pushed by areinholdt into branch 'master'. Apply fix from 3.1: Always pass the domain if it is not empty and not a DNS-SD domain. M +1-1core/smb4kmounter.cpp https://invent.kde.org/network/smb4k/commit/6a02c8ee6231e5f001dda3c8fa3ea8c76ab508f4 -- You are receiving this mail because: You are watching all bug changes.
[Smb4k] [Bug 462798] Smb4K mount functionality is broken after Kubuntu upgrade from 20.04 to 22.04
https://bugs.kde.org/show_bug.cgi?id=462798 --- Comment #11 from Alexander Reinholdt --- Created attachment 154486 --> https://bugs.kde.org/attachment.cgi?id=154486=edit Latest version with domain handling fix This packages contains a fixed version of the code for mounting. Please try it out and report any issues. Thanks! -- You are receiving this mail because: You are watching all bug changes.
[Smb4k] [Bug 462798] Smb4K mount functionality is broken after Kubuntu upgrade from 20.04 to 22.04
https://bugs.kde.org/show_bug.cgi?id=462798 Alexander Reinholdt changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED Latest Commit||https://invent.kde.org/netw ||ork/smb4k/commit/3423493d97 ||bb916da083f781271ddd18fb402 ||6f6 --- Comment #10 from Alexander Reinholdt --- Git commit 3423493d97bb916da083f781271ddd18fb4026f6 by Alexander Reinholdt. Committed on 10/12/2022 at 14:39. Pushed by areinholdt into branch '3.1'. Always pass the domain if it is not empty and not a DNS-SD domain. M +1-1core/smb4kmounter.cpp https://invent.kde.org/network/smb4k/commit/3423493d97bb916da083f781271ddd18fb4026f6 -- You are receiving this mail because: You are watching all bug changes.
[Smb4k] [Bug 462798] Smb4K mount functionality is broken after Kubuntu upgrade from 20.04 to 22.04
https://bugs.kde.org/show_bug.cgi?id=462798 --- Comment #8 from Alexander Reinholdt --- Thank you very much for the confirmation. What confuses me a bit is that you wrote that in Smb4K 3.0.x it was sufficient to leave the domain empty. In that case the domain was not passed to the mount command also back then... I will commit a fix. Would you be willing to test the new version? -- You are receiving this mail because: You are watching all bug changes.
[Smb4k] [Bug 462798] Smb4K mount functionality is broken after Kubuntu upgrade from 20.04 to 22.04
https://bugs.kde.org/show_bug.cgi?id=462798 --- Comment #6 from Alexander Reinholdt --- I think I found the problem. Could you please confirm that mounting via the command line fails if you do not provide the domain? -- You are receiving this mail because: You are watching all bug changes.
[Smb4k] [Bug 462798] Smb4K mount functionality is broken after Kubuntu upgrade from 20.04 to 22.04
https://bugs.kde.org/show_bug.cgi?id=462798 --- Comment #4 from Alexander Reinholdt --- ... ah okay, you already tried 3.1.3 which did not change in the mount code compared to the latest version. So, you do not need to test. -- You are receiving this mail because: You are watching all bug changes.
[Smb4k] [Bug 462798] Smb4K mount functionality is broken after Kubuntu upgrade from 20.04 to 22.04
https://bugs.kde.org/show_bug.cgi?id=462798 --- Comment #3 from Alexander Reinholdt --- Thank you for reporting this issue. Currently I am trying to understand what causes this problem. Could you please give an example mount command line that works? Is the share mounted from within the browser or via the mount dialog? Apart from that, would you be willing to test the latest version for Kubuntu 22.04 (see: https://software.opensuse.org//download.html?project=home%3Aareinholdt=smb4k)? In case you decide to do so, please backup your ~/.local/share/smb4k/custom_options.xml and ~/.local/share/smb4k/bookmarks.xml files to be able to restore the old formats after your tests. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 459929] USB-C connected display goes black when mouse is moved from laptop display
https://bugs.kde.org/show_bug.cgi?id=459929 --- Comment #8 from Alexander Reinholdt --- (In reply to Simon Redman from comment #7) > Issue opened here: https://github.com/DisplayLink/evdi/issues/388 > > I have replaced my displaylink dock because it was causing too many > headaches but I still have it on my desk so I can test. Someone who is more > impacted (Alexander Reinholdt, if you're following this bug, for instance) > may want to take point on responding to the EVDI bug if the developers on > that side respond. Sure, I will track that bug report and will give answers if requested. Thanks for opening the bug report with the EVDI developers. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 459085] Second monitor is disabled in Displaylink setup under Wayland
https://bugs.kde.org/show_bug.cgi?id=459085 --- Comment #21 from Alexander Reinholdt --- Cool, it works again! Even the faulty logout behavior is gone. Thanks! The only thing I noticed is that under certain circumstances the mouse now drags a tail behind it (minor display glitch). But I can live with that for the time being. So, I leave the KWIN_FORCE_SW_CURSOR=1 variable in the /etc/environment until the new evdi driver version is released? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 459085] Second monitor is disabled in Displaylink setup under Wayland
https://bugs.kde.org/show_bug.cgi?id=459085 --- Comment #19 from Alexander Reinholdt --- What I just wanted to mention - because it confuses me quite a bit - is that when I am in the wayland session and log out, I will immediately be logged back in without sddm asking me for my password. I guess that is a side effect of the wayland malfunction, but I think that is not good... -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 459085] Second monitor is disabled in Displaylink setup under Wayland
https://bugs.kde.org/show_bug.cgi?id=459085 --- Comment #18 from Alexander Reinholdt --- Created attachment 153359 --> https://bugs.kde.org/attachment.cgi?id=153359=edit dmesg drm debug output Here is the requested output. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 459085] Second monitor is disabled in Displaylink setup under Wayland
https://bugs.kde.org/show_bug.cgi?id=459085 --- Comment #16 from Alexander Reinholdt --- Created attachment 153357 --> https://bugs.kde.org/attachment.cgi?id=153357=edit journalctl output with debug Here is the output. I ran the command without sudo. If that is needed as well, please let me know. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 459085] Second monitor is disabled in Displaylink setup under Wayland
https://bugs.kde.org/show_bug.cgi?id=459085 --- Comment #14 from Alexander Reinholdt --- Created attachment 153222 --> https://bugs.kde.org/attachment.cgi?id=153222=edit New journalctl output journalctl output (after running kwriteconfig5 command as normal user and with sudo) -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 459085] Second monitor is disabled in Displaylink setup under Wayland
https://bugs.kde.org/show_bug.cgi?id=459085 --- Comment #13 from Alexander Reinholdt --- (In reply to Zamundaaa from comment #12) > Your journalctl output is empty. Did you change the systemd boot setting? If > so, you can re-enable it with "kwriteconfig5 --file startkderc --group > General --key systemdBoot true" I did not change anything in the boot process. Maybe something was wrong with the command I issued in the terminal the first time, since - after running the command you gave above as normal user and with sudo - I can now provide the needed output dating back to September 19th. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 459085] Second monitor is disabled in Displaylink setup under Wayland
https://bugs.kde.org/show_bug.cgi?id=459085 --- Comment #11 from Alexander Reinholdt --- Created attachment 153159 --> https://bugs.kde.org/attachment.cgi?id=153159=edit dmesg output after running systemsettings Collected after opening systemsettings where I was told that one display was removed and the settings were reloaded. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 459085] Second monitor is disabled in Displaylink setup under Wayland
https://bugs.kde.org/show_bug.cgi?id=459085 --- Comment #10 from Alexander Reinholdt --- Created attachment 153158 --> https://bugs.kde.org/attachment.cgi?id=153158=edit dmesg output Collected directly after reboot and login into the wayland session. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 459085] Second monitor is disabled in Displaylink setup under Wayland
https://bugs.kde.org/show_bug.cgi?id=459085 --- Comment #9 from Alexander Reinholdt --- Created attachment 153157 --> https://bugs.kde.org/attachment.cgi?id=153157=edit journalctl output Collected directly after reboot and login into the wayland session. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 459085] Second monitor is disabled in Displaylink setup under Wayland
https://bugs.kde.org/show_bug.cgi?id=459085 --- Comment #8 from Alexander Reinholdt --- Created attachment 153156 --> https://bugs.kde.org/attachment.cgi?id=153156=edit drm_info output Collected directly after reboot and login into the wayland session. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 459085] Second monitor is disabled in Displaylink setup under Wayland
https://bugs.kde.org/show_bug.cgi?id=459085 --- Comment #6 from Alexander Reinholdt --- Today, I upgraded to plasma 5.26 (Manjaro testing). The problem persists. Under X11, fortunately, my setup works somehow (I always have to re-adjust my settings on startup), but under Wayland, my external monitor is still not recognized. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 459085] Second monitor is disabled in Displaylink setup under Wayland
https://bugs.kde.org/show_bug.cgi?id=459085 Alexander Reinholdt changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 459085] Second monitor is disabled in Displaylink setup under Wayland
https://bugs.kde.org/show_bug.cgi?id=459085 --- Comment #4 from Alexander Reinholdt --- If you need some more information, please let me know. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 459085] Second monitor is disabled in Displaylink setup under Wayland
https://bugs.kde.org/show_bug.cgi?id=459085 --- Comment #3 from Alexander Reinholdt --- I created a new test user. After logging into the account with Plasma Wayland, it takes a few seconds and the second monitor is recognized and seems to work. However, only the background is seen. No panel or plasmoids. If I then go to systemsettings to adjust the settings, the behavior seen in the video starts and the external monitor gets unusable. Interestingly, the monitor does not get blank / black, but the background shown before is still visible. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 459085] Second monitor is disabled in Displaylink setup under Wayland
https://bugs.kde.org/show_bug.cgi?id=459085 Alexander Reinholdt changed: What|Removed |Added CC||alexander.reinholdt@kdemail ||.net --- Comment #2 from Alexander Reinholdt --- Created attachment 152057 --> https://bugs.kde.org/attachment.cgi?id=152057=edit KWin behavior while Displaylink docking station is connected I took a video with my mobile phone showing the described behavior. However, on second thought, this might not exactly be a crash. In my setting under Plasma 5.24, the laptop display was deactivated and only the external monitor activated. Maybe what we see here is the attempt to activate the external monitor, which fails, and then the fallback to the laptop monitor... By the way, I have displaylink-connect installed (package from AUR) and both monitors are recognized initially: SDDM can be seen on both. But when I enter the Plasma Wayland session, the external monitor stops working and the behavior is as can be seen in the video. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 459085] New: Second monitor is disabled in Displaylink setup under Wayland
https://bugs.kde.org/show_bug.cgi?id=459085 Bug ID: 459085 Summary: Second monitor is disabled in Displaylink setup under Wayland Product: kwin Version: 5.25.5 Platform: Manjaro OS: Linux Status: REPORTED Severity: grave Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: alexander.reinho...@kdemail.net Target Milestone: --- SUMMARY I am using a TUXEDO Computer PULSE 15 (gen 1, specs see down below) laptop with an i-tec Displaylink adapter (TUXEDO Office Hub). After the upgrade from Plasma 5.24.5 to 5.25.5, my external monitor is disabled when starting Plasma under Wayland. Also, it seems that the display is entering an infinite loop of crashes and attempts to recover. Strangely, changing once into the console (e. g. CTRL+ALT+F3) stops this loop. However, the external monitor is never activated / recognized. So, from my point of view, this is a regression compared to 5.24, since my setup worked back then. Using Xorg is currently unfortunately not an option, since then everything is slowed down to a few FPS. Maybe I can provide a screenshot of the config page with the error message shown, but due to the continuously crashing KWin, it's quite hard to do anything... STEPS TO REPRODUCE 1. Attach the laptop to the Displaylink adapter 2. Log in with the Wayland session 3. OBSERVED RESULT The external monitor is not recognized / activated and the display / KWin enters an infinite loop of crash and recovery. EXPECTED RESULT Working display setup. SOFTWARE/OS VERSIONS Operating System: Manjaro Linux KDE Plasma Version: 5.25.5 KDE Frameworks Version: 5.97.0 Qt Version: 5.15.5 Kernel Version: 5.19.7-1-MANJARO (64-bit) Graphics Platform: Wayland Processors: 16 × AMD Ryzen 7 4800H with Radeon Graphics Memory: 15.1 GiB of RAM Graphics Processor: AMD RENOIR Manufacturer: TUXEDO Product Name: TUXEDO Pulse 15 Gen1 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[frameworks-solid] [Bug 442258] Solid::NetworkShare does not know SMB3 filesystem
https://bugs.kde.org/show_bug.cgi?id=442258 Alexander Reinholdt changed: What|Removed |Added Status|ASSIGNED|RESOLVED Version Fixed In||5.98.0 Resolution|--- |FIXED -- You are receiving this mail because: You are watching all bug changes.
[Smb4k] [Bug 455772] smb4k 3.1.2 imports old .kde4/share/apps/smb4k/bookmarks.xml and dislikes format
https://bugs.kde.org/show_bug.cgi?id=455772 Alexander Reinholdt changed: What|Removed |Added Latest Commit|https://invent.kde.org/netw |https://invent.kde.org/netw |ork/smb4k/commit/c735be02cd |ork/smb4k/commit/6b486314a1 |49de6497228194a1dbb639dbbc9 |9e192de18e39ba28b3692483b23 |ec3 |399 --- Comment #3 from Alexander Reinholdt --- Git commit 6b486314a19e192de18e39ba28b3692483b23399 by Alexander Reinholdt. Committed on 06/07/2022 at 18:16. Pushed by areinholdt into branch '3.1'. Remove KDE4 migration code. M +2-93 smb4k/main.cpp https://invent.kde.org/network/smb4k/commit/6b486314a19e192de18e39ba28b3692483b23399 -- You are receiving this mail because: You are watching all bug changes.
[Smb4k] [Bug 455772] smb4k 3.1.2 imports old .kde4/share/apps/smb4k/bookmarks.xml and dislikes format
https://bugs.kde.org/show_bug.cgi?id=455772 Alexander Reinholdt changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED Latest Commit||https://invent.kde.org/netw ||ork/smb4k/commit/c735be02cd ||49de6497228194a1dbb639dbbc9 ||ec3 --- Comment #2 from Alexander Reinholdt --- Git commit c735be02cd49de6497228194a1dbb639dbbc9ec3 by Alexander Reinholdt. Committed on 03/07/2022 at 08:02. Pushed by areinholdt into branch 'master'. Remove KDE4 migration code. M +1-70 smb4k/main.cpp https://invent.kde.org/network/smb4k/commit/c735be02cd49de6497228194a1dbb639dbbc9ec3 -- You are receiving this mail because: You are watching all bug changes.
[Smb4k] [Bug 454687] smb4k crash when trying to mount
https://bugs.kde.org/show_bug.cgi?id=454687 Alexander Reinholdt changed: What|Removed |Added Latest Commit|https://invent.kde.org/netw |https://invent.kde.org/netw |ork/smb4k/commit/e09add2429 |ork/smb4k/commit/b8821ed967 |82336c513789d2196bc7d006620 |edc30a99d5fc024ca8a0b835173 |f93 |8c8 --- Comment #2 from Alexander Reinholdt --- Git commit b8821ed967edc30a99d5fc024ca8a0b8351738c8 by Aexander Reinholdt. Committed on 04/06/2022 at 09:05. Pushed by areinholdt into branch '3.1'. Fix a crash when the mount point is not available. M +4-1core/smb4kshare.cpp https://invent.kde.org/network/smb4k/commit/b8821ed967edc30a99d5fc024ca8a0b8351738c8 -- You are receiving this mail because: You are watching all bug changes.
[Smb4k] [Bug 454687] smb4k crash when trying to mount
https://bugs.kde.org/show_bug.cgi?id=454687 Alexander Reinholdt changed: What|Removed |Added Latest Commit||https://invent.kde.org/netw ||ork/smb4k/commit/e09add2429 ||82336c513789d2196bc7d006620 ||f93 Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #1 from Alexander Reinholdt --- Git commit e09add242982336c513789d2196bc7d006620f93 by Alexander Reinholdt. Committed on 04/06/2022 at 08:54. Pushed by areinholdt into branch 'master'. Fix a crash when the mount point is not available. M +4-1core/smb4kshare.cpp https://invent.kde.org/network/smb4k/commit/e09add242982336c513789d2196bc7d006620f93 -- You are receiving this mail because: You are watching all bug changes.
[Smb4k] [Bug 417754] Starts with error "The URL does not exist"
https://bugs.kde.org/show_bug.cgi?id=417754 Alexander Reinholdt changed: What|Removed |Added Resolution|--- |FIXED Status|REOPENED|RESOLVED --- Comment #21 from Alexander Reinholdt --- Since this bug has already been fixed, I close this report. -- You are receiving this mail because: You are watching all bug changes.
[Smb4k] [Bug 452293] command line error in notification.
https://bugs.kde.org/show_bug.cgi?id=452293 Alexander Reinholdt changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #2 from Alexander Reinholdt --- Since this bug has already been fixed, I close this report. -- You are receiving this mail because: You are watching all bug changes.
[Smb4k] [Bug 452293] command line error in notification.
https://bugs.kde.org/show_bug.cgi?id=452293 --- Comment #1 from Alexander Reinholdt --- Thank you very much for reporting this issue. However, it has already been fixed in later versions. From the screenshot you attached, I see that you are using MX Linux, presumably based on Debian 10 (buster). If it is possible for you, I suggest that you try the latest release (version 3.1.2) for Debian 10 provided here: https://software.opensuse.org//download.html?project=home%3Aareinholdt=smb4k. With the new version, the error message should disappear. NOTE: Since Smb4K version 3.0.0, DNS-SD and WS Discovery as a replacement for the domain lookup using the insecure SMB protocol version 1 are supported. -- You are receiving this mail because: You are watching all bug changes.
[Smb4k] [Bug 442187] Smb4K 3.1.0 still has frustrating, old usability glitches and bugs (explained in description). Kills usability.
https://bugs.kde.org/show_bug.cgi?id=442187 --- Comment #26 from Alexander Reinholdt --- Git commit 50ada05e1220584bfa492678a9e502c16f359134 by Alexander Reinholdt. Committed on 06/12/2021 at 05:03. Pushed by areinholdt into branch 'master'. It seems that menu()->adjustSize() is needed to avoid the nasty display glitch. M +2-0smb4k/smb4kbookmarkmenu.cpp M +2-0smb4k/smb4ksharesmenu.cpp https://invent.kde.org/network/smb4k/commit/50ada05e1220584bfa492678a9e502c16f359134 -- You are receiving this mail because: You are watching all bug changes.
[Smb4k] [Bug 442187] Smb4K 3.1.0 still has frustrating, old usability glitches and bugs (explained in description). Kills usability.
https://bugs.kde.org/show_bug.cgi?id=442187 --- Comment #25 from Alexander Reinholdt --- Git commit 14f06271f5e6a8939258d22574b23f3f253cf7e3 by Alexander Reinholdt. Committed on 18/11/2021 at 20:46. Pushed by areinholdt into branch 'master'. Implement a better fix for bug 442187: Process all events after the shares / bookmarks were added. Fix null pointer access crash in the bookmarks menu. Applied clang-format. M +33 -30 smb4k/smb4kbookmarkmenu.cpp M +1-1smb4k/smb4kbookmarkmenu.h M +10 -10 smb4k/smb4ksharesmenu.cpp https://invent.kde.org/network/smb4k/commit/14f06271f5e6a8939258d22574b23f3f253cf7e3 -- You are receiving this mail because: You are watching all bug changes.
[Smb4k] [Bug 442187] Smb4K 3.1.0 still has frustrating, old usability glitches and bugs (explained in description). Kills usability.
https://bugs.kde.org/show_bug.cgi?id=442187 --- Comment #24 from Alexander Reinholdt --- Git commit 0f4e619c94f6591f988e27d5afb40e076dc1e173 by Alexander Reinholdt. Committed on 15/11/2021 at 18:00. Pushed by areinholdt into branch 'master'. Further improved code of the bookmark and the shares menu. M +11 -16 smb4k/smb4kbookmarkmenu.cpp M +12 -17 smb4k/smb4ksharesmenu.cpp https://invent.kde.org/network/smb4k/commit/0f4e619c94f6591f988e27d5afb40e076dc1e173 -- You are receiving this mail because: You are watching all bug changes.
[Smb4k] [Bug 442187] Smb4K 3.1.0 still has frustrating, old usability glitches and bugs (explained in description). Kills usability.
https://bugs.kde.org/show_bug.cgi?id=442187 --- Comment #23 from Alexander Reinholdt --- Git commit 0187849ec06324ec37ac3fc0da4bd9cad2e863d5 by Alexander Reinholdt. Committed on 12/11/2021 at 06:18. Pushed by areinholdt into branch 'master'. Refactored the bookmark menu to overcome the same glitch the shares menu suffered from. This is still work in progress. M +11 -10 core/smb4kbookmarkhandler.cpp M +14 -0core/smb4kbookmarkhandler.h M +506 -249 smb4k/smb4kbookmarkmenu.cpp M +42 -12 smb4k/smb4kbookmarkmenu.h https://invent.kde.org/network/smb4k/commit/0187849ec06324ec37ac3fc0da4bd9cad2e863d5 -- You are receiving this mail because: You are watching all bug changes.
[Smb4k] [Bug 442187] Smb4K 3.1.0 still has frustrating, old usability glitches and bugs (explained in description). Kills usability.
https://bugs.kde.org/show_bug.cgi?id=442187 --- Comment #22 from Alexander Reinholdt --- (In reply to flan_suse from comment #20) > (In reply to Alexander Reinholdt from comment #19) > > Could it be due to something upstream (Qt / KDE)? > > However, I have never noticed this behaviour anywhere else except for Smb4K, > so it might not be upstream. After further testing, it became obvious to me that the shares menu was not correctly resized. The code now forces an adjustment of the size each time a share is mounted and added to the menu. So far, I did not see the glitch anymore. I committed the code to master and will backport it to the 3.1 branch soon. -- You are receiving this mail because: You are watching all bug changes.
[Smb4k] [Bug 442187] Smb4K 3.1.0 still has frustrating, old usability glitches and bugs (explained in description). Kills usability.
https://bugs.kde.org/show_bug.cgi?id=442187 --- Comment #21 from Alexander Reinholdt --- Git commit 092fdfaf0ba32f3d7774a7a78d71d02c65f4e9e9 by Alexander Reinholdt. Committed on 03/11/2021 at 05:38. Pushed by areinholdt into branch 'master'. To fixed a display glitch in the shares menu, where the first mounted share might not be shown. Refactored code on the way. M +186 -102 smb4k/smb4ksharesmenu.cpp M +29 -4smb4k/smb4ksharesmenu.h https://invent.kde.org/network/smb4k/commit/092fdfaf0ba32f3d7774a7a78d71d02c65f4e9e9 -- You are receiving this mail because: You are watching all bug changes.
[Smb4k] [Bug 442187] Smb4K 3.1.0 still has frustrating, old usability glitches and bugs (explained in description). Kills usability.
https://bugs.kde.org/show_bug.cgi?id=442187 --- Comment #19 from Alexander Reinholdt --- Continuing my tests, I found out that the shares are obviously correctly added to the menu (the number of actions in the menu is correct), but they are not displayed. What causes this issue, I haven't found out yet, though. Even repainting the whole menu did not fix it. I suspect that I am missing something... -- You are receiving this mail because: You are watching all bug changes.
[Smb4k] [Bug 442187] Smb4K 3.1.0 still has frustrating, old usability glitches and bugs (explained in description). Kills usability.
https://bugs.kde.org/show_bug.cgi?id=442187 --- Comment #17 from Alexander Reinholdt --- (In reply to flan_suse from comment #15) > Created attachment 142640 [details] > greyed-out-mounted-shares-tray-icon > > >These glitches involves "Unmount All" and "Unmount" being greyed out in the > >tray context menu, yet working normally from the main window. > > Since this bug is less predictable compared to the others, it's tricky to > catch in real-time. However, this is what it looks like. This bug is quite nasty. I thought I fixed it here and now it reappears with the refactored / reworked code as well. I have got the impression that it only appears when the main window is minimized, the shares menu has never been opened before in the tray's popup menu and the first share is mounted. Is that also your experience? -- You are receiving this mail because: You are watching all bug changes.
[Smb4k] [Bug 442187] Smb4K 3.1.0 still has frustrating, old usability glitches and bugs (explained in description). Kills usability.
https://bugs.kde.org/show_bug.cgi?id=442187 Alexander Reinholdt changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 -- You are receiving this mail because: You are watching all bug changes.
[Smb4k] [Bug 442187] Smb4K 3.1.0 still has frustrating, old usability glitches and bugs (explained in description). Kills usability.
https://bugs.kde.org/show_bug.cgi?id=442187 --- Comment #16 from Alexander Reinholdt --- (In reply to flan_suse from comment #15) > The test share is not in my Bookmarks. I manually go to the Tray -> > right-click -> Open Mount Dialog > > It mounts correctly. > > Browseable with Dolphin. > > Works from the Smb4K Main Window. > > However, you will notice "Mounted Shares" from the Tray icon is "greyed out" > as if nothing is currently mounted. > > This screenshot was taken with Smb4K version 3.1.1. Thank you for providing the screenshot. I could reproduce this issue in the meantime and will search for the error now. -- You are receiving this mail because: You are watching all bug changes.
[Smb4k] [Bug 397453] SMB4K failed logins result in crash
https://bugs.kde.org/show_bug.cgi?id=397453 Alexander Reinholdt changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #3 from Alexander Reinholdt --- This problem should be fixed. Please reopen this bug report or file a new one, if the problem reoccurs. -- You are receiving this mail because: You are watching all bug changes.
[Smb4k] [Bug 434543] SMB4K not mounting share on NAS
https://bugs.kde.org/show_bug.cgi?id=434543 Alexander Reinholdt changed: What|Removed |Added Resolution|--- |WORKSFORME Status|REPORTED|RESOLVED --- Comment #3 from Alexander Reinholdt --- Closing this bug report, since the problem seems to be solved. Please reopen this report or file a new one, if it should reappear. -- You are receiving this mail because: You are watching all bug changes.
[Smb4k] [Bug 442187] Smb4K 3.1.0 still has frustrating, old usability glitches and bugs (explained in description). Kills usability.
https://bugs.kde.org/show_bug.cgi?id=442187 --- Comment #13 from Alexander Reinholdt --- The problem with the freezing main window should be fixed in Smb4K 3.1.1. Could you please confirm this? -- You are receiving this mail because: You are watching all bug changes.
[Smb4k] [Bug 430627] Remounting of previously used shares on program start
https://bugs.kde.org/show_bug.cgi?id=430627 Alexander Reinholdt changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED Version Fixed In||3.1.1 --- Comment #7 from Alexander Reinholdt --- This problem is fixed in version 3.1.1. Please reopen this bug or file a new report, if the problem should reoccur. -- You are receiving this mail because: You are watching all bug changes.
[Smb4k] [Bug 430627] Remounting of previously used shares on program start
https://bugs.kde.org/show_bug.cgi?id=430627 --- Comment #6 from Alexander Reinholdt --- Thank you for the extra information. With Smb4K 3.1.0, I could reproduce the problem. Meanwhile, I rewrote parts of the mounthelper utility and the problem does not occur anymore so far. The fix will be in Smb4K 3.1.1 which will be released shortly. -- You are receiving this mail because: You are watching all bug changes.
[Smb4k] [Bug 442187] Smb4K 3.1.0 still has frustrating, old usability glitches and bugs (explained in description). Kills usability.
https://bugs.kde.org/show_bug.cgi?id=442187 Alexander Reinholdt changed: What|Removed |Added Depends on||442877 Referenced Bugs: https://bugs.kde.org/show_bug.cgi?id=442877 [Bug 442877] Submenus of KStatusNotifierItem open to the wrong side -- You are receiving this mail because: You are watching all bug changes.
[frameworks-knotifications] [Bug 442877] Submenus of KStatusNotifierItem open to the wrong side
https://bugs.kde.org/show_bug.cgi?id=442877 Alexander Reinholdt changed: What|Removed |Added Blocks||442187 Referenced Bugs: https://bugs.kde.org/show_bug.cgi?id=442187 [Bug 442187] Smb4K 3.1.0 still has frustrating, old usability glitches and bugs (explained in description). Kills usability. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-knotifications] [Bug 442877] Submenus of KStatusNotifierItem open to the wrong side
https://bugs.kde.org/show_bug.cgi?id=442877 Alexander Reinholdt changed: What|Removed |Added CC||windows2li...@zoho.com -- You are receiving this mail because: You are watching all bug changes.
[frameworks-knotifications] [Bug 442877] New: Submenus of KStatusNotifierItem open to the wrong side
https://bugs.kde.org/show_bug.cgi?id=442877 Bug ID: 442877 Summary: Submenus of KStatusNotifierItem open to the wrong side Product: frameworks-knotifications Version: 5.85.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdelibs-b...@kde.org Reporter: alexander.reinho...@kdemail.net CC: kdelibs-b...@kde.org Target Milestone: --- SUMMARY When hovering over a submenu of KStatusNotifierItem's context menu the first time, very often the submenu is opened to the wrong side. A user of Smb4K made a video showing this bug very nicely (see also bug report 442187): https://imgur.com/a/WGs2NP9 Besides Smb4K at least also Yakuake is affected by this bug (Height and Width submenus). STEPS TO REPRODUCE 1. Open the context menu of the status notifier item. 2. Hover over a submenu the first time. OBSERVED RESULT The submenu opens to the wrong side and, hence, cannot be seen and used. After moving away and hovering back over the submenu, it most of the time opens to the correct side. EXPECTED RESULT The submenu always opens to the correct side. SOFTWARE/OS VERSIONS Operating System: Manjaro Linux KDE Plasma Version: 5.22.5 KDE Frameworks Version: 5.85.0 Qt Version: 5.15.2 Kernel Version: 5.14.2-1-MANJARO (64-bit) Graphics Platform: X11 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[Smb4k] [Bug 442187] Smb4K 3.1.0 still has frustrating, old usability glitches and bugs (explained in description). Kills usability.
https://bugs.kde.org/show_bug.cgi?id=442187 --- Comment #12 from Alexander Reinholdt --- (In reply to flan_suse from comment #9) > Glad we could narrow down the submenu issue. =) I did not find a way to convince the submenus to always open on the correct side. I will open a bug report against KStatusNotifierItem. -- You are receiving this mail because: You are watching all bug changes.
[Smb4k] [Bug 442187] Smb4K 3.1.0 still has frustrating, old usability glitches and bugs (explained in description). Kills usability.
https://bugs.kde.org/show_bug.cgi?id=442187 --- Comment #11 from Alexander Reinholdt --- Git commit 1856b7c9fe046189ba3952ab89ba7ec5fbac7473 by Alexander Reinholdt. Committed on 23/09/2021 at 08:37. Pushed by areinholdt into branch '3.1'. Merge changes made to the mount helper from master into 3.1. M +212 -252 helpers/smb4kmounthelper.cpp M +4-4helpers/smb4kmounthelper.h https://invent.kde.org/network/smb4k/commit/1856b7c9fe046189ba3952ab89ba7ec5fbac7473 -- You are receiving this mail because: You are watching all bug changes.
[Smb4k] [Bug 442187] Smb4K 3.1.0 still has frustrating, old usability glitches and bugs (explained in description). Kills usability.
https://bugs.kde.org/show_bug.cgi?id=442187 --- Comment #10 from Alexander Reinholdt --- (In reply to flan_suse from comment #9) > Glad we could narrow down the submenu issue. =) > > > Git commit 2a98352625ecdde057e19cd6e4f8dc63a9879d04 by Alexander Reinholdt. > > Since I'm by no means a developer, is that commit in related to the submenu > issue, or the freeze issue from video #1? This is related to the freeze. I changed the way the mount helper waits for the mount process to finish. Now, the application should net freeze anymore even if the mount process hangs. Also, I implemented an automatic termination after 5 seconds, in case a process hangs. -- You are receiving this mail because: You are watching all bug changes.
[Smb4k] [Bug 442187] Smb4K 3.1.0 still has frustrating, old usability glitches and bugs (explained in description). Kills usability.
https://bugs.kde.org/show_bug.cgi?id=442187 --- Comment #8 from Alexander Reinholdt --- (In reply to flan_suse from comment #6) I did some testing with other applications that implement a status icon via KStatusNotifierIcon and also have submenus. Yakuake, for example, shows the same glitch you reported. So it seems that the problem lies within the systemtray itself. However, the trash icon seems to behave correctly. I will have a look on how to fix or work around the problem. Maybe the code of the trash icon helps. -- You are receiving this mail because: You are watching all bug changes.
[Smb4k] [Bug 442187] Smb4K 3.1.0 still has frustrating, old usability glitches and bugs (explained in description). Kills usability.
https://bugs.kde.org/show_bug.cgi?id=442187 Alexander Reinholdt changed: What|Removed |Added Resolution|FIXED |--- Status|RESOLVED|REPORTED -- You are receiving this mail because: You are watching all bug changes.
[Smb4k] [Bug 442187] Smb4K 3.1.0 still has frustrating, old usability glitches and bugs (explained in description). Kills usability.
https://bugs.kde.org/show_bug.cgi?id=442187 Alexander Reinholdt changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED Latest Commit||https://invent.kde.org/netw ||ork/smb4k/commit/2a98352625 ||ecdde057e19cd6e4f8dc63a9879 ||d04 --- Comment #7 from Alexander Reinholdt --- Git commit 2a98352625ecdde057e19cd6e4f8dc63a9879d04 by Alexander Reinholdt. Committed on 22/09/2021 at 07:14. Pushed by areinholdt into branch 'master'. Implement a non-blocking sleep to wait for the shell process to finish. M +12 -2helpers/smb4kmounthelper.cpp https://invent.kde.org/network/smb4k/commit/2a98352625ecdde057e19cd6e4f8dc63a9879d04 -- You are receiving this mail because: You are watching all bug changes.
[Smb4k] [Bug 442187] Smb4K 3.1.0 still has frustrating, old usability glitches and bugs (explained in description). Kills usability.
https://bugs.kde.org/show_bug.cgi?id=442187 --- Comment #3 from Alexander Reinholdt --- Thank you for providing the video. Does the freeze only happen after mounting (unmounting) some shares? Or also when no shares at all have been mounted (or unmounted) before? -- You are receiving this mail because: You are watching all bug changes.
[frameworks-solid] [Bug 442459] New: Network devices (Samba shares) loose their type when being removed
https://bugs.kde.org/show_bug.cgi?id=442459
Bug ID: 442459
Summary: Network devices (Samba shares) loose their type when
being removed
Product: frameworks-solid
Version: 5.85.0
Platform: Manjaro
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: general
Assignee: lu...@kde.org
Reporter: alexander.reinho...@kdemail.net
CC: kdelibs-b...@kde.org
Target Milestone: ---
SUMMARY
When Samba shares are unmounted (removed), Solid::Device::isDeviceInterface()
won't return Solid::DeviceInterface::NetworkShare as type.
STEPS TO REPRODUCE
1. Connect a slot to the signal deviceAdded() and deviceRemoved() of
Solid::DeviceNotifier::instance(), respectively.
2. Implement the following code in both slots:
Solid::Device device(udi);
if (device.isDeviceInterface(Solid::DeviceInterface::NetworkShare)) {
qDebug() << "Success";
} else {
qDebug() << "Failure";
}
3. Run the application.
OBSERVED RESULT
When mounting a Samba share, the output will be "Success". When unmounting that
share afterwards, the output will always be "Failure".
EXPECTED RESULT
On both occasions "Success" is returned.
SOFTWARE/OS VERSIONS
Operating System: Manjaro Linux
KDE Plasma Version: 5.22.5
KDE Frameworks Version: 5.85.0
Qt Version: 5.15.2
Kernel Version: 5.13.13-1-MANJARO (64-bit)
Graphics Platform: X11
ADDITIONAL INFORMATION
--
You are receiving this mail because:
You are watching all bug changes.
[frameworks-solid] [Bug 442258] Solid::NetworkShare does not know SMB3 filesystem
https://bugs.kde.org/show_bug.cgi?id=442258 --- Comment #1 from Alexander Reinholdt --- In addition: The output will be "success", when you mount the share with one of the defined filesystems (NFS and CIFS). -- You are receiving this mail because: You are watching all bug changes.
[frameworks-solid] [Bug 442258] New: Solid::NetworkShare does not know SMB3 filesystem
https://bugs.kde.org/show_bug.cgi?id=442258
Bug ID: 442258
Summary: Solid::NetworkShare does not know SMB3 filesystem
Product: frameworks-solid
Version: 5.85.0
Platform: Manjaro
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: general
Assignee: lu...@kde.org
Reporter: alexander.reinho...@kdemail.net
CC: kdelibs-b...@kde.org
Target Milestone: ---
SUMMARY
Solid::NetworkShare does not know the network filesystem SMB3 and, thus, mounts
with that filesystem are not detected on the system.
STEPS TO REPRODUCE
1. Connect a slot to the deviceAdded() signal of
Solid::DeviceNotifier::instance().
2. Add the following if statement to the slot:
if (device.isDeviceInterface(Solid::DeviceInterface::NetworkShare)) {
qDebug() << "success";
} else {
qDebug() << "failure";
}
3. Mount a Samba share with the SMB3 filesystem:
$ mount.smb3 //server/share /mount/point
OBSERVED RESULT
The output will always be "failure", even when a share with an SMB3 filesystem
is mounted.
EXPECTED RESULT
The output is "success" when a share with SMB3 filesystem is mounted and
"failure" otherwise.
SOFTWARE/OS VERSIONS
Operating System: Manjaro Linux
KDE Plasma Version: 5.22.5
KDE Frameworks Version: 5.85.0
Qt Version: 5.15.2
Kernel Version: 5.13.13-1-MANJARO (64-bit)
Graphics Platform: X11
ADDITIONAL INFORMATION
--
You are receiving this mail because:
You are watching all bug changes.
[Smb4k] [Bug 442187] Smb4K 3.1.0 still has frustrating, old usability glitches and bugs (explained in description). Kills usability.
https://bugs.kde.org/show_bug.cgi?id=442187 --- Comment #1 from Alexander Reinholdt --- Thank you for reporting this. I will try to reproduce and fix the listed issues as soon as possible. -- You are receiving this mail because: You are watching all bug changes.
[Smb4k] [Bug 417754] Starts with error "The URL does not exist"
https://bugs.kde.org/show_bug.cgi?id=417754 --- Comment #19 from Alexander Reinholdt --- (In reply to postix from comment #17) > It has moved: > > https://docs.kde.org/stable5/en/smb4k/smb4k/special_remarks.html > > however I don't see #special_remarks_problems_browsing_samba_47 there. The handbook was updated to version 3.1.0 recently. To view the handbook for your installed version of Smb4K, plase press the F1 key. -- You are receiving this mail because: You are watching all bug changes.
[Smb4k] [Bug 417754] Starts with error "The URL does not exist"
https://bugs.kde.org/show_bug.cgi?id=417754 --- Comment #18 from Alexander Reinholdt --- (In reply to Roger Wright from comment #15) > I have this too now. Any progress? My symptoms are as above. Which version of Smb4K are you using? With Smb4K 3.1.0 or 3.0.7 this should not happen no more. -- You are receiving this mail because: You are watching all bug changes.
[Smb4k] [Bug 435497] Smb4k does not mount all drives
https://bugs.kde.org/show_bug.cgi?id=435497 Alexander Reinholdt changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |WORKSFORME --- Comment #1 from Alexander Reinholdt --- Thank you for reporting this issue. However, the version you are using is quite outdated and the problem should already be fixed. Thus, I close this bug report. If the problem should still occur with the latest version, please feel free to reopen this report. -- You are receiving this mail because: You are watching all bug changes.
[Smb4k] [Bug 434543] SMB4K not mounting share on NAS
https://bugs.kde.org/show_bug.cgi?id=434543 --- Comment #1 from Alexander Reinholdt --- Thank you for reporting this issue. Can you please give me some additional information? - Which version of Smb4K are you using? - Are you saving the credentials to the wallet? - Which operating system is running on the NAS? -- You are receiving this mail because: You are watching all bug changes.
[Smb4k] [Bug 430627] Remounting of previously used shares on program start
https://bugs.kde.org/show_bug.cgi?id=430627 --- Comment #3 from Alexander Reinholdt --- I tried to reproduce your problem with the latest development version, but I was not successful. Could you please try Smb4K 3.0.80 and check, if your problem is still there? -- You are receiving this mail because: You are watching all bug changes.
[Smb4k] [Bug 417754] Starts with error "The URL does not exist"
https://bugs.kde.org/show_bug.cgi?id=417754 Alexander Reinholdt changed: What|Removed |Added See Also|https://bugs.kde.org/show_b | |ug.cgi?id=429528| -- You are receiving this mail because: You are watching all bug changes.
[Smb4k] [Bug 429528] SCAN NETWORK **URL does not exist on Manjaro
https://bugs.kde.org/show_bug.cgi?id=429528 Alexander Reinholdt changed: What|Removed |Added See Also|https://bugs.kde.org/show_b | |ug.cgi?id=417754| -- You are receiving this mail because: You are watching all bug changes.
[Smb4k] [Bug 417754] Starts with error "The URL does not exist"
https://bugs.kde.org/show_bug.cgi?id=417754 Alexander Reinholdt changed: What|Removed |Added CC||j...@groundscouts.com --- Comment #14 from Alexander Reinholdt --- *** Bug 429528 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[Smb4k] [Bug 429528] SCAN NETWORK **URL does not exist on Manjaro
https://bugs.kde.org/show_bug.cgi?id=429528 Alexander Reinholdt changed: What|Removed |Added Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED --- Comment #1 from Alexander Reinholdt --- *** This bug has been marked as a duplicate of bug 417754 *** -- You are receiving this mail because: You are watching all bug changes.
[Smb4k] [Bug 417754] Starts with error "The URL does not exist"
https://bugs.kde.org/show_bug.cgi?id=417754 Alexander Reinholdt changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=429528 -- You are receiving this mail because: You are watching all bug changes.
[Smb4k] [Bug 429528] SCAN NETWORK **URL does not exist on Manjaro
https://bugs.kde.org/show_bug.cgi?id=429528 Alexander Reinholdt changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=417754 -- You are receiving this mail because: You are watching all bug changes.
[Smb4k] [Bug 417754] Starts with error "The URL does not exist"
https://bugs.kde.org/show_bug.cgi?id=417754 Alexander Reinholdt changed: What|Removed |Added See Also|https://bugs.kde.org/show_b | |ug.cgi?id=429528| -- You are receiving this mail because: You are watching all bug changes.
