[plasmashell] [Bug 370023] New: plasmashell crash when attempting to use search bar

[Marcus Harrison via KDE Bugzilla]

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

Bug ID: 370023
   Summary: plasmashell crash when attempting to use search bar
   Product: plasmashell
   Version: 5.7.5
  Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: mar...@harrisonland.co.uk
CC: bhus...@gmail.com, plasma-b...@kde.org

Application: plasmashell (5.7.5)

Qt Version: 5.6.1
Frameworks Version: 5.26.0
Operating System: Linux 4.7.5-200.fc24.x86_64 x86_64
Distribution (Platform): Fedora RPMs

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

I had opened the default application launcher menu and typed a search term into
the search bar. After the list of favourite options had disappeared, and before
the list of results appeared, plasmashell crashed.

While the symptoms are similar to another crash report I filed in the Red Hat
bugzilla at https://bugzilla.redhat.com/show_bug.cgi?id=1273609#c21, I now have
Baloo enabled and plasmashell crashes are considerably less frequent. Finally,
I am using a more up-to-date version of Fedora and plasmashell than I was when
I reported that bug. Having checked this backtrace, it doesn't seem that the
two bugs are related, but I am including that report here for completeness.

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

Thread 17 (Thread 0x7f871affd700 (LWP 2549)):
#0  0x7f8800f21bd0 in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f88027d801a in QWaitCondition::wait(QMutex*, unsigned long) () at
/lib64/libQt5Core.so.5
#2  0x7f87418cd8c0 in
ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*,
bool, bool, bool) () at /lib64/libKF5ThreadWeaver.so.5
#3  0x7f87418d1a68 in
ThreadWeaver::WorkingHardState::applyForWork(ThreadWeaver::Thread*, bool) () at
/lib64/libKF5ThreadWeaver.so.5
#4  0x7f87418cca3d in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/lib64/libKF5ThreadWeaver.so.5
#5  0x7f87418cf909 in ThreadWeaver::Thread::run() () at
/lib64/libKF5ThreadWeaver.so.5
#6  0x7f88027d799a in QThreadPrivate::start(void*) () at
/lib64/libQt5Core.so.5
#7  0x7f8800f1c5ca in start_thread () at /lib64/libpthread.so.0
#8  0x7f8801bcaf6d in clone () at /lib64/libc.so.6

Thread 16 (Thread 0x7f871b7fe700 (LWP 2548)):
#0  0x7f8800f21bd0 in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f88027d801a in QWaitCondition::wait(QMutex*, unsigned long) () at
/lib64/libQt5Core.so.5
#2  0x7f87418cd8c0 in
ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*,
bool, bool, bool) () at /lib64/libKF5ThreadWeaver.so.5
#3  0x7f87418d1a68 in
ThreadWeaver::WorkingHardState::applyForWork(ThreadWeaver::Thread*, bool) () at
/lib64/libKF5ThreadWeaver.so.5
#4  0x7f87418cca3d in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/lib64/libKF5ThreadWeaver.so.5
#5  0x7f87418cf909 in ThreadWeaver::Thread::run() () at
/lib64/libKF5ThreadWeaver.so.5
#6  0x7f88027d799a in QThreadPrivate::start(void*) () at
/lib64/libQt5Core.so.5
#7  0x7f8800f1c5ca in start_thread () at /lib64/libpthread.so.0
#8  0x7f8801bcaf6d in clone () at /lib64/libc.so.6

Thread 15 (Thread 0x7f871bfff700 (LWP 2547)):
#0  0x7f8800f21bd0 in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f88027d801a in QWaitCondition::wait(QMutex*, unsigned long) () at
/lib64/libQt5Core.so.5
#2  0x7f87418cd8c0 in
ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*,
bool, bool, bool) () at /lib64/libKF5ThreadWeaver.so.5
#3  0x7f87418d1a68 in
ThreadWeaver::WorkingHardState::applyForWork(ThreadWeaver::Thread*, bool) () at
/lib64/libKF5ThreadWeaver.so.5
#4  0x7f87418cca3d in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/lib64/libKF5ThreadWeaver.so.5
#5  0x7f87418cf909 in ThreadWeaver::Thread::run() () at
/lib64/libKF5ThreadWeaver.so.5
#6  0x7f88027d799a in QThreadPrivate::start(void*) () at
/lib64/libQt5Core.so.5
#7  0x7f8800f1c5ca in start_thread () at /lib64/libpthread.so.0
#8  0x7f8801bcaf6d in clone () at /lib64/libc.so.6

Thread 14 (Thread 0x7f8720d89700 (LWP 2546)):
#0  0x7f8800f21bd0 in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f88027d801a in QWaitCondition::wait(QMutex*, unsigned long) () at
/lib64/libQt5Core.so.5
#2  0x7f87418cd8c0 in
ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*,
bool, bool, bool) () at /lib64/libKF5ThreadWeaver.so.5
#3  0x7f87418d1a68 in

[kmail2] [Bug 304525] Auto-suggesting contacts from address book using nicknames fails for first search

[Marcus Harrison via KDE Bugzilla]

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

--- Comment #2 from Marcus Harrison  ---
I have just tested this in KMail 4.14.10 from Fedora RPM packages.
Auto-completion still appears to only search the "Name" and "E-mail" fields
recorded in KAddressBook, and not the "Nickname" field.

I'll investigate building or otherwise installing a Frameworks-based version of
KMail.

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

[plasmashell] [Bug 367831] New: chinese word render error

[TOM Harrison via KDE Bugzilla]

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

Bug ID: 367831
   Summary: chinese word render error
   Product: plasmashell
   Version: 5.6.5
  Platform: Kubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: major
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: l12...@yahoo.com.tw
CC: bhus...@gmail.com, plasma-b...@kde.org

all the font about chinese in kde5 all render weird in mono font.

there are some screenshot for sample.
All the font rather in konsole or kate, as soon as I using mono font. the
chinese font will always like this. 

http://i.imgur.com/lVCdRJV.png
http://i.imgur.com/Rcy2ImQ.png

Reproducible: Always

Steps to Reproduce:
1. Always
2.
3.

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

[plasmashell] [Bug 363395] Plasma shell config dialogue drop-down menus do not honour QWidget colour scheme

[Marcus Harrison via KDE Bugzilla]

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

--- Comment #1 from Marcus Harrison  ---
Created attachment 99130
  --> https://bugs.kde.org/attachment.cgi?id=99130=edit
Example screenshot of the bug

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

[plasmashell] [Bug 363395] New: Plasma shell config dialogue drop-down menus do not honour QWidget colour scheme

[Marcus Harrison via KDE Bugzilla]

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

Bug ID: 363395
   Summary: Plasma shell config dialogue drop-down menus do not
honour QWidget colour scheme
   Product: plasmashell
   Version: 5.5.5
  Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: mar...@harrisonland.co.uk
CC: bhus...@gmail.com, plasma-b...@kde.org

When opening a configuration dialogue for a plasmashell widget, most of the
configuration dialogue honours the currently selected QWidget colour scheme.

However, drop-down menus in these dialogues have a white background and blue
hover-over background, while keeping the colour scheme text colour. This can
make certain dark colour schemes difficult to use with these menus.

Reproducible: Always

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

[phonon-backend-gstreamer] [Bug 334421] amarok will increase the memory usage after long time music switch

[TOM Harrison via KDE Bugzilla]

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

--- Comment #11 from TOM Harrison  ---
by the way, after I update to 4.8.3. it still happened.

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

[phonon-backend-gstreamer] [Bug 334421] amarok will increase the memory usage after long time music switch

[TOM Harrison via KDE Bugzilla]

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

--- Comment #9 from TOM Harrison  ---
ii  phonon-backend-gstreamer:amd64   4:4.7.80-0ubuntu2~ubuntu14.04 
 amd64Phonon GStreamer 1.0.x backend
ii  phonon-backend-gstreamer-common:amd644:4.7.80-0ubuntu2~ubuntu14.04 
 amd64Phonon GStreamer 1.0.x backend icons
ii  phonon-backend-gstreamer1.0  4:4.7.80-0ubuntu2~ubuntu14.04 
 all  transitional package

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

[kwin] [Bug 274931] Windows with no border (decoration) are visible on all activities

[TOM Harrison via KDE Bugzilla]

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

--- Comment #35 from TOM Harrison  ---
I am now kde4 is simply remove the !noborder in if
XD

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

[kwin] [Bug 274931] Windows with no border (decoration) are visible on all activities

[TOM Harrison via KDE Bugzilla]

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

--- Comment #29 from TOM Harrison  ---
could I create a review patch for kde 4 ? I am still using kubuntu 14.04.4.
which is only could use kde 4. 
I just remove the !noborder in "line 204 of kwin/manage.cpp" and seems work.
currently it did not have some other effect.

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

[kwin] [Bug 322975] desktop render will twisted when the opengl application is closed.

[TOM Harrison via KDE Bugzilla]

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

--- Comment #53 from TOM Harrison  ---
I have saw that, the work around in kwin 5.4.0 seems nor work in kwin 4 due to
the function did not exist in kwin 4

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

[dolphin] [Bug 362668] Dolphin crash because Home/.config/katerc NOT writeable

[Harrison via KDE Bugzilla]

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

--- Comment #1 from Harrison  ---
Should Home/.config/katerc User/Group Ownership really be "root"?  Not knowing
any better, I changed  the Permissions for Ownership User to my User Id and the
problem has not reoccurred.  But, beware of suggestions by ignorant users!
=
Also, do I need to do anything special for the other bug I reported?  I could
provide additional information but it would really be helpful if someone could
reproduce the problem under Windows Hyper-V in a different environment.  Thank
you,

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

[dolphin] [Bug 362668] New: Dolphin crash because Home/.config/katerc NOT writeable

[Harrison via KDE Bugzilla]

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

Bug ID: 362668
   Summary: Dolphin crash because Home/.config/katerc NOT
writeable
   Product: dolphin
   Version: 15.12.3
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: dolphin-bugs-n...@kde.org
  Reporter: sainokawara.sisyp...@gmail.com

Application: dolphin (15.12.3)

Qt Version: 5.5.1
Operating System: Linux 4.4.0-21-generic x86_64
Distribution: Ubuntu 16.04 LTS

-- Information about the crash:
- What I was doing when the application crashed:
Attempting to view Home/.config/krfbrc .  Whatever the problem is, it is not
confined to just this case.  I am encountering this problem in many similar
situations.  I was not running as SuperUser when this occurred.

The crash can be reproduced every time.

-- Backtrace:
Application: Dolphin (dolphin), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f09c900c8c0 (LWP 3751))]

Thread 3 (Thread 0x7f09b353a700 (LWP 3752)):
#0  0x7f09c8a43e8d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7f09bd1cfc62 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1
#2  0x7f09bd1d18d7 in xcb_wait_for_event () from
/usr/lib/x86_64-linux-gnu/libxcb.so.1
#3  0x7f09b588c629 in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5
#4  0x7f09c361584e in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7f09bfdc36fa in start_thread (arg=0x7f09b353a700) at
pthread_create.c:333
#6  0x7f09c8a4fb5d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 2 (Thread 0x7f09a5e07700 (LWP 3753)):
#0  0x7ffdc65dd9a7 in ?? ()
#1  0x7ffdc65ddcd5 in clock_gettime ()
#2  0x7f09c8a5dfb6 in __GI___clock_gettime (clock_id=1, tp=0x7f09a5e06a70)
at ../sysdeps/unix/clock_gettime.c:115
#3  0x7f09c36c5c16 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7f09c384a529 in QTimerInfoList::updateCurrentTime() () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7f09c384aa95 in QTimerInfoList::timerWait(timespec&) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7f09c384be7e in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7f09bf2378ad in g_main_context_prepare () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#8  0x7f09bf23824b in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#9  0x7f09bf23842c in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#10 0x7f09c384ca9b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#11 0x7f09c37f3dea in
QEventLoop::exec(QFlags) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#12 0x7f09c36108a4 in QThread::exec() () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#13 0x7f09c361584e in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#14 0x7f09bfdc36fa in start_thread (arg=0x7f09a5e07700) at
pthread_create.c:333
#15 0x7f09c8a4fb5d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 1 (Thread 0x7f09c900c8c0 (LWP 3751)):
[KCrash Handler]
#6  0x in ?? ()
#7  0x7f09c3806fc7 in QMetaObject::invokeMethod(QObject*, char const*,
Qt::ConnectionType, QGenericReturnArgument, QGenericArgument, QGenericArgument,
QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument,
QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x7f09c7048b99 in KDialogJobUiDelegate::Private::next() () from
/usr/lib/x86_64-linux-gnu/libKF5JobWidgets.so.5
#9  0x7f09c3825ea1 in QObject::event(QEvent*) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#10 0x7f09c42f905c in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#11 0x7f09c42fe516 in QApplication::notify(QObject*, QEvent*) () from
/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#12 0x7f09c37f662b in QCoreApplication::notifyInternal(QObject*, QEvent*)
() from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#13 0x7f09c37f8a26 in QCoreApplicationPrivate::sendPostedEvents(QObject*,
int, QThreadData*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#14 0x7f09c384c673 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#15 0x7f09bf238127 in g_main_context_dispatch () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#16 0x7f09bf238380 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#17 0x7f09bf23842c in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#18 0x7f09c384ca7f in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#19 0x7f09c37f3dea in
QEventLoop::exec(QFlags) () from

[plasmashell] [Bug 361200] Plasmashell Signal: Illegal Instruction - On KUBUNTU 16.04 Beta2 - During Install - Under Hyper-V

[Harrison via KDE Bugzilla]

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

--- Comment #5 from Harrison  ---
Good news, the problem ONLY occurs under Hyper-V!  I created an Install DVD and
it boots just fine.  So, the problem must be related to something in the
release of Plasmashell that is shipped with Kubuntu 16.04 [famous last words]. 
Is there any possibility of having someone else with a different environment
try this under Hyper-V to eliminate the possibility that it is unique to my
environment: Intel XEON E3-1275-v5 running on a ASRockRack C236M systemboard
with the Intel C236 chipset using the onboard processor graphics support?

If the "backtrace" would be of additional value, I will see whether there is
some way of creating a file that I can send to you.  The problem is, as I
previously said, this problem occurs so early in the Install process, there
isn't even any formatted disks upon which to put the backtrace file when the
crash occurs.  And, Hyper-V imposes limitations/restrictions on the test
environment [by design].

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

[plasmashell] [Bug 361200] Plasmashell Signal: Illegal Instruction - On KUBUNTU 16.04 Beta2 - During Install - Under Hyper-V

[Harrison via KDE Bugzilla]

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

--- Comment #4 from Harrison  ---
Created attachment 98209
  --> https://bugs.kde.org/attachment.cgi?id=98209=edit
Second page of "backtrace"

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

[plasmashell] [Bug 361200] Plasmashell Signal: Illegal Instruction - On KUBUNTU 16.04 Beta2 - During Install - Under Hyper-V

[Harrison via KDE Bugzilla]

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

--- Comment #3 from Harrison  ---
Created attachment 98208
  --> https://bugs.kde.org/attachment.cgi?id=98208=edit
First page of "backtrace"

The crash occurs so early in the Install process that it is difficult for me to
capture any data.  However, Kubuntu appears to be operational so I might be
able to install/configure SSH after the crash so I can copy the "backtrace" to
my Windows system.  Until then, perhaps, the following two screen capture pages
contain something of value.  And, I definitely saw a "flash" of the Plasma
Desktop before it crashed this time.

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

[plasmashell] [Bug 361200] Plasmashell Signal: Illegal Instruction - On KUBUNTU 16.04 Beta2 - During Install - Under Hyper-V

[Harrison via KDE Bugzilla]

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

--- Comment #1 from Harrison  ---
Installed Kubuntu 15.10 under Hyper-V on Intel E3-1275-v5 & chipset C236 and
everything worked fine.

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

[plasmashell] [Bug 361200] New: Plasmashell Signal: Illegal Instruction - On KUBUNTU 16.04 Beta2 - During Install - Under Hyper-V

[Harrison via KDE Bugzilla]

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

Bug ID: 361200
   Summary: Plasmashell Signal: Illegal Instruction - On KUBUNTU
16.04 Beta2 - During Install - Under Hyper-V
   Product: plasmashell
   Version: 5.5.95
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: grave
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: sainokawara.sisyp...@gmail.com
CC: bhus...@gmail.com, plasma-b...@kde.org

Problem occurs at boot of .iso doing Install:  I did see a "Logon Request"
screen and then the crash occurred when it appeared to try to use the Plasma
Desktop.  In addition to running the new Kubuntu 16.04 Beta 2 under Windows 10
Hyper-V, it is on the new Intel Xeon E3-1275-v5 AND I am using the onboard
processor graphics support, not a graphics card.

I will be happy to run/test anything you have that will allow you collect any
additional information you require.  There are so many new things involved in
this failure, I wouldn't know where to start.

Reproducible: Always

Steps to Reproduce:
1. Install under Windows 10 Hyper-V
2. Boot new Kubuntu 16.04 Beta 2 .ISO File for Install
3. Possibly related to new Intel Xeon E3-1275-v5 onboard processor graphics
support

Actual Results:  
Get message: "Executable: plasmashell PID: 1922 Signal: Illedgal instruction
(4)

Unfortunately, "Not Enough Information to submit "bug report" through the
normal channel.

Expected Results:  
Not "crashed".

If someone has something they would like me to try or report, I will be more
than happy to do so.  Unfortunately, I am currently limited on trying this in a
different physical environment: non-Hyper-V, non-Windows 10, using a graphics
card instead of the onboard E3-1275-v5 processor graphics support.

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

[krita] [Bug 360682] New: bug+fix: compiling Krita without OpenGL

[Brian Harrison via KDE Bugzilla]

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

Bug ID: 360682
   Summary: bug+fix: compiling Krita without OpenGL
   Product: krita
   Version: 2.9.11
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Tools
  Assignee: krita-bugs-n...@kde.org
  Reporter: urqu...@yahoo.com

I was building Krita on a platform without OpenGL, only OpenGL ES.  It would
fail in calligra/krita/ui/canvas/kiscanvas2.cpp saying that
m_d->openGLImageTextures was not a member function.  Since I knew I could do
this in the past, I tracked it down and found that in two locations,
openGLImageTextures was called outside of a "#ifdef HAVE_OPENGL".

Around line 261 I changed:

if (m_d->currentCanvasIsOpenGL) {
#ifdef HAVE_OPENGL
Q_ASSERT(m_d->openGLImageTextures);
m_d->openGLImageTextures->setChannelFlags(m_d->channelFlags);
#else
Q_ASSERT_X(0, "KisCanvas2::setChannelFlags", "Bad use of
setChannelFlags(). It shouldn't have happened =(");
#endif
} else {
Q_ASSERT(m_d->prescaledProjection);
m_d->prescaledProjection->setChannelFlags(m_d->channelFlags);
}

***to***

#ifdef HAVE_OPENGL
if (m_d->currentCanvasIsOpenGL) {
//#ifdef HAVE_OPENGL
Q_ASSERT(m_d->openGLImageTextures);
m_d->openGLImageTextures->setChannelFlags(m_d->channelFlags);
//#else
Q_ASSERT_X(0, "KisCanvas2::setChannelFlags", "Bad use of
setChannelFlags(). It shouldn't have happened =(");
//#endif
} else {
#endif
Q_ASSERT(m_d->prescaledProjection);
m_d->prescaledProjection->setChannelFlags(m_d->channelFlags);
#ifdef HAVE_OPENGL
}
#endif

***and around line 413***

{
m_d->prescaledProjection = 0;
m_d->openGLImageTextures = 0;

***to***

{
m_d->prescaledProjection = 0;
#ifdef HAVE_OPENGL
m_d->openGLImageTextures = 0;
#endif

  Dirty, but it compiles and runs.  Seems to be stable.  I wish I could fully
test it, but the next step is getting the OS to see the tablet.

Reproducible: Always

Steps to Reproduce:
1.  Follow standard feline instructions to compile Krita 2.9.11 on an OpenGL ES
platform.  It *might* happen if you hard-wire KoConfig.h to "#define
HAVE_OPENGL false" on any machine.
2.
3.

Actual Results:  
error: m_d->openGLImageTextures was not a member function

Expected Results:  
compile without OpenGL

Hardware: ODROID XU4.  Obscure platform.  Bug low priority.  I would not have
reported it except that I also found a solution.  Dirty though it is.

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