[wacomtablet] [Bug 395332] New: Wacom Co., Ltd PTH-660 [Intuos Pro (M)] - missing from wacom_devicelist
https://bugs.kde.org/show_bug.cgi?id=395332 Bug ID: 395332 Summary: Wacom Co., Ltd PTH-660 [Intuos Pro (M)] - missing from wacom_devicelist Product: wacomtablet Version: 3.0.0 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: general Assignee: jazzv...@gmail.com Reporter: nomastery...@gmail.com Target Milestone: --- $ lsusb: Wacom Co.,Ltd. Wacom Intuos Pro M as /devices/pci:00/:00:1c.0/:02:00.0/:03:02.0/:38:00.0/usb3/3-1/3-1.3/3-1.3:1.0/0003:056A:0357.0007/input/input33 [66024.007672] hid-generic 0003:056A:0357.0007: input,hiddev0,hidraw0: USB HID v1.10 Mouse [Wacom Co.,Ltd. Wacom Intuos Pro M] on usb-:38:00.0-1.3/input0 [66024.009378] hid-generic 0003:056A:0357.0008: hiddev3,hidraw1: USB HID v1.10 Device [Wacom Co.,Ltd. Wacom Intuos Pro M] on usb-:38:00.0-1.3/input2 [66024.100492] input: Wacom Intuos Pro M Pen as /devices/pci:00/:00:1c.0/:02:00.0/:03:02.0/:38:00.0/usb3/3-1/3-1.3/3-1.3:1.0/0003:056A:0357.0007/input/input34 [66024.100553] input: Wacom Intuos Pro M Pad as /devices/pci:00/:00:1c.0/:02:00.0/:03:02.0/:38:00.0/usb3/3-1/3-1.3/3-1.3:1.0/0003:056A:0357.0007/input/input36 [66024.100685] wacom 0003:056A:0357.0007: hidraw0: USB HID v1.10 Mouse [Wacom Co.,Ltd. Wacom Intuos Pro M] on usb-:38:00.0-1.3/input0 [66024.101017] input: Wacom Intuos Pro M Finger as /devices/pci:00/:00:1c.0/:02:00.0/:03:02.0/:38:00.0/usb3/3-1/3-1.3/3-1.3:1.2/0003:056A:0357.0008/input/input38 [66024.101074] wacom 0003:056A:0357.0008: hidraw1: USB HID v1.10 Device [Wacom Co.,Ltd. Wacom Intuos Pro M] on usb-:38:00.0-1.3/input2 Wacom Intuos Pro Medium tablet wacom_devicelist requires modification for Plasma desktop control via kcm-wacomtablet. Optional packages from the AUR: wacom-utility-git -- Graphical tablet configuration utility input-wacom-dkms -- Latest Kernel modules form Wacom tablets (DKMS). Useful if your wacom tablet is not supported upstream yet (not sure how useful in this instance). Verify you tablet is identified: lsusb 056a:0357 Wacom Co., Ltd PTH-660 [Intuos Pro (M)] Edit /usr/share/wacomtablet/data/wacom_devicelist and search for that ID (or 660). This ID is not located in the file. Copy the previous model of the Medium tablet in the wacom_devicelist to the end of wacom_devicelist file, edit device ID and device name to match the name similar to the code below: sudo vi /usr/share/wacomtablet/data/wacom_devicelist ## [0357] model=PTH-660 layout=bl_4 name=Wacom Intuos Pro M padbuttons=9 wheel=no touchring=yes touchstripl=no touchstripr=no hwbutton1=1 hwbutton2=2 hwbutton3=3 hwbutton4=8 hwbutton5=9 hwbutton6=10 hwbutton7=11 hwbutton8=12 hwbutton9=13 Disconnect tablet and reconnect to verify it is identified. Open the Graphic Tablet from Plasma menu or Settings and the tablet now appears as expected and can be configured properly. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 388874] Undo multiple levels caused crash (Krita Beta)
https://bugs.kde.org/show_bug.cgi?id=388874 --- Comment #2 from Jeff H <nomastery...@gmail.com> --- Indeed same bug it appears. On Fri, Jan 12, 2018, 11:08 AM Boudewijn Rempt <bugzilla_nore...@kde.org> wrote: > https://bugs.kde.org/show_bug.cgi?id=388874 > > Boudewijn Rempt <b...@valdyas.org> changed: > >What|Removed |Added > > > CC||b...@valdyas.org > > --- Comment #1 from Boudewijn Rempt <b...@valdyas.org> --- > Hm, it's the same crash as in https://bugs.kde.org/show_bug.cgi?id=382315 > -- > could it be related? > > -- > You are receiving this mail because: > You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 388874] New: Undo multiple levels caused crash (Krita Beta)
https://bugs.kde.org/show_bug.cgi?id=388874 Bug ID: 388874 Summary: Undo multiple levels caused crash (Krita Beta) Product: krita Version: unspecified Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: General Assignee: krita-bugs-n...@kde.org Reporter: nomastery...@gmail.com Target Milestone: --- Application: krita (4.0.0-beta1 (git 30620eb)) Qt Version: 5.10.0 Frameworks Version: 5.41.0 Operating System: Linux 4.14.12-1-ARCH x86_64 Distribution: "Arch Linux" -- Information about the crash: - What I was doing when the application crashed: I was undoing 5 steps of work including layer selection, pattern application across layer. -- Backtrace: Application: Krita (krita), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7f66d0752800 (LWP 4164))] Thread 15 (Thread 0x7f65dd3fa700 (LWP 31337)): #0 0x7f66c6ca16dd in pthread_cond_timedwait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f66cda2bec1 in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #2 0x7f66cda27d91 in () at /usr/lib/libQt5Core.so.5 #3 0x7f66cda2ab2d in () at /usr/lib/libQt5Core.so.5 #4 0x7f66c6c9b08c in start_thread () at /usr/lib/libpthread.so.0 #5 0x7f66cd11be1f in clone () at /usr/lib/libc.so.6 Thread 14 (Thread 0x7f65df7fe700 (LWP 31336)): #0 0x7f66c6ca16dd in pthread_cond_timedwait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f66cda2bec1 in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #2 0x7f66cda27d91 in () at /usr/lib/libQt5Core.so.5 #3 0x7f66cda2ab2d in () at /usr/lib/libQt5Core.so.5 #4 0x7f66c6c9b08c in start_thread () at /usr/lib/libpthread.so.0 #5 0x7f66cd11be1f in clone () at /usr/lib/libc.so.6 Thread 13 (Thread 0x7f6608fd9700 (LWP 31335)): #0 0x7f66c6ca16dd in pthread_cond_timedwait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f66cda2bec1 in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #2 0x7f66cda27d91 in () at /usr/lib/libQt5Core.so.5 #3 0x7f66cda2ab2d in () at /usr/lib/libQt5Core.so.5 #4 0x7f66c6c9b08c in start_thread () at /usr/lib/libpthread.so.0 #5 0x7f66cd11be1f in clone () at /usr/lib/libc.so.6 Thread 12 (Thread 0x7f66097da700 (LWP 31334)): #0 0x7f66c6ca16dd in pthread_cond_timedwait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f66cda2bec1 in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #2 0x7f66cda27d91 in () at /usr/lib/libQt5Core.so.5 #3 0x7f66cda2ab2d in () at /usr/lib/libQt5Core.so.5 #4 0x7f66c6c9b08c in start_thread () at /usr/lib/libpthread.so.0 #5 0x7f66cd11be1f in clone () at /usr/lib/libc.so.6 Thread 11 (Thread 0x7f65d700 (LWP 31333)): #0 0x7f66c6ca16dd in pthread_cond_timedwait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f66cda2bec1 in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #2 0x7f66cda27d91 in () at /usr/lib/libQt5Core.so.5 #3 0x7f66cda2ab2d in () at /usr/lib/libQt5Core.so.5 #4 0x7f66c6c9b08c in start_thread () at /usr/lib/libpthread.so.0 #5 0x7f66cd11be1f in clone () at /usr/lib/libc.so.6 Thread 10 (Thread 0x7f65debfd700 (LWP 31332)): #0 0x7f66c6ca16dd in pthread_cond_timedwait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f66cda2bec1 in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #2 0x7f66cda27d91 in () at /usr/lib/libQt5Core.so.5 #3 0x7f66cda2ab2d in () at /usr/lib/libQt5Core.so.5 #4 0x7f66c6c9b08c in start_thread () at /usr/lib/libpthread.so.0 #5 0x7f66cd11be1f in clone () at /usr/lib/libc.so.6 Thread 9 (Thread 0x7f65de3fc700 (LWP 31331)): #0 0x7f66c6ca16dd in pthread_cond_timedwait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f66cda2bec1 in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #2 0x7f66cda27d91 in () at /usr/lib/libQt5Core.so.5 #3 0x7f66cda2ab2d in () at /usr/lib/libQt5Core.so.5 #4 0x7f66c6c9b08c in start_thread () at /usr/lib/libpthread.so.0 #5 0x7f66cd11be1f in clone () at /usr/lib/libc.so.6 Thread 8 (Thread 0x7f65ddbfb700 (LWP 31330)): #0 0x7f66c6ca16dd in pthread_cond_timedwait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f66cda2bec1 in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #2 0x7f66cda27d91 in () at /usr/lib/libQt5Core.so.5 #3 0x7f66cda2ab2d in () at /usr/lib/libQt5Core.so.5 #4 0x7f66c6c9b08c in start_thread () at /usr/lib/libpthread.so.0 #5 0x7f66cd11be1f in clone () at /usr/lib/libc.so.6 Thread 7 (Thread 0x7f668147c700 (LWP 4246)): #0 0x7f66cd10d3d8 in
[kipiplugins] [Bug 381664] Plugin leads to the home page of Flickr and 'An error has occurred: Invalid Frob It can not be continued.'
https://bugs.kde.org/show_bug.cgi?id=381664 Jeff H <nomastery...@gmail.com> changed: What|Removed |Added CC||nomastery...@gmail.com --- Comment #8 from Jeff H <nomastery...@gmail.com> --- I had my /home drive die last evening and of course my authentication was within the config directory for DigiKam. So I tried to login today and found the same error is happening to me. I suppose Yahoo has implemented Oauth2 as of today August 3, 2017. Oh Joy. You guys have created a masterpiece of photo management and I truly appreciate your efforts. Will wait patiently for a fix. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 368363] OpenGL canvas remains blank with some driver/gpu combinations on Windows
https://bugs.kde.org/show_bug.cgi?id=368363 --- Comment #6 from Jeff H. <jeffh...@yahoo.com> --- Created attachment 105029 --> https://bugs.kde.org/attachment.cgi?id=105029=edit blob.jpg -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 368363] OpenGL canvas remains blank with some driver/gpu combinations on Windows
https://bugs.kde.org/show_bug.cgi?id=368363 --- Comment #5 from Jeff H. <jeffh...@yahoo.com> --- Here is the intel driver information but I have an NVIDIA GT540M on the system as well so I think that is what it should be using. Including the info for it as well. Thanks for following up on the bug and let me know if there's anything else I can provide to assist in identifying the problem. Jeff H. On Friday, April 14, 2017 2:44 PM, Boudewijn Rempt <bugzilla_nore...@kde.org> wrote: https://bugs.kde.org/show_bug.cgi?id=368363 Boudewijn Rempt <b...@valdyas.org> changed: What |Removed |Added Resolution|--- |DUPLICATE Status|UNCONFIRMED |RESOLVED --- Comment #4 from Boudewijn Rempt <b...@valdyas.org> --- Can you please tell me the exact driver versoin and intel HD display chip version you have? We're trying to compile a list to see what's up. *** This bug has been marked as a duplicate of bug 360601 *** -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 375562] New: Digikam crashes while scanning images into sqlite database
https://bugs.kde.org/show_bug.cgi?id=375562 Bug ID: 375562 Summary: Digikam crashes while scanning images into sqlite database Product: digikam Version: 5.4.0 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: Import Assignee: digikam-de...@kde.org Reporter: nomastery...@gmail.com Target Milestone: --- Created attachment 103640 --> https://bugs.kde.org/attachment.cgi?id=103640=edit KDE Bug report New digikam installation - wiped old database and digikamrc file to be sure it was ready for the new QT5 and hit a snag. Every time I have it scan my images, it crashes. Bug report attached. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 368363] Brush cursor dissapears in opengl canvas
https://bugs.kde.org/show_bug.cgi?id=368363 Jeff H. <jeffh...@yahoo.com> changed: What|Removed |Added CC||jeffh...@yahoo.com --- Comment #1 from Jeff H. <jeffh...@yahoo.com> --- I have encountered this same bug. When attempting to draw with any brush on the canvas, the canvas does not update. When I change focus to a menu item or click the right mouse button, the canvas suddenly updates, showing all the strokes that were made. Windows 10 on Intel I7 with 12GB RAM, NVIDIA Geforce GT540M w/1GB and Krita 3.0.1.1. This also occurred on the previous version of krita. Like the original poster, disabling OpenGL removes the problem. -- You are receiving this mail because: You are watching all bug changes.
