Re: [kde-freebsd] 9-CURRENT (r197801) && artsd of kde-3.5.10_2 gives SIGSEGV
On Wednesday 14 October 2009 08:32:21 Matthias Apitz wrote:
> I think only supporting KDE4 is not a good idea. IMHO, KDE4 is a bit
> heading in the wrong direction. KDE4 is unusable for a lot of (older)
> hardware and is unusable, at least, for smaller laptops or netbooks,
> just because of the resources it is consuming. If the KDE team is
> leaving KDE3, and I don't expect further development, but only
> compability with upcoming FreeBSD ABI changes (or whatever), than we
> will not have KDE3 anymore from 9-CURRENT (or even from 8.0-RELEASE)
> anymore. Which would be a real pity :-(
I'm suprised someone actually uses artsd. As a fellow KDE3 user on 9-CURRENT
(on beefy hardware btw), I didn't have this issue because I always disable
artsd because I don't want sound notifications. As long as people are using
KDE3 I don't think it will die because people just like you will find the
problem(s) and fix it.
That said, I couldn't reproduce the problem (artsd works fine if I enable it).
Uname: FreeBSD 9.0-CURRENT #2: Fri Oct 9 08:37:37 CEST 2009 i386
- Pieter
>
> I'm willing to nail this small issue down. I've already compiled the
> arts-1.5.10_2,1 port with --enable-debug=full and will test it the
> upcoming weekend. Do you have any hints for me on debugging?
> I have had already a look into the code where it crashes in
> soundserver/kmedia2.cc:
>
> ...
> unsigned long Arts::PlayObject_private_base::_IID =
> Arts::MCOPUtils::makeIID("Arts::PlayObject_private");
>
> Arts::PlayObject_base *Arts::PlayObject_base::_create(const std::string&
> subClass) {
> Arts::Object_skel *skel =
> Arts::ObjectManager::the()->create(subClass); assert(skel);
> Arts::PlayObject_base *castedObject = (Arts::PlayObject_base
> *)skel->_cast(Arts::PlayObject_base::_IID); assert(castedObject);
> return castedObject;
> }
> ...
>
> but can't see anything what could cause this SIGSEGV;
>
> as well I have fetched the 8.0-RC1 precompiled package arts-1.5.10_2,1.tbz
> and will give it a try in 9-CURRENT.
>
> Will let you know what I can find out.
>
> Thanks
>
> matthias
___
kde-freebsd mailing list
kde-freebsd@kde.org
https://mail.kde.org/mailman/listinfo/kde-freebsd
See also http://freebsd.kde.org/ for latest information
Re: [kde-freebsd] 9-CURRENT (r197801) && artsd of kde-3.5.10_2 gives SIGSEGV
El día Wednesday, October 14, 2009 a las 02:33:10PM +0200, Pieter de Goeje escribió: > On Wednesday 14 October 2009 08:32:21 Matthias Apitz wrote: > > I think only supporting KDE4 is not a good idea. IMHO, KDE4 is a bit > > heading in the wrong direction. KDE4 is unusable for a lot of (older) > > hardware and is unusable, at least, for smaller laptops or netbooks, > > just because of the resources it is consuming. If the KDE team is > > leaving KDE3, and I don't expect further development, but only > > compability with upcoming FreeBSD ABI changes (or whatever), than we > > will not have KDE3 anymore from 9-CURRENT (or even from 8.0-RELEASE) > > anymore. Which would be a real pity :-( > > I'm suprised someone actually uses artsd. As a fellow KDE3 user on 9-CURRENT > (on beefy hardware btw), I didn't have this issue because I always disable (btw: I'm using KDE3 on 8-CURRENT on my beefy laptop too); > artsd because I don't want sound notifications. As long as people are using > KDE3 I don't think it will die because people just like you will find the > problem(s) and fix it. > > That said, I couldn't reproduce the problem (artsd works fine if I enable it). > Uname: FreeBSD 9.0-CURRENT #2: Fri Oct 9 08:37:37 CEST 2009 i386 what is the SVN rev number of your kernel (mine is r197801) and how aRts came to your system, via /usr/ports or how? matthias -- Matthias Apitz t +49-89-61308 351 - f +49-89-61308 399 - m +49-170-4527211 e - w http://www.unixarea.de/ Vote NO to EU The Lisbon Treaty: http://www.no-means-no.eu ___ kde-freebsd mailing list kde-freebsd@kde.org https://mail.kde.org/mailman/listinfo/kde-freebsd See also http://freebsd.kde.org/ for latest information
Re: [kde-freebsd] 9-CURRENT (r197801) && artsd of kde-3.5.10_2 gives SIGSEGV
On Wednesday 14 October 2009 14:44:10 Matthias Apitz wrote: > El día Wednesday, October 14, 2009 a las 02:33:10PM +0200, Pieter de Goeje escribió: > > On Wednesday 14 October 2009 08:32:21 Matthias Apitz wrote: > > > I think only supporting KDE4 is not a good idea. IMHO, KDE4 is a bit > > > heading in the wrong direction. KDE4 is unusable for a lot of (older) > > > hardware and is unusable, at least, for smaller laptops or netbooks, > > > just because of the resources it is consuming. If the KDE team is > > > leaving KDE3, and I don't expect further development, but only > > > compability with upcoming FreeBSD ABI changes (or whatever), than we > > > will not have KDE3 anymore from 9-CURRENT (or even from 8.0-RELEASE) > > > anymore. Which would be a real pity :-( > > > > I'm suprised someone actually uses artsd. As a fellow KDE3 user on > > 9-CURRENT (on beefy hardware btw), I didn't have this issue because I > > always disable > > (btw: I'm using KDE3 on 8-CURRENT on my beefy laptop too); > > > artsd because I don't want sound notifications. As long as people are > > using KDE3 I don't think it will die because people just like you will > > find the problem(s) and fix it. > > > > That said, I couldn't reproduce the problem (artsd works fine if I enable > > it). Uname: FreeBSD 9.0-CURRENT #2: Fri Oct 9 08:37:37 CEST 2009 i386 > > what is the SVN rev number of your kernel (mine is r197801) and how aRts > came to your system, via /usr/ports or how? I can't give you an exact revision (sources were obtained with csup) but r197869 should be pretty close. Arts was build using ports/audio/arts (version 1.5.10_2,1). Another PC running RELENG_8 (amd64) from Sep. 24 also has a working arts (same version, also compiled/installed via ports). - Pieter ___ kde-freebsd mailing list kde-freebsd@kde.org https://mail.kde.org/mailman/listinfo/kde-freebsd See also http://freebsd.kde.org/ for latest information
Re: [kde-freebsd] k3b freebsd contact
On Fri, 9 Oct 2009 17:15:33 -0400, "Jason E. Hale" wrote: > On Friday 09 October 2009 15:42:38 Heiner wrote: > >> That's me, although I am planning to retire here: I have currently not >> enought resources to move to KDE4 so that I will most likley be unable >> to >> do the KDE4 port of k3b once it is available. Is anybody here who wants >> to >> take the k3b port? >> > > I have been working the KDE4 version of the K3B port, so I would be > willing to > talk with anyone who has ideas for that. So far what I have pretty much > works, except K3B can never find the cdrecord executable even though the > KDE3 > version works just fine. As soon as I figure that one out, I may submit > the > port. I would prefer to wait until there is at least a beta release, but > they > haven't exactly been pushing releases out the door. > Jason, I would be interested in seeing what you have so far. I got completely stuck on the k3b side and glad to see you have made so much progress. Thanks! Rusty Nejdl http://networking.ringofsaturn.com ___ kde-freebsd mailing list kde-freebsd@kde.org https://mail.kde.org/mailman/listinfo/kde-freebsd See also http://freebsd.kde.org/ for latest information
Re: [kde-freebsd] k3b freebsd contact
on 14/10/2009 19:02 Rusty Nejdl said the following:
> On Fri, 9 Oct 2009 17:15:33 -0400, "Jason E. Hale"
> wrote:
>> On Friday 09 October 2009 15:42:38 Heiner wrote:
>>
>>> That's me, although I am planning to retire here: I have currently not
>>> enought resources to move to KDE4 so that I will most likley be unable
>>> to
>>> do the KDE4 port of k3b once it is available. Is anybody here who
> wants
>>> to
>>> take the k3b port?
>>>
>> I have been working the KDE4 version of the K3B port, so I would be
>> willing to
>> talk with anyone who has ideas for that. So far what I have pretty much
>
>> works, except K3B can never find the cdrecord executable even though the
>> KDE3
>> version works just fine. As soon as I figure that one out, I may submit
>> the
>> port. I would prefer to wait until there is at least a beta release,
> but
>> they
>> haven't exactly been pushing releases out the door.
>>
>
> Jason,
>
> I would be interested in seeing what you have so far. I got completely
> stuck on the k3b side and glad to see you have made so much progress.
Guys,
I also did some hacking on KDE4 k3b and here are some diffs that could be
useful:
1. Without this k3b doesn't find my DVD writer. It seems that it tries
cam_open_pass on /dev/cd0 which fails.
Index: libk3bdevice/k3bdevice.cpp
===
--- libk3bdevice/k3bdevice.cpp (revision 1034980)
+++ libk3bdevice/k3bdevice.cpp (working copy)
@@ -157,7 +157,7 @@
#ifdef Q_OS_FREEBSD
K3b::Device::Device::Handle K3b::Device::openDevice( const char* name, bool
write )
{
-K3b::Device::Device::Handle handle = cam_open_pass (name, O_RDWR,0 /* NULL
*/);
+K3b::Device::Device::Handle handle = cam_open_device( name, O_RDWR );
kDebug() << "(K3b::Device::openDevice) open device " << name
<< ((handle)?" succeeded.":" failed.") << endl;
return handle;
2. Without this k3b doesn't find cdrecord and mkisofs (what Jason said). It
looks
that if k3b doesn't find cdrecord at the first path it tries (in my case it was
/usr/bin), then it gets confused and begins to think that cdrkit is installed
(not
sure what it is) and searches for programs with names "wodim" and "genisoimage"
instead of "cdrecord" and "mkisofs".
Index: libk3b/core/k3bdefaultexternalprograms.cpp
===
--- libk3b/core/k3bdefaultexternalprograms.cpp (revision 1034980)
+++ libk3b/core/k3bdefaultexternalprograms.cpp (working copy)
@@ -128,10 +128,14 @@
QFileInfo(K3b::resolveLink( cdrtoolsPath )).baseName() != m_cdrkitAlt
) {
m_usingCdrkit = false;
path = cdrtoolsPath;
+#ifdef Q_OS_WIN32
+ setVersionIdentifier( name() );
+#endif
}
else if( QFile::exists( cdrkitPath ) ) {
m_usingCdrkit = true;
path = cdrkitPath;
+setVersionIdentifier( m_cdrkitAlt );
}
#ifndef Q_OS_WIN32
@@ -140,13 +144,6 @@
}
#endif
-if ( m_usingCdrkit )
-setVersionIdentifier( m_cdrkitAlt );
-#ifdef Q_OS_WIN32
-else
- setVersionIdentifier( name() );
-#endif
-
return path;
}
I also have an uncompleted major change (half a re-write) for
libk3bdevice/k3bscsicommand_bsd.cpp that allows k3b to correctly work when
ahci(4)
driver is used (in 8.0/CURRENT).
--
Andriy Gapon
___
kde-freebsd mailing list
kde-freebsd@kde.org
https://mail.kde.org/mailman/listinfo/kde-freebsd
See also http://freebsd.kde.org/ for latest information
Re: [kde-freebsd] k3b freebsd contact
On Wednesday 14 October 2009, Andriy Gapon wrote:
> 1. Without this k3b doesn't find my DVD writer. It seems that it tries
> cam_open_pass on /dev/cd0 which fails.
> Index: libk3bdevice/k3bdevice.cpp
> ===
> --- libk3bdevice/k3bdevice.cpp(revision 1034980)
> +++ libk3bdevice/k3bdevice.cpp(working copy)
> @@ -157,7 +157,7 @@
> #ifdef Q_OS_FREEBSD
> K3b::Device::Device::Handle K3b::Device::openDevice( const char* name,
> bool write ) {
> -K3b::Device::Device::Handle handle = cam_open_pass (name, O_RDWR,0 /*
> NULL */); +K3b::Device::Device::Handle handle = cam_open_device( name,
> O_RDWR ); kDebug() << "(K3b::Device::openDevice) open device " << name <<
> ((handle)?" succeeded.":" failed.") << endl;
> return handle;
Hi!
I am not sure, if this is a good idea. FreeBSD requires two devices to access
the CD: the /dev/cdX and the /dev/passX device (and sometimes the bus, targt,
lun ids). On the console, I read during the k3b startup:
(BSDDeviceScan) number of matches 23
(BSDDeviceScan) periph: cd0
(BSDDeviceScan) periph: pass0
(BSDDeviceScan) add device /dev/cd0:2:0:0 (/dev/pass0)
(K3bDevice::Device) /dev/cd0: init()
(K3bDevice::openDevice) open device /dev/pass0 succeeded.
This means, that my /dev/cd0 is aquivalent to /dev/pass1 and has the ids
2:0:0. From your error description, I guess, that on your system the cdX and
passX are mixed. So I expect the following on your console:
(BSDDeviceScan) number of matches 23
(BSDDeviceScan) periph: pass0 <- should be cd0
(BSDDeviceScan) periph: cd0 <- should be pass0
(BSDDeviceScan) add device /dev/pass0:2:0:0 (/dev/cd0)<- wrong!!
(K3bDevice::Device) /dev/pass0: init() <- should be cd0
(K3bDevice::openDevice) open device /dev/cd0 failed. <- should be pass0
Your patch would make init run on your system but break it on other systems.
Furthermore other things won't work on your system as well (if cdX is
expected).
I would recommend to look at K3bDevice::DeviceManager::BSDDeviceScan().
Obvioulsy in FreeBSD 8 the cam has changed and the devices might be ordered
differently. The code you see there was initially taken from the camcontrol
sources, so looking, what "camcontrol devlist" in its sources does is a good
start. I guess, that something has changed here since FreeBSD 7.x A fix
should make sure, that device->m_passDevice always points to a passX and
cddev to the cdX.
> 2. Without this k3b doesn't find cdrecord and mkisofs (what Jason said). It
looks
> that if k3b doesn't find cdrecord at the first path it tries (in my case it
was
Which k3b version you are working on?
Best regards,
Heiner
___
kde-freebsd mailing list
kde-freebsd@kde.org
https://mail.kde.org/mailman/listinfo/kde-freebsd
See also http://freebsd.kde.org/ for latest information
Re: [kde-freebsd] k3b freebsd contact
On Wednesday 14 October 2009 12:02:16 Rusty Nejdl wrote: > On Fri, 9 Oct 2009 17:15:33 -0400, "Jason E. Hale" > > wrote: > > On Friday 09 October 2009 15:42:38 Heiner wrote: > >> That's me, although I am planning to retire here: I have currently not > >> enought resources to move to KDE4 so that I will most likley be unable > >> to > >> do the KDE4 port of k3b once it is available. Is anybody here who > > wants > > >> to > >> take the k3b port? > > > > I have been working the KDE4 version of the K3B port, so I would be > > willing to > > talk with anyone who has ideas for that. So far what I have pretty much > > > > works, except K3B can never find the cdrecord executable even though the > > KDE3 > > version works just fine. As soon as I figure that one out, I may submit > > the > > port. I would prefer to wait until there is at least a beta release, > > but > > > they > > haven't exactly been pushing releases out the door. > > Jason, > > I would be interested in seeing what you have so far. I got completely > stuck on the k3b side and glad to see you have made so much progress. > > Thanks! > Rusty Nejdl > http://networking.ringofsaturn.com > I'm attaching a shar containing what I have done so far for the k3b-kde4 port. I included Andriy's fix for cdrecord not being found as well. I came up with the same patch for the cd device not being found, but it seems like that may not be the right way to go according to Heiner. I am not much of a programmer, so I don't know. I just thought I would give this port a go since I didn't hear anything about it until a few days ago. I actually started doing this a while back but lost interest since K3B had terrible trouble with QT 4.4. Anyways, the port should at least build, run, and install and deinstall cleanly. I have only tried this with FreeBSD 7.2 i386 though. It should at least provide a good starting point. - Jason k3b-kde4.shar Description: Unix shell archive ___ kde-freebsd mailing list kde-freebsd@kde.org https://mail.kde.org/mailman/listinfo/kde-freebsd See also http://freebsd.kde.org/ for latest information
