[neon] [Bug 377145] New: colord-kde should be installed by default
https://bugs.kde.org/show_bug.cgi?id=377145 Bug ID: 377145 Summary: colord-kde should be installed by default Product: neon Version: unspecified Platform: Neon Packages OS: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: Packages User Edition Assignee: neon-b...@kde.org Reporter: ene...@gmail.com CC: j...@jriddell.org, neon-b...@kde.org, sit...@kde.org Target Milestone: --- Currently KDE doesn't have color management GUI enabled by default. It would be nice to have this preinstalled in Neon same as in Ubuntu/Gnome/Windows. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 372342] Face tag area is very short
https://bugs.kde.org/show_bug.cgi?id=372342 --- Comment #15 from caulier.gil...@gmail.com --- No. You cannot push. You have no right to do it. A developer account is for student selected for GSoC event. Not now... Please make a patch of your difference from your local repository : git diff > mydiff.patch ...and attach this patch to this entry. That all. It's simple no ??? Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 377144] New: Make folder dialog maximizes to dolphin window
https://bugs.kde.org/show_bug.cgi?id=377144 Bug ID: 377144 Summary: Make folder dialog maximizes to dolphin window Product: dolphin Version: 16.12.0 Platform: Neon Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: ene...@gmail.com Target Milestone: --- Created attachment 104333 --> https://bugs.kde.org/attachment.cgi?id=104333=edit Gif showing make folder dialog resized to dolphin window I'm not sure if it's bug or intentional, but please take a look @ gif -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 377081] Icons squashed horizontally in Discover
https://bugs.kde.org/show_bug.cgi?id=377081 Alexchanged: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |WORKSFORME --- Comment #1 from Alex --- It works fine after update from today, thank you! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 375976] appmenu not shown for gtk apps
https://bugs.kde.org/show_bug.cgi?id=375976 Kai Uwe Broulikchanged: What|Removed |Added Assignee|plasma-b...@kde.org |k...@privat.broulik.de CC||k...@privat.broulik.de, ||plasma-b...@kde.org Product|kded-appmenu|plasmashell Component|export |Global Menu Target Milestone|--- |1.0 --- Comment #4 from Kai Uwe Broulik --- The confirmed state doesn't have a consistent meaning to us. I set it to confirmed when I know that I will definitely work on fixing it soon'ish and/or already know roughly how which isn't the case here. Also, constantly reporting that it still doesn't work won't get it magically fixed. GTK doesn't support the global menu protocol we use anymore and therefore it won't ever work unless we support theirs which is declared a "non-stable protocol" by them, so I don't see how it can be implemented without a huge maintenance burden I am not willing to take. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 376433] Crash with composite transition
https://bugs.kde.org/show_bug.cgi?id=376433 --- Comment #8 from Aleksey Samoilov--- Same on 16.08.3 Application: Kdenlive (kdenlive), signal: Aborted Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 [Current thread is 1 (Thread 0x7f23046298c0 (LWP 3514))] Thread 11 (Thread 0x7f229f7ff700 (LWP 3657)): [KCrash Handler] #6 0x7f22fe082428 in __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:54 #7 0x7f22fe08402a in __GI_abort () at abort.c:89 #8 0x7f22c7422dde in movit::FlatInput::set_gl_state (this=0x7f22a614ce30, glsl_program_num=, prefix=..., sampler_num=0x7f229f7fe380) at flat_input.cpp:140 #9 0x7f22c7416838 in movit::EffectChain::execute_phase (this=this@entry=0x7f22a6151840, phase=phase@entry=0x7f22a6154760, last_phase=, bound_attribute_indices=bound_attribute_indices@entry=0x7f229f7fe490, output_textures=output_textures@entry=0x7f229f7fe4f0, generated_mipmaps=generated_mipmaps@entry=0x7f229f7fe4c0) at effect_chain.cpp:1876 #10 0x7f22c7416f70 in movit::EffectChain::render_to_fbo (this=this@entry=0x7f22a6151840, dest_fbo=2, width=width@entry=1280, height=height@entry=720) at effect_chain.cpp:1753 #11 0x7f22c7683a12 in GlslManager::render_frame_rgba (this=, chain=chain@entry=0x7f22a6151840, frame=frame@entry=0x7f22a4007990, width=width@entry=1280, height=height@entry=720, image=image@entry=0x7f229f7feae8) at filter_glsl_manager.cpp:451 #12 0x7f22c7684a49 in movit_render (chain=0x7f22a6151840, frame=0x7f22a4007990, format=0x28d26ec, output_format=mlt_image_rgb24a, width=1280, height=720, image=0x7f229f7feae8) at filter_movit_convert.cpp:454 #13 0x7f22c7686802 in convert_image (frame=0x7f22a4007990, image=0x7f229f7feae8, format=0x28d26ec, output_format=mlt_image_rgb24a) at filter_movit_convert.cpp:573 #14 0x7f230382d7a8 in mlt_frame_get_image (self=0x7f22a4007990, buffer=0x7f229f7feae8, format=0x28d26ec, width=0x7f229f7fecb4, height=0x7f229f7fecb8, writable=1) at mlt_frame.c:591 #15 0x7f230382d757 in mlt_frame_get_image (self=self@entry=0x7f22a4007990, buffer=buffer@entry=0x7f229f7feae8, format=format@entry=0x28d26ec, width=width@entry=0x7f229f7fecb4, height=height@entry=0x7f229f7fecb8, writable=writable@entry=1) at mlt_frame.c:585 #16 0x7f22cac73ab1 in transition_get_image (a_frame=a_frame@entry=0x7f22a4007990, image=image@entry=0x7f229f7feae8, format=format@entry=0x28d26ec, width=width@entry=0x7f229f7fecb4, height=height@entry=0x7f229f7fecb8, writable=writable@entry=0) at transition_affine.c:422 #17 0x7f230382d757 in mlt_frame_get_image (self=0x7f22a4007990, buffer=0x7f229f7feae8, format=0x28d26ec, width=0x7f229f7fecb4, height=0x7f229f7fecb8, writable=0) at mlt_frame.c:585 #18 0x7f230382d757 in mlt_frame_get_image (self=self@entry=0x7f22a4007990, buffer=buffer@entry=0x7f229f7feae8, format=format@entry=0x28d26ec, width=width@entry=0x7f229f7fecb4, height=height@entry=0x7f229f7fecb8, writable=writable@entry=0) at mlt_frame.c:585 #19 0x7f22c6ce0ad7 in transition_get_image (a_frame=a_frame@entry=0x7f2253e967f0, image=image@entry=0x7f229f7fecc8, format=format@entry=0x28d26ec, width=width@entry=0x7f229f7fecb4, height=height@entry=0x7f229f7fecb8, writable=writable@entry=0) at transition_frei0r.c:47 #20 0x7f230382d757 in mlt_frame_get_image (self=self@entry=0x7f2253e967f0, buffer=buffer@entry=0x7f229f7fecc8, format=format@entry=0x28d26ec, width=width@entry=0x7f229f7fecb4, height=height@entry=0x7f229f7fecb8, writable=writable@entry=0) at mlt_frame.c:585 #21 0x7f2303843789 in producer_get_image (self=self@entry=0x7f22a41362d0, buffer=buffer@entry=0x7f229f7fecc8, format=format@entry=0x28d26ec, width=width@entry=0x7f229f7fecb4, height=height@entry=0x7f229f7fecb8, writable=writable@entry=0) at mlt_tractor.c:370 #22 0x7f230382d757 in mlt_frame_get_image (self=self@entry=0x7f22a41362d0, buffer=buffer@entry=0x7f229f7fecc8, format=format@entry=0x28d26ec, width=width@entry=0x7f229f7fecb4, height=height@entry=0x7f229f7fecb8, writable=writable@entry=0) at mlt_frame.c:585 #23 0x7f2303840f34 in consumer_read_ahead_thread (arg=0x3e63eb0) at mlt_consumer.c:825 #24 0x00809929 in RenderThread::run() () #25 0x7f22feb4fb48 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #26 0x7f22fc5ae6ba in start_thread (arg=0x7f229f7ff700) at pthread_create.c:333 #27 0x7f22fe15382d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 10 (Thread 0x7f22adde4700 (LWP 3656)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f23038411bb in mlt_consumer_rt_frame (self=self@entry=0x3e63eb0) at mlt_consumer.c:1576 #2 0x7f22c7898d90 in consumer_thread (arg=0x3e63eb0) at consumer_sdl_audio.c:531 #3 0x7f22fc5ae6ba in start_thread (arg=0x7f22adde4700) at pthread_create.c:333 #4 0x7f22fe15382d in clone ()
[Heaptrack] [Bug 377143] New: Broken cleanup
https://bugs.kde.org/show_bug.cgi?id=377143 Bug ID: 377143 Summary: Broken cleanup Product: Heaptrack Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: m...@milianw.de Reporter: anton.ani...@htower.ru Target Milestone: --- version 1.0, build on ubuntu 16.04 When we run heaptrack in "attach to process" mode, the breaking (with Ctrl-C or kill) the analysis leads to not-full cleanup. Steps to reproduce: 1) Run some application 2) Take it PID 3) Run "heaptrack -p PID" from terminal 4) After "injection finished" message press Ctrl-C (break) or kill heaptrack process. Expected behavior: Heaptrack stops it work and perform all cleanup actions. Real behavior: Heaptrack stops it work and NOT perform cleanup actions. In particular the "heaptrack_interpret" process is still running and "breaks" next heaptrack runs. After the killing this "zombie" the attached process also died with error. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 372342] Face tag area is very short
https://bugs.kde.org/show_bug.cgi?id=372342 --- Comment #14 from Yingjie Liu <1127553...@qq.com> --- Hi Gilles, I cloned the repository from KDE server, added my code, compiled it and committed it. However, I can't push it to the server using git. So I do as the tutorial said: https://techbase.kde.org/Development/Tutorials/Git/GitQuickStart#Tell_ssh_to_use_this_key But I can't find a place in my kde account to edit the public ssh keys, so I still can't push the code. Then I read this tutorial: https://community.kde.org/Infrastructure/Get_a_Developer_Account#How_to_get_read-write_access_to_git.2Fsvn As it said, I applied for the KDE developer access (uploaded the ssh keys in applying page) and I set your name as Supporter. Is it necessary to have the KDE developer access to push the code to server? If so, please help my account to have the access. If not, can you tell me another way of how to set to push the code. Thanks! Yingjie Liu -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 365669] Face Recognition improvement suggestion
https://bugs.kde.org/show_bug.cgi?id=365669 --- Comment #6 from Evert Vorster--- Hi there, Gilles. I think my suggestion here was more to have a sort of training mode for the face recognition software. Normally it tries to detect and recognize all the faces as quick as possible. Unfortunately, this causes many faces to be wrongly detected and it is a pain to fix. I was thinking of a "training" or "manual" mode where the face tagger would go through your photos and stop as soon as it detects a face. The UI can then show the face, along with an configurable amount of guesses as to whose face it is in the picture. The user can then select the correct face, or add a new tag if the name is not on the list. Then it can carry on to the next face. In this way the software tries to help, and may speed up face tagging, but it won't be incorrectly tagging faces, and so won't learn the wrong faces. This alternative workflow would reduce the wrong detections quite a bit. Once the face tagger guesses correct every time, then one can put it into automatic mode. -Evert- -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 377135] Kwin crashes at random times
https://bugs.kde.org/show_bug.cgi?id=377135 Martin Gräßlinchanged: What|Removed |Added Status|UNCONFIRMED |NEEDSINFO Resolution|--- |BACKTRACE --- Comment #1 from Martin Gräßlin --- If KWin crashes we need the backtrace. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 377142] Move Tool Sluggish Performance in Wrap-around Mode
https://bugs.kde.org/show_bug.cgi?id=377142 --- Comment #1 from Emmet O'Neill--- I should add that the performance problem becomes noticeably worse as you zoom out and can see more instances of the canvas. Also, here are my current specs: Windows 10 64-bit Intel Core i7 930 (Bloomfield) 2.8Ghz 6GB DDR3 RAM @ 1333MHz AMD Radeon HD 7770 300Mhz 1GB VRAM Krita 3.1.2 with ~default configuration. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 377142] New: Move Tool Sluggish Performance in Wrap-around Mode
https://bugs.kde.org/show_bug.cgi?id=377142 Bug ID: 377142 Summary: Move Tool Sluggish Performance in Wrap-around Mode Product: krita Version: 3.1.2 Platform: MS Windows OS: MS Windows Status: UNCONFIRMED Severity: normal Priority: NOR Component: Tools Assignee: krita-bugs-n...@kde.org Reporter: emmetoneill@gmail.com Target Milestone: --- The Move Tool (T) suffers from a major performance hit when working in Wrap-around Mode (W). I noticed this while painting a moderately sized (1024x1024) tiling texture. It's probably just due to the sheer number of pixels that need to be drawn in Wrap-around mode, but it feels bad and is annoying to work with. Maybe there is some kind of optimization, level-of-detail, or 'Instant Preview Mode' kind of thing that can be used to speed up Wrap-around mode rendering? -- You are receiving this mail because: You are watching all bug changes.
[kpat] [Bug 377141] New: ran in terminal, output below, no sound
https://bugs.kde.org/show_bug.cgi?id=377141 Bug ID: 377141 Summary: ran in terminal, output below, no sound Product: kpat Version: 3.6 Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: co...@kde.org Reporter: sde...@pldi.net CC: kde-games-b...@kde.org Target Milestone: --- ALSA lib pcm.c:7966:(snd_pcm_recover) cannot recovery from underrun, prepare failed: Input/output error -- You are receiving this mail because: You are watching all bug changes.
[kded-appmenu] [Bug 375976] appmenu not shown for gtk apps
https://bugs.kde.org/show_bug.cgi?id=375976 PGillespiechanged: What|Removed |Added CC||vtp...@myfairpoint.net --- Comment #3 from PGillespie --- Updated to Plasma 5.9.3. Global menu still doesn't work with LibreOffice. Haven't tested with other applications. How is this still unconfirmed after so many reports? -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kconfig] [Bug 377067] Excessive fdatasync in KConfig::sync
https://bugs.kde.org/show_bug.cgi?id=377067 Michael Pynechanged: What|Removed |Added Ever confirmed|0 |1 CC||mp...@kde.org Status|UNCONFIRMED |CONFIRMED --- Comment #1 from Michael Pyne --- I can confirm KConfig::sync()s are happening that appear to be needless, which results in lock files being generated. This happens about 2-3 times for me on startup which isn't "excessive" IMO but is definitely not optimal. The fdatasync() are almost certainly intentional as part of QLockFile though, but I think it would only be necessary as part of the 'stale lock' detection (otherwise the contents of the lock file do not matter, only its presence in the directory is important for locking). Removing the fdatasync and relying on the FS's own data commit timing would be an upstream bug. That still leaves the question of why the KConfig object is promptly becoming dirty upon startup (the KConfig::sync method already avoids touching the disk if it doesn't think a writeback is necessary), or whether a QLockFile is the best anti-contention tool (maybe there's some kind of in-memory processed-shared primitive that would work... though that way is fraught with problems of its own). -- You are receiving this mail because: You are watching all bug changes.
[clazy] [Bug 377140] New: Signal methods no longer known as signals if signal method definition has been seen (e.g. with automoc)
https://bugs.kde.org/show_bug.cgi?id=377140 Bug ID: 377140 Summary: Signal methods no longer known as signals if signal method definition has been seen (e.g. with automoc) Product: clazy Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: kosse...@kde.org CC: smart...@kde.org Target Milestone: --- Created attachment 104332 --> https://bugs.kde.org/attachment.cgi?id=104332=edit Diff to tests/incorrect-emit/main.cpp to reproduce the bug In Okteta I get some wrong "warning: Emit keyword being used with non-signal X::y" on emitting calls of some signals in inline methods of subclasses of the class with the signal. It seems that happens when the method->getLocStart() in AccessSpecifierManager::qtAccessSpecifierType(...) does not point to the declaration of the signal method, but instead the definition (in the moc file). This happens e.g. on compiling automoc-generated bundle files, when the moc.cpp file for the class with the signal is included before the moc cpp files of the subclasses, whose inline methods (thus in the header) emit the signals: OktetaKastenGui_automoc.cpp has e.g. the lines #include "OktetaKastenGui_automoc.dir/moc_abstractbytear_XBUWMXYENN5IHJ.cpp" #include "OktetaKastenGui_automoc.dir/moc_bytearraybase3_YVTH2B5RNQKBMM.cpp" where the first line is the moc file for the class with the signal, and has void Kasten::AbstractByteArrayStreamEncoder::settingsChanged() { QMetaObject::activate(this, , 0, Q_NULLPTR); } Then the second pulls in the header of the subclass #include "some/long/relative/path/bytearraybase32streamencoder.h" That header has the inline definition of a method which emits settingsChanged(): inline void ByteArrayBase32StreamEncoder::setSettings( const Base32StreamEncoderSettings& settings ) { mSettings = settings; emit settingsChanged(); } Which then gets the warning: Emit keyword being used with non-signal Kasten::AbstractByteArrayStreamEncoder::settingsChanged [-Wclazy-incorrect-emit] The reason for this misbehaviour can be seen by the output of methodLoc.printToString(m_ci.getSourceManager()) in AccessSpecifierManager::qtAccessSpecifierType(...): .../kasten/gui/OktetaKastenGui_automoc.dir/moc_abstractbytear_XBUWMXYENN5IHJ.cpp:124:1 so this now is not the signal method declaration, but the definition. Which screws the assumption in the method. No clue about clang, also only typing this during sleep-interruption ;) thus just this report. I could reduce the problem to the code attached as patch, as a new test case for tests/incorrect-emit. Not sure how much 377134 is related to this bug or if it only screws the bug simulation a little. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney4] [Bug 331538] Wrong balance calculation
https://bugs.kde.org/show_bug.cgi?id=331538 --- Comment #14 from Rene A.--- Any luck? > On Mar 1, 2017, at 11:41 AM, Jack wrote: > > https://bugs.kde.org/show_bug.cgi?id=331538 > > --- Comment #13 from Jack --- > I will look at the test file later today. > > -- > You are receiving this mail because: > You are on the CC list for the bug. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 367732] Plasma panel tooltip sometimes shows blury/pixelated app icon
https://bugs.kde.org/show_bug.cgi?id=367732 --- Comment #7 from Dr. Chapatin--- Sorry, I dont know. How can I check the resolution of these icons? -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 377139] Changing widget style does not work
https://bugs.kde.org/show_bug.cgi?id=377139 --- Comment #1 from Christoph Feck--- It works here. Some random comments: - Make sure you are actually changing the style for the correct Qt version. For Qt5 applications, start systemsettings5, for Qt4 applications, "kcmshell4 colors" or "kcmshell4 style". - Please also check if the files ~/.config/kdeglobals (for Qt5) or ~/.kde4/share/config/kdeglobals (for Qt4) are writable and contain the changes you made. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 377139] New: Changing widget style does not work
https://bugs.kde.org/show_bug.cgi?id=377139 Bug ID: 377139 Summary: Changing widget style does not work Product: systemsettings Version: 5.8.6 Platform: PCLinuxOS OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: kcm_style Assignee: tibi...@kde.org Reporter: terauck-...@yahoo.com.au Target Milestone: --- System Settings > Appearance > Application Style > Widget Style. Changing the widget style does not take effect. I have tried with the Fusion and Oxygen widget styles. Those styles use ticked or checked boxes to indicate when an option is selected. The Breeze style uses coloured boxes and that continues notwithstanding the choice of another widget style. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 367732] Plasma panel tooltip sometimes shows blury/pixelated app icon
https://bugs.kde.org/show_bug.cgi?id=367732 David Edmundsonchanged: What|Removed |Added Status|UNCONFIRMED |NEEDSINFO Resolution|--- |WAITINGFORINFO --- Comment #6 from David Edmundson --- Do any of them provide high resolution icons? If they don't, that's the fault of the application. If they do, then it's our fault - can you reset this bug to unconfirmed when you reply. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 367732] Plasma panel tooltip sometimes shows blury/pixelated app icon
https://bugs.kde.org/show_bug.cgi?id=367732 David Edmundsonchanged: What|Removed |Added Component|Panel |Task Manager CC||k...@davidedmundson.co.uk, ||plasma-b...@kde.org Assignee|plasma-b...@kde.org |h...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 375388] Crash in QQuickItemPrivate::setEffectiveVisibleRecursive
https://bugs.kde.org/show_bug.cgi?id=375388 David Edmundsonchanged: What|Removed |Added Assignee|k...@davidedmundson.co.uk|plasma-b...@kde.org Component|general |generic-crash -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 377137] Plasma crash
https://bugs.kde.org/show_bug.cgi?id=377137 David Edmundsonchanged: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |DUPLICATE --- Comment #1 from David Edmundson --- *** This bug has been marked as a duplicate of bug 375388 *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 375388] Crash in QQuickItemPrivate::setEffectiveVisibleRecursive
https://bugs.kde.org/show_bug.cgi?id=375388 David Edmundsonchanged: What|Removed |Added CC||forz...@hotmail.com --- Comment #18 from David Edmundson --- *** Bug 377137 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[umbrello] [Bug 377138] New: Umbrello might benefit from a make check target
https://bugs.kde.org/show_bug.cgi?id=377138 Bug ID: 377138 Summary: Umbrello might benefit from a make check target Product: umbrello Version: Git Platform: Compiled Sources OS: All Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: general Assignee: umbrello-de...@kde.org Reporter: k...@thevertigo.com Target Milestone: --- I'm not sure how exactly it could be implemented, but at present I don't think Umbrello has any unit testing framework that is invoked on the standard GCS make check target. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 377137] New: Plasma crash
https://bugs.kde.org/show_bug.cgi?id=377137 Bug ID: 377137 Summary: Plasma crash Product: plasmashell Version: 5.9.3 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: forz...@hotmail.com CC: bhus...@gmail.com, plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.9.3) Qt Version: 5.8.0 Frameworks Version: 5.31.0 Operating System: Linux 4.9.11-1-ARCH x86_64 Distribution: "Arch Linux" -- Information about the crash: - What I was doing when the application crashed: Sometimes when I click on the plasma applet on the top left corner Plasma crash completely and restarts. The crash can be reproduced sometimes. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7f42332d1800 (LWP 582))] Thread 8 (Thread 0x7f416b430700 (LWP 717)): #0 0x7f422d2a7ef9 in QTimerInfoList::repairTimersIfNeeded() () at /usr/lib/libQt5Core.so.5 #1 0x7f422d2a7f83 in QTimerInfoList::timerWait(timespec&) () at /usr/lib/libQt5Core.so.5 #2 0x7f422d2a963e in () at /usr/lib/libQt5Core.so.5 #3 0x7f42277a3c8d in g_main_context_prepare () at /usr/lib/libglib-2.0.so.0 #4 0x7f42277a46cb in () at /usr/lib/libglib-2.0.so.0 #5 0x7f42277a48bc in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #6 0x7f422d2aa06b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #7 0x7f422d25389a in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #8 0x7f422d075a73 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #9 0x7f416dd020a7 in KCupsConnection::run() () at /usr/lib/libkcupslib.so #10 0x7f422d07a6d8 in () at /usr/lib/libQt5Core.so.5 #11 0x7f422bf45454 in start_thread () at /usr/lib/libpthread.so.0 #12 0x7f422c98f7df in clone () at /usr/lib/libc.so.6 Thread 7 (Thread 0x7f417e2da700 (LWP 716)): #0 0x7f42277e9e64 in g_mutex_unlock () at /usr/lib/libglib-2.0.so.0 #1 0x7f42277a475a in () at /usr/lib/libglib-2.0.so.0 #2 0x7f42277a48bc in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #3 0x7f422d2aa06b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x7f422d25389a in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #5 0x7f422d075a73 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #6 0x7f4230d62fd6 in () at /usr/lib/libQt5Quick.so.5 #7 0x7f422d07a6d8 in () at /usr/lib/libQt5Core.so.5 #8 0x7f422bf45454 in start_thread () at /usr/lib/libpthread.so.0 #9 0x7f422c98f7df in clone () at /usr/lib/libc.so.6 Thread 6 (Thread 0x7f4208d57700 (LWP 713)): #0 0x7f422bf4b10f in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f4232a57234 in () at /usr/lib/libQt5Script.so.5 #2 0x7f4232a57279 in () at /usr/lib/libQt5Script.so.5 #3 0x7f422bf45454 in start_thread () at /usr/lib/libpthread.so.0 #4 0x7f422c98f7df in clone () at /usr/lib/libc.so.6 Thread 5 (Thread 0x7f420ad89700 (LWP 710)): #0 0x7f422c98648d in poll () at /usr/lib/libc.so.6 #1 0x7f42277a47a6 in () at /usr/lib/libglib-2.0.so.0 #2 0x7f42277a48bc in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #3 0x7f422d2aa06b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x7f422d25389a in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #5 0x7f422d075a73 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #6 0x7f42301af025 in () at /usr/lib/libQt5Qml.so.5 #7 0x7f422d07a6d8 in () at /usr/lib/libQt5Core.so.5 #8 0x7f422bf45454 in start_thread () at /usr/lib/libpthread.so.0 #9 0x7f422c98f7df in clone () at /usr/lib/libc.so.6 Thread 4 (Thread 0x7f4218f08700 (LWP 649)): #0 0x7f42277a3d9d in g_main_context_prepare () at /usr/lib/libglib-2.0.so.0 #1 0x7f42277a46cb in () at /usr/lib/libglib-2.0.so.0 #2 0x7f42277a48bc in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #3 0x7f422d2aa06b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x7f422d25389a in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #5 0x7f422d075a73 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #6 0x7f42301af025 in () at /usr/lib/libQt5Qml.so.5 #7 0x7f422d07a6d8 in () at /usr/lib/libQt5Core.so.5 #8 0x7f422bf45454 in start_thread () at /usr/lib/libpthread.so.0 #9 0x7f422c98f7df in clone () at /usr/lib/libc.so.6 Thread 3 (Thread 0x7f421a950700 (LWP 625)): #0 0x7f42277e9e49 in g_mutex_lock () at /usr/lib/libglib-2.0.so.0 #1 0x7f42277a3670 in g_main_context_acquire () at /usr/lib/libglib-2.0.so.0 #2
[dolphin] [Bug 377136] New: Dolphin crashes shift-Deleting 60 files on nfs4 volume on server
https://bugs.kde.org/show_bug.cgi?id=377136 Bug ID: 377136 Summary: Dolphin crashes shift-Deleting 60 files on nfs4 volume on server Product: dolphin Version: 16.08.2 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: mnpmo...@gmail.com Target Milestone: --- Application: dolphin (16.08.2) Qt Version: 5.6.1 Frameworks Version: 5.26.0 Operating System: Linux 4.4.49-16-default x86_64 Distribution: "openSUSE Leap 42.2" -- Information about the crash: - What I was doing when the application crashed: Shift deleting 60 large files on an nfs4 volume on local server. 10 tabs. separate dolpin window remained open -- Backtrace: Application: Dolphin (dolphin), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7fb792182900 (LWP 2321))] Thread 5 (Thread 0x7fb762b70700 (LWP 2398)): #0 0x7fb7868657d4 in g_mutex_unlock () at /usr/lib64/libglib-2.0.so.0 #1 0x7fb786823d99 in g_main_context_check () at /usr/lib64/libglib-2.0.so.0 #2 0x7fb7868242a8 in () at /usr/lib64/libglib-2.0.so.0 #3 0x7fb78682442c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #4 0x7fb78bd1232b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7fb78bcbffdb in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #6 0x7fb78bafaf1a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #7 0x7fb78baff9e9 in () at /usr/lib64/libQt5Core.so.5 #8 0x7fb7873ab734 in start_thread () at /lib64/libpthread.so.0 #9 0x7fb791a3fd3d in clone () at /lib64/libc.so.6 Thread 4 (Thread 0x7fb767ec6700 (LWP 2386)): #0 0x7fb7873b00af in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fb772f7e533 in () at /usr/lib64/dri/r600_dri.so #2 0x7fb772f7dd57 in () at /usr/lib64/dri/r600_dri.so #3 0x7fb7873ab734 in start_thread () at /lib64/libpthread.so.0 #4 0x7fb791a3fd3d in clone () at /lib64/libc.so.6 Thread 3 (Thread 0x7fb778c4e700 (LWP 2330)): #0 0x7fb791a3749d in poll () at /lib64/libc.so.6 #1 0x7fb786824314 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7fb78682442c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7fb78bd1232b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7fb78bcbffdb in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7fb78bafaf1a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #6 0x7fb78c1261d5 in () at /usr/lib64/libQt5DBus.so.5 #7 0x7fb78baff9e9 in () at /usr/lib64/libQt5Core.so.5 #8 0x7fb7873ab734 in start_thread () at /lib64/libpthread.so.0 #9 0x7fb791a3fd3d in clone () at /lib64/libc.so.6 Thread 2 (Thread 0x7fb77a7d9700 (LWP 2327)): #0 0x7fb791a3749d in poll () at /lib64/libc.so.6 #1 0x7fb7847de3e2 in () at /usr/lib64/libxcb.so.1 #2 0x7fb7847dffcf in xcb_wait_for_event () at /usr/lib64/libxcb.so.1 #3 0x7fb77cd33839 in () at /usr/lib64/libQt5XcbQpa.so.5 #4 0x7fb78baff9e9 in () at /usr/lib64/libQt5Core.so.5 #5 0x7fb7873ab734 in start_thread () at /lib64/libpthread.so.0 #6 0x7fb791a3fd3d in clone () at /lib64/libc.so.6 Thread 1 (Thread 0x7fb792182900 (LWP 2321)): [KCrash Handler] #6 0x7fb790f4f884 in KNotification::flags() const () at /usr/lib64/libKF5Notifications.so.5 #7 0x7fb790f6d7e7 in () at /usr/lib64/libKF5Notifications.so.5 #8 0x7fb790f73265 in () at /usr/lib64/libKF5Notifications.so.5 #9 0x7fb78bcebbb1 in QMetaObject::activate(QObject*, int, int, void**) () at /usr/lib64/libQt5Core.so.5 #10 0x7fb78d398ea5 in () at /usr/lib64/libphonon4qt5.so.4 #11 0x7fb78bced166 in QObject::event(QEvent*) () at /usr/lib64/libQt5Core.so.5 #12 0x7fb78cc49e3c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib64/libQt5Widgets.so.5 #13 0x7fb78cc4e49a in QApplication::notify(QObject*, QEvent*) () at /usr/lib64/libQt5Widgets.so.5 #14 0x7fb78bcc1fc5 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib64/libQt5Core.so.5 #15 0x7fb78bcc3daa in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () at /usr/lib64/libQt5Core.so.5 #16 0x7fb78bd12c83 in () at /usr/lib64/libQt5Core.so.5 #17 0x7fb786824134 in g_main_context_dispatch () at /usr/lib64/libglib-2.0.so.0 #18 0x7fb786824388 in () at /usr/lib64/libglib-2.0.so.0 #19 0x7fb78682442c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #20 0x7fb78bd1230c in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #21 0x7fb78bcbffdb in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #22 0x7fb78bcc7ec6 in
[plasmashell] [Bug 377016] mouse-button-events in systemtray changes virtual desktop
https://bugs.kde.org/show_bug.cgi?id=377016 David Edmundsonchanged: What|Removed |Added Status|CONFIRMED |NEEDSINFO Resolution|--- |WAITINGFORINFO CC||k...@davidedmundson.co.uk --- Comment #2 from David Edmundson --- If you make a new panel, does it happen there? I removed "containment actions" from being default the panel years ago, but as I did it mostly as a memory optimisation, I didn't clean up existing configs. Please reopen the bug when you reply. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 377135] New: Kwin crashes at random times
https://bugs.kde.org/show_bug.cgi?id=377135 Bug ID: 377135 Summary: Kwin crashes at random times Product: kwin Version: unspecified Platform: RedHat RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: compositing Assignee: kwin-bugs-n...@kde.org Reporter: billrclar...@stny.rr.com Target Milestone: --- Kwin crashes at random times for no apparent reason. The screen may flash and the message window will appear. The problem occurs when it occurs, and I cannot see any consistency to it. There may or may not be some visible results, such as all window title bars turn black. Am using Opensuse 42.2, KDE Plasma and an NVIDIA graphics card. Problem also occurs in Plasma 5. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 377019] [copyq-git, qt5 build] why menu is soo high?
https://bugs.kde.org/show_bug.cgi?id=377019 David Edmundsonchanged: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |UPSTREAM --- Comment #4 from David Edmundson --- Just read upstream, they're changing the number of items in repsonse to aboutToShow; they're sending the new data after we've resized the popups. They claim it's us with the bug, I'm not very convinced. If they want to send us a bustle log, we can see either way. Anyway, they've worked round it upstream so that the we get the DBus reply from aboutToShow before they signal layoutChanged. Seems to work. -- You are receiving this mail because: You are watching all bug changes.
[clazy] [Bug 377134] New: Class method wrongly tagged as Qt signal if defined after class declaration with Q_SIGNALS as last section
https://bugs.kde.org/show_bug.cgi?id=377134 Bug ID: 377134 Summary: Class method wrongly tagged as Qt signal if defined after class declaration with Q_SIGNALS as last section Product: clazy Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: kosse...@kde.org CC: smart...@kde.org Target Milestone: --- Created attachment 104331 --> https://bugs.kde.org/attachment.cgi?id=104331=edit Diff to tests/incorrect-emit/main.cpp to reproduce the bug In Okteta I get some wrong "warning: Missing emit keyword on signal call" on calls of some methods defined separately as inline methods right after the class declaration in the header. I could reduce the problem to the code attached as patch, as a new test case for tests/incorrect-emit. Seems that somehow the code location comparison in AccessSpecifierManager::qtAccessSpecifierType(...) does not work as intended, but I am too tired to research this more tonight, so just dumping the current state and hoping for the expert to quickly find the mistake :) -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 377133] New: Multiple tags don't display in video metadata
https://bugs.kde.org/show_bug.cgi?id=377133 Bug ID: 377133 Summary: Multiple tags don't display in video metadata Product: digikam Version: 5.4.0 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Metadata-Editor Assignee: digikam-de...@kde.org Reporter: fionabeat...@gmail.com Target Milestone: --- Hi, I have attached more than one tag to my video files (MP4); however, only one shows up in the IPTC field. This is not the case for photo files, where multiple tags show up separated by a comma in the IPTC field. Is there a solution for this? Cheers, -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 377056] Double icon for pinned Krita, only one with recent documents
https://bugs.kde.org/show_bug.cgi?id=377056 David Edmundsonchanged: What|Removed |Added CC||k...@davidedmundson.co.uk, ||plasma-b...@kde.org Assignee|plasma-b...@kde.org |h...@kde.org Component|Panel |Task Manager -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 377085] Glitches and crash
https://bugs.kde.org/show_bug.cgi?id=377085 David Edmundsonchanged: What|Removed |Added Resolution|--- |DUPLICATE Status|UNCONFIRMED |RESOLVED --- Comment #1 from David Edmundson --- Please upgrade your version of Mesa. If you still have problems with the latest version report the bug there. Thanks *** This bug has been marked as a duplicate of bug 365899 *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 365899] Plasma unexpectedly crashes
https://bugs.kde.org/show_bug.cgi?id=365899 David Edmundsonchanged: What|Removed |Added CC||masterofn...@protonmail.ch --- Comment #4 from David Edmundson --- *** Bug 377085 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 363118] Plasma crashes when turning on external audio device connected via HDMI
https://bugs.kde.org/show_bug.cgi?id=363118 David Edmundsonchanged: What|Removed |Added Component|general |generic-crash Assignee|k...@davidedmundson.co.uk|plasma-b...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 377132] Add three finger swipes (up, down, left, right) as possible shortcut inputs.
https://bugs.kde.org/show_bug.cgi?id=377132 David Edmundsonchanged: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |LATER --- Comment #1 from David Edmundson --- It's planned, for touchpad too. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 376958] Tax form fill in doesn't work
https://bugs.kde.org/show_bug.cgi?id=376958 Albert Astals Cidchanged: What|Removed |Added Status|UNCONFIRMED |RESOLVED Latest Commit||https://commits.kde.org/oku ||lar/4573c7a646068c2f49a02c5 ||0ee8bc4c157a3f791 Resolution|--- |FIXED --- Comment #4 from Albert Astals Cid --- Git commit 4573c7a646068c2f49a02c50ee8bc4c157a3f791 by Albert Astals Cid. Committed on 03/03/2017 at 00:08. Pushed by aacid into branch 'master'. Recalculate forms after other are edited M +35 -0core/document.cpp M +2-0core/document_p.h M +7-0generators/poppler/generator_pdf.cpp https://commits.kde.org/okular/4573c7a646068c2f49a02c50ee8bc4c157a3f791 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 377059] Open Folder in New Window fails if folder name ends with space
https://bugs.kde.org/show_bug.cgi?id=377059 Christoph Feckchanged: What|Removed |Added Resolution|--- |UPSTREAM Status|UNCONFIRMED |RESOLVED --- Comment #2 from Christoph Feck --- Thanks, just found David's comment in bug 368999. https://codereview.qt-project.org/186246 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 377132] New: Add three finger swipes (up, down, left, right) as possible shortcut inputs.
https://bugs.kde.org/show_bug.cgi?id=377132 Bug ID: 377132 Summary: Add three finger swipes (up, down, left, right) as possible shortcut inputs. Product: plasmashell Version: master Platform: Other OS: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: matthewma...@gmail.com CC: bhus...@gmail.com, plasma-b...@kde.org Target Milestone: 1.0 Plasma5 already has shortcuts for switching between desktops, maximizing windows, etc, but the inputs for these shortcuts are key presses only. It would be great for laptop users if three finger swipes on the touchpad could activate these as well. -- You are receiving this mail because: You are watching all bug changes.
[i18n] [Bug 376243] Várias traduções estão em pt-pt
https://bugs.kde.org/show_bug.cgi?id=376243 Luiz Fernando Ranghettichanged: What|Removed |Added Resolution|--- |FIXED Status|REOPENED|RESOLVED --- Comment #8 from Luiz Fernando Ranghetti --- Olá, Traduzidos: https://websvn.kde.org/?revision=1483889=revision -> stable https://websvn.kde.org/?revision=1483890=revision -> trunk Não gostarias de ajudar com as traduções? -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 377131] Audio files with colon in name are silently ignored by rendering
https://bugs.kde.org/show_bug.cgi?id=377131 dahutdedio...@gmail.com changed: What|Removed |Added CC||dahutdedio...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 377131] New: Audio files with colon in name are silently ignored by rendering
https://bugs.kde.org/show_bug.cgi?id=377131 Bug ID: 377131 Summary: Audio files with colon in name are silently ignored by rendering Product: kdenlive Version: 16.12.2 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Video Display & Export Assignee: j...@kdenlive.org Reporter: dahutdedio...@gmail.com Target Milestone: --- I have an audio file named "00:00.flac", which is normally played in the preview, but is silently replaced by the same time of silence after rendering, using any rendering profile. It can be fixed by renaming the file into "00.00.flac" or "foo-bar.flac". However, "foo:bar.flac" does not work, so I conclude that colons are not correctly escaped somewhere in the rendering process. I had the same problem with .wav files, except that it was also not played in the preview. I didn't tested the fix for this case. I also did not test any other file format. The absence of warning or error makes it difficult to troubleshoot. Either a fix or a warning when opening such a file would be great. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 376935] Global shortcut settings: component selection list is editable
https://bugs.kde.org/show_bug.cgi?id=376935 Christoph Feckchanged: What|Removed |Added Resolution|--- |FIXED Status|UNCONFIRMED |RESOLVED Latest Commit||https://commits.kde.org/pla ||sma-desktop/cafc7d5a448a190 ||47762af3eb0d5e5a495ef58ad Version Fixed In||5.9.4 --- Comment #1 from Christoph Feck --- Git commit cafc7d5a448a19047762af3eb0d5e5a495ef58ad by Christoph Feck. Committed on 02/03/2017 at 23:21. Pushed by cfeck into branch 'Plasma/5.8'. Disable editing of 'Global Shortcuts' component names FIXED-IN: 5.9.4 Differential Revision: https://phabricator.kde.org/D4905 M +3-0kcms/keys/kglobalshortcutseditor.ui https://commits.kde.org/plasma-desktop/cafc7d5a448a19047762af3eb0d5e5a495ef58ad -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 377130] New: Power Saving Settings screen cut off when using resolution scaling. Does not scroll, either.
https://bugs.kde.org/show_bug.cgi?id=377130 Bug ID: 377130 Summary: Power Saving Settings screen cut off when using resolution scaling. Does not scroll, either. Product: kwin Version: unspecified Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: minor Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: matthewma...@gmail.com Target Milestone: --- Created attachment 104330 --> https://bugs.kde.org/attachment.cgi?id=104330=edit Example of window not scrolling I have a 1080p monitor (Dell XPS 13 9350) with resolution scaling set to 1.5. Most other windows work fine, but the power management window does not scroll and cannot be resized. The options on the bottom of the menu are inaccessible. See screenshot for example. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 376960] Preferencias del sistema se detuvo
https://bugs.kde.org/show_bug.cgi?id=376960 Christoph Feckchanged: What|Removed |Added Resolution|--- |DUPLICATE Status|UNCONFIRMED |RESOLVED --- Comment #1 from Christoph Feck --- Memory corruption likely caused by visiting one of the QML based modules. If you still get a crash with version 5.9.2, please add a comment. *** This bug has been marked as a duplicate of bug 373628 *** -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 376971] System Settings crashes after setting 'Defaults' to specific Application Style options and returning
https://bugs.kde.org/show_bug.cgi?id=376971 Christoph Feckchanged: What|Removed |Added Resolution|--- |DUPLICATE Status|UNCONFIRMED |RESOLVED --- Comment #1 from Christoph Feck --- *** This bug has been marked as a duplicate of bug 373628 *** -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 355711] System Settings crashed during exit processing.
https://bugs.kde.org/show_bug.cgi?id=355711 Christoph Feckchanged: What|Removed |Added CC||patrick.cara...@gmail.com --- Comment #50 from Christoph Feck --- *** Bug 376969 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 377118] kcm scrolls over window edge on wayland
https://bugs.kde.org/show_bug.cgi?id=377118 Christoph Feckchanged: What|Removed |Added Component|general |kcm Product|systemsettings |KScreen Assignee|plasma-b...@kde.org |se...@kde.org --- Comment #1 from Christoph Feck --- Not sure if this is specific to how the kscreen kcm embeds its QML controls, or if other QML based modules (e.g. try the kwin effects list) behave similar. -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 377129] New: Akregator crashes immediatelly after being launched
https://bugs.kde.org/show_bug.cgi?id=377129 Bug ID: 377129 Summary: Akregator crashes immediatelly after being launched Product: akregator Version: unspecified Platform: Neon Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: olar.bogdan@gmail.com Target Milestone: --- Application: akregator (5.4.2) Qt Version: 5.7.1 Frameworks Version: 5.31.0 Operating System: Linux 4.4.0-64-generic x86_64 Distribution: KDE neon User Edition 5.9 -- Information about the crash: - What I was doing when the application crashed: Starting the application using the Application Launcher. This happens every time I try to start Akregator. -- Backtrace: Application: Akregator (akregator), signal: Aborted Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7fdd2af959c0 (LWP 9265))] Thread 2 (Thread 0x7fdd20b55700 (LWP 9267)): #0 0x7fdd55903b5d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7fdd4d68e38c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fdd4d68e49c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fdd5643975b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7fdd563e40ba in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7fdd56213f64 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7fdd59535735 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #7 0x7fdd56218b48 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7fdd4f54f6ba in start_thread (arg=0x7fdd20b55700) at pthread_create.c:333 #9 0x7fdd5590f82d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 1 (Thread 0x7fdd2af959c0 (LWP 9265)): [KCrash Handler] #6 0x7fdd5583e428 in __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:54 #7 0x7fdd5584002a in __GI_abort () at abort.c:89 #8 0x7fdd561ff811 in QMessageLogger::fatal(char const*, ...) const () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #9 0x7fdd43d2bea6 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #10 0x7fdd43d2741d in ?? () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #11 0x7fdd43d28fa5 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #12 0x7fdd43ccbeb1 in QtWebEngineCore::BrowserContextAdapter::defaultContext() () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #13 0x7fdd594c0090 in QWebEngineProfile::defaultProfile() () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineWidgets.so.5 #14 0x7fdd594c4c19 in QWebEngineSettings::defaultSettings() () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineWidgets.so.5 #15 0x7fdd1b3a5ba6 in Akregator::Part::initFonts (this=this@entry=0x2889650) at /workspace/build/src/akregator_part.cpp:790 #16 0x7fdd1b3a834c in Akregator::Part::Part (this=this@entry=0x2889650, parentWidget=parentWidget@entry=0x27d97a0, parent=parent@entry=0x27d97a0, __in_chrg=, __vtt_parm=) at /workspace/build/src/akregator_part.cpp:258 #17 0x7fdd1b3ab1b1 in KPluginFactory::createPartInstance (parentWidget=0x27d97a0, parent=0x27d97a0, args=...) at /usr/include/KF5/KCoreAddons/kpluginfactory.h:485 #18 0x7fdd56b22d1f in KPluginFactory::create(char const*, QWidget*, QObject*, QList const&, QString const&) () from /usr/lib/x86_64-linux-gnu/libKF5CoreAddons.so.5 #19 0x0040aca5 in KPluginFactory::create (args=..., parent=0x27d97a0, this=0x288f900) at /usr/include/KF5/KCoreAddons/kpluginfactory.h:497 #20 Akregator::MainWindow::loadPart (this=this@entry=0x27d97a0) at /workspace/build/src/mainwindow.cpp:110 #21 0x0040908e in Akregator::Application::activate (this=0x7ffc6deab010, args=..., workingDir=...) at /workspace/build/src/main.cpp:65 #22 0x7fdd58fafa3d in KontactInterface::PimUniqueApplication::start(QStringList const&, bool) () from /usr/lib/x86_64-linux-gnu/libKF5KontactInterface.so.5 #23 0x00408707 in main (argc=1, argv=0x7ffc6deab178) at /workspace/build/src/main.cpp:103 Possible duplicates by query: bug 376837, bug 375284, bug 364721, bug 364342, bug 362635. Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 377077] Systemsettings5 sometimes crashes when I make modifications in some settings
https://bugs.kde.org/show_bug.cgi?id=377077 Christoph Feckchanged: What|Removed |Added Resolution|--- |DUPLICATE Status|UNCONFIRMED |RESOLVED --- Comment #1 from Christoph Feck --- *** This bug has been marked as a duplicate of bug 373628 *** -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 373628] systemsettings5 crashes when closing or going back
https://bugs.kde.org/show_bug.cgi?id=373628 Christoph Feckchanged: What|Removed |Added CC||anvar...@gmail.com --- Comment #95 from Christoph Feck --- *** Bug 377077 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 373628] systemsettings5 crashes when closing or going back
https://bugs.kde.org/show_bug.cgi?id=373628 Christoph Feckchanged: What|Removed |Added CC||mana.rall...@outlook.com --- Comment #94 from Christoph Feck --- *** Bug 376971 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 376969] crash after trying to change the hight of the characters to display the full needed info
https://bugs.kde.org/show_bug.cgi?id=376969 Christoph Feckchanged: What|Removed |Added Resolution|--- |DUPLICATE Status|UNCONFIRMED |RESOLVED --- Comment #1 from Christoph Feck --- *** This bug has been marked as a duplicate of bug 355711 *** -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 373628] systemsettings5 crashes when closing or going back
https://bugs.kde.org/show_bug.cgi?id=373628 Christoph Feckchanged: What|Removed |Added CC||cucure...@gmail.com --- Comment #93 from Christoph Feck --- *** Bug 376960 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 376924] Crashed while using system settings
https://bugs.kde.org/show_bug.cgi?id=376924 Christoph Feckchanged: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |DUPLICATE --- Comment #1 from Christoph Feck --- Memory corruption likely caused by visiting the window decoration or screenlock module. If you are sure you never visited these, please add a comment here. *** This bug has been marked as a duplicate of bug 373628 *** -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 373628] systemsettings5 crashes when closing or going back
https://bugs.kde.org/show_bug.cgi?id=373628 Christoph Feckchanged: What|Removed |Added CC||jkd...@zoho.com --- Comment #92 from Christoph Feck --- *** Bug 376924 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 376862] Colour scheme editor: little layout bug
https://bugs.kde.org/show_bug.cgi?id=376862 Christoph Feckchanged: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |DUPLICATE --- Comment #1 from Christoph Feck --- *** This bug has been marked as a duplicate of bug 372309 *** -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 372309] Appearance -> Colors -> Edit Scheme (dialog breakup on vertical expand)
https://bugs.kde.org/show_bug.cgi?id=372309 Christoph Feckchanged: What|Removed |Added CC||war...@gmx.de --- Comment #4 from Christoph Feck --- *** Bug 376862 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 357120] Remember rectangular region when retaking screenshot
https://bugs.kde.org/show_bug.cgi?id=357120 --- Comment #11 from Christoph Feck--- See also bug 375556. -- You are receiving this mail because: You are watching all bug changes.
[Oxygen] [Bug 366749] GTK+ applications complain about missing size field in oxygen
https://bugs.kde.org/show_bug.cgi?id=366749 Christoph Feckchanged: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #6 from Christoph Feck --- https://commits.kde.org/oxygen-icons5/7648c0005fafd5a6834d2479796c3717b77e5549 -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 377092] Krusader crashed on opening jpeg image in built-in viewer (using F3)
https://bugs.kde.org/show_bug.cgi?id=377092 --- Comment #2 from Christoph Feck--- Interesting that there are actually two threads started with Gwenview... Not sure if starting a single thread would solve the issue, or if this is an exiv2 bug. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 377096] Compsiting won't work no matter what I do...
https://bugs.kde.org/show_bug.cgi?id=377096 Chrischanged: What|Removed |Added Resolution|--- |FIXED Status|UNCONFIRMED |RESOLVED --- Comment #5 from Chris --- Ok... nevermind... turns out there was something corrupt, or something whacky in my settings... AND I didn't put my test user in the video group... just a coincidence that it was giving me similar issues. It threw me off track. Everything works as expected. Thanks for the assistance, sorry for the false post. -- You are receiving this mail because: You are watching all bug changes.
[kolourpaint] [Bug 377002] Scan button grayed out.
https://bugs.kde.org/show_bug.cgi?id=377002 Christoph Feckchanged: What|Removed |Added Resolution|WAITINGFORINFO |DOWNSTREAM Status|NEEDSINFO |RESOLVED --- Comment #5 from Christoph Feck --- Ah, I didn't notice the image you added. Indeed, it was not compiled against the ksane dependency. Please report this issue to the bug tracker of your distribution. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 377070] Kmail emptied inbox, all emails deleted!!!
https://bugs.kde.org/show_bug.cgi?id=377070 --- Comment #5 from William L. Thomson Jr.--- I cannot replicate this. I am sorry but at the time, dealing with the lost emails was more important than going on a mission to help developers fix a bug... I am not sure I could produce anything anyway. I have seen it happen before and was not much for me to produce in the form of log output etc. Does akonadi even have an activity log file? Nothing in /var/log/* even mentions akonadi... mysql logs are empty with last touched date of January 18th. Exactly where is this output I should be producing? I write lots of software. I rarely ever find or run into bugs my users report. Unit tests do not seem to eliminate user bugs either. That KDE Pim developers do not experience issues is of no surprise. I would google kmail2, and you will find countless reports of users having issues. Not sure you can even compare a Gentoo env to a Debian one. Assuming everything is the same version, maybe something newer in Gentoo than Debian, hard to say, lots of variables. The fact that akonadi does not log any output to system log files by default shows one of its many design flaws. Who ever came up with this concept clearly missed some very important aspects needed for debugging and fixing issues... Who writes software that does not log output by default. Much less core software like this? This is a joke... https://techbase.kde.org/KDE_PIM/Akonadi/Debug_IMAP#Debug_Output How is that supposed to help in situations where you cannot replicate what happpened. Go set that up after the fact of a problem occurring. Without log activity there is no trail. Write better software that produces logs of activity. That way when something goes wrong that log can be used to determine what went wrong. If this akonadi had logging by default, I would have included that with my bug report. You can see your giving users nothing to help developers in addressing issues. This software is horribly designed and coded all around. It is WAY to experimental and keeps radically changing. Some akonadi2/kube in the works, etc. Need to stop messing with things. Email should be reliable, rock solid. I have lost lots of individual emails. Kmail also has no ability to handle imap T flag. It pulls in messages that the server maybe trying to delete that come with the T flag. It keeps those in the folders, grayed out. I have to go into the folder in disk and delete the email. Then it is removed from the list. This losing all emails is another matter entirely. It not only wiped out inbox/cur but inbox/new. I will conclude with I have never had any issues with other email clients like I have repeatedly had with Kmail. I an not a novice user by any means. If I am running into such issues I can only imagine others. Anyone I speak to does not run kmail. Most avoid it for known issues. Even most on Gentoo who maintain KDE run from kmail2. Its you all software and reputation. Akonadi and kmail2 are very below subpar... New features added that are stupid while core features cause major issues... Some stupid area for favorite folders I cannot get rid of. Some dumb text next to emails saying no html message etc. While I lose all emails with no log output... -- You are receiving this mail because: You are watching all bug changes.
[kolourpaint] [Bug 377002] Scan button grayed out.
https://bugs.kde.org/show_bug.cgi?id=377002 --- Comment #4 from Christoph Feck--- Just installing all 'sane' related packages won't help, if kolourpaint was not compiled against the ksane dependency. In other words, we still need the information requested in comment 1. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 377120] invalidaccess -7
https://bugs.kde.org/show_bug.cgi?id=377120 Wolfgang Bauerchanged: What|Removed |Added CC||wba...@tmo.at --- Comment #1 from Wolfgang Bauer --- I would suspect this is the same as bug#371887 (caused by a security "fix" in ghostscript). Please try the fix in comment#7 there. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 377128] New: Zooming with ctrl+scrolling too fast
https://bugs.kde.org/show_bug.cgi?id=377128 Bug ID: 377128 Summary: Zooming with ctrl+scrolling too fast Product: okular Version: 1.0.0 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: minor Priority: NOR Component: general Assignee: okular-de...@kde.org Reporter: oceanofsola...@gmx.net Target Milestone: --- When I zoom using ctrl+scrolling (using a touchpad or a thinkpad pointing stick), okular zooms out or in way too fast. Reproduce: Open a document at 100% zoom, hold ctrl and scroll half a fingers width on your touchpad Result: Okular zooms out to 12% zoom (smallest level) Expected: Zoom out one step (to e.g. 90 %). The same happens when zooming in (get to 1600% zoom while barely moving my fingers). This makes zooming using ctrl+scroll impossible since I always overshoot my desired zoom level by large margins. This is on Arch Linux with KDE 5.9.3 and okular 1.0.2, the touchpad being handled by libinput 1.6.2. The fault might also lie with the way libinput generates scroll events. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 377127] New: Wrong item count on years in Dates View
https://bugs.kde.org/show_bug.cgi?id=377127 Bug ID: 377127 Summary: Wrong item count on years in Dates View Product: digikam Version: 5.5.0 Platform: Appimage OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: digikam-de...@kde.org Reporter: wscheffn...@gmail.com Target Milestone: --- The item count on one year "folder" says (0) although there are a lot of images in it. The month "folder" have correct counts. I found out so far that it happens to all year "folders" that were open when digiKam was closed last time. Steps to reproduce: - open a year in Dates View - close digiKam - start digiKam -> the count of the open year will be (0) - close that year - open one or more other years - restart digiKam -> now the count of the first year (now closed) will be correct again, instead those you opened are now showing (0). -- You are receiving this mail because: You are watching all bug changes.
[Oxygen] [Bug 366749] GTK+ applications complain about missing size field in oxygen
https://bugs.kde.org/show_bug.cgi?id=366749 --- Comment #5 from Tristan Miller--- No longer reproducible for me with Oxygen 5.30.0. Looks like the double comma has been removed in this version (possibly by my distribution). -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 372597] /usr/bin/kaccess crashes when started in a Wayland Session
https://bugs.kde.org/show_bug.cgi?id=372597 Lasse Bjerrechanged: What|Removed |Added CC||la...@lgb.dk --- Comment #16 from Lasse Bjerre --- I am also experiencing these crashes. This bug was introduced with Wayland 1.13. Downgrading to 1.12 fixes the problem temporarily. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 377070] Kmail emptied inbox, all emails deleted!!!
https://bugs.kde.org/show_bug.cgi?id=377070 Martin Steigerwaldchanged: What|Removed |Added CC||mar...@lichtvoll.de --- Comment #4 from Martin Steigerwald --- William, as is your report is not really actionable. It might be a duplicate or related to: [kmail2] [Bug 375149] New: Kmail deletes emails from folder after switching to folder which would indicate that it may have been introduced in a quite recent version of KMail + Akonadi. I currently use 16.04 on Debian and… since… years KMail did not loose a single mail. And I expect the same for the KDEPIM developers… so… if you want them to help you, I suggest you better create a bug report that contains enough information so that developers can really work with it. Christoph made some suggestions. I suggest you create a new bug report and we better forget about this one which isn´t really constructive. ++information, --rant … is what I suggest to you if you are really into creating a change for the better. (I certainly understand frustrations with Akonadi… I went through those as well.) -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 377126] New: Can't paste a folder from a local folder to a smb folder (fstab)
https://bugs.kde.org/show_bug.cgi?id=377126 Bug ID: 377126 Summary: Can't paste a folder from a local folder to a smb folder (fstab) Product: dolphin Version: 16.12.0 Platform: Neon Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: fre...@protonmail.com Target Milestone: --- I have an entry in my /etc/fstab like this : //192.168.0.1/Music /home/aaa/smb/Music cifs username=aaa,password=aaa,iocharset=utf8 0 0 When mounted, I can see my shared folder in Dolphin (this is not the problem). When I try to cut/paste a folder from my local DD to the remote folder (smb/cifs : //192.168.0.1/Music) I have an error : permission error. However if I just do copy/paste the same folder, then it works ... (I don't have this issue with Nautilus file manager installed on the same computer/os) -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 313702] Lost all emails in a folder
https://bugs.kde.org/show_bug.cgi?id=313702 --- Comment #7 from William L. Thomson Jr.--- This occurred again with my inbox I filed a new bug 377070. I wish this was taken more seriously. This seems to happen at times for no reason as happened with my inbox -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 377070] Kmail emptied inbox, all emails deleted!!!
https://bugs.kde.org/show_bug.cgi?id=377070 --- Comment #3 from William L. Thomson Jr.--- This is not something I can replicate. I have no clue how it happened. I have had nothing but problems with akonadi. It is complete garbage all around. This is DEFINITELY a bug report! Akonadi screwed up and wiped out my inbox and deleted all emails in the inbox maildir. There is NOTHING else that would delete files in just that one folder. Nothing else managed those maildir folders but kmail/akonadi. My contacts are all screwed up and other issues with akonadi I do not bother reporting or looking into. Stuff that is not in the address book file. Nor that shows in my contacts as I can correct or edit that stuff. So much garbage from akonadi its not funny. Seems another Gentoo dev started Trojita, I will likely see about contributing to that and moving on. Every for every potential benefit of akonadi there is substantially more issues. It is the WRONG direction to go and needs to be optional. Till it is not longer experimental and does not mess up. This may have been mysql corruption, since its using a HORRIBLE RDBMS, Should be using Posgresql or Firebird. Which really only Firebird has a true embedded option and mode. Not requiring a daemon. I had other issues early on with sqlite and that was dropped entirely. I cannot replicate. But ANY code in Akonadi to remove emails from disk should be removed immediately. It did not move the emails to the trash or anything. It literally wiped them from existence on my system. I have lots of filters, folders, hundreds of thousands of emails. No issue in other folders. However I have seen this indexing thing, were the emails seem to populate and messed with scrollbar, as akonadi is clearly doing something with the database and syncing emails on disk. Only KDE bugs I have ever filed are all on kmail2... https://bugs.kde.org/buglist.cgi?bug_status=UNCONFIRMED_status=CONFIRMED_status=ASSIGNED_status=REOPENED_status=RESOLVED_status=NEEDSINFO_status=VERIFIED_status=CLOSED=wlt=1=substring_id=1425933_format=advanced I really cannot emphasis enough the amount of issues since day 1. Across so many versions, libraries, etc. It is garbage It is extremely unreliable. It seems to be widely known but just about anyone. Not sure what it will take for KDE devs to get the message and stop this madness... If I leave KDE for another, it will be 100% due to kmail2. I wish I never left evolution seriously! Kmail has been nothing but a headache. If migrating away was trivial I would have already. -- You are receiving this mail because: You are watching all bug changes.
[Oxygen] [Bug 366749] GTK+ applications complain about missing size field in oxygen
https://bugs.kde.org/show_bug.cgi?id=366749 --- Comment #4 from qual...@gmail.com --- Comment on attachment 104329 --> https://bugs.kde.org/attachment.cgi?id=104329 Patch to index.theme In the file /usr/share/icons/oxygen/index.theme there is a Directories property in the [Icon Theme] section. This line includes two commas in a row. One of these commas should be removed. --> 256x256/apps,,256x256/applets -- You are receiving this mail because: You are watching all bug changes.
[Oxygen] [Bug 366749] GTK+ applications complain about missing size field in oxygen
https://bugs.kde.org/show_bug.cgi?id=366749 qual...@gmail.com changed: What|Removed |Added CC||qual...@gmail.com --- Comment #3 from qual...@gmail.com --- Created attachment 104329 --> https://bugs.kde.org/attachment.cgi?id=104329=edit Patch to index.theme -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 376952] Video playback issues - no sound
https://bugs.kde.org/show_bug.cgi?id=376952 --- Comment #10 from Maik Qualmann--- Gilles, which soundsystem does support CentOS 6.8? Pulse? OpenAL? Maik -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 377070] Kmail emptied inbox, all emails deleted!!!
https://bugs.kde.org/show_bug.cgi?id=377070 Christoph Feckchanged: What|Removed |Added Status|UNCONFIRMED |NEEDSINFO Resolution|--- |WAITINGFORINFO --- Comment #2 from Christoph Feck --- If this should indeed be a bug report (and not just a rant), make sure developers can follow what you see. Please add exact steps to reproduce, including configuration, ideally starting from a fresh user account. There is also the akonadiconsole and several akonadi log files that can help understanding and pinpointing your issue. akonadiconsole is described at https://techbase.kde.org/KDE_PIM/Akonadi/Development_Tools -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 377096] Compsiting won't work no matter what I do...
https://bugs.kde.org/show_bug.cgi?id=377096 --- Comment #4 from Chris--- Hmm... not sure how that got truncated but here it is: $ glxinfo name of display: :0 display: :0 screen: 0 direct rendering: Yes server glx vendor string: NVIDIA Corporation server glx version string: 1.4 server glx extensions: GLX_ARB_context_flush_control, GLX_ARB_create_context, GLX_ARB_create_context_profile, GLX_ARB_create_context_robustness, GLX_ARB_fbconfig_float, GLX_ARB_multisample, GLX_EXT_buffer_age, GLX_EXT_create_context_es2_profile, GLX_EXT_create_context_es_profile, GLX_EXT_framebuffer_sRGB, GLX_EXT_import_context, GLX_EXT_libglvnd, GLX_EXT_stereo_tree, GLX_EXT_swap_control, GLX_EXT_swap_control_tear, GLX_EXT_texture_from_pixmap, GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_NV_copy_image, GLX_NV_delay_before_swap, GLX_NV_float_buffer, GLX_NV_robustness_video_memory_purge, GLX_SGIX_fbconfig, GLX_SGIX_pbuffer, GLX_SGI_swap_control, GLX_SGI_video_sync client glx vendor string: NVIDIA Corporation client glx version string: 1.4 client glx extensions: GLX_ARB_context_flush_control, GLX_ARB_create_context, GLX_ARB_create_context_profile, GLX_ARB_create_context_robustness, GLX_ARB_fbconfig_float, GLX_ARB_get_proc_address, GLX_ARB_multisample, GLX_EXT_buffer_age, GLX_EXT_create_context_es2_profile, GLX_EXT_create_context_es_profile, GLX_EXT_fbconfig_packed_float, GLX_EXT_framebuffer_sRGB, GLX_EXT_import_context, GLX_EXT_stereo_tree, GLX_EXT_swap_control, GLX_EXT_swap_control_tear, GLX_EXT_texture_from_pixmap, GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_NV_copy_buffer, GLX_NV_copy_image, GLX_NV_delay_before_swap, GLX_NV_float_buffer, GLX_NV_multisample_coverage, GLX_NV_present_video, GLX_NV_robustness_video_memory_purge, GLX_NV_swap_group, GLX_NV_video_capture, GLX_NV_video_out, GLX_SGIX_fbconfig, GLX_SGIX_pbuffer, GLX_SGI_swap_control, GLX_SGI_video_sync GLX version: 1.4 GLX extensions: GLX_ARB_context_flush_control, GLX_ARB_create_context, GLX_ARB_create_context_profile, GLX_ARB_create_context_robustness, GLX_ARB_fbconfig_float, GLX_ARB_get_proc_address, GLX_ARB_multisample, GLX_EXT_buffer_age, GLX_EXT_create_context_es2_profile, GLX_EXT_create_context_es_profile, GLX_EXT_framebuffer_sRGB, GLX_EXT_import_context, GLX_EXT_stereo_tree, GLX_EXT_swap_control, GLX_EXT_swap_control_tear, GLX_EXT_texture_from_pixmap, GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_NV_copy_image, GLX_NV_delay_before_swap, GLX_NV_float_buffer, GLX_NV_robustness_video_memory_purge, GLX_SGIX_fbconfig, GLX_SGIX_pbuffer, GLX_SGI_swap_control, GLX_SGI_video_sync OpenGL vendor string: NVIDIA Corporation OpenGL renderer string: GeForce GTX 750/PCIe/SSE2 OpenGL core profile version string: 4.5.0 NVIDIA 378.13 OpenGL core profile shading language version string: 4.50 NVIDIA OpenGL core profile context flags: (none) OpenGL core profile profile mask: core profile OpenGL core profile extensions: GL_AMD_multi_draw_indirect, GL_AMD_seamless_cubemap_per_texture, GL_ARB_ES2_compatibility, GL_ARB_ES3_1_compatibility, GL_ARB_ES3_2_compatibility, GL_ARB_ES3_compatibility, GL_ARB_arrays_of_arrays, GL_ARB_base_instance, GL_ARB_bindless_texture, GL_ARB_blend_func_extended, GL_ARB_buffer_storage, GL_ARB_clear_buffer_object, GL_ARB_clear_texture, GL_ARB_clip_control, GL_ARB_color_buffer_float, GL_ARB_compressed_texture_pixel_storage, GL_ARB_compute_shader, GL_ARB_compute_variable_group_size, GL_ARB_conditional_render_inverted, GL_ARB_conservative_depth, GL_ARB_copy_buffer, GL_ARB_copy_image, GL_ARB_cull_distance, GL_ARB_debug_output, GL_ARB_depth_buffer_float, GL_ARB_depth_clamp, GL_ARB_depth_texture, GL_ARB_derivative_control, GL_ARB_direct_state_access, GL_ARB_draw_buffers, GL_ARB_draw_buffers_blend, GL_ARB_draw_elements_base_vertex, GL_ARB_draw_indirect, GL_ARB_draw_instanced, GL_ARB_enhanced_layouts, GL_ARB_explicit_attrib_location, GL_ARB_explicit_uniform_location, GL_ARB_fragment_coord_conventions, GL_ARB_fragment_layer_viewport, GL_ARB_fragment_program, GL_ARB_fragment_program_shadow, GL_ARB_fragment_shader,
[kalzium] [Bug 377114] qml file unused?
https://bugs.kde.org/show_bug.cgi?id=377114 Christoph Feckchanged: What|Removed |Added Resolution|--- |FIXED Status|UNCONFIRMED |RESOLVED --- Comment #1 from Christoph Feck --- https://commits.kde.org/kalzium/61cf33bbde4efa14e2d5081c75a8d880c35eec05 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 377109] Plasma panels display a strange background
https://bugs.kde.org/show_bug.cgi?id=377109 --- Comment #3 from tro...@free.fr --- I can't tell you right now because the bug occurs on my work computer, and I'm at home now (I'll tell you tomorrow). But, on my home computer on Wayland, the bug does not seem to happen, and the blur settings on this computer are : half-ticked blur option, strong effect strenght, and "Intermediate results" is ticked. And it seems to work this way. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 377103] "Sheet" effect doesn't work on Wayland
https://bugs.kde.org/show_bug.cgi?id=377103 --- Comment #2 from tro...@free.fr --- Yes, you're right : the effect works perfectly on Gnome File manager's Property modal dialog, which uses XWayland. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 377100] Wayland switches my monitors
https://bugs.kde.org/show_bug.cgi?id=377100 --- Comment #2 from tro...@free.fr --- OK, but there is still a "Primary display" option in the Kscreen configuration module. And Wayland puts all my plasma element on the wrong monitor. -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 202414] allow to hide status bar and toolbar
https://bugs.kde.org/show_bug.cgi?id=202414 --- Comment #9 from andydecle...@gmail.com --- Woo! -- You are receiving this mail because: You are watching all bug changes.
[krdc] [Bug 377107] key translation issue connecting to Linux from Mac
https://bugs.kde.org/show_bug.cgi?id=377107 RJVBchanged: What|Removed |Added CC||rjvber...@gmail.com --- Comment #1 from RJVB --- Created attachment 104328 --> https://bugs.kde.org/attachment.cgi?id=104328=edit patch for the keysym translation issue This patch adapts the solution from http://italc.sourcearchive.com/documentation/1.0.9.1/vncview_8cpp-source.html The test `if (QGuiApplication::platformName() == QStringLiteral("xcb"))` must probably include the wayland QPA, if that platform also returns X11/RFB keysyms from QKeyEvent::nativeVirtualKey(). -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 376931] Volume set to 100% when deleting a file
https://bugs.kde.org/show_bug.cgi?id=376931 --- Comment #1 from Christoph Feck--- Does it also happen with Phonon gstreamer backend? -- You are receiving this mail because: You are watching all bug changes.
[kio-extras] [Bug 375249] "File not found" when trying to open file from nfs
https://bugs.kde.org/show_bug.cgi?id=375249 --- Comment #4 from Luca Weiss--- Created attachment 104327 --> https://bugs.kde.org/attachment.cgi?id=104327=edit Workaround patch, not a proposed patch! -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 202414] allow to hide status bar and toolbar
https://bugs.kde.org/show_bug.cgi?id=202414 --- Comment #8 from Christoph Feck--- Valerio submitted https://phabricator.kde.org/D4901 (and did not add any reviewers :) -- You are receiving this mail because: You are watching all bug changes.
[kio-extras] [Bug 375249] "File not found" when trying to open file from nfs
https://bugs.kde.org/show_bug.cgi?id=375249 --- Comment #3 from Luca Weiss--- So after quite a bit of debugging I have found out that apparently the problem is that my NFS server has a share that's not available for my IP address (only for another one) and fhStatus.fhs_status (in nfsv3.cpp->openConnection()) gets set to 13 and if checks if the status is zero and otherwise throws an error (not right away but later). I have managed to work around this problem by putting a else if(fhStatus.fhs_status == 13) { continue; // skip mounts with no permission } there and I can now browse my NFS share again. luca@g550jk ~> showmount -e 192.168.0.50 Export list for 192.168.0.50: /mnt/data/libvirt 192.168.0.21 /mnt/data/media (everyone) Sample patch that *works around the problem* is attached. Note, that I have little experience in NFS and have no idea what the "13" actually means. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 365451] Task context menu incorrectly positioned to the left in multi-display mode
https://bugs.kde.org/show_bug.cgi?id=365451 Roman Gilgchanged: What|Removed |Added Resolution|--- |FIXED Status|REOPENED|RESOLVED --- Comment #8 from Roman Gilg --- Kai's problem should be fixed with: https://cgit.kde.org/plasma-framework.git/commit/?id=daee27f0962d7e0fe6cb38859689ea5f73c74379 Closing again. -- You are receiving this mail because: You are watching all bug changes.
[basket] [Bug 376872] kolourpaint hardcoded for image editing in basket?
https://bugs.kde.org/show_bug.cgi?id=376872 --- Comment #3 from Christoph Feck--- I guess for many users, the system default for images is a viewer, not an editing application, so that would be a reason to check for kolourpaint first. Still it should start the default if kolourpaint is not found. Keeping open for maintainers to decide. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 352519] Delete, cut copy and paste recursively from a group or multiple selected layer
https://bugs.kde.org/show_bug.cgi?id=352519 --- Comment #8 from David REVOY--- @gordie.lachance : It's already possible since more than 4 years to perform transform tool on multiple layers within a selection. ( ref: https://youtu.be/kgTkfebleCE?t=18s ) just group them, select the group on the layer stack, draw a selection and Ctrl+T. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 376910] Scrolling does not follow system settings
https://bugs.kde.org/show_bug.cgi?id=376910 keitalbamechanged: What|Removed |Added CC||keitalb...@posteo.net -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 377121] Screen layout is unusable when a single screen is rotated on wayland
https://bugs.kde.org/show_bug.cgi?id=377121 Martin Gräßlinchanged: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |INVALID --- Comment #1 from Martin Gräßlin --- It is not yet possible to rotate screens on Wayland. We even point out to it in the known issue section that screen configuration is not yet fully implemented. This is not yet part of our feature set. Thus I mark it as invalid (it is not a bug from our perspective). We track the development of new features through https://phabricator.kde.org/project/view/99/ -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 377096] Compsiting won't work no matter what I do...
https://bugs.kde.org/show_bug.cgi?id=377096 --- Comment #3 from Martin Gräßlin--- glxinfo provides way more output. That is just a very small part of it. Please attach the full glxinfo output. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 377109] Plasma panels display a strange background
https://bugs.kde.org/show_bug.cgi?id=377109 Martin Gräßlinchanged: What|Removed |Added Component|wayland-generic |effects-various Flags||Wayland+ --- Comment #2 from Martin Gräßlin --- what are your blur settings? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 364483] Wayland : Kwin's "Slide Back" effect does not work.
https://bugs.kde.org/show_bug.cgi?id=364483 Martin Gräßlinchanged: What|Removed |Added Flags||Wayland+ -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 377103] "Sheet" effect doesn't work on Wayland
https://bugs.kde.org/show_bug.cgi?id=377103 Martin Gräßlinchanged: What|Removed |Added Component|wayland-generic |effects-various Flags||Wayland+ --- Comment #1 from Martin Gräßlin --- There are no "modal dialog windows" on Wayland yet. Thus the effect cannot work. For X11 windows it should also work on Wayland. -- You are receiving this mail because: You are watching all bug changes.