November 2012 - openSUSE Users - openSUSE Mailing Lists

[opensuse] CINELERRA for 12.2 x86_64
by Basil Chupin 02 Nov '12

02 Nov '12

Are there any Cinelerra users reading this list or can you answer these vexing questions for me, please? In YaST the latest installable version of Cinelerra is 2.2CV - and I have it installed. However, on the heroinewarrior.com site I see that there is version 4.4 released. My questions thererefore are: 1. Has anyone compiled this 4.4 version for oS 12.2 AMD64 from source tar.xz - and perhaps the rpm is available in one of those private repos on opensuse.org? 2. I have downloaded the source code for 4.4 but wonder if it is safe to simply use the instructions given in the tar file to compile it (ie, just run '/.cinlelerra'? Thanks for any feedback. BC -- Using openSUSE 12.2 x86_64 KDE 4.9.2 & kernel 3.6.4-1 on a system with- AMD FX 8-core 3.6/4.2GHz processor 16GB PC14900/1866MHz Quad Channel Corsair "Vengeance" RAM Gigabyte AMD3+ m/board; Gigabyte nVidia GTX550Ti 1GB DDR5 GPU -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

5 10

RE: [opensuse] dbus problems resolved
by j.e.perry＠cox.net 01 Nov '12

01 Nov '12

On Thu, Nov 1, 2012 at 12:45 AM, Patrick Shanahan wrote: > The dbus problems, especially with VirtualBox, discussed here the last > 7-10 days are resolved on my boxes by today's update: > dbus-1-1.5.12-4.10.1 Wed 31 Oct 2012 04:50:46 PM > EDT > libdbus-1-3-32bit-1.5.12-4.10.1 Wed 31 Oct 2012 04:50:44 PM > EDT > libdbus-1-3-1.5.12-4.10.1 Wed 31 Oct 2012 04:50:44 PM > EDT > dbus-1-x11-1.5.12-4.10.1 Wed 31 Oct 2012 04:50:40 PM > EDT > dbus-1-32bit-1.5.12-4.10.1 Wed 31 Oct 2012 04:50:40 PM > EDT > > good job. Yes, that's solved my first problem, too. Thanks; I now have the machine starting up and using the raw disk vmdk. Now to find out how to get beyond a bare, unresponsive grub prompt when I try to start the machine. John Perry -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

1 0

[opensuse] /media/floppy
by Istvan Gabor 01 Nov '12

01 Nov '12

Hello: From SUSE 9.x through openSUSE 11.2 I had this line in /etc/fstab: /dev/fd0 /media/floppy auto noauto,user,async,shortname=winnt,iocharset=utf8 0 0 I also created /media/floppy directory manually. This worked in all suse versions mentioned above. In oS 12.1 I have the same setup, but the manually created /media/floppy directory is always removed at boot. Why is this difference, where is it documented, and how could I fix it, prevent the removing /media/floppy? Thanks, Istvan -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

4 5

[opensuse] Shutdown sometimes hangs
by Andrea Turrini 01 Nov '12

01 Nov '12

Hi all, sometimes I face a strange problem on shutdown: it simply hangs until I press Ctrl-Alt-Del several times (the required number of times is random). At screen I see that plymouth fails and log contains: Oct 07 22:41:57 orodruin.lotr xdm[28730]: Shutting down service lightdm..done Oct 07 22:41:57 orodruin.lotr vboxdrv[28808]: Stopping VirtualBox kernel modules..done Oct 07 22:41:58 orodruin.lotr network-remotefs[28789]: Shutting down (remotefs) network interfaces: Oct 07 22:41:58 orodruin.lotr network-remotefs[28789]: Shutting down service (remotefs) network . . . . . . . . ...done Oct 07 22:41:59 orodruin.lotr network[29301]: Shutting down (localfs) network interfaces: Oct 07 22:41:59 orodruin.lotr network[29301]: eth0 device: Atheros Communications Inc. AR8131 Gigabit Et Oct 07 22:41:59 orodruin.lotr ifdown[29631]: eth0 device: Atheros Communications Inc. AR8131 Gigabit Et Oct 07 22:41:59 orodruin.lotr dhcpcd[29675]: eth0: dhcpcd not running Oct 07 22:41:59 orodruin.lotr dhcpcd[29675]: eth0: exiting Oct 07 22:42:00 orodruin.lotr network[29301]: ..done wlan0 device: Intel Corporation Centrino Wireless-N 1000 Oct 07 22:42:00 orodruin.lotr ifdown[29775]: wlan0 device: Intel Corporation Centrino Wireless-N 1000 Oct 07 22:42:01 orodruin.lotr dhcpcd[29819]: wlan0: dhcpcd not running Oct 07 22:42:01 orodruin.lotr dhcpcd[29819]: wlan0: exiting Oct 07 22:42:03 orodruin.lotr network[29301]: ..doneShutting down service (localfs) network . . . . . . . . ...done Oct 07 22:42:41 orodruin.lotr systemd[1]: plymouth-reboot.service: control process exited, code=exited status=69 Oct 07 22:42:41 orodruin.lotr systemd[1]: Unit plymouth-reboot.service entered failed state. Oct 07 22:42:51 orodruin.lotr systemd[1]: plymouth-reboot.service: control process exited, code=exited status=69 Oct 07 22:42:51 orodruin.lotr systemd[1]: Unit plymouth-reboot.service entered failed state. Oct 07 22:43:09 orodruin.lotr systemd[1]: plymouth-reboot.service: control process exited, code=exited status=69 Oct 07 22:43:09 orodruin.lotr systemd[1]: Unit plymouth-reboot.service entered failed state. Oct 07 22:43:13 orodruin.lotr systemd[1]: plymouth-reboot.service: control process exited, code=exited status=69 Oct 07 22:43:13 orodruin.lotr systemd[1]: Unit plymouth-reboot.service entered failed state. [the same messages repeated several times] Oct 07 22:43:21 orodruin.lotr systemd[1]: plymouth-reboot.service: control process exited, code=exited status=69 Oct 07 22:43:21 orodruin.lotr systemd[1]: Unit plymouth-reboot.service entered failed state. Oct 07 22:43:21 orodruin.lotr systemd[1]: plymouth-reboot.service start request repeated too quickly, refusing to start. Oct 07 22:43:21 orodruin.lotr systemd[1]: systemd-random-seed-save.service start request repeated too quickly, refusing to start. Oct 07 22:43:21 orodruin.lotr systemd[1]: alsa-store.service start request repeated too quickly, refusing to start. Oct 07 22:43:21 orodruin.lotr systemd[1]: plymouth-reboot.service start request repeated too quickly, refusing to start. Oct 07 22:43:21 orodruin.lotr systemd[1]: systemd-random-seed-save.service start request repeated too quickly, refusing to start. Oct 07 22:43:21 orodruin.lotr systemd[1]: alsa-store.service start request repeated too quickly, refusing to start. Oct 07 22:43:22 orodruin.lotr systemd[1]: plymouth-reboot.service start request repeated too quickly, refusing to start. [the same messages repeated several times] Oct 07 22:43:24 orodruin.lotr systemd[1]: plymouth-reboot.service start request repeated too quickly, refusing to start. Oct 07 22:43:24 orodruin.lotr systemd[1]: systemd-random-seed-save.service start request repeated too quickly, refusing to start. Oct 07 22:43:24 orodruin.lotr systemd[1]: alsa-store.service start request repeated too quickly, refusing to start. Oct 07 22:43:27 orodruin.lotr systemd[1]: dbus.service stopping timed out (2). Killing. Oct 07 22:43:27 orodruin.lotr systemd[1]: Unit dbus.service entered failed state. Oct 07 22:43:27 orodruin.lotr systemd[1]: Shutting down. Oct 07 22:43:27 orodruin.lotr systemctl[30129]: Failed to get D-Bus connection: Connection terminated during authentication. Oct 07 22:43:27 orodruin.lotr systemd-journal[282]: Journal stopped (the line at 22:42:03 is as reported by systemd-journal, it is not a copy&paste problem) The first message at 22:42:41 should correspond to my first Ctrl-Alt-Del as the splash was not animated, so I pressed Esc to see the messages, the shutdown sequence was hanged and then I started to press Ctrl-Alt-Del repeatedly (with shorter and shorter interval) to force the shutdown. On a regular shutdown, I obtain: Oct 06 23:24:46 orodruin.lotr network[31080]: ..done wlan0 device: Intel Corporation Centrino Wireless-N 1000 Oct 06 23:24:46 orodruin.lotr ifdown[31558]: wlan0 device: Intel Corporation Centrino Wireless-N 1000 Oct 06 23:24:46 orodruin.lotr dhcpcd[31602]: wlan0: dhcpcd not running Oct 06 23:24:46 orodruin.lotr dhcpcd[31602]: wlan0: exiting Oct 06 23:24:48 orodruin.lotr network[31080]: ..doneShutting down service (localfs) network . . . . . . . . ...done Oct 06 23:24:49 orodruin.lotr systemd[1]: Shutting down. Oct 06 23:24:49 orodruin.lotr systemd-journal[276]: Journal stopped So, since this is clearly a subject for a bug report, the question is: against which component? Best, Andrea PS: nothing has changed at system level between the two shutdowns since no package has been installed/removed/updated. -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

3 4

Re: [opensuse] Support and repairtools: A laughing stock!
by Oddball 01 Nov '12

01 Nov '12

Op 01-11-12 12:30, Oddball schreef: > Op 01-11-12 12:22, Oddball schreef: >> Op 01-11-12 12:10, Oddball schreef: >>> Op 01-11-12 09:53, Oddball schreef: >>>> Op 01-11-12 09:34, Hans Witvliet schreef: >>>>> On Wed, 2012-10-31 at 23:53 +0100, Oddball wrote: >>>>> >>>>>> The other thing is a mistake i made: i never use lvm. >>>>>> This time i thought ok, lets try it. >>>>>> Lvm is not supported yet in Knoppix, so the partitions could not get >>>>>> mounted, only windows and /boot were visible. >>>>>> >>>>> Instead of kroppix, >>>>> you can use either the KDE-live-cd, or the install-12.2-DVD and >>>>> choose >>>>> "live-KDE". LVM and soft raid are recognized there... >>>>> And do the repair work hence on. >>>> >>>> That is an opportunity, but it is the question if it would boot at >>>> all. >>>> Install the bootloader and mkinitrd might be done if the system is >>>> mounted... >>>> I think new install will be better. >>>> Maybe keep /home, and lvm for now, or use kde to transfer /home to >>>> an external hdd, and get rid of lvm. >>>> >>> >>> Nope, lvm is not recognised there... >>> And this was the first and last time i was ever gonna use it. >>> So backing up my files is not an option. >>> >>> I think some serious rethinking should be done about what is the aim >>> on opensuse? >>> >>> Create an os that is useless always broken but looks sometimes shiny? >>> Or a system that uses only tools that work, and that are supported? >>> A repair kit that is usable?, or just something that looks like it, >>> but it is not even good enough to wipe your ass with? (difficult >>> with a laptop or pc i agree.. :-D) >>> >>> I think, if opensuse continous, to go on, on this road, the userbase >>> will shrink further. >>> >>> What is the use of an update tool, if the system is broken? >>> >>> First :1) repair the system, 2) support it, and 3) create a working >>> repairkit, >>> so people who test, do not have use their valuable time on >>> re-installing their system. >>> >>> This is the formula for openSUSE 123. >>> >>> >> >> Who creates a live cd with a password? >> What is the password? >> How to find it? >> >> Also, this is not very clever.... >> One goes away to another pc, or for some coffee: desktop locked! >> > > If you don't know ctrl+alt+2xbackspace, you are f****d. > > Cannot unlock the session because the authentication system failed to > work; > You must kill kscreenlocker (pid 4,836) manually > > It is really funny, is this created to make fun of users? > > Like: no keyboard found: Press any key to continue. > Well, we all had a good laugh, didn't we? To the order of the day: noresume 5 took me to the loginscreen, and system is accessible, as expected. But the root to desktop refusal still exists. We know that we can better drop lvm, as it is not supported anywhere. We know that the commands to get booted, have to be visible at all times, even 'imbedded' into the release notes, or visible somewhere to find easy. But probably only testers would need these commands, and where do you need testers for? (!) -- Enjoy your time around, Oddball (M9.) (Now or never...) OS: Linux 2.6.37.1-1.2-desktop x86_64 Huidige gebruiker: oddball@AMD64x2sfn1 Systeem: openSUSE 11.4 (x86_64) KDE: 4.6.00 (4.6.0) "release 6" -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

1 0

[opensuse] Python and MySQL
by Chuck Payne 01 Nov '12

01 Nov '12

Guys, I am working on teaching myself python and I am trying to get connectors to worked. I followed the following package for Debian/Ubuntu python-mysqldb But, I can't find it on opensuse, what is the equal Can you please let me know what I need to do so I can do this... import MySQLdb Thanks, -- Terror PUP a.k.a Chuck "PUP" Payne (678) 636-9678 ----------------------------------------- Discover it! Enjoy it! Share it! openSUSE Linux. ----------------------------------------- openSUSE -- en.opensuse.org/User:Terrorpup openSUSE Ambassador/openSUSE Member Community Manager -- Southeast Linux Foundation (SELF) skype,twiiter,identica,friendfeed -- terrorpup freenode(irc) --terrorpup/lupinstein Register Linux Userid: 155363 Have you tried SUSE Studio? Need to create a Live CD, an app you want to package and distribute , or create your own linux distro. Give SUSE Studio a try. www.susestudio.com. See you at Southeast Linux Fest, June 8-10, 2012 in Charlotte, NC. www.southeastlinuxfest.org -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

3 2

[opensuse] SuseFirewall2 does not allow pings to ext network?
by Marc Chamberlin 01 Nov '12

01 Nov '12

I have a network setup where I have a openSuSE 11.4 system acting as a firewall between an external and an internal network. Using SuSEfirewall2, I have enabled routing (FW_ROUTE="yes") and masquerading (FW_MASQUERATE="yes") between the two nets, and do not protect the firewall from the internal network. I have also set FW_ALLOW_PING_EXT="yes" in the SuSEfirewall2 configuration file. While I can ping all the devices in the external network from my firewall computer, I CANNOT ping any of the external devices from computers within my internal network. My grokking of the comments on this parameter is that by setting this value to yes, this is exactly what I should be able to do!? I tried pinging both with direct IP addresses and using names resolved via my DNS server with no difference, so that eliminates DNS name resolution as a possible cause. I get the feeling that this is some kind of routing or NAT issue because I am not able to access any other service provided by devices on the external network, from computers on the internal network, either. Although my firewall computer can do so just fine. On the external network I have a router which is the gateway between the external network and the internet. It too is set up to do NAT translations and has a simplified firewall, could it somehow be the cause of why my internal network cannot reach devices on my external network? That seems odd to me but then I don't claim to fully understand the way networks work. What am I missing? Thanks in advance for any ideas/thoughts, I am kinda stumped... Marc -- "The Truth is out there" - Spooky -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

5 16

[opensuse] dbus problems resolved
by Patrick Shanahan 01 Nov '12

01 Nov '12

The dbus problems, especially with VirtualBox, discussed here the last 7-10 days are resolved on my boxes by today's update: dbus-1-1.5.12-4.10.1 Wed 31 Oct 2012 04:50:46 PM EDT libdbus-1-3-32bit-1.5.12-4.10.1 Wed 31 Oct 2012 04:50:44 PM EDT libdbus-1-3-1.5.12-4.10.1 Wed 31 Oct 2012 04:50:44 PM EDT dbus-1-x11-1.5.12-4.10.1 Wed 31 Oct 2012 04:50:40 PM EDT dbus-1-32bit-1.5.12-4.10.1 Wed 31 Oct 2012 04:50:40 PM EDT good job. -- (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

1 0