December 2016 - openSUSE Users - openSUSE Mailing Lists

[opensuse] how to keep kde desktop icons position over reboot?
by Daniel Bauer 17 Dec '16

17 Dec '16

Hi, Since some updates, maybe since a month, many icons on my desktop are repositioned ever time I bot the computer. This is an uptodate leap 42.1 with kde, using the classic desktop folder view. It looks quite random which icons are moved. I thought, maybe during boot the actual screen size isn’t known and thus icons from the border are moved to an empty space, but that's can't be, because some icons that I laced in the center of the screen move up to the top of the screen, others, just beside or below, stay where I've placed them. How can I resolve this? Can I fix their positions somehow? Or at least find out what causes these repositionings? What and where should I look? Thanks for your hints. Daniel -- Daniel Bauer photographer Basel Barcelona http://www.daniel-bauer.com -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

2 2

[opensuse] is this fix in upcoming leap? Could it be "backported" to older supported distro-releases (13.2?)?
by L A Walsh 17 Dec '16

17 Dec '16

Just ran into a bug in the "ld.gold" linker in binutils. When trying to compile the 4.9 vanilla kernel (as downloaded from kernel.org) I got: ld: internal error in target, at ../../gold/parameters.h:105 scripts/Makefile.build:498: recipe for target 'lib/lib-ksyms.o' failed make[1]: *** [lib/lib-ksyms.o] Error 1 Makefile:988: recipe for target 'lib' failed make: *** [lib] Error 2 It's caused by a bug in the gold linker (but is not present in the "ld.bfd" version of the linker). Apparently it's been patch in the trunk version of binutils as of 2016-11-21. Since it affect anyone compiling the kernel (and who's alternatives point "ld" to the ld.gold linker), it might be nice to backport. If not backported, then users can only work around the problem by overriding the "alternatives" dir and not using the gold linker -- which I though had various other benefits/features -- i.e. might cause other random compatibility issues if switched (I don't know how likely this is, but it makes me nervous to switch "ld" just for the kernel compiles and have it affect all other products that use "ld". -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

2 1

Re: [opensuse] leap422 okular printing issue
by stakanov＠freenet.de 16 Dec '16

16 Dec '16

> -----Ursprüngliche Nachricht----- > Von: Per Jessen > Gesendet: Do. 15.12.2016 08:20 > An: opensuse(a)opensuse.org > Betreff: Re: [opensuse] leap422 okular printing issue > > Carlos E. R. wrote: > >> -----BEGIN PGP SIGNED MESSAGE----- >> Hash: SHA256 >> >> On 2016-12-14 14:28, Per Jessen wrote: >>> Carlos E. R. wrote: >> >> >>>>>> I'll check. >>>>> >>>>> There are no page-size related settings in YaST for this >>>>> printer. It's all about whether it is the default and which >>>>> driver to use (currently 'raw'). >>>> >>>> It should be in the CUPS control web page. >>> >>> But the local CUPS isn't in use. >> >> Then remote cups page. > > Yes, but as it works with every other system, there's no need to fiddle > with it. In fact, that is a good reason _not_ to fiddle with it. > Besides, I think every print-job has its own page-size setting? > >> I think that you would use the local CUPS with the driver for the >> printer, which hands up to a remote CUPS, set up as "raw". One of the >> two uses the printer driver, not the two. > > The client system talks directly to the printserver via this: > > lpstat -v > device for BESR-printer: ipp://192.168.2.128:631/printers/BESR-printer > device for Kyocera: ipp://192.168.2.128:631/printers/Kyocera > device for Kyocera2: ipp://192.168.2.128:631/printers/Kyocera2 > > There are no PPDs installed locally. > > I dont know where I saw the 'raw' driver setting, somewhere in YaST I > think. > > > > -- > Per Jessen, Zürich (0.2°C) >http://www.cloudsuisse.com/ - your owncloud, hosted in Switzerland. > > > -- > To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org > To contact the owner, e-mail: opensuse+owner(a)opensuse.org > > > > -----Ursprüngliche Nachricht Ende----- Oh, great. I think I know the problem. AFAIK, you need(!) for every printer to talk in raw to, the ppd installed locally for that printer. Then, you need to specifiy within raw that you are talking to a kyocera. I did paste you an image where to do this in yast: http://paste.opensuse.org/75014130 Note that for what I know you need also to have the ppd locally installed for that(!) specific printer. So yast will know that it needs raw, it will know to which brand to send it and it should format it rightly using the specific ppd setting. This is what I had to do with a non professional setup working with raw. But since your problem seem right like mine, have a try. --- Die Bundesliga hat begonnen! Alle Tore, alle Ergebnisse, alle News: Pocket Liga jetzt im https://app.adjust.com/dpynzd oder https://app.adjust.com/dpynzd herunterladen - kostenlos! -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

5 7

[opensuse] Memory corruption detected in low memory
by Carlos E. R. 16 Dec '16

16 Dec '16

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Hi, What should I think of this? It is a warning, not an error, apparently. In the BIOS, perhaps. <0.3> 2016-12-11T13:37:26.094997+01:00 Isengard kernel - - - [382640.164069] Corrupted low memory at ffff880000002000 (2000 phys) = 0000f0f6 <0.4> 2016-12-11T13:37:26.095031+01:00 Isengard kernel - - - [382640.164092] ------------[ cut here ]------------ <0.4> 2016-12-11T13:37:26.095034+01:00 Isengard kernel - - - [382640.164111] WARNING: CPU: 1 PID: 7380 at ../arch/x86/kernel/check.c:141 check_for_bios_corruption+0xf9/0x110() <0.3> 2016-12-11T13:37:26.095036+01:00 Isengard kernel - - - [382640.164114] Memory corruption detected in low memory <0.4> 2016-12-11T13:37:26.095037+01:00 Isengard kernel - - - [382640.164116] Modules linked in: rfcomm fuse nf_log_ipv6 xt_pkttype nf_log_ipv4 nf_log_common xt_LOG xt_limit xt_recent af_packet iscsi_ibft iscsi_boot_sysfs ip6t_REJECT nf_reject_ipv6 xt_tcpudp nf_conntrack_ipv6 nf_defrag_ipv6 ip6table_raw ipt_REJECT nf_reject_ipv4 iptable_raw xt_CT iptable_filter bnep ip6table_mangle nf_conntrack_netbios_ns nf_conntrack_broadcast nf_conntrack_ipv4 nf_defrag_ipv4 ip_tables xt_conntrack nf_conntrack ip6table_filter ip6_tables x_tables dm_crypt snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_codec_generic xfs libcrc32c intel_rapl intel_powerclamp coretemp kvm_intel kvm irqbypass crct10dif_pclmul crc32_pclmul crc32c_intel jitterentropy_rng nls_iso8859_1 arc4 nls_cp437 vfat fat dm_mod drbg ansi_cprng joydev hid_logitech_hidpp iTCO_wdt iTCO_vendor_support iwlmvm mac80211 msi_wmi sparse_keymap snd_hda_intel snd_hda_codec snd_intel_sst_acpi i915 snd_hda_core aesni_intel snd_intel_sst_core drm_kms_helper btusb iwlwifi drm aes_x86_64 btrtl snd_soc_rt5670 lrw fb_sys_fops btbcm gf128mul snd_soc_sst_mfld_platform hid_logitech_dj pcspkr r8169 btintel snd_hwdep serio_raw snd_soc_rl6231 lpc_ich glue_helper bluetooth mii mfd_core ablk_helper cryptd snd_soc_core i2c_i801 cfg80211 nxp_nci_i2c snd_compress syscopyarea sysfillrect sysimgblt nxp_nci mei_txe i2c_algo_bit shpchp mei snd_pcm nci thermal fan nfc snd_timer regmap_i2c battery snd wmi fjes i2c_designware_platform i2c_designware_core video rfkill_gpio rfkill soundcore 8250_dw pwm_lpss_platform pwm_lpss pinctrl_cherryview button processor sunrpc ext4 crc16 jbd2 mbcache uas usb_storage usbhid sd_mod ahci libahci xhci_pci xhci_hcd usbcore usb_common libata sdhci_pci i2c_hid sdhci_acpi sdhci mmc_core sg scsi_mod efivarfs autofs4 <0.4> 2016-12-11T13:37:26.095040+01:00 Isengard kernel - - - [382640.164309] CPU: 1 PID: 7380 Comm: kworker/1:2 Not tainted 4.4.27-2-default #1 <0.4> 2016-12-11T13:37:26.095042+01:00 Isengard kernel - - - [382640.164313] Hardware name: Micro-Star International Co., Ltd. MS-B120/MS-B120, BIOS EB120IMS.820 03/03/2016 <0.4> 2016-12-11T13:37:26.095043+01:00 Isengard kernel - - - [382640.164321] Workqueue: events check_corruption <0.4> 2016-12-11T13:37:26.095044+01:00 Isengard kernel - - - [382640.164323] 0000000000000000 ffffffff81327657 ffff880063aa7d98 ffffffff81a4c986 <0.4> 2016-12-11T13:37:26.095046+01:00 Isengard kernel - - - [382640.164329] ffffffff8107e821 0000000000000000 ffff880063aa7de8 ffffffff821edff0 <0.4> 2016-12-11T13:37:26.095047+01:00 Isengard kernel - - - [382640.164334] 0000000000000001 ffff880000000000 ffffffff8107e89c ffffffff81a43dc0 <0.4> 2016-12-11T13:37:26.095048+01:00 Isengard kernel - - - [382640.164340] Call Trace: <0.4> 2016-12-11T13:37:26.095049+01:00 Isengard kernel - - - [382640.164358] [<ffffffff81019e69>] dump_trace+0x59/0x320 <0.4> 2016-12-11T13:37:26.095051+01:00 Isengard kernel - - - [382640.164368] [<ffffffff8101a22a>] show_stack_log_lvl+0xfa/0x180 <0.4> 2016-12-11T13:37:26.095052+01:00 Isengard kernel - - - [382640.164372] [<ffffffff8101afd1>] show_stack+0x21/0x40 <0.4> 2016-12-11T13:37:26.095053+01:00 Isengard kernel - - - [382640.164380] [<ffffffff81327657>] dump_stack+0x5c/0x85 <0.4> 2016-12-11T13:37:26.095054+01:00 Isengard kernel - - - [382640.164387] [<ffffffff8107e821>] warn_slowpath_common+0x81/0xb0 <0.4> 2016-12-11T13:37:26.095056+01:00 Isengard kernel - - - [382640.164395] [<ffffffff8107e89c>] warn_slowpath_fmt+0x4c/0x50 <0.4> 2016-12-11T13:37:26.095057+01:00 Isengard kernel - - - [382640.164400] [<ffffffff81060da9>] check_for_bios_corruption+0xf9/0x110 <0.4> 2016-12-11T13:37:26.095058+01:00 Isengard kernel - - - [382640.164408] [<ffffffff81060dca>] check_corruption+0xa/0x40 <0.4> 2016-12-11T13:37:26.095059+01:00 Isengard kernel - - - [382640.164413] [<ffffffff81097205>] process_one_work+0x155/0x440 <0.4> 2016-12-11T13:37:26.095060+01:00 Isengard kernel - - - [382640.164418] [<ffffffff81097d46>] worker_thread+0x116/0x4b0 <0.4> 2016-12-11T13:37:26.095062+01:00 Isengard kernel - - - [382640.164425] [<ffffffff8109d328>] kthread+0xc8/0xe0 <0.4> 2016-12-11T13:37:26.095063+01:00 Isengard kernel - - - [382640.164433] [<ffffffff8160978f>] ret_from_fork+0x3f/0x70 <0.4> 2016-12-11T13:37:26.095064+01:00 Isengard kernel - - - [382640.167228] DWARF2 unwinder stuck at ret_from_fork+0x3f/0x70 <0.4> 2016-12-11T13:37:26.095065+01:00 Isengard kernel - - - [382640.167231] <0.4> 2016-12-11T13:37:26.095067+01:00 Isengard kernel - - - [382640.167232] Leftover inexact backtrace: <0.4> 2016-12-11T13:37:26.095068+01:00 Isengard kernel - - - [382640.167232] <0.4> 2016-12-11T13:37:26.095069+01:00 Isengard kernel - - - [382640.167242] [<ffffffff8109d260>] ? kthread_park+0x50/0x50 <0.4> 2016-12-11T13:37:26.095070+01:00 Isengard kernel - - - [382640.167246] ---[ end trace 3ac627478cecce4d ]--- Machine is running Leap 42.2. Memtest passed with no errors. - -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" (Minas Tirith)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iF4EAREIAAYFAlhOGPwACgkQja8UbcUWM1xB/QD+JiVm8KxuWPXm9fttxKprFwet krWdsThsByUE4z/4eaAA/0g9R8zr4TWNZFRKLb0zLzdx3k7AApHj+i4Zbk2bRyc7 =d7FR -----END PGP SIGNATURE----- N��r��y隊Z)z{.�ﮞ˛��m�)z{.��+�:�{Zr�az�'z��j)h��Ǿ� ޮ�^�ˬz��

2 5

[opensuse] Network Manager issues
by Per Jessen 16 Dec '16

16 Dec '16

On a new laptop, I was forced to use Network Manager as wicked does not work (bug#1012299). I normally never use Network Manager, so I'm new to this - questions: a) is it normal that NM does not set the hostname based on what DHCP dishes out? Can I change this somewhere? b) network drives - when I rebooted just now, they were not automatically mounted. They're in fstab, it has always worked fine with wicked/systemd. -- Per Jessen, Zürich (0.6°C) http://www.dns24.ch/ - free dynamic DNS, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

3 6

[opensuse] openSUSE Conference & Registration
by Douglas DeMaio 16 Dec '16

16 Dec '16

Hi all, The new year is quickly approaching, which means it is time to prepare for this year's openSUSE Conference. The planning for the conference will begin in January, and we want to assemble teams to help build upon the success of last year's conference. If you are interesting in taking part in the planning of oSC17, please send me an email. Registration for the conference is open at https://events.opensuse.org/, so be sure to register over the holidays if you have time. Also, don't forget to answer the question about your T-Shirts Size. The Call for Papers is also open, so if you get some crazy ideas over the next 107 days, please be sure to submit it at https://events.opensuse.org/conference/oSC17/program/proposal/new (Must be Signed In). Further information will follow in the months ahead, so enjoy the holiday season. v/r Doug -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

2 1

Re: [opensuse] leap422 okular printing issue
by stakanov＠freenet.de 15 Dec '16

15 Dec '16

> -----Ursprüngliche Nachricht----- > Von: Per Jessen > Gesendet: Di. 13.12.2016 18:07 > An: opensuse(a)opensuse.org > Betreff: [opensuse] leap422 okular printing issue > > Printing an A4 page from Okular makes it come out scaled down to what > looks like 2/3 size. Printing to the same printserver from 13.1 works > fine. I don't even know where to begin to look. Any hints? > > > -- > Per Jessen, Zürich (1.0°C) >http://www.hostsuisse.com/ - virtual servers, made in Switzerland. > > > -- > To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org > To contact the owner, e-mail: opensuse+owner(a)opensuse.org > > > > -----Ursprüngliche Nachricht Ende----- Sorry if this should be a "thred breaker" but I haven't yet been accepted by another mailer (ip problem it seems). So, to make it short: I am using 42.1 and Lexmark. With 13.1-13.2 no problems. But with 42..1 I had quite a few with scaling. It boils down to the point that with 13.2 and before, the printersettings in the printerfirmware where ingnored or overridden. With 42.1 if there is Legal in the firmware of the printer as size and A4 in the settings of yast.....the thing prints badly formatted. When I did find out and corrected, within the firmware, to A4, the problem stopped. This could also be your case. Look if you do not have B4 or B5 setted for what ever reasons in your printer firmware. Or if it is et to "enveloppe". With me that caused disturbances in 42.1 that did NOT manifest before with the very settings. Hope that helps. Controll also the settings in yast. I had the case with tumbleweed that the change to another cups version resetted the driver settings to Legal instead of A4 as it was. Once set up by hand it worked again. --- Die Bundesliga hat begonnen! Alle Tore, alle Ergebnisse, alle News: Pocket Liga jetzt im https://app.adjust.com/dpynzd oder https://app.adjust.com/dpynzd herunterladen - kostenlos! -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

3 8

[opensuse] OpenSUSE Leap42.2 NFS installation
by Mathias Radtke 15 Dec '16

15 Dec '16

Hi In our company we work on automatic OS provisioning. Currently I am trying to make an OpenSUSELeap42.2 unattended installation. The install process itself uses the iso as an nfs source. The installation works fine in stage 1. When booting stage 2 the installer cannot access the nfs share. Therefore the unattended installation breaks and the skip butTon has to be clicked. However the nfs share cannot be accessed because in stage 2 the installer first tries to access the share, when skipped it configures the network card. I need stage 2, because of custom scripts injected into the install process. Is there any way to suppress the error message on the nfs mount. Or is it even a bug that the network isn't configured and a share shall be accessed? y2log is attached Cheers Mathias -- Mathias Radtke --- http://uib.de/de/support-schulung/schulung/ --- uib gmbh Bonifaziusplatz 1B 55118 Mainz Tel. 06131 / 27561-16 <phone:061312756116> Fax 06131 / 27561-22 <phone:061312756122> E-Mail: m.radtke(a)uib.de Internet: www.uib.de Geschäftsführer: dr. detlef oertel & erol ueluekmen Handelsregister: Amtsgericht Mainz HRB 6942

3 4

[opensuse] OSS on oS 13.1
by Roger Oberholtzer 15 Dec '16

15 Dec '16

I am playing with sound on openSUSE 13.1. It seems that sound hardware is detected and various kernel modules loaded. However, snd_pcm_oss is not getting loaded. So there is no /dev/dspX. Which I want. If I load the driver then the device node is created. I can of course add this to an rc script. But I am curious why this might not be loaded. What might I have missed? Especially since all the other snd* kernel drivers seem to be loaded. -- Roger Oberholtzer -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

2 1

[opensuse] automatic time synching when computer connects to the net
by Istvan Gabor 15 Dec '16

15 Dec '16

Hello: I am interested if this is possible, and how, in openSUSE 13.1 and 13.2 systems: The computer is mostly offline and is connected to the network for limited periods only (by USB mobile net device). The computer's clock is inaccurate and shows large differences (tens of minutes), which is becoming worse at every bootup. Instead of playing with adjtime etc, I would like the system to synchronize the time automatically with an ntp server when the computer is connected to the network. I am afraid if I turn on ntp daemon, it causes long delays at boot if net connection isn't available. Thanks, Istvan -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

9 17