February 2015 - openSUSE Users - openSUSE Mailing Lists

[opensuse] Switch off GSS for NFS?
by MarkusGMX 13 Feb '15

13 Feb '15

Hello, when switching on NFS to my external NAS I get messages in /var/log/messages : rpc.gssd[17127]: ERROR: No credentials found for connection to server NAS.mydom.at rpc.gssd[17127]: ERROR: gssd_refresh_krb5_machine_credential: no usable keytab entry found in keytab /etc/krb5.keytab for connection with host NAS.mydom.at I did not turn on GSS security in yast when switching on NFS client. So why is gss turned on? I do not need it since the network is an internal one. The NAS does not have any gss as far as I can see. BR ME -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

5 8

[opensuse] Disturbing puzzle about 13.2 (and Firefox 35.0)
by Basil Chupin 13 Feb '15

13 Feb '15

My wife and I are using 13.2 installed from the same DVD, and I update the systems daily using zypper. The only difference is that her computer has an Intel 4-core CPU with 8GB of RAM and I have an AMD 8-core CPU with 16GB of RAM. (Yes, OK, the graphics cards are also different.) Earlier today my wife received a post giving her an URL to some video on YouTube. She tried to play it and found that Firefox 35.0 refused to open the video because the flashplayer was out-of-date and therefore was a "security" risk. I went thru the motions of trying to upgrade flashplayer to the new version but- 1) the "1-click" install (from Adobe) produced the error message that 'my' backside did not have the necessary doohickies to do such an installation; and 2) when I tried to manually install the downloaded RPM I got a bunch of "file dependency" errors. So, no upgrade to the latest flashplayer from Adobe! (I tried doing the same upgrade of flashplayer on my computer and got the same results: my butt has not the ability to do these upgrades, and "dependency errors".) Now, there *IS* an upgrade of Adobe flash for Firefox so why isn't this upgrade made available in openSUSE 13.2 for Firefox 35.0? ....................................................................... There is one more puzzle :-( . On both our systems we have the OpenH264 Video Codec from Cisco installed. When I go to YouTube and select to use HTML5 I get the result that my Firefox can handle html5, but when I do the same on my wife's computer I get the result that Firefox *cannot* handle html5! ............................................................... I have to conclude that most, if not all, developers are not married and so they do not know what it is like to handle the high pitched accusation flung at you when your wife comes out with, "WHAT have you done NOW?! WHY isn't this working?! STOP updating my system!" So, developers/packagers, get things straightened out and get things to work properly, OK? :'( BC -- Using openSUSE 13.2, KDE 4.14.3 & kernel 3.18.5-1 on a system with- AMD FX 8-core 3.6/4.2GHz processor 16GB PC14900/1866MHz Quad Channel RAM Gigabyte AMD3+ m/board; Gigabyte nVidia GTX660 GPU -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

12 20

Re: [opensuse] Re: Why is systemd[1] is mounting noauto partitions?
by Dirk Gently 13 Feb '15

13 Feb '15

Araluen wrote: > On Sun, 2014-06-01 at 16:13 -0400, Dirk Gently wrote: >> Linda Walsh wrote: >>> Felix Miata wrote: >>>> WRT openSUSE: The fence is down. The barn is empty. For all practical >>>> purposes the herd has been lost. If you don't want a system dependent >>>> on systemd... >>> --- >>> Well, that's until it goes a bit too far. >>> >>> Remember, it's just something to help help your system boot faster by >>> doing parallel boot. And now? Seems like it fell a bit short of that >>> initial goal, as well. If you already booted direct from HD and used >>> parallel boot in the run scripts, there seems to be a slowdown. What >>> I don't understand is why people keep converting more to systemd, when >>> it didn't make good on its initial promises. >> >> >> >> More importantly, shaving a couple of seconds off of boot time is >> really sooooper-dooooper important, why, exactly? >> >> Systemd is doing the equivalent of fouling up the reliability of all the >> critical control systems of an automobile, all for the stated goal of >> gettin the engine to start in 3 seconds rather than 4. >> >> The rsultant calamities would wind up in court as criminal malfeasance. >> >> Nobody has yet explained WHY saving a couple of seconds at boot time >> is ooh soooo important (And I remember the days when unix systems with only >> 1 MB of memory took 15 minutes to boot up) that it justifies fucking up the >> entire concept of run-levels, and using well-debugged shell-scripts rather than >> some pulled-out-of-the-ass custom scripting language which is NOT anywhere >> close to fully debugged, and config files full of XML crud. >> >> I think we both agree that the net effect of the trade-offs is not beneficial to users or system >> administrators, but it sure does stroke the ego of Lennert Poettering and Kay Sievert. There's >> going to be a special place in hell for those two. >> > > Well then, if we are compromising system stability for such a negotiable > benefit, how do we turn the situation around? > Or is it full speed ahead and damn the torpedoes. Unlike Farrugut's order at the Battle of Mobile Bay, going full-speed ahead is not going to achieve any useful objectives, yet the dangers of systemd are still there. For one, systemd is making APPLICATIONS now dependant on the systemd API, which means when even the biggest fanboys here, at Redhat, and other distributions finally are forced to admit that systemd is a crock of shit.... we won't be able to remove it.... in other words, unlike Farragut, the probability of eventually being blown out of the water by a systemd torpedo is 100%. SysV init has problems, but without a doubt, it does NOT present itself as being a massive security hole, nor present the risk of making a system unbootable. > > Cheers, Mark > -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

33 291

Re: [opensuse] Re: Why is systemd[1] is mounting noauto partitions?
by ianseeks 13 Feb '15

13 Feb '15

On Thursday 12 Feb 2015 11:52:49 Joe Zappa wrote: > ianseeks wrote: > > On Wednesday 11 Feb 2015 10:43:32 Joe Zappa wrote: > >> ianseeks wrote: > >>> On Tuesday 03 Jun 2014 03:08:45 Dirk Gently wrote: > >>>> Damian Ivanov wrote: > >>>>> You have no idea. Not the slightest clue. You can't keep it technical. > >>>>> Fuck you Dirk Gently. > >>>> > >>>> 1. systemd doesn't produce ASCII (or for that matter, UTF) log files, > >>>> it > >>>> produces binary blob log files. > >>>> > >>>> > >>>> Which means you can't just browse through a log file using grep, awk, > >>>> and/or more (or less). > >>> > >>> journalctl | grep xxx > >> > >> And why do you need to run journalctl instead of just grepping the file > >> directly??? > > > > how many files do you have to grep to trace the issue you are looking for? > > Hey, Ian, > > When you look at > > > grep pattern /var/log/somelogfile > > and > > journalctl | grep pattern > > > What is the HUGE difference between those two command lines? For a single line there is no real difference. If you read the question i asked, i said "files", not a "file". > Are you clever enough to spot it? > > > just configure it to use rsyslog if you want to increase your workload and > > Yes, increase your system workload because SYSTEMD DOES LOGGING COMPLETELY > WRONG! that's your personal opinion not a valid reason > > grep multiple files. using journalctl will make your life easier and > > reduce > > the repetitive creating of using scripts to do your job > > No, JOURNALCTRL adds additional overhead i see you avoided answering that question. > >> Because the log file is a binary blob which MUST BE INTERPRETED BY > >> JOURNALCTL. > > > > why do you use "grep" instead of editing the files manually? > > What kind of idiotic question is this? i was saying you'll use tools that make viewing files (and other tasks) easier (journalctl is a tool) > > Note that I'm not asking IF it is an idiotic question, I'm asking > you to tell me which particular type of idiotic question you > intend for it to be. > > > It makes life > > > > easier which is one of the uses of computers. How do you interpret > > MariaDB > > database files, do you grep them? > > You have left the sphere of rational discourse, just like every other > proponent of systemd, now that the discussion gets down to specifics. no, just pointing out the obvious that you'd be happy with files being in a binary format elsewhere on the system > >>> or > >>> > >>> journalctl > /tmp/xxxx > >>> then do your stuff > >> > >> That doesn't change the fact that systemd violates on the major > >> principles > >> of what has made Unix and now Linux so successful -- NO BINARY BLOBS FOR > >> HUMAN READABLE INFORMATION. > > > > if you go back in time far enough i'd expect you'll find using a GUI was > > violating the Unix principle of only using a cli. I heard many an argument > > about the GUI/cli offerings. Compromises are made all the time, have a > > read of this as an example > > http://www.johndcook.com/blog/2012/05/25/unix-doesnt-follow-the-unix-philo > > sophy/ > > > > an example of the benefit of journalctl. whats easier? > > create a script(s) that produces a single sorted output from all the log > > files for a specified date/time range of 07:37 to 08:29 and note the time > > it took to write it and debug it. > > or > > a single line > > journalctl --since 07:37 --until 08:29 > > You might think that's simpler. it is far simpler and quicker, show me the way you'd do it that is simpler and quicker and can be done on one line >Most of us don't. > I have over 20 years administrating Unix and Linux systems. > If journalctl was a win, I would jump right on it, > but like nearly everything associated with systemd, > minor wins are accompanied by HUGE losses. perhaps you need to watch this, its called " The Six Stages of systemd " https://www.youtube.com/watch?v=-97qqUHwzGM I think you might be in the "denial" stage > >>>> 2. systemd eliminates separate log files... so if you're looking for > >>>> ntp > >>>> messages, we no longer have ntp log files... now we have to wade > >>>> through > >>>> the whole combined (binary only) logfile > >>> > >>> journalctl | grep ntp > >> > >> Once again, show us how to do it WITHOUTH journalctl. > > > > configure systemd to use rsyslog. > > > >> 1. What if your journalctl executable gets compromised? > > > > what if any executable on your system gets compromised? > > > >> 2. Why do we need this extra overhead every time we want > >> to look at a journal? > > > > What overhead? it'll save you loads of time if you have to a lot of > > searching of log files, its only 10 letters to type and no changing of > > directories. If 10 letters are too much to type, create an alias. > > > >>> The ntp log files exist on my opensuse 13.2 > >>> > >>>> 3. The old time tested method of keeping log files small and maneagble > >>>> (daily rotation) is now also broken, YATFUBSD (Yet Another Thing Fucked > >>>> Up > >>>> By SystemD) > >>> > >>> http://www.h-online.com/news/item/Latest-release-of-systemd-includes-tim > >>> e-> > based-log-rotation-1735258.html>> > >> So, in other words, after much harping by the community, Poettering, et > >> al > >> have finally pulled their heads out of their asses on this ONE point.... > > > > that was a news article from 2012 which is quite early in systemd's > > development life cycle. Maybe you don't know but when developing software, > > it takes time and not all functions are ready on day one. > > > >>>> Obviously, you're either ignorant or making up more lies. Which is it? > >>> > >>> you are obviously out of date on info about systemd > >>> > >>>> Do you want to keep on playing this idiotic game where you make false > >>>> assertions, and I point out how the truth differs from what you say it > >>>> is? > >>> > >>> you wouldn't know the truth if it smacked you in the mouth > >>> > >>> Now go away and do some reading about systemd and find out what it > >>> really > >>> does > >> > >> I've read a lot about it. > >> > >>>>> 2014-06-03 2:26 GMT+02:00 Dirk Gently <dirk.gently00(a)gmail.com>: > >>>>>> Damian Ivanov wrote: > >>>>>>> You can run a different logging daemon like syslog-ng no problem. > >>>>>>> Also > >>>>>>> journalctl which seems to be your problem can filer per application, > >>>>>>> time etc. everything and write to file. no problem. > >>>>>> > >>>>>> So, we're supposed to run TO loggin deamons now.... > >>>>>> > >>>>>> And this is an improvement how, exactly, Damian? > >>>>>> > >>>>>> Do you understand how absolutely idiotic that "solution" is? > >>>>>> > >>>>>> It's not a solution, it's a pollution. > >>>>>> > >>>>>>> 2014-06-02 9:19 GMT+02:00 Dirk Gently <dirk.gently00(a)gmail.com>: > >>>>>>>> Damian Ivanov wrote: > >>>>>>>>> Maybe on Kay Sievert, yes he is problematic (as personality in > >>>>>>>>> open > >>>>>>>>> source). systemd doesn't not do everything. Under the systemd > >>>>>>>>> umbrella > >>>>>>>>> are few additional daemons reimplenting a lot of services. If you > >>>>>>>>> build systemd with all configuration options enabled you will > >>>>>>>>> build > >>>>>>>>> 69 > >>>>>>>>> individual binaries. These binaries all serve different tasks, and > >>>>>>>>> are > >>>>>>>>> neatly separated for a number of reasons. At compile time you have > >>>>>>>>> a > >>>>>>>>> number of configure switches to select what you want to build, and > >>>>>>>>> what not. > >>>>>>>>> > >>>>>>>>> That developers code stuff that requires systemd is not systemd's > >>>>>>>>> fault. > >>>>>>>> > >>>>>>>> You don't konw that the fuck you're talking about. > >>>>>>>> > >>>>>>>> If the syslog deamon has been removed, then I can't sent logging > >>>>>>>> messages > >>>>>>>> to > >>>>>>>> a standard file handle which can (in the startup script) be sent to > >>>>>>>> the > >>>>>>>> syslog process. > >>>>>>>> > >>>>>>>> Instead, deamons NOW have to call a special logging function in > >>>>>>>> systemd > >>>>>>>> to > >>>>>>>> have anything logged. > >>>>>>>> > >>>>>>>> Thus, now the applications have to be aware of systemd... which > >>>>>>>> then > >>>>>>>> makes > >>>>>>>> systemd NON-REPLACEABLE. > >>>>>>>> > >>>>>>>> > >>>>>>>> haven't the past 30 years of Microsoft's machinations taught you > >>>>>>>> anything > >>>>>>>> about the inherent evilness of "embrace and extend" programming. > >>>>>>>> > >>>>>>>> Systemd is being designed to be a one-way trapdoor, so that, > >>>>>>>> if/when > >>>>>>>> people > >>>>>>>> realize that it's not all it's been sold as being (in fact, not > >>>>>>>> even > >>>>>>>> close) > >>>>>>>> then it will be impossible to replace it without ALSO rewriting > >>>>>>>> tons > >>>>>>>> of > >>>>>>>> other code in other projects. > >>>>>>>> > >>>>>>>> That reason alone makes it stupid for any distribution to adopt it. > >>>>>>>> > >>>>>>>>> You don't like GNOME? Use something else. You have a problem > >>>>>>>>> > >>>>>>>>> with systemd as init or with some of all the services under > >>>>>>>>> systemd's > >>>>>>>>> umbrella (logind etc.)? You could develop alternatives for these. > >>>>>>>>> You > >>>>>>>>> don't want to? You want other people to develop for YOUR personal > >>>>>>>>> preferences? This ain't gonna happen. And as upstart is dead from > >>>>>>>>> now > >>>>>>>>> on and openrc doesn't do the job, let's embrace systemd with all > >>>>>>>>> of > >>>>>>>>> our heart. > >>>>>>>> > >>>>>>>> -- > >>>>>>>> To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org > >>>>>>>> To contact the owner, e-mail: opensuse+owner(a)opensuse.org > >>>>>> > >>>>>> -- > >>>>>> To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org > >>>>>> To contact the owner, e-mail: opensuse+owner(a)opensuse.org -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

1 0

[opensuse] opensuse source file archives
by don fisher 13 Feb '15

13 Feb '15

Sorry for showing my age again, but when I used Red Hat there were FTP sites that contained all of the distribution RPMs and in another directory RPMs containing the source code for each package. I cannot find such a site for opensuse. They say the source is available, but where? Thanks, Don -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

5 4

Re: [opensuse] Re: Why is systemd[1] is mounting noauto partitions?
by ianseeks 12 Feb '15

12 Feb '15

On Wednesday 11 Feb 2015 10:43:32 Joe Zappa wrote: > ianseeks wrote: > > On Tuesday 03 Jun 2014 03:08:45 Dirk Gently wrote: > >> Damian Ivanov wrote: > >>> You have no idea. Not the slightest clue. You can't keep it technical. > >>> Fuck you Dirk Gently. > >> > >> 1. systemd doesn't produce ASCII (or for that matter, UTF) log files, it > >> produces binary blob log files. > >> > >> > >> Which means you can't just browse through a log file using grep, awk, > >> and/or more (or less). > > > > journalctl | grep xxx > > And why do you need to run journalctl instead of just grepping the file > directly??? how many files do you have to grep to trace the issue you are looking for? just configure it to use rsyslog if you want to increase your workload and grep multiple files. using journalctl will make your life easier and reduce the repetitive creating of using scripts to do your job > Because the log file is a binary blob which MUST BE INTERPRETED BY > JOURNALCTL. why do you use "grep" instead of editing the files manually? It makes life easier which is one of the uses of computers. How do you interpret MariaDB database files, do you grep them? > > or > > > > journalctl > /tmp/xxxx > > then do your stuff > > That doesn't change the fact that systemd violates on the major principles > of what has made Unix and now Linux so successful -- NO BINARY BLOBS FOR > HUMAN READABLE INFORMATION. if you go back in time far enough i'd expect you'll find using a GUI was violating the Unix principle of only using a cli. I heard many an argument about the GUI/cli offerings. Compromises are made all the time, have a read of this as an example http://www.johndcook.com/blog/2012/05/25/unix-doesnt-follow-the-unix-philos… an example of the benefit of journalctl. whats easier? create a script(s) that produces a single sorted output from all the log files for a specified date/time range of 07:37 to 08:29 and note the time it took to write it and debug it. or a single line journalctl --since 07:37 --until 08:29 > > >> 2. systemd eliminates separate log files... so if you're looking for ntp > >> messages, we no longer have ntp log files... now we have to wade through > >> the whole combined (binary only) logfile > > > > journalctl | grep ntp > > Once again, show us how to do it WITHOUTH journalctl. configure systemd to use rsyslog. > 1. What if your journalctl executable gets compromised? what if any executable on your system gets compromised? > 2. Why do we need this extra overhead every time we want > to look at a journal? What overhead? it'll save you loads of time if you have to a lot of searching of log files, its only 10 letters to type and no changing of directories. If 10 letters are too much to type, create an alias. > > The ntp log files exist on my opensuse 13.2 > > > >> 3. The old time tested method of keeping log files small and maneagble > >> (daily rotation) is now also broken, YATFUBSD (Yet Another Thing Fucked > >> Up > >> By SystemD) > > > > http://www.h-online.com/news/item/Latest-release-of-systemd-includes-time-> > based-log-rotation-1735258.html > So, in other words, after much harping by the community, Poettering, et al > have finally pulled their heads out of their asses on this ONE point.... that was a news article from 2012 which is quite early in systemd's development life cycle. Maybe you don't know but when developing software, it takes time and not all functions are ready on day one. > >> Obviously, you're either ignorant or making up more lies. Which is it? > > > > you are obviously out of date on info about systemd > > > >> Do you want to keep on playing this idiotic game where you make false > >> assertions, and I point out how the truth differs from what you say it > >> is? > > > > you wouldn't know the truth if it smacked you in the mouth > > > > Now go away and do some reading about systemd and find out what it really > > does > I've read a lot about it. > > >>> 2014-06-03 2:26 GMT+02:00 Dirk Gently <dirk.gently00(a)gmail.com>: > >>>> Damian Ivanov wrote: > >>>>> You can run a different logging daemon like syslog-ng no problem. Also > >>>>> journalctl which seems to be your problem can filer per application, > >>>>> time etc. everything and write to file. no problem. > >>>> > >>>> So, we're supposed to run TO loggin deamons now.... > >>>> > >>>> And this is an improvement how, exactly, Damian? > >>>> > >>>> Do you understand how absolutely idiotic that "solution" is? > >>>> > >>>> It's not a solution, it's a pollution. > >>>> > >>>>> 2014-06-02 9:19 GMT+02:00 Dirk Gently <dirk.gently00(a)gmail.com>: > >>>>>> Damian Ivanov wrote: > >>>>>>> Maybe on Kay Sievert, yes he is problematic (as personality in open > >>>>>>> source). systemd doesn't not do everything. Under the systemd > >>>>>>> umbrella > >>>>>>> are few additional daemons reimplenting a lot of services. If you > >>>>>>> build systemd with all configuration options enabled you will build > >>>>>>> 69 > >>>>>>> individual binaries. These binaries all serve different tasks, and > >>>>>>> are > >>>>>>> neatly separated for a number of reasons. At compile time you have a > >>>>>>> number of configure switches to select what you want to build, and > >>>>>>> what not. > >>>>>>> > >>>>>>> That developers code stuff that requires systemd is not systemd's > >>>>>>> fault. > >>>>>> > >>>>>> You don't konw that the fuck you're talking about. > >>>>>> > >>>>>> If the syslog deamon has been removed, then I can't sent logging > >>>>>> messages > >>>>>> to > >>>>>> a standard file handle which can (in the startup script) be sent to > >>>>>> the > >>>>>> syslog process. > >>>>>> > >>>>>> Instead, deamons NOW have to call a special logging function in > >>>>>> systemd > >>>>>> to > >>>>>> have anything logged. > >>>>>> > >>>>>> Thus, now the applications have to be aware of systemd... which then > >>>>>> makes > >>>>>> systemd NON-REPLACEABLE. > >>>>>> > >>>>>> > >>>>>> haven't the past 30 years of Microsoft's machinations taught you > >>>>>> anything > >>>>>> about the inherent evilness of "embrace and extend" programming. > >>>>>> > >>>>>> Systemd is being designed to be a one-way trapdoor, so that, if/when > >>>>>> people > >>>>>> realize that it's not all it's been sold as being (in fact, not even > >>>>>> close) > >>>>>> then it will be impossible to replace it without ALSO rewriting tons > >>>>>> of > >>>>>> other code in other projects. > >>>>>> > >>>>>> That reason alone makes it stupid for any distribution to adopt it. > >>>>>> > >>>>>>> You don't like GNOME? Use something else. You have a problem > >>>>>>> > >>>>>>> with systemd as init or with some of all the services under > >>>>>>> systemd's > >>>>>>> umbrella (logind etc.)? You could develop alternatives for these. > >>>>>>> You > >>>>>>> don't want to? You want other people to develop for YOUR personal > >>>>>>> preferences? This ain't gonna happen. And as upstart is dead from > >>>>>>> now > >>>>>>> on and openrc doesn't do the job, let's embrace systemd with all of > >>>>>>> our heart. > >>>>>> > >>>>>> -- > >>>>>> To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org > >>>>>> To contact the owner, e-mail: opensuse+owner(a)opensuse.org > >>>> > >>>> -- > >>>> To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org > >>>> To contact the owner, e-mail: opensuse+owner(a)opensuse.org -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

3 2

[opensuse] Hibernate broken since yesterday
by Aaron Digulla 12 Feb '15

12 Feb '15

Hi, I installed a bunch of patches and updated packages yesterday. I could hibernate yesterday evening but couldn't resume (Linux would just boot normally). When I now try to hibernate, nothing happens. I tried (as root): # /usr/bin/powersave --suspend-to-disk Error org.freedesktop.DBus.Error.UnknownMethod: Method "Hibernate" with signature "" on interface "org.freedesktop.UPower" doesn't exist I also tried (as root) # /usr/sbin/pm-hibernate which doesn't do anything anymore. That worked yesterday. # rpm -qi pm-utils-1.4.1-38.4.1.x86_64 Name : pm-utils Version : 1.4.1 Release : 38.4.1 Architecture: x86_64 Install Date: Sa 06 Dez 2014 00:20:48 CET Package hasn't changed, though. Using the button in my KDE start menu locks the screen and then displays a dialog "Legitimierung ist zum Aktivieren des Ruhezustands des Systems notwendig, während andere Benutzer angemeldet sind" (English: Give me root password to suspend while other users are logged in). Action: "Hibernate the system while other users are logged in" Vendor: The systemd Project The action is a link. When I hover over it, it says "Click to edit org.freedesktop.login1.hibernate-multiple-sessions" Clicking doesn't do anything. But grepping in /etc eventually pointed me to /etc/polkit-default-privs.local where I added this line: org.freedesktop.login1.hibernate-multiple-sessions auth_self:auth_self:yes I then looked into /var/log/pm-suspend.log: Running hook /usr/lib/pm-utils/sleep.d/30s2disk-check hibernate hibernate: INFO: checking for suspend-to-disk prerequisites... ERROR: no resume parameter on kernel commandline, can not suspend WARNING: /var/run/pm-utils/pm-suspend/storage/inhibit will be created to prevent suspending! Yast says: resume=/dev/sda2 splash=verbose quiet showopts elevator=cfq console=tty0 plymouth.enable=0 I also see these values in grub.cfg and they look right to me. Any ideas? How can I see the current init parameters of the kernel? Regards, -- Aaron "Optimizer" Digulla a.k.a. Philmann Dark "It's not the universe that's limited, it's our imagination. Follow me and I'll show you something beyond the limits." http://blog.pdark.de/ -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

8 25

[opensuse] newbee question on root password
by don fisher 11 Feb '15

11 Feb '15

I am trying to leave a Fedora environment and am having problems with the root and user password. I did a 13.2 install from the DVD, leaving the mark highlighted that indicated that the user and root password would be the same (I think). When I tried to su to root, it said the password was invalid. When I logged of, it also said that the user password was now invalid. As I recall, it worked the first time I booted the system. I used a short password that the system said was not safe, but I did not care at this time. I looked at the /etc/password file from another system and there was no entry for root at all! I there a way to mount the system using the rescue boot option so that I can change my user password back? And how do I get root back? I have never had to do an adduser root. Did the system get angry at my short passwords and just ignore them? I would have expected the installation to halt if it could not generate a root account. I assume opensuse does have a root account? Don -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

7 11

[opensuse] enumerate card reader after HDs (restore sda & sdb to HDs)?
by Felix Miata 11 Feb '15

11 Feb '15

Apparently I'm not Googling the correct terms to find an answer to this. On this system I have had an internal all-in-1 USB device reader since I first built the box. 11.0 was the first installed on it, followed by 11.2, 11.4, 13.1, 13.2 & TW. In all of 11.0-13.1, HDs have been sda & sdb. 13.2 & TW make them sde & sdf, reserving a-d for USB devices. I have similar internal readers in other installations of 13.1, 13.2 & TW that automatically put the HDs on sda or sda & sdb. Is there something I can exclude from the initrd or add to grub stanza to force HDs to be assigned device names before USB storage in 13.2 & TW? BrokenModules=usb_storage maybe? Something else? -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

3 6

Re: [opensuse] RE: Bug Report Zebra 2.0.60 in favour of Zebra 2.0.59 (package idzebra-2.0)
by Greg Freemyer 10 Feb '15

10 Feb '15

On Tue, Feb 10, 2015 at 5:53 PM, David Cook <dcook(a)prosentient.com.au> wrote: > Thanks for the info, Greg! > > Bjørn Lie got in touch with me yesterday and was very helpful as well. He > gave me the name of the package maintainer, provided a link to a Zebra > update he’d already prepared (I think he’d done updates for Zebra in the > past as well), and encouraged me to report the bug! > > At this point, the package maintainer (Karl Eichwalder) has accepted the > update request, and forwarded it on to maintenance! I’m not 100% sure where > things go from now… I imagine QA then inclusion in a maintenance release of > some kind, so that’s a really positive outcome. > > I didn’t realize that my Bugzilla login would work at build.opensuse.org as > well, so that’s good to know! Maybe I’ll contribute more down the road if > anything comes up! There are several different openSUSE websites that all use the same login credentials. Once you create an account you have access to all of the various sites. In my opinion build.opensuse.org is one of the jewels of openSUSE. It is worth exploring, even if you don't contribute. It is where openSUSE comes from. 100% of the distro is built there and you can see most of the details without even logging in. Once you login, you get to start doing more than just look. Greg -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

1 0