I've app-cdr/k3b-1.0.5-r6 and just installed app-cdr/k3b-1.68.0_alpha3 (both available now because of different SLOT used). The old k3b (/usr/kde/3.5/bin/k3b) works ok, while new (/usr/bin/k3b) unable to detect my DVD-writing devices (I've two). On startup, new k3b output this (several times) to console: QStringList Solid::Backends::Hal::HalManager::findDeviceByDeviceInterface(const Solid::DeviceInterface::Type&) error: "org.freedesktop.DBus.Error.Disconnected" Looks like it will not work without HAL... I don't have hal installed (I don't use kde, just run few kde apps using fluxbox as wm), and there was no needs in installing hal for me before. Reproducible: Always Portage 2.1.6.13 (hardened/linux/x86/10.0, gcc-4.3.4, glibc-2.9_p20081201-r2, 2.6.28-hardened-r9 i686) ================================================================= System uname: Linux-2.6.28-hardened-r9-i686-Intel-R-_Core-TM-2_CPU_6600_@_2.40GHz-with-gentoo-1.12.13 Timestamp of tree: Sat, 07 Nov 2009 14:30:01 +0000 app-shells/bash: 4.0_p28 dev-java/java-config: 2.1.9-r1 dev-lang/python: 2.6.2-r1 dev-util/cmake: 2.6.4-r3 sys-apps/baselayout: 1.12.13 sys-apps/sandbox: 1.6-r2 sys-devel/autoconf: 2.13, 2.63-r1 sys-devel/automake: 1.7.9-r1, 1.8.5-r3, 1.9.6-r2, 1.10.2 sys-devel/binutils: 2.18-r3 sys-devel/gcc-config: 1.4.1 sys-devel/libtool: 2.2.6a virtual/os-headers: 2.6.27-r2 ACCEPT_KEYWORDS="x86" CBUILD="i686-pc-linux-gnu" CFLAGS="-march=prescott -O2 -pipe" CHOST="i686-pc-linux-gnu" CONFIG_PROTECT="/etc /service /usr/inferno/keydb /usr/inferno/lib /usr/inferno/services /usr/kde/3.5/env /usr/kde/3.5/share/config /usr/kde/3.5/shutdown /usr/share/config /var/log /var/qmail/alias /var/qmail/control" CONFIG_PROTECT_MASK="/etc/ca-certificates.conf /etc/env.d /etc/env.d/java/ /etc/fonts/fonts.conf /etc/gconf /etc/php/apache2-php5/ext-active/ /etc/php/cgi-php5/ext-active/ /etc/php/cli-php5/ext-active/ /etc/revdep-rebuild /etc/sandbox.d /etc/terminfo /etc/udev/rules.d" CXXFLAGS="-march=prescott -O2 -pipe" DISTDIR="/usr/portage-distfiles" EMERGE_DEFAULT_OPTS="--with-bdeps=y" FEATURES="distlocks fixpackages parallel-fetch protect-owned sandbox sfperms strict unmerge-orphans userfetch userpriv usersandbox" GENTOO_MIRRORS="http://ftp.lug.ro/gentoo/ http://mirror.qubenet.net/mirror/gentoo/" LANG="ru_RU.UTF-8" LDFLAGS="-Wl,-O1" LINGUAS="en ru" MAKEOPTS="-j3" PKGDIR="/usr/portage-packages" PORTAGE_CONFIGROOT="/" PORTAGE_RSYNC_OPTS="--recursive --links --safe-links --perms --times --compress --force --whole-file --delete --stats --timeout=180 --exclude=/distfiles --exclude=/local --exclude=/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="/usr/local/portage/layman/powerman /usr/local/portage/layman/sunrise /usr/local/portage" SYNC="rsync://rsync.gentoo.org/gentoo-portage" USE="X Xaw3d a52 aac acl acpi aim alsa apache2 arts asf avi bash-completion berkdb bitmap-fonts bzip2 cdr chm cli cracklib crypt cscope curl dbus dga divx4linux djvu dlloader dri dts dvd dvdr dvdread encode fastcgi ffmpeg flac flash gd gdbm gif gnutls gpg gtk gtk2 hardened hddtemp iconv icq idn imagemagick imap imlib irc jabber javascript jpeg kde kdeenablefinal lm_sensors lzo mad mailbox mbox mmx mng modules motif mp3 mpeg msn mudflap mysql ncurses nls nptl nptlonly ogg opengl openmp oss pam pcre perl pic png pppd pwdb python qt qt3support quicktime readline reflection rss rtc samba sdl session spell spl sse sse2 ssl ssse3 svg sysfs tcltk tcpd tiff truetype truetype-fonts type1-fonts unicode urandom vim-pager vim-syntax vim-with-x vorbis win32codecs x86 xinetd xorg xv xvid yahoo zlib" ALSA_CARDS="ali5451 als4000 atiixp atiixp-modem bt87x ca0106 cmipci emu10k1 emu10k1x ens1370 ens1371 es1938 es1968 fm801 hda-intel intel8x0 intel8x0m maestro3 trident usb-audio via82xx via82xx-modem ymfpci" ALSA_PCM_PLUGINS="adpcm alaw asym copy dmix dshare dsnoop empty extplug file hooks iec958 ioplug ladspa lfloat linear meter mmap_emul mulaw multi null plug rate route share shm softvol" APACHE2_MODULES=" log_config vhost_alias autoindex alias rewrite dir deflate filter mime negotiation auth_basic authn_file authz_host authz_user authz_groupfile cgi actions headers env setenvif " ELIBC="glibc" INPUT_DEVICES="keyboard mouse" KERNEL="linux" LCD_DEVICES="bayrad cfontz cfontz633 glk hd44780 lb216 lcdm001 mtxorb ncurses text" LINGUAS="en ru" LIRC_DEVICES="serial" USERLAND="GNU" VIDEO_CARDS="vesa fbdev nv nvidia" Unset: CPPFLAGS, CTARGET, FFLAGS, INSTALL_MASK, LC_ALL, PORTAGE_COMPRESS, PORTAGE_COMPRESS_FLAGS, PORTAGE_RSYNC_EXTRA_OPTS
Yes, it needs a running hald.
Added the missing runtime depend for sys-apps/hal.
(In reply to comment #1) > Yes, it needs a running hald. Does one need anything else in addition? I have hald/dbus running (started manually /etc/init.d/hald start), but k3b-1.68 still does not see the optical device, although 1.0.5 does.
Reopening unless confirmed.
I also have dbus/hald started and app-cdr/k3b-1.68.0_alpha3 does not find my recorder. I see this line many times in console: QStringList Solid::Backends::Hal::HalManager::findDeviceByDeviceInterface(const Solid::DeviceInterface::Type&) error: "org.freedesktop.DBus.Error.AccessDenied"
(In reply to comment #4) > Reopening unless confirmed. This is quite odd. After a number of restarts of various daemons (and suspend-to-disk + suspend-to-ram cycles), k3b became finally aware of the optical drive. I cannot quite put my finger on exactly what particular change triggered that. I am certain that hald and dbus were running the first time I launched k3b-1.68. Unfortunately all I can report now is that "somehow" k3b-1.68 works and I cannot say specifically what I did to change that.
It only needs a working dbus/hald configuration, that's all. We can't fix your setup from k3b's ebuild.
Reopening bug. Does still not work for me with current configuration. Currently it requires hal with policykit USE flag to be able to detect my recorder.
(In reply to comment #7) > It only needs a working dbus/hald configuration, that's all. We can't fix your > setup from k3b's ebuild. I agree. However, I have not touched hal's configuration files. It could be that I compiled something that k3b relies on without the hal userflag, though. In any case, this looks like an error on my part. My apologies for an imprecise report.
(In reply to comment #2) I added the policykit in USE and re-compile the HAL and consolkit. That fit the k3b detect DVD_Write device problem. At the same time the kded4 segfault and adding a usb drive crash the plasma-desktop problem also go away.
Thanks for the hint, problem solved here too !
Re-emerging --deep --newuse -u world with "policykit" set solved the problem for me too.
i had the same pb here using app-cdr/k3b-9999-r1. Shouldn't those ebuilds depend on policykit if that's so much of a problem ?
(In reply to comment #13) > i had the same pb here using app-cdr/k3b-9999-r1. Shouldn't those ebuilds > depend on policykit if that's so much of a problem ? > Only if someone is willing to debug it and find out why it's required... Because it isn't for most of us. Having consolekit/hald without polkit/policykit works fine here with my user in cdrw, cdrom and plugdev groups w/ "brw-rw---- 1 root cdrom 11, 0 Jan 30 17:34 /dev/sr0"
Seems to me k3b itself should be fixed not to depend on hald, as everybody (eg: Xorg) is deprecating hald now, because it seems it's not mantained anymore.
My k3b (1.91.0_rc2) suddenly broke with the upgrade to dbus-1.2.24 the other day (I didn't notice it until I tried to run k3b just now). Adding "policykit" to my USE flags and recompiling hal via emerge -auvtND world allows k3b to work again. Downgrading to dbus-1.2.3-r1 (and subsequently removing the policykit use flag and merging config files) fixes the issue. So, there is something about dbus-1.2.24 or the configuration files that Gentoo ships with it that by default doesn't play so nicely with k3b.
This appears to be affecting me as well.
I've played around with 1.2.24 and 1.2.3-r1... 1.2.24 works if the config file /etc/dbus-1/system.conf is left at the 1.2.3-r1 version.
I tried to bisect down the exact change in the configuration where the problem occurred, and wound up with the same system.conf as the 1.2.24 ebuild... and it still works. This appears to be similar to comment #6 above... I may try to investigate it some more later.
I should add that in my testing I only changed dbus. k3b was still at the same version the whole time (actually 1.70.0_beta1), and I didn't recompile it at all.
(In reply to comment #20) > I should add that in my testing I only changed dbus. k3b was still at the same > version the whole time (actually 1.70.0_beta1), and I didn't recompile it at > all. Is your user in plugdev group?
(In reply to comment #21) > (In reply to comment #20) > > I should add that in my testing I only changed dbus. k3b was still at the same > > version the whole time (actually 1.70.0_beta1), and I didn't recompile it at > > all. > > Is your user in plugdev group? > Yes it is, and I'm pretty sure it was there at the time I tested.
Hi, Is this reproducible with either 1.92.0_rc3 (arch) or the newly released 2.0.0 (~arch) ?
(In reply to comment #23) > Hi, > > Is this reproducible with either 1.92.0_rc3 (arch) or the newly released 2.0.0 > (~arch) ? > 2.0.0 seems to work without the need for the policykit USE flag.
k3b-2.0.0 does not see the device either with dbus-1.2.3-r1 or dbus-1.2.24, neither with consolekit and hal compiled either with policykit support or without. Brasero and Nero-3 works fine. It used to work perfectly 3 months ago... I've just installed 3 months worth of updates in one go: everything else seems to be working now except k3b...
Ok, works now... No need to downgrade or recompile-without-policykit anything. I had a slightly misconfigured kernel after moving to libATA: people who has problems with k3b/hal, please check that CONFIG_BLK_DEV_SR is set AND /etc/udev/rules.d/70-persistent-cd.rules is correct (if in doubt, remove it and it will be recreated at the next boot)
Gathering from the comments that this is fixed in 2.0.0. 1.92.0_rc3 is stable now and is the next-to-last release candidate, so it's likely it works there too. Anyway 2.0.0 is in ~arch. Resolving.
I am running k3b 2.0.0 and had to compile hal with policykit in order to get k3b finding my drives
I'm using k3b-2.0.0 and it doesn't detect my optical drives, though i recompiled hal, consolekit and kdelibs with policykit flag. I also tried different versions of dbus; currently i have dbus-1.2.24, since dbus-1.2.3-r1 didn't affect the problem. I've also tried to include BLK_DEV_SR in my kernel (2.6.29-gentoo-r5), though it used to work well. What else could i've missed?
I've upgraded to gentoo-2.6.34-r1 and rebuild hal, dbus and k3b, but still no progress.
Denis: do you have /dev/cdrom, /dev/dvd etc. symlinks pointing to a correct device? (In my case it is sr0)
$ grep CONFIG_BLK_DEV_SR /etc/kernels/kernel-config-x86-2.6.34-gentoo-r1 CONFIG_BLK_DEV_SR=y CONFIG_BLK_DEV_SR_VENDOR=y $ id uid=1000(dimon) gid=100(users) groups=100(users),6(disk),10(wheel),18(audio),19(cdrom),27(video),80(cdrw),85(usb),250(portage),261(zope),442(plugdev),444(games) $ eix hal [I] sys-apps/hal ... Installed versions: 0.5.14-r2{tbz2}(11:13:55 PM 07/23/2010)(X acpi consolekit crypt doc kernel_linux laptop -apm -debug -dell -disk-partition -kernel_FreeBSD -policykit -selinux) ... all of the above and no dice - I'm in the process of "emerge -uDN world" with policykit set in USE flags.
confirmed that policykit USE flag "fixes" K3b
Sorry, for the late reply... Yes all links are correct, besides, everything else is working fine, except k3b. One thing i forgot is to emerge -deep -newuse -au world; currently i'm in the middle of the process. Some packages are failing ot emerge, but probably nothing special. I hope to finish everything till Monday. P.S. k3b-2.0.1 is out, although it's unstable, could be a good thing to try.
I've managed to solve this. The problem was because of the CONFIG_IDE set in the kernel, which udev doesn't like. Unsetting deprecated CONFIG_IDE caused all my IDE devices to change from /dev/hd* to /dev/sd*, also i had to specify root=/dev/sdb1 kernel option in order to boot properly. Thanks for help everyone!
I can confirm this, made me crazy. CONFIG_IDE should be disabled now and configure the new PATA drivers to match your hardware. Maybe an idea to let udev/hald give a warning about this? For me it was not necessary to set +policykit (it did not hurt either).
