[plasma-pa] [Bug 372419] New: Have shortcut to audio / multimedia settings

[Daniel]

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

Bug ID: 372419
   Summary: Have shortcut to audio / multimedia settings
   Product: plasma-pa
   Version: 5.8.3
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: applet
  Assignee: now...@gmail.com
  Reporter: mayazcherq...@gmail.com
CC: plasma-b...@kde.org
  Target Milestone: ---

Often times I open the audio plasmoid on the panel wanting to do something,
only to realise it can't and I have to do it in system settings (namely
selecting audio output device for an application). The way it currently is, I
have to close the plasmoid, open the Dash, open System Settings, then go to
Multimedia Settings. 

Just being able to click on a settings button on the plasmoid to take me to
Multimedia Settings would be so much more preferable.

Thank you.

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

[frameworks-knotifications] [Bug 372418] New: Have notifications / notification icons show on the users lock screen

[Daniel]

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

Bug ID: 372418
   Summary: Have notifications / notification icons show on the
users lock screen
   Product: frameworks-knotifications
   Version: 5.27.0
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: mklape...@kde.org
  Reporter: mayazcherq...@gmail.com
CC: kdelibs-b...@kde.org
  Target Milestone: ---

Please add the ability to show a users sessions notifications when on the SDDM
lock screen. Ssimilar to what Android offers (show no notifications, show
notification icons only, show full notifications).

GNOME only does the "show notification icons only" part, but it preferably (for
me) it would be better to also have the "show full notifications" part.

Thank you.

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

[gwenview] [Bug 372417] New: Entering fullscreen will switch to other monitor

[Daniel]

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

Bug ID: 372417
   Summary: Entering fullscreen will switch to other monitor
   Product: gwenview
   Version: Other (add details in bug description)
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: gwenview-bugs-n...@kde.org
  Reporter: mayazcherq...@gmail.com
CC: myr...@kde.org
  Target Milestone: ---

When entering fullscreen on Gwenview, it will always seem to move to my second
monitor for some reason, no matter the monitor I have the window initially
placed on (first, or second). There is no option to control this, either, as
far as I can see.

Using version: 16.08.3 (Frameworks 5.27.0, Qt 5.7.0)

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

[gwenview] [Bug 372416] New: Make scrollwheel zoom/unzoom images

[Daniel]

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

Bug ID: 372416
   Summary: Make scrollwheel zoom/unzoom images
   Product: gwenview
   Version: Other (add details in bug description)
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: gwenview-bugs-n...@kde.org
  Reporter: mayazcherq...@gmail.com
CC: myr...@kde.org
  Target Milestone: ---

At the moment, in order to zoom in / zoom out of an image, I have to hold down
the Ctrl key and then use the scroll wheel to zoom in and out, rather than the
much more familiar action of just scrolling and zooming in / out (no holding
down Ctrl key).

Please make it so that scrolling the mouse wheel will zoom in and out.

Thank you.

Using version: 16.08.3 (Frameworks 5.27.0, Qt 5.7.0)

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

[systemsettings] [Bug 372415] New: Default Applications: Update gvfs if present.

[Daniel]

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

Bug ID: 372415
   Summary: Default Applications: Update gvfs if present.
   Product: systemsettings
   Version: 5.8.3
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: minor
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: mayazcherq...@gmail.com
  Target Milestone: ---

If gvfs is present on the system, when a default application is selected /
change, update gvfs too.

Why? Because some applications use it.

My use-case:

I use HexChat as my IRC client. I like to use Google Chrome as my web browser.
I installed Chrome first. I then installed Firefox later (for testing some
website layouts). Now all links in HexChat, when clicked, open Firefox and not
my default browser (Chrome). No matter what I do, I cannot change this.

Thanks. :-)

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

[krita] [Bug 372414] в

[Владимир]

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

--- Comment #1 from Владимир  ---
Слишком мало профиля кистей

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

[krita] [Bug 372414] в

[Владимир]

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

Владимир  changed:

   What|Removed |Added

 CC||nahapetyan.volo...@gmail.co
   ||m

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

[krita] [Bug 372414] New: в

[Владимир]

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

Bug ID: 372414
   Summary: в
   Product: krita
   Version: 3.0.1.1
  Platform: MS Windows
OS: MS Windows
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Brush engine
  Assignee: krita-bugs-n...@kde.org
  Reporter: nahapetyan.volo...@gmail.com
  Target Milestone: ---

Created attachment 102199
  --> https://bugs.kde.org/attachment.cgi?id=102199=edit
слишком мало кистей

Слишком мало профиля кистей

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

[Discover] [Bug 372277] Discover crashes when used to open rpm file

[Mustafa Muhammad]

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

--- Comment #4 from Mustafa Muhammad  ---
(In reply to Rex Dieter from comment #3)
> I didn't think discover supported installing packages directly, it's desktop
> file only contains:
> MimeType=x-scheme-handler/appstream;
> 
> (no mention of package mimetypes)

Maybe it doesn't, I was trying, and I think it should support this.

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

[plasmashell] [Bug 359220] Widgets can't be moved or resized and right-side menu isn't shown regardless of widgets being locked or unlocked

[Christoph Feck]

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

Christoph Feck  changed:

   What|Removed |Added

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

--- Comment #7 from Christoph Feck  ---
Can you confirm that the steps explained in comment #2 resolve the issue?

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

[frameworks-kwidgetsaddons] [Bug 372392] Remains the bug 359220 (on Plasma 5.8.3) : Widgets can't be moved or resized and right-side menu isn't shown regardless of widgets being locked or unlocked

[Christoph Feck]

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

Christoph Feck  changed:

   What|Removed |Added

 Resolution|--- |INVALID
 Status|UNCONFIRMED |RESOLVED

--- Comment #2 from Christoph Feck  ---
Already reported as bug 359220.

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

[dolphin] [Bug 371130] unable to reassign standard shortcut for backspace to "up" instead of "back"

[S . Christian Collins]

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

--- Comment #6 from S. Christian Collins  ---
Aah, so the real problem seems to be that not all of the assigned shortcut keys
for "Back" are visible in System Settings -> Shortcuts, or the "Configure
Shortcuts" option within the individual programs.

Thanks for the workaround, jingyu9575!

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

[kwin] [Bug 372413] New: Yast - Partitioner

[Paul Adams]

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

Bug ID: 372413
   Summary: Yast  - Partitioner
   Product: kwin
   Version: 5.8.3
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kwin-bugs-n...@kde.org
  Reporter: paul.zrexx...@gmail.com
  Target Milestone: ---

Application: kwin_x11 (5.8.3)

Qt Version: 5.7.0
Frameworks Version: 5.27.0
Operating System: Linux 4.8.6-2-default x86_64
Distribution: "openSUSE Tumbleweed"

-- Information about the crash:
Yast Control Center opened, selected System ---> Partitioner --> Yes in dialog
box

The crash can be reproduced sometimes.

-- Backtrace:
Application: KWin (kwin_x11), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f409a0e2940 (LWP 2915))]

Thread 5 (Thread 0x7f406e5ee700 (LWP 3239)):
#0  0x7f4099a6e751 in ppoll () at /lib64/libc.so.6
#1  0x7f4097142b41 in qt_safe_poll(pollfd*, unsigned long, timespec const*)
() at /usr/lib64/libQt5Core.so.5
#2  0x7f4097144428 in
QEventDispatcherUNIX::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#3  0x7f40970f11ea in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#4  0x7f4096f1f8b3 in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#5  0x7f40918baa75 in  () at /usr/lib64/libQt5Qml.so.5
#6  0x7f4096f24558 in  () at /usr/lib64/libQt5Core.so.5
#7  0x7f4092d89454 in start_thread () at /lib64/libpthread.so.0
#8  0x7f4099a7739f in clone () at /lib64/libc.so.6

Thread 4 (Thread 0x7f405700 (LWP 3017)):
#0  0x7f4092d8f10f in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f40960ac834 in  () at /usr/lib64/libQt5Script.so.5
#2  0x7f40960ac879 in  () at /usr/lib64/libQt5Script.so.5
#3  0x7f4092d89454 in start_thread () at /lib64/libpthread.so.0
#4  0x7f4099a7739f in clone () at /lib64/libc.so.6

Thread 3 (Thread 0x7f406700 (LWP 3005)):
#0  0x7f4099a6e751 in ppoll () at /lib64/libc.so.6
#1  0x7f4097142b41 in qt_safe_poll(pollfd*, unsigned long, timespec const*)
() at /usr/lib64/libQt5Core.so.5
#2  0x7f4097144428 in
QEventDispatcherUNIX::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#3  0x7f40970f11ea in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#4  0x7f4096f1f8b3 in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#5  0x7f40918baa75 in  () at /usr/lib64/libQt5Qml.so.5
#6  0x7f4096f24558 in  () at /usr/lib64/libQt5Core.so.5
#7  0x7f4092d89454 in start_thread () at /lib64/libpthread.so.0
#8  0x7f4099a7739f in clone () at /lib64/libc.so.6

Thread 2 (Thread 0x7f4082bdd700 (LWP 2940)):
#0  0x7f4099a6e751 in ppoll () at /lib64/libc.so.6
#1  0x7f4097142b41 in qt_safe_poll(pollfd*, unsigned long, timespec const*)
() at /usr/lib64/libQt5Core.so.5
#2  0x7f4097144428 in
QEventDispatcherUNIX::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#3  0x7f40970f11ea in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#4  0x7f4096f1f8b3 in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#5  0x7f4090a933e5 in  () at /usr/lib64/libQt5DBus.so.5
#6  0x7f4096f24558 in  () at /usr/lib64/libQt5Core.so.5
#7  0x7f4092d89454 in start_thread () at /lib64/libpthread.so.0
#8  0x7f4099a7739f in clone () at /lib64/libc.so.6

Thread 1 (Thread 0x7f409a0e2940 (LWP 2915)):
[KCrash Handler]
#6  0x7f40918a6130 in QQmlBinding::write(QQmlPropertyData const&,
QV4::Value const&, bool, QFlags) () at
/usr/lib64/libQt5Qml.so.5
#7  0x7f40918a7095 in
QQmlBinding::update(QFlags) () at
/usr/lib64/libQt5Qml.so.5
#8  0x7f40918b0d35 in  () at /usr/lib64/libQt5Qml.so.5
#9  0x7f409183a5fe in QQmlComponentPrivate::complete(QQmlEnginePrivate*,
QQmlComponentPrivate::ConstructionState*) () at /usr/lib64/libQt5Qml.so.5
#10 0x7f409183a6c7 in QQmlComponentPrivate::completeCreate() () at
/usr/lib64/libQt5Qml.so.5
#11 0x7f409183a530 in QQmlComponent::create(QQmlContext*) () at
/usr/lib64/libQt5Qml.so.5
#12 0x7f407c38e4b7 in  () at
/usr/lib64/qt5/plugins/org.kde.kdecoration2/kwin5_aurorae.so
#13 0x7f4099696ed9 in  () at /usr/lib64/libkwin.so.5
#14 0x7f4099577572 in KWin::Client::createDecoration(QRect const&) () at
/usr/lib64/libkwin.so.5
#15 0x7f409957815d in KWin::Client::updateDecoration(bool, bool) () at
/usr/lib64/libkwin.so.5
#16 0x7f40995d7175 in KWin::Client::manage(unsigned int, bool) () at
/usr/lib64/libkwin.so.5
#17 0x7f409955aa84 in KWin::Workspace::createClient(unsigned int, bool) ()
at /usr/lib64/libkwin.so.5
#18 0x7f40995c4387 in KWin::Workspace::workspaceEvent(xcb_generic_event_t*)
() at /usr/lib64/libkwin.so.5
#19 0x7f40970f032f in
QAbstractEventDispatcher::filterNativeEvent(QByteArray const&, void*, long*) ()
at /usr/lib64/libQt5Core.so.5

[ktouch] [Bug 372412] New: ktouch on start traing click font size changes from comfortable 18pt to 4pt unreadable internal crash

[bugzilla_noreply]

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

Bug ID: 372412
   Summary: ktouch on start traing click font size changes from
comfortable 18pt to 4pt unreadable internal crash
   Product: ktouch
   Version: 2.3.0
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: sebastiangottfr...@web.de
  Reporter: dc6...@gmail.com
  Target Milestone: ---

ktouch 2.3.0 no way to change font size or type; 18pt font reduced to 4pt when
start training clicked on unreadable. internal crash may occur

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

[kopete] [Bug 82317] font size is not saved

[bugzilla_noreply]

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

dc6...@gmail.com changed:

   What|Removed |Added

 CC||dc6...@gmail.com

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

[frameworks-kio] [Bug 372411] New: MTP flickers with android

[Olivier Churlaud]

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

Bug ID: 372411
   Summary: MTP flickers with android
   Product: frameworks-kio
   Version: 5.27.0
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: fa...@kde.org
  Reporter: oliv...@churlaud.com
CC: kdelibs-b...@kde.org
  Target Milestone: ---

Installing gvfs-gphoto2, gvfs-mtp and nautilus is a common solution to be able
to load an Android with MTP.

KIO (and dolphin) should be able to do the same. 

Currently the mtp session cannot hold and the devices keeps
appearing/disappearing. It is impossible to browse.

My System

ArchLinux, all up-to-date
Phone: Samsung A3, with Android 6.0

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

[plasmashell] [Bug 356225] Panel moves to wrong screen when external monitor is connected

[PhillB]

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

--- Comment #241 from PhillB  ---
Thanks Flex1911:

I created an xorg.conf file similar to yours but based on:

X -config /root/xorg.conf.new

then hacked at it until it worked. I used Ctrl-Alt-F2 to switch to another
screen. Then hacked at the xorg.conf and ran it using xinit -- :2

If it blew up then Ctrl-Alt-F8 and Ctrl-Alt-F2 to recover and look at:
/var/log/Xorg.2.log

Finally got it going. The primary stays the primary and the screens go where
they should. The panel always go to the primary now.

Anyway, thanks for the tip. It worked for me.

PhillB

Section "ServerLayout"
Identifier "X.org Configured"
Screen  "ScreenLVDS"
Screen  "ScreenVGA"
#   Screen  "ScreenLVDS" 1050 912
#   Screen  "ScreenVGA"  0 0
#   Screen  "ScreenLVDS" Absolute 1050 912
#   Screen  "ScreenVGA"  Absolute 0 0
InputDevice "Mouse0" "CorePointer"
InputDevice "Keyboard0"  "CoreKeyboard"
EndSection

Section "Files"
ModulePath  "/usr/lib64/xorg/modules"
FontPath"catalogue:/etc/X11/fontpath.d"
FontPath"built-ins"
EndSection

Section "Module"
Load  "glx"
EndSection

Section "InputDevice"
Identifier  "Keyboard0"
Driver  "kbd"
EndSection

Section "InputDevice"
Identifier  "Mouse0"
Driver  "mouse"
Option  "Protocol" "auto"
Option  "Device" "/dev/input/mice"
Option  "ZAxisMapping" "4 5 6 7"
EndSection

Section "Monitor"
Identifier  "LVDS1"
VendorName  "Acer"
ModelName   "5750 Monitor"
Option  "Primary" "true"
Option  "Position" "1050 912"
#   Option  "RightOf" "VGA1"
#   Option  "DPMS""true"
EndSection

Section "Monitor"
Identifier  "VGA1"
VendorName  "Benq"
ModelName   "ScreenEye"
Option  "Rotate"   "Left"
Option  "Position" "0 0"
#   Option  "LeftOf"   "LVDS1"
#   Option  "DPMS" "true"
EndSection

Section "Device"
### Available Driver options are:-
### Values: : integer, : float, : "True"/"False",
### : "String", : " Hz/kHz/MHz",
### : "%"
### [arg]: arg optional
#Option "Accel" # []
#Option "AccelMethod"   # 
#Option "Backlight" # 
#Option "CustomEDID"# 
#Option "DRI"   # 
#Option "Present"   # []
#Option "ColorKey"  # 
#Option "VideoKey"  # 
#Option "Tiling"# []
#Option "LinearFramebuffer" # []
#Option "HWRotation"# []
#Option "VSync" # []
#Option "PageFlip"  # []
#Option "SwapbuffersWait"   # []
#Option "TripleBuffer"  # []
#Option "XvPreferOverlay"   # []
#Option "HotPlug"   # []
#Option "ReprobeOutputs"# []
#Option "XvMC"  # []
#Option "ZaphodHeads"   # 
#Option "VirtualHeads"  # 
#Option "TearFree"  # []
#Option "PerCrtcPixmaps"# []
#Option "FallbackDebug" # []
#Option "DebugFlushBatches" # []
#Option "DebugFlushCaches"  # []
#Option "DebugWait" # []
#Option "BufferCache"   # []
Identifier  "Card0"
Driver  "intel"
BusID   "PCI:0:2:0"
Option  "LVDS1" "LVDS1"
Option  "VGA1"  "VGA1"
EndSection

Section "Screen"
Identifier "ScreenLVDS"
Device "Card0"
Monitor"LVDS1"
SubSection "Display"
Viewport   0 0
Depth 1
EndSubSection
SubSection "Display"
Viewport   0 0
Depth 4
EndSubSection
SubSection "Display"
Viewport   0 0
Depth 8
EndSubSection
SubSection "Display"
Viewport   0 0
Depth 15
EndSubSection
SubSection "Display"
Viewport   0 0
Depth 16
EndSubSection
SubSection "Display"
Viewport   0 0
Depth 24
EndSubSection
EndSection

Section "Screen"
Identifier "ScreenVGA"
Device "Card0"
Monitor"VGA1"
SubSection "Display"
Viewport   0 0
Depth 1
EndSubSection
SubSection "Display"
Viewport  

[plasmashell] [Bug 372317] Crash upon re-enabling display in 4k

[Con Kolivas]

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

--- Comment #3 from Con Kolivas  ---
Thanks for the suggestion. Alas the usual production problem applies - I'm
stuck with whatever kubuntu packages for Ubuntu 16.04 LTS are limited to.

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

[kde-cli-tools] [Bug 372239] Kcmshell5 segfaults when changing notification configurations and actions.

[Horacio Sanson]

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

--- Comment #3 from Horacio Sanson  ---
Created attachment 102198
  --> https://bugs.kde.org/attachment.cgi?id=102198=edit
Screen capture showing the crash

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

[kde-cli-tools] [Bug 372239] Kcmshell5 segfaults when changing notification configurations and actions.

[Horacio Sanson]

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

--- Comment #2 from Horacio Sanson  ---
I am using the packages that come by default with KDE Neon so they are supposed
to be latest versions:

apt-cache show libqt5core5a 
Package: libqt5core5a 
Priority: optional  
Section: libs 
Installed-Size: 5033
Maintainer: Ubuntu Developers    
Original-Maintainer: Debian Qt/KDE Maintainers 
Architecture: amd64 
Source: qtbase-opensource-src 
Version: 5.7.0+dfsg-1+16.04+build5  
Provides: qtbase-abi-5-7-0   
Depends: libc6 (>= 2.14), libgcc1 (>= 1:3.4), libglib2.0-0 (>= 2.22.0),
libicu55 (>= 55.1-1~), libpcre16-3 (>= 2:8.35-4), libstdc++6 (>=
 5), zlib1g (>= 1:1.1.4)   
Recommends:
qttranslations5-l10n   
Suggests: libthai0 
   
Breaks: libqt5scintilla2-12v5 (<< 2.9.2+dfsg-2~) 
Filename:
pool/main/q/qtbase-opensource-src/libqt5core5a_5.7.0+dfsg-1+16.04+build5_amd64.deb
Size: 1804294   
MD5sum: afcc20867080c46aaad638d30ad9faca
SHA1: 021b00dda0d26d87dac8fb49484c05b63d91f42d
SHA256: c7c9c1342734b0cfed093f3ec920d1961e338b1d9643e2f57f36025eff109762
SHA512:
de6c73a2f4e46fd1241fb55c664531af4722f10344eae020d5987ac271145c0e732cfd453f9d4f4774a49fd129200d2252b8e2206647ca545fb6b68fae361d79
Description: Qt 5 core module
Description-md5: 75c9109eafc0c1da6d6b6ca7b292f133
Homepage: http://qt-project.org/
Multi-Arch: same

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

[Breeze] [Bug 371914] Icon request: Claws-mail

[andreas]

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

andreas  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 Resolution|FIXED   |---
 Status|RESOLVED|REOPENED

--- Comment #7 from andreas  ---
feedback for the claws icon theme is needed.

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

[Breeze] [Bug 371914] Icon request: Claws-mail

[andreas]

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

--- Comment #6 from andreas  ---
Created attachment 102197
  --> https://bugs.kde.org/attachment.cgi?id=102197=edit
claws icon theme

please test the icon theme (I didn't use claws) will send the theme to the app
developer if everything works fine.

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

[kwin] [Bug 366651] Kwin Compositor Stops Updating Windows

[Oscar Fuentes]

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

Oscar Fuentes  changed:

   What|Removed |Added

 CC||o...@wanadoo.es

--- Comment #7 from Oscar Fuentes  ---
(In reply to Martin Gräßlin from comment #6)
> Please try to use the breeze window decoration.

I'm experiencing the problem described on this bug report.

What do yo mean by "Please try to use the breeze window decoration."? I'm using
Breeze but after switching to Plastik the problem persists.

For the record, the problem was first seen after upgrading to Kubuntu 16.04.
Now I'm on Kubuntu 16.10 (KDE Plasma 5.7.5). I'm using the radeon driver.

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

[Breeze] [Bug 371914] Icon request: Claws-mail

[andreas]

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

andreas  changed:

   What|Removed |Added

  Latest Commit||http://commits.kde.org/bree
   ||ze-icons/92510347590deb
   ||f96b6d9b5724e8d31905b5
 Resolution|--- |FIXED
 Status|UNCONFIRMED |RESOLVED

--- Comment #5 from andreas  ---
Git commit 92510347590debf96b6d9b5724e8d31905b5 by andreas kainz.
Committed on 13/11/2016 at 01:11.
Pushed by andreask into branch 'master'.

add claws icon from jens (thanks) I'll make also a breeze theme

A  +579  -0icons-dark/apps/48/claws_mail_icon.svg
A  +579  -0icons/apps/48/claws_mail_icon.svg

http://commits.kde.org/breeze-icons/92510347590debf96b6d9b5724e8d31905b5

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

[frameworks-kio] [Bug 343452] Does not sort numbers naturally any longer

[Konstantinos Smanis]

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

Konstantinos Smanis  changed:

   What|Removed |Added

 CC||konstantinos.smanis@gmail.c
   ||om

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

[gwenview] [Bug 349390] regression: sort order incoherent with Dolphin's smart sort order

[Konstantinos Smanis]

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

Konstantinos Smanis  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |DUPLICATE
 CC||konstantinos.smanis@gmail.c
   ||om

--- Comment #3 from Konstantinos Smanis  ---


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

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

[frameworks-kio] [Bug 343452] Does not sort numbers naturally any longer

[Konstantinos Smanis]

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

Konstantinos Smanis  changed:

   What|Removed |Added

 CC||public+...@enkore.de

--- Comment #14 from Konstantinos Smanis  ---
*** Bug 349390 has been marked as a duplicate of this bug. ***

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

[umbrello] [Bug 371990] Crash when removing pin widgets after owning component has been removed before

[bugzilla_noreply]

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

--- Comment #11 from clush...@gmx.net ---
Created attachment 102196
  --> https://bugs.kde.org/attachment.cgi?id=102196=edit
Turn PinPortBase into child item

Attached patch cleans up m_pOw in PinPortBase, and fixes all issues arising due
to this change.

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

[kdenlive] [Bug 372410] New: "colgate" aka "white balance LMS" effect missing from kdenlive-16.12-alpha2-x86_64.AppImage

[Lutz Vieweg]

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

Bug ID: 372410
   Summary: "colgate" aka "white balance LMS" effect missing from
kdenlive-16.12-alpha2-x86_64.AppImage
   Product: kdenlive
   Version: git-master
  Platform: Appimage
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Effects & Transitions
  Assignee: vpi...@kde.org
  Reporter: k...@5t9.de
  Target Milestone: ---

The frei0r "colgate" effect (also known as "White Balance (LMS)" in kdenlive)
is missing from the kdenlive-16.12-alpha2-x86_64.AppImage.

The colgate.xml effect description is there, the effect is also listed in
kdenliveeffectscategory.rc - there is no indication why it should not work.

However, the effect is not selectable from the GUI, and thus cannot be applied.

Am I missing something?

(This effect is vital to my work on underwater video - so much that I would
need to keep working with kdenlive 0.9x if it wasn't available in current
versions.)

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

[lokalize] [Bug 367712] Selecting a .pot file in the project windows, in the editor window Save as... does not fill in the .po file name

[Karl Ove Hufthammer]

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

Karl Ove Hufthammer  changed:

   What|Removed |Added

 CC||k...@huftis.org
 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |INVALID

--- Comment #1 from Karl Ove Hufthammer  ---
The ‘Save As‘ menu option is specifically for saving the file with a *new* file
name, and having no name by default seems like correct behaviour. If you want
to save the file with the default name (which is what you want ~100% of the
time), just use ‘Save’ instead of ‘Save As’. This will use the original name
and folder of the .pot file, but with the .po extension instead of the .pot
extension and the translation folder corresponding to the template folder, e.g.
if the template is

  templates/kdeutils/application.pot

and the current language set for the project is ‘xx’, the file will be stored
as

  xx/kdeutils/application.po

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

[Spectacle] [Bug 372409] New: Background for Rectangular Region Interferes with Region Selection

[David Rankin]

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

Bug ID: 372409
   Summary: Background for Rectangular Region Interferes with
Region Selection
   Product: Spectacle
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: General
  Assignee: m...@baloneygeek.com
  Reporter: drankina...@suddenlinkmail.com
  Target Milestone: ---

Version 16.08.3 - Sorry For Any Inconvenience

KDE Frameworks 5.27.0
Qt 5.7.0 (built against 5.7.0)
The xcb windowing system

When capturing a rectangular region Spectacle shades the screen obscuring the
details needed to mark the start and end of the desired capture region.
Changing the preferences, unselecting [ ] Use light background color, does not
remove the shading, but makes the shading dark making it virtually impossible
to see the screen at all on laptops.

There should be a way to completely disable this shading entirely as it makes
it more difficult in many cases to select the desired rectangular region.
ksnapshot worked perfectly without any shading allowing you to accurately
capture the region of interest. The shading makes it impossible to determine
where to start/stop a region when attempting to avoid parts of gradients,
etc... forcing yet another import into gimp to clean up what should have been a
simple screen grab.

I would include a screenshot showing the problem, but since spectacle can't
even run a multiple instance -- that is impossible too. (frustrating, when
ksnapshot had none of these issues)

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

[kdenlive] [Bug 372261] git master 2016-11-09: Output video rendered from proxies of mlt, not originals

[Evert Vorster]

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

Evert Vorster  changed:

   What|Removed |Added

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

--- Comment #2 from Evert Vorster  ---
Indeed it is.

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

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

[kdenlive] [Bug 371064] rendering uses proxies even though "render using proxy clips" is disabled

[Evert Vorster]

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

Evert Vorster  changed:

   What|Removed |Added

 CC||evert.vors...@yandex.com

--- Comment #2 from Evert Vorster  ---
*** Bug 372261 has been marked as a duplicate of this bug. ***

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

[Spectacle] [Bug 372408] Spectacle Capture Active Window includes Unwanted Margin Outside Active Window

[David Rankin]

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

--- Comment #1 from David Rankin  ---
Note: the space around the 'Active Window' shown in the snapshot is actually
transparent in color, but is shown in KDE as a solid color based on your
current color scheme.

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

[Spectacle] [Bug 372408] New: Spectacle Capture Active Window includes Unwanted Margin Outside Active Window

[David Rankin]

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

Bug ID: 372408
   Summary: Spectacle Capture Active Window includes Unwanted
Margin Outside Active Window
   Product: Spectacle
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: General
  Assignee: m...@baloneygeek.com
  Reporter: drankina...@suddenlinkmail.com
  Target Milestone: ---

Created attachment 102195
  --> https://bugs.kde.org/attachment.cgi?id=102195=edit
Screenshot Showing Areas Outside Active Window (in blue)

Version 16.08.3

KDE Frameworks 5.27.0
Qt 5.7.0 (built against 5.7.0)
The xcb windowing system

Spectacle Capture Active Window includes an unwanted additional 10-15 pixel
margin or buffer around the outside of the Active Window causing the user to
have to manually crop every image taken just to get an actual snapshot of the
current window. This is incredibly cumbersome and frustrating. Why would
capture 'Active Window' be grabbing an additional 10-15 pixels outside the
current window?

Expected behavior - when capturing any window, especially the 'Active Window'
spectacle should only capture the 'Active Window' without including any
extraneous margin or buffer outside the 'Active Window'

A screenshot is attached showing the unwanted additional info captured outside
the active window

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

[systemsettings] [Bug 372407] Edit Scheme Color Preview Not Working (black & white only) and No Update

[David Rankin]

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

--- Comment #1 from David Rankin  ---
Created attachment 102194
  --> https://bugs.kde.org/attachment.cgi?id=102194=edit
General Dialog Preview

General 'Application Color Scheme' dialog that does show static colors of
current scheme on entry into kcm_color module

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

[systemsettings] [Bug 372407] New: Edit Scheme Color Preview Not Working (black & white only) and No Update

[David Rankin]

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

Bug ID: 372407
   Summary: Edit Scheme Color Preview Not Working (black & white
only) and No Update
   Product: systemsettings
   Version: 5.8.3
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: kcm_colors
  Assignee: mwoehlke.fl...@gmail.com
  Reporter: drankina...@suddenlinkmail.com
CC: jpwhit...@kde.org
  Target Milestone: ---

Created attachment 102193
  --> https://bugs.kde.org/attachment.cgi?id=102193=edit
Edit Preview

System Settings > Appearance > Colors > Edit Scheme > [Colors tab]

The color preview for the current scheme shown at the top of the dialog when
the colors tab is selected does not reflect the current color scheme and does
not respond to any changes to the color scheme. Of all the color scheme
previews in KDE, this is the one that must work to aid the color scheme setting
changes.

Expected behavior - upon selecting the color tab the preview should reflect the
current color scheme. Upon a change of a color setting, the preview should
update to reflect the change. This does not happen. (in fact, it doesn't appear
to work at all) 

The preview box shown on the general 'Application Color Scheme' dialog does at
least have colors shown when you enter the 'Colors' part of System Settings,
but it ignores any changes made during editing.

On selection of 'Edit Scheme' > [Colors] tab, the preview box shown appears to
have only 2 colors (gray and darker gray). (see screenshot 'Editing Preview')
It does not reflect the colors for the current scheme being edited and it fails
to shown any changes made to the scheme. (at first I though maybe it only
displays 'changes' so I set all text to Red to test -- nope, it just doesn't
display any color and does not work at all)

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

[kde] [Bug 372406] New: crash using razor tool on timeline

[bugzilla_noreply]

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

Bug ID: 372406
   Summary: crash using razor tool on timeline
   Product: kde
   Version: unspecified
  Platform: unspecified
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: unassigned-b...@kde.org
  Reporter: p...@alicious.com
  Target Milestone: ---

Application: kdenlive (16.07.70)

Qt Version: 5.5.1
Frameworks Version: 5.23.0
Operating System: Linux 4.4.0-45-generic x86_64
Distribution: Ubuntu 16.04.1 LTS

-- Information about the crash:
- What I was doing when the application crashed: had made a few edits on a
single clip with audio and video in one track; used razor tool again to cut at
a marker point and application crashed.

-- Backtrace:
Application: Kdenlive (kdenlive), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7eff4c7668c0 (LWP 4387))]

Thread 37 (Thread 0x7efef1ff6700 (LWP 5040)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7eff18637cdd in ?? () from /usr/lib/mlt/libmltsdl.so
#2  0x7eff450a270a in start_thread (arg=0x7efef1ff6700) at
pthread_create.c:333
#3  0x7eff467a182d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 36 (Thread 0x7efeefb8a700 (LWP 5039)):
#0  0x7eff46795c21 in __GI_ppoll (fds=0x7efedba88050, nfds=3,
timeout=, sigmask=0x0) at ../sysdeps/unix/sysv/linux/ppoll.c:50
#1  0x7eff4179eaad in pa_mainloop_poll () from
/usr/lib/x86_64-linux-gnu/libpulse.so.0
#2  0x7eff4179f0ae in pa_mainloop_iterate () from
/usr/lib/x86_64-linux-gnu/libpulse.so.0
#3  0x7eff183cafeb in ?? () from /usr/lib/x86_64-linux-gnu/libSDL-1.2.so.0
#4  0x7eff1839d920 in ?? () from /usr/lib/x86_64-linux-gnu/libSDL-1.2.so.0
#5  0x7eff183a70b8 in ?? () from /usr/lib/x86_64-linux-gnu/libSDL-1.2.so.0
#6  0x7eff183e6f59 in ?? () from /usr/lib/x86_64-linux-gnu/libSDL-1.2.so.0
#7  0x7eff450a270a in start_thread (arg=0x7efeefb8a700) at
pthread_create.c:333
#8  0x7eff467a182d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 35 (Thread 0x7efeed4c1700 (LWP 5038)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7eff4c0f97f3 in ?? () from /usr/lib/libmlt.so.6
#2  0x007fb645 in RenderThread::run() ()
#3  0x7eff471a87be in QThreadPrivate::start (arg=0x7efea68342d0) at
thread/qthread_unix.cpp:331
#4  0x7eff450a270a in start_thread (arg=0x7efeed4c1700) at
pthread_create.c:333
#5  0x7eff467a182d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 34 (Thread 0x7efef27f7700 (LWP 5037)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7eff1863868f in ?? () from /usr/lib/mlt/libmltsdl.so
#2  0x7eff450a270a in start_thread (arg=0x7efef27f7700) at
pthread_create.c:333
#3  0x7eff467a182d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 33 (Thread 0x7efef0c21700 (LWP 5007)):
#0  pthread_cond_timedwait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_timedwait.S:225
#1  0x7eff471a9996 in QWaitConditionPrivate::wait_relative (time=3,
this=0x3f1fec0) at thread/qwaitcondition_unix.cpp:126
#2  QWaitConditionPrivate::wait (time=3, this=0x3f1fec0) at
thread/qwaitcondition_unix.cpp:134
#3  QWaitCondition::wait (this=this@entry=0x37ee660,
mutex=mutex@entry=0x37c93b0, time=3) at thread/qwaitcondition_unix.cpp:208
#4  0x7eff471a5463 in QThreadPoolThread::run (this=0x37ee650) at
thread/qthreadpool.cpp:127
#5  0x7eff471a87be in QThreadPrivate::start (arg=0x37ee650) at
thread/qthread_unix.cpp:331
#6  0x7eff450a270a in start_thread (arg=0x7efef0c21700) at
pthread_create.c:333
#7  0x7eff467a182d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 32 (Thread 0x7efe7a7f7700 (LWP 4865)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7eff252c6f5e in ?? () from
/usr/lib/x86_64-linux-gnu/libavcodec-ffmpeg.so.56
#2  0x7eff450a270a in start_thread (arg=0x7efe7a7f7700) at
pthread_create.c:333
#3  0x7eff467a182d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 31 (Thread 0x7efe7aff8700 (LWP 4864)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7eff252c6f5e in ?? () from
/usr/lib/x86_64-linux-gnu/libavcodec-ffmpeg.so.56
#2  0x7eff450a270a in start_thread (arg=0x7efe7aff8700) at
pthread_create.c:333
#3  0x7eff467a182d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 30 (Thread 0x7efe7b7f9700 (LWP 4863)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at

[kdenlive] [Bug 372261] git master 2016-11-09: Output video rendered from proxies of mlt, not originals

[Wegwerf]

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

Wegwerf  changed:

   What|Removed |Added

 CC||wegwerf-1-...@gmx.de

--- Comment #1 from Wegwerf  ---
Is this a duplicate of #371064?

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

[kdenlive] [Bug 371792] Extract frame not working

[Wegwerf]

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

Wegwerf  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|UNCONFIRMED |RESOLVED
 CC||wegwerf-1-...@gmx.de

--- Comment #4 from Wegwerf  ---
Only latest version is maintained, as stated on Kdenlive's web site.

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

[plasmashell] [Bug 372405] New: Plasma crashes consistantly & immediately following startx since 1st reboot following last system auto-update

[Erich]

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

Bug ID: 372405
   Summary: Plasma crashes consistantly & immediately following
startx since 1st reboot following last system
auto-update
   Product: plasmashell
   Version: 5.5.5
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: k...@stepfordrobotics.com
CC: bhus...@gmail.com, plasma-b...@kde.org
  Target Milestone: 1.0

Application: plasmashell (5.5.5)

Qt Version: 5.5.1
Operating System: Linux 4.4.0-47-generic x86_64
Distribution: Ubuntu 16.04.1 LTS

-- Information about the crash:
- What I was doing when the application crashed: Either system restart or
startx from terminal

- Unusual behavior I noticed: On system restart, loads to non-responsive blank
black screen with only funtioning mouse pointer.  Ctrl-alt-F(1-6) starts
terminal, and startx results in three separate Plasma crash reports.  This is
the output of the first report.

The crash can be reproduced every time.

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

Thread 6 (Thread 0x7fa94d21c700 (LWP 1577)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7fa97bd4dbd4 in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5Script.so.5
#2  0x7fa97bd4dc19 in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5Script.so.5
#3  0x7fa972bff754 in ?? () from /usr/lib/nvidia-304/libGL.so.1
#4  0x7fa9761f270a in start_thread (arg=0x7fa94d21c700) at
pthread_create.c:333
#5  0x7fa976a1b82d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 5 (Thread 0x7fa94eb91700 (LWP 1576)):
#0  0x7fa9737a48eb in g_main_context_prepare () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#1  0x7fa9737a52cb in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7fa9737a54ac in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7fa97733c7eb in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7fa9772e3b4a in
QEventLoop::exec(QFlags) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7fa977100834 in QThread::exec() () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7fa9799a83c5 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5
#7  0x7fa9771057be in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x7fa972bff754 in ?? () from /usr/lib/nvidia-304/libGL.so.1
#9  0x7fa9761f270a in start_thread (arg=0x7fa94eb91700) at
pthread_create.c:333
#10 0x7fa976a1b82d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 4 (Thread 0x7fa954a80700 (LWP 1567)):
#0  __lll_unlock_wake () at
../sysdeps/unix/sysv/linux/x86_64/lowlevellock.S:371
#1  0x7fa9761f654f in __pthread_mutex_unlock_usercnt (decr=1,
mutex=0x7fa972e5ca40) at pthread_mutex_unlock.c:55
#2  __GI___pthread_mutex_unlock (mutex=0x7fa972e5ca40) at
pthread_mutex_unlock.c:314
#3  0x7fa972bf974b in ?? () from /usr/lib/nvidia-304/libGL.so.1
#4  0x7fa972bfe766 in ?? () from /usr/lib/nvidia-304/libGL.so.1
#5  0x7fa96f5d9bf7 in ?? () from
/usr/lib/nvidia-304/tls/libnvidia-tls.so.304.132
#6  0x7fa9737e8740 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#7  0x7fa9737a4e84 in g_main_context_check () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#8  0x7fa9737a5340 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#9  0x7fa9737a54ac in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#10 0x7fa97733c7eb in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#11 0x7fa9772e3b4a in
QEventLoop::exec(QFlags) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#12 0x7fa977100834 in QThread::exec() () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#13 0x7fa9799a83c5 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5
#14 0x7fa9771057be in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#15 0x7fa972bff754 in ?? () from /usr/lib/nvidia-304/libGL.so.1
#16 0x7fa9761f270a in start_thread (arg=0x7fa954a80700) at
pthread_create.c:333
#17 0x7fa976a1b82d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 3 (Thread 0x7fa95f5ef700 (LWP 1543)):
#0  __lll_lock_wait () at ../sysdeps/unix/sysv/linux/x86_64/lowlevellock.S:135
#1  0x7fa9761f4e92 in __GI___pthread_mutex_lock (mutex=0x7fa972e5ca40) at
../nptl/pthread_mutex_lock.c:115
#2  0x7fa972bf99f2 in ?? () from /usr/lib/nvidia-304/libGL.so.1
#3  0x7fa972bfe290 in ?? () from /usr/lib/nvidia-304/libGL.so.1
#4  

[plasmashell] [Bug 356225] Panel moves to wrong screen when external monitor is connected

[Dan Duris]

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

--- Comment #240 from Dan Duris  ---
Hi,

defaulting Plasma to whatever setup you have works for me with the provided
script in one of the comments:
http://pastebin.com/GDuUZQni

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

[Discover] [Bug 372404] New: plasma-discover crashes on Kubuntu 16.10

[Matt Z .]

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

Bug ID: 372404
   Summary: plasma-discover crashes on Kubuntu 16.10
   Product: Discover
   Version: unspecified
  Platform: Kubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: critical
  Priority: NOR
 Component: discover
  Assignee: aleix...@kde.org
  Reporter: ma...@hotmail.com
  Target Milestone: ---

loaded fresh install of Kubuntu 16.10 on HP Pavilion dv6000 Notebook

Discover crashes every time with a segmentation fault. Sorry, but the "file
report" window says debug info is useless.

KDE Plasma: 5.7.5
KDE Frameworks: 5.26.0
Qt Version: 5.6.1
Kernel: 4.8.0-27-generic
OS Type: 64-bit
AMD processor with 2.8 GiB RAM

Graphics Card: NVIDIA C67 (GeForce 7150M / nForce 630M)
Display Driver: nouveau -- resolution 1280x800

Notes:
-- using the nvidia driver causes blank screen at boot (presumably at the login
screen)
-- if booting with 'nomodeset', graphics is default vga, and discover does not
crash
-- previous version Kubuntu 15.10 worked ok (wish I still had the iso so I
could reinstall that)
-- tried reinstalling 16.10, no difference

Matt

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

[digikam] [Bug 372362] Build error due to private function

[Maik Qualmann]

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

Maik Qualmann  changed:

   What|Removed |Added

 CC||metzping...@gmail.com
 Resolution|--- |FIXED
 Status|UNCONFIRMED |RESOLVED

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

[digikam] [Bug 372362] Build error due to private function

[Maik Qualmann]

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

--- Comment #3 from Maik Qualmann  ---
Git commit 0cb457e58c9de989a2e997812d636aabc5daa596 by Maik Qualmann.
Committed on 12/11/2016 at 21:32.
Pushed by mqualmann into branch 'master'.

fix compile current master branch #2

M  +2-2utilities/fuzzysearch/findduplicatesalbumitem.cpp
M  +9-9utilities/fuzzysearch/findduplicatesview.cpp

http://commits.kde.org/digikam/0cb457e58c9de989a2e997812d636aabc5daa596

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

[krita] [Bug 372403] New: Krita crashed when attempted to clear a layer

[mangouste]

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

Bug ID: 372403
   Summary: Krita crashed when attempted to clear a layer
   Product: krita
   Version: unspecified
  Platform: Debian testing
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: krita-bugs-n...@kde.org
  Reporter: mangoust...@gmail.com
  Target Milestone: ---

Application: krita (2.4.4)
KDE Platform Version: 4.14.25
Qt Version: 4.8.7
Operating System: Linux 4.7.0-1-amd64 x86_64
Distribution: Debian GNU/Linux testing (stretch)

-- Information about the crash:
- What I was doing when the application crashed:
1) Opened a new project
2) Created a new layer
3) Draw something (a point is enough)
4) Hit  key to clear the layer => Krita crashes

The crash can be reproduced every time.

-- Backtrace:
Application: Krita (krita), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
pthread_cond_timedwait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_timedwait.S:225
[Current thread is 1 (Thread 0x7f50a702a380 (LWP 28325))]

Thread 9 (Thread 0x7f505f7fe700 (LWP 28412)):
#0  pthread_cond_timedwait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_timedwait.S:225
#1  0x7f50a452a2f4 in QWaitCondition::wait(QMutex*, unsigned long) () from
/usr/lib/x86_64-linux-gnu/libQtCore.so.4
#2  0x7f50a451cf97 in ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#3  0x7f50a4529daa in ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#4  0x7f509f971464 in start_thread (arg=0x7f505f7fe700) at
pthread_create.c:333
#5  0x7f50a667f9df in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:105

Thread 8 (Thread 0x7f505700 (LWP 28411)):
#0  pthread_cond_timedwait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_timedwait.S:225
#1  0x7f50a452a2f4 in QWaitCondition::wait(QMutex*, unsigned long) () from
/usr/lib/x86_64-linux-gnu/libQtCore.so.4
#2  0x7f50a451cf97 in ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#3  0x7f50a4529daa in ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#4  0x7f509f971464 in start_thread (arg=0x7f505700) at
pthread_create.c:333
#5  0x7f50a667f9df in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:105

Thread 7 (Thread 0x7f5071cda700 (LWP 28410)):
#0  pthread_cond_timedwait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_timedwait.S:225
#1  0x7f50a452a2f4 in QWaitCondition::wait(QMutex*, unsigned long) () from
/usr/lib/x86_64-linux-gnu/libQtCore.so.4
#2  0x7f50a451cf97 in ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#3  0x7f50a4529daa in ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#4  0x7f509f971464 in start_thread (arg=0x7f5071cda700) at
pthread_create.c:333
#5  0x7f50a667f9df in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:105

Thread 6 (Thread 0x7f50724db700 (LWP 28409)):
#0  pthread_cond_timedwait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_timedwait.S:225
#1  0x7f50a452a2f4 in QWaitCondition::wait(QMutex*, unsigned long) () from
/usr/lib/x86_64-linux-gnu/libQtCore.so.4
#2  0x7f50a451cf97 in ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#3  0x7f50a4529daa in ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#4  0x7f509f971464 in start_thread (arg=0x7f50724db700) at
pthread_create.c:333
#5  0x7f50a667f9df in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:105

Thread 5 (Thread 0x7f505e7fc700 (LWP 28376)):
#0  0x7f50a66782b3 in select () at ../sysdeps/unix/syscall-template.S:84
#1  0x7f50a46675df in qt_safe_select(int, fd_set*, fd_set*, fd_set*,
timeval const*) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#2  0x7f50a466d2bb in
QEventDispatcherUNIXPrivate::doSelect(QFlags,
timeval*) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#3  0x7f50a466d778 in
QEventDispatcherUNIX::processEvents(QFlags) ()
from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#4  0x7f50a463882f in
QEventLoop::processEvents(QFlags) () from
/usr/lib/x86_64-linux-gnu/libQtCore.so.4
#5  0x7f50a4638b95 in
QEventLoop::exec(QFlags) () from
/usr/lib/x86_64-linux-gnu/libQtCore.so.4
#6  0x7f50a45274d9 in QThread::exec() () from
/usr/lib/x86_64-linux-gnu/libQtCore.so.4
#7  0x7f50a4618603 in ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#8  0x7f50a4529daa in ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#9  0x7f509f971464 in start_thread (arg=0x7f505e7fc700) at
pthread_create.c:333
#10 0x7f50a667f9df in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:105

Thread 4 (Thread 0x7f505effd700 (LWP 28375)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f50a452a316 in QWaitCondition::wait(QMutex*, unsigned long) () 

[digikam] [Bug 372362] Build error due to private function

[Simon]

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

--- Comment #2 from Simon  ---
Created attachment 102192
  --> https://bugs.kde.org/attachment.cgi?id=102192=edit
Fixes more of the same issues.

This fixed this particular problem, but there were more. Now that I knew what
it was about I corrected them myself. See attached patch.

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

[digikam] [Bug 372362] Build error due to private function

[Simon]

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

Simon  changed:

   What|Removed |Added

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

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

[kmymoney4] [Bug 372402] New: touchpad disabled intermittently in KDE when running KMyMoney

[Yuri Shirman]

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

Bug ID: 372402
   Summary: touchpad disabled intermittently in KDE when running
KMyMoney
   Product: kmymoney4
   Version: 4.7.2
  Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kmymoney-de...@kde.org
  Reporter: yshir...@gmail.com
  Target Milestone: ---

When running KMyMoney in KDE on Fedora 24, my touchpad on the Lenovo Thinkpad
Yoga gets periodically disabled. The pointing stick continues to work. Often
(probably most of the time) Alt-Tab fixes the issue temporarily.
Sometimes/often the issue persists even after exiting KMyMoney. The problem
happens only when running KMyMoney and only in KDE. No other app causes similar
behavior for me in KDE and there is no problem if I run KMyMoney in Cinnamon.

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

[konsole] [Bug 372401] New: console crashed in background

[Marcin Gryszkalis]

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

Bug ID: 372401
   Summary: console crashed in background
   Product: konsole
   Version: 16.08.1
  Platform: Compiled Sources
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: konsole-de...@kde.org
  Reporter: m...@fork.pl
  Target Milestone: ---

Application: konsole (16.08.1)
 (Compiled from sources)
Qt Version: 5.6.1
Frameworks Version: 5.26.0
Operating System: Linux 4.4.2-gentoo-ines x86_64
Distribution: "Gentoo Base System release 2.3"

-- Information about the crash:
- What I was doing when the application crashed:
Nothing, ie. console was in background and different app was active.

Console had 2 windows with several tabs in each one.

-- Backtrace:
Application: Konsole (konsole), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fe3d0cdf740 (LWP 4886))]

Thread 2 (Thread 0x7fe3bd7c0700 (LWP 4904)):
#0  0x7fe3d0a24edd in poll () from /lib64/libc.so.6
#1  0x7fe3c847a24c in g_main_context_iterate.isra () from
/usr/lib64/libglib-2.0.so.0
#2  0x7fe3c847a35c in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#3  0x7fe3cd658a3c in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib64/libQt5Core.so.5
#4  0x7fe3cd60cbf2 in
QEventLoop::exec(QFlags) () from
/usr/lib64/libQt5Core.so.5
#5  0x7fe3cd46cab4 in QThread::exec() () from /usr/lib64/libQt5Core.so.5
#6  0x7fe3d10061bd in QDBusConnectionManager::run() () from
/usr/lib64/libQt5DBus.so.5
#7  0x7fe3cd47118b in QThreadPrivate::start(void*) () from
/usr/lib64/libQt5Core.so.5
#8  0x7fe3c9f3842c in start_thread () from /lib64/libpthread.so.0
#9  0x7fe3d0a2de3d in clone () from /lib64/libc.so.6

Thread 1 (Thread 0x7fe3d0cdf740 (LWP 4886)):
[KCrash Handler]
#6  0x7fe3d068a0e0 in Konsole::ProcessInfo::name(bool*) const () from
/usr/lib64/libkonsoleprivate.so.16
#7  0x7fe3d06a93cc in Konsole::Session::getDynamicTitle() () from
/usr/lib64/libkonsoleprivate.so.16
#8  0x7fe3d06b4849 in Konsole::SessionController::snapshot() () from
/usr/lib64/libkonsoleprivate.so.16
#9  0x7fe3cd6349bf in QMetaObject::activate(QObject*, int, int, void**) ()
from /usr/lib64/libQt5Core.so.5
#10 0x7fe3cd6413d8 in QTimer::timerEvent(QTimerEvent*) () from
/usr/lib64/libQt5Core.so.5
#11 0x7fe3cd6358c3 in QObject::event(QEvent*) () from
/usr/lib64/libQt5Core.so.5
#12 0x7fe3ce1351dc in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() from /usr/lib64/libQt5Widgets.so.5
#13 0x7fe3ce139890 in QApplication::notify(QObject*, QEvent*) () from
/usr/lib64/libQt5Widgets.so.5
#14 0x7fe3cd60dfc0 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() from /usr/lib64/libQt5Core.so.5
#15 0x7fe3cd65807e in QTimerInfoList::activateTimers() () from
/usr/lib64/libQt5Core.so.5
#16 0x7fe3cd65858c in idleTimerSourceDispatch(_GSource*, int (*)(void*),
void*) () from /usr/lib64/libQt5Core.so.5
#17 0x7fe3c8479fd4 in g_main_context_dispatch () from
/usr/lib64/libglib-2.0.so.0
#18 0x7fe3c847a2b0 in g_main_context_iterate.isra () from
/usr/lib64/libglib-2.0.so.0
#19 0x7fe3c847a35c in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#20 0x7fe3cd658a1f in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib64/libQt5Core.so.5
#21 0x7fe3cd60cbf2 in
QEventLoop::exec(QFlags) () from
/usr/lib64/libQt5Core.so.5
#22 0x7fe3cd61457c in QCoreApplication::exec() () from
/usr/lib64/libQt5Core.so.5
#23 0x7fe3d0d0834c in kdemain () from /usr/lib64/libkdeinit5_konsole.so
#24 0x7fe3d0969780 in __libc_start_main () from /lib64/libc.so.6
#25 0x00400769 in _start ()

Possible duplicates by query: bug 370762, bug 370652.

Reported using DrKonqi

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

[plasmashell] [Bug 372400] New: Plasma shell aborts - apparently some sort of timeout - every time I try to log in since system updated.

[bugzilla_noreply]

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

Bug ID: 372400
   Summary: Plasma shell aborts - apparently some sort of timeout
- every time I try to log in since system updated.
   Product: plasmashell
   Version: 5.5.5
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: neuschein-cot...@yahoo.co.uk
CC: bhus...@gmail.com, plasma-b...@kde.org
  Target Milestone: 1.0

Application: plasmashell (5.5.5)

Qt Version: 5.5.1
Operating System: Linux 4.4.0-47-generic i686
Distribution: Ubuntu 16.04.1 LTS

-- Information about the crash:
- What I was doing when the application crashed:
Trying to log in.
The crash is reported 3 times. If I then leave the system, the screen locks and
there is a message saying that the unlocker is broken so that I can only unlock
it from a terminal login. But if I do that, there is still nothing working when
I come back to the session that crashed. Choosing the option on the crash
report to restart the program just results in it crashing again.

- Unusual behavior I noticed:
 It happens every time I try it, since I restarted the system after having some
updates applied. (I tried to suggest that this might be a duplicate of 372352
but the crash reporting assistant didn't seem to accept that and insists that I
haven't selected a duplicate, so I'm mentioning it here instead.) There we a
lot of updates and I had the impression that they finished more quickly than
usual, so I don't know if that implies they didn't work properly, but there
were no error messages in the "Discoverer" program.

The crash can be reproduced every time.

-- Backtrace:
Application: Plasma (plasmashell), signal: Aborted
Using host libthread_db library "/lib/i386-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0xafe05800 (LWP 1643))]

Thread 7 (Thread 0xa7d23b40 (LWP 1708)):
#0  0xb770fc31 in __kernel_vsyscall ()
#1  0xb4bf1d42 in __lll_lock_wait () at
../sysdeps/unix/sysv/linux/i386/lowlevellock.S:144
#2  0xb4beb949 in __GI___pthread_mutex_lock (mutex=0xb427b2a0) at
../nptl/pthread_mutex_lock.c:115
#3  0xb42348c9 in ?? () from /usr/lib/nvidia-304/libGL.so.1
Backtrace stopped: previous frame inner to this frame (corrupt stack?)

Thread 6 (Thread 0xa9471b40 (LWP 1693)):
#0  0xb770fc31 in __kernel_vsyscall ()
#1  0xb4beea9c in pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/i386/pthread_cond_wait.S:187
#2  0xb4d4d64d in __pthread_cond_wait (cond=0xb767a8d0, mutex=0xb767a8b8) at
forward.c:149
#3  0xb7542a2c in ?? () from /usr/lib/i386-linux-gnu/libQt5Script.so.5
#4  0xb7542a6c in ?? () from /usr/lib/i386-linux-gnu/libQt5Script.so.5
#5  0xb423a2c1 in ?? () from /usr/lib/nvidia-304/libGL.so.1
#6  0x5c8b0824 in ?? ()
#7  0xbab80424 in ?? ()
#8  0x6500 in ?? ()
#9  0x001015ff in ?? ()
#10 0xd389 in ?? ()
#11 0xfff0013d in ?? ()
#12 0x7d830fff in ?? ()
#13 0xc3fffec0 in ?? ()
#14 0x90669066 in ?? ()
#15 0x90669066 in ?? ()
#16 0x90669066 in ?? ()
#17 0xe8535657 in ?? ()
#18 0x000f32dd in ?? ()
#19 0x5938c781 in ?? ()
#20 0xec810018 in ?? ()
#21 0x0094 in ?? ()
#22 0xa4249c8b in ?? ()
#23 0x8d00 in ?? ()
#24 0x56082474 in ?? ()
#25 0xe853006a in ?? ()
#26 0xf998 in ?? ()
#27 0x8510c483 in ?? ()
#28 0x8d6978c0 in ?? ()
#29 0x01b8ff4b in ?? ()
#30 0x8900 in ?? ()
#31 0x8be0d3ca in ?? ()
#32 0x00a4248c in ?? ()
#33 0xeac1 in ?? ()
#34 0x75c98505 in ?? ()
#35 0x81d0f737 in ?? ()
#36 0x0088248c in ?? ()
#37 0x in ?? ()

Thread 5 (Thread 0xaa5c0b40 (LWP 1687)):
#0  0xb770fc31 in __kernel_vsyscall ()
#1  0xb4d36d0f in poll () at ../sysdeps/unix/syscall-template.S:84
#2  0xb43e4b10 in g_poll () from /lib/i386-linux-gnu/libglib-2.0.so.0
#3  0xb43d610c in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
#4  0xb43d6244 in g_main_context_iteration () from
/lib/i386-linux-gnu/libglib-2.0.so.0
#5  0xb5243964 in QEventDispatcherGlib::processEvents (this=0xadb52de8,
flags=...) at kernel/qeventdispatcher_glib.cpp:420
#6  0xb51e87a3 in QEventLoop::processEvents (this=0xaa5c0124, flags=...) at
kernel/qeventloop.cpp:128
#7  0xb51e8bfa in QEventLoop::exec (this=0xaa5c0124, flags=...) at
kernel/qeventloop.cpp:204
#8  0xb500ef1d in QThread::exec (this=0x8a85b58) at thread/qthread.cpp:503
#9  0xb6880aff in QQmlThreadPrivate::run (this=0x8a85b58) at
qml/ftw/qqmlthread.cpp:141
#10 0xb501443b in QThreadPrivate::start (arg=0x8a85b58) at
thread/qthread_unix.cpp:331
#11 0xb423a2c1 in ?? () from /usr/lib/nvidia-304/libGL.so.1
#12 0x5c8b0824 in ?? ()
#13 0xbab80424 in ?? ()
#14 0x6500 in ?? ()
#15 0x001015ff in ?? ()
#16 0xd389 in ?? ()
#17 0xfff0013d in ?? ()
#18 0x7d830fff in ?? ()
#19 0xc3fffec0 in ?? ()
#20 0x90669066 in ?? ()
#21 0x90669066 in ?? ()
#22 0x90669066 in ?? ()
#23 0xe8535657 in ?? ()
#24 

[kdenlive] [Bug 372399] New: Proxy not created

[Fahad Hasan]

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

Bug ID: 372399
   Summary: Proxy not created
   Product: kdenlive
   Version: 16.08.2
  Platform: RedHat RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: major
  Priority: NOR
 Component: Translation
  Assignee: vpi...@kde.org
  Reporter: excentri...@gmail.com
  Target Milestone: ---

Proxy can not be created in 16.08.2. Working on unstable build
kdenlive-16.12-alpha2-x86_64.

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

[plasmashell] [Bug 372398] New: Get rid of arrow in System Tray

[alxgvr]

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

Bug ID: 372398
   Summary: Get rid of arrow in System Tray
   Product: plasmashell
   Version: master
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: System Tray
  Assignee: plasma-b...@kde.org
  Reporter: alx...@gmail.com
  Target Milestone: 1.0

Created attachment 102191
  --> https://bugs.kde.org/attachment.cgi?id=102191=edit
Annoying black arrow.

Hi. I like to keep my panel clean, remove all excess indicators. 
And this arrow in system tray annoys me too much.

I like unity\cinnamon\xfce system tray. They do not have pop-up windows with
extra indicators. It looks clean.
So, I would like to remove that pop-up list and that black arrow. 

Yes, I can just remove items from it in System Tray Settings (like KDE connect,
or Device notifier), so when no items left to show in pop-up window - it
disappears. But if only one extra-indicator left - it will be present. 

I think it is not correct to keep arrow element and pop-up window for only one
component. I want to have such items like Battery indicator or updates, but not
in pop-up window. I want to see all of them on the panel. 

So I wish it will be an option to show all hidden components of system tray on
the panel. All of them, or set quantity of items that will be shown on panel
manually (others will be hidden).

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

[plasmashell] [Bug 372397] New: Plasma Crash on Log In

[bugzilla_noreply]

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

Bug ID: 372397
   Summary: Plasma Crash on Log In
   Product: plasmashell
   Version: 5.8.3
  Platform: Neon Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: tylerbi...@gmail.com
CC: bhus...@gmail.com, plasma-b...@kde.org
  Target Milestone: 1.0

Application: plasmashell (5.8.3)

Qt Version: 5.7.0
Frameworks Version: 5.27.0
Operating System: Linux 4.4.0-47-generic x86_64
Distribution: KDE neon User Edition 5.8

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

I logged in from startup. I was also trying to log out and back in a couple
times since my desk settings were reversed between my two monitors.

- Unusual behavior I noticed:

As stated above my monitor settings were reversed. The taskbars were on the
wrong screens, the bars are set to only show applications running on that
screen but were showing applications on the oppsite screen. Wallpaper settings
also now default despite being set to slideshow.

The crash can be reproduced sometimes.

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

Thread 16 (Thread 0x7f0f59dab700 (LWP 2663)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f1041bd9adb in QWaitCondition::wait(QMutex*, unsigned long) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#2  0x7f1044e46f5d in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
#3  0x7f1044e47835 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
#4  0x7f1041bd8c28 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7f1040cbc70a in start_thread (arg=0x7f0f59dab700) at
pthread_create.c:333
#6  0x7f10414e582d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 15 (Thread 0x7f0f5affc700 (LWP 2662)):
#0  0x7f10414d9b5d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7f103d0bc39c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f103d0bc4ac in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f1041e0430b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7f1041daed9a in
QEventLoop::exec(QFlags) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7f1041bd4044 in QThread::exec() () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7f1044453685 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5
#7  0x7f1041bd8c28 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x7f1040cbc70a in start_thread (arg=0x7f0f5affc700) at
pthread_create.c:333
#9  0x7f10414e582d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 14 (Thread 0x7f0f5bffe700 (LWP 2654)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f1041bd9adb in QWaitCondition::wait(QMutex*, unsigned long) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#2  0x7f1044e46f5d in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
#3  0x7f1044e47835 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
#4  0x7f1041bd8c28 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7f1040cbc70a in start_thread (arg=0x7f0f5bffe700) at
pthread_create.c:333
#6  0x7f10414e582d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 13 (Thread 0x7f0f6cd42700 (LWP 2650)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f1041bd9adb in QWaitCondition::wait(QMutex*, unsigned long) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#2  0x7f1044e46f5d in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
#3  0x7f1044e47835 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
#4  0x7f1041bd8c28 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7f1040cbc70a in start_thread (arg=0x7f0f6cd42700) at
pthread_create.c:333
#6  0x7f10414e582d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 12 (Thread 0x7f0f6e021700 (LWP 2643)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f1041bd9adb in QWaitCondition::wait(QMutex*, unsigned long) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#2  0x7f1044e46f5d in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
#3  0x7f1044e47835 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
#4  0x7f1041bd8c28 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7f1040cbc70a in start_thread 

[plasmashell] [Bug 356225] Panel moves to wrong screen when external monitor is connected

[Michael Butash]

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

--- Comment #239 from Michael Butash  ---
Glitching the video card itself to lose the hdmi port hard reset everything
oddly, which caused me to have to re-setup resolution and everything here, but
once back in order, the task bar was still sitting on dfp-1 (right of 3) when
set to dfp-2 (middle of 3).  

Weird part is when doing that, cairo-dock that I use suddenly thought it's
primary display was dfp-1 as well, and moved there, where at least it typically
knew it should be in center relative to x resolution.  Really odd.

I did use nvidia-setting to re-setup the display, as last time using kde
display settings blew it up, is it possible it's setting a wrong index qt vs
gtk-based apps are following?  Cairo seems more gtk-based, but kde is typically
more "wrong" in terms of display, aside from currently.

So far every time I boot neon I seem to get a different behavior now.  Keeps
life interesting at least.

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

[digikam] [Bug 261417] Duplicate image counter is not adjusted when removing a duplicate

[bugzilla_noreply]

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

--- Comment #7 from caulier.gil...@gmail.com ---
I can't check the patch actually but I suspect that you fired a signal from
icon view item context menu to duplicates list view to decrease count of items.
This is not the right way. You must fired a signal to database iOS job to
refresh search album for duplicates. This will update properties the virtual
album in database. 

THE process is similar that to refresh all duplicates virtual album from button
on left sidebar, but it must only to be processed on current selected
duplicates virtual search album.

Gilles caulier

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

[digikam] [Bug 372314] I cannot choose the template predefined in the import window while renaming (F2)

[Maik Qualmann]

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

Maik Qualmann  changed:

   What|Removed |Added

   Version Fixed In||5.4.0
  Latest Commit||http://commits.kde.org/digi
   ||kam/8150258bce78249f5d54768
   ||b6b37c1fa92d29a10
 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |FIXED

--- Comment #4 from Maik Qualmann  ---
Git commit 8150258bce78249f5d54768b6b37c1fa92d29a10 by Maik Qualmann.
Committed on 12/11/2016 at 20:25.
Pushed by mqualmann into branch 'master'.

fix select first combobox item because it is already selected
FIXED-IN: 5.4.0

M  +2-1NEWS
M  +1-0utilities/advancedrename/advancedrenameinput.cpp

http://commits.kde.org/digikam/8150258bce78249f5d54768b6b37c1fa92d29a10

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

[plasmashell] [Bug 356225] Panel moves to wrong screen when external monitor is connected

[Michael Butash]

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

--- Comment #238 from Michael Butash  ---
So yeah, the task bar bouncing back and forth between monitors is back with
this, actually 5.8.3-0neon+16.04+build* versions, and this was from a neon cd
direct install.  

Any time I've shut off my displays, making them disappear on the hdmi, it
rearranges the task bar again despite whatever display is set  as primary.  The
only real different now is the later version, and that I'm using an nvidia card
with binary drivers vs. amd with oss drivers.  Both seem to still use xrandr
for control though, so I don't know what the issue is (or technically what was
fixed prior).

I've had kwin start glitching, and rearranging my wallpapers again (sigh) too,
which had been resolved.  Trying to use kde display manager instead of
nvidia-setting caused my hdmi port on the video card to disappear from being
found, just trying to change around the primary desktop to get it to stick my
taskbar in the right spot.  Time for a reboot, hope my hdmi comes back...

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

[digikam] [Bug 361047] Wishlist: make grouped images more prominently visible [patch]

[Jens B . Benecke]

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

--- Comment #54 from Jens B. Benecke  ---
OK, no hurry. .)
Anything I can do to help (non-coder)? I have some more time now.

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

[digikam] [Bug 361047] Wishlist: make grouped images more prominently visible [patch]

[bugzilla_noreply]

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

--- Comment #53 from caulier.gil...@gmail.com ---
The patch is not yet integrated because Its not visually suitable and do not
work yet in all conditions. The basis is here but GUI code need to be rewrites.

Gilles caulier

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

[kdesudo] [Bug 353263] No icons show on root session. unable to assign any too.

[Ilyes Kechidi]

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

Ilyes Kechidi  changed:

   What|Removed |Added

 CC||ilyes@gmail.com

--- Comment #20 from Ilyes Kechidi  ---
(In reply to Russ White from comment #19)
> I have confirmed that creating a file in /etc/sudoers.d with 
> 
>   Defaults env_keep += "KDE_SESSION_VERSION KDE_FULL_SESSION"
> 
> fixes the issue for programs launched using sudo however
> theme/style/icons/etc are still missing if launched using kdesudo.  Is there
> something that differentiates them?  I was under the impression that kdesudo
> was just the GUI version of sudo.

I found that changing the HOME environment variable fixes problem

try executing kdesudo -c "HOME=$HOME dolphin"

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

[digikam] [Bug 372323] Camera autodetection fails when using AppImage bundle

[bugzilla_noreply]

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

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

   What|Removed |Added

 CC||caulier.gil...@gmail.com

--- Comment #1 from caulier.gil...@gmail.com ---
This is due certainly to use older lbgphoto2 from centoos6.8 instead a more
recent one. I tried to use last libgphoto2 but it do not compile under centos6
due to incompatible libjpeg which is also very old. So I must use more recent
low level dependencies for next 5.4.0 AppImage

Gilles caulier

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

[plasmashell] [Bug 359220] Widgets can't be moved or resized and right-side menu isn't shown regardless of widgets being locked or unlocked

[Simon Andric]

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

Simon Andric  changed:

   What|Removed |Added

 CC||simonandr...@gmail.com

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

[frameworks-kwidgetsaddons] [Bug 372392] Remains the bug 359220 (on Plasma 5.8.3) : Widgets can't be moved or resized and right-side menu isn't shown regardless of widgets being locked or unlocked

[Simon Andric]

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

Simon Andric  changed:

   What|Removed |Added

 CC||simonandr...@gmail.com

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

[ark] [Bug 365200] Open Recent action is enabled while opening an archive

[Elvis Angelaccio]

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

--- Comment #1 from Elvis Angelaccio  ---
Found the cause: the action is correctly disabled when the Part emits the busy
signal, but then m_recentFilesAction->addUrl(url) in MainWindow::openUrl()
unexpectedly enables the action again.

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

[plasmashell] [Bug 372396] New: plasma crash when passing from single to dual monitor

[Samuel Bernardo]

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

Bug ID: 372396
   Summary: plasma crash when passing from single to dual monitor
   Product: plasmashell
   Version: 5.8.3
  Platform: Compiled Sources
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: samuelbernardo.m...@gmail.com
CC: bhus...@gmail.com, plasma-b...@kde.org
  Target Milestone: 1.0

Application: plasmashell (5.8.3)
 (Compiled from sources)
Qt Version: 5.6.2
Frameworks Version: 5.27.0
Operating System: Linux 4.4.30-gentoox99 x86_64
Distribution: "Gentoo Base System release 2.2"

-- Information about the crash:
Connected the primary monitor that was disconnected before.

The crash can be reproduced every time.

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

Thread 11 (Thread 0x7f2b5a9a1700 (LWP 4968)):
#0  0x7f2b69af1cdd in poll () from /lib64/libc.so.6
#1  0x7f2b6db40882 in _xcb_conn_wait () from /usr/lib64/libxcb.so.1
#2  0x7f2b6db4266f in xcb_wait_for_event () from /usr/lib64/libxcb.so.1
#3  0x7f2b5cb06269 in QXcbEventReader::run() () from
/usr/lib64/libQt5XcbQpa.so.5
#4  0x7f2b6a1b3c0c in QThreadPrivate::start(void*) () from
/usr/lib64/libQt5Core.so.5
#5  0x7f2b69302434 in start_thread () from /lib64/libpthread.so.0
#6  0x7f2b69afadfd in clone () from /lib64/libc.so.6

Thread 10 (Thread 0x7f2b58d87700 (LWP 5035)):
#0  0x7f2b69af1cdd in poll () from /lib64/libc.so.6
#1  0x7f2b65b7cf5c in g_main_context_iterate.isra () from
/usr/lib64/libglib-2.0.so.0
#2  0x7f2b65b7d06c in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#3  0x7f2b6a3a62ac in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib64/libQt5Core.so.5
#4  0x7f2b6a357d8a in
QEventLoop::exec(QFlags) () from
/usr/lib64/libQt5Core.so.5
#5  0x7f2b6a1af444 in QThread::exec() () from /usr/lib64/libQt5Core.so.5
#6  0x7f2b6f28a0e5 in QDBusConnectionManager::run() () from
/usr/lib64/libQt5DBus.so.5
#7  0x7f2b6a1b3c0c in QThreadPrivate::start(void*) () from
/usr/lib64/libQt5Core.so.5
#8  0x7f2b69302434 in start_thread () from /lib64/libpthread.so.0
#9  0x7f2b69afadfd in clone () from /lib64/libc.so.6

Thread 9 (Thread 0x7f2b531e2700 (LWP 5111)):
#0  0x7f2b65bc0cc9 in g_mutex_lock () from /usr/lib64/libglib-2.0.so.0
#1  0x7f2b65b7c377 in g_main_context_prepare () from
/usr/lib64/libglib-2.0.so.0
#2  0x7f2b65b7ce88 in g_main_context_iterate.isra () from
/usr/lib64/libglib-2.0.so.0
#3  0x7f2b65b7d06c in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#4  0x7f2b6a3a62ac in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib64/libQt5Core.so.5
#5  0x7f2b6a357d8a in
QEventLoop::exec(QFlags) () from
/usr/lib64/libQt5Core.so.5
#6  0x7f2b6a1af444 in QThread::exec() () from /usr/lib64/libQt5Core.so.5
#7  0x7f2b6c9ed715 in QQmlThreadPrivate::run() () from
/usr/lib64/libQt5Qml.so.5
#8  0x7f2b6a1b3c0c in QThreadPrivate::start(void*) () from
/usr/lib64/libQt5Core.so.5
#9  0x7f2b69302434 in start_thread () from /lib64/libpthread.so.0
#10 0x7f2b69afadfd in clone () from /lib64/libc.so.6

Thread 8 (Thread 0x7f2b5101a700 (LWP 5128)):
#0  0x7f2b65bc0ce4 in g_mutex_unlock () from /usr/lib64/libglib-2.0.so.0
#1  0x7f2b65b7c799 in g_main_context_query () from
/usr/lib64/libglib-2.0.so.0
#2  0x7f2b65b7ced7 in g_main_context_iterate.isra () from
/usr/lib64/libglib-2.0.so.0
#3  0x7f2b65b7d06c in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#4  0x7f2b6a3a62ac in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib64/libQt5Core.so.5
#5  0x7f2b6a357d8a in
QEventLoop::exec(QFlags) () from
/usr/lib64/libQt5Core.so.5
#6  0x7f2b6a1af444 in QThread::exec() () from /usr/lib64/libQt5Core.so.5
#7  0x7f2b6c9ed715 in QQmlThreadPrivate::run() () from
/usr/lib64/libQt5Qml.so.5
#8  0x7f2b6a1b3c0c in QThreadPrivate::start(void*) () from
/usr/lib64/libQt5Core.so.5
#9  0x7f2b69302434 in start_thread () from /lib64/libpthread.so.0
#10 0x7f2b69afadfd in clone () from /lib64/libc.so.6

Thread 7 (Thread 0x7f2b4739e700 (LWP 5131)):
#0  0x7f2b6930800f in pthread_cond_wait () from /lib64/libpthread.so.0
#1  0x7f2b6ebd1b44 in QTWTF::TCMalloc_PageHeap::scavengerThread() () from
/usr/lib64/libQt5Script.so.5
#2  0x7f2b6ebd1b89 in QTWTF::TCMalloc_PageHeap::runScavengerThread(void*)
() from /usr/lib64/libQt5Script.so.5
#3  0x7f2b69302434 in start_thread () from /lib64/libpthread.so.0
#4  0x7f2b69afadfd in clone () from /lib64/libc.so.6

Thread 6 (Thread 0x7f2abc02b700 (LWP 5133)):
#0  0x7f2b69af1cdd in poll () from /lib64/libc.so.6

[digikam] [Bug 372326] digiKam crashed when closing it

[Maik Qualmann]

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

Maik Qualmann  changed:

   What|Removed |Added

 Resolution|--- |FIXED
  Latest Commit||http://commits.kde.org/digi
   ||kam/3f19074357ddccab2a56fff
   ||179225dd582ce20f6
   Version Fixed In||5.4.0
 Status|UNCONFIRMED |RESOLVED

--- Comment #1 from Maik Qualmann  ---
Git commit 3f19074357ddccab2a56fff179225dd582ce20f6 by Maik Qualmann.
Committed on 12/11/2016 at 19:53.
Pushed by mqualmann into branch 'master'.

shut down the LoadSaveThread at end
FIXED-IN: 5.4.0

M  +2-1NEWS
M  +1-1libs/threadimageio/loadsavethread.cpp

http://commits.kde.org/digikam/3f19074357ddccab2a56fff179225dd582ce20f6

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

[digikam] [Bug 372314] I cannot choose the template predefined in the import window while renaming (F2)

[bugzilla_noreply]

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

--- Comment #3 from piotergmo...@hotmail.com ---
Clicking on the list does nothing.

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

[digikam] [Bug 372314] I cannot choose the template predefined in the import window while renaming (F2)

[bugzilla_noreply]

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

--- Comment #2 from piotergmo...@hotmail.com ---
Created attachment 102190
  --> https://bugs.kde.org/attachment.cgi?id=102190=edit
Drop down not chooseable

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

[digikam] [Bug 372341] Title not showing in tool-tip

[Syiad]

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

--- Comment #2 from Syiad  ---
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Great to see that digikam is under such active development.

Thanks
Syiad

Am 12. November 2016 20:27:00 MEZ, schrieb Maik Qualmann
:
>https://bugs.kde.org/show_bug.cgi?id=372341
>
>Maik Qualmann  changed:
>
>   What|Removed |Added
>
> Status|UNCONFIRMED |RESOLVED
>   Version Fixed In||5.4.0
> Latest Commit||http://commits.kde.org/digi
>  ||kam/b52fe95f8adb920ab579d92
>   ||81ad3aaab8733a899
> Resolution|--- |FIXED
>
>--- Comment #1 from Maik Qualmann  ---
>Git commit b52fe95f8adb920ab579d9281ad3aaab8733a899 by Maik Qualmann.
>Committed on 12/11/2016 at 19:25.
>Pushed by mqualmann into branch 'master'.
>
>fix saving tooltip titles
>FIXED-IN: 5.4.0
>
>M  +2-1NEWS
>M  +2-0libs/settings/applicationsettings.cpp
>
>http://commits.kde.org/digikam/b52fe95f8adb920ab579d9281ad3aaab8733a899
-BEGIN PGP SIGNATURE-

iIcEAREKAC8oHFN5aWFkIFQuIEFsLUR1cmkgPHN5aWFkLmFsLWR1cmlAd2ViLmRl
PgUCWCdvGwAKCRC3myyjdhJEAxGtAP9Be2aIPjisQ3veaCTxOkwJ6S/wDAi2PIbn
Eb1XY+mAXAEAiXIaa+VULJG4JSGdCA+7M00/2VFPe4MoMi2vyohX25I=
=c4nA
-END PGP SIGNATURE-

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

[digikam] [Bug 372314] I cannot choose the template predefined in the import window while renaming (F2)

[Maik Qualmann]

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

Maik Qualmann  changed:

   What|Removed |Added

 CC||metzping...@gmail.com

--- Comment #1 from Maik Qualmann  ---
Problem is not reproducible here. Are all elements grayed out in the drop down
list? Maybe a screenshot?

Maik

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

[Akonadi] [Bug 332109] Excessive IO usage of akonadi_baloo feeder

[Allen Winter]

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

Allen Winter  changed:

   What|Removed |Added

 CC||win...@kde.org
 Resolution|WAITINGFORINFO  |WONTFIX
 Status|NEEDSINFO   |RESOLVED

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

[digikam] [Bug 372341] Title not showing in tool-tip

[Maik Qualmann]

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

Maik Qualmann  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
   Version Fixed In||5.4.0
  Latest Commit||http://commits.kde.org/digi
   ||kam/b52fe95f8adb920ab579d92
   ||81ad3aaab8733a899
 Resolution|--- |FIXED

--- Comment #1 from Maik Qualmann  ---
Git commit b52fe95f8adb920ab579d9281ad3aaab8733a899 by Maik Qualmann.
Committed on 12/11/2016 at 19:25.
Pushed by mqualmann into branch 'master'.

fix saving tooltip titles
FIXED-IN: 5.4.0

M  +2-1NEWS
M  +2-0libs/settings/applicationsettings.cpp

http://commits.kde.org/digikam/b52fe95f8adb920ab579d9281ad3aaab8733a899

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

[Akonadi] [Bug 332109] Excessive IO usage of akonadi_baloo feeder

[Vojtěch Zeisek]

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

--- Comment #7 from Vojtěch Zeisek  ---
OK, so this is another problem and this bug can be closed.

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

[kontact] [Bug 372395] Kontact crashed on close

[Tobias Guggenmos]

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

Tobias Guggenmos  changed:

   What|Removed |Added

Version|unspecified |5.3.0

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

[kontact] [Bug 372395] Kontact crashed on close

[Tobias Guggenmos]

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

Tobias Guggenmos  changed:

   What|Removed |Added

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

--- Comment #1 from Tobias Guggenmos  ---


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

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

[kontact] [Bug 364010] Kontact crashed on close

[Tobias Guggenmos]

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

Tobias Guggenmos  changed:

   What|Removed |Added

 CC||guggenmost.tr...@gmail.com

--- Comment #1 from Tobias Guggenmos  ---
*** Bug 372395 has been marked as a duplicate of this bug. ***

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

[kontact] [Bug 372395] New: Kontact crashed on close

[Tobias Guggenmos]

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

Bug ID: 372395
   Summary: Kontact crashed on close
   Product: kontact
   Version: unspecified
  Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdepim-b...@kde.org
  Reporter: guggenmost.tr...@gmail.com
  Target Milestone: ---

Application: kontact (5.3.0 (QtWebEngine))

Qt Version: 5.7.0
Frameworks Version: 5.27.0
Operating System: Linux 4.8.6-300.fc25.x86_64 x86_64
Distribution (Platform): Fedora RPMs

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

The Crash occured when closing Kontact after sending a Email with Kmail. The
Email had already been successfully send at that point of time.

The crash does not seem to be reproducible.

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

Thread 46 (Thread 0x7f24964e8700 (LWP 11959)):
#0  0x7f2643ae6a7b in idleTimerSourcePrepare(_GSource*, int*) () from
/lib64/libQt5Core.so.5
#1  0x7f2635fc1699 in g_main_context_prepare () from
/lib64/libglib-2.0.so.0
#2  0x7f2635fc207b in g_main_context_iterate.isra () from
/lib64/libglib-2.0.so.0
#3  0x7f2635fc226c in g_main_context_iteration () from
/lib64/libglib-2.0.so.0
#4  0x7f2643ae6d8b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /lib64/libQt5Core.so.5
#5  0x7f2643a980ba in
QEventLoop::exec(QFlags) () from
/lib64/libQt5Core.so.5
#6  0x7f26438f5643 in QThread::exec() () from /lib64/libQt5Core.so.5
#7  0x7f26438f9a1a in QThreadPrivate::start(void*) () from
/lib64/libQt5Core.so.5
#8  0x7f263aa476ca in start_thread () from /lib64/libpthread.so.0
#9  0x7f2642cecf6f in clone () from /lib64/libc.so.6

Thread 45 (Thread 0x7f2499770700 (LWP 9378)):
#0  0x7f2636007814 in g_mutex_unlock () from /lib64/libglib-2.0.so.0
#1  0x7f2635fc168c in g_main_context_prepare () from
/lib64/libglib-2.0.so.0
#2  0x7f2635fc207b in g_main_context_iterate.isra () from
/lib64/libglib-2.0.so.0
#3  0x7f2635fc226c in g_main_context_iteration () from
/lib64/libglib-2.0.so.0
#4  0x7f2643ae6d8b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /lib64/libQt5Core.so.5
#5  0x7f2643a980ba in
QEventLoop::exec(QFlags) () from
/lib64/libQt5Core.so.5
#6  0x7f26438f5643 in QThread::exec() () from /lib64/libQt5Core.so.5
#7  0x7f26438f9a1a in QThreadPrivate::start(void*) () from
/lib64/libQt5Core.so.5
#8  0x7f263aa476ca in start_thread () from /lib64/libpthread.so.0
#9  0x7f2642cecf6f in clone () from /lib64/libc.so.6

Thread 44 (Thread 0x7f2499f71700 (LWP 9376)):
#0  0x7f2635fc1fd9 in g_main_context_iterate.isra () from
/lib64/libglib-2.0.so.0
#1  0x7f2635fc226c in g_main_context_iteration () from
/lib64/libglib-2.0.so.0
#2  0x7f2643ae6d8b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /lib64/libQt5Core.so.5
#3  0x7f2643a980ba in
QEventLoop::exec(QFlags) () from
/lib64/libQt5Core.so.5
#4  0x7f26438f5643 in QThread::exec() () from /lib64/libQt5Core.so.5
#5  0x7f26438f9a1a in QThreadPrivate::start(void*) () from
/lib64/libQt5Core.so.5
#6  0x7f263aa476ca in start_thread () from /lib64/libpthread.so.0
#7  0x7f2642cecf6f in clone () from /lib64/libc.so.6

Thread 43 (Thread 0x7f249a772700 (LWP 9374)):
#0  0x7f26360077f9 in g_mutex_lock () from /lib64/libglib-2.0.so.0
#1  0x7f2635fc1bb6 in g_main_context_check () from /lib64/libglib-2.0.so.0
#2  0x7f2635fc20f4 in g_main_context_iterate.isra () from
/lib64/libglib-2.0.so.0
#3  0x7f2635fc226c in g_main_context_iteration () from
/lib64/libglib-2.0.so.0
#4  0x7f2643ae6d8b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /lib64/libQt5Core.so.5
#5  0x7f2643a980ba in
QEventLoop::exec(QFlags) () from
/lib64/libQt5Core.so.5
#6  0x7f26438f5643 in QThread::exec() () from /lib64/libQt5Core.so.5
#7  0x7f26438f9a1a in QThreadPrivate::start(void*) () from
/lib64/libQt5Core.so.5
#8  0x7f263aa476ca in start_thread () from /lib64/libpthread.so.0
#9  0x7f2642cecf6f in clone () from /lib64/libc.so.6

Thread 42 (Thread 0x7f249af73700 (LWP 9372)):
#0  0x7f2642ce100d in poll () from /lib64/libc.so.6
#1  0x7f2635fc2156 in g_main_context_iterate.isra () from
/lib64/libglib-2.0.so.0
#2  0x7f2635fc226c in g_main_context_iteration () from
/lib64/libglib-2.0.so.0
#3  0x7f2643ae6d8b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /lib64/libQt5Core.so.5
#4  0x7f2643a980ba in
QEventLoop::exec(QFlags) () from
/lib64/libQt5Core.so.5
#5  0x7f26438f5643 in QThread::exec() () from /lib64/libQt5Core.so.5
#6  0x7f26438f9a1a in QThreadPrivate::start(void*) () from
/lib64/libQt5Core.so.5
#7  0x7f263aa476ca in 

[digikam] [Bug 372164] Camera related photograph properties are unavailable (erroneously)

[Maik Qualmann]

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

--- Comment #6 from Maik Qualmann  ---
Created attachment 102189
  --> https://bugs.kde.org/attachment.cgi?id=102189=edit
Screenshot

Everything is displayed correctly.
Please test digiKam-5.3.0 AppImage bundle for Linux:

http://download.kde.org/stable/digikam/

Maik

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

[frameworks-kwallet] [Bug 370189] kwallet-query --list-entries does not work without folder

[Valentin Rusu]

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

Valentin Rusu  changed:

   What|Removed |Added

 Status|RESOLVED|CLOSED

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

[frameworks-kwallet] [Bug 370189] kwallet-query --list-entries does not work without folder

[Valentin Rusu]

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

Valentin Rusu  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |INVALID

--- Comment #4 from Valentin Rusu  ---
kwallet-query lists folders only from the "passwords" main directory, as seen
in the kwallet manager, when invoked with:

$ kwallet-query -l 

It's real use could be seen here:
https://github.com/valir/kwallet-dmenu

So, as suggested, I'll close this.

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

[plasmashell] [Bug 371975] Akonadi event still not shown

[Olivier Churlaud]

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

Olivier Churlaud  changed:

   What|Removed |Added

 Resolution|--- |WORKSFORME
 Status|UNCONFIRMED |RESOLVED

--- Comment #3 from Olivier Churlaud  ---
Removing completely solved the issue. Very strange. Thank you for the advice.

I close it as a workform. Cheers

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

[kfile] [Bug 312747] KDE file open dialog truncates showing of file/folder names

[Andreas Hartmetz]

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

Andreas Hartmetz  changed:

   What|Removed |Added

 CC||ahartm...@gmail.com

--- Comment #4 from Andreas Hartmetz  ---
The fix was more about the name column being too narrow even when just opening
one folder. By giving the other columns just their required widths and the rest
to the name column, the name column automatically gets the maximum possible
width, which kind of fixes this bug as a side effect.
The interactions are pretty complicated so I've only pushed the change to
master where it can get some testing and possibly further fixes.

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

[kipiplugins] [Bug 372380] Support for Digikam 5.2.0?

[Maik Qualmann]

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

Maik Qualmann  changed:

   What|Removed |Added

 CC||metzping...@gmail.com

--- Comment #2 from Maik Qualmann  ---
This is a package problem. Mediawiki is available here.
Please test digiKam-5.3.0 AppImage bundle for Linux:

http://download.kde.org/stable/digikam/

Maik

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

[kaddressbook] [Bug 371195] Edit Contact Name is missing Display Name field

[Kolya Ay]

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

Kolya Ay  changed:

   What|Removed |Added

 CC||kolya...@gmail.com

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

[kfile] [Bug 312747] KDE file open dialog truncates showing of file/folder names

[Andreas Hartmetz]

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

Andreas Hartmetz  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |FIXED
  Latest Commit||http://commits.kde.org/kio/
   ||9a997fba312f4d9596cc880685e
   ||c1e28deb7a665

--- Comment #3 from Andreas Hartmetz  ---
Git commit 9a997fba312f4d9596cc880685ec1e28deb7a665 by Andreas Hartmetz.
Committed on 12/11/2016 at 18:19.
Pushed by ahartmetz into branch 'master'.

Never stretch the last (=date) column in the file dialog.

Stretching the date column makes it appear to need the excessive
width when adding up non-name column widths in expandNameColumn().
The name column consequently became too narrow.
Now why could the date column expand if the names needed a lot of
space? It probably has something to do with expandNameColumn()
being called several times while the directory model is loading
and the exact order in which things are updated. Needs a more
detailed analysis if this change causes a regression or still
doesn't completely fix the problem.

M  +1-2src/filewidgets/kdiroperatordetailview.cpp

http://commits.kde.org/kio/9a997fba312f4d9596cc880685ec1e28deb7a665

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

[plasmashell] [Bug 372394] New: Executable: plasmashell PID: 8357 Signal: Segmentation fault (11)

[Don Curtis]

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

Bug ID: 372394
   Summary: Executable: plasmashell PID: 8357 Signal: Segmentation
fault (11)
   Product: plasmashell
   Version: 5.8.2
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: bugrprt21...@online.de
CC: bhus...@gmail.com, plasma-b...@kde.org
  Target Milestone: 1.0

Application: plasmashell (5.8.2)

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

-- Information about the crash:
openSUSE Leap 42.2 Release Candidate 2 (RC2)

- What I was doing when the application crashed:
New, fresh, user; 1st login; not yet logged out (no logout then re-login);
setting up the Digital Clock Plasmoid options -- Appearance; Calendar; Time
Zones; Holidays.

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

Thread 14 (Thread 0x7f976189a700 (LWP 9037)):
#0  0x7f983b6b449d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7f9837d2f314 in ?? () from /usr/lib64/libglib-2.0.so.0
#2  0x7f9837d2f42c in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#3  0x7f983bfc532b in QEventDispatcherGlib::processEvents
(this=0x7f97580008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:419
#4  0x7f983bf72fdb in QEventLoop::exec (this=this@entry=0x7f9761899cd0,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#5  0x7f983bdadf1a in QThread::exec (this=) at
thread/qthread.cpp:500
#6  0x7f983bdb29e9 in QThreadPrivate::start (arg=0x16ba7e0) at
thread/qthread_unix.cpp:341
#7  0x7f983aeb3734 in start_thread (arg=0x7f976189a700) at
pthread_create.c:334
#8  0x7f983b6bcd3d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 13 (Thread 0x7f976daba700 (LWP 9032)):
#0  0x7f9837d707d4 in g_mutex_unlock () from /usr/lib64/libglib-2.0.so.0
#1  0x7f9837d2ef0a in g_main_context_dispatch () from
/usr/lib64/libglib-2.0.so.0
#2  0x7f9837d2f388 in ?? () from /usr/lib64/libglib-2.0.so.0
#3  0x7f9837d2f42c in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#4  0x7f983bfc532b in QEventDispatcherGlib::processEvents
(this=0x7f975c003490, flags=...) at kernel/qeventdispatcher_glib.cpp:419
#5  0x7f983bf72fdb in QEventLoop::exec (this=this@entry=0x7f976dab9cb0,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#6  0x7f983bdadf1a in QThread::exec (this=) at
thread/qthread.cpp:500
#7  0x7f983f0df9b8 in ?? () from /usr/lib64/libQt5Qml.so.5
#8  0x7f983bdb29e9 in QThreadPrivate::start (arg=0x1d7d360) at
thread/qthread_unix.cpp:341
#9  0x7f983aeb3734 in start_thread (arg=0x7f976daba700) at
pthread_create.c:334
#10 0x7f983b6bcd3d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 12 (Thread 0x7f976ece2700 (LWP 8515)):
#0  0x7f983b6b449d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7f9837d2f314 in ?? () from /usr/lib64/libglib-2.0.so.0
#2  0x7f9837d2f42c in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#3  0x7f983bfc532b in QEventDispatcherGlib::processEvents
(this=0x7f97680008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:419
#4  0x7f983bf72fdb in QEventLoop::exec (this=this@entry=0x7f976ece1c90,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#5  0x7f983bdadf1a in QThread::exec (this=) at
thread/qthread.cpp:500
#6  0x7f97701348f7 in KCupsConnection::run() () from
/usr/lib64/libkcupslib.so
#7  0x7f983bdb29e9 in QThreadPrivate::start (arg=0x3a1eb30) at
thread/qthread_unix.cpp:341
#8  0x7f983aeb3734 in start_thread (arg=0x7f976ece2700) at
pthread_create.c:334
#9  0x7f983b6bcd3d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 11 (Thread 0x7f97fbfff700 (LWP 8504)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f98416b693b in ?? () from /usr/lib64/libQt5Script.so.5
#2  0x7f98416b6969 in ?? () from /usr/lib64/libQt5Script.so.5
#3  0x7f983aeb3734 in start_thread (arg=0x7f97fbfff700) at
pthread_create.c:334
#4  0x7f983b6bcd3d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 10 (Thread 0x7f9801f1a700 (LWP 8503)):
#0  0x7f983b6b449d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7f9837d2f314 in ?? () from /usr/lib64/libglib-2.0.so.0
#2  0x7f9837d2f42c in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#3  0x7f983bfc532b in QEventDispatcherGlib::processEvents
(this=0x7f97fc0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:419
#4  

[kwin] [Bug 372305] Crash in ContrastEffect::uploadRegion

[Martin Gräßlin]

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

--- Comment #3 from Martin Gräßlin  ---
> My mesa version is 13.0.0. Please tell me when you need further information

That's what I feared :-( Mesa 13 has a change that when a graphics reset
happens some methods will return a nullptr. And I think you run into that
problem here. To fix will be difficult as it can be many calls affected, so it
will be a little bit like whack-a-mole.

Important question: are you able to trigger the problem at will? If yes that
could end up super helpful as I could provide patches which should address it.

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

[gwenview] [Bug 361029] view ordering by name mismatch

[Konstantinos Smanis]

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

Konstantinos Smanis  changed:

   What|Removed |Added

 CC||konstantinos.smanis@gmail.c
   ||om

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

[digikam] [Bug 372378] Action after the search of the duplicated images

[Wolfgang Scheffner]

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

Wolfgang Scheffner  changed:

   What|Removed |Added

 CC||wscheffn...@gmail.com

--- Comment #1 from Wolfgang Scheffner  ---
Seems a bit difficult to me. How can an automated process decide which one of
two identical images to process (delete or whatever)? Of course you could set
the threshold to 100% and then say it doesn't matter, just process one of them.
But 1. your search result gets very small with 100% and 2. the process would
still need a rule to decide and that will most likely not match everybody's
needs.

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

[plasmashell] [Bug 372391] f25 plasma "networks" and "instant messaging" icons are invisible.

[Martin Gräßlin]

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

Martin Gräßlin  changed:

   What|Removed |Added

Product|plasma-integration  |plasmashell
   Target Milestone|--- |1.0
   Assignee|mgraess...@kde.org  |k...@davidedmundson.co.uk
 CC||bhus...@gmail.com,
   ||plasma-b...@kde.org
Version|unspecified |5.8.3
  Component|general |general

--- Comment #2 from Martin Gräßlin  ---
No idea where exactly the problem should be, but clearly not in
plasma-integration

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

[ark] [Bug 363719] Sidebar can not be resized even when the details are too long

[Elvis Angelaccio]

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

Elvis Angelaccio  changed:

   What|Removed |Added

 Status|REOPENED|RESOLVED
 Resolution|--- |FIXED
  Latest Commit|http://commits.kde.org/ark/ |http://commits.kde.org/ark/
   |e042955233662282813feac3d02 |a6a38b5bf64a58df332aa834411
   |e38beb2048929   |54fb85b68464d
   Version Fixed In|16.08.0 |16.12.0

--- Comment #10 from Elvis Angelaccio  ---
Git commit a6a38b5bf64a58df332aa83441154fb85b68464d by Elvis Angelaccio.
Committed on 12/11/2016 at 18:09.
Pushed by elvisangelaccio into branch 'master'.

infopanel: always use KSqueezedTextLabel

This ensures that resizing of the panel always works, no matter what the
Type label might contain.
FIXED-IN: 16.12.0

M  +10   -10   part/infopanel.ui

http://commits.kde.org/ark/a6a38b5bf64a58df332aa83441154fb85b68464d

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

[digikam] [Bug 372362] Build error due to private function

[Maik Qualmann]

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

Maik Qualmann  changed:

   What|Removed |Added

  Latest Commit||http://commits.kde.org/digi
   ||kam/ae97095f68795dcc114ca25
   ||4fa36eed2b141f53d
   Version Fixed In||5.4.0
 Resolution|--- |FIXED
 Status|UNCONFIRMED |RESOLVED

--- Comment #1 from Maik Qualmann  ---
Git commit ae97095f68795dcc114ca254fa36eed2b141f53d by Maik Qualmann.
Committed on 12/11/2016 at 18:00.
Pushed by mqualmann into branch 'master'.

fix compile current master branch
FIXED-IN: 5.4.0

M  +2-1NEWS
M  +5-4utilities/fuzzysearch/fuzzysearchview.cpp

http://commits.kde.org/digikam/ae97095f68795dcc114ca254fa36eed2b141f53d

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

[frameworks-kwindowsystem] [Bug 372389] kwindowsystem make test failures

[Allen Winter]

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

Allen Winter  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |INVALID

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

[ark] [Bug 372210] [unarchiver] Crash while trying to open or extract big archives

[Elvis Angelaccio]

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

--- Comment #18 from Elvis Angelaccio  ---
@Nikolay: patch up for review: https://phabricator.kde.org/D3350

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

[ark] [Bug 372210] [unarchiver] Crash while trying to open or extract big archives

[Elvis Angelaccio]

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

Elvis Angelaccio  changed:

   What|Removed |Added

  Component|general |plugins
   Assignee|elvis.angelac...@kde.org|rthoms...@gmail.com
 CC||elvis.angelac...@kde.org

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

[plasmashell] [Bug 372393] New: Remains the bug 359220 (on Plasma 5.8.3) : Widgets can't be moved or resized and right-side menu isn't shown regardless of widgets being locked or unlocked

[felipe . facundes]

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

Bug ID: 372393
   Summary: Remains the bug 359220 (on Plasma 5.8.3) : Widgets
can't be moved or resized and right-side menu isn't
shown regardless of widgets being locked or unlocked
   Product: plasmashell
   Version: 5.8.3
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Widget Explorer
  Assignee: plasma-b...@kde.org
  Reporter: felipe.facun...@gmail.com
  Target Milestone: 1.0

Created attachment 102188
  --> https://bugs.kde.org/attachment.cgi?id=102188=edit
Remains the bug 359220 (on Plasma 5.8.3) : Widgets can't be moved or resized
and right-side menu isn't shown regardless of widgets being locked or unlocked

Remains the bug 359220 (on Plasma 5.8.3) : Widgets can't be moved or resized
and right-side menu isn't shown regardless of widgets being locked or unlocked

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

[cirkuit] [Bug 366495] Image in preview window and output PDFs clipped in Kubuntu 16.04 and Mint 18

[Andrew]

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

--- Comment #1 from Andrew  ---
To fix patch src/lib/generator.cpp (replace lines 160-175 with that below).
Note epstool must be installed on your system.

if (in == Format::Dvi) {
if (out == Format::Postscript) {
QStringList args;
args << formatPath(in) << "-q" << QString("-o
%1").arg(formatPath(Format::Postscript));
return execute(new Command("dvips", "", args, this));
} else if (out == Format::Eps) {
QStringList args;
QString tmpfile = (d->tempFileInfo->baseName()) +
QString::fromAscii("-tmp");
args << "-E" << formatPath(in) << "-q" << "-o" <<
tmpfile.arg(formatPath(Format::Eps));
execute(new Command("dvips", "", args, this));
args.clear();
args << "--bbox"  << "--copy" << "--output" <<
formatPath(Format::Eps) << tmpfile.arg(formatPath(Format::Eps));
return execute(new Command("epstool", "", args, this));

} else {
bool b = true;
if (!convert(in,Format::Eps)) b = false;
if (!convert(Format::Eps,out)) b = false;
return b;
}
}

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

[frameworks-kwidgetsaddons] [Bug 372392] Remains the bug 359220 (on Plasma 5.8.3) : Widgets can't be moved or resized and right-side menu isn't shown regardless of widgets being locked or unlocked

[felipe . facundes]

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

--- Comment #1 from felipe.facundes  ---
Remains the bug 359220 (on Plasma 5.8.3) : Widgets can't be moved or resized
and right-side menu isn't shown regardless of widgets being locked or unlocked

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

[frameworks-kwidgetsaddons] [Bug 372392] New: Remains the bug 359220 (on Plasma 5.8.3) : Widgets can't be moved or resized and right-side menu isn't shown regardless of widgets being locked or unlocke

[felipe . facundes]

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

Bug ID: 372392
   Summary: Remains the bug 359220 (on Plasma 5.8.3) : Widgets
can't be moved or resized and right-side menu isn't
shown regardless of widgets being locked or unlocked
   Product: frameworks-kwidgetsaddons
   Version: 5.27.0
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: cf...@kde.org
  Reporter: felipe.facun...@gmail.com
CC: kdelibs-b...@kde.org
  Target Milestone: ---

Remains the bug 359220 (on Plasma 5.8.3) : Widgets can't be moved or resized
and right-side menu isn't shown regardless of widgets being locked or unlocked

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