August 2012 - openSUSE Users - openSUSE Mailing Lists

[opensuse] HP 2840 LaserJet
by Patrick Shanahan 28 Aug '12

28 Aug '12

I just inherited an HP 2840 LaserJet printer. Looking for *any* words of wisdom.... tks, -- (paka)Patrick Shanahan Plainfield, Indiana, USA HOG # US1244711 http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 http://en.opensuse.org openSUSE Community Member Registered Linux User #207535 @ http://linuxcounter.net -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

4 4

[opensuse] virt-manager unable to connect to libvirt after update
by Ralf Müller 28 Aug '12

28 Aug '12

Hi there. I'm running a Xen-Server using the Tumbleweed repository. After I updated this system an hour before (zypper dup --from Tumbleweed; zypper up; reboot) virt-manager is not able to connect to libvirt anymore. All domU's are up and running, "xm list" shows them correctly, but virt-manager reports the following after start: Unable to connect to libvirt. internal error libxenlight state driver is not active Verify that: - A Xen host kernel was booted - The Xen service has been started Details Unable to connect to libvirt. internal error libxenlight state driver is not active Verify that: - A Xen host kernel was booted - The Xen service has been started Libvirt URI is: xen:/// Traceback (most recent call last): File "/usr/share/virt-manager/virtManager/connection.py", line 1027, in _open_thread self.vmm = self._try_open() File "/usr/share/virt-manager/virtManager/connection.py", line 1009, in _try_open flags) File "/usr/lib64/python2.7/site-packages/libvirt.py", line 102, in openAuth if ret is None:raise libvirtError('virConnectOpenAuth() failed') libvirtError: internal error libxenlight state driver is not active rclibvirtd status reports: libvirtd.service - Virtualization daemon Loaded: loaded (/lib/systemd/system/libvirtd.service; enabled) Active: active (running) since Tue, 28 Aug 2012 09:19:18 +0200; 33min ago Main PID: 11360 (libvirtd) CGroup: name=systemd:/system/libvirtd.service └ 11360 /usr/sbin/libvirtd --listen Any idea what goes wrong? Best regards Ralf-- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

1 0

[opensuse] Installation problem with keyboard
by Robert Rawlinson 27 Aug '12

27 Aug '12

I have been trying to install Opensuse 12.1 but I can't key in anything. It seems to ignore anything I do on the keyboard. I can't move the pointer to install. I am using a HP keyboard thru a KVM 4 port. I am trying to put it on a system that works fine on 11.4. Bob R -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

5 6

[opensuse] Case flipping in KDE3 (OpenSuSE 12.1)
by j debert 27 Aug '12

27 Aug '12

After a day or two in KDE3, I am finding that case in silently and globally flipped: Caps lock is off and all alphas are upper case, all punctuation is shifted, no numbers are available only the symbols you get using the shift key, keypad doesn't work, and arrow, page up/down and delete keys, function keys, etc., don't work. Using shift or caps lock gets me only the lower case alphabet. Replugging keyboard or changing keyboard does not solve this. Whether keyboard is PS/2 or USB makes no difference. Restarting the session usually does not change this. Restarting display manager resolves it. There is nothing in the logs, no errors, complaints at all. This is new behaviour, starting within the last month. Been using 12.1 since at least May. This is interfering with remote jobs I have running. Can't just shut down and restart while the jobs are running. What else can I look at? jd -- -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

3 3

[opensuse] universal desktop boxes (Was : Throw "apper" out of 12.2?)
by Dsant 27 Aug '12

27 Aug '12

On Friday August 24 2012 09:25:08 Dominique Leuenberger a.k.a DimStar wrote: > Quoting Dominik Baumann <dominik.baumann(a)geekmail.de>: > > Shouldn't it be easy for someone who knows how to access the > > notification area, to do something similar to the following crontab > > entry?: > > > > 10 10 * * 2 ( export DISPLAY=:0 ; kdialog --msgbox "`zypper --quiet > > patch-check`" ) > > It should be... now please come up with a crontab line that does the > right thing, independent of the user running GNOME, KDE, XFCe, LXDE, > Mate, E17, [...] > Interesting, is there a minimal "desktop language" to draw basic windows, buttons... And compatible with these desktops ? Dsant -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

3 2

[opensuse] Re: how do I boot to a text console in 12.2?
by Linda Walsh 27 Aug '12

27 Aug '12

Felix Miata wrote: > 2-Kernel/initrd changes require "running" lilo before a reboot can use > them. ---- This is because lilo a lilo booted kernel doesn't need to know the FS format before booting --- it reads the boot code from the disk sectors. This is the most efficient type of boot though it can have problems. I always run a lilo as part of my install new kernel script, so it was never an issue. Grub needs to know how to read a file system -- and how to read those file sectors off disk. It screwed that up so badly, that Suse stopped supporting XFS because grub doing direct disk read/writes on a live file system wasn' supported. I was told that was fixed, but XFS support at SuSE never recovered to where it was. Now SuSE doesn't support TEXT MODE booting, because it's not in GRUB? HEY LYNN, it still works in LILO! I remember that breaking in Grub when I first tried switching to grub because grub uses a graphical boot instead of BIOS VGA chip modes... > 3-Grub shell allows to manually boot from the Grub shell, crucially > handy if menu.lst is missing or otherwise problematic. --- Can you use grub to boot directly from the hard disk, or do you need a ram disk to pre-boot from in order to really boot from your hard disk? > > 4-Interactive editing of initrd & kernel cmdline. > 5-Chainloads NTLDR, IBM BM (at least in theory), other Grubs, & even Lilo. --- lilo allows both of those > > 6-Easily configurable & installable even though booted to another OS or > media. > 7-Needs no files in /etc to be able to function or configure. --- You mean the "System Config dir?"... why would having config dirs in the system config dir be a bad thing? And so far, I've never had problems with video... well... sorta scratch... when I boot from memory (kexec), but that doesn't count -- it's not using lilo then.. Hey, I would love to use grub if it worked...but last time I tried it -- it turned off the video during boot and I couldn't see the bootup.... That's probably what the OP wants too!... grub isn't giving her one of the builtin VGA or EVGA console modes.... -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

6 16

[opensuse] Users don't want the grief of submitting bug reports....
by Linda Walsh 26 Aug '12

26 Aug '12

Rajko wrote: > On Tue, 07 Aug 2012 12:45:41 -0700 > It is about 3-4 openSUSE users that I know about and it is for period > of last few years, which is insignificant, if one would not know: > http://www.useit.com/alertbox/participation_inequality.html > > Due to this issue alone, openSUSE lost quite some number of reports, > and most likely users. ---- OpenSuse Doesn't want those reports. If they can't even follow the corporate line in regards to creating a login, then how are they going to follow open-suse mindthink that further narrows the fields of what is even ***ALLOWED*** to be reported as a bug without being abused? See https://bugzilla.novell.com/show_bug.cgi?id=771516 For a great example of something that used to work, but no longer does -- except under some ideal suse-build environment. It's a real bug report for something that used to work -- bug it now broken, yet the pressure (as documented in the report) has been to tell the user that it is their problem and that their valid, current, suse install the problem -- and is unsupported for a build environment. I had to fight just to have the bug closed as "WONTFIX" -- the developers wanted to close it as INVALID because their build works under their idealized build & test conditions. It used to be products were build to run on released products -- not just factory-only sterile conditions, but this was before openSUSE's Tivoization efforts to turn openSUSE into a platform for platform for developing end-user appliances. It's a retreat from the general linux-distro model of 1 source working anywhere (including other OS's) to an opposite and antithetical extreme of it working on virtually no end-user's real "in-use", production system (clean room build and test only!). This was most of my latest reply on that bug -- as it well details they problem(s) in the in the attitude shift that's caused the problem. The fact that most users are ok with this this (as indicated by the responder's last comment "this is how the community feels about your bug reports)" is a very strong reason why most users wouldn't be comfortable submitting feedback or bugreports. ----------------------- (In reply to comment #11) > If it is faulty please provide a patch to enhance the working version. ==== The purpose of a bug-tracking mechanism is not to force nor beat users into submission for having submitted a bug. It's not to prove the superiority of your build process over theirs. It's not to prove to them that your idealized value of how to run the program works and whatever they are doing is wrong. The point is to get feed back about something that broke for the user -- specifically something that *USED* to work (building samba from RPM) for them. This is a regression. It used to be those were treated as P1/S1 bugs. Now the user is abused for not having an approved setup and the user has to try to explain why they bug report isn't invalid. > It's your build which fails and I don't have the time nor do I see the value > to the project to debug your failing build. ---- At one point in time people cared about the projects and products they shipped on to build in as many configurations (to the point that they build on DIFFERENT OS's). You only care that your build works on some idealized config -- which is very different from the attitude of how open source development used to be done. > It is faulty for your requirements but not for the requirements we have as an > Open Source Software project. ---- The Samba project builds on multiple architectures with no were near the restrictions of the open suse project. Opensuse's version of rpm build is faulty because it doesn't build -- NOT just in all the places that samba builds, but because it doesn't even build on "generic" (not specially tuned) machines as does the original script. Why? because you remove various pieces from samba necessary for it to build all of itself. I cannot submit a patch -- because it would be rejected. I have been that route before -- It's not because I can't submit a patch -- it's because suse only wants certain things two work. If you want to swear that you will accept my patch, I can create one -- but I would bet I'll hear that "users don't want all that other stuff on their machines (ldb, tdb, docs...etc)... You are creating 'use-only' machines by design (that don't easily support modification or developers). I can't create a patch for that as it's a high level decision made about products more than just samba. It's what stallman calls the 'Tivo-ization' of the product. > > I don't care if the bug state stays at wontfix. It demonstrates very > well your unwilling habit to learn and cooperate. ---- Only if I'd never submitted patches that had been rejected would that be true. But having done so, because it's not the direction open suse has decided to take, the bug staying at won't fix is documentation of configurations that suse doesn't support. It isn't a reflection of your development abilities. It documentation of an area that Suse no longer supports. This information is vital if open suse is ever to figure out how their decisions affect those who try to use all of suse as a development platform and the effects of their Tivoization program in moving openSuse to be an appliance development platform rather than a linux development platform. > See also comment #1 to get a picture what our community thinks. ---- It shows me very well the picture of a user that says "I got mine", and the fact that your build, which used to work, no longer works is your problem, and unless you apologize for wasting our time for having even submitted a case were something doesn't work, we are gonna ignore you for having a system we no longer support. Do you really think their weight counts any more than me than that of a petulant 5-year old? This note is a perfect example of why it's pointless to worry about people registering for bugs -- when they will get this type of response to reporting them. It's called "hypocrisy". -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

1 0

[opensuse] connecting my telephone to the internet
by xpol 26 Aug '12

26 Aug '12

Hi all, I would like to connect my telephone to the internet, so as to be able to exploit telephone internet facilities (e.g. google talk). I guees a computer with modem as server should be set up, to link my plain old telephon line to my telephone. Any comments and suggestions? Thank you Paolo -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

7 50

[opensuse] how to update iso image of opensuse releases to the latest (fixed) packages that had been released ever since gold status?
by cagsm 25 Aug '12

25 Aug '12

Good day, I would like to actually advocate for opensuse releasing updated iso images of their opensuse versions after gold status, similar to debian with their r1 r2 r3 rx... releases after their initial r0 of a major release. Why? I remember and experienced myself a great many of bugs that affect upgradability and give endless troubles (for example say hello to perl bootloader packages and other crazy stuff). As until so far, opensuse never releases (I think there was one incident in the past when a vanilla iso got rebuilt because of a serious showstopper bug in the gold media) updated iso files, so no matter how long I wait after a gold of a release and even if I read the often endless bugreports on really serious bugs (with e.g bootloaders, grub, raid1 systemss and many other really pretty bugs (according to my understanding of what a basic system would need to provide for in terms of usability and stability), I will always have to cope with these bugs (maybe long fixed with updates though) and read through bugreports and understand workarounds and fixes, and I often had to use rescue systems to chroot/boot into messed up nonbooting systems and fix stuff so often. So I really really would like to integrate especially these fundamental fixes into the opensuse isos. If opensuse is limited and cant to updated rX versions of their releases, please can anyone tell me how I take the packages from the /update/ repository (what files exactly? index files? simply add the update folder in some way to the iso image, or can I actually really replace the preexisting older versioned rpm inside the iso?) to the precompiled iso images of vanilla opensuse? Maybe some others think of this situation expressed here, as worthy to be tackled and maybe opensuse could also come up with a concept of patch integration into release media and doing updated enhanced revisions of major releases as well. Thanks for explanations and helping. -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

7 25

[opensuse] ssh -x: obscure output delay
by Stefan Gofferje 25 Aug '12

25 Aug '12

Hi, I am having some weird effect when using ssh -x. I have a perl-script '/scripts/colorlogs' that colors log output. I have a bash script '/scripts/mess' that calls 'tail -fn48 /var/log/messages | /scripts/colorlogs'. Now, when I ssh to the machine and call /scripts/mess, everything is just fine. However, when I call 'ssh root@machine -x /scripts/mess', the script is running but the last few lines of the file are missing. Sometimes, the output stops in the middle of a line. It looks like sshd when connected by 'ssh -x' would use some buffer and would only transmit data to the client when the buffer is full. Does anybody happen to know how to avoid this? T:Stefan -- (o_ Stefan Gofferje | SCLT, MCP, CCSA //\ Reg'd Linux User #247167 | VCP #2263 V_/_ Heckler & Koch - the original point and click interface -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

2 2