[plasmashell] [Bug 355953] Desktop on screens are switched on restart
https://bugs.kde.org/show_bug.cgi?id=355953 --- Comment #3 from Bernd Steinhauser --- Another interesting observation. Yesterday Plasma moved the panel, after disconnecting one screen. And it moved it onto the screen I just disconnected. Interestingly, when reconnecting, it wasn't moved back. I think that shouldn't happen. ;) -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 355777] Kate crashes when doing "Save" or "Save AS"
https://bugs.kde.org/show_bug.cgi?id=355777 --- Comment #4 from ole...@gmail.com --- Hi. I reported this bug(?) when running Linux Mint 17.2 The back trace is from Mint 17.3. However I did a clean reinstall (wiped my disk) and installed Linux Mint 17.3. And Kate still crashes. Kate is distributed in Mints default software repository. -- $ kate -version Qt: 4.8.6 KDE Development Platform: 4.14.2 Kate: 3.14.2 --- $ cat /etc/issue Linux Mint 17.3 Rosa \n \l -- $ cat /etc/os-release NAME="Ubuntu" VERSION="14.04.3 LTS, Trusty Tahr" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 14.04.3 LTS" VERSION_ID="14.04" HOME_URL="http://www.ubuntu.com/"; SUPPORT_URL="http://help.ubuntu.com/"; BUG_REPORT_URL="http://bugs.launchpad.net/ubuntu/"; -- -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 356844] Plasma 5 Wayland session doesn't start
https://bugs.kde.org/show_bug.cgi?id=356844 --- Comment #4 from Martin Gräßlin --- weston unlike kwin doesn't require Xwayland. If you start weston with xwayland support, Xwayland is only started on first X application. And yes, you can try running kwin manually. Either nested in an X session or from a tty: kwin_wayland --xwayland "application-to-start --args" -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 340489] All windows in KDE 5 starts glitching after some usage time
https://bugs.kde.org/show_bug.cgi?id=340489 xdmx changed: What|Removed |Added CC||x...@email.it --- Comment #34 from xdmx --- I'm experiencing this bug as well under Arch linux with all packages updated. I have an Intel video card with xf86-video-intel 1:2.99.917+478+gdf72bc5-3 -- You are receiving this mail because: You are watching all bug changes.
[klipper] [Bug 356837] One cannot clear history when first time is not confirmed
https://bugs.kde.org/show_bug.cgi?id=356837 --- Comment #4 from Martin Gräßlin --- > On confirmation window I checked "Don't ask again" That explains it. You selected don't ask again and no. So the automatic selection is to always apply no when clicking the button. I need to check where the config is stored. -- You are receiving this mail because: You are watching all bug changes.
[kscreensaver] [Bug 316348] kscreenlocker_greet constantly consumes around 20% CPU time
https://bugs.kde.org/show_bug.cgi?id=316348 --- Comment #23 from Martin Gräßlin --- I just locked the desktop, switched to another vt, run top and I couldn't even find kscreenlocker_greet in the list. Those experiencing the problem need to help us: please gdb into the process and get a backtrace, so that we can see where it consumes the CPU. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 356827] KWrite crashes when clicking "save as" on a blank file
https://bugs.kde.org/show_bug.cgi?id=356827 --- Comment #2 from emele...@gmail.com --- (In reply to Kåre Särs from comment #1) > Are you by chance using Compiz as window manager? No, I'm not. I'm using kwin -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 355093] Crash if I click on new mail
https://bugs.kde.org/show_bug.cgi?id=355093 Jan changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |CONFIRMED -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 354056] Deleted emails stay, but greyed out
https://bugs.kde.org/show_bug.cgi?id=354056 Jan changed: What|Removed |Added Priority|NOR |HI -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 352055] plasma-pa plasmoid not shown in systemtray after startup
https://bugs.kde.org/show_bug.cgi?id=352055 Brallan Aguilar changed: What|Removed |Added CC||apcomp...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 356846] Volume control icon not shown in system tray
https://bugs.kde.org/show_bug.cgi?id=356846 Brallan Aguilar changed: What|Removed |Added CC||apcomp...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 352256] Korganizer / Kontakt crash [EventViews::AgendaView::placeDecorations]
https://bugs.kde.org/show_bug.cgi?id=352256 Laurent Montel changed: What|Removed |Added CC||mon...@kde.org --- Comment #6 from Laurent Montel --- is it 5.1 ? master ? 4.14.x ? -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 346961] Multi Monitor configuration lost on reboot, must reconfigure after startup
https://bugs.kde.org/show_bug.cgi?id=346961 --- Comment #29 from Dmitry --- (In reply to gene smith from comment #28) > Well, guess I spoke too soon. Today the problem happened again on KDE > startup. Will try it set to run script on "Pre-KDE startup" for a while and > see if that makes a difference. You'right it should start as soon as possible. Also it's better to disable kscreen daemon in kde system settings / startup / services. -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 336228] pressing f12 (or the equivalent closekey) causes respawn of yakuake if mouse is in yakuake
https://bugs.kde.org/show_bug.cgi?id=336228 Egor Y. Egorov changed: What|Removed |Added CC||egorov_e...@bk.ru -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 351039] Show desktop requires two clicks
https://bugs.kde.org/show_bug.cgi?id=351039 Egor Y. Egorov changed: What|Removed |Added CC||egorov_e...@bk.ru -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 342638] Yakauke doesn't retract properly when you press F12
https://bugs.kde.org/show_bug.cgi?id=342638 Egor Y. Egorov changed: What|Removed |Added CC||egorov_e...@bk.ru -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 350826] plasma desktop containment seems to intermediately switch window type to normal when showing desktop
https://bugs.kde.org/show_bug.cgi?id=350826 Egor Y. Egorov changed: What|Removed |Added CC||egorov_e...@bk.ru -- You are receiving this mail because: You are watching all bug changes.
[klipper] [Bug 356837] One cannot clear history when first time is not confirmed
https://bugs.kde.org/show_bug.cgi?id=356837 --- Comment #3 from Piotr Mierzwinski --- And one more thing. On confirmation window I checked "Don't ask again". Without this checking "Clear history" button worked. After that stopped. I reproduced it on new working configuration. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 356843] Newly selected wallpaper is replaced with default one after use Alt+F2 and putting any letter in edit box
https://bugs.kde.org/show_bug.cgi?id=356843 --- Comment #9 from Piotr Mierzwinski --- Minor fix to my instruction. Of course should be: rm -rf .cache .kde .kde4 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 356843] Newly selected wallpaper is replaced with default one after use Alt+F2 and putting any letter in edit box
https://bugs.kde.org/show_bug.cgi?id=356843 --- Comment #8 from Piotr Mierzwinski --- And one more thing. When I killed both plasmashell procesess (first one was "stopped" one and after that nothing happened) and started again plasmashell (from konsole) then I got my changed desktop including wallpaper and plasmoids. -- You are receiving this mail because: You are watching all bug changes.
[drkonqi] [Bug 356822] Can not add similar issues
https://bugs.kde.org/show_bug.cgi?id=356822 sederic changed: What|Removed |Added CC||sebastian.end...@online.de --- Comment #2 from sederic --- Oh, yes, it seems to be related... But sometimes this feature works, I think... -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 356843] Newly selected wallpaper is replaced with default one after use Alt+F2 and putting any letter in edit box
https://bugs.kde.org/show_bug.cgi?id=356843 --- Comment #7 from Piotr Mierzwinski --- Replying to your question. There is no change. I can see on desktop only default empty wallpaper. I checked the list of processes after that - using Ctrl+Esc looking for plasmashell. After desktop was sliding to the right side (and as I got default wallpaper) I noticed that in the list of process I have two plasmashell processes. First one, looking on top (primary I guess), takes ~120MB (in other simplest test had 105MB) and in "Window Title" "Plazma" value. Second one (slipping I guess) has state "stopped" in "CPU" column and empty value in "Window Title". I think the numbers here not matter only saying that primary process takes more memory and is working. After that I was looking for the simplest test to reproduce this issue and I found one :). 1. Compositor must be on (I have it "on" from default, so I don't need to change nothing in configuration). Here I have default configuration (you can find in top post). Therefore my test I started from the second point. 2. Being on login screen switch to any text terminal and... Remove or rename cache and configuration directories rm .cashe .kde .kde4 mv .config .config.bak mv .local .local.bak 3. Log in to Plasma and set two virtual desktops 4. Change wallpaper (no matter which one, might be even first one) Note. Wallpaper window has default settings as following: Desktop, Picture, Scaled (sorry if the names doesn't match accurately I translate them from my local language) I have also installed couple additional wallpapers, but I'm not sure is it important here. 5. Invoke Alt+F2, and put "k" letter in edit box Result: wallpaper sliding including plasmoids if any there are placed on the desktop Using in this moment SHIFT+Alt+F12 nothing change. Even second "stopped" plasmashell process still exists on the processes list. Ah. OK. Only (bottom) panel a bit changes (there is no artefacts only it changes a bit its look). -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 348753] more issues with nvidia legacy (304.xxx) blob and explicit syncing (here on login)
https://bugs.kde.org/show_bug.cgi?id=348753 summersons96-squarefor...@yahoo.ie changed: What|Removed |Added CC||summersons96-squareformat@y ||ahoo.ie --- Comment #47 from summersons96-squarefor...@yahoo.ie --- (In reply to Jordyn Carattini from comment #33) > Created attachment 93237 [details] > KWin Problem's Fix Bash Script Where can this file be placed? Previously I used /etc/profile.d to place a simple kwin.sh script. Is there a preferred path for this file of yours? Thanking for your efforts -- You are receiving this mail because: You are watching all bug changes.
[kmines] [Bug 356811] Kmines number indicators are incorrect.
https://bugs.kde.org/show_bug.cgi?id=356811 --- Comment #5 from Alex Zaballa --- I guess I may be understanding the game wrong. Isn't the mine with the X over it, still a mine? If not, then delete this entire report. If so, then the numbers directly below should read as '332' not '221'. This is what I get for being bored quite honestly. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 356791] KDE Applications won't show contents of nfs mount (automount)
https://bugs.kde.org/show_bug.cgi?id=356791 Rex Dieter changed: What|Removed |Added CC||rdie...@math.unl.edu -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356856] New: plasmashell crashes after double click on klipboard icon
https://bugs.kde.org/show_bug.cgi?id=356856 Bug ID: 356856 Summary: plasmashell crashes after double click on klipboard icon Product: plasmashell Version: 5.5.1 Platform: Mageia RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: piotr.mierzwin...@gmail.com CC: bhus...@gmail.com, plasma-b...@kde.org Application: plasmashell (5.5.1) Qt Version: 5.5.1 Operating System: Linux 4.3.2-desktop-2.mga6 x86_64 Distribution: "Mageia 6" -- Information about the crash: - What I was doing when the application crashed: plasmashell crashes after double click on klipboard icon. When I try to reproduce this nothing bad happened. Before double click I have in clipboard only one text entry, which was entered to the clipboard by clickng double in string (become highlighted) in Opera browser. -- Backtrace: Application: Plazma (plasmashell), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7fca2274f800 (LWP 10954))] Thread 7 (Thread 0x7fca0dfb0700 (LWP 10958)): #0 0x7fca1ce8bdbd in poll () at /lib64/libc.so.6 #1 0x7fca20f14ac2 in _xcb_conn_wait () at /lib64/libxcb.so.1 #2 0x7fca20f16697 in xcb_wait_for_event () at /lib64/libxcb.so.1 #3 0x7fca100d7cc9 in QXcbEventReader::run() () at /lib64/libQt5XcbQpa.so.5 #4 0x7fca1d57601f in QThreadPrivate::start(void*) () at /lib64/libQt5Core.so.5 #5 0x7fca1c68865d in start_thread () at /lib64/libpthread.so.0 #6 0x7fca1ce97bfd in clone () at /lib64/libc.so.6 Thread 6 (Thread 0x7fca075ef700 (LWP 10971)): #0 0x7fca1ce876dd in read () at /lib64/libc.so.6 #1 0x7fca1a1367d0 in g_wakeup_acknowledge () at /lib64/libglib-2.0.so.0 #2 0x7fca1a0f3f64 in g_main_context_check () at /lib64/libglib-2.0.so.0 #3 0x7fca1a0f43d8 in g_main_context_iterate.isra () at /lib64/libglib-2.0.so.0 #4 0x7fca1a0f453c in g_main_context_iteration () at /lib64/libglib-2.0.so.0 #5 0x7fca1d79992b in QEventDispatcherGlib::processEvents(QFlags) () at /lib64/libQt5Core.so.5 #6 0x7fca1d74380a in QEventLoop::exec(QFlags) () at /lib64/libQt5Core.so.5 #7 0x7fca1d5711bc in QThread::exec() () at /lib64/libQt5Core.so.5 #8 0x7fca1fdfdcd5 in QQmlThreadPrivate::run() () at /lib64/libQt5Qml.so.5 #9 0x7fca1d57601f in QThreadPrivate::start(void*) () at /lib64/libQt5Core.so.5 #10 0x7fca1c68865d in start_thread () at /lib64/libpthread.so.0 #11 0x7fca1ce97bfd in clone () at /lib64/libc.so.6 Thread 5 (Thread 0x7fc9fed8d700 (LWP 11013)): #0 0x7fca1ce8bdbd in poll () at /lib64/libc.so.6 #1 0x7fca1a0f4434 in g_main_context_iterate.isra () at /lib64/libglib-2.0.so.0 #2 0x7fca1a0f453c in g_main_context_iteration () at /lib64/libglib-2.0.so.0 #3 0x7fca1d79992b in QEventDispatcherGlib::processEvents(QFlags) () at /lib64/libQt5Core.so.5 #4 0x7fca1d74380a in QEventLoop::exec(QFlags) () at /lib64/libQt5Core.so.5 #5 0x7fca1d5711bc in QThread::exec() () at /lib64/libQt5Core.so.5 #6 0x7fca1fdfdcd5 in QQmlThreadPrivate::run() () at /lib64/libQt5Qml.so.5 #7 0x7fca1d57601f in QThreadPrivate::start(void*) () at /lib64/libQt5Core.so.5 #8 0x7fca1c68865d in start_thread () at /lib64/libpthread.so.0 #9 0x7fca1ce97bfd in clone () at /lib64/libc.so.6 Thread 4 (Thread 0x7fc9fd62f700 (LWP 11018)): #0 0x7fca1a137ab4 in g_mutex_unlock () at /lib64/libglib-2.0.so.0 #1 0x7fca1a0f43ee in g_main_context_iterate.isra () at /lib64/libglib-2.0.so.0 #2 0x7fca1a0f453c in g_main_context_iteration () at /lib64/libglib-2.0.so.0 #3 0x7fca1d79992b in QEventDispatcherGlib::processEvents(QFlags) () at /lib64/libQt5Core.so.5 #4 0x7fca1d74380a in QEventLoop::exec(QFlags) () at /lib64/libQt5Core.so.5 #5 0x7fca1d5711bc in QThread::exec() () at /lib64/libQt5Core.so.5 #6 0x7fca1fdfdcd5 in QQmlThreadPrivate::run() () at /lib64/libQt5Qml.so.5 #7 0x7fca1d57601f in QThreadPrivate::start(void*) () at /lib64/libQt5Core.so.5 #8 0x7fca1c68865d in start_thread () at /lib64/libpthread.so.0 #9 0x7fca1ce97bfd in clone () at /lib64/libc.so.6 Thread 3 (Thread 0x7fc9f75c6700 (LWP 11039)): #0 0x7fca1c68dc3f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fca22190fd4 in QTWTF::TCMalloc_PageHeap::scavengerThread() () at /lib64/libQt5Script.so.5 #2 0x7fca22191019 in () at /lib64/libQt5Script.so.5 #3 0x7fca1c68865d in start_thread () at /lib64/libpthread.so.0 #4 0x7fca1ce97bfd in clone () at /lib64/libc.so.6 Thread 2 (Thread 0x7fc9f4ae3700 (LWP 11040)): #0 0x7fca1ce8bdbd in poll () at /lib64/libc.so.6 #1 0x7fca1a0f4434 in g_main_context_iterate.isra () at /lib64/libglib-2.0.so.0 #2 0x7fca1a0f453c in g_main_context_i
[amarok] [Bug 356855] New: Crash in scriptengine (MetaTypeExporter)
https://bugs.kde.org/show_bug.cgi?id=356855 Bug ID: 356855 Summary: Crash in scriptengine (MetaTypeExporter) Product: amarok Version: 2.8.90 (2.9 beta) Platform: Gentoo Packages OS: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: Tools/Script Manager Assignee: amarok-bugs-d...@kde.org Reporter: wielkie...@gmail.com CC: darthco...@gmail.com Hello, In amarok 2.8 beta, I have found a problem with the MetaTrackPrototype class after investigating a SIGSEGV due to one of the custom amarok scripts I use (to be more precise it's amarokontrol). Since my understanding of amarok codebase as well as my time is limited, I wanted to just point out an obvious mistake without any patch that could fix it. The mentioned class has a private QScriptEngine* m_engine field. However, it is never assigned. It is then read in imagePixmap() method and then the SIGSEGV occurs. The problem doesn't occur in amarok 2.8, but if I understand correctly this class has been introduced after 2.8. Reproducible: Always Steps to Reproduce: 1. Install amarokontrol script (http://kde-apps.org/content/show.php?content=161189) along with an associated android client application 2. Configure the android application 3. Poke inside the android application, change the song a few times, etc. Actual Results: Crash in AmarokScript::MetaTrackPrototype::imagePixmap(). Expected Results: No crash More complete backtrace: (gdb) bt #0 QScriptEngine::create (this=0x40, type=type@entry=70, ptr=ptr@entry=0x7ffd4b680480) at /var/tmp/portage/dev-qt/qtscript-4.8.7/work/qt-everywhere-opensource-src-4.8.7/src/script/api/qscriptengine.cpp:3000 #1 0x7fe67ef58166 in qScriptValueFromValue_helper (ptr=0x7ffd4b680480, type=70, engine=) at /usr/include/qt4/QtScript/qscriptengine.h:323 #2 qScriptValueFromValue (t=..., engine=) at /usr/include/qt4/QtScript/qscriptengine.h:329 #3 QScriptEngine::toScriptValue (value=..., this=) at /usr/include/qt4/QtScript/qscriptengine.h:215 #4 AmarokScript::MetaTrackPrototype::imagePixmap (this=this@entry=0x41e9aa0, size=1) at /var/tmp/portage/media-sound/amarok-2.8.90/work/amarok-2.8.90/src/scripting/scriptengine/exporters/MetaTypeExporter.cpp:267 #5 0x7fe67ef583f6 in AmarokScript::MetaTrackPrototype::qt_static_metacall (_o=_o@entry=0x41e9aa0, _id=_id@entry=2, _a=_a@entry=0x7ffd4b680ba0, _c=QMetaObject::InvokeMetaMethod) at /var/tmp/portage/media-sound/amarok-2.8.90/work/amarok-2.8.90_build/src/MetaTypeExporter.moc:101 #6 0x7fe67ef586e3 in AmarokScript::MetaTrackPrototype::qt_static_metacall (_a=0x7ffd4b680ba0, _id=2, _c=QMetaObject::InvokeMetaMethod, _o=0x41e9aa0) at /var/tmp/portage/media-sound/amarok-2.8.90/work/amarok-2.8.90_build/src/MetaTypeExporter.moc:144 #7 AmarokScript::MetaTrackPrototype::qt_metacall (this=0x41e9aa0, _c=QMetaObject::InvokeMetaMethod, _id=2, _a=0x7ffd4b680ba0) at /var/tmp/portage/media-sound/amarok-2.8.90/work/amarok-2.8.90_build/src/MetaTypeExporter.moc:145 #8 0x7fe67b22a63d in QScript::callQtMethod (exec=0x7fe5dcd401f0, callType=QMetaMethod::Method, thisQObject=0x41e9aa0, scriptArgs=..., meta=0x7fe67f421940 , initialIndex=6, maybeOverloaded=true) at /var/tmp/portage/dev-qt/qtscript-4.8.7/work/qt-everywhere-opensource-src-4.8.7/src/script/bridge/qscriptqobject.cpp:960 #9 0x7fe67b22b8d7 in QScript::QtFunction::execute (this=0x7ffd4b6804e0, this@entry=0x7fe5dc9bf000, exec=0x40, thisValue=..., thisValue@entry=..., scriptArgs=...) at /var/tmp/portage/dev-qt/qtscript-4.8.7/work/qt-everywhere-opensource-src-4.8.7/src/script/bridge/qscriptqobject.cpp:1015 #10 0x7fe67b22baea in QScript::QtFunction::call (exec=0x7fe5dcd401f0, callee=0x7fe5dc9bf000, thisValue=..., args=...) at /var/tmp/portage/dev-qt/qtscript-4.8.7/work/qt-everywhere-opensource-src-4.8.7/src/script/bridge/qscriptqobject.cpp:1030 #11 0x7fe67b12a648 in QTJSC::NativeFuncWrapper::operator() (this=this@entry=0x7ffd4b680db0, exec=0x7fe5dcd401f0, jsobj=jsobj@entry=0x7fe5dc9bf000, thisValue=..., argList=...) at /var/tmp/portage/dev-qt/qtscript-4.8.7/work/qt-everywhere-opensource-src-4.8.7/src/3rdparty/javascriptcore/JavaScriptCore/runtime/CallData.cpp:46 #12 0x7fe67b105790 in QTJSC::cti_op_call_NotJSFunction (args=0x7ffd4b680e00) at /var/tmp/portage/dev-qt/qtscript-4.8.7/work/qt-everywhere-opensource-src-4.8.7/src/3rdparty/javascriptcore/JavaScriptCore/jit/JITStubs.cpp:1780 #13 0x7fe55803c516 in ?? () #14 0x00f6 in ?? () #15 0x7fe5dc9bf000 in ?? () #16 0x7fe6000f in ?? () #17 0x0001 in ?? () #18 0x7fe50003 in ?? () #19 0x7ffd0010 in ?? () #20 0x0010 in ?? () #21 0x7fe67d438b1f in QAbstractItemView::update (this=, index=...) at /var/tmp/portage/dev-qt/qtgui-4.8.7/work/qt-everywhere-opensource-src-4.8.7/src/gui/itemviews/qabstractitemview.cpp:3167 #22 0x0
[systemsettings] [Bug 356444] Fonts on the rigth side of the font manager appear without smoothed edges
https://bugs.kde.org/show_bug.cgi?id=356444 --- Comment #2 from slartibar...@gmail.com --- Also happens on a laptop with (older) amd graphics without additional amd drivers. I suspect the xrender engine being responsible for the problem? -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 334019] Okular should warn if closing with multiple tabs opened
https://bugs.kde.org/show_bug.cgi?id=334019 --- Comment #13 from torham...@yahoo.com --- I added it to reviewboard before adding it here. I apologize, is this KDE bug tracking website deprecated? I've seen the use of both such type websites before, and that was how I saw them used - make sure a copy is in both places. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 346165] OSX: No pen pressure when OpenGL is turned off
https://bugs.kde.org/show_bug.cgi?id=346165 Callum Gare changed: What|Removed |Added CC||cal...@gare.com.au --- Comment #8 from Callum Gare --- MacBook Pro (Retina, 13-inch, Mid 2013), OS X 10.10.5, Kirta 2.9.9, Wacom Intus Pen & Touch. I also get the same issue when testing on my friends computer which is a MacBook Air (13-inch, late 2015) (all other details same as above). Initially turning openGL on and off was not enough to get pressure to work but after I also right clicked a bit, just toggling openGL on and off started getting pressure to work. Once working it will stop working when the application is closed and reopened or when the master pressure control is edited (probably other situations too, their just the ways I've noticed it). It appears pressure sensitivity works for me IN openGL mode but unfortunately openGL doesn't work properly (it will display changes in the layer previews but not the canvas for example). I'm surprised this doesn't seem to be effecting more uses. I don't have a partially strange setup and it's all pretty new. Cheers :) -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 334019] Okular should warn if closing with multiple tabs opened
https://bugs.kde.org/show_bug.cgi?id=334019 --- Comment #12 from Albert Astals Cid --- What do you not understand of "Please use reviewboard.kde.org for the patch"? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 343674] Plasma is brought down by libqxcb segfaults with the screen locked & switched off
https://bugs.kde.org/show_bug.cgi?id=343674 bj.car...@gmail.com changed: What|Removed |Added CC||bj.car...@gmail.com --- Comment #17 from bj.car...@gmail.com --- God almighty diabelko! You solved my problem. I am.seeing this very frequently, especially when plugging and unplugging screens across reboots on an Optimus laptop. The last time it got stuck like this I just reinstalled from.scratch but it was definitely one of the profiles in kscreen that was messing everything up. For reference, I saw the same kscreen segfaults mentioned above. Following which sddm would dump to a black screen. It seems easily reproducible on my laptop if I boot with a DisplatPort device attached and then detach it and plug in HDMI. Both plugs go to the same screen so it is possible it somehow gets confused by the EDID info that comes back or something. -- You are receiving this mail because: You are watching all bug changes.
[kdesrc-build] [Bug 356788] README in git sources v15.10-16-gdb8826f starts out with factual errors
https://bugs.kde.org/show_bug.cgi?id=356788 Michael Pyne changed: What|Removed |Added Version Fixed In||15.12 Status|UNCONFIRMED |RESOLVED Latest Commit||http://commits.kde.org/kdes ||rc-build/68a5b27f4bfe25aff5 ||ecf0b23ffb0ec0d5160197 Resolution|--- |FIXED --- Comment #3 from Michael Pyne --- Git commit 68a5b27f4bfe25aff5ecf0b23ffb0ec0d5160197 by Michael Pyne. Committed on 17/12/2015 at 22:58. Pushed by mpyne into branch 'master'. Update README to be more clear about the install directory. FIXED-IN:15.12 M +3-3README http://commits.kde.org/kdesrc-build/68a5b27f4bfe25aff5ecf0b23ffb0ec0d5160197 -- You are receiving this mail because: You are watching all bug changes.
[kdesrc-build] [Bug 356788] README in git sources v15.10-16-gdb8826f starts out with factual errors
https://bugs.kde.org/show_bug.cgi?id=356788 --- Comment #2 from Michael Pyne --- The "kdesrc-build directory" is where you cloned kdesrc-build.git to. For any future kdesrc-build tarball releases, the "kdesrc-build directory" would be the directory holding the extracted tarball contents. I will try to make the wording more clear. -- You are receiving this mail because: You are watching all bug changes.
[amarok] [Bug 356798] Crashes when adding directory with large number of entries
https://bugs.kde.org/show_bug.cgi?id=356798 Myriam Schweingruber changed: What|Removed |Added CC||123k...@gmail.com Component|general |Metadata Editing and ||Reading Status|UNCONFIRMED |RESOLVED Resolution|--- |DUPLICATE --- Comment #1 from Myriam Schweingruber --- *** This bug has been marked as a duplicate of bug 345535 *** -- You are receiving this mail because: You are watching all bug changes.
[amarok] [Bug 345535] crash when I add any music to playlist
https://bugs.kde.org/show_bug.cgi?id=345535 Myriam Schweingruber changed: What|Removed |Added CC||trburkhol...@gmail.com --- Comment #10 from Myriam Schweingruber --- *** Bug 356798 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[simon] [Bug 351279] Simon can't build against OpenCV 3 because of wrong include headers
https://bugs.kde.org/show_bug.cgi?id=351279 --- Comment #4 from andreas.sturmlech...@gmail.com --- FIY, git master builds fine because of the following commit: https://quickgit.kde.org/?p=simon.git&a=commit&h=b4e663e5cc36511b15ef20865c723182cd3d88c9 -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 346961] Multi Monitor configuration lost on reboot, must reconfigure after startup
https://bugs.kde.org/show_bug.cgi?id=346961 Arthur c changed: What|Removed |Added CC|clement.art...@gmail.com| -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 346961] Multi Monitor configuration lost on reboot, must reconfigure after startup
https://bugs.kde.org/show_bug.cgi?id=346961 --- Comment #28 from gene smith --- (In reply to gene smith from comment #27) > (In reply to Dmitry from comment #25) > > The most reliable solution at this moment is to create an .sh script like > > this: > > $ cat ~/bin/display.sh > > #!/bin/bash > > xrandr --output HDMI1 --primary --auto --pos 0x265 --output VGA1 --auto > > --rotation left --pos 1920x0 > > And place it to autostart. > > Thanks. Putting this in autostart does seem to "fix" the problem. After > restarting several times over a few days I haven't had a problem with both > monitors coming up correctly. Well, guess I spoke too soon. Today the problem happened again on KDE startup. Will try it set to run script on "Pre-KDE startup" for a while and see if that makes a difference. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356854] New: Tray Icons don't follow user settings customization
https://bugs.kde.org/show_bug.cgi?id=356854 Bug ID: 356854 Summary: Tray Icons don't follow user settings customization Product: plasmashell Version: master Platform: Debian unstable OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: System Tray Assignee: plasma-b...@kde.org Reporter: gotokrik...@gmail.com If I go inside the settings of the system tray and manually set the icons I want to be loaded (network; Battery; volume; printers) and the one I don't, the settings are not saved and I can only see the kdeaccessible applet (that I deactivated) and the one about the notes. Reproducible: Always Steps to Reproduce: 1.Try to change the behavior with the settings of the tray 2.I select the elements I want to be on the tray 3.I save the settings Actual Results: Nothing, the system does not care about the settings and shows always the same icons. Expected Results: That the system does what I would like to do. -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 356853] New: Wrong split is focused when showing/hiding the terminal.
https://bugs.kde.org/show_bug.cgi?id=356853 Bug ID: 356853 Summary: Wrong split is focused when showing/hiding the terminal. Product: yakuake Version: 2.9.9 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: h...@kde.org Reporter: d.misdani...@gmail.com Having more than one split, if the terminal is shown/hidden a few times (sometimes as little as one time) the wrong split is focused, i.e. not the one that was focused before hiding the terminal. Reproducible: Always Steps to Reproduce: 1. Split terminal into at least 2 terminals, and notice which terminal is currently focused 2. Show/Hide yakuake a few times 3. After a few tries (anywhere between 2-7) focus will change to a random split Actual Results: A split other than the lastly focused split gained focus. Expected Results: The focus should remain on the split lastly focused. -- You are receiving this mail because: You are watching all bug changes.
[kdepim] [Bug 356093] Kmail does not display PGP/Inline signed mails
https://bugs.kde.org/show_bug.cgi?id=356093 Marcus Behrendt changed: What|Removed |Added Component|general |general Version|Git (master)|GIT (master) Product|kmail2 |kdepim -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 356786] KWrite crashes attempting Open, from menu or toolbar.
https://bugs.kde.org/show_bug.cgi?id=356786 --- Comment #4 from aschm...@graphtek.com --- There was a large swath up updates to kde files in F23 this morning. Lo, opening from the toolbar has worked for me twice with compositing on (having it work with compositing off worked before the update). One of the packages updated was indeed kwrite (qt5-qtbase-gui was not updated -- alas, "dnf history info last" gives me nothing, since I was stupid and allowed packagekit to do the update, and my ability to read the backtrace is limited as far as what to look at as a likely failure candidate). -- You are receiving this mail because: You are watching all bug changes.
[Baloo] [Bug 356601] Baloo does not index new files
https://bugs.kde.org/show_bug.cgi?id=356601 --- Comment #9 from hotmusic...@mail.bg --- OK, why should I do that? Isn't /Desktop a subdirectory of /home? And doesn't Baloo monitor just everything? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356660] Notification pop-up from left side sometimes
https://bugs.kde.org/show_bug.cgi?id=356660 --- Comment #7 from Martin Klapetek --- I've made a refactor of the internals that should fix this for good. Patch up at https://git.reviewboard.kde.org/r/126408/ if anybody wants to give it a try. That would help a lot if someone else could test it. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356461] Notification Settings wrong default display for notifications and notifaction position.
https://bugs.kde.org/show_bug.cgi?id=356461 --- Comment #29 from Martin Klapetek --- Patch up at https://git.reviewboard.kde.org/r/126408/ if anybody wants to give it a try. That would help a lot if someone else could test it. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 356786] KWrite crashes attempting Open, from menu or toolbar.
https://bugs.kde.org/show_bug.cgi?id=356786 Gérald Hameau changed: What|Removed |Added CC||gerald.ham...@gmail.com --- Comment #3 from Gérald Hameau --- I have this crash, and more. They always involve file dialog. kwrite or kate : - open = crash - save as = crash. With or without content. I can open file through dolphin, and then save them, with both applications (eg: click on a file in dolphin, and open it with kwrite or kate... or use a previous kate session). fedora 22, with recent kde 5.5.0 update. Both kf5 5.16 & 5.17 window manager = kwin compositor = opengl 2.0, or 3.1, glx, on intel chipset (laptop, with nvidia secondary chip. Not active) -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 356852] New: Kate's printing schema prints white on white when Breeze Dark color setting is selected
https://bugs.kde.org/show_bug.cgi?id=356852 Bug ID: 356852 Summary: Kate's printing schema prints white on white when Breeze Dark color setting is selected Product: kate Version: unspecified Platform: Ubuntu Packages URL: https://i.imgur.com/agefT3J.png OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: kwrite Assignee: kwrite-bugs-n...@kde.org Reporter: david.lesicn...@gmail.com I set the "Color" setting in the System Settings to Breeze Dark, launched Kate, wrote some text. Then I selected to print that file to PDF (made sure that the "Printing" schema was selected) and the output was near-white on white. If I switch the Color setting back to normal Breeze Kate prints black on white normally. Reproducible: Always Steps to Reproduce: 1. Switch to Breeze Dark color option 2. Write some text in Kate 3. Print said text (to PDF, for example) Actual Results: The output PDF contained near-white on white text, which was completely unreadable Expected Results: The output PDF cointained black on white, as defined in the "Printing" schema Even if I switch to the Printing schema in Kate itself while Breeze Dark is enable, it's displayed black on white (as show in the URL demonstration), so it makes me think that the printing thing doesn't "respect" the Printing schema's black normal text. -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 356831] cannot send image to clipboard in background mode
https://bugs.kde.org/show_bug.cgi?id=356831 Boudhayan Gupta changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |WONTFIX --- Comment #1 from Boudhayan Gupta --- It turns out the clipboard loses its content if the application closes down, making this feature impossible in background mode. I must have forgotten to remove the clipboard option from the final release - I'll do that in the next point release. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 334019] Okular should warn if closing with multiple tabs opened
https://bugs.kde.org/show_bug.cgi?id=334019 --- Comment #11 from torham...@yahoo.com --- Created attachment 96157 --> https://bugs.kde.org/attachment.cgi?id=96157&action=edit Git diff -- You are receiving this mail because: You are watching all bug changes.
[drkonqi] [Bug 356822] Can not add similar issues
https://bugs.kde.org/show_bug.cgi?id=356822 opensuse.lietuviu.ka...@gmail.com changed: What|Removed |Added CC||opensuse.lietuviu.kalba@gma ||il.com --- Comment #1 from opensuse.lietuviu.ka...@gmail.com --- Seems very related to https://bugs.kde.org/show_bug.cgi?id=356722 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 356851] New: System keyboard layout ctrl capslock requires re-apply after log out
https://bugs.kde.org/show_bug.cgi?id=356851 Bug ID: 356851 Summary: System keyboard layout ctrl capslock requires re-apply after log out Product: systemsettings Version: 5.5.0 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: kcm_keyboard Assignee: ary...@gmail.com Reporter: torys.ander...@gmail.com Using an external keyboard on my laptop, Configure Desktop -> Hardware -> Input Devices -> Keyboard -> Advanced -> Caps Lock key behavior -> Make Caps Lock an additional CTRL is enabled. The setting is remembered insomuch as it retains the check mark from log-in to log-in, but each log-in it will not, in actuality, be working until I uncheck, check, "Apply". Also needs to be applied again whenever the system has returned to log-in screen due to inactivity. Possibly related to bug 353413, which deals with remembering settings and fixing by re-applying. Reproducible: Always Steps to Reproduce: 1. plug in external keyboard 2. Check Keyboard -> Advanced -> Caps Lock key behavior -> Make Caps Lock an additional CTRL, apply 3. Log out, log back in Actual Results: Keyboard -> Advanced -> Caps Lock key behavior -> Make Caps Lock an additional CTRL will show as selected, but behavior does not agree. Expected Results: Capslock should remain an additional ctrl. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356839] plasma 5 doesn't start on very old PCs who have a graphic card who supports only openGL 1.3
https://bugs.kde.org/show_bug.cgi?id=356839 opensuse.lietuviu.ka...@gmail.com changed: What|Removed |Added CC||opensuse.lietuviu.kalba@gma ||il.com --- Comment #1 from opensuse.lietuviu.ka...@gmail.com --- This is known: KDE Plasma 5 needs OpenGL 2. Try use Software accelerator instead of hardware: echo 'QT_XCB_FORCE_SOFTWARE_OPENGL=1' > ~/.bashrc echo 'LIBGL_ALWAYS_SOFTWARE="true"' > ~/.bashrc This will add two line in /home/[username]/.bashrc : QT_XCB_FORCE_SOFTWARE_OPENGL=1 LIBGL_ALWAYS_SOFTWARE="true" Or you can create /etc/xdg/plasma-workspace/env/plasma-Qt5-OpenGL2.sh file with content (and make this file executable): #!/bin/sh OPENGL_VERSION=`LANG=C glxinfo | grep '^OpenGL version string: ' | head -n 1 | sed -e 's/^OpenGL version string: \([0-9]\).*$/\1/g'` if [ "$OPENGL_VERSION" -lt 2 ]; then QT_XCB_FORCE_SOFTWARE_OPENGL=1 export QT_XCB_FORCE_SOFTWARE_OPENGL fi -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 353413] New keyboard shortcuts aren't active until you toggle them off and on, even after restart
https://bugs.kde.org/show_bug.cgi?id=353413 torys.ander...@gmail.com changed: What|Removed |Added CC||torys.ander...@gmail.com --- Comment #1 from torys.ander...@gmail.com --- I can confirm this. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 356846] Volume control icon not shown in system tray
https://bugs.kde.org/show_bug.cgi?id=356846 opensuse.lietuviu.ka...@gmail.com changed: What|Removed |Added CC||opensuse.lietuviu.kalba@gma ||il.com --- Comment #1 from opensuse.lietuviu.ka...@gmail.com --- See https://bugs.kde.org/show_bug.cgi?id=352055 , https://bugreports.qt.io/browse/QTBUG-48870 and http://lists.opensuse.org/opensuse-factory/2015-12/msg00133.html -- You are receiving this mail because: You are watching all bug changes.
[kmines] [Bug 356811] Kmines number indicators are incorrect.
https://bugs.kde.org/show_bug.cgi?id=356811 --- Comment #4 from Frederik Schwarzer --- Created attachment 96156 --> https://bugs.kde.org/attachment.cgi?id=96156&action=edit With marked assignments. -- You are receiving this mail because: You are watching all bug changes.
[kmines] [Bug 356811] Kmines number indicators are incorrect.
https://bugs.kde.org/show_bug.cgi?id=356811 --- Comment #3 from Frederik Schwarzer --- Thanks. External links might disappear. As for the issue, I am not sure I understand the problem. I took your image and marked all assignments in the upper left. All seems fine. I am not a kmines expert but from what I see it was not possible to clearly say if the mine there was under the field on the left or the right. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356850] KDEVARTMP environment variable is ignored after upgrade from KDE 4 to 5
https://bugs.kde.org/show_bug.cgi?id=356850 Daniel Boles changed: What|Removed |Added Keywords||regression, usability -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356850] KDEVARTMP environment variable is ignored after upgrade from KDE 4 to 5
https://bugs.kde.org/show_bug.cgi?id=356850 --- Comment #1 from Daniel Boles --- Created attachment 96155 --> https://bugs.kde.org/attachment.cgi?id=96155&action=edit ~/.config/plasma-workspace/env/kwin_env.sh (formerly in ~/.kde/env/) This is the script that gets run, exports the KDEVARTMP file, but does not have the previous/desired effect. chmod permissions are 755 and it's executable. /tmp is mounted as a tmpfs in RAM and previously worked fine as the path for KDEVARTMP stuff (kde-cache etc) in v4 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356850] New: KDEVARTMP environment variable is ignored after upgrade from KDE 4 to 5
https://bugs.kde.org/show_bug.cgi?id=356850 Bug ID: 356850 Summary: KDEVARTMP environment variable is ignored after upgrade from KDE 4 to 5 Product: plasmashell Version: 5.4.3 Platform: Debian testing OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: db0...@gmail.com CC: bhus...@gmail.com, plasma-b...@kde.org I previously used a .sh file in ~/.kde/env to mkdir a folder in my /tmp ramdrive and set KDEVARTMP to that folder. This resulted in KDE caching everything in RAM and seemed to have no ill effects. I have since upgraded from KDE 4 to 5, moved the .sh script to the new corresponding location - ~/.config/plasma-workspace/env - and noticed that although it is executed and the environment variable set, that variable is seemingly no longer used. KDE continues to use its default path in /var/tmp Is this intentional and the documentation outdated, or has KDEVARTMP been deprecated, or is something else stopping this from working with the folder I designate? Thanks in advance. Reproducible: Always Steps to Reproduce: 1. export KDEVARTMP from a startup env script, e.g. as /tmp/KDEVARTMP (prefaced by the required mkdir so this folder exists in advance) Actual Results: 2. KDEVARTMP is set 3. It does not have the documented effect, i.e. changing kdecache-* directories to be placed in the KDEVARTMP path Expected Results: 3. kde-cache-* et al should be placed in the KDEVARTMP path as claimed in the documentation -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 332897] [regression] cannot send to distribution list
https://bugs.kde.org/show_bug.cgi?id=332897 Cyril Brosch changed: What|Removed |Added CC||i...@cyrilbrosch.net --- Comment #10 from Cyril Brosch --- In KMail 5.0.3, Frameworks 5.16.0, it does not work. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 356380] Regression on breeze dark theme in 5.17.0
https://bugs.kde.org/show_bug.cgi?id=356380 Sudhir Khanger changed: What|Removed |Added CC||sud...@sudhirkhanger.com -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 356849] ownCloud Icon is hardly visible when using breeze dark-desktop and light-icon theme
https://bugs.kde.org/show_bug.cgi?id=356849 --- Comment #1 from Sudhir Khanger --- Created attachment 96154 --> https://bugs.kde.org/attachment.cgi?id=96154&action=edit screenshot of hardly visible ownCloud icon -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 356849] ownCloud Icon is hardly visible when using breeze dark-desktop and light-icon theme
https://bugs.kde.org/show_bug.cgi?id=356849 Sudhir Khanger changed: What|Removed |Added Platform|Other |Fedora RPMs -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 356849] New: ownCloud Icon is hardly visible when using breeze dark-desktop and light-icon theme
https://bugs.kde.org/show_bug.cgi?id=356849 Bug ID: 356849 Summary: ownCloud Icon is hardly visible when using breeze dark-desktop and light-icon theme Product: Breeze Version: 5.5.0 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Icons Assignee: uri_herr...@nitrux.in Reporter: sud...@sudhirkhanger.com CC: kain...@gmail.com I am using Breeze Dark desktop theme and Breeze light icon theme. ownCloud icon is hardly visible if I use light icon theme. If I use dark icon theme with Breeze light color theme then all icons go invisible on my system. ownCloud icon was just fine before the update with the sam setup. I can't use Breeze light desktop theme because I can hardly see in the light background. I need that dark background and contrast. Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[Oxygen] [Bug 356845] Scrollbars not displaying correctly in oxygen-gtk3
https://bugs.kde.org/show_bug.cgi?id=356845 --- Comment #8 from Hugo Pereira Da Costa --- alternative is to "not use" gtk3 applications ... -- You are receiving this mail because: You are watching all bug changes.
[Oxygen] [Bug 356845] Scrollbars not displaying correctly in oxygen-gtk3
https://bugs.kde.org/show_bug.cgi?id=356845 --- Comment #7 from Ruslan Kabatsayev --- GTK3 is binary incompatible with GTK2, and it uses CSS to do all its theming now. So no way to use oxygen-gtk2 with GTK3 apps. Your only option is to downgrade GTK3, although some GTK3 apps might require the features introduced in 3.15 and higher. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 350874] After login, my dual head config is stubbornly messed up.
https://bugs.kde.org/show_bug.cgi?id=350874 Michał changed: What|Removed |Added CC||kice...@gmail.com --- Comment #2 from Michał --- I've same problem: two monitors, before login everything is ok, views are separated. After login second monitor becomes a clone of the first one and both monitors are falling back to common resolution. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 356848] New themed icons for configure Kdenlive dialog section "Project Defaults"
https://bugs.kde.org/show_bug.cgi?id=356848 --- Comment #2 from wegwerf-1-...@gmx.de --- Created attachment 96153 --> https://bugs.kde.org/attachment.cgi?id=96153&action=edit lt_project-defaults.svgz -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 356848] New themed icons for configure Kdenlive dialog section "Project Defaults"
https://bugs.kde.org/show_bug.cgi?id=356848 --- Comment #1 from wegwerf-1-...@gmx.de --- Created attachment 96152 --> https://bugs.kde.org/attachment.cgi?id=96152&action=edit dk_project-defaults.svgz -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 356848] New themed icons for configure Kdenlive dialog section "Project Defaults"
https://bugs.kde.org/show_bug.cgi?id=356848 wegwerf-1-...@gmx.de changed: What|Removed |Added CC||wegwerf-1-...@gmx.de -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 356848] New: New themed icons for configure Kdenlive dialog section "Project Defaults"
https://bugs.kde.org/show_bug.cgi?id=356848 Bug ID: 356848 Summary: New themed icons for configure Kdenlive dialog section "Project Defaults" Product: kdenlive Version: unspecified Platform: Compiled Sources OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: User Interface Assignee: j...@kdenlive.org Reporter: wegwerf-1-...@gmx.de This bug report proposed new dark/light breeze themed icons to be used in the Kdenlive configuration dialog for the section "project defaults". Reproducible: Always Steps to Reproduce: 1. In Kdenlive, choose "Settings", then "Configure Kdenlive". Actual Results: Timeline section currently uses a plain file icon that may be interpreted as file-related settings. Expected Results: film icon with "new" star in black/white for project defaults, in line with typical breeze icons. -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 352256] Korganizer / Kontakt crash [EventViews::AgendaView::placeDecorations]
https://bugs.kde.org/show_bug.cgi?id=352256 Kevin Funk changed: What|Removed |Added CC||f.ma...@mail.com --- Comment #5 from Kevin Funk --- *** Bug 354729 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 354729] Trying to create an event or clicking on agenda results in whole app crashing
https://bugs.kde.org/show_bug.cgi?id=354729 Kevin Funk changed: What|Removed |Added Resolution|--- |DUPLICATE Status|UNCONFIRMED |RESOLVED --- Comment #1 from Kevin Funk --- *** This bug has been marked as a duplicate of bug 352256 *** -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 354896] Korganizer crashed with Wikipedia extension enabled
https://bugs.kde.org/show_bug.cgi?id=354896 Kevin Funk changed: What|Removed |Added Resolution|--- |DUPLICATE Status|UNCONFIRMED |RESOLVED --- Comment #1 from Kevin Funk --- *** This bug has been marked as a duplicate of bug 352256 *** -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 352256] Korganizer / Kontakt crash [EventViews::AgendaView::placeDecorations]
https://bugs.kde.org/show_bug.cgi?id=352256 Kevin Funk changed: What|Removed |Added CC||s.scalabri...@gmail.com --- Comment #4 from Kevin Funk --- *** Bug 354896 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 352256] Korganizer / Kontakt crash
https://bugs.kde.org/show_bug.cgi?id=352256 Kevin Funk changed: What|Removed |Added CC||kaminpattana...@gmail.com --- Comment #3 from Kevin Funk --- *** Bug 355492 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 352256] Korganizer / Kontakt crash [EventViews::AgendaView::placeDecorations]
https://bugs.kde.org/show_bug.cgi?id=352256 Kevin Funk changed: What|Removed |Added Summary|Korganizer / Kontakt crash |Korganizer / Kontakt crash ||[EventViews::AgendaView::pl ||aceDecorations] -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 355492] KOrganizer crash everytime when opened, after change the application settings
https://bugs.kde.org/show_bug.cgi?id=355492 Kevin Funk changed: What|Removed |Added Resolution|--- |DUPLICATE Status|UNCONFIRMED |RESOLVED --- Comment #1 from Kevin Funk --- *** This bug has been marked as a duplicate of bug 352256 *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 356843] Newly selected wallpaper is replaced with default one after use Alt+F2 and putting any letter in edit box
https://bugs.kde.org/show_bug.cgi?id=356843 --- Comment #6 from Thomas Lübking --- > When I have turned off compositor and I change wallpaper then it remains. What I wanted you to check is to - enable the compositor - change wallpaper - show krunner - make the desktop slide/old wallpaper appears/yaddayaddayadda happen - suspend the compositor (SHIFT+Alt+F12) -> what do you see now? I want to know whether this is something that happens only visually in the compositor or actually some odd behavior in the desktop process and no - I can obviously not reproduce whatever you see there. Otherwise i'd not ask but fix it. -- You are receiving this mail because: You are watching all bug changes.
[ark] [Bug 356806] use-after-free crash on closing ark after opening a damaged archive
https://bugs.kde.org/show_bug.cgi?id=356806 Elvis Angelaccio changed: What|Removed |Added CC||elvis.angelac...@kdemail.ne ||t Ever confirmed|0 |1 Status|UNCONFIRMED |CONFIRMED --- Comment #1 from Elvis Angelaccio --- I can confirm the crash with Ark 15.12. Thanks for reporting. -- You are receiving this mail because: You are watching all bug changes.
[ark] [Bug 356649] use-after-free crash on closing ark on previewing an archive
https://bugs.kde.org/show_bug.cgi?id=356649 --- Comment #11 from Elvis Angelaccio --- (In reply to Santhiar from comment #10) > Done :) [https://bugs.kde.org/show_bug.cgi?id=356806] > Since you were able to repro this, could you change the status to CONF? No, because I can't reproduce it on Ark 15.12, which is the latest stable release. This bug is either a duplicate of #355757, or a downstream issue. Until further investigations, let's keep it as unconfirmed. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 356847] New themed icons for configure Kdenlive dialog section "Timeline"
https://bugs.kde.org/show_bug.cgi?id=356847 wegwerf-1-...@gmx.de changed: What|Removed |Added CC||wegwerf-1-...@gmx.de -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 356847] New themed icons for configure Kdenlive dialog section "Timeline"
https://bugs.kde.org/show_bug.cgi?id=356847 --- Comment #2 from wegwerf-1-...@gmx.de --- Created attachment 96151 --> https://bugs.kde.org/attachment.cgi?id=96151&action=edit lt_time-line.svgz -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 356847] New themed icons for configure Kdenlive dialog section "Timeline"
https://bugs.kde.org/show_bug.cgi?id=356847 --- Comment #1 from wegwerf-1-...@gmx.de --- Created attachment 96150 --> https://bugs.kde.org/attachment.cgi?id=96150&action=edit dk_time-line.svgz -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 356847] New: New themed icons for configure Kdenlive dialog section "Timeline"
https://bugs.kde.org/show_bug.cgi?id=356847 Bug ID: 356847 Summary: New themed icons for configure Kdenlive dialog section "Timeline" Product: kdenlive Version: unspecified Platform: Compiled Sources OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: User Interface Assignee: j...@kdenlive.org Reporter: wegwerf-1-...@gmx.de This bug report proposed new dark/light breeze themed icons to be used in the Kdenlive configuration dialog for the section "timeline". Reproducible: Always Steps to Reproduce: 1. In Kdenlive, choose "Settings", then "Configure Kdenlive". Actual Results: Timeline section currently uses a colored display icon to be used with applications or system configuration. Expected Results: Timeline icon showing a heavily simplified timeline in black/white, thus in line with typical breeze icons. Please find themed icons attached. -- You are receiving this mail because: You are watching all bug changes.
[klipper] [Bug 356837] One cannot clear history when first time is not confirmed
https://bugs.kde.org/show_bug.cgi?id=356837 Piotr Mierzwinski changed: What|Removed |Added CC||piotr.mierzwin...@gmail.com --- Comment #2 from Piotr Mierzwinski --- Strangely. My "Clear history" button passed in state "readonly" and I can't use it even after relogin and even after restart the system. Only I can remove items one by one :-(. The only one configuration what I found is located in ~/.local/share/klipper and this is history: "history2.lst". I'm not aware about other configuration maybe there is another? Anyway. When I removed this configuration, and removed plasmoid and added it again, still I can't use "Clear history" button. It is locked for me :-(. How could I restore it properly? -- You are receiving this mail because: You are watching all bug changes.
[Oxygen] [Bug 356845] Scrollbars not displaying correctly in oxygen-gtk3
https://bugs.kde.org/show_bug.cgi?id=356845 --- Comment #6 from David Rosenstrauch --- Any suggestions on how I might be able to continue using the Oxygen theme on GTK apps? (Oxygen's a gorgeous theme which I've been using for years, and I'd like to continue.) Is there a way to tell GTK3 apps to use the oxygen-gtk2 theme instead? -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 356846] New: Volume control icon not shown in system tray
https://bugs.kde.org/show_bug.cgi?id=356846 Bug ID: 356846 Summary: Volume control icon not shown in system tray Product: kde Version: unspecified Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: rdb...@gmail.com The volume control icon is not shown in the system tray. There is a blank space for it but no icon. This is on some version 5 of KDE. Apparently version information is no longer shown on 'Help | About KDE'. Reproducible: Always Steps to Reproduce: 1. boot the system 2. 3. Actual Results: No volume control icon in system tray Expected Results: Volume control icon should be displayed in the system tray when enabled. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 356843] Newly selected wallpaper is replaced with default one after use Alt+F2 and putting any letter in edit box
https://bugs.kde.org/show_bug.cgi?id=356843 --- Comment #5 from Piotr Mierzwinski --- After relogin. Again I get default wallpaper and plasmoids disappeared. And when I invoked Alt+F2 and put k letter desktop again was slidding in the left side, but already has default wallpaper so it not changed :/. And one more curiosity. When I invoked "Plasma Widget Explorer" and found previously added plasmoids then I saw them with status "added". I mean I saw number 1 which was displayed in left top corner. Please note I have write permission for configuration directories (~/.config and ~/.local). Are you able to reproduce it? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 356844] Plasma 5 Wayland session doesn't start
https://bugs.kde.org/show_bug.cgi?id=356844 --- Comment #3 from Mike Lothian --- I can get weston-1.9 working ok, I'm not sure how I can investigate this issue, which logs should I be looking at for clues? Can I try and start kwin manually? Is there anything I need to set up? -- You are receiving this mail because: You are watching all bug changes.
[kscreensaver] [Bug 316348] kscreenlocker_greet constantly consumes around 20% CPU time
https://bugs.kde.org/show_bug.cgi?id=316348 James Carlson changed: What|Removed |Added CC||carls...@workingcode.com --- Comment #22 from James Carlson --- Also seen with plasma5-workspace-5.4.3-1.1.x86_64. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 356843] Newly selected wallpaper is replaced with default one after use Alt+F2 and putting any letter in edit box
https://bugs.kde.org/show_bug.cgi?id=356843
--- Comment #4 from Piotr Mierzwinski ---
Maybe "plasmashell" process crash/restart but I can't see any window message
only desktop is sliding
When I have turned off compositor and I change wallpaper then it remains. The
same with plasmoids. When I again turn on compositor (Alt+Shift+F12) then all
is fine - nothing like described above is not happens.
I had checked ("Enable compositor on starup") and then it happened when I
changed wallpaper and added plasmoids.
I try to log off and log in again with working (on startup) compositor.
--
You are receiving this mail because:
You are watching all bug changes.
[kwin] [Bug 356844] Plasma 5 Wayland session doesn't start
https://bugs.kde.org/show_bug.cgi?id=356844 Martin Gräßlin changed: What|Removed |Added Resolution|--- |UPSTREAM Status|UNCONFIRMED |RESOLVED Component|backend-wayland |wayland-generic --- Comment #2 from Martin Gräßlin --- It looks like Xwayland doesn't work. It reports lots of errors and we have messages about "Did the X11 server die?" and the failure to start the launcher also looks very suspicious. -- You are receiving this mail because: You are watching all bug changes.
[Oxygen] [Bug 356845] Scrollbars not displaying correctly in oxygen-gtk3
https://bugs.kde.org/show_bug.cgi?id=356845 Hugo Pereira Da Costa changed: What|Removed |Added Resolution|DUPLICATE |WONTFIX --- Comment #5 from Hugo Pereira Da Costa --- Hi, Thanks for reporting. Now, unfortunately, oxygen-gtk3 has become unmaintained, because it is not supported anymore upstream by latests versions of gtk3. Consequently, bugs will not be fixed, since the code is bound to be abandoned completely next time you update gtk3. See https://bugs.kde.org/show_bug.cgi?id=340288 and https://bugzilla.gnome.org/show_bug.cgi?id=735211 for more details. ... sorry. -- You are receiving this mail because: You are watching all bug changes.
[Oxygen] [Bug 356845] Scrollbars not displaying correctly in oxygen-gtk3
https://bugs.kde.org/show_bug.cgi?id=356845 Ruslan Kabatsayev changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |DUPLICATE --- Comment #4 from Ruslan Kabatsayev --- *** This bug has been marked as a duplicate of bug 340288 *** -- You are receiving this mail because: You are watching all bug changes.
[Oxygen] [Bug 340288] Port to CSS as GTK+3.15.0 doesn't load theme engines
https://bugs.kde.org/show_bug.cgi?id=340288 Ruslan Kabatsayev changed: What|Removed |Added CC||dar...@darose.net --- Comment #5 from Ruslan Kabatsayev --- *** Bug 356845 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[Oxygen] [Bug 356845] Scrollbars not displaying correctly in oxygen-gtk3
https://bugs.kde.org/show_bug.cgi?id=356845 --- Comment #3 from David Rosenstrauch --- I've added screenshots to show what I'm talking about. -- You are receiving this mail because: You are watching all bug changes.
[Oxygen] [Bug 356845] Scrollbars not displaying correctly in oxygen-gtk3
https://bugs.kde.org/show_bug.cgi?id=356845 --- Comment #2 from David Rosenstrauch --- Created attachment 96149 --> https://bugs.kde.org/attachment.cgi?id=96149&action=edit Scrollbars in oxygen-gtk3 -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 356772] "connect" does not work for mobile broadband connection
https://bugs.kde.org/show_bug.cgi?id=356772 Stefan Vater changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |WORKSFORME --- Comment #5 from Stefan Vater --- No, sorry compiling plasma-nm would take me a while, time I do not have right now. However, I managed to solve my problem by setting up a new "connection" in the connection editor. With this, everything seems to work. Sorry that I did not think about this possibility before. When I look at the configuration files in /etc/NetworkManager/system-connections the difference is essentially in password-flags and pin-flags. For the non-working connection it is: password-flags=1 pin-flags=2 while for the working one it is: password-flags=4 pin-flags=4 It is strange that I cannot even edit the non-working connection with the connection editor. When I open it the "OK" button is always greyed out and there pops up a notification saying "Connection data for SURFSTICK could not be gathered" (my translation) "No agents were available for this request". Hopefully this helps for future problems with old connection setups. If you would like to have the full configuration file, please let me know. Thanks a lot for the quick help! I set the status to RESOLVED/WORKSFORME. I hope that is right. -- You are receiving this mail because: You are watching all bug changes.
