[klipper] [Bug 409803] "Enable clipboard actions" missing from context menu

2020-01-08 Thread Jeff Trull
https://bugs.kde.org/show_bug.cgi?id=409803

Jeff Trull  changed:

   What|Removed |Added

 Status|REPORTED|CONFIRMED
 Ever confirmed|0   |1

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

[klipper] [Bug 409803] "Enable clipboard actions" missing from context menu

2020-01-08 Thread Jeff Trull
https://bugs.kde.org/show_bug.cgi?id=409803

--- Comment #2 from Jeff Trull  ---
Created attachment 124980
  --> https://bugs.kde.org/attachment.cgi?id=124980=edit
UI element referring to nonexistent control

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

[klipper] [Bug 409803] "Enable clipboard actions" missing from context menu

2020-01-08 Thread Jeff Trull
https://bugs.kde.org/show_bug.cgi?id=409803

Jeff Trull  changed:

   What|Removed |Added

 CC||jetr...@sbcglobal.net

--- Comment #1 from Jeff Trull  ---
The irony here (and what I came to report) is the documentation and at least
one UI control refer to a "Enable clipboard actions" control - which does not
exist. Attached is an error message that refers to it - but there is no such
control when you right-click on klipper.

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

[clazy] [Bug 389473] Clang plugin error with latest versions

2018-01-29 Thread Jeff Trull
https://bugs.kde.org/show_bug.cgi?id=389473

--- Comment #12 from Jeff Trull <jetr...@sbcglobal.net> ---
IMO an acceptable resolution would be to add an LLVM version check ("clazy has 
only been tested with versions X, Y, or Z") etc.

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

[clazy] [Bug 389473] Clang plugin error with latest versions

2018-01-28 Thread Jeff Trull
https://bugs.kde.org/show_bug.cgi?id=389473

--- Comment #9 from Jeff Trull <jetr...@sbcglobal.net> ---
Rebuilding clang with -DBUILD_SHARED_LIBS=ON and then rebuilding clazy results
in a slightly different error message:

: CommandLine Error: Option 'help-list' registered more than once!
fatal error: error in backend: inconsistency in registered CommandLine options
clang: error: clang frontend command failed with exit code 70 (use -v to see
invocation)

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

[clazy] [Bug 389473] Clang plugin error with latest versions

2018-01-28 Thread Jeff Trull
https://bugs.kde.org/show_bug.cgi?id=389473

--- Comment #5 from Jeff Trull <jetr...@sbcglobal.net> ---
Perhaps it is a simple matter of testing the libTooling version in CMake, since
the API is unstable (assuming you are expecting a particular LLVM release)...

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

[clazy] [Bug 389473] Clang plugin error with latest versions

2018-01-28 Thread Jeff Trull
https://bugs.kde.org/show_bug.cgi?id=389473

--- Comment #4 from Jeff Trull <jetr...@sbcglobal.net> ---
cmake -DLLVM_ROOT=/home/jet/oss/llvm/build

where /home/jet/oss/llvm is svn head as of a week ago. 

On Sunday, January 28, 2018 9:05 AM, Sergio Martins
<bugzilla_nore...@kde.org> wrote:


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

--- Comment #3 from Sergio Martins <smart...@kde.org> ---
which cmake configure line ?

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

[clazy] [Bug 389473] Clang plugin error with latest versions

2018-01-28 Thread Jeff Trull
https://bugs.kde.org/show_bug.cgi?id=389473

--- Comment #2 from Jeff Trull <jetr...@sbcglobal.net> ---
   This is a full source build...

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

[clazy] [Bug 389473] New: Clang plugin error with latest versions

2018-01-26 Thread Jeff Trull
https://bugs.kde.org/show_bug.cgi?id=389473

Bug ID: 389473
   Summary: Clang plugin error with latest versions
   Product: clazy
   Version: unspecified
  Platform: Compiled Sources
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: unassigned-b...@kde.org
  Reporter: jetr...@sbcglobal.net
CC: smart...@kde.org
  Target Milestone: ---

Clazy 1.3 with Clang 7.0 produces a plugin-related error when I try to run
using the non-standalone (i.e. QMAKE_CXX=clazy) version:

clazy -c -pipe -O2 -std=c++1y -Wall -W -D_REENTRANT -fPIC -DQT_NO_DEBUG
-DQT_GUI_LIB -DQT_CORE_LIB -I. -I/home/jet/Qt5.5.1.clang/include
-I/home/jet/Qt5.5.1.clang/include/QtGui
-I/home/jet/Qt5.5.1.clang/include/QtCore -I.
-I/home/jet/Qt5.5.1.clang/mkspecs/linux-clang -o foo.o ../../foo.cpp

: CommandLine Error: Option 'static-func-full-module-prefix' registered more
than once!
fatal error: error in backend: inconsistency in registered CommandLine options
clang-7.0: error: clang frontend command failed with exit code 70 (use -v to
see invocation)

Clang runs fine on its own.

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

[plasmashell] [Bug 378052] New: Moving windows to other desktops crashes plasma sometimes

2017-03-24 Thread Jeff Trull
https://bugs.kde.org/show_bug.cgi?id=378052

Bug ID: 378052
   Summary: Moving windows to other desktops crashes plasma
sometimes
   Product: plasmashell
   Version: 5.8.5
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: jetr...@sbcglobal.net
CC: bhus...@gmail.com, plasma-b...@kde.org
  Target Milestone: 1.0

Application: plasmashell (5.8.5)

Qt Version: 5.6.1
Frameworks Version: 5.28.0
Operating System: Linux 4.8.0-41-generic x86_64
Distribution: Ubuntu 16.10

-- Information about the crash:
I was moving 3 of my 4 Chrome windows to a different desktop when Plasma
crashed and gave me this reporting assistant wizard.

-- Backtrace:
Application: Plasma (plasmashell), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fc14980ed40 (LWP 2726))]

Thread 26 (Thread 0x7fc05cde4700 (LWP 23826)):
#0  0x7fc138717eee in pa_pstream_ref () from
/usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-9.0.so
#1  0x7fc138718694 in ?? () from
/usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-9.0.so
#2  0x7fc138718a69 in ?? () from
/usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-9.0.so
#3  0x7fc1387192ea in ?? () from
/usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-9.0.so
#4  0x7fc1394c625c in pa_mainloop_dispatch () from
/usr/lib/x86_64-linux-gnu/libpulse.so.0
#5  0x7fc1394c665c in pa_mainloop_iterate () from
/usr/lib/x86_64-linux-gnu/libpulse.so.0
#6  0x7fc1394c6700 in pa_mainloop_run () from
/usr/lib/x86_64-linux-gnu/libpulse.so.0
#7  0x7fc1394d4729 in ?? () from /usr/lib/x86_64-linux-gnu/libpulse.so.0
#8  0x7fc138729228 in ?? () from
/usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-9.0.so
#9  0x7fc14388e6ca in start_thread (arg=0x7fc05cde4700) at
pthread_create.c:333
#10 0x7fc1440ba0af in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:105

Thread 25 (Thread 0x7fc0749b9700 (LWP 21896)):
#0  0x7fffa27fe939 in ?? ()
#1  0x7fffa27febc9 in clock_gettime ()
#2  0x7fc1440c8846 in __GI___clock_gettime (clock_id=1,
tp=tp@entry=0x7fc0749b8a40) at ../sysdeps/unix/clock_gettime.c:115
#3  0x7fc14485a726 in qt_clock_gettime (ts=0x7fc0749b8a40, clock=) at tools/qelapsedtimer_unix.cpp:105
#4  do_gettime (frac=, sec=) at
tools/qelapsedtimer_unix.cpp:156
#5  qt_gettime () at tools/qelapsedtimer_unix.cpp:165
#6  0x7fc1449da039 in QTimerInfoList::updateCurrentTime
(this=this@entry=0x7f801c0012e0) at kernel/qtimerinfo_unix.cpp:84
#7  0x7fc1449da5e5 in QTimerInfoList::timerWait (this=0x7f801c0012e0,
tm=...) at kernel/qtimerinfo_unix.cpp:381
#8  0x7fc1449db99e in timerSourcePrepareHelper (timeout=0x7fc0749b8b14,
src=) at kernel/qeventdispatcher_glib.cpp:126
#9  timerSourcePrepare (source=, timeout=0x7fc0749b8b14) at
kernel/qeventdispatcher_glib.cpp:159
#10 0x7fc140deded9 in g_main_context_prepare () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#11 0x7fc140dee8fb in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#12 0x7fc140deeaec in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#13 0x7fc1449dc4ab in QEventDispatcherGlib::processEvents
(this=0x7f801c002800, flags=...) at kernel/qeventdispatcher_glib.cpp:419
#14 0x7fc1449840fa in QEventLoop::exec (this=this@entry=0x7fc0749b8ce0,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#15 0x7fc1447a9d43 in QThread::exec (this=) at
thread/qthread.cpp:500
#16 0x7fc1470abc65 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5
#17 0x7fc1447aec68 in QThreadPrivate::start (arg=0x61678a0) at
thread/qthread_unix.cpp:341
#18 0x7fc14388e6ca in start_thread (arg=0x7fc0749b9700) at
pthread_create.c:333
#19 0x7fc1440ba0af in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:105

Thread 24 (Thread 0x7fc05d7fa700 (LWP 8109)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7fc1447afb2b in QWaitConditionPrivate::wait
(time=18446744073709551615, this=0x48c42e0) at
thread/qwaitcondition_unix.cpp:136
#2  QWaitCondition::wait (this=, mutex=0x45937b0,
time=18446744073709551615) at thread/qwaitcondition_unix.cpp:208
#3  0x7fc08d7dc0af in
ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*,
bool, bool, bool) () from /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#4  0x7fc08d7e00a8 in ?? () from
/usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#5  0x7fc08d7db29d in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from
/usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#6  0x7fc08d7e0102 in ?? () from
/usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#7  

[drkonqi] [Bug 354288] Crash Reporting Assistant gets error 32000 from bugzilla

2016-01-27 Thread Jeff Trull via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=354288

Jeff Trull <jetr...@sbcglobal.net> changed:

   What|Removed |Added

 CC||jetr...@sbcglobal.net

--- Comment #1 from Jeff Trull <jetr...@sbcglobal.net> ---
This just happened to me as well.  Please mark as confirmed.

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


[krunner] [Bug 353977] Krunner crashes when connecting/disconnecting second monitor.

2015-12-21 Thread Jeff Trull via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=353977

--- Comment #8 from Jeff Trull <jetr...@sbcglobal.net> ---
Would you mind posting that upstream bug report?  Would be nice to track it. 
Thanks!

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


[krunner] [Bug 353977] Krunner crashes when connecting/disconnecting second monitor.

2015-12-21 Thread Jeff Trull via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=353977

Jeff Trull <jetr...@sbcglobal.net> changed:

   What|Removed |Added

 CC||jetr...@sbcglobal.net

--- Comment #6 from Jeff Trull <jetr...@sbcglobal.net> ---
I have this too, with similar stack trace.  Can we mark it "confirmed"?

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