[Skanlite] [Bug 370972] Scanned image is bad

[Marc via KDE Bugzilla]

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

--- Comment #6 from Marc  ---
Created attachment 101675
  --> https://bugs.kde.org/attachment.cgi?id=101675=edit
scan like specific option

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

[Skanlite] [Bug 370972] Scanned image is bad

[Marc via KDE Bugzilla]

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

--- Comment #5 from Marc  ---
Created attachment 101674
  --> https://bugs.kde.org/attachment.cgi?id=101674=edit
scan lite basic option

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

[Skanlite] [Bug 370972] Scanned image is bad

[Marc via KDE Bugzilla]

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

--- Comment #3 from Marc  ---
i use hp scanjet 3300c

get same result with grey or color mode

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

[Skanlite] [Bug 370972] Scanned image is bad

[Marc via KDE Bugzilla]

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

--- Comment #1 from Marc  ---
Created attachment 101593
  --> https://bugs.kde.org/attachment.cgi?id=101593=edit
scanned image with skanlite

scanned image with skanlite

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

[Skanlite] [Bug 370972] New: Scanned image is bad

[Marc via KDE Bugzilla]

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

Bug ID: 370972
   Summary: Scanned image is bad
   Product: Skanlite
   Version: unspecified
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kare.s...@iki.fi
  Reporter: marccollin7...@gmail.com

when i try to scan an image with skanlite, i get a very bad image.

if i pass by digikam or showfoto, image is ok.

Reproducible: Always

Steps to Reproduce:
1. start skanlite
2. scan image
3. save image

Actual Results:  
image is bad

Expected Results:  
scanned image should be ok

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

[digikam] [Bug 370958] Cannot save a scanned image

[Marc via KDE Bugzilla]

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

--- Comment #5 from Marc  ---
tried to put a value in filter but get same result.

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

[digikam] [Bug 370958] Cannot save a scanned image

[Marc via KDE Bugzilla]

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

--- Comment #4 from Marc  ---
Created attachment 101590
  --> https://bugs.kde.org/attachment.cgi?id=101590=edit
file dialog image

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

[digikam] [Bug 370958] Cannot save a scanned image

[Marc via KDE Bugzilla]

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

--- Comment #2 from Marc  ---
Created attachment 101588
  --> https://bugs.kde.org/attachment.cgi?id=101588=edit
image scanned with skanlite

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

[digikam] [Bug 370958] Cannot save a scanned image

[Marc via KDE Bugzilla]

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

--- Comment #1 from Marc  ---
strangely, if i pass directly by skanLite, i can save the image but the image
is not good

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

[digikam] [Bug 370958] New: Cannot save a scanned image

[Marc via KDE Bugzilla]

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

Bug ID: 370958
   Summary: Cannot save a scanned image
   Product: digikam
   Version: 5.2.0
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: digikam-de...@kde.org
  Reporter: marccollin7...@gmail.com

I try to import an image via the scann, i use the entry in the file entry menu.

After the image is scanner, i save the image but  i get an error: jpg image
format is not supported... same thing with png

Reproducible: Always

Steps to Reproduce:
1. click on import scanned image
2. scan image
3. save image

Actual Results:  
Error about the image format is not supported

Expected Results:  
Image shoud be saved

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

[kwin] [Bug 363224] Kwin crashes from time to time (this time using Virtual Machine Manager)

[marc via KDE Bugzilla]

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

--- Comment #20 from marc  ---
Actually, the issue does not come up with compositor turned off. 

Dnia czwartek, 13 października 2016 06:52:57 CEST piszesz:
> https://bugs.kde.org/show_bug.cgi?id=363224
> 
> Ronny Standtke  changed:
> 
>What|Removed |Added
> 
> CC||ronny.stand...@gmx.net
> 
> --- Comment #19 from Ronny Standtke  ---
> Created attachment 101553
>   --> https://bugs.kde.org/attachment.cgi?id=101553=edit
> my .xsession-errors file after the crash
> 
> I just installed Debian testing (64 Bit), selected KDE as desktop and run
> into exactly this bug. I used mostly VirtualBox and Synaptic in the
> sessions when the crash occurs. Attached is my .xsession-errors file from
> after the crash. I hope this helps somehow to find and fix the bug.

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

[plasmashell] [Bug 345563] Assert in QGLXContext::init when OpenGL drivers are not installed

[Marc via KDE Bugzilla]

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

Marc  changed:

   What|Removed |Added

 CC|macattack...@gmail.com  |

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

[digikam] [Bug 370245] Be able to rename tags which have been setted in pictures

[Marc via KDE Bugzilla]

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

--- Comment #5 from Marc  ---
Hello,
Thanks you for your feedback. I didn't know this possibility.
So this feature request is not required anymore.

But I agree with Andrew: if we don't know the appropriate process, we can think
this feature does not exists.
It could be easier to save tag in picture automatically, (after a confirm), or
provide a configuration option which allow to enable this feature.

Anyway, thanks for your feedback.

Regards

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

[digikam] [Bug 370245] Be able to rename tags which have been setted in pictures

[Marc via KDE Bugzilla]

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

--- Comment #2 from Marc  ---
Yes, we are unable to rename tags but it does not also apply the update into
the picture:
- set a people tag in a picture called "Jon Doe".
- exitool picture.CR2 display "Jon Doe"
- rename from Digikam "Jon Doe" into "John Doe"
- exiftool picture.CR2 still display "Jon Doe"

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

[digikam] [Bug 370245] New: Be able to rename tags which have been setted in pictures

[Marc via KDE Bugzilla]

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

Bug ID: 370245
   Summary: Be able to rename tags which have been setted in
pictures
   Product: digikam
   Version: 5.2.0
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: wishlist
  Priority: NOR
 Component: Tags
  Assignee: digikam-de...@kde.org
  Reporter: erme...@gmail.com

Rename tags in file could help us to earn many time:
For example fixing a typo error in a person tag, or reorder the locations tags
defined in a picture to another picture.

Reproducible: Always

Steps to Reproduce:
1.Seek people into pictures
2.Set a name for each identified face with sometimes adding a typo in the
person's name

Actual Results:  
To fix the typo error, you need to:
- create the appropriate person tag
- browse all pictures where this person is identified, and replace the
identification tag by the appropriate one.


Expected Results:  
- from the tags directory tree, be able to rename the tag. After renaming, all
pictures with the tag which contains the typo error contains now the new tag
content.

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

[digikam] [Bug 370245] Be able to rename tags which have been setted in pictures

[Marc via KDE Bugzilla]

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

Marc  changed:

   What|Removed |Added

 CC||erme...@gmail.com

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

[digikam] [Bug 369668] EXIF orientation tag is not the same after a RAW export in JPEG

[Marc via KDE Bugzilla]

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

--- Comment #4 from Marc  ---
Created attachment 101388
  --> https://bugs.kde.org/attachment.cgi?id=101388=edit
Screenshot of the rotation configuration used

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

[digikam] [Bug 369668] EXIF orientation tag is not the same after a RAW export in JPEG

[Marc via KDE Bugzilla]

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

--- Comment #3 from Marc  ---
Created attachment 101387
  --> https://bugs.kde.org/attachment.cgi?id=101387=edit
Screenshot of the orientation tag available in the generated JPG, which differ
from the CR2 orientation tag

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

[digikam] [Bug 369668] EXIF orientation tag is not the same after a RAW export in JPEG

[Marc via KDE Bugzilla]

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

--- Comment #2 from Marc  ---
Created attachment 101386
  --> https://bugs.kde.org/attachment.cgi?id=101386=edit
Screenshot of the orientation tag available in the CR2 file used to generate
the JPG file

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

[digikam] [Bug 369668] EXIF orientation tag is not the same after a RAW export in JPEG

[Marc via KDE Bugzilla]

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

--- Comment #1 from Marc  ---
Created attachment 101385
  --> https://bugs.kde.org/attachment.cgi?id=101385=edit
The queue process which have been launched to generate the JPG from CR2 file

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

[digikam] [Bug 369668] New: EXIF orientation tag is not the same after a RAW export in JPEG

[Marc via KDE Bugzilla]

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

Bug ID: 369668
   Summary: EXIF orientation tag is not the same after a RAW
export in JPEG
   Product: digikam
   Version: 5.2.0
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: major
  Priority: NOR
 Component: BatchQueueManager-Tool-Convert
  Assignee: digikam-de...@kde.org
  Reporter: erme...@gmail.com

After an export to google photos, pictures in a portrait orientation are not
well oriented when they are coming from a RAW (CR2) file.


Reproducible: Always

Steps to Reproduce:
1.Select a CR2 picture with an portrait orientation.
2.Process to export this file in a google photo folder with the following
parameters: 72dpi, max size 2048px, split tags.

Actual Results:  
generated JPG is google photos not well oriented.

Expected Results:  
generated JPG would have the same orientation than the picture in digikam.

Perhaps this is the batch queue manager which is responsible of that:
- Select the same pictures: orientation exif tag is setted as right,top.
- Create a new batch queue process where we select in the configuration center
"Convert > Convert in JPG"
- process the queue.
- generated JPG have an exif tag setted to top,left.

This problem does not seem to appear when we process jpg pictures.

Configuration setted for digikam is in "Configure Digikam > Metadatas >
Rotation":
- Rotate when setting an flag only
- Write a flag if possible
- Display the pictures and thumbnails according with the orientation flag
Others options are unchecked.

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

[digikam] [Bug 355861] Sort images by lens model

[Marc via KDE Bugzilla]

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

Marc  changed:

   What|Removed |Added

 CC||erme...@gmail.com

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

[digikam] [Bug 355838] Sort images by orientation mode

[Marc via KDE Bugzilla]

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

Marc  changed:

   What|Removed |Added

 CC||erme...@gmail.com

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

[digikam] [Bug 350098] Sort images on photograph specific metadata

[Marc via KDE Bugzilla]

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

Marc  changed:

   What|Removed |Added

 CC||erme...@gmail.com

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

[digikam] [Bug 326404] Unable to select picture in map search view

[Marc via KDE Bugzilla]

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

Marc  changed:

   What|Removed |Added

 CC||erme...@gmail.com

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

[calligrasheets] [Bug 368020] New: Calligra sheets crashes when using text to columns

[Marc via KDE Bugzilla]

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

Bug ID: 368020
   Summary: Calligra sheets crashes when using text to columns
   Product: calligrasheets
   Version: 2.9.11
  Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: calligra-sheets-bugs-n...@kde.org
  Reporter: mrcm...@aim.com

Application: calligrasheets (2.9.11)
KDE Platform Version: 4.14.22
Qt Version: 4.8.7
Operating System: Linux 4.6.7-300.fc24.x86_64 x86_64
Distribution: "Fedora release 24 (Twenty Four)"

-- Information about the crash:
- What I was doing when the application crashed:
I was converting several rows of text into columns using a dash as column
delimiter in the text field when Calligra sheets crashed.  I tried to do the
same operation two more times with different files and I get the same result.

The crash can be reproduced every time.

-- Backtrace:
Application: Calligra Sheets (calligrasheets), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[KCrash Handler]
#6  0x7f11a31817f6 in
QSharedDataPointer::detach_helper()
(this=0x31) at /usr/include/QtCore/qatomic_x86_64.h:121
#7  0x7f11a31817f6 in
QSharedDataPointer::detach_helper()
(other=..., this=0x55a7d96deb18) at /usr/include/QtCore/qhash.h:282
#8  0x7f11a31817f6 in
QSharedDataPointer::detach_helper()
(this=0x55a7d96deb10) at /usr/src/debug/calligra-2.9.11/sheets/Style.cpp:147
#9  0x7f11a31817f6 in
QSharedDataPointer::detach_helper()
(this=0x7ffe590789e8) at /usr/include/QtCore/qshareddata.h:227
#10 0x7f11a31817f6 in
QSharedDataPointer::detach_helper()
(this=this@entry=0x7ffe590789e8) at /usr/include/QtCore/qshareddata.h:233
#11 0x7f11a317143a in
Calligra::Sheets::Style::releaseSubStyle(Calligra::Sheets::Style::Key)
(this=0x7ffe590789e8) at /usr/include/QtCore/qshareddata.h:75
#12 0x7f11a317143a in
Calligra::Sheets::Style::releaseSubStyle(Calligra::Sheets::Style::Key)
(this=0x7ffe590789e8) at /usr/include/QtCore/qshareddata.h:78
#13 0x7f11a317143a in
Calligra::Sheets::Style::releaseSubStyle(Calligra::Sheets::Style::Key)
(this=this@entry=0x7ffe590789e0, key=) at
/usr/src/debug/calligra-2.9.11/sheets/Style.cpp:2705
#14 0x7f11a31714d3 in
Calligra::Sheets::Style::insertSubStyle(Calligra::Sheets::SharedSubStyle
const&) (this=this@entry=0x7ffe590789e0, subStyle=...) at
/usr/src/debug/calligra-2.9.11/sheets/Style.cpp:2699
#15 0x7f11a31951d8 in
Calligra::Sheets::StyleStorage::composeStyle(QList
const&) const (this=this@entry=0x55a7d86c37b0, subStyles=...) at
/usr/src/debug/calligra-2.9.11/sheets/StyleStorage.cpp:925
#16 0x7f11a319571e in Calligra::Sheets::StyleStorage::contains(QPoint
const&) const (this=0x55a7d86c37b0, point=...) at
/usr/src/debug/calligra-2.9.11/sheets/StyleStorage.cpp:246
#17 0x7f11a307e4cf in Calligra::Sheets::CellStorage::style(int, int) const
(this=, column=column@entry=2, row=row@entry=12) at
/usr/src/debug/calligra-2.9.11/sheets/CellStorage.cpp:546
#18 0x7f11a30696cf in Calligra::Sheets::Cell::style() const
(this=this@entry=0x7ffe59078b40) at
/usr/src/debug/calligra-2.9.11/sheets/Cell.cpp:346
#19 0x7f11a362f8f0 in
Calligra::Sheets::CellView::CellView(Calligra::Sheets::SheetView*, int, int)
(this=0x55a7d95f2b20, sheetView=0x55a7d920f3d0, col=2, row=12) at
/usr/src/debug/calligra-2.9.11/sheets/ui/CellView.cpp:201
#20 0x7f11a3640801 in Calligra::Sheets::SheetView::createCellView(int, int)
(this=0x55a7d920f3d0, col=2, row=12) at
/usr/src/debug/calligra-2.9.11/sheets/ui/SheetView.cpp:681
#21 0x7f11a36418c3 in Calligra::Sheets::SheetView::cellView(int, int)
(this=0x55a7d920f3d0, col=2, row=12) at
/usr/src/debug/calligra-2.9.11/sheets/ui/SheetView.cpp:244
#22 0x7f11a3641ece in
Calligra::Sheets::SheetView::Private::cellViewToProcess(Calligra::Sheets::Cell&,
QPointF&, QSet&, Calligra::Sheets::SheetView*, QRect
const&) (this=0x55a7d9212400, cell=..., coordinate=...,
processedObscuredCells=..., sheetView=sheetView@entry=0x55a7d920f3d0,
visRect=...) at /usr/src/debug/calligra-2.9.11/sheets/ui/SheetView.cpp:149
#23 0x7f11a3643c32 in Calligra::Sheets::SheetView::paintCells(QPainter&,
QRectF const&, QPointF const&, Calligra::Sheets::CanvasBase*, QRect const&)
(this=, painter=..., paintRect=..., topLeft=...,
visibleRect=...) at /usr/src/debug/calligra-2.9.11/sheets/ui/SheetView.cpp:383
#24 0x7f11a35bc5ba in Calligra::Sheets::CanvasBase::paint(QPainter*, QRectF
const&) (this=this@entry=0x55a7d830d978, painter=painter@entry=0x7ffe59079000,
painterRect=...) at
/usr/src/debug/calligra-2.9.11/sheets/part/CanvasBase.cpp:475
#25 0x7f11a35bdf9c in Calligra::Sheets::Canvas::paintEvent(QPaintEvent*)
(this=0x55a7d830d950, event=0x7ffe59079490) at
/usr/src/debug/calligra-2.9.11/sheets/part/Canvas.cpp:316
#26 0x7f11be883720 in QWidget::event(QEvent*) 

[krita] [Bug 365966] no cursor is visable, action is not shown.

[Marc via KDE Bugzilla]

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

--- Comment #4 from Marc  ---
Thanks for sending these updates on owto resolve the reported issue.
I will take time to test the suggestions shortly!!

yours sincerely,

To: "dhr m ober" 
Sent: Wednesday, 17 August, 2016 10:17:57 AM
Subject: [krita] [Bug 365966] no cursor is visable, action is not shown.

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

Boudewijn Rempt  changed:

   What|Removed |Added

 CC||alecdr...@yahoo.com

--- Comment #3 from Boudewijn Rempt  ---
*** Bug 367061 has been marked as a duplicate of this bug. ***

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

[krita] [Bug 365966] New: no cursor is visable, action is not shown.

[Marc via KDE Bugzilla]

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

Bug ID: 365966
   Summary: no cursor is visable, action is not shown.
   Product: krita
   Version: 3.0
  Platform: MS Windows
OS: MS Windows
Status: UNCONFIRMED
  Severity: grave
  Priority: NOR
 Component: Vector Objects and Tools
  Assignee: krita-bugs-n...@kde.org
  Reporter: dhr_m.o...@online.nl

as soon as I go over the field where the drawing is shown, the cursor or tool
or whatever selected disappears. there is no action visable what I do untill
the next action.
As yo can understand its unworkable this way. to bad!
working with windows 10 btw

Reproducible: Always

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

[kwin] [Bug 363224] Kwin crashes from time to time (this time using Virtual Machine Manager)

[marc via KDE Bugzilla]

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

--- Comment #8 from marc  ---
>>> run "kcmshell5 desktop" and disable the indication in the second tab <<<

I've had this already disabled when the crash occured.

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

[kwin] [Bug 364944] New: KWin crashes when "Edit machine / general preferences" window is closed. | VirtualBox QT interface

[marc via KDE Bugzilla]

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

Bug ID: 364944
   Summary: KWin crashes when "Edit machine / general preferences"
window is closed. | VirtualBox QT interface
   Product: kwin
   Version: 5.6.4
  Platform: Debian testing
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kwin-bugs-n...@kde.org
  Reporter: marc_sm...@gmx.com

Application: kwin_x11 (5.6.4)

Qt Version: 5.6.1
Frameworks Version: 5.23.0
Operating System: Linux 4.6.0-1-amd64 x86_64
Distribution: Debian GNU/Linux testing (stretch)

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

Editing preferences in VirtualBox for virtual machine, and then for VirtualBox
itself

- Custom settings of the application:

Most default KWin effects disabled

The crash can be reproduced every time.

-- Backtrace:
Application: KWin (kwin_x11), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f29741ba940 (LWP 13350))]

Thread 6 (Thread 0x7f293b7fe700 (LWP 13365)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f29713cc574 in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5Script.so.5
#2  0x7f29713cc5b9 in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5Script.so.5
#3  0x7f296d97d464 in start_thread (arg=0x7f293b7fe700) at
pthread_create.c:334
#4  0x7f2973cc5e5d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 5 (Thread 0x7f294677b700 (LWP 13363)):
#0  0x7f2973cbeb83 in select () at ../sysdeps/unix/syscall-template.S:84
#1  0x7f2972478a1f in qt_safe_select(int, fd_set*, fd_set*, fd_set*,
timespec const*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#2  0x7f297247a45e in
QEventDispatcherUNIXPrivate::doSelect(QFlags,
timespec*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#3  0x7f297247a972 in
QEventDispatcherUNIX::processEvents(QFlags) ()
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7f2972425e4a in
QEventLoop::exec(QFlags) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7f297224e9e4 in QThread::exec() () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7f296c8da405 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5
#7  0x7f2972253808 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x7f296d97d464 in start_thread (arg=0x7f294677b700) at
pthread_create.c:334
#9  0x7f2973cc5e5d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 4 (Thread 0x7f2953765700 (LWP 13362)):
#0  0x7f2973cbeb83 in select () at ../sysdeps/unix/syscall-template.S:84
#1  0x7f2972478a1f in qt_safe_select(int, fd_set*, fd_set*, fd_set*,
timespec const*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#2  0x7f297247a45e in
QEventDispatcherUNIXPrivate::doSelect(QFlags,
timespec*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#3  0x7f297247a972 in
QEventDispatcherUNIX::processEvents(QFlags) ()
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7f2972425e4a in
QEventLoop::exec(QFlags) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7f297224e9e4 in QThread::exec() () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7f296c8da405 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5
#7  0x7f2972253808 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x7f296d97d464 in start_thread (arg=0x7f2953765700) at
pthread_create.c:334
#9  0x7f2973cc5e5d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 3 (Thread 0x7f2959e7a700 (LWP 13355)):
#0  0x7f2973cbeb83 in select () at ../sysdeps/unix/syscall-template.S:84
#1  0x7f2972478a1f in qt_safe_select(int, fd_set*, fd_set*, fd_set*,
timespec const*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#2  0x7f297247a45e in
QEventDispatcherUNIXPrivate::doSelect(QFlags,
timespec*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#3  0x7f297247a972 in
QEventDispatcherUNIX::processEvents(QFlags) ()
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7f2972425e4a in
QEventLoop::exec(QFlags) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7f297224e9e4 in QThread::exec() () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7f29742de515 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5
#7  0x7f2972253808 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x7f296d97d464 in start_thread (arg=0x7f2959e7a700) at
pthread_create.c:334
#9  0x7f2973cc5e5d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 2 (Thread 0x7f295b9c2700 (LWP 13353)):
#0  0x7f2973cbcdcd in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7f2971f8e382 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1
#2  

[krita] [Bug 363965] Krita crashes when touching pen to tablet using Adesso CyberTablet M14

[Marc via KDE Bugzilla]

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

--- Comment #2 from Marc  ---
No, but I will test. Where are the 3.0 release builds located? 

Uninstalling and trying this one - krita-3.0-9e17aff-x64.zip (it is from the
link you sent). It works just fine with that release! Thank you!! 

So, am I missing out on any features with that version? Is there anyway for you
guys to patch the version that most folks use?

Sorry but it is relevant. One of my first questions when troubleshooting this
issue would be to ask "How do you know the tablet works? Have you tried the
tablet with a different software program?" That's why I am letting you know
that the tablet works.

I got the driver from the adesso site -
http://www.adesso.com/download/download-list-4.html

Thank you!!

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

[krita] [Bug 363965] Krita crashes when touching pen to tablet using Adesso CyberTablet M14

[Marc via KDE Bugzilla]

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

Marc  changed:

   What|Removed |Added

 CC||marcbri...@gmail.com

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

[krita] [Bug 363965] New: Krita crashes when touching pen to tablet using Adesso CyberTablet M14

[Marc via KDE Bugzilla]

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

Bug ID: 363965
   Summary: Krita crashes when touching pen to tablet using Adesso
CyberTablet M14
   Product: krita
   Version: 3.0
  Platform: MS Windows
OS: MS Windows
Status: UNCONFIRMED
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: krita-bugs-n...@kde.org
  Reporter: marcbri...@gmail.com

Krita works fine until I touch the pen to the tablet to start drawing.

Have used Paint Tool Sai for quite awhile now with the same tablet, works fine.



Reproducible: Always

Steps to Reproduce:
1. Start Krita
2. Touch tablet with pen
3. Crashes everytime

Actual Results:  
I reported the issue.

Expected Results:  
It should work.

Using Windows 10 64-bit.

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

[plasmashell] [Bug 363142] New: Plasma crashes when attaching an external monitor

[Marc via KDE Bugzilla]

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

Bug ID: 363142
   Summary: Plasma crashes when attaching an external monitor
   Product: plasmashell
   Version: 5.4.3
  Platform: Debian testing
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: mrcm...@aim.com
CC: bhus...@gmail.com, plasma-b...@kde.org

Application: plasmashell (5.4.3)

Qt Version: 5.5.1
Operating System: Linux 4.5.0-2-amd64 x86_64
Distribution: Debian GNU/Linux testing (stretch)

-- Information about the crash:
- Unusual behavior I noticed:

When attaching an external monitor, my laptod screen (Thinkpad X1 Carbon) goes
black and does not show menus when clicking on it.

The crash can be reproduced every time.

-- 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 0x7f338bb59940 (LWP 2105))]

Thread 9 (Thread 0x7f3376b8d700 (LWP 2111)):
#0  0x7f3386292e5d in poll () from /lib/x86_64-linux-gnu/libc.so.6
#1  0x7f338a34a382 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1
#2  0x7f338a34bff7 in xcb_wait_for_event () from
/usr/lib/x86_64-linux-gnu/libxcb.so.1
#3  0x7f3377e84789 in QXcbEventReader::run (this=0x25f7af0) at
qxcbconnection.cpp:1230
#4  0x7f338697c7fe in QThreadPrivate::start (arg=0x25f7af0) at
thread/qthread_unix.cpp:331
#5  0x7f3385a9b454 in start_thread () from
/lib/x86_64-linux-gnu/libpthread.so.0
#6  0x7f338629beed in clone () from /lib/x86_64-linux-gnu/libc.so.6

Thread 8 (Thread 0x7f336700 (LWP 2126)):
#0  0x7f338303b382 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#1  0x7f330001 in ?? ()
#2  0x02621d40 in ?? ()
#3  0x7f3368002e70 in ?? ()
#4  0x in ?? ()

Thread 7 (Thread 0x7f3366b78700 (LWP 2153)):
#0  0x7f3386292e5d in poll () from /lib/x86_64-linux-gnu/libc.so.6
#1  0x7f338303e32c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f338303e43c in g_main_context_pending () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f3386bb3a5b in QEventDispatcherGlib::processEvents
(this=0x7f3368c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420
#4  0x7f3386b5ad6a in QEventLoop::exec (this=this@entry=0x7f3366b77c60,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#5  0x7f3386977854 in QThread::exec (this=) at
thread/qthread.cpp:503
#6  0x7f338920a105 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5
#7  0x7f338697c7fe in QThreadPrivate::start (arg=0x2a68020) at
thread/qthread_unix.cpp:331
#8  0x7f3385a9b454 in start_thread () from
/lib/x86_64-linux-gnu/libpthread.so.0
#9  0x7f338629beed in clone () from /lib/x86_64-linux-gnu/libc.so.6

Thread 6 (Thread 0x7f3364a23700 (LWP 2262)):
#0  0x7f3383082a90 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#1  0x7f338303d8b0 in g_main_context_prepare () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f338303e25b in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f338303e43c in g_main_context_pending () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7f3386bb3a5b in QEventDispatcherGlib::processEvents
(this=0x7f33580008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420
#5  0x7f3386b5ad6a in QEventLoop::exec (this=this@entry=0x7f3364a22c60,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#6  0x7f3386977854 in QThread::exec (this=) at
thread/qthread.cpp:503
#7  0x7f338920a105 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5
#8  0x7f338697c7fe in QThreadPrivate::start (arg=0x2b5d9c0) at
thread/qthread_unix.cpp:331
#9  0x7f3385a9b454 in start_thread () from
/lib/x86_64-linux-gnu/libpthread.so.0
#10 0x7f338629beed in clone () from /lib/x86_64-linux-gnu/libc.so.6

Thread 5 (Thread 0x7f335efbd700 (LWP 2275)):
#0  0x7f3385aa104f in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib/x86_64-linux-gnu/libpthread.so.0
#1  0x7f338b5b71c4 in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5Script.so.5
#2  0x7f338b5b7209 in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5Script.so.5
#3  0x7f3385a9b454 in start_thread () from
/lib/x86_64-linux-gnu/libpthread.so.0
#4  0x7f338629beed in clone () from /lib/x86_64-linux-gnu/libc.so.6

Thread 4 (Thread 0x7f32d7fff700 (LWP 2317)):
#0  0x7f338303d771 in g_main_context_wait () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#1  0x in ?? ()

Thread 3 (Thread 0x7f32c7842700 (LWP 2588)):
#0  0x7f3386bb19d2 in QTimerInfoList::repairTimersIfNeeded
(this=0x7f32c0002cd0) at kernel/qtimerinfo_unix.cpp:154
#1  0x7f3386bb1a63 in QTimerInfoList::timerWait (this=0x7f32c0002cd0,
tm=...) at kernel/qtimerinfo_unix.cpp:382
#2  0x7f3386bb338c in 

[akregator] [Bug 361847] Akregator always crashes when selecting an article on fok.nl

[Marc via KDE Bugzilla]

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

--- Comment #2 from Marc  ---
With Version 5.2.45 pre (QtWebEngine) it no longer crashes :)

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

[akregator] [Bug 361847] New: Akregator always crashes when selecting an article on fok.nl

[Marc via KDE Bugzilla]

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

Bug ID: 361847
   Summary: Akregator always crashes when selecting an article on
fok.nl
   Product: akregator
   Version: unspecified
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdepim-b...@kde.org
  Reporter: cyberbob1...@gmail.com

Application: akregator (4.14.10)
KDE Platform Version: 4.14.18
Qt Version: 4.8.6
Operating System: Linux 4.1.20-11-default x86_64
Distribution: "openSUSE Leap 42.1 (x86_64)"

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

When I select an article on ( http://rss.fok.nl/feeds/nieuws ), akregator
always crashes

OpenSUSE 42.1 64 bits
Akregator: 4.14.10
KDE Development Platform 4.14.18

The crash can be reproduced every time.

-- Backtrace:
Application: Akregator (akregator), signal: Floating point exception
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f7acdde6800 (LWP 2382))]

Thread 8 (Thread 0x7f7aa528a700 (LWP 7957)):
#0  0x7f7ac5fca03f in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f7aae60deb6 in WTF::TCMalloc_PageHeap::scavengerThread() () at
/usr/lib64/libQtWebKit.so.4
#2  0x7f7aae60dee9 in  () at /usr/lib64/libQtWebKit.so.4
#3  0x7f7ac5fc60a4 in start_thread () at /lib64/libpthread.so.0
#4  0x7f7aca8e0fed in clone () at /lib64/libc.so.6

Thread 7 (Thread 0x7f7a9fbe5700 (LWP 7958)):
#0  0x7f7ac51eccf0 in g_mutex_lock () at /usr/lib64/libglib-2.0.so.0
#1  0x7f7ac51aa4b9 in g_main_context_prepare () at
/usr/lib64/libglib-2.0.so.0
#2  0x7f7ac51aad80 in  () at /usr/lib64/libglib-2.0.so.0
#3  0x7f7ac51aaf7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#4  0x7f7acc229fde in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQtCore.so.4
#5  0x7f7acc1fbd4f in
QEventLoop::processEvents(QFlags) () at
/usr/lib64/libQtCore.so.4
#6  0x7f7acc1fc045 in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQtCore.so.4
#7  0x7f7acc0f94df in QThread::exec() () at /usr/lib64/libQtCore.so.4
#8  0x7f7acc0fbbbf in  () at /usr/lib64/libQtCore.so.4
#9  0x7f7ac5fc60a4 in start_thread () at /lib64/libpthread.so.0
#10 0x7f7aca8e0fed in clone () at /lib64/libc.so.6

Thread 6 (Thread 0x7f7a9ed64700 (LWP 7959)):
#0  0x7f7ac5fca03f in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f7aae380b3d in JSC::BlockAllocator::blockFreeingThreadMain() () at
/usr/lib64/libQtWebKit.so.4
#2  0x7f7aae635a06 in WTF::wtfThreadEntryPoint(void*) () at
/usr/lib64/libQtWebKit.so.4
#3  0x7f7ac5fc60a4 in start_thread () at /lib64/libpthread.so.0
#4  0x7f7aca8e0fed in clone () at /lib64/libc.so.6

Thread 5 (Thread 0x7f7a56d66700 (LWP 7988)):
#0  0x7f7ac5fca03f in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f7a56dcdd79 in  () at
/usr/lib64/java-1_8_0-openjdk-plugin/lib/IcedTeaPlugin.so
#2  0x7f7a56dce819 in  () at
/usr/lib64/java-1_8_0-openjdk-plugin/lib/IcedTeaPlugin.so
#3  0x7f7ac5fc60a4 in start_thread () at /lib64/libpthread.so.0
#4  0x7f7aca8e0fed in clone () at /lib64/libc.so.6

Thread 4 (Thread 0x7f7a55bc7700 (LWP 7989)):
#0  0x7f7ac5fca03f in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f7a56dcdd79 in  () at
/usr/lib64/java-1_8_0-openjdk-plugin/lib/IcedTeaPlugin.so
#2  0x7f7a56dce819 in  () at
/usr/lib64/java-1_8_0-openjdk-plugin/lib/IcedTeaPlugin.so
#3  0x7f7ac5fc60a4 in start_thread () at /lib64/libpthread.so.0
#4  0x7f7aca8e0fed in clone () at /lib64/libc.so.6

Thread 3 (Thread 0x7f7a553c6700 (LWP 7990)):
#0  0x7f7ac5fca03f in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f7a56dcdd79 in  () at
/usr/lib64/java-1_8_0-openjdk-plugin/lib/IcedTeaPlugin.so
#2  0x7f7a56dce819 in  () at
/usr/lib64/java-1_8_0-openjdk-plugin/lib/IcedTeaPlugin.so
#3  0x7f7ac5fc60a4 in start_thread () at /lib64/libpthread.so.0
#4  0x7f7aca8e0fed in clone () at /lib64/libc.so.6

Thread 2 (Thread 0x7f7a3391f700 (LWP 7996)):
#0  0x7f7aca8dcf79 in syscall () at /lib64/libc.so.6
#1  0x7f7ac51ecf3e in g_cond_wait_until () at /usr/lib64/libglib-2.0.so.0
#2  0x7f7ac5180dc1 in  () at /usr/lib64/libglib-2.0.so.0
#3  0x7f7ac518134b in g_async_queue_timeout_pop () at
/usr/lib64/libglib-2.0.so.0
#4  0x7f7a397b8777 in  () at
/usr/lib64/browser-plugins/libfreshwrapper-flashplayer.so
#5  0x7f7a397a595c in  () at
/usr/lib64/browser-plugins/libfreshwrapper-flashplayer.so
#6  0x7f7ac5fc60a4 in start_thread () at /lib64/libpthread.so.0
#7  0x7f7aca8e0fed in clone () at /lib64/libc.so.6

Thread 1 (Thread 0x7f7acdde6800 (LWP 2382)):
[KCrash Handler]
#6  0x7f7a31a5755a in  () at 

[amarok] [Bug 360866] Alphabetic Characters are not allowed in track number field

[Marc via KDE Bugzilla]

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

--- Comment #2 from Marc  ---
Thank you.

In a future release can another field be added that can be used for LP track
numbers?

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

[amarok] [Bug 360866] New: Alphabetic Characters are not allowed in track number field

[Marc via KDE Bugzilla]

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

Bug ID: 360866
   Summary: Alphabetic Characters are not allowed in track number
field
   Product: amarok
   Version: unspecified
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: critical
  Priority: NOR
 Component: general
  Assignee: amarok-bugs-d...@kde.org
  Reporter: marcerick...@gmail.com

Alphabetic characters aren't allowed in the track number field.  There are
billions of vinyl LPs still existing in the world and any song from an LP
cannot be listed properly while this bug exists.

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

[plasmashell] [Bug 359937] New: plasma crashes

[Marc via KDE Bugzilla]

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

Bug ID: 359937
   Summary: plasma crashes
   Product: plasmashell
   Version: 5.4.3
  Platform: Debian stable
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: mrcm...@aim.com
CC: bhus...@gmail.com, plasma-b...@kde.org

Application: plasmashell (5.4.3)

Qt Version: 5.5.1
Operating System: Linux 4.3.0-1-amd64 x86_64
Distribution: Debian GNU/Linux 7.9 (wheezy)

-- Information about the crash:
- What I was doing when the application crashed:
Connecting an external monitor

- Unusual behavior I noticed:
Laptop screen did not show wallpaper adn right click on Desktop did not show
any menu. Eventually the panel disapears and later on plasma crashes.  After
plasma restarts, everything works fine.
- Custom settings of the application:

The crash can be reproduced sometimes.

-- 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 0x7f22373dc940 (LWP 17178))]

Thread 10 (Thread 0x7f459700 (LWP 17180)):
#0  0x7f2231b2bb6d in poll () at ../sysdeps/unix/syscall-template.S:81
#1  0x7f2235be0382 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1
#2  0x7f2235be1ff7 in xcb_wait_for_event () from
/usr/lib/x86_64-linux-gnu/libxcb.so.1
#3  0x7f222374f5b9 in QXcbEventReader::run (this=0x1e5fb00) at
qxcbconnection.cpp:1230
#4  0x7f223221088e in QThreadPrivate::start (arg=0x1e5fb00) at
thread/qthread_unix.cpp:331
#5  0x7f223132d284 in start_thread (arg=0x7f459700) at
pthread_create.c:333
#6  0x7f2231b34a4d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 9 (Thread 0x7f221bbe2700 (LWP 17199)):
#0  0x7f2231b2bb6d in poll () at ../sysdeps/unix/syscall-template.S:81
#1  0x7f222e8d31cc in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f222e8d32dc in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f22324482db in QEventDispatcherGlib::processEvents
(this=0x7f22140008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420
#4  0x7f22323ef2ea in QEventLoop::exec (this=this@entry=0x7f221bbe1c60,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#5  0x7f223220b8d4 in QThread::exec (this=) at
thread/qthread.cpp:503
#6  0x7f2234aa0105 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5
#7  0x7f223221088e in QThreadPrivate::start (arg=0x1f3d6a0) at
thread/qthread_unix.cpp:331
#8  0x7f223132d284 in start_thread (arg=0x7f221bbe2700) at
pthread_create.c:333
#9  0x7f2231b34a4d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 8 (Thread 0x7f2212415700 (LWP 17241)):
#0  socketNotifierSourceCheck (source=0x7f220c002c00) at
kernel/qeventdispatcher_glib.cpp:70
#1  0x7f222e8d2c01 in g_main_context_check () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f222e8d3170 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f222e8d32dc in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7f22324482db in QEventDispatcherGlib::processEvents
(this=0x7f220c0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420
#5  0x7f22323ef2ea in QEventLoop::exec (this=this@entry=0x7f2212414c60,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#6  0x7f223220b8d4 in QThread::exec (this=) at
thread/qthread.cpp:503
#7  0x7f2234aa0105 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5
#8  0x7f223221088e in QThreadPrivate::start (arg=0x22acc30) at
thread/qthread_unix.cpp:331
#9  0x7f223132d284 in start_thread (arg=0x7f2212415700) at
pthread_create.c:333
#10 0x7f2231b34a4d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 7 (Thread 0x7f220bfff700 (LWP 17672)):
#0  0x7f2231b2bb6d in poll () at ../sysdeps/unix/syscall-template.S:81
#1  0x7f222e8d31cc in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f222e8d32dc in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f22324482db in QEventDispatcherGlib::processEvents
(this=0x7f22040008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420
#4  0x7f22323ef2ea in QEventLoop::exec (this=this@entry=0x7f220bffec60,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#5  0x7f223220b8d4 in QThread::exec (this=) at
thread/qthread.cpp:503
#6  0x7f2234aa0105 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5
#7  0x7f223221088e in QThreadPrivate::start (arg=0x2327460) at
thread/qthread_unix.cpp:331
#8  0x7f223132d284 in start_thread (arg=0x7f220bfff700) at
pthread_create.c:333
#9  0x7f2231b34a4d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 6 (Thread 0x7f220a7bc700 

[plasmashell] [Bug 359908] New: Crashed twice trying to configure yahoo and gmail accounts

[Marc via KDE Bugzilla]

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

Bug ID: 359908
   Summary: Crashed twice trying to configure yahoo and gmail
accounts
   Product: plasmashell
   Version: 5.4.2
  Platform: Compiled Sources
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: detox_grou...@yahoo.com
CC: bhus...@gmail.com, plasma-b...@kde.org

Application: plasmashell (5.4.2)
 (Compiled from sources)
Qt Version: 5.4.2
Operating System: Linux 4.2.0-30-generic x86_64
Distribution: Ubuntu 15.10

-- Information about the crash:
I was just trying to change settings and as soon as I clicked on the option the
messenger crashed, happens every time I attempt same process.

The crash can be reproduced sometimes.

-- 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 0x7fb4de938800 (LWP 7360))]

Thread 9 (Thread 0x7fb4c9f94700 (LWP 7362)):
#0  0x7fb4d90e188d in poll () at ../sysdeps/unix/syscall-template.S:81
#1  0x7fb4dd128bd2 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1
#2  0x7fb4dd12a74f in xcb_wait_for_event () from
/usr/lib/x86_64-linux-gnu/libxcb.so.1
#3  0x7fb4cc2dea39 in ?? () from
/usr/lib/x86_64-linux-gnu/qt5/plugins/platforms/libqxcb.so
#4  0x7fb4d97d42be in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7fb4d88c36aa in start_thread (arg=0x7fb4c9f94700) at
pthread_create.c:333
#6  0x7fb4d90ece9d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 8 (Thread 0x7fb4c35ef700 (LWP 7366)):
#0  0x7fb4d5e8d791 in g_main_context_prepare () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#1  0x7fb4d5e8e11b in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7fb4d5e8e2fc in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7fb4d9a0b29b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7fb4d99b175a in
QEventLoop::exec(QFlags) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7fb4d97cf3d4 in QThread::exec() () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7fb4dbff7f85 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5
#7  0x7fb4d97d42be in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x7fb4d88c36aa in start_thread (arg=0x7fb4c35ef700) at
pthread_create.c:333
#9  0x7fb4d90ece9d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 7 (Thread 0x7fb4b8411700 (LWP 7367)):
#0  0x7fb4d5e8d888 in g_main_context_prepare () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#1  0x7fb4d5e8e11b in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7fb4d5e8e2fc in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7fb4d9a0b29b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7fb4d99b175a in
QEventLoop::exec(QFlags) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7fb4d97cf3d4 in QThread::exec() () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7fb4dbff7f85 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5
#7  0x7fb4d97d42be in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x7fb4d88c36aa in start_thread (arg=0x7fb4b8411700) at
pthread_create.c:333
#9  0x7fb4d90ece9d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 6 (Thread 0x7fb4b5c5f700 (LWP 7371)):
#0  0x7fb4d97cc4d0 in QMutex::lock() () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#1  0x7fb4d9a0a81f in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#2  0x7fb4d5e8d77d in g_main_context_prepare () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7fb4d5e8e11b in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7fb4d5e8e2fc in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x7fb4d9a0b29b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7fb4d99b175a in
QEventLoop::exec(QFlags) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7fb4d97cf3d4 in QThread::exec() () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x7fb4dbff7f85 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5
#9  0x7fb4d97d42be in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#10 0x7fb4d88c36aa in start_thread (arg=0x7fb4b5c5f700) at
pthread_create.c:333
#11 0x7fb4d90ece9d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 5 (Thread 0x7fb4a7fff700 (LWP 7372)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7fb4de383114 in ?? () from