[okular] [Bug 407579] New: Bad behavior of RadioButton groups in Optional Contents
https://bugs.kde.org/show_bug.cgi?id=407579 Bug ID: 407579 Summary: Bad behavior of RadioButton groups in Optional Contents Product: okular Version: 1.6.3 Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: PDF backend Assignee: okular-de...@kde.org Reporter: edouard.ca...@univ-rennes1.fr Target Milestone: --- Created attachment 120100 --> https://bugs.kde.org/attachment.cgi?id=120100&action=edit PDF 1.5 Standard Compliant example using RBGroups SUMMARY When using RBGroups (RadioButton groups) of Optional Contents, we can switch from one group to another one in the "layers" panel of okular, but the drawing of the corresponding graphic objects is not updated. STEPS TO REPRODUCE 1. open the attached file "Labels_and_Languages_3_OC.pdf" 2. open the "layers" panel 3. open the "Language" group 4. switch from one language to another OBSERVED RESULT The switching between languages in the user interface is correct (mutually exclusive Optional Contents is implemented via the RadioButton group) but the display is not updated: texts are overwritten on the display. EXPECTED RESULT Each language should lead to different text strings. SOFTWARE/OS VERSIONS Linux distro: Ubuntu-19.04 (and before) Okular version: 1.6.3 PDF Backend: 0.6.5 KDE Framework: 5.56.0 Qt version: 5.12.2 ADDITIONAL INFORMATION The PDF has been generated by my own graphic library Muesli. You can open the attached PDF file with any text editor since it uses only ASCII characters. To my knowledge, it is standard compliant: 'mupdf' doesn't claim about any errors, and the "PDF Tools Online" validator (https://www.pdf-online.com/osa/validate.aspx) returns nothing special about it: Validating file "Labels_and_Languages_3_OC.pdf" for conformance level pdf1.5 The document does conform to the PDF 1.5 standard. Done. -- You are receiving this mail because: You are watching all bug changes.
[xdg-desktop-portal-kde] [Bug 406672] Application startup delay with KDE runtime
https://bugs.kde.org/show_bug.cgi?id=406672 Jan Grulich changed: What|Removed |Added CC||ahay...@gmail.com --- Comment #4 from Jan Grulich --- *** Bug 407572 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[xdg-desktop-portal-kde] [Bug 407572] Flatpaks using org.kde.Platform take minutes to launch on Kubuntu 19.04
https://bugs.kde.org/show_bug.cgi?id=407572 Jan Grulich changed: What|Removed |Added CC||jgrul...@redhat.com Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED --- Comment #1 from Jan Grulich --- *** This bug has been marked as a duplicate of bug 406672 *** -- You are receiving this mail because: You are watching all bug changes.
[kile] [Bug 407578] New: Correct display of Latex compilation error with math in align environment
https://bugs.kde.org/show_bug.cgi?id=407578
Bug ID: 407578
Summary: Correct display of Latex compilation error with math
in align environment
Product: kile
Version: 2.9.92
Platform: Archlinux Packages
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: general
Assignee: michel.lud...@kdemail.net
Reporter: ch...@sunderhauf.net
Target Milestone: ---
Kile doesn't parse a LaTeX error message correctly.
Minimal example:
\documentclass{article}
\usepackage{amsmath}
\begin{document}
\begin{align}
\limit % the correct command would be \lim
\end{align}
\end{document}
In the Messages pane, the clickable link for the error says
"tmp.tex:6:Undefined control sequence \end{align}", while actually the problem
is the \limit
However the LaTeX output contains
! Undefined control sequence.
\limit
l.6 \end{align}
It would be helpful for Kile to parse the error message better. On a side note,
the text in the messages pane is not selectable (nor copy-pasteable).
Note that using an equation environment instead of align, the error is
displayed correctly.
--
You are receiving this mail because:
You are watching all bug changes.
[korganizer] [Bug 407577] Passwords containing certain non-ASCII characters not communicated correctly
https://bugs.kde.org/show_bug.cgi?id=407577 --- Comment #2 from Laurent Montel --- I don't have a caldav server for testing it... -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 407577] Passwords containing certain non-ASCII characters not communicated correctly
https://bugs.kde.org/show_bug.cgi?id=407577 Laurent Montel changed: What|Removed |Added CC||mon...@kde.org --- Comment #1 from Laurent Montel --- Sorry for the moment I can't test it as I don't have server support -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 406572] Hotkey and Brush Preset search bug
https://bugs.kde.org/show_bug.cgi?id=406572 Bug Janitor Service changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #3 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 396488] Hovering with Pen Tablet
https://bugs.kde.org/show_bug.cgi?id=396488 Bug Janitor Service changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #4 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 407023] KDNLIVE crash. It's go out.
https://bugs.kde.org/show_bug.cgi?id=407023 --- Comment #3 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 407494] Stock price updating slow
https://bugs.kde.org/show_bug.cgi?id=407494 --- Comment #5 from bren...@coupeware.com --- When I updated stocks from Yahoo tonight the update was extremely fast. I tried it from both computers and they were both fast. Both are running KMM from the 5.0 branch from about 2 weeks ago and both were slow until tonight. Since nothing changed in KMM this appears to be a Yahoo (Verizon) problem. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 385976] Pressing enter to crop does not work consistently
https://bugs.kde.org/show_bug.cgi?id=385976 vanyossi changed: What|Removed |Added CC||ghe...@gmail.com --- Comment #3 from vanyossi --- This works as expected in master (b1ac484) in macOS, maybe this was a bug on earlier versinos. On big images the action to recover the image is visible, but the tool never stops working correctly -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 400770] Erratic Kmail filtering (startup problem?)
https://bugs.kde.org/show_bug.cgi?id=400770 --- Comment #7 from David Lochrin --- (In reply to David Lochrin from comment #1) > But sometimes two copies of the email go to the Link mailbox, one which > seems perfectly OK and a second which has no bodypart, is permanently > flagged as "unread", and cannot be deleted. Other effects are > unpredictable; I have an instance now where the same two copies also > appeared in the scratch folder but the copy with a blank bodypart was > successfully deleted. This problem still occurs, and it's extremely annoying to the point where I'm considering ditching Kmail altogether. The obvious problem can be fixed by renaming the Kmail folder, creating a new folder with the original name, moving all emails except the offending one(s) to the new folder, deleting the renamed folder, and finally re-specifying the folder in the relevant filter. However I have no idea in what state this leaves the Kmail database. The problem cannot be solved by running the Kmail database utility. Is there any plan for fixing it? -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 407577] Passwords containing certain non-ASCII characters not communicated correctly
https://bugs.kde.org/show_bug.cgi?id=407577 mds_f...@protonmail.com changed: What|Removed |Added CC||mds_f...@protonmail.com -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 407577] New: Passwords containing certain non-ASCII characters not communicated correctly
https://bugs.kde.org/show_bug.cgi?id=407577 Bug ID: 407577 Summary: Passwords containing certain non-ASCII characters not communicated correctly Product: korganizer Version: unspecified Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: groupware Assignee: kdepim-b...@kde.org Reporter: mds_f...@protonmail.com Target Milestone: --- Created attachment 120099 --> https://bugs.kde.org/attachment.cgi?id=120099&action=edit Error message upon testing the connection SUMMARY KOrganizer does not seem to communicate passwords containing certain non-ASCII characters correctly when communicating to a CalDAV server. In this case, a stable Nextcloud instance was used. STEPS TO REPRODUCE 1. Add Calendar 2. Select "DAV groupware resource" 3. Fill in the username 4. Type in a password with certain non-ASCII characters, like 'ö', select "Next" 5. In "Use one of those servers" select "Nextcloud" 6. Fill in the correct host data 7. On the next dialog, click the "Test Connection" button OBSERVED RESULT Upon testing the connection, the error with the following error message occurs: "An error occurred: There was a problem with the request. Invalid username/password (401)." EXPECTED RESULT The login data should be accepted. SOFTWARE/OS VERSIONS Linux kernel: 5.1.2 KOrganizer: 5.11.1 KDE Plasma Version: 5.15-1 KDE Frameworks Version: 5.58.0 Qt Version: 5.12.3 (built against 5.12.3) Nextcloud: 15.0.7 All versions are the latest available versions. ADDITIONAL INFORMATION Using a password only containing ASCII characters works as expected. The password has been copied, pasted, and checked for errors. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 406867] Dolphin name grouping feature doesn't work with cyrillic names
https://bugs.kde.org/show_bug.cgi?id=406867 --- Comment #3 from Andrey Kozlovskiy --- It turned out that the problem depends on the language. For example, grouping works fine with English (GB and US) and German, but not with Russian (ru_RU.UTF-8). Run dolphin with LANGUAGE variable to test: > LANGUAGE="en_US.UTF-8" dolphin -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 400770] Erratic Kmail filtering (startup problem?)
https://bugs.kde.org/show_bug.cgi?id=400770 --- Comment #6 from David Lochrin --- (In reply to Andy Goss from comment #4) > Filters cannot be run manually on a folder unless the Settings > Configure > Filters utility is opened, and one filter, it doesn't matter which, is > selected, and OK pressed. Then filters can be run manually on a folder, and > any subsequent incoming emails during the session will be fully filtered. > > The problem does not occur on every startup, just most of them. On rare > occasions no filters are applied. I can confirm this. My Kmail-client startup does not download immediately which gives me time to open the "apply filters" menu and clock "OK". That reliably initialises the filters. Clearly Kmail startup is buggy. -- You are receiving this mail because: You are watching all bug changes.
[kpat] [Bug 407132] install "poker cards" does not give the poker cards.
https://bugs.kde.org/show_bug.cgi?id=407132 --- Comment #2 from Charles MacDonald --- On 2019-05-15 5:36 p.m., Albert Astals Cid wrote: > https://bugs.kde.org/show_bug.cgi?id=407132 > > Albert Astals Cid changed: > > What|Removed |Added > >Component|solver |general > CC||aa...@kde.org > > --- Comment #1 from Albert Astals Cid --- > Works fine for me https://i.imgur.com/9oYXfOI.png > > I know it's not much solace knowing it works for other people. > > You don't really need to follow those instructions, just hitting the install > button makes the card appear as selectable to me. > did find it, it was selectable but in the middle of the long list. I had scrolled past it without seeing it. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 406867] Dolphin name grouping feature doesn't work with cyrillic names
https://bugs.kde.org/show_bug.cgi?id=406867 --- Comment #2 from Andrey Kozlovskiy --- Created attachment 120098 --> https://bugs.kde.org/attachment.cgi?id=120098&action=edit Grouping works fine with some non-latin chars Sorry, forgot to mention that not all non-latin symbols maps to latin A..Z. That's why I only wrote about cyrillic names. Greek symbols works fine for me, also chinese and japanese, for example. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 407576] New: Quickly cycling through sidebars in the settings of several widgets crashes plasmashell
https://bugs.kde.org/show_bug.cgi?id=407576 Bug ID: 407576 Summary: Quickly cycling through sidebars in the settings of several widgets crashes plasmashell Product: plasmashell Version: master Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: herzensch...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 Created attachment 120097 --> https://bugs.kde.org/attachment.cgi?id=120097&action=edit Example with Event Calendar. SUMMARY Checking the settings for specific plasmoids/widgets, clicking on their sidebar and cycling upwards and downwards with arrow keys crashes plasmashell. Plasmoids that are known to do this: Digital Clock, Kicker, Event Calendar, and the plasma-nm, battery and sound widgets. Please refer to https://github.com/Zren/plasma-applet-eventcalendar/issues/76 for more details and some backtraces by Zren. Or should I copy the discussion here for better readability? STEPS TO REPRODUCE 1. Have the widget available and clickable (either natively or using plasmawindowed). 2. Right click the widget and select Configure [widget name]... 3. Click the sidebar. 4. Cycle between elements using the Up and Down arrow keys very fast. This is reproduceable at least with Kubuntu 19.04 and Manjaro. Plasmoidviewer cannot be used to reproduce this. -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 406906] Option to Disable Rich/HTML Text
https://bugs.kde.org/show_bug.cgi?id=406906 --- Comment #1 from Christoph Feck --- It defaults to rich text, see https://cgit.kde.org/kdeplasma-addons.git/tree/applets/notes/package/contents/ui/main.qml#n137 If this is adapted to also handle plain text, the various places where it converts '\n' to '' need to be adapted, too. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kglobalaccel] [Bug 406932] Add .kksrc extension to the file name when global shorcuts scheme is exported
https://bugs.kde.org/show_bug.cgi?id=406932 Christoph Feck changed: What|Removed |Added Keywords||junior-jobs --- Comment #1 from Christoph Feck --- The source actually tries to set the extension, but maybe in a wrong way. It should be easy to check how it is set elsewhere in KDE code. https://cgit.kde.org/plasma-desktop.git/tree/kcms/keys/kglobalshortcutseditor.cpp#n526 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 407035] Mass rename sometimes preserves extensions for directories
https://bugs.kde.org/show_bug.cgi?id=407035 --- Comment #1 from Christoph Feck --- Dolphin checks for known extensions. A folder named "test.jpeg" will keep its extension on rename, like it is kept for renaming files. I am not sure if there are registered folder name extensions, such as for mailbox directories etc. If there are, they really should be preserved. Maybe the MIME database knows extensions that apply to folder names. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 406867] Dolphin name grouping feature doesn't work with cyrillic names
https://bugs.kde.org/show_bug.cgi?id=406867 Christoph Feck changed: What|Removed |Added Status|REPORTED|CONFIRMED Keywords||junior-jobs Ever confirmed|0 |1 --- Comment #1 from Christoph Feck --- Indeed the latin letter range 'A'...'Z' is hardcoded, see https://cgit.kde.org/dolphin.git/tree/src/kitemviews/kfileitemmodel.cpp#n1899 We could add (at least) greek and cyrillic letter ranges. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 407570] Kdenlive is not for professionals and not for amateurs
https://bugs.kde.org/show_bug.cgi?id=407570 Christoph Feck changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |NOT A BUG --- Comment #1 from Christoph Feck --- Since you actually have read bug 406933 comment #1, I won't repeat it here. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 407575] New: Default transition duration does not apply to the in-point
https://bugs.kde.org/show_bug.cgi?id=407575 Bug ID: 407575 Summary: Default transition duration does not apply to the in-point Product: kdenlive Version: 19.04.1 Platform: MS Windows OS: MS Windows Status: REPORTED Severity: normal Priority: NOR Component: User Interface Assignee: j...@kdenlive.org Reporter: ksy20...@chollian.net Target Milestone: --- Created attachment 120096 --> https://bugs.kde.org/attachment.cgi?id=120096&action=edit Default transition duration does not apply to in-point transition SUMMARY When clicked lower-left corner of a clip to apply default transition, the duration gets full length of the clip. (In case of out-point transition, the duration is OK. 1 second just.) STEPS TO REPRODUCE 1. Import or create some clips in the project bin 2. Drag and drop a longer clip into V1 track 3. Drag and drop another shorter clip into V2 track, within the duration range of the first clip 4. Click lower-left corner of the second clip OBSERVED RESULT The transition is added with same duration of the clip EXPECTED RESULT The duration of the transition added should be 1 second (default) SOFTWARE/OS VERSIONS Windows: both 7 and 10 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.
[kdenlive] [Bug 407574] New: Cannot edit clip duration
https://bugs.kde.org/show_bug.cgi?id=407574 Bug ID: 407574 Summary: Cannot edit clip duration Product: kdenlive Version: 19.04.1 Platform: MS Windows OS: MS Windows Status: REPORTED Severity: major Priority: NOR Component: User Interface Assignee: j...@kdenlive.org Reporter: ksy20...@chollian.net Target Milestone: --- Created attachment 120095 --> https://bugs.kde.org/attachment.cgi?id=120095&action=edit Duration and position edit fields are all read-only SUMMARY It is very hard to change the duration of each clips. STEPS TO REPRODUCE 1. Import or create any clip in the project bin 2. Drag the clip and drop it on the timeline 3. Double-click the clip on the timeline, the Duration dialog will not popup 4. Right-click the clip on the timeline, and select the "Edit Duration" command OBSERVED RESULT Now, the Position and Duration edit fields are all read-only. CANNOT TYPE IN ANYTHING EXPECTED RESULT Users should be able to edit the duration of selected clip by typing numbers. The only way to adjust the duration is to click the tiny up/down buttons on the right side of edit fields. SOFTWARE/OS VERSIONS Windows: both 7 and 10 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.
[kdevelop] [Bug 372172] Enable text copy from tooltip
https://bugs.kde.org/show_bug.cgi?id=372172 Luis changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |NOT A BUG --- Comment #2 from Luis --- I checked again in version 5.3.1 and it in deed works with Ctrl+C, it didn't work before. I think this can be closed Thanks -- You are receiving this mail because: You are watching all bug changes.
[kaffeine] [Bug 388232] Provide Flatpak or AppImage for kaffeine
https://bugs.kde.org/show_bug.cgi?id=388232 Mauro Carvalho Chehab changed: What|Removed |Added Status|REOPENED|RESOLVED Resolution|--- |FIXED --- Comment #13 from Mauro Carvalho Chehab --- Ok, running it should be easy: just install Docker and run: docker pull maurochehab/kaffeine docker run -it --env="DISPLAY" --env="QT_X11_NO_MITSHM=1" --volume="/tmp/.X11-unix:/tmp/.X11-unix:rw" --volume="$HOME:/home/kaffeine:rw" $(for i in $(ls /dev/dvb/adapter*/*); do echo -n "--device=$i:$i:rwm "; done) maurochehab/kaffeine I'll be pushing a quick set of instructions at the README.md file. With that, I'm closing this BZ. -- You are receiving this mail because: You are watching all bug changes.
[kiriki] [Bug 407016] Rules of play
https://bugs.kde.org/show_bug.cgi?id=407016 Albert Astals Cid changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME --- Comment #3 from Albert Astals Cid --- user stopped caring to check his report, we don't really have a status for that -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 407213] Using Tab to switch focus does not cycle correctly
https://bugs.kde.org/show_bug.cgi?id=407213 Nate Graham changed: What|Removed |Added CC||n...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[kiriki] [Bug 407016] Rules of play
https://bugs.kde.org/show_bug.cgi?id=407016 --- Comment #2 from kingtesti...@gmail.com --- ..I moved on, uninstalled it. I'm gonna stick to regular physical dice, thanks.. On Wed, May 15, 2019, 5:39 PM Albert Astals Cid wrote: > https://bugs.kde.org/show_bug.cgi?id=407016 > > Albert Astals Cid changed: > >What|Removed |Added > > > Resolution|--- |WAITINGFORINFO > Status|REPORTED|NEEDSINFO > > --- Comment #1 from Albert Astals Cid --- > The rules are defined at > https://docs.kde.org/trunk5/en/kdegames/kiriki/rules_and_tips.html > > Have you spotted any discrepancy between that and what the game does? > > -- > You are receiving this mail because: > You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 406256] PPC64, vector floating point instructions don't handle subnormal according to VSCR[NJ] bit setting
https://bugs.kde.org/show_bug.cgi?id=406256 --- Comment #11 from Carl Love --- Julian: > https://urldefense.proofpoint.com/v2/url?u=https-3A__bugs.kde.org_sho > w-5Fbug.cgi-3Fid-3D406256&d=DwIFaQ&c=jf_iaSHvJObTbx- > siA1ZOg&r=RFEmMkZAk > -- > _wFGN5tkM_A&m=5o2Sjz00Tqqxz4dOXWvuGwWsbia9aURAkghSmeY0Sm0&s=1rRXfsCpJ > Dor_oQ1SSmOvBBYZkeJgD7aT4Iz_gYMxGk&e= > > --- Comment #8 from Julian Seward --- > Thanks for the respin. I have mostly only minor comments about > it. Is OK to > land provided all the comments below are addressed, except for the > one about > vectorising negateVF32, which would be nice to fix if you can do so > relatively > easily, but is not essential. > > Also, when landing, please split the patch into two parts: the > implementation > and the tests, and land the implementation first. Done. I had all the changes in one patch to make it easier to move files around to 5 different machines for testing. > > > --- a/VEX/priv/guest_ppc_toIR.c > +++ b/VEX/priv/guest_ppc_toIR.c > > is_Zero_Vector, is_Denorm_Vector and dnormV32_adj have vectorised > nicely. Is > it also possible to do negateVF32 with vectors, rather lane > by lane as at > present? Note, for a vector version of is_NaN, you can see more or > less how > to do it by looking at isNan() in host_ppc_isel.c. > Renamed negateVF32(value) to negate_Vector( size, value) to make the naming more consistent. Also, structured it to generalize easily to more vector sizes. Currently just supporting vector of F32. This change requires creating the new function is_NaN_Vector(size, value) as you eluded to above. Again, structured the function to easily extend to more vector sizes. > > +static IRExpr* dnormV32_adj ( IRExpr* src ) > > nit: maybe rename this to be more consistent with your other vector- > helper > function names (is_Zero_Vector etc) > Yea, consistency is a good thing. Renamed dnormV32_adj() to dnorm_adj_Vector(). Note did not restructure the function to easily extend to other vector sizes. Left that for the future. > > + assign ( VSCR_NJ_mask, binop( Iop_64HLtoV128, > + unop( Iop_1Sto64, > + mkexpr( VSCR_NJ ) ) , > + unop( Iop_1Sto64, > + mkexpr( VSCR_NJ ) ) ) ); > > nit: VSCR_NJ isn't used past this point. Change its type to Ity_I64 > and lift > the 1Sto64 operation into that definition, so it isn't duplicated > here. > Yea, that would be better. Fixed. > > --- a/coregrind/m_dispatch/dispatch-ppc32-linux.S > +++ b/coregrind/m_dispatch/dispatch-ppc32-linux.S > > LafterFP2: > + /* set host Vector Status Control Register bit NJ to zero > + to ensure the host generate subnormal results for the > + vector floating point instructions. */ > +mfvscr 16 /* Clear NJ bit */ > +vspltisw 9,0x1 /* 4x 0x0001 */ > +vspltisw 8,0x0 /* zero */ > +vsldoi 9,8,9,0x2 /* <<2*8 => 4x 0x0001 > */ > +vnor 9,9,9 /* 4x 0xFFFE */ > + vand 16,16,9 /* Mask out NJ bit */ > +mtvscr 16 > > (1) Guard these with #ifdef HAS_ALTIVEC like the other Altivec stuff > in > this file. Otherwise this will fail when run on a non-Altivec > enabled target > (do we still support any of those)? And the same for the other to > assembly > files. > (2) (As a check) is the above sequence runnable even on the lowest > level > Altivec subset? Otherwise (again) it will fail at run time. > > (3) I wasn't entirely clear what the changes to the post-run > invariant checks > are (after label "postamble:"). IIUC, they already do check that > VSCR[NJ].host == 0, but the comments are wrong, and you've updated > the > comments, but not the code? Can you clarify/re-check? When I went in to fix up the code per you comments, I noticed that the code I added to set VSCR[NJ] = 0 is not doing anything. I had missed the code a bit lower: /* set host AltiVec control word to the default mode expected by VEX-generated code. */ ld 6,.tocent__vgPlain_machine_ppc64_has_VMX@toc(2) ld 6,0(6) cmpldi 6,0 beq .LafterVMX2 vspltisw 3,0x0 /* generate zero */ mtvscr 3 which is forcing the entire VSCR register to zero. The instruction vtvscr moves the contents of the specified register to VSCR. This is actually what I had originally been looking for when I was trying to figure out why Valgrind always generated subnormal results but natively I wasn't getting subnormal results on BE. This code t
[plasmashell] [Bug 407571] DnD checkbox doesn't indicate DnD state
https://bugs.kde.org/show_bug.cgi?id=407571 --- Comment #2 from Nicolas Fella --- yes. After I select an entry and the DnD is active I'd expect the checkbox to be checked -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 407571] DnD checkbox doesn't indicate DnD state
https://bugs.kde.org/show_bug.cgi?id=407571 David Edmundson changed: What|Removed |Added CC||k...@davidedmundson.co.uk --- Comment #1 from David Edmundson --- When you press it do you see a context menu? -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 395497] Menubar - No text
https://bugs.kde.org/show_bug.cgi?id=395497 Albert Astals Cid changed: What|Removed |Added Status|CONFIRMED |NEEDSINFO Resolution|--- |WAITINGFORINFO --- Comment #19 from Albert Astals Cid --- (In reply to jimbo1qaz from comment #18) > I found this bug independently, with a slightly different procedure. > > 1. Open Okular, Configure Toolbars dialog. > 2. Add "About KDE" to Main Toolbar . > 3. Press Apply, which creates ~/.local/share/kxmlgui5/okular/shell.rc. You mean this three steps gives you a "No text" menubar? Can the rest of you reproduce this? I can't, just works fine for me -- You are receiving this mail because: You are watching all bug changes.
[kiriki] [Bug 407016] Rules of play
https://bugs.kde.org/show_bug.cgi?id=407016 Albert Astals Cid changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|REPORTED|NEEDSINFO --- Comment #1 from Albert Astals Cid --- The rules are defined at https://docs.kde.org/trunk5/en/kdegames/kiriki/rules_and_tips.html Have you spotted any discrepancy between that and what the game does? -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 407340] PPC64, does not support the vlogefp, vexptefp instructions
https://bugs.kde.org/show_bug.cgi?id=407340 --- Comment #3 from Carl Love --- Created attachment 120093 --> https://bugs.kde.org/attachment.cgi?id=120093&action=edit separate test case patch The test case changes were split into a separate patch -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 407340] PPC64, does not support the vlogefp, vexptefp instructions
https://bugs.kde.org/show_bug.cgi?id=407340 --- Comment #2 from Carl Love --- Created attachment 120092 --> https://bugs.kde.org/attachment.cgi?id=120092&action=edit updated patch per changes to previous dnormal patch The patch to add support for the vlogefp and vexptefp instructions is dependent on the dnormal patch. The patch was also split into a VEX patch and a test case patch -- You are receiving this mail because: You are watching all bug changes.
[kpat] [Bug 407132] install "poker cards" does not give the poker cards.
https://bugs.kde.org/show_bug.cgi?id=407132 Albert Astals Cid changed: What|Removed |Added Component|solver |general CC||aa...@kde.org --- Comment #1 from Albert Astals Cid --- Works fine for me https://i.imgur.com/9oYXfOI.png I know it's not much solace knowing it works for other people. You don't really need to follow those instructions, just hitting the install button makes the card appear as selectable to me. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 372172] Enable text copy from tooltip
https://bugs.kde.org/show_bug.cgi?id=372172 Alexander Potashev changed: What|Removed |Added CC||aspotas...@gmail.com --- Comment #1 from Alexander Potashev --- Ctrl+C works for me, however it's not discoverable. -- You are receiving this mail because: You are watching all bug changes.
[plasma-simplemenu] [Bug 407573] New: Simple Menu mostly displayed off-screen on first launch on top panel
https://bugs.kde.org/show_bug.cgi?id=407573 Bug ID: 407573 Summary: Simple Menu mostly displayed off-screen on first launch on top panel Product: plasma-simplemenu Version: unspecified Platform: Kubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: h...@kde.org Reporter: botelho2...@gmail.com CC: plasma-b...@kde.org Target Milestone: --- Created attachment 120091 --> https://bugs.kde.org/attachment.cgi?id=120091&action=edit Image of menu off-screen SUMMARY STEPS TO REPRODUCE 1. Boot OS, or place new/fresh Simple Menu widget on a top panel 2. Activate Simple Menu either by clicking icon or activating keyboard shortcut OBSERVED RESULT Simple Menu is displayed mostly off-screen at the top of screen when using top panel. This ONLY happens during the first activation of Simple Menu either after booting or after placing the widget and only using a top panel. EXPECTED RESULT Simple Menu is displayed fully on-screen from first activation on top panel. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Kubuntu 18.04 (available in About System) KDE Plasma Version: 5.12.7 -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 406256] PPC64, vector floating point instructions don't handle subnormal according to VSCR[NJ] bit setting
https://bugs.kde.org/show_bug.cgi?id=406256 --- Comment #10 from Carl Love --- Created attachment 120090 --> https://bugs.kde.org/attachment.cgi?id=120090&action=edit Update test case, add new test The test case patch that goes with the subnormal changes in VEX. -- You are receiving this mail because: You are watching all bug changes.
[xdg-desktop-portal-kde] [Bug 407572] New: Flatpaks using org.kde.Platform take minutes to launch on Kubuntu 19.04
https://bugs.kde.org/show_bug.cgi?id=407572 Bug ID: 407572 Summary: Flatpaks using org.kde.Platform take minutes to launch on Kubuntu 19.04 Product: xdg-desktop-portal-kde Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: jgrul...@redhat.com Reporter: ahay...@gmail.com Target Milestone: --- SUMMARY Flatpaks using org.kde.Platform take minutes to launch on Kubuntu 19.04 STEPS TO REPRODUCE 1. Install org.telegram.desktop on kubuntu 19.04 2. Observe that the app takes 1-3 minutes to launch 3. Observe that apps that don't use org.kde.platform launch fine, and that using other DEs are fine. Also observe that in the journal there are lots of errors relating to xdg-desktop-portal-kde (eg https://pastebin.ubuntu.com/p/6m2fVWGc93/ ) ADDITIONAL INFORMATION This is a copy of https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal-kde/+bug/1829269 reported by Eric Adams. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 406256] PPC64, vector floating point instructions don't handle subnormal according to VSCR[NJ] bit setting
https://bugs.kde.org/show_bug.cgi?id=406256 --- Comment #9 from Carl Love --- Created attachment 120089 --> https://bugs.kde.org/attachment.cgi?id=120089&action=edit Updated patch to fix issues with dnormal values v5 Updated the patch per latest comments from Julian. Split patch into VEX patch and test case patch. Renamed negateVF32(value) to negate_Vector( size, value), vectorized. Created new function is_NaN_Vector(size, value) Renamed dnormV32_adj() to dnorm_adj_Vector(). Lifted VSCR_NJ, made it Ity_I64. The various assembly routines: Removed my new code to set VSCR[NJ]=0 as it is redundant given that there is existing code that is already clearing the register. Updated the comments in the code to make it clear where VSCR[NJ] is set to 0. Updated comments with regard to the invarent check to make it clear what is being checked and what to do based on the check. There are now no functional changes to the assembly functions as they already ensure the VSCR[NJ] but is set to 0. -- You are receiving this mail because: You are watching all bug changes.
[kaffeine] [Bug 388232] Provide Flatpak or AppImage for kaffeine
https://bugs.kde.org/show_bug.cgi?id=388232 --- Comment #12 from Mauro Carvalho Chehab --- Kaffeine's Docker container is now at: https://cloud.docker.com/u/maurochehab/repository/docker/maurochehab/kaffeine -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 407571] New: DnD checkbox doesn't indicate DnD state
https://bugs.kde.org/show_bug.cgi?id=407571 Bug ID: 407571 Summary: DnD checkbox doesn't indicate DnD state Product: plasmashell Version: master Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Notifications Assignee: k...@privat.broulik.de Reporter: nicolas.fe...@gmx.de CC: plasma-b...@kde.org Target Milestone: 1.0 SUMMARY STEPS TO REPRODUCE 1. Press Do not Disturb checkbox in Plasmoid 2. Select something OBSERVED RESULT Checkbox is checked for a split second EXPECTED RESULT Checkbox is checked for as long as DnD is active SOFTWARE/OS VERSIONS KDE Plasma Version: master KDE Frameworks Version: master Qt Version: 5.12.3 -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 389576] Okular snap package cannot access files outside home directory
https://bugs.kde.org/show_bug.cgi?id=389576 Nate Graham changed: What|Removed |Added Version|1.7.0 |unspecified Assignee|okular-de...@kde.org|neon-b...@kde.org Product|okular |neon CC||neon-b...@kde.org Component|general |Snaps -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 406933] New GUI bad, can't open old edits. No Audio on/off in video time line. The list goes on........
https://bugs.kde.org/show_bug.cgi?id=406933 RafaMar changed: What|Removed |Added CC||rafamar.mm...@gmail.com --- Comment #2 from RafaMar --- Do not go back to windows, try Olive Video Edition, which is still unfinished, what we call alpha status, but it has fewer errors than kdenlive ... the kde team should do a very serious reflection on this editor, there is no person who I recommend that two days later he asks me for another recommendation ... because it closes them, fails them, etc ... and this with versions 17, 18, and the 19 ... a disaster. It's sad but in Gnu / Linux we do not have a free alternative to mount video that is satisfactory. I am looking forward to the project that I quote you at the beginning. I have more than 20 tutorials written about kdenlive, with their corresponding videos, in Spanish, but what I started with enthusiasm with what I chose as the best free alternative has ended in a big disappointment, with kdenlive I do not enjoy working as if I enjoy blender, gimp, Krita, inkscape, synfigstudio ... Sorry I did not show up, my name is Rafa and I work in the audiovisual world in special effects and 3D. I usually work with Avid, Premiere, SonyVegas or Final Cut video editing, 3D with Maya and Blender and the image editing almost 100% with Gimp when it depends on me, sometimes Krita, and photoshop when they are projects that are being worked on on equipment from this application. With this experience I affirm that kdenlive is badly written and can not be considered a good video editor to an editor that requires the user to be a computer programmer. Here I leave it, but I think my disappointment is clear. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 407554] Crashed when creating a text after autosaving on a document has a selection somewhere
https://bugs.kde.org/show_bug.cgi?id=407554 --- Comment #5 from acc4commissi...@gmail.com --- It seems you don't need to hold your mouse button. Just 1. Make a selection 2. Autosave 3. Create a text always leads to crash. -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 346510] Nikon D810 metadata not all available
https://bugs.kde.org/show_bug.cgi?id=346510 Nate Graham changed: What|Removed |Added Version Fixed In||19.08.0 -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 346510] Nikon D810 metadata not all available
https://bugs.kde.org/show_bug.cgi?id=346510 Nate Graham changed: What|Removed |Added Latest Commit||https://commits.kde.org/gwe ||nview/a985ad14dc073653e996d ||7550dbb58653ce2 Resolution|--- |FIXED Status|ASSIGNED|RESOLVED --- Comment #9 from Nate Graham --- Git commit a985ad14dc073653e996d7550dbb58653ce2 by Nate Graham, on behalf of Tom Moebert. Committed on 15/05/2019 at 20:29. Pushed by ngraham into branch 'master'. Fix incomplete EXIF data for RAW files Summary: In case of RAW files exiv2 retrieved the EXIF data from the JPEG preview image `previewData`. This however contains incomplete EXIF data. Thus provide exiv2 with the full raw image and let it find the most suitable EXIF data chunk. Reviewers: #gwenview, ngraham Reviewed By: #gwenview, ngraham Subscribers: ngraham Tags: #gwenview Differential Revision: https://phabricator.kde.org/D21161 M +5-5lib/document/loadingdocumentimpl.cpp https://commits.kde.org/gwenview/a985ad14dc073653e996d7550dbb58653ce2 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 407345] Verbose debug messages
https://bugs.kde.org/show_bug.cgi?id=407345 --- Comment #3 from Maik Qualmann --- export QT_LOGGING_RULES="*=false" or digikam > /dev/null Maik -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 407565] entering multi tags to the same photo failed
https://bugs.kde.org/show_bug.cgi?id=407565 Maik Qualmann changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED Latest Commit||https://invent.kde.org/kde/ ||digikam/commit/763ba6139656 ||7fc644ed9da9f4281af8903fdf5 ||6 Version Fixed In||6.2.0 --- Comment #1 from Maik Qualmann --- Git commit 763ba61396567fc644ed9da9f4281af8903fdf56 by Maik Qualmann. Committed on 15/05/2019 at 20:19. Pushed by mqualmann into branch 'master'. select all created tags FIXED-IN: 6.2.0 M +2-1NEWS M +8-2core/libs/tags/engine/tagmodificationhelper.cpp https://invent.kde.org/kde/digikam/commit/763ba61396567fc644ed9da9f4281af8903fdf56 -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 407570] New: Kdenlive is not for professionals and not for amateurs
https://bugs.kde.org/show_bug.cgi?id=407570 Bug ID: 407570 Summary: Kdenlive is not for professionals and not for amateurs Product: kdenlive Version: 19.04.1 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: User Interface Assignee: j...@kdenlive.org Reporter: rafamar.mm...@gmail.com Target Milestone: --- SUMMARY Today a person has made me open my eyes with Kdenlive, if a video editor requires you to have to be a computer programmer to work with him we are facing a bad video editor that is badly written because it is wasting a lot of time fixing errors. And the good thing about this statement is that it's true, something is wrong with kdenlive, but not with the new version, but with all of them, I would do a serious thought because I think that it has reached a point of making a version discarding all of the above , because people are very disappointed about this editor. I work professionally in the audiovisual world, I work with professional editors, I do not demand that kdenlive is at their level, but what is sad is that what should be a pleasant task like mounting a video with kdenlive becomes a bad experience that leads to disappointment with the application and to look for other alternatives. Kde deserves to have a good video editor as if he has a good image editor, like Krita, just to cite one of the wonders of this project. But kdenlive deserves to be rewritten from 0 because the current version inherits too many problems that are already some years back. STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT EXPECTED RESULT 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.
[kaffeine] [Bug 388232] Provide Flatpak or AppImage for kaffeine
https://bugs.kde.org/show_bug.cgi?id=388232 Mauro Carvalho Chehab changed: What|Removed |Added Resolution|FIXED |--- Ever confirmed|0 |1 Status|RESOLVED|REOPENED --- Comment #11 from Mauro Carvalho Chehab --- (In reply to Mauro Carvalho Chehab from comment #10) > Git commit 5dda1825c50d8330795ed0ff8b786186acd38c63 by Mauro Carvalho Chehab. This patch adds container support for Kaffeine. The container itself is easily built by running this from Kaffeine's git: $ docker build -t "kaffeine" . (after having docker properly installed) As explained, however, it has one major drawback: it won't have persistent data, at least if one runs it with: $ docker run -it --env="DISPLAY" --env="QT_X11_NO_MITSHM=1" --volume="/tmp/.X11-unix:/tmp/.X11-unix:rw" --volume="$HOME:$HOME:rw" $(for i in $(ls /dev/dvb/adapter*/*); do echo -n "--device=$i:$i:rwm "; done) kaffeine I suspect that this can be managed via some docker run command (or by using some high level container tooling), but I need to dig further. So, for now, I'll keep this bug opened. -- You are receiving this mail because: You are watching all bug changes.
[kaffeine] [Bug 388232] Provide Flatpak or AppImage for kaffeine
https://bugs.kde.org/show_bug.cgi?id=388232 Mauro Carvalho Chehab changed: What|Removed |Added Latest Commit||https://commits.kde.org/kaf ||feine/5dda1825c50d8330795ed ||0ff8b786186acd38c63 Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #10 from Mauro Carvalho Chehab --- Git commit 5dda1825c50d8330795ed0ff8b786186acd38c63 by Mauro Carvalho Chehab. Committed on 15/05/2019 at 20:11. Pushed by mauroc into branch 'master'. Add a Dockerfile to allow building Kaffeine inside a container This is a basic Dockerfile with builds Kaffeine inside an Ubuntu Disco container. With the current settings, the container doesn't access the DVB devices with are outside the container. A command that would allow opening a file from your home directory and to use a Digital TV device would be like: $ docker run -it --env="DISPLAY" --env="QT_X11_NO_MITSHM=1" --volume="/tmp/.X11-unix:/tmp/.X11-unix:rw" --volume="$HOME:$HOME:rw" $(for i in $(ls /dev/dvb/adapter*/*); do echo -n "--device=$i:$i:rwm "; done) kaffeine Please notice, however, that, with the above there won't be any persistent storage. every time the docker container runs, it will forget any previously configured data, EPG information, etc. Signed-off-by: Mauro Carvalho Chehab A +46 -0Dockerfile https://commits.kde.org/kaffeine/5dda1825c50d8330795ed0ff8b786186acd38c63 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 407569] Extra padding in Plasmashell when switching from Xorg to Wayland
https://bugs.kde.org/show_bug.cgi?id=407569 Nate Graham changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|REPORTED|NEEDSINFO --- Comment #1 from Nate Graham --- Does this happen with only the Breeze Plasma theme, or other Plasma themes as well? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 407569] Extra padding in Plasmashell when switching from Xorg to Wayland
https://bugs.kde.org/show_bug.cgi?id=407569 Nate Graham changed: What|Removed |Added CC||n...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[elisa] [Bug 399211] crash when I add a new path in elisa settings
https://bugs.kde.org/show_bug.cgi?id=399211 --- Comment #2 from Patrick Silva --- I can't reproduce with elisa-git on Arch Linux. I'm closing this report as fixed. Thank you Matthieu. -- You are receiving this mail because: You are watching all bug changes.
[elisa] [Bug 399211] crash when I add a new path in elisa settings
https://bugs.kde.org/show_bug.cgi?id=399211 Patrick Silva changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 407569] New: Extra padding in Plasmashell when switching from Xorg to Wayland
https://bugs.kde.org/show_bug.cgi?id=407569 Bug ID: 407569 Summary: Extra padding in Plasmashell when switching from Xorg to Wayland Product: plasmashell Version: 5.15.5 Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Theme - Breeze Assignee: visual-des...@kde.org Reporter: v...@veqz.net CC: plasma-b...@kde.org Target Milestone: 1.0 Created attachment 120088 --> https://bugs.kde.org/attachment.cgi?id=120088&action=edit Combined two screenshots of Kicker: the inserted/rightmost is in Xorg, and the leftmost is afterwards in Wayland SUMMARY Wanting to test out Wayland more, I logged out of Plasma under Xorg and logged in to Plasma under Wayland. Once there, the padding is much larger than expected. See the attachment, where I have combined two screenshots of Kicker. The inserted/rightmost is in Xorg, and the leftmost is afterwards in Wayland. STEPS TO REPRODUCE 1. Having logged in to Plasma under Xorg 2. Logging out and loggin in to Plasma under Wayland OBSERVED RESULT The padding in Plasmashell is larger than expected. EXPECTED RESULT The padding should have been similar under Wayland as under Xorg. SOFTWARE/OS VERSIONS KDE neon User Edition KDE Plasma Version: 5.15.5 KDE Frameworks Version: 5.58 Qt Version: 5.12.0 ADDITIONAL INFORMATION I tried to report this earlier with https://bugs.kde.org/show_bug.cgi?id=398636, and David Edmundson found a workaround. This is still a problem however, and shouldn't happen. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kconfig] [Bug 407568] New: add option to disable mouse just like a touchpad (for certain combos)
https://bugs.kde.org/show_bug.cgi?id=407568 Bug ID: 407568 Summary: add option to disable mouse just like a touchpad (for certain combos) Product: frameworks-kconfig Version: unspecified Platform: Compiled Sources OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: matt...@mjdsystems.ca Reporter: f...@ffoxfire.33mail.com CC: kdelibs-b...@kde.org Target Milestone: --- KDE has this wonderful helpful higly-sensical option (via system settings) to disable the touchpad while another mouse is plugged in - since it is a terrible pain ita while typing (accidental touch will reorient cursor or worse). Of course we all use it on the laptop compy. These days you get reasonably priced and compact keyboard/touchpad combinations (e.g. rapoo), very compact and well made. But you gessed it: To save space, the touchpad sits right next to the KBD and is hit inadvertendly by the right hand often times which is a terrible nuisance while typing. The touchpad, however, looks like a mouse to Linux, so in system settings one is not allowed to disable it and use a hotkey/shortcut to switch it ON/OFF. That is so convenient with real touchapds. I'd imagine, the modification to allow both mice AND touchpads to be switched off or have some plug-in automatism like we already have ought to be moderate. Of course, you'd want to safeguard users from disabling their real and only mouse. But with such a keyboard, users would want just that. Ideally also making sure there is a hotkey to switch on the mouse back. That logic probably required extra programming. Still though, those combos with no option to get rid of the mouse have ultra-poor usability. Or maybe some little extra DBUS call may be helpful, activated by hotkey rather than system settings to temporarily get rid of the only mouse attached in KDE? -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 371511] kontact/akregator crashes while trying to open a link from the list (middle click)
https://bugs.kde.org/show_bug.cgi?id=371511 --- Comment #49 from Wolfgang Bauer --- That's what I would propose as a fix now: https://phabricator.kde.org/D21236 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 406835] Plasma 5.15.4 crash
https://bugs.kde.org/show_bug.cgi?id=406835 --- Comment #5 from nl.smart --- Hi, Thank you for your message and the explications, I'll send them the bugg. Le mar. 14 mai 2019 à 21:18, Christoph Feck a écrit : > https://bugs.kde.org/show_bug.cgi?id=406835 > > --- Comment #4 from Christoph Feck --- > Please ask for help in a forum of your distribution. Providing debug > symbols on > Arch-based distribution might require to compile software with different > options. > > -- > You are receiving this mail because: > You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 407218] Add support for the copy_file_range syscall
https://bugs.kde.org/show_bug.cgi?id=407218 Mark Wielaard changed: What|Removed |Added Resolution|--- |FIXED Status|ASSIGNED|RESOLVED --- Comment #6 from Mark Wielaard --- (In reply to Petar Jovanovic from comment #5) > (In reply to Mark Wielaard from comment #4) > > Does the following work on mips32? > > Yes, it does. Can you commit the change? commit c212b72a63e43be323a4e028bbdbe8b023c22be8 Author: Mark Wielaard Date: Wed May 15 21:30:00 2019 +0200 Explicitly make testcase variable for sys-copy_file_range undefined. On some systems an extra warning could occur when a variable in the memcheck/tests/linux/sys-copy_file_range testcase was undefined, but (accidentially) pointed to known bad memory. Fix by defining the variable as 0, but then marking it explicitly undefined using memcheck VALGRIND_MAKE_MEM_UNDEFINED. Followup for https://bugs.kde.org/show_bug.cgi?id=407218 -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 407469] Problems with rendering Previews and with GLSL/Movit
https://bugs.kde.org/show_bug.cgi?id=407469 --- Comment #5 from Andrey --- And I cannot create a proxy for the PNG sequence (it results in "Cannot open file qimage:/home/olaf/.cache/kdenlive/proxy/ef3d466a7956492baaf307c4627706be.mkv"). As well as for a single PNG image. That's also bad. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 407469] Problems with rendering Previews and with GLSL/Movit
https://bugs.kde.org/show_bug.cgi?id=407469 --- Comment #4 from Andrey --- Another thing: even on my better than average machine 4K editing on CPU-only is painfully slow, so I still at least have to use proxy files. But there is a problem: even such a simple effect as white balance correction causes them to play back slower than realtime or at least on the verge even with the "Track compositing" set to "Preview". I am making art videos which require a lot of fine tuning and inevitably some effects, at least curves and sometimes a vignette, and I don't understand why they are SO slow even when the proxy resolution is quarter the original size? -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 407469] Problems with rendering Previews and with GLSL/Movit
https://bugs.kde.org/show_bug.cgi?id=407469 --- Comment #3 from Andrey --- Okay, I tried the AppImage. In fact, I did try it before but could not resize the timeline area to fit my hidpi screen, it immediately snapped back to the original size and even was getting shrunk with every attempt, but now it's fixed somehow, I don't know why, so nevermind. To business: it goes better with the AppImage but still with some quirks in the preview rendering: 1. Preview of the intro (PNG sequence) is still very slow, just like if the frames are still read from the original files. 2. The final titles are still cause the preview renderer crash. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 407453] on Italian Windows version the 0/1 sliders are getting only integers.
https://bugs.kde.org/show_bug.cgi?id=407453 emohr changed: What|Removed |Added Status|REPORTED|CONFIRMED Flags||Brainstorm+ Ever confirmed|0 |1 CC||fritzib...@gmx.net --- Comment #2 from emohr --- Thank you Davy for reporting. I added it as another example to issue: https://invent.kde.org/kde/kdenlive/issues/78 . Hoping JBM or Alcinos can fix that. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 407469] Problems with rendering Previews and with GLSL/Movit
https://bugs.kde.org/show_bug.cgi?id=407469 emohr changed: What|Removed |Added Flags||timeline_corruption+ Status|REPORTED|NEEDSINFO CC||fritzib...@gmx.net Resolution|--- |WAITINGFORINFO --- Comment #2 from emohr --- Movit and GPU acceleration is experimental and not supported yet. Please switch off. Please try with the current Kdenlive AppImage version 19.04.1 to see if there are any packaging issues https://files.kde.org/kdenlive/release/ or Kdenlive_Nightly_Appimage https://binary-factory.kde.org/job/Kdenlive_Nightly_Appimage_Build/lastSuccessfulBuild/artifact/ If they don't occur when using the AppImage, then it's your configuration or packaging. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 407460] new notifications: "Open" and hamburger buttons should have the same height
https://bugs.kde.org/show_bug.cgi?id=407460 --- Comment #10 from David Edmundson --- So the code is: max(fontSize * 1.6, textSize + marginTop + marginBottom) fontSize will apply for icon only, but textSize will be 0 In theory fontSize and textSize should be the same. Clearly you guys have margins that are bigger than your font * 0.6 It seems this doesn't exist with PC3, so maybe it's not worth fixing the root issue. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 407528] GoTo -> Guide, context menu missing
https://bugs.kde.org/show_bug.cgi?id=407528 emohr changed: What|Removed |Added Ever confirmed|0 |1 CC||fritzib...@gmx.net Status|REPORTED|CONFIRMED Flags||Brainstorm+ -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 407566] Dolphin crashes when opening a folder or a file
https://bugs.kde.org/show_bug.cgi?id=407566 --- Comment #1 from alicengizk...@gmail.com --- additional info qt5-base version 5.12.2 kde plasma 5.14.4 kde-app 19.04.0 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 407485] "Thumbnail Aside" does not work in fullscreen mode and without titlebar
https://bugs.kde.org/show_bug.cgi?id=407485 --- Comment #4 from Csaba Kertész --- Ok! Thank you for your awesome quick fix! -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 407485] "Thumbnail Aside" does not work in fullscreen mode and without titlebar
https://bugs.kde.org/show_bug.cgi?id=407485 --- Comment #3 from Vlad Zagorodniy --- It's already resolved so no need to close. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 407537] KArchive cannot read some files created with quazip
https://bugs.kde.org/show_bug.cgi?id=407537 Boudewijn Rempt changed: What|Removed |Added Summary|[corrupted kra file] One of |KArchive cannot read some |my *.kra saved with 4.2 |files created with quazip |behaves differently than| |other | -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kirigami] [Bug 381182] Scrolling choppy/slow under Wayland
https://bugs.kde.org/show_bug.cgi?id=381182 Nate Graham changed: What|Removed |Added Resolution|WAITINGFORINFO |FIXED Version Fixed In||5.58 Status|NEEDSINFO |RESOLVED --- Comment #10 from Nate Graham --- Sounds like this particular bug is fixed, then. Can you open a new one for the new (thankfully less severe) issue you're encountering now? Thanks! -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 407485] "Thumbnail Aside" does not work in fullscreen mode and without titlebar
https://bugs.kde.org/show_bug.cgi?id=407485 --- Comment #2 from Csaba Kertész --- I can confirm that the committed fix works on my local Ubuntu after patching, recompiling, installing and restarting KWin. Can I close this bug or it is tied to CI somehow? -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 407567] New: i want to connect for the or KDE connect in my mobile to PC
https://bugs.kde.org/show_bug.cgi?id=407567 Bug ID: 407567 Summary: i want to connect for the or KDE connect in my mobile to PC Product: kdeconnect Version: unspecified Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: critical Priority: NOR Component: android-application Assignee: albertv...@gmail.com Reporter: sureshwai...@gmail.com Target Milestone: --- SUMMARY my mobile to a Linux PC system is not connected. dives name not showing in both system STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION: sorry, I don't know the information about my system -- You are receiving this mail because: You are watching all bug changes.
[frameworks-qqc2-desktop-style] [Bug 405471] QQC2 slider behaving badly when initial value is 1
https://bugs.kde.org/show_bug.cgi?id=405471
Filip Fila changed:
What|Removed |Added
Resolution|--- |FIXED
Status|CONFIRMED |RESOLVED
Latest Commit||https://commits.kde.org/qqc
||2-desktop-style/6d0289d7b28
||4f5074c5f8ffe5ee6879f656e07
||24
--- Comment #4 from Filip Fila ---
Git commit 6d0289d7b284f5074c5f8ffe5ee6879f656e0724 by Filip Fila.
Committed on 15/05/2019 at 16:34.
Pushed by filipf into branch 'master'.
[QQC2 Slider Style] Fix wrong handle positioning when initial value is 1
Summary:
Old code was not reading value properly when initial value was 1, misplacing
the handle as a result.
Test Plan:
Tested by running qmlscene with:
```
import QtQuick.Controls 2.5
Slider {
from: 1
to: 5
stepSize: 1
//orientation: Qt.Vertical
}
```
Tested both in horizontal and vertical orientation.
You can also test this in the Mouse KCM, with the Pointer Speed slider.
Reviewers: mart, #plasma, ngraham, broulik
Reviewed By: mart, #plasma, ngraham
Subscribers: broulik, plasma-devel
Tags: #plasma
Differential Revision: https://phabricator.kde.org/D21075
M +3-2org.kde.desktop/Slider.qml
https://commits.kde.org/qqc2-desktop-style/6d0289d7b284f5074c5f8ffe5ee6879f656e0724
--
You are receiving this mail because:
You are watching all bug changes.
[digikam] [Bug 407235] macOS : digiKam 6.1.0 crashes when quitting
https://bugs.kde.org/show_bug.cgi?id=407235 --- Comment #6 from christoph...@runbox.com --- Here is the log when just quitting: 2019-05-15 18:22:38.378655+0200 digikam[5349:1316418] [digikam.geoiface] 2019-05-15 18:22:39.010323+0200 digikam[5349:1316418] [digikam.general] Cancel Main Thread 2019-05-15 18:22:39.010386+0200 digikam[5349:1316418] [digikam.general] Cancel Main Thread Process 5349 stopped * thread #1, queue = 'com.apple.main-thread', stop reason = EXC_BAD_ACCESS (code=EXC_I386_GPFLT) frame #0: 0x00010002583e dyld`dyld::fastBindLazySymbol(ImageLoader**, unsigned long) + 43 dyld`dyld::fastBindLazySymbol: -> 0x10002583e <+43>: movq 0x140(%rax), %rax 0x100025845 <+50>: movq 0x3b274(%rip), %rdx ; dyld::gLibSystemHelpers 0x10002584c <+57>: xorl %ecx, %ecx 0x10002584e <+59>: testq %rdx, %rdx Target 0: (digikam) stopped. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 226905] Add support for mime-type sections to .kateconfig files
https://bugs.kde.org/show_bug.cgi?id=226905 Dominik Haumann changed: What|Removed |Added Resolution|--- |FIXED Status|CONFIRMED |RESOLVED --- Comment #5 from Dominik Haumann --- Then let's close it. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 407566] New: Dolphin crashes when opening a folder or a file
https://bugs.kde.org/show_bug.cgi?id=407566 Bug ID: 407566 Summary: Dolphin crashes when opening a folder or a file Product: dolphin Version: 19.04.0 Platform: Pardus PiSi Packages OS: Linux Status: REPORTED Severity: critical Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: alicengizk...@gmail.com CC: elvis.angelac...@kde.org Target Milestone: --- Created attachment 120086 --> https://bugs.kde.org/attachment.cgi?id=120086&action=edit dolphin crash report SUMMARY we are developer of Pisilinux Kernel version 4.19.34 STEPS TO REPRODUCE 1. dolphin(19.04) crashes when opening any folder or any file 2. This bug releated with kio version 5.56.0 3. İf we use older version of kio dolphin works fine. OBSERVED RESULT EXPECTED RESULT 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.
[digikam] [Bug 407565] New: entering multi tags to the same photo failed
https://bugs.kde.org/show_bug.cgi?id=407565 Bug ID: 407565 Summary: entering multi tags to the same photo failed Product: digikam Version: 6.1.0 Platform: MS Windows OS: MS Windows Status: REPORTED Severity: normal Priority: NOR Component: Tags-Captions Assignee: digikam-bugs-n...@kde.org Reporter: ab...@takeadventure.com Target Milestone: --- Created attachment 120085 --> https://bugs.kde.org/attachment.cgi?id=120085&action=edit print screens of the last step of the sequence SUMMARY Not clear is it bug or feature request. STEPS TO REPRODUCE (DigiKam v6.1 on Windows 7): 1. select the photo, 2. in caption select the tag, 3. right mouse button, select add new tag, 4. enter 3 different tags (in my example test1, test2 and test3, separated by "," and press ok, 5. all 3 tags are loaded but only the last one is confirmed that belongs to the photo. I would expect all 3 tags should belong to the photo. Thank you for your kind consideration. SOFTWARE/OS VERSIONS Windows: Yes 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.
[valgrind] [Bug 407218] Add support for the copy_file_range syscall
https://bugs.kde.org/show_bug.cgi?id=407218 --- Comment #5 from Petar Jovanovic --- (In reply to Mark Wielaard from comment #4) > > Does the following work on mips32? Yes, it does. Can you commit the change? Thanks. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 401400] kate vi mode does not synchronize content from clipboard
https://bugs.kde.org/show_bug.cgi?id=401400 --- Comment #9 from Ritesh Raj Sarraf --- Created attachment 120084 --> https://bugs.kde.org/attachment.cgi?id=120084&action=edit kate clipboard No need to confirm for any one. It does look like kate has its own clipboard for `vi-mode` -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 407564] New: Discover shows no error message on Arch Linux when update fails because dependencies issues
https://bugs.kde.org/show_bug.cgi?id=407564 Bug ID: 407564 Summary: Discover shows no error message on Arch Linux when update fails because dependencies issues Product: Discover Version: 5.15.5 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Updater Assignee: lei...@leinir.dk Reporter: bugsefor...@gmx.com CC: aleix...@kde.org Target Milestone: --- SUMMARY Today update via Discover failed on my Arch Linux without any error message. Immediately I ran "sudo pacman -Syu" in konsole and got the following error: error: failed to prepare transaction (could not satisfy dependencies) :: unable to satisfy dependency "linux<5.1" required by r8168 EXPECTED RESULT Discover gives feedback when the update process fails SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.15.5 KDE Frameworks Version: 5.58.0 Qt Version: 5.13.0 beta3 ADDITIONAL INFORMATION Discover installed the update for a flatpak package (Elisa) as expected. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 407563] New: [brush preset docker(top bar)] Wrong aspect ratio + a column disapear.
https://bugs.kde.org/show_bug.cgi?id=407563 Bug ID: 407563 Summary: [brush preset docker(top bar)] Wrong aspect ratio + a column disapear. Product: krita Version: 4.2.0-alpha Platform: Appimage OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Usability Assignee: krita-bugs-n...@kde.org Reporter: i...@davidrevoy.com Target Milestone: --- Created attachment 120083 --> https://bugs.kde.org/attachment.cgi?id=120083&action=edit ^ screenshot of the bug with annotations in red Hi, When using small icons in the brush preset docker (top bar/drop down), the thumbnails change to a rectangular aspect ratio. Also, the last column of presets on the right disapears outside of the frame. To reproduce: = 1. Open a new Krita document 2. Click on the brush presets selector in the top toolbar. 3. In the preferences of the docker (on top-right, next to the "Tags" button) change the size for a smaller one. Result: === - Wrong aspect ratio of the thumbnails. - A column of preset almost disappear on rigth. -- You are receiving this mail because: You are watching all bug changes.
[kdiff3] [Bug 407562] New: movement between delta's is broken
https://bugs.kde.org/show_bug.cgi?id=407562 Bug ID: 407562 Summary: movement between delta's is broken Product: kdiff3 Version: 1.8.x Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: application Assignee: reeves...@gmail.com Reporter: vkr...@yahoo.com Target Milestone: --- SUMMARY Ctrl-Up/Down does not navigate between delta's anymore. STEPS TO REPRODUCE 1. Create a multiline text file, copy it and make some changes on different non-consequtive lines in the copy. 2. Open files in kdiff3 3. Attempt to go from first to next delta using Ctrl-Down - nothing happens. Under "Movement" only "goto current delta" is turned on. kdiff3-1.8-lp150.17.1.x86_64 OBSERVED RESULT EXPECTED RESULT 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.
[kate] [Bug 401400] kate vi mode does not synchronize content from clipboard
https://bugs.kde.org/show_bug.cgi?id=401400 --- Comment #8 from Ritesh Raj Sarraf --- (In reply to Ahmad Samir from comment #7) > In vi-mode, kate behaves like this, IIUC: > - if you copy text via Ctrl+C or yanking (which is specific to vi-mode), you > can paste the text with Ctrl+V (in and out of kate) or a plain command p > - if you copy text from outside kate, you can paste it in kate via Ctrl+v, > but if you want to paste it via the vi-mode commands you'd have to use "+p > Can you please elaborate a little about using "+p ? If that is a special case and works, that still is a good thing. > So, if there's a bug here, I'd say that kate shouldn't copy the text to the > clipboard if the user yanks the text in vi-mode, that would match the > behaviour in vim. But I am by no means an expert when it comes to vim or the > vi-mode in kate, so... I agree. But that is something for you or the other developers to confirm. Even in vim, there's the +clipboard feature wherein when you yank something in vim, it gets copied to the clipboard. Now, like you said, it could very well be that kwrite/kate is internally having its own clipboard when run in 'vi mode'. And it copies the buffer to that clipboard when something is yanked in kate's 'vi mode'. Doesn't feel like that is what the kate devs must have done, but there is the possibility. And if that is the case, it'd be nice to have this bug report turned into a Feature Request to have an option to sync 'vi-mode' copy buffers to the Klipper clipboard. Essentially, implement the equivalent of vim's +clipboard feature. -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 407561] New: [Usability] Configuration options in Network applet's right-click menu are confusingly named
https://bugs.kde.org/show_bug.cgi?id=407561 Bug ID: 407561 Summary: [Usability] Configuration options in Network applet's right-click menu are confusingly named Product: plasma-nm Version: 5.15.5 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: applet Assignee: jgrul...@redhat.com Reporter: kishor...@gmail.com Target Milestone: --- SUMMARY If we right-click on the 'Networks' item in the system tray, we get two options. One of them opens the system settings panel to configure networks, while the other opens a configuration window for the plasmoid. Currently, it is difficult to distinguish which does what from the name alone. The option that opens the configuration for the plasmoid should be more clearly named as 'Configure Networks Plasmoid' or 'Configure this applet'. SOFTWARE/OS VERSIONS Linux distro: Arch Linux KDE Plasma Version: 5.15.5 KDE Frameworks Version: 5.57.0 Qt Version: 5.13.0 ADDITIONAL INFORMATION Simliar to bug 407560, but for this plasmoid. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 407560] New: [Usability] Configuration options in Battery plasmoid's right-click menu are confusingly named
https://bugs.kde.org/show_bug.cgi?id=407560 Bug ID: 407560 Summary: [Usability] Configuration options in Battery plasmoid's right-click menu are confusingly named Product: plasmashell Version: 5.15.5 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: Battery Monitor Assignee: k...@privat.broulik.de Reporter: kishor...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 SUMMARY If we right-click on the 'Battery and Brightness' item in the system tray, we get two options: 'Configure Power Saving', and 'Configure Battery and Brightness'. The former opens the system settings area, while the latter opens the configuration for the plasmoid. The option that opens the configuration window for the plasmoid should be named more clearly as 'Configure Battery and Brightness Plasmoid' or 'Configure this Plasmoid'. Currently, I find it confusing as to which option does what. SOFTWARE/OS VERSIONS Linux distro: Arch Linux KDE Plasma Version: 5.15.5 KDE Frameworks Version: 5.57.0 Qt Version: 5.13.0 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 407235] macOS : digiKam 6.1.0 crashes when quitting
https://bugs.kde.org/show_bug.cgi?id=407235 --- Comment #5 from Maik Qualmann --- The digiKam version for OS X should contain debug symbol, launch digiKam in a terminal / console with the following command: lldb /opt/digikam/Applications/KF5/digikam.app/Contents/MacOS/digikam Maik -- You are receiving this mail because: You are watching all bug changes.
[kiofuse] [Bug 75324] Integrate KIO Slaves into file system using FUSE gateway
https://bugs.kde.org/show_bug.cgi?id=75324 --- Comment #101 from Nate Graham --- In fact, the kio-fuse project is being worked on for Google Summer of Code this year! -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 407533] Zoom on hover does not always register cursor movement correctly
https://bugs.kde.org/show_bug.cgi?id=407533 --- Comment #6 from Antti Aho --- Created attachment 120082 --> https://bugs.kde.org/attachment.cgi?id=120082&action=edit New video with Latte Dock launched with the commands -d --graphics I updated Latte Dock to the latest version in master ran it with the following command "$ latte-dock -d --graphics". In this video I have set animations speed to x2 if that makes a difference. The Mouse Sensitivity for Parabolic effect is set to "High". -- You are receiving this mail because: You are watching all bug changes.
[xdg-desktop-portal-kde] [Bug 407559] New: long list of apps can't be fully seen in app chooser
https://bugs.kde.org/show_bug.cgi?id=407559 Bug ID: 407559 Summary: long list of apps can't be fully seen in app chooser Product: xdg-desktop-portal-kde Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: jgrul...@redhat.com Reporter: someuniquen...@gmail.com Target Milestone: --- SUMMARY App chooser app icons are very large, and window has no scrollbar, so if you have many apps associated with file type, it is not possible to see the full list. STEPS TO REPRODUCE 1. open file from flatpak application. OBSERVED RESULT On the screenshot, i have many apps to chose from, and can't see the end of the list: https://i.imgur.com/rDwK2YK.png EXPECTED RESULT I should be able to see and pick any app from the list version: xdg-desktop-portal-kde-5.15.5-1.1.x86_64 -- You are receiving this mail because: You are watching all bug changes.
[kdev-python] [Bug 402760] Source browse mode activated when saving the document with shortcut
https://bugs.kde.org/show_bug.cgi?id=402760 --- Comment #20 from Simone Gaiarin --- Regarding Alt having already the function of the tooltip, that is true, but on the other hand that function is used only when the user interact with the keyboard, so that the user does not even notice that Alt is enabling source browse mode on the code (because the mouse is not moved). When instead the user uses the mouse, Alt is irrelevant to show the tooltip, because the tooltip appears on mouse hoover and Alt can be used to enable source browse mode. So I think all in all keeping Alt for source browse mode it is an ok solution for now, and it is also backward compatible given that it was already there. -- You are receiving this mail because: You are watching all bug changes.
[kdiff3] [Bug 407344] Segfault when scrolling
https://bugs.kde.org/show_bug.cgi?id=407344 --- Comment #3 from michael --- No problem. That's what I'd expect. Now there's a record of it. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 407545] Ctrl-C or triple-click in Chrome omnibar creates multiple context menus
https://bugs.kde.org/show_bug.cgi?id=407545 Harrison McCullough changed: What|Removed |Added Status|NEEDSINFO |RESOLVED --- Comment #2 from Harrison McCullough --- I recently uninstalled and re-installed a bunch of things, including a lot of KDE-related things. However, I hadn't restarted my computer since then. Today, after a full shutdown and reboot, it looks like things are fine. Sorry for the spurious bug report! -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 406820] Akonadi Facebook Resource Crash when I add Facebook account to KOganizer
https://bugs.kde.org/show_bug.cgi?id=406820 Mauro changed: What|Removed |Added Version|5.11.0 |5.10.3 Platform|Archlinux Packages |Ubuntu Packages CC||jasmi...@email.it --- Comment #1 from Mauro --- Same here on Ubuntu 19.04 -- You are receiving this mail because: You are watching all bug changes.
