Bug#872752: [Pkg-sugar-devel] Bug#872752: Following user config, nothing happens, strace exposes Heisenbug

[martin f krafft]

also sprach Jonas Smedegaard  [2017-08-20 23:00 +0200]:
> Did you file the bugreport on the system you also run Sugar?

No, and I am sorry about that. I'll augment that tonight. I have
all recommendations installed, but I also now learnt where to look
for logs, so I might well close this issue and open a new one with
all the details, for a fresh start. Sorry guys.

-- 
 .''`.   martin f. krafft  @martinkrafft
: :'  :  proud Debian developer
`. `'`   http://people.debian.org/~madduck
  `-  Debian - when you have better things to do than fixing systems
 
time wounds all heels.
 -- groucho marx


digital_signature_gpg.asc
Description: Digital GPG signature (see http://martin-krafft.net/gpg/sig-policy/999bbcc4/current)

Bug#872752: [Pkg-sugar-devel] Bug#872752: Following user config, nothing happens, strace exposes Heisenbug

[James Cameron]

Behaviour that Martin reports is expected.  There are many ways that
Sugar fails to start if any of the dependencies are missing.

The strace contains the traceback, but it is not as easy as
reading the traceback in ~/.sugar/default/logs/shell.log so please
post that next time you have a problem starting Sugar.

All I can see is that it was in homewindow.py -> meshbox.py ->
neighborhood.py, which suggests Telepathy Salut is missing, and that
correlates with Martin's "Versions of packages sugar-session
recommends" list.

As sugar-session contains tools that don't need Telepathy Salut to be
installed, I'm fine with the dependency remaining as Recommends.

On IRC Martin mentioned installing sugar-session package; my usual
recommendation is to install the sucrose package, and that's what is
maintained on the Sugar Wiki;

http://wiki.sugarlabs.org/go/Debian

-- 
James Cameron
http://quozl.netrek.org/

Bug#872752: [Pkg-sugar-devel] Bug#872752: Following user config, nothing happens, strace exposes Heisenbug

[Jonas Smedegaard]

Quoting martin f krafft (2017-08-20 21:11:08)

> Versions of packages sugar-session depends on:
> ii  dconf-gsettings-backend [gsettings-backend]  0.26.0-2+b1
> ii  gconf2   3.2.6-4+b1
> pn  gir1.2-gconf-2.0 
> ii  gir1.2-glib-2.0  1.50.0-1+b1
> ii  gir1.2-gtk-3.0   3.22.16-1
> pn  gir1.2-gudev-1.0 
> pn  gir1.2-nmgtk-1.0 
> ii  gir1.2-pango-1.0 1.40.6-1
> pn  gir1.2-upowerglib-1.0
> pn  gir1.2-xkl-1.0   
> ii  python   2.7.13-2
> ii  python-cairo 1.8.8-2.2
> ii  python-dbus  1.2.4-1+b2
> pn  python-jarabe
> pn  python-sugar3
> pn  sugar-themes 
> 
> Versions of packages sugar-session recommends:
> ii  dbus-user-session [default-dbus-session-bus]  1.10.20-1
> ii  dbus-x11 [dbus-session-bus]   1.10.20-1
> ii  ethtool   1:4.8-1+b1
> ii  fonts-dejavu-core 2.37-1
> pn  gvfs  
> ii  lsb-release   9.20161125
> pn  mobile-broadband-provider-info
> ii  modemmanager  1.6.8-1
> pn  network-manager   
> pn  sugar-browse-activity 
> pn  sugar-chat-activity   
> pn  sugar-imageviewer-activity
> pn  sugar-jukebox-activity
> pn  sugar-log-activity
> pn  sugar-pippy-activity  
> pn  sugar-read-activity   
> pn  sugar-terminal-activity   
> pn  sugar-write-activity  
> pn  telepathy-salut   
> ii  tzdata2017b-2
> ii  upower0.99.4-4+b1

Did you file the bugreport on the system you also run Sugar?

The missing version numbers even for dependencies look odd.

If you have suppressed recommendations then you have an exotic setup 
that may work only for exotic things (like selecting a color but not 
actually entering Sugar).

Please make sure that you have both dependencies and recommendations 
satisfied before testing further.


 - Jonas

-- 
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/

 [x] quote me freely  [ ] ask before reusing  [ ] keep private


signature.asc
Description: signature

Bug#872752: [Pkg-sugar-devel] Bug#872752: Following user config, nothing happens, strace exposes Heisenbug

[Jonas Smedegaard]

Quoting martin f krafft (2017-08-20 22:19:24)
> also sprach Jonas Smedegaard  [2017-08-20 21:37 +0200]:

> > Can you try remove/rename ~/.sugar and then login not via a custom 
> > .xsession shell call, but using the desktop entry (i.e. by selecting 
> > Sugar in the popup window in LightDM.  If using the default Gtk+ 
> > interface then that should be available in the top right corner. If 
> > that crashes too then there is some bug in the package - else I lean 
> > towards dismissing this as a user error (an undocumented way to 
> > start Sugar), but I can be persuaded to try dig deeper if you want 
> > to help explore it further.
> 
> The behaviour seems exactly the same if I choose "Sugar" as the 
> session to use from lightdm

Hm. A bug it is, then!


> — thanks for letting me know how to do that, I wasn't even aware of 
> the menu up top ;)

Took me some years to discover it myself :-)


 - Jonas

-- 
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/

 [x] quote me freely  [ ] ask before reusing  [ ] keep private


signature.asc
Description: signature

Bug#872752: [Pkg-sugar-devel] Bug#872752: Following user config, nothing happens, strace exposes Heisenbug

[martin f krafft]

also sprach Jonas Smedegaard  [2017-08-20 21:37 +0200]:
> Possibly there is some info in the various logfiles below ~/sugar - in 
> there should also be a config file where you can uncomment a debug flag 
> to get more verbose logs.

I'll look into this more later this week.

> Can you try remove/rename ~/.sugar and then login not via a custom
> .xsession shell call, but using the desktop entry (i.e. by
> selecting Sugar in the popup window in LightDM.  If using the
> default Gtk+ interface then that should be available in the top
> right corner. If that crashes too then there is some bug in the
> package - else I lean towards dismissing this as a user error (an
> undocumented way to start Sugar), but I can be persuaded to try
> dig deeper if you want to help explore it further.

The behaviour seems exactly the same if I choose "Sugar" as the
session to use from lightdm — thanks for letting me know how to do
that, I wasn't even aware of the menu up top ;)

-- 
 .''`.   martin f. krafft  @martinkrafft
: :'  :  proud Debian developer
`. `'`   http://people.debian.org/~madduck
  `-  Debian - when you have better things to do than fixing systems
 
if you see an onion ring -- answer it!


digital_signature_gpg.asc
Description: Digital GPG signature (see http://martin-krafft.net/gpg/sig-policy/999bbcc4/current)

Bug#872752: [Pkg-sugar-devel] Bug#872752: Following user config, nothing happens, strace exposes Heisenbug

[Jonas Smedegaard]

Quoting martin f krafft (2017-08-20 21:11:08)
> After I chose colour, gender, age, I am left with the Sugar cursor on 
> top of the same background as lightdm had, but nothing else happens.

Thanks (also for the other details, which might be useful for upstream, 
should we need to pass it on to them later).

Possibly there is some info in the various logfiles below ~/sugar - in 
there should also be a config file where you can uncomment a debug flag 
to get more verbose logs.


> I have to remove ~/.sugar to get back to the setup, after which the 
> cycle starts again: Sugar cursor and lightdm background.

Color and gender selection happens only on initial login - that is a 
feature, not a bug.  But then you were supposed to enter the Sugar 
environment, not be thrown back to the login manager, obviously.

Can you try remove/rename ~/.sugar and then login not via a custom 
.xsession shell call, but using the desktop entry (i.e. by selecting 
Sugar in the popup window in LightDM.  If using the default Gtk+ 
interface then that should be available in the top right corner. If that 
crashes too then there is some bug in the package - else I lean towards 
dismissing this as a user error (an undocumented way to start Sugar), 
but I can be persuaded to try dig deeper if you want to help explore it 
further.


 - Jonas

-- 
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/

 [x] quote me freely  [ ] ask before reusing  [ ] keep private


signature.asc
Description: signature