You are not logged in.
@markc , I totally understand, and like i said before, the actuel qt-copy package ( from kde-svn) works great (at least for me) with Qt Jambi, in spite of the -qt3support and the /usr prefix. So don't worry
Offline
Hi... I asked this question a couple of days ago:
@Markc, do you have any idea why the kde print manager is not showing in System Settings ?
According to the developers it should have two components:
KDEPrint is dead, long live system-config-printer-kde (kdeadmin) and printer-applet (kdeutils)! Thanks to jriddell for these.
I have looked in the files installed by these two packages and there's nothing related to printers in them.
Offline
@habarnam: I don't have a printer to test with but in looking at this there are some python based components missing plus system-config-printer and hal-cups-utils. I remember looking at this a long time ago and thinking, no way, I don't even want this gnome crap on my desktop let alone on the build server. I was hoping that in 3 or 6 months the kde developers would come up with a printing solution that does not depend on this stuff. Well, it's near the 4.2 release time and this is what installing the missing hal-cups-utils would bring along with it...
pycups-1.9.42-2 pycairo-1.6.4-2 pygobject-2.15.4-2 python-numeric-24.2-3 pygtk-2.13.0-2
python-notify-0.1.1-5 pyxml-0.8.4-5 dbus-python-0.83.0-2 orbit2-2.14.16-1
pyorbit-2.24.0-2 libart-lgpl-2.3.20-1 libgnomecanvas-2.20.1.1-2
gconf-2.24.0-1 gnome-mime-data-2.18.0-3 gnome-vfs-2.24.0-1
libbonobo-2.24.0-1 libgnome-2.24.1-1 libbonoboui-2.24.0-1
gnome-keyring-2.24.1-1 libgnomeui-2.24.0-1 gnome-python-2.22.3-3
system-config-printer-1.0.9-2 hal-cups-utils-0.6.13-1
I really really don't like all those g-words. I think if you or anyone want to try out printing then simply install hal-cups-utils and build kdeutils yourself. It's not a very big package so it would not take much time or effort once you get set up to do so. If this sounds like a reasonable compromise, but you are not sure how to proceed, then just say so and I'll post specific instructions.
Having to install Java for one single backend component was bad enough, installing half of a Gnome desktop just to print is... no, I just can't do it, sorry.
Offline
Ok, I completely understand. I don't like cross DE dependencies either.
Should this be considered a bug and reported to Arch developers ? (Because I see in other distros, that the dependency for system-config-printer is missing)
laterer edit:
I don't understand why hal-cups-manager has system-config-printer as dependency. I managed to compile it just fine using this AUR packages and removing the system-config-printer dependency.
final edit:
markc is it possible to add the PKGBUILD I proposed to your custom list and use it to have the damn pinter config ?
Last edited by habarnam (2008-12-07 21:46:27)
Offline
Hi,
This may seem a minor issue but it's driving me nuts. I have a USB wireless mouse. Before we start, let me point out that I have installed nothing except the usual Arch software that comes as part of an Suy run. I also keep up to date with Mark's packages and install them each time he rolls out a new set.What I've noticed is that from every few days I get a release of KDE4 that causes the mouse cursor to 'freeze' for a few seconds and/or jump around without apparent reason. Usually I notice it most on Firefox or Thunderbird. The problem seems to be caused by KDE4 as that is the package that changes almost every day.
Is there a way to 'prioritize' mouse handling?
Here's the relevant pieces of my current Xorg.conf;******
Identifier "Layout0"
Screen "Screen0" 0 0
InputDevice "Keyboard0" "CoreKeyboard"
InputDevice "Mouse0" "CorePointer"
*****Identifier "Mouse0"
Driver "mouse"
Option "Protocol" "auto"
Option "Device" "/dev/psaux"
Option "Emulate3Buttons" "no"
Option "ZAxisMapping" "4 5"
EndSectionI have tried with the mouse listed as USB Mouse but that seemed to make no difference.
Any ideas?
Thanks.
Try to add: Option "AllowEmptyInput" "false"
worked for me
Offline
@Lazer,
Thanks for the info. I've added that line and will report back as to it's effectiveness.
Offline
@habarnam: I finally added a [dev]/hal-cups-utils package compiled without any system-config-printer dependency. It took me a while to locate the upstream Git repo. It's untested so please let us know if it works, or not.
There is also a another temporary demo package of the [dev]/qt3d from http://labs.trolltech.com/blogs/2008/12 … -wolfenqt/
Last edited by markc (2008-12-11 06:31:56)
Offline
I sure will. So far I still don't have the printer manager thing with today's update.
Offline
EDIT: Just noticed your post a few lines above, markc. Yeah, i have system-config-printer installed and working, and with the new hal-cups-utils, hal completely failed to start, causing all sorts of problems on my hal-reliant setup.
If anyone has any trouble with hal failing to start and/or their sound cards seemingly failing to start (kde will nag about it) if you have pulseaudio (i think the sound card problem is only an issue if you use pulseaudio) the culprit is the new hal-cups-utils. For me, it prevented hal from running at all and caused all kinds of problems (pulseaudio relies on hal iirc). Revert it to the one released a few days ago, and you'll be good to go.
Last edited by FrozenFox (2008-12-11 13:21:14)
Offline
Weather plasmoid isn't working for a week or more now.
Is it true for you as well?
Offline
@FrozenFox: oh dear, so this "new" hal-cups-utils package is causing you grief! When you say revert it to the one released a few days ago do you mean revert back to the standard Archlinux package from [community] ? The next update is building against my dev/hal-cups-utils so I'm obviously concerned it may cause even more problems.
Anyone else using the weather plasmoid?
Offline
There are a number of plasmoids that don't work - with error This object could not be created for the following reason: Could not find requested component: X
I imagine this has something to do with some changes on plasma, but I couldn't find any commit logs or submitted bugs on this issue, so maybe it is something related to kde-svn ?
Here is my list of plasmoids and their status:
* Activity Bar - OK
* Analog Clock - OK
* Application Launcher [Menu] - Ok
* Battery Monitor - OK
* BBalL - Not OK (nothing appears on the dashboard - I assume there's a different issue)
* Binary Clock - OK
* Calculator - OK
* Calendar - OK
* Character selector - OK
* Chemestry - did you know - Not OK (the message I mentioned above)
* Color Picker - OK
* Comic strip - OK
* Command watch - Not OK
* Commit log - Not OK
* Contacts - Not OK
* Darkstat - Not OK
* Device notifier - OK
* Dictionary - OK
* Digital clock - OK
* Embedded window - Not OK
* Fifteen puzzle - OK
* File watcher - OK
* Folder view - OK
* Fuzzy clock - OK
* Grid - OK
* Grid Cell - Not OK
* Incoming message - OK
* Internal extender container - OK
* Job view - Not OK (crashes Plasma)
* KAlgebra - Not OK
* KGet.* - OK
* KMLDonkey - OK
* KTimetracker - Not OK
* KTorrent - OK
* Kate Session Applet - OK
* Keyboard Status Applet - OK
* Konqueror profiles - OK
* Konsolator - Not OK (crashes Plasma)
* Konsole profiles - OK
* LCD Weather station - OK
* Lancelot [Part|Launcher] - OK
* Leave a note - OK
* Life - OK
* Logout - OK
* Luna - OK
* MID COntrol - Not OK (Crashes Plasma)
* Menubar - Not OK
* Moodbar - Not OK
* News - OK
* Notes - OK
* Now Playing - OK
* Pager - OK
* Parley - Not OK
* Paste[bin] - OK
* Peachy - Not OK
* Picture frame - OK
* PlasmoBiff - Not OK
* Previewer - OK
* Quicklaunch - OK
* RSSNOW - OK
* Sample Rotating Applet - OK
* Scripted HTML - Not OK
* ServerHotlink - Not OK
* Shaman - Not OK
* Show Desktop - OK
* Show Widget Dashboard - OK
* SlideInSlideOutExample - Not OK
* Spacer - OK
* Stock watch - Not OK
* SvgPanel test - Not OK
* System command - Not OK
* System Monitor [- .*] - OK
* System Tray - OK
* Task Manager - OK
* Test Applet - Not OK
* Timer - OK
* Toggle desktop effects - Not OK (the widget does not show up on the dashboard)
* Trashcan - OK
* Twitter microblogging - OK
* UnitConverter - Not OK
* Weather Applet - Not OK
* Web Browser - OK
* WiFi Signal Strength meter - Not OK
* World Clock - Not OK
*aKademy group photo - Not OK
Last edited by habarnam (2008-12-11 14:23:51)
Offline
If I were to venture a guess I'd say there are some external components of these plasmoids that are missing from the packages, either not commited by the KDE developers (but since there are no bugs summited with this issue, I doubt it) either some glitch with building all these stuff.
Markc is there a possibility for this last thing ?
As a side note this made me think of a reply Aaron Seigo gave me to a request I posted on KDE bug tracker: I requested that Show Desktop plasmoid should have a keyboard shortcut. He replied that in 4.2 already has.
Last edited by habarnam (2008-12-11 14:40:09)
Offline
EDIT: Apparently, quirkiness from hal on my machine and amazing coincidence proved me wrong on what I thought was an issue in a package. Nothing to see here, move along >_>
Last edited by FrozenFox (2008-12-11 17:47:31)
Offline
@habarnam: thanks for checking all those plugins and providing a summary of what is working or not. It's certainly possible there is a glitch building the packages. I'm also a bit suspicious that some developers may develop against kde svn checkouts but on systems (kubuntu/fedora/whatever) that have older (most likely) libraries. I'll have to reinstall a [core] desktop partition with qt-copy before I can see for myself (I run qt-snapshot so kwin/plasma hasn't worked for me for a month now). If you svn checkout the source packages you could also build some of them and check the logfile (makepkg -L) and see if cmake is reporting anything strange. I just had a look at kdeplasma-addons and one lines says "-- libplasma doesn't support OpenGL applets" but a little further it says that OpenGL + libkexiv2 were found okay. It looks like this package provides 36 plasmoids so the issue could be narrowed down to mostly compiling this one package.
@FrozenFox: that's a bit scary because as far as I know there was no difference, that I am aware of, when building either of those 2 packages other than the 12 hours difference between them. It's a fairly simple package, just a /usr/lib/cups/backend/hal library, a perl script /usr/libexec/hal_lpadmin, and an xml fdi file called 10-hal_lpadmin.fdi. Not a lot to go wrong. Not sure what to suggest other than hope the next update is better. It'll take me another day or so before I can investigate any deeper.
Offline
Ok, I compiled my own xorg-server as per a pkgbuild I found on the kde forums for making intel cards work. Being a sucker for punishment, I am now back on kdemod 4.2b - This time with working desktop effects! FTW!
However, I am still stuck with konsole, kwrite, kate, krunner crashing whenever I try to type something in them (edit: make that any kde app with a space to type in, be it amarok, kmail or systemsettings. Only kde apps though. Others). Smplayer is now also a declared enemy of kde and will crash at will whether running a video or not. The latter is not a huge problem as vlc still works, but what can I do about the former? I needz my editors.
I'm also having trouble loading non kde apps. Thunar and openoffice won't launch, neither will a java app I use. Others like opera, aurora, xterm, compizconfig (just to test a gtk app) and lxappperance load just fine though. Odd and very hard to see the pattern in what works and what doesn't.
Last edited by b9anders (2008-12-11 23:54:00)
Offline
OK, Markc, I will try to build some of the packages using your (I almost said ebuilds) PKGCONFIGs... and get back with comments.
Any easy way of doing this on my main machine (I mean without breaking anything ) ?
Offline
@markc: At your suggestion that the two packages were the same, I retried to see if I could recreate hal breaking.
*The first time I came to the conclusion that it was the new package was when hal messed up with the new and reverting to the old fixed it. A quick revert-n-retry seemed to fix the issue after looking around for anything related to hal that might crash it.
* After upgrading and rebooting, hal was indeed screwed up again. I hadn't changed anything. I copied both files over to my main folder to find a possible difference, found they were the same bit to bit -- except somehow, according to konqueror, they are 3 bytes away from each other in size compressed. I have no idea how that might happen. On retrying one more time to be sure afterwards, hal apparently was still broken with either package, meaning okayyy, it's not the package, and there has been some incredible timing coincidence going on......
* Sigh. Now that I think of it, I have posted quite a few times with bizarre, unexplainable (pretty much, anyway) problems with hal on these forums.. Apparently, usually with amazing coincidence of deceptive timing, looking back. Apologies for the (I hope!) false problem report. If I figure out the issue, which I somehow highly doubt I will, I will edit the previous post with the new information.
Last edited by FrozenFox (2008-12-11 17:49:14)
Offline
@habarnam: heh, I think you meant PKGBUILDs, and keep in mind my kde-svn PKGBUILDs are slightly different to all other Archlinux versions as mine have an extra getsource() function that clearly shows how sources files are fetched and you can see it cd's to $SRCDEST first before getting any source, which is non-standard. Point being, $SRCDEST and $PKGDEST in /etc/makepkg.conf must be uncommented and the 2 directories must exist and be writable by your normal user ID. If you also install my dev/mpkg package then some things are simpler and, for instance, mpkg kdeplasma-addons will fetch, build, install and setup the binary package in a proper binary repo that could then be used by (from other computers) pacman -S. The mpkg package has 2 shell scripts, mpkg and mcfg, and just typing them on their own will provide help... mcfg sh kde-svn shows the build order of the kde-svn packages and a mpkg kde-svn will build them all in that order (about 2 to 3 hours build time but it will pull in 2Gb of svn source first).
@FrozenFox: no worries about these reports as you never know when it may be a local or general problem and someone else might have a solution. I've found that 3 times this year that simply reinstalling some packages has fixed "wierd" problems so, if your are desperate, try reinstalling pacman -S dbus dbus-core dbus-glib hal hal-info hal-cups-utils. I don't think this can do any harm and it might just kick something in the right place.
Offline
@Lazer,
Thanks for the suggestion above. That seems to have cured the problem. Amazing how irritating something as small as that can get. Anyway, I appreciate the input.
@Anyone,
Is there a way to stop the system demanding a password when returning to it after a period? I have looked and tried various things in System Setting to no avail.
Thanks
Offline
@markc,
Where firefox nightly is installed ?? It's not in /usr/lib/firefox ?
Offline
@maattd: in /opt/mozilla/firefox-3.1 (pacman -Ql firefox-nightly) the version number is really 3.2 something. Feel free to suggest where else it could be installed.
Last edited by markc (2008-12-12 14:18:37)
Offline
@maattd: in /opt/mozilla/firefox-3.1 (pacman -Ql firefox-nightly) the version number is really 3.2 something. Feel free to suggest where else it could be installed.
shouldn't it be /usr/local ?
Zygfryd Homonto
Offline
Or in /usr/lib/firefox-nightly
Offline
Apart from not being called 'Gran Paradiso' is there any benefit to the firefox nightly builds??
Thanks.
Offline