*** This bug is a duplicate of bug 1195007 ***
https://bugs.launchpad.net/bugs/1195007
I have the same problem with
ubuntu 12.04 64 bit
Qt: 4.8.2
KDE Development Platform: 4.11.2
KDevelop: 4.5.1
Any idea how to solve the problem here
--
You received this bug notification because you are a
I got the same problem …… and I'm Install Ubuntu 13.04 today!!
i had use sudo apt-get install kdevelop to installed it ……
something wrong with the office download source ?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Seems to be fixed with today's qt update...
--
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to kdevelop in Ubuntu.
https://bugs.launchpad.net/bugs/1178843
Title:
kdevelop won't start
To manage notifications about this bug go to:
*** This bug is a duplicate of bug 1195007 ***
https://bugs.launchpad.net/bugs/1195007
** This bug has been marked a duplicate of bug 1195007
qt patch introduces fatal gdk_x_error handler
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Same thing, I had the problem with 4.4.x, upgraded to 4.5.1 and still
the same thing. The splash and welcome screen render then everything
disappears with the following error:
The program 'kdevelop' received an X Window System error.
This probably reflects a bug in the program.
The error was
Lets separate issues please. Those people that see
The error was 'BadWindow (invalid Window parameter)'.
(Details: serial 1615 error_code 3 request_code 20 minor_code 0)
(Note to programmers: normally, X errors are reported asynchronously;
that is, you will receive the error a while after
I have the same problem, kdeveop can not open.
when I start it from shell, then I got the follow error:
WARNING: deleting stale lockfile
/home/jimmy/.kdevduchain/{a1b775b5-6df4-43bd-944b-d1c541c7f7fb}/1/lock
kdevelop(8882)/kdevplatform (language) KDevelop::ItemRepositoryRegistry::open:
I just noticed that some of my gnome-settings-daemon crashes (~2 or 3
per day) have been BadWindow errors. I doubt gnome-settings-daemon uses
any KDE libraries. Could this bug be unrelated to KDE? (If so, it
looks like KDE apps tickle the bug more reliably than other apps.)
--
You received
About a month ago I started getting BadWindow errors with konsole and
amarok, so I think it's a problem with some KDE library, not kdevelop.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1178843
Yes, it looks like this bug affects all KDE apps.
http://ubuntuforums.org/showthread.php?t=2157427
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1178843
Title:
kdevelop won't start
To manage
This problem started to happen to me yesterday. I tried kdevelop 4.4.1
and afterwards added the ppa from kubuntu, upgraded and had the same
issue with kdevelop 4.5.1.
$ kdevelop --sync
KGlobal::locale(): Warning your global KLocale is being recreated with a valid
main component instead of a fake
I started experiencing the same issue in Ubuntu 13.04 after apt-get
update/upgrade.
$ kdevelop --version
Qt: 4.8.4
KDE Development Platform: 4.10.4
KDevelop: 4.4.1
$ uname -a
Linux bert 3.8.0-25-generic #37-Ubuntu SMP Thu Jun 6 20:47:07 UTC 2013 x86_64
x86_64 x86_64 GNU/Linux
The splash screen
I started kdevelop with :
---
sudo su
su yabgu
kdevelop
yabgu@Desktop:~$ sudo su
[sudo] password for yabgu:
root@Desktop:/home/yabgu# su yabgu
yabgu@Desktop:~$ kdevelop
WARNING: deleting stale lockfile
same problem here...
KGlobal::locale(): Warning your global KLocale is being recreated with a valid
main component instead of a fake component, this usually means you tried to
call i18n related functions before your main component was created. You should
not do that since it most likely will
This started happening to me today.
** As a workaround, I can open kdevelop with sudo **
so I guess the problem has something to do with sessions.
stdout:
kdevelop
WARNING: deleting stale lockfile
/home/bruno/.kdevduchain/{5bb877a5-d8b2-4cdc-b694-6c9b8bf67781}/1/lock
I have the same error here. Both kdevelop 4.5 and a recent checkout from
git:
eendebakpt@woelmuis:~/.cache$ kdevelop
KGlobal::locale(): Warning your global KLocale is being recreated with a valid
main component instead of a fake component, this usually means you tried to
call i18n related
Same problem! Even with latest version (built from source)
$ kdevelop --version
Qt: 4.8.4
KDE Development Platform: 4.10.80
KDevelop: 4.5.60
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1178843
this is mine output from kdevelop
kdevelop
WARNING: deleting stale lockfile
/home/peci/.kde/share/apps/kdevelop/sessions//{a61b7b97-994c-44ab-89cf-d09e00e671e5}/lock
WARNING: deleting stale lockfile
/home/peci/.kdevduchain/{a61b7b97-994c-44ab-89cf-d09e00e671e5}/1/lock
I had the very same problem with 4.4 (from the standard repo). I then
upgraded to 4.5.1 (from the kubuntu backports repo) hoping that this
might fix it - but it did not. Still the very same.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: kdevelop (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1178843
Title:
In my case it just simply doesn't start. This happened after an update
from kdevelop 4.5 to 4.5.1
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1178843
Title:
kdevelop won't start
To manage
constantine@flow:~$ kdevelop
Fontconfig warning: /etc/fonts/conf.d/50-user.conf, line 14: reading
configurations from ~/.fonts.conf is deprecated.
KGlobal::locale(): Warning your global KLocale is being recreated with a valid
main component instead of a fake component, this usually means you
If it helps, here the stdout from `kdevelop` :
(kdevelop:6689): Gtk-CRITICAL **: IA__gtk_settings_set_long_property: assertion
`GTK_SETTINGS (settings)' failed
(kdevelop:6689): Gtk-CRITICAL **: IA__gtk_settings_set_long_property:
assertion `GTK_SETTINGS (settings)' failed
(kdevelop:6689):
23 matches
Mail list logo