http://bugzilla.suse.com/show_bug.cgi?id=1151368http://bugzilla.suse.com/show_bug.cgi?id=1151368#c8
Matthias Brugger <mbrugger(a)suse.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |WONTFIX
Assignee|kernel-maintainers(a)forge.pr |mbrugger(a)suse.com
|ovo.novell.com |
--- Comment #8 from Matthias Brugger <mbrugger(a)suse.com> ---
I think this is rather something that the python-RPi.GPIO would need to fix. A
quick look on the code gives me the feeling that this is rather trivial [1].
[1]
https://sourceforge.net/p/raspberry-gpio-python/code/ci/default/tree/source…
--
You are receiving this mail because:
You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1148679http://bugzilla.suse.com/show_bug.cgi?id=1148679#c3
Michal Filka <mfilka(a)suse.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Flags|needinfo?(mfilka(a)suse.com) |needinfo?(jeriveramoya@suse
| |.com)
--- Comment #3 from Michal Filka <mfilka(a)suse.com> ---
There were quite some changes in past weeks as we switched to completely new
backend in yast2 network. Could you pls verify if the bug is still valid?
--
You are receiving this mail because:
You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1152627
Bug ID: 1152627
Summary: Installer crash due to a circular dependency between
Host and DNS modules
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: igonzalezsosa(a)suse.com
QA Contact: jsrain(a)suse.com
Found By: ---
Blocker: ---
Created attachment 820150
--> http://bugzilla.suse.com/attachment.cgi?id=820150&action=edit
YaST2 logs
It looks like a circular dependency between Host and DNS module is crashing the
installer as you can see in
https://openqa.opensuse.org/tests/1044832#step/welcome/5
--
You are receiving this mail because:
You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1145193http://bugzilla.suse.com/show_bug.cgi?id=1145193#c63
--- Comment #63 from Reinhard Max <max(a)suse.com> ---
Please stop this, Ravas, you are running completely into the wrong direction
and cluttering this already messy bug report even more.
If there are services running on a system that require a synchronised time
there is no way around chrony-wait.service (or anything else that blocks untill
the time is in sync), because anything else that you are suggesting would
continue booting with unsynchronized time.
So, disabling chrony-wait.service can only be a short-term workaround (on which
the YaST team is working right now), but the final goal (as I have stated
several time already) has to be to minimize the set of services that depend on
time-sync.target and to make sure nothing depends on it that is on the
dependency path to an interactive session.
Again, please top this unhelpful discussion about alternatives to having
"waitsync" in chrony-wait.service, because there are no.
--
You are receiving this mail because:
You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1142862http://bugzilla.suse.com/show_bug.cgi?id=1142862#c15
Joaquín Rivera <jeriveramoya(a)suse.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jeriveramoya(a)suse.com
--- Comment #15 from Joaquín Rivera <jeriveramoya(a)suse.com> ---
I have created this bug, feel free to handle as you think is better, reopening
this one and rejecting the other one or just continue in:
https://bugzilla.suse.com/show_bug.cgi?id=1152535
I attached there some screenshots for what happen after ignoring errors and
trying to go forward in the installation.
--
You are receiving this mail because:
You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1151291http://bugzilla.suse.com/show_bug.cgi?id=1151291#c10
--- Comment #10 from Michal Filka <mfilka(a)suse.com> ---
(In reply to Fabian Vogt from comment #9)
> (In reply to Fabian Vogt from comment #5)
> > (In reply to Michal Filka from comment #4)
> > > I was unable to reproduce the issue. Could you pls check what I did if it
> > > confirms the test?
> > > - started kde live iso (downloaded from the BS, with yast2-network 4.2.12)
> > > - installer reported active network -> enabled online repositories
> > > - started installation
> > >
> > > Did I miss some special configuration step?
> >
> > AFAICT that's what openQA does as well. Did you wait until the end of the
> > installation?
> >
> > I'll try to reproduce it here as well.
>
> I can indeed not reproduce the error dialog, but after the installation DNS
> lookups are broken as resolv.conf does not have any entries.
>
> I assume it breaks in openQA differently because the installation takes a
> bit longer, so the cache expires just before it finishes.
That's weird bcs "my" installation even have complete resolv.conf. Moreover
resolv.conf at target system is not touched by yast during installation. Could
you check if it is not another issue like not running network service or an
issue on network?
--
You are receiving this mail because:
You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1092345http://bugzilla.suse.com/show_bug.cgi?id=1092345#c4
Alexander Herzig <aherzig(a)suse.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |aherzig(a)suse.com
--- Comment #4 from Alexander Herzig <aherzig(a)suse.com> ---
Whats the status here? Can we move forward?
--
You are receiving this mail because:
You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1151291http://bugzilla.suse.com/show_bug.cgi?id=1151291#c9
Fabian Vogt <fvogt(a)suse.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Flags|needinfo?(fvogt(a)suse.com) |
--- Comment #9 from Fabian Vogt <fvogt(a)suse.com> ---
(In reply to Fabian Vogt from comment #5)
> (In reply to Michal Filka from comment #4)
> > I was unable to reproduce the issue. Could you pls check what I did if it
> > confirms the test?
> > - started kde live iso (downloaded from the BS, with yast2-network 4.2.12)
> > - installer reported active network -> enabled online repositories
> > - started installation
> >
> > Did I miss some special configuration step?
>
> AFAICT that's what openQA does as well. Did you wait until the end of the
> installation?
>
> I'll try to reproduce it here as well.
I can indeed not reproduce the error dialog, but after the installation DNS
lookups are broken as resolv.conf does not have any entries.
I assume it breaks in openQA differently because the installation takes a bit
longer, so the cache expires just before it finishes.
--
You are receiving this mail because:
You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1152601
Bug ID: 1152601
Summary: Awesome WM crashes on launch when installed with
upstream branding
Classification: openSUSE
Product: openSUSE Tumbleweed
Version: Current
Hardware: x86-64
OS: Other
Status: NEW
Severity: Normal
Priority: P5 - None
Component: X11 Applications
Assignee: bnc-team-screening(a)forge.provo.novell.com
Reporter: axelsn(a)gmail.com
QA Contact: qa-bugs(a)suse.de
Found By: ---
Blocker: ---
Awesome is crashing immediately on a minimal system if installed with
"awesome-branding-upstream" due to the missing dependency
"typelib-1_0-GdkPixbuf-2_0". This doesn't happen with
"awesome-branding-openSUSE" because the required package is properly installed
as a dependency.
--
You are receiving this mail because:
You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1151291http://bugzilla.suse.com/show_bug.cgi?id=1151291#c8
--- Comment #8 from Fabian Vogt <fvogt(a)suse.com> ---
(In reply to Michal Filka from comment #6)
> How was the live media connected to the machine? Using emulated DVD drive or
> e.g. booted over network?
Emulated drive, as you can see in autoinst-log.txt (here from 15.2):
https://openqa.opensuse.org/tests/1043695/file/autoinst-log.txt
[2019-09-28T22:09:36.001 CEST] [debug] running /usr/bin/qemu-img create -f
qcow2 -b
/var/lib/openqa/pool/1/openSUSE-Leap-15.2-KDE-Live-x86_64-Snapshot13.86-Media.iso
/var/lib/openqa/pool/1/raid/cd0-overlay0 964689920
[2019-09-28T22:09:36.016 CEST] [debug] Formatting
'/var/lib/openqa/pool/1/raid/cd0-overlay0', fmt=qcow2 size=964689920
backing_file=/var/lib/openqa/pool/1/openSUSE-Leap-15.2-KDE-Live-x86_64-Snapshot13.86-Media.iso
cluster_size=65536 lazy_refcounts=off refcount_bits=16
Use of uninitialized value in numeric ne (!=) at
/usr/lib/os-autoinst/OpenQA/Qemu/DriveDevice.pm line 124.
[2019-09-28T22:09:36.016 CEST] [debug] starting: /usr/bin/qemu-system-x86_64
-only-migratable -chardev ringbuf,id=serial0,logfile=serial0,logappend=on
-serial chardev:serial0 -soundhw hda -global isa-fdc.driveA= -m 1536 -cpu
qemu64 -netdev user,id=qanet0 -device
virtio-net,netdev=qanet0,mac=52:54:00:12:34:56 -boot
once=d,menu=on,splash-time=5000 -device usb-ehci -device usb-tablet -smp 1
-enable-kvm -no-shutdown -vnc :91,share=force-shared -device virtio-serial
-chardev
socket,path=virtio_console,server,nowait,id=virtio_console,logfile=virtio_console.log,logappend=on
-device
virtconsole,chardev=virtio_console,name=org.openqa.console.virtio_console
-chardev
socket,path=qmp_socket,server,nowait,id=qmp_socket,logfile=qmp_socket.log,logappend=on
-qmp chardev:qmp_socket -S -device virtio-scsi-pci,id=scsi0 -blockdev
driver=file,node-name=hd0-file,filename=/var/lib/openqa/pool/1/raid/hd0,cache.no-flush=on
-blockdev driver=qcow2,node-name=hd0,file=hd0-file,cache.no-flush=on -device
virtio-blk,id=hd0-device,drive=hd0,serial=hd0 -blockdev
driver=file,node-name=cd0-overlay0-file,filename=/var/lib/openqa/pool/1/raid/cd0-overlay0,cache.no-flush=on
-blockdev
driver=qcow2,node-name=cd0-overlay0,file=cd0-overlay0-file,cache.no-flush=on
-device scsi-cd,id=cd0-device,drive=cd0-overlay0,serial=cd0
--
You are receiving this mail because:
You are on the CC list for the bug.