openSUSE Bugs February 2015

bugs@lists.opensuse.org

1 participants
4458 discussions

[Bug 905418] New: No audio/no sound when headphone is plugged in -- choosing "Headphones (unplugged)" in pavucontrol then works
by bugzilla_noreply＠novell.com 29 May '21

29 May '21

http://bugzilla.suse.com/show_bug.cgi?id=905418 Bug ID: 905418 Summary: No audio/no sound when headphone is plugged in -- choosing "Headphones (unplugged)" in pavucontrol then works Classification: openSUSE Product: openSUSE Factory Version: 201411* Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Sound Assignee: tiwai(a)suse.com Reporter: gp(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 613619 --> http://bugzilla.suse.com/attachment.cgi?id=613619&action=edit Screenshot showing pavucontrol vs GNOME Sound panel when external jack is unplugged This is an interesting one, current Factory with kernel 3.16.4-1.g7a8842b-default (and before that also with kernel-default-3.17.1-1.2.g5c4d099 I believe). Sounds on this Lenovo T430s notebook works just fine. Except when I plug in speakers or a headset, instead of switching off the internal speakers and activating that external audio -- silence. The GNOME Sound panel provides no way to address this. pavucontrol, however shows "Headphones (unplugged)", and when I select that as Output Device, everything works as it used to (with 13.1, 13.2 and Factory until a few days ago). 14: PCI 1b.0: 0403 Audio device [Created at pci.328] Unique ID: u1Nb.0TDI6CRLz81 SysFS ID: /devices/pci0000:00/0000:00:1b.0 SysFS BusID: 0000:00:1b.0 Hardware Class: sound Model: "Intel 7 Series/C210 Series Chipset Family High Definition Audio Controller" Vendor: pci 0x8086 "Intel Corporation" Device: pci 0x1e20 "7 Series/C210 Series Chipset Family High Definition Audio Controller" SubVendor: pci 0x17aa "Lenovo" SubDevice: pci 0x21fb Revision: 0x04 Driver: "snd_hda_intel" Driver Modules: "snd_hda_intel" Memory Range: 0xf2530000-0xf2533fff (rw,non-prefetchable) IRQ: 46 (1867 events) Module Alias: "pci:v00008086d00001E20sv000017AAsd000021FBbc04sc03i00" Driver Info #0: Driver Status: snd_hda_intel is active Driver Activation Cmd: "modprobe snd_hda_intel" Config Status: cfg=yes, avail=yes, need=no, active=unknown -- You are receiving this mail because: You are on the CC list for the bug.

2 7

[Bug 911401] New: Wrong yast language when multiple languages specified in LANGUAGE env variable
by bugzilla_noreply＠novell.com 30 Mar '21

30 Mar '21

http://bugzilla.opensuse.org/show_bug.cgi?id=911401 Bug ID: 911401 Summary: Wrong yast language when multiple languages specified in LANGUAGE env variable Classification: openSUSE Product: openSUSE Factory Version: 201412* Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 Assignee: yast2-maintainers(a)suse.de Reporter: PVince81(a)yahoo.fr QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- Steps to reproduce: 1. Make sure that neither LANG nor any LC_* variables are set 2. Run: export LANGUAGE="en_US:de:fr" (or set this language order in KDE's language settings) 3. Run: kdesu yast2 Expected result: Since English is the first language, Yast2 should be in English. Actual result: Yast2 is in German! More info: If you do: - export LANGUAGE="en_US" - kdesu yast2 Yast2 will be in English. It seems zypper is also affected partially. When LANGUAGE="en_US:de:fr" then zypper is in English, but the confirmation prompt is in German: Overall download size: 682.1 MiB. Already cached: 0 B After the operation, additional 753.3 MiB will be used. Fortfahren? [j/n/? zeigt alle Optionen] (j): Could be a duplicate of https://bugzilla.opensuse.org/show_bug.cgi?id=843573 but that one didn't have any details. -- 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 899104] New: KDE complains about X-KDE-Library from yast desktop files
by bugzilla_noreply＠novell.com 08 Jan '21

08 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 18 Dec '20

18 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 915168] New: During boot message i2c_hid i2c-SYN1B7E:01: failed to retrieve report from device. is shown
by bugzilla_noreply＠novell.com 07 Jul '20

07 Jul '20

http://bugzilla.opensuse.org/show_bug.cgi?id=915168 Bug ID: 915168 Summary: During boot message i2c_hid i2c-SYN1B7E:01: failed to retrieve report from device. is shown Classification: openSUSE Product: openSUSE Factory Version: 201501* Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-maintainers(a)forge.provo.novell.com Reporter: freek(a)opensuse.org QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- On my Acer laptop with Intel N3530 and apparently a touchpad with name SYN1B7E I see the following: During boot message: i2c_hid i2c-SYN1B7E:01: failed to retrieve report from device. is shown. Ifound some reference about this device in http://www.adamdrew.net/?tag=kernel -- You are receiving this mail because: You are on the CC list for the bug.

2 8

[Bug 904210] New: package link not shown in web UI
by bugzilla_noreply＠novell.com 24 Jun '20

24 Jun '20

http://bugzilla.opensuse.org/show_bug.cgi?id=904210 Bug ID: 904210 Summary: package link not shown in web UI Classification: openSUSE Product: openSUSE.org Version: unspecified Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: BuildService Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: nico.kruber(a)gmail.com QA Contact: adrian(a)suse.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:33.0) Gecko/20100101 Firefox/33.0 Build Identifier: if repo B is based on repo A which contains package C, then linking to B:C (without C being directly available in B) produces no UI elements to show (un)expanded sources in the web UI, neither is the link shown as such ("links to ...") example: https://build.opensuse.org/package/show/KDE:Extra/PackageKit https://build.opensuse.org/package/show/KDE:Extra/PackageKit?expand=0 https://build.opensuse.org/package/show/KDE:Extra/PackageKit?expand=1 Reproducible: Always Steps to Reproduce: 1. create link to a package in openSUSE:13.2:Update which is only available in openSUSE:13.2 2. browse to that link Actual Results: the link exists but is not shown as such Expected Results: same UI as if the package was linked to openSUSE:13.2 directly -- You are receiving this mail because: You are on the CC list for the bug.

2 2

[Bug 911001] New: dnsmasq apparmor profile prevents libvirt default network to start
by bugzilla_noreply＠novell.com 05 Jun '20

05 Jun '20

http://bugzilla.suse.com/show_bug.cgi?id=911001 Bug ID: 911001 Summary: dnsmasq apparmor profile prevents libvirt default network to start Classification: openSUSE Product: openSUSE Factory Version: 201412* Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: AppArmor Assignee: suse-beta(a)cboltz.de Reporter: cbosdonnat(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- This commit in libvirt forces dnsmasq to actually use the leaseshelper program: http://libvirt.org/git/?p=libvirt.git;a=commit;h=421406808abaf7eb66abd27d71… The problem is that the dnsmasq apparmor profile prevents the libvirt default network to start due to: * Not allowing /bin/bash to be run * Not allowing leaseshealper contained in /usr/lib64 folder to be run. Note that this bug may hit 13.2 if an updated libvirt is shipped there. -- You are receiving this mail because: You are on the CC list for the bug.

2 2

[Bug 894783] New: CA management: Sign Request: Don't use sequential serial numbers
by bugzilla_noreply＠novell.com 27 Apr '20

27 Apr '20

https://bugzilla.novell.com/show_bug.cgi?id=894783 https://bugzilla.novell.com/show_bug.cgi?id=894783#c0 Summary: CA management: Sign Request: Don't use sequential serial numbers Classification: openSUSE Product: openSUSE 12.3 Version: Final Platform: All OS/Version: All Status: NEW Severity: Enhancement Priority: P5 - None Component: YaST2 AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: Ulrich.Windl(a)rz.uni-regensburg.de QAContact: jsrain(a)suse.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux i686; rv:31.0) Gecko/20100101 Firefox/31.0 (In openssl tradition certificates use sequential serial numbers) YaST's certificate signing function uses sequential serial numbers to issue (sign) certificates (like 01, 02, 03, ... 09, 0A, 0B, ...) Due to some weaknesses in SHA-1, there's a recommendation to use serial numbers with a higher entropy. See https://www.bsi.bund.de/SharedDocs/Downloads/DE/BSI/ElekSignatur/BSI_SHA1_Z… (German): ---BEGIN quote--- Kollisionsangriffe gegen die Zertifikaterstellung mit SHA-1 können von vornherein verhindert werden, wenn folgendes gilt: 1) Es wird das X.509v3 Format gemäß ISIS-MTT verwendet. 2) Die Seriennummer ("serialNumber") des Zertifikats hat eine genügend hohe Entropie h für den Angreifer. D.h. die Unsicherheit des Angreifers über die Seriennummer eines zu erstellenden Zertifikats ist mindestens h Bits. (...) ---END quote--- Reproducible: Always Steps to Reproduce: 1. Sign a certificate request (CSR) in YaST's CA management Actual Results: The certificate gets a serial number that can easily be guessed Expected Results: The serial number should not be easy to guess See also http://www.heise.de/security/meldung/Fragwuerdige-Hash-Funktion-SHA-1-immer… (German) -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 5

Jump to page:

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

openSUSE Bugs February 2015