Trisquel 7 asks twice for user password
- Anmelden oder Registrieren um Kommentare zu schreiben
During startup, Trisquel 7 has normally been asking for my user password, but today it started asking for my password _twice_, once right after the Plymouth screen passes to my wallpaper, and again after I enter my password, followed by a grey screen, and then my wallpaper again, whereupon it asks for my password once more. I have not tried to go past the second request, as I do not know what I am authenticating at that stage. Any ideas ?
The following two kernels exhibit this behavior:
Linux-Libre 3.13.0-67-lowlatency and Linux-Libre 3.13.0-66-lowlatency
Linux-Libre 3.13.0-65-lowlatency behaves normally.
Just now I tried a couple of restarts, looking for messages during shutdown, and the double password request vanished. I had not asked for any software update/upgrades, however, so the behavior hasn't repeated. I was puzzled by the fact that the previous kernel, Linux-Libre 3.13.0-66-lowlatency, showed the same behavior this morning, as it had not done so previously.
Not crazy. Linux-Libre 3.13.0-67-lowlatency just did it again. Random negative reinforcement ?
Maddening. Does it randomly whichever kernel I choose from the Grub menu. Sometimes three starts in a row.
I just tried it on Linux-Libre 3.13.0-59-lowlatency. Same random behavior.
Must be some app that I installed yesterday; all from the Trisquel repository by apt-get install.
Something that needs to be run with authentication that's in the startup menu ? I'll look in BUM.
Research results from BUM:
Unchecking wicd, tor, clamav-freshclam, postfix, and hddtemp in BUM had no effect, but unchecking clamav-daemon did. Now I've gone through a half-dozen restarts without getting a second password request.
Still have no idea what's in store if I accede to that second request.
Nothing has changed; with no programs checked in BUM, the duplicate password requests proceed on a random basis. Sheesh.
Don't you simply mistype the password? Also, what is BUM? You can look at APT's logs in /var/log/apt.
I am a translator!
Banana Magique: BUM is boot-up manager, a very neat and usefull application.
The password prompt window usually has a clickable link that can display which component is asking the password.
One question: did you change the display manager from lightdm to gdm or others?
Is the previous Display manager on the system?
If that is so I might have the solution to your problem. Tell us all DMs you have installed and do not uninstall anything.
Mis-typed password: No - when I flub my password, the system tells me so and just repeats the same window without any intervening screen displays.
New display manager: No.
BUM is the bootup manager.
I looked in today's system log, during which I started three times in order to get just one request for user authentication:
----------------------------------------------------------------------------------------------------------------
These two sequences only happened during the first of the three startups:
----------------------------------------------------------------------------------------------------------------
Nov 10 07:15:12 george-ThinkPad-T420 avahi-daemon[619]: Found user 'avahi' (UID 107) and group 'avahi' (GID 113).
Nov 10 07:15:12 george-ThinkPad-T420 avahi-daemon[619]: Successfully dropped root privileges.
Nov 10 07:15:12 george-ThinkPad-T420 avahi-daemon[619]: avahi-daemon 0.6.31 starting up.
Nov 10 07:15:12 george-ThinkPad-T420 avahi-daemon[619]: Successfully called chroot().
Nov 10 07:15:12 george-ThinkPad-T420 avahi-daemon[619]: Successfully dropped remaining capabilities.
Nov 10 07:15:12 george-ThinkPad-T420 bluetoothd[637]: Bluetooth daemon 4.101
Nov 10 07:15:12 george-ThinkPad-T420 bluetoothd[637]: Starting SDP server
Nov 10 07:15:12 george-ThinkPad-T420 avahi-daemon[619]: No service file found in /etc/avahi/services.
...
Nov 10 07:15:22 george-ThinkPad-T420 avahi-daemon[619]: New relevant interface wlan0.IPv6 for mDNS.
Nov 10 07:15:22 george-ThinkPad-T420 avahi-daemon[619]: Registering new address record for fe80::aa54:b2ff:fea7:643d on wlan0.*.
Nov 10 07:15:23 george-ThinkPad-T420 NetworkManager[1116]: Activation (wlan0) successful, device activated.
-----------------------------------------------------------------------------------------------------------------
These sequences happened in the first two startups:
-----------------------------------------------------------------------------------------------------------------
Startup 1 (asked for user authentication twice):
Nov 10 07:15:30 george-ThinkPad-T420 gnome-session[1677]: GLib-CRITICAL: g_environ_setenv: assertion 'value != NULL' failed
Nov 10 07:15:32 george-ThinkPad-T420 kernel: [ 49.337979] do_trap: 123 callbacks suppressed
Nov 10 07:15:32 george-ThinkPad-T420 kernel: [ 49.337983] traps: gnome-panel[1877] trap int3 ip:7fc9d7fc8c13 sp:7ffda6a9e560 error:0
Nov 10 07:15:33 george-ThinkPad-T420 gnome-session[1677]: WARNING: Application 'gnome-panel.desktop' killed by signal 5
Nov 10 07:15:33 george-ThinkPad-T420 kernel: [ 51.008657] traps: gnome-panel[1967] trap int3 ip:7f00b74c9c13 sp:7ffd660f0e60 error:0
Nov 10 07:15:33 george-ThinkPad-T420 ModemManager[826]: Creating modem with plugin 'Generic' and '1' ports
Nov 10 07:15:33 george-ThinkPad-T420 ModemManager[826]: Could not grab port (tty/ttyS4): 'Cannot add port 'tty/ttyS4', unhandled serial type'
Nov 10 07:15:33 george-ThinkPad-T420 ModemManager[826]: Couldn't create modem for device at '/sys/devices/pci0000:00/0000:00:16.3': Failed to find primary AT port
Nov 10 07:15:33 george-ThinkPad-T420 gnome-session[1677]: WARNING: App 'gnome-panel.desktop' respawning too quickly
Nov 10 07:15:33 george-ThinkPad-T420 gnome-session[1677]: CRITICAL: We failed, but the fail whale is dead. Sorry....
Nov 10 07:15:33 george-ThinkPad-T420 bluetoothd[637]: Endpoint unregistered: sender=:1.63 path=/MediaEndpoint/HFPAG
Nov 10 07:15:33 george-ThinkPad-T420 bluetoothd[637]: Endpoint unregistered: sender=:1.63 path=/MediaEndpoint/HFPHS
Nov 10 07:15:33 george-ThinkPad-T420 bluetoothd[637]: Endpoint unregistered: sender=:1.63 path=/MediaEndpoint/A2DPSource
Nov 10 07:15:33 george-ThinkPad-T420 bluetoothd[637]: Endpoint unregistered: sender=:1.63 path=/MediaEndpoint/A2DPSink
Nov 10 07:15:33 george-ThinkPad-T420 colord: device removed: xrandr-LVDS1
Nov 10 07:15:33 george-ThinkPad-T420 colord: Profile removed: icc-26153eb0fd28abe9bd6a2287f37d5be7
Nov 10 07:15:33 george-ThinkPad-T420 colord: Profile removed: icc-fc5a5724d8e38a55136af5074661119d
Nov 10 07:15:34 george-ThinkPad-T420 acpid: client 1134[0:0] has disconnected
Nov 10 07:15:34 george-ThinkPad-T420 acpid: client connected from 1979[0:0]
Nov 10 07:15:34 george-ThinkPad-T420 acpid: 1 client rule loaded
Nov 10 07:15:40 george-ThinkPad-T420 NetworkManager[1116]: (wlan0): IP6 addrconf timed out or failed.
Nov 10 07:15:40 george-ThinkPad-T420 NetworkManager[1116]: Activation (wlan0) Stage 4 of 5 (IPv6 Configure Timeout) scheduled...
Nov 10 07:15:40 george-ThinkPad-T420 NetworkManager[1116]: Activation (wlan0) Stage 4 of 5 (IPv6 Configure Timeout) started...
Nov 10 07:15:40 george-ThinkPad-T420 NetworkManager[1116]: Activation (wlan0) Stage 4 of 5 (IPv6 Configure Timeout) complete.
Nov 10 07:15:41 george-ThinkPad-T420 dbus[581]: [system] Activating service name='org.freedesktop.systemd1' (using servicehelper)
Nov 10 07:15:41 george-ThinkPad-T420 dbus[581]: [system] Successfully activated service 'org.freedesktop.systemd1'
--------------------------------------------------------------------------------------------------------------------
Startup 2 (asked for user authentication twice):
Nov 10 07:16:51 george-ThinkPad-T420 gnome-session[1677]: GLib-CRITICAL: g_environ_setenv: assertion 'value != NULL' failed
Nov 10 07:16:54 george-ThinkPad-T420 kernel: [ 50.342129] do_trap: 123 callbacks suppressed
Nov 10 07:16:54 george-ThinkPad-T420 kernel: [ 50.342133] traps: gnome-panel[1887] trap int3 ip:7fd8cd4ccc13 sp:7ffdb1224a60 error:0
Nov 10 07:16:54 george-ThinkPad-T420 ModemManager[830]: Creating modem with plugin 'Generic' and '1' ports
Nov 10 07:16:54 george-ThinkPad-T420 ModemManager[830]: Could not grab port (tty/ttyS4): 'Cannot add port 'tty/ttyS4', unhandled serial type'
Nov 10 07:16:54 george-ThinkPad-T420 ModemManager[830]: Couldn't create modem for device at '/sys/devices/pci0000:00/0000:00:16.3': Failed to find primary AT port
Nov 10 07:16:54 george-ThinkPad-T420 gnome-session[1677]: WARNING: Application 'gnome-panel.desktop' killed by signal 5
Nov 10 07:16:55 george-ThinkPad-T420 kernel: [ 51.481159] traps: gnome-panel[1986] trap int3 ip:7f53f154cc13 sp:7ffe5670ee00 error:0
Nov 10 07:16:55 george-ThinkPad-T420 gnome-session[1677]: WARNING: App 'gnome-panel.desktop' respawning too quickly
Nov 10 07:16:55 george-ThinkPad-T420 gnome-session[1677]: CRITICAL: We failed, but the fail whale is dead. Sorry....
Nov 10 07:16:55 george-ThinkPad-T420 bluetoothd[619]: Endpoint unregistered: sender=:1.61 path=/MediaEndpoint/HFPAG
Nov 10 07:16:55 george-ThinkPad-T420 bluetoothd[619]: Endpoint unregistered: sender=:1.61 path=/MediaEndpoint/HFPHS
Nov 10 07:16:55 george-ThinkPad-T420 bluetoothd[619]: Endpoint unregistered: sender=:1.61 path=/MediaEndpoint/A2DPSource
Nov 10 07:16:55 george-ThinkPad-T420 bluetoothd[619]: Endpoint unregistered: sender=:1.61 path=/MediaEndpoint/A2DPSink
Nov 10 07:16:55 george-ThinkPad-T420 NetworkManager[1097]: error requesting auth for org.freedesktop.NetworkManager.sleep-wake: (3) GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Could not get UID of name ':1.74': no such name
Nov 10 07:16:55 george-ThinkPad-T420 NetworkManager[1097]: error requesting auth for org.freedesktop.NetworkManager.enable-disable-wifi: (3) GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Could not get UID of name ':1.74': no such name
Nov 10 07:16:55 george-ThinkPad-T420 NetworkManager[1097]: error requesting auth for org.freedesktop.NetworkManager.enable-disable-wwan: (3) GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Could not get UID of name ':1.74': no such name
Nov 10 07:16:55 george-ThinkPad-T420 NetworkManager[1097]: error requesting auth for org.freedesktop.NetworkManager.enable-disable-wimax: (3) GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Could not get UID of name ':1.74': no such name
Nov 10 07:16:55 george-ThinkPad-T420 NetworkManager[1097]: error requesting auth for org.freedesktop.NetworkManager.network-control: (3) GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Could not get UID of name ':1.74': no such name
Nov 10 07:16:55 george-ThinkPad-T420 colord: device removed: xrandr-LVDS1
Nov 10 07:16:55 george-ThinkPad-T420 colord: Profile removed: icc-26153eb0fd28abe9bd6a2287f37d5be7
Nov 10 07:16:55 george-ThinkPad-T420 colord: Profile removed: icc-fc5a5724d8e38a55136af5074661119d
Nov 10 07:16:55 george-ThinkPad-T420 NetworkManager[1097]: error requesting auth for org.freedesktop.NetworkManager.wifi.share.protected: (3) GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Could not get UID of name ':1.74': no such name
Nov 10 07:16:55 george-ThinkPad-T420 NetworkManager[1097]: error requesting auth for org.freedesktop.NetworkManager.wifi.share.open: (3) GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Could not get UID of name ':1.74': no such name
Nov 10 07:16:55 george-ThinkPad-T420 NetworkManager[1097]: error requesting auth for org.freedesktop.NetworkManager.settings.modify.system: (3) GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Could not get UID of name ':1.74': no such name
Nov 10 07:16:55 george-ThinkPad-T420 NetworkManager[1097]: error requesting auth for org.freedesktop.NetworkManager.settings.modify.own: (3) GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Could not get UID of name ':1.74': no such name
Nov 10 07:16:55 george-ThinkPad-T420 NetworkManager[1097]: error requesting auth for org.freedesktop.NetworkManager.settings.modify.hostname: (3) GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Could not get UID of name ':1.74': no such name
Nov 10 07:16:55 george-ThinkPad-T420 acpid: client 1103[0:0] has disconnected
Nov 10 07:16:55 george-ThinkPad-T420 acpid: client connected from 2024[0:0]
Nov 10 07:16:55 george-ThinkPad-T420 acpid: 1 client rule loaded
Nov 10 07:16:59 george-ThinkPad-T420 NetworkManager[1097]: (wlan0): IP6 addrconf timed out or failed.
Nov 10 07:16:59 george-ThinkPad-T420 NetworkManager[1097]: Activation (wlan0) Stage 4 of 5 (IPv6 Configure Timeout) scheduled...
Nov 10 07:16:59 george-ThinkPad-T420 NetworkManager[1097]: Activation (wlan0) Stage 4 of 5 (IPv6 Configure Timeout) started...
Nov 10 07:16:59 george-ThinkPad-T420 NetworkManager[1097]: Activation (wlan0) Stage 4 of 5 (IPv6 Configure Timeout) complete.
Nov 10 07:17:00 george-ThinkPad-T420 wpa_supplicant[1157]: wlan0: CTRL-EVENT-SCAN-STARTED
Nov 10 07:17:01 george-ThinkPad-T420 CRON[2167]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly)
Nov 10 07:17:02 george-ThinkPad-T420 kernel: [ 58.254703] type=1400 audit(1447157822.082:53): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/cups/backend/cups-pdf" pid=2175 comm="apparmor_parser"
Nov 10 07:17:02 george-ThinkPad-T420 kernel: [ 58.254709] type=1400 audit(1447157822.082:54): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/sbin/cupsd" pid=2175 comm="apparmor_parser"
Nov 10 07:17:02 george-ThinkPad-T420 kernel: [ 58.255045] type=1400 audit(1447157822.082:55): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/sbin/cupsd" pid=2175 comm="apparmor_parser"
Nov 10 07:17:02 george-ThinkPad-T420 colord: Profile added: HP-LaserJet-P1505n-Gray..
Nov 10 07:17:02 george-ThinkPad-T420 colord: Device added: cups-HP-LaserJet-P1505n
Nov 10 07:17:04 george-ThinkPad-T420 dbus[567]: [system] Activating service name='org.freedesktop.systemd1' (using servicehelper)
Nov 10 07:17:04 george-ThinkPad-T420 dbus[567]: [system] Successfully activated service 'org.freedesktop.systemd1'
-----------------------------------------------------------------------------------------------------------------
Following is the same region of the startup record for the third (successful) startup:
-----------------------------------------------------------------------------------------------------------------
Startup 3 (only asked for user authentication once):
Nov 10 07:18:11 george-ThinkPad-T420 gnome-session[1663]: GLib-CRITICAL: g_environ_setenv: assertion 'value != NULL' failed
Nov 10 07:18:13 george-ThinkPad-T420 ModemManager[784]: Creating modem with plugin 'Generic' and '1' ports
Nov 10 07:18:14 george-ThinkPad-T420 ModemManager[784]: Could not grab port (tty/ttyS4): 'Cannot add port 'tty/ttyS4', unhandled serial type'
Nov 10 07:18:14 george-ThinkPad-T420 ModemManager[784]: Couldn't create modem for device at '/sys/devices/pci0000:00/0000:00:16.3': Failed to find primary AT port
Nov 10 07:18:15 george-ThinkPad-T420 dbus[573]: [system] Activating service name='org.freedesktop.UDisks2' (using servicehelper)
Nov 10 07:18:15 george-ThinkPad-T420 udisksd[1978]: udisks daemon version 2.1.3 starting
Nov 10 07:18:15 george-ThinkPad-T420 dbus[573]: [system] Successfully activated service 'org.freedesktop.UDisks2'
------------------------------------------------------------------------------------------------------------------
Note that the third startup is to a different service than the first two.
What is the difference between org.freedesktop.systemd1 and org.freedesktop.UDisks2 ?
Taking a stab at answering my own question:
> What is the difference between org.freedesktop.systemd1 and org.freedesktop.UDisks2 ?
The latter makes it possible to mount a [Windows] hard drive without a password;
the former ? http://trisquel.info/en/forum/could-systemd-be-inconvenient-portability
Is this another wet pants-psychiatrist problem ?
Next time I'll just enter my password a second time and see what happens.
Last night I wrote:
> Next time I'll just enter my password a second time and see what happens.
OK. I did it, and I was asked to authenticate _three_ times.
All I can say is that I see these twice in the syslog:
> Nov 12 08:21:32 george-ThinkPad-T420 kernel: [ 53.726908] do_trap: 105 callbacks suppressed
> Nov 12 08:21:32 george-ThinkPad-T420 kernel: [ 53.726912] traps: gnome-panel[1873] trap int3 ip:7f266e18fc13 sp:7fff36dd0f40 error:0
> Nov 12 08:21:33 george-ThinkPad-T420 gnome-session[1677]: WARNING: Application 'gnome-panel.desktop' killed by signal 5
> Nov 12 08:21:33 george-ThinkPad-T420 kernel: [ 54.711111] traps: gnome-panel[1962] trap int3 ip:7f2eeb21ec13 sp:7fff27e3bd50 error:0
> Nov 12 08:21:33 george-ThinkPad-T420 gnome-session[1677]: WARNING: App 'gnome-panel.desktop' respawning too quickly
> Nov 12 08:21:33 george-ThinkPad-T420 gnome-session[1677]: CRITICAL: We failed, but the fail whale is dead. Sorry....
> Nov 12 08:21:47 george-ThinkPad-T420 kernel: [ 68.892798] traps: gnome-panel[2337] trap int3 ip:7f87feb1ac13 sp:7ffebee3f880 error:0
> Nov 12 08:21:47 george-ThinkPad-T420 dbus[930]: [system] Activating service name='org.freedesktop.UDisks2' (using servicehelper)
> Nov 12 08:21:47 george-ThinkPad-T420 gnome-session[2133]: WARNING: Application 'gnome-panel.desktop' killed by signal 5
> Nov 12 08:21:47 george-ThinkPad-T420 kernel: [ 69.144803] traps: gnome-panel[2451] trap int3 ip:7feaedad2c13 sp:7ffc44a8d2f0 error:0
> Nov 12 08:21:48 george-ThinkPad-T420 gnome-session[2133]: WARNING: App 'gnome-panel.desktop' respawning too quickly
> Nov 12 08:21:48 george-ThinkPad-T420 gnome-session[2133]: CRITICAL: We failed, but the fail whale is dead. Sorry....
There were three numbered gnome-sessions, and org.freedesktop.systemd1 won out in the end.
I tried dmesg |tail:
[ 37.597201] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
[ 37.838924] init: samba-ad-dc main process (1347) terminated with status 1
[ 53.726908] do_trap: 105 callbacks suppressed
[ 53.726912] traps: gnome-panel[1873] trap int3 ip:7f266e18fc13 sp:7fff36dd0f40 error:0
[ 54.711111] traps: gnome-panel[1962] trap int3 ip:7f2eeb21ec13 sp:7fff27e3bd50 error:0
[ 68.892798] traps: gnome-panel[2337] trap int3 ip:7f87feb1ac13 sp:7ffebee3f880 error:0
[ 69.144803] traps: gnome-panel[2451] trap int3 ip:7feaedad2c13 sp:7ffc44a8d2f0 error:0
[ 1390.920079] type=1400 audit(1447335829.661:59): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/cups/backend/cups-pdf" pid=3443 comm="apparmor_parser"
[ 1390.920091] type=1400 audit(1447335829.661:60): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/sbin/cupsd" pid=3443 comm="apparmor_parser"
[ 1390.920976] type=1400 audit(1447335829.662:61): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/sbin/cupsd" pid=3443 comm="apparmor_parser"
There are a bunch of bugs related to "gnome-panel trap int3" but I see no solutions.
I ran Software-updater and got Linux-Libre 3.13.0-678lowlatency, etc.
Still asking for the password twice ...
Here's what seems to be the trouble in the syslog:
> Nov 12 12:52:05 george-ThinkPad-T420 kernel: [ 51.353770] traps: gnome-panel[1974] trap int3 ip:7fe5b372dc13 sp:7ffd3b78b250 error:0
> Nov 12 12:52:05 george-ThinkPad-T420 gnome-session[1669]: WARNING: App 'gnome-panel.desktop' respawning too quickly
> Nov 12 12:52:05 george-ThinkPad-T420 gnome-session[1669]: CRITICAL: We failed, but the fail whale is dead. Sorry....
Here's what I get with dmesg, in part:
[ 38.663736] wlan0: authenticate with 00:7f:28:26:11:a1
[ 39.097440] wlan0: send auth to 00:7f:28:26:11:a1 (try 1/3)
[ 39.099319] wlan0: authenticated
[ 39.100327] wlan0: associate with 00:7f:28:26:11:a1 (try 1/3)
[ 39.103900] wlan0: RX AssocResp from 00:7f:28:26:11:a1 (capab=0x431 status=0 aid=1)
[ 39.116132] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
[ 39.116270] wlan0: associated
[ 39.147136] wlan0: deauthenticating from 00:7f:28:26:11:a1 by local choice (reason=2)
[ 39.294825] cfg80211: Calling CRDA for country: US
[ 39.294922] wlan0: authenticate with 00:7f:28:26:11:a1
[ 39.570701] wlan0: send auth to 00:7f:28:26:11:a1 (try 1/3)
[ 39.572553] wlan0: authenticated
[ 39.573410] wlan0: associate with 00:7f:28:26:11:a1 (try 1/3)
[ 39.576934] wlan0: RX AssocResp from 00:7f:28:26:11:a1 (capab=0x431 status=0 aid=1)
[ 39.591218] wlan0: associated
[ 47.912367] do_trap: 105 callbacks suppressed
[ 47.912372] traps: gnome-panel[1874] trap int3 ip:7ffad67b2c13 sp:7ffd85afc550 error:0
[ 51.353770] traps: gnome-panel[1974] trap int3 ip:7fe5b372dc13 sp:7ffd3b78b250 error:0
These multiple password requests seem to be coming from wlan0.
I am a translator!
amenex: if you like tinkering with your system and finding the root of an issue is something you are very passionate about then keep doing it. That is indeed a nice thing and wanting to understand how something works or why it doesn't work and how to possibly solve it is actually an admirable behavior.
BUT..
if that is not the case and you just want this thing solved and you reckon it is a bug that it is worth reinstalling, then do a fresh installation. It will take you 3 hours tops to reinstall everything and customize it the way you want it. On the other hand trying to solve it has already taken more time (I guess) to you and will take you even more (I guess).
cheers
[ 39.147136] wlan0: deauthenticating from 00:7f:28:26:11:a1 by local choice (reason=2)
Here's why, I suppose. How is it possible to find that reason=2?
Didn't read them, but they talk about it here:
https://code.google.com/p/chromium/issues/detail?id=186867
http://crunchbang.org/forums/viewtopic.php?id=31052
SuperTramp83 suggested that I see the the proverbial psychiatrist about a problem that appears to be mine alone, so I can let my system keep on doing the double-password thing without having it get under my skin. He's right !
In the meantime I'm gradually stashing my important data in safe places ... when that's accomplished, I'll probably _really_ not care much about the double passwords any more. After all, it's just the authorization of wlan0.
Solved. Everybody except the developer[s?] gave up on this issue, and so it went away. Dunno why ...
- Anmelden oder Registrieren um Kommentare zu schreiben