[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.

[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.

[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.

[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 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.