March 2015 - openSUSE Users - openSUSE Mailing Lists

[opensuse] Is Baloo at end of life already?
by John Andersen 05 Mar '15

05 Mar '15

After many months of KDE updates, as well as Yast updates I've noticed zero new functionality in Baloo, and no further integration with Yast. Baloo seems to work, its fast, doesn't seem to use and resources to speak of. But half the functionality is missing. However: But 1) configuration is via some totally undocumented files deep within /home/<user>/.kde4/share/config. 2) No integration with Yast 3) No usable search facility except from within Dolphin, and that is limited. 4) No integration of tags in the search (what the hell are tags in Dolphin actually good for?) 5) No standalone search facility uses Baloo It seems like the package, and the entire concept of a built-in-search is abandoned. I find Baloo search really useful for finding things in a mountain of source code, not to mention documents etc. But the search capability is extremely limited. It won't search on metadata, tags, comments, or do any complex searches. If Baloo is going nowhere, I'm in the market for a good full text indexing system, which can index any mounted files. Any suggestion? -- 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

5 9

[opensuse] ChatCam webcam
by Robert Rea 05 Mar '15

05 Mar '15

I picked up this cheap webcam to see if it works. I plugged it in to the usb port and nothing happened. Any idea on what to try next? Of course the only OS listed on the box is XP, but I thought I would try it. -- Bob Rea mailto:gapetard@stsams.org http://www.petard.us http://www.petard.us/blog http://www.petard.us/gallery What do you say to Jesus when he comes again? Where have you been? You said you were coming right back. -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

4 4

[opensuse] Dell Wireless 1704 OpenSUSE 13.2
by Paul Groves 05 Mar '15

05 Mar '15

I have recently upgraded a laptop from 13,1 to 13.2 and I am now having trouble with the wireless adapter. It is a Dell Wireless 1704 with Broadcom BCM43412 chipset. Out of the box the bluetooth wirks but not the wifi. lspci shows the adapter fine. I was very surprised when I installed 13.1 some time ago and the Broadcom adater actually worked because this is the only Broadcom card I have EVER seen working in Linux (OpenSUSE, Ubuntu, Fedora, Debian and CentOS). Obviously I got my hopes up too soon and now it does not work in 13.2. On 13.1 all I had to do was install broadcom-wl then reboot and the card worked fine. However on 13.2 this does not work and performing those same steps achieves nothing. I have just reinstalled 13.1 and can replicate the installation and the card works fine. I have tried 13.2 again and no luck. Apart from the obvious solution to every Broadcom driver issue that I have encountered in the past. (Which is to buy a Wireless adapter that works properly with Linux out of the box like Atheros or Realtek :D). Does anyone have any ideas? -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

3 5

[opensuse] CUPS and Let's Print Droid
by James Knott 05 Mar '15

05 Mar '15

I have "Let's Print Droid" enabled on my Android phone to print on my printer. It can find the printer and print to it, but the document is not printed. If I go into CUPS, I can see the print job as being successfully printed, even though it wasn't. The printer is connected via USB. Any ideas about why jobs from another computer can print via CUPS on this computer, but not from Let's Print Droid? Is there something I can check? tnx jk -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

1 1

[opensuse] Installation problem
by A. den Oudsten 05 Mar '15

05 Mar '15

On my desktop I deleted the partitions / and /home in order to make a fresh install for which I used the Tumbleweed 20150227 DVD. The install went flawless until, after the restart, the standard wallpaper appeared without the default panel. Trying to make a panel ended in a mess. Another trial with a newly downloaded DVD gave the same results. Has anybody a suggestion how to solve this situation? Thanks in advance. André den Oudsten -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

5 6

[opensuse] 13.2 and Sound - specifically the volume setting
by Basil Chupin 05 Mar '15

05 Mar '15

Prior to 13.2 I set the sound volume in the Mixer (bottom right, System Tray) and it would stay as set from logout to login to logout..... ad finitum. Now, under 13.2 the volume setting changes according to some unknown algorithm. For example, last night I set the volume(s) in the Mixer to be at their maximum and I then adjust the actual volume of the sound I want to hear from the speakers via the volume control of my sound card (SoundBlaster X-Fi Titanium). A few minutes ago I turn on VLC to be able to watch some television --- and find that there is almost no sound coming from the speakers! I look at the Mixer (icon/widget, bottom RH) and found that all the volume settings have been reset to much lower level. Reset by _what_? Anyone know, please, what is required to make the settings in Mixer to *stick* and not be randomly altered by something in 13.2? (There have been posts in this mail list from people who suddenly found that they had no sound. I think that the answer to my question would also solve their problem.) BC -- Using openSUSE 13.2, KDE 4.14.4 & kernel 3.19.0-3 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

2 3

[opensuse] Who catches XEvents, such as laptop lid close etc.
by don fisher 05 Mar '15

05 Mar '15

Title says it all. I am tying to control what happens when I close the lid, touch the power button etc. I have not searched under openSuse, but there was once a thing called acpi with scripts in /etc/acpi that could be set to control these events. I do no wish to break the existing system, so would like to know how to interface with these options. I am running openSuse 3.2. I do not wish to have to dig back into those 7 volumes of the X window system. Yes, I still have them:-) Thanks Don -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

2 7

[opensuse] Grub troubles
by Frans de Boer 04 Mar '15

04 Mar '15

Hi, I have a server running 12.3 and want to install on a different partition the newer 13.2 distribution. Alas, after installation I can't boot 12.3 anymore because of wrong references. Every time I install a fresh kernel I have to manually edit the grub.cfg files to get 12.3 booted again. I also want to install a third system (LFS) without having to manually edit grub.cfg every time. So, is it possible to install the GRUB core image in a different partition and have the kernels be placed in the /boot directory of their respective partitions? Using this method I just need to chain to the relevant partition to start the local GRUB menu handler. - Between MBR and first partition: GRUB bootloader. - First partition: GRUB core and simple menu. - Second partition contains swap space - partitions 3..n Contain GRUB menu handlers and local linux kernels in local /boot dir. I need local GRUB handlers because of preserving the kernel version as supported by openSuse and newer standard kernels with better or newer support modules. Reading the GRUB 2.00 manual is not so helpful - to me - because of lack of unambiguous explanations or examples. Any suggestions? Regards, Frans. -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

4 6

[opensuse] Network settings in openSuse
by don fisher 04 Mar '15

04 Mar '15

I would like to know how to change the settings in openSuse without causing damage. I looked at yast, but it declares these are managed by NetworkManager. I looked at a couple of the network manager applets, but did not see how to proceed. I wish to change my ports from DHCP to static. I need to be able to add name servers etc. when I do this. I would also like to be able to tell the system what the password for my Wi-Fi is so that it does not prompt me all of the time. I think NetworkManager needs to be shut down to make these changes. But how does one do that. I tried disabling it in services but that did not appear to work. I would also like to know how to modify user parameters, such as the default shell, without breaking the system. I used a command line tool (forgot which one:-( and nobody was able to log into the system. I assume the damn check sums were not updated correctly. It used to be so easy to just edit /etc/passwd, or /etc/networking to make these changes. Thanks, Don -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

5 11

[opensuse] Tumbleweed update question
by Roger Oberholtzer 03 Mar '15

03 Mar '15

We are in the process of deciding if we will move from doing traditional openSUSE installs (e.g., 13.1, 13.2, etc via our home-cooked KIWI OEM images) or if we should move to Tumbleweed (perhaps also via a KIWI OEM image). Our biggest question is how often one should do an update to Tumbleweed once it is installed. More specifically, how long one can wait between updates? I know that is a tricky question. But I am guessing that there are some stated goals in the Tumbleweed project related to this? In our use case, openSUSE is installed in road vehicles that do not spend time in the office. Occasionally a vehicle is in a state where we can do an update. Either it is in the garage for other maintenance or is between contracts (our favorite time to do upgrades). This can occur roughly every 6 - 8 months. That would mean that we would only update Tumbleweed with that frequency. Or perhaps longer. Our current approach is to update to a new openSUSE every 2 years or so. Then, as each vehicle is available, it gets a new install. The advantage of using Tumbleweed, even at the 6-8 month update frequency, is that all the system settings are kept. When doing a destructive install more hand work is required and thus more errors can occur. Doing a Tumbleweed update should lessen the chance of an error because of re-installation. It is one of the reasons we update as seldom as we do. Increasing the frequency of updates allows us to keep our system more similar. Which is a good thing. Opinions? -- Roger Oberholtzer -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

5 10