December 2015 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 934256] New: Passwords maintained by Filezilla are easily recovered in some cases
by bugzilla_noreply＠novell.com 19 Mar '21

19 Mar '21

http://bugzilla.opensuse.org/show_bug.cgi?id=934256 Bug ID: 934256 Summary: Passwords maintained by Filezilla are easily recovered in some cases Classification: openSUSE Product: openSUSE Distribution Version: 13.2 Hardware: Other OS: openSUSE 13.2 Status: NEW Severity: Normal Priority: P5 - None Component: Security Assignee: security-team(a)suse.de Reporter: Greg.Freemyer(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- I'm testing with LaZagne: http://www.kitploit.com/2015/02/the-lazagne-project-recover-most-common.html Or in OBS @ home:gregfreemyer:Tools-for-forensic-boot-cd LaZagne Running LaZagne under my normal user account recovered one filezilla stored passwd. The amount of time taken was near instantaneous so I believe the password was simply decoded, not cracked in the sense of "John the ripper". The password was associated with a SFTP account, so it is a password I consider needing to be kept securely. I don't know if Filezilla simply handles passwords poorly or if it can be compiled differently to store passwords securely. -- You are receiving this mail because: You are on the CC list for the bug.

2 2

[Bug 918028] New: no Grub Legacy shell history
by bugzilla_noreply＠novell.com 19 Mar '21

19 Mar '21

http://bugzilla.opensuse.org/show_bug.cgi?id=918028 Bug ID: 918028 Summary: no Grub Legacy shell history Classification: openSUSE Product: openSUSE Distribution Version: 13.2 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Bootloader Assignee: jsrain(a)suse.com Reporter: mrmazda(a)earthlink.net QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- To reproduce: 1-login root on tty[1-6] on en_US installation 2-grub 3-find /boot/grub/stage1 4-keystroke <UP> Actual behavior: 1-^[[A appears at prompt Expected behavior: 1-find /boot/grub/stage1 appears at prompt Comments: 1-Shell cmdline history works as expected in 13.1, as in all previous openSUSE releases. 2-I recognized this problem many months ago, maybe as much as a year ago, but only just surmised it was almost certainly 13.2 and up Grub Legacy post-0.97-194.1.2 itself rather than having anything to do with kernel, framebuffer configuration, video mode, or files contained in target /boot/grub/. "Downgrading" to 13.1's 0.97-194.1.2 fixes 13.2 and Tumbleweed. 3-Nearly all my Grub stanzas include "splash=verbose vga=791 video=1024x768@60 3 " on cmdline. 4-All my openSUSE installations are on multiboot hardware (no VMs), with keyboards on PS/2 ports. 5-Plymouth is not installed in any of my openSUSE installations. -- You are receiving this mail because: You are on the CC list for the bug.

2 8

[Bug 912059] New: networkmanager plasmoid shows nearly everybody connected (although it seems that only one wpa2 is correctly connected
by bugzilla_noreply＠novell.com 11 Feb '21

11 Feb '21

http://bugzilla.opensuse.org/show_bug.cgi?id=912059 Bug ID: 912059 Summary: networkmanager plasmoid shows nearly everybody connected (although it seems that only one wpa2 is correctly connected Classification: openSUSE Product: openSUSE Distribution Version: 13.2 Hardware: x86-64 OS: openSUSE 13.2 Status: NEW Severity: Minor Priority: P5 - None Component: KDE4 Applications Assignee: kde-maintainers(a)suse.de Reporter: stakanov(a)freenet.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 618858 --> http://bugzilla.opensuse.org/attachment.cgi?id=618858&action=edit wrong connection info of networkmanager plugin Create several users. Create in user A a connection with wpa2 encryption, choose: only this user can connect. Save and connect. Look at the list of the plasmoid: it shows all available wlan as not connected and the one you created as connected. Now change to user B or C. As you are still up with user A and you are connected, now in user B or C it should show the same as in user A. Only it should not be possible to end simply this connection or to start it. But you will be able to use it. What happens: in B or C respectively, the list of all available stations shows up as "connected". So in theory you are connected to all wireless of the area. All? No, some do show up correctly as "not connected" but the list here is so long that I can show only the beginning of the screen-shot. The output of ifconfig and netstat seem normal. So this seems to be more an apparent than a real bug. I join a screenshot. What should have done the program: show the correct connection information. Screen-shot: the only "real" connection iw the one with the button disconnect. The other ssids are from the neighborhood. -- You are receiving this mail because: You are on the CC list for the bug.

2 3

[Bug 956264] New: cobbler_web apache config uses old syntax
by bugzilla_noreply＠novell.com 14 Jan '21

14 Jan '21

http://bugzilla.suse.com/show_bug.cgi?id=956264 Bug ID: 956264 Summary: cobbler_web apache config uses old syntax Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.1 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Installation Assignee: yast2-maintainers(a)suse.de Reporter: osynge(a)suse.com QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- Please set up cobbler and cobbler_web to use new syntax. Require all granted instead of Order allow,deny Allow from all See http://httpd.apache.org/docs/2.4/upgrading.html. -- You are receiving this mail because: You are on the CC list for the bug.

2 8

[Bug 956153] New: Software Update Error "License Agreement Failed" But A License Agreement Is Never Presented
by bugzilla_noreply＠novell.com 08 Jan '21

08 Jan '21

http://bugzilla.opensuse.org/show_bug.cgi?id=956153 Bug ID: 956153 Summary: Software Update Error "License Agreement Failed" But A License Agreement Is Never Presented Classification: openSUSE Product: openSUSE Tumbleweed Version: 2015* Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Maintenance Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: bill_wayson(a)yahoo.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 656868 --> http://bugzilla.opensuse.org/attachment.cgi?id=656868&action=edit Zip file with error message screenshot, zypper.log, and pk_backend_zypp files On Saturday morning (11/21/2015 PST) I am presented with 246 updates by the software updater. I press the "Install Updates" button, and the update begins. But it quickly stops with a message dialog "Update Error The license agreement failed. The license agreement was not agreed to. To use this software you have to accept the license." The problems are that a license agreement dialog is never presented, and there is no indication of which of the 246 updates require the license agreement (so that I can, say, deselect it). I have attached a zip file that contains a screenshot of the message along with the zypper.log and pk_backend_zypp files. The latter file appears to be the log updated by the software updater. My tumbleweed is currently at 20151113. I hope I chose the correct component. -- You are receiving this mail because: You are on the CC list for the bug.

2 9

[Bug 954603] New: Leap lacks tomcat
by bugzilla_noreply＠novell.com 07 Jan '21

07 Jan '21

http://bugzilla.suse.com/show_bug.cgi?id=954603 Bug ID: 954603 Summary: Leap lacks tomcat Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.1 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Java Assignee: bnc-team-java(a)forge.provo.novell.com Reporter: tchvatal(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Leap lacks tomcat as it didn't build. I will submit fixed dbcp that should go later as maint-update to SLE12 directly and for tomcat we can grab 1:1 the SLE-12:SP1 counterpart. -- You are receiving this mail because: You are on the CC list for the bug.

2 11

[Bug 899104] New: KDE complains about X-KDE-Library from yast desktop files
by bugzilla_noreply＠novell.com 07 Jan '21

07 Jan '21

http://bugzilla.suse.com/show_bug.cgi?id=899104 Bug ID: 899104 Summary: KDE complains about X-KDE-Library from yast desktop files Classification: openSUSE Product: openSUSE Factory Version: 201409* Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 Assignee: yast2-maintainers(a)suse.de Reporter: lnussel(a)suse.com QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- See https://openqa.opensuse.org/tests/25123/file/XSE KDE complains about the X-KDE-Library entries in yast's desktop files. -- You are receiving this mail because: You are on the CC list for the bug.

2 7

[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 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 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