[KBibTeX] [Bug 476502] binary and libraries are compiled with rpath

2023-11-22 Thread Cor Blom
https://bugs.kde.org/show_bug.cgi?id=476502

--- Comment #6 from Cor Blom  ---
OK. Is asked on the openSUSE list and the suggestion was to add
-DCMAKE_SKIP_RPATH=FALSE and -DCMAKE_SKIP_INSTALL_RPATH=TRUE to cmake, which
solves the issue. Still not clear why kbibtex needs this and other apps not.
I'll let you know when I hear something about that.

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

[KBibTeX] [Bug 476502] binary and libraries are compiled with rpath

2023-11-20 Thread Cor Blom
https://bugs.kde.org/show_bug.cgi?id=476502

--- Comment #4 from Cor Blom  ---
(In reply to Thomas Fischer from comment #3)
> (In reply to Cor Blom from comment #2)
> > Sorry, cannot help you with that. I maintain kbibtex for openSUSE and with
> > this new version there is a rpmlint check that complains about RPATH. There
> > is a workaround that I use (chrpath). I don't know anything about build
> > systems apart from being able to compile a program.
> Ok. Can you check how other KDE program's packages handle RPATH? For
> example, passing additional arguments to cmake, patching the build system,
> or simply ignoring the whole issue? Best check for Extra Gear programs that
> are not (yet) part of the KDE Applications release.

I don't see anything that can explain this. RPATH is not mentioned. As far as I
understand the default cmake behavior is that RPATH is used during build but
removed during install, so no special treatment should be necessary.

The only thing I could find is:

https://gitlab.kitware.com/cmake/community/-/wikis/doc/cmake/RPATH-handling#caveats

This is really not my area of expertise. Sorry.

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

[KBibTeX] [Bug 476502] binary and libraries are compiled with rpath

2023-11-19 Thread Cor Blom
https://bugs.kde.org/show_bug.cgi?id=476502

--- Comment #2 from Cor Blom  ---
Sorry, cannot help you with that. I maintain kbibtex for openSUSE and with this
new version there is a rpmlint check that complains about RPATH. There is a
workaround that I use (chrpath). I don't know anything about build systems
apart from being able to compile a program.

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

[KBibTeX] [Bug 476502] New: binary and libraries are compiled with rpath

2023-11-03 Thread Cor Blom
https://bugs.kde.org/show_bug.cgi?id=476502

Bug ID: 476502
   Summary: binary and libraries are compiled with rpath
Classification: Applications
   Product: KBibTeX
   Version: 0.10
  Platform: openSUSE
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Compiling/packaging
  Assignee: fisc...@unix-ag.uni-kl.de
  Reporter: corne...@solcon.nl
  Target Milestone: ---

SUMMARY
On openSUSE's OBS when building kbibtex 0.10 I get an error because rpaths are
included. This is forbidden in the distro (and other distros).

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. Build a package of kbibtex on OBS
2. See the rpmlint output
3. Build fails because of presence rpath in binary and libraries

OBSERVED RESULT


EXPECTED RESULT
Either there is an option to disable rpath, or the buildsystem must be updated
to make this possible or that rpath is removed.

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

ADDITIONAL INFORMATION
See https://en.opensuse.org/openSUSE:Packaging_checks
and: https://wiki.debian.org/RpathIssue

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

[kdelibs] [Bug 204886] Automatic selection on mouse over has no effect in system settings

2023-09-03 Thread Cor
https://bugs.kde.org/show_bug.cgi?id=204886

Cor  changed:

   What|Removed |Added

 CC||kde-b...@corz.org

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

[kwin] [Bug 342326] window contents freeze

2022-07-28 Thread cor
https://bugs.kde.org/show_bug.cgi?id=342326

--- Comment #42 from cor  ---
Does KDE share with Ubuntu? Seems you should have directed this to the Kubuntu
team. I am only reporting what I have encountered. And to tell you the truth,
this is not working for me. I regret ever contacting bugs.

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

[kwin] [Bug 342326] window contents freeze

2022-07-28 Thread cor
https://bugs.kde.org/show_bug.cgi?id=342326

--- Comment #40 from cor  ---
That's not a part of Kubuntu 20.04. I am an end user, not a developer or
tester.

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

[kwin] [Bug 342326] window contents freeze

2022-07-28 Thread cor
https://bugs.kde.org/show_bug.cgi?id=342326

--- Comment #38 from cor  ---
Version 5.18.7 still has an issue. After about 1-2 days following a reboot,
portions of the screen stop being repainted. I can correct this by changing any
of the Compositor settings.  Lately, I have been checking and unchecking the
"Allow applications to block compositing". This will fix only for an
indeterminate time.

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

[krita] [Bug 456084] New: Krita crashes when attempting to save a file

2022-06-28 Thread Ome Cor
https://bugs.kde.org/show_bug.cgi?id=456084

Bug ID: 456084
   Summary: Krita crashes when attempting to save a file
   Product: krita
   Version: 5.0.5
  Platform: Neon Packages
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: General
  Assignee: krita-bugs-n...@kde.org
  Reporter: oco...@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 a (any) image file by right-clicking on the file in Dolphin or by
opening the file in Krita
2. Save the file in any other format 

OBSERVED RESULT
Krita crashes without saving the file in the new format or with any changes
made to the image

EXPECTED RESULT
Krita should save the file in the chosen format with all changes made

SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: Linux (x86_64) release 5.13.0-51-generic / KDE Neon
(available in About System)
KDE Plasma Version: 5.25.0
KDE Frameworks Version:  v5.95.0
Qt Version: 5.15.4

ADDITIONAL INFORMATION
Krita

 Version: 5.0.5
 Languages: en_US, en, en_GB, en, nl_NL, nl, en_US, en, en_US, en
 Hidpi: false

Qt

  Version (compiled): 5.15.3
  Version (loaded): 5.15.4

OS Information

  Build ABI: x86_64-little_endian-lp64
  Build CPU: x86_64
  CPU: x86_64
  Kernel Type: linux
  Kernel Version: 5.13.0-51-generic
  Pretty Productname: KDE neon User - 5.25
  Product Type: neon
  Product Version: 20.04
  Desktop: KDE

OpenGL Info

  Vendor:  "Intel" 
  Renderer:  "Mesa Intel(R) Xe Graphics (TGL GT2)" 
  Version:  "4.6 (Compatibility Profile) Mesa 21.2.6" 
  Shading language:  "4.60" 
  Requested format:  QSurfaceFormat(version 3.0, options
QFlags(DeprecatedFunctions), depthBufferSize 24,
redBufferSize 8, greenBufferSize 8, blueBufferSize 8, alphaBufferSize 8,
stencilBufferSize 8, samples -1, swapBehavior QSurfaceFormat::DoubleBuffer,
swapInterval 0, colorSpace QSurfaceFormat::DefaultColorSpace, profile 
QSurfaceFormat::CompatibilityProfile) 
  Current format:  QSurfaceFormat(version 4.6, options
QFlags(DeprecatedFunctions), depthBufferSize 24,
redBufferSize 8, greenBufferSize 8, blueBufferSize 8, alphaBufferSize 8,
stencilBufferSize 8, samples -1, swapBehavior QSurfaceFormat::DoubleBuffer,
swapInterval 0, colorSpace QSurfaceFormat::DefaultColorSpace, profile 
QSurfaceFormat::CompatibilityProfile) 
 Version: 4.6
 Supports deprecated functions true 
 is OpenGL ES: false 
  supportsBufferMapping: true 
  supportsBufferInvalidation: true 
  Extensions: 
 "GL_EXT_framebuffer_multisample_blit_scaled" 
 "GL_ARB_shader_texture_lod" 
 "GL_NV_light_max_exponent" 
 "GL_ARB_fragment_coord_conventions" 
 "GL_ARB_spirv_extensions" 
 "GL_ARB_texture_env_add" 
 "GL_ARB_vertex_attrib_binding" 
 "GL_NV_compute_shader_derivatives" 
 "GL_ARB_shader_viewport_layer_array" 
 "GL_IBM_rasterpos_clip" 
 "GL_ARB_compute_variable_group_size" 
 "GL_ARB_explicit_uniform_location" 
 "GL_ARB_explicit_attrib_location" 
 "GL_EXT_point_parameters" 
 "GL_ARB_texture_env_combine" 
 "GL_EXT_copy_texture" 
 "GL_ARB_enhanced_layouts" 
 "GL_EXT_gpu_shader4" 
 "GL_ATI_draw_buffers" 
 "GL_EXT_shader_samples_identical" 
 "GL_ATI_blend_equation_separate" 
 "GL_ARB_transform_feedback_instanced" 
 "GL_ARB_base_instance" 
 "GL_ARB_shader_atomic_counter_ops" 
 "GL_ARB_gl_spirv" 
 "GL_KHR_context_flush_control" 
 "GL_ARB_seamless_cube_map" 
 "GL_ARB_texture_cube_map_array" 
 "GL_EXT_texture_env_add" 
 "GL_NV_texture_barrier" 
 "GL_OES_read_format" 
 "GL_AMD_draw_buffers_blend" 
 "GL_KHR_blend_equation_advanced" 
 "GL_ARB_stencil_texturing" 
 "GL_ANGLE_texture_compression_dxt5" 
 "GL_EXT_blend_color" 
 "GL_ATI_separate_stencil" 
 "GL_EXT_texture_env_dot3" 
 "GL_ARB_viewport_array" 
 "GL_MESA_texture_signed_rgba" 
 "GL_EXT_stencil_wrap" 
 "GL_EXT_texture_shared_exponent" 
 "GL_OES_EGL_image" 
 "GL_EXT_texture_snorm" 
 "GL_3DFX_texture_compression_FXT1" 
 "GL_ARB_texture_storage" 
 "GL_ARB_fragment_layer_viewport" 
 "GL_AMD_seamless_cubemap_per_texture" 
 "GL_IBM_multimode_draw_arrays" 
 "GL_EXT_rescale_normal" 
 "GL_EXT_texture_filter_anisotropic" 
 "GL_ARB_texture_border_clamp" 
 "GL_EXT_gpu_program_parameters" 
 "GL_ARB_texture_compression" 
 "GL_AMD_shader_trinary_minmax" 
 "GL_ARB_shader_image_size" 
 "GL_ARB_compute_shader" 
 "GL_ARB_texture_gather" 
 "GL_EXT_texture_array" 
 "GL_ARB_gpu_shader_fp64" 
 "GL_AMD_vertex_shader_viewport_index" 
 "GL_KHR_texture_compression_astc_ldr" 
 "GL_NV_half_float" 
 "GL_ARB_sample_shading" 
 "GL_ARB_vertex_program" 
 

[Powerdevil] [Bug 454161] Brightness stuck at 30%

2022-06-14 Thread Cor Blom
https://bugs.kde.org/show_bug.cgi?id=454161

Cor Blom  changed:

   What|Removed |Added

 CC||corne...@solcon.nl

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

[Breeze] [Bug 453645] In Zotero scrollbar is too fat or background is not transparant

2022-05-12 Thread Cor Blom
https://bugs.kde.org/show_bug.cgi?id=453645

--- Comment #5 from Cor Blom  ---
Final update: Firefox 78 also shows the thick scrollbars. Zotero is working on
moving to newer firefox and then this should be solved.

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

[Breeze] [Bug 453645] In Zotero scrollbar is too fat or background is not transparant

2022-05-11 Thread Cor Blom
https://bugs.kde.org/show_bug.cgi?id=453645

--- Comment #4 from Cor Blom  ---
Ok, thanks. Reported it downstream:

https://forums.zotero.org/discussion/97116/bug-scrollbars-in-zotero-do-not-work-well-with-upcoming-breeze-gtk-5-25-in-kde-plasma?new=1

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

[Breeze] [Bug 453645] In Zotero scrollbar is too fat or background is not transparant

2022-05-11 Thread Cor Blom
https://bugs.kde.org/show_bug.cgi?id=453645

--- Comment #2 from Cor Blom  ---
Created attachment 148741
  --> https://bugs.kde.org/attachment.cgi?id=148741=edit
Screenshot of whole window

Screenshot as asked. The grey area in the middle is made by me. I don't care
for the world to see my list of books. :)

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

[Breeze] [Bug 453645] New: In Zotero scrollbar is too fat or background is not transparant

2022-05-11 Thread Cor Blom
https://bugs.kde.org/show_bug.cgi?id=453645

Bug ID: 453645
   Summary: In Zotero scrollbar is too fat or background is not
transparant
   Product: Breeze
   Version: master
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: gtk theme
  Assignee: uhh...@gmail.com
  Reporter: corne...@solcon.nl
CC: plasma-b...@kde.org
  Target Milestone: ---

Created attachment 148723
  --> https://bugs.kde.org/attachment.cgi?id=148723=edit
Screenshot of relevant part scrollbar

SUMMARY
***
Installed git version of today, May 11 2022. Everything works fine, except
Zotero. I have download Zotero from zotero.org. I believe it is an application
based on firefox 78. With 5.24 I have good scrollbars, but with the new
scrollbars for 5.25 they are too thick in Zotero. Looking carefulllig I think
there is a non-transparant background behind the slider, giving it a thick
look.
***


SOFTWARE/OS VERSIONS
Linux/KDE Plasma: openSUSE Tumbleweed
(available in About System)
KDE Plasma Version: 5.24.5
KDE Frameworks Version: 5.93
Qt Version: 5.15.2

ADDITIONAL INFORMATION
I have attached a screenshot of the new scrollbar slider

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

[Elisa] [Bug 417964] Artist and Album names are case sensitive

2022-05-03 Thread Cor Blom
https://bugs.kde.org/show_bug.cgi?id=417964

Cor Blom  changed:

   What|Removed |Added

 CC||corne...@solcon.nl

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

[gwenview] [Bug 453207] New: gwenview crashes when removing red eyes

2022-04-29 Thread Cor Blom
https://bugs.kde.org/show_bug.cgi?id=453207

Bug ID: 453207
   Summary: gwenview crashes when removing red eyes
   Product: gwenview
   Version: 21.12.3
  Platform: openSUSE RPMs
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: gwenview-bugs-n...@kde.org
  Reporter: corne...@solcon.nl
  Target Milestone: ---

Application: gwenview (21.12.3)

Qt Version: 5.15.2
Frameworks Version: 5.90.0
Operating System: Linux 5.14.21-150400.19-default x86_64
Windowing System: X11
Distribution: "openSUSE Leap 15.4 Beta"
DrKonqi: 5.24.4 [KCrashBackend]

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

I opened a photo with red eyes, clicked on the red eye remover in the sidebar,
double clicked on the red eye, Then the program crashed.

The crash can be reproduced every time.

-- Backtrace:
Application: Gwenview (gwenview), signal: Segmentation fault

[KCrash Handler]
#4  0x7f2c0b2794e4 in __memmove_evex_unaligned_erms () from
/lib64/libc.so.6
#5  0x7f2c0cf222ce in memcpy (__len=12288, __src=0x7f2bccf25010,
__dest=) at /usr/include/bits/string_fortified.h:34
#6  QImage::copy (this=0x556755ee4d00, r=...) at image/qimage.cpp:1239
#7  0x7f2c10b16412 in Gwenview::RasterImageItem::paint
(this=0x556755c9de20, painter=0x7ffe3c05d020) at
/usr/src/debug/gwenview5-21.12.3-bp154.1.3.x86_64/lib/documentview/rasterimageitem.cpp:106
#8  0x7f2c0db42716 in QGraphicsScenePrivate::draw
(this=this@entry=0x5567556afd30, item=item@entry=0x556755c9de20,
painter=painter@entry=0x7ffe3c05d020, viewTransform=,
transformPtr=transformPtr@entry=0x556755e84250, exposedRegion=,
widget=, opacity=opacity@entry=1, effectTransform=, wasDirtyParentSceneTransform=, drawItem=)
at graphicsview/qgraphicsscene.cpp:4981
#9  0x7f2c0db42efe in QGraphicsScenePrivate::drawSubtreeRecursive
(this=this@entry=0x5567556afd30, item=0x556755c9de20,
painter=painter@entry=0x7ffe3c05d020, viewTransform=viewTransform@entry=0x0,
exposedRegion=exposedRegion@entry=0x5567557bca60, widget=,
widget@entry=0x5567556b0740, parentOpacity=parentOpacity@entry=1,
effectTransform=0x0) at graphicsview/qgraphicsscene.cpp:4873
#10 0x7f2c0db4229c in QGraphicsScenePrivate::draw
(this=this@entry=0x5567556afd30, item=item@entry=0x556755d44080,
painter=painter@entry=0x7ffe3c05d020, viewTransform=,
transformPtr=transformPtr@entry=0x556755a2c590, exposedRegion=,
widget=, opacity=opacity@entry=1, effectTransform=, wasDirtyParentSceneTransform=, drawItem=)
at graphicsview/qgraphicsscene.cpp:5013
#11 0x7f2c0db42efe in QGraphicsScenePrivate::drawSubtreeRecursive
(this=this@entry=0x5567556afd30, item=0x556755d44080,
painter=painter@entry=0x7ffe3c05d020, viewTransform=viewTransform@entry=0x0,
exposedRegion=exposedRegion@entry=0x5567557bca60, widget=,
widget@entry=0x5567556b0740, parentOpacity=parentOpacity@entry=1,
effectTransform=0x0) at graphicsview/qgraphicsscene.cpp:4873
#12 0x7f2c0db4229c in QGraphicsScenePrivate::draw
(this=this@entry=0x5567556afd30, item=, painter=,
viewTransform=, transformPtr=,
exposedRegion=, widget=, opacity=,
effectTransform=, wasDirtyParentSceneTransform=,
drawItem=) at graphicsview/qgraphicsscene.cpp:5013
#13 0x7f2c0db0a8a1 in QGraphicsItemEffectSourcePrivate::draw
(this=0x5567559fa620, painter=0x7ffe3c05d020) at
graphicsview/qgraphicsitem.cpp:11328
#14 0x7f2c0dbaaf35 in QGraphicsEffectSource::draw (this=0x556755e2ccc0,
painter=0x7ffe3c05d020) at effects/qgraphicseffect.cpp:236
#15 0x7f2c0dbab022 in QGraphicsEffect::drawSource (this=,
painter=) at effects/qgraphicseffect.cpp:255
#16 0x7f2c0dbaba45 in QGraphicsOpacityEffect::draw (this=0x556755d82b80,
painter=0x7ffe3c05d020) at effects/qgraphicseffect.cpp:1199
#17 0x7f2c0db42ea6 in QGraphicsScenePrivate::drawSubtreeRecursive
(this=this@entry=0x5567556afd30, item=0x556755cbb0c0,
painter=painter@entry=0x7ffe3c05d020, viewTransform=viewTransform@entry=0x0,
exposedRegion=exposedRegion@entry=0x5567557bca60, widget=,
widget@entry=0x5567556b0740, parentOpacity=parentOpacity@entry=1,
effectTransform=0x0) at graphicsview/qgraphicsscene.cpp:4867
#18 0x7f2c0db436aa in QGraphicsScenePrivate::drawItems
(this=this@entry=0x5567556afd30, painter=painter@entry=0x7ffe3c05d020,
viewTransform=viewTransform@entry=0x0,
exposedRegion=exposedRegion@entry=0x5567557bca60, widget=0x5567556b0740) at
graphicsview/qgraphicsscene.cpp:4735
#19 0x7f2c0db68a95 in QGraphicsView::paintEvent (this=0x5567556c3a50,
event=) at graphicsview/qgraphicsview.cpp:3561
#20 0x7f2c0d865ad8 in QWidget::event (this=this@entry=0x5567556c3a50,
event=event@entry=0x7ffe3c05d5f0) at kernel/qwidget.cpp:9020
#21 0x7f2c0d90ca5e in QFrame::event (this=0x5567556c3a50, e=0x7ffe3c05d5f0)
at widgets/qframe.cpp:550
#22 0x7f2c0db67633 in QGraphicsView::viewportEvent (this=0x5567556c3a50,
event=0x7ffe3c05d5f0) 

[systemsettings] [Bug 441668] Please make middle-click pasting optional

2021-12-03 Thread Cor Blom
https://bugs.kde.org/show_bug.cgi?id=441668

Cor Blom  changed:

   What|Removed |Added

 CC||corne...@solcon.nl

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

[Akonadi] [Bug 421664] Sending email does not work with XOAUTH2

2021-11-09 Thread Cor Blom
https://bugs.kde.org/show_bug.cgi?id=421664

Cor Blom  changed:

   What|Removed |Added

 CC||corne...@solcon.nl

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

[plasmashell] [Bug 444602] LyX menu stops opening after a while

2021-10-29 Thread Cor Blom
https://bugs.kde.org/show_bug.cgi?id=444602

Cor Blom  changed:

   What|Removed |Added

 CC||corne...@solcon.nl

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

[plasmashell] [Bug 438565] Mute audio icon appear on all pinned but not running icons when using Pipewire

2021-10-13 Thread Cor Blom
https://bugs.kde.org/show_bug.cgi?id=438565

Cor Blom  changed:

   What|Removed |Added

 CC||corne...@solcon.nl

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

[ksysguard] [Bug 436566] New: Unable to close unused tabs

2021-05-03 Thread cor
https://bugs.kde.org/show_bug.cgi?id=436566

Bug ID: 436566
   Summary: Unable to close unused tabs
   Product: ksysguard
   Version: 5.18.4
  Platform: Ubuntu Packages
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: ksysguard
  Assignee: ksysguard-b...@kde.org
  Reporter: corcaig...@zohomail.com
CC: plasma-b...@kde.org
  Target Milestone: ---

SUMMARY


STEPS TO REPRODUCE
1. Open ksysguard
2. Enabled "Close" in toolbar
3. 

OBSERVED RESULT
No change to toolbar and unable to close any tabs.

EXPECTED RESULT
Ability to close tabs

SOFTWARE/OS VERSIONS
Operating System: Kubuntu 20.04
KDE Plasma Version: 5.18.5
KDE Frameworks Version: 5.68.0
Qt Version: 5.12.8
Kernel Version: 5.8.0-50-generic
OS Type: 64-bit
Processors: 4 × AMD Ryzen 3 2200G with Radeon Vega Graphics
Memory: 29.4 GiB of RAM


ADDITIONAL INFORMATION

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

[Active Window Control] [Bug 404359] Application menu does not show

2020-10-12 Thread Cor Blom
https://bugs.kde.org/show_bug.cgi?id=404359

--- Comment #13 from Cor Blom  ---
This software is abandoned. Should we not close this as will not be fixed. It
has been removed from openSUSE.

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

[plasma-integration] [Bug 397322] In some cases fake italic is used instead of real

2020-09-30 Thread Cor Blom
https://bugs.kde.org/show_bug.cgi?id=397322

--- Comment #1 from Cor Blom  ---
On openSUSE Leap 15.2 I do not see this anymore. Did some testing and could not
find a font that used fake italics.

I assume this means this bug can be closed.

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

[systemsettings] [Bug 421329] New Global Shortcuts KCM: shortcuts to launch 3rd-party apps don't work

2020-07-24 Thread cor
https://bugs.kde.org/show_bug.cgi?id=421329

--- Comment #28 from cor  ---
The suggestion to add kglobalaccel directory made no difference at all. Please
address this issue. It is hard to believe that it was allowed to get through in
the first place. Something that has worked flawlessly for years has suddenly
stopped functioning. It almost seems deliberate. I report problems to you
people and you do nothing but look for someone else to blame. FIX THE ISSUE! IT
IS REAL! As I stated this is a fresh install. Brand new and broken.

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

[systemsettings] [Bug 421329] New Global Shortcuts KCM: shortcuts to launch 3rd-party apps don't work

2020-07-24 Thread cor
https://bugs.kde.org/show_bug.cgi?id=421329

cor  changed:

   What|Removed |Added

 CC||corcaig...@linuxmail.org

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

[kxkb] [Bug 424576] New: Custom keyboard shortcuts are not working

2020-07-23 Thread cor
https://bugs.kde.org/show_bug.cgi?id=424576

Bug ID: 424576
   Summary: Custom keyboard shortcuts are not working
   Product: kxkb
   Version: unspecified
  Platform: Neon Packages
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: unassigned-b...@kde.org
  Reporter: corcaig...@linuxmail.org
  Target Milestone: ---

SUMMARY


STEPS TO REPRODUCE
1. Set "F12" to open Konsole
2. Save
3. Tried other apps as well, like changing "Ctrl+Esc" to open Ksysguard

OBSERVED RESULT
None of my settings for custom keys are working. This is a fresh neon install.

EXPECTED RESULT
Shortcut keys to open apps.

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

ADDITIONAL INFORMATION
Operating System: KDE neon 5.19
KDE Plasma Version: 5.19.3
KDE Frameworks Version: 5.72.0
Qt Version: 5.14.2
Kernel Version: 5.4.0-42-generic
OS Type: 64-bit
Processors: 4 × AMD Ryzen 3 2200G with Radeon Vega Graphics
Memory: 29.4 GiB of RAM
Graphics Processor: AMD RAVEN

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

[kwin] [Bug 342326] window contents freeze

2020-06-01 Thread cor
https://bugs.kde.org/show_bug.cgi?id=342326

--- Comment #36 from cor  ---
And it's impossible to report something that happens at random!

On 6/1/20 3:18 AM, Vlad Zahorodnii wrote:
> https://bugs.kde.org/show_bug.cgi?id=342326
>
> --- Comment #35 from Vlad Zahorodnii  ---
>> Please fix this MAJOR FLAW!
> It's pretty difficult to fix a bug if one can't reproduce it.
>

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

[kdeconnect] [Bug 357051] KDE Connect fails to detect my PC and my PC fails to detect my Android 6.0 Phone.

2020-05-30 Thread cor
https://bugs.kde.org/show_bug.cgi?id=357051

cor  changed:

   What|Removed |Added

 CC||corcaig...@linuxmail.org

--- Comment #7 from cor  ---
Worked for a time then after an update, it just stopped. No error messages. No
way of knowing what the problem may be. Entered IP address and Hostname of PC
on my local network, nothing changes. Complete removal and reinstallation do
nothing. I question why this even exists outside of beta testing.

AMD Ryzen3 2200g
16GB RAM
7 TB storage
Kubuntu 18.04

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

[kwin] [Bug 342326] window contents freeze

2020-05-29 Thread cor
https://bugs.kde.org/show_bug.cgi?id=342326

cor  changed:

   What|Removed |Added

   Platform|Other   |Ubuntu Packages
Version|5.1.2   |5.12.8
 CC||corcaig...@linuxmail.org

--- Comment #34 from cor  ---
This issue with the compositor has been going on for YEARS! Is this beyond
everyone's grasp? It would be most helpful and logical to get to the root of
this problem. It can cause unrecoverable disk errors. I have had to re-install
my OS several times directly as a result of this bug. I see people reporting
this and being told to try changing the rendering backend, but that is not a
solution. And then the issue is closed as if it is resolved. It has not been
resolved. Please fix this MAJOR FLAW! A lot of blame is being laid on the intel
driver...guess what? I don't have an intel anything in my desktop pc. It is all
AMD.

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

[systemsettings] [Bug 412346] Personal settings not being saved

2019-10-11 Thread cor
https://bugs.kde.org/show_bug.cgi?id=412346

--- Comment #5 from cor  ---
You provide no way to indicate I want this closed. I am no longer using Linux
Mint.

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

[systemsettings] [Bug 412346] Personal settings not being saved

2019-09-26 Thread cor
https://bugs.kde.org/show_bug.cgi?id=412346

--- Comment #3 from cor  ---
Created attachment 122887
  --> https://bugs.kde.org/attachment.cgi?id=122887=edit
after edit

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

[systemsettings] [Bug 412346] Personal settings not being saved

2019-09-26 Thread cor
https://bugs.kde.org/show_bug.cgi?id=412346

--- Comment #2 from cor  ---
Created attachment 122886
  --> https://bugs.kde.org/attachment.cgi?id=122886=edit
before editing

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

[systemsettings] [Bug 412346] New: Personal settings not being saved

2019-09-25 Thread cor
https://bugs.kde.org/show_bug.cgi?id=412346

Bug ID: 412346
   Summary: Personal settings not being saved
   Product: systemsettings
   Version: 5.8.9
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: corcaig...@linuxmail.org
  Target Milestone: ---

SUMMARY
I have repeatedly cleared history and turned off all Plasma Search plugins
and
changed the sort order of the Folder Widget. The settings are not being saved.
When I return to SystemSettings Search it is back to default and nothing has
been removed from history. The sort order of the Folders make no sense
whatsoever.

STEPS TO REPRODUCE
1. Clear search history
2. Un-check all search plug-ins
3. Save

OBSERVED RESULT
Nothing is changing.

EXPECTED RESULT
Cleared history and properly sorted folders from the plasma folder widget.

SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: LinuxMint 18.3 64Bit
(available in About System)
KDE Plasma Version: 5.8.9
KDE Frameworks Version: 5.36.0
Qt Version: 5.6.1

ADDITIONAL INFORMATION

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

[Active Window Control] [Bug 404359] Application menu does not show

2019-06-27 Thread Cor Blom
https://bugs.kde.org/show_bug.cgi?id=404359

--- Comment #7 from Cor Blom  ---
You should also try Plasma's own applet for application menu, to see if it is a
general problem with the appmenu.

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

[Active Window Control] [Bug 404359] Application menu does not show

2019-06-27 Thread Cor Blom
https://bugs.kde.org/show_bug.cgi?id=404359

--- Comment #6 from Cor Blom  ---
(In reply to john from comment #5)
> Any clue or idea how to fix it / maybe reset the plasmoid...

Removing the plasmoid from the panel and adding it again resets it for me.

You can also try a new account with empty kde setting to see if something has
messed up your settings.

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

[Active Window Control] [Bug 404359] Application menu does not show

2019-06-27 Thread Cor Blom
https://bugs.kde.org/show_bug.cgi?id=404359

--- Comment #4 from Cor Blom  ---
It has moved to the kde infrastructure, nothing more as far as I know. SeeL

https://phabricator.kde.org/source/plasma-active-window-control/

Tumbleweed has the latest git version with two additional patches and for me it
is working fine. I am the maintainer of that package in openSUSE. I cannot
reproduce this.

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

[Active Window Control] [Bug 404359] Application menu does not show

2019-06-26 Thread Cor Blom
https://bugs.kde.org/show_bug.cgi?id=404359

Cor Blom  changed:

   What|Removed |Added

 CC||corne...@solcon.nl

--- Comment #2 from Cor Blom  ---
The active window control applet is part of openSUSE Tumbleweed and you should
install from there, not from store.kde.org. It needs to be compiled to have all
functions. When you use the version from the Tumbleweed repo, all should work
fine.

(Of course, this applet does not seems to be developed anymore, so it is
available until it breaks.)

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

[plasmashell] [Bug 407555] Starting X-Server with 2nd monitor throws panel menus half way up the screen.

2019-05-30 Thread Cor
https://bugs.kde.org/show_bug.cgi?id=407555

Cor  changed:

   What|Removed |Added

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

--- Comment #4 from Cor  ---
See comment.

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

[plasmashell] [Bug 407555] Starting X-Server with 2nd monitor throws panel menus half way up the screen.

2019-05-30 Thread Cor
https://bugs.kde.org/show_bug.cgi?id=407555

--- Comment #3 from Cor  ---
Created attachment 120410
  --> https://bugs.kde.org/attachment.cgi?id=120410=edit
env.out,qtdiag.out,xrandr.out

Okay, I set my system for graphical login. It happens rarely now but still does
happen occasionally. Rather than half way up the screen, the menu pops up from
the second display (where the menu itself is on the primary display), making it
difficult to navigate to.

Again, re-inserting the HDMI cable fixes the issue.

Attached are the files you requested.

As using a graphical login definitely has a big impact, could you give me a
clue as to how I might fix this for regular logins? I don't want to use a
graphical login, nomatter how forking cool it is.

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

[plasmashell] [Bug 407555] Starting X-Server with 2nd monitor throws panel menus half way up the screen.

2019-05-15 Thread Cor
https://bugs.kde.org/show_bug.cgi?id=407555

Cor  changed:

   What|Removed |Added

 CC||kde-b...@corz.org

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

[plasmashell] [Bug 407555] New: Starting X-Server with 2nd monitor throws panel menus half way up the screen.

2019-05-15 Thread Cor
https://bugs.kde.org/show_bug.cgi?id=407555

Bug ID: 407555
   Summary: Starting X-Server with 2nd monitor throws panel menus
half way up the screen.
   Product: plasmashell
   Version: master
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Panel
  Assignee: plasma-b...@kde.org
  Reporter: kde-b...@corz.org
  Target Milestone: 1.0

Created attachment 120080
  --> https://bugs.kde.org/attachment.cgi?id=120080=edit
Screen Capture doesn't capture the panel!

SUMMARY


STEPS TO REPRODUCE
1. Attach second monitor (MiniDP > NEC HDMI Display). 
2. Bootup, login, startx
3. Activate panel's application Application Launcher (Click or Meta or
whatever).

OBSERVED RESULT

The panel pops up from half way up the screen,instead of the bottom (where the
panel is). Underneath it is a large empty gap. Only a small part (the top) of
the panel is visible. This affects many other menus that popup, e.g. context
menus for System Tray items.

I tried taking a screenshot, but the panel is not captured. Excuse my dodgy
photo of the main (laptop) screen.

If I unplug the second monitor and plug it back in again, everything works
fine, as if "reset".


EXPECTED RESULT

The bottom of the Application Launcher begins where the panel ends!


SOFTWARE/OS VERSIONS

Linux/KDE Plasma: Slackware -current
KDE Plasma Version: 5.15.5
KDE Frameworks Version: 5.58.0
Qt Version: 5.12.3

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

[kdialog] [Bug 397689] "Select icon" dialog can't get focus when changing icon from kdialog file picker

2019-05-15 Thread Cor
https://bugs.kde.org/show_bug.cgi?id=397689

Cor  changed:

   What|Removed |Added

 CC||kde-b...@corz.org

--- Comment #5 from Cor  ---
I'm still seeing this issue with Chromium.

Linux/KDE Plasma: Slackware -current
KDE Plasma Version: 5.15.5
KDE Frameworks Version: 5.58.0
Qt Version: 5.12.3

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

[plasmashell] [Bug 399975] LyX does not work well with global menu

2018-11-24 Thread Cor Blom
https://bugs.kde.org/show_bug.cgi?id=399975

--- Comment #3 from Cor Blom  ---
Thanks for fixing this.

Can the fix also be applied to the Active Window Control applet? It has the
same code.

Maybe this is not the right place to ask, but I do not know how else to do
this.

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

[plasmashell] [Bug 399975] New: LyX does not work well with global menu

2018-10-18 Thread Cor Blom
https://bugs.kde.org/show_bug.cgi?id=399975

Bug ID: 399975
   Summary: LyX does not work well with global menu
   Product: plasmashell
   Version: 5.14.0
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Global Menu
  Assignee: k...@privat.broulik.de
  Reporter: corne...@solcon.nl
CC: plasma-b...@kde.org
  Target Milestone: 1.0

SUMMARY
The bugreport as the side of LyX can be found here:

https://www.lyx.org/trac/ticket/11130

The global menu is working somewhat with the active window plasmoid, but with
the the global menu of plasma itself it is not working. The menu shows, but
does not open (or opens so fast that it is hardly seen).

In the bugreport from Lyx one of the developpers offered to explain how Lyx's
menus work. Maybe a solution can be found?



SOFTWARE VERSIONS
(available in About System)
KDE Plasma Version: 5.41.0
KDE Frameworks Version: 5.50
Qt Version: 5.11.2

ADDITIONAL INFORMATION

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

[KBibTeX] [Bug 398136] kbibtex crashes when editing element

2018-09-11 Thread Cor Blom
https://bugs.kde.org/show_bug.cgi?id=398136

--- Comment #3 from Cor Blom  ---
After applying the patch kbibtex works fine and does not crash.

Thanks.

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

[KBibTeX] [Bug 398136] New: kbibtex crashes when editing element

2018-09-01 Thread Cor Blom
https://bugs.kde.org/show_bug.cgi?id=398136

Bug ID: 398136
   Summary: kbibtex crashes when editing element
   Product: KBibTeX
   Version: 0.8.1
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: General
  Assignee: fisc...@unix-ag.uni-kl.de
  Reporter: corne...@solcon.nl
  Target Milestone: ---

Application: kbibtex (0.8.1)

Qt Version: 5.9.4
Frameworks Version: 5.45.0
Operating System: Linux 4.12.14-lp150.12.16-default x86_64
Distribution: "openSUSE Leap 15.0"

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

I open an element to edit. In the editing window, when I click on a following
tab, the program disappears. I get this with both webkit and webengine (but
only webkit the option to report this bug in plasma).

The crash can be reproduced every time.

-- Backtrace:
Application: KBibTeX (kbibtex), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fad87b7ae80 (LWP 771))]

Thread 4 (Thread 0x7fad62f16700 (LWP 775)):
#0  0x7fad81fed08b in poll () from /lib64/libc.so.6
#1  0x7fad78bf0109 in ?? () from /usr/lib64/libglib-2.0.so.0
#2  0x7fad78bf021c in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#3  0x7fad8291bc0b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib64/libQt5Core.so.5
#4  0x7fad828c409a in
QEventLoop::exec(QFlags) () from
/usr/lib64/libQt5Core.so.5
#5  0x7fad826f34da in QThread::exec() () from /usr/lib64/libQt5Core.so.5
#6  0x7fad809af985 in ?? () from /usr/lib64/libQt5DBus.so.5
#7  0x7fad826f80ce in ?? () from /usr/lib64/libQt5Core.so.5
#8  0x7fad7a114559 in start_thread () from /lib64/libpthread.so.0
#9  0x7fad81ff782f in clone () from /lib64/libc.so.6

Thread 3 (Thread 0x7fad66fff700 (LWP 774)):
#0  0x7fad81fed08b in poll () from /lib64/libc.so.6
#1  0x7fad78986387 in ?? () from /usr/lib64/libxcb.so.1
#2  0x7fad78987faa in xcb_wait_for_event () from /usr/lib64/libxcb.so.1
#3  0x7fad69738029 in ?? () from /usr/lib64/libQt5XcbQpa.so.5
#4  0x7fad826f80ce in ?? () from /usr/lib64/libQt5Core.so.5
#5  0x7fad7a114559 in start_thread () from /lib64/libpthread.so.0
#6  0x7fad81ff782f in clone () from /lib64/libc.so.6

Thread 2 (Thread 0x7fad6a707700 (LWP 773)):
#0  0x7fad7a11a89d in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7fad8237570c in
std::condition_variable::wait(std::unique_lock&) () from
/usr/lib64/libstdc++.so.6
#2  0x7fad7f6eb657 in ?? () from /usr/lib64/libQt5WebKit.so.5
#3  0x7fad7f6eb799 in ?? () from /usr/lib64/libQt5WebKit.so.5
#4  0x7fad8237b40f in ?? () from /usr/lib64/libstdc++.so.6
#5  0x7fad7a114559 in start_thread () from /lib64/libpthread.so.0
#6  0x7fad81ff782f in clone () from /lib64/libc.so.6

Thread 1 (Thread 0x7fad87b7ae80 (LWP 771)):
[KCrash Handler]
#6  0x7fad82770086 in operator<(QString const&, QString const&) () from
/usr/lib64/libQt5Core.so.5
#7  0x7fad858a20f0 in qMapLessThanKey (key2=..., key1=...) at
/usr/include/qt5/QtCore/qmap.h:71
#8  QMapNode::lowerBound (akey=..., this=) at
/usr/include/qt5/QtCore/qmap.h:155
#9  QMapData::findNode (this=, akey=...) at
/usr/include/qt5/QtCore/qmap.h:287
#10 0x7fad858a2a8d in QMap::remove
(this=this@entry=0x55f6795e0f50, akey=...) at
/usr/include/qt5/QtCore/qmap.h:937
#11 0x7fad858a0d5b in Entry::remove (this=0x55f6795e0f40, key=...) at
/usr/src/debug/kbibtex-0.8.1-lp150.8.1.x86_64/src/data/entry.cpp:174
#12 0x7fad87542c2d in EntryConfiguredWidget::apply (this=0x55f678f34b90,
element=...) at
/usr/src/debug/kbibtex-0.8.1-lp150.8.1.x86_64/src/gui/element/elementwidgets.cpp:111
#13 0x7fad87533a3f in ElementEditor::ElementEditorPrivate::switchTo
(futureTab=0x55f67928d450, this=0x55f678feb410) at
/usr/src/debug/kbibtex-0.8.1-lp150.8.1.x86_64/src/gui/element/elementeditor.cpp:422
#14 ElementEditor::tabChanged (this=) at
/usr/src/debug/kbibtex-0.8.1-lp150.8.1.x86_64/src/gui/element/elementeditor.cpp:591
#15 0x7fad828f314c in QMetaObject::activate(QObject*, int, int, void**) ()
from /usr/lib64/libQt5Core.so.5
#16 0x7fad8380f67e in QTabWidget::currentChanged(int) () from
/usr/lib64/libQt5Widgets.so.5
#17 0x7fad8381175f in ?? () from /usr/lib64/libQt5Widgets.so.5
#18 0x7fad828f304a in QMetaObject::activate(QObject*, int, int, void**) ()
from /usr/lib64/libQt5Core.so.5
#19 0x7fad837f29ee in QTabBar::currentChanged(int) () from
/usr/lib64/libQt5Widgets.so.5
#20 0x7fad837f6ee7 in QTabBar::setCurrentIndex(int) () from
/usr/lib64/libQt5Widgets.so.5
#21 0x7fad837f93f5 in QTabBar::mousePressEvent(QMouseEvent*) () from
/usr/lib64/libQt5Widgets.so.5
#22 0x7fad836926f9 in QWidget::event(QEvent*) () from
/usr/lib64/libQt5Widgets.so.5
#23 

[plasma-integration] [Bug 397322] New: In some cases fake italic is used instead of real

2018-08-09 Thread Cor Blom
https://bugs.kde.org/show_bug.cgi?id=397322

Bug ID: 397322
   Summary: In some cases fake italic is used instead of real
   Product: plasma-integration
   Version: 5.12.5
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: corne...@solcon.nl
  Target Milestone: ---

I saw this first in Lyx (see https://www.lyx.org/trac/ticket/11233), but
discovers this happens in other Qt apps and only under Plasma. Under IceWM it
was working correctly.

If in the properties of a font the truetype name is set to "Book" real italic
is used (e.g Times New Roman), if it is set to "Regular" fake italics is used
(e.g. Tinos).

I have seen this in lyx, sigil, calligra words.

This is only happening in workspace area, In the UI italic is working correclty
(in systemsettings > fonts > fonts). It is also working correctly in kate.

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

[plasmashell] [Bug 391868] Incorrect Libre Office first topmenu item when office file launched directly

2018-04-17 Thread Cor Blom
https://bugs.kde.org/show_bug.cgi?id=391868

Cor Blom <corne...@solcon.nl> changed:

   What|Removed |Added

 CC||corne...@solcon.nl

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

[plasmashell] [Bug 342763] Crash In Task Manager Item Changed

2016-12-07 Thread Cor Blom
https://bugs.kde.org/show_bug.cgi?id=342763

Cor Blom <corne...@solcon.nl> changed:

   What|Removed |Added

 CC|corne...@solcon.nl  |

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

[plasmashell] [Bug 364698] New: Psalma crashed after closing dolphin window

2016-06-24 Thread Cor Blom via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=364698

Bug ID: 364698
   Summary: Psalma crashed after closing dolphin window
   Product: plasmashell
   Version: 5.5.5
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: corne...@solcon.nl
CC: bhus...@gmail.com, plasma-b...@kde.org

Application: plasmashell (5.5.5)

Qt Version: 5.5.1
Operating System: Linux 4.1.26-21-default x86_64
Distribution: "openSUSE Leap 42.1 (x86_64)"

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

I closed a dolphin window (maybe last window?). It is happening more often,
although I don't if it is always.

The crash can be reproduced sometimes.

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

Thread 18 (Thread 0x7f7d6561e700 (LWP 1567)):
#0  0x7f7d741a3bbd in poll () at /lib64/libc.so.6
#1  0x7f7d790f7422 in  () at /usr/lib64/libxcb.so.1
#2  0x7f7d790f900f in xcb_wait_for_event () at /usr/lib64/libxcb.so.1
#3  0x7f7d67da13c9 in  () at /usr/lib64/libQt5XcbQpa.so.5
#4  0x7f7d7489e32f in  () at /usr/lib64/libQt5Core.so.5
#5  0x7f7d739ad0a4 in start_thread () at /lib64/libpthread.so.0
#6  0x7f7d741abfed in clone () at /lib64/libc.so.6

Thread 17 (Thread 0x7f7d5e424700 (LWP 1610)):
#0  0x7f7d741b85bf in __libc_enable_asynccancel () at /lib64/libc.so.6
#1  0x7f7d741a3bb2 in poll () at /lib64/libc.so.6
#2  0x7f7d70880e64 in  () at /usr/lib64/libglib-2.0.so.0
#3  0x7f7d70880f7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#4  0x7f7d74ad0d8b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#5  0x7f7d74a77d53 in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#6  0x7f7d7489961a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#7  0x7f7d77bade18 in  () at /usr/lib64/libQt5Qml.so.5
#8  0x7f7d7489e32f in  () at /usr/lib64/libQt5Core.so.5
#9  0x7f7d739ad0a4 in start_thread () at /lib64/libpthread.so.0
#10 0x7f7d741abfed in clone () at /lib64/libc.so.6

Thread 16 (Thread 0x7f7d4fb5c700 (LWP 1624)):
#0  0x7f7d74ad0af1 in  () at /usr/lib64/libQt5Core.so.5
#1  0x7f7d708804ad in g_main_context_prepare () at
/usr/lib64/libglib-2.0.so.0
#2  0x7f7d70880d80 in  () at /usr/lib64/libglib-2.0.so.0
#3  0x7f7d70880f7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#4  0x7f7d74ad0d8b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#5  0x7f7d74a77d53 in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#6  0x7f7d7489961a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#7  0x7f7d77bade18 in  () at /usr/lib64/libQt5Qml.so.5
#8  0x7f7d7489e32f in  () at /usr/lib64/libQt5Core.so.5
#9  0x7f7d739ad0a4 in start_thread () at /lib64/libpthread.so.0
#10 0x7f7d741abfed in clone () at /lib64/libc.so.6

Thread 15 (Thread 0x7f7d4e26a700 (LWP 1625)):
#0  0x7f7d741a3bbd in poll () at /lib64/libc.so.6
#1  0x7f7d70880e64 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7f7d70880f7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#3  0x7f7d74ad0d8b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#4  0x7f7d74a77d53 in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#5  0x7f7d7489961a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#6  0x7f7d77bade18 in  () at /usr/lib64/libQt5Qml.so.5
#7  0x7f7d7489e32f in  () at /usr/lib64/libQt5Core.so.5
#8  0x7f7d739ad0a4 in start_thread () at /lib64/libpthread.so.0
#9  0x7f7d741abfed in clone () at /lib64/libc.so.6

Thread 14 (Thread 0x7f7d4c8f5700 (LWP 1633)):
#0  0x7f7d739b103f in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f7d7a37c86b in  () at /usr/lib64/libQt5Script.so.5
#2  0x7f7d7a37c899 in  () at /usr/lib64/libQt5Script.so.5
#3  0x7f7d739ad0a4 in start_thread () at /lib64/libpthread.so.0
#4  0x7f7d741abfed in clone () at /lib64/libc.so.6

Thread 13 (Thread 0x7f7d45235700 (LWP 1670)):
#0  0x7ffdbffdcb26 in clock_gettime ()
#1  0x7f7d741b8c3d in clock_gettime () at /lib64/libc.so.6
#2  0x7f7d7494f7d6 in  () at /usr/lib64/libQt5Core.so.5
#3  0x7f7d74acf3b9 in QTimerInfoList::updateCurrentTime() () at
/usr/lib64/libQt5Core.so.5
#4  0x7f7d74acf945 in QTimerInfoList::timerWait(timespec&) () at
/usr/lib64/libQt5Core.so.5
#5  0x7f7d74ad0b5e in  () at /usr/lib64/libQt5Core.so.5
#6  0x7f7d708804ad in g_main_context_prepare () at
/usr/lib64/libglib-2.0.so.0
#7  0x7f7d70880d80 in  () at /usr/lib64/libglib-2.0.so.0
#8  

[systemsettings] [Bug 336089] Font preview - rendering problem

2016-01-09 Thread Cor Blom via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=336089

--- Comment #45 from Cor Blom <corne...@solcon.nl> ---
(In reply to Thomas Lübking from comment #43)
> Resp. this one (the ARGB32 translucency handling is uncritical, it's applied
> to the preconverted image. This should be the single point of failure)
> 
> diff --git a/kcms/kfontinst/lib/FcEngine.cpp
> b/kcms/kfontinst/lib/FcEngine.cpp
> index 19b7206..012a9d5 100644
> --- a/kcms/kfontinst/lib/FcEngine.cpp
> +++ b/kcms/kfontinst/lib/FcEngine.cpp
> @@ -537,7 +537,14 @@ QImage CFcEngine::Xft::toImage(int w, int h) const
>  if (!xImage) {
>  return QImage();
>  }
> -return QImage(xImage->data, xImage->width, xImage->height,
> xImage->stride, QImage::Format_ARGB32_Premultiplied, , xImage);
> +QImage::Format format = QImage::Format_RGB32;
> +switch (DefaultDepth(QX11Info::display(), 0)) {
> +case 32: format = QImage::Format_ARGB32_Premultiplied; break;
> +case 16: format = QImage::Format_RGB16; break;
> +case 8: format = QImage::Format_Grayscale8; break;
> +default: break;
> +}
> +return QImage(xImage->data, xImage->width, xImage->height,
> xImage->stride, format, , xImage);
>  }
>  
>  inline int point2Pixel(int point)

This patch solved the bug on openSUSE Leap 42.1 and nouveau (a NVD9 card)

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