Re: [Evergreen] 13.1 - latest update broke graphical login

[Axel Braun]

Hi,
let me answer in one run.

Am Freitag, 28. Oktober 2016, 16:40:12 schrieb Bruno Friedmann:
> On vendredi, 28 octobre 2016 14.37:41 h CEST Axel Braun wrote:
> > Am Freitag, 28. Oktober 2016, 14:21:18 schrieb Carlos E. R.:
> > > >> Any idea what this could be ?
> > > > 
> > > > when I have seen startx can access but other methods fail, the
> > > > graphical
> > > > driver has not matched the kernel (nvidia in my experience) and/or
> > > > perms
> > > > for /usr/bin/Xorg needs to be suid.
> > > 
> > > When the nvidia driver fails it fails both in level 5 and via startx.
> > > Actually, starting via startx serves to read the diagnosis messages.
> > > 
> > > 
> > > Axel, I would look at "/var/log/Xorg.0.log*" files for clues.

That looks OK to me - it installs the Radeon driver for the Mobility X600 chip 
(yes, its quite old)
and it claims that it does not find the legacy fglrx driver. No other EE 
messages

> Also check if your system is still setup to boot on level 5
> 
> it can be changed by yast, or systemctl
> 
> systemctl status default.target
> ● graphical.target - Graphical Interface

This is interresting, If I go into the runlevel editor in Yast it does not 
offer anyrunlevels to set (expert mode) - the combo-box is empty!

Anyway, systemctl get-default issues graphical.target as result.
Having set this once again, and rebootet, the output during boot is still
'Reached target graphical interface'

So...even if the Default_WM would have changed, it should at least reach the 
login screen
Switching console with ALT-Fx, terminal login and startx still works...

Any other ideas?
Thx
Axel
___
Evergreen mailing list
Evergreen@lists.rosenauer.org
http://lists.rosenauer.org/mailman/listinfo/evergreen

Re: [Evergreen] 13.1 - latest update broke graphical login

[Axel Braun]

Am Freitag, 28. Oktober 2016, 14:21:18 schrieb Carlos E. R.:
> >> Any idea what this could be ?
> >
> > when I have seen startx can access but other methods fail, the graphical
> > driver has not matched the kernel (nvidia in my experience) and/or perms
> > for /usr/bin/Xorg needs to be suid.
> 
> When the nvidia driver fails it fails both in level 5 and via startx.
> Actually, starting via startx serves to read the diagnosis messages.
> 
> 
> Axel, I would look at "/var/log/Xorg.0.log*" files for clues.

Will do when I'm back at that Laptop, thanks!

/Ax
___
Evergreen mailing list
Evergreen@lists.rosenauer.org
http://lists.rosenauer.org/mailman/listinfo/evergreen

[Evergreen] 13.1 - latest update broke graphical login

[Axel Braun]

Hi,

as we know from Murphy's law, one issue does not come aloneafter the 
desktop PC died I got an old ThinkPad Z60m out of the drawer, run an update on 
the installed 13.1 (some 500MB - last update was some time ago - graphical 
login is not working any longer. It is stuck at 

2016-10-28T11:47:10.881583+02:00 Z60 systemd[1]: Starting Graphical Interface.
2016-10-28T11:47:10.888012+02:00 Z60 systemd[1]: Reached target Graphical 
Interface.
...but no graphical login comes up.

The rest from the /var/log/messages does not tell me too much with regard to 
this issue:

2016-10-28T11:47:10.881583+02:00 Z60 systemd[1]: Starting Graphical Interface.
2016-10-28T11:47:10.888012+02:00 Z60 systemd[1]: Reached target Graphical 
Interface.
2016-10-28T11:47:10.893618+02:00 Z60 systemd[1]: Starting Stop Read-Ahead Data 
Collection 10s After Completed Startup.
2016-10-28T11:47:10.896837+02:00 Z60 systemd[1]: Started Stop Read-Ahead Data 
Collection 10s After Completed Startup.
2016-10-28T11:47:10.906509+02:00 Z60 systemd[1]: Starting Update UTMP about 
System Runlevel Changes...
2016-10-28T11:47:10.921473+02:00 Z60 systemd[1]: Started Update UTMP about 
System Runlevel Changes.
2016-10-28T11:47:10.935072+02:00 Z60 systemd[1]: Startup finished in 13.092s 
(kernel) + 22.798s (userspace) = 35.891s.
2016-10-28T11:47:15.916961+02:00 Z60 kernel: [   40.872436] lib80211_crypt: 
registered algorithm 'CCMP'
2016-10-28T11:47:15.923906+02:00 Z60 kernel: [   40.879228] lib80211_crypt: 
registered algorithm 'TKIP'
2016-10-28T11:47:16.157378+02:00 Z60 dhclient[1035]: Internet Systems 
Consortium DHCP Client 4.2.5-P1
2016-10-28T11:47:16.158317+02:00 Z60 dhclient[1035]: Copyright 2004-2013 
Internet Systems Consortium.
2016-10-28T11:47:16.158670+02:00 Z60 dhclient[1035]: All rights reserved.
2016-10-28T11:47:16.159010+02:00 Z60 dhclient[1035]: For info, please visit 
https://www.isc.org/software/dhcp/
2016-10-28T11:47:16.159335+02:00 Z60 dhclient[1035]: 
2016-10-28T11:47:16.214188+02:00 Z60 dhclient[1035]: Listening on 
LPF/eth1/00:13:ce:c7:09:dd
2016-10-28T11:47:16.215831+02:00 Z60 dhclient[1035]: Sending on   
LPF/eth1/00:13:ce:c7:09:dd
2016-10-28T11:47:16.216731+02:00 Z60 dhclient[1035]: Sending on   
Socket/fallback
2016-10-28T11:47:16.217568+02:00 Z60 dhclient[1035]: DHCPREQUEST on eth1 to 
255.255.255.255 port 67
2016-10-28T11:47:16.220535+02:00 Z60 dhclient[1035]: DHCPACK from 192.168.2.1
2016-10-28T11:47:16.235284+02:00 Z60 dhclient[1035]: bound to 192.168.2.111 -- 
renewal in 40093 seconds.
2016-10-28T11:47:16.235994+02:00 Z60 avahi-daemon[655]: Joining mDNS multicast 
group on interface eth1.IPv4 with address 192.168.2.111.
2016-10-28T11:47:16.236712+02:00 Z60 avahi-daemon[655]: New relevant interface 
eth1.IPv4 for mDNS.
2016-10-28T11:47:16.237221+02:00 Z60 avahi-daemon[655]: Registering new address 
record for 192.168.2.111 on eth1.IPv4.
2016-10-28T11:47:17.326244+02:00 Z60 dbus[653]: [system] Activating via 
systemd: service name='org.freedesktop.nm_dispatcher' 
unit='dbus-org.freedesktop.nm-dispatcher.service'
2016-10-28T11:47:17.327694+02:00 Z60 dbus[653]: [system] Activation via systemd 
failed for unit 'dbus-org.freedesktop.nm-dispatcher.service': Unit 
dbus-org.freedesktop.nm-dispatcher.service failed to load: No such file or 
directory.
2016-10-28T11:47:24.001557+02:00 Z60 kernel: [   48.957593] nf_conntrack: 
automatic helper assignment is deprecated and it will be removed soon. Use the 
iptables CT target to attach helpers instead.
2016-10-28T11:47:41.045423+02:00 Z60 systemd[1]: Starting Stop Read-Ahead Data 
Collection...
2016-10-28T11:47:41.057079+02:00 Z60 systemd[1]: Started Stop Read-Ahead Data 
Collection.
2016-10-28T11:48:09.643541+02:00 Z60 systemd[1]: Received SIGINT.

-> I rebooted here

when booting into console and running startx it works as normal.

Any idea what this could be ?

Thanks
Axel
___
Evergreen mailing list
Evergreen@lists.rosenauer.org
http://lists.rosenauer.org/mailman/listinfo/evergreen

Re: [Evergreen] openSUSE 13.1 after 2016-11-01

[Axel Braun]

Am Sonntag, 23. Oktober 2016, 22:49:26 schrieb Felix Miata:
> > Me, I think something else would be easier, perhaps ubuntu.
> 
> Ubuntu *is* (a) Debian (derivative), just with a custom set of personality 
> modifications designed for shielding its users from the underlying power of 
> FOSS, e.g. Unity (aka only one way), and sudo (Ugh!).

As long as you just use it from the CLI, it should be OK. Using Ubuntu with 
Unity is clearly a no-go in terms of privacy.

But using TW from command line and not running behind each and every update 
may be OK for a server as well. Depends on the needs.

Cheers
Axel

___
Evergreen mailing list
Evergreen@lists.rosenauer.org
http://lists.rosenauer.org/mailman/listinfo/evergreen

Re: [Evergreen] [opensuse-buildservice] Re: Where is the 'Science' repository

[Axel Braun]

Am Freitag, 17. Juni 2016, 14:03:54 schrieb Xaver Gerster:
> sure, I appealed to the maintainers at
> https://build.opensuse.org/project/show/science
> 
> ... BUT ...
> 
> we all know how busy these guys are.
> 
> So maybe a little more help in 'convincing' them from other Evergreen
> users might really be helpful. So, anyone else on this email list here
> willing to write an additional comment on their repo page?
> That would be great! Thanks.

Maybe this helps:
ftp://ftp.gwdg.de/pub/linux/suse/opensuse/repositories/science/openSUSE_13.1/

Cheers
Axel
___
Evergreen mailing list
Evergreen@lists.rosenauer.org
http://lists.rosenauer.org/mailman/listinfo/evergreen

Re: [Evergreen] Expanded Support for OpenSuSE 13.2

[Axel Braun]

Hello Per,

> Gesendet: Montag, 11. April 2016 um 08:00 Uhr
> Von: "Per Jessen" 
> An: evergreen@lists.rosenauer.org
> Betreff: Re: [Evergreen] Expanded Support for OpenSuSE 13.2
>
> Ruediger Meier wrote:
> 
> > On Sunday 10 April 2016, Per Jessen wrote:
> >> jdd wrote:
> >> > Le 10/04/2016 14:39, reinhard hennig a écrit :
> >> >> Dear Members,
> >> >>
> >> >> will it be possible to provide an evergreen project for OpenSuSE
> >> >> 13.2? We are just about to switch to it (from OS 12.2) and would
> >> >> like to benefit from expanded LTS. We are using Linux on 12.000
> >> >> PC´s.
> >> >>
> >> >> B.R.
> >> >
> >> > if you don't have major reason to use 13.2, prefere 13.1 (present
> >> > evergreen) or Leap 42.1 (extended support probable, upgrade easy)
> >>
> >> For a production environment, I would definitely not recommend
> >> Leap421.
> > 
> > Do you have some kind of check list what are the most annoying issues
> > in 42.1 for you?
> 
> Hi Rudi
> 
> - lack of dolphin thumbnails, tooltips (pdf, libreoffice)
> - plasmashell crashes frequently
> - screen locker crashes (apparently won't be fixed until 422)
> - alt-tab windows switching is slow/unresponsive.

Hm, I use Leap every day on my workhorse (ThinkPad T520), but did not come 
around any of the issues you mentioned so far. But there are others that make 
life uneasy (e.g. multi-monitor presentations...), but no showstoppers so far.

> For a server, I might consider going with Leap421, but the steady stream
> of updates makes me a little uneasy.  Of course, it's also a good
> thing, it just seems to be a little too much. 

Many of the updates relate to KDE, so not really something you take care about 
on a test-only server

> >> I would also like to see 13.2 supported long-term, it's a very solid
> >> release.

I feel the community is in a difficult position here: The commitment is to 
support 13.1 long-term, which is, by the way, a solid release as well. On the 
other hand, 13.2 is the last 32bit release, which brings it into a special 
position.

Personally I'm happy with using 13.1 on older hardware, but under the above 
light, maybe it is worth to discuss this again?

Best regards
Axel
___
Evergreen mailing list
Evergreen@lists.rosenauer.org
http://lists.rosenauer.org/mailman/listinfo/evergreen