Re: Kaffeine 0.7.1 findings
Le Saturday 17 September 2005 09:52, Martin Steigerwald(Martin Steigerwald <[EMAIL PROTECTED]>) disait: > Hello, Hi, > > I installed Kaffeine 0.7.1 and found the following problems: > > 1) xine engine doesn't work at all. Whenever I open a movie for > playing, Kaffeine crashes or at least exits silently. These are > the last signs of live: Try to reinstall 'kaffeine-xine'? > 5) The Kaffeine dialog for checking the installations comes up > *every* time I start Kaffeine. It should only come up for the > first time I think like it used to be before. It's a bug (http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=329177). The wizzard fails to create '~/.kde/share/apps/kaffeine/wizard_stamp_v0.7.1' after the first run. 'touch ~/.kde/share/apps/kaffeine/wizard_stamp_v0.7.1' may solve the issue ! -- Glennie "La vie offre toujours deux pentes. On grimpe ou on se laisse glisser." pgp7yKB0uVOQS.pgp Description: PGP signature
Re: KDE 3.4.2 backport now?
Le Samedi 24 Septembre 2005 21:49, Mikhail Ramendik ё a écrit : > Nick Leverton wrote: > > For my part, kdepim 3.4.2 is the other package I had compile errors in. > > But I think that's my PC's fault, as I have similar problems compiling > > kernels on it. This coming week I'm going to set up pbuilder on a > > faster machine which I know has no compile problems, and try again. > > Patrick Dreker's complete backport seems to be here: > > http://mirror.debianforum.de/kde-3.4.2/ I tried it and I got: grave bugs of kdm (4:3.4.1-1 -> 4:3.4.2-2) #324018 - kdm does not have the binary in the package anymore #327273 - kdm does not start xorg server grave bugs of kdeprint (4:3.4.1-1 -> 4:3.4.2-2) #329249 - kdeprint: fails to print anything grave bugs of kdelibs4 (4:3.4.1-1 -> 4:3.4.2-3) #325092 - kmail: Kmail segfault with libqt3c102-mt but works fine with libqt3-mt, but this situation isn't a livable one. Merged with: 320581 grave bugs of kdebase-bin (4:3.4.1-1 -> 4:3.4.2-2) #327039 - CAN-2005-2494: Insecure lockfile handling permits potential local root privilege escalation grave bugs of artsbuilder (4:3.4.1-1 -> 4:3.4.2-2) #329830 - artsbuilder: artsd crashes on startup grave bugs of kmail (4:3.4.1-1 -> 4:3.4.2-1) #326165 - kmail: kamil doesn't install after upgrade to kde 3.4.2 grave bugs of kamera (4:3.4.1-1 -> 4:3.4.2-1) #329673 - kamera: depends on obsolete package libexif10 grave bugs of kghostview (4:3.4.1-1 -> 4:3.4.2-1) #325128 - kghostview: hangs and sucks CPU resouces up, when loading PS file with PDF extension Summary: kdm(2 bugs), kdeprint(1 bug), kdelibs4(1 bug), kdebase-bin(1 bug), kamera(1 bug), kghostview(1 bug), artsbuilder(1 bug), kmail(1 bug) So I did not go on. Klaus
KDevelop and the embedded Vim component
Hi, On Sarge, when installing and configuring the Vim component, it doesn't turn up in the editor list in KDevelop (configure -> editor -> embedded editor). It does, however, work for an application as KWrite. This is, for me, quite a pity. Anyone any suggestions to get this working? Or is it disabled by default? A friend, running Suse x.y, noticed that KDevelop crashed when he enabled the Vim thingy, so I can imagine that this is the case? Regards, Bob -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Kaffeine 0.7.1 findings
Am Sonntag, 25. September 2005 12:39 schrieb Glennie Vignarajah: > > 5) The Kaffeine dialog for checking the installations comes up > > *every* time I start Kaffeine. It should only come up for the > > first time I think like it used to be before. > > It's a bug (http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=329177). > The wizzard fails to create > '~/.kde/share/apps/kaffeine/wizard_stamp_v0.7.1' after the first > run. > 'touch ~/.kde/share/apps/kaffeine/wizard_stamp_v0.7.1' may solve the > issue ! Thanks a lot, maybe add that to the bug report? Anything for the "kaffeine-0.7 crashes when closed" bug? HS -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Kaffeine 0.7.1 findings
Le Sunday 25 September 2005 17:29, Hendrik Sattler(Hendrik Sattler <[EMAIL PROTECTED]>) disait: Hi, > maybe add that to the bug report? Done. -- Glennie "La vie offre toujours deux pentes. On grimpe ou on se laisse glisser." pgptQoBzNEHz7.pgp Description: PGP signature
Re: Kaffeine 0.7.1 findings
El Domingo, 25 de Septiembre de 2005 17:29, Hendrik Sattler escribió: > Anything for the "kaffeine-0.7 crashes when closed" bug? I've downloaded the debian source and reverse-patched the debian diff, and it doesn't crash on closing anymore... Rafael Rodríguez
Re: Kaffeine 0.7.1 findings
Erm.. In fact i've just reapplied the patch, and again works. So i have two scenarios: 1) I build the debian source with 'fakeroot dpkg-buildpackage -uc -us -b'. It crashes on closing 2) building with the typical "./configure --enable-debug=full; make". It won't crash Rafael Rodríguez El Domingo, 25 de Septiembre de 2005 18:50, Rafael Rodríguez escribió: > El Domingo, 25 de Septiembre de 2005 17:29, Hendrik Sattler escribió: > > Anything for the "kaffeine-0.7 crashes when closed" bug? > > I've downloaded the debian source and reverse-patched the debian diff, and > it doesn't crash on closing anymore... > > Rafael Rodríguez
Re: AW: Running KDE 3.4.2 with Transparent Windows
Hm. If I enable RenderAccel, Xorg shoots up to 99% of the CPU time while the splash screen is showing and never finishes booting. The mouse works, but that's it. I have to log in over ssh and kill -9 the Xorg process by hand. Without that set, the transparency and shadow effects are there but the system is also unusably slow. Any idea what the issue could be? My card is an NVidia GeForce3, using their proprietary driver installed the "debian way". Thanks. On Saturday 24 September 2005 12:08 pm, Mart van Santen wrote: > Here also no problems, please be sure to enable the RenderAccel and > AllowGLXWithComposite option in xorg.conf/XF86Config > > Before I enabled RenderAccel it was unusable slow. > > This is my config (only device, module and section settings): > > Section "Device" > Identifier "NVIDIA Corporation NV40 [GeForce 6200 TurboCache]" > Driver "nvidia" > BusID "PCI:1:0:0" > Option "AllowGLXWithComposite" "true" > Option "RenderAccel" "true" > EndSection > > Section "Module" > Load"bitmap" > Load"dbe" > Load"ddc" > Load"extmod" > Load"freetype" > Load"glx" > Load"int10" > Load"record" > Load"type1" > Load"vbe" > EndSection > > Section "Extensions" > Option "Composite" "true" > EndSection > > Regards, > > Mart -- Larry Garfield AIM: LOLG42 [EMAIL PROTECTED] ICQ: 6817012 "If nature has made any one thing less susceptible than all others of exclusive property, it is the action of the thinking power called an idea, which an individual may exclusively possess as long as he keeps it to himself; but the moment it is divulged, it forces itself into the possession of every one, and the receiver cannot dispossess himself of it." -- Thomas Jefferson -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: KDevelop and the embedded Vim component
El Domingo, 25 de Septiembre de 2005 15:56, Bob Vloon escribió: > Anyone any suggestions to get this working? Or is it disabled by default? A > friend, running Suse x.y, noticed that KDevelop crashed when he enabled the > Vim thingy, so I can imagine that this is the case? http://www.yzis.org/ The vimpart never worked well for me. :-( This editor looks a good alternative, but it still needs time and support. -- Alex (a.k.a. suy) - GPG ID 0x0B8B0BC2 http://darkshines.net/ - Jabber ID: [EMAIL PROTECTED]
kaudiocdcreator - How install encoders ?
Hi all, How can I get & install the encoders ? Thanks a lot [Marcelo Cury - Rio de Janeiro, Brazil] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: AW: Running KDE 3.4.2 with Transparent Windows
Larry Garfield wrote (Monday 26 September 2005 4:38 am): > Hm. If I enable RenderAccel, Xorg shoots up to 99% of the CPU time while > the splash screen is showing and never finishes booting. The mouse works, > but that's it. I have to log in over ssh and kill -9 the Xorg process by > hand. Without that set, the transparency and shadow effects are there but > the system is also unusably slow. > > Any idea what the issue could be? My card is an NVidia GeForce3, using > their proprietary driver installed the "debian way". Thanks. I'm using GeForce2 and I get similar behaviour. I think it's probably related to NVidia claiming the RenderAccel is still *experimental*. Shame. Peace, Brendon pgpGvgIXeOL3w.pgp Description: PGP signature
Re: AW: Running KDE 3.4.2 with Transparent Windows
On 25/09/05, Brendon Lloyd Higgins <[EMAIL PROTECTED]> wrote: Larry Garfield wrote (Monday 26 September 2005 4:38 am):> Hm. If I enable RenderAccel, Xorg shoots up to 99% of the CPU time while> the splash screen is showing and never finishes booting. The mouse works, > but that's it. I have to log in over ssh and kill -9 the Xorg process by> hand. Without that set, the transparency and shadow effects are there but> the system is also unusably slow. I have an ATI MOBILITY™ RADEON™ 9000 IGP with 64MB DDR video memory shared video memory (to quote). Would enableing RenderAccel cause a bit of a break (and my having to some how reverse this), or is it safe to enable it? (I think I can also change the 64MB, but I do not konw how off-hand.) Sorry to butt in like this.Thank you in advance, none the less.-- —A watched bread-crumb never boils.—My hover-craft is full of eels.—[...]and that's the he and the she of it.
Re: Automounting experiments
John O'Hagan schrieb: ... Then I upgraded udev and hal, and suddenly pmount needed to be called manually. ... Which raised the question, how was it working in KDE without g-v-m,... If someone could figure out what those changes were, and how to make them (optionally) permanent, KDE's device automounting would be improved. Any thoughts? I think USB mounting is one of the greatest quagmires Linux has to offer; I don't know how much of this is due to - or on the other hand corrigible by - KDE. The mounting of USB-devices seems to involve too many competing systems and I havn't found a document which describes which methods are compatible and which are obsolete. E.g. I just read in LinuxUser that with hal, hotplug is no longer required. Yet Kubuntu, the only distribution I have tried which really works regarding with USB semi-automounting, still has hotplug. hotplug, automount, pmount, udev, hal and many more: this is a real mess only comprehensible to people who live and breathe Linux. Users who simply want to read and write their data are put off. I have spent hours trying to sort these out and many kind people on this list have given useful advice. I had to install a new kernel to even use pmount, which killed my sound and I havn't been able to get this back even with the help of experts on the debian-kernel list and have gone back to my old kernel. There seem to be (say) three generations of USB mounting systems: 1) The good old way: USB partitions showed up in /proc somewhere, e.g. /proc/partitions and one had to write an entry line in /etc/fstab and then mount manually as root or create a desktop icon which mounts and opens the device in konqueror. Problem: the partition labels change with different devices, so you need to either do a bit of detective work occasionally or maintain a whole zoo of /etc/fstab entries. (Completely manual mounting without going through /etc/fstab often doesn't work because often the file system type is unknown. In this case the only thing I have found which will even find the partition is QTparted, a super partitioning tool which is unfortunately incomplete and buggy and no longer maintained or even part of Debian, as far as I can tell.) 2) The semiautomatic way: detective work as above in 1), then use pmount /dev/sd. Device will show up in /media/sd and even on the desktop if you have "show devices" activated in KDE. Problem: needs a modern kernel. 3) The modern way: device icon appears automatically (unmounted) on desktop. Clicking mounts it in Konqueror. Right-clicking allows safe removal. Problem: requires modern kernel and lots of other things. Only few distributions (e.g. Kunbuntu) seem to have gotten this right, certainly not Sarge. I note that even 3) isn't true automounting, so maybe there is a 4). My personal solution is to forget about USB-mounting in my Debian system and to use a Kubuntu Live-CD whenever I need to use USB. Theo Schmidt -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
