http://bugzilla.opensuse.org/show_bug.cgi?id=1204018
Bug ID: 1204018
Summary: Virtualization:vagrant/vagrant-libvirt: Bug vagrant up
fail with public_network
Classification: openSUSE
Product: openSUSE.org
Version: unspecified
Hardware: Other
OS: Other
Status: NEW
Severity: Normal
Priority: P5 - None
Component: 3rd party software
Assignee: dcermak(a)suse.com
Reporter: thieryy(a)ovh.fr
QA Contact: screening-team-bugs(a)suse.de
CC: opensuse_buildservice(a)ojkastl.de
Found By: ---
Blocker: ---
Hello,
I try to set up a VM on public network (bridge), but I have this error :
> vagrant up resolver
Bringing machine 'resolver' up with 'libvirt' provider...
/usr/share/vagrant/gems/gems/vagrant-libvirt-0.10.2/lib/vagrant-libvirt/driver.rb:205:in
`list_host_devices': undefined method `client' for nil:NilClass (NoMethodError)
@connection.client.list_all_interfaces
^^^^^^^
from
/usr/share/vagrant/gems/gems/vagrant-libvirt-0.10.2/lib/vagrant-libvirt/config.rb:1217:in
`host_devices'
from
/usr/share/vagrant/gems/gems/vagrant-libvirt-0.10.2/lib/vagrant-libvirt/config.rb:1070:in
`block in validate'
from
/usr/share/vagrant/gems/gems/vagrant-libvirt-0.10.2/lib/vagrant-libvirt/config.rb:1056:in
`each'
from
/usr/share/vagrant/gems/gems/vagrant-libvirt-0.10.2/lib/vagrant-libvirt/config.rb:1056:in
`each_with_index'
from
/usr/share/vagrant/gems/gems/vagrant-libvirt-0.10.2/lib/vagrant-libvirt/config.rb:1056:in
`validate'
from
/usr/share/vagrant/gems/gems/vagrant-2.2.19/plugins/kernel_v2/config/vm.rb:960:in
`validate'
from
/usr/share/vagrant/gems/gems/vagrant-2.2.19/lib/vagrant/config/v2/root.rb:71:in
`block in validate'
from
/usr/share/vagrant/gems/gems/vagrant-2.2.19/lib/vagrant/config/v2/root.rb:66:in
`each'
from
/usr/share/vagrant/gems/gems/vagrant-2.2.19/lib/vagrant/config/v2/root.rb:66:in
`validate'
from
/usr/share/vagrant/gems/gems/vagrant-2.2.19/lib/vagrant/action/builtin/config_validate.rb:15:in
`call'
from
/usr/share/vagrant/gems/gems/vagrant-2.2.19/lib/vagrant/action/warden.rb:48:in
`call'
from
/usr/share/vagrant/gems/gems/vagrant-2.2.19/lib/vagrant/action/builder.rb:149:in
`call'
from
/usr/share/vagrant/gems/gems/vagrant-2.2.19/lib/vagrant/action/runner.rb:89:in
`block in run'
from
/usr/share/vagrant/gems/gems/vagrant-2.2.19/lib/vagrant/util/busy.rb:19:in
`busy'
from
/usr/share/vagrant/gems/gems/vagrant-2.2.19/lib/vagrant/action/runner.rb:89:in
`run'
from
/usr/share/vagrant/gems/gems/vagrant-2.2.19/lib/vagrant/machine.rb:246:in
`action_raw'
from
/usr/share/vagrant/gems/gems/vagrant-2.2.19/lib/vagrant/machine.rb:215:in
`block in action'
from
/usr/share/vagrant/gems/gems/vagrant-2.2.19/lib/vagrant/environment.rb:614:in
`lock'
from
/usr/share/vagrant/gems/gems/vagrant-2.2.19/lib/vagrant/machine.rb:201:in
`call'
from
/usr/share/vagrant/gems/gems/vagrant-2.2.19/lib/vagrant/machine.rb:201:in
`action'
from
/usr/share/vagrant/gems/gems/vagrant-2.2.19/lib/vagrant/batch_action.rb:86:in
`block (2 levels) in run'
Here is the Vagrantfile I used :
Vagrant.configure("2") do |config|
config.vm.network :public_network
config.vm.define "resolver" do |resolver|
resolver.vm.box = "opensuse/Tumbleweed.x86_64"
resolver.vm.hostname = "resolver00"
end
config.vm.define "dns" do |dns|
dns.vm.box = "opensuse/Tumbleweed.x86_64"
dns.vm.hostname = "dns00"
end
end
The vagrant-libvirt come with the release 0.10.2 on OpenSUSE Tumbleweed:
> vagrant plugin list
vagrant-libvirt (0.10.2, system)
https://build.opensuse.org/package/show/Virtualization:vagrant/vagrant-libv…
I think this related to this issue :
https://github.com/vagrant-libvirt/vagrant-libvirt/issues/1561
A fix as already been published :
https://github.com/vagrant-libvirt/vagrant-libvirt/releases/tag/0.10.4
If you have some time, can you upgrade the package please? :)
Best regards,
Rollniak
--
You are receiving this mail because:
You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1203967
Bug ID: 1203967
Summary: calibre complains about missing
libQt6Gui.so.6(Qt_6.3.2_PRIVATE_API)(64bit) thus
uninstallable (or forces uninstall if installed,
during zypper dup)
Classification: openSUSE
Product: openSUSE Tumbleweed
Version: Current
Hardware: x86-64
OS: openSUSE Tumbleweed
Status: NEW
Severity: Normal
Priority: P5 - None
Component: Other
Assignee: screening-team-bugs(a)suse.de
Reporter: stakanov(a)disroot.org
QA Contact: qa-bugs(a)suse.de
Found By: ---
Blocker: ---
#### YaST2 conflicts list - generated 2022-10-03 17:43:53 ####
nessun elemento fornisce 'libQt6Gui.so.6(Qt_6.3.2_PRIVATE_API)(64bit)'
obbligatorio per calibre-6.5.0-1.1.x86_64 da installare
[ ] non installare calibre-6.5.0-1.1.x86_64
[ ] installa comunque calibre-6.5.0-1.1.x86_64 ignorando alcune delle sue
dipendenze
#### YaST2 conflicts list END ###
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1202541https://bugzilla.suse.com/show_bug.cgi?id=1202541#c32
Bernhard Wiedemann <bwiedemann(a)suse.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |WORKSFORME
--- Comment #32 from Bernhard Wiedemann <bwiedemann(a)suse.com> ---
Did not re-encounter trouble so far, so let's close it for now.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1198523https://bugzilla.suse.com/show_bug.cgi?id=1198523#c26
--- Comment #26 from Swamp Workflow Management <swamp(a)suse.de> ---
SUSE-RU-2022:3521-1: An update that has one recommended fix can now be
installed.
Category: recommended (critical)
Bug References: 1198523
CVE References:
JIRA References:
Sources used:
openSUSE Leap 15.4 (src): lvm2-2.03.05-150400.178.1,
lvm2-device-mapper-2.03.05-150400.178.1, lvm2-lvmlockd-2.03.05-150400.178.1
SUSE Linux Enterprise Module for Basesystem 15-SP4 (src):
lvm2-2.03.05-150400.178.1, lvm2-device-mapper-2.03.05-150400.178.1
SUSE Linux Enterprise High Availability 15-SP4 (src):
lvm2-lvmlockd-2.03.05-150400.178.1
NOTE: This line indicates an update has been released for the listed
product(s). At times this might be only a partial fix. If you have questions
please reach out to maintenance coordination.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1203363https://bugzilla.suse.com/show_bug.cgi?id=1203363#c3
Takashi Iwai <tiwai(a)suse.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |tiwai(a)suse.com
Assignee|kernel-bugs(a)opensuse.org |rgoldwyn(a)suse.com
--- Comment #3 from Takashi Iwai <tiwai(a)suse.com> ---
Tossed to filesystem team.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1203719https://bugzilla.suse.com/show_bug.cgi?id=1203719#c3
Takashi Iwai <tiwai(a)suse.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
CC| |tiwai(a)suse.com
Resolution|--- |DUPLICATE
--- Comment #3 from Takashi Iwai <tiwai(a)suse.com> ---
This is a known regression of intel_iommu. Fixed in the next release.
*** This bug has been marked as a duplicate of bug 1203505 ***
--
You are receiving this mail because:
You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1202037
Bug ID: 1202037
Summary: Certain Characters Displayed Wrong on zh-MO Locale if
Noto TC fonts are installed as well as Noto HK fonts
Classification: openSUSE
Product: openSUSE Tumbleweed
Version: Current
Hardware: Other
OS: Other
Status: NEW
Severity: Normal
Priority: P5 - None
Component: Other
Assignee: screening-team-bugs(a)suse.de
Reporter: pirateclip(a)protonmail.com
QA Contact: qa-bugs(a)suse.de
Found By: ---
Blocker: ---
Created attachment 860522
--> http://bugzilla.opensuse.org/attachment.cgi?id=860522&action=edit
zh-MO Locale with Noto TC and Noto HK installed
1. Enable zh-MO Locale
2. Install Noto HK Fonts (noto-sans-hk-fonts, noto-serif-hk-fonts,
noto-sans-hk-mono-fonts)
3. Take a screenshot of what the character���������appears as on Kate. (You can zoom
in kate via Ctrl+Scroll)
4. Install Noto TC Fonts (noto-sans-tc-fonts, noto-serif-tc-fonts,
noto-sans-tc-mono-fonts)
3. Take another screenshot of what the character���������appears as on Kate. It will
appear incorrectly as the (Taiwan) TC version instead of the HK (Traditional
Chinese) version.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1196357https://bugzilla.suse.com/show_bug.cgi?id=1196357#c3
Chester Lin <chester.lin(a)suse.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |CONFIRMED
--- Comment #3 from Chester Lin <chester.lin(a)suse.com> ---
It looks like a read-speed limitation on the MMC controller of hifive unmatched
since I tried manually loading the initrd (97M) from a SD card to the system
RAM by u-boot CLI and it was as slow [over 1 min] as I observed in efistub. The
same symptom can be found on the preload image offered by sifive as well [cmd:
ext4load].
Loading the initrd from NVMe is much faster.
--
You are receiving this mail because:
You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1041794
Bug ID: 1041794
Summary: Recent update breaks some Youtube videos
Classification: openSUSE
Product: openSUSE Distribution
Version: Leap 42.2
Hardware: x86-64
OS: Linux
Status: NEW
Severity: Normal
Priority: P5 - None
Component: Other
Assignee: bnc-team-screening(a)forge.provo.novell.com
Reporter: james.knott(a)rogers.com
QA Contact: qa-bugs(a)suse.de
Found By: ---
Blocker: ---
An update around mid May caused some Youtube videos to fail. When this
happens, loading the video stops, leaving only the dot going around a circle
showing. This happens with Firefox, Seamonkey and Chromium browsers. The
videos that fail play OK in Windows. To verify the problem, I tried the videos
with a VirtualBox VM or a fresh 42.2 install. The problem videos played. I
then cloned the VM and ensured the videos played. I then updated the clone to
the latest updates and now the videos fail. The original non-updated VM still
continued to play the videos. It appears the problem is related to the type of
codec used. For example, videos with the vp9 codec play, but those with
avc1.4d400d now fail.
Here are 2 links, this one plays OK:
https://www.youtube.com/watch?v=Rzqq581Q3Us
But this one doesn't:
https://www.youtube.com/watch?v=t8tdmaEhMHE
Again, this problem occurred recently. Videos that played a few weeks ago now
fail.
--
You are receiving this mail because:
You are on the CC list for the bug.