[Bug 1143125] New: systemd-vconsole-setup.service succeeds and fails several times on each boot
http://bugzilla.opensuse.org/show_bug.cgi?id=1143125 Bug ID: 1143125 Summary: systemd-vconsole-setup.service succeeds and fails several times on each boot Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: i586 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: bnc-team-screening@forge.provo.novell.com Reporter: forumino@riseup.net QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- Created attachment 811849 --> http://bugzilla.opensuse.org/attachment.cgi?id=811849&action=edit journalctl Booting a freshly installed Tumbleweed system with the following vconsole.conf results in sequential success and failure (seen in attached journalctl) # cat /etc/vconsole.conf KEYMAP=us FONT=eurlatgr.psfu FONT_MAP= FONT_UNIMAP= -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1143125
http://bugzilla.opensuse.org/show_bug.cgi?id=1143125#c18
Suse User
http://bugzilla.opensuse.org/show_bug.cgi?id=1143125
http://bugzilla.opensuse.org/show_bug.cgi?id=1143125#c19
--- Comment #19 from Martin Liška
http://bugzilla.opensuse.org/show_bug.cgi?id=1143125
Martin Liška
http://bugzilla.opensuse.org/show_bug.cgi?id=1143125
http://bugzilla.opensuse.org/show_bug.cgi?id=1143125#c20
Suse User
Hm, I can't reproduce that on my Tumbleweed on x86_64.
As per this ticket the report is for i586.
Can you please provide information about your system?
The issue was noticed on Acer TravelMate 2410. Attaching the requested output too. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1143125
http://bugzilla.opensuse.org/show_bug.cgi?id=1143125#c21
Martin Liška
Created attachment 816509 [details] requested info
Hm, I can't reproduce that on my Tumbleweed on x86_64.
As per this ticket the report is for i586.
Ah, ok, now I can reproduce that on i586 with: mprotect(0x435000, 53248, PROT_READ|PROT_WRITE|PROT_EXEC) = -1 EPERM (Operation not permitted) writev(2, [{iov_base="/usr/bin/gzip", iov_len=13}, {iov_base=": ", iov_len=2}, {iov_base="error while loading shared libra"..., iov_len=36}, {iov_base=": ", iov_len=2}, {iov_base="", iov_len=0}, {iov_base="", iov_len=0}, {iov_base="cannot make segment writable for"..., io v_len=43}, {iov_base=": ", iov_len=2}, {iov_base="Operation not permitted", iov_len=23}, {iov_base="\n", iov_len=1}], 10) = 122 It's unclear to me why the dynamic linker sets PROT_EXEC. @Andreas, @Micha: Can you help us here please? -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply@novell.com