November 2016 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 996848] [Build 0166] Deleting "quiet splash=silent" from grub line during installation in "Booting" section has no effect
by bugzilla_noreply＠novell.com 03 Nov '16

03 Nov '16

http://bugzilla.opensuse.org/show_bug.cgi?id=996848 http://bugzilla.opensuse.org/show_bug.cgi?id=996848#c6 --- Comment #6 from Oliver Kurz <okurz(a)suse.com> --- I will take a look into this. Please be patient for just a bit :-) -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1008191] Openning Format cell dialog takes a long time
by bugzilla_noreply＠novell.com 03 Nov '16

03 Nov '16

http://bugzilla.suse.com/show_bug.cgi?id=1008191 Chenzi Cao <chcao(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|bnc-team-screening(a)forge.pr |tchvatal(a)suse.com |ovo.novell.com | -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1008211] chromium update wants to uninstall chromium-desktop-gnome
by bugzilla_noreply＠novell.com 03 Nov '16

03 Nov '16

http://bugzilla.suse.com/show_bug.cgi?id=1008211 http://bugzilla.suse.com/show_bug.cgi?id=1008211#c2 George Anchev <studio(a)anchev.net> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|WORKSFORME |--- --- Comment #2 from George Anchev <studio(a)anchev.net> --- (In reply to Tomáš Chvátal from comment #1) > Yes. The chromium by default use autodetection of the keyring present on the > system. The gnome/kde desktop ones just simply hardcoded kwalled and > gnome-keyring in there. > > It is really not needed, even in case both of the packages are on the system > the chromium checks which one is running and binds itself to it... Sorry to reopen but I need a little clarification here: On my system I use Plasma but for chromium I do (and prefer to) use gnome keyring (with seahorse) because this allows me to use separate keyrings for different applications (what kwallet cannot do). >From what you say I understand that if I uninstall chromium-desktop-gnome then chromium will autodetect kde and use kwallet instead (which is not what I want). What is the way to continue using Plasma but with gnome keyring for chromium? -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 935027] New: Enable CONFIG_EFI_MIXED
by bugzilla_noreply＠novell.com 03 Nov '16

03 Nov '16

http://bugzilla.suse.com/show_bug.cgi?id=935027 Bug ID: 935027 Summary: Enable CONFIG_EFI_MIXED Classification: openSUSE Product: openSUSE Factory Version: 201505* Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-maintainers(a)forge.provo.novell.com Reporter: kukuk(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- CONFIG_EFI_MIXED is disabled in SLE and openSUSE. Even if we official don't support systems with a 32bit EFI firmware, there are consumer machines out there which have them. Since we still ship a grub2 capable of booting machines with a pure 32bit EFI firmware, I did run into a lot of problems since CONFIG_EFI_MIXED was disabled: - YaST does not detect that this is a EFI system - efibootmgr cannot access EFI variables - wlan driver did not work - reboot does not work And most likely quite some more. I don't know which disadvantages this option has, but could we please enable it at least for openSUSE? -- You are receiving this mail because: You are on the CC list for the bug.

1 6

[Bug 1004917] [doc]
by bugzilla_noreply＠novell.com 03 Nov '16

03 Nov '16

http://bugzilla.suse.com/show_bug.cgi?id=1004917 http://bugzilla.suse.com/show_bug.cgi?id=1004917#c3 --- Comment #3 from Dmitri Popov <dmitri.popov(a)suse.com> --- Hi Tomas, Yep, I contribute to LPM, and I'm really happy to hear that you find my articles useful. :-) Thank you for your kind words and clarification. You do have a point there. I'm trying to find the best possible wording. According to Tuxera: "Please note that using setuid-root can result unforeseen privilege escalation and its usage is discouraged. Only the absolutely trusted users must be granted such access." So this is not a sensible option. So I'm thinking of replacing this sentence: To mount a Windows partition as a normal user, proceed as follows with: Since under normal conditions the unprivileged user can not mount NTFS block devices using the external FUSE library, the following steps require root privileges. How does this sound? Best, Dmitri -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 955343] plasmashell does not start on dual-monitor
by bugzilla_noreply＠novell.com 03 Nov '16

03 Nov '16

http://bugzilla.suse.com/show_bug.cgi?id=955343 http://bugzilla.suse.com/show_bug.cgi?id=955343#c1 Christoph G <foss(a)grueninger.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P5 - None |P3 - Medium CC| |foss(a)grueninger.de --- Comment #1 from Christoph G <foss(a)grueninger.de> --- I can confirm this behavior with openSuse 42.2 RC2, too. There is a KDE bug https://bugs.kde.org/show_bug.cgi?id=353975 and they claim the problem is gone with plasma 5.8. But for me the error persists. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1008266] New: VUL-0: CVE-2016-7420: cryptopp: Library documentation lacks treatment of -DNDEBUG and Static Initialization
by bugzilla_noreply＠novell.com 03 Nov '16

03 Nov '16

http://bugzilla.suse.com/show_bug.cgi?id=1008266 Bug ID: 1008266 Summary: VUL-0: CVE-2016-7420: cryptopp: Library documentation lacks treatment of -DNDEBUG and Static Initialization Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.1 Hardware: Other OS: Other Status: NEW Severity: Minor Priority: P5 - None Component: Security Assignee: pascal.bleser(a)opensuse.org Reporter: astieger(a)suse.com QA Contact: qa-bugs(a)suse.de CC: meissner(a)suse.com, pascal.bleser(a)opensuse.org, security-team(a)suse.de Found By: Security Response Team Blocker: --- CVE-2016-7420 is a procedural finding due to external build systems failing to define NDEBUG for release builds. The gap was the project's failure to tell users to define NDEBUG. References: https://bugzilla.redhat.com/show_bug.cgi?id=1376696 http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2016-7420 http://seclists.org/oss-sec/2016/q3/520 http://www.openwall.com/lists/oss-security/2015/11/10/12 http://seclists.org/oss-sec/2016/q3/559 http://seclists.org/oss-sec/2016/q3/527 http://seclists.org/oss-sec/2016/q3/600 http://people.canonical.com/~ubuntu-security/cve/2016/CVE-2016-7420.html http://www.cvedetails.com/cve/CVE-2016-7420/ http://github.com/weidai11/cryptopp/commit/823bc93357da32a3a4a2b71b9915a4e1… -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1008211] chromium update wants to uninstall chromium-desktop-gnome
by bugzilla_noreply＠novell.com 03 Nov '16

03 Nov '16

http://bugzilla.suse.com/show_bug.cgi?id=1008211 http://bugzilla.suse.com/show_bug.cgi?id=1008211#c1 Tomáš Chvátal <tchvatal(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |WORKSFORME --- Comment #1 from Tomáš Chvátal <tchvatal(a)suse.com> --- Yes. The chromium by default use autodetection of the keyring present on the system. The gnome/kde desktop ones just simply hardcoded kwalled and gnome-keyring in there. It is really not needed, even in case both of the packages are on the system the chromium checks which one is running and binds itself to it... -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 997179] Plasma 5 freeze
by bugzilla_noreply＠novell.com 03 Nov '16

03 Nov '16

http://bugzilla.suse.com/show_bug.cgi?id=997179 http://bugzilla.suse.com/show_bug.cgi?id=997179#c3 --- Comment #3 from Christoph G <foss(a)grueninger.de> --- I will do, thanks for the suggestions. But for the last two weeks, there was no such crash. Maybe that's luck, maybe the reason has been fixed. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1008262] New: gnome-session randomly crashed in _gtk_style_provider_private_get_settings (provider=0x0) at gtkstyleproviderprivate.c:123
by bugzilla_noreply＠novell.com 03 Nov '16

03 Nov '16

http://bugzilla.opensuse.org/show_bug.cgi?id=1008262 Bug ID: 1008262 Summary: gnome-session randomly crashed in _gtk_style_provider_private_get_settings (provider=0x0) at gtkstyleproviderprivate.c:123 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: GNOME Assignee: bnc-team-gnome(a)forge.provo.novell.com Reporter: martin.liska(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- gnome-shell --version GNOME Shell 3.22.1 marxin@marxinbox:~> coredumpctl gdb 19795 PID: 19795 (gnome-session-f) UID: 1000 (marxin) GID: 100 (users) Signal: 11 (SEGV) Timestamp: Thu 2016-11-03 10:08:43 CET (57s ago) Command Line: /usr/lib/gnome-session-failed --debug --allow-logout Executable: /usr/lib/gnome-session-failed Control Group: /user.slice/user-1000.slice/session-1.scope Unit: session-1.scope Slice: user-1000.slice Session: 1 Owner UID: 1000 (marxin) Boot ID: 0b94ce0c80734102afa1c52341023b58 Machine ID: 016627c3c4784cd4812d4b7e96a34226 Hostname: marxinbox Coredump: /var/lib/systemd/coredump/core.gnome-session-f.1000.0b94ce0c80734102afa1c52341023b58.19795.1478164123000000.xz Message: Process 19795 (gnome-session-f) of user 1000 dumped core. GNU gdb (GDB; openSUSE Tumbleweed) 7.11.1 Copyright (C) 2016 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "x86_64-suse-linux". Type "show configuration" for configuration details. For bug reporting instructions, please see: <http://bugs.opensuse.org/>. Find the GDB manual and other documentation resources online at: <http://www.gnu.org/software/gdb/documentation/>. For help, type "help". Type "apropos word" to search for commands related to "word"... Reading symbols from /usr/lib/gnome-session-failed...(no debugging symbols found)...done. warning: core file may not match specified executable file. [New LWP 19795] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib64/libthread_db.so.1". Core was generated by `/usr/lib/gnome-session-failed --debug --allow-logout'. Program terminated with signal SIGSEGV, Segmentation fault. #0 0x00007efebd6c8ca9 in _gtk_style_provider_private_get_settings (provider=0x0) at gtkstyleproviderprivate.c:123 123 gtkstyleproviderprivate.c: No such file or directory. Missing separate debuginfos, use: zypper install gnome-session-core-debuginfo-3.22.1-1.1.x86_64 (gdb) bt #0 0x00007efebd6c8ca9 in _gtk_style_provider_private_get_settings (provider=0x0) at gtkstyleproviderprivate.c:123 #1 0x00007efebd5650d8 in gtk_css_value_initial_compute (value=<optimized out>, property_id=1, provider=0x0, style=0x1876020, parent_style=0x0) at gtkcssinitialvalue.c:52 #2 0x00007efebd57a154 in gtk_css_static_style_compute_value (style=0x1876020, provider=<optimized out>, parent_style=<optimized out>, id=1, specified=0x7efebdce8200 <inherit>, section=0x0) at gtkcssstaticstyle.c:237 #3 0x00007efebd56640c in _gtk_css_lookup_resolve (lookup=lookup@entry=0x1874800, provider=provider@entry=0x0, style=style@entry=0x1876020, parent_style=parent_style@entry=0x0) at gtkcsslookup.c:122 #4 0x00007efebd57a07c in gtk_css_static_style_new_compute (provider=provider@entry=0x0, matcher=matcher@entry=0x0, parent=parent@entry=0x0) at gtkcssstaticstyle.c:195 #5 0x00007efebd57a0d5 in gtk_css_static_style_get_default () at gtkcssstaticstyle.c:164 #6 0x00007efebd566d72 in gtk_css_node_init (cssnode=0x1861e90) at gtkcssnode.c:663 #7 0x00007efebcec2c6f in g_type_create_instance () at /usr/lib64/libgobject-2.0.so.0 #8 0x00007efebcea4b5b in () at /usr/lib64/libgobject-2.0.so.0 #9 0x00007efebcea656d in g_object_newv () at /usr/lib64/libgobject-2.0.so.0 #10 0x00007efebcea6d24 in g_object_new () at /usr/lib64/libgobject-2.0.so.0 #11 0x00007efebd5825ba in gtk_css_widget_node_new (widget=widget@entry=0x1872380) at gtkcsswidgetnode.c:301 #12 0x00007efebd75fc87 in gtk_widget_init (instance=0x1872380, g_class=0x1871210) at gtkwidget.c:4407 #13 0x00007efebcec2c6f in g_type_create_instance () at /usr/lib64/libgobject-2.0.so.0 #14 0x00007efebcea4b5b in () at /usr/lib64/libgobject-2.0.so.0 #15 0x00007efebcea656d in g_object_newv () at /usr/lib64/libgobject-2.0.so.0 #16 0x00007efebcea6d24 in g_object_new () at /usr/lib64/libgobject-2.0.so.0 #17 0x0000000000402003 in () #18 0x00007efebc7fa291 in __libc_start_main (main=0x401f50, argc=3, argv=0x7fff486f9b88, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7fff486f9b78) at ../csu/libc-start.c:289 #19 0x000000000040240a in () -- You are receiving this mail because: You are on the CC list for the bug.

1 1