March 2010 - openSUSE Users - openSUSE Mailing Lists

[opensuse] Sound problem with openSUSE 11.2
by Bogdan Cristea 19 Mar '10

19 Mar '10

Does anyone experience sound problem with openSUSE 11.2 with KDE ? I have two systems, an AMD Athlon on 64 bits and an Intel Atom on 32 bits, both don't have sound. Anyone knows a way to solve this issue ? -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse+help(a)opensuse.org

4 4

[opensuse] Update Wireshark?
by James Knott 19 Mar '10

19 Mar '10

The latest OpenSUSE version of Wireshark is 1.0.0, but the current version is 1.2.6 and 1.4.x will be out shortly. Is there an updated OpenSUSE package? Or will it be necessary to get the latest from wireshark.org? tnx jk BTW, users of Wireshark may be interested in this book: http://www.wiresharkbook.com -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse+help(a)opensuse.org

3 8

[opensuse] open a daa file
by William 19 Mar '10

19 Mar '10

I have a daa file I need to open O would like to know how to open it ? -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse+help(a)opensuse.org

2 1

[opensuse] Unlocking a locked file
by Stan Goodman 19 Mar '10

19 Mar '10

My VirtualBox program has become corrupted, and I wish to remove it and start over again from scratch. At the moment, it won't start at all. I find that reinstalling over what is there is not permitted, because there is a locked file. How can I unlock this file? This is not the ose version of the program, I downloaded it from the VBox site. This is what happens when I try to uninsstall: # rpm -e VirtualBox* error: package VirtualBox-3.1-3.1.4_57640_openSUSE111-1.x86_64.rpm is not installed # On the other hand, here is what happens when I try to reinstall: # rpm -U VirtualBox* warning: VirtualBox-3.1-3.1.4_57640_openSUSE111-1.x86_64.rpm: Header V4 DSA signature: NOKEY, key ID 6dfbcbae package VirtualBox-3.1-3.1.4_57640_openSUSE111-1.x86_64 is already installed # When I try to reinstall from the user prompt, the response is: rpm -U VirtualBox* warning: VirtualBox-3.1-3.1.4_57640_openSUSE111-1.x86_64.rpm: Header V4 DSA signature: NOKEY, key ID 6dfbcbae error: can't create transaction lock on /var/lib/rpm/__db.000 How can I remove VirtualBox from the system completely, so that I can install a clean program? -- Stan Goodman Qiryat Tiv'on Israel -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse+help(a)opensuse.org

5 5

[opensuse] how to define partition size in sectors?
by Istvan Gabor 19 Mar '10

19 Mar '10

Hello: I'd like to create partitions on a new hard drive and would like to give the partitions' sizes in sectors instead of bytes/megabytes/gigabytes. I tried with both cfdisk and fdisk but they take partition size input in megabytes even if units are set to sectors. How could I define the partitions' sizes in sectors? (I want to clone data from other partition and I want the new partition to have exactly the same size as the old one.) Thanks, Istvan -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse+help(a)opensuse.org

4 8

[opensuse] Re: Unlocking a locked file
by Joachim Schrod 19 Mar '10

19 Mar '10

Stan Goodman wrote: > At 02:55:20 on Friday Friday 19 March 2010, Joachim Schrod > <jschrod(a)acm.org> wrote: >> Stan Goodman wrote: >> > At 13:36:05 on Wednesday Wednesday 17 March 2010, Stan Goodman >> > >> > <stan.goodman(a)hashkedim.com> wrote: >> >> At 21:19:58 on Tuesday Tuesday 16 March 2010, Joachim Schrod >> >> >> >> > > WARNING: Can't read >> >> > > module >> >> > > >> >> > > /lib/modules/2.6.27.45-0.1-default/weak-updates/updates/vboxvf >> >> > >s.ko: No such file or directory >> >> > > WARNING: Can't read >> >> > > module >> >> > > >> >> > > /lib/modules/2.6.27.45-0.1-default/weak-updates/updates/vboxad >> >> > >d.ko: No such file or directory >> >> > > >> >> > > # find -name "vbox*.ko" >> >> > > ./lib/modules/2.6.27.45-0.1-default/misc/vboxnetadp.ko >> >> > > ./lib/modules/2.6.27.45-0.1-default/misc/vboxnetflt.ko >> >> > > ./lib/modules/2.6.27.45-0.1-default/misc/vboxdrv.ko >> >> > > >> >> > > ./lib/modules/2.6.27.45-0.1-default/weak-updates/updates/vboxv >> >> > >fs.ko >> >> > > ./lib/modules/2.6.27.45-0.1-default/weak-updates/updates/vboxa >> >> > >dd.ko ./lib/modules/2.6.27.39-0.2-default/misc/vboxnetadp.ko >> >> > > ./lib/modules/2.6.27.39-0.2-default/misc/vboxnetflt.ko >> >> > > ./lib/modules/2.6.27.39-0.2-default/misc/vboxdrv.ko >> >> > > ./lib/modules/2.6.27.39-0.2-trace/misc/vboxnetadp.ko >> >> > > ./lib/modules/2.6.27.39-0.2-trace/misc/vboxnetflt.ko >> >> > > ./lib/modules/2.6.27.39-0.2-trace/misc/vboxdrv.ko >> >> > > ./lib/modules/2.6.27.39-0.2-debug/misc/vboxnetadp.ko >> >> > > ./lib/modules/2.6.27.39-0.2-debug/misc/vboxnetflt.ko >> >> > > ./lib/modules/2.6.27.39-0.2-debug/misc/vboxdrv.ko >> >> > > >> >> > > ./lib/modules/2.6.27.45-0.1-trace/weak-updates/updates/vboxvfs >> >> > >.ko >> >> > > ./lib/modules/2.6.27.45-0.1-trace/weak-updates/updates/vboxadd >> >> > >.ko ./lib/modules/2.6.27.42-0.1-trace/updates/vboxvfs.ko >> >> > > ./lib/modules/2.6.27.42-0.1-trace/updates/vboxadd.ko >> > >> > In a nutshell, the problem has been reduced to redirecting the two >> > symlinks to kernel modules of the proper version. At present, they >> > are as follows: >> > vboxvfs.ko -> /lib/modules/2.6.27.42-0.1-default/updates/vboxvfs.ko >> > vboxadd.ko -> /lib/modules/2.6.27.42-0.1-default/updates/vboxadd.ko >> > >> > whereas they should be instead >> > ~vboxvfs.ko -> /lib/modules/2.6.27.45-0.1-default/updates/vboxvfs.ko >> > ~vboxadd.ko -> /lib/modules/2.6.27.45-0.1-default/updates/vboxadd.ko >> >> No. The symlink in weak-updates/ should point to existing files in >> the updates/ subdirectory of an older kernel. >> >> One must not have the same kernel modules in weak-updates/ and in >> updates/ of one kernel release, that'll cause havoc. (A symlink to >> an existing file is the same as having that file there.) >> >> > and I should do (from the directory containing the links: >> > ln -sf vboxvfs /lib/modules/2.6.27.45-0.1-default/updates/vboxvfs.ko >> > ln -sf vboxadd /lib/modules/2.6.27.45-0.1-default/updates/vboxadd >> >> No. Check that the files really exist in >> /lib/modules/2.6.27.42-0.1-trace/updates/, and that there are no >> symlinks. > > They don't, as I discovered yesterday after I wrote. Here is the search: > > # find -name "vboxadd.ko" > ./lib/modules/2.6.27.45-0.1-default/weak-updates/updates/vboxadd.ko > ./lib/modules/2.6.27.45-0.1-trace/weak-updates/updates/vboxadd.ko > ./lib/modules/2.6.27.42-0.1-trace/updates/vboxadd.ko > # find -name "vboxvfs.ko" > ./lib/modules/2.6.27.45-0.1-default/weak-updates/updates/vboxvfs.ko > ./lib/modules/2.6.27.45-0.1-trace/weak-updates/updates/vboxvfs.ko > ./lib/modules/2.6.27.42-0.1-trace/updates/vboxvfs.ko > # > > In fact, the directory /lib/modules/2.6.27.42-0.1-default/ doesn't exist. Yes, that was established several posts ago. Please read my post again, with careful attention to the directory names that I used. I directed you to a different directory, namely to the ...trace/ directory, not to the ...default/ directory. That's where I suspect that the real files are. If yes, that's where the symlinks should point to. *Then*, one can call "depmod -a" and try to load them. Your find statement is not sufficient to show the state of your system. It just outputs directory entries, not if these are symlinks or real files. You may add -ls as an option to see that. Joachim -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Joachim Schrod Email: jschrod(a)acm.org Roedermark, Germany -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse+help(a)opensuse.org

3 2

[opensuse] Re: Unlocking a locked file
by Joachim Schrod 19 Mar '10

19 Mar '10

Stan Goodman wrote: > At 13:36:05 on Wednesday Wednesday 17 March 2010, Stan Goodman > <stan.goodman(a)hashkedim.com> wrote: >> At 21:19:58 on Tuesday Tuesday 16 March 2010, Joachim Schrod >> > > >> > > WARNING: Can't read >> > > module >> > > /lib/modules/2.6.27.45-0.1-default/weak-updates/updates/vboxvfs.ko: >> > > No such file or directory >> > > WARNING: Can't read >> > > module >> > > /lib/modules/2.6.27.45-0.1-default/weak-updates/updates/vboxadd.ko: >> > > No such file or directory >> > > >> > > # find -name "vbox*.ko" >> > > ./lib/modules/2.6.27.45-0.1-default/misc/vboxnetadp.ko >> > > ./lib/modules/2.6.27.45-0.1-default/misc/vboxnetflt.ko >> > > ./lib/modules/2.6.27.45-0.1-default/misc/vboxdrv.ko >> > > ./lib/modules/2.6.27.45-0.1-default/weak-updates/updates/vboxvfs.ko >> > > ./lib/modules/2.6.27.45-0.1-default/weak-updates/updates/vboxadd.ko >> > > ./lib/modules/2.6.27.39-0.2-default/misc/vboxnetadp.ko >> > > ./lib/modules/2.6.27.39-0.2-default/misc/vboxnetflt.ko >> > > ./lib/modules/2.6.27.39-0.2-default/misc/vboxdrv.ko >> > > ./lib/modules/2.6.27.39-0.2-trace/misc/vboxnetadp.ko >> > > ./lib/modules/2.6.27.39-0.2-trace/misc/vboxnetflt.ko >> > > ./lib/modules/2.6.27.39-0.2-trace/misc/vboxdrv.ko >> > > ./lib/modules/2.6.27.39-0.2-debug/misc/vboxnetadp.ko >> > > ./lib/modules/2.6.27.39-0.2-debug/misc/vboxnetflt.ko >> > > ./lib/modules/2.6.27.39-0.2-debug/misc/vboxdrv.ko >> > > ./lib/modules/2.6.27.45-0.1-trace/weak-updates/updates/vboxvfs.ko >> > > ./lib/modules/2.6.27.45-0.1-trace/weak-updates/updates/vboxadd.ko >> > > ./lib/modules/2.6.27.42-0.1-trace/updates/vboxvfs.ko >> > > ./lib/modules/2.6.27.42-0.1-trace/updates/vboxadd.ko > > In a nutshell, the problem has been reduced to redirecting the two > symlinks to kernel modules of the proper version. At present, they are as > follows: > vboxvfs.ko -> /lib/modules/2.6.27.42-0.1-default/updates/vboxvfs.ko > vboxadd.ko -> /lib/modules/2.6.27.42-0.1-default/updates/vboxadd.ko > > whereas they should be instead > ~vboxvfs.ko -> /lib/modules/2.6.27.45-0.1-default/updates/vboxvfs.ko > ~vboxadd.ko -> /lib/modules/2.6.27.45-0.1-default/updates/vboxadd.ko No. The symlink in weak-updates/ should point to existing files in the updates/ subdirectory of an older kernel. One must not have the same kernel modules in weak-updates/ and in updates/ of one kernel release, that'll cause havoc. (A symlink to an existing file is the same as having that file there.) > and I should do (from the directory containing the links: > ln -sf vboxvfs /lib/modules/2.6.27.45-0.1-default/updates/vboxvfs.ko > ln -sf vboxadd /lib/modules/2.6.27.45-0.1-default/updates/vboxadd No. Check that the files really exist in /lib/modules/2.6.27.42-0.1-trace/updates/, and that there are no symlinks. Then do cd /lib/modules/`uname -r`/weak-updates ln -sf /lib/modules/2.6.27.42-0.1-trace/updates/vbox*.ko . depmod -a Then, run modprobe vboxvfs and see if error messages are output to console or to /var/log/messages. If not, the kernel module problem has probably been resolved. If yes, somebody knowledgable about VirtualBox must help you to check what went wrong with your installation. Joachim -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Joachim Schrod Email: jschrod(a)acm.org Roedermark, Germany -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse+help(a)opensuse.org

4 4

Re: [opensuse] Pinentry problem
by Petr Uzel 19 Mar '10

19 Mar '10

On Wed, Mar 17, 2010 at 11:59:55AM -0400, Anton Aylward wrote: > Petr Uzel said the following on 03/17/2010 11:01 AM: > > > > Graphical pinentry's have precedence over pinentry-curses. If DISPLAY > > is not set, then pinentry-{qt,gtk-2} runs pinentry-curses instead. > > If you don't like this behavior, you can modify gpg-agent.conf > > as mentioned above. > That is not the case. > From tty2 I ran 'sh - /usr/bin/pinentry' > I recorded it with 'script' > Sadly, "who am i" doens't seem to work within script, so you'll have to > take my word that this was on tty2 > > The result is: > > Script started on Wed 17 Mar 2010 11:49:22 AM EDT > anton@BigBoy:~/tmp> > anton@BigBoy:~/tmp> unset DISPLAY > anton@BigBoy:~/tmp> sh -x /usr/bin/pinentry > + kde_running= > + '[' -n '' ']' > + '[' -n '' ']' > + arg= > + display= > + '[' -n '' ']' > + '[' -n '' -a x = 4x -a -f /usr/bin/pinentry-qt4 ']' > + '[' -n '' -a -f /usr/bin/pinentry-qt ']' > + '[' -f /usr/bin/pinentry-gtk-2 ']' > + export PINENTRY_BINARY=/usr/bin/pinentry-gtk-2 > + PINENTRY_BINARY=/usr/bin/pinentry-gtk-2 > + exec /usr/bin/pinentry-gtk-2 > OK Your orders please Yes, that's expected. Most likely I wasn't clear before. You are right that in such case it is pinentry-gtk-2, what is 'selected' by /usr/bin/pinentry script. But since it figures out there is no $DISPLAY, it runs pinentry-curses-like interface which is embedded into pinentry-gtk-2 binary (as well as to other graphical pinentry's). You can verify this by doing the following at tty2: gpg --sign some_file -> pinentry-curses dialog appears, don't close it switch to another console and issue ps aux | grep pinentry -> it shows it is actually pinentry-gtk-2, which does the curses-like interface. > ^C > anton@BigBoy:~/tmp> exit > > Script done on Wed 17 Mar 2010 11:50:02 AM EDT > > > That's what I eamn about the if/elseif chain being wrong. > That code segment reads > > > # otherwise test if pinentry-gtk-2 is installed > elif [ -f /usr/bin/pinentry-gtk-2 ] > then > export PINENTRY_BINARY="/usr/bin/pinentry-gtk-2" > # otherwise test if pinentry-qt4 exists although KDE is not detected > elif [ -f /usr/bin/pinentry-qt4 ] > then > export PINENTRY_BINARY="/usr/bin/pinentry-qt4" > # otherwise test if pinentry-qt exists although KDE is not detected > elif [ -f /usr/bin/pinentry-qt ] > then > export PINENTRY_BINARY="/usr/bin/pinentry-qt" > # pinentry-curses is installed by default > else > export PINENTRY_BINARY="/usr/bin/pinentry-curses" > fi > > > > So if -gtk-2 or -qt4 or -qt exist they well be used > EVEN IF KDE IS NOT DETECTED. And what would you suggest to use instead? > I think this is WRONG ! Pinentry-curses is used as a fallback only if there is no graphical pinentry installed. That's intentional. Since every graphical pinentry provides also embedded pinentry-curses interface, this is fine IMHO. > The test for KDE only happens if DISPLAY is set. If DISPLAY is not set, why should we care about KDE/GNOME? It even does not make sense. Or am I missing something? > So what about other window managers? Sorry, I don't get this question. Anyway, this whole question about which pinentry version should be ran under various circumstances seems to be totally unrelated to the original issue with keychain freezing. Did you manage to test the workaround? Thanks, Petr -- Petr Uzel, openSUSE Boosters Team IRC: ptr_uzl @ freenode

2 7

[opensuse] Minor issues
by eddie 19 Mar '10

19 Mar '10

I have a couple of minor issues that irritate me with kde4. Does anyone know how to globally switch off grouping on the taskbar. One can do it on a temporary basis with individual programs but this is tedious. I like to see everything on the taskbar and not have to click to find out what I've got and where it is. Another thing is the virtual desktops. One can name them but there seems to be no way to display the name. So what's the point? I hate to say this (but not really :-) ) but I did not have these problems in KDE3 and annoys me that these functions which allow individuals to personalise their desktop has been removed. Not wanting to start a flame war or whatever but would be grateful if someone in the know can explain to me how I can accomplish these two little tasks. Many thanks. Eddie -- Delight thyself also in the Lord and He shall give thee the desires of thine heart. Psalm. 37:4 -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse+help(a)opensuse.org

3 5

[opensuse] kbluetooth connection problems
by Michael S. Dunsavage 18 Mar '10

18 Mar '10

I have an HTC Fuze cell phone (running windows mobile) and I'm trying to connect to it via Kbluetooth. However when trying to add the phone as a device, kbluetooth complains that the device "does not support input service" Has anyone connected a windows mobile phone like this to a linux machine? It connects fine through windows bluetooth. -- Michael S. Dunsavage -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse+help(a)opensuse.org

2 1