https://bugs.kde.org/show_bug.cgi?id=500855
--- Comment #1 from Alexander Reinholdt ---
Thank you for reporting this issue. I will try to reproduce it.
Obviously, the crash happens in the Smb4KSynchronizer class on exit. Did you
synchronize data prior to closing the application?
--
You are
https://bugs.kde.org/show_bug.cgi?id=495534
Alexander Reinholdt changed:
What|Removed |Added
Resolution|--- |WORKSFORME
Status|REOPENED
https://bugs.kde.org/show_bug.cgi?id=495534
Alexander Reinholdt changed:
What|Removed |Added
Status|RESOLVED|REOPENED
Ever confirmed|0
https://bugs.kde.org/show_bug.cgi?id=495534
--- Comment #4 from Alexander Reinholdt ---
Thank you for the additional information. I will try to reproduce the problem
(with the latest Qt5 version of Smb4K) and fix it, if I found it.
--
You are receiving this mail because:
You are watching all
https://bugs.kde.org/show_bug.cgi?id=495534
Alexander Reinholdt changed:
What|Removed |Added
Status|REPORTED|RESOLVED
Resolution
https://bugs.kde.org/show_bug.cgi?id=484712
--- Comment #6 from Alexander Reinholdt ---
(In reply to Brett Hagen from comment #5)
> This has happened to me as well. What traces could I include to help with
> this?
Could you please provide the crash report that is generated when Smb4K c
https://bugs.kde.org/show_bug.cgi?id=493610
--- Comment #5 from Alexander Reinholdt ---
(In reply to Steve from comment #4)
> Disregard - reading a similar bug (492437) I realized that I was missing two
> packages after a fresh install:
>
> * plasma5-integration
> * kwayland5
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 watc
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
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 separat
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 stor
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
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
> Q
https://bugs.kde.org/show_bug.cgi?id=486474
Alexander Reinholdt changed:
What|Removed |Added
Resolution|--- |FIXED
Latest Commit
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
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
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
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.
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.
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&action=edit
Wayland debug output
This is the requested debug output. Smb4K started docked to the system tray,
i.e. t
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
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
https://bugs.kde.org/show_bug.cgi?id=472467
Alexander Reinholdt changed:
What|Removed |Added
Resolution|--- |FIXED
Status|REPORTED
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:
Yo
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.
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
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 infor
https://bugs.kde.org/show_bug.cgi?id=465392
Alexander Reinholdt changed:
What|Removed |Added
Status|REPORTED|NEEDSINFO
Resolution
https://bugs.kde.org/show_bug.cgi?id=462988
Alexander Reinholdt changed:
What|Removed |Added
Resolution|--- |FIXED
Status|REPORTED
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
https://bugs.kde.org/show_bug.cgi?id=463637
Alexander Reinholdt changed:
What|Removed |Added
Status|REPORTED|RESOLVED
Resolution
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
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
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
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&action=edit
Latest version with domain handling fix
This packages contains a fixed version of the code for mounting. Ple
https://bugs.kde.org/show_bug.cgi?id=462798
Alexander Reinholdt changed:
What|Removed |Added
Status|REPORTED|RESOLVED
Resolution
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
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.
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
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
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
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
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
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&action=edit
dmesg drm debug output
Here is the requested output.
--
You are receiving this mail because:
You are watch
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&action=edit
journalctl output with debug
Here is the output. I ran the command without sudo. If that is needed as well,
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&action=edit
New journalctl output
journalctl output (after running kwriteconfig5 command as normal user and with
sudo)
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 --grou
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&action=edit
dmesg output after running systemsettings
Collected after opening systemsettings where I was told that one
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&action=edit
dmesg output
Collected directly after reboot and login into the wayland session.
--
You are receiving th
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&action=edit
journalctl output
Collected directly after reboot and login into the wayland session.
--
You are receivi
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&action=edit
drm_info output
Collected directly after reboot and login into the wayland session.
--
You are receiving th
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
https://bugs.kde.org/show_bug.cgi?id=459085
Alexander Reinholdt changed:
What|Removed |Added
Status|NEEDSINFO |REPORTED
Resolution
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.
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
https://bugs.kde.org/show_bug.cgi?id=459085
Alexander Reinholdt changed:
What|Removed |Added
CC||alexander.reinholdt@kdemail
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:
https://bugs.kde.org/show_bug.cgi?id=442258
Alexander Reinholdt changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Version Fixed In
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
https://bugs.kde.org/show_bug.cgi?id=455772
Alexander Reinholdt changed:
What|Removed |Added
Status|REPORTED|RESOLVED
Resolution
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
https://bugs.kde.org/show_bug.cgi?id=454687
Alexander Reinholdt changed:
What|Removed |Added
Latest Commit||https://invent.kde.org/netw
https://bugs.kde.org/show_bug.cgi?id=417754
Alexander Reinholdt changed:
What|Removed |Added
Resolution|--- |FIXED
Status|REOPENED
https://bugs.kde.org/show_bug.cgi?id=452293
Alexander Reinholdt changed:
What|Removed |Added
Status|REPORTED|RESOLVED
Resolution
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
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 ne
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: P
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
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 overcom
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 beh
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 m
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
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&quo
https://bugs.kde.org/show_bug.cgi?id=442187
Alexander Reinholdt changed:
What|Removed |Added
Status|REPORTED|CONFIRMED
Ever confirmed|0
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.
>
>
https://bugs.kde.org/show_bug.cgi?id=397453
Alexander Reinholdt changed:
What|Removed |Added
Resolution|--- |FIXED
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=434543
Alexander Reinholdt changed:
What|Removed |Added
Resolution|--- |WORKSFORME
Status|REPORTED
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.
https://bugs.kde.org/show_bug.cgi?id=430627
Alexander Reinholdt changed:
What|Removed |Added
Resolution|--- |FIXED
Status|REPORTED
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
https://bugs.kde.org/show_bug.cgi?id=442187
Alexander Reinholdt changed:
What|Removed |Added
Depends on||442877
Referenced Bugs:
https
https://bugs.kde.org/show_bug.cgi?id=442877
Alexander Reinholdt changed:
What|Removed |Added
Blocks||442187
Referenced Bugs:
https
https://bugs.kde.org/show_bug.cgi?id=442877
Alexander Reinholdt changed:
What|Removed |Added
CC||windows2li...@zoho.com
--
You are
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: REPORTE
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 agai
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 m
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
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
https://bugs.kde.org/show_bug.cgi?id=442187
Alexander Reinholdt changed:
What|Removed |Added
Resolution|FIXED |---
Status|RESOLVED
https://bugs.kde.org/show_bug.cgi?id=442187
Alexander Reinholdt changed:
What|Removed |Added
Resolution|--- |FIXED
Status|REPORTED
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
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
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.
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
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.
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_
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 m
https://bugs.kde.org/show_bug.cgi?id=435497
Alexander Reinholdt changed:
What|Removed |Added
Status|REPORTED|RESOLVED
Resolution
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
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
1 - 100 of 202 matches
Mail list logo
