May 2019 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1133720] Canon LIDE30 + sane / xsane: cannot scan more than one page
by bugzilla_noreply＠novell.com 02 May '19

02 May '19

http://bugzilla.suse.com/show_bug.cgi?id=1133720 http://bugzilla.suse.com/show_bug.cgi?id=1133720#c11 --- Comment #11 from robert spitzenpfeil <madworm_de.novell(a)spitzenpfeil.org> --- Works with tumbleweed. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1029527] zypper outputs the message: "warning: Unsupported version of key: V3"
by bugzilla_noreply＠novell.com 02 May '19

02 May '19

http://bugzilla.suse.com/show_bug.cgi?id=1029527 http://bugzilla.suse.com/show_bug.cgi?id=1029527#c11 --- Comment #11 from Přemysl Vrba <vrbap(a)email.cz> --- Hi, I have a new information about this strange error: V3. I have tried to upgrade system to tumbleweed again. Before this, I have rebuilded a rpm database with the rpmdb --rebulddb command. It finished without error, so I have update first and second from problematic packages, xrefres with the zypper up xrefresh and then zypper up xkill command. Both of them finished without error. I have continued with zypper dup. The first V3 error occured, when package alevt was upgraded. It is the next problematic package in a row, so I have finished this upgrade with choosing "ignore" option at all next problems. Again. A rpm command refuse to delete some of old packages. I have forced zypper to install rpm package from opensuse-42.3-update-oss repository (break all necessary dependencies), version 4.11.?? and there was no problem with removing old problematic packages with rpm -e problematic_package-exact-version. Then I have installed new rpm and run zypper verify command. Malfunctions with deleting packages disappear, but when I have tried to substitute a wine package installed from opensuse-tumbleweed repository a few hours ago with a wine-staging package, rpm version 4.14 refused to delete the package wine with V3 error. So I have repeated this exercise with rpm packages several times, always rpm from opensuse-42.3 repostiory works, but one from opensuse-tumbleweed repository fail. I have checked public certificates with rpm -vv -qf /etc command and there was one old V3 certificate. I have deleted it and rpm stops work entirely (version from opensuse-tumbleweed). Every using of this application finished with SIGSEG fault. Distribution 42.3 is upgraded to last version from repositories. Zypper claims, there are some packages newer than equal packages from opensuse-tumbleweed repository. There are next possibilities how to upgrade this distribution, but only a few now. I have a lot of configuration in this distribution, I don't want to find all of them, backup them, and reinstall distribution entirely. Installation system on CD is not working with LVM snapped and/or mirrored partitions. It can not recognize them, so automatic moving of configurations is not possible. May be, a solution is to lock rpm package at version 4.11.??. I am sorry for bothering You. Preema -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1134001] New: ant-apache-bsf - Optional apache bsf tasks for ant is incorrect
by bugzilla_noreply＠novell.com 02 May '19

02 May '19

http://bugzilla.opensuse.org/show_bug.cgi?id=1134001 Bug ID: 1134001 Summary: ant-apache-bsf - Optional apache bsf tasks for ant is incorrect Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.0 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: osv(a)kiae.ru QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- The ant-apache-bsf - Optional apache bsf tasks for ant contains /etc/ant.d/apache-bsf file with the following content r70:/etc/ant.d # cat apache-bsf bsf ant/ant-apache-bsf this does not provide concrete scripting engines like the javascripi engine or such. This makes the user to edit then config file to add something like 70:/etc/ant.d # cat apache-bsf rhino bsf ant/ant-apache-bsf otherwise ant script tasks just do not work. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1134000] New: bsf - Bean Scripting Framework package is corrupted
by bugzilla_noreply＠novell.com 02 May '19

02 May '19

http://bugzilla.opensuse.org/show_bug.cgi?id=1134000 Bug ID: 1134000 Summary: bsf - Bean Scripting Framework package is corrupted Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.0 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: osv(a)kiae.ru QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- The bsf package is expected to contain certain Java classes that implement Bean Scripting Framework. In particular the /usr/share/java/bsf.jar is expected to contain: org/apache/bsf/engines/javascript/JavaScriptEngine.class. This corrupted /usr/share/java/bsf.jar makes some tasks failing when using ant tool. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1133997] New: Incorrect package ant-commons-logging - Optional commons logging tasks for ant
by bugzilla_noreply＠novell.com 02 May '19

02 May '19

http://bugzilla.opensuse.org/show_bug.cgi?id=1133997 Bug ID: 1133997 Summary: Incorrect package ant-commons-logging - Optional commons logging tasks for ant Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.0 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: osv(a)kiae.ru QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- The ant-commons-logging - Optional commons logging tasks for ant package installs with the following file in /etc/ant.d/commons-logging r70:/etc/ant.d # cat commons-logging jakarta-commons-logging ant/ant-commons-logging But this should be: apache-commons-logging ant/ant-commons-logging Leap 15 does not provide jakarta-commons-logging.jar, but apache-commons-logging.jar, The above inconsistency makes 'ant' unusable with tasks that need logging. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1133991] New: Kubeadm does not pull images with cri-o and ignores Proxy settings in the environment.
by bugzilla_noreply＠novell.com 02 May '19

02 May '19

http://bugzilla.opensuse.org/show_bug.cgi?id=1133991 Bug ID: 1133991 Summary: Kubeadm does not pull images with cri-o and ignores Proxy settings in the environment. Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kubic Assignee: kubic-bugs(a)opensuse.org Reporter: m.sammeth(a)fis-asp.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Kubeadm init can not pull the images via proxy server which is configured through /etc/sysconfig/proxy While it knows that a proxy is set because it says that the own IP and the container network is going through a proxy and explicitly warns about that it will still not pull the kubernetes container with cri-o. I had additionally to con.figure the environment in /etc/sysconfig/crio which is loaded by crio.service. Then the Images could be pulled correctly. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1131208] kernel:stable 5.0.11, non-fatal trace: "RIP: 0010:__sbitmap_queue_get_shallow+0x85/0xb0"
by bugzilla_noreply＠novell.com 02 May '19

02 May '19

1 0

[Bug 1131208] kernel:stable 5.0.5, non-fatal trace: "RIP: 0010:__sbitmap_queue_get_shallow+0x85/0xb0"
by bugzilla_noreply＠novell.com 02 May '19

02 May '19

http://bugzilla.suse.com/show_bug.cgi?id=1131208 http://bugzilla.suse.com/show_bug.cgi?id=1131208#c2 --- Comment #2 from pgnd _ <pgnet.dev(a)gmail.com> --- (In reply to Hannes Reinecke from comment #1) > Please retest with the latest kernel update to see if the problem persists. it does. --------------------------------------- ... [ 29.986557] CPU: 2 PID: 2022 Comm: cupsd Not tainted 5.0.11-24.g07c5318-default #1 openSUSE Tumbleweed (unreleased) [ 29.986560] Hardware name: System manufacturer System Product Name/M3A78-CM, BIOS 2801 08/23/2010 [ 29.986568] RIP: 0010:__sbitmap_queue_get_shallow+0x86/0xb0 [ 29.986573] Code: 48 83 c4 08 5b 5d 41 5c c3 48 8b 53 18 65 c7 02 00 00 00 00 48 83 c4 08 5b 5d 41 5c c3 45 31 e4 85 ed 75 0a 65 44 89 20 eb 99 <0f> 0b eb 86 89 74 24 04 e8 cd 8c fa ff 31 d2 8b 74 24 04 f7 f5 48 [ 29.986576] RSP: 0018:ffffad0ac27afa28 EFLAGS: 00010282 [ 29.986580] RAX: ffff9bf8e41bff00 RBX: ffff9bf8e41bff10 RCX: ffffad0ac27afa78 [ 29.986583] RDX: 0000000000000000 RSI: 0000000000000008 RDI: ffff9bf8e41bff10 [ 29.986585] RBP: ffff9bf8e41bff10 R08: ffff9bf8e41bff10 R09: 0000000000000000 [ 29.986588] R10: 0000000000000000 R11: 0000000000001000 R12: ffff9bf8e1f33050 [ 29.986590] R13: 0000000000000000 R14: ffff9bf8e1f1ac00 R15: 0000000000000000 [ 29.986595] FS: 00007ff727557000(0000) GS:ffff9bf8e6a80000(0000) knlGS:0000000000000000 [ 29.986598] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 29.986601] CR2: 00007fab1ffe2090 CR3: 0000000223802000 CR4: 00000000000006e0 [ 29.986603] Call Trace: [ 29.986616] blk_mq_get_tag+0x263/0x2c0 [ 29.986624] ? wait_woken+0x70/0x70 [ 29.986630] blk_mq_get_request+0x332/0x450 [ 29.986635] blk_mq_make_request+0x10a/0x4b0 [ 29.986641] ? generic_make_request_checks+0x1d6/0x670 [ 29.986646] generic_make_request+0x16f/0x3e0 [ 29.986657] flush_bio_list+0x9c/0xe0 [raid1] [ 29.986665] raid1_unplug+0xc7/0xe0 [raid1] [ 29.986671] blk_flush_plug_list+0x9a/0xd0 [ 29.986678] blk_finish_plug+0x21/0x2e [ 29.986684] ext4_writepages+0x76e/0x940 [ 29.986691] ? __mark_inode_dirty+0x262/0x380 [ 29.986701] ? do_writepages+0x33/0xc0 [ 29.986707] ? mpage_map_and_submit_extent+0x4d0/0x4d0 [ 29.986712] do_writepages+0x33/0xc0 [ 29.986719] ? __generic_file_write_iter+0xf9/0x1d0 [ 29.986726] __filemap_fdatawrite_range+0xa1/0xe0 [ 29.986732] ext4_release_file+0x6c/0xa0 [ 29.986739] __fput+0xb9/0x220 [ 29.986746] task_work_run+0xa1/0xc0 [ 29.986753] exit_to_usermode_loop+0xf9/0x100 [ 29.986759] do_syscall_64+0xe2/0x110 [ 29.986767] entry_SYSCALL_64_after_hwframe+0x49/0xbe [ 29.986772] RIP: 0033:0x7ff726177f14 [ 29.986776] Code: 00 f7 d8 64 89 02 48 c7 c0 ff ff ff ff eb b7 0f 1f 80 00 00 00 00 8b 05 da c4 20 00 48 63 ff 85 c0 75 13 b8 03 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 44 f3 c3 66 90 48 83 ec 18 48 89 7c 24 08 e8 [ 29.986779] RSP: 002b:00007ffc45058e48 EFLAGS: 00000246 ORIG_RAX: 0000000000000003 [ 29.986782] RAX: 0000000000000000 RBX: 000055bcde597860 RCX: 00007ff726177f14 [ 29.986785] RDX: 00007ff726161c78 RSI: 00007ff725f2f6d0 RDI: 0000000000000005 [ 29.986787] RBP: 0000000000000077 R08: 000055bcde597860 R09: 0000000000000000 [ 29.986789] R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000005 [ 29.986792] R13: 0000000000000000 R14: 0000000000000001 R15: 000055bcde57b924 [ 29.986797] ---[ end trace bfa6be3539631aa1 ]--- ... --------------------------------------- -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1133290] LTO: vlc build fails
by bugzilla_noreply＠novell.com 02 May '19

02 May '19

http://bugzilla.suse.com/show_bug.cgi?id=1133290 http://bugzilla.suse.com/show_bug.cgi?id=1133290#c1 --- Comment #1 from Swamp Workflow Management <swamp(a)suse.de> --- This is an autogenerated message for OBS integration: This bug (1133290) was mentioned in https://build.opensuse.org/request/show/700173 Factory / vlc https://build.opensuse.org/request/show/700175 15.1 / vlc -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1133897] New: repeated kernel crashing on Intel GM965
by bugzilla_noreply＠novell.com 02 May '19

02 May '19

http://bugzilla.opensuse.org/show_bug.cgi?id=1133897 Bug ID: 1133897 Summary: repeated kernel crashing on Intel GM965 Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.1 Hardware: Other OS: Other Status: NEW Severity: Major Priority: P5 - None Component: Kernel Assignee: kernel-maintainers(a)forge.provo.novell.com Reporter: mrmazda(a)earthlink.net QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 804001 --> http://bugzilla.opensuse.org/attachment.cgi?id=804001&action=edit y2logs System: Host: bernp Kernel: 4.12.14-lp151.24-default x86_64 bits: 64 compiler: gcc v: 7.4.0 parameters: root=LABEL=fu200s151 ipv6.disable=1 net.ifnames=0 noresume vga=791 video=1280x800@60 drm.debug=0x1e log_buf_len=1M 3 Desktop: IceWM 1.4.2 info: icewmtray dm: startx Distro: openSUSE Leap 15.1 Machine: Type: Laptop System: Sony product: VGN-CR290E v: R5360986 serial: 28399244-3000212 Chassis: type: 10 serial: N/A Mobo: Sony model: VAIO serial: N/A BIOS: Phoenix v: R1080Q0 date: 09/21/2007 Battery: ID-1: BAT1 charge: 41.1 Wh condition: 41.1/53.3 Wh (77%) volts: 3.9/11.1 model: Sony Corp. VGP-BPS9 type: Li-ion serial: 15474 status: Full CPU: Dual Core: Intel Core2 Duo T7500 type: MCP arch: Core Merom speed: 798 MHz min/max: 800/2201 MHz Graphics: Device-1: Intel Mobile GM965/GL960 Integrated Graphics vendor: Sony driver: i915 v: kernel bus ID: 00:02.0 chip ID: 8086:2a02 Display: server: X.Org 1.20.3 driver: modesetting alternate: fbdev,intel,vesa resolution: 1280x800~60Hz Message: Unable to show advanced data. Required tool glxinfo missing. Network: Device-1: Intel PRO/Wireless 4965 AG or AGN [Kedron] Network driver: iwl4965 v: in-tree: port: 1c00 bus ID: 02:00.0 chip ID: 8086:4229 Device-2: Realtek RTL8101/2/6E PCI Express Fast Ethernet vendor: Sony driver: r8169 v: 2.3LK-NAPI port: 4000 bus ID: 06:00.0 chip ID: 10ec:8136 Drives: Local Storage: total: 186.31 GiB used: 1.95 GiB (1.0%) Info: Processes: 107 Uptime: N/A Memory: 1.93 GiB used: 189.5 MiB (9.6%) Init: systemd v: 234 runlevel: 3 target: multi-user.target Compilers: gcc: N/A Shell: bash v: 4.4.23 running in: xterm inxi: 3.0.34 Booting to multi-user it's hard to tell when boot completes due to the debris on vtty1. Switching to other vttys works as expected, as does startx IceWM, but it takes an unusually long time to reach a desktop, and there's a significant pause running inxi in xterm. -- You are receiving this mail because: You are on the CC list for the bug.

1 12