February 2015 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 902359] Add profile-based proxy settings
by bugzilla_noreply＠novell.com 02 Feb '15

02 Feb '15

http://bugzilla.suse.com/show_bug.cgi?id=902359 Michal Filka <mfilka(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|mfilka(a)suse.com |mvidner(a)suse.com --- Comment #4 from Michal Filka <mfilka(a)suse.com> --- Well, there is problem that you run NetworkManager and set proxy via yast. It can be considered to be workaround for NetworkManager not being able to set proxy on his own (?) Anyway, reassigning to yast2-proxy maintainer -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 901511] unable to search by package name
by bugzilla_noreply＠novell.com 02 Feb '15

02 Feb '15

http://bugzilla.suse.com/show_bug.cgi?id=901511 --- Comment #9 from Guido Berhoerster <gber(a)opensuse.org> --- (In reply to Ancor Gonzalez Sosa from comment #8) > It's already in the 13.2 release notes since November but, in order to make > sure people is not longer confused by this issue and we can finally close > it... > > Is anybody against backporting this commit (in Factory/TW since November as > well) as maintenance update for 13.2? > https://github.com/yast/yast-yast2/commit/ > 54939c5367a9068f9e0bc2348746d6966cbdc016 > > Including maintenance@ as needinfo. If they are fine and nobody complains in > a couple of days I'll do the backport. I made an effort that two months ago, so far the YaST maintainers stance has been to keep the broken frontend and thereby to ignore that people run into bugs and report them here, which I find not very acceptable. See https://github.com/yast/yast-yast2/pull/302#issuecomment-64540837 and my replies. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 914911] dictionaries missing in Firefox - do not exist on system
by bugzilla_noreply＠novell.com 02 Feb '15

02 Feb '15

http://bugzilla.suse.com/show_bug.cgi?id=914911 Petr Gajdos <pgajdos(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|CONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #14 from Petr Gajdos <pgajdos(a)suse.com> --- Package submitted. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 906625] "xdg-open tool" does not open file with the filetype's "standard application"
by bugzilla_noreply＠novell.com 02 Feb '15

02 Feb '15

http://bugzilla.novell.com/show_bug.cgi?id=906625 --- Comment #13 from Swamp Workflow Management <swamp(a)suse.de> --- openSUSE-SU-2015:0191-1: An update that solves one vulnerability and has one errata is now available. Category: security (moderate) Bug References: 906625,913676 CVE References: CVE-2014-9622 Sources used: openSUSE 13.2 (src): xdg-utils-20140922-12.1 -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 901511] unable to search by package name
by bugzilla_noreply＠novell.com 02 Feb '15

02 Feb '15

http://bugzilla.suse.com/show_bug.cgi?id=901511 Ancor Gonzalez Sosa <ancor(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |ancor(a)suse.com, | |maintenance(a)opensuse.org Assignee|yast2-maintainers(a)suse.de |ancor(a)suse.com Flags| |needinfo?(maintenance@opens | |use.org) --- Comment #8 from Ancor Gonzalez Sosa <ancor(a)suse.com> --- It's already in the 13.2 release notes since November but, in order to make sure people is not longer confused by this issue and we can finally close it... Is anybody against backporting this commit (in Factory/TW since November as well) as maintenance update for 13.2? https://github.com/yast/yast-yast2/commit/54939c5367a9068f9e0bc2348746d6966… Including maintenance@ as needinfo. If they are fine and nobody complains in a couple of days I'll do the backport. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 841060] lvscan gives no output while "lvs" does
by bugzilla_noreply＠novell.com 02 Feb '15

02 Feb '15

http://bugzilla.suse.com/show_bug.cgi?id=841060 --- Comment #14 from Liuhua Wang <lwang(a)suse.com> --- (In reply to Markus Koßmann from comment #11) > <http://www.redhat.com/archives/lvm-devel/2012-August/msg00069.html> seems > to be the patch, which introduced the silent switch. > But if I understand it right silent=1 does the same thing as using the -qq > option on command line. > > The man page of lvm.conf says: > Set to 1 to suppress all non-essential tool output. > When set, display and reporting tools will still write the > requested device properties to standard output, but messages > confirming that something was or wasn't changed will be > reduced to the 'verbose' level and not appear unless -v is > supplied. > If lvscan is considered to be a "display and reporting tool" , then it's a > bug in lvscan. I think lvscan is an operation command which scan (all disks) for Logical Volumes. So it is reasonable not to output when silent=1. If you think it is needed, I can also fix the manual. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 915752] New: libreoffice crashes if ctrl+o is used while opening a file
by bugzilla_noreply＠novell.com 02 Feb '15

02 Feb '15

http://bugzilla.opensuse.org/show_bug.cgi?id=915752 Bug ID: 915752 Summary: libreoffice crashes if ctrl+o is used while opening a file Classification: openSUSE Product: openSUSE Distribution Version: 13.2 Hardware: x86-64 OS: openSUSE 13.2 Status: NEW Severity: Normal Priority: P5 - None Component: LibreOffice Assignee: bnc-team-ooo(a)forge.provo.novell.com Reporter: richlv(a)nakts.net QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Opera/9.80 (X11; Linux x86_64) Presto/2.12.388 Version/12.16 Build Identifier: kde file dialogs. try opening writer files - hit ctrl+o, click on a file, then quickly hit ctrl+o again. for me, usually after doing this for 1-4 times, libreoffice crashes. i trigger this problem accidentally several times per day, so it seems to be rather easy to do. it might be easier to trigger with larger files that take a bit longer to open, but i'm not sure about that. Reproducible: Sometimes -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 840527] Vim error when opening php files
by bugzilla_noreply＠novell.com 02 Feb '15

02 Feb '15

http://bugzilla.opensuse.org/show_bug.cgi?id=840527 Marcus Rückert <mrueckert(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|IN_PROGRESS |RESOLVED Resolution|--- |FIXED Flags|needinfo?(mrueckert(a)suse.co | |m) | --- Comment #3 from Marcus Rückert <mrueckert(a)suse.com> --- looks like it. (at least after deleting some php related things in ~/.vim/) -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[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.suse.com/show_bug.cgi?id=897910 Ancor Gonzalez Sosa <ancor(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED CC| |ancor(a)suse.com Resolution|--- |DUPLICATE --- Comment #2 from Ancor Gonzalez Sosa <ancor(a)suse.com> --- As discussed on bug#901511, of which this one can be considered a duplicate, the GTK+ YaST front-end was deprecated/dropped in 13.2 and Tumbleweed. *** This bug has been marked as a duplicate of bug 901511 *** -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 901511] unable to search by package name
by bugzilla_noreply＠novell.com 02 Feb '15

02 Feb '15

http://bugzilla.suse.com/show_bug.cgi?id=901511 Ancor Gonzalez Sosa <ancor(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |badshah400(a)gmail.com --- Comment #7 from Ancor Gonzalez Sosa <ancor(a)suse.com> --- *** Bug 897910 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are on the CC list for the bug.

1 0