[konsole] [Bug 185422] Konsole TAB option "copy input": setting not being saved with desktop
https://bugs.kde.org/show_bug.cgi?id=185422 Manfred Knick changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME --- Comment #6 from Manfred Knick --- Hi, Kurt! As far as I am concerned, I really would not mind to have this closed - preferably as "OBSOLETE". Thanks! Kind regards Manfred Postscriptum - OT: Nowadays, I enjoy the effectiveness of extreme simplicity: dwl <- wlroots <- wayland; plus bemenu and foot - that's all to support any ( KDE ) application I might need: [ https://codeberg.org/dwl/dwl ] , perfectly providing a 2x2 Monitor workstation (Gentoo) setup as well as a "Road Warrior" Notebook. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 421922] kde-apps/akonadi-{19.08.3,19.12.2} with dev-db/mysql-8.0.19{-r1} - error: 'Can't connect to local MySQL server through socket '/run/user/1000/akonadi/mysql.socket' (2)'
https://bugs.kde.org/show_bug.cgi?id=421922 --- Comment #10 from Manfred Knick --- Does Akonadi 20.12.0 contain any progress on this issue? -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 379914] [Multiple separate X11 screens] [Awesome WM] kde-apps/konsole-17.04.1 :: "close" :: app re-locates to another (hidden) tab
https://bugs.kde.org/show_bug.cgi?id=379914 --- Comment #6 from Manfred Knick --- Burying my father took precedence. - - - - - Multiple separate X11 screens setup (Zaphod, no Xinerama), although being a perfect liable X11 option, has been ignored and explicitly labeled as "irrelevant" by the two main KDE developers and others. Thus I finally gave up on KDE and dbus broken by design. https://bugs.kde.org/buglist.cgi?bug_status=UNCONFIRMED&bug_status=CONFIRMED&bug_status=ASSIGNED&bug_status=REOPENED&bug_status=RESOLVED&bug_status=NEEDSINFO&bug_status=VERIFIED&bug_status=CLOSED&email2=Manfred.Knick%40T-Online.de&emailassigned_to2=1&emailcc2=1&emailreporter2=1&emailtype2=substring&list_id=1818181&order=Importance&query_format=advanced is dating back to 2015 and before. Reported errors have been verified even on ctwm (!) with 4 screens. After all these years of ignorance, NEEDSINFO sounds quite bitter in my ears. The named setup is not available any more. RESOLVED as WONTFIX would be much more honest, at least. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 421922] kde-apps/akonadi-{19.08.3,19.12.2} with dev-db/mysql-8.0.19{-r1} - error: 'Can't connect to local MySQL server through socket '/run/user/1000/akonadi/mysql.socket' (2)'
https://bugs.kde.org/show_bug.cgi?id=421922 Manfred Knick changed: What|Removed |Added CC||manfred.kn...@t-online.de --- Comment #9 from Manfred Knick --- After recent *stable* updates, problem still persists: kde-apps/akonadi-{19.08.3,19.12.2,20.08.3} with dev-db/mysql-{8.0.19{-r1},8.0.21-r1} [ https://bugs.gentoo.org/709812#c30 ] -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 278935] Please make XMP Sidecar filename configurable [patch]
https://bugs.kde.org/show_bug.cgi?id=278935 --- Comment #16 from knick --- You're saying patching the source code and compiling the whole app with all it's dependencies relative easy? No miracle why linux doesn't make it's way to desktop users. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 278935] Please make XMP Sidecar filename configurable [patch]
https://bugs.kde.org/show_bug.cgi?id=278935 knick changed: What|Removed |Added CC||kn...@byom.de --- Comment #14 from knick --- As windows user for ages I wanted to give dk another try and found that it would just read meta data from my tiffs but none from my raw files. What a mess! Browsing the web I found a few discussions on this problem and finally arrived here. I always felt dropping the extension and adding ".ext" to a file name was a bad decision by adobe. I sometimes stumbled in this trap too with my ".cr2" and ".nef" files using the same base name. But it is widely accepted since many years and I have more than 350,000 side car files following this rule. I also love the idea to allow side cars for all file types, even ".jpg", ".tiff" or whatever. Using side cars is much smarter than writing meta data into the image files. Makes backup much smaller and faster :-) So here's my suggestion to allow all thinkable naming schemes and leave the decision to the users. There already exists a dialogue to add other extensions like ".pp3". But this only can give "{basename}{ext}.pp3". Why not drill this procedure and allow to type full templates like "{basename}{ext}.ext" (used by dk) "{basename}.ext" (the standard from adobe and widely used outside the linux world) "{basename}{ext}.pp3" (the sample in the dialogue in dk) or even "{subfolder}/{basename}{ext}.ext" (for people who love to browse their file base and down't want to see the side cars) and also allow to type any other combination the users might want. Templates like "tiff:{basename}{ext}.ext" "jpg:{basename}{ext}.ext" "nef:{basename}.ext" "cr2:{basename}.ext" would even allow to have different naming schemes for different file types. Then make the top most template the default for writing if no other side car can be found and try the list top down to find a side car for reading. Thanx for reading, knick -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 379489] [Multiple separate X11 screens] [Multiple WMs] Dolphin spawns applications on current active tag of wrong X11 screen
https://bugs.kde.org/show_bug.cgi?id=379489 Manfred Knick changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WONTFIX --- Comment #5 from Manfred Knick --- > Would that be okay for you? Certainly, as already proposed at the end of comment 3 above. Julian, I'm sorry but I have given up on KDE in scenarios where I necessarily have to combine multiple different HW adapters, ensuring that special applications definitely run on their desired monitor ... Thanks for looking into the issue and for your polite, friendly statement. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 379488] [Multiple separate X11 screens] [Awesome WM] kate starts on wrong tag of current active X11 screen
https://bugs.kde.org/show_bug.cgi?id=379488 --- Comment #8 from Manfred Knick --- (In reply to Christoph Cullmann from comment #7) > Kate reuses existing instances. Which is a very good habit, indeed! > It ATM tries to reuse the "right" instance > based on your current active virtual desktop. ..^^^ Not precisely: it ignores from which X11 Screen it is requested. > kate -n will avoid that, ... No - c.f. (comment #1) : > > . . . "kate --n" > > do not help, as already stated in ... > I don't see how I can "change" kate to help your with that issue. Evaluate the _tuple_ [ X11 Screen | virtual screen ] of requesting in kate's initial code trying to identify _which_ instance of kate is running on the same X11 Screen. Two humble questions, for example: A) https://cgit.kde.org/kate.git/tree/kate/main.cpp#n325 ff // prefer the Kate instance running on the current virtual desktop ??? Does KWindowSystem::currentDesktop() respect Multiple X11 Screens? B) https://cgit.kde.org/kate.git/tree/kate/main.cpp#n334 ff // query instance current desktop ??? Does QDBusConnection::sessionBus() ? ??? Which sessionBus() ? Always that from Screen_0 ? Compare --> "B" in https://github.com/awesomeWM/awesome/issues/1759#issuecomment-298374308 . P.S.: WONTFIX is o.k. for me ... Thanks for answering! -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 379488] [Multiple separate X11 screens] [Awesome WM] kate starts on wrong tag of current active X11 screen
https://bugs.kde.org/show_bug.cgi?id=379488 --- Comment #6 from Manfred Knick --- (In reply to Christoph Feck from comment #5) > Since you reported it for multiple KDE applications, .^^. ??? Sorry - I don't understand. > are there actually KDE > applications that work correctly? Lots of. > In other words, is there anything that can > be fixed inside Kate, Surely. Esp., c.f. [ https://github.com/awesomeWM/awesome/issues/1759#issuecomment-298638157 ] To me, the code trying to map new KDE requests to already running ones seems broken. > or is this a general problem with all Qt5 applications? Definitely _not_ . Perhaps, you might consider reading the links referenced in "Description" above, esp. "Overview" and "... Patterns". Then, note the contradictory cross-check findings concerning ctwm and FVWM. You are welcome to use PM as desired. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 379914] [Multiple separate X11 screens] [Awesome WM] kde-apps/konsole-17.04.1 :: "close" :: app re-locates to another (hidden) tab
https://bugs.kde.org/show_bug.cgi?id=379914 --- Comment #2 from Manfred Knick --- Although confirmed as working stable multiple times, unfortunately, Elv13 stated that nobody @ Awesome would care about independent X11 screens ("ZaphoMode") any more; c.f. https://github.com/awesomeWM/awesome/issues/598#issuecomment-305114301 ff. Same disinterest stated by leading upstream (=KDE) developers. If really nobody cares besides me, I do not mind to close as "WONTFIX". -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 379914] [Multiple separate X11 screens] [Awesome WM] kde-apps/konsole-17.04.1 :: "close" :: app re-locates to another (hidden) tab
https://bugs.kde.org/show_bug.cgi?id=379914 --- Comment #1 from Manfred Knick --- Meanwhile also verified on ctwm with 4 screens. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 379489] [Multiple separate X11 screens] [Multiple WMs] Dolphin spawns applications on current active tag of wrong X11 screen
https://bugs.kde.org/show_bug.cgi?id=379489 --- Comment #3 from Manfred Knick --- Although confirmed as working stable multiple times, unfortunately, Elv13 stated that nobody @ Awesome would care about independent X11 screens ("ZaphoMode") any more; c.f. https://github.com/awesomeWM/awesome/issues/598#issuecomment-305114301 ff. Same disinterest stated by leading upstream (=KDE) developers. If really nobody cares besides me, I do not mind to close as "WONTFIX". -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 379489] [Multiple separate X11 screens] [Multiple WMs] Dolphin spawns applications on current active tag of wrong X11 screen
https://bugs.kde.org/show_bug.cgi?id=379489 --- Comment #2 from Manfred Knick --- Meanwhile also verified on ctwm with 4 screens. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 379488] [Multiple separate X11 screens] [Awesome WM] kate starts on wrong tag of current active X11 screen
https://bugs.kde.org/show_bug.cgi?id=379488 --- Comment #4 from Manfred Knick --- Although confirmed as working stable multiple times, unfortunately, Elv13 stated that nobody @ Awesome would care about independent X11 screens ("ZaphoMode") any more; c.f. https://github.com/awesomeWM/awesome/issues/598#issuecomment-305114301 ff. Same disinterest stated by leading upstream (=KDE) developers. If really nobody cares besides me, I do not mind to close as "WONTFIX". -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 379488] [Multiple separate X11 screens] [Awesome WM] kate starts on wrong tag of current active X11 screen
https://bugs.kde.org/show_bug.cgi?id=379488 --- Comment #3 from Manfred Knick --- Meanwhile also verified on ctwm with 4 screens. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 379914] New: [Multiple separate X11 screens] [Awesome WM] kde-apps/konsole-17.04.1 :: "close" :: app re-locates to another (hidden) tab
https://bugs.kde.org/show_bug.cgi?id=379914 Bug ID: 379914 Summary: [Multiple separate X11 screens] [Awesome WM] kde-apps/konsole-17.04.1 :: "close" :: app re-locates to another (hidden) tab Product: konsole Version: 17.04.0 Platform: Gentoo Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: konsole-de...@kde.org Reporter: manfred.kn...@t-online.de Target Milestone: --- Created attachment 105597 --> https://bugs.kde.org/attachment.cgi?id=105597&action=edit emerge --info konsole >> 0_emerge--info-konsole.txt Description: AWESOME Issue #1784 [Multiple separate X11 screens] kde-apps/konsole-17.04.1 :: "close" :: app re-locates to another (hidden) tab https://github.com/awesomeWM/awesome/issues/1784 -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 379488] [Multiple separate X11 screens] [Awesome WM] kate starts on wrong tag of current active X11 screen
https://bugs.kde.org/show_bug.cgi?id=379488 --- Comment #2 from Manfred Knick --- CONFIRM: " ... awesome pretty much does the same thing as you do when you start kate from a terminal." https://github.com/awesomeWM/awesome/issues/1759#issuecomment-298390441 At the very end, the cross-check findings concerning "FVWM -s" in [ https://github.com/awesomeWM/awesome/issues/1759#issuecomment-298620529 ] very much caught myself by suprise against all gathered expectation. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 379488] [Multiple separate X11 screens] [Awesome WM] kate starts on wrong tag of current active X11 screen
https://bugs.kde.org/show_bug.cgi?id=379488 --- Comment #1 from Manfred Knick --- In contrast to . . . "konsole --separate" [ https://github.com/awesomeWM/awesome/issues/598#issuecomment-166920100 ] , . . . "kate --startanon" . . . "kate -s" . . . "kate --n" do not help, as already stated in [ https://github.com/awesomeWM/awesome/issues/1759#issuecomment-298611832 ] . -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 379489] [Multiple separate X11 screens] [Multiple WMs] Dolphin spawns applications on current active tag of wrong X11 screen
https://bugs.kde.org/show_bug.cgi?id=379489 --- Comment #1 from Manfred Knick --- Created attachment 105332 --> https://bugs.kde.org/attachment.cgi?id=105332&action=edit emerge --info dbus >> 0_emerge--info-dbus.txt -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 379489] New: [Multiple separate X11 screens] [Multiple WMs] Dolphin spawns applications on current active tag of wrong X11 screen
https://bugs.kde.org/show_bug.cgi?id=379489 Bug ID: 379489 Summary: [Multiple separate X11 screens] [Multiple WMs] Dolphin spawns applications on current active tag of wrong X11 screen Product: dolphin Version: 17.04.0 Platform: Gentoo Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: manfred.kn...@t-online.de Target Milestone: --- Created attachment 105331 --> https://bugs.kde.org/attachment.cgi?id=105331&action=edit emerge --info dolphin >> 0_emerge--info-dolphin.txt Apps started via file-entries' context menu pop up on a wrong X11 screen. The real pursuit may well reside inside klauncher or dbus. In case, please be so kind to re-locate (I am not a QT/KDE expert). Overview: https://github.com/awesomeWM/awesome/issues/1759#issuecomment-298620529 Description of Startup Procedure: https://github.com/awesomeWM/awesome/issues/1759#issuecomment-298611832 Observation of Patterns: https://github.com/awesomeWM/awesome/issues/1759#issuecomment-298374308 Please, let me know which further information would be helpful. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 379488] New: [Multiple separate X11 screens] [Awesome WM] kate starts on wrong tag of current active X11 screen
https://bugs.kde.org/show_bug.cgi?id=379488 Bug ID: 379488 Summary: [Multiple separate X11 screens] [Awesome WM] kate starts on wrong tag of current active X11 screen Product: kate Version: 17.04.0 Platform: Gentoo Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: kwrite-bugs-n...@kde.org Reporter: manfred.kn...@t-online.de Target Milestone: --- Created attachment 105329 --> https://bugs.kde.org/attachment.cgi?id=105329&action=edit emerge --info kate >> 0_emerge--info-kate.txt Overview: https://github.com/awesomeWM/awesome/issues/1759#issuecomment-298620529 Description of Startup Procedure: https://github.com/awesomeWM/awesome/issues/1759#issuecomment-298611832 Observation of Patterns: https://github.com/awesomeWM/awesome/issues/1759#issuecomment-298374308 Please, let me know which further information would be helpful. -- You are receiving this mail because: You are watching all bug changes.