--1462886711.1caa0.32083
Date: Tue, 10 May 2016 13:25:11 +0000
MIME-Version: 1.0
Content-Type: text/plain

http://bugzilla.opensuse.org/show_bug.cgi?id=979278

            Bug ID: 979278
           Summary: Missing stable sound backports up to 4.6
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 42.1
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Sound
          Assignee: tiwai-at-suse.com
          Reporter: tiwai-at-suse.com
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

A few commits for sound stuff are missing in stable 4.1.x tree, but can be
backported to Leap kernel individually:

ALSA: hda - Add dock support for ThinkPad X260
  037e119738120c1cdc460c6ae33871c3000531f3
ALSA: hda - Apply fix for white noise on Asus N550JV, too
  83a9efb5b8170b7cffef4f62656656e1d8ad2ccd
ALSA: hda - Asus N750JV external subwoofer fixup
  70cf2cbd685e218c3ffd105d9fb6cf0f8d767481
ALSA: hda - Fix broken reconfig
  addacd801e1638f41d659cb53b9b73fc14322cb1
ALSA: hda - Fix headphone mic input on a few Dell ALC293 machines
  c04017ea81dc1eccae87be7ac7b82b2972f9931f
ALSA: hda - Fix subwoofer pin on ASUS N751 and N551
  3231e2053eaeee70bdfb216a78a30f11e88e2243
ALSA: hda - Fix white noise on Asus N750JV headphone
  9d4dc5840f93bcb002fa311693349deae7702bc5
ALSA: hda - Fix white noise on Asus UX501VW headset
  2da2dc9ead232f25601404335cca13c0f722d41b
ALSA: hda/realtek - Add ALC3234 headset mode for Optiplex 9020m
  afecb146d8d8a60a1dde9cdf570c278649617fde
ALSA: hda/realtek - New codecs support for ALC234/ALC274/ALC294
  dcd4f0db6141d6bf2cb897309d5d6f53d1b1696f
ALSA: hda/realtek - New codec support of ALC225
  4231430da9607fb2eb7ea92f3b93ceef3bc2ed93
ALSA: hda/realtek - Support headset mode for ALC225
  4cc9b9d627af2c443cf98e651e3738d84f991cec
ALSA: pcxhr: Fix missing mutex unlock
  67f3754b51f22b18c4820fb84062f658c30e8644
ALSA: usb-audio: Quirk for yet another Phoenix Audio devices (v2)
  2d2c038a9999f423e820d89db2b5d7774b67ba49


body:
--1462890795.A7Bb0.19008
Date: Tue, 10 May 2016 14:33:15 +0000
MIME-Version: 1.0
Content-Type: text/plain

http://bugzilla.novell.com/show_bug.cgi?id=979301

            Bug ID: 979301
           Summary: Update of several KDE packages with Yast or Apper needs too much time
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: KDE Workspace (Plasma)
          Assignee: opensuse-kde-bugs-at-opensuse.org
          Reporter: w.pelser-at-web.de
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

Created attachment 676383
  --> http://bugzilla.novell.com/attachment.cgi?id=676383&action=edit
part of systemd-journal opened by Yast (screenshot)

Since a few weeks update of several KDE packages as amrok, akonadi-serever,
k3b, some libs of kde4, KDE-pim and others require ca. 4 min each. You can hear
the hard-disk working all the time.
Update of KDE framework5 can need more than half an hour because there are a
few packages with this long installation time.
Same thing with Yast or Apper.
It seems to happen only with KDE packages, but I’m not completely sure.

I have made three attachments to show the very big amount of time, which is
needed to erase an old package and to install a new one, for example here with
installation of amarok.

pkgs: amarok calligra kdepim-runtime kdevelop4 kile kmymoney


body:
--1462952317.D7F433.12253
Date: Wed, 11 May 2016 07:38:37 +0000
MIME-Version: 1.0
Content-Type: text/plain

http://bugzilla.suse.com/show_bug.cgi?id=979421

            Bug ID: 979421
           Summary: sntp command line syntax has changed
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: 13.2
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: YaST2
          Assignee: yast2-maintainers-at-suse.de
          Reporter: max-at-suse.com
        QA Contact: jsrain-at-suse.com
                CC: ancor-at-suse.com, behlert-at-suse.com,
                    Knut.Anderssen-at-suse.com, max-at-suse.com,
                    mvidner-at-suse.com, rw-at-suse.com, schubi-at-suse.com
            Blocks: 979416
          Found By: ---
           Blocker: ---

We also need this change for OpenSUSE 13.2.

+++ This bug was initially created as a clone of Bug #916617 (SLE11) +++
+++ Other clones are bug #937837 (SLE12) and bug #979416 (SLE10) +++

With the upgrade of ntp to 4.2.8 the command line syntax of sntp has changed
quite heavily. Unfortunately even some of the old switches got reused for a
different purpose.

In the install system /usr/share/YaST2/clients/ntp-client_proposal.ycp should
now call sntp with these options:

sntp -S -c '%1'

-S causes the time to be set via the settimeofday() syscall
-c causes all IP addresses to which %1 resolves to be queried in parallel

If it is also desired to silence the "Cannot open KoD db file" warning that
appears by default, the following option can be set in addition:

-K /dev/null

The same applies to /usr/share/YaST2/modules/NtpClient.ycp.

summary: sntp command line syntax has changed


--1462978305.4efA5eE0.18025
Date: Wed, 11 May 2016 14:51:45 +0000
MIME-Version: 1.0
Content-Type: text/plain

http://bugzilla.opensuse.org/show_bug.cgi?id=979524

            Bug ID: 979524
           Summary: server:database/mariadb: why handlersocket plugin is removed?
    Classification: openSUSE
           Product: openSUSE.org
           Version: unspecified
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: 3rd party software
          Assignee: kstreitova-at-suse.com
          Reporter: novell@tower-net.de
        QA Contact: opensuse-communityscreening-at-forge.provo.novell.com
          Found By: ---
           Blocker: ---

Hi,

is there a reason why you remove the handlersocket plugin in your mariadb
builds?
First you enable it to build and then you simply do a "rm ...handlersocket.so".

See https://mariadb.com/kb/en/mariadb/handlersocket/


--1463056847.6744FDbA0.26366
Date: Thu, 12 May 2016 12:40:47 +0000
MIME-Version: 1.0
Content-Type: text/plain

http://bugzilla.opensuse.org/show_bug.cgi?id=979702

            Bug ID: 979702
           Summary: Endless loop at resuming from ALSA dmix plugin
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Sound
          Assignee: tiwai-at-suse.com
          Reporter: tiwai-at-suse.com
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

alsa-lib dmix PCM has a bug at suspend / resume.  The resume doesn't work
properly, so applications like aplay may trigger the resume endlessly.

The bug was introduced in the commit 8985742d91dbdd74b2f605374207473393454fff
  pcm: dmix: Handle slave PCM xrun and unexpected states properly
and fixed recently.

The affected version is alsa-lib 1.1.0.


--1463064171.4E123.24332
Date: Thu, 12 May 2016 14:42:50 +0000
MIME-Version: 1.0
Content-Type: text/plain

http://bugzilla.suse.com/show_bug.cgi?id=979728

            Bug ID: 979728
           Summary: kernel: unplug of USB stick makes systemd-udev trigger an Oops
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 42.1
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Kernel
          Assignee: kernel-maintainers-at-forge.provo.novell.com
          Reporter: pwieczorkiewicz-at-suse.com
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

May 12 16:00:35 linux-3kv5 kernel: usb-storage 3-7.1:1.0: USB Mass Storage
device detected
May 12 16:00:35 linux-3kv5 kernel: scsi host8: usb-storage 3-7.1:1.0
May 12 16:00:35 linux-3kv5 kernel: usbcore: registered new interface driver
usb-storage
May 12 16:00:35 linux-3kv5 kernel: usbcore: registered new interface driver uas
May 12 16:00:36 linux-3kv5 kernel: scsi 8:0:0:0: Direct-Access     Kingston
DataTraveler 3.0 PMAP PQ: 0 ANSI: 6
May 12 16:00:36 linux-3kv5 kernel: sd 8:0:0:0: Attached scsi generic sg3 type 0
May 12 16:00:36 linux-3kv5 kernel: SFW2-INext-DROP-DEFLT IN=brsuse OUT=
PHYSIN=eth0.301 MAC=33:33:00:00:00:fb:90:b1:1
May 12 16:00:37 linux-3kv5 kernel: sd 8:0:0:0: [sdc] 61457664 512-byte logical
blocks: (31.5 GB/29.3 GiB)
May 12 16:00:37 linux-3kv5 kernel: sd 8:0:0:0: [sdc] Write Protect is off
May 12 16:00:37 linux-3kv5 kernel: sd 8:0:0:0: [sdc] Mode Sense: 23 00 00 00
May 12 16:00:37 linux-3kv5 kernel: sd 8:0:0:0: [sdc] No Caching mode page found
May 12 16:00:37 linux-3kv5 kernel: sd 8:0:0:0: [sdc] Assuming drive cache:
write through
May 12 16:00:37 linux-3kv5 kernel:  sdc: sdc1
May 12 16:00:37 linux-3kv5 kernel: sd 8:0:0:0: [sdc] Attached SCSI removable
disk
May 12 16:00:41 linux-3kv5 kernel: usb 3-7.1: USB disconnect, device number 48
May 12 16:00:41 linux-3kv5 systemd-udevd[13416]: inotify_add_watch(7, /dev/sdc,
10) failed: No such file or directory
May 12 16:00:42 linux-3kv5 kernel: BUG: unable to handle kernel paging request
at ffffebe004004000
May 12 16:00:42 linux-3kv5 kernel: IP: [<ffffffff811c2aed>] kfree+0x6d/0x2b0
May 12 16:00:42 linux-3kv5 kernel: PGD 0
May 12 16:00:42 linux-3kv5 kernel: Oops: 0000 [#1] PREEMPT SMP
May 12 16:00:42 linux-3kv5 kernel: Modules linked in: uas usb_storage dm_mod
binfmt_misc qat_1_6_mux(O) qat_mux(O) fu
May 12 16:00:42 linux-3kv5 kernel:  coretemp snd_hda_codec snd_hda_core
snd_hwdep kvm_intel snd_pcm kvm btrfs crct10d
May 12 16:00:42 linux-3kv5 kernel: CPU: 0 PID: 13416 Comm: systemd-udevd
Tainted: G           O    4.1.20-11-default
May 12 16:00:42 linux-3kv5 kernel: Hardware name: Dell Inc. Precision Tower
5810/0K240Y, BIOS A09 09/26/2015
May 12 16:00:42 linux-3kv5 kernel: task: ffff880140d1e2d0 ti: ffff880004420000
task.ti: ffff880004420000
May 12 16:00:42 linux-3kv5 kernel: RIP: 0010:[<ffffffff811c2aed>]
[<ffffffff811c2aed>] kfree+0x6d/0x2b0
May 12 16:00:42 linux-3kv5 kernel: RSP: 0018:ffff880004423c28  EFLAGS: 00010086
May 12 16:00:42 linux-3kv5 kernel: RAX: ffffebe004004000 RBX: 0000000000000202
RCX: ffffea0000000000
May 12 16:00:42 linux-3kv5 kernel: RDX: 0000000180100123 RSI: 0000000000000286
RDI: 0000000100100123
May 12 16:00:42 linux-3kv5 kernel: RBP: 0000000100100123 R08: ffff880004420000
R09: 00000000000001de
May 12 16:00:42 linux-3kv5 kernel: R10: 0000000000000008 R11: 0000000000000010
R12: ffffffffa0073fad
May 12 16:00:42 linux-3kv5 kernel: R13: ffff88014101a000 R14: ffff8802a8c91b58
R15: 000000000002005d
May 12 16:00:42 linux-3kv5 kernel: FS:  00007fe6745d3880(0000)
GS:ffff8804bfc00000(0000) knlGS:0000000000000000
May 12 16:00:42 linux-3kv5 kernel: CS:  0010 DS: 0000 ES: 0000 CR0:
0000000080050033
May 12 16:00:42 linux-3kv5 kernel: CR2: ffffebe004004000 CR3: 00000000157ff000
CR4: 00000000001406f0
May 12 16:00:42 linux-3kv5 kernel: Stack:
May 12 16:00:42 linux-3kv5 kernel:  ffff880131b01680 ffff8802e196dc00
000000000002005d 0000000000000001
May 12 16:00:42 linux-3kv5 kernel:  ffff8802e196dda0 ffff88049e3b8800
0000000000000001 ffff88049e3b8800
May 12 16:00:42 linux-3kv5 kernel:  ffff88049e3b8800 ffff8804aa4b7400
ffff88014101a000 ffff8802a8c91b58
May 12 16:00:42 linux-3kv5 kernel: Call Trace:
May 12 16:00:42 linux-3kv5 kernel:  [<ffffffffa0073fad>]
usb_release_bos_descriptor+0x1d/0x40 [usbcore]
May 12 16:00:42 linux-3kv5 kernel:  [<ffffffffa0060347>]
usb_release_dev+0x27/0x60 [usbcore]
May 12 16:00:42 linux-3kv5 kernel:  [<ffffffff81482ecd>]
device_release+0x2d/0xa0
May 12 16:00:42 linux-3kv5 kernel:  [<ffffffff8135d5c2>]
kobject_cleanup+0x72/0x1a0
May 12 16:00:42 linux-3kv5 kernel:  [<ffffffffa006f14c>]
usb_release_interface+0x2c/0x50 [usbcore]
May 12 16:00:42 linux-3kv5 kernel:  [<ffffffff81482ecd>]
device_release+0x2d/0xa0
May 12 16:00:42 linux-3kv5 kernel:  [<ffffffff8135d5c2>]
kobject_cleanup+0x72/0x1a0
May 12 16:00:42 linux-3kv5 kernel:  [<ffffffff814ae1ab>]
scsi_host_dev_release+0xcb/0x100
May 12 16:00:42 linux-3kv5 kernel:  [<ffffffff81482ecd>]
device_release+0x2d/0xa0
May 12 16:00:42 linux-3kv5 kernel:  [<ffffffff8135d5c2>]
kobject_cleanup+0x72/0x1a0
May 12 16:00:42 linux-3kv5 kernel:  [<ffffffff81482ecd>]
device_release+0x2d/0xa0
May 12 16:00:42 linux-3kv5 kernel:  [<ffffffff8135d5c2>]
kobject_cleanup+0x72/0x1a0
May 12 16:00:42 linux-3kv5 kernel:  [<ffffffff8108099f>]
execute_in_process_context+0x5f/0x70
May 12 16:00:42 linux-3kv5 kernel:  [<ffffffff81482ecd>]
device_release+0x2d/0xa0
May 12 16:00:42 linux-3kv5 kernel:  [<ffffffff8135d5c2>]
kobject_cleanup+0x72/0x1a0
May 12 16:00:42 linux-3kv5 kernel:  [<ffffffff814c119f>]
scsi_disk_put+0x2f/0x50
May 12 16:00:42 linux-3kv5 kernel:  [<ffffffff81217524>]
__blkdev_put+0x194/0x200
May 12 16:00:42 linux-3kv5 kernel:  [<ffffffff81217fb5>] blkdev_close+0x25/0x30
May 12 16:00:42 linux-3kv5 kernel:  [<ffffffff811e0b99>] __fput+0xb9/0x1c0
May 12 16:00:42 linux-3kv5 kernel:  [<ffffffff81085077>]
task_work_run+0xa7/0xe0
May 12 16:00:42 linux-3kv5 kernel:  [<ffffffff81002f59>]
do_notify_resume+0x69/0x90
May 12 16:00:42 linux-3kv5 kernel:  [<ffffffff81665104>] int_signal+0x12/0x17
May 12 16:00:42 linux-3kv5 kernel:  [<00007fe673747ac0>] 0x7fe673747ac0
May 12 16:00:42 linux-3kv5 kernel: Code: 00 00 00 80 ff 77 00 00 48 b9 00 00 00
00 00 ea ff ff 48 01 ea 48 0f 42 05 3
May 12 16:00:42 linux-3kv5 kernel: RIP  [<ffffffff811c2aed>] kfree+0x6d/0x2b0
May 12 16:00:43 linux-3kv5 kernel:  RSP <ffff880004423c28>
May 12 16:00:43 linux-3kv5 kernel: CR2: ffffebe004004000
May 12 16:00:43 linux-3kv5 kernel: ---[ end trace 5da93a5d2c6c621a ]---
May 12 16:00:42 linux-3kv5 systemd-udevd[479]: worker [13416] terminated by
signal 9 (Killed)
May 12 16:00:42 linux-3kv5 systemd-udevd[479]: worker [13416] failed while
handling '/devices/pci0000:00/0000:00:14.0


--1463069225.1c2B01f0.17079
Date: Thu, 12 May 2016 16:07:05 +0000
MIME-Version: 1.0
Content-Type: text/plain

http://bugzilla.suse.com/show_bug.cgi?id=979749

            Bug ID: 979749
           Summary: Error flagged up during latest zypper dup
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: x86-64
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: libzypp
          Assignee: zypp-maintainers-at-forge.provo.novell.com
          Reporter: ianseeks-at-btinternet.com
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

I ran zypper dup today on openSUSE Tumbleweed (20160511) (x86_64) and the error
below was displayed - is it anything to worry about?  I'm not sure what other
info to provide, please let me know how and what you might need.

Updating /etc/sysconfig/mdadm ...
Failed to try-restart mdmon@.service: Unit name mdmon@.service is not valid.
Failed to try-restart mdadm-last-resort@.service: Unit name mdadm-last-
resort@.service is not valid.
Failed to try-restart mdadm-grow-continue@.service: Unit name mdadm-grow-
continue@.service is not valid.


--1463128248.bA743.29584
Date: Fri, 13 May 2016 08:30:48 +0000
MIME-Version: 1.0
Content-Type: text/plain

http://bugzilla.suse.com/show_bug.cgi?id=979853

            Bug ID: 979853
           Summary: OBS build worker problems on lamb*: Hanging mounts
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 42.1
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Kernel
          Assignee: kernel-maintainers-at-forge.provo.novell.com
          Reporter: adrian-at-suse.com
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

I see hanging "umount" calls on our "lamb" workers after updating obs worker
images from 13.2 to 42.1, using current released maintenance kernel:

[41323.182015] BUG: unable to handle kernel NULL pointer dereference at
0000000000000246
[41323.190266] IP: [<ffffffff81664755>] _raw_spin_unlock_irqrestore+0x5/0x30
[41323.197261] PGD 0
[41323.199490] Oops: 0002 [#1] PREEMPT SMP
[41323.203686] Modules linked in: ipmi_devintf iscsi_ibft iscsi_boot_sysfs
ipmi_si kvm_amd kvm crct10dif_pclmul ipmi_msghandler crc32_pclmul aesni_intel
joydev sp5100_tco aes_x86_64 lrw gf128mul amd64_edac_mod glue_helper edac_core
ablk_helper edac_mce_amd fam15h_power cryptd pcspkr k10temp serio_raw shpchp
i2c_piix4 tpm_tis 8250_fintek acpi_cpufreq tpm processor sg fuse dm_mod
squashfs loop brd af_packet hid_generic usbhid ohci_pci syscopyarea sysfillrect
sysimgblt ttm ohci_hcd ehci_pci drm_kms_helper igb ehci_hcd dca ptp ata_generic
crc32c_intel usbcore pps_core drm pata_atiixp usb_common i2c_algo_bit button
[last unloaded: dm_mod]
[41323.262830] CPU: 3 PID: 17921 Comm: qemu-system-x86 Not tainted
4.1.20-11-default #1
[41323.270952] Hardware name: Supermicro H8DGT   /H8DGT   , BIOS 3.5b
10/06/2015
[41323.279001] task: ffff8807b7784510 ti: ffff8807f5ccc000 task.ti:
ffff8807f5ccc000
[41323.286842] RIP: 0010:[<ffffffff81664755>]  [<ffffffff81664755>]
_raw_spin_unlock_irqrestore+0x5/0x30
[41323.296435] RSP: 0018:ffff8807f5ccf940  EFLAGS: 00010246
[41323.301951] RAX: ffff8817f4edc218 RBX: ffff8817f4edc190 RCX:
ffff8817f4edc218
[41323.309293] RDX: ffff8817f4edc200 RSI: 0000000000000246 RDI:
0000000000000246
[41323.316625] RBP: 0000000000000001 R08: 0000000000000007 R09:
ffff8807fc6a83d0
[41323.323960] R10: 0000000000000000 R11: 0000000000000000 R12:
ffff8817f4edc190
[41323.331296] R13: 0000000000000000 R14: 0000000000000000 R15:
ffff880ff693e818
[41323.338632] FS:  0000000034859000(00d8) GS:ffff8807ffcc0000(00e0)
knlGS:0000000000000000
[41323.347098] CS:  0010 DS: 0000 ES: 0000 CR0: 000000008005003b
[41323.353035] CR2: 0000000000000246 CR3: 00000007ba649000 CR4:
00000000000406e0
[41323.360378] Stack:
[41323.362571]  ffffffffa0582069 0000000000000dce ffff8817d97ca200
0000000000000000
[41323.370424]  ffffffffa05b6601 00000000000000fd ffff8817d97ca200
0000000000000000
[41323.378310]  0000000000000000 0000000000016700 ffff8807f5ccfa44
ffff8807f5ccfa8c
[41323.386141] Call Trace:
[41323.388788]  [<ffffffffa0582069>] kvm_vcpu_kick+0x39/0xb0 [kvm]
[41323.394976]  [<ffffffffa05b6601>] __apic_accept_irq+0x321/0x330 [kvm]
[41323.401631]  [<ffffffffa05b73b2>] kvm_irq_delivery_to_apic_fast+0xf2/0x290
[kvm]
[41323.409447]  [<ffffffffa05bb1b4>] kvm_irq_delivery_to_apic+0x54/0x250 [kvm]
[41323.416632]  [<ffffffffa05b68b6>] apic_reg_write+0x106/0x680 [kvm]
[41323.423014]  [<ffffffffa05b6edb>] apic_mmio_write+0x6b/0x80 [kvm]
[41323.429390]  [<ffffffffa058dec1>] write_mmio+0x41/0x120 [kvm]
[41323.435332]  [<ffffffffa058f50e>] emulator_read_write_onepage+0xde/0x340
[kvm]
[41323.442999]  [<ffffffffa058f834>] emulator_read_write+0xc4/0x170 [kvm]
[41323.449727]  [<ffffffffa05afb03>] segmented_write.isra.11+0x43/0x50 [kvm]
[41323.456718]  [<ffffffffa05b02a4>] writeback+0x134/0x2d0 [kvm]
[41323.462664]  [<ffffffffa05b3fcf>] x86_emulate_insn+0x6ef/0xe00 [kvm]
[41323.469277]  [<ffffffffa05997ed>] x86_emulate_instruction+0x1cd/0x720 [kvm]
[41323.476438]  [<ffffffffa05a2676>] kvm_mmu_page_fault+0x76/0x140 [kvm]
[41323.483121]  [<ffffffffa0596c57>] vcpu_enter_guest+0x937/0xef0 [kvm]
[41323.489735]  [<ffffffffa059d84d>] kvm_arch_vcpu_ioctl_run+0x2bd/0x430 [kvm]
[41323.496898]  [<ffffffffa0586429>] kvm_vcpu_ioctl+0x329/0x620 [kvm]
[41323.503336]  [<ffffffff811f218f>] do_vfs_ioctl+0x2ff/0x510
[41323.509016]  [<ffffffff811f2421>] SyS_ioctl+0x81/0xa0
[41323.514254]  [<ffffffff81664f32>] system_call_fastpath+0x16/0x75
[41323.520454]  [<00007f6fcecbcb87>] 0x7f6fcecbcb87
[41323.525254] Code: 90 90 90 90 90 90 66 66 66 66 90 66 83 07 01 65 ff 0d e0
62 9a 7e 74 06 c3 0f 1f 44 00 00 e8 74 45 d0 ff c3 66 90 66 66 66 66 90 <66> 83
07 01 48 89 f7 57 9d 66 66 90 66 90 65 ff 0d b6 62 9a 7e
[41323.546328] RIP  [<ffffffff81664755>] _raw_spin_unlock_irqrestore+0x5/0x30
[41323.553442]  RSP <ffff8807f5ccf940>
[41323.557125] CR2: 0000000000000246
[41323.561000] ---[ end trace 79ea05a78ef3b128 ]---


--1463163962.1E6EA00.10416
Date: Fri, 13 May 2016 18:26:02 +0000
MIME-Version: 1.0
Content-Type: text/plain

http://bugzilla.opensuse.org/show_bug.cgi?id=979981

            Bug ID: 979981
           Summary: network:time/ntp: Bug in ntp-wait.service
    Classification: openSUSE
           Product: openSUSE.org
           Version: unspecified
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: 3rd party software
          Assignee: max-at-suse.com
          Reporter: matwey.kornilov-at-gmail.com
        QA Contact: opensuse-communityscreening-at-forge.provo.novell.com
          Found By: ---
           Blocker: ---

Hello,

ntp-wait don't like floating-point sleep argument.

# /usr/sbin/ntp-wait -s 0.2 -n 30000
Value "0.2" invalid for option s (number expected)
ntp-wait - Wait for ntpd to stabilize the system clock - Ver. 4.2.8p6
USAGE: ntp-wait [ -<flag> [<val>] | --<name>[{=| }<val>] ]...

    -n, --tries=num              Number of times to check ntpd
    -s, --sleep=num              How long to sleep between tries
    -v, --verbose                Be verbose
    -?, --help                   Display usage information and exit
        --more-help              Pass the extended usage text through a pager

Whereas ntp-wait.service has the following:

[Service]
Type=oneshot
ExecStart=/usr/sbin/ntp-wait -s 0.2 -n 30000
RemainAfterExit=yes
StandardOutput=null

And then it fails as the following:

● ntp-wait.service - Wait for ntpd to synchronize system clock
   Loaded: loaded (/usr/lib/systemd/system/ntp-wait.service; enabled; vendor
preset: disabled)
   Active: failed (Result: exit-code) since Чт 1970-01-01 01:00:43 CET; 46
years 4 months ago
  Process: 927 ExecStart=/usr/sbin/ntp-wait -s 0.2 -n 30000 (code=exited,
status=1/FAILURE)
 Main PID: 927 (code=exited, status=1/FAILURE)

янв 01 01:00:42 nohostname systemd[1]: Starting Wait for ntpd to synchronize
system clock...
янв 01 01:00:43 nohostname systemd[1]: ntp-wait.service: Main process exited,
code=exited, status=1/FAILURE
янв 01 01:00:43 nohostname systemd[1]: Failed to start Wait for ntpd to
synchronize system clock.
янв 01 01:00:43 nohostname systemd[1]: ntp-wait.service: Unit entered failed
state.
янв 01 01:00:43 nohostname systemd[1]: ntp-wait.service: Failed with result
'exit-code'.


body:
--1463212612.27aB7E285.9982
Date: Sat, 14 May 2016 07:56:52 +0000
MIME-Version: 1.0
Content-Type: text/plain

http://bugzilla.opensuse.org/show_bug.cgi?id=980041

            Bug ID: 980041
           Summary: Update libstoragemgmt to version 1.3.1
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 42.1
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Basesystem
          Assignee: mpluskal-at-suse.com
          Reporter: mpluskal-at-suse.com
        QA Contact: qa-bugs-at-suse.de
                CC: cnfourt-at-gmail.com
          Found By: ---
           Blocker: ---

Latest version bring several significant improvements:
1.3.1:
  * Fix local disk querying in fakeroot(change root) when '/dev'
    is not mounted.
- Upgrade to version 1.3.0:
  * Change the raid card cache split (%read, %write)
  * Retrieve/update cache information of both the card and
    physical disks (enable/disable caching etc.)
  * Turn on/off identify and fault LEDs
  * Retrieve information on batteries
  * Retrieve a physical disk RPM, link type and location string for
    a disk
  * Retrieve the vpd 0x83 for directly attached disk(s)
  * Given a vpd 0x83 return list of local disk paths
  * Given a disk path return the vpd 0x83 value
  * Retrieve list of local disks
- Removed package:
  * libstoragemgmt-rest

summary: Update libstoragemgmt to version 1.3.1


body:
--1463326459.AFCD3.11824
Date: Sun, 15 May 2016 15:34:19 +0000
MIME-Version: 1.0
Content-Type: text/plain

http://bugzilla.opensuse.org/show_bug.cgi?id=980066

            Bug ID: 980066
           Summary: KDE Frameworks 5.22.0 released
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 42.1
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Development
          Assignee: hrvoje.senjan-at-gmail.com
          Reporter: hrvoje.senjan-at-gmail.com
        QA Contact: qa-bugs-at-suse.de
                CC: maintenance-at-opensuse.org
          Found By: ---
           Blocker: ---

https://www.kde.org/announcements/kde-frameworks-5.22.0.php

pkgs: kiconthemes krunner kwayland

summary: KDE Frameworks 5.22.0 released


body:
--1463368976.dCB0bd2f0.23597
Date: Mon, 16 May 2016 03:22:56 +0000
MIME-Version: 1.0
Content-Type: text/plain

http://bugzilla.opensuse.org/show_bug.cgi?id=980081

            Bug ID: 980081
           Summary: Apparmor tries create existing folder
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: x86-64
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: AppArmor
          Assignee: suse-beta-at-cboltz.de
          Reporter: liudas.alisauskas-at-gmail.com
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

Created attachment 676980
  --> http://bugzilla.opensuse.org/attachment.cgi?id=676980&action=edit
Apparmor error details

Apparmor tries create existing folder during boot, thus error entries are
generated in log:

--
May 16 05:45:25 HOSTNAME libapparmor[516]: Can't create cache directory
'/etc/apparmor.d/cache': File exists
--

More details in attachment.

summary: Apparmor tries create existing folder


--1463398335.1B3A6a0.10831
Date: Mon, 16 May 2016 11:32:15 +0000
MIME-Version: 1.0
Content-Type: text/plain

http://bugzilla.novell.com/show_bug.cgi?id=980124

            Bug ID: 980124
           Summary: TW20160514: Heavy flickering after x-server update on skylake architecture
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: x86-64
                OS: Other
            Status: NEW
          Severity: Critical
          Priority: P5 - None
         Component: X.Org
          Assignee: xorg-maintainer-bugs-at-forge.provo.novell.com
          Reporter: robby.engelmann@igfs-ev.de
        QA Contact: xorg-maintainer-bugs-at-forge.provo.novell.com
          Found By: ---
           Blocker: Yes

After update and rebooting the system, I gave a heavy flickering of screen
elements. Mouse cursor is painting traces and in general kinds of graphics
elements show bad repaints with flickering around like crazy.
The Desktop is almost unusable now. Thus, I activate the Pontostroy repo and
upgraded all packages from there. Now it works again without flickering.

Hardware: Tuxedo Infinity Book v2 with i7 Skylake.
True for kernel 4.5.3 from TW repo and 4.6 rc7 from kernel:head


--1463405700.12bE08Eb3.25211
Date: Mon, 16 May 2016 13:35:00 +0000
MIME-Version: 1.0
Content-Type: text/plain

http://bugzilla.opensuse.org/show_bug.cgi?id=980137

            Bug ID: 980137
           Summary: openSUSE Leap 42.1: Cannot update kernel
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 42.1
          Hardware: x86-64
                OS: openSUSE 42.1
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Kernel
          Assignee: kernel-maintainers-at-forge.provo.novell.com
          Reporter: matwey.kornilov-at-gmail.com
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

Hello,

I am facing the following issue. When I try to update kernel, it conflicts with
xtables which I would like to keep. I need xtables.

# LANG=c zypper patch
Loading repository data...
Reading installed packages...
Resolving package dependencies...

Problem: xtables-addons-kmp-default-2.8_k4.1.12_1-6.17.x86_64 requires
ksym(default:ip6_route_output) = c88b167f, but this requirement cannot be
provided
  uninstallable providers: kernel-default-4.1.12-1.1.x86_64[repo-oss]
                   kernel-default-base-4.1.12-1.1.x86_64[repo-oss]
                   kernel-default-4.1.13-5.1.x86_64[repo-update]
                   kernel-default-base-4.1.13-5.1.x86_64[repo-update]
                   kernel-default-base-4.1.15-8.1.x86_64[repo-update]
 Solution 1: deinstallation of
xtables-addons-kmp-default-2.8_k4.1.12_1-6.17.x86_64
 Solution 2: do not install patch:openSUSE-2016-445-1.noarch
 Solution 3: break xtables-addons-kmp-default-2.8_k4.1.12_1-6.17.x86_64 by
ignoring some of its dependencies

Choose from above solutions by number or cancel [1/2/3/c] (c): c


body:
--1463408736.0A3DcDe5.32301
Date: Mon, 16 May 2016 14:25:36 +0000
MIME-Version: 1.0
Content-Type: text/plain

http://bugzilla.opensuse.org/show_bug.cgi?id=980149

            Bug ID: 980149
           Summary: zopfli contains funny[tm] manpage
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: Other
                OS: openSUSE 13.2
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Basesystem
          Assignee: p.drouand-at-gmail.com
          Reporter: suse-beta-at-cboltz.de
        QA Contact: qa-bugs-at-suse.de
                CC: mpluskal-at-suse.com
          Found By: Beta-Customer
           Blocker: ---

man zopfli looks funny[tm]. Enjoy yourself (pasted below), and then please fix
it ;-)

# man zopfli

PLEASE(1)                      User Commands                      PLEASE(1)

NAME
       Please - o-info

DESCRIPTION
       Invalid filename: h

       For help, type: ./zopfli -h

SEE ALSO
       The  full  documentation for Please is maintained as a Texinfo manual.
       If the info and Please programs are properly installed at  your  site,
       the command

              info Please

       should give you access to the complete manual.

Please provide filename          April 2016                       PLEASE(1)

summary: zopfli contains funny[tm] manpage


body:
--1463409432.4d742D6.1718
Date: Mon, 16 May 2016 14:37:12 +0000
MIME-Version: 1.0
Content-Type: text/plain

http://bugzilla.opensuse.org/show_bug.cgi?id=980155

            Bug ID: 980155
           Summary: zopfli: package zopflipng PNG optimizer
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: Other
                OS: openSUSE 13.2
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Basesystem
          Assignee: p.drouand-at-gmail.com
          Reporter: suse-beta-at-cboltz.de
        QA Contact: qa-bugs-at-suse.de
                CC: mpluskal-at-suse.com, stefan.bruens@rwth-aachen.de
          Found By: Beta-Customer
           Blocker: ---

zopfli includes zopflipng, which is a quite impressive optimizer for PNG images
(see https://github.com/openSUSE/landing-page/pull/103 for an example).

Please adjust the zopfli package to also include zopflipng.

You might want to look at
https://build.opensuse.org/package/show/home:StefanBruens:branches:Archiving/zopfli
where this was already done. Unfortunately this branch has merge conflicts, but
looking at the (unmerged) .spec should show what you need. (Or Stefan can solve
the merge conflict and send a SR... ;-)

summary: zopfli: package zopflipng PNG optimizer


body:
--1463422576.Cf76CF4A1.1081
Date: Mon, 16 May 2016 18:16:16 +0000
MIME-Version: 1.0
Content-Type: text/plain

http://bugzilla.opensuse.org/show_bug.cgi?id=980196

            Bug ID: 980196
           Summary: Package request: mbedtls 2.x
    Classification: openSUSE
           Product: openSUSE.org
           Version: unspecified
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: 3rd party software
          Assignee: fisiu-at-opensuse.org
          Reporter: andy-at-onthewings.net
        QA Contact: opensuse-communityscreening-at-forge.provo.novell.com
                CC: crrodriguez-at-opensuse.org
          Found By: ---
           Blocker: ---

Currently the mbedtls package in Factory is at 1.3.16. I would like to request
for an update to 2.x.

The Neko package I'm maintaining at devel:languages:haxe/neko will requires
mbedtls 2.x for packaging its next upstream version.

summary: Package request: mbedtls 2.x


--1463430561.bfA251.23171
Date: Mon, 16 May 2016 20:29:21 +0000
MIME-Version: 1.0
Content-Type: text/plain

http://bugzilla.opensuse.org/show_bug.cgi?id=980207

            Bug ID: 980207
           Summary: Yast doesn't start 'Boot loader' or 'Kernel Settings' modules
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 42.1
          Hardware: x86-64
                OS: openSUSE 42.1
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: YaST2
          Assignee: yast2-maintainers-at-suse.de
          Reporter: wvvelzen-at-gmail.com
        QA Contact: jsrain-at-suse.com
          Found By: ---
           Blocker: ---

When I try to start the 'Boot loader' or 'Kernel Settings' module, I only get
an error window with the following content:

Internal error. Please report a bug report with logs.
Details: Unknown udev device /dev/disk/by-id/nvme-200253851615031e4-part2
Caller: /usr/share/YaST2/lib/bootloader/udev_mapping.rb:42:in
`to_kernel_device'

This is a "fresh" Leap install, and the reported 'Unknown udev device' does
indeed not exist.

The disk I'm booting from without problems is: /dev/nvme0n1


--1463482840.F1A18feC4.5877
Date: Tue, 17 May 2016 11:00:40 +0000
MIME-Version: 1.0
Content-Type: text/plain

http://bugzilla.suse.com/show_bug.cgi?id=980303

            Bug ID: 980303
           Summary: openSUSE Leap 42.1 has boot issues with encrypted partitions on NVMe after updates
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 42.1
          Hardware: x86-64
                OS: openSUSE 42.1
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Basesystem
          Assignee: bnc-team-screening-at-forge.provo.novell.com
          Reporter: sebastian.parschauer-at-suse.com
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

When installing openSUSE Leap 42.1 on an NVMe SSD with encrypted home without
networking, booting it, setting up networking, installing updates and
rebooting, then nothing asks for the decryption password any more. The boot
continues directly to asking for the user name and login password which of
cause fails as the home partition isn't decrypted yet.

It happens with the default setup with btrfs on / with encryped XFS /home and
also with ext4 on /.


--1463483806.3C6BD9.8334
Date: Tue, 17 May 2016 11:16:46 +0000
MIME-Version: 1.0
Content-Type: text/plain

http://bugzilla.suse.com/show_bug.cgi?id=980313

            Bug ID: 980313
           Summary: /usr/lib/zypp/plugins/commit/susemanager should be moved to susemanager related package and not be part of base salt-minion
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 42.1
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Other
          Assignee: bnc-team-screening-at-forge.provo.novell.com
          Reporter: mrueckert-at-suse.com
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

seen with salt-minion-2015.8.8-68.1.x86_64 from systemsmanagement:saltstack

the salt setup on the machine was turned off atm and this noticably slows down
all zypp operations. if this plugin is mostly for susemanager it shouldnt be
part of the normal salt-minion package. if it is meant to be used with normal
salt, i would recommend renaming it.


--1463486085.ba0Bf0FD4.5228
Date: Tue, 17 May 2016 11:54:45 +0000
MIME-Version: 1.0
Content-Type: text/plain

http://bugzilla.opensuse.org/show_bug.cgi?id=980325

            Bug ID: 980325
           Summary: Cannot add dependency job for unit initrd-udevadm-cleanup-db.service
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: 13.2
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Basesystem
          Assignee: bnc-team-screening-at-forge.provo.novell.com
          Reporter: per-at-computer.org
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

On a newly installed 13.2 32bit xen guest:

temp78:~ # journalctl -b -o short-precise --no-pager | grep
initrd-udevadm-cleanup
May 17 12:53:40.560991 template78 systemd[1]: Cannot add dependency job for
unit initrd-udevadm-cleanup-db.service, ignoring: Unit
initrd-udevadm-cleanup-db.service failed to load: No such file or directory.

"/usr/lib/systemd/system/initrd-udevadm-cleanup-db.service" seems to have gone
missing from udev.

On a backlevel openSUSE 13.2 system that file does exist:

sogo:~ #
rpm -qf /usr/lib/systemd/system/initrd-udevadm-cleanup-db.service
udev-210.1456152170.f2b9ea6-25.34.1.i586

On one of the patched test systems:
temp78:~ # rpm -q udev
udev-210.1459453449.5237776-25.37.1.i586


body:
Build Identifier:

NetworkManager segfaults frequently (but not always), apparently when
performing a WiFi scan. If WiFi is off (e.g. airplane mode), then the crash
does not occur.

Reproducible: Always

Steps to Reproduce:
1. Start NetworkManager.
2. Turn on WiFi.
Actual Results:
NetworkManager crashes (segfault).

GDB trace:

Program received signal SIGSEGV, Segmentation fault.
on_bss_proxy_acquired (proxy=0x8b7890, result=0x8872e0, user_data=<optimized
out>)
    at supplicant-manager/nm-supplicant-interface.c:158
158             while (*iter) {

(gdb) bt
#0  0x000000000049ef47 in on_bss_proxy_acquired (proxy=0x8b7890,
result=0x8872e0, user_data=<optimized out>) at
supplicant-manager/nm-supplicant-interface.c:158
#1  0x00007ffff5644807 in g_simple_async_result_complete ()
    at /usr/lib64/libgio-2.0.so.0
#2  0x00007ffff5644869 in  () at /usr/lib64/libgio-2.0.so.0
#3  0x00007ffff50b7b65 in g_main_context_dispatch () at
/usr/lib64/libglib-2.0.so.0
#4  0x00007ffff50b7ed8 in  () at /usr/lib64/libglib-2.0.so.0
#5  0x00007ffff50b819a in g_main_loop_run () at /usr/lib64/libglib-2.0.so.0
#6  0x000000000043bee7 in main (argc=1, argv=0x7fffffffddb8) at main.c:513

---------------------------------------

Apparently the same issue as e.g.:
https://bugzilla.redhat.com/show_bug.cgi?id=1266003
https://bugzilla.redhat.com/show_bug.cgi?id=1267462
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1547575

summary: NetworkManager segfaults while scanning WiFi networks


--1463499381.EABb3A52.14932
Date: Tue, 17 May 2016 15:36:21 +0000
MIME-Version: 1.0
Content-Type: text/plain

http://bugzilla.novell.com/show_bug.cgi?id=980382

            Bug ID: 980382
           Summary: Mesa: glXGetFBConfigs has invalid screen bounds (java3d crash)
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: X.Org
          Assignee: xorg-maintainer-bugs-at-forge.provo.novell.com
          Reporter: jslaby-at-suse.com
        QA Contact: xorg-maintainer-bugs-at-forge.provo.novell.com
          Found By: ---
           Blocker: ---

This is a local dup of upstream:
https://bugs.freedesktop.org/show_bug.cgi?id=95456


--1463499548.7b8EA1.16660
Date: Tue, 17 May 2016 15:39:08 +0000
MIME-Version: 1.0
Content-Type: text/plain

http://bugzilla.suse.com/show_bug.cgi?id=980384

            Bug ID: 980384
           Summary: Enable PIE and full relro build for firefox
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Firefox
          Assignee: bnc-team-mozilla-at-forge.provo.novell.com
          Reporter: dsterba-at-suse.com
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

Created attachment 677257
  --> http://bugzilla.suse.com/attachment.cgi?id=677257&action=edit
enable firefox PIE and full relro on x86_64

PIE (position independent code) and full relro are features that have security
implications on built binaries. The firefox browser does not have enabled them
but as it's it an exposed tool, the improvements are desirable.

Upstream builds do not enable PIE for very unconvincing reasons (because some
graphical file manager does not recigonize the binary with PIE as executable).

Firefox upstream bug: https://bugzilla.mozilla.org/show_bug.cgi?id=1076892
References: http://bugs.gw.com/view.php?id=404

I've tested build on Factory (currently 46.0), passes, binary (firefox-bin)
verified to have the mentioned features.

Attached patch enables them on x86_64. More arches can be added later.


--1463504841.06ddaf34.15770
Date: Tue, 17 May 2016 17:07:21 +0000
MIME-Version: 1.0
Content-Type: text/plain

http://bugzilla.opensuse.org/show_bug.cgi?id=980393

            Bug ID: 980393
           Summary: command-not-found (cnf) doesn't find packages anymore
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Other
          Assignee: bnc-team-screening-at-forge.provo.novell.com
          Reporter: antoine.belvire-at-laposte.net
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

cnf (command-not-found) seems broken, it doesn't find the packages which
provide the given command.

It looks like bug #951977.

I'm running openSUSE Tumbleweed (20160512) but I can't say which snapshot
introduced the problem.

It seems that there is something wrong when calling libsolv's Dataiterator in
scout's bin.py:

>    def search(self, term, inversesearch = False):
>        pkgmatch = []
>        if not inversesearch:
>            pathreprg = re.compile(self.pathre + re.escape(term) + '$')
>            # SEARCH_STRING without SEARCH_FILES matches basenames
>            for d in self.pool.Dataiterator(solv.SOLVABLE_FILELIST, term, solv.Dataiterator.SEARCH_STRING):
>                path = str(d)
>                # do matching for path
>                if not pathreprg.match(path): continue
>                row = ( 'zypp (%s)' % d.solvable.repo.name.decode('utf-8'), d.solvable.name.decode('utf-8'), path[:-len(term)-1], term )
>                if not row in pkgmatch:
>                    pkgmatch.append( row )
>        else:

Steps to reproduce:
1. Run 'cnf bash'

Expected result:
>
> Program 'bash' is present in package 'bash', which is installed on your system.
>
> Absolute path to 'bash' is '/bin/bash'. Please check your $PATH variable to see whether it contains the mentioned path.
>

Actual result:
> bash: command not found.


--1463518508.1ceCD17.12821
Date: Tue, 17 May 2016 20:55:08 +0000
MIME-Version: 1.0
Content-Type: text/plain

http://bugzilla.opensuse.org/show_bug.cgi?id=980421

            Bug ID: 980421
           Summary: gnome-shell-extension-gpaste version number incompatible with gnome-shell version in Leap
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 42.1
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: GNOME
          Assignee: bnc-team-gnome-at-forge.provo.novell.com
          Reporter: sb56637-at-gmail.com
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

Hello, the gnome-shell-extension-gpaste version number of the extension is for
Gnome Shell 3.14, and yet it is packaged for Leap, which has Gnome 3.16. I
manually changed the metadata file from 3.14 to 3.16 and it works fine.


body:
--1463542942.BDb06.11308
Date: Wed, 18 May 2016 03:42:22 +0000
MIME-Version: 1.0
Content-Type: text/plain

http://bugzilla.opensuse.org/show_bug.cgi?id=980441

            Bug ID: 980441
           Summary: gnome-boxes does not start any VM's
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: GNOME
          Assignee: bnc-team-gnome-at-forge.provo.novell.com
          Reporter: calinuswork-at-gmail.com
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

Created attachment 677303
  --> http://bugzilla.opensuse.org/attachment.cgi?id=677303&action=edit
Log for a leap 42 guest.

Steps to reproduce:

1. open gnome boxes
2. click on a vm

Expected result:

The VM should boot

Actual Result:

The busy indicator spins for a wile and then a fail to start notification
appears

Attached is the troubleshooting log for a leap 42 guest.

summary: gnome-boxes does not start any VM's


body:
--1463556233.25736.1710
Date: Wed, 18 May 2016 07:23:53 +0000
MIME-Version: 1.0
Content-Type: text/plain

http://bugzilla.opensuse.org/show_bug.cgi?id=980474

            Bug ID: 980474
           Summary: gnome-terminal occasionally segfaults
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: GNOME
          Assignee: bnc-team-gnome-at-forge.provo.novell.com
          Reporter: martin.liska-at-suse.com
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

Hi.

After I've updated my Tumbleweed to GNOME Terminal 3.20.1, the terminal crashes
times to time:

[159741.844359] gnome-terminal-[13891]: segfault at 0 ip 00007f224ff8a533 sp
00007ffd6a631c30 error 4 in libgtk-3.so.0.2000.3[7f224fc29000+6c8000]

Looks it's the same as described here:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=822736

Martin

summary: gnome-terminal occasionally segfaults


--1463582721.FB700.9802
Date: Wed, 18 May 2016 14:45:21 +0000
MIME-Version: 1.0
Content-Type: text/plain

http://bugzilla.suse.com/show_bug.cgi?id=980577

            Bug ID: 980577
           Summary: "cobbler get-loaders" doesn't resolve www.clobberd.org
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 42.1
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Basesystem
          Assignee: bnc-team-screening-at-forge.provo.novell.com
          Reporter: pablo.suarezhernandez-at-suse.com
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

ferruja:~ # cobbler get-loaders
task started: 2016-05-18_154111_get_loaders
task started (id=Download Bootloader Content, time=Wed May 18 15:41:11 2016)
downloading http://www.cobblerd.org/loaders/README to
/var/lib/cobbler/loaders/README
Exception occured: <class 'urlgrabber.grabber.URLGrabError'>
Exception value: [Errno 14] PYCURL ERROR 6 - "Could not resolve host:
www.cobblerd.org"
Exception Info:
  File "/usr/lib/python2.7/site-packages/cobbler/remote.py", line 87, in run
    rc = self._run(self)
   File "/usr/lib/python2.7/site-packages/cobbler/remote.py", line 181, in
runner
    return self.remote.api.dlcontent(self.options.get("force",False),
self.logger)
   File "/usr/lib/python2.7/site-packages/cobbler/api.py", line 751, in
dlcontent
    return grabber.run(force)
   File "/usr/lib/python2.7/site-packages/cobbler/action_dlcontent.py", line
72, in run
    urlgrabber.grabber.urlgrab(src, filename=dst, proxies=proxies)
   File "/usr/lib/python2.7/site-packages/urlgrabber/grabber.py", line 618, in
urlgrab
    return default_grabber.urlgrab(url, filename, **kwargs)
   File "/usr/lib/python2.7/site-packages/urlgrabber/grabber.py", line 982, in
urlgrab
    return self._retry(opts, retryfunc, url, filename)
   File "/usr/lib/python2.7/site-packages/urlgrabber/grabber.py", line 886, in
_retry
    r = apply(func, (opts,) + args, {})
   File "/usr/lib/python2.7/site-packages/urlgrabber/grabber.py", line 968, in
retryfunc
    fo = PyCurlFileObject(url, filename, opts)
   File "/usr/lib/python2.7/site-packages/urlgrabber/grabber.py", line 1063, in
__init__
    self._do_open()
   File "/usr/lib/python2.7/site-packages/urlgrabber/grabber.py", line 1352, in
_do_open
    self._do_grab()
   File "/usr/lib/python2.7/site-packages/urlgrabber/grabber.py", line 1482, in
_do_grab
    self._do_perform()
   File "/usr/lib/python2.7/site-packages/urlgrabber/grabber.py", line 1339, in
_do_perform
    raise err

!!! TASK FAILED !!!


--1463588455.5e10E0.30846
Date: Wed, 18 May 2016 16:20:55 +0000
MIME-Version: 1.0
Content-Type: text/plain

http://bugzilla.suse.com/show_bug.cgi?id=980596

            Bug ID: 980596
           Summary: Please allow ipv6 raw sockets for 'ping'
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: AppArmor
          Assignee: suse-beta-at-cboltz.de
          Reporter: mchandras-at-suse.com
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

Hi,

I was looking into packaging the latest iputils[1]. In that version 'ping' and
ping6 have been consolidated into a single executable which can control the
inet family using -4 or -6. Latest 'ping' will try to create both ipv4 and ipv6
sockets[2] by default. However, this is prohibited by the apparmor profile in
/etc/apparmor.d/bin.ping

With the current profile I get the following behavior:

~ $ ping -c 1 www.google.com
ping: socket: Permission denied
PING www.google.com (216.58.210.36) 56(84) bytes of data.
64 bytes from lhr14s23-in-f36.1e100.net (216.58.210.36): icmp_seq=1 ttl=56
time=23.8 ms

But an ipv4-only ping results to
~ $ ping -4 -c 1 www.google.com
PING www.google.com (216.58.210.36) 56(84) bytes of data.
64 bytes from lhr14s23-in-f36.1e100.net (216.58.210.36): icmp_seq=1 ttl=56
time=24.2 ms

Changing the profile to:

@@ -18,6 +18,7 @@
   capability net_raw,
   capability setuid,
   network inet raw,
+  network inet6 raw,

   /{,usr/}bin/ping mixr,
   /etc/modules.conf r

makes newest ping works as expected.

~ $ ping -c 1 www.google.com
PING www.google.com (216.58.210.36) 56(84) bytes of data.
64 bytes from lhr14s23-in-f36.1e100.net (216.58.210.36): icmp_seq=1 ttl=56
time=24.0 ms

Please consider updating the apparmor profile to support that. It might also
worth pushing such change to upstream as well.

[1] https://github.com/iputils/iputils/releases/tag/s20160308
[2] https://github.com/iputils/iputils/blob/master/ping.c#L446


body:
--1463642226.0fAd4BDB1.27555
Date: Thu, 19 May 2016 07:17:06 +0000
MIME-Version: 1.0
Content-Type: text/plain

http://bugzilla.opensuse.org/show_bug.cgi?id=980653

            Bug ID: 980653
           Summary: Update libstoragemgmt to version 1.3.2
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 42.1
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Basesystem
          Assignee: mpluskal-at-suse.com
          Reporter: mpluskal-at-suse.com
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

Update to version 1.3.2
* Fix local disk VPD83 searching in fakeroot(change root) when '/dev' is not
mounted.
* New configure option to skip memory leak check test.
* Fix regression introduced by 1.3.1 when run as non-root user.
* New configure option '--without-test' to skip all test cases and their build
requirements.

summary: Update libstoragemgmt to version 1.3.2


--1463647044.3Fc6dDcF1.27534
Date: Thu, 19 May 2016 08:37:24 +0000
MIME-Version: 1.0
Content-Type: text/plain

http://bugzilla.opensuse.org/show_bug.cgi?id=980663

            Bug ID: 980663
           Summary: apache systemd notify related log message
    Classification: openSUSE
           Product: openSUSE 13.1
           Version: Final
          Hardware: x86-64
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Apache
          Assignee: bnc-team-apache-at-forge.provo.novell.com
          Reporter: patrick.schaaf-at-yalwa.com
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

With the latest systemd etc. updates for 13.1 on my production
webservers, I started to get these messages, several times a day:

2016-05-12T13:13:01.494327+02:00 HOSTNAME systemd[1]: apache2.service:
Got notification message from PID 14342, but reception only permitted
for main PID 1621

Adding "NotifyAccess=all" to apache2.service [Service] section (done
locally through a dropin at the moment), seems to fix the symptom.

Maybe that could be put into apache2.service in a future package
update?


--1463671244.722e0d0.13694
Date: Thu, 19 May 2016 15:20:44 +0000
MIME-Version: 1.0
Content-Type: text/plain

http://bugzilla.opensuse.org/show_bug.cgi?id=980750

            Bug ID: 980750
           Summary: Plymouth prevents loading DRM/KMS driver for newly installed graphics card
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 42.1
          Hardware: All
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Basesystem
          Assignee: bnc-team-screening-at-forge.provo.novell.com
          Reporter: maximilian.staudt-at-suse.com
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

When changing a VGA card in an already installed system, Plymouth will prevent
its modern (DRM/KMS) kernel mode driver to be loaded.

Example:

1. Install Leap 42.1 in QEMU using the emulated Cirrus card (-vga cirrus).
2. The system boots up with a splash screen.
3. Shut down the system.
4. Start the VM, this time with the Bochs VGA card (-vga std).
5. A splash screen will be shown, but then X falls back to the VESA driver.

As a bonus, switching to a text VT (Ctrl-Alt-F1) only gives a blinking cursor.
The VT works just fine and is usable, except the user has to operate it blindly
as no video is shown.


--1463679752.7035aeBd4.4117
Date: Thu, 19 May 2016 17:42:32 +0000
MIME-Version: 1.0
Content-Type: text/plain

http://bugzilla.opensuse.org/show_bug.cgi?id=980768

            Bug ID: 980768
           Summary: magicpoint draw transparent image with strange border colors
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: X11 Applications
          Assignee: bnc-team-screening-at-forge.provo.novell.com
          Reporter: tiwai-at-suse.com
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

When drawing an image with transparent via magicpoint on a slide, it's drawn
badly with some borders in an ugly pink color.

The pink color is a side-effect of the patch to zoom with bilinear resampling.
mgp marks the transparent pixel with a fixed color in pink, but the bilinear
resampling code doesn't care but just takes the value as is.

Unfortunately, fixing this properly isn't trivial.  By the size change, one
would need the anti-aliasing of the transparent image border; i.e. we need the
proper alpha channel handling.


--1463731682.A68c1664.27963
Date: Fri, 20 May 2016 08:08:01 +0000
MIME-Version: 1.0
Content-Type: text/plain

http://bugzilla.opensuse.org/show_bug.cgi?id=980830

            Bug ID: 980830
           Summary: No sidebar available in mutt 1.6.1 from Tumbleweed snapshot 20160514
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Other
          Assignee: bnc-team-screening-at-forge.provo.novell.com
          Reporter: tbechtold-at-suse.com
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

The sidebar for mutt is gone.
$ mutt -v|grep SIDEBAR
+USE_HCACHE +USE_IMAP -USE_NOTMUCH +USE_POP +USE_SASL -USE_SETGID -USE_SIDEBAR

And compiling with "--enable-sidebar" doesn't work.


body:
--1463732483.4AF02011.29492
Date: Fri, 20 May 2016 08:21:23 +0000
MIME-Version: 1.0
Content-Type: text/plain

http://bugzilla.suse.com/show_bug.cgi?id=980834

            Bug ID: 980834
           Summary: parted with --wipesignatures fails
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Major
          Priority: P5 - None
         Component: Basesystem
          Assignee: bnc-team-screening-at-forge.provo.novell.com
          Reporter: aschnell-at-suse.com
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

I have to build util-linux and parted myself to test the new parted
option --wipesignatures.

Using parted with that option fails with the error:

# parted --script --wipesignatures /dev/sdb mkpart a ext4 1MiB 1025MiB
Error: Partition(s) 1 on /dev/sdb have been written, but we have been unable to
inform the kernel of the change, probably because it/they are in use.  As a
result, the old partition(s) will remain in use.  You should reboot now before
making further changes.

AFAIS opening and closing the disk device to run blkid_do_probe/wipe triggers
udev events that cause the device to be busy when parted wants to inform
the kernel. Adding a sleep(10) after the close in
parted-implement-wipesignatures-option.patch resolved to issue (as a
workaround).

Maybe it would be better to move the wiping to libparted and use the already
existing file descriptor to not cause extra udev events.

This bug prevents finishing fate #319893 since commiting the new code to
the libstorage repository will cause failures in openQA testing of openSUSE.

summary: parted with --wipesignatures fails


--1463825284.ABDf0.30083
Date: Sat, 21 May 2016 10:08:04 +0000
MIME-Version: 1.0
Content-Type: text/plain

http://bugzilla.opensuse.org/show_bug.cgi?id=981004

            Bug ID: 981004
           Summary: Ensure template unit instances are deleted
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: All
                OS: Linux
            Status: NEW
          Severity: Enhancement
          Priority: P5 - None
         Component: Basesystem
          Assignee: jengelh-at-inai.de
          Reporter: jengelh-at-inai.de
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

When a package is uninstalled, it will also be removed from the boot sequence,
by means of %preun generally calling %service_del_preun foo.service, which
expands to (among other things) `systemctl disable foo.service`.

To disable template instances such as foo-at-bar.service and foo-at-baz.service, one
can - and must, since "bar" and "baz" are not known at any time to the package
management system - use `systemctl disable foo@.service`, which will disable
all instances.

A number of packages are lacking the corresponding %service_del_preun
template@.service lines, which means template instance links like
foo-at-bar.service will stick around after package uninstall.

389-ds apache2 arpwatch autossh booth chrony cups device-mapper dracut envoy
freeipa govpn gpsd kmscon libteam lvm2 lvm2-clvm mariadb mdadm mgetty mysql
mysql-community-server openct openvpn parkverbot rear redis rfkill syncthing
system-config-printer systemd systemd-mini tomcat vpnc vsftpd wicked
xf86-input-wacom


--1463851198.d4B77cb61.30369
Date: Sat, 21 May 2016 17:19:58 +0000
MIME-Version: 1.0
Content-Type: text/plain

http://bugzilla.opensuse.org/show_bug.cgi?id=981008

            Bug ID: 981008
           Summary: Yast2 has no support for "Asturian (Spain, with bottom-dot H and bottom-dot L)" keyboard layout
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: x86-64
                OS: SUSE Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: YaST2
          Assignee: yast2-maintainers-at-suse.de
          Reporter: enolp-at-softastur.org
        QA Contact: jsrain-at-suse.com
          Found By: ---
           Blocker: ---

Yast2 has no support for Asturian keyboard layout so that i cannot type Ḥ - ḥ
and Ḷ - ḷ with the correct key combination, instead I get Ħ - ħ and Ł - ł
because of Spanish keyboard layout automatically set by Yast2.
OpenSUSE installer has also the same problem setting Asturian as the installer
language.

I attach a link about this keyboard layout:
https://bugs.freedesktop.org/show_bug.cgi?id=14277


--1463872747.CaE620.28923
Date: Sat, 21 May 2016 23:19:07 +0000
MIME-Version: 1.0
Content-Type: text/plain

http://bugzilla.opensuse.org/show_bug.cgi?id=981011

            Bug ID: 981011
           Summary: PackageKit dumps core during offline update
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Upgrade Problems
          Assignee: bnc-team-screening-at-forge.provo.novell.com
          Reporter: badshah400-at-gmail.com
        QA Contact: jsrain-at-suse.com
          Found By: ---
           Blocker: ---

Created attachment 677842
  --> http://bugzilla.opensuse.org/attachment.cgi?id=677842&action=edit
journalctl log for the update session

I tried to update my TW system from 20160505 to current using the PK offline
upgrades method and after rebooting into the update mode it dumped core and
hung. After manually rebooting, it booted into my old 20160505 desktop state.
Couldn't install the exact versioned debuginfos because TW rpms have moved on
since then, but both the journalctl and gdb bt from the coredump are attached
here.


--1463875733.cD54aCf17.525
Date: Sun, 22 May 2016 00:08:53 +0000
MIME-Version: 1.0
Content-Type: text/plain

http://bugzilla.opensuse.org/show_bug.cgi?id=981012

            Bug ID: 981012
           Summary: gdm: [DM] X-Server dont open tcp Port 6000 for remote use
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: x86-64
                OS: openSUSE 42.1
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: GNOME
          Assignee: badshah400-at-gmail.com
          Reporter: badshah400-at-gmail.com
        QA Contact: qa-bugs-at-suse.de
                CC: badshah400-at-gmail.com,
                    bnc-team-gnome-at-forge.provo.novell.com,
                    d.guelow-at-spsg.de, eich-at-suse.com, jmatejek-at-suse.com,
                    kde-maintainers-at-suse.de, nadvornik-at-suse.com
            Blocks: 978262
          Found By: Customer
           Blocker: ---

+++ This bug was initially created as a clone of Bug #978262 +++

Cloning for gdm.


--1463908008.Ec2a7404.13220
Date: Sun, 22 May 2016 09:06:48 +0000
MIME-Version: 1.0
Content-Type: text/plain

http://bugzilla.opensuse.org/show_bug.cgi?id=981020

            Bug ID: 981020
           Summary: gnupg segmentation fault "mpi-bit.c: No such file or directory."
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: Other
                OS: All
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Other
          Assignee: bnc-team-screening-at-forge.provo.novell.com
          Reporter: sebix+novell.com-at-sebix.at
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

Created attachment 677848
  --> http://bugzilla.opensuse.org/attachment.cgi?id=677848&action=edit
zypper.log starting from yesterday including all updates from today

After the latest upgrade today (2016-05-22) I cannot run gnupg2 anymore. I
attached the zypper logs starting from yesterday.

Thus is the output from gdb with all necessary debugging symbols installed
(those proposed by gdb).

> gdb gpg2
GNU gdb (GDB; openSUSE Tumbleweed) 7.11
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 gpg2...Reading symbols from
/usr/lib/debug/usr/bin/gpg2.debug...done.
done.
(gdb) r -k
Starting program: /usr/bin/gpg2 -k
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib64/libthread_db.so.1".
gpg: checking the trustdb
gpg: removing stale lockfile (created by 19531)

Program received signal SIGSEGV, Segmentation fault.
_gcry_mpi_normalize (a=0x0) at mpi-bit.c:61
61    mpi-bit.c: No such file or directory.

I tried to install openmpi (just a guess), but nothing changed. I also removed
libgcrypt20-32bit and other -32bit packages which have been installed because
of 1 32bit-only package.

I can't downgrade libgcrypt20 to the previous installed version too :(

> sudo zypper install -f libgcrypt20-1.6.5-1.3
root's password:
Loading repository data...
Reading installed packages...
Package 'libgcrypt20-1.6.5-1.3' not found.
Resolving package dependencies...

Nothing to do.
> sudo zypper install -f libgcrypt20=1.6.5-1.3
Loading repository data...
Reading installed packages...
Package 'libgcrypt20=1.6.5-1.3' not found.
Resolving package dependencies...

Nothing to do.

Any ideas how to downgrade (so I can use gpg again, which I need) or debug
this?


--1463935287.d8a730.16734
Date: Sun, 22 May 2016 16:41:27 +0000
MIME-Version: 1.0
Content-Type: text/plain

http://bugzilla.opensuse.org/show_bug.cgi?id=981024

            Bug ID: 981024
           Summary: ispell-american, ispell-british: remove "maintenence"
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: x86-64
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Other
          Assignee: bnc-team-screening-at-forge.provo.novell.com
          Reporter: j_k_v-at-ro.ru
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

Package: ispell-american, ispell-british
Version: 3.4.00-1.2

Both the right and the wrong spelling are in the dictionary:

> egrep -o -a -i "maintenance|maintenence" /usr/lib/ispell/british* /usr/lib/ispell/american*
/usr/lib/ispell/british.hash:MAINTENANCE
/usr/lib/ispell/british.hash:MAINTENENCE
/usr/lib/ispell/britishmed.hash:MAINTENANCE
/usr/lib/ispell/britishxlg.hash:MAINTENANCE
/usr/lib/ispell/britishxlg.hash:MAINTENENCE
/usr/lib/ispell/american.hash:MAINTENANCE
/usr/lib/ispell/american.hash:MAINTENENCE
/usr/lib/ispell/americanmed.hash:MAINTENANCE
/usr/lib/ispell/americanxlg.hash:MAINTENANCE
/usr/lib/ispell/americanxlg.hash:MAINTENENCE

Alternatively, you can start emacs, choose ispell as the spellchecker, choose
the american or british dictionary, and run ispell on it.

Please remove the wrong one "maintenence". It's not a word according to
Merriam-Webster, Oxford, and Cambridge online dictionaries.

(You can alternatively direct me upstream, but the links on
http://fmg-www.cs.ucla.edu/geoff/ispell-dictionaries.html#English-dicts are
still dead, so I still don't know where upstream is or whether it exists at all
any more. The documentation in /usr/share/doc/packages/ispell is not giving any
clue about the upstream location.)


--1463991484.e5cdf3.18568
Date: Mon, 23 May 2016 08:18:04 +0000
MIME-Version: 1.0
Content-Type: text/plain

http://bugzilla.opensuse.org/show_bug.cgi?id=981054

            Bug ID: 981054
           Summary: updating python3-websockets to version 3.1
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 42.1
          Hardware: Other
                OS: openSUSE 42.1
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Other
          Assignee: maintenance-at-opensuse.org
          Reporter: mschnitzer-at-suse.com
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---
         Component: Other
           Version: Leap 42.1
           Product: openSUSE Distribution

I would like to update the package python3-websockets from version 3.0 to 3.1.

Changelog:
 * Avoided a warning when closing a connection before the opening handshake.
 * Added flow control for incoming data.


--1463997515.aEAacdAB0.6117
Date: Mon, 23 May 2016 09:58:35 +0000
MIME-Version: 1.0
Content-Type: text/plain

http://bugzilla.opensuse.org/show_bug.cgi?id=981080

            Bug ID: 981080
           Summary: kiwi: fails to find modules when using perl 5.24
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Other
          Assignee: bnc-team-screening-at-forge.provo.novell.com
          Reporter: dimstar-at-opensuse.org
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

openSUSE:Factory:Staging:B currently contains perl 5.24.0

With this setup, kiwi fails to produce a media, the errors listed are:

>zeus.leuenberger.net:/root # kiwi --root /usr/src/packages/KIWIROOT -v 5 --logfile terminal -p /usr/src/packages/SOURCES --create-instsource /usr/src/packages/SOURCES
>May-23 09:53:32 <1> : Setting log file to: terminal
>May-23 09:53:32 <1> : kiwi --root /usr/src/packages/KIWIROOT -v 5 --logfile terminal -p /usr/src/packages/SOURCES --create-instsource /usr/src/packages/SOURCES
>May-23 09:53:32 <1> : kiwi revision: 24db6c8a171001a4a8988e92d19116804f5f9c56
>May-23 09:53:32 <1> : Setting log file to: terminal
>May-23 09:53:32 <3> : Module <KIWICollect> is not available!
>May-23 09:53:32 <1> : Closing session with ecode: 3
>May-23 09:53:32 <3> : KIWI exited with error(s)

According to an srace log, kiwi did open
 stat("/usr/share/kiwi/modules/KIWICollect.pm", {st_mode=S_IFREG|0644,
st_size=104415, ...}) = 0
 open("/usr/share/kiwi/modules/KIWICollect.pm", O_RDONLY) = 3

(so the file at least is present)

A bit of 'digging' brought me to this error:

Experimental keys on scalar is now forbidden at
/usr/share/kiwi/modules/KIWICollect.pm line 1370.


body:
--1463997932.25EFA0.31625
Date: Mon, 23 May 2016 10:05:32 +0000
MIME-Version: 1.0
Content-Type: text/plain

http://bugzilla.novell.com/show_bug.cgi?id=981083

            Bug ID: 981083
           Summary: rpm ksyms fileattrs do not expand %name
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Basesystem
          Assignee: bnc-team-screening-at-forge.provo.novell.com
          Reporter: jslaby-at-suse.com
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

When the kernel is built in OBS, provides are being found. But this emits a lot
of:
[  400s] sed: can't read /usr/src/packages/SOURCES/%name.spec: No such file or
directory

The process tree is:
    \_ rpmbuild -ba --define _srcdefattr (-,root,root) --nosignature
/home/abuild/rpmbuild/SOURCES/kernel-default.spec
        \_ /bin/bash /home/abuild/rpmbuild/SOURCES/find-provides kernel-default
            \_ /bin/sh /usr/lib/rpm/find-provides kernel-default
                \_ /usr/lib/rpm/rpmdeps --provides
                    \_ /bin/bash /usr/lib/rpm/find-supplements.ksyms %name
                        \_ /bin/bash /usr/lib/rpm/find-supplements.ksyms %name
                        |   \_ /bin/bash /usr/lib/rpm/find-supplements.ksyms
%name
                        |   \_ sed -nre s,(.+:.+),modalias(kernel-default:\1),p
                        |   \_ tee -a /tmp/tmp.6NZ7l2NDRz
                        \_ sort -u
                        \_ /bin/bash /usr/lib/rpm/find-supplements.ksyms %name

It can be seen, that this is executed:
/usr/lib/rpm/find-supplements.ksyms %name

I believe this is from /usr/lib/rpm/fileattrs/ksyms.attr:
%__ksyms_provides       %{_rpmconfigdir}/find-provides.ksyms %name
%__ksyms_requires       %{_rpmconfigdir}/find-requires.ksyms %name
%__ksyms_supplements    %{_rpmconfigdir}/find-supplements.ksyms %name
%__ksyms_path   (/lib/modules/.*\.ko(\.gz)?)|(/boot/vmlinu[xz].*)$

But %name is never expanded here.

summary: rpm ksyms fileattrs do not expand %name


--1464001480.83e5D74A3.16875
Date: Mon, 23 May 2016 11:04:40 +0000
MIME-Version: 1.0
Content-Type: text/plain

http://bugzilla.opensuse.org/show_bug.cgi?id=981094

            Bug ID: 981094
           Summary: OpenStack Mitaka: Launching xen instance fails with rbd image
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 42.1
          Hardware: x86-64
                OS: openSUSE 42.1
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Virtualization:Tools
          Assignee: virt-bugs-at-suse.de
          Reporter: eblock-at-nde.ag
        QA Contact: qa-bugs-at-suse.de
                CC: jmozdzen-at-nde.ag
          Found By: ---
           Blocker: ---

Created attachment 677903
  --> http://bugzilla.opensuse.org/attachment.cgi?id=677903&action=edit
nova compute logs and xml configs

Issue: I have an OpenStack Cloud (Mitaka) running on Leap with a ceph cluster
as storage backend, all the relevant services use ceph as storage backend
(glance, cinder-volume, nova).
Launching an instance from an rbd image fails on Xen hypervisor due to missing
backend driver name 'qemu' in the resulting xml config.

Steps to reproduce:

1. Boot an instance with nova CLI or Horizon on a Xen hypervisor, the source
image should be located in an rbd cluster.

Actual result:
Instance fails with ERROR state. nova-compute.log reports

libvirtError: internal error: libxenlight failed to create new domain
'instance-00000229'

Please find detailed (verbose) log output from nova-compute for both xen and
kvm hypervisor in the attached tarball. The log files are truncated.

Expected result:
Instance boots with a clone of the provided rbd image.

Additional information:
The instance does boot successfully if you choose "boot from image (creates a
new volume)", in that case nova provides the driver name, there's a function
call pick_disk_driver_name() in
/usr/lib/python2.7/site-packages/nova/virt/libvirt/volume/volume.py. If no
volume is created, libxl has to provide the driver name.

The package versions I'm using:

---cut here---
compute1:~ # rpm -qi python-nova-13.0.1~a0~dev46-1.1.noarch
Name        : python-nova
Version     : 13.0.1~a0~dev46
Release     : 1.1
Architecture: noarch
Install Date: Di 10 Mai 2016 12:38:57 CEST
Group       : Development/Languages/Python
Size        : 16549000
License     : Apache-2.0
Signature   : RSA/SHA256, Mo 09 Mai 2016 13:39:20 CEST, Key ID 893a90dad85f9316
Source RPM  : openstack-nova-13.0.1~a0~dev46-1.1.src.rpm
Build Date  : Mo 09 Mai 2016 13:38:09 CEST
Build Host  : cloud113
Relocations : (not relocatable)
Vendor      : obs://build.opensuse.org/Cloud:OpenStack
URL         : https://launchpad.net/nova
Summary     : OpenStack Compute (Nova) - Python module
Description :
This package contains the core Python module of OpenStack Nova.
Distribution: Cloud:OpenStack:Mitaka / openSUSE_Leap_42.1

#################################################################

compute1:~ # rpm -qi xen-libs
Name        : xen-libs
Version     : 4.7.0_03
Release     : 440.1
Architecture: x86_64
Install Date: Di 10 Mai 2016 13:59:52 CEST
Group       : System/Kernel
Size        : 1560640
License     : GPL-2.0
Signature   : RSA/SHA256, Fr 06 Mai 2016 16:33:12 CEST, Key ID a193fbb572174fc2
Source RPM  : xen-4.7.0_03-440.1.src.rpm
Build Date  : Fr 06 Mai 2016 16:31:47 CEST
Build Host  : build74
Relocations : (not relocatable)
Vendor      : obs://build.opensuse.org/Virtualization

#################################################################

compute1:~ # rpm -qi qemu-block-rbd
Name        : qemu-block-rbd
Version     : 2.5.93
Release     : 327.6
Architecture: x86_64
Install Date: Di 10 Mai 2016 14:53:26 CEST
Group       : System/Emulators/PC
Size        : 84024
License     : BSD-3-Clause and GPL-2.0 and GPL-2.0+ and LGPL-2.1+ and MIT
Signature   : (none)
Source RPM  : qemu-2.5.93-327.6.src.rpm
Build Date  : Di 10 Mai 2016 14:42:57 CEST
Build Host  : compute1.cloud.hh.nde.ag

---cut here---

As you can see, we're running a self-compiled version of qemu. I'm not sure if
it still holds true with above version, but at least with earlier versions, we
had to modify the spec file to enable RBD support.

For completeness sake, I ran an additional test case and now see the following
behavior:

- KVM, boot from volume: "driver_name" provided by Nova
- KVM, boot from image:  "driver_name" provided by libvirt
- Xen, boot from volume: "driver_name" provided by Nova
- Xen, boot from image:  error, no-one provides "driver_name"

Please find further information in the mailing list:
https://lists.opensuse.org/opensuse-cloud/2016-05/msg00000.html

I have attached a tarball containing 3 xml files (nova-xen-conf.xml,
nova-kvm-conf.xml, virsh-kvm-conf.xml) and the nova-compute.logs for both
compute nodes (xen and kvm).
You can find the <disk> config section created by nova in nova-compute logs or
in the seperate xml files.

The file virsh-kvm-conf.xml contains output of 'virsh dumpxml <instance>' to
illustrate the resulting <disk> section containing a driver name.


--1464070755.DF6C0F0.11837
Date: Tue, 24 May 2016 06:19:15 +0000
MIME-Version: 1.0
Content-Type: text/plain

http://bugzilla.opensuse.org/show_bug.cgi?id=981268

            Bug ID: 981268
           Summary: [modestting] Driver crashes in FreeRec()
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: Other
                OS: Other
            Status: CONFIRMED
          Severity: Normal
          Priority: P5 - None
         Component: X.Org
          Assignee: eich-at-suse.com
          Reporter: eich-at-suse.com
        QA Contact: xorg-maintainer-bugs-at-forge.provo.novell.com
          Found By: Development
           Blocker: ---

The driver ScreenInfo private may be accessed in ms_ent_priv() after it was
NULLed.
To avoid this, free later.


--1464099645.6edFd26.24370
Date: Tue, 24 May 2016 14:20:45 +0000
MIME-Version: 1.0
Content-Type: text/plain

http://bugzilla.suse.com/show_bug.cgi?id=981372

            Bug ID: 981372
           Summary: Patch gdm-workaround-boo971852.patch is breaking my X session
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: All
                OS: SUSE Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: GNOME
          Assignee: bnc-team-gnome-at-forge.provo.novell.com
          Reporter: werner-at-suse.com
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

IMHO there is no need to brak my X session.  Why this harshly patch has been
added?  What is wrong with my type of X session?


body:
--1464103843.FDeee1E810.27356
Date: Tue, 24 May 2016 15:30:43 +0000
MIME-Version: 1.0
Content-Type: text/plain

http://bugzilla.opensuse.org/show_bug.cgi?id=981407

            Bug ID: 981407
           Summary: Update putty to 0.67
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 42.1
          Hardware: All
                OS: Linux
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Network
          Assignee: jengelh-at-inai.de
          Reporter: jengelh-at-inai.de
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

From http://www.chiark.greenend.org.uk/~sgtatham/putty/
"""
 2016-03-05 PuTTY 0.67 released, fixing a SECURITY HOLE

PuTTY 0.67, released today, fixes a security hole in 0.66 and before:
vuln-pscp-sink-sscanf."""

This update is so far missing from 13.2, 42.1, and should be sent there too.

summary: Update putty to 0.67


body:
Build Identifier:

sntp 4.2.8p7 always displays "error waiting on child [number]: No child
processes" when invoked with the -s or -S parameters.

This behaviour is not seen in 4.2.8p4.

The time is adjusted appropriately, making the error more of an annoyance than
anything else.

Reproducible: Always

Steps to Reproduce:
1. As root, execute sntp -s pool.ntp.org (or -S)
2.
3.
Actual Results:
error waiting on child [number]: No child processes is displayed before the
normal output of the command, i.e.

sntp 4.2.8p7@1.3265-o Thu May 12 16:14:59 UTC 2016 (1)
error waiting on child 32071: No child processes
2016-05-24 08:58:00.535743 (-0700) -0.009292 +/- 0.054712 pool.ntp.org
204.2.134.164 s3 no-leap

Expected Results:
Error should not be displayed.

summary: sntp always reports error waiting on child [number]: No child processes


body:
Build Identifier:

Valgrind is unusable because of an unhandled instruction in standart C++
library.

Reproducible: Always

Steps to Reproduce:
1.Install valgrind and LibreOffice
2. Launch LibreOffice inside valgrind by using valgrind
/usr/lib64/libreoffice/program/soffice.bin
3. LibreOffice stops on an unhandled instruction
Actual Results:
==3600== ERROR SUMMARY: 74 errors from 74 contexts (suppressed: 0 from 0)
vex amd64->IR: unhandled instruction bytes: 0xF 0xC7 0xF0 0x89 0x6 0xF 0x42
0xC1
vex amd64->IR:   REX=0 REX.W=0 REX.R=0 REX.X=0 REX.B=0
vex amd64->IR:   VEX=0 VEX.L=0 VEX.nVVVV=0x0 ESC=0F
vex amd64->IR:   PFX.66=0 PFX.F2=0 PFX.F3=0
==3599== valgrind: Unrecognised instruction at address 0x10d64aa5.
==3599==    at 0x10D64AA5: std::(anonymous namespace)::__x86_rdrand()
(random.cc:69)
==3599==    by 0x10D64C11: std::random_device::_M_getval() (random.cc:130)

Expected Results:
soffice.bin should continue

summary: "unhandled instruction bytes" during valgrind'd launched C++ application


body:
--1464120747.8fD0b6a0.12605
Date: Tue, 24 May 2016 20:12:27 +0000
MIME-Version: 1.0
Content-Type: text/plain

http://bugzilla.opensuse.org/show_bug.cgi?id=981470

            Bug ID: 981470
           Summary: libsidplay1 fails to build with gcc6
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Other
          Assignee: bnc-team-screening-at-forge.provo.novell.com
          Reporter: dimstar-at-opensuse.org
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

In an attemot to move to GCC6, we have seen that libsidplay1 fails to build.
This library is used by Gstreamer to play the nostalgic C64 .sid tunes and it
would be a shame to lose this support.

The build fails with this error:

[   73s] libtool: compile:  g++ -DPACKAGE_NAME=\"\" -DPACKAGE_TARNAME=\"\"
-DPACKAGE_VERSION=\"\" -DPACKAGE_STRING=\"\" -DPACKAGE_BUGREPORT=\"\"
-DPACKAGE_URL=\"\" -DPACKAGE=\"libsidplay\" -DVERSION=\"1.36.59\"
-DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1
-DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1
-DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 -DSIZEOF_CHAR=1 -DSIZEOF_SHORT_INT=2
-DSIZEOF_INT=4 -DSIZEOF_LONG_INT=8 -DSTDC_HEADERS=1 -DHAVE_LONG_FILE_NAMES=1
-DHAVE_DLFCN_H=1 -DLT_OBJDIR=\".libs/\" -I. -I.. -fmessage-length=0
-grecord-gcc-switches -O2 -Wall -D_FORTIFY_SOURCE=2 -fstack-protector
-funwind-tables -fasynchronous-unwind-tables -g -c samples.cpp  -fPIC -DPIC -o
.libs/samples.o
[   73s] samples.cpp:82:1: error: narrowing conversion of '128' from 'int' to
'sbyte {aka signed char}' inside { } [-Wnarrowing]
[   73s]  };
[   73s]  ^
[   73s] samples.cpp:82:1: error: narrowing conversion of '145' from 'int' to
'sbyte {aka signed char}' inside { } [-Wnarrowing]

summary: libsidplay1 fails to build with gcc6


--1464158837.0efdC0.6422
Date: Wed, 25 May 2016 06:47:17 +0000
MIME-Version: 1.0
Content-Type: text/plain

http://bugzilla.opensuse.org/show_bug.cgi?id=981522

            Bug ID: 981522
           Summary: sessreg Module experiences buffer overflow at high UID
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: 13.2
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: X.Org
          Assignee: xorg-maintainer-bugs-at-forge.provo.novell.com
          Reporter: reinhard.hennig@ofd-z.niedersachsen.de
        QA Contact: xorg-maintainer-bugs-at-forge.provo.novell.com
          Found By: ---
           Blocker: ---

xdm and kdm crash when UID beyond 10.000.000 are used. Some UIDs provide stable
logins but some don't. For example 20.000.000 works fine, 25.000.000 fails. You
can provoke the error by make a simple account like this in your /etc/passwd
file:
otto:x:25000107:25000000:Testuser lokal:/opt/home/otto:/bin/bash

kdm and xdm crash, while terminal based login and graphical logins using gdm
work fine.

This account in your /etc/passwd works fine:
willi:x:20000107:20000000:Testuser lokal:/opt/home/willi:/bin/bash

reason for that behaviour is a buffer overflow in this module: sessreg

used by xdm and kdm.

It doesn't depend on the source (/etc/passwd or ldap).

You may check by doing

sessreg -a willi # works, returns no error

sessreg -a otto # returns error:
seeking lastlog entry: Invalid argument

Other Scenarios: Yes: Login using gdm displaymanager is not affected
Fix: choose different UIDs or gdm

Fast help would be appreciated.


--1464185266.abfe16.29319
Date: Wed, 25 May 2016 14:07:46 +0000
MIME-Version: 1.0
Content-Type: text/plain

http://bugzilla.suse.com/show_bug.cgi?id=981645

            Bug ID: 981645
           Summary: Installation slide-show  talks about Leap 42.1, not TW
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Installation
          Assignee: yast2-maintainers-at-suse.de
          Reporter: mkravec-at-suse.com
        QA Contact: jsrain-at-suse.com
          Found By: ---
           Blocker: ---

Created attachment 678313
  --> http://bugzilla.suse.com/attachment.cgi?id=678313&action=edit
slideshow

During Tumbleweed installation there is no mention of TW in slide-show. All
slides are about Leap 42.1.

Tested with openSUSE-Tumbleweed-DVD-x86_64-Snapshot20160520


body:
--1464188381.Cbd2D0.19770
Date: Wed, 25 May 2016 14:59:41 +0000
MIME-Version: 1.0
Content-Type: text/plain

http://bugzilla.opensuse.org/show_bug.cgi?id=981663

            Bug ID: 981663
           Summary: patterns-openSUSE-x11 recommends xorg-x11-Xvnc
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: X.Org
          Assignee: xorg-maintainer-bugs-at-forge.provo.novell.com
          Reporter: dimstar-at-opensuse.org
        QA Contact: xorg-maintainer-bugs-at-forge.provo.novell.com
          Found By: ---
           Blocker: ---

In a default installation, the pattern patterns-openSUSE-x11 is being installed
as a condition to most DEs (if not all) - which makes perfect sense.

said pattern recommends the installation of xorg-x11-Xvnc

Is this dependency still conform for today's usage? If anybody were to go and
enable 'Remote Administration' inside YaST, the installation of the package is
automatically triggered anyway (already by starting the module).

(as for doing the work of updating the pattern, I will gladly assist if we get
to the conclusion that this should be done)

pkgs: patterns-openSUSE tigervnc twm xmonad


body:
--1464204563.52EF8dcB3.1794
Date: Wed, 25 May 2016 19:29:23 +0000
MIME-Version: 1.0
Content-Type: text/plain

http://bugzilla.opensuse.org/show_bug.cgi?id=981717

            Bug ID: 981717
           Summary: Touchscreen not recognised
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 42.2
          Hardware: x86-64
                OS: Other
            Status: NEW
          Severity: Major
          Priority: P5 - None
         Component: Kernel
          Assignee: kernel-maintainers-at-forge.provo.novell.com
          Reporter: badshah400-at-gmail.com
        QA Contact: qa-bugs-at-suse.de
                CC: jkosina-at-suse.com, tiwai-at-suse.com
        Depends on: 975841
          Found By: ---
           Blocker: ---

+++ This bug was initially created as a clone of Bug #975841 +++

Just bought a new laptop: ThinkPad Yoga 260 and installed TW 20160411 on it
with kernel 4.5. This has a touch sensitive screen and a pen. Unfortunately,
although it seems that the touchscreen is recognised as a Wacom tablet,
tapping/touching the screen leaves it unresponsive. Further, on every login
into a GNOME session, I get the warning: Unknown Wacom tablet detected, this
device may not work as expected. Indeed it doesn't work at all. Hardware info
from YaST attached.

This was finally fixed in kernel 4.6 by this commit:
http://git.kernel.org/cgit/linux/kernel/git/jikos/hid.git/commit/?id=326ea2a90500fe4add86c5fb95d914d46910e780

Could we get this backported for the Leap 42.2 kernel too, please?

summary: Touchscreen not recognised


--1464239669.CCceB40.15400
Date: Thu, 26 May 2016 05:14:29 +0000
MIME-Version: 1.0
Content-Type: text/plain

http://bugzilla.novell.com/show_bug.cgi?id=981750

            Bug ID: 981750
           Summary: TW20160524: xf86-input-synaptics  is pulled in automatically but it should not
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: x86-64
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: X.Org
          Assignee: xorg-maintainer-bugs-at-forge.provo.novell.com
          Reporter: robby.engelmann@igfs-ev.de
        QA Contact: xorg-maintainer-bugs-at-forge.provo.novell.com
          Found By: ---
           Blocker: ---

According to TW release mail:
- removed Supplements: xorg-x11-server, so the driver no longer
  gets installed by default

However, when I remove it by zypper rm it will be pulled in again by a zypper
dup. I have to taboo this package, if I do not want use synaptics driver but
libinput as before that snapshot was released.


body:
--1464267915.30Dc00.25106
Date: Thu, 26 May 2016 13:05:15 +0000
MIME-Version: 1.0
Content-Type: text/plain

http://bugzilla.opensuse.org/show_bug.cgi?id=981836

            Bug ID: 981836
           Summary: virt-manager does not support all boot methods for AArch64
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: aarch64
                OS: Other
            Status: NEW
          Severity: Critical
          Priority: P5 - None
         Component: Virtualization:Tools
          Assignee: virt-bugs-at-suse.de
          Reporter: awafaa-at-opensuse.org
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

Created attachment 678492
  --> http://bugzilla.opensuse.org/attachment.cgi?id=678492&action=edit
Screenshot of new VM options

Trying to set up VMs with virt-manager to boot from .iso is not possible.
Neither is booting from Netwrok Install (HTTP, FTP, or NFS) or Network Boot
(PXE). Only installing from existing disk image.

Only error message is a warning.

pkgs: libvirt virt-manager


--1464283632.e45C1aD00.32628
Date: Thu, 26 May 2016 17:27:12 +0000
MIME-Version: 1.0
Content-Type: text/plain

http://bugzilla.novell.com/show_bug.cgi?id=981887

            Bug ID: 981887
           Summary: wicked does not start without CONFIG_FIB_RULES in kernel
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Network
          Assignee: bnc-team-screening-at-forge.provo.novell.com
          Reporter: jslaby-at-suse.com
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

Why does wicked need advanced routing? RTM_GETRULE is only available if
advanced routing is compiled in kernel, but wicked/src/iflist.c tries to
enforce this netlink command to be present.

There is no reason why networking should not start without
RTM_GETRULE/FIB_RULES.

The failure is as follows:
# /usr/sbin/wickedd  --foreground
wickedd: ni_nl_dump_store: failed to receive response: Operation not supported
wickedd: failed to refresh interface list
wickedd: failed to discover interface state

This is a regression from previous networking setups with dhcp clients like
dhclient or dhcpcd.


--1464310813.58fFf16.27726
Date: Fri, 27 May 2016 01:00:13 +0000
MIME-Version: 1.0
Content-Type: text/plain

http://bugzilla.opensuse.org/show_bug.cgi?id=981924

            Bug ID: 981924
           Summary: Touchpad no longer recognised unless xf86-input-synaptics in uninstalled
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: x86-64
                OS: SUSE Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: GNOME
          Assignee: bnc-team-gnome-at-forge.provo.novell.com
          Reporter: badshah400-at-gmail.com
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

Created attachment 678575
  --> http://bugzilla.opensuse.org/attachment.cgi?id=678575&action=edit
journalctl from boot when touchpad wasnt beeing seen

After TW upgrade to 20160524, my touchpad stopped being recognised in the
gnome-control-panel. It only shows mouse (which it recognises the Lenovo track
point as) properties, so no tap-to-click settings etc. All gone, with warnings
like these on the journal:
May 27 02:35:02 tp-yoga260 gnome-control-center.desktop[2370]:
(gnome-control-center:2370): mouse-cc-panel-WARNING **: Detected synaptics X
driver, please migrate to libinput

At this point libinput pkgs were all installed on my system:
S | Name                | Summary
          | Type
--+---------------------+-----------------------------------------------------------------+--------
i | libinput-udev       | Input device and event processing library integration
into udev | package
i | libinput10          | Input device and event processing library
          | package
i | xf86-input-libinput | Libinput driver for the Xorg X server
          | package

On a hunch, I uninstalled the xf86-input-synaptics package which also removed
the xorg-x11-driver-input and then rebooted. Gnome-control-center now sees my
touchpad again. Seems this synaptics package should really not be installed by
default then. If I do "zypper inr" it tries to pull in these two pkgs again.


--1464351832.cba6A6.17680
Date: Fri, 27 May 2016 12:23:52 +0000
MIME-Version: 1.0
Content-Type: text/plain

http://bugzilla.suse.com/show_bug.cgi?id=982003

            Bug ID: 982003
           Summary: VUL-0: CVE-2016-5103: roundcube: XSS vulnerability in mail content page
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 42.1
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Security
          Assignee: nix-at-opensuse.org
          Reporter: abergmann-at-suse.com
        QA Contact: qa-bugs-at-suse.de
                CC: aj-at-ajaissle.de, lrupp-at-suse.com, wolfgang-at-rosenauer.org
          Found By: Security Response Team
           Blocker: ---

rh#1339654

A 1.2.0 release of roundcubemail fixed an XSS vulnerability in href attribute
on area tag.

External references:

https://github.com/roundcube/roundcubemail/issues/5240

Upstream fix:

https://github.com/roundcube/roundcubemail/pull/5241

CVE assignment:

http://seclists.org/oss-sec/2016/q2/414

References:
https://bugzilla.redhat.com/show_bug.cgi?id=1339654
http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2016-5103
http://seclists.org/oss-sec/2016/q2/414