I notice that a lot of MIDI programs require jack-audio-connection-kit in order to
Do I need to somehow terminate pulseaudio before running jack, or will there be no
problem with both on at the same time?
Will jack-controlled applications respond to the volume slider of kmix, even though
this is used by pulseaudio?
And, when I am finished noodling, I will terminate jack, but do I need to somehow
restart pulseaudio, or will it simply be working when jack stops?
On Sat 13 February 2010 4:01:52 am Frode Nicolaisen wrote:
> Using the KDE version of fedora 12 and notice that the kplayer doesnt play
> mp3s via samba/networkshares. It plays for some seconds and just crash!
> Anyone know what to do to fix it!?
Please ask this on the proper list for KDE-on-Fedora support.
This list is for the discussion of topics related to the development of
== http://hackersramblings.wordpress.com | http://rix.si/ ==
I have installed both fluidynth and timidity++. I set kmid2 to start timidity at
start-up and have a midi mapper file selected. I left the default settings in kmid2
for timidity alone (I do not know whether a sound font will be automatically loaded,
nor do I know how to load one in timidity).
When I select a midi file to play, the progress indicator suggests that the file is
indeed playing, but there is no sound.
I have checked kmix and all the available volume sliders are up (I checked if other
ones were available, but I don't think any of the ones not shown would be needed or
have any use).
I have no idea how timidity or fluidsynth work. In the past, I used to expressly
install an old SoundBlaster Live card with built-in midi for the purpose, but,
according to the kmid2 documentation, soft-synths such as timidity and fluidsynth
should be sufficient.
I decided to give 4.4 a try and it does feel better than the beta that I tried
and made me go back to 4.3 but I cannot get kontact to work for me. kmail,
kaddressbook, korganizer etc all work fine standalone but kontact refuses to
I made sure that akonadi is running before starting it up, removed kontactrc
and .kde/share/apps/kontact and I get messages like these in the console:
> <unknown program name>(2118)/: Communication problem with "kontact" , it
> probably crashed. Error message was: "org.freedesktop.DBus.Error.NoReply"
> : " "Did not receive a reply. Possible causes include: the remote
> application did not send a reply, the message bus security policy blocked
> the reply, the reply timeout expired, or the network connection was
> broken." "
> kontact(2119)/khtml (caret) DOM::Selection::moveTo: Selection[ Position(
> 0x0 "null" : 0 ) Position( 0x0 "null" : 0 ) Position( 0x0 "null" : 0 )
> Position( 0x0 "null" : 0 ) 1 ] Position( 0x0 "null" : 0 ) Position( 0x0
> "null" : 0 )
:: Christos Lazaridis +41 22 76 70573 ( office ) ::
:: PhD Student, CMS Group +41 76 26 82453 ( cell ) ::
:: Department of Physics CERN/32 3-B16 ::
:: University of Wisconsin-Madison http://chrislaz.net ::
:: There is still something in everything I do that defeats me, ::
:: makes me dissatisfied, challenges me to further effort. ::
:: Sometimes I rise above my level, sometimes I fall below it, ::
:: but always I fall short of the things I dream. ::
:: ~ H.G. Wells, The Island of Dr. Moreau ::
A couple of days ago I started getting artifacts on my netbook's desktop. The
attached is approximately the top left-hand quarter of my screen. Any idea
what could be causing this?
New to KDE4? - get help from http://userbase.kde.org
Just found a cool new feature? Add it to UserBase
For some reason I often see a big yellow border around GVIM when I run
it. Never noticed it until today and use gvim all the time. I assume
this is something kde 4.4 is doing since gvim or vim have not been
updated recently. Have not applied todays updates to see if it affect it.
After starting system this evening I see no display. Can't get terminal using
alt-F* keys either. Only way to get in was via ssh. Below is the crash part of
After upgrade last night it kept working OK but didn't reboot then. Actaully
upgrade to 4.4 several days with several intervening boots, until today...
Not sure if this is KDE problem or just another radeon driver problem?
(II) RADEON(0): Acceleration enabled
(==) RADEON(0): DPMS enabled
(==) RADEON(0): Silken mouse enabled
(II) RADEON(0): Set up textured video
Output CRT1 disable success
(II) RADEON(0): DIG0 transmitter: Coherent Mode enabled
Output DIG0 transmitter setup success
Blank CRTC 0 success
Disable CRTC memreq 0 success
Disable CRTC 0 success
Blank CRTC 1 success
Disable CRTC memreq 1 success
Disable CRTC 1 success
0: /usr/bin/X (xorg_backtrace+0x28) [0x49ecc8]
1: /usr/bin/X (0x400000+0x61cf9) [0x461cf9]
2: /lib64/libpthread.so.0 (0x3b12a00000+0xf0f0) [0x3b12a0f0f0]
3: /usr/bin/X (xf86GetPrimaryOutput+0x35) [0x4819a5]
4: /usr/bin/X (xf86SetDesiredModes+0x8b) [0x483dbb]
5: /usr/lib64/xorg/modules/drivers/radeon_drv.so (0x7f462205f000+0x46f2e)
6: /usr/bin/X (AddScreen+0x1d4) [0x4278b4]
7: /usr/bin/X (InitOutput+0x7b4) [0x470164]
8: /usr/bin/X (0x400000+0x21c5a) [0x421c5a]
9: /lib64/libc.so.6 (__libc_start_main+0xfd) [0x3b11e1eb1d]
10: /usr/bin/X (0x400000+0x219a9) [0x4219a9]
Segmentation fault at address 0xa0
Fatal server error:
Caught signal 11 (Segmentation fault). Server aborting
A few days ago I got KDE 4.4.0 (without RCx) pushed to my rawhide partition.
Is the version in rawhide identical to the one that was today officially
I ask, because I still experience the 'akonadi/kmail'-issue. Does anyone have
some more info on this? Shouldn't this be a release blocker?