Bug 233107 - Chakra-Tribe Install Crash
Summary: Chakra-Tribe Install Crash
Status: RESOLVED WORKSFORME
Alias: None
Product: unknown
Classification: Miscellaneous
Component: general (show other bugs)
Version: unspecified
Platform: unspecified Linux
: NOR crash
Target Milestone: ---
Assignee: Unassigned bugs mailing-list
URL:
Keywords: investigated, triaged
Depends on:
Blocks:
 
Reported: 2010-04-02 20:57 UTC by Joshua Dobiac
Modified: 2018-10-21 04:39 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Joshua Dobiac 2010-04-02 20:57:25 UTC
Application: tribe (1.0 alpha)
KDE Platform Version: 4.4.1 (KDE 4.4.1)
Qt Version: 4.6.2
Operating System: Linux 2.6.32-ARCH i686
Distribution (Platform): Archlinux Packages

-- Information about the crash:
When I attempt to install Chakra Linux the installer crashes everytime I attempt to move on from the partition tab.

The crash can be reproduced every time.

 -- Backtrace:
Application: Tribe (tribe), signal: Segmentation fault
[KCrash Handler]
#6  PartitioningPage::aboutToGoToNext (this=0xa0b3408) at /home/phil/kdemod/chakra/chakra-tribe/src/tribe-build/src/pages/PartitioningPage.cpp:847
#7  0x0807879e in PartitioningPage::qt_metacall (this=0xa0b3408, _c=QMetaObject::InvokeMetaMethod, _id=41, _a=0xbf979a48)
    at /home/phil/kdemod/chakra/chakra-tribe/src/tribe-build/PartitioningPage.moc:231
#8  0xb6bae06a in QMetaObject::metacall(QObject*, QMetaObject::Call, int, void**) () from /usr/lib/libQtCore.so.4
#9  0xb6bbc65f in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /usr/lib/libQtCore.so.4
#10 0xb680e149 in QAbstractButton::clicked(bool) () from /usr/lib/libQtGui.so.4
#11 0xb64f0119 in ?? () from /usr/lib/libQtGui.so.4
#12 0xb64f0f64 in ?? () from /usr/lib/libQtGui.so.4
#13 0xb64f121e in QAbstractButton::mouseReleaseEvent(QMouseEvent*) () from /usr/lib/libQtGui.so.4
#14 0xb614c9a8 in QWidget::event(QEvent*) () from /usr/lib/libQtGui.so.4
#15 0xb64effbe in QAbstractButton::event(QEvent*) () from /usr/lib/libQtGui.so.4
#16 0xb6599a82 in QPushButton::event(QEvent*) () from /usr/lib/libQtGui.so.4
#17 0xb60eee4c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/libQtGui.so.4
#18 0xb60f663f in QApplication::notify(QObject*, QEvent*) () from /usr/lib/libQtGui.so.4
#19 0xb76b40ca in KApplication::notify(QObject*, QEvent*) () from /usr/lib/libkdeui.so.5
#20 0xb6ba8e6b in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib/libQtCore.so.4
#21 0xb60f5367 in QApplicationPrivate::sendMouseEvent(QWidget*, QMouseEvent*, QWidget*, QWidget*, QWidget**, QPointer<QWidget>&, bool) () from /usr/lib/libQtGui.so.4
#22 0xb617f7dc in ?? () from /usr/lib/libQtGui.so.4
#23 0xb617ed43 in QApplication::x11ProcessEvent(_XEvent*) () from /usr/lib/libQtGui.so.4
#24 0xb61aba62 in ?? () from /usr/lib/libQtGui.so.4
#25 0xb42a7398 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#26 0xb42aac10 in g_main_context_iterate () from /usr/lib/libglib-2.0.so.0
#27 0xb42aad43 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#28 0xb6bd47b5 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
#29 0xb61ab5c5 in ?? () from /usr/lib/libQtGui.so.4
#30 0xb6ba74a9 in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
#31 0xb6ba78fa in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
#32 0xb6baba6f in QCoreApplication::exec() () from /usr/lib/libQtCore.so.4
#33 0xb60eeee7 in QApplication::exec() () from /usr/lib/libQtGui.so.4
#34 0x08057396 in main (argc=1, argv=0xbf97acc4) at /home/phil/kdemod/chakra/chakra-tribe/src/tribe-build/src/main.cpp:93

Reported using DrKonqi
Comment 1 Dario Andres 2010-04-03 03:07:49 UTC
@Dario F.: do you use the Chakra bugtracker for Tribe ?
Regards
Comment 2 Joshua Dobiac 2010-04-03 04:01:31 UTC
Yeah, actually it's a bug, but a minor one that can easily be avoided.  I'm
going through the Chakra bugtracker now.  I realized shortly after filling
out the form that kde bugtracking was an inappropriate forum for distro
specific bugs.

Best,

Joshua Dobiac

On Fri, Apr 2, 2010 at 9:07 PM, Dario Andres <andresbajotierra@gmail.com>wrote:

> https://bugs.kde.org/show_bug.cgi?id=233107
>
>
> Dario Andres <andresbajotierra@gmail.com> changed:
>
>           What    |Removed                     |Added
>
> ----------------------------------------------------------------------------
>             Status|UNCONFIRMED                 |NEEDSINFO
>                 CC|                            |andresbajotierra@gmail.com
> ,
>                   |                            |drf@kde.org
>          Component|general                     |general
>         Resolution|                            |WAITINGFORINFO
>            Product|kde                         |unknown
>
>
>
>
> --- Comment #1 from Dario Andres <andresbajotierra gmail com>  2010-04-03
> 03:07:49 ---
> @Dario F.: do you use the Chakra bugtracker for Tribe ?
> Regards
>
> --
> Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
> ------- You are receiving this mail because: -------
> You reported the bug.
>
Comment 3 Andrew Crouthamel 2018-09-20 21:50:57 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days, the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please set the bug status as REPORTED so that the KDE team knows that the bug is ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 4 Andrew Crouthamel 2018-10-21 04:39:42 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!