April 2009 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 497407] New: zypper up -t patch does not install patches
by bugzilla_noreply＠novell.com 01 May '09

01 May '09

http://bugzilla.novell.com/show_bug.cgi?id=497407 Summary: zypper up -t patch does not install patches Classification: openSUSE Product: openSUSE 11.1 Version: Final Platform: x86 OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: libzypp AssignedTo: zypp-maintainers(a)forge.provo.novell.com ReportedBy: christiandehne(a)web.de QAContact: qa(a)suse.de Found By: --- User-Agent: Mozilla/5.0 (compatible; Konqueror/4.2; Linux) KHTML/4.2.2 (like Gecko) SUSE zypper up -t patch does not install patches on my notebook, however another computer of mine is not effected by this bug. zypper lu -t patch Daten des Repositorys laden... Installierte Pakete lesen... Patches Repository | Name | Version | Kategorie | Status ---------------------+---------+---------+-------------+--------- openSUSE-11.1-Update | libpcap | 693 | recommended | Benötigt zypper up -t patch Loading repository data... Reading installed packages... Resolving package dependencies... Nothing to do. I will attach zypper.log generated by 'ZYPP_LOGFILE=zypper.log zypper -vv up -t patch' and the solvertestcase generated by 'zypper up -t patch --debug-solver' Reproducible: Always -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 13

[Bug 495786] New: icecream: input from stdin fails
by bugzilla_noreply＠novell.com 01 May '09

01 May '09

http://bugzilla.novell.com/show_bug.cgi?id=495786 Summary: icecream: input from stdin fails Classification: openSUSE Product: openSUSE 11.1 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Development AssignedTo: pth(a)novell.com ReportedBy: teheo(a)novell.com QAContact: qa(a)suse.de Found By: --- The following command fails if it doesn't hit the local gcc fast path. ie. running the following command fail only if other compile jobs are already occupying the scheduler. $ echo -e '.cfi_startproc\n.cfi_rel_offset rsp,0\n.cfi_endproc' | /usr/bin/icecc -c -xassembler -o ~/tmp/asdf.o - Input from stdin is used in kernel build to test tool chain features to select appropriate compiler flags and the success/failure of the above command being indeterministic, it often triggers full-rebuild due to command line changes. Bug exists on both 0.9.2 and 0.9.3. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 5

[Bug 381141] [multiscreen]: Panel weirdness switching between single/dual head
by bugzilla_noreply＠novell.com 30 Apr '09

30 Apr '09

1 0

[Bug 381141] [multiscreen]: Panel weirdness switching between single/dual head
by bugzilla_noreply＠novell.com 30 Apr '09

30 Apr '09

http://bugzilla.novell.com/show_bug.cgi?id=381141 User federico(a)novell.com added comment http://bugzilla.novell.com/show_bug.cgi?id=381141#c2 Federico Mena Quintero <federico(a)novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED --- Comment #2 from Federico Mena Quintero <federico(a)novell.com> 2009-04-30 15:18:01 MDT --- Hmm. AFAIK the panel currently does this: 1. Save the monitor number for each panel --- "this panel goes in monitor 0", or "monitor 1", etc. 2. If a monitor disappears, the corresponding panels get moved to another monitor (which one? I'm not sure --- probably just monitor 0). 3. If a monitor appears again, the panels should move back to it. So Magnus's problem is that (3) isn't happening. Somewhere, the panel is (re)writing its configuration to say "the panel is in monitor 0", rather than leaving "monitor 1" in the configuration. Simon's problem is that (3) happens sometimes. So, sometimes his panel configuration says "panel is in monitor 1" --- sometimes it is preserved, sometimes it isn't. I'll look for the place where the panel saves this configuration; it's probably just rewriting it at the wrong time. However, the *real* solution for this would be for the panel to not use monitor numbers (which can come and go as you add/remove monitors --- in most cases you'll just have monitors 0 and even 1, though). Instead, the panel should be able to remember explicit monitor configurations --- grep for "keying monitor configurations" in http://live.gnome.org/RandR1.2 -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 0

[Bug 438071] root owned icons on the desktop
by bugzilla_noreply＠novell.com 30 Apr '09

30 Apr '09

http://bugzilla.novell.com/show_bug.cgi?id=438071 User bphilips(a)novell.com added comment http://bugzilla.novell.com/show_bug.cgi?id=438071#c22 --- Comment #22 from Brandon Philips <bphilips(a)novell.com> 2009-04-30 15:16:36 MDT --- Will this be fixed in 11.2? -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 0

[Bug 438071] root owned icons on the desktop
by bugzilla_noreply＠novell.com 30 Apr '09

30 Apr '09

http://bugzilla.novell.com/show_bug.cgi?id=438071 User alext(a)novell.com added comment http://bugzilla.novell.com/show_bug.cgi?id=438071#c21 --- Comment #21 from Alex Tsariounov <alext(a)novell.com> 2009-04-30 15:04:46 MDT --- (In reply to comment #16) > I found the two icons on the desktop locked, and where do you think they were? > Not in the desktop folder, no, they are in /usr/share/dist/desktop-files/ You > need to use nautilus file browser as root, Ah.. Thank you! $ sudo rm /usr/share/dist/desktop-files/* -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 0

[Bug 457570] Boot of system with SATA Raid hangs in GRUB
by bugzilla_noreply＠novell.com 30 Apr '09

30 Apr '09

http://bugzilla.novell.com/show_bug.cgi?id=457570 User juhliarik(a)novell.com added comment http://bugzilla.novell.com/show_bug.cgi?id=457570#c10 Jozef Uhliarik <juhliarik(a)novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |CLOSED Resolution| |INVALID --- Comment #10 from Jozef Uhliarik <juhliarik(a)novell.com> 2009-04-30 13:14:19 MDT --- And my last comment is about the bug. In this case bug is invalid but I accept that huge number of UI components are not what the users whant. I will change it but not yet. There are more important bugs but the number of checkoxes will be decreased to 11.2 ;-) maybe there will only "Boot from" and you can select device. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 0

[Bug 457570] Boot of system with SATA Raid hangs in GRUB
by bugzilla_noreply＠novell.com 30 Apr '09

30 Apr '09

http://bugzilla.novell.com/show_bug.cgi?id=457570 User juhliarik(a)novell.com added comment http://bugzilla.novell.com/show_bug.cgi?id=457570#c9 --- Comment #9 from Jozef Uhliarik <juhliarik(a)novell.com> 2009-04-30 13:10:17 MDT --- I am sure that my comment #8 explain a lot of things. You only forgot to deselect "Write generic boot code to MBR". It is "hidden" checkbox in tab "Boot Loader Installation" -> button "Boot Loader Options". It is cause why your MBR was broken and your PC doesn't boot any OS. Next your settings were valid because all partitions were valid and only proposal take care about settings what "to guarantee" that the system is bootloable. yast2-bootloader allows "break" booting as you whish ;-) I accept that some additional warning message should be shown but playing with booting is for experts. I see basic problem in: "How to find in yast2-bootloader setting for..." I will add short serial on our wiki about how to modify bootloader settings via yast2-bootloader (special installation) and I will add ling here: http://en.opensuse.org/Bootloader (now you can find there other links about bootloader) -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 0

[Bug 487556] creation of Wrapper
by bugzilla_noreply＠novell.com 30 Apr '09

30 Apr '09

http://bugzilla.novell.com/show_bug.cgi?id=487556 Philipp Thomas <pth(a)novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 0

[Bug 461372] boost.test cause valgrind error
by bugzilla_noreply＠novell.com 30 Apr '09

30 Apr '09

http://bugzilla.novell.com/show_bug.cgi?id=461372 User pth(a)novell.com added comment http://bugzilla.novell.com/show_bug.cgi?id=461372#c5 Philipp Thomas <pth(a)novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Resolution| |FIXED --- Comment #5 from Philipp Thomas <pth(a)novell.com> 2009-04-30 13:03:39 MDT --- OK, but I'll close this bug. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 0