[plasmashell] [Bug 368818] Panel on wrong position on wrong screen
https://bugs.kde.org/show_bug.cgi?id=368818 --- Comment #7 from Adam--- Created attachment 101492 --> https://bugs.kde.org/attachment.cgi?id=101492=edit a screenshot demonstrating the problem (virtual areas in red) I think this is related: when i open a picture in dolphin, the gwenview window is too big. i can't see the title bar on the small screen (see attachment). I can move it with alt and when maximizing the correct size is used. maximizing works normally. the attached screen layout was made automatically when attaching the cable (if it matters: same apple macbook air with thunderbolt / mini display port and intel on board gpu) -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 355540] Tooltips color wrong in gtk applications
https://bugs.kde.org/show_bug.cgi?id=355540 Adamchanged: What|Removed |Added CC||k...@xibo.at --- Comment #25 from Adam --- I can confirm on Plasma 5.8. It was working on Gimp, but not on Inkscape. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 343235] SFTP: Dolphin is unresponsive when copying file via directory browse
https://bugs.kde.org/show_bug.cgi?id=343235 Adamchanged: What|Removed |Added CC||k...@xibo.at -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 344432] SFTP: When attempting to view kdeconnect in dolphin it crashes
https://bugs.kde.org/show_bug.cgi?id=344432 Adamchanged: What|Removed |Added CC||k...@xibo.at -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 368818] Panel on wrong position on wrong screen
https://bugs.kde.org/show_bug.cgi?id=368818 --- Comment #6 from Adam--- Created attachment 101369 --> https://bugs.kde.org/attachment.cgi?id=101369=edit in addition, the panel is missing after i unplug the second monitor i can get it back by rotating the the primary display (laptop screen) in "system settings" -> "display and monitor" by 90 degrees and back. if it matters, my laptop is a macbook air with intel gpu and thunderbolt (Mini DisplayPort). -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 368818] Panel on wrong position on wrong screen
https://bugs.kde.org/show_bug.cgi?id=368818 Adamchanged: What|Removed |Added CC||k...@xibo.at --- Comment #5 from Adam --- Created attachment 101368 --> https://bugs.kde.org/attachment.cgi?id=101368=edit same issue. red areas are virtual i can confirm on kde 5.7.95 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 355642] Desktop Settings closes when changing Layout and pressing Apply
https://bugs.kde.org/show_bug.cgi?id=355642 Adamchanged: What|Removed |Added CC||k...@xibo.at --- Comment #1 from Adam --- also happens in 5.8 beta. -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 366299] System setting "Energy Saving" window is too large for a standard laptop screen
https://bugs.kde.org/show_bug.cgi?id=366299 Adamchanged: What|Removed |Added CC||k...@xibo.at -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 357651] No error message if file pasting failed
https://bugs.kde.org/show_bug.cgi?id=357651 Adamchanged: What|Removed |Added CC||k...@xibo.at --- Comment #1 from Adam --- I just encountered the same issue in Dolphin 16.08.0 (KDE Frameworks 5.26.0, openSUSE Leap 42.2 beta), when dragging files in splitview from the hard disk to a pen drive. I was puzzled because just the second before I moved a smaller file and it worked. If that were not the case, my work would be stalled. Would be cool if this is fixed for 5.8 LTS, because i really like the new version :D (coming from mint/kde 4.14) -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 368729] New: Segfault when launching krunner
https://bugs.kde.org/show_bug.cgi?id=368729 Bug ID: 368729 Summary: Segfault when launching krunner Product: krunner Version: 5.6.5 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general Assignee: k...@privat.broulik.de Reporter: adambo...@gmail.com ubuntu 16.04, kde plasma 5.6.5, kde frameworks 5.23.0, qt 5.5.1 This is a pretty new installation. I'm using some other themes and stuff, but really not much changed. Boot, open terminal, run krunner. It segfaults. Reproducible: Always Steps to Reproduce: $ krunner # nothing happened here $ krunner KCrash: crashing... crashRecursionCounter = 2 KCrash: Application Name = krunner path = /usr/bin pid = 4925 KCrash: Arguments: /usr/bin/krunner Segmentation fault (core dumped) $ killall -9 krunner $ krunner "file:///usr/share/plasma/look-and-feel/org.kde.breeze.desktop/contents/runcommand/RunCommand.qml" "Error loading QML file.\n126: Type Milou.ResultsView unavailable\n79: Type ResultDelegate unavailable\n144: Cannot assign to non-existent property \"separatorVisible\"\n" Actual Results: Segfault Expected Results: Run krunner -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 196998] Konsole should reflow the text when resizing
https://bugs.kde.org/show_bug.cgi?id=196998 Alexander Adamchanged: What|Removed |Added CC||bugs.kde.1...@antifarben.de -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 360072] Option "manage profiles" doesn't work, doesn't do anything
https://bugs.kde.org/show_bug.cgi?id=360072 Adamchanged: What|Removed |Added CC||adamwar.t...@seznam.cz -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 364442] New: plasma crash on wake
https://bugs.kde.org/show_bug.cgi?id=364442 Bug ID: 364442 Summary: plasma crash on wake Product: plasmashell Version: 5.5.5 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: adami...@gmail.com CC: bhus...@gmail.com, plasma-b...@kde.org Application: plasmashell (5.5.5) Qt Version: 5.5.1 Operating System: Linux 4.4.0-24-generic x86_64 Distribution: Ubuntu 16.04 LTS -- Information about the crash: - What I was doing when the application crashed: I am forced to close the lid on this laptop if I wake it up with the mouse, because the keybord stops working at the login screen. The crash can be reproduced sometimes. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f80a9d188c0 (LWP 1698))] Thread 9 (Thread 0x7f8094e38700 (LWP 1705)): #0 0x7f80a43bbe8d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7f80a84cac62 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 #2 0x7f80a84cc8d7 in xcb_wait_for_event () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 #3 0x7f8096fb2629 in QXcbEventReader::run (this=0x15f4170) at qxcbconnection.cpp:1253 #4 0x7f80a4abe84e in QThreadPrivate::start (arg=0x15f4170) at thread/qthread_unix.cpp:331 #5 0x7f80a3b906fa in start_thread (arg=0x7f8094e38700) at pthread_create.c:333 #6 0x7f80a43c7b5d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 8 (Thread 0x7f808e5f8700 (LWP 1747)): #0 0x7f80a4ab69aa in QBasicAtomicOps<8>::testAndSetRelaxed(currentValue=, newValue=0x1, expectedValue=0x0, _q_value=@0x16c4ea8: 0x1) at ../../include/QtCore/../../src/corelib/arch/qatomic_x86.h:259 #1 QGenericAtomicOps >::testAndSetAcquire (currentValue=, newValue=, expectedValue=0x0, _q_value=@0x16c4ea8: 0x1) at ../../include/QtCore/../../src/corelib/thread/qgenericatomic.h:166 #2 QBasicAtomicPointer::testAndSetAcquire (currentValue=, newValue=, expectedValue=0x0, this=0x16c4ea8, this@entry=0x1) at ../../include/QtCore/../../src/corelib/thread/qbasicatomic.h:276 #3 QBasicMutex::fastTryLock (current=, this=0x16c4ea8, this@entry=0x1) at thread/qmutex.h:82 #4 QMutex::lock (this=this@entry=0x16c4ea8) at thread/qmutex.cpp:212 #5 0x7f80a4cf501f in QMutexLocker::QMutexLocker (m=0x16c4ea8, this=) at ../../include/QtCore/../../src/corelib/thread/qmutex.h:128 #6 QThreadData::canWaitLocked (this=0x16c4e80) at ../../include/QtCore/5.5.1/QtCore/private/../../../../../src/corelib/thread/qthread_p.h:240 #7 postEventSourcePrepare (s=0x7f80880012d0, timeout=0x7f808e5f7b24) at kernel/qeventdispatcher_glib.cpp:254 #8 0x7f80a10e28ad in g_main_context_prepare () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #9 0x7f80a10e324b in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #10 0x7f80a10e342c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #11 0x7f80a4cf5a9b in QEventDispatcherGlib::processEvents (this=0x7f80880008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420 #12 0x7f80a4c9cdea in QEventLoop::exec (this=this@entry=0x7f808e5f7ce0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #13 0x7f80a4ab98a4 in QThread::exec (this=this@entry=0x16b1970) at thread/qthread.cpp:503 #14 0x7f80a73823c5 in QQmlThreadPrivate::run (this=0x16b1970) at qml/ftw/qqmlthread.cpp:141 #15 0x7f80a4abe84e in QThreadPrivate::start (arg=0x16b1970) at thread/qthread_unix.cpp:331 #16 0x7f80a3b906fa in start_thread (arg=0x7f808e5f8700) at pthread_create.c:333 #17 0x7f80a43c7b5d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 7 (Thread 0x7f8083a30700 (LWP 1749)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f808797b213 in ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #2 0x7f808797a937 in ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #3 0x7f80a3b906fa in start_thread (arg=0x7f8083a30700) at pthread_create.c:333 #4 0x7f80a43c7b5d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 6 (Thread 0x7f807f108700 (LWP 1750)): #0 0x7f80a10e2750 in g_main_context_prepare () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7f80a10e324b in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f80a10e342c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f80a4cf5a9b in QEventDispatcherGlib::processEvents (this=0x7f80780008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420 #4 0x7f80a4c9cdea in QEventLoop::exec (this=this@entry=0x7f807f107ce0, flags=...,
[krita] [Bug 358350] Version 2.9.9 in OS X 10.9.5 and MS Windows 7 crash opening JPEG file from scanned image.
https://bugs.kde.org/show_bug.cgi?id=358350 --- Comment #6 from Adam--- Created attachment 99254 --> https://bugs.kde.org/attachment.cgi?id=99254=edit image from a phone camera that crashes krita on mac os -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 358350] Version 2.9.9 in OS X 10.9.5 and MS Windows 7 crash opening JPEG file from scanned image.
https://bugs.kde.org/show_bug.cgi?id=358350 --- Comment #5 from Adam--- Created attachment 99253 --> https://bugs.kde.org/attachment.cgi?id=99253=edit stack trace -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 358350] Version 2.9.9 in OS X 10.9.5 and MS Windows 7 crash opening JPEG file from scanned image.
https://bugs.kde.org/show_bug.cgi?id=358350 Adamchanged: What|Removed |Added CC||k...@xibo.at --- Comment #4 from Adam --- i have the same problem on osx 10.11.5. the attached files open/crash as described. I'll attach a stack trace and another jpeg that doesn't work (came from a phone camera). -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 346961] Multi Monitor configuration lost on reboot, must reconfigure after startup
https://bugs.kde.org/show_bug.cgi?id=346961 --- Comment #58 from Adam--- Ok, not sure if this offers any clues, or if it's something unrelated. Logged in this morning and the screen layout had been reset. After trying a few times ( normally logging out/back in fixes it now the kscreen file is ro ) it still wasn't working, so I looked in .local/share/kscreen/ and found that it had got around the ro file thing by creating a new file dated yesterday - I deleted that and things were back to normal when I logged back in. That leads me to a train of thought. Maybe, sometimes during the boot process, kscreen fails to read the kscreen directory. This has more weight because my entire /home is a luks partition mounted with pam_mount - so could it be that there's a timing issue here? pam_mount hasn't completed before kscreen tries to initialise? Is there an easy way I can test this theory ( put a delay in somewhere, force kscreen to rely on pam_mount completing, or some such? ) -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 346961] Multi Monitor configuration lost on reboot, must reconfigure after startup
https://bugs.kde.org/show_bug.cgi?id=346961 --- Comment #54 from Adam--- (In reply to Mika Norén from comment #52) > Here's an ugly workaround to use meanwhile: The workaround didn't work for me. I'm using the KDE Neon unstable archives now and the issue still exists - doesn't seem as bad as it used to be for me in that much of the time the configuration remains correct but every now and again it's still lost. This morning I logged in and the screens were mirrored ( rather than extended over both. ) Rebooted and it was fine again. This is with the kscreen config file set to read only. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 362604] New: Kate on Windows doesn't recognize UTF-8 encoding, even using BOM
https://bugs.kde.org/show_bug.cgi?id=362604 Bug ID: 362604 Summary: Kate on Windows doesn't recognize UTF-8 encoding, even using BOM Product: kate Version: unspecified Platform: MS Windows OS: MS Windows Status: UNCONFIRMED Severity: normal Priority: NOR Component: encoding Assignee: kwrite-bugs-n...@kde.org Reporter: cristian.a...@gmx.net Installed Kate version 16.07.70 on Windows 10 and opened an UTF-8 encoded text file. File was showing the pretty UTF-8 characters in ISO-8859-1 encoding. Set the fallback encoding to UTF-8. Reopened the file, same story. Clicked on adding the UTF-8 BOM to the file. Reopened the file, same story. UTF-8 files are default also on Windows. I've created that text file using Notepad++. I was at least expecting BOM to work. It didn't. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 346961] Multi Monitor configuration lost on reboot, must reconfigure after startup
https://bugs.kde.org/show_bug.cgi?id=346961 Adamchanged: What|Removed |Added CC||sidepip...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 353977] Krunner crashes when connecting/disconnecting second monitor.
https://bugs.kde.org/show_bug.cgi?id=353977 Alexander Adamchanged: What|Removed |Added CC||bugs.kde.1...@antifarben.de -- You are receiving this mail because: You are watching all bug changes.