[digikam] [Bug 405378] Missing libz.dll on launch
https://bugs.kde.org/show_bug.cgi?id=405378 --- Comment #4 from caulier.gil...@gmail.com --- Bill, The problem must be fixed in next Windows installers for pre-release 6.1.0. Files will be uploaded this morning (compilation just started - this take 2 hours). Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[umbrello] [Bug 405408] Line type preset
https://bugs.kde.org/show_bug.cgi?id=405408 Ralf Habacker changed: What|Removed |Added Severity|normal |wishlist CC||ralf.habac...@freenet.de -- You are receiving this mail because: You are watching all bug changes.
[rkward] [Bug 405386] RKWard Version 0.7.0z+0.7.1+devel1 can't preview Markdown
https://bugs.kde.org/show_bug.cgi?id=405386 --- Comment #6 from Thomas Friedrichsmeier --- Interesting observation. But for me, the xmlns-line does not cause any trouble, and I'm not sure, why it should. Sorry, if I need to insist: How *exactly* did you install RKWard. Is it directly from git? Or did you download a package? If so, where from, exactly? Also, the output of rk.sessionInfo() may be useful, as this could be a bug in Qt/KDE libraries, and so I'd like to know the version numbers of those. Finally, I was not asking specific enough with question number 2: Does rk.show.html() work, correctly, when pointed to the preview file (without removing the xmlns)? -- You are receiving this mail because: You are watching all bug changes.
[libkgapi] [Bug 404691] choosing reverse name => "France" become "FR"
https://bugs.kde.org/show_bug.cgi?id=404691
--- Comment #4 from Philippe ROUBACH ---
there is an update about 18.12.3 and 5.55.0
it seems the patch
sam. 09 mars 2019 13:00:00 CET
lbeltr...@kde.org
- Update to 18.12.3
* New bugfix release
* For more details please see:
* https://www.kde.org/announcements/announce-applications-18.12.3.php
- Changes since 18.12.2:
* Fix googletalk protocol.
* Contacts: fix email type deserialization (kde#398847)
- Dropped patches, now upstream:
* Contacts-fix-email-type-deserialization.patch
has fixed the problem ("FR" became "France") but not completely. A few
addresses "FR" stays "FR".
--
You are receiving this mail because:
You are watching all bug changes.
[kwin] [Bug 390021] Add day option to Night Color
https://bugs.kde.org/show_bug.cgi?id=390021 Anthony Fieroni changed: What|Removed |Added CC||bvb...@abv.bg --- Comment #3 from Anthony Fieroni --- (In reply to Roman Gilg from comment #1) > The idea was to put the daytime/overall color temperature value in the end > in a separate KCM, that replaces KGamma on Wayland and handles all color > correction. This should then also do this per screen. > > The nighttime color temperature value would then be a relative delta to the > daytime/overall color temperature value on each screen. > > Fine with that? I look at the code of night color so it will be better to be distinct kcm, also note that's good feature, by myself i'm using it for years (at days as well) so that's missing in Wayland. -- You are receiving this mail because: You are watching all bug changes.
[libkgapi] [Bug 405167] all contacts, no more address
https://bugs.kde.org/show_bug.cgi?id=405167 --- Comment #5 from Philippe ROUBACH --- there was an update about 18.12.3 and 5.55.0 it seems the patch sam. 09 mars 2019 13:00:00 CET lbeltr...@kde.org - Update to 18.12.3 * New bugfix release * For more details please see: * https://www.kde.org/announcements/announce-applications-18.12.3.php - Changes since 18.12.2: * Fix googletalk protocol. * Contacts: fix email type deserialization (kde#398847) - Dropped patches, now upstream: * Contacts-fix-email-type-deserialization.patch fixed the problem but not for all addresses. a few addresses stays "not displayed" and we get a bonus: for a few addresses "Pari, 75002" is displayed instead of "75002 PARIS" for all addresses "PARI" is displayed instead of "PARIS" -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 404272] vex amd64->IR: unhandled instruction bytes: 0x66 0xF 0x38 0x23 0xC0 0xF3 (PMOVSXWD)
https://bugs.kde.org/show_bug.cgi?id=404272
--- Comment #5 from Julian Seward ---
I made a test case using the failing bytes you sent, as below, and
it runs ok with the trunk.
int main ( void )
{
// 66 0f 38 23 c0 pmovsxwd %xmm0,%xmm0
__asm__ __volatile__(".byte 0x66, 0xF, 0x38, 0x23, 0xC0"
:::"cc","memory");
return 0;
}
--
You are receiving this mail because:
You are watching all bug changes.
[krita] [Bug 405416] Clear Undo Stack for Krita
https://bugs.kde.org/show_bug.cgi?id=405416 Boudewijn Rempt changed: What|Removed |Added CC||b...@valdyas.org --- Comment #1 from Boudewijn Rempt --- What's your setting for the undo stack? The default limit is 30 undo steps, and you can change that yourself. -- You are receiving this mail because: You are watching all bug changes.
[libkgapi] [Bug 405167] all contacts, no more address
https://bugs.kde.org/show_bug.cgi?id=405167 --- Comment #6 from Philippe ROUBACH --- we get another bonus: in the address english "PO BOX 33" instead of french "BP 33" -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 366632] Windows not resized to maximize area if initially too large
https://bugs.kde.org/show_bug.cgi?id=366632 seqular...@tutanota.com changed: What|Removed |Added CC||seqular...@tutanota.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 405421] New: FEATURE REQUEST: Quick Tiling as a window rule
https://bugs.kde.org/show_bug.cgi?id=405421 Bug ID: 405421 Summary: FEATURE REQUEST: Quick Tiling as a window rule Product: kwin Version: unspecified Platform: unspecified OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: rules Assignee: kwin-bugs-n...@kde.org Reporter: e...@ecocode.net Target Milestone: --- Please add a window rule to quick tile to left/right/top/bottom new windows. see https://www.reddit.com/r/kde/comments/b0dhk6/force_quick_tile_to_right_as_a_window_rule/ -- You are receiving this mail because: You are watching all bug changes.
[kaddressbook] [Bug 398847] Kaddressbook not parsing gmail contacts
https://bugs.kde.org/show_bug.cgi?id=398847
--- Comment #29 from Philippe ROUBACH ---
many problems were fixed with recent patches about gapi core and gapi contacts
by just updating and restarting PC.
the 2 recents patches fixed many problems but not all see
https://bugs.kde.org/show_bug.cgi?id=405167
https://bugs.kde.org/show_bug.cgi?id=404691
these 2 recents patches (you can see them if your software management tool list
them) :
sam. 09 mars 2019 13:00:00 CET
lbeltr...@kde.org
- Update to 18.12.3
* New bugfix release
* For more details please see:
* https://www.kde.org/announcements/announce-applications-18.12.3.php
- Changes since 18.12.2:
* Fix googletalk protocol.
* Contacts: fix email type deserialization (kde#398847)
- Dropped patches, now upstream:
* Contacts-fix-email-type-deserialization.patch
lun. 25 févr. 2019 13:00:00 CET
wba...@tmo.at
- Add Contacts-fix-email-type-deserialization.patch to fix broken
email fields in google contacts (boo#1126614, kde#398847)
- Use < %{version} again for obsoleting sasl2-kdexoauth2-3
--
You are receiving this mail because:
You are watching all bug changes.
[kwin] [Bug 405421] FEATURE REQUEST: Quick Tiling as a window rule
https://bugs.kde.org/show_bug.cgi?id=405421 Vlad Zagorodniy changed: What|Removed |Added Severity|normal |wishlist -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 404572] Sorting by desktop not working
https://bugs.kde.org/show_bug.cgi?id=404572 --- Comment #15 from Eike Hein --- My pleasure! Thanks for the report/info, and especially for testing the patches. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 404572] Sorting by desktop not working
https://bugs.kde.org/show_bug.cgi?id=404572 --- Comment #16 from Eike Hein --- (Whoops! Accidental Bugzilla reply.) -- You are receiving this mail because: You are watching all bug changes.
[frameworks-ktexteditor] [Bug 403295] Bookmark icon over dark background almost invisible
https://bugs.kde.org/show_bug.cgi?id=403295 --- Comment #5 from Gabriele Menna --- I suppose I got where the problem is. I'm using a ligth color schema for application and icons (Breeze), but a dark dark one for text editor (Breeze Dark). And breeze bookmark icon becomes pretty invisible over a dark background... -- You are receiving this mail because: You are watching all bug changes.
[ksudoku] [Bug 405422] New: ksudoku live-git (commit 09814312d) small-game generation fails with "Unable to generate a puzzle of the chosen variant"
https://bugs.kde.org/show_bug.cgi?id=405422 Bug ID: 405422 Summary: ksudoku live-git (commit 09814312d) small-game generation fails with "Unable to generate a puzzle of the chosen variant" Product: ksudoku Version: unspecified Platform: Gentoo Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: iandw...@gmail.com Reporter: 1i5t5.dun...@cox.net CC: kde-games-b...@kde.org Target Milestone: --- This just started happening a few days ago. I like a quick 6x6 game so that's my normal default, but games smaller than standard 9x9 seem to fail with "Unable to generate a puzzle of the chosen variant", now. However, given that ksudoku has had only a single GIT_SILENT commit since Jan 11, and it worked well after Jan 11, I suspect the trigger to be an update of some dependency. So what might trigger the above error on particularly smaller games? (Note that I'm running live-git of nearly everything kde related, including all frameworks and plasma packages, so if it's a kde-related dep it's likely live-git, while other deps are reasonably recent, being gentoo/~amd64, aka testing. For toolchain, glibc-2.28-r5 updated on Mar 10, I /think/ after the problem already appeared, and gcc-3.3.0 updated on Feb 24, I believe before the problem altho I wouldn't have rebuilt kde packages until they had a commit, and qt-5.12.1 on Feb 14 as parts of live-git plasma require qt-5.12 now...) Also, out-of-routine I recently tried a big 25x25 which took me a couple of days to solve (BTW, the timer apparently wrapped at some point as it said only a few hours, but that'd be a different bug I've not actually filed yet, is it known or should I file a bug on it). AFAIK the 6x6 games were working before that, and broken very soon after, but I tried deleting (well, renaming) the ksudokurc file and it didn't solve the problem, so if it's corrupted state it must be elsewhere. -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 405423] New: Can't change default search engine
https://bugs.kde.org/show_bug.cgi?id=405423 Bug ID: 405423 Summary: Can't change default search engine Product: Falkon Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: now...@gmail.com Reporter: and...@alweb.dk Target Milestone: --- SUMMARY I tried to change the default search engine, but it did not take effect until I removed the former default search engine. 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.
[Falkon] [Bug 405424] New: Add ability to allow ads in certain sites, in adblocker addon
https://bugs.kde.org/show_bug.cgi?id=405424 Bug ID: 405424 Summary: Add ability to allow ads in certain sites, in adblocker addon Product: Falkon Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: extensions Assignee: now...@gmail.com Reporter: and...@alweb.dk Target Milestone: --- It would be nice to be able to make exceptions for specifik urls in adblocker, like in other browsers. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 405256] kdeconnect does not stay connected
https://bugs.kde.org/show_bug.cgi?id=405256 --- Comment #1 from Philippe ROUBACH --- android kdeconnect 1.11 kde kdeconnect 1.3.3 it seems that problem is fixed but i wait for a week to be sure. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 405394] Add support for sched_setattr and sched_getattr system call.
https://bugs.kde.org/show_bug.cgi?id=405394
--- Comment #3 from Daniel Wagner ---
With PRE_MEM_READ valgrind will complain for code like this (which should be
fine, right?):
void run_deadline() {
struct sched_attr attr;
ret = sched_getattr(0, &attr, sizeof(attr), 0);
}
==11537== Thread 2:
==11537== Syscall param sched_getattr(p) points to uninitialised byte(s)
==11537==at 0x49A1EFD: syscall (in /usr/lib64/libc-2.28.so)
==11537==by 0x403E68: run_deadline (cyclicdeadline.c:784)
==11537==by 0x489058D: start_thread (in /usr/lib64/libpthread-2.28.so)
==11537==by 0x49A76A2: clone (in /usr/lib64/libc-2.28.so)
==11537== Address 0x5671ea0 is on thread 2's stack
==11537== in frame #1, created by run_deadline (cyclicdeadline.c:772)
==11537==
No complains with PRE_MEM_WRITE.
--
You are receiving this mail because:
You are watching all bug changes.
[kdeconnect] [Bug 382365] kdeconnect does not connect automatically
https://bugs.kde.org/show_bug.cgi?id=382365 --- Comment #4 from Philippe ROUBACH --- android kdeconnect 1.11 problem still there. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 405394] Add support for sched_setattr and sched_getattr system call.
https://bugs.kde.org/show_bug.cgi?id=405394 --- Comment #4 from Tom Hughes --- Well that one doesn't need a PRE_MEM_READ so the fact that it would complain isn't really relevant. You should use PRE_MEM_READ before the system call for any memory which will be read by the system call and PRE_MEM_WRITE for any memory which will be written by the system call (unless it is also read - you don't need to do both). After the system call completes you should use POST_MEM_WRITE on any memory that the system call has written. Basically PRE_MEM_READ checks that the memory is both addressable (that there is actual accessible memory at that address) and defined (that it has been initialised with known contents) while PRE_MEM_WRITE just does the first check. Then POST_MEM_WRITE marks the memory as defined if it has been filled in by the system call. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 405366] Flatten image with alpha inheritance in python results in a blank image.
https://bugs.kde.org/show_bug.cgi?id=405366 Tymond changed: What|Removed |Added CC||tamtamy.tym...@gmail.com --- Comment #1 from Tymond --- Works for me... could you please include a file that gives you that behaviour? I'll checked with my test files for similar problems and they all worked. (In the previous issue like that: BUG 405119 the problem was when the layer inside of the group was selected, nothing special about alpha inheritance; so in this case, I checked saving my test files with different layers selected and none gave me the issue, that's why I need exactly the same file that gives you issues to make sure the same layer is selected and located in the same combination of layers and groups). -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 405119] Flatten image with from a layers inside of a group results in all layers dissapearing.
https://bugs.kde.org/show_bug.cgi?id=405119 Tymond changed: What|Removed |Added Summary|Flatten image with a layer |Flatten image with from a |stack containing apha |layers inside of a group |inheritance results in all |results in all layers |layers dissapearing.|dissapearing. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 405247] baloo (baloo_file_extractor) should report what file is causing it problems
https://bugs.kde.org/show_bug.cgi?id=405247 Méven Car changed: What|Removed |Added CC||meve...@gmail.com --- Comment #1 from Méven Car --- Related to https://bugs.kde.org/show_bug.cgi?id=405294 and https://bugs.kde.org/show_bug.cgi?id=405210 -- You are receiving this mail because: You are watching all bug changes.
[ksysguard] [Bug 346124] CPU and network usage is not available !!!
https://bugs.kde.org/show_bug.cgi?id=346124 --- Comment #5 from kukulski.przemys...@gmail.com --- Deleting ~/.local/share/ksysguard fixed the problem for me. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 405119] Flatten image with from a layers inside of a group results in all layers dissapearing.
https://bugs.kde.org/show_bug.cgi?id=405119 --- Comment #5 from Tymond --- Since the problem was caused by a slightly different thing that the previous title suggested, I changed the title so future readers don't get confused. Problem happened iff the selected layer while flattening was taking place was inside of a group. As far as I know, nothing was caused specifically by alpha inheritance. If the issue persists in some cases regarding the alpha inheritance, please reopen this bug and provide more information. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 390295] The active virtual desktop is no longer remembered between sessions
https://bugs.kde.org/show_bug.cgi?id=390295 Vlad Zagorodniy changed: What|Removed |Added Latest Commit|https://commits.kde.org/kwi |https://commits.kde.org/kwi |n/a9e469bf13f6d99c24eb2ae24 |n/f7af113261f7e899e1d954b05 |c3a0f4ec0a79d61 |58b2c637a9cced1 --- Comment #5 from Vlad Zagorodniy --- Git commit f7af113261f7e899e1d954b0558b2c637a9cced1 by Vlad Zagorodniy. Committed on 13/03/2019 at 09:45. Pushed by vladz into branch 'Plasma/5.12'. Properly restore current desktop from session Summary: VirtualDesktopManager is initialized in two places: Workspace::init and Workspace::initWithX11. The former method loads virtual desktops from the config file and the latter method synchronizes VirtualDesktopManager with RootInfo. Both methods do if (!VirtualDesktopManager::self()->setCurrent(m_initialDesktop)) VirtualDesktopManager::self()->setCurrent(1); which makes sense in Workspace::init, but not in Workspace::initWithX11. When Workspace::initWithX11 is called, the current virtual desktop is the same as m_initialDesktop. So that piece of code basically makes the first virtual desktop current no matter what. FIXED-IN: 5.15.3 Reviewers: #kwin, davidedmundson Reviewed By: #kwin, davidedmundson Subscribers: kwin Tags: #kwin Differential Revision: https://phabricator.kde.org/D19520 M +3-3workspace.cpp https://commits.kde.org/kwin/f7af113261f7e899e1d954b0558b2c637a9cced1 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 405247] baloo (baloo_file_extractor) should report what file is causing it problems
https://bugs.kde.org/show_bug.cgi?id=405247 --- Comment #2 from Méven Car --- Have you tried "balooshow file.jpg", it could be of help. Seen from https://community.kde.org/Baloo/Debugging You issue seams triggered by a photo created on 14th of January 2017 probably at 1am, it could help you find it. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 405210] baloofile_extractor crash
https://bugs.kde.org/show_bug.cgi?id=405210 Méven Car changed: What|Removed |Added CC||craig.a.den...@gmail.com --- Comment #1 from Méven Car --- *** Bug 405294 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 405294] Baloo File Extractor continuously crashes starting at first boot-up
https://bugs.kde.org/show_bug.cgi?id=405294 Méven Car changed: What|Removed |Added Resolution|--- |DUPLICATE CC||meve...@gmail.com Status|REPORTED|RESOLVED --- Comment #1 from Méven Car --- *** This bug has been marked as a duplicate of bug 405210 *** -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 405424] Add ability to allow ads in certain sites, in adblocker addon
https://bugs.kde.org/show_bug.cgi?id=405424 Anders Lund changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |WORKSFORME -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 405412] Discover suddenly started crashing on launch
https://bugs.kde.org/show_bug.cgi?id=405412 --- Comment #2 from Dan Jensen --- *** Bug 405413 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 405413] Discover crashes on start
https://bugs.kde.org/show_bug.cgi?id=405413 Dan Jensen changed: What|Removed |Added Resolution|--- |DUPLICATE CC||ad...@leinir.dk Status|REPORTED|RESOLVED --- Comment #1 from Dan Jensen --- *** This bug has been marked as a duplicate of bug 405412 *** -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 405412] Discover suddenly started crashing on launch
https://bugs.kde.org/show_bug.cgi?id=405412 Dan Jensen changed: What|Removed |Added Resolution|--- |DUPLICATE CC||ad...@leinir.dk Status|REPORTED|RESOLVED --- Comment #3 from Dan Jensen --- Thank you for the report, it is good to get more information - i realise it's sometimes difficult to find other bugs with the same cause if the automatic search doesn't find them for you :) *** This bug has been marked as a duplicate of bug 405290 *** -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 405290] discover closes when trying to general update
https://bugs.kde.org/show_bug.cgi?id=405290 Dan Jensen changed: What|Removed |Added CC||j...@helfert.us --- Comment #2 from Dan Jensen --- *** Bug 405412 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 405425] New: error en dependencias, no se puede instalar, eliminado despues ultima actualización
https://bugs.kde.org/show_bug.cgi?id=405425 Bug ID: 405425 Summary: error en dependencias, no se puede instalar, eliminado despues ultima actualización Product: dolphin Version: unspecified Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: mateo...@gmail.com CC: elvis.angelac...@kde.org Target Milestone: --- SUMMARY 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.
[buildsystem] [Bug 369554] sleeper design bug in the installation layout due to assumptions about filesystem case sensitivity
https://bugs.kde.org/show_bug.cgi?id=369554 --- Comment #7 from David Faure --- This is definitely not just about two frameworks, it's about ALL of them. Look at it, they all install forwarding headers. Reducing the number of -I arguments is not a goal, it's in fact counter-productive. We want to make sure each framework is explicitly used, not just by chance. Users of Attica forwarding headers: indeed I didn't see any either. Fixed. https://commits.kde.org/discover/712a7dfcab388b93dba7477eb55dc95d48bcafca -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 405394] Add support for sched_setattr and sched_getattr system call.
https://bugs.kde.org/show_bug.cgi?id=405394 Daniel Wagner changed: What|Removed |Added Attachment #118743|0 |1 is obsolete|| --- Comment #5 from Daniel Wagner --- Created attachment 118767 --> https://bugs.kde.org/attachment.cgi?id=118767&action=edit Add support for sched_setattr and sched_getattr v2 -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 405394] Add support for sched_setattr and sched_getattr system call.
https://bugs.kde.org/show_bug.cgi?id=405394 --- Comment #6 from Daniel Wagner --- I am not sure if I handle the size argument correctly. Here the snipped from the man pages: size This field should be set to the size of the structure in bytes, as in sizeof(struct sched_attr). If the provided structure is smaller than the ker‐ nel structure, any additional fields are assumed to be '0'. If the provided structure is larger than the kernel structure, the kernel verifies that all additional fields are 0; if they are not, sched_setattr() fails with the error E2BIG and updates size to contain the size of the kernel structure. The above behavior when the size of the user-space sched_attr structure does not match the size of the kernel structure allows for future extensibility of the interface. Malformed applications that pass oversize structures won't break in the future if the size of the kernel sched_attr structure is increased. In the future, it could also allow applications that know about a larger user-space sched_attr structure to determine whether they are running on an older kernel that does not support the larger structure. -- You are receiving this mail because: You are watching all bug changes.
[latte-dock] [Bug 405311] latte-dock icons not showing up
https://bugs.kde.org/show_bug.cgi?id=405311 --- Comment #16 from Tycho Grouwstra --- Created attachment 118768 --> https://bugs.kde.org/attachment.cgi?id=118768&action=edit no icons also in the Add Widget panel (not pictured, closed when trying to take screenshot) Thank you for the idea, I think you were on to something there. Though showing green outlines and diagnostic variables, no icons would show yet. Notably though, in the Add Widget panel (not pictured, closed when trying to take screenshot) I could not see icons either (at all, so including for this analog clock). I suppose this is indicating the issue is not actually specific to latte-dock, and perhaps this ticket should be closed accordingly. P.S.: my distro is NixOS rather than Nitrux. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 405351] Plasma crashes with frameworks-plasma 5.56.0
https://bugs.kde.org/show_bug.cgi?id=405351 Rik Mills changed: What|Removed |Added CC||rikmi...@kubuntu.org --- Comment #10 from Rik Mills --- Fixing commit I think: https://cgit.kde.org/plasma-framework.git/commit/?id=ebae2d63033647950cf0f9d97410723a8c7db1f3 -- You are receiving this mail because: You are watching all bug changes.
[kinfocenter] [Bug 405128] Icon of "IO-Ports" section is missing in tooltips
https://bugs.kde.org/show_bug.cgi?id=405128 Marco Martin changed: What|Removed |Added Status|CONFIRMED |RESOLVED CC||notm...@gmail.com Resolution|--- |FIXED -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 405426] New: kontact crash
https://bugs.kde.org/show_bug.cgi?id=405426 Bug ID: 405426 Summary: kontact crash Product: kontact Version: unspecified Platform: Neon Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: gzmor...@gmail.com Target Milestone: --- Application: kontact (5.10.1) Qt Version: 5.12.0 Frameworks Version: 5.56.0 Operating System: Linux 4.15.0-46-generic x86_64 Distribution: KDE neon User Edition 5.15 -- Information about the crash: - What I was doing when the application crashed: Try to open kontact configuration - What I was expectiing To be able to change kontact configuration - What I get: kontact crash The crash can be reproduced every time. -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7fc4b0695bc0 (LWP 6103))] Thread 29 (Thread 0x7fc35d5bc700 (LWP 6175)): #0 0x7fc4a88c2ed9 in futex_reltimed_wait_cancelable (private=, reltime=0x7fc35d5bb710, expected=0, futex_word=0x7fc35d5bb8f8) at ../sysdeps/unix/sysv/linux/futex-internal.h:142 #1 0x7fc4a88c2ed9 in __pthread_cond_wait_common (abstime=0x7fc35d5bb7b0, mutex=0x7fc35d5bb8a8, cond=0x7fc35d5bb8d0) at pthread_cond_wait.c:533 #2 0x7fc4a88c2ed9 in __pthread_cond_timedwait (cond=0x7fc35d5bb8d0, mutex=0x7fc35d5bb8a8, abstime=0x7fc35d5bb7b0) at pthread_cond_wait.c:667 #3 0x7fc49df22177 in base::ConditionVariable::TimedWait(base::TimeDelta const&) () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #4 0x7fc49df22ada in base::WaitableEvent::TimedWaitUntil(base::TimeTicks const&) () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #5 0x7fc49df22bc2 in base::WaitableEvent::TimedWait(base::TimeDelta const&) () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #6 0x7fc49dee0851 in base::internal::SchedulerWorker::Delegate::WaitForWork(base::WaitableEvent*) () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #7 0x7fc49dee3387 in base::internal::SchedulerWorker::RunWorker() () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #8 0x7fc49dee3974 in base::internal::SchedulerWorker::RunPooledWorker() () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #9 0x7fc49df24cd1 in base::(anonymous namespace)::ThreadFunc(void*) () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #10 0x7fc4a88bc6db in start_thread (arg=0x7fc35d5bc700) at pthread_create.c:463 #11 0x7fc4acfc788f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 28 (Thread 0x7fc35e1dd700 (LWP 6171)): #0 0x7fc4acfb60b4 in __GI___libc_read (fd=106, buf=0x7fc35e1dc7d0, nbytes=16) at ../sysdeps/unix/sysv/linux/read.c:27 #1 0x7fc4a6a34cd0 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fc4a69f0027 in g_main_context_check () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fc4a69f04e0 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7fc4a69f064c in g_main_context_iteration () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7fc4adb1515b in QEventDispatcherGlib::processEvents(QFlags) (this=0x7fc354000b20, flags=...) at kernel/qeventdispatcher_glib.cpp:424 #6 0x7fc4adab664a in QEventLoop::exec(QFlags) (this=this@entry=0x7fc35e1dc9e0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:225 #7 0x7fc4ad8de41a in QThread::exec() (this=) at thread/qthread.cpp:531 #8 0x7fc4ad8dfbc2 in QThreadPrivate::start(void*) (arg=0x55f5b4425ff0) at thread/qthread_unix.cpp:361 #9 0x7fc4a88bc6db in start_thread (arg=0x7fc35e1dd700) at pthread_create.c:463 #10 0x7fc4acfc788f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 27 (Thread 0x7fc35f3ee700 (LWP 6168)): #0 0x7fc4acfbabb9 in __GI___poll (fds=0x7fc350004a10, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7fc4a69f0539 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fc4a69f064c in g_main_context_iteration () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fc4adb1515b in QEventDispatcherGlib::processEvents(QFlags) (this=0x7fc35b20, flags=...) at kernel/qeventdispatcher_glib.cpp:424 #4 0x7fc4adab664a in QEventLoop::exec(QFlags) (this=this@entry=0x7fc35f3ed9e0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:225 #5 0x7fc4ad8de41a in QThread::exec() (this=) at thread/qthread.cpp:531 #6 0x7fc4ad8dfbc2 in QThreadPrivate::start(void*) (arg=0x55f5b43eb4f0) at thread/qthread_unix.cpp:361 #7 0x7fc4a88bc6db in start_thread (arg=0x7fc35f3ee700) at pthread_create.c:463 #8 0x7fc4acfc788f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 26 (Thread 0x7fc35fbef700 (LWP 6165)): #0 0x7fc4acfbabf9 in __GI___poll (fds=0x7fc358003ce0, nfds=1, ti
[frameworks-kiconthemes] [Bug 396990] [Regression from Frameworks 5.47 -> 5.48] Dolphin icons are incorrectly aligned if display scaling is used
https://bugs.kde.org/show_bug.cgi?id=396990 --- Comment #17 from Kai Uwe Broulik --- Git commit 89344923c00b7bc502f5c24be50027b457d82177 by Kai Uwe Broulik. Committed on 13/03/2019 at 11:20. Pushed by broulik into branch 'master'. Fix padding icon that doesn't exactly match the requested size The size we get already takes into account scaling, so we end up creating a pixmap whose size was scaled twice and then had the view scale it down again. Reviewed-By: Marco Martin Related: bug 397106 M +1-1src/kiconengine.cpp https://commits.kde.org/kiconthemes/89344923c00b7bc502f5c24be50027b457d82177 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kirigami] [Bug 397106] Some icons look fuzzy when I set 1.2 as display scaling factor
https://bugs.kde.org/show_bug.cgi?id=397106 Kai Uwe Broulik changed: What|Removed |Added Latest Commit||https://commits.kde.org/kic ||onthemes/89344923c00b7bc502 ||f5c24be50027b457d82177 Status|CONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #6 from Kai Uwe Broulik --- Git commit 89344923c00b7bc502f5c24be50027b457d82177 by Kai Uwe Broulik. Committed on 13/03/2019 at 11:20. Pushed by broulik into branch 'master'. Fix padding icon that doesn't exactly match the requested size The size we get already takes into account scaling, so we end up creating a pixmap whose size was scaled twice and then had the view scale it down again. Reviewed-By: Marco Martin Related: bug 396990 M +1-1src/kiconengine.cpp https://commits.kde.org/kiconthemes/89344923c00b7bc502f5c24be50027b457d82177 -- You are receiving this mail because: You are watching all bug changes.
[LabPlot2] [Bug 405387] Feature request: python scripting
https://bugs.kde.org/show_bug.cgi?id=405387 Alexander Semke changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 -- You are receiving this mail because: You are watching all bug changes.
[latte-dock] [Bug 405311] latte-dock icons not showing up
https://bugs.kde.org/show_bug.cgi?id=405311 --- Comment #17 from Michail Vourlakos --- Yep, if you don't see images in the plasma Add Widgets window then something is broken in your system or distro. Please contact your distro in order to give you some hints for next steps -- You are receiving this mail because: You are watching all bug changes.
[latte-dock] [Bug 405311] latte-dock icons not showing up
https://bugs.kde.org/show_bug.cgi?id=405311 Michail Vourlakos changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |DOWNSTREAM -- You are receiving this mail because: You are watching all bug changes.
[plasma-browser-integration] [Bug 402144] Add "Show in Folder" button to file download notifications
https://bugs.kde.org/show_bug.cgi?id=402144 --- Comment #1 from Kai Uwe Broulik --- Git commit b09312ad384b41c3eaaca0d11a75c8b07cd4fc2e by Kai Uwe Broulik. Committed on 13/03/2019 at 11:30. Pushed by broulik into branch 'master'. [DownloadJob] Set destUrl and total amount Will eventually allow us to show a nice finished notification. Related: bug 404182 Differential Revision: https://phabricator.kde.org/D19589 M +7-1host/downloadjob.cpp https://commits.kde.org/plasma-browser-integration/b09312ad384b41c3eaaca0d11a75c8b07cd4fc2e -- You are receiving this mail because: You are watching all bug changes.
[plasma-browser-integration] [Bug 404182] Allow download notification to be drag and dropped
https://bugs.kde.org/show_bug.cgi?id=404182 --- Comment #4 from Kai Uwe Broulik --- Git commit b09312ad384b41c3eaaca0d11a75c8b07cd4fc2e by Kai Uwe Broulik. Committed on 13/03/2019 at 11:30. Pushed by broulik into branch 'master'. [DownloadJob] Set destUrl and total amount Will eventually allow us to show a nice finished notification. Related: bug 402144 Differential Revision: https://phabricator.kde.org/D19589 M +7-1host/downloadjob.cpp https://commits.kde.org/plasma-browser-integration/b09312ad384b41c3eaaca0d11a75c8b07cd4fc2e -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 405427] New: KWin crashes after waking from suspension
https://bugs.kde.org/show_bug.cgi?id=405427 Bug ID: 405427 Summary: KWin crashes after waking from suspension Product: kwin Version: 5.13.5 Platform: Ubuntu Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: emanuel.ang...@gmail.com Target Milestone: --- Application: kwin_x11 (5.13.5) Qt Version: 5.11.1 Frameworks Version: 5.50.0 Operating System: Linux 4.18.0-16-generic x86_64 Distribution: Ubuntu 18.10 -- Information about the crash: - What I was doing when the application crashed: I woke up my laptop from suspension by opening the lid. - Unusual behavior I noticed: After having the laptop suspended for several hours, when I wake it up it usually presents an error message. Sometimes it messes up the desktop's icons' titles and/or the windows' titlebar. The crash can be reproduced sometimes. -- Backtrace: Application: KWin (kwin_x11), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f332a081840 (LWP 10383))] Thread 5 (Thread 0x7f3307fff700 (LWP 10574)): #0 0x7f3331e4d2eb in futex_wait_cancelable (private=, expected=0, futex_word=0x7f3332c2afb8) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 0x7f3331e4d2eb in __pthread_cond_wait_common (abstime=0x0, mutex=0x7f3332c2af68, cond=0x7f3332c2af90) at pthread_cond_wait.c:502 #2 0x7f3331e4d2eb in __pthread_cond_wait (cond=0x7f3332c2af90, mutex=0x7f3332c2af68) at pthread_cond_wait.c:655 #3 0x7f3332b33e2a in () at /usr/lib/x86_64-linux-gnu/libQt5Script.so.5 #4 0x7f3332b33e49 in () at /usr/lib/x86_64-linux-gnu/libQt5Script.so.5 #5 0x7f3331e47164 in start_thread (arg=) at pthread_create.c:486 #6 0x7f3334678def in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 4 (Thread 0x7f3322c42700 (LWP 10485)): #0 0x7f333466c7d6 in __GI_ppoll (fds=0x7f3318000d28, nfds=1, timeout=, sigmask=0x0) at ../sysdeps/unix/sysv/linux/ppoll.c:39 #1 0x7f20d141 in qt_safe_poll(pollfd*, unsigned long, timespec const*) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #2 0x7f20e5b9 in QEventDispatcherUNIX::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #3 0x7f1be16b in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f00d0b6 in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f33316781f5 in () at /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #6 0x7f016c87 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f3331e47164 in start_thread (arg=) at pthread_create.c:486 #8 0x7f3334678def in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 3 (Thread 0x7f3323fff700 (LWP 10408)): #0 0x7f333466c7d6 in __GI_ppoll (fds=0x7f331c00b878, nfds=1, timeout=, sigmask=0x0) at ../sysdeps/unix/sysv/linux/ppoll.c:39 #1 0x7f20d141 in qt_safe_poll(pollfd*, unsigned long, timespec const*) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #2 0x7f20e5b9 in QEventDispatcherUNIX::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #3 0x7f1be16b in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f00d0b6 in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f333115c545 in () at /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #6 0x7f016c87 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f3331e47164 in start_thread (arg=) at pthread_create.c:486 #8 0x7f3334678def in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 2 (Thread 0x7f33294ca700 (LWP 10403)): #0 0x7f333466c6d9 in __GI___poll (fds=0x7f33294c9c78, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f3334171917 in () at /usr/lib/x86_64-linux-gnu/libxcb.so.1 #2 0x7f333417353a in xcb_wait_for_event () at /usr/lib/x86_64-linux-gnu/libxcb.so.1 #3 0x7f33299ac159 in () at /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5 #4 0x7f016c87 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f3331e47164 in start_thread (arg=) at pthread_create.c:486 #6 0x7f3334678def in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 1 (Thread 0x7f332a081840 (LWP 10383)): [KCrash Handler] #6 0x7f3332da9b0b in KWin::WindowQuadList::makeInterleavedArrays(unsigned int, KWin::GLVertex2D*, QMatrix4x4 const&) const () at /usr/lib/x86_64-linux-gnu/libkwineffects.so.11 #7 0x7f3320fdcf42 in () at /usr/lib/x86_64-linux-gnu/qt5/plugins/org.kde.kwin.scenes/KWinSceneOpenGL.so #8 0x7f3320fe58b9 in () at /usr/lib/x86_64-linux-gnu/qt5/plugins/org.kde.kwin.scenes/KWinSceneOpenGL.so #9 0x7f3320fe59e7 in () at /usr/lib/x86_64-linux-gnu/qt5/p
[digikam] [Bug 392727] Images are missing (Windows)
https://bugs.kde.org/show_bug.cgi?id=392727 caulier.gil...@gmail.com changed: What|Removed |Added Version|5.9.0 |6.1.0 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 392727] Images are missing (Windows)
https://bugs.kde.org/show_bug.cgi?id=392727 --- Comment #5 from p.st...@sternbyname.net --- Hi Gilles The behaviour is unchanged in 6.1.0. For instance I have a folder with 666 images, none of them duplicates, ie there is only one version of each image. On the Settings > Image Editor > Versioning tab, if I uncheck 'Always show original images' then one image disappears. If I uncheck 'Always show intermediate snapshots' then 11 more images disappear. This is with a pre-existing folder of course - the images were created with an earlier version of Digikam. Best wishes. Pablo -- You are receiving this mail because: You are watching all bug changes.
[latte-dock] [Bug 405252] Add a more definite hover effect to improve visual feedback /accessibility. (normal hover effect, like you see in menubars etc.)
https://bugs.kde.org/show_bug.cgi?id=405252 --- Comment #11 from leftcrane --- Well, I don't know about you but I am constantly clicking on the wrong items in the dock precisely because there is no visual feedback to tell me what I am about to click on. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 405234] Refresh does no work
https://bugs.kde.org/show_bug.cgi?id=405234 --- Comment #7 from harald.a...@web.de --- Created attachment 118769 --> https://bugs.kde.org/attachment.cgi?id=118769&action=edit digiKam Log Hi, Interesting tool -- hadn't heard of it before. The file name in line 466 is correct. The file name in line 468 is not -- somehow a second "Schottland" gets inserted. Hope this helps, and best regards, Harald -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 405234] Refresh does no work
https://bugs.kde.org/show_bug.cgi?id=405234 --- Comment #8 from harald.a...@web.de --- Of course, "file name" should have been "folder name", but I'm sure you guessed that. -- You are receiving this mail because: You are watching all bug changes.
[latte-dock] [Bug 405252] Add a more definite hover effect to improve visual feedback /accessibility. (normal hover effect, like you see in menubars etc.)
https://bugs.kde.org/show_bug.cgi?id=405252 --- Comment #12 from Michail Vourlakos --- Well I am constantly clicking the correct items and mouse pointer helps with that... BTW why don't you replace Latte plasmoid with a plasma taskmanager? -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 405353] Akonadi doesn't correctly assign "new" and "cur" mail within local-mail - deleted mail shows up again and again
https://bugs.kde.org/show_bug.cgi?id=405353 Robert David changed: What|Removed |Added CC||robert.david.public@gmail.c ||om --- Comment #1 from Robert David --- I can confirm wired behaviour of moving between "new" and "cur". I have different setup, fetching mail using mbsync and kmail is only client above these maildirs (I have multiple accounts). Clicking on new mail will handle it correctly (move from new to cur). But marking a folder as read will do nothing (let say it will mark the akonadi cache as read but do not propagate it lower). So when I clean the directory cache from akonadi and let it resync, the messages would be unread. Other side effect is that it would not resync to server, but this is issue of my not common setup (I was tired of regular hangs of akonadi imap sync mainly from our unstable stupid company imap server). -- You are receiving this mail because: You are watching all bug changes.
[kaffeine] [Bug 405278] [feature request] EPG from xmltv
https://bugs.kde.org/show_bug.cgi?id=405278 --- Comment #14 from Mauro Carvalho Chehab --- (In reply to higuita from comment #13) > > Well, as xmltv format allows multiple display names, IMHO, the right fix > > would be >to address those at the parser. > (...) > > Btw, no need to even modify the parser. A simple script using xmlstarlet > > would >be able to add new channel associations. > > your script to add to the xmltv file the same display names as DVB-T worked > great and i agree that is lot more clean than trying to workaround and map > things in kaffeine. This way the source xmltv is already fixed and even > doing rescan channels or adding new channels are easy to keep everything > working. Good! > > Again, thanks for the help and this feature > > > > There's one thing feature in Kaffeine's implementation, though: right now, > > it > > will associate just one channel to the EPG data. So, on a channel with both > > "SD" and "HD", it will fill EPG just for the first one. > > At least here in Portugal, the EPG data for SD and HD channels are the same, > so using the first one loaded on both versions of the channel is not really > a problem... i do not know if there are places where the data is really > different between those channels Here in Brazil, the same applies for ISDB-T (1seg, SD and HD) and for the DVB-C and DVB-S providers I'm aware - although here, EPG data is reliable for most channels and there's no xmltv grabber for Brazilian channels - AFAIKT. > > > >> Finally, editing the channel, we would have a new drop down list with the > > with the problem fixed in the xmltv file, i do not see the need to add this > now, at least for me, it is easier to maintain the map in the script than in > any (one by one) GUI. I suspect that this is always the case. Mapping it on GUI has a disadvantage: if a channel changes and a re-scan is needed, one has to re-map everything. > But a feature would still be useful, a column in the channel config window > to show what channels already have epg and those that don't. The alternative > is to manually click each channel to find out. in my setup, 62 clicks to > find 27 channels with EPG and 35 without You don't need to go to the channel's config window. Just open the EPG guide from the TV menu. All channels with EPG are there. > > Sadly i do not know how to program, so i can't really helping develop this :) That's a good opportunity to learn :-) > all i can do is open a new "feature request", if someone wants later to pick > this up (if you agree that this is useful too) -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 373178] Blurry scaling on HiDPI
https://bugs.kde.org/show_bug.cgi?id=373178 --- Comment #38 from younker...@gmail.com --- It's now 2019, and the issue still was not fixed yet for gwenview and digikam. Good thing is I found another one named qimgv which act right. So just use that for a temporary solution for viewing my photos. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 405234] Refresh does no work
https://bugs.kde.org/show_bug.cgi?id=405234 --- Comment #9 from harald.a...@web.de --- Created attachment 118770 --> https://bugs.kde.org/attachment.cgi?id=118770&action=edit Log when doing a manual Refresh The same log as above, but continued. This is how a manual "Refresh" is logged. Best regards, Harald -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 405353] Akonadi doesn't correctly assign "new" and "cur" mail within local-mail - deleted mail shows up again and again
https://bugs.kde.org/show_bug.cgi?id=405353 --- Comment #2 from Robert David --- Seems like duplicate bug is 376032. 376032 - Emails not being moved from "new" to "cur" -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 404572] Sorting by desktop not working
https://bugs.kde.org/show_bug.cgi?id=404572 --- Comment #17 from Michael D --- Yes, thanks very much for the quick fix! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 404644] Windows unable to resize fullscreen after disconnect of secondary monitor
https://bugs.kde.org/show_bug.cgi?id=404644
--- Comment #3 from Gstubbe ---
xprop -root before unplug:
_NET_WORKAREA(CARDINAL) = 0, 25, 2560, 2499
_KDE_SLIDE(_KDE_SLIDE) = 0x0
_KDE_PRESENT_WINDOWS_GROUP(_KDE_PRESENT_WINDOWS_GROUP) = 0x0
_KDE_PRESENT_WINDOWS_DESKTOP(_KDE_PRESENT_WINDOWS_DESKTOP) = 0x0
_KDE_KWIN_KSCREEN_SUPPORT(_KDE_KWIN_KSCREEN_SUPPORT) = 0x0
_KDE_WINDOW_HIGHLIGHT(_KDE_WINDOW_HIGHLIGHT) = 0x0
_KDE_NET_WM_BACKGROUND_CONTRAST_REGION(_KDE_NET_WM_BACKGROUND_CONTRAST_REGION)
= 0x0
_KDE_NET_WM_BLUR_BEHIND_REGION(_KDE_NET_WM_BLUR_BEHIND_REGION) = 0x0
_NET_CLIENT_LIST_STACKING(WINDOW): window id # 0x18f, 0x1800017, 0x3a1,
0x401, 0x487, 0x2600010, 0x260003d, 0x2600025, 0x2600031
_NET_CLIENT_LIST(WINDOW): window id # 0x18f, 0x1800017, 0x2600010,
0x2600025, 0x2600031, 0x260003d, 0x3a1, 0x401, 0x487
_NET_DESKTOP_GEOMETRY(CARDINAL) = 2560, 2584
_NET_ACTIVE_WINDOW(WINDOW): window id # 0x487
_NET_CURRENT_DESKTOP(CARDINAL) = 0
_NET_DESKTOP_VIEWPORT(CARDINAL) = 0, 0
_NET_NUMBER_OF_DESKTOPS(CARDINAL) = 1
_NET_DESKTOP_LAYOUT(CARDINAL) = 0, 1, 1, 0
_NET_DESKTOP_NAMES(UTF8_STRING) = "Desktop 1"
_NET_SUPPORTING_WM_CHECK(WINDOW): window id # 0x2a7
_NET_SUPPORTED(ATOM) = _NET_SUPPORTED, _NET_SUPPORTING_WM_CHECK,
_NET_CLIENT_LIST, _NET_CLIENT_LIST_STACKING, _NET_NUMBER_OF_DESKTOPS,
_NET_DESKTOP_GEOMETRY, _NET_CURRENT_DESKTOP, _NET_DESKTOP_NAMES,
_NET_ACTIVE_WINDOW, _NET_WORKAREA, _NET_DESKTOP_LAYOUT, _NET_CLOSE_WINDOW,
_NET_RESTACK_WINDOW, _NET_SHOWING_DESKTOP, _NET_WM_MOVERESIZE,
_NET_MOVERESIZE_WINDOW, _NET_WM_NAME, _NET_WM_VISIBLE_NAME, _NET_WM_DESKTOP,
_NET_WM_WINDOW_TYPE, _NET_WM_WINDOW_TYPE_NORMAL, _NET_WM_WINDOW_TYPE_DESKTOP,
_NET_WM_WINDOW_TYPE_DOCK, _NET_WM_WINDOW_TYPE_TOOLBAR,
_NET_WM_WINDOW_TYPE_MENU, _NET_WM_WINDOW_TYPE_DIALOG,
_NET_WM_WINDOW_TYPE_UTILITY, _NET_WM_WINDOW_TYPE_SPLASH,
_KDE_NET_WM_WINDOW_TYPE_OVERRIDE, _NET_WM_STATE, _NET_WM_STATE_MODAL,
_NET_WM_STATE_MAXIMIZED_VERT, _NET_WM_STATE_MAXIMIZED_HORZ,
_NET_WM_STATE_SHADED, _NET_WM_STATE_SKIP_TASKBAR, _NET_WM_STATE_SKIP_PAGER,
_KDE_NET_WM_STATE_SKIP_SWITCHER, _NET_WM_STATE_HIDDEN,
_NET_WM_STATE_FULLSCREEN, _NET_WM_STATE_ABOVE, _NET_WM_STATE_BELOW,
_NET_WM_STATE_DEMANDS_ATTENTION, _NET_WM_STATE_STAYS_ON_TOP, _NET_WM_STRUT,
_NET_WM_STRUT_PARTIAL, _NET_WM_ICON_GEOMETRY, _NET_WM_ICON, _NET_WM_PID,
_NET_WM_PING, _NET_WM_USER_TIME, _NET_STARTUP_ID, _NET_WM_FULLSCREEN_MONITORS,
_NET_WM_ALLOWED_ACTIONS, _NET_WM_ACTION_MOVE, _NET_WM_ACTION_RESIZE,
_NET_WM_ACTION_MINIMIZE, _NET_WM_ACTION_SHADE, _NET_WM_ACTION_MAXIMIZE_VERT,
_NET_WM_ACTION_MAXIMIZE_HORZ, _NET_WM_ACTION_FULLSCREEN,
_NET_WM_ACTION_CHANGE_DESKTOP, _NET_WM_ACTION_CLOSE, _NET_FRAME_EXTENTS,
_KDE_NET_WM_FRAME_STRUT, _KDE_NET_WM_TEMPORARY_RULES, _NET_WM_FULL_PLACEMENT,
_KDE_NET_WM_ACTIVITIES, _KDE_NET_WM_SHADOW, _NET_WM_OPAQUE_REGION
KWIN_RUNNING(KWIN_RUNNING) = 0x1
_ORG_KDE_KWIN_DBUS_SERVICE(UTF8_STRING) = "org.kde.KWin"
AT_SPI_BUS(STRING) =
"unix:abstract=/tmp/dbus-0qH7SrLoHM,guid=ce0c25eca16c98b3356904525c88f663"
GDK_VISUALS(INTEGER) = 274, 353
PULSE_COOKIE(STRING) =
"12295a02397b36dcf54ea994eb7df104f3df7c04a80577b4a82dbe2d04e0c0c07d2c9761c542376f55964d21334ecd39b684f21f40d688cd201d797af34af503b278a002153c0d541902127e99a5147fd6ae41706b27c20c7242d22411f1f92308f5dc639688fd208351a41c90179c158d9e2838001019c2151d063e44d635d6085d4d4f48d0b1de28a1d7fa3eb2c3684b45fa33cee99b3cce04a267f67b724261c6acfdcf00aa8d10df8da8106d2a1302e33f305337691493cc6294033f2d096602c9fd28f4229331af47f3dd1c91a2de68d31b8324911e68871b8da6f3f22290c26645d2ce5b299a4c753ed3f3dcdaea95ddf01b0ba1e300bf20c85836bc25"
PULSE_SERVER(STRING) =
"{94a22df02f584e2db4437b776659a21c}unix:/run/user/1000/pulse/native"
PULSE_SESSION_ID(STRING) = "c2"
PULSE_ID(STRING) = "1000@94a22df02f584e2db4437b776659a21c/747"
_QT_SETTINGS_TIMESTAMP_:0(_QT_SETTINGS_TIMESTAMP_:0) = 0x0, 0x0, 0x0, 0x0, 0x0,
0x25, 0x83, 0xbc, 0x2, 0xe0, 0x1c, 0x6, 0x0
RESOURCE_MANAGER(STRING) =
"*Box.background:\t#31363b\n*Box.foreground:\t#eff0f1\n*Button.activeBackground:\t#31363b\n*Button.activeForeground:\t#eff0f1\n*Button.background:\t#31363b\n*Button.foreground:\t#eff0f1\n*Button.highlightBackground:\t#31363b\n*Button.highlightColor:\t#eff0f1\n*Canvas.activeBackground:\t#232629\n*Canvas.activeForeground:\t#eff0f1\n*Canvas.background:\t#232629\n*Canvas.foreground:\t#eff0f1\n*Canvas.highlightBackground:\t#232629\n*Canvas.highlightColor:\t#eff0f1\n*Canvas.selectbackground:\t#3daee9\n*Canvas.selectforeground:\t#eff0f1\n*Checkbutton.activeBackground:\t#31363b\n*Checkbutton.activeForeground:\t#eff0f1\n*Checkbutton.background:\t#31363b\n*Checkbutton.foreground:\t#eff0f1\n*Checkbutton.highlightBackground:\t#31363b\n*Checkbutton.highlightColor:\t#eff0f1\n*Command.background:\t#31363b\n*Command.foreground:\t#eff0f1\n*Dialog.background:\t#31363b\n*Dialog.foreground:\t#eff0f1\n*Entry.activeBackground:\t#232629\n*Entry.activeForeground:\t#eff0f1\n*Entry.background:\t#232629\n*Entry.foreground:\t#eff0f1\n*Entry.highlightBackground:\t#232629\n*Entry
[latte-dock] [Bug 405252] Add a more definite hover effect to improve visual feedback /accessibility. (normal hover effect, like you see in menubars etc.)
https://bugs.kde.org/show_bug.cgi?id=405252 --- Comment #13 from leftcrane --- lol it's cause I need the cycle effect. The KDE dock has no decent alternative for switching between grouped windows. Also the indicators are really poorly executed. Imo, Latte dock would be ideal if it kept the magnification feature - which is useful on small screens, but stuck to a sane default style, like Gnome dash to dock. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 403434] Incompatible version of Qt/qutebrowser packaged
https://bugs.kde.org/show_bug.cgi?id=403434 --- Comment #1 from Harald Sitter --- The situation is fairly terrible to be sure. If/when https://phabricator.kde.org/T10282 gets implemented we can supposedly hide it from software stores, alas, that does nothing for CLIs which generally offer no 100% way to prevent installation of something. Perhaps a larger design goal behind this should be to actively force application installation to not ever go to distribution packages but instead go for snaps or flatpaks. -- You are receiving this mail because: You are watching all bug changes.
[latte-dock] [Bug 405252] Add a more definite hover effect to improve visual feedback /accessibility. (normal hover effect, like you see in menubars etc.)
https://bugs.kde.org/show_bug.cgi?id=405252 --- Comment #14 from Michail Vourlakos --- Gnome dask to dock does not have parabolic effect, You could try Plasma or Unity style indicators in Latte master version, you won't lose parabolic effect with them... They are considered of course work in progress currently, more touches are missing for them -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 404644] Windows unable to resize fullscreen after disconnect of secondary monitor
https://bugs.kde.org/show_bug.cgi?id=404644
--- Comment #4 from Gstubbe ---
xrandr -q in broken state:
Screen 0: minimum 8 x 8, current 2256 x 1504, maximum 32767 x 32767
eDP1 connected primary 2256x1504+0+0 (normal left inverted right x axis y axis)
290mm x 190mm
2256x1504 60.00*+ 48.01
1856x1392 60.01
1792x1344 60.01
2048x1152 59.9059.91
1920x1200 59.8859.95
1920x1080 59.9659.93
1600x1200 60.00
1680x1050 59.9559.88
1400x1050 59.98
1600x900 59.9559.82
1280x1024 60.02
1400x900 59.9659.88
1280x960 60.00
1368x768 59.8859.85
1280x800 59.8159.91
1280x720 59.8659.74
1128x752 60.00
1024x768 60.00
1024x576 59.9059.82
960x540 59.6359.82
800x600 60.3256.25
864x486 59.9259.57
640x480 59.94
720x405 59.5158.99
640x360 59.8459.32
DP1 disconnected (normal left inverted right x axis y axis)
DP2 disconnected (normal left inverted right x axis y axis)
HDMI1 disconnected (normal left inverted right x axis y axis)
HDMI2 disconnected (normal left inverted right x axis y axis)
VIRTUAL1 disconnected (normal left inverted right x axis y axis)
xprop -root in broken state:
_KDE_SLIDE(_KDE_SLIDE) = 0x0
_KDE_PRESENT_WINDOWS_GROUP(_KDE_PRESENT_WINDOWS_GROUP) = 0x0
_KDE_PRESENT_WINDOWS_DESKTOP(_KDE_PRESENT_WINDOWS_DESKTOP) = 0x0
_KDE_KWIN_KSCREEN_SUPPORT(_KDE_KWIN_KSCREEN_SUPPORT) = 0x0
_KDE_WINDOW_HIGHLIGHT(_KDE_WINDOW_HIGHLIGHT) = 0x0
_KDE_NET_WM_BACKGROUND_CONTRAST_REGION(_KDE_NET_WM_BACKGROUND_CONTRAST_REGION)
= 0x0
_KDE_NET_WM_BLUR_BEHIND_REGION(_KDE_NET_WM_BLUR_BEHIND_REGION) = 0x0
KWIN_RUNNING(KWIN_RUNNING) = 0x1
_ORG_KDE_KWIN_DBUS_SERVICE(UTF8_STRING) = "org.kde.KWin"
_NET_WORKAREA(CARDINAL) = 0, 0, 2256, 1444
_NET_CLIENT_LIST_STACKING(WINDOW): window id # 0x18f, 0x3a1, 0x401,
0x487, 0x2600031, 0x2600010
_NET_CLIENT_LIST(WINDOW): window id # 0x18f, 0x3a1, 0x401,
0x487, 0x2600031, 0x2600010
_NET_DESKTOP_GEOMETRY(CARDINAL) = 2256, 1504
_NET_ACTIVE_WINDOW(WINDOW): window id # 0x487
_NET_CURRENT_DESKTOP(CARDINAL) = 0
_NET_DESKTOP_VIEWPORT(CARDINAL) = 0, 0
_NET_NUMBER_OF_DESKTOPS(CARDINAL) = 1
_NET_DESKTOP_LAYOUT(CARDINAL) = 0, 1, 1, 0
_NET_DESKTOP_NAMES(UTF8_STRING) = "Desktop 1"
_NET_SUPPORTING_WM_CHECK(WINDOW): window id # 0x4c7
_NET_SUPPORTED(ATOM) = _NET_SUPPORTED, _NET_SUPPORTING_WM_CHECK,
_NET_CLIENT_LIST, _NET_CLIENT_LIST_STACKING, _NET_NUMBER_OF_DESKTOPS,
_NET_DESKTOP_GEOMETRY, _NET_CURRENT_DESKTOP, _NET_DESKTOP_NAMES,
_NET_ACTIVE_WINDOW, _NET_WORKAREA, _NET_DESKTOP_LAYOUT, _NET_CLOSE_WINDOW,
_NET_RESTACK_WINDOW, _NET_SHOWING_DESKTOP, _NET_WM_MOVERESIZE,
_NET_MOVERESIZE_WINDOW, _NET_WM_NAME, _NET_WM_VISIBLE_NAME, _NET_WM_DESKTOP,
_NET_WM_WINDOW_TYPE, _NET_WM_WINDOW_TYPE_NORMAL, _NET_WM_WINDOW_TYPE_DESKTOP,
_NET_WM_WINDOW_TYPE_DOCK, _NET_WM_WINDOW_TYPE_TOOLBAR,
_NET_WM_WINDOW_TYPE_MENU, _NET_WM_WINDOW_TYPE_DIALOG,
_NET_WM_WINDOW_TYPE_UTILITY, _NET_WM_WINDOW_TYPE_SPLASH,
_KDE_NET_WM_WINDOW_TYPE_OVERRIDE, _NET_WM_STATE, _NET_WM_STATE_MODAL,
_NET_WM_STATE_MAXIMIZED_VERT, _NET_WM_STATE_MAXIMIZED_HORZ,
_NET_WM_STATE_SHADED, _NET_WM_STATE_SKIP_TASKBAR, _NET_WM_STATE_SKIP_PAGER,
_KDE_NET_WM_STATE_SKIP_SWITCHER, _NET_WM_STATE_HIDDEN,
_NET_WM_STATE_FULLSCREEN, _NET_WM_STATE_ABOVE, _NET_WM_STATE_BELOW,
_NET_WM_STATE_DEMANDS_ATTENTION, _NET_WM_STATE_STAYS_ON_TOP, _NET_WM_STRUT,
_NET_WM_STRUT_PARTIAL, _NET_WM_ICON_GEOMETRY, _NET_WM_ICON, _NET_WM_PID,
_NET_WM_PING, _NET_WM_USER_TIME, _NET_STARTUP_ID, _NET_WM_FULLSCREEN_MONITORS,
_NET_WM_ALLOWED_ACTIONS, _NET_WM_ACTION_MOVE, _NET_WM_ACTION_RESIZE,
_NET_WM_ACTION_MINIMIZE, _NET_WM_ACTION_SHADE, _NET_WM_ACTION_MAXIMIZE_VERT,
_NET_WM_ACTION_MAXIMIZE_HORZ, _NET_WM_ACTION_FULLSCREEN,
_NET_WM_ACTION_CHANGE_DESKTOP, _NET_WM_ACTION_CLOSE, _NET_FRAME_EXTENTS,
_KDE_NET_WM_FRAME_STRUT, _KDE_NET_WM_TEMPORARY_RULES, _NET_WM_FULL_PLACEMENT,
_KDE_NET_WM_ACTIVITIES, _KDE_NET_WM_SHADOW, _NET_WM_OPAQUE_REGION
AT_SPI_BUS(STRING) =
"unix:abstract=/tmp/dbus-0qH7SrLoHM,guid=ce0c25eca16c98b3356904525c88f663"
GDK_VISUALS(INTEGER) = 274, 353
PULSE_COOKIE(STRING) =
"12295a02397b36dcf54ea994eb7df104f3df7c04a80577b4a82dbe2d04e0c0c07d2c9761c542376f55964d21334ecd39b684f21f40d688cd201d797af34af503b278a002153c0d541902127e99a5147fd6ae41706b27c20c7242d22411f1f92308f5dc639688fd208351a41c90179c158d9e2838001019c2151d063e44d635d6085d4d4f48d0b1de28a1d7fa3eb2c3684b45fa33cee99b3cce04a267f67b724261c6acfdcf00aa8d10df8da8106d2a1302e33f305337691493cc6294033f2d096602c9fd28f4229331af47f3dd1c91a2de68d31b8324911e68871b8da6f3f22290c26645d2ce5b299a4c753ed3f3dcdaea95ddf01b0ba1e300bf20c85836bc25"
PULSE_SERVER(STRING) =
"{94a22df02f584e2db4437b776659a21c}unix:/run/user/1000/pulse/native"
PULSE_SESSION_ID(STRING) = "c2"
PULSE_ID(STRING) = "1000@94a22df02f584e2db4437b776659a21c/747"
_QT_SETTINGS_
[plasmashell] [Bug 404644] Windows unable to resize fullscreen after disconnect of secondary monitor
https://bugs.kde.org/show_bug.cgi?id=404644 --- Comment #5 from Gstubbe --- I can also confirm that 'kwin --replace &' does not fix the issue. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 348172] Scaling options missing in print dialog
https://bugs.kde.org/show_bug.cgi?id=348172 Murz changed: What|Removed |Added CC||mur...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 405428] New: Secondary monitor positioned to right acts as a primary monitor (windows positions are not remembered either)
https://bugs.kde.org/show_bug.cgi?id=405428 Bug ID: 405428 Summary: Secondary monitor positioned to right acts as a primary monitor (windows positions are not remembered either) Product: kwin Version: 5.14.3 Platform: Kubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: multihead Assignee: kwin-bugs-n...@kde.org Reporter: leftcr...@tutanota.com Target Milestone: --- Operating System: Kubuntu 18.10 KDE Plasma Version: 5.15.2 KDE Frameworks Version: 5.54.0 Qt Version: 5.11.1 Kernel Version: 4.18.0-16-generic OS Type: 64-bit Display server: X11 This occurs when you have two monitors connected to a laptop (screen inactive) and the right-hand one is primary. Once you disconnect the monitors and reconnect, windows start to appear on the left-hand monitor (even if the mouse is on the primary monitor). This goes for both windows that were already open, which get moved to the right-hand monitor and for some new windows. This includes, notably, the full-screen program launcher. Even though its icon is located on the right screen, the launcher opens on the left after disconnect/reconnect. The same is true for many other programs, with the exception of the latest KDE and Gnome software. They get launched on the secondary monitor. Window positions aren't being remembered either - they always go to the non-primary monitor on the left, for most programs. Interestingly, latte panels from the left secondary monitor shift to the right upon disconnecting the secondary monitor. I can't tell if this is due to the latest KDE upgrade or due to me having switched my secondary monitor from right to left side a week ago. (I have active screen follows mouse enabled). I realize that is is not an exhaustive or terribly clear summary of the bug, but please be on the lookout for it. It's extremely annoying. I am not sure I can document this much further. It's a complex bug and I have a solution that works well enough for me: I just have a hotkey that restarts KWin, Latte, and Plasma every time I disconnect/reconnect monitors. Luckily KDE perfromance is good enough to permit this workaround. -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 390424] Reordering applications in the Application Dashboard favorites, launches applications
https://bugs.kde.org/show_bug.cgi?id=390424 Thibaut FRANCOIS changed: What|Removed |Added CC||t...@humeurlibre.fr -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 404519] Adding Hold Frames to a horizontal range often removes selection
https://bugs.kde.org/show_bug.cgi?id=404519 Bollebib changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- --- Comment #2 from Bollebib --- https://www.youtube.com/watch?v=VuL3ZRMttsg&feature=youtu.be It still happens in today's nightly At a certain moment I DID get to keep the selection. But then another issue arose if you ADD to the selection then the later selected frames go out of bounds of the selection The selection should grow and shrink with the frames for the most consitant behaviour. -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 390424] Reordering applications in the Application Dashboard favorites, launches applications
https://bugs.kde.org/show_bug.cgi?id=390424 --- Comment #10 from Thibaut FRANCOIS --- After draging, sometimes the application isn't launch, but each time after draging an application, the dashboard closes. So it's necessary to re-open the dashoard to continue to reordering the favorites, it's not at all practical in terms of behaviour. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 405428] Secondary monitor positioned to right acts as a primary monitor (windows positions are not remembered either)
https://bugs.kde.org/show_bug.cgi?id=405428 --- Comment #1 from leftcrane --- I'll just add that some apps appear confused about the primary monitor while others (like inkscape opening a file) actively want to appear on the right-hand secondary monitor. (for these latter apps, I have a KWin rule to force them to the primary screen). -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 404246] Data loss - Lost frames if you add many holds to a range of frames
https://bugs.kde.org/show_bug.cgi?id=404246 Bollebib changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED --- Comment #2 from Bollebib --- https://www.youtube.com/watch?v=tyLnDSvGX64&feature=youtu.be tested in the current nightly it still happens I go over details in the video -- You are receiving this mail because: You are watching all bug changes.
[buildsystem] [Bug 369554] sleeper design bug in the installation layout due to assumptions about filesystem case sensitivity
https://bugs.kde.org/show_bug.cgi?id=369554 --- Comment #8 from RJVB --- >This is definitely not just about two frameworks, it's about ALL of them. Look >at it, they all install forwarding headers. Did you miss the bit where I said the others all install the forwarding headers at the same level? :) >counter-productive. We want to make sure each framework is explicitly used, not >just by chance. A moot concern given how you still keep the framework-specific directories if you use include/KF5/Attica/AccountBalance include/KF5/Attica/accountbalance.h #include #include instead of include/KF5/Attica/fwd/Attica/AccountBalance include/KF5/Attica/attica/accountbalance.h #include #include In addition, the former implementation will allow installing the frameworks as proper (Mac) frameworks. >Fixed. I'm still not convinced that I find this an improvement (= fix); increase the amount of I/O required just to get (supposedly) nicer looking #include lines? -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 405366] Flatten image with alpha inheritance in python results in a blank image.
https://bugs.kde.org/show_bug.cgi?id=405366 --- Comment #2 from wolthera --- Created attachment 118771 --> https://bugs.kde.org/attachment.cgi?id=118771&action=edit File to open with the script. This file reproduces the bug with Krita Version: 4.2.0-pre-alpha (git 52ee93a) on KDE Neon. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 399287] amd64 front end: Illegal Instruction vcmptrueps
https://bugs.kde.org/show_bug.cgi?id=399287 Julian Seward changed: What|Removed |Added Summary|Illegal Instruction |amd64 front end: Illegal |vcmptrueps |Instruction vcmptrueps -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 404644] Windows unable to resize fullscreen after disconnect of secondary monitor
https://bugs.kde.org/show_bug.cgi?id=404644 --- Comment #6 from Gstubbe --- I can also confirm restart plasmashell does also not fix it. The only thing fixing it currently is logging out and logging back in with sddm -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 399287] amd64 front end: Illegal Instruction vcmptrueps
https://bugs.kde.org/show_bug.cgi?id=399287 Julian Seward changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #3 from Julian Seward --- Fixed: ecc4e970936b8ab2057f0a899d220ac611e83c3e implementation ea09451baf13c13dfea3869b0df34b677e0557bb test cases -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 405403] s390x disassembler cannot be used on x86
https://bugs.kde.org/show_bug.cgi?id=405403 --- Comment #1 from Andreas Arnez --- Ilya, thanks for the patch. Your patch makes the code independent from endianness and a bit shorter than before. In my view this is a useful clean-up, and I haven't seen any problems with it in my testing. So I'd like to push this, if there are no objections. Does anyone see any issues with Ilya's approach? -- You are receiving this mail because: You are watching all bug changes.
[latte-dock] [Bug 405252] Add a more definite hover effect to improve visual feedback /accessibility. (normal hover effect, like you see in menubars etc.)
https://bugs.kde.org/show_bug.cgi?id=405252 --- Comment #15 from leftcrane --- I know, but this isn't about the indicators - it's about the hover effect. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 405429] New: Onion skin color filters - Arrange the colors horizontally,without dropdown
https://bugs.kde.org/show_bug.cgi?id=405429 Bug ID: 405429 Summary: Onion skin color filters - Arrange the colors horizontally,without dropdown Product: krita Version: 4.1.7 Platform: Other OS: MS Windows Status: REPORTED Severity: wishlist Priority: NOR Component: Animation Assignee: krita-bugs-n...@kde.org Reporter: kwadraatn...@hotmail.com Target Milestone: --- I would like that the onion skin filter colors would just be put horizontally under the onion skin sliders. They dont need to be in a dropdown,there is enough space to accomodate them there. It would also speed up the usage significantly,by not requiring that extra click It's seemingly small issue,but it has prevented me from using this feature -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 405429] JJ: Onion skin color filters - Arrange the colors horizontally,without dropdown
https://bugs.kde.org/show_bug.cgi?id=405429 Scott Petrovic changed: What|Removed |Added Summary|Onion skin color filters - |JJ: Onion skin color |Arrange the colors |filters - Arrange the |horizontally,without|colors horizontally,without |dropdown|dropdown CC||scottpetro...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 405429] JJ: Onion skin color filters - Arrange the colors horizontally,without dropdown
https://bugs.kde.org/show_bug.cgi?id=405429 Scott Petrovic changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|CONFIRMED --- Comment #1 from Scott Petrovic --- This is a good idea. We have the space. Confirming and marking this as a junior job. -- You are receiving this mail because: You are watching all bug changes.
[buildsystem] [Bug 369554] sleeper design bug in the installation layout due to assumptions about filesystem case sensitivity
https://bugs.kde.org/show_bug.cgi?id=369554 --- Comment #9 from David Faure --- Ah you're still confused by non-namespaced frameworks vs namespaced frameworks. KIO, KParts and others behave like Attica: the class is namespaced (KParts::Part) so the forwarding header is namespaced (KParts/Part). And it still has to be inside the framework-specific directory, so yes, KF5/KParts/fwd/KParts/Part. include/KF5/Attica/AccountBalance #include Would mean the include works even if you didn't ask to use Attica via find_package, that's what we want to prevent here. Can we accept this and move on? All of this is just additional discussion that is not related to the bug at hand. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 405430] New: Use gcc -Wimplicit-fallthrough=2 by default if available
https://bugs.kde.org/show_bug.cgi?id=405430
Bug ID: 405430
Summary: Use gcc -Wimplicit-fallthrough=2 by default if
available
Product: valgrind
Version: 3.15 SVN
Platform: Other
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: general
Assignee: jsew...@acm.org
Reporter: m...@klomp.org
CC: mips3...@gmail.com
Target Milestone: ---
I would like to enable -Wimplicit-fallthrough=2 by default when available. It
was introduced in GCC7. It caught a couple of bugs, but it does need a bit of
extra comments to explain when a switch case statement fall-through is
deliberate. Luckily with -Wimplicit-fallthrough=2 various existing comments
already do that. I have fixed the bugs, but adding explicit break statements
where necessary and added comments where the fall-through was correct.
There is just one place that produces a warning for a fallthrough that I am not
sure is deliberate or not.
priv/guest_mips_toIR.c: In function ‘disInstr_MIPS_WRK’:
priv/guest_mips_toIR.c:30205:13: warning: this statement may fall through
[-Wimplicit-fallthrough=]
if (VEX_MIPS_COMP_ID(archinfo->hwcaps) == VEX_PRID_COMP_CAVIUM) {
^
priv/guest_mips_toIR.c:30211:7: note: here
case 0xC: /* INSV */
^~~~
--
You are receiving this mail because:
You are watching all bug changes.
[kstars] [Bug 405393] KSTAR version 3.1 seems to require OS-X 10.12 to run
https://bugs.kde.org/show_bug.cgi?id=405393 Jasem Mutlaq changed: What|Removed |Added CC||mutla...@ikarustech.com --- Comment #1 from Jasem Mutlaq --- Ok, we had to change to 10.12 because of Qt. We will update the KStars page to reflect that. -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 405393] KSTAR version 3.1 seems to require OS-X 10.12 to run
https://bugs.kde.org/show_bug.cgi?id=405393 Jasem Mutlaq changed: What|Removed |Added Resolution|--- |INTENTIONAL Status|REPORTED|RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 405430] Use gcc -Wimplicit-fallthrough=2 by default if available
https://bugs.kde.org/show_bug.cgi?id=405430
--- Comment #1 from Julian Seward ---
+1 for this; I am all in favour of more compile-time analysis.
As far as the guest_mips_toIR.c fallthrough goes, I'd guess it is
intended. I say this because it looks as if all 3 of
case 0xA: /* LX */
case 0xC: /* INSV */
case 0x38: { /* EXTR.W */
are handled by the call to disDSPInstr_MIPS_WRK at line 30212. At least,
from a quick check, it looks like disDSPInstr_MIPS_WRK handles them all.
But it is so huge it's hard to tell for sure.
--
You are receiving this mail because:
You are watching all bug changes.
[ksysguard] [Bug 353497] Graph shows double of the real data rate
https://bugs.kde.org/show_bug.cgi?id=353497 --- Comment #4 from keln...@gmail.com --- I don't even use KDE anymore - not now at least. But Jimmy seemingly answered the mystery: I was most probably using a VPN at that time. So it's probably not a bug, but I don't think measurement should work this way. 30 Mb left my computer in a second, not 60. I don't think it's useful information for the user how much data is passed between physical and logical network interfaces combined. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 405431] New: "next/previous FILTERED frame"
https://bugs.kde.org/show_bug.cgi?id=405431 Bug ID: 405431 Summary: "next/previous FILTERED frame" Product: krita Version: 4.1.7 Platform: Other OS: MS Windows Status: REPORTED Severity: wishlist Priority: NOR Component: Animation Assignee: krita-bugs-n...@kde.org Reporter: kwadraatn...@hotmail.com Target Milestone: --- Using filters in onion skins is very powerful but it would be good to have a 2 extra shortcuts to only go to next and previous FILTERED frame this would be different from the current functions we already have it would be an adjusted Previous/Next KEYFRAME function Alternatively it could be a function that uses the Previous/Next KEYFRAME function ,without changing it. But you need to activate a button or shortcut to go into this mode This has the benefit of needing only one shortcut,or even none if you use the button. And you can reuse your current shortcuts. the button can be put underneath the tint color options in onion skin,maybe -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 405403] s390x disassembler cannot be used on x86
https://bugs.kde.org/show_bug.cgi?id=405403 --- Comment #2 from Julian Seward --- (In reply to Andreas Arnez from comment #1) Andreas, if you think the patch is OK, and won't cause regressions, then fine, land it. It is however a huge patch and it would be nice to have a few lines of description in the commit message explaining what it does. This will, I assume, create rebase issues for any other unlanded s390 front end patches. But IIUC, that's only the initial z14 work. Yes? -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 405430] Use gcc -Wimplicit-fallthrough=2 by default if available
https://bugs.kde.org/show_bug.cgi?id=405430
Mark Wielaard changed:
What|Removed |Added
Ever confirmed|0 |1
Status|REPORTED|ASSIGNED
Assignee|jsew...@acm.org |m...@klomp.org
--- Comment #2 from Mark Wielaard ---
Created attachment 118772
--> https://bugs.kde.org/attachment.cgi?id=118772&action=edit
Enable GCC7 -Wimplicit-fallthrough=2 by default when available
The changes to Makefile.all.am and configure.ac are simply to test if
-Wimplicit-fallthrough=2 is available and enable it by default.
https://developers.redhat.com/blog/2017/03/10/wimplicit-fallthrough-in-gcc-7/
VEX/priv/guest_amd64_toIR.c: VROUNDPS should not fallthrough to VROUNDPD and
VROUNDPD should not fallthrough to VROUNDSS/VROUNDSD.
VEX/priv/guest_arm64_toIR.c: Move fallthrough comments so GCC recognizes them.
VEX/priv/guest_arm_toIR.c: Likewise
VEX/priv/guest_mips_toIR.c: Add fillthrough comments for cases that just add
signaling. Add breaks after emitting an ILLEGAL_INSTRUCTION.
I am unsure about the following block:
/* --- MIPS32(r2) DSP ASE(r2) / Cavium Specfic (LX) instructions --- */
case 0xA: /* LX */
if (VEX_MIPS_COMP_ID(archinfo->hwcaps) == VEX_PRID_COMP_CAVIUM) {
if (dis_instr_CVM(cins))
break;
goto decode_failure;
}
/* ??? */
case 0xC: /* INSV */
case 0x38: { /* EXTR.W */
if (VEX_MIPS_PROC_DSP(archinfo->hwcaps)) {
UInt retVal = disDSPInstr_MIPS_WRK ( cins );
if (0 != retVal ) {
goto decode_failure_dsp;
}
break;
} else {
goto decode_failure_dsp;
}
break;
}
Should the LX (0xA) case fall through to INSV EXTR.W or is that a missing
break?
VEX/priv/guest_ppc_toIR.c: Add a fallthrough comment when the immedizate offset
is partially given by simm16. dadd, dsub, dmul and ddiv should not fallthrough
to dcmpo, dcmpu if they couldn't be decoded. Add comment for xsabsqp,
xsxexpqp,xsnabsqp, xsnegqp, xsxsigqp fallthrough to VSX Scalar Quad-Precision
instructions.
VEX/priv/guest_x86_toIR.c: Add fallthrough comments for REP[N][E] cases.
VEX/priv/host_arm64_isel.c: Replace comment with explicit goto irreducible. I
don't trust the comment is correct and if the intent is to signal irreducible
lets just do that.
VEX/priv/host_arm_isel.c: Likewise.
VEX/priv/host_mips_defs.c: Add explicit fallthrough comments in mkFormBIT.
VEX/priv/host_mips_isel.c: Add fallthrough comments after vassert(mode64).
coregrind/m_gdbserver/m_gdbserver.c: Add comment explaining that if
give_control_back_to_vgdb returns then the fallthrough to the vg_assert is
correct.
coregrind/m_syswrap/syswrap-linux.c: Move vfork comment so GCC recognizes it.
VKI_BPF_BTF_LOAD should not fallthrough to VKI_BPF_TASK_FD_QUERY.
memcheck/mc_malloc_wrappers.c: Change fallback comments to fallthrough.
--
You are receiving this mail because:
You are watching all bug changes.
[valgrind] [Bug 405430] Use gcc -Wimplicit-fallthrough=2 by default if available
https://bugs.kde.org/show_bug.cgi?id=405430 Mark Wielaard changed: What|Removed |Added CC||c...@us.ibm.com -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 395496] Weather applet layout offset to the right and not visible with long city names
https://bugs.kde.org/show_bug.cgi?id=395496
--- Comment #4 from Adel Q ---
(In reply to Christoph Feck from comment #1)
> Is it caused by the long city name? Does it reproduce with a shorter name?
> Which weather provider are you using?
Yes, it is caused by the long city name. When using a shorter city name, the
tabs are shown fine. I am using the NOAA weather provider. The location to
reproduce is "Detroit, Detroit Metropolitan Wayne County Airport, MI (noaa)".
(In reply to Duncan from comment #3)
> This second method, adding the weather-report plasmoid directly to the panel
> (or desktop if preferred), instead of nesting it inside the system-tray
> plasmoid, avoids the popup-window size constraints of the system-tray, thus
> avoiding the problem. =:^)
I can confirm that this happens in my case as well -- the plasmoid resizes to
the full width of the city name when placed as an independent plasmoid rather
than in the system-tray. I think the preferred behavior should be truncating
the location name with "..." rather than overextending. For an extreme example,
try the "Bloomington/Normal, Central Illinois Regional Airport at
Bloomington-Normal" NOAA station, the weather widget shouldn't take up half the
screen.
For testing purposes of different stations, you can use the following to get
the list of NOAA stations sorted by length:
wget https://w1.weather.gov/xml/current_obs/index.xml
xmllint --xpath '//station/station_name/text()' index.xml | awk '{ print
length, $0 }' | sort -rns | less
Bug is still reproducible in the most current releases.
Distro: Arch Linux (up to date)
Qt Version: 5.12.1
KDE Plasma Version: 5.15.3
KDE Frameworks Version: 5.56.0
--
You are receiving this mail because:
You are watching all bug changes.
[latte-dock] [Bug 405252] Add a more definite hover effect to improve visual feedback /accessibility. (normal hover effect, like you see in menubars etc.)
https://bugs.kde.org/show_bug.cgi?id=405252 --- Comment #16 from Michail Vourlakos --- Indicators will have their own hover effects if they want -- You are receiving this mail because: You are watching all bug changes.
