August 2015 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 940779] fcitx cannot normally work
by bugzilla_noreply＠novell.com 06 Aug '15

06 Aug '15

http://bugzilla.suse.com/show_bug.cgi?id=940779 Stephan Kulow <coolo(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|cfarrell(a)suse.com |i(a)marguerite.su -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 922529] fails to find eMMC during initial install
by bugzilla_noreply＠novell.com 06 Aug '15

06 Aug '15

http://bugzilla.suse.com/show_bug.cgi?id=922529 http://bugzilla.suse.com/show_bug.cgi?id=922529#c69 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(trenn(a)suse.com) |needinfo?(gerrysw11(a)gmail.c | |om) --- Comment #69 from Takashi Iwai <tiwai(a)suse.com> --- (In reply to Oliver Neukum from comment #54) > The drive first errors out when you access an rpmb partition. It looks like > we are running blkid on this partition. We must not do that. RPMB partitions > cannot have a filesystem. The best option is to ignore it. > Now it would be best if the driver were able to recover, but failing that, > don't crash it. > > [ 28.005490] mmc1: Got data interrupt 0x00000002 even though no data > operation was in progress. > [ 28.021864] mmcblk0rpmb: error -110 transferring data, sector 8064, nr 8, > cmd response 0x900, card status 0xb00 > [ 28.029502] mmcblk0rpmb: retrying using single block read > [ 28.031787] mmcblk0rpmb: timed out sending r/w cmd command, card status > 0x400900 > [ 28.041820] mmcblk0rpmb: timed out sending r/w cmd command, card status > 0x400900 > [ 28.051618] mmcblk0rpmb: timed out sending r/w cmd command, card status > 0x400900 > [ 28.061314] mmcblk0rpmb: timed out sending r/w cmd command, card status > 0x400900 > [ 28.070912] mmcblk0rpmb: timed out sending r/w cmd command, card status > 0x400900 > [ 28.080383] mmcblk0rpmb: timed out sending r/w cmd command, card status > 0x400900 > [ 28.087579] end_request: I/O error, dev mmcblk0rpmb, sector 8064 FYI, there is a recent upstream fix (in 4.1) regarding RPMB partition: 4e93b9a6abc0d028daf3c8a00cb77b679d8a4df4 mmc: card: Don't access RPMB partitions for normal read/write So, it's anyway good to test the latest Tumbleweed indeed. The relevant dracut fix has been already merged in TW. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 940657] Patch openSUSE-2015-535 broke secure boot (UEFI systems)
by bugzilla_noreply＠novell.com 06 Aug '15

06 Aug '15

http://bugzilla.suse.com/show_bug.cgi?id=940657 http://bugzilla.suse.com/show_bug.cgi?id=940657#c5 Michael Schröder <mls(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(mls(a)suse.com) | --- Comment #5 from Michael Schröder <mls(a)suse.com> --- Oh well. Configuration error. The automatic pubkey extension overwrote the old openSUSE Cert with the maintenance cert. Please rebuild the maintenance update to fix the cert. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 940290] SLE12 Valgrind fails to build for kernel 4.1
by bugzilla_noreply＠novell.com 06 Aug '15

06 Aug '15

http://bugzilla.suse.com/show_bug.cgi?id=940290 http://bugzilla.suse.com/show_bug.cgi?id=940290#c1 Dirk Mueller <dmueller(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|dmueller(a)suse.com |coolo(a)suse.com --- Comment #1 from Dirk Mueller <dmueller(a)suse.com> --- submitted the factory package. can you somehow make sure to not inherit SLE code for valgrind? its a leaf package so it should be updated from the openSUSE Tumbleweed side of things, inheriting it from SLE makes no sense at all. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 940657] Patch openSUSE-2015-535 broke secure boot (UEFI systems)
by bugzilla_noreply＠novell.com 06 Aug '15

06 Aug '15

http://bugzilla.suse.com/show_bug.cgi?id=940657 http://bugzilla.suse.com/show_bug.cgi?id=940657#c4 --- Comment #4 from Marcus Meissner <meissner(a)suse.com> --- openSUSE:Maintenance:3929 -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 742756] no application menu on left monitor (dual monitor)
by bugzilla_noreply＠novell.com 06 Aug '15

06 Aug '15

http://bugzilla.suse.com/show_bug.cgi?id=742756 http://bugzilla.suse.com/show_bug.cgi?id=742756#c9 Martin Pluskal <mpluskal(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mpluskal(a)suse.com --- Comment #9 from Martin Pluskal <mpluskal(a)suse.com> --- Well for the record, chris(a)computersalat.de hasn't confirmed that issue is still occuring, (In reply to Christian Wittmer from comment #6) > Will you then wait for an answer until 13.2 is running out of updates ? > Is this the way BUGs are handled ? Waiting until dist is running out of > updates ? Chris, you haven't confirmed that issue is still occurring, I am sorry that you had this experience but please bear in mind that maintainers have also other stuff to deal with, and sadly this was probably very low on their list. So is issue still present in openSUSE which you are currently using? -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 742756] no application menu on left monitor (dual monitor)
by bugzilla_noreply＠novell.com 06 Aug '15

06 Aug '15

http://bugzilla.suse.com/show_bug.cgi?id=742756 http://bugzilla.suse.com/show_bug.cgi?id=742756#c8 Chenzi Cao <chcao(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|bnc-team-screening(a)forge.pr |nadvornik(a)suse.com |ovo.novell.com | Flags|needinfo?(chcao(a)suse.com) | --- Comment #8 from Chenzi Cao <chcao(a)suse.com> --- Hi Christian, it is unfortunate that the bug is still there, but would you please help to have a try on a newer version since openSUSE 11.4 is no longer supported? If the bug is still existing, please create a new bug to the latest version. But please feel free to stick to this version if any particular concern, thanks. Hi Vladimir, would you please help here? Thank you! -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 940779] fcitx cannot normally work
by bugzilla_noreply＠novell.com 06 Aug '15

06 Aug '15

http://bugzilla.suse.com/show_bug.cgi?id=940779 Chenzi Cao <chcao(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |chcao(a)suse.com Assignee|bnc-team-screening(a)forge.pr |cfarrell(a)suse.com |ovo.novell.com | -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 926031] New: No console output on Beagleboard XM
by bugzilla_noreply＠novell.com 06 Aug '15

06 Aug '15

http://bugzilla.opensuse.org/show_bug.cgi?id=926031 Bug ID: 926031 Summary: No console output on Beagleboard XM Classification: openSUSE Product: openSUSE Distribution Version: 13.2 Hardware: armv7 OS: openSUSE 13.2 Status: NEW Severity: Major Priority: P5 - None Component: Kernel Assignee: kernel-maintainers(a)forge.provo.novell.com Reporter: wk(a)ire.pw.edu.pl QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 630062 --> http://bugzilla.opensuse.org/attachment.cgi?id=630062&action=edit Serial console output of openSUSE-13.2-ARM-E17-beagle.armv7l-1.12.1-Build33.6 While attempting to install E17 or XFCE versions of openSUSE 13.2 on Beagleboard XM rev. B, nothing is shown on the console. The last line of serial port output is the message "Starting kernel ...". Monitor screen goes plain yellow wkhile running u-boot but turns black just after loading kernel. "No signal" message appears on screen after a while. The console output is in attachment. Flash card images were from: http://download.opensuse.org/ports/armv7hl/distribution/13.2/appliances/ and found for all tested beagle images imcluding: openSUSE-13.2-ARM-E17-beagle.armv7l-1.12.1-Build33.6.raw.xz and: openSUSE-13.2-ARM-XFCE-beagle.armv7l-1.12.1-Build33.6.raw.xz The problem makes image useless, since it cannot be configured with Firstboot. The JeOS images also do not display anything on screen, but can be accessed through serial console. -- You are receiving this mail because: You are on the CC list for the bug.

1 5

[Bug 906797] New: logout on bugzilla.opensuse.org doesn't works
by bugzilla_noreply＠novell.com 06 Aug '15

06 Aug '15

http://bugzilla.opensuse.org/show_bug.cgi?id=906797 Bug ID: 906797 Summary: logout on bugzilla.opensuse.org doesn't works Classification: openSUSE Product: openSUSE.org Version: unspecified Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Bugzilla Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: colAflash(a)gmx.net QA Contact: novbugzilla-bugs(a)forge.provo.novell.com Found By: --- Blocker: --- Logout on https://bugzilla.opensuse.org doesn't works. When clicking on logout, I'm being redirected to https://www.suse.com/common/util/logout.php The page asks me to login again "Please sign in". But when going back to https://bugzilla.opensuse.org/index.cgi I'm still logged in and I can still do stuff like posting bug-reports. Tested on openSUSE 13.2 with Firefox 33 and Chromium 38. To force logout (which probably doesn't deletes the session information on the server), I've got to delete all cookies of these domains in my browser. Probably I don't really have to delete all of those, but at least some... novell.com bugzilla.novell.com opensuse.org bugzilla.opensuse.org attachmategroup.com esp.attachmategroup.com login.attachmategroup.com -- You are receiving this mail because: You are on the CC list for the bug.

1 6