July 2014 - openSUSE Users - openSUSE Mailing Lists

Re: [opensuse] Encryption password fail on install > internationalisation <
by Carlos E. R. 25 Jul '14

25 Jul '14

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Please remember to post to the list. On 2014-07-23 00:04, Mark Ballard wrote: > > You can add more passwords to the encrypted filesystem. > > Aha! > > Didn't think of that. Probably because even though it is what I will > do, with much gratitude, it is no less inconvenient than, say, using > an alphanumeric password instead. In either instance it requires the > install process to be started over again. Non-US users really should > be spared this initiation. I don't see why the need to reinstall... provided you manage to open the encrypted (LUKS) filesystem once, there is a procedure to add more passwords to it, I can dig the procedure on my notes tomorrow, perhaps. > >> You could >> change temporarily the keyboard to the US one, and then type the same >> keys as on the UK one, which now will be different chars - no matter >> which. I'm unsure if you understand the idea? > > I must have understood this at one time quite recently. I had to > employ the services of Trinity Rescue CD. I had to change the keymap > to the US one in order to enter my passwords. I must have used the > same keys. It doesn't make sense to me any more. It's late. All I can > see at the moment is that some characters on the US keyboard appear on > keys that don't exist on the UK keyboard. Please spare us the pain. > > But anyway, this appears not to be possible during opensuse install. > It's not a command prompt. It's a password prompt on a command screen. > The install hasn't completed yet. It's asking for the encryption > password in US keyboard layout. I'm not sure of that install phase, but I think that what it is saying is that: - it is going to use the current defined keyboard. - on boot, it will use the US keyboard. - thus make sure you now, during install, use keys that are the same both in the US keyboard and your local one. They are not saying, I believe, that during installation the keyboard switches momentarily to the US layout for the password entry., > > >>> Perhaps the problem has not occured in other countries where >>> language differences have focused more attention on >>> internationlisation? >> >> Actually, they are worse. > > Agh. We have more different keys. In Spanish and French, for instance, we have "accents". In German, they have, how they call it... umlauts? Some keys do not produce output the first time you press them, the result depends on the next key you press. I can just barely guess what happens with non Latin alphabet languages. - -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" (Minas Tirith)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iF4EAREIAAYFAlPPF+wACgkQja8UbcUWM1zExgD9H40fvGwEQXVAApx3u4Tdk8XD TuMsqJ4NENbiSE/ZHMUBAJFbnbKAY0Rq34UuxP+Ed7K/fZLmz43Cgk4nkcCBf7gD =VbcF -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

3 7

[opensuse] openSUSE 13.2 milestone various
by Mark Misulich 25 Jul '14

25 Jul '14

Hi, I received a post to this list some time ago that showed the various release dates for 13.2 milestone X, and I think that Milestone 1 was supposed to be released in June or July. I think that it has been slipped to sometime later now, but can't find the calendar of release dates anymore. Where does the calendar of release dates for different milestones live now, and when will Milestone 1 be released? Mark -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

3 2

[opensuse] SuSE 13.1 as NFS client: boot hangs
by MarkusGMX 25 Jul '14

25 Jul '14

Hello, I had this on my SuSE machines since SuSE 10.3, always without problems: A NAS acts as NFS server and my SuSE machine as NFS client. I simply create some mount directories and let yast2 do the magic in creating the connection between NAS as NFS server and machine as NFS client. I never touched any NFS config files as it worked out of the box as it should be. Now I changed to SuSE 13.1, did the same as always and it hangs at a certain time when booting. :-(((( After I switch on the NAS, the boot goes on. What is that hickup? I just use the default yast2 settings as with every SuSE before. After deleting the NFS shares in Yast2 there is only one share that appears in df -k I unmount that and the next one appears. I unmount the 2nd and the 3rd appears ->? In previous versions of SuSE "df -k" always showed all NFS shares! In this forum there are other problems with NFS but afaics not this one. Internet is not helpful. https://en.opensuse.org/YaST_NFS_Client says "Boot times increased while waiting for a response from network NFS servers. This was resolved with full systemd which simply bypasses unavailable drives using short timeouts and then connects when drives become available. " Is that broken? Any pointers? Thx -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

3 6

[opensuse] help? ISP apparently indulging in DNS hijacking and censoring
by jdebert 25 Jul '14

25 Jul '14

Sprint appears to be hijacking DNS, replying with IP's to their own ad/"search" server for bad hostnames that should return NXDOMAIN. Also, using 'dig +DNSSEC example.com 8.8.8.8' returns with Sprint's response prepended to the queried server's NXDOMAIN response and the ad bit cleared. According the google, the ad bit is supposed to be set in replies for DNSSEC enabled queries,since their public server is configured to do just that. Further, for some DNS queries, such as for isc.org, there is no response at all, not even NXDOMAIN. I know those sites still exist because I can get the IP from websites with DNS tools. Sprint definitely appears to be intercepting all port 53 traffic. This started within the last month. Sprint still uses HTTP redirects to send http requests to nonexistent servers to it's own ad/"search" servers. Is it possible to avoid this stuff? I don't see how it is possible when Sprint is not merely watching DNS traffic but actively intercepting it and modifying it, disabling DNSSEC. Unrelated(?), there are occasions where invalid SSL/TLS certificates are received with the correct CN but the wrong fingerprint, etc., and the wrong server keys received when connecting to servers using SSH. It does not stop until I drop the connection and reconnect. jd -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

6 11

Re: [opensuse] SuSE 13.1: Evince: Top menus broken
by Simon Heimbach 24 Jul '14

24 Jul '14

Hi! I guess you're running KDE. Try this: System Settings -> Application Appearance -> GTK -> oxygen gtk (or whatever you're using) for GTK 2 and GTK 3. You may also want to look in YAST's software center for anything like gtk- oxygen-theme. Then I'd start evince from bash to see any error messages popping up. This might help you a bit. Simon Am Donnerstag, 24. Juli 2014, 20:35:54 schrieb MarkusGMX: > Am 20/07/14 um 18:23 schrieb MarkusGMX: > > Am 20/07/14 14:17, schrieb MarkusGMX: > >> I have an obvious error in the menu of > >> Evince: > >> > >> http://img5.fotos-hochladen.net/uploads/evincebugqx3fjckpil.jpg > >> > >> Any pointers what that could be? > >> Any changed icon directories in OpenSuSE 13.1 ? > >> > >> Mouse over of course works. > >> > >> On SuSE 12.1 evince was working without problems. > >> > >> Thx in advance > > > > There are some hints in > > https://bugs.mageia.org/show_bug.cgi?id=5132 > > but all these are installed ( gnome-icon-theme-symbolic ). > > > > When I run evince as root it works: > > http://img5.fotos-hochladen.net/uploads/correctevinceas2tsuw37xnf.jpg > > > > Any ideas? > > No ideas? > > BR ------------------------------------------------------------- -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

1 0

[opensuse] grub2 does not reflect installation of new kernel - how to add entry?
by David C. Rankin 24 Jul '14

24 Jul '14

All, As part of troublshooting the acpi backlight bug in 13.1, https://bugzilla.novell.com/show_bug.cgi?id=887629 there was a request I install and test the 3.15 kernel from kernel:/stable/standard. The install went fine after adding the repository and was done via 'zypper up -t package'. The zypp.conf multiverison preserved the 3.11 kernel: kernel-default-devel-3.11.10-17.2.x86_64 kernel-default-devel-3.15.6-2.1.gedc5ddf.x86_64 kernel-desktop-3.11.10-17.2.x86_64 kernel-desktop-3.15.6-2.1.gedc5ddf.x86_64 kernel-desktop-devel-3.11.10-17.2.x86_64 kernel-desktop-devel-3.15.6-2.1.gedc5ddf.x86_64 kernel-devel-3.11.10-17.2.noarch kernel-devel-3.15.6-2.1.gedc5ddf.noarch kernel-firmware-20140624git-35.1.noarch kernel-source-3.11.10-17.2.noarch kernel-source-3.15.6-2.1.gedc5ddf.noarch kernel-syms-3.11.10-17.1.x86_64 kernel-syms-3.15.6-2.1.gedc5ddf.x86_64 kernel-xen-devel-3.11.10-17.2.x86_64 kernel-xen-devel-3.15.6-2.1.gedc5ddf.x86_64 The problem is that grub2 only reflects a single menu entry for 'openSuSE 13.1' and no second entry to boot the 3.11 kernel. Now with good-old grub, I'd simply edit /boot/grub/menu.lst and add a new menu entry for 3.11. But what do you do for grub2? Also, why doesn't the kernel install create menu entries like it did in 11.4? From 11.4 updates, I had a page full of kernels to choose from. Now, just 1? What says the brain-trust? -- 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

4 10

[opensuse] Is an UPDATE from 12.3 (32 bit) to 13.1 (64 bit) supported
by Mark Hounschell 24 Jul '14

24 Jul '14

Is doing an UPDATE from 12.3 (32 bit) to 13.1 (64 bit) supported. Thanks Mark -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

5 6

[opensuse] aaa_base-extras keeps messing up alias.bash on update, how to prevent?
by David C. Rankin 24 Jul '14

24 Jul '14

All, aaa_base-extras is a real pain. After going through the trouble to get rid of all the --color-auto stuff from grep, it's BACK... :( There used to be logic, I think that was a list provided by SuSEConfig or one of the sysconfig files that checked file sizes in /etc and if the current file size in /etc was not the original then any subsequent attempt to overwrite the file would cause the file to be installed as .rpmsav or the like. If something like that still exists, can I add /etc/profile.d/alias.bash to that check somehow? Also, why doesn't /etc/profile source something like /etc/profile.local? At least that way there would be one file where you could undo the non-standard stuff that would not be overwritten on every update? We could do it in /etc/bash.bashrc.local, but I'd much prefer putting revisions to the /etc/profile scheme in an /etc/profile.local so at least it tells me where the original came from. I'm looking for a system level solution that isn't overwritten on each update that can accomplish this. Hopefully something short of rpm -e aaa_base-extras. Is there any good solution to the aaa_base-extras fun? -- 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 2

[opensuse] 13.1 - Are ucode-amd and mkinitrd from kernel:/stable/standard compatible with 3.11 kernel?
by David C. Rankin 24 Jul '14

24 Jul '14

All, I noticed that installing the 3.15 kernel from kernel:/stable/standard also installs and updated ucode-amd and mkinitrd. I'm fairly certain the mkinitrd is backwards compatible for all 3.X kernels on 13.1, but I'm not 100% sure. If I downgrade to the 3.11 kernel (or boot it) will the current mkinitrd from kernel:/stable/standard be fine for generating kernel images? Same question for ucode-amd. I'm not familiar with the package. If I boot the 3.11 kernel, will the ucode-amd installed from kernel:/stable/standard cause any issues? Just making sure I don't run into any surprises if I switch back and forth between the kernels. -- 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

1 0

[opensuse] What happened to Adobe Acrobat reader
by Anton Aylward 23 Jul '14

23 Jul '14

I can't seem to find acroread any more. -- Capitalism is the astounding belief that the most wickedest of men will do the most wickedest of things for the greatest good of everyone. --John Maynard Keynes -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

14 48