January 2017 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1012957] New: Dolphin: fail to copy files within nested directories from hdd to usb-media (with fat 32)
by bugzilla_noreply＠novell.com 04 Jul '18

04 Jul '18

http://bugzilla.opensuse.org/show_bug.cgi?id=1012957 Bug ID: 1012957 Summary: Dolphin: fail to copy files within nested directories from hdd to usb-media (with fat 32) Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: KDE Applications Assignee: opensuse-kde-bugs(a)opensuse.org Reporter: stakanov(a)freenet.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- I can reproduce this. Insert a usb-key. Open dolphin. Only particularity, have the title with a mixed latin - chinese charakter (with me it is (HSK 上). To be exact: Main folder (with this mixed title) containing 3 folders with also mixed title. Let every of this folder have multiple mp3. Behaviour: First folder is created. Then apparently two subfolders are created but the third not. The two subfolders are created without content. This is repeatable. Then: you can create the third folder by hand, then you can copy every single mp3 file by hand. You also can copy the content into the beforehand created folders without content. However, every try to create in one glitch a copy of nested folders with content on a usb-key with fat32 fails. Once copied by hand, the usb-key the files are readable and the directory are correctly recognized on another PC with Leap 42.1. So, the usb-key and its file system seem to be O.K.. The created content seams O.K. I checked for permissions of the files, all O.K. But if trying to copy nested folders onto the usb with the latest tumbleweed that fails. -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 899627] New: p7zip package is missing 7zr executable
by bugzilla_noreply＠novell.com 03 Jul '18

03 Jul '18

http://bugzilla.opensuse.org/show_bug.cgi?id=899627 Bug ID: 899627 Summary: p7zip package is missing 7zr executable Classification: openSUSE Product: openSUSE 13.1 Version: Final Hardware: x86-64 OS: openSUSE 13.1 Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: me(a)shadsterling.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- /usr/bin/7zr, the "stand-alone" program that only handles the 7-zip format is missing from the p7zip package. /usr/bin/7z and /usr/bin/7za are included, as are man pages are for 7z, 7za, and 7zr. -- You are receiving this mail because: You are on the CC list for the bug.

1 10

[Bug 1004657] New: wrong udev-id displayed
by bugzilla_noreply＠novell.com 27 Jun '18

27 Jun '18

http://bugzilla.suse.com/show_bug.cgi?id=1004657 Bug ID: 1004657 Summary: wrong udev-id displayed Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 Assignee: yast2-maintainers(a)suse.de Reporter: aschnell(a)suse.com QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- YaST displays a wrong udev-id if a disk contains a lvm pv and then the lvm pv is deleted and a partition on the disk is created. I my case there is initially the udev id link: lvm-pv-uuid-iVJRSF-4fdA-hGcS-KTj9-JCh2-H2IO-J7O1Oq -> sdb That link vanishes in the system when the lvm pv is deleted. But YaST does not know that and shows a wrong link for the new partition sdb1: lvm-pv-uuid-iVJRSF-4fdA-hGcS-KTj9-JCh2-H2IO-J7O1Oq-part1 -- You are receiving this mail because: You are on the CC list for the bug.

1 8

[Bug 978593] New: EFI fails to load up the grub2 image erroring out on snapshot path
by bugzilla_noreply＠novell.com 26 Jun '18

26 Jun '18

http://bugzilla.suse.com/show_bug.cgi?id=978593 Bug ID: 978593 Summary: EFI fails to load up the grub2 image erroring out on snapshot path Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Bootloader Assignee: jsrain(a)suse.com Reporter: tchvatal(a)suse.com QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- After current clean Tumbleweed install efi fails to load up the grub2 menu. It tries to load it somewhere from snapshot and such file is not present. This computer has direct access to efi files and if I by hand select grub.efi file on the drive it loads up properly. (screenshot of the error will be attached). Fstab of the system: UUID=42ef9dda-9378-4c69-bbb9-540d8b8128db swap swap defaults 0 0 UUID=5a0b5b07-f0da-40f4-9993-1cf094d5c7b7 / btrfs defaults 0 0 UUID=5a0b5b07-f0da-40f4-9993-1cf094d5c7b7 /boot/grub2/i386-pc btrfs subvol=@/boot/grub2/i386-pc 0 0 UUID=5a0b5b07-f0da-40f4-9993-1cf094d5c7b7 /boot/grub2/x86_64-efi btrfs subvol=@/boot/grub2/x86_64-efi 0 0 UUID=5a0b5b07-f0da-40f4-9993-1cf094d5c7b7 /opt btrfs subvol=@/opt 0 0 UUID=5a0b5b07-f0da-40f4-9993-1cf094d5c7b7 /srv btrfs subvol=@/srv 0 0 UUID=5a0b5b07-f0da-40f4-9993-1cf094d5c7b7 /tmp btrfs subvol=@/tmp 0 0 UUID=5a0b5b07-f0da-40f4-9993-1cf094d5c7b7 /usr/local btrfs subvol=@/usr/local 0 0 UUID=5a0b5b07-f0da-40f4-9993-1cf094d5c7b7 /var/crash btrfs subvol=@/var/crash 0 0 UUID=5a0b5b07-f0da-40f4-9993-1cf094d5c7b7 /var/lib/libvirt/images btrfs subvol=@/var/lib/libvirt/images 0 0 UUID=5a0b5b07-f0da-40f4-9993-1cf094d5c7b7 /var/lib/mailman btrfs subvol=@/var/lib/mailman 0 0 UUID=5a0b5b07-f0da-40f4-9993-1cf094d5c7b7 /var/lib/mariadb btrfs subvol=@/var/lib/mariadb 0 0 UUID=5a0b5b07-f0da-40f4-9993-1cf094d5c7b7 /var/lib/mysql btrfs subvol=@/var/lib/mysql 0 0 UUID=5a0b5b07-f0da-40f4-9993-1cf094d5c7b7 /var/lib/named btrfs subvol=@/var/lib/named 0 0 UUID=5a0b5b07-f0da-40f4-9993-1cf094d5c7b7 /var/lib/pgsql btrfs subvol=@/var/lib/pgsql 0 0 UUID=5a0b5b07-f0da-40f4-9993-1cf094d5c7b7 /var/log btrfs subvol=@/var/log 0 0 UUID=5a0b5b07-f0da-40f4-9993-1cf094d5c7b7 /var/opt btrfs subvol=@/var/opt 0 0 UUID=5a0b5b07-f0da-40f4-9993-1cf094d5c7b7 /var/spool btrfs subvol=@/var/spool 0 0 UUID=5a0b5b07-f0da-40f4-9993-1cf094d5c7b7 /var/tmp btrfs subvol=@/var/tmp 0 0 UUID=5a0b5b07-f0da-40f4-9993-1cf094d5c7b7 /.snapshots btrfs subvol=(a)/.snapshots 0 0 UUID=5312-C90E /boot/efi vfat umask=0002,utf8=true 0 0 UUID=005d3151-b79e-435c-bcad-9d0304f53a9a /home xfs defaults 1 2 elitebook:~ # efibootmgr BootCurrent: 0000 Timeout: 0 seconds BootOrder: 0000,0001 Boot0000* Notebook Upgrade Bay Boot0001* Notebook Hard Drive Boot0002* Notebook Hard Drive Boot0003* USB Hard Drive 1 - Alcor Micro Mass Storage Device Boot0004* SD Card Boot0005* opensuse -- You are receiving this mail because: You are on the CC list for the bug.

1 26

[Bug 999100] New: grub2 menu
by bugzilla_noreply＠novell.com 26 Jun '18

26 Jun '18

http://bugzilla.opensuse.org/show_bug.cgi?id=999100 Bug ID: 999100 Summary: grub2 menu Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.2 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Bootloader Assignee: jsrain(a)suse.com Reporter: me(a)xto.de QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- Hi all, i just installed the 42.2-beta on my new Acer Travelmate B116. The grub-bootmenu is painted painfully slow (and really ugly (graphical). In first installation with original HDD i needed nomodeset to install 42.2-beta correctly (it broke with unreadable letters iprn text mode) so i tried with nomodeset which worked. Today i installed it again on a new and sealed ssd and I didnt need nomodeset-swith in installation-boot-menu (from USB-stick). I can provide more information as long as you tell me what to do :-) Greetings, Christian -- You are receiving this mail because: You are on the CC list for the bug.

1 10

[Bug 1021654] New: Sometimes clisp build fails on i586/x86_64 on testing sockets
by bugzilla_noreply＠novell.com 26 Jun '18

26 Jun '18

http://bugzilla.suse.com/show_bug.cgi?id=1021654 Bug ID: 1021654 Summary: Sometimes clisp build fails on i586/x86_64 on testing sockets Classification: openSUSE Product: openSUSE.org Version: unspecified Hardware: All OS: All Status: NEW Severity: Normal Priority: P5 - None Component: BuildService Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: werner(a)suse.com QA Contact: adrian(a)suse.com Found By: --- Blocker: --- This is how it should look like and how it does look most times: [ 594s] 33 path: 0 errors out of 176 tests [ 594s] 34 setf: 0 errors out of 197 tests [ 594s] 35 socket: 0 errors out of 92 tests [ 594s] 36 steele7: 0 errors out of 86 tests [ 594s] 37 streams: 0 errors out of 374 tests [ 594s] 38 streamslong: 0 errors out of 25 tests [ 594s] 39 strings: 0 errors out of 409 tests but sometimes the KVM build fails with [ 669s] 33 path: 0 errors out of 176 tests [ 669s] 34 setf: 0 errors out of 197 tests [ 669s] 35 socket: 1 error out of 92 tests [ 669s] 36 steele7: 0 errors out of 86 tests [ 669s] 37 streams: 0 errors out of 374 tests [ 669s] 38 streamslong: 0 errors out of 25 tests [ 669s] 39 strings: 0 errors out of 409 tests and this on both i586 and x86_64 ... compare with devel:languages:misc/clisp -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 964353] New: QT 5.5.based plasmashell and sddm-greeter can't cope with no monitor or monitor powered down
by bugzilla_noreply＠novell.com 22 Jun '18

22 Jun '18

http://bugzilla.opensuse.org/show_bug.cgi?id=964353 Bug ID: 964353 Summary: QT 5.5.based plasmashell and sddm-greeter can't cope with no monitor or monitor powered down Classification: openSUSE Product: openSUSE Distribution Version: 13.2 Hardware: x86-64 OS: openSUSE 42.1 Status: NEW Severity: Major Priority: P5 - None Component: KDE Workspace (Plasma) Assignee: opensuse-kde-bugs(a)opensuse.org Reporter: lorenzodes(a)fastwebnet.it QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Plasmashell crashes or displays malfunctions if a monitor is unplugged or powered off. The problem is reported here: https://forums.opensuse.org/showthread.php/512997-Plasma-5-KDE-Switching-mo… To reproduce: xrandr --output DP3 --off ; xrandr --output DP3 --auto (change DP3 to the pertinent display name) This is the crash report: (gdb) bt #0 0x00007f7d08147ded in nanosleep () at /lib64/libc.so.6 #1 0x00007f7d08147c84 in sleep () at /lib64/libc.so.6 #2 0x00007f7d0e89bbac in startProcessInternal(int, char const**, bool, bool) (argc=<optimized out>, argv=0x7ffe4b4744b0, waitAndExit=waitAndExit@entry=true, directly=directly@entry=false) at /usr/src/debug/kcrash-5.18.0/src/kcrash.cpp:650 #3 0x00007f7d0e89c22a in KCrash::startProcess(int, char const**, bool) (argc=argc@entry=21, argv=argv@entry=0x7ffe4b4744b0, waitAndExit=waitAndExit@entry=true) at /usr/src/debug/kcrash-5.18.0/src/kcrash.cpp:616 #4 0x00007f7d0e89c675 in KCrash::defaultCrashHandler(int) (sig=<optimized out>) at /usr/src/debug/kcrash-5.18.0/src/kcrash.cpp:527 #5 0x00007f7d080c6200 in <signal handler called> () at /lib64/libc.so.6 #6 0x00007f7d08fb8290 in QScreen::handle() const (this=0x0) at kernel/qscreen.cpp:112 #7 0x00007f7cfa7f4be9 in QXcbIntegration::createPlatformWindow(QWindow*) const (this=<optimized out>, window=0x2ae79d0) at qxcbintegration.cpp:196 #8 0x00007f7d08f98e25 in QWindowPrivate::create(bool) (this=0x1175d80, recursive=recursive@entry=false) at kernel/qwindow.cpp:392 #9 0x00007f7d08f9901b in QWindow::create() (this=this@entry=0x2ae79d0) at kernel/qwindow.cpp:548 #10 0x00007f7d08f990a8 in QWindow::winId() const (this=0x2ae79d0) at kernel/qwindow.cpp:567 #11 0x00007f7d0e667175 in () at /usr/lib64/libKF5PlasmaQuick.so.5 #12 0x00007f7d0e6699f9 in () at /usr/lib64/libKF5PlasmaQuick.so.5 #13 0x00007f7d08a70cc6 in QMetaObject::activate(QObject*, int, int, void**) (sender=0x297d830, signalOffset=<optimized out>, local_signal_index=<optimized out>, argv=0x0) at kernel/qobject.cpp:3713 #14 0x00007f7d08a7073f in QMetaObject::activate(QObject*, int, int, void**) (a=0x7ffe4b474f90, r=0x297d830, this=0x29a86f0) at ../../src/corelib/kernel/qobject_impl.h:124 #15 0x00007f7d08a7073f in QMetaObject::activate(QObject*, int, int, void**) (sender=0xdf8370, signalOffset=<optimized out>, local_signal_index=<optimized out>, argv=0x0) at kernel/qobject.cpp:3698 #16 0x00007f7d08a70cc6 in QMetaObject::activate(QObject*, int, int, void**) (sender=sender@entry=0xdf41e0, signalOffset=<optimized out>, local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x0) at kernel/qobject.cpp:3713 #17 0x00007f7d08a712e7 in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) (sender=sender@entry=0xdf41e0, m=m@entry=0x7f7d08e8f860 <QTimer::staticMetaObject>, local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x0) at kernel/qobject.cpp:3578 #18 0x00007f7d08af2a90 in QTimer::timeout(QTimer::QPrivateSignal) (this=this@entry=0xdf41e0) at .moc/moc_qtimer.cpp:197 #19 0x00007f7d08a7df22 in QTimer::timerEvent(QTimerEvent*) (this=0xdf41e0, e=<optimized out>) at kernel/qtimer.cpp:247 #20 0x00007f7d08a718bc in QObject::event(QEvent*) (this=0xdf41e0, e=<optimized out>) at kernel/qobject.cpp:1220 #21 0x00007f7d09db9e7c in QApplicationPrivate::notify_helper(QObject*, QEvent*) (this=this@entry=0xc666a0, receiver=receiver@entry=0xdf41e0, e=e@entry= 0x7ffe4b4754f0) at kernel/qapplication.cpp:3716 #22 0x00007f7d09dbecc8 in QApplication::notify(QObject*, QEvent*) (this=0x7ffe4b4758a0, receiver=0xdf41e0, e=0x7ffe4b4754f0) at kernel/qapplication.cpp:3499 #23 0x00007f7d08a40e95 in QCoreApplication::notifyInternal(QObject*, QEvent*) (this=0x7ffe4b4758a0, receiver=0xdf41e0, event=event@entry=0x7ffe4b4754f0) at kernel/qcoreapplication.cpp:965 #24 0x00007f7d08a9777d in QTimerInfoList::activateTimers() (event=0x7ffe4b4754f0, receiver=<optimized out>) at ../../src/corelib/kernel/qcoreapplication.h:224 #25 0x00007f7d08a9777d in QTimerInfoList::activateTimers() (this=0xcadc50) at kernel/qtimerinfo_unix.cpp:637 #26 0x00007f7d08a97aa1 in timerSourceDispatch(GSource*, GSourceFunc, gpointer) (source=<optimized out>) at kernel/qeventdispatcher_glib.cpp:177 #27 0x00007f7d0484ec84 in g_main_context_dispatch () at /usr/lib64/libglib-2.0.so.0 #28 0x00007f7d0484eed8 in () at /usr/lib64/libglib-2.0.so.0 #29 0x00007f7d0484ef7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #30 0x00007f7d08a97d8b in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) (this=0xca3db0, flags=...) at kernel/qeventdispatcher_glib.cpp:420 #31 0x00007f7d08a3ed53 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) (this=this@entry=0x7ffe4b475730, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #32 0x00007f7d08a468f6 in QCoreApplication::exec() () at kernel/qcoreapplication.cpp:1229 #33 0x00007f7d08f8a79c in QGuiApplication::exec() () at kernel/qguiapplication.cpp:1527 #34 0x00007f7d09db6605 in QApplication::exec() () at kernel/qapplication.cpp:2976 #35 0x0000000000436ab6 in main(int, char**) (argc=2, argv=<optimized out>) at /usr/src/debug/plasma-workspace-5.5.4/shell/main.cpp:181 sddm-greeter exits if the monitor is not switched on when the gretter is shown. The problem is reported here: https://forums.opensuse.org/showthread.php/513153-ssdm-greeter-exits-or-han… System logs: 2016-01-28T23:11:19.980147+01:00 kenshiro sddm[1091]: Running display setup script "/etc/X11/xdm/Xsetup" 2016-01-28T23:11:19.993288+01:00 kenshiro sddm[1091]: Display server started. 2016-01-28T23:11:19.993497+01:00 kenshiro sddm[1091]: Socket server starting... 2016-01-28T23:11:19.993639+01:00 kenshiro sddm[1091]: Socket server started. 2016-01-28T23:11:19.993885+01:00 kenshiro sddm[1091]: Greeter starting... 2016-01-28T23:11:19.994039+01:00 kenshiro sddm[1091]: Adding cookie to "/run/sddm/{5ab51fe3-b0e9-41b7-b2ed-294821cc0322}" 2016-01-28T23:11:19.998523+01:00 kenshiro sddm-helper[1653]: [PAM] Starting... 2016-01-28T23:11:19.998753+01:00 kenshiro sddm-helper[1653]: [PAM] Authenticating... 2016-01-28T23:11:19.998916+01:00 kenshiro sddm-helper[1653]: [PAM] returning. 2016-01-28T23:11:19.999052+01:00 kenshiro sddm-helper: pam_unix(sddm-greeter:session): session opened for user sddm by (uid=0) 2016-01-28T23:11:20.014407+01:00 kenshiro sddm[1091]: Greeter session started successfully 2016-01-28T23:11:20.027505+01:00 kenshiro sddm-greeter[1655]: Reading from "/usr/share/xsessions/enlightenment.desktop" 2016-01-28T23:11:20.027786+01:00 kenshiro sddm-greeter[1655]: Reading from "/usr/share/xsessions/gnome.desktop" 2016-01-28T23:11:20.027936+01:00 kenshiro sddm-greeter[1655]: Reading from "/usr/share/xsessions/icewm.desktop" 2016-01-28T23:11:20.028071+01:00 kenshiro sddm-greeter[1655]: Reading from "/usr/share/xsessions/kde-plasma.desktop" 2016-01-28T23:11:20.028204+01:00 kenshiro sddm-greeter[1655]: Reading from "/usr/share/xsessions/plasma5.desktop" 2016-01-28T23:11:20.028340+01:00 kenshiro sddm-greeter[1655]: Connected to the daemon. 2016-01-28T23:11:20.028474+01:00 kenshiro sddm[1091]: Message received from greeter: Connect 2016-01-28T23:11:20.062294+01:00 kenshiro sddm-greeter[1655]: QObject::installEventFilter(): Cannot filter events for objects in a different thread. 2016-01-28T23:11:20.250847+01:00 kenshiro sddm-greeter[1655]: QObject::installEventFilter(): Cannot filter events for objects in a different thread. 2016-01-28T23:11:20.404977+01:00 kenshiro sddm-greeter[1655]: file:///usr/share/sddm/themes/breeze/components/InfoPane.qml:52:22: Unable to assign [undefined] to int 2016-01-28T23:11:20.405245+01:00 kenshiro sddm-greeter[1655]: Adding view for "HDMI2" QRect(0,0 1920x1080) 2016-01-28T23:11:20.408967+01:00 kenshiro sddm-greeter[1655]: Message received from daemon: Capabilities 2016-01-28T23:11:20.409139+01:00 kenshiro sddm-greeter[1655]: Message received from daemon: HostName 2016-01-28T23:15:03.058840+01:00 kenshiro sddm-helper[1653]: [PAM] Ended. 2016-01-28T23:15:03.059337+01:00 kenshiro sddm[1091]: Auth: sddm-helper exited successfully 2016-01-28T23:15:03.059517+01:00 kenshiro sddm[1091]: Greeter stopped. Apparently both are related to this upstream bug: https://bugreports.qt.io/browse/QTBUG-42985 Leap 42.1 KDE is basically unusable in this state and, as far as I can tell, upstream provided a bugfix but decided not to implement it in QT 5.5. Would it be possible to upgrade QT in Leap to 5.6? -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 892893] New: Unable to Configure NFS Server a Reboot is Required
by bugzilla_noreply＠novell.com 19 Jun '18

19 Jun '18

https://bugzilla.novell.com/show_bug.cgi?id=892893 https://bugzilla.novell.com/show_bug.cgi?id=892893#c0 Summary: Unable to Configure NFS Server a Reboot is Required Classification: openSUSE Product: openSUSE 13.1 Version: Final Platform: x86-64 OS/Version: openSUSE 13.1 Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 AssignedTo: yast2-maintainers(a)suse.de ReportedBy: secure(a)aphofis.com QAContact: jsrain(a)suse.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Firefox/31.0 Enter Yast>Network Services>NFS Server> Start Services, Open Firewall, Disable NFSv4, Export 2 Directories>Finish ERROR Unable to stop idmapd. Reproducible: Always Steps to Reproduce: 1.Enter Yast>Network Services>NFS Server> Start Services, Open Firewall, Disable NFSv4, Export 2 Directories>Finish ERROR Unable to stop idmapd. 2. 3. Actual Results: ERROR Unable to stop idmapd. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 5

[Bug 869116] New: Apper No Longer Requires escalation to root auth to make changes to installing O/S changes
by bugzilla_noreply＠novell.com 19 Jun '18

19 Jun '18

https://bugzilla.novell.com/show_bug.cgi?id=869116 https://bugzilla.novell.com/show_bug.cgi?id=869116#c0 Summary: Apper No Longer Requires escalation to root auth to make changes to installing O/S changes Classification: openSUSE Product: openSUSE 12.3 Version: Final Platform: x86-64 OS/Version: openSUSE 12.3 Status: NEW Severity: Major Priority: P5 - None Component: Security AssignedTo: security-team(a)suse.de ReportedBy: secure(a)aphofis.com QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:27.0) Gecko/20100101 Firefox/27.0 Apper in its now current for will not call for escalation to root authority to modify and install changes to O/S. If we wanted to copy MS convention where updates and changes to the O/S....we would use it. This is one of the stand-out security features thats sets our O/S above the rest and to enable these changes without root authority sets a dangerous precedent Reproducible: Always Steps to Reproduce: 1. Every time apper wants to make changes to the O/S 100% reproducable 2. 3. Actual Results: No escalation to root authority is called by apper Expected Results: Changes to O/S should be the privilege of root and no user authority and escalation to root should be called for before we let any application change the O/S With so much log data files I don’t really no what to supply to support this...Please provide details of what audit log files you require to solve. Priority set as this is a direct threat to O/S security and its now broken as previously root auth was always required. Please do not close as DOWNSTREAM OR UPSTREAM..Apper is an integral and non optional inclusion to the packing list of 12.3 and as such the product opensuse is the arbiter and coordinator of Apper -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 1

[Bug 848914] New: Publish Information around Partitioning Requirements of Boot Requirements with UEFI BIOS
by bugzilla_noreply＠novell.com 19 Jun '18

19 Jun '18

https://bugzilla.novell.com/show_bug.cgi?id=848914 https://bugzilla.novell.com/show_bug.cgi?id=848914#c0 Summary: Publish Information around Partitioning Requirements of Boot Requirements with UEFI BIOS Classification: openSUSE Product: openSUSE 12.3 Version: Final Platform: x86-64 OS/Version: openSUSE 12.3 Status: NEW Severity: Enhancement Priority: P5 - None Component: Installation AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: secure(a)aphofis.com QAContact: jsrain(a)suse.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0 If ever we are going to see changed in PC BIOS's it will be in this decade. Current UEFI BIOS's are standard with most all X_64 Motherboards. The UEFI BIOS is a temporary measure to permit backwardly compatible Processors and Motherboards and my enhancement would be to publish partitioning information on screen thats not an option before the partitioning phase of Installation. Current warnings generated by the Partitioner itself do warn of requirements for /boot/uefi with FAT. As there will be many changes to BIOS this decade I think we need a mandatory full screen explanation of partitioning changes that can be written for all coming versions as it will be needed and under that preface every installation from 13.x to anything can all make use of a text screen before the partitioner is displayed on screen as part of every Installation Reproducible: Always Steps to Reproduce: 1. Try to configure a boot partition with an X_64 UEFI BIOS and a warning is generated on the users final acceptance of the chosen partitioning. 2. The warning is too late and there is not sufficient space to provide detailed instructions and the reasoning and its going to get more problematic. Additionally as soon as M.S come out with a new file formation partitioning we will need to spell partitioning out in a clear concise way before the user does anything with the partitioner 3. Expected Results: Its a small and advantages addition to the Install Program to have a text screen available before the partitioning part of our current installation is reached. Currently we only knock back the partitioning with a warning after the partitioner has been used. It needs full explanation before not a single line after. It should be very easy to implement this text screen as the need far outweighs the man hour time factor it would take to implement above. I believe this should be assigned and completed as an urgent undertaking before we ship another version as its benefit now and future is so very important. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 2