[konversation] [Bug 349675] Commands such as /fortune do not send messages
https://bugs.kde.org/show_bug.cgi?id=349675 argonel changed: What|Removed |Added Latest Commit|https://invent.kde.org/netw |https://invent.kde.org/netw |ork/konversation/-/commit/a |ork/konversation/-/commit/9 |941c4fd4faf45cb8a9bdda1b13f |f0a87cbc0376bb188076c9c23c0 |bc035cad4335|9e337754e9ce --- Comment #6 from argonel --- Git commit 9f0a87cbc0376bb188076c9c23c09e337754e9ce by Eli MacKenzie. Committed on 21/05/2024 at 23:49. Pushed by argonel into branch 'release/24.05'. Provide scripts with an env var to find qdbus While the qdbus tool has been a RUNTIME dependency of Konversation since 2008, most distros didn't add a requirement. Given there's no standard way to advertise runtime deps, qdbus is now a build dep in addition to being a runtime dep. Unfortunately qdbus doesn't have a consistent name nor location. This attempts to find it by asking Qt where the binaries probably got installed and then tries a few possible names. A script run from inside Konversation now expects to receive an environment variable "KONVERSATION_DBUS_BIN" that is the full pathname of the actual program. This is set by the script launcher if it isn't present in the environment on launch. FIXED-IN: 1.10.24020 M +11 -0CMakeLists.txt M +1-0ChangeLog M +2-0NEWS M +5-4data/scripting_support/python/konversation/dbus.py M +2-2data/scripting_support/python/konversation/i18n.py M +2-1data/scripts/fortune M +2-2data/scripts/gauge M +3-2data/scripts/media M +1-1data/scripts/sayclip M +2-2data/scripts/tinyurl M +7-5data/scripts/uptime M +13 -0src/CMakeLists.txt A +1-0src/konvi_qdbus.h.in M +3-0src/scriptlauncher.cpp https://invent.kde.org/network/konversation/-/commit/9f0a87cbc0376bb188076c9c23c09e337754e9ce -- You are receiving this mail because: You are watching all bug changes.
[konversation] [Bug 349675] Commands such as /fortune do not send messages
https://bugs.kde.org/show_bug.cgi?id=349675 argonel changed: What|Removed |Added Latest Commit|https://invent.kde.org/netw |https://invent.kde.org/netw |ork/konversation/-/commit/b |ork/konversation/-/commit/a |7a551d6fd07c901d81b25f46f07 |941c4fd4faf45cb8a9bdda1b13f |82a9846c7c23|bc035cad4335 --- Comment #5 from argonel --- Git commit a941c4fd4faf45cb8a9bdda1b13fbc035cad4335 by Eli MacKenzie. Committed on 21/05/2024 at 23:50. Pushed by argonel into branch 'master'. Provide scripts with an env var to find qdbus While the qdbus tool has been a RUNTIME dependency of Konversation since 2008, most distros didn't add a requirement. Given there's no standard way to advertise runtime deps, qdbus is now a build dep in addition to being a runtime dep. Unfortunately qdbus doesn't have a consistent name nor location. This attempts to find it by asking Qt where the binaries probably got installed and then tries a few possible names. A script run from inside Konversation now expects to receive an environment variable "KONVERSATION_DBUS_BIN" that is the full pathname of the actual program. This is set by the script launcher if it isn't present in the environment on launch. FIXED-IN: 1.10.24020 M +11 -0CMakeLists.txt M +1-0ChangeLog M +2-0NEWS M +5-4data/scripting_support/python/konversation/dbus.py M +2-2data/scripting_support/python/konversation/i18n.py M +2-1data/scripts/fortune M +2-2data/scripts/gauge M +3-2data/scripts/media M +1-1data/scripts/sayclip M +2-2data/scripts/tinyurl M +7-5data/scripts/uptime M +13 -0src/CMakeLists.txt A +1-0src/konvi_qdbus.h.in M +3-0src/scriptlauncher.cpp https://invent.kde.org/network/konversation/-/commit/a941c4fd4faf45cb8a9bdda1b13fbc035cad4335 -- You are receiving this mail because: You are watching all bug changes.
[konversation] [Bug 471865] Open ircs:// URLs with the IANA-assigned port 6697 and not 6667
https://bugs.kde.org/show_bug.cgi?id=471865 argonel changed: What|Removed |Added Summary|Automatically open ircs:// |Open ircs:// URLs with the |protocol links with its |IANA-assigned port 6697 and |assinged port 6697 and not |not 6667 |6667| Status|CONFIRMED |ASSIGNED Component|protocol|general --- Comment #1 from argonel --- Per RFC 7194[1] port 994 was historically assigned for TLS/SSL, but appears to have been replaced with 6697 "ircs-u" in the IANA registry. Konversation doesn't use 994 either. [1] https://datatracker.ietf.org/doc/html/rfc7194 [2] https://www.iana.org/assignments/service-names-port-numbers/service-names-port-numbers.xhtml?search=6697 -- You are receiving this mail because: You are watching all bug changes.
[konversation] [Bug 471865] Automatically open ircs:// protocol links with its assinged port 6697 and not 6667
https://bugs.kde.org/show_bug.cgi?id=471865 argonel changed: What|Removed |Added Ever confirmed|0 |1 CC||argo...@gmail.com Assignee|konversation-de...@kde.org |argo...@gmail.com Status|REPORTED|CONFIRMED -- You are receiving this mail because: You are watching all bug changes.
[konversation] [Bug 482617] clicking the close button in 'Konversation' Does not close the app or right clicking and selecting close doesn't work either.
https://bugs.kde.org/show_bug.cgi?id=482617 argonel changed: What|Removed |Added Resolution|--- |DUPLICATE CC||argo...@gmail.com Status|REPORTED|RESOLVED --- Comment #1 from argonel --- *** This bug has been marked as a duplicate of bug 482316 *** -- You are receiving this mail because: You are watching all bug changes.
[konversation] [Bug 482316] Close to system tray not working after program start
https://bugs.kde.org/show_bug.cgi?id=482316 argonel changed: What|Removed |Added CC||mrjoehar...@outlook.com --- Comment #4 from argonel --- *** Bug 482617 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[konversation] [Bug 482316] Close to system tray not working after program start
https://bugs.kde.org/show_bug.cgi?id=482316 argonel changed: What|Removed |Added Resolution|--- |FIXED Latest Commit||https://invent.kde.org/netw ||ork/konversation/-/commit/1 ||d554cb2c29e57bfd58b9aed7643 ||dcb60fbf8659 Status|REPORTED|RESOLVED --- Comment #2 from argonel --- Git commit 1d554cb2c29e57bfd58b9aed7643dcb60fbf8659 by Eli MacKenzie. Committed on 03/03/2024 at 22:33. Pushed by argonel into branch 'release/24.02'. Delay tray setup until mainwindow state restored Otherwise the the KSNI appears to lose track of the main window. M +3-3src/mainwindow.cpp https://invent.kde.org/network/konversation/-/commit/1d554cb2c29e57bfd58b9aed7643dcb60fbf8659 -- You are receiving this mail because: You are watching all bug changes.
[konversation] [Bug 349675] Commands such as /fortune do not send messages
https://bugs.kde.org/show_bug.cgi?id=349675 argonel changed: What|Removed |Added Resolution|--- |FIXED Version Fixed In||1.10.24020 Status|CONFIRMED |RESOLVED Latest Commit||https://invent.kde.org/netw ||ork/konversation/-/commit/b ||7a551d6fd07c901d81b25f46f07 ||82a9846c7c23 --- Comment #4 from argonel --- Git commit b7a551d6fd07c901d81b25f46f0782a9846c7c23 by Eli MacKenzie. Committed on 22/02/2024 at 05:28. Pushed by argonel into branch 'release/24.02'. Provide scripts with an env var to find qdbus While the qdbus tool has been a RUNTIME dependency of Konversation since 2008, most distros didn't add a requirement. Given there's no standard way to advertise runtime deps, qdbus is now a build dep in addition to being a runtime dep. Unfortunately qdbus doesn't have a consistent name nor location. This attempts to find it by asking Qt where the binaries probably got installed and then tries a few possible names. A script run from inside Konversation now expects to receive an environment variable "KONVERSATION_DBUS_BIN" that is the full pathname of the actual program. This is set by the script launcher if it isn't present in the environment on launch. FIXED-IN: 1.10.24020 M +11 -0CMakeLists.txt M +1-0ChangeLog M +2-0NEWS M +5-4data/scripting_support/python/konversation/dbus.py M +2-2data/scripting_support/python/konversation/i18n.py M +2-1data/scripts/fortune M +2-2data/scripts/gauge M +3-2data/scripts/media M +1-1data/scripts/sayclip M +2-2data/scripts/tinyurl M +7-5data/scripts/uptime M +13 -0src/CMakeLists.txt A +1-0src/konvi_qdbus.h.in M +3-0src/scriptlauncher.cpp https://invent.kde.org/network/konversation/-/commit/b7a551d6fd07c901d81b25f46f0782a9846c7c23 -- You are receiving this mail because: You are watching all bug changes.
[konversation] [Bug 480452] konversation kf6 embedded konsole doesn't work
https://bugs.kde.org/show_bug.cgi?id=480452 argonel changed: What|Removed |Added Resolution|--- |FIXED Latest Commit||https://invent.kde.org/netw ||ork/konversation/-/commit/c ||2421f419e162ad2e7a09cf9eeb5 ||611aba3d3263 Status|CONFIRMED |RESOLVED --- Comment #1 from argonel --- Git commit c2421f419e162ad2e7a09cf9eeb5611aba3d3263 by Eli MacKenzie. Committed on 31/01/2024 at 04:04. Pushed by argonel into branch 'release/24.02'. Fix the embedded Konsole Qt6 appears to require the explicit addition of the kpart's widget to its parent. M +1-0src/konsolepanel.cpp https://invent.kde.org/network/konversation/-/commit/c2421f419e162ad2e7a09cf9eeb5611aba3d3263 -- You are receiving this mail because: You are watching all bug changes.
[konversation] [Bug 480452] konversation kf6 embedded konsole doesn't work
https://bugs.kde.org/show_bug.cgi?id=480452 argonel changed: What|Removed |Added CC||argo...@gmail.com Ever confirmed|0 |1 Assignee|konversation-de...@kde.org |argo...@gmail.com Status|REPORTED|CONFIRMED -- You are receiving this mail because: You are watching all bug changes.
[konversation] [Bug 467524] Please give i18n context at "Query author" in src/viewer/irccontextmenus.cpp
https://bugs.kde.org/show_bug.cgi?id=467524 argonel changed: What|Removed |Added Latest Commit|https://invent.kde.org/netw |https://invent.kde.org/netw |ork/konversation/commit/e5f |ork/konversation/-/commit/9 |96268c234deec8771f4ae4fdfe1 |c1e10c32cef9e96f3dbcf517d77 |d4ff990903 |8c85cf3dfeee --- Comment #2 from argonel --- Git commit 9c1e10c32cef9e96f3dbcf517d778c85cf3dfeee by Eli MacKenzie. Committed on 26/11/2023 at 23:03. Pushed by argonel into branch 'master'. Adds an i18n context to the topic editor OpenQuery action The term "query" is used in IRC clients to refer to a private message window, which could be ambiguous to those that do not use IRC. (cherry picked from commit e5f96268c234deec8771f4ae4fdfe1d4ff990903) This was intended to be merged to master prior to 23.08 but was missed, so it does not exist in that version. M +1-1src/viewer/irccontextmenus.cpp https://invent.kde.org/network/konversation/-/commit/9c1e10c32cef9e96f3dbcf517d778c85cf3dfeee -- You are receiving this mail because: You are watching all bug changes.
[konversation] [Bug 471940] Konversation does not send CAP END if no CAP REQ is required
https://bugs.kde.org/show_bug.cgi?id=471940 argonel changed: What|Removed |Added Latest Commit|https://invent.kde.org/netw |https://invent.kde.org/netw |ork/konversation/-/commit/3 |ork/konversation/-/commit/1 |81c067f62a77a2e0dfbac801546 |bc9a08c119c963d8a1be7dec5c8 |ebbd98b0b43f|aa98231ec589 --- Comment #3 from argonel --- Git commit 1bc9a08c119c963d8a1be7dec5c8aa98231ec589 by Eli MacKenzie, on behalf of Thomas Jepp. Committed on 07/08/2023 at 03:58. Pushed by argonel into branch 'master'. caps: prevent connection hang when none are requested Konversation didn't send CAP END after CAP LS, unless it actually requested caps with CAP REQ. As per https://ircv3.net/specs/extensions/capability-negotiation.html it must send CAP END - otherwise servers will just hang the connection and never complete the initial registration. (cherry picked from commit 381c067f62a77a2e0dfbac801546ebbd98b0b43f) M +2-0src/irc/server.cpp https://invent.kde.org/network/konversation/-/commit/1bc9a08c119c963d8a1be7dec5c8aa98231ec589 -- You are receiving this mail because: You are watching all bug changes.
[konversation] [Bug 471940] Konversation does not send CAP END if no CAP REQ is required
https://bugs.kde.org/show_bug.cgi?id=471940 argonel changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED Latest Commit||https://invent.kde.org/netw ||ork/konversation/-/commit/3 ||81c067f62a77a2e0dfbac801546 ||ebbd98b0b43f --- Comment #2 from argonel --- Git commit 381c067f62a77a2e0dfbac801546ebbd98b0b43f by Eli MacKenzie, on behalf of Thomas Jepp. Committed on 07/08/2023 at 03:49. Pushed by argonel into branch 'release/23.08'. caps: prevent connection hang when none are requested Konversation didn't send CAP END after CAP LS, unless it actually requested caps with CAP REQ. As per https://ircv3.net/specs/extensions/capability-negotiation.html it must send CAP END - otherwise servers will just hang the connection and never complete the initial registration. M +2-0src/irc/server.cpp https://invent.kde.org/network/konversation/-/commit/381c067f62a77a2e0dfbac801546ebbd98b0b43f -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 422006] [Dolphin] Emptying trash does not trigger view refresh
https://bugs.kde.org/show_bug.cgi?id=422006 argonel changed: What|Removed |Added Status|CONFIRMED |NEEDSINFO CC||argo...@gmail.com Resolution|--- |WAITINGFORINFO --- Comment #21 from argonel --- (In reply to adec2011.ac from comment #20) > (In reply to adec2011.ac from comment #19) > > (In reply to Méven Car from comment #17) > > > I don't reproduce this in Dolphin 22.12. > > > > > > Can anyone still reproduce it ? > > > > It is still happening for me. > > > > In an open dolphin windows I have a wastebin icon under the places list. > > WHen i right click and select empty wastebin the bin doesnt empty and the > > icon doesnt change unless i physically click the icon to open it in the > > dolphin window and refresh the contents > > > > Operating System: KDE neon Testing Edition > > KDE Plasma Version: 5.27.4 > > KDE Frameworks Version: 5.105.0 > > Qt Version: 5.15.8 > > Kernel Version: 6.2.10-1-liquorix-amd64 (64-bit) > > Graphics Platform: X11 > > Processors: 4 × Intel® Core™ i5-4460 CPU @ 3.20GHz > > Memory: 15.6 GiB of RAM > > Graphics Processor: NVIDIA GeForce GTX 1050 Ti/PCIe/SSE2 > > Manufacturer: Gigabyte Technology Co., Ltd. > > Product Name: H81M-S2H > > Just to add my dolphin is Version 23.03.90 It looks like you're running Neon, which has kde-inotify-survey packaged. That package installs a notifier module, but also a commandline utility that outputs the current inotify usage as a json file. If you were to run kde-inotify-survey in Konsole immediately after reproducing the issue and paste the results into a reply here, it might help diagnose the problem. -- You are receiving this mail because: You are watching all bug changes.
[konversation] [Bug 467524] Please give i18n context at "Query author" in src/viewer/irccontextmenus.cpp
https://bugs.kde.org/show_bug.cgi?id=467524 argonel changed: What|Removed |Added Resolution|--- |FIXED Latest Commit||https://invent.kde.org/netw ||ork/konversation/commit/e5f ||96268c234deec8771f4ae4fdfe1 ||d4ff990903 Status|REPORTED|RESOLVED --- Comment #1 from argonel --- Git commit e5f96268c234deec8771f4ae4fdfe1d4ff990903 by Eli MacKenzie. Committed on 27/03/2023 at 06:28. Pushed by argonel into branch 'release/23.04'. Adds an i18n context to the topic editor OpenQuery action The term "query" is used in IRC clients to refer to a private message window, which could be ambiguous to those that do not use IRC. M +1-1src/viewer/irccontextmenus.cpp https://invent.kde.org/network/konversation/commit/e5f96268c234deec8771f4ae4fdfe1d4ff990903 -- You are receiving this mail because: You are watching all bug changes.
[konversation] [Bug 407290] Notifications do not work in Windows OS
https://bugs.kde.org/show_bug.cgi?id=407290 --- Comment #5 from argonel --- *** Bug 465139 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[konversation] [Bug 465139] Notifications are not working at all in Windows :/
https://bugs.kde.org/show_bug.cgi?id=465139 argonel changed: What|Removed |Added Status|REPORTED|RESOLVED CC||argo...@gmail.com Resolution|--- |DUPLICATE --- Comment #1 from argonel --- *** This bug has been marked as a duplicate of bug 407290 *** -- You are receiving this mail because: You are watching all bug changes.
[konversation] [Bug 436384] Notifications do not work on Windows
https://bugs.kde.org/show_bug.cgi?id=436384 argonel changed: What|Removed |Added Resolution|--- |DUPLICATE CC||argo...@gmail.com Status|CONFIRMED |RESOLVED --- Comment #3 from argonel --- *** This bug has been marked as a duplicate of bug 407290 *** -- You are receiving this mail because: You are watching all bug changes.
[konversation] [Bug 407290] Notifications do not work in Windows OS
https://bugs.kde.org/show_bug.cgi?id=407290 argonel changed: What|Removed |Added CC||fhdpo2zdkgrgktctxxumrxd2ayh ||t...@onionmail.org --- Comment #4 from argonel --- *** Bug 436384 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[konversation] [Bug 407290] Notifications do not work in Windows OS
https://bugs.kde.org/show_bug.cgi?id=407290 argonel changed: What|Removed |Added Summary|Notifications do not work |Notifications do not work ||in Windows OS CC||argo...@gmail.com --- Comment #3 from argonel --- Windows builds are created by the KDE build service, there are no Windows-based Konversation developers. -- You are receiving this mail because: You are watching all bug changes.
[konversation] [Bug 311086] Konversation reconnects and rejoins after the client is /kill'd and /kick'd
https://bugs.kde.org/show_bug.cgi?id=311086 argonel changed: What|Removed |Added Status|NEEDSINFO |CONFIRMED Resolution|WAITINGFORINFO |--- Ever confirmed|0 |1 --- Comment #9 from argonel --- Kill handling has not been implemented. -- You are receiving this mail because: You are watching all bug changes.
[konversation] [Bug 335236] Alt+Space shortcut will be taken in PlasmaNext
https://bugs.kde.org/show_bug.cgi?id=335236 argonel changed: What|Removed |Added Ever confirmed|0 |1 Version|unspecified |Git Status|NEEDSINFO |CONFIRMED Resolution|WAITINGFORINFO |--- --- Comment #7 from argonel --- Konversation's default shortcut is still alt+space, and it does conflict as predicted. -- You are receiving this mail because: You are watching all bug changes.
[konversation] [Bug 159967] Option to strip bold, underline and italic control codes from incoming messages
https://bugs.kde.org/show_bug.cgi?id=159967 argonel changed: What|Removed |Added Assignee|konsole-de...@kde.org |konversation-de...@kde.org Component|general |general Resolution|REMIND |--- Product|konsole |konversation Status|NEEDSINFO |CONFIRMED Platform|PCLinuxOS |unspecified --- Comment #8 from argonel --- (In reply to Dennis Vargason from comment #7) > When I try to put my password in it,It don't show in box stays blank than > said wrong password Dennis, you appear to have updated the wrong bug. This one is about the formatting of incoming messages in Konversation. -- You are receiving this mail because: You are watching all bug changes.
[konversation] [Bug 461051] log file name prefix not updated when network renamed
https://bugs.kde.org/show_bug.cgi?id=461051 argonel changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|CONFIRMED -- You are receiving this mail because: You are watching all bug changes.
[konversation] [Bug 461051] New: log file name prefix not updated when network renamed
https://bugs.kde.org/show_bug.cgi?id=461051 Bug ID: 461051 Summary: log file name prefix not updated when network renamed Classification: Applications Product: konversation Version: Git Platform: Other OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: general Assignee: konversation-de...@kde.org Reporter: argo...@gmail.com Target Milestone: --- SUMMARY If one changes the network name without first closing the tab for the server, the logging will continue in the old network name. STEPS TO REPRODUCE 1. Create a network with the name "A" and add a server to it 2. Connect to said network so as to create the logs 3. Open the logging dir in Dolphin 4. See that the files are prefixed with "A" 5. Disconnect from the network but do not close the tab 6. Rename the network in the server list box 7. Reconnect to the network 8. See that no files with the new name are created 9. Repeat steps above but close the tab in step 6 and see that the new name is used OBSERVED RESULT When the network is disconnected but not closed, renaming the network doesn't switch to logging under the new name. EXPECTED RESULT Technically the logging could immediately begin in the new logs given the way the files are used, but this would be somewhat jarring when reading the logs later. Konversation could offer to rename the existing logs if the network is connected. When the network is disconnected however, it should behave the same as if the network is closed. -- You are receiving this mail because: You are watching all bug changes.
[konversation] [Bug 372857] First space eaten at beginning of line if formatting is used
https://bugs.kde.org/show_bug.cgi?id=372857 argonel changed: What|Removed |Added Status|NEEDSINFO |CONFIRMED Version|frameworks |Git Ever confirmed|0 |1 Resolution|WAITINGFORINFO |--- --- Comment #2 from argonel --- The space is sent, it is lost after receipt. -- You are receiving this mail because: You are watching all bug changes.
[konversation] [Bug 355405] Raw window can't be cleared
https://bugs.kde.org/show_bug.cgi?id=355405 argonel changed: What|Removed |Added Ever confirmed|0 |1 Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |CONFIRMED --- Comment #2 from argonel --- This is unchanged, although Edit -> Clear All does affect the raw tab. -- You are receiving this mail because: You are watching all bug changes.
[konversation] [Bug 460217] Quick buttons not show on screen
https://bugs.kde.org/show_bug.cgi?id=460217 argonel changed: What|Removed |Added Status|RESOLVED|CLOSED Resolution|FIXED |NOT A BUG -- You are receiving this mail because: You are watching all bug changes.
[konversation] [Bug 460217] Quick buttons not show on screen
https://bugs.kde.org/show_bug.cgi?id=460217 argonel changed: What|Removed |Added CC||argo...@gmail.com Status|REPORTED|RESOLVED Resolution|--- |WORKSFORME --- Comment #1 from argonel --- The setting in Interface -> Quick Buttons is "Show quick buttons that operate on nicknames in nickname context menus", which will cause any quickbutton that contains the "%u" placeholder to also appear in the context menu of a nickname. To enable the quick buttons in the chat window, the setting is Interface -> Chat Window -> Show quick buttons. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 438596] .profile not being sourced
https://bugs.kde.org/show_bug.cgi?id=438596 argonel changed: What|Removed |Added Resolution|--- |WAITINGFORINFO CC||argo...@gmail.com Status|REOPENED|RESOLVED --- Comment #4 from argonel --- (In reply to Chris Caudle from comment #3) > Seems unlikely this is a shell configuration issue. My .bash_profile is > sourced in Konsole in Plasma/X11, in non-graphical tty, in bash through SSH. > Only in Konsole running in Plasma/Wayland is .bash_profile not sourced. I > believe this was incorrectly marked as not a bug. The non-graphical and SSH would be login sessions, and bash would therefore source .bash_profile. (https://www.gnu.org/savannah-checkouts/gnu/bash/manual/bash.html#Bash-Startup-Files) Given that it works in X11 but not in Wayland, perhaps you have a .xsession file that sources .profile or .bash_profile. (https://wiki.debian.org/Xsession). -- You are receiving this mail because: You are watching all bug changes.
[konversation] [Bug 451725] Window maximized state and toolbar visibility lost after restart
https://bugs.kde.org/show_bug.cgi?id=451725 argonel changed: What|Removed |Added CC||argo...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[konversation] [Bug 451588] natively support ZNC networks
https://bugs.kde.org/show_bug.cgi?id=451588 argonel changed: What|Removed |Added Summary|Konversation identifies |natively support ZNC |networks strangely |networks CC||argo...@gmail.com Severity|normal |wishlist -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 447745] Deleting saved html page does not delete associated folder
https://bugs.kde.org/show_bug.cgi?id=447745 argonel changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |DOWNSTREAM --- Comment #3 from argonel --- (In reply to hong from comment #2) > Created attachment 145008 [details] > attachment-19124-0.html > > yes, for web developers perhaps, > but not for the general public. > ok, if not a bug, can it be a feature request? The feature request would need to be for the browser that saved the page as an html file and an adjacent folder. It could create a folder and save the items within, or it could save the page as a single file. There is no reliable way for Dolphin to know that the folder and the html file are associated. The only way to do this in Dolphin would be to employ a heuristic that needs to be kept in sync with the browser that saved the page. If the developers of that browser change their minds about how page saving works, Dolphin would need to support both the "old" way(s) and the "new" way. Each browser uses its own convention for saving pages, and thus Dolphin would need a heuristic for each of them. This is not sustainable. -- You are receiving this mail because: You are watching all bug changes.
[konversation] [Bug 446673] Channel Settings, Modes tab "User Limit" QSpinBox uses default max=99, messing up any higher setting by /cmode +l NNN
https://bugs.kde.org/show_bug.cgi?id=446673 argonel changed: What|Removed |Added Summary|Channel Settings, Modes tab |Channel Settings, Modes tab | "User L_imit" QSpinBox | "User Limit" QSpinBox uses |uses default max=99,|default max=99, messing up |messing up any higher |any higher setting by |setting by /cmode +l NNN|/cmode +l NNN -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 440986] Okular is able to overwrite read-only files
https://bugs.kde.org/show_bug.cgi?id=440986 argonel changed: What|Removed |Added CC||argo...@gmail.com --- Comment #3 from argonel --- (In reply to Adriano Vilela from comment #0) > I reported this on a Debian mailing list (I'm using Debian Testing), and > somebody suggested that this probably happens because Okular is saving the > modifications to a temporary file and then deleting the original file and > writing the temporary file to a new file with the same name as the original > file. I understand that. However, I think that this behavior is unexpected > and very problematic. That description is almost correct. What actually happens is that the file is saved as a new file which is then renamed to have the old file's name. This method of saving a file is to preserve the original data if something goes wrong during save, taking advantage of the POSIX rules regarding renaming files. A discussion about why the lack of a "write" permission doesn't make a file "read-only" belongs elsewhere, but the "write" permission doesn't apply to the file's name (or any of its other metadata). A proper solution for truly making files "read-only" isn't in Okular's scope, but to be friendly Okular could check to see if the file is "writable" and prompt if it isn't. (In reply to David Hurka from comment #2) > This is AFAIK the only way of saving files that is used by existing > applications. Modifying files in-place maybe makes sense for databases, > which Okular isn’t. The lack of a "write" permission actually _prevents_ "in-place" modification, so technically the behavior here is correct. -- You are receiving this mail because: You are watching all bug changes.
