- openSUSE Bugs

[Bug 198125] fglrx driver does not support X.Org > 7.1 / Mesa > 6.4.2
by bugzilla_noreply＠novell.com 18 Oct '06

18 Oct '06

https://bugzilla.novell.com/show_bug.cgi?id=198125 thoenig(a)novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Version|Alpha 5 |Alpha 5 plus ------- Comment #16 from thoenig(a)novell.com 2006-10-18 04:20 MST ------- -> Alpha 5 plus As promised by Stefan, now fglrx can not be used at all, as the hack (comment #4) was removed. If one wants to use fglrx he needs to rebuild xorg-x11-server with the hack being enabled. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.

1 0

[Bug 211774] New: gwget-0.98.1-13: local variable used before set
by bugzilla_noreply＠novell.com 18 Oct '06

18 Oct '06

https://bugzilla.novell.com/show_bug.cgi?id=211774 Summary: gwget-0.98.1-13: local variable used before set Product: openSUSE 10.2 Version: Alpha 5 Platform: All OS/Version: SuSE Linux 10.1 Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: dcb314(a)hotmail.com QAContact: qa(a)suse.de I just tried to compile package gwget-0.98.1-13 with the Intel C compiler. The compiler said ephy-gwget-extension.c(94): warning #592: variable "timestamp" is used before its value is set The source code is if (!dbus_g_proxy_call (remote_object, "OpenWindow", &error, G_TYPE_UINT, timestamp, G_TYPE_INVALID, G_TYPE_INVALID)) { g_warning (error->message); g_clear_error (&error); return FALSE; } Suggest initialise local variable "timestamp" before first use. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.

1 3

[Bug 149613] nscd sometimes dies
by bugzilla_noreply＠novell.com 18 Oct '06

18 Oct '06

https://bugzilla.novell.com/show_bug.cgi?id=149613 gdeschner(a)novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |cyril.peponnet(a)mpsa.com ------- Comment #6 from gdeschner(a)novell.com 2006-10-18 03:47 MST ------- *** Bug 212482 has been marked as a duplicate of this bug. *** -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.

1 0

[Bug 212482] New: nscd daemon gets down with status "dead" or "unused"
by bugzilla_noreply＠novell.com 18 Oct '06

18 Oct '06

https://bugzilla.novell.com/show_bug.cgi?id=212482 Summary: nscd daemon gets down with status "dead" or "unused" Product: SUSE Linux 10.1 Version: Final Platform: x86 OS/Version: SLED 10 Status: NEW Severity: Major Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: cyril.peponnet(a)mpsa.com QAContact: qa(a)suse.de CC: jeallison(a)novell.com As I said, nscd daemon gets down a few minutes after logging on cached account (AD auth with winbind) I've made some straces, it appears that nscd is terminated by a SIGTERM You can find both, log files and strace output attached. Regards (this bug can be a dupplicate of https://bugzilla.novell.com/show_bug.cgi?id=149613) -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.

1 3

[Bug 149613] nscd sometimes dies
by bugzilla_noreply＠novell.com 18 Oct '06

18 Oct '06

https://bugzilla.novell.com/show_bug.cgi?id=149613 ------- Comment #5 from gdeschner(a)novell.com 2006-10-18 03:45 MST ------- Created an attachment (id=101848) --> (https://bugzilla.novell.com/attachment.cgi?id=101848&action=view) nscd corefile -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.

1 0

[Bug 149613] nscd sometimes dies
by bugzilla_noreply＠novell.com 18 Oct '06

18 Oct '06

https://bugzilla.novell.com/show_bug.cgi?id=149613 gdeschner(a)novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|REMIND | ------- Comment #4 from gdeschner(a)novell.com 2006-10-18 03:43 MST ------- This very often happens to me as well, I managed to get a corefile. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.

1 0

[Bug 175939] Grub boot menu doesn't appear after suspending to disk (hibernating) and powering on the machine (it should allow only specific kernel or other OS's)
by bugzilla_noreply＠novell.com 18 Oct '06

18 Oct '06

https://bugzilla.novell.com/show_bug.cgi?id=175939 ------- Comment #12 from seife(a)novell.com 2006-10-18 03:19 MST ------- (In reply to comment #10) > I mean: I consider myself an advanced user and I have suffered this > inconsistent problem just once (some years ago, using two hard disks with > Windows, and Hibernating and using the other to boot), but since then I haven't > been in the situation of sharing partitions. It's not very usual for the common > user then. Often the windows partitions will be mounted in Linux. > I would personally vote for, not only making this configurable by a sysconfig > variable, but make it too via YAST or some automated UI, giving very big I am against helping people enable stupid setups. You can disagree and host your own branch of yast2-power-management on the openSUSE Buildservice :-) > WARNING messages before enabling it, and also giving the warning at GRUB just > before selecting to boot into an OS and having hibernated the last time. This is not trivial and not worth the hassle. > Just my 2 cents. Thanks for all comments on the bug. Sorry if i sound harsh on this bug, but i receive such reports every few months (i just didn't want to dig out the old numbers to duplicate this one) and this all has been discussed a thousand times. It is very unlikely that i will change my mind on this one. Making this safe would require too much work, advanced users can set it in /etc/powersave/common. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.

1 0

[Bug 158573] <Tradition Chinese Font are different.
by bugzilla_noreply＠novell.com 18 Oct '06

18 Oct '06

https://bugzilla.novell.com/show_bug.cgi?id=158573 ------- Comment #38 from zsu(a)novell.com 2006-10-18 02:59 MST ------- I'm implementing the algorithm that Werner mentioned. I'll give you result asap. I had tried to improve the patch posted in Comment #25 to test four borders, but it seems that it still can't handle some glyphs in FZSongTi.ttf and sazanami-mincho.ttf. However, I'm willing to test your patch to see whether it's better or not. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.

1 0

[Bug 211340] New: GIMP installed instead of Krita by default
by bugzilla_noreply＠novell.com 18 Oct '06

18 Oct '06

https://bugzilla.novell.com/show_bug.cgi?id=211340 Summary: GIMP installed instead of Krita by default Product: openSUSE 10.2 Version: Alpha 5 Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: KDE AssignedTo: kde-maintainers(a)suse.de ReportedBy: martin.schlander(a)gmail.com QAContact: qa(a)suse.de On alpha4 krita was the default for image editing - on alpha5 the GIMP was back. Why? Krita integrates better with KDE, is more user friendly, has more than enough functionality for the vast majority of users. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.

1 3

[Bug 158573] <Tradition Chinese Font are different.
by bugzilla_noreply＠novell.com 18 Oct '06

18 Oct '06

https://bugzilla.novell.com/show_bug.cgi?id=158573 david(a)freetype.org changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |david(a)freetype.org ------- Comment #37 from david(a)freetype.org 2006-10-18 02:42 MST ------- Hello everyone, I'm pretty new here, but I'd like to make a few statements. First of all, the TrueType specification clearly wasn't designed with easy emboldening in mind, since it explicitely allows: - two contours to intersect (note: this is note the same than a single self-intersecting contour). See http://developer.apple.com/textfonts/TTRefMan/RM01/Chap1.html#intersecting - contours in arbitrary drawing directions, see the graphics in: http://developer.apple.com/textfonts/TTRefMan/RM02/Chap2.html#distinguishing note that even if all contours are oriented uniformly, you could have a reversal of the drawing direction in a composite glyph using, for example a mirroring transform (i've seen this implemented in a font to generate the reversed cyrillic R, for example) this is a lot less strict than the Postscript font design rules, which allow the emboldening algorithm to work flawlessly for any compliant font. Generally speaking, the current algorithm tries to do its job very quickly by simply "displacing" the glyph outline towards the "exterior" direction. It is quick because it doesn't try to compute new points in the outline, or see if there are intersections. And it works well in a *lot* of cases :-) it simply assumes that the glyph is wel-formed, computes its orientation, then apply the relevant displacements to all points. A general-purpose emboldening algorithm is something *very* different that must be capable of computing all intersections in the glyph (not only in each contour), and tesselate the result appropriately when these are found. This involves a lot of complex mathematics, with very subtle and hard-to-fix rounding issues; while it is possible to implement something like this, its performance will most certainly suck (witness the performance of the Cairo tesselators, where the original one is a drag and the new "optimized" one only provides massive speed-ups in complex/theorical cases, while being slower in practical ones at the moment; all this means is that writing an efficient tesselator is *hard* stuff). And consider that what we need here is considerably more difficult than what is used in Cairo, since we need to deal with Bezier arcs, not only line segments. in an ideal world, we should be able to quickly determine if a glyph is well-formed, and use the short-cut when this is the case. When note, we should be able to use the slow algorithm (when and if it exists). however, I'm for a more practical approach at the moment. I'll try to submit a patch that will do the following: - to compute the global orientation, try to compute the orientation of all 4 borders of the glyph (top/bottom/left/right) - if they all match, return the corresponding value - if only 3 of them match, return their value since it probably means a self-intersecting gizmo like the one in the FZSongTi.ttf - the only alternative is where we have 2 opposite values in equal numbers (2+2), in this case, we have a problem, and do *nothing*, at least we'll have something nicer to display. what do you think about it ? It's only a slightly refined heuristic that doesn't force us to actually compute overlaps/intersections, but I hope it should be enough for the curious cases we're seeing. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.

1 0