Re: amarok 2.1 beta1
Well, what about now? I see both qtscript and taglib-extras in repos. 2009/4/22 Modestas Vainius > Hello, > > On 2009 m. April 22 d., Wednesday 11:11:18 Andrea Cavaliero wrote: > > is it possible to have a package of amarok 2.1 beta1 in experimental? > I've > > seen that there are already older snapshots but i was waiting for the > beta > > to try it out. > It is not possible because its dependencies (qtscriptgenerator and taglib- > extras) are waiting in NEW queue[1] for almost 2 months now. > > 1. http://ftp-master.debian.org/new.html > > -- > Modestas Vainius > -- Best regards, Valentin Pavlyuchenko
Re: KDE 4.2.2 unkillable new device dialog
Can you try with new user and empty home directory? AFAIK you should remove configs from home when upgrading KDE. Even if I'm wrong - just try. 2009/5/10 B A > I have posted a similar question on the KDE community list, and gotten some > help, but no resolution to the issue. I think it is Debian-specific. I'm > having an issue with the device notifier. This box is a c2d/4GB with an > nVidia 8600GT (running the nvidia drivers) running Debian/sid. > > It was upgraded from kde 3.5.10 to kde 4.1.x (from experimental) and is > currently running kde 4.2.2-2. > > When I plug a USB device in to the hub (thumb drive, USB hard drive, mp3 > player), it pops up a kde3-style dialog box stating "A new device has been > detected...What would you like to do?" which gives me the options "open in > Dolphin," "download pictures with digicam," or "do nothing." > > However, I cannot do anything with this dialog box. I can't select any of > the options, click Ok, Cancel, or even close the dialog using the kde close > button. In order to get rid of the dialog, I have to log out and back in. I > can manually mount the device from the command line. Note that I had a very > similar setup on a laptop, and did not display this behavior. > > The other day, I tried to burn a CD. I inserted a blank into the drive, and > started k3b. The splash screen came up, and it went gray. I couldn't get rid > of it, not even with a pkill -9 k3b. > > I was running kde 4.2.2-2 on Debian/sid on my laptop before I had to turn > it in, and didn't have any problems. > > It was suggested that part of kde 3.5 was still installed on the machine, > and I do have libs, etc. because I obviously have kde3 apps still installed, > like k3b and amarok. bcooksley, a kde dev, suggested that the apps are > waiting for I/O, which is one of the few ways to make an application > "unkillable. > > I did have a bunch of old .DCOP sockets in my home directory, but deleted > them, and the behavior persists. I also noticed that when I plugged in a > device, it started up gvfs-hal-volume-monitor, gvfsd-burn and > gvfs-gphoto2-volume-monitor, > which appear to be decidedly non-kde. > > Any idea why this strange behavior is occurring on my system and what I can > do to fix it? > > Thanks, > --b > -- Best regards, Valentin Pavlyuchenko
Re: amarok 2.1 beta1
Hello, On 2009 m. May 10 d., Sunday 23:28:28 Valentin Pavlyuchenko wrote: > Well, what about now? > I see both qtscript and taglib-extras in repos. http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=528082 -- Modestas Vainius signature.asc Description: This is a digitally signed message part.
Re: Wrong keyboard after KDE4.2 startup, ok after a while [solved]
Hi all, I kinda solved my problem: > > On Sunday, 2009-04-26, Stephan Hachinger wrote: (...) > > > I'm having a bizarre problem here. My system is lenny, with qt 4.4.3, > > > X.Org > > > 1.4.2 and recompiled KDE 4.2.2 from unstable. The kernel is a > > > self-compiled > > > 2.6.28. keyboard layouts are deactivated in kcontrol; activating them > > > didn't change anything to the better. > > > > > > After I start KDE, the keyboard layout for ~the first 2 apps I start is > > > US. > > > Typically I have this in the program starter (lancelot or kickoff), and in > > > the first iceweasel I start afterwards. For all apps I start then (e.g. if (...) I managed to get the kde keyboard layout switcher to work. Before, I had problems with it - it was disabling the arrow keys etc. Here, selecting "Evdev-managed keyboard" as keyboard type instead of the generic 105 key did the trick. Now this gives me a German layout in all apps I start. A problem remains with lancelot / kickoff, which is apparently started before the layout switcher is initialized. Here I chose, as a dirty workaround, to kill lancelot via autostart. This means it is restarted the first time I click on the K menu. Meanwhile, I've recompiled hal, xorg and evdev from debian sid; I have however not yet tested if this makes the problem disappear as a whole. Anyway, I think I won't file a KDE bugreport about this story because I still think that the problem here is related to my weird system setup. Cheers, Stephan -- To UNSUBSCRIBE, email to debian-kde-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Not Mouse or Keyboard in login screen
Hi, Today I was install Debian in a friend's PC. What is my surprise when after make a dist-upgrade to sid branch in the login screen the mouse and keyboard are dead. Keyboard and Mouse are installing in PS/2 Any suggestion ? Thanks in advance, GUAN
Re: Not Mouse or Keyboard in login screen
Am Montag, 11. Mai 2009 schrieb Guan de dio: > Today I was install Debian in a friend's PC. > What is my surprise when after make a dist-upgrade to sid branch in > the login screen the mouse and keyboard are dead. Can you make sure this is not connected to the recent X11 upgrades? The newest packages remove the former -mouse and -kbd package to replace them with xserver-xorg-input-evdev. Christoph
Re: Not Mouse or Keyboard in login screen
Well, I'm not sure I installed a old Debian etch in the PC and after that I make the dist-upgrade to sid branch. Apparently the upgrade was successful, but the mouse and kbd did not make nothing in the login. I download a new lenny CD to try the installation with a most recent brunch. I don't know what is happen GUAN 2009/5/11 Christoph Burgmer > Am Montag, 11. Mai 2009 schrieb Guan de dio: > > Today I was install Debian in a friend's PC. > > What is my surprise when after make a dist-upgrade to sid branch in > > the login screen the mouse and keyboard are dead. > > > Can you make sure this is not connected to the recent X11 upgrades? The > newest packages remove the former -mouse and -kbd package to replace them > with xserver-xorg-input-evdev. > > > Christoph >
