[Marknote] [Bug 487500] New: [Feature request] no inline nor code block
https://bugs.kde.org/show_bug.cgi?id=487500 Bug ID: 487500 Summary: [Feature request] no inline nor code block Classification: Applications Product: Marknote Version: 1.2.1 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: m...@kaidan.im Reporter: docampo.an...@gmail.com CC: c...@carlschwan.eu, m...@kaidan.im Target Milestone: --- SUMMARY: There is no code block nor with markdown, neither with the rich text format tool. We should be able to do a `inline` code formatting as well as ```bash do a code block ``` -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 485464] New: Notification label in obtain new complements shows the words cut off
https://bugs.kde.org/show_bug.cgi?id=485464 Bug ID: 485464 Summary: Notification label in obtain new complements shows the words cut off Classification: I don't know Product: kde Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: docampo.an...@gmail.com Target Milestone: --- Created attachment 168437 --> https://bugs.kde.org/attachment.cgi?id=168437=edit error show in different dialogs SUMMARY I noticed the words in the sentence, “The content available here has been submitted by users like you, so its functionality and stability has not been tested by its distributor.” (sorry I have that sentence in Spanish, I had to translate it, perhaps in English is not that exact sentence) when you are adding a community downloadable content like a wallpaper, a SDDM theme, a plasmoid, etc, shows cut off as in the attached image. STEPS TO REPRODUCE 1. Try to download a wallpaper/plasmoid/theme through the button "Obtain new complements" OBSERVED RESULT The information text is cut off. If you maximize that window, the text is shown fine. EXPECTED RESULT Info text should be properly aligned SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch Linux amd64 KDE Plasma Version: 6.0.3 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.3 -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 485423] New: [Feature Request] [Discussion] Remember/change password
https://bugs.kde.org/show_bug.cgi?id=485423 Bug ID: 485423 Summary: [Feature Request] [Discussion] Remember/change password Classification: I don't know Product: kde Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: docampo.an...@gmail.com Target Milestone: --- I usually face low-level users (the kind of users who write their passwords on a post-it) who don’t use their computer in a daily basis, and sometimes they call me because they forgot their password. I can do nothing besides tell them to bring their computer and I will reset the password with the live CD method. On Windows, they can use the 3 secret questions method for local accounts, and if you use an online account, you can reset your password though email validation or other methods, mac also offers some options to reset a forgotten password. Obviously, those OSes are targeted to less tech-savy users, but I think it would be nice to offer a solution on Linux. The three secret questions seems to be the easiest one to develop, but sddm and the underlying desktop environment (or window manager) perhaps needs to be in “harmony”. At least, sddm should be able to change the user’s password if they answer the three questions, on the other hand, there should be a “wizard” asking for those questions inside the desktop (a secondary application). I think devs from at least KDE and SDDM should agree to do their part of the job, KDE devs to do the wizard, and SDDM the logic to remember/reset the password using the secret questions entered by the user. What do you think? It’s this even doable? I’m going to open this discussion as well on SDDM’s github https://github.com/sddm/sddm/issues/1913 because I think this cannot be implemented lonely by Plasma devs. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 484256] plasma closes session automatically
https://bugs.kde.org/show_bug.cgi?id=484256 --- Comment #7 from Angel Docampo --- Just to mention I disabled nvidia_modeset because, IIRC, I activated it to make hyprland working with nvidia, but as we can see, plasma hangs even with this change, and I had installed hypranland and the nvidia_modeset module activated for more than a year, and all this stuff began with the plasma 6 upgrade. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 484256] plasma closes session automatically
https://bugs.kde.org/show_bug.cgi?id=484256 --- Comment #6 from Angel Docampo --- It happened again. This time, I was in a videocall in the company's Mac, and my computer was going idle, and everytime the screen went off, I pressed quickly one key before the desktop were locked. One time, though, even I pressed the key, the sddm screen appeared, and yes, the session started once again. I paste the logs, they are pretty similar than the last I posted: X11 seems to die just when the screen lock starts. Here is the pastebin of the sudden crash and this time, I'm including the login as well https://hastebin.com/share/rifegefisi.sql -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 484256] plasma closes session automatically
https://bugs.kde.org/show_bug.cgi?id=484256 --- Comment #5 from Angel Docampo --- It happened again. I went to lunch, and I when I came back, session was closed. I opened a terminal and execute the command uptime. > uptime > > > > 15:40:33 up 7:27, 1 user, load average: 3,45, 0,93, 0,32 I've took a look into journalctl and I saw a core dump, but I don't know if it was related to KDE... https://hastebin.com/share/kozoqefiji.yaml -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 484256] plasma closes session automatically
https://bugs.kde.org/show_bug.cgi?id=484256 Angel Docampo changed: What|Removed |Added Resolution|FIXED |--- Status|NEEDSINFO |REPORTED --- Comment #4 from Angel Docampo --- The issue is present after the upgrade to plasma 6, so while it could be due to my OS, the only change is the version of plasma. As I said, I would be eager to help if someone tell me how can I see the plasma logs and have a look when this happens, which happens in a daily basis -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 484256] plasma closes session automatically
https://bugs.kde.org/show_bug.cgi?id=484256 Angel Docampo changed: What|Removed |Added Resolution|WAITINGFORINFO |FIXED --- Comment #2 from Angel Docampo --- Sure, what else can I provide? Is there any log where I can see if something has closed the session? When I start plasma again, there is no crash report, so it seems it closed "properly". I'm running arhc linux in this computer since my last computer died 3 years ago. So I've been upgrading everything to the latest version since then. This issue is hard to reproduce, I turn on the computer at 7am and power it off around 2am, I work from home, so I leave it with my session open always, and sometimes I need to go AFK for a while. It does not happens every time, just one time or so each day. If I could take a look somewhere in those moments, it would be of great help. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 484256] New: plasma closes session automatically
https://bugs.kde.org/show_bug.cgi?id=484256 Bug ID: 484256 Summary: plasma closes session automatically Classification: Plasma Product: plasmashell Version: 6.0.2 Platform: Arch Linux OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: docampo.an...@gmail.com CC: k...@davidedmundson.co.uk Target Milestone: 1.0 SUMMARY Since the upgrade to Plasma 6, I find many times, at least once per day, when I left my computer with the desktop idle during a while, when I come back, the session has been closed. Uptime command shows my computer hasn't been restarted, but when I enter the credentials, the desktop loads as if the session were closed. STEPS TO REPRODUCE 1. Open plasma session 2. Do some stuff 3. Leave the computer, go for a walk, to lunch, etc OBSERVED RESULT Sometimes when I come back, the session is locked (as expected), some other times the session is still unlocked (even if it has been idle for two or three hours, which is not normal, but I think it's not related to this issue and is not so fatidic as at least I don't lose any job, or close any ssh), and sometimes, the session has been closed, which in my opinion is the worst case scenario, because in this case, I've lost all the unsaved work. EXPECTED RESULT Session should be locked and monitors in saving energy mode. (if it's configured like this) SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE Plasma Version: 6.0.2 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 ADDITIONAL INFORMATION I'm on X11, as Wayland is buggy with my nvidia card. -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 483714] New: Focus stays on old terminal
https://bugs.kde.org/show_bug.cgi?id=483714 Bug ID: 483714 Summary: Focus stays on old terminal Classification: Applications Product: yakuake Version: 24.02.0 Platform: Arch Linux OS: Linux Status: REPORTED Severity: major Priority: NOR Component: general Assignee: h...@kde.org Reporter: docampo.an...@gmail.com Target Milestone: --- SUMMARY Since the latest update, I noticed when I split a terminal (vertically or horizontally), focus remain on the original terminal, and not in the new spawned one. If I hide and show yakuake again, then, the focus goes to the new splitted terminal, but if I split the terminal again, then I lose the focus completely, and I have to point it with the mouse (or hide and show the terminal once again to regain focus on the new opened terminal). STEPS TO REPRODUCE 1. open yakuake 2. split a terminal 3. focus remains on the first terminal, not in the new one -- don't do nothing yet 4. hide yakuake 5. show it again 6. focus now is in the newest terminal split -- still don't do nothing 7. split the terminal again 8. now there is no terminal focused at all, you need to a) grab your mouse and point it, b) switch focus with your hotkeys, or c) hide and show yakuake once again. 9. now, every time you split your terminal, the focus is lost. EXPECTED RESULT When a terminal is split, focused split terminal should be the newest one. Besides, hiding and showing the terminal should not lose the focus at all, nor losing it when new splitting are done. SOFTWARE/OS VERSIONS Linux/KDE Plasma: 24.02.0 KDE Plasma Version: 6.0.1 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[Keysmith] [Bug 475427] Import/export functionality
https://bugs.kde.org/show_bug.cgi?id=475427 Angel Docampo changed: What|Removed |Added CC||docampo.an...@gmail.com --- Comment #1 from Angel Docampo --- I would like to see the export feature, to be able to back up/sync my keys to another devices, and why not, to change to another application if keysmith doesn't fulfill my needs. -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 470890] Allow to reorder runners
https://bugs.kde.org/show_bug.cgi?id=470890 Angel Docampo changed: What|Removed |Added CC||docampo.an...@gmail.com --- Comment #1 from Angel Docampo --- Created attachment 165826 --> https://bugs.kde.org/attachment.cgi?id=165826=edit opening VLC is a pain On my systems, yet the order of runners are also hardcoded, the Applications aren't the first option, which is quite inconvenient as shown in the attached image. There should be an option to let the user reorder the runners. -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 480245] Toggle maximize of split view
https://bugs.kde.org/show_bug.cgi?id=480245 Angel Docampo changed: What|Removed |Added CC||docampo.an...@gmail.com --- Comment #1 from Angel Docampo --- I endorse this request. I was just about to open this very same issue, but I notized Uwe did it first a few days ago. I'm a hardcore user of yakuake since more than a decade, and I always missed this functionality. My coworkers are using terminator o even tmux because those can maximize the split view and restore it back. Now konsole can do it, how hard should be to implement it on yakuake? -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 474222] Digital signing huge letters
https://bugs.kde.org/show_bug.cgi?id=474222 Angel Docampo changed: What|Removed |Added CC||docampo.an...@gmail.com --- Comment #1 from Angel Docampo --- Created attachment 161444 --> https://bugs.kde.org/attachment.cgi?id=161444=edit Signature options on other applications I've added another software to explain better what am I asking for. On the left side is MasterPDF options, and on the right side, Autofirma (the spanish official tool to sign documents). Both of them let configure some options, beign Autofirma the best one, letting the user configure the size, font, and information shown, and a live preview depending on the box size when dragged. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 474222] New: Digital signing huge letters
https://bugs.kde.org/show_bug.cgi?id=474222 Bug ID: 474222 Summary: Digital signing huge letters Classification: Applications Product: okular Version: 23.08.0 Platform: Archlinux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: PDF backend Assignee: okular-de...@kde.org Reporter: docampo.an...@gmail.com Target Milestone: --- Created attachment 161443 --> https://bugs.kde.org/attachment.cgi?id=161443=edit Text shown on a normal box SUMMARY I've added successfully my DNIe (country official's ID card) to okular certificates and signed the PDF. But I would like to have a preview and configure the size of the text inside the signing box as it is very huge and it's quite ugly. STEPS TO REPRODUCE 1. Add a proper certificate on okular 2. Sign a document on a "normal" box 3. See the result (on attachment) OBSERVED RESULT The text inside the box is huge, you can't even see the signature date without opening the signatures panel or similar on other readers EXPECTED RESULT The complete text (or relevant information) should be presented on the box. User should be able to configure the text size and information shown on the box. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch Linux 6.4.12-arch1-1 KDE Plasma Version: 5.27.7 KDE Frameworks Version: 5.109.0 Qt Version: 5.15.10 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 469253] Record screen feature missing
https://bugs.kde.org/show_bug.cgi?id=469253 --- Comment #2 from Angel Docampo --- (In reply to Nate Graham from comment #1) > In the 23.04 version, Spectacle grew its own screen recording feature in the > app itself when run on Wayland. > > On X11, this feature unfortunately isn't available. The fact that on X11, > Spectacle no longer advertises 3rd-party screen recording apps is > intentional. We were trying to declutter the GUI. Oh, well, I tried Wayland in the past and I had quite a few issues with plasma, so I stayed in X11, which is also fully compatible with steam. I'm not a hardcore gamer, but I don't even shutdown the computer at night, so closing the session on Wayland to re-open it on X11 just to play would be an annoyance. I could try again plasma with Wayland to see how well it behaves. Ok, thank you for the info, Nate. -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 469253] Record screen feature missing
https://bugs.kde.org/show_bug.cgi?id=469253 Angel Docampo changed: What|Removed |Added CC||docampo.an...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 469253] New: Record screen feature missing
https://bugs.kde.org/show_bug.cgi?id=469253 Bug ID: 469253 Summary: Record screen feature missing Classification: Applications Product: Spectacle Version: 23.04.0 Platform: Archlinux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: noaha...@gmail.com Reporter: docampo.an...@gmail.com CC: k...@david-redondo.de Target Milestone: --- SUMMARY Since the upgrade to 23.04.0, the record screen feature is missing. I would like to know if it was intended. I know I can open directly peek, obs or whatever application I like directly by other means, but it was a good way to let the users know cools applications for screen recording. STEPS TO REPRODUCE 1. Open spectacle OBSERVED RESULT No button to screen recording methods are shown. EXPECTED RESULT A dropdown menu like "Export" with screen recording options should be shown, like the old GUI SOFTWARE/OS VERSIONS Linux/KDE Plasma: Archlinux 6.2.13-arch1-1 (64 bits) (available in About System) KDE Plasma Version: 5.27.4 KDE Frameworks Version: 5.105.0 Qt Version: 5.15.9 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 469252] New layout in Spanish shows incomplete text
https://bugs.kde.org/show_bug.cgi?id=469252 Angel Docampo changed: What|Removed |Added CC||docampo.an...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 469252] New: New layout in Spanish shows incomplete text
https://bugs.kde.org/show_bug.cgi?id=469252 Bug ID: 469252 Summary: New layout in Spanish shows incomplete text Classification: Applications Product: Spectacle Version: 23.04.0 Platform: Archlinux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: noaha...@gmail.com Reporter: docampo.an...@gmail.com CC: k...@david-redondo.de Target Milestone: --- Created attachment 158616 --> https://bugs.kde.org/attachment.cgi?id=158616=edit Incomplete text SUMMARY Spectacle 23.04.0 shows a new interface. In Spanish, at least, but perhaps in even more languages, it shows incomplete words as shown in the attached screenshot. Resizing or maximizing the window doesn't do anything, and the right panel isn't resizable either, so, no workaround is possible. STEPS TO REPRODUCE 1. Set the language to Spanish 2. Open spectacle OBSERVED RESULT The words "pantalla" and "captura" are shown incomplete, "pantalla" is shown just as "pa", and "captura" shows "captur" and a half "a". EXPECTED RESULT All the text should be shown completely and with the proper right pan. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Archlinux 6.2.13-arch1-1 KDE Plasma Version: 5.27.4 KDE Frameworks Version: 5.105.0 Qt Version: 5.15.9 ADDITIONAL INFORMATION Screen resolution is 2K (2560x1440) and I'm on X11. -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 462952] Stats missing in bridge mode
https://bugs.kde.org/show_bug.cgi?id=462952 Angel Docampo changed: What|Removed |Added CC||docampo.an...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 462952] New: Stats missing in bridge mode
https://bugs.kde.org/show_bug.cgi?id=462952 Bug ID: 462952 Summary: Stats missing in bridge mode Classification: Plasma Product: plasma-nm Version: 5.26.4 Platform: Archlinux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: applet Assignee: plasma-b...@kde.org Reporter: docampo.an...@gmail.com Target Milestone: --- Created attachment 154534 --> https://bugs.kde.org/attachment.cgi?id=154534=edit applet doen't show stats anymore. SUMMARY Stats (upload and download bandwidth) has disappeared since I've changed my connection from ethernet to a bridged connection. STEPS TO REPRODUCE 1. Change the connection from ethernet to bridge network 2. Transfer something in the background 3. Expand properties on the bridge adapter (see attachment) OBSERVED RESULT No stats are shown EXPECTED RESULT Bandwidth stats show be shown SOFTWARE/OS VERSIONS Linux/KDE Plasma: 6.0.12-arch1-1 KDE Plasma Version: 5.26.4 KDE Frameworks Version: 5.101.0 Qt Version: 5.15.71 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 462951] VPN icon missing when on bridge
https://bugs.kde.org/show_bug.cgi?id=462951 Angel Docampo changed: What|Removed |Added CC||docampo.an...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 462951] New: VPN icon missing when on bridge
https://bugs.kde.org/show_bug.cgi?id=462951 Bug ID: 462951 Summary: VPN icon missing when on bridge Classification: Plasma Product: plasma-nm Version: 5.26.4 Platform: Archlinux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: applet Assignee: plasma-b...@kde.org Reporter: docampo.an...@gmail.com Target Milestone: --- Created attachment 154533 --> https://bugs.kde.org/attachment.cgi?id=154533=edit only way to know if you're connected to a vpn SUMMARY I've recently switched from normal ethernet connection to a bridge connection, in order to configure properly QEMU network. I've noticed the nm applet now has changed its icon to a blue cable, instead of a white cable. So far, no problem with that, and as I can see on this bug report (https://bugs.kde.org/show_bug.cgi?id=361874) it seems it is intended to behave like this. The problem is now, I cannot longer know with a simple glare, if I am connected to a VPN or not, as the lock icon shown before the change, no longer appears. The icon on the applet always shows the same look. STEPS TO REPRODUCE 1. Create a bridge connection 2. Log in into a VPN (I'm using OpenVPN, but I guess any VPN will do the same) OBSERVED RESULT The nm applet icon doesn't change, you don't know just by looking the icon, if you're connected or not, you need to click on the icon and see on the dropdown. (see attachment) EXPECTED RESULT The icon should change to represent you're connected to a VPN, a lock, a shield, or whatever the VPN icon is. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 462950] Navigate items with cursor up leaves an underline
https://bugs.kde.org/show_bug.cgi?id=462950 Angel Docampo changed: What|Removed |Added CC||docampo.an...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 462950] New: Navigate items with cursor up leaves an underline
https://bugs.kde.org/show_bug.cgi?id=462950 Bug ID: 462950 Summary: Navigate items with cursor up leaves an underline Classification: Applications Product: dolphin Version: 22.12.0 Platform: Archlinux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: view-engine: details mode Assignee: dolphin-bugs-n...@kde.org Reporter: docampo.an...@gmail.com CC: kfm-de...@kde.org Target Milestone: --- Created attachment 154532 --> https://bugs.kde.org/attachment.cgi?id=154532=edit moving the selection leaves an uderline SUMMARY Since a while ago (don't remember exactly when) dolphin began to make an annoying flaw. When I navigate through the items on the detailed or compact view, I can move just fine, but when I press the "up" key, it leaves an "underline" on even files of each type (files and directories). This "underline" seems to be a flaw of the selection focused color, which leaves a "trail". See the video attached STEPS TO REPRODUCE 1. Open a dolphin folder with several items on it 2. Change to detailed or compact view 3. go down several items on the list, and then go up OBSERVED RESULT A colored line under even item's name is drawn. Going "down" again, removes the line EXPECTED RESULT No "trail" is expected. SOFTWARE/OS VERSIONS Linux/KDE Plasma: 6.0.12-arch1-1 KDE Plasma Version: 5.26.4 KDE Frameworks Version: 5.101.0 Qt Version: 5.15.7 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 441753] Focused terminal stays in blue
https://bugs.kde.org/show_bug.cgi?id=441753 Angel Docampo changed: What|Removed |Added CC||docampo.an...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 441753] Focused terminal stays in blue
https://bugs.kde.org/show_bug.cgi?id=441753 Angel Docampo changed: What|Removed |Added Platform|Other |Archlinux Packages -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 441753] New: Focused terminal stays in blue
https://bugs.kde.org/show_bug.cgi?id=441753 Bug ID: 441753 Summary: Focused terminal stays in blue Product: yakuake Version: 21.08.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: h...@kde.org Reporter: docampo.an...@gmail.com Target Milestone: --- Created attachment 141152 --> https://bugs.kde.org/attachment.cgi?id=141152=edit yakuake showing the bug SUMMARY After the latest upgrade, when I change the focus to another terminal, the blue highlight stays fixed instead of the normal quick blink. STEPS TO REPRODUCE 1. Set highlight terminals when focus change on yakuake' settings --> Aspect --> General 2. (optional) set "focus terminals when the mouse pointier is over them" 3. Split yakuake and set more than one terminal and change between them, through hotkeys or mouse over them. OBSERVED RESULT Terminal background highlight in blue, but instead of being a quick blink, the blue stays, and if you type, just the line where typing becomes normal (see attached image) EXPECTED RESULT Highlight must be just a quick blink, to let the user know where the focus is. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch Linux KDE Plasma Version: 5.22.4 KDE Frameworks Version: 5.85.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 440128] Yakuake sticks on the activity it was started first
https://bugs.kde.org/show_bug.cgi?id=440128 --- Comment #4 from Angel Docampo --- (In reply to Trevor Parsons from comment #1) > Created attachment 140647 [details] > Window rule settings for Yakuake to appear on all activities > > Workaround by setting a window rule... After restarting, kwin rule got away... so now it's opening on just one activity once again... :| -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 440128] Yakuake sticks on the activity it was started first
https://bugs.kde.org/show_bug.cgi?id=440128 --- Comment #2 from Angel Docampo --- (In reply to Trevor Parsons from comment #1) > Created attachment 140647 [details] > Window rule settings for Yakuake to appear on all activities > > Workaround by setting a window rule... Good one, it worked :) Yet an option under yakuake settings would be great rather than dealing with kwin rules, imo. Thank you, Trevor, for the hint ;) -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 440128] New: Yakuake sticks on the activity it was started first
https://bugs.kde.org/show_bug.cgi?id=440128 Bug ID: 440128 Summary: Yakuake sticks on the activity it was started first Product: yakuake Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: h...@kde.org Reporter: docampo.an...@gmail.com Target Milestone: --- SUMMARY Well, the title says everything. If you have more than one activity and invoke yakuake on one of them, changing to another and invoking yakuake on that activity, it doesn't open on that activity but switches to the activity where yakuake was started and shows it. STEPS TO REPRODUCE 1. Have at least two activities (lest call them A and B) 2. Open yakuake on activity A 3. Switch to activity B 4. Invoke yakuake OBSERVED RESULT Instead of show yakuake on activity B, desktop switches to activity A and shows yakuake on there EXPECTED RESULT Yakuake should be opened on the activity in course. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch Linux KDE Plasma Version: 5.22.3 KDE Frameworks Version: 5.84.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[Ruqola] [Bug 435409] Honor message permissions like edit or delete
https://bugs.kde.org/show_bug.cgi?id=435409 --- Comment #16 from Angel Docampo --- >There is not caching so perhaps you change setting without restart ruqola and >ruqola doesn't react on it but if you relaunch it it will get permission etc >from server. That's exactly what I'm doing. Closing the session but not closing ruqola. When I close and re-open ruqola, permissions and visibility are shown properly More precisely, if I log in first with an unprivileged user and close the session, and re-open with an administrator user, permissions and visibility are shown properly: I can see and edit/delete posts If I do the contrary, close the session with a privileged user and re-open with an unprivileged user, I can see **the last chat where the administrator was connected**, and I'm able to see the "Edit" and "Delete" menu option, yet they throw an error. So the menu re-draws properly from non-privileged to privileged user but not vice-versa, and it happens the same with the conversation chat window: when I log off from an administrator account and log in with an unprivileged user, that unprivileged user sees the chat where the administrator was before the logout (although if he changes to another chat, he cannot see again the administrator chat conversation), but if with that unprivileged user I select a chat room where the administrator has no access and log off, and re-log on with the administrator account, it cannot see that chat. So, it seems re-drawing of the interface works with the admin account at logon time, but with the unprivileged user works at launch time. -- You are receiving this mail because: You are watching all bug changes.
[Ruqola] [Bug 435409] Honor message permissions like edit or delete
https://bugs.kde.org/show_bug.cgi?id=435409 --- Comment #15 from Angel Docampo --- Where should I see debug output? If I invoke ruqola from the command line, the output is the same with and w/o debug options -- You are receiving this mail because: You are watching all bug changes.
[Ruqola] [Bug 435409] Honor message permissions like edit or delete
https://bugs.kde.org/show_bug.cgi?id=435409
--- Comment #13 from Angel Docampo ---
ok, I've compiled with debug, open ruqola and... context menu showed *without*
edit and delete options for the user without permissions...
I logged in back with my user (which is an administrator), and the options were
there, so far so good.
I logged it back with the non-privileged user and the options this time were
shown...
Closing ruqola and open it back, showed the context menu just fine, without the
options.
I think you can reproduce the error by yourself, if not, tell me how to to send
the debug, as in the output I can just see this:
org.kde.rocketchatqtrestapi: "RocketChatRestApi::UpdateMessageJob" error reply:
"Error transferring https://chat.eoniantec.com/api/v1/chat.update - server
replied: Bad Request"
org.kde.rocketchatqtrestapi: errorType "error-action-not-allowed"
org.kde.rocketchatqtrestapi: RESTAPI: "UpdateMessageJob: problem: {\n
\"details\": {\n\"action\": \"Message_editing\",\n\"method\":
\"updateMessage\"\n},\n\"error\": \"Message editing not allowed
[error-action-not-allowed]\",\n\"errorType\":
\"error-action-not-allowed\",\n\"success\": false\n}\n"
--
You are receiving this mail because:
You are watching all bug changes.
[Ruqola] [Bug 435409] Honor message permissions like edit or delete
https://bugs.kde.org/show_bug.cgi?id=435409
--- Comment #11 from Angel Docampo ---
like this?
bool RocketChatAccount::isMessageDeletable(const Message ) const
{
if (!allowMessageDeletingEnabled()) {
return false;
}
if (hasPermission(QStringLiteral("force-delete-message"))) {
return true;
}
if (hasPermission(QStringLiteral("delete-message"))) {
return true;
}
if (message.userId() != userId()) {
return false;
}
if (ruqolaServerConfig()->blockDeletingMessageInMinutes() == 0) { // TODO
verify it
return true;
}
qDebug() << " message.userId() " << message.userId() << " userId() " <<
userId();
return (message.timeStamp() +
ruqolaServerConfig()->blockDeletingMessageInMinutes() * 60 * 1000) >
QDateTime::currentMSecsSinceEpoch();
}
--
You are receiving this mail because:
You are watching all bug changes.
[Ruqola] [Bug 435409] Honor message permissions like edit or delete
https://bugs.kde.org/show_bug.cgi?id=435409 --- Comment #9 from Angel Docampo --- Create Public Channels Create Direct Messages Create Private Channels Create Personal Access Tokens delete-own-message Leave Channels Leave Private Groups Mention All Mention Here Preview Public Channel start-discussion start-discussion-other-user View Public Channel View Direct Messages View History View Outside Room View Private Room -- You are receiving this mail because: You are watching all bug changes.
[Ruqola] [Bug 434963] [feature-request] Jump to mentions
https://bugs.kde.org/show_bug.cgi?id=434963
--- Comment #17 from Angel Docampo ---
This is the backtrace
Application: Ruqola (ruqola), signal: Aborted
[KCrash Handler]
#4 0x7ff32a305ef5 in raise () from /usr/lib/libc.so.6
#5 0x7ff32a2ef862 in abort () from /usr/lib/libc.so.6
#6 0x7ff32a8629ac in QMessageLogger::fatal(char const*, ...) const () from
/usr/lib/libQt5Core.so.5
#7 0x7ff32a861db6 in qt_assert_x(char const*, char const*, char const*,
int) () from /usr/lib/libQt5Core.so.5
#8 0x7ff32ccd244f in QVector::at (this=0x55a8a7b32ed8, i=-3) at
/usr/include/qt/QtCore/qvector.h:449
#9 0x7ff32cccbfcd in MessageModel::messageIdFromIndex
(this=0x55a8a7b32ec0, rowIndex=-3) at
/home/malevolent/development/ruqola/src/core/model/messagemodel.cpp:170
#10 0x7ff32d05e8c1 in operator() (__closure=0x55a8a7c0f440, obj=...) at
/home/malevolent/development/ruqola/src/widgets/room/roomwidget.cpp:571
#11 0x7ff32d060b49 in QtPrivate::FunctorCall,
QtPrivate::List, void,
RoomWidget::slotJumpToUnreadMessage(qint64)::
>::call(struct {...} &, void **) (f=..., arg=0x7ffe96245d70) at
/usr/include/qt/QtCore/qobjectdefs_impl.h:146
#12 0x7ff32d06092b in
QtPrivate::Functor, 1>::call, void>(struct
{...} &, void *, void **) (f=..., arg=0x7ffe96245d70) at
/usr/include/qt/QtCore/qobjectdefs_impl.h:256
#13 0x7ff32d06078e in
QtPrivate::QFunctorSlotObject, 1, QtPrivate::List, void>::impl(int,
QtPrivate::QSlotObjectBase *, QObject *, void **, bool *) (which=1,
this_=0x55a8a7c0f430, r=0x55a8a778a910, a=0x7ffe96245d70, ret=0x0) at
/usr/include/qt/QtCore/qobjectdefs_impl.h:443
#14 0x7ff32aabf996 in ?? () from /usr/lib/libQt5Core.so.5
#15 0x7ff32c7a6cba in
RocketChatRestApi::ChannelHistoryJob::channelHistoryDone (this=0x55a8a88bc580,
_t1=..., _t2=...) at
/home/malevolent/development/ruqola/build/src/rocketchatrestapi-qt5/librocketchatrestapi-qt5_autogen/GKMA37ZLDK/moc_channelhistoryjob.cpp:152
#16 0x7ff32c81d546 in
RocketChatRestApi::ChannelHistoryJob::slotLoadHistoryChannelFinished
(this=0x55a8a88bc580) at
/home/malevolent/development/ruqola/src/rocketchatrestapi-qt5/channels/channelhistoryjob.cpp:60
#17 0x7ff32c81e7ff in QtPrivate::FunctorCall,
QtPrivate::List<>, void, void
(RocketChatRestApi::ChannelHistoryJob::*)()>::call(void
(RocketChatRestApi::ChannelHistoryJob::*)(),
RocketChatRestApi::ChannelHistoryJob*, void**) (f=(void
(RocketChatRestApi::ChannelHistoryJob::*)(RocketChatRestApi::ChannelHistoryJob
* const)) 0x7ff32c81d3ca
,
o=0x55a8a88bc580, arg=0x7ffe96245f80) at
/usr/include/qt/QtCore/qobjectdefs_impl.h:152
#18 0x7ff32c81e782 in QtPrivate::FunctionPointer::call,
void>(void (RocketChatRestApi::ChannelHistoryJob::*)(),
RocketChatRestApi::ChannelHistoryJob*, void**) (f=(void
(RocketChatRestApi::ChannelHistoryJob::*)(RocketChatRestApi::ChannelHistoryJob
* const)) 0x7ff32c81d3ca
,
o=0x55a8a88bc580, arg=0x7ffe96245f80) at
/usr/include/qt/QtCore/qobjectdefs_impl.h:185
#19 0x7ff32c81e6ed in QtPrivate::QSlotObject,
void>::impl(int, QtPrivate::QSlotObjectBase*, QObject*, void**, bool*)
(which=1, this_=0x55a8a8848b40, r=0x55a8a88bc580, a=0x7ffe96245f80, ret=0x0) at
/usr/include/qt/QtCore/qobjectdefs_impl.h:418
#20 0x7ff32aabf996 in ?? () from /usr/lib/libQt5Core.so.5
#21 0x7ff32adcdcd5 in ?? () from /usr/lib/libQt5Network.so.5
#22 0x7ff32aab5142 in QObject::event(QEvent*) () from
/usr/lib/libQt5Core.so.5
#23 0x7ff32b739762 in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() from /usr/lib/libQt5Widgets.so.5
#24 0x7ff32aa8863a in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() from /usr/lib/libQt5Core.so.5
#25 0x7ff32aa8b133 in QCoreApplicationPrivate::sendPostedEvents(QObject*,
int, QThreadData*) () from /usr/lib/libQt5Core.so.5
#26 0x7ff32aae1b04 in ?? () from /usr/lib/libQt5Core.so.5
#27 0x7ff329e5002c in g_main_context_dispatch () from
/usr/lib/libglib-2.0.so.0
#28 0x7ff329ea3b59 in ?? () from /usr/lib/libglib-2.0.so.0
#29 0x7ff329e4d781 in g_main_context_iteration () from
/usr/lib/libglib-2.0.so.0
#30 0x7ff32aae1141 in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/libQt5Core.so.5
#31 0x7ff32aa86f9c in
QEventLoop::exec(QFlags) () from
/usr/lib/libQt5Core.so.5
#32 0x7ff32aa8f454 in QCoreApplication::exec() () from
/usr/lib/libQt5Core.so.5
#33 0x55a8a691ffb1 in main (argc=1, argv=0x7ffe96246608) at
/home/malevolent/development/ruqola/src/apps/widget/main.cpp:132
[Inferior 1 (process 318784) detached]
--
You are receiving this mail because:
You are watching all bug changes.
[Ruqola] [Bug 434963] [feature-request] Jump to mentions
https://bugs.kde.org/show_bug.cgi?id=434963 --- Comment #16 from Angel Docampo --- Created attachment 137598 --> https://bugs.kde.org/attachment.cgi?id=137598=edit jump to first unread crashes ruqola Today I've noticed the banner on top when you have unread messages, unfortunately, it crashes ruqola every time I click on it. -- You are receiving this mail because: You are watching all bug changes.
[Ruqola] [Bug 435409] Honor message permissions like edit or delete
https://bugs.kde.org/show_bug.cgi?id=435409 --- Comment #7 from Angel Docampo --- Created attachment 137597 --> https://bugs.kde.org/attachment.cgi?id=137597=edit showing last chat window In this image, I'm showing how the user test12 just when logs in, can see the content cached where the last user (angel.docampo) was looking at, in this case, the IT channel, where test12 has no access at all. I'm wondering if context menu has some kind of cache as well, and that's why I'm seeing the options -- You are receiving this mail because: You are watching all bug changes.
[Ruqola] [Bug 435409] Honor message permissions like edit or delete
https://bugs.kde.org/show_bug.cgi?id=435409 --- Comment #6 from Angel Docampo --- Created attachment 137596 --> https://bugs.kde.org/attachment.cgi?id=137596=edit editing without permissions -- You are receiving this mail because: You are watching all bug changes.
[Ruqola] [Bug 435409] Honor message permissions like edit or delete
https://bugs.kde.org/show_bug.cgi?id=435409 --- Comment #5 from Angel Docampo --- Created attachment 137595 --> https://bugs.kde.org/attachment.cgi?id=137595=edit trying to delete wihtout permissions -- You are receiving this mail because: You are watching all bug changes.
[Ruqola] [Bug 435409] Honor message permissions like edit or delete
https://bugs.kde.org/show_bug.cgi?id=435409 --- Comment #4 from Angel Docampo --- Created attachment 137594 --> https://bugs.kde.org/attachment.cgi?id=137594=edit context menu with a user who doesn't have edit/delete permissions -- You are receiving this mail because: You are watching all bug changes.
[Ruqola] [Bug 435409] Honor message permissions like edit or delete
https://bugs.kde.org/show_bug.cgi?id=435409 --- Comment #3 from Angel Docampo --- Just removed the test user which I created to make the test, let me create it again and show you. -- You are receiving this mail because: You are watching all bug changes.
[Ruqola] [Bug 435409] Honor message permissions like edit or delete
https://bugs.kde.org/show_bug.cgi?id=435409 --- Comment #1 from Angel Docampo --- In ruqola 1.3.81 beta 2 seems to be improved. Now there are those options to everyone on the context menu, and if the user has permissions, can proceed with edit or deletion, and if the user hasn't the permissions, and error arises when trying to edit or delete a message. I think it would be idea to hide the options from the context menu if the user has no permissions to carry on with them. -- You are receiving this mail because: You are watching all bug changes.
[Ruqola] [Bug 435718] Many incoming webooks are not displayed
https://bugs.kde.org/show_bug.cgi?id=435718
--- Comment #5 from Angel Docampo ---
Do you want the files? I can send them to you, but I'm putting here the text
for a completely empty incoming webhook.
empty content: (sorry, this bugtracking has no markdown support like gitlab)
Received: Message:{
"_id": "Yj3wcLPi2xfr2Gc65",
"_updatedAt": {
"$date": 1617087956309
},
"alias": "",
"attachments": [
{
"channel": "#notifications",
"color": "warning",
"fallback": "Started: RunDeck Job Notification:",
"fields": [
{
"short": true,
"title": "Job Name",
"value":
"<https://rundeck.newlotusweb.net/project/eonian/job/show/ac162ac0-2c51-45a8-a737-b9e419404362|Affiliation/Esmeralda
/ Deploy Special Affiliation Oraculum for Esmeralda FR>"
},
{
"short": true,
"title": "Project",
"value": "eonian"
},
{
"short": true,
"title": "Status",
"value": "Started"
},
{
"short": true,
"title": "Execution ID",
"value":
"<https://rundeck.newlotusweb.net/project/eonian/execution/follow/3724|#3,724>"
},
{
"short": true,
"title": "Options",
"value": "N/A"
},
{
"short": true,
"title": "Started By",
"value": "jordi.vilar"
}
],
"icon_emoji": ":rundeck:",
"title": "RunDeck Job Started",
"ts": "1970-01-01T00:00:00.000Z"
}
],
"bot": {
"i": "CHRkkKgywmGAfG8FD"
},
"channels": [
],
"groupable": false,
"mentions": [
],
"msg": "",
"parseUrls": false,
"rid": "EGpqR23fNnjsTHua4",
"ts": {
"$date": 1617082008028
},
"u": {
"_id": "rocket.cat",
"name": "Rocket.Cat",
"username": "rocket.cat"
}
}
This other is for one showing partially some text
Received: Message:{
"_id": "bGPfZkAePkiCjEKPZ",
"_updatedAt": {
"$date": 1618402509618
},
"alias": "Taiga (Angel Docampo)",
"attachments": [
{
"color": "warning",
"fallback": "*status:* from *Initial tests* to *Done*",
"fields": [
{
"short": true,
"title": "status",
"value": "*From* Initial tests *to* Done"
}
],
"mrkdwn_in": [
"fields",
"title",
"fallback"
],
"ts": "1970-01-01T00:00:00.000Z"
}
],
"bot": {
"i": "nQnpkCztSqnGAXJhj"
},
"channels": [
],
"groupable": false,
"mentions": [
],
"msg": "Changed User Story:
*<https://tasks.eoniantec.com/project/angeldocampo-operations/us/26|#26: Buy
more RAM for the PVE Cluster>*",
"parseUrls": false,
"rid": "mLkrwMQaQ4uYtxvj8",
"ts": {
"$date": 1618402509599
},
"u": {
"_id": "rocket.cat",
"name": "Rocket.Cat",
"username": "rocket.cat"
},
"unread": true
}
And this other is for one removing the links from hyperlinks, or at least,
clicking on them does nothing, and in order to show the message, I have to
click first on the"eye" icon.
Received: Message:{
"_id": "zc2ZEfMBffRgqC6Wz",
"_updatedAt": {
"$date": 1617876860729
},
"alias": "Héctor Rovira",
"attachments": [
{
"color": "#FF",
"text": "Card moved: \"[test1](https://trello.com/c/qErZFThk)\"
from list \"TO-DO reunion' to 'Assigned-Waiting'\n",
"title": "Campagne Manager",
"title_link": "https://trello.com/b/63TFCh20;,
"ts": "1970-01-01T00:00:00.000Z"
}
],
"avatar":
"https://trello-members.s3.amazonaws.com/5d5bf5371f5d565e44d66d72/cefb7644e18a16b25531e09d2d6a5d22/170.png;,
"bot": {
"i": "aAqQRxwHoexx5MzJM"
},
"channels": [
],
"groupable": false,
"mentions": [
],
"msg": "",
"parseUrls": false,
"rid": "EGpqR23fNnjsTHua4",
"ts": {
"$date": 1617874423534
},
"u": {
"_id": "rocket.cat",
"name": "Rocket.Cat",
"username": "rocket.cat"
}
}
--
You are receiving this mail because:
You are watching all bug changes.
[Ruqola] [Bug 435718] Many incoming webooks are not displayed
https://bugs.kde.org/show_bug.cgi?id=435718 --- Comment #3 from Angel Docampo --- Created attachment 137591 --> https://bugs.kde.org/attachment.cgi?id=137591=edit ruqola showing content of trello incoming webhooks removing the link from hyperlinks -- You are receiving this mail because: You are watching all bug changes.
[Ruqola] [Bug 435718] Many incoming webooks are not displayed
https://bugs.kde.org/show_bug.cgi?id=435718 --- Comment #2 from Angel Docampo --- Created attachment 137590 --> https://bugs.kde.org/attachment.cgi?id=137590=edit ruqola showing partial text of the incoming webhook -- You are receiving this mail because: You are watching all bug changes.
[Ruqola] [Bug 435718] Many incoming webooks are not displayed
https://bugs.kde.org/show_bug.cgi?id=435718 --- Comment #1 from Angel Docampo --- Created attachment 137589 --> https://bugs.kde.org/attachment.cgi?id=137589=edit how incoming webhooks are shown on ruqola -- You are receiving this mail because: You are watching all bug changes.
[Ruqola] [Bug 435718] New: Many incoming webooks are not displayed
https://bugs.kde.org/show_bug.cgi?id=435718 Bug ID: 435718 Summary: Many incoming webooks are not displayed Product: Ruqola Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: frontend Assignee: mon...@kde.org Reporter: docampo.an...@gmail.com Target Milestone: --- Created attachment 137588 --> https://bugs.kde.org/attachment.cgi?id=137588=edit wehook on RC SUMMARY We have many incoming webhooks from other services notifying the status of each service (e.g: rundeck, taiga, monit, etc) On ruqola some of them, those which are plain text, seems to work just fine, but there are others which aren't displayed at all, I can just see the bot's name as if it was posting something, but there is nothing or the incoming hook is incomplete. (see attachments) STEPS TO REPRODUCE 1. Configure an incoming webhook for any service, let's say rundeck, netdata, taiga, etc 2. Trigger the webhook OBSERVED RESULT Ruqola doesn't show the content of the webhook in many cases, or just a partial content EXPECTED RESULT Ruqola should show the content of the webhook, at least the plain text part and hyperlinks, there is no need to show images, videos or another fancy stuff, but the text and links are a bare minimal -- You are receiving this mail because: You are watching all bug changes.
[Ruqola] [Bug 435409] New: Honor message permissions like edit or delete
https://bugs.kde.org/show_bug.cgi?id=435409 Bug ID: 435409 Summary: Honor message permissions like edit or delete Product: Ruqola Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: mon...@kde.org Reporter: docampo.an...@gmail.com Target Milestone: --- SUMMARY Ruqola seems not to honor permissions on chat messages for administrators, so as an admin, I cannot delete or edit other user's messages STEPS TO REPRODUCE 1. Log in as an admin or other user with enough permissions to edit or delete messages from other users. 2. Right-click on a message of other user OBSERVED RESULT There is no option to edit or delete message EXPECTED RESULT I should be the options for delete and edit messages -- You are receiving this mail because: You are watching all bug changes.
[Ruqola] [Bug 434963] [feature-request] Jump to mentions
https://bugs.kde.org/show_bug.cgi?id=434963 --- Comment #15 from Angel Docampo --- (facepalm) Sorry, I slept just 4h today, and I'm a bit slow... I never used it before that button. So, how can we jump to the next unread message? Is there a way I'm too sleepy I can't see either? -- You are receiving this mail because: You are watching all bug changes.
[Ruqola] [Bug 434963] [feature-request] Jump to mentions
https://bugs.kde.org/show_bug.cgi?id=434963 --- Comment #13 from Angel Docampo --- Created attachment 137220 --> https://bugs.kde.org/attachment.cgi?id=137220=edit unkwnon icon I don't know how to do it. I noticed an icon which I don't know the meaning, and I thought it could be, but it's disabled -see attachemnt-. I've search on the hotkeys, so see if there were any hotkey for that like for "Jump to Next Unread Channel", but I didn't find it either. -- You are receiving this mail because: You are watching all bug changes.
[Ruqola] [Bug 434963] [feature-request] Jump to mentions
https://bugs.kde.org/show_bug.cgi?id=434963 --- Comment #10 from Angel Docampo --- Created attachment 137191 --> https://bugs.kde.org/attachment.cgi?id=137191=edit cannot see the last unread messages I've scrolled up the chat up to yesterday, and changed to another chat and waited for someone to chat me, the counter of unreaded messages apperared, then I changed back to the chat, but I cannot see how can I jump to the unread messages. What am i doing wrong? -- You are receiving this mail because: You are watching all bug changes.
[Ruqola] [Bug 434963] [feature-request] Jump to mentions
https://bugs.kde.org/show_bug.cgi?id=434963 --- Comment #8 from Angel Docampo --- 50 messages of history? But this won't do even the current day. Yes, seems that if I scroll up to the day someone's mentioned me, forcing ruqola to load more messages from the server, then jumps to the message, but, imo, if I need to scroll up the history, the "Go to mention" feature loses all the utility. Bonus: I've just tried the "Search tool" and it does the same, it shows the results, but I cannot go to the message either, so I guess both are using the same method. I don't know other people, but where I work, jump to -very- old conversations is quite important, that's one of the main reason I convinced the boss to left Skype in favour of RC, because Skype' search was a pain in the **s I'm glad you already have this in your TODO :D -- You are receiving this mail because: You are watching all bug changes.
[Ruqola] [Bug 434965] Read messages count doesn't disappear until you type something
https://bugs.kde.org/show_bug.cgi?id=434965 --- Comment #4 from Angel Docampo --- (In reply to Laurent Montel from comment #3) > Yep it shows the newer. > I want to implement "show last unread message" in the future You mean "first" unread message, I guess. That would be very useful, indeed! -- You are receiving this mail because: You are watching all bug changes.
[Ruqola] [Bug 434963] [feature-request] Jump to mentions
https://bugs.kde.org/show_bug.cgi?id=434963 --- Comment #6 from Angel Docampo --- Nice to know. Anyway "too old" is a message from yesterday? It seems to work just wiht today's metions. -- You are receiving this mail because: You are watching all bug changes.
[Ruqola] [Bug 434963] [feature-request] Jump to mentions
https://bugs.kde.org/show_bug.cgi?id=434963 --- Comment #4 from Angel Docampo --- (In reply to Laurent Montel from comment #2) > you have a show mention dialog =>right click =>go to message damn, I've posted the image and not the comment. It doesn't seem to work on my side -- You are receiving this mail because: You are watching all bug changes.
[Ruqola] [Bug 434963] [feature-request] Jump to mentions
https://bugs.kde.org/show_bug.cgi?id=434963 --- Comment #3 from Angel Docampo --- Created attachment 137084 --> https://bugs.kde.org/attachment.cgi?id=137084=edit mentions go to message does not work -- You are receiving this mail because: You are watching all bug changes.
[Ruqola] [Bug 434965] Read messages count doesn't disappear until you type something
https://bugs.kde.org/show_bug.cgi?id=434965 --- Comment #2 from Angel Docampo --- Well, if people looks nice this behaviour, I'm no one to say the contrary ;) but If I come back from holidays, I'm not gonna read 2 weeks of logs, only if I've been mentioned, I would jump to that message block. I guess the best approach is what Mattermost or even RC does: when you click on a channel, it shows the first unread message and if the user wants to read everything, there is no need to scroll up to the red line, and there is a button to go to the last message and other to mark as read. I think ruqola shows the newer message when you click on a channel, not the older unread, isn't it? Anyway, is nice to know the Esc hotkey trick. -- You are receiving this mail because: You are watching all bug changes.
[Ruqola] [Bug 434965] New: Read messages count doesn't disappear until you type something
https://bugs.kde.org/show_bug.cgi?id=434965 Bug ID: 434965 Summary: Read messages count doesn't disappear until you type something Product: Ruqola Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: frontend Assignee: mon...@kde.org Reporter: docampo.an...@gmail.com Target Milestone: --- Created attachment 137074 --> https://bugs.kde.org/attachment.cgi?id=137074=edit unread messages counter doesn't disappear SUMMARY When you have new messages and read them, the unread messages counter isn't disappearing until you answer on the chat, which I found is not normal, as you have in fact read the messages. STEPS TO REPRODUCE 1. Say someone to chat while you are not in the same channel 2. See how the unread counter shows you have unread messages 3. Enter the chat channel where you have unread messages OBSERVED RESULT Unread messages counter doesn't disappear and channel is still highlighted as if it had unread messages. EXPECTED RESULT Unread messages counter should disappear as soon as you enter the chat, or at least, as soon as you reach the end of the conversation, not just when you send a message back to the channel. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch Linux KDE Plasma Version: 5.21.3 KDE Frameworks Version: 5.80.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[Ruqola] [Bug 434963] [feature-request] Jump to mentions
https://bugs.kde.org/show_bug.cgi?id=434963 --- Comment #1 from Angel Docampo --- Attachment too large, I'm posting a link to see what I'm talking about https://cloud.docampo.net/index.php/s/7K4ipi6RrftnEGK -- You are receiving this mail because: You are watching all bug changes.
[Ruqola] [Bug 434963] New: [feature-request] Jump to mentions
https://bugs.kde.org/show_bug.cgi?id=434963 Bug ID: 434963 Summary: [feature-request] Jump to mentions Product: Ruqola Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: frontend Assignee: mon...@kde.org Reporter: docampo.an...@gmail.com Target Milestone: --- SUMMARY On RC client, you can see where you've been mentioned with a red line on the scroll bar. On ruqola there is no way to see it, just an "@" sign on the chat list says you've N mentions to read, but once you enter the chat, you need to manually scroll up to see the mentions, and look for them reading all the text. STEPS TO REPRODUCE 1. Say somebody to chat you while you are away, if possible, more than once and with quite text between mention and mention 2. After a while, enter in ruqola, and you'll see the chat notification and the at sign with a number in parentheses meaning the number of unread mentions. 3. Enter the chat and look for your mentions manually. OBSERVED RESULT You need to manually scroll up to the red line of unread message and then manually scroll down reading all the messages until you find the mentions EXPECTED RESULT It should be a graphical or automatical way to "jump" to the mentions: a modal window, a key combination (like Ctrl+M... or if you can throttle through mentions Crtr+J for the previous mention, Ctrl+K for the next mention) or it would be awesome (for me at least) if it can be done, a chat preview (like kate's side minipreview) instead of the scrollbar where mentions are highlighted. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch Linux KDE Plasma Version: 5.21.2 KDE Frameworks Version: 5.79.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[Ruqola] [Bug 434765] New: Scroll up on chat history becomes very slow
https://bugs.kde.org/show_bug.cgi?id=434765 Bug ID: 434765 Summary: Scroll up on chat history becomes very slow Product: Ruqola Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: mon...@kde.org Reporter: docampo.an...@gmail.com Target Milestone: --- SUMMARY Often we need to take a look on chat's history, if we remember some sentence of what we talked, we can use the search, but some other times, is faster to just scroll up and re-read the chat log. One of the best things in ruqola is the fact it's blazing fast compared to RC's client, but on this it behaves a quite weird: as more chats are loaded, more sensation of it doing nothing arises. Then some images are drawn, but you cannot scroll up until some time has passed. STEPS TO REPRODUCE 1. select a chat, as more people and messages, the better 2. scroll up with the mouse wheel or by pressing page up OBSERVED RESULT When you have scrolled up quite long, ruqola starts to become, not irresponsive, but it seems it cannot scroll up any longer, you can scroll down change to another chat, come back to the chat you where scrolling up, and nothing. Then , suddendly, it starts to draw some images (if there were any) but you cannot scroll anymore... or at least that's what you think, again, after 30~60s, it loads a bit more of chats and stops again a bunch of seconds. EXPECTED RESULT Some kind of user information should be shown: a message on the status bar (there is no status bar currentlly) showing it's loading older messages, or drawing any kind of text animation on top (a dotted line, or colored line) to let the user there are still older messages to show, or yet better, let the user scroll up to the wanted date and then, print the messages (I guess this cannot be achieved if the API doesn't let do this) SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch Linux KDE Plasma Version: 5.21.2 KDE Frameworks Version: 5.79.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION I think it would be completely awesome, because even the official client doesn't have that option, to put a datepicker and let the user jump directly to a selected date (or the nearest one), more or less like the search tool does. So the user could easily jump to a very old message. I know ruqola depends on the API, but let me dream :P -- You are receiving this mail because: You are watching all bug changes.
[Ruqola] [Bug 434473] Dropdow command list freeze system
https://bugs.kde.org/show_bug.cgi?id=434473 --- Comment #4 from Angel Docampo --- Yes, this must be the ancient X11 bug, I think this will be solved on wayland, afaik. -- You are receiving this mail because: You are watching all bug changes.
[Ruqola] [Bug 434473] Dropdow command list freeze system
https://bugs.kde.org/show_bug.cgi?id=434473 --- Comment #2 from Angel Docampo --- I can confirm it works better now. Desktop effects continue unresponsive (ie: hovering cursor on plasma taskbar or tray icon items doesn't highlight or fire any popup) , but clicking in any item outside the dropdown, collapses the dropdown, which is the normal behaviour on Plasma applications (I think desktop effect should be responsive, but that's not ruqola's fault). :) -- You are receiving this mail because: You are watching all bug changes.
[Ruqola] [Bug 434537] Cannot see an image just pasted
https://bugs.kde.org/show_bug.cgi?id=434537 --- Comment #2 from Angel Docampo --- I've just noticed if I press the "eye" icon to hide/show the image, also works, I was wondering if you can somehow force this behaviour programmatically *before* rendering the image on the chat. -- You are receiving this mail because: You are watching all bug changes.
[Ruqola] [Bug 434534] Need to click "Accept" when pasting an image
https://bugs.kde.org/show_bug.cgi?id=434534 --- Comment #2 from Angel Docampo --- Confirmed, works perfect now. -- You are receiving this mail because: You are watching all bug changes.
[Ruqola] [Bug 434439] commands compatibility
https://bugs.kde.org/show_bug.cgi?id=434439 --- Comment #11 from Angel Docampo --- I had to try :P Telegram has a very nice GUI and feature-wise, and shows awesome QT capabilities -- You are receiving this mail because: You are watching all bug changes.
[Ruqola] [Bug 434537] New: Cannot see an image just pasted
https://bugs.kde.org/show_bug.cgi?id=434537 Bug ID: 434537 Summary: Cannot see an image just pasted Product: Ruqola Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: frontend Assignee: mon...@kde.org Reporter: docampo.an...@gmail.com Target Milestone: --- Created attachment 136779 --> https://bugs.kde.org/attachment.cgi?id=136779=edit demonstration SUMMARY When the user pastes an image, this is now shown completely until he or she types anything else or change the chat window and returning to the chat window where the image was pasted. See attached video to see what I'm speaking about. STEPS TO REPRODUCE 1. Insert an image to the chat window OBSERVED RESULT You cannot see the image thumbnail completely EXPECTED RESULT You should see the image thumbnail completely SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch Linux KDE Plasma Version: 5.21.2 KDE Frameworks Version: 5.79.0 Qt Version: 5.15.2 -- You are receiving this mail because: You are watching all bug changes.
[Ruqola] [Bug 434439] commands compatibility
https://bugs.kde.org/show_bug.cgi?id=434439 --- Comment #9 from Angel Docampo --- A crazy idea just passed to me. I know you will say a categorical "NO" because it must be a giant effort to implement, and I'm not pretty sure it would solve anything of the current issue, but I will tell you anyway, just in case you didn't think about it, and because the interface could solve some other issues like chat grouping or embed videos and preview links and other modern and cool stuff. What about using Telegram desktop UI? Is QT5 and C++, so perhaps is not as crazy idea as it can sound. https://github.com/telegramdesktop/tdesktop -- You are receiving this mail because: You are watching all bug changes.
[Ruqola] [Bug 434534] New: Need to click "Accept" when pasting an image
https://bugs.kde.org/show_bug.cgi?id=434534 Bug ID: 434534 Summary: Need to click "Accept" when pasting an image Product: Ruqola Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: frontend Assignee: mon...@kde.org Reporter: docampo.an...@gmail.com Target Milestone: --- SUMMARY When pasting an image to the chat conversation, a modal window appears to put some description on the image, which may be of use for some people, but we need to click on the Accept button or pressing Tab up to that button. It's not quite user-friendly. STEPS TO REPRODUCE 1. Copy to the clipboard an image 2. The Upload dialog appears with the temporary path already filled 3. Press Enter OBSERVED RESULT Nothing happens EXPECTED RESULT Focus should be on Accept button, instead of Description field, so a user can just paste the image and press enter, in most situations, is what a user wants. In this way, when this upload windows is presented, pressing Escape key will cancel, and Enter key will Accept. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch Linux KDE Plasma Version: 5.21.2 KDE Frameworks Version: 5.79.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION As the upload window is the same for normal file upload, Accept button should make sure first there are something on the File field. -- You are receiving this mail because: You are watching all bug changes.
[Ruqola] [Bug 434474] Honor "real name" setting
https://bugs.kde.org/show_bug.cgi?id=434474 --- Comment #1 from Angel Docampo --- Created attachment 136723 --> https://bugs.kde.org/attachment.cgi?id=136723=edit ruqola doesn't honor Show Real Names setting -- You are receiving this mail because: You are watching all bug changes.
[Ruqola] [Bug 434474] New: Honor "real name" setting
https://bugs.kde.org/show_bug.cgi?id=434474 Bug ID: 434474 Summary: Honor "real name" setting Product: Ruqola Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: frontend Assignee: mon...@kde.org Reporter: docampo.an...@gmail.com Target Milestone: --- Created attachment 136722 --> https://bugs.kde.org/attachment.cgi?id=136722=edit Real Names are shown on RC SUMMARY On RC server there is an option on Settings --> Layout --> User interface that let admin set if you want to show the username or the real name on the chat screen STEPS TO REPRODUCE 1. On RC server, make sure you have enabled Settings --> Layout --> User interface --> Use Real Name OBSERVED RESULT See attachments to compare RC and Ruqola, on RC Real Names ar shown while in ruqola uses the format @username EXPECTED RESULT It should honor the RC server settings. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch Linux KDE Plasma Version: 5.21.2 KDE Frameworks Version: 5.79.0 Qt Version: 5.15.2 -- You are receiving this mail because: You are watching all bug changes.
[Ruqola] [Bug 434473] New: Dropdow command list freeze system
https://bugs.kde.org/show_bug.cgi?id=434473 Bug ID: 434473 Summary: Dropdow command list freeze system Product: Ruqola Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: frontend Assignee: mon...@kde.org Reporter: docampo.an...@gmail.com Target Milestone: --- Created attachment 136721 --> https://bugs.kde.org/attachment.cgi?id=136721=edit Dropdown freezing plasma SUMMARY When you start typing a command or emoji on the chat textbox, and the dropdown appears, Plasma becomes completely unresponsive. STEPS TO REPRODUCE 1. Open a chat 2. Start typing a command (/command or :emotji) OBSERVED RESULT when the dropdown appears, move the mouse and click on any region of the desktop and see how it doesn't respond to clicks, or mouseove. EXPECTED RESULT Desktop shold be responsive, or at least, by left-clicking outisde the dropdown, this should be collapsed and desktop be responsive, as other plasma application does. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch Linux KDE Plasma Version: 5.21.2 KDE Frameworks Version: 5.79.0 Qt Version: 5.15.2 -- You are receiving this mail because: You are watching all bug changes.
[Ruqola] [Bug 434439] commands compatibility
https://bugs.kde.org/show_bug.cgi?id=434439 --- Comment #7 from Angel Docampo --- I'm not a developer, but I'm aware some options are hard to develop in an IRC-like desktop application like ruqola. Perhaps we can tackle most of the scenarios with modals like you're doing to show images and so. By the way, I still didn't thank you for your awesome work! -- You are receiving this mail because: You are watching all bug changes.
[Ruqola] [Bug 434439] commands compatibility
https://bugs.kde.org/show_bug.cgi?id=434439 --- Comment #5 from Angel Docampo --- Hum I should open another issue regarding commands? they not just not autocomplete (by pressing Tab) but also hangs the system for a while if I click on the result dropdown, once ruqola itself had a unexpected closing. -- You are receiving this mail because: You are watching all bug changes.
[Ruqola] [Bug 434439] commands compatibility
https://bugs.kde.org/show_bug.cgi?id=434439 --- Comment #4 from Angel Docampo --- Here you have, some command invocation on ruqola and their counterpart on RC -- You are receiving this mail because: You are watching all bug changes.
[Ruqola] [Bug 434439] commands compatibility
https://bugs.kde.org/show_bug.cgi?id=434439 --- Comment #3 from Angel Docampo --- Created attachment 136694 --> https://bugs.kde.org/attachment.cgi?id=136694=edit same on RC Same tests on official RC client -- You are receiving this mail because: You are watching all bug changes.
[Ruqola] [Bug 434439] commands compatibility
https://bugs.kde.org/show_bug.cgi?id=434439 --- Comment #2 from Angel Docampo --- Created attachment 136693 --> https://bugs.kde.org/attachment.cgi?id=136693=edit commands in ruqola This are the commands in ruqola, first some working as they are just plain text output, then some other with the html preview converted to plain text and finally some others non-working at all -- You are receiving this mail because: You are watching all bug changes.
[Ruqola] [Bug 434439] New: commands compatibility
https://bugs.kde.org/show_bug.cgi?id=434439 Bug ID: 434439 Summary: commands compatibility Product: Ruqola Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: mon...@kde.org Reporter: docampo.an...@gmail.com Target Milestone: --- SUMMARY There are commands (ie. starting with a / ) doesn't work at all: poll, tenor, giphy Other commands like urbandictionary, amazon, etc which usually prints a web link just show some text Text commands like system commands or shrug, tableflip, etc are working STEPS TO REPRODUCE 1. install tenor, poll, amazon,imgur and urban dictionary on RC instance from the Marketplace 2. try to invoke them OBSERVED RESULT None happens EXPECTED RESULT A window to select gifs, images or invoke the poll form should appear SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch Linux KDE Plasma Version: 5.21.2 KDE Frameworks Version: 5.79.0 Qt Version: 5.15.2 -- You are receiving this mail because: You are watching all bug changes.
[Ruqola] [Bug 434380] Search only search on opened chats
https://bugs.kde.org/show_bug.cgi?id=434380 --- Comment #2 from Angel Docampo --- It is curious how there are two "Search Channels" with different meaning: - Search Channel menu searches both on the non-opened users and channels/discussion chats (the later I cannot confirm because I cannot see on the search results the group channels nor discussions I'm on) - Search Channel hotkey searches on the opened list of users, groups and discussions I think those terms are confusing and search hotkey should also search globally as the menu Search Channel does. -- You are receiving this mail because: You are watching all bug changes.
[Ruqola] [Bug 423962] The user needs to retype their password every morning improvement request
https://bugs.kde.org/show_bug.cgi?id=423962 Angel Docampo changed: What|Removed |Added CC||docampo.an...@gmail.com --- Comment #2 from Angel Docampo --- Is working just fine on 1.3.44 alpha, I just had to insert the password on the very first login, yet I also had the Login Failed: invalid username or password' issue, but I closed ruqola and re-opened and since then it always logged in without entering the credentials anymore. -- You are receiving this mail because: You are watching all bug changes.
[Ruqola] [Bug 434380] New: Search only search on opened chats
https://bugs.kde.org/show_bug.cgi?id=434380 Bug ID: 434380 Summary: Search only search on opened chats Product: Ruqola Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: frontend Assignee: mon...@kde.org Reporter: docampo.an...@gmail.com Target Milestone: --- SUMMARY On RC, Ctrl+K searches on all the user's directory, channels, discussions, etc, already opened or not, depending on the visibility of the user's permissions. On ruqola seems to search just in the opened chat list. STEPS TO REPRODUCE 1. Make a search agains for example, a user who you didn't chat yet OBSERVED RESULT You won't find any result, in order to start a chat with a user who you didn't chat before is opening a new channel and invite that user, then, there you will start typing the user's name, and it will autocompleted. EXPECTED RESULT Ctrl+K should search in all the directory of chats, and depending the visibility of each channel will be shown all matching channels/discussions and users. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch Linux KDE Plasma Version: 5.21.2 KDE Frameworks Version: 5.79.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[Ruqola] [Bug 434378] New: Make more visual group ordering setting
https://bugs.kde.org/show_bug.cgi?id=434378 Bug ID: 434378 Summary: Make more visual group ordering setting Product: Ruqola Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: frontend Assignee: mon...@kde.org Reporter: docampo.an...@gmail.com Target Milestone: --- SUMMARY On RC there is a global option under administrator setting on Accounts --> Default user preferences named "Group by type" which populates chat list into the "categories" Favorites, Discussions, Private, Public and Direct, and all chats are grouped there depending on which category it belongs. STEPS TO REPRODUCE 1. Set to true "Group by type" option in RC administrator interface OBSERVED RESULT ON RC Official client chat list are reordered, on ruqola, all chats are "ordered" by the same grouping but no header or some kind of division are shown, so there is almost no use. EXPECTED RESULT Some kind of grouping would be awesome: a collapsable/expandable category name with the belonging chats inside, a header with the division name and a line between categories, the category name and chats belonging to that category tabbed... any graphical option to make easy for the user to know which chat is ever chat SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch Linux KDE Plasma Version: 5.21.2 KDE Frameworks Version: 5.79.0 Qt Version: 5.15.2 -- You are receiving this mail because: You are watching all bug changes.
[Ruqola] [Bug 434377] New: Animated custom icons aren't animated
https://bugs.kde.org/show_bug.cgi?id=434377 Bug ID: 434377 Summary: Animated custom icons aren't animated Product: Ruqola Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: frontend Assignee: mon...@kde.org Reporter: docampo.an...@gmail.com Target Milestone: --- SUMMARY Custom animated emojis (like if they were stickers) uploaded to RC server as gif, are shown as static emojis on ruqola STEPS TO REPRODUCE 1. via official client as an admin, upload a custom emoji, and upload an animated gif 2. type the alias of the emoji, or select it from "custom" on both clients, official and ruqola OBSERVED RESULT Observe the emoji on the official client is the miniature of the emoji you just upload while on ruqola is a (even tinier) static image of that emoji EXPECTED RESULT The emoji shold be animated SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch Linux KDE Plasma Version: 5.21.2 KDE Frameworks Version: 5.79.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION It would be great to use RC emojis instead Plasma emojis (like noto-fonts-emoji) as the user experience is more like if it were using the official one. Besides, on ruqola, there is no option to show "Custom icons", so or the user knows the emoji code, or he won't be able to use it ever. -- You are receiving this mail because: You are watching all bug changes.
[kcalc] [Bug 410231] Calculations history
https://bugs.kde.org/show_bug.cgi?id=410231 --- Comment #1 from Angel Docampo --- Created attachment 121743 --> https://bugs.kde.org/attachment.cgi?id=121743=edit Windows calculator Windows 10 calculator gives an idea of what I'm talking about. -- You are receiving this mail because: You are watching all bug changes.
[kcalc] [Bug 410231] New: Calculations history
https://bugs.kde.org/show_bug.cgi?id=410231 Bug ID: 410231 Summary: Calculations history Product: kcalc Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: ete...@alum.rit.edu Reporter: docampo.an...@gmail.com Target Milestone: --- SUMMARY It would be very useful to have a side panel with the history of calculations made, and thus not have to use the traditional memory buttons. In this way the user can review the calculations made at a single glance, you could even copy the result to the clipboard or use it in the current operation. -- You are receiving this mail because: You are watching all bug changes.
[kdepim] [Bug 408685] I cann't add a ews account
https://bugs.kde.org/show_bug.cgi?id=408685 --- Comment #6 from Angel Docampo --- Also here, after adding the dependency qt5-networkauth, the wizard appears. It doesn't work but that issue is not related to this one. -- You are receiving this mail because: You are watching all bug changes.
[kdepim] [Bug 408685] I cann't add a ews account
https://bugs.kde.org/show_bug.cgi?id=408685 Angel Docampo changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|CONFIRMED CC||docampo.an...@gmail.com --- Comment #1 from Angel Docampo --- Very same behavior here, also with arch linux and with the same versions like OP. -- You are receiving this mail because: You are watching all bug changes.
[parley] [Bug 403488] New: Parley crashes when cancel practice
https://bugs.kde.org/show_bug.cgi?id=403488 Bug ID: 403488 Summary: Parley crashes when cancel practice Product: parley Version: unspecified Platform: Archlinux Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: parley-bugs-n...@kde.org Reporter: docampo.an...@gmail.com Target Milestone: --- Application: parley (18.12.1) Qt Version: 5.12.0 Frameworks Version: 5.54.0 Operating System: Linux 4.20.3-arch1-1-ARCH x86_64 Distribution (Platform): Archlinux Packages -- Information about the crash: Just discovered Parley and thought I could try to see what this software was. So, I created a new profile, selected primary and secondary languages, and click on "Start Practicing". As I didn't know what to do next, I clicked on return to control panel. Then Parley crashes I repeated the process two times more with the very same result. I don't know if I can help anymore, as I said, it was my very first time using this. I've just updated today Arch linux and my kdeapps are on version 18.12.1 I can try in a few hours with other computer, with arch linux as well, to see if I can reproduce this also on it. The crash does not seem to be reproducible. -- Backtrace: Application: Parley (parley), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7f49e32fa440 (LWP 2851))] Thread 4 (Thread 0x7f49d0c2f700 (LWP 2884)): #0 0x7f49f6ae27a4 in read () at /usr/lib/libc.so.6 #1 0x7f49ecd54782 in pa_read () at /usr/lib/pulseaudio/libpulsecommon-12.2.so #2 0x7f49f532155f in pa_mainloop_prepare () at /usr/lib/libpulse.so.0 #3 0x7f49f5321fd1 in pa_mainloop_iterate () at /usr/lib/libpulse.so.0 #4 0x7f49f5322091 in pa_mainloop_run () at /usr/lib/libpulse.so.0 #5 0x7f49f53305ae in () at /usr/lib/libpulse.so.0 #6 0x7f49ecd849fc in () at /usr/lib/pulseaudio/libpulsecommon-12.2.so #7 0x7f49edf08a9d in start_thread () at /usr/lib/libpthread.so.0 #8 0x7f49f6af1b23 in clone () at /usr/lib/libc.so.6 Thread 3 (Thread 0x7f49d9dcd700 (LWP 2853)): #0 0x7f49f6ae6c21 in poll () at /usr/lib/libc.so.6 #1 0x7f49ed7fe540 in () at /usr/lib/libglib-2.0.so.0 #2 0x7f49ed7fe62e in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #3 0x7f49f70195c4 in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x7f49f6fc258c in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #5 0x7f49f6e065c9 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #6 0x7f49f7f5aba6 in () at /usr/lib/libQt5DBus.so.5 #7 0x7f49f6e079cc in () at /usr/lib/libQt5Core.so.5 #8 0x7f49edf08a9d in start_thread () at /usr/lib/libpthread.so.0 #9 0x7f49f6af1b23 in clone () at /usr/lib/libc.so.6 Thread 2 (Thread 0x7f49e1cf4700 (LWP 2852)): #0 0x7f49f6ae6c21 in poll () at /usr/lib/libc.so.6 #1 0x7f49ed523630 in () at /usr/lib/libxcb.so.1 #2 0x7f49ed5252db in xcb_wait_for_event () at /usr/lib/libxcb.so.1 #3 0x7f49e2c3796b in () at /usr/lib/libQt5XcbQpa.so.5 #4 0x7f49f6e079cc in () at /usr/lib/libQt5Core.so.5 #5 0x7f49edf08a9d in start_thread () at /usr/lib/libpthread.so.0 #6 0x7f49f6af1b23 in clone () at /usr/lib/libc.so.6 Thread 1 (Thread 0x7f49e32fa440 (LWP 2851)): [KCrash Handler] #6 0x7f49f8b19088 in KEduVocDocument::identifierCount() const () at /usr/lib/libKEduVocDocument.so.5 #7 0x563e6c11fc8e in () #8 0x7f49f6f76edd in QAbstractItemModel::hasIndex(int, int, QModelIndex const&) const () at /usr/lib/libQt5Core.so.5 #9 0x563e6c0d7870 in () #10 0x563e6c11f26b in () #11 0x563e6c11f491 in () #12 0x7f49f6fec1cb in QObjectPrivate::deleteChildren() () at /usr/lib/libQt5Core.so.5 #13 0x7f49f79c610f in QWidget::~QWidget() () at /usr/lib/libQt5Widgets.so.5 #14 0x7f49f7b3122a in QSplitter::~QSplitter() () at /usr/lib/libQt5Widgets.so.5 #15 0x7f49f6fec1cb in QObjectPrivate::deleteChildren() () at /usr/lib/libQt5Core.so.5 #16 0x7f49f79c610f in QWidget::~QWidget() () at /usr/lib/libQt5Widgets.so.5 #17 0x7f49f79c632a in QWidget::~QWidget() () at /usr/lib/libQt5Widgets.so.5 #18 0x7f49f6fec1cb in QObjectPrivate::deleteChildren() () at /usr/lib/libQt5Core.so.5 #19 0x7f49f79c610f in QWidget::~QWidget() () at /usr/lib/libQt5Widgets.so.5 #20 0x7f49f8978e35 in KMainWindow::~KMainWindow() () at /usr/lib/libKF5XmlGui.so.5 #21 0x563e6c09ab65 in () #22 0x563e6c09ac09 in () #23 0x7f49f6feeb81 in QObject::event(QEvent*) () at /usr/lib/libQt5Core.so.5 #24 0x7f49f79cae8c in QWidget::event(QEvent*) () at /usr/lib/libQt5Widgets.so.5 #25 0x7f49f7ad73a5 in QMainWindow::event(QEvent*) () at /usr/lib/libQt5Widgets.so.5 #26 0x7f49f897b3bc in KMainWindow::event(QEvent*) () at
[knotes] [Bug 324840] sync notes with owncloud notes app
https://bugs.kde.org/show_bug.cgi?id=324840 Angel Docampo changed: What|Removed |Added CC||docampo.an...@gmail.com --- Comment #5 from Angel Docampo --- Well, I was about to suggest this. As per in 2019 I think is a basic feature for a notes application to sync with popular public and private cloud providers, like nextcloud or google drive, to mention one of each. I know it not critical at all, but I would stop using other notes applications if Knotes has some other "modern" features like this. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 393247] KDE tray popup notifications appears twice on dual monitor configuration
https://bugs.kde.org/show_bug.cgi?id=393247 Angel Docampo changed: What|Removed |Added CC||docampo.an...@gmail.com --- Comment #5 from Angel Docampo --- Yes, I can understand to show just one popup in each monitor, but it doesn't make sense to show three popups on each of your three monitors of the very same notification. Its weird. Confirmed this happens since years, I would even say since plasma (I would bet it didn't happened on KDE). I've just opened a new proposal to let the user configure notifications a bit deeper (let's see what plasma devs think about this) https://bugs.kde.org/show_bug.cgi?id=402078 But anyway, I don't even want to imagine what kind of crazy hell must be to have six monitors and transfer a file xD -- You are receiving this mail because: You are watching all bug changes.
[frameworks-knotifications] [Bug 402078] New: Notifications popup in multi-monitor set up configuration
https://bugs.kde.org/show_bug.cgi?id=402078 Bug ID: 402078 Summary: Notifications popup in multi-monitor set up configuration Product: frameworks-knotifications Version: 5.52.0 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdelibs-b...@kde.org Reporter: docampo.an...@gmail.com CC: kdelibs-b...@kde.org Target Milestone: --- Created attachment 116886 --> https://bugs.kde.org/attachment.cgi?id=116886=edit duplicated notification example SUMMARY In those desktops with two o more monitors, and one panel on each, every notification popup is show in each monitor and one notification per monitor (i.e.: if you have three monitors, you'll see three popups on each monitor) by default, which seems a bug to me and has been already reported (https://bugs.kde.org/show_bug.cgi?id=393247) I can disable completely notifications on additional monitor, which is not ideal, because I would like to see what's happening if I have my main monitor with some full screen application overlapping the panel. Or I can hide just system notifications or just transfer notifications on the additional monitors for not to show them on there, which in my opinion, isn't ideal either, because perhaps I would like to see for example file transfer notifications every now and then on that notification system tray. STEPS TO REPRODUCE 1. Put a default panel in each monitor (two monitors minimum) 2. Transfer a set of files and wait to finish OBSERVED RESULT You'll see two notifications in each monitor (if you are on a two-monitor set up) (see attachment) EXPECTED RESULT At least, if you have notifications enabled on all system tray notification widget, you should only see one notification popup in each monitor, not as many popups as monitors SOFTWARE/OS VERSIONS KDE Plasma Version: 5.14.4 KDE Frameworks Version: 5.52.0 Qt Version: 5.11.2 ADDITIONAL INFORMATION I think the ideal notification icon should be managed globally, not per monitor/panel. On notification settings, where now you let to choose the location of the notification popup, I would also add three options: - show in all monitors - show just in main monitor - show the notification of the applications in the current monitor (just like the taskbar does) then, if for example, you want to work on the main monitor with yakuake at full screen, you can beforehand drag the dolphin window to your auxiliary monitor when copying those bunch of files and the notification will be shown on that monitor, even you start the file transfer on your main monitor. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 389902] Android Remote Keyboard cannot input Enter/Return in some contexts
https://bugs.kde.org/show_bug.cgi?id=389902 Angel Docampo changed: What|Removed |Added CC||docampo.an...@gmail.com --- Comment #1 from Angel Docampo --- Can confirm this issue also on Termux (which is very unpleasant) -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 402019] Accents not send to device
https://bugs.kde.org/show_bug.cgi?id=402019 --- Comment #1 from Angel Docampo --- I must say, but, I'm on version 1.10 (beta) on android while on 1.3.3 on desktop, if that matters. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 402019] Accents not send to device
https://bugs.kde.org/show_bug.cgi?id=402019 Angel Docampo changed: What|Removed |Added Version|1.3.3 |1.10 -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 402019] New: Accents not send to device
https://bugs.kde.org/show_bug.cgi?id=402019 Bug ID: 402019 Summary: Accents not send to device Product: kdeconnect Version: 1.3.3 Platform: Other OS: Linux Status: REPORTED Severity: major Priority: NOR Component: common Assignee: albertv...@gmail.com Reporter: docampo.an...@gmail.com Target Milestone: --- SUMMARY KDEConnect's remote keyboard (computer --> mobile device) doesn't seem to send those characters with accent (i.e.: á, é..), so if you send for example the word "clásico", on the device will appear "clsico", omitting the character completely. STEPS TO REPRODUCE 1. Configure plasmoid and device to send keystrokes to the mobile device 2. Open some app with a text field on mobile device, select "KDE Connect Remote Keyboard" 3. Open plasmoid on Plasma desktop, and enter some text on the text field, something with an accent. Send the text OBSERVED RESULT The text sent will appear without the accentuated character EXPECTED RESULT The text sent should appear as written on plasmoid SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch Linux 4.19.4 KDE Plasma Version: 5.14.4 KDE Frameworks Version: 5.52.0 Qt Version: 5.11.2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[print-manager] [Bug 395885] Printer Settings should be saved under user profile, not global CUPS configuration
https://bugs.kde.org/show_bug.cgi?id=395885 --- Comment #4 from Angel Docampo --- Thank you Daniel for your fast answer and kind words. I will tell what you say to whom may concern. -- You are receiving this mail because: You are watching all bug changes.
[print-manager] [Bug 395885] Printer Settings should be saved under user profile, not global CUPS configuration
https://bugs.kde.org/show_bug.cgi?id=395885 Angel Docampo changed: What|Removed |Added CC||docampo.an...@gmail.com --- Comment #2 from Angel Docampo --- Created attachment 113621 --> https://bugs.kde.org/attachment.cgi?id=113621=edit Per user settings override global settings. I would love to provide a patch but I can't because I'm not a developer, and I didn't see the code, but CUPS provide some utilities (lpoptions, lpq, lpstat, lpadmin, and so) which modify the user's printers, without the need to be superuser or root. You need (by default) to be root to add new printers, but CUPS let the user set the default settings for each printer. If you see the attachment, you'll see how I had set the default printer with `lpoptions -d printername` it will set printername as my user's default printer, ignoring the settings I have on the print-manager -kate shows my user's default printer, not the system printer shown on print-manager- as it doesn't look at the user's configuration, but the global's one. I think both home and enterprise users would benefit if print-manager looks onto user's settings to set the printer preferences. -- You are receiving this mail because: You are watching all bug changes.
