Search results for

[opensuse-factory] Re: About dropped packages -- xmms

by Philipp Thomas

* Alexey Eremenko (al4321(a)gmail.com) [20070905 14:50]: > I would like to see XMMS included with openSUSE. As soon as xmms2 is in a usable state, I'm sure it will be included. xmms was dropped because a) it's a gtk1/glib1 package and b) isn't maintained anymore upstreams. Philipp --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

17 years, 2 months

Re: [opensuse-factory] About dropped packages -- xmms

by Stanislav Brabec

Robert Kaiser wrote: > I think it would be good if xmms would be available from build service > at least until GTK1 really gets killed. What about creating GNOME:GNOME1. I can move there related gtk1, libgnome1 packages from GNOME:STABLE and GNOME:UNSTABLE and add xmms. If anybody will want more there, it will be up to anybody to add more GNOME1 packages. -- Best Regards / S pozdravem, Stanislav Brabec software developer --------------------------------------------------------------------- SUSE LINUX, s. r. o. e-mail: sbrabec(a)suse.cz Lihovarská 1060/12 tel: +420 284 028 966 190 00 Praha 9 fax: +420 284 028 951 Czech Republic http://www.suse.cz/ --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

17 years, 2 months

Re: [opensuse-factory] About dropped packages -- xmms

by Patrick Shanahan

* Ain Vagula <avagula(a)gmail.com> [01-01-70 11:34]: > as current version of audacious14 (64-bit) does not like something > about installed curl, it does not play streams. so... Revert to audacious-1.3.2-0.pm.0@x86_64. It does not have a problem with streams, listening to http://66.220.3.52:9010 atm. -- Patrick Shanahan Plainfield, Indiana, USA HOG # US1244711 http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 Registered Linux User #207535 @ http://counter.li.org --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

17 years, 2 months

Re: [opensuse-factory] Re: BulletProofX - a critical feature request for openSUSE

by Stanislav Brabec

Philipp Thomas wrote: > > Ubuntu's "bulletproofX" is mostly hype as they're just utilising an > > existing functionality of GDM, but it would be nice to have the same > > functionality. > > So in order to "test and integrate", you'd first have to implement the same > functionality in a way suitable for openSUSE. Volunteers anyone? It was oneliner. Wed Sep 5 17:45:26 CEST 2007 - sbrabec(a)suse.cz - Search for SaX2 in XKeepsCrashing. Just done. -- Best Regards / S pozdravem, Stanislav Brabec software developer --------------------------------------------------------------------- SUSE LINUX, s. r. o. e-mail: sbrabec(a)suse.cz Lihovarská 1060/12 tel: +420 284 028 966 190 00 Praha 9 fax: +420 284 028 951 Czech Republic http://www.suse.cz/ --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

17 years, 2 months

Re: [opensuse-factory] Grub Problem

by Jonathan D. Arnold / Daemon Dancing

Sid Boyce wrote: > Gabriel wrote: >> Sid Boyce escribió: >>> Felix Miata wrote: >>>> On 2007/08/29 04:25 (GMT+0100) Sid Boyce apparently typed: >>>> >>>>> I had a failing IDE HD as /dev/sda, so I installed 10.3 on a new SATA >>>>> drive /dev/sdb and was booting from it until I removed /dev/sda. The >>>>> SATA drive is now /dev/sda, but it won't boot, just the cursor on the >>>>> top of the screen. >>>>> Booted from DVD to rescue, altered fstab and menu.lst was changed >>>>> from (hd1,0) to (hd0,0), still won't boot and grub commands give >>>>> unrecognised device string errors. >>>>> menu.lst now says >>>>> gfxmenu (hd0,0)/boot/message >>>>> No luck. >>>> Rescue isn't as easy as it used to be. The solution in >>>> http://lists.opensuse.org/opensuse-factory/2007-04/msg00048.html >>>> might be >>>> your solution. >>> Did all that, /dev/disk/by-* tree is sound, looked up "info grub" and >>> "info grub-install", nothing makes any sense. >>> # grub-install /dev/sda1 >>> # grub-install /dev/sda >>> # grub-install (hd0) >>> # grub-install (hd0,0) >>> grub> setup --stage2=/boot/grub/stage2 (hd0) >>> grub> setup --stage2=/boot/grub/stage2 (hd0,0) >>> and other combinations using /dev/sda and /de/sda1 all give "Error 12: >>> Invalid device requested". >>> The odd thing is that when I had the IDE drive installed (/dev/sda) with >>> the SATA (/dev/sdb), it booted off /dev/sdb, after removing the IDE >>> drive, it refused to boot. "fdisk -l /dev/sda" shows the bootable flag >>> on /dev/sda1. I have / and a swap partition on the drive. >>> I can't think of any incantation that will make grub do anything. >>> /dev/disk/by-id: >>> total 0 >>> drwxr-xr-x 2 root root 240 Aug 29 11:13 ./ >>> drwxr-xr-x 5 root root 120 Aug 29 12:02 ../ >>> lrwxrwxrwx 1 root root 9 Aug 29 11:14 >>> ata-WDC_WD3200AAKS-22SBA0_WD-WCAPZ1455963 -> ../../sda >>> lrwxrwxrwx 1 root root 10 Aug 29 11:14 >>> ata-WDC_WD3200AAKS-22SBA0_WD-WCAPZ1455963-part1 -> ../../sda1 >>> lrwxrwxrwx 1 root root 10 Aug 29 11:14 >>> ata-WDC_WD3200AAKS-22SBA0_WD-WCAPZ1455963-part2 -> ../../sda2 >>> lrwxrwxrwx 1 root root 9 Aug 29 11:14 edd-int13_dev80 -> ../../sda >>> lrwxrwxrwx 1 root root 10 Aug 29 11:14 edd-int13_dev80-part1 -> >>> ../../sda1 >>> lrwxrwxrwx 1 root root 10 Aug 29 11:14 edd-int13_dev80-part2 -> >>> ../../sda2 >>> lrwxrwxrwx 1 root root 9 Aug 29 11:14 >>> scsi-SATA_WDC_WD3200AAKS-_WD-WCAPZ1455963 -> ../../sda >>> lrwxrwxrwx 1 root root 10 Aug 29 11:14 >>> scsi-SATA_WDC_WD3200AAKS-_WD-WCAPZ1455963-part1 -> ../../sda1 >>> lrwxrwxrwx 1 root root 10 Aug 29 11:14 >>> scsi-SATA_WDC_WD3200AAKS-_WD-WCAPZ1455963-part2 -> ../../sda2 >>> lrwxrwxrwx 1 root root 9 Aug 29 11:14 >>> usb-HP_Photosmart_C4180_MY6CMH72JX04J7-0:0 -> ../../sdb >>> >>> /dev/disk/by-path: >>> total 0 >>> drwxr-xr-x 2 root root 140 Aug 29 11:13 ./ >>> drwxr-xr-x 5 root root 120 Aug 29 12:02 ../ >>> lrwxrwxrwx 1 root root 9 Aug 29 11:14 >>> pci-0000:00:02.1-usb-0:2.3:1.3-scsi-0:0:0:0 -> ../../sdb >>> lrwxrwxrwx 1 root root 9 Aug 29 11:14 pci-0000:00:04.0-scsi-0:0:0:0 -> >>> ../../sr0 >>> lrwxrwxrwx 1 root root 9 Aug 29 11:14 pci-0000:00:05.0-scsi-0:0:0:0 -> >>> ../../sda >>> lrwxrwxrwx 1 root root 10 Aug 29 11:14 >>> pci-0000:00:05.0-scsi-0:0:0:0-part1 -> ../../sda1 >>> lrwxrwxrwx 1 root root 10 Aug 29 11:14 >>> pci-0000:00:05.0-scsi-0:0:0:0-part2 -> ../../sda2 >>> >>> /dev/disk/by-uuid: >>> total 0 >>> drwxr-xr-x 2 root root 80 Aug 29 11:13 ./ >>> drwxr-xr-x 5 root root 120 Aug 29 12:02 ../ >>> lrwxrwxrwx 1 root root 10 Aug 29 11:14 >>> 85d24d84-6169-4acd-8b05-0d4283199835 -> ../../sda1 >>> lrwxrwxrwx 1 root root 10 Aug 29 11:14 >>> e99d0381-afb9-4678-93bb-14f9afd27247 -> ../../sda2 >>> >>> Regards >>> Sid. >> >> Shouldn't be necessary because you switch the disks, but, did you check >> device.map ? >> >> Regards. >> --------------------------------------------------------------------- >> > > I certainly did and it is the same before and after the problem was > fixed. I also had removed the line "(hd1) /dev/sdb)". > (fd0) /dev/fd0 > (hd0) /dev/sda > I'm perplexed as to why simply removing the IDE drive would cause the > SATA drive to suddenly not boot, must have been something in the stages. Coming to this party a little late, but the reason why the SATA drive wouldn't boot is because by removing the IDE drive, you changed the device name for the SATA drive. It went from hd1/sdb to hd0/sda, and so everywhere GRUB was looking for hd1 or sdb had to be changed to match the new disk layout. I wrote up a short bit about restoring grub here, after they messed with the easy page found on the ubuntu wiki: http://linuxbraindump.org/2007/08/17/restoring-grub Of course, this just allows you to boot grub. You will also have to edit the menu.lst file for it to find the new locations. -- Jonathan Arnold (mailto:jdarnold@buddydog.org) LinuxBrainDump, Linux HowTo's and Tutorials: http://www.linuxbrainddump.org Daemon Dancing in the Dark, an Open OS weblog: http://freebsd.amazingdev.com/blog/ --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

17 years, 2 months

Re: [opensuse-factory] Frequent rpmdb crashes in opensuse 10.3 beta 2

by Juan Erbes

2007/9/5, Michael Schroeder <mls(a)suse.de>: > On Tue, Sep 04, 2007 at 07:47:20PM -0300, Juan Erbes wrote: > > How long time I must run memtest? > > I runed it for many minutes, and not appear any memory error. > > Then your memory is good. A couple of minutes should be enough to > show errors. > > > I changed the voltage from the memorys from 1.9 to 2.1 volts as > > recomended by OCZ: > > http://www.ocztechnology.com/products/memory/ocz_ddr2_pc2_6400_reaper_hpc_e… > > (This is the exact model of the memorys) > > Yesterday I rebuilded the rpmdb, and now after adjusting the memorys > > voltage, the problem continues. > > Sorry, in that case I don't know what's wrong. > I mean that the problem with the rpmdb is derived from a file system access error, because a inmature state of the ahci driver for the SB600/RD580 chipset . For example if I do: dmesg | grep ahci ahci 0000:00:12.0: version 3.0 ahci 0000:00:12.0: controller can't do 64bit DMA, forcing 32bit ahci 0000:00:12.0: controller can't do PMP, turning off CAP_PMP ahci 0000:00:12.0: AHCI 0001.0100 32 slots 4 ports 3 Gbps 0xf impl SATA mode ahci 0000:00:12.0: flags: ncq sntf ilck led clo pio slum part scsi0 : ahci scsi1 : ahci scsi2 : ahci scsi3 : ahci For installing the the 64 bits kde version I must resizing a partition for create a new partition. It was very difficult, and the only way was starting the install process with "safe settings", because the hard disk controller has restarted from time to time (driver ahci). Regards --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

17 years, 2 months

Re: [opensuse-factory] Frequent rpmdb crashes in opensuse 10.3 beta 2

by Michel Salim

On 05/09/07, Juan Erbes <jerbes(a)gmail.com> wrote: > 2007/9/5, Michael Schroeder <mls(a)suse.de>: > > On Tue, Sep 04, 2007 at 07:47:20PM -0300, Juan Erbes wrote: > > > How long time I must run memtest? > > > I runed it for many minutes, and not appear any memory error. > > > > Then your memory is good. A couple of minutes should be enough to > > show errors. > > > > > I changed the voltage from the memorys from 1.9 to 2.1 volts as > > > recomended by OCZ: > > > http://www.ocztechnology.com/products/memory/ocz_ddr2_pc2_6400_reaper_hpc_e… > > > (This is the exact model of the memorys) > > > Yesterday I rebuilded the rpmdb, and now after adjusting the memorys > > > voltage, the problem continues. > > > > Sorry, in that case I don't know what's wrong. > > > > I mean that the problem with the rpmdb is derived from a file system access > error, because a inmature state of the ahci driver for the > SB600/RD580 chipset . For example if I do: > > dmesg | grep ahci > ahci 0000:00:12.0: version 3.0 > ahci 0000:00:12.0: controller can't do 64bit DMA, forcing 32bit > ahci 0000:00:12.0: controller can't do PMP, turning off CAP_PMP > ahci 0000:00:12.0: AHCI 0001.0100 32 slots 4 ports 3 Gbps 0xf impl SATA mode > ahci 0000:00:12.0: flags: ncq sntf ilck led clo pio slum part > scsi0 : ahci > scsi1 : ahci > scsi2 : ahci > scsi3 : ahci > > For installing the the 64 bits kde version I must resizing a partition > for create a new partition. It was very difficult, and the only way > was starting the install process with "safe settings", because the > hard disk controller has restarted from time to time (driver ahci). > Could you set your ATA controller (in BIOS) to compatibility mode? The only problem that might cause is that different modes might expose different drive geometries to the kernel, so you might not be able to switch back later on. -- Michel --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

17 years, 2 months

[opensuse-factory] About choices...

by M9.

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 First of all: I am impressed by the improvement made, compared with 10.2 : The network is up imediately, and finds the sources without any problem. Net-install just fine :-) To the point: The way the choices are made between the install-sources are not good. One should choose net-install, :or: adding media (addon) Not both. The dependencies are unsolvable, and installing is impossible...(when adding the media, *and* the the factory-sources) To nerds this might be obvious, but to noobs, or lesser noobs, like me, this is absolutely not. What happens when adding both might give a totaly wrong impression: fail to install.. ;-( My suggestion is to grey out the option addon, if the net-sources are selected. Realy very much improved.. ;-) Thanks for this nice job, to all who made 10.3 possible... - -- Have a nice day, M9. Now, is the only time that exists. OS: Linux 2.6.22.5-8-default x86_64 Huidige gebruiker: monkey9@tribal-sfn2 Systeem: openSUSE 10.3 (X86-64) Beta3 KDE: 3.5.7 "release 56" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4-svn0 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org iD8DBQFG3ycJX5/X5X6LpDgRAgXIAKCdZ2uqXNIS+KvfWMpbmPK0zKSTTwCdHppt Oo1tzIK8avYo1NdAimbu57I= =njO8 -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

17 years, 2 months

Re: [opensuse-factory] Device already mounted or mountpoint busy error after some beta2 update, I guess

by Rajko M.

On Wednesday 05 September 2007 09:25:10 am Wolfgang Woehl wrote: > Mittwoch, 5. September 2007 Dirk Mueller: > > On Wednesday, 5. September 2007, Wolfgang Woehl wrote: > > > No. And again: I did not configure or invoke device-mapper explivitly. > > > This is a non-tweaked 10.3beta2 install and the mount behaviour changed > > > a day after the install with -- i guess -- an automatic update. > > > > The bug is tracked in #302422 and its marked as fixed for Beta3. please > > try there again. > > Thank you. Sorry for not reading through 302422 up to the multipath-tools > and kpartx change comment. > > How can i "upgrade" to beta3? > Wolfgang 1) Download Beta 3 CD/DVD and update. 2) Using YaST module Update to Factory. I guess it is already frozen in Beta3 Status. This is how I'm going to update. -- Regards, Rajko. --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

17 years, 2 months

Re: [opensuse-factory] Frequent rpmdb crashes in opensuse 10.3 beta 2

by Juan Erbes

2007/9/5, Michel Salim <michel.sylvan(a)gmail.com>: > On 05/09/07, Juan Erbes <jerbes(a)gmail.com> wrote: > > 2007/9/5, Michael Schroeder <mls(a)suse.de>: > > > On Tue, Sep 04, 2007 at 07:47:20PM -0300, Juan Erbes wrote: > > > > How long time I must run memtest? > > > > I runed it for many minutes, and not appear any memory error. > > > > > > Then your memory is good. A couple of minutes should be enough to > > > show errors. > > > > > > > I changed the voltage from the memorys from 1.9 to 2.1 volts as > > > > recomended by OCZ: > > > > http://www.ocztechnology.com/products/memory/ocz_ddr2_pc2_6400_reaper_hpc_e… > > > > (This is the exact model of the memorys) > > > > Yesterday I rebuilded the rpmdb, and now after adjusting the memorys > > > > voltage, the problem continues. > > > > > > Sorry, in that case I don't know what's wrong. > > > > > > > I mean that the problem with the rpmdb is derived from a file system access > > error, because a inmature state of the ahci driver for the > > SB600/RD580 chipset . For example if I do: > > > > dmesg | grep ahci > > ahci 0000:00:12.0: version 3.0 > > ahci 0000:00:12.0: controller can't do 64bit DMA, forcing 32bit > > ahci 0000:00:12.0: controller can't do PMP, turning off CAP_PMP > > ahci 0000:00:12.0: AHCI 0001.0100 32 slots 4 ports 3 Gbps 0xf impl SATA mode > > ahci 0000:00:12.0: flags: ncq sntf ilck led clo pio slum part > > scsi0 : ahci > > scsi1 : ahci > > scsi2 : ahci > > scsi3 : ahci > > > > For installing the the 64 bits kde version I must resizing a partition > > for create a new partition. It was very difficult, and the only way > > was starting the install process with "safe settings", because the > > hard disk controller has restarted from time to time (driver ahci). > > > Could you set your ATA controller (in BIOS) to compatibility mode? The > only problem that might cause is that different modes might expose > different drive geometries to the kernel, so you might not be able to > switch back later on. The system (opensuse) asumes ahci, it not depends on the bios settings. --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

17 years, 2 months

openSUSE Factory search results for query "a"