I installed task- sugar and dependencies, rebooted I selected it at login, but the only thing that happens is that mouse pointer change to a large arrow, on top of the (image of the) login screen. I was just curious to try it, and have not tried anything to get it to work. Not important for me but I can try something if someone want to debug.
Created attachment 7991 [details] part of output of "journalctl -ab"; log begin at user log in
CC: (none) => marja11Assignee: bugsquad => lists.jjorge
I see it got updated but still same result here on all of three tested installs on 64 bit cauldron machines where other DE work: § i7n workstation with ati proprietary driver, updated from mga5 § Centrino vPro Nvidia Quadro laptop with Nvidia driver, updated from mga5 § Centrino Duo laptop with ati GPU using xorg vesa, fresh install 6_d1+updates Is it really correct that sugar-base is version 0.98.0-7.mga6, while all other parts seem to be version 0.108.1-3.mga6 ? Is it working for most installs and I am just unlucky? If broken for most, IMO we can not ship it in mga6. I set it to release blocker to get it investigated.
Severity: major => criticalSource RPM: task-sugar 0.107.0-1.mga6 => sugar 0.108.1-3.mga6Priority: Normal => release_blocker
(In reply to Morgan Leijström from comment #2) > I see it got updated but still same result here on all of three tested > installs on 64 bit cauldron machines where other DE work: > § i7n workstation with ati proprietary driver, updated from mga5 > § Centrino vPro Nvidia Quadro laptop with Nvidia driver, updated from mga5 > § Centrino Duo laptop with ati GPU using xorg vesa, fresh install > 6_d1+updates > > Is it really correct that sugar-base is version 0.98.0-7.mga6, while all > other parts seem to be version 0.108.1-3.mga6 ? CC'ing daviddavid, who packaged it > > Is it working for most installs and I am just unlucky? > > If broken for most, IMO we can not ship it in mga6. > > I set it to release blocker to get it investigated.
Blocks: (none) => 15527CC: (none) => geiger.david68210
as this isn't in a iso media (and if it is, why ?), I don't see how it could be release blocker
(In reply to Manuel Hiebel from comment #4) > as this isn't in a iso media (and if it is, why ?), I don't see how it could > be release blocker You're right, Manuel, it's not on an iso, thanks :-)
Priority: release_blocker => Normal
Blocks: 15527 => (none)
Ah. Thanks for the correction on release blocker.
According to Bug 1969 sugar was working in mga4. I have no idea if it was working in mga5.
Hi, thanks for reporting this bug. We are sorry, but we no longer maintains this version of Mageia. Please upgrade to the latest version and reopen this bug against that version if this bug exists there. As a result we are setting this bug to RESOLVED:OLD
CC: (none) => ouaurelienResolution: (none) => OLDStatus: NEW => RESOLVED
Tried now on mga7, an install which have not had this installed before: Installed task-sugar, rebooted, at login selected Sugar; Then there are four questions each asked in centre of screen in full screen mode. It asks for name, i accepted mine. But the questions of selecting colour, sex, and age can not be answered because the big mouse cursor only works to click the next and continue buttons at left and right screen bottom. To be more precise there is not even any visible alternative to click except for the age question. So the bug may be it is unable to present click-able alternatives? A missing dep? And i can not go further because at question of age the next button is greyed. Only exit i found was to kill X; Ctrl+Alt+ twice backspace, and i find myself in login manager. Tested with login managers SDDM and GDM, same result. IMO this should finally get fixed, or dropped.
Resolution: OLD => (none)URL: (none) => http://sugarlabs.org/Status: RESOLVED => REOPENEDTarget Milestone: --- => Mageia 8Source RPM: sugar 0.108.1-3.mga6 => task-sugar-0.112-3.mga7.noarch.rpmVersion: Cauldron => 7Severity: critical => major
Hello, To be able to have the icons when launching sugar (from Plasma but after from SDDM), i had to install the package python2-gi-cairo as it is a python2 application (at least in the packaged version). In Cauldron, the version is 0.116 (is this version support python3 ?).
CC: (none) => joe_c_moi
CC: joe_c_moi => (none)
Ah, thank you Nicolas, now it works! So the depencency python2-gi-cairo should get added to task-sugar, or maybe better sugar-base Alternatively drop sugar desktop, because from this bug it seems it is not much used in Mageia...
Summary: Sugar desktop: fail logging in => Sugar desktop: missing dependencyAssignee: lists.jjorge => pkg-bugsStatus comment: (none) => See comment 10
I think we should drop it or look if upstream has released sources against Python3, not Python2, which we want to be dropped.
Yes sugar version on Cauldron seem to be 0.116-2, while task-sugar is 0.112-5 Ported to Python3 https://github.com/sugarlabs/sugar/pull/805 https://github.com/sugarlabs/sugar/issues/787 "Either it builds or gets nuked" https://ml.mageia.org/l/arc/dev/2020-09/msg00261.html
Whiteboard: (none) => MGA7TOOStatus comment: See comment 10 => Solution or drop it. see comment 10 +Source RPM: task-sugar-0.112-3.mga7.noarch.rpm => task-sugar-0.112-3.mga7.noarch task-sugar-0.112-5.mga8.noarchVersion: 7 => Cauldron
In https://ml.mageia.org/l/arc/dev/2020-09/msg00276.html Jani wrote: " Sugar was ported to python3 after mga7 was released and starts OK in Cauldron after I applied a patch from upstream. However I don't know if it's used by anyone. " With the maintainer gone (José Jorge) and not much used i suggest dropping Sugar desktop.
Will probably get dropped https://ml.mageia.org/l/arc/dev/2020-10/msg00105.html
was dropped
Resolution: (none) => FIXEDStatus: REOPENED => RESOLVED
Sugar is still in 8 and cauldron /core/release/ You mean decided to be dropped ?
(In reply to Manuel Hiebel from comment #16) > was dropped It seem to still be in Cauldron https://madb.mageia.org/package/list/t_search/sugar/release/cauldron And in repos. Is working in Cauldron/mga9 ? Not launching in mga8, another QA member report. (64 bit, launch from SDDM)
Status: RESOLVED => REOPENEDTarget Milestone: Mageia 8 => Mageia 9Whiteboard: MGA7TOO => MGA8TOOResolution: FIXED => (none)
Blocks: (none) => 30163
tried F36 Sugar on a Stick -HDD install and that seems to work, so it appears to be Mageia implementation that has an issue.
CC: (none) => westel
Sugar 0.120 is in release for Mageia 9. Do we know it works, and can close this bug?
MGA8 x86_64 Plasma Host MGA9 x86_64 Plasma VirtualBox Guest Sugar does not start. After selecting sugar in SDDM and login, the window goes completely black. Nothing happens.... Still grandiosely broken...
Keywords: (none) => FOR_ERRATA9
Summary: Sugar desktop: missing dependency => Sugar desktop: blackKeywords: FOR_ERRATA9 => IN_ERRATA9
Tried the launch, and extracted the pertinent part in journal: juin 18 19:38:59 sddm-helper[2499]: gkr-pam: unable to locate daemon control file juin 18 19:38:59 sddm-helper[2499]: gkr-pam: stashed password to try later in open session juin 18 19:38:59 systemd[1]: Started session-c2.scope. juin 18 19:38:59 kernel: ------------[ cut here ]------------ juin 18 19:38:59 kernel: refcount_t: underflow; use-after-free. juin 18 19:38:59 kernel: WARNING: CPU: 0 PID: 2457 at lib/refcount.c:28 refcount_warn_saturate+0xba/0x110 juin 18 19:38:59 kernel: Modules linked in: snd_hrtimer ip6t_REJECT nf_reject_ipv6 xt_comment ip6table_mangle ip6table_nat ip6table_raw ip6table_filter ip6_tables xt_recent ipt_IFWLOG ipt_p> juin 18 19:38:59 kernel: intel_powerclamp snd_timer rapl snd psmouse e1000 joydev i2c_piix4 soundcore vboxguest evdev input_leds sch_fq_codel msr dm_mod fuse loop configfs dmi_sysfs ip_tab> juin 18 19:38:59 kernel: CPU: 0 PID: 2457 Comm: sddm-greeter Not tainted 6.3.5-desktop-1.mga9 #1 juin 18 19:38:59 kernel: Hardware name: innotek GmbH VirtualBox/VirtualBox, BIOS VirtualBox 12/01/2006 juin 18 19:38:59 kernel: RIP: 0010:refcount_warn_saturate+0xba/0x110 juin 18 19:38:59 kernel: Code: 01 01 e8 a9 3a 9e ff 0f 0b c3 cc cc cc cc 80 3d 6a 77 31 01 00 75 85 48 c7 c7 70 07 4e b8 c6 05 5a 77 31 01 01 e8 86 3a 9e ff <0f> 0b c3 cc cc cc cc 80 3d 45 > juin 18 19:38:59 kernel: RSP: 0018:ffffa63f80ab3d40 EFLAGS: 00010286 juin 18 19:38:59 kernel: RAX: 0000000000000000 RBX: ffff9716d87fc400 RCX: 0000000000000027 juin 18 19:38:59 kernel: RDX: ffff97173dc1d648 RSI: 0000000000000001 RDI: ffff97173dc1d640 juin 18 19:38:59 kernel: RBP: ffff9716e0d63e00 R08: 0000000000000000 R09: ffffa63f80ab3be8 juin 18 19:38:59 kernel: R10: 0000000000000003 R11: ffffffffb88c2f08 R12: 0000000000000040 juin 18 19:38:59 kernel: R13: ffff9716e0d63e58 R14: ffff9716e0d63e40 R15: 0000000000000040 juin 18 19:38:59 kernel: FS: 00007fc7d7516880(0000) GS:ffff97173dc00000(0000) knlGS:0000000000000000 juin 18 19:38:59 kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 juin 18 19:38:59 kernel: CR2: 0000000001069008 CR3: 00000000137aa003 CR4: 00000000000706f0 juin 18 19:38:59 kernel: Call Trace: juin 18 19:38:59 kernel: <TASK> juin 18 19:38:59 kernel: ? refcount_warn_saturate+0xba/0x110 juin 18 19:38:59 kernel: ? __warn+0x7d/0x130 juin 18 19:38:59 kernel: ? refcount_warn_saturate+0xba/0x110 juin 18 19:38:59 kernel: ? report_bug+0x16d/0x1a0 juin 18 19:38:59 kernel: ? handle_bug+0x41/0x70 juin 18 19:38:59 kernel: ? exc_invalid_op+0x13/0x60 juin 18 19:38:59 kernel: ? asm_exc_invalid_op+0x16/0x20 juin 18 19:38:59 kernel: ? refcount_warn_saturate+0xba/0x110 juin 18 19:38:59 kernel: drm_gem_handle_delete+0x8c/0xd0 [drm] juin 18 19:38:59 kernel: ? __pfx_vmw_bo_unref_ioctl+0x10/0x10 [vmwgfx] juin 18 19:38:59 kernel: vmw_bo_unref_ioctl+0xf/0x20 [vmwgfx] juin 18 19:38:59 kernel: drm_ioctl_kernel+0xc1/0x160 [drm] juin 18 19:38:59 kernel: drm_ioctl+0x24c/0x490 [drm] juin 18 19:38:59 kernel: ? __pfx_vmw_bo_unref_ioctl+0x10/0x10 [vmwgfx] juin 18 19:38:59 kernel: ? do_vmi_munmap+0xc7/0x120 juin 18 19:38:59 kernel: ? __pfx_drm_ioctl+0x10/0x10 [drm] juin 18 19:38:59 kernel: vmw_generic_ioctl+0xab/0x140 [vmwgfx] juin 18 19:38:59 kernel: __x64_sys_ioctl+0x90/0xd0 juin 18 19:38:59 kernel: do_syscall_64+0x3a/0x90 juin 18 19:38:59 kernel: entry_SYSCALL_64_after_hwframe+0x72/0xdc juin 18 19:38:59 kernel: RIP: 0033:0x7fc7d8321e68 juin 18 19:38:59 kernel: Code: 00 00 48 8d 44 24 08 48 89 54 24 e0 48 89 44 24 c0 48 8d 44 24 d0 48 89 44 24 c8 b8 10 00 00 00 c7 44 24 b8 10 00 00 00 0f 05 <89> c2 3d 00 f0 ff ff 77 07 89 > juin 18 19:38:59 kernel: RSP: 002b:00007ffc356453f8 EFLAGS: 00000246 ORIG_RAX: 0000000000000010 juin 18 19:38:59 kernel: RAX: ffffffffffffffda RBX: 00007fc7ac70f920 RCX: 00007fc7d8321e68 juin 18 19:38:59 kernel: RDX: 00007ffc35645448 RSI: 0000000040086442 RDI: 000000000000000e juin 18 19:38:59 kernel: RBP: 00007ffc35645448 R08: 0000000000000007 R09: 00007fc7ac072d90 juin 18 19:38:59 kernel: R10: 00007ffc357e8080 R11: 0000000000000246 R12: 0000000040086442 juin 18 19:38:59 kernel: R13: 000000000000000e R14: 0000000001fac140 R15: 00007ffc35645668 juin 18 19:38:59 kernel: </TASK> juin 18 19:38:59 kernel: ---[ end trace 0000000000000000 ]--- juin 18 19:38:59 systemd-logind[675]: New session c2 of user yves. juin 18 19:38:59 sddm-helper[2499]: pam_unix(sddm:session): session opened for user yves(uid=1000) by (uid=0) juin 18 19:38:59 sddm-helper[2437]: pam_unix(sddm-greeter:session): session closed for user sddm juin 18 19:38:59 systemd-logind[675]: Session c1 logged out. Waiting for processes to exit. juin 18 19:38:59 systemd[1]: session-c1.scope: Deactivated successfully. juin 18 19:38:59 systemd[1]: session-c1.scope: Consumed 1.362s CPU time.
CC: (none) => yves.brungard_mageia
If we are to keep it -and soon really fix it! then now drop the blocking of Bug 30163 - [TRACKER] Packages that need to be obsoleted
no updates since 2021, i think we should drop it
CC: (none) => mageia
task-sugar 0.120-1 is still in cauldron.
Target Milestone: Mageia 9 => Mageia 10Blocks: 30163 => 32127
I found that sugar miss a requires: python3-decorator After added it, I can launch sugar from SDDM I have however obsoleted sugar-runner which uses still Python2, not touched since 7 years.
Nice. So we can add that require and make it work in mga9 (possibly mga8 too) :) Later we decide if to keep sugar in mga10. Can you put that fix in mga9 testing, then set this to QA? sugar-runner is a emulator for development. sugar-runner is already in mga9, i guess best is just let it be. Normal users dont use it and developers know about Python2
Source RPM: task-sugar-0.112-3.mga7.noarch task-sugar-0.112-5.mga8.noarch => task-sugar-0.120-1.mga9.noarchWhiteboard: MGA8TOO => MGA8TOO, MGA9TOO
Also, make sugar-runner not be autoselected when selecting task-sugar! And without sugar-runner maybe other packages are not needed to be required either, I guess as an example x11-server-xephyr?
Updated in cauldron Submitted in Mageia 9: sugar-cp-webaccount-0.120-2.1.mga9.noarch.rpm sugar-cp-datetime-0.120-2.1.mga9.noarch.rpm sugar-cp-background-0.120-2.1.mga9.noarch.rpm sugar-cp-power-0.120-2.1.mga9.noarch.rpm sugar-cp-frame-0.120-2.1.mga9.noarch.rpm sugar-cp-updater-0.120-2.1.mga9.noarch.rpm sugar-cp-keyboard-0.120-2.1.mga9.noarch.rpm sugar-cp-modemconfiguration-0.120-2.1.mga9.noarch.rpm sugar-cp-language-0.120-2.1.mga9.noarch.rpm sugar-cp-all-0.120-2.1.mga9.noarch.rpm sugar-cp-backup-0.120-2.1.mga9.noarch.rpm sugar-cp-network-0.120-2.1.mga9.noarch.rpm sugar-0.120-2.1.mga9.noarch.rpm Source: sugar-0.120-2.1.mga9.src.rpm Submitted Mageia 8: sugar-cp-webaccount-0.120-2.1.mga8.noarch.rpm sugar-cp-background-0.120-2.1.mga8.noarch.rpm sugar-cp-power-0.120-2.1.mga8.noarch.rpm sugar-cp-datetime-0.120-2.1.mga8.noarch.rpm sugar-cp-frame-0.120-2.1.mga8.noarch.rpm sugar-cp-updater-0.120-2.1.mga8.noarch.rpm sugar-cp-keyboard-0.120-2.1.mga8.noarch.rpm sugar-cp-modemconfiguration-0.120-2.1.mga8.noarch.rpm sugar-cp-backup-0.120-2.1.mga8.noarch.rpm sugar-cp-language-0.120-2.1.mga8.noarch.rpm sugar-cp-network-0.120-2.1.mga8.noarch.rpm sugar-cp-all-0.120-2.1.mga8.noarch.rpm sugar-0.120-2.1.mga8.noarch.rpm Source sugar-0.120-2.1.mga8.src.rpm
Whiteboard: MGA8TOO, MGA9TOO => MGA8TOOAssignee: pkg-bugs => qa-bugsStatus comment: Solution or drop it. see comment 10 + => (none)Version: Cauldron => 9
Advisory: ======== Launching the sugar desktop session wasn't possible. The new release adds a requirement of python-decorator which was missing. ======== For Mageia 8 ======== Launching the sugar desktop session wasn't possible. The new release has been updated to 0.120 and adds a requirement of python-decorator which was missing. ========
oh dear, something appears to be wrong: Sorry, the following packages cannot be selected: - sugar-0.120-2.1.mga9.noarch (due to unsatisfied typelib(Xkl)[== 1.0]) - sugar-cp-all-0.120-2.1.mga9.noarch (due to unsatisfied sugar-cp-background) - sugar-cp-background-0.120-2.1.mga9.noarch (due to unsatisfied sugar[== 0.120-2.1.mga9]) - sugar-cp-backup-0.120-2.1.mga9.noarch (due to unsatisfied sugar[== 0.120-2.1.mga9]) - sugar-cp-datetime-0.120-2.1.mga9.noarch - sugar-cp-frame-0.120-2.1.mga9.noarch (due to unsatisfied sugar[== 0.120-2.1.mga9]) - sugar-cp-keyboard-0.120-2.1.mga9.noarch (due to unsatisfied typelib(Xkl)) - sugar-cp-language-0.120-2.1.mga9.noarch (due to unsatisfied sugar[== 0.120-2.1.mga9]) - sugar-cp-modemconfiguration-0.120-2.1.mga9.noarch (due to unsatisfied sugar[== 0.120-2.1.mga9]) - sugar-cp-network-0.120-2.1.mga9.noarch (due to unsatisfied sugar[== 0.120-2.1.mga9]) - sugar-cp-power-0.120-2.1.mga9.noarch (due to unsatisfied sugar[== 0.120-2.1.mga9]) - sugar-cp-updater-0.120-2.1.mga9.noarch (due to unsatisfied sugar[== 0.120-2.1.mga9]) - sugar-cp-webaccount-0.120-2.1.mga9.noarch (due to unsatisfied sugar[== 0.120-2.1.mga9])
possibly more helpful: A requested package cannot be installed: sugar-0.120-2.1.mga9.noarch (due to unsatisfied typelib(WebKit2)[== 4.0])
mostly working. just cannot register with the sugar.org server
(In reply to Ben McMonagle from comment #32) > possibly more helpful: > > A requested package cannot be installed: > sugar-0.120-2.1.mga9.noarch (due to unsatisfied typelib(WebKit2)[== 4.0]) Yes, this is more helpful. However, I don't understand why you can't install this requires. urpmq --whatprovides "typelib(WebKit2)" lib64webkit2gtk-gir4.0|lib64webkit2gtk-gir4.1
Here mga9-64 no problem installing. Will test later.
(In reply to papoteur from comment #34) > (In reply to Ben McMonagle from comment #32) > > possibly more helpful: > > > > A requested package cannot be installed: > > sugar-0.120-2.1.mga9.noarch (due to unsatisfied typelib(WebKit2)[== 4.0]) > > Yes, this is more helpful. > However, I don't understand why you can't install this requires. > urpmq --whatprovides "typelib(WebKit2)" > lib64webkit2gtk-gir4.0|lib64webkit2gtk-gir4.1 # rpm -q --provides lib64webkit2gtk4.1_0 lib64webkit2gtk4.1_0 = 2.40.3-1.mga9 lib64webkit2gtk4.1_0(x86-64) = 2.40.3-1.mga9 libwebkit2gtk-4.1.so.0()(64bit) On a Mageia 8 install ... $ rpm -q --provides lib64webkit2gtk-gir4.0 lib64webkit2gtk-gir4.0 = 2.40.5-1.mga8 lib64webkit2gtk-gir4.0(x86-64) = 2.40.5-1.mga8 typelib(WebKit2) = 4.0 typelib(WebKit2WebExtension) = 4.0 So m8 has a version specific provides while m9 does not.
CC: (none) => davidwhodgins
@ papoteur I haven't uploaded the advisory, yet, because it is unclear to me whether the package needs to be updated for Mageia 8. See the comments above.
Keywords: (none) => feedback
OK on mga9-64 Running on: nvidia470, kernel 6.4.16-desktop-4.mga9, intel i7-870, DM:sddm It launches, and I surfed web, tested OK to draw and write, and some other stuff. Some things does not work but we can work on that later... maybe § Like Ben noted above, it fail to connect to sever when trying to register § Calculator do not launch § Programming example opens but fail to run, could not find a file § It is not adapted well to a 4K screen
Whiteboard: MGA8TOO => MGA8TOO, MGA9-64-OK
OK on mga8-64 Tested in a Plasma Guest in VirtualBox. I used QArepo to download the proposed packages, then went to MCC and installed task-sugar. That pulled in sugar, and 192 dependencies, mostly Gnome-related packages from the look of it. Strangely enough, it did not bring in any of the sugar-cp packages. I rebooted anyway, logging into sugar. I only played a little, but most seemed to work. Then I logged out and back into Plasma, and installed sugar-cp-all, which apparently drew in the rest of the cp packages. I rebooted once more, logging into sugar again, and again most seemed to work. Removing the feedback flag, and validating. Marja, go ahead with the advisory from comment 30
CC: (none) => andrewsfarm, sysadmin-bugsKeywords: feedback => validated_updateWhiteboard: MGA8TOO, MGA9-64-OK => MGA8TOO, MGA9-64-OK MGA8-64-OK
Keywords: (none) => advisory
An update for this issue has been pushed to the Mageia Updates repository. https://advisories.mageia.org/MGAA-2023-0111.html
Status: REOPENED => RESOLVEDResolution: (none) => FIXED
Errata 9 updated. Was and is not in Errata 8. ___Note for future work: We dropped the emulator for development, sugar-runner - Comment 26. Some issues to maybe have a look at - Comment 38.