October 2016 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1000287] [patch] AppArmor change_hat failures
by bugzilla_noreply＠novell.com 07 Oct '16

07 Oct '16

http://bugzilla.suse.com/show_bug.cgi?id=1000287 http://bugzilla.suse.com/show_bug.cgi?id=1000287#c10 --- Comment #10 from Michal Kubeček <mkubecek(a)suse.com> --- For the record, evergreen-13.1 is merging SLE12-SP1 branch so that it's going to get the fix as well. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1003472] New: Release in Installer "Slide Show" reads "Leap Leap 42.2"
by bugzilla_noreply＠novell.com 06 Oct '16

06 Oct '16

http://bugzilla.opensuse.org/show_bug.cgi?id=1003472 Bug ID: 1003472 Summary: Release in Installer "Slide Show" reads "Leap Leap 42.2" Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.2 Hardware: All OS: SUSE Other Status: NEW Severity: Minor Priority: P5 - None Component: Installation Assignee: yast2-maintainers(a)suse.de Reporter: bpesavento(a)infinito.it QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- Many (not all) instances of release identification in the Installer "Slide Show" read "Leap Leap 42.2" as originally pointed out by https://lists.opensuse.org/opensuse-factory/2016-09/msg00538.html Still present in 42.2 Beta3 (Build0215) DVD-x86_64 iso image. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 977729] [LANG=RU, yast2] localization bug in ru-locale in yast2 prompt window
by bugzilla_noreply＠novell.com 06 Oct '16

06 Oct '16

http://bugzilla.novell.com/show_bug.cgi?id=977729 http://bugzilla.novell.com/show_bug.cgi?id=977729#c13 --- Comment #13 from Mikhail Kasimov <mikhail.kasimov(a)gmail.com> --- (In reply to Shane Wims from comment #10) > openSUSE 13.2 used the following translation for "&Abandon". Is it OK to use > in SLE? (Weblate search function is not very good so I did not look there). > > https://svn.opensuse.org/svn/opensuse-i18n/branches/openSUSE-13_2-Branch/ > yast/ru/po/qt-pkg.ru.po?view=markup&revision=90881 > > #: src/YQPackageSelectorBase.cc:249 > msgid "&Abandon" > msgstr "Отк&азаться" Yes, this translation is correct. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 982141] ceph is in unresolvable state for ppc64le
by bugzilla_noreply＠novell.com 06 Oct '16

06 Oct '16

http://bugzilla.suse.com/show_bug.cgi?id=982141 Swamp Workflow Management <swamp(a)suse.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Whiteboard| |ibs:running:3311:moderate -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1003410] New: Leap 42.2 Beta 3 - installation language German - installation text is English
by bugzilla_noreply＠novell.com 06 Oct '16

06 Oct '16

http://bugzilla.opensuse.org/show_bug.cgi?id=1003410 Bug ID: 1003410 Summary: Leap 42.2 Beta 3 - installation language German - installation text is English Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.2 Hardware: x86-64 OS: SUSE Other Status: NEW Severity: Major Priority: P5 - None Component: Installation Assignee: yast2-maintainers(a)suse.de Reporter: bugrprt21882(a)online.de QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- Leap 42.2 Beta 3 Network Installation: Despite choosing "F2" installation language "Deutsch" at the first installation screen (Network Installation ISO image on a CD-RW), the following installation screens are all in English -- for example: "Language, Keyboard and License Agreement". - At that screen the Language is "German - Deutsch" and the Keyboard Layout is "German". The Keyboard Test functions correctly. - The License Agreement is in English with no possibility to view the German translation. At the following installation screens occasionally German language progress strings appear. At the "Suggested Partitioning" screen, the Partition information is in German. At the "Clock and Time Zone" screen, the location is Europe/Germany. At the "List of Online Repositories" screen the "Summary:" and "Description:" text strings are in German. the following screen where the repositories are added is also partially in German. ---------------------------------------------------- Once the (mostly English language) installation completes, a German language system boots. -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 922405] 1 minute delay until USB thumb drive is usable
by bugzilla_noreply＠novell.com 06 Oct '16

06 Oct '16

http://bugzilla.suse.com/show_bug.cgi?id=922405 http://bugzilla.suse.com/show_bug.cgi?id=922405#c22 --- Comment #22 from Alan Ott <alan(a)softiron.co.uk> --- (In reply to Hannes Reinecke from comment #21) > Which is precisely what we do nowadays; with the most recent sg3_utils we're > just looking at the respective sysfs attributes, and will not query the > device itself. The most recent 55-scsi-sg3_id.rules has eg: > > # SCSI EVPD page 0x80 values > KERNEL=="sd*[!0-9]|sr*", ENV{ID_SCSI}=="1", ENV{ID_SCSI_SN}=="1", > IMPORT{program}="/usr/bin/sg_inq --export > --inhex=/sys/block/$kernel/device/vpd_pg80 --raw" > KERNEL=="sd*[!0-9]|sr*", ENV{ID_SCSI}=="1", ENV{ID_SCSI_SN}!="1", > IMPORT{program}="/usr/bin/sg_inq --export --page=sn $tempnode" Sorry, I read it wrong. You are right. So right now, the new version does: 1. If /sys/block/$kernel/device/inquiry exists, then assume: /sys/block/$kernel/device/vpd_pg80 and /sys/block/$kernel/device/vpd_pg83 both exist (or can't exist) and use them.... 2. But if /sys/block/$kernel/device/inquiry doesn't exist, then call sg_inq to try to get the data from the device directly. what's the point of #2? What is the use case where this matters? When will a device _not_ have an inquiry sysfs node? If a device doesn't have an inquiry node (meaning the INQUIRY requests to the device by the kernel have all failed), do we really think sending VPD inquiries from user space is guaranteed to not make things worse? The reason I'm asking #2 is because I'm skeptical that there is _any_ reason to be issuing scsi commands from user space (other than testing and debugging). The kernel goes to great lengths to get the proper information from the device, working around many types of buggy devices. The data is either there and can be read from sysfs, or the kernel is unable to get the data, in which case user space shouldn't try it, because you might either get bad data or lock up the device. In my opinion, I'd remove all sg_inq calls in this sysfs file. Either the kernel has read the data or the kernel can't read the data. User space should trust the kernel to interact with scsi devices. > > ie we're trying to read from /sys/block/sdX/device/vpg_pg89 (if existing) > or, if this doesn't exist, use the sg_inq program to read from device. > You're reading from /sys/.../vpg_pg83 if sys/.../inquiry exists. why not just read from sysfs and call it done? I reiterate that calling scsi commands from user space when the kernel has already decided that these commands aren't going to work doesn't make sense. > We might need to update the sg3_utils package in Leap, though. Please do. That would seem to fix the immediate problem. Alan. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1002699] xfs_fsr segfault
by bugzilla_noreply＠novell.com 06 Oct '16

06 Oct '16

http://bugzilla.suse.com/show_bug.cgi?id=1002699 Jeff Mahoney <jeffm(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jeffm(a)suse.com Assignee|jeffm(a)suse.com |lurodriguez(a)suse.com -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1000907] Cannot get directory listing of Windows share. Error "Object is remote" using 4.1.31-30-default kernel
by bugzilla_noreply＠novell.com 06 Oct '16

06 Oct '16

http://bugzilla.suse.com/show_bug.cgi?id=1000907 http://bugzilla.suse.com/show_bug.cgi?id=1000907#c5 --- Comment #5 from Richard Hamilton <richard.hamilton(a)microfocus.com> --- Attached is the Wireshark capture. The output from the terminal was: hts44prod2:/home/rhamilton/Documents/smb # mount -t cifs //us.netiq.corp/files/HOU/TechSupport /mnt/corpdom -o username=rhamilton,domain=corpdom,iocharset=utf8,file_mode=0777,dir_mode=0777 Password for rhamilton(a)//us.netiq.corp/files/HOU/TechSupport: ************** hts44prod2:/home/rhamilton/Documents/smb # ls /mnt/ corpdom/ gw/ hts44prod2:/home/rhamilton/Documents/smb # ls /mnt/corpdom/ ls: reading directory /mnt/corpdom/: Object is remote -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1000498] New: i586 installer broken
by bugzilla_noreply＠novell.com 06 Oct '16

06 Oct '16

http://bugzilla.suse.com/show_bug.cgi?id=1000498 Bug ID: 1000498 Summary: i586 installer broken 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: msuchanek(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- I tried to install on an i586 class notebook - in the main menu (outside of installer) there is an option to run shell. It returns immediately. - there is a help text on terminal 9 saying shells are running on terminals 2 5 6 and 9. They are not - there is an e100 NIC in the notebook. The linuxrc claims it loaded e100 and eepro100 drivers during boot. It claims there is no network card when trying to configure network in the main menu. It claims there are no modules loaded in the same menu. -- You are receiving this mail because: You are on the CC list for the bug.

1 7

[Bug 955101] YaST2 doesn't start under Gnome / Wayland
by bugzilla_noreply＠novell.com 06 Oct '16

06 Oct '16

http://bugzilla.suse.com/show_bug.cgi?id=955101 http://bugzilla.suse.com/show_bug.cgi?id=955101#c14 --- Comment #14 from Stefan Hundhammer <shundhammer(a)suse.com> --- (In reply to Calin Calin from comment #13) > Can you please link to the feature request? Unfortunately, the feature tracking tool is not accessible from the outside. We are aware that this is a limitation with negative impact for the community. Sorry for that. I know there are discussions going on how to improve that, but I don't know how far this has progressed. -- You are receiving this mail because: You are on the CC list for the bug.

1 0