F14->F15 compiz problem
by Dj YB
Hello,
I have just finished upgrade few hours ago and since then I can't use compiz.
every time it starts it crashes/
all the settings are new, when I try to load the old config file using import it
is being ignored.
anyone else experience this problem?
how can I downgrade for now back to 0.8.6 ?
Thanks,
YB.
12 years, 10 months
kde-4.6.4 status
by Rex Dieter
Turns out we'd finished our initial set of builds, queue'd this for
updates-testing, stuffed into kde-testing... and,
Some last minute badness showed up that the source tarballs we used may
be bad, and include some older code. Given that, I revoked the update
and yanked it from kde-testing, pending further review and investigation.
For anyone who'd already grabbed it, you have 2 choices in the meantime:
1. when we sort things out, we'll ensure things upgrade smoothly (ie,
you can wait).
2. downgrade back to 4.6.3
-- Rex
12 years, 10 months
KWallet behavior
by John Aldrich
KWallet is behaving strangely for me... it waits until I try to send an
email to ask for the wallet password. For awhile I thought it was causing
my Chrome password issues, but I figured out that it was asking for the
GMail password to sync my Chrome.
Seriously, though... WTF is up with KWallet now? I just upgraded to F15 a
couple weeks ago and now it's not working like it "should"?!?!?!?! I have
it configured as follows:
1) It is enabled
2) Close when last application using it closes
3) Show in System tray
3b)Hide system tray icon when last wallet closes
Access Control:
1) Prompt when an application accesses an open wallet.
WHAT in there says "don't ask for the password until I specifically try to
access a password"???? How do I configure it to open the wallet with KMail
like it used to?
12 years, 10 months
Re: kde Digest, Vol 31, Issue 18
by Thomas Ritter
> Hi Thomas,
>
Hi Jaroslav
> do you have Bluetooth service enabled in your system?
>
> systemctl status bluetooth.service
>
$ systemctl status bluetooth.service
bluetooth.service - Bluetooth Manager
Loaded: loaded (/lib/systemd/system/bluetooth.service)
Active: inactive (dead)
CGroup: name=systemd:/system/bluetooth.service
***
I didn't obviously, a
$ systemctl enable bluetooth.service
did actually fix it. Is this enabled permanently now? If not, where can I
configure this?
Thank you very much for your help!
-- Thomas
12 years, 10 months
Bluetooth does not work
by Thomas Ritter
Hi all,
I'm using Fedora 15 (64bit on a ThinkPad T410s) and Bluetooth does not work,
although it did with Fedora 14.
In the KDE System Settings, the Bluetooth configuration says "No Bluetooth
adapters have been found."
The Gnome Bluetooth wizard does not complain about a missing bluetooth
adapters, but does not find any devices to pair either.
kernel:
2.6.38.7-30.fc15.x86_64
bluetooth controller:
Bus 001 Device 004: ID 0a5c:217f Broadcom Corp. Bluetooth Controller
Do you have any suggestion on how to debug this problem? Or should I file a
bug?
Thanks in advance!
-- Thomas
12 years, 10 months
'Lost and Found' category in 'System Settings'?
by Alexander Volovics
I installed the 32 bit 'flash-plugin' rpm from the adobe repository
in Fed15/KDE x86_64 just like I always do under Fed/Gnome x86_64
(and have also done in Fed15/Gnome3) using yum.
The flash-plugin itself works OK but something did not quite go
right with the install.
You should get an Adobe Flash Player icon somewhere so that you
can start 'usr/bin/flash-player-properties' to configure the
use of the plugin.
I found the icon in 'System Settings' in a rather strange category
"Lost and Found". Clicking on the icon produces an error message:
Could not find plugin 'Adobe Flash Player' for application
'systemsettings' Library "kcm_adobe_flash_player" not found
'rpm -ql flash=plugin' shows '/usr/lib/kde4/kcm_adobe_flash_player.so'
installed!
What is happening here? An install gone wrong somewhere?
NB
I can start 'flash-player-properties' as a command in a terminal
and it seems to work (I did have to install an additional i686
library first that it complained was missing)
Alexander
12 years, 10 months
Sound works with Gnome, not with KDE
by Patrick O'Callaghan
F15 x86_64, basic onboard Intel sound chip, nothing fancy.
Some recent update to F15 seems to have banjaxed my sound output under
KDE. The Systems Settings widget shows only Analog Output, no Pulseaudio,
even with "Special Devices" selected. I restarted the PA server and now
it does appear, but still no sound.
Speakers are connected and on. KMix has all volume controls at max, and
is not muted. pavucontrol ditto.
Under Gnome, without touching any settings, sound just works.
Now some further details:
1) On opening KDE's System Settings (Multimedia->Phonon) I get:
KDE detected that one or more internal sound devices were
removed.
Do you want KDE to permanently forget about these devices?
This is the list of devices KDE thinks can be removed:
* Capture: HDA Intel (STAC92xx Analog)
* Output: HDA Intel (STAC92xx Analog)
If I discard this (i.e. exit the dialogue with no changes), it does not
reappear on opening it again. Meaning that some state was saved even
when I told it not to.
2) The Backend is gstreamer.
3) Pulseaudio does not appear as a device in the Settings dialogue,
though the PA service is running. Killing and restarting the server
causes it to appear in the dialogue, but to no avail, i.e. still no
sound, including with the Test button.
4) I looked for PA-related messages:
$ sudo grep pulseaudio /var/log/messages
Jun 11 20:02:56 bree kernel: [ 132.916821] rtkit-daemon[1978]: Successfully made thread 1977 of process 1977 (/usr/bin/pulseaudio) owned by '500' high priority at nice level -11.
Jun 11 20:02:56 bree kernel: [ 139.078510] rtkit-daemon[1978]: Successfully made thread 2088 of process 2088 (/usr/bin/pulseaudio) owned by '500' high priority at nice level -11.
Jun 11 20:02:56 bree kernel: [ 139.084094] pulseaudio[2088]: pid.c: Daemon already running.
Jun 11 20:02:56 bree kernel: [ 139.093314] rtkit-daemon[1978]: Successfully made thread 2089 of process 2089 (/usr/bin/pulseaudio) owned by '500' high priority at nice level -11.
Jun 11 20:02:56 bree kernel: [ 139.094078] pulseaudio[2089]: pid.c: Daemon already running.
Jun 11 20:02:56 bree kernel: [ 139.103424] rtkit-daemon[1978]: Successfully made thread 2090 of process 2090 (/usr/bin/pulseaudio) owned by '500' high priority at nice level -11.
Jun 11 20:02:56 bree kernel: [ 139.104576] pulseaudio[2090]: pid.c: Daemon already running.
Jun 11 20:02:56 bree kernel: [ 421.060176] pulseaudio[1977]: ratelimit.c: 572 events suppressed
Jun 11 20:02:56 bree kernel: [17502.549480] pulseaudio[1977]: alsa-sink.c: ALSA woke us up to write new data to the device, but there was actually nothing to write!
Jun 11 20:02:56 bree kernel: [17502.549497] pulseaudio[1977]: alsa-sink.c: Most likely this is a bug in the ALSA driver 'snd_hda_intel'. Please report this issue to the ALSA developers.
Jun 11 20:02:56 bree kernel: [17502.549509] pulseaudio[1977]: alsa-sink.c: We were woken up with POLLOUT set -- however a subsequent snd_pcm_avail() returned 0 or another value < min_avail.
Jun 11 20:02:56 bree kernel: [18247.101045] rtkit-daemon[1978]: Successfully made thread 4599 of process 4599 (/usr/bin/pulseaudio) owned by '500' high priority at nice level -11.
Jun 11 20:02:56 bree kernel: [18247.578129] rtkit-daemon[1978]: Successfully made thread 4605 of process 4605 (/usr/bin/pulseaudio) owned by '500' high priority at nice level -11.
Jun 11 20:02:56 bree kernel: [18247.582081] pulseaudio[4605]: pid.c: Daemon already running.
Jun 11 20:02:56 bree kernel: [18250.447238] rtkit-daemon[1978]: Successfully made thread 4608 of process 4608 (/usr/bin/pulseaudio) owned by '500' high priority at nice level -11.
Jun 11 20:02:56 bree kernel: [18250.448408] pulseaudio[4608]: pid.c: Daemon already running.
Jun 12 00:50:59 bree rtkit-daemon[1953]: Successfully made thread 1952 of process 1952 (/usr/bin/pulseaudio) owned by '500' high priority at nice level -11.
Jun 12 00:51:04 bree rtkit-daemon[1953]: Successfully made thread 2064 of process 2064 (/usr/bin/pulseaudio) owned by '500' high priority at nice level -11.
Jun 11 20:21:04 bree pulseaudio[2064]: pid.c: Daemon already running.
Jun 12 00:51:04 bree rtkit-daemon[1953]: Successfully made thread 2065 of process 2065 (/usr/bin/pulseaudio) owned by '500' high priority at nice level -11.
Jun 11 20:21:04 bree pulseaudio[2065]: pid.c: Daemon already running.
Jun 12 00:51:04 bree rtkit-daemon[1953]: Successfully made thread 2067 of process 2067 (/usr/bin/pulseaudio) owned by '500' high priority at nice level -11.
Jun 11 20:21:04 bree pulseaudio[2067]: pid.c: Daemon already running.
Jun 11 21:34:15 bree pulseaudio[1952]: ratelimit.c: 603 events suppressed
Jun 11 21:36:13 bree pulseaudio[1952]: ratelimit.c: 630 events suppressed
Jun 12 02:15:44 bree rtkit-daemon[1953]: Successfully made thread 3178 of process 3178 (/usr/bin/pulseaudio) owned by '500' high priority at nice level -11.
Jun 12 02:15:44 bree rtkit-daemon[1953]: Successfully made thread 3183 of process 3183 (/usr/bin/pulseaudio) owned by '500' high priority at nice level -11.
Jun 11 21:45:44 bree pulseaudio[3183]: pid.c: Daemon already running.
Jun 12 02:15:46 bree rtkit-daemon[1953]: Successfully made thread 3186 of process 3186 (/usr/bin/pulseaudio) owned by '500' high priority at nice level -11.
Jun 11 21:45:46 bree pulseaudio[3186]: pid.c: Daemon already running.
None of that looks very interesting, but I'm no multimedia expert.
Any enlightenment would be welcome. I need to edit some videos and
without sound it's rather hit-and-miss ...
poc
12 years, 10 months
nepomuk errors: 'reference to page with free remap dp' fills disk
by Bill McGonigle
Hi, everybody,
I've got a 26G sporano-virtuoso.log and a 30G .xsession-errors filled
with 'reference to page with free remap dp' messages from nepomuk.
Does anybody know what might be going on or if there's an underlying bug
that's been fixed?
I see a few reports of it on a Google search, but nothing helpful.
I'm bzipping the logs from single user mode in case they might be useful.
This is f15, kde-runtime-4.6.3-1.fc15.x86_64.
Thanks,
-Bill
--
Bill McGonigle, Owner
BFC Computing, LLC
http://bfccomputing.com/
Telephone: +1.855.SW.LIBRE
Email, IM, VOIP: bill(a)bfccomputing.com
VCard: http://bfccomputing.com/vcard/bill.vcf
Social networks: bill_mcgonigle/bill.mcgonigle
12 years, 10 months
Apropos qt-4.8...?
by Peter G.
After I updated to qt-4.8 a few days ago, I noticed that:
- the titlebar wheel events no longer work
- the buttons on the titlebar are now all the same (the button popups still
work, and they are located in their old places, but otherwise, it is not
possible to tell which is for maximizing, minimizing, etc.)
Is this a bugzilla issue, or just a minor temporary thing until the next kde or
some other update?
12 years, 10 months
Some questions on networking gateways
by Timothy Murphy
I have a home LAN on network 192.168.2.0,
with a server at 192.168.2.2,
and various other laptops, iphones, etc on the LAN,
eg I am currently on laptop 192.168.2.7 .
There seem to be 3 places where gateways are specified:
1. In /etc/dhcpd.conf on the server, under "option routers";
2. In /etc/sysconfig/network-scripts/ifcfg-*
on the client machines;
3. In /etc/network on these machines.
I've read that the entries in ifcfg-* are ignored?
I haven't actually given gateways in /etc/network anywhere.
Perhaps I should?
My server has address 192.168.2.2 on eth1,
and address 192.168.1.2 on eth0, which is
connected to my ADSL modem with address 192.168.1.254 .
Now I'm wondering if I should give
GATEWAY=192.168.2.2 or GATEWAY=192.168.1.254
on client machines?
route -n on the server gives
------------------------------
Destination Gateway Genmask Flags Metric Ref Use
Iface
192.168.5.2 0.0.0.0 255.255.255.255 UH 0 0 0 tun0
192.168.5.0 192.168.5.2 255.255.255.0 UG 0 0 0 tun0
192.168.2.0 0.0.0.0 255.255.255.0 U 0 0 0 eth1
192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0
169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 eth1
0.0.0.0 192.168.1.254 0.0.0.0 UG 0 0 0 eth0
------------------------------
I'm not sure how it found the (correct) default gateway 192.168.1.254 ?
These questions arise because I tried changing my server
to machine 192.168.1.5, connected to the modem.
Everything worked fine on the new server,
but I could not access the ethernet on other machines,
even after modifying the route tables on these machines
to have default gateway 192.168.2.5 (the new server).
I tried both with NetworkManager and with the network service,
but neither worked satisfactorily.
Any enlightenment gratefully received.
--
Timothy Murphy
e-mail: gayleard /at/ eircom.net
tel: +353-86-2336090, +353-1-2842366
s-mail: School of Mathematics, Trinity College, Dublin 2, Ireland
12 years, 10 months
