[krita] [Bug 396779] Desaturated reference images still give original saturated color when using the color picker

2018-09-28 Thread Altguard
https://bugs.kde.org/show_bug.cgi?id=396779

--- Comment #2 from Altguard  ---
This escaped my mind until the 4.1.3 release - the issue was noted as fixed in
the patch notes and, sure enough, it seems to have been resolved with the
latest version.

I apologize for not providing more information before.

-- 
You are receiving this mail because:
You are watching all bug changes.

[krita] [Bug 396779] New: Desaturated reference images still give original saturated color when using the color picker

2018-07-22 Thread Altguard
https://bugs.kde.org/show_bug.cgi?id=396779

Bug ID: 396779
   Summary: Desaturated reference images still give original
saturated color when using the color picker
   Product: krita
   Version: 4.1.1
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Tools/Reference Images
  Assignee: krita-bugs-n...@kde.org
  Reporter: altgu...@gmail.com
  Target Milestone: ---

Created attachment 114077
  --> https://bugs.kde.org/attachment.cgi?id=114077&action=edit
Video Example

Adding a reference image, desaturating the image using the reference image tool
options, then color picking from the desaturated reference image will pick the
original saturated color from the reference image.

Reproducable: Always

Steps to reproduce:

1) Add a color reference image

2) Us the Reference Image Tool Options to desaturate the reference image

3) Switch to the Color Selector Tool and pick a color from the desaturated
reference image

Actual Result:

The Color Picker will pick the original, fully saturated color from the
reference image.

Expected Result:

The Color Picker picks the desaturated color.

-- 
You are receiving this mail because:
You are watching all bug changes.

[Falkon] [Bug 395941] AdBlock fails to load subscriptions

2018-06-28 Thread Altguard
https://bugs.kde.org/show_bug.cgi?id=395941

--- Comment #5 from Altguard  ---
Ah, ok that was the problem. QNetworkAccessManager was attempting to connect to
a different network interface that I once used months ago, but is no longer
installed. Everything seemed to be working though, so I never noticed. Clearing
that up fixed the AdBlock issue.

Sorry to bother you with that.

-- 
You are receiving this mail because:
You are watching all bug changes.

[Falkon] [Bug 395941] AdBlock fails to load subscriptions

2018-06-28 Thread Altguard
https://bugs.kde.org/show_bug.cgi?id=395941

--- Comment #3 from Altguard  ---
I am attempting to add EasyList (from URL:
https://easylist.to/easylist/easylist.txt) and Peter Lowe's List (from URL:
http://pgl.yoyo.org/adservers/serverlist.php?hostformat=adblockplus&mimetype=plaintext)

-- 
You are receiving this mail because:
You are watching all bug changes.

[Falkon] [Bug 395941] AdBlock fails to load subscriptions

2018-06-28 Thread Altguard
https://bugs.kde.org/show_bug.cgi?id=395941

--- Comment #2 from Altguard  ---
Created attachment 113622
  --> https://bugs.kde.org/attachment.cgi?id=113622&action=edit
Terminal output

-- 
You are receiving this mail because:
You are watching all bug changes.

[krita] [Bug 395942] Request/Wishlist: Please bring back the "Hide Docker Titlebars" option

2018-06-28 Thread Altguard
https://bugs.kde.org/show_bug.cgi?id=395942

--- Comment #2 from Altguard  ---
Ah, I see. Well, it was worth  a shot. Thanks for the explanation.

-- 
You are receiving this mail because:
You are watching all bug changes.

[krita] [Bug 395942] New: Request/Wishlist: Please bring back the "Hide Docker Titlebars" option

2018-06-27 Thread Altguard
https://bugs.kde.org/show_bug.cgi?id=395942

Bug ID: 395942
   Summary: Request/Wishlist: Please bring back the "Hide Docker
Titlebars" option
   Product: krita
   Version: 4.1.0
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: wishlist
  Priority: NOR
 Component: Dockers
  Assignee: krita-bugs-n...@kde.org
  Reporter: altgu...@gmail.com
  Target Milestone: ---

When some of the extra docker options were removed for the sake of simplicity,
the option to remove the docker titlebars in the settings dropdown menu was
also removed. Hiding the titlebars gives the dockers themselves a little bit of
extra precious UI space and, more importantly, prevents accidential closing of
some dockers. I quite liked it, and would like to see it return if at all
possible.

-- 
You are receiving this mail because:
You are watching all bug changes.

[Falkon] [Bug 395941] New: AdBlock fails to load subscriptions

2018-06-27 Thread Altguard
https://bugs.kde.org/show_bug.cgi?id=395941

Bug ID: 395941
   Summary: AdBlock fails to load subscriptions
   Product: Falkon
   Version: unspecified
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: extensions
  Assignee: now...@gmail.com
  Reporter: altgu...@gmail.com
  Target Milestone: ---

AdBlock doesn't appear to be filtering out ads from subscriptions at all.
Oftentimes subscriptions display "(Error: Cannot load subscription!)" after
their title either when initially adding them, or after attempting to update
subscriptions. Whether the error is displayed or not though, there appears to
be no filtering happening based on subscriptions; individual custom rules work,
but not subscriptions.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 388182] Plasma breaks when taking a screenshot of chromium

2018-01-13 Thread Altguard
https://bugs.kde.org/show_bug.cgi?id=388182

--- Comment #19 from Altguard  ---
In addition, taking a full screen screenshot of both monitors at once does not
cause any issues - only the window screenshot.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 388182] Plasma breaks when taking a screenshot of chromium

2018-01-13 Thread Altguard
https://bugs.kde.org/show_bug.cgi?id=388182

--- Comment #18 from Altguard  ---
That just gave me an idea I didn't consider before - resizing the windows. As
it turns out, this isn't just Chromium - after trying multiple applications at
different window sizes, it looks like taking a screenshot of *any* application
past a certain window size causes the crash, and shrinking the chromium window
down allows me to take a screenshot without issues. I always have Chromium
windows open at a larger size than everything else, so I never caught on until
now. My apologies.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 388182] Plasma breaks when taking a screenshot of chromium

2018-01-13 Thread Altguard
https://bugs.kde.org/show_bug.cgi?id=388182

--- Comment #16 from Altguard  ---
Interesting, apparently I can take an active window screenshot of Chromium on
my smaller monitor without any problems. The issue only seems to happen on my
larger main monitor, and it only happens with Chromium. Screenshots of any
other application don't cause the issue, regardless of which monitor I take the
screenshot on.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 388182] Plasma breaks when taking a screenshot of chromium

2018-01-12 Thread Altguard
https://bugs.kde.org/show_bug.cgi?id=388182

--- Comment #13 from Altguard  ---
I tried running that while the problem was active, and I got the output
"Service 'org.kde.KWin' does not exist.", so the output I'm attaching was run
while the problem was not active.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 388182] Plasma breaks when taking a screenshot of chromium

2018-01-12 Thread Altguard
https://bugs.kde.org/show_bug.cgi?id=388182

--- Comment #14 from Altguard  ---
Created attachment 109827
  --> https://bugs.kde.org/attachment.cgi?id=109827&action=edit
Output of | qdbus org.kde.KWin /KWin supportInformation

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 388182] Plasma breaks when taking a screenshot of chromium

2018-01-12 Thread Altguard
https://bugs.kde.org/show_bug.cgi?id=388182

Altguard  changed:

   What|Removed |Added

 Attachment #109814|0   |1
is obsolete||

--- Comment #11 from Altguard  ---
Created attachment 109821
  --> https://bugs.kde.org/attachment.cgi?id=109821&action=edit
Xorg log from  | xdotool key XF86LogGrabInfo

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 388182] Plasma breaks when taking a screenshot of chromium

2018-01-12 Thread Altguard
https://bugs.kde.org/show_bug.cgi?id=388182

--- Comment #10 from Altguard  ---
Ah, I didn't, sorry. However, I have now done it again while the problem was
happening and there still weren't any active grabs listed (I'll attach the new
log, but it's no different as far as I could see).

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 388182] Plasma breaks when taking a screenshot of chromium

2018-01-12 Thread Altguard
https://bugs.kde.org/show_bug.cgi?id=388182

--- Comment #8 from Altguard  ---
Created attachment 109814
  --> https://bugs.kde.org/attachment.cgi?id=109814&action=edit
Xorg log from  | xdotool key XF86LogGrabInfo

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 388182] Plasma breaks when taking a screenshot of chromium

2018-01-12 Thread Altguard
https://bugs.kde.org/show_bug.cgi?id=388182

--- Comment #7 from Altguard  ---
Ah, my apologies. I forgot all about this after  the holidays. I'll attach the
log now.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 388182] Plasma breaks when taking a screenshot of chromium

2017-12-24 Thread Altguard
https://bugs.kde.org/show_bug.cgi?id=388182

--- Comment #4 from Altguard  ---
Also, it just  crossed my mind to screenshot Chromium after restarting kwin_x11
in konsole, which produces this:

===
$ kwin_x11
QXcbConnection: XCB error: 3 (BadWindow), sequence: 172, resource id: 2097158,
major code: 20 (GetProperty), minor code: 0
OpenGL vendor string:   NVIDIA Corporation
OpenGL renderer string: GeForce GTX 1070/PCIe/SSE2
OpenGL version string:  3.1.0 NVIDIA 387.34
OpenGL shading language version string: 1.40 NVIDIA via Cg compiler
Driver: NVIDIA
Driver version: 387.34
GPU class:  Unknown
OpenGL version: 3.1
GLSL version:   1.40
X server version:   1.19.5
Linux kernel version:   4.14.8
Requires strict binding:no
GLSL shaders:   yes
Texture NPOT support:   yes
Virtual Machine:no
kpluginindex: Not cached "/home/altguard/.local/share/kwin/effects"
kpluginindex: Not cached "/usr/share/kwin/effects"
kf5.kcoreaddons.desktopparser: Property type "Url" is not a known QVariant
type. Found while parsing property definition for "X-KWin-Video-Url" in
"/usr/share/kservicetypes5/kwineffect.desktop"
kpluginindex: Not cached "/usr/local/share/kwin/effects"
QXcbConnection: XCB error: 9 (BadDrawable), sequence: 2090, resource id: 0,
major code: 14 (GetGeometry), minor code: 0
QXcbConnection: XCB error: 9 (BadDrawable), sequence: 2092, resource id: 0,
major code: 14 (GetGeometry), minor code: 0
QXcbConnection: XCB error: 9 (BadDrawable), sequence: 2100, resource id: 0,
major code: 14 (GetGeometry), minor code: 0
QXcbConnection: XCB error: 9 (BadDrawable), sequence: 2110, resource id: 0,
major code: 14 (GetGeometry), minor code: 0
QXcbConnection: XCB error: 9 (BadDrawable), sequence: 2111, resource id: 0,
major code: 14 (GetGeometry), minor code: 0
QXcbConnection: XCB error: 9 (BadDrawable), sequence: 2112, resource id: 0,
major code: 14 (GetGeometry), minor code: 0
QXcbConnection: XCB error: 9 (BadDrawable), sequence: 2113, resource id: 0,
major code: 14 (GetGeometry), minor code: 0
QXcbConnection: XCB error: 9 (BadDrawable), sequence: 2114, resource id: 0,
major code: 14 (GetGeometry), minor code: 0
QXcbConnection: XCB error: 9 (BadDrawable), sequence: 2115, resource id: 0,
major code: 14 (GetGeometry), minor code: 0
QXcbConnection: XCB error: 9 (BadDrawable), sequence: 2116, resource id: 0,
major code: 14 (GetGeometry), minor code: 0
QXcbConnection: XCB error: 9 (BadDrawable), sequence: 2117, resource id: 0,
major code: 14 (GetGeometry), minor code: 0
QXcbConnection: XCB error: 9 (BadDrawable), sequence: 2120, resource id: 0,
major code: 14 (GetGeometry), minor code: 0
QXcbConnection: XCB error: 9 (BadDrawable), sequence: 2121, resource id: 0,
major code: 14 (GetGeometry), minor code: 0
QXcbConnection: XCB error: 9 (BadDrawable), sequence: 2122, resource id: 0,
major code: 14 (GetGeometry), minor code: 0
QXcbConnection: XCB error: 9 (BadDrawable), sequence: 2123, resource id: 0,
major code: 14 (GetGeometry), minor code: 0
kpluginindex: Not cached "/home/altguard/.local/share/kwin/scripts/"
kpluginindex: Not cached "/usr/share/kwin/scripts/"
kpluginindex: Not cached "/usr/local/share/kwin/scripts/"
===

After screenshotting Chromium:

===
The X11 connection broke (error 4). Did the X11 server die?
The X11 connection broke: Maximum allowed requested length exceeded (code 4)
XIO:  fatal IO error 2 (No such file or directory) on X server ":0"
  after 4871 requests (4871 known processed) with 0 events remaining.
$
===

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 388182] Plasma breaks when taking a screenshot of chromium

2017-12-24 Thread Altguard
https://bugs.kde.org/show_bug.cgi?id=388182

--- Comment #3 from Altguard  ---
I'm unclear as  to whether or not you'd like for me to  run gdb on the process
before or after kwin locks, so I tried both.

Trying to run it after locking kwin, I get "ptrace: No such process". After
searching through htop and ksysguard, it seems like the kwin_x11 process is
entirely gone after screenshotting Chromium, and running "kwin_x11" from
konsole actually fixes the problem.

The attached file is from running gdb while kwin is still working properly
(Which I'm assuming is not what you needed from me, but its  there just  in
case).

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 388182] Plasma breaks when taking a screenshot of chromium

2017-12-24 Thread Altguard
https://bugs.kde.org/show_bug.cgi?id=388182

--- Comment #2 from Altguard  ---
Created attachment 109506
  --> https://bugs.kde.org/attachment.cgi?id=109506&action=edit
gdb output

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 388182] New: Plasma breaks when taking a screenshot of chromium

2017-12-23 Thread Altguard
https://bugs.kde.org/show_bug.cgi?id=388182

Bug ID: 388182
   Summary: Plasma breaks when taking a screenshot of chromium
   Product: plasmashell
   Version: master
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: altgu...@gmail.com
CC: plasma-b...@kde.org
  Target Milestone: 1.0

Taking an active window screenshot of a web page in Chromium often causes
Plasma to break in a number of ways -  any hidden toolbars will become
permanently visible, many windows will loose their window decoration and become
unable to be moved, clicking on a different window doesn't change window focus
and bring it to the forefront, various widgets stop  working, etc. etc. 

This seems  to only happen with Chromium window screenshots - I can't recreate 
the bug with screenshots of any other application or web browser.

The link below is a video of the bug:
https://youtu.be/_mrwpKCwZ2Y

-- 
You are receiving this mail because:
You are watching all bug changes.

[krita] [Bug 388136] Krita crashed after removing a vector layer (text)

2017-12-22 Thread Altguard
https://bugs.kde.org/show_bug.cgi?id=388136

--- Comment #4 from Altguard  ---
That alone helps me out. Thanks.

-- 
You are receiving this mail because:
You are watching all bug changes.

[krita] [Bug 388136] Krita crashed after removing a vector layer (text)

2017-12-22 Thread Altguard
https://bugs.kde.org/show_bug.cgi?id=388136

--- Comment #2 from Altguard  ---
(In reply to Boudewijn Rempt from comment #1)
> Can you reproduce this crash? If so, could you 
> 
> a) install the debug symbols -- this backtrace doesn't give enough
> information to work out what might be going on.
> 
> b) start Krita from a terminal and check whether there is any "interesting"
> output on the terminal.

I can't seem to reproduce it even when doing the same thing on the same file, 
 unfortunately (or is it fortunate?). It seems to have been a one-off crash.

If you don't mind me asking, are the debug symbols a separate package that
needs installing, or an option to enable within Krita? I'd like to have that
installed if it'll make my backtraces useful for crash reports.

-- 
You are receiving this mail because:
You are watching all bug changes.

[krita] [Bug 388136] New: Krita crashed after removing a vector layer (text)

2017-12-21 Thread Altguard
https://bugs.kde.org/show_bug.cgi?id=388136

Bug ID: 388136
   Summary: Krita crashed after  removing  a vector layer (text)
   Product: krita
   Version: 3.3.2
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: General
  Assignee: krita-bugs-n...@kde.org
  Reporter: altgu...@gmail.com
  Target Milestone: ---

Application: krita (3.3.2)

Qt Version: 5.10.0
Frameworks Version: 5.41.0
Operating System: Linux 4.14.7-1-ARCH x86_64
Distribution (Platform): Archlinux Packages

-- Information about the crash:
- What I was doing when the application crashed:

I typed some text with the artistic text tool on the canvas, decided I didn't
want it and deleted the layer, then went to paint on  the canvas and crashed
when my pen made contact with the  canvas

-- Backtrace:
Application: Krita (krita), signal: Segmentation fault
Using host libthread_db library "/usr/lib/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f33ca88e180 (LWP 1532))]

Thread 5 (Thread 0x7f334700 (LWP 1560)):
#0  0x7f33c114238d in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7f33c7c0f00c in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/libQt5Core.so.5
#2  0x7f33c8d94b76 in  () at /usr/lib/libQt5Widgets.so.5
#3  0x7f33c7c0db2d in  () at /usr/lib/libQt5Core.so.5
#4  0x7f33c113c08a in start_thread () at /usr/lib/libpthread.so.0
#5  0x7f33c72fe42f in clone () at /usr/lib/libc.so.6

Thread 4 (Thread 0x7f3354d70700 (LWP 1559)):
#0  0x7f33c114238d in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7f33c7c0f00c in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/libQt5Core.so.5
#2  0x7f33c7c072c9 in QSemaphore::tryAcquire(int, int) () at
/usr/lib/libQt5Core.so.5
#3  0x7f33c506283d in KisTileDataSwapper::run() () at
/usr/lib/libkritaimage.so.18
#4  0x7f33c7c0db2d in  () at /usr/lib/libQt5Core.so.5
#5  0x7f33c113c08a in start_thread () at /usr/lib/libpthread.so.0
#6  0x7f33c72fe42f in clone () at /usr/lib/libc.so.6

Thread 3 (Thread 0x7f3355571700 (LWP 1558)):
#0  0x7f33c114238d in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7f33c7c0f00c in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/libQt5Core.so.5
#2  0x7f33c7c0705c in QSemaphore::acquire(int) () at
/usr/lib/libQt5Core.so.5
#3  0x7f33c50444e7 in  () at /usr/lib/libkritaimage.so.18
#4  0x7f33c7c0db2d in  () at /usr/lib/libQt5Core.so.5
#5  0x7f33c113c08a in start_thread () at /usr/lib/libpthread.so.0
#6  0x7f33c72fe42f in clone () at /usr/lib/libc.so.6

Thread 2 (Thread 0x7f33a7c69700 (LWP 1535)):
#0  0x7f33c72f3f2b in poll () at /usr/lib/libc.so.6
#1  0x7f33bf5d9ed3 in  () at /usr/lib/libglib-2.0.so.0
#2  0x7f33bf5d9fae in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#3  0x7f33c7e566b4 in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#4  0x7f33c7df882b in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#5  0x7f33c7c0878e in QThread::exec() () at /usr/lib/libQt5Core.so.5
#6  0x7f33c1367416 in  () at /usr/lib/libQt5DBus.so.5
#7  0x7f33c7c0db2d in  () at /usr/lib/libQt5Core.so.5
#8  0x7f33c113c08a in start_thread () at /usr/lib/libpthread.so.0
#9  0x7f33c72fe42f in clone () at /usr/lib/libc.so.6

Thread 1 (Thread 0x7f33ca88e180 (LWP 1532)):
[KCrash Handler]
#5  0x7f33ca14c6eb in  () at /usr/lib/libkritaui.so.18
#6  0x7f33ca151033 in bool
KisShortcutMatcher::tryRunSingleActionShortcutImpl(Qt::Key,
QEvent*, QSet const&) () at /usr/lib/libkritaui.so.18
#7  0x7f33ca1503a1 in KisShortcutMatcher::keyPressed(Qt::Key) () at
/usr/lib/libkritaui.so.18
#8  0x7f33ca138b9e in KisInputManager::eventFilterImpl(QEvent*) () at
/usr/lib/libkritaui.so.18
#9  0x7f33c7df9eac in
QCoreApplicationPrivate::sendThroughObjectEventFilters(QObject*, QEvent*) () at
/usr/lib/libQt5Core.so.5
#10 0x7f33c8b74e18 in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() at /usr/lib/libQt5Widgets.so.5
#11 0x7f33c8b7dda3 in QApplication::notify(QObject*, QEvent*) () at
/usr/lib/libQt5Widgets.so.5
#12 0x7f33ca1add98 in KisApplication::notify(QObject*, QEvent*) () at
/usr/lib/libkritaui.so.18
#13 0x7f33c7dfa1e0 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() at /usr/lib/libQt5Core.so.5
#14 0x7f33c8bd298b in  () at /usr/lib/libQt5Widgets.so.5
#15 0x7f33c8b74e3c in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() at /usr/lib/libQt5Widgets.so.5
#16 0x7f33c8b7c816 in QApplication::notify(QObject*, QEvent*) () at
/usr/lib/libQt5Widgets.so.5
#17 0x7f33ca1add98 in KisApplication::notify(QObject*, QEvent*) () at
/usr/lib/libkritaui.so.18
#18 0x7f33c7dfa1e0 in QCoreApplication::notifyInternal2(QObject*, QEvent