[kwin] [Bug 486030] New: Plasma6 regression. Inconvenient hot keys on menu "Move to desktop"

2024-04-23 Thread vyacheslav
https://bugs.kde.org/show_bug.cgi?id=486030

Bug ID: 486030
   Summary: Plasma6 regression. Inconvenient hot keys on menu
"Move to desktop"
Classification: Plasma
   Product: kwin
   Version: unspecified
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: appmenu
  Assignee: kwin-bugs-n...@kde.org
  Reporter: galdra...@bk.ru
  Target Milestone: ---

Created attachment 168844
  --> https://bugs.kde.org/attachment.cgi?id=168844=edit
"Move to desktop" menu on plasma5 and plasma6

SUMMARY
Right clicking on task item and on window title has submenu "Move to desktop".

Plasma5:
- both menus "Move to desktop" is identical
- this menu has hot keys 1,2,3,4 ...

Plasma6:
- menu on task item has hot keys, but they inconvenient, not 1,2,3,4 ...
- menu on window title does not have hot keys

See screenshot for further explanation.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Arch Linux
KDE Plasma Version: 6.0.4
KDE Frameworks Version: 6.1.0
Qt Version: 6.7.0

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

[kwin] [Bug 484980] Plasma6. "Plastik" window decoration: right click on window title shows menu at incorrect position

2024-04-03 Thread vyacheslav
https://bugs.kde.org/show_bug.cgi?id=484980

vyacheslav  changed:

   What|Removed |Added

Summary|Plasma6. "Plastik" window   |Plasma6. "Plastik" window
   |decoration: right click on  |decoration: right click on
   |window title shows menu on  |window title shows menu at
   |incorrect position  |incorrect position

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

[kwin] [Bug 484980] New: Plasma6. "Plastik" window decoration: right click on window title shows menu on incorrect position

2024-04-03 Thread vyacheslav
https://bugs.kde.org/show_bug.cgi?id=484980

Bug ID: 484980
   Summary: Plasma6. "Plastik" window decoration: right click on
window title shows menu on incorrect position
Classification: Plasma
   Product: kwin
   Version: 6.0.3
  Platform: Arch Linux
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: decorations
  Assignee: kwin-bugs-n...@kde.org
  Reporter: galdra...@bk.ru
  Target Milestone: ---

SUMMARY
Right clicking on window title should show menu at cursor position.

STEPS TO REPRODUCE
1. Select "plastik" window decoration
2. Right click on window title

OBSERVED RESULT
Appeared menu not at cursor position

EXPECTED RESULT
Appeared menu should be at cursor position

SOFTWARE/OS VERSIONS
KDE Plasma Version: 6.0.3
KDE Frameworks Version: 6.0.0
Qt Version: 6.6.3

ADDITIONAL INFORMATION
Plasma6+"Breeze" window decoration - menu position ok.
Plasma6+"Oxygen" window decoration - menu position ok.
Plasma6+"Plastik" window decoration - menu position incorrect.
Plasma5+"Plastik" window decoration - menu position ok.

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

[plasmashell] [Bug 423676] Task buttons must never change order when sorting and grouping disabled

2024-03-21 Thread vyacheslav
https://bugs.kde.org/show_bug.cgi?id=423676

--- Comment #8 from vyacheslav  ---
When sort mode is "Manually" highlighted items does not change position on
taskbar while switching desktops. "Do not sort" should be as well as
"Manually".

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

[plasmashell] [Bug 423676] Task buttons must never change order when sorting and grouping disabled

2024-03-21 Thread vyacheslav
https://bugs.kde.org/show_bug.cgi?id=423676

--- Comment #7 from vyacheslav  ---
Attachment created on plasma 6.0.2

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

[plasmashell] [Bug 423676] Task buttons must never change order when sorting and grouping disabled

2024-03-21 Thread vyacheslav
https://bugs.kde.org/show_bug.cgi?id=423676

vyacheslav  changed:

   What|Removed |Added

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

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

[plasmashell] [Bug 423676] Task buttons must never change order when sorting and grouping disabled

2024-03-21 Thread vyacheslav
https://bugs.kde.org/show_bug.cgi?id=423676

--- Comment #6 from vyacheslav  ---
Created attachment 167578
  --> https://bugs.kde.org/attachment.cgi?id=167578=edit
Demonstration how items change order on taskbar

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

[plasmashell] [Bug 423676] Task buttons must never change order when sorting and grouping disabled

2024-03-09 Thread vyacheslav
https://bugs.kde.org/show_bug.cgi?id=423676

--- Comment #5 from vyacheslav  ---
(In reply to Nate Graham from comment #3)
> Sorry it's taken us so long to get to this. I Cannot reproduce the issue in
> Plasma 6 (which is scheduled to be released in 5 days). If you can, would
> you be able to attach a screen recording that shows the issue happening so I
> can make sure I'm testing in the right way? Thanks a lot!

It is reproducible on plasma 5.27.10.
I will test it on plasma 6 later.

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

[krita] [Bug 475052] Crop artefacts

2023-10-02 Thread Vyacheslav
https://bugs.kde.org/show_bug.cgi?id=475052

--- Comment #6 from Vyacheslav  ---
(In reply to Dmitry Kazakov from comment #5)
> Hi, Vyacheslav!
> 
> If you disable Canvas Graphics Acceleration, do you still have the bug?
> 
> Could you please also attach the info from Help->System Information?

If Canvas Graphics Acceleration disabled looks like all ok.

Krita

 Version: 5.1.5
 Hidpi: true

Qt

  Version (compiled): 5.12.12
  Version (loaded): 5.12.12

OS Information

  Build ABI: arm64-little_endian-lp64
  Build CPU: arm64
  CPU: arm64
  Kernel Type: darwin
  Kernel Version: 23.0.0
  Pretty Productname: macOS 14.0
  Product Type: osx
  Product Version: 14.0

Locale

  Languages: en_RU
  C locale: C
  QLocale current: en
  QLocale system: en
  QTextCodec for locale: UTF-8

OpenGL Info

  Vendor:  "Apple" 
  Renderer:  "Apple M1 Pro" 
  Version:  "4.1 Metal - 86" 
  Shading language:  "4.10" 
  Requested format:  QSurfaceFormat(version 3.2, options
QFlags(), depthBufferSize 24, redBufferSize 8,
greenBufferSize 8, blueBufferSize 8, alphaBufferSize 8, stencilBufferSize 8,
samples -1, swapBehavior QSurfaceFormat::DoubleBuffer, swapInterval 0,
colorSpace QSurfaceFormat::DefaultColorSpace, profile 
QSurfaceFormat::CoreProfile) 
  Current format:  QSurfaceFormat(version 4.1, options
QFlags(), depthBufferSize 32, redBufferSize 8,
greenBufferSize 8, blueBufferSize 8, alphaBufferSize 8, stencilBufferSize 8,
samples 0, swapBehavior QSurfaceFormat::DoubleBuffer, swapInterval 0,
colorSpace QSurfaceFormat::DefaultColorSpace, profile 
QSurfaceFormat::CoreProfile) 
 Version: 4.1
 Supports deprecated functions false 
 is OpenGL ES: false 
  supportsBufferMapping: true 
  supportsBufferInvalidation: false 
  forceDisableTextureBuffers: false 
  Extensions: 
 "GL_ARB_gpu_shader_fp64" 
 "GL_ARB_texture_gather" 
 "GL_EXT_framebuffer_multisample_blit_scaled" 
 "GL_ARB_texture_rgb10_a2ui" 
 "GL_EXT_debug_label" 
 "GL_ARB_separate_shader_objects" 
 "GL_ARB_shader_subroutine" 
 "GL_APPLE_client_storage" 
 "GL_EXT_texture_filter_anisotropic" 
 "GL_ARB_texture_swizzle" 
 "GL_APPLE_row_bytes" 
 "GL_ARB_sample_shading" 
 "GL_EXT_texture_compression_s3tc" 
 "GL_ARB_explicit_attrib_location" 
 "GL_ARB_instanced_arrays" 
 "GL_ARB_tessellation_shader" 
 "GL_ARB_gpu_shader5" 
 "GL_APPLE_container_object_shareable" 
 "GL_ARB_texture_buffer_object_rgb32" 
 "GL_ARB_vertex_attrib_64bit" 
 "GL_ARB_draw_buffers_blend" 
 "GL_APPLE_flush_render" 
 "GL_EXT_debug_marker" 
 "GL_ARB_ES2_compatibility" 
 "GL_NV_texture_barrier" 
 "GL_ARB_draw_indirect" 
 "GL_ARB_internalformat_query" 
 "GL_ARB_timer_query" 
 "GL_ARB_sampler_objects" 
 "GL_APPLE_rgb_422" 
 "GL_ARB_transform_feedback2" 
 "GL_ARB_transform_feedback3" 
 "GL_ARB_occlusion_query2" 
 "GL_APPLE_texture_range" 
 "GL_ARB_vertex_type_2_10_10_10_rev" 
 "GL_ARB_texture_storage" 
 "GL_EXT_texture_sRGB_decode" 
 "GL_ARB_viewport_array" 
 "GL_ARB_shader_bit_encoding" 
 "GL_ARB_texture_query_lod" 
 "GL_ARB_blend_func_extended" 
 "GL_ARB_texture_cube_map_array" 
 "GL_ARB_shading_language_include" 

QPA OpenGL Detection Info 
  supportsDesktopGL: true 
  supportsOpenGLES: false 
  isQtPreferOpenGLES: false 

useBufferInvalidation (config option): false


Hardware Information

  GPU Acceleration: desktop
  Memory: 16384 Mb
  Number of Cores: 8
  Swap Location: /private/var/folders/3k/cfbb23wj4973b38bqbs_n1z0gn/T
  Built for: arm64+neon
  Base instruction set: arm64+neon
  Supported instruction sets: arm64+neon arm32+neon avx512bw avx512dq avx512cd
avx512f fma3+avx2 avx2 fma3+avx avx fma4 fma3+sse4.2 sse4.2 sse4.1 ssse3 sse3
sse2 

Current Settings

  Current Swap Location:
/private/var/folders/3k/cfbb23wj4973b38bqbs_n1z0gn/T
  Current Swap Location writable: true
  Undo Enabled: true
  Undo Stack Limit: 200
  Use OpenGL: true
  Use OpenGL Texture Buffer: true
  Disable Vector Optimizations: false
  Disable AVX Optimizations: false
  Canvas State: OPENGL_SUCCESS
  Autosave Interval: 420
  Use Backup Files: true
  Number of Backups Kept: 1
  Backup File Suffix: ~
  Backup Location: Same Folder as the File
  Backup Location writable: false
  Resource Location: /Users/slava/Library/Application Support/krita
  Use Win8 Pointer Input: false
  Use RightMiddleTabletButton Workaround: false
  Levels of Detail Enabled: false
  Use Zip64: f

[krita] [Bug 475052] Crop artefacts

2023-10-02 Thread Vyacheslav
https://bugs.kde.org/show_bug.cgi?id=475052

--- Comment #4 from Vyacheslav  ---
(In reply to Dmitry Kazakov from comment #1)
> Hi, Vyacheslav!
> 
> Could you check two things?
> 
> 1) What happens if you save the image (into a backup location!) and open it
> again? Do the artifacts persist?
> 2) Could you also check if you have Canvas Graphics Acceleration enabled in
> Krita settings or not?
> 
> I have a feeling like this bug might be related to bug 452854...

1) When i save image and open it again, all ok (is no artifacts). BTW to remove
artefacts need just make layer hide and visible again.
2) Canvas Graphics Acceleration - enabled

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

[krita] [Bug 475052] New: Crop artefacts

2023-09-30 Thread Vyacheslav
https://bugs.kde.org/show_bug.cgi?id=475052

Bug ID: 475052
   Summary: Crop artefacts
Classification: Applications
   Product: krita
   Version: 5.1.5
  Platform: macOS (DMG)
OS: macOS
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: * Unknown
  Assignee: krita-bugs-n...@kde.org
  Reporter: vya...@yandex.ru
  Target Milestone: ---

Created attachment 161974
  --> https://bugs.kde.org/attachment.cgi?id=161974=edit
Example of problem

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 jpg file or create new document larger than 2000x2000 px.
2. Crop it to smaller.
3. Resize and drag canvas in view

OBSERVED RESULT

Broken canvas with transparent grid artefacts.

EXPECTED RESULT

Just crop of image.

SOFTWARE/OS VERSIONS
Windows: 
macOS: Sonoma 14.0 Apple M1 Pro
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 469325] New: Who is a cheapie.

2023-05-03 Thread Vyacheslav Sakhno
https://bugs.kde.org/show_bug.cgi?id=469325

Bug ID: 469325
   Summary: Who is a cheapie.
Classification: Plasma
   Product: plasmashell
   Version: master
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: critical
  Priority: NOR
 Component: Activity Switcher
  Assignee: plasma-b...@kde.org
  Reporter: vyacheslav.sa...@yandex.ru
CC: ivan.cu...@kde.org
  Target Milestone: 1.0

I don't want to know you all but, through plasmashell you are fucked by cheapie
hackers. Or is it QML fault? Are you friends with them? Just do the job.

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

[kde] [Bug 467438] New: Clip from the library into the bin and onto the track

2023-03-16 Thread Vyacheslav
https://bugs.kde.org/show_bug.cgi?id=467438

Bug ID: 467438
   Summary: Clip from the library into the bin and onto the track
Classification: I don't know
   Product: kde
   Version: unspecified
  Platform: Other
OS: Microsoft Windows
Status: REPORTED
  Severity: task
  Priority: NOR
 Component: general
  Assignee: unassigned-b...@kde.org
  Reporter: mitchel...@mail.ru
  Target Milestone: ---

Created attachment 157332
  --> https://bugs.kde.org/attachment.cgi?id=157332=edit
on the video, I add a clip with the MLT extension to the various tracks

When I want to add a clip with an MLT extension to the timeline, I can't do it
on track v2, v3, etc. I can only do it on the v1 track. When I add on v2, for
example, the clip just goes

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

[kde] [Bug 467389] New: Copying a clip with the ALT key pressed

2023-03-15 Thread Vyacheslav
https://bugs.kde.org/show_bug.cgi?id=467389

Bug ID: 467389
   Summary: Copying a clip with the ALT key pressed
Classification: I don't know
   Product: kde
   Version: unspecified
  Platform: Other
OS: Other
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: unassigned-b...@kde.org
  Reporter: mitchel...@mail.ru
  Target Milestone: ---

Created attachment 157294
  --> https://bugs.kde.org/attachment.cgi?id=157294=edit
In this GIF I have shown how it is implemented in Addo Premiere

Hello, this is a request to add a feature. It would be very convenient if there
was an option to copy clips by holding down the ALT key. this feature would
make our tasks easier and make life a little easier. Thanks for your hard work.
An example is attached below

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

[kid3] [Bug 466264] New: Kid3 does not show some fields from mp3 tag

2023-02-22 Thread vyacheslav
https://bugs.kde.org/show_bug.cgi?id=466264

Bug ID: 466264
   Summary: Kid3 does not show some fields from mp3 tag
Classification: Applications
   Product: kid3
   Version: 3.9.x
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: uflei...@users.sourceforge.net
  Reporter: galdra...@bk.ru
  Target Milestone: ---

Created attachment 156617
  --> https://bugs.kde.org/attachment.cgi?id=156617=edit
Archive with 2 mp3 files

Kid3 does not show some fields from mp3 tag. See attachment: NoTitle.mp3 - kid3
shows empty title, NoTrackNumber.mp3 - kid3 shows empty track number.
Other multimedia programs easytag and audacious shows this files correctly.

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

[kwin] [Bug 453197] When window maximized vertically it vertical size becomes not maximized after maximize and unmaximize

2023-01-18 Thread vyacheslav
https://bugs.kde.org/show_bug.cgi?id=453197

--- Comment #9 from vyacheslav  ---
(In reply to Vlad Zahorodnii from comment #7)
> If you manually resize the window, kwin will be aware of that new size. If a
> window is initially maximized, kwin has no idea what its previous size had
> been. kwin doesn't know the previous state of apps.

Kwin should be aware of window size when it initially created not only when it
manually resized.

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

[kwin] [Bug 453197] When window maximized vertically it vertical size becomes not maximized after maximize and unmaximize

2023-01-18 Thread vyacheslav
https://bugs.kde.org/show_bug.cgi?id=453197

vyacheslav  changed:

   What|Removed |Added

 Resolution|INTENTIONAL |---
 Status|RESOLVED|REOPENED

--- Comment #6 from vyacheslav  ---
> kwin has insufficient information to properly restore the window so it picks 
> a size of its own.

Kwin restores window size correctly if window was manually resized before
maximize. So it HAS previous size information. Why it can't restore size
without manually resizing?

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

[kwin] [Bug 453197] When window maximized vertically it vertical size becomes not maximized after maximize and unmaximize

2023-01-17 Thread vyacheslav
https://bugs.kde.org/show_bug.cgi?id=453197

vyacheslav  changed:

   What|Removed |Added

 Status|RESOLVED|REOPENED
 Resolution|INTENTIONAL |---

--- Comment #4 from vyacheslav  ---
(In reply to Vlad Zahorodnii from comment #3)
> > But when window initially vertically maximized then size after unmaximize 
> > is lost
> 
> when a window is started initially vertically maximized, kwin has no idea
> what size the window must have after unmaximizing, e.g. whether it should
> have the same size as the height of the work area or something else. Atm
> iirc it picks some small size.

Why kwin does not know previous size? Kwin remember it before maximize and
restores it after unmaximize. It works for any size except when height equals
to work area size. And further: If vertical size to stretch manually to whole
work area using mouse then kwin restores it after unmaximize as expected(!).
Restoring does not working, for some reason, only if window height initially
equal to work area size.

So:
1. When window height less than work area height kwin restores it after
unmaximize - OK
2. When window height equal to work area height and height was changed manually
by mouse kwin restores it after unmaximize - OK
3. When window height equal to work area height initially and height WAS NOT
changed by mouse kwin does not restore it after unmaximize - FAIL

It is real bug. And it is very annoying restore windows vertical size after
unmaximize (using mouse) hundred times per day.

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

[kwin] [Bug 453197] New: When window maximized vertically it vertical size becomes not maximized after maximize and unmaximize

2022-04-29 Thread vyacheslav
https://bugs.kde.org/show_bug.cgi?id=453197

Bug ID: 453197
   Summary: When window maximized vertically it vertical size
becomes not maximized after maximize and unmaximize
   Product: kwin
   Version: 5.24.4
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: core
  Assignee: kwin-bugs-n...@kde.org
  Reporter: galdra...@bk.ru
  Target Milestone: ---

STEPS TO REPRODUCE
1. Run kolourpaint and maximize it vertically
2. Close kolourpaint
3. Start again kolourpaint. Height is equal to height of screen
4. Maximize it to full screen and unmaximize
5. Height of window is not equal to height of screen

When changing vertical size (using mouse) equal to size of screen then after
unmaximize size restored as expected. But when window initially vertically
maximized then size after unmaximize is lost.

OBSERVED RESULT
After unmaximize size of window always should be same as before maximize.

SOFTWARE/OS VERSIONS
KDE Plasma Version: 5.24.4
KDE Frameworks Version: 5.93
Qt Version: 5.15.3

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

[kwin] [Bug 423620] If new window maximized VERTICALLY it changes height after full maximize/unmaximize

2022-02-20 Thread vyacheslav
https://bugs.kde.org/show_bug.cgi?id=423620

vyacheslav  changed:

   What|Removed |Added

Version|5.19.2  |5.24.1

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

[plasmashell] [Bug 423676] Task buttons must never change order when sorting and grouping disabled

2022-01-30 Thread vyacheslav
https://bugs.kde.org/show_bug.cgi?id=423676

vyacheslav  changed:

   What|Removed |Added

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

--- Comment #2 from vyacheslav  ---
(In reply to galdera from comment #1)
> Looks like an old issue. Setting it to needs more info.
> Please try with a newer version(plasma 5.23.5) and if this is not an issue
> any more let us know.
> Bugs placed into NEEDSINFO status will receive a reminder if the ticket:
> 
> Is at least 15 days old
> Has not received any comment within 15 days
> 
> If a bug remains in NEEDSINFO for another 15 days with no comment, it will
> be closed as RESOLVED > WORKSFORME.
> If a bug remains in NEEDSINFO with a comment provided within less than 15
> days, no action will be taken (as it does not meet the above criteria).

It is reproducible on plasma 5.23.5

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

[plasmashell] [Bug 444834] New: "Do not sort" setting in task manager sorts some task items

2021-11-02 Thread vyacheslav
https://bugs.kde.org/show_bug.cgi?id=444834

Bug ID: 444834
   Summary: "Do not sort" setting in task manager sorts some task
items
   Product: plasmashell
   Version: 5.23.2
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Task Manager and Icons-Only Task Manager
  Assignee: h...@kde.org
  Reporter: galdra...@bk.ru
CC: plasma-b...@kde.org
  Target Milestone: 1.0

SUMMARY
Sorting and grouping task items disabled.
Demanding attention items on taskbar is moved to top of taskbar (on vertical
taskbar) when switching to another desktop and back to current desktop.

STEPS TO REPRODUCE
1. Disable sorting and grouping in task manager settings.
2. Switch to another virtual desktop when taskbar has demanding attention
items.
3. Switch back to current desktop
4. After switching items moved to beginning of taskbar

OBSERVED RESULT
Demanding attention items always moved to beginning of taskbar when switching
desktops

EXPECTED RESULT
When sorting disabled items should never change it position on taskbar.
Should be check box in "Task Manager Settings" to disable "demanding attention"
items (don't highlight its on taskbar).


SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Arch Linux
(available in About System)
KDE Plasma Version: 5.23.2
KDE Frameworks Version: 5.87
Qt Version: 5.15.2

ADDITIONAL INFORMATION

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

[kwin] [Bug 423620] If new window maximized VERTICALLY it changes height after full maximize/unmaximize

2021-11-02 Thread vyacheslav
https://bugs.kde.org/show_bug.cgi?id=423620

--- Comment #1 from vyacheslav  ---
It is same annoying behavior for horizontal maximizing.
This is very old bug. It is exists many years.

Someone can fix this?

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

[plasmashell] [Bug 444409] New: When you call the menu with the right button in the workrave program, Plasma consumes 100% of the CPU

2021-10-26 Thread Vyacheslav
https://bugs.kde.org/show_bug.cgi?id=09

Bug ID: 09
   Summary: When you call the menu with the right button in the
workrave program, Plasma consumes 100% of the CPU
   Product: plasmashell
   Version: 5.23.1
  Platform: Neon Packages
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: System Tray
  Assignee: plasma-b...@kde.org
  Reporter: so...@magsis.ru
CC: mate...@gmail.com
  Target Milestone: 1.0

SUMMARY
When you call the menu with the right button in the workrave program, Plasma
consumes 100% of the CPU

STEPS TO REPRODUCE
1. Open workrave
2. Right-click on the Workrave icon in the tray
3. The interface sticks, artifacts appear.
4. The problem appears in 90% of cases

OBSERVED RESULT


EXPECTED RESULT
About a month ago, everything worked fine.


SOFTWARE/OS VERSIONS
Operating System: KDE neon 5.23
KDE Plasma Version: 5.23.1
KDE Frameworks Version: 5.87.0
Qt Version: 5.15.3
Kernel Version: 5.11.0-38-generic (64-bit)
Graphics Platform: X11
Processors: 4 × Intel® Core™ i5-3230M CPU @ 2.60GHz
Memory: 15,5 GiB of RAM
Graphics Processor: Mesa DRI Intel® HD Graphics 4000

ADDITIONAL INFORMATION

окт 26 10:59:58 neon plasmashell[1972]: Could not find DBusMenu interface,
falling back to calling ContextMenu()
окт 26 10:59:58 neon plasmashell[1972]: Could not find DBusMenu interface,
falling back to calling ContextMenu()
окт 26 10:59:58 neon plasmashell[1972]: Could not find DBusMenu interface,
falling back to calling ContextMenu()
окт 26 10:59:58 neon plasmashell[1972]: Could not find DBusMenu interface,
falling back to calling ContextMenu()

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

[Falkon] [Bug 439298] New: User Style Sheet should override all style sheets on page

2021-06-29 Thread vyacheslav
https://bugs.kde.org/show_bug.cgi?id=439298

Bug ID: 439298
   Summary: User Style Sheet should override all style sheets on
page
   Product: Falkon
   Version: unspecified
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: now...@gmail.com
  Reporter: galdra...@bk.ru
  Target Milestone: ---

Created attachment 139739
  --> https://bugs.kde.org/attachment.cgi?id=139739=edit
User css

SUMMARY
Some time ago browsers has very ugly behavior to draw underlined links using
NOT SOLID line.
This behavior can be removed from all pages using "User Style Sheet" file with
content
* { text-decoration-skip-ink: none; }

It is works on most web sites. But on some sites it is not worked. One of this
sites is https://archlinux.org.
On firefox browser using userContent.css it works on ALL sites as expected.


STEPS TO REPRODUCE
1. Specify "User Style Sheet" file from attachment in falkon preferences
2. Open https://archlinux.org (or https://archlinux.org/packages)
3. Move mouse cursor on any link that contains letter p,q,g,y (for example
"Packages", "Bugs" on page top). Link becomes underlined and line is not solid.
4. Now you can go https://bugs.kde.org find any link that becomes underlined
under mouse cursor and contain letter p,q,g,y.
And you can see that line is solid.

OBSERVED RESULT
On some web pages attached css file is not work

EXPECTED RESULT
Attached css file should work on all web pages(like in firefox browser)


SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: any linux
(available in About System)
KDE Plasma Version: Any Plasma (5.20,5.21,5.22)
KDE Frameworks Version: 5.83
Qt Version: 5.15.2

ADDITIONAL INFORMATION

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

[plasmashell] [Bug 433782] Task manager buttons shows incorrect title for some applications

2021-06-28 Thread vyacheslav
https://bugs.kde.org/show_bug.cgi?id=433782

vyacheslav  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|REPORTED|RESOLVED

--- Comment #2 from vyacheslav  ---
It seems has been fixed in plasma 5.22.

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

[systemsettings] [Bug 435128] New: Incorrect highlighted text color in system color settings

2021-03-29 Thread vyacheslav
https://bugs.kde.org/show_bug.cgi?id=435128

Bug ID: 435128
   Summary: Incorrect highlighted text color in system color
settings
   Product: systemsettings
   Version: 5.21.3
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: kcm_colors
  Assignee: plasma-b...@kde.org
  Reporter: galdra...@bk.ru
CC: jpwhit...@kde.org, mwoehlke.fl...@gmail.com
  Target Milestone: ---

SUMMARY
System color settings widget shows highlighted text color using color from
CURRENT color scheme for ALL color schemes.

STEPS TO REPRODUCE
1. Go to system color settings
2. See that highlighted text color is same for all color schemes

OBSERVED RESULT
Highlighted text color is same for all color schemes

EXPECTED RESULT
Highlighted text color should be from every color scheme.

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

ADDITIONAL INFORMATION

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

[plasmashell] [Bug 433782] Task manager buttons shows incorrect title for some applications

2021-03-24 Thread vyacheslav
https://bugs.kde.org/show_bug.cgi?id=433782

--- Comment #1 from vyacheslav  ---
If replace symlink /usr/lib/libtaskmanager.so.6 pointing to
libtaskmanager.so.5.20.5 from plasma 5.20.5 it is working as expected.

So problem in libtaskmanager.so

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

[plasmashell] [Bug 433782] New: Task manager buttons shows incorrect title for some applications

2021-03-01 Thread vyacheslav
https://bugs.kde.org/show_bug.cgi?id=433782

Bug ID: 433782
   Summary: Task manager buttons shows incorrect title for some
applications
   Product: plasmashell
   Version: master
  Platform: Archlinux Packages
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Task Manager and Icons-Only Task Manager
  Assignee: h...@kde.org
  Reporter: galdra...@bk.ru
CC: plasma-b...@kde.org
  Target Milestone: 1.0

SUMMARY
Since 5.21 task manager buttons shows incorrect title for some applications.
This is happen sometimes for different applications but it is 100% reproducible
for Qmmp audio player. Qmmp shows playing file in application title but task
manager button has only one word "Qmmp".


STEPS TO REPRODUCE
1. Task manager should display text on buttons (not icons-only view).
2. Run qmmp and start playing any audio file.
3. Compare task manager button text of qmmp and text displayed by kwin when
switching through applications using Alt+Tab.

OBSERVED RESULT

EXPECTED RESULT
Text on task manager buttons should same as shows kwin when switching using
Alt+Tab. As it was in 5.20 and previous versions.

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

ADDITIONAL INFORMATION

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

[plasmashell] [Bug 428197] Since plasma 5.20 task button is not highlighted when mouse on button

2020-10-27 Thread vyacheslav
https://bugs.kde.org/show_bug.cgi?id=428197

vyacheslav  changed:

   What|Removed |Added

 Status|NEEDSINFO   |RESOLVED
 Resolution|WAITINGFORINFO  |NOT A BUG

--- Comment #5 from vyacheslav  ---
This is not a bug. I found problem in my system.

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

[plasmashell] [Bug 428197] Since plasma 5.20 task button is not highlighted when mouse on button

2020-10-26 Thread vyacheslav
https://bugs.kde.org/show_bug.cgi?id=428197

--- Comment #3 from vyacheslav  ---
(In reply to Nate Graham from comment #2)
> Looks like you're using a non-default Plasma theme. Which one is it?

When this bug occurs it is reproduced on any theme.

It is strange reproducibility. After fresh install of plasma-desktop all works
as expected. But after 1-2 days buttons stops highlighting. May be changing
some settings affects this behavior.

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

[plasmashell] [Bug 428198] New: Plasma 5.20 system tray on vertical panel overlaps next panel item

2020-10-24 Thread vyacheslav
https://bugs.kde.org/show_bug.cgi?id=428198

Bug ID: 428198
   Summary: Plasma 5.20 system tray on vertical panel overlaps
next panel item
   Product: plasmashell
   Version: 5.20.1
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: System Tray
  Assignee: plasma-b...@kde.org
  Reporter: galdra...@bk.ru
  Target Milestone: 1.0

Created attachment 132692
  --> https://bugs.kde.org/attachment.cgi?id=132692=edit
Screenshot that explains this bug

SUMMARY
See screenshot

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Arch Linux
KDE Plasma Version: 5.21
KDE Frameworks Version: 5.75
Qt Version: 5.15.1

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

[plasmashell] [Bug 428197] New: Since plasma 5.20 task button is not highlighted when mouse on button

2020-10-24 Thread vyacheslav
https://bugs.kde.org/show_bug.cgi?id=428197

Bug ID: 428197
   Summary: Since plasma 5.20 task button is not highlighted when
mouse on button
   Product: plasmashell
   Version: 5.20.1
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Task Manager and Icons-Only Task Manager
  Assignee: h...@kde.org
  Reporter: galdra...@bk.ru
CC: plasma-b...@kde.org
  Target Milestone: 1.0

Created attachment 132690
  --> https://bugs.kde.org/attachment.cgi?id=132690=edit
Screenshot for plasma task buttons 5.19 and 5.20

SUMMARY
Task button is not highlighted when mouse on button.
See attached screenshot

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Arch Linux
KDE Plasma Version: 5.20.1
KDE Frameworks Version: 5.75
Qt Version: 5.15.1

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

[kwin] [Bug 387775] KWin touch screen edge creates a 1 pixel dead zone on that edge that doesn't accept mouse clicks or scrolls outside of full-screen mode

2020-10-20 Thread vyacheslav
https://bugs.kde.org/show_bug.cgi?id=387775

--- Comment #42 from vyacheslav  ---
Following c++ code removes this stupid 1 pixel area. It can be compiled and
placed to autostart or executed manually. After changing some system settings
(for example after changing system font) it is need to run it again.
It is fix this bug for me.


#include 
#include 
#include 
#include 

int main(int argc, char* argv[])
{
   QApplication app(argc, argv);

   xcb_connection_t* conn = QX11Info::connection();
   xcb_query_tree_cookie_t cookie = xcb_query_tree(conn,
QX11Info::appRootWindow());
   if (xcb_query_tree_reply_t* reply = xcb_query_tree_reply(conn, cookie,
NULL))
   {
  xcb_window_t* children = xcb_query_tree_children(reply);
  for(int i = 0, size = xcb_query_tree_children_length(reply); i < size;
i++)
  {
 xcb_get_geometry_cookie_t cookie = xcb_get_geometry(conn,
children[i]);
 if (xcb_get_geometry_reply_t* geomReply = xcb_get_geometry_reply(conn,
cookie, NULL))
 {
if (geomReply->x == 0 && geomReply->width == 1)
{
   if (geomReply->height > 500)
   {
  const static uint32_t values[] = { 1, 1 };
  xcb_configure_window(conn, children[i],
XCB_CONFIG_WINDOW_WIDTH | XCB_CONFIG_WINDOW_HEIGHT, values);
   }
}
free(geomReply);
 }
  }
  free(reply);
   }
   return 0;
}

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

[kwin] [Bug 424096] New: kwin and left vertical plasma panel issue

2020-07-11 Thread vyacheslav
https://bugs.kde.org/show_bug.cgi?id=424096

Bug ID: 424096
   Summary: kwin and left vertical plasma panel issue
   Product: kwin
   Version: 5.19.3
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: core
  Assignee: kwin-bugs-n...@kde.org
  Reporter: galdra...@bk.ru
  Target Milestone: ---

SUMMARY
When plasma panel has BOTTOM HORIZONTAL position most BOTTOM cursor position
belongs to panel.
Mouse click on most bottom position works on taskbar as expected.
When plasma panel has TOP HORIZONTAL position most TOP cursor position belongs
to panel.
When plasma panel has RIGHT VERTICAL position most RIGHT cursor position
belongs to panel.

But when plasma panel has LEFT VERTICAL position most LEFT cursor position DOES
NOT belong to panel.
And click on most left cursor position not working.

Investigation of this issue shows that kwin creates window of 1 pixel width on
left position of screen.
For what this window?
No other window manager do this.

STEPS TO REPRODUCE
Try mouse click on last cursor position for every screen edge and corresponding
taskbar position (left,top,right,bottom)

OBSERVED RESULT
For top,bottom,right position of plasma panel click on last corresponding
cursor position works as expected.
For left position of plasma panel click on last corresponding cursor position
is not working.

EXPECTED RESULT
For left position of panel most left cursor position should belong to panel


SOFTWARE/OS VERSIONS
Linux/KDE Plasma: ArchLinux
KDE Plasma Version: 5.19.3
KDE Frameworks Version: 5.71
Qt Version: 5.15

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

[okular] [Bug 424095] New: Since okular in kde applications 20.04 scrolling using up/down keys inconvenient

2020-07-11 Thread vyacheslav
https://bugs.kde.org/show_bug.cgi?id=424095

Bug ID: 424095
   Summary: Since okular in kde applications 20.04 scrolling using
up/down keys inconvenient
   Product: okular
   Version: 1.10.3
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: okular-de...@kde.org
  Reporter: galdra...@bk.ru
  Target Milestone: ---

SUMMARY
Okular from kde applications 19.12 and earlier scrolls approximately one text
line when using up/down keys.
Since 20.04 when pressing up/down key okular jumps over several text lines.
When reading text this jump confuse eyes from current reading position. It is
very inconvenient.

STEPS TO REPRODUCE
Compare scroll lines/pixels count using up/down keys in okular from kde
applications 19.12 and 20.04

EXPECTED RESULT
Scroll count using up/down keys should be as it was in okular from 19.12


SOFTWARE/OS VERSIONS
Linux/KDE Plasma: ArchLinux
KDE Plasma Version: 5.19.3
KDE Frameworks Version: 5.71
Qt Version: 5.15

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

[plasmashell] [Bug 423676] New: Task buttons must never change order when sorting and grouping disabled

2020-06-29 Thread vyacheslav
https://bugs.kde.org/show_bug.cgi?id=423676

Bug ID: 423676
   Summary: Task buttons must never change order when sorting and
grouping disabled
   Product: plasmashell
   Version: master
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Task Manager
  Assignee: h...@kde.org
  Reporter: galdra...@bk.ru
CC: plasma-b...@kde.org
  Target Milestone: 1.0

SUMMARY
When inactive application creates windows it becomes highlighted on task bar.
When task manager has such highlighted buttons after changing desktop all
highlighted buttons moved to up (vertical panel) or to left (horizontal panel).

STEPS TO REPRODUCE
1. Disable sorting and grouping in panel task manager.
2. Achieve task manager has highlighted buttons. For example, run audacity and
open a few mp3 files and while it open files switch to another application.
Typically highlighted buttons located and end of task buttons list.
3. Switch to another desktop

OBSERVED RESULT
After switching desktop highlighted buttons changed its positions on task bar.
All other buttons stays on its positions.

EXPECTED RESULT
When sorting and grouping disabled any task bar button must never change it
position on task bar.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Arch Linux
KDE Plasma Version: 5.19.2
KDE Frameworks Version: 5.71
Qt Version: 5.15

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

[plasmashell] [Bug 423625] Clipboard is not working when clipboard tray icon disabled

2020-06-29 Thread vyacheslav
https://bugs.kde.org/show_bug.cgi?id=423625

--- Comment #2 from vyacheslav  ---
(In reply to Konrad Materka from comment #1)
> I don't understand what is d=the issue or I cannot reproduce. I disabled
> Clipboard applet in System Tray setting, copy works as expected.
> 
> Can you describe in more details? In addition, please add information about
> your system (Plasma/Qt/Frameworks versions, X11 or Wayland etc)

Copy/paste works without clipboard service.
Main feature of clipboard service is ability to paste text when application
that copied text to clipboard is exited.
Without service clipboard is cleared when application that copied text is
exited.

Try disable icon, copy text from any application and close it. You can't paste
just copied text anywhere but ought to be.

System versions currently latest: plasma 5.19.2,qt 5.15,framework 5.71,X11

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

[plasmashell] [Bug 423625] New: Clipboard is not working when clipboard tray icon disabled

2020-06-28 Thread vyacheslav
https://bugs.kde.org/show_bug.cgi?id=423625

Bug ID: 423625
   Summary: Clipboard is not working when clipboard tray icon
disabled
   Product: plasmashell
   Version: master
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: System Tray
  Assignee: plasma-b...@kde.org
  Reporter: galdra...@bk.ru
  Target Milestone: 1.0

OBSERVED RESULT
Clipboard is not working when clipboard tray icon disabled

EXPECTED RESULT
Clipboard service must be always running independently on hidden/visible tray
icon.

I never use clipboard icon for many years. I assume most of peaple also never
use it. But clipboard service is useful and must be running.

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

[ktorrent] [Bug 423623] New: Quit confirmation using tray icon is annoying

2020-06-28 Thread vyacheslav
https://bugs.kde.org/show_bug.cgi?id=423623

Bug ID: 423623
   Summary: Quit confirmation using tray icon is annoying
   Product: ktorrent
   Version: unspecified
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: joris.guis...@gmail.com
  Reporter: galdra...@bk.ru
  Target Milestone: ---

SUMMARY
Pressing quit in ktorrent application menu quits as expected.
Pressing quit in ktorrent tray icon CONFIRMS quit.

EXPECTED RESULT
Confirming exit annoying in any application.
Quit confirmation should be removed.

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

[kdesu] [Bug 423622] New: "Remember password" check box is not working if password contains double quote(")

2020-06-28 Thread vyacheslav
https://bugs.kde.org/show_bug.cgi?id=423622

Bug ID: 423622
   Summary: "Remember password" check box is not working if
password contains double quote(")
   Product: kdesu
   Version: unspecified
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: kdesu
  Assignee: kdesu-bugs-n...@kde.org
  Reporter: galdra...@bk.ru
  Target Milestone: ---

STEPS TO REPRODUCE
1. Set root password to word containing double quote(")
2. Run kdesu any_application
3. Enter password and check "Remember password"

OBSERVED RESULT
Application does not start. No errors displayed. kdesu silently quits and all.

EXPECTED RESULT
kdesu should understand all printable characters in password

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Arch linux
KDE Plasma Version: 5.19.2
KDE Frameworks Version: 5.71
Qt Version: 5.15

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

[kwin] [Bug 423620] New: If new window maximized VERTICALLY it changes height after full maximize/unmaximize

2020-06-28 Thread vyacheslav
https://bugs.kde.org/show_bug.cgi?id=423620

Bug ID: 423620
   Summary: If new window maximized VERTICALLY it changes height
after full maximize/unmaximize
   Product: kwin
   Version: 5.19.2
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: core
  Assignee: kwin-bugs-n...@kde.org
  Reporter: galdra...@bk.ru
  Target Milestone: ---

STEPS TO REPRODUCE
1. Run kolourpaint and maximize it vertically
2. Close kolourpaint
3. Start again kolourpaint. Height is equal to height of screen
4. Maximize it to full screen and unmaximize
5. Height of window is not equal to height of screen

OBSERVED RESULT
After first unmaximize kolourpaint window loses its height equal to height of
screen. But if maximize it vertically again all next maximize/unmaximize works
as expected. It affects only FIRST maximize/unmaximize.

All above also valid for horizontal maximizing. First maximize/unmaximize
changes initial width of window.

Very annoying behavior.

EXPECTED RESULT
Height(or width) equal to height(or width) of screen should be preserved after
first unmaximize as all next maximize/unmaximize.

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

[valgrind] [Bug 400099] New: Memcheck produces truncated backtrace when len(argv + env) = 4096

2018-10-21 Thread Vyacheslav Belous
https://bugs.kde.org/show_bug.cgi?id=400099

Bug ID: 400099
   Summary: Memcheck produces truncated backtrace when len(argv +
env) = 4096
   Product: valgrind
   Version: unspecified
  Platform: unspecified
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: memcheck
  Assignee: jsew...@acm.org
  Reporter: belous...@yandex.ru
  Target Milestone: ---

Created attachment 115798
  --> https://bugs.kde.org/attachment.cgi?id=115798=edit
Valgrind result with '-v'

SUMMARY
It looks like memcheck could produce truncated backtrace when "stacksize" in
coregrind/m_initimg/initimg-linux.c:setup_client_stack becomes equal to 4096.

STEPS TO REPRODUCE
1. docker run -it --rm i386/centos:centos7 linux32
2. yum install vim gcc git make automake autoconf gcc-objc libobjc
3. build and install valgrind with patch (see ADDITIONAL INFORMATION)
4. cd /root
5. echo '
void foo(void *f) 
{
int bar(void) { return f == (void *)0; }
void *ff = bar; (void)ff;
}' > lib.c
6. gcc -shared -fPIC lib.c -ggdb3  -o libxxx.so
7. echo 'int main(void) { return 0; }' > xxx.c
8. gcc -ggdb3 -o binary  xxx.c -lobjc -L. -lxxx
9. LD_LIBRARY_PATH=. /usr/local/bin/valgrind --leak-check=full ./binary `perl
-e '@o = map { "a" x 200 } (1 .. int($ARGV[0]/200)); push @o, "b" x ($ARGV[0] %
200); print "@o"' 1924`

OBSERVED RESULT
stringsize=3808 auxsize=168 stacksize=4096 maxsize=0x80
clstack_start 0xFED9C000
clstack_end   0xFED9DFFF

==12870== 16 bytes in 2 blocks are definitely lost in loss record 4 of 11
==12870==at 0x402B4C8: malloc (vg_replace_malloc.c:299)

EXPECTED RESULT
...
==16059== 8 bytes in 1 blocks are definitely lost in loss record 5 of 48
==16059==at 0x402B4C8: malloc (vg_replace_malloc.c:299)
==16059==by 0x404829A: objc_malloc (in /usr/lib/libobjc.so.4.0.0)
==16059==by 0x4046EEE: ??? (in /usr/lib/libobjc.so.4.0.0)
==16059==by 0x404710F: ??? (in /usr/lib/libobjc.so.4.0.0)
==16059==by 0x404789E: __objc_exec_class (in /usr/lib/libobjc.so.4.0.0)
==16059==by 0x404125C: ??? (in /usr/lib/libobjc.so.4.0.0)
==16059==by 0x401020D: _dl_init (in /usr/lib/ld-2.17.so)
==16059==by 0x400104E: ??? (in /usr/lib/ld-2.17.so)


ADDITIONAL INFORMATION
# docker, because I can reproduce it only on centos.i386 with packages:
rpm -qa | grep gcc
libgcc-4.8.5-28.el7_5.1.i686
gcc-4.8.5-28.el7_5.1.i686
gcc-objc-4.8.5-28.el7_5.1.i686

Valgrind built from master (d00dd9c2dd3f2e623f4db48d66d3b54b858842dd) with
patch:
diff --git a/coregrind/m_initimg/initimg-linux.c
b/coregrind/m_initimg/initimg-linux.c
index 61cc458..78e3fc5 100644
--- a/coregrind/m_initimg/initimg-linux.c
+++ b/coregrind/m_initimg/initimg-linux.c
@@ -492,7 +492,7 @@ Addr setup_client_stack( void*  init_sp,
/* The max stack size */
clstack_max_size = VG_PGROUNDUP(clstack_max_size);

-   if (0)
+   if (1)
   VG_(printf)("stringsize=%u auxsize=%u stacksize=%u maxsize=0x%lx\n"
   "clstack_start %p\n"
   "clstack_end   %p\n",

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

[plasmashell] [Bug 385466] New: Task manager and system tray on vertical panel on plasma 5.6 and later versions

2017-10-07 Thread vyacheslav
https://bugs.kde.org/show_bug.cgi?id=385466

Bug ID: 385466
   Summary: Task manager and system tray on vertical panel on
plasma 5.6 and later versions
   Product: plasmashell
   Version: 5.10.5
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Task Manager
  Assignee: h...@kde.org
  Reporter: galdra...@bk.ru
CC: plasma-b...@kde.org
  Target Milestone: 1.0

Created attachment 108222
  --> https://bugs.kde.org/attachment.cgi?id=108222=edit
Screenshot with plasma 5.6.5 and 5.10.5 that describes this issue

Task manager and system tray on plasma 5.10.5 have bad behavior and look.
Plasma 5.6.5 is better. See attached screenshot with descriptions

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

[yakuake] [Bug 381084] Unexpected switching the active window after hide/show

2017-06-10 Thread Vyacheslav
https://bugs.kde.org/show_bug.cgi?id=381084

Vyacheslav <alexeev.c...@gmail.com> changed:

   What|Removed |Added

Summary|Switching the active window |Unexpected switching the
   |after hide/show |active window after
   ||hide/show

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

[yakuake] [Bug 381084] New: Switching the active window after hide/show

2017-06-10 Thread Vyacheslav
https://bugs.kde.org/show_bug.cgi?id=381084

Bug ID: 381084
   Summary: Switching the active window after hide/show
   Product: yakuake
   Version: 3.0.4
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: minor
  Priority: NOR
 Component: general
  Assignee: h...@kde.org
  Reporter: alexeev.c...@gmail.com
  Target Milestone: ---

I uses yakuake with 2 splitted windows.
When I hide and show yakuake, it switch active window.

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

[kwin] [Bug 375047] New: plasma crashed

2017-01-14 Thread Vyacheslav
https://bugs.kde.org/show_bug.cgi?id=375047

Bug ID: 375047
   Summary: plasma crashed
   Product: kwin
   Version: 5.8.5
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kwin-bugs-n...@kde.org
  Reporter: slavca2...@yandex.ru
  Target Milestone: ---

Application: kwin_x11 (5.8.5)

Qt Version: 5.7.1
Frameworks Version: 5.29.0
Operating System: Linux 4.8.13-1-ARCH x86_64
Distribution (Platform): Archlinux Packages

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

выдает ошибку и закрытие любого приложения при запуске этого приложения

The crash can be reproduced sometimes.

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

Thread 6 (Thread 0x7f1b110e5700 (LWP 781)):
#0  0x7f1b37218551 in ppoll () at /usr/lib/libc.so.6
#1  0x7f1b348c75f9 in qt_safe_poll(pollfd*, unsigned long, timespec const*)
() at /usr/lib/libQt5Core.so.5
#2  0x7f1b348c8efa in
QEventDispatcherUNIX::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#3  0x7f1b34875d3a in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#4  0x7f1b34698063 in QThread::exec() () at /usr/lib/libQt5Core.so.5
#5  0x7f1b2f1ebe75 in  () at /usr/lib/libQt5Qml.so.5
#6  0x7f1b3469ccf8 in  () at /usr/lib/libQt5Core.so.5
#7  0x7f1b30491454 in start_thread () at /usr/lib/libpthread.so.0
#8  0x7f1b372217df in clone () at /usr/lib/libc.so.6

Thread 5 (Thread 0x7f1aff014700 (LWP 571)):
#0  0x7f1b3049710f in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7f1b3380d1f4 in  () at /usr/lib/libQt5Script.so.5
#2  0x7f1b3380d239 in  () at /usr/lib/libQt5Script.so.5
#3  0x7f1b30491454 in start_thread () at /usr/lib/libpthread.so.0
#4  0x7f1b372217df in clone () at /usr/lib/libc.so.6

Thread 4 (Thread 0x7f1b12af6700 (LWP 567)):
#0  0x7f1b348c8deb in
QEventDispatcherUNIX::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#1  0x7f1b34875d3a in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#2  0x7f1b34698063 in QThread::exec() () at /usr/lib/libQt5Core.so.5
#3  0x7f1b2f1ebe75 in  () at /usr/lib/libQt5Qml.so.5
#4  0x7f1b3469ccf8 in  () at /usr/lib/libQt5Core.so.5
#5  0x7f1b30491454 in start_thread () at /usr/lib/libpthread.so.0
#6  0x7f1b372217df in clone () at /usr/lib/libc.so.6

Thread 3 (Thread 0x7f1b1904e700 (LWP 529)):
#0  0x7f1b348c8e58 in
QEventDispatcherUNIX::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#1  0x7f1b34875d3a in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#2  0x7f1b34698063 in QThread::exec() () at /usr/lib/libQt5Core.so.5
#3  0x7f1b2e3b5de5 in  () at /usr/lib/libQt5DBus.so.5
#4  0x7f1b3469ccf8 in  () at /usr/lib/libQt5Core.so.5
#5  0x7f1b30491454 in start_thread () at /usr/lib/libpthread.so.0
#6  0x7f1b372217df in clone () at /usr/lib/libc.so.6

Thread 2 (Thread 0x7f1b1b176700 (LWP 518)):
#0  0x7f1b3721848d in poll () at /usr/lib/libc.so.6
#1  0x7f1b363588e0 in  () at /usr/lib/libxcb.so.1
#2  0x7f1b3635a679 in xcb_wait_for_event () at /usr/lib/libxcb.so.1
#3  0x7f1b1c04e789 in  () at /usr/lib/libQt5XcbQpa.so.5
#4  0x7f1b3469ccf8 in  () at /usr/lib/libQt5Core.so.5
#5  0x7f1b30491454 in start_thread () at /usr/lib/libpthread.so.0
#6  0x7f1b372217df in clone () at /usr/lib/libc.so.6

Thread 1 (Thread 0x7f1b377f3880 (LWP 494)):
[KCrash Handler]
#6  0x40868c0f in  ()
#7  0x7f1b25b8a2d0 in  () at /usr/lib/libnvidia-glcore.so.340.101
#8  0x7f1b25b91360 in  () at /usr/lib/libnvidia-glcore.so.340.101
#9  0x7f1b257fe378 in  () at /usr/lib/libnvidia-glcore.so.340.101
#10 0x7f1b350d5c04 in QOpenGLTextureGlyphCache::resizeTextureData(int, int)
() at /usr/lib/libQt5Gui.so.5
#11 0x7f1b350762a6 in QTextureGlyphCache::fillInPendingGlyphs() () at
/usr/lib/libQt5Gui.so.5
#12 0x7f1b2f89edd7 in  () at /usr/lib/libQt5Quick.so.5
#13 0x7f1b2f89cc84 in  () at /usr/lib/libQt5Quick.so.5
#14 0x7f1b2f9249b7 in QQuickTextNode::addGlyphs(QPointF const&, QGlyphRun
const&, QColor const&, QQuickText::TextStyle, QColor const&, QSGNode*) () at
/usr/lib/libQt5Quick.so.5
#15 0x7f1b2f9296c4 in  () at /usr/lib/libQt5Quick.so.5
#16 0x7f1b2f92593c in QQuickTextNode::addTextLayout(QPointF const&,
QTextLayout*, QColor const&, QQuickText::TextStyle, QColor const&, QColor
const&, QColor const&, QColor const&, int, int, int, int) () at
/usr/lib/libQt5Quick.so.5
#17 0x7f1b2f924397 in QQuickText::updatePaintNode(QSGNode*,
QQuickItem::UpdatePaintNodeData*) () at /usr/lib/libQt5Quick.so.5
#18 0x7f1b2f8e1810 in QQuickWindowPrivate::updateDirtyNode(QQuickItem*) ()
at