Dear Tumbleweed users and hackers,
What a week! Tumbleweed once again is the first (to my knowledge) to ship the just released GNOME 3.24.0 as part of its main repository. Being shipped to the users in less than 48 hours since the official release announcement is something we can only do thanks to all the automatic building and testing AND the efforts put into the packages! If packagers would not be at the ball the whole time, this would not be possible. Even though the week has seen ‘only’ 4 snapshots (0317, 0318, 0320 and 0322) the changes delivered to the user base is enormous.
The major changes this week were:
* GNOME 3.24.0 – Released on March 22nd, part of snapshot 0322 * The YaST Teams work regarding the desktop selection workflow [0] * qemu 2.8.0 * Linux kernel 4.10.4 * Mozilla Firefox 52 – NOTE: no more support for NPAPI plugins * GCC 7 is available as optional compiler (distro still built using gcc6 though) * More work to get the ‘system user’ situation changed, having special packages creating the users [1]
One important note at this point: again there were users falling into the trap with incomplete updated systems with snapshot 0322. Important: """zypper up""" is NOT the right thing to keep your Tumbleweed system running. Use """zypper dup [--no-allow-vendor-change]"""
Things currently being prepared for you
* GCC7 as default compiler – this might still take a while, but it IS coming * KDE Plasma 5.9.4 * Linux kernel 4.10.5 – and beyond * More python packages converted to singlespec
For the next three weeks, Tumbleweed will be given in the careful care of Max and Ludwig, while I will be enjoying some time off. As is usual when teams are running on lower resources, it is possible that snapshots might be delayed a little bit, but I don’t fear to much for that: you can continue submitting as you’re used to – just in case of some delays, please show some understanding. I’m sure Max and Ludwig will be there for you if you need any help. Also, in this period, I will not provide the weekly reviews. I might try to do a recap once I’m back, but no promises there.
Cheers, Dominique
[0] https://lizards.opensuse.org/2017/02/20/highlights-of-yast-developm ent-sprint-31/ [1] https://lists.opensuse.org/opensuse-packaging/2017-02/msg00022.html
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256
Il 24/03/2017 11:53, Dimstar / Dominique Leuenberger ha scritto:
Dear Tumbleweed users and hackers, > > What a week! Tumbleweed once again is the first (to my knowledge)
to > ship the just released GNOME 3.24.0 as part of its main repository.
Being shipped to the users in less than 48 hours since the official >
release announcement is something we can only do thanks to all the > automatic building and testing AND the efforts put into the packages! > If packagers would not be at the ball the whole time, this would not be
possible. Even though the week has seen ‘only’ 4 snapshots (0317,
0318, > 0320 and 0322) the changes delivered to the user base is enormous. > > The major changes this week were: > > * GNOME 3.24.0 – Released on March 22nd, part of snapshot 0322 > * The YaST Teams work regarding the desktop selection workflow [0] > * qemu 2.8.0 > * Linux kernel 4.10.4 > * Mozilla Firefox 52 – NOTE: no more support for NPAPI plugins > * GCC 7 is available as optional compiler (distro still built using > gcc6 though) > * More work to get the ‘system user’ situation changed, having > special packages creating the users [1] > > One important note at this point: again there were users falling into > the trap with incomplete updated systems with snapshot 0322. > Important: """zypper up""" is NOT the right thing to keep your > Tumbleweed system running. > Use """zypper dup [--no-allow-vendor-change]""" > > Things currently being prepared for you > > * GCC7 as default compiler – this might still take a while, but it IS > coming > * KDE Plasma 5.9.4 > * Linux kernel 4.10.5 – and beyond > * More python packages converted to singlespec > > For the next three weeks, Tumbleweed will be given in the careful care > of Max and Ludwig, while I will be enjoying some time off. As is usual > when teams are running on lower resources, it is possible that > snapshots might be delayed a little bit, but I don’t fear to much for > that: you can continue submitting as you’re used to – just in case of > some delays, please show some understanding. I’m sure Max and Ludwig > will be there for you if you need any help. Also, in this period, I > will not provide the weekly reviews. I might try to do a recap once I’m
back, but no promises there. > > Cheers, > Dominique > > [0]
https://lizards.opensuse.org/2017/02/20/highlights-of-yast-developm > ent-sprint-31/ > [1] https://lists.opensuse.org/opensuse-packaging/2017-02/msg00022.html > > As updated to latest TW 0322, I cannot start anymore my system into graphical mode as before, I had to modify /etc/sysconfig/displaymanager by replacing *"gdm"* with *"kdm"* and to change also /etc/sysconfig/windowmanager, replacing previous setting "gnome" to *"xfce"*.
Not a so terrific task, but I would like to report this occurrence here, in case other users being facing same issues.
Cheers,
- -- Marco Calistri Opensuse Tumbleweed 64 bit Intel® Core™ i5-2410M CPU @ 2.30GHz × 4 Intel® Sandybridge Mobile
N�����r��y隊Z)z{.���r�+�맲��r��z�^�ˬz��N�(�֜��^� ޭ隊Z)z{.���r�+��0�����Ǩ�
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 03/25/17 11:53, Marco Calistri wrote:
As updated to latest TW 0322, I cannot start anymore my system into graphical mode as before, I had to modify /etc/sysconfig/displaymanager by replacing *"gdm"* with *"kdm"* and to change also /etc/sysconfig/windowmanager, replacing previous setting "gnome" to *"xfce"*.
- From here, it looks as if "gdm" is okay. But Gnome 3.24 is badly broken .
Using "gdm", I login to KDE. And all is fine.
I login to Gnome (should be using Wayland), and I run into problems:
Problems 1: I cannot run Yast. I can "su" in terminal and get a root session. And "$DISPLAY" looks ok, "$XAUTHORITY" looks okay. But "yast2" says that it cannot connect to the display. Similarly, "xterm" (from the root session) says that it cannot connect to the display. But "xterm" from the user session is fine.
Then I logout. And I cannot login to KDE or Gnome again. I can login to Icewm.
I can login to a different user. With that different user, I run ps -fu original-user
and it looks as if the original user's login session is still running. The logout from Gnome did not terminate the user processes.
Reboot. Then I login to Gnome-Xorg. And that seems to work. I logout, and then login as a different user. Once again, it looks as if the original user Gnome login session is still mostly running. Even on Xorg, a Gnome logout is not properly terminating the session.
As the original user, I can now login to KDE. But a whole bunch of Gnome processes are still running.
I tried switching to "sddm" (and rebooting). If I login to a Gnome/Wayland session with "sddm", then logout, I run into all of the same problems.
I can file a bug report if needed. However, I am mainly a KDE user, so perhaps it would be better for this to be reported by a Gnome user.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256
Il 25/03/2017 16:54, Neil Rickert ha scritto:
On 03/25/17 11:53, Marco Calistri wrote:
As updated to latest TW 0322, I cannot start anymore my system into graphical mode as before, I had to modify /etc/sysconfig/displaymanager by replacing *"gdm"* with *"kdm"* and to change also /etc/sysconfig/windowmanager, replacing previous setting "gnome" to *"xfce"*.
- From here, it looks as if "gdm" is okay. But Gnome 3.24 is badly
broken .
Using "gdm", I login to KDE. And all is fine.
I've neither tested to change just windowmanager settings, may be it could works for me too, I wish just to inform my experience regarding failure of graphic login.
I login to Gnome (should be using Wayland), and I run into problems:
Problems 1: I cannot run Yast. I can "su" in terminal and get a root session. And "$DISPLAY" looks ok, "$XAUTHORITY" looks okay. But "yast2" says that it cannot connect to the display. Similarly, "xterm" (from the root session) says that it cannot connect to the display. But "xterm" from the user session is fine.
Then I logout. And I cannot login to KDE or Gnome again. I can login to Icewm.
I can login to a different user. With that different user, I run ps -fu original-user
and it looks as if the original user's login session is still running. The logout from Gnome did not terminate the user processes.
Reboot. Then I login to Gnome-Xorg. And that seems to work. I logout, and then login as a different user. Once again, it looks as if the original user Gnome login session is still mostly running. Even on Xorg, a Gnome logout is not properly terminating the session.
As the original user, I can now login to KDE. But a whole bunch of Gnome processes are still running.
I tried switching to "sddm" (and rebooting). If I login to a Gnome/Wayland session with "sddm", then logout, I run into all of the same problems.
I can file a bug report if needed. However, I am mainly a KDE user, so perhaps it would be better for this to be reported by a Gnome user.
I've also seen an error related to gnome keyring but I've not saved it. Cheers, - -- Marco Calistri Opensuse Tumbleweed 64 bit Intel® Core™ i5-2410M CPU @ 2.30GHz × 4 Intel® Sandybridge Mobile
N�����r��y隊Z)z{.���r�+�맲��r��z�^�ˬz��N�(�֜��^� ޭ隊Z)z{.���r�+��0�����Ǩ�
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 03/25/17 15:10, Marco Calistri wrote:
Il 25/03/2017 16:54, Neil Rickert ha scritto:
I've neither tested to change just windowmanager settings, may be it could works for me too, I wish just to inform my experience regarding failure of graphic login.
I need to clarify my earlier reply. I'll do that below.
I've also seen an error related to gnome keyring but I've not saved it. Cheers,
If you have switched to "kdm", then the gnome keyring is not automatically opened during login.
Anyway, my clarifications.
Most of what I previously described was on a Tumbleweed system first installed over a year ago (and updated). I've since tried on a couple of Tumbleweeds more recently installed (October 2016 and March 2017).
With the more newly installed systems, Gnome seems to only startup under Xorg. It does not seem to start a Wayland session. And the problems with login seem to only be in a Wayland session, so I am not seeing those on the more newly installed systems. If you are using "kdm" now, then that won't give a Wayland session anyway, which is probably why that works for you.
The problem with logout leaving lots of running Gnome processes still happens with Xorg. But it does not prevent another login.
Le samedi 25 mars 2017 à 14:54 -0500, Neil Rickert a écrit :
On 03/25/17 11:53, Marco Calistri wrote:
As updated to latest TW 0322, I cannot start anymore my system into graphical mode as before, I had to modify /etc/sysconfig/displaymanager by replacing *"gdm"* with *"kdm"* and to change also /etc/sysconfig/windowmanager, replacing previous setting "gnome" to *"xfce"*.
From here, it looks as if "gdm" is okay. But Gnome 3.24 is badly broken .
Using "gdm", I login to KDE. And all is fine.
I login to Gnome (should be using Wayland), and I run into problems:
Problems 1: I cannot run Yast. I can "su" in terminal and get a root session. And "$DISPLAY" looks ok, "$XAUTHORITY" looks okay. But "yast2" says that it cannot connect to the display. Similarly, "xterm" (from the root session) says that it cannot connect to the display. But "xterm" from the user session is fine.
run xhost +SI:localuser:root
It will allow root applications to connect to XWayland for the current session.
On 03/27/17 02:48, Frederic Crozat wrote:
run xhost +SI:localuser:root
It will allow root applications to connect to XWayland for the current session.
Thanks. That solved the problem of being able to run Yast.
Is there any documentation -- preferably a man page -- on this. The "xhost" man page mentions "si" but without any details.
I still have a problem, that logout from the Wayland Gnome session leaves many running processes. And these seem to interfere with login to a KDE session by the same user. (Manually killing the processes does solve the problem).
And I still have the problem that Gnome is not running under Wayland in a more recent install of Tumbleweed. It cannot be a graphic display problem, because it is on the same computer (different partition) as the one that does give Wayland sessions.
On Mon, 27 Mar 2017 18:58, Neil Rickert wrote:
On 03/27/17 02:48, Frederic Crozat wrote:
run xhost +SI:localuser:root
It will allow root applications to connect to XWayland for the current session.
Thanks. That solved the problem of being able to run Yast.
Is there any documentation -- preferably a man page -- on this. The "xhost" man page mentions "si" but without any details.
I still have a problem, that logout from the Wayland Gnome session leaves many running processes. And these seem to interfere with login to a KDE session by the same user. (Manually killing the processes does solve the problem).
And I still have the problem that Gnome is not running under Wayland in a more recent install of Tumbleweed. It cannot be a graphic display problem, because it is on the same computer (different partition) as the one that does give Wayland sessions.
1. Google/etc "xhost si:localuser" 2. From a leap 42.1 system: "man 1 xhost" (part of xhost package) excerpt:
The local family specifies all the local connections at once. How- ever, the server interpreted address "si:localuser:[username]" can be used to specify a single local user. (See the Xsecurity(7) manual page for more details.)
"man 7 Xsecurity" (part of xorg-docs package) online: https://www.x.org/archive/X11R6.8.1/doc/Xsecurity.7.html https://linux.die.net/man/7/xsecurity
excerpt: Server Interpreted The Server Interpreted method provides two strings to the X server for entry in the access control list. The first string represents the type of entry, and the second string contains the value of the entry. These strings are interpreted by the server and different implementations and builds may support different types of entries. The types supported in the sample implementation are defined in the SERVER INTERPRETED ACCESS TYPES section below. Entries of this type can be manipulated via xhost. For example to add a Server Interpreted entry of type localuser with a value of root, the command is xhost +si:localuser:root.
- Yamaban
Le samedi 25 mars 2017 à 16:53 +0000, Marco Calistri a écrit :
Il 24/03/2017 11:53, Dimstar / Dominique Leuenberger ha scritto:
Dear Tumbleweed users and hackers, > > What a week! Tumbleweed once again is the first (to my knowledge)
to > ship the just released GNOME 3.24.0 as part of its main repository.
Being shipped to the users in less than 48 hours since the official
release announcement is something we can only do thanks to all the > automatic building and testing AND the efforts put into the packages!
If packagers would not be at the ball the whole time, this would not be
possible. Even though the week has seen ‘only’ 4 snapshots (0317,
0318, > 0320 and 0322) the changes delivered to the user base is enormous. > > The major changes this week were: > > * GNOME 3.24.0 – Released on March 22nd, part of snapshot 0322 > * The YaST Teams work regarding the desktop selection workflow [0] > * qemu 2.8.0 > * Linux kernel 4.10.4 > * Mozilla Firefox 52 – NOTE: no more support for NPAPI plugins > * GCC 7 is available as optional compiler (distro still built using > gcc6 though) > * More work to get the ‘system user’ situation changed, having > special packages creating the users [1] > > One important note at this point: again there were users falling into > the trap with incomplete updated systems with snapshot 0322. > Important: """zypper up""" is NOT the right thing to keep your > Tumbleweed system running. > Use """zypper dup [--no-allow-vendor-change]""" > > Things currently being prepared for you > > * GCC7 as default compiler – this might still take a while, but it IS > coming > * KDE Plasma 5.9.4 > * Linux kernel 4.10.5 – and beyond > * More python packages converted to singlespec > > For the next three weeks, Tumbleweed will be given in the careful care > of Max and Ludwig, while I will be enjoying some time off. As is usual > when teams are running on lower resources, it is possible that > snapshots might be delayed a little bit, but I don’t fear to much for
that: you can continue submitting as you’re used to – just in case of
some delays, please show some understanding. I’m sure Max and Ludwig
will be there for you if you need any help. Also, in this period, I > will not provide the weekly reviews. I might try to do a recap once I’m
back, but no promises there. > > Cheers, > Dominique > > [0]
https://lizards.opensuse.org/2017/02/20/highlights-of-yast-developm > ent-sprint-31/ > [1] https://lists.opensuse.org/opensuse-packaging/2017-02/msg00022.html >
As updated to latest TW 0322, I cannot start anymore my system into graphical mode as before, I had to modify /etc/sysconfig/displaymanager by replacing *"gdm"* with *"kdm"* and to change also /etc/sysconfig/windowmanager, replacing previous setting "gnome" to *"xfce"*.
Try running zypper dup, the upgrade to GNOME 3.24 requires it (as most TW upgrade should be done).
Il 27/03/2017 04:47, Frederic Crozat ha scritto:
Le samedi 25 mars 2017 à 16:53 +0000, Marco Calistri a écrit :
As updated to latest TW 0322, I cannot start anymore my system into graphical mode as before, I had to modify /etc/sysconfig/displaymanager by replacing *"gdm"* with *"kdm"* and to change also /etc/sysconfig/windowmanager, replacing previous setting "gnome" to *"xfce"*.
Try running zypper dup, the upgrade to GNOME 3.24 requires it (as most TW upgrade should be done).
Thanks for your feedback Frederic, Since my system uses also not standard repos, I would avoid to run zypper dup.
Is there another "more conservative" way to install just the Gnome 3.24 packages and its related dependecies without have to lead with a plenty of zypper warnings I would face by running an overall distibution upgrade?
Mni Tks,
Marco Calistri <amdturion> Being superstitious brings bad luck. N�����r��y隊Z)z{.���r�+�맲��r��z�^�ˬz��N�(�֜��^� ޭ隊Z)z{.���r�+��0�����Ǩ�
Le lundi 27 mars 2017 à 15:33 +0000, Marco Calistri a écrit :
Il 27/03/2017 04:47, Frederic Crozat ha scritto:
Le samedi 25 mars 2017 à 16:53 +0000, Marco Calistri a écrit :
As updated to latest TW 0322, I cannot start anymore my system into graphical mode as before, I had to modify /etc/sysconfig/displaymanager by replacing *"gdm"* with *"kdm"* and to change also /etc/sysconfig/windowmanager, replacing previous setting "gnome" to *"xfce"*.
Try running zypper dup, the upgrade to GNOME 3.24 requires it (as most TW upgrade should be done).
Thanks for your feedback Frederic, Since my system uses also not standard repos, I would avoid to run zypper dup.
Is there another "more conservative" way to install just the Gnome 3.24 packages and its related dependecies without have to lead with a plenty of zypper warnings I would face by running an overall distibution upgrade?
zypper dup --no-allow-vendor-change
should do it
Il 27/03/2017 12:42, Frederic Crozat ha scritto:
Le lundi 27 mars 2017 à 15:33 +0000, Marco Calistri a écrit :
Il 27/03/2017 04:47, Frederic Crozat ha scritto:
Le samedi 25 mars 2017 à 16:53 +0000, Marco Calistri a écrit :
As updated to latest TW 0322, I cannot start anymore my system into graphical mode as before, I had to modify /etc/sysconfig/displaymanager by replacing *"gdm"* with *"kdm"* and to change also /etc/sysconfig/windowmanager, replacing previous setting "gnome" to *"xfce"*.
Try running zypper dup, the upgrade to GNOME 3.24 requires it (as most TW upgrade should be done).
Thanks for your feedback Frederic, Since my system uses also not standard repos, I would avoid to run zypper dup.
Is there another "more conservative" way to install just the Gnome 3.24 packages and its related dependecies without have to lead with a plenty of zypper warnings I would face by running an overall distibution upgrade?
zypper dup --no-allow-vendor-change
should do it
Hi Frederic,
For me that procedure (zypper dup) has not succeded I'm relying on XFCE and/or KDE.
Both GNOME and Cinnamon (which I was using as my default DE) fails to start (also Gnome Classic or Cinnamon into low resolution mode). Is there a specific log I can watch to discover eventual gdm problem?
Cheers,
Le jeudi 30 mars 2017 à 12:49 +0000, Marco Calistri a écrit :
Il 27/03/2017 12:42, Frederic Crozat ha scritto:
Le lundi 27 mars 2017 à 15:33 +0000, Marco Calistri a écrit :
Il 27/03/2017 04:47, Frederic Crozat ha scritto:
Le samedi 25 mars 2017 à 16:53 +0000, Marco Calistri a écrit :
As updated to latest TW 0322, I cannot start anymore my system into graphical mode as before, I had to modify /etc/sysconfig/displaymanager by replacing *"gdm"* with *"kdm"* and to change also /etc/sysconfig/windowmanager, replacing previous setting "gnome" to *"xfce"*.
Try running zypper dup, the upgrade to GNOME 3.24 requires it (as most TW upgrade should be done).
Thanks for your feedback Frederic, Since my system uses also not standard repos, I would avoid to run zypper dup.
Is there another "more conservative" way to install just the Gnome 3.24 packages and its related dependecies without have to lead with a plenty of zypper warnings I would face by running an overall distibution upgrade?
zypper dup --no-allow-vendor-change
should do it
Hi Frederic,
For me that procedure (zypper dup) has not succeded I'm relying on XFCE and/or KDE.
Both GNOME and Cinnamon (which I was using as my default DE) fails to start (also Gnome Classic or Cinnamon into low resolution mode). Is there a specific log I can watch to discover eventual gdm problem?
Check journalctl -b or /var/lib/gdm/.cache/gdm/
Il 30/03/2017 09:56, Frederic Crozat ha scritto:
Le jeudi 30 mars 2017 à 12:49 +0000, Marco Calistri a écrit :
Il 27/03/2017 12:42, Frederic Crozat ha scritto:
Le lundi 27 mars 2017 à 15:33 +0000, Marco Calistri a écrit :
Il 27/03/2017 04:47, Frederic Crozat ha scritto:
Le samedi 25 mars 2017 à 16:53 +0000, Marco Calistri a écrit :
As updated to latest TW 0322, I cannot start anymore my system into graphical mode as before, I had to modify /etc/sysconfig/displaymanager by replacing *"gdm"* with *"kdm"* and to change also /etc/sysconfig/windowmanager, replacing previous setting "gnome" to *"xfce"*.
Try running zypper dup, the upgrade to GNOME 3.24 requires it (as most TW upgrade should be done).
Thanks for your feedback Frederic, Since my system uses also not standard repos, I would avoid to run zypper dup.
Is there another "more conservative" way to install just the Gnome 3.24 packages and its related dependecies without have to lead with a plenty of zypper warnings I would face by running an overall distibution upgrade?
zypper dup --no-allow-vendor-change
should do it
Hi Frederic,
For me that procedure (zypper dup) has not succeded I'm relying on XFCE and/or KDE.
Both GNOME and Cinnamon (which I was using as my default DE) fails to start (also Gnome Classic or Cinnamon into low resolution mode). Is there a specific log I can watch to discover eventual gdm problem?
Check journalctl -b or /var/lib/gdm/.cache/gdm/
Found some interesting points by journalctl:
---------------------------------------------- marco@linux-turion64:~> sudo journalctl -b|grep gnome|more [sudo] password di root: mar 30 15:02:57 linux-turion64.ddns.net gnome-session[1686]: gnome-session-binary[1686]: WARNING: Could not parse desktop file powerdevil.desktop or it references a not found TryExec binary mar 30 15:02:57 linux-turion64.ddns.net gnome-session[1686]: gnome-session-binary[1686]: WARNING: Could not parse desktop file baloo_file.desktop or it references a not found TryExec binary mar 30 15:02:57 linux-turion64.ddns.net gnome-keyring-secrets.desktop[1992]: gnome-keyring-daemon: insufficient process capabilities, unsecure memory might get used mar 30 15:02:57 linux-turion64.ddns.net gnome-keyring pkcs11.desktop[1991]: gnome-keyring-daemon: insufficient process capabilities, unsecure memory might get used mar 30 15:02:57 linux-turion64.ddns.net gnome-keyring-ssh.desktop[1989]: gnome-keyring-daemon: insufficient process capabilities, unsecure memory might get used mar 30 15:02:57 linux-turion64.ddns.net gnome-keyring-daemon[1995]: couldn't access control socket: /run/user/1000/keyring/control: File o directory non esistente
mar 30 15:03:01 linux-turion64.ddns.net dbus-daemon[1707]: Activating service name='org.gnome.GConf' mar 30 15:03:01 linux-turion64.ddns.net dbus-daemon[1707]: Successfully activated service 'org.gnome.GConf' mar 30 15:03:02 linux-turion64.ddns.net gnome-shell[2003]: Theme parsing error: gtk.css:68:35: The style property GtkButton:child-displacement-x is deprecated and shouldn't be used anymore. It will be removed in a future version mar 30 15:03:02 linux-turion64.ddns.net gnome-shell[2003]: Theme parsing error: gtk.css:69:35: The style property GtkButton:child-displacement-y is deprecated and shouldn't be used anymore. It will be removed in a future version
mar 30 15:03:28 linux-turion64.ddns.net gnome-shell[2003]: GNOME Shell started at Thu Mar 30 2017 15:03:20 GMT-0300 mar 30 15:03:29 linux-turion64.ddns.net dbus-daemon[1707]: Activating via systemd: service name='org.gnome.zeitgeist.SimpleIndexer' unit='zeitgeist-fts.service' mar 30 15:03:29 linux-turion64.ddns.net dbus-daemon[1707]: Successfully activated service 'org.gnome.zeitgeist.Engine' mar 30 15:03:30 linux-turion64.ddns.net zeitgeist-daemon[2348]: [18:03:30.517345 CRITICAL] file ext-fts.c: line 748: unexpected error: Errore nel chiamare StartServiceBy Name per org.gnome.zeitgeist.SimpleIndexer: GDBus.Error:org.freedesktop.DBus.Error.InvalidArgs: Unit zeitgeist-fts.service is not loaded properly: Invalid argument. (g-d bus-error-quark, 16) mar 30 15:03:30 linux-turion64.ddns.net zeitgeist-datah[2441]: zeitgeist-datahub.vala:224: Unable to get name "org.gnome.zeitgeist.datahub" on the bus! mar 30 15:03:35 linux-turion64.ddns.net gnome-software-service.desktop[2341]: 18:03:35:0158 Gs Failed to create permission org.freedesktop.Flatpak.appstream-update: GDB us.Error:org.freedesktop.PolicyKit1.Error.Failed: Action org.freedesktop.Flatpak.appstream-update is not registered ---------------------------------------------- As you can see a lot of "mess" I tried to force the reinstall of some packages withouts success but as soon I restarted the Login I have been able to see Gnome Desktop for a while then it crashed again :-(
Thanks and regards,
Le jeudi 30 mars 2017 à 18:30 +0000, Marco Calistri a écrit :
Il 30/03/2017 09:56, Frederic Crozat ha scritto:
Le jeudi 30 mars 2017 à 12:49 +0000, Marco Calistri a écrit :
Il 27/03/2017 12:42, Frederic Crozat ha scritto:
Le lundi 27 mars 2017 à 15:33 +0000, Marco Calistri a écrit :
Il 27/03/2017 04:47, Frederic Crozat ha scritto:
Le samedi 25 mars 2017 à 16:53 +0000, Marco Calistri a écrit : > > > >
> > > > As updated to latest TW 0322, I cannot start anymore my > system > into graphical mode as before, I had to modify > /etc/sysconfig/displaymanager by replacing *"gdm"* with > *"kdm"* > and > to change also /etc/sysconfig/windowmanager, replacing > previous > setting "gnome" to *"xfce"*.
Try running zypper dup, the upgrade to GNOME 3.24 requires it (as most TW upgrade should be done).
Thanks for your feedback Frederic, Since my system uses also not standard repos, I would avoid to run zypper dup.
Is there another "more conservative" way to install just the Gnome 3.24 packages and its related dependecies without have to lead with a plenty of zypper warnings I would face by running an overall distibution upgrade?
zypper dup --no-allow-vendor-change
should do it
Hi Frederic,
For me that procedure (zypper dup) has not succeded I'm relying on XFCE and/or KDE.
Both GNOME and Cinnamon (which I was using as my default DE) fails to start (also Gnome Classic or Cinnamon into low resolution mode). Is there a specific log I can watch to discover eventual gdm problem?
Check journalctl -b or /var/lib/gdm/.cache/gdm/
Found some interesting points by journalctl:
marco@linux-turion64:~> sudo journalctl -b|grep gnome|more
Don't grep on gnome, you are probably hiding relevant message.
I would suggest to discuss the issue on #opensuse-gnome on IRC.
Il 31/03/2017 04:55, Frederic Crozat ha scritto:
Le jeudi 30 mars 2017 à 18:30 +0000, Marco Calistri a écrit :
Il 30/03/2017 09:56, Frederic Crozat ha scritto:
Le jeudi 30 mars 2017 à 12:49 +0000, Marco Calistri a écrit :
Il 27/03/2017 12:42, Frederic Crozat ha scritto:
Le lundi 27 mars 2017 à 15:33 +0000, Marco Calistri a écrit :
Il 27/03/2017 04:47, Frederic Crozat ha scritto: > > > > Le samedi 25 mars 2017 à 16:53 +0000, Marco Calistri a > écrit : >> >> >> >>
> > > >> >> >> >> As updated to latest TW 0322, I cannot start anymore my >> system >> into graphical mode as before, I had to modify >> /etc/sysconfig/displaymanager by replacing *"gdm"* with >> *"kdm"* >> and >> to change also /etc/sysconfig/windowmanager, replacing >> previous >> setting "gnome" to *"xfce"*. > > Try running zypper dup, the upgrade to GNOME 3.24 requires > it > (as > most TW upgrade should be done). >
Thanks for your feedback Frederic, Since my system uses also not standard repos, I would avoid to run zypper dup.
Is there another "more conservative" way to install just the Gnome 3.24 packages and its related dependecies without have to lead with a plenty of zypper warnings I would face by running an overall distibution upgrade?
zypper dup --no-allow-vendor-change
should do it
Hi Frederic,
For me that procedure (zypper dup) has not succeded I'm relying on XFCE and/or KDE.
Both GNOME and Cinnamon (which I was using as my default DE) fails to start (also Gnome Classic or Cinnamon into low resolution mode). Is there a specific log I can watch to discover eventual gdm problem?
Check journalctl -b or /var/lib/gdm/.cache/gdm/
Found some interesting points by journalctl:
marco@linux-turion64:~> sudo journalctl -b|grep gnome|more
Don't grep on gnome, you are probably hiding relevant message.
I would suggest to discuss the issue on #opensuse-gnome on IRC.
Ok, thanks for your time Frederic. Regards,
Il 31/03/2017 04:55, Frederic Crozat ha scritto:
Le jeudi 30 mars 2017 à 18:30 +0000, Marco Calistri a écrit :
SUPER CUT...
Don't grep on gnome, you are probably hiding relevant message.
I would suggest to discuss the issue on #opensuse-gnome on IRC.
I've been able to isolate the issue, it was located into my ~/.config/autostart folder, on particular the SpiderOakOne desktop launcher which was causing Gnome to crash and back me to login greeter.
BTW I also noticed that Gnome crash in the same way if I try to use Tweak-Tool Autostart Application, as soon as I click on the "+" button.
I tried to acces IRC Net without success.
Regards,
Il 08/04/2017 16:07, Marco Calistri ha scritto:
Il 31/03/2017 04:55, Frederic Crozat ha scritto:
Le jeudi 30 mars 2017 à 18:30 +0000, Marco Calistri a écrit :
SUPER CUT...
Don't grep on gnome, you are probably hiding relevant message.
I would suggest to discuss the issue on #opensuse-gnome on IRC.
I've been able to isolate the issue, it was located into my ~/.config/autostart folder, on particular the SpiderOakOne desktop launcher which was causing Gnome to crash and back me to login greeter.
BTW I also noticed that Gnome crash in the same way if I try to use Tweak-Tool Autostart Application, as soon as I click on the "+" button.
I tried to acces IRC Net without success.
Regards,
Filled the bug Bug #1033216
https://bugzilla.opensuse.org/show_bug.cgi?id=1033216
Il 10/04/2017 08:27, Marco Calistri ha scritto:
Il 08/04/2017 16:07, Marco Calistri ha scritto:
Il 31/03/2017 04:55, Frederic Crozat ha scritto:
Le jeudi 30 mars 2017 à 18:30 +0000, Marco Calistri a écrit :
SUPER CUT...
Don't grep on gnome, you are probably hiding relevant message.
I would suggest to discuss the issue on #opensuse-gnome on IRC.
I've been able to isolate the issue, it was located into my ~/.config/autostart folder, on particular the SpiderOakOne desktop launcher which was causing Gnome to crash and back me to login greeter.
BTW I also noticed that Gnome crash in the same way if I try to use Tweak-Tool Autostart Application, as soon as I click on the "+" button.
I tried to acces IRC Net without success.
Regards,
Filled the bug Bug #1033216
...So far nobody from Bugzilla replied or commented anything at the issue above I opened on April 10th.
Side note: The problem is still present after the late snapshot.
Then it is hard to listen to the "standard academic recommendation":
"Please be so kind to open a bug-report"... :-/
Cheers,
Marco Calistri <amdturion> Being superstitious brings bad luck. N�����r��y隊Z)z{.���r�+�맲��r��z�^�ˬz��N�(�֜��^� ޭ隊Z)z{.���r�+��0�����Ǩ�
Hello,
Am Donnerstag, 20. April 2017, 19:33:04 CEST schrieb Marco Calistri:
Il 10/04/2017 08:27, Marco Calistri ha scritto:
Filled the bug Bug #1033216
...So far nobody from Bugzilla replied or commented anything at the issue above I opened on April 10th.
Side note: The problem is still present after the late snapshot.
Then it is hard to listen to the "standard academic recommendation":
"Please be so kind to open a bug-report"... :-/
I'm quite sure the "standard academic recommendation" did not include a guarantee that bugs get handled (or even fixed) within 10 days ;-) - especially if these 10 days include the easter weekend and lots of people take some days off.
To quote an old joke from the german mailinglist: If you aren't satisfied, you can ask to get your money back ;-))
On a more serious note: Lots of bugs get fixed [1], but it might take some time.
BTW: We have enough bugs for everybody ;-) So if someone has some time, help is more than welcome. You don't need to be a developer - one way to help is to check if things in old bugreports are still reproducable in the latest version. Closing a bug as "fixed in the meantime" means the developers can focus on the still-existing bugs ;-)
Regards,
Christian Boltz
[1] Last time I checked, more than 50% of all bugreports were marked as FIXED, so there are good chances to get things fixed. The other bugs have a mix of the other resolutions - duplicates, invalid, wontfix, and even a (not-so-)nice amount of "noresponse" where the bugreporter didn't answer questions.
Il 22/04/2017 08:13, Christian Boltz ha scritto:
Hello,
Am Donnerstag, 20. April 2017, 19:33:04 CEST schrieb Marco Calistri:
Il 10/04/2017 08:27, Marco Calistri ha scritto:
Filled the bug Bug #1033216
...So far nobody from Bugzilla replied or commented anything at the issue above I opened on April 10th.
Side note: The problem is still present after the late snapshot.
Then it is hard to listen to the "standard academic recommendation":
"Please be so kind to open a bug-report"... :-/
I'm quite sure the "standard academic recommendation" did not include a guarantee that bugs get handled (or even fixed) within 10 days ;-) - especially if these 10 days include the easter weekend and lots of people take some days off.
True, also my professional job is as technical support for a telecom company then I know perfectly what you mean.
To quote an old joke from the german mailinglist: If you aren't satisfied, you can ask to get your money back ;-))
In this case since I spent zero for OpenSUSE, how much money I will get back :-)
On a more serious note: Lots of bugs get fixed [1], but it might take some time.
BTW: We have enough bugs for everybody ;-) So if someone has some time, help is more than welcome. You don't need to be a developer - one way to help is to check if things in old bugreports are still reproducable in the latest version. Closing a bug as "fixed in the meantime" means the developers can focus on the still-existing bugs ;-)
Regards,
Christian Boltz
[1] Last time I checked, more than 50% of all bugreports were marked as FIXED, so there are good chances to get things fixed. The other bugs have a mix of the other resolutions - duplicates, invalid, wontfix, and even a (not-so-)nice amount of "noresponse" where the bugreporter didn't answer questions.
I will placidly keep waiting for the issue being resolved, in the meanwhile I will use other DE don't worry!
Regards,
-
Christian Boltz -
Dimstar / Dominique Leuenberger -
Frederic Crozat -
Marco Calistri -
Neil Rickert -
Yamaban