[Falkon] [Bug 486028] Content of some (React/Nuxt/NodeJS based?) websites disappear after loaded
https://bugs.kde.org/show_bug.cgi?id=486028 acidrums4 changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |UPSTREAM --- Comment #2 from acidrums4 --- > I dare to say this is due to QtWebEngine in Qt5 being based on Chromium 87 > (or something similar) which is "way too old" for current websites. After being able to download Fedora 40 (while trying to do so is how I remembered abot this!) and installing Falkon on its live session, I can confirm that you were absolutely right - in Falkon 24.* this is not happening at all. Alas KDE6 is still masked on Gentoo so I'm stuck with the "old" QtWebEngine 5.x. I'm marking this as "Resolved upstream" as this was a thing from QtWebEngine. Thank you so much and sorry for the noise. -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 486028] New: Content of some (React/Nuxt/NodeJS based?) websites disappear after loaded
https://bugs.kde.org/show_bug.cgi?id=486028 Bug ID: 486028 Summary: Content of some (React/Nuxt/NodeJS based?) websites disappear after loaded Classification: Applications Product: Falkon Version: 23.08.5 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: grave Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: acidrums4+st...@gmail.com Target Milestone: --- SUMMARY The content in some websites will suddenly disappear after its content is fully loaded, for example: https://fedoraproject.org/workstation/download https://www.olimpica.com/ https://www.specialized.com/ STEPS TO REPRODUCE 1. Open any of the websites aforementioned in Falkon. 2. Wait until they load. OBSERVED RESULT Their content will disappear all of a sudden without any clue (sans the specialized one, where they ask to see the console). EXPECTED RESULT Their content will be shown and the user can see and interact with it normally. SOFTWARE/OS VERSIONS Linux/KDE Plasma: 6.8 KDE Plasma Version: 5.27.11 KDE Frameworks Version: 5.115.0 Qt Version: 5.15.13 ADDITIONAL INFORMATION I could test this behavior on both my daily driver system (Gentoo) and with Fedora on a fresh-out-of-the-box installation. I'll get some weird errors that won't happen on other browsers while interacting with elements of certain websites, i.e. an everhour widget inside a Trello card no longer works due to a "ReferenceError: structuredClone is not defined" error. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 458210] New: Option to create animations with glxanimate is disabled and .rawr/.json animations can't be loaded
https://bugs.kde.org/show_bug.cgi?id=458210
Bug ID: 458210
Summary: Option to create animations with glxanimate is
disabled and .rawr/.json animations can't be loaded
Product: kdenlive
Version: 22.08.0
Platform: Gentoo Packages
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: Video Display & Export
Assignee: j...@kdenlive.org
Reporter: acidrums4+st...@gmail.com
Target Milestone: ---
SUMMARY
Need to incorporate an existing glaxnimate animation into a kdenlive project
_pronto_, but for some reason the option to create an animation and add it to
the project's library is disabled (it shows up but you can't click on it),
though I have set the correct path to the glanimate binary in settings.
Also, kdenlive won't recognize none of `.rawr` or `.json` file formats as valid
(not even trying to import them with the 'all files' setting in the file
chooser dialog). The `.mp4` export is not useful as I need the animation as an
overlay to the project; `.svg` is loaded just as a blank clip into kdenlive
(though it works if you open said file in a web browser) and `.webp` and `.gif`
exports fail within glaxnimate. I reckon this 'load an existing animation'
wasn't intended explicitly as a new feature but I think it doesn't make much
sense being able to create a new animation with glaxnimate but *not* being able
to load an existing animation created with it.
STEPS TO REPRODUCE
1. Open an existing kdenlive project
2. Try to create a new animation ('plus' button in library->'Create animation')
OR try to add a saved glxanimate animation
OBSERVED RESULT
The option to create a new animation is disabled and glaxnimate file formats
are not recognized
EXPECTED RESULT
'Create animation' button is enabled when you set the glaxnimate binary file
path correctly and you can create new animations with it AND correctly load
existing ones
SOFTWARE/OS VERSIONS
Linux: Kernel 5.19.0
KDE Plasma Version: 5.25.4
KDE Frameworks Version: 5.97.0
Qt Version: 5.15.5
--
You are receiving this mail because:
You are watching all bug changes.
[kdenlive] [Bug 436174] Feature Request: Shortcuts for horizontal timeline scrolling
https://bugs.kde.org/show_bug.cgi?id=436174 --- Comment #6 from acidrums4 --- (In reply to emohr from comment #5) > What type of mouse is that? Do you have 2 scroll-wheels? Yup, it's a Logitech MX Master 3. It has a horizontal scroll wheel for the thumb > With the normal mouse wheel you can horizontally scroll Oh Thank you. Dumb me am so used to that thumb horizontal scroll wheel that kind of forgot about the vertical one. Still though I do think it would be nice the timeline supported scrolling with a horizontal scroll wheel. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 436174] Feature Request: Shortcuts for horizontal timeline scrolling
https://bugs.kde.org/show_bug.cgi?id=436174 acidrums4 changed: What|Removed |Added CC||acidrums4+st...@gmail.com --- Comment #4 from acidrums4 --- Not really sure if this is the place to say this or if I should open a new bug, but I wish the timeline supports scrolling with a horizontal mouse wheel, i.e. I have a mouse with one of those and now intuitively use it to scroll horizontally on most KDE stuff but now that I needed to edit a video that ability is notoriously lacking in kdenlive. Which is a bummer, 'cause the only way I found was clicking the scroll handle and dragging it, zooming in/out (!) or directly setting a time in the timeline monitor. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 456730] New: Kcommandbar ("HUD menu") makes Kmail to crash
https://bugs.kde.org/show_bug.cgi?id=456730
Bug ID: 456730
Summary: Kcommandbar ("HUD menu") makes Kmail to crash
Product: kmail2
Version: unspecified
Platform: Gentoo Packages
OS: Linux
Status: REPORTED
Severity: crash
Priority: NOR
Component: UI
Assignee: kdepim-b...@kde.org
Reporter: acidrums4+st...@gmail.com
Target Milestone: ---
SUMMARY
***
Calling Kmail's KCommandbar ("HUD menu") (Ctrl->Alt->I) and trying to select
anything from it, or just by only hovering the cursor over it, makes Kmail to
crash.
***
STEPS TO REPRODUCE
1. Invoke the HUD menu (Ctrl->Alt->I)
2. Type something to filter the available options, or place the cursor over it.
OBSERVED RESULT
Kmail crashes immediately (segfault). When running kmail from the terminal and
doing the procedure mentioned above, it says "KMail got signal 11 (Exiting).
Dead letters dumped." (not using debug symbols, sorry)
EXPECTED RESULT
Kmail should not crash; instead, it will let you select and successfully
activate whatever option you pick from the HUD menu.
SOFTWARE/OS VERSIONS
Linux/KDE Plasma: 5.18.0
KDE Plasma Version: 5.25.3
KDE Frameworks Version: 5.96.0
Qt Version: 5.15.5
--
You are receiving this mail because:
You are watching all bug changes.
[kmail2] [Bug 455861] Kmail is not using detailed notifications
https://bugs.kde.org/show_bug.cgi?id=455861 acidrums4 changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #4 from acidrums4 --- Closing this as seems to be fixed since Plasma 5.25.2 (turned out to be a plasma issue I guess?). Sorry for the noise. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 455863] New: A qml datasource/dataengine for emails (and maybe even other Akonadi stuff, like Akregator's feeds)?
https://bugs.kde.org/show_bug.cgi?id=455863 Bug ID: 455863 Summary: A qml datasource/dataengine for emails (and maybe even other Akonadi stuff, like Akregator's feeds)? Product: Akonadi Version: unspecified Platform: Gentoo Packages OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: acidrums4+st...@gmail.com Target Milestone: --- SUMMARY A thing I actually miss when I had to use Windows back in the day was Gmail Notifier Plus[0], a mini app that sat in the taskbar and notified you for each new mail, giving you the chance to cycle though all new emails, preview them and opening/deleting them. It was immensely useful since one didn't had the need to have a tab opened for gmail every time (or, know, kmail running) - you could pretty much manage your email from that mini app. For a brief moment we had a kind of similar thing in the KDE4 days, whose name I cannot remember. Sadly, since KDE "5" and the migration from Python to QML plasmoids, that ability to interact with kmail was lost and, after getting to know a bit about QML since a couple of years ago, primarly due to not having any datasource/dataengine where to pull email data from. With that in mind I think kmail (and Plasma, in general) are lacking a proper and more complete email notification system. The current one works fine for a single email (well, not very much at this moment[1]) but the thing with the QML datasource/dataengine handicaps any possibility that even a iliterate programmer like me can provide an option for that. So my wish is to have QML datasources/dataengines for more of the stuff Akonadi handles - not only emails but akonadi feeds, contacts, reminders and the like. ADDITIONAL INFORMATION [0] https://github.com/shellscape/Gmail-Notifier-Plus [1] https://bugs.kde.org/show_bug.cgi?id=455861 -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 455861] Kmail is not using detailed notifications
https://bugs.kde.org/show_bug.cgi?id=455861 --- Comment #2 from acidrums4 --- (In reply to Laurent Montel from comment #1) > It shows all info only if you receive one email not multiple emails No, it's not. That is the point of this bug report. -- You are receiving this mail because: You are watching all bug changes.
[kalendar] [Bug 455862] New: Kalendar only shows the Google events I created, but not the ones I was invited to
https://bugs.kde.org/show_bug.cgi?id=455862 Bug ID: 455862 Summary: Kalendar only shows the Google events I created, but not the ones I was invited to Product: kalendar Version: 22.04.2 Platform: Gentoo Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: claudio.cam...@gmail.com Reporter: acidrums4+st...@gmail.com CC: c...@carlschwan.eu Target Milestone: --- SUMMARY For Google Calendar events, Kalendar only shows the events I created, but not the ones I was invited to. Weirdly enough, the "Event Calendar" plasmoid shows them all - no, not with their 'backend', but using the 'PIM events' setting. STEPS TO REPRODUCE 1. Set a Google account to be used with Kalendar/Korganizer 2. Set Kalendar to show the calendars used with the Google account you just set 3. Be invited to a Google Calendar event 4. Create an event in Google Calendar OBSERVED RESULT For the event in the previous step 2, Kalendar won't show anything. Meanwhile, the event created in step 3 will show. EXPECTED RESULT Kalendar will show any Google Calendar event you are invited to, wheter you created it or not. SOFTWARE/OS VERSIONS Linux: 5.18.0 KDE Plasma Version: 5.25.1 KDE Frameworks Version: 5.95.0 Qt Version: 5.15.4 -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 455861] New: Kmail is not using detailed notifications
https://bugs.kde.org/show_bug.cgi?id=455861 Bug ID: 455861 Summary: Kmail is not using detailed notifications Product: kmail2 Version: 5.20.2 Platform: Gentoo Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: acidrums4+st...@gmail.com Target Milestone: --- SUMMARY Prior to 22.04, kmail notified each new email with a complete notification showing the sender, its address, subject and buttons to open and delete the email (setting it to do so in Settings->Accounts->Reception->Detailed new email notification). Now, despite having that setting activated, the new email notification only shows the sender's name. STEPS TO REPRODUCE 1. Setting kmail to show detailed notifications for each new email (Settings->Accounts->Reception->Detailed new email notification) 2. Get a new email. OBSERVED RESULT The notification only shows the sender's name. EXPECTED RESULT Notification will show the data it used to show - sender's name and address, subject, and buttons to open or delete said email. SOFTWARE/OS VERSIONS Linux: 5.18.0 KDE Plasma Version: 5.25.1 KDE Frameworks Version: 5.95.0 Qt Version: 5.15.4 -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 455860] New: Kmail is sending read receipts, despite setting it not to do so
https://bugs.kde.org/show_bug.cgi?id=455860 Bug ID: 455860 Summary: Kmail is sending read receipts, despite setting it not to do so Product: kmail2 Version: 5.20.2 Platform: Gentoo Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: MDN Assignee: kdepim-b...@kde.org Reporter: acidrums4+st...@gmail.com Target Milestone: --- SUMMARY Since 5.20 or maybe even before, kmail is sending read receipts despite setting it not to do so (both with "ignore" and with "ask each time" an clicking "ignore"). Not sure if this comes down to Gmail, as it's the backend for the email accounts I have to use, but the very second I open an email with a read receipt, kmail sends it. STEPS TO REPRODUCE 1. Set kmail to ignore read receipts (Settings->Security->Message Disposition Notifications->Send Policy->Ignore (or ask) 2. Open an email with a read receipt (and click "ignore" if you set "ask" in the previous step) OBSERVED RESULT Kmail will send the read receipt immediately, no matter what setting you have in the first step. EXPECTED RESULT Kmail will never send any read receipt if you set "Ignore" (or "Ask" and you click "ignore" in an email with a read receipt). SOFTWARE/OS VERSIONS Linux: Kernel 5.18.0 KDE Plasma Version: Plasma 5.25.1 KDE Frameworks Version: 5.95.0 Qt Version: 5.15.4 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 438467] On button factor, the whole menu autocloses when circulating though first-level menu items, and second-onward levels show at the center of the screen
https://bugs.kde.org/show_bug.cgi?id=438467 --- Comment #2 from acidrums4 --- Just wanted to add that recently tried the patch proposed in the mentioned merge request, and now globalmenu it's working as expected. Hope to see the final fix in the main branch soon. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kglobalaccel] [Bug 448159] New: [Wayland] Falkon window won't open if firing it with a custom shortcut
https://bugs.kde.org/show_bug.cgi?id=448159 Bug ID: 448159 Summary: [Wayland] Falkon window won't open if firing it with a custom shortcut Product: frameworks-kglobalaccel Version: 5.90.0 Platform: Gentoo Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdelibs-b...@kde.org Reporter: acidrums4+st...@gmail.com Target Milestone: --- SUMMARY *** In Wayland, Falkon won't show up if you fire it with a custom keyboard shortcut set in Settings. In a X session Falkon will launch correctly. *** STEPS TO REPRODUCE 1. Open 'Settings' (or fire the kcm module, kcmshell5 kcm_keys). 2. Set a custom keyboard shortcut to fire Falkon (in my case, [Meta][F]. 3. In Wayland, Press that shortcut to launch Falkon. OBSERVED RESULT Falkon won't show up, though it is launched (ps aux shows it is indeed running, but for some reason its window won't show up). In the Wayland log (.local/share/sddm/wayland-session.log) won't show anything telling (at least for me), but some lines saying Omitting both --window and --windowclass arguments is not recommended Got an error Got an error A new Falkon window will successfully show up if you press your custom keyboard shortcut once Falkon has been launched with another method (Kickoff, krunner...). EXPECTED RESULT Falkon will show up when firing any custom keyboard shortcut you set for it. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Kernel 5.15.13-gentoo KDE Plasma Version: 21.12.1 KDE Frameworks Version: 5.90.0 Qt Version: 5.15.2 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 392693] [wayland] - Blur effect isnt applied under wayland
https://bugs.kde.org/show_bug.cgi?id=392693 acidrums4 changed: What|Removed |Added CC||acidrums4+st...@gmail.com --- Comment #28 from acidrums4 --- Sorry for the noise - blur is not working for me with Wayland here with 5.23 (nor 5.22, nor 5.21, nor 5.20). It works fine with X11. Both blur and background contrast effects are enabled. Still, when using Wayland the only blurred thing I can see is the background of the lock screen. The weird thing is that with my older PC it worked, but not sure why in this one it won't. Using an integrated Intel graphics card. I sincerely don't know what is going on, as this allegedly was fixed - no answers after asking on Reddit, KDE or Gentoo forums. The output of my qdbus org.kde.KWin /KWin supportInformation can be found in https://pastebin.com/YfvcUrnh -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 344027] Synchronise news with feedly
https://bugs.kde.org/show_bug.cgi?id=344027 acidrums4 changed: What|Removed |Added CC||acidrums4+st...@gmail.com --- Comment #7 from acidrums4 --- (In reply to jerryzh0524 from comment #6) > Is there any update on this feature? Alas as with all of this features on the wishlist, this won't be implemented until someone interested and with enough skills and knowledge can step up and take a look at it. But it's been 6+ years since it was reported, so... And this will be a complicated one, because it will mean not only dealing with the Feedly API and KDEPIM/Akonadi thingies, but setting the path so Akregator can have synchronization with other third-party services, and I guess it would mean a huge deal in how Akregator code is structured right now. In top of all of that, there's the fact that RSS popularity has decayed. One can hope that the incoming feature on Chrome about 'reviving' RSS can give it a second chance, but also it seems KDEPIM devs are focused on KMail, the new Kalendar thing and that stuff - maybe someone at some GSoC could take this one, or we can keep it upvoting this bug report and making noise about it so there's more chance of it to be discovered by someone who can do this. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 438467] New: On button factor, the whole menu autocloses when circulating though first-level menu items, and second-onward levels show at the center of the screen
https://bugs.kde.org/show_bug.cgi?id=438467 Bug ID: 438467 Summary: On button factor, the whole menu autocloses when circulating though first-level menu items, and second-onward levels show at the center of the screen Product: plasmashell Version: 5.22.0 Platform: Gentoo Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Global Menu Assignee: k...@privat.broulik.de Reporter: acidrums4+st...@gmail.com CC: mvourla...@gmail.com, plasma-b...@kde.org Target Milestone: 1.0 SUMMARY I find this rather difficult to explain in plain text and can't record the screen because wayland, so I'd do my best. Setting globalmenu in button factor (where it shows itself as a three-bar icon, you click it and the app menu appears) don't work as expected with Wayland. You can move your cursor through the elements of the first level menu (i.e. File, Edit, Preferences...). The second you move the cursor from one menu item to other, the menu autocloses itself, so you have to click the globalmenu button again and go to the desired menu item, being careful enough to not hover over any other menu item. Also, the second-level popup menu (say, for example, the menu items contained by the 'File' menu) shows at the absolute center of the screen. There's a obscure pattern there too, because if you move the cursor in some direction the whole menu will autoclose, but in other way it does not - can't explain how, because I'm not quite sure of how that pattern works. Weird enough, globalmenu works as expected when clicking the globalmenu item and activating the menu items with the keyboard (with cursor keys) or *almost* as expected when setting a global keyboard shortcut for it and activating it via keyboard. Second-onward level menus appear where they're supposed to show up, right next to the first level menu, but when setting a global keyboard shortcut and activating globalmenu with it, sometimes the first level menu will show up with a weird layout where the items show up with center-aligned texts and are not activatable/hoverable. STEPS TO REPRODUCE 1. Add globalmenu to a panel, whether horizontal or vertical, and set it to button factor. 2. Open an app that has appmenu support (say, Dolphin). 3. Click the globalmenu button created in the panel. 4. Hover over a menu item and, if said menu item has a secondary menu, move the cursor to it. 5. Hover over several menu items on the first level. OBSERVED RESULT If (4) has a secondary menu, it will show at the absolute center of the screen. Trying to reach it with the cursor is difficult - if you move the cursor a certain way, the whole menu will close automatically. On (5) the whole menu closes automatically, not letting the user to walk through the secondary items of a menu - you'd need to click globalmenu again, and carefully place the cursor over the desired menu item without hovering over any other item, or the whole menu will close automatically again. EXPECTED RESULT The user can walk through the items of any given menu without needing to activate globalmenu for each menu item, and secondary-onwards levels should show up right next to their parent. As traditional menus do. SOFTWARE/OS VERSIONS Linux: Gentoo x86-64, Kernel 5.12 KDE Plasma Version: 5.22 KDE Frameworks Version: 5.82 Qt Version: 5.15.2 -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 435708] New: Can't see someone else's shared screen
https://bugs.kde.org/show_bug.cgi?id=435708 Bug ID: 435708 Summary: Can't see someone else's shared screen Product: Falkon Version: 3.1.0 Platform: Gentoo Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: now...@gmail.com Reporter: acidrums4+st...@gmail.com Target Milestone: --- SUMMARY When in a Google Meet's meeting, if someone shares their screen so other participants see it, I cannot. The "X is showing their screen" message appears but nothing else. Which is weird, because when someone is using their camera, I can see them. It's just when they share their screen. This is happening to me since december, 2020 - I didn't upgraded qtwebengine neither falkon (obviously, no updates since forever...) so I'm not sure about the reason for this weird issue. STEPS TO REPRODUCE 1. Be in a Google Meet's meeting 2. Someone else shares their screen OBSERVED RESULT Cannot see their screen EXPECTED RESULT See their shared screen SOFTWARE/OS VERSIONS (available in About System) KDE Plasma Version: 5.21.4 KDE Frameworks Version: 5.81.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION Falkon version: 3.1.0 Qtwebengine version: 5.15.2 (plus Gentoo's patches from april 6, 2021, dev-qt/qtwebengine-5.15.2_p20210406) -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 433961] Falkon doesn't allow to share audio and video on Jitsi or Google meet
https://bugs.kde.org/show_bug.cgi?id=433961 acidrums4 changed: What|Removed |Added CC||acidrums4+st...@gmail.com --- Comment #2 from acidrums4 --- (In reply to louicellier.jl from comment #1) > On Google meet, when you start up a meeting, a menu briefly appears about > microphone and camera, but disappears and all you get is a blank page. It is > even impossible to start actually the meeting. With Qt 5.15 (QtWebengine 5.15.2) and Frameworks 5.81 I'm not having issues with audio and it'll allow me to be in meetings, both listening to people and talking. Can't tell about camera because I don't have one. What I can't do is neither share my screen or see other person's shared screen, though up to december 2020 I could see someone else's shared screen, which is the reason I stumbled upon this - to file a bug about that. -- You are receiving this mail because: You are watching all bug changes.
[KDb] [Bug 427047] In plasma-wayland,global menu: Only one menu of an app can be opened on the panel.After that,the other Menus cannot be opened.
https://bugs.kde.org/show_bug.cgi?id=427047 acidrums4 changed: What|Removed |Added Ever confirmed|0 |1 Status|RESOLVED|REOPENED Resolution|FIXED |--- --- Comment #4 from acidrums4 --- alexjp.lene...@gmail.com - Not sure if you even read the little information OP gave or what I wrote, which I think was well explained, but it is definitely *not* what you are saying. I concede OP did reported it in the wrong product but this issue is NOT SOLVED. Right now with Plasma 5.21 and Frameworks 5.80 I'm still having this issue. You can close this as "invalid" if you please, OP's mistake on reporting it on the wrong product is certainly a valid point against making this invalid, and if you do so I will make another one again trying to look up for the right place - but misconstruing the point of a report is not a good way to solve any bug. -- You are receiving this mail because: You are watching all bug changes.
[calligracommon] [Bug 269653] Krita and Karbon always exports PDF with A4 size
https://bugs.kde.org/show_bug.cgi?id=269653 --- Comment #3 from acidrums4 --- Now with Qt 5 this is working - sort of. - You set a document size, other than A4 in Preferences->Page layout - Export your document as PDF (File->Export as PDF) - A dialog appears where you have to set *again* the dimensions of your document. If you don't, it will export it as A4 by default -- You are receiving this mail because: You are watching all bug changes.
[karbon] [Bug 128718] Transforming bitmaps into vector graphics
https://bugs.kde.org/show_bug.cgi?id=128718 --- Comment #9 from acidrums4 --- To this day, Karbon doesn't have any bitmap tracing auxiliar/dock/option/whatever. Hope it can have that. -- You are receiving this mail because: You are watching all bug changes.
[karbon] [Bug 286839] Measurement in pixels/Auto-transform measures in 'Geometry' dock
https://bugs.kde.org/show_bug.cgi?id=286839 --- Comment #6 from acidrums4 --- This is still present, Karbon has no pixel units in its preferences. -- You are receiving this mail because: You are watching all bug changes.
[karbon] [Bug 296749] Boolean operations always return polygons
https://bugs.kde.org/show_bug.cgi?id=296749 --- Comment #5 from acidrums4 --- Not only it is still not working but doing any boolean operation does make the involved shapes to disappear. -- You are receiving this mail because: You are watching all bug changes.
[KDb] [Bug 427047] In plasma-wayland,global menu: Only one menu of an app can be opened on the panel.After that,the other Menus cannot be opened.
https://bugs.kde.org/show_bug.cgi?id=427047 acidrums4 changed: What|Removed |Added CC||acidrums4+st...@gmail.com --- Comment #1 from acidrums4 --- Chiming in because OP didn't provided any additional details but I know what he's talking about. Say you put the global menu plasmoid somewhere in your panel and set it up to show the compact version (where only the three bar icon shows and you click it to show the application's menu). Say then you hover over the 'File' menu, and a submenu appears. At this day, with plasma 5.21, said submenu is still showing up at the absolute center of the screen. It's annoying but still you can use it. Then, say you didn't meant to use something under the 'File' menu but on the 'Edit' one, so you place your mouse over it - the whole menu closes, so you have to click the three bar button, and *carefully* place your mouse over the 'Edit' menu without hovering any other menu, because the whole thing will close itself again. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 432505] New: "Save attachments" does nothing
https://bugs.kde.org/show_bug.cgi?id=432505 Bug ID: 432505 Summary: "Save attachments" does nothing Product: kmail2 Version: 5.16.1 Platform: Gentoo Packages OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: message list Assignee: kdepim-b...@kde.org Reporter: acidrums4+st...@gmail.com Target Milestone: --- SUMMARY The "save attachments" from the contextual menu in the email list view does nothing - though the menu item from the single message view works as expected. STEPS TO REPRODUCE 1. Right-click an email with multiple attachments in the list view. 2. Select "Save attachments..." from the contextual menu. OBSERVED RESULT Nothing happens. EXPECTED RESULT A folder chooser dialog should show up asking where to save the attachments from the selected email, just like it does when selecting "Download attachments" from the single message window. SOFTWARE/OS VERSIONS KDE Plasma: 5.20 KDE Frameworks Version: 5.78 Qt Version: 5.15.2 Kmail version: 5.16.1 (20.12.0) -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 242617] Okular does not play animated pdf files
https://bugs.kde.org/show_bug.cgi?id=242617 acidrums4 changed: What|Removed |Added CC||acidrums4+st...@gmail.com --- Comment #12 from acidrums4 --- This won't work with ConTeXt JS animated files, i.e. the found in http://dl.contextgarden.net/examples/euro-anim/ -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 422741] Crash when trying to open facebook or random websites under Wayland
https://bugs.kde.org/show_bug.cgi?id=422741 --- Comment #1 from acidrums4 --- Just found out that setting QT_QPA_PLATFORM=xcb serves as a workaround. -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 422741] New: Crash when trying to open facebook or random websites under Wayland
https://bugs.kde.org/show_bug.cgi?id=422741 Bug ID: 422741 Summary: Crash when trying to open facebook or random websites under Wayland Product: Falkon Version: 3.1.0 Platform: Gentoo Packages OS: Linux Status: REPORTED Severity: critical Priority: NOR Component: general Assignee: now...@gmail.com Reporter: acidrums4+st...@gmail.com Target Milestone: --- SUMMARY Since Plasma 5.18, Falkon will crash everytime trying to open facebook.com or other websites (not every website), but only when using it under Wayland. Updated today to Plasma 5.19, re-emerged Falkon but it's still crashing. This didn't happened before, it was stable both on X and Wayland. Tried to create a new test user and reproduce and opening it with no extensions (-e), portable mode (-o) and private mode (-i), but on all cases it crashed. It saves a crashlog file, but (I guess it's because my system doesn't have gcc debug symbols) it only says this: Time: wed. jun. 10 07:09:20 2020 Qt version: 5.14.2 (compiled with 5.14.2) Falkon version: 3.1.0 Rendering engine: QtWebEngine == BACKTRACE == #0: falkon(+0x412a) [0x55e4112a712a] #1: /lib64/libc.so.6(+0x3332c387a0) [0x7f7671a437a0] I don't know what else to do. This made me go back to X as Wayland was already my daily driver. Though it's weird I hadn't read about someone else with the same issue anywhere else. STEPS TO REPRODUCE 1. Be under a Wayland session with Plasma 5.18/5.19 2. Open Falkon 3. Open facebook.com OBSERVED RESULT Falkon immediately crashes before the progress bar even reaching its 100% state. EXPECTED RESULT Hmmm... Not crashing? SOFTWARE/OS VERSIONS Linux: Kernel 5.6.0-pf7 (pf-sources) KDE Plasma Version: Plasma 5.19 KDE Frameworks Version: 5.70 Qt Version: 5.14.2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 385595] KWin::WorkspaceWrapper signal clientAdded(KWin::Client *client) doesn't trigger on Wayland
https://bugs.kde.org/show_bug.cgi?id=385595 acidrums4 changed: What|Removed |Added CC||acidrums4+st...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 399808] Dragging an image file into wallpaper picker dialog shows an "not allowed" cursor
https://bugs.kde.org/show_bug.cgi?id=399808 --- Comment #4 from acidrums4 --- (In reply to Nate Graham from comment #3) > I don't see that in 5.16. Can you attach a screen recording that shows the > issue? Sorry for being late, busy at work. Here you go. https://streamable.com/1joo1 BUT you were right - it's fixed... on X11. As I'm already using Wayland as daily diver I hadn't noticed this was fixed for X11. But alas this won't work on Wayland - I can't even record the screen under there, so I can't show you how it goes (pretty much the same, but instead of a "plus" cursor you got a "not-allowed" one). I still do think (apart that this should be fixed for Wayland) that a visual feedback, other than the "plus" cursor (not only here, but say for example, dragging a text file from Dolphin to Kate), would be awesome.https://streamable.com/1joo1 Thank you -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 399808] Dragging an image file into wallpaper picker dialog shows an "not allowed" cursor
https://bugs.kde.org/show_bug.cgi?id=399808 --- Comment #2 from acidrums4 --- (In reply to Nate Graham from comment #1) > Seems to be fixed as of Plasma 5.15.5 and 5.16. I updated to 5.16 last week and tried it (it was time to change to a new wallpaper) - still the same thing... -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 402610] New: Add a subgrid to reference images
https://bugs.kde.org/show_bug.cgi?id=402610 Bug ID: 402610 Summary: Add a subgrid to reference images Product: krita Version: unspecified Platform: Gentoo Packages OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: Tools/Reference Images Assignee: krita-bugs-n...@kde.org Reporter: acidrums4+st...@gmail.com Target Milestone: --- In addition to #396155, I'd love the reference images tool to have a sort of "subgrid" painted over it, based on the main grid that is shown over the artboard (see https://www.artistsnetwork.com/wp-content/uploads/2016/06/drawing-grid-method-Lee-Hammond-061616.jpg as a reference of what I mean). This would be useful for us who are learning to draw by eye, or in general for users who need to draw from reference with some degree of accuracy. -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 399531] No geolocation support
https://bugs.kde.org/show_bug.cgi?id=399531 acidrums4 changed: What|Removed |Added Resolution|WORKSFORME |UPSTREAM --- Comment #2 from acidrums4 --- As a matter of fact, Qt 5.11.3 was added yesterday to Portage's unstable tree and with it this worked - So I'm changing this from "Resolved worksforsome" to "Resolved upstream". -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 399808] New: Dragging an image file into wallpaper picker dialog shows an "not allowed" cursor
https://bugs.kde.org/show_bug.cgi?id=399808 Bug ID: 399808 Summary: Dragging an image file into wallpaper picker dialog shows an "not allowed" cursor Product: plasmashell Version: master Platform: Gentoo Packages OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: Image Wallpaper Assignee: notm...@gmail.com Reporter: acidrums4+st...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 SUMMARY I remember not long agou you couldn't drag an image file (say, from Dolphin) into the wallpaper picker to be able to choose it as a wallpaper. That was fixed but I just recently noticed that, because there is a tiny caveat: while dragging the image file over the wallpaper picker dialog/widget, it will turn the cursor as a "not-allowed" one - but still, if you release the image file there, it will appear as a new option to set a wallpaper. For the sake of usability, I think not only the cursor thing should be fixed (and changed to a default cursor), but there should be some sort of feedback about the ability of that wallpaper picker widget for receiving dragged image files, so users can know they're doing something the widget is able to do - for example, highlighting the widget, turning its background color to a 'selected' or 'highlighted' colour, or something like that. STEPS TO REPRODUCE 1. Right-click your desktop and select "Configure desktop" and select "Desktop wallpaper". It should be configured as "Slideshow" or "Still image" (this happens on those two cases; I don't know how all those buttons and things are actually named in english Plasma releases). 2. Pick an image from your file browser and drag them to the wallpaper widget (the area where available wallpaper images are shown). OBSERVED RESULT Cursor is turned to a "not-allowed" state while dragging an image file over it. EXPECTED RESULT Cursor should keep its "default" state, or something that lets the user know they can drag image files into it. Also, some sort of feedback from the widget should reinforce that idea on users so they can be sure they're doing something allowed and when they can release the image so the widget will catch it (highlighting the widget area, for example). -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 399806] New: "Extract" submenu won't show op on compressed files without extension
https://bugs.kde.org/show_bug.cgi?id=399806 Bug ID: 399806 Summary: "Extract" submenu won't show op on compressed files without extension Product: dolphin Version: 18.08.2 Platform: Gentoo Packages OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: acidrums4+st...@gmail.com CC: elvis.angelac...@kde.org Target Milestone: --- SUMMARY Dolphin can group and correctly identify filetypes for compressed files (.zip, .tar, .7z, .rar...). But for a file that does not have the extension in its filename, and you right-click it, the "Extract" submenu won't appear - but still it will offer to open them with Ark. You have to manually add an extension to that file to be able to get that submenu via right click. I've noticed this happens on .zip, .tar.gz and .rar files - maybe on other filetypes happens, too. So my suggestion is that the conditional to make this submenu appears should be based on whatever Dolphin uses to identify filetypes (magic numbers and that stuff) instead of file extensions. STEPS TO REPRODUCE 1. Get a compressed file without extension in its name (rename an existing file deleting its extension, download a master branch of some project from GitHub...) 2. Right-click on it. OBSERVED RESULT "Extract" submenu does not show up on the listed options. EXPECTED RESULT "Extract" submenu should appear for those files, regardless of their extension on their filename but according to whatever file type Dolphin retrieves for said files. -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 399531] New: No geolocation support
https://bugs.kde.org/show_bug.cgi?id=399531 Bug ID: 399531 Summary: No geolocation support Product: Falkon Version: unspecified Platform: Gentoo Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: now...@gmail.com Reporter: acidrums4+st...@gmail.com Target Milestone: --- I'm using Falkon 3.0.1 with QtWebEngine 5.11.1 on Gentoo/Linux. Geolocation is still not working. For example, https://html5demos.com/geo/ will keep forever on "checking" (on private mode it will return "failed", even with the do not track flag disabled (since there's still no web inspector (...), can't tell anything else about this). On the same machine, geolocation works on Firefox 52. I guess this has to be something related to upstream, though, because it seems Falkon is not the only Qt browser where geolocation is not working (https://www.reddit.com/r/qutebrowser/comments/8fquv8/geolocation_doesnt_work/) despite support for it was added on qt upstream since 5.5 (https://doc.qt.io/qt-5/qtwebengine-features.html#html5-geolocation). -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 397251] Unable change desktop or lockscreen wallpapers
https://bugs.kde.org/show_bug.cgi?id=397251 acidrums4 changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |INVALID --- Comment #6 from acidrums4 --- (In reply to David Edmundson from comment #5) > > kpluginindex.json > > try either deleting this or running sudo kpackagetool5 --generate-index -g It did it! Thank you so much :) > And if you can read gentoo packaging to see if the emerge is calling > something like that last line explicitly that would be much appreciated. > It's not from any KDE code. Well, I just did: grep -r kpackagetools5 /usr/portage grep -r kpackagetools5 /var/lib/layman/kde grep -r kpluginindex.json /usr/portage grep -r kpluginindex.json /var/lib/layman/kde and all of them returned nothing. Not sure if that's what you meant but I guess it didn't came from any KDE ebuild but rather from an plasma widget I got from the store quite time ago. However, than you so much for your help. Leaving this as invalid, as I could finally confirm this wasn't related to upstream. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 397251] Unable change desktop or lockscreen wallpapers
https://bugs.kde.org/show_bug.cgi?id=397251 --- Comment #4 from acidrums4 --- (In reply to David Edmundson from comment #1) > Please include: > - a screenshot > - ls of /usr/share/plasma/wallpapers Thank you so much for your quick answer. Here's the ls output: ls -alLh /usr/share/plasma/wallpapers total 40K drwxr-xr-x 6 root root 124 ago 7 16:46 . drwxr-xr-x 11 root root 4,0K may 12 2017 .. -rw-r--r-- 1 root root 33K nov 4 2017 kpluginindex.json drwxr-xr-x 3 root root 101 ago 7 07:02 org.kde.color drwxr-xr-x 4 root root 87 ago 7 07:02 org.kde.image drwxr-xr-x 3 root root 64 jul 14 07:02 org.kde.plasma.worldmap drwxr-xr-x 3 root root 64 ago 7 07:02 org.kde.slideshow -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 397251] Unable change desktop or lockscreen wallpapers
https://bugs.kde.org/show_bug.cgi?id=397251 --- Comment #3 from acidrums4 --- Created attachment 114367 --> https://bugs.kde.org/attachment.cgi?id=114367=edit Screenshot from Settings->Desktop behavior->Lockscreen->Visual -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 397251] Unable change desktop or lockscreen wallpapers
https://bugs.kde.org/show_bug.cgi?id=397251 --- Comment #2 from acidrums4 --- Created attachment 114366 --> https://bugs.kde.org/attachment.cgi?id=114366=edit Screenshot from right-click->Desktop settings->Desktop wallpaper -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 397251] New: Unable change desktop or lockscreen wallpapers
https://bugs.kde.org/show_bug.cgi?id=397251 Bug ID: 397251 Summary: Unable change desktop or lockscreen wallpapers Product: plasmashell Version: 5.13.3 Platform: Gentoo Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Image Wallpaper Assignee: notm...@gmail.com Reporter: acidrums4+st...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 (Reporting as a bug as I got no help on forums). >From 5.12 onwards, every time I right-click on the desktop or try to change lockscreen wallpaper, the"Wallpaper type" (or what is says in english) selection widget has no options. I tried creating a whole new user on my system, but from there the thing is the same. Expected results: Being able to select "static image", "color" and etc (and being able to select an image when selecting "static image") when changing lockscreen and desktop wallpapers. Still I can change desktop wallpaper by dragging an image file from Dolphin. Alas I don't know if there's a similar workaround for changing the lock screen wallpaper. The output of plasmashell can be found here (there are some weird things there, but I don't know if they're relevant to this): https://pastebin.com/w2rcTadT OS: Gentoo amd64 Plasma 5.13 & Frameworks 5.48 from the KDE overlay. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 385280] digikam does not use the native Plasma file dialog under Plasma
https://bugs.kde.org/show_bug.cgi?id=385280 --- Comment #9 from acidrums4 <acidrums4+st...@gmail.com> --- (In reply to Maik Qualmann from comment #8) > Did you activate the option for the native file dialog in the digiKam > Setup-> Miscellaneous? Sweet mother of Qt, I'm so embarrased. I didn't noticed that. Thank you so much :) -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 385280] digikam does not use the native Plasma file dialog under Plasma
https://bugs.kde.org/show_bug.cgi?id=385280 acidrums4 <acidrums4+st...@gmail.com> changed: What|Removed |Added CC| |acidrums4+st...@gmail.com --- Comment #7 from acidrums4 <acidrums4+st...@gmail.com> --- Hmmm... At least for me with Digikam 5.9 (updated yesterday), both Digikam (at least when selecting a location for a local collection) and Showfoto (on opening/saving images) are using the default Qt selection dialog rather than Plasma one... This is under Gentoo. I'm not switching this bug to "reopened" (it would be rude from my part) but hope you take a closer look on this. I really hoped this was fixed on 5.8, but as 5.9 arrived and it's still the same... -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 375053] enabling global menu breaks copy/paste shortcuts in qupzilla
https://bugs.kde.org/show_bug.cgi?id=375053 --- Comment #17 from acidrums4 <acidrums4+st...@gmail.com> --- Weirdly enough, this was solved for me with today's update on Qupzilla (2.2.4). It feels like Global Menu wasn't the only one to blame... -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 375053] enabling global menu breaks copy/paste shortcuts in qupzilla
https://bugs.kde.org/show_bug.cgi?id=375053 acidrums4 <acidrums4+st...@gmail.com> changed: What|Removed |Added CC| |acidrums4+st...@gmail.com --- Comment #15 from acidrums4 <acidrums4+st...@gmail.com> --- Though it's been marked resolved, I can still reproduce this, despite using plasma-workspace-5.11.4, Qupzilla 2.2.3 and Qt 5.9.3 (on a Gentoo amd64 box). The `KDE_NO_GLOBAL_MENU=1 qupzilla` did worked for me, though. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 387561] Krita won't use KDE's color scheme
https://bugs.kde.org/show_bug.cgi?id=387561 --- Comment #3 from acidrums4 <acidrums4+st...@gmail.com> --- Sorry, but though I barely understand the technical reasons behind, I don't get why you're marking this as "wontfix" nor why you're saying "this isn't a bug but a feature". Many other "cross platform" Non-KDE-but-Qt apps will obey KDE color schemes (say Scribus, VLC, Otter...) and you're doing efforts to make Krita integrated with other DE/OS. Why are you leaving KDE behind on this? I mean, at least the option to select those user color schemes would be great. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 387560] Krita won't use KDE file dialog within KDE
https://bugs.kde.org/show_bug.cgi?id=387560 acidrums4 <acidrums4+st...@gmail.com> changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |INVALID --- Comment #3 from acidrums4 <acidrums4+st...@gmail.com> --- Didn't knew about that option under Krita's settings. Activated, KDE file dialogs are back. Thanks! I'm marking by myself this bug as "resolved invalid" but still I'm curious about the "KDE platform integration plugin". Where can I get that? Why isn't it shipped with the Gentoo ebuild? -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 387561] New: Krita won't use KDE's color scheme
https://bugs.kde.org/show_bug.cgi?id=387561 Bug ID: 387561 Summary: Krita won't use KDE's color scheme Product: krita Version: 3.3.2 Platform: Gentoo Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: General Assignee: krita-bugs-n...@kde.org Reporter: acidrums4+st...@gmail.com Target Milestone: --- Since 3.0.0 release, Krita won't use the color scheme set on KDE's "Settings" - nor won't let you select a custom/user color scheme that wasn't shipped with KDE. For example, if you downloaded another color scheme from KDE's "Settings" and you set it so KDE will use it among KDE apps, Krita won't use it - even it won't list it under Krita -> Settings -> Themes so you can pick it from there. That will happen if you created a custom KDE color scheme and place it under ~/.kde4/share/apps/color-schemes/ (Frameworks 5 is still using that folder to load/save custom color schemes). -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 387560] New: Krita won't use KDE file dialog within KDE
https://bugs.kde.org/show_bug.cgi?id=387560 Bug ID: 387560 Summary: Krita won't use KDE file dialog within KDE Product: krita Version: 3.3.2 Platform: Gentoo Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: General Assignee: krita-bugs-n...@kde.org Reporter: acidrums4+st...@gmail.com Target Milestone: --- On recent releases (I seem to recall 3.0.x won't have this issue), Krita won't use KDE file dialog within KDE Frameworks 5 to open/save files, import layers and stuff like that, but default Qt file dialog. Which is pretty annoying - no previews, no bookmarks, no KIO... Right now I'm under Gentoo GNU/Linux with KDE Frameworks 5.40, and Krita was emerged with Qt 5.9.2. Let me know if you need something from my part. :) -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 361811] Krita forces use of Fusion theme even in a KDE session
https://bugs.kde.org/show_bug.cgi?id=361811 --- Comment #9 from acidrums4 <acidru...@gmail.com> --- (In reply to Boudewijn Rempt from comment #7) > I have to admit I'm actually not sure who the breeze style maintainer is and > whether there's a mailing list for it. Well, as a former KDE VDG member I seem to recall someone there came up with Breeze widget style, hacking what Oxygen widget style was at that time. So I created a post on KDE VDG forum, linking this bug report there and linking that post here, hoping he/she/they can read it and get in touch with you, maybe via this bug report. https://forum.kde.org/viewtopic.php?f=285=133587 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 361811] Krita forces use of Fusion theme even in a KDE session
https://bugs.kde.org/show_bug.cgi?id=361811 acidrums4 <acidru...@gmail.com> changed: What|Removed |Added CC||acidru...@gmail.com --- Comment #6 from acidrums4 <acidru...@gmail.com> --- (In reply to Christoph Feck from comment #5) > Would it be possible to check if a "-style" argument was passed? As far as I remember, on "KDE 4" you could pass a "--style" argument, but seems that was ditched for Frameworks 5 - which for this specific case is sad, because Krita's not only ignoring the environment widget style but also the color scheme (and we don't even know why the other styles are "broken" so Fusion style had to be hardcoded). -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 357708] krita fails to build against qt built with OpenGLES support
https://bugs.kde.org/show_bug.cgi?id=357708 acidrums4 <acidru...@gmail.com> changed: What|Removed |Added CC||acidru...@gmail.com --- Comment #2 from acidrums4 <acidru...@gmail.com> --- I'm facing this same issue with the stable Krita 3.0 on Gentoo/GNU Linux, with both GLES and OpenGL USE flags enabled. Compilation fails because it finds using Qt with GLES. As far as Krita 2.9, GLES was supported. Don't get why now on 3.0 it isn't. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 334080] kdeconnect,some sent photo are uncomplete
https://bugs.kde.org/show_bug.cgi?id=334080 acidrums4 <acidru...@gmail.com> changed: What|Removed |Added CC||acidru...@gmail.com --- Comment #34 from acidrums4 <acidru...@gmail.com> --- I'm facing this very issue with kdeconnect-0.9g, CM12 and KDE Frameworks 5. The transfer of pictures I sent from my phone to pc (or viceversa) never ends (sometimes a transfer of a picture actually end, but neither the pc or the phone "notice" that). -- You are receiving this mail because: You are watching all bug changes.
[telepathy] [Bug 353901] Add support for Facebook chat using Whatsapp-purple
https://bugs.kde.org/show_bug.cgi?id=353901 --- Comment #2 from acidrums4 <acidru...@gmail.com> --- (In reply to acidrums4 from comment #1) > I guess everyone here knows this, but on the remote case someone don't: > there's also a facebook plugin for bitlbee that is working right now > (https://github.com/bitlbee/bitlbee-facebook). Maybe the solution hadn't > necessarily involve the purple mechanism. I don't know which of them would > be more reliable, but it's just to have the bitlbee one in mind. > > I agree too about this and the whatsapp thing (As far as I know, Bitlbee is > planning to support Whatsapp on its core, and there's some python plugin for > it since a few months) are holding me back to use KTP, since I of the > services it supports I just have GTalk/Hangouts. And seems many people are > in this situation, too. Oh, and seems someone was doing a Telepathy-Qt connection manager for KTP already, but abandoned: https://github.com/WeedBilbaoGaming/KtP-facebook-GraphAPI -- You are receiving this mail because: You are watching all bug changes.
[telepathy] [Bug 353901] Add support for Facebook chat using Whatsapp-purple
https://bugs.kde.org/show_bug.cgi?id=353901 acidrums4 <acidru...@gmail.com> changed: What|Removed |Added CC||acidru...@gmail.com --- Comment #1 from acidrums4 <acidru...@gmail.com> --- I guess everyone here knows this, but on the remote case someone don't: there's also a facebook plugin for bitlbee that is working right now (https://github.com/bitlbee/bitlbee-facebook). Maybe the solution hadn't necessarily involve the purple mechanism. I don't know which of them would be more reliable, but it's just to have the bitlbee one in mind. I agree too about this and the whatsapp thing (As far as I know, Bitlbee is planning to support Whatsapp on its core, and there's some python plugin for it since a few months) are holding me back to use KTP, since I of the services it supports I just have GTalk/Hangouts. And seems many people are in this situation, too. -- You are receiving this mail because: You are watching all bug changes.
