November 2014 - openSUSE Users - openSUSE Mailing Lists

[opensuse] Btrfs: Error Upon Installation
by Sam M. 10 Nov '14

10 Nov '14

Hi, I installed btrfs over an EXT4 operating system partition (/), and I got a strange error message. The options the dialogue box gave pertaining to the error were Continue and Abort. I clicked Continue, and then I got a lengthy error message about a problem creating initrd. I clicked continue or ignore (I forget), and if I recall correctly the installation finished. I think when I rebooted the system, all I got was a black grub screen with a flashing cursor. Has anyone else gotten this? I installed btrfs on another test laptop and there were no problems. The drive I'm using has no bad sectors and passes SMART, so I don't think it's that. Here is the error message: "Failure occured during the following action: Formatting partition /dev/sda3 (20.00 GiB) with btrfs System error code was: -3043 /bin/mount -t btrfs -o subvolid=0,acl,user_xattr '/dev/sda3' '/tmp/libstorage-CDkTv4/tmp-mp-MB9Er9': mount: wrong fs type, bad option, bad superblock on /dev/sda3, missing codepage or helper program, or other error In some cases useful info is found in syslog - try ... Continue despite the error" -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

4 8

[opensuse] printing colored pdf in grayscale or black and white
by Istvan Gabor 10 Nov '14

10 Nov '14

Hello: I have a pdf file with colored graphics but I have only a black and white printer. When printing the file the colored parts are almost invisibly pale. I would like to print the file in grayscale or black and white so that the colored parts would be visible. I have openSUSE 12.2 with KDE 3, and adobe reader 9 and kpdf. I could not find option to print in grayscale or black and white in either one. I remember that windows adobe reader has such option. How could I print the file in black and white in openSUSE? Thanks, Istvan -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

3 5

[opensuse] Fresh 13.2 install fail - two problems - help please
by listreader 10 Nov '14

10 Nov '14

Howdy... :~> uname -a Linux msbmainhp.site 3.11.10-21-desktop #1 SMP PREEMPT Mon Jul 21 15:28:46 UTC 2014 (9a9565d) x86_64 x86_64 x86_64 GNU/Linux Tried to do an install of 13.2 from DVD and I had a fail. I did a new/fresh install as I wanted to try the new brtfs/xfs default file systems. Problem #1: Install procedure almost completed but failed when it tried to install the bootloader. The pop-up box message was: "An error occurred during boot loader installation. Retry boot loader configuration? Yes No" I played around with the configuration, changed the bootloader location from MBR where it had defaulted to and moved it to the Extended Partition (where my current 13.1 bootloader resides), tried setting the Active Flag (it was not already set), tried Write generic Boot Code to MBR (it was not already set), etc., but no go, same message. So then I just answered NO and the install finished, system rebooted, and my old 13.1 bootloader appeared. All my various existing OS boots were there but no 13.2 option. Problem #2: I booted into 13.1 and looked at the new 13.2 brtfs and xfs partitions. The brtfs looks fine, or at least I can browse what's in there. The xfs partition, though, appears broken. I had LUKS encrypted it during the install/format process but when I try to mount I get the familiar bad old message about: "Error mounting /dev/dm-2 at /run/media/(..snip..): Command-line `mount -t "xfs" -o "uhelper=udisks2,nodev,nosuid" "/dev/dm-2" "/run/media/(..snip..)"' exited with non-zero exit status 32: mount: wrong fs type, bad option, bad superblock on /dev/mapper/luks-5fd1dd43-e7fc-(..snip..), missing codepage or helper program, or other error" dmesg shows this additional interesting info: [ 2227.799239] XFS (dm-2): Version 5 superblock detected. This kernel has EXPERIMENTAL support enabled! Use of these features in this kernel is at your own risk! [ 2227.799246] XFS (dm-2): Superblock has unknown incompatible features (0x1) enabled. Filesystem can not be safely mounted by this kernel. I tried "xfs_repair -n" (from 13.1) on all 3 possiblities: the normal device (/dev/sdb8), the dm device number shown in the above message (dm-2), and the mapper device also in the above message (/dev/mapper/luks-5fd1dd43-e7fc-(..snip..) but it just goes off hunting endlessly for an alternate superblock. Any ideas, anyone? Keep it simple as I'm just a simple user. Thanks in advance! Ralph -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

9 41

Re: [opensuse] aaron won't go away
by Anton Aylward 10 Nov '14

10 Nov '14

On 11/09/2014 09:39 PM, Joe Zappa wrote: > > But now you've just said that it's dependent upon whether he's running > a version which is systemd-aware, or not. > > > So, which is it? > > ...same old pattern of fucking lies out of the systemd camp. We are all aware. Aaron, that you had your sense of humour surgically removed before birth, but why that should induce Tourette's Syndrome I don't know. Lets put it very plainly: * if it wasn't started by systemd then its not going to be stopped by systemd * if its created explicitly not to be managed by systemd then its not going to be stopped or started by systemd This is not a systemd problem. It is a mis-information problem, Ruben failed to tell us, up front, that he had his onw custom compiled version that was called httpd rather than Apache2, which he had started without systemd. You, aaron, are just adding to the confusion and tying to play this as a systemd problem when systemd had nothing to do with it. Your attitude makes me wonder if a lack of sense of humour somehow impacts the ability to listen and reason. -- A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting frowned upon? -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

1 0

Re: [opensuse] httpd won't go away
by Anton Aylward 10 Nov '14

10 Nov '14

On 11/09/2014 07:27 PM, Joe Zappa wrote: > Anton Aylward wrote: >> On 11/09/2014 08:50 AM, Ruben Safir wrote: >>> Actually, I have my own compliled package so it is called httpd and it >>> lives in /usr/local/apache and under /sbin/apachectl and it is called >>> httpd >> >> Ah, you didn't mention this before. >> Since you choose to do this and since you choose not to have it managed >> by systemd, then arguing that systemd didn't tell you anything about it >> seems pointless. >> >> If you do something that doesn't correspond to the way the rest of us >> run Apache but don't tell us that up front, then of course the advice we >> give won't work. >> >> But in this circumstance you have no reason to blame systemd; you chose >> to run your "own compiled" version outside of systemd. >> > > > Why in the FUCK should systemd care about which version of apache he's > running? > > Explain this Anton. It has nothing to do with the version. I don't know why you think that. -- A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting frowned upon? -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

1 0

[opensuse] Strange syslogd message
by Robert Rea 08 Nov '14

08 Nov '14

This popped up. What does it mean and how should I deal with it? 2014-11-07T16:51:27.936324-05:00 gandalf kernel: [ 8571.877863] Uhhuh. NMI received for unknown reason 21 on CPU 1. 2014-11-07T16:51:27.936387-05:00 gandalf kernel: [ 8571.877878] Do you have a strange power saving mode enabled? 2014-11-07T16:51:27.936393-05:00 gandalf kernel: [ 8571.877884] Dazed and confused, but trying to continue Possible clue: I haver humoungous online lag, 1.5 sec at the moment, often above 2 sec. -- Bob Rea mailto:gapetard@stsams.org http://www.petard.us http://www.petard.us/blog http://www.petard.us/gallery America, it was a wonderful country until they took it private and turned it into a theme park of itself -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

4 5

[opensuse] Backup Options?
by Lew Wolfgang 08 Nov '14

08 Nov '14

Hi Folks, Does anyone have any suggestions for automated backups of heterogeneous desktops these days? I've been using rdiff-backup for many years for Linux clients, but now have a requirement to add Windows 7 to the mix. Years ago I used Samba's smbclient to copy shared Windows XP directories to a central Linux box under cron control, but I'm not sure that's the best way for incremental backups and it might not even work any more. Any suggestions/ideas? Bacula? Thanks, Lew -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

6 14

Re: [opensuse] NetworkManager not starting after upgrade on tumbleweed
by Cristian Rodríguez 08 Nov '14

08 Nov '14

El 08/11/14 a las 11:38, Tom Desmet escribió: > Thanks for your reply. Hereby the list .... > > # | Alias | Name > | Enabled | Refresh | URI > --+----------------------------------+----------------------------------+---------+---------+------------------------------------------------------------------------- > 1 | google-chrome | google-chrome > | Yes | Yes | > http://dl.google.com/linux/chrome/rpm/stable/x86_64 > 2 | openSUSE:Stable_OSS | openSUSE:Stable_OSS > | Yes | Yes | > http://download.opensuse.org/distribution/openSUSE-current/repo/oss/ > 3 | openSUSE:Stable_Updates | openSUSE:Stable_Updates > | Yes | Yes | > http://download.opensuse.org/update/openSUSE-current/ > 4 | openSUSE:Stable_non-OSS | openSUSE:Stable_non-OSS > | Yes | Yes | > http://download.opensuse.org/distribution/openSUSE-current/repo/non-oss/ > 5 | openSUSE:Stable_non-OSS__Updates | > openSUSE:Stable_non-OSS__Updates | Yes | Yes | > http://download.opensuse.org/update/openSUSE-non-oss-current/ > 6 | openSUSE:Tumbleweed | openSUSE:Tumbleweed > | Yes | Yes | > http://download.opensuse.org/repositories/openSUSE:/Tumbleweed/standard/ There are two things here: The first issue is that your repositories are mixed up.. tumbleweed is now the same as factory, a rolling release. but you have openSUSE-current repos which is the latest stable release. remove them all except the chrome one and follow the steps outlined in https://en.opensuse.org/openSUSE:Tumbleweed_installation section "repositories" and "running the upgrade" The second issue is that NetworkManager must hard-require a version greater or equal of dbus-glib than the version used for build, so you never end in this kerfuffle in the first place. -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

1 0

[opensuse] NetworkManager not starting after upgrade on tumbleweed
by Tom Desmet 08 Nov '14

08 Nov '14

Hi all, After doing an upgrade today, networkmanager isn't starting any more. The error I have when issuing a "systemctl -l status NetworkManager.service" is at the bottom. I would suspect that this is related to a wrong version of dbus-1-glib. My current version is "dbus-1-glib-0.102-2.1.3.x86_ 64". Anyone having any ideas/suggestions. Thanks for any reply! NetworkManager.service - Network Manager Loaded: loaded (/usr/lib/systemd/system/NetworkManager.service; enabled) Active: failed (Result: exit-code) since Sat 2014-11-08 07:29:43 CET; 9min ago Process: 1717 ExecStart=/usr/sbin/NetworkManager --no-daemon (code=exited, status=127) Main PID: 1717 (code=exited, status=127) Nov 08 07:29:43 centrino NetworkManager[1717]: <info> NetworkManager (version 0.9.10.0) is starting... Nov 08 07:29:43 centrino NetworkManager[1717]: <info> Read config: /etc/NetworkManager/NetworkManager.conf Nov 08 07:29:43 centrino NetworkManager[1717]: <info> WEXT support is enabled Nov 08 07:29:43 centrino NetworkManager[1717]: <info> VPN: loaded org.freedesktop.NetworkManager.pptp Nov 08 07:29:43 centrino NetworkManager[1717]: <info> VPN: loaded org.freedesktop.NetworkManager.openvpn Nov 08 07:29:43 centrino NetworkManager[1717]: <info> VPN: loaded org.freedesktop.NetworkManager.vpnc Nov 08 07:29:43 centrino NetworkManager[1717]: /usr/sbin/NetworkManager: symbol lookup error: /usr/lib64/libdbus-glib-1.so.2: undefined symbol: g_type_check_instance_is_fundamentally_a -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

2 1

[opensuse] Has some one tried bcache in openSUSE, and reported it?
by Carlos E. R. 07 Nov '14

07 Nov '14

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, bcache is like a huge hd disk cache residing in a flash disk. <http://en.wikipedia.org/wiki/Bcache> +++······································ bcache is a Linux kernel's block layer cache (hence the name, block cache), developed by Kent Overstreet. It allows one or more fast storage devices such as flash-based solid-state drives (SSDs) to act as a cache for one or more slower hard disk drives, effectively creating hybrid volumes. It is designed around the performance characteristics of SSDs, minimizing write amplification by never performing random writes and by turning them into sequential writes instead – for both the cache and the primary storage. That helps in extending the lifetime of flash-based devices used as caches, and also improves performance of write-sensitive primary storages, like RAID 5. ······································++- Has some one tried it in openSUSE? Do you know of some document? I tried searching our site, but search is broken: <https://en.opensuse.org/Special:Search?search=bcache> : An error has occurred while searching: Error fetching URL: couldn't connect to host - -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iEYEARECAAYFAlRObZMACgkQtTMYHG2NR9W9RwCfaH62rgX7E4242QgdcCUfzJ2S 5pkAn0xcQ+sImwzrv2ghiBO9Fm+aEu1d =9iaR -----END PGP SIGNATURE-----

7 10

Re: [opensuse] Re: rm broken by POSIX
by Linda Walsh 07 Nov '14

07 Nov '14

Joe Zappa wrote: > Linda Walsh wrote: >> Joe Zappa wrote: >>> Linda Walsh wrote: >>>> Used to be rm -fr dir/. was the safest way to clean out a directory, >>>> *w/o* >>>> deleting the directory. I used it all the time to delete >>>> tmp dir contents (not usually '/tmp', but others). Now, there is no >>>> easy way. You need to use some incarnation of 'find', with >>>> >>>> find / -delete >>>> find /tmp/. delete >>>> >>>> replacing the previous rm based "solutions". >>>> >>>> Neat thing about find / -delete, is that it *seems* (not >>>> going to test it here!) to have no protections -- unlike >>>> "rm -fr /" where you had to specify some arg to override >>>> the default. >>>> >>> >>> >>> This is why I like Linda... she's a true hacker (by the pre-1985 >>> definition) >> ---- >> >> *blink*. >> >> ?? What happened in 1985? War Games? > > > That's about the time the (ignorant as usual) press started making > the wrongful equivocation between hacking and criminal conduct. > > >> >> You shoulda seen rumors fly when my employer found out I coded up >> a remote shell & file server in my office to download all of Intel's >> SW to my home PC -- all paid for, of course, since Intel only charged >> disk duplication fees for employees to obtain a copy on 8" floppies, >> which were generally worthless on 1st generation 8088-based PC's, but >> as I worked on the compiler back end -- writing an adapter / shell to >> make their PL/M compiler and linker work on that PC was fairly trivial >> (circa 82-83). > > Wow. It's amazing that anybody in the industry would be amazed at > a programmer writing such trivial stuff. --- There was nothing on the PC at the time to support SW development. The stuff I coded up on the PC end that did the file download modem handling was written using the ROM BASIC BIOS code until I could bootstrap the utils to allow running the devel code native. Writing things like that on computers at school was less of a problem, but at the time, at Intel, the only shell ran on ISIS on the 8080/8085 -- all 8086 work used a daughterboard in an 8085-based "workstation", so that I had the x86 devel tools running natively on the PC was initially, surprising (old hat not long afterward, but the PC's were so new, that Intel helped out with an employee purchase program)... > > > I had to write such sorts of software as weekly assignments for > 1-credit-hour lab classes which used 8080- or 6809-based machines. --- The microcomputer lab at my school went from using 80k floppies to 1M in just a few years around then.. things were moving pretty fast. > > I had one project for senior-level design project, instead of using > the 6809 machines, decided to use a 68HC11... so, the first order of > business was to write up a 6811 assembler... which took me all of a > couple hours. [By that time, I had already had to write an assembler > in both a CS class and a EE class... so by that time, it was old hat] --- Yeah.. they had the 300/400-level students writing 'COMPASS' assembly and debugger environments for use by the 200 level students about 2-3 years after we new CDC (Control Data) mainframes (Uof.Illinois). -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

1 0

Re: [opensuse] Re: rm broken by POSIX
by Linda Walsh 07 Nov '14

07 Nov '14

Joe Zappa wrote: > Linda Walsh wrote: >> Used to be rm -fr dir/. was the safest way to clean out a directory, >> *w/o* >> deleting the directory. I used it all the time to delete >> tmp dir contents (not usually '/tmp', but others). Now, there is no >> easy way. You need to use some incarnation of 'find', with >> >> find / -delete >> find /tmp/. delete >> >> replacing the previous rm based "solutions". >> >> Neat thing about find / -delete, is that it *seems* (not >> going to test it here!) to have no protections -- unlike >> "rm -fr /" where you had to specify some arg to override >> the default. >> > > > This is why I like Linda... she's a true hacker (by the pre-1985 > definition) ---- *blink*. ?? What happened in 1985? War Games? You shoulda seen rumors fly when my employer found out I coded up a remote shell & file server in my office to download all of Intel's SW to my home PC -- all paid for, of course, since Intel only charged disk duplication fees for employees to obtain a copy on 8" floppies, which were generally worthless on 1st generation 8088-based PC's, but as I worked on the compiler back end -- writing an adapter / shell to make their PL/M compiler and linker work on that PC was fairly trivial (circa 82-83). ...thanks? I think?... ;-) -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

1 0

[opensuse] rdesktop broken in 13.1?
by David C. Rankin 07 Nov '14

07 Nov '14

All, I have used rdesktop for ages to connect to various remote computers/VM's (Win, VBox (headless), etc..). Attempting to connect on 13.1 fails -- I get nothing but a black (blank) window (with what looks like the remote OS cursor). The only console output is: rdesktop-1.8.2-63.1.x86_64: NOT IMPLEMENTED: PDU 12 NOT IMPLEMENTED: PDU 8 NOT IMPLEMENTED: PDU 12 NOT IMPLEMENTED: PDU 8 NOT IMPLEMENTED: PDU 12 rdesktop-1.8.2-74.1.x86_64: NOT IMPLEMENTED: PDU 9 My command line hasn't changed: rdesktop somehost.somedomain.tld -u me -g 1280x800 -E -x b & Anybody have any ideas why rdesktop isn't working anymore. (It has been rock solid for the past decade) -- 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] 13.1 to 13.2 upgrade failure
by lynn 07 Nov '14

07 Nov '14

Downloaded (79Mb) network iso and sent to USB. Boots OK. Choose upgrade. Dumps me at linuxrc: 'Make sure the installation medium is available'. Retry? OWTTE. And I have to abort. Is the network upgrade possible? Thanks, L x -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

4 11

[opensuse] 13.2 Upgrade issue
by Marco Calistri 07 Nov '14

07 Nov '14

Hello, I have just upgraded my 13.1 to 13.2 by "zypper dup" following the instructions. Rebooting stops to very early stage of grub. I then used an older DVD of openSUSE to boot my system and login into 13.2, I could verify via Yast Boot options which it is still reporting "13.1" as the new grub2 went not saved on disk. Wonder how I can recover this issue. Beside this I can use only XFCE, Gnome both Classic and Standard are not working at all. Thanks, -- Marco Calistri opensuse 13.1 (Bottle) 64 bit - Kernel 3.16.2-1.gdcee397-default Gnome 3.12.2 Intel® Core™ i5-2410M CPU @ 2.30GHz × 4 - Intel® Sandybridge Mobile -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

7 11

Re: [opensuse] Btrfs.. Whats the difference
by Anton Aylward 07 Nov '14

07 Nov '14

On 11/06/2014 11:08 AM, Joe Zappa wrote: >> > > > So something *cough* *cough* systemd *cough* is remounting root > filesystems as readonly. > > You've known about that for how long? > > And you continue to defend that pile of crap. No this has nothing to do with systemd in particular. I had it happen before systemd. Come to think about it, I recall having it happen back in the days I used SCO UNIX. In fact I've not had it happen to me since I started using systemd. -- The computing field is always in need of new cliches. Alan Perlis -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

3 3

Re: [opensuse] Btrfs.. Whats the difference
by John Andersen 07 Nov '14

07 Nov '14

On 11/06/2014 09:10 PM, Joe Zappa wrote: > And if you have multiple disks??? It still does only one write at a time. If you have multiple disks one core is STILL more than enough to handle the load. Remember this is only carls assertion that Reiserfs can't possibly handle multiple disks, because its all single thread in a single core of a single processor. Yet systems with dozens of disks work just fine with Reiserfs. In fact I've raid on riserfs partitions on 4 drives with zero performance problems. -- After all is said and done, more is said than done. -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

3 3

[opensuse] Updating VMware Workstation 10
by Koenraad Lelong 07 Nov '14

07 Nov '14

Hi, I have VMworkstation 10.0.2. I'm trying to update it to the latest version (10.0.4), but it seems not to work. Via the Workstation GIU it just hangs, via the command-line I can't get past the license. The same happens with 10.0.3. Command-line-output (for 10.0.3, but it's the same for 10.0.4) : ./VMware-Workstation-Full-10.0.3-1895310.x86_64.bundle Extracting VMware Installer...done. You must accept the VMware OVF Tool component for Linux End User License Agreement to continue. Press Enter to proceed. Do you agree? [yes/no]: y You must accept the VMware Workstation End User License Agreement to continue. Press Enter to proceed. I tried inputting "yes", but it's the same. Anyone can give comments ? TIA, Koenraad Lelong. P.S. Just looked in /var/log/vmware-installer : [2014-11-07 09:04:12,968] Top level exception handler Traceback (most recent call last): File "/usr/lib/vmware-installer/2.1.0/vmis/core/transaction.py", line 414, in RunThreadedTransaction txn.Run() File "/usr/lib/vmware-installer/2.1.0/vmis/core/transaction.py", line 76, in Run self.get()() File "/usr/lib/vmware-installer/2.1.0/vmis/ui/console.py", line 49, in Show answer = txn.ui.ShowEULA(eula.text, eula.componentName) File "/usr/lib/vmware-installer/2.1.0/vmis/ui/console.py", line 384, in ShowEULA Popen(self._getMoreBin(), stdin=PIPE).communicate(input=text) File "/usr/lib/vmware-installer/2.1.0/python/lib/subprocess.py", line 642, in communicate self.stdin.write(input) UnicodeEncodeError: 'ascii' codec can't encode character u'\u201c' in position 424: ordinal not in range(128) [2014-11-07 09:04:14,051] destination /tmp/tmpgPGfTF/.installer/10.0.3/include/systemType.py already exists, overwriting. [2014-11-07 09:04:14,052] destination /tmp/tmpgPGfTF/.installer/10.0.3/include/update.py already exists, overwriting. [2014-11-07 09:04:14,053] destination /tmp/tmpgPGfTF/.installer/10.0.3/__init__.py already exists, overwriting. [2014-11-07 09:04:14,054] destination /tmp/tmpgPGfTF/.installer/10.0.3/include/initscript.py already exists, overwriting. [2014-11-07 09:04:14,056] destination /tmp/tmpgPGfTF/.installer/10.0.3/vmware-workstation.py already exists, overwriting. [2014-11-07 09:04:14,057] destination /tmp/tmpgPGfTF/.installer/10.0.3/include/versions.py already exists, overwriting. UnicodeEncodeError : is this the problem ? I don't understand why though. -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

2 3

[opensuse] openSUSE 13.2 and nvidia Quadro FX 560?
by John Young 07 Nov '14

07 Nov '14

I have an old Sun Ultra-20 with an nVidia Quadro FX 560 graphics card. I just upgraded to openSUSE 13.2 yesterday and now I cannot get my dual monitors to work properly. The website https://en.opensuse.org/SDB:NVIDIA_drivers says that drivers for the GeForce FX cards are available for openSUSE 13.1 and older only. Has anyone gotten the nouveau driver working with dual monitors and openSUSE 13.2 on an nvidia Quadro FX or do I have to figure out how to drop back to openSUSE 13.1? -- JY ------------------------------------------------------------ John E. Young NASA LaRC B1148/R226 Analytical Services and Materials, Inc. (757) 864-8659 'All ideas and opinions expressed in this communication are those of the author alone and do not necessarily reflect the ideas and opinions of anyone else.' -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

3 2

[opensuse] Btrfs.. Whats the difference
by John Andersen 07 Nov '14

07 Nov '14

While installing 13.2 I let it use btrfs for root and xfs for /home partition. Then you get these nebulous message that says some of the subvolumes of root are shadowed by other filesystems. That message means that you have a subvolume named /home defined in the /root automatically, and also a /home partition. Better language is needed for that error message. The term "Duplicate directory" names comes to mind. "Shadowed" is not very descriptive. But then I began to wonder why btrfs defines subvolumes instead of letting the system define sub-directories? Whats the difference in functionality? Are these sub-volume sizes fixed? Is it just part of the snapshot process? What's up with that? -- _____________________________________ ---This space for rent--- -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

14 35

[opensuse] How to stop systemd automounting umounted devices?
by Ruediger Meier 07 Nov '14

07 Nov '14

Hi, just noticed that systemd automatically mounts devices again allthough I've manually umounted them. Here is what I did $ mount | grep local /dev/mapper/vg0-local on /mnt/local type ext4 (rw,relatime,data=ordered) ## umount and disable that lvm device $ umount /mnt/local $ lvchange -an vg0/local systemd[1]: Stopping File System Check on /dev/vg0/local... systemd[1]: Stopped File System Check on /dev/vg0/local. ## enable device again $ lvchange -ay vg0/local systemd[1]: Found device /dev/mapper/vg0-local. systemd[1]: Found device /dev/disk/by-uuid/177a415d-174d-4c30-8897-5502c0419ef8. systemd[1]: Found device /dev/disk/by-id/dm-uuid-LVM-uF33oY4c9yu00EPAP42a8A2XZCfQTRRPGfiv0cNZRwPKIRJnOboscsc1z60174dd. systemd[1]: Found device /dev/disk/by-id/dm-name-vg0-local. systemd[1]: Found device /dev/dm-0. systemd[1]: Found device /sys/devices/virtual/block/dm-0. systemd[1]: Starting File System Check on /dev/vg0/local... systemd-fsck[6386]: /dev/mapper/vg0-local: clean, 648240/3276800 files, 9308645/13107200 blocks systemd[1]: Started File System Check on /dev/vg0/local. systemd[1]: Mounting /mnt/local... kernel: [ 5542.579700] EXT4-fs (dm-0): mounted filesystem with ordered data mode. Opts: acl,user_xattr systemd[1]: Mounted /mnt/local. $ mount | grep local /dev/mapper/vg0-local on /mnt/local type ext4 (rw,relatime,data=ordered) So what kind of automount is this? How to disable this odd behaviour? Is this a known bug? cu, Rudi -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

18 66

[opensuse] Live USB - persistent file system?
by James Knott 06 Nov '14

06 Nov '14

I just created a Live USB of 32 bit 13.2. According to the instructions, I should be able to create a persistent file system. I entered the command "kiwi_hybridpersistent=yes" on the boot prompt as describe. However, I don't see any evidence of that file system. It doesn't show in Yast Partitioner and I don't see that command anywhere in the boot loader settings. What am I missing? tnx jk http://en.opensuse.org/Live_USB_stick#Live_USB_stick_with_persistent_file_s… -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

2 2

Re: [opensuse] 13.2 installation nvidia problem
by Mark Hounschell 06 Nov '14

06 Nov '14

On 11/06/2014 01:41 PM, Mark Hounschell wrote: > After installing the nvidia driver kde will no longer start. The Xorg log file shows nothing wrong but /var/log/kdm.log shows. > > X.Org X Server 1.16.1 > Release Date: 2014-09-21 > X Protocol Version 11, Revision 0 > Build Operating System: openSUSE SUSE LINUX > Current Operating System: Linux harley 3.16.6-2-desktop #1 SMP PREEMPT Mon Oct 20 13:47:22 UTC 2014 (feb42ea) x86_64 > Kernel command line: BOOT_IMAGE=/vmlinuz-3.16.6-2-desktop root=UUID=dce2f85b-899e-4d21-b79d-698c78fe0886 resume=/dev/disk/by-id/ata-ST3160815AS_6RACD7A6-part2 splash=silent quiet showopts nomodeset > Build Date: 08 October 2014 05:49:10PM > > Current version of pixman: 0.32.6 > Before reporting problems, check http://wiki.x.org > to make sure that you have the latest version. > Markers: (--) probed, (**) from config file, (==) default setting, > (++) from command line, (!!) notice, (II) informational, > (WW) warning, (EE) error, (NI) not implemented, (??) unknown. > (==) Log file: "/var/log/Xorg.0.log", Time: Thu Nov 6 09:35:29 2014 > (==) Using config file: "/etc/X11/xorg.conf" > (==) Using config directory: "/etc/X11/xorg.conf.d" > (==) Using system config directory "/usr/share/X11/xorg.conf.d" > /usr/bin/Xorg: symbol lookup error: /usr/lib64/xorg/modules/extensions/libglx.so: undefined symbol: LoadExtension > > The card is: > > 01:00.0 VGA compatible controller: NVIDIA Corporation G70 [GeForce 7800 GT] (rev a1) > > The nvidia packages were the 304-121 versions. > > Seems like a bug to me. Anyone else? > > Thanks > Mark > It appears to be already reported as Bug 904048. It looks like, but not sure, that the new 304-123 versions may fix it? They are not in the repo to try yet though. Mark -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

1 0

[opensuse] libqdialogsolver
by John Andersen 06 Nov '14

06 Nov '14

In yast, if you right click on any installed package and select show solver information you get a pop up saying libqdialogsolver is required for this feature. But libqdialogsolver is not on the system, and if you chekc RPM Requires on a search for libqdialogsolver nothing shows up. But if you check RPM Provides, and search it is said to be in the base package for openSuse Release, yet it id not in the file list. -- Explain again the part about rm -rf / -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

1 1

[opensuse] Midnight Commander unable to delete files : Solution found
by ellanios82 06 Nov '14

06 Nov '14

Hello List , - after rsync had errors, i see that i have a directory which has accumulated files : owned by root.root size : 0 Mode : 0000 "cannot access 648527.ldb: Input/output error" ............. - as root , seems impossible to force deletion - any ideas please how to get rid of these files ? ............... Solved :)) - by running : # fsck.ext4 -f /dev/sdXX ........... regards -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

1 0