Even the distribution sidux has already replaced KTorrent2.2.7 with 3.1
while it is still a kde3 desktop environment.
--
New Upstream + package merge ktorrent 3.1
https://bugs.launchpad.net/bugs/234514
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
When can we expect a new KTorrent package from 3.1?
PS.There had been rumours KTorrent 3.1.1 would come out this weekend.
--
New Upstream + package merge ktorrent 3.1
https://bugs.launchpad.net/bugs/234514
You received this bug notification because you are a member of Ubuntu
Bugs, which is subsc
Hello world?
--
ktorrent 3.1 beta 2
https://bugs.launchpad.net/bugs/234514
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
I tried it out and i still get the busybox...
Also, it seems like i have an nForce4 not an nForce3 chip.
--
[alpha4 and 5] I get a busybox on one of my computers
https://bugs.launchpad.net/bugs/195524
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
The final release of KTorrent is already out! Can i please request you
to update this package in the backports of 8.04?
--
ktorrent 3.1 beta 2
https://bugs.launchpad.net/bugs/234514
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubu
I am sorry, i do not know which package this would involve... i have not
tested this lately, but i will try it out again with the new 8.10
release to see whether this issue seems to be fixed or not. So i will
report back later.
--
[alpha4 and 5] I get a busybox on one of my computers
https://bugs
+1, happens here too.
--
ktorrent-kde4 IP filter not loaded
https://bugs.launchpad.net/bugs/197226
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman
Well, as i know it, the busybox is a very spartain terminal where you
cannot do that much. Someone told me once that a busybox only happens
when there is something seriously wrong with the computer, and seeing
this does not happen with dapper nor gutsy, i thought i would be a good
idea to report th
Can this please be released? There was a socket leak fixed
http://ktorrent.org/forum/viewtopic.php?p=12402&sid=1b9839128d486e3115b0ce894194e97a
and currenty in RC1 the limit of 1024 is reached soon with 2 torrents
with each one file in it.
Please?
--
[FF exception] New upstream release ktorrent-
Public bug reported:
The desktop-cd does not boot properly, as it goes into a busybox.
My hardware:
AMD64 3200+
asus a8n sli-deluxe with nforce3 chipset
asus nvidia 6600gt 128MB ram
1GB OCZ
It is also good to note that gutsy and dapper do run fine on this pc, so
it got to be something new.
** A
Right.
Sorry guys, the spam load i got during the holidays did me remove some legimit
mail too...
All looks fine here for gamin.
The leak was not an issue anymore when i upgraded to dapper.
I remember the cpu was still bumpy on gamin though in the beginning of
my dapper time, but i think have no
Public bug reported:
I installed
apt-cache policy kpersonalizer
kpersonalizer:
Geïnstalleerd: 4:3.5.4-0ubuntu1~dapper2
Kandidaat: 4:3.5.4-0ubuntu1~dapper2
Versietabel:
*** 4:3.5.4-0ubuntu1~dapper2 0
500 http://kubuntu.org dapper/main Packages
100 /var/lib/dpkg/status
4
Hmm, the restart on every boot of kpersonalizer seems to be "normal". (not so
pretty! )
And the preview resolution problem seems to only be there when i activate
"framebuffer-interface in the kernel".
Still dunno where the black screen came from though
--
Kpersonalizer start every boot AND
Public bug reported:
I installed
apt-cache policy kpersonalizer
kpersonalizer:
Geïnstalleerd: 4:3.5.4-0ubuntu1~dapper2
Kandidaat: 4:3.5.4-0ubuntu1~dapper2
Versietabel:
*** 4:3.5.4-0ubuntu1~dapper2 0
500 http://kubuntu.org dapper/main Packages
100 /var/lib/dpkg/status
4
--
Installer crashed
https://launchpad.net/bugs/56371
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
--
Installer crashed
https://launchpad.net/bugs/56371
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
--
Installer crashed
https://launchpad.net/bugs/56371
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Public bug reported:
edgy build of todays ubuntu
Traceback (most recent call last):
File "/usr/bin/ubiquity", line 132, in ?
install(sys.argv[1])
File "/usr/bin/ubiquity", line 57, in install
ret = wizard.run()
File "/usr/lib/ubiquity/ubiquity/frontend/gtkui.py", line 264, in run
* they
--
Opens one thread per file even if not used
https://launchpad.net/bugs/40141
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
In svn there was a commit after 1.2 which should close files on the fly when
there are not needed.
Please check this issue on 2.0.
--
Opens one thread per file even if not used
https://launchpad.net/bugs/40141
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/ma
Never seen this here, not in [EMAIL PROTECTED] and not in 2.0 final.
Normally KTorrent tries to bind to the next port when it fails to bind to the
ports set in config, and stops trying at +10 ports. (with a message, looking at
the po file)
--
KTorrent crashes at startup if socket in use
https:/
Me neither on dapper on kde 3.5.4 with version 2.0 and svn.
Just some random question:
Is this on gnome?
Does this also happen when you just start the program(with starting torrents or
do anything)?
--
ktorrent makes logout impossible
https://launchpad.net/bugs/50059
--
ubuntu-bugs mailing li
Same crashing kded bug here, i installed kat on dapper with kde 3.5.4.
Seeing that the problem pops up directly after a boot without needing to load
kat, the problem is probably somewhere in or around the daemon of kat.
I don't know much about the packages, only that the problem is gone
after rem
23 matches
Mail list logo
