[kdenlive] [Bug 361773] Kdenlive freeze - edit external altered project
https://bugs.kde.org/show_bug.cgi?id=361773 --- Comment #6 from Ovidiu-Florin BOGDAN--- The source clip in question is 3,8GB. If you want I can send it to you somehow, in private. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 361047] Wishlist: make grouped images more prominently visible [patch]
https://bugs.kde.org/show_bug.cgi?id=361047 --- Comment #11 from caulier.gil...@gmail.com --- Thanks Omar for you patch. 1/ code cosmetic : * Always add a space after a coma, especially with methods arguments. * Try to always align code with multi-lines * Wrap code with bracket after if/else statements, especially with multi-lines. 2/ new border : why the rotated frames are not centered with thumb center ? It's wanted ? They show more visible on the bottom side. 3/ optimization : these calls to generateFuzzyRect() are time consuming : +QPixmap ThumbBarDock::generateFuzzyRectForGroup(const QSize& size, const QColor& color, int radius) +{ +// Create two normal borders +QPixmap border1 = generateFuzzyRect(size,color,radius); +QPixmap border2 = generateFuzzyRect(size,color,radius); For some thumbnails it's not a problem. But imagine in an album with 100 grouped items ? Why not yo simply make deep copy of first pixmap ? 4/ Go to Setup/Album-View, and turn on huge thumbnail support for HD screen (thumbs >256 pixels size). The grouped frame do not work. Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 357471] Dolphin opens .desktop files in Kate
https://bugs.kde.org/show_bug.cgi?id=357471 Peter Rootschanged: What|Removed |Added Resolution|--- |FIXED Status|UNCONFIRMED |RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 361726] WARNING:unhandled syscall on ppc64
https://bugs.kde.org/show_bug.cgi?id=361726 Abhishekchanged: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|UNCONFIRMED |NEEDSINFO --- Comment #2 from Abhishek --- Hi Josef, Thanks. I have checked the latest version of Valgrind 3.11 and these syscall handlers are not implemented in newer version as well on PPC64 architecture. Please help me how can I proceed further to resolve this issue. Regards, Abhishek -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kservice] [Bug 353203] 20 seconds delay on kde login with kservice 5.14.3
https://bugs.kde.org/show_bug.cgi?id=353203 --- Comment #52 from Søren Holm--- This bug has - for kubuntu 16.04 - been completely solved until a few days ago. Can anyone confirm that? -- You are receiving this mail because: You are watching all bug changes.
[konversation] [Bug 345574] Konversation segfault upon changing widget style
https://bugs.kde.org/show_bug.cgi?id=345574 krasnochanged: What|Removed |Added CC||krasnog...@gmail.com --- Comment #2 from krasno --- I also experience this issue. I changed Breeze settings and Konversation crashed. Qt 5.6, Konversation 1.6. Current Arch. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 361952] kicker v5.6.2 still use KF5::ActivitiesExperimentalStats of kactivities-5.16.0 deprecated in v5.21.0
https://bugs.kde.org/show_bug.cgi?id=361952 --- Comment #3 from Leslie Zhai--- (In reply to Bhushan Shah from comment #1) > On Tue, Apr 19, 2016 at 10:21 AM, Leslie Zhai via KDE Bugzilla > wrote: > > but KF5::ActivitiesExperimentalStats was deprecated in kactivities-5.21.0 > > already, so History/Recentusage is empty! > > New framework : kactivities-stats was released. kactivities-stats is not relative with ActivitiesExperimentalStats, and it is ivan's branch ;-) https://github.com/KDE/kactivities/tree/ivan/libkactivities-experimental-stats so I git pull the latest plasma-desktop, and diff with plasma-desktop-5.6.2 to generate the kicker conflict kactivities version patch ;-P -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 361952] kicker v5.6.2 still use KF5::ActivitiesExperimentalStats of kactivities-5.16.0 deprecated in v5.21.0
https://bugs.kde.org/show_bug.cgi?id=361952 Bhushan Shahchanged: What|Removed |Added CC||bhus...@gmail.com --- Comment #2 from Bhushan Shah --- Sorry, mistook bug. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 361952] kicker v5.6.2 still use KF5::ActivitiesExperimentalStats of kactivities-5.16.0 deprecated in v5.21.0
https://bugs.kde.org/show_bug.cgi?id=361952 Leslie Zhaichanged: What|Removed |Added Summary|kicker v5.6.2 still use |kicker v5.6.2 still use |kactivities-5.16.0 |KF5::ActivitiesExperimental ||Stats of kactivities-5.16.0 ||deprecated in v5.21.0 Resolution|INVALID |--- Status|RESOLVED|UNCONFIRMED -- You are receiving this mail because: You are watching all bug changes.
[ktorrent] [Bug 361951] Torrent list isn't properly migrated from 4.x to 5.x
https://bugs.kde.org/show_bug.cgi?id=361951 --- Comment #1 from Dick Tracey--- And I'm not 100% sure but those looked like from KDE3 days. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 361952] kicker v5.6.2 still use kactivities-5.16.0
https://bugs.kde.org/show_bug.cgi?id=361952 Bhushan Shahchanged: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |INVALID --- Comment #1 from Bhushan Shah --- On Tue, Apr 19, 2016 at 10:21 AM, Leslie Zhai via KDE Bugzilla wrote: > but KF5::ActivitiesExperimentalStats was deprecated in kactivities-5.21.0 > already, so History/Recentusage is empty! New framework : kactivities-stats was released. -- You are receiving this mail because: You are watching all bug changes.
[telepathy] [Bug 337881] Telepathy tries to connect even when network is down
https://bugs.kde.org/show_bug.cgi?id=337881 --- Comment #4 from Guillaume DE BURE--- Just a gentle "up" :) Still present in : * Archlinux * KDE Apps 16.03.90 * Frameworks 5.21.0 * Qt 5.6.0 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 361952] New: kicker v5.6.2 still use kactivities-5.16.0
https://bugs.kde.org/show_bug.cgi?id=361952 Bug ID: 361952 Summary: kicker v5.6.2 still use kactivities-5.16.0 Product: plasmashell Version: 5.6.2 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Application Menu (Kicker) Assignee: h...@kde.org Reporter: xiangzha...@gmail.com CC: plasma-b...@kde.org in plasma-desktop-5.6.2/applets/kicker/CMakeLists.txt target_link_libraries(... KF5::ActivitiesExperimentalStats ) but KF5::ActivitiesExperimentalStats was deprecated in kactivities-5.21.0 already, so History/Recentusage is empty! Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[user-manager] [Bug 361832] System settings; account details; user manager: doesn't display the other users. I'm administrator. Using Kubuntu 15.10.
https://bugs.kde.org/show_bug.cgi?id=361832 Burkhard Lueckchanged: What|Removed |Added CC||lu...@hube-lueck.de --- Comment #1 from Burkhard Lueck --- Works for me using Kubuntu 15.10 -- You are receiving this mail because: You are watching all bug changes.
[ktorrent] [Bug 361951] New: Torrent list isn't properly migrated from 4.x to 5.x
https://bugs.kde.org/show_bug.cgi?id=361951 Bug ID: 361951 Summary: Torrent list isn't properly migrated from 4.x to 5.x Product: ktorrent Version: 5.0 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: grave Priority: NOR Component: general Assignee: joris.guis...@gmail.com Reporter: traceyd...@yandex.com I just upgraded to 5.0.1 from 4.3.1, and almost all of the torrents I was downloading/seeding are gone. Instead, I'm mostly seeing stuff that I already downloaded and removed ages ago. (so lots of File cannot be found. Recreate/Do not download/etc questions). When I tried to remove some of those zombie entries, I either get /blah/blah/ktorrent/config/folder/tor17 couldn't be found, or it silently removes it. When I restart ktorrent, everything comes back, just like a true zombie. I downgraded ktorrent and libktorrent to 4.3.1 and 1.3.1 and my list is there again. Hopefully this bug will be address soon given that people don't want to lose their downloads/uploads. Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[dragonplayer] [Bug 355077] Cursor disappeared in main window after full screen play ends
https://bugs.kde.org/show_bug.cgi?id=355077 Anthonychanged: What|Removed |Added CC||bvb...@abv.bg Resolution|--- |FIXED Status|UNCONFIRMED |RESOLVED --- Comment #1 from Anthony --- https://git.reviewboard.kde.org/r/127095/ -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 356228] DesktopView screen geometry size was strange when kcm_screen rotated 90 degrees then rotated back again
https://bugs.kde.org/show_bug.cgi?id=356228 --- Comment #8 from Leslie Zhai--- (In reply to Pieterjan Camerlynck from comment #7) > https://git.reviewboard.kde.org/r/127656/ Thanks for your great patch, please ship it ;-) -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 361047] Wishlist: make grouped images more prominently visible [patch]
https://bugs.kde.org/show_bug.cgi?id=361047 caulier.gil...@gmail.com changed: What|Removed |Added Version|4.14.0 |5.0.0 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 361047] Wishlist: make grouped images more prominently visible [patch]
https://bugs.kde.org/show_bug.cgi?id=361047 caulier.gil...@gmail.com changed: What|Removed |Added Summary|Wishlist: make grouped |Wishlist: make grouped |images more prominently |images more prominently |visible [MOCKUP]|visible [patch] -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 361950] Should provide a option of vim mode default?
https://bugs.kde.org/show_bug.cgi?id=361950 chourychanged: What|Removed |Added CC||zhouwei...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 361950] New: Should provide a option of vim mode default?
https://bugs.kde.org/show_bug.cgi?id=361950 Bug ID: 361950 Summary: Should provide a option of vim mode default? Product: kdevelop Version: 4.90.91 Platform: Debian unstable OS: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: all editors Assignee: kdevelop-bugs-n...@kde.org Reporter: zhouwei...@gmail.com At this version, I should trigger vim mode every time when I open a new file. Pleas provide a option of vim mode globally or a shortcut key ( such as ESC) to enable it. Juse make it like 4.x. Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 361949] New: Kontact (or Akgregator?) crash
https://bugs.kde.org/show_bug.cgi?id=361949 Bug ID: 361949 Summary: Kontact (or Akgregator?) crash Product: kontact Version: unspecified Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: gijsb...@rondte.nl Application: kontact (5.0.2) Qt Version: 5.5.1 Operating System: Linux 4.2.0-35-generic x86_64 Distribution: Ubuntu 15.10 -- Information about the crash: - What I was doing when the application crashed: Rebooted the computer which I had closed the evening before, without specifically closing Kontact (assuming that this is a possibility of Kubuntu: switching off the computer and then rebooting and restarting right where one had left). -- 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 0x7f9976ebc880 (LWP 1464))] Thread 10 (Thread 0x7f996c347700 (LWP 1558)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f999171efeb in ?? () from /usr/lib/x86_64-linux-gnu/libQt5WebKit.so.5 #2 0x7f999171f029 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5WebKit.so.5 #3 0x7f998cecf6aa in start_thread (arg=0x7f996c347700) at pthread_create.c:333 #4 0x7f9992610e9d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 9 (Thread 0x7f992b891700 (LWP 1562)): #0 0x7f998c291884 in g_mutex_unlock () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7f998c24d1e1 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f998c24d2fc in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f999314a50b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f99930f150a in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f9992f0dac4 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f9992f12a6e in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f998cecf6aa in start_thread (arg=0x7f992b891700) at pthread_create.c:333 #8 0x7f9992610e9d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 8 (Thread 0x7f9929e4d700 (LWP 1569)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f999142d0d4 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5WebKit.so.5 #2 0x7f999174eea1 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5WebKit.so.5 #3 0x7f998cecf6aa in start_thread (arg=0x7f9929e4d700) at pthread_create.c:333 #4 0x7f9992610e9d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 7 (Thread 0x7f992964c700 (LWP 1570)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f999142e103 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5WebKit.so.5 #2 0x7f999174eea1 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5WebKit.so.5 #3 0x7f998cecf6aa in start_thread (arg=0x7f992964c700) at pthread_create.c:333 #4 0x7f9992610e9d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 6 (Thread 0x7f9928e4b700 (LWP 1571)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f999142e103 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5WebKit.so.5 #2 0x7f999174eea1 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5WebKit.so.5 #3 0x7f998cecf6aa in start_thread (arg=0x7f9928e4b700) at pthread_create.c:333 #4 0x7f9992610e9d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 5 (Thread 0x7f991bfff700 (LWP 1572)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f999142e103 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5WebKit.so.5 #2 0x7f999174eea1 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5WebKit.so.5 #3 0x7f998cecf6aa in start_thread (arg=0x7f991bfff700) at pthread_create.c:333 #4 0x7f9992610e9d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 4 (Thread 0x7f991b7fe700 (LWP 1573)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f999142e103 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5WebKit.so.5 #2 0x7f999174eea1 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5WebKit.so.5 #3 0x7f998cecf6aa in start_thread (arg=0x7f991b7fe700) at pthread_create.c:333 #4 0x7f9992610e9d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 3 (Thread 0x7f991affd700 (LWP 1574)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f999142e103 in
[plasmashell] [Bug 361948] New: plasmashell panel krashes on resuming after docking. drkongqi crashes on bug reporting
https://bugs.kde.org/show_bug.cgi?id=361948 Bug ID: 361948 Summary: plasmashell panel krashes on resuming after docking. drkongqi crashes on bug reporting Product: plasmashell Version: master Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Panel Assignee: plasma-b...@kde.org Reporter: bugzi...@in-egypt.net i recently upgraded to plasma 5.5.5.* since then i have noticed that plasmashell will crash and the panel disappears when this scenario happens. while the laptop is suspended, dock the machine. resume. on login, the plasmashell panel will be missing and drkonqi will as to report the bug. when attempting to report the bug drkonqi crashes too. thereby losing the backtrace i do not think this is related to plasmashell maxing out the cpu on resume Reproducible: Always Steps to Reproduce: 1.see above 2. 3. Expected Results: everything works(tm) [marafa@laptop ~] $ xrandr -q Screen 0: minimum 8 x 8, current 2560 x 1024, maximum 32767 x 32767 LVDS1 connected (normal left inverted right x axis y axis) 1366x768 60.10 + 1280x720 60.00 1024x768 60.00 1024x576 60.00 960x540 60.00 800x600 60.3256.25 864x486 60.00 640x480 59.94 720x405 60.00 680x384 60.00 640x360 60.00 DP1 disconnected (normal left inverted right x axis y axis) DP2 disconnected (normal left inverted right x axis y axis) DP3 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) HDMI3 connected primary 1280x1024+0+0 (normal left inverted right x axis y axis) 338mm x 270mm 1280x1024 60.02*+ 75.02 1152x864 75.00 1024x768 75.0870.0760.00 832x624 74.55 800x600 72.1975.0060.32 640x480 75.0072.8160.00 720x400 70.08 VGA1 connected 1280x1024+1280+0 (normal left inverted right x axis y axis) 338mm x 270mm 1280x1024 60.02*+ 75.02 1152x864 75.00 1024x768 75.0870.0760.00 832x624 74.55 800x600 72.1975.0060.32 640x480 75.0072.8160.00 720x400 70.08 [marafa@laptop ~] $ cat ~/bin/monitors.sh #!/bin/sh #laptop monitor IN="LVDS1" #externaml monitors EXT1="VGA1" #when possible always make VGA1 the 1st external; most laptops come with a VGA port EXT2="HDMI3" if (xrandr | grep "$EXT1 disconnected" > /dev/null 2>&1); then xrandr --output $IN --mode 1366x768 --primary --output $EXT1 --off --output $EXT2 --off else xrandr --output $IN --off --output $EXT1 --auto --output $EXT2 --auto --left-of $EXT1 --primary fi i loop on that script via a kde auto start script -- You are receiving this mail because: You are watching all bug changes.
[parley] [Bug 361947] vocabularies don't get promoted when answered correctly
https://bugs.kde.org/show_bug.cgi?id=361947 --- Comment #1 from Juergen--- Here are some of the stuck words: = world el mundo 0 4 7 1 2016-04-18T21:49:21 0 === seat el asiento 0 4 12 1 2016-04-12T04:32:26 0 la silla partner/mate el compañero 0 4 12 1 2016-04-18T17:04:49 0 acompañante === finger, toe el dedo 0 3 11 1 2016-04-15T19:17:17 0 la uña -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356225] Panel moves to wrong screen when external monitor is connected
https://bugs.kde.org/show_bug.cgi?id=356225 Mohammed Arafachanged: What|Removed |Added CC||bugzi...@in-egypt.net -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356394] Crash at some point while monitor power cycled
https://bugs.kde.org/show_bug.cgi?id=356394 Mohammed Arafachanged: What|Removed |Added CC||bugzi...@in-egypt.net -- You are receiving this mail because: You are watching all bug changes.
[parley] [Bug 361947] New: vocabularies don't get promoted when answered correctly
https://bugs.kde.org/show_bug.cgi?id=361947 Bug ID: 361947 Summary: vocabularies don't get promoted when answered correctly Product: parley Version: 1.1.0 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Severity: major Priority: NOR Component: general Assignee: parley-bugs-n...@kde.org Reporter: b4tas...@auroville.org.in Parley 1.1.1 , KDE 4.14.13 ubuntu 14.04 64 bit A number of vocabularies don't get promoted when answered correctly. They are stuck on level 2. Reproducible: Always Steps to Reproduce: 1. go to practise mode 2. answer correctly. first time the words get promoted from level 1 to 2, then get stuck forever on level 2 Expected Results: All words should be promoted. In my vocabulary file presently it is about 20 words out of 1000 -- You are receiving this mail because: You are watching all bug changes.
[amarok] [Bug 361910] Amarok doesn't play when VLC is running after a video on Phonon-VLC
https://bugs.kde.org/show_bug.cgi?id=361910 --- Comment #3 from Myriam Schweingruber--- I strongly suggest you check with your distribution, as we do not provide packaging for neither Qt, nor VLC, nor Phonon or its backends. Since Amarok doesn't use VLC, but the phonon backend which in turn is compiled with libvlc, an independent library, playing something in VLC has zero influence over how Amarok plays something, Those packages are totally independent of each other (VLC doesn't use Phonon for playback for instance). -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 361619] Input event lag/drop-out when OpenGL is ON with large window
https://bugs.kde.org/show_bug.cgi?id=361619 --- Comment #31 from Tyson Tan--- But I'm using Ubuntu 15.10, it has Qt 5.4.2 with it. Both AppImage and my local build had this problem, while Windows version seems to work fine. I'm not very sure about the speculation in Comment 30. -- You are receiving this mail because: You are watching all bug changes.
[KAccounts] [Bug 354565] account setup sometimes fails, race condition?
https://bugs.kde.org/show_bug.cgi?id=354565 Rex Dieterchanged: What|Removed |Added Resolution|--- |WORKSFORME Status|UNCONFIRMED |RESOLVED --- Comment #1 from Rex Dieter --- I haven't experienced this in awhile especially after upgrading to 15.12.3, and re-setting things up multiple times. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 361047] Wishlist: make grouped images more prominently visible [MOCKUP]
https://bugs.kde.org/show_bug.cgi?id=361047 --- Comment #10 from Omar Amin--- Created attachment 98456 --> https://bugs.kde.org/attachment.cgi?id=98456=edit Screenshot of the new grouped images border -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 361047] Wishlist: make grouped images more prominently visible [MOCKUP]
https://bugs.kde.org/show_bug.cgi?id=361047 --- Comment #9 from Omar Amin--- Created attachment 98455 --> https://bugs.kde.org/attachment.cgi?id=98455=edit Group border modification patch This patch is for grouped images border new background -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 361946] New: Dolphin may crash when file in opened folder get modified
https://bugs.kde.org/show_bug.cgi?id=361946 Bug ID: 361946 Summary: Dolphin may crash when file in opened folder get modified Product: dolphin Version: unspecified Platform: Chakra OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: wen...@gmail.com Application: dolphin (16.04.0) Qt Version: 5.6.0 Frameworks Version: 5.21.0 Operating System: Linux 4.3.3-1-surfacepro3 x86_64 Distribution (Platform): Chakra -- Information about the crash: - What I was doing when the application crashed: I was editing a po file in lokalize (Though I don't think which application matters), just at the time I hit save button, dolphin crashed while dolphin was displaying the folder containing the saved file. The crash can be reproduced sometimes. -- Backtrace: Application: Dolphin (dolphin), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7f8498b09800 (LWP 5827))] Thread 5 (Thread 0x7f8482afe700 (LWP 5830)): #0 0x7f849852e18d in poll () from /usr/lib/libc.so.6 #1 0x7f848ca9cae2 in ?? () from /usr/lib/libxcb.so.1 #2 0x7f848ca9e757 in xcb_wait_for_event () from /usr/lib/libxcb.so.1 #3 0x7f8484625329 in QXcbEventReader::run (this=0x176de90) at qxcbconnection.cpp:1313 #4 0x7f8493004238 in QThreadPrivate::start (arg=0x176de90) at thread/qthread_unix.cpp:340 #5 0x7f848f50f464 in start_thread () from /usr/lib/libpthread.so.0 #6 0x7f849853712d in clone () from /usr/lib/libc.so.6 Thread 4 (Thread 0x7f8481861700 (LWP 5831)): #0 0x7f848d3e9a23 in g_main_context_query () from /usr/lib/libglib-2.0.so.0 #1 0x7f848d3ea157 in ?? () from /usr/lib/libglib-2.0.so.0 #2 0x7f848d3ea322 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #3 0x7f849322d1fb in QEventDispatcherGlib::processEvents (this=0x7f84740008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:419 #4 0x7f84931d5c2a in QEventLoop::exec (this=this@entry=0x7f8481860d90, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #5 0x7f8492fff434 in QThread::exec (this=this@entry=0x7f8498c5ed80 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at thread/qthread.cpp:503 #6 0x7f8498be7859 in QDBusConnectionManager::run (this=0x7f8498c5ed80 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at qdbusconnection.cpp:181 #7 0x7f8493004238 in QThreadPrivate::start (arg=0x7f8498c5ed80 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at thread/qthread_unix.cpp:340 #8 0x7f848f50f464 in start_thread () from /usr/lib/libpthread.so.0 #9 0x7f849853712d in clone () from /usr/lib/libc.so.6 Thread 3 (Thread 0x7f84788db700 (LWP 5832)): #0 0x7f848f51503f in pthread_cond_wait@@GLIBC_2.3.2 () from /usr/lib/libpthread.so.0 #1 0x7f8478a631b4 in ?? () from /usr/lib/libQt5Script.so.5 #2 0x7f8478a631f9 in ?? () from /usr/lib/libQt5Script.so.5 #3 0x7f848f50f464 in start_thread () from /usr/lib/libpthread.so.0 #4 0x7f849853712d in clone () from /usr/lib/libc.so.6 Thread 2 (Thread 0x7f83f3bef700 (LWP 5833)): #0 0x7f849852e18d in poll () from /usr/lib/libc.so.6 #1 0x7f848d3ea1e5 in ?? () from /usr/lib/libglib-2.0.so.0 #2 0x7f848d3ea322 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #3 0x7f849322d1fb in QEventDispatcherGlib::processEvents (this=0x7f83ec0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:419 #4 0x7f84931d5c2a in QEventLoop::exec (this=this@entry=0x7f83f3beedc0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #5 0x7f8492fff434 in QThread::exec (this=) at thread/qthread.cpp:503 #6 0x7f8493004238 in QThreadPrivate::start (arg=0x1dcf680) at thread/qthread_unix.cpp:340 #7 0x7f848f50f464 in start_thread () from /usr/lib/libpthread.so.0 #8 0x7f849853712d in clone () from /usr/lib/libc.so.6 Thread 1 (Thread 0x7f8498b09800 (LWP 5827)): [KCrash Handler] #6 QList::operator+= (this=this@entry=0x7ffec9a5bf50, l=...) at /usr/include/qt5/QtCore/qlist.h:931 #7 0x7f8498196d79 in QList::append (t=..., this=0x7ffec9a5bf50) at /usr/include/qt5/QtCore/qlist.h:954 #8 KFileItemModelRolesUpdater::rolesData (this=this@entry=0x1dc4110, item=...) at /chakra/desktop/dolphin/src/dolphin-16.04.0/src/kitemviews/kfileitemmodelrolesupdater.cpp:1091 #9 0x7f849819ab32 in KFileItemModelRolesUpdater::applyResolvedRoles (this=this@entry=0x1dc4110, index=index@entry=2, hint=hint@entry=KFileItemModelRolesUpdater::ResolveAll) at /chakra/desktop/dolphin/src/dolphin-16.04.0/src/kitemviews/kfileitemmodelrolesupdater.cpp:1047 #10 0x7f849819c791 in KFileItemModelRolesUpdater::resolveNextPendingRoles (this=0x1dc4110) at
[i18n] [Bug 361795] ki18n5.js installed by both ki18n and kde-l10n
https://bugs.kde.org/show_bug.cgi?id=361795 Albert Astals Cidchanged: What|Removed |Added CC||caslav.i...@gmx.net --- Comment #1 from Albert Astals Cid --- Chusslove, i remember us discussing/fixing this at some point or is it a dream? -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 331864] Merge Tags with same name when moving to same hierarchy level
https://bugs.kde.org/show_bug.cgi?id=331864 Dan O.changed: What|Removed |Added CC||belbo...@gmail.com --- Comment #1 from Dan O. --- While assigning the duplicate tag to all images currently tagged with a duplicate tag and then deleting the duplicate is a viable solution for regular tags, it is not an effective work-around for face tags. If you assign all the images with a face tag of an individual to another, it simply adds a standard tag, it does not alter the face tag as each face tag is only given one name. Having duplicate face tags effectively means you must remove one entire selection of face tags, and re-run the face tagging operation, effectively repeating all of the work involved in face tagging. While I can change an individual face tag, I cannot do so for an entire selection. Changing 100+ face tags individually isn't a practical solution. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 361945] "More Settings" Panel Menu doesn't indicate selection...
https://bugs.kde.org/show_bug.cgi?id=361945 PGillespiechanged: What|Removed |Added Summary|Visibility Customizations |"More Settings" Panel Menu |no longer selectable... |doesn't indicate ||selection... -- You are receiving this mail because: You are watching all bug changes.
[rsibreak] [Bug 361853] rsibreak does not start automatically after install
https://bugs.kde.org/show_bug.cgi?id=361853 Albert Astals Cidchanged: What|Removed |Added Status|UNCONFIRMED |NEEDSINFO Resolution|--- |WAITINGFORINFO --- Comment #1 from Albert Astals Cid --- what is the value of AutoStart in your .config/rsibreakrc file? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 361945] New: Visibility Customizations no longer selectable...
https://bugs.kde.org/show_bug.cgi?id=361945 Bug ID: 361945 Summary: Visibility Customizations no longer selectable... Product: plasmashell Version: 5.5.5 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Panel Assignee: plasma-b...@kde.org Reporter: vtp...@myfairpoint.net After the last update to 16.04 (April 15th 2016), Mouse Over does not highlight any of the options under Panel Alignment or Visibility. In some cases, this makes confirmation that one has actually selected the item difficult to ascertain. This may or may not be related to: https://bugs.kde.org/show_bug.cgi?id=348043 Which also affects this system. Kernel: 4.4.0-18-generic x86_64 (64 bit) Desktop: KDE Plasma 5.5.5 Distro: Ubuntu 16.04 xenial Machine: System: LENOVO (portable) product: 20428 v: Lenovo Yoga 2 11 Reproducible: Always Steps to Reproduce: 1. Select More Settings under Panel Options. 2. Select any option under Panel Alignment or Visibility. Actual Results: Nothing. Expected Results: The selected option is highlighted with a mouse click (or some indication confirming the mouse click). -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 361726] WARNING:unhandled syscall on ppc64
https://bugs.kde.org/show_bug.cgi?id=361726 Josef Weidendorferchanged: What|Removed |Added Component|callgrind |general Assignee|josef.weidendor...@gmx.de |jsew...@acm.org --- Comment #1 from Josef Weidendorfer --- This bug report seems to be about a problem in the debug info reader and missing syscall handlers, and not about callgrind. Therefore, reassigning to "General". However, 3.9.0 is quite old. You should test with newest release (3.11) or better the current SVN version. -- You are receiving this mail because: You are watching all bug changes.
[clazy] [Bug 361691] Suggestion to turn string into QStringLiteral instead of QLatin1String
https://bugs.kde.org/show_bug.cgi?id=361691 --- Comment #12 from Stephen Kelly--- Your benchmark is only for the case of the searched string being empty. In other benchmarks here, the two perform the same. That isn't a good reason for clazy to recommend something that 1) goes against the general recommendation, 2) we don't have strong benchmarks in favor of. After https://codereview.qt-project.org/156181 I get results for your benchmark which are the same within experimental error. Please apply it and confirm. If you think clazy should continue to recommend non-use of QLatin1String for these methods, please provide a better benchmark than either of the ones we've posted so far. -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 361938] Kontact crashes on changing languages in identities
https://bugs.kde.org/show_bug.cgi?id=361938 koffeinfried...@gmail.com changed: What|Removed |Added Product|korgac |kontact Component|general |general -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 361938] Kontact crashes on changing languages in identities in kmail
https://bugs.kde.org/show_bug.cgi?id=361938 koffeinfried...@gmail.com changed: What|Removed |Added Summary|Kontact crashes on changing |Kontact crashes on changing |languages in identities |languages in identities in ||kmail Component|general |general Product|kontact |kmail2 -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 361941] Build fails with cppparsejob.cpp:847:47: error: ‘document’ was not declared in this scope
https://bugs.kde.org/show_bug.cgi?id=361941 --- Comment #5 from andreas.sturmlech...@gmail.com --- Built fine after the fix! Thank you. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 361941] Build fails with cppparsejob.cpp:847:47: error: ‘document’ was not declared in this scope
https://bugs.kde.org/show_bug.cgi?id=361941 Kevin Funkchanged: What|Removed |Added Version Fixed In||5.0 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 361940] In focus follows mouse mode, the window under the pointer sometimes does not have focus
https://bugs.kde.org/show_bug.cgi?id=361940 --- Comment #5 from k...@happyjack.org --- Created attachment 98454 --> https://bugs.kde.org/attachment.cgi?id=98454=edit xprop and xwininfo output These are not from the layout in the prior attachment (I'd closed all those windows), but I did verify that the loss of focus was happening with the Firefox instance I used to get the output here. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 361378] Tags are not being removed from files metadata
https://bugs.kde.org/show_bug.cgi?id=361378 --- Comment #6 from wildcowboy--- (In reply to Maik Qualmann from comment #5) > The problem also not to reproduce here with digiKam-4.14. Only certain tags > (Color label, Pick label...)? Do you use sidecar files for metadata? > > Maik Hello, I do not use color labels / pick labels nor sidecar files. I use regular tags and star ratings only and write it to files' metadata. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 355837] Icons-only task manager: Layout broken if required space exceeds available space
https://bugs.kde.org/show_bug.cgi?id=355837 --- Comment #7 from Eike Hein--- I still can't reproduce this problem at all, and I don't want to apply patches blindly. Could you try to nail down the steps to reproduce a bit more specifically? Maybe post relevant Plasma config bits re panel size and applet config, and exact number of launchers and icons. It may well be that your patch solves it and I'll gladly take it, but I'd rather see the problem first. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 361941] Build fails with cppparsejob.cpp:847:47: error: ‘document’ was not declared in this scope
https://bugs.kde.org/show_bug.cgi?id=361941 Kevin Funkchanged: What|Removed |Added Latest Commit||http://commits.kde.org/kdev ||elop/24d995d3d893ee4182f90a ||904c3312420cf6e431 Resolution|WAITINGFORINFO |FIXED --- Comment #4 from Kevin Funk --- Git commit 24d995d3d893ee4182f90a904c3312420cf6e431 by Kevin Funk. Committed on 18/04/2016 at 21:10. Pushed by kfunk into branch '5.0'. oldcpp: Make compile M +5-4languages/cpp/codecompletion/model.h M +1-1languages/cpp/cppparsejob.cpp M +1-1languages/cpp/tests/cppjsontests.h http://commits.kde.org/kdevelop/24d995d3d893ee4182f90a904c3312420cf6e431 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 361940] In focus follows mouse mode, the window under the pointer sometimes does not have focus
https://bugs.kde.org/show_bug.cgi?id=361940 --- Comment #4 from Thomas Lübking--- no problem, can you please dump xprop and xwininfo -all on the firefox window? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 361940] In focus follows mouse mode, the window under the pointer sometimes does not have focus
https://bugs.kde.org/show_bug.cgi?id=361940 --- Comment #3 from k...@happyjack.org --- It's neither active nor has focus: the titlebar is active for Firefox (which is still below the terminal), and keyboard input goes to Firefox. Excellent point on Firefox: I think I just assumed it was a kwin issue separate from the underlying programs, but it does appear to be related to Firefox/Mozilla. I tested a variety of different programs with various toolkits (Qt5, Qt4, Qt3, Motif, gtk2) and was only able to reproduce it with Firefox and Thunderbird (but not Seamonkey). Apologies for not being thorough enough in initial testing; I should have caught that. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 361941] Build fails with cppparsejob.cpp:847:47: error: ‘document’ was not declared in this scope
https://bugs.kde.org/show_bug.cgi?id=361941 --- Comment #3 from andreas.sturmlech...@gmail.com --- Yes, I had built kdevplatform branch 5.0 right before that. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 290787] KMail shown "Unknown" date when Date field exist
https://bugs.kde.org/show_bug.cgi?id=290787 --- Comment #16 from Mike Goodwin--- Sorry, I always forget that there's no edit here like github. I wanted to include: Fedora 23: # rpm -qa | grep "kmail\|akonadi" kmail-libs-4.14.10-10.fc23.x86_64 baloo-akonadi-4.14.3-5.fc23.x86_64 akonadi-mysql-1.13.0-20.fc23.x86_64 akonadi-1.13.0-20.fc23.x86_64 kdepimlibs-akonadi-4.14.10-8.fc23.x86_64 kmail-4.14.10-10.fc23.x86_64 -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 290787] KMail shown "Unknown" date when Date field exist
https://bugs.kde.org/show_bug.cgi?id=290787 Mike Goodwinchanged: What|Removed |Added CC||m...@mgoodwin.net --- Comment #15 from Mike Goodwin --- Absolutely, I specifically noticed this when sorting my email by "Date/Time of Most Recent in Subtree" because i've been dealing with mailing lists lately. Once I did that all the "Unknowns" came right to the top where I didn't want them to be. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 361944] New: Plasma crashes constantly after login
https://bugs.kde.org/show_bug.cgi?id=361944 Bug ID: 361944 Summary: Plasma crashes constantly after login Product: plasmashell Version: 5.6.2 Platform: Gentoo Packages OS: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: dieselmach...@mail.ru CC: bhus...@gmail.com, plasma-b...@kde.org Just after I logged in and splash screen disappears plasma crashes immediately. I just see black screen and a mouse cursor. Plasma tries to restart but crashes again and again in endless loop Application: plasmashell (5.6.2) Qt Version: 5.5.1 Frameworks Version: 5.21.0 Operating System: Linux 4.1.15-gentoo-r1 x86_64 Distribution (Platform): Gentoo Packages The crash can be reproduced every time. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f1da3795740 (LWP 3359))] Thread 6 (Thread 0x7f1d9210d700 (LWP 3360)): #0 0x7f1d9e03f23d in poll () from /lib64/libc.so.6 #1 0x7f1da1f4ca9a in ?? () from /usr/lib64/libxcb.so.1 #2 0x7f1da1f4e7b7 in xcb_wait_for_event () from /usr/lib64/libxcb.so.1 #3 0x7f1d9488b9e9 in ?? () from /usr/lib64/libQt5XcbQpa.so.5 #4 0x7f1d9e6a69b3 in ?? () from /usr/lib64/libQt5Core.so.5 #5 0x7f1d9d84b456 in start_thread () from /lib64/libpthread.so.0 #6 0x7f1d9e04834d in clone () from /lib64/libc.so.6 Thread 5 (Thread 0x7f1d8b3ea700 (LWP 3365)): #0 0x7f1d9a109dbb in ?? () from /usr/lib64/libglib-2.0.so.0 #1 0x7f1d9a10c28b in g_main_context_prepare () from /usr/lib64/libglib-2.0.so.0 #2 0x7f1d9a10cb90 in ?? () from /usr/lib64/libglib-2.0.so.0 #3 0x7f1d9a10cd84 in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #4 0x7f1d9e890e63 in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib64/libQt5Core.so.5 #5 0x7f1d9e845d5b in QEventLoop::exec(QFlags) () from /usr/lib64/libQt5Core.so.5 #6 0x7f1d9e6a20ca in QThread::exec() () from /usr/lib64/libQt5Core.so.5 #7 0x7f1da0e18840 in ?? () from /usr/lib64/libQt5Qml.so.5 #8 0x7f1d9e6a69b3 in ?? () from /usr/lib64/libQt5Core.so.5 #9 0x7f1d9d84b456 in start_thread () from /lib64/libpthread.so.0 #10 0x7f1d9e04834d in clone () from /lib64/libc.so.6 Thread 4 (Thread 0x7f1d802fc700 (LWP 3366)): #0 0x7f1d9a109e37 in ?? () from /usr/lib64/libglib-2.0.so.0 #1 0x7f1d9a10c28b in g_main_context_prepare () from /usr/lib64/libglib-2.0.so.0 #2 0x7f1d9a10cb90 in ?? () from /usr/lib64/libglib-2.0.so.0 #3 0x7f1d9a10cd84 in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #4 0x7f1d9e890e63 in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib64/libQt5Core.so.5 #5 0x7f1d9e845d5b in QEventLoop::exec(QFlags) () from /usr/lib64/libQt5Core.so.5 #6 0x7f1d9e6a20ca in QThread::exec() () from /usr/lib64/libQt5Core.so.5 #7 0x7f1da0e18840 in ?? () from /usr/lib64/libQt5Qml.so.5 #8 0x7f1d9e6a69b3 in ?? () from /usr/lib64/libQt5Core.so.5 #9 0x7f1d9d84b456 in start_thread () from /lib64/libpthread.so.0 #10 0x7f1d9e04834d in clone () from /lib64/libc.so.6 Thread 3 (Thread 0x7f1d7e374700 (LWP 3367)): #0 0x7f1d9a10c232 in g_main_context_prepare () from /usr/lib64/libglib-2.0.so.0 #1 0x7f1d9a10cb90 in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x7f1d9a10cd84 in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #3 0x7f1d9e890e63 in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib64/libQt5Core.so.5 #4 0x7f1d9e845d5b in QEventLoop::exec(QFlags) () from /usr/lib64/libQt5Core.so.5 #5 0x7f1d9e6a20ca in QThread::exec() () from /usr/lib64/libQt5Core.so.5 #6 0x7f1da0e18840 in ?? () from /usr/lib64/libQt5Qml.so.5 #7 0x7f1d9e6a69b3 in ?? () from /usr/lib64/libQt5Core.so.5 #8 0x7f1d9d84b456 in start_thread () from /lib64/libpthread.so.0 #9 0x7f1d9e04834d in clone () from /lib64/libc.so.6 Thread 2 (Thread 0x7f1d7ca10700 (LWP 3368)): #0 0x7f1d9d850fcf in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f1da31d8e5b in ?? () from /usr/lib64/libQt5Script.so.5 #2 0x7f1da31d8e89 in ?? () from /usr/lib64/libQt5Script.so.5 #3 0x7f1d9d84b456 in start_thread () from /lib64/libpthread.so.0 #4 0x7f1d9e04834d in clone () from /lib64/libc.so.6 Thread 1 (Thread 0x7f1da3795740 (LWP 3359)): [KCrash Handler] #6 0x7f1d9e8710b1 in QObjectPrivate::addConnection(int, QObjectPrivate::Connection*) () from /usr/lib64/libQt5Core.so.5 #7 0x7f1d9e873503 in QObjectPrivate::connectImpl(QObject const*, int, QObject const*, void**, QtPrivate::QSlotObjectBase*, Qt::ConnectionType, int const*, QMetaObject const*) () from /usr/lib64/libQt5Core.so.5 #8 0x7f1d9e8738b4 in QObject::connectImpl(QObject
[krita] [Bug 361698] [MONOPRICE] Brush Tip Misalignment in the Preview Window when using Monoprice Tablet
https://bugs.kde.org/show_bug.cgi?id=361698 --- Comment #1 from Sam Keeper--- Created attachment 98453 --> https://bugs.kde.org/attachment.cgi?id=98453=edit Brush tip misalignment in canvas Update on this bug: I've discovered that apparently there's something odd going on with the alignment in the main canvas itself, as seen here. The eyedropper tool is detecting the color several pixels down and to the right of where it is actually located on the screen. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 361943] New: systemsettings - Workspace Theme - Desktop Theme - Get New Themes > Loading ... failed
https://bugs.kde.org/show_bug.cgi?id=361943 Bug ID: 361943 Summary: systemsettings - Workspace Theme - Desktop Theme - Get New Themes > Loading ... failed Product: systemsettings Version: 5.6.2 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: ja...@nurealm.net Arch systemsettings 5.6.2-1 Workspace Theme - Desktop Theme - Get New Theme - Get Hot New Stuff/System Setttings Add-On Installer first gives: Loading provider information then gives the error: Loading of providers from file: http://download.kde.org/ocs/providers.xml failed even though entering that URL into a browser does return a file: opendesktop https://api.opendesktop.org/v1/ openDesktop.org https://opendesktop.org/terms/ https://opendesktop.org/usermanager/new.php I don't know that I've ever seen "Get New Themes" actually work in kde though. Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 361941] Build fails with cppparsejob.cpp:847:47: error: ‘document’ was not declared in this scope
https://bugs.kde.org/show_bug.cgi?id=361941 Kevin Funkchanged: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|UNCONFIRMED |RESOLVED --- Comment #2 from Kevin Funk --- Are you using kdevplatform 5.0 branch, too? You have to. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 361940] In focus follows mouse mode, the window under the pointer sometimes does not have focus
https://bugs.kde.org/show_bug.cgi?id=361940 --- Comment #2 from Thomas Lübking--- "Doesn't get focus" or "doesn't turn active" ? (does the titlebar look reflect the focus condition) And is firefox (? The browser, is it not?) a relevant part or does this also work with eg. kwrite? -- You are receiving this mail because: You are watching all bug changes.
[trojita] [Bug 361942] New: make source code git with debian Wheezy
https://bugs.kde.org/show_bug.cgi?id=361942 Bug ID: 361942 Summary: make source code git with debian Wheezy Product: trojita Version: git Platform: Debian stable OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Core Assignee: trojita-b...@kde.org Reporter: jonatanfie...@gmail.com Linking CXX executable test_Composer_responses [ 82%] Building CXX object CMakeFiles/DesktopGui.dir/src/Gui/TagListWidget.cpp.o [ 83%] Building CXX object CMakeFiles/DesktopGui.dir/src/Gui/TagWidget.cpp.o [ 83%] Built target test_Composer_responses Scanning dependencies of target test_Cryptography_MessageModel [ 83%] Building CXX object CMakeFiles/test_Cryptography_MessageModel.dir/tests/Cryptography/test_Cryptography_MessageModel.cpp.o [ 83%] Building CXX object CMakeFiles/DesktopGui.dir/src/Gui/TaskProgressIndicator.cpp.o [ 83%] Building CXX object CMakeFiles/DesktopGui.dir/src/Gui/UserAgentWebPage.cpp.o [ 84%] Building CXX object CMakeFiles/DesktopGui.dir/src/Gui/Util.cpp.o [ 84%] Building CXX object CMakeFiles/DesktopGui.dir/src/Gui/Window.cpp.o [ 84%] Building CXX object CMakeFiles/DesktopGui.dir/src/Gui/ShortcutHandler/ShortcutConfigDialog.cpp.o [ 85%] Building CXX object CMakeFiles/DesktopGui.dir/src/Gui/ShortcutHandler/ShortcutConfigWidget.cpp.o [ 85%] Building CXX object CMakeFiles/test_Cryptography_MessageModel.dir/test_Cryptography_MessageModel_automoc.cpp.o [ 85%] Building CXX object CMakeFiles/DesktopGui.dir/src/Gui/ShortcutHandler/ShortcutHandler.cpp.o /root/dev/trojita/src/Gui/Window.cpp: In lambda function: /root/dev/trojita/src/Gui/Window.cpp:743:68: error: ‘this’ was not captured for this lambda function make[2]: *** [CMakeFiles/DesktopGui.dir/src/Gui/Window.cpp.o] Error 1 make[2]: *** Se espera a que terminen otras tareas Scanning dependencies of target test_Formatting [ 85%] Building CXX object CMakeFiles/test_Formatting.dir/tests/Misc/test_Formatting.cpp.o [ 85%] Building CXX object CMakeFiles/test_Formatting.dir/test_Formatting_automoc.cpp.o Linking CXX executable test_Cryptography_MessageModel Scanning dependencies of target test_Html_formatting [ 85%] Building CXX object CMakeFiles/test_Html_formatting.dir/tests/Composer/test_Html_formatting.cpp.o Linking CXX executable test_Formatting [ 85%] Built target test_Formatting Scanning dependencies of target test_Imap_BodyParts [ 86%] make[1]: *** [CMakeFiles/DesktopGui.dir/all] Error 2 make[1]: *** Se espera a que terminen otras tareas [ 86%] Building CXX object CMakeFiles/test_Imap_BodyParts.dir/tests/Imap/test_Imap_BodyParts.cpp.o Building CXX object CMakeFiles/test_Html_formatting.dir/test_Html_formatting_automoc.cpp.o [ 86%] Built target test_Cryptography_MessageModel [ 86%] Building CXX object CMakeFiles/test_Imap_BodyParts.dir/test_Imap_BodyParts_automoc.cpp.o Linking CXX executable test_Html_formatting [ 86%] Built target test_Html_formatting Linking CXX executable test_Imap_BodyParts [ 86%] Built target test_Imap_BodyParts make: *** [all] Error 2 root@debian-term:~/dev/trojita/_build# uname -a Linux debian-term 3.16.0-0.bpo.4-686-pae #1 SMP Debian 3.16.7-ckt9-3~deb8u1~bpo70+1 (2015-04-27) i686 GNU/Linux root@debian-term:~/dev/trojita/_build# cmake --version cmake version 2.8.11. root@debian-term:~# qmake -qt=qt5 -v QMake version 3.0 Using Qt version 5.3.2 in /usr/lib/i386-linux-gnu -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 361917] KRunner window blocks Kate session selection window
https://bugs.kde.org/show_bug.cgi?id=361917 Kai Uwe Broulikchanged: What|Removed |Added Status|UNCONFIRMED |CONFIRMED Component|sessions|general Ever confirmed|0 |1 Assignee|kwrite-bugs-n...@kde.org|fa...@kde.org Product|kate|frameworks-kio CC||k...@privat.broulik.de, ||kdelibs-b...@kde.org --- Comment #3 from Kai Uwe Broulik --- The services runner just does KRun::runService which seems to block if the application doesn't return. Re-assigning to KIO. Suggestions? It looks like KRun ends up calling KToolInvocation::startServiceByDesktopPath which is deprecated but has a nowait parameter which I cannot use from KRun. Irregardless of the behavior in the bug it's quite annoying that KRunner often blocks while the application is starting because of this behavior. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 361916] Maximizing app crashes KDE
https://bugs.kde.org/show_bug.cgi?id=361916 kaalichanged: What|Removed |Added CC||exc...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 361941] Build fails with cppparsejob.cpp:847:47: error: ‘document’ was not declared in this scope
https://bugs.kde.org/show_bug.cgi?id=361941 --- Comment #1 from andreas.sturmlech...@gmail.com --- Created attachment 98452 --> https://bugs.kde.org/attachment.cgi?id=98452=edit build.log -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 361941] New: Build fails with cppparsejob.cpp:847:47: error: ‘document’ was not declared in this scope
https://bugs.kde.org/show_bug.cgi?id=361941 Bug ID: 361941 Summary: Build fails with cppparsejob.cpp:847:47: error: ‘document’ was not declared in this scope Product: kdevelop Version: 4.90.91 Platform: Gentoo Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Language Support: CPP Assignee: kdevelop-bugs-n...@kde.org Reporter: andreas.sturmlech...@gmail.com I can not successfully build kdevelop 5.0 branch right now - build.log attached. The line was introduced with commit 2947a8b43895db23bc8406a0acfc9b2a2fc6d9eb Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[kde-gtk-config] [Bug 314738] System setting crashed when clicking on Gtk Configuration
https://bugs.kde.org/show_bug.cgi?id=314738 kaalichanged: What|Removed |Added CC||exc...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 361909] add extra options to ctags command for project plugin
https://bugs.kde.org/show_bug.cgi?id=361909 --- Comment #2 from Dominik Haumann--- Hi Roberto, could you please submit your patch at http://git.reviewboard.kde.org? Also, I would like to change the json to: { "name": "Bash Project" , "files": [{"directory": ".", "filters": ["*.sh", "*.profile", "*.func", "*.awk", "*.cfg"], "recursive": 1}] , "ctags": { options": [ "--langdef=Cfg" , "--langmap=Cfg:.cfg\(*.profile\)" , "--regex-Cfg=/^[[:space:]]*((declare|local)[[:space:]]+(-[a-z]+[[:space:]]+))?([[:alpha:]][[:alnum:]]+(\\[[[:alnum:]]+])?)=/\\4/v,variables/" , "--exclude=*.awk" ] } } This allows us to easily extend the ctags section for future releases. -- You are receiving this mail because: You are watching all bug changes.
[clazy] [Bug 361691] Suggestion to turn string into QStringLiteral instead of QLatin1String
https://bugs.kde.org/show_bug.cgi?id=361691 --- Comment #11 from Sergio Martins--- That's cheating, that benchmark doesn't compare QLatin1String vs QStringLiteral, well, maybe it does, for 0.1 % of the code, the remaining 99.9% it's running the common implementation between both contains() overloads. For me, both runs give me the same time, can you reproduce that consistently ? I don't think it's bad to optimize the small string case if it doesn't make the big string worse. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 334210] PDF: In-line annotation font face is always the same
https://bugs.kde.org/show_bug.cgi?id=334210 --- Comment #5 from V字龍(Vdragon)--- OK I found the Poppler bug report, just for anyone's convenience. Bug 65956 – okular does not show non-latin characters in inline notes https://bugs.freedesktop.org/show_bug.cgi?id=65956 -- You are receiving this mail because: You are watching all bug changes.
[kdebugsettings] [Bug 361688] kscreen.xcb.help fill log at insane rate
https://bugs.kde.org/show_bug.cgi?id=361688 Sebastian Küglerchanged: What|Removed |Added Latest Commit||http://commits.kde.org/kdeb ||ugsettings/8d274b043c252ffc ||69f86caee752f30d31f7f05e Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #7 from Sebastian Kügler --- Git commit 8d274b043c252ffc69f86caee752f30d31f7f05e by Sebastian Kügler. Committed on 18/04/2016 at 19:47. Pushed by sebas into branch 'Applications/16.04'. Fix category of xcb helper for libkscreen M +1-1data/kde.categories http://commits.kde.org/kdebugsettings/8d274b043c252ffc69f86caee752f30d31f7f05e -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 361917] KRunner window blocks Kate session selection window
https://bugs.kde.org/show_bug.cgi?id=361917 --- Comment #2 from Dominik Haumann--- Can reproduce, quite annoying. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 361940] In focus follows mouse mode, the window under the pointer sometimes does not have focus
https://bugs.kde.org/show_bug.cgi?id=361940 --- Comment #1 from k...@happyjack.org --- Created attachment 98451 --> https://bugs.kde.org/attachment.cgi?id=98451=edit Window layout which can trigger the behavior -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 361940] New: In focus follows mouse mode, the window under the pointer sometimes does not have focus
https://bugs.kde.org/show_bug.cgi?id=361940 Bug ID: 361940 Summary: In focus follows mouse mode, the window under the pointer sometimes does not have focus Product: kwin Version: 5.6.2 Platform: Compiled Sources OS: Linux Status: UNCONFIRMED Severity: minor Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: k...@happyjack.org Possibly-relevant kwin settings: * Focus Follows Mouse - Mouse Precedence * 0ms delay * No focus stealing prevention * Raise on hover delayed 500ms * Active screen follows mouse In some cases, the window under the pointer doesn't get focus; this seems to be the result of quickly switching between a few windows. I'll attach a screenshot of the window layout I'm using to reproduce the behavior described. Reproducible: Sometimes Steps to Reproduce: 1. Place the pointer in the small terminal window on the right 2. Quickly (as fast as you can, basically) move the pointer horizontally from the small window across the large browser window into the mid-sized terminal window above it Actual Results: Perhaps 20% of the time the large window gains and retains focus, even when the mouse moves into the mid-sized window. Expected Results: The mid-size window always has the focus once the pointer is inside of it. I don't recall this behavior in version 5.5; I've only seen it in 5.6. -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 360777] Due to faulty configuration desktop loading time is ~20 seconds longer
https://bugs.kde.org/show_bug.cgi?id=360777 Luis Gustavo S. Barretochanged: What|Removed |Added CC||gustavosbarr...@gmail.com --- Comment #7 from Luis Gustavo S. Barreto --- Can you paste the output of the following command? cat .xsession-errors | grep "startup completed" I think this bug is related to this change in plasma-framework: commit 309c64f5e90453c5253baf19e6c01759e8aa6f83 Author: Aleix Pol Date: Wed Mar 16 12:33:10 2016 +0100 Don't import an nonexistent layout It should have a containment at least REVIEW: 127345 https://git.reviewboard.kde.org/r/127345/ -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 361926] unhandled x86-solaris syscall: 84
https://bugs.kde.org/show_bug.cgi?id=361926 Ivo Raisrchanged: What|Removed |Added Status|UNCONFIRMED |CONFIRMED CC||iv...@ivosh.net Assignee|jsew...@acm.org |iv...@ivosh.net Ever confirmed|0 |1 --- Comment #1 from Ivo Raisr --- Adding the missing syscall wrapper should be straightforward. -- You are receiving this mail because: You are watching all bug changes.
[amarok] [Bug 361910] Amarok doesn't play when VLC is running after a video on Phonon-VLC
https://bugs.kde.org/show_bug.cgi?id=361910 --- Comment #2 from Abderrahman Najjar--- I also have phonon-qt4-vlc, in fact I have all the Phonon backends installed $ pacman -Ss phonon extra/phonon-qt4 4.8.3-6 [installed] The multimedia framework for KDE4 extra/phonon-qt4-gstreamer 4.8.2-4 [installed] Phonon GStreamer backend for Qt4 extra/phonon-qt4-vlc 0.8.2-4 [installed] Phonon VLC backend for Qt4 extra/phonon-qt5 4.8.3-6 [installed] The multimedia framework for KF5 extra/phonon-qt5-gstreamer 4.8.2-4 [installed] Phonon GStreamer backend for Qt5 extra/phonon-qt5-vlc 0.8.2-4 [installed] Phonon VLC backend for Qt5 In Amarok I have Phonon VLC selected, the version says 0.8.2. However, there's no v4.8.3 (Qt4) visible to select -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 359072] web browser widget doesn't understand web shortcuts
https://bugs.kde.org/show_bug.cgi?id=359072 Michael Molchanged: What|Removed |Added CC||mike...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 357387] can't use specific homepage for browser-widget
https://bugs.kde.org/show_bug.cgi?id=357387 Michael Molchanged: What|Removed |Added CC||mike...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 359073] web browser widget: shown website cannot be resized, always too small
https://bugs.kde.org/show_bug.cgi?id=359073 Michael Molchanged: What|Removed |Added CC||mike...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 361566] Panel auto-hide is completely broken
https://bugs.kde.org/show_bug.cgi?id=361566 Rex Dieterchanged: What|Removed |Added CC||rdie...@math.unl.edu -- You are receiving this mail because: You are watching all bug changes.
[korgac] [Bug 361938] New: Kontact crashes on changing languages in identities
https://bugs.kde.org/show_bug.cgi?id=361938 Bug ID: 361938 Summary: Kontact crashes on changing languages in identities Product: korgac Version: unspecified Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: korganizer-de...@kde.org Reporter: koffeinfried...@gmail.com Application: korgac (5.1.3) Qt Version: 5.5.1 Operating System: Linux 4.4.0-20-generic x86_64 Distribution: Ubuntu 16.04 LTS -- Information about the crash: - What I was doing when the application crashed: Kontact crashes if I change the default language or spell correction in my identities. This is reproducable for each change. The crash can be reproduced every time. -- Backtrace: Application: KOrganizer-Erinnerungsmodul (korgac), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f6fd3761940 (LWP 11267))] Thread 4 (Thread 0x7f6fcb3e9700 (LWP 11284)): #0 0x7f6fe1ea5a64 in g_mutex_unlock () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7f6fe1e61436 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f6fe9561a9b in QEventDispatcherGlib::processEvents (this=0x7f6fc40008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420 #3 0x7f6fe9508dea in QEventLoop::exec (this=this@entry=0x7f6fcb3e8c80, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #4 0x7f6fe93258a4 in QThread::exec (this=) at thread/qthread.cpp:503 #5 0x7f6fe932a84e in QThreadPrivate::start (arg=0x1f798c0) at thread/qthread_unix.cpp:331 #6 0x7f6fe23826fa in start_thread (arg=0x7f6fcb3e9700) at pthread_create.c:333 #7 0x7f6fe8a2ab5d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 3 (Thread 0x7f6fcabe8700 (LWP 11286)): #0 0x7f6fe93dab8c in QElapsedTimer::clockType () at tools/qelapsedtimer_unix.cpp:150 #1 0x7f6fe93dabd9 in QElapsedTimer::isMonotonic () at tools/qelapsedtimer_unix.cpp:145 #2 0x7f6fe955fa2e in QTimerInfoList::repairTimersIfNeeded (this=0x7f6fbc002cd0) at kernel/qtimerinfo_unix.cpp:155 #3 0x7f6fe955faa3 in QTimerInfoList::timerWait (this=0x7f6fbc002cd0, tm=...) at kernel/qtimerinfo_unix.cpp:382 #4 0x7f6fe9560e7e in timerSourcePrepareHelper (timeout=0x7f6fcabe7ac4, src=) at kernel/qeventdispatcher_glib.cpp:127 #5 timerSourcePrepare (source=, timeout=0x7f6fcabe7ac4) at kernel/qeventdispatcher_glib.cpp:160 #6 0x7f6fe1e608ad in g_main_context_prepare () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #7 0x7f6fe1e6124b in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #8 0x7f6fe1e6142c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #9 0x7f6fe9561a9b in QEventDispatcherGlib::processEvents (this=0x7f6fbc0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420 #10 0x7f6fe9508dea in QEventLoop::exec (this=this@entry=0x7f6fcabe7c80, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #11 0x7f6fe93258a4 in QThread::exec (this=) at thread/qthread.cpp:503 #12 0x7f6fe932a84e in QThreadPrivate::start (arg=0x1f6d330) at thread/qthread_unix.cpp:331 #13 0x7f6fe23826fa in start_thread (arg=0x7f6fcabe8700) at pthread_create.c:333 #14 0x7f6fe8a2ab5d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 2 (Thread 0x7f6fca3e7700 (LWP 11288)): #0 0x7f6fe1ea5a49 in g_mutex_lock () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7f6fe1e61418 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f6fe9561a9b in QEventDispatcherGlib::processEvents (this=0x7f6fc8c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420 #3 0x7f6fe9508dea in QEventLoop::exec (this=this@entry=0x7f6fca3e6c80, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #4 0x7f6fe93258a4 in QThread::exec (this=) at thread/qthread.cpp:503 #5 0x7f6fe932a84e in QThreadPrivate::start (arg=0x1f65ba0) at thread/qthread_unix.cpp:331 #6 0x7f6fe23826fa in start_thread (arg=0x7f6fca3e7700) at pthread_create.c:333 #7 0x7f6fe8a2ab5d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 1 (Thread 0x7f6fd3761940 (LWP 11267)): [KCrash Handler] #6 0x7f6fed0b4c90 in ?? () from /usr/lib/x86_64-linux-gnu/libKF5CalendarCore.so.5 #7 0x7f6fed0b0894 in KCalCore::Calendar::setupRelations(QSharedPointer const&) () from /usr/lib/x86_64-linux-gnu/libKF5CalendarCore.so.5 #8 0x7f6fed0eebac in KCalCore::MemoryCalendar::addIncidence(QSharedPointer const&) () from /usr/lib/x86_64-linux-gnu/libKF5CalendarCore.so.5 #9 0x7f6feda88e9e in ?? () from /usr/lib/x86_64-linux-gnu/libKF5AkonadiCalendar.so.5 #10 0x7f6feda966f8 in ?? () from /usr/lib/x86_64-linux-gnu/libKF5AkonadiCalendar.so.5 #11 0x7f6feda97959 in ?? () from
[krita] [Bug 360595] Krita crashes when we cancel the save custom shortcut dialog box
https://bugs.kde.org/show_bug.cgi?id=360595 Michaelchanged: What|Removed |Added CC||miabr...@gmail.com --- Comment #7 from Michael --- This should be fixed. -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 345750] The currency conversion doesn't show proper values
https://bugs.kde.org/show_bug.cgi?id=345750 Tonatiuh Miramontes Pérezchanged: What|Removed |Added CC||tonatiuhmiramon...@gmail.co ||m -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 353102] Support for XF86AudioMicMute events
https://bugs.kde.org/show_bug.cgi?id=353102 David Roscachanged: What|Removed |Added CC||now...@gmail.com --- Comment #2 from David Rosca --- It's still in review. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 360008] Contents of Power vr registers contents is not printed correctly when the --vgdb-shadow-registers=yes option is used.
https://bugs.kde.org/show_bug.cgi?id=360008 Carl Lovechanged: What|Removed |Added Attachment #98449|0 |1 is obsolete|| --- Comment #8 from Carl Love --- Created attachment 98450 --> https://bugs.kde.org/attachment.cgi?id=98450=edit Secone update to patch to fix GDB issue, changed some comments Noticed a comment that needed a little work when I was verifying the correct patch was in the attachment. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 360008] Contents of Power vr registers contents is not printed correctly when the --vgdb-shadow-registers=yes option is used.
https://bugs.kde.org/show_bug.cgi?id=360008 Carl Lovechanged: What|Removed |Added Attachment #98384|0 |1 is obsolete|| --- Comment #7 from Carl Love --- Created attachment 98449 --> https://bugs.kde.org/attachment.cgi?id=98449=edit Updated patch to fix GDB issue Attached the updated patch -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 360008] Contents of Power vr registers contents is not printed correctly when the --vgdb-shadow-registers=yes option is used.
https://bugs.kde.org/show_bug.cgi?id=360008 Carl Lovechanged: What|Removed |Added Status|UNCONFIRMED |CONFIRMED Ever confirmed|0 |1 --- Comment #6 from Carl Love --- > * typo in power64-core.xml : typo: regect -> rejectFIXED > * powerpc-altivec64l-valgrind.xml : I am not sure to fully understand why we > have 2 new > includes for power64-core2-valgrind-s1.xml and power64-core2-valgrind-s1.xml, > but there was > no addition of power64-core2.xml after power-fpu.xml : normally, the s1 and > s2 files should be > similar in structure to the 'non shadow' register files. I see that the > power64-core2*xml files are > defining the shadow registers for e.g. pc/msr/cr while the equivalent non > shadow registers are > in power64-core.xml It is unclear to me why the shadow registers for these > cannot be defined > in files that are 'similar in structure' to the non shadow files. In power64-core.xml, there is a comment about why the GPRs and pc/msr/cr have to be in that file. In power64-core-valgrind-s*xml, I tried to explain why the definitions of the pc/msr/cr registers had to be moved to power64-core2-valgrind-s*xml but I guess the explanation wasn't clear. I reworked the comments in the power64-core-valgrind-s*xml files to try and make the explanation clearer. Obviously, I didn't get the message across the first time. I think the reworked comments are a lot better. See what you think. > * valgrind-low-ppc64.c : typos fpmap -> fp map lower lower -> lower psuedo -> > pseudo (twice this typo) remove final , after + { "vs31h", 10720, 64 }, > FIXED > * valgrind-low-ppc64.c : we have a bunch of lines that are (almost) > duplicated for big/little Good suggestion, I added two variables low_offset and high_offset and then set them using the ifdefs for big and little endian. That way we have the one copy of the code which uses low_offset and high_offset to index the correct 64-bits in the 128-bit array. The code is much cleaner and more compact. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 361755] 5.21.0: Immediate "Host not found" for all http/https links (within KDE 4 environment)
https://bugs.kde.org/show_bug.cgi?id=361755 --- Comment #6 from Luke-Jr--- $ echo $QT_PLUGIN_PATH /usr/lib/kde4/plugins:/home/luke-jr/.kde4/lib/kde4/plugins/:/usr/lib/kde4/plugins/ $ QT_SELECT=5 qmake -query | grep PLUGINS QT_INSTALL_PLUGINS:/usr/lib/qt5/plugins $ kioclient5 cat ~/.bashrc bash: kioclient5: command not found $ kioclient --version # which is installed by kde-apps/kioclient-15.12.3 Qt: 4.8.6 KDE Development Platform: 4.14.16 KIO Client: 2.0 kioclient works with both the local URI and kde.org -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 361619] Input event lag/drop-out when OpenGL is ON with large window
https://bugs.kde.org/show_bug.cgi?id=361619 --- Comment #30 from Dmitry Kazakov--- I got a new PC with AMD on Saturday. The first tries show that the problem is not only in AMD. It is in combination of Qt 5.6, AMD and openGL mode. Absence of any part of the equation, make the bug not reproducible :) E.g. Qt 5.6 + Haswell + openGL works fine, Qt 5.5.1 + AMD + openGL works also fine :) -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 359030] G'Mic for Krita is limited to one CPU thread
https://bugs.kde.org/show_bug.cgi?id=359030 --- Comment #12 from David Tschumperlé--- Well, maybe there is filters remaining where the two parallelization methods are used in the same time (which is useless of course). Precisely, could you tell what filter allows you to choose the number of CPU and still works with all CPUs at the same time ? This is probably an error from my side, so I can correct it (basically, I'll remove the 'number of threads' option in this case). I don't have any options to choose the number of threads for OpenMP-parallelized algorithms in any case. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 361889] Digikam 5 beta 5: vertical menus (left and right) not displayed properly
https://bugs.kde.org/show_bug.cgi?id=361889 --- Comment #5 from philippe.quag...@laposte.net --- Hello Gilles and Maik. I have reported the bug again because the breeze icon theme was already installed in my computer. I remember the previous discussion after my first submission of the bug. However, Maik comment makes me discover that there are 2 places in Digikam where the theme can be set. One is in «settings» «Theme», where «Breeze» was already set, but still get the bug. But thanks to Maik, I have discovered that there is also a theme related setting in «settings»«configure digikam»«miscaleneous». This was not properly set in my configuration. When I did set Breeze here, and restart Digikam, everything went fine. So I guess it is not a bug, but it is quite confusing for me to have 2 places in the setting where the theme can be set. I thank you again for your help and for this great release. I particularly appreciate the work you have done to fix the panorama tools (works great now) and the date setting of the pano. -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 346118] Plasmashell crash when disconnecting/reconnecting my WiFi connection after changing MTU
https://bugs.kde.org/show_bug.cgi?id=346118 --- Comment #88 from madc...@atlas.cz --- Thanks for pointing me to this bug. I did a little investigation on my own, although I'm not sure how useful it was. I discovered a few things. Dave's "debug 2" patch appears to be wrong. The patch leads to this code: for (int i = 0; i < signalIndexes.count(); ++i) qDebug() << "DAVE notifying delegates"; QMetaObject::activate(item, signalIndexes.at(i), 0); which I assume is supposed to look like this instead: qDebug() << "DAVE notifying delegates"; for (int i = 0; i < signalIndexes.count(); ++i) QMetaObject::activate(item, signalIndexes.at(i), 0); I believe that's what's caused the odd behavior noticed by Alexander. I modified the patch and replaced qDebug() with fputs(), hoping that if there is a threading issue the simpler nature of fputs() might not mess with the timing too much to mask the problem. qt5-declarative package with my patch still crashes the plasma for me with the following output in the terminal. To trigger the crash I had my laptop connect to network "labak" and once the link was up I tried to connect to another available network: DAVE notifying delegates DAVE notifying delegates DAVE notifying delegates DAVE notifying delegates DAVE notifying delegates DAVE notifying delegates DAVE notifying delegates DAVE notifying delegates DAVE notifying delegates DAVE notifying delegates Currrent active notifications: QHash() Guessing partOf as: 0 New Notification: "labak" "Connection 'labak' activated." -1 & Part of: 0 DAVE notifying delegates DAVE notifying delegates DAVE notifying delegates DAVE notifying delegates DAVE notifying delegates DAVE notifying delegates DAVE notifying delegates DAVE notifying delegates DAVE notifying delegates DAVE notifying delegates DAVE notifying delegates DAVE notifying delegates DAVE notifying delegates DAVE notifying delegates DAVE notifying delegates DAVE notifying delegates DAVE notifying delegates DAVE notifying delegates DAVE notifying delegates DAVE notifying delegates DAVE notifying delegates DAVE notifying delegates DAVE notifying delegates DAVE notifying delegates DAVE notifying delegates DAVE notifying delegates DAVE notifying delegates DAVE notifying delegates DAVE notifying delegates DAVE notifying delegates DAVE notifying delegates DAVE notifying delegates DAVE notifying delegates DAVE notifying delegates DAVE notifying delegates DAVE notifying delegates DAVE notifying delegates DAVE notifying delegates DAVE notifying delegates DAVE notifying delegates DAVE notifying delegates DAVE notifying delegates DAVE notifying delegates DAVE notifying delegates DAVE notifying delegates DAVE notifying delegates DAVE notifying delegates DAVE notifying delegates DAVE notifying delegates DAVE notifying delegates DAVE notifying delegates DAVE notifying delegates DAVE notifying delegates DAVE notifying delegates DAVE notifying delegates DAVE notifying delegates DAVE notifying delegates DAVE notifying delegates DAVE notifying delegates DAVE notifying delegates DAVE notifying delegates DAVE notifying delegates DAVE notifying delegates DAVE notifying delegates DAVE notifying delegates DAVE notifying delegates DAVE notifying delegates DAVE notifying delegates DAVE notifying delegates DAVE notifying delegates DAVE notifying delegates DAVE notifying delegates DAVE notifying delegates DAVE notifying delegates DAVE notifying delegates DAVE notifying delegates DAVE notifying delegates DAVE notifying delegates DAVE notifying delegates DAVE notifying delegates DAVE notifying delegates DAVE notifying delegates DAVE notifying delegates DAVE notifying delegates DAVE notifying delegates DAVE notifying delegates DAVE notifying delegates DAVE notifying delegates DAVE notifying delegates DAVE notifying delegates DAVE notifying delegates DAVE notifying delegates DAVE notifying delegates DAVE notifying delegates DAVE notifying delegates DAVE notifying delegates DAVE notifying delegates DAVE notifying delegates DAVE notifying delegates DAVE notifying delegates DAVE notifying delegates DAVE notifying delegates DAVE notifying delegates DAVE notifying delegates DAVE notifying delegates DAVE notifying delegates DAVE notifying delegates DAVE notifying delegates DAVE notifying delegates DAVE notifying delegates DAVE notifying delegates DAVE notifying delegates DAVE notifying delegates DAVE notifying delegates DAVE notifying delegates DAVE notifying delegates DAVE notifying delegates DAVE notifying delegates DAVE notifying delegates DAVE notifying delegates DAVE notifying delegates DAVE notifying delegates DAVE notifying delegates DAVE notifying delegates DAVE notifying delegates DAVE notifying delegates DAVE notifying delegates DAVE notifying delegates DAVE notifying delegates DAVE notifying delegates DAVE notifying delegates KCrash: Attempting to start /usr/bin/plasmashell from kdeinit sock_file=/run/user/1000/kdeinit5__0 KCrash:
[amarok] [Bug 140414] passive popup offering to save a stream URL or playlist when it got opened
https://bugs.kde.org/show_bug.cgi?id=140414 Simon Andricchanged: What|Removed |Added CC||simonandr...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 361937] New: kscreenlocker didn't greeter screen when I want to wake up the session (KDE 5.6)
https://bugs.kde.org/show_bug.cgi?id=361937 Bug ID: 361937 Summary: kscreenlocker didn't greeter screen when I want to wake up the session (KDE 5.6) Product: kscreenlocker Version: unspecified Platform: openSUSE RPMs URL: http://paste.opensuse.org/81978323 OS: Linux Status: UNCONFIRMED Severity: major Priority: NOR Component: greeter Assignee: plasma-b...@kde.org Reporter: adnan...@gmail.com CC: bhus...@gmail.com, mgraess...@kde.org OS openSUSE 13.2 Kernel 3.16.7-35-Desktop KDE Plasma Version 5.6 KDE Framework Version 5.21.0 Qt Version 5.6.0 Kscreenlocker Version kscreenlocker-5.6.2-21.1.x86_64 Output of kscreenlocker_greet --testing kadal@linux-drh2:~> /usr/lib64/libexec/kscreenlocker_greet --testing Locked at 1460995567 file:///usr/share/plasma/look-and-feel/org.kde.breeze.desktop/contents/components/UserPasswordPrompt.qml:25: ReferenceError: userModel is not defined file:///usr/share/plasma/look-and-feel/org.kde.breeze.desktop/contents/components/UserDelegate.qml:82:9: QML Image: Cannot open: file:///usr/share/plasma/look-and-feel/org.kde.breeze.desktop/contents/components/system-log-out org.kde.keyboardLayout: Layouts list changed: ("us") but the greeter screen is come up like it suppose to be, but the session is not lock up completely (panel and icon in panel are shows up and work when i click it) Reproducible: Always Steps to Reproduce: 1. let the screen lock or time out or using Ctrl + Alt + L 2. Wait until screen black 3. Waking up the screen with key touch or mousepad Actual Results: black screen with the message below " The screen locker is broken and unlocking it is not possible any more. In order to unlock switch to virtual terminal (e.g. Ctrl+Alt+F2) login and execute the command : loginctl unlock-sessions Afterwards switch back to the running session (Ctrl+Alt+F7) Expected Results: come up the greeter like it suppose to be, and the session is completely lock up this bug maybe same as bug number 361187 except that kcreenlock-greeter screen is not show up completely from the beginning, and when I use kcreenlock-greeter --testing, my password can unlock it easily like it suppose to be. -- You are receiving this mail because: You are watching all bug changes.
[kdebugsettings] [Bug 361688] kscreen.xcb.help fill log at insane rate
https://bugs.kde.org/show_bug.cgi?id=361688 Bruno Friedmannchanged: What|Removed |Added Resolution|INVALID |--- Status|RESOLVED|UNCONFIRMED Component|libkscreen |general Product|KScreen |kdebugsettings Version|git |unspecified --- Comment #6 from Bruno Friedmann --- Ok I've erase the file, and test kdebugdialog5 and kdedebugdialog (the qt4) none of them create it. the application responsible to create it is kdebugsettings-16.07.70git-12.1.x86_64 I'm moving to the right component. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney4] [Bug 360435] CSV Importer doesn't recognize security if its symbol isn't lower case
https://bugs.kde.org/show_bug.cgi?id=360435 --- Comment #18 from NSLW--- (In reply to allan from comment #17) > That sounds good to me. > Would you check on the Frameworks side please, as Christian committed only > my 'partial' patch. Yeah, I'll check on both branches: frameworks and master. -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 361332] Upgrade from 4.14.2 to 15.12.3 breaks syncing with original ICS calendar file
https://bugs.kde.org/show_bug.cgi?id=361332 Bruno Friedmannchanged: What|Removed |Added CC||mon...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 361332] Upgrade from 4.14.2 to 15.12.3 breaks syncing with original ICS calendar file
https://bugs.kde.org/show_bug.cgi?id=361332 Bruno Friedmannchanged: What|Removed |Added CC||br...@ioda-net.ch --- Comment #1 from Bruno Friedmann --- Still true with git version Message pick from .xsession-error Invalid URL: QUrl("/home/bruno/oc/agendas/bf_2004-2005.ics") "Could not load file '/home/bruno/oc/agendas/bf_2004-2005.ics'." Can be worse, if you change the name of the calendar (right click properties), the file is rewritten with only the first event (data loss) -- You are receiving this mail because: You are watching all bug changes.
[kalarm] [Bug 361936] New: Kalarm startup warning: Time zones are not accessible
https://bugs.kde.org/show_bug.cgi?id=361936 Bug ID: 361936 Summary: Kalarm startup warning: Time zones are not accessible Product: kalarm Version: unspecified Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: djar...@kde.org Reporter: cklim...@hotmail.com My KAlarm version: Version 2.11.2-5ak KDE Frameworks 5.15.0 Qt 5.4.2, kompiliert gegen 5.4.2) Das xcbFenstersystem My OS: Ubuntu 15.10, 64 Bit My version of KAlarm starts at Login which is fine. Only, each time I am disturbed by the following message: “Time zones are not accessible: KAlarm will use the UTC time zone. (The KDE time zone service is not available: check that ktimezoned is installed.)” I have activated the option: “Don't show this message again” but it still continues showing up every time. I don't mind if KAlarm uses the UTC time zone. Nevertheless I would be very grateful if you could let me know how I can get rid of the warning message once and for all. Further information: -The set time zone in my Ubuntu system settings is “Berlin” and that is correct. -I do not have any service or process called timezone or ktimezone running or set in my OS. -In my KAlarm under Settings → Configure KAlarm → Time and Date → Time zone, the only option available is UTC. -I do not have any Plasma workspace installed on my System. Thank you for investigating this bug. Reproducible: Always Steps to Reproduce: 1.Install Kalarm 2.Configure the settings so that Kalarm starts at login 3.Reboot your OS 4.When the Kalarm Timezone warning appears: Check the box so that the Kalarm Timezone warning will not be shown again 5.Reboot your OS and see that the warning is there once again Actual Results: The following warning message is displayed: "Time zones are not accessible: KAlarm will use the UTC time zone. (The KDE time zone service is not available: check that ktimezoned is installed." There is a box to be checked if one does not wish to see the above message again. Checking the box does not change anything. Expected Results: I would expect that activating the option "not to see this message again" should put a definite end to the permanent showing up of this warning each time a boot my OS. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 361935] New: Desktop Effects were restarted due to a graphics reset...
https://bugs.kde.org/show_bug.cgi?id=361935 Bug ID: 361935 Summary: Desktop Effects were restarted due to a graphics reset... Product: plasmashell Version: 5.5.5 Platform: Other OS: Linux Status: UNCONFIRMED Severity: grave Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: vtp...@myfairpoint.net CC: bhus...@gmail.com, plasma-b...@kde.org This error is a regular occurrence after upgrading to 16.04. I've been using this system since 14.10 and have never before run into this bug. Kernel: 4.4.0-18-generic x86_64 (64 bit) Desktop: KDE Plasma 5.5.5 Distro: Ubuntu 16.04 xenial Machine: System: LENOVO (portable) product: 20428 v: Lenovo Yoga 2 11 Mobo: LENOVO model: VIUU4 v: 31900058WIN Bios: LENOVO v: AACN21WW date: 01/30/2015 CPU: Dual core Intel Core i3-4012Y (-HT-MCP-) cache: 3072 KB clock speeds: max: 1500 MHz 1: 1500 MHz 2: 1500 MHz 3: 1155 MHz 4: 1498 MHz Graphics: Card: Intel Device 0a1e Display Server: X.Org 1.18.3 drivers: intel (unloaded: fbdev,vesa) Resolution: 1366x768@60.00hz GLX Renderer: Mesa DRI Intel Haswell GLX Version: 3.0 Mesa 11.2.0 Reproducible: Sometimes Steps to Reproduce: 1.) It can seemingly occur at random---though possibly related to page-rendering in browsers. 2.) It also frequently occurs (though not always) when recovering from suspend mode. 3.) If the system has been unplugged during suspend, restarting can not only cause the above error but also lead to missing text as described in Bug: https://bugs.kde.org/show_bug.cgi?id=361211 But the two Bugs may not be directly related? That is, restarting Desktop Effects only leads to Missing Text 1 out of every 10 restarts. I've marked the Bug as Grave because of its unpredictability and because, at its worst (with missing text) the system is "basically unusable now" and needs to be rebooted. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 361934] New: Konsole Crashed on fast window switch with Alt+Tab
https://bugs.kde.org/show_bug.cgi?id=361934 Bug ID: 361934 Summary: Konsole Crashed on fast window switch with Alt+Tab Product: konsole Version: 15.08.0 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: konsole-de...@kde.org Reporter: m...@s-light.eu Application: konsole (15.08.0) Qt Version: 5.4.2 Operating System: Linux 4.2.0-35-generic x86_64 Distribution: Ubuntu 15.10 -- Information about the crash: - What I was doing when the application crashed: i just switched between windows with Alt+Tab (was multiple fast switches) -- Backtrace: Application: Konsole (konsole), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7ff543961840 (LWP 6379))] Thread 2 (Thread 0x7ff540ae7700 (LWP 6380)): #0 0x7ff55637688d in poll () at ../sysdeps/unix/syscall-template.S:81 #1 0x7ff54eef5bd2 in poll (__timeout=-1, __nfds=1, __fds=0x7ff540ae6c80) at /usr/include/x86_64-linux-gnu/bits/poll2.h:46 #2 _xcb_conn_wait (c=c@entry=0x25bd970, cond=cond@entry=0x25bd9b0, vector=vector@entry=0x0, count=count@entry=0x0) at ../../src/xcb_conn.c:459 #3 0x7ff54eef774f in xcb_wait_for_event (c=0x25bd970) at ../../src/xcb_in.c:623 #4 0x7ff54328ba39 in QXcbEventReader::run (this=0x25cb250) at qxcbconnection.cpp:1105 #5 0x7ff552d852be in QThreadPrivate::start (arg=0x25cb250) at thread/qthread_unix.cpp:337 #6 0x7ff54e8c96aa in start_thread (arg=0x7ff540ae7700) at pthread_create.c:333 #7 0x7ff556381e9d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 1 (Thread 0x7ff543961840 (LWP 6379)): [KCrash Handler] #6 poll_for_reply (c=c@entry=0x25bd970, request=request@entry=11889, reply=reply@entry=0x7ffdf5514898, error=error@entry=0x7ffdf5514990) at ../../src/xcb_in.c:423 #7 0x7ff54eef74f4 in wait_for_reply (c=c@entry=0x25bd970, request=11889, e=e@entry=0x7ffdf5514990) at ../../src/xcb_in.c:490 #8 0x7ff54eef75f1 in xcb_wait_for_reply (c=c@entry=0x25bd970, request=11889, e=e@entry=0x7ffdf5514990) at ../../src/xcb_in.c:521 #9 0x7ff550457a47 in _XReply (dpy=0x25bc5e0, rep=0x7ffdf5514a10, extra=0, discard=0) at ../../src/xcb_io.c:602 #10 0x7ff542e20f32 in XIQueryDevice () from /usr/lib/x86_64-linux-gnu/libXi.so.6 #11 0x7ff5432ac1be in QXcbConnection::handleEnterEvent (this=0x25bc220) at qxcbconnection_xi2.cpp:699 #12 0x7ff54329cc19 in QXcbWindow::handleEnterNotifyEvent (this=0x27aecd0, event=0x7ff53c0033a0) at qxcbwindow.cpp:2102 #13 0x7ff54328dc53 in QXcbConnection::handleXcbEvent (this=this@entry=0x25bc220, event=event@entry=0x7ff53c0033a0) at qxcbconnection.cpp:895 #14 0x7ff54328e3b3 in QXcbConnection::processXcbEvents (this=0x25bc220) at qxcbconnection.cpp:1303 #15 0x7ff552f96651 in QObject::event (this=0x25bc220, e=) at kernel/qobject.cpp:1245 #16 0x7ff553832b8c in QApplicationPrivate::notify_helper (this=this@entry=0x259ce20, receiver=receiver@entry=0x25bc220, e=e@entry=0x7ff53c0034f0) at kernel/qapplication.cpp:3720 #17 0x7ff553838230 in QApplication::notify (this=0x7ffdf55153d0, receiver=0x25bc220, e=0x7ff53c0034f0) at kernel/qapplication.cpp:3503 #18 0x7ff552f64f1b in QCoreApplication::notifyInternal (this=0x7ffdf55153d0, receiver=0x25bc220, event=event@entry=0x7ff53c0034f0) at kernel/qcoreapplication.cpp:935 #19 0x7ff552f67057 in QCoreApplication::sendEvent (event=0x7ff53c0034f0, receiver=) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:228 #20 QCoreApplicationPrivate::sendPostedEvents (receiver=receiver@entry=0x0, event_type=event_type@entry=0, data=0x254da10) at kernel/qcoreapplication.cpp:1552 #21 0x7ff552f67588 in QCoreApplication::sendPostedEvents (receiver=receiver@entry=0x0, event_type=event_type@entry=0) at kernel/qcoreapplication.cpp:1410 #22 0x7ff552fbbe73 in postEventSourceDispatch (s=0x25efbf0) at kernel/qeventdispatcher_glib.cpp:271 #23 0x7ff54e192ff7 in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #24 0x7ff54e193250 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #25 0x7ff54e1932fc in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #26 0x7ff552fbc27f in QEventDispatcherGlib::processEvents (this=0x25ffa00, flags=...) at kernel/qeventdispatcher_glib.cpp:418 #27 0x7ff552f6275a in QEventLoop::exec (this=this@entry=0x7ffdf5515290, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #28 0x7ff552f6a2cc in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1188 #29 0x7ff55327f00c in QGuiApplication::exec () at kernel/qguiapplication.cpp:1510 #30 0x7ff55382f025 in QApplication::exec () at kernel/qapplication.cpp:2956 #31 0x7ff55bdb in kdemain (argc=1, argv=0x7ffdf5515518) at
[krita] [Bug 356086] Double-sized ghost of previous frame when moving a layer with the onion skin enabled
https://bugs.kde.org/show_bug.cgi?id=356086 Dmitry Kazakovchanged: What|Removed |Added Ever confirmed|0 |1 CC||dimul...@gmail.com Status|UNCONFIRMED |CONFIRMED --- Comment #2 from Dmitry Kazakov --- Ok, in the current version of Krita it draws the scaled copy of the onin scin, and then hides it back. Weird bug, but confirmed :) -- You are receiving this mail because: You are watching all bug changes.