May 2019 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1113553] New: Out of date package: openSUSE:Factory/lxterminal is out of date
by bugzilla_noreply＠novell.com 06 Jul '20

06 Jul '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1113553 Bug ID: 1113553 Summary: Out of date package: openSUSE:Factory/lxterminal is out of date Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Enhancement Priority: P5 - None Component: Other Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: sean(a)suspend.net QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- https://build.opensuse.org/package/show/openSUSE:Factory/lxterminal is out of date. Current upstream is available at: https://github.com/lxde/lxterminal/archive/0.3.2.tar.gz. -- You are receiving this mail because: You are on the CC list for the bug.

2 2

[Bug 1080485] New: dracut: device mapper cannot be disassembled on shutdown
by bugzilla_noreply＠novell.com 04 Jul '20

04 Jul '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1080485 Bug ID: 1080485 Summary: dracut: device mapper cannot be disassembled on shutdown 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: Stromeko(a)NexGo.DE QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Since a few months dracut spews about two pages of errors/warnings on shutdown. Yesterday I halted the system instead of poweroff to be able to read those and it seems that the unmount of /oldroot fails and then the disassembly of the device-mapper devices errors out (maybe there'd been other errors before that that already rolled off the screen). Interestingly, I sometimes get a lot less of these errors when a kernel update just happened before. -- You are receiving this mail because: You are on the CC list for the bug.

2 60

[Bug 1104588] New: unable to configure /tmp using tmpfs
by bugzilla_noreply＠novell.com 02 Jul '20

02 Jul '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1104588 Bug ID: 1104588 Summary: unable to configure /tmp using tmpfs Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.0 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Installation Assignee: yast2-maintainers(a)suse.de Reporter: jcdole(a)free.fr QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- Up to Leap 42.3 you have the possibility to have "/tmp" using "tmpfs". In the partitioner you have the option to add partition using tmpfs : see http://paste.opensuse.org/87010584 This options is also indicated in : http://doc.opensuse.org/documentation/leap/reference/html/book.opensuse.ref… This is missing on leap 15.0 Any comment is welcome. -- You are receiving this mail because: You are on the CC list for the bug.

2 9

[Bug 1029775] New: systemd-presets-branding: Versioning inconsistency between openSUSE and SLE
by bugzilla_noreply＠novell.com 30 Jun '20

30 Jun '20

http://bugzilla.suse.com/show_bug.cgi?id=1029775 Bug ID: 1029775 Summary: systemd-presets-branding: Versioning inconsistency between openSUSE and SLE Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: lnussel(a)suse.com Reporter: sbrabec(a)suse.com QA Contact: qa-bugs(a)suse.de CC: fbui(a)suse.com, meissner(a)suse.com Blocks: 1012850 Found By: --- Blocker: --- While creating unified util-linux.spec that can be used for Tumbleweed, Leap and SLE, I found a versioning problem that makes impossible to require or conflict correct version of systemd-presets-branding symbol: systemd-presets-branding-SLE has version 12.1 in SLE 12 SP3. systemd-presets-branding-openSUSE has version 0.3 in Leap 42.3. systemd-presets-branding-openSUSE has version 0.4 in Tumbleweed. All three packages export symbol systemd-presets-branding = %{version} This versioning is not usable. Now I am going to add uuidd to both Leap and SLE. It requires version increment for branding package and conflict in util-linux package. We have to make branding versioning consistent between SLE and openSUSE. And we have to use numbers > 12.1. Maybe all branding packages should use: Version: %{suse_version} or Version: %{suse_version}.1 >From systemd-presets-branding-SLE: Wed Feb 12 16:35:33 UTC 2014 - meissner(a)suse.com - bump version to match product This versioning change was never done in systemd-presets-branding-SLE. -- You are receiving this mail because: You are on the CC list for the bug.

2 11

[Bug 1033277] New: Gnome does not scale all elements on 4k display with wayland
by bugzilla_noreply＠novell.com 29 Jun '20

29 Jun '20

http://bugzilla.suse.com/show_bug.cgi?id=1033277 Bug ID: 1033277 Summary: Gnome does not scale all elements on 4k display with wayland Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: GNOME Assignee: bnc-team-gnome(a)forge.provo.novell.com Reporter: tchvatal(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 720542 --> http://bugzilla.suse.com/attachment.cgi?id=720542&action=edit screenshot.png In multimonitor setup where one screen is 4k and other is normal fullhd the scaling seem to work weirdly. See the attached image, the gnome shell menu is still tiny as hell compared to the terminal bellow it. There also is a bit of problem with mutter as it by default does not scale the elements at all unless I patch it with patch I will attach as another comment. Last it seems that mutter does not tell this scaling factor to Qt applications, thus they are remaining really tiny, unless I override them via env variable. -- You are receiving this mail because: You are on the CC list for the bug.

2 8

[Bug 1001473] New: Can not record screen via gnome-shell's integrated screen-recorder
by bugzilla_noreply＠novell.com 26 Jun '20

26 Jun '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1001473 Bug ID: 1001473 Summary: Can not record screen via gnome-shell's integrated screen-recorder Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: GNOME Assignee: bnc-team-gnome(a)forge.provo.novell.com Reporter: tbechtold(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- This is Tumbleweed 20160925 with gnome-shell 3.22 (but I had the same problem with gnome-shell 3.20). When starting gnome-shell recording and after some seconds stop it, the resulting file has 0 bytes and no recording is available. The log output is: Sep 27 16:11:50 basilikum org.gnome.Shell.desktop[2613]: Recording to /home/tom/Videos/Screencast from 27.09.2016 16:11:50.webm Sep 27 16:11:50 basilikum gnome-shell[2613]: Error in recording pipeline: Internal data flow error. Sep 27 16:11:50 basilikum gnome-shell[2613]: recorder_record_frame: assertion 'recorder->current_pipeline != NULL' failed Sep 27 16:11:54 basilikum gnome-shell[2613]: shell_recorder_close: assertion 'recorder->state != RECORDER_STATE_CLOSED' failed -- You are receiving this mail because: You are on the CC list for the bug.

2 10

[Bug 1051358] New: Root password asked for when connecting to a new WiFi network
by bugzilla_noreply＠novell.com 26 Jun '20

26 Jun '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1051358 Bug ID: 1051358 Summary: Root password asked for when connecting to a new WiFi network Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: GNOME Assignee: bnc-team-gnome(a)forge.provo.novell.com Reporter: badshah400(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- The root password prompt pops up when trying to connect to a new WiFi network, whether that network requires authentication (in which case it still pops-up even if you choose to only save the password for just the current user) or not. This makes it impossible for someone without the root password to just use any public wifi. We should default to saving the authentication password, if any, for the current user (by default it tries to save for all users, which is really ugly) and then just stop asking for the root password. There are some old related bugs, all closed: bug 751211, bug 780137. -- You are receiving this mail because: You are on the CC list for the bug.

2 1

[Bug 1036432] New: gnome-shell crashes when restarting display-manager service
by bugzilla_noreply＠novell.com 26 Jun '20

26 Jun '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1036432 Bug ID: 1036432 Summary: gnome-shell crashes when restarting display-manager service Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: GNOME Assignee: bnc-team-gnome(a)forge.provo.novell.com Reporter: vliaskovitis(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 722858 --> http://bugzilla.opensuse.org/attachment.cgi?id=722858&action=edit core dump backtrace of gnome-shell gnome-shell crashes in mutter when attempting to restart the display-manager (systemctl restart display-manager) from a VT. Attached is the gnome-shell backtrace. It looks like an X11 error. Tested with TW20170407 and current TW. I can also open a GNOME bugzilla, if the issue is suspected to be an upstream mutter/gnome-shell bug. Sometimes when restarting the display-manager, there is no segfault, but there are weird input problems and/or screen tearing in the VT. I will open a separate ticket for that if I can reproduce. -- You are receiving this mail because: You are on the CC list for the bug.

2 2

[Bug 1135401] New: gnome-shell: Clutter.txt has been already deallocated — impossible to access it.
by bugzilla_noreply＠novell.com 26 Jun '20

26 Jun '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1135401 Bug ID: 1135401 Summary: gnome-shell: Clutter.txt has been already deallocated — impossible to access it. Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other URL: https://openqa.opensuse.org/tests/932899/modules/shutd own/steps/6 OS: Other Status: NEW Severity: Major Priority: P5 - None Component: GNOME Assignee: bnc-team-gnome(a)forge.provo.novell.com Reporter: normand(a)linux.vnet.ibm.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- gnome-shell: Clutter.txt has been already deallocated — impossible to access it. error reported in openQA create_hdd_gnome test before shutdown for ppc64le and aarch64 architectures on Tumbleweed. as previously reported by issue https://progress.opensuse.org/issues/51266 log extracted from https://openqa.opensuse.org/tests/935838/file/serial0.txt (aarch64) ``` [ 1125.390120] systemd[1]: Starting Flush Journal to Persistent Storage...^M [ 1125.468248] systemd[1]: Started Flush Journal to Persistent Storage.^M [ 1128.317763] gsd-color[1723]: unable to get EDID for xrandr-Virtual-1: unable to get EDID for output^M [ 1129.125793] gsd-color[1723]: unable to get EDID for xrandr-Virtual-1: unable to get EDID for output^M [ 1141.091327] gdm-password][3623]: gkr-pam: unlocked login keyring^M [ 1141.503517] NetworkManager[1051]: <info> [1558003632.8836] agent-manager: req[0xaaaafcf95e60, :1.22/org.gnome.Shell.NetworkAgent/1000]: agent registered^M [ 1141.533338] gnome-shell[1423]: Object Clutter.Text (0xaaaae81bb4c0), has been already deallocated — impossible to access it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs.^M [ 1141.538802] org.gnome.Shell.desktop[1423]: == Stack trace for context 0xaaaae5948240 ==^M [ 1141.541388] org.gnome.Shell.desktop[1423]: #0 ffffd55e32e0 b resource:///org/gnome/gjs/modules/overrides/GObject.js:468 (700001c70d0 @ 25)^M [ 1141.570835] org.gnome.Shell.desktop[1423]: #1 aaaae8970e58 i resource:///org/gnome/shell/ui/main.js:491 (700001e3670 @ 290)^M [ 1141.572953] org.gnome.Shell.desktop[1423]: #2 aaaae8970d90 i resource:///org/gnome/shell/ui/screenShield.js:1259 (700003cb280 @ 299)^M [ 1141.574821] org.gnome.Shell.desktop[1423]: #3 aaaae8970d10 i resource:///org/gnome/shell/ui/screenShield.js:1226 (700003cb1f0 @ 17)^M [ 1141.576684] org.gnome.Shell.desktop[1423]: #4 aaaae8970c88 i resource:///org/gnome/shell/gdm/authPrompt.js:493 (700003f3430 @ 61)^M [ 1141.578553] org.gnome.Shell.desktop[1423]: #5 aaaae8970c00 i resource:///org/gnome/shell/ui/unlockDialog.js:129 (70000400ca0 @ 25)^M [ 1141.590856] org.gnome.Shell.desktop[1423]: #6 aaaae8970b80 i resource:///org/gnome/shell/ui/screenShield.js:1226 (700003cb160 @ 46)^M [ 1141.593027] org.gnome.Shell.desktop[1423]: #7 aaaae8970b00 i resource:///org/gnome/shell/ui/screenShield.js:549 (700003c7670 @ 13)^M [ 1141.613247] org.gnome.Shell.desktop[1423]: #8 ffffd55e63e0 b resource:///org/gnome/gjs/modules/signals.js:142 (700001d8670 @ 386)^M [ 1141.615337] org.gnome.Shell.desktop[1423]: #9 aaaae8970a60 i resource:///org/gnome/gjs/modules/overrides/Gio.js:169 (700001ec3a0 @ 39)^M ``` For ppc64le, the failure is solid. For aarch64 seems to be intermittent; so probably a timing issue. ## Observation openQA test in scenario opensuse-Tumbleweed-DVD-ppc64le-create_hdd_gnome@ppc64le fails in [shutdown](https://openqa.opensuse.org/tests/932899/modules/shutdown/steps/6) ## Test suite description image creation job used as parent for other jobs testing based on existing installation. GUI-Installation and selecting the gnome desktop during installation. ## Reproducible Fails since (at least) Build [20190505](https://openqa.opensuse.org/tests/925245) ## Expected result Last good: [20190430](https://openqa.opensuse.org/tests/922364) (or more recent) ## Further details Always latest result in this scenario: [latest](https://openqa.opensuse.org/tests/latest?machine=ppc64le&arch=ppc64… -- You are receiving this mail because: You are on the CC list for the bug.

2 4

[Bug 1112824] New: Severe Performance Degradation with update to latest tumbleweed (20181018)
by bugzilla_noreply＠novell.com 26 Jun '20

26 Jun '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1112824 Bug ID: 1112824 Summary: Severe Performance Degradation with update to latest tumbleweed (20181018) Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: Other Status: NEW Severity: Major Priority: P5 - None Component: GNOME Assignee: bnc-team-gnome(a)forge.provo.novell.com Reporter: ldewey(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 786777 --> http://bugzilla.opensuse.org/attachment.cgi?id=786777&action=edit journalctl output There is a severe performance degradation when upgrading to the latest version of tumbleweed. Mouse movements are extremely jittery, typing is choppy, slow, and will often repeat characters which were only typed once. Behavior is consistent with all things utilizing gnome-shell version 3.30.0 and 3.30.1 (attempted to use GNOME_factory repository). Performance is bad enough to render the entire desktop environment virtually unusable. Journalctl Logs: ================ (See attached file). System Information: =================== (See attached file). -- You are receiving this mail because: You are on the CC list for the bug.

2 186