November 2017 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 911623] New: Bluetooth will not pair a headset
by bugzilla_noreply＠novell.com 17 Dec '20

17 Dec '20

http://bugzilla.opensuse.org/show_bug.cgi?id=911623 Bug ID: 911623 Summary: Bluetooth will not pair a headset Classification: openSUSE Product: openSUSE Distribution Version: 13.2 Hardware: x86-64 OS: openSUSE 13.2 Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-maintainers(a)forge.provo.novell.com Reporter: bbagger(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- When trying to pair a Bluetooh headset (BPM X1 Headphones) the operations times out, and the following appears in /var/log/messages: ==== 112416+01:00 yosie kernel: [ 4397.298229] ------------[ cut here ]------------ 2015-01-04T19:25:28.112450+01:00 yosie kernel: [ 4397.298288] WARNING: CPU: 1 PID: 28817 at ../net/bluetooth/hci_conn.c:296 hci_conn_timeout+0x4a/0x280 [bluetooth]() 2015-01-04T19:25:28.112454+01:00 yosie kernel: [ 4397.298293] Modules linked in: fuse nfsv3 nfs_acl rpcsec_gss_krb5 auth_rpcgss oid_registry nfsv4 dns_resolver nfs lockd sunrpc fscache rfcomm iscsi_ibft iscsi_boot_sysfs af_packet bnep ecb btusb bluetooth 6lowpan_iphc raid1 uvcvideo md_mod videobuf2_vmalloc snd_usb_audio videobuf2_memops videobuf2_core snd_usbmidi_lib v4l2_common videodev eeepc_wmi asus_wmi sparse_keymap rfkill video kvm_amd kvm snd_hda_codec_realtek snd_hda_codec_generic serio_raw snd_hda_codec_hdmi pcspkr k10temp snd_hda_intel snd_hda_controller snd_hda_codec snd_hwdep r8169 mii snd_ens1371 snd_rawmidi snd_ac97_codec snd_pcm shpchp ac97_bus gameport i2c_piix4 wmi tpm_infineon tpm_tis tpm acpi_cpufreq button processor snd_seq snd_seq_device snd_timer snd soundcore ata_generic pata_atiixp ohci_pci radeon sr_mod cdrom i2c_algo_bit drm_kms_helper ttm drm xhci_hcd dm_mirror dm_region_hash dm_log dm_mod sg 2015-01-04T19:25:28.112458+01:00 yosie kernel: [ 4397.298411] CPU: 1 PID: 28817 Comm: kworker/u9:0 Tainted: G W 3.16.7-7-desktop #1 2015-01-04T19:25:28.112461+01:00 yosie kernel: [ 4397.298416] Hardware name: System manufacturer System Product Name/F1A75-M-PRO R2.0, BIOS 5010 08/09/2012 2015-01-04T19:25:28.112464+01:00 yosie kernel: [ 4397.298446] Workqueue: hci0 hci_conn_timeout [bluetooth] 2015-01-04T19:25:28.112467+01:00 yosie kernel: [ 4397.298451] 0000000000000009 ffffffff8161bd03 0000000000000000 ffffffff8105cad7 2015-01-04T19:25:28.112469+01:00 yosie kernel: [ 4397.298458] ffff8800b8cfa8b8 00000000ffffffff ffff8800b8cfa800 ffff88021158a900 2015-01-04T19:25:28.112472+01:00 yosie kernel: [ 4397.298465] 0000000000000000 ffffffffa05c3d3a ffffffff8161e59d ffff8800b8cfa8b8 2015-01-04T19:25:28.112474+01:00 yosie kernel: [ 4397.298471] Call Trace: 2015-01-04T19:25:28.112477+01:00 yosie kernel: [ 4397.298499] [<ffffffff810051ee>] dump_trace+0x8e/0x350 2015-01-04T19:25:28.112479+01:00 yosie kernel: [ 4397.298511] [<ffffffff81005556>] show_stack_log_lvl+0xa6/0x190 2015-01-04T19:25:28.112482+01:00 yosie kernel: [ 4397.298521] [<ffffffff81006c51>] show_stack+0x21/0x50 2015-01-04T19:25:28.112484+01:00 yosie kernel: [ 4397.298532] [<ffffffff8161bd03>] dump_stack+0x49/0x6a 2015-01-04T19:25:28.112487+01:00 yosie kernel: [ 4397.298543] [<ffffffff8105cad7>] warn_slowpath_common+0x77/0x90 2015-01-04T19:25:28.112489+01:00 yosie kernel: [ 4397.298576] [<ffffffffa05c3d3a>] hci_conn_timeout+0x4a/0x280 [bluetooth] 2015-01-04T19:25:28.112584+01:00 yosie kernel: [ 4397.298640] [<ffffffff810770fd>] process_one_work+0x16d/0x460 2015-01-04T19:25:28.112596+01:00 yosie kernel: [ 4397.298651] [<ffffffff810779e5>] worker_thread+0x115/0x5102015-01-04T19:25:28.112416+01:00 yosie kernel: [ 4397.298229] ------------[ cut here ]------------ 2015-01-04T19:25:28.112450+01:00 yosie kernel: [ 4397.298288] WARNING: CPU: 1 PID: 28817 at ../net/bluetooth/hci_conn.c:296 hci_conn_timeout+0x4a/0x280 [bluetooth]() 2015-01-04T19:25:28.112454+01:00 yosie kernel: [ 4397.298293] Modules linked in: fuse nfsv3 nfs_acl rpcsec_gss_krb5 auth_rpcgss oid_registry nfsv4 dns_resolver nfs lockd sunrpc fscache rfcomm iscsi_ibft iscsi_boot_sysfs af_packet bnep ecb btusb bluetooth 6lowpan_iphc raid1 uvcvideo md_mod videobuf2_vmalloc snd_usb_audio videobuf2_memops videobuf2_core snd_usbmidi_lib v4l2_common videodev eeepc_wmi asus_wmi sparse_keymap rfkill video kvm_amd kvm snd_hda_codec_realtek snd_hda_codec_generic serio_raw snd_hda_codec_hdmi pcspkr k10temp snd_hda_intel snd_hda_controller snd_hda_codec snd_hwdep r8169 mii snd_ens1371 snd_rawmidi snd_ac97_codec snd_pcm shpchp ac97_bus gameport i2c_piix4 wmi tpm_infineon tpm_tis tpm acpi_cpufreq button processor snd_seq snd_seq_device snd_timer snd soundcore ata_generic pata_atiixp ohci_pci radeon sr_mod cdrom i2c_algo_bit drm_kms_helper ttm drm xhci_hcd dm_mirror dm_region_hash dm_log dm_mod sg 2015-01-04T19:25:28.112458+01:00 yosie kernel: [ 4397.298411] CPU: 1 PID: 28817 Comm: kworker/u9:0 Tainted: G W 3.16.7-7-desktop #1 2015-01-04T19:25:28.112461+01:00 yosie kernel: [ 4397.298416] Hardware name: System manufacturer System Product Name/F1A75-M-PRO R2.0, BIOS 5010 08/09/2012 2015-01-04T19:25:28.112464+01:00 yosie kernel: [ 4397.298446] Workqueue: hci0 hci_conn_timeout [bluetooth] 2015-01-04T19:25:28.112467+01:00 yosie kernel: [ 4397.298451] 0000000000000009 ffffffff8161bd03 0000000000000000 ffffffff8105cad7 2015-01-04T19:25:28.112469+01:00 yosie kernel: [ 4397.298458] ffff8800b8cfa8b8 00000000ffffffff ffff8800b8cfa800 ffff88021158a900 2015-01-04T19:25:28.112472+01:00 yosie kernel: [ 4397.298465] 0000000000000000 ffffffffa05c3d3a ffffffff8161e59d ffff8800b8cfa8b8 2015-01-04T19:25:28.112474+01:00 yosie kernel: [ 4397.298471] Call Trace: 2015-01-04T19:25:28.112477+01:00 yosie kernel: [ 4397.298499] [<ffffffff810051ee>] dump_trace+0x8e/0x350 2015-01-04T19:25:28.112479+01:00 yosie kernel: [ 4397.298511] [<ffffffff81005556>] show_stack_log_lvl+0xa6/0x190 2015-01-04T19:25:28.112482+01:00 yosie kernel: [ 4397.298521] [<ffffffff81006c51>] show_stack+0x21/0x50 2015-01-04T19:25:28.112484+01:00 yosie kernel: [ 4397.298532] [<ffffffff8161bd03>] dump_stack+0x49/0x6a 2015-01-04T19:25:28.112487+01:00 yosie kernel: [ 4397.298543] [<ffffffff8105cad7>] warn_slowpath_common+0x77/0x90 2015-01-04T19:25:28.112489+01:00 yosie kernel: [ 4397.298576] [<ffffffffa05c3d3a>] hci_conn_timeout+0x4a/0x280 [bluetooth] 2015-01-04T19:25:28.112584+01:00 yosie kernel: [ 4397.298640] [<ffffffff810770fd>] process_one_work+0x16d/0x460 2015-01-04T19:25:28.112596+01:00 yosie kernel: [ 4397.298651] [<ffffffff810779e5>] worker_thread+0x115/0x510 2015-01-04T19:25:28.112598+01:00 yosie kernel: [ 4397.298662] [<ffffffff8107dd5d>] kthread+0xbd/0xe0 2015-01-04T19:25:28.112601+01:00 yosie kernel: [ 4397.298672] [<ffffffff8162297c>] ret_from_fork+0x7c/0xb0 2015-01-04T19:25:28.112604+01:00 yosie kernel: [ 4397.298681] ---[ end trace 4772ff5681be4670 ]--- 2015-01-04T19:25:28.194795+01:00 yosie bluetoothd[1061]: connect error: Software caused connection abort (103) 2015-01-04T19:25:28.112598+01:00 yosie kernel: [ 4397.298662] [<ffffffff8107dd5d>] kthread+0xbd/0xe0 2015-01-04T19:25:28.112601+01:00 yosie kernel: [ 4397.298672] [<ffffffff8162297c>] ret_from_fork+0x7c/0xb0 2015-01-04T19:25:28.112604+01:00 yosie kernel: [ 4397.298681] ---[ end trace 4772ff5681be4670 ]--- 2015-01-04T19:25:28.194795+01:00 yosie bluetoothd[1061]: connect error: Software caused connection abort (103) ===== I have tried to pair the same headset on a live Rosa setup, and there it works as expected. -- You are receiving this mail because: You are on the CC list for the bug.

2 10

[Bug 1052770] New: Failed to save IO scheduler settings
by bugzilla_noreply＠novell.com 11 Dec '20

11 Dec '20

http://bugzilla.suse.com/show_bug.cgi?id=1052770 Bug ID: 1052770 Summary: Failed to save IO scheduler settings Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 Assignee: yast2-maintainers(a)suse.de Reporter: hguo(a)suse.com QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- Created attachment 735702 --> http://bugzilla.suse.com/attachment.cgi?id=735702&action=edit y2log The system is a freshly installed KVM running the latest snapshot of tumbleweed. When attempting to change system-wide IO scheduler to noop, this error occurs: Details: Invalid argument @ fptr_finalize_flush - /sys/block/vda/queue/scheduler Caller: /usr/share/YaST2/modules/SystemSettings.rb:252:in `write' lsblk -O output is the following: NAME KNAME MAJ:MIN FSTYPE MOUNTPOINT LABEL UUID PARTTYPE PARTLABEL PARTUUID PARTFLAGS RA RO RM HOTPLUG MODEL SERIAL SIZE STATE OWNER GROUP MODE ALIGNMENT MIN-IO OPT-IO PHY-SEC LOG-SEC ROTA SCHED RQ-SIZE TYPE DISC-ALN DISC-GRAN DISC-MAX DISC-ZERO WSAME WWN RAND PKNAME HCTL TRAN SUBSYSTEMS REV VENDOR ZONED sr0 sr0 11:0 512 0 1 1 QEMU 1024M runni root cdrom brw-rw---- 0 512 0 512 512 1 noop 128 rom 0 0B 0B 0 0B 1 0:0:0:0 sata block:scsi:pci 2.5+ QEMU none vda vda 254:0 512 0 0 0 64G root disk brw-rw---- 0 512 0 512 512 1 mq-deadline │ 256 disk 0 0B 0B 0 0B 0 block:virtio:pci │ 0x1af4 none ├─vda1 │ vda1 254:1 swap [SWAP] aeec6ca8-628d-49e3-ae58-1daf1c3accc2 0x82 328c4097-01 512 0 0 0 2G root disk brw-rw---- 0 512 0 512 512 1 mq-deadline │ 256 part 0 0B 0B 0 0B 0 vda block:virtio:pci │ none └─vda2 vda2 254:2 ext4 / f871d33d-0b38-4b2d-b9e0-ba204b2bb05e 0x83 328c4097-02 0x80 512 0 0 0 62G root disk brw-rw---- 0 512 0 512 512 1 mq-deadline 256 part 0 0B 0B 0 0B 0 vda block:virtio:pci none -- You are receiving this mail because: You are on the CC list for the bug.

2 6

[Bug 981596] New: XFCE Login manager usability with many users existing
by bugzilla_noreply＠novell.com 03 Dec '20

03 Dec '20

http://bugzilla.opensuse.org/show_bug.cgi?id=981596 Bug ID: 981596 Summary: XFCE Login manager usability with many users existing Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Minor Priority: P5 - None Component: Xfce Assignee: bnc-team-xfce(a)forge.provo.novell.com Reporter: dheidler(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- When I create >10 Users on a system, xfce login manager should make it easier to select the username. Currently I need to select the user from a dropdown menu. see https://raw.githubusercontent.com/os-autoinst/os-autoinst-needles-opensuse/… The option to specify the username via text field exists, but is only accessable at the bottom of the dropdown menu. This is not very nice to use, when there are many users available on the system (or the computer has NIS). Most of the other login managers fall back to a textfield for username selection, when there are too many users or make the button that shows the textfield easier accessable. The XFCE login manager should do this as well. Related openQA test (that currently has a workaround needle for some reason): https://openqa.opensuse.org/tests/198348/modules/multi_users_dm/steps/15/src -- You are receiving this mail because: You are on the CC list for the bug.

2 4

[Bug 956525] New: missing qemu-x86-debuginfo package on Tubleweed
by bugzilla_noreply＠novell.com 30 Nov '20

30 Nov '20

http://bugzilla.suse.com/show_bug.cgi?id=956525 Bug ID: 956525 Summary: missing qemu-x86-debuginfo package on Tubleweed Classification: openSUSE Product: openSUSE Tumbleweed Version: 2015* Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Development Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: dmaiocchi(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- The qemu-x86-debuginfo is missing on Tubleweed and also on Leap 42.1. 1) $ zypper se qemu -> to notify that qemu-x86-debuginfo is missed as package. -- You are receiving this mail because: You are on the CC list for the bug.

2 7

[Bug 1067414] New: virt-manager: unicode argument expected, got str
by bugzilla_noreply＠novell.com 30 Nov '20

30 Nov '20

http://bugzilla.suse.com/show_bug.cgi?id=1067414 Bug ID: 1067414 Summary: virt-manager: unicode argument expected, got str Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: KVM Assignee: kvm-bugs(a)forge.provo.novell.com Reporter: jhura(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- When trying to install VM via netboot from oS:TW, I get the following error after I hit "Finish" button: > Unable to complete install: 'unicode argument expected, got 'str'' > > Traceback (most recent call last): > File "/usr/share/virt-manager/virtManager/asyncjob.py", line 89, in cb_wrapper > callback(asyncjob, *args, **kwargs) > File "/usr/share/virt-manager/virtManager/create.py", line 2625, in _do_async_install > guest.start_install(meter=meter) > File "/usr/share/virt-manager/virtinst/guest.py", line 509, in start_install > self._prepare_install(meter, dry) > File "/usr/share/virt-manager/virtinst/guest.py", line 316, in _prepare_install > self.installer.prepare(self, meter) > File "/usr/share/virt-manager/virtinst/installer.py", line 200, in prepare > self._prepare(guest, meter) > File "/usr/share/virt-manager/virtinst/distroinstaller.py", line 222, in _prepare > self._prepare_kernel_url(guest, fetcher) > File "/usr/share/virt-manager/virtinst/distroinstaller.py", line 129, in _prepare_kernel_url > store = self._get_store(guest, fetcher) > File "/usr/share/virt-manager/virtinst/distroinstaller.py", line 116, in _get_store > self._cached_store = urlfetcher.getDistroStore(guest, fetcher) > File "/usr/share/virt-manager/virtinst/urlfetcher.py", line 530, in getDistroStore > dist = _distroFromSUSEContent(fetcher, arch, _type) > File "/usr/share/virt-manager/virtinst/urlfetcher.py", line 395, in _distroFromSUSEContent > cbuf = fetcher.acquireFileContent("content") > File "/usr/share/virt-manager/virtinst/urlfetcher.py", line 176, in acquireFileContent > self._grabURL(filename, fileobj) > File "/usr/share/virt-manager/virtinst/urlfetcher.py", line 96, in _grabURL > total = self._write(urlobj, fileobj) > File "/usr/share/virt-manager/virtinst/urlfetcher.py", line 212, in _write > fileobj.write(data) > TypeError: unicode argument expected, got 'str' When trying the same from SLES, it's OK. -- You are receiving this mail because: You are on the CC list for the bug.

2 2

[Bug 972954] New: hardware/mtx: tapeinfo no shows remaining size
by bugzilla_noreply＠novell.com 25 Nov '20

25 Nov '20

http://bugzilla.opensuse.org/show_bug.cgi?id=972954 Bug ID: 972954 Summary: hardware/mtx: tapeinfo no shows remaining size Classification: openSUSE Product: openSUSE.org Version: unspecified Hardware: x86-64 OS: openSUSE 42.1 Status: NEW Severity: Minor Priority: P5 - None Component: 3rd party software Assignee: jmatejek(a)suse.com Reporter: svalx78(a)gmail.com QA Contact: opensuse-communityscreening(a)forge.provo.novell.com Found By: --- Blocker: --- I has write about 237Gb on to tape by GNU tar and get those tapeinfo output: # tapeinfo -f /dev/nst0 Product Type: Tape Drive Vendor ID: 'HP ' Product ID: 'Ultrium 3-SCSI ' Revision: 'C26D' Attached Changer API: No SerialNumber: '**********' MinBlock: 1 MaxBlock: 16777215 SCSI ID: 16 SCSI LUN: 0 Ready: yes BufferedMode: yes Medium Type: Not Loaded Density Code: 0x44 BlockSize: 0 DataCompEnabled: yes DataCompCapable: yes DataDeCompEnabled: yes CompType: 0x1 DeCompType: 0x1 Block Position: 1933551 Partition 0 Remaining Kbytes: 400308 Partition 0 Size in Kbytes: 400308 ActivePartition: 0 EarlyWarningSize: 0 NumPartitions: 0 MaxPartitions: 0 Firstly, Partition 0 Remaining Kbytes tell me that I no used any tape space. Secondly, if I try to calculate the used space using the MaxBlock and Block Position data, I get obviously wrong value: about 11.5% used. But my backup data is not well compressible - it is video and photo. mt tell give me the same thing: At block 1933551. How to estimate the used space on tape? -- You are receiving this mail because: You are on the CC list for the bug.

2 6

[Bug 928020] New: RTL8723be wireless card disconnects
by bugzilla_noreply＠novell.com 21 Nov '20

21 Nov '20

http://bugzilla.opensuse.org/show_bug.cgi?id=928020 Bug ID: 928020 Summary: RTL8723be wireless card disconnects Classification: openSUSE Product: openSUSE Distribution Version: 13.2 Hardware: x86-64 OS: openSUSE 13.2 Status: NEW Severity: Normal Priority: P5 - None Component: Network Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: roeland.jansen(a)snow.nl QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- hardware: HP Probook 450G2; wireless is RTL8723BE on several different access points (cisco, fritzbox huawei, kpn box, samsung galaxy s4 as ap): traffic stops and you are not able to ping the default gateway anymore. It seems to be random. Sometimes it keeps running for hours; other times it breaks after 10 minutes. The same hardware with windows 8.1 keeps the connection. commands like ""iwlist wlan0 scanning fails at this point with wlan0 Failed to read scan data : Resource temporarily unavailable. at this time. If I # rmmod rtl8723be # rtl8723_common # modprobe rtl8723be the wireless network is functional again. if logs are needed, let me know what you want to look at -- the current logs don't show obvious things. -- You are receiving this mail because: You are on the CC list for the bug.

2 5

[Bug 1057666] New: Log-in screen freezes with NVidia drivers (proprietary) and 2 Monitors (4K and Full-HD)
by bugzilla_noreply＠novell.com 16 Nov '20

16 Nov '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1057666 Bug ID: 1057666 Summary: Log-in screen freezes with NVidia drivers (proprietary) and 2 Monitors (4K and Full-HD) Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: PC OS: openSUSE Factory Status: NEW Severity: Critical Priority: P5 - None Component: Basesystem Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: tobi.goergens(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:55.0) Gecko/20100101 Firefox/55.0 Build Identifier: If I install the NVidia drivers, from the repositories, and reboot with 2 Monitors activated, (4K and Full-HD), the log in screen freezes after about 3 seconds every time. If I start the system with just one monitor connected (it does not matter which), I can log in without problems. There is also no problem, when I turn the 4K monitor off before I see the log in screen, log in just with the Full-HD Monitor detected, and then turn the 4K monitor on again. I think it has to do with the detection of the 4K monitor, because the log in screen freezes every time the 4K monitor is detected by the system. That's why it seems to be a driver problem, it does not happen if I install the open-source driver or the "original" drivers from the Nvidia website. With KDE 5.10.5 installed, directly after new system installation Reproducible: Always Steps to Reproduce: 1. install Nvidia driver from repository 2. install them 3. reboot with 2 Monitors, one has to be 4K 4. have a look at the log-in screen Actual Results: The log-in screen freezes after about 3 seconds, I'm not able to log-in in the graphical environment anymore. Expected Results: detect the 4K monitor correctly and give the chance to log in to the system (can still use terminal with CTRL+ALT+F1, F2...) I wasn't able to find any logs with relevant information, sorry. :( I have an Intel Core I7-6700K, Geforce GTX 1800 and a 4K monitor. -- You are receiving this mail because: You are on the CC list for the bug.

2 7

[Bug 1044910] New: KDE:Qt5/python-qscintilla-qt4: Bug nothing provide python-qscintilla-sip
by bugzilla_noreply＠novell.com 15 Nov '20

15 Nov '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1044910 Bug ID: 1044910 Summary: KDE:Qt5/python-qscintilla-qt4: Bug nothing provide python-qscintilla-sip Classification: openSUSE Product: openSUSE.org Version: unspecified Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: 3rd party software Assignee: fabian(a)ritter-vogt.de Reporter: bruno(a)ioda-net.ch QA Contact: opensuse-communityscreening(a)forge.provo.novell.com Found By: --- Blocker: --- With the last version of spec nothing provide python-qscintilla-sip. zypper se -s --provide python-qscintilla-sip Loading repository data... Reading installed packages... No matching items found. while zypper se -s --provide python-qscintilla Loading repository data... Reading installed packages... S | Name | Type | Version | Arch | Repository ---+---------------------------+---------+--------------+--------+----------- i+ | openSUSE-release | package | 20170617-1.2 | x86_64 | oss v | openSUSE-release | package | 20170617-1.2 | i586 | oss i | python-qscintilla-qt4-sip | package | 2.10-2.1 | x86_64 | oss v | python-qscintilla-qt4-sip | package | 2.10-2.1 | i586 | oss | python-qscintilla-qt5-sip | package | 2.10-2.1 | x86_64 | oss | python-qscintilla-qt5-sip | package | 2.10-2.1 | i586 | oss i+ | python2-qscintilla-qt4 | package | 2.10-2.1 | x86_64 | oss v | python2-qscintilla-qt4 | package | 2.10-2.1 | i586 | oss | python2-qscintilla-qt5 | package | 2.10-2.1 | x86_64 | oss | python2-qscintilla-qt5 | package | 2.10-2.1 | i586 | oss Can we have back the provide for the -sip package it will ease the maintenance of package depending on it. Thanks. -- You are receiving this mail because: You are on the CC list for the bug.

2 6

[Bug 991250] New: VUL-0: CVE-2013-7458: redis: World readable .rediscli_history
by bugzilla_noreply＠novell.com 11 Nov '20

11 Nov '20

http://bugzilla.suse.com/show_bug.cgi?id=991250 Bug ID: 991250 Summary: VUL-0: CVE-2013-7458: redis: World readable .rediscli_history Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.1 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Security Assignee: security-team(a)suse.de Reporter: astieger(a)suse.com QA Contact: qa-bugs(a)suse.de CC: kstreitova(a)suse.com, lars.vogdt(a)microfocus.com, michal.hrusecky(a)opensuse.org, mpluskal(a)suse.com, mrueckert(a)suse.com, mseben(a)gmail.com, nix(a)opensuse.org, pth(a)suse.com Found By: Security Response Team Blocker: --- http://seclists.org/oss-sec/2016/q3/189 https://bugs.debian.org/832460 redis-cli stores its history in ~/.rediscli_history, this file is created with permissions 0644. Home folders are world readable as well in debian, so any user can access other users' redis history, including AUTH commands, which include credentials. I've contacted upstream on 2016-05-30 without any reaction at all and discovered this bug was first reported 3 years ago, still unfixed. @RedisLabs keeps referring to their paid support on twitter. Demo: `cat /home/*/.rediscli_history` Upstream report: https://github.com/antirez/redis/issues/3284 https://github.com/antirez/redis/pull/3322 https://github.com/antirez/redis/pull/1418 References: http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2013-7458 http://seclists.org/oss-sec/2016/q3/189 http://people.canonical.com/~ubuntu-security/cve/2013/CVE-2013-7458.html https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=832460 -- You are receiving this mail because: You are on the CC list for the bug.

2 3