1 |
"Mark Haney" <mhaney@××××××××××××.org> posted |
2 |
4A65A339.6080109@××××××××××××.org, excerpted below, on Tue, 21 Jul 2009 |
3 |
07:15:05 -0400: |
4 |
|
5 |
> Fernando Boaglio wrote: |
6 |
>> Hi there, |
7 |
>> |
8 |
>> I'm a big fan of KDE, but since release 4.2.4 I 've been through some |
9 |
>> issues ... and AFAIK is 64bit only: |
10 |
|
11 |
Did you upgrade from 3.5 to 4.2.4 directly, or had you run earlier 4.x |
12 |
versions as well? Were the earlier 4.x versions working? |
13 |
|
14 |
FWIW, I've been trying to switch to the 4.x version since the 4.0 betas, |
15 |
but without success until I got some extra time the last couple weeks and |
16 |
decided now was the time to do it. I'm still having various issues, but |
17 |
have overcome enough of them that I'm running 4.2.4 by default now, and |
18 |
have unmerged most all of kde-3.5.10 but the base environment as I switch |
19 |
to kde4 versions of kmail, etc. |
20 |
|
21 |
Note that the rest of this comes across much more strongly negative than |
22 |
I tend to be in general or about kde in general. Fighting for hours a |
23 |
day, for days, to the point I'm only sleeping 3-4 hours most nights as |
24 |
I'm up struggling with yet another problem, trying to fix or work around |
25 |
issues in kde4 where kde3 "just worked", can do that to a guy. But I AM |
26 |
gradually working thru them, often developing workarounds for what |
27 |
remains broken, but other times finding fixes to apply. But honestly, if |
28 |
I didn't believe in KDE, and didn't therefore have strong motivation to |
29 |
stick with it, I'd not be bothering and thus wouldn't be so grumpy right |
30 |
about now, so it's not all as negative as it seems. |
31 |
|
32 |
But most of my issues are "power user" issues. Stuff like the fact that |
33 |
I used khotkeys multi-key mode HEAVILY in 3.5, and global multikeys don't |
34 |
work at all in 4.x and probably won't for some time, according to the |
35 |
bug. Stuff like no replacement for the ksysguard kicker applet. |
36 |
(ksysguard itself is still there, now called system monitor, but there's |
37 |
no plasmoid containment to run it in, yet.) |
38 |
|
39 |
But meanwhile, I've found the kde lists (kde, listed as kde-general on |
40 |
gmane's list2news gateway, and kde-linux) reasonably helpful. You might |
41 |
wish to come over and have a look around. =:^) |
42 |
|
43 |
>> - Amarok is mute =( |
44 |
|
45 |
I finally got fed-up with amarok, when the devs decided to require a |
46 |
mysql client library that was wasn't designed for the way they were using |
47 |
it, and that was broken on amd64. But that was simply the last straw, as |
48 |
they'd already pulled most of the features out of the 4.x version that I |
49 |
used amarok for, while leaving the features I didn't use much and didn't |
50 |
care about, requiring all sorts of dependencies I didn't otherwise need |
51 |
on my system, and developing even MORE such features and dependencies, |
52 |
including, eventually, that mysql library thing. |
53 |
|
54 |
So I switched to something else. As it happens, mpd, music player |
55 |
daemon, with various clients (qmpdclient for kde4, at first kmp for kde3 |
56 |
tho I've unmerged it with the other "extra" kde3 stuff now, mpc for the |
57 |
command line, and ncmpc and ncmpcpp for ncurses based interface, there's |
58 |
also gtk and even web based clients tho I don't have those installed...) |
59 |
was still WAY WAY less bloated than amarok, still has a music library |
60 |
(tho I do mostly net/shoutcast streaming based listening), AND doesn't |
61 |
shut down when I close X. |
62 |
|
63 |
I still miss the kde3/amarok visualizations and winamp skin |
64 |
compatibility, but those were some of the features that I mentioned above |
65 |
that I actually used that were done away with for the kde4 version, so |
66 |
it's not like I lost anything I wasn't already losing in amarok, and I |
67 |
gained a lot, including console based playback and all sorts of client |
68 |
flexibility, while losing all those bloated dependencies for features I |
69 |
didn't use anyway. |
70 |
|
71 |
But that's just me, based on what I used of it. If you use the music |
72 |
scoring and advanced library management features of amarok, you'll |
73 |
probably want to keep it, regardless of the bloat. YMMV, as they say, |
74 |
but there ARE other alternatives if you're looking for something not |
75 |
quite as "heavy", and without the issues keeping it working. |
76 |
|
77 |
>> - devices are not mounting automatically =( |
78 |
>> |
79 |
>> I've tried some fixes I read on forums without any luck. |
80 |
>> |
81 |
>> So... how about you guys, same thing? =) |
82 |
>> |
83 |
>> BTW, I'm running now 4.3RC2 with the same problems =/ |
84 |
|
85 |
I got burnt out on pre-alpha quality kde4 being billed as release quality |
86 |
some time ago, so I've stayed away from everything but full releases for |
87 |
awhile... and it's STILL nowhere near kde3.5's quality, tho the trend is |
88 |
good and it's MUCH better than it was. I'm not alone in predicting it |
89 |
might actually get to something approaching 3.5 quality by 4.5, which, |
90 |
given their six month minor release timing and the fact that 4.3 is |
91 |
scheduled for just days from now, should be about a year... |
92 |
|
93 |
But I'm still getting tempted to try 4.3 rcs, now that I've worked around |
94 |
enough of the issues remaining in 4.2.4 to actually start using it as my |
95 |
default desktop. |
96 |
|
97 |
> My Amarok works just fine, I use it all the time for radio and podcasts |
98 |
> without trouble. |
99 |
|
100 |
Yeah, now that all the distributions finished running around like |
101 |
chickens with their heads cut off trying to fix the broken on amd64 |
102 |
libraries that the amarok devs decided to use... without considering the |
103 |
effect on their amd64 users or the various distributions trying to |
104 |
support them. |
105 |
|
106 |
But regardless, it's no longer a problem I need to deal with, now. My |
107 |
current solution "just works". YMMV. |
108 |
|
109 |
> As for mounting devices automatically I don't do that anymore, I had |
110 |
> issues with devices automounting, but being boinced from mount point to |
111 |
> mount point (ie /dev/sda1 to /dev/sdb1 to /dev/sdc1) even if I left the |
112 |
> device connected. So I manually mount everything now. |
113 |
|
114 |
Same here, for the most part. I tend to distrust "automagic" stuff like |
115 |
automount, due to the various issues I've had with that sort of stuff and |
116 |
a certain proprietary platform that does all that automagic including |
117 |
autorun, by default, with the resulting malware including such things as |
118 |
Sony branded rootkits, etc. |
119 |
|
120 |
If I want it mounted, I mount it. If I want it unmounted, I unmount it. |
121 |
Don't complicate my life by breaking what's perfectly functional as it |
122 |
is, and I'll be happy. |
123 |
|
124 |
(Still, I said "for the most part", as I do occasionally take advantage |
125 |
of hal notification and automount for thumb drives and the like, despite |
126 |
my misgivings, when it works. I just don't expect it to always work, and |
127 |
have already had problems with for instance k3b, due to hal wanting to |
128 |
mount a just-burned disk one place, while /etc/fstab says it should be |
129 |
mounted elsewhere, and various bits of k3b getting mixed up when they |
130 |
look one place and it's at the other, or not mounted at all due to hal |
131 |
not obeying the plain as day configuration in fstab, when k3b is /trying/ |
132 |
to verify the image it just burned. If hal would just stay out of the |
133 |
way and let fstab and k3b or manual mounting handle it, my live wouldn't |
134 |
have had to be complicated by that bug!) |
135 |
|
136 |
-- |
137 |
Duncan - List replies preferred. No HTML msgs. |
138 |
"Every nonfree program has a lord, a master -- |
139 |
and if you use the program, he is your master." Richard Stallman |