May 2015 - openSUSE Users - openSUSE Mailing Lists

[opensuse] macbook multi monitor
by blue hut 08 May '15

08 May '15

Hello, I have a Macbook with an intel and nvidia graphics card. I used the nouveau driver and nvidia card for some time. But my laptop got really hot. So recently I blacklisted the noveau driver. And only use intel card. But then I realized: multiple monitor doesn't work with it! So now I consider switching back to nvidia, is the proprietary driver better? Also I read this: https://en.opensuse.org/SDB:NVIDIA_Bumblebee but it seems that won't help me cooling down my laptop, since I will use multiple monitors all the time I guess all the time it will also use the nvidia card, is this correct? I understand bumblebee like this: If I need not much good graphics, it switched to lower card (intel), if I need good graphic, it enabled the high card (nvidia). But when I will need multi monitor, it will use nvidia all the time, right? Is it even right that the intel card doesn't support multiple displays? regards, Michael -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

2 1

[opensuse] Firefox Problem
by Bob Rea 07 May '15

07 May '15

I restarted os 12.3 because the system was operation sluggishly, especially firefox. When I restarted firefox offered to restore windows but before I could reply, it started showing error message, the standard one, crash reporter. I tried to start firefox and it told me it was already running, and I needed to close it to start anew. I tried to kill all firefox processes, but the last of these showed: ob@gandalf:~> ps ax |grep firefox 4028 pts/0 S+ 0:00 grep --color=auto firefox bob@gandalf:~> ps ax |grep firefox 4103 pts/0 S+ 0:00 grep --color=auto firefox bob@gandalf:~> kill 4028 4103 bash: kill: (4028) - No such process bash: kill: (4103) - No such process Each time, It shows a new process that does not exist. It just keeps doing this. top does not show firefox, nor does ksysguard. What can I do about this? -- 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

5 10

[opensuse] problem with opensuse 13.1 repos?
by Michael J Dur 07 May '15

07 May '15

I just did a 13.1 install from disc, and I'm not able to refresh/update. I can access http://download.opensuse.org/distribution/13.1/repo/non-oss/ in the browser. The message is: zypper refresh Repository 'openSUSE-13.1-1.10' is up to date. Retrieving repository 'openSUSE-13.1-Non-Oss' metadata -------------------------------------[\] File '/repodata/repomd.xml' not found on medium 'http://download.opensuse.org/distribution/13.1/repo/non-oss/' Abort, retry, ignore? [a/r/i/? shows all options] (a): i Retrieving repository 'openSUSE-13.1-Non-Oss' metadata .................................[error] Repository 'openSUSE-13.1-Non-Oss' is invalid. [|] Valid metadata not found at specified URL Please check if the URIs defined for this repository are pointing to a valid repository. Skipping repository 'openSUSE-13.1-Non-Oss' because of the above error. Retrieving repository 'openSUSE-13.1-Oss' metadata -----------------------------------------[|] File '/repodata/repomd.xml' not found on medium 'http://download.opensuse.org/distribution/13.1/repo/oss/' Abort, retry, ignore? [a/r/i/? shows all options] (a): i Retrieving repository 'openSUSE-13.1-Oss' metadata .....................................[error] Repository 'openSUSE-13.1-Oss' is invalid. [|] Valid metadata not found at specified URL Please check if the URIs defined for this repository are pointing to a valid repository. Skipping repository 'openSUSE-13.1-Oss' because of the above error. Repository 'openSUSE-13.1-Update' is up to date. Repository 'openSUSE-13.1-Update-Non-Oss' is up to date. Some of the repositories have not been refreshed because of an error. -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

2 2

[opensuse] inserting USB stick crashes plasma desktop
by Istvan Gabor 07 May '15

07 May '15

Hello: If I insert an USB flashdisk into my computer with openSUSE 13.2, KDE 4.14.3, a window appears saying "We are sorry, Plasma Desktop Shell closed unexpectedly.". The screen flashes but everything restores. But if I click on the device notifier icon, the desktop crashes again, finally resulting in the disappearance of the panel. I can still switch between open windows by ctrl-Alt, but I cannot access my USB stick. Is this normal? If not, how could I prevent/fix it? The USB stick works without problem in my other openSUSE 12.2 system with KDE 3, so the problem is probably not with the flashdisk. This is the "Developer Information" saved form The KDE Crash Handler window: Application: Plasma Desktop Shell (plasma-desktop), signal: Bus error Using host libthread_db library "/lib/libthread_db.so.1". [Current thread is 1 (Thread 0xb5445740 (LWP 12733))] Thread 4 (Thread 0xa419fb40 (LWP 12734)): #0 0xffffffff in () Thread 3 (Thread 0xa1802b40 (LWP 12735)): #0 0xffffffff in () #1 0x00200001 in () #2 0x0000000d in () #3 0x00200001 in () #4 0x00000000 in () Thread 2 (Thread 0xa0d6eb40 (LWP 12736)): #0 0xffffffff in () Thread 1 (Thread 0xb5445740 (LWP 12733)): #0 0xffffffff in () #1 0x00000000 in () Thanks for your help, Istvan -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

2 2

[opensuse] blank spam
by jdd 06 May '15

06 May '15

Hello, I receive on a regular basis (several a day) blank messages that are obviously spam, here two of them as examples (below): Return-Path: <Franklin_Sabrina30(a)corexsud.com> X-Original-To: jdd(a)dodin.org Delivered-To: jdd(a)dodin.org Received: from 94-183-247-79.shatel.ir (unknown [94.183.247.79]) by ks311900.kimsufi.com (Postfix) with SMTP id B2554C0234 for <jdd(a)dodin.org>; Wed, 6 May 2015 01:33:06 +0200 (CEST) Message-ID: <8[10 Return-Path: <Longoria_Devin30(a)activcomputing.com> X-Original-To: jdd(a)dodin.org Delivered-To: jdd(a)dodin.org Received: from 188.165.211.22 (unknown [37.1.18.77]) by ks311900.kimsufi.com (Postfix) with SMTP id C136EC0145 for <jdd(a)dodin.org>; Tue, 5 May 2015 23:50:41 +0200 (CEST) Message-ID: <7[10 as you can see the return path and the from are different for each message. Thunderbird anti spam do not see them. I fear filtering out all blank message may me miss some friends error. the kimsufi part is my own imap server what do you think? thank jdd -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

5 8

[opensuse] no space left on the device
by jdd 06 May '15

06 May '15

Hello, I was hit this morning by the "no space left on the device" symptom, probably related to BTRFS (?), when btrfs's df (znd normal df) gives at least half space free. To work I had to reinstall on the other disk a 13.2 version (with ext4, this time). I know it's a discussed problem, and I read many posts on the subject, but It still don't get how to solve it. I *can* login with the failsafe mode, as root (or not), CLI only, but any action that include temp file fails with "no space left on the device", yast segfault... I cleared /tmp and some files in /home with no change. Is it possible to recover this? how? thanks jdd -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

17 77

[opensuse] New Kernel and Systemd (was: Dracut)
by Frans de Boer 06 May '15

06 May '15

On 05/06/2015 08:01 AM, Per Jessen wrote: > Frans de Boer wrote: > >> I recreated the initrd for the stock kernel and everything >> worked...:\ >> So, maybe not the initrd creation is at fault, maybe something in the >> kernel itself? If so, what has changed between 12.3 and 13.2 that the >> kernels compiled do not proceed with the boot process but seem to wait >> for disks. my guess is the dracut modules? > > Hi Frans > > Apart from the dracut initrd being bigger and less easy to handle, I > have not noticed any issues with it. If anything is waiting for disks, > it's probably not the kernel but maybe systemd? > > /Per The message where the boot process hangs is: [ ] (x of 3) A start job running for dev-disk-by\x2duuid-<....> This appears also sometimes when closing the distribution provided kernel. I dislike the cumbersome uuid notion and rather use label, but beside that, has anybody seen this in conjunction of systemd? It does not matter if some or all modules are compiled into the kernel, the result is always the same. Again, any suggestion? Frans -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

1 0

[opensuse] New article on BTRFS FULL
by John M Andersen 05 May '15

05 May '15

Just to pass on an article that might be of help: http://marc.merlins.org/perso/btrfs/post_2014-05-04_Fixing-Btrfs-Filesystem… -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

2 3

[opensuse] checkinstall doesn't work
by Masaru Nomiya 04 May '15

04 May '15

Hello, I'm using openSUSE 13.2. I installed checkinstall package from http://software.opensuse.org/package/checkinstall?search_term=checkinstall Then I tried to make rpm package for the libiconv-1.14.tar.gz. The build of libiconv-1.4 successed, but checkinstall command failed to make rpm package; [...] Building target platforms: x86_64 Building for target x86_64 Processing files: libiconv-1.14-1.x86_64 error: Not a directory: /var/tmp/tmp.OEFTDky3Lf/package/usr/local/lib64/libcharset.so.1 error: Not a directory: /var/tmp/tmp.OEFTDky3Lf/package/usr/local/lib64/libiconv.so.2 error: Not a directory: /var/tmp/tmp.OEFTDky3Lf/package/usr/local/lib64/libiconv.so error: Not a directory: /var/tmp/tmp.OEFTDky3Lf/package/usr/local/lib64/libcharset.so RPM build errors: Not a directory: /var/tmp/tmp.OEFTDky3Lf/package/usr/local/lib64/libcharset.so.1 Not a directory: /var/tmp/tmp.OEFTDky3Lf/package/usr/local/lib64/libiconv.so.2 Not a directory: /var/tmp/tmp.OEFTDky3Lf/package/usr/local/lib64/libiconv.so Not a directory: /var/tmp/tmp.OEFTDky3Lf/package/usr/local/lib64/libcharset.so How can I solve this problem? Thanks in adavance. --- ┏━━┓彡 Masaru Nomiya mail-to: nomiya @ galaxy.dti.ne.jp ┃＼／彡 ┗━━┛ "Bill! You married with Computers. Not with Me!" "No..., with money." -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

5 10

[opensuse] How do I fix a startup error in which the bios(?) reports an absence of a bootable device
by Ted Byers 04 May '15

04 May '15

This happened today. The machine in question is running OpenSuse 13.2, on a decent sized SSD. The only symptom I can document is that once I try to boot the machine, I se the usual items flash by as the bios runs through the boot sequence, until the point where the drive from which the system is supposed to boot is sought, and at that point, I get a message complaining that no bootable device was found and asking that I connect a bootable device or insertt an optical disk from which I can boot, and then press a button to proceed. This morning, the city in which I live experienced a power failure. While all my systems are protected by two surge suppressors (one on the mains, before power enters the building's power panel, and the other is a device into which my computers are plugged. Alas, the 'UPS' was inadequate to keep all the machines running until the power was restored. Only this one machine (the workstation on which I work developing computer programs) is affected. None of the others (about 6 in all) have any indication of a problem. First question is, what is the likelihood that there is physical damage to the SSD? Second, what would be the steps to try to restore this machine? I know, in a worst case scenario, I can buy another SSD, install the latest and greatest release of OpenSuse, but first I need to see if I can fix this. I really do not want to lose the data I have on that drive. Can you point me to a few of your favourite web pages that deal with this specific problem? Thanks Ted -- R.E.(Ted) Byers, Ph.D.,Ed.D. -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

4 3