[ark] [Bug 378904] New: Ark should use charset auto-detection for filenames

[Nicolas Frattaroli]

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

Bug ID: 378904
   Summary: Ark should use charset auto-detection for filenames
   Product: ark
   Version: unspecified
  Platform: unspecified
OS: Linux
Status: UNCONFIRMED
  Severity: wishlist
  Priority: NOR
 Component: general
  Assignee: elvis.angelac...@kde.org
  Reporter: kdeb...@fratti.ch
CC: rthoms...@gmail.com
  Target Milestone: ---

ZIP archives have no standardised encoding for filenames and do not supply the
charset information in the archive itself. This results in a problem that
occurs when opening a ZIP created by, say, a Japanese Windows user, in Ark, as
the filenames will come out as a garbled mess since Ark will expect a different
encoding than the one that was used.

This can be worked around by using a library such as uchardet, which can guess
the used encoding from the binary filename string. Allowing users to manually
specify which encoding should be tried would also be a helpful addition.

A file demonstrating this issue can be found here:
http://maltinerecords.cs8.biz/release/164/MARU164.zip

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

[kdenlive] [Bug 378832] use of vaapi in transcoding and rendering

[Jean-Baptiste Mardelle]

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

--- Comment #1 from Jean-Baptiste Mardelle  ---
Git commit 456635ac2c5e15d3445d9889cdb0e42b5d984811 by Jean-Baptiste Mardelle.
Committed on 18/04/2017 at 05:45.
Pushed by mardelle into branch 'Applications/17.04'.

Allow passing pre-parameters using "-i" to specify where the input file name
should go in ffmpeg parameters
Should work in proxy and transcoding, for example:
-vaapi_device /dev/dri/renderD128 -hwaccel vaapi -hwaccel_output_format vaapi
-i -an -c:v dnxhd
Will insert source file name after "-i".

M  +1-1src/mainwindow.cpp
M  +18   -7src/project/cliptranscode.cpp
M  +6-1src/project/jobs/cutclipjob.cpp
M  +11   -3src/project/jobs/proxyclipjob.cpp
M  +0-2src/ui/projectsettings_ui.ui

https://commits.kde.org/kdenlive/456635ac2c5e15d3445d9889cdb0e42b5d984811

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

[frameworks-kio] [Bug 346403] kdialog freezes when startDir in --getopenfilename contains a lot of files

[Martin Koller]

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

Martin Koller  changed:

   What|Removed |Added

 Status|UNCONFIRMED |CONFIRMED
 CC||kol...@aon.at
 Ever confirmed|0   |1

--- Comment #13 from Martin Koller  ---
I can confirm this with your example, using detail view, file preview NOT
activated. Using KIO from 5.32.0 on openSuse 42.2

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

[kwin] [Bug 378452] Escape key not detected by several games in wayland

[Martin Gräßlin]

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

Martin Gräßlin  changed:

   What|Removed |Added

  Flags||ReviewRequest+
URL||https://phabricator.kde.org
   ||/D5488

--- Comment #11 from Martin Gräßlin  ---
Proposed patch: https://phabricator.kde.org/D5488

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

[Discover] [Bug 378903] New: Discover doesn't respond to keyboard characters as you would expect.

[Paul]

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

Bug ID: 378903
   Summary: Discover doesn't respond to keyboard characters as you
would expect.
   Product: Discover
   Version: 5.9.4
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: discover
  Assignee: aleix...@kde.org
  Reporter: paul.hancock.17041...@live.com
  Target Milestone: ---

Usually for modern applications and GUIs you would expect that pressing any
standard characters would start either a search, jump or filter automatically,
discover lacks this and requires you to actually click the search box, which
would be very frequently due to how basic the list views are.

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

[Discover] [Bug 378902] New: Discover will not install downloaded rpm packages.

[Paul]

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

Bug ID: 378902
   Summary: Discover will not install downloaded rpm packages.
   Product: Discover
   Version: 5.9.4
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: discover
  Assignee: aleix...@kde.org
  Reporter: paul.hancock.17041...@live.com
  Target Milestone: ---

Discover will not install externally downloaded rpm packages, you click install
and it will flicker for one frame and that's it.

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

[Discover] [Bug 378901] New: Discover will hang on closing.

[Paul]

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

Bug ID: 378901
   Summary: Discover will hang on closing.
   Product: Discover
   Version: 5.9.4
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: discover
  Assignee: aleix...@kde.org
  Reporter: paul.hancock.17041...@live.com
  Target Milestone: ---

When telling discover to close, while nothing is occurring, it will hang
completely and require a KILL to be closed.

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

[krita] [Bug 378900] New: Allow the grid to be displayed under a layer

[bugzilla_noreply]

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

Bug ID: 378900
   Summary: Allow the grid to be displayed under a layer
   Product: krita
   Version: unspecified
  Platform: Other
OS: All
Status: UNCONFIRMED
  Severity: wishlist
  Priority: NOR
 Component: general
  Assignee: krita-bugs-n...@kde.org
  Reporter: lariv...@chello.at
  Target Milestone: ---

Currently the grid is simply displayed on top, which I find a bit distracting
since it goes over my line drawings. I'd prefer it to be displayed under my
drawings layer so that I can draw on top of it.

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

[plasmashell] [Bug 366451] "display scaling" on hidpi screen results in poor font quality

[bugzilla_noreply]

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

e.ekme...@gmail.com changed:

   What|Removed |Added

 CC||e.ekme...@gmail.com

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

[konsole] [Bug 373232] Horizontal lines with fractional HiDPI scaling

[bugzilla_noreply]

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

e.ekme...@gmail.com changed:

   What|Removed |Added

 CC||e.ekme...@gmail.com

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

[KScreen] [Bug 377436] Non-integer scaling values are not properly propagated to force fonts DPI setting

[bugzilla_noreply]

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

e.ekme...@gmail.com changed:

   What|Removed |Added

 CC||e.ekme...@gmail.com

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

[konqueror] [Bug 378899] New: loading a webpage - Konqueror crashed, segfault, plasma5

[Jose Da Silva]

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

Bug ID: 378899
   Summary: loading a webpage - Konqueror crashed, segfault,
plasma5
   Product: konqueror
   Version: unspecified
  Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: konq-b...@kde.org
  Reporter: digi...@joescat.com
  Target Milestone: ---

Application: konqueror (4.14.25)
KDE Platform Version: 4.14.30
Qt Version: 4.8.7
Operating System: Linux 4.10.9-200.fc25.i686 i686
Distribution (Platform): Fedora RPMs

-- Information about the crash:
- What I was doing when the application crashed:
Typed URL into URL space, and webpage got partially loaded, then crashed.
Suspect a bad gif, jpg, or flash causes problem, since a fresh restart with new
ads no longer triggers segfault.

The crash can be reproduced every time.

-- Backtrace:
Application: Konqueror (konqueror), signal: Segmentation fault
Using host libthread_db library "/lib/libthread_db.so.1".
[Current thread is 1 (Thread 0xb4cc8800 (LWP 4460))]

Thread 3 (Thread 0xabbffb40 (LWP 4462)):
#0  0xb77b4cd9 in __kernel_vsyscall ()
#1  0xb6affe9c in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/libpthread.so.0
#2  0xb057e0f4 in WTF::ThreadCondition::wait(WTF::Mutex&) () from
/lib/sse2/libQtWebKit.so.4
#3  0xb020ab8b in JSC::BlockAllocator::blockFreeingThreadMain() () from
/lib/sse2/libQtWebKit.so.4
#4  0xb057d977 in WTF::wtfThreadEntryPoint(void*) () from
/lib/sse2/libQtWebKit.so.4
#5  0xb6afa4ee in start_thread () from /lib/libpthread.so.0
#6  0xb5c1f02e in clone () from /lib/libc.so.6

Thread 2 (Thread 0xacaa4b40 (LWP 4461)):
#0  0xb54f4ae8 in g_main_context_prepare () from /lib/libglib-2.0.so.0
#1  0xb54f5592 in g_main_context_iterate.isra () from /lib/libglib-2.0.so.0
#2  0xb54f57e7 in g_main_context_iteration () from /lib/libglib-2.0.so.0
#3  0xb6ced78f in
QEventDispatcherGlib::processEvents(QFlags) ()
from /lib/libQtCore.so.4
#4  0xb6cb48f0 in
QEventLoop::processEvents(QFlags) () from
/lib/libQtCore.so.4
#5  0xb6cb4cbd in QEventLoop::exec(QFlags) ()
from /lib/libQtCore.so.4
#6  0xb6b7df6b in QThread::exec() () from /lib/libQtCore.so.4
#7  0xb6b7e0dc in QThread::run() () from /lib/libQtCore.so.4
#8  0xb6b80f24 in QThreadPrivate::start(void*) () from /lib/libQtCore.so.4
#9  0xb6afa4ee in start_thread () from /lib/libpthread.so.0
#10 0xb5c1f02e in clone () from /lib/libc.so.6

Thread 1 (Thread 0xb4cc8800 (LWP 4460)):
[KCrash Handler]
#7  0xb6093c7c in comp_func_Source_sse2(unsigned int*, unsigned int const*,
int, unsigned int) () from /lib/libQtGui.so.4
#8  0xb62d0b35 in void blend_untransformed_generic<(SpanMethod)0>(int,
QT_FT_Span_ const*, void*) () from /lib/libQtGui.so.4
#9  0xb62b8782 in fillRect_normalized(QRect const&, QSpanData*,
QRasterPaintEnginePrivate*) () from /lib/libQtGui.so.4
#10 0xb62bee06 in QRasterPaintEngine::drawImage(QRectF const&, QImage const&,
QRectF const&, QFlags) () from /lib/libQtGui.so.4
#11 0xb62c74f6 in QRasterPaintEngine::drawPixmap(QRectF const&, QPixmap const&,
QRectF const&) () from /lib/libQtGui.so.4
#12 0xb623f0a1 in QPainter::drawPixmap(QRectF const&, QPixmap const&, QRectF
const&) () from /lib/libQtGui.so.4
#13 0xaf76bb22 in WebCore::BitmapImage::draw(WebCore::GraphicsContext*,
WebCore::FloatRect const&, WebCore::FloatRect const&, WebCore::ColorSpace,
WebCore::CompositeOperator) () from /lib/sse2/libQtWebKit.so.4
#14 0xaf448027 in WebCore::GraphicsContext::drawImage(WebCore::Image*,
WebCore::ColorSpace, WebCore::FloatRect const&, WebCore::FloatRect const&,
WebCore::CompositeOperator, WebCore::RespectImageOrientationEnum, bool) [clone
.part.26] () from /lib/sse2/libQtWebKit.so.4
#15 0xaf44952d in WebCore::GraphicsContext::drawImage(WebCore::Image*,
WebCore::ColorSpace, WebCore::IntRect const&, WebCore::IntRect const&,
WebCore::CompositeOperator, WebCore::RespectImageOrientationEnum, bool) () from
/lib/sse2/libQtWebKit.so.4
#16 0xaf4495c5 in WebCore::GraphicsContext::drawImage(WebCore::Image*,
WebCore::ColorSpace, WebCore::IntRect const&, WebCore::CompositeOperator,
WebCore::RespectImageOrientationEnum, bool) () from /lib/sse2/libQtWebKit.so.4
#17 0xaf5de7d0 in
WebCore::RenderImage::paintIntoRect(WebCore::GraphicsContext*,
WebCore::LayoutRect const&) () from /lib/sse2/libQtWebKit.so.4
#18 0xaf5df0cf in WebCore::RenderImage::paintReplaced(WebCore::PaintInfo&,
WebCore::LayoutPoint const&) () from /lib/sse2/libQtWebKit.so.4
#19 0xaf678c60 in WebCore::RenderReplaced::paint(WebCore::PaintInfo&,
WebCore::LayoutPoint const&) () from /lib/sse2/libQtWebKit.so.4
#20 0xaf5e0d1e in WebCore::RenderImage::paint(WebCore::PaintInfo&,
WebCore::LayoutPoint const&) () from /lib/sse2/libQtWebKit.so.4
#21 0xaf524799 in WebCore::InlineBox::paint(WebCore::PaintInfo&,
WebCore::LayoutPoint const&, WebCore::LayoutUnit, WebCore::LayoutUnit) () from

[gwenview] [Bug 373178] Blurry scaling on HiDPI

[bugzilla_noreply]

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

e.ekme...@gmail.com changed:

   What|Removed |Added

 CC||e.ekme...@gmail.com

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

[konsole] [Bug 378264] tmux trunk breaks URL recognition

[Markus Trippelsdorf]

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

--- Comment #2 from Markus Trippelsdorf  ---
(In reply to Kurt Hindenburg from comment #1)
> Do you happen to know if it works with other terminals?  and what version of
> tmux did it work with?

Other terminals don't have URL recognition (at least xterm doesn't).
tmux-2.3 (current release) works fine. The next version (not yet released) will
break many thinks (copy, vim, etc.).
I think that playing these redraw games in tmux is way too fragile.

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

[konsole] [Bug 378264] tmux trunk breaks URL recognition

[Kurt Hindenburg]

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

--- Comment #1 from Kurt Hindenburg  ---
Do you happen to know if it works with other terminals?  and what version of
tmux did it work with?

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

[plasmashell] [Bug 378898] New: Menu will not respond to scroll from scrollwheel, yet responds to trackpad.

[Paul]

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

Bug ID: 378898
   Summary: Menu will not respond to scroll from scrollwheel, yet
responds to trackpad.
   Product: plasmashell
   Version: master
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Application Menu (Kicker)
  Assignee: h...@kde.org
  Reporter: paul.hancock.17041...@live.com
CC: plasma-b...@kde.org
  Target Milestone: 1.0

Menu will not respond to scroll from scrollwheel, yet responds to trackpad,
scrollwheel works in all other applications.

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

[kdenlive] [Bug 378897] New: missing cursor in timeline

[lawrencelile]

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

Bug ID: 378897
   Summary: missing cursor in timeline
   Product: kdenlive
   Version: 16.12.3
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: major
  Priority: NOR
 Component: User Interface
  Assignee: j...@kdenlive.org
  Reporter: lawrencel...@gmail.com
  Target Milestone: ---

There is no cursor in the timeline.  I've installed, de-installed, and
reinstalled from the KDE PPA's, same result.  This happens as soon as I open
the program.  Clicking on a point in the timeline, and pressing "play" in the
clip monitor does not change the playback position - it continues playing where
it was before.  

Using kdenlive Version 16.12.3  Using:
KDE Frameworks 5.18.0
Qt 5.5.1 (built against 5.5.1)
The xcb windowing system

Ubuntu 16.04,  I am running ubuntu 16.04, Nvidia driver 340.12, X server 11.0,
Quadro NVS 290 video card



Similar to bug 366798 which was marked as resolved.  There are others posting
about this issue in the kdenlive forums, so I do not believe it was resolved.

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

[konsole] [Bug 378458] Shortcuts to navigate in split view

[Kurt Hindenburg]

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

--- Comment #1 from Kurt Hindenburg  ---
That report is for the shortcuts to create the split views.  As I understand,
you want to navigate between the views correct?

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

[konsole] [Bug 378520] Konsole freezes when pressing TAB or BACKSPACE

[Kurt Hindenburg]

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

--- Comment #1 from Kurt Hindenburg  ---
Need more info - does this work OK in another terminal?
xterm/gnome-terminal/etc?

I don't quite see how it could be Konsole.

Also are you running master git branch?

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

[konsole] [Bug 373232] Horizontal lines with fractional HiDPI scaling

[Kurt Hindenburg]

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

Kurt Hindenburg  changed:

   What|Removed |Added

 Status|UNCONFIRMED |CONFIRMED
 Ever confirmed|0   |1

--- Comment #13 from Kurt Hindenburg  ---
Yes It is clear the scaling causes these issues - even the non blicking square
cursor looks off.

I'm not entirely sure what that scaling does or how to detect it in Konsole
(which does a lot of calculations).

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

[k3b] [Bug 378633] k3bdeviceglobalstest fails

[Leslie Zhai]

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

Leslie Zhai  changed:

   What|Removed |Added

 CC||xiangzha...@gmail.com

--- Comment #1 from Leslie Zhai  ---
Hi Heiko,

Welcome patch :)

Regards,
Leslie Zhai

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

[konsole] [Bug 378784] Konsole doesn't notify user if it cannot save profile

[Kurt Hindenburg]

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

Kurt Hindenburg  changed:

   What|Removed |Added

 Status|UNCONFIRMED |CONFIRMED
 Ever confirmed|0   |1

--- Comment #1 from Kurt Hindenburg  ---
Thanks I tend to agree with the patch although the dialog is rather vague as
I'm sure how many people have 'system administrators'.  We could also catch the
return value and create our own dialog.

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

[konsole] [Bug 378795] Konsole text on fully maximized widget displays top 3-4 lines at low intensity

[Kurt Hindenburg]

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

Kurt Hindenburg  changed:

   What|Removed |Added

Version|unspecified |16.12.3

--- Comment #1 from Kurt Hindenburg  ---
https://bugzilla.redhat.com/show_bug.cgi?id=1438439

As they asked for as well, a screenshot would be great either there or here

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

[plasmashell] [Bug 378895] Panel resizes on reboot rendering computer unusable

[David Edmundson]

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

--- Comment #10 from David Edmundson  ---
It's not that the last one wins, it's that it's storing the panel thickness
setting per monitor-size.

[PlasmaViews][Panel 1][Vertical899]

Is the panel 1 setting when the monitor is 899 pixels high.

An issue with virtual machines - but less so on real setups. Without it you end
up with a different bug.

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

[Spectacle] [Bug 370945] 'Window under cursor' works more like 'all windows of an application'

[Francisco Fernandes]

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

Francisco Fernandes  changed:

   What|Removed |Added

 CC||francisco.fernandes.j@gmail
   ||.com

--- Comment #3 from Francisco Fernandes  ---
I confirmed the behavior described by @Achim in my these environment:

  * Plasma 5.9.4
  * KDE Frameworks 5.33.0
  * Qt 5.8.0
  * XCB windowing system

Also, when I click "Capture the only pop-up" and do the "On click" screenshot
Delay setting, nothing happens and the 'Printscreen' button shortcut stop
working. So, if I want to take another shot, I have to call from KRunner or
from the Application launcher.

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

[KScreen] [Bug 378896] Enabling a secondary Monitor left of the Primary moves all windows

[evea]

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

evea  changed:

   What|Removed |Added

 CC||everm...@pc-portal.at

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

[plasmashell] [Bug 378895] Panel resizes on reboot rendering computer unusable

[Aaron Peterson]

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

--- Comment #9 from Aaron Peterson  ---
Created attachment 105069
  --> https://bugs.kde.org/attachment.cgi?id=105069=edit
there was a history line, that is completely innapropriate for being in a
config

This is the plasmarc.txt   I have no idea why panel 1 would be there so many
times... it appears that the last one wins.  I tried making this readonly...
and it complained

There was a history line in here... which is session information... not
configuration.. and I am angry that that was in here, and it has nothing to do
with the configuration of my machine... I deleted that history line before I
realized that I should save a copy to share with people.

Why is there session data still mixed with configuration data?
anyway... thickness should probably be a few hundred pixles, but it keeps on
coming up really thin.

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

[KScreen] [Bug 378896] New: Enabling a secondary Monitor left of the Primary moves all windows

[evea]

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

Bug ID: 378896
   Summary: Enabling a secondary Monitor left of the Primary moves
all windows
   Product: KScreen
   Version: 5.9.4
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: common
  Assignee: se...@kde.org
  Reporter: everm...@pc-portal.at
  Target Milestone: ---

When enabling a secondary monitor, which is located left of the primary, all
windows are moved to the secondary monitor, this includes dockers liker Plank.

No matter if you use the system settings, Meta+p or xrandr.

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

[plasmashell] [Bug 378895] Panel resizes on reboot rendering computer unusable

[Aaron Peterson]

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

--- Comment #8 from Aaron Peterson  ---
also, right clicking on the desktop now makes new note widgets...
right now I'm not able to get into a konsole

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

[plasmashell] [Bug 378895] Panel resizes on reboot rendering computer unusable

[Aaron Peterson]

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

Aaron Peterson  changed:

   What|Removed |Added

 Resolution|WAITINGFORINFO  |---
 Status|NEEDSINFO   |UNCONFIRMED

--- Comment #7 from Aaron Peterson  ---
It is so trivial to recreate, I'm sort of offended that it was set up as
striked thru  waiting for info... I'm right here struggling to figure out how
to solve this problem so I can let the person use the computer!

I'll send you the rc

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

[digikam] [Bug 347937] SETUP : Collections added as "Removable Media" change as "Local Collections"

[RJVB]

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

--- Comment #21 from RJVB  ---
(In reply to caulier.gilles from comment #20)

> After all this time, KF5::Solid API do not support yet MacOS better... Why ?

Because no one bothered improving it, presumably in (large?) part because it's
seen as something needed on Plasma desktops, not in KDE applications running in
other environments?

The other thing is that it isn't the easiest kind of code to write, and also
not something you want to develop on a virtual machine.

BTW, I tested with the 5.6.0 installer preview.

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

[plasmashell] [Bug 378895] Panel resizes on reboot rendering computer unusable

[David Edmundson]

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

David Edmundson  changed:

   What|Removed |Added

 Resolution|--- |WAITINGFORINFO
   Severity|major   |normal
 Status|UNCONFIRMED |NEEDSINFO
 CC||k...@davidedmundson.co.uk

--- Comment #6 from David Edmundson  ---
Do you still have your plasmashellrc?

Are you rebooting with a different sized screen?

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

[plasmashell] [Bug 378895] Panel resizes on reboot rendering computer unusable

[Aaron Peterson]

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

--- Comment #5 from Aaron Peterson  ---
Created attachment 105068
  --> https://bugs.kde.org/attachment.cgi?id=105068=edit
change the y screen resolution and the computer is unusable

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

[plasmashell] [Bug 378895] Panel resizes on reboot rendering computer unusable

[Aaron Peterson]

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

--- Comment #4 from Aaron Peterson  ---
Created attachment 105067
  --> https://bugs.kde.org/attachment.cgi?id=105067=edit
THis is roughly how it should look

I think I didn't set the windows can cover setting... that also gets lost.

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

[plasmashell] [Bug 378895] Panel resizes on reboot rendering computer unusable

[Aaron Peterson]

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

Aaron Peterson  changed:

   What|Removed |Added

Version|5.5.5   |5.8.5

--- Comment #3 from Aaron Peterson  ---
It also affects 5.8.5
if I change the screen height, the panel goes antman small.

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

[plasmashell] [Bug 378895] Panel resizes on reboot rendering computer unusable

[Aaron Peterson]

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

--- Comment #2 from Aaron Peterson  ---
To top it off, even though the plasmashellRc was edited and made not writable
the bug still occurs.

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

[plasmashell] [Bug 378895] Panel resizes on reboot rendering computer unusable

[Aaron Peterson]

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

--- Comment #1 from Aaron Peterson  ---
I found that new entries were being written into plasmashell.rc so I deleted
all the extra ones (the last one wins apparently)
and made it read only... Then plasmashell gave me a warning that the file was
not writable!  This is also a bug...  People who lock down their settings are
not experiencing a bug.

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

[frameworks-baloo] [Bug 378754] /usr/bin/baloo_file_extractor consuming 100 %, seemingly concatenating symlink loop to endless path.

[Jan-Matthias Braun]

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

--- Comment #3 from Jan-Matthias Braun  ---
The indexer is ignoring the exclude hint on the parent directory. I don't know
if this could be connected to https://bugs.kde.org/show_bug.cgi?id=378884 .

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

[plasmashell] [Bug 378895] New: Panel resizes on reboot rendering computer unusable

[Aaron Peterson]

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

Bug ID: 378895
   Summary: Panel resizes on reboot rendering computer unusable
   Product: plasmashell
   Version: 5.5.5
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: major
  Priority: NOR
 Component: Panel
  Assignee: plasma-b...@kde.org
  Reporter: alpeter...@gmail.com
  Target Milestone: 1.0

Created attachment 105066
  --> https://bugs.kde.org/attachment.cgi?id=105066=edit
Panel is miniscule.  Users cannot use this panel because things are too small.

I have a kubuntu 16.04 computer deployed and apparently after every restart
after the update, the width of the left panel was reset to narrow, rendering
the panel useless to the user.
Since this is deployed to people with limited capability or desire to mess with
settings, this is a severe bug, and I must find a solution ASAP.

I was able to reproduce it in a virtual machine...

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

[krunner] [Bug 375500] Very high CPU usage, goes away after restarting the process

[Jan-Matthias Braun]

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

--- Comment #4 from Jan-Matthias Braun  ---
Hi!

I am having a better backtrace. This backtrace seems to relate to bug
https://bugs.kde.org/show_bug.cgi?id=378754 .

#0  0x7f5298b604d9 in QConcatenable::appendTo (
out=: 0x7f52780e71ca "drive_c/users/user/Meine
Dokumente/lib/wine/program/drive_c/users/user/Meine
Dokumente/lib/wine/program/drive_c/users/user/Meine
Dokumente/lib/wine/program/drive_c/users/user/Meine Dokumente/lib/wine/p"...,
ba=...) at /usr/include/qt5/QtCore/qstringbuilder.h:354
#1  QConcatenable, QByteArray>
>::appendTo (
out=: 0x7f52780e71ca "drive_c/users/user/Meine
Dokumente/lib/wine/program/drive_c/users/user/Meine
Dokumente/lib/wine/program/drive_c/users/user/Meine
Dokumente/lib/wine/program/drive_c/users/user/Meine Dokumente/lib/wine/p"...,
p=...) at /usr/include/qt5/QtCore/qstringbuilder.h:372
#2  QStringBuilder,
QByteArray>::convertTo (this=) at
/usr/include/qt5/QtCore/qstringbuilder.h:118
#3  QStringBuilder, QByteArray>::operator
QByteArray (this=) at
/usr/include/qt5/QtCore/qstringbuilder.h:131
#4  Baloo::DocumentUrlDB::get (this=this@entry=0x7f528effc9e0,
docId=docId@entry=150699235501735430) at
/var/tmp/portage/kde-frameworks/baloo-5.33.0/work/baloo-5.33.0/src/engine/documenturldb.cpp:145
#5  0x7f5298b7a6e1 in Baloo::Transaction::documentUrl
(this=this@entry=0x7f528effca80, id=150699235501735430)
at
/var/tmp/portage/kde-frameworks/baloo-5.33.0/work/baloo-5.33.0/src/engine/transaction.cpp:104
#6  0x7f5298fd4523 in Baloo::SearchStore::exec
(this=this@entry=0x7f528effcb60, term=..., offset=,
limit=, sortResults=)
at
/var/tmp/portage/kde-frameworks/baloo-5.33.0/work/baloo-5.33.0/src/lib/searchstore.cpp:108
#7  0x7f5298fc328f in Baloo::Query::exec (this=0x7f528effcc30) at
/var/tmp/portage/kde-frameworks/baloo-5.33.0/work/baloo-5.33.0/src/lib/query.cpp:210
#8  0x7f52991e43a4 in SearchRunner::match(Plasma::RunnerContext&, QString
const&, QString const&) () from
/usr/lib64/qt5/plugins/krunner_baloosearchrunner.so
#9  0x7f52991e5436 in SearchRunner::match(Plasma::RunnerContext&) () from
/usr/lib64/qt5/plugins/krunner_baloosearchrunner.so
#10 0x7f52a75a7108 in
Plasma::AbstractRunner::performMatch(Plasma::RunnerContext&) () from
/usr/lib64/libKF5Runner.so.5
#11 0x7f52a7385a78 in
ThreadWeaver::Executor::run(QSharedPointer const&,
ThreadWeaver::Thread*) () from /usr/lib64/libKF5ThreadWeaver.so.5
#12 0x7f52a73846c0 in
ThreadWeaver::Job::execute(QSharedPointer const&,
ThreadWeaver::Thread*) () from /usr/lib64/libKF5ThreadWeaver.so.5
#13 0x7f52a73841c0 in ThreadWeaver::Thread::run() () from
/usr/lib64/libKF5ThreadWeaver.so.5
#14 0x7f52c5194fed in QThreadPrivate::start(void*) () from
/usr/lib64/libQt5Core.so.5
#15 0x7f52c2a53374 in start_thread () from /lib64/libpthread.so.0
#16 0x7f52c4a47b2f in clone () from /lib64/libc.so.6

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

[systemsettings] [Bug 378863] Touchpad configuration not working on Zesty

[Victor Sanchez]

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

Victor Sanchez  changed:

   What|Removed |Added

 CC||vsanc...@promed.com.pa

--- Comment #1 from Victor Sanchez  ---
I can confirm this. Mouseclick emulation and scrolling direction are not
changed... however, logging out and logging in again correctly configures the
touchpad at least in my XPS 13.

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

[rsibreak] [Bug 377419] End of short/long break notifies all the time

[Albert Astals Cid]

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

Albert Astals Cid  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |FIXED
  Latest Commit||https://commits.kde.org/rsi
   ||break/0cdbdf5dd11b2acd50ef5
   ||addfc62d7734c668a02

--- Comment #4 from Albert Astals Cid  ---
Git commit 0cdbdf5dd11b2acd50ef5addfc62d7734c668a02 by Albert Astals Cid.
Committed on 17/04/2017 at 21:18.
Pushed by aacid into branch 'master'.

Only trigger end of break when we're actually on a break

If we are resetting the timer because of user inactivity do not notify
break ending since that gets notified as "timer reset"

M  +24   -16   src/rsitimer.cpp
M  +2-2src/rsitimer.h

https://commits.kde.org/rsibreak/0cdbdf5dd11b2acd50ef5addfc62d7734c668a02

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

[digikam] [Bug 378804] lensfun uses only one core, pls. parallize [patch]

[Maik Qualmann]

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

Maik Qualmann  changed:

   What|Removed |Added

   Version Fixed In||5.6.0
  Latest Commit||https://commits.kde.org/dig
   ||ikam/0238f8a8234154b3d4c887
   ||7de94b72505f55ad7d
 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |FIXED

--- Comment #10 from Maik Qualmann  ---
Git commit 0238f8a8234154b3d4c8877de94b72505f55ad7d by Maik Qualmann.
Committed on 17/04/2017 at 20:57.
Pushed by mqualmann into branch 'master'.

use QtConcurrent to parallelize the Lensfun filter and use all CPU cores
FIXED-IN: 5.6.0

M  +2-1NEWS
M  +119  -87   libs/dimg/filters/lens/lensfunfilter.cpp
M  +3-0libs/dimg/filters/lens/lensfunfilter.h

https://commits.kde.org/digikam/0238f8a8234154b3d4c8877de94b72505f55ad7d

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

[digikam] [Bug 347937] SETUP : Collections added as "Removable Media" change as "Local Collections"

[bugzilla_noreply]

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

--- Comment #20 from caulier.gil...@gmail.com ---
RJVB,

After all this time, KF5::Solid API do not support yet MacOS better... Why ?

Gilles Caulier

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

[digikam] [Bug 347937] SETUP : Collections added as "Removable Media" change as "Local Collections"

[bugzilla_noreply]

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

caulier.gil...@gmail.com changed:

   What|Removed |Added

Version|4.10.0  |5.5.0

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

[Discover] [Bug 376241] software centre is empty

[josevallegas]

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

--- Comment #35 from josevalle...@gmail.com  ---
Hi Aleix,
Discover is no longer empty after this weekend update. It was a ruge update
with more than 3 handred files.
Thank you
José Vallegas

2017-04-06 13:40 GMT-03:00 Aleix Pol :

> https://bugs.kde.org/show_bug.cgi?id=376241
>
> Aleix Pol  changed:
>
>What|Removed |Added
> 
> 
>  CC||josevalle...@gmail.com
>
> --- Comment #31 from Aleix Pol  ---
> *** Bug 378482 has been marked as a duplicate of this bug. ***
>
> --
> You are receiving this mail because:
> You are on the CC list for the bug.

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

[amarok] [Bug 378869] Recently added albums is empty

[robert marshall]

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

--- Comment #4 from robert marshall  ---
No it wasn't fixed - it's the webform which put two combo boxes beneath the
comment box, one with 'unconfirmed' the other with 'fixed' and I knew which was
going to win :-( nothing else in the fixed combo looked suitable so I just left
it.

Thanks for restoring it back to unconfirmed. In this case there's only an
unconfirmed one so I hope it stays!

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

[Discover] [Bug 378556] Can not open plasma-discover-updater (Update Manager)

[N . W .]

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

--- Comment #1 from N. W.  ---
Anyone who can help here?

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

[Discover] [Bug 378556] Can not open plasma-discover-updater (Update Manager)

[N . W .]

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

N. W.  changed:

   What|Removed |Added

  Component|general |Updater
Product|neon|Discover

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

[digikam] [Bug 378804] lensfun uses only one core, pls. parallize [patch]

[bugzilla_noreply]

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

--- Comment #9 from caulier.gil...@gmail.com ---
Comment on attachment 105063
  --> https://bugs.kde.org/attachment.cgi?id=105063
lensfunfilter.patch

You have right Maik,

This version of the patch fix the problem. I forget to catch loop variable at
end of last filter stage. 

So you can apply this patch over git/master now, and close this entry.

Thanks

Gilles

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

[amarok] [Bug 378869] Recently added albums is empty

[Myriam Schweingruber]

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

Myriam Schweingruber  changed:

   What|Removed |Added

 Status|NEEDSINFO   |UNCONFIRMED
 Resolution|FIXED   |---

--- Comment #3 from Myriam Schweingruber  ---
Thanks for the fast answer, changing back to unconfirmed, I have yet to test
this (I guess it was not really fixed, or was it?)

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

[plasmashell] [Bug 378894] Visual change failure

[Kai Uwe Broulik]

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

Kai Uwe Broulik  changed:

   What|Removed |Added

 Resolution|--- |DUPLICATE
 CC||k...@privat.broulik.de
 Status|UNCONFIRMED |RESOLVED

--- Comment #1 from Kai Uwe Broulik  ---


*** This bug has been marked as a duplicate of bug 378508 ***

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

[plasmashell] [Bug 378508] when remove panel applet plasma crashed

[Kai Uwe Broulik]

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

Kai Uwe Broulik  changed:

   What|Removed |Added

 CC||mib...@gmail.com

--- Comment #8 from Kai Uwe Broulik  ---
*** Bug 378894 has been marked as a duplicate of this bug. ***

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

[plasmashell] [Bug 378508] when remove panel applet plasma crashed

[Kai Uwe Broulik]

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

--- Comment #7 from Kai Uwe Broulik  ---
Yeah sorry the (hopefully proper) patch is still pending, will finalize it
tomorrow (so it will be in 5.9.5)

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

[Discover] [Bug 376241] software centre is empty

[Ted Becker]

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

--- Comment #34 from Ted Becker  ---
Sorry I won't be able to test it.  There were enough other issues with 16.04
that I switched back to 14.04.

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

[amarok] [Bug 378869] Recently added albums is empty

[robert marshall]

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

robert marshall  changed:

   What|Removed |Added

 Resolution|WAITINGFORINFO  |FIXED

--- Comment #2 from robert marshall  ---
Yes maybe I should have put the word applet in the subject and a few more times
in the body than I did!

This is KDE 4.14.22

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

[amarok] [Bug 378869] Recently added albums is empty

[Myriam Schweingruber]

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

Myriam Schweingruber  changed:

   What|Removed |Added

 Status|UNCONFIRMED |NEEDSINFO
  Component|general |Context View/Albums
 Resolution|--- |WAITINGFORINFO

--- Comment #1 from Myriam Schweingruber  ---
I was a tad puzzled what you were talking about until I remembered the Albums
applet :-)
Is this on KDE 4.x or on Plasma 5.x? In the latter case I wouldn't be
astonished to see plenty of bugs showing up due to the difference in
platform...

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

[valgrind] [Bug 378892] Unhandled amd64-linux syscall: 324 [membarrier]

[Tom Hughes]

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

--- Comment #1 from Tom Hughes  ---
This appears to be membarrier and should be fairly simple to support.

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

[dolphin] [Bug 378776] dolphin crashes

[bugzilla_noreply]

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

hu...@gmx.de changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |FIXED

--- Comment #2 from hu...@gmx.de ---
Ark (16.08.2) did not start. I also installed ark version 17.3.80. Now ark
works and dolphion doesn't crash anymore. Thank you.

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

[valgrind] [Bug 378892] Unhandled amd64-linux syscall: 324 [membarrier]

[Tom Hughes]

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

Tom Hughes  changed:

   What|Removed |Added

 CC||t...@compton.nu
Summary|Unhandled amd64-linux   |Unhandled amd64-linux
   |syscall: 324|syscall: 324 [membarrier]

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

[konsole] [Bug 360072] Option "manage profiles" doesn't work, doesn't do anything

[Craig]

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

Craig  changed:

   What|Removed |Added

 CC||craig.finne...@gmail.com

--- Comment #8 from Craig  ---
Hey guys,
This has been around for over a year now for such a critical thing affecting
yakuake, can we expect any movement?

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

[plasmashell] [Bug 378894] New: Visual change failure

[Miguel Angel]

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

Bug ID: 378894
   Summary: Visual change failure
   Product: plasmashell
   Version: 5.9.4
  Platform: unspecified
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: mib...@gmail.com
CC: bhus...@gmail.com, plasma-b...@kde.org
  Target Milestone: 1.0

Application: plasmashell (5.9.4)

Qt Version: 5.8.0
Frameworks Version: 5.33.0
Operating System: Linux 4.10.9-1 x86_64
Distribution: "KaOS"

-- Information about the crash:
Failure visual change of workspace (theme plasma), changes of windows and
desktop.
On workspace themes and visual aspect when trying change with using desktop
theme design.- What I was doing when the application crashed:

The crash can be reproduced every time.

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

Thread 11 (Thread 0x7fa33f56f700 (LWP 7713)):
#0  0x7fa427ba05cf in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib/libpthread.so.0
#1  0x7fa428ce948b in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/libQt5Core.so.5
#2  0x7fa42bd5eccd in  () at /usr/lib/libQt5Quick.so.5
#3  0x7fa42bd5f565 in  () at /usr/lib/libQt5Quick.so.5
#4  0x7fa428ce86e9 in  () at /usr/lib/libQt5Core.so.5
#5  0x7fa427b9a494 in start_thread () at /lib/libpthread.so.0
#6  0x7fa4286036ff in clone () at /lib/libc.so.6

Thread 10 (Thread 0x7fa33fffa700 (LWP 7627)):
#0  0x7fa427ba05cf in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib/libpthread.so.0
#1  0x7fa428ce948b in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/libQt5Core.so.5
#2  0x7fa42bd5eccd in  () at /usr/lib/libQt5Quick.so.5
#3  0x7fa42bd5f565 in  () at /usr/lib/libQt5Quick.so.5
#4  0x7fa428ce86e9 in  () at /usr/lib/libQt5Core.so.5
#5  0x7fa427b9a494 in start_thread () at /lib/libpthread.so.0
#6  0x7fa4286036ff in clone () at /lib/libc.so.6

Thread 9 (Thread 0x7fa350e63700 (LWP 3903)):
#0  0x7fa427ba05cf in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib/libpthread.so.0
#1  0x7fa428ce948b in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/libQt5Core.so.5
#2  0x7fa42bd5eccd in  () at /usr/lib/libQt5Quick.so.5
#3  0x7fa42bd5f565 in  () at /usr/lib/libQt5Quick.so.5
#4  0x7fa428ce86e9 in  () at /usr/lib/libQt5Core.so.5
#5  0x7fa427b9a494 in start_thread () at /lib/libpthread.so.0
#6  0x7fa4286036ff in clone () at /lib/libc.so.6

Thread 8 (Thread 0x7fa35b862700 (LWP 2153)):
#0  0x7fa4285f5f7d in read () at /lib/libc.so.6
#1  0x7fa41f53d073 in  () at /usr/lib/libnvidia-tls.so.378.13
#2  0x7fa421e681c0 in  () at /usr/lib/libglib-2.0.so.0
#3  0x7fa421e2450e in g_main_context_check () at /usr/lib/libglib-2.0.so.0
#4  0x7fa421e249a8 in  () at /usr/lib/libglib-2.0.so.0
#5  0x7fa421e24b0c in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#6  0x7fa428f00ebb in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#7  0x7fa428eaebba in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#8  0x7fa428ce3d7c in QThread::exec() () at /usr/lib/libQt5Core.so.5
#9  0x7fa35e46c347 in KCupsConnection::run() () at /usr/lib/libkcupslib.so
#10 0x7fa428ce86e9 in  () at /usr/lib/libQt5Core.so.5
#11 0x7fa427b9a494 in start_thread () at /lib/libpthread.so.0
#12 0x7fa4286036ff in clone () at /lib/libc.so.6

Thread 7 (Thread 0x7fa3746c2700 (LWP 1883)):
#0  0x7fa4285f9ffd in poll () at /lib/libc.so.6
#1  0x7fa421e24a04 in  () at /usr/lib/libglib-2.0.so.0
#2  0x7fa421e24b0c in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#3  0x7fa428f00ebb in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#4  0x7fa428eaebba in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#5  0x7fa428ce3d7c in QThread::exec() () at /usr/lib/libQt5Core.so.5
#6  0x7fa42bcf01b2 in  () at /usr/lib/libQt5Quick.so.5
#7  0x7fa428ce86e9 in  () at /usr/lib/libQt5Core.so.5
#8  0x7fa427b9a494 in start_thread () at /lib/libpthread.so.0
#9  0x7fa4286036ff in clone () at /lib/libc.so.6

Thread 6 (Thread 0x7fa40cb5a700 (LWP 1842)):
#0  0x7fa427ba05cf in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib/libpthread.so.0
#1  0x7fa42d7c8934 in  () at /usr/lib/libQt5Script.so.5
#2  0x7fa42d7c8979 in  () at /usr/lib/libQt5Script.so.5
#3  0x7fa427b9a494 in start_thread () at /lib/libpthread.so.0
#4  0x7fa4286036ff in clone () at /lib/libc.so.6

Thread 5 (Thread 0x7fa40e99a700 (LWP 1750)):
#0  0x7fa4285f9ffd in poll () at /lib/libc.so.6
#1  0x7fa421e24a04 in  () at /usr/lib/libglib-2.0.so.0
#2  0x7fa421e24b0c in 

[plasmashell] [Bug 378508] when remove panel applet plasma crashed

[RJ]

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

RJ  changed:

   What|Removed |Added

 Status|RESOLVED|REOPENED
 Resolution|DUPLICATE   |---

--- Comment #6 from RJ  ---
Hm as I see here bug was fixed in 5.9.4
https://cgit.kde.org/plasma-workspace.git/commit/?h=Plasma/5.9=bcb6b86d3ab8bd196877473af343b72c53e4f932
but I reported it at this version!

Make this reopened.

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

[plasmashell] [Bug 378508] when remove panel applet plasma crashed

[RJ]

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

--- Comment #5 from RJ  ---
Created attachment 105064
  --> https://bugs.kde.org/attachment.cgi?id=105064=edit
bug

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

[Discover] [Bug 376241] software centre is empty

[Matthias K .]

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

--- Comment #33 from Matthias K.  ---
This is highly likely
https://bugs.launchpad.net/ubuntu/+source/plasma-discover/+bug/1663695 which
should be resolved soonish. You can help fixing it by testing the AppStream
package in -updates-proposed.

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

[kwin] [Bug 378891] Kwin Crash

[Martin Gräßlin]

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

Martin Gräßlin  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |DUPLICATE

--- Comment #1 from Martin Gräßlin  ---
There is no need to report further such crash reports.

*** This bug has been marked as a duplicate of bug 378853 ***

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

[kwin] [Bug 378853] Kin Crash

[Martin Gräßlin]

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

--- Comment #2 from Martin Gräßlin  ---
*** Bug 378891 has been marked as a duplicate of this bug. ***

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

[gwenview] [Bug 378893] New: Loader crashes when loading BlackMarble20161km.jpg

[Jan Schnackenberg]

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

Bug ID: 378893
   Summary: Loader crashes when loading BlackMarble20161km.jpg
   Product: gwenview
   Version: Other (add details in bug description)
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: gwenview-bugs-n...@kde.org
  Reporter: j...@schnackenberg.org
CC: myr...@kde.org
  Target Milestone: ---

When loading the file
https://www.nasa.gov/specials/blackmarble/media/BlackMarble20161km.jpg with
gwenview 16.04.3 (Kubuntu 16.10) the file will show (after a few seconds)
fitted to the current window size.

When clicking on "100%" the display-area will go white and only show a message,
that the loading of the image failed (German message: Das Laden der Datei
"BlackMarble20161km.jpg" ist fehlgeschlagen. Laden des Bildes fehlgeschlagen).

I kind of expected problems (the image is 43200x21600 pixel) but... well, I
thought my machine should be able to handle files of this size. :)

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

[Discover] [Bug 376241] software centre is empty

[José Manuel Santamaría Lema]

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

José Manuel Santamaría Lema  changed:

   What|Removed |Added

 CC||panfa...@gmail.com

--- Comment #32 from José Manuel Santamaría Lema  ---
Hi,

I have been digging a bit into this, this is what I found so far:

- xenial provides discover 5.6.4, I built 5.6.5 in a PPA for xenial, that
doesn't fix the issue

- if I'm not mistaken, this is not the packagekit issue pointed out by Matthias
(thanks for the info) because the packagekit issue doesn't affect the version
in xenial; it was affecting zesty but it was already fixed

- from a clean installation from the kubuntu iso 16.04.2 I can reproduce the
bug *without* updating the system

- from a clean installation from the kubuntu iso 16.04.1 (without updates) you
won't see the bug, however, as soon as you type "appstreamcli refresh" you will
get discover listing of installed packages broken

So I presume this is a "clockwork bomb" bug either in the old discover (or
appstream) versions provided by the Kubuntu LTS. I doubt very much this is a
packaging issue.

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

[valgrind] [Bug 378892] New: Unhandled amd64-linux syscall: 324

[Phil]

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

Bug ID: 378892
   Summary: Unhandled amd64-linux syscall: 324
   Product: valgrind
   Version: 3.12.0
  Platform: Compiled Sources
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: memcheck
  Assignee: jsew...@acm.org
  Reporter: adia...@centurylink.net
  Target Milestone: ---

The following appears immediately upon execution:

phil@phil:~/tmp/Bridge$ valgrind --leak-check=yes ./Bridge
==23243== Memcheck, a memory error detector
==23243== Copyright (C) 2002-2015, and GNU GPL'd, by Julian Seward et al.
==23243== Using Valgrind-3.12.0 and LibVEX; rerun with -h for copyright info
==23243== Command: ./Bridge
==23243== 
--23243-- WARNING: unhandled amd64-linux syscall: 324
--23243-- You may be able to write your own handler.
--23243-- Read the file README_MISSING_SYSCALL_OR_IOCTL.
--23243-- Nevertheless we consider this a bug.  Please report
--23243-- it at http://valgrind.org/support/bug_reports.html.

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

[Heaptrack] [Bug 378765] Invoke glibc cleanup when present (__libc_freeres)

[Milian Wolff]

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

Milian Wolff  changed:

   What|Removed |Added

  Latest Commit||https://commits.kde.org/hea
   ||ptrack/3cb1b7fd2f4b3fd65675
   ||8060582001f1e78c3e12
 Resolution|--- |FIXED
 Status|UNCONFIRMED |RESOLVED

--- Comment #1 from Milian Wolff  ---
Git commit 3cb1b7fd2f4b3fd656758060582001f1e78c3e12 by Milian Wolff.
Committed on 17/04/2017 at 19:14.
Pushed by mwolff into branch 'master'.

Call libc and libstdc++ freeres functions in heaptrack_preload on exit

These functions are used by Valgrind already and can be used to force
a clean shutdown of libc and libstdc++. Both usually don't bother
freeing their global resources, which used to be reported as memory
leaks by heaptrack. By calling the freeres functions we now get a
clean shutdown of the libc_leaks.c example without any memory leaks
reported.

Thanks to Maxim Golov for pointing out this hidden functionality and
providing a test case.

M  +19   -0src/track/heaptrack_preload.cpp
M  +2-0tests/manual/CMakeLists.txt
A  +30   -0tests/manual/libc_leaks.c [License: LGPL (v2+)]

https://commits.kde.org/heaptrack/3cb1b7fd2f4b3fd656758060582001f1e78c3e12

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

[kwin] [Bug 378891] New: Kwin Crash

[Seth Izenzon]

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

Bug ID: 378891
   Summary: Kwin Crash
   Product: kwin
   Version: 5.9.4
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kwin-bugs-n...@kde.org
  Reporter: izen...@gmail.com
  Target Milestone: ---

Application: kwin_x11 (5.9.4)

Qt Version: 5.7.1
Frameworks Version: 5.31.0
Operating System: Linux 4.10.0-19-generic x86_64
Distribution: Ubuntu 17.04

-- Information about the crash:
Just opening  a website in Google Chrome when Kwin Crashed, I bet it has to do
with my other Kwin Crash bugs with Nvidia. No idea though.

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 0x7f9eb91c5900 (LWP 13234))]

Thread 5 (Thread 0x7f9e925e0700 (LWP 9893)):
#0  0x7ffdda5fc949 in  ()
#1  0x7ffdda5fcbd9 in clock_gettime ()
#2  0x7f9eb8c18906 in __GI___clock_gettime (clock_id=1, tp=0x7f9e925dfae0)
at ../sysdeps/unix/clock_gettime.c:115
#3  0x7f9eb632bf71 in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7f9eb64a8ba9 in QTimerInfoList::updateCurrentTime() () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7f9eb64a9155 in QTimerInfoList::timerWait(timespec&) () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7f9eb64a7e44 in
QEventDispatcherUNIX::processEvents(QFlags) ()
at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7f9eb645488a in
QEventLoop::exec(QFlags) () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x7f9eb6281fe3 in QThread::exec() () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#9  0x7f9eb0fd4df5 in  () at /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5
#10 0x7f9eb6286c98 in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#11 0x7f9eb22816da in start_thread (arg=0x7f9e925e0700) at
pthread_create.c:456
#12 0x7f9eb8c0a17f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:105

Thread 4 (Thread 0x7f9e8598f700 (LWP 13320)):
#0  0x7f9eb2287510 in pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f9eb56022c4 in  () at /usr/lib/x86_64-linux-gnu/libQt5Script.so.5
#2  0x7f9eb5602309 in  () at /usr/lib/x86_64-linux-gnu/libQt5Script.so.5
#3  0x7f9eb22816da in start_thread (arg=0x7f9e8598f700) at
pthread_create.c:456
#4  0x7f9eb8c0a17f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:105

Thread 3 (Thread 0x7f9e93671700 (LWP 13288)):
#0  0x7f9eb8bfe251 in __GI_ppoll (fds=0x7f9e88000ac8, nfds=1,
timeout=, sigmask=0x0) at ../sysdeps/unix/sysv/linux/ppoll.c:39
#1  0x7f9eb64a6251 in qt_safe_poll(pollfd*, unsigned long, timespec const*)
() at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#2  0x7f9eb64a7b4a in
QEventDispatcherUNIX::processEvents(QFlags) ()
at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#3  0x7f9eb645488a in
QEventLoop::exec(QFlags) () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7f9eb6281fe3 in QThread::exec() () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7f9eb0fd4df5 in  () at /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5
#6  0x7f9eb6286c98 in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7f9eb22816da in start_thread (arg=0x7f9e93671700) at
pthread_create.c:456
#8  0x7f9eb8c0a17f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:105

Thread 2 (Thread 0x7f9ea2009700 (LWP 13235)):
#0  0x7f9eb8bfe18d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7f9ead804576 in  () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f9ead80468c in g_main_context_iteration () at
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f9eb64aaf2b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7f9eb645488a in
QEventLoop::exec(QFlags) () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7f9eb6281fe3 in QThread::exec() () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7f9eb01a25c5 in  () at /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5
#7  0x7f9eb6286c98 in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x7f9eb22816da in start_thread (arg=0x7f9ea2009700) at
pthread_create.c:456
#9  0x7f9eb8c0a17f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:105

Thread 1 (Thread 0x7f9eb91c5900 (LWP 13234)):
[KCrash Handler]
#6  0x4189363b in  ()
#7  0x7f9e873c50c4 in  () at
/usr/lib/x86_64-linux-gnu/libnvidia-glcore.so.381.09
#8  0x7f9e873ca398 in  () at
/usr/lib/x86_64-linux-gnu/libnvidia-glcore.so.381.09
#9  0x7f9e86f98618 in  () at
/usr/lib/x86_64-linux-gnu/libnvidia-glcore.so.381.09
#10 0x7f9eb6cb7484 in QOpenGLTextureGlyphCache::resizeTextureData(int, int)
() at /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5

[krita] [Bug 346534] Color History Ring in Pop-up palette becomes unclickable under certain circumstances

[Raghavendra kamath]

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

Raghavendra kamath  changed:

   What|Removed |Added

 CC||raghavendr.ra...@gmail.com

--- Comment #8 from Raghavendra kamath  ---
Does this still happen in latest krita version. I tried to reproduce the issue
by random and repeatedly right clicking on the popup pallete but for me it is
working as it should. Am I missing something. Can you please check in the
latest version of krita. The popup palette got revamped a bit in 3.0 I think it
may have been solved.

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

[systemsettings] [Bug 378890] New: Disconnects from the internet

[Mariano D . Abadie]

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

Bug ID: 378890
   Summary: Disconnects from the internet
   Product: systemsettings
   Version: 5.9.4
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: mgmarian...@gmail.com
  Target Milestone: ---

Disconnects from the internet after a period of time without surfing. The
equipment is not suspended nor a hymn. Only X amount of time remains inactive.
Time solution: disconnect from the network and reconnect.

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

[krita] [Bug 353474] Hidden icon 'Path editing' for 'Vector Selection'

[Raghavendra kamath]

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

Raghavendra kamath  changed:

   What|Removed |Added

 CC||raghavendr.ra...@gmail.com

--- Comment #4 from Raghavendra kamath  ---
In the upcoming version of krita the path editing tool is always shown,
regardless of the type of layer selected, i Checked this in the krita built
from git master 4.0 alpha and i can edit the vector selection by clicking on
the path editing tool which is always shown.

So I think this bug will be solved in future releases. 
please try the new release with vector tools when it gets released and close
the bug if the problem is solved.

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

[krita] [Bug 369349] Low framerate when drawing with the stabilizer

[Mat]

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

--- Comment #20 from Mat  ---
I'm still with this problem, since 3.0.1
Specs:
-GTX 970 4GB Galax
-AMD FX 8350
-8GB RAM
-WACOM INTUOS PEN S
Please someone help me I really want to go back using krita.

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

[frameworks-kio] [Bug 378889] New: After upgrade from 5.32.0 to 5.33.0, sftp public key authentication fails in dolphin, works from command line

[bugzilla_noreply]

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

Bug ID: 378889
   Summary: After upgrade from 5.32.0 to 5.33.0, sftp public key
authentication fails in dolphin, works from command
line
   Product: frameworks-kio
   Version: 5.33.0
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: fa...@kde.org
  Reporter: walmartshop...@msn.com
CC: kdelibs-b...@kde.org
  Target Milestone: ---

I connect to an Amazon EC2 server daily which requires public key ssh
authentication. This morning I upgraded to frameworks 5.33.0, and now I get
"Authentication Failed" when trying to connect to the server in dolphin via
sftp.  I have not changed anything in my ssh config or kde wallet.  I can still
connect from the command line without issues. I have the following entry in my
~/.ssh/config file:

Host 
  User ec2-user
  IdentityFile ~/amazon_key.pem

I downgraded to frameworks 5.32 and it started working again.

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

[plasmashell] [Bug 378887] Keyboard doesn't work in text fields - some problem with polkit ?

[bugzilla_noreply]

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

--- Comment #2 from oc...@ichf.edu.pl ---
Finally, I used the other solution from
https://askubuntu.com/questions/838613/keyboard-not-working-properly-in-kde-after-upgrade-to-kubuntu-16-10
:

###

sudo apt purge ibus
sudo apt install fcitx
sudo dpkg-reconfigure fcitx
sudo reboot

###

This solution seems to work.

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

[krusader] [Bug 280270] Saved Locked Tabs each create extra tab on start

[Alex Bikadorov]

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

Alex Bikadorov  changed:

   What|Removed |Added

 CC||alex.bikado...@kdemail.net

--- Comment #2 from Alex Bikadorov  ---
Still in 2.6.0

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

[krita] [Bug 340300] Reset Original Preset Button does not reset the brush size of Eraser Mode

[Raghavendra kamath]

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

Raghavendra kamath  changed:

   What|Removed |Added

 CC||raghavendr.ra...@gmail.com

--- Comment #1 from Raghavendra kamath  ---
Is this still happening in krita for you.

I am using krita built from source (latest git master - 4.0 alpha - git 9D352f0
) on arch linux . I cannot reproduce this issue in krita. 

The eraser size doesn't remain the same when I switch it on across preset

for example 
1) When I select fill circle the size of brush is 50 px, I switch to eraser,
the size of eraser now is 50px

2) when I click on the airbrush pressure brush preset the size of the brush
becomes 400px , and when I switch to eraser mode the size is 400px and not 50px
from previous brush.

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

[dolphin] [Bug 378888] New: Copy Dropbox Link does not work anymore

[rjx_]

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

Bug ID: 37
   Summary: Copy Dropbox Link does not work anymore
   Product: dolphin
   Version: 16.12.3
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: plugins: dropbox
  Assignee: emmanuelpescosta...@gmail.com
  Reporter: 7c6s4b+cc6efdty3b...@sharklasers.com
CC: dolphin-bugs-n...@kde.org
  Target Milestone: ---

According to official help entry https://www.dropbox.com/help/16 direct links
from public folder were disabled for basic accounts (and they are planning to
get rid of it for paid ones too in september) from 15 march on. And sure thing
creation of them from dolphin's plugin menu entry does not work anymore
(curiously selecting this entry hangs plasma for a little while in my case).
And as of 23.4.19 version of official linux Dropbox client "Create Dropbox
Link" in dolphin does not work for any other folder or file either, however
according to the same help entry creation of "shared links" should still work.
I unfortunately never used this feature and can't really remember if menu for
creating shared links ever existed in dolphin, nor have I tested other Dropbox
related menu entries - they might be broken too now for all i know.

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

[plasmashell] [Bug 378887] Keyboard doesn't work in text fields - some problem with polkit ?

[bugzilla_noreply]

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

--- Comment #1 from oc...@ichf.edu.pl ---
The same problem was reported here:

https://askubuntu.com/questions/838613/keyboard-not-working-properly-in-kde-after-upgrade-to-kubuntu-16-10

I used their script.

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

[plasmashell] [Bug 378887] New: Keyboard doesn't work in text fields - some problem with polkit ?

[bugzilla_noreply]

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

Bug ID: 378887
   Summary: Keyboard doesn't work in text fields - some problem
with polkit ?
   Product: plasmashell
   Version: 5.9.4
  Platform: Kubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: oc...@ichf.edu.pl
CC: bhus...@gmail.com, plasma-b...@kde.org
  Target Milestone: 1.0

Keyboard doesn't work in text fields of plasma applications, for example:
- When I use Alt+F2 to run an application, I can't enter any text in the text
field.
- When I click on the main menu on bottom panel and try to search something in
the text field "Type to search".
- When the updater notifies about a new updates and wants me to enter password.

I am using a system where Ubuntu packages were installed first, and then I
additionally installed kubuntu-desktop and all the other corresponding
packages.

The problem disappears after I run the following script to restart plasmashell,
 krunner, and polkit-kde-authentication-agent-1 :

#

killall plasmashell #to stop plasmashell
kstart plasmashell #to restart plasmashell
killall krunner #to stop krunner
krunner #to start krunner
killall polkit-kde-authentication-agent-1

#

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

[krita] [Bug 333431] Broken canvas input shortcut naming when pressing keys used to switch keyboard layouts

[Raghavendra kamath]

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

Raghavendra kamath  changed:

   What|Removed |Added

 CC||raghavendr.ra...@gmail.com

--- Comment #8 from Raghavendra kamath  ---
I can confirm this happens in latest git master (git 9D252f0) too.
I think the problem here is once you assign Alt + Shift to keyboard layout
change. and try to modify the shortcut in kirta, the moment you press Alt +
shift kde changes your keyboard layout and the shift key is changed. For me it
shows Alt + + , so it depends on your layout.

I think this is similar to alt window drag behaviour problem.

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

[digikam] [Bug 347937] SETUP : Collections added as "Removable Media" change as "Local Collections"

[RJVB]

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

--- Comment #19 from RJVB  ---
How could it NOT be reproducible as long as the Solid framework doesn't provide
the required information, and digiKam itself doesn't remember under which
category a collection was added?

I tested with an external harddisk: added as a removable collection, closed the
Preferences dialog, re-opened that dialog; the new collection was listed under
the regular, fixed collections.

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

[kdev-python] [Bug 378827] Kevelop 4.7, 5.0.x, and 5.1.0 crashes when background parsing is turned on for Unreal Engine 4

[Sven Brauch]

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

--- Comment #4 from Sven Brauch  ---
Alright thanks, I'll try ASAP

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

[kde] [Bug 378886] New: Crash when closing the notification that a panel was just removed

[Mike]

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

Bug ID: 378886
   Summary: Crash when closing the notification that a panel was
just removed
   Product: kde
   Version: unspecified
  Platform: unspecified
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: unassigned-b...@kde.org
  Reporter: noeero...@gmail.com
  Target Milestone: ---

Application: plasmashell (5.9.90)

Qt Version: 5.8.0
Frameworks Version: 5.33.0
Operating System: Linux 4.10.9-1-default x86_64
Distribution: "openSUSE Tumbleweed"

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

I had just removed a panel that I was using to play with Latte Dock.  The
generic "panel removed" notification appeared and I closed it, then the plasma
crash.

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

Thread 7 (Thread 0x7f733629d700 (LWP 25661)):
#0  0x7f73ed5417bd in poll () at /lib64/libc.so.6
#1  0x7f73e8120a86 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7f73e8120b9c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#3  0x7f73ede4f91b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#4  0x7f73eddfc52a in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#5  0x7f73edc3aa5b in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#6  0x7f733785bdf7 in KCupsConnection::run() () at
/usr/lib64/libkcupslib.so
#7  0x7f73edc3f469 in QThreadPrivate::start(void*) () at
/usr/lib64/libQt5Core.so.5
#8  0x7f73ecaf1537 in start_thread () at /lib64/libpthread.so.0
#9  0x7f73ed54b04f in clone () at /lib64/libc.so.6

Thread 6 (Thread 0x7f73511b7700 (LWP 25618)):
#0  0x7f73ecaf79a6 in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f735484c0da in  () at /usr/lib64/dri/r600_dri.so
#2  0x7f735484bed7 in  () at /usr/lib64/dri/r600_dri.so
#3  0x7f73ecaf1537 in start_thread () at /lib64/libpthread.so.0
#4  0x7f73ed54b04f in clone () at /lib64/libc.so.6

Thread 5 (Thread 0x7f73d6291700 (LWP 25616)):
#0  0x7f73ecaf79a6 in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f73f354b9d4 in  () at /usr/lib64/libQt5Script.so.5
#2  0x7f73f354ba19 in  () at /usr/lib64/libQt5Script.so.5
#3  0x7f73ecaf1537 in start_thread () at /lib64/libpthread.so.0
#4  0x7f73ed54b04f in clone () at /lib64/libc.so.6

Thread 4 (Thread 0x7f73d8139700 (LWP 25579)):
#0  0x7f73ede4f0f0 in postEventSourcePrepare(_GSource*, int*) () at
/usr/lib64/libQt5Core.so.5
#1  0x7f73e811ff7d in g_main_context_prepare () at
/usr/lib64/libglib-2.0.so.0
#2  0x7f73e81209ab in  () at /usr/lib64/libglib-2.0.so.0
#3  0x7f73e8120b9c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#4  0x7f73ede4f91b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#5  0x7f73eddfc52a in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#6  0x7f73edc3aa5b in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#7  0x7f73f0cdf925 in  () at /usr/lib64/libQt5Qml.so.5
#8  0x7f73edc3f469 in QThreadPrivate::start(void*) () at
/usr/lib64/libQt5Core.so.5
#9  0x7f73ecaf1537 in start_thread () at /lib64/libpthread.so.0
#10 0x7f73ed54b04f in clone () at /lib64/libc.so.6

Thread 3 (Thread 0x7f73d99dd700 (LWP 25510)):
#0  0x7f73ed5417bd in poll () at /lib64/libc.so.6
#1  0x7f73e8120a86 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7f73e8120b9c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#3  0x7f73ede4f91b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#4  0x7f73eddfc52a in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#5  0x7f73edc3aa5b in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#6  0x7f73f0cdf925 in  () at /usr/lib64/libQt5Qml.so.5
#7  0x7f73edc3f469 in QThreadPrivate::start(void*) () at
/usr/lib64/libQt5Core.so.5
#8  0x7f73ecaf1537 in start_thread () at /lib64/libpthread.so.0
#9  0x7f73ed54b04f in clone () at /lib64/libc.so.6

Thread 2 (Thread 0x7f73e0fc5700 (LWP 25470)):
#0  0x7f73ed5417bd in poll () at /lib64/libc.so.6
#1  0x7f73e8120a86 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7f73e8120b9c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#3  0x7f73ede4f91b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#4  0x7f73eddfc52a in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#5  0x7f73edc3aa5b in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#6  0x7f73ee266315 in  () at /usr/lib64/libQt5DBus.so.5
#7  0x7f73edc3f469 in 

[marble] [Bug 378885] New: Marble crashes sometime when using the vector map theme

[Bernhard Beschow]

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

Bug ID: 378885
   Summary: Marble crashes sometime when using the vector map
theme
   Product: marble
   Version: unspecified
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: marble-b...@kde.org
  Reporter: shen...@gmail.com
  Target Milestone: ---

Application: marble (2.2.20 (2.3 development version))

Qt Version: 5.8.0
Frameworks Version: 5.33.0
Operating System: Linux 4.10.9-1-ARCH x86_64
Distribution (Platform): Archlinux Packages

-- Information about the crash:
When using the vector map theme, Marble crashes sproadically with this
backtrace.

The crash can be reproduced sometimes.

-- Backtrace:
Application: Marble – Virtueller Globus (marble), signal: Segmentation fault
Using host libthread_db library "/usr/lib/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fbf631ce7c0 (LWP 25989))]

Thread 10 (Thread 0x7fbede218700 (LWP 26025)):
#0  0x7fbf58a20b63 in pthread_cond_timedwait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7fbf5eea84c6 in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/libQt5Core.so.5
#2  0x7fbf5eea3bc4 in  () at /usr/lib/libQt5Core.so.5
#3  0x7fbf5eea76d8 in  () at /usr/lib/libQt5Core.so.5
#4  0x7fbf58a1a2e7 in start_thread () at /usr/lib/libpthread.so.0
#5  0x7fbf5e5a354f in clone () at /usr/lib/libc.so.6

Thread 9 (Thread 0x7fbedea19700 (LWP 26024)):
#0  0x7fbf5e59967d in poll () at /usr/lib/libc.so.6
#1  0x7fbf561aa7a6 in  () at /usr/lib/libglib-2.0.so.0
#2  0x7fbf561aa8bc in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#3  0x7fbf5f0d706b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#4  0x7fbf5f08089a in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#5  0x7fbf5eea2a73 in QThread::exec() () at /usr/lib/libQt5Core.so.5
#6  0x7fbf5eea76d8 in  () at /usr/lib/libQt5Core.so.5
#7  0x7fbf58a1a2e7 in start_thread () at /usr/lib/libpthread.so.0
#8  0x7fbf5e5a354f in clone () at /usr/lib/libc.so.6

Thread 8 (Thread 0x7fbee4cce700 (LWP 26007)):
#0  0x7fbf58a20b63 in pthread_cond_timedwait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7fbf5eea84c6 in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/libQt5Core.so.5
#2  0x7fbf5eea3bc4 in  () at /usr/lib/libQt5Core.so.5
#3  0x7fbf5eea76d8 in  () at /usr/lib/libQt5Core.so.5
#4  0x7fbf58a1a2e7 in start_thread () at /usr/lib/libpthread.so.0
#5  0x7fbf5e5a354f in clone () at /usr/lib/libc.so.6

Thread 7 (Thread 0x7fbee7fff700 (LWP 25998)):
#0  0x7fbf58a20756 in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7fbf5cb91563 in  () at /usr/lib/libQt5WebKit.so.5
#2  0x7fbf5cec9781 in  () at /usr/lib/libQt5WebKit.so.5
#3  0x7fbf58a1a2e7 in start_thread () at /usr/lib/libpthread.so.0
#4  0x7fbf5e5a354f in clone () at /usr/lib/libc.so.6

Thread 6 (Thread 0x7fbeeceea700 (LWP 25997)):
#0  0x7fbf58a20756 in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7fbf5cb90411 in  () at /usr/lib/libQt5WebKit.so.5
#2  0x7fbf5cec9781 in  () at /usr/lib/libQt5WebKit.so.5
#3  0x7fbf58a1a2e7 in start_thread () at /usr/lib/libpthread.so.0
#4  0x7fbf5e5a354f in clone () at /usr/lib/libc.so.6

Thread 5 (Thread 0x7fbf2de0b700 (LWP 25996)):
#0  0x7fbf58a20756 in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7fbf5ce9860b in  () at /usr/lib/libQt5WebKit.so.5
#2  0x7fbf5ce98649 in  () at /usr/lib/libQt5WebKit.so.5
#3  0x7fbf58a1a2e7 in start_thread () at /usr/lib/libpthread.so.0
#4  0x7fbf5e5a354f in clone () at /usr/lib/libc.so.6

Thread 4 (Thread 0x7fbf448eb700 (LWP 25992)):
#0  0x7ffee81f3b02 in clock_gettime ()
#1  0x7fbf5e5b0826 in clock_gettime () at /usr/lib/libc.so.6
#2  0x7fbf5f0d6201 in  () at /usr/lib/libQt5Core.so.5
#3  0x7fbf5f0d49c9 in QTimerInfoList::updateCurrentTime() () at
/usr/lib/libQt5Core.so.5
#4  0x7fbf5f0d69c5 in  () at /usr/lib/libQt5Core.so.5
#5  0x7fbf561aa1a9 in g_main_context_check () at /usr/lib/libglib-2.0.so.0
#6  0x7fbf561aa744 in  () at /usr/lib/libglib-2.0.so.0
#7  0x7fbf561aa8bc in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#8  0x7fbf5f0d706b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#9  0x7fbf5f08089a in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#10 0x7fbf5eea2a73 in QThread::exec() () at /usr/lib/libQt5Core.so.5
#11 0x7fbf5eea76d8 in  () at /usr/lib/libQt5Core.so.5
#12 0x7fbf58a1a2e7 in start_thread () at /usr/lib/libpthread.so.0
#13 0x7fbf5e5a354f in clone () at /usr/lib/libc.so.6

Thread 3 (Thread 0x7fbf450ec700 (LWP 25991)):
#0  0x7ffee81f3b02 in 

[systemsettings] [Bug 378875] Reverse Scoll direction not working after 17.04 upgrade

[bugzilla_noreply]

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

i...@gmx.net changed:

   What|Removed |Added

   Platform|Other   |Kubuntu Packages

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

[frameworks-baloo] [Bug 378884] New: baloosearch doesn't respect --directory parameter

[Saman]

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

Bug ID: 378884
   Summary: baloosearch doesn't respect --directory parameter
   Product: frameworks-baloo
   Version: 5.33.0
  Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Engine
  Assignee: pinak.ah...@gmail.com
  Reporter: svps777+...@gmail.com
  Target Milestone: ---

When I try to limit the search with --directory, I'll see the result from other
sibling directories. For example:

$ pwd
/home/foo/Music Video/Imagine Dragons
$ baloosearch -d . ""

I can see unexpected results such as:

/home/foo/Music Video/Infernal/ 

but I only see the unexpected results from sibling directories. It seems it
limit the result to the parent directory (--directory /home/foo/Music Video).

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

[kdevelop] [Bug 378883] New: Source code editor can become unresponsive temporarily.

[Markus Elfring]

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

Bug ID: 378883
   Summary: Source code editor can become unresponsive
temporarily.
   Product: kdevelop
   Version: 5.1.0
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: All editors
  Assignee: kdevelop-bugs-n...@kde.org
  Reporter: markus.elfr...@web.de
  Target Milestone: ---

I am trying the application “KDevelop 5.1.0-26.1” out. I have noticed that the
editor can become unresponsive for a while as I am adjusting and navigating
through source code from Linux modules. The read rate can increase over 2 M/s
for my local hard disk during such a data processing event and a processor core
could be almost fully busy for this case.

I find these hiccups strange at the moment. I have not found an editing pattern
so far with which I could reproduce undesired run time behaviour long enough.

My observations might be similar to information from a bug report like
“KDevelop editor become unresponsive when clicking into a problem”.
https://bugs.kde.org/show_bug.cgi?id=372040

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

[digikam] [Bug 378804] lensfun uses only one core, pls. parallize [patch]

[Maik Qualmann]

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

--- Comment #8 from Maik Qualmann  ---
Created attachment 105063
  --> https://bugs.kde.org/attachment.cgi?id=105063=edit
lensfunfilter.patch

fix vignetting / color correction and distortion / geometry corrections.

Maik

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

[kdev-python] [Bug 378827] Kevelop 4.7, 5.0.x, and 5.1.0 crashes when background parsing is turned on for Unreal Engine 4

[Michael G Hart]

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

--- Comment #3 from Michael G Hart  ---
Sorry but I don't have anything bug in symbols. However with all the
versions of kdevelop I tried I got the same failure wedding background
parsing was turned on
So I would be very surprised if you cannot replicate the problem.


On Apr 17, 2017 12:02 PM, "Sven Brauch"  wrote:

> https://bugs.kde.org/show_bug.cgi?id=378827
>
> --- Comment #2 from Sven Brauch  ---
> Do you have debug symbols by any chance? Otherwise I can also try to
> reproduce
> this ...
>
> --
> You are receiving this mail because:
> You reported the bug.

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

[digikam] [Bug 378804] lensfun uses only one core, pls. parallize [patch]

[Maik Qualmann]

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

Maik Qualmann  changed:

   What|Removed |Added

 Attachment #105056|0   |1
is obsolete||

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

[konversation] [Bug 378882] New: symbols in nickname not handled well "`"

[LtWorf]

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

Bug ID: 378882
   Summary: symbols in nickname not handled well "`"
   Product: konversation
   Version: 1.6.2
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: konversation-de...@kde.org
  Reporter: tipos...@tiscali.it
  Target Milestone: ---

If someone has a ` in the nickname, clicking on it opens a query tab that
includes the HTML escape, not the real nickname of the user.

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

[KScreen] [Bug 378881] New: Laptop screen doesn't wake up after disconnecting HDMI

[Simone Gaiarin]

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

Bug ID: 378881
   Summary: Laptop screen doesn't wake up after disconnecting HDMI
   Product: KScreen
   Version: 5.9.4
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: common
  Assignee: se...@kde.org
  Reporter: simg...@gmail.com
  Target Milestone: ---

When I attach the HDMI cable the laptop screen turns off, leaving only the
external monitor on according to my configuration.

When I detach the HDMI cable the laptop screen doesn't turn on. This happens
both when I only attach the HDMI external monitor and also when I attach it
while the laptop is connected to a docking station with another external
monitor.

Another strange thing is that sometimes, when I connect the HDMI external
monitor and I open the configuration dialog, the HDMI output is marked as
disabled even though is in fact enabled and working.

Kscreen seems to not produce kscreen.log, so I cannot provide that type of
extra information.

Kscreen 4.9.4
Kernel 4.9.22
Graphics:  Card: Intel Haswell-ULT Integrated Graphics Controller
   Display Server: X.Org 1.19.3 driver: intel Resolution:
1920x1080@60.02hz, 1920x1080@60.00hz
   GLX Renderer: Mesa DRI Intel Haswell Mobile GLX Version: 3.0 Mesa
17.0.3

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

[kmail2] [Bug 378315] KMail crash on logout

[Gerd Fleischer]

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

Gerd Fleischer  changed:

   What|Removed |Added

 CC||gerdfleisc...@web.de

--- Comment #2 from Gerd Fleischer  ---
I installed some debug packages,
here is what is in xsession-errors,
saving log was not possible yet.

ksmserver: SmsDie WM timeout
4 "#83 0x00403974 in main (argc=1, argv=0x7ffcd2cb4c98) at
/usr/src/debug/kmail-17.03.80/src/main.cpp:163\n"
4 "#82 0x7ff8b3337ece in KMKernel::cleanup (this=this@entry=0x7ffcd2cb4a80)
at /usr/src/debug/kmail-17.03.80/src/kmkernel.cpp:1153\n"
4 "#81 KMKernel::closeAllKMailWindows (this=this@entry=0x7ffcd2cb4a80) at
/usr/src/debug/kmail-17.03.80/src/kmkernel.cpp:1138\n"
4 "#80 qDeleteAll > (c=...) at
/usr/include/qt5/QtCore/qalgorithms.h:328\n"
4 "#79 0x7ff8b332fd27 in qDeleteAll::const_iterator>
(end=..., begin=...) at /usr/include/qt5/QtCore/qalgorithms.h:320\n"
4 "#78 0x7ff8b331e319 in KMMainWin::~KMMainWin (this=0x14f0c30,
__in_chrg=, __vtt_parm=) at
/usr/src/debug/kmail-17.03.80/src/kmmainwin.cpp:100\n"
4 "#77 0x7ff8b331e2c4 in KMMainWin::~KMMainWin (this=this@entry=0x14f0c30,
__in_chrg=, __vtt_parm=) at
/usr/src/debug/kmail-17.03.80/src/kmmainwin.cpp:95\n"
3 "#76 0x7ff8b06c7cb4 in KMainWindow::~KMainWindow() () from
/usr/lib64/libKF5XmlGui.so.5\n"
3 "#75 0x7ff8b22243b5 in QWidget::~QWidget() () from
/usr/lib64/libQt5Widgets.so.5\n"
3 "#74 0x7ff8b1558f65 in QObjectPrivate::deleteChildren() () from
/usr/lib64/libQt5Core.so.5\n"
4 "#73 0x7ff8b336e019 in KMMainWidget::~KMMainWidget (this=0x14f93a0,
__in_chrg=) at
/usr/src/debug/kmail-17.03.80/src/kmmainwidget.cpp:390\n"
4 "#72 0x7ff8b336de5f in KMMainWidget::~KMMainWidget (this=0x14f93a0,
__in_chrg=) at
/usr/src/debug/kmail-17.03.80/src/kmmainwidget.cpp:389\n"
4 "#71 0x7ff8b336dc73 in KMMainWidget::destruct (this=this@entry=0x14f93a0)
at /usr/src/debug/kmail-17.03.80/src/kmmainwidget.cpp:405\n"
4 "#70 0x7ff8b33514c3 in KMMainWidget::deleteWidgets
(this=this@entry=0x14f93a0) at
/usr/src/debug/kmail-17.03.80/src/kmmainwidget.cpp:967\n"
3 "#69 0x7ff8b235ec59 in QSplitter::~QSplitter() () from
/usr/lib64/libQt5Widgets.so.5\n"
3 "#68 0x7ff8b22243b5 in QWidget::~QWidget() () from
/usr/lib64/libQt5Widgets.so.5\n"
3 "#67 0x7ff8b1558f65 in QObjectPrivate::deleteChildren() () from
/usr/lib64/libQt5Core.so.5\n"
3 "#66 0x7ff8b235ec59 in QSplitter::~QSplitter() () from
/usr/lib64/libQt5Widgets.so.5\n"
3 "#65 0x7ff8b22243b5 in QWidget::~QWidget() () from
/usr/lib64/libQt5Widgets.so.5\n"
3 "#64 0x7ff8b1558f65 in QObjectPrivate::deleteChildren() () from
/usr/lib64/libQt5Core.so.5\n"
4 "#63 0x7ff8b331ec89 in KMReaderWin::~KMReaderWin (this=0x1582610,
__in_chrg=) at
/usr/src/debug/kmail-17.03.80/src/kmreaderwin.cpp:248\n"
3 "#62 0x7ff8b22243b5 in QWidget::~QWidget() () from
/usr/lib64/libQt5Widgets.so.5\n"
3 "#61 0x7ff8b1558f65 in QObjectPrivate::deleteChildren() () from
/usr/lib64/libQt5Core.so.5\n"
4 "#60 0x7ff8ada8f739 in MessageViewer::Viewer::~Viewer (this=0x15e9440,
__in_chrg=) at
/usr/src/debug/messagelib-17.03.80/messageviewer/src/viewer/viewer.cpp:62\n"
3 "#59 0x7ff8b22243b5 in QWidget::~QWidget() () from
/usr/lib64/libQt5Widgets.so.5\n"
3 "#58 0x7ff8b1558f65 in QObjectPrivate::deleteChildren() () from
/usr/lib64/libQt5Core.so.5\n"
4 "#57 0x7ff8ada9f919 in MessageViewer::ViewerPrivate::~ViewerPrivate
(this=0x15a2090, __in_chrg=) at
/usr/src/debug/messagelib-17.03.80/messageviewer/src/viewer/viewer_p.cpp:304\n"
4 "#56 0x7ff8ada9f744 in MessageViewer::ViewerPrivate::~ViewerPrivate
(this=0x15a2090, __in_chrg=) at
/usr/src/debug/messagelib-17.03.80/messageviewer/src/viewer/viewer_p.cpp:299\n"
4 "#55 0x7ff8adaefb89 in
MessageViewer::MailWebEngineView::~MailWebEngineView (this=0x16452c0,
__in_chrg=) at
/usr/src/debug/messagelib-17.03.80/messageviewer/src/viewer/webengine/mailwebengineview.cpp:121\n"
3 "#54 0x7ff8b22243b5 in QWidget::~QWidget() () from
/usr/lib64/libQt5Widgets.so.5\n"
3 "#53 0x7ff8b1558f65 in QObjectPrivate::deleteChildren() () from
/usr/lib64/libQt5Core.so.5\n"
4 "#52 0x7ff8adaf1ff9 in
MessageViewer::MailWebEnginePage::~MailWebEnginePage (this=0x168ff80,
__in_chrg=) at
/usr/src/debug/messagelib-17.03.80/messageviewer/src/viewer/webengine/mailwebenginepage.cpp:41\n"
4 "#51 QWebEnginePage::~QWebEnginePage (this=0x168ff80, __in_chrg=) at api/qwebenginepage.cpp:802\n"
4 "#50 QScopedPointer::~QScopedPointer
(this=0x168ff90, __in_chrg=) at
/usr/include/qt5/QtCore/qscopedpointer.h:107\n"
4 "#49 0x7ff89be99790 in
QScopedPointerDeleter::cleanup (pointer=)
at /usr/include/qt5/QtCore/qscopedpointer.h:60\n"
4 "#48 0x7ff89be9a639 in 

[ktorrent] [Bug 378833] Wrong web site link in About

[Burkhard Lueck]

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

Burkhard Lueck  changed:

   What|Removed |Added

 Resolution|--- |FIXED
  Latest Commit||https://commits.kde.org/kto
   ||rrent/0ce4f5cdb642b89d4557a
   ||c3b612fc5921b334397
 Status|UNCONFIRMED |RESOLVED

--- Comment #1 from Burkhard Lueck  ---
Git commit 0ce4f5cdb642b89d4557ac3b612fc5921b334397 by Burkhard Lück.
Committed on 17/04/2017 at 16:33.
Pushed by lueck into branch 'master'.

Fix link to obsolete website

replace ktorrent.org with kde.org/applications/internet/ktorrent/

Differential Revision: https://phabricator.kde.org/D5480

M  +2-2ktorrent/main.cpp
M  +1-1ktupnptest/main.cpp
M  +1-1plasma/applet/plasma-applet-ktorrent.desktop
M  +1-1plugins/bwscheduler/ktorrent_bwscheduler.desktop
M  +1-1plugins/downloadorder/ktorrent_downloadorder.desktop
M  +1-1plugins/infowidget/ktorrent_infowidget.desktop
M  +1-1plugins/ipfilter/ktorrent_ipfilter.desktop
M  +1-1plugins/logviewer/ktorrent_logviewer.desktop
M  +1-1plugins/magnetgenerator/ktorrent_magnetgenerator.desktop
M  +1-1plugins/mediaplayer/ktorrent_mediaplayer.desktop
M  +1-1plugins/scanfolder/ktorrent_scanfolder.desktop
M  +1-1plugins/scripting/ktorrent_scripting.desktop
M  +1-1plugins/scripting/scripts/auto_remove/auto_remove.desktop
M  +1-1plugins/scripting/scripts/auto_resume/auto_resume.desktop
M  +1-1   
plugins/scripting/scripts/email_notifications/email_notifications.desktop
M  +1-1plugins/scripting/scripts/tracker_groups/tracker_groups.desktop
M  +1-1plugins/search/ktorrent_search.desktop
M  +1-1plugins/shutdown/ktorrent_shutdown.desktop
M  +1-1plugins/stats/ktorrent_stats.desktop
M  +1-1plugins/syndication/ktorrent_syndication.desktop
M  +1-1plugins/upnp/ktorrent_upnp.desktop
M  +1-1plugins/webinterface/ktwebinterfaceplugin.desktop
M  +1-1plugins/zeroconf/ktorrent_zeroconf.desktop

https://commits.kde.org/ktorrent/0ce4f5cdb642b89d4557ac3b612fc5921b334397

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

[kmail2] [Bug 259813] reading mails in unread mode instantly disappears from list

[Delian Krustev]

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

Delian Krustev  changed:

   What|Removed |Added

 CC||krus...@krustev.net

--- Comment #41 from Delian Krustev  ---
I also find this bug annoying.

I've used KMail from Debian Wheezy - vKMail 4.4.11 (
https://packages.debian.org/wheezy/kmail ). Interestingly, others reported that
the feature was removed in much previous version. It worked for me in 4.4.1
though.

Now I'm with Debian Stretch with KMail 5.2.3 .

A workaround I currently use is to disable the immediate marking of opened
messages as read.

IMHO filters to the message list should only be applied "onChange" of the
filter button, as it previously was.

And guys, thanks for the wonderful software!
I've been using it for a decade .. or more ;)

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

[kontact] [Bug 378880] New: kontact Signal: Segmentation fault (11)

[Don Curtis]

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

Bug ID: 378880
   Summary: kontact Signal: Segmentation fault (11)
   Product: kontact
   Version: 5.3.0
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdepim-b...@kde.org
  Reporter: bugrprt21...@online.de
  Target Milestone: ---

Created attachment 105061
  --> https://bugs.kde.org/attachment.cgi?id=105061=edit
Complete crash report

Application: kontact (5.3.0 (QtWebEngine))

Qt Version: 5.6.1
Frameworks Version: 5.26.0
Operating System: Linux 4.4.57-18.3-default x86_64
Distribution: "openSUSE Leap 42.2"

-- Information about the crash:
- What I was doing when the application crashed:
In the Address Book, clicked the symbol to change an e-Mail address to the
"preferred address".

-- Backtrace:
Application: Kontact (kontact), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f050e7847c0 (LWP 11239))]

** Shortened crash dump -- complete dump is attached. **

Thread 1 (Thread 0x7f050e7847c0 (LWP 11239)):
[KCrash Handler]
#6  0x7f050bc27254 in
QSortFilterProxyModelPrivate::proxy_to_source(QModelIndex const&) const
(this=0x1c1bf60, proxy_index=...) at itemmodels/qsortfilterproxymodel.cpp:185
#7  0x7f050bc27254 in
QSortFilterProxyModelPrivate::proxy_to_source(QModelIndex const&) const
(this=0x1c1bf60, proxy_index=...) at itemmodels/qsortfilterproxymodel.cpp:377
#8  0x7f050bc2732d in QSortFilterProxyModel::mapToSource(QModelIndex
const&) const (this=, proxyIndex=...) at
itemmodels/qsortfilterproxymodel.cpp:2750
#9  0x7f050bc29fce in
QSortFilterProxyModelPrivate::store_persistent_indexes()
(this=this@entry=0x1c1bf60) at itemmodels/qsortfilterproxymodel.cpp:1018
#10 0x7f050bc2e2a6 in
QSortFilterProxyModelPrivate::_q_sourceDataChanged(QModelIndex const&,
QModelIndex const&, QVector const&) (this=0x1c1bf60, source_top_left=...,
source_bottom_right=..., roles=...) at
itemmodels/qsortfilterproxymodel.cpp:1218
#11 0x7f050bc301d8 in QSortFilterProxyModel::qt_static_metacall(QObject*,
QMetaObject::Call, int, void**) (_o=, _c=,
_id=, _a=) at
.moc/moc_qsortfilterproxymodel.cpp:202
#12 0x7f050bc87bb1 in QMetaObject::activate(QObject*, int, int, void**)
(sender=sender@entry=0xa18d570, signalOffset=,
local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7ffcadccd250)
at kernel/qobject.cpp:3730
#13 0x7f050bc88717 in QMetaObject::activate(QObject*, QMetaObject const*,
int, void**) (sender=sender@entry=0xa18d570, m=m@entry=0x7f050c0a3ca0
,
local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7ffcadccd250)
at kernel/qobject.cpp:3595
#14 0x7f050bcfe04c in QAbstractItemModel::dataChanged(QModelIndex const&,
QModelIndex const&, QVector const&) (this=this@entry=0xa18d570, _t1=...,
_t2=..., _t3=...) at .moc/moc_qabstractitemmodel.cpp:566
#15 0x7f050bc2e413 in
QSortFilterProxyModelPrivate::_q_sourceDataChanged(QModelIndex const&,
QModelIndex const&, QVector const&) (this=0xa18d590, source_top_left=...,
source_bottom_right=..., roles=...) at
itemmodels/qsortfilterproxymodel.cpp:1251
#16 0x7f050bc301d8 in QSortFilterProxyModel::qt_static_metacall(QObject*,
QMetaObject::Call, int, void**) (_o=, _c=,
_id=, _a=) at
.moc/moc_qsortfilterproxymodel.cpp:202
#17 0x7f050bc87bb1 in QMetaObject::activate(QObject*, int, int, void**)
(sender=sender@entry=0x1ccbae0, signalOffset=,
local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7ffcadccd580)
at kernel/qobject.cpp:3730
#18 0x7f050bc88717 in QMetaObject::activate(QObject*, QMetaObject const*,
int, void**) (sender=sender@entry=0x1ccbae0, m=m@entry=0x7f050c0a3ca0
,
local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7ffcadccd580)
at kernel/qobject.cpp:3595
#19 0x7f050bcfe04c in QAbstractItemModel::dataChanged(QModelIndex const&,
QModelIndex const&, QVector const&) (this=this@entry=0x1ccbae0, _t1=...,
_t2=..., _t3=...) at .moc/moc_qabstractitemmodel.cpp:566
#20 0x7f050a7aad3f in
Akonadi::EntityTreeModelPrivate::dataChanged(QModelIndex const&, QModelIndex
const&) (this=this@entry=0x3b56300, top=..., bottom=...) at
/usr/src/debug/akonadi-16.08.2/src/core/models/entitytreemodel_p.cpp:1703
#21 0x7f050a7b198b in
Akonadi::EntityTreeModelPrivate::monitoredItemChanged(Akonadi::Item const&,
QSet const&) (this=0x3b56300, item=...) at
/usr/src/debug/akonadi-16.08.2/src/core/models/entitytreemodel_p.cpp:1167
#22 0x7f050bc87bb1 in QMetaObject::activate(QObject*, int, int, void**)
(sender=0x77e9940, signalOffset=,
local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7ffcadccd850)
at kernel/qobject.cpp:3730
#23 0x7f050bc88717 in QMetaObject::activate(QObject*, QMetaObject const*,
int, void**) (sender=, m=m@entry=0x7f050aa46e00
,
local_signal_index=local_signal_index@entry=0,