June 2017 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1011815] [Build 20161121] Console messages writes over YaST configuration page in terminal
by bugzilla_noreply＠novell.com 01 Jun '17

01 Jun '17

http://bugzilla.suse.com/show_bug.cgi?id=1011815 http://bugzilla.suse.com/show_bug.cgi?id=1011815#c31 Rodion Iafarov <riafarov(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |riafarov(a)suse.com --- Comment #31 from Rodion Iafarov <riafarov(a)suse.com> --- Hi all, so here is small update. I've performed tests by increasing loglevel to debug to get kernel messages. For 3 following cases we have same behavior: 1) console=tty 2) console=ttyX , where X = {1..9} 3) no console set during the boot kernel message is shown in active console. Even if for virtual console I set loglevel to 1 using dmesg, or disable the printing of messages to the console, I still get kernel messages on active console. For openQA we are thinking about using serial console only, I'm in progress of verifying possible side effects, as last defined console is linked as /dev/console. I believe current behavior is acceptable when is configured, as we explicitly say that we want kernel messages on tty, whereas it should not be default and possibly configurable per virtual console, so user could disable it for current console to avoid flood. Changing logging levels helps in most of the cases, whereas there is no guarantee that there is no flood of messages with KERN_CRIT level. As an more recent example of such issue: http://gershwin.arch.suse.de/tests/27#step/yast2_tftp/20 Note: there loglevel is set to debug. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1042182] New: ibus-sunpinyin can not pop pre-edit window to input Chinese.
by bugzilla_noreply＠novell.com 01 Jun '17

01 Jun '17

http://bugzilla.opensuse.org/show_bug.cgi?id=1042182 Bug ID: 1042182 Summary: ibus-sunpinyin can not pop pre-edit window to input Chinese. Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: All OS: All Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: qzhao(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Description of problem: In openSUSE TumbleWeed or Leap, ibus-sunpinyin can be activated, but there's no pre-edit window which let user to input Chinese charactors. Version-Release: openSUSE Tumbleweed current release How reproducible: always Steps to Reproduce: 1, install openSUSE-Tumbleweed with language Chinese/Japanese/Korean; 2, After installation, login to desktop. 4, Switch current input framework to ibus. 5, Active ibus-sunpinyin in gnome-control-center-> language&regions. 6, open a text application(say gedit), use ibus-sunpinyin to input Chinese. Actual results: ibus-sunpinyin can not input Chinese. Expected results: ibus-sunpinyin can work well. Additional info: none -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1039638] moc player gives segmentation fault
by bugzilla_noreply＠novell.com 01 Jun '17

01 Jun '17

http://bugzilla.suse.com/show_bug.cgi?id=1039638 http://bugzilla.suse.com/show_bug.cgi?id=1039638#c2 Ian Jones <i22a(a)yahoo.co.uk> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED Flags|needinfo?(i22a(a)yahoo.co.uk) | --- Comment #2 from Ian Jones <i22a(a)yahoo.co.uk> --- Yes it is working now. I will close the bug. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1042042] New: Could not log in after last update
by bugzilla_noreply＠novell.com 01 Jun '17

01 Jun '17

http://bugzilla.opensuse.org/show_bug.cgi?id=1042042 Bug ID: 1042042 Summary: Could not log in after last update Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: 64bit OS: Other Status: NEW Severity: Major Priority: P5 - None Component: KDE Workspace (Plasma) Assignee: opensuse-kde-bugs(a)opensuse.org Reporter: aegoreev(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Hello, I updated the system last night and left it running overnight. This morning when I came back I was not able to log in. I typed in the password, pressed Enter and nothing happened. I tried many times. Password is 100% correct. Hard reset helped but I don't like doing this. I went to Yast - System log but it was empty. Please let me know if you want me to provide any specific logs to track the issue down. Thanks for reading. Andrius -- You are receiving this mail because: You are on the CC list for the bug.

1 10

[Bug 1042040] New: Education/OpenBoard: Needs to link to the Qt5 version of quazip
by bugzilla_noreply＠novell.com 01 Jun '17

01 Jun '17

http://bugzilla.opensuse.org/show_bug.cgi?id=1042040 Bug ID: 1042040 Summary: Education/OpenBoard: Needs to link to the Qt5 version of quazip Classification: openSUSE Product: openSUSE.org Version: unspecified Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: 3rd party software Assignee: mrueckert(a)suse.com Reporter: cfeck(a)kde.org QA Contact: opensuse-communityscreening(a)forge.provo.novell.com Found By: --- Blocker: --- Already report on the mailing list, but there was no action since then. http://opensuse.14.x6.nabble.com/OpenBoard-1-3-4-now-available-as-package-t… -- You are receiving this mail because: You are on the CC list for the bug.

1 5

[Bug 1039700] [Build 0243] hanging system within plasma session
by bugzilla_noreply＠novell.com 01 Jun '17

01 Jun '17

http://bugzilla.suse.com/show_bug.cgi?id=1039700 http://bugzilla.suse.com/show_bug.cgi?id=1039700#c15 Oliver Kurz <okurz(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?, | |needinfo?(tiwai(a)suse.com) --- Comment #15 from Oliver Kurz <okurz(a)suse.com> --- Now I let the system run over night and it's stuck in the locking screen, the mouse cursor still moves. So I collected a back trace on kwin_x11 instead. Full output is available in http://susepaste.org/30285788 . What looks suspiciuous to me now is the following section ``` Thread 1 (Thread 0x7fd02c168940 (LWP 2883)): #0 0x00007fd02b8c349d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x00007fd02aa473e2 in poll (__timeout=-1, __nfds=1, __fds=0x7ffc275fefe0) at /usr/include/bits/poll2.h:46 #2 _xcb_conn_wait (c=c@entry=0x1be81b0, cond=cond@entry=0x7ffc275ff100, vector=vector@entry=0x0, count=count@entry=0x0) at xcb_conn.c:459 #3 0x00007fd02aa48d1f in wait_for_reply (c=c@entry=0x1be81b0, request=request@entry=76426, e=e@entry=0x7ffc275ff1c8) at xcb_in.c:516 #4 0x00007fd02aa48e92 in xcb_wait_for_reply64 (c=c@entry=0x1be81b0, request=76426, e=e@entry=0x7ffc275ff1c8) at xcb_in.c:560 #5 0x00007fd0224ff110 in _XReply (dpy=dpy@entry=0x1be6f50, rep=rep@entry=0x7ffc275ff240, extra=extra@entry=0, discard=discard@entry=0) at xcb_io.c:596 #6 0x00007fd02146ede3 in DRI2GetBuffersWithFormat (dpy=0x1be6f50, drawable=50331657, width=width@entry=0x1e95f48, height=height@entry=0x1e95f4c, attachments=0x7ffc275ff320, count=1, outCount=outCount@entry=0x7ffc275ff31c) at dri2.c:491 #7 0x00007fd02146f0eb in dri2GetBuffersWithFormat (driDrawable=<optimized out>, width=0x1e95f48, height=0x1e95f4c, attachments=<optimized out>, count=<optimized out>, out_count=0x7ffc275ff31c, loaderPrivate=0x1e47ce0) at dri2_glx.c:894 #8 0x00007fd00c88342a in intel_query_dri2_buffers (buffer_count=0x7ffc275ff31c, buffers=<synthetic pointer>, drawable=0x1e95f20, brw=0x7fd00bc43040) at brw_context.c:1575 #9 intel_update_dri2_buffers (drawable=0x1e95f20, brw=0x7fd00bc43040) at brw_context.c:1413 #10 intel_update_renderbuffers (context=context@entry=0x1df4ed0, drawable=drawable@entry=0x1e95f20) at brw_context.c:1469 #11 0x00007fd00c88386f in intel_prepare_render (brw=brw@entry=0x7fd00bc43040) at brw_context.c:1488 #12 0x00007fd00c884719 in brw_try_draw_prims (indirect=0x0, stream=0, xfb_obj=0x0, max_index=4294967295, min_index=4294967295, index_bounds_valid=false, ib=0x7ffc275ff470, nr_prims=1, prims=0x7ffc275ff490, arrays=0x20ea638, ctx=0x7fd00bc43040) at brw_draw.c:478 #13 brw_draw_prims (ctx=0x7fd00bc43040, prims=0x7ffc275ff490, nr_prims=1, ib=0x7ffc275ff470, index_bounds_valid=<optimized out>, min_index=4294967295, max_index=4294967295, gl_xfb_obj=0x0, stream=0, indirect=0x0) at brw_draw.c:688 ``` so is it about the Intel graphics driver after all? Takashi, can you please take a second look here? -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1041742] Filetriggers do not fire (reliably)
by bugzilla_noreply＠novell.com 01 Jun '17

01 Jun '17

http://bugzilla.suse.com/show_bug.cgi?id=1041742 http://bugzilla.suse.com/show_bug.cgi?id=1041742#c8 --- Comment #8 from Dominique Leuenberger <dimstar(a)opensuse.org> --- In this case we need a way to clearly make sure that transfiletriggers are NOT supported in openSUSE - making clear what sideffects / errors it will have. Preferably rpmbuild will fail on a .spec file with a transfiletrigger linking to the doc )or we will get fun bug reports at one time - just like this one) -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1041099] Max user processes limit is reached easily with Chromium
by bugzilla_noreply＠novell.com 01 Jun '17

01 Jun '17

http://bugzilla.suse.com/show_bug.cgi?id=1041099 http://bugzilla.suse.com/show_bug.cgi?id=1041099#c1 --- Comment #1 from Tomáš Chvátal <tchvatal(a)suse.com> --- What I can see is that the limit for them is 4096. max user processes (-u) 4096 Also I don't think this is chromium bug. Something must loop on your system. ATM I have open 4 chromium windows each with at least 20 tabs and I get 800 running processes for the whole user. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1026910] freetds-devel missing libtdsodbc.so.0.0.0
by bugzilla_noreply＠novell.com 01 Jun '17

01 Jun '17

http://bugzilla.suse.com/show_bug.cgi?id=1026910 Tomáš Chvátal <tchvatal(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1042080] X11:Bumblebee/nvidia-bumblebee: current version broken for kernel 4.11.x
by bugzilla_noreply＠novell.com 01 Jun '17

01 Jun '17

http://bugzilla.suse.com/show_bug.cgi?id=1042080 http://bugzilla.suse.com/show_bug.cgi?id=1042080#c1 Tomáš Chvátal <tchvatal(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #1 from Tomáš Chvátal <tchvatal(a)suse.com> --- As submission to the project was included I am closing this bug. -- You are receiving this mail because: You are on the CC list for the bug.

1 0