from:"Artur"

https://bugs.kde.org/show_bug.cgi?id=456238

--- Comment #5 from Artur Rudenko  ---
I also created minimal pygtk inhibit example and when I run it it says  "Is
currently blocking sleep and screen locking" however the flag that I set there
is GTK_APPLICATION_INHIBIT_SUSPEND

So the suspend inhibitor is also perceived as screen locking inhibitor, but gtk
documentation says that GTK_APPLICATION_INHIBIT_IDLE should block screen
locking and not GTK_APPLICATION_INHIBIT_SUSPEND
(https://docs.gtk.org/gtk4/flags.ApplicationInhibitFlags.html)

I didn't try inhibiting using qt or dbus though, but chromium most likely uses
gtk to do this

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

[plasmashell] [Bug 456238] Active job progress notifications inappropriately block screen locking

https://bugs.kde.org/show_bug.cgi?id=456238

--- Comment #4 from Artur Rudenko  ---
Created attachment 151980
  --> https://bugs.kde.org/attachment.cgi?id=151980=edit
pygtk4 minimal inhibit example (chromium most likely uses gtk to do this)

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

[plasmashell] [Bug 456238] Active job progress notifications inappropriately block screen locking

https://bugs.kde.org/show_bug.cgi?id=456238

--- Comment #3 from Artur Rudenko  ---
(In reply to Kai Uwe Broulik from comment #1)
> Check whether Chrome actually posts an inhibition. I think Chrome blocks
> suspend during downloads, but that shouldn't block the screen locker.

I added an attachment. Yes, it blocks sleep, but why would it also block screen
locking? I also installed plasma integration extension in chromium if it
matters.

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

[plasmashell] [Bug 456238] Active job progress notifications inappropriately block screen locking

https://bugs.kde.org/show_bug.cgi?id=456238

--- Comment #2 from Artur Rudenko  ---
Created attachment 151978
  --> https://bugs.kde.org/attachment.cgi?id=151978=edit
chrome blocking sleep and screen locking (but not screen dimming)

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

[frameworks-baloo] [Bug 457335] File search is case sensitive

2022-09-02 Thread Artur Rudenko

https://bugs.kde.org/show_bug.cgi?id=457335

--- Comment #7 from Artur Rudenko  ---
(In reply to tagwerk19 from comment #6)
> Does this cover all the questions? You've got baloo working again?

Yeah, it started to work properly. I think this bug status should be changed to
NOTABUG because the problem most likely is that baloo indexing was slow/buggy
and not that it was wrong. If I have new questions about baloo, should I ask
them in kde matrix channel or here?

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

[frameworks-baloo] [Bug 457335] File search is case sensitive

2022-08-23 Thread Artur Rudenko

https://bugs.kde.org/show_bug.cgi?id=457335

--- Comment #4 from Artur Rudenko  ---
(In reply to tagwerk19 from comment #3)
> (In reply to Artur Rudenko from comment #2)
> > This could be that newly created files remain unindexed
> > some time after the creation ...
> Yes, could be that baloo "got stuck". It relies on "iNotify" alerts to see
> when files are created, deleted or changed - and there are times when baloo
> misses something. 

Why does it miss? It's a baloo bug or inotify problem?

> > ... Maybe it would be better if dolphin did
> > fallback to the classic search when baloo can't find needed files?
> I'm not sure how Dolphin would know that baloo has not indexed particular
> files.

Maybe when iNotify notifies about a file created (or modified), baloo should
mark parent folder as un-indexed?


> In general though baloo should be quick at noticing new files and changed 
> file details. It knows "content indexing" is harder work and queues up "full 
> text" indexing (something you can watch happening with a "balooctl monitor")

But in real situation it is not. For example, try to unpack some archive and
then search in unpacked folder. Baloo won't find anything and i think in this
case dolphin should just use a general search in this folder (while adding it
to index queue), but it doesn't, and it ends up in useless search feature

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

[frameworks-baloo] [Bug 457335] File search is case sensitive

2022-08-21 Thread Artur Rudenko

https://bugs.kde.org/show_bug.cgi?id=457335

--- Comment #2 from Artur Rudenko  ---
(In reply to tagwerk19 from comment #1)
> For me, if I create SomeFileWithUppercase.txt and somefilewithuppercase.txt,
> I see both:
> 
> $ baloosearch -i somefilewithuppercase
> 140413fc01 /home/test/somefilewithuppercase.txt
> 140388fc01 /home/test/SomeFileWithUppercase.txt
> 
> and I see, with balooshow, that the index contains the two files:
> 
> $ balooshow -x somefilewithuppercase.txt
> 140413fc01 64513 1311763 somefilewithuppercase.txt
> [/home/test/somefilewithuppercase.txt]
> Mtime: 1660941653 2022-08-19T22:40:53
> Ctime: 1660941653 2022-08-19T22:40:53
> Cached properties:
> Line Count: 1
> 
> Internal Info
> Terms: Mplain Mtext T5 T8 X20-1 hello penguin
> File Name Terms: Fsomefilewithuppercase Ftxt
> XAttr Terms:
> lineCount: 1
> 
> $ balooshow -x SomeFileWithUppercase.txt
> 140388fc01 64513 1311624 SomeFileWithUppercase.txt
> [/home/test/SomeFileWithUppercase.txt]
> Mtime: 1660941644 2022-08-19T22:40:44
> Ctime: 1660941644 2022-08-19T22:40:44
> Cached properties:
> Line Count: 1
> 
> Internal Info
> Terms: Mplain Mtext T5 T8 X20-1 hello penguin
> File Name Terms: Fsomefilewithuppercase Ftxt
> XAttr Terms:
> lineCount: 1
> 
> The "File Name Terms" for both are held in lower case - baloo squashes terms
> down to lower case.
> 
> I did this test on Neon with ext4 filesystem, one that treats
> SomeFileWithUppercase.txt and somefilewithuppercase.txt as distinct.
> 
> The question is what might happen with other filesystems; for vfat if you
> try to create SomeFileWithUppercase.txt and then somefilewithuppercase.txt,
> you are creating just the one file.
> 
> You are on an arch setup? What filesystem are you using? (I'm assuming your
> files are on a local disc)

Yes, I'm on updated arch setup and it's ext4 on local disc, but now after I
reindexed everything, it works now (I searched using dolphin with file search
in settings). This could be that newly created files remain unindexed some time
after the creation. Maybe it would be better if dolphin did fallback to the
classic search when baloo can't find needed files?

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

[frameworks-baloo] [Bug 457335] New: File search is case sensitive

2022-07-31 Thread Artur Rudenko

https://bugs.kde.org/show_bug.cgi?id=457335

Bug ID: 457335
   Summary: File search is case sensitive
   Product: frameworks-baloo
   Version: unspecified
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: baloo-bugs-n...@kde.org
  Reporter: catcool...@gmail.com
  Target Milestone: ---

SUMMARY
***
NOTE: If you are reporting a crash, please try to attach a backtrace with debug
symbols.
See
https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
***
When searching files, typing lowercase name in search bar doesn't find the
appropriate uppercase files

STEPS TO REPRODUCE
1. Create SomeFileWithUppercase.txt
2. Create somefilewithuppercase.txt
3. Try to search "somefilewithuppercase"

OBSERVED RESULT
It finds only the file with lowercase name

EXPECTED RESULT
It finds both SomeFileWithUppercase.txt and  somefilewithuppercase.txt files

Operating System: Arch Linux
KDE Plasma Version: 5.25.3
KDE Frameworks Version: 5.96.0
Qt Version: 5.15.5
Kernel Version: 5.18.15-arch1-1 (64-bit)
Graphics Platform: X11
Processors: 16 × Intel® Core™ i7-10700F CPU @ 2.90GHz
Memory: 31.3 GiB of RAM
Graphics Processor: AMD Radeon RX 470 Graphics
Manufacturer: Gigabyte Technology Co., Ltd.
Product Name: Z490 GAMING X AX
System Version: -CF

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

[kwin] [Bug 457303] New: Drag and drop between xwayland and wayland apps doesn't work

2022-07-30 Thread Artur Rudenko

https://bugs.kde.org/show_bug.cgi?id=457303

Bug ID: 457303
   Summary: Drag and drop between xwayland and wayland apps
doesn't work
   Product: kwin
   Version: 5.25.3
  Platform: Archlinux Packages
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: wayland-generic
  Assignee: kwin-bugs-n...@kde.org
  Reporter: catcool...@gmail.com
  Target Milestone: ---

SUMMARY
***
NOTE: If you are reporting a crash, please try to attach a backtrace with debug
symbols.
See
https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
***


STEPS TO REPRODUCE
1.  Open chromium (via xwayland)
2.  Open telegram (4.x)
3.  Try to drag-n-drop some text from chromium to telegram


SOFTWARE/OS VERSIONS

Operating System: Arch Linux
KDE Plasma Version: 5.25.3
KDE Frameworks Version: 5.96.0
Qt Version: 5.15.5
Kernel Version: 5.18.15-arch1-1 (64-bit)
Graphics Platform: Wayland
Processors: 16 × Intel® Core™ i7-10700F CPU @ 2.90GHz
Memory: 31.3 GiB of RAM
Graphics Processor: AMD Radeon RX 470 Graphics
Manufacturer: Gigabyte Technology Co., Ltd.
Product Name: Z490 GAMING X AX
System Version: -CF

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

[plasmashell] [Bug 456239] New: [Wayland] In plasma, escape and left arrow closes the whole context menu, not sub-context menus

2022-07-02 Thread Artur Rudenko

https://bugs.kde.org/show_bug.cgi?id=456239

Bug ID: 456239
   Summary: [Wayland] In plasma, escape and left arrow closes the
whole context menu, not sub-context menus
   Product: plasmashell
   Version: 5.25.2
  Platform: Archlinux Packages
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: catcool...@gmail.com
CC: k...@davidedmundson.co.uk
  Target Milestone: 1.0

SUMMARY
***
NOTE: If you are reporting a crash, please try to attach a backtrace with debug
symbols.
See
https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
***


STEPS TO REPRODUCE
1. Open a context menu on plasma desktop
2. Hover some item with submenu, for example, "Icons"
3. Press left arrow or escape

OBSERVED RESULT
Current submenu is closed

EXPECTED RESULT
The whole context menu is closed

SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma:
(available in About System)
KDE Plasma Version: 5.25.2
KDE Frameworks Version: 5.95.0
Qt Version: 5.15.5

ADDITIONAL INFORMATION

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

[Powerdevil] [Bug 456238] New: Active notifications block auto lock

2022-07-02 Thread Artur Rudenko

https://bugs.kde.org/show_bug.cgi?id=456238

Bug ID: 456238
   Summary: Active notifications block auto lock
   Product: Powerdevil
   Version: 5.25.2
  Platform: Archlinux Packages
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: catcool...@gmail.com
CC: m...@ratijas.tk
  Target Milestone: ---

SUMMARY
***
NOTE: If you are reporting a crash, please try to attach a backtrace with debug
symbols.
See
https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
***

When there's an active notification i.e. it indicates some process progress
(like downloading in chrome), automatic lockscreen doesn't trigger, only
screensaver does

STEPS TO REPRODUCE
1. Set both dim screen and automatic lock timeout to 1 minute
2. Start a large file downloading in chromium with plasma integration addon

OBSERVED RESULT
After 1 minute, screen dimming triggers, but auto locking doesn't

EXPECTED RESULT
Both auto lock and screen dimming work after 1 minute

SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 5.25.2
KDE Frameworks Version: 5.95.0
Qt Version: 5.15.5

ADDITIONAL INFORMATION
I think this issue also can be randomly caused by regular notifications if
those appear and persist while auto locking timeout ends

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

[plasmashell] [Bug 456090] New: Panel popups are shown under kickoff (wayland)

2022-06-28 Thread Artur Rudenko

https://bugs.kde.org/show_bug.cgi?id=456090

Bug ID: 456090
   Summary: Panel popups are shown under kickoff  (wayland)
   Product: plasmashell
   Version: 5.25.2
  Platform: Archlinux Packages
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: catcool...@gmail.com
CC: k...@davidedmundson.co.uk
  Target Milestone: 1.0

SUMMARY
***
NOTE: If you are reporting a crash, please try to attach a backtrace with debug
symbols.
See
https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
***
When hovering an icon in panel while kickoff is open, kickoff overlaps popups
so they are not visible

STEPS TO REPRODUCE
1. Open kickoff
2. Hover an app icon in panel


OBSERVED RESULT
Popups are not visible

EXPECTED RESULT
Popups are visible

SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 5.25.2
KDE Frameworks Version: 5.95.0
Qt Version: 5.15.5

ADDITIONAL INFORMATION
Occurs only in wayland

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

[plasmashell] [Bug 456088] New: In kickoff, after moving an item, it freezes till clicked (wayland)

2022-06-28 Thread Artur Rudenko

https://bugs.kde.org/show_bug.cgi?id=456088

Bug ID: 456088
   Summary: In kickoff, after moving an item, it freezes till
clicked (wayland)
   Product: plasmashell
   Version: 5.25.2
  Platform: Archlinux Packages
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Application Launcher (Kickoff)
  Assignee: plasma-b...@kde.org
  Reporter: catcool...@gmail.com
CC: mikel5...@gmail.com, noaha...@gmail.com
  Target Milestone: 1.0

SUMMARY
***
NOTE: If you are reporting a crash, please try to attach a backtrace with debug
symbols.
See
https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
***
When moving an item in kickoff is done, it freezes until right or left clicked.
In case of left click, it open recently moved item, in case of right click, it
opens context menu and kickoff unfreezes.

STEPS TO REPRODUCE
1. Open kickoff
2. Move item

SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 5.25.2
KDE Frameworks Version: 5.95.0
Qt Version: 5.15.5

ADDITIONAL INFORMATION
This bug is wayland-only

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

[Powerdevil] [Bug 455360] Screen saver activates but auto lock screen doesn't (security issue?)

2022-06-23 Thread Artur Rudenko

https://bugs.kde.org/show_bug.cgi?id=455360

--- Comment #7 from Artur Rudenko  ---
(In reply to Artur Rudenko from comment #6)
> (In reply to Nate Graham from comment #5)
> > I can't remember if inhibitions are universal, or an app gets to choose what
> > to inhibit. Hopefully the Powerdevil developers can help some more.
> 
> Looks like I didn't understand the problem correctly. Lutris (which has the
> problem I described) uses Gtk.Application.inhibit with
> GTK_APPLICATION_INHIBIT_SUSPEND and GTK_APPLICATION_INHIBIT_IDLE flags. 
> GTK_APPLICATION_INHIBIT_IDLE flag should inhibit both dim screen and lock
> screen (if I understood correctly from
> https://docs.gtk.org/gtk3/flags.ApplicationInhibitFlags.html) but
> powerdevil(?) interprets it as "disable lock screen but not dim screen" so
> it's probably powerdevil's regression. But it only work not intended when an
> app is not in focus. 
> 
> It's a bug anyway because it either should ignore inhibitors for minimized
> apps or respect them fully anywhere except lock screen. Blocking auto
> locking and not screen dimming is confusing.

In addition, because of this bug, lutris now can't block screen dimming for
games anymore.

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

[Powerdevil] [Bug 455360] Screen saver activates but auto lock screen doesn't (security issue?)

2022-06-23 Thread Artur Rudenko

https://bugs.kde.org/show_bug.cgi?id=455360

--- Comment #6 from Artur Rudenko  ---
(In reply to Nate Graham from comment #5)
> I can't remember if inhibitions are universal, or an app gets to choose what
> to inhibit. Hopefully the Powerdevil developers can help some more.

Looks like I didn't understand the problem correctly. Lutris (which has the
problem I described) uses Gtk.Application.inhibit with
GTK_APPLICATION_INHIBIT_SUSPEND and GTK_APPLICATION_INHIBIT_IDLE flags. 
GTK_APPLICATION_INHIBIT_IDLE flag should inhibit both dim screen and lock
screen (if I understood correctly from
https://docs.gtk.org/gtk3/flags.ApplicationInhibitFlags.html) but powerdevil(?)
interprets it as "disable lock screen but not dim screen" so it's probably
powerdevil's regression. But it only work not intended when an app is not in
focus. 

It's a bug anyway because it either should ignore inhibitors for minimized apps
or respect them fully anywhere except lock screen. Blocking auto locking and
not screen dimming is confusing.

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

[kwin] [Bug 455526] New: Blur glitches started to appear in wayland again

2022-06-17 Thread Artur Rudenko

https://bugs.kde.org/show_bug.cgi?id=455526

Bug ID: 455526
   Summary: Blur glitches started to appear in wayland again
   Product: kwin
   Version: 5.25.0
  Platform: Archlinux Packages
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: wayland-generic
  Assignee: kwin-bugs-n...@kde.org
  Reporter: catcool...@gmail.com
  Target Milestone: ---

SUMMARY
***
NOTE: If you are reporting a crash, please try to attach a backtrace with debug
symbols.
See
https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
***
There was a glitches when you open a context menu above a surface with blur
effect,  and those were fixed in plasma 5.24 for both wayland and xorg, but
after updating to plasma 5.25 they started to appear again but only in wayland
session

STEPS TO REPRODUCE
1. Open konsole
2. Enable blur in konsole
3. Open a context menu in konsole

OBSERVED RESULT
Blur effect glitches

SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: Arch linux
(available in About System)
KDE Plasma Version:  5.25.0
KDE Frameworks Version: 5.95.0
Qt Version: 5.15.4

ADDITIONAL INFORMATION
AMD gpu. I can't reproduce that on plasma shell blurred menus, also I can't
reproduce it in konsole while recording through obs/pipewire

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

[plasmashell] [Bug 455360] Screen saver activates but auto lock screen doesn't (security issue?)

2022-06-17 Thread Artur Rudenko

https://bugs.kde.org/show_bug.cgi?id=455360

--- Comment #4 from Artur Rudenko  ---
(In reply to Nate Graham from comment #3)
> So yeah, it's doing what it says: blocking sleep and screen locking.
> 
> Are you saying that something different happened in the past? If so,
> specifically what? What changed, and when?

So it blocks sleep (system sleep or "suspend") and screen locking but not
display sleeping?

In the past (before plasma 5.24, it seems) I think it wouldn't trigger monitor
sleep at all when there's any inhibitor that blocks somethings even with
minimized window or locked screen.

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

[plasmashell] [Bug 455360] Screen saver activates but auto lock screen doesn't (security issue?)

2022-06-16 Thread Artur Rudenko

https://bugs.kde.org/show_bug.cgi?id=455360

--- Comment #2 from Artur Rudenko  ---
(In reply to Nate Graham from comment #1)
> Open the Battery & Brightness applet in your System Tray; what does it say
> about Chromium?

"Chromium is currently blocking sleep and screen locking (playing audio)" (when
minimized)
This bug also occurs when lutris blocks sleep with "running game" message.


Also, maybe it's little off topic, but in xorg firefox after minimizing removes
it's inhibitor, but for wayland it doesn't. That's weird because wayland also
sends minimize event? So it's probably either firefox wayland implementation
bug or xwayland bug?

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

[kwin] [Bug 448273] Kwin doesn't show "App is not responding" i.e. kwin_killer_helper doesn't work (wayland)

2022-06-15 Thread Artur Rudenko

https://bugs.kde.org/show_bug.cgi?id=448273

--- Comment #3 from Artur Rudenko  ---
Looks in wayland it works for xwayland apps

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

[plasmashell] [Bug 455360] New: Screen saver activates but auto lock screen doesn't (security issue?)

2022-06-15 Thread Artur Rudenko

https://bugs.kde.org/show_bug.cgi?id=455360

Bug ID: 455360
   Summary: Screen saver activates but auto lock screen doesn't
(security issue?)
   Product: plasmashell
   Version: 5.24.5
  Platform: Archlinux Packages
OS: Linux
Status: REPORTED
  Severity: major
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: catcool...@gmail.com
CC: k...@davidedmundson.co.uk
  Target Milestone: 1.0

SUMMARY
***
NOTE: If you are reporting a crash, please try to attach a backtrace with debug
symbols.
See
https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
***
After recent plasma's screensaver behavior changes, plasma now doesn't take
into account screensaver inhibitors that come from non focused apps. This is a
correct behavior, however, while screen dimming works in that case, automatic
screen locking doesn't work. Some apps do dim screen inhibiting randomly (for
example, steam) and this can lead to unexpected results, as the user may think
that if the screen turns off and nothing interferes with it, then the system
should be locked as specified in the settings, but because it doesn't trigger
screen locking, unwanted persons can access the OS.

STEPS TO REPRODUCE

1. Set both screen dimming and auto locking timeout to 1 minute
2. Open some video in a chromium (so it will inhibit screen dimming)
3. Minimize this window

OBSERVED RESULT
Screensaver works but after 1 minute OS is still unlocked

EXPECTED RESULT
Both screensaver and automatic screen locking works

SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: Arch Linux
(available in About System)
KDE Plasma Version: 5.24.5
KDE Frameworks Version: 5.95.0
Qt Version: 5.15.4

ADDITIONAL INFORMATION
Wayland/Xorg

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

[plasmashell] [Bug 449218] New: App icons can be moved from icon-only task manager to tray

https://bugs.kde.org/show_bug.cgi?id=449218

Bug ID: 449218
   Summary: App icons can be moved from icon-only task manager to
tray
   Product: plasmashell
   Version: 5.23.90
  Platform: Archlinux Packages
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Show Desktop/Minimize All
  Assignee: plasma-b...@kde.org
  Reporter: catcool...@gmail.com
  Target Milestone: 1.0

Created attachment 145975
  --> https://bugs.kde.org/attachment.cgi?id=145975=edit
Screen recording (xorg)

SUMMARY
***
NOTE: If you are reporting a crash, please try to attach a backtrace with debug
symbols.
See
https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
***

App icons can be moved to tray and after they moved, some phantom spacer
appears

STEPS TO REPRODUCE
1. Drag and drop icon to tray
2. Try it again but with another app

SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma:
(available in About System)
KDE Plasma Version: 5.23.90 
KDE Frameworks Version: 5. 90.0
Qt Version: 5.15.2

ADDITIONAL INFORMATION
See attachment

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

[kwin] [Bug 448515] No lock/unlock animation

https://bugs.kde.org/show_bug.cgi?id=448515

--- Comment #4 from Artur Rudenko  ---
(In reply to Vlad Zahorodnii from comment #1)
> hmm, can you clarify what you mean by unlock animation? as far as I know,
> kwin has never had an effect to animate unlocking of the screen

As you can see from attachment, plasma had a fade effect on locking and
unlocking. Though I didn't find it in desktop effects settings

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

[kwin] [Bug 448515] No lock/unlock animation

https://bugs.kde.org/show_bug.cgi?id=448515

--- Comment #3 from Artur Rudenko  ---
Created attachment 145974
  --> https://bugs.kde.org/attachment.cgi?id=145974=edit
arch plasma 5.23.90 unlock screen recording

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

[kwin] [Bug 448515] No lock/unlock animation

https://bugs.kde.org/show_bug.cgi?id=448515

--- Comment #2 from Artur Rudenko  ---
Created attachment 145973
  --> https://bugs.kde.org/attachment.cgi?id=145973=edit
manjaro plasma 5.23.4 screen recording

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

[krunner] [Bug 416145] Krunner doesn't immediately intercept keystrokes, leading the user to accidentally type text into whatever app is open

2022-01-25 Thread Artur Raczyński

https://bugs.kde.org/show_bug.cgi?id=416145

Artur Raczyński  changed:

   What|Removed |Added

 CC||artur.raczyn...@gmail.com

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

[dolphin] [Bug 440663] New Dolphin window or tab opened after compression/extraction when certain default options are disabled, or when the job is canceled, or when the Dolphin window that initiated i

2021-12-16 Thread Artur Paiva

https://bugs.kde.org/show_bug.cgi?id=440663

--- Comment #56 from Artur Paiva  ---
(In reply to smow from comment #55)
> (In reply to Pulse from comment #53)
> > openSUSE Tumbleweed
> > 5.23.3
> > 5.88.0
> > Ark - 21.08.3
> > Dolphin - 21.08.3
> 
> Looks like it was fixed in 21.12, but you're still on 21.08.

It wasn't. Upgraded Ark to 21.12.0 and the bug is still present. Had to
downgrade back to Ark 20.04.3. Dolphin can be updated suggesting that the bug
is related to Ark not Dolphin.

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

[dolphin] [Bug 440663] New Dolphin window or tab opened after compression/extraction when certain default options are disabled, or when the job is canceled, or when the Dolphin window that initiated i

2021-12-10 Thread Artur Paiva

https://bugs.kde.org/show_bug.cgi?id=440663

--- Comment #50 from Artur Paiva  ---
(In reply to Shay G from comment #49)
> The bug is in Ark or Dolphin? Just wondering if I can upgrade dolphin to
> 21.12.

Its on Ark, running dolphin 21.12.0 just fine, had to freeze ark on 21.04.3.

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

[dolphin] [Bug 440663] New Dolphin window or tab opened after compression/extraction when certain default options are disabled, or when the job is canceled, or when the Dolphin window that initiated i

2021-12-04 Thread Artur Paiva

https://bugs.kde.org/show_bug.cgi?id=440663

--- Comment #47 from Artur Paiva  ---
(In reply to Artur Paiva from comment #46)
> Confirmed here, and looks like a Ark issue not a Dolphin one. Downgrading
> Ark to 21.07.90 fixed the issue to me. Bug confirmed on:
> 
> Dolphin: 21.08.3
> Ark: 21.08.3
> Operating System: Arch Linux
> KDE Plasma Version: 5.23.4
> KDE Frameworks Version: 5.88.0
> Qt Version: 5.15.2
> Kernel Version: 5.15.6-zen2-1-zen (64-bit)
> Graphics Platform: X11
> Processors: 32 x AMD Ryzen 5950X 16-Core Processor
> Memory: 62.7 GiB of RAM
> Graphics Processor: NVIDIA GeForce RTX2060/PCIe/SSE2

A cache on dolphin made my previous result invalid, I've now checked every
package of Ark available for me and made sure that both dolphin and ark was
closed before each test. on <= 21.04.3 the issue doens't show up, on >=
21.07.80 the issue is present. Unfortunatelly I dont have packages for any
version in between those two to pinpoint a more accurate version. Hope it
helps.

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

[dolphin] [Bug 440663] New Dolphin window or tab opened after compression/extraction when certain default options are disabled, or when the job is canceled, or when the Dolphin window that initiated i

2021-12-04 Thread Artur Paiva

https://bugs.kde.org/show_bug.cgi?id=440663

Artur Paiva  changed:

   What|Removed |Added

 CC||dr.ho...@gmail.com

--- Comment #46 from Artur Paiva  ---
Confirmed here, and looks like a Ark issue not a Dolphin one. Downgrading Ark
to 21.07.90 fixed the issue to me. Bug confirmed on:

Dolphin: 21.08.3
Ark: 21.08.3
Operating System: Arch Linux
KDE Plasma Version: 5.23.4
KDE Frameworks Version: 5.88.0
Qt Version: 5.15.2
Kernel Version: 5.15.6-zen2-1-zen (64-bit)
Graphics Platform: X11
Processors: 32 x AMD Ryzen 5950X 16-Core Processor
Memory: 62.7 GiB of RAM
Graphics Processor: NVIDIA GeForce RTX2060/PCIe/SSE2

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

[Active Window Control] [Bug 443217] Bug trying to change widget settings

2021-10-02 Thread Artur

https://bugs.kde.org/show_bug.cgi?id=443217

--- Comment #1 from Artur  ---
(In reply to Artur from comment #0)
> Created attachment 142079 [details]
> Video demonstrathion
> 
> SUMMARY
> Artur Navitanyuk:Bug trying to change widget settings
> 
> STEPS TO REPRODUCE
> 1. Right Mouse click on top panel
> 2. Click on "Edit panel"
> 3. User should try to click on "Configure" in widget
> 
> OBSERVED RESULT
> Hard to hit the "Configure" button
> 
> EXPECTED RESULT
> 
> 
> SOFTWARE/OS VERSIONS
> Windows: 
> macOS: 
> Linux/KDE Plasma: Kali GNU/Linux Rolling x86_64
> (available in About System)
> KDE Plasma Version: 5.21.5
> KDE Frameworks Version: 5.86.0
> Qt Version: 5.15.2
> 
> ADDITIONAL INFORMATION

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

[Active Window Control] [Bug 443217] New: Bug trying to change widget settings

2021-10-02 Thread Artur

https://bugs.kde.org/show_bug.cgi?id=443217

Bug ID: 443217
   Summary: Bug trying to change widget settings
   Product: Active Window Control
   Version: unspecified
  Platform: Debian unstable
OS: Linux
Status: REPORTED
  Severity: minor
  Priority: NOR
 Component: General
  Assignee: zrenf...@gmail.com
  Reporter: mister-p...@outlook.com
CC: plasma-b...@kde.org
  Target Milestone: ---

Created attachment 142079
  --> https://bugs.kde.org/attachment.cgi?id=142079=edit
Video demonstrathion

SUMMARY
Artur Navitanyuk:Bug trying to change widget settings

STEPS TO REPRODUCE
1. Right Mouse click on top panel
2. Click on "Edit panel"
3. User should try to click on "Configure" in widget

OBSERVED RESULT
Hard to hit the "Configure" button

EXPECTED RESULT


SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 
KDE Frameworks Version: 
Qt Version: 

ADDITIONAL INFORMATION

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

[plasmashell] [Bug 443206] New: Dual monitor mixed refresh rate

2021-10-01 Thread Artur

https://bugs.kde.org/show_bug.cgi?id=443206

Bug ID: 443206
   Summary: Dual monitor mixed refresh rate
   Product: plasmashell
   Version: 5.22.4
  Platform: Manjaro
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: generic-performance
  Assignee: plasma-b...@kde.org
  Reporter: artur.bory...@gmail.com
  Target Milestone: 1.0

SUMMARY
I don't want to report a bug, but share what I've lately experienced. I have a
laptop to which I plug in external monitor. Built-in display has 144 Hz refresh
rate and the external one has 120 Hz although via HDMI it works only up to 60
Hz. I have Lenovo Legion 5i with RTX 2060 and integrated Intel GPU. I believe
I'm not the only one who experiences some stuttering while the external display
is connected. I got used to it, however, a few days ago I have turned on my
laptop without power plugged in and without HDMI plugged in. I've logged into
my account and then plugged in power and HDMI. Now the internal display looks
much smoother and the stuttering is a lot less noticeable. When I boot my
laptop and log in with external display connected, the stuttering is noticeable
again and the internal display is a lot more choppy.


STEPS TO REPRODUCE
1. Boot the laptop without power and with external display disconnected
2. Log in
3. Connect power and external display

OBSERVED RESULT
Only by following the steps the internal display is smooth. When booting and
logging in with power and external display connected, everything is choppy.

EXPECTED RESULT
It shouldn't matter if I boot with external monitor plugged in or not

SOFTWARE/OS VERSIONS
Linux: Manjaro
KDE Plasma Version: 5.22.5
KDE Frameworks Version: 5.86.0
Qt Version: 5.15.2

ADDITIONAL INFORMATION
I'm using X11 with nvidia drivers and optimus-manager.

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

[lattedock] [Bug 429140] Latte Dock is unclickable when PLASMA_USE_QT_SCALING is set to 1

2021-08-12 Thread Artur

https://bugs.kde.org/show_bug.cgi?id=429140

--- Comment #2 from Artur  ---
Yes, as well as previous reporter noted Latte Dock does not react to  mouse
input after manual restart after start up crash.

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

[lattedock] [Bug 429140] Latte Dock is unclickable when PLASMA_USE_QT_SCALING is set to 1

2021-08-12 Thread Artur

https://bugs.kde.org/show_bug.cgi?id=429140

--- Comment #1 from Artur  ---
Created attachment 140660
  --> https://bugs.kde.org/attachment.cgi?id=140660=edit
New crash information added by DrKonqi

latte-dock (0.10.0) using Qt 5.15.2

- What I was doing when the application crashed:

The application crashes during the system start up.

- Unusual behavior I noticed:

- Custom settings of the application:

I have set "PLASMA_USE_QT_SCALING=1" environment variable. This variable
changes behaviour of the application.

The application was crashing with the official ArchLinux package. I have
compiled it my self to get useful backtraces. The bug still present.

In addition I am using Window AppMenu (v0.7.1) and Active Window Control (v1.1)
widgets.

-- Backtrace (Reduced):
#4  QString::QString (other=..., this=this@entry=0x7ffdc61b0010) at
/usr/include/qt/QtCore/qstring.h:1093
#5  Latte::Layout::AbstractLayout::name (this=0x0) at
/usr/src/debug/latte-dock-0.10.0/app/layout/abstractlayout.cpp:204
#6  0x558f461e1ca7 in Latte::Layouts::Synchronizer::currentLayoutsNames
(this=) at
/usr/src/debug/latte-dock-0.10.0/app/layouts/synchronizer.cpp:202
#7  0x558f461ca653 in Latte::Layouts::Manager::currentLayoutsNames
(this=) at
/usr/src/debug/latte-dock-0.10.0/app/layouts/manager.cpp:155
#8  0x558f46227940 in Latte::Settings::Controller::Layouts::initLayouts
(this=this@entry=0x558f480525f0) at
/usr/src/debug/latte-dock-0.10.0/app/settings/settingsdialog/layoutscontroller.cpp:582

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

[lattedock] [Bug 429140] Latte Dock is unclickable when PLASMA_USE_QT_SCALING is set to 1

2021-08-12 Thread Artur

https://bugs.kde.org/show_bug.cgi?id=429140

Artur  changed:

   What|Removed |Added

 CC||art.and...@gmail.com

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

[systemsettings] [Bug 436015] Cursor size not syncing

2021-04-21 Thread Artur

https://bugs.kde.org/show_bug.cgi?id=436015

Artur  changed:

   What|Removed |Added

Version|unspecified |5.21.4

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

[systemsettings] [Bug 436015] New: Cursor size not syncing

2021-04-21 Thread Artur

https://bugs.kde.org/show_bug.cgi?id=436015

Bug ID: 436015
   Summary: Cursor size not syncing
   Product: systemsettings
   Version: unspecified
  Platform: Manjaro
OS: Linux
Status: REPORTED
  Severity: major
  Priority: NOR
 Component: kcm_sddm
  Assignee: k...@davidedmundson.co.uk
  Reporter: shkadinski...@gmail.com
CC: k...@david-redondo.de, plasma-b...@kde.org
  Target Milestone: ---

[ENG]

Manjaro KDE

The problem itself - when synchronizing SDDM with a theme that is installed by
the user, the cursor is not saved and it remains as small in SDDM as it was
Here is a link to the solution -
https://forum.kde.org/viewtopic.php?f=66=143080
Here is the solution itself - change the contents (namely, add at the end) of
the / etc / environment file. You need to add: "XCURSOR_SIZE = {xx}"
{xx} - depending on the scale: 24, 36, 48, 64. Checked only 36

--

[RU]

Manjaro KDE

Сама проблема - при синхронизации SDDM с темой которая установлена у
пользователя курсор не сохраняется и он остается такой же маленький в SDDM как
и был
Вот ссылка на решение - https://forum.kde.org/viewtopic.php?f=66=143080
Вот само решение - изменить содержимое (а именно в конец добавить) файла
/etc/environment. Добавить нужно:  "XCURSOR_SIZE={xx}"
{xx} - в зависимости от масштаба: 24, 36, 48, 64. Проверил только 36

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

[krusader] [Bug 428298] Krusader crashes after trying view (F3) LibreOffice Calc document

2020-11-11 Thread Artur

https://bugs.kde.org/show_bug.cgi?id=428298

Artur  changed:

   What|Removed |Added

 Status|NEEDSINFO   |RESOLVED

--- Comment #3 from Artur  ---
I confirm that version 2.8.0-dev "Bleeding Edge" does not have this problem.

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

[krusader] [Bug 428298] New: Krusader crashes after trying view (F3) LibreOffice Calc document

2020-10-26 Thread Artur

https://bugs.kde.org/show_bug.cgi?id=428298

Bug ID: 428298
   Summary: Krusader crashes after trying view (F3) LibreOffice
Calc document
   Product: krusader
   Version: unspecified
  Platform: openSUSE RPMs
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: krusader-bugs-n...@kde.org
  Reporter: l...@interia.pl
CC: krusader-bugs-n...@kde.org
  Target Milestone: ---

Application: krusader (2.7.2 "Peace of Mind")

Qt Version: 5.15.1
Frameworks Version: 5.75.0
Operating System: Linux 5.8.15-1-default x86_64
Windowing system: X11
Distribution: "openSUSE Tumbleweed"

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

Press F3 when LibreOffice spreadsheet document (*.ods) is selected.

The crash can be reproduced every time.

-- Backtrace:
Application: Krusader (krusader), signal: Segmentation fault

[New LWP 23676]
[New LWP 23677]
[New LWP 23678]
[New LWP 23679]
[New LWP 23680]
[New LWP 23684]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib64/libthread_db.so.1".
0x7f0e214fbe7f in poll () from /lib64/libc.so.6
[Current thread is 1 (Thread 0x7f0e1fb65300 (LWP 23673))]

Thread 7 (Thread 0x7f0e0b7fe640 (LWP 23684)):
#0  0x7f0e203d2488 in ?? () from /usr/lib64/libglib-2.0.so.0
#1  0x7f0e203d3a33 in g_main_context_prepare () from
/usr/lib64/libglib-2.0.so.0
#2  0x7f0e203d451b in ?? () from /usr/lib64/libglib-2.0.so.0
#3  0x7f0e203d470f in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#4  0x7f0e21c015cb in QEventDispatcherGlib::processEvents
(this=0x7f0dfb60, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#5  0x7f0e21ba8a1b in QEventLoop::exec (this=this@entry=0x7f0e0b7fdc70,
flags=..., flags@entry=...) at
../../include/QtCore/../../src/corelib/global/qflags.h:141
#6  0x7f0e219c97ce in QThread::exec (this=) at
../../include/QtCore/../../src/corelib/global/qflags.h:121
#7  0x7f0e22daba27 in ?? () from /usr/lib64/libQt5DBus.so.5
#8  0x7f0e219ca911 in QThreadPrivate::start (arg=0x7f0e22e18d80) at
thread/qthread_unix.cpp:329
#9  0x7f0e210fbeb1 in start_thread () from /lib64/libpthread.so.0
#10 0x7f0e21506ccf in clone () from /lib64/libc.so.6

Thread 6 (Thread 0x7f0e037fe640 (LWP 23680)):
#0  0x7f0e21102082 in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7f0e16e42fbb in ?? () from /usr/lib64/dri/r600_dri.so
#2  0x7f0e16e42477 in ?? () from /usr/lib64/dri/r600_dri.so
#3  0x7f0e210fbeb1 in start_thread () from /lib64/libpthread.so.0
#4  0x7f0e21506ccf in clone () from /lib64/libc.so.6

Thread 5 (Thread 0x7f0e0bfff640 (LWP 23679)):
#0  0x7f0e21102082 in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7f0e16e42fbb in ?? () from /usr/lib64/dri/r600_dri.so
#2  0x7f0e16e42477 in ?? () from /usr/lib64/dri/r600_dri.so
#3  0x7f0e210fbeb1 in start_thread () from /lib64/libpthread.so.0
#4  0x7f0e21506ccf in clone () from /lib64/libc.so.6

Thread 4 (Thread 0x7f0e10b03640 (LWP 23678)):
#0  0x7f0e21102082 in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7f0e16e42fbb in ?? () from /usr/lib64/dri/r600_dri.so
#2  0x7f0e16e42477 in ?? () from /usr/lib64/dri/r600_dri.so
#3  0x7f0e210fbeb1 in start_thread () from /lib64/libpthread.so.0
#4  0x7f0e21506ccf in clone () from /lib64/libc.so.6

Thread 3 (Thread 0x7f0e11304640 (LWP 23677)):
#0  0x7f0e21102082 in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7f0e16e42fbb in ?? () from /usr/lib64/dri/r600_dri.so
#2  0x7f0e16e42477 in ?? () from /usr/lib64/dri/r600_dri.so
#3  0x7f0e210fbeb1 in start_thread () from /lib64/libpthread.so.0
#4  0x7f0e21506ccf in clone () from /lib64/libc.so.6

Thread 2 (Thread 0x7f0e11b05640 (LWP 23676)):
#0  0x7f0e21102082 in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7f0e16e42fbb in ?? () from /usr/lib64/dri/r600_dri.so
#2  0x7f0e16e42477 in ?? () from /usr/lib64/dri/r600_dri.so
#3  0x7f0e210fbeb1 in start_thread () from /lib64/libpthread.so.0
#4  0x7f0e21506ccf in clone () from /lib64/libc.so.6

Thread 1 (Thread 0x7f0e1fb65300 (LWP 23673)):
[KCrash Handler]
#4  QHashData::nextNode (node=node@entry=0x55f5a1b28670) at tools/qhash.cpp:591
#5  0x7f0e094973cb in QHash::const_iterator::operator++ (this=) at
/usr/include/qt5/QtCore/qhash.h:425
#6  QSet::const_iterator::operator++ (this=) at
/usr/include/qt5/QtCore/qset.h:174
#7  JobTracker::~JobTracker (this=, this=) at
/usr/src/debug/ark-20.08.2-1.1.x86_64/part/jobtracker.cpp:41
#8  0x7f0e09497429 in JobTracker::~JobTracker (this=,
this=) at
/usr/src/debug/ark-20.08.2-1.1.x86_64/part/jobtracker.cpp:44
#9  0x7f0e21bd3c7e in QObjectPrivate::deleteChildren

[frameworks-knewstuff] [Bug 414570] Items installed from KDE Store are not listed while "Installed" radio button is selected in "Get New Window Decorations..." window

2020-05-27 Thread Artur Oliveira

https://bugs.kde.org/show_bug.cgi?id=414570

Artur Oliveira  changed:

   What|Removed |Added

 CC||artur...@protonmail.com

--- Comment #5 from Artur Oliveira  ---
Same thing here! Using Kubuntu 20.04.

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

[valgrind] [Bug 399584] Support macOS Mojave (10.14)

2020-03-20 Thread Artur Troian

https://bugs.kde.org/show_bug.cgi?id=399584

Artur Troian  changed:

   What|Removed |Added

 CC||troian...@gmail.com

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

[ksmserver] [Bug 361073] Session Logout and Session Switch User (from application launcher) get wrong position on the dialog.

2020-02-23 Thread Artur O.

https://bugs.kde.org/show_bug.cgi?id=361073

--- Comment #3 from Artur O.  ---
(In reply to Gregor Mi from comment #1)
> Hello Artur, thanks for the report. Two years have passed now. Is this
> report still valid or did anything change for the better in the meantime?

Not sure but don't think so, since then i have moved to Gnome environment. But
can see if i can get KDE going and test.

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

[kdevelop] [Bug 410131] New: performing pointer arithmetic on a null pointer has undefined behavior if the offset is nonzero

2019-07-23 Thread Artur

https://bugs.kde.org/show_bug.cgi?id=410131

Bug ID: 410131
   Summary: performing pointer arithmetic on a null pointer has
undefined behavior if the offset is nonzero
   Product: kdevelop
   Version: git master
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: minor
  Priority: NOR
 Component: Language Support: QML/JavaScript
  Assignee: kdevelop-bugs-n...@kde.org
  Reporter: kdebugzi...@ebasoft.com.pl
  Target Milestone: ---

plugins/qmljs/duchain/frameworks/nodejs.cpp:78:36:
warning: performing pointer arithmetic on a null pointer has undefined behavior
if the offset is nonzero
(QmlJS::AST::Node*)nullptr + index,
~~ ^

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

[kdevplatform] [Bug 410130] New: explicitly assigning value of variable to itself

2019-07-23 Thread Artur

https://bugs.kde.org/show_bug.cgi?id=410130

Bug ID: 410130
   Summary: explicitly assigning value of variable to itself
   Product: kdevplatform
   Version: git master
  Platform: unspecified
OS: Linux
Status: REPORTED
  Severity: minor
  Priority: NOR
 Component: util
  Assignee: kdevelop-bugs-n...@kde.org
  Reporter: kdebugzi...@ebasoft.com.pl
  Target Milestone: ---

kdevplatform/util/dbus_socket_transformer/main.cpp:253:14:
warning: explicitly assigning value of variable of type 'std::string' (aka
'basic_string') to itself
path = path;
 ^ 

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

[okular] [Bug 403632] Cannot handle some fields in PDF forms.

2019-01-26 Thread Artur R. Czechowski

https://bugs.kde.org/show_bug.cgi?id=403632

--- Comment #2 from Artur R. Czechowski  ---
Probably you are right. I've finally found a software where it works (guess,
what is it...) and, indeed, part of the first field is being copied to second
field.

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

[okular] [Bug 403632] New: Cannot handle some fields in PDF forms.

2019-01-26 Thread Artur R. Czechowski

https://bugs.kde.org/show_bug.cgi?id=403632

Bug ID: 403632
Summary: Cannot handle some fields in PDF forms.
Product: okular
Version: 1.3.2
Platform: Debian unstable
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: PDF backend
Assignee: okular-de...@kde.org
Reporter: artu...@hell.pl
Target Milestone: ---

Created attachment 117664
--> https://bugs.kde.org/attachment.cgi?id=117664=edit
PDF form not being handled properly

SUMMARY
There is a PDF form to Tax Office in The Netherlands which is not being handled
properly. The file is available at
https://www.belastingdienst.nl/wps/wcm/connect/bldcontentnl/themaoverstijgend/programmas_en_formulieren/aangifte-melding-opgaaf-bpm
- the first link, titled Aangifte/melding/opgaaf bpm (pdf - 427kB). I have
attached the file for reference as well.

STEPS TO REPRODUCE
1. Open attached file in okular
2. Goto second fillable field "Documentkenmerk (Laatste 7 posities van het
VIN)"
3. Try to enter anything into this field.

OBSERVED RESULT
Nothing happens

EXPECTED RESULT
One should be able to enter data into this field.

It might be possible this field is being auto filled after filling the first
one, for VIN, however this scenario does not work as well. In that case it
could be related to #344776.

SOFTWARE/OS VERSIONS

Linux/KDE Plasma: Debian GNU/Linux buster/sid (unstable)
KDE Plasma Version: 5.13.2
KDE Frameworks Version: 5.47.0
Qt Version: 5.11.1

ADDITIONAL INFORMATION
Okular 1.3.2 installed from Debian package okular 4:17.12.2-2.1

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

[juk] [Bug 279584] JuK crashed on File/Reload.

2018-11-02 Thread Artur Zaprzała

https://bugs.kde.org/show_bug.cgi?id=279584

Artur Zaprzała  changed:

   What|Removed |Added

 Status|NEEDSINFO   |REPORTED
 Resolution|WAITINGFORINFO  |---

--- Comment #2 from Artur Zaprzała  ---
I can't reproduce this bug any more.

Juk 18.04.3
KDE Frameworks 5.48.0
Qt 5.11.1
Fedora 28

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

[plasmashell] [Bug 399903] Plasma crashed after adding the application to Application Menu Bar

2018-10-16 Thread Artur Tretiak

https://bugs.kde.org/show_bug.cgi?id=399903

--- Comment #1 from Artur Tretiak  ---
Created attachment 115693
  --> https://bugs.kde.org/attachment.cgi?id=115693=edit
Application Menu Bar Demonstration

That how my App Menu Bar seems like.

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

[plasmashell] [Bug 399903] New: Plasma crashed after adding the application to Application Menu Bar

2018-10-16 Thread Artur Tretiak

https://bugs.kde.org/show_bug.cgi?id=399903

Bug ID: 399903
   Summary: Plasma crashed after adding the application to
Application Menu Bar
   Product: plasmashell
   Version: 5.14.0
  Platform: Archlinux Packages
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: sti...@protonmail.com
CC: plasma-b...@kde.org
  Target Milestone: 1.0

Application: plasmashell (5.14.0)

Qt Version: 5.11.2
Frameworks Version: 5.50.0
Operating System: Linux 4.18.12-arch1-1-ARCH x86_64
Distribution (Platform): Archlinux Packages

-- Information about the crash:
- What I was doing when the application crashed:
Dropped Application(any) to Application Menu Bar

I tried to place (and that was placed after crush) Battle for Wesnoth from
steam.
Also any other apps placing can cause this crash.

The crash can be reproduced sometimes.

-- Backtrace:
Application: Plasma (plasmashell), signal: Segmentation fault
Using host libthread_db library "/usr/lib/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f7f6ba970c0 (LWP 695))]

Thread 16 (Thread 0x7f7f19cf5700 (LWP 1785)):
#0  0x7f7f71dcdbb1 in poll () at /usr/lib/libc.so.6
#1  0x7f7f55bb1673 in  () at /usr/lib/libpulse.so.0
#2  0x7f7f55ba2990 in pa_mainloop_poll () at /usr/lib/libpulse.so.0
#3  0x7f7f55ba2fe0 in pa_mainloop_iterate () at /usr/lib/libpulse.so.0
#4  0x7f7f55ba3091 in pa_mainloop_run () at /usr/lib/libpulse.so.0
#5  0x7f7f55bb15ae in  () at /usr/lib/libpulse.so.0
#6  0x7f7f5574b9fc in  () at /usr/lib/pulseaudio/libpulsecommon-12.2.so
#7  0x7f7f7100ca9d in start_thread () at /usr/lib/libpthread.so.0
#8  0x7f7f71dd8a43 in clone () at /usr/lib/libc.so.6

Thread 15 (Thread 0x7f7f1b7fe700 (LWP 1241)):
#0  0x7f7f71012afc in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7f7f720f471c in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/libQt5Core.so.5
#2  0x7f7f56ae7469 in
ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*,
bool, bool, bool) () at /usr/lib/libKF5ThreadWeaver.so.5
#3  0x7f7f56aeb339 in  () at /usr/lib/libKF5ThreadWeaver.so.5
#4  0x7f7f56ae652d in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib/libKF5ThreadWeaver.so.5
#5  0x7f7f56aeb392 in  () at /usr/lib/libKF5ThreadWeaver.so.5
#6  0x7f7f56ae652d in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib/libKF5ThreadWeaver.so.5
#7  0x7f7f56ae9389 in ThreadWeaver::Thread::run() () at
/usr/lib/libKF5ThreadWeaver.so.5
#8  0x7f7f720f3f65 in  () at /usr/lib/libQt5Core.so.5
#9  0x7f7f7100ca9d in start_thread () at /usr/lib/libpthread.so.0
#10 0x7f7f71dd8a43 in clone () at /usr/lib/libc.so.6

Thread 14 (Thread 0x7f7f1bfff700 (LWP 1240)):
#0  0x7f7f71012afc in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7f7f720f471c in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/libQt5Core.so.5
#2  0x7f7f56ae7469 in
ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*,
bool, bool, bool) () at /usr/lib/libKF5ThreadWeaver.so.5
#3  0x7f7f56aeb339 in  () at /usr/lib/libKF5ThreadWeaver.so.5
#4  0x7f7f56ae652d in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib/libKF5ThreadWeaver.so.5
#5  0x7f7f56aeb392 in  () at /usr/lib/libKF5ThreadWeaver.so.5
#6  0x7f7f56ae652d in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib/libKF5ThreadWeaver.so.5
#7  0x7f7f56ae9389 in ThreadWeaver::Thread::run() () at
/usr/lib/libKF5ThreadWeaver.so.5
#8  0x7f7f720f3f65 in  () at /usr/lib/libQt5Core.so.5
#9  0x7f7f7100ca9d in start_thread () at /usr/lib/libpthread.so.0
#10 0x7f7f71dd8a43 in clone () at /usr/lib/libc.so.6

Thread 13 (Thread 0x7f7f30dea700 (LWP 1239)):
#0  0x7f7f71012afc in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7f7f720f471c in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/libQt5Core.so.5
#2  0x7f7f56ae7469 in
ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*,
bool, bool, bool) () at /usr/lib/libKF5ThreadWeaver.so.5
#3  0x7f7f56aeb339 in  () at /usr/lib/libKF5ThreadWeaver.so.5
#4  0x7f7f56ae652d in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib/libKF5ThreadWeaver.so.5
#5  0x7f7f56aeb392 in  () at /usr/lib/libKF5ThreadWeaver.so.5
#6  0x7f7f56ae652d in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib/libKF5ThreadWeaver.so.5
#7  0x7f7f56ae9389 in ThreadWeaver::Thread::run() () at
/usr/lib/libKF5ThreadWeaver.so.5
#8  0x7f7f720f3f65 in  () at /usr/lib/libQt5Core.so.5
#9

[krita] [Bug 391265] New: Mouse Mode mapping goes into Pen Mode

2018-03-01 Thread Artur Ryba

https://bugs.kde.org/show_bug.cgi?id=391265

Bug ID: 391265
   Summary: Mouse Mode mapping goes into Pen Mode
   Product: krita
   Version: 3.3.3
  Platform: MS Windows
OS: MS Windows
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: CPU Canvas
  Assignee: krita-bugs-n...@kde.org
  Reporter: artur.ryba...@gmail.com
  Target Milestone: ---

Generally my tablet mapping is set to Mouse mode mapping but when I open Krita
and hover my pointer over blank page to draw something it automatically changes
my tablet mapping into Pen Mode, which I truly don't like, but when I hover for
instance over tools Krita is making my tablet mapping normally (Mouse mode). I
dont have any idea how to solve it. Im using Wacom One.

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

[kwin] [Bug 387308] Kwin crash when getting popup in Steam

2017-11-26 Thread Artur O .

https://bugs.kde.org/show_bug.cgi?id=387308

--- Comment #2 from Artur O. <commander.alch...@gmail.com> ---
(In reply to Martin Flöser from comment #1)
> Unfortunately the backtrace is lacking debug symbols. Due to that we are
> unable to investigate. If you are able to reproduce please attach a new
> backtrace with full debug symbols.

Hm, issue is that there are no debug symbols in repo. The is a qt-debug but
kwin is not there and building kwin is quite a pain. The is a kwin-git in aur
however i would guess that i need everything in git then not just kwin and it's
make depends?

Or do you know any repo from KDE that supplies with debug symbols for Arch?

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

[kwin] [Bug 387308] New: Kwin crash when getting popup in Steam

2017-11-25 Thread Artur O .

https://bugs.kde.org/show_bug.cgi?id=387308

Bug ID: 387308
   Summary: Kwin crash when getting popup in Steam
   Product: kwin
   Version: 5.11.3
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kwin-bugs-n...@kde.org
  Reporter: commander.alch...@gmail.com
  Target Milestone: ---

Application: kwin_x11 (5.11.3)

Qt Version: 5.9.3
Frameworks Version: 5.40.0
Operating System: Linux 4.13.12-1-ARCH x86_64
Distribution: "Arch Linux"

-- Information about the crash:
- What I was doing when the application crashed:
Seems to trigger each time i get a popup in steam after trying to launch a
game. Seems kwin just hangs and i have to call kill -11 from another tty.

The crash can be reproduced every time.

-- Backtrace:
Application: KWin (kwin_x11), signal: Segmentation fault
Using host libthread_db library "/usr/lib/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f6360d01840 (LWP 793))]

Thread 6 (Thread 0x7f63291e9700 (LWP 3069)):
#0  0x7f636069f076 in ppoll () at /usr/lib/libc.so.6
#1  0x7f635dcd4d23 in qt_safe_poll(pollfd*, unsigned long, timespec const*)
() at /usr/lib/libQt5Core.so.5
#2  0x7f635dcd64bf in
QEventDispatcherUNIX::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#3  0x7f635dc7c99b in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#4  0x7f635da9527e in QThread::exec() () at /usr/lib/libQt5Core.so.5
#5  0x7f635da9a1cb in  () at /usr/lib/libQt5Core.so.5
#6  0x7f635963908a in start_thread () at /usr/lib/libpthread.so.0
#7  0x7f63606a947f in clone () at /usr/lib/libc.so.6

Thread 5 (Thread 0x7f63231ee700 (LWP 1059)):
#0  0x7f635963f38d in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7f635cbf2ef7 in  () at /usr/lib/libQt5Script.so.5
#2  0x7f635cbf2f39 in  () at /usr/lib/libQt5Script.so.5
#3  0x7f635963908a in start_thread () at /usr/lib/libpthread.so.0
#4  0x7f63606a947f in clone () at /usr/lib/libc.so.6

Thread 4 (Thread 0x7f633e352700 (LWP 1026)):
#0  0x7f636069f076 in ppoll () at /usr/lib/libc.so.6
#1  0x7f635dcd4d23 in qt_safe_poll(pollfd*, unsigned long, timespec const*)
() at /usr/lib/libQt5Core.so.5
#2  0x7f635dcd64bf in
QEventDispatcherUNIX::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#3  0x7f635dc7c99b in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#4  0x7f635da9527e in QThread::exec() () at /usr/lib/libQt5Core.so.5
#5  0x7f6358140cf9 in  () at /usr/lib/libQt5Qml.so.5
#6  0x7f635da9a1cb in  () at /usr/lib/libQt5Core.so.5
#7  0x7f635963908a in start_thread () at /usr/lib/libpthread.so.0
#8  0x7f63606a947f in clone () at /usr/lib/libc.so.6

Thread 3 (Thread 0x7f6344f4f700 (LWP 857)):
#0  0x7f636069f076 in ppoll () at /usr/lib/libc.so.6
#1  0x7f635dcd4d23 in qt_safe_poll(pollfd*, unsigned long, timespec const*)
() at /usr/lib/libQt5Core.so.5
#2  0x7f635dcd64bf in
QEventDispatcherUNIX::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#3  0x7f635dc7c99b in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#4  0x7f635da9527e in QThread::exec() () at /usr/lib/libQt5Core.so.5
#5  0x7f63572e2376 in  () at /usr/lib/libQt5DBus.so.5
#6  0x7f635da9a1cb in  () at /usr/lib/libQt5Core.so.5
#7  0x7f635963908a in start_thread () at /usr/lib/libpthread.so.0
#8  0x7f63606a947f in clone () at /usr/lib/libc.so.6

Thread 2 (Thread 0x7f63475db700 (LWP 817)):
#0  0x7f636069ef7b in poll () at /usr/lib/libc.so.6
#1  0x7f635f79c8e0 in  () at /usr/lib/libxcb.so.1
#2  0x7f635f79e679 in xcb_wait_for_event () at /usr/lib/libxcb.so.1
#3  0x7f63484b690a in  () at /usr/lib/libQt5XcbQpa.so.5
#4  0x7f635da9a1cb in  () at /usr/lib/libQt5Core.so.5
#5  0x7f635963908a in start_thread () at /usr/lib/libpthread.so.0
#6  0x7f63606a947f in clone () at /usr/lib/libc.so.6

Thread 1 (Thread 0x7f6360d01840 (LWP 793)):
[KCrash Handler]
#5  0x7f636069f076 in ppoll () at /usr/lib/libc.so.6
#6  0x7f635dcd4d23 in qt_safe_poll(pollfd*, unsigned long, timespec const*)
() at /usr/lib/libQt5Core.so.5
#7  0x7f635dcd64bf in
QEventDispatcherUNIX::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#8  0x7f634851bace in  () at /usr/lib/libQt5XcbQpa.so.5
#9  0x7f635dc7c99b in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#10 0x7f635dc859e8 in QCoreApplication::exec() () at
/usr/lib/libQt5Core.so.5
#11 0x7f63609736e3 in kdemain () at /usr/lib/libkdeinit5_kwin_x11.so
#12 0x7f63605d3f6a in __libc_start_main () at /usr/lib/libc.so.6
#13 0x563bd3c4d7aa in _start ()

Possible duplicates by query: bug 387289, bug 387227, bug 386888, bug 386018,
bug 385922.

Reported using DrKonqi

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

[kwin] [Bug 383965] New: Kwin crashes while debugging an opengl app in qtcreator

2017-08-24 Thread Artur K .

https://bugs.kde.org/show_bug.cgi?id=383965

Bug ID: 383965
   Summary: Kwin crashes while debugging an opengl app in
qtcreator
   Product: kwin
   Version: 5.10.4
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kwin-bugs-n...@kde.org
  Reporter: nemer...@gmail.com
  Target Milestone: ---

Application: kwin_x11 (5.10.4)

Qt Version: 5.9.1
Frameworks Version: 5.37.0
Operating System: Linux 4.12.8-2-ARCH x86_64
Distribution (Platform): Archlinux Packages

-- Information about the crash:
Attempted to 'kill' debugged application after it crashed. Switched window to
the application - kwin crashed as a result.

-- Backtrace:
Application: KWin (kwin_x11), signal: Segmentation fault
Using host libthread_db library "/usr/lib/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f3f6c424840 (LWP 591))]

Thread 6 (Thread 0x7f3ea8938700 (LWP 855)):
#0  0x7f3f64f841ad in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7f3f691bc5ec in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/libQt5Core.so.5
#2  0x7f3f64171ae8 in  () at /usr/lib/libQt5Quick.so.5
#3  0x7f3f64171f4a in  () at /usr/lib/libQt5Quick.so.5
#4  0x7f3f691bb15b in  () at /usr/lib/libQt5Core.so.5
#5  0x7f3f64f7e049 in start_thread () at /usr/lib/libpthread.so.0
#6  0x7f3f6bdedf0f in clone () at /usr/lib/libc.so.6

Thread 5 (Thread 0x7f3eb8eeb700 (LWP 748)):
#0  0x7f3f6bde3f76 in ppoll () at /usr/lib/libc.so.6
#1  0x7f3f693f4ba3 in qt_safe_poll(pollfd*, unsigned long, timespec const*)
() at /usr/lib/libQt5Core.so.5
#2  0x7f3f693f633f in
QEventDispatcherUNIX::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#3  0x7f3f6939cffb in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#4  0x7f3f691b640e in QThread::exec() () at /usr/lib/libQt5Core.so.5
#5  0x7f3f63a7f1d5 in  () at /usr/lib/libQt5Qml.so.5
#6  0x7f3f691bb15b in  () at /usr/lib/libQt5Core.so.5
#7  0x7f3f64f7e049 in start_thread () at /usr/lib/libpthread.so.0
#8  0x7f3f6bdedf0f in clone () at /usr/lib/libc.so.6

Thread 4 (Thread 0x7f3f3bfff700 (LWP 663)):
#0  0x7f3f64f841ad in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7f3f68313b04 in  () at /usr/lib/libQt5Script.so.5
#2  0x7f3f68313b49 in  () at /usr/lib/libQt5Script.so.5
#3  0x7f3f64f7e049 in start_thread () at /usr/lib/libpthread.so.0
#4  0x7f3f6bdedf0f in clone () at /usr/lib/libc.so.6

Thread 3 (Thread 0x7f3f498fe700 (LWP 655)):
#0  0x7f3f6bde3f76 in ppoll () at /usr/lib/libc.so.6
#1  0x7f3f693f4ba3 in qt_safe_poll(pollfd*, unsigned long, timespec const*)
() at /usr/lib/libQt5Core.so.5
#2  0x7f3f693f633f in
QEventDispatcherUNIX::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#3  0x7f3f6939cffb in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#4  0x7f3f691b640e in QThread::exec() () at /usr/lib/libQt5Core.so.5
#5  0x7f3f63a7f1d5 in  () at /usr/lib/libQt5Qml.so.5
#6  0x7f3f691bb15b in  () at /usr/lib/libQt5Core.so.5
#7  0x7f3f64f7e049 in start_thread () at /usr/lib/libpthread.so.0
#8  0x7f3f6bdedf0f in clone () at /usr/lib/libc.so.6

Thread 2 (Thread 0x7f3f4bfff700 (LWP 619)):
#0  0x7f3f6bde3f76 in ppoll () at /usr/lib/libc.so.6
#1  0x7f3f693f4ba3 in qt_safe_poll(pollfd*, unsigned long, timespec const*)
() at /usr/lib/libQt5Core.so.5
#2  0x7f3f693f633f in
QEventDispatcherUNIX::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#3  0x7f3f6939cffb in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#4  0x7f3f691b640e in QThread::exec() () at /usr/lib/libQt5Core.so.5
#5  0x7f3f62c22396 in  () at /usr/lib/libQt5DBus.so.5
#6  0x7f3f691bb15b in  () at /usr/lib/libQt5Core.so.5
#7  0x7f3f64f7e049 in start_thread () at /usr/lib/libpthread.so.0
#8  0x7f3f6bdedf0f in clone () at /usr/lib/libc.so.6

Thread 1 (Thread 0x7f3f6c424840 (LWP 591)):
[KCrash Handler]
#5  0x0050 in  ()
#6  0x7f3f6b8c893d in KWin::Workspace::constrainedStackingOrder() () at
/usr/lib/libkwin.so.5
#7  0x7f3f6b8c9721 in KWin::Workspace::updateStackingOrder(bool) () at
/usr/lib/libkwin.so.5
#8  0x7f3f6b8c9ac1 in KWin::Workspace::blockStackingUpdates(bool) () at
/usr/lib/libkwin.so.5
#9  0x7f3f6b870294 in KWin::Client::destroyClient() () at
/usr/lib/libkwin.so.5
#10 0x7f3f6b8d9bff in
KWin::Client::unmapNotifyEvent(xcb_unmap_notify_event_t*) () at
/usr/lib/libkwin.so.5
#11 0x7f3f6b8dd904 in KWin::Client::windowEvent(xcb_generic_event_t*) () at
/usr/lib/libkwin.so.5
#12 0x7f3f6b8ded60 in KWin::Workspace::workspaceEvent(xcb_generic_event_t*)
() at /usr/lib/libkwin.so.5
#13 0x7f3f6939ba1f in
QAbstractEventDispatcher::filterNativeEvent(QByteArray const&, void*, long*) ()
at

[kdevelop] [Bug 382901] Kdevelop 5.1.1 crashes when typing anything in .c/.h file

2017-07-30 Thread Artur Langner

https://bugs.kde.org/show_bug.cgi?id=382901

--- Comment #4 from Artur Langner <k...@xene.eu> ---
After a whole day of use I had no crashes.
Whole system was built with binutils 2.25.1

Rest of emerge --info :

ACCEPT_KEYWORDS="amd64"
ACCEPT_LICENSE="*"
CBUILD="x86_64-pc-linux-gnu"
CFLAGS="-O2 -pipe -march=native -g"
CHOST="x86_64-pc-linux-gnu"
CONFIG_PROTECT="/etc /etc/stunnel/stunnel.conf
/usr/lib64/libreoffice/program/sofficerc /usr/share/config /usr/share/easy-rsa
/usr/share/gnupg/qualified.txt /usr/share/themes/oxygen-gtk/gtk-2.0"
CONFIG_PROTECT_MASK="/etc/ca-certificates.conf /etc/dconf /etc/env.d
/etc/fonts/fonts.conf /etc/gconf /etc/gentoo-release
/etc/php/apache2-php7.0/ext-active/ /etc/php/cgi-php7.0/ext-active/
/etc/php/cli-php7.0/ext-active/ /etc/revdep-rebuild /etc/sandbox.d
/etc/terminfo"
CXXFLAGS="-O2 -pipe -march=native -g"
DISTDIR="/home/distfiles"
FCFLAGS="-O2 -pipe"
FEATURES="assume-digests binpkg-logs config-protect-if-modified distlocks
ebuild-locks fixlafiles merge-sync news parallel-fetch preserve-libs
protect-owned sandbox sfperms splitdebug strict unknown-features-warn
unmerge-logs unmerge-orphans userfetch userpriv usersandbox usersync xattr"
FFLAGS="-O2 -pipe"
GENTOO_MIRRORS="http://distfiles.gentoo.org;
LANG="en_US.UTF-8"
LDFLAGS="-Wl,-O1 -Wl,--as-needed"
MAKEOPTS="-j6"
PKGDIR="/usr/portage/packages"
PORTAGE_CONFIGROOT="/"
PORTAGE_RSYNC_OPTS="--recursive --links --safe-links --perms --times
--omit-dir-times --compress --force --whole-file --delete --stats
--human-readable --timeout=180 --exclude=/distfiles --exclude=/local
--exclude=/packages --exclude=/.git"
PORTAGE_TMPDIR="/home/tmp"
USE="X a52 aac acl acpi alsa amd64 ao audiofile bash-completion bcmath berkdb
bluetooth branding btrfs bzip2 cairo cdda cdr cgi cli client consolekit
cracklib crypt css cups curl cvs cxx dbus declarative designer device-lib djvu
dmraid dri dts dvd dvdr emboss encode exfat exif extensions extraengine f2fs
fam fat ffmpeg fftw firefox flac fpm ftdi ftp garden gcrypt gd gdbm gif git
github glamor glut gnuplot gnutls gpm graph gsm gstreamer gtk gzip hfs iconv
icu imagemagick imap ipv6 jabber javascript jpeg jpeg2k kde kipi kwallet lame
lcms ldap libnotify libsamplerate libssh lightdm lm_sensors lzma lzo mad
matroska mcs51 mdadm mhash mime mmx mng modules mozilla mp3 mp4 mpeg mplayer
multilib mysql mysqli ncurses nls non-free nptl ntfs ntp offensive ogg okteta
opengl openmp otr packihx pam pango passwordsave pcntl pcre pdf pdo phonon php
pic14 pic16 pkcs11 plasma png policykit portaudio postgres postscript
powermanagement ppds printupport pulseaudio python qml qt3support qt4 qt5
quicktime rdesktop readline reiser4 reiserfs sdbinutils sdcdb sdcpp sdl seccomp
semantic-desktop server session sftp sockets sound sox speex spell sqlite
sqlite3 sse sse2 sse3 sse4_1 ssh sshdump ssl ssse3 startup-notification
subversion svg syslog sysvipc tcpd theora threads tidy tiff tls truetype ucsim
udev udisks unicode upower usb v4l vnc vorbis webkit widgets wifi wmf wxwidgets
x264 xattr xcb xcomposite xfs xinerama xinted xkb xml xmlrpc xmpp xpm
xscreensaver xv xvid zip zlib" ABI_X86="32 64" ALSA_CARDS="ali5451 als4000
atiixp atiixp-modem bt87x ca0106 cmipci emu10k1x ens1370 ens1371 es1938 es1968
fm801 hda-intel intel8x0 intel8x0m maestro3 trident usb-audio via82xx
via82xx-modem ymfpci" APACHE2_MODULES="authn_core authz_core socache_shmcb
unixd actions alias auth_basic authn_alias authn_anon authn_dbm authn_default
authn_file authz_dbm authz_default authz_groupfile authz_host authz_owner
authz_user autoindex cache cgi cgid dav dav_fs dav_lock deflate dir disk_cache
env expires ext_filter file_cache filter headers include info log_config logio
mem_cache mime mime_magic negotiation rewrite setenvif speling status unique_id
userdir usertrack vhost_alias" CALLIGRA_FEATURES="kexi words flow plan sheets
stage tables krita karbon braindump author" COLLECTD_PLUGINS="df interface irq
load memory rrdtool swap syslog" CPU_FLAGS_X86="aes avx avx2 fma3 mmx mmxext
popcnt sse sse2 sse3 sse4_1 sse4_2 ssse3" ELIBC="glibc"
GPSD_PROTOCOLS="nmea0183" INPUT_DEVICES="evdev synaptics" KERNEL="linux"
LCD_DEVICES="bayrad cfontz cfontz633 glk hd44780 lb216 lcdm001 mtxorb ncurses
text" LIBREOFFICE_EXTENSIONS="presenter-console presenter-minimizer"
OFFICE_IMPLEMENTATION="libreoffice" PHP_TARGETS="php5-6"
POSTGRES_TARGETS="postgres9_5" PYTHON_SINGLE_TARGET="python3_4"
PYTHON_TARGETS="python2_7 python3_4" QEMU_USER_TARGETS="i386 x86_64"
RUBY_TARGETS="ruby21 ruby22" USERLAND="GNU" VIDEO_CARDS="intel i965"
XTABLES_ADDONS="quota2 psd pknock lscan length2 ipv4options ipset ipp2p iface
geoip fuzzy condition tee tarpit sysrq steal rawnat logmark ipmark dhcpmac
delude chaos account"
Unset:  CC, CPPFLAGS, CTARGET, CXX, EMERGE_DEFAULT_OPTS, INSTALL_MASK, LC_ALL,
PORTAGE_BUNZIP2_COMMAND, PORTAGE_COMPRESS, PORTAGE_COMPRESS_FLAGS,
PORTAGE_RSYNC_EXTRA_OPTS, USE_PYTHON

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

[kdevelop] [Bug 382901] Kdevelop 5.1.1 crashes when typing anything in .c/.h file

2017-07-29 Thread Artur Langner

https://bugs.kde.org/show_bug.cgi?id=382901

--- Comment #2 from Artur Langner <k...@xene.eu> ---
I reinstalled qtscript-5.7.1 with the JIT flag disabled. Kdevelop now works
fine. Thanks.

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

[kdevelop] [Bug 382901] Kdevelop 5.1.1 crashes when typing anything in .c/.h file

2017-07-29 Thread Artur Langner

https://bugs.kde.org/show_bug.cgi?id=382901

Artur Langner <k...@xene.eu> changed:

   What|Removed |Added

   Platform|Compiled Sources|Gentoo Packages

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

[kdevelop] [Bug 382901] New: Kdevelop 5.1.1 crashes when typing anything in .c/.h file

2017-07-29 Thread Artur Langner

https://bugs.kde.org/show_bug.cgi?id=382901

Bug ID: 382901
   Summary: Kdevelop 5.1.1 crashes when typing anything in .c/.h
file
   Product: kdevelop
   Version: 5.1.1
  Platform: Compiled Sources
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdevelop-bugs-n...@kde.org
  Reporter: k...@xene.eu
  Target Milestone: ---

Application: kdevelop (5.1.1)
 (Compiled from sources)
Qt Version: 5.7.1
Frameworks Version: 5.34.0
Operating System: Linux 3.18.0-rc4 x86_64
Distribution (Platform): Gentoo Packages

-- Information about the crash:
I have installed Kdevelop 5.1.1 on Gentoo. When I type anything in a .c/.h file
(single letter) Kdevelop crashes. Every single time. The crash happens in a
.c/.h files, editing/saving makefiles works flawlessly. It also happens when
the following plugins are *disabled*: cppcheck, class browser, code browser.
Editing the very same files work fine in Kate and Kwrite. 

There is something about allocator in the backtrace (I don't know how to read
that exactly). I have 8GB of RAM, usually less than 2GB are used. I have no
ulimits, no grsecurity, no SElinux. I have no other problems - KDE is stable,
all other apps are also stable.

$ ulimit -a
core file size  (blocks, -c) 0
data seg size   (kbytes, -d) unlimited
scheduling priority (-e) 0
file size   (blocks, -f) unlimited
pending signals (-i) 31635
max locked memory   (kbytes, -l) 64
max memory size (kbytes, -m) unlimited
open files  (-n) 1024
pipe size(512 bytes, -p) 8
POSIX message queues (bytes, -q) 819200
real-time priority  (-r) 0
stack size  (kbytes, -s) 8192
cpu time   (seconds, -t) unlimited
max user processes  (-u) 31635
virtual memory  (kbytes, -v) 400
file locks  (-x) unlimited

My system:
Portage 2.3.6 (python 2.7.12-final-0, default/linux/amd64/13.0/desktop/plasma,
gcc-5.4.0, glibc-2.25-r2, 3.18.0-rc4 x86_64)
=
System uname:
Linux-3.18.0-rc4-x86_64-Intel-R-_Core-TM-_i5-4210U_CPU_@_1.70GHz-with-gentoo-2.3
KiB Mem: 8101340 total,   1999404 free
KiB Swap:  0 total, 0 free
Timestamp of repository gentoo: Sat, 15 Jul 2017 12:30:01 +
sh bash 4.3_p48-r1
ld GNU ld (Gentoo 2.25.1 p1.1) 2.25.1
app-shells/bash:  4.3_p48-r1::gentoo
dev-java/java-config: 2.2.0-r3::gentoo
dev-lang/perl:5.24.1-r2::gentoo
dev-lang/python:  2.7.12::gentoo, 3.4.5::gentoo
dev-util/cmake:   3.7.2::gentoo
dev-util/pkgconfig:   0.28-r2::gentoo
sys-apps/baselayout:  2.3::gentoo
sys-apps/openrc:  0.26.3::gentoo
sys-apps/sandbox: 2.10-r3::gentoo
sys-devel/autoconf:   2.13::gentoo, 2.69::gentoo
sys-devel/automake:   1.11.6-r1::gentoo, 1.14.1::gentoo, 1.15-r2::gentoo
sys-devel/binutils:   2.25.1-r1::gentoo, 2.26.1::gentoo, 2.28-r2::gentoo
sys-devel/gcc:5.4.0-r3::gentoo
sys-devel/gcc-config: 1.7.3::gentoo
sys-devel/libtool:2.4.6-r3::gentoo
sys-devel/make:   4.2.1::gentoo
sys-kernel/linux-headers: 4.4::gentoo (virtual/os-headers)
sys-libs/glibc:   2.25-r2::gentoo

The crash can be reproduced every time.

-- Backtrace:
Application: KDevelop (kdevelop), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f58570067c0 (LWP 5107))]

Thread 12 (Thread 0x7f58167fc700 (LWP 5216)):
#0  0x7f586c2e1722 in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7f5864f954f4 in QTWTF::TCMalloc_PageHeap::scavengerThread
(this=0x7f586507c2e0 ) at
../3rdparty/javascriptcore/JavaScriptCore/wtf/FastMalloc.cpp:2359
#2  0x7f5864f95539 in QTWTF::TCMalloc_PageHeap::runScavengerThread
(context=) at
../3rdparty/javascriptcore/JavaScriptCore/wtf/FastMalloc.cpp:1464
#3  0x7f586c2da937 in start_thread () from /lib64/libpthread.so.0
#4  0x7f587238bc5f in clone () from /lib64/libc.so.6

Thread 11 (Thread 0x7f5816ffd700 (LWP 5190)):
#0  0x7f586c2e1722 in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7f5872ae395a in QWaitConditionPrivate::wait
(time=18446744073709551615, this=0x23cd500) at
thread/qwaitcondition_unix.cpp:143
#2  QWaitCondition::wait (this=, mutex=0x2394bc0,
time=18446744073709551615) at thread/qwaitcondition_unix.cpp:215
#3  0x7f5867d8f48f in
ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*,
bool, bool, bool) () from /usr/lib64/libKF5ThreadWeaver.so.5
#4  0x7f5867d934a8 in ?? () from /usr/lib64/libKF5ThreadWeaver.so.5
#5  0x7f5867d8e64d in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from

[kwin] [Bug 382385] New: Kwin crash

2017-07-15 Thread Artur O .

https://bugs.kde.org/show_bug.cgi?id=382385

Bug ID: 382385
   Summary: Kwin crash
   Product: kwin
   Version: 5.10.3
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kwin-bugs-n...@kde.org
  Reporter: commander.alch...@gmail.com
  Target Milestone: ---

Application: kwin_x11 (5.10.3)

Qt Version: 5.9.1
Frameworks Version: 5.36.0
Operating System: Linux 4.11.9-1-ARCH x86_64
Distribution: "Arch Linux"

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

I opened the steam store and kwin crashed, probably not related though.

-- Backtrace:
Application: KWin (kwin_x11), signal: Aborted
Using host libthread_db library "/usr/lib/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f2787f3c840 (LWP 20874))]

Thread 6 (Thread 0x7f27577ff700 (LWP 16140)):
#0  0x7f2780ab81ad in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7f2784d385ec in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/libQt5Core.so.5
#2  0x7f2784d30d0c in QSemaphore::acquire(int) () at
/usr/lib/libQt5Core.so.5
#3  0x7f274f3ed82c in  () at
/usr/lib/qt/plugins/texttospeech/libqttexttospeech_flite.so
#4  0x7f2784d3715b in  () at /usr/lib/libQt5Core.so.5
#5  0x7f2780ab2049 in start_thread () at /usr/lib/libpthread.so.0
#6  0x7f2787990f0f in clone () at /usr/lib/libc.so.6

Thread 5 (Thread 0x7f2765f5a700 (LWP 20791)):
#0  0x7f2787986f76 in ppoll () at /usr/lib/libc.so.6
#1  0x7f2784f70ba3 in qt_safe_poll(pollfd*, unsigned long, timespec const*)
() at /usr/lib/libQt5Core.so.5
#2  0x7f2784f7233f in
QEventDispatcherUNIX::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#3  0x7f2784f18ffb in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#4  0x7f2784d3240e in QThread::exec() () at /usr/lib/libQt5Core.so.5
#5  0x7f2784d3715b in  () at /usr/lib/libQt5Core.so.5
#6  0x7f2780ab2049 in start_thread () at /usr/lib/libpthread.so.0
#7  0x7f2787990f0f in clone () at /usr/lib/libc.so.6

Thread 4 (Thread 0x7f274e4f6700 (LWP 20899)):
#0  0x7f2780ab81ad in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7f2783e83b04 in  () at /usr/lib/libQt5Script.so.5
#2  0x7f2783e83b49 in  () at /usr/lib/libQt5Script.so.5
#3  0x7f2780ab2049 in start_thread () at /usr/lib/libpthread.so.0
#4  0x7f2787990f0f in clone () at /usr/lib/libc.so.6

Thread 3 (Thread 0x7f2767df2700 (LWP 20893)):
#0  0x7f2787986f76 in ppoll () at /usr/lib/libc.so.6
#1  0x7f2784f70ba3 in qt_safe_poll(pollfd*, unsigned long, timespec const*)
() at /usr/lib/libQt5Core.so.5
#2  0x7f2784f7233f in
QEventDispatcherUNIX::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#3  0x7f2784f18ffb in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#4  0x7f2784d3240e in QThread::exec() () at /usr/lib/libQt5Core.so.5
#5  0x7f277e94f396 in  () at /usr/lib/libQt5DBus.so.5
#6  0x7f2784d3715b in  () at /usr/lib/libQt5Core.so.5
#7  0x7f2780ab2049 in start_thread () at /usr/lib/libpthread.so.0
#8  0x7f2787990f0f in clone () at /usr/lib/libc.so.6

Thread 2 (Thread 0x7f276e04a700 (LWP 20892)):
#0  0x7f2787986e9d in poll () at /usr/lib/libc.so.6
#1  0x7f2786a5f8e0 in  () at /usr/lib/libxcb.so.1
#2  0x7f2786a61679 in xcb_wait_for_event () at /usr/lib/libxcb.so.1
#3  0x7f276f14872a in  () at /usr/lib/libQt5XcbQpa.so.5
#4  0x7f2784d3715b in  () at /usr/lib/libQt5Core.so.5
#5  0x7f2780ab2049 in start_thread () at /usr/lib/libpthread.so.0
#6  0x7f2787990f0f in clone () at /usr/lib/libc.so.6

Thread 1 (Thread 0x7f2787f3c840 (LWP 20874)):
[KCrash Handler]
#5  0x7f27878d68c0 in raise () at /usr/lib/libc.so.6
#6  0x7f27878d7f72 in abort () at /usr/lib/libc.so.6
#7  0x7f2784d219a8 in  () at /usr/lib/libQt5Core.so.5
#8  0x7f2784d312fe in QThread::~QThread() () at /usr/lib/libQt5Core.so.5
#9  0x7f2784d3135a in QThread::~QThread() () at /usr/lib/libQt5Core.so.5
#10 0x7f2784f482cd in QObjectPrivate::deleteChildren() () at
/usr/lib/libQt5Core.so.5
#11 0x7f2784f51f0c in QObject::~QObject() () at /usr/lib/libQt5Core.so.5
#12 0x7f27673cc309 in KWin::X11StandalonePlatform::~X11StandalonePlatform()
() at /usr/lib/qt/plugins/org.kde.kwin.platforms/KWinX11Platform.so
#13 0x7f2784f482cd in QObjectPrivate::deleteChildren() () at
/usr/lib/libQt5Core.so.5
#14 0x7f2784f51f0c in QObject::~QObject() () at /usr/lib/libQt5Core.so.5
#15 0x7f2784f1cddc in QCoreApplication::~QCoreApplication() () at
/usr/lib/libQt5Core.so.5
#16 0x7f2785c478c9 in QApplication::~QApplication() () at
/usr/lib/libQt5Widgets.so.5
#17 0x7f2787c52743 in  () at /usr/lib/libkdeinit5_kwin_x11.so
#18 0x7f2787c54029 in kdemain () at /usr/lib/libkdeinit5_kwin_x11.so
#19

[kwin] [Bug 381938] Kwin compositor crashes, (twice when opening steam store)

2017-07-02 Thread Artur O .

https://bugs.kde.org/show_bug.cgi?id=381938

--- Comment #1 from Artur O. <commander.alch...@gmail.com> ---
Driver version: Nvidia 384.47 @ Nvidia MSI GTX 970

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

[kwin] [Bug 381938] Kwin compositor crashes, (twice when opening steam store)

2017-07-02 Thread Artur O .

https://bugs.kde.org/show_bug.cgi?id=381938

Artur O. <commander.alch...@gmail.com> changed:

   What|Removed |Added

Summary|Kwin compositor crashes.|Kwin compositor crashes,
   ||(twice when opening steam
   ||store)

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

[kwin] [Bug 381938] New: Kwin compositor crashes.

2017-07-02 Thread Artur O .

https://bugs.kde.org/show_bug.cgi?id=381938

Bug ID: 381938
   Summary: Kwin compositor crashes.
   Product: kwin
   Version: 5.10.3
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kwin-bugs-n...@kde.org
  Reporter: commander.alch...@gmail.com
  Target Milestone: ---

Application: kwin_x11 (5.10.3)

Qt Version: 5.9.0
Frameworks Version: 5.35.0
Operating System: Linux 4.11.8-1-ck-piledriver x86_64
Distribution: "Arch Linux"

-- Information about the crash:
- What I was doing when the application crashed:
Kwin compositor keeps crashing, mostly (2 times now) but cannot reproduce it
all the time, was when opening steam Store window. Desktop freezes for couple
of seconds and then shows the "crash reporting assistant" and you see that
desktop effects are disabled. 

I need to go to compositor settings and re-enable and then restart kwin to
bring it back.

-- Backtrace:
Application: KWin (kwin_x11), signal: Aborted
Using host libthread_db library "/usr/lib/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f68f7d76840 (LWP 730))]

Thread 7 (Thread 0x7f68d5cba700 (LWP 1609)):
[KCrash Handler]
#5  0x7f68f7716670 in raise () at /usr/lib/libc.so.6
#6  0x7f68f7717d00 in abort () at /usr/lib/libc.so.6
#7  0x7f68f4b79807 in  () at /usr/lib/libQt5Core.so.5
#8  0x7f68d712da23 in  () at
/usr/lib/qt/plugins/org.kde.kwin.platforms/KWinX11Platform.so
#9  0x7f68f4d9757f in QMetaObject::activate(QObject*, int, int, void**) ()
at /usr/lib/libQt5Core.so.5
#10 0x7f68f4e14767 in QTimer::timeout(QTimer::QPrivateSignal) () at
/usr/lib/libQt5Core.so.5
#11 0x7f68f4da4008 in QTimer::timerEvent(QTimerEvent*) () at
/usr/lib/libQt5Core.so.5
#12 0x7f68f4d97e2b in QObject::event(QEvent*) () at
/usr/lib/libQt5Core.so.5
#13 0x7f68f5a9746c in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() at /usr/lib/libQt5Widgets.so.5
#14 0x7f68f5a9ecf4 in QApplication::notify(QObject*, QEvent*) () at
/usr/lib/libQt5Widgets.so.5
#15 0x7f68f4d68b98 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() at /usr/lib/libQt5Core.so.5
#16 0x7f68f4dbfbae in QTimerInfoList::activateTimers() () at
/usr/lib/libQt5Core.so.5
#17 0x7f68f4dbddc2 in
QEventDispatcherUNIX::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#18 0x7f68f4d6721a in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#19 0x7f68f4b8940a in QThread::exec() () at /usr/lib/libQt5Core.so.5
#20 0x7f68f4b8dcbd in  () at /usr/lib/libQt5Core.so.5
#21 0x7f68f0902297 in start_thread () at /usr/lib/libpthread.so.0
#22 0x7f68f77d01ef in clone () at /usr/lib/libc.so.6

Thread 6 (Thread 0x7f68c4a27700 (LWP 1608)):
#0  0x7f68f090839d in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7f68f4b8f0eb in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/libQt5Core.so.5
#2  0x7f68f4b87f7b in QSemaphore::acquire(int) () at
/usr/lib/libQt5Core.so.5
#3  0x7f68bebc582c in  () at
/usr/lib/qt/plugins/texttospeech/libqttexttospeech_flite.so
#4  0x7f68f4b8dcbd in  () at /usr/lib/libQt5Core.so.5
#5  0x7f68f0902297 in start_thread () at /usr/lib/libpthread.so.0
#6  0x7f68f77d01ef in clone () at /usr/lib/libc.so.6

Thread 5 (Thread 0x7f68b700 (LWP 877)):
#0  0x7f68f090839d in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7f68f3cd3ac4 in  () at /usr/lib/libQt5Script.so.5
#2  0x7f68f3cd3b09 in  () at /usr/lib/libQt5Script.so.5
#3  0x7f68f0902297 in start_thread () at /usr/lib/libpthread.so.0
#4  0x7f68f77d01ef in clone () at /usr/lib/libc.so.6

Thread 4 (Thread 0x7f68d5272700 (LWP 798)):
#0  0x7f68f77c6326 in ppoll () at /usr/lib/libc.so.6
#1  0x7f68f4dbc471 in qt_safe_poll(pollfd*, unsigned long, timespec const*)
() at /usr/lib/libQt5Core.so.5
#2  0x7f68f4dbdb5e in
QEventDispatcherUNIX::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#3  0x7f68f4d6721a in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#4  0x7f68f4b8940a in QThread::exec() () at /usr/lib/libQt5Core.so.5
#5  0x7f68ef612645 in  () at /usr/lib/libQt5Qml.so.5
#6  0x7f68f4b8dcbd in  () at /usr/lib/libQt5Core.so.5
#7  0x7f68f0902297 in start_thread () at /usr/lib/libpthread.so.0
#8  0x7f68f77d01ef in clone () at /usr/lib/libc.so.6

Thread 3 (Thread 0x7f68d7b52700 (LWP 758)):
#0  0x7f68f77c6326 in ppoll () at /usr/lib/libc.so.6
#1  0x7f68f4dbc471 in qt_safe_poll(pollfd*, unsigned long, timespec const*)
() at /usr/lib/libQt5Core.so.5
#2  0x7f68f4dbdb5e in
QEventDispatcherUNIX::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#3  0x7f68f4d6721a in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#4  0x7f68f4b8940a in QThread::exec() () at /usr/lib/libQt5Core.so.5
#5  0x7f68ee7a8d45

[kio] [Bug 357959] Bug while copying font files to local system from Windows networked location

2017-06-20 Thread Artur

https://bugs.kde.org/show_bug.cgi?id=357959

Artur <artu...@issp.ac.ru> changed:

   What|Removed |Added

 CC||artu...@issp.ac.ru

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

[kio] [Bug 357959] Bug while copying font files to local system from Windows networked location

2017-06-20 Thread Artur

https://bugs.kde.org/show_bug.cgi?id=357959

--- Comment #2 from Artur <artu...@issp.ac.ru> ---
Created attachment 106180
  --> https://bugs.kde.org/attachment.cgi?id=106180=edit
New crash information added by DrKonqi

dolphin (4.14.3) on KDE Platform 4.14.10 using Qt 4.8.7

- What I was doing when the application crashed: I was copying a large number
of images (~3000, ~1.4 MB each) from KDE to FAT32 flashcards, at ~ 1000th it
has been stopped and the bug window was appeared. The error is repeated for
different (and for certain, of course) flashcards

- Custom settings of the application:

-- Backtrace (Reduced):
#8  0x000805c33324 in QNetworkProxyFactory::systemProxyForQuery () from
/usr/local/lib/qt4/libQtNetwork.so.4
#9  0x000805c4aae7 in QLocalServer::qt_metacall () from
/usr/local/lib/qt4/libQtNetwork.so.4
#10 0x000805c4326c in QAbstractSocket::waitForBytesWritten () from
/usr/local/lib/qt4/libQtNetwork.so.4
#11 0x00080c4d17ee in KIO::Connection::close () from
/usr/local/lib/libkio.so.5
#12 0x00080c4d00c8 in KIO::Connection::sendnow () from
/usr/local/lib/libkio.so.5

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

[Breeze] [Bug 378820] Icons without white border in breeze-cursor theme

2017-04-15 Thread Artur

https://bugs.kde.org/show_bug.cgi?id=378820

--- Comment #1 from Artur <arturjo...@gmail.com> ---
Forgot to mention that this also happens in breeze-snow-cursor the other way
around; no black border in "cross" and "crosshair" as in the rest of the
images.

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

[Breeze] [Bug 378820] New: Icons without white border in breeze-cursor theme

2017-04-15 Thread Artur

https://bugs.kde.org/show_bug.cgi?id=378820

Bug ID: 378820
   Summary: Icons without white border in breeze-cursor theme
   Product: Breeze
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: major
  Priority: NOR
 Component: Icons
  Assignee: visual-des...@kde.org
  Reporter: arturjo...@gmail.com
CC: kain...@gmail.com
  Target Milestone: ---

All the icons in this theme have a white border to make visibility easy but
"cross" and "crosshair".

"cross" and "crosshair" don't have a white border and when they become active
in some applications with dark background I can't barely see them. If I move
the mouse quick my eyes looses them.

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

[kwin] [Bug 378585] Old icons appear when toggling compositing on/off

2017-04-14 Thread Artur O .

https://bugs.kde.org/show_bug.cgi?id=378585

Artur O. <commander.alch...@gmail.com> changed:

   What|Removed |Added

Product|plasmashell |kwin
  Component|general |compositing
   Target Milestone|1.0 |---

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

[plasmashell] [Bug 378585] Old icons appear when toggling compositing on/off

2017-04-09 Thread Artur O .

https://bugs.kde.org/show_bug.cgi?id=378585

--- Comment #1 from Artur O. <commander.alch...@gmail.com> ---
Doing; 
kquitapp5 plasmashell
plasmashell &>/dev/null &

will fix this temporary only to be triggered later on.

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

[plasmashell] [Bug 378585] New: Old icons appear when toggling compositing on/off

2017-04-09 Thread Artur O .

https://bugs.kde.org/show_bug.cgi?id=378585

Bug ID: 378585
   Summary: Old icons appear when toggling compositing on/off
   Product: plasmashell
   Version: 5.9.4
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: commander.alch...@gmail.com
CC: bhus...@gmail.com, plasma-b...@kde.org
  Target Milestone: 1.0

When toggling kwin compositing on/off using the hotkeys it seems that the
plasmashell stops rendering and everything is stuck at "that" time; Icons, tray
icons, icon-only taskmanager even the digital clock on the panel and widgets on
desktop are affected.

Here are two screenshots from the exact same time, however on one it seems that
it was taken several hours ago; 

Compositing on: http://i.imgur.com/xqUTxo1.png
Compositing off: http://i.imgur.com/nRqPRtE.png

I've experianced this for quite some time now, think i mentioned it in
https://bugs.kde.org/show_bug.cgi?id=361154

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

[systemsettings] [Bug 376603] New: Crash after changing composing engine to OpenGL 3.1

2017-02-17 Thread Artur

https://bugs.kde.org/show_bug.cgi?id=376603

Bug ID: 376603
   Summary: Crash after changing composing engine to OpenGL 3.1
   Product: systemsettings
   Version: 5.8.5
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: arturpol...@gmail.com
  Target Milestone: ---

Application: systemsettings5 (5.8.5)

Qt Version: 5.7.1
Frameworks Version: 5.28.0
Operating System: Linux 4.9.0-15-generic x86_64
Distribution: Ubuntu Zesty Zapus (development branch)

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

Ubuntu 17.04 with kubuntu-desktop package installed ...
Change composing engine to OpenGL 3.1 and disabling screen lock

-- Backtrace:
Application: Ustawienia systemowe (systemsettings5), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f6de9df58c0 (LWP 5085))]

Thread 4 (Thread 0x7f6db407e700 (LWP 5101)):
#0  0x7ffda2390ad7 in clock_gettime ()
#1  0x7f6de5ba7886 in __GI___clock_gettime (clock_id=1, tp=0x7f6db407da40)
at ../sysdeps/unix/clock_gettime.c:115
#2  0x7f6de6331f71 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#3  0x7f6de64aeba9 in QTimerInfoList::updateCurrentTime() () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7f6de64af155 in QTimerInfoList::timerWait(timespec&) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7f6de64b04fe in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7f6ddfd4df9d in g_main_context_prepare () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#7  0x7f6ddfd4e9cb in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#8  0x7f6ddfd4ebbc in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#9  0x7f6de64b0f2b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#10 0x7f6de645a88a in
QEventLoop::exec(QFlags) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#11 0x7f6de6287fe3 in QThread::exec() () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#12 0x7f6de45d4df5 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5
#13 0x7f6de628cc98 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#14 0x7f6de1e7d6ca in start_thread (arg=0x7f6db407e700) at
pthread_create.c:333
#15 0x7f6de5b990ff in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:105

Thread 3 (Thread 0x7f6dcd7eb700 (LWP 5088)):
#0  0x7f6de5b8d10d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7f6ddfd4eaa6 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f6ddfd4ebbc in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f6de64b0f2b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7f6de645a88a in
QEventLoop::exec(QFlags) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7f6de6287fe3 in QThread::exec() () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7f6de6db45c5 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5
#7  0x7f6de628cc98 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x7f6de1e7d6ca in start_thread (arg=0x7f6dcd7eb700) at
pthread_create.c:333
#9  0x7f6de5b990ff in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:105

Thread 2 (Thread 0x7f6dd615d700 (LWP 5087)):
#0  0x7f6de5b8d10d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7f6de26f4c62 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1
#2  0x7f6de26f68d7 in xcb_wait_for_event () from
/usr/lib/x86_64-linux-gnu/libxcb.so.1
#3  0x7f6dd86b4c49 in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5
#4  0x7f6de628cc98 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7f6de1e7d6ca in start_thread (arg=0x7f6dd615d700) at
pthread_create.c:333
#6  0x7f6de5b990ff in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:105

Thread 1 (Thread 0x7f6de9df58c0 (LWP 5085)):
[KCrash Handler]
#6  0x7f6de44a7495 in QV4::WeakValue::free() () from
/usr/lib/x86_64-linux-gnu/libQt5Qml.so.5
#7  0x7f6de4518152 in QV4::QObjectWrapper::destroyObject(bool) () from
/usr/lib/x86_64-linux-gnu/libQt5Qml.so.5
#8  0x7f6de43aa69f in QV4::MemoryManager::sweep(bool) () from
/usr/lib/x86_64-linux-gnu/libQt5Qml.so.5
#9  0x7f6de43abaac in QV4::MemoryManager::~MemoryManager() () from
/usr/lib/x86_64-linux-gnu/libQt5Qml.so.5
#10 0x7f6de4496e2b in QV4::ExecutionEngine::~ExecutionEngine() () from
/usr/lib/x86_64-linux-gnu/libQt5Qml.so.5
#11 0x7f6de45d68a6 in QV8Engine::~QV8Engine() () from
/usr/lib/x86_64-linux-gnu/libQt5Qml.so.5
#12 0x7f6de45d69c9 in QV8Engine::~QV8Engine() () from
/usr/lib/x86_64-linux-gnu/libQt5Qml.so.5
#13

[kwin] [Bug 361236] Aurorae crashes in QQmlBinding::write on creation - Qt 5.6

2016-08-24 Thread Artur R . Czechowski via KDE Bugzilla

https://bugs.kde.org/show_bug.cgi?id=361236

Artur R. Czechowski <artu...@hell.pl> changed:

   What|Removed |Added

 CC||artu...@hell.pl

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

[kwin] [Bug 365799] Graphical corruption and display stops updating when connecting external monitor through HDMI

2016-08-16 Thread Artur O . via KDE Bugzilla

https://bugs.kde.org/show_bug.cgi?id=365799

--- Comment #16 from Artur O. <commander.alch...@gmail.com> ---
(In reply to Thomas Lübking from comment #15)
> I wanted to see KWin's opinion on the screen config ;-)
> 
> ==> Did you try OpenGL 2.0?
> 
> Ftr, GLX_EXT_buffer_age is *not* supported (the listing in client extensions
> is insufficient, one would expect it in server and general extensions as
> well)

Well after playing around and searching i found some help in #archlinux
channel. Uninstalling xf86-video-intel drivers solved my issues. No more
corruption and no more freezing when connecting/disconnecting monitor.

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

[kwin] [Bug 365799] Graphical corruption and display stops updating when connecting external monitor through HDMI

2016-07-19 Thread Artur O . via KDE Bugzilla

https://bugs.kde.org/show_bug.cgi?id=365799

--- Comment #14 from Artur O. <commander.alch...@gmail.com> ---
Created attachment 100183
  --> https://bugs.kde.org/attachment.cgi?id=100183=edit
kwin system log

The systemlog as requested (after the freezing occurs), but not sure if needed
now that this seems to be a compositing issue?

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

[kwin] [Bug 365799] Graphical corruption and display stops updating when connecting external monitor through HDMI

2016-07-19 Thread Artur O . via KDE Bugzilla

https://bugs.kde.org/show_bug.cgi?id=365799

--- Comment #13 from Artur O. <commander.alch...@gmail.com> ---
Created attachment 100182
  --> https://bugs.kde.org/attachment.cgi?id=100182=edit
glxinfo for ref

It supports bugger age it seems, but wanted to just include whole glxinfo just
for ref.

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

[kwin] [Bug 365799] Graphical corruption and display stops updating when connecting external monitor through HDMI

2016-07-19 Thread Artur O . via KDE Bugzilla

https://bugs.kde.org/show_bug.cgi?id=365799

--- Comment #12 from Artur O. <commander.alch...@gmail.com> ---
(In reply to Thomas Lübking from comment #10)
> The corruption looks very much like a driver bug, you see the buffer tiles
> which partially contain junk.
> Could be a buffer_age issue - check glxinfo for general support and in case
> KWIN_USE_BUFFER_AGE=0 kwin_x11 --replace &
> 
> https://community.kde.org/KWin/Environment_Variables#KWIN_USE_BUFFER_AGE
> 
> On
> > laptop screen stops updating while the second monitor works fine
> 
> Can you please dump the supportInformation again, but this time after
> attaching the screen and when one screen is dead (given that kwin actually
> responds in this state)
> Also, does restarting the compositor (SHIFT+Alt+F12, twice) resolve the
> state as well?
> 
> ---
> nb: this is on Qt 5.7.0 ...

Well I  played with this at work today. 

* You can drag/move windows when its "frozen", mouse updates as usual when
draging occurs just it won't update the screen/window position other than the
mouse.

* When toggling compositing with with the combination the moment you turn
compositing off the screen updates quickly as nothing has happend. The freeze
will also only occur when compositing is enabled. Turning compositing off with
the combination and then plugging in the external monitor just works.

* I tried the 'KWIN_USE_BUFFER_AGE=0 kwin_x11 --replace &' but the corruption
still occurs.

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

[kwin] [Bug 365799] Graphical corruption and display stops updating when connecting external monitor through HDMI

https://bugs.kde.org/show_bug.cgi?id=365799

--- Comment #9 from Artur O. <commander.alch...@gmail.com> ---
Here is a link to the video corruption I'm talking about
https://www.youtube.com/watch?v=x8fBxuncT9k

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

[kwin] [Bug 365799] Graphical corruption and display stops updating when connecting external monitor through HDMI

https://bugs.kde.org/show_bug.cgi?id=365799

--- Comment #8 from Artur O. <commander.alch...@gmail.com> ---
(In reply to Artur O. from comment #7)
> Created attachment 100157 [details]
> kwin when screen corruption occur after unplugging external screen

most of these errors show up even after --replace and no visual errors occur.
Only new in this one is;
QXcbConnection: XCB error: 3 (BadWindow), sequence: 10168, resource id:
35651862, major code: 15 (QueryTree), minor code: 0

But not sure if this is even related or just coincidence.

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

[kwin] [Bug 365799] Graphical corruption and display stops updating when connecting external monitor through HDMI

https://bugs.kde.org/show_bug.cgi?id=365799

--- Comment #7 from Artur O. <commander.alch...@gmail.com> ---
Created attachment 100157
  --> https://bugs.kde.org/attachment.cgi?id=100157=edit
kwin when screen corruption occur after unplugging external screen

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

[kwin] [Bug 365799] Graphical corruption and display stops updating when connecting external monitor through HDMI

https://bugs.kde.org/show_bug.cgi?id=365799

--- Comment #6 from Artur O. <commander.alch...@gmail.com> ---
Created attachment 100156
  --> https://bugs.kde.org/attachment.cgi?id=100156=edit
xrandr with external screen

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

[kwin] [Bug 365799] Graphical corruption and display stops updating when connecting external monitor through HDMI