[krusader] [Bug 376506] Problem at least when synchronizing zip files

[Toni Asensi Esteve]

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

--- Comment #2 from Toni Asensi Esteve  ---
Created attachment 104041
  --> https://bugs.kde.org/attachment.cgi?id=104041=edit
After the start button was pressed

If the "Synchronize" button is pressed and then the "Start" button is pressed,
then Krusader does not respond. 

if Krusader is closed and it's executed:
ps aux | grep -i [k]rusader
then it is seen something like this even when Krusader was closed:
user 13698  0.6  5.1 718532 82304 ?Sl   08:13   0:06
/usr/bin/krusader
user 13733  0.0  1.0 290172 15996 ?S08:25   0:00
kio_krarc.so [kdeinit5] krarc
local:/run/user/1000/klauncherTJ1377.1.slave-socket
local:/run/user/1000/krusadern13698.4.slave-socket
and then a command like
killall krusader
must be executed to regretfully do that to our dear Krusader :-)

Thanks for Krusader!

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

[krusader] [Bug 376506] Problem at least when synchronizing zip files

[Toni Asensi Esteve]

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

--- Comment #1 from Toni Asensi Esteve  ---
Created attachment 104040
  --> https://bugs.kde.org/attachment.cgi?id=104040=edit
Simple case

For example, in this simple case:

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

[krusader] [Bug 376506] New: Problem at least when synchronizing zip files

[Toni Asensi Esteve]

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

Bug ID: 376506
   Summary: Problem at least when synchronizing zip files
   Product: krusader
   Version: Git
  Platform: Compiled Sources
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: m...@fork.pl
  Reporter: toni.ase...@kdemail.net
  Target Milestone: ---

Using at least Kubuntu 16.10: it seems that there's a bug in Krusader at least 
when synchronizing zip files. I'll attach some screenshots.

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

[kmail2] [Bug 376381] Ability to skip spell-check

[Laurent Montel]

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

Laurent Montel  changed:

   What|Removed |Added

 Resolution|--- |FIXED
   Version Fixed In||5.5.0
 Status|UNCONFIRMED |RESOLVED
  Latest Commit||https://commits.kde.org/kpi
   ||mtextedit/684837d810bdeb922
   ||989951fc3a2c7430e91e888

--- Comment #4 from Laurent Montel  ---
Git commit 684837d810bdeb922989951fc3a2c7430e91e888 by Montel Laurent.
Committed on 15/02/2017 at 07:13.
Pushed by mlaurent into branch 'master'.

Fix Bug 376381 - Ability to skip spell-check

FIXED-IN: 5.5.0

M  +12   -0src/texteditor/richtexteditor/richtexteditor.cpp

https://commits.kde.org/kpimtextedit/684837d810bdeb922989951fc3a2c7430e91e888

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

[kwin] [Bug 376505] kwin compile error in Gentoo gcc-6.3.0, glibc-2.25

[Ясен]

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

Ясен  changed:

   What|Removed |Added

Product|plasmashell |kwin
   Target Milestone|1.0 |---
  Component|general |general

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

[plasmashell] [Bug 376505] New: kwin compile error in Gentoo gcc-6.3.0, glibc-2.25

[Ясен]

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

Bug ID: 376505
   Summary: kwin compile error in Gentoo gcc-6.3.0, glibc-2.25
   Product: plasmashell
   Version: 5.9.2
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: iasen.stoia...@gmail.com
CC: bhus...@gmail.com, plasma-b...@kde.org
  Target Milestone: 1.0

CBUILD="x86_64-pc-linux-gnu"
CFLAGS="-O2 -march=native -fPIC -pipe -fomit-frame-pointer"
CHOST="x86_64-pc-linux-gnu"
---

 83%] Building CXX object CMakeFiles/kwin.dir/logind.cpp.o
/usr/bin/x86_64-pc-linux-gnu-g++  -DKCOREADDONS_LIB -DQT_CONCURRENT_LIB
-DQT_CORE_LIB -DQT_DBUS_LIB -DQT_DISABLE_DEPRECATED_BEFORE=0 -DQT_GUI_LIB
-DQT_NETWORK_LIB -DQT_NO_DEBUG -DQT_QML_LIB -DQT_QUICK_LIB -DQT_SCRIPT_LIB
-DQT_USE_QSTRINGBUILDER -DQT_WIDGETS_LIB -DQT_X11EXTRAS_LIB -DQT_XML_LIB
-D_GNU_SOURCE -D_LARGEFILE64_SOURCE -Dkwin_EXPORTS
-I/home/portage/portage/kde-plasma/kwin-5.9.2/work/kwin-5.9.2_build
-I/home/portage/portage/kde-plasma/kwin-5.9.2/work/kwin-5.9.2
-I/home/portage/portage/kde-plasma/kwin-5.9.2/work/kwin-5.9.2/tabbox
-I/home/portage/portage/kde-plasma/kwin-5.9.2/work/kwin-5.9.2/effects
-I/home/portage/portage/kde-plasma/kwin-5.9.2/work/kwin-5.9.2/libkwineffects
-I/home/portage/portage/kde-plasma/kwin-5.9.2/work/kwin-5.9.2_build/libkwineffects
-I/home/portage/portage/kde-plasma/kwin-5.9.2/work/kwin-5.9.2_build/effects
-isystem /usr/include/qt5 -isystem /usr/include/qt5/QtDBus -isystem
/usr/include/qt5/QtCore -isystem /usr/lib64/qt5/mkspecs/linux-g++ -isystem
/usr/include/qt5/QtWidgets -isystem /usr/include/qt5/QtGui -isystem
/usr/include/KF5/KConfigCore -isystem /usr/include/KF5 -isystem
/usr/include/KF5/KCoreAddons -isystem /usr/include/KF5/KWindowSystem -isystem
/usr/include/KF5/KWayland/Server -isystem /usr/include/qt5/QtConcurrent
-isystem /usr/include/qt5/QtQuick -isystem /usr/include/qt5/QtQml -isystem
/usr/include/qt5/QtNetwork -isystem /usr/include/qt5/QtScript -isystem
/usr/include/qt5/QtX11Extras -isystem /usr/include/KF5/KConfigWidgets -isystem
/usr/include/KF5/KCodecs -isystem /usr/include/KF5/KWidgetsAddons -isystem
/usr/include/KF5/KConfigGui -isystem /usr/include/qt5/QtXml -isystem
/usr/include/KF5/KAuth -isystem /usr/include/KF5/KGlobalAccel -isystem
/usr/include/KF5/KService -isystem /usr/include/KF5/KI18n -isystem
/usr/include/KF5/KNotifications -isystem /usr/include/KF5/KPackage -isystem
/usr/include/KF5/Plasma -isystem /usr/include/KDecoration2 -isystem
/usr/include/KScreenLocker -isystem /usr/include/KF5/KActivities -isystem
/usr/include/KF5/KWayland/Client   -DQT_NO_DEBUG -DNDEBUG -O2 -march=native
-fPIC -pipe -fomit-frame-pointer -std=c++0x -fno-operator-names -fno-exceptions
-Wall -Wextra -Wcast-align -Wchar-subscripts -Wformat-security -Wno-long-long
-Wpointer-arith -Wundef -Wnon-virtual-dtor -Woverloaded-virtual
-Werror=return-type -fPIC -fvisibility=hidden -fvisibility-inlines-hidden  
-fPIC -std=gnu++11 -o CMakeFiles/kwin.dir/logind.cpp.o -c
/home/portage/portage/kde-plasma/kwin-5.9.2/work/kwin-5.9.2/logind.cpp
/home/portage/portage/kde-plasma/kwin-5.9.2/work/kwin-5.9.2/logind.cpp: In
member function ‘int KWin::LogindIntegration::takeDevice(const char*)’:
/home/portage/portage/kde-plasma/kwin-5.9.2/work/kwin-5.9.2/logind.cpp:315:65:
error: ‘major’ was not declared in this scope
 message.setArguments(QVariantList({QVariant(major(st.st_rdev)),
QVariant(minor(st.st_rdev))}));
 ^
/home/portage/portage/kde-plasma/kwin-5.9.2/work/kwin-5.9.2/logind.cpp:315:94:
error: ‘minor’ was not declared in this scope
 message.setArguments(QVariantList({QVariant(major(st.st_rdev)),
QVariant(minor(st.st_rdev))}));
   
  ^
/home/portage/portage/kde-plasma/kwin-5.9.2/work/kwin-5.9.2/logind.cpp:315:97:
error: no matching function for call to ‘QList::QList()’
 message.setArguments(QVariantList({QVariant(major(st.st_rdev)),
QVariant(minor(st.st_rdev))}));
   
 ^
In file included from /usr/include/qt5/QtCore/qobject.h:49:0,
 from /usr/include/qt5/QtCore/qcoreapplication.h:46,
 from /usr/include/qt5/QtCore/QCoreApplication:1,
 from
/home/portage/portage/kde-plasma/kwin-5.9.2/work/kwin-5.9.2/libkwineffects/kwinglobals.h:24,
 from
/home/portage/portage/kde-plasma/kwin-5.9.2/work/kwin-5.9.2/logind.h:23,
 from
/home/portage/portage/kde-plasma/kwin-5.9.2/work/kwin-5.9.2/logind.cpp:20:
/usr/include/qt5/QtCore/qlist.h:159:12: note: candidate:
QList::QList(std::initializer_list<_Tp>) [with T = QVariant]

[digikam] [Bug 376470] Title is not refreshed when read again metadata from file is launched

[Maik Qualmann]

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

Maik Qualmann  changed:

   What|Removed |Added

 CC||metzping...@gmail.com

--- Comment #2 from Maik Qualmann  ---
Created attachment 104039
  --> https://bugs.kde.org/attachment.cgi?id=104039=edit
titleLanguage.patch

If "x-default" language not found use the first language if available in the
titles map.

Maik

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

[digikam] [Bug 376470] Title is not refreshed when read again metadata from file is launched [patch]

[Maik Qualmann]

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

Maik Qualmann  changed:

   What|Removed |Added

Summary|Title is not refreshed when |Title is not refreshed when
   |read again metadata from|read again metadata from
   |file is launched|file is launched [patch]

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

[krita] [Bug 375878] Eraser will not switch back to brush after turning Wacom pen back around

[Diego]

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

Diego  changed:

   What|Removed |Added

 CC||eggowaffles...@gmail.com

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

[krita] [Bug 376160] selected brush changes to another when flipping the tip of the tablet pencil to the seccondary tip

[Diego]

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

Diego  changed:

   What|Removed |Added

 CC||eggowaffles...@gmail.com

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

[krunner] [Bug 375396] Opening files with krunner can spawn subprocesses which use 100% CPU

[kafei]

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

kafei  changed:

   What|Removed |Added

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

--- Comment #4 from kafei  ---
I still haven't been able to reproduce this over the past week, and can't
reproduce it now with Plasma 5.9.2, so I'm going to close this.

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

[kwin] [Bug 376457] Revert wrapping in window swithing

[Martin Gräßlin]

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

Martin Gräßlin  changed:

   What|Removed |Added

 Resolution|--- |WONTFIX
 Status|REOPENED|RESOLVED

--- Comment #7 from Martin Gräßlin  ---
I don't think that autorepeat changes anything. We have quite a few global
shortcuts which do not work correctly or do not make sense when keys auto
repeat. Common examples are Alt+Tab, Present Windows, Mute, etc. etc. In fact
only very few keys make sense with auto repeat, prominent example Lower/Raise
Audio.

Given that we don't have special handling for any global shortcut with regards
to auto repeat I don't think this needs adjustment. It is up to the user to
configure a global shortcut which won't auto repeat.

I'm setting this again to wontfix and this is the final maintainer decision.

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

[kate] [Bug 376504] New: Switching to Vi input mode causes a CPU usage spike

[V C]

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

Bug ID: 376504
   Summary: Switching to Vi input mode causes a CPU usage spike
   Product: kate
   Version: 16.08
  Platform: MS Windows
OS: MS Windows
Status: UNCONFIRMED
  Severity: major
  Priority: NOR
 Component: Vi Input Mode
  Assignee: kwrite-bugs-n...@kde.org
  Reporter: venka...@gmail.com
  Target Milestone: ---

On Windows, with v16.08.3, switching to 'Vi' input mode and performing some Vi
operation (in the command mode, say, :25,$s/^/#) causes a CPU spike (on my
system to over 23%) and stays up. This does not come down even when I switch
back to 'Normal' input mode.

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

[plasmashell] [Bug 376250] ignored clicks

[Vladyslav]

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

Vladyslav  changed:

   What|Removed |Added

 CC||innerm...@gmail.com

--- Comment #1 from Vladyslav  ---
I can reproduce this issue, too.

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

[frameworks-baloo] [Bug 376503] New: Baloo file extracter crash

[vikram goyal]

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

Bug ID: 376503
   Summary: Baloo file extracter crash
   Product: frameworks-baloo
   Version: 5.29.0
  Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: Baloo File Daemon
  Assignee: pinak.ah...@gmail.com
  Reporter: vikigo...@gmail.com
  Target Milestone: ---

Application: baloo_file_extractor (5.29.0)

Qt Version: 5.7.1
Frameworks Version: 5.29.0
Operating System: Linux 4.9.9-200.fc25.x86_64 x86_64
Distribution: "Fedora release 25 (Twenty Five)"

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

I was writing mail on Thunderbird, Firefox was running since previous day &
normal desktop activities were being done.

-- Backtrace:
Application: Baloo File Extractor (baloo_file_extractor), signal: Segmentation
fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f5839e238c0 (LWP 21229))]

Thread 3 (Thread 0x7f581a8ff700 (LWP 21231)):
#0  0x7f5836e2e01d in poll () at /lib64/libc.so.6
#1  0x7f5832a29156 in g_main_context_iterate.isra () at
/lib64/libglib-2.0.so.0
#2  0x7f5832a2926c in g_main_context_iteration () at
/lib64/libglib-2.0.so.0
#3  0x7f5837c346eb in
QEventDispatcherGlib::processEvents(QFlags) ()
at /lib64/libQt5Core.so.5
#4  0x7f5837be568a in
QEventLoop::exec(QFlags) () at
/lib64/libQt5Core.so.5
#5  0x7f5837a425e3 in QThread::exec() () at /lib64/libQt5Core.so.5
#6  0x7f5839f43739 in QDBusConnectionManager::run() () at
/lib64/libQt5DBus.so.5
#7  0x7f5837a469ca in QThreadPrivate::start(void*) () at
/lib64/libQt5Core.so.5
#8  0x7f583637c6ca in start_thread () at /lib64/libpthread.so.0
#9  0x7f5836e39f7f in clone () at /lib64/libc.so.6

Thread 2 (Thread 0x7f58239a3700 (LWP 21230)):
#0  0x7f5836e2e01d in poll () at /lib64/libc.so.6
#1  0x7f5831b63d10 in _xcb_conn_wait () at /lib64/libxcb.so.1
#2  0x7f5831b65aa9 in xcb_wait_for_event () at /lib64/libxcb.so.1
#3  0x7f582804cd69 in QXcbEventReader::run() () at /lib64/libQt5XcbQpa.so.5
#4  0x7f5837a469ca in QThreadPrivate::start(void*) () at
/lib64/libQt5Core.so.5
#5  0x7f583637c6ca in start_thread () at /lib64/libpthread.so.0
#6  0x7f5836e39f7f in clone () at /lib64/libc.so.6

Thread 1 (Thread 0x7f5839e238c0 (LWP 21229)):
[KCrash Handler]
#6  0x7f5836e86093 in __memcpy_ssse3 () at /lib64/libc.so.6
#7  0x7f5839228154 in Baloo::PostingCodec::decode(QByteArray const&) () at
/lib64/libKF5BalooEngine.so.5
#8  0x7f5839212b44 in Baloo::PostingDB::get(QByteArray const&) () at
/lib64/libKF5BalooEngine.so.5
#9  0x7f5839225088 in Baloo::WriteTransaction::commit() () at
/lib64/libKF5BalooEngine.so.5
#10 0x7f583921bf52 in Baloo::Transaction::commit() () at
/lib64/libKF5BalooEngine.so.5
#11 0x556b58d8944c in Baloo::App::processNextFile() ()
#12 0x7f5837c19996 in QSingleShotTimer::timerEvent(QTimerEvent*) () at
/lib64/libQt5Core.so.5
#13 0x7f5837c0e79b in QObject::event(QEvent*) () at /lib64/libQt5Core.so.5
#14 0x7f5838426ecc in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() at /lib64/libQt5Widgets.so.5
#15 0x7f583842e671 in QApplication::notify(QObject*, QEvent*) () at
/lib64/libQt5Widgets.so.5
#16 0x7f5837be66fa in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() at /lib64/libQt5Core.so.5
#17 0x7f5837c33ceb in QTimerInfoList::activateTimers() () at
/lib64/libQt5Core.so.5
#18 0x7f5837c34279 in idleTimerSourceDispatch(_GSource*, int (*)(void*),
void*) () at /lib64/libQt5Core.so.5
#19 0x7f5832a28e42 in g_main_context_dispatch () at /lib64/libglib-2.0.so.0
#20 0x7f5832a291c0 in g_main_context_iterate.isra () at
/lib64/libglib-2.0.so.0
#21 0x7f5832a2926c in g_main_context_iteration () at
/lib64/libglib-2.0.so.0
#22 0x7f5837c346cf in
QEventDispatcherGlib::processEvents(QFlags) ()
at /lib64/libQt5Core.so.5
#23 0x7f5837be568a in
QEventLoop::exec(QFlags) () at
/lib64/libQt5Core.so.5
#24 0x7f5837bed18c in QCoreApplication::exec() () at /lib64/libQt5Core.so.5
#25 0x556b58d881ff in main ()

Reported using DrKonqi

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

[kmail2] [Bug 376381] Ability to skip spell-check

[Vishnu]

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

--- Comment #3 from Vishnu  ---
Created attachment 104038
  --> https://bugs.kde.org/attachment.cgi?id=104038=edit
Spellcheck screen

As you can see in the attached image, there is no option to skip. The 'Ignore
All' button just ignores all instances of the word in question. So what is
requires is a separate 'Skip' button.

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

[frameworks-kactivities] [Bug 371924] KActivities shouldn't signal currentActivityChanged() unless it actually changed.

[Jamie Smith]

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

Jamie Smith  changed:

   What|Removed |Added

 Status|REOPENED|RESOLVED
 Resolution|--- |WORKSFORME

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

[plasma4] [Bug 354209] Taskbar "Show only task from the current screen" option Shows only the windows in the other screen

[Konstantin Pereiaslov]

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

Konstantin Pereiaslov  changed:

   What|Removed |Added

 CC||per...@perk11.info

--- Comment #2 from Konstantin Pereiaslov  ---
This happens in 5.9.1 every time I connect an external monitor.
After reboot the issue disappears.
Disconnecting monitor makes taskbar not show any windows at aall.

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

[k3b] [Bug 350403] DVD rip fails with [transcode] failed to open output

[Leslie Zhai]

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

Leslie Zhai  changed:

   What|Removed |Added

 CC||xiangzha...@gmail.com

--- Comment #6 from Leslie Zhai  ---
transcode was NO longer be maintained!
https://bitbucket.org/achurch_/transcode/pull-requests/1/migrate-to-ffmpeg-313/diff

It is able to use mplayer or vlc to rip dvd ;-)
http://www.leetcode.cn/2016/08/k3b.html#bug

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

[konqueror] [Bug 370177] No longer stores any configuration after removal of profile support

[bugzilla_noreply]

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

n...@leippe.com changed:

   What|Removed |Added

 CC||n...@leippe.com

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

[frameworks-kactivities] [Bug 371924] KActivities shouldn't signal currentActivityChanged() unless it actually changed.

[Jamie Smith]

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

--- Comment #13 from Jamie Smith  ---
Checking if the service is running seems to work.

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

[konsole] [Bug 372991] Terminal gets stuck on interrupting a program that is outputting, preventing further output from being shown

[Hello71]

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

--- Comment #5 from Hello71  ---
this is clearly some type of race condition, since it only breaks sometimes.

you can try "taskset -c 0 konsole", which for me fixes the problem.

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

[konsole] [Bug 376462] konsole stops displaying output after too much

[Hello71]

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

Hello71  changed:

   What|Removed |Added

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

--- Comment #7 from Hello71  ---


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

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

[konsole] [Bug 372991] Terminal gets stuck on interrupting a program that is outputting, preventing further output from being shown

[Hello71]

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

Hello71  changed:

   What|Removed |Added

 CC||alex_y...@yahoo.ca

--- Comment #4 from Hello71  ---
*** Bug 376462 has been marked as a duplicate of this bug. ***

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

[okular] [Bug 363776] Text selection begins prematurely following change to tool

[Jonathan]

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

--- Comment #5 from Jonathan  ---
Created attachment 104037
  --> https://bugs.kde.org/attachment.cgi?id=104037=edit
Patch to fix problem

It's not very elegant, but this patch solves the problem. It does this by
creating a function handleGenericRightButtonRelease, partly replacing handling
right-click in different places in the code. It has the beneficial side-effect
of resolving the inconsistent response to right-clicking while in text
selection mode as described here: https://git.reviewboard.kde.org/r/127496/

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

[kdeconnect] [Bug 373967] Android File System not Mounted and Pairing is no longer persistent.

[bugzilla_noreply]

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

--- Comment #8 from accoun...@christopherbartels.com ---
(In reply to Michael Tunnell from comment #5)
> > That's likely because you ran dolphin as root and it created files on your 
> > .cache directory
> 
> I did totally open it as root previously. It wasn't .cache that had weird
> permissions but rather it was "~/.config/kdeconnect/config". I renamed the
> folder for regenerating the folder and it seems to have worked. I then
> deleted the other older folder and will provide updates to whether this
> solved it or not. (so far it seems fixed)

Tried this, no effect. Same problem.

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

[kdeconnect] [Bug 373967] Android File System not Mounted and Pairing is no longer persistent.

[bugzilla_noreply]

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

--- Comment #7 from accoun...@christopherbartels.com ---
(In reply to Albert Vaca from comment #4)
> That's likely because you ran dolphin as root and it created files on your
> .cache directory, that you don't have permissions to change now. Delete
> .cache and it should get fixed. It's better if you first make sure all files
> under your home dir belong to you.

Ran #chown -R username:username /home/username/, then deleted
/home/username/.cache but the issue persists.

Please advise.

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

[krita] [Bug 376502] New: Eraser tip does not reset erase mode

[bugzilla_noreply]

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

Bug ID: 376502
   Summary: Eraser tip does not reset erase mode
   Product: krita
   Version: 3.1.2
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: tablet support
  Assignee: krita-bugs-n...@kde.org
  Reporter: m...@skeledong.me
  Target Milestone: ---

On my Intuos5 tablet, flipping the pen around to the eraser tip activates
eraser mode, as expected. However, flipping the pen back to the drawing end
causes the erase mode button to flip back off, but actually drawing with the
pen down erases instead of draws. I have to press "e" to manually turn off
erase mode (the state of the erase button does not change when I do this).

I don't think this is a driver issue, as the eraser tip works as expected in
Xournal, and it also worked in Krita until I updated to 3.1.2 a couple days
ago.

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

[plasmashell] [Bug 376501] New: Initial loading screen uses wrong resolution on one monitor if monitors have different resolutions

[Chris]

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

Bug ID: 376501
   Summary: Initial loading screen uses wrong resolution on one
monitor if monitors have different resolutions
   Product: plasmashell
   Version: master
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Multi-screen support
  Assignee: aleix...@kde.org
  Reporter: emailofch...@gmail.com
CC: plasma-b...@kde.org
  Target Milestone: 1.0

The black screen with the white KDE logo that appears while the desktop is
1920x1080 on my 4K DisplayPort monitor. My secondary monitor (HDMI) is 1080p,
and that's where SDDM shows up for some reason...
https://github.com/sddm/sddm/issues/115

If I have my secondary monitor disconnected, the loading screen fills up the
whole display and appears to be the correct resolution. If monitor 2 is
connected, whether it's enabled or not, the loading screen fills up a quarter
of the display.

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

[kalgebra] [Bug 373384] Only a single 3D graph plotted

[Aleix Pol]

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

Aleix Pol  changed:

   What|Removed |Added

 Status|CONFIRMED   |RESOLVED
  Latest Commit||https://commits.kde.org/kal
   ||gebra/cb101600d027a3e509f84
   ||24dec57af115d447a23
 Resolution|--- |FIXED

--- Comment #4 from Aleix Pol  ---
Git commit cb101600d027a3e509f8424dec57af115d447a23 by Aleix Pol.
Committed on 15/02/2017 at 00:00.
Pushed by apol into branch 'master'.

Use PlotsView3DES to render 3D plots

Uses the same code we use on the mobile version, which doesn't have the
reported bug.

M  +6-6src/kalgebra.cpp
M  +3-4src/kalgebra.h

https://commits.kde.org/kalgebra/cb101600d027a3e509f8424dec57af115d447a23

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

[kalgebra] [Bug 373384] Only a single 3D graph plotted

[Aleix Pol]

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

--- Comment #3 from Aleix Pol  ---
Git commit e10d40be86b1b27e3506c478ed28add7ffcb4ef3 by Aleix Pol.
Committed on 14/02/2017 at 23:58.
Pushed by apol into branch 'master'.

Consider Plotter3D, the non-OpenGLES version, deprecated

It wasn't working well (see reported bug) and it is essentially duplicating
effort.

M  +1-0analitzaplot/CMakeLists.txt
M  +6-17   analitzaplot/examples/plots3ddemo.cpp
M  +1-0analitzawidgets/CMakeLists.txt
M  +1-1analitzawidgets/plotsview3d.h

https://commits.kde.org/analitza/e10d40be86b1b27e3506c478ed28add7ffcb4ef3

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

[konsole] [Bug 373440] konsole --new-tab opens window instead

[Wolfgang Bauer]

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

--- Comment #23 from Wolfgang Bauer  ---
I can confirm that the fix doesn't work.
The --new-tab option still opens a new window if "Run all Konsole windows in a
single process" is disabled.

I tried the patch on top of 16.12.2 and also tried with the latest source from
git master.

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

[Plasma SDK] [Bug 376500] New: Emoji does not show up in plasmoidviewer

[Chris Holland]

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

Bug ID: 376500
   Summary: Emoji does not show up in plasmoidviewer
   Product: Plasma SDK
   Version: 5.9.1
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: plasmoidviewer
  Assignee: plasma-b...@kde.org
  Reporter: zrenf...@gmail.com
CC: giorgos.tsiapalio...@kde.org
  Target Milestone: ---

While debugging an emoji related crash, I found out that emojis don't show up
in plasmoidviewer, but will show up fine in plasmashell.

The character isn't a missing box glyph, it takes up space, it just doesn't
display anything.

Screenshots:
https://github.com/Zren/plasma-applets/issues/60#issuecomment-279560171
More info further down here:
https://github.com/Zren/plasma-applets/issues/60#issuecomment-279863928

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

[kmldonkey] [Bug 376499] New: KMldonkey crashes on startup

[Aitor]

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

Bug ID: 376499
   Summary: KMldonkey crashes on startup
   Product: kmldonkey
   Version: 2.0.7
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: gmazzurc...@gmail.com
  Reporter: m...@aitorpazos.es
  Target Milestone: ---

Application: kmldonkey (2.0.7)
KDE Platform Version: 4.14.29
Qt Version: 4.8.7
Operating System: Linux 4.9.9-1-default x86_64
Distribution: "openSUSE Tumbleweed"

-- Information about the crash:
This started happening after certain update. It was long ago so unfortunately I
can't provide the version.

- What I was doing when the application crashed:
KMldonkey crashes on every startup.

The crash can be reproduced every time.

-- Backtrace:
Application: KMLDonkey (kmldonkey), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[KCrash Handler]
#6  0x7f3d7757c1b0 in ServerInfo::isConnected() const () at
/usr/lib64/liblibkmldonkey.so.5
#7  0x7f3d77566692 in DonkeyProtocol::processMessage() () at
/usr/lib64/liblibkmldonkey.so.5
#8  0x7f3d743a95d0 in QMetaObject::activate(QObject*, QMetaObject const*,
int, void**) () at /usr/lib64/libQtCore.so.4
#9  0x7f3d7756baed in  () at /usr/lib64/liblibkmldonkey.so.5
#10 0x7f3d743a95d0 in QMetaObject::activate(QObject*, QMetaObject const*,
int, void**) () at /usr/lib64/libQtCore.so.4
#11 0x7f3d73860f2e in  () at /usr/lib64/libQtNetwork.so.4
#12 0x7f3d7386a4ad in  () at /usr/lib64/libQtNetwork.so.4
#13 0x7f3d748d50ec in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() at /usr/lib64/libQtGui.so.4
#14 0x7f3d748dbfec in QApplication::notify(QObject*, QEvent*) () at
/usr/lib64/libQtGui.so.4
#15 0x7f3d75b3067a in KApplication::notify(QObject*, QEvent*) () at
/usr/lib64/libkdeui.so.5
#16 0x7f3d743952cd in QCoreApplication::notifyInternal(QObject*, QEvent*)
() at /usr/lib64/libQtCore.so.4
#17 0x7f3d743c5e12 in  () at /usr/lib64/libQtCore.so.4
#18 0x7f3d6f414687 in g_main_context_dispatch (context=0x1e3a9c0) at
gmain.c:3203
#19 0x7f3d6f414687 in g_main_context_dispatch
(context=context@entry=0x1e3a9c0) at gmain.c:3856
#20 0x7f3d6f4148f0 in g_main_context_iterate
(context=context@entry=0x1e3a9c0, block=block@entry=1,
dispatch=dispatch@entry=1, self=) at gmain.c:3929
#21 0x7f3d6f41499c in g_main_context_iteration (context=0x1e3a9c0,
may_block=1) at gmain.c:3990
#22 0x7f3d743c582e in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQtCore.so.4
#23 0x7f3d7497ddb6 in  () at /usr/lib64/libQtGui.so.4
#24 0x7f3d74393b9f in
QEventLoop::processEvents(QFlags) () at
/usr/lib64/libQtCore.so.4
#25 0x7f3d74393f05 in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQtCore.so.4
#26 0x7f3d74399af9 in QCoreApplication::exec() () at
/usr/lib64/libQtCore.so.4
#27 0x0042660b in  ()
#28 0x7f3d73afc291 in __libc_start_main (main=0x426180, argc=5,
argv=0x7fffa392e398, init=, fini=,
rtld_fini=, stack_end=0x7fffa392e388) at ../csu/libc-start.c:289
#29 0x004267fa in _start ()

Reported using DrKonqi

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

[korganizer] [Bug 353240] Day numbers are cropped at the bottom in month view in korganizer

[bugzilla_noreply]

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

kzho...@gmail.com changed:

   What|Removed |Added

 Status|UNCONFIRMED |CONFIRMED
 Ever confirmed|0   |1

--- Comment #14 from kzho...@gmail.com ---
*** This bug has been confirmed by popular vote. ***

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

[kde] [Bug 376498] "Safe remove" should not be available for external drives containing OS install and/or /home folder

[bugzilla_noreply]

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

wor...@gmail.com changed:

   What|Removed |Added

 CC||wor...@gmail.com

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

[kde] [Bug 376498] New: "Safe remove" should not be available for external drives containing OS install and/or /home folder

[bugzilla_noreply]

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

Bug ID: 376498
   Summary: "Safe remove" should not be available for external
drives containing OS install and/or /home folder
   Product: kde
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: unassigned-b...@kde.org
  Reporter: wor...@gmail.com
  Target Milestone: ---

Reproducible: Always

Steps to reproduce:
1. Install any GNU/Linux distro and Plasma on external storage media, such as
USB flash drive or USB HDD/SSD (or regular one in external USB enclosure).
2. Boot into it.
3. Open the Device Notifier icon in system tray and check volumes available for
"safe unmount".
4. Open the default file manager (Dolphin) and right click the drive

Expected results: "safe remove" feature should not be available for volumes
containing / and/or /home folders and they should not be displayed in Device
Notifier on step #3. They cannot be safely unmounted anyway, so there's no
reason to show these volumes as safely removable.

Actual results: "safe remove" is available. When clicked, it complains that the
volume cannot be unmounted because it's still used by something. Due to this,
for example, Device Notifier icon wastes space on the screen if there are no
other removable devices connected.

I have up-to-date Arch Linux with KDE Plasma installed on SSD inside external
USB enclosure. If this matters, the drive is Samsung 840 Pro and the enclosure
is one of those based on ASM1351 chipset. The drive in enclosure is handled by
uas driver in the system. cat /sys/block/sdb/removable returns 0 (sdb is the
subject drive). The volumes, which are displayed in the tray are mounted at /
and /home.

The system is booted in UEFI mode, and what's interesting is that the ESP (EFI
System Partition), which is mounted at /boot, is not shown in system tray. I
switched to UEFI boot only recently, and noticed, that before the switch, the
/boot was shown in system tray among the other volumes. Not sure, however, if
this info is helpful.

None of these volumes are shown in system tray when the drive is connected to
the motherboard using regular internal SATA interface.

Also reproducible on freshly updated Kubuntu 16.10.
I was not able to reproduce the issue on latest and freshly updated Ubuntu
(Unity), Fedora Workstation (Gnome), and Arch with Gnome. They all don't show
the external drive in this case as safely removable, but show any other USB
storage devices as such.

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

[kig] [Bug 376477] wrong owner "root" for file install_manifest.txt after "make install"

[Maurizio Paolini]

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

--- Comment #2 from Maurizio Paolini  ---
This is the exact sequence of commands (as user "paolini") [omitting the
stdout/stderr of "cmake",
"make", "make install":

$ git clone g...@git.kde.org:kig
$ cd kig
$ cmake . -DCMAKE_INSTALL_PREFIX=/usr -DCMAKE_BUILD_TYPE=debugfull
-DPLUGIN_INSTALL_DIR:PATH=/usr/lib/qt5/plugins
$ make
$ su
Password: ***
# make install
# exit
$ ls -l | grep root
-rw-r--r-- 1 rootroot 18579 14 feb 23.51 install_manifest.txt

Perhaps there is something wrong in the cmake options that I use...

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

[kig] [Bug 376477] wrong owner "root" for file install_manifest.txt after "make install"

[Maurizio Paolini]

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

Maurizio Paolini  changed:

   What|Removed |Added

Summary|wrong owner "roor" for file |wrong owner "root" for file
   |install_manifest.txt after  |install_manifest.txt after
   |"make install"  |"make install"

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

[systemsettings] [Bug 372451] mouse cursor is small in titlebar, large elsewhere

[Ashley]

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

Ashley  changed:

   What|Removed |Added

 CC||ashleylest...@gmail.com

--- Comment #5 from Ashley  ---
I'm using KDE Neon (KDE 5.9 on Ubuntu 16.04). I'm running it on a Macbook with
Retina display. I scaled the display to 2x in system settings. 

The mouse cursor behaviour varies from run-to-run. It is normally the correct
size (i.e. 48x) when:

- on the desktop background
- within the window borders in an application, apart from Firefox
- on icons, text elements and the taskbar

It is normally the incorrect size (i.e. 24x) when:

- on the backgrounds of taskbar widgets, e.g. calender, launcher, volume, etc,
unless over a text element or icon within that taskbar widget
- on window borders (upper, lower, left, right) and the window title (i.e.
generally window decorations)

Setting the cursor size to 48x instead of resolution dependent does not affect
behaviour. Occasionally, a restart, or a power-down, wait a while, power-up,
fixes some instances. For example, right now, it's correct everywhere apart
from within the window borders on Firefox.

The behaviour does not seem to be dependent on cursor theme.

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

[Discover] [Bug 376354] Discover keeps crashing while trying to install apps

[Aleix Pol]

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

--- Comment #2 from Aleix Pol  ---
Something looks fishy. It's crashing upon daemonQuit, is PackageKit daemon
crashing too?

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

[frameworks-kactivities] [Bug 371924] KActivities shouldn't signal currentActivityChanged() unless it actually changed.

[Ivan Čukić]

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

--- Comment #12 from Ivan Čukić  ---
When the application starts, it does not have all the data synchronized with
the activity manager (the API is completely non-blocking). For it, the current
activity is null until it gets the data. When the data is received, then the
signal is sent - the activity is changed from the null activity to the proper
one.

Do you listen to the serviceStatusChanged signal? When it becomes Running, this
should meant that the sync is complete.

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

[krita] [Bug 376497] New: Krita crash at double click on polyline object.

[bugzilla_noreply]

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

Bug ID: 376497
   Summary: Krita crash at double click on polyline object.
   Product: krita
   Version: 3.1.1
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: krita-bugs-n...@kde.org
  Reporter: tuxtor...@openmailbox.org
  Target Milestone: ---

Application: krita (3.1.1)

Qt Version: 5.7.1
Frameworks Version: 5.30.0
Operating System: Linux 4.9.6-1-MANJARO x86_64
Distribution: "Manjaro Linux"

-- Information about the crash:
- What I was doing when the application crashed:
Double click selecting polyline objects, and at one moment it crashed,
without any apparent reason.

The crash does not seem to be reproducible.

-- Backtrace:
Application: Krita (krita), signal: Segmentation fault
Using host libthread_db library "/usr/lib/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fa3cc600c80 (LWP 5721))]

Thread 7 (Thread 0x7fa35bfff700 (LWP 5869)):
#0  0x7fa3c34104f7 in do_futex_wait.constprop () at
/usr/lib/libpthread.so.0
#1  0x7fa3c34105a4 in __new_sem_wait_slow.constprop.0 () at
/usr/lib/libpthread.so.0
#2  0x7fa3c2d3d99a in  () at /usr/lib/primus/libGL.so.1
#3  0x7fa3c3408454 in start_thread () at /usr/lib/libpthread.so.0
#4  0x7fa3c93d87df in clone () at /usr/lib/libc.so.6

Thread 6 (Thread 0x7fa363ffe700 (LWP 5868)):
#0  0x7fa3c34104f7 in do_futex_wait.constprop () at
/usr/lib/libpthread.so.0
#1  0x7fa3c34105a4 in __new_sem_wait_slow.constprop.0 () at
/usr/lib/libpthread.so.0
#2  0x7fa3c2d3b8da in  () at /usr/lib/primus/libGL.so.1
#3  0x7fa3c3408454 in start_thread () at /usr/lib/libpthread.so.0
#4  0x7fa3c93d87df in clone () at /usr/lib/libc.so.6

Thread 5 (Thread 0x7fa37e6a0700 (LWP 5812)):
#0  0x7fa3c340e10f in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7fa3c9cdab9b in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/libQt5Core.so.5
#2  0x7fa3cadb3c41 in  () at /usr/lib/libQt5Widgets.so.5
#3  0x7fa3c9cd9ce8 in  () at /usr/lib/libQt5Core.so.5
#4  0x7fa3c3408454 in start_thread () at /usr/lib/libpthread.so.0
#5  0x7fa3c93d87df in clone () at /usr/lib/libc.so.6

Thread 4 (Thread 0x7fa37f2a2700 (LWP 5803)):
#0  0x7fa3c340e10f in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7fa3c9cdab9b in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/libQt5Core.so.5
#2  0x7fa3c9cd3d86 in QSemaphore::tryAcquire(int, int) () at
/usr/lib/libQt5Core.so.5
#3  0x7fa3c74f30ca in KisTileDataSwapper::run() () at
/usr/lib/libkritaimage.so.16
#4  0x7fa3c9cd9ce8 in  () at /usr/lib/libQt5Core.so.5
#5  0x7fa3c3408454 in start_thread () at /usr/lib/libpthread.so.0
#6  0x7fa3c93d87df in clone () at /usr/lib/libc.so.6

Thread 3 (Thread 0x7fa37faa3700 (LWP 5802)):
#0  0x7fa3c340e10f in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7fa3c9cdab9b in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/libQt5Core.so.5
#2  0x7fa3c9cd3a93 in QSemaphore::acquire(int) () at
/usr/lib/libQt5Core.so.5
#3  0x7fa3c74d6c6d in  () at /usr/lib/libkritaimage.so.16
#4  0x7fa3c9cd9ce8 in  () at /usr/lib/libQt5Core.so.5
#5  0x7fa3c3408454 in start_thread () at /usr/lib/libpthread.so.0
#6  0x7fa3c93d87df in clone () at /usr/lib/libc.so.6

Thread 2 (Thread 0x7fa3a8f45700 (LWP 5723)):
#0  0x7ffe71bbeb02 in clock_gettime ()
#1  0x7fa3c93e56b6 in clock_gettime () at /usr/lib/libc.so.6
#2  0x7fa3c9d7f261 in  () at /usr/lib/libQt5Core.so.5
#3  0x7fa3c9f07119 in QTimerInfoList::updateCurrentTime() () at
/usr/lib/libQt5Core.so.5
#4  0x7fa3c9f076c5 in QTimerInfoList::timerWait(timespec&) () at
/usr/lib/libQt5Core.so.5
#5  0x7fa3c9f08a5e in  () at /usr/lib/libQt5Core.so.5
#6  0x7fa3c1db9c89 in g_main_context_prepare () at
/usr/lib/libglib-2.0.so.0
#7  0x7fa3c1dba6ab in  () at /usr/lib/libglib-2.0.so.0
#8  0x7fa3c1dba89c in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#9  0x7fa3c9f0948b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#10 0x7fa3c9eb2e9a in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#11 0x7fa3c9cd5053 in QThread::exec() () at /usr/lib/libQt5Core.so.5
#12 0x7fa3c3633de5 in  () at /usr/lib/libQt5DBus.so.5
#13 0x7fa3c9cd9ce8 in  () at /usr/lib/libQt5Core.so.5
#14 0x7fa3c3408454 in start_thread () at /usr/lib/libpthread.so.0
#15 0x7fa3c93d87df in clone () at /usr/lib/libc.so.6

Thread 1 (Thread 0x7fa3cc600c80 (LWP 5721)):
[KCrash Handler]
#6  0x7fa3c6acb2fe in KoSelection::count() const () at
/usr/lib/libkritaflake.so.16
#7  0x7fa3919ad46d in  () at /usr/lib/kritaplugins/krita_flaketools.so
#8  0x7fa3c6b2141e in 

[plasmashell] [Bug 376055] Plasma crashes when switching activities after unpinning a launcher specific to an activity

[Ivan Čukić]

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

--- Comment #10 from Ivan Čukić  ---
You'll need to install the packages which contain the debugging information.

This is unfortunately not helpful:

[KCrash Handler]
#6  0x7f0d790a2336 in ?? ()
#7  0x02befb90 in ?? ()
#8  0x7f0e2ad6af1c in QQmlData::signalEmitted(QAbstractDeclarativeData*,
QObject*, int, void**) () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5

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

[kdenlive] [Bug 376496] New: Video track size size stuck to small size

[bugzilla_noreply]

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

Bug ID: 376496
   Summary: Video track size size stuck to small size
   Product: kdenlive
   Version: 16.12.1
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: User Interface
  Assignee: j...@kdenlive.org
  Reporter: psub...@gmail.com
  Target Milestone: ---

Created attachment 104036
  --> https://bugs.kde.org/attachment.cgi?id=104036=edit
Screenshot showing small track size

Cannot make the size of the video and audio tracks bigger. Used to occupy the
entire space below monitor as shown on attachment.
Tried to change default settings with no success. Seems to stay that small even
when loading views made prior to bug.

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

[kdenlive] [Bug 376495] New: Bin effects expand when changing anything in the effect stack

[jooert]

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

Bug ID: 376495
   Summary: Bin effects expand when changing anything in the
effect stack
   Product: kdenlive
   Version: 16.12.1
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: User Interface
  Assignee: j...@kdenlive.org
  Reporter: johannes.oer...@uni-due.de
  Target Milestone: ---

Collapsed bin effects expand when reordering any effect in the stack or when
adding a new effect. This does not happen with clip effects.

(Version is 16.2.2)

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

[kdenlive] [Bug 376494] New: Bin effect parameters do not reset properly

[jooert]

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

Bug ID: 376494
   Summary: Bin effect parameters do not reset properly
   Product: kdenlive
   Version: 16.12.1
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: User Interface
  Assignee: j...@kdenlive.org
  Reporter: johannes.oer...@uni-due.de
  Target Milestone: ---

When hitting "Reset Effect" in a bin effect's menu, the viewer and the scopes
show the image as if the parameters were reset but the values of the effect
parameters in the properties window remain unchanged. If I click for example in
the timeline so that the bin effect window turns empty, the parameters have the
correct, reset values afterwards.

However, when I collapse the effect immediately after resetting, the old values
stay and the viewer and scopes show the image with these old values again.

This does not happen with clip effects.

(The correct version is actually 16.2.2, but Bugzilla doesn't offer that as an
option.)

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

[dolphin] [Bug 376493] New: Dolphin crashes after copying file to NTFS partition over NFS

[Gordon Parikh]

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

Bug ID: 376493
   Summary: Dolphin crashes after copying file to NTFS partition
over NFS
   Product: dolphin
   Version: 15.12.3
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: dolphin-bugs-n...@kde.org
  Reporter: chicagosox...@gmail.com
  Target Milestone: ---

Application: dolphin (15.12.3)

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

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

After copying a file from a POSIX-compliant NFS share to an NTFS partition
exported over NFS (which doesn't support permissions), Dolphin attempts to
change permissions on the new file and crashes. The expected behavior would be
to show the error message that permissions could not be changed, but to remain
open. While this is certainly not a typical situation that would be encountered
very often, the uncaught exception causing the program to crash is very
disruptive and should be handled differently.

The crash can be reproduced every time.

-- Backtrace:
Application: Dolphin (dolphin), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f8127b3e8c0 (LWP 4304))]

Thread 11 (Thread 0x7f8113ca2700 (LWP 4526)):
#0  0x7f81311a4a79 in g_mutex_lock () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#1  0x7f813115f929 in g_main_context_prepare () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f81311602bb in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f813116049c in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7f81357757eb in QEventDispatcherGlib::processEvents
(this=0x7f810c0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420
#5  0x7f813571cb4a in QEventLoop::exec (this=this@entry=0x7f8113ca1d00,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#6  0x7f8135539834 in QThread::exec (this=) at
thread/qthread.cpp:503
#7  0x7f813553e7be in QThreadPrivate::start (arg=0x12f7ce0) at
thread/qthread_unix.cpp:331
#8  0x7f8131cec6ba in start_thread (arg=0x7f8113ca2700) at
pthread_create.c:333
#9  0x7f813a97882d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 10 (Thread 0x7f8117626700 (LWP 4449)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f811ed41aa3 in ?? () from
/usr/lib/x86_64-linux-gnu/dri/swrast_dri.so
#2  0x7f811ed41907 in ?? () from
/usr/lib/x86_64-linux-gnu/dri/swrast_dri.so
#3  0x7f8131cec6ba in start_thread (arg=0x7f8117626700) at
pthread_create.c:333
#4  0x7f813a97882d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 9 (Thread 0x7f8117e27700 (LWP 4448)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f811ed41aa3 in ?? () from
/usr/lib/x86_64-linux-gnu/dri/swrast_dri.so
#2  0x7f811ed41907 in ?? () from
/usr/lib/x86_64-linux-gnu/dri/swrast_dri.so
#3  0x7f8131cec6ba in start_thread (arg=0x7f8117e27700) at
pthread_create.c:333
#4  0x7f813a97882d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 8 (Thread 0x7f8118628700 (LWP 4447)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f811ed41aa3 in ?? () from
/usr/lib/x86_64-linux-gnu/dri/swrast_dri.so
#2  0x7f811ed41907 in ?? () from
/usr/lib/x86_64-linux-gnu/dri/swrast_dri.so
#3  0x7f8131cec6ba in start_thread (arg=0x7f8118628700) at
pthread_create.c:333
#4  0x7f813a97882d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 7 (Thread 0x7f8118e29700 (LWP 4446)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f811ed41aa3 in ?? () from
/usr/lib/x86_64-linux-gnu/dri/swrast_dri.so
#2  0x7f811ed41907 in ?? () from
/usr/lib/x86_64-linux-gnu/dri/swrast_dri.so
#3  0x7f8131cec6ba in start_thread (arg=0x7f8118e29700) at
pthread_create.c:333
#4  0x7f813a97882d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 6 (Thread 0x7f811962a700 (LWP 4445)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f811ed41aa3 in ?? () from
/usr/lib/x86_64-linux-gnu/dri/swrast_dri.so
#2  0x7f811ed41907 in ?? () from
/usr/lib/x86_64-linux-gnu/dri/swrast_dri.so
#3  0x7f8131cec6ba in start_thread (arg=0x7f811962a700) at
pthread_create.c:333
#4  0x7f813a97882d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 5 (Thread 0x7f8119e2b700 (LWP )):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at

[systemsettings] [Bug 376492] New: System Settings Crash

[bugzilla_noreply]

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

Bug ID: 376492
   Summary: System Settings Crash
   Product: systemsettings
   Version: 5.9.1
  Platform: Neon Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: cyni...@hush.ai
  Target Milestone: ---

Application: systemsettings5 (5.9.1)

Qt Version: 5.7.1
Frameworks Version: 5.30.0
Operating System: Linux 4.4.0-63-generic x86_64
Distribution: KDE neon User Edition 5.9

-- Information about the crash:
- What I was doing when the application crashed:Hit the back button on system
settings. I was in "Desktop Behavior" looking at different options. Hit the
"All Settings"
button to go back and it crashed. This is not the first time this has happened.

-- Backtrace:
Application: System Settings (systemsettings5), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fa15dfc18c0 (LWP 11890))]

Thread 9 (Thread 0x7fa0fedf1700 (LWP 11912)):
#0  0x7fa15adeb329 in QMutex::unlock() () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#1  0x7fa15b013ec1 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#2  0x7fa15584991d in g_main_context_prepare () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7fa15584a2bb in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7fa15584a49c in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x7fa15b01475b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7fa15afbf0ba in
QEventLoop::exec(QFlags) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7fa15adeef64 in QThread::exec() () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x7fa15adf3b48 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#9  0x7fa1579056ba in start_thread (arg=0x7fa0fedf1700) at
pthread_create.c:333
#10 0x7fa15a70082d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 8 (Thread 0x7fa10d4f7700 (LWP 11908)):
#0  0x7fa15adeb329 in QMutex::unlock() () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#1  0x7fa15b013ec1 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#2  0x7fa15584991d in g_main_context_prepare () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7fa15584a2bb in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7fa15584a49c in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x7fa15b01475b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7fa15afbf0ba in
QEventLoop::exec(QFlags) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7fa15adeef64 in QThread::exec() () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x7fa15adf3b48 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#9  0x7fa1579056ba in start_thread (arg=0x7fa10d4f7700) at
pthread_create.c:333
#10 0x7fa15a70082d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 7 (Thread 0x7fa10effe700 (LWP 11905)):
#0  0x7fa15588e653 in g_private_get () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#1  0x7fa155871060 in g_thread_self () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7fa15584930c in g_main_context_acquire () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7fa15584a245 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7fa15584a49c in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x7fa15b01475b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7fa15afbf0ba in
QEventLoop::exec(QFlags) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7fa15adeef64 in QThread::exec() () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x7fa15974bbf5 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5
#9  0x7fa15adf3b48 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#10 0x7fa1579056ba in start_thread (arg=0x7fa10effe700) at
pthread_create.c:333
#11 0x7fa15a70082d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 6 (Thread 0x7fa115e3d700 (LWP 11900)):
#0  0x7fa15a6f4b5d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7fa15584a38c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7fa15584a49c in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7fa15b01475b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7fa15afbf0ba in
QEventLoop::exec(QFlags) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7fa15adeef64 in QThread::exec() () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  

[okular] [Bug 363776] Text selection begins prematurely following change to tool

[Jonathan]

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

--- Comment #4 from Jonathan  ---
I just reproduced the problem once again using Okular from Debian/unstable.
I've attached a copy of the PDF and a screen capture video to demonstrate. The
important bit to notice is at 0:22 after I choose "Text Selection Tool" from
the "Tools" menu. I then move the mouse across the text, which begins selecting
even though I have not pressed the mouse button to begin selection.

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

[okular] [Bug 363776] Text selection begins prematurely following change to tool

[Jonathan]

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

--- Comment #3 from Jonathan  ---
Created attachment 104035
  --> https://bugs.kde.org/attachment.cgi?id=104035=edit
Screen capture video demonstrating bug

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

[okular] [Bug 363776] Text selection begins prematurely following change to tool

[Jonathan]

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

--- Comment #2 from Jonathan  ---
Created attachment 104034
  --> https://bugs.kde.org/attachment.cgi?id=104034=edit
PDF that demonstrates bug

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

[Akonadi] [Bug 376220] Crash in Akonadi::Monitor::mimeTypesMonitored

[Kai Uwe Broulik]

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

Kai Uwe Broulik  changed:

   What|Removed |Added

  Component|general |general
 CC||k...@privat.broulik.de
   Assignee|k...@davidedmundson.co.uk|kdepim-b...@kde.org
Product|plasmashell |Akonadi
   Target Milestone|1.0 |---
Version|5.9.1   |unspecified
Summary|Browsing the Plasma5|Crash in
   |Extensions  |Akonadi::Monitor::mimeTypes
   ||Monitored

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

[plasmashell] [Bug 376449] Plasma (plasmashell), signal: Segmentation fault out of the blue and unrelated to the actual activity

[Kai Uwe Broulik]

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

Kai Uwe Broulik  changed:

   What|Removed |Added

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

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


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

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

[plasmashell] [Bug 376220] Browsing the Plasma5 Extensions

[Kai Uwe Broulik]

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

Kai Uwe Broulik  changed:

   What|Removed |Added

 CC||bugrprt21...@online.de

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

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

[systemsettings] [Bug 376490] KDE5 does not allow configuration of units of measure, time, or date format separate from the single value allowed by locale

[Christoph Feck]

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

Christoph Feck  changed:

   What|Removed |Added

   Assignee|caslav.i...@gmx.net |se...@kde.org
  Component|klocale |kcm_formats
Product|kdelibs |systemsettings
   Severity|major   |wishlist

--- Comment #1 from Christoph Feck  ---
> KDE4 let me configure use of ISO date-time values system wide

What you configured in KDE4 systemsettings only affected KDE4 application
(those the used KLocale class). Any other Qt, GTK, or bash application used the
system locale, which was not configurable.

For applications based on KF5, we have abandoned KLocale, and now are using Qt
to format numbers according to the locale. Unfortunately, Qt's QLocale does not
allow customization yet.

See also bug 340982.

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

[dragonplayer] [Bug 222844] Dragon Player cannot skip to previous track or next track of an audio CD

[Dr . Chapatin]

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

Dr. Chapatin  changed:

   What|Removed |Added

 CC||yy...@gmx.com

--- Comment #3 from Dr. Chapatin  ---
More than 3 years later and this bug is still present.
Dragon plays only the first track from audio cds.

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

[kdeconnect] [Bug 376491] unable to ignore unknown devices

[Albert Vaca]

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

Albert Vaca  changed:

   What|Removed |Added

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

--- Comment #1 from Albert Vaca  ---
KDE Connect indicator is an independent project, and not part of the KDE
Connect project nor the KDE community. Please report the bug to the author of
KDE Connect indicator.

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

[kdeconnect] [Bug 376491] New: unable to ignore unknown devices

[Andrés Alcarraz]

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

Bug ID: 376491
   Summary: unable to ignore unknown devices
   Product: kdeconnect
   Version: 0.8
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: minor
  Priority: NOR
 Component: common
  Assignee: albertv...@gmail.com
  Reporter: alcar...@gmail.com
  Target Milestone: ---

Hi, this is more a feature request than a bug, but this is the only place I
encountered to express my problem.

I'm using kde connect indicator in unity and in a big wifi I see an entry in
the indicators panel for each device. I would like to be able to somehow ignore
devices that I know they're not mine so they stop appearing in the indicators
panel.

Thank you in advance

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

[kdelibs] [Bug 376490] New: KDE5 does not allow configuration of units of measure, time, or date format separate from the single value allowed by locale

[Kevin Coonan]

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

Bug ID: 376490
   Summary: KDE5 does not allow configuration of units of measure,
time, or date format separate from the single value
allowed by locale
   Product: kdelibs
   Version: unspecified
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: major
  Priority: NOR
 Component: klocale
  Assignee: caslav.i...@gmx.net
  Reporter: kevin.coo...@gmail.com
  Target Milestone: ---

Users in a given locale have different requirements for date-time format and
use of units.  In the United States, in spite of many (if not a majority)
clinging to the Imperial units of measure, many communities (e.g. military,
medicine, science, transportation, weather) routinely use ISO date-time and/or
metric units of measure.  Different communities have different
per-measurement-type preferences (e.g. in medicine we use mm and cm quite a
bit, km not so much) even within the broad scope of the metric system.

This is a solved problem, with well described options.  For example, while
units of measurement were limited to what the OS actually used (quite
reasonable), KDE4 let me configure use of ISO date-time values system wide.

KDE5 apparently ignored this rather significant user requirement.

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

[kdevelop] [Bug 354444] Let user set the C++ standard version globally

[Sven Brauch]

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

--- Comment #7 from Sven Brauch  ---
I'd suggest to implement a feature which queries the C++ standard from the
project manager. That will make it work for at least cmake projects
automatically.

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

[kdevelop] [Bug 375849] Show annotate on current document doesn't work in a git worktree

[Sven Brauch]

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

Sven Brauch  changed:

   What|Removed |Added

 CC||m...@svenbrauch.de

--- Comment #2 from Sven Brauch  ---
The place where this needs to be fixed I think is
plugins/git/gitplugin.cpp:QUrl GitPlugin::repositoryRoot(const QUrl& path).

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

[kaffeine] [Bug 376206] Kaffeine partly not translated

[bugzilla_noreply]

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

--- Comment #7 from yuli...@mailbox.org ---
I looked at the code and found out that KWrite uses the same function
(QFileDialog::getOpenFileUrls) for the dialogue as kaffeine does. Both use the
same QT version and so on, and for me it makes no sense why the KWrite dialogue
is translated and the one in kaffeine not. Apart from the open file dialogue
both applications are completely translated.
Maybe for a programmer it is easier to find out what the difference could be.

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

[kdevelop] [Bug 376432] kdevelop is calling utimes() on a C/C++ file

[Sven Brauch]

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

Sven Brauch  changed:

   What|Removed |Added

 CC||m...@svenbrauch.de

--- Comment #9 from Sven Brauch  ---
KDevelop still references unsermake? Patches removing that are very welcome.

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

[valgrind] [Bug 370028] Reduce the number of compiler warnings on MIPS platforms

[Ivo Raisr]

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

--- Comment #17 from Ivo Raisr  ---
I was also wondering of the impact on other architectures.
Please could you conduct a quick test to see how the compiler resolves
ASSUME_ALIGNED on amd64/ppc, for example? And mips/arm for comparison?
Perhaps we will see that the assembly both cases (with and without
ASSUME_ALIGNED) is the same, perhaps not. If not, then the implementation of
ASSUME_ALIGNED should be guarded with the corresponding arch-specific #ifdefs.

Please supply the fixed first patch afterwards.

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

[kdesvn] [Bug 375776] KF5-based doesn't display the authorization dialog for ssh

[Safa Alfulaij]

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

--- Comment #2 from Safa Alfulaij  ---
I faced it even before Plasma 5.8 maybe :-)
Months months ago..

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

[kdesvn] [Bug 375776] KF5-based doesn't display the authorization dialog for ssh

[Christoph Feck]

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

--- Comment #1 from Christoph Feck  ---
If this requires ksshaskpass, and this error only appears in Plasma 5.9, it
could be a duplicate of bug 376228.

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

[digikam] [Bug 376489] New: Pentax K-5

[Gustav]

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

Bug ID: 376489
   Summary: Pentax K-5
   Product: digikam
   Version: 5.4.0
  Platform: Other
OS: MS Windows
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Metadata
  Assignee: digikam-de...@kde.org
  Reporter: gustav-g...@web.de
  Target Milestone: ---

Hello,
since version 5.4, digikam can not read metadata (Pentax K-5)and crashes
regularly. Only at the pentax.
Version 5.3 was Error-free.
Greatings from Berlin
Stephan

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

[krita] [Bug 376488] New: krita crashes

[enriK]

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

Bug ID: 376488
   Summary: krita crashes
   Product: krita
   Version: unspecified
  Platform: Windows CE
OS: Windows CE
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: krita-bugs-n...@kde.org
  Reporter: planning...@hotmail.com
  Target Milestone: ---

Krita crashes when i open the program, few seconds later. 

System Windows 7 64 bit
4 GB RAM
Dell Inspiron N7010

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

[krunner] [Bug 376483] Krunner Segmentation fault

[André Martins]

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

--- Comment #4 from André Martins  ---
That didn't work, I had to do the following

$ gdb /usr/bin/krunner
GNU gdb (GDB) Fedora 7.12.1-41.fc25
...
Reading symbols from /usr/bin/krunner...Reading symbols from
/usr/lib/debug/usr/bin/krunner.debug...done.
done.
(gdb) b exit
Function "exit" not defined.
Make breakpoint pending on future shared library load? (y or [n]) y
Breakpoint 1 (exit) pending.
(gdb) b _exit
Function "_exit" not defined.
Make breakpoint pending on future shared library load? (y or [n]) y
Breakpoint 2 (_exit) pending.
(gdb) b __exit
Function "__exit" not defined.
Make breakpoint pending on future shared library load? (y or [n]) y
Breakpoint 3 (__exit) pending.
(gdb) run
Starting program: /usr/bin/krunner 
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib64/libthread_db.so.1".
[New Thread 0x7fffd972a700 (LWP 22336)]
[New Thread 0x7fffd3df5700 (LWP 22370)]

Thread 1 "krunner" hit Breakpoint 1, __GI_exit (status=status@entry=0) at
exit.c:105
105   __run_exit_handlers (status, &__exit_funcs, true, true);
(gdb) bt
#0  0x73840450 in __GI_exit (status=status@entry=0) at exit.c:105
#1  0x75f09f45 in
KDBusService::KDBusService(QFlags, QObject*)
(this=, options=..., parent=) at
/usr/src/debug/kdbusaddons-5.29.0/src/kdbusservice.cpp:129
#2  0xa847 in main(int, char**) (argc=,
argv=)
at /usr/src/debug/plasma-workspace-5.8.5/krunner/main.cpp:69
(gdb) thread apply all bt

Thread 3 (Thread 0x7fffd3df5700 (LWP 22370)):
#0  0x7390201d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7fffeb8c4156 in g_main_context_poll (priority=,
n_fds=2, fds=0x7fffcc003020, timeout=, context=0x7fffcc000990)
at gmain.c:4228
#2  0x7fffeb8c4156 in g_main_context_iterate
(context=context@entry=0x7fffcc000990, block=block@entry=1,
dispatch=dispatch@entry=1, self=) at gmain.c:3924
#3  0x7fffeb8c426c in g_main_context_iteration (context=0x7fffcc000990,
may_block=may_block@entry=1) at gmain.c:3990
#4  0x747086cf in
QEventDispatcherGlib::processEvents(QFlags)
(this=0x7fffcc0008c0, flags=...)
at kernel/qeventdispatcher_glib.cpp:423
#5  0x746b968a in
QEventLoop::exec(QFlags)
(this=this@entry=0x7fffd3df4c40, flags=..., 
flags@entry=...) at kernel/qeventloop.cpp:212
#6  0x745165e3 in QThread::exec() (this=this@entry=0x77fc2060
<(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at
thread/qthread.cpp:507
#7  0x77f4c739 in QDBusConnectionManager::run() (this=0x77fc2060
<(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at
qdbusconnection.cpp:178
#8  0x7451a9ca in QThreadPrivate::start(void*) (arg=0x77fc2060
<(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at
thread/qthread_unix.cpp:368
#9  0x703246ca in start_thread (arg=0x7fffd3df5700) at
pthread_create.c:333
#10 0x7390df7f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:105

Thread 2 (Thread 0x7fffd972a700 (LWP 22336)):
#0  0x7390201d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x72969d10 in poll (__timeout=-1, __nfds=1, __fds=0x7fffd9729b80)
at /usr/include/bits/poll2.h:46
#2  0x72969d10 in _xcb_conn_wait (c=c@entry=0x55796490,
cond=cond@entry=0x557964d0, vector=vector@entry=0x0, count=count@entry=0x0)
at xcb_conn.c:479
#3  0x7296baa9 in xcb_wait_for_event (c=0x55796490) at xcb_in.c:693
#4  0x7fffdcf7fd69 in QXcbEventReader::run() (this=0x557a0b60) at
qxcbconnection.cpp:1343
#5  0x7451a9ca in QThreadPrivate::start(void*) (arg=0x557a0b60) at
thread/qthread_unix.cpp:368
#6  0x703246ca in start_thread (arg=0x7fffd972a700) at
pthread_create.c:333
#7  0x7390df7f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:105

Thread 1 (Thread 0x77e17940 (LWP 22250)):
#0  0x73840450 in __GI_exit (status=status@entry=0) at exit.c:105
---Type  to continue, or q  to quit---
#1  0x75f09f45 in
KDBusService::KDBusService(QFlags, QObject*)
(this=, options=..., parent=) at
/usr/src/debug/kdbusaddons-5.29.0/src/kdbusservice.cpp:129
#2  0xa847 in main(int, char**) (argc=,
argv=)
at /usr/src/debug/plasma-workspace-5.8.5/krunner/main.cpp:69

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

[plasmashell] [Bug 368522] systray: thunderbird icon gone

[arne anka]

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

--- Comment #3 from arne anka  ---
seems to be fixed now.

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

[kaffeine] [Bug 375811] Siano driver stopped working after upgrading to Kernel 4.9

[Mauro Carvalho Chehab]

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

Mauro Carvalho Chehab  changed:

   What|Removed |Added

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

--- Comment #5 from Mauro Carvalho Chehab  ---
As this is a Kernel bug, whose patch was sent upstream, I'm marking it as
fixed.

It should be available soon at Kernel 4.10, and backported to Kernel 4.9 by
Kernel stable maintainers. It could take a while until distributions backport
them to their Kernels.

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

[www.kde.org] [Bug 376479] Make banners & pictures linked, not just the "Learn more" box

[Albert Astals Cid]

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

Albert Astals Cid  changed:

   What|Removed |Added

 CC||aa...@kde.org

--- Comment #1 from Albert Astals Cid  ---
+1 on https://www.kde.org/products i really want to click on the images.

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

[kaffeine] [Bug 375811] Siano driver stopped working after upgrading to Kernel 4.9

[Mauro Carvalho Chehab]

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

--- Comment #4 from Mauro Carvalho Chehab  ---
Created attachment 104033
  --> https://bugs.kde.org/attachment.cgi?id=104033=edit
Patch for Kernel 4.9 and upper to fix Siano driver

This is really a Kernel bug. The attached patch fix it for the Kernel. I'll
send it though the usual Kernel channels, hopefully in time for Kernel 4.10,
with should be released next week.

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

[kaffeine] [Bug 375811] Siano driver stopped working after upgrading to Kernel 4.9

[Mauro Carvalho Chehab]

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

Mauro Carvalho Chehab  changed:

   What|Removed |Added

Summary|how fix kaffeine for dvb-t  |Siano driver stopped
   |?!  |working after upgrading to
   ||Kernel 4.9

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

[krunner] [Bug 376483] Krunner Segmentation fault

[Rex Dieter]

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

--- Comment #3 from Rex Dieter  ---
No, that doesn't look like a crash, and is not a backtrace.

Ideally, you'd do:

gdb /usr/bin/krunner
...
(gdb) run
... then it crashes
(gdb) thread apply all backtrace

(then post the backtrace generated)

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

[krunner] [Bug 376483] Krunner Segmentation fault

[André Martins]

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

--- Comment #2 from André Martins  ---
(In reply to Kai Uwe Broulik from comment #1)
> Can you please run it through gdb.

[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib64/libthread_db.so.1".
[New Thread 0x7fffd972a700 (LWP 27660)]
[New Thread 0x7fffd3df5700 (LWP 27661)]
[Thread 0x7fffd3df5700 (LWP 27661) exited]
[Thread 0x77e17940 (LWP 27562) exited]
[Inferior 1 (process 27562) exited normally]
(gdb) [21272:21272:0214/190944.879540:ERROR:interface_registry.cc(210)] Failed
to locate a binder for interface: mojom::ResourceUsageReporter requested by: 
exposed by:  via InterfaceProviderSpec "service_manager:connector".

InterfaceRegistry(service_manager:connector):

  --> InterfaceRegistry is not yet bound to a pipe.

Does this helps?

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

[krita] [Bug 376487] New: Everything is slow

[bugzilla_noreply]

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

Bug ID: 376487
   Summary: Everything is slow
   Product: krita
   Version: 3.1.2
  Platform: unspecified
OS: unspecified
Status: UNCONFIRMED
  Severity: critical
  Priority: NOR
 Component: general
  Assignee: krita-bugs-n...@kde.org
  Reporter: hoangwave...@gmail.com
  Target Milestone: ---

Opening the program takes ages, and once it's open everything is crazy slow. I
know it's not my computer because all my other programs run fine. It's so slow
it took 5 minutes to create a canvas, and I can't see my cursor over the canvas
because it lags so much. Also it's constantly not responding, I just installed
it yesterday and it makes me want to just go back to Paint tool sai because I
don't have to wait a million years to make one brush stroke. It's very
frustrating!

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

[kdevelop] [Bug 376432] kdevelop is calling utimes() on a C/C++ file

[http://atom-symbol.net]

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

--- Comment #8 from Jan Ziak (http://atom-symbol.net) 
<0xe2.0x9a.0...@gmail.com> ---
(In reply to Kevin Funk from comment #6)
> Done. Unfortunately that won't really affect the probability this is getting
> fixed.
> 
> Stepping up & contributing a patch would increase probability a lot more ;)
> 
> See: https://www.kdevelop.org/contribute-kdevelop

The patch: https://phabricator.kde.org/D4612

Also: I have never heard of the "unsermake" alternative to make/gmake until I
examined kdevelop custommake source code. From internet search, it seems to be
an abandoned thing from year 2003. It may be beneficial to completely remove
unsermake support from kdevelop.

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

[krita] [Bug 376486] New: Audio out of sync with animation when scrubbing

[Diego]

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

Bug ID: 376486
   Summary: Audio out of sync with animation when scrubbing
   Product: krita
   Version: 3.1.2
  Platform: unspecified
OS: MS Windows
Status: UNCONFIRMED
  Severity: major
  Priority: NOR
 Component: Animation
  Assignee: krita-bugs-n...@kde.org
  Reporter: eggowaffles...@gmail.com
  Target Milestone: ---

Can't reliably sync animation with sound using krita's in program audio

tested with an audio file counting down 10 to 1 
Marked every 24th frame 10,9,8,7,6,5,4,3,2,1 repeated for 60 sec

around the 120 frame audio was starting to delay studder

Audio reached the end of the loop "3,2,1-10" between 312th and 336th frame 
14 second of animation for what should be 10 seconds of in program audio.

Rendering out the animation resulted in 60 sec and the correct timing of audio
and frames.

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

[digikam] [Bug 376213] Tag selection fails to find tagged photo's

[bugzilla_noreply]

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

--- Comment #10 from caulier.gil...@gmail.com ---
rbugman28,

Can we close this file now ?

Gilles Caulier

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

[systemsettings] [Bug 376484] [Regresion] SDDM-kcm action'Clear Image' is breaking the Breeze sddm theme configuration file

[Rog131]

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

--- Comment #2 from Rog131  ---
Thank you - that was quick.

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

[krunner] [Bug 376483] Krunner Segmentation fault

[Rex Dieter]

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

Rex Dieter  changed:

   What|Removed |Added

 CC||rdie...@math.unl.edu

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

[KScreen] [Bug 360058] Kscreen should check screen at wakeup from suspend

[Simone Gaiarin]

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

--- Comment #20 from Simone Gaiarin  ---
Ok. So I tried again today and I can find the process
/usr/lib/kf5/kscreen_backend_launcher, so yesterday probably it crashed.

Case 1:
In any case now I've tried this:
- Undock from work
- kill /usr/lib/kf5/kscreen_backend_launcher
- Remove all the kscreen bad configurations
- Run /usr/lib/kf5/kscreen_backend_launcher
- Dock the notebook at home

A this point the external monitor is not activated

Case 2:
If I do instead
- Undock from work
- Suspend
- Unsuspend
- Dock the notebook at home

the external monitor is activated but a bad configuration is generated.

If I do Case 1 with system settings 'display' dialog open, the notebook screen
become messed up and I cannot interact with anything.

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

[Spectacle] [Bug 358641] Have Spectacle remember filename

[Heiko Steindl]

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

Heiko Steindl  changed:

   What|Removed |Added

 CC||he...@steindl.com

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

[Spectacle] [Bug 361640] Option to default to JPG on save & exit

[Heiko Steindl]

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

Heiko Steindl  changed:

   What|Removed |Added

 CC||he...@steindl.com

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

[kgpg] [Bug 373910] kgpg crash when changing key trust

[Gábor Katona]

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

Gábor Katona  changed:

   What|Removed |Added

 CC||kato...@gmail.com

--- Comment #3 from Gábor Katona  ---
Kgpg 16.12.2 also has this problem on openSUSE Tumbleweed (Qt: 5.7.1,
frameworks: 5.30.0). 

The crash only occurs if setting Ultimate trust level. Any other level can be
set.

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

[kig] [Bug 376477] wrong owner "roor" for file install_manifest.txt after "make install"

[Christoph Feck]

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

--- Comment #1 from Christoph Feck  ---
Are you sure it is installed into source directory, not in the build directory?

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

[systemsettings] [Bug 376484] [Regresion] SDDM-kcm action'Clear Image' is breaking the Breeze sddm theme configuration file

[David Edmundson]

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

David Edmundson  changed:

   What|Removed |Added

  Latest Commit||https://commits.kde.org/sdd
   ||m-kcm/1c77df276e459e56b51e1
   ||a1e6accea3682b4033c
 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |FIXED

--- Comment #1 from David Edmundson  ---
Git commit 1c77df276e459e56b51e1a1e6accea3682b4033c by David Edmundson.
Committed on 14/02/2017 at 17:01.
Pushed by davidedmundson into branch 'Plasma/5.9'.

Check the background is valid when choosing background type

Summary:
I rushed in an emergency fix for 5.9.1 that added support for setting
the background type, which was a new property someone added to the
breeze theme in 5.9.1.

My last patch doesn't support clearing the background properly.
Effectively the old code would always set the type to "image".

Test Plan:
Set background to image. Checked config
Cleared background. Checked config

Reviewers: #plasma

Subscribers: plasma-devel

Tags: #plasma

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

M  +6-4src/themeconfig.cpp

https://commits.kde.org/sddm-kcm/1c77df276e459e56b51e1a1e6accea3682b4033c

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

[kwin] [Bug 376457] Revert wrapping in window swithing

[Yichao Yu]

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

--- Comment #6 from Yichao Yu  ---
Yet another acceptable solution would be to expose the new `switchWindow`
function in the KWin scripting interface (I thought it's possible to trigger
script with hotkey/add hotkey from a script?). I'm happy to implement and add
test with either methods though I'll need some help for how to add a test for
it.

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

[systemsettings] [Bug 376484] [Regresion] SDDM-kcm action'Clear Image' is breaking the Breeze sddm theme configuration file

[Dr . Chapatin]

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

Dr. Chapatin  changed:

   What|Removed |Added

 CC||yy...@gmx.com

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

[konsole] [Bug 233991] color remap xterm ANSI sequences not supported

[Egmont Koblinger]

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

Egmont Koblinger  changed:

   What|Removed |Added

 CC||egm...@gmail.com

--- Comment #7 from Egmont Koblinger  ---
OSC 4, 10 and 11 (and probably a few more in the 12-19 range for cursor and
highlight fg/bg, see
http://invisible-island.net/xterm/ctlseqs/ctlseqs.html#h2-Operating-System-Commands)
would be useful for xtermcontrol(1) to work, e.g. to be able to query the
default fg/bg colors. See also bug 336849. Note that these should be
implemented along with their 104, 110, 111 etc. counterparts that reset these
colors.

In VTE (gnome-terminal and friends) the implementation used to take escape
sequences (OSC 4, 10...) and API (user changing the palette in the prefs
dialog) equally. This led to confusions and unexpected behavior when e.g.
opening and closing the prefs (without changing anything) would overwrite the
effect of a previous OSC 4.

So we ended up fixing this (in version 0.36) by introducing two levels. For
each slot (256 for the palette of OSC 4, plus a few one-offs like default
foreground and background) there's the value set via API (e.g. prefs dialog)
which always contains a color, and there's the optional value set via OSC 4
(this can be undefined, and actually the OSC hundred's clear this). If the OSC
slot is defined for a particular color entry then that one is used, otherwise
we fallback to the API. In other words, escape sequences have precedence.

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

[kwin] [Bug 376457] Revert wrapping in window swithing

[Yichao Yu]

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

Yichao Yu  changed:

   What|Removed |Added

Summary|Provide an option to|Revert wrapping in window
   |disable wrapping in window  |swithing
   |swithing|

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

[konsole] [Bug 336849] Upon colorscheme changes, COLORFGBG is not modified in already running Konsole's tabs

[Egmont Koblinger]

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

--- Comment #6 from Egmont Koblinger  ---
... oh, and OSC 4 is about the palette colors only. The default
background/foreground are actually OSC 10 and 11 if I recall correctly. It's
pretty much the same story though.

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

[konsole] [Bug 336849] Upon colorscheme changes, COLORFGBG is not modified in already running Konsole's tabs

[Egmont Koblinger]

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

--- Comment #5 from Egmont Koblinger  ---
Lack of OSC 4 support is tracked in bug 233991.

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

[kwin] [Bug 376457] Revert wrapping in window swithing

[Yichao Yu]

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

--- Comment #5 from Yichao Yu  ---
Also, although I'm not that familiar with how the auto testing is done on X11,
it seems that this should be a relatively easy thing to test for both options
and should not be strongly coupled to other options so detecting breakage
should be possible.

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

[kwin] [Bug 376457] Revert wrapping in window swithing

[Yichao Yu]

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

Yichao Yu  changed:

   What|Removed |Added

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

--- Comment #4 from Yichao Yu  ---
In that case, consider this a request to revert the behavior since I don't
think the usability feedback considered the effect of keyboard autorepeating.

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

[konsole] [Bug 376462] konsole stops displaying output after too much

[Egmont Koblinger]

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

--- Comment #6 from Egmont Koblinger  ---
Yeah they do sound the same.

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

[konsole] [Bug 336849] Upon colorscheme changes, COLORFGBG is not modified in already running Konsole's tabs

[Egmont Koblinger]

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

--- Comment #4 from Egmont Koblinger  ---
Oops, you're right. I forgot that konsole doesn't support OSC 4.

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

[systemsettings] [Bug 370521] [Regresion] SDDM breeze theme unable to change backgound.

[Rog131]

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

--- Comment #12 from Rog131  ---
At here the
https://cgit.kde.org/sddm-kcm.git/commit/?id=19e83b28161783d570bde2ced692a8b5f2236693
is fixing the background change problem. But it is making a new bug:
https://bugs.kde.org/show_bug.cgi?id=376484

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