** Changed in: kdebase
Importance: Unknown => Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
https://bugs.launchpad.net/bugs/47455
Title:
KDM detected memory corruption
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubunt
kdelibs (4:3.5.7-1ubuntu9) gutsy; urgency=low
[ Anthony Mercatante ]
* Fixed kubuntu_91_execute_feedback.patch again, improving the speed
of the effect to 3
[ Sarah Hobbs ]
* Added kubuntu_93_kdelibs-kdesudo-support-wflags-and-kab-fix.diff.
Thankyou to Stefan Skotte for this patch
** Changed in: kdelibs (Ubuntu Gutsy)
Assignee: Jonathan Riddell => Sarah Hobbs
--
KDM detected memory corruption
https://bugs.launchpad.net/bugs/47455
You received this bug notification because you are a member of Kubuntu
Team, which is a direct subscriber.
--
kubuntu-bugs mailing list
[E
** Changed in: kdelibs (Ubuntu Gutsy)
Sourcepackagename: kdebase => kdelibs
--
KDM detected memory corruption
https://bugs.launchpad.net/bugs/47455
You received this bug notification because you are a member of Kubuntu
Team, which is a direct subscriber.
--
kubuntu-bugs mailing list
[EMAIL PROT
the patch breaks kdm because it enforces a hard-coded $HOME, while kdm
sets up its own one dynamically - it's not my fault that the admin and
the system have the same user id on unix. :)
the patch is utterly misguided. not any applications, but sudo should be
fixed. for su, the x-aware variant sux
** Changed in: kdebase (Ubuntu Gutsy)
Assignee: (unassigned) => Jonathan Riddell
Status: Confirmed => In Progress
Target: None => tribe-3
--
KDM detected memory corruption
https://bugs.launchpad.net/bugs/47455
You received this bug notification because you are a member of Kubun
seems that it's a specific Red Hat and Ubuntu patch:
kubuntu_28_fix_sudo.diff
that produce the problem, probably fixing that broken patch finally fix this
bug ;)
I really don't know why this patch produce this bug, and why it's needed here.
--
KDM detected memory corruption
https://bugs.launchp
** Changed in: kdebase (upstream)
Status: New => Invalid
--
KDM detected memory corruption
https://bugs.launchpad.net/bugs/47455
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.
** Changed in: kdebase (upstream)
Status: Unknown => New
--
KDM detected memory corruption
https://bugs.launchpad.net/bugs/47455
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.
** Changed in: kdebase (Ubuntu Gutsy)
Target: tribe-3 => None
** Changed in: kdebase (Ubuntu Gutsy)
Status: Incomplete => Confirmed
--
KDM detected memory corruption
https://bugs.launchpad.net/bugs/47455
You received this bug notification because you are a member of Kubuntu
Team, w
** Also affects: kdebase (upstream) via
http://bugs.kde.org/show_bug.cgi?id=147454
Importance: Unknown
Status: Unknown
--
KDM detected memory corruption
https://bugs.launchpad.net/bugs/47455
You received this bug notification because you are a member of Kubuntu
Team, which is a direc
an upstream bug report finally arrived here:
https://bugs.kde.org/show_bug.cgi?id=147454
please help if you feel qualified.
--
KDM detected memory corruption
https://bugs.launchpad.net/bugs/47455
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscr
I'm seeing the same problem.
However the workaround to change the fonts from Kevin
(https://bugs.launchpad.net/ubuntu/gutsy/+source/kdebase/+bug/47455/comments/8)
does not make a difference here.
I'm using nvidia binary drivers.
--
KDM detected memory corruption
https://bugs.launchpad.net/bugs/
> I'm told that this is a X bug.
How a memory corruption in an X client process (KDM greeter) could be an
X server process issue?
> Is there anyone here who is *not* using a propriatory driver
(including Nvidia from their site, ATI from their site), who is getting
this bug?
I'm using the MGA dri
On Wednesday 27 June 2007, Sarah Hobbs wrote:
> I'm told that this is a X bug.
>
> Is there anyone here who is *not* using a propriatory driver (including
> Nvidia from their site, ATI from their site), who is getting this bug?
>
> ** Changed in: kdebase (Ubuntu Gutsy)
>Status: Confirmed =
On Wednesday 27 June 2007, JacobSteelsmith wrote:
> Confirming this too. I have a kubuntu 7.04 upgrade running KDE 3.5.6. I
> have an NVIDIA GeForce 6200 and use the NVIDIA driver from their
> website.
>
> KDE does restart, sending me back to the login screen, but it's stable
> otherwise. It may j
Another data point: I'm using the non-proprietary/free 'nv' driver from
X.org according to my /etc/X11/xorg.conf
--
KDM detected memory corruption
https://bugs.launchpad.net/bugs/47455
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
I am using XNest with XDMCP to log into the machine. Locally, the
machine is using the "ati" driver on a Radeon X600, which I assume is
the free driver (I certainly didn't download a proprietary one).
--
KDM detected memory corruption
https://bugs.launchpad.net/bugs/47455
You received this bug n
I am using whatever video drivers are installed by default for an IBM TP21 with
graphics controller S3 Savage /IX-MV.
So I assume I am not using a propietary driver.
I should remind it does not happen under Ubuntu Feisty on the same machine.
The xorg.conf files are effectively the same.
--
K
I'm told that this is a X bug.
Is there anyone here who is *not* using a propriatory driver (including
Nvidia from their site, ATI from their site), who is getting this bug?
** Changed in: kdebase (Ubuntu Gutsy)
Status: Confirmed => Incomplete
--
KDM detected memory corruption
https://bu
Confirming this too. I have a kubuntu 7.04 upgrade running KDE 3.5.6. I
have an NVIDIA GeForce 6200 and use the NVIDIA driver from their
website.
KDE does restart, sending me back to the login screen, but it's stable
otherwise. It may just be me, but it seems to happen frequently when I
run Adept
Just to confirm on a clean Kubuntu 7.04 install, I get the messages in
system log:
Jun 26 14:46:21 tp21 kdm_greet[5121]: Can't open default user face
Jun 26 14:46:48 tp21 kdm_greet[5121]: Internal error: memory corruption detected
but with no apparent ill effects.
I have no user face.
--
KDM de
I have fresh installed Feisty and get the "kdm_greet[5241]: Internal error:
memory corruption detected" message also.
When I start the machine, hard disk operates a while but screen stays black. If
I wait a minute and then press ctrl+alt+delete, login screen appears. After
that everything seems
** Changed in: kdebase (Ubuntu)
Target: None => tribe-3
--
KDM detected memory corruption
https://bugs.launchpad.net/bugs/47455
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.c
No, I was getting a gray screen when I tried to do a remote XDMCP login.
That message in the syslog was the only clue I could find.
--
KDM detected memory corruption
https://bugs.launchpad.net/bugs/47455
You received this bug notification because you are a member of Kubuntu
Team, which is a direc
You are most welcome - I'm glad to give a little back.
Are you getting the VT switch problem I wrote about? Every time a client logs
off the VT switches the server (which is my maiin client).
cheers,
Kevin
On Wednesday 13 June 2007, Michael wrote:
> This problem was preventing me from doing r
This problem was preventing me from doing remote XDMCP logins. Thank
you Kevin for your workaround above in comment 8! Can't this workaround
be made default until the problem has been solved upstream?
--
KDM detected memory corruption
https://bugs.launchpad.net/bugs/47455
You received this bug
I've been seeing this error ever since I switched to ubuntu (during the
dapper days). It was there in edgy, and it is still there in feisty. I
can't see anything wrong in the system. Everything just works during
login, but the error is a bit disconcerting.
Looks like a kdm_greet bug to me. It alw
I got also both of these errors on fresh Kubuntu Feisty Fawn install and I
think they were a reason for some instabilities.
Both errors (and instabilities) disappeared when I disabled the faces
completely (both settings for this).
I would recommend switching them off by default until the corrupt
Adding my comment to add weight. I found this error in the course of
trying to understand why vmware player will spontaneously die (big error
message and exit). My system runs fine otherwise, but this, of course,
is cause for a little concern.
2.6.20-15-generic #2 SMP Sun Apr 15 07:36:31 UTC 200
Yep, still there in feisty. I think this may be causing
problems/freezes during shutdown. My system freezes if I try to
shutdown/restart/logout from within kde. although it's fine if I just go
to console and ++, or shutdown -h now.
--
KDM detected memory corruption
https://bugs.launchpad.net/bu
Still there with 3.5.6 on feisty
--
KDM detected memory corruption
https://launchpad.net/bugs/47455
--
kubuntu-bugs mailing list
kubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
Still there with kde 3.5.6 on edgy (packages from kubuntu.org)
--
KDM detected memory corruption
https://launchpad.net/bugs/47455
--
kubuntu-bugs mailing list
kubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
Currently using Edgy with xen. Came across a lock up on my monitor. Upon
checking the logs, I found similar messages.
First off, "Can't open default user face" is because the default faces are
missing. Specifically, I did the following:
cd /usr/share/apps/kdm/faces/
ln -s ../pics/users
It appears that the kdm mem corruption problem is not gone. It still
comes up, but is no longer causing an issue. But did solve the lock-up
as being a swap issue with Kubuntu. Xorg and KDM were simply the
symptom.
--
KDM detected memory corruption
https://launchpad.net/bugs/47455
--
ubuntu-bugs
Ditto on Feisty... the two error messages occur at different times,
however:
"Can't open default user face" happens as KDM is opening (and removing
my ~/.face.icon has nothing to do with it).
"Internal error: memory corruption detected" occurs *ater* starting to
log in, and the login proceeds nor
i have the same problem... take a look here :
Nov 10 02:17:34 l-laptop kdm_greet[5196]: Can't open default user face
Nov 10 02:17:41 l-laptop kdm_greet[5196]: Internal error: memory corruption
detected
i use the Kubuntu 6.10 (Edgy) what can i do?
--
KDM detected memory corruption
https://launc
I can confirm this for Edgy current
(Kde 3.5.5, kdebase 4:3.5.5-0ubuntu3)
--
KDM detected memory corruption
https://launchpad.net/bugs/47455
--
kubuntu-bugs mailing list
kubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
Correction: it was still on kde 3.5.4 on edgy
--
KDM detected memory corruption
https://launchpad.net/bugs/47455
--
kubuntu-bugs mailing list
kubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
Confirmed on up-to-date Edgy with kde 3.5.5 (see bug 65689)
** Changed in: kdebase (Ubuntu)
Importance: Medium => High
Status: Unconfirmed => Confirmed
--
KDM detected memory corruption
https://launchpad.net/bugs/47455
--
kubuntu-bugs mailing list
kubuntu-bugs@lists.ubuntu.com
https:
Not yet. Will file a bug report on LTSP as it is still getting a
problem.
Do you have the terrible X memory leak too?
--
KDM detected memory corruption
https://launchpad.net/bugs/47455
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bug
i've got this memory corruption message also.
haven't tested kevin suggestion yet.
Kevin: about your LTSP issue i'm getting same issue do you have a bug
report on this??
--
KDM detected memory corruption
https://launchpad.net/bugs/47455
--
kubuntu-bugs mailing list
kubuntu-bugs@lists.ubuntu.c
I have had this problem for some time:
I upgraded from Breezy to Dapper
KDE wouldn't work at all!
That turned out to be a problem with the Indic, Thai and other Asian
fonts that had been installed along the way in the upgrade. Removing
them caused KDM to behave itself.
I had the user face probl
I too can confirm this bug for me. Kubuntu (upgraded from Breezy) with the
2.6.15-25-k7 kernel, NVidia Geforce 440 MX with the free driver ("nv").
Crashes happen from time to time, sometimes the machines doesn't even boot. No
mouse and keyboard then, reset by powerbutton needed.
--
KDM detected
44 matches
Mail list logo
