[prev in list] [next in list] [prev in thread] [next in thread] 

List:       opensuse
Subject:    [opensuse] Re: Wireless networking fail > KDW wallet interference precedes segmentation fault
From:       Mark Ballard <markjballard () googlemail ! com>
Date:       2014-08-23 14:20:09
Message-ID: CAMJSjjsaGeUJ710DEgGxo90G6n7EMo+zExCFZ64wkP6JSAragQ () mail ! gmail ! com
[Download RAW message or body]

If anyone wants to look at this as a bug, please note the networking
is now working. Another problem vector was that I was using the wrong
password.

These things can be deduced from this:

. The segmentation fault still occured.

This is still a bug. The invalid password may have been a contributing
factor. KDE Wallet may even have been a contributing factor. But it
looks more likely related to the config systems' hanging and not
handling multiple requests to open very well.

. KDE Wallet may not have been interfering with the network manager

. KDE Wallet still nevertheless does not know when it is not wanted.

Nor does it give a convincing case to be used.

. The network config does handles wrong password ineligantly

Given a wrong password, the network config dialogue closes and GUI
attention is passed to the network manager notification panel. The
notification gives no indication whatsoever that the password was
wrong. It just stops. The user is left in the dark. When the network
config is reoppened, the password is gone. You have to retype it.

So with freezing, segmentation fault, multiple windows, poor
communication, unestablished connection, unsaved password, the network
manager gives the distinct impression that an incorrect password may
be the least of your troubles.

It is like many, many linux user experiences, frustrating, despairing,
disappointing, time-consuming, troublesome, heart-breaking; but ever
hopeful and eternally grateful because for all our pain and hardship
(our long-suffering dedication to the cause, our denial that really
Linux is a shoddy, perpetually half-finished, bug-ridden operating
system and a curse on one's free time) we are still not worthy.

Mark.

On 23 August 2014 13:57, Mark Ballard <markjballard@googlemail.com> wrote:
> KDE Wallet stopped me connecting my wireless network. And now the
> network config has crashed. I can't connect.
>
> Not only that, KDE Wallet doesn't know when it's not wanted. I keep
> telling it to go away. It keeps coming back.
>
> KDE Wallet
> ---------------
>
> If I must use KDE wallet for this opensuse system to work, then it
> should say: "you *must* do this or your system won't work".
>
> If KDE Wallet is optional, then it should learn to know when it's not
> wanted. If I tell it to go away, I do not want it to keep coming back.
>
> If there is a compelling reason to use KDE wallet, it is not apparent
> from the description it gives when it comes up in the way it does. If
> there is a good reason for using wallet, it has not conveyed this
> information. I suspect there is not.
>
> This did no become more than an irritation until it came to
> networking. Prior to attempting to establish a connection KDE Wallet
> came up every time I wanted to put in a password. I pressed <ESC> and
> it went away.
>
> KDE Wallet and Wireless Networking
> ----------------------------------------------
>
> But KDE Wallet prevented me from establishing a connection to my
> wireless network. I configured the network. But when I tried to
> connect, it would say, "waiting for authorization", and it would soon
> become apparent that the KDE Wallet config window had popped up in the
> background.
>
> If I told KDE Wallet to go away, the network app would stop trying to
> establish a connection.
>
> The wallet was forcing itself upon me. So I figured I would have to
> use it against my wishes.
>
> When I addressed the KDE Wallet dialogue, however, it provided a tick
> box on the first page that I would have to click to indicate that I
> wanted to use it. So it seemed I did have an option after all. What a
> relief! Maybe now I could connect my network and KDE Wallet would go
> away for good! So having not ticked the box I clicked <Next>. I kept
> having to click <Next> to skip through the setup process, studiously
> not entering any information. Then I clicked okay and the wallet went
> away. Hooray!
>
> But then when I tried to connect the network, it said "waiting for
> authorization" again (though you have to squint really hard to see
> it). And nothing more happened. The KDE Wallet didn't come back. There
> was nothing I could do.
>
> I had searched out the KDE Wallet config again. It had a useful
> looking interface with a tickbox prominently offering to <Enable kDE
> Wallet>. So this did imply again that I did not have to enable it. I
> have to trust this, don't I? Despite appearances, I have to trust that
> I don't need to enable the wallet to use the networking, don't I?
>
> I tried looking at <Manage Connections>. It showed the connection I
> had set up. But I had trouble getting the details up. When I selected
> the connection and pressed <Edit>, nothing happened. Nothing happened
> either when I double clicked on the connnection.
>
> After an inordinate amount of time - and quite by chance, really, that
> I was still in the room - an error came up. It said:
>
> "Error: KDE Control Module - Did not receive a reply. Possible causes
> include: the remote application did not send a reply; the message bus
> security policy blocked the reply; the reply time out expired; or the
> network connection was broken".
>
> So it looked like KDE Wallet was still in the way.
>
> I went to check the wireless password dialogue and the password was no
> longer there. It was when I entered this last time that the KDE Wallet
> first came up, if I remember correctly. I entered the password again.
> It failed to establish a conenction. It is not very good at reporting
> what's going on. It also doesn't know when it already has a config
> window open for a particular network. In clicking to open the network
> config I somehow managed to open more than one. I sent one off with a
> password and it came back with nothing. I sent another one off. And it
> crashed.
>
> It reported a segmentation fault:
> ----------------------------------------
>
> Executable: kcmshell4 PID: 20187 Signal: Segmentation fault (11)
>
> I'm afraid I was not able to report this in the usual way because I
> don't have a connection.
>
> I was unable to report it to your forum because - surprise! - it has
> proved probitively difficult getting a login and actually using it.
>
> (I've got logins to bugzilla, launchpad, stackexchange etc, easily
> enough, why does your's have to be so difficult - and why can't I just
> use one of those other logins?).
>
> Perhaps someone would be kind enough to file this somewhere where it
> might get dealt with?
>
> It reported the following bug details:
> --------------------------------------------
>
> Application: KDE Control Module (kcmshell4), signal: Segmentation fault
> Using host libthread_db library "/lib/libthread_db.so.1".
> [Current thread is 1 (Thread 0xb5446740 (LWP 20187))]
>
> Thread 2 (Thread 0xae262b40 (LWP 20198)):
> #0  0xb773f430 in __kernel_vsyscall ()
> #1  0xb5f92372 in clock_gettime () from /lib/libc.so.6
> #2  0xb6ce007c in ?? () from /usr/lib/libQtCore.so.4
> #3  0xb6dc5e82 in ?? () from /usr/lib/libQtCore.so.4
> #4  0xb6dc443b in ?? () from /usr/lib/libQtCore.so.4
> #5  0xb6dc44ca in ?? () from /usr/lib/libQtCore.so.4
> #6  0xb59330d3 in g_main_context_prepare () from /usr/lib/libglib-2.0.so.0
> #7  0xb59339ef in ?? () from /usr/lib/libglib-2.0.so.0
> #8  0xb5933c38 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
> #9  0xb6dc460f in
> QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>)
> () from /usr/lib/libQtCore.so.4
> #10 0xb6d93a03 in
> QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) ()
> from /usr/lib/libQtCore.so.4
> #11 0xb6d93d29 in
> QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from
> /usr/lib/libQtCore.so.4
> #12 0xb6c8230d in QThread::exec() () from /usr/lib/libQtCore.so.4
> #13 0xb6d73e14 in ?? () from /usr/lib/libQtCore.so.4
> #14 0xb6c84c5f in ?? () from /usr/lib/libQtCore.so.4
> #15 0xb6c0107a in start_thread () from /lib/libpthread.so.0
> #16 0xb5f8480e in clone () from /lib/libc.so.6
>
> Thread 1 (Thread 0xb5446740 (LWP 20187)):
> [KCrash Handler]
> #6  0xb6cd37f3 in QString::operator=(QString const&) () from
> /usr/lib/libQtCore.so.4
> #7  0xae636846 in Knm::Connection::setName(QString const&) () from
> /usr/lib/libknminternals.so.4
> #8  0xae68b776 in ConnectionWidget::writeConfig() () from /usr/lib/libknmui.so.4
> #9  0xae6c893f in ConnectionPreferences::save() () from /usr/lib/libknmui.so.4
> #10 0xae6d1e2b in ConnectionEditor::editConnection(Knm::Connection*)
> () from /usr/lib/libknmui.so.4
> #11 0xae780621 in ?? () from /usr/lib/kde4/kcm_networkmanagement.so
> #12 0xae77db74 in ?? () from /usr/lib/kde4/kcm_networkmanagement.so
> #13 0xb6da9c55 in QMetaObject::activate(QObject*, QMetaObject const*,
> int, void**) () from /usr/lib/libQtCore.so.4
> #14 0xae6ffadd in
> NMDBusSettingsConnectionProvider::getConnectionSecretsCompleted(bool,
> QString const&, QString const&) () from /usr/lib/libknm_nm.so
> #15 0xae73ef18 in
> NMDBusSettingsConnectionProvider::onConnectionSecretsArrived(QDBusPendingCallWatcher*)
> () from /usr/lib/libknm_nm.so
> #16 0xae6ffc71 in ?? () from /usr/lib/libknm_nm.so
> #17 0xb6da9c55 in QMetaObject::activate(QObject*, QMetaObject const*,
> int, void**) () from /usr/lib/libQtCore.so.4
> #18 0xb5b364c5 in
> QDBusPendingCallWatcher::finished(QDBusPendingCallWatcher*) () from
> /usr/lib/libQtDBus.so.4
> #19 0xb5b3650c in ?? () from /usr/lib/libQtDBus.so.4
> #20 0xb6da63da in QMetaCallEvent::placeMetaCall(QObject*) () from
> /usr/lib/libQtCore.so.4
> #21 0xb6dae2bb in QObject::event(QEvent*) () from /usr/lib/libQtCore.so.4
> #22 0xb62804b4 in QApplicationPrivate::notify_helper(QObject*,
> QEvent*) () from /usr/lib/libQtGui.so.4
> #23 0xb6286ee3 in QApplication::notify(QObject*, QEvent*) () from
> /usr/lib/libQtGui.so.4
> #24 0xb74e5cb4 in KApplication::notify(QObject*, QEvent*) () from
> /usr/lib/libkdeui.so.5
> #25 0xb6d94fba in QCoreApplication::notifyInternal(QObject*, QEvent*)
> () from /usr/lib/libQtCore.so.4
> #26 0xb6d982e5 in QCoreApplicationPrivate::sendPostedEvents(QObject*,
> int, QThreadData*) () from /usr/lib/libQtCore.so.4
> #27 0xb6d9880c in QCoreApplication::sendPostedEvents(QObject*, int) ()
> from /usr/lib/libQtCore.so.4
> #28 0xb6dc4e0e in ?? () from /usr/lib/libQtCore.so.4
> #29 0xb59337ce in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
> #30 0xb5933b78 in ?? () from /usr/lib/libglib-2.0.so.0
> #31 0xb5933c38 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
> #32 0xb6dc45ef in
> QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>)
> () from /usr/lib/libQtCore.so.4
> #33 0xb633051e in ?? () from /usr/lib/libQtGui.so.4
> #34 0xb6d93a03 in
> QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) ()
> from /usr/lib/libQtCore.so.4
> #35 0xb6d93d29 in
> QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from
> /usr/lib/libQtCore.so.4
> #36 0xb67b15d1 in QDialog::exec() () from /usr/lib/libQtGui.so.4
> #37 0xb52d0ff9 in kdemain () from /usr/lib/libkdeinit4_kcmshell4.so
> #38 0x0804fba3 in _start ()
>
> ---------------------------------
-- 
To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org
To contact the owner, e-mail: opensuse+owner@opensuse.org

[prev in list] [next in list] [prev in thread] [next in thread]