May 2017 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 983221] system fails to load dm-* modules after kernel/lvm2 updates
by bugzilla_noreply＠novell.com 04 May '17

04 May '17

http://bugzilla.suse.com/show_bug.cgi?id=983221 http://bugzilla.suse.com/show_bug.cgi?id=983221#c34 zhen ren <zren(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- See Also| |http://bugzilla.suse.com/sh | |ow_bug.cgi?id=1026707 --- Comment #34 from zhen ren <zren(a)suse.com> --- *** Bug 1026707 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

[Bug 1037475] backintime-qt4 does not start on missing module error
by bugzilla_noreply＠novell.com 04 May '17

04 May '17

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

1 0

[Bug 1033198] mtr crashes in libncurses
by bugzilla_noreply＠novell.com 04 May '17

04 May '17

http://bugzilla.suse.com/show_bug.cgi?id=1033198 http://bugzilla.suse.com/show_bug.cgi?id=1033198#c16 --- Comment #16 from Gary Ching-Pang Lin <glin(a)suse.com> --- I encountered the similar crash with cscope, so I updated ncurses from Base:System. Now cscope works as expected. However, mutt starts to crash :-( The backtrace of "gdb mutt": Program received signal SIGSEGV, Segmentation fault. _nc_init_acs_sp (sp=sp@entry=0x55555588aad0) at ../ncurses/tinfo/lib_acs.c:95 95 real_map[j] = 0; (gdb) bt #0 0x00007ffff797ec72 in _nc_init_acs_sp (sp=sp@entry=0x55555588aad0) at ../ncurses/tinfo/lib_acs.c:95 #1 0x00007ffff7bbb775 in _nc_setupscreen_sp (spp=spp@entry=0x7fffffffd478, slines=<optimized out>, scolumns=<optimized out>, output=output@entry=0x7ffff65875e0 <_IO_2_1_stdout_>, filtered=<optimized out>, slk_format=slk_format@entry=0) at ../ncurses/base/lib_set_term.c:587 #2 0x00007ffff7bb6c21 in newterm_sp (sp=<optimized out>, name=name@entry=0x7fffffffeafc "xterm-256color", ofp=<optimized out>, ifp=<optimized out>) at ../ncurses/base/lib_newterm.c:222 #3 0x00007ffff7bb715c in newterm (name=name@entry=0x7fffffffeafc "xterm-256color", ofp=<optimized out>, ifp=<optimized out>) at ../ncurses/base/lib_newterm.c:352 #4 0x00007ffff7bb2c86 in initscr () at ../ncurses/base/lib_initscr.c:89 #5 0x000055555556cfdd in start_curses () at main.c:147 #6 0x000055555556cfdd in main (argc=1, argv=0x7fffffffdda8) at main.c:412 (gdb) p real_map[0] Cannot access memory at address 0x80ffff00 (gdb) p real_map $1 = (chtype *) 0x80ffff00 (gdb) -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1036356] Missing docker dependencies
by bugzilla_noreply＠novell.com 03 May '17

03 May '17

http://bugzilla.suse.com/show_bug.cgi?id=1036356 http://bugzilla.suse.com/show_bug.cgi?id=1036356#c7 --- Comment #7 from Alexandre Vicenzi <vicenzi.alexandre(a)gmail.com> --- (In reply to Jordi Massaguer from comment #5) > About runc, coreos had a similar issue and the problem was fixed by > specifying the commit when building > > https://github.com/coreos/coreos-overlay/pull/2428/commits/ > a0294fbf2caf5f1a04651a22bb67357969f5831f > > There is a similar issue in RedHat bugzilla. The warning is harmless but the > thing is that docker checks whether you are using their docker runc binary > built with a very specific commit. > > If this is not causing you an issue, we can fix that in the next docker > update. There's no problem, I can use docker with these warnings. I was just curious about these logs. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1036356] Missing docker dependencies
by bugzilla_noreply＠novell.com 03 May '17

03 May '17

http://bugzilla.suse.com/show_bug.cgi?id=1036356 http://bugzilla.suse.com/show_bug.cgi?id=1036356#c6 --- Comment #6 from Alexandre Vicenzi <vicenzi.alexandre(a)gmail.com> --- (In reply to Jordi Massaguer from comment #4) > the runc issue is more concerning. > > Can you give us the output of: > > rpm -qa | grep docker docker-libnetwork-0.0.0+git20161019.0f53435-1.1.x86_64 docker-compose-1.8.1-1.1.noarch docker-bash-completion-1.13.0-2.1.noarch docker-image-migrator-1.0.2-2.4.x86_64 docker-zsh-completion-1.13.0-2.1.noarch python-dockerpty-0.4.1-1.2.noarch docker-1.13.0-2.1.x86_64 python-docker-pycreds-0.2.1-3.1.noarch python-docker-py-1.10.6-1.1.noarch > rpm -qa | grep runc runc-0.1.1+gitr2942_2f7393a-2.1.x86_64 > > ls -l /usr/bin/docker-runc lrwxrwxrwx 1 root root 12 abr 17 06:04 /usr/bin/docker-runc -> ../sbin/runc > ls -l /usr/sbin/runc -rwxr-xr-x 1 root root 4996288 abr 17 06:04 /usr/sbin/runc > > runc --version runc version spec: 1.0.0-rc2-dev > > I see it is also a warning. Is this causing you some real issue? I mean, are > you able to run your docker images even the warning? As far as I know everything is working. Didn't had any problem with docker. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1035601] System will freeze when watching video randomly
by bugzilla_noreply＠novell.com 03 May '17

03 May '17

http://bugzilla.suse.com/show_bug.cgi?id=1035601 http://bugzilla.suse.com/show_bug.cgi?id=1035601#c36 --- Comment #36 from Borislav Petkov <bpetkov(a)suse.com> --- No, that's some ubuntu apport-<something> file which can regenerate the stack trace but I'd need the full environment for that and so on and so on. So instead please consider doing comment #26. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1036998] New: Intel Centrino Advanced-N 6235 detects wifi nets but cannot connect
by bugzilla_noreply＠novell.com 03 May '17

03 May '17

http://bugzilla.suse.com/show_bug.cgi?id=1036998 Bug ID: 1036998 Summary: Intel Centrino Advanced-N 6235 detects wifi nets but cannot connect Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.2 Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-maintainers(a)forge.provo.novell.com Reporter: eliwap(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- I am using opensuse 42.2 installed and fully updated kernerl version is .4.57-18.3-default. The network card on my laptop is a Intel Centrino Advanced-N 6235 Network Manager is able to detect WIFI networks, but is unable to connect to anyone of them. I tried a Kubuntu 17.04 live DVD and I was able to connect to my home network without issue. I have no idea how to go about diagnosing the issue. I would be very happy to participate in anyway I can to track down and help resolve this problem Thanks -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1037291] VirtualBox fails to start VMs "Kernel driver not installed (rc=-1908)" and then VERR_SUPDRV_COMPONENT_NOT_FOUND
by bugzilla_noreply＠novell.com 03 May '17

03 May '17

http://bugzilla.suse.com/show_bug.cgi?id=1037291 http://bugzilla.suse.com/show_bug.cgi?id=1037291#c1 Larry Finger <Larry.Finger(a)lwfinger.net> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |IN_PROGRESS --- Comment #1 from Larry Finger <Larry.Finger(a)lwfinger.net> --- You have several problems. 1. Sometime between snapshots 20170407 and 20170414, Tumbleweed stopped starting VB from the sysv init scripts in /etc/init.d/, even though this code has worked on every previous version of openSUSE. 2. When you manually modprobed vboxdrv, you failed to get all the routines needed to operate the network. A better command is "sudo modprobe -av vboxnetflt vboxnetadp vboxpci" That will load all the modules. Your network problem is due to the vboxnet* modules not being loaded. 3. The openSUSE implementation is missing /sbin/vboxconfig as you noted. Unfortunately, that file would not have helped you. A version of VB is now building (https://build.opensuse.org/request/show/492163) that fixes all of the above problems. To fix #1 and #2, systemd service files have been created, thus the sysv to systemd conversion routines are not needed. The new routine will load all the drivers. For #3, /sbin/vboxconfig is created. In addition, that routine will be called automatically by the systemd service for those cases that the kernel fails to match the module versions, thus the user should never see the popup telling them to run the script as it will already have been run. I have no idea how long it will take until the new code is published. The TW snapshot method takes longer than the update methods of Leap 42.1 and 42.2. My request was submitted 4 days ago. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1035601] System will freeze when watching video randomly
by bugzilla_noreply＠novell.com 03 May '17

03 May '17

http://bugzilla.suse.com/show_bug.cgi?id=1035601 http://bugzilla.suse.com/show_bug.cgi?id=1035601#c35 --- Comment #35 from miko sabor <mixalhs194858(a)gmail.com> --- Created attachment 723667 --> http://bugzilla.suse.com/attachment.cgi?id=723667&action=edit maybe that? maybe that? -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1031606] [Build 20170324][s390x] Calling the YaST module 'inst_desktop_roles' has failed'
by bugzilla_noreply＠novell.com 03 May '17

03 May '17

http://bugzilla.suse.com/show_bug.cgi?id=1031606 http://bugzilla.suse.com/show_bug.cgi?id=1031606#c7 --- Comment #7 from Stefan Hundhammer <shundhammer(a)suse.com> --- This is stuck in NEEDINFO. Matthias, can you answer Josef's question? If not, that's also ok, but then let's please get rid of that NEEDINFO state. Is this still a problem after those 4 weeks, or has it fixed itself in a newer build with newer packages? -- You are receiving this mail because: You are on the CC list for the bug.

1 0