http://bugzilla.opensuse.org/show_bug.cgi?id=1135550
Bug ID: 1135550
Summary: After last update (kernel 5.1.2-1) several program get
segmentation fault error
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: virex(a)mail.ru
QA Contact: qa-bugs(a)suse.de
Found By: ---
Blocker: ---
After last update (kernel 5.1.2-1) several program get segmentation fault error
for example
mc
deadbeef
soundconverter
qmmp
--
You are receiving this mail because:
You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1137055
Bug ID: 1137055
Summary: Build20190529: wine-32bit uninstallable, version
4.9-1.15 was not published?
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: okurz(a)suse.com
QA Contact: qa-bugs(a)suse.de
Found By: ---
Blocker: ---
## Observation
As reported in
https://lists.opensuse.org/opensuse-factory/2019-06/msg00005.htmlhttps://download.opensuse.org/tumbleweed/repo/oss/x86_64/?P=wine*
looks incomplete indeed with
wine-4.8-1.1.x86_64.rpm 14-May-2019 13:03
wine-4.9-1.15.x86_64.rpm 30-May-2019 12:38
wine-32bit-4.8-1.1.x86_64.rpm 14-May-2019 12:41
I am not sure how I should read
https://build.opensuse.org/package/show/openSUSE:Factory/wine
but at least
https://build.opensuse.org/package/live_build_log/openSUSE:Factory/wine/sta…
shows that
RPMS/x86_64/wine-32bit-4.9-1.15.x86_64.rpm
is correctly generated but was not published as part of the past two snapshots
20190527 or 20190529 it seems.
## Reproducible
yes
```
docker run -it --rm opensuse/tumbleweed 'zypper -n in wine wine-32bit'
```
yields
```
Problem: nothing provides wine-32bit = 4.9 needed by wine-4.9-1.15.x86_64
Solution 1: do not install wine-4.9-1.15.x86_64
Solution 2: break wine-4.9-1.15.x86_64 by ignoring some of its dependencies
```
--
You are receiving this mail because:
You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1137054
Bug ID: 1137054
Summary: Python Appindicator segfaults on Tumbleweed - fine on
Leap
Classification: openSUSE
Product: openSUSE Tumbleweed
Version: Current
Hardware: x86-64
OS: Other
Status: NEW
Severity: Normal
Priority: P5 - None
Component: KDE Workspace (Plasma)
Assignee: opensuse-kde-bugs(a)opensuse.org
Reporter: richard.eigenmann(a)gmail.com
QA Contact: qa-bugs(a)suse.de
Found By: ---
Blocker: ---
Have been experimenting with system tray icons and came across a very simple
Python example how to use them. It worked fine on my openSUSE Leap desktop and
segfaults on my Tumbleweed laptop. Both fully updated as of today (1 June
2019).
Here is the Python code that puts an avatar in the system tray with a menu item
to open up a zenity info dialog with your user name or shut down the script:
#!/usr/bin/python3
# Inspiration:
https://fosspost.org/tutorials/custom-system-tray-icon-indicator-linux
# Install: sudo zypper in typelib-1_0-AppIndicator3-0_1
# Install: sudo zypper in zenity
import os
import gi
gi.require_version('Gtk', '3.0')
gi.require_version('AppIndicator3', '0.1')
from gi.repository import Gtk as gtk, AppIndicator3 as appindicator
def main():
indicator = appindicator.Indicator.new("systrayExperiment",
"avatar-default-symbolic", appindicator.IndicatorCategory.APPLICATION_STATUS)
indicator.set_status(appindicator.IndicatorStatus.ACTIVE)
indicator.set_menu(menu())
indicator.set_title("Cute Systray Experiment")
gtk.main()
def menu():
menu = gtk.Menu()
command_hello = gtk.MenuItem('Say Hello')
command_hello.connect('activate', hello)
menu.append(command_hello)
exittray = gtk.MenuItem('Exit Tray')
exittray.connect('activate', quit)
menu.append(exittray)
menu.show_all()
return menu
def hello(_):
os.system("/usr/bin/zenity --info --text \"Hello, $(whoami)!\"")
def quit(_):
gtk.main_quit()
if __name__ == "__main__":
main()
Output from Tumbleweed:
me@laptop:~> ./minimalAppIndicator.py
(process:3049): Gtk-CRITICAL **: 16:37:30.781: gtk_icon_theme_get_for_screen:
assertion 'GDK_IS_SCREEN (screen)' failed
./minimalAppIndicator.py:14: Warning: invalid (NULL) pointer instance
indicator = appindicator.Indicator.new("systrayExperiment",
"avatar-default-symbolic", appindicator.IndicatorCategory.APPLICATION_STATUS)
./minimalAppIndicator.py:14: Warning: g_signal_connect_data: assertion
'G_TYPE_CHECK_INSTANCE (instance)' failed
indicator = appindicator.Indicator.new("systrayExperiment",
"avatar-default-symbolic", appindicator.IndicatorCategory.APPLICATION_STATUS)
(process:3049): Gtk-CRITICAL **: 16:37:30.784:
_gtk_style_provider_private_get_settings: assertion
'GTK_IS_STYLE_PROVIDER_PRIVATE (provider)' failed
(process:3049): Gtk-CRITICAL **: 16:37:30.784:
_gtk_style_provider_private_get_settings: assertion
'GTK_IS_STYLE_PROVIDER_PRIVATE (provider)' failed
(process:3049): Gtk-CRITICAL **: 16:37:30.784:
_gtk_style_provider_private_get_settings: assertion
'GTK_IS_STYLE_PROVIDER_PRIVATE (provider)' failed
Segmentation fault (core dumped)
--
You are receiving this mail because:
You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1136436
Bug ID: 1136436
Summary: btrfs mainainance crashed and left system unbootable
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: P.Suetterlin(a)royac.iac.es
QA Contact: qa-bugs(a)suse.de
Found By: ---
Blocker: ---
Last night my Tumbleweed system (20190520) performed the regular btrfs
maintainance. I was working at that time, and noticed that the application I
used did not respond anymore. Other stuff seemed to continue working (e.g.,
bringing an editor window in front). So I thought its the application and
tried to terminate it, but nothing happened. Short after that everything on
the screen became unresponsive, keyboard LEDS didn't react on state change etc.
I finally pressed the power button to restart the system (laptop, no reset).
However, the boot did not succeed. It hang, systemd reporting its waiting for
four processes. Two of those were 'flush journal to persistent memory' and
'save rfkill switch state'. For some time the console display showed those
jobs in a loop, then it would also stop and become unresponsive.
This was consistent, I tried some three times or so.
So I finally booted from an USB rescue stick. I could mount the FS without
problems. Not knowing better, I ran a 'btrfs scrub' on it, which finished
after some 1-2 minutes without errors. Not sure what to do next, I rebooted
from the hard disk - and the system came up clean.
By now I assume the crashes/hangs were only temporary(?) and the system might
have returned after longer waits, but I'm not absolutely sure.
However, looking at the logfile from the first hang I found some issue where
balancing failed with a 'no space left on device (although it has/had 5.6G free
when starting). More alarming was this one:
May 27 00:02:10 woodstock.pitnet btrfs-balance.sh[17806]: Done, had to relocate
1 out of 84 chunks
May 27 00:02:10 woodstock.pitnet kernel: BTRFS info (device sda2): balance:
start -musage=10 -susage=10
May 27 00:02:10 woodstock.pitnet kernel: BTRFS info (device sda2): relocating
block group 398848950272 flags
system
May 27 00:02:10 woodstock.pitnet kernel: BTRFS info (device sda2): relocating
block group 398815395840 flags
metadata
May 27 00:02:10 woodstock.pitnet kernel: assertion failed: root, file:
fs/btrfs/relocation.c, line: 804
May 27 00:02:10 woodstock.pitnet kernel: ------------[ cut here ]------------
May 27 00:02:10 woodstock.pitnet kernel: kernel BUG at fs/btrfs/ctree.h:3518!
Unfortunately the log ends with this line, so no more info.
The full system log starting with the btrfs maintainance call is available at
http://paste.opensuse.org/24906643 (1 month lifetime - should I rather attach
it?)
--
You are receiving this mail because:
You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1135794
Bug ID: 1135794
Summary: Strange translation errot
Classification: openSUSE
Product: openSUSE Tumbleweed
Version: Current
Hardware: x86-64
OS: SUSE Other
Status: NEW
Severity: Critical
Priority: P5 - None
Component: Translations
Assignee: ke(a)suse.com
Reporter: genetus(a)yandex.ru
QA Contact: ke(a)suse.com
Found By: ---
Blocker: ---
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:69.0) Gecko/20100101
Firefox/69.0
Build Identifier:
After last "zypper dup" udate on several computer (my home PC and my home
file-sharing server) have strange bahaviour.
In my local (Russian) localization in console:
- Midnight Commander not work: segment fault,
- yast software & repository manager component not run (no error in console
output);
In GUI (KDE) "yast2 sw_single" not run and no console error output.
If I force change localization to en_EN, all these app work propertly. (but in
install screen yast software component spam @ as empty space in console). GUI
not tested.
When PC installed I chose Russian language at license step - all other setup
was on russian language.
Reproducible: Always
Steps to Reproduce:
1. Install ru languages pack
2. Chose russian localization in profile
3. Enter console.
4. Run mc - error
5. Run yast, Select software management (Управление программным обеспечением)
6. Nothing happen
Actual Results:
MC - segment fault: Ошибка сегментирования (стек памяти сброшен на диск)
Yast - Nothing happen
Expected Results:
MC - Run MC
YAST - Run yast software management
--
You are receiving this mail because:
You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1137051
Bug ID: 1137051
Summary: Virtualbox guest additions fails on openSUSE
Tumbleweed
Classification: openSUSE
Product: openSUSE Tumbleweed
Version: Current
Hardware: x86-64
OS: Other
Status: NEW
Severity: Minor
Priority: P5 - None
Component: Kernel
Assignee: kernel-maintainers(a)forge.provo.novell.com
Reporter: lars(a)schmidtstenberg.dk
QA Contact: qa-bugs(a)suse.de
Found By: ---
Blocker: ---
Created attachment 806585
--> http://bugzilla.opensuse.org/attachment.cgi?id=806585&action=edit
vbox guest additions run log
Hi,
After successful Virtualbox 6.0.4 install, tried to run Virtualbox guest
additions (as I usually do w/o problems on other linux distributions) but it
fails.
First time because guest additions script claims kernel headers are missing (so
no recompilation of kernel possible). After adding kernel-develop module in
Yast2, rerunning script now fails for another reason - see attached log file
from Virtualbox guest additions script.
BR
--
You are receiving this mail because:
You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1136927
Bug ID: 1136927
Summary: [Build 20190528] System does not use same network
names after update
Classification: openSUSE
Product: openSUSE Tumbleweed
Version: Current
Hardware: Other
URL: https://openqa.opensuse.org/tests/945719/modules/check
_network/steps/3
OS: Other
Status: NEW
Severity: Critical
Priority: P5 - None
Component: Basesystem
Assignee: bnc-team-screening(a)forge.provo.novell.com
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-update_Leap_15.0_cryptlvm@uefi fails in
[check_network](https://openqa.opensuse.org/tests/945719/modules/check_netwo…
## Test suite description
Upgrade scenario with cryptlvm for Leap 15.0.
Maintainer: riafarov.
## Reproducible
Fails since (at least) Build
[20190528](https://openqa.opensuse.org/tests/945450)
## Expected result
Last good: [20190527](https://openqa.opensuse.org/tests/943840) (or more
recent)
## Further details
Always latest result in this scenario:
[latest](https://openqa.opensuse.org/tests/latest?distri=opensuse&machine=ue…
So far, we kept the network name from an openSUSE Leap 15.x update (using eth0)
to Tumbleweed, in order to have 'least surprise' for the user.
With the update to dracut 0.49+git... this seems to have gotten lost: as can be
seen in the referenced job run, the system now uses an ens4 network interface
name (and as a consequence has no valid network configuration, as
/etc/sysconfig/network only has a config for eth0)
This is critical, as a remote-upgraded system will not be accessible without
network interfaces coming up
--
You are receiving this mail because:
You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1133084
Bug 1133084 depends on bug 1136862, which changed state.
Bug 1136862 Summary: LTO: python-CherryPy build fails
http://bugzilla.suse.com/show_bug.cgi?id=1136862
What |Removed |Added
----------------------------------------------------------------------------
Status|IN_PROGRESS |RESOLVED
Resolution|--- |FIXED
--
You are receiving this mail because:
You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1136862http://bugzilla.suse.com/show_bug.cgi?id=1136862#c4
Martin Liška <martin.liska(a)suse.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|IN_PROGRESS |RESOLVED
Resolution|--- |FIXED
--- Comment #4 from Martin Liška <martin.liska(a)suse.com> ---
Fixed, thanks you Matej.
--
You are receiving this mail because:
You are on the CC list for the bug.