[Spectacle] [Bug 356831] cannot send image to clipboard in background mode
https://bugs.kde.org/show_bug.cgi?id=356831 --- Comment #2 from dantmnf --- It's a bad news :-( Can you add a "instant copy" option to GUI mode? -- You are receiving this mail because: You are watching all bug changes.
[Baloo] [Bug 356890] Digikam crashed always when try to rotate picture
https://bugs.kde.org/show_bug.cgi?id=356890 caulier.gil...@gmail.com changed: What|Removed |Added Version|4.13.0 |unspecified Product|digikam |Baloo Assignee|digikam-de...@kde.org |m...@vhanda.in Component|general |General CC||caulier.gil...@gmail.com, ||pinak.ah...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kcmutils] [Bug 352471] KPluginSelector::addPlugins() says last 'config' parameter can be default, but asserts if it is
https://bugs.kde.org/show_bug.cgi?id=352471 --- Comment #2 from Jonathan Marten --- https://git.reviewboard.kde.org/r/126423/ -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 356901] New: Remove Klipper KDE component from Global Keyboard Shortcuts
https://bugs.kde.org/show_bug.cgi?id=356901 Bug ID: 356901 Summary: Remove Klipper KDE component from Global Keyboard Shortcuts Product: systemsettings Version: 5.5.0 Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: kcm_keys Assignee: k...@michael-jansen.biz Reporter: sud...@sudhirkhanger.com The clipboard manager's keyboard shortcut settings are moved to Plasma component of the Global Keyboard Shortcuts. The Klipper component is redundant and doesn't work. Reproducible: Always Steps to Reproduce: 1. SystemSettings>Shortcuts>Global Keyboard Shortcuts 2. Making changes to clipboard manager keyboard settings will not change values in klipper component but will make changes to Plasma component. 3. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 356878] v15.08.3: Several kate instances are restored during login / kate does not exit
https://bugs.kde.org/show_bug.cgi?id=356878 Gregor Mi changed: What|Removed |Added Summary|v15.08.3: Several kate |v15.08.3: Several kate |instances are restored |instances are restored |during login|during login / kate does ||not exit --- Comment #1 from Gregor Mi --- I started kate from the console. It prints some warnings: 0x27e6220 void QWindowPrivate::setTopLevelScreen(QScreen*, bool) ( QScreen(0x1f974b0) ): Attempt to set a screen on a child window. 0x27e6740 void QWindowPrivate::setTopLevelScreen(QScreen*, bool) ( QScreen(0x1f974b0) ): Attempt to set a screen on a child window. But when I close kate using the X-Button from the window the process does not end. When I use File->Quit however, kate closes properly. (This does not happen with kwrite) -- You are receiving this mail because: You are watching all bug changes.
[kmymoney4] [Bug 345655] Rounding problems between checking and investment account
https://bugs.kde.org/show_bug.cgi?id=345655 --- Comment #7 from Romain Henriet --- Will patch from bug 303026 be reverted ? Difference between kmymoney's reconciled value and my bank's value is growing slowly... -- You are receiving this mail because: You are watching all bug changes.
[kdepim] [Bug 356859] After update to Applications 15.12 Kontact apps(Korganizer, Kmail etc) don't start
https://bugs.kde.org/show_bug.cgi?id=356859 Bernd Weigelt changed: What|Removed |Added CC||weigelt.be...@web.de --- Comment #1 from Bernd Weigelt --- same problem here with Leap 42.1 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356843] Plasmashell segfault after use Alt+F2 and putting any letter in edit box
https://bugs.kde.org/show_bug.cgi?id=356843 --- Comment #13 from Thomas Lübking --- (In reply to Piotr Mierzwinski from comment #11) > Probably because kernel what I use (4.3.2) has not set parameter: > CONFIG_SECURITY_YAMA. I suppose like that because I get error "no such file" > when I try to check this file. Yes, it's just meanwhile usually enabled and you cannot attach to random process when it's set. Just attach to the running process: gdb --pid 123456 2>&1 | tee plasmashell.gdb # proper pid please ;-) then continue then cause the crash, gdb should not the segfault, then finally run (in gdb) thread apply all bt -- You are receiving this mail because: You are watching all bug changes.
[gcompris] [Bug 355851] Hotspot in ‘Find the details’ activity is wrong
https://bugs.kde.org/show_bug.cgi?id=355851 Bruno Coudoin changed: What|Removed |Added Latest Commit|http://commits.kde.org/gcom |http://commits.kde.org/gcom |pris/49374323c65c976f18c5fc |pris/76237417e8ed067a3ae049 |b679a51e14971c8c59 |3a186c6cca195b7b8a --- Comment #5 from Bruno Coudoin --- Git commit 76237417e8ed067a3ae0493a186c6cca195b7b8a by Bruno Coudoin. Committed on 19/12/2015 at 09:12. Pushed by bcoudoin into branch 'KDE/0.50'. babymatch, use the shortest dist to target instead of drop target M +30 -22 src/activities/babymatch/Babymatch.qml M +159 -144 src/activities/babymatch/DragListItem.qml M +42 -77 src/activities/babymatch/DropAnswerItem.qml M +22 -16 src/activities/babymatch/ListWidget.qml M +39 -7src/activities/babymatch/babymatch.js http://commits.kde.org/gcompris/76237417e8ed067a3ae0493a186c6cca195b7b8a -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 356831] cannot send image to clipboard in background mode
https://bugs.kde.org/show_bug.cgi?id=356831 --- Comment #3 from Boudhayan Gupta --- You can just press the "Copy to Clipboard" button or Ctrl+C on the keyboard. Adding a "Copy to clipboard on Spectacle start" will unintentionally destroy clipboard contents and confuse users who were expecting to paste something, so that won't happen without careful thought and consideration. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 350956] Simple remote Konsole window using huge amount of bandwidth
https://bugs.kde.org/show_bug.cgi?id=350956 --- Comment #1 from d...@newtech.fi --- Just "upgraded" to FC23 and got konsole v. 15.08.3 on KDE 5.17.0 (Qt 5.5.1) and now this problem is even worse - A lot worse.. The same procedure as described above will consume ALL the bandwith of my WiFi for one simple konsole window. Come on guys, you are putting far too much effort into Wayland neglecting the current X-window remote user... -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 350651] Konsole has scrolling artifacts if HiDPI screen with scaling in Qt
https://bugs.kde.org/show_bug.cgi?id=350651 --- Comment #5 from Tsu Jan --- A part of the issue: https://bugreports.qt.io/browse/QTBUG-48116 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356892] system hangs after screensave
https://bugs.kde.org/show_bug.cgi?id=356892 --- Comment #1 from rysic --- One more thing. System hangs on screensave every time but this debut error mesage appears only once. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 343349] in vertical panel icons in systemtray are ridiculously huge
https://bugs.kde.org/show_bug.cgi?id=343349 Phil Schaf changed: What|Removed |Added CC||flying-sh...@web.de --- Comment #9 from Phil Schaf --- Created attachment 96197 --> https://bugs.kde.org/attachment.cgi?id=96197&action=edit blurry 22px icons -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 343349] in vertical panel icons in systemtray are ridiculously huge
https://bugs.kde.org/show_bug.cgi?id=343349 Phil Schaf changed: What|Removed |Added Status|UNCONFIRMED |CONFIRMED Ever confirmed|0 |1 --- Comment #10 from Phil Schaf --- i have this problem as well. no idea of a recent sans-serif font change or system upgrade caused it, but my icons are now 22px instead of 16px like before. not only are some of the icons blurred (volume and network), but with the padding this now means i need >50px wide vertical bar to fit two columns (as seen in the screenshot above) it would be very useful to 1. add 22px versions for the missing icons 2. give an option to keep the icons small -- You are receiving this mail because: You are watching all bug changes.
[Baloo] [Bug 356601] Baloo does not index new files
https://bugs.kde.org/show_bug.cgi?id=356601 --- Comment #10 from Pinak Ahuja --- Normally desktop is a subdirector of /home/username but since you explicitly wrote /Desktop (notice the slash in front) i thought you might have a special setup. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 343632] DockManager support (or similar interface) for displaying badges, progress bars etc. on icons
https://bugs.kde.org/show_bug.cgi?id=343632 Phil Schaf changed: What|Removed |Added CC||flying-sh...@web.de --- Comment #1 from Phil Schaf --- the old icon-tasks had support for unity’s Launcher API: https://wiki.ubuntu.com/Unity/LauncherAPI since they declare that the GLib-based C API is stable and the DBus API not, it makes sense to not keep compatibility here. KDE depending on GLib will (hopefully) never happen, else the floodgates are open for monoculture. i found a spec for the DockManager API here: https://github.com/sandsmark/quassel-web/blob/6ba98cf72fee47e2b1bea2d8d62e0cab03922962/dev-notes/DockManager-spec.txt -- You are receiving this mail because: You are watching all bug changes.
[Baloo] [Bug 356601] Baloo does not index new files
https://bugs.kde.org/show_bug.cgi?id=356601 --- Comment #11 from Pinak Ahuja --- Could you run balooctl status on one of the files that doesn't show up in the results and paste the output? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 349358] Lag on first opening of plasma elements like menu, calendar, network (see video)
https://bugs.kde.org/show_bug.cgi?id=349358 --- Comment #16 from jeremy9...@gmail.com --- David, I will be happy if you can give us your thought here https://forum.kde.org/viewtopic.php?f=289&t=130131 -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 356902] New: Starters are visually indistinguishable from listed tasks in the task manager widget on breeze light
https://bugs.kde.org/show_bug.cgi?id=356902 Bug ID: 356902 Summary: Starters are visually indistinguishable from listed tasks in the task manager widget on breeze light Product: Breeze Version: 5.5.1 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: plasma-de...@kde.org Reporter: flying-sh...@web.de occurs in both icons-only task widget and regular task widget. Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 356902] Starters are visually indistinguishable from listed tasks in the task manager widget on breeze light
https://bugs.kde.org/show_bug.cgi?id=356902 --- Comment #1 from Phil Schaf --- Created attachment 96198 --> https://bugs.kde.org/attachment.cgi?id=96198&action=edit firefox is an opened task, the systemsettings icon is a starter -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 356903] New: akonadi notes agent use 800Mb of RAM all the time
https://bugs.kde.org/show_bug.cgi?id=356903 Bug ID: 356903 Summary: akonadi notes agent use 800Mb of RAM all the time Product: Akonadi Version: 4.13 Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED Severity: major Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: m...@vowleyfarm.co.uk I use Kontact (4.14.10 under Plasma5, Fedora22), and the akonadi_notes_agent always occupies around about this much memory. I have very few notes, but it seems ALL my email is also listed in a notebook. I don't want this, I'm not aware of having set it up like this, I don't seem to be able to stop it. If I select "Notes" in Kontact then its RAM usage goes up around 1.25Gb and 50% cpu usage. I haven't been able to find a solution either from the help or the IRC channel(s). Reproducible: Always Steps to Reproduce: 1. Turn on computer 2. 3. -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 352055] plasma-pa plasmoid not shown in systemtray after startup
https://bugs.kde.org/show_bug.cgi?id=352055 Olivier Churlaud changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|UPSTREAM|--- --- Comment #48 from Olivier Churlaud --- The problem disappeared and came back... Again with plasma-pa. My system: Archlinux Plasma 5.5.1 (on Arch, the package is plasma-workspace 5.5.1.1-1) Frameworks 5.17. I reopened... Feel free to tell me to open a new bug if needed. -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 352055] plasma-pa plasmoid not shown in systemtray after startup
https://bugs.kde.org/show_bug.cgi?id=352055 --- Comment #49 from Olivier Churlaud --- Killing and starting again plasmashell solves the issue... -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356904] New: File transfer indication disappears after changing display option
https://bugs.kde.org/show_bug.cgi?id=356904 Bug ID: 356904 Summary: File transfer indication disappears after changing display option Product: plasmashell Version: 5.4.3 Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Notifications Assignee: mklape...@kde.org Reporter: kdde@porcupinefactory.org CC: plasma-b...@kde.org When switching displaying of file transfers from notification area to a separate window during a transfer, any transfer indication disappears completely. Reproducible: Didn't try Steps to Reproduce: 1. Start long-running file transfer 2. Click the transfer indicator (on a panel) 3. Right-click transfer box and select notification settings 4. Uncheck "Track file transfers [...]" and apply. Actual Results: Transfer disappears from notification area. Expected Results: 1. Transfer disappears from notification area and dedicated transfer window appears. or 2. Newly started transfers get their own windows. -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 352055] plasma-pa plasmoid not shown in systemtray after startup
https://bugs.kde.org/show_bug.cgi?id=352055 --- Comment #50 from Kirill Bogdanenko --- (In reply to Olivier Churlaud from comment #49) > Killing and starting again plasmashell solves the issue... You can also try toggling off and on plasma-pa widget in systemtray settings -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356904] File transfer windows don't show up
https://bugs.kde.org/show_bug.cgi?id=356904 kdde@porcupinefactory.org changed: What|Removed |Added Summary|File transfer indication|File transfer windows don't |disappears after changing |show up |display option | --- Comment #1 from kdde@porcupinefactory.org --- Update: Transfer window doesn't appear at all when the option mentioned above is unchecked. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 356905] New: Desktop effects does not work, KDE5 Plasma5
https://bugs.kde.org/show_bug.cgi?id=356905 Bug ID: 356905 Summary: Desktop effects does not work, KDE5 Plasma5 Product: kde Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: herald...@gmail.com Hi friends! I'm on NixOS with KDE5. Desktop effects seem not to work at all (neither with OpenGL not XRender selected). When switching compositing type appears error hint saying "26 desktop effects could not be loaded.", also in `General` tab I see following error message: > No such method 'compositingNotPossibleReason' in interface 'org.kde.KWin' at > object path '/KWin' (signature '') I use nvidia proprietary drivers, but I believe this does not makes any difference. I'm fairy new to KDE and NixOS too, so please guide what additional information should I provide. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356906] New: Irregular updates
https://bugs.kde.org/show_bug.cgi?id=356906 Bug ID: 356906 Summary: Irregular updates Product: plasmashell Version: 5.4.3 Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: kdde@porcupinefactory.org CC: bhus...@gmail.com, plasma-b...@kde.org After running for some time (~2 days, hibernation may be at play here), widgets start to draw updates irregularly. Digital clock: most of the time, every 2 seconds (only other updates coming from net/cpu/mem monitors), sometimes every 1 second, very rarely 3 seconds. Task switcher: any updates happen only on 1 second boundaries, leading to significant lag when selecting active window. Reproducible: Sometimes Steps to Reproduce: 1. Start KDE with the setup described in Additional Information 2. Use for a few days, hibernating between sessions. Actual Results: Digital clock: most of the time, every 2 seconds (only other updates coming from net/cpu/mem monitors), sometimes every 1 second, very rarely 3 seconds. Task switcher: any updates happen only on 1 second boundaries, leading to significant lag when switching workspaces or selecting active window. (The 1-second boundary aligns with a clock bump, clock bump can be forced by switching windows.) Expected Results: Digital clock bumps the number by 1 approximately every second when not CPU starved Task switcher never waits for a one-second boundary to update active window highlight. System uses Intel HD4000 GPU, default Fedora 22 setup. When panel semi-transparent, underlying windows' updates imediately seen "through" the panel yet the problem persists. Panel setup: One of 2 panels; vertical. Widgets: CPU, mem, net monitor, task manager, digital clock. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356904] File transfer windows don't show up
https://bugs.kde.org/show_bug.cgi?id=356904 Kai Uwe Broulik changed: What|Removed |Added Status|UNCONFIRMED |CONFIRMED Ever confirmed|0 |1 CC||k...@privat.broulik.de --- Comment #2 from Kai Uwe Broulik --- The jobs dataengine isn't properly unloaded and/or it fails to unregister the job view service. Does it work if you uncheck this option and restart Plasma? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356907] New: Plasma crashed while watching a broadcast in steam big picture mode
https://bugs.kde.org/show_bug.cgi?id=356907 Bug ID: 356907 Summary: Plasma crashed while watching a broadcast in steam big picture mode Product: plasmashell Version: 5.5.1 Platform: Gentoo Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: k...@kaishome.de CC: bhus...@gmail.com, plasma-b...@kde.org Application: plasmashell (5.5.1) Qt Version: 5.5.1 Operating System: Linux 4.2.8-gentoo x86_64 Distribution: "Gentoo Base System release 2.2" -- Information about the crash: - What I was doing when the application crashed: I did nothing but watching a video broadcast in Steam when suddenly the crash reporter of KDE popped into front. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". pthread_cond_wait () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 [Current thread is 1 (Thread 0x7ff8db951880 (LWP 1292))] Thread 16 (Thread 0x7ff8dae33700 (LWP 1293)): #0 0x003535adfc7d in poll () at ../sysdeps/unix/syscall-template.S:81 #1 0x00345540aac2 in poll (__timeout=-1, __nfds=1, __fds=0x7ff8dae32c40) at /usr/include/bits/poll2.h:46 #2 _xcb_conn_wait (c=c@entry=0xcdcf60, cond=cond@entry=0xcdcfa0, vector=vector@entry=0x0, count=count@entry=0x0) at /var/tmp/portage/x11-libs/libxcb-1.11.1/work/libxcb-1.11.1/src/xcb_conn.c:459 #3 0x00345540c72f in xcb_wait_for_event (c=0xcdcf60) at /var/tmp/portage/x11-libs/libxcb-1.11.1/work/libxcb-1.11.1/src/xcb_in.c:693 #4 0x7ff8db49bc89 in QXcbEventReader::run (this=0xceb0f0) at qxcbconnection.cpp:1229 #5 0x003081ea04a2 in QThreadPrivate::start (arg=0xceb0f0) at thread/qthread_unix.cpp:331 #6 0x003536207324 in start_thread (arg=0x7ff8dae33700) at pthread_create.c:333 #7 0x003535ae8a9d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 15 (Thread 0x7ff8d8eea700 (LWP 1328)): #0 g_mutex_unlock (mutex=0x7ff8cc000990) at /var/tmp/portage/dev-libs/glib-2.44.1-r1/work/glib-2.44.1/glib/gthread-posix.c:1348 #1 0x0036d7c490a0 in g_main_context_prepare (context=context@entry=0x7ff8cc000990, priority=priority@entry=0x7ff8d8ee9bf0) at /var/tmp/portage/dev-libs/glib-2.44.1-r1/work/glib-2.44.1/glib/gmain.c:3408 #2 0x0036d7c49a98 in g_main_context_iterate (context=context@entry=0x7ff8cc000990, block=block@entry=1, dispatch=dispatch@entry=1, self=) at /var/tmp/portage/dev-libs/glib-2.44.1-r1/work/glib-2.44.1/glib/gmain.c:3788 #3 0x0036d7c49c7c in g_main_context_iteration (context=0x7ff8cc000990, may_block=1) at /var/tmp/portage/dev-libs/glib-2.44.1-r1/work/glib-2.44.1/glib/gmain.c:3869 #4 0x00308209aebc in QEventDispatcherGlib::processEvents (this=0x7ff8cc0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:418 #5 0x00308204c17a in QEventLoop::exec (this=this@entry=0x7ff8d8ee9d20, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #6 0x003081e9ba34 in QThread::exec (this=this@entry=0xdcc690) at thread/qthread.cpp:503 #7 0x00308c6ede65 in QQmlThreadPrivate::run (this=0xdcc690) at qml/ftw/qqmlthread.cpp:141 #8 0x003081ea04a2 in QThreadPrivate::start (arg=0xdcc690) at thread/qthread_unix.cpp:331 #9 0x003536207324 in start_thread (arg=0x7ff8d8eea700) at pthread_create.c:333 #10 0x003535ae8a9d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 14 (Thread 0x7ff8d0ae8700 (LWP 1351)): #0 0x003535adbccd in read () at ../sysdeps/unix/syscall-template.S:81 #1 0x0036d7c8cd90 in read (__nbytes=16, __buf=0x7ff8d0ae7b20, __fd=) at /usr/include/bits/unistd.h:44 #2 g_wakeup_acknowledge (wakeup=0x7ff8cc0025a0) at /var/tmp/portage/dev-libs/glib-2.44.1-r1/work/glib-2.44.1/glib/gwakeup.c:210 #3 0x0036d7c4961c in g_main_context_check (context=context@entry=0x7ff8c8000990, max_priority=2147483647, fds=fds@entry=0x7ff8c8002e70, n_fds=n_fds@entry=1) at /var/tmp/portage/dev-libs/glib-2.44.1-r1/work/glib-2.44.1/glib/gmain.c:3600 #4 0x0036d7c49b10 in g_main_context_iterate (context=context@entry=0x7ff8c8000990, block=block@entry=1, dispatch=dispatch@entry=1, self=) at /var/tmp/portage/dev-libs/glib-2.44.1-r1/work/glib-2.44.1/glib/gmain.c:3805 #5 0x0036d7c49c7c in g_main_context_iteration (context=0x7ff8c8000990, may_block=1) at /var/tmp/portage/dev-libs/glib-2.44.1-r1/work/glib-2.44.1/glib/gmain.c:3869 #6 0x00308209aebc in QEventDispatcherGlib::processEvents (this=0x7ff8c80008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:418 #7 0x00308204c17a in QEventLoop::exec (this=this@entry=0x7ff8d0ae7d20, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #8 0x003081e9ba34 in QThread::exec (this=this@entry=0x10a2500) at thread/qthread.cpp:503 #9 0x00308c6ede65 in QQmlThreadPrivate::
[plasmashell] [Bug 356904] File transfer windows don't show up
https://bugs.kde.org/show_bug.cgi?id=356904 --- Comment #3 from kdde@porcupinefactory.org --- Yes, after restarting Plasma shell, a file transfer window appeared. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 355148] Missing function: "Code -> Move to source"
https://bugs.kde.org/show_bug.cgi?id=355148 --- Comment #2 from Milian Wolff --- In my eyes, the Clang-based refactoring has a too high complexity and does not integrate that well into our existing structure and code base. It also had serious problems with project-wide refactorings. So imo, we should try to look at bringing back this functionality requested here and others based on a slimmed down architecture, also leveraging our DUChain where possible. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356908] New: popup does not factor in auto-hiding panel
https://bugs.kde.org/show_bug.cgi?id=356908 Bug ID: 356908 Summary: popup does not factor in auto-hiding panel Product: plasmashell Version: 5.4.3 Platform: Debian unstable OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Battery Monitor Assignee: k...@privat.broulik.de Reporter: kde-b...@ginguppin.de CC: plasma-b...@kde.org panel set to to auto-hide battery icon in what used to be the systray, left mouse click opens up the info popup with brightness and battery status the lower part id covered by the panel and thus inaccessible. obviously the popup calculates it lower bound from the hidden panel, thereby ignoring the the panel will be visible when the popup is shown and thus cover the lower part of the popup even scrolling in that lower scrollable does not help see screenshot Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356909] New: Virtual desktop switcher shows minimized windows when setting "Keep window thumbnails" to "Always" in KWin
https://bugs.kde.org/show_bug.cgi?id=356909 Bug ID: 356909 Summary: Virtual desktop switcher shows minimized windows when setting "Keep window thumbnails" to "Always" in KWin Product: plasmashell Version: 5.4.2 Platform: Debian testing OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Pager Assignee: plasma-b...@kde.org Reporter: alexander-...@xmine128.tk See "Steps to Reproduce" and "Additional Information"… Reproducible: Always Steps to Reproduce: 1. Make sure the "Pager" is present on the plasma shell somewhere and that you are using "KWin" as window manager 2. Minimize some window (preferably on an otherwise empty virtual desktop) and observe it disappearing from the "Pager" display 3. Open the "System settings" (from KDE 5) 4. Navigate to "Display and Monitor" → "Compositor" 5. Change the setting "Keep window thumbnails" to "Always" 6. Click "Apply" Actual Results: The minimized window is displayed in the "Pager" display as if it weren't minimized (but it's actually not visible when switching to that virtual desktop). Expected Results: The minimized window should be display in the "Pager" preview area. Changing the "Keep window thumbnails" setting should not have any effect. Using "xprop" and "diff" on the window in question, the following observations were made: When disabling window thumbnails for minimized windows, the minimized window has its window state set to "Iconic"; when enabling window thumbnails for minimized windows it's window state is always "Normal" and does change (whether you minimize it or not). Minimized windows always receive the additional "_NET_WM_STATE_HIDDEN" window manager state flag. This is behaviour is not influenced by the "keep window thumbnails" settings. My (educated) guess therefor is that "Pager" only checks whether a window's state is "Iconic" or not to determine whether it should be displayed as part of the preview or not. It does not, however, also check for the "_NET_WM_STATE_HIDDEN" atom to determine whether a window really is visible or not. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356908] popup does not factor in auto-hiding panel
https://bugs.kde.org/show_bug.cgi?id=356908 --- Comment #1 from arne anka --- Created attachment 96199 --> https://bugs.kde.org/attachment.cgi?id=96199&action=edit screnshot illustrating issue to clarify: despite the scrollbar visible at the bottom, it only scrolls so that barely the name is visible, bot not the bar -- You are receiving this mail because: You are watching all bug changes.
[kdelibs] [Bug 355275] kdelibs upgrade - Kopete crashes after closing a window
https://bugs.kde.org/show_bug.cgi?id=355275 Rex Dieter changed: What|Removed |Added Version Fixed In|4.14.15 |4.14.16 --- Comment #43 from Rex Dieter --- fyi, Fixed In: 4.14.15 is wrong, this commit came after 4.14.15 tagging/release as far as I can tell, adjusting to 4.14.16 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 317765] dangeling pointer in unconstrained_stacking_order, strongly related to tabbox and NO compositing
https://bugs.kde.org/show_bug.cgi?id=317765 Johannes Rauh changed: What|Removed |Added CC||jar...@web.de -- You are receiving this mail because: You are watching all bug changes.
Re: [dolphin] [Bug 356163] New: Dolphin crashes when right-clicking a file
Nick Elliott via KDE Bugzilla kde.org> writes: > > https://bugs.kde.org/show_bug.cgi?id=356163 > > Bug ID: 356163 >Summary: Dolphin crashes when right-clicking a file >Product: dolphin >Version: 15.08.2 > Platform: Kubuntu Packages > OS: Linux > Status: UNCONFIRMED > Severity: normal > Priority: NOR > Component: general > Assignee: dolphin-bugs-null kde.org > Reporter: nick nick-elliott.net > > I am seeing frequent (but not consistent) crashes when I right-click a file to > perform file operations in Dolphin. > > I work in split-view mode. > > This behaviour started since upgrading to 15:10. > > Reproducible: Sometimes > > Steps to Reproduce: > 1. Right-click a file in Dolphin > 2. > 3. > > Actual Results: > The Dolphin windows closes - sometimes there will be a delay before the window > disappears. > Sometimes it crashes before the file operations menu appears, other times not. > I get this a lot also, with Kubuntu 15.10 Seems to always happen with right-clicking on a .png file saved in the Home directory, and trying "Open With..." (I have Pinta installed, and like to open with Pinta for editing) If I move the png file to the Home/Pictures folder, then the same issue no longer occurs. So- could be a settings issue around file types (to do with auto-preview perhaps) in certain folders?
[kexi] [Bug 356888] Kexi crashes at the attempt to create a table row.
https://bugs.kde.org/show_bug.cgi?id=356888 --- Comment #3 from Jan --- Created attachment 96200 --> https://bugs.kde.org/attachment.cgi?id=96200&action=edit The Database file. Thanks for the quick response. Sorry I forgot to deliver more information. This is the relevant database. -- You are receiving this mail because: You are watching all bug changes.
[kdepim] [Bug 356859] After update to Applications 15.12 Kontact apps(Korganizer, Kmail etc) don't start
https://bugs.kde.org/show_bug.cgi?id=356859 Dave Griffiths changed: What|Removed |Added CC||dave.griffith...@gmail.com --- Comment #2 from Dave Griffiths --- Confirmed on Leap 42.1, permanent error. -- You are receiving this mail because: You are watching all bug changes.
Re: [dolphin] [Bug 356163] New: Dolphin crashes when right-clicking a file
Nick Elliott via KDE Bugzilla kde.org> writes: > > https://bugs.kde.org/show_bug.cgi?id=356163 > > Bug ID: 356163 >Summary: Dolphin crashes when right-clicking a file >Product: dolphin >Version: 15.08.2 > Platform: Kubuntu Packages > OS: Linux > Status: UNCONFIRMED > Severity: normal > Priority: NOR > Component: general > Assignee: dolphin-bugs-null kde.org > Reporter: nick nick-elliott.net > > I am seeing frequent (but not consistent) crashes when I right-click a file to > perform file operations in Dolphin. > > I work in split-view mode. > > This behaviour started since upgrading to 15:10. > > Reproducible: Sometimes > > Steps to Reproduce: > 1. Right-click a file in Dolphin > 2. > 3. > > Actual Results: > The Dolphin windows closes - sometimes there will be a delay before the window > disappears. > Sometimes it crashes before the file operations menu appears, other times not. > I get this a lot also, with Kubuntu 15.10 Seems to always happen with right-clicking on a .png file saved in the Home directory, and trying "Open With..." (I have Pinta installed, and like to open with Pinta for editing) If I move the png file to the Home/Pictures folder, then the same issue no longer occurs. So- could be a settings issue around file types (to do with auto-preview perhaps) in certain folders?
[kdelibs] [Bug 355275] kdelibs upgrade - Kopete crashes after closing a window
https://bugs.kde.org/show_bug.cgi?id=355275 --- Comment #44 from Alex Merry --- I committed it before the 4.14.15 tag had been pushed, so I assumed I'd made it, but clearly not. -- You are receiving this mail because: You are watching all bug changes.
[kdepim] [Bug 356859] After update to Applications 15.12 Kontact apps(Korganizer, Kmail etc) don't start
https://bugs.kde.org/show_bug.cgi?id=356859 Raymond Wooninck changed: What|Removed |Added CC||tittiatc...@gmail.com --- Comment #3 from Raymond Wooninck --- If everyone would have a proper look, then it would have been visible that the KDEPIM package itself was not published yet. Unfortunately KDE Applications finds itself in a slow building state, so it will take time to get this completely published. This is actually the risk of utilizing a development repository. KDE Applications would have come to Tumbleweed and Leap 42.1 as soon as everything would have been build properly. At this moment, I would suggest to revert back to the versions that are offered in Tumbleweed and/or Leap:Updates -- You are receiving this mail because: You are watching all bug changes.
[kdepim] [Bug 356859] After update to Applications 15.12 Kontact apps(Korganizer, Kmail etc) don't start
https://bugs.kde.org/show_bug.cgi?id=356859 --- Comment #4 from Raymond Wooninck --- Please close this bug as invalid and this one should have been reported at bugzilla.opensuse.org -- You are receiving this mail because: You are watching all bug changes.
[kdepim] [Bug 356859] After update to Applications 15.12 Kontact apps(Korganizer, Kmail etc) don't start
https://bugs.kde.org/show_bug.cgi?id=356859 Laurent Montel changed: What|Removed |Added Resolution|--- |INVALID Status|UNCONFIRMED |RESOLVED CC||mon...@kde.org --- Comment #5 from Laurent Montel --- opensuse problem -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356900] Crashing plasma after double click mouse wheel on networkmanager applet
https://bugs.kde.org/show_bug.cgi?id=356900 --- Comment #2 from AnAkkk --- This seem to be a duplicate of: https://bugs.kde.org/show_bug.cgi?id=356428 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356900] Crashing plasma after double click mouse wheel on networkmanager applet
https://bugs.kde.org/show_bug.cgi?id=356900 AnAkkk changed: What|Removed |Added CC||anakin...@gmail.com --- Comment #1 from AnAkkk --- I'm getting this same crash, many times per day, not when double clicking on the networkmanager applet though, but mostly with interacting with the task bar. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 356428] Plasmashell crash when minimizing app and then hovering mouse over taskmanager
https://bugs.kde.org/show_bug.cgi?id=356428 AnAkkk changed: What|Removed |Added CC||anakin...@gmail.com --- Comment #7 from AnAkkk --- I have the same issue, it's happening all the time when I am in a fullscreen app (CS GO), minimize it, and put my mouse over the taskbar. This is very annoying. -- You are receiving this mail because: You are watching all bug changes.
[kdepim] [Bug 356859] After update to Applications 15.12 Kontact apps(Korganizer, Kmail etc) don't start
https://bugs.kde.org/show_bug.cgi?id=356859 Bernd Weigelt changed: What|Removed |Added CC|weigelt.be...@web.de| -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kactivities] [Bug 356910] New: No Ability to Edit Activities without Installing "Activities" widget
https://bugs.kde.org/show_bug.cgi?id=356910 Bug ID: 356910 Summary: No Ability to Edit Activities without Installing "Activities" widget Product: frameworks-kactivities Version: 5.1.0 Platform: Kubuntu Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: ivan.cu...@kde.org Reporter: vtp...@myfairpoint.net CC: plasma-b...@kde.org In earlier versions of Plasma (I assume) if one depressed Super+Tab, the sidebar would remain active, allowing one to edit or add activities. Currently, Super+Tab acts like Alt+Tab, which means as soon as the keys are lifted, the sidebar/editing window disappears. The only workaround to this bug (that I know of) is to temporarily install the "Activities" widget. Clicking on the Activities widget allows the sidebar to remain active (and the user can edit or add Activities). Afterwards, the user must remove the widget (if, as in my case, it isn't wanted). Reproducible: Always Steps to Reproduce: 1. Super+Tab 2. Attempt to edit or Add activities is impossible. . If KDE devs want Super+Tab to behave like Alt+Tab, then Activities should be editable within Preferences. -- You are receiving this mail because: You are watching all bug changes.
[ark] [Bug 356911] New: Ark randomly crashes
https://bugs.kde.org/show_bug.cgi?id=356911 Bug ID: 356911 Summary: Ark randomly crashes Product: ark Version: 2.19 Platform: Mint (Debian based) OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: rak...@freebsd.org Reporter: d.anielhej...@gmail.com Application: ark (2.19) KDE Platform Version: 4.14.2 Qt Version: 4.8.6 Operating System: Linux 3.16.0-4-amd64 x86_64 Distribution: LMDE 2 Betsy -- Information about the crash: Trying to extrack by drag & drop from Ark to Dolphhin. The crash can be reproduced sometimes. -- Backtrace: Application: Ark (ark), signal: Bus error Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 [Current thread is 1 (Thread 0x7f6ed9a15780 (LWP 14890))] Thread 2 (Thread 0x7f6ec241b700 (LWP 14979)): [KCrash Handler] #6 0x7f6ed7065cdf in QVariant::cmp(QVariant const&) const () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #7 0x7f6ec2b23710 in operator== (v=..., this=) at /usr/include/qt4/QtCore/qvariant.h:405 #8 QList::contains (this=this@entry=0x1ea05e0, t=...) at /usr/include/qt4/QtCore/qlist.h:885 #9 0x7f6ec2b1f102 in LibArchiveInterface::copyFiles (this=0x1db6360, files=..., destinationDirectory=..., options=...) at ../../../plugins/libarchive/libarchivehandler.cpp:232 #10 0x7f6ed9622401 in Kerfuffle::ExtractJob::doWork (this=0x1ea05b0) at ../../kerfuffle/jobs.cpp:266 #11 0x7f6ed96208c1 in Kerfuffle::Job::Private::run (this=0x1bf3a50) at ../../kerfuffle/jobs.cpp:58 #12 0x7f6ed6f3770f in ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #13 0x7f6ed34fc0a4 in start_thread (arg=0x7f6ec241b700) at pthread_create.c:309 #14 0x7f6ed68ed04d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111 Thread 1 (Thread 0x7f6ed9a15780 (LWP 14890)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f6ed6f37c66 in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #2 0x7f6ed6f3729e in QThread::wait(unsigned long) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #3 0x7f6ed9620860 in Kerfuffle::Job::~Job (this=0x1ea05b0, __in_chrg=) at ../../kerfuffle/jobs.cpp:87 #4 0x7f6ed9623739 in ~ExtractJob (this=0x1ea05b0, __in_chrg=) at ../../kerfuffle/jobs.h:118 #5 Kerfuffle::ExtractJob::~ExtractJob (this=0x1ea05b0, __in_chrg=) at ../../kerfuffle/jobs.h:118 #6 0x7f6ec6e46a74 in JobTracker::~JobTracker (this=this@entry=0x1db7220, __in_chrg=) at ../../part/jobtracker.cpp:43 #7 0x7f6ec6e46ac9 in JobTracker::~JobTracker (this=0x1db7220, __in_chrg=) at ../../part/jobtracker.cpp:45 #8 0x7f6ed7059248 in QObjectPrivate::deleteChildren() () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #9 0x7f6ed7ab3173 in QWidget::~QWidget() () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4 #10 0x7f6ed7ecdd69 in QSplitter::~QSplitter() () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4 #11 0x7f6ed912492f in KParts::Part::~Part() () from /usr/lib/libkparts.so.4 #12 0x7f6ec6e2b949 in Ark::Part::~Part (this=0x1c454d0, __in_chrg=, __vtt_parm=) at ../../part/part.cpp:139 #13 0x7f6ec6e2b999 in Ark::Part::~Part (this=0x1c454d0, __in_chrg=, __vtt_parm=) at ../../part/part.cpp:146 #14 0x0040ddff in MainWindow::~MainWindow (this=this@entry=0x1bf47d0, __in_chrg=, __vtt_parm=) at ../../app/mainwindow.cpp:72 #15 0x0040deb9 in MainWindow::~MainWindow (this=0x1bf47d0, __in_chrg=, __vtt_parm=) at ../../app/mainwindow.cpp:74 #16 0x7f6ed705ae38 in QObject::event(QEvent*) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #17 0x7f6ed7ab3c63 in QWidget::event(QEvent*) () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4 #18 0x7f6ed7e8fb23 in QMainWindow::event(QEvent*) () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4 #19 0x7f6ed88d98e9 in KXmlGuiWindow::event(QEvent*) () from /usr/lib/libkdeui.so.5 #20 0x7f6ed7a6048c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4 #21 0x7f6ed7a66fa8 in QApplication::notify(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4 #22 0x7f6ed87d81aa in KApplication::notify(QObject*, QEvent*) () from /usr/lib/libkdeui.so.5 #23 0x7f6ed704171d in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #24 0x7f6ed7044fc1 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #25 0x7f6ed7070bd3 in ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #26 0x7f6ed3014c5d in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #27 0x7f6ed3014f48 in ?? () from /lib/x8
[dolphin] [Bug 352594] Some settings always restore to default
https://bugs.kde.org/show_bug.cgi?id=352594 gerstavros changed: What|Removed |Added Resolution|--- |FIXED Status|UNCONFIRMED |RESOLVED --- Comment #4 from gerstavros --- No problem with latest version (15.08.3). I haven't relized also that double click was set from System settings -- You are receiving this mail because: You are watching all bug changes.
[ark] [Bug 356912] New: Falling ark
https://bugs.kde.org/show_bug.cgi?id=356912 Bug ID: 356912 Summary: Falling ark Product: ark Version: 2.19 Platform: Mint (Debian based) OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: rak...@freebsd.org Reporter: d.anielhej...@gmail.com Application: ark (2.19) KDE Platform Version: 4.14.2 Qt Version: 4.8.6 Operating System: Linux 3.16.0-4-amd64 x86_64 Distribution: LMDE 2 Betsy -- Information about the crash: Open zip file containing zip file, recursively. Extract. Try to close. The crash can be reproduced every time. -- Backtrace: Application: Ark (ark), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [KCrash Handler] #6 0x7f1475d3d4a0 in KXMLGUIFactory::removeClient(KXMLGUIClient*) () from /usr/lib/libkdeui.so.5 #7 0x7f1464285914 in Ark::Part::~Part (this=0xd15390, __in_chrg=, __vtt_parm=) at ../../part/part.cpp:141 #8 0x7f1464285999 in Ark::Part::~Part (this=0xd15390, __in_chrg=, __vtt_parm=) at ../../part/part.cpp:146 #9 0x7f147657e3b9 in KParts::Part::slotWidgetDestroyed() () from /usr/lib/libkparts.so.4 #10 0x7f14744b071c in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #11 0x7f14744b118f in QObject::destroyed(QObject*) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #12 0x7f14744b53b7 in QObject::~QObject() () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #13 0x7f1474f0d207 in QWidget::~QWidget() () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4 #14 0x7f1475327d69 in QSplitter::~QSplitter() () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4 #15 0x7f14744b3248 in QObjectPrivate::deleteChildren() () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #16 0x7f1474f0d173 in QWidget::~QWidget() () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4 #17 0x7f1475d2eae9 in KVBox::~KVBox() () from /usr/lib/libkdeui.so.5 #18 0x7f14744b3248 in QObjectPrivate::deleteChildren() () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #19 0x7f1474f0d173 in QWidget::~QWidget() () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4 #20 0x7f14642916a4 in ~ArkViewer (this=0xda28a0, __in_chrg=) at ../../part/arkviewer.cpp:56 #21 ArkViewer::~ArkViewer (this=0xda28a0, __in_chrg=) at ../../part/arkviewer.cpp:58 #22 0x7f14744b3248 in QObjectPrivate::deleteChildren() () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #23 0x7f1474f0d173 in QWidget::~QWidget() () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4 #24 0x7f1475327d69 in QSplitter::~QSplitter() () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4 #25 0x7f147657e92f in KParts::Part::~Part() () from /usr/lib/libkparts.so.4 #26 0x7f1464285949 in Ark::Part::~Part (this=0xb2fb60, __in_chrg=, __vtt_parm=) at ../../part/part.cpp:139 #27 0x7f1464285999 in Ark::Part::~Part (this=0xb2fb60, __in_chrg=, __vtt_parm=) at ../../part/part.cpp:146 #28 0x0040ddff in MainWindow::~MainWindow (this=this@entry=0xae9c50, __in_chrg=, __vtt_parm=) at ../../app/mainwindow.cpp:72 #29 0x0040deb9 in MainWindow::~MainWindow (this=0xae9c50, __in_chrg=, __vtt_parm=) at ../../app/mainwindow.cpp:74 #30 0x7f14744b4e38 in QObject::event(QEvent*) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #31 0x7f1474f0dc63 in QWidget::event(QEvent*) () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4 #32 0x7f14752e9b23 in QMainWindow::event(QEvent*) () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4 #33 0x7f1475d338e9 in KXmlGuiWindow::event(QEvent*) () from /usr/lib/libkdeui.so.5 #34 0x7f1474eba48c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4 #35 0x7f1474ec0fa8 in QApplication::notify(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4 #36 0x7f1475c321aa in KApplication::notify(QObject*, QEvent*) () from /usr/lib/libkdeui.so.5 #37 0x7f147449b71d in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #38 0x7f147449efc1 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #39 0x7f14744cabd3 in ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #40 0x7f147046ec5d in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #41 0x7f147046ef48 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #42 0x7f147046effc in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #43 0x7f14744cad1d in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #44 0x7f1474f5ef96 in ?? () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4 #45 0x7f147449a271 in QEventLoop::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQtCore.
[akregator] [Bug 260972] "share services" should also support Facebook
https://bugs.kde.org/show_bug.cgi?id=260972 Laurent Montel changed: What|Removed |Added Resolution|--- |FIXED Status|UNCONFIRMED |RESOLVED CC||mon...@kde.org --- Comment #1 from Laurent Montel --- Now we have a menu to share article on facebook and co -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 356816] When I open certain pdf documents, each entry in table of contents contains weird chracters at the end.
https://bugs.kde.org/show_bug.cgi?id=356816 Albert Astals Cid changed: What|Removed |Added CC||aa...@kde.org Resolution|--- |WAITINGFORINFO Status|UNCONFIRMED |NEEDSINFO --- Comment #4 from Albert Astals Cid --- Need the pdf file, can't fix bugs without the pdf file. -- You are receiving this mail because: You are watching all bug changes.
[Baloo] [Bug 356601] Baloo does not index new files
https://bugs.kde.org/show_bug.cgi?id=356601 --- Comment #12 from hotmusic...@mail.bg --- @Pinak Ahuja I haven't any special setup - all is by default and my /Desktop is a subdirectory of /home - this is visible in the first screenshot with the file manager. I performed this command searcching 03 - Believe.flac in the 'problematic' folder. This is the output: File: /home/hotmusicfan/Desktop/New/Morgan Basic Indexing: Disbabled -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 334019] Okular should warn if closing with multiple tabs opened
https://bugs.kde.org/show_bug.cgi?id=334019 --- Comment #14 from Albert Astals Cid --- (In reply to torhamzed from comment #13) > I added it to reviewboard before adding it here. I don't see it here https://git.reviewboard.kde.org/dashboard/?group=okular&view=to-group > I apologize, is this KDE bug tracking website deprecated? No, the bug tracking website is used to track bugs, not patches. > I've seen the use of both such type > websites before, and that was how I saw them used - make sure a copy is in > both places. Having things in more than one place is a bad practice, it's the perfect way to get things that only some people from one place read and only some other in some other and you end up with lots of lost communication. -- You are receiving this mail because: You are watching all bug changes.
[Baloo] [Bug 356913] New: fall when deleting files on external sdcard
https://bugs.kde.org/show_bug.cgi?id=356913 Bug ID: 356913 Summary: fall when deleting files on external sdcard Product: Baloo Version: unspecified Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: General Assignee: m...@vhanda.in Reporter: vilem.iva...@gmail.com CC: pinak.ah...@gmail.com Application: baloo_file (5.16.0) Qt Version: 5.5.1 Operating System: Linux 4.3.0-2-default i686 Distribution: "openSUSE Tumbleweed (20151217) (i586)" -- Information about the crash: - What I was doing when the application crashed: app was using cca 25% of CPU so i killed it and i received this bug report -- Backtrace: Application: Baloo File Indexing Daemon (baloo_file), signal: Segmentation fault Using host libthread_db library "/lib/libthread_db.so.1". [Current thread is 1 (Thread 0xb5079800 (LWP 1625))] Thread 2 (Thread 0x73692b40 (LWP 2189)): #0 0xb76e6d80 in __kernel_vsyscall () #1 0xb6c6e23b in read () from /lib/libc.so.6 #2 0xb56e5dd5 in ?? () from /usr/lib/libglib-2.0.so.0 #3 0xb56a1a26 in g_main_context_check () from /usr/lib/libglib-2.0.so.0 #4 0xb56a1ee1 in ?? () from /usr/lib/libglib-2.0.so.0 #5 0xb56a2084 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #6 0xb71c2b14 in QEventDispatcherGlib::processEvents (this=0x72d00468, flags=...) at kernel/qeventdispatcher_glib.cpp:420 #7 0xb716a533 in QEventLoop::processEvents (this=0x73692114, flags=...) at kernel/qeventloop.cpp:128 #8 0xb716a96a in QEventLoop::exec (this=0x73692114, flags=...) at kernel/qeventloop.cpp:204 #9 0x08065fae in Baloo::FileContentIndexer::run (this=0x84be050) at /usr/src/debug/baloo-5.16.0/src/file/filecontentindexer.cpp:71 #10 0xb6fa04f1 in QThreadPoolThread::run (this=0x848d0f0) at thread/qthreadpool.cpp:93 #11 0xb6fa3c20 in QThreadPrivate::start (arg=0x848d0f0) at thread/qthread_unix.cpp:331 #12 0xb63da315 in start_thread () from /lib/libpthread.so.0 #13 0xb6c7e26e in clone () from /lib/libc.so.6 Thread 1 (Thread 0xb5079800 (LWP 1625)): [KCrash Handler] #7 0xb5c49853 in mdb_get (txn=0xbfa1a928, dbi=7, key=0xbfa1a7b0, data=0xbfa1a7b8) at mdb.c:5417 #8 0xb746fe8a in Baloo::IdTreeDB::get (this=0xbfa1a82c, docId=0) at /usr/src/debug/baloo-5.16.0/src/engine/idtreedb.cpp:82 #9 0xb746c7cc in Baloo::DocumentUrlDB::getId (this=0xbfa1a884, docId=0, fileName=...) at /usr/src/debug/baloo-5.16.0/src/engine/documenturldb.cpp:186 #10 0xb747fbb9 in Baloo::Transaction::documentId (this=0xbfa1a910, path=...) at /usr/src/debug/baloo-5.16.0/src/engine/transaction.cpp:121 #11 0x0806e9f9 in Baloo::MetadataMover::removeMetadata (this=0x84a9538, tr=0xbfa1a910, url=...) at /usr/src/debug/baloo-5.16.0/src/file/metadatamover.cpp:74 #12 0x0806ead2 in Baloo::MetadataMover::removeFileMetadata (this=0x84a9538, file=...) at /usr/src/debug/baloo-5.16.0/src/file/metadatamover.cpp:66 #13 0x0806c212 in call (arg=0xbfa1aa38, o=0x84a9538, f=) at /usr/include/qt5/QtCore/qobjectdefs_impl.h:501 #14 call, void> (arg=0xbfa1aa38, o=0x84a9538, f=) at /usr/include/qt5/QtCore/qobjectdefs_impl.h:520 #15 QtPrivate::QSlotObject, void>::impl (which=1, this_=0x84a2358, r=0x84a9538, a=0xbfa1aa38, ret=0x0) at /usr/include/qt5/QtCore/qobject_impl.h:143 #16 0xb719b7a0 in call (a=0xbfa1aa38, r=0x84a9538, this=) at ../../src/corelib/kernel/qobject_impl.h:124 #17 QMetaObject::activate (sender=0x848b660, signalOffset=3, local_signal_index=3, argv=0xbfa1aa38) at kernel/qobject.cpp:3698 #18 0xb719c07d in QMetaObject::activate (sender=0x848b660, m=0x8092c08 , local_signal_index=3, argv=0xbfa1aa38) at kernel/qobject.cpp:3578 #19 0x08078525 in Baloo::PendingFileQueue::removeFileIndex (this=0x848b660, _t1=...) at /usr/src/debug/baloo-5.16.0/build/src/file/moc_pendingfilequeue.cpp:217 #20 0x0806cbd6 in Baloo::PendingFileQueue::processCache (this=0x848b660) at /usr/src/debug/baloo-5.16.0/src/file/pendingfilequeue.cpp:89 #21 0x0806de5b in call (arg=, o=0x848b660, f=) at /usr/include/qt5/QtCore/qobjectdefs_impl.h:501 #22 call, void> (arg=, o=0x848b660, f=) at /usr/include/qt5/QtCore/qobjectdefs_impl.h:520 #23 QtPrivate::QSlotObject, void>::impl(int, QtPrivate::QSlotObjectBase*, QObject*, void**, bool*) (which=1, this_=0x8499f70, r=0x848b660, a=0xbfa1ab4c, ret=0x0) at /usr/include/qt5/QtCore/qobject_impl.h:143 #24 0xb719b7a0 in call (a=0xbfa1ab4c, r=0x848b660, this=) at ../../src/corelib/kernel/qobject_impl.h:124 #25 QMetaObject::activate (sender=0x848b66c, signalOffset=3, local_signal_index=0, argv=0x0) at kernel/qobject.cpp:3698 #26 0xb719c07d in QMetaObject::activate (sender=0x848b66c, m=0xb73d64d0 , local_signal_index=0, argv=0x0) at kernel/qobject.cpp:3578 #27 0xb721aa22 in QTimer::timeout (this=0x848b66c) at .moc/moc_qtimer.cpp:197 #28 0xb71a7ff1 in QTimer::timerEvent (this=0x848b66c, e=0xbfa1ad30) at kernel/qtimer.cpp:247 #29 0xb719c67e in QObject::eve
[kdeconnect] [Bug 356914] New: Add an option to don't start playing media when call ends
https://bugs.kde.org/show_bug.cgi?id=356914 Bug ID: 356914 Summary: Add an option to don't start playing media when call ends Product: kdeconnect Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: common Assignee: albertv...@gmail.com Reporter: loic.dam...@gmail.com When a call end, the module which pause media when a call is received start the paused media. But when a call end, I may not be in front of my computer anymore, or at least ready to continue viewing what I was viewing. There should be an option to not start playing media when a call end. Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kactivities] [Bug 356910] No Ability to Edit Activities without Installing "Activities" widget
https://bugs.kde.org/show_bug.cgi?id=356910 Kai Uwe Broulik changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |WONTFIX CC||k...@privat.broulik.de --- Comment #1 from Kai Uwe Broulik --- Previously there was no indication whatsoever when switching activities with Meta+Tab, it is intended that it only serves as an Alt+Tab like switcher. To get the full blown UI you can use Meta+Q -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kactivities] [Bug 356910] No Ability to Edit Activities without Installing "Activities" widget
https://bugs.kde.org/show_bug.cgi?id=356910 --- Comment #2 from PGillespie --- (In reply to Kai Uwe Broulik from comment #1) > Previously there was no indication whatsoever when switching activities with > Meta+Tab, it is intended that it only serves as an Alt+Tab like switcher. To > get the full blown UI you can use Meta+Q Okay, thanks. Then I guess discoverability is the issue. I couldn't remember where to locate this key combination---got it into my head that Meta+Tab was the same as Meta+Q. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kactivities] [Bug 356910] No Ability to Edit Activities without Installing "Activities" widget
https://bugs.kde.org/show_bug.cgi?id=356910 --- Comment #3 from Kai Uwe Broulik --- If you right click your desktop there's an Activities entry in the context menu which should also show Meta+Q a its shortcut -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 356457] valgrind: m_mallocfree.c:2042 (vgPlain_arena_free): Assertion 'blockSane(a, b)' failed.
https://bugs.kde.org/show_bug.cgi?id=356457 --- Comment #5 from Philippe Waroquiers --- (In reply to Joost VandeVondele from comment #3) > just happened again, but it is really rare. (this is a 12 core server > running valgrind +-12h a day... and this seems to happen every +- 10 days). > Is any of the suggestions mentioned above possible without runtime overhead > and excessive IO ? Assuming you know which executable/test causes the bug, the first thing to try is the 'self-hosting', and run your test executable under valgrind self-hosted under itself. and/or run in a loop valgrind on the executable that gave the problem, with the options -v -v -v -d -d -d --vgdb-stop-at=valgrindabexit A failing run will then stop, and allow to examine the debug output of valgrind. The above will for sure consume CPU, but you can sleep during that time :) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356915] New: plasma crash after upgrading 13.2 to tumbleweed
https://bugs.kde.org/show_bug.cgi?id=356915 Bug ID: 356915 Summary: plasma crash after upgrading 13.2 to tumbleweed Product: plasmashell Version: 5.4.3 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: jinni...@bobsown.net CC: bhus...@gmail.com, plasma-b...@kde.org Application: plasmashell (5.4.3) Qt Version: 5.5.1 Operating System: Linux 4.3.0-2-default x86_64 Distribution: "openSUSE Tumbleweed (20151124) (x86_64)" -- Information about the crash: I upgraded 13.2 to tumbleweed via the 2015-12-17 snapshot dvd. On initial boot, Plasma crashed. I switched to the console, logged in as root and did a: killall -u bob The login screen appeared and I logged in to my user. Plasma again crashed The crash can be reproduced every time. -- Backtrace: Application: Plasma (plasmashell), signal: Aborted Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7effa1a54900 (LWP 2442))] Thread 7 (Thread 0x7eff895c2700 (LWP 2444)): #0 0x7eff9b00024d in poll () at /lib64/libc.so.6 #1 0x7eff9febd432 in () at /usr/lib64/libxcb.so.1 #2 0x7eff9febf007 in xcb_wait_for_event () at /usr/lib64/libxcb.so.1 #3 0x7eff8bd42e29 in () at /usr/lib64/libQt5XcbQpa.so.5 #4 0x7eff9b6f194f in () at /usr/lib64/libQt5Core.so.5 #5 0x7eff9a8074a4 in start_thread () at /lib64/libpthread.so.0 #6 0x7eff9b008bdd in clone () at /lib64/libc.so.6 Thread 6 (Thread 0x7eff81c6d700 (LWP 2454)): #0 0x7eff9affc22d in read () at /lib64/libc.so.6 #1 0x7eff92789f45 in () at /usr/lib64/tls/libnvidia-tls.so.340.96 #2 0x7eff97739210 in () at /usr/lib64/libglib-2.0.so.0 #3 0x7eff976f6d94 in g_main_context_check () at /usr/lib64/libglib-2.0.so.0 #4 0x7eff976f7208 in () at /usr/lib64/libglib-2.0.so.0 #5 0x7eff976f736c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #6 0x7eff9b91652b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #7 0x7eff9b8c063a in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #8 0x7eff9b6ecb1c in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #9 0x7eff9e9989a5 in () at /usr/lib64/libQt5Qml.so.5 #10 0x7eff9b6f194f in () at /usr/lib64/libQt5Core.so.5 #11 0x7eff9a8074a4 in start_thread () at /lib64/libpthread.so.0 #12 0x7eff9b008bdd in clone () at /lib64/libc.so.6 Thread 5 (Thread 0x7eff764a3700 (LWP 2460)): #0 0x7eff9a80fcfc in __lll_lock_wait () at /lib64/libpthread.so.0 #1 0x7eff9a809bb2 in pthread_mutex_lock () at /lib64/libpthread.so.0 #2 0x7eff96b09e90 in () at /usr/X11R6/lib64/libGL.so.1 #3 0x7eff96b0d41e in () at /usr/X11R6/lib64/libGL.so.1 #4 0x7eff96b0d81b in () at /usr/X11R6/lib64/libGL.so.1 #5 0x7eff92789fc0 in () at /usr/lib64/tls/libnvidia-tls.so.340.96 #6 0x7eff97739210 in () at /usr/lib64/libglib-2.0.so.0 #7 0x7eff976f6d94 in g_main_context_check () at /usr/lib64/libglib-2.0.so.0 #8 0x7eff976f7208 in () at /usr/lib64/libglib-2.0.so.0 #9 0x7eff976f736c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #10 0x7eff9b91652b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #11 0x7eff9b8c063a in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #12 0x7eff9b6ecb1c in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #13 0x7eff9e9989a5 in () at /usr/lib64/libQt5Qml.so.5 #14 0x7eff9b6f194f in () at /usr/lib64/libQt5Core.so.5 #15 0x7eff9a8074a4 in start_thread () at /lib64/libpthread.so.0 #16 0x7eff9b008bdd in clone () at /lib64/libc.so.6 Thread 4 (Thread 0x7eff749b9700 (LWP 2464)): #0 0x7eff9b00024d in poll () at /lib64/libc.so.6 #1 0x7eff976f7264 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7eff976f736c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7eff9b91652b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7eff9b8c063a in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7eff9b6ecb1c in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #6 0x7eff9e9989a5 in () at /usr/lib64/libQt5Qml.so.5 #7 0x7eff9b6f194f in () at /usr/lib64/libQt5Core.so.5 #8 0x7eff9a8074a4 in start_thread () at /lib64/libpthread.so.0 #9 0x7eff9b008bdd in clone () at /lib64/libc.so.6 Thread 3 (Thread 0x7eff6efbd700 (LWP 2465)): #0 0x7eff9a80d07f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7effa112ca84 in () at /usr/lib64/libQt5Script.so.5 #2 0x7effa112cac9 in () at /usr/lib64/libQt5Script.so.5 #3 0x7eff9a8074a4 in start_thread () at /lib64/libpthread.so.0 #4 0x7eff9b008bdd in clone () at /lib64
[plasmashell] [Bug 356916] New: Plasma 5.5 crashed when awaking
https://bugs.kde.org/show_bug.cgi?id=356916 Bug ID: 356916 Summary: Plasma 5.5 crashed when awaking Product: plasmashell Version: 5.5.1 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: kerryla...@islandnet.com CC: bhus...@gmail.com, plasma-b...@kde.org Application: plasmashell (5.5.1) Qt Version: 5.5.0 Operating System: Linux 4.1.13-5-default x86_64 Distribution: "openSUSE Leap 42.1 (x86_64)" -- Information about the crash: - What I was doing when the application crashed: My computer had been left on overnight and when I went to use it first thing in the morning, when the screen came back on, the crash reporting assistant was already in the bottom tray. I have two screens, and both were attached when the computer was left overnight and when I went to use it first thing in the morning. - Unusual behavior I noticed: As the screens came back on, one of the screens flickered unusually and very briefly displayed randomly spaced thin vertical lines near the centre of the screen. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f8f29202800 (LWP 12519))] Thread 19 (Thread 0x7f8f121e2700 (LWP 12523)): #0 0x7f8f22715c1d in poll () at /lib64/libc.so.6 #1 0x7f8f2764e422 in () at /usr/lib64/libxcb.so.1 #2 0x7f8f2765000f in xcb_wait_for_event () at /usr/lib64/libxcb.so.1 #3 0x7f8f14964c29 in () at /usr/lib64/libQt5XcbQpa.so.5 #4 0x7f8f22e0c55f in () at /usr/lib64/libQt5Core.so.5 #5 0x7f8f21f1f0a4 in start_thread () at /lib64/libpthread.so.0 #6 0x7f8f2271e04d in clone () at /lib64/libc.so.6 Thread 18 (Thread 0x7f8f0afc9700 (LWP 12530)): #0 0x7f8f22715c1d in poll () at /lib64/libc.so.6 #1 0x7f8f1edf5e64 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7f8f1edf5f7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7f8f2303da5b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7f8f22fe4a63 in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7f8f22e0784a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #6 0x7f8f261105f8 in () at /usr/lib64/libQt5Qml.so.5 #7 0x7f8f22e0c55f in () at /usr/lib64/libQt5Core.so.5 #8 0x7f8f21f1f0a4 in start_thread () at /lib64/libpthread.so.0 #9 0x7f8f2271e04d in clone () at /lib64/libc.so.6 Thread 17 (Thread 0x7f8efeb22700 (LWP 12531)): #0 0x7f8f22711ced in read () at /lib64/libc.so.6 #1 0x7f8f1a8c4073 in () at /usr/lib64/tls/libnvidia-tls.so.358.16 #2 0x7f8f1ee36b60 in () at /usr/lib64/libglib-2.0.so.0 #3 0x7f8f1edf5999 in g_main_context_check () at /usr/lib64/libglib-2.0.so.0 #4 0x7f8f1edf5df8 in () at /usr/lib64/libglib-2.0.so.0 #5 0x7f8f1edf5f7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #6 0x7f8f2303da5b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #7 0x7f8f22fe4a63 in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #8 0x7f8f22e0784a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #9 0x7f8f261105f8 in () at /usr/lib64/libQt5Qml.so.5 #10 0x7f8f22e0c55f in () at /usr/lib64/libQt5Core.so.5 #11 0x7f8f21f1f0a4 in start_thread () at /lib64/libpthread.so.0 #12 0x7f8f2271e04d in clone () at /lib64/libc.so.6 Thread 16 (Thread 0x7f8efd27a700 (LWP 12532)): #0 0x7f8f22711ced in read () at /lib64/libc.so.6 #1 0x7f8f1a8c4073 in () at /usr/lib64/tls/libnvidia-tls.so.358.16 #2 0x7f8f1ee36b60 in () at /usr/lib64/libglib-2.0.so.0 #3 0x7f8f1edf5999 in g_main_context_check () at /usr/lib64/libglib-2.0.so.0 #4 0x7f8f1edf5df8 in () at /usr/lib64/libglib-2.0.so.0 #5 0x7f8f1edf5f7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #6 0x7f8f2303da5b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #7 0x7f8f22fe4a63 in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #8 0x7f8f22e0784a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #9 0x7f8f261105f8 in () at /usr/lib64/libQt5Qml.so.5 #10 0x7f8f22e0c55f in () at /usr/lib64/libQt5Core.so.5 #11 0x7f8f21f1f0a4 in start_thread () at /lib64/libpthread.so.0 #12 0x7f8f2271e04d in clone () at /lib64/libc.so.6 Thread 15 (Thread 0x7f8ef77ba700 (LWP 12533)): #0 0x7f8f21f2305f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f8f288d37eb in () at /usr/lib64/libQt5Script.so.5 #2 0x7f8f288d3819 in () at /usr/lib64/libQt5Script.so.5 #3 0x7f8f21f1f0a4 in start_thread () at /lib64/libpthread.so.0 #4 0x7f8f2271e04d in clone () at /lib64/li
[valgrind] [Bug 356457] valgrind: m_mallocfree.c:2042 (vgPlain_arena_free): Assertion 'blockSane(a, b)' failed.
https://bugs.kde.org/show_bug.cgi?id=356457 --- Comment #6 from Philippe Waroquiers --- (In reply to Kim Rosberg from comment #4) > I'm experience exactly the same behavior. But the interval is between +-4 > days and I'm running multiple servers 24h. > > ==247219== Memcheck, a memory error detector > ==247219== Copyright (C) 2002-2013, and GNU GPL'd, by Julian Seward et al. > ==247219== Using Valgrind-3.11.0 and LibVEX; rerun with -h for copyright info > ==247219== Command: some test.elf > ==247219== Parent PID: 247218 > ==247219== > blockSane: fail -- redzone-hi > > valgrind: m_mallocfree.c:2047 (vgPlain_arena_free): Assertion 'blockSane(a, > b)' failed. The above line nr is strange. There is no assertion at line 2047. There is one at line 2042. It would be good if you could (both) indicate which distribution and libraries your executables are using : this might give a hint about the origin. I am now re-running all valgrind tests under itself on a amd64 Debian 7, just in case. -- You are receiving this mail because: You are watching all bug changes.
[konversation] [Bug 356917] New: Can Konversation support server-time
https://bugs.kde.org/show_bug.cgi?id=356917 Bug ID: 356917 Summary: Can Konversation support server-time Product: konversation Version: 1.6 Platform: Kubuntu Packages OS: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: general Assignee: konversation-de...@kde.org Reporter: marco_pari...@hotmail.com I asked this question in https://forum.kde.org/viewtopic.php?f=18&t=130124, but maybe it is a wishlist item. I would like to be able to retrieve the actual timestamps from the KDE Bouncer. -- You are receiving this mail because: You are watching all bug changes.
[konversation] [Bug 356917] Can Konversation support server-time
https://bugs.kde.org/show_bug.cgi?id=356917 Marco Parillo changed: What|Removed |Added URL||https://forum.kde.org/viewt ||opic.php?f=18&t=130124 -- You are receiving this mail because: You are watching all bug changes.
[kdesvn] [Bug 329835] Add a menu entry to ignore files
https://bugs.kde.org/show_bug.cgi?id=329835 Christian Ehrlicher changed: What|Removed |Added CC||ch.ehrlic...@gmx.de Resolution|--- |FIXED Status|UNCONFIRMED |RESOLVED --- Comment #1 from Christian Ehrlicher --- A menu entry to ignore/unignore unversioned files was added with 93a316c616b7d2c90670a50ee50f9e08df448a9a -- You are receiving this mail because: You are watching all bug changes.
[kscreensaver] [Bug 316348] kscreenlocker_greet constantly consumes around 20% CPU time
https://bugs.kde.org/show_bug.cgi?id=316348 apetro...@gmail.com changed: What|Removed |Added CC|apetro...@gmail.com | -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356916] Plasma 5.5 crashed when awaking
https://bugs.kde.org/show_bug.cgi?id=356916 d...@kaosx.us changed: What|Removed |Added CC||d...@kaosx.us -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356918] New: Plasma crashed after last update
https://bugs.kde.org/show_bug.cgi?id=356918 Bug ID: 356918 Summary: Plasma crashed after last update Product: plasmashell Version: 5.5.1 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: aders1...@gmail.com CC: bhus...@gmail.com, plasma-b...@kde.org Application: plasmashell (5.5.1) Qt Version: 5.5.1 Operating System: Linux 4.3.0-2-default x86_64 Distribution: "openSUSE Tumbleweed (20151124) (x86_64)" -- Information about the crash: After last update Opensuse Tumbleweed to 20151217 and reboot plasma crashed. The crash can be reproduced every time. -- Backtrace: Application: Плазма (plasmashell), signal: Aborted Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7fcccf29d900 (LWP 1867))] Thread 3 (Thread 0x7fccb6f44700 (LWP 1875)): #0 0x7fccc883624d in poll () at /lib64/libc.so.6 #1 0x7fcccd708432 in () at /usr/lib64/libxcb.so.1 #2 0x7fcccd70a007 in xcb_wait_for_event () at /usr/lib64/libxcb.so.1 #3 0x7fccb96c4e29 in () at /usr/lib64/libQt5XcbQpa.so.5 #4 0x7fccc8f2794f in () at /usr/lib64/libQt5Core.so.5 #5 0x7fccc803d4a4 in start_thread () at /lib64/libpthread.so.0 #6 0x7fccc883ebdd in clone () at /lib64/libc.so.6 Thread 2 (Thread 0x7fccaf5ef700 (LWP 1882)): #0 0x7fccc883222d in read () at /lib64/libc.so.6 #1 0x7fccbffd7f75 in () at /usr/lib64/tls/libnvidia-tls.so.352.63 #2 0x7fccc4f6d210 in () at /usr/lib64/libglib-2.0.so.0 #3 0x7fccc4f2ad94 in g_main_context_check () at /usr/lib64/libglib-2.0.so.0 #4 0x7fccc4f2b208 in () at /usr/lib64/libglib-2.0.so.0 #5 0x7fccc4f2b36c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #6 0x7fccc914c52b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #7 0x7fccc90f663a in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #8 0x7fccc8f22b1c in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #9 0x7f1ef9a5 in () at /usr/lib64/libQt5Qml.so.5 #10 0x7fccc8f2794f in () at /usr/lib64/libQt5Core.so.5 #11 0x7fccc803d4a4 in start_thread () at /lib64/libpthread.so.0 #12 0x7fccc883ebdd in clone () at /lib64/libc.so.6 Thread 1 (Thread 0x7fcccf29d900 (LWP 1867)): [KCrash Handler] #6 0x7fccc8789d38 in raise () at /lib64/libc.so.6 #7 0x7fccc878b18a in abort () at /lib64/libc.so.6 #8 0x7fccc8f1582e in () at /usr/lib64/libQt5Core.so.5 #9 0x7fccb96e04f5 in QXcbWindow::create() () at /usr/lib64/libQt5XcbQpa.so.5 #10 0x7fccb5af7259 in () at /usr/lib64/qt5/plugins/xcbglintegrations/libqxcb-egl-integration.so #11 0x7fccb96cc721 in QXcbIntegration::createPlatformWindow(QWindow*) const () at /usr/lib64/libQt5XcbQpa.so.5 #12 0x7fccc96430d7 in QWindowPrivate::create(bool) () at /usr/lib64/libQt5Gui.so.5 #13 0x7fccc9643368 in QWindow::winId() const () at /usr/lib64/libQt5Gui.so.5 #14 0x7fcccecc3b4d in PlasmaQuick::Dialog::setType(PlasmaQuick::Dialog::WindowType) () at /usr/lib64/libKF5PlasmaQuick.so.5 #15 0x7fcccecc6a9e in () at /usr/lib64/libKF5PlasmaQuick.so.5 #16 0x7fcccecc816b in PlasmaQuick::Dialog::qt_metacall(QMetaObject::Call, int, void**) () at /usr/lib64/libKF5PlasmaQuick.so.5 #17 0x7f159d80 in QQmlVMEMetaObject::metaCall(QMetaObject::Call, int, void**) () at /usr/lib64/libQt5Qml.so.5 #18 0x7f172bbc in QQmlPropertyPrivate::writeBinding(QObject*, QQmlPropertyData const&, QQmlContextData*, QQmlJavaScriptExpression*, QV4::Value const&, bool, QFlags) () at /usr/lib64/libQt5Qml.so.5 #19 0x7f1dc775 in QQmlBinding::update(QFlags) () at /usr/lib64/libQt5Qml.so.5 #20 0x7f1e5786 in () at /usr/lib64/libQt5Qml.so.5 #21 0x7f178eca in () at /usr/lib64/libQt5Qml.so.5 #22 0x7f179adc in QQmlIncubationController::incubateFor(int) () at /usr/lib64/libQt5Qml.so.5 #23 0x7fcccd247bac in () at /usr/lib64/libKF5Declarative.so.5 #24 0x7f179949 in QQmlEnginePrivate::incubate(QQmlIncubator&, QQmlContextData*) () at /usr/lib64/libQt5Qml.so.5 #25 0x7f1752ec in QQmlComponent::create(QQmlIncubator&, QQmlContext*, QQmlContext*) () at /usr/lib64/libQt5Qml.so.5 #26 0x7fcccd244a65 in KDeclarative::QmlObject::completeInitialization(QHash const&) () at /usr/lib64/libKF5Declarative.so.5 #27 0x7fcccd244b0c in () at /usr/lib64/libKF5Declarative.so.5 #28 0x7fcccd244ca9 in () at /usr/lib64/libKF5Declarative.so.5 #29 0x004668bb in Osd::Osd(ShellCorona*) () #30 0x00459d82 in ShellCorona::ShellCorona(QObject*) () #31 0x00462fc9 in ShellManager::loadHandlers() () #32 0x7fccc9126d79 in QObject::event(QEvent*) () at /usr/lib64/libQt5Core.so.5 #33 0x7fccca46f8cc in QApplicationPrivate::notify_helper(
[konsole] [Bug 343803] Konsole keeps running in background after closing window with nvidia drivers
https://bugs.kde.org/show_bug.cgi?id=343803 --- Comment #33 from jeremy9...@gmail.com --- These seems to be duplicates : bug 350475, bug 354965, bug 351587 -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 350475] konsole uses 100% cpu
https://bugs.kde.org/show_bug.cgi?id=350475 Rex Dieter changed: What|Removed |Added Resolution|--- |DUPLICATE Status|UNCONFIRMED |RESOLVED CC||rdie...@math.unl.edu --- Comment #2 from Rex Dieter --- *** This bug has been marked as a duplicate of bug 343803 *** -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 343803] Konsole keeps running in background after closing window with nvidia drivers
https://bugs.kde.org/show_bug.cgi?id=343803 --- Comment #35 from Rex Dieter --- *** Bug 351587 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 351587] konsole does not end when closing window
https://bugs.kde.org/show_bug.cgi?id=351587 Rex Dieter changed: What|Removed |Added CC||rdie...@math.unl.edu Resolution|--- |DUPLICATE Status|UNCONFIRMED |RESOLVED --- Comment #4 from Rex Dieter --- *** This bug has been marked as a duplicate of bug 343803 *** -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 343803] Konsole keeps running in background after closing window with nvidia drivers
https://bugs.kde.org/show_bug.cgi?id=343803 Rex Dieter changed: What|Removed |Added CC||illumil...@gmail.com --- Comment #34 from Rex Dieter --- *** Bug 350475 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kblocks] [Bug 264088] It should not be possible to pause the game before starting it
https://bugs.kde.org/show_bug.cgi?id=264088 Julian Helfferich changed: What|Removed |Added CC||julian.helfferich@googlemai ||l.com Resolution|--- |FIXED Status|UNCONFIRMED |RESOLVED --- Comment #5 from Julian Helfferich --- Git commit 6879ab00fbbda433174bb3fa8b8de8bcc7c950a8 by Julian Helfferich. Committed on 17/12/2015 at 02:26. Pushed by helfferich into branch 'master'. Deactivate pause button when no game is running Before, the pause button was always activated even when no game was running. This lead to undesired behavior, e.g. making it necessary to press the pause button twice to pause the game. With this fix, the pause button is deactivated on startup. The button gets activated when a game is started and when the button is pressed, it checks whether there is a running game. REVIEW: 126200 M +17 -0KBlocksWin.cpp http://commits.kde.org/kblocks/6879ab00fbbda433174bb3fa8b8de8bcc7c950a8 -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 354965] Konsole 100% CPU usage after using sshfs
https://bugs.kde.org/show_bug.cgi?id=354965 Rex Dieter changed: What|Removed |Added CC||rdie...@math.unl.edu --- Comment #1 from Rex Dieter --- Are you using nvidia binary driver? If so, good chance this is a dup of bug #343803 -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 356902] Starters are visually indistinguishable from listed tasks in the task manager widget on breeze light
https://bugs.kde.org/show_bug.cgi?id=356902 Eike Hein changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|UNCONFIRMED |NEEDSINFO CC||h...@kde.org --- Comment #2 from Eike Hein --- Can you specify your KF5 version? The theme is shipped with plasma-framework. On my system running tasks have a rectangle around the button contents. -- You are receiving this mail because: You are watching all bug changes.
[forum.kde.org] [Bug 322866] KDE Identity: knowledge of username is required to reset password and to obtain information about username
https://bugs.kde.org/show_bug.cgi?id=322866 Alexandre Pereira changed: What|Removed |Added CC||pereira.a...@gmail.com --- Comment #50 from Alexandre Pereira --- ... Would it be possible to also know my username ? My email is pereira.a...@gmail.com It should be a combination of "pereira" and "alex" words, but cannot figure it out. Thanks -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 340489] All windows in KDE 5 starts glitching after some usage time
https://bugs.kde.org/show_bug.cgi?id=340489 --- Comment #36 from Filip --- I am experiencing a significant increase in glitching since I started playing Xonotic (the game also crashes Kwin in most cases). One thing I forgot to mention was that I did not experience these issues in KDE 4, on the same hardware. As I mentioned before, disabling the two suggested variables and enabling full scene repaints does not help, but since I might not have set things up properly, I will attach a screenshot. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 340489] All windows in KDE 5 starts glitching after some usage time
https://bugs.kde.org/show_bug.cgi?id=340489 --- Comment #37 from Filip --- Created attachment 96201 --> https://bugs.kde.org/attachment.cgi?id=96201&action=edit kwin variables -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 355936] 15.11.90: Spacer tool moves transitions of locked tracks
https://bugs.kde.org/show_bug.cgi?id=355936 --- Comment #2 from wegwerf-1-...@gmx.de --- I still *do* reproduce using 15.12.0 from git Applications/15.12. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 355936] 15.11.90: Spacer tool moves transitions of locked tracks
https://bugs.kde.org/show_bug.cgi?id=355936 --- Comment #3 from wegwerf-1-...@gmx.de --- More details: 1. I can reproduce using an existing 15.11.90 project loaded into 15.12.0. 2. I cannot reproduce on a new 15.12.0 project. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 355936] 15.11.90: Spacer tool moves transitions of locked tracks
https://bugs.kde.org/show_bug.cgi?id=355936 --- Comment #4 from wegwerf-1-...@gmx.de --- More details: 1. Add an existing 15.11.90 project as a clip to a new 15.12.0 project. 2. Drag clip into timeline. 3. Timeline > Current Clip > Expand Clip 4. Lock first track with clip & transition. Now, "move" mode correctly doesn't touch the transition on the first clip anymore. But when using the project directly, problem persists. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 355936] 15.11.90: Spacer tool moves transitions of locked tracks
https://bugs.kde.org/show_bug.cgi?id=355936 --- Comment #5 from wegwerf-1-...@gmx.de --- Finally found out while working on a minimized test case that unlocking and locking the track causes some MLT/project state cleanup in that then locking works as expected, so that "move" mode doesn't move the locked transition anymore. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 355936] 15.11.90: Spacer tool moves transitions of locked tracks
https://bugs.kde.org/show_bug.cgi?id=355936 --- Comment #6 from wegwerf-1-...@gmx.de --- Created attachment 96202 --> https://bugs.kde.org/attachment.cgi?id=96202&action=edit locked track transition selection bug testcase 1. Load test case project into Kdenlive 15.12.0; tell Kdenlive to replace missing clip with placeholder. 2. Do *not* unlock topmost track. Enter move mode by keying "m". Then select clip on track 2. Note how the transition on locked track 1 gets selected too. 3. Unlock track 1, immediately lock it again. 4. Select clip on track 2 again, notice that locked transition doesn't get selected anymore. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 355936] 15.11.90: Spacer tool moves transitions of locked tracks
https://bugs.kde.org/show_bug.cgi?id=355936 --- Comment #7 from wegwerf-1-...@gmx.de --- Created and attached testcase project showing the bug being present still on 15.12.0. 1. Load test case project into Kdenlive 15.12.0; tell Kdenlive to replace missing clip with placeholder. 2. Do *not* unlock topmost track. Enter move mode by keying "m". Then select clip on track 2. Note how the transition on locked track 1 gets selected too. 3. Unlock track 1, immediately lock it again. 4. Select clip on track 2 again, notice that locked transition doesn't get selected anymore. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 356919] New: Crash when app is closed
https://bugs.kde.org/show_bug.cgi?id=356919 Bug ID: 356919 Summary: Crash when app is closed Product: krita Version: unspecified Platform: unspecified OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: krita-bugs-n...@kde.org Reporter: danielmwo...@gmail.com Application: krita () Qt Version: 5.5.1 Operating System: Linux 4.2.6-1 x86_64 Distribution: "KaOS" -- Information about the crash: Every time Krite is closed it crashes with a segfault. I'm using KaOS. The crash can be reproduced every time. -- Backtrace: Application: krita (krita), signal: Segmentation fault Using host libthread_db library "/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7fa8b0be6800 (LWP 4648))] Thread 6 (Thread 0x7fa8777fe700 (LWP 4659)): #0 0x7fa8ae5fe33c in pselect () from /lib/libc.so.6 #1 0x7fa8af0b81dc in qt_safe_select(int, fd_set*, fd_set*, fd_set*, timespec const*) () from /usr/lib/libQt5Core.so.5 #2 0x7fa8af0b9c65 in QEventDispatcherUNIXPrivate::doSelect(QFlags, timespec*) () from /usr/lib/libQt5Core.so.5 #3 0x7fa8af0ba171 in QEventDispatcherUNIX::processEvents(QFlags) () from /usr/lib/libQt5Core.so.5 #4 0x7fa8af064022 in QEventLoop::exec(QFlags) () from /usr/lib/libQt5Core.so.5 #5 0x7fa8aee8285c in QThread::exec() () from /usr/lib/libQt5Core.so.5 #6 0x7fa8aee8772f in ?? () from /usr/lib/libQt5Core.so.5 #7 0x7fa8a97bf374 in start_thread () from /lib/libpthread.so.0 #8 0x7fa8ae60532d in clone () from /lib/libc.so.6 Thread 5 (Thread 0x7fa87d46c700 (LWP 4660)): #0 0x7fa8a97c49af in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/libpthread.so.0 #1 0x7fa8aee8879b in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib/libQt5Core.so.5 #2 0x7fa8aee814ab in QSemaphore::acquire(int) () from /usr/lib/libQt5Core.so.5 #3 0x7fa8acca094e in ?? () from /usr/lib/libkritaimage.so.15 #4 0x7fa8acca13e1 in ?? () from /usr/lib/libkritaimage.so.15 #5 0x7fa8aee8772f in ?? () from /usr/lib/libQt5Core.so.5 #6 0x7fa8a97bf374 in start_thread () from /lib/libpthread.so.0 #7 0x7fa8ae60532d in clone () from /lib/libc.so.6 Thread 4 (Thread 0x7fa88a38e700 (LWP 4661)): #0 0x7fa8a97c49af in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/libpthread.so.0 #1 0x7fa8aee8879b in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib/libQt5Core.so.5 #2 0x7fa8aee81736 in QSemaphore::tryAcquire(int, int) () from /usr/lib/libQt5Core.so.5 #3 0x7fa8accbd7ca in KisTileDataSwapper::run() () from /usr/lib/libkritaimage.so.15 #4 0x7fa8aee8772f in ?? () from /usr/lib/libQt5Core.so.5 #5 0x7fa8a97bf374 in start_thread () from /lib/libpthread.so.0 #6 0x7fa8ae60532d in clone () from /lib/libc.so.6 Thread 3 (Thread 0x7fa877fff700 (LWP 4664)): #0 0x7fa8aee7f7ba in QMutex::lock() () from /usr/lib/libQt5Core.so.5 #1 0x7fa8af0ba07b in QEventDispatcherUNIX::processEvents(QFlags) () from /usr/lib/libQt5Core.so.5 #2 0x7fa8af064022 in QEventLoop::exec(QFlags) () from /usr/lib/libQt5Core.so.5 #3 0x7fa8aee8285c in QThread::exec() () from /usr/lib/libQt5Core.so.5 #4 0x7fa8aee8772f in ?? () from /usr/lib/libQt5Core.so.5 #5 0x7fa8a97bf374 in start_thread () from /lib/libpthread.so.0 #6 0x7fa8ae60532d in clone () from /lib/libc.so.6 Thread 2 (Thread 0x7fa86ab6e700 (LWP 4667)): #0 0x7fa8aee7f7ba in QMutex::lock() () from /usr/lib/libQt5Core.so.5 #1 0x7fa8af0ba07b in QEventDispatcherUNIX::processEvents(QFlags) () from /usr/lib/libQt5Core.so.5 #2 0x7fa8af064022 in QEventLoop::exec(QFlags) () from /usr/lib/libQt5Core.so.5 #3 0x7fa8aee8285c in QThread::exec() () from /usr/lib/libQt5Core.so.5 #4 0x7fa8aee8772f in ?? () from /usr/lib/libQt5Core.so.5 #5 0x7fa8a97bf374 in start_thread () from /lib/libpthread.so.0 #6 0x7fa8ae60532d in clone () from /lib/libc.so.6 Thread 1 (Thread 0x7fa8b0be6800 (LWP 4648)): [KCrash Handler] #5 0x in ?? () #6 0x7fa8b061b888 in KisOpenGLImageTextures::destroyImageTextureTiles() () from /usr/lib/libkritaui.so.15 #7 0x7fa8b061f895 in KisOpenGLImageTextures::~KisOpenGLImageTextures() () from /usr/lib/libkritaui.so.15 #8 0x7fa8b061fa99 in KisOpenGLImageTextures::~KisOpenGLImageTextures() () from /usr/lib/libkritaui.so.15 #9 0x7fa8b0780bf4 in KisAnimationFrameCache::~KisAnimationFrameCache() () from /usr/lib/libkritaui.so.15 #10 0x7fa8b0780c59 in KisAnimationFrameCache::~KisAnimationFrameCache() () from /usr/lib/libkritaui.so.15 #11 0x7fa8828908ae in TimelineFramesModel::~TimelineFramesModel() () from /usr/lib/krita/kritaanimationdocker.so #12 0x7fa8828908c9 in TimelineFramesModel::~TimelineFramesModel() () from /usr/lib/krita/kritaanimationdocker.so #13 0x7fa8af0939bc in QObjectPrivate::deleteChildren() () from
[kdenlive] [Bug 355936] 15.12.0: Spacer tool moves transitions of locked tracks
https://bugs.kde.org/show_bug.cgi?id=355936 wegwerf-1-...@gmx.de changed: What|Removed |Added Summary|15.11.90: Spacer tool moves |15.12.0: Spacer tool moves |transitions of locked |transitions of locked |tracks |tracks -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 356030] 15.11.80: track speaker icon coloring is ambiguous and inconsistent with other track icons
https://bugs.kde.org/show_bug.cgi?id=356030 wegwerf-1-...@gmx.de changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #9 from wegwerf-1-...@gmx.de --- Fixed in 15.12.0. Many thanks! -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 356920] New: klauncher said: Unknown protocol 'krarc'
https://bugs.kde.org/show_bug.cgi?id=356920 Bug ID: 356920 Summary: klauncher said: Unknown protocol 'krarc' Product: krusader Version: Git Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: krarc Assignee: m...@fork.pl Reporter: a...@gaydenko.com KDE 15.08.3 is in use with Krusader from current git. On hitting enter on pdf file inside zip archive Okular shows error "Could not open krarc:/some/path/to.zip/file.pdf. Reason: Could not start process Unable to create io-slave: klauncher said: Unknown protocol 'krarc'." F3 opens the file with lister in hex mode. -- You are receiving this mail because: You are watching all bug changes.
[kompare] [Bug 356921] New: Unwanted debug output
https://bugs.kde.org/show_bug.cgi?id=356921 Bug ID: 356921 Summary: Unwanted debug output Product: kompare Version: 4.1.3 Platform: Compiled Sources OS: All Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: kompare-de...@kde.org Reporter: rjvber...@gmail.com Kompare somehow activates output from qCDebug(), which generates a *lot* of things I do not want to see by default. Other applications using QLoggingCategory are appropriately silent by default for me, so I presume Kompare must activate logging output. I just haven't discovered yet where. Reproducible: Always Steps to Reproduce: 1. start kompare from a terminal Actual Results: Debugging statement pollution. Expected Results: Only important error messages should show up in release software (this is KDE Applications 15.12, not exactly a version number that screams pre-alpha quality). -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kdeclarative] [Bug 356529] I18N_PLURAL_ARGUMENT_MISSING in various places
https://bugs.kde.org/show_bug.cgi?id=356529 MiRacLe changed: What|Removed |Added CC||mira...@rpz.name -- You are receiving this mail because: You are watching all bug changes.
[telepathy] [Bug 354949] Can't connect to gtalk account (Authentication failed: invalid-authzid)
https://bugs.kde.org/show_bug.cgi?id=354949 MiRacLe changed: What|Removed |Added CC||mira...@rpz.name -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 356882] No compositing with Mesa 11.1.0 (EGL 1.5) and Plasma/KWin 5.5.1 when using EGL OpenGL interface
https://bugs.kde.org/show_bug.cgi?id=356882 --- Comment #4 from Dennis Schridde --- (In reply to Thomas Lübking from comment #3) > > libkwinglutils: Update of color profiles failed > > Color correction related? Probably. But that's the output when using GLX. It does not explain why EGL does not work at all. > Otherwise let's get us some more debug out: > > echo -e '*.debug=true\n*.warning=true' > ~/.config/kdelogging.ini > QT_LOGGING_CONF=~/.config/kdelogging.ini kwin_x11 --replace & Does not add any output at all: # cat .config/kdelogging.ini *.debug=true *.warning=true # env QT_LOGGING_CONF=~/.config/kdelogging.ini kwin_x11 --replace QXcbConnection: XCB error: 3 (BadWindow), sequence: 172, resource id: 127926278, major code: 20 (GetProperty), minor code: 0 kwin_core: Failed to initialize compositing, compositing disabled QXcbConnection: XCB error: 3 (BadWindow), sequence: 1979, resource id: 111, major code: 3 (GetWindowAttributes), minor code: 0 QXcbConnection: XCB error: 9 (BadDrawable), sequence: 1980, resource id: 111, major code: 14 (GetGeometry), minor code: 0 -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 356920] klauncher said: Unknown protocol 'krarc'
https://bugs.kde.org/show_bug.cgi?id=356920 Andrew Gaydenko changed: What|Removed |Added Platform|Other |Archlinux Packages -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 352924] delayed crash upon any pen input anywhere within main window
https://bugs.kde.org/show_bug.cgi?id=352924 --- Comment #9 from jeffrey.thr...@gmail.com --- Thank you for responding. I know it's probably not a simple fix, but since my Adesso tablet works fine in the latest stable versions of Blender, Gimp, and other drawing software, I thought I should report the bug anyway. I'm no programming expert, but is there any way you can collaborate with the coders behind the abovementioned software to help with this bug? On Dec 14, 2015 1:21 AM, "Boudewijn Rempt via KDE Bugzilla" < bugzilla_nore...@kde.org> wrote: > https://bugs.kde.org/show_bug.cgi?id=352924 > > --- Comment #8 from Boudewijn Rempt --- > Well, in Krita 3.0 the tablet code is rewritten once again. In 2.8 we used > Qt's > code, but that didn't support a whole bunch of tablets. In 2.9, we had our > own > code on Windows and X11, but the variety of hardware out there is really > hard > to support. Especially cheaper tablets send out really strange data, and > it is > really hard to predict what we're getting. In 3.0, we've done another > rewrite... I still hope to have 3.0 pre-alpha packages out before the end > of > the year, ready for testing. > > -- > 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.
