[kmail2] [Bug 374546] Issue with content encoding
https://bugs.kde.org/show_bug.cgi?id=374546 Daniel Vrátil changed: What|Removed |Added CC||dvra...@kde.org --- Comment #4 from Daniel Vrátil --- Do you have a specific email that you can reproduce the issue with? Could you attach it here or share it privately with me? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 379649] New: Application Launcher search box does not accept keyboard input
https://bugs.kde.org/show_bug.cgi?id=379649 Bug ID: 379649 Summary: Application Launcher search box does not accept keyboard input Product: plasmashell Version: 5.7.1 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Application Launcher (Kickoff) Assignee: k...@davidedmundson.co.uk Reporter: h.k.gh...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 DESCRIPTION Starting with Kubuntu 16.10, and still under 17.04, the Application Launcher is refusing to accept keyboard input in the "Type to search..." input box section[1]. When the launcher is opened, I can give the keyboard focus to it, but hitting keyboard keys results in nothing being written to it, making it unusable during normal usage. EXPECTED BEHAVIOR The search box accepts keyboard inputs and performs its automatic search while the user is typing. OBSERVED BEHAVIOR Most of the time, nothing happens. In a few cases, the first key pressed will be registered, but nothing else after that. STEPS TO REPRODUCE 1. Open the Application Launcher 2. Place the cursor on the "Type to search..." input box within the launcher (e.g. mouse click) 3. Press keyboard keys VERSION INFORMATION I'm not sure what version the Application Launcher is, so I retrieved version values that I hope are relevant from Dolphin >> Help >> About Dolphin >> Libraries Tab: * KDE Frameworks 5.31.0 * Qt 5.7.1 (built against 5.7.1) REMARKS If I copy a word, and then paste it on to it, either by using Ctrl+V or Right-Mouse Button -> Paste, the text is actually added to the input box and it works as intended. The problem is only seen when trying to enter input with key presses directly. This actually used to work during the initial 16.10 install, but broke several months after that (perhaps during a package update). I don't know how long it had been broken by the time I noticed it was actually broken, unfortunately. I've tried removing/purging the kubuntu-desktop and plasma-desktop packages and configuration files, rebooting, and then re-installing those packages, but the issue is still present. I'll note that this is happening in a laptop. I've never seen this problem in my desktop[2], which was also running 16.10 and was also upgraded to 17.04. FOOTNOTES [1] I've noticed the same problem with the network manager, particularly when you need to enter a password (e.g. connecting to a VPN), but I'm filing under Application Launcher b/c it's the most visible and annoying of them. The issue, however, might be related. [2] Generally, my laptop experience is always more problematic than my desktop experience, including sddm's refusal to launch and having to rely on lightdm, among others, but I don't know why this is the case. -- You are receiving this mail because: You are watching all bug changes.
[umbrello] [Bug 376305] Windows 7 Umbrello won't save model no mime types installed
https://bugs.kde.org/show_bug.cgi?id=376305 --- Comment #7 from Ralf Habacker --- I added a related faq entry to https://userbase.kde.org/Umbrello/FAQ#How_to_fix_the_error_message_.27There_was_a_problem_saving_file.27_.3F Thanks for pointing this out. Does this help you to fix your problem ? -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 350365] Battery monitor in tray randomly shows there is no battery
https://bugs.kde.org/show_bug.cgi?id=350365 Stefan Schmid changed: What|Removed |Added CC||schmidi...@gmail.com --- Comment #16 from Stefan Schmid --- (In reply to Jannis Mast from comment #7) > Same problem here on Gentoo, running Linux 4.7.10, KDE frameworks 5.26.0 and > Plasma 5.7.5. I have first seen this after upgrading from Plasma 5.6 and > frameworks 5.23. The same also here... All components except those from KDE recognize the battery correctly. :( Why is no developer interested in this problem again? -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 378554] Connections can't be edited
https://bugs.kde.org/show_bug.cgi?id=378554 Jan Grulich changed: What|Removed |Added CC||christian.la...@gmx.net --- Comment #6 from Jan Grulich --- *** Bug 379645 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 379645] Networkmanager can not save custom DNS settings
https://bugs.kde.org/show_bug.cgi?id=379645 Jan Grulich changed: What|Removed |Added Resolution|--- |DUPLICATE Status|UNCONFIRMED |RESOLVED CC||jgrul...@redhat.com --- Comment #1 from Jan Grulich --- *** This bug has been marked as a duplicate of bug 378554 *** -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 379650] New: Krita seriously crashes in latest stable version (WIN10 PRO)
https://bugs.kde.org/show_bug.cgi?id=379650 Bug ID: 379650 Summary: Krita seriously crashes in latest stable version (WIN10 PRO) Product: krita Version: 3.1.3 Platform: MS Windows OS: MS Windows Status: UNCONFIRMED Severity: crash Priority: NOR Component: general Assignee: krita-bugs-n...@kde.org Reporter: garb...@gmail.com Target Milestone: --- This is a crash log that has happened since last alpha/beta/stable versions of KRITA 3.1.3 on one of my WINDOWS systems (WIN10 64-bit with INTEL gfx-card that has latest drivers installed): "Error occurred on Tuesday, May 9, 2017 at 09:27:25. krita.exe caused an Access Violation at location 7FFF4A6D5FE0 in module libkritaimage.dll Reading from location 9142EF20. AddrPC Params 7FFF4A6D5FE0 7FFF4A6D60D6 006819C0 libkritaimage.dll!cblas_xerbla 7FFF4A6D417A 006819C0 libkritaimage.dll!cblas_xerbla 7FFF4A6D4A05 02D82301 0001 A5EDF8A0 libkritaimage.dll!cblas_xerbla 7FFF4A811856 8000 A5EDF8A0 libkritaimage.dll!operator+=, QString> 7FFF4A544C4C 0001 A5B76F10 A5B76F30 libkritaimage.dll!KisUpdateTimeMonitor::instance 7FFF4A554331 A5F9ECB1 688990A7 A603F640 libkritaimage.dll!KisImage::notifyProjectionUpdated 68A2EBCA A5D01A08 6889D51A Qt5Core.dll!QMetaObject::activate 7FFF4A662D90 0010 A704FDD0 A603F640 libkritaimage.dll!KisUpdaterContext::qt_static_metacall 68A2EBCA A5B76190 00F0 0003 Qt5Core.dll!QMetaObject::activate 7FFF4A6FE905 68B4E4DC 0010 libkritaimage.dll!KisUpdateJobItem::run 6889BEC9 A603F5E0 A5B78110 0A6E7280 Qt5Core.dll!QThreadPoolPrivate::startThread 6889DB6C 031FEA70 Qt5Core.dll!QThread::setTerminationEnabled 7FFF768BB2BA 7FFF76910670 0A6E7280 msvcrt.dll!_beginthreadex 7FFF768BB38C msvcrt.dll!_endthreadex 7FFF76A38364 KERNEL32.DLL!BaseThreadInitThunk 7FFF77A270D1 ntdll.dll!RtlUserThreadStart krita.exe ntdll.dll 6.2.14393.479 KERNEL32.DLL6.2.14393.0 KERNELBASE.dll 6.2.14393.1066 apphelp.dll 6.2.14393.0 msvcrt.dll 7.0.14393.0 libkritaui.dll libkritawidgetutils.dll libKF5I18n.dll Qt5Core.dll 5.6.1.0 Qt5Gui.dll 5.6.1.0 Qt5Widgets.dll 5.6.1.0 ADVAPI32.dll6.2.14393.0 USER32.dll 6.2.14393.576 sechost.dll 6.2.14393.0 win32u.dll 6.2.14393.51 RPCRT4.dll 6.2.14393.82 GDI32.dll 6.2.14393.206 ole32.dll 6.2.14393.1066 gdi32full.dll 6.2.14393.1066 combase.dll 6.2.14393.953 ucrtbase.dll6.2.14393.0 libkritaglobal.dll bcryptPrimitives.dll6.2.14393.0 libkritaplugin.dll SHELL32.dll 6.2.14393.1066 cfgmgr32.dll6.2.14393.0 windows.storage.dll 6.2.14393.1066 libKF5ConfigCore.dll powrprof.dll6.2.14393.0 libKF5ConfigGui.dll libKF5CoreAddons.dll shlwapi.dll 6.2.14393.0 kernel.appcore.dll 6.2.14393.0 shcore.dll 6.2.14393.953 profapi.dll 6.2.14393.0 WS2_32.dll 6.2.14393.206 libKF5GuiAddons.dll libKF5ItemViews.dll libKF5WidgetsAddons.dll libKF5WindowSystem.dll Qt5PrintSupport.dll 5.6.1.0 Qt5Xml.dll 5.6.1.0 libintl.DLL 0.18.0.0 libkritacolor.dll libkritaflake.dll libkritaimage.dll comdlg32.dll6.2.14393.479 libkritalibbrush.dll libkritaodf.dll libkritapigment.dll libkritapsd.dll libkritastore.dll libkritaundo2.dll libkritaversion.dll libkritawidgets.dll libexiv2.dll libKF5Completion.dll PSAPI.DLL 6.2.14393.0 Qt5Network.dll 5.6.1.0 Qt5Multimedia.dll 5.6.1.0 MPR.dll 6.2.14393.0 libHalf.dll libpng16.dll OPENGL32.dll6.2.14393.0 NETAPI32.dll6.2.14393.0 USERENV.dll 6.2.14393.0 iconv.dll WINSPOOL.DRV6.2.14393.953 Qt5Svg.dll 5.6.1.0 COMCTL32.dll5.82.14393.447 libfftw3-3.dll Qt5Concurrent.dll 5.6.1.0 libKF5Archive.dll libexpat.dll libz.dll1.2.8.0 DNSAPI.dll 6.2.14393.953 IPHLPAPI.DLL6.2.14393.953 NSI.dll 6.2.14393.0 GLU32.dll 6.2.14393.0 DDRAW.dll 6.2.14393.953 bcrypt.dll 6.2.14393.576 NETUTILS.DLL6.2.14393.0 DCIMAN32.dll6.2.14393.0 LOGONCLI.DLL6.2.14393.0 SAMCLI.DLL 6.2.14393.0 IMM32.DLL 6.2.14393.0 qwindows.dll5.6.1.0 OLEAUT32.dll6.2.14393.1066 msvcp_win.dll 6.2.14393.0 WINMM.dll 6.2.14393.0 WINMMBASE.dll 6.2.14393.0 uxtheme.dll 6.2.14393.0 dwmapi.dll 6.2.14393.206 ig7icd64.dll10.18.10.4425 igdu
[plasma-nm] [Bug 378890] Disconnects from the internet
https://bugs.kde.org/show_bug.cgi?id=378890 Jan Grulich changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED CC||jgrul...@redhat.com Resolution|--- |WONTFIX --- Comment #1 from Jan Grulich --- This doesn't look like a problem in plasma-nm, I would suggest reporting this to NetworkManager instead [1]. [1] - https://bugzilla.gnome.org/page.cgi?id=browse.html&product=NetworkManager -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 379651] New: Vector issue on Krita 3.1.3.5
https://bugs.kde.org/show_bug.cgi?id=379651 Bug ID: 379651 Summary: Vector issue on Krita 3.1.3.5 Product: krita Version: 3.1.3 Platform: MS Windows OS: MS Windows Status: UNCONFIRMED Severity: crash Priority: NOR Component: Vector Objects and Tools Assignee: krita-bugs-n...@kde.org Reporter: jan...@grzybek.anet.pl Target Milestone: --- Created attachment 105407 --> https://bugs.kde.org/attachment.cgi?id=105407&action=edit Krita log When I try add a vector object (ellipse, polygon, etc.) to document it always closes Krita 3.1.3. After downgrade to Krita 3.1.2.2 it works OK. I attached bug log. Win 10 32-bit, Intel i7-2700K, ATI Radeon HD6450, Best regards, Janusz -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 374546] Issue with content encoding
https://bugs.kde.org/show_bug.cgi?id=374546 --- Comment #5 from Vishnu --- Created attachment 105408 --> https://bugs.kde.org/attachment.cgi?id=105408&action=edit Signed mail sent with KMail I'm attaching the two mails from my 'Sent' folder. The 'To' address is also mine, and even the messages I receive in that mailbox show the same behaviour as those in the sent folders. i.e., that KMail accepts both signatures as valid; Evolution doesn't accept the ones sent by KMail. To check, you'll have to locally sign my key. My OpenPGP fingerprint is: 5015 1D4C 9BDF 9062 A9E1 62CB 5B1F4BEE7EED7131 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 379647] Crash on starting animation
https://bugs.kde.org/show_bug.cgi?id=379647 Boudewijn Rempt changed: What|Removed |Added CC||b...@valdyas.org Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #3 from Boudewijn Rempt --- This issue is already fixed and I will be making a new 3.1.4 release this week. The issue that pretty much none of the developers and beta testers (of which we have way too few!) use Krita with opengl disabled. -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 378316] High cpu usage in task manager network monitor when "Setting network address" state
https://bugs.kde.org/show_bug.cgi?id=378316 Jan Grulich changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED CC||jgrul...@redhat.com Resolution|--- |DUPLICATE --- Comment #3 from Jan Grulich --- *** This bug has been marked as a duplicate of bug 356479 *** -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 379630] false positive std::mutex problems
https://bugs.kde.org/show_bug.cgi?id=379630 --- Comment #6 from Gregory Nilsson --- Created attachment 105409 --> https://bugs.kde.org/attachment.cgi?id=105409&action=edit test case with mutex wrapper -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356479] plasmashell uses 100% CPU when there is an animation in the task bar
https://bugs.kde.org/show_bug.cgi?id=356479 Jan Grulich changed: What|Removed |Added CC||torres.sold...@gmail.com --- Comment #126 from Jan Grulich --- *** Bug 378316 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 374546] Issue with content encoding
https://bugs.kde.org/show_bug.cgi?id=374546 --- Comment #6 from Vishnu --- Created attachment 105410 --> https://bugs.kde.org/attachment.cgi?id=105410&action=edit Signed mail sent with Evolution The main difference between the two is that in the one sent with Evolution, there is a '=20' just before where I display my 'OpenPGP Fingerprint' in the body of the mail. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 379630] false positive std::mutex problems
https://bugs.kde.org/show_bug.cgi?id=379630 --- Comment #7 from Gregory Nilsson --- Created attachment 105411 --> https://bugs.kde.org/attachment.cgi?id=105411&action=edit log when using wrapper -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 378259] [RFE] NetworkManager does not send new hostname to DHCP server
https://bugs.kde.org/show_bug.cgi?id=378259 Jan Grulich changed: What|Removed |Added Summary|NetworkManager does not |[RFE] NetworkManager does |send new hostname to DHCP |not send new hostname to |server |DHCP server -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 379630] false positive std::mutex problems
https://bugs.kde.org/show_bug.cgi?id=379630 --- Comment #8 from Gregory Nilsson --- I've created a wrapper for the std::mutex (updated test code attached), with VALGRIND_HG_MUTEX_INIT_POST/VALGRIND_HG_MUTEX_DESTROY_PRE in its constructor/destructor. The lock order violation error is now gone (log attached). Is this how I should do it if I want helgrind to handle std::mutex correctly? -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 379650] Krita seriously crashes in latest stable version (WIN10 PRO)
https://bugs.kde.org/show_bug.cgi?id=379650 Boudewijn Rempt changed: What|Removed |Added CC||b...@valdyas.org --- Comment #1 from Boudewijn Rempt --- Though the crash seems to be in a maths library, it's a very weird backtrace. I've seen this backtrace reported by one or two other people, but, of course, I don't experience it myself on any of my windows test systems. Does it also crash if you disable opengl? And could you please tell me the exact version of the intel opengl driver -- check it in the Device Manager application, since that gives Intel's numbering, the settings system info gives Microsoft's numbering. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 379651] Vector issue on Krita 3.1.3.5
https://bugs.kde.org/show_bug.cgi?id=379651 Boudewijn Rempt changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|UNCONFIRMED |NEEDSINFO CC||b...@valdyas.org --- Comment #1 from Boudewijn Rempt --- Hi Janusz, I still cannot reproduce the issue. Could you also try to install the debug symbols? That should give a fuller crash log. See https://docs.krita.org/Dr._Mingw_debugger -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 379609] "Krita.exe stopped working'' after opening the Animation-Japanese-En template.
https://bugs.kde.org/show_bug.cgi?id=379609 Boudewijn Rempt changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|UNCONFIRMED |NEEDSINFO CC||b...@valdyas.org --- Comment #1 from Boudewijn Rempt --- Could you please install the debug symbols (https://docs.krita.org/Dr._Mingw_debugger) and provide a crash log? I cannot reproduce the crash here. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 375415] free list of blocks, mempool blocks and describe addr do not work properly together
https://bugs.kde.org/show_bug.cgi?id=375415 --- Comment #4 from Ruurd Beerstra --- Sorry for the delay, I'm doing lots of stuff on other projects and valgrind is on the back burner for me. It "just works" as part of our regression framework, doing several thousand runs every night and catches newly introduced memory errors every so often. So I hope I can still make sense here :-) Point 1 (bad redzone): My bad, caused by being all new to valgrind when I took a stab at modifying it. Our code doesn't use redzones, so both are zero and I didn't look closely enough. Needs a fix. Point 2: The not-is-mempool test: Unless I'm completely wrong here: If I take that test out, many application-malloced blocks that lie within a mempool block will be described as lying within a mempool block, with the allocation stack being the one that triggered the allocation of that mempool block (some random moment when the pool is exhausted). That is not what I want: I want the description of the malloc that was done *from* the mempool block, with the proper allocation stack. This is because our allocator uses itself to allocate the mempool blocks, so both mempool-block allocs and plain application allocs are on the same malloc list. The test for a mempool block at the end was added to catch the case where an application-malloc is NOT within a mempool, which should not happen in our custom-allocator case, but the case needs handling. Your remark: "what you have removed is that a mempool (inner for meta pool) block is never landing in an error address description" is correct: I consider that address description an internal and uninteresting affair of our custom allocator and there should always be a more interesting, application malloc stack that I want to show. Does that make sense? Point 3: About the order: I think you sort of echo there what I try to describe above. This is hard stuff, trying to get the best address description in all cases. All I can say: The current version works for me, and I gather there are few custom allocators these days that use the mempool features. But if my amateur changes require rework: feel free to improve upon it. I'll (test) run it in our test environment. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 372828] vex amd64->IR: unhandled instruction bytes: 0x66 0x4D 0xF 0x38 0xF6 0xD2 0x66 0x4D
https://bugs.kde.org/show_bug.cgi?id=372828 --- Comment #2 from m...@cyrilbouvier.fr --- (In reply to Ivo Raisr from comment #1) > Please could you report which unhandled instruction is this? You can use gdb > or objdump, for example. Hi, Can you be more specific on how to use gdb or objdump to find the illegal instruction ? Thanks, Cyril. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 379652] New: konsole pane shows delete confirmation for temporary file
https://bugs.kde.org/show_bug.cgi?id=379652
Bug ID: 379652
Summary: konsole pane shows delete confirmation for temporary
file
Product: kdevelop
Version: 5.1.0
Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: NOR
Component: general
Assignee: kdevelop-bugs-n...@kde.org
Reporter: lars.diec...@googlemail.com
Target Milestone: ---
reproduction
alias rm='/bin/rm -i'
start kdevelop
open the konsole pane
result
--
kdevelop! is run, which in turn calls kdevplatform_shell_environment.sh
output of these shell script is shown in the pane
there's a delete confirmation that's impossible to answer
the temporary file hangs around after the scripts finish
what should happen
--
don't show a delete confirmation
do delete the temporary file
remedy
--
add the `-f` option
diff --git a/kdevplatform_shell_environment.sh
b/kdevplatform_shell_environment.sh
index 58b536e..6104276 100755
--- a/kdevplatform_shell_environment.sh
+++ b/kdevplatform_shell_environment.sh
@@ -786,7 +786,7 @@ function setenv! {
executeInAppSync "if ! [ -e $(getCurrentShellEnvPath) ]; then touch
$(getCurrentShellEnvPath); fi" ""
fi
source $TEMP
-rm $TEMP
+rm -f $TEMP
}
function showenv! {
--
You are receiving this mail because:
You are watching all bug changes.
[valgrind] [Bug 372828] vex amd64->IR: unhandled instruction bytes: 0x66 0x4D 0xF 0x38 0xF6 0xD2 0x66 0x4D
https://bugs.kde.org/show_bug.cgi?id=372828 --- Comment #3 from Ivo Raisr --- For example with objdump: objdump -d /home/x/lib/libgmp.so.10.3.1 | grep '66 4d 0f 38 f6 d2 66 4d' and the instruction name should be right after the byte sequence. -- You are receiving this mail because: You are watching all bug changes.
[kdevplatform] [Bug 379652] konsole pane shows delete confirmation for temporary file
https://bugs.kde.org/show_bug.cgi?id=379652 Kevin Funk changed: What|Removed |Added Product|kdevelop|kdevplatform Status|UNCONFIRMED |CONFIRMED Ever confirmed|0 |1 Component|general |shell -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 371722] Let crash handler install debug packages
https://bugs.kde.org/show_bug.cgi?id=371722 --- Comment #5 from Pascal d'Hermilly --- Created attachment 105412 --> https://bugs.kde.org/attachment.cgi?id=105412&action=edit We are almost there screenshot - but I'm not getting the prompt for password. Now after a plasma crash I was able to click somehing like "get debug packages", but unfortunately it looks like it's searching forever or the password prompt just never happens. Super nice to see progress though :D -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 379653] New: class declaration not shown in classes pane
https://bugs.kde.org/show_bug.cgi?id=379653
Bug ID: 379653
Summary: class declaration not shown in classes pane
Product: kdevelop
Version: 5.1.0
Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: NOR
Component: Language Support: QML/JavaScript
Assignee: kdevelop-bugs-n...@kde.org
Reporter: lars.diec...@googlemail.com
Target Milestone: ---
reproduce
-
insert code
class Custom_Collection extends Backbone.Collection {
initialize(build) {
super.initialize(build);
}
get model() { return; }
populate() { return; }
}
into an empty document and save as `foo.js`
filetype detection is performed and the appropriate syntax highlighting is
applied
open the classes pane
result
--
class declaration is not shown in the pane
what should happen
--
class declaration is shown in the pane
--
You are receiving this mail because:
You are watching all bug changes.
[valgrind] [Bug 372828] vex amd64->IR: unhandled instruction bytes: 0x66 0x4D 0xF 0x38 0xF6 0xD2 0x66 0x4D
https://bugs.kde.org/show_bug.cgi?id=372828 --- Comment #4 from m...@cyrilbouvier.fr --- Hope it can help : > objdump -d libgmp.so.10.3.1 | grep '66 4d 0f 38 f6 d2' 2cac2: 66 4d 0f 38 f6 d2 adcx %r10,%r10 Cyril -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 379654] New: Dolphin does not allow renaming Wastebin to 'Trash'
https://bugs.kde.org/show_bug.cgi?id=379654 Bug ID: 379654 Summary: Dolphin does not allow renaming Wastebin to 'Trash' Product: dolphin Version: 17.04.0 Platform: unspecified OS: Linux Status: UNCONFIRMED Severity: minor Priority: NOR Component: panels: places Assignee: dolphin-bugs-n...@kde.org Reporter: g...@politeia.in Target Milestone: --- Hello, Independently of my chosen locale/translation - it is impossible to rename the Wastebin place name to 'Trash' in Dolphin, it reverts it back to... (in my case) Wastebin. I can rename it to everything else that isn't the word 'Trash' (with capital T), all other variations like 'trash', 'TRash', 'TRASH' work as expected. Visual example here: https://i.imgur.com/4Scq5QM.gif Thanks in advance. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 379650] Krita seriously crashes in latest stable version (WIN10 PRO)
https://bugs.kde.org/show_bug.cgi?id=379650 --- Comment #2 from MichalG --- Of course Intel sucks at its drivers as on another computer at home I have Nvidia's 1060 and Krita works flawlessly. As for INTEL drivers (which is the latest probably): x.x.x.4425 (Graphics) and 10.1.1.14 (Chipset). I cannot see OpenGL's version there. It is WIN 10 64-bit, 4 GB RAM, i5-3470 @3.20 Ghz processor When I disable OpenGL, Krita hangs(up) and there is no response from the program... :( -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 372828] vex amd64->IR: unhandled instruction bytes: 0x66 0x4D 0xF 0x38 0xF6 0xD2 0x66 0x4D (adcx)
https://bugs.kde.org/show_bug.cgi?id=372828 Ivo Raisr changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |CONFIRMED --- Comment #5 from Ivo Raisr --- Yes, it indeed does. Thank you. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 372828] vex amd64->IR: unhandled instruction bytes: 0x66 0x4D 0xF 0x38 0xF6 0xD2 0x66 0x4D (adcx)
https://bugs.kde.org/show_bug.cgi?id=372828 Ivo Raisr changed: What|Removed |Added Summary|vex amd64->IR: unhandled|vex amd64->IR: unhandled |instruction bytes: 0x66 |instruction bytes: 0x66 |0x4D 0xF 0x38 0xF6 0xD2 |0x4D 0xF 0x38 0xF6 0xD2 |0x66 0x4D |0x66 0x4D (adcx) -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 379651] Vector issue on Krita 3.1.3.5
https://bugs.kde.org/show_bug.cgi?id=379651 --- Comment #2 from Janusz Grzybek --- Created attachment 105413 --> https://bugs.kde.org/attachment.cgi?id=105413&action=edit New log (with Debug package) I used Krita portable + debug package, but seems to me there is no more info in the log. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 372828] vex amd64->IR: unhandled instruction bytes: 0x66 0x4D 0xF 0x38 0xF6 0xD2 0x66 0x4D (adcx)
https://bugs.kde.org/show_bug.cgi?id=372828 --- Comment #6 from Ivo Raisr --- This bug is a duplicate of: 360415 amd64 instructions ADCX and ADOX are not implemented in VEX -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 372828] vex amd64->IR: unhandled instruction bytes: 0x66 0x4D 0xF 0x38 0xF6 0xD2 0x66 0x4D (adcx)
https://bugs.kde.org/show_bug.cgi?id=372828 Ivo Raisr changed: What|Removed |Added Assignee|jsew...@acm.org |iv...@ivosh.net -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 372828] vex amd64->IR: unhandled instruction bytes: 0x66 0x4D 0xF 0x38 0xF6 0xD2 0x66 0x4D (adcx)
https://bugs.kde.org/show_bug.cgi?id=372828 Ivo Raisr changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |DUPLICATE --- Comment #7 from Ivo Raisr --- *** This bug has been marked as a duplicate of bug 360415 *** -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 360415] amd64 instructions ADCX and ADOX are not implemented in VEX
https://bugs.kde.org/show_bug.cgi?id=360415 Ivo Raisr changed: What|Removed |Added CC||m...@cyrilbouvier.fr --- Comment #13 from Ivo Raisr --- *** Bug 372828 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 379655] New: Inbox uses outbox icon
https://bugs.kde.org/show_bug.cgi?id=379655 Bug ID: 379655 Summary: Inbox uses outbox icon Product: kmail2 Version: Git (master) Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: folders Assignee: kdepim-b...@kde.org Reporter: tipos...@tiscali.it Target Milestone: --- Created attachment 105414 --> https://bugs.kde.org/attachment.cgi?id=105414&action=edit the issue And there is no way to change that. While the icon for the other folder can be customised, the inbox only uses the icon for the sent emails folder. The version I use is not listed, but it's 4:16.04.3-3. -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 378216] Kmail / Kontact crash when moving & copying mail folders
https://bugs.kde.org/show_bug.cgi?id=378216 Michel changed: What|Removed |Added CC||dubois.mic...@gmail.com --- Comment #1 from Michel --- Hi, I've got the same problem. I went to import my backup mail to my new kontact/kmail interface due a crash. I can not move my old mail folder to a new one. I did many akonadi_ctl restart no issue. KDE Frameworks 5.18.0 Qt 5.5.1 (built against 5.5.1) Ubuntu 16.04.2 LTS -- You are receiving this mail because: You are watching all bug changes.
[plasma-pk-updates] [Bug 379462] Checkboxes flicker when scrolled
https://bugs.kde.org/show_bug.cgi?id=379462 Jan Grulich changed: What|Removed |Added CC||jgrul...@redhat.com --- Comment #1 from Jan Grulich --- This looks like a Qt issue, I don't think this is a problem of plasma-pk-updates. -- You are receiving this mail because: You are watching all bug changes.
[konversation] [Bug 379594] Downgrade emoticons dependency to optional
https://bugs.kde.org/show_bug.cgi?id=379594 Christoph Feck changed: What|Removed |Added Severity|normal |wishlist -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 379656] New: Missing unrar crashes KDE Dolphin on unrar request via context menu
https://bugs.kde.org/show_bug.cgi?id=379656 Bug ID: 379656 Summary: Missing unrar crashes KDE Dolphin on unrar request via context menu Product: dolphin Version: 15.12.3 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: 2017.hn2s@stumpf.de Target Milestone: --- Application: dolphin (15.12.3) Qt Version: 5.5.1 Operating System: Linux 4.4.0-75-generic x86_64 Distribution: Ubuntu 16.04.2 LTS -- Information about the crash: - What I was doing when the application crashed: 1. Dragged a .rar-file in ~/Downloads to the same folder ~/Downloads 2. Released the mouse button 3. Selected "Extract here" in context menu 4. Crash This was performed on a rather fresh Kubuntu installation. Packages "unrar" or "unrar-free" were not present, so unpacking should have failed probably. However, with an informational message and not a crash. After installing "unrar" package dolphin did not crash anymore. After removing "unrar" and installing "unrar-free" dolphin dit not crash anymore, but the file could not be unpacked and no error code was displayed. It couldn't be unpacked on the console either - perhaps the file format was too new. --- output information about the rar file: # unrar lt BilderPersonalKoerper.rar UNRAR 5.30 beta 2 freeware Copyright (c) 1993-2015 Alexander Roshal Archive: BilderPersonalKoerper.rar Details: RAR 4 Name: Organigramm.jpg Type: File Size: 119767 Packed size: 83303 Ratio: 69% mtime: 2017-05-05 18:49:33,852 Attributes: ..A CRC32: 459D1845 Host OS: Windows Compression: RAR 3.0(v29) -m3 -md=2M The crash can be reproduced every time. -- Backtrace: Application: Dolphin (dolphin), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f7b42e6c8c0 (LWP 5521))] Thread 4 (Thread 0x7f7b0b7fd700 (LWP 14907)): [KCrash Handler] #6 0x7f7b50a69f87 in QObjectPrivate::connectImpl(QObject const*, int, QObject const*, void**, QtPrivate::QSlotObjectBase*, Qt::ConnectionType, int const*, QMetaObject const*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f7b50a6a3ea in QObject::connectImpl(QObject const*, void**, QObject const*, void**, QtPrivate::QSlotObjectBase*, Qt::ConnectionType, int const*, QMetaObject const*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f7b2b69a74c in Kerfuffle::Job::connectToArchiveInterfaceSignals() () from /usr/lib/x86_64-linux-gnu/libkerfuffle.so.15 #9 0x7f7b2b69ace9 in Kerfuffle::ListJob::doWork() () from /usr/lib/x86_64-linux-gnu/libkerfuffle.so.15 #10 0x7f7b2b699131 in Kerfuffle::Job::Private::run() () from /usr/lib/x86_64-linux-gnu/libkerfuffle.so.15 #11 0x7f7b508577be in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #12 0x7f7b4d0056ba in start_thread (arg=0x7f7b0b7fd700) at pthread_create.c:333 #13 0x7f7b55c9182d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 3 (Thread 0x7f7b32183700 (LWP 5523)): #0 0x7f7b55c85b5d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7f7b4c47938c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f7b4c47949c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f7b50a8e7eb in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f7b50a35b4a in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f7b50852834 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f7b508577be in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f7b4d0056ba in start_thread (arg=0x7f7b32183700) at pthread_create.c:333 #8 0x7f7b55c9182d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 2 (Thread 0x7f7b405f4700 (LWP 5522)): #0 0x7f7b55c85b5d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7f7b4a40dc62 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 #2 0x7f7b4a40f8d7 in xcb_wait_for_event () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 #3 0x7f7b42946629 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5 #4 0x7f7b508577be in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f7b4d0056ba in start_thread (arg=0x7f7b405f4700) at pthread_create.c:333 #6 0x7f7b55c9182d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 1 (Thread 0x7f7b42e6c8c0 (LWP 5521)): #0 0x7f7b55c816fd in write () at ../sysdeps/unix/syscall-template.S:84 #1 0x7f7b4c4bc792 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f7b4c4756fc in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7
[krita] [Bug 379657] New: Creating new canvas makes Krita crash
https://bugs.kde.org/show_bug.cgi?id=379657 Bug ID: 379657 Summary: Creating new canvas makes Krita crash Product: krita Version: unspecified Platform: MS Windows OS: MS Windows Status: UNCONFIRMED Severity: critical Priority: NOR Component: OpenGL Canvas Assignee: krita-bugs-n...@kde.org Reporter: moonris...@outlook.com Target Milestone: --- Created attachment 105415 --> https://bugs.kde.org/attachment.cgi?id=105415&action=edit A backtrace of crashes I used various versions of Krita and this crash appeared on all of them (even on the newest version) for a year or more. If I have OpenGL enabled and try to create new Canvas, the program crashes. There isn't any problem when I open already existing file. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 371722] Let crash handler install debug packages
https://bugs.kde.org/show_bug.cgi?id=371722 --- Comment #6 from Harald Sitter --- Nope it's installing after you've authenticated. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 379639] Krita doesnt show changes until I minimize it or open a drop down menu
https://bugs.kde.org/show_bug.cgi?id=379639 --- Comment #3 from Boudewijn Rempt --- Yes, that's definitely the latest driver. I'll ping my contact at Intel... -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 379651] Vector issue on Krita 3.1.3.5
https://bugs.kde.org/show_bug.cgi?id=379651 --- Comment #3 from Boudewijn Rempt --- Comment on attachment 105413 --> https://bugs.kde.org/attachment.cgi?id=105413 New log (with Debug package) Hm no... That doesn't help either :-( -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 379481] Manually sort favorites
https://bugs.kde.org/show_bug.cgi?id=379481 Christoph Feck changed: What|Removed |Added CC||plasma-b...@kde.org Target Milestone|--- |1.0 Product|kmenuedit |plasmashell Assignee|unassigned-b...@kde.org |h...@kde.org Component|general |Application Menu (Kicker) Summary|would like ability to |Manually sort favorites |manually sort menu items| -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 379344] systemsettings segfaults when opening "Display and Monitor" with multiple monitors
https://bugs.kde.org/show_bug.cgi?id=379344 Christoph Feck changed: What|Removed |Added Resolution|BACKTRACE |UPSTREAM Status|NEEDSINFO |RESOLVED --- Comment #3 from Christoph Feck --- Yes, there is a recursion in QFontEngine. Please report this issue directly to Qt developers via https://bugreports.qt.io/ -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 379296] Reloading file hides the annotation toolbar
https://bugs.kde.org/show_bug.cgi?id=379296 Jonathan Verner changed: What|Removed |Added CC||jonathan.ver...@gmail.com --- Comment #3 from Jonathan Verner --- > Is it better to allow closing the document without hiding the toolbar, or is > it > better to make reload re-open the toolbar if it was open before? I would expect the toolbar to remain shown when closing a document... -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 379521] Kscreenlocker takes a full minute until it is responsive
https://bugs.kde.org/show_bug.cgi?id=379521 Christoph Feck changed: What|Removed |Added Status|NEEDSINFO |UNCONFIRMED Resolution|BACKTRACE |--- --- Comment #3 from Christoph Feck --- Thanks for the update; it looks like a Qt issue. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 371722] Let crash handler install debug packages
https://bugs.kde.org/show_bug.cgi?id=371722 --- Comment #7 from Pascal d'Hermilly --- (In reply to Harald Sitter from comment #6) > Nope it's installing after you've authenticated. But it didn't ask me to authenticate - even check for hidden windows in the taskbar. Eventually I clicked cancel and drkonqi crashed and also wanted to install debug packages for it. From there it could have been an endless loop, it seems ;-) -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 379549] kwin crash after klockscreen+monitor off
https://bugs.kde.org/show_bug.cgi?id=379549 Christoph Feck changed: What|Removed |Added Resolution|BACKTRACE |--- Status|NEEDSINFO |UNCONFIRMED --- Comment #3 from Christoph Feck --- Thanks for the update. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 378679] Intel modeseting drive intense tear with Skylake CPUs
https://bugs.kde.org/show_bug.cgi?id=378679 Christoph Feck changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |INVALID --- Comment #4 from Christoph Feck --- No response, changing status. If you have new information, please add it. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 379657] Creating new canvas makes Krita crash
https://bugs.kde.org/show_bug.cgi?id=379657 Boudewijn Rempt changed: What|Removed |Added Resolution|--- |UPSTREAM Status|UNCONFIRMED |RESOLVED CC||b...@valdyas.org --- Comment #1 from Boudewijn Rempt --- See https://docs.krita.org/KritaFAQ#Krita_starts_with_a_black_or_blank_canvas_and_nothing_changes_when_you_try_to_draw.2Fshows_a_black_or_blank_screen_on_my_Windows_system_with_an_Intel_GPU -- please update your intel display driver. You have version 10.18.10.3574, current versions start with 15. -- You are receiving this mail because: You are watching all bug changes.
[umbrello] [Bug 376305] Windows 7 Umbrello won't save model no mime types installed
https://bugs.kde.org/show_bug.cgi?id=376305 --- Comment #8 from dhlocker --- This helps very much. Many thanks. - Original Message - > From: "Ralf Habacker" > To: dhloc...@comcast.net > Sent: Tuesday, May 9, 2017 3:15:26 AM > Subject: [umbrello] [Bug 376305] Windows 7 Umbrello won't save model no mime > types installed > > https://bugs.kde.org/show_bug.cgi?id=376305 > > --- Comment #7 from Ralf Habacker --- > I added a related faq entry to > https://userbase.kde.org/Umbrello/FAQ#How_to_fix_the_error_message_.27There_was_a_problem_saving_file.27_.3F > > Thanks for pointing this out. Does this help you to fix your problem ? > > -- > You are receiving this mail because: > You are on the CC list for the bug. > You voted for the bug. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 379657] Creating new canvas makes Krita crash
https://bugs.kde.org/show_bug.cgi?id=379657 Boudewijn Rempt changed: What|Removed |Added Resolution|UPSTREAM|DUPLICATE --- Comment #2 from Boudewijn Rempt --- *** This bug has been marked as a duplicate of bug 360601 *** -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 360601] [INTEL] Canvas doesn't update but is not black either
https://bugs.kde.org/show_bug.cgi?id=360601 Boudewijn Rempt changed: What|Removed |Added CC||moonris...@outlook.com --- Comment #34 from Boudewijn Rempt --- *** Bug 379657 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 379650] Krita seriously crashes in latest stable version (WIN10 PRO)
https://bugs.kde.org/show_bug.cgi?id=379650 Boudewijn Rempt changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |DUPLICATE --- Comment #3 from Boudewijn Rempt --- I know now where to look in the crash log for the intel driver version. It's: ig7icd64.dll10.18.10.4425 igdusc64.dll10.18.10.4425 Current drivers start with 15; so this is very likely the problem from this faq: https://docs.krita.org/KritaFAQ#Krita_starts_with_a_black_or_blank_canvas_and_nothing_changes_when_you_try_to_draw.2Fshows_a_black_or_blank_screen_on_my_Windows_system_with_an_Intel_GPU Please try to update your driver to the latest version. *** This bug has been marked as a duplicate of bug 360601 *** -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 360601] [INTEL] Canvas doesn't update but is not black either
https://bugs.kde.org/show_bug.cgi?id=360601 Boudewijn Rempt changed: What|Removed |Added CC||moonris...@outlook.com CC||garb...@gmail.com --- Comment #34 from Boudewijn Rempt --- *** Bug 379657 has been marked as a duplicate of this bug. *** --- Comment #35 from Boudewijn Rempt --- *** Bug 379650 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 379646] crash Toggle What's Interesting
https://bugs.kde.org/show_bug.cgi?id=379646 --- Comment #3 from Jasem Mutlaq --- Can you please re-download the installer and try again? -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 379638] Icon request: equal, unequal and swap
https://bugs.kde.org/show_bug.cgi?id=379638 --- Comment #1 from Jens Reuterberg --- For clarity of the icons - I am not a big Krusader user myself so just want to ask some (perhaps obvious) questions concerning the usage so we don't make icons that are more confusing than anything else. Show Equal Files - would an equal sign be clear enough or would for example an "equal sign within a document" make more sense (or less)? Show Unequal Files - should share some kind of similarity with the Equal Files icon so that both are "connected" in my logic (which is why say a document or file symbol with an equal/unequal sign in it would make more sense in my mind). But maybe that would be muddling the understanding of it. Swap - since that might look like a "reload" icon would say a line in the middle or something that represent the two panels make sense? Am I way of base in this thinking? On Mon, May 8, 2017 at 9:33 , Alex Bikadorov wrote: > https://bugs.kde.org/show_bug.cgi?id=379638 > > Bug ID: 379638 >Summary: Icon request: equal, unequal and swap >Product: Breeze >Version: unspecified > Platform: Other > OS: Linux > Status: UNCONFIRMED > Severity: normal > Priority: NOR > Component: Icons > Assignee: visual-des...@kde.org > Reporter: alex.bikado...@kdemail.net > CC: kain...@gmail.com > Target Milestone: --- > > The Krusader project needs three icons: > * equal: a simple "=" sign as icon, monochrome colours > * unequal: the mathematical unequal sign (equal combined with a > slash), > monochrome and additionally in red if this is not too much work > * swap (sides): a double arrow "<->", monochrome > > Background/Usage: Krusader file synchronizing feature > * equal: show identical files > * unequal: show differing files > * swap: swap the panel sides > > All of them might be useful for other applications. > > Thank you! > > -- > You are receiving this mail because: > You are the assignee for the bug. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 379549] kwin crash after klockscreen+monitor off
https://bugs.kde.org/show_bug.cgi?id=379549 --- Comment #4 from Christian Höne --- additional info: - crash time is not necessarily at where you unlock. - hard to say how long monitor has to be off, but it is about 90% probability that this crash happens if monitor is off for more than 30min, if you turn off monitor only for a short time it doesn't occur. - crash happens not only on one machine. what is in common: openSUSE 42.2, nvidia graphics card with proprietary driver and a monitor connected via display port. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 379638] Icon request: equal, unequal and swap
https://bugs.kde.org/show_bug.cgi?id=379638 --- Comment #2 from andreas --- please add an screenshot and maybe a icon name recommandation thanks -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 379639] Krita doesnt show changes until I minimize it or open a drop down menu
https://bugs.kde.org/show_bug.cgi?id=379639 --- Comment #4 from Boudewijn Rempt --- Which tool did you use to update? I'm trying to update my win10 laptop with a HD4000, but the installer keeps installing a 10.x driver. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 379650] Krita seriously crashes in latest stable version (WIN10 PRO)
https://bugs.kde.org/show_bug.cgi?id=379650 --- Comment #4 from MichalG --- Well... I just can't update driver other than one that is latest. It said I have the newest driver. What can I do else? The screenshot is here: https://imagebin.ca/v/3LrdLaqNvSez -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 379650] Krita seriously crashes in latest stable version (WIN10 PRO)
https://bugs.kde.org/show_bug.cgi?id=379650 --- Comment #5 from MichalG --- OK, I will try manually downloaded driver and reply here later... -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 379650] Krita seriously crashes in latest stable version (WIN10 PRO)
https://bugs.kde.org/show_bug.cgi?id=379650 --- Comment #6 from Boudewijn Rempt --- Um, that screenshot shows that it offers to download 15.33 for you? -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 379650] Krita seriously crashes in latest stable version (WIN10 PRO)
https://bugs.kde.org/show_bug.cgi?id=379650 --- Comment #7 from Boudewijn Rempt --- I'm actually going through the same utility and the same process on my old hd4000 laptop; that had the same driver you had, though for me, on that old thinkpad, no crashes were happening... -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 379650] Krita seriously crashes in latest stable version (WIN10 PRO)
https://bugs.kde.org/show_bug.cgi?id=379650 --- Comment #8 from Boudewijn Rempt --- Okay, even weirder... That 15.33 installer actually seems to install the 10.18 driver! I don't get Intel. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 379658] New: Widget location in panel not saving on logout
https://bugs.kde.org/show_bug.cgi?id=379658 Bug ID: 379658 Summary: Widget location in panel not saving on logout Product: plasmashell Version: 5.9.5 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Panel Assignee: plasma-b...@kde.org Reporter: joshuadodd1...@gmail.com Target Milestone: 1.0 Created attachment 105417 --> https://bugs.kde.org/attachment.cgi?id=105417&action=edit Screenshot of bug Hello, I am using global menu on the left of the panel and I have moved the system tray, time and show desktop widgets to the very right of the panel. After I logout and log back in they appear next to the global menu again. This bug is really annoying because I have to keep changing their position every time I login. Is anyone else experiencing this issue? Thank you -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kpackage] [Bug 367923] kpackagetool5 does not create appdata files for types like "Plasma/Wallpaper" or "Plasma/LookAndFeel", but shows error
https://bugs.kde.org/show_bug.cgi?id=367923 Fabian Vogt changed: What|Removed |Added CC||fab...@ritter-vogt.de --- Comment #4 from Fabian Vogt --- This results in a build cycle in the openSUSE packages as plasma-workspace requires kwin during build, which requires breeze, which in turn requires plasma-workspace during build to generate the metainfo. A workaround is to break the breeze/kwin runtime dependency and build plasma-workspace without breeze installed, but that should not be necessary. -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 379646] crash Toggle What's Interesting
https://bugs.kde.org/show_bug.cgi?id=379646 --- Comment #4 from Tommy LKW --- (In reply to Jasem Mutlaq from comment #3) > Can you please re-download the installer and try again? Cant download the windows installer file. "Error displaying the error page" -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 378216] Kmail / Kontact crash when moving & copying mail folders
https://bugs.kde.org/show_bug.cgi?id=378216 --- Comment #2 from Michel --- HI Fixed after the command 'akonadictl fsck' Sorry to spam and borring. Thanks for your support -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 371722] Let crash handler install debug packages
https://bugs.kde.org/show_bug.cgi?id=371722 --- Comment #8 from Harald Sitter --- Oh, sorry, I didn't read your comment properly. Nevermind then :S -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 379646] crash Toggle What's Interesting
https://bugs.kde.org/show_bug.cgi?id=379646 --- Comment #5 from Jasem Mutlaq --- Sorry about that, try again. The link was updated. -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 379646] crash Toggle What's Interesting
https://bugs.kde.org/show_bug.cgi?id=379646 --- Comment #6 from Tommy LKW --- (In reply to Jasem Mutlaq from comment #5) > Sorry about that, try again. The link was updated. Yes. Downloading. Thanks a lot -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 379646] crash Toggle What's Interesting
https://bugs.kde.org/show_bug.cgi?id=379646 --- Comment #7 from Tommy LKW --- It works. Thank you. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 379521] Kscreenlocker takes a full minute until it is responsive
https://bugs.kde.org/show_bug.cgi?id=379521 --- Comment #4 from spa...@modanese.net --- @Christoph Feck So should I go and file a bug on the Qt tracker? Right now it happens only with kscreenlocker though. I'll keep an eye open, see if any other Qt programs show similar behavior. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 371722] Let crash handler install debug packages
https://bugs.kde.org/show_bug.cgi?id=371722 --- Comment #9 from Harald Sitter --- if you could run the installer manually on a terminal and paste the output here that'd be very handy drkonqi-pk-debug-installer /usr/bin/plasmashell -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 379659] New: could not install new data in Kstars 2.7.7
https://bugs.kde.org/show_bug.cgi?id=379659 Bug ID: 379659 Summary: could not install new data in Kstars 2.7.7 Product: kstars Version: unspecified Platform: Other OS: MS Windows Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: mutla...@ikarustech.com Reporter: tlk...@yahoo.com Target Milestone: --- Latest Kstars 2.7.7 could not install data : File not found 1. Sharpless HII region cat 2. Hickson Compact Groups 3. NGC images displayed. 4. IC images displayed Please help... -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 370028] Reduce the number of compiler warnings on MIPS platforms
https://bugs.kde.org/show_bug.cgi?id=370028 Tamara Vlahovic changed: What|Removed |Added CC||tamara.vlaho...@imgtec.com --- Comment #30 from Tamara Vlahovic --- Created attachment 105418 --> https://bugs.kde.org/attachment.cgi?id=105418&action=edit Patch for mc_main.c This patch solves "cast-align" warnings in mecheck/mc_main.c In a lot of places in this file after checking for alignment UChar array pointer vabits8 in structure SecMap is casted in UShort pointer. To avoid this cast SecMap can be transformed to an union of UChar vabits8 array and UShort vabits16 array with same byte count. In two other places ASSUME_ALIGNED can be used. -- You are receiving this mail because: You are watching all bug changes.
[simon] [Bug 356452] Simon can't add Arabic or Hebrew words
https://bugs.kde.org/show_bug.cgi?id=356452
--- Comment #10 from Mario Fux ---
Ok now back to this bug. Christopher, I can add the word () bug get a
sphinxtrain error as well. The one below:
You wrote this:
an error message appears:
Kmeans_init.exe has stopped working
Does this mean that "Kmeans_init.exe has stopped working" is your error
message?
Thanks for a quick feedback
Mario
/usr/bin/sphinxtrain -t default{201cb64d-4f61-49b4-9ed2-b3ddb536f6f0} setup
Sphinxtrain path: /usr/lib/sphinxtrain
Sphinxtrain binaries path: /usr/lib/sphinxtrain
Setting up the database default{201cb64d-4f61-49b4-9ed2-b3ddb536f6f0}
/usr/bin/sphinxtrain run
Sphinxtrain path: /usr/lib/sphinxtrain
Sphinxtrain binaries path: /usr/lib/sphinxtrain
Running the training
Configuration (e.g. etc/sphinx_train.cfg) not defined
Compilation failed in require at
/usr/lib/sphinxtrain/scripts/000.comp_feat/slave_feat.pl line 51.
BEGIN failed--compilation aborted at
/usr/lib/sphinxtrain/scripts/000.comp_feat/slave_feat.pl line 51.
--
You are receiving this mail because:
You are watching all bug changes.
[cantor] [Bug 348128] The sage backend does not starts with sage 6.7
https://bugs.kde.org/show_bug.cgi?id=348128 --- Comment #26 from jackdyson31 --- @christopher this might be useful (and a lot better): https://github.com/sagemathinc/smc/tree/master/src/dev/docker regards, Jack -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 379646] crash Toggle What's Interesting
https://bugs.kde.org/show_bug.cgi?id=379646 Jasem Mutlaq changed: What|Removed |Added Resolution|--- |FIXED Status|CONFIRMED |RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 379638] Icon request: equal, unequal and swap
https://bugs.kde.org/show_bug.cgi?id=379638 --- Comment #3 from Alex Bikadorov --- Created attachment 105419 --> https://bugs.kde.org/attachment.cgi?id=105419&action=edit Synchronizer in Krusader -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 379638] Icon request: equal, unequal and swap
https://bugs.kde.org/show_bug.cgi?id=379638 --- Comment #4 from Alex Bikadorov --- Created attachment 105420 --> https://bugs.kde.org/attachment.cgi?id=105420&action=edit Krusader main window -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 379638] Icon request: equal, unequal and swap
https://bugs.kde.org/show_bug.cgi?id=379638 --- Comment #5 from Alex Bikadorov --- No problem. Here are more information and screenshots. Should have provided them earlier. "Synchronizer" is a tool in Krusader with an own window. It can compare content of folders and synchronize them. See first screenshot, the icons in question are marked. >Show Equal Files - would an equal sign be clear enough or would for >example an "equal sign within a document" make more sense (or less)? I definitely need an icon with only the equal sign (for another use case: show same folder in both panels; see second screenshot) and it would also better fit here to other icons next to it (see first screenshot). >Show Unequal Files - should share some kind of similarity with the >Equal Files icon so that both are "connected" in my logic (which is why >say a document or file symbol with an equal/unequal sign in it would >make more sense in my mind). But maybe that would be muddling the >understanding of it. Yes, there are logically connected - but also with other icons: arrow-right, arrow-left and trash (= show deleted files). Again: please see screenshot. >Swap - since that might look like a "reload" icon would say a line in >the middle or something that represent the two panels make sense? Yes. Visualizing the panels would fit here. But maybe its better to make it more general, so it can be used in other cases/applications. I don't want you guys to make icons for every single use case. Thanks again. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 379638] Icon request: equal, unequal and swap
https://bugs.kde.org/show_bug.cgi?id=379638 --- Comment #6 from Alex Bikadorov --- oh, icon name recommendation: - "equals" or "document-equals" - equivalent "unequals" or "document-unequals" - "swap" or "swap-sides" or "swap-panels" ? Not sure. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 379650] Krita seriously crashes in latest stable version (WIN10 PRO)
https://bugs.kde.org/show_bug.cgi?id=379650 --- Comment #9 from MichalG --- So... Drivers are updated (even manually), system was restarted, and then... Krita hangs-up after choosing selected canvas (when it is about to start after loading). Krita hangs-up no matter OpenGL is turned on or off. :( Bad luck, I'm outta here... P.S. Fortunately there are another machine with GTX1060 which 'likes' KRITA. :) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 379481] Manually sort favorites
https://bugs.kde.org/show_bug.cgi?id=379481 Eike Hein changed: What|Removed |Added Resolution|--- |WORKSFORME Status|UNCONFIRMED |RESOLVED --- Comment #3 from Eike Hein --- Favorites can be moved around by drag and drop. -- You are receiving this mail because: You are watching all bug changes.
[Heaptrack] [Bug 379660] New: Collapse template arguments in flamegraph
https://bugs.kde.org/show_bug.cgi?id=379660 Bug ID: 379660 Summary: Collapse template arguments in flamegraph Product: Heaptrack Version: unspecified Platform: Compiled Sources OS: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: general Assignee: m...@milianw.de Reporter: mcgu...@kde.org Target Milestone: --- When running heaptrack on something that uses a lot of templates, like std::string, the flamegraph becomes unreadable because all the template arguments are obscuring the function name. Some suggestions: - Elide the function name in the middle instead of cutting it off a the end - Collapse long tempate arguments: Instead of "std::map, blub blub blub>::operator[](std::string &const)", say just "std::map<...>::operator[](std::string &const)" -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 379661] New: Dolhinc crasheslisitng a DFS folder
https://bugs.kde.org/show_bug.cgi?id=379661 Bug ID: 379661 Summary: Dolhinc crasheslisitng a DFS folder Product: dolphin Version: 15.12.3 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: luis.panad...@gmail.com Target Milestone: --- Application: dolphin (15.12.3) Qt Version: 5.5.1 Operating System: Linux 4.4.0-75-generic x86_64 Distribution: Ubuntu 16.04.2 LTS -- Information about the crash: - What I was doing when the application crashed: Trying to open with Dolphin a DFS folder with smb:\\ . Using mount.cifs over the same folder don't give any error and allow to Dolphin navigate on the same folder. The crash can be reproduced every time. -- Backtrace: Application: Dolphin (dolphin), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f18958718c0 (LWP 11965))] Thread 2 (Thread 0x7f1888ed1700 (LWP 11967)): #0 0x7f18a8694b5d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7f189ee8838c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f189ee8849c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f18a349d7eb in QEventDispatcherGlib::processEvents (this=0x7f18840008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420 #4 0x7f18a3444b4a in QEventLoop::exec (this=this@entry=0x7f1888ed0d00, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #5 0x7f18a3261834 in QThread::exec (this=) at thread/qthread.cpp:503 #6 0x7f18a32667be in QThreadPrivate::start (arg=0x1292c40) at thread/qthread_unix.cpp:331 #7 0x7f189fa146ba in start_thread (arg=0x7f1888ed1700) at pthread_create.c:333 #8 0x7f18a86a082d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 1 (Thread 0x7f18958718c0 (LWP 11965)): [KCrash Handler] #6 0x7f18a3457d25 in QMetaObject::invokeMethod (obj=obj@entry=0x1511a80, member=member@entry=0x7f18a6ca87e6 "next", type=178249072, type@entry=Qt::QueuedConnection, ret=..., val0=..., val1=..., val2=..., val3=..., val4=..., val5=..., val6=..., val7=..., val8=..., val9=...) at kernel/qmetaobject.cpp:1464 #7 0x7f18a6c99b99 in QMetaObject::invokeMethod (val9=..., val8=..., val7=..., val6=..., val5=..., val4=..., val3=..., val2=..., val1=..., val0=..., type=Qt::QueuedConnection, member=0x7f18a6ca87e6 "next", obj=0x1511a80) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qobjectdefs.h:409 #8 KDialogJobUiDelegate::Private::next (this=0x1511a80) at ../../src/kdialogjobuidelegate.cpp:82 #9 0x7f18a3476c01 in QObject::event (this=0x1511a80, e=) at kernel/qobject.cpp:1239 #10 0x7f18a3f4a05c in QApplicationPrivate::notify_helper (this=this@entry=0xcf63e0, receiver=receiver@entry=0x1511a80, e=e@entry=0x13b38c0) at kernel/qapplication.cpp:3716 #11 0x7f18a3f4f516 in QApplication::notify (this=0x7fff0a9fe750, receiver=0x1511a80, e=0x13b38c0) at kernel/qapplication.cpp:3499 #12 0x7f18a344738b in QCoreApplication::notifyInternal (this=0x7fff0a9fe750, receiver=0x1511a80, event=event@entry=0x13b38c0) at kernel/qcoreapplication.cpp:965 #13 0x7f18a3449786 in QCoreApplication::sendEvent (event=0x13b38c0, receiver=) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:224 #14 QCoreApplicationPrivate::sendPostedEvents (receiver=receiver@entry=0x0, event_type=event_type@entry=0, data=0xcf4870) at kernel/qcoreapplication.cpp:1593 #15 0x7f18a3449c68 in QCoreApplication::sendPostedEvents (receiver=receiver@entry=0x0, event_type=event_type@entry=0) at kernel/qcoreapplication.cpp:1451 #16 0x7f18a349d3c3 in postEventSourceDispatch (s=0xd311e0) at kernel/qeventdispatcher_glib.cpp:271 #17 0x7f189ee88197 in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #18 0x7f189ee883f0 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #19 0x7f189ee8849c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #20 0x7f18a349d7cf in QEventDispatcherGlib::processEvents (this=0xd3b6f0, flags=...) at kernel/qeventdispatcher_glib.cpp:418 #21 0x7f18a3444b4a in QEventLoop::exec (this=this@entry=0x7fff0a9fe620, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #22 0x7f18a344cbec in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1229 #23 0x7f18a3990bfc in QGuiApplication::exec () at kernel/qguiapplication.cpp:1542 #24 0x7f18a3f46495 in QApplication::exec () at kernel/qapplication.cpp:2976 #25 0x7f18a89c0e2b in kdemain (argc=1, argv=) at /build/dolphin-HvGmRr/dolphin-15.12.3/src/main.cpp:150 #26 0x7f18a85ba830 in __libc_start_main (main=0x400710 , argc=1, argv=0x7fff0a9fe8d8, init=, fini=, rtld_fini=, stack_end=0x7fff0a9fe8c8) at ../csu/libc-start.c:291 #27 0x
[kmail2] [Bug 378526] KMail 5.4.3: Attachment displayed with wrong filename
https://bugs.kde.org/show_bug.cgi?id=378526 Laurent Montel changed: What|Removed |Added Version Fixed In||5.5.2 Latest Commit||https://commits.kde.org/mes ||sagelib/cbbe13d470caa4b2050 ||5009f27888fcde6cd22b5 Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #1 from Laurent Montel --- Git commit cbbe13d470caa4b20505009f27888fcde6cd22b5 by Montel Laurent. Committed on 09/05/2017 at 14:05. Pushed by mlaurent into branch 'Applications/17.04'. Fix Bug 378526 - KMail 5.4.3: Attachment displayed with wrong filename FIXED-IN: 5.5.2 M +1-1messageviewer/src/viewer/viewer_p.cpp https://commits.kde.org/messagelib/cbbe13d470caa4b20505009f27888fcde6cd22b5 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 379661] Dolphin crashes lisitng a DFS folder --> smb:\\server\dfs\
https://bugs.kde.org/show_bug.cgi?id=379661 Luis changed: What|Removed |Added Summary|Dolhinc crasheslisitng a|Dolphin crashes lisitng a |DFS folder |DFS folder --> ||smb:\\server\dfs\ -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 357288] Setting "Screen Energy Saving" in "Energy Saving" config has no effect
https://bugs.kde.org/show_bug.cgi?id=357288 Raman Gupta changed: What|Removed |Added Version|5.8.4 |5.9.4 --- Comment #10 from Raman Gupta --- Now on Plasma 5.9.4, I can see in the battery manager applet that Power Management is suppressed by a tab in google-chrome-stable. The tab doesn't exist, and Chrome isn't even running (confirmed with ps as root), but hey, at least now there is some information that explains why the energy saving isn't working. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kpackage] [Bug 367923] kpackagetool5 does not create appdata files for types like "Plasma/Wallpaper" or "Plasma/LookAndFeel", but shows error
https://bugs.kde.org/show_bug.cgi?id=367923 Fabian Vogt changed: What|Removed |Added Severity|normal |major --- Comment #5 from Fabian Vogt --- Oh, and plasma-workspace itself needs plasma-workspace installed during build, due to: [ 91s] CMake Warning at /usr/lib64/cmake/KF5Package/KF5PackageMacros.cmake:58 (message): [ 91s] warnings during generation of metainfo for org.kde.breeze.desktop: Package [ 91s] type "Plasma/LookAndFeel" not found [ 91s] [ 91s] Call Stack (most recent call first): [ 91s] /usr/lib64/cmake/KF5Plasma/KF5PlasmaMacros.cmake:33 (kpackage_install_package) [ 91s] CMakeLists.txt:115 (plasma_install_package) -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 379344] systemsettings segfaults when opening "Display and Monitor" with multiple monitors
https://bugs.kde.org/show_bug.cgi?id=379344 --- Comment #4 from NOGISAKA Sadata --- Thank you. I reported this issue by https://bugreports.qt.io/browse/QTBUG-60697. -- You are receiving this mail because: You are watching all bug changes.
[ktorrent] [Bug 327771] Queue Manager: New Torrents added to the top
https://bugs.kde.org/show_bug.cgi?id=327771 Alejandro Villar changed: What|Removed |Added CC||alx5...@alx5000.net -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 379662] New: Kontact 5.5.0 does not respect KWin window placement
https://bugs.kde.org/show_bug.cgi?id=379662 Bug ID: 379662 Summary: Kontact 5.5.0 does not respect KWin window placement Product: kontact Version: GIT (master) Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: till2.schae...@uni-dortmund.de Target Milestone: --- Kontact seems to do some magic regarding his initial window placement. Typically KWin remembers the last size and position of a window and restores it, when it is opened a second time. This is not the case for kontact. Furthermore, windows rules that are applied initially for the size or position of Kontact do not have any effect (using rule mode force does have). Thus, I guess Kontact does some special handling about the size and position of the window and does some magic about its placement on its own (and bypass KWin rules by doing so). This is also problematic if one is working with dual monitor setup as Kontact is always started on the left screen ---regardless of the primary screen setting or the active screen---. If the left screen then has some horizontal offset, the position of Kontact may be even outside of the visible area! Example: I have to monitors and can only move Kontact to the visible area by using a shortcut. It is always started on screen HDMI1. As you can see from the screen configuration below HDMI1 has an offset of 416 pixels, which is not respected by the Kontact window placement. Screens: - HDMI1 connected 1280x1024+0+416 (normal left inverted right x axis y axis) 380mm x 300mm - DP2 connected primary 2560x1440+1280+0 (normal left inverted right x axis y axis) 600mm x 340mm Proposal: Do not set the size and position of Kontact after initialization. This breaks the placement rules of KWin. -- You are receiving this mail because: You are watching all bug changes.
