[krita] [Bug 408041] New: Brush freezes when attempting to paint.
https://bugs.kde.org/show_bug.cgi?id=408041 Bug ID: 408041 Summary: Brush freezes when attempting to paint. Product: krita Version: 4.1.7 Platform: Windows CE OS: Windows CE Status: REPORTED Severity: crash Priority: NOR Component: Brush engines Assignee: krita-bugs-n...@kde.org Reporter: raptori...@gmail.com Target Milestone: --- SUMMARY STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT All works fine, until I try to paint, the brush just freezes, but I can still hover over and click the tabs, UI, and options just fine. EXPECTED RESULT Some kind of fix. SOFTWARE/OS VERSIONS Windows: Windows 10 macOS: N/A Linux/KDE Plasma: N/A (available in About System) KDE Plasma Version: N/A KDE Frameworks Version: N/A Qt Version: N/A ADDITIONAL INFORMATION: Haven't been able to do anything on Krita since I purchased. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 408041] Brush freezes when attempting to paint.
https://bugs.kde.org/show_bug.cgi?id=408041 --- Comment #4 from Callum --- Hello, sorry for the late reply. I have tried turning off openGL, the problem still accrued. Also, I am using a GTX 1050 Graphics card. Sent from Mail for Windows 10 From: Scott Petrovic Sent: 28 May 2019 20:47 To: raptori...@gmail.com Subject: [krita] [Bug 408041] Brush freezes when attempting to paint. https://bugs.kde.org/show_bug.cgi?id=408041 Scott Petrovic changed: What|Removed |Added CC||scottpetro...@gmail.com --- Comment #1 from Scott Petrovic --- Can you try to turn off OpenGL in the settings and see if the issue goes away? Sometimes old Intel graphics cards can have that issue. Maybe that is the culprit? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 381759] New: KDE Crashes when removing some system tray icons
https://bugs.kde.org/show_bug.cgi?id=381759 Bug ID: 381759 Summary: KDE Crashes when removing some system tray icons Product: plasmashell Version: 5.10.2 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: dragonsfed...@gmail.com CC: bhus...@gmail.com, plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.10.2) Qt Version: 5.9.0 Frameworks Version: 5.35.0 Operating System: Linux 4.4.73-1-MANJARO x86_64 Distribution: "Manjaro Linux" -- Information about the crash: - Custom settings of the application: > I hide the clipboard icon from the system tray. > I then removed the device notifier from the system tray. I then clicked "Apply", KDE then crashed and restarted. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7fd39bbf6d80 (LWP 915))] Thread 13 (Thread 0x7fd29f7fe700 (LWP 1293)): #0 0x7fd394b0b39d in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7fd39593e0eb in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #2 0x7fd2da97e3cd in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #3 0x7fd2da9832b8 in () at /usr/lib/libKF5ThreadWeaver.so.5 #4 0x7fd2da97d913 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #5 0x7fd2da983312 in () at /usr/lib/libKF5ThreadWeaver.so.5 #6 0x7fd2da97d913 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #7 0x7fd2da980b6b in ThreadWeaver::Thread::run() () at /usr/lib/libKF5ThreadWeaver.so.5 #8 0x7fd39593ccbd in () at /usr/lib/libQt5Core.so.5 #9 0x7fd394b05297 in start_thread () at /usr/lib/libpthread.so.0 #10 0x7fd3952511ef in clone () at /usr/lib/libc.so.6 Thread 12 (Thread 0x7fd29700 (LWP 1292)): #0 0x7fd394b0b39d in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7fd39593e0eb in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #2 0x7fd2da97e3cd in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #3 0x7fd2da9832b8 in () at /usr/lib/libKF5ThreadWeaver.so.5 #4 0x7fd2da97d913 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #5 0x7fd2da983312 in () at /usr/lib/libKF5ThreadWeaver.so.5 #6 0x7fd2da97d913 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #7 0x7fd2da983312 in () at /usr/lib/libKF5ThreadWeaver.so.5 #8 0x7fd2da97d913 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #9 0x7fd2da983312 in () at /usr/lib/libKF5ThreadWeaver.so.5 #10 0x7fd2da97d913 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #11 0x7fd2da983312 in () at /usr/lib/libKF5ThreadWeaver.so.5 #12 0x7fd2da97d913 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #13 0x7fd2da983312 in () at /usr/lib/libKF5ThreadWeaver.so.5 #14 0x7fd2da97d913 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #15 0x7fd2da983312 in () at /usr/lib/libKF5ThreadWeaver.so.5 #16 0x7fd2da97d913 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #17 0x7fd2da983312 in () at /usr/lib/libKF5ThreadWeaver.so.5 #18 0x7fd2da97d913 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #19 0x7fd2da980b6b in ThreadWeaver::Thread::run() () at /usr/lib/libKF5ThreadWeaver.so.5 #20 0x7fd39593ccbd in () at /usr/lib/libQt5Core.so.5 #21 0x7fd394b05297 in start_thread () at /usr/lib/libpthread.so.0 #22 0x7fd3952511ef in clone () at /usr/lib/libc.so.6 Thread 11 (Thread 0x7fd2c0b2a700 (LWP 1291)): #0 0x7fd394b0b39d in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7fd39593e0eb in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #2 0x7fd2da97e3cd in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #3 0x7fd2da9832b8 in () at /usr/lib/libKF5ThreadWeaver.so.5 #4 0x7fd2da97d913 in ThreadWeaver::Weaver::applyFo
[plasmashell] [Bug 381759] KDE Crashes when removing some system tray icons
https://bugs.kde.org/show_bug.cgi?id=381759 Callum Smith changed: What|Removed |Added Component|general |System Tray -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 507592] New: Charger unplug not always detected
https://bugs.kde.org/show_bug.cgi?id=507592 Bug ID: 507592 Summary: Charger unplug not always detected Classification: Plasma Product: plasmashell Version First 6.4.3 Reported In: Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Power management & brightness Assignee: plasma-b...@kde.org Reporter: callum.mcg...@gmail.com Target Milestone: 1.0 SUMMARY On a ThinkPad P14s Gen 4 (AMD), unplugging a charger connected to the USB-C port can sometimes result in Plasma still believing a charger is connected - this results in power-related settings not changing to "on battery" mode. STEPS TO REPRODUCE 1. Plug in charger, notice sound plays and Plasma switches settings to On AC mode. 2. Unplug charger, no change. 3. Insert charger into another USB-C port, repeat a few times. Eventually plasma will apply the correct power profile when unplugged. OBSERVED RESULT Inconsistent behaviour on charger connect/disconnect. EXPECTED RESULT Reliable connect/disconnect event listening. SOFTWARE/OS VERSIONS (available in the Info Center app, or by running `kinfo` in a terminal window) Linux/KDE Plasma: Fedora Linux 42. Kernel 6.15.7-200.fc42.x86_64 (64-bit) KDE Plasma Version: 6.4.3 KDE Frameworks Version: 6.16.0 Qt Version: 6.9.1 ADDITIONAL INFORMATION Upon unplugging the charger, this event can be found when running `acpi_listen` from `acpid` utilities. ``` battery PNP0C0A:00 0080 0001 ibm/hotkey LEN0268:00 0080 6032 ac_adapter ACPI0003:00 0080 ``` With this series of events happening when plugging in the charger. ``` ac_adapter ACPI0003:00 0080 0001 battery PNP0C0A:00 0080 0001 ibm/hotkey LEN0268:00 0080 6032 ``` -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 507592] Charger unplug not always detected
https://bugs.kde.org/show_bug.cgi?id=507592 --- Comment #2 from Callum McGing --- (In reply to TraceyC from comment #1) > Can you run this, reproduce the bug, and then press Ctrl+C to end it? That > will save a log file, which you can attach to this report. This may have > information that helps us get more information about what's happening: > > sudo journalctl -f > ~/logs.txt > > Thanks! Is this the correct command? Nothing seems to be logged after the basic startup, either by running under sudo or as the regular user. For reference here is the output of sudo journalctl -f > ~/logs.txt ``` Aug 02 11:49:10 cmcging-thonkpad systemd[4800]: Reached target basic.target - Basic System. Aug 02 11:49:10 cmcging-thonkpad systemd[4800]: drkonqi-coredump-cleanup.service - Cleanup lingering KCrash metadata was skipped because of an unmet condition check (ConditionPathExistsGlob=/root/.cache/kcrash-metadata/*.ini). Aug 02 11:49:10 cmcging-thonkpad systemd[1]: Started user@0.service - User Manager for UID 0. Aug 02 11:49:10 cmcging-thonkpad audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=user@0 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' Aug 02 11:49:10 cmcging-thonkpad systemd[4800]: Starting unity-gtk-module.service - Unity GTK Module Environment variables... Aug 02 11:49:10 cmcging-thonkpad systemd[1]: Started session-c4.scope - Session c4 of User root. Aug 02 11:49:10 cmcging-thonkpad audit[4796]: USER_START pid=4796 uid=1000 auid=1000 ses=3 msg='op=PAM:session_open grantors=pam_keyinit,pam_limits,pam_keyinit,pam_limits,pam_systemd,pam_unix acct="root" exe="/usr/bin/sudo" hostname=cmcging-thonkpad addr=? terminal=/dev/pts/1 res=success' Aug 02 11:49:10 cmcging-thonkpad sudo[4796]: pam_unix(sudo:session): session opened for user root(uid=0) by cmcging(uid=1000) Aug 02 11:49:10 cmcging-thonkpad systemd[4800]: Created slice session.slice - User Core Session Slice. Aug 02 11:49:10 cmcging-thonkpad systemd[4800]: Starting dbus-broker.service - D-Bus User Message Bus... Aug 02 11:49:10 cmcging-thonkpad dbus-broker-launch[4822]: Service file '/usr/share//dbus-1/services/org.kde.dolphin.FileManager1.service' is not named after the D-Bus name 'org.freedesktop.FileManager1'. Aug 02 11:49:10 cmcging-thonkpad dbus-broker-launch[4822]: Service file '/usr/share//dbus-1/services/org.kde.kscreen.service' is not named after the D-Bus name 'org.kde.KScreen'. Aug 02 11:49:10 cmcging-thonkpad dbus-broker-launch[4822]: Policy to allow eavesdropping in /usr/share/dbus-1/session.conf +31: Eavesdropping is deprecated and ignored Aug 02 11:49:10 cmcging-thonkpad dbus-broker-launch[4822]: Policy to allow eavesdropping in /usr/share/dbus-1/session.conf +33: Eavesdropping is deprecated and ignored Aug 02 11:49:10 cmcging-thonkpad dbus-broker-launch[4822]: Service file '/usr/share//dbus-1/services/org.kde.plasma.Notifications.service' is not named after the D-Bus name 'org.freedesktop.Notifications'. Aug 02 11:49:10 cmcging-thonkpad systemd[4800]: Started dbus-broker.service - D-Bus User Message Bus. Aug 02 11:49:10 cmcging-thonkpad dbus-broker-launch[4822]: Ready Aug 02 11:49:10 cmcging-thonkpad systemd[4800]: Finished unity-gtk-module.service - Unity GTK Module Environment variables. Aug 02 11:49:10 cmcging-thonkpad systemd[4800]: Reached target default.target - Main User Target. Aug 02 11:49:10 cmcging-thonkpad systemd[4800]: Startup finished in 442ms. Aug 02 11:49:15 cmcging-thonkpad kernel: NMI watchdog: Enabled. Permanently consumes one hw-PMU counter. ``` -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 346165] OSX: No pen pressure when OpenGL is turned off
https://bugs.kde.org/show_bug.cgi?id=346165 Callum Gare changed: What|Removed |Added CC||cal...@gare.com.au --- Comment #8 from Callum Gare --- MacBook Pro (Retina, 13-inch, Mid 2013), OS X 10.10.5, Kirta 2.9.9, Wacom Intus Pen & Touch. I also get the same issue when testing on my friends computer which is a MacBook Air (13-inch, late 2015) (all other details same as above). Initially turning openGL on and off was not enough to get pressure to work but after I also right clicked a bit, just toggling openGL on and off started getting pressure to work. Once working it will stop working when the application is closed and reopened or when the master pressure control is edited (probably other situations too, their just the ways I've noticed it). It appears pressure sensitivity works for me IN openGL mode but unfortunately openGL doesn't work properly (it will display changes in the layer previews but not the canvas for example). I'm surprised this doesn't seem to be effecting more uses. I don't have a partially strange setup and it's all pretty new. Cheers :) -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 346165] OSX: No pen pressure when OpenGL is turned off
https://bugs.kde.org/show_bug.cgi?id=346165 --- Comment #10 from Callum Gare --- (In reply to Boudewijn Rempt from comment #9) > Well, it affects _all_ krita users on OSX. But there aren't that many OSX > users because Krita 2.9 on OSX is still nothing more than a tech preview... > I hope we can fix stuff for 3.0 and then have OSX as a really supported > platform. Ah, right oh. Thanks very much for that :) -- You are receiving this mail because: You are watching all bug changes.
