[systemsettings] [Bug 401604] Allow to cofigure `x-scheme-handler` MymeTypes
https://bugs.kde.org/show_bug.cgi?id=401604 Anton Latuha changed: What|Removed |Added Component|kcm_componentchooser|general Assignee|unassigned-b...@kde.org |plasma-b...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 401604] New: Allow to cofigure `x-scheme-handler` MymeTypes
https://bugs.kde.org/show_bug.cgi?id=401604 Bug ID: 401604 Summary: Allow to cofigure `x-scheme-handler` MymeTypes Product: systemsettings Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: kcm_componentchooser Assignee: unassigned-b...@kde.org Reporter: piroxil...@gmail.com Target Milestone: --- SUMMARY Allow to manage MimeTypes `x-scheme-handler/x`. To be able to pass to applications a custom protocols (URLs). For example in `x-scheme-handler/x`, `x` can be: - magnet (for torrent magnet links), - spotify (spotify), - tg (telegram), - rtsp (real-time streaming protocol), - org-protocol (protocol to path through information to the Emacs Org). STEPS TO REPRODUCE 1. Open Settings -> Application -> File Associations OBSERVED RESULT There is no `x-scheme-handler` section nor a possibility to create a handler. EXPECTED RESULT There to be `x-scheme-handler` section which shows the currently known protocols and allows to declare new ones/set default applications for them. SOFTWARE/OS VERSIONS Linux/KDE Plasma: current NixOS 19.03pre KDE Plasma Version: 5.14.3 KDE Frameworks Version: 5.51.0 Qt Version: 5.11.1 ADDITIONAL INFORMATION Here I describe the current way to register `x-scheme-handler`. I have not found the solid source of information to this process. To set the connection between URL and application - user must make a pretty wide research, get the knowledge about desktop files, MimeTypes, how `x-scheme-handler` protocols work and get info on what to do. Manually create the right `~/.local/share/applications/handler.desktop` entry. Register the desktop entry with `kbuildsycoca5`. Register the desktop entry with right xdg command, aka `xdg-mime default org-protocol.desktop x-scheme-handler/org-protocol` Only because found the next thread - managed to register `x-scheme-handler`, in the thread, you can see what it takes to discover the path I described: https://lists.fedoraproject.org/archives/list/k...@lists.fedoraproject.org/thread/ZERZXDKGTJXBAEVMBTOAEI32EQ4VOK4L/ Thank you for everything. Good day for you. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 379126] digiKam on Wayland Plasma crashes at start
https://bugs.kde.org/show_bug.cgi?id=379126 --- Comment #6 from Anton Latuha --- I've closed bug. Ok. Next time something major like this - compilation with debug symbols. Thank you. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 379126] digiKam on Wayland Plasma crashes at start
https://bugs.kde.org/show_bug.cgi?id=379126 Anton Latuha changed: What|Removed |Added Resolution|--- |FIXED Status|UNCONFIRMED |RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 379126] digiKam on Wayland Plasma crashes at start
https://bugs.kde.org/show_bug.cgi?id=379126 --- Comment #5 from Anton Latuha --- Thank you, that waited some time. Yes, it works now on the same Arch system. Close this. -- You are receiving this mail because: You are watching all bug changes.
[kdialog] [Bug 363185] file selection dialog very slow when samba shares are not present
https://bugs.kde.org/show_bug.cgi?id=363185 --- Comment #5 from Anton Latuha --- People please vote for this bug. -- You are receiving this mail because: You are watching all bug changes.
[kdialog] [Bug 363185] file selection dialog very slow when samba shares are not present
https://bugs.kde.org/show_bug.cgi?id=363185 Anton Latuha changed: What|Removed |Added CC||piroxil...@gmail.com --- Comment #4 from Anton Latuha --- Somebody, please take notice. My additional information. In Firefox it loads eventually, after ~30 seconds, in Chromium seems completely not. And I do have disconnected NFS now. Dolphin also freezes completely, when I click that NFS folder. It is also reported for Kdialog in: Bug 323650 Bug 340584 Bug 354694 Bug 340584 And in Kfile Bug 320560 And in Dolphin Bug 357509 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 379125] Opening with... in file manager results in for every image digiKam instance spawns
https://bugs.kde.org/show_bug.cgi?id=379125 --- Comment #4 from Anton Latuha --- Open with -> Other... Choose or type, 'digiKam'. Yes, there is no option in the package. Package done right. As in Windows, as in Linux Desktops - file associations in parts is a mess. Like VLC and Firefox, LibreOffice, Inkscape - spam a file associations no one uses in the right state of mind (like open PDF in Inkscape), but sometime they can be used. And it does not mean user cannot chose custom action. All DE has "Open With, choose application", that is why that is legitimate feature to implement. Ok, I have no choice but to agree and put it to rest as is. P.S. ## Question If I get to implement features, such as that to KDE. Does it going to be accepted upstream in KDE community? I love KDE, but I have a list of features lacking, and tried couple of times to get in. But QML + KDE + QT5 + C++ KDE writing standards + C++ itself, was to this time too hard and too layered for me to penetrate it through successfully and to write a good code. If I get to KDE, does my half-quality features get accepted/discussed one and I get in the process. Or probably features not going to be accepted because developers have view and KDE philosophy, way? Thank you. Regards, Anton Latukha -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 379125] Opening with... in file manager results in for every image digiKam instance spawns
https://bugs.kde.org/show_bug.cgi?id=379125 Anton Latuha changed: What|Removed |Added Status|RESOLVED|UNCONFIRMED Resolution|DOWNSTREAM |--- --- Comment #2 from Anton Latuha --- I am not stupid. You probably have not completely understood my description. ## I was looking how to import images. Not from a USB drive. Not from Camera. But, simple. Images from a folder, but so they on import going to be integrated in album structure (date structure). I am not adept of digiKam. And I could not find that simple action for tens of minutes of decisive looking. Trying different variants and searching manuals. Looks like I was doing it somehow before (or maybe I wasn't importing pictures from time I created and album). But I can't find how to do it. And I know, this is what application is for. Application need to have some action on that, I probably can't find it. I have a plethora of image viewers. And image editors. Package is configured right. I thought to fill question, bug-report (suggesting menu/action results to be more understandable). But that seems too stupid to ask, before I find a way or try and fail every path by myself. ## I tried to open images in digiKam deliberately. To see what action is going to happen. Because maybe it going to ask me what to do with them, or import them. And this happens. ## Hanging a system with a couple of hundreds of instances can be considered a usability problem. I have that problem in different applications from time to time, as you probably had also. When working with a lot of files, and hit enter not in that window, by mistake, or choosing to open them in application, inspecting/expecting application to treat them. Action probably needs to be covered with some action processing or a test-case. Or do a popup and point to launch showFoto instead. Or at least hang is a report. It is from my standpoint. Most good applications have that. showFoto, GIMP, Inkscape, Eye of GNOME. I understand, from programmers perspective, digiKam not connected to open photo action. And there is a default stud. But users expect otherwise. ## User thinks: digiKam manages photos, so it have some sort of action with them. If I open photos with it, probably action going to be the most logical one, the most useful one (and it probably is what I think). The way like I experienced with applications before. And it is hard to look at this user logic as wrong. ## Sorry, I open it ones. Because I don't know, do you read massages on resolved, downstream'ed ones. Regards, Anton Latukha. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 379126] digiKam on Wayland Plasma crashes at start
https://bugs.kde.org/show_bug.cgi?id=379126 --- Comment #1 from Anton Latuha --- Created attachment 105158 --> https://bugs.kde.org/attachment.cgi?id=105158&action=edit system log from start of application to finish System log during digiKam start and crash. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 379126] New: digiKam on Wayland Plasma crashes at start
https://bugs.kde.org/show_bug.cgi?id=379126 Bug ID: 379126 Summary: digiKam on Wayland Plasma crashes at start Product: digikam Version: 5.5.0 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: digikam-de...@kde.org Reporter: piroxil...@gmail.com Target Milestone: --- Application: digikam (5.5.0) Qt Version: 5.8.0 Frameworks Version: 5.33.0 Operating System: Linux 4.10.10-1-ARCH x86_64 Distribution (Platform): Archlinux Packages -- Information about the crash: - What I was doing when the application crashed: Starting digiKam application. (From Application Launcher.) - Custom settings of the application: Plasma on Wayland - Additional information: digikam (5.5.0) Kwin_wayland (kwin 5.9.4) Plasma Desktop (5.9.4) Arch Linux (Linux Archer 4.10.10-1-ARCH #1 SMP PREEMPT Wed Apr 12 18:50:28 CEST 2017 x86_64 GNU/Linux) The crash can be reproduced every time. -- Backtrace: Application: digiKam (digikam), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7f034bcc8680 (LWP 23631))] Thread 84 (Thread 0x7f02171d6700 (LWP 23768)): #0 0x7f0341dd8756 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f0347e897cb in QWaitCondition::wait(QReadWriteLock*, unsigned long) () at /usr/lib/libQt5Core.so.5 #2 0x7f03435e4b7b in QtAV::BlockingQueue::take() () at /usr/lib/libQtAV.so.1 #3 0x7f034364e5b8 in QtAV::ExtractThread::run() () at /usr/lib/libQtAV.so.1 #4 0x7f0347e886d8 in () at /usr/lib/libQt5Core.so.5 #5 0x7f0341dd22e7 in start_thread () at /usr/lib/libpthread.so.0 #6 0x7f034718454f in clone () at /usr/lib/libc.so.6 Thread 83 (Thread 0x7f02179d7700 (LWP 23767)): #0 0x7f0341dd8756 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f0347e897cb in QWaitCondition::wait(QReadWriteLock*, unsigned long) () at /usr/lib/libQt5Core.so.5 #2 0x7f03435e4b7b in QtAV::BlockingQueue::take() () at /usr/lib/libQtAV.so.1 #3 0x7f034364e5b8 in QtAV::ExtractThread::run() () at /usr/lib/libQtAV.so.1 #4 0x7f0347e886d8 in () at /usr/lib/libQt5Core.so.5 #5 0x7f0341dd22e7 in start_thread () at /usr/lib/libpthread.so.0 #6 0x7f034718454f in clone () at /usr/lib/libc.so.6 Thread 82 (Thread 0x7f02181d8700 (LWP 23766)): #0 0x7f0341dd8756 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f0347e897cb in QWaitCondition::wait(QReadWriteLock*, unsigned long) () at /usr/lib/libQt5Core.so.5 #2 0x7f03435e4b7b in QtAV::BlockingQueue::take() () at /usr/lib/libQtAV.so.1 #3 0x7f034364e5b8 in QtAV::ExtractThread::run() () at /usr/lib/libQtAV.so.1 #4 0x7f0347e886d8 in () at /usr/lib/libQt5Core.so.5 #5 0x7f0341dd22e7 in start_thread () at /usr/lib/libpthread.so.0 #6 0x7f034718454f in clone () at /usr/lib/libc.so.6 Thread 81 (Thread 0x7f02189d9700 (LWP 23765)): #0 0x7f0341dd8756 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f0347e897cb in QWaitCondition::wait(QReadWriteLock*, unsigned long) () at /usr/lib/libQt5Core.so.5 #2 0x7f03435e4b7b in QtAV::BlockingQueue::take() () at /usr/lib/libQtAV.so.1 #3 0x7f034364e5b8 in QtAV::ExtractThread::run() () at /usr/lib/libQtAV.so.1 #4 0x7f0347e886d8 in () at /usr/lib/libQt5Core.so.5 #5 0x7f0341dd22e7 in start_thread () at /usr/lib/libpthread.so.0 #6 0x7f034718454f in clone () at /usr/lib/libc.so.6 Thread 80 (Thread 0x7f02191da700 (LWP 23764)): #0 0x7f0341dd8756 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f0347e897cb in QWaitCondition::wait(QReadWriteLock*, unsigned long) () at /usr/lib/libQt5Core.so.5 #2 0x7f03435e4b7b in QtAV::BlockingQueue::take() () at /usr/lib/libQtAV.so.1 #3 0x7f034364e5b8 in QtAV::ExtractThread::run() () at /usr/lib/libQtAV.so.1 #4 0x7f0347e886d8 in () at /usr/lib/libQt5Core.so.5 #5 0x7f0341dd22e7 in start_thread () at /usr/lib/libpthread.so.0 #6 0x7f034718454f in clone () at /usr/lib/libc.so.6 Thread 79 (Thread 0x7f02199db700 (LWP 23763)): #0 0x7f0341dd8756 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f0347e897cb in QWaitCondition::wait(QReadWriteLock*, unsigned long) () at /usr/lib/libQt5Core.so.5 #2 0x7f03435e4b7b in QtAV::BlockingQueue::take() () at /usr/lib/libQtAV.so.1 #3 0x7f034364e5b8 in QtAV::ExtractThread::run() () at /usr/lib/libQtAV.so.1 #4 0x7f0347e886d8 in () at /usr/lib/libQt5Core.so.5 #5 0x7f0341dd22e7 in start_thread () at /usr/lib/libpthread.so.0 #6 0x7f034718454f in clone () at /usr/lib/libc.so.6 Thread 78 (Thread 0x7f021a1dc700 (LWP 23762)): #0 0x7f0341dd8756 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1
[digikam] [Bug 379125] New: Opening with... in file manager results in for every image digiKam instance spawns
https://bugs.kde.org/show_bug.cgi?id=379125 Bug ID: 379125 Summary: Opening with... in file manager results in for every image digiKam instance spawns Product: digikam Version: 5.5.0 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Workflow Assignee: digikam-de...@kde.org Reporter: piroxil...@gmail.com Target Milestone: --- Thank you, digiKam guys. Steps to reproduce: 1. Use any file manager. (I use Dolphin) 2. In file manager open a folder with number of images. 3. Select a number of images. 4. Open Right click menu -> Open with... and open them with digiKam. 5. digiKam is going to load a new instance for every image. (I had 100 images selected, and my desktop machine gone to almost unresponsive state. So I needed to somehow execute `killall digiKam`) Additional information: digikam (5.5.0) Kwin_wayland (kwin 5.9.4) Plasma Desktop (5.9.4) Arch Linux (Linux Archer 4.10.10-1-ARCH #1 SMP PREEMPT Wed Apr 12 18:50:28 CEST 2017 x86_64 GNU/Linux) P.S. 1. Severity Effect of bug can be equal to "Crash" severity, because it hangs all system almost completely. I waited for 20 minutes for desktop to sort-out situation. But in the end I needed take another 5 minutes to login to Linux console and kill all digiKam instances. 2. What I wanted to do Basically I was figuring-out how to import images to my album structure. And tried this variant. As a user I expected: Select one image - open import dialog for that image. Or ask me for action. Select bunch of images - open import dialog for that images. Or ask me for action. If images are in albums already - select them there. Or ask me for a custom action. Asking what I want to do. If some images already present - have option to ignore already imported images, report how much of them ignored, how much left to import and view of them (with a button to view what images was ignored, and where they are already in digiKam). Thank you, I appreciate digiKam. Regards, Anton Latukha. -- You are receiving this mail because: You are watching all bug changes.
