[krita] [Bug 369480] Preset choosing bugs: stylus tip-presets don't switch properly, / key broken

[Robert via KDE Bugzilla]

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

--- Comment #3 from Robert  ---
I am also experiencing this same bug with the git master build 3.0.90

I see the link Boudenwijn posted, but I have no idea how to apply it.

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

[krita] [Bug 369480] Preset choosing bugs: stylus tip-presets don't switch properly, / key broken

[Robert via KDE Bugzilla]

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

Robert  changed:

   What|Removed |Added

 CC||rggor...@gmail.com

--- Comment #2 from Robert  ---
I am also experiencing this same bug with the git master build 3.0.90

I see the link Boudenwijn posted, but I have no idea how to apply it.

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

[kdenlive] [Bug 364438] The preview screen is black when I give play

[Robert via KDE Bugzilla]

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

--- Comment #5 from Robert  ---
I've updated the nvidia drivers and it fixed the problem, I guess that some
modules may not work as intended after kernel update (the problem with black
preview in kdenlive appeared after system upgrade using apt).

Hope that my post will help someone experiencing similar issue.

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

[kdenlive] [Bug 364438] The preview screen is black when I give play

[Robert via KDE Bugzilla]

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

Robert  changed:

   What|Removed |Added

 CC||rgru...@gmail.com

--- Comment #4 from Robert  ---
Hi there, I have Kdenlive 16.04.3 installed on Kali linux (Linux (x86_64)
release 4.6.0-kali1-amd64, nvidia graphic driver) and have same problem as
described above. The playback screen is allways black, it does not depend on
clip codecs etc. When started from console kdenlive, loaded previously working
project with clip on timeline it does not throw any errors:

roof@desktop:~$ kdenlive
Removing cache at "/home/roof/.cache/kdenlive-thumbs.kcache"
OpenGL vendor:  "NVIDIA Corporation"
OpenGL renderer:  "GeForce GTS 450/PCIe/SSE2"
OpenGL ARG_SYNC:  true
OpenGL OpenGLES:  false
OpenGL vendor:  "NVIDIA Corporation"
OpenGL renderer:  "GeForce GTS 450/PCIe/SSE2"
OpenGL ARG_SYNC:  true
OpenGL OpenGLES:  false
 // / processing file open
 // / processing file open: validate
Opening a document with version  0.94  /  0.94
 // / processing file validate ok
***
FOUND GUIDES:  0 
**
"Creating audio thumbnails (1/2)"
"Creating audio thumbnails (2/5)"
"Creating audio thumbnails (3/5)"
"Creating audio thumbnails (4/5)"
"Creating audio thumbnails (5/5)"
"Creating audio thumbnails (6/5)"

The sound from clip is played properly, but the preview screen stays black no
matter what. I've tried different configurations settings, resetting to
defaults etc. If you have any questions feel free to ask.

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

[krita] [Bug 365178] Floating docker causes wacom pen to stop registering brush strokes

[Robert via KDE Bugzilla]

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

--- Comment #7 from Robert  ---
I wonder why it re-emerged.

On Fri, Jul 8, 2016 at 3:01 AM, Boudewijn Rempt via KDE Bugzilla <
bugzilla_nore...@kde.org> wrote:

> https://bugs.kde.org/show_bug.cgi?id=365178
>
> --- Comment #6 from Boudewijn Rempt  ---
> Hm, then your issue might be a bug that got fixed in 5.6 then :-)
>
> --
> You are receiving this mail because:
> You reported the bug.
>

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

[krita] [Bug 365178] Floating docker causes wacom pen to stop registering brush strokes

[Robert via KDE Bugzilla]

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

--- Comment #5 from Robert  ---
(In reply to Robert from comment #4)
> (In reply to Boudewijn Rempt from comment #3)
> > Then I suspect you also have Qt 5.7 and that it's a regression in Qt, and
> > might be related to https://bugs.kde.org/show_bug.cgi?id=364850
> 
> "qmake --version" "QMake version 2.01a
Using Qt version 4.8.6 in /usr/lib64/qt4"
dev-qt/qtgui 4.8.6 and 5.5.1 are installed on my system.
I don't know that my issue is the same as with the other bug you linked. I
didn't experience any problem with scrolling. The canvas would stop responding
when the floating docker was clicked on with the pen or mouse. When I used the
shortcut, after restarting Krita, to another tool, and back to the brush, I
didn't have an issue. That is how I figured that it was the floating dockers
that was causing the malfunction.

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

[krita] [Bug 365178] Floating docker causes wacom pen to stop registering brush strokes

[Robert via KDE Bugzilla]

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

--- Comment #4 from Robert  ---
(In reply to Boudewijn Rempt from comment #3)
> Then I suspect you also have Qt 5.7 and that it's a regression in Qt, and
> might be related to https://bugs.kde.org/show_bug.cgi?id=364850

dev-qt/qtgui 4.8.6 and 5.5.1 are installed.

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

[krita] [Bug 365178] Floating docker causes wacom pen to stop registering brush strokes

[Robert via KDE Bugzilla]

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

--- Comment #2 from Robert  ---
(In reply to wolthera from comment #1)
> Does the same happen with the appimage?

No it does not. I works like it should when running the appimage. I can have
any of the dockers undocked and switch between any of the tools without loosing
the use of my pen's contact with my tablet, or ability to work in the document.

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

[krita] [Bug 365178] New: Floating docker causes wacom pen to stop registering brush strokes

[Robert via KDE Bugzilla]

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

Bug ID: 365178
   Summary: Floating docker causes wacom pen to stop registering
brush strokes
   Product: krita
   Version: git master
  Platform: Gentoo Packages
OS: Linux
Status: UNCONFIRMED
  Severity: major
  Priority: NOR
 Component: Dockers
  Assignee: krita-bugs-n...@kde.org
  Reporter: rggor...@gmail.com

In Krita 3.1 (git ed52ec5), if any docker is un-docked, when selecting another
tool or docker box the wacom pen will stop registering pen stokes, button
clicks, or presses. Changing to another brush preset will only allow for one
pen stroke, but once it pen is lifted, it no longer works again. The current
document has to be saved with keyboard short cuts, closed, and restarted before
being able to use the pen again.

gdb info:
gdb krita
GNU gdb (Gentoo 7.10.1 vanilla) 7.10.1
Copyright (C) 2015 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-pc-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
.
Find the GDB manual and other documentation resources online at:
.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from krita...done.
(gdb) run
Starting program: /home/rbear/krita/inst/bin/krita 
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib64/libthread_db.so.1".
krita.lib.pigment: Legacy integer arithmetics implementation
[New Thread 0x7fffe64aa700 (LWP 8002)]
Set style "fusion"
OpenGL Info
  Vendor:  NVIDIA Corporation
  Renderer:  GeForce GTX 980 Ti/PCIe/SSE2
  Version:  4.5.0 NVIDIA 367.27
  Shading language:  4.50 NVIDIA
  Requested format:  QSurfaceFormat(version 3.0, options QFlags(0x4),
depthBufferSize 24, redBufferSize -1, greenBufferSize -1, blueBufferSize -1,
alphaBufferSize -1, stencilBufferSize 8, samples -1, swapBehavior 2,
swapInterval 0, profile  2)
  Current format:QSurfaceFormat(version 4.5, options QFlags(0x4),
depthBufferSize 24, redBufferSize 8, greenBufferSize 8, blueBufferSize 8,
alphaBufferSize 0, stencilBufferSize 8, samples -1, swapBehavior 2,
swapInterval 0, profile  2)
krita has opengl true
Setting XDG_DATA_DIRS
"/home/rbear/krita/inst/bin/../share:/usr/local/share:/usr/share"
Available translations QSet("en_US")
Available domain translations QSet("en_US")
Override language: ""
[Thread 0x7fffe64aa700 (LWP 8002) exited]
[Inferior 1 (process 7998) exited normally]
(gdb) run
Starting program: /home/rbear/krita/inst/bin/krita 
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib64/libthread_db.so.1".
krita.lib.pigment: Legacy integer arithmetics implementation
[New Thread 0x7fffe64aa700 (LWP 8771)]
Set style "fusion"
OpenGL Info
  Vendor:  NVIDIA Corporation
  Renderer:  GeForce GTX 980 Ti/PCIe/SSE2
  Version:  4.5.0 NVIDIA 367.27
  Shading language:  4.50 NVIDIA
  Requested format:  QSurfaceFormat(version 3.0, options QFlags(0x4),
depthBufferSize 24, redBufferSize -1, greenBufferSize -1, blueBufferSize -1,
alphaBufferSize -1, stencilBufferSize 8, samples -1, swapBehavior 2,
swapInterval 0, profile  2)
  Current format:QSurfaceFormat(version 4.5, options QFlags(0x4),
depthBufferSize 24, redBufferSize 8, greenBufferSize 8, blueBufferSize 8,
alphaBufferSize 0, stencilBufferSize 8, samples -1, swapBehavior 2,
swapInterval 0, profile  2)
krita has opengl true
Setting XDG_DATA_DIRS
"/home/rbear/krita/inst/bin/../share:/usr/local/share:/usr/share"
Available translations QSet("en_US")
Available domain translations QSet("en_US")
Override language: ""
KoJsonTrader will load its plugins from
"/home/rbear/krita/inst/lib64/kritaplugins"
[New Thread 0x7fffcbb6d700 (LWP 12062)]
[New Thread 0x7fffcb36c700 (LWP 12063)]
libpng warning: iCCP: too many profiles
libpng warning: iCCP: too many profiles
libpng warning: iCCP: too many profiles
libpng warning: iCCP: too many profiles
[New Thread 0x7fffca76a700 (LWP 12149)]
[Thread 0x7fffca76a700 (LWP 12149) exited]
[New Thread 0x7fffca76a700 (LWP 12169)]
KoJsonTrader will load its plugins from
"/home/rbear/krita/inst/lib64/kritaplugins"
[New Thread 0x7fffb9d91700 (LWP 15306)]
[New Thread 0x7fffb9590700 (LWP 15307)]
[New Thread 0x7fffb8d8f700 (LWP 15308)]
[New Thread 0x7fffabfff700 (LWP 15309)]
[New Thread 0x7fffab7fe700 (LWP 15310)]
[New Thread 0x7fffaaffd700 (LWP 15311)]
[New Thread 0x7fffaa7fc700 (LWP 15312)]
[New Thread 0x7fffa9ffb700 (LWP 15313)]
[New Thread 0x7fffa97fa700 (LWP 15314)]
[New Thread 0x7fffa8ff9700 (LWP 15315)]
[New Thread 0x7fff8bfff700 (L

[plasmashell] [Bug 364920] New: Remote Login per VNC/XVNC crashes Plasma Shell/Desktop

[Robert via KDE Bugzilla]

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

Bug ID: 364920
   Summary: Remote Login per VNC/XVNC crashes Plasma Shell/Desktop
   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: rob...@gaiswinkler.de
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:
Remote Login with VNC to XVNX (xinetd). Tried with home directory of former
KDE4 account and with home directory of fresh user without configuration - both
crash.

Some dialogs show up (keyring, dropbox etc.) but there is no desktop GUI.

The crash can be reproduced every time.

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

Thread 10 (Thread 0x7f12066cf700 (LWP 27156)):
#0  0x7f122426d03f in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f1211209ac3 in  () at /usr/lib64/dri/swrast_dri.so
#2  0x7f1211209637 in  () at /usr/lib64/dri/swrast_dri.so
#3  0x7f12242690a4 in start_thread () at /lib64/libpthread.so.0
#4  0x7f1224a67fed in clone () at /lib64/libc.so.6

Thread 9 (Thread 0x7f1205ece700 (LWP 27157)):
#0  0x7f122426d03f in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f1211209ac3 in  () at /usr/lib64/dri/swrast_dri.so
#2  0x7f1211209637 in  () at /usr/lib64/dri/swrast_dri.so
#3  0x7f12242690a4 in start_thread () at /lib64/libpthread.so.0
#4  0x7f1224a67fed in clone () at /lib64/libc.so.6

Thread 8 (Thread 0x7f12056cd700 (LWP 27158)):
#0  0x7f122426d03f in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f1211209ac3 in  () at /usr/lib64/dri/swrast_dri.so
#2  0x7f1211209637 in  () at /usr/lib64/dri/swrast_dri.so
#3  0x7f12242690a4 in start_thread () at /lib64/libpthread.so.0
#4  0x7f1224a67fed in clone () at /lib64/libc.so.6

Thread 7 (Thread 0x7f1204ecc700 (LWP 27159)):
#0  0x7f122426d03f in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f1211209ac3 in  () at /usr/lib64/dri/swrast_dri.so
#2  0x7f1211209637 in  () at /usr/lib64/dri/swrast_dri.so
#3  0x7f12242690a4 in start_thread () at /lib64/libpthread.so.0
#4  0x7f1224a67fed in clone () at /lib64/libc.so.6

Thread 6 (Thread 0x7f1202472700 (LWP 27160)):
#0  0x7f1224a5fbbd in poll () at /lib64/libc.so.6
#1  0x7f122113ce64 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7f122113cf7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#3  0x7f122538cd8b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#4  0x7f1225333d53 in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#5  0x7f122515561a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#6  0x7f1228469e18 in  () at /usr/lib64/libQt5Qml.so.5
#7  0x7f122515a32f in  () at /usr/lib64/libQt5Core.so.5
#8  0x7f12242690a4 in start_thread () at /lib64/libpthread.so.0
#9  0x7f1224a67fed in clone () at /lib64/libc.so.6

Thread 5 (Thread 0x7f11f695e700 (LWP 27161)):
#0  0x7f1224a5fbbd in poll () at /lib64/libc.so.6
#1  0x7f122113ce64 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7f122113cf7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#3  0x7f122538cd8b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#4  0x7f1225333d53 in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#5  0x7f122515561a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#6  0x7f1228469e18 in  () at /usr/lib64/libQt5Qml.so.5
#7  0x7f122515a32f in  () at /usr/lib64/libQt5Core.so.5
#8  0x7f12242690a4 in start_thread () at /lib64/libpthread.so.0
#9  0x7f1224a67fed in clone () at /lib64/libc.so.6

Thread 4 (Thread 0x7f11f5132700 (LWP 27162)):
#0  0x7f122113c017 in g_main_context_release () at
/usr/lib64/libglib-2.0.so.0
#1  0x7f122113ce0e in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7f122113cf7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#3  0x7f122538cd8b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#4  0x7f1225333d53 in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#5  0x7f122515561a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#6  0x7f1228469e18 in  () at /usr/lib64/libQt5Qml.so.5
#7  0x7f122515a32f in  () at /usr/lib64/libQt5Core.so.5
#8  0x7f12242690a4 in start_thread () at /lib64/libpthread.so.0
#9  0x7f1224a67fed in clone () at /lib64/libc.so.6

Thr

[okular] [Bug 364246] some text not visible in pdf view

[Robert via KDE Bugzilla]

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

--- Comment #5 from Robert  ---
> Can you check what is the version of poppler (shown in the package suffix)?

I have these poppler rpms installed:
poppler-0.34.0-2.fc23.x86_64
poppler-qt-0.34.0-2.fc23.x86_64
poppler-sharp-0.0.3-8.fc23.x86_64
poppler-qt5-0.34.0-2.fc23.x86_64

> Is it possible to check if all fonts from your document are inbuilt in it
> (File -> Properties -> Fonts)?

there are 3, all named 'n/a', type 3, Fully embedded

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

[okular] [Bug 364246] some text not visible in pdf view

[Robert via KDE Bugzilla]

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

--- Comment #3 from Robert  ---
Created attachment 99475
  --> https://bugs.kde.org/attachment.cgi?id=99475&action=edit
page 2 extracted using pdfedit

pdfedit was able to extract the legalese page which exhibits the issue.

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

[okular] [Bug 364246] some text not visible in pdf view

[Robert via KDE Bugzilla]

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

--- Comment #2 from Robert  ---
Created attachment 99474
  --> https://bugs.kde.org/attachment.cgi?id=99474&action=edit
page 2 with print preview

here you can see the missing text in the print preview dialog and the large
blank area in the normal display.

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

[okular] [Bug 364246] some text not visible in pdf view

[Robert via KDE Bugzilla]

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

--- Comment #1 from Robert  ---
Created attachment 99473
  --> https://bugs.kde.org/attachment.cgi?id=99473&action=edit
page 2 as displayed

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

[okular] [Bug 364246] New: some text not visible in pdf view

[Robert via KDE Bugzilla]

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

Bug ID: 364246
   Summary: some text not visible in pdf view
   Product: okular
   Version: 0.24.0
  Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: PDF backend
  Assignee: okular-de...@kde.org
  Reporter: r...@bugs.kde.pu.futz.org

When I download my credit card statements for a particular (large) bank. Most
of the text is not visible. However, if I select 'print preview' or print, the
text is there. (All text is visible using xpdf.)

It's almost like there are 2 layers - generic background text (bank name, some
legalese) which is visible, and then all the normal information (address,
transaction information) which is not.

This is just with one company. My other statements work fine.

rpm version is okular-15.12.3-1.fc23.x86_64, about dialog says 0.24.2.

Reproducible: Always

Steps to Reproduce:
1. open bank pdf

Actual Results:  
some text not visible

Expected Results:  
all text visible

Unfortunately, being that it's my credit card statement, I don't feel
comfortable attaching an example. I do have some screen-shots I'll attach from
a page with mostly legalese.

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

[krunner] [Bug 363195] New: Error reported when attempting to open a mail message from krunner

[Robert via KDE Bugzilla]

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

Bug ID: 363195
   Summary: Error reported when attempting to open a mail message
from krunner
   Product: krunner
   Version: 4.11.9
  Platform: Gentoo Packages
OS: Linux
Status: UNCONFIRMED
  Severity: minor
  Priority: NOR
 Component: general
  Assignee: m...@vhanda.in
  Reporter: sam...@yahoo.com

When I hit enter to open a mail message in Krunner I the message doesn't open
and I get a dialog box telling me to file a bug report about it. The precise
error message is:

"Internal Error Please send a full bug report at http://bugs.kde.org Unable to
fetch item from backend (collection -1) : Unable to retrieve item from
resource: Cannot fetch item in offline mode."
Not sure why it says it's in offline mode, I'm connected to the Internet while
I'm doing this.

Three additional errors appear in the notifier in the system tray:
"Examining Finished" "akonadi://?item=10610"
"AOL Mail (Samnis)" "AOL mail (Samnis): Cannot fetch item in offline mode."
"/var/tmp/kdecache-logomachist/krun/5622_0_"

There was a fourth notifier error message that appeared the first few times I
reproduced this, but I didn't catch what it was and now I'm only seeing three
errors. 

Reproducible: Always

Steps to Reproduce:
1. Press Alt + F2 to get the krunner box.
2. Type something that brings up an email on the dropdown menu.
3. Hit enter to open the email.

Actual Results:  
After the error messages appeared? Nothing.

Expected Results:  
I believe it was supposed to open the email in Kmail.

I'm running Linux 3.14.16-gentoo.

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

[plasmashell] [Bug 362510] New: plasmas crashing multiple times per day

[Robert via KDE Bugzilla]

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

Bug ID: 362510
   Summary: plasmas crashing multiple times per day
   Product: plasmashell
   Version: 5.5.5
  Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: r...@bugs.kde.pu.futz.org
CC: bhus...@gmail.com, plasma-b...@kde.org

Application: plasmashell (5.5.5)

Qt Version: 5.6.0
Operating System: Linux 4.4.7-300.fc23.x86_64 x86_64
Distribution: "Fedora release 23 (Twenty Three)"

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

normal usage.. crashes seem to be when opening/closing apps or switching
deskdtops/activities.

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 0x7f3f21192940 (LWP 2733))]

Thread 9 (Thread 0x7f3f17ab7700 (LWP 2742)):
#0  0x7f3f2fa24fdd in poll () at /lib64/libc.so.6
#1  0x7f3f34b97272 in _xcb_conn_wait () at /lib64/libxcb.so.1
#2  0x7f3f34b98ee7 in xcb_wait_for_event () at /lib64/libxcb.so.1
#3  0x7f3f19d0a349 in QXcbEventReader::run() () at /lib64/libQt5XcbQpa.so.5
#4  0x7f3f30636e18 in QThreadPrivate::start(void*) () at
/lib64/libQt5Core.so.5
#5  0x7f3f2ed6460a in start_thread () at /lib64/libpthread.so.0
#6  0x7f3f2fa30a4d in clone () at /lib64/libc.so.6

Thread 8 (Thread 0x7f3f164c1700 (LWP 2745)):
#0  0x7f3f2fa20bcd in read () at /lib64/libc.so.6
#1  0x7f3f2b541390 in g_wakeup_acknowledge () at /lib64/libglib-2.0.so.0
#2  0x7f3f2b4fdc64 in g_main_context_check () at /lib64/libglib-2.0.so.0
#3  0x7f3f2b4fe110 in g_main_context_iterate.isra () at
/lib64/libglib-2.0.so.0
#4  0x7f3f2b4fe27c in g_main_context_iteration () at
/lib64/libglib-2.0.so.0
#5  0x7f3f3085fd0b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /lib64/libQt5Core.so.5
#6  0x7f3f308086ea in
QEventLoop::exec(QFlags) () at
/lib64/libQt5Core.so.5
#7  0x7f3f30632004 in QThread::exec() () at /lib64/libQt5Core.so.5
#8  0x7f3f30ff74b5 in QDBusConnectionManager::run() () at
/lib64/libQt5DBus.so.5
#9  0x7f3f30636e18 in QThreadPrivate::start(void*) () at
/lib64/libQt5Core.so.5
#10 0x7f3f2ed6460a in start_thread () at /lib64/libpthread.so.0
#11 0x7f3f2fa30a4d in clone () at /lib64/libc.so.6

Thread 7 (Thread 0x7f3f14c80700 (LWP 2760)):
#0  0x7f3f2b4fe0d2 in g_main_context_iterate.isra () at
/lib64/libglib-2.0.so.0
#1  0x7f3f2b4fe27c in g_main_context_iteration () at
/lib64/libglib-2.0.so.0
#2  0x7f3f3085fd0b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /lib64/libQt5Core.so.5
#3  0x7f3f308086ea in
QEventLoop::exec(QFlags) () at
/lib64/libQt5Core.so.5
#4  0x7f3f30632004 in QThread::exec() () at /lib64/libQt5Core.so.5
#5  0x7f3f33a271b5 in QQmlThreadPrivate::run() () at /lib64/libQt5Qml.so.5
#6  0x7f3f30636e18 in QThreadPrivate::start(void*) () at
/lib64/libQt5Core.so.5
#7  0x7f3f2ed6460a in start_thread () at /lib64/libpthread.so.0
#8  0x7f3f2fa30a4d in clone () at /lib64/libc.so.6

Thread 6 (Thread 0x7f3f01a58700 (LWP 2839)):
#0  0x7f3f2fa24fdd in poll () at /lib64/libc.so.6
#1  0x7f3f2b4fe16c in g_main_context_iterate.isra () at
/lib64/libglib-2.0.so.0
#2  0x7f3f2b4fe27c in g_main_context_iteration () at
/lib64/libglib-2.0.so.0
#3  0x7f3f3085fd0b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /lib64/libQt5Core.so.5
#4  0x7f3f308086ea in
QEventLoop::exec(QFlags) () at
/lib64/libQt5Core.so.5
#5  0x7f3f30632004 in QThread::exec() () at /lib64/libQt5Core.so.5
#6  0x7f3f33a271b5 in QQmlThreadPrivate::run() () at /lib64/libQt5Qml.so.5
#7  0x7f3f30636e18 in QThreadPrivate::start(void*) () at
/lib64/libQt5Core.so.5
#8  0x7f3f2ed6460a in start_thread () at /lib64/libpthread.so.0
#9  0x7f3f2fa30a4d in clone () at /lib64/libc.so.6

Thread 5 (Thread 0x7f3efbfff700 (LWP 2846)):
#0  0x7f3f2b542734 in g_mutex_unlock () at /lib64/libglib-2.0.so.0
#1  0x7f3f2b4fd790 in g_main_context_prepare () at /lib64/libglib-2.0.so.0
#2  0x7f3f2b4fe09b in g_main_context_iterate.isra () at
/lib64/libglib-2.0.so.0
#3  0x7f3f2b4fe27c in g_main_context_iteration () at
/lib64/libglib-2.0.so.0
#4  0x7f3f3085fd0b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /lib64/libQt5Core.so.5
#5  0x7f3f308086ea in
QEventLoop::exec(QFlags) () at
/lib64/libQt5Core.so.5
#6  0x7f3f30632004 in QThread::exec() () at /lib64/libQt5Core.so.5
#7  0x7f3f33a271b5 in QQmlThreadPrivate::run() () at /lib64/libQt5Qml.so.5
#8  0x7f3f30636e18 in QThreadPrivate::start(void*) () at
/lib64/libQt5Core.so.5
#9  0x7f3f2ed6460a in start_thread () at /lib64/libpthread.so.0
#10 0x7f3f2fa30a4

[kde] [Bug 360444] New: Actually it's Version 4.14.2 ... Self Mutilating -- Self Destruct

[Robert via KDE Bugzilla]

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

Bug ID: 360444
   Summary: Actually it's Version 4.14.2 ... Self Mutilating --
Self Destruct
   Product: kde
   Version: 4.14.1
  Platform: Debian stable
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: unassigned-b...@kde.org
  Reporter: rjbrad...@gmail.com

2016.03.20
in Konsole as root for some apt - time updating and such... (Yes I know APT is
not a KDE program but just read this anyway to see if it is related.)

apt comes back with this absurdity from whence I wonder how it came to this
conclusion if not from KDE on a self destruct mission then where would apt be
getting this from and where then should I report this?:

# apt-get install wodim
Reading package lists... Done
Building dependency tree   
Reading state information... Done
wodim is already the newest version.
wodim set to manually installed.
"The following packages were automatically installed and are no longer
required:
  akregator apper apper-data ark cdrdao dns-root-data dnsmasq-base dragonplayer
dvd+rw-tools easy-rsa growisofs gwenview hyphen-en-us iputils-arping juk k3b
k3b-data k3b-i18n kamera kate kcalc
  kdeplasma-addons kdesudo kmix kopete kscreensaver ksnapshot kwalletmanager
libdebconf-kde0 libeventviews4 libgee-0.8-2 libk3b6 libk3b6-extracodecs
libkateinterfaces4 libkopete4
  liblistaller-glib0 libmbim-glib4 libmbim-proxy libmediastreamer-base3
libmm-glib0 libmodemmanagerqt1 libmsn0.3 libndp0 libnetworkmanagerqt1
libnm-glib-vpn1 libnm-glib4 libnm-util2 liboath0
  libopenconnect3 libortp9 libotr5 libpackagekitqt4-0 libpkcs11-helper1
libqapt-runtime libqapt1 libqmi-glib1 libqmi-proxy libqoauth1 libsrtp0
libstoken1 libteamdctl0 listaller
  mobile-broadband-provider-info modemmanager network-manager
network-manager-openvpn network-manager-pptp network-manager-vpnc openvpn
p7zip-full plasma-containments-addons
  plasma-dataengines-addons plasma-desktopthemes-artwork plasma-nm
plasma-runners-addons plasma-wallpapers-addons plasma-widget-lancelot
plasma-widget-networkmanagement plasma-widgets-addons
  pptp-linux python3-dbus python3-gi python3-pykde4 python3-software-properties
qapt-batch software-properties-common software-properties-kde sweeper
unattended-upgrades vcdimager vpnc
  vpnc-scripts
Use 'apt-get autoremove' to remove them."

Now that's a whole bunch of Kstuff and Plasma things that I really don't want
to remove  but my quick draw button pushing finger got the better of me and
Y'd them into oblivion anyway cuz it trusts Apt to be smart that way ya know.

I've Never in my 16 years of Linux-Life ever seen this bad package management
fluke in any distro and surely did not expect to see it pop up in Debian
(jessie).

So... KDE or not to KDE?

_
Continued...

# apt-get install dragonplayer dvd+rw-tools akregator apper apper-data ark
cdrdao gwenview hyphen-en-us iputils-arping juk k3b k3b-data kate kcalc kmix
kopete kscreensaver ksnapshot kwalletmanager
Reading package lists... Done
Building dependency tree   
Reading state information... Done
The following extra packages will be installed:
  growisofs kamera libdebconf-kde0 libgee-0.8-2 libk3b6 libk3b6-extracodecs
libkateinterfaces4 libkopete4 liblistaller-glib0 libmediastreamer-base3
libmsn0.3 libortp9 libotr5 libpackagekitqt4-0
  libqapt-runtime libqapt1 libsrtp0 listaller p7zip-full python3-dbus
python3-gi python3-pykde4 python3-software-properties qapt-batch
software-properties-common software-properties-kde
  unattended-upgrades vcdimager
Suggested packages:
  debconf-kde-helper rar cdrskin svgpart k3b-extrathemes k3b-i18n
normalize-audio movixmaker-2 kde-config-cddb kdeartwork-emoticons
kscreensaver-xsavers libotr5-bin srtp-utils p7zip-rar
  python-dbus-doc python3-dbus-dbg
The following NEW packages will be installed:
  akregator apper apper-data ark cdrdao dragonplayer dvd+rw-tools growisofs
gwenview hyphen-en-us iputils-arping juk k3b k3b-data kamera kate kcalc kmix
kopete kscreensaver ksnapshot
  kwalletmanager libdebconf-kde0 libgee-0.8-2 libk3b6 libk3b6-extracodecs
libkateinterfaces4 libkopete4 liblistaller-glib0 libmediastreamer-base3
libmsn0.3 libortp9 libotr5 libpackagekitqt4-0
  libqapt-runtime libqapt1 libsrtp0 listaller p7zip-full python3-dbus
python3-gi python3-pykde4 python3-software-properties qapt-batch
software-properties-common software-properties-kde
  unattended-upgrades vcdimager
0 upgraded, 48 newly installed, 0 to remove and 32 not upgraded.
Need to get 30.4 MB of archives.
After this operation, 104 MB of additional disk space will be used.
Do you want to continue? [Y/n] y



all good and installed -- now to try and reproduce it:
root@---:~# apt-get install wodim
Reading package lists... Done
Building dependency tree   
Reading state information... Done
wodim is already the n

[akregator] [Bug 352512] 5.0.xx after a crash, the restore session pops up twice then akregator crashes

[Robert via KDE Bugzilla]

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

Robert  changed:

   What|Removed |Added

 CC||alnila...@go2.pl

--- Comment #15 from Robert  ---
Run into that bug after upgrade to Kubuntu 15.10. Does anybody know the
solution? Fresh install?

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