Hello,
I boot to grafical login screen, but i’m not able to log in. When I switch to command line mode (by Ctrl+Alt+F2), I can log in corectly. Next I can run X Server (by command startx), but only in super user mode.
Thenks for help.
Hello,
I boot to grafical login screen, but i’m not able to log in. When I switch to command line mode (by Ctrl+Alt+F2), I can log in corectly. Next I can run X Server (by command startx), but only in super user mode.
Thenks for help.
That’s normal. Running startx as user is not supported anymore by default because of security reasons.
Does it work if you select another session at the graphical login screen? (IceWM f.e.)
Also, what exactly happens when you are “not able to login”? Do you get an error message?
On 2013-07-17 12:46, socool2 wrote:
>
> Hello,
>
> I boot to grafical login screen, but i’m not able to log in. When I
> switch to command line mode (by Ctrl+Alt+F2), I can log in corectly.
> Next I can run X Server (by command startx), but only in super user
> mode.
Run “df -h” there, see if there is any partition full.
–
Cheers / Saludos,
Carlos E. R.
(from 12.3 x86_64 “Dartmouth” at Telcontar)
Unable to login mean, that after I type username and password nothing happened. I’m still on login screen.
I use LXDE. I also try Openbox, but with same result.
Result of df -h:
raspberrypi:~ # df -h
Filesystem Size Used Avail Use% Mounted on
/dev/root 9.9G 2.6G 6.9G 28% /
devtmpfs 85M 4.0K 85M 1% /dev
tmpfs 93M 0 93M 0% /dev/shm
tmpfs 93M 2.1M 91M 3% /run
tmpfs 93M 0 93M 0% /sys/fs/cgroup
tmpfs 93M 2.1M 91M 3% /var/lock
tmpfs 93M 2.1M 91M 3% /var/run
/dev/mmcblk0p1 75M 15M 61M 20% /boot
/dev/mmcblk0p4 3.4G 71M 3.2G 3% /home
And what login manager are you using? (kdm, gdm, …)
Try switching to xdm.
DISPLAYMANAGER="xdm"
I have try it, but style same result. I’m not able to login. I also try lxdm. I don’t know why, but when i login as standart user to command line mode, sytem wont to change user password.
Now it look that:
startx
startlxdm
Have you some idea, where can be problem?
On 2013-07-19 21:36, socool2 wrote:
> Now it look that:
>
> 1) I’m not able to login on grafical login screen.
> 2) I can login at commandline mode as standard user (change pasword
> required) and also as root
Have you tried changing that password?
–
Cheers / Saludos,
Carlos E. R.
(from 12.3 x86_64 “Dartmouth” at Telcontar)
Yes I change it each time when it was required
On 2013-07-19 22:16, socool2 wrote:
>
> Yes I change it each time when it was required
Huh? You don’t have a normal setup. By default it is never required.
What else have you changed?
–
Cheers / Saludos,
Carlos E. R.
(from 12.3 x86_64 “Dartmouth” at Telcontar)
Only password was required.
I have the same problem. (For info: I just did a hostile upgrade from 12.2 32-bit to 12.3 64-bit. It worked a whole lot better than I had any reason to expect.)
12.2 was fine. Now I can only login with root.
Login as myself gives gfx modes changing a few times (I see the crt futz the display back and forth) and then I am back to login again.
I tried making a new user. I briefly saw a gnome error message pop up before the login screen jumped back.
Then I tried to login with TWM(?), and now I am typing here as you can see.
There is some error that gnome is not happy about. Could it be some of this I see from dmesg?
1177.489665] nvidia 0000:02:00.0: irq 46 for MSI/MSI-X
1185.069772] end_request: I/O error, dev fd0, sector 0
1185.094703] end_request: I/O error, dev fd0, sector 0
1185.506560] gnome-panel[6063]: segfault at 8 ip 00007f924b595845 sp 00007fffb40f35b0 error 4 in libstartup-notification-1.so.0.0.0[7f924b592000+9000]
1185.851693] nvidia 0000:02:00.0: irq 46 for MSI/MSI-X
1199.794592] end_request: I/O error, dev fd0, sector 0
1199.820506] end_request: I/O error, dev fd0, sector 0
1963.853153] nvidia 0000:02:00.0: irq 46 for MSI/MSI-X
1974.939300] nvidia 0000:02:00.0: irq 46 for MSI/MSI-X
1985.046693] end_request: I/O error, dev fd0, sector 0
1985.070614] end_request: I/O error, dev fd0, sector 0
2121.768243] gnome-panel[7462]: segfault at 20be200 ip 00000000020be200 sp 00007fffe5b6b778 error 15
2122.094741] nvidia 0000:02:00.0: irq 46 for MSI/MSI-X
2138.204512] end_request: I/O error, dev fd0, sector 0
2138.229441] end_request: I/O error, dev fd0, sector 0
2140.218628] nvidia 0000:02:00.0: irq 46 for MSI/MSI-X
On 2013-07-31 07:06, NorthWay wrote:
>
> I have the same problem. (For info: I just did a hostile upgrade from
> 12.2 32-bit to 12.3 64-bit. It worked a whole lot better than I had any
> reason to expect.)
I did that myself, on another version.
>
> 12.2 was fine. Now I can only login with root.
> Login as myself gives gfx modes changing a few times (I see the crt
> futz the display back and forth) and then I am back to login again.
I would run an rpm query to verify that there are no 32 bit packages hiding.
rpm -q -a --queryformat "%{INSTALLTIME} %{INSTALLTIME:day} \
%{BUILDTIME:day} %-30{NAME} %15{VERSION}-%-7{RELEASE} %{arch} \
%25{VENDOR}%25{PACKAGER} == %{DISTRIBUTION} %{DISTTAG}
" \
| sort | cut --fields="2-" | tee rpmlist | less -S
I think the {arch} field is the one of interest for you.
–
Cheers / Saludos,
Carlos E. R.
(from 12.3 x86_64 “Dartmouth” at Telcontar)
Ehm… that was a list of 2753 lines. And I don’t really know exactly what I’m looking for…
Is there any log or errors file somewhere that I can peek into to see what barfs when I log in?
(And did I get some funny font business in the upgrade? I seem to have fixed width fonts in Firefox menues now.)
On 2013-08-01 02:16, NorthWay wrote:
>
> robin_listas;2575845 Wrote:
>>
>> I would run an rpm query to verify that there are no 32 bit packages
>> hiding.
>>
> Ehm… that was a list of 2753 lines. And I don’t really know exactly
> what I’m looking for…
Well, the {arch} field should be “x86_64”. If you see anything
different, like “i686” or “i686”, you should investigate that package.
> Is there any log or errors file somewhere that I can peek into to see
> what barfs when I log in?
The first thing to do after a 32–>64 bit upgrade is verifying that you
do not have 32 bit packages remaining. When you do that, we can go to
other ideas.
As you also upgraded from 12.2 to 12.3, another possibility is that you
have 12.2 packages remaining. This should be easier to verify:
rpm -q -a --queryformat "%{INSTALLTIME} %{INSTALLTIME:day} \
%{BUILDTIME:day} %-30{NAME} %15{VERSION}-%-7{RELEASE} %{arch} \
%25{VENDOR}%25{PACKAGER} == %{DISTRIBUTION} %{DISTTAG}
" \
| sort | cut --fields="2-" | tee rpmlist | \
egrep -v "openSUSE.12\.3" | less -S
This assuming that the string to find is exactly “openSUSE.12.3” - if
some packages have different tags, they will hide from the filter.
Notice that the list is sorted by date: the lines at the top are the
older packages, possibly from before the upgrade, so they are the
candidates for inspection. Those are the bottom are new and safe.
–
Cheers / Saludos,
Carlos E. R.
(from 12.3 x86_64 “Dartmouth” at Telcontar)
I rolled back 12.2. I’ll wait for the next release before I try again.
On 2013-08-02 18:46, NorthWay wrote:
>
> I rolled back 12.2. I’ll wait for the next release before I try again.
Oh
–
Cheers / Saludos,
Carlos E. R.
(from 12.3 x86_64 “Dartmouth” at Telcontar)