May 2019 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 954329] New: Purely virtual bridge breaks networking
by bugzilla_noreply＠novell.com 08 Feb '22

08 Feb '22

http://bugzilla.suse.com/show_bug.cgi?id=954329 Bug ID: 954329 Summary: Purely virtual bridge breaks networking Classification: openSUSE Product: openSUSE Tumbleweed Version: 2015* Hardware: Other OS: Other Status: NEW Severity: Major Priority: P5 - None Component: Network Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: lmb(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Take a purely virtual bridge (to be used for VMs) with a static network configuration: # cat /etc/sysconfig/network/ifcfg-br0 STARTMODE='auto' BOOTPROTO='static' BRIDGE='yes' BRIDGE_PORTS='' BRIDGE_FORWARDDELAY='0' BRIDGE_STP='off' IPADDR='172.16.1.1/24' enp0s25 is the local, normal ethernet interface which is working fine: 2: enp0s25: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP mode DEFAULT group default qlen 1000 Now: # ifup br0 # ip link 2: enp0s25: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master br0 state UP mode DEFAULT group default qlen 1000 link/ether 28:d2:44:df:33:18 brd ff:ff:ff:ff:ff:ff 9: br0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DEFAULT group default qlen 1000 link/ether 28:d2:44:df:33:18 brd ff:ff:ff:ff:ff:ff It seems that the scripts use the ethernet interface as the *default* value for BRIDGE_PORTS, which obviously then breaks networking. (If I had wanted a slaved network device, I'd have configured one.) brctl addbr br0 ; ip a add dev br0 172.16.1.1/24 ; ip link set br0 up creates the desired configuration just fine and is what I'd have expected given the configuration file. -- You are receiving this mail because: You are on the CC list for the bug.

2 9

[Bug 1057592] New: Cannot connect to EAP secured wireless network with wicked
by bugzilla_noreply＠novell.com 08 Feb '22

08 Feb '22

http://bugzilla.suse.com/show_bug.cgi?id=1057592 Bug ID: 1057592 Summary: Cannot connect to EAP secured wireless network with wicked Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Major Priority: P5 - None Component: Network Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: lmb(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- I have trouble connecting my laptop to a PEAP secured wireless network, embarrassingly the AttachemateGroup one at SUSE HQ. The network settings seem to be right and match: BOOTPROTO='dhcp' BROADCAST='' DHCLIENT_SET_DEFAULT_ROUTE='yes' ETHTOOL_OPTIONS='' IPADDR='' MTU='' NAME='Wireless 7260' NETMASK='' NETWORK='' REMOTE_IPADDR='' STARTMODE='manual' WIRELESS_AP='' WIRELESS_AP_SCANMODE='1' WIRELESS_AUTH_MODE='eap' WIRELESS_BITRATE='auto' WIRELESS_CA_CERT='' WIRELESS_CHANNEL='' WIRELESS_CLIENT_CERT='' WIRELESS_CLIENT_KEY='' WIRELESS_CLIENT_KEY_PASSWORD='' WIRELESS_DEFAULT_KEY='0' WIRELESS_EAP_AUTH='MSCHAPV2' WIRELESS_EAP_MODE='PEAP' WIRELESS_ESSID='AttachmateGroup' WIRELESS_FREQUENCY='' WIRELESS_KEY='' WIRELESS_KEY_0='' WIRELESS_KEY_1='' WIRELESS_KEY_2='' WIRELESS_KEY_3='' WIRELESS_KEY_LENGTH='128' WIRELESS_MODE='Managed' WIRELESS_NICK='' WIRELESS_NWID='' WIRELESS_PEAP_VERSION='' WIRELESS_POWER='no' WIRELESS_WPA_ANONID='' WIRELESS_WPA_IDENTITY='lmb' WIRELESS_WPA_PASSWORD='xxxxxxxx' WIRELESS_WPA_PSK='' Sep 07 13:44:40 hermes kernel: iwlwifi 0000:03:00.0: L1 Enabled - LTR Enabled Sep 07 13:44:43 hermes kernel: wlp3s0: authenticate with f0:5c:19:1f:93:f0 Sep 07 13:44:43 hermes kernel: wlp3s0: send auth to f0:5c:19:1f:93:f0 (try 1/3) Sep 07 13:44:43 hermes kernel: wlp3s0: authenticated Sep 07 13:44:43 hermes kernel: wlp3s0: associate with f0:5c:19:1f:93:f0 (try 1/3) Sep 07 13:44:43 hermes kernel: wlp3s0: RX AssocResp from f0:5c:19:1f:93:f0 (capab=0x1411 status=0 aid=9) Sep 07 13:44:43 hermes kernel: wlp3s0: associated Sep 07 13:44:43 hermes wickedd-dhcp4[1521]: wlp3s0: Request to acquire DHCPv4 lease with UUID 4957ae59-c728-0b00-f205-000033000000 Sep 07 13:44:43 hermes kernel: wlp3s0: Limiting TX power to 23 (23 - 0) dBm as advertised by f0:5c:19:1f:93:f0 Sep 07 13:44:46 hermes kernel: wlp3s0: deauthenticating from f0:5c:19:1f:93:f0 by local choice (Reason: 3=DEAUTH_LEAVING) Sep 07 13:44:53 hermes wickedd-dhcp4[1521]: unable to confirm lease Sep 07 13:44:58 hermes wickedd-dhcp4[1521]: wlp3s0: defer timeout 15 reached (state INIT) Sep 07 13:45:00 hermes kernel: wlp3s0: authenticate with f0:5c:19:1f:97:f0 Sep 07 13:45:00 hermes kernel: wlp3s0: send auth to f0:5c:19:1f:97:f0 (try 1/3) Sep 07 13:45:00 hermes kernel: wlp3s0: authenticated Sep 07 13:45:00 hermes kernel: wlp3s0: associate with f0:5c:19:1f:97:f0 (try 1/3) Sep 07 13:45:00 hermes kernel: wlp3s0: RX AssocResp from f0:5c:19:1f:97:f0 (capab=0x1411 status=0 aid=13) Sep 07 13:45:00 hermes kernel: wlp3s0: associated Sep 07 13:45:00 hermes wickedd-dhcp4[1521]: wlp3s0: Request to acquire DHCPv4 lease with UUID 4957ae59-c728-0b00-f205-000033000000 Sep 07 13:45:00 hermes kernel: wlp3s0: Limiting TX power to 30 (30 - 0) dBm as advertised by f0:5c:19:1f:97:f0 Sep 07 13:45:03 hermes kernel: wlp3s0: deauthenticating from f0:5c:19:1f:97:f0 by local choice (Reason: 3=DEAUTH_LEAVING) Sep 07 13:45:10 hermes wickedd-dhcp4[1521]: unable to confirm lease Sep 07 13:45:15 hermes wickedd-dhcp4[1521]: wlp3s0: defer timeout 15 reached (state INIT) Sep 07 13:45:41 hermes kernel: wlp3s0: authenticate with f0:5c:19:1f:93:e0 Sep 07 13:45:41 hermes kernel: wlp3s0: send auth to f0:5c:19:1f:93:e0 (try 1/3) Sep 07 13:45:41 hermes kernel: wlp3s0: f0:5c:19:1f:93:e0 denied authentication (status 17) Sep 07 13:45:43 hermes wickedd-nanny[1523]: device wlp3s0: got signal linkDown Sep 07 13:45:43 hermes kernel: wlp3s0: authenticate with f0:5c:19:1f:93:e0 Sep 07 13:45:43 hermes kernel: wlp3s0: send auth to f0:5c:19:1f:93:e0 (try 1/3) Sep 07 13:45:43 hermes kernel: wlp3s0: aborting authentication with f0:5c:19:1f:93:e0 by local choice (Reason: 3=DEAUTH_LEAVING) So there are a bunch of successful authentication attempts, but then DHCP doesn't work. Eventually the server throws me out again though. And no, the password is not incorrect. ;-) -- You are receiving this mail because: You are on the CC list for the bug.

2 8

[Bug 1091864] New: [RPM] The %make_install macro from marcos.cmake gets overwritten by macro.qt5
by bugzilla_noreply＠novell.com 08 Feb '22

08 Feb '22

http://bugzilla.suse.com/show_bug.cgi?id=1091864 Bug ID: 1091864 Summary: [RPM] The %make_install macro from marcos.cmake gets overwritten by macro.qt5 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Development Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: asn(a)cryptomilk.org QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- The cmake macros allow you to use ninja [1]. However it doesn't work if macros.qt5 is installed because it overwrite the macro. Instead of ninja, make is called. [1] https://en.opensuse.org/openSUSE:Build_system_recipes#cmake -- You are receiving this mail because: You are on the CC list for the bug.

2 24

[Bug 1089938] New: yast-samba-client fails to join if /etc/samba/smb.conf or /etc/krb5.conf don't exist
by bugzilla_noreply＠novell.com 03 Feb '22

03 Feb '22

http://bugzilla.suse.com/show_bug.cgi?id=1089938 Bug ID: 1089938 Summary: yast-samba-client fails to join if /etc/samba/smb.conf or /etc/krb5.conf don't exist Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Samba Assignee: samba-maintainers(a)SuSE.de Reporter: david.mulder(a)suse.com QA Contact: samba-maintainers(a)SuSE.de Found By: --- Blocker: --- # sudo rm /etc/samba/smb.conf /etc/krb5.conf Join fails with "Cannot use the Workgroup xxxx for linux authentication" # sudo touch /etc/samba/smb.conf Join begins, but fails with "Failed to join domain: failed to connect to AD: Included profile file could not be read" # sudo touch /etc/krb5.conf Join succeeds and stubs out the smb.conf and krb5.conf files. -- You are receiving this mail because: You are on the CC list for the bug.

2 3

[Bug 996088] New: After updates today (29/08/16) efibootmgr: Could not set BootOrder: No space left on device
by bugzilla_noreply＠novell.com 28 Jan '22

28 Jan '22

http://bugzilla.opensuse.org/show_bug.cgi?id=996088 Bug ID: 996088 Summary: After updates today (29/08/16) efibootmgr: Could not set BootOrder: No space left on device Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Bootloader Assignee: jsrain(a)suse.com Reporter: stuart(a)stella-maris.org.uk QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- After performing an update today, 29/08/16, I decided to run efibootmgr -v as I have had issues before. I then found it returned BootCurrent: 0003 Timeout: 1 seconds No BootOrder is set; firmware will attempt recovery Boot0000* opensuse HD(1,GPT,2eca2750-fed6-4e3f-887f-27f183020fda,0x800,0x61800)/File(\EFI\opensuse\grubx64.efi) Boot0001* Hard Drive BBS(HD,,0x0) Boot0002* CD/DVD Drive BBS(CDROM,,0x0) After which I ran efibootmgr -o 0000,0001,0002 which returned efibootmgr: Could not set BootOrder: No space left on device I then tried both update-bootloader --reinit which failed, then grub2-install which failed as well. This ended up with no efi boot options at all. I had to resort to chrooting from TW rescue disk and re-install grub2 and recover my PC. So far I have not tried to run the update-bootloader --reinit or grub2-install again since recovering my system as I fear it will mess up the system once more. As part of the update various grub2 packages were updated all not at beta3-10 level, the zypper history shows dracut running but no apparent errors were reported there. -- You are receiving this mail because: You are on the CC list for the bug.

2 9

[Bug 1111728] New: Out of date package: openSUSE:Factory/efibootmgr
by bugzilla_noreply＠novell.com 28 Jan '22

28 Jan '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1111728 Bug ID: 1111728 Summary: Out of date package: openSUSE:Factory/efibootmgr Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: sean(a)suspend.net QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- https://build.opensuse.org/package/show/openSUSE:Factory/efibootmgr is out of date (14). Current upstream is https://github.com/rhinstaller/efibootmgr/releases/download/17/efibootmgr-1…. -- You are receiving this mail because: You are on the CC list for the bug.

2 5

[Bug 1093071] New: YaST constantly steals focus
by bugzilla_noreply＠novell.com 24 Jan '22

24 Jan '22

http://bugzilla.suse.com/show_bug.cgi?id=1093071 Bug ID: 1093071 Summary: YaST constantly steals focus Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: openSUSE Factory Status: NEW Severity: Major Priority: P5 - None Component: YaST2 Assignee: yast2-maintainers(a)suse.de Reporter: okurz(a)suse.com QA Contact: jsrain(a)suse.com CC: ben.kevan(a)bio-rad.com, casualprogrammer(a)opensuse.org, cyberorg(a)opensuse.org, diego.ercolani(a)gmail.com, ensonic(a)sonicpulse.de, federico(a)suse.com, francis(a)opensuse.org, gabriel(a)opensuse.org, jdsn(a)suse.com, jonas(a)jonasbjork.net, l_v_brienen(a)casema.nl, m.moeller(a)opensuse.org, Markus.Elfring(a)web.de, martin(a)oneiros.de, mmeeks(a)suse.com, ptomes(a)gmail.com, ric8cruz(a)gmail.com, Roland.Kletzing(a)dguv.de, sbrabec(a)suse.com, tilman(a)imap.cc, Ulrich.Windl(a)rz.uni-regensburg.de, volker_apelt(a)yahoo.de Found By: --- Blocker: --- +++ This bug was initially created as a clone of Bug #326158 +++ ## Observation There are a lot of very old bugs already and at least in the current state seems like the behaviour described in these bugs is still present: YaST during some actions, especially package installation (but not in the "software management" module itself), opens many popup dialogs and steals the focus preventing to work with the system while yast does its actions ## Steps to reproduce * In an installed system, open the yast control center, open "Remote Administration (VNC)", enable any of the Remote Administration options and confirm * Confirm installation of necessary package and minimize or focus another application * Observe how the yast configuration dialog gains focus again (unminimized) ## Expected result * For minimised YaST progress dialogs should never popup * progress dialogs should not get focus for unfocussed foreground applications ## Further details Seems this has been reported already many times so it might be interesting to dig a bit into history here: * https://bugzilla.suse.com/show_bug.cgi?id=326158 * https://bugzilla.suse.com/show_bug.cgi?id=331835 * https://bugzilla.suse.com/show_bug.cgi?id=34759 * https://bugzilla.suse.com/show_bug.cgi?id=334631 * https://bugzilla.suse.com/show_bug.cgi?id=615927 * https://bugzilla.suse.com/show_bug.cgi?id=372319 * https://bugzilla.suse.com/show_bug.cgi?id=74073 * https://bugzilla.suse.com/show_bug.cgi?id=330649 * https://bugzilla.suse.com/show_bug.cgi?id=297642 * https://bugzilla.suse.com/show_bug.cgi?id=298071 -- You are receiving this mail because: You are on the CC list for the bug.

2 6

[Bug 1131437] New: dbench4 regression with 5.0 kernel on anderson and marvin7
by bugzilla_noreply＠novell.com 21 Jan '22

21 Jan '22

http://bugzilla.suse.com/show_bug.cgi?id=1131437 Bug ID: 1131437 Summary: dbench4 regression with 5.0 kernel on anderson and marvin7 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-maintainers(a)forge.provo.novell.com Reporter: jack(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Our performance dashboard shows significant regressions (up to 20%) for dbench4 on anderson and marvin7 especially on XFS filesystem but to some extent also on ext4. This appears both with and without mitigations. -- You are receiving this mail because: You are on the CC list for the bug.

2 25

[Bug 1084804] New: Plasma + Wayland: input method does not start
by bugzilla_noreply＠novell.com 19 Jan '22

19 Jan '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1084804 Bug ID: 1084804 Summary: Plasma + Wayland: input method does not start Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.0 Hardware: Other OS: Other Status: NEW Severity: Major Priority: P5 - None Component: KDE Workspace (Plasma) Assignee: opensuse-kde-bugs(a)opensuse.org Reporter: ftake(a)geeko.jp QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- On Plasma + Wayland session, input method like IBus, Fcitx does not start anymore. This is simply because /etc/X11/xim, which has been a script to launch one of input methods, is not executed on a Wayland session. So we need to update our input method launcher script to support Wayland. How can we do that? What is the right way to set environment variables such as GTK_IM_MODULE and QT_IM_MODULE according to the current selected input method under on Wayland session? Workaround: Set GTK_IM_MODULE and QT_IM_MODULE in ~/.i18n and start ibus-daemon -xd or fcitx by using KDE auto start settings. However, both IBus and Fcitx will not work correctly due to other bugs and limitations related to Wayland. -- You are receiving this mail because: You are on the CC list for the bug.

2 9

[Bug 1047498] New: gnuhealth not installable
by bugzilla_noreply＠novell.com 17 Jan '22

17 Jan '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1047498 Bug ID: 1047498 Summary: gnuhealth not installable Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.3 Hardware: Other OS: Other Status: NEW Severity: Critical Priority: P5 - None Component: Other Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: fvogt(a)suse.com QA Contact: qa-bugs(a)suse.de CC: axel.braun(a)gmx.de, okurz(a)suse.com Found By: --- Blocker: --- Found by openQA (https://openqa.opensuse.org/tests/441262#step/gnuhealth_install/12) and confirmed by installcheck: can't install gnuhealth-3.2.0-1.1.noarch: nothing provides python3-caldav needed by gnuhealth-3.2.0-1.1.noarch nothing provides python3-cracklib needed by gnuhealth-3.2.0-1.1.noarch nothing provides python3-pyBarcode needed by gnuhealth-3.2.0-1.1.noarch -- You are receiving this mail because: You are on the CC list for the bug.

2 9

[Bug 1125433] New: gvfs: removal of /usr/share/polkit-1/rules.d/org.gtk.vfs.file-operations.rules
by bugzilla_noreply＠novell.com 17 Jan '22

17 Jan '22

http://bugzilla.suse.com/show_bug.cgi?id=1125433 Bug ID: 1125433 Summary: gvfs: removal of /usr/share/polkit-1/rules.d/org.gtk.vfs.file-operation s.rules Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Security Assignee: bnc-team-gnome(a)forge.provo.novell.com Reporter: matthias.gerstner(a)suse.com QA Contact: qa-bugs(a)suse.de CC: security-team(a)suse.de Found By: --- Blocker: --- As described in bug 1125314 we want to remove polkit rules files that grant members of the wheel group special privileges. gvfsd-backends ships one such rules file in /usr/share/polkit-1/rules.d/org.gtk.vfs.file-operations.rules. This file is currently not effective anyways, because the polkit-default-privs take precendence over it. I suggest to move this file to /usr/share/doc/... as an example for users that want to manually enable this rule on their system. -- You are receiving this mail because: You are on the CC list for the bug.

2 14

[Bug 966599] New: home:j-engel/bacula: Bug
by bugzilla_noreply＠novell.com 15 Jan '22

15 Jan '22

http://bugzilla.opensuse.org/show_bug.cgi?id=966599 Bug ID: 966599 Summary: home:j-engel/bacula: Bug Classification: openSUSE Product: openSUSE.org Version: unspecified Hardware: x86-64 OS: openSUSE 13.2 Status: NEW Severity: Normal Priority: P5 - None Component: 3rd party software Assignee: jcnengel(a)gmail.com Reporter: marc(a)marcchamberlin.com QA Contact: opensuse-communityscreening(a)forge.provo.novell.com Found By: --- Blocker: --- Tried to download/install Bacula 7.4.0 using the 1 click installer and downloading the RPM package. I get the following error - nothing provides libbaccats-7.4.0.so()(64bit) needed by bacula-7.4.0-6.2.x86_64 -- You are receiving this mail because: You are on the CC list for the bug.

2 1

[Bug 940478] New: ASL: rename conflicting-confusing package
by bugzilla_noreply＠novell.com 14 Jan '22

14 Jan '22

http://bugzilla.opensuse.org/show_bug.cgi?id=940478 Bug ID: 940478 Summary: ASL: rename conflicting-confusing package Classification: openSUSE Product: openSUSE Factory Version: 201505* Hardware: All OS: All Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: alinm.elena(a)gmail.com Reporter: jengelh(a)inai.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- openSUSE:Factory already has an "asl" package, and recently gained an "ASL" package. This very same name is, I will argue, confusing for both users and developers, as they only differ in case, and case is not something people pay sufficient attention to when e.g. reporting bugs or discussing. I suggest to rename the ASL package. Considering that "asl library" yields lots of different things on Google already, a package name like "advsimlib" might work better than "asllib". Confer with the asl.org.il team perhaps. [ The current plan is to reject, in the direct future, same-name submissions to Factory which only differ in casing. On a related notem, libzypp even falls over currently (but probably intentionally; see bug #940477). ] -- You are receiving this mail because: You are on the CC list for the bug.

2 3

[Bug 1089434] New: enchant-2 voikko backend installed but not hunspell backend despite en.GB language settings
by bugzilla_noreply＠novell.com 13 Jan '22

13 Jan '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1089434 Bug ID: 1089434 Summary: enchant-2 voikko backend installed but not hunspell backend despite en.GB language settings Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Major Priority: P5 - None Component: GNOME Assignee: bnc-team-gnome(a)forge.provo.novell.com Reporter: badshah400(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- This must have happened fairly recently, but I noticed only after finding every English word marked in red when composing emails. Apparently, enchant-2 does not automatically install the hunspell backend despite one's locale setting being set to en.GB. The voikko backend is installed, however, thus automatically treating all spell-checking inputs as Finnish (and marking them obviously). Manually installing enchant-2-backend-hunspell did the trick, since the correct myspell dicts were already installed. -- You are receiving this mail because: You are on the CC list for the bug.

2 10

[Bug 1116225] New: qemu ALSA backend broken
by bugzilla_noreply＠novell.com 05 Jan '22

05 Jan '22

http://bugzilla.suse.com/show_bug.cgi?id=1116225 Bug ID: 1116225 Summary: qemu ALSA backend broken 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: tiwai(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- It seems that qemu ALSA backend is broken. When I start an audio playback on VM, the whole VM including GUI stalls. Tested qemu 3.0.0 with qemu-audio-alsa package. Switching to PA backend seems working, so this might be specific to the audio backend. -- You are receiving this mail because: You are on the CC list for the bug.

2 10

[Bug 1060506] New: libkolabxml packages differ for every build
by bugzilla_noreply＠novell.com 03 Jan '22

03 Jan '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1060506 Bug ID: 1060506 Summary: libkolabxml packages differ for every build Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: openSUSE Factory Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: lbeltrame(a)kde.org Reporter: bwiedemann(a)suse.com QA Contact: qa-bugs(a)suse.de CC: matthias(a)mailaender.name Found By: Development Blocker: --- When working on the reproducible builds project for openSUSE I found that libkolabxml packages differ for every build unless ASLR is disabled in the build system. This indicates either usage of unitinialized memory (compare [1]) or using (randomized) pointers in output. /usr/lib64/libkolabxml.so.1.1.6 differs because of /home/abuild/rpmbuild/BUILD/libkolabxml-1.1.6/build/kolabformat-xcal-schema.cxx 2018-10-30 08:42:53.622040000 +0000 @@ -9014,9 +9014,9 @@ 0x00, 0x01, 0x6d, 0x09, 0x00, 0x01, 0x3f, 0x07, 0x00, 0x01, 0x23, 0x07, 0x00, 0x01, 0x53, 0x0a, 0x00, 0x01, 0x68, 0x07, 0x00, 0x01, 0x7f, 0x09, 0x00, 0x01, 0x4e, 0x04, 0x00, 0x01, 0xfe, 0xff, 0xff, 0xff, 0x1d, 0x00, - 0x06, 0x0e, 0x00, 0x06, 0xe8, 0x08, 0x00, 0x01, 0xff, 0xff, 0xff, 0xff, + 0x06, 0x0e, 0x00, 0x06, 0x25, 0x07, 0x00, 0x01, 0xff, 0xff, 0xff, 0xff, 0x00, 0x03, 0x0c, 0x00, 0x06, 0x58, 0x53, 0x41, 0x6e, 0x6e, 0x6f, 0x74, - 0x61, 0x74, 0x69, 0x6f, 0x6e, 0x00, 0x03, 0x11, 0x09, 0x00, 0x05, 0x3c, + 0x61, 0x74, 0x69, 0x6f, 0x6e, 0x00, 0x03, 0xb6, 0x01, 0x00, 0x05, 0x3c, 0x00, 0xff, 0x78, 0x73, 0x3a, 0x61, 0x6e, 0x6e, 0x6f, 0x74, 0x61, 0x74, [...] which probably comes from # Compile Schemas add_custom_command(OUTPUT kolabformat-xcal-schema.cxx COMMAND ${XSDBIN} --verbose --array-name iCalendar_schema --output-dir ${CMAKE_BINARY_DIR} ${SCHEMAS} which might be from ./compiled/xsdbin.cxx and/or involving the xsd package [1] https://build.opensuse.org/package/view_file/M17N/gcin/gcin-reproducible.pa… -- You are receiving this mail because: You are on the CC list for the bug.

2 5

[Bug 1061219] New: trackerbug: packages do not build reproducibly from including uninitialized memory
by bugzilla_noreply＠novell.com 03 Jan '22

03 Jan '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1061219 Bug ID: 1061219 Summary: trackerbug: packages do not build reproducibly from including uninitialized memory Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: openSUSE Factory Status: CONFIRMED Severity: Normal Priority: P5 - None Component: Other Assignee: bwiedemann(a)suse.com Reporter: bwiedemann(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: Development Blocker: --- See also https://reproducible-builds.org/ When packages write uninitialized memory into files that are packaged it results in binaries that differ on every build. These thus trigger rebuilds of depending packages and are published to mirrors and users when actually nothing really changed. -- You are receiving this mail because: You are on the CC list for the bug.

2 13

[Bug 1101756] New: enable specification of custom GRUB_DISTRIBUTOR= in UEFI bootloader installation
by bugzilla_noreply＠novell.com 31 Dec '21

31 Dec '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1101756 Bug ID: 1101756 Summary: enable specification of custom GRUB_DISTRIBUTOR= in UEFI bootloader installation Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.1 Hardware: x86-64 OS: Other Status: NEW Severity: Enhancement Priority: P5 - None Component: Installation Assignee: yast2-maintainers(a)suse.de Reporter: mrmazda(a)earthlink.net QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- Created attachment 777382 --> http://bugzilla.opensuse.org/attachment.cgi?id=777382&action=edit 15.0 y2logs from host ab250 YaST2 currently offers no opportunity to specify a custom name to facilitate multiboot hosts. It needs one. Because it does not, e.g. when installation of Leap follows installation of Tumbleweed, the previous UEFI configuration is destroyed. The BIOS boot manager may or may not accommodate a proper selection of the preferred choice from the EFI/ESP partition. In the Leap follows TW case I just tried with an Asus B250M-C/CSM Kaby Lake motherboard with AMI BIOS version 1205 of 2018-05-11, the BIOS did not. As I normally do during installation, I deselected probe foreign OS. In attempting to avoid this overwrite, during installation of 15.0 I used vi to edit /mnt/etc/default/grub to include GRUB_DISTRIBUTOR="opensuse150". Actual bootloader installation at the end of overall installation changed it to GRUB_DISTRIBUTOR=, with the result that next boot only offered 15.0 to the exclusion of TW's /boot/grub2/custom.cfg which contains the custom stanzas for the other installed distros. I was forced to "choose" only 15.0 at next boot. I did work around that by using e on the 15.0 stanza to specify the TW kernel and initrd. Current EFI boot configuration: # efibootmgr BootCurrent: 0000 BootOrder: 0000,0001,0002 Boot0000* opensuse Boot0001* debian Boot0002* UEFI OS Expected EFI boot configuration subsequent to 15.0 installation was: # efibootmgr BootCurrent: 0000 BootOrder: 0000,0001,0002,0003,0004 Boot0000* opensuseTW Boot0001* debian Boot0002* ubuntu Boot0003* opensuse150 Boot0004* UEFI OS -- You are receiving this mail because: You are on the CC list for the bug.

2 8

[Bug 1109968] New: Daisy chained DisplayPort v1.2 screens randomly doesn't resume
by bugzilla_noreply＠novell.com 31 Dec '21

31 Dec '21

http://bugzilla.suse.com/show_bug.cgi?id=1109968 Bug ID: 1109968 Summary: Daisy chained DisplayPort v1.2 screens randomly doesn't resume Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.0 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-maintainers(a)forge.provo.novell.com Reporter: jkohoutek(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- When resuming from blank power saving, sometimes some of the displays connected trough Daisy chained DisplayPort v1.2 doesn't resume. Which one of the display doesn't wake up is random. GPU: Intel® HD Graphics 520 (Skylake GT2) Displays: 2x 1920x1080 Dell U2414H -- You are receiving this mail because: You are on the CC list for the bug.

2 7

[Bug 1060111] New: bash: have: command not found
by bugzilla_noreply＠novell.com 30 Dec '21

30 Dec '21

http://bugzilla.suse.com/show_bug.cgi?id=1060111 Bug ID: 1060111 Summary: bash: have: command not found Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: Linux Status: NEW Severity: Minor Priority: P5 - None Component: Basesystem Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: matthias(a)mailaender.name QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- I just encountered this in openSUSE Tumbleweed where every terminal displays > bash: have: command not found upon startup. http://www.jerous.org/2016/09/19/bash-have-not-found describes the problem and proposes a solution. I don't know if it is the correct approach. -- You are receiving this mail because: You are on the CC list for the bug.

2 10

[Bug 1136292] New: ktorrent don't find the file "http://geolite.maxmind.com/download/geoip/database/GeoLiteCountry/GeoIP.dat.gz"
by bugzilla_noreply＠novell.com 22 Dec '21

22 Dec '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1136292 Bug ID: 1136292 Summary: ktorrent don't find the file "http://geolite.maxmind.com/download/geoip/database/Ge oLiteCountry/GeoIP.dat.gz" Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.1 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: KDE Applications Assignee: opensuse-kde-bugs(a)opensuse.org Reporter: x3.141592(a)yahoo.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 805988 --> http://bugzilla.opensuse.org/attachment.cgi?id=805988&action=edit ktorrent message Please see the attachment. I get this message when I start ktorrent. -- You are receiving this mail because: You are on the CC list for the bug.

2 12

[Bug 937067] New: efi=1 does not seem to work anymore
by bugzilla_noreply＠novell.com 17 Dec '21

17 Dec '21

http://bugzilla.suse.com/show_bug.cgi?id=937067 Bug ID: 937067 Summary: efi=1 does not seem to work anymore Classification: openSUSE Product: openSUSE Factory Version: 201505* Hardware: Other OS: Other Status: NEW Severity: Major Priority: P5 - None Component: Installation Assignee: yast2-maintainers(a)suse.de Reporter: kukuk(a)suse.com QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- In the past, you could add efi=1 as argument for the installer, and your system was setup for EFI boot, even if the detection fails. This works only partly with Tumbleweed 20150630: the bootloader still installs and configures grub2-x86_64-efi, but the storage proposal does not create a vfat /boot/EFI partition anymore. This works with SLES12, haven't tested openSUSE 13.2. -- You are receiving this mail because: You are on the CC list for the bug.

2 10

[Bug 997918] New: TW 20160901: unable to dup since docker-compose conflicts with python-requests
by bugzilla_noreply＠novell.com 15 Dec '21

15 Dec '21

http://bugzilla.opensuse.org/show_bug.cgi?id=997918 Bug ID: 997918 Summary: TW 20160901: unable to dup since docker-compose conflicts with python-requests Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: robert.munteanu(a)gmail.com QA Contact: qa-bugs(a)suse.de CC: fcastelli(a)suse.com Found By: --- Blocker: --- Another iteration of bug #984309 Problem: docker-compose-1.7.1-2.2.noarch conflicts with python-requests >= 2.11 provided by python-requests-2.11.1-1.1.noarch Solution 1: deinstallation of docker-compose-1.7.1-2.2.noarch Solution 2: keep obsolete python-requests-2.10.0-3.1.noarch -- You are receiving this mail because: You are on the CC list for the bug.

2 4

[Bug 1072403] New: [Build 20171211] openQA test fails in docker_compose
by bugzilla_noreply＠novell.com 15 Dec '21

15 Dec '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1072403 Bug ID: 1072403 Summary: [Build 20171211] openQA test fails in docker_compose Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other URL: http://openqa.opensuse.org/tests/557372/modules/docker _compose/steps/14 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Containers Assignee: containers-bugowner(a)suse.de Reporter: dimstar(a)opensuse.org QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- ## Observation openQA test in scenario opensuse-Tumbleweed-DVD-x86_64-extra_tests_in_textmode@64bit fails in [docker_compose](http://openqa.opensuse.org/tests/557372/modules/docker_comp… ## Reproducible Fails since (at least) Build [20170428](http://openqa.opensuse.org/tests/395051) ## Expected result Last good: (unknown) (or more recent) ## Further details Always latest result in this scenario: [latest](http://openqa.opensuse.org/tests/latest?test=extra_tests_in_textmod… docker-compose is no longer installable, as python-texttable has been updated to version 1.1.1 (from 0.8.3) in sr 555176 -- You are receiving this mail because: You are on the CC list for the bug.

2 4

[Bug 1062084] New: docker-compose broken because of python-docker-py
by bugzilla_noreply＠novell.com 15 Dec '21

15 Dec '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1062084 Bug ID: 1062084 Summary: docker-compose broken because of python-docker-py Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Virtualization:Tools Assignee: virt-bugs(a)suse.de Reporter: jc(a)phocean.net QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Docker-compose broke after the last update, because of a broken dependancy on python-docker-py. % sudo zypper in docker-compose Chargement des données du dépôt... Lecture des paquets installés... Résolution des dépendances des paquets... Problème : rien ne fournit python-docker-py >= 1.10.3, qui est requis par docker-compose-1.8.1-1.2.noarch Solution 1 : ne pas installer docker-compose-1.8.1-1.2.noarch Solution 2 : casser docker-compose-1.8.1-1.2.noarch en ignorant certaines de ses dépendances % zypper info python-dockerpty Chargement des données du dépôt... Lecture des paquets installés... Informations sur paquet python-dockerpty : ------------------------------------------ Dépôt : openSUSE:Tumbleweed Nom : python-dockerpty Version : 0.4.1-1.3 Arch : noarch Fabricant : openSUSE Taille une fois installé : 78,6 KiB installé : Non État : non installé Paquet source : python-dockerpty-0.4.1-1.3.src Résumé : Docker API Client Description : Provides the functionality needed to operate the pseudo-tty (PTY) allocated to a docker container, using the Python client. % zypper info docker-compose Chargement des données du dépôt... Lecture des paquets installés... Informations sur paquet docker-compose : ---------------------------------------- Dépôt : openSUSE:Tumbleweed Nom : docker-compose Version : 1.8.1-1.2 Arch : noarch Fabricant : openSUSE Taille une fois installé : 512,9 KiB installé : Non État : non installé Paquet source : docker-compose-1.8.1-1.2.src Résumé : Define and run complex applications using Docker Description : Compose is a tool for defining and running complex applications with Docker. With Compose, you define a multi-container application in a single file, then spin your application up in a single command which does everything that needs to be done to get it running. Compose is great for development environments, staging servers, and CI. We don't recommend that you use it in production yet. Previously known as Fig. -- You are receiving this mail because: You are on the CC list for the bug.

2 23

[Bug 1004927] New: Upgrade to docker-compose 1.8.1
by bugzilla_noreply＠novell.com 15 Dec '21

15 Dec '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1004927 Bug ID: 1004927 Summary: Upgrade to docker-compose 1.8.1 Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.2 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Virtualization:Other Assignee: virt-bugs(a)suse.de Reporter: noga.dany(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Docker in Leap 42.2 was updated to 1.12, but docker-compose, which can use new capabilities stuck on version 1.6.1. Please update docker-compose too. -- You are receiving this mail because: You are on the CC list for the bug.

2 3

[Bug 1027448] New: Please use key release event for bracket completion plugin
by bugzilla_noreply＠novell.com 15 Dec '21

15 Dec '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1027448 Bug ID: 1027448 Summary: Please use key release event for bracket completion plugin Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.2 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: GNOME Assignee: bnc-team-gnome(a)forge.provo.novell.com Reporter: hillwoodroc(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 715892 --> http://bugzilla.opensuse.org/attachment.cgi?id=715892&action=edit bracketcompletion: use key release event to work with input method From: bgo#778737 https://bugzilla.gnome.org/show_bug.cgi?id=778737 Some user reported that ibus-libpinyin/ibus-pinyin doesn't work with gedit plugin bracket completion. I tried to modify the gedit plugin code, it seems work now. Please review it, thanks! How to reproduce it: 1. Switch to C/C++ mode, press "(", bracket completion works. 2. Switch input method to "Intelligent Pinyin" or "Pinyin", it doesn't work. -- You are receiving this mail because: You are on the CC list for the bug.

2 7

[Bug 1098245] New: gnome-keyring-daemon: insufficient process capabilities, unsecure memory might get used
by bugzilla_noreply＠novell.com 14 Dec '21

14 Dec '21

http://bugzilla.suse.com/show_bug.cgi?id=1098245 Bug ID: 1098245 Summary: gnome-keyring-daemon: insufficient process capabilities, unsecure memory might get used Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.0 Hardware: x86-64 OS: Linux Status: NEW Severity: Minor Priority: P5 - None Component: GNOME Assignee: bnc-team-gnome(a)forge.provo.novell.com Reporter: jmader2(a)gmu.edu QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- starting `gnome-session` there is the console message, gnome-keyring-daemon: insufficient process capabilities, unsecure memory might get used I am currently working around this with, setcap cap_ipc_lock=+ep /usr/bin/gnome-keyring-daemon -- You are receiving this mail because: You are on the CC list for the bug.

2 1

[Bug 1002875] New: plymouth boot splash not working in tumbleweed
by bugzilla_noreply＠novell.com 12 Dec '21

12 Dec '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1002875 Bug ID: 1002875 Summary: plymouth boot splash not working in tumbleweed Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: cristian_anita(a)yahoo.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Hi All, I recently made a fresh install of Tumbleweed 20160924 and plymouth splash screen does not appear at startup (only blinking cursor between grub2 and sddm) and shutdown (only some message about watchdog). plymouth-0.9.2-2.4 plymouth-branding-openSUSE-13.3-4.3 grub2-2.02~beta3-11.1 Same with latest TW update (20161003) Regards, Cristian ANITA -- You are receiving this mail because: You are on the CC list for the bug.

2 111

[Bug 972787] New: [gpg-agent] Rework agent startup for DM sessions.
by bugzilla_noreply＠novell.com 01 Dec '21

01 Dec '21

http://bugzilla.opensuse.org/show_bug.cgi?id=972787 Bug ID: 972787 Summary: [gpg-agent] Rework agent startup for DM sessions. Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: All OS: openSUSE 42.1 Status: NEW Severity: Major Priority: P5 - None Component: Security Assignee: security-team(a)suse.de Reporter: eich(a)suse.com QA Contact: qa-bugs(a)suse.de CC: astieger(a)suse.com, meissner(a)suse.com, premysl.janouch(a)suse.com, werner(a)suse.com, xorg-maintainer-bugs(a)forge.provo.novell.com Found By: Development Blocker: --- The gpg-agent for a user session is started by the script /etc/X11/xdm/sys.xsession. An openSUSE user pointed out to me that the socket handling of the gpg-agent has changed with gpg 2.1 - now neither a env file is written (the option --write-env-file is ignored) nor nor does anything use the env variable GPG_AGENT_INFO. Instead today a standard socket is used in $HOME/.gnupg/S.gpg-agent. Also check: https://gnupg.org/faq/whats-new-in-2.1.html If NFS mounted homes are desired, it can be handled as described in: https://wiki.gnupg.org/NFS This requires reworking of the gpg-agent startup (and possibly also of the ssh-agent) in sys.xsession. Any takers? -- You are receiving this mail because: You are on the CC list for the bug.

2 4

[Bug 1099755] New: /etc/hosts.allow /etc/hosts.deny not support ssh
by bugzilla_noreply＠novell.com 01 Dec '21

01 Dec '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1099755 Bug ID: 1099755 Summary: /etc/hosts.allow /etc/hosts.deny not support ssh Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Factory Status: NEW Severity: Normal Priority: P5 - None Component: Security Assignee: security-team(a)suse.de Reporter: simon(a)becherer.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- wrong security feeling, because text of file /etc/hosts.allow is wrong. written is: # /etc/hosts.allow # See 'man tcpd' and 'man 5 hosts_access' for a detailed description # of /etc/hosts.allow and /etc/hosts.deny. # # short overview about daemons and servers that are built with # tcp_wrappers support: #. # package name | daemon path | token # ---------------------------------------------------------------------------- # ssh, openssh | /usr/sbin/sshd | sshd, sshd-fwd-x11, sshd-fwd-<port> # quota | /usr/sbin/rpc.rquotad | rquotad # tftpd | /usr/sbin/in.tftpd | in.tftpd # portmap | /sbin/portmap | portmap at least toke sshd to allow and deny will not work any more on actual systems (tumbleweed). (maybe others tokens also affected) so user (as i) with low background knowlidge will feel secure if they make settings like: sshd : ALL : deny sshd : 127.0.0.1 : allow sshd : 192.168.0.30 : allow but the system ignores this. -> leading text and maybe manpage has to be changed! -> or if this 2 files host.allow / hosts.deny ar complete obsolete, do not install it at all. -- You are receiving this mail because: You are on the CC list for the bug.

2 1

[Bug 1087860] New: wine repeatedly asks to install wine-mono even though the package wine-mono was installed
by bugzilla_noreply＠novell.com 29 Nov '21

29 Nov '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1087860 Bug ID: 1087860 Summary: wine repeatedly asks to install wine-mono even though the package wine-mono was installed Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.0 Hardware: Other URL: http://lord.arch/tests/737/modules/wine/steps/26 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: meissner(a)suse.com Reporter: okurz(a)suse.com QA Contact: okurz(a)suse.com Found By: --- Blocker: --- ## Observation After installing packages "wine" and "wine-mono" explicitly on openSUSE Leap build 184.1 and calling wine on even a trivial Windows program a dialog pops up to download and install a "wine-mono" package which should be there already. This can now also be reproduced in an openQA test: scenario opensuse-15.0-DVD-x86_64-wine@64bit in [wine](http://lord.arch.suse.de/tests/737/modules/wine/steps/26) ## Reproducible Every time on a clean installation of wine on openSUSE Leap 15.0 and I think just the same on openSUSE Tumbleweed. Might also be on openSUSE Leap 42.3 but I am not sure about this. ## Expected result There should be no question for wine-mono installation if the system package is alread installed OR a better description of the system package describing what it is actually used for. I think the problem is that even if someone would answer "yes" to the question to install the internal (non-openSUSE) wine-mono package the next time the question pops up again but I'm not 100% sure on this. ## Further details Always latest result in this scenario: [latest](http://lord.arch/tests/latest?arch=x86_64&test=wine&machine=64bit&flavor=DVD&version=15.0&distri=opensuse) -- You are receiving this mail because: You are on the CC list for the bug.

2 3

[Bug 1095670] New: Problem with suid pgms on Leap-15.0
by bugzilla_noreply＠novell.com 24 Nov '21

24 Nov '21

http://bugzilla.suse.com/show_bug.cgi?id=1095670 Bug ID: 1095670 Summary: Problem with suid pgms on Leap-15.0 Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.0 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: dmarkh(a)cfl.rr.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- I am upgrading an older SuSE-13.2 box to Leap. I have done a fresh Leap-15.0 install and ported over the source code that we ran on the 13.2 box. It builds fine but I am having an issue. The program is/has to be an suid pgm. It also uses fork/execvpe/wait to execute some external scripts. And that is where my problem lies. The user is a member of several groups but these group memberships seem to disappear when these external scripts are executed. For instance the user is a member of the cdrom group so he can eject and work with a DVD. I have created a simple example script and source for a pgm that execvpe's that script which shows my problem. test.sh script: #!/bin/sh whoami id test.c pgm source: #define _GNU_SOURCE #include <unistd.h> #include <stdio.h> #include <stdlib.h> #include <string.h> int main() { char *path = getenv("PATH"); char pathenv[strlen(path) + sizeof("PATH=")]; sprintf(pathenv, "PATH=%s", path); char *envp[] = {pathenv, NULL}; char *tests[] = {"./test.sh", NULL}; execvpe(tests[0], tests, envp); } #cc test.c #/a.out markh uid=5076(markh) gid=100(users) groups=100(users),19(floppy),200(lcrs),484(tape),485(lp),488(disk),489(dialout),490(cdrom) Then as root: #chown root ./a.out #chgrp root ./a.out #chmod +s ./a.out Then as user #./a.out markh uid=5076(markh) gid=100(users) groups=100(users) Once the pgm is owned by root and suid, I lose all my group memberships for some unknown reason. It is not proper to me. This all works fine on 13.2 but does not on Leap 15 or Leap 42.3. Is there some security setting somewhere that broke this? -- You are receiving this mail because: You are on the CC list for the bug.

2 19

[Bug 929755] New: shutter is missing perl(Gnome2) in Tumbleweed
by bugzilla_noreply＠novell.com 21 Nov '21

21 Nov '21

http://bugzilla.opensuse.org/show_bug.cgi?id=929755 Bug ID: 929755 Summary: shutter is missing perl(Gnome2) in Tumbleweed Classification: openSUSE Product: openSUSE Factory Version: 201503* Hardware: x86-64 OS: SUSE Other Status: NEW Severity: Major Priority: P5 - None Component: Other Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: f_koch(a)gmx.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/41.0.2272.101 Safari/537.36 Build Identifier: flo@linux-mvsa:~> sudo zypper in shutter Loading repository data... Reading installed packages... Resolving package dependencies... Problem: nothing provides perl(Gnome2) needed by shutter-0.93.1-1.1.noarch Solution 1: do not install shutter-0.93.1-1.1.noarch Solution 2: break shutter-0.93.1-1.1.noarch by ignoring some of its dependencies Choose from above solutions by number or cancel [1/2/c] (c): Reproducible: Always -- You are receiving this mail because: You are on the CC list for the bug.

2 12

[Bug 1133254] New: LTO: llvm[67] build fails
by bugzilla_noreply＠novell.com 19 Nov '21

19 Nov '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1133254 Bug ID: 1133254 Summary: LTO: llvm[67] build fails Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: martin.liska(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Fails due to: clang-6.0: error: linker command failed with exit code 1 (use -v to see invocation) I would expect the package should use a LTO bootstrap configuration. -- You are receiving this mail because: You are on the CC list for the bug.

2 10

[Bug 1126907] New: LLVM requires patching to prevent a rustc crash when building Firefox
by bugzilla_noreply＠novell.com 19 Nov '21

19 Nov '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1126907 Bug ID: 1126907 Summary: LLVM requires patching to prevent a rustc crash when building Firefox Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Development Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: jones_ld(a)protonmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- LLVM 7 has a bug in the discriminator code which causes a crash in rustc when building Firefox (and many other projects). The patches required are here, along with the discussion: https://github.com/rust-lang/rust/issues/57762#issuecomment-456155466 -- You are receiving this mail because: You are on the CC list for the bug.

2 1

[Bug 1120098] New: Clang 7 packaging is inconsistent
by bugzilla_noreply＠novell.com 19 Nov '21

19 Nov '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1120098 Bug ID: 1120098 Summary: Clang 7 packaging is inconsistent Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Development Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: aaronpuchert(a)alice-dsl.net QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- In llvm7.spec, the Clang binaries are renamed: # Fix the clang -> clang-X.Y symlink to work with update-alternatives mv %{buildroot}%{_bindir}/clang-%{_sonum} %{buildroot}%{_bindir}/clang ln -s %{_bindir}/clang-%{_relver} %{buildroot}%{_bindir}/clang-%{_minor} but the installed CMake files (in /usr/lib64/cmake/clang/) aren't changed accordingly. This makes it hard to build software that uses libclang. (I came across this when trying to update include-what-you-use.) The issue is easy to reproduce. Just create a folder with a CMakeLists.txt having just this line: find_package(Clang CONFIG REQUIRED) Then run "cmake ." and there will be an error message like CMake Error at /usr/lib64/cmake/clang/ClangTargets.cmake:296 (message): The imported target "clang" references the file "/usr/bin/clang-7" but this file does not exist. Possible reasons include: [...] Indeed, we have * /usr/bin/clang -> /etc/alternatives/clang -> /usr/bin/clang-7.0.0 * /usr/bin/clang-7.0 -> /usr/bin/clang-7.0.0 but no /usr/bin/clang-7. That is a bit unusual. On the other hand for gcc, we have * /usr/bin/gcc -> /usr/bin/gcc-8 -- You are receiving this mail because: You are on the CC list for the bug.

2 9

[Bug 1119092] New: llvm7: libLLVM is ABI incompatible between GCC and CLANG
by bugzilla_noreply＠novell.com 19 Nov '21

19 Nov '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1119092 Bug ID: 1119092 Summary: llvm7: libLLVM is ABI incompatible between GCC and CLANG Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Development Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: msrb(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- There is a clang-specific optimization in llvm::Optional, which makes code compiled with gcc and clang incompatible with each other. We build libLLVM, libclang, etc using clang, but the rest of the distribution is build using gcc. So anything that links against libLLVM, libclang, etc may be broken. Bug that introduced the clang-only optimization: https://bugs.llvm.org/show_bug.cgi?id=35978 Fix (removing the optimization from everywhere): https://reviews.llvm.org/D50710 -- You are receiving this mail because: You are on the CC list for the bug.

2 3

[Bug 1112730] New: llvm opt-viewer can not find style.css
by bugzilla_noreply＠novell.com 19 Nov '21

19 Nov '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1112730 Bug ID: 1112730 Summary: llvm opt-viewer can not find style.css Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.0 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Development Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: msrb(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Using opt-viewer fails with: FileNotFoundError: [Errno 2] No such file or directory: '/usr/bin/style.css' The opt-viewer script is installed in /usr/bin and looks for "style.css" in its own directory, but "style.css" is installed in /usr/share/opt-viewer. LLVM by default installs all opt* tools in /usr/share/opt-viewer, but we move them to /usr/bin to follow our packaging rules. The opt-viewer needs to be patched to find the file. -- You are receiving this mail because: You are on the CC list for the bug.

2 2

[Bug 1106000] New: llvm-config contains gcc-incompatible flags
by bugzilla_noreply＠novell.com 19 Nov '21

19 Nov '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1106000 Bug ID: 1106000 Summary: llvm-config contains gcc-incompatible flags Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Development Assignee: msrb(a)suse.com Reporter: fvogt(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- llvm-config --cflags contains "-Werror=unguarded-availability-new" which makes builds with gcc fail: cc1plus: error: -Werror=unguarded-availability-new: no option -Wunguarded-availability-new -- You are receiving this mail because: You are on the CC list for the bug.

2 3

[Bug 1092697] New: LLVM build fails on armv7l
by bugzilla_noreply＠novell.com 19 Nov '21

19 Nov '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1092697 Bug ID: 1092697 Summary: LLVM build fails on armv7l Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Development Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: msrb(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- The llvm4/5/6 build fails on armv7l because it is running out of memory. It is happening during linking of stage1, most likely because of the size of debuginfo. Stage1 should not be built with debuginfo (it is only used to compile the next stage), but it got the "-g" parameter accidentally from %optflags. -- You are receiving this mail because: You are on the CC list for the bug.

2 4

[Bug 1087136] New: GCC 8: llvm5 build fails
by bugzilla_noreply＠novell.com 19 Nov '21

19 Nov '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1087136 Bug ID: 1087136 Summary: GCC 8: llvm5 build fails Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: martin.liska(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Build the package with GCC 8, there's error: https://build.opensuse.org/package/live_build_log/openSUSE:Factory:Staging:… Please build the project as follows to reproduce the issue: osc build --alternative-project=openSUSE:Factory:Staging:Gcc7 -- You are receiving this mail because: You are on the CC list for the bug.

2 6

[Bug 1086445] New: libLLVMTableGen not packaged
by bugzilla_noreply＠novell.com 19 Nov '21

19 Nov '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1086445 Bug ID: 1086445 Summary: libLLVMTableGen not packaged Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Development Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: guillaume.gardet(a)opensuse.org QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Currently, in Tumbleweed, LLVM only packages libLLVM.so* and we are missing additional libraries, such as libLLVMTableGen.so* Some packages fails to build (e.g. ldc package) because of the missing additional libraries. -- You are receiving this mail because: You are on the CC list for the bug.

2 10

[Bug 1073210] New: Link Time Optimization doesn't work out of the box on 64 bit systems because of bfd-plugins path mixup
by bugzilla_noreply＠novell.com 19 Nov '21

19 Nov '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1073210 Bug ID: 1073210 Summary: Link Time Optimization doesn't work out of the box on 64 bit systems because of bfd-plugins path mixup Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.3 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Development Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: l.lunak(a)centrum.cz QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- When using LTO, linker is supposed to find a plugin for handling LTO in /usr/lib/bfd-plugins . And this path is hardcoded in sources, and it's "lib" even for 64 bit systems. However, neither GCC nor Clang/LLVM install their plugin there. GCC doesn't do anything with its plugin except for shipping it in its own directory, and LLVMGold is installed to /usr/lib64/bfd-plugins. So instead of LTO simply working when using -flto, one has to use gcc-ar/llvm-ar etc. to override the ar etc. which should work but don't because of this. I can easily submit fixed binutils and gcc packages to make them use /usr/lib64/bfd-plugins too, but I've first created this bugreport so that there's just one place for referring to this issue. Also I would first like to verify that this would indeed be the proper fix - is there any special reason why binutils hardcodes the "lib" there? -- You are receiving this mail because: You are on the CC list for the bug.

2 3

[Bug 1065464] New: Don't allow multiple OpenCL ICD packages to be installed simultaneously
by bugzilla_noreply＠novell.com 19 Nov '21

19 Nov '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1065464 Bug ID: 1065464 Summary: Don't allow multiple OpenCL ICD packages to be installed simultaneously Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Installation Assignee: yast2-maintainers(a)suse.de Reporter: sonichedgehog_hyperblast00(a)yahoo.com QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- I considered this important enough to warrant a bug report. The forum thread where I discovered and further explained the issue can be found here: https://forums.opensuse.org/showthread.php/527821-Blender-crashes-at-startu… When running the command 'zypper dup' without additional parameters, zypper wants to install the OpenCL ICD named pocl. However Mesa already uses another ICD which seems to come in the package libOpenCL1. This is a problem because from the looks of it, you may only have one ICD installed on your system at once; More than that will cause a conflict, and every OpenCL application will crash with the following error: mesa: CommandLine Error: Option 'enable-value-profiling' registered more than once! LLVM ERROR: inconsistency in registered CommandLine options To test and confirm this, you can install both "libOpenCL1" and "pocl" simultaneously then attempt to run Blender 3D: The application should crash on startup with the console output quoted above. After removing the pocl package however, Blender will start and work properly again. Until this bug is solved by the X11 developers, it might be a good idea for the openSUSE repositories to be aware of it and mark multiple OpenCL ICD packages as incompatible, only recommending that you install one at once. Users may find that OpenCL applications have suddenly stopped working, and not know what to do in order to fix the problem. A workaround for the time being is to mark pocl as "taboo / never install". -- You are receiving this mail because: You are on the CC list for the bug.

2 17

[Bug 1041469] New: llvm4 spec issues
by bugzilla_noreply＠novell.com 19 Nov '21

19 Nov '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1041469 Bug ID: 1041469 Summary: llvm4 spec issues Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Development Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: msuchanek(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Hello, llvm4 has this conditional: %if 0%{?sle_version} <= 130000 BuildRequires: gcc6 BuildRequires: gcc6-c++ %else BuildRequires: gcc BuildRequires: gcc-c++ %endif Since TW has no sle_version you get gcc6 on TW which is probably not intended. However, llvm4 is the only llvm which passes test on arm64 which may be the result of building with gcc6. Also lldb4 has ExclusiveArch: arm x86_64 arm is not an arch so this will build on x86_64 only. Maybe it was supposed to be %arm or armv7 or ... ? -- You are receiving this mail because: You are on the CC list for the bug.

2 5

[Bug 1026191] New: Add BPF into llvm target for PowerPC64 and AArch64
by bugzilla_noreply＠novell.com 19 Nov '21

19 Nov '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1026191 Bug ID: 1026191 Summary: Add BPF into llvm target for PowerPC64 and AArch64 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: glin(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- To build bcc on PowerPC64 and AArch64, we need to add BPF into the llvm build targets. We currently only build the native target on those two architectures. This is also for fate#322227. -- You are receiving this mail because: You are on the CC list for the bug.

2 3

[Bug 1012260] New: Clang++-3.8 symlink is missing
by bugzilla_noreply＠novell.com 19 Nov '21

19 Nov '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1012260 Bug ID: 1012260 Summary: Clang++-3.8 symlink is missing Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Development Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: alex.richardson(a)gmx.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- lrwxrwxrwx 1 root root 23 Oct 31 11:44 /usr/bin/clang -> /etc/alternatives/clang lrwxrwxrwx 1 root root 25 Oct 31 11:44 /usr/bin/clang++ -> /etc/alternatives/clang++ lrwxrwxrwx 1 root root 11 Oct 31 11:45 /usr/bin/clang-3.8 -> clang-3.8.1 -rwxr-xr-x 1 root root 99176 Oct 31 11:44 /usr/bin/clang-3.8.1 lrwxrwxrwx 1 root root 11 Oct 31 11:45 /usr/bin/clang++-3.8.1 -> clang-3.8.1 There should also be a symlink /usr/bin/clang++-3.8 -> /usr/bin/clang++-3.8.1 I am building some software that expects clang++-$MAJOR.$MINOR to exist and it would be nice if I didn't have to create that link myself. -- You are receiving this mail because: You are on the CC list for the bug.

2 2

[Bug 1135744] New: [Staging] texlive fails to build against gc 8.x
by bugzilla_noreply＠novell.com 18 Nov '21

18 Nov '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1135744 Bug ID: 1135744 Summary: [Staging] texlive fails to build against gc 8.x Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: dimstar(a)opensuse.org QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- gc 8.0.4 was submitted for inclusion into Factory. During the staging process though, texlive resulted in a build failure > /usr/lib64/gcc/x86_64-suse-linux/8/../../../../x86_64-suse-linux/bin/ld: picture.o: in function `operator new(unsigned long, GCPlacement, void (*)(void*, void*), void*)': [ 1376s] /usr/include/gc/gc_cpp.h:545: undefined reference to `GC_throw_bad_alloc()' [ 1376s] /usr/lib64/gcc/x86_64-suse-linux/8/../../../../x86_64-suse-linux/bin/ld: settings.o: in function `operator new(unsigned long, GCPlacement, void (*)(void*, void*), void*)': [ 1376s] /usr/include/gc/gc_cpp.h:545: undefined reference to `GC_throw_bad_alloc()' [ 1376s] /usr/lib64/gcc/x86_64-suse-linux/8/../../../../x86_64-suse-linux/bin/ld: settings.o: in function `gc::operator new(unsigned long)': [ 1376s] /usr/include/gc/gc_cpp.h:410: undefined reference to `GC_throw_bad_alloc()' [ 1376s] /usr/lib64/gcc/x86_64-suse-linux/8/../../../../x86_64-suse-linux/bin/ld: /usr/include/gc/gc_cpp.h:410: undefined reference to `GC_throw_bad_alloc()' [ 1376s] /usr/lib64/gcc/x86_64-suse-linux/8/../../../../x86_64-suse-linux/bin/ld: /usr/include/gc/gc_cpp.h:410: undefined reference to `GC_throw_bad_alloc()' [ 1376s] /usr/lib64/gcc/x86_64-suse-linux/8/../../../../x86_64-suse-linux/bin/ld: settings.o:/usr/include/gc/gc_cpp.h:410: more undefined references to `GC_throw_bad_alloc()' follow This can either be an issue in texlive (making use of code exposed in a library it is not linking, e.g. gccpp) or gc might use them implicitly and not linking the lib itself (possibly texlive needs a different way to identify what to link) -- You are receiving this mail because: You are on the CC list for the bug.

2 5

[Bug 991027] New: Seamonkey Mail crashes on startup since version 2.40-2.1
by bugzilla_noreply＠novell.com 16 Nov '21

16 Nov '21

http://bugzilla.opensuse.org/show_bug.cgi?id=991027 Bug ID: 991027 Summary: Seamonkey Mail crashes on startup since version 2.40-2.1 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: bjoernv(a)arcor.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 685863 --> http://bugzilla.opensuse.org/attachment.cgi?id=685863&action=edit Stacktrace produced with "seamonkey -safe-mode --debugger gdb -mail 2>&1" The latest release of Seamonkey (2.40-2.1) crashes on startup. It only crashes, if E-Mail accounts are configured in selected profile. Add-Ons do not matter, because I run Seamonkey in safe-mode for testing. The previous version 2.40-1.12 which is still available for download is unaffected, so it can be used until this bug is fixed. A full GDB stacktrace is attached. -- You are receiving this mail because: You are on the CC list for the bug.

2 17