Re: [opensuse-factory] [status report] openSUSE distribution, week 36
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Juan Erbes escribió: > 2007/9/4, Christoph Thiel <[EMAIL PROTECTED]>: >> Preface: ... a bit late and short due to Beta3 preparations, but still on >> time (it's still Tuesday ;)) >> >> status report: openSUSE distribution, week 36 >> --- >> >> - 10.3 Beta3: first internal test build from today looks promising. Will >> hopefully only need minor tweaks tomorrow. Public release is scheduled for >> Thursday (2007-09-06). >> - autobuild status: 8 failing packages on i386, 7 on x86_64, 25 on ppc. >> - bug count down from last week: 14 blockers, 90 critical. >> * bug review pending after Beta3 is out >> * if there is anything > NEEDINFO to cthiel or coolo, to get it onto our radar. >> - the team made very good progress on libzypp / package management last >> week! >> - bundle-lang situation improved -- not completly solved for Beta3 (check >> out #302270 for details) >> - current focus for Beta3: >> * bundle-lang and friends >> * patterns / media layout >> * LiveCD >> * libzypp >> >> > > In my system with the last update of factory (comes from beta 1 the > problem) all applications based on wxGTK (such as audacity or amule) > fail in 32 or 64 bits when I try to save a file. > For example for audacity I got with ddd in 32 bits kde version: > > Program received signal SIGABRT, Aborted. > [Switching to Thread 0xb678f6d0 (LWP 16176)] > 0xe410 in __kernel_vsyscall () > (gdb) bt > #0 0xe410 in __kernel_vsyscall () > #1 0xb724e835 in raise () from /lib/libc.so.6 > #2 0xb7250121 in abort () from /lib/libc.so.6 > #3 0xb728b41b in ?? () from /lib/libc.so.6 > #4 0x in ?? () > > For example for amule I got with ddd in 32 bits kde version: > > Program received signal SIGABRT, Aborted. > [Switching to Thread 0xb6c76a00 (LWP 16283)] > 0xe410 in __kernel_vsyscall () > (gdb) > No source file named 0.0.0.0. > (gdb) bt > #0 0xe410 in __kernel_vsyscall () > #1 0xb773b835 in raise () from /lib/libc.so.6 > #2 0xb773d121 in abort () from /lib/libc.so.6 > #3 0xb777841b in ?? () from /lib/libc.so.6 > #4 0x in ?? () > > Other problem appeared in the 32 bits kde version (updated from 10.2), > is the frequent crash of the rpmdb. This problem not appear in the > same system with the 64 bits version and a fresh install of 10.3 beta > 2 X86-64 kde. > > I mean that the problem with the rpmdb comes from e file system access > error, derived from a inmature state of the ahci driver for the > SB600/RD580 chipset . For example now I do: > > dmesg | grep ahci > ahci :00:12.0: version 3.0 > ahci :00:12.0: controller can't do 64bit DMA, forcing 32bit > ahci :00:12.0: controller can't do PMP, turning off CAP_PMP > ahci :00:12.0: AHCI 0001.0100 32 slots 4 ports 3 Gbps 0xf impl SATA mode > ahci :00:12.0: flags: ncq sntf ilck led clo pio slum part > scsi0 : ahci > scsi1 : ahci > scsi2 : ahci > scsi3 : ahci > > For installing the the 64 bits kde version I must resizing a partition > for create a new partition. It was very difficult, and the only way > was starting the install process with "safe settings", because the > hard disk controller has restarted from time to time. > > Regards > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > Hi: I'm sorry Juan,but using beta1,beta2 and now beta3 I have no problem with audacity,amule or rpmdb...I only use 32 bits system.It's possible the problem only appears on 64 bits system using 32 bits programs... Regards - -- Chema Ollés Usuario Linux: #198057 openSUSE 10.3 (i586) Beta3 kernel-2.6.22.5-8-default #1 SMP 2007/08/31 14:06:44 UTC i686 GNU/Linux -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.4-svn0 (GNU/Linux) iD8DBQFG3lOam5lTdgS9W18RAhXGAKCNXMZNEs1eTidcwp4LesGhXgs41wCfQk9w uZ1u2dcDsUZuJf1+9ozVOsU= =9LDB -END PGP SIGNATURE- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-factory] Device already mounted or mountpoint busy error after some beta2 update, I guess
On Tuesday 04 September 2007 15:50, Wolfgang Woehl wrote: > Dienstag, 4. September 2007 Wolfgang Woehl: > > Montag, 3. September 2007 Rajko M.: > > > On Sunday 02 September 2007 16:15, Wolfgang Woehl wrote: > > > > But my initial posting was about an internal device > > > > disappearing from the usual mount infrastructure. > > > > > > It is solved. > > > > I still don't know why the internal device got grabbed by device-mapper. > > I suspect not having it in fstab (which was on purpose) led to it. > > Although I never conciously configured or invoked dm-mechanisms. > > Plus, I realize this just now, plugging in a usb mass-storage device makes > kde pop up "open in window?" which it tries but fails to show the content > of because device-mapper grabbed it. Is this the default behaviour? It > can't be. I'm pretty sure it is not. Is this happening after deleting /etc/udev/rules.d/62-dm_linear.rules and dmsetup remove_all -- Regards, Rajko. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-factory] [status report] openSUSE distribution, week 36
2007/9/4, Christoph Thiel <[EMAIL PROTECTED]>: > Preface: ... a bit late and short due to Beta3 preparations, but still on > time (it's still Tuesday ;)) > > status report: openSUSE distribution, week 36 > --- > > - 10.3 Beta3: first internal test build from today looks promising. Will > hopefully only need minor tweaks tomorrow. Public release is scheduled for > Thursday (2007-09-06). > - autobuild status: 8 failing packages on i386, 7 on x86_64, 25 on ppc. > - bug count down from last week: 14 blockers, 90 critical. > * bug review pending after Beta3 is out > * if there is anything NEEDINFO to cthiel or coolo, to get it onto our radar. > - the team made very good progress on libzypp / package management last > week! > - bundle-lang situation improved -- not completly solved for Beta3 (check > out #302270 for details) > - current focus for Beta3: > * bundle-lang and friends > * patterns / media layout > * LiveCD > * libzypp > > In my system with the last update of factory (comes from beta 1 the problem) all applications based on wxGTK (such as audacity or amule) fail in 32 or 64 bits when I try to save a file. For example for audacity I got with ddd in 32 bits kde version: Program received signal SIGABRT, Aborted. [Switching to Thread 0xb678f6d0 (LWP 16176)] 0xe410 in __kernel_vsyscall () (gdb) bt #0 0xe410 in __kernel_vsyscall () #1 0xb724e835 in raise () from /lib/libc.so.6 #2 0xb7250121 in abort () from /lib/libc.so.6 #3 0xb728b41b in ?? () from /lib/libc.so.6 #4 0x in ?? () For example for amule I got with ddd in 32 bits kde version: Program received signal SIGABRT, Aborted. [Switching to Thread 0xb6c76a00 (LWP 16283)] 0xe410 in __kernel_vsyscall () (gdb) No source file named 0.0.0.0. (gdb) bt #0 0xe410 in __kernel_vsyscall () #1 0xb773b835 in raise () from /lib/libc.so.6 #2 0xb773d121 in abort () from /lib/libc.so.6 #3 0xb777841b in ?? () from /lib/libc.so.6 #4 0x in ?? () Other problem appeared in the 32 bits kde version (updated from 10.2), is the frequent crash of the rpmdb. This problem not appear in the same system with the 64 bits version and a fresh install of 10.3 beta 2 X86-64 kde. I mean that the problem with the rpmdb comes from e file system access error, derived from a inmature state of the ahci driver for the SB600/RD580 chipset . For example now I do: dmesg | grep ahci ahci :00:12.0: version 3.0 ahci :00:12.0: controller can't do 64bit DMA, forcing 32bit ahci :00:12.0: controller can't do PMP, turning off CAP_PMP ahci :00:12.0: AHCI 0001.0100 32 slots 4 ports 3 Gbps 0xf impl SATA mode ahci :00:12.0: flags: ncq sntf ilck led clo pio slum part scsi0 : ahci scsi1 : ahci scsi2 : ahci scsi3 : ahci For installing the the 64 bits kde version I must resizing a partition for create a new partition. It was very difficult, and the only way was starting the install process with "safe settings", because the hard disk controller has restarted from time to time. Regards - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-factory] Frequent rpmdb crashes in opensuse 10.3 beta 2
2007/9/4, Michael Schroeder <[EMAIL PROTECTED]>: > On Mon, Sep 03, 2007 at 09:45:30PM -0300, Juan Erbes wrote: > > The last days I got more than 5 crashes with the rpmdb, and must > > rebuild it with "rpm --rebuilddb", and in one case, after rebuilding, > > in the first case I woluld to install a rpm package. > > The last case was installing a package compiled in the system and > > created by checkinstall: > > > > rpmdb: PANIC: Argumento inválido > > rpmdb: PANIC: fatal region error detected; run recovery > > [...] > > Hmm, a problem with your memory chips? Please run memtest. > I runned for new memtest for about 33 minutes, after changing the memorys voltage (rpmdb crashes again), and not appear any memory error. I tested the 2 cores of the cpu in windows with orthos http://files.extremeoverclocking.com/file.php?f=200 and not apear any cpu error About the memory bandwith with my Athlon64 X2 5200, they are: L1 cache 128 21416 MB/s L2 cache 1024 K 5321 MB/s (1024 K per core) Memory 2047 M 2916 MB/s Those values are right? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-factory] Frequent rpmdb crashes in opensuse 10.3 beta 2
2007/9/4, Michael Schroeder <[EMAIL PROTECTED]>: > On Mon, Sep 03, 2007 at 09:45:30PM -0300, Juan Erbes wrote: > > The last days I got more than 5 crashes with the rpmdb, and must > > rebuild it with "rpm --rebuilddb", and in one case, after rebuilding, > > in the first case I woluld to install a rpm package. > > The last case was installing a package compiled in the system and > > created by checkinstall: > > > > rpmdb: PANIC: Argumento inválido > > rpmdb: PANIC: fatal region error detected; run recovery > > [...] > > Hmm, a problem with your memory chips? Please run memtest. > How long time I must run memtest? I runed it for many minutes, and not appear any memory error. I changed the voltage from the memorys from 1.9 to 2.1 volts as recomended by OCZ: http://www.ocztechnology.com/products/memory/ocz_ddr2_pc2_6400_reaper_hpc_edition (This is the exact model of the memorys) Yesterday I rebuilded the rpmdb, and now after adjusting the memorys voltage, the problem continues. Regards - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[opensuse-factory] [status report] openSUSE distribution, week 36
Preface: ... a bit late and short due to Beta3 preparations, but still on time (it's still Tuesday ;)) status report: openSUSE distribution, week 36 --- - 10.3 Beta3: first internal test build from today looks promising. Will hopefully only need minor tweaks tomorrow. Public release is scheduled for Thursday (2007-09-06). - autobuild status: 8 failing packages on i386, 7 on x86_64, 25 on ppc. - bug count down from last week: 14 blockers, 90 critical. * bug review pending after Beta3 is out * if there is anything
Re: [opensuse-factory] Device already mounted or mountpoint busy error after some beta2 update, I guess
Dienstag, 4. September 2007 Wolfgang Woehl: > Montag, 3. September 2007 Rajko M.: > > On Sunday 02 September 2007 16:15, Wolfgang Woehl wrote: > > > But my initial posting was about an internal device > > > disappearing from the usual mount infrastructure. > > > > It is solved. > > I still don't know why the internal device got grabbed by device-mapper. I > suspect not having it in fstab (which was on purpose) led to it. Although I > never conciously configured or invoked dm-mechanisms. Plus, I realize this just now, plugging in a usb mass-storage device makes kde pop up "open in window?" which it tries but fails to show the content of because device-mapper grabbed it. Is this the default behaviour? It can't be. Wolfgang - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-factory] Default package request
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Stephan Kulow wrote: > Am Donnerstag 30 August 2007 schrieb Alex Lau: >> Is that possible to install pin by default? >> >> So we can create the next great thing call pin-install ... meaning base >> on the pin info after locating the package which is missing and trigger >> the install ? Or just install webpin to have it query the online database that includes community repositories: http://dev-loki.blogspot.com/search/label/webpin It's in http://download.opensuse.org/repositories/openSUSE:/Tools/ cheers - -- -o) Pascal Bleser http://linux01.gwdg.de/~pbleser/ /\\ <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> _\_v The more things change, the more they stay insane. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org iD8DBQFG3cOir3NMWliFcXcRAn6LAJ9yVS39HOO41JEGZFbwphKXXhXq/ACfUgh8 Ol+s6qJycuO7eI8KKvMWhgQ= =3lRn -END PGP SIGNATURE- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-factory] High number of serious bugs in GNOME
On Tue, 2007-09-04 at 15:37 -0300, Druid wrote: > > > > 3) We (as the GNOME maintainers who work for Novell) have traditionally > > not focused on openSUSE much, rather spending most of our time on SLED. > > This improved for 10.3 and well continue to improve, but we lagged a > > little more than we thought due to SP1 of SLED 10. > > > > Seems one of those very traditional traditions that goes through > centuries and more centuries, and generations and more generations. > > As far as I know, KDE is included in SLED too. How come KDE doesnt > have those problems of too much focus in SLED? What can we expect of > that? That the gnome in opensuse is barely maintained? Or does that > mean that the KDE guys doesnt put much effort in SLED? I think its fair to say that in the past its been paid less attention than the GNOME in SLED, although I would rate it as higher than "barely maintained". But things like features, polish, maintenance updates, etc have been targeted at SLED not openSUSE for development cycles. All I can say is: if you're a KDE user on openSUSE doesn't affect you much :-). If you're a GNOME use drop by our list or irc channel and help keep us on track just like Alberto did by sending the original mail :-). -JP -- JP Rosevear <[EMAIL PROTECTED]> Novell, Inc. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-factory] High number of serious bugs in GNOME
Druid <[EMAIL PROTECTED]> writes: >> >> 3) We (as the GNOME maintainers who work for Novell) have traditionally >> not focused on openSUSE much, rather spending most of our time on SLED. >> This improved for 10.3 and well continue to improve, but we lagged a >> little more than we thought due to SP1 of SLED 10. >> > > Seems one of those very traditional traditions that goes through > centuries and more centuries, and generations and more generations. > > As far as I know, KDE is included in SLED too. How come KDE doesnt > have those problems of too much focus in SLED? What can we expect of > that? That the gnome in opensuse is barely maintained? Or does that > mean that the KDE guys doesnt put much effort in SLED? It's not as easy as you're thinking. The KDE guys had some advantage with no major release for quite some time. Stabilizing KDE 3.5.x is much less work than stabilizing a major release like KDE 4 - or GNOME 2.20. So, there have been quite synergies between openSUSE and SLED on the KDE side - something we could not benefit from with GNOME. And that means we have to do more work with GNOME and then you might focus... I'm glad that the GNOME maintainers have already improve much working on openSUSE, Andreas -- Andreas Jaeger, Director Platform/openSUSE, [EMAIL PROTECTED] SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) Maxfeldstr. 5, 90409 Nürnberg, Germany GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126 pgp7mBtvZWPzo.pgp Description: PGP signature
Re: [opensuse-factory] High number of serious bugs in GNOME
> > 3) We (as the GNOME maintainers who work for Novell) have traditionally > not focused on openSUSE much, rather spending most of our time on SLED. > This improved for 10.3 and well continue to improve, but we lagged a > little more than we thought due to SP1 of SLED 10. > Seems one of those very traditional traditions that goes through centuries and more centuries, and generations and more generations. As far as I know, KDE is included in SLED too. How come KDE doesnt have those problems of too much focus in SLED? What can we expect of that? That the gnome in opensuse is barely maintained? Or does that mean that the KDE guys doesnt put much effort in SLED? thanks Marcio Ferreira --- Druid > 4) As some one else mentioned, you almost never close out all the bugs > for release > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-factory] High number of serious bugs in GNOME
On Sun, 2007-09-02 at 17:52 +0200, Alberto Passalacqua wrote: > Hello everyone, > during a discussion on IRC it emerged that GNOME still has a very high > number of blockers and critical bugs. > As it can be seen here: > > https://bugzilla.novell.com/report.cgi?x_axis_field=&y_axis_field=component&z_axis_field=&query_format=report-table&short_desc_type=allwordssubstr&short_desc=&long_desc_type=fulltext&long_desc=&classification=openSUSE&product=openSUSE+10.3&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=anywords&keywords=&bug_status=NEW&bug_status=ASSIGNED&bug_status=NEEDINFO&bug_status=REOPENED&bug_severity=Blocker&bug_severity=Critical&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailqa_contact2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&format=table&action=wrap&field0-0-0=noop&type0-0-0=noop&value0-0-0= > > GNOME + Evolution has 26 of them. > Plus, from bugzilla it appears that GNOME + GNOME Admin/Platform + > Evolution have 201 bugs: > > https://bugzilla.novell.com/report.cgi?x_axis_field=&y_axis_field=component&z_axis_field=&query_format=report-table&short_desc_type=allwordssubstr&short_desc=&long_desc_type=fulltext&long_desc=&classification=openSUSE&product=openSUSE+10.3&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=anywords&keywords=&bug_status=NEW&bug_status=ASSIGNED&bug_status=NEEDINFO&bug_status=REOPENED&bug_severity=Blocker&bug_severity=Critical&bug_severity=Major&bug_severity=Normal&bug_severity=Minor&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailqa_contact2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&format=table&action=wrap&field0-0-0=noop&type0-0-0=noop&value0-0-0= > > Considering the short time before the final release (~1 month), I think > it would be helpful to know the actual situation of the fixes, and if > there's enough time to solve all these issues before the release date. I'll answer the original mail, but I'll collect thoughts related to other replies here too. For the GNOME bugs in particular at least there are several issues causing the count to be high and not well maintained: 1) We (as the GNOME maintainers) have not been good at redirecting bugs upstream. We do have the keyword "should_go_upstream" in use which indicates what we want to upstream it and resolve it in the opensuse bugzilla, but we've been slow to do this though and its something we've not publicized and that was probably wrong. 2) We have not been good at grading bug severity, generally severity has been left at whatever the filer put it, although Blocker/Critical/Major have undergone more scrutiny in 10.3 at least. Further complicating this is that we (as a project) do not define severity well for instance from what I could find: http://en.opensuse.org/Bug_Reporting_FAQ http://en.opensuse.org/Submitting_Bug_Reports Only one mentions severity but its a brief reference to blocker. The ones on the Novell bugzilla are also weak: https://bugzilla.novell.com/page.cgi?id=fields.html#bug_severity 3) We (as the GNOME maintainers who work for Novell) have traditionally not focused on openSUSE much, rather spending most of our time on SLED. This improved for 10.3 and well continue to improve, but we lagged a little more than we thought due to SP1 of SLED 10. 4) As some one else mentioned, you almost never close out all the bugs for release Now, not one to simply list problems with out a solution, here on some positives: 1) I've been monitoring the count, its been trending down over the last three weeks (including major and above) 2) There are a number of easy packaging related things (bnc-team-gnome-build) we can pick off before 10.3 3) Mark Gordon a Novell QA person has been able to spend a lot more time triaging and moving bugs upstream over the last several weeks 4) Of the criticals, only 3 have not been active (generally activity means they are getting attention on the way to a fix) in the last week and they are: https://bugzilla.novell.com/show_bug.cgi?id=299331 https://bugzilla.novell.com/show_bug.cgi?id=299005 Both being worked on by hpj as part of a larger set of help fixes (rarian integration), its just a big mess atm because we have to tie this help system into the suse help system which is based on how kde discovers help files and our older patches broke big time. We should look at the for 10.4 Thats good and all , but it doesn't go all the way of course - Gary Ekker has been getting some better bug criteria created for understanding when we should upstream, wontfix, invalid, etc. Its for both SLED and openSUSE, we did a test run last week and it worked reasonably well. I think Gary would like to publish these so
Re: [opensuse-factory] High number of serious bugs in GNOME
On Mon, 2007-09-03 at 11:47 +0200, Alberto Passalacqua wrote: > > I suppose for the quality of GNOME it would be more helpful if people > > would report issues upstream. At least if the perception is correct > > that bugs in openSUSE GNOME are only fixed by pulling new releases > > from upstream. > > That's ok, but it should have been clarified at the beginning of the > development stage, I think. Now, 17 days before the release, it is > probably too late to get them fixed for 2.20, which will be included in > openSUSE 10.3. > > Moreover, on what basis should we distinguish between GNOME bugs to > report upstream, and GNOME bugs to report on bugzilla? The best thing to do is to report it here so that we are aware of the bug. -Gary - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-factory] High number of serious bugs in GNOME
On Mon, 2007-09-03 at 10:52 +0200, Richard Guenther wrote: > On Sun, 2 Sep 2007, Francis Giannaros wrote: > > > On 9/2/07, Bernhard Walle <[EMAIL PROTECTED]> wrote: > > > * Alberto Passalacqua <[EMAIL PROTECTED]> [2007-09-02 17:52]: > > > > during a discussion on IRC it emerged that GNOME still has a very high > > > > number of blockers and critical bugs. > > > > > > GNOME will be updated before release. > > > > Perhaps you could clarify what this means? Is it hoped that the > > updates and final release will solve all the 200+ bugs? The only > > reason I ask about this is because I notice around the place the > > general sense from some users of neglect for GNOME in openSUSE, which > > I know is certainly as a statement unfair; but I can see why some of > > them might question things when you take a look at comparative figures > > like this (GNOME 200+ with a lot of blockers, KDE just 64, and dealing > > with a web browser). > > > > It would be a real shame to have GNOME slip behind as it did in 10.2 > > which I think everyone will agree was not ideal. > > I suppose for the quality of GNOME it would be more helpful if people > would report issues upstream. At least if the perception is correct > that bugs in openSUSE GNOME are only fixed by pulling new releases > from upstream. That perception is not accurate. Although we are tracking some of these bugs upstream and taking the fixes from the upstream release as they become available. -Gary - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-factory] High number of serious bugs in GNOME
On Sun, 2007-09-02 at 22:02 +0100, Francis Giannaros wrote: > On 9/2/07, Bernhard Walle <[EMAIL PROTECTED]> wrote: > > * Alberto Passalacqua <[EMAIL PROTECTED]> [2007-09-02 17:52]: > > > during a discussion on IRC it emerged that GNOME still has a very high > > > number of blockers and critical bugs. > > > > GNOME will be updated before release. > > Perhaps you could clarify what this means? Is it hoped that the > updates and final release will solve all the 200+ bugs? The only > reason I ask about this is because I notice around the place the > general sense from some users of neglect for GNOME in openSUSE, which > I know is certainly as a statement unfair; but I can see why some of > them might question things when you take a look at comparative figures > like this (GNOME 200+ with a lot of blockers, KDE just 64, and dealing > with a web browser). There are only 12 GNOME bugs of severity critical and blocker. I'm confident that we can resolve those before the release of 10.3. > > It would be a real shame to have GNOME slip behind as it did in 10.2 > which I think everyone will agree was not ideal. None of us want that and we are working hard to ensure that it doesn't happen with 10.3. -Gary - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-factory] High number of serious bugs in GNOME
On Sun, 2007-09-02 at 17:52 +0200, Alberto Passalacqua wrote: > Hello everyone, > during a discussion on IRC it emerged that GNOME still has a very high > number of blockers and critical bugs. > As it can be seen here: > > https://bugzilla.novell.com/report.cgi?x_axis_field=&y_axis_field=component&z_axis_field=&query_format=report-table&short_desc_type=allwordssubstr&short_desc=&long_desc_type=fulltext&long_desc=&classification=openSUSE&product=openSUSE+10.3&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=anywords&keywords=&bug_status=NEW&bug_status=ASSIGNED&bug_status=NEEDINFO&bug_status=REOPENED&bug_severity=Blocker&bug_severity=Critical&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailqa_contact2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&format=table&action=wrap&field0-0-0=noop&type0-0-0=noop&value0-0-0= > > GNOME + Evolution has 26 of them. > Plus, from bugzilla it appears that GNOME + GNOME Admin/Platform + > Evolution have 201 bugs: > > https://bugzilla.novell.com/report.cgi?x_axis_field=&y_axis_field=component&z_axis_field=&query_format=report-table&short_desc_type=allwordssubstr&short_desc=&long_desc_type=fulltext&long_desc=&classification=openSUSE&product=openSUSE+10.3&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=anywords&keywords=&bug_status=NEW&bug_status=ASSIGNED&bug_status=NEEDINFO&bug_status=REOPENED&bug_severity=Blocker&bug_severity=Critical&bug_severity=Major&bug_severity=Normal&bug_severity=Minor&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailqa_contact2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&format=table&action=wrap&field0-0-0=noop&type0-0-0=noop&value0-0-0= > > Considering the short time before the final release (~1 month), I think > it would be helpful to know the actual situation of the fixes, and if > there's enough time to solve all these issues before the release date. Yes we still have time to resolve the critical and blocker bugs, as well as many of the majors. -Gary - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[opensuse-factory] Re: BulletProofX - a critical feature request for openSUSE
> BulletProofX can really enlarge our user base to lots of new Windows > users alike. > It is very important to test this technology, and later integrate into our OS. You haven't read Benji's mail, have you? I'll quote to make it easier for you: > Ubuntu's "bulletproofX" is mostly hype as they're just utilising an > existing functionality of GDM, but it would be nice to have the same > functionality. So in order to "test and integrate", you'd first have to implement the same functionality in a way suitable for openSUSE. Volunteers anyone? Philipp - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-factory] Device already mounted or mountpoint busy error after some beta2 update, I guess
Montag, 3. September 2007 Rajko M.: > On Sunday 02 September 2007 16:15, Wolfgang Woehl wrote: > > But my initial posting was about an internal device > > disappearing from the usual mount infrastructure. > > It is solved. I still don't know why the internal device got grabbed by device-mapper. I suspect not having it in fstab (which was on purpose) led to it. Although I never conciously configured or invoked dm-mechanisms. > Have fun! I'm having more fun than I expected really :} Wolfgang - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-factory] GNOME: Pidgin, sane defaults
Magnus Boman wrote: > I've been talking to some people about the Pidgin defaults and we agreed > that the upstream defaults are not really sane. > We have an opportunity to get this patched with sane settings. > > Apart from https://bugzilla.novell.com/show_bug.cgi?id=304635, does > anyone have any other suggestions on what defaults we should have? Existence of an active Bonjour account would be really interesting feature for small companies - intranet IM working out of the box. Many of them now internally (and illegally) use ICQ, because their admin doesn't know, how to configure jabberd up. But I think, that hostname should not be configurable (but auto-generated) and should not be a part of user ID (I don't exactly know, how it is implemented and it does not work for me just now - see bugzilla), so one could "IM joe, wherever he sits", but be able to see, that joe is logged as [EMAIL PROTECTED] and [EMAIL PROTECTED] SuSE people can look at FATE 302550. -- Best Regards / S pozdravem, Stanislav Brabec software developer - SUSE LINUX, s. r. o. e-mail: [EMAIL PROTECTED] Lihovarská 1060/12tel: +420 284 028 966 190 00 Praha 9fax: +420 284 028 951 Czech Republichttp://www.suse.cz/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-factory] Default package request
Am Donnerstag 30 August 2007 schrieb Alex Lau: > Dear all > > Is that possible to install pin by default? > > So we can create the next great thing call pin-install ... meaning base > on the pin info after locating the package which is missing and trigger > the install ? I don't understand. Where would that pin-install be? Greetings, Stephan -- SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-factory] Frequent rpmdb crashes in opensuse 10.3 beta 2
On Mon, Sep 03, 2007 at 09:45:30PM -0300, Juan Erbes wrote:
> The last days I got more than 5 crashes with the rpmdb, and must
> rebuild it with "rpm --rebuilddb", and in one case, after rebuilding,
> in the first case I woluld to install a rpm package.
> The last case was installing a package compiled in the system and
> created by checkinstall:
>
> rpmdb: PANIC: Argumento inválido
> rpmdb: PANIC: fatal region error detected; run recovery
> [...]
Hmm, a problem with your memory chips? Please run memtest.
Cheers,
Michael.
--
Michael Schroeder [EMAIL PROTECTED]
SUSE LINUX Products GmbH, GF Markus Rex, HRB 16746 AG Nuernberg
main(_){while(_=~getchar())putchar(~_-1/(~(_|32)/13*2-11)*13);}
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-factory] High number of serious bugs in GNOME
"Rajko M." <[EMAIL PROTECTED]> writes: > On Monday 03 September 2007 13:06, Alberto Passalacqua wrote: >> > And for instance: >> > 301716Cri P5 open NEW Pidgin segfaults when sending >> > AIM message to yourself. >> > >> > Taking the type of application is it really critical? >> > Is that mean that critical is used for any crash? >> >> Funny, indeed. >> >> The reporter is Bryan Perry @ Novell, so it is probably considered >> important. > > It might be the company policy to set critical if application crashes, I have > seen such comment in one of bugs that you can find on the list. If you look > the list than you can see few similar reports. Later I'm going to see more, > but if there are many of the above kind GNOME is safe :-) I'm not aware of something - let's downgrade this bug, Andreas -- Andreas Jaeger, Director Platform / openSUSE, [EMAIL PROTECTED] SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) Maxfeldstr. 5, 90409 Nürnberg, Germany GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126 pgpF7uaLrHWQi.pgp Description: PGP signature
Re: [opensuse-factory] Can't add Full-Qualified-Hostname to hosts file using yast2
Hi James,
> In the "/etc/hosts" file on opensuse 10.2, I have the
> "Full-Qualified-Hostname" on my machine in like this:
> # IP-Address Full-Qualified-Hostname Short-Hostname
> 127.0.0.2 my_hostname.my_dns my_hostname
>
> This was not the case with 10.3 after I installed it - so I tried to add it
> (for reasons I won't go into here).
>
> I can add a Full-Qualified-Hostname (in the form of the line above)
> manually via the command line but I can't using yast2 by running "DNS and
> Hostname" with the "Change Hostname via DHCP" and "Write to Hostname to
> /etc/hosts" options selected.
Please file a bug and assign it to me. As there is a new feature in 10.3
("Enable defining different hostname for each static IP address"), the way
how hostnames are written to /etc/hosts has been changed. It seems that I've
moved around more code than it was necessary :(
Cheers
B.
--
\ Katarina Machalkova
\\\__o YaST developer
__\\\'/_ & hedgehog painter
signature.asc
Description: This is a digitally signed message part.
Re: [opensuse-factory] dev null incorrect permissions
On Mon, 2007-09-03 at 22:51 +0200, Marcus Meissner wrote: > On Mon, Sep 03, 2007 at 10:24:11PM +0200, Gerald Pfeifer wrote: > > On Sun, 2 Sep 2007, Florin Samareanu wrote: > > > Is this happening to anyone here with a current -FACTORY? > > > > > > [EMAIL PROTECTED]:~> ls -l /dev/*null* > > > -rw-rw-rw- 1 root root0 2007-09-02 22:45 /dev/null > > > -rwxrwxrwx 1 root root 2173 2007-09-02 22:24 /dev/null.2007-09-02.0 > > > lrwxrwxrwx 1 root root 17 2007-09-02 22:23 /dev/null.current -> > > > null.2007-09-02.0 > > > > > > Initial permissions on /dev/null were correct (like above) but after gdm > > > login permissions get rw for owner, none for other. also, permissions > > > for /dev/null.2007-09-02 are rw for owner , none for others. > > > > Yup. I have not been able to nail this down yet, because I cannot > > easily experiment with the machine I am seeing this on, but I have > > a hunch it is related to suspend (and only appears after resume). > > > > Can you, or anyone else, confirm and/or file a bug report on this? > > /dev/null should also be a device, not a file I guess. > although i have been able to reproduce it at will last week, after yesterday`s updates the bug no longer appears. I`m not sure what happened, but i hope it stays this way. 10x. > Ciao, Marcus - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-factory] opensuse10.3beta2 can not support dmraid
On Tue, Sep 04, 2007 at 01:55:22PM +0800, Pang Dawei wrote: > I installed opensuse10.3beta2 to a dmraid (raid1)function machine, > At the end of installation, the yast can not create initrd and > install bootloader. > Because the creating initrd missed 70-kpartx.rule file, the > mkinitrd is failed. > Can we fix the bug in the beta3? It has been addressed already. Ths fix will be in Beta3. Best, Christoph -- Christoph Thiel, Tech. Project Management, Research & Development SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
