openSUSE Bugs August 2018

bugs@lists.opensuse.org

1 participants
3300 discussions

[Bug 1102408] New: trackerbug: packages do not build reproducibly from race conditions

by bugzilla_noreply＠novell.com

http://bugzilla.opensuse.org/show_bug.cgi?id=1102408 Bug ID: 1102408 Summary: trackerbug: packages do not build reproducibly from race conditions Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: All OS: openSUSE Factory Status: CONFIRMED Severity: Normal Priority: P5 - None Component: Development Assignee: bwiedemann(a)suse.com Reporter: bwiedemann(a)suse.com QA Contact: qa-bugs(a)suse.de Depends on: 1021335, 1021353 Blocks: 1081754 Found By: Development Blocker: --- See also https://reproducible-builds.org/ and https://github.com/bmwiedemann/theunreproduciblepackage/tree/master/race When packages build with make -j$N (N>1), it sometimes results in binaries that differ between builds and thus trigger rebuilds of depending packages and are published to mirrors and users when actually nothing really changed. Build results can also be incorrect due to races. Often it is possible to fix races by adding proper dependencies between build targets (e.g. https://bugzilla.sudo.ws/show_bug.cgi?id=842 ) or fixing involved racy tools -- You are receiving this mail because: You are on the CC list for the bug.

21 hours, 3 minutes

[Bug 1101735] New: 40grub2: debug messages

by bugzilla_noreply＠novell.com

http://bugzilla.opensuse.org/show_bug.cgi?id=1101735 Bug ID: 1101735 Summary: 40grub2: debug messages Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.0 Hardware: x86-64 OS: Other Status: NEW Severity: Minor Priority: P5 - None Component: Bootloader Assignee: jsrain(a)suse.com Reporter: novell(a)howorth.org.uk QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- there are a lot of messages in /var/log/messages that start with 40grub2: debug: parsing: Why are they there and how do I get them to stop? PS Why is openSUSE Leap 15.0 not in the list of OS? -- You are receiving this mail because: You are on the CC list for the bug.

2 days, 18 hours

[Bug 993885] New: Kde-Live net installer does not reboot after installation

by bugzilla_noreply＠novell.com

http://bugzilla.suse.com/show_bug.cgi?id=993885 Bug ID: 993885 Summary: Kde-Live net installer does not reboot after installation Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Live Medium Assignee: fvogt(a)suse.com Reporter: okurz(a)suse.com QA Contact: okurz(a)suse.com Found By: --- Blocker: --- ## observation Continuing through the whole installation process of the NET installer on the Kde-Live medium until the "reboot now" dialog shows up works fine but the reboot does not seem to happen ## steps to reproduce I am in the process of automating this but it can be as easy as * start Kde-Live * call installation from within plasma session * let installer run into "reboot now" action * observe that the system does not reboot ## expected result system should reboot into installed system ## workaround manual reboot of the system yields a properly setup Tumbleweed installation so the installation is ok. -- You are receiving this mail because: You are on the CC list for the bug.

3 days, 5 hours

[Bug 1033081] New: fetchmail hardcoded to use log file - syslogging thus unavailable

by bugzilla_noreply＠novell.com

http://bugzilla.suse.com/show_bug.cgi?id=1033081 Bug ID: 1033081 Summary: fetchmail hardcoded to use log file - syslogging thus unavailable Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.2 Hardware: x86-64 OS: openSUSE 42.2 Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: jmozdzen(a)nde.ag QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- :~ # rpm -qi fetchmail Name : fetchmail Version : 6.3.26 Release : 18.1 Architecture: x86_64 Looking at fetchmail.service -> /usr/lib/fetchmail-systemd-exec, I see that using logging to log file is hard-coded there: --- cut here: /usr/lib/fetchmail-systemd-exec --- [...] exec /usr/bin/fetchmail $OPTS $FETCHMAIL_EXPERT_OPTIONS \ -f $FETCHMAIL_RC_PATH -L /var/log/fetchmail --- cut here --- Hence, activating logging to syslog via options doesn't work: --- cut here --- :~ # grep syslog /etc/fetchmailrc set syslog :~ # systemctl restart fetchmail :~ # 2017-04-09T17:36:13.480966+02:00 myhost fetchmail[4441]: syslog and logfile options are both set, ignoring syslog, and logging to /var/log/fetchmail --- cut here --- A possible change would be to move "-L /var/log/fetchmail" to /etc/sysconfig/fetchmail (i.e. to FETCHMAIL_EXPERT_OPTIONS variable, or a new one). -- You are receiving this mail because: You are on the CC list for the bug.

3 days, 13 hours

[Bug 1105282] New: vc4 not working in linuxrc because of PCM

by bugzilla_noreply＠novell.com

http://bugzilla.suse.com/show_bug.cgi?id=1105282 Bug ID: 1105282 Summary: vc4 not working in linuxrc because of PCM Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: afaerber(a)suse.com Reporter: agraf(a)suse.com QA Contact: qa-bugs(a)suse.de CC: sndirsch(a)suse.com, snwint(a)suse.com, tzimmermann(a)suse.com Found By: --- Blocker: --- When I boot up the current Tumbleweed installer system on the Raspberry Pi, HDMI output is not showing. This is related to the vc4 driver being unable to properly load: [ 17.735109] vc4_hdmi 3f902000.hdmi: Could not register PCM component: -517 [ 17.742312] vc4-drm soc:gpu: failed to bind 3f902000.hdmi (ops vc4_hdmi_ops [vc4]): -517 [ 17.750679] vc4-drm soc:gpu: master bind failed: -517 I think there are 2 bugs here really: The first one is with vc4. It shouldn't declare itself as viable graphics output driver (kicking out the well working efifb one) when it can not find all of its dependencies. The other one is that we probably need to include snd_pcm and snd_soc_core in the linuxrc initrd so that vc4 does load properly and allows us to install: rpi31:~ # lsmod | grep -i snd snd_soc_core 237568 1 vc4 snd_pcm_dmaengine 16384 1 snd_soc_core snd_pcm 151552 3 vc4,snd_pcm_dmaengine,snd_soc_core snd_timer 36864 1 snd_pcm snd 106496 3 snd_timer,snd_soc_core,snd_pcm soundcore 20480 1 snd I'll leave it to Andreas to determine who to assign this bug to and thus which path of the 2 to fix this we should take ;). -- You are receiving this mail because: You are on the CC list for the bug.

4 days, 1 hour

[Bug 955233] New: Software Updates applet shows "Network is offline"

by bugzilla_noreply＠novell.com

http://bugzilla.opensuse.org/show_bug.cgi?id=955233 Bug ID: 955233 Summary: Software Updates applet shows "Network is offline" Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.1 Hardware: x86-64 OS: openSUSE 42.1 Status: NEW Severity: Normal Priority: P5 - None Component: Network Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: madakis1988(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- The applet occasionally shows that the "Network is offline" even though there's an active connection to the internet. There's no other connection enabled. This results in inability to check for updates. It usually goes back to normal after a reboot. YaST -> Online Update works fine every time. -- You are receiving this mail because: You are on the CC list for the bug.

1 week, 1 day

[Bug 1006815] New: [Build 20161024] yast2 nfs-client does not mount added export

by bugzilla_noreply＠novell.com

http://bugzilla.suse.com/show_bug.cgi?id=1006815 Bug ID: 1006815 Summary: [Build 20161024] yast2 nfs-client does not mount added export Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 Assignee: yast2-maintainers(a)suse.de Reporter: jpupava(a)suse.com QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- Created attachment 699166 --> http://bugzilla.suse.com/attachment.cgi?id=699166&action=edit y2logs ### observed nfs client does not mount added export, nfs client configuration is ok and the export is added in fstab, nfs client service is running but export is not mounted https://openqa.opensuse.org/tests/289982#step/yast2_nfs_client/14 ### workaround mount -a does mount nfs export ### expected added export should be also mounted linux-2cg7:~ # systemctl status nfs-client.target ● nfs-client.target - NFS client services Loaded: loaded (/usr/lib/systemd/system/nfs-client.target; disabled; vendor preset: disabled) Drop-In: /usr/lib/systemd/system/nfs-client.target.d └─nfs.conf Active: active since Tue 2016-10-25 09:36:52 EDT; 36s ago Oct 25 09:36:52 linux-2cg7 systemd[1]: Reached target NFS client services. linux-2cg7:~ # linux-2cg7:~ # systemctl show nfs.service --property=Id --property=MainPID --property=Description --property=LoadState --property=ActiveState --property=SubState --property=UnitFileState --property=FragmentPath MainPID=0 Id=nfs.service Description=Alias for NFS client LoadState=loaded ActiveState=active SubState=exited FragmentPath=/usr/lib/systemd/system/nfs.service UnitFileState=enabled linux-2cg7:~ # mount|grep nfs sunrpc on /var/lib/nfs/rpc_pipefs type rpc_pipefs (rw,relatime) nfsd on /proc/fs/nfsd type nfsd (rw,relatime) linux-2cg7:~ # linux-2cg7:~ # grep nfs /etc/fstab localhost:/tmp/nfs/server /tmp/nfs/client nfs defaults 0 0 linux-2cg7:~ # linux-2cg7:~ # mount -a linux-2cg7:~ # mount|grep nfs sunrpc on /var/lib/nfs/rpc_pipefs type rpc_pipefs (rw,relatime) nfsd on /proc/fs/nfsd type nfsd (rw,relatime) localhost:/tmp/nfs/server on /tmp/nfs/client type nfs4 (rw,relatime,vers=4.2,rsize=131072,wsize=131072,namlen=255,hard,proto=tcp6,port=0,timeo=600,retrans=2,sec=sys,clientaddr=::1,local_lock=none,addr=::1) linux-2cg7:~ # -- You are receiving this mail because: You are on the CC list for the bug.

1 week, 4 days

[Bug 1041090] New: trackerbug: packages do not build reproducibly from unsorted input

by bugzilla_noreply＠novell.com

http://bugzilla.opensuse.org/show_bug.cgi?id=1041090 Bug ID: 1041090 Summary: trackerbug: packages do not build reproducibly from unsorted input Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: openSUSE 13.2 Status: NEW 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/docs/stable-inputs/ When linking .o files in random filesystem order the linker will vary the ordering of functions and apply varying optimizations resulting in binaries that differ on every build and 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.

1 week, 4 days

[Bug 991027] New: Seamonkey Mail crashes on startup since version 2.40-2.1

by bugzilla_noreply＠novell.com

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.

1 week, 4 days

[Bug 984637] New: MozillaFirefox, MozillaThunderbird rebuild failure with binutils

by bugzilla_noreply＠novell.com

http://bugzilla.opensuse.org/show_bug.cgi?id=984637 Bug ID: 984637 Summary: MozillaFirefox, MozillaThunderbird rebuild failure with binutils Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.2 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Firefox Assignee: pcerny(a)suse.com Reporter: lnussel(a)suse.com QA Contact: qa-bugs(a)suse.de CC: bnc-team-mozilla(a)forge.provo.novell.com, matz(a)suse.com, pcerny(a)suse.com, rguenther(a)suse.com, schwab(a)suse.com, wolfgang(a)rosenauer.org Blocks: 983048 Found By: --- Blocker: --- Looks like the updated binutils in SP2 causes firefox and thunderbird fail to build: [ 2513s] /usr/lib64/gcc/x86_64-suse-linux/4.8/../../../../x86_64-suse-linux/bin/ld: ../../xpcom/components/nsComponentManager.o: relocation R_X86_64_PC32 against protected symbol `end_kPStaticModules_NSModule' can not be used when making a shared object [ 2513s] /usr/lib64/gcc/x86_64-suse-linux/4.8/../../../../x86_64-suse-linux/bin/ld: final link failed: Bad value https://build.opensuse.org/package/live_build_log/openSUSE:Leap:42.2:Stagin… https://build.opensuse.org/package/live_build_log/openSUSE:Leap:42.2:Stagin… Is this a bug in binutils or firefox/tb? -- You are receiving this mail because: You are on the CC list for the bug.

1 week, 4 days

Jump to page:

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

openSUSE Bugs August 2018