June 2019 - openSUSE Bugs - openSUSE Mailing Lists

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

05 Jun '19

http://bugzilla.suse.com/show_bug.cgi?id=1135401 http://bugzilla.suse.com/show_bug.cgi?id=1135401#c4 xiaoguang wang <xwang(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(xwang(a)suse.com) | --- Comment #4 from xiaoguang wang <xwang(a)suse.com> --- (In reply to Yifan Jiang from comment #3) > From appearance of the openQA screenshot, it looks the error message pops up > when an unlock happens. Since GDM 3.32 works quite differently, perhaps it > makes more sense to diagnose it when gdm 3.32 is shipped. > > @Xiaoguang, WDYT? The fault happened since gnome upgraded to 3.32. Test case works well on gnome 3.30. After inputting password on unlock screen, we should see the desktop, but we get another login screen, the 'unlock' button becomes 'next' button. I don't know what happens here, I need journal log to analyse. And It's better to test it on a real ppc machine. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1136815] Unable to install from kubic dvd due to missing bcache-tools
by bugzilla_noreply＠novell.com 05 Jun '19

05 Jun '19

http://bugzilla.suse.com/show_bug.cgi?id=1136815 http://bugzilla.suse.com/show_bug.cgi?id=1136815#c2 Thorsten Kukuk <kukuk(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #2 from Thorsten Kukuk <kukuk(a)suse.com> --- Will be on the DVD with one of the next snapshots. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1136549] New: ncurses (yast2_lan, dialog) looks bad in LXDE but is ok on GNOME installation
by bugzilla_noreply＠novell.com 05 Jun '19

05 Jun '19

http://bugzilla.opensuse.org/show_bug.cgi?id=1136549 Bug ID: 1136549 Summary: ncurses (yast2_lan, dialog) looks bad in LXDE but is ok on GNOME installation Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other URL: https://openqa.opensuse.org/tests/944165/modules/yast2 _lan/steps/13 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: guillaume.gardet(a)arm.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- yast2_lan ncurses in LXDE (broken): https://openqa.opensuse.org/tests/944165/modules/yast2_lan/steps/13 yast2_lan ncurses in GNOME (ok): https://openqa.opensuse.org/tests/944179#step/yast2_lan/11 -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1136246] New: Invalid certificate with Admin node. build 20190521
by bugzilla_noreply＠novell.com 05 Jun '19

05 Jun '19

http://bugzilla.suse.com/show_bug.cgi?id=1136246 Bug ID: 1136246 Summary: Invalid certificate with Admin node. build 20190521 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kubic Assignee: kubic-bugs(a)opensuse.org Reporter: jason.evans(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Issue: Unable to initialize certificates or kubicctl admin:~ # kubicctl certificates initialize Error invoking certstrap: exit status 1 CA with specified name "Kubic-Control-CA" already exists! Error creating CA: exit status 1 admin:~ # kubicctl init --pod-network cilium Initializing kubernetes master can take several minutes, please be patient. Could not initialize: rpc error: code = Unavailable desc = all SubConns are in TransientFailure, latest connection error: connection error: desc = "transport: authentication handshake failed: x509: certificate has expired or is not yet valid" -- You are receiving this mail because: You are on the CC list for the bug.

1 6

[Bug 1135217] [Build 20190513] openQA test fails in kdump_and_crash - no kdump initial ramdisk found
by bugzilla_noreply＠novell.com 05 Jun '19

05 Jun '19

http://bugzilla.suse.com/show_bug.cgi?id=1135217 http://bugzilla.suse.com/show_bug.cgi?id=1135217#c6 Jiri Slaby <jslaby(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|IN_PROGRESS |RESOLVED Resolution|--- |FIXED --- Comment #6 from Jiri Slaby <jslaby(a)suse.com> --- We are done here. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1134554] New: yast2 online update fails with wrong 'No update repository configured yet' message
by bugzilla_noreply＠novell.com 05 Jun '19

05 Jun '19

http://bugzilla.opensuse.org/show_bug.cgi?id=1134554 Bug ID: 1134554 Summary: yast2 online update fails with wrong 'No update repository configured yet' message Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.1 Hardware: aarch64 URL: https://openqa.opensuse.org/tests/928646/modules/yast2 _control_center/steps/29 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 Assignee: yast2-maintainers(a)suse.de Reporter: guillaume.gardet(a)arm.com QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- ## Observation openQA test in scenario opensuse-15.1-DVD-aarch64-yast2_gui@aarch64 fails in [yast2_control_center](https://openqa.opensuse.org/tests/928646/modules/yast… ## Test suite description Maintainer: zluo, riafarov Test for yast2 UI, GUI only. Running on created gnome images which provides both text console for ncurses UI tests as well as the gnome environment for the GUI tests. Temporarily added YAST2_GUI_TERMINATE_PREVIOUS_INSTANCES to see if helps. This variable triggers code which terminates all yast2 processes before starting new one. (see poo#26104). ## Reproducible Fails since (at least) Build [457.7](https://openqa.opensuse.org/tests/928438) ## Expected result Last good: [457.6](https://openqa.opensuse.org/tests/927037) (or more recent) ## Further details Always latest result in this scenario: [latest](https://openqa.opensuse.org/tests/latest?machine=aarch64&arch=aarch… -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1137071] New: teamviewer 12,13,14 versions get error about verification failed after update to wine 4.9-1006.1
by bugzilla_noreply＠novell.com 05 Jun '19

05 Jun '19

http://bugzilla.opensuse.org/show_bug.cgi?id=1137071 Bug ID: 1137071 Summary: teamviewer 12,13,14 versions get error about verification failed after update to wine 4.9-1006.1 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: virex(a)mail.ru QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- teamviewer 12,13,14 versions get error: Verification of your teamviewer version failed! Teamviewer will quit for security reasons. Please reinstall teamviewer. console output is here: ~> winefile 002b:fixme:ole:CoInitializeSecurity ((nil),-1,(nil),(nil),0,3,(nil),0,(nil)) - stub! 002b:fixme:heap:RtlSetHeapInformation (nil) 1 (nil) 0 stub 002b:fixme:process:SetProcessDEPPolicy (3): stub 002b:fixme:process:GetProcessMitigationPolicy (0xffffffff, 6, 0x32fd8c, 4): stub 002b:fixme:process:SetProcessMitigationPolicy (6, 0x32fd8c, 4): stub 002b:fixme:msg:ChangeWindowMessageFilter 233 00000001 002b:fixme:msg:ChangeWindowMessageFilter 4a 00000001 002b:fixme:msg:ChangeWindowMessageFilter 407 00000001 002b:fixme:msg:ChangeWindowMessageFilter 49 00000001 002c:fixme:console:CONSOLE_DefaultHandler Terminating process 8 on event 0 -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1134303] New: aarch64 kernel are not signed
by bugzilla_noreply＠novell.com 05 Jun '19

05 Jun '19

http://bugzilla.opensuse.org/show_bug.cgi?id=1134303 Bug ID: 1134303 Summary: aarch64 kernel are not signed Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: aarch64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-maintainers(a)forge.provo.novell.com Reporter: guillaume.gardet(a)arm.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- On aarch64, "pesign -S -i /boot/Image-5.0.7-5.g8a6bcaf-default" returns: No signatures found. This is because in kernel-binary.spec.in, we only have the x86_64 image format: BRP_PESIGN_FILES="/boot/vmlinuz-%kernelrelease-%build_flavor" For aarch64, we should have: BRP_PESIGN_FILES="/boot/Image-%kernelrelease-%build_flavor" -- You are receiving this mail because: You are on the CC list for the bug.

1 25

[Bug 1137290] New: GNOME:Factory/gdm: journal shows Unknown modifiers in command '+d'
by bugzilla_noreply＠novell.com 05 Jun '19

05 Jun '19

http://bugzilla.opensuse.org/show_bug.cgi?id=1137290 Bug ID: 1137290 Summary: GNOME:Factory/gdm: journal shows Unknown modifiers in command '+d' Classification: openSUSE Product: openSUSE.org Version: unspecified Hardware: Other OS: Other Status: NEW Severity: Enhancement Priority: P5 - None Component: 3rd party software Assignee: os.gnome.maintainers(a)gmail.com Reporter: sebix+novell.com(a)sebix.at QA Contact: bnc-team-screening(a)forge.provo.novell.com Found By: --- Blocker: --- The journal shows these three lines as errors on startup: Jun 04 20:00:42 giraffe systemd-tmpfiles[1013]: [/usr/lib/tmpfiles.d/gdm.conf:1] Unknown modifiers in command '+d' Jun 04 20:00:42 giraffe systemd-tmpfiles[1013]: [/usr/lib/tmpfiles.d/gdm.conf:2] Unknown modifiers in command '+d' Jun 04 20:00:42 giraffe systemd-tmpfiles[1013]: [/usr/lib/tmpfiles.d/gdm.conf:3] Unknown modifiers in command '+d' -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1135272] New: Error in /usr/lib/tmpfiles.d/gdm.conf
by bugzilla_noreply＠novell.com 05 Jun '19

05 Jun '19

http://bugzilla.opensuse.org/show_bug.cgi?id=1135272 Bug ID: 1135272 Summary: Error in /usr/lib/tmpfiles.d/gdm.conf Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Minor Priority: P5 - None Component: GNOME Assignee: bnc-team-gnome(a)forge.provo.novell.com Reporter: stuart.knock(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- While it is not obviously causing any problems, I recently (several zypper dup ago, I'm currently on 20190514) started getting the following errors in my logs during boot: > systemd-tmpfiles[962]: [/usr/lib/tmpfiles.d/gdm.conf:1] Unknown modifiers in command '+d' > systemd-tmpfiles[962]: [/usr/lib/tmpfiles.d/gdm.conf:2] Unknown modifiers in command '+d' > systemd-tmpfiles[962]: [/usr/lib/tmpfiles.d/gdm.conf:3] Unknown modifiers in command '+d' >From a quick look at /usr/lib/tmpfiles.d/gdm.conf and https://www.freedesktop.org/software/systemd/man/tmpfiles.d.html my guess is the prepended '+' is a typo and should be removed. -- You are receiving this mail because: You are on the CC list for the bug.

1 3