November 2016 - openSUSE Users - openSUSE Mailing Lists

[opensuse] leap42x - automatically activating network printers during/after installation?
by Per Jessen 15 Nov '16

15 Nov '16

After a new installation, instead of manually having to run yast, configure printers, enable "listen for network broadcast", is there any way of having this done automagically? tnx Per -- Posted with knode 4.14 from openSUSE Leap42.1 office34: Cyrix 486DX2/66MHz, 4096Mb RAM, #9 GXE -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

1 0

[opensuse] Grub error when booting secondary openSUSE linux system.
by Carlos E. R. 15 Nov '16

15 Nov '16

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Hi, In my laptop I have Win 10, OS 13.1, and 42.2 RC2; the later just installed and doesn't boot. In 13.1 I have grub 1, with this entry that has worked for years: title openSUSE Factory (/dev/sda9) via chainloader rootnoverify (hd0,8) chainloader +1 but now produces this error: Error 13: Invalid or unsupported executable format press any key to continue The documentation says: 13 : Invalid or unsupported executable format This error is returned if the kernel image being loaded is not recognized as Multiboot or one of the supported native formats (Linux zImage or bzImage, FreeBSD, or NetBSD). which I fail to understand. There should not be a kernel there, but grub2. Attached is the information from bootinfoscript. In partition sda9 is installed Leap 42.2 RC2, and grub "should" be installed just there, but I am not sure it was. The RC2 installer has changed and I'm unsure what it did. I'll describe it. Leap 42.2 RC2 boot settings (installation settings window) (/dev/sda9) (photos available) +++---------------- Booting The installer will not modify the MBR of the disk. Unless it already contains boot code, the BIOS won't be able to boot from this disk. * Bot loader type: grub2 * Enable trusted boot: no * Change location: * Do not install bootcode into MBR (install) * Warning: No location for bootloader stage 1 selected. Unless you know what you are doing please select another location * Order of hard disks: /dev/sda, /dev/sdb - ----------------++- This is wrong, so I click on "Booting" and modify it. +++---------------- Boot code options (photo available on request) Boot loader Location [ ] Boot from master boot record [X] Custom boot partition [/dev/sda9 ] [ ] Set active flag in partition table for boot partition [ ] Write generic boot code to MBR [ ] Enable trusted boot support - ----------------++- Notice that changing the tab clears the modification in this tab. I have to select "Accept", which renders: +++---------------- Booting The installer will not modify the MBR of the disk. Unless it already contains boot code, the BIOS won't be able to boot from this disk. * Bot loader type: grub2 * Enable trusted boot: no * Status location: /dev/sda9 ("/") * Change location: * Do not install bootcode into MBR (install) * Order of hard disks: /dev/sda, /dev/sdb - ----------------++- On previous years, there was a list of choices to boot from, like "boot from root partition", which is what I wanted to do. I can not permit the installer to modify the MBR, which is customized. Touch it and booting breaks. Now there is a line where to type the "custom boot partition". It is possible that YaST did not write the grub images at all anywhere. So I'm not totally sure of what happened. If the problem is in grub1 in the main system (13.1) or in the new 42.2 grub 2. - -- Cheers Carlos E. R. (from 13.1 x86_64 "Bottle" (Minas Tirith)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iF4EAREIAAYFAlgnxsIACgkQja8UbcUWM1xXggD/ZRWPgYKEdW2H5sI/39j0Qn/Q EHb/YonqT53lEuhAnzoA/14bToOg4IfgPvIZCGnfpIebK8wH1Qk9Ox2bXyY83Pgn =hom6 -----END PGP SIGNATURE-----

3 17

[opensuse] Leap 42.2 - Baloo? How to prevent it indexing /run mounted USB drives
by Greg Freemyer 14 Nov '16

14 Nov '16

I've got 42.2 RC2 on one of my machines. Its a pure vanilla setup. I'm using KDE more extensively than I have in a couple years (I'm normally more CLI only). I just noticed someting (baloo?) is indexing my USB mounted drives. In this case I connected the drive and KDE automounted it under /run. I don't want it to index anything under /run/media/ 1) Is it a bug that it is even indexing /run/media in the first place? 2) I don't see a way to configure baloo under configure desktop. Is there a way other than a text editor? Thanks Greg -- Greg Freemyer -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

4 4

[opensuse] fail2ban - a cautionary note
by Greg Freemyer 14 Nov '16

14 Nov '16

After 3 years of having a server in the cloud with fail2ban on it, it locked me out from my house ISP recently! I had my house's IP in the ignoreip line, but ... Apparently my ISP changed my IP and I had made a typo or two in my password since the IP change. Fortunately my cloud vendor provides console access via a java app so I could log into the console and add me new home IP to the ignore IP line. Just a cautionary note for others, but it was pretty confusing since I could login for a few minutes after reboot, but then re-connecting would be blocked. Greg -- Greg Freemyer -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

9 15

[opensuse] Release Party for openSUSE Leap 42.2
by ddemaio 14 Nov '16

14 Nov '16

Hi all, As you know, the release of openSUSE Leap 42.2 is less the 48 hours from now. There is tons of time to plan a release party. If you do plan on having a release party, please consider adding it to the wiki page https://en.opensuse.org/openSUSE:Launch_parties If you are thinking about having some marketing material for a release party, please contact me at least two weeks before the date you plan on having the release. v/r Doug -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

1 0

[opensuse] There are no buildservice mirrors active
by Bill Merriam 13 Nov '16

13 Nov '16

http://mirrors.opensuse.org/list/bs.html This is supposed to show build service mirrors. It shows none. Is that expected? Bill -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

1 0

[opensuse] Xfce + nouveau: screensaver loses monitors
by Roger Price 13 Nov '16

13 Nov '16

OS: 42.2 Beta kernel 4.4.27, fully patched 2016-11-13. Card: NVIDIA GF100GL [Quadro 4000] Driver: nouveau, X.org server 7.6_1.18.3 Monitors: Iiyama ProLite B2783QSU Power indicator blue=normal, orange=power-saving DP-1 connected 1440x2560+0+0 DP-2 connected 1440x2560+1440+0 Without the screensaver, Xfce+nouveau is stable, but when the screensaver is turned on, it is not always possible to recover the monitors with a user action such as moving the mouse. Example 1: After some 10+ minutes of inactivity (not timed exactly) both monitors go black with no fading. On clicking the Ctl key I recover only the right monitor. The left monitor stays black with power indicator orange. Example 2: I re-booted the machine and logged in a user. This user does nothing. When the screensaver blanked the monitors, I moved the mouse and this was sufficient to recover both monitors. After 7 hours, moving the mouse was no longer sufficient. The right monitor stays blank, although both monitors show the blue power indicator. I have filed bug 1009932 https://bugzilla.opensuse.org/show_bug.cgi?id=1009932 Roger -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

1 0

[opensuse] Howto boot HP elitebook 8760w in legacy mode?
by David C. Rankin 13 Nov '16

13 Nov '16

All, I've gotten a new old laptop (HP EliteBook 8760w) and I cannot get it to boot. It came with Win10 which boots in Legacy mode and all UEFI options in the bios disabled. I've tried a traditions MBR setup: # fdisk -l /dev/sda Disk /dev/sda: 931.5 GiB, 1000204886016 bytes, 1953525168 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disklabel type: dos Disk identifier: 0xff7d45aa Device Boot Start End Sectors Size Id Type /dev/sda1 2048 1953525167 1953523120 931.5G 5 Extended /dev/sda5 * 4096 1028095 1024000 500M 83 Linux /dev/sda6 1030144 105887743 104857600 50G 83 Linux /dev/sda7 105889792 1951383551 1845493760 880G 83 Linux /dev/sda8 1951385600 1953525167 2139568 1G 82 Linux swap / Solaris I've tried GPT with bios_boot: # fdisk -l /dev/sda Disk /dev/sda: 931.5 GiB, 1000204886016 bytes, 1953525168 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disklabel type: gpt Disk identifier: 00B6A48C-CBDB-4071-A1EC-97FA828A6C26 Device Start End Sectors Size Type /dev/sda1 2048 4095 2048 1M BIOS boot /dev/sda2 4096 1028095 1024000 500M Linux filesystem /dev/sda3 1028096 105885695 104857600 50G Linux filesystem /dev/sda4 105885696 1949282303 1843396608 879G Linux filesystem /dev/sda5 1949282304 1951379455 2097152 1G Linux swap I've even tried enabling UEFI and partitioning with a UEFI scheme and booting via systemd, no joy: # fdisk -l /dev/sda Disk /dev/sda: 931.5 GiB, 1000204886016 bytes, 1953525168 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disklabel type: gpt Disk identifier: 00B6A48C-CBDB-4071-A1EC-97FA828A6C26 Device Start End Sectors Size Type /dev/sda1 2048 4095 2048 1M BIOS boot /dev/sda2 4096 1028095 1024000 500M EFI System /dev/sda3 1028096 105885695 104857600 50G Linux filesystem /dev/sda4 105885696 1949282303 1843396608 879G Linux filesystem /dev/sda5 1949282304 1951379455 2097152 1G Linux swap (on this model use of UEFI is not recommended -- which explains why it was disabled to begin with) The odd thing about it is I can boot with any .iso with grub and choose to "Boot existing OS" (changing 'hd0 0' to 'hd1 0') and boot just fine. I just have to boot from USB because the laptop will not see grub any other way. Has anyone else encountered a stubborn HP laptop that takes something out of the ordinary to boot with a simple MBR setup? The frustrating thing is I can throw the Win10 disk back in and it boots just fine. Nothing explains to my why I can boot from an .iso in legacy mode just fine, but cannot boot from the hard drive the same way. There have been no errors on grub install or on grub.cfg generation (the problem is it is just not seeing grub on the drive to begin with) grub is right where it should be, because choosing "Boot existing OS" brings the grub menu right up and boots to a fully functioning install. Currently I'm working with the Arch .iso given the direct access to grubs command line. Does anybody have any thoughts on what to check to see what is causing the bootloader being missed on the hard drives? In nearly 20 years of Linux, probably 50-100 installs, this is the first time I've ever run into a box that just will not see grub on a hard drive. I've reset bios defaults, pulled all batteries, held the power on to drain any residual power, etc.. and the issue isn't an embedded drive signature the box is trying to boot (it wouldn't like the USB if that were the case.) All Disk Lock and other bios security features are disabled. (the bios is actually a very limited laptop bios with very few settings to complicate things.) It's not a question of the laptop not seeing the drive. I've installed a full plasma/KDE5 setup on the drive, I just have to boot it from a darn USB. Does the braintrust have an tips or diagnostics that may shed light on this issue? -- David C. Rankin, J.D.,P.E. -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

2 8

[opensuse] Leap 42.2 updates are not announced yet although published and available?
by cagsm 12 Nov '16

12 Nov '16

Hello. |install|mysql-community-server-errormessages|5.6.34-19.2|x86_64||repo-update|0ff2aa9c4e1e0c73fe4e5431f938fc48ac5cc46511523a42c9364aa0d13c3c57| I see no mentioning of 42.2 in for example <http://lists.opensuse.org/opensuse-updates/2016-11/msg00029.html> <http://lists.opensuse.org/opensuse-security-announce/2016-11/msg00021.html> or on those lists in general. Whereas there is some number of stuff in <http://download.opensuse.org/update/leap/42.2/oss/x86_64/> already Would people not be able to cope or deal with if there were already 42.2 update announcements before the public release of 42.2 itself? Thank you. -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

2 1

[opensuse] Update-alternatives: Some link group broken. What does this mean?
by cagsm 12 Nov '16

12 Nov '16

Is this to mean anything? Seeing it on zypper dup (42.1 -> 42.2) (1036/2732) Installing: kcoreaddons-5.26.0-2.1.x86_64 ....................................................................................[done] Additional rpm output: Unknown media type in type 'all/all' Unknown media type in type 'all/allfiles' Additional rpm output: update-alternatives: warning: forcing reinstallation of alternative /usr/bin/coverage-3.4 because link group coverage is broken (1445/2732) Installing: python3-pip-7.1.2-5.3.noarch .....................................................................................[done] (1446/2732) Installing: python3-nose-1.3.7-3.3.noarch ....................................................................................[done] Additional rpm output: update-alternatives: warning: forcing reinstallation of alternative /usr/bin/nosetests-3.4 because link group nosetests is broken (2027/2732) Installing: gcr-viewer-3.20.0-2.2.x86_64 .....................................................................................[done] Additional rpm output: Unknown media type in type 'all/all' Unknown media type in type 'all/allfiles' Additional rpm output: update-alternatives: warning: forcing reinstallation of alternative /usr/lib64/java-1_8_0-openjdk-plugin/lib/IcedTeaPlugin.so because link group javaplugin is broken (2186/2732) Installing: java-1_7_0-openjdk-plugin-1.6.1-2.38.x86_64 ......................................................................[done] Additional rpm output: update-alternatives: warning: forcing reinstallation of alternative /usr/lib64/java-1_8_0-openjdk-plugin/lib/IcedTeaPlugin.so because link group javaplugin is broken -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

1 0