October 2017 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1058103] New: twilio-utils needs to switch to php7 from php5 on Tumbleweed
by bugzilla_noreply＠novell.com 03 Oct '17

03 Oct '17

http://bugzilla.suse.com/show_bug.cgi?id=1058103 Bug ID: 1058103 Summary: twilio-utils needs to switch to php7 from php5 on Tumbleweed Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: archie.cobbs(a)gmail.com Reporter: tchvatal(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- We are removing php5 from SLE15 and Tubmleweed as such package in $SUMMARY still requires php5 to build and as such will be unresolvable. Please switch to use unversioned php or php7. -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1056020] New: mutt layout distorted after updating terminfo
by bugzilla_noreply＠novell.com 03 Oct '17

03 Oct '17

http://bugzilla.suse.com/show_bug.cgi?id=1056020 Bug ID: 1056020 Summary: mutt layout distorted after updating terminfo 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: glin(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- After updating terminfo to 6.0-27.2, mutt layout became strange. It happened both in konsole and xfce4-terminal. According to the discussion in the factory ML(*), it can be worked around by changing TERM from "xterm-256color" to "konsole" or some other types. Since "xterm-256color" is the default TERM for konsole and xfce4-terminal, we should fix the issue or the new user will encounter the issue without any clue. (*) https://lists.opensuse.org/opensuse-factory/2017-08/msg00443.html -- You are receiving this mail because: You are on the CC list for the bug.

1 20

[Bug 1055641] "Command failed" messages on shutdown phase
by bugzilla_noreply＠novell.com 03 Oct '17

03 Oct '17

http://bugzilla.suse.com/show_bug.cgi?id=1055641 http://bugzilla.suse.com/show_bug.cgi?id=1055641#c84 --- Comment #84 from Olli Tuominen <otuominen(a)suse.com> --- Just to info that when doing the "lvm vgchange -ay" timed and I stopped it with "ctrl+c" and run same command again it responded immediately. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1055641] "Command failed" messages on shutdown phase
by bugzilla_noreply＠novell.com 03 Oct '17

03 Oct '17

http://bugzilla.suse.com/show_bug.cgi?id=1055641 http://bugzilla.suse.com/show_bug.cgi?id=1055641#c83 --- Comment #83 from Olli Tuominen <otuominen(a)suse.com> --- Created attachment 742850 --> http://bugzilla.suse.com/attachment.cgi?id=742850&action=edit dmesg at shutdown phase -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1055641] "Command failed" messages on shutdown phase
by bugzilla_noreply＠novell.com 03 Oct '17

03 Oct '17

http://bugzilla.suse.com/show_bug.cgi?id=1055641 http://bugzilla.suse.com/show_bug.cgi?id=1055641#c82 Olli Tuominen <otuominen(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(otuominen(a)suse.co | |m) | --- Comment #82 from Olli Tuominen <otuominen(a)suse.com> --- Created attachment 742847 --> http://bugzilla.suse.com/attachment.cgi?id=742847&action=edit requred shutdown.txt -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1004830] New: gnome tells me I have no bluetooth adapter when I have bluetooth devices connected
by bugzilla_noreply＠novell.com 03 Oct '17

03 Oct '17

http://bugzilla.opensuse.org/show_bug.cgi?id=1004830 Bug ID: 1004830 Summary: gnome tells me I have no bluetooth adapter when I have bluetooth devices connected 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: msuchanek(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- I tried connecting bluetooth headphones to PC. After some fiddling I found that I have to - install pulseaudio BT module - restart pulseaudio (if running) - install firmware for dongle - insert dongle - bring hci0 interface up with hciconfig - connect device with bluetoothctl - switch pulseaudio sink to headphones In spite of this gnome-control-center bluetooth applet tells me I have no bluetooth hardware whatsoever (not even a dongle). -- You are receiving this mail because: You are on the CC list for the bug.

1 26

[Bug 1051248] VUL-1: PlayOnLinux: privacy issues
by bugzilla_noreply＠novell.com 03 Oct '17

03 Oct '17

http://bugzilla.novell.com/show_bug.cgi?id=1051248 http://bugzilla.novell.com/show_bug.cgi?id=1051248#c3 Eric Schirra <ecsos(a)schirra.net> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(astieger(a)suse.com | |) --- Comment #3 from Eric Schirra <ecsos(a)schirra.net> --- Hello Andreas, i have done a patch here https://build.opensuse.org/package/show/home%3Aecsos/PlayOnLinux Can you please check if this fix the issue? And can you check if it will generate no errors? -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 844041] [BlueZ5] Tracking Bug
by bugzilla_noreply＠novell.com 03 Oct '17

03 Oct '17

http://bugzilla.opensuse.org/show_bug.cgi?id=844041 Bug 844041 depends on bug 852851, which changed state. Bug 852851 Summary: Gnome cannot pair with bluetooth devices requiring a pin code http://bugzilla.opensuse.org/show_bug.cgi?id=852851 What |Removed |Added ---------------------------------------------------------------------------- Status|CONFIRMED |RESOLVED Resolution|--- |NORESPONSE -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 852851] Gnome cannot pair with bluetooth devices requiring a pin code
by bugzilla_noreply＠novell.com 03 Oct '17

03 Oct '17

http://bugzilla.opensuse.org/show_bug.cgi?id=852851 http://bugzilla.opensuse.org/show_bug.cgi?id=852851#c10 Flavio Castelli <fcastelli(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|CONFIRMED |RESOLVED Resolution|--- |NORESPONSE Flags|needinfo?(fcastelli(a)suse.co | |m) | --- Comment #10 from Flavio Castelli <fcastelli(a)suse.com> --- I ran away screaming from bluetooth devices sometimes ago, I cannot verify the fix anymore. Closing the issue. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1058028] SLES12 SP2: During boot, within 30seconds systemd-udevd daemons are getting killed and megaraid_sas failing to configure controller
by bugzilla_noreply＠novell.com 03 Oct '17

03 Oct '17

http://bugzilla.suse.com/show_bug.cgi?id=1058028 http://bugzilla.suse.com/show_bug.cgi?id=1058028#c15 Shivasharan Srikanteshwara <shivasharan.srikanteshwara(a)broadcom.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(shivasharan.srika | |nteshwara(a)broadcom.com) | --- Comment #15 from Shivasharan Srikanteshwara <shivasharan.srikanteshwara(a)broadcom.com> --- (In reply to Thomas Blume from comment #14) > (In reply to Shivasharan Srikanteshwara from comment #13) > > I have attached the requested logs, but there is nothing related to > > udev-settle service in the logs. > > Do I need to enable the service explicitly after OS install? > > How does this service get triggered? > > I can see multipathd.service and dmraid-activation.service have lines that > > refer to systemd-udev-settle.service. But both multipathd and dmraid are not > > enabled. > > > > linux-so07:/usr/lib/systemd # grep -R "udev-settle" * > > system/multipathd.service:Wants=systemd-udev-trigger.service > > systemd-udev-settle.service > > system/multipathd.service:After=multipathd.socket > > systemd-udev-trigger.service systemd-udev-settle.service > > system/dmraid-activation.service:After=systemd-udev-settle.service > > system/dmraid-activation.service:Wants=systemd-udev-settle.service > > > > Thanks. > > Indeed systemd-udev-settle.service is only triggered at certain conditions. > That doesn't look correct, it should be triggered by > systemd-udev-trigger.service. > Could you please do the following changes in systemd-udev-trigger.service: > > --> > --- /usr/lib/systemd/system/systemd-udev-trigger.service.orig 2017-09-29 > 10:10:08.423500663 +0200 > +++ /usr/lib/systemd/system/systemd-udev-trigger.service 2017-09-29 > 10:10:24.143500663 +0200 > @@ -9,7 +9,7 @@ > Description=udev Coldplug all Devices > Documentation=man:udev(7) man:systemd-udevd.service(8) > DefaultDependencies=no > -Wants=systemd-udevd.service > +Wants=systemd-udevd.service systemd-udev-settle.service > After=systemd-udevd-kernel.socket systemd-udevd-control.socket > systemd-hwdb-update.service > Before=sysinit.target > ConditionPathIsReadWrite=/sys > --< > > afterwards run mkinitrd and check whether the issue still appears after > reboot? This does alleviate my problem a bit but does not solve completely. The udev-settle service has a default timeout of 120secs. So with this the tolerance increases from 30secs to about 150seconds (120 secs for udev-settle to timeout + earlier 30secs for systemd-udevd to kill all child processes). Let me know if you require the logs with these changes. >From the various experiments I have been running, if "KillMode=mixed" option in systemd-udevd.service file is removed the problem goes away completely... Even without the udev-settle changes. With KillMode=mixed, systemd sends a SIGKILL after 30secs timeout. But the default behaviour is to send a SIGTERM after 30seconds. Looks like the SIGKILL is causing all the trouble here. Is the KillMode option required for systemd-udevd? -- You are receiving this mail because: You are on the CC list for the bug.

1 0