February 2015 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 897910] Searching is broken in YaST package manager when using gtk interface
by bugzilla_noreply＠novell.com 02 Feb '15

02 Feb '15

http://bugzilla.novell.com/show_bug.cgi?id=897910 Thomas Göttlicher <tgoettlicher(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |tgoettlicher(a)suse.com Assignee|tgoettlicher(a)suse.com |yast2-maintainers(a)suse.de -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 849730] New: Yast package manager on LIVE image exits after refreshing sources
by bugzilla_noreply＠novell.com 02 Feb '15

02 Feb '15

https://bugzilla.novell.com/show_bug.cgi?id=849730 https://bugzilla.novell.com/show_bug.cgi?id=849730#c0 Summary: Yast package manager on LIVE image exits after refreshing sources Classification: openSUSE Product: openSUSE 13.1 Version: Final Platform: x86-64 OS/Version: SUSE Other Status: NEW Severity: Normal Priority: P5 - None Component: Live Medium AssignedTo: coolo(a)suse.com ReportedBy: cus(a)fazekas.hu QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0 Whenever I start the yast package manager on the Gnome LIVE image, it exists after refreshing the sources. Reproducible: Always Steps to Reproduce: 1. Boot from LIVE image 2. Start Package Manager 3. The package manager unexpectedly exits after refreshing live sources Actual Results: Package mangager exits. Expected Results: Package manager shows the detailed package manager window. Yast repository management and console zypper works. -- 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.

1 5

[Bug 915736] spamd service unit does not have a reload action
by bugzilla_noreply＠novell.com 02 Feb '15

02 Feb '15

http://bugzilla.novell.com/show_bug.cgi?id=915736 --- Comment #2 from Bernhard Wiedemann <bwiedemann(a)suse.com> --- This is an autogenerated message for OBS integration: This bug (915736) was mentioned in https://build.opensuse.org/request/show/283720 13.2+13.1 / spamassassin -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 816739] Problems with 4096 byte sector size
by bugzilla_noreply＠novell.com 02 Feb '15

02 Feb '15

http://bugzilla.suse.com/show_bug.cgi?id=816739 Michael Chang <mchang(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|CONFIRMED |RESOLVED Resolution|--- |WONTFIX --- Comment #2 from Michael Chang <mchang(a)suse.com> --- Won't fix, as os-prober itself worked fine. The problem was some tools not able to handle 4096 bytes and could be harmless for the result. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 914967] kernel: " Failed to start Login Service"
by bugzilla_noreply＠novell.com 02 Feb '15

02 Feb '15

http://bugzilla.suse.com/show_bug.cgi?id=914967 --- Comment #9 from Dr. Werner Fink <werner(a)suse.com> --- (In reply to Walther Pelser from comment #8) Hmmm ... the file /etc/dbus-1/system.d/org.freedesktop.login1.conf is marked as %config(noreplace) due to the fact that we want to avoid that every update will override the users added configurations in this file. That is after an update the new file should be installed as /etc/dbus-1/system.d/org.freedesktop.login1.conf.rpmnew compare with less +/noreplace /usr/share/doc/packages/rpm/manual/spec ...nevertheless I'd like to know *how* and/or *which* package had changed the line <allow own="org.freedesktop.login1"/> to <allow own="org.freedesktop.KDE:/Qt5/"/> -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 915435] new FLTK version breaks builds
by bugzilla_noreply＠novell.com 02 Feb '15

02 Feb '15

http://bugzilla.suse.com/show_bug.cgi?id=915435 --- Comment #6 from Petr Gajdos <pgajdos(a)suse.com> --- Yep, that's it. Thanks Dominique -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 888406] Problem Install opensuse 13.3 with UEFI system
by bugzilla_noreply＠novell.com 02 Feb '15

02 Feb '15

http://bugzilla.suse.com/show_bug.cgi?id=888406 Michael Chang <mchang(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|CONFIRMED |RESOLVED Resolution|--- |INVALID --- Comment #4 from Michael Chang <mchang(a)suse.com> --- Your EFI System Partition (ESP) was not properly mounted on /boot/efi, which grub2-install requires to be there for copying files to and also generating boot entries from it. Therefore I close this as invalid, if you find anything wrong in my comment, feel free to reopen. Thanks. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 915435] new FLTK version breaks builds
by bugzilla_noreply＠novell.com 02 Feb '15

02 Feb '15

http://bugzilla.suse.com/show_bug.cgi?id=915435 --- Comment #5 from Dominique Leuenberger <dimstar(a)opensuse.org> --- (In reply to Petr Gajdos from comment #4) > Hmm, > > when I link oyranos from multimedia:color_management and fltk from factory > (e. g. to home:pgajdos), it builds. When I delete fltk then, older fltk > (without the patch) is picked. > > But that's temporary I guess. You likely build against openSUSE:Factory/snapshot (or openSUSE:Tumbleweed) - then yes, this fix did not make it there yet; openSUSE:Factory/standard has it (hence also no longer broken in Factory builds directly) -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 854353] YaST incorrectly removes UEFI boot variables on installation and kernel update.
by bugzilla_noreply＠novell.com 02 Feb '15

02 Feb '15

http://bugzilla.suse.com/show_bug.cgi?id=854353 --- Comment #8 from Michael Chang <mchang(a)suse.com> --- (In reply to Dexter Foster from comment #7) > (In reply to comment #5) > > >GRUB is simply not necessary on UEFI platforms. All that an OS installer > > >need do is to correctly write the path to the OS/OS loader into a UEFI > > >boot variable and the UEFI BIOS handles everything else. > > > > Call me a skeptic, but I very much doubt this. > > GRUB fixes the lack of a boot manager in legacy bios. UEFI includes the boot > manager, GRUB is simply redundant. No. It's not enough in many circumstance, that's why arm64 has UEFI support still working hard on grub2 port to UEFI. Another problem is you're now relying on firmware vendor to any bootloader features and that's not possible to control. Even it has the feature you have, you may have a hard time to do it twice on other firmware type (or firmware-specific loader) and that's terrible effort also in terms of integrating them, if your distribution has to support multiple arch. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 897816] libcurl: SIGSEGV after multiple calls to curl_multi_remove_handle
by bugzilla_noreply＠novell.com 02 Feb '15

02 Feb '15

1 0