[kmail2] [Bug 323929] kmail high cpu load, seems stuck looping on fetching mails from akonadi
https://bugs.kde.org/show_bug.cgi?id=323929 --- Comment #40 from Martin Steigerwald --- Please retest with most recent KDEPIM + Akonadi 15.12. It has a ton of performance fixes that are not going to be backported due to shift from Akonadi from Qt4 to Qt5. -- You are receiving this mail because: You are watching all bug changes.
[kalarm] [Bug 358625] New: klarm crashed when opening from systray
https://bugs.kde.org/show_bug.cgi?id=358625 Bug ID: 358625 Summary: klarm crashed when opening from systray Product: kalarm Version: unspecified Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: djar...@kde.org Reporter: v...@pelcak.org Application: kalarm (2.11.3-5ak) Qt Version: 5.5.1 Operating System: Linux 4.4.0-1-default x86_64 Distribution: "openSUSE Tumbleweed (20160121) (x86_64)" -- Information about the crash: - What I was doing when the application crashed: I had Kalarm in systray and when I clicked on its icon, I got segfault. Now when I want to reproduce it, kalarm won't create icon in systray. -- Backtrace: Application: KAlarm (kalarm), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7fb178831940 (LWP 2657))] Thread 4 (Thread 0x7fb157577700 (LWP 2658)): #0 0x7fb16fed424d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7fb16a2d3432 in _xcb_conn_wait (__timeout=-1, __nfds=1, __fds=0x7fb157576b80) at /usr/include/bits/poll2.h:46 #2 0x7fb16a2d3432 in _xcb_conn_wait (c=c@entry=0x2118b40, cond=cond@entry=0x2118b80, vector=vector@entry=0x0, count=count@entry=0x0) at xcb_conn.c:459 #3 0x7fb16a2d5007 in xcb_wait_for_event (c=0x2118b40) at xcb_in.c:693 #4 0x7fb15929fe29 in QXcbEventReader::run() (this=0x2123200) at qxcbconnection.cpp:1229 #5 0x7fb1707dc94f in QThreadPrivate::start(void*) (arg=0x2123200) at thread/qthread_unix.cpp:331 #6 0x7fb16a4f04a4 in start_thread (arg=0x7fb157577700) at pthread_create.c:334 #7 0x7fb16fedcbdd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 3 (Thread 0x7fb15568c700 (LWP 2659)): #0 0x7fb16fed424d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7fb169baf264 in g_main_context_iterate (priority=2147483647, n_fds=1, fds=0x7fb148003020, timeout=, context=0x7fb148000990) at gmain.c:4135 #2 0x7fb169baf264 in g_main_context_iterate (context=context@entry=0x7fb148000990, block=block@entry=1, dispatch=dispatch@entry=1, self=) at gmain.c:3835 #3 0x7fb169baf36c in g_main_context_iteration (context=0x7fb148000990, may_block=may_block@entry=1) at gmain.c:3901 #4 0x7fb170a0152b in QEventDispatcherGlib::processEvents(QFlags) (this=0x7fb1480008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420 #5 0x7fb1709ab63a in QEventLoop::exec(QFlags) (this=this@entry=0x7fb15568bc90, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #6 0x7fb1707d7b1c in QThread::exec() (this=) at thread/qthread.cpp:503 #7 0x7fb1707dc94f in QThreadPrivate::start(void*) (arg=0x21f6e90) at thread/qthread_unix.cpp:331 #8 0x7fb16a4f04a4 in start_thread (arg=0x7fb15568c700) at pthread_create.c:334 #9 0x7fb16fedcbdd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 2 (Thread 0x7fb154e8b700 (LWP 23572)): #0 0x7fb16fed424d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7fb169baf264 in g_main_context_iterate (priority=2147483647, n_fds=1, fds=0x7fb14c002e50, timeout=, context=0x7fb14c002cb0) at gmain.c:4135 #2 0x7fb169baf264 in g_main_context_iterate (context=context@entry=0x7fb14c002cb0, block=block@entry=1, dispatch=dispatch@entry=1, self=) at gmain.c:3835 #3 0x7fb169baf36c in g_main_context_iteration (context=0x7fb14c002cb0, may_block=may_block@entry=1) at gmain.c:3901 #4 0x7fb170a0152b in QEventDispatcherGlib::processEvents(QFlags) (this=0x7fb14c003f10, flags=...) at kernel/qeventdispatcher_glib.cpp:420 #5 0x7fb1709ab63a in QEventLoop::exec(QFlags) (this=this@entry=0x7fb154e8ac90, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #6 0x7fb1707d7b1c in QThread::exec() (this=) at thread/qthread.cpp:503 #7 0x7fb1707dc94f in QThreadPrivate::start(void*) (arg=0x2626cb0) at thread/qthread_unix.cpp:331 #8 0x7fb16a4f04a4 in start_thread (arg=0x7fb154e8b700) at pthread_create.c:334 #9 0x7fb16fedcbdd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 1 (Thread 0x7fb178831940 (LWP 2657)): [KCrash Handler] #6 0x7fb170192b98 in main_arena () at /lib64/libc.so.6 #7 0x7fb1592b5329 in QXcbWindow::mapToNative(QRect const&, QXcbScreen const*) const (this=, rect=..., screen=0x2125b80) at qxcbwindow.cpp:203 #8 0x7fb1592bbab3 in QXcbWindow::setGeometry(QRect const&) (this=0x25f3960, rect=...) at qxcbwindow.cpp:732 #9 0x7fb171c91032 in QWidgetPrivate::show_sys() (this=this@entry=0x2221880) at kernel/qwidget.cpp:7889 #10 0x7fb171c99ee6 in QWidgetPrivate::show_helper() (this=this@entry=0x2221880) at kernel/qwidget.cpp:7827 #11 0x7fb171c9c845 in QWidget::setVisible(bool) (this=0x2295ce0, visible=) at kernel/qwidget.cpp:8111 #12 0x7fb171c99c18 in QWidgetPrivate::showChildren(bool) (
[kwin] [Bug 358610] alt-tab dialog flickers if aborted during animation and "Show selected window" is enabled
https://bugs.kde.org/show_bug.cgi?id=358610 Martin Gräßlin changed: What|Removed |Added Status|UNCONFIRMED |CONFIRMED Ever confirmed|0 |1 --- Comment #4 from Martin Gräßlin --- With slow animation speed I'm able to reproduce. My guess is it's a mishandling in either sliding popup or blur effect. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356225] Panel moves to wrong screen when external monitor is connected
https://bugs.kde.org/show_bug.cgi?id=356225 brancaleone changed: What|Removed |Added CC||cedric.devill...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 358624] Plasma Panel stays on disconnected Primary Output
https://bugs.kde.org/show_bug.cgi?id=358624 Malte S. Stretz changed: What|Removed |Added Platform|Other |Ubuntu Packages --- Comment #1 from Malte S. Stretz --- This happens on Kubuntu 15.10 (wily); KDE from the kubuntu-ppa. I notice this because everything worked fine with plasma 4 on Kubuntu 14.04. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 358620] ARM: unhandled syscall: 357
https://bugs.kde.org/show_bug.cgi?id=358620 Tom Hughes changed: What|Removed |Added Summary|WARNING: unhandled syscall: |ARM: unhandled syscall: 357 |357 | CC||t...@compton.nu -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 358624] New: Plasma Panel stays on disconnected Primary Output
https://bugs.kde.org/show_bug.cgi?id=358624 Bug ID: 358624 Summary: Plasma Panel stays on disconnected Primary Output Product: plasmashell Version: 5.5.3 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Multi-screen support Assignee: aleix...@kde.org Reporter: m...@apache.org CC: plasma-b...@kde.org This is probably the same issue as bug 355466 and bug 356608 but I file a new one since the way of getting there is differently. Reproducible: Always Steps to Reproduce: 1. Connect a second monitor to your laptop (HDMI3 below) 2. Set that display as the Primary 3. Configure you Panel to be on that screen 4. Shut down 5. Disconnect the Primary monitor 6. Power up your machine again Actual Results: The panel is lost, probably still on the primary monitor. It is impossible to use desktop unless you know your tricks (eg. how to pull up KRunner). Expected Results: The Panel should be available on the sole available screen (unless otherwise configured). Especially if there's only one panel. When the primary is disconnected, no screen is marked as primary anymore: Screen 0: minimum 8 x 8, current 1600 x 900, maximum 32767 x 32767 LVDS1 connected 1600x900+0+0 (normal left inverted right x axis y axis) 309mm x 174mm 1600x900 60.01*+ 40.00 1440x900 59.89 1368x768 60.00 1360x768 59.8059.96 1152x864 60.00 1280x720 60.00 1024x768 60.00 1024x576 60.00 960x540 60.00 800x600 60.3256.25 864x486 60.00 800x450 60.00 640x480 59.94 720x405 60.00 640x360 60.00 DP1 disconnected (normal left inverted right x axis y axis) DP2 disconnected (normal left inverted right x axis y axis) DP3 disconnected (normal left inverted right x axis y axis) HDMI1 disconnected (normal left inverted right x axis y axis) HDMI2 disconnected (normal left inverted right x axis y axis) HDMI3 disconnected (normal left inverted right x axis y axis) VGA1 disconnected (normal left inverted right x axis y axis) VIRTUAL1 disconnected (normal left inverted right x axis y axis) -- You are receiving this mail because: You are watching all bug changes.
[frameworks-solid] [Bug 358603] unlocking luks encrypted drive gives an error
https://bugs.kde.org/show_bug.cgi?id=358603 --- Comment #1 from Éric Brunet --- I forgot to mention that everything used to work fine on my fedora 21 system (with kde 4), so this is a regression. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 357803] System tray + kf 5.18 = ugly clipper icon
https://bugs.kde.org/show_bug.cgi?id=357803 --- Comment #7 from Anthony --- It's *MUST* be Klipper, but it's device mounter. It's clear now? -- You are receiving this mail because: You are watching all bug changes.
[frameworks-knotifications] [Bug 356523] Hide/restore window from system tray cause change it position
https://bugs.kde.org/show_bug.cgi?id=356523 --- Comment #13 from Anthony --- Any results here? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 344879] memory leak in plasmashell - huge ram usage
https://bugs.kde.org/show_bug.cgi?id=344879 --- Comment #117 from Anthony --- (In reply to painless roaster from comment #113) > Faster test: > - download plasmoid thermal monitor and set: > - refresh speed - 0.1s > - create 5 fields for temperature monitoring (physical id and 4 cores) > - in this test is leak speed is 12MB / minute > > Is any chance for use memory leak profiler please? For example compile > plasma-workspace with library jemalloc and use jeprof. > Valgrind is too slow and not monitor during run. But jemalloc is ideal > library for memory monitoring. I cannot confirm i use it regular since it created, not remember, not leak at all. Tell your graphic driver, mine is radeon, your nvidia? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 356318] I can run wayland plasma session from terminal, not from sddm
https://bugs.kde.org/show_bug.cgi?id=356318 --- Comment #2 from Martin Gräßlin --- > sddm looks freezed and I only have a mouse curser moving does kwin start at all in that case? Are we still on sddm or did KWin take over the session? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 321190] Please re-add mousebutton to close windows in Present Windows
https://bugs.kde.org/show_bug.cgi?id=321190 --- Comment #92 from Martin Gräßlin --- hey all, as you now even point me to the code of conduct: The code of conduct does not force me to write code or to review code. So let me explain why I won't implement it and won't let a feature go back in: because I'm sick of this report. Sick of the behavior expressed by the small number of people here. Sick of the accusations thrown at me. It's a waste of my time to comment on this bug report. I just don't want to have anything to do with it any more. The easiest way would be to just let the feature in again, but I don't make maintainer decisions based on bullying by a small number of people. Everything regarding this bug report has been said. There won't be new information going in and nobody of those wanting the feature back, will accept the arguments we presented. So why should we continue to spend time on it? If you think that this is all badly handled and you think I violate the code of conduct I urge you to contact the community working group. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 357803] System tray + kf 5.18 = ugly clipper icon
https://bugs.kde.org/show_bug.cgi?id=357803 --- Comment #6 from Bhushan Shah --- ??? In comment #1 you said its Clipboard now you say device mounter?? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 357803] System tray + kf 5.18 = ugly clipper icon
https://bugs.kde.org/show_bug.cgi?id=357803 --- Comment #5 from Anthony --- This is not Klipper at all, it's device mounter when click it show status of mounted device in the panel. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 358620] ARM: unhandled syscall: 357
https://bugs.kde.org/show_bug.cgi?id=358620 --- Comment #2 from alexander.ress...@gmail.com --- Yes, it's epol_create1. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 358620] ARM: unhandled syscall: 357
https://bugs.kde.org/show_bug.cgi?id=358620 --- Comment #1 from Tom Hughes --- This is epoll_create1. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 319839] --unique-per-file option
https://bugs.kde.org/show_bug.cgi?id=319839 --- Comment #4 from Jonathan Verner --- (In reply to Walter Rudametkin from comment #3) > Hi, > > Is there anything missing for your patch to be applied? I'd really like to > see this in Okular. > > Regards, It is not fully tested yet (missing unit tests)... If you are brave, you might try downloading Okular's source, applying the patch and building it yourself. I planned to work on it at the end of last year but unfortunately life again got into the way. As it stands, I currently don't have much time, so the chances of me finishing it soon are rather slim :-( Sorry for that. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 358553] "Open recent" entries should be added on file open rather than file close
https://bugs.kde.org/show_bug.cgi?id=358553 --- Comment #3 from Dominik Haumann --- ...or it also could be, that a sync of the kate session is missing. As iirc, the recent files are per session. -- You are receiving this mail because: You are watching all bug changes.
[kinfocenter] [Bug 358623] New: core dumped, when using AMD open source driver
https://bugs.kde.org/show_bug.cgi?id=358623 Bug ID: 358623 Summary: core dumped, when using AMD open source driver Product: kinfocenter Version: 5.5.4 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: major Priority: NOR Component: OpenGL Assignee: hubn...@gmail.com Reporter: ali.sheri...@yahoo.com If I run $ xrandr --setprovideroffloadsink radeon intel then open the program with $ DRI_PRIME=1 kinfocenter, KInfoCenter crashes, after I click on OpenGL. Arch is up to date. Error messsage: Segmentation fault (core dumped) Reproducible: Always Steps to Reproduce: 1. Run xrandr --setprovideroffloadsink radeon intel. 2. Run DRI_PRIME=1 kinfocenter. 3. Click on OpenGL Actual Results: Segmentation fault (core dumped) Expected Results: I see OpenGL data. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 358610] alt-tab dialog flickers if aborted during animation and "Show selected window" is enabled
https://bugs.kde.org/show_bug.cgi?id=358610 --- Comment #3 from Federico Lorenzi --- I posted a link to a Reddit thread: https://www.reddit.com/r/kde/comments/31s438/plasma_52_flickering_on_short_alttab/ that has my original YouTube video showing the problem in Plasma 5.2 ( https://www.youtube.com/watch?v=NJPUF8iT0UY ), as well as a few "me toos". I've taken some new videos now (on the exact machine that the support info is from): Showing the bug (Show selected window enabled): https://www.youtube.com/watch?v=b-05weuHDUM&feature=youtu.be (slow speed) https://www.youtube.com/watch?v=Pa2YjI-ikMA&feature=youtu.be (normal speed) Not showing the bug (Show selected window disabled): https://www.youtube.com/watch?v=n8IZLYs3D0A&feature=youtu.be (normal speed) https://www.youtube.com/watch?v=BF_7qM0-QVA&feature=youtu.be (slow speed) The behavior mirrors what I see exactly (ie, there are no screen recording artifacts). I'm not sure what you mean about the flicker being persistent? It happens every time I alt-tab, but once it has happened (ie, done alt-tabbing) everything is normal. -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 358608] Enable "Print images" kipi plugin
https://bugs.kde.org/show_bug.cgi?id=358608 --- Comment #1 from Boudhayan Gupta --- I don't want to re-enable the KIPI plugin for this, for a few reasons: 1) Eventually KIPI support will be dropped as Purpose matures. 2) Printing is a core feature, we don't want to rely on an external plugin for this. 3) Having two Print actions (one core, one via KIPI) will only confuse users. Not having those additional print settings is a bummer though. Perhaps the way to fix this bug is to try incorporate those features into Spectacle's own print feature? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 358610] alt-tab dialog flickers if aborted during animation and "Show selected window" is enabled
https://bugs.kde.org/show_bug.cgi?id=358610 --- Comment #2 from Federico Lorenzi --- Created attachment 96863 --> https://bugs.kde.org/attachment.cgi?id=96863&action=edit Output of qdbus org.kde.KWin /KWin supportInformation This is the output from my desktop, running the binary Nvidia drivers. However, the exact same problem appears on my laptop (using the open source Intel drivers). Tweaking VSync / Compositor settings don't seem to make a difference (it still happens with XRender compositing). -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 358577] Maintenance tool rebuild thumbnails directory filter not working on video files
https://bugs.kde.org/show_bug.cgi?id=358577 --- Comment #9 from Evert Vorster --- I have QT5 thumbnailer installed. How else would I get the thumbnails in the first place? A little bit of history... DigiKam 4.xx started failing on thumbnails for video recently, and so I installed DigiKam 5.0.0. I re-built my entire data base's thumbnails, and it took many hours. Everything looked to be fine. Then I imported from two sources at once, my wife's phone and an SD card reader. One of the video thumbnails is incorrect in DigiKam only, and shows correct on Dolphin. (5) Refreshing the album does not fix the thumbnail in DigiKam. Using the maintenance tools also does not delete the cached thumbnail. I do not want to delete ALL my thumbnails again, since it will take a very long tie to re-create all of them. It should be easy to delete a thumbnail and let DigiKam re-create it as if it is a new file. Hy, I just found an easy workaround. I navigated to the directory in a console, and just touched the file with bad thumbnail. DigiKam then re-created the thumbnail, and got it right this time. :) -- You are receiving this mail because: You are watching all bug changes.
[kdelibs] [Bug 358622] New: Crash after resume from suspend to disk, unlock screen
https://bugs.kde.org/show_bug.cgi?id=358622 Bug ID: 358622 Summary: Crash after resume from suspend to disk, unlock screen Product: kdelibs Version: unspecified Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: kded Assignee: unassigned-b...@kde.org Reporter: opensuse.lietuviu.ka...@gmail.com Application: kded4 (4.14.9) KDE Platform Version: 4.14.9 Qt Version: 4.8.6 Operating System: Linux 3.16.7-29-desktop x86_64 Distribution: "openSUSE 13.2 (Harlequin) (x86_64)" -- Information about the crash: - What I was doing when the application crashed: I suspend computer to hard disk at evening. In morning I boot computer, Linux system with KDE resumed. I entered password to unlock desktop. I see crash notification. This isfirst time I see such notification. -- Backtrace: Application: KDE tarnyba (kded4), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f06de355780 (LWP 3617))] Thread 4 (Thread 0x7f06b7214700 (LWP 3630)): #0 0x7f06d8a9d337 in g_main_context_prepare () at /usr/lib64/libglib-2.0.so.0 #1 0x7f06d8a9db03 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7f06d8a9dcec in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7f06dcfeb0de in QEventDispatcherGlib::processEvents(QFlags) (this=0x7f06a40008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:452 #4 0x7f06dcfbce6f in QEventLoop::processEvents(QFlags) (this=this@entry=0x7f06b7213e20, flags=...) at kernel/qeventloop.cpp:149 #5 0x7f06dcfbd165 in QEventLoop::exec(QFlags) (this=this@entry=0x7f06b7213e20, flags=...) at kernel/qeventloop.cpp:204 #6 0x7f06dceba0bf in QThread::exec() (this=) at thread/qthread.cpp:538 #7 0x7f06c271a287 in KCupsConnection::run() () at /usr/lib64/libkcupslib.so #8 0x7f06dcebc79f in QThreadPrivate::start(void*) (arg=0x1b34e10) at thread/qthread_unix.cpp:349 #9 0x7f06dcc260a4 in start_thread (arg=0x7f06b7214700) at pthread_create.c:309 #10 0x7f06db99308d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111 Thread 3 (Thread 0x7f06b6a13700 (LWP 3631)): #0 0x7f06dcc2ca9d in read () at ../sysdeps/unix/syscall-template.S:81 #1 0x7f06d8ade750 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7f06d8a9d714 in g_main_context_check () at /usr/lib64/libglib-2.0.so.0 #3 0x7f06d8a9db7b in () at /usr/lib64/libglib-2.0.so.0 #4 0x7f06d8a9dcec in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #5 0x7f06dcfeb0de in QEventDispatcherGlib::processEvents(QFlags) (this=0x7f06940008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:452 #6 0x7f06dcfbce6f in QEventLoop::processEvents(QFlags) (this=this@entry=0x7f06b6a12e60, flags=...) at kernel/qeventloop.cpp:149 #7 0x7f06dcfbd165 in QEventLoop::exec(QFlags) (this=this@entry=0x7f06b6a12e60, flags=...) at kernel/qeventloop.cpp:204 #8 0x7f06dceba0bf in QThread::exec() (this=) at thread/qthread.cpp:538 #9 0x7f06dcebc79f in QThreadPrivate::start(void*) (arg=0x1b20b30) at thread/qthread_unix.cpp:349 #10 0x7f06dcc260a4 in start_thread (arg=0x7f06b6a13700) at pthread_create.c:309 #11 0x7f06db99308d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111 Thread 2 (Thread 0x7f06b6212700 (LWP 3632)): #0 0x7f06db98ac5d in poll () at ../sysdeps/unix/syscall-template.S:81 #1 0x7f06d8a9dbe4 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7f06d8a9dcec in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7f06dcfeb0de in QEventDispatcherGlib::processEvents(QFlags) (this=0x7f068c0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:452 #4 0x7f06dcfbce6f in QEventLoop::processEvents(QFlags) (this=this@entry=0x7f06b6211e20, flags=...) at kernel/qeventloop.cpp:149 #5 0x7f06dcfbd165 in QEventLoop::exec(QFlags) (this=this@entry=0x7f06b6211e20, flags=...) at kernel/qeventloop.cpp:204 #6 0x7f06dceba0bf in QThread::exec() (this=this@entry=0x1cb0090) at thread/qthread.cpp:538 #7 0x7f06dcf9e783 in QInotifyFileSystemWatcherEngine::run() (this=0x1cb0090) at io/qfilesystemwatcher_inotify.cpp:265 #8 0x7f06dcebc79f in QThreadPrivate::start(void*) (arg=0x1cb0090) at thread/qthread_unix.cpp:349 #9 0x7f06dcc260a4 in start_thread (arg=0x7f06b6212700) at pthread_create.c:309 #10 0x7f06db99308d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111 Thread 1 (Thread 0x7f06de355780 (LWP 3617)): [KCrash Handler] #6 0x7f06dcfc4847 in QMetaObject::cast(QObject*) const (this=0x7f06dcc05e60 , obj=0x160) at kernel/qmetaobject.cpp:274 #7 0x7f06dc1fb56e in createWriteHandlerHelper(QIODevice*, QByteArray const&) (object=) at ../../src/corelib/kernel/qobject.h:380 #8 0x7f06dc1fb56e in createWriteHandlerHelper(QIODevice*, QByteArray const&) (device=0x7ffc55d
[kmail2] [Bug 358621] New: crash at first startup after login
https://bugs.kde.org/show_bug.cgi?id=358621 Bug ID: 358621 Summary: crash at first startup after login Product: kmail2 Version: 5.1 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: br...@ioda-net.ch Application: kmail (5.1) Qt Version: 5.5.1 Operating System: Linux 4.4.0-1-default x86_64 Distribution: "openSUSE Tumbleweed (20160121) (x86_64)" -- Information about the crash: - What I was doing when the application crashed: I'm using a global shortcut to launch at the same time korganizer & kmail. Meta+A -> /usr/bin/korganizer & /usr/bin/kmail Immediately this crash is reported, but kmail start and work correctly afterwards. Nvidia drivers : 352.79 double écran hiDPI ( 3840 x 2160 ) The crash can be reproduced sometimes. -- Backtrace: Application: KMail (kmail), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7fc5e318f940 (LWP 3220))] Thread 16 (Thread 0x7fc5bcb4b700 (LWP 3222)): #0 0x7fc5e01d724d in poll () at /lib64/libc.so.6 #1 0x7fc5d3610432 in () at /usr/lib64/libxcb.so.1 #2 0x7fc5d3612007 in xcb_wait_for_event () at /usr/lib64/libxcb.so.1 #3 0x7fc5beea4e29 in () at /usr/lib64/libQt5XcbQpa.so.5 #4 0x7fc5e0adf94f in () at /usr/lib64/libQt5Core.so.5 #5 0x7fc5d6a0f4a4 in start_thread () at /lib64/libpthread.so.0 #6 0x7fc5e01dfbdd in clone () at /lib64/libc.so.6 Thread 15 (Thread 0x7fc5b64fc700 (LWP 3225)): #0 0x7fc5d6a17cfc in __lll_lock_wait () at /lib64/libpthread.so.0 #1 0x7fc5d6a11bb2 in pthread_mutex_lock () at /lib64/libpthread.so.0 #2 0x7fc5d5529fcc in () at /usr/X11R6/lib64/libGL.so.1 #3 0x7fc5d552eb11 in () at /usr/X11R6/lib64/libGL.so.1 #4 0x7fc5d552f018 in () at /usr/X11R6/lib64/libGL.so.1 #5 0x7fc5ca73c001 in () at /usr/lib64/tls/libnvidia-tls.so.352.79 #6 0x7fc5d6534210 in () at /usr/lib64/libglib-2.0.so.0 #7 0x7fc5d64f1d94 in g_main_context_check () at /usr/lib64/libglib-2.0.so.0 #8 0x7fc5d64f2208 in () at /usr/lib64/libglib-2.0.so.0 #9 0x7fc5d64f236c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #10 0x7fc5e0d0452b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #11 0x7fc5e0cae63a in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #12 0x7fc5e0adab1c in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #13 0x7fc5e0adf94f in () at /usr/lib64/libQt5Core.so.5 #14 0x7fc5d6a0f4a4 in start_thread () at /lib64/libpthread.so.0 #15 0x7fc5e01dfbdd in clone () at /lib64/libc.so.6 Thread 14 (Thread 0x7fc5b4e76700 (LWP 3923)): #0 0x7fc5e01d322d in read () at /lib64/libc.so.6 #1 0x7fc5ca73bf75 in () at /usr/lib64/tls/libnvidia-tls.so.352.79 #2 0x7fc5d6534210 in () at /usr/lib64/libglib-2.0.so.0 #3 0x7fc5d64f1d94 in g_main_context_check () at /usr/lib64/libglib-2.0.so.0 #4 0x7fc5d64f2208 in () at /usr/lib64/libglib-2.0.so.0 #5 0x7fc5d64f236c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #6 0x7fc5e0d0452b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #7 0x7fc5e0cae63a in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #8 0x7fc5e0adab1c in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #9 0x7fc5e0adf94f in () at /usr/lib64/libQt5Core.so.5 #10 0x7fc5d6a0f4a4 in start_thread () at /lib64/libpthread.so.0 #11 0x7fc5e01dfbdd in clone () at /lib64/libc.so.6 Thread 13 (Thread 0x7fc5a7fff700 (LWP 3927)): #0 0x7fc5d64f18d1 in g_main_context_prepare () at /usr/lib64/libglib-2.0.so.0 #1 0x7fc5d64f2193 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7fc5d64f236c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7fc5e0d0452b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7fc5e0cae63a in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7fc5e0adab1c in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #6 0x7fc5e0adf94f in () at /usr/lib64/libQt5Core.so.5 #7 0x7fc5d6a0f4a4 in start_thread () at /lib64/libpthread.so.0 #8 0x7fc5e01dfbdd in clone () at /lib64/libc.so.6 Thread 12 (Thread 0x7fc5a77fe700 (LWP 3930)): #0 0x7fc5d6a1507f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fc5d147c3bb in () at /usr/lib64/libQt5WebKit.so.5 #2 0x7fc5d147c3f9 in () at /usr/lib64/libQt5WebKit.so.5 #3 0x7fc5d6a0f4a4 in start_thread () at /lib64/libpthread.so.0 #4 0x7fc5e01dfbdd in clone () at /lib64/libc.so.6 Thread 11 (Thread 0x7fc5b5677700 (LWP 3941)): #0 0x7fc5e01d322d in read () at /lib64/libc.so.6 #1 0x7fc5ca73bf75 in () at /usr/lib64/tls/libnvidi
[valgrind] [Bug 358620] New: WARNING: unhandled syscall: 357
https://bugs.kde.org/show_bug.cgi?id=358620 Bug ID: 358620 Summary: WARNING: unhandled syscall: 357 Product: valgrind Version: 3.7.0 Platform: Debian stable OS: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: memcheck Assignee: jsew...@acm.org Reporter: alexander.ress...@gmail.com I have an ARMv6 Raspberry Pi that I'm compiling and testing a small TCP server on. I'm using the epoll system call in my c/c++ program. The program runs fine when I don't use valgrind. However, when I use valgrind, the call to 'epoll_wait' returns -1, which indicates a kernel level error. This doesn't happen with valgrind and the same program on my typical desktop with an intel i7 cpu. See the results of valgrind below. ==2615== Memcheck, a memory error detector ==2615== Copyright (C) 2002-2011, and GNU GPL'd, by Julian Seward et al. ==2615== Using Valgrind-3.7.0 and LibVEX; rerun with -h for copyright info ==2615== Command: ./src/app/bserver ==2615== --2615-- WARNING: unhandled syscall: 357 --2615-- You may be able to write your own handler. --2615-- Read the file README_MISSING_SYSCALL_OR_IOCTL. --2615-- Nevertheless we consider this a bug. Please report --2615-- it at http://valgrind.org/support/bug_reports.html. --2615-- WARNING: unhandled syscall: 357 --2615-- You may be able to write your own handler. --2615-- Read the file README_MISSING_SYSCALL_OR_IOCTL. --2615-- Nevertheless we consider this a bug. Please report --2615-- it at http://valgrind.org/support/bug_reports.html. disInstr(arm): unhandled instruction: 0xF1010200 cond=15(0xF) 27:20=16(0x10) 4:4=0 3:0=0(0x0) ==2615== valgrind: Unrecognised instruction at address 0x4842588. ==2615==at 0x4842588: ??? (in /usr/lib/arm-linux-gnueabihf/libcofi_rpi.so) ==2615== Your program just tried to execute an instruction that Valgrind ==2615== did not recognise. There are two possible reasons for this. ==2615== 1. Your program has a bug and erroneously jumped to a non-code ==2615==location. If you are running Memcheck and you just saw a ==2615==warning about a bad jump, it's probably your program's fault. ==2615== 2. The instruction is legitimate but Valgrind doesn't handle it, ==2615==i.e. it's Valgrind's fault. If you think this is the case or ==2615==you are not sure, please let us know and we'll try to fix it. ==2615== Either way, Valgrind will now raise a SIGILL signal which will ==2615== probably kill your program. ==2615== ==2615== Process terminating with default action of signal 4 (SIGILL) ==2615== Illegal opcode at address 0x4842588 ==2615==at 0x4842588: ??? (in /usr/lib/arm-linux-gnueabihf/libcofi_rpi.so) ==2615== ==2615== HEAP SUMMARY: ==2615== in use at exit: 44,142 bytes in 302 blocks ==2615== total heap usage: 347 allocs, 45 frees, 48,218 bytes allocated ==2615== ==2615== LEAK SUMMARY: ==2615==definitely lost: 0 bytes in 0 blocks ==2615==indirectly lost: 0 bytes in 0 blocks ==2615== possibly lost: 3,060 bytes in 87 blocks ==2615==still reachable: 41,082 bytes in 215 blocks ==2615== suppressed: 0 bytes in 0 blocks ==2615== Rerun with --leak-check=full to see details of leaked memory ==2615== ==2615== For counts of detected and suppressed errors, rerun with: -v ==2615== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0) Killed -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 358619] New: Moving a layer to the top is annoying
https://bugs.kde.org/show_bug.cgi?id=358619 Bug ID: 358619 Summary: Moving a layer to the top is annoying Product: krita Version: 3.0 Alpha Platform: MS Windows OS: MS Windows Status: UNCONFIRMED Severity: normal Priority: NOR Component: usability Assignee: krita-bugs-n...@kde.org Reporter: zottgram...@gmail.com 1. Have at least 2 layers. Layer 1 and 2, 2 is at the top. 2. Try to click and drag and move Layer 1 above layer 2. There is a 1 pixel window/border where the cursor has to land and release to allow this move. This is a very precise requirement for a simple and common action. It seems to be an inefficient UX. Suggest: Increasing the target size to something like 10pixels or so to make it easier to 'land' on it. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 358618] New: Plasma crashed when closing an application
https://bugs.kde.org/show_bug.cgi?id=358618 Bug ID: 358618 Summary: Plasma crashed when closing an application Product: plasmashell Version: 5.5.3 Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: vhrad...@cfl.rr.com CC: bhus...@gmail.com, plasma-b...@kde.org Application: plasmashell (5.5.3) Qt Version: 5.5.1 Operating System: Linux 4.3.3-301.fc23.x86_64 x86_64 Distribution: "Fedora release 23 (Twenty Three)" -- Information about the crash: I was shutting own for the night and was closing the open applications. I tried to close a Firefox browser and Plasma crashed. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f2235e2f940 (LWP 12480))] Thread 8 (Thread 0x7f2215f02700 (LWP 12484)): #0 0x7f222d816fdd in poll () at /lib64/libc.so.6 #1 0x7f2233cce272 in _xcb_conn_wait () at /lib64/libxcb.so.1 #2 0x7f2233ccfee7 in xcb_wait_for_event () at /lib64/libxcb.so.1 #3 0x7f2217e8cda9 in QXcbEventReader::run() () at /lib64/libQt5XcbQpa.so.5 #4 0x7f222e41f3de in QThreadPrivate::start(void*) () at /lib64/libQt5Core.so.5 #5 0x7f222cb5a60a in start_thread () at /lib64/libpthread.so.0 #6 0x7f222d822a4d in clone () at /lib64/libc.so.6 Thread 7 (Thread 0x7f220f3ea700 (LWP 12503)): #0 0x7f222d816fdd in poll () at /lib64/libc.so.6 #1 0x7f2228d3d16c in g_main_context_iterate.isra () at /lib64/libglib-2.0.so.0 #2 0x7f2228d3d27c in g_main_context_iteration () at /lib64/libglib-2.0.so.0 #3 0x7f222e656ecb in QEventDispatcherGlib::processEvents(QFlags) () at /lib64/libQt5Core.so.5 #4 0x7f222e5fdeca in QEventLoop::exec(QFlags) () at /lib64/libQt5Core.so.5 #5 0x7f222e41a434 in QThread::exec() () at /lib64/libQt5Core.so.5 #6 0x7f2232765b45 in QQmlThreadPrivate::run() () at /lib64/libQt5Qml.so.5 #7 0x7f222e41f3de in QThreadPrivate::start(void*) () at /lib64/libQt5Core.so.5 #8 0x7f222cb5a60a in start_thread () at /lib64/libpthread.so.0 #9 0x7f222d822a4d in clone () at /lib64/libc.so.6 Thread 6 (Thread 0x7f220656d700 (LWP 12504)): #0 0x7f222d816fdd in poll () at /lib64/libc.so.6 #1 0x7f2228d3d16c in g_main_context_iterate.isra () at /lib64/libglib-2.0.so.0 #2 0x7f2228d3d27c in g_main_context_iteration () at /lib64/libglib-2.0.so.0 #3 0x7f222e656ecb in QEventDispatcherGlib::processEvents(QFlags) () at /lib64/libQt5Core.so.5 #4 0x7f222e5fdeca in QEventLoop::exec(QFlags) () at /lib64/libQt5Core.so.5 #5 0x7f222e41a434 in QThread::exec() () at /lib64/libQt5Core.so.5 #6 0x7f2232765b45 in QQmlThreadPrivate::run() () at /lib64/libQt5Qml.so.5 #7 0x7f222e41f3de in QThreadPrivate::start(void*) () at /lib64/libQt5Core.so.5 #8 0x7f222cb5a60a in start_thread () at /lib64/libpthread.so.0 #9 0x7f222d822a4d in clone () at /lib64/libc.so.6 Thread 5 (Thread 0x7f2204b08700 (LWP 12505)): #0 0x7f222d816fdd in poll () at /lib64/libc.so.6 #1 0x7f2228d3d16c in g_main_context_iterate.isra () at /lib64/libglib-2.0.so.0 #2 0x7f2228d3d27c in g_main_context_iteration () at /lib64/libglib-2.0.so.0 #3 0x7f222e656ecb in QEventDispatcherGlib::processEvents(QFlags) () at /lib64/libQt5Core.so.5 #4 0x7f222e5fdeca in QEventLoop::exec(QFlags) () at /lib64/libQt5Core.so.5 #5 0x7f222e41a434 in QThread::exec() () at /lib64/libQt5Core.so.5 #6 0x7f2232765b45 in QQmlThreadPrivate::run() () at /lib64/libQt5Qml.so.5 #7 0x7f222e41f3de in QThreadPrivate::start(void*) () at /lib64/libQt5Core.so.5 #8 0x7f222cb5a60a in start_thread () at /lib64/libpthread.so.0 #9 0x7f222d822a4d in clone () at /lib64/libc.so.6 Thread 4 (Thread 0x7f21ff19a700 (LWP 12506)): #0 0x7f222cb5fb10 in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f22355be514 in QTWTF::TCMalloc_PageHeap::scavengerThread() () at /lib64/libQt5Script.so.5 #2 0x7f22355be559 in () at /lib64/libQt5Script.so.5 #3 0x7f222cb5a60a in start_thread () at /lib64/libpthread.so.0 #4 0x7f222d822a4d in clone () at /lib64/libc.so.6 Thread 3 (Thread 0x7f2177636700 (LWP 12507)): #0 0x7f222d816fdd in poll () at /lib64/libc.so.6 #1 0x7f2228d3d16c in g_main_context_iterate.isra () at /lib64/libglib-2.0.so.0 #2 0x7f2228d3d27c in g_main_context_iteration () at /lib64/libglib-2.0.so.0 #3 0x7f222e656ecb in QEventDispatcherGlib::processEvents(QFlags) () at /lib64/libQt5Core.so.5 #4 0x7f222e5fdeca in QEventLoop::exec(QFlags) () at /lib64/libQt5Core.so.5 #5 0x7f222e41a434 in QThread::exec() () at /lib64/libQt5Core.so.5 #6 0x7f22333138d6 in QQuickPixmapReader::run() () at /lib64/libQt5Quick.so.5 #7 0x7
[kwin] [Bug 344278] deco kcm segfault in KDecoration2::Decoration::update()
https://bugs.kde.org/show_bug.cgi?id=344278 Christoph Feck changed: What|Removed |Added CC||jessetalav...@aol.com --- Comment #112 from Christoph Feck --- *** Bug 358616 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 358616] Crash when trying to change window decorations
https://bugs.kde.org/show_bug.cgi?id=358616 Christoph Feck changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |DUPLICATE --- Comment #1 from Christoph Feck --- *** This bug has been marked as a duplicate of bug 344278 *** -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 358609] ‘Labels’ easily confused with ‘tags’ – new name?
https://bugs.kde.org/show_bug.cgi?id=358609 --- Comment #2 from caulier.gil...@gmail.com --- http://photography.tutsplus.com/tutorials/unlocking-the-power-of-lightroom-color-labels--cms-21876 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 358609] ‘Labels’ easily confused with ‘tags’ – new name?
https://bugs.kde.org/show_bug.cgi?id=358609 caulier.gil...@gmail.com changed: What|Removed |Added CC||caulier.gil...@gmail.com Resolution|--- |INVALID Status|UNCONFIRMED |RESOLVED --- Comment #1 from caulier.gil...@gmail.com --- Labels are tags, technically in digiKam core database, but dedicated for specific tasks. - Color Labels to mark images with customized colored mark in workflow. - Pick Labels to mark wanted images with a flag while sorting. - Rating to mark images with stars after sorting. Tags are text annotation, not a graphical mark. LightRoom (and also other pro photo tools) use also "Labels" terms about graphical marks to apply on images, and "Tags" about text annotations. Gillles Caulier -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 358298] QuickShare plasmoid don't work as share
https://bugs.kde.org/show_bug.cgi?id=358298 Aleix Pol changed: What|Removed |Added Resolution|--- |INVALID Status|UNCONFIRMED |RESOLVED --- Comment #3 from Aleix Pol --- Yes, the functionality changed slightly over the port. If there's a server you especially look forward to, please let us know. (or even better, come up with a patch! :D). If you manage to predictably reproduce the error or find some information, don't hesitate to reopen. -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 350901] krunner segfault might because KDeclarative::QmlObject is NULL
https://bugs.kde.org/show_bug.cgi?id=350901 Leslie Zhai changed: What|Removed |Added Resolution|--- |FIXED Status|UNCONFIRMED |RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 356482] crash on closing help window
https://bugs.kde.org/show_bug.cgi?id=356482 --- Comment #1 from Cobus Carstens --- Created attachment 96862 --> https://bugs.kde.org/attachment.cgi?id=96862&action=edit New crash information added by DrKonqi konsole (15.08.0) using Qt 5.5.1 - What I was doing when the application crashed: I resumed the laptop and plugged in a second screen. -- Backtrace (Reduced): #6 0x7f64aef738ff in QXcbWindow::handleClientMessageEvent(xcb_client_message_event_t const*) () from /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5 #7 0x7f64aef5eadb in QXcbConnection::handleXcbEvent(xcb_generic_event_t*) () from /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5 #8 0x7f64aef5f003 in QXcbConnection::processXcbEvents() () from /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5 #9 0x7f64bd94d7b1 in QObject::event(QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #10 0x7f64be2129dc in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 356482] crash on closing help window
https://bugs.kde.org/show_bug.cgi?id=356482 Cobus Carstens changed: What|Removed |Added CC||cobus.carst...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 348514] Device Notifier missing KDE 4 actions
https://bugs.kde.org/show_bug.cgi?id=348514 Eric S changed: What|Removed |Added CC||subscri...@blackbrook.org --- Comment #1 from Eric S --- Maybe this is distro-specific but all my actions from kde4 are in /usr/share/apps/solid/actions. It seems to me one solution or workaround might be distros handled this. KDE ought to highlight the need for this to the distros in some info prominently provided to them when they get the Plasma 5 sources. -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 358617] New: Crash in krunner due to Qalculate
https://bugs.kde.org/show_bug.cgi?id=358617 Bug ID: 358617 Summary: Crash in krunner due to Qalculate Product: krunner Version: 5.5.3 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: m...@vhanda.in Reporter: volo...@mindspring.com Application: krunner (5.5.3) Qt Version: 5.5.1 Operating System: Linux 4.2.0-25-generic x86_64 Distribution: Ubuntu 15.10 -- Information about the crash: - What I was doing when the application crashed: If I enter =(1C)^2 and then press / the widget crashes. Similar crashes occurred before for incomplete or not fully formed expressions. The crash can be reproduced every time. -- Backtrace: Application: krunner (krunner), signal: Segmentation fault 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 0x7fdd50023800 (LWP 20648))] Thread 19 (Thread 0x7fdd3c363700 (LWP 20649)): #0 0x7fdd4ca818dd in poll () at ../sysdeps/unix/syscall-template.S:81 #1 0x7fdd4bf71bd2 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 #2 0x7fdd4bf7374f in xcb_wait_for_event () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 #3 0x7fdd3e4ac7e9 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5 #4 0x7fdd4d177a6e in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7fdd4acd16aa in start_thread (arg=0x7fdd3c363700) at pthread_create.c:333 #6 0x7fdd4ca8ceed in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 18 (Thread 0x7fdd31d41700 (LWP 20650)): #0 0x7fdd4ca818dd in poll () at ../sysdeps/unix/syscall-template.S:81 #1 0x7fdd4a1521ec in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fdd4a1522fc in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fdd4d3af50b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7fdd4d35650a in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7fdd4d172ac4 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7fdd4eff0c35 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #7 0x7fdd4d177a6e in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7fdd4acd16aa in start_thread (arg=0x7fdd31d41700) at pthread_create.c:333 #9 0x7fdd4ca8ceed in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 17 (Thread 0x7fdd2294a700 (LWP 20651)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7fdd4d178d0b in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #2 0x7fdd2ad6355b in ThreadWeaver::Weaver::blockThreadUntilJobsAreBeingAssigned_locked (this=, th=) at ../../src/weaver.cpp:594 #3 0x7fdd2ad6430f in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait (this=0x215f710, th=th@entry=0x3ed6960, threadWasBusy=threadWasBusy@entry=false, suspendIfInactive=suspendIfInactive@entry=false, justReturning=justReturning@entry=false) at ../../src/weaver.cpp:554 #4 0x7fdd2ad68568 in ThreadWeaver::WorkingHardState::applyForWork (this=0x2864370, th=0x3ed6960, wasBusy=) at ../../src/workinghardstate.cpp:66 #5 0x7fdd2ad634bd in ThreadWeaver::Weaver::applyForWork (this=, th=0x3ed6960, wasBusy=) at ../../src/weaver.cpp:568 #6 0x7fdd2ad685c2 in ThreadWeaver::WorkingHardState::applyForWork (this=0x2864370, th=0x3ed6960, wasBusy=) at ../../src/workinghardstate.cpp:73 #7 0x7fdd2ad634bd in ThreadWeaver::Weaver::applyForWork (this=, th=0x3ed6960, wasBusy=) at ../../src/weaver.cpp:568 #8 0x7fdd2ad663d3 in ThreadWeaver::Thread::run (this=0x3ed6960) at ../../src/thread.cpp:103 #9 0x7fdd4d177a6e in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #10 0x7fdd4acd16aa in start_thread (arg=0x7fdd2294a700) at pthread_create.c:333 #11 0x7fdd4ca8ceed in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 16 (Thread 0x7fdd22149700 (LWP 20652)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7fdd4d178d0b in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #2 0x7fdd2ad6355b in ThreadWeaver::Weaver::blockThreadUntilJobsAreBeingAssigned_locked (this=, th=) at ../../src/weaver.cpp:594 #3 0x7fdd2ad6430f in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait (this=0x215f710, th=th@entry=0x3ee6de0, threadWasBusy=threadWasBusy@entry=false, suspendIfInactive=suspendIfInactive@entry=false, justReturning=justReturning@entry=false) at ../../src/weaver.cpp:554 #4 0x7fdd2ad68568 in ThreadWeaver::Working
[plasmashell] [Bug 357803] System tray + kf 5.18 = ugly clipper icon
https://bugs.kde.org/show_bug.cgi?id=357803 Bhushan Shah changed: What|Removed |Added CC||bhus...@gmail.com --- Comment #4 from Bhushan Shah --- @David: I think yes, it sometimes happen that klipper expands itself in system tray and not dialog. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 357726] volume indicator and wifi quality are too hard to read
https://bugs.kde.org/show_bug.cgi?id=357726 Eric S changed: What|Removed |Added CC||subscri...@blackbrook.org --- Comment #1 from Eric S --- I second this! And it is still the case with 5.5.3. This flaw does falls out of the decision to make such icons monochrome in breeze. I'm not fond of that at all. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 328593] Dual screen has regressed in plasma-shell
https://bugs.kde.org/show_bug.cgi?id=328593 Martin Klapetek changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |UNMAINTAINED --- Comment #5 from Martin Klapetek --- This bug seems quite outdated. Multi-screen issues are now tracked in the Multi-Screen component and this has no use anymore as its purpose was to track regressions for the first release. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 346181] K menu, context menus, system tray popups not displayed (or displayed off-screen) after an external monitor is plugged in
https://bugs.kde.org/show_bug.cgi?id=346181 Martin Klapetek changed: What|Removed |Added Status|UNCONFIRMED |CONFIRMED Ever confirmed|0 |1 CC||mklape...@kde.org --- Comment #12 from Martin Klapetek --- I have this issue now too. Plasma popups appear on the wrong screen, sometimes don't appear at all. -- You are receiving this mail because: You are watching all bug changes.
[plasma4] [Bug 310156] Windows go below when "Always visible" is set and using multihead
https://bugs.kde.org/show_bug.cgi?id=310156 --- Comment #10 from Eric S --- Oops, nevermind, there already is a Plasma 5 version of this: 348043 -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 358298] QuickShare plasmoid don't work as share
https://bugs.kde.org/show_bug.cgi?id=358298 --- Comment #2 from SinClaus --- Today QS uploads picture and return link, but it don't have any config option to select share server (as in KDE 4) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 348043] Maximized windows are covered by plasma panel in "always visible mode".
https://bugs.kde.org/show_bug.cgi?id=348043 Eric S changed: What|Removed |Added CC||subscri...@blackbrook.org --- Comment #14 from Eric S --- This is still the case in Plasma 5.5.3. Shouldn't someone update the version? -- You are receiving this mail because: You are watching all bug changes.
[plasma4] [Bug 310156] Windows go below when "Always visible" is set and using multihead
https://bugs.kde.org/show_bug.cgi?id=310156 Eric S changed: What|Removed |Added CC||subscri...@blackbrook.org --- Comment #9 from Eric S --- Still happening in Plasma 5.5.3. Btw this seems to have been fixed in Plasma 4...it worked properly in the last several versions I'd used. Could someone update the product and version fields to reflect that? Or does this need to be refiled for Plamsa 5? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 357917] Tabbing away from mail finishing being send in Thunderbird, windows loose decorations
https://bugs.kde.org/show_bug.cgi?id=357917 Martin Klapetek changed: What|Removed |Added Target Milestone|1.0 |--- Product|plasmashell |kwin Summary|Tabbing away from mail |Tabbing away from mail |finishing being send in |finishing being send in |Thunderbird, crashes Plasma |Thunderbird, windows loose ||decorations Component|general |general CC||mklape...@kde.org Assignee|k...@davidedmundson.co.uk|kwin-bugs-n...@kde.org --- Comment #1 from Martin Klapetek --- Thanks for the report The issue you describe seems like KWin is actually crashing. The Plasma crash you see on reboot seems unrelated. In any case, please try updating your Qt to 5.5.x which is available for *buntu and see if that helps. In our experience it helps a lot with crashes like these. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 357962] Some features in notification area may crash plasmashell
https://bugs.kde.org/show_bug.cgi?id=357962 Martin Klapetek changed: What|Removed |Added Status|UNCONFIRMED |NEEDSINFO Resolution|--- |WAITINGFORINFO CC||mklape...@kde.org --- Comment #1 from Martin Klapetek --- Thanks for the report Can you please describe what were you doing when this crash occured? -- You are receiving this mail because: You are watching all bug changes.
[kalgebra] [Bug 358451] Constants are not graphed correctly
https://bugs.kde.org/show_bug.cgi?id=358451 --- Comment #3 from resplin --- That makes sense and is very useful. A few suggestions: * It should be documented on the "Syntax" page of the manual. * x=5 and y=5 should return a syntax error instead of an incorrect result. * Syntax errors should point people at the Syntax page of the manual. Thanks. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 358156] Clock doesn't update after switching back from tty
https://bugs.kde.org/show_bug.cgi?id=358156 Martin Klapetek changed: What|Removed |Added Resolution|--- |DUPLICATE Status|UNCONFIRMED |RESOLVED --- Comment #5 from Martin Klapetek --- *** This bug has been marked as a duplicate of bug 356290 *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356290] Digital Clock doesn't render all digits
https://bugs.kde.org/show_bug.cgi?id=356290 Martin Klapetek changed: What|Removed |Added CC||fker...@gmail.com --- Comment #6 from Martin Klapetek --- *** Bug 358156 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 355528] Multiple monitor support is erratic
https://bugs.kde.org/show_bug.cgi?id=355528 --- Comment #9 from Eric S --- Also, it's frustrating not to be able to vote for this. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 355528] Multiple monitor support is erratic
https://bugs.kde.org/show_bug.cgi?id=355528 Eric S changed: What|Removed |Added CC||subscri...@blackbrook.org --- Comment #8 from Eric S --- "Erratic" is putting it nicely. How about "fundementally broken." -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 357567] Ksudoku
https://bugs.kde.org/show_bug.cgi?id=357567 Martin Klapetek changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED CC||mklape...@kde.org Resolution|--- |DUPLICATE --- Comment #1 from Martin Klapetek --- Thanks for the report This is a crash in your graphics driver, please upgrade or downgrade your driver. Some helpful info may be in here - https://bugs.freedesktop.org/show_bug.cgi?id=92504 *** This bug has been marked as a duplicate of bug 355150 *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 355150] Plasma crashes repeatedly after login
https://bugs.kde.org/show_bug.cgi?id=355150 --- Comment #6 from Martin Klapetek --- *** Bug 357567 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 357507] Crash when checling properties of desktop folder entry
https://bugs.kde.org/show_bug.cgi?id=357507 Martin Klapetek changed: What|Removed |Added Component|general |Task Manager Status|UNCONFIRMED |NEEDSINFO Assignee|k...@davidedmundson.co.uk|h...@kde.org Resolution|--- |BACKTRACE CC||mklape...@kde.org --- Comment #1 from Martin Klapetek --- Thanks for the report Can you reproduce this crash? This looks like a completly random one but if you can reliably reproduce it, please install debug symbols for libKF5WindowSystem package, reproduce the crash and post updated backtrace Thanks -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 358616] New: Crash when trying to change window decorations
https://bugs.kde.org/show_bug.cgi?id=358616 Bug ID: 358616 Summary: Crash when trying to change window decorations Product: systemsettings Version: 5.4.1 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: jessetalav...@aol.com Application: systemsettings5 (5.4.1) Qt Version: 5.4.2 Operating System: Linux 4.2.0-25-generic x86_64 Distribution: Ubuntu 15.10 -- Information about the crash: The application crashes when I try to change the window decorations. The crash can be reproduced sometimes. -- Backtrace: Application: System Settings (systemsettings5), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f1791f6a800 (LWP 13344))] Thread 4 (Thread 0x7f1780ae9700 (LWP 13345)): #0 0x7f178e7128dd in poll () at ../sysdeps/unix/syscall-template.S:81 #1 0x7f178c422bd2 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 #2 0x7f178c42474f in xcb_wait_for_event () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 #3 0x7f1783037a39 in QXcbEventReader::run (this=0x2484270) at qxcbconnection.cpp:1105 #4 0x7f178ee052be in QThreadPrivate::start (arg=0x2484270) at thread/qthread_unix.cpp:337 #5 0x7f178bbad6aa in start_thread (arg=0x7f1780ae9700) at pthread_create.c:333 #6 0x7f178e71deed in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 3 (Thread 0x7f17708bf700 (LWP 14575)): #0 0x7f178e7128dd in poll () at ../sysdeps/unix/syscall-template.S:81 #1 0x7f178b68e1ec in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f178b68e2fc in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f178f03c29b in QEventDispatcherGlib::processEvents (this=0x7f176c0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420 #4 0x7f178efe275a in QEventLoop::exec (this=this@entry=0x7f17708beda0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #5 0x7f178ee003d4 in QThread::exec (this=) at thread/qthread.cpp:503 #6 0x7f178d789f85 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #7 0x7f178ee052be in QThreadPrivate::start (arg=0x2af6a10) at thread/qthread_unix.cpp:337 #8 0x7f178bbad6aa in start_thread (arg=0x7f17708bf700) at pthread_create.c:333 #9 0x7f178e71deed in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 2 (Thread 0x7f1768b28700 (LWP 14663)): #0 0x7f178eddc500 in g_main_context_iteration@plt () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #1 0x7f178f03c29b in QEventDispatcherGlib::processEvents (this=0x7f17640008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420 #2 0x7f178efe275a in QEventLoop::exec (this=this@entry=0x7f1768b27da0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #3 0x7f178ee003d4 in QThread::exec (this=) at thread/qthread.cpp:503 #4 0x7f178d789f85 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #5 0x7f178ee052be in QThreadPrivate::start (arg=0x2e1e5f0) at thread/qthread_unix.cpp:337 #6 0x7f178bbad6aa in start_thread (arg=0x7f1768b28700) at pthread_create.c:333 #7 0x7f178e71deed in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 1 (Thread 0x7f1791f6a800 (LWP 13344)): [KCrash Handler] #6 0x7f1770d08917 in KDecoration2::Decoration::update(QRect const&) () from /usr/lib/x86_64-linux-gnu/libkdecorations2.so.5 #7 0x7f1770d089bb in KDecoration2::Decoration::update() () from /usr/lib/x86_64-linux-gnu/libkdecorations2.so.5 #8 0x7f1769250275 in Oxygen::Decoration::setOpacity (this=this@entry=0x2d89f20, value=) at ../../kdecoration/oxygendecoration.cpp:94 #9 0x7f176926a2c8 in Oxygen::Decoration::qt_metacall (this=0x2d89f20, _c=QMetaObject::WriteProperty, _id=0, _a=0x7fffc5e71a70) at moc_oxygendecoration.cpp:155 #10 0x7f178ede630a in QPropertyAnimationPrivate::updateProperty (newValue=..., this=0x2dc8800) at animation/qpropertyanimation.cpp:135 #11 QPropertyAnimation::updateCurrentValue (this=, value=...) at animation/qpropertyanimation.cpp:242 #12 0x7f178ede2318 in QVariantAnimationPrivate::setCurrentValueForProgress (this=this@entry=0x2dc8800, progress=progress@entry=0.91451) at animation/qvariantanimation.cpp:290 #13 0x7f178ede2a17 in QVariantAnimationPrivate::recalculateCurrentInterval (this=0x2dc8800, force=) at animation/qvariantanimation.cpp:275 #14 0x7f178eddf42f in QAbstractAnimation::setCurrentTime (this=0x2dbe120, msecs=119) at animation/qabstractanimation.cpp:1321 #15 0x7f178eddf72d in QAnimationTimer::updateAnimationsTime (delta=31, this=0x2644160) at animation/qabstractanimation.cpp:606 #16 QUnifiedTimer::updateAnimationTimers (this=0x25f7b20) at animation/qabstractanimation.cpp:323 #17 0x7f178d7c
[plasmashell] [Bug 357554] Plasma Krasch when using LibreOffice Calc
https://bugs.kde.org/show_bug.cgi?id=357554 Martin Klapetek changed: What|Removed |Added Assignee|k...@davidedmundson.co.uk|h...@kde.org CC||mklape...@kde.org Component|general |Task Manager --- Comment #1 from Martin Klapetek --- Thanks for the report As a first step, please try updating your Qt to 5.5.x, it greatly improves Plasma's functionality and it should be available for *buntu already. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356225] Panel moves to wrong screen when external monitor is connected
https://bugs.kde.org/show_bug.cgi?id=356225 Martin Klapetek changed: What|Removed |Added CC||lutz.wr...@gmail.com --- Comment #9 from Martin Klapetek --- *** Bug 358220 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 358220] Default panel shown on secondary output
https://bugs.kde.org/show_bug.cgi?id=358220 Martin Klapetek changed: What|Removed |Added CC||mklape...@kde.org Resolution|--- |DUPLICATE Status|UNCONFIRMED |RESOLVED --- Comment #1 from Martin Klapetek --- *** This bug has been marked as a duplicate of bug 356225 *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 358211] Plasma crash when re-activating screen
https://bugs.kde.org/show_bug.cgi?id=358211 Martin Klapetek changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |UNCONFIRMED --- Comment #2 from Martin Klapetek --- Oh sorry, overlooked it at the top of your comment. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 358211] Plasma crash when re-activating screen
https://bugs.kde.org/show_bug.cgi?id=358211 Martin Klapetek changed: What|Removed |Added Resolution|--- |WAITINGFORINFO CC||mklape...@kde.org Status|UNCONFIRMED |NEEDSINFO --- Comment #1 from Martin Klapetek --- Thanks for the report What's your Qt version? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 358351] plasma crashes when manipulating with systray
https://bugs.kde.org/show_bug.cgi?id=358351 Martin Klapetek changed: What|Removed |Added Component|general |System Tray Assignee|k...@davidedmundson.co.uk|plasma-b...@kde.org CC||mklape...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356225] Panel moves to wrong screen when external monitor is connected
https://bugs.kde.org/show_bug.cgi?id=356225 Martin Klapetek changed: What|Removed |Added CC||sigmadraco...@gmail.com --- Comment #8 from Martin Klapetek --- *** Bug 354386 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 354386] System tray panel changes to secondary monitor that is on top/above on dual-monitor config
https://bugs.kde.org/show_bug.cgi?id=354386 Martin Klapetek changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED CC||mklape...@kde.org Resolution|--- |DUPLICATE --- Comment #10 from Martin Klapetek --- *** This bug has been marked as a duplicate of bug 356225 *** -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 346118] Plasmashell crash when disconnecting/reconnecting my WiFi connection after changing MTU
https://bugs.kde.org/show_bug.cgi?id=346118 David Edmundson changed: What|Removed |Added CC||benk...@gmail.com --- Comment #38 from David Edmundson --- *** Bug 358613 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 358615] New: Quick link's Icon not shown at certain size / zoom level
https://bugs.kde.org/show_bug.cgi?id=358615 Bug ID: 358615 Summary: Quick link's Icon not shown at certain size / zoom level Product: kde Version: 4.13.3 Platform: Kubuntu Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: st...@murcsack.de On my desktop I have a folder view widget, which contains several quick links (*.desktop). All of these quick links have custom images set as their icons. I noticed that when the quick links / icons have a certain size, some of them are not shown. This behaviour is also observable in Dolphin. If I change the zoom/size (CTRL + mouse wheel scrolling), the icons disappear at a certain zoom level. Reproducible: Always Steps to Reproduce: Desktop Folder View Widget 1. Create own icon 2. Select icon for quicklink 3. Go to folder widget settings 4. Change icon size Dolphin 1. Open folder contain quick links 2. Zoom in/out using CTRL + mouse wheel Actual Results: Icons disappear at certain zoom level / size Expected Results: Icons are shown at all sizes. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 358019] [Session Management] Some application wont exit properly
https://bugs.kde.org/show_bug.cgi?id=358019 Martin Klapetek changed: What|Removed |Added Resolution|--- |WAITINGFORINFO CC||mklape...@kde.org Status|UNCONFIRMED |RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 358019] [Session Management] Some application wont exit properly
https://bugs.kde.org/show_bug.cgi?id=358019 Martin Klapetek changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Ever confirmed|0 |1 Status|RESOLVED|REOPENED --- Comment #5 from Martin Klapetek --- Wrong status, sorry. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 358019] [Session Management] Some application wont exit properly
https://bugs.kde.org/show_bug.cgi?id=358019 --- Comment #4 from Martin Klapetek --- Can anyone else confirm that Kate is fixed with 15.12 please? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 341143] Wallpaper on every desktop is gone.
https://bugs.kde.org/show_bug.cgi?id=341143 --- Comment #169 from Fraser_Bell --- Wow! Thank you so much, David. Some of us (most?) do appreciate your willingness to remain involved in this. If you have any idea how I might be able to help with this, contact me. -Gerry (In reply to David Edmundson from comment #167) > Update: > > I met with Martin G (kwin maintainer) and Marco to come up with a solid plan > moving forward. > > - We make ShellClient virtual desktops contain an ID not merely a stack > index. > > - ShellClient VD cardinality is changed to match activities. > > - DesktopGrid Effect gets rewritten in QtQuick (we need a change in there > for the cardinality changes, and Martin G has had a rule since 2014 that it > needs a rewrite before any edits..) > > - I invert the DesktopView mapping logic in ShellCorona from Activity -> > Physical Screen to Physical Screen -> Activity. (possibly refactoring into > ScreenCorona class: Rule of Dave - if you have nested maps, you're missing a > class.) > > - KWin activity code gets dropped completely. > > - 1 DesktopView is created per VD. > > Bam everyone wins, and we get this feature without any config migrations > needed. > Will take some time, so please continue to be patient. > > Note: This is a bug tracker for devs, not a public forum. > I do not want to be flooded with off topic comments. It makes my job harder, > as I need to find my notes. Do so and I will close this bug. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 358019] [Session Management] Some application wont exit properly
https://bugs.kde.org/show_bug.cgi?id=358019 Martin Klapetek changed: What|Removed |Added CC||valorie.zimmer...@gmail.com --- Comment #3 from Martin Klapetek --- *** Bug 358344 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 358344] Whenever I restart, there are 3 copies of Kate (empty) and 3 copies of Zanshin on my desktop
https://bugs.kde.org/show_bug.cgi?id=358344 Martin Klapetek changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED CC||mklape...@kde.org Resolution|--- |DUPLICATE --- Comment #1 from Martin Klapetek --- *** This bug has been marked as a duplicate of bug 358019 *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 358102] New method to re-size and move widgets is not intuitive, as is discovering the configuration option.
https://bugs.kde.org/show_bug.cgi?id=358102 Martin Klapetek changed: What|Removed |Added Resolution|--- |WAITINGFORINFO CC||h...@kde.org, ||mklape...@kde.org Status|UNCONFIRMED |NEEDSINFO --- Comment #1 from Martin Klapetek --- Thanks for the report All applets should have the handle pop up on left-mouse button long-press. Can you verify that is not the case? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 341143] Wallpaper on every desktop is gone.
https://bugs.kde.org/show_bug.cgi?id=341143 --- Comment #168 from Michael Fox --- You should make Walk Through Desktops do this http://az648995.vo.msecnd.net/win/2015/04/Clip3.gif or something similar that makes dragging between desktops easier. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 344365] Panel and task switcher appear on the wrong display.
https://bugs.kde.org/show_bug.cgi?id=344365 Martin Klapetek changed: What|Removed |Added CC||mklape...@kde.org Resolution|--- |DUPLICATE Status|UNCONFIRMED |RESOLVED --- Comment #7 from Martin Klapetek --- *** This bug has been marked as a duplicate of bug 356225 *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356225] Panel moves to wrong screen when external monitor is connected
https://bugs.kde.org/show_bug.cgi?id=356225 Martin Klapetek changed: What|Removed |Added CC||abhina...@gmail.com --- Comment #7 from Martin Klapetek --- *** Bug 344365 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356225] Panel moves to wrong screen when external monitor is connected
https://bugs.kde.org/show_bug.cgi?id=356225 Martin Klapetek changed: What|Removed |Added CC||mklape...@kde.org Assignee|plasma-b...@kde.org |aleix...@kde.org Component|Panel |Multi-screen support -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 358614] New: kmail always opens links with konqueror
https://bugs.kde.org/show_bug.cgi?id=358614 Bug ID: 358614 Summary: kmail always opens links with konqueror Product: kmail2 Version: unspecified Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: commands and actions Assignee: kdepim-b...@kde.org Reporter: seanmcne...@gmail.com When any message has a URL and it is clicked on, kmail does not honor the settings for the default component web browser. It always uses konqueror. Reproducible: Always Steps to Reproduce: 1. In Settings, change default Web Browser app to google-chrome 2. Open email with a URL link 3. Click on link. Actual Results: Konqueror starts and views the URL. Expected Results: URL should be handled by google-chrome. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 358262] time dataEngine has empty Local source
https://bugs.kde.org/show_bug.cgi?id=358262 Martin Klapetek changed: What|Removed |Added CC||mklape...@kde.org, ||plasma-b...@kde.org Assignee|plasma-b...@kde.org |mklape...@kde.org Resolution|--- |WAITINGFORINFO Status|UNCONFIRMED |NEEDSINFO Component|DataEngines |Digital Clock --- Comment #1 from Martin Klapetek --- Thanks for the report Can you please tell me your Qt version and also look if you have a TZ env var set and tell me to what, if you do. -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 358320] Password query on every network connection fail
https://bugs.kde.org/show_bug.cgi?id=358320 Martin Klapetek changed: What|Removed |Added Component|general |general Target Milestone|1.0 |--- Product|plasmashell |plasma-nm Assignee|k...@davidedmundson.co.uk|lu...@kde.org CC||jgrul...@redhat.com, ||mklape...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 358473] Plasma shows more then one notif. if you have multiple activities
https://bugs.kde.org/show_bug.cgi?id=358473 --- Comment #1 from Martin Klapetek --- Thanks for the report It shows once for every activity obviously, which it probably shouldn't. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 357085] Unplug VGA output then plug again and plasmashell segfaults
https://bugs.kde.org/show_bug.cgi?id=357085 Martin Klapetek changed: What|Removed |Added CC||mklape...@kde.org Summary|plugout VGA output then |Unplug VGA output then plug |plugin plasmashell segfault |again and plasmashell ||segfaults -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 358613] networkmanager causes plasma crash
https://bugs.kde.org/show_bug.cgi?id=358613 David Edmundson changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |DUPLICATE --- Comment #1 from David Edmundson --- *** This bug has been marked as a duplicate of bug 346118 *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 358613] New: networkmanager causes plasma crash
https://bugs.kde.org/show_bug.cgi?id=358613 Bug ID: 358613 Summary: networkmanager causes plasma crash Product: plasmashell Version: 5.5.3 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: benk...@gmail.com CC: bhus...@gmail.com, plasma-b...@kde.org Application: plasmashell (5.5.3) Qt Version: 5.5.1 Operating System: Linux 4.4.0-1-default x86_64 Distribution: "openSUSE Tumbleweed (20160117) (x86_64)" -- Information about the crash: - What I was doing when the application crashed: I have a poorly functioning wifi dongle that occasionally overheats and stops working. Most of the time it works, but occasionally when it overheats and NM is trying to connect to a network at that time, Plasma crashes. It's possible that due to the occasional restarts of the dongle NM / the kernel may have listed the dongle twice. Plasma certainly showed two different wifi devices I could attempt to connect with when this crash occurred. I'm not really interested in trying to make this dongle work better - it's poorly designed and nothing can help that. I just don't want Plasma to crash, regardless of what the devices attached to the system do. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f61c54d2900 (LWP 25680))] Thread 25 (Thread 0x7f61ad171700 (LWP 25683)): #0 0x7f61bea4c24d in poll () at /lib64/libc.so.6 #1 0x7f61c3922432 in () at /usr/lib64/libxcb.so.1 #2 0x7f61c3924007 in xcb_wait_for_event () at /usr/lib64/libxcb.so.1 #3 0x7f61af8f1e29 in () at /usr/lib64/libQt5XcbQpa.so.5 #4 0x7f61bf13d94f in () at /usr/lib64/libQt5Core.so.5 #5 0x7f61be2534a4 in start_thread () at /lib64/libpthread.so.0 #6 0x7f61bea54bdd in clone () at /lib64/libc.so.6 Thread 24 (Thread 0x7f61a5fe2700 (LWP 25695)): #0 0x7f61bea4c24d in poll () at /lib64/libc.so.6 #1 0x7f61bb140264 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7f61bb14036c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7f61bf36252b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7f61bf30c63a in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7f61bf138b1c in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #6 0x7f61c24089a5 in () at /usr/lib64/libQt5Qml.so.5 #7 0x7f61bf13d94f in () at /usr/lib64/libQt5Core.so.5 #8 0x7f61be2534a4 in start_thread () at /lib64/libpthread.so.0 #9 0x7f61bea54bdd in clone () at /lib64/libc.so.6 Thread 23 (Thread 0x7f61993b8700 (LWP 25696)): #0 0x7f61bea4822d in read () at /lib64/libc.so.6 #1 0x7f61b61eaf75 in () at /usr/lib64/nvidia/tls/libnvidia-tls.so.352.63 #2 0x7f61bb182210 in () at /usr/lib64/libglib-2.0.so.0 #3 0x7f61bb13fd94 in g_main_context_check () at /usr/lib64/libglib-2.0.so.0 #4 0x7f61bb140208 in () at /usr/lib64/libglib-2.0.so.0 #5 0x7f61bb14036c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #6 0x7f61bf36252b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #7 0x7f61bf30c63a in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #8 0x7f61bf138b1c in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #9 0x7f61c24089a5 in () at /usr/lib64/libQt5Qml.so.5 #10 0x7f61bf13d94f in () at /usr/lib64/libQt5Core.so.5 #11 0x7f61be2534a4 in start_thread () at /lib64/libpthread.so.0 #12 0x7f61bea54bdd in clone () at /lib64/libc.so.6 Thread 22 (Thread 0x7f6193a72700 (LWP 25697)): #0 0x7f61bea4c24d in poll () at /lib64/libc.so.6 #1 0x7f61bb140264 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7f61bb14036c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7f61bf36252b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7f61bf30c63a in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7f61bf138b1c in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #6 0x7f61c24089a5 in () at /usr/lib64/libQt5Qml.so.5 #7 0x7f61bf13d94f in () at /usr/lib64/libQt5Core.so.5 #8 0x7f61be2534a4 in start_thread () at /lib64/libpthread.so.0 #9 0x7f61bea54bdd in clone () at /lib64/libc.so.6 Thread 21 (Thread 0x7f6191cde700 (LWP 25698)): #0 0x7f61be25907f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f61c4bb0a84 in () at /usr/lib64/libQt5Script.so.5 #2 0x7f61c4bb0ac9 in () at /usr/lib64/libQt5Script.so.5 #3 0x7f61be2534a4 in start_thread () at /lib64/libpthread.so.0 #4 0x7f61bea54bdd in clone () at /lib64/libc.so.6 Thread 20 (Thread 0x7f610b008700 (LWP 25699)): #
[kalarm] [Bug 358217] Occasional crash on startup
https://bugs.kde.org/show_bug.cgi?id=358217 --- Comment #5 from David Jarvie --- Preferably reopen this bug rather than a new one if you see the problem again. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356854] Tray Icons don't follow user settings customization
https://bugs.kde.org/show_bug.cgi?id=356854 --- Comment #5 from gotokrik...@gmail.com --- The framework version is 5.13 -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 358602] Do not open twice the same document
https://bugs.kde.org/show_bug.cgi?id=358602 Christoph Feck changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=319839 -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 319839] --unique-per-file option
https://bugs.kde.org/show_bug.cgi?id=319839 Christoph Feck changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=358602 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 358232] When Plasmashell is restarted after a crash formerly opened konsole windows cannot be accessed via the Panel anymore
https://bugs.kde.org/show_bug.cgi?id=358232 --- Comment #9 from Thomas Abraham --- Yes, I am sure it is still running. 'ps auxw|grep konsole' shows activities. When quitting KDE itself I'm asked to close running konsole windows without giving me the chance to view them. Sad but true. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 358369] Plasma crashed after opening an HTML5 video in Chrome
https://bugs.kde.org/show_bug.cgi?id=358369 --- Comment #10 from superrobowiz...@gmail.com --- So I'm stuck with a theme I don't like or a theme that crashes my window manager occasionally. This doesn't sound like a good deal to me. Does only the desktop theme matter, only the window borders matter, or both? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356479] plasmashell uses 100% CPU when there is an animation in the task bar
https://bugs.kde.org/show_bug.cgi?id=356479 --- Comment #8 from AnAkkk --- This doesn't seem to fix the issue. I mean, when there is any animation, it seems to use at least 15% CPU constantly. I don't currently have time to wait longer to see if it increase to 100% over time like it did before. Will keep octopi notifier enabled and report back. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 358555] kconsole's background is transparent on second screen
https://bugs.kde.org/show_bug.cgi?id=358555 Ian Pilcher changed: What|Removed |Added CC||arequip...@gmail.com --- Comment #1 from Ian Pilcher --- I am also seeing this on Fedora 23, also with both AMD and Intel graphics. One thing that I did notice is that the shell does appear to be running in the konsole, even though it isn't visible. If one blindly starts an application (such as top) and then clicks on the close button, the "Confirm Close" dialog will pop up. So this seems like it may be more of a rendering/compositing issue (but I'm not sure if that actually helps). -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 358427] 15.13 git master: monitor audio levels have no indicators for 0, -5, -10, -20 dB
https://bugs.kde.org/show_bug.cgi?id=358427 --- Comment #17 from Jean-Baptiste Mardelle --- Git commit 723a8b8fa9d8c0c0c8cfebd2b7cbe027a2d071d4 by Jean-Baptiste Mardelle. Committed on 27/01/2016 at 00:13. Pushed by mardelle into branch 'master'. Refactor new audio levels, should fix most problems. M +1-1src/audiospectrum/audiographspectrum.h M +1-2src/monitor/CMakeLists.txt M +6-73 src/monitor/glwidget.cpp M +2-5src/monitor/glwidget.h M +18 -10 src/monitor/monitor.cpp M +3-7src/monitor/monitor.h A +6-0src/monitor/scopes/CMakeLists.txt A +162 -0src/monitor/scopes/dataqueue.h [License: GPL (v3+)] A +201 -0src/monitor/scopes/monitoraudiolevel.cpp [License: GPL] A +60 -0src/monitor/scopes/monitoraudiolevel.h [License: GPL] A +95 -0src/monitor/scopes/scopewidget.cpp [License: GPL (v3+)] A +129 -0src/monitor/scopes/scopewidget.h [License: GPL (v3+)] A +209 -0src/monitor/scopes/sharedframe.cpp [License: GPL (v3+)] A +77 -0src/monitor/scopes/sharedframe.h [License: GPL (v3+)] M +1-2src/renderer.cpp http://commits.kde.org/kdenlive/723a8b8fa9d8c0c0c8cfebd2b7cbe027a2d071d4 -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 355190] copy current date/time into clipboard
https://bugs.kde.org/show_bug.cgi?id=355190 Reuben Peterkin changed: What|Removed |Added CC||reube...@yahoo.com -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 358268] Quickshare right-click => black screen
https://bugs.kde.org/show_bug.cgi?id=358268 --- Comment #1 from Aleix Pol --- Does it always happen? I need some way to reproduce... -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 358298] QuickShare plasmoid don't work as share
https://bugs.kde.org/show_bug.cgi?id=358298 --- Comment #1 from Aleix Pol --- Do you know the error? Does it happen every time? -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 358298] QuickShare plasmoid don't work as share
https://bugs.kde.org/show_bug.cgi?id=358298 Aleix Pol changed: What|Removed |Added Summary|Quick share plasmoid don't |QuickShare plasmoid don't |work as share |work as share -- You are receiving this mail because: You are watching all bug changes.
[kalgebra] [Bug 358451] Constants are not graphed correctly
https://bugs.kde.org/show_bug.cgi?id=358451 Aleix Pol changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |CONFIRMED --- Comment #2 from Aleix Pol --- the way to do this is by passing x->5. I won't close the bug just yet, but that's how the language was designed. -- You are receiving this mail because: You are watching all bug changes.
