[kontact] [Bug 384324] View Calendars Side by Side
https://bugs.kde.org/show_bug.cgi?id=384324 --- Comment #2 from Laurent Montel --- Git commit 0330ab1ac26f7be7b3ce92eccf956d21b1b67c9f by Montel Laurent. Committed on 07/09/2017 at 06:58. Pushed by mlaurent into branch 'Applications/17.08'. Make sure that agenda is not null M +3-0src/agenda/timelabels.cpp M +3-3src/agenda/timelabels.h https://commits.kde.org/eventviews/0330ab1ac26f7be7b3ce92eccf956d21b1b67c9f -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 384454] lag when working on canvas
https://bugs.kde.org/show_bug.cgi?id=384454 Alvin Wong changed: What|Removed |Added CC||alvinhoc...@gmail.com Resolution|--- |WAITINGFORINFO Component|CPU Canvas |OpenGL Canvas Status|UNCONFIRMED |NEEDSINFO --- Comment #1 from Alvin Wong --- Since you left out the most important OS information on the bug report, we can't really get anything useful out of it... but judging by your symptoms it would very likely be the Intel driver bug... If you are using Windows and is on a system with Intel HD Graphics, then it is most definitely a bug in the Intel drivers. See Bug 360601 ** The current workaround would be to go to "Configure Krita" -> "Display" and uncheck OpenGL. ** Please reply so we know if this works or not. --- We're working on another way of handling the canvas display which should work better with the Intel drivers, and we have a test version available: https://krita.org/en/item/angle-and-windows-ink-a-new-test-version-of-krita-for-windows/ It would help if you can try it for a bit, and help fill in the short survey so we can see how well it works. We've also decided to include this in the next Krita release. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 384447] Optional window decoration button for fullscreen
https://bugs.kde.org/show_bug.cgi?id=384447 --- Comment #3 from Thomas Pfeiffer --- Actually, thinking about it more, I came to the same conclusion as you, Martin (before reading your comment): In the current state, this would be a big problem. What OS X does with fullscreen windows is still showing the titlebar if the cursor is pushed to the top of the screen. That would make having that titlebar button perfectly fine, but it would be a needed dependency. About OS X not having a maximize button: It does not have a separate button for it, but it does have the feature: You can maximize a window by pressing alt and clicking the fullscreen button. It's not the default behavior at all, but the functionality is there. Would such a feature be feasible / make sense form KWin's perspective? -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 384454] lag when working on canvas
https://bugs.kde.org/show_bug.cgi?id=384454 --- Comment #2 from Jess --- Got it to work by going to "configure krita" -> "performance" checking "enable performance logging" and unchecking "performance reporting" and then restarting my computer, that seemed do the trick. But if it does happen again i'll try what you suggested, thank you for replying though! I will try the test version and fill out the survey. On Thu, Sep 7, 2017 at 3:05 AM, Alvin Wong wrote: > https://bugs.kde.org/show_bug.cgi?id=384454 > > Alvin Wong changed: > >What|Removed |Added > > > CC||alvinhoc...@gmail.com > Resolution|--- |WAITINGFORINFO > Component|CPU Canvas |OpenGL Canvas > Status|UNCONFIRMED |NEEDSINFO > > --- Comment #1 from Alvin Wong --- > Since you left out the most important OS information on the bug report, we > can't really get anything useful out of it... but judging by your symptoms > it > would very likely be the Intel driver bug... > > If you are using Windows and is on a system with Intel HD Graphics, then > it is > most definitely a bug in the Intel drivers. See Bug 360601 > > ** The current workaround would be to go to "Configure Krita" -> "Display" > and > uncheck OpenGL. ** Please reply so we know if this works or not. > > --- > > We're working on another way of handling the canvas display which should > work > better with the Intel drivers, and we have a test version available: > > https://krita.org/en/item/angle-and-windows-ink-a-new- > test-version-of-krita-for-windows/ > > It would help if you can try it for a bit, and help fill in the short > survey so > we can see how well it works. We've also decided to include this in the > next > Krita release. > > -- > You are receiving this mail because: > You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 384447] Optional window decoration button for fullscreen
https://bugs.kde.org/show_bug.cgi?id=384447 --- Comment #4 from Thomas Pfeiffer --- See Firefox as an example: When using its built-in fullscreen mode, the way to get back is by pushing the cursor against the screen edge, which reveals a custom title bar with a "restore" button. Having that but with KWin drawing the title bar would be the equivalent for a Kwin-managed fullscreen mode. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 384458] New: some web sites unreachable behind proxy
https://bugs.kde.org/show_bug.cgi?id=384458 Bug ID: 384458 Summary: some web sites unreachable behind proxy Product: neon Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Packages User Edition Assignee: neon-b...@kde.org Reporter: cemalettink...@gmail.com CC: j...@jriddell.org, neon-b...@kde.org, sit...@kde.org Target Milestone: --- Hello, I recenlty migrated to kde neon from ubuntu 16.04 . I configured firefox,kde, and system to use proxy server. But, some web sites i.e planetkde.org unreachble on firefox. firefox says proxy server taking too long to respond. but, i can reach google etc. at same time. i had never issue like that when i used ubuntu.if you need addtioanal log, please let me know. Thank you. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 384456] plasma-discover doesn't have libkf5declarative-dev listed as a build dep
https://bugs.kde.org/show_bug.cgi?id=384456 --- Comment #1 from Harald Sitter --- https://packaging.neon.kde.org/plasma/plasma-discover.git/tree/debian/control?h=Neon/unstable&id=37b11bcdd876e6b8290fbb605172a0490d45e3a2#n22 I don't see how this could not be installed. The bdep is there for years. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-ktexteditor] [Bug 384459] New: Text folding becomes invalid after file external update
https://bugs.kde.org/show_bug.cgi?id=384459 Bug ID: 384459 Summary: Text folding becomes invalid after file external update Product: frameworks-ktexteditor Version: 5.37.0 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: kwrite-bugs-n...@kde.org Reporter: w01dn...@gmail.com Target Milestone: --- If there is an opened file with some parts folded and some external change comes folding after (or which includes) that change becomes invalid — keeps old line numbers and doesn't match region anymore. How to reproduce: 1. Open some file which has regions for folding (C++, XML, etc) in Kate or KWrite. 2. Fold some region. 3. Open that file other text editor, e.g. vim, and add new line inside of that region. 4. Back to Kate/KWrite, and update file. Actual results: End of folding is broken. Expected results: Folding is either unfolded or recalculated based on new start and end of region. As Kate keeps foldings after restart unnoticed refresh may lead to very strange folds especially after VCS code update and many lines removed/added. I'm not sure this is the right place, but at least bug reproduced with both Kate and KWrite. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 381630] Crash in wl_proxy_create_wrapper in QtWayland after window destruction
https://bugs.kde.org/show_bug.cgi?id=381630 Kai Uwe Broulik changed: What|Removed |Added CC||k...@privat.broulik.de --- Comment #16 from Kai Uwe Broulik --- Reliably happens after closing the panel controller. The ComboBox in Containment Actions only crashes in a multi screen setup, however. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 379669] KDevelop continues to hang on exit in itemrepository.h [Bucket::deleteItem]
https://bugs.kde.org/show_bug.cgi?id=379669 Kevin Funk changed: What|Removed |Added CC||david.nolden.kde@art-master ||.de, m...@milianw.de --- Comment #13 from Kevin Funk --- Confirmed, it's still not fixed. I'd really like this to get fixed *now* but it's over my head -- I don't understand the root cause. I'm afraid we'll have to resort using Rene's patch in order to at least fix the constant hangs-on-exit or CPU churn for our end users... If someone else from the KDevelop core team could have a look at this issue that'b appreciated. It's daunting to debug though. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 384460] New: "Plastik" is not the default theme.
https://bugs.kde.org/show_bug.cgi?id=384460 Bug ID: 384460 Summary: "Plastik" is not the default theme. Product: plasmashell Version: master Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Look & Feel package Assignee: plasma-b...@kde.org Reporter: teu...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 A "flat" design removes the distinction between navigation controls and content. Historically, navigation controls such as buttons were shaded, or given 3D relief, to distinguish them from the application or web page's content. https://www.theregister.co.uk/2017/09/05/flat_uis_designs_are_22_per_cent_slower_official/ -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 384460] "Plastik" is not the default theme.
https://bugs.kde.org/show_bug.cgi?id=384460 Teunizz changed: What|Removed |Added CC||teu...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kconfigwidgets] [Bug 384461] New: PyKF5 bindings: no way to construct a KColorScheme from Python
https://bugs.kde.org/show_bug.cgi?id=384461 Bug ID: 384461 Summary: PyKF5 bindings: no way to construct a KColorScheme from Python Product: frameworks-kconfigwidgets Version: 5.37.0 Platform: Archlinux Packages OS: All Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: kdelibs-b...@kde.org Reporter: flying-sh...@web.de Target Milestone: --- When building KConfigWidgets, the only non-copying constructor for KColorScheme is skipped by some rule: [...] KColorScheme(const KColorScheme & __0); [...] // Discarded CONSTRUCTOR on line 327 'KColorScheme' (by Qt5Ruleset.py:FunctionRuleDb[11],function_discard) [...] Also, there seems to be no way to customize templates for the binding generator (please correct me if i’m wrong), so this bug isn’t fixable until the sip customizations in extra-cmake-modules are modified to allow custom templates per project. -- You are receiving this mail because: You are watching all bug changes.
[kopete] [Bug 173261] kopete can't change avatar
https://bugs.kde.org/show_bug.cgi?id=173261 Matteo Croce changed: What|Removed |Added Resolution|WAITINGFORINFO |WONTFIX Status|NEEDSINFO |RESOLVED --- Comment #3 from Matteo Croce --- MSN has been abandoned -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 384460] "Plastik" is not the default theme.
https://bugs.kde.org/show_bug.cgi?id=384460 Kai Uwe Broulik changed: What|Removed |Added Resolution|--- |WONTFIX CC||k...@privat.broulik.de Status|UNCONFIRMED |RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 377338] Kontact crashes often when trying to select an addressee via the address book, for a mail sent via Kmail.
https://bugs.kde.org/show_bug.cgi?id=377338 Geoffrey changed: What|Removed |Added CC||l...@cvbt-web.org --- Comment #5 from Geoffrey --- I have the same problem: Kmail>Compose>Select "It" starts loading my address books and then - crash - and bug report dialog box. I just added a new contact. I don't think it was happening before that. I have a backtrace but don't see how to attach it. Would you like me to file a separate bug report? -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kconfigwidgets] [Bug 384461] PyKF5 bindings: no way to construct a KColorScheme from Python
https://bugs.kde.org/show_bug.cgi?id=384461 --- Comment #1 from Phil Schaf --- This bug is fixed in shaheed’s fork of extra-cmake-modules: https://github.com/ShaheedHaque/extra-cmake-modules -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 384346] Keep the kdenlive buildscript in the git repo so we can send patches to fix it
https://bugs.kde.org/show_bug.cgi?id=384346 carion.nico...@gmail.com changed: What|Removed |Added CC||carion.nico...@gmail.com --- Comment #1 from carion.nico...@gmail.com --- May I ask why you're not building directly from the git version ? -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 378222] SDDM-kcm doesn't change the breeze sddm theme background if the new background image name is same as the old name
https://bugs.kde.org/show_bug.cgi?id=378222 Dr. Chapatin changed: What|Removed |Added CC||yy...@gmx.com -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kconfigwidgets] [Bug 384461] PyKF5 bindings: no way to construct a KColorScheme from Python
https://bugs.kde.org/show_bug.cgi?id=384461 Phil Schaf changed: What|Removed |Added CC||srha...@theiet.org, ||steve...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 363548] file area becomes inaccessible for the mouse after opening a file on hidpi screen when using a multi monitor setting
https://bugs.kde.org/show_bug.cgi?id=363548 --- Comment #33 from Mads --- To clarify: dolphin does not appear to have this unclickable file area issue anymore if using: - kde-frameworks 5.37 - dolphin 17.08.0 - plasma 5.10.0 - Qt 5.9.1 - modesetting ddx - QT_SCREEN_SCALE_FACTORS="2;2" There might still be an issue at play, but that might belong to another bugreport (scaling variable set for non-existing outputs (or vice versa) leads to high cpu usage on plasmashell process and erroneous scaling on outputs that are actually connected) -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 384346] Keep the kdenlive buildscript in the git repo so we can send patches to fix it
https://bugs.kde.org/show_bug.cgi?id=384346 --- Comment #2 from alberto --- Im using the build script found on the wiki https://community.kde.org/Kdenlive/Development/KF5#A_build_scripts what do you mean by not building directly from the git version? The script downloads the git version It builds important dependences as well But its a text file uploaded on a wiki, not really under git -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 363548] file area becomes inaccessible for the mouse after opening a file on hidpi screen when using a multi monitor setting
https://bugs.kde.org/show_bug.cgi?id=363548 --- Comment #34 from Wim Delvaux --- and also not if you use context menues to start programs. It only happens to me if I click directly no a file and then only for certain programs. E.g. dragon player seems to work, vlc does not -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 384462] New: Maximize effect does not apply to wayland clients
https://bugs.kde.org/show_bug.cgi?id=384462 Bug ID: 384462 Summary: Maximize effect does not apply to wayland clients Product: kwin Version: git master Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: k...@privat.broulik.de Target Milestone: --- When maximizing a Wayland client it is not animated. X clients animate just fine. When doing so I noticed that the order and amount of signals emitted is different for the two: Maximizing an X client: Shape changed old was QRect(0,0 682x512) Shape changed old was QRect(0,0 1024x768) Shape changed old was QRect(0,0 682x512) Maximized changed true true Maximizing a Wayland client: Shape changed old was QRect(342,260 682x512) Maximized changed true true Shape changed old was QRect(342,260 682x512) -- You are receiving this mail because: You are watching all bug changes.
[k3b] [Bug 381074] [MATSHITA BD-MLT UJ240AS] Does not write image "debian-8.8.0-amd64-BD-1.iso"
https://bugs.kde.org/show_bug.cgi?id=381074 --- Comment #74 from Cristian Aravena Romero --- (In reply to Cristian Aravena Romero from comment #72) [...] > (In reply to Thomas Schmitt from comment #70) > > > [...] > > > $ fgrep -r MEDIA_WRITABLE_DVD';' . > > ./libk3b/projects/videodvd/k3bvideodvddoc.cpp:return > > K3b::Device::MEDIA_WRITABLE_DVD; > > ./libk3b/jobs/k3biso9660imagewritingjob.cpp:mt = > > K3b::Device::MEDIA_WRITABLE_DVD; > > ./libk3b/jobs/k3biso9660imagewritingjob.cpp:mt = > > K3b::Device::MEDIA_WRITABLE_DVD; > > caravena@caravena-530U3C-530U4C:~/Projects/k3b/k3b$ fgrep -r > MEDIA_WRITABLE_DVD';' . > ./libk3b/projects/videodvd/k3bvideodvddoc.cpp:return > K3b::Device::MEDIA_WRITABLE_DVD; > caravena@caravena-530U3C-530U4C:~/Projects/k3b/k3b$ > ./libk3b/projects/videodvd/k3bvideodvddoc.cpp:return > K3b::Device::MEDIA_WRITABLE_DVD; > bash: ./libk3b/projects/videodvd/k3bvideodvddoc.cpp:: No existe el archivo o > el directorio > caravena@caravena-530U3C-530U4C:~/Projects/k3b/k3b$ > ./libk3b/jobs/k3biso9660imagewritingjob.cpp:mt = > K3b::Device::MEDIA_WRITABLE_DVD; > bash: ./libk3b/jobs/k3biso9660imagewritingjob.cpp:: No existe el archivo o > el directorio > caravena@caravena-530U3C-530U4C:~/Projects/k3b/k3b$ > ./libk3b/jobs/k3biso9660imagewritingjob.cpp:mt = > K3b::Device::MEDIA_WRITABLE_DVD; > bash: ./libk3b/jobs/k3biso9660imagewritingjob.cpp:: No existe el archivo o > el directorio Hello, Help... Regards, -- Cristian -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 384462] Maximize effect does not apply to wayland clients
https://bugs.kde.org/show_bug.cgi?id=384462 --- Comment #1 from Kai Uwe Broulik --- Output with new geometries: X client Shape changed old was QRect(432,232 682x512) now is QRect(432,232 682x508) Shape changed old was QRect(0,0 1024x768) now is QRect(0,0 1024x768) Shape changed old was QRect(432,232 682x512) now is QRect(0,0 1024x768) Maximized changed true true Wayland client: Shape changed old was QRect(251,350 1024x768) now is QRect(251,350 1024x768) Maximized changed true true Shape changed old was QRect(251,350 1024x768) now is QRect(0,0 1024x768) (this is the output from when double clicking the title bar to maximize, I do get geometry changed events when moving the window, obviously, but in the instance of maximizing there's some superfluous events) -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 363548] file area becomes inaccessible for the mouse after opening a file on hidpi screen when using a multi monitor setting
https://bugs.kde.org/show_bug.cgi?id=363548 --- Comment #35 from Kai Uwe Broulik --- @Mads So the issue still persists with KDE Frameworks 5.37 in your normal setup (ie. when you don't set it to 2;2 manually)? -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 381387] display brightness is increased when come back from closed lid
https://bugs.kde.org/show_bug.cgi?id=381387 Sebastian Kügler changed: What|Removed |Added Assignee|plasma-de...@kde.org|plasma-b...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[k3b] [Bug 380067] [MATSHITA BD-MLT UJ240AS] :-( unable to WRITE@LBA=6d9a00h: Input/output error
https://bugs.kde.org/show_bug.cgi?id=380067 --- Comment #51 from Cristian Aravena Romero --- Hello, What do I do now? Regards, -- Cristian -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 384185] Markdown backend does not reload automatically if the file has changed
https://bugs.kde.org/show_bug.cgi?id=384185 Julian Wolff changed: What|Removed |Added Resolution|--- |FIXED Latest Commit||https://commits.kde.org/oku ||lar/e3747ca3fd9b9926ff8c528 ||79da7fca1a620fef5 Status|UNCONFIRMED |RESOLVED --- Comment #9 from Julian Wolff --- Git commit e3747ca3fd9b9926ff8c52879da7fca1a620fef5 by Julian Wolff. Committed on 07/09/2017 at 11:18. Pushed by jwolff into branch 'master'. Fix automatic reload of files saved with QSaveFile Summary: Files saved with QSaveFile don't get dirty. They are deleted and replaced. Thus, inotify and KDirWatch don't emit a "dirty" signal (which is the correct behaviour). Listening for the "created" signal of KDirWatch allows us to get notified on replaced files. Test Plan: Opened a markdown document in Okular. Edited and saved the document with Kate. The file is reloaded in Okular as expected. Reviewers: aacid Reviewed By: aacid Subscribers: sander, rkflx, #okular Tags: #okular Differential Revision: https://phabricator.kde.org/D7671 M +1-0part.cpp https://commits.kde.org/okular/e3747ca3fd9b9926ff8c52879da7fca1a620fef5 -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 384463] New: can't search on update page
https://bugs.kde.org/show_bug.cgi?id=384463 Bug ID: 384463 Summary: can't search on update page Product: Discover Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: discover Assignee: aleix...@kde.org Reporter: sit...@kde.org Target Milestone: --- - have updates avialable - go to updates page - type something in the search field - nothing happens Seeing as the hint text on the field says 'Search in Updates' it probably should filter the update model? Or well, not search in Updates but instead everything? -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 384464] New: Message window does not display Chinese characters
https://bugs.kde.org/show_bug.cgi?id=384464 Bug ID: 384464 Summary: Message window does not display Chinese characters Product: kmail2 Version: 5.6.0 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: UI Assignee: kdepim-b...@kde.org Reporter: metkome...@gmail.com Target Milestone: --- Chinese characters are not displayed in KMail's message window. I tried all possible encodings (from the display menu) and different fonts, in particular Chinese character fonts that display alright in every other KDE application. Whe I answer the email, the cited text looks correct, so it's a problem of the message viewer only (and not the composer window). You can replicate it by sending yourself a message with some Chinese characters from a webpage, for example. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 384465] New: With Compact Flash Card Created date in thumbnails is wrong
https://bugs.kde.org/show_bug.cgi?id=384465 Bug ID: 384465 Summary: With Compact Flash Card Created date in thumbnails is wrong Product: digikam Version: 5.6.0 Platform: MS Windows OS: MS Windows Status: UNCONFIRMED Severity: normal Priority: NOR Component: Import-Rename Assignee: digikam-bugs-n...@kde.org Reporter: igor...@visi1.org Target Milestone: --- Created attachment 107731 --> https://bugs.kde.org/attachment.cgi?id=107731&action=edit compact flash with Created Date wrong Description: In "Import Window", with only Compact Flash Card "Created date" in thumbnails is wrong but the "Metadata date" is correct. Software ver: digiKam v.5.6.-01-win64 OS: Microsoft OS-version: Win7-64bit. Reproducibility: always Steps: 1) A Compact Flash card in a Card Readers plug in and I go on Import menu. 2) "Import Window" shows all the thumbnails with the "Created date: 31/12/1979 23:00" but in the "Metadata properties" the dates is correct. A) I tested this issue with other CF (Compact Flash)card also of the other Camera but the "Created date" always is 31/12/1979 23:00". B) If I connect a SD card the "Creates date" is in sync with metadata. PS: I tested this also in a old version for windows "digiKam-installer-4.12.0-win32" with the same issue. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 363548] file area becomes inaccessible for the mouse after opening a file on hidpi screen when using a multi monitor setting
https://bugs.kde.org/show_bug.cgi?id=363548 --- Comment #36 from Mads --- Oh, I managed to not be clear on that, sorry! No, I can't reproduce the no-clickable issue at all anymore. So for me, this bug is resolved. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 363548] file area becomes inaccessible for the mouse after opening a file on hidpi screen when using a multi monitor setting
https://bugs.kde.org/show_bug.cgi?id=363548 Kai Uwe Broulik changed: What|Removed |Added Status|REOPENED|RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are watching all bug changes.
[k3b] [Bug 381074] [MATSHITA BD-MLT UJ240AS] Does not write image "debian-8.8.0-amd64-BD-1.iso"
https://bugs.kde.org/show_bug.cgi?id=381074 --- Comment #75 from Thomas Schmitt --- Hi, > Help... I am riddling what we see with your fgrep run. Did you copy+paste my fgrep line together with my three output lines ? Somehow the shell "bash" tried to execute the lines which were found by my local fgrep. Your local fgrep found only one, probably because Leslie's change is already in your local K3B git copy. bash complains about non-existence of the files instead of complaining about lack of x-permission. This is because my fgrep output lines have the filenames with trailing ':'. They only exist without that ':'. Whatever, this is not related to K3B's functionality. Actually i did not expect that you execute that fgrep yourself. I was just showing the query by which i found the decisive spot in the code. Important to K3B would be the questions: - Did the burn run with the Debian ISO succeed ? (Your image https://bugsfiles.kde.org/attachment.cgi?id=107724 shows it at 68 percent.) - Did you already verify the result as proposed by Debian CD FAQ ? https://www.debian.org/CD/faq/#verify I translate it to these shell commands: /sbin/isosize -x debian-9.1.0-amd64-BD-1.iso which is supposed to say: sector count: 11223478, sector size: 2048 and dd if=/dev/sr0 count=11223478 bs=2048 | sha512sum which is supposed to say: 81761e602af6d0e0ffde2d102c706c220e9ff0d31a612ea9ae1db1688c24cdf2a0bf45f02f738dc96651a5a64ae22d60527fe15549a195ab692b66bd669ea1d5 - according to https://cdimage.debian.org/debian-cd/current/amd64/jigdo-bd/SHA512SUMS If the SHA-512 sum is not 8176...a1d5, then compute the SHA-512 of the ISO by sha512sum debian-9.1.0-amd64-BD-1.iso to verify that the .iso image indeed yields the announced 8176...a1d5 If both answers are "yes", then the next quesition would be whether it boots on your machine. If "no" then it would not be K3B's fault, but i myself would be the one to inspect the boot process until the first Debian logo appears. Have a nice day :) Thomas -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 384465] With Compact Flash Card Created date in thumbnails is wrong
https://bugs.kde.org/show_bug.cgi?id=384465 caulier.gil...@gmail.com changed: What|Removed |Added CC||caulier.gil...@gmail.com Component|Import-Rename |Import-IconView -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 384359] Regression in 5.6.0 / 17.08 compared to 17.04.3: MySQL load always 100%, constant queries, extremely sluggisch behaviour
https://bugs.kde.org/show_bug.cgi?id=384359 --- Comment #2 from Gunter Ohrner --- Created attachment 107732 --> https://bugs.kde.org/attachment.cgi?id=107732&action=edit Screenshot Akonadiconsole Query Sequence Debugger The query debugger query sequence view "nicely" illustrates the problem: The second query is very slow with 650 ms execution time per call, and uses most of the processing time. The sum shown as "TOTAL" basically resembles wall clock time, as Akonadi loads the CPU 100% (actually mysqld). This never seems to finish, at least it ran for lots of hours several times, before I finally terminated it using "akonadictl stop". -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 384359] Regression in 5.6.0 / 17.08 compared to 17.04.3: MySQL load always 100%, constant queries, extremely sluggisch behaviour
https://bugs.kde.org/show_bug.cgi?id=384359 Gunter Ohrner changed: What|Removed |Added Product|kmail2 |Akonadi Component|general |IMAP resource CC||kdepim-b...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 384359] Regression in 5.6.0 / 17.08 compared to 17.04.3: MySQL load always 100%, constant queries, extremely sluggisch behaviour
https://bugs.kde.org/show_bug.cgi?id=384359 --- Comment #3 from Gunter Ohrner --- Not quite sure if really IMAP ressource is the culprit, but I think so. How can I find out who or what is triggering all those (slow) queries? -- You are receiving this mail because: You are watching all bug changes.
[k3b] [Bug 381074] [MATSHITA BD-MLT UJ240AS] Does not write image "debian-8.8.0-amd64-BD-1.iso"
https://bugs.kde.org/show_bug.cgi?id=381074 --- Comment #76 from Thomas Schmitt --- Hi, i forgot to mention that dd if=/dev/sr0 count=11223478 bs=2048 | sha512sum will last about 1200 seconds at average 4x read speed and probably make some noise when it reaches 6x or 8x speed near the end. Have a nice day :) Thomas -- You are receiving this mail because: You are watching all bug changes.
[k3b] [Bug 381074] [MATSHITA BD-MLT UJ240AS] Does not write image "debian-8.8.0-amd64-BD-1.iso"
https://bugs.kde.org/show_bug.cgi?id=381074 --- Comment #77 from Thomas Schmitt --- Hi, forget my first question whether the burn run ended successfully. I just found https://bugsfiles.kde.org/attachment.cgi?id=107723 which looks very good. Effective speed around 2x with Defect Management enabled indicates a good relation between drive and medium So there only remains the question whether the BD-R yields the same blocks as written (plus some trailing garbage which we keep dd from reading by the "count=" option). This will be answered by the run of dd if=/dev/sr0 count=11223478 bs=2048 | sha512sum Have a nice day :) Thomas -- You are receiving this mail because: You are watching all bug changes.
[k3b] [Bug 380067] [MATSHITA BD-MLT UJ240AS] :-( unable to WRITE@LBA=6d9a00h: Input/output error
https://bugs.kde.org/show_bug.cgi?id=380067 --- Comment #52 from Thomas Schmitt --- Hi, > What do I do now? About the failure to burn successfully (Bug 380067): If it happens again, gather experience about which media fail and which succeed. We found no evidence that K3B or growisofs are to blame for the failures. It must be in the relation of drive and computer or of drive and media. @Leslie: This is hardly a duplicate of Bug 384443 which says "It does not record its maximum speed". The short answer is: Because Defect Management is enabled by default and thus the drive writes and checkreads alternatingly. Can you please split these two bugs again ? I dimly remember we had this topic already ... Have a nice day :) Thomas -- You are receiving this mail because: You are watching all bug changes.
[k3b] [Bug 381074] [MATSHITA BD-MLT UJ240AS] Does not write image "debian-8.8.0-amd64-BD-1.iso"
https://bugs.kde.org/show_bug.cgi?id=381074 --- Comment #78 from Cristian Aravena Romero --- Hello, (In reply to Thomas Schmitt from comment #75) [...] > Important to K3B would be the questions: > > - Did the burn run with the Debian ISO succeed ? > (Your image > https://bugsfiles.kde.org/attachment.cgi?id=107724 > shows it at 68 percent.) Yes!: https://bugs.kde.org/attachment.cgi?id=107723 > - Did you already verify the result as proposed by Debian CD FAQ ? > https://www.debian.org/CD/faq/#verify > I translate it to these shell commands: > > /sbin/isosize -x debian-9.1.0-amd64-BD-1.iso caravena@caravena-530U3C-530U4C:/media/mis-doc/ISO/debian$ LANGUAGE=C isosize -x debian-9.1.0-amd64-BD-1.iso sector count: 11223478, sector size: 2048 > which is supposed to say: sector count: 11223478, sector size: 2048 > and > > dd if=/dev/sr0 count=11223478 bs=2048 | sha512sum caravena@caravena-530U3C-530U4C:/media/mis-doc/ISO/debian$ LANGUAGE=C dd if=/dev/sr0 count=11223478 bs=2048 | sha512sum 11223478+0 records in 11223478+0 records out 22985682944 bytes (23 GB, 21 GiB) copied, 1217,61 s, 18,9 MB/s 81761e602af6d0e0ffde2d102c706c220e9ff0d31a612ea9ae1db1688c24cdf2a0bf45f02f738dc96651a5a64ae22d60527fe15549a195ab692b66bd669ea1d5 - > which is supposed to say: > 81761e602af6d0e0ffde2d102c706c220e9ff0d31a612ea9ae1db1688c24cdf2a0bf45f02f738 > dc96651a5a64ae22d60527fe15549a195ab692b66bd669ea1d5 - > according to > https://cdimage.debian.org/debian-cd/current/amd64/jigdo-bd/SHA512SUMS > > If the SHA-512 sum is not 8176...a1d5, then compute the SHA-512 of the ISO > by > > sha512sum debian-9.1.0-amd64-BD-1.iso > > to verify that the .iso image indeed yields the announced 8176...a1d5 > > If both answers are "yes", then the next quesition would be whether it > boots on your machine. If "no" then it would not be K3B's fault, but i > myself would be the one to inspect the boot process until the first Debian > logo appears. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-qqc2-desktop-style] [Bug 384466] New: Crash running some code
https://bugs.kde.org/show_bug.cgi?id=384466 Bug ID: 384466 Summary: Crash running some code Product: frameworks-qqc2-desktop-style Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: notm...@gmail.com Reporter: aa...@kde.org CC: k...@davidedmundson.co.uk Target Milestone: --- I'm running some qml tests on some non public code (sorry) and got this crash. valgrind trace follows ==27797== Process terminating with default action of signal 11 (SIGSEGV): dumping core ==27797== Access not within mapped region at address 0x0 ==27797==at 0x21E6FE06: KQuickStyleItem::initStyleOption() (kquickstyleitem.cpp:588) ==27797==by 0x21E69DE2: KQuickStyleItem::sizeFromContents(int, int) (kquickstyleitem.cpp:779) ==27797==by 0x21E6A9C4: KQuickStyleItem::updateSizeHint() (kquickstyleitem.cpp:977) ==27797==by 0x21E6DF71: KQuickStyleItem::qt_static_metacall(QObject*, QMetaObject::Call, int, void**) (moc_kquickstyleitem_p.cpp:612) ==27797==by 0x7599801: ??? (in /usr/lib/libQt5Qml.so.5.9.1) ==27797==by 0x7620418: ??? (in /usr/lib/libQt5Qml.so.5.9.1) ==27797==by 0x76236D5: ??? (in /usr/lib/libQt5Qml.so.5.9.1) ==27797==by 0x7624E68: ??? (in /usr/lib/libQt5Qml.so.5.9.1) ==27797==by 0x762175F: ??? (in /usr/lib/libQt5Qml.so.5.9.1) ==27797==by 0x7622504: ??? (in /usr/lib/libQt5Qml.so.5.9.1) ==27797==by 0x7624BA9: ??? (in /usr/lib/libQt5Qml.so.5.9.1) ==27797==by 0x7624E68: ??? (in /usr/lib/libQt5Qml.so.5.9.1) ==27797== If you believe this happened as a result of a stack ==27797== overflow in your program's main thread (unlikely but ==27797== possible), you can try to increase the size of the ==27797== main thread stack using the --main-stacksize= flag. ==27797== The main thread stack size used in this run was 8388608. I think this is on tear down, so may be that you're trying to update something that is not there anymore? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 383498] Mount media when clicking on it without having to click the "mount" button besides
https://bugs.kde.org/show_bug.cgi?id=383498 David Edmundson changed: What|Removed |Added CC||k...@davidedmundson.co.uk --- Comment #1 from David Edmundson --- Automatically mounting is the intended behaviour, and (as unhelpful as this comment is) it works here. Is this just on your personal machine or Limux too? Can you run "solid-hardware5 listen" whilst you plug in the disk then try to open it with the "open with file manager" -- You are receiving this mail because: You are watching all bug changes.
[kruler] [Bug 384435] Regression - Rotation button missing from ruler.
https://bugs.kde.org/show_bug.cgi?id=384435 --- Comment #3 from Paul --- (In reply to Christoph Feck from comment #2) > The Rotate command is also in the context menu, so you do not need to use > the keyboard. Yes, I was aware of that also. :) Previously it was possible to place the rotate button(s) on the ruler itself. Thus negating the need to right click to bring up the context menu and select rotate. Sorry, definitely a backward step in terms of usability... The fewer mouse clicks / keystrokes / whatever, the better. -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 361725] Yakuake task appears in the task manager some times, when opening Yakuake with hotkey
https://bugs.kde.org/show_bug.cgi?id=361725 michele mazza changed: What|Removed |Added CC||michele.ma...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 384276] [kstars 2.8.2] Wrong placement of asteroid Florence
https://bugs.kde.org/show_bug.cgi?id=384276 Jasem Mutlaq changed: What|Removed |Added Latest Commit||https://commits.kde.org/kst ||ars/d758bd02ca07ed6cb72c7ba ||8e23cc9e7377ab0b4 Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #2 from Jasem Mutlaq --- Git commit d758bd02ca07ed6cb72c7ba8e23cc9e7377ab0b4 by Jasem Mutlaq. Committed on 07/09/2017 at 12:55. Pushed by mutlaqja into branch 'master'. Fix inaccurate positions of asteroids, comets, and other solar system bodies. There were problem in multiple places, but the Earth ecliptic longitude from VSOP87 was not accurate. Valentin submitted improved Earth VSOP87 files with better accuracy which resolved the earth problem. Next, I made a few fixes to the asteroid class and now the solar system bodies positions are more accurate and very close to JPL Horizons results. Please double check and let me know if there are any major problems now. CCMAIL:kstars-de...@kde.org M +15 -5kstars/skyobjects/ksasteroid.cpp https://commits.kde.org/kstars/d758bd02ca07ed6cb72c7ba8e23cc9e7377ab0b4 -- You are receiving this mail because: You are watching all bug changes.
[k3b] [Bug 384443] [MATSHITA BD-MLT UJ240AS] It does not record its maximum speed
https://bugs.kde.org/show_bug.cgi?id=384443 Thomas Schmitt changed: What|Removed |Added CC||scdbac...@gmx.net --- Comment #2 from Thomas Schmitt --- Hi, the low effective speed is not a bug but a feature of formatted BD-R media. During writeing the freshly written blocks are read and compared with the data which are still in the drive buffer. This frequent change between writing and reading slows down overall speed. Especially if reading is not very successful. I.e. very low effectiive speed indicates a bad relation between drive and medium and announces failure to come soon. https://bugs.kde.org/attachment.cgi?id=107725 looks like good relation for 4x speed and mediocre for 6x speed. You may ask the drive with an unused medium for the speed list by dvd+rw-mediainfo /dev/sr0 which will reply something like Write Speed #0:8.0x4495=35968KB/s Write Speed #1:6.0x4495=26976KB/s Write Speed #2:4.0x4495=17984KB/s - Defect management can be avoided on BD-R media by adding -use-the-force-luke=spare=none to the list of extra options for growisofs. It will then skip formatting the BD-R medium before writing begins. In my olde Debian 8 K3B this would be: Pulldown menu: Settings Item: Configure K3B Side bar icon: Programs Tab: User Parameters Line: growisofs Click at column: Parameters Write the text: -use-the-force-luke=spare=none The BD-R will have full nominal capacity and will be burnt at increasing speed up to reaching full nominal speed near the end. Noise might be substantial. On BD-RE it cannot be avoided to format the medium. Above option might or might not lead to full speed. The medium will have nominal capacity. The only way to bring BD-RE to full speed is the option stream_recording=on of backend program cdrskin (or command -stream_recording of xorriso, or burn option Stream Recording in Xfburn). Have a nice day :) Thomas -- You are receiving this mail because: You are watching all bug changes.
[k3b] [Bug 384443] [MATSHITA BD-MLT UJ240AS] It does not record its maximum speed
https://bugs.kde.org/show_bug.cgi?id=384443 --- Comment #3 from Thomas Schmitt --- I meant "the only sure way to bring BD-RE to full speed". Some few drives burn at full speed if there is no Spare Area with replacement blocks. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-solid] [Bug 379516] hide loop devices created by snapd
https://bugs.kde.org/show_bug.cgi?id=379516 Greg Lepore changed: What|Removed |Added CC||g...@rhobard.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 383498] Mount media when clicking on it without having to click the "mount" button besides
https://bugs.kde.org/show_bug.cgi?id=383498
Tobias Leupold changed:
What|Removed |Added
CC||tobias.leup...@gmx.de
--- Comment #2 from Tobias Leupold ---
What do you mean with "or Limux too?"?
Here's the output:
$ solid-hardware5 listen
Listening to add/remove events:
"/org/freedesktop/UDisks2/drives/UFD_3_2e0_Silicon_Power16G_P1503992734160100178"
has new interfaces: ("org.freedesktop.UDisks2.Drive")
Device Added:
udi =
'/org/freedesktop/UDisks2/drives/UFD_3_2e0_Silicon_Power16G_P1503992734160100178'
"/org/freedesktop/UDisks2/block_devices/sdb" has new interfaces:
("org.freedesktop.UDisks2.Block", "org.freedesktop.UDisks2.PartitionTable")
Device Added:
udi = '/org/freedesktop/UDisks2/block_devices/sdb'
"/org/freedesktop/UDisks2/block_devices/sdb1" has new interfaces:
("org.freedesktop.UDisks2.Block", "org.freedesktop.UDisks2.Filesystem",
"org.freedesktop.UDisks2.Partition")
Device Added:
udi = '/org/freedesktop/UDisks2/block_devices/sdb1'
No output is generated when I try to "Open with file manager" (which produces
the error described above) or actually mount the device via the "mount" button.
Also, I get the very same output if I have Dolphin open. When I click on the
device to view it, it's mounted, but also no additional output is genrerated.
--
You are receiving this mail because:
You are watching all bug changes.
[k3b] [Bug 381074] [MATSHITA BD-MLT UJ240AS] Does not write image "debian-8.8.0-amd64-BD-1.iso"
https://bugs.kde.org/show_bug.cgi?id=381074 --- Comment #79 from Thomas Schmitt --- Hi, the outcome of the sha512sum run indicates full success as far as K3B is concerned. This bug is indeed completely done. Have a nice day :) Thomas -- You are receiving this mail because: You are watching all bug changes.
[k3b] [Bug 381074] [MATSHITA BD-MLT UJ240AS] Does not write image "debian-8.8.0-amd64-BD-1.iso"
https://bugs.kde.org/show_bug.cgi?id=381074 --- Comment #80 from Cristian Aravena Romero --- Created attachment 107733 --> https://bugs.kde.org/attachment.cgi?id=107733&action=edit Running Debian 9.1.0 (In reply to Thomas Schmitt from comment #75) [...] > If both answers are "yes", then the next quesition would be whether it > boots on your machine. If "no" then it would not be K3B's fault, but i > myself would be the one to inspect the boot process until the first Debian > logo appears. I am attaching image .jpg running Debian 9.1.0 Regards, -- Cristian -- You are receiving this mail because: You are watching all bug changes.
[frameworks-qqc2-desktop-style] [Bug 384466] Crash running on a QGuiApplication
https://bugs.kde.org/show_bug.cgi?id=384466 Albert Astals Cid changed: What|Removed |Added Summary|Crash running some code |Crash running on a ||QGuiApplication -- You are receiving this mail because: You are watching all bug changes.
[frameworks-qqc2-desktop-style] [Bug 384466] Crash running on a QGuiApplication
https://bugs.kde.org/show_bug.cgi?id=384466 --- Comment #1 from Albert Astals Cid --- So we've dicovered this is because my application is a QGuiApplication and this code uses qApp->style() quite a lot, and that will crash, so either this needs to stop using qApp->style() or the plugin itself should not load if the app is a QGuiApplication instead of a QApplication -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 384467] New: Crash on KDE5.37.0
https://bugs.kde.org/show_bug.cgi?id=384467 Bug ID: 384467 Summary: Crash on KDE5.37.0 Product: kdeconnect Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: common Assignee: albertv...@gmail.com Reporter: mte90smanetta...@gmail.com Target Milestone: --- I compiled KDE Connect on Debian Sid with qt5 because the debian package has issues. After the compile I was expecting that was working because didn't reported errors on cmake or make. When I execute kdeconnect-cli: kdeconnect-cli: symbol lookup error: kdeconnect-cli: undefined symbol: _ZN19DaemonDbusInterface11deviceAddedERK7QString On Settings systems I get another error about an undefined symbol. How can I help to give more information to fix this problem? -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 383421] (Enhancement wish) Make Breeze Icons more distinctive
https://bugs.kde.org/show_bug.cgi?id=383421 --- Comment #21 from Paul --- (In reply to Christoph Feck from comment #12) > Please do not mix multiple issues in a single ticket. The breeze icons > follow specific design decisions, and this makes them flat, not 3D. It looks > like you might want to switch to a different icon theme. It's official: Users navigate flat UI designs 22 per cent slower. Put in some chrome and shade. https://www.theregister.co.uk/2017/09/05/flat_uis_designs_are_22_per_cent_slower_official/ Don't take it to heart, just couldn't resist the urge to post the link... :) -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 384463] can't search on update page
https://bugs.kde.org/show_bug.cgi?id=384463 Dr. Chapatin changed: What|Removed |Added CC||yy...@gmx.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 384462] Maximize effect does not apply to wayland clients
https://bugs.kde.org/show_bug.cgi?id=384462 Dr. Chapatin changed: What|Removed |Added CC||yy...@gmx.com -- You are receiving this mail because: You are watching all bug changes.
[k3b] [Bug 381074] [MATSHITA BD-MLT UJ240AS] Does not write image "debian-8.8.0-amd64-BD-1.iso"
https://bugs.kde.org/show_bug.cgi?id=381074 --- Comment #81 from Cristian Aravena Romero --- Hello, Thomas asked me to add this "K3b::Device::MEDIA_WRITABLE_BD;" in two places of the same file. And now in the official patch only a line is edited https://cgit.kde.org/k3b.git/commit/?id=a359173975e574c4cae62214f7de28648d14167c Regards, - Cristian -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 384455] Does not list application name
https://bugs.kde.org/show_bug.cgi?id=384455 --- Comment #2 from Aleix Pol --- Created attachment 107734 --> https://bugs.kde.org/attachment.cgi?id=107734&action=edit Plasma/5.10 Here's attached what it looks like for me. I used this flatpakref file for testing, because I couldn't find the one you used. Maybe you can provide it to me? https://dl.tingping.se/flatpak/gnome-twitch.flatpakref -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 383181] 'fix' dependencies to allow for updated mesa i386 drivers
https://bugs.kde.org/show_bug.cgi?id=383181 revan changed: What|Removed |Added CC||radu.margine...@gmail.com --- Comment #3 from revan --- Con confirm it also happens to me on KDE Neon with the https://launchpad.net/~paulo-miguel-dias/+archive/ubuntu/pkppa installed. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 383421] (Enhancement wish) Make Breeze Icons more distinctive
https://bugs.kde.org/show_bug.cgi?id=383421 --- Comment #22 from hotmusic...@mail.bg --- (In reply to Paul from comment #21) > (In reply to Christoph Feck from comment #12) > > Please do not mix multiple issues in a single ticket. The breeze icons > > follow specific design decisions, and this makes them flat, not 3D. It looks > > like you might want to switch to a different icon theme. > > It's official: Users navigate flat UI designs 22 per cent slower. > Put in some chrome and shade. > > https://www.theregister.co.uk/2017/09/05/ > flat_uis_designs_are_22_per_cent_slower_official/ > > Don't take it to heart, just couldn't resist the urge to post the link... :) Supporting with two hands! -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 384463] can't search on update page
https://bugs.kde.org/show_bug.cgi?id=384463 --- Comment #1 from Aleix Pol --- Yes, correct. At the moment what it does is to visually select the filtered ones. I didn't want to hide them because then maybe we'd want not to update them if "Update All" is pressed. Or yes? Weird UX anyway. We're looking into moving the search field altogether anyway, maybe that will be a better solution than figuring out a search use case that probably isn't even there. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 383823] flatpak standalone doesnt work
https://bugs.kde.org/show_bug.cgi?id=383823 --- Comment #4 from Aleix Pol --- https://cgit.kde.org/flatpak-kde-applications.git/tree/org.kde.discover.json Feel free to extend it to include flatpak, I'll be happy to review it and merge it if it works. :) -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 371820] Kipi plugins are working but with less features than gwenview was kde4 app
https://bugs.kde.org/show_bug.cgi?id=371820 sorath changed: What|Removed |Added CC||torokhov_...@mail.ru --- Comment #6 from sorath --- Current kipi-plugins is useless for many people who used it previously. Gwenview+Kipi was powerful and convinient tool for batch processing. Is it planning to backport (from digikam source code) or add similar functionality (as imagemagick frontend) like batch resizing, rotating, adding borders (as for single image) etc. to gwenview? -- You are receiving this mail because: You are watching all bug changes.
[kolourpaint] [Bug 384468] New: Copy and paste no work into same image
https://bugs.kde.org/show_bug.cgi?id=384468 Bug ID: 384468 Summary: Copy and paste no work into same image Product: kolourpaint Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: kolourpaint-supp...@lists.sourceforge.net Reporter: cdani...@gmail.com Target Milestone: --- Created attachment 107735 --> https://bugs.kde.org/attachment.cgi?id=107735&action=edit Image error Hi, I install kolorpaint in Deepin, but no work correctly. Copy and paste no work into same image -- You are receiving this mail because: You are watching all bug changes.
[kolourpaint] [Bug 384468] Copy and paste no work into same image
https://bugs.kde.org/show_bug.cgi?id=384468 --- Comment #1 from cDaniel GE --- Created attachment 107736 --> https://bugs.kde.org/attachment.cgi?id=107736&action=edit Gif error -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 380013] Could not locate service type file kservicetypes5/kwin-effect.desktop
https://bugs.kde.org/show_bug.cgi?id=380013 988a...@mail.ru changed: What|Removed |Added CC||988a...@mail.ru -- You are receiving this mail because: You are watching all bug changes.
[k3b] [Bug 381074] [MATSHITA BD-MLT UJ240AS] Does not write image "debian-8.8.0-amd64-BD-1.iso"
https://bugs.kde.org/show_bug.cgi?id=381074 --- Comment #82 from Thomas Schmitt --- Hi, > now in the official patch only a line is edited > https://cgit.kde.org/k3b.git/commit/?id=a359173975e574c4cae62214f7de28648d14167c This is not the fix for Bug 381074 but rather the cleanup after the fix plus a courageous move to allow BD media for "VideoDvdDoc" which talks of the typical filesystem structures of Video DVD. E.g. directory "VIDEO_TS". The decisive bug fix changeset is https://cgit.kde.org/k3b.git/commit/?id=329c969be1dbc3455d65925bcad32f4df3a5b428 where Leslie and i would still need to discuss the outdated comments. We'd both need to practice with git in order to keep the experiments away from the final fix. -- As for the courage in above changeset: The format requirements for Blu-ray Video differ from DVD video. With much caution read and compare https://en.wikipedia.org/wiki/Blu-ray#Data_format_standards https://en.wikipedia.org/wiki/DVD-Video and keep in mind that these requirements only apply to consumer electronics (aka "living room") video players. With general data storage or with video files which your computer can play from hard disk, there is no need to use UDF as filesystem or to have a "BDMV" directory. I know of no free tool on GNU/Linux which would produce the prescribed format for Blu-ray video. If K3B and its helper programs can do, i'd like to learn a URL to which i can send people who ask for Blu-ray video. - @Leslie: Maybe an amateurish idea, but how about you revoke all three new "| K3b::Device::MEDIA_WRITABLE_BD". I.e. the two fixes and the courageous one. Also remove comment "10" above the two bug fix lines. It is outdated now. Then commit the two MEDIA_WRITABLE_BD lines in https://cgit.kde.org/k3b.git/commit/?id=329c969be1dbc3455d65925bcad32f4df3a5b428 as official fix of Bug 381074. Leave out comment "10" and the qDebug(), of course. If you feel still ok with the MEDIA_WRITABLE_BD in k3bvideodvddoc.cpp, then better commit it separately. Have a nice day :) Thomas -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 380013] Could not locate service type file kservicetypes5/kwin-effect.desktop
https://bugs.kde.org/show_bug.cgi?id=380013 --- Comment #4 from 988a...@mail.ru --- I have the same bug on KDE 5.10.5. This actions can help: sudo ln -s /usr/share/kservicetypes5/kwinscript.desktop /usr/share/kservicetypes5/kwin-script.desktop sudo ln -s /usr/share/kservicetypes5/kwineffect.desktop /usr/share/kservicetypes5/kwin-effect.desktop As you see there is a mistake in filenames. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 369088] After upgrading from fedora 20 to 24 everything crashes on startup, KDE unusable
https://bugs.kde.org/show_bug.cgi?id=369088 --- Comment #10 from Martin Flöser --- (In reply to kde.org from comment #9) > It seems pretty complete to me. What do you think is missing? It isn't. It's lacking debug symbols. We don't have code lines, we don't have variable values, etc. etc. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 384457] Wrong render decoration on Nvidia
https://bugs.kde.org/show_bug.cgi?id=384457 Martin Flöser changed: What|Removed |Added Resolution|--- |INVALID Status|UNCONFIRMED |RESOLVED --- Comment #2 from Martin Flöser --- Sorry, but that is nothing we can influence. Please note that 3D hardware does not guarantee pixel perfect rendering. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 384447] Optional window decoration button for fullscreen
https://bugs.kde.org/show_bug.cgi?id=384447 --- Comment #5 from Martin Flöser --- > Would such a feature be feasible / make sense form KWin's perspective? As with all feature requests: if we had infinite developer time it would be feasible, everything is feasible then. With the limited resources we have any request (be it user or VDG) is getting pushed below the Wayland port. Anything which in some way could create a problem for the Wayland port is being pushed even further down. This would fall into this category as it would require different code for X11 and Wayland. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 383421] (Enhancement wish) Make Breeze Icons more distinctive
https://bugs.kde.org/show_bug.cgi?id=383421 --- Comment #23 from andreas --- I'm not sure if the header is right? make breeze more distinctiv or do you mean make oxygen fit plasma 5. maybe I also wrote in a way that was not friendly. sorry. two options: 1. submit patches for oxygen to support plasma 5 in a better way 2. fork breeze and make new higs this doesn't mean that I want accept patches to breeze but it would be better to have a fork and when the fork work quite good, we can merge. I would be very happy if someone is interested into solution 1 or 2. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 384462] Maximize effect does not apply to wayland clients
https://bugs.kde.org/show_bug.cgi?id=384462 Martin Flöser changed: What|Removed |Added Flags||Wayland+, X11- Component|wayland-generic |core --- Comment #2 from Martin Flöser --- This used to work in the past, given that I assume it's another Qt 5.9 regression. I'm not going to investigate prior to xdg shell v6 support landed. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 384457] Wrong render decoration on Nvidia
https://bugs.kde.org/show_bug.cgi?id=384457 --- Comment #3 from varlesh --- Disagree, see screen other elements and icons render right - with pixel align: https://i.imgur.com/sWXy8nI.png Also i'm report this bug on devtalk.nvidia.com forum: https://devtalk.nvidia.com/default/topic/1023706/linux/-kde-wrong-render-buttons-aurorae-decoration-on-nvidia/ -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 384442] ARM: bad pc in complaint if instruction changes pc
https://bugs.kde.org/show_bug.cgi?id=384442 --- Comment #1 from John Reiser --- Both problems can be solved by a special case for 'ldmdb' (LoaD Multiple registers, Decrementing the address Before each fetch). If either r15(==pc) or r13(==sp) is to be loaded, then assign the new value to a temporary, and perform the final assign-from-temporary-to-pc-or-sp only after all other registers have been fetched and assigned. This analysis can be done at translation time. The same analysis works for any 'ldm', although ldmdb has the most exposure because r15 and r13 appear before most other registers in the serial processing. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 384457] Wrong render decoration on Nvidia
https://bugs.kde.org/show_bug.cgi?id=384457 --- Comment #4 from varlesh --- Why RESOLVED INVALID? Why on Intel this render right but on NVidia not? -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 383421] (Enhancement wish) Make Breeze Icons more distinctive
https://bugs.kde.org/show_bug.cgi?id=383421 --- Comment #24 from Jens Reuterberg --- Paul: if you don't want people to take it to heart then why post that clickbait article in a bug list? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 383498] Mount media when clicking on it without having to click the "mount" button besides
https://bugs.kde.org/show_bug.cgi?id=383498 --- Comment #3 from David Edmundson --- I think I have your name confused with someone else... sorry. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 383498] Mount media when clicking on it without having to click the "mount" button besides
https://bugs.kde.org/show_bug.cgi?id=383498 --- Comment #4 from David Edmundson --- The fact that you see the error means we're trying to mount it, which is a good sign. Is there anything in the udisks2 log? sudo journalctl -u udisks2 -b -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 384469] New: [Regression] Not able to associate a notification sound to "This device can now be safely removed."
https://bugs.kde.org/show_bug.cgi?id=384469 Bug ID: 384469 Summary: [Regression] Not able to associate a notification sound to "This device can now be safely removed." Product: plasmashell Version: 5.10.5 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Device Notifier Assignee: plasma-b...@kde.org Reporter: pip@gmx.com Target Milestone: 1.0 "Event Notifications & Actions" lacks the ability to "Play a Sound" upon the notification "This device can now be safely removed." (was present in the old KDE4 version). -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 384442] ARM: bad pc in complaint if instruction changes pc
https://bugs.kde.org/show_bug.cgi?id=384442 --- Comment #2 from John Reiser --- Context: [valgrind-users] by Kacper Kowalski on 2017-08-31 and replies through the following week. * processor: 0 model name: ARMv7 Processor rev 10 (v7l) BogoMIPS: 132.00 Features: half thumb fastmult vfp edsp neon vfpv3 tls vfpd32 CPU implementer: 0x41 CPU architecture: 7 CPU variant: 0x2 CPU part: 0xc09 CPU revision: 10 Hardware: Freescale i.MX6 Quad/DualLite (Device Tree) Revision: Serial: Operating system info: cat /etc/openwrt_release DISTRIB_ID='OpenWrt' DISTRIB_RELEASE='15.05' DISTRIB_REVISION='r48153' DISTRIB_CODENAME='chaos_calmer' DISTRIB_TARGET='imx6/generic' DISTRIB_DESCRIPTION='OpenWrt Chaos Calmer 15.05' DISTRIB_TAINTS='no-all busybox' cat /proc/version Linux version 3.18.23 (gcc version 5.3.0 (OpenWrt GCC 5.3.0 r48153) ) #6 SMP Tue Jul 11 16:35:20 CEST 2017 Source code could be downloaded from: https://uclibc.org/downloads/uClibc-0.9.33.2.tar.bz2 Extracted chunks from trace output can be downloaded from: https://github.com/KKoovalsky/Valgrind-problems * (gdb) target remote | /usr/lib/valgrind/../../bin/vgdb --pid=8269 Remote debugging using | /usr/lib/valgrind/../../bin/vgdb --pid=8269 relaying data between gdb and process 8269 Reading symbols from /lib/ld-uClibc.so.0...done. Loaded symbols for /lib/ld-uClibc.so.0 0x04000e68 in _start () from /lib/ld-uClibc.so.0 (gdb) c Continuing. Reading in symbols for ldso/ldso/ldso.c...done. Reading symbols from /usr/lib/valgrind/vgpreload_core-arm-linux.so...done. Loaded symbols for /usr/lib/valgrind/vgpreload_core-arm-linux.so Reading symbols from /usr/lib/valgrind/vgpreload_memcheck-arm-linux.so...done. Loaded symbols for /usr/lib/valgrind/vgpreload_memcheck-arm-linux.so Reading symbols from /usr/lib/libboost_thread.so.1.64.0...(no debugging symbols found)...done. Loaded symbols for /usr/lib/libboost_thread.so.1.64.0 Reading symbols from /usr/lib/libboost_system.so.1.64.0...(no debugging symbols found)...done. Loaded symbols for /usr/lib/libboost_system.so.1.64.0 Reading symbols from /lib/libpthread.so.0...done. Loaded symbols for /lib/libpthread.so.0 Reading symbols from /usr/lib/libstdc++.so.6...done. Loaded symbols for /usr/lib/libstdc++.so.6 Reading symbols from /lib/libm.so.0...done. Loaded symbols for /lib/libm.so.0 Reading symbols from /lib/libgcc_s.so.1...done. Loaded symbols for /lib/libgcc_s.so.1 Reading symbols from /lib/libc.so.0...done. Loaded symbols for /lib/libc.so.0 Reading symbols from /usr/lib/libboost_atomic.so.1.64.0...(no debugging symbols found)...done. Loaded symbols for /usr/lib/libboost_atomic.so.1.64.0 Reading symbols from /lib/librt.so.0...done. Loaded symbols for /lib/librt.so.0 Reading symbols from /lib/libdl.so.0...done. Loaded symbols for /lib/libdl.so.0 * ==8269== Invalid read of size 4 ==8269==at 0x40058F8: _dl_get_ready_to_run (ldso.c:1396) ==8269== Address 0x7d80c624 is on thread 1's stack ==8269== 20 bytes below stack pointer ==8269== Program received signal SIGTRAP, Trace/breakpoint trap. _dl_get_ready_to_run (Reading in symbols for libc/sysdeps/linux/arm/crti.S...done. tpnt=0x4007ac0, load_addr=, auxvt=0x7d80ca48, envp=, argv=0x0) at ldso/ldso/ldso.c:1396 1396ldso/ldso/ldso.c: No such file or directory. Current language: auto The current source language is "auto; currently c". (gdb) bt #0 _dl_get_ready_to_run (tpnt=0x4007ac0, load_addr=, auxvt=0x7d80ca48, envp=, argv=0x0) at ldso/ldso/ldso.c:1396 #1 0x049be918 in _init () at libc/sysdeps/linux/arm/crti.S:22 Backtrace stopped: previous frame inner to this frame (corrupt stack?) * ==8269== Invalid read of size 4 ==8269==at 0x4A16E70: __uClibc_fini (__uClibc_main.c:304) ==8269==by 0x4A134BB: exit (_atexit.c:336) ==8269==by 0x4A1718F: __uClibc_main (__uClibc_main.c:511) ==8269==by 0x: ??? ==8269== Address 0x7d80ca0c is on thread 1's stack ==8269== 20 bytes below stack pointer ==8269== Program received signal SIGTRAP, Trace/breakpoint trap. __GI___uClibc_fini () at libc/misc/internals/__uClibc_main.c:304 304in libc/misc/internals/__uClibc_main.c (gdb) bt Reading in symbols for libc/stdlib/exit.c...done. #0 __GI___uClibc_fini () at libc/misc/internals/__uClibc_main.c:304 #1 0x04a134bc in __GI_exit (rv=0) at libc/stdlib/_atexit.c:336 #2 0x04a17190 in __uClibc_main (main=0x7d80cc04, argc=0752, argv=0x4a17190 <__uClibc_main+764>, app_init=0x0, app_fini=0x10680 <_fini>, rtld_fini=0x4000df0 <_dl_fini>, stack_end=0x7d80cc04) at libc/misc/internals/__uClibc_main.c:511 #3 0x in ?? () Backtrace stopped: previous frame identical to this frame (corrupt stack?) * -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 383125] single window mode is not respected across virtual desktops
https://bugs.kde.org/show_bug.cgi?id=383125 --- Comment #4 from avlas --- Thanks, sunweb, for helping clarifying the point :) -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 384455] Does not list application name
https://bugs.kde.org/show_bug.cgi?id=384455 --- Comment #3 from Aaron Honeycutt --- I got the flatpakref from flathub.org: https://flathub.org/repo/appstream/com.vinszent.GnomeTwitch.flatpakref -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 384470] New: Plasma crash and restart on-the-way-up during login
https://bugs.kde.org/show_bug.cgi?id=384470 Bug ID: 384470 Summary: Plasma crash and restart on-the-way-up during login Product: plasmashell Version: 5.10.5 Platform: Neon Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: georgeogood...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.10.5) Qt Version: 5.9.1 Frameworks Version: 5.37.0 Operating System: Linux 4.10.0-33-generic x86_64 Distribution: KDE neon User Edition 5.10 -- Information about the crash: I'd just entered my password at the display manager screen and hit return to login. When I looked back at my screen, all looked well, but for the red notification icon for a Plasma crash. The crash does not seem to be reproducible. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 [Current thread is 1 (Thread 0x7f015b6ee8c0 (LWP 2353))] Thread 13 (Thread 0x7f008f3fe700 (LWP 2578)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f015662b8eb in QWaitConditionPrivate::wait (time=18446744073709551615, this=0x4703220) at thread/qwaitcondition_unix.cpp:143 #2 QWaitCondition::wait (this=this@entry=0x4706a68, mutex=mutex@entry=0x4706a60, time=time@entry=18446744073709551615) at thread/qwaitcondition_unix.cpp:215 #3 0x7f015971710d in QSGRenderThreadEventQueue::takeEvent (wait=true, this=0x4706a58) at scenegraph/qsgthreadedrenderloop.cpp:245 #4 QSGRenderThread::processEventsAndWaitForMore (this=this@entry=0x47069e0) at scenegraph/qsgthreadedrenderloop.cpp:701 #5 0x7f0159717a05 in QSGRenderThread::run (this=0x47069e0) at scenegraph/qsgthreadedrenderloop.cpp:730 #6 0x7f015662a989 in QThreadPrivate::start (arg=0x47069e0) at thread/qthread_unix.cpp:368 #7 0x7f01554cf6ba in start_thread (arg=0x7f008f3fe700) at pthread_create.c:333 #8 0x7f0155f373dd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 12 (Thread 0x7f008fbff700 (LWP 2577)): #0 0x7f0155f2b70d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7f015a09dc62 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 #2 0x7f015a09e31d in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 #3 0x7f015a09e3a5 in xcb_writev () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 #4 0x7f015a2f34ae in _XSend () from /usr/lib/x86_64-linux-gnu/libX11.so.6 #5 0x7f015a2f37f5 in _XFlush () from /usr/lib/x86_64-linux-gnu/libX11.so.6 #6 0x7f015a2d4e4a in XFlush () from /usr/lib/x86_64-linux-gnu/libX11.so.6 #7 0x7f015b8c07a2 in QGLXContext::swapBuffers (this=0x42ec0f0, surface=0x2f6b5d0) at qglxintegration.cpp:545 #8 0x7f0156c29a3d in QOpenGLContext::swapBuffers (this=0x2c6cdd0, surface=) at kernel/qopenglcontext.cpp:1107 #9 0x7f01597131b1 in QSGRenderThread::syncAndRender (this=this@entry=0x4313b90) at scenegraph/qsgthreadedrenderloop.cpp:643 #10 0x7f01597178dc in QSGRenderThread::run (this=0x4313b90) at scenegraph/qsgthreadedrenderloop.cpp:721 #11 0x7f015662a989 in QThreadPrivate::start (arg=0x4313b90) at thread/qthread_unix.cpp:368 #12 0x7f01554cf6ba in start_thread (arg=0x7f008fbff700) at pthread_create.c:333 #13 0x7f0155f373dd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 11 (Thread 0x7f008ebfd700 (LWP 2570)): #0 0x7f0155f2724d in read () at ../sysdeps/unix/syscall-template.S:84 #1 0x7f01518d76f0 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f0151893e74 in g_main_context_check () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f0151894330 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f015189449c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f015685394b in QEventDispatcherGlib::processEvents (this=0x7f00800156b0, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #6 0x7f01567fc7ca in QEventLoop::exec (this=this@entry=0x7f008ebfccc0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:212 #7 0x7f0156625cd4 in QThread::exec (this=) at thread/qthread.cpp:515 #8 0x7f00717d9517 in KCupsConnection::run() () from /usr/lib/x86_64-linux-gnu/libkcupslib.so #9 0x7f015662a989 in QThreadPrivate::start (arg=0x4129fb0) at thread/qthread_unix.cpp:368 #10 0x7f01554cf6ba in start_thread (arg=0x7f008ebfd700) at pthread_create.c:333 #11 0x7f0155f373dd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 10 (Thread 0x7f00a6523700 (LWP 2538)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:18
[kdenlive] [Bug 371849] audio file sounds "clicky" when on project timeline; affects rendered file
https://bugs.kde.org/show_bug.cgi?id=371849 --- Comment #24 from S. Christian Collins --- I am using Kdenlive 17.08.0 now with custom-compiled MLT from git, which Kdenlive reports as version 6.5.0. However, new projects still are created using "combine" rather than "sum", and exhibit the clicky audio. After manually editing the .kdenlive file to replace "combine" with "sum", I can confirm that MLT's new "sum" feature no longer reduces the volume :) -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 379170] 2.6.0 - Regression: "Spacebar calculates disk space" feature is missing
https://bugs.kde.org/show_bug.cgi?id=379170 --- Comment #14 from torbj...@stabo.se --- Den 2017-09-06 kl. 23:29, skrev Christoph Feck: > https://bugs.kde.org/show_bug.cgi?id=379170 > > --- Comment #13 from Christoph Feck --- > torbjorn, what does "ls -l" show for the size of the folders? Empty > directories > indeed need disk space. > (The folders I used for testing before were empty, as in no files in them) Technically they do, no arguing there. But I'd expect next to everyone to expect the reported size to be for the folder *contents*, not the number of bytes/blocks used in total for the folder structures on disk. Like I said before, the way it is now the returned value/functionality is unusable when looking for empty - as in folders with no files, or at the most files with no contents - folders. /Regards, Torbjörn Stabo -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 383421] (Enhancement wish) Make Breeze Icons more distinctive
https://bugs.kde.org/show_bug.cgi?id=383421 --- Comment #25 from Paul --- (In reply to Jens Reuterberg from comment #24) > Paul: if you don't want people to take it to heart then why post that > clickbait article in a bug list? If you view that article as "clickbait" then so be it. The point made is nonetheless valid IMHO. (I've no intention of engaging in some sort of "flame war" either). -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 378953] Effect "Freeze" stops working after overlay
https://bugs.kde.org/show_bug.cgi?id=378953 S. Christian Collins changed: What|Removed |Added CC||s_chriscoll...@hotmail.com --- Comment #3 from S. Christian Collins --- Created attachment 107737 --> https://bugs.kde.org/attachment.cgi?id=107737&action=edit video showing the bug Here is a video I made showing this bug in action. Steps to reproduce: 1. Add a video clip to video track 2. 2. Add another clip to video track 3 above, starting a little bit before the end of the video clip on track 2 (tested with video, PNG, and color clip). 3. Click the bottom-left corner of the clip on video track 3 to add a dissolve transition. 4. Drag the "Motion" -> "Freeze" effect to the clip on video track 2. Result: When playing the project, the clip on video track 2 is frozen as it should be, but when it hits the dissolve transition, the video no longer remains frozen, and the dissolve transition does not occur. ** My System ** Kdenlive: 17.08.0 MLT: compiled from GIT (reported by Kdenlive as 6.5.0) OS: KDE Neon 5.10.5 64-bit (Plasma Desktop 5.10.5, KDE Frameworks 5.37.0, Qt 5.9.1) Linux Kernel: 4.10.0.33-generic Video: NVIDIA GeForce GTX 970 w/ 4GB RAM (PCI Express) NVIDIA video driver: 375.66 -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 384439] Kmail 'Print' (non-HTML email) uses WebEngine instead if direct print
https://bugs.kde.org/show_bug.cgi?id=384439 --- Comment #3 from Maurice Batey --- (In reply to Laurent Montel from comment #1) > Update your version. > it's fixed in 5.5.x + qt> 5.8 > so you need to increase version. Do you know if that version also addresses the "Retrieving Folder Contents" lockup? (E.g. As covered by: https://bugs.mageia.org/show_bug.cgi?id=21486 ) -- You are receiving this mail because: You are watching all bug changes.
[k3b] [Bug 384471] New: Media type selection for Image burning is partly wrong, comments are very wrong
https://bugs.kde.org/show_bug.cgi?id=384471
Bug ID: 384471
Summary: Media type selection for Image burning is partly
wrong, comments are very wrong
Product: k3b
Version: unspecified
Platform: Other
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: NOR
Component: general
Assignee: k...@kde.org
Reporter: scdbac...@gmx.net
CC: mich...@jabster.pl, tr...@kde.org
Target Milestone: ---
Hi,
K3b::Iso9660ImageWritingJob::startWriting() inapropriately accepts DVD+R for
m_writingMode == K3b::WritingModeRestrictedOverwrite :
https://cgit.kde.org/k3b.git/tree/libk3b/jobs/k3biso9660imagewritingjob.cpp#n261
else if( m_writingMode == K3b::WritingModeRestrictedOverwrite ) {
mt =
K3b::Device::MEDIA_DVD_PLUS_R|K3b::Device::MEDIA_DVD_PLUS_R_DL|K3b::Device::MEDIA_DVD_PLUS_RW|K3b::Device::MEDIA_DVD_RW_OVWR;
Restricted Overwrite a speciality of formatted DVD-RW.
"Overwrite" like with DVD-RAM, DVD+RW, BD-RE. "Resctricted" because only
full chunks of 32 KiB may be written.
The allowed gestures are also allowed with DVD+RW, DVD-RAM, BD-RE.
But it is not compatible with DVD+R or DVD+R DL.
So, after due checking whether WritingModeRestrictedOverwrite really
means what its name suggests, all types except formatted DVD-RW should be
removed from the "mt" list.
If one wants to allow DVD+RW, then also DVD-RAM and BD-RE should be allowed.
(In general i wonder why K3B already knows the future write type but not the
medium type yet. Must be a GUI precognition thing.)
--
The comment in line 236 ff. is obviously outdated. The choice of wanted DVD
(and now BD) does not depend on the use of growisofs. The comment lists 10
decisions or remarks:
1. Ok. (but obviously writing app is not auto)
2. Wrong. The code looks for cdrdao as writing app, not for "not growisofs".
3. Wrong. If not cdrdao and not d->isDvdImage, then all media (including BD)
4. Ok.
5. No such code is to see.
6. No such code is to see.
7. No such code is to see.
8. No such code is to see.
9. Wrong. DVD+R and DVD+R DL are accepted inappropiately.
DVD+RW is ok, but misplaced here, nevertheless.
10. obsolete, now that Bug 381074 is fixed.
In the code i see currently these five decisions:
1. If special CD features are requested: CD types only
Special are: K3b::WritingAppCdrdao , K3b::WritingModeTao , WritingModeRaw
2. If formatted DVD-RW is requested: formatted DVD-RW, DVD+R, DVD+R DL, DVD+RW
Request is: K3b::WritingModeRestrictedOverwrite
3. If image is larger than 900 MiB (d->isDvdImage == true): DVD or BD types
See K3b::Iso9660ImageWritingJob::start()
4. If image not larger than 900 MiB: All media types
5. If not decided yet: All media types
After fixing my objection above, number 2 should become
2. If formatted DVD-RW is requested: formatted DVD-RW only
Request is: K3b::WritingModeRestrictedOverwrite
Have a nice day :)
Thomas
--
You are receiving this mail because:
You are watching all bug changes.
[kwin] [Bug 384441] Freeze caused by Plasma DialogShadows
https://bugs.kde.org/show_bug.cgi?id=384441 Martin Flöser changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Latest Commit||https://commits.kde.org/kwi ||n/e0f95fd913b6e7c9106ca153c ||0dd1e3d46c9e297 Resolution|--- |FIXED --- Comment #2 from Martin Flöser --- Git commit e0f95fd913b6e7c9106ca153c0dd1e3d46c9e297 by Martin Flöser. Committed on 07/09/2017 at 17:06. Pushed by graesslin into branch 'master'. Delay syncing internal window geometry to end of cycle Summary: The syncing of the window geometry to the internal geometry can unfortunately cause a freeze in very special conditions: 1. create QML component 2. a Plasma::Dialog gets created 3. It creates the DialogShadows 4. This triggers QGlobalStatic creation which locks a non-recursive mutex 5. The creation of DialogShadows creates a Registry and triggers a roundtrip on the Wayland server 6. KWin processes all Wayland events 7. This triggers the creation of a ShellClient 8. The ShellClient has a PlasmaShellSurface which requested a position 9. The new geometry does not match the geometry of the Plasma::Dialog 10. ShellClient syncs the geometry to the Plasma::Dialog 11. Plasma::Dialog updates the theme because window geometry changed 12. This accesses the DialogShadows... which is still in the non recursive mutex and we have a freeze. By delaying the sync to the end of cycle we jump out of this deadly sequence. Test Plan: The freeze doesn't hit any more. It's possible that some test cases need adjustments. Reviewers: #kwin, #plasma Subscribers: plasma-devel, kwin Tags: #kwin Differential Revision: https://phabricator.kde.org/D7712 M +3-3autotests/integration/internal_window.cpp M +2-1shell_client.cpp https://commits.kde.org/kwin/e0f95fd913b6e7c9106ca153c0dd1e3d46c9e297 -- You are receiving this mail because: You are watching all bug changes.
[k3b] [Bug 384471] Media type selection for Image burning is partly wrong, comments are very wrong
https://bugs.kde.org/show_bug.cgi?id=384471 --- Comment #1 from Thomas Schmitt --- Hi, already the first bug in my bug report. Implemented decision 5 is indeed: 5. If not decided yet: DVD and BD media types. This seems to assume that all CD use cases are completely covered by the previous decisions. If i was in charge i would allow all media types and let the media waiter decide by the requested size and the size of the inserted media type. Have a nice day :) Thomas -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 384425] digikam-5.7.0/core/libs/rawengine/libraw/samples/dcraw_emu.cpp:468]: (style) Suspicious condition
https://bugs.kde.org/show_bug.cgi?id=384425 caulier.gil...@gmail.com changed: What|Removed |Added Resolution|--- |FIXED Latest Commit||https://commits.kde.org/dig ||ikam/3cba5a9b5be82c59688659 ||74686be8ffd350c460 Status|UNCONFIRMED |RESOLVED Version Fixed In||5.8.0 --- Comment #2 from caulier.gil...@gmail.com --- Git commit 3cba5a9b5be82c5968865974686be8ffd350c460 by Gilles Caulier. Committed on 07/09/2017 at 17:18. Pushed by cgilles into branch 'master'. apply patch to fix test in dcraw_emu CLI tool FIXED-IN: 5.8.0 M +2-1libs/rawengine/libraw/samples/dcraw_emu.cpp https://commits.kde.org/digikam/3cba5a9b5be82c5968865974686be8ffd350c460 -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 383421] (Enhancement wish) Make Breeze Icons more distinctive
https://bugs.kde.org/show_bug.cgi?id=383421 --- Comment #26 from Paul --- (In reply to andreas from comment #23) > ... make oxygen fit plasma 5. ... Now, I'm not a Graphic Designer / Artist. Just a user who needs to get work done in a productive manner. The change from KDE4/Oxygen to Plasma5/Breeze was a seismic shift. For some it was a shift too far. Yes, oxygen icons are still available, and indeed I believe you yourself are maintaining them. For that I, and I'm sure others, are thankful. One of the problems with oxygen though, is it's lack of full integration with plasma 5. Plasmoids for example still look "wrong" when using the Oxygen Look & Feel; that I suspect is something unlikely to change. Limited resources in terms of manpower (should that be people power?), coupled with the (it seems) probable believe there is no real demand for oxygen any longer, it's not "modern", it's not "arty". Ultimately though, the choice is with the user, if one has the ability, open source allows you to make your own contributions. Most users are not in that fortunate position, myself included. We use what we are given, if we don't like it nothing forces us to use it. Users do however get frustrated, sometimes that frustration is vented on developers. But, if you create anything, no matter what, and put it into the public domain, then one must take the brickbats as well as the bouquets. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 384425] Suspicious condition in dcraw_emu CLI tool source code.
https://bugs.kde.org/show_bug.cgi?id=384425 caulier.gil...@gmail.com changed: What|Removed |Added Summary|digikam-5.7.0/core/libs/raw |Suspicious condition in |engine/libraw/samples/dcraw |dcraw_emu CLI tool source |_emu.cpp:468]: (style) |code. |Suspicious condition| -- You are receiving this mail because: You are watching all bug changes.
