https://bugs.kde.org/show_bug.cgi?id=442187

            Bug ID: 442187
           Summary: Smb4K 3.1.0 still has frustrating, old usability
                    glitches and bugs (explained in description). Kills
                    usability.
           Product: Smb4k
           Version: unspecified
          Platform: Manjaro
                OS: Linux
            Status: REPORTED
          Severity: normal
          Priority: NOR
         Component: general
          Assignee: alexander.reinho...@kdemail.net
          Reporter: windows2li...@zoho.com
  Target Milestone: ---

SUMMARY:

Even before using version 3.1.0, SmbK4 has, and continues to suffer from the
same GUI glitches that are not simply "aesthetic" but also break mounts and
basic usage.

These *continue* to be an issue on multiple computers, Intel and Nvidia GPU,
latest stable KDE branch.

I believe the reason they were never submitted as "bugs" is because it's hard
to really provide a "crash" or debug logs. It's all in the behavior of Smb4K.
There's no distinctive pattern. (I'm hoping the developers might be able to
clue in on something.)

These glitches involves "phantom" mounts that don't show up in Smb4K's tray
menu nor main window, nor menu bars; yet they exist in the mtab (proven by
invoking "mount" in a terminal) and in Dolphin's shortcuts.

These glitches involves "Unmount All" and "Unmount" being greyed out in the
tray context menu, yet working normally from the main window.

These glitches affect bookmarks (not truthfully displaying which ones are
available.)


---


SYSTEM INFORMATION:

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.0-0-MANJARO (64-bit)
Graphics Platform: X11
Processors: 8 × 11th Gen Intel® Core™ i7-1165G7 @ 2.80GHz
Memory: 15.4 GiB of RAM
Graphics Processor: Mesa Intel® Xe Graphics
Smb4K: 3.1.0

(The same exact glitches and breakages also happen on a different computer
running Nvidia graphics.)


---


I can demonstrate with videos and screenshots if needed.

I can explain how to look out for these glitches yourself.

I can provide logs if applicable.

However, I think if a developer experiences these themselves, it will make more
sense than simply trying to explain it.


---


DESCRIPTION:

* Occasionally (and I'd argue "too often" for an application that deals with
SMB network shares), currently mounted shares will show up in Dolphin and the
mtab, yet are NOT displayed in Smb4K's main window nor tray context menu. There
is NO MEANS to unmount the share(s) by using Smb4K. You either have to
completely quit the application or use admin privileges to manually unmount
them in a terminal.

* Occasionally, the tray icon context menu does NOT reflect what the main
window displays. For example, if I have shares currently mounted (which ARE
visible in the main window), they do NOT show up in the tray icon menu. If I
wish to browser them or unmount them, I must do it from the main window, since
the current mounts in the tray icon are either greyed out or missing!

* Almost always it's glitchy to use the tray icon context menu, since hovering
over bookmarks doesn't reveal anything... until I move my mouse cursor up and
down to get Smb4K to go "Oh! Right... your bookmarks... okay here they are!"
Why the delay and ritual? Why not just immediately present me with the list of
my bookmarks? It's as if moving up and down the context menu forces the loading
of entries in a sub-menu.

* The above glitches affect overall usage and stability of using your desktop,
since they deal with mounts. Things are greyed out or missing when they
shouldn't be. Nothing obviously indicates whether or not a share is currently
mounted. The only way to know for sure is to run "mount" in a terminal. I often
have to fully quit and re-launch Smb4K to "shake off" some glitches when they
occur.


--- 


It's been like this for a while, well before 3.1.0, so my hunch tells me it's
to do with base code that the updates were built on top of? I waited until
after 3.1.0 was released, due to reading developer notes how 3.1.0 would
introduce some big changes. I figured it was being re-coded from the ground up
and naturally these bugs would not be an issue anymore.

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to