No login

unklar · 2016-04-19 15:40:30

I have the same problem as here, on a real machine.
Yesterday, the d-u

Log started: 2016-04-18  16:32:16
(Lese Datenbank ... 
...
(Lese Datenbank ... 100%
(Lese Datenbank ... 106325 Dateien und Verzeichnisse sind derzeit installiert.)
Vorbereitung zum Entpacken von .../bunsen-pipemenus_8.9-1_all.deb ...
Entpacken von bunsen-pipemenus (8.9-1) über (8.8.4-1) ...
Vorbereitung zum Entpacken von .../bunsen-welcome_8.10-1_all.deb ...
Entpacken von bunsen-welcome (8.10-1) über (8.9-1) ...
Vorbereitung zum Entpacken von .../bunsen-common_8.8-1_all.deb ...
Entpacken von bunsen-common (8.8-1) über (8.7.1-1) ...
Vorbereitung zum Entpacken von .../bunsen-configs_8.7-1_all.deb ...
Entpacken von bunsen-configs (8.7-1) über (8.6.15-1) ...
Vorbereitung zum Entpacken von .../bunsen-docs_8.1-1_all.deb ...
Entpacken von bunsen-docs (8.1-1) über (8.0.2-2) ...
Vorbereitung zum Entpacken von .../bunsen-images_8.5-1_all.deb ...
Entpacken von bunsen-images (8.5-1) über (8.4-1) ...
Vorbereitung zum Entpacken von .../bunsen-meta-java_8.10-1_all.deb ...
Entpacken von bunsen-meta-java (8.10-1) über (8.9-1) ...
Vorbereitung zum Entpacken von .../bunsen-meta-printer-support_8.10-1_all.deb ...
Entpacken von bunsen-meta-printer-support (8.10-1) über (8.9-1) ...
Vorbereitung zum Entpacken von .../bunsen-meta-ssh_8.10-1_all.deb ...
Entpacken von bunsen-meta-ssh (8.10-1) über (8.9-1) ...
Vorbereitung zum Entpacken von .../bunsen-meta-vcs_8.10-1_all.deb ...
Entpacken von bunsen-meta-vcs (8.10-1) über (8.9-1) ...
Vorbereitung zum Entpacken von .../bunsen-utilities_8.6.7-1_all.deb ...
Entpacken von bunsen-utilities (8.6.7-1) über (8.6.5-1) ...
Trigger für hicolor-icon-theme (0.13-1) werden verarbeitet ...
Trigger für desktop-file-utils (0.22-1) werden verarbeitet ...
Trigger für mime-support (3.58) werden verarbeitet ...
bunsen-common (8.8-1) wird eingerichtet ...
bunsen-pipemenus (8.9-1) wird eingerichtet ...
bunsen-welcome (8.10-1) wird eingerichtet ...
bunsen-configs (8.7-1) wird eingerichtet ...
Neue Version der Konfigurationsdatei /etc/lightdm/lightdm-gtk-greeter.conf.bunsen wird installiert ...

Konfigurationsdatei »/etc/lightdm/lightdm.conf.bunsen«
 ==> Geändert (von Ihnen oder von einem Skript) seit der Installation.
 ==> Paketverteiler hat eine aktualisierte Version herausgegeben.
   Wie möchten Sie vorgehen? Ihre Wahlmöglichkeiten sind:
    Y oder I : Die Version des Paket-Betreuers installieren
    N oder O : Die momentan installierte Version beibehalten
       D     : Die Unterschiede zwischen den Versionen anzeigen
       Z     : Eine Shell starten, um die Situation zu begutachten
 Der Standardweg ist das Beibehalten der momentanen Version.
*** lightdm.conf.bunsen (Y/I/N/O/D/Z) [Vorgabe=N] ? N
bunsen-docs (8.1-1) wird eingerichtet ...
bunsen-images (8.5-1) wird eingerichtet ...
update-alternatives: /usr/share/images/bunsen/grub/default.png wird verwendet, um /usr/share/images/desktop-base/desktop-grub.png (desktop-grub) im automatischen Modus bereitzustellen
update-alternatives: /usr/share/images/bunsen/login/default.png wird verwendet, um /usr/share/images/bunsen/login/bl-login-background (bl-login-background) im automatischen Modus bereitzustellen
Generating grub configuration file ...
Found background image: /usr/share/images/desktop-base/desktop-grub.png
Linux-Abbild gefunden: /boot/vmlinuz-3.16.0-4-amd64
initrd-Abbild gefunden: /boot/initrd.img-3.16.0-4-amd64
Mageia 5 (5) auf /dev/sda1 gefunden
Mageia 6 LXQT (6) auf /dev/sda11 gefunden
siduction LXQt-DR (2014.1 ) auf /dev/sda12 gefunden
ROSA Desktop Fresh R5 (2014.1) auf /dev/sda7 gefunden
Mageia 4 kde (4) auf /dev/sda8 gefunden
Mageia 6 (6) auf /dev/sda9 gefunden
Windows 7 (loader) auf /dev/sdb1 gefunden
Arch auf /dev/sdb5 gefunden
KaOS (rolling) auf /dev/sdb7 gefunden
erledigt
bunsen-meta-java (8.10-1) wird eingerichtet ...
bunsen-meta-printer-support (8.10-1) wird eingerichtet ...
bunsen-meta-ssh (8.10-1) wird eingerichtet ...
bunsen-meta-vcs (8.10-1) wird eingerichtet ...
bunsen-utilities (8.6.7-1) wird eingerichtet ...
Log ended: 2016-04-18  16:35:47

Sign up is made so far with "Auto-login"
Now I'm on tty1 and "startx" in the system.

What should I do?

Head_on_a_Stick · 2016-04-19 20:51:24

I think this is the problem:

Konfigurationsdatei »/etc/lightdm/lightdm.conf.bunsen«
 ==> Geändert (von Ihnen oder von einem Skript) seit der Installation.
 ==> Paketverteiler hat eine aktualisierte Version herausgegeben.
   Wie möchten Sie vorgehen? Ihre Wahlmöglichkeiten sind:
    Y oder I : Die Version des Paket-Betreuers installieren
    N oder O : Die momentan installierte Version beibehalten
       D     : Die Unterschiede zwischen den Versionen anzeigen
       Z     : Eine Shell starten, um die Situation zu begutachten
 Der Standardweg ist das Beibehalten der momentanen Version.
*** lightdm.conf.bunsen (Y/I/N/O/D/Z) [Vorgabe=N] ? N

It looks like you have kept the old version of /etc/lightdm/lightdm.conf.bunsen when you should have accepted the new version.

Try re-installing the package and say "yes" when it asks again.

sudo aptitude reinstall bunsen-configs

jjr · 2016-04-19 21:32:39

Hello,
After update, I have kept the old version of /etc/lightdm/lightdm.conf.bunsen .
And now the system doesn't accept my password.
I can't open my pc
How to solved that

sudo aptitude reinstall bunsen-configs

doesn't work

I have installed slim to work with my equipment.

But it's not the good solution I thinks

Thanks

Last edited by jjr (2016-04-19 22:07:48)

Head_on_a_Stick · 2016-04-19 21:38:34

jjr wrote:

I can't open my pc
How to solved that

Press <Ctrl>+<Alt>+F2 (at the same time) to get to a console screen and login from there instead.

You can then run this command to start you desktop:

startx

Head_on_a_Stick · 2016-04-19 21:40:39

jjr wrote:

sudo aptitude reinstall bunsen-configs

doesn't work

Oh dear

Did you see the question again?

Did you answer "yes" to the question?

EDIT: Try:

sudo mv /etc/lightdm/lightdm.conf.bunsen ~/
sudo aptitude reinstall bunsen-configs

Last edited by Head_on_a_Stick (2016-04-19 21:48:28)

Sector11 · 2016-04-19 22:03:02

My BL gets to the login screen - my username is there but it will not accept my password.

EDIT:

What do I do? What I did:

Logged in with another distro ( #! on Wheezy to be exact ) and as root edited:

/etc/lightdm/lightdm.conf.bunsen

(thanks HoaS)

editing line 114 to read:

session-setup-script=/usr/lib/bunsen/configs/bl-user-setup

(thanks damo)

That got me here in my BunsenLabs again.

Now can someone please help me with these:

Grub has the Debian screen now, and
Lightdm has a black background - no Bunsen image

Any help appreciated.

damo · 2016-04-19 22:39:09

Sector11 wrote:

My BL gets to the login screen - my username is there but it will not accept my password.
What do I do?

Have you tried this fix...?
Edit `/etc/lightdm/lightdm.conf`. It should have line 114 changed to reflect the filepaths changes:

session-setup-script=/usr/lib/bunsen/configs/bl-user-setup

Then restart

Ninja EDIT

For grub you can try `Menu -> System -> Edit Debian Alternatives`

For lightdm, check `lightdm-gtk-greeter`. Menu -> System -> Login Settings

background=/usr/share/images/bunsen/login/bl-login-background

(You can change it with Debian Alternatives)

Last edited by damo (2016-04-19 22:43:27)

Sector11 · 2016-04-20 00:58:09

Thanks damo.

That did lightdm by editing: /etc/lightdm/lightdm-gtk-greeter.conf.bunsen - which is what I was looking for anyway

... but it didn't get the grub screen.

What 'file' do I need to edit for grub. All I can fine is: /boot/grub/grub.cfg that starts with:

#
# DO NOT EDIT THIS FILE
#

Horizon_Brave · 2016-04-20 01:06:00

Sector11 wrote:

Thanks damo.
That did lightdm by editing: /etc/lightdm/lightdm-gtk-greeter.conf.bunsen - which is what I was looking for anyway
... but it didn't get the grub screen.
What 'file' do I need to edit for grub. All I can fine is: /boot/grub/grub.cfg that starts with:
#
# DO NOT EDIT THIS FILE
#

Try /etc/default/grub

EDIT: Oh yea and you'll have to run the "update-grub" command after for any changes to take place ;D

Last edited by Horizon_Brave (2016-04-20 01:11:16)

johnraff · 2016-04-20 01:36:23

damo wrote:

For grub you can try `Menu -> System -> Edit Debian Alternatives`

And the alternative to edit is "desktop-grub".
Then

Horizon_Brave wrote:

you'll have to run the "update-grub" command after for any changes to take place

If that doesn't work I'd like to know, because it means a bug somewhere.

Sector11 · 2016-04-20 01:53:17

Well I checked and it was set to use the default ... I've rebooted twice and got the "Debian 8" screen...
So I did both steps again - again choosing the default grub screen and then running upg (alias for sudo update-grub) and rebooted ... and it worked??????????

I'm going to bed now ... I'm jinxed. but at least it got it.

jjr · 2016-04-20 06:11:21

Hello,
solved with editing line 114.

Thanks for your help

unklar · 2016-04-20 10:16:50

Actually this is a joke, what are you doing here.
It can not be that the update new bunsen-software

..
bunsen-common (8.8-1) wird eingerichtet ...
bunsen-pipemenus (8.9-1) wird eingerichtet ...
bunsen-welcome (8.10-1) wird eingerichtet ...
bunsen-configs (8.7-1) wird eingerichtet ...
Neue Version der Konfigurationsdatei /etc/lightdm/lightdm-gtk-greeter.conf.bunsen wird installiert ...

the debian-rule

Konfigurationsdatei »/etc/lightdm/lightdm.conf.bunsen«
 ==> Geändert (von Ihnen oder von einem Skript) seit der Installation.
 ==> Paketverteiler hat eine aktualisierte Version herausgegeben.
   Wie möchten Sie vorgehen? Ihre Wahlmöglichkeiten sind:
    Y oder I : Die Version des Paket-Betreuers installieren
    N oder O : Die momentan installierte Version beibehalten
       D     : Die Unterschiede zwischen den Versionen anzeigen
       Z     : Eine Shell starten, um die Situation zu begutachten
 Der Standardweg ist das Beibehalten der momentanen Version.
*** lightdm.conf.bunsen (Y/I/N/O/D/Z) [Vorgabe=N] ? N

is turned off and the user no longer comes into its system with its PW.

The different answers, what to do, prove that.

Right now I'm by the command of HoaS

sudo systemctl set-default multi-user.target

to tty1 and sign up there with User + Pw on and start X with "startx".

Maybe I should all back "and consider purging" and only work with lightdm because bunsen my main system and its GRUB is started all the other distros.

Sorry, that was my 2 cents.
Yes, and the announcement is here, I had not noticed. :8

xaos52 · 2016-04-20 11:32:01

Hi unklar,

unklar wrote:

"and consider purging"

It is not clear to me what you mean by that.
Es ist mir nicht klar, was sie damit meinen, unklar

Is your problem solved, or do you need more help?

Head_on_a_Stick · 2016-04-20 18:24:59

@unklar -- this command will fix your system:

git clone https://github.com/BunsenLabs/bunsen-configs.git && sudo cp bunsen-configs/lightdm.conf.bunsen /etc/lightdm/lightdm.conf.bunsen && rm -rf bunsen-configs

unklar · 2016-04-21 09:15:26

@xaos52,
I was angry.

@HoaS,
too late.
johnraff

Thanks.

Last edited by unklar (2016-04-21 09:16:18)

#1 2016-04-19 15:40:30

No login

#2 2016-04-19 20:51:24

Re: No login

#3 2016-04-19 21:32:39

Re: No login

#4 2016-04-19 21:38:34

Re: No login

#5 2016-04-19 21:40:39

Re: No login

#6 2016-04-19 22:03:02

Re: No login

EDIT:

#7 2016-04-19 22:39:09

Re: No login

#8 2016-04-20 00:58:09

Re: No login

#9 2016-04-20 01:06:00

Re: No login

#10 2016-04-20 01:36:23

Re: No login

#11 2016-04-20 01:53:17

Re: No login

#12 2016-04-20 06:11:21

Re: No login

#13 2016-04-20 10:16:50

Re: No login

#14 2016-04-20 11:32:01

Re: No login

#15 2016-04-20 18:24:59

Re: No login

#16 2016-04-21 09:15:26

Re: No login

Board footer