[opensuse-gnome] [important] GNOME shipstoppers for 11.2
Hi, Please read this mail carefully -- if you think you can't help, you're wrong because you can definitely help, even if you don't know how to package/code and even if you don't have a free machine to test factory. I'll talk about what I think are our current shipstoppers, and then how people can help. Oh, and it'd be nice to avoid turning this thread into a "please fix this specific bug" unless the bug in question is really major ;-) Current shipstoppers ==================== This is my current list of GNOME shipstoppers. Note that this is different from the official list of shipstoppers (decided by coolo), and so it could be seen as a list of "Vincent really wants this to be fixed for 11.2" bugs. Also note that some majors issues are already fixed in G:F but the fixes are not yet available (waiting for the build service to publish them, but you can download them via the build service web interface). One such issue is a bad crash in many gtk+ apps -- if you experience this, you probably want the gtk2 package in G:F. GNOME live system wants empty root password https://bugzilla.novell.com/show_bug.cgi?id=537343 This is currently NEEDINFO, if someone can provide the requested information, that would help a lot. Restart fails to restart computer https://bugzilla.novell.com/show_bug.cgi?id=540482 I would think the gdm package that is waiting to be built/published in G:F fixes at least part of this. Testing welcome. More investigation might be needed: clicking on "Restart" in GDM takes a bit too long before something happens. Could be a ConsoleKit issue. after suspend via lid close the system resumes and then suspends again https://bugzilla.novell.com/show_bug.cgi?id=540517 The issue is identified, and I've pushed the bug upstream for discussion. I tried a first fix that doesn't work, but I have an idea of another workaround that should be easy to implement. no gnome taskbar after install https://bugzilla.novell.com/show_bug.cgi?id=543876 The panel crashes on start. I have *no idea* why this happens. I've requested some information (in this bug, and in an upstream bug which is linked from there too). If you can reproduce the issue, please please get in touch with me so that we can debug it. Just launching the panel in gdb would help. sonar: gdm panel contains GtkComboBox that are unreadable https://bugzilla.novell.com/show_bug.cgi?id=544079 This happens with the latest sonar version. I tried to fix this but I'm obviously not good enough with gtk+ theming. If someone can fix it before Jakub, then please do it. Open with install Software cannot be used. https://bugzilla.novell.com/show_bug.cgi?id=543595 Looks like some gnome-packagekit issue. 'Preferred Applications' appears twice in gnome control center https://bugzilla.novell.com/show_bug.cgi?id=533491 We need to make sure the applications appear in the right place and only once in the applications/preferences menu. This bug is just one example of this. Someone should come up with a list of all issues and then we can easily fix all of them at once. Just use the menu bar applet in the panel to make sure you see all the right submenus. Then we have some less important issues, but still things that I think we should really focus on: tomboy is needed by (installed) gconf2-branding-openSUSE-2.26-6.1.noarch https://bugzilla.novell.com/show_bug.cgi?id=531836 This is an issue for KDE users that have gconf2-branding-openSUSE installed -- they probably don't want to have tomboy, gnome-panel and all the mono stack just because of the gconf2-branding-openSUSE package. We can switch the Requires to a Recommends, but the real fix is to fix the branding package, which is not easy... Help welcome there (note: implies good knowledge of packaging). gnome-user-share: Could not make a filename from '' https://bugzilla.novell.com/show_bug.cgi?id=515025 Would need to know if it's still valid with current G:F. Game "lightsoff" cannot start https://bugzilla.novell.com/show_bug.cgi?id=541824 There is also an issue with same-gnome-clutter. If this is still valid, we might want to just disable the experimental games in gnome-games for 11.2. The Epiphany Web Browser cannot be used. https://bugzilla.novell.com/show_bug.cgi?id=543577 Needs investigation. (Note that it doesn't mean other bugs don't get fixed -- we do fix other bugs too, but those ones are really important) How to help =========== 0) Identify other potential shipstoppers It's easy to do so: go over our bug list (GNOME bugs in 11.2) and look for any other really big issue that I missed. The bug has to be quite visible, and has to look like it could affect more than one person. 1) Bug fixing Well, if you can fix bugs, then just do it :-) Nothing really important to say there. 2) Look if a fix exists elsewhere You can look if a fix for a bug already exists somewhere. There are various places where you can check: + newer upstream version of a package: if there's a new upstream version, maybe it already contains the fix. If it does, then please tell us! + git/svn/etc.: the fix might already be upstream, but not in a released version. In this case, you need to look at git/svn/etc. Most projects have a web interface that lets you do this easily (eg, http://git.gnome.org/ for GNOME) + patches in other distros: it often happens that another distro already found the issue and fixed it with a patch. There are links to websites where you can see patches from packages in other distros at http://live.gnome.org/VendorPatches. Often, I just check at Fedora, Mandriva and Ubuntu. + upstream bug: if nothing else worked, you can check the upstream bugzilla for a similar bug. There might be a patch attached there. 3) Test a potential fix For some bugs, we already have a potential fix (or we found one with the steps above), and we need someone to make sure it fixes the issue. This might imply rebuilding a package locally (to avoid waiting for the build service), but it's easy to do so with osc. If you need help for this, just join #opensuse-gnome and people will guide you. (This step is of course quite important so you can definitely help) 4) Provide required information For some bugs, we need more information. We request this in the bug, and then we have to wait for somebody to provide the information. And unfortunately, sometimes we have to wait quite a bit :/ 5) Try to reproduce the bug with latest packages It happens that the bug is just fixed with a package update. So just running GNOME:Factory and trying to reproduce the issues can help identify fixed bugs. I can't run Factory on my computer ================================== Yep, this happens and this is understandable. But you can still run it in a virtual machine and work on most issues there (some issues require some specific hardware, so those ones are obviously not reproducable in the virtual machine). Here's how to do this: + install VirtualBox + download the latest LiveCD from http://download.opensuse.org/factory/iso/ + launch a virtual machine and boot from the livecd. + then, you can try to reproduce issues directly from there, or you can first install the livecd (I recommend you configure the virtual machine with a 5GB disk in this case). The latter is better. + if you install the livecd, then please also enable the GNOME:Factory and GNOME:Backports:Factory repositories from the build service. You can follow the instructions at http://en.opensuse.org/GNOME/2.26 to do this. You will need to adapt the instructions like this: - replace GNOME:STABLE:2.26 with GNOME:Factory - replace GNOME:Backports:2.26 with GNOME:Backports:Factory - replace openSUSE_11.1 with openSUSE_Factory + if you installed and configured the repositories, make sure to update to the latest version of the packages with "zypper ref; zypper dup" And then you're all set! I can't stress enough that doing one of the above will help us a lot, so if you have some free time, please do it! Cheers, Vincent -- Les gens heureux ne sont pas pressés. -- To unsubscribe, e-mail: opensuse-gnome+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-gnome+help@opensuse.org
lø., 03.10.2009 kl. 12.30 +0200, skrev Vincent Untz:
The Epiphany Web Browser cannot be used. https://bugzilla.novell.com/show_bug.cgi?id=543577 Needs investigation.
I had this issue as well in a earlier milestone. Now Epip. starts just fine and works ok. However, if I enable some extensions -> those do not work that good. It's not possible to edit settings of extensions and what not. I've replied in the bug in question, asking the reporter to disable plugins, lets see if that makes a diff. for the user. If it does, I guess we need to file a new bug for the epiphany-extensions package. Bjørn -- To unsubscribe, e-mail: opensuse-gnome+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-gnome+help@opensuse.org
Dňa 3.10.2009 12:30, Vincent Untz wrote / napísal(a):
Hi,
Please read this mail carefully -- if you think you can't help, you're wrong because you can definitely help, even if you don't know how to package/code and even if you don't have a free machine to test factory.
I'll talk about what I think are our current shipstoppers, and then how people can help. Oh, and it'd be nice to avoid turning this thread into a "please fix this specific bug" unless the bug in question is really major ;-)
Current shipstoppers ====================
This is my current list of GNOME shipstoppers. Note that this is different from the official list of shipstoppers (decided by coolo), and so it could be seen as a list of "Vincent really wants this to be fixed for 11.2" bugs.
Also note that some majors issues are already fixed in G:F but the fixes are not yet available (waiting for the build service to publish them, but you can download them via the build service web interface). One such issue is a bad crash in many gtk+ apps -- if you experience this, you probably want the gtk2 package in G:F.
GNOME live system wants empty root password https://bugzilla.novell.com/show_bug.cgi?id=537343 This is currently NEEDINFO, if someone can provide the requested information, that would help a lot.
What i noticed, the root password is required by live installer - /sbin/yast2 live-installer on LiveCD. Reproducible on real harware and in VMware.
Restart fails to restart computer https://bugzilla.novell.com/show_bug.cgi?id=540482 I would think the gdm package that is waiting to be built/published in G:F fixes at least part of this. Testing welcome. More investigation might be needed: clicking on "Restart" in GDM takes a bit too long before something happens. Could be a ConsoleKit issue.
I can confirm that in M8 shutdown, restart and logout don´t work correctly. Reproducible on real hardware, in VMware, from LiveCD and from installed system also. Logout : system always logs in back Restart: system is logs in back the first time, the second time is restarted Shutdown: system is logs in back the first time, the second time is halted.
after suspend via lid close the system resumes and then suspends again https://bugzilla.novell.com/show_bug.cgi?id=540517 The issue is identified, and I've pushed the bug upstream for discussion. I tried a first fix that doesn't work, but I have an idea of another workaround that should be easy to implement.
I can confirm the same experience on HP NX 6110.
no gnome taskbar after install https://bugzilla.novell.com/show_bug.cgi?id=543876 The panel crashes on start. I have *no idea* why this happens. I've requested some information (in this bug, and in an upstream bug which is linked from there too). If you can reproduce the issue, please please get in touch with me so that we can debug it. Just launching the panel in gdb would help.
sonar: gdm panel contains GtkComboBox that are unreadable https://bugzilla.novell.com/show_bug.cgi?id=544079 This happens with the latest sonar version. I tried to fix this but I'm obviously not good enough with gtk+ theming. If someone can fix it before Jakub, then please do it.
It is hard to test, because is unable to log out. The bug above.
Open with install Software cannot be used. https://bugzilla.novell.com/show_bug.cgi?id=543595 Looks like some gnome-packagekit issue.
I can confirm it. It´s reproducible.
'Preferred Applications' appears twice in gnome control center https://bugzilla.novell.com/show_bug.cgi?id=533491 We need to make sure the applications appear in the right place and only once in the applications/preferences menu. This bug is just one example of this. Someone should come up with a list of all issues and then we can easily fix all of them at once. Just use the menu bar applet in the panel to make sure you see all the right submenus.
Yes, 'Preferred Applications' is appeared twice.
Then we have some less important issues, but still things that I think we should really focus on:
tomboy is needed by (installed) gconf2-branding-openSUSE-2.26-6.1.noarch https://bugzilla.novell.com/show_bug.cgi?id=531836 This is an issue for KDE users that have gconf2-branding-openSUSE installed -- they probably don't want to have tomboy, gnome-panel and all the mono stack just because of the gconf2-branding-openSUSE package. We can switch the Requires to a Recommends, but the real fix is to fix the branding package, which is not easy... Help welcome there (note: implies good knowledge of packaging).
gnome-user-share: Could not make a filename from '' https://bugzilla.novell.com/show_bug.cgi?id=515025 Would need to know if it's still valid with current G:F.
Game "lightsoff" cannot start https://bugzilla.novell.com/show_bug.cgi?id=541824 There is also an issue with same-gnome-clutter. If this is still valid, we might want to just disable the experimental games in gnome-games for 11.2.
The Epiphany Web Browser cannot be used. https://bugzilla.novell.com/show_bug.cgi?id=543577 Needs investigation.
(Note that it doesn't mean other bugs don't get fixed -- we do fix other bugs too, but those ones are really important)
How to help ===========
0) Identify other potential shipstoppers
It's easy to do so: go over our bug list (GNOME bugs in 11.2) and look for any other really big issue that I missed. The bug has to be quite visible, and has to look like it could affect more than one person.
1) Bug fixing
Well, if you can fix bugs, then just do it :-) Nothing really important to say there.
2) Look if a fix exists elsewhere
You can look if a fix for a bug already exists somewhere. There are various places where you can check:
+ newer upstream version of a package: if there's a new upstream version, maybe it already contains the fix. If it does, then please tell us! + git/svn/etc.: the fix might already be upstream, but not in a released version. In this case, you need to look at git/svn/etc. Most projects have a web interface that lets you do this easily (eg, http://git.gnome.org/ for GNOME) + patches in other distros: it often happens that another distro already found the issue and fixed it with a patch. There are links to websites where you can see patches from packages in other distros at http://live.gnome.org/VendorPatches. Often, I just check at Fedora, Mandriva and Ubuntu. + upstream bug: if nothing else worked, you can check the upstream bugzilla for a similar bug. There might be a patch attached there.
3) Test a potential fix
For some bugs, we already have a potential fix (or we found one with the steps above), and we need someone to make sure it fixes the issue. This might imply rebuilding a package locally (to avoid waiting for the build service), but it's easy to do so with osc. If you need help for this, just join #opensuse-gnome and people will guide you.
(This step is of course quite important so you can definitely help)
4) Provide required information
For some bugs, we need more information. We request this in the bug, and then we have to wait for somebody to provide the information. And unfortunately, sometimes we have to wait quite a bit :/
5) Try to reproduce the bug with latest packages
It happens that the bug is just fixed with a package update. So just running GNOME:Factory and trying to reproduce the issues can help identify fixed bugs.
I can't run Factory on my computer ==================================
Yep, this happens and this is understandable. But you can still run it in a virtual machine and work on most issues there (some issues require some specific hardware, so those ones are obviously not reproducable in the virtual machine).
Here's how to do this:
+ install VirtualBox + download the latest LiveCD from http://download.opensuse.org/factory/iso/ + launch a virtual machine and boot from the livecd. + then, you can try to reproduce issues directly from there, or you can first install the livecd (I recommend you configure the virtual machine with a 5GB disk in this case). The latter is better. + if you install the livecd, then please also enable the GNOME:Factory and GNOME:Backports:Factory repositories from the build service. You can follow the instructions at http://en.opensuse.org/GNOME/2.26 to do this. You will need to adapt the instructions like this: - replace GNOME:STABLE:2.26 with GNOME:Factory - replace GNOME:Backports:2.26 with GNOME:Backports:Factory - replace openSUSE_11.1 with openSUSE_Factory + if you installed and configured the repositories, make sure to update to the latest version of the packages with "zypper ref; zypper dup"
And then you're all set!
I can't stress enough that doing one of the above will help us a lot, so if you have some free time, please do it!
Cheers,
Vincent
-- S pozdravom / Best regards, Rasto -- To unsubscribe, e-mail: opensuse-gnome+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-gnome+help@opensuse.org
Restart fails to restart computer https://bugzilla.novell.com/show_bug.cgi?id=540482
With the latest G:F on 11.1, this appears sorted to me.
'Preferred Applications' appears twice in gnome control center https://bugzilla.novell.com/show_bug.cgi?id=533491 We need to make sure the applications appear in the right place and only once in the applications/preferences menu. This bug is just one example of this. Someone should come up with a list of all issues and then we can easily fix all of them at once. Just use the menu bar applet in the panel to make sure you see all the right submenus.
For each issue, a suggestion of which place they should reside would be handy too as they're spotted. In this case, I'd say System rather than Look & Feel. SubmitReq submitted - 21632. -- James Ogley (riggwelter) openSUSE Member GNOME Team and Planet SUSE e: riggwelter@opensuse.org w: http://opensuse.org/GNOME t: @riggwelter w: http://www.planetsuse.org openSUSE: Get It, Discover It, Create It at http://www.opensuse.org -- To unsubscribe, e-mail: opensuse-gnome+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-gnome+help@opensuse.org
tomboy is needed by (installed) gconf2-branding-openSUSE-2.26-6.1.noarch https://bugzilla.novell.com/show_bug.cgi?id=531836 This is an issue for KDE users that have gconf2-branding-openSUSE installed -- they probably don't want to have tomboy, gnome-panel and all the mono stack just because of the gconf2-branding-openSUSE package. We can switch the Requires to a Recommends, but the real fix is to fix the branding package, which is not easy... Help welcome there (note: implies good knowledge of packaging).
I can totally take this one. I spent some serious time messing with the branding in *SUSE. I was think that the ideal fix would be to remove tomboy from the panel and branding and have the tomboy package add itself to the panel? Stephen -- To unsubscribe, e-mail: opensuse-gnome+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-gnome+help@opensuse.org
participants (5)
-
Bjørn Lie -
James Ogley -
Rastislav Krupanský -
Stephen Shaw -
Vincent Untz