[konsole] [Bug 155603] Konsole needs an easy way to resize the window to 80 columns
https://bugs.kde.org/show_bug.cgi?id=155603 Darin McBride changed: What|Removed |Added CC||tankta...@gmail.com --- Comment #27 from Darin McBride --- (In reply to Vaso from comment #26) > So properties like TerminalColumns and TerminalRows are still ignoring by > konsole FYI, with konsole 20.12.3, KDE Frameworks 5.84.0, Qt 5.15.2 on Gentoo, these properties appear to work for me. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 440284] New: No way to reset opacity to full once changed with mouse wheel
https://bugs.kde.org/show_bug.cgi?id=440284 Bug ID: 440284 Summary: No way to reset opacity to full once changed with mouse wheel Product: kwin Version: 5.22.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: compositing Assignee: kwin-bugs-n...@kde.org Reporter: tankta...@gmail.com Target Milestone: --- SUMMARY Having set the "Window Management -> Window Behavior -> Window Actions -> Inner Window, Titlebar and Frame Actions -> Mouse wheel" option to "Change opacity", I am finding that, once I've changed a window's opacity to be something other than full opacity, I cannot scroll the wheel with the modifier key pressed to get it back to full opacity. Further, the scroll wheel action still bleeds through to the underlying window, scrolling my browser window, for example. STEPS TO REPRODUCE 1. Set "Window Management -> Window Behavior -> Window Actions -> Inner Window, Titlebar and Frame Actions -> Mouse wheel" to "Change opacity" 2. Use your modifier key while scrolling the wheel. 3. Try to scroll back to full opacity OBSERVED RESULT Opacity cannot return to full. EXPECTED RESULT Can get the opacity back to 100% SOFTWARE/OS VERSIONS Windows: - macOS: - Linux/KDE Plasma: 5.22.3 (available in About System) KDE Plasma Version: 5.22.3 KDE Frameworks Version: 5.84.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION Gentoo, NVidia binary driver, GeForce GTX 1050 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 440284] No way to reset opacity to full once changed with mouse wheel
https://bugs.kde.org/show_bug.cgi?id=440284 Darin McBride changed: What|Removed |Added Platform|Other |Flatpak -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 440284] No way to reset opacity to full once changed with mouse wheel
https://bugs.kde.org/show_bug.cgi?id=440284 Darin McBride changed: What|Removed |Added Platform|Flatpak |Gentoo Packages -- You are receiving this mail because: You are watching all bug changes.
[ktorrent] [Bug 473111] New: Opening magnet immediately crashes
https://bugs.kde.org/show_bug.cgi?id=473111
Bug ID: 473111
Summary: Opening magnet immediately crashes
Classification: Applications
Product: ktorrent
Version: 23.04.3
Platform: Compiled Sources
OS: Linux
Status: REPORTED
Keywords: drkonqi
Severity: crash
Priority: NOR
Component: general
Assignee: joris.guis...@gmail.com
Reporter: tankta...@gmail.com
Target Milestone: ---
Application: ktorrent (23.04.3)
(Compiled from sources)
Qt Version: 5.15.10
Frameworks Version: 5.108.0
Operating System: Linux 6.1.12-gentoo x86_64
Windowing System: X11
Distribution: "Gentoo Linux"
DrKonqi: 5.27.7 [KCrashBackend]
-- Information about the crash:
Whether ktorrent is started from chrome with the magnet or I use the open url
option inside ktorrent, I get a crash.
The crash can be reproduced every time.
-- Backtrace:
Application: KTorrent (ktorrent), signal: Aborted
Content of s_kcrashErrorMessage: std::unique_ptr = {get() = 0x0}
[KCrash Handler]
#6 __pthread_kill_implementation (threadid=,
signo=signo@entry=6, no_tid=no_tid@entry=0) at pthread_kill.c:44
#7 0x7f9f1658ed6f in __pthread_kill_internal (signo=6, threadid=) at pthread_kill.c:78
#8 0x7f9f16541532 in __GI_raise (sig=sig@entry=6) at
../sysdeps/posix/raise.c:26
#9 0x7f9f1652b4b2 in __GI_abort () at abort.c:79
#10 0x7f9f18d4fcc3 in bt::QtMessageOutput (type=, msg=...)
at
/var/tmp/portage/net-libs/libktorrent-23.04.3/work/libktorrent-23.04.3/src/util/log.cpp:296
#11 0x7f9f16adaf20 in qt_message_print (msgType=msgType@entry=QtFatalMsg,
context=..., message=...) at
/var/tmp/portage/dev-qt/qtcore-5.15.10/work/qtbase-everywhere-src-5.15.10/src/corelib/global/qlogging.cpp:1843
#12 0x7f9f16adb078 in qt_message(QtMsgType, const QMessageLogContext &,
const char *, typedef __va_list_tag __va_list_tag *)
(msgType=msgType@entry=QtFatalMsg, context=..., msg=msg@entry=0x7f9f16dd1988
"ASSERT: \"%s\" in file %s, line %d", ap=ap@entry=0x7ffc69129720) at
/var/tmp/portage/dev-qt/qtcore-5.15.10/work/qtbase-everywhere-src-5.15.10/src/corelib/global/qlogging.cpp:378
#13 0x7f9f16a85036 in QMessageLogger::fatal
(this=this@entry=0x7ffc69129808, msg=msg@entry=0x7f9f16dd1988 "ASSERT: \"%s\"
in file %s, line %d") at
/var/tmp/portage/dev-qt/qtcore-5.15.10/work/qtbase-everywhere-src-5.15.10/src/corelib/global/qlogging.cpp:890
#14 0x7f9f16a83c64 in qt_assert (assertion=assertion@entry=0x7f9f16eb7ab2
"last < rowCount(parent)", file=file@entry=0x7f9f16eb7508
"/var/tmp/portage/dev-qt/qtcore-5.15.10/work/qtbase-everywhere-src-5.15.10/src/corelib/itemmodels/qabstractitemmodel.cpp",
line=line@entry=2815) at
/var/tmp/portage/dev-qt/qtcore-5.15.10/work/qtbase-everywhere-src-5.15.10/src/corelib/global/qglobal.cpp:3391
#15 0x7f9f16aa6424 in QAbstractItemModel::beginRemoveRows
(this=0x55ed568cdb50, parent=..., first=0, last=0) at
/var/tmp/portage/dev-qt/qtcore-5.15.10/work/qtbase-everywhere-src-5.15.10/src/corelib/itemmodels/qabstractitemmodel.cpp:2815
#16 0x55ed53e6fc74 in kt::MagnetModel::removeRows (parent=...,
count=, row=0, this=0x55ed568cdb50) at
/var/tmp/portage/net-p2p/ktorrent-23.04.3/work/ktorrent-23.04.3/ktorrent/tools/magnetmodel.cpp:142
#17 kt::MagnetModel::onUpdateQueue (this=0x55ed568cdb50, idx=0, count=0) at
/var/tmp/portage/net-p2p/ktorrent-23.04.3/work/ktorrent-23.04.3/ktorrent/tools/magnetmodel.cpp:60
#18 0x7f9f16d1c960 in QtPrivate::QSlotObjectBase::call (a=0x7ffc69129a70,
r=0x55ed568cdb50, this=0x55ed568cdc90) at
/var/tmp/portage/dev-qt/qtcore-5.15.10/work/qtbase-everywhere-src-5.15.10/include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398
#19 doActivate (sender=0x55ed56791060, signal_index=4,
argv=0x7ffc69129a70) at
/var/tmp/portage/dev-qt/qtcore-5.15.10/work/qtbase-everywhere-src-5.15.10/src/corelib/kernel/qobject.cpp:3925
#20 0x7f9f16d155d7 in QMetaObject::activate (sender=,
m=m@entry=0x7f9f18f70f40 ,
local_signal_index=local_signal_index@entry=1, argv=argv@entry=0x7ffc69129a70)
at
/var/tmp/portage/dev-qt/qtcore-5.15.10/work/qtbase-everywhere-src-5.15.10/src/corelib/kernel/qobject.cpp:3985
#21 0x7f9f18efc0d6 in kt::MagnetManager::updateQueue (this=,
_t1=, _t2=) at
/var/tmp/portage/net-p2p/ktorrent-23.04.3/work/ktorrent-23.04.3_build/libktcore/ktcore_autogen/WEMDBQPFF4/moc_magnetmanager.cpp:379
#22 0x7f9f16d1c960 in QtPrivate::QSlotObjectBase::call (a=0x7ffc69129b80,
r=0x55ed56791060, this=0x55ed56fcf2e0) at
/var/tmp/portage/dev-qt/qtcore-5.15.10/work/qtbase-everywhere-src-5.15.10/include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398
#23 doActivate (sender=0x7f9f04008090, signal_index=3,
argv=0x7ffc69129b80) at
/var/tmp/portage/dev-qt/qtcore-5.15.10/work/qtbase-everywhere-src-5.15.10/src/corelib/kernel/qobject.cpp:3925
#24 0x7f9f16d155d7 in QMetaObject::activate
(sender=sender@entry=0x7f9f04008090, m=m@entry=0x7f9f18e936e0
,
local_signal_index=local_signal_
[konsole] [Bug 405930] Shortcut for switching profiles opens a new tab unlike the mouse option
https://bugs.kde.org/show_bug.cgi?id=405930 Darin McBride changed: What|Removed |Added CC||tankta...@gmail.com --- Comment #4 from Darin McBride --- Did another bug get opened? Because this "fix" has crippled my workflow. In fact, it is a bug - now when I use the keyboard shortcut, it simply changes the colors in the window, but *does not run the command in the profile*. That is a bug. Please revert. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 408217] Konsole switch profile from gui only change termial theme but not excute the customed command
https://bugs.kde.org/show_bug.cgi?id=408217 Darin McBride changed: What|Removed |Added CC||tankta...@gmail.com --- Comment #3 from Darin McBride --- (In reply to Achim Bohnet from comment #2) > Hi, > AFAIR this behaviour is not new. That's the way konsole treated the > switch-profile as long as I can remember. Prior to https://bugs.kde.org/show_bug.cgi?id=405930, if I used the keyboard shortcut, it would properly create a new tab. Switching an existing tab to a new process makes no sense to me. Also, if I use the switch-profile like the way it is now, whether keyboard or menu, and then restart KDE such that that konsole gets restarted, then that tab has the theme AND runs the command, which is different behaviour. I'd say that it's far more broken now than it was before that "fix". The only way I can see to salvage the difference between "switch profile" and "new tab -> profile" is to separate out *theme* from command/profile. That is, everything under "Settings" changes from "profile" to "theme". There is no command or current directory associated with a theme. The entire "General" tab in profiles would be removed. And then a new configuration, say "template", would exist that would have that "General" tab that just got removed, plus a link to an existing "theme". (Perhaps the ability to create a new theme at the same time would be there, doesn't matter to me.) Both themes and templates can have keyboard shortcuts. I would personally never use the shortcut for the theme, but that doesn't mean others wouldn't. On re-startup, konsole would have to know what template and theme each tab had, and apply as appropriate. That's the salvage. Otherwise, I would simply move the whole profile thing to be starting new tabs. Because as long as a command exists there, which is the sole reason why I use profiles in the first place, switching a tab to a profile without running the command specified is inherently broken. -- You are receiving this mail because: You are watching all bug changes.
[ktorrent] [Bug 366448] Crash when removing multiple torrents at a time
https://bugs.kde.org/show_bug.cgi?id=366448 --- Comment #2 from Darin McBride --- Unfortunately, due to bug 396727, I cannot retest this, as I can't get any torrents to run at all. (Maybe if I was using torrents that used torrent files rather than magnets, then I could test.) -- You are receiving this mail because: You are watching all bug changes.
[konquest] [Bug 226399] "P" planets look like "F", making it hard to tell which is which for keyboard use
https://bugs.kde.org/show_bug.cgi?id=226399 Darin McBride changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED --- Comment #3 from Darin McBride --- IMO, yes, the P and the F look incredibly similar just because of how the top-left of the planet is situated on that overlap, and that the top-left is white, like the font. Perhaps if the planets were turned, or if the lettering was a different colour, that would help. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 408217] Switching profile does not execute the custom command
https://bugs.kde.org/show_bug.cgi?id=408217 --- Comment #11 from Darin McBride --- I can confirm the old behaviour has been restored - if you're on a distro that's not carrying KDE apps 19.08.3+ (maybe earlier), then you'll have to wait until the distro makes available the upgrade. (Which is why these regressions are so painful - it can take a long time for some distros, especially the LTS releases, to get the fixes.) However, I thank the developers for fixing it. It's really appreciated and helpful. -- You are receiving this mail because: You are watching all bug changes.
[ktorrent] [Bug 396727] New: Crash when magnet removed from list
https://bugs.kde.org/show_bug.cgi?id=396727 Bug ID: 396727 Summary: Crash when magnet removed from list Product: ktorrent Version: unspecified Platform: Compiled Sources OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: joris.guis...@gmail.com Reporter: tankta...@gmail.com Target Milestone: --- Application: ktorrent (5.1.0) (Compiled from sources) Qt Version: 5.11.1 Frameworks Version: 5.46.0 Operating System: Linux 4.17.2-gentoo x86_64 Distribution: "NAME=Gentoo" -- Information about the crash: - What I was doing when the application crashed: Whether I delete a magnet that hasn't finished downloading, or the magnet finishes downloading and is being removed from the list automatically, ktorrent is crashing on removal. The crash can be reproduced every time. -- Backtrace: Application: KTorrent (ktorrent), signal: Aborted Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7fa341bc7c40 (LWP 11329))] Thread 7 (Thread 0x7fa2f601b700 (LWP 11348)): #0 futex_wait_cancelable (private=, expected=0, futex_word=0x55f6079acca4) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 __pthread_cond_wait_common (abstime=0x0, mutex=0x55f6079acc50, cond=0x55f6079acc78) at pthread_cond_wait.c:502 #2 __pthread_cond_wait (cond=0x55f6079acc78, mutex=0x55f6079acc50) at pthread_cond_wait.c:655 #3 0x7fa33c7ebe7b in QWaitConditionPrivate::wait (time=18446744073709551615, this=0x55f6079acc50) at thread/qwaitcondition_unix.cpp:143 #4 QWaitCondition::wait (this=this@entry=0x55f6079e8e38, mutex=mutex@entry=0x55f6079e8e30, time=time@entry=18446744073709551615) at thread/qwaitcondition_unix.cpp:215 #5 0x7fa34142e18b in net::ReverseResolverThread::run (this=0x55f6079e8e20) at /var/tmp/portage/net-libs/libktorrent-/work/libktorrent-/src/net/reverseresolver.cpp:124 #6 0x7fa33c7eab18 in QThreadPrivate::start (arg=0x55f6079e8e20) at thread/qthread_unix.cpp:367 #7 0x7fa337a0590a in start_thread (arg=0x7fa2f601b700) at pthread_create.c:465 #8 0x7fa33bb1633f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 6 (Thread 0x7fa2f681c700 (LWP 11347)): #0 0x7fa33bae1158 in __GI___nanosleep (requested_time=requested_time@entry=0x7fa2f681bd90, remaining=remaining@entry=0x7fa2f681bd90) at ../sysdeps/unix/sysv/linux/nanosleep.c:27 #1 0x7fa33ca2c01d in qt_nanosleep (amount=...) at kernel/qelapsedtimer_unix.cpp:195 #2 0x7fa33c7e9ef8 in QThread::msleep (msecs=) at thread/qthread_unix.cpp:537 #3 0x7fa34142ab8b in net::UploadThread::update (this=0x55f606c7ea90) at /var/tmp/portage/net-libs/libktorrent-/work/libktorrent-/src/net/uploadthread.cpp:89 #4 0x7fa34142b249 in net::NetworkThread::run (this=0x55f606c7ea90) at /var/tmp/portage/net-libs/libktorrent-/work/libktorrent-/src/net/networkthread.cpp:48 #5 0x7fa33c7eab18 in QThreadPrivate::start (arg=0x55f606c7ea90) at thread/qthread_unix.cpp:367 #6 0x7fa337a0590a in start_thread (arg=0x7fa2f681c700) at pthread_create.c:465 #7 0x7fa33bb1633f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 5 (Thread 0x7fa2f701d700 (LWP 11346)): #0 0x7fa33ba9db97 in __GI___libc_malloc (bytes=56) at malloc.c:3029 #1 0x7fa33c3e5418 in operator new (sz=sz@entry=56) at /var/tmp/portage/sys-devel/gcc-7.3.0-r3/work/gcc-7.3.0/libstdc++-v3/libsupc++/new_op.cc:50 #2 0x7fa34142e912 in __gnu_cxx::new_allocator > > >::allocate (this=, __n=1) at /usr/lib/gcc/x86_64-pc-linux-gnu/6.4.0/include/g++-v6/ext/new_allocator.h:104 #3 std::allocator_traits > > > >::allocate (__a=..., __n=1) at /usr/lib/gcc/x86_64-pc-linux-gnu/6.4.0/include/g++-v6/bits/alloc_traits.h:436 #4 std::_Rb_tree >, std::_Select1st > >, std::less, std::allocator > > >::_M_get_node (this=0x55f606c7e798) at /usr/lib/gcc/x86_64-pc-linux-gnu/6.4.0/include/g++-v6/bits/stl_tree.h:505 #5 std::_Rb_tree >, std::_Select1st > >, std::less, std::allocator > > >::_M_create_node, std::tuple<> >(std::piecewise_construct_t const&, std::tuple&&, std::tuple<>&&) (this=0x55f606c7e798) at /usr/lib/gcc/x86_64-pc-linux-gnu/6.4.0/include/g++-v6/bits/stl_tree.h:559 #6 std::_Rb_tree >, std::_Select1st > >, std::less, std::allocator > > >::_M_emplace_hint_unique, std::tuple<> >(std::_Rb_tree_const_iterator > >, std::piecewise_construct_t const&, std::tuple&&, std::tuple<>&&) (__pos=..., this=0x55f606c7e798) at /usr/lib/gcc/x86_64-pc-linux-gnu/6.4.0/include/g++-v6/bits/stl_tree.h:2196 #7 std::map, std::less, std::allocator > > >::operator[] (__k=: , this=0x55f606c7e798) at /usr/lib/gcc/x86_64-pc-linux-gnu/6.4.0/include/g++-v6/bits/stl_map.h:483 #8 net::Poll::add (this=this@entry=0x55f606c7e770, pc=...) at /var/tmp/portage/net-libs/libktorrent-/work/libktorrent-/src/net/poll.cpp:74 #9 0x7fa34142aea6 in ne
[amarok] [Bug 384332] amarok crash when toggling non-started amarok
https://bugs.kde.org/show_bug.cgi?id=384332 Darin McBride changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #4 from Darin McBride --- Having recompiled git today at commit c9b5bbb727068c2ec616678d1cbc6316c854b530 , this seems to be resolved. Awesome job! Thanks! -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 399818] New: System Settings crash on exit
https://bugs.kde.org/show_bug.cgi?id=399818 Bug ID: 399818 Summary: System Settings crash on exit Product: systemsettings Version: 5.13.5 Platform: Compiled Sources OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: tankta...@gmail.com Target Milestone: --- Application: systemsettings5 (5.13.5) (Compiled from sources) Qt Version: 5.11.1 Frameworks Version: 5.50.0 Operating System: Linux 4.18.11-gentoo x86_64 Distribution: "Gentoo Base System release 2.4.1" -- Information about the crash: - What I was doing when the application crashed: I had been manipulating various aspects of my system settings. Once I was done, many hours later, I closed it and got this crash. The crash does not seem to be reproducible. -- Backtrace: Application: System Settings (systemsettings5), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f92084d0780 (LWP 14268))] Thread 4 (Thread 0x7f91c67fb700 (LWP 19126)): #0 0x7f92038d2434 in __GI___poll (fds=0x55a49501cbc0, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f91fce86f36 in g_main_context_poll (priority=, n_fds=1, fds=0x55a49501cbc0, timeout=, context=0x55a497a4def0) at /var/tmp/portage/dev-libs/glib-2.52.3/work/glib-2.52.3/glib/gmain.c:4271 #2 g_main_context_iterate (context=0x55a497a4def0, block=block@entry=1, dispatch=dispatch@entry=1, self=) at /var/tmp/portage/dev-libs/glib-2.52.3/work/glib-2.52.3/glib/gmain.c:3967 #3 0x7f91fce872c2 in g_main_loop_run (loop=0x55a4973730b0) at /var/tmp/portage/dev-libs/glib-2.52.3/work/glib-2.52.3/glib/gmain.c:4168 #4 0x7f91c6f90c16 in gdbus_shared_thread_func (user_data=0x55a497373080) at /var/tmp/portage/dev-libs/glib-2.52.3/work/glib-2.52.3/gio/gdbusprivate.c:252 #5 0x7f91fceb8125 in g_thread_proxy (data=0x55a4977248a0) at /var/tmp/portage/dev-libs/glib-2.52.3/work/glib-2.52.3/glib/gthread.c:784 #6 0x7f91ff2f48ea in start_thread (arg=0x7f91c67fb700) at pthread_create.c:465 #7 0x7f92038dde3f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 3 (Thread 0x7f91cdc6b700 (LWP 19125)): #0 0x7f91fce86670 in g_main_context_query (context=context@entry=0x55a495c7ac20, max_priority=2147483647, timeout=timeout@entry=0x7f91cdc6ae34, fds=fds@entry=0x55a496e8d380, n_fds=n_fds@entry=1) at /var/tmp/portage/dev-libs/glib-2.52.3/work/glib-2.52.3/glib/gmain.c:3696 #1 0x7f91fce86ea8 in g_main_context_iterate (context=context@entry=0x55a495c7ac20, block=block@entry=1, dispatch=dispatch@entry=1, self=) at /var/tmp/portage/dev-libs/glib-2.52.3/work/glib-2.52.3/glib/gmain.c:3954 #2 0x7f91fce8704c in g_main_context_iteration (context=0x55a495c7ac20, may_block=may_block@entry=1) at /var/tmp/portage/dev-libs/glib-2.52.3/work/glib-2.52.3/glib/gmain.c:4033 #3 0x7f91fce87091 in glib_worker_main (data=) at /var/tmp/portage/dev-libs/glib-2.52.3/work/glib-2.52.3/glib/gmain.c:5824 #4 0x7f91fceb8125 in g_thread_proxy (data=0x55a497724800) at /var/tmp/portage/dev-libs/glib-2.52.3/work/glib-2.52.3/glib/gthread.c:784 #5 0x7f91ff2f48ea in start_thread (arg=0x7f91cdc6b700) at pthread_create.c:465 #6 0x7f92038dde3f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 2 (Thread 0x7f91ebdfa700 (LWP 14271)): #0 0x7f92038d2434 in __GI___poll (fds=0x7f91e4014b80, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f91fce86f36 in g_main_context_poll (priority=, n_fds=1, fds=0x7f91e4014b80, timeout=, context=0x7f91e4000bf0) at /var/tmp/portage/dev-libs/glib-2.52.3/work/glib-2.52.3/glib/gmain.c:4271 #2 g_main_context_iterate (context=context@entry=0x7f91e4000bf0, block=block@entry=1, dispatch=dispatch@entry=1, self=) at /var/tmp/portage/dev-libs/glib-2.52.3/work/glib-2.52.3/glib/gmain.c:3967 #3 0x7f91fce8704c in g_main_context_iteration (context=0x7f91e4000bf0, may_block=may_block@entry=1) at /var/tmp/portage/dev-libs/glib-2.52.3/work/glib-2.52.3/glib/gmain.c:4033 #4 0x7f92042a900b in QEventDispatcherGlib::processEvents (this=0x7f91e4000b20, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #5 0x7f920424146b in QEventLoop::exec (this=this@entry=0x7f91ebdf9df0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:214 #6 0x7f920404e840 in QThread::exec (this=this@entry=0x7f92049a5da0 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at thread/qthread.cpp:525 #7 0x7f9204711885 in QDBusConnectionManager::run (this=0x7f92049a5da0 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at qdbusconnection.cpp:178 #8 0x7f920405bcd6 in QThreadPrivate::start (arg=0x7f92049a5da0 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at thread/qthread_unix.cpp:367 #9 0x7f91ff2f48e
[amarok] [Bug 373590] Amarok KF5 - Play/Pause global hotkey does not exist.
https://bugs.kde.org/show_bug.cgi?id=373590 --- Comment #5 from Darin McBride --- I've reinstalled from scratch(ish) due to a hard drive failure. Amarok has given me a few hiccups here, but I don't have this hotkey created and the play/pause key on my keyboard works just fine. So, assuming no one else is encountering such a problem, it appears this can be closed. For the record, I'm now running Qt 5.11.1 and KF5 5.49 and Plasma 5.13.5. It may have been fixed at any point up to now, and I just may not have noticed since the amarok -t method was working. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 198981] kwin crash while playing konquest
https://bugs.kde.org/show_bug.cgi?id=198981 --- Comment #5 from Darin McBride --- It's highly unlikely the system was overloaded at the time. However, in the intervening years, between 2009 and 2011, or 2011 and 2018 (now), pretty much everything has changed. The KDE versions are all different, the video drivers are improved, X has upgraded, and many other changes. Heck, I've upgraded hardware more than once. The net result is that I'm not having this issue now, so I'm not really able to provide more information than is already attached. It seems like it's fixed, but whether that was Konquest, Kwin, X, or nvidia drivers, I can't really be sure. -- You are receiving this mail because: You are watching all bug changes.
[konqueror] [Bug 307793] konqueror stops responding after trying to close window
https://bugs.kde.org/show_bug.cgi?id=307793 Darin McBride changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED --- Comment #6 from Darin McBride --- I provided the information requested, I believe, though I can no longer reproduce this problem with newer konquerors. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 373517] New: System Settings crash when removing custom keys
https://bugs.kde.org/show_bug.cgi?id=373517 Bug ID: 373517 Summary: System Settings crash when removing custom keys Product: systemsettings Version: 5.8.4 Platform: Compiled Sources OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: tankta...@gmail.com Target Milestone: --- Application: systemsettings5 (5.8.4) (Compiled from sources) Qt Version: 5.6.2 Frameworks Version: 5.28.0 Operating System: Linux 4.8.12-gentoo-r1 x86_64 Distribution: "NAME=Gentoo" -- Information about the crash: - What I was doing when the application crashed: I'm trying to set custom keys for Amarok's Play/Pause action, and I get this regularly when attempting to remove an old setting. Turns out that when I restart system settings and return to the global shortcuts to try again, the removal is registered there. (I'm also unsuccessful at getting Amarok to play/pause with the shortcut chosen). The crash can be reproduced every time. -- Backtrace: Application: System Settings (systemsettings5), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f587ec9d740 (LWP 14382))] Thread 3 (Thread 0x7f586dd9f700 (LWP 14383)): #0 0x7f587b21b3ed in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7f5878d67952 in poll (__timeout=-1, __nfds=1, __fds=0x7f586dd9ed60) at /usr/include/bits/poll2.h:46 #2 _xcb_conn_wait (c=c@entry=0x1dbd450, cond=cond@entry=0x1dbd490, vector=vector@entry=0x0, count=count@entry=0x0) at /var/tmp/portage/x11-libs/libxcb-1.12/work/libxcb-1.12/src/xcb_conn.c:479 #3 0x7f5878d6a169 in xcb_wait_for_event (c=0x1dbd450) at /var/tmp/portage/x11-libs/libxcb-1.12/work/libxcb-1.12/src/xcb_in.c:693 #4 0x7f5870759479 in QXcbEventReader::run (this=0x1dcb570) at qxcbconnection.cpp:1331 #5 0x7f587b8e61f9 in QThreadPrivate::start (arg=0x1dcb570) at thread/qthread_unix.cpp:365 #6 0x7f58784e6434 in start_thread (arg=0x7f586dd9f700) at pthread_create.c:334 #7 0x7f587b22450d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 2 (Thread 0x7f5864e6a700 (LWP 14384)): #0 0x7f587b21b3ed in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7f587676973c in g_main_context_poll (priority=2147483647, n_fds=1, fds=0x7f5860003020, timeout=16668, context=0x7f586990) at /var/tmp/portage/dev-libs/glib-2.48.2/work/glib-2.48.2/glib/gmain.c:4135 #2 g_main_context_iterate (context=context@entry=0x7f586990, block=block@entry=1, dispatch=dispatch@entry=1, self=) at /var/tmp/portage/dev-libs/glib-2.48.2/work/glib-2.48.2/glib/gmain.c:3835 #3 0x7f587676984c in g_main_context_iteration (context=0x7f586990, may_block=1) at /var/tmp/portage/dev-libs/glib-2.48.2/work/glib-2.48.2/glib/gmain.c:3901 #4 0x7f587bb368ac in QEventDispatcherGlib::processEvents (this=0x7f5868c0, flags=...) at kernel/qeventdispatcher_glib.cpp:417 #5 0x7f587bad9442 in QEventLoop::exec (this=this@entry=0x7f5864e69e50, flags=..., flags@entry=...) at kernel/qeventloop.cpp:206 #6 0x7f587b8e030b in QThread::exec (this=this@entry=0x7f587ee1fb00 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at thread/qthread.cpp:500 #7 0x7f587ed9b4b8 in QDBusConnectionManager::run (this=0x7f587ee1fb00 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at qdbusconnection.cpp:189 #8 0x7f587b8e61f9 in QThreadPrivate::start (arg=0x7f587ee1fb00 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at thread/qthread_unix.cpp:365 #9 0x7f58784e6434 in start_thread (arg=0x7f5864e6a700) at pthread_create.c:334 #10 0x7f587b22450d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 1 (Thread 0x7f587ec9d740 (LWP 14382)): [KCrash Handler] #6 QString::QString (other=, this=this@entry=0x7fffc00a2040) at ../../include/QtCore/../../src/corelib/tools/qstring.h:889 #7 QLabel::text (this=0x0) at widgets/qlabel.cpp:337 #8 0x7f587e566a21 in ShortcutEditWidget::setKeySequence (this=0x2661a00, activeSeq=...) at /var/tmp/portage/kde-frameworks/kxmlgui-5.28.0/work/kxmlgui-5.28.0/src/kshortcuteditwidget.cpp:192 #9 0x7f587bb0b649 in QtPrivate::QSlotObjectBase::call (a=0x7fffc00a21c0, r=0x7f5879a88640 <(anonymous namespace)::Q_QGS_s_instance::innerFunction()::holder>, this=0x2738ee0) at ../../include/QtCore/../../src/corelib/kernel/qobject_impl.h:124 #10 QMetaObject::activate (sender=0x7f5879a88640 <(anonymous namespace)::Q_QGS_s_instance::innerFunction()::holder>, signalOffset=, local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7fffc00a21c0) at kernel/qobject.cpp:3715 #11 0x7f587bb0bb07 in QMetaObject::activate (sender=, m=m@entry=0x7f5879a87940 , local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7fffc00a21c0) at
[amarok] [Bug 373590] New: Amarok KF5 - Play/Pause global hotkey does not exist.
https://bugs.kde.org/show_bug.cgi?id=373590 Bug ID: 373590 Summary: Amarok KF5 - Play/Pause global hotkey does not exist. Product: amarok Version: kf5 Platform: Gentoo Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: amarok-bugs-d...@kde.org Reporter: tankta...@gmail.com Target Milestone: 2.9 After upgrading kde frameworks to 5.28.0 from 5.27.0 (and plasma from 5.8.3 to 5.8.4), and using the kf5 branch of amarok, I'm finding that I can no longer use a global hotkey for Play/Pause at all. I'm not sure if this is a problem in amarok or in khotkeys or whatever, so I'm making a guess by starting with amarok. As a workaround, I've created a custom hotkey which will run `amarok -t` - but that seems like a weird workaround for something that used to work so nicely. -- You are receiving this mail because: You are watching all bug changes.
[amarok] [Bug 373590] Amarok KF5 - Play/Pause global hotkey does not exist.
https://bugs.kde.org/show_bug.cgi?id=373590 --- Comment #2 from Darin McBride --- Sure, but if you don't get users' feedback on it, how will you know when it's ready? :) As to whether it's amarok or kf5, I wouldn't know how to prove it is one or the other, and figured amarok has the smaller profile, and thus easier to prove? If there was some debug code or something I could run to show that KF5 wasn't doing what Amarok asked by omitting these global entries, then I could take that over to the khotkeys team, perhaps? I'll attach a screen shot of the problem here, though I don't imagine this will be everything required to prove where the problem lays. -- You are receiving this mail because: You are watching all bug changes.
[amarok] [Bug 373590] Amarok KF5 - Play/Pause global hotkey does not exist.
https://bugs.kde.org/show_bug.cgi?id=373590 --- Comment #3 from Darin McBride --- Created attachment 102756 --> https://bugs.kde.org/attachment.cgi?id=102756&action=edit Image of problem -- You are receiving this mail because: You are watching all bug changes.
[amarok] [Bug 384332] amarok crash when toggling non-started amarok
https://bugs.kde.org/show_bug.cgi?id=384332 --- Comment #2 from Darin McBride --- Yes, I've been running amarok from git for years and years. I get that it's not production-ready, that's always the risk of going straight to the git repo. On the other hand, I've reported a number of pre-release bugs over the years which have helped (I think) get them fixed before being released. Gentoo has "build from git" as an option for a number of packages, amarok being one. And there it's specifying the branch to be "kf5", so I'm pretty sure this is the kf5 branch :) It generally works, too. A couple of minor hiccups here and there, but I get my music, I'm happy. This particular bug isn't a major impediment or anything, but I thought that you'd want to know about a crash :) -- You are receiving this mail because: You are watching all bug changes.
[amarok] [Bug 384332] New: amarok crash when toggling non-started amarok
https://bugs.kde.org/show_bug.cgi?id=384332 Bug ID: 384332 Summary: amarok crash when toggling non-started amarok Product: amarok Version: 2.8-git Platform: Compiled Sources OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: amarok-bugs-d...@kde.org Reporter: tankta...@gmail.com Target Milestone: 2.9 Application: amarok (2.8-git) (Compiled from sources) Qt Version: 5.7.1 Frameworks Version: 5.34.0 Operating System: Linux 4.12.5-gentoo x86_64 Distribution: "NAME=Gentoo" -- Information about the crash: - What I was doing when the application crashed: I ran "amarok -t" to play/pause amarok. However, amarok wasn't running, and so the process I was launching crashed. What I expected: well, not crashing anyway. I was hoping it would notice amarok wasn't running, launch it, and toggle that (i.e., play). The crash can be reproduced every time. -- Backtrace: Application: Amarok (amarok), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f3e6deeb740 (LWP 18731))] Thread 3 (Thread 0x7f3e689e9700 (LWP 18733)): #0 0x7f3e7f7ab45d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7f3e77e910bc in g_main_context_poll (priority=2147483647, n_fds=1, fds=0x7f3e5c003020, timeout=-1, context=0x7f3e5c000990) at /var/tmp/portage/dev-libs/glib-2.50.3-r1/work/glib-2.50.3/glib/gmain.c:4228 #2 g_main_context_iterate (context=context@entry=0x7f3e5c000990, block=block@entry=1, dispatch=dispatch@entry=1, self=) at /var/tmp/portage/dev-libs/glib-2.50.3-r1/work/glib-2.50.3/glib/gmain.c:3924 #3 0x7f3e77e911cc in g_main_context_iteration (context=0x7f3e5c000990, may_block=1) at /var/tmp/portage/dev-libs/glib-2.50.3-r1/work/glib-2.50.3/glib/gmain.c:3990 #4 0x7f3e8015f4ac in QEventDispatcherGlib::processEvents (this=0x7f3e5c0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:423 #5 0x7f3e80102372 in QEventLoop::exec (this=this@entry=0x7f3e689e8e50, flags=..., flags@entry=...) at kernel/qeventloop.cpp:212 #6 0x7f3e7ff10f2b in QThread::exec (this=this@entry=0x7f3e7a5b2240 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at thread/qthread.cpp:507 #7 0x7f3e7a52d6e8 in QDBusConnectionManager::run (this=0x7f3e7a5b2240 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at qdbusconnection.cpp:178 #8 0x7f3e7ff16b89 in QThreadPrivate::start (arg=0x7f3e7a5b2240 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at thread/qthread_unix.cpp:368 #9 0x7f3e7e6353b4 in start_thread (arg=0x7f3e689e9700) at pthread_create.c:333 #10 0x7f3e7f7b455d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 2 (Thread 0x7f3e6aa4a700 (LWP 18732)): #0 0x7f3e7f7ab45d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7f3e736de952 in poll (__timeout=-1, __nfds=1, __fds=0x7f3e6aa49d60) at /usr/include/bits/poll2.h:46 #2 _xcb_conn_wait (c=c@entry=0x1b87c30, cond=cond@entry=0x1b87c70, vector=vector@entry=0x0, count=count@entry=0x0) at /var/tmp/portage/x11-libs/libxcb-1.12-r2/work/libxcb-1.12/src/xcb_conn.c:479 #3 0x7f3e736e1169 in xcb_wait_for_event (c=0x1b87c30) at /var/tmp/portage/x11-libs/libxcb-1.12-r2/work/libxcb-1.12/src/xcb_in.c:693 #4 0x7f3e6cde3389 in QXcbEventReader::run (this=0x1b95d40) at qxcbconnection.cpp:1343 #5 0x7f3e7ff16b89 in QThreadPrivate::start (arg=0x1b95d40) at thread/qthread_unix.cpp:368 #6 0x7f3e7e6353b4 in start_thread (arg=0x7f3e6aa4a700) at pthread_create.c:333 #7 0x7f3e7f7b455d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 1 (Thread 0x7f3e6deeb740 (LWP 18731)): [KCrash Handler] #6 QWeakPointer::data (this=0x30) at /usr/include/qt5/QtCore/qsharedpointer_impl.h:604 #7 EngineController::playPause (this=0x0) at /var/tmp/portage/media-sound/amarok-/work/amarok-/src/EngineController.cpp:607 #8 0x7f3e81e52fcb in App::handleCliArgs (this=this@entry=0x7ffe621ace50, cwd=...) at /var/tmp/portage/media-sound/amarok-/work/amarok-/src/App.cpp:313 #9 0x7f3e81e5321e in App::newInstance (this=0x7ffe621ace50) at /var/tmp/portage/media-sound/amarok-/work/amarok-/src/App.cpp:605 #10 0x7f3e81e536c8 in App::continueInit (this=this@entry=0x7ffe621ace50) at /var/tmp/portage/media-sound/amarok-/work/amarok-/src/App.cpp:424 #11 0x00408647 in main (argc=2, argv=) at /var/tmp/portage/media-sound/amarok-/work/amarok-/src/main.cpp:346 Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[ktorrent] [Bug 366448] New: Crash when removing multiple torrents at a time
https://bugs.kde.org/show_bug.cgi?id=366448 Bug ID: 366448 Summary: Crash when removing multiple torrents at a time Product: ktorrent Version: unspecified Platform: Compiled Sources OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: joris.guis...@gmail.com Reporter: tankta...@gmail.com Application: ktorrent (5.0.1) (Compiled from sources) Qt Version: 5.6.1 Frameworks Version: 5.23.0 Operating System: Linux 4.6.5-gentoo x86_64 Distribution: "NAME=Gentoo" -- Information about the crash: I selected four different torrents to delete, hit the delete key, and this is the crash that resulted. When I restarted, three of the four were gone, but one remained. Compiled from git yesterday. -- Backtrace: Application: KTorrent (ktorrent), signal: Aborted Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f69e2e60740 (LWP 28307))] Thread 7 (Thread 0x7f69ca3cf700 (LWP 28309)): #0 0x7f69dd8e33ed in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7f69d78806bc in g_main_context_poll (priority=2147483647, n_fds=1, fds=0x7f69bc003020, timeout=-1, context=0x7f69bc000990) at /var/tmp/portage/dev-libs/glib-2.46.2-r3/work/glib-2.46.2/glib/gmain.c:4135 #2 g_main_context_iterate (context=context@entry=0x7f69bc000990, block=block@entry=1, dispatch=dispatch@entry=1, self=) at /var/tmp/portage/dev-libs/glib-2.46.2-r3/work/glib-2.46.2/glib/gmain.c:3835 #3 0x7f69d78807cc in g_main_context_iteration (context=0x7f69bc000990, may_block=1) at /var/tmp/portage/dev-libs/glib-2.46.2-r3/work/glib-2.46.2/glib/gmain.c:3901 #4 0x7f69de70b9ec in QEventDispatcherGlib::processEvents (this=0x7f69bc0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:417 #5 0x7f69de6ae792 in QEventLoop::exec (this=this@entry=0x7f69ca3cee50, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #6 0x7f69de4b535b in QThread::exec (this=this@entry=0x7f69e2facb40 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at thread/qthread.cpp:500 #7 0x7f69e2f284b8 in QDBusConnectionManager::run (this=0x7f69e2facb40 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at qdbusconnection.cpp:189 #8 0x7f69de4bb249 in QThreadPrivate::start (arg=0x7f69e2facb40 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at thread/qthread_unix.cpp:341 #9 0x7f69d9cca434 in start_thread (arg=0x7f69ca3cf700) at pthread_create.c:334 #10 0x7f69dd8ec50d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 6 (Thread 0x7f69b7fff700 (LWP 28311)): #0 0x7f69dd8e33e6 in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7f69d78806bc in g_main_context_poll (priority=2147483647, n_fds=1, fds=0x7f69b0003070, timeout=10136, context=0x7f69b990) at /var/tmp/portage/dev-libs/glib-2.46.2-r3/work/glib-2.46.2/glib/gmain.c:4135 #2 g_main_context_iterate (context=context@entry=0x7f69b990, block=block@entry=1, dispatch=dispatch@entry=1, self=) at /var/tmp/portage/dev-libs/glib-2.46.2-r3/work/glib-2.46.2/glib/gmain.c:3835 #3 0x7f69d78807cc in g_main_context_iteration (context=0x7f69b990, may_block=1) at /var/tmp/portage/dev-libs/glib-2.46.2-r3/work/glib-2.46.2/glib/gmain.c:3901 #4 0x7f69de70b9ec in QEventDispatcherGlib::processEvents (this=0x7f69b8c0, flags=...) at kernel/qeventdispatcher_glib.cpp:417 #5 0x7f69de6ae792 in QEventLoop::exec (this=this@entry=0x7f69b7ffee80, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #6 0x7f69de4b535b in QThread::exec (this=) at thread/qthread.cpp:500 #7 0x7f69de4bb249 in QThreadPrivate::start (arg=0xbbc1f0) at thread/qthread_unix.cpp:341 #8 0x7f69d9cca434 in start_thread (arg=0x7f69b7fff700) at pthread_create.c:334 #9 0x7f69dd8ec50d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 5 (Thread 0x7f69c35ef700 (LWP 28312)): #0 0x7f69d787fd00 in g_source_iter_next (source=, iter=) at /var/tmp/portage/dev-libs/glib-2.46.2-r3/work/glib-2.46.2/glib/gmain.c:936 #1 g_main_context_prepare (context=context@entry=0x7f69b8002cd0, priority=priority@entry=0x7f69c35eed40) at /var/tmp/portage/dev-libs/glib-2.46.2-r3/work/glib-2.46.2/glib/gmain.c:3420 #2 0x7f69d78805e8 in g_main_context_iterate (context=context@entry=0x7f69b8002cd0, block=block@entry=1, dispatch=dispatch@entry=1, self=) at /var/tmp/portage/dev-libs/glib-2.46.2-r3/work/glib-2.46.2/glib/gmain.c:3820 #3 0x7f69d78807cc in g_main_context_iteration (context=0x7f69b8002cd0, may_block=1) at /var/tmp/portage/dev-libs/glib-2.46.2-r3/work/glib-2.46.2/glib/gmain.c:3901 #4 0x7f69de70b9ec in QEventDispatcherGlib::processEvents (this=0x7f69b8002c00, flags=...) at kernel/qeventdispatcher_glib.cpp:417 #5 0x7f69de6ae792 in QEventLoop::exec (this=this@entry=0x7f69c35eee80, fl
[kontact] [Bug 358967] Crash going into my inbox
https://bugs.kde.org/show_bug.cgi?id=358967 --- Comment #3 from Darin McBride --- Created attachment 98981 --> https://bugs.kde.org/attachment.cgi?id=98981&action=edit email causing the crash. -- You are receiving this mail because: You are watching all bug changes.
[dragonplayer] [Bug 357794] New: dragon no longer remembers current position in video files
https://bugs.kde.org/show_bug.cgi?id=357794 Bug ID: 357794 Summary: dragon no longer remembers current position in video files Product: dragonplayer Version: 2.0 Platform: Gentoo Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: sit...@kde.org Reporter: tankta...@gmail.com CC: myr...@kde.org I've encountered this before (somewhere around 4.7), opened bug 281618, it got fixed ... and it seems to be back. When I restart a video, it has lost track of its current position. I'm using KDE 15.08, but with 4.14 it was fine. I may need to downgrade dragon for this. -- You are receiving this mail because: You are watching all bug changes.
[dragonplayer] [Bug 357795] New: dragon no longer allows files to be given on the command line
https://bugs.kde.org/show_bug.cgi?id=357795 Bug ID: 357795 Summary: dragon no longer allows files to be given on the command line Product: dragonplayer Version: 2.0 Platform: Gentoo Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: sit...@kde.org Reporter: tankta...@gmail.com CC: myr...@kde.org "dragon myvideo.mp4" used to work in KDE 4.14. Now, with 15.08 I need to use "dragon file://`pwd`/myvideo.mp4" it seems - allowing the shortcut of a filename would be very very useful. This seems like a regression in functionality to me. I generally run dragon from the command line, not from dolphin. -- You are receiving this mail because: You are watching all bug changes.
[dragonplayer] [Bug 357794] dragon no longer remembers current position in video files
https://bugs.kde.org/show_bug.cgi?id=357794 --- Comment #2 from Darin McBride --- "Phonon VLC" is the only backend that shows up in my KDE system settings, so I'm pretty sure that's the one I'm using :) I don't even have any other backend installed. -- You are receiving this mail because: You are watching all bug changes.
[dragonplayer] [Bug 357794] dragon no longer remembers current position in video files
https://bugs.kde.org/show_bug.cgi?id=357794 Darin McBride changed: What|Removed |Added Status|NEEDSINFO |RESOLVED --- Comment #4 from Darin McBride --- My apologies. After a debacle involving nvidia-drivers-368.16 forcing a downgrade and reboot, this problem has gone away (still using vlc, mind you). I don't know what caused it originally, but it has disappeared. There are other problems, which deserve separate reports, but this one seems gone. -- You are receiving this mail because: You are watching all bug changes.
[dragonplayer] [Bug 355249] Video proportion is not in maximized window
https://bugs.kde.org/show_bug.cgi?id=355249 Darin McBride changed: What|Removed |Added CC||tankta...@gmail.com --- Comment #1 from Darin McBride --- Same here using KF 15.08.3 on Gentoo (compiled from sources), Qt 5.5.1, kwin_x11. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 358128] New: Application Launcher should allow forgetting of documents separate from applications
https://bugs.kde.org/show_bug.cgi?id=358128 Bug ID: 358128 Summary: Application Launcher should allow forgetting of documents separate from applications Product: plasmashell Version: 5.5.3 Platform: Gentoo Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Application Launcher (Kickoff) Assignee: k...@davidedmundson.co.uk Reporter: tankta...@gmail.com CC: plasma-b...@kde.org In KDE 4, there were options to forget recent documents without forgetting recent applications, and vice versa. Please bring those separate options back. I don't mind the forget all option, but I generally prefer only forgetting some of history instead of all of it. -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 358967] New: Crash going into my inbox
https://bugs.kde.org/show_bug.cgi?id=358967 Bug ID: 358967 Summary: Crash going into my inbox Product: kontact Version: unspecified Platform: Compiled Sources OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: tankta...@gmail.com Application: kontact (4.14.10) KDE Platform Version: 4.14.16 (Compiled from sources) Qt Version: 4.8.6 Operating System: Linux 4.3.3-gentoo x86_64 Distribution: "NAME=Gentoo" -- Information about the crash: There may be something about a specific email that loads, but going into my inbox gets me this every single time, but other folders are fine. The crash can be reproduced every time. -- Backtrace: Application: Kontact (kontact), signal: Aborted Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f57e8917880 (LWP 22014))] Thread 3 (Thread 0x7f57cb719700 (LWP 22015)): #0 pthread_cond_wait () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f57e3b7f1ca in WTF::TCMalloc_PageHeap::scavengerThread (this=) at /var/tmp/portage/dev-qt/qtwebkit-4.8.6-r1/work/qt-everywhere-opensource-src-4.8.6/src/3rdparty/webkit/Source/JavaScriptCore/wtf/FastMalloc.cpp:2495 #2 0x7f57e3b7f209 in WTF::TCMalloc_PageHeap::runScavengerThread (context=) at /var/tmp/portage/dev-qt/qtwebkit-4.8.6-r1/work/qt-everywhere-opensource-src-4.8.6/src/3rdparty/webkit/Source/JavaScriptCore/wtf/FastMalloc.cpp:1618 #3 0x7f57e0049324 in start_thread (arg=0x7f57cb719700) at pthread_create.c:333 #4 0x7f57e5af7a1d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 2 (Thread 0x7f57cae18700 (LWP 22016)): #0 0x7f57e5aeedcd in poll () at ../sysdeps/unix/syscall-template.S:81 #1 0x7f57df1f2196 in g_main_context_poll (priority=, n_fds=1, fds=0x7f57c40013e0, timeout=-1, context=0x7f57c40009a0) at /var/tmp/portage/dev-libs/glib-2.44.1-r1/work/glib-2.44.1/glib/gmain.c:4103 #2 g_main_context_iterate (context=context@entry=0x7f57c40009a0, 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:3803 #3 0x7f57df1f22ac in g_main_context_iteration (context=0x7f57c40009a0, may_block=1) at /var/tmp/portage/dev-libs/glib-2.44.1-r1/work/glib-2.44.1/glib/gmain.c:3869 #4 0x7f57e7136b8e in QEventDispatcherGlib::processEvents (this=0x7f57c40008c0, flags=...) at /var/tmp/portage/dev-qt/qtcore-4.8.6-r2/work/qt-everywhere-opensource-src-4.8.6/src/corelib/kernel/qeventdispatcher_glib.cpp:452 #5 0x7f57e70f9978 in QEventLoop::processEvents (this=this@entry=0x7f57cae17d10, flags=...) at /var/tmp/portage/dev-qt/qtcore-4.8.6-r2/work/qt-everywhere-opensource-src-4.8.6/src/corelib/kernel/qeventloop.cpp:149 #6 0x7f57e70f9c3e in QEventLoop::exec (this=this@entry=0x7f57cae17d10, flags=...) at /var/tmp/portage/dev-qt/qtcore-4.8.6-r2/work/qt-everywhere-opensource-src-4.8.6/src/corelib/kernel/qeventloop.cpp:204 #7 0x7f57e6fc0d36 in QThread::exec (this=) at /var/tmp/portage/dev-qt/qtcore-4.8.6-r2/work/qt-everywhere-opensource-src-4.8.6/src/corelib/thread/qthread.cpp:538 #8 0x7f57e6fc38dd in QThreadPrivate::start (arg=0xc13d70) at /var/tmp/portage/dev-qt/qtcore-4.8.6-r2/work/qt-everywhere-opensource-src-4.8.6/src/corelib/thread/qthread_unix.cpp:349 #9 0x7f57e0049324 in start_thread (arg=0x7f57cae18700) at pthread_create.c:333 #10 0x7f57e5af7a1d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 1 (Thread 0x7f57e8917880 (LWP 22014)): [KCrash Handler] #6 0x7f57e5a441c7 in __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:55 #7 0x7f57e5a4550a in __GI_abort () at abort.c:89 #8 0x7f57e6fb62ec in qt_message_output (msgType=msgType@entry=QtFatalMsg, buf=) at /var/tmp/portage/dev-qt/qtcore-4.8.6-r2/work/qt-everywhere-opensource-src-4.8.6/src/corelib/global/qglobal.cpp:2359 #9 0x7f57e6fb71a8 in qt_message (ap=0x7ffdef8f81c8, msg=0x7f57e7177078 "ASSERT: \"%s\" in file %s, line %d", msgType=QtFatalMsg) at /var/tmp/portage/dev-qt/qtcore-4.8.6-r2/work/qt-everywhere-opensource-src-4.8.6/src/corelib/global/qglobal.cpp:2405 #10 qFatal (msg=msg@entry=0x7f57e7177078 "ASSERT: \"%s\" in file %s, line %d") at /var/tmp/portage/dev-qt/qtcore-4.8.6-r2/work/qt-everywhere-opensource-src-4.8.6/src/corelib/global/qglobal.cpp:2588 #11 0x7f57e6fb7316 in qt_assert (assertion=assertion@entry=0x7f57e6a9e5d0 "(pos == end && glyphPosition == current.num_glyphs) || logClusters[pos] == glyphPosition", file=file@entry=0x7f57e6a9e508 "/var/tmp/portage/dev-qt/qtgui-4.8.6-r4/work/qt-everywhere-opensource-src-4.8.6/src/gui/text/qtextlayout.cpp", line=line@entry=1709) at /var/tmp/portage/dev-qt/qtcore-4.8.6-r2/work/qt-everywhere-opensource-src-4.8.6/src/corelib/global/qglobal.cpp:2054 #12 0x7f57e6586ced i
[kontact] [Bug 358967] Crash going into my inbox
https://bugs.kde.org/show_bug.cgi?id=358967 Darin McBride changed: What|Removed |Added CC||tankta...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 358967] Crash going into my inbox
https://bugs.kde.org/show_bug.cgi?id=358967 --- Comment #1 from Darin McBride --- Created attachment 98101 --> https://bugs.kde.org/attachment.cgi?id=98101&action=edit New crash information added by DrKonqi kontact (4.14.10) on KDE Platform 4.14.18 using Qt 4.8.6 - What I was doing when the application crashed: I was scrolling up to my latest inbox in gmail (IMAP). Not sure what that message is that is causing problems, if I go to the web gmail, the latest message has " -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 359935] New: kontact crash opening PDF
https://bugs.kde.org/show_bug.cgi?id=359935 Bug ID: 359935 Summary: kontact crash opening PDF Product: kontact Version: unspecified Platform: Compiled Sources OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: tankta...@gmail.com Application: kontact (4.14.10) KDE Platform Version: 4.14.17 (Compiled from sources) Qt Version: 4.8.6 Operating System: Linux 4.3.6-gentoo x86_64 Distribution: "NAME=Gentoo" -- Information about the crash: - What I was doing when the application crashed: I got a pdf attachment, clicked on it and got this crash. When I restarted, went to the same email, clicked again, and the PDF opened in Okular as expected. The crash does not seem to be reproducible. -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f65851dd880 (LWP 21786))] Thread 4 (Thread 0x7f6568779700 (LWP 21791)): #0 pthread_cond_wait () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f658041b1ca in WTF::TCMalloc_PageHeap::scavengerThread (this=) at /var/tmp/portage/dev-qt/qtwebkit-4.8.6-r1/work/qt-everywhere-opensource-src-4.8.6/src/3rdparty/webkit/Source/JavaScriptCore/wtf/FastMalloc.cpp:2495 #2 0x7f658041b209 in WTF::TCMalloc_PageHeap::runScavengerThread (context=) at /var/tmp/portage/dev-qt/qtwebkit-4.8.6-r1/work/qt-everywhere-opensource-src-4.8.6/src/3rdparty/webkit/Source/JavaScriptCore/wtf/FastMalloc.cpp:1618 #3 0x7f657c8df334 in start_thread (arg=0x7f6568779700) at pthread_create.c:333 #4 0x7f65823ba2cd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 3 (Thread 0x7f6567e78700 (LWP 21792)): #0 0x7f65823b13ed in poll () at ../sysdeps/unix/syscall-template.S:81 #1 0x7f657ba82196 in mapped_file_new_from_fd (error=0x7f65600013e0, filename=, writable=, fd=1743223728) at /var/tmp/portage/dev-libs/glib-2.46.2-r2/work/glib-2.46.2/glib/gmappedfile.c:126 #2 g_mapped_file_new (filename=, writable=, error=0x7f65600013e0) at /var/tmp/portage/dev-libs/glib-2.46.2-r2/work/glib-2.46.2/glib/gmappedfile.c:268 #3 0x7f65839bef70 in memcpy (__len=, __src=, __dest=) at /usr/include/bits/string3.h:53 #4 QVector::realloc (this=0x7f65839be978 )+56>, asize=36, aalloc=0) at ../../include/QtCore/../../../qt-everywhere-opensource-src-4.8.6/src/corelib/tools/qvector.h:503 #5 0x7f65839bec3e in QEventLoop::exec (this=0x7f65600031a0, this@entry=0x7f6567e77d10, flags=...) at /var/tmp/portage/dev-qt/qtcore-4.8.6-r2/work/qt-everywhere-opensource-src-4.8.6/src/corelib/kernel/qeventloop.cpp:204 #6 0x7f6583885d36 in QThread::exec (this=) at /var/tmp/portage/dev-qt/qtcore-4.8.6-r2/work/qt-everywhere-opensource-src-4.8.6/src/corelib/thread/qthread.cpp:538 #7 0x7f6583dd in QThreadPrivate::start (arg=0x19f57c0) at /var/tmp/portage/dev-qt/qtcore-4.8.6-r2/work/qt-everywhere-opensource-src-4.8.6/src/corelib/thread/qthread_unix.cpp:349 #8 0x7f657c8df334 in start_thread (arg=0x7f6567e78700) at pthread_create.c:333 #9 0x7f65823ba2cd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 2 (Thread 0x7f651343f700 (LWP 10449)): #0 pthread_cond_timedwait () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_timedwait.S:238 #1 0x7f65838893dc in QWaitConditionPrivate::wait (time=, this=0x7f650c008ac0) at /var/tmp/portage/dev-qt/qtcore-4.8.6-r2/work/qt-everywhere-opensource-src-4.8.6/src/corelib/thread/qwaitcondition_unix.cpp:84 #2 QWaitCondition::wait (this=this@entry=0x7f650c005a20, mutex=mutex@entry=0x7f650c004798, time=) at /var/tmp/portage/dev-qt/qtcore-4.8.6-r2/work/qt-everywhere-opensource-src-4.8.6/src/corelib/thread/qwaitcondition_unix.cpp:158 #3 0x7f658387902e in QThreadPoolThread::run (this=0x7f650c005a10) at /var/tmp/portage/dev-qt/qtcore-4.8.6-r2/work/qt-everywhere-opensource-src-4.8.6/src/corelib/concurrent/qthreadpool.cpp:142 #4 0x7f6583dd in QThreadPrivate::start (arg=0x7f650c005a10) at /var/tmp/portage/dev-qt/qtcore-4.8.6-r2/work/qt-everywhere-opensource-src-4.8.6/src/corelib/thread/qthread_unix.cpp:349 #5 0x7f657c8df334 in start_thread (arg=0x7f651343f700) at pthread_create.c:333 #6 0x7f65823ba2cd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 1 (Thread 0x7f65851dd880 (LWP 21786)): [KCrash Handler] #6 KMime::Content::parent (this=this@entry=0x0004) at /var/tmp/portage/kde-apps/kdepimlibs-4.14.11_pre20160211/work/kdepimlibs/kmime/kmime_content.cpp:976 #7 0x7f6579bcd9eb in KMime::Content::topLevel (this=this@entry=0x631e0a0) at /var/tmp/portage/kde-apps/kdepimlibs-4.14.11_pre20160211/work/kdepimlibs/kmime/kmime_content.cpp:985 #8 0x7f6579bd1ac4 in KMime::Content::index (this=this@entry=0x631e0a0) at /var/tmp/portage/kde
