August 2011 - openSUSE Users - openSUSE Mailing Lists

Re: [opensuse] KDE 4.7 , opensuse 11.4 64bit.
by Anton Aylward 07 Aug '11

07 Aug '11

Thomas Lübking said the following on 08/07/2011 09:35 AM: > Am Sun, 07 Aug 2011 07:22:29 -0400 > schrieb Anton Aylward<Anton.Aylward(a)rogers.com>: > >> Phenomena like: The size and position of the widgets on screen is >> the same every time I login even if I move, resize delete or add. >> >> >> Phenomena like: the set of programs in the kickoff menu's "recently >> used" set is the same on every new login regardless of what I ran in >> a previous session. > > Is *only* "plasma-stuff" affected? I'm not sure what you mean by "plasma-stuff" How do I tell the stuff I've put in my panel and on the desktop after right-click on scree, clicking "unlock widgets" then "add widgets"? Things like analog clock, weather, cpu load, temperature .... or perhaps the same to the bottom panel > Check the timestamps on ~/.kde4/share/config/(plasma*|kickoff*) (that > might be zsh only syntax) - are they being written? Sorry. I thought I made that clear with the example of kickoffrc. The timestamp alters each day but the contents don't. I suppose I could add kernel taps to record what gets written to disk, but that might just overflow my disk. > Copy those files. Alter some widgets on your desktop. "kquitapp > plasma-desktop". Then diff the copies agains the actual config files. > Any updates? I'll do that, but could you explain how that is different from login alter some widgets (e.g. add to desktop, change the size/position of "folder view" and the folder it refers to, its sort order log out log in again And find that those changes are no longer there. Similarly with kickoff not recording the recently used. Yes, I took a copy of kickoffrc in "init 3"mode before a session. No matter how many programs I started during a session and could see on the 'recently used' _during_ the session, when I logged out the "new" kickoffrc was the same as before. I'm sorry, I thought I made that clear in a previous post. Is the kickoff menu a widget or a plasmoid? When I use the "add widget" I can select "categories" and "running" and see "application launcher" there. Along with "folder view" and the other things I have on my desktop like the clock ..... That makes these 'widgets' and 'widgets are not plasmoids? Now if I DO wipe ~/.kde4, start kde4 and set up a new set of widget - or should I be calling them plasmoids? - then this new set are there. And if I alter them in a session .... they get recorded from that "empty" session and are the new 'baseline' I log out and they get recorded because there was no session before. When in log in, that first session's settings come back. I make changes, but .. It doesn't stick once I have logged out and in again. Whenever I log in again I get that first sessions settings AGAIN. The Desktop Naming bug seemed limited. This seems more comprehensive, affecting many widgets. Or plasmoids. -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse+help(a)opensuse.org

1 0

[opensuse] accented characters in libre office
by George OLson 07 Aug '11

07 Aug '11

Howdy all, I am working with a minority language group (a spoken language, not a programming language :) ) which does not have language support of any kind in any platform. However, for the script we are using, all I need to be able to do is put 1 of 3 characters over the vowels - a right accent (don't know how to insert, as here it only goes straight down like this ' but I want it to go to the right), a grave accent `, and a carat ^. Here are some examples I have cut and pasted from old data I typed in using microsoft office: binoó - means piled tùpa - means to share equally lugtâ - means dirt or land When I used windows, I installed the english international keyboard in the operating system, as this has those 3 characters. However, since I am trying to migrate over to suse linux, how can I do something comparable? All I need to do is to be able to use the keyboard to enter the characters without having to take a mouse and clicking on an insert special character function when I type out data in a word processor like libre office, or when I enter text in a cell in a spreadsheet or database. Thanks, G -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse+help(a)opensuse.org

7 12

Re: [opensuse] zypper refuses to update some software
by j.e.perry＠cox.net 06 Aug '11

06 Aug '11

Sorry if this doesn't make it properly into the thread. My ISP has the silly idea that it's unsafe for me to post messages from outside my home area, and I'm traveling, so have to do email by webmail (why does webmail suck so bad??). Anton Aylward said: >> Do I need to fix something? What? > No. That's what I'd hoped to hear. I knew the man page differences, but effects are sometimes obscure to us to don't have a solid knowledge of system matters. Roger Oberholzer said: > I would imagine one should use care when using 'dup'. Depending on the > repos you have enabled, I could imagine some unexpected results. > Having > said that, I have never had a problem when I have used it. I had some problems that were obscure when I was using dup, then I saw a comment that one should use up unless one had a reason to use dup, but that we shouldn't mix the two. So I switched over, hoping it would help. I _think_ it has, but this constant refusal to update things that look (to my ignorant eye) important. Marcus Meissner said: > It looks like it wants to install the update stack patch first. > After you have done it, the rest will also be installable. > zypper patch // first run will install update stack update (new > zypper/libzypp) > zypper patch // second run will install the rest updates So any time I see a zypper update I should run zypper twice in succession? I recall having seen the difference between zypper patch and zypper update, but I don't recall enough to be sure why I stuck with up. I seem to remember that it didn't make a lot of practical difference? Marcus: > You can always check with a direct zypper in why zypper thinks > it would be a bad idea to install them: > zypper in NetworkManager-kde4-libs > which will likely print the reason of why not. Thanks also, Joachim and Ken for your comments. This particular thread was initiated by my observation that there are almost always kde items that are not updated. Also, gstreamer is never updated as far as I can remember, and amarok and kaffeine both have missing plugins. vlc almost always works, and when it doesn't, mplayer does, but neither of them is the default for any multimedia file, and I haven't taken the trouble to learn how change the defaults. But I was wondering if some of these non-updates were part of the problem, and if I needed to do something. And, fo course, if I was missing out on some important things. jp -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse+help(a)opensuse.org

4 3

[opensuse] openSUSE Weekly News 187 is out!
by Sascha Manns 06 Aug '11

06 Aug '11

We are pleased to announce: Issue 187 of openSUSE Weekly News is out! [0] In this Issue: * Are you ready for RWX³ ? * Google Summer of Code Reports * Jos Poortvlieet: And they keep rocking… For a list of available translations see the Translations Section in the actual Weekly News. [0] http://bit.ly/nfzczS (in PDF) [0] http://bit.ly/rlmlbE (in HTML with Bento Theme) [0] http://bit.ly/q1lbID (in HTML with Susebooks Theme)) -- Sincerely yours Sascha Manns open-slx.com openSUSE Community & Support Agent openSUSE Marketing Team Blog: http://saigkill.wordpress.com -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse+help(a)opensuse.org

1 0

[opensuse] 11.4 problems: Kdm Sound temprature
by Anton Aylward 06 Aug '11

06 Aug '11

Now I have a bootable kernel I have worked though matters with 11.4 All the personal config came though intact :-) A lot of the system config has been altered and I'm not sure if that is just 11.3/11.4 differences or what. These are the problems I see now 1. KDM does not work. The greeter fails. The log file reads X.Org X Server 1.9.3 Release Date: 2010-12-13 X Protocol Version 11, Revision 0 Build Operating System: openSUSE SUSE LINUX Current Operating System: Linux BigBoy 2.6.37.6-0.5-pae #1 SMP 2011-04-25 21:48:33 +0200 i686 Kernel command line: root=/dev/sda3 resume=/dev/sda2 splash=silent quiet PROFILE=default vga=0x317 Build Date: 22 February 2011 10:15:34PM Current version of pixman: 0.20.0 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: Sat Apr 30 07:12:51 2011 (==) Using config directory: "/etc/X11/xorg.conf.d" (II) [KMS] Kernel modesetting enabled. No protocol specified kdmgreet: cannot connect to X server :0 There is nothing wrong with X. I can start it with 'startx' from the command line under both the root account and my personal account and with a few oddities (see later) it works. I don't know what to make of that message or how to proceed. 2. Lots of odd errors in config files Many things started from the command line produce stuff like this kbuildsycoca4(4522)/kdecore (services) KServicePrivate::init: The desktop entry file "/usr/share/applications/YaST2/inetd.desktop" has Type= "Application" but also has a X-KDE-Library key. This works for now, but makes user-preference handling difficult, so support for this might be removed at some point. Consider splitting it into two desktop files. kbuildsycoca4(4522)/kdecore (services) KServicePrivate::init: The desktop entry file "/usr/share/applications/YaST2/sw_source.desktop" has Type= "Application" but also has a X-KDE-Library key. This works for now, but makes user-preference handling difficult, so support for this might be removed at some point. Consider splitting it into two desktop files. kbuildsycoca4(4522)/kdecore (services) KServicePrivate::init: The desktop entry file "/usr/share/applications/YaST2/users.desktop" has Type= "Application" but also has a X-KDE-Library key. This works for now, but makes user-preference handling difficult, so support for this might be removed at some point. Consider splitting it into two desktop files. kbuildsycoca4(4522)/kdecore (services) KServicePrivate::init: The desktop entry file "/usr/share/applications/YaST2/nfs.desktop" has Type= "Application" but also has a X-KDE-Library key. This works for now, but makes user-preference handling difficult, so support for this might be removed at some point. Consider splitting it into two desktop files. kbuildsycoca4(4522)/kdecore (services) KServicePrivate::init: The desktop entry file "/usr/share/applications/YaST2/security.desktop" has Type= "Application" but also has a X-KDE-Library key. This works for now, but makes user-preference handling difficult, so support for this might be removed at some point. Consider splitting it into two desktop files. kbuildsycoca4(4522)/kdecore (services) KServicePrivate::init: The desktop entry file "/usr/share/applications/YaST2/hwinfo.desktop" has Type= "Application" but also has a X-KDE-Library key. This works for now, but makes user-preference handling difficult, so support for this might be removed at some point. Consider splitting it into two desktop files. kbuildsycoca4(4522)/kdecore (services) KServicePrivate::init: The desktop entry file "/usr/share/applications/YaST2/mouse.desktop" has Type= "Application" but also has a X-KDE-Library key. This works for now, but makes user-preference handling difficult, so support for this might be removed at some point. Consider splitting it into two desktop files. kbuildsycoca4(4522)/kdecore (services) KServicePrivate::init: The desktop entry file "/usr/share/applications/YaST2/vendor.desktop" has Type= "Application" but also has a X-KDE-Library key. This works for now, but makes user-preference handling difficult, so support for this might be removed at some point. Consider splitting it into two desktop files. kbuildsycoca4(4522)/kdecore (services) KServicePrivate::init: The desktop entry file "/usr/share/applications/YaST2/host.desktop" has Type= "Application" but also has a X-KDE-Library key. This works for now, but makes user-preference handling difficult, so support for this might be removed at some point. Consider splitting it into two desktop files. kbuildsycoca4(4522)/kdecore (services) KServicePrivate::init: The desktop entry file "/usr/share/applications/YaST2/SD_logprof.desktop" has Type= "Application" but also has a X-KDE-Library key. This works for now, but makes user-preference handling difficult, so support for this might be removed at some point. Consider splitting it into two desktop files. kbuildsycoca4(4522) parseLayoutNode: The menu spec file contains a Layout or DefaultLayout tag without the mandatory Merge tag inside. Please fix your file. 3. Latency on menubar Just about every application, thunderbird & firefox in particular, but all the KDE applications as well, have a delay when top menubar items are clicked. I am used to this on LiveCD where the system has to drag in the relevant stuff from the CD but not on a real system. The KDE applications seem to cache items, the GTK applications don't seem to. 4. No sound. Sound has stopped working. Testing with LiveCD tells me its not a hardware problem The mixer icon doesn't appear in the system tray on starting KDE4 and when it is started everything is set to zero. Even then sound isn't working. This isn't a modules problem, the modules are all loaded as I expect. # lsmod | grep snd snd_pcm_oss 47823 0 snd_mixer_oss 16817 1 snd_pcm_oss snd_seq 57265 0 snd_seq_device 6646 1 snd_seq snd_intel8x0m 12017 0 snd_intel8x0 27766 1 snd_ac97_codec 106641 2 snd_intel8x0,snd_intel8x0m ac97_bus 1082 1 snd_ac97_codec snd_pcm 88249 4 snd_pcm_oss,snd_intel8x0,snd_intel8x0m,snd_ac97_codec snd_timer 21876 2 snd_seq,snd_pcm snd 65966 11 snd_pcm_oss,snd_mixer_oss,snd_seq,snd_seq_device,snd_intel8x0,snd_intel8x0m,snd_ac97_codec,snd_pcm,snd_timer soundcore 6854 1 snd snd_page_alloc 8025 3 snd_intel8x0,snd_intel8x0m,snd_pcm -- If you lie to the compiler, it will get its revenge. - Henry Spencer -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse+help(a)opensuse.org

6 13

[opensuse] Free Usenet servers?
by James Hatridge 06 Aug '11

06 Aug '11

Hi all, Does anyone know of a free usenet server that has the alt.b.* lists? Thanks JIM -- The US was colonized by the religious, political, economic, and criminal rejects of every country in the world. We have been carefully breeding insane, obsessive, fanatic lunatics with each other for over 400 years, resulting in the glorious strain of humanity known as "Americans". You have to expect some... peculiarities. -Mark Damon Hughes -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse+help(a)opensuse.org

4 7

[opensuse] Re: [opensuse-kde] Kmail2 from KDE 4.7 slow folders
by ianseeks 06 Aug '11

06 Aug '11

On Friday 05 Aug 2011 23:27:09 Malte Gell wrote: > Hi there, > > I use kmail-4.7.0-10.1.x86_64 and whenever I open an email folder, be it an > IMAP folder or local folder with email fetched from POP3 accounts, it > sometakes takes very long (up to one minute) until the folder is accessable. I had that with kmail1, i thought it might have been because my maildir was rather large Dont seem to have the problem with kmail2 (but do have other problems) > Is there something I can do to fasten opening email folders? It is annyoying > when you have many folders and each takes ages to open.... > > Regards > Malte -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse+help(a)opensuse.org

1 0

[opensuse] kmail2, moving to a new fresh install on a second user
by Constant Brouerius van Nidek 06 Aug '11

06 Aug '11

Due to the problems I have with kmail2 I want to make a new user and install there a new kmail. I want to export the kmail contents and import them in the new user. How to export or archive them? According to the kmail handbook there should be an "archive" possibility. There is a "save as" choice and I used it on one folder. But there is no choice and only a lot of activity which I have canceled in order to find out on the list if that is normal and what and where it is saved and in which format. I want 34 folders to move to the new user. Is that to be done folder by folder? Problems I have with my kmail2 are among others, sending email via has no choices (could have used Message in the toolbar) so yesterday it just send emails to the list from the account which is dedicated as default. The regular asked question which of two emails are to be kept, the right, left or both. Do not see differences. Do not know if these are problems seen by others or that it is the aftermath of a corked emigration from kmail to kmail2. -- Linux User 183145 using LXDE and KDE4 on a Pentium IV , powered by openSUSE 11.4 (i586) Kernel: 3.0.0-7-desktop LXDE WM & KDE Development Platform: 4.7.00 (4.7.0) 12:21pm up 13:55, 3 users, load average: 1.21, 1.24, 1.25 -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse+help(a)opensuse.org

2 1

[opensuse] New SANE for Canon 9000F
by LLLActive＠GMX.Net 06 Aug '11

06 Aug '11

Hi all, I got the source for the Canon 9000F scanner from Gernot Hassenpflug to try on my new scanner. I got the backend compiled on openSUSE 11.4 /64, and working with Xsane and gimp. It scans up to 2400 at the moment, and with adjustments also 4800. I still get some errors with higher resolutions, but it is workabel for normal use at the moment. Gernot is working on the Same project, and will complete this driver perhaps before the end of the year. I used his "compiling gutenprint CVS and adding Canon printers" directions from http://aikishugyo.dnsdojo.org/blog/ (It is not always up, therefore I include what he sent me below) Source is available from him over his Blog, or mail me and I can send what he sent me. It is added into /usr/src/sane-backends/backend directory. YaST does see the scanner with the scanner install: Driver: pixma Scanner: CANON Canoscan 9000F at pixma:04A91908 You can test it as well: Test with 'scanimage -d pixma:04A91908 -v' succeeded. The result I got: scanimage: scanning image of size 638x877 pixels at 24 bits/pixel scanimage: acquiring RGB frame scanimage: min/max graylevel value = 37/248 scanimage: read 1678578 bytes in total In XSANE or other scan apps it may not be detected when starting it as a user. I got the Error: Failed to open devive `pixma:04A91908': Invalid argument To check if it works, run as root: # export SANE_DEBUG_PIXMA=11 # xsane Debug scrolls in the terminal while xsane starts up. If starting Xsane as a user, and it produces errors, it is a rights issue. I just gave all rights to all to get it going, but still have to figure out how it should be done correctly. :-) Al HowTo: compiling SANE from source Compiling SANE <http://www.sane-project.org/> from source is necessary whenever some changes are made to backend code. For reference is shown also how to get the latest code. Ensure that git <http://git-scm.com/> is installed, and go to the directory chosen for development, before getting the latest source with the /clone/ command. cd ~/src git clone git://git.debian.org/sane/sane-backends.git <http://git.debian.org/sane/sane-backends.git> To update the existing code, you can use the /pull/ command from the /sane-backends/ directory. Now, the compilation process must begin using the /autoconf/ and /automake/ commands[1]. Problems that arise in these steps must first be solved before continuing. POSIX warnings can be ignored. cd sane-backends autoconf automake Next is the compilation with specified backends. If only one backend is needed, no quote marks are needed. If all backends should be compiled, the BACKENDS variable is not needed. The default installation directory is /usr/local/ so there should be no clash with the installed system SANE. BACKENDS="pixma epson2" ./configure make sudo make install Sometimes /sudo/ will not have the desired permissions, so executing the previous block as root might be necessary for individual users. Note that this should be avoided for production systems. Footnotes [1] According to a SANE mailing list posting, autoconf and automake execution is not needed since the /.in/ files are part of the git repository. However, I consider the commands good for detecting some possible problems early on. References The SANE project website: http://www.sane-project.org <http://www.sane-project.org/> Pointers for general confusions avoidance: 1. SANE uses libusb to talk to USB scanners 2. sane-find-scanner uses libusb to check that libusb can recognize the scanner. It does not use the SANE backends (like pixma backend) to do anything with the scanner. So it is just a check that libusb is working. 3. scanimage uses the SANE backend to talk to the scanner, so this is the real test. But you might need to be root to use it. Or else set up some sane-related conf file. 4. make sure the sane-find-scanner and scanimage used are the ones in /usr/local after compiling SANE. 5. after scanimage as root, you could also try xsane as root. 6. if you can set up your system to work also as non-root with scanimage and xsane, maybe send me (Gernot) the info on what you did so I can help people who ask me later. You could also post to the SANE mailing list if you like. -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse+help(a)opensuse.org

1 0

[opensuse] shorewall will be in the next openSUSE release
by Togan Muftuoglu 05 Aug '11

05 Aug '11

Hi, Just to pass the news [1], shorewall firewall package will be part of the next openSUSE release, meaning users would not need to set up an extra repository (of course they can always choose to follow the development repo). Togan [1]<http://lizards.opensuse.org/2011/08/05/factory-progress-2011-08-05/> -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse+help(a)opensuse.org

1 0