dropping .desktop seems the sensible thing, as you say, it needs an
argument, exactly as does mprof-decoder in the same package but only
heap viewer has an errant .desktop file, seems accidental to me unless
i'm missing something
--
mono-profiler: mprof-heap-viewer.desktop contains
it seems paman removes its desktop entry. if the entry is edited ( ie,
set visible) then this is copied to
~/.local/share/applications/paman.desktop. now when paman is removed
this entry isnt removed. i'm not sure this is a bug since technically
its a custom user entry
--
Gnome menu entry left
thanks fabrice, i'll remember that for next time :)
--
Monkey studio crashes on startup: *** glibc detected *** monkeystudio:
corrupted double-linked list: 0x04710540 ***
https://bugs.launchpad.net/bugs/442151
You received this bug notification because you are a member of Ubuntu
Bugs,
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/32973757/Dependencies.txt
** Attachment added: XsessionErrors.txt
http://launchpadlibrarian.net/32973758/XsessionErrors.txt
--
Monkey studio crashes on startup: *** glibc detected *** monkeystudio:
corrupted
Public bug reported:
Binary package hint: monkeystudio
Monkeystudio crashes on startup on up to date karmic (04/10/2009), with error,
*** glibc detected *** monkeystudio: corrupted double-linked list:
0x04710540 ***
$ monkeystudio
Found plugin: AStyle, type: 1
Found plugin:
** Bug watch added: Debian Bug tracker #534667
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=534667
** Also affects: monkeystudio (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=534667
Importance: Unknown
Status: Unknown
--
Monkey studio crashes on startup: ***
this is fixed in a new upstream release
monkeystudio (1.8.4.0~beta1-1) unstable; urgency=low
.
* New upstream beta release.
+ Built against new qscintilla2, thus Closes: #534667.
--
Monkey studio crashes on startup: *** glibc detected *** monkeystudio:
corrupted double-linked list:
** Changed in: monkeystudio (Ubuntu)
Status: New = Fix Released
** Changed in: monkeystudio (Ubuntu)
Status: Fix Released = New
--
Monkey studio crashes on startup: *** glibc detected *** monkeystudio:
corrupted double-linked list: 0x04710540 ***
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/32483834/Dependencies.txt
--
XSplash in briefly interupted by gdm login screen when gdm is set to autologin
https://bugs.launchpad.net/bugs/437129
You received this bug notification because you are a member of Ubuntu
Bugs,
** Attachment added: apport.google-gadgets-gtk.apport
http://launchpadlibrarian.net/32481519/apport.google-gadgets-gtk.apport
** Summary changed:
- Google gadget failed to start
+ Google gadget failed to start - failed to load module: js-script-runtime
--
Google gadget failed to start -
** Attachment added: strace.txt
http://launchpadlibrarian.net/32481331/strace.txt
--
Google gadget failed to start
https://bugs.launchpad.net/bugs/434127
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
noticed this when installing a kernel update, so it doesnt just affect failing
drivers
1. have nvidia dkms installed on kernel
2. install a kernel update
3. reboot
4. dkms hasnt build nvidia module on kernel but...
5 gdm restarts repeatedly since X will fail because dkms hasnt finished
building
Public bug reported:
Binary package hint: xsplash
When xsplash is running, the gdm login screen briefly interrupts it and
flashes on to the screen before xsplash returns. gdm is set to autologin
so it doesnt need to be seen until the desktop is reached
ProblemType: Bug
Architecture: amd64
Date:
** Changed in: gnome-terminal (Ubuntu)
Status: New = Confirmed
--
gnome-terminal assert failure:
Vte:ERROR:/build/buildd/vte-0.22.0/./src/vtestream-file.h:30:_xread: assertion
failed: (fd || !len)
https://bugs.launchpad.net/bugs/435367
You received this bug notification because you are
*** This bug is a duplicate of bug 435367 ***
https://bugs.launchpad.net/bugs/435367
** Changed in: gnome-terminal (Ubuntu)
Status: New = Confirmed
** This bug has been marked a duplicate of bug 435367
gnome-terminal assert failure:
remember, the new hald start service has been 'upstarted' so its now
$ sudo start hal
--
kaffeine : device not connected
https://bugs.launchpad.net/bugs/429049
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
With nouveau driver on startup
$ gnome-display-properties
(gnome-display-properties:2317): Gtk-WARNING **: Ignoring the separator
setting
(gnome-display-properties:2317): Gtk-WARNING **: No object called:
**
display-properties:ERROR:xrandr-capplet.c:643:rebuild_resolution_combo: code
should
** Attachment added: strace.txt
http://launchpadlibrarian.net/32379193/strace.txt
--
gnome-display-properties assert failure:
display-properties:ERROR:xrandr-capplet.c:643:rebuild_resolution_combo: code
should not be reached
https://bugs.launchpad.net/bugs/431953
You received this bug
Not sure if mine really is the same problem but i'll describe it and a sort of
workaround
My default resolution is 1280x1024 but when desktop starts its in 1280x960 and
and xrandr shows seemingly wrong resolution list without 1280x1024 on it. if it
ret to start gnome-display-properties now i
Correction to above, i need to set xrand to one of the original
available resolutions before xrandr will show the 'correct' set of
resolutions and i can set it to 1280x1024. note, i do not get this with
the nvidia binaryt driver, only nouveau. the set of commands in terminal
on new login is
might not be the same thing but is hal running? i had what sounds like
the same problem but it was caused by kaffeine trying to 'get property'
from hal, but hal isnt running so it needed to be started manually. i
believe hal is in the process of being deprecated(?)
--
kaffeine : device not
i have a version that build/installs, whether it works or not is a binary thing
:)
i'll upload it in the ppa below as fglrx-installer_8.632-0ubuntu2~dinxter3
https://launchpad.net/~dinxter/+archive/ppa
essentially it just does as hunger mentioned above, removes popd and
pushd, and alters
just to note this still occurs with 2.6.31-9, i915 autoloads and causes
problems with nouveau loading
[8.111977] ttm: Unknown symbol drm_class_device_register
[8.113104] ttm: Unknown symbol drm_class_device_unregister
$rmmod i915 drm ttm
and then,
$modprobe nouveau
allows the nouveau
attached dpkg.log and x log
** Attachment added: dpkg-xorg.tar.gz
http://launchpadlibrarian.net/30891512/dpkg-xorg.tar.gz
--
nvidia-glx-185 conflicts nvidia-glx-180 ( 185.18.37) version is too high,
this means that dummy package nvidia-glx-180 can't upgrade
note the conflicts in apt-cache show nvidia-glx-185 with
nvidia-glx-180 ( 185.18.37)
this seems to be #NEXTVER# from debian/upstream_info.
In debian/control.in nvidia-glx-185 uses conflicts nvidia-glx-180 (
#NEXTVER#)
should this not just be #VERSION# ?
# apt-cache show
if i replace the #NEXTVER# terms in debian/control.in with #VERSION# i
can now install all the dummy 180 packages alongside the 185 ones as
expected since #VERSION# is RELEASE=185.18.36 in debian/upstream_info so
the conflicts work out as with 180 packages 185.18.36 which seems
right to me. i
tried upgrading from previous 180 versions to new 180 and 185 versions
with the changes and it seems to all work fine
** Attachment added: control.in_version.diff
http://launchpadlibrarian.net/30892893/control.in_version.diff
--
nvidia-glx-185 conflicts nvidia-glx-180 ( 185.18.37) version is
seems to be a one line change to MUTEX_init to semaphore_init in nv-linux.c
-#define NV_INIT_MUTEX(mutex) init_MUTEX(mutex)
+#define NV_INIT_MUTEX(mutex) semaphore_init(mutex)
builds and works fine here with that on 2.6.31-3-rt
** Attachment added: mutex_semaphore_nvidia.patch
using 2.6.31-8-generic on amd64 and system now restarts properly, thanks
all
--
[Karmic] Hangs during shutdown with kernel 2.6.31-7
https://bugs.launchpad.net/bugs/418509
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
Public bug reported:
nvidia-glx-185 conflicts with nvidia-glx-180 ( 185.18.37), this means
that newly dummy package nvidia-glx-180 cant't upgrade to the current
185.18.36-0ubuntu1 version. on upgrade this leads to all nvidia-180
packages being uninstalled and nvidia-185-kernel-source and
same thing, heres some kernel type stuff which may or may not be helpful
- stack backtrace of all currently executing tasks
- current tasks
- blocked tasks
** Attachment added: kernel.txt
http://launchpadlibrarian.net/30831850/kernel.txt
--
[Karmic] Hangs during shutdown
as the comment that goes with the patch says,
* The performance counter framework will initialize the LVTPC
* vector as NMI. We can't disable the framework but the kernel loader
* script will do 'echo 2 /proc/sys/kernel/perf_counter_paranoid'
* which hopefilly prevents any usage of hardware
actually i'll not quickly test on 2.6.30, its been dropped from ubuntu
pool for amd64. if someones still got it installed see if you can
generate the problem. if it comes down to it i'll rebuild from source
but obviously it would be easier if someone with it still installed
tried. i think their
in ppa
https://launchpad.net/~dinxter/+archive/ppa
** Attachment added: proc_owner_173-2.6.31.patch
http://launchpadlibrarian.net/30579888/proc_owner_173-2.6.31.patch
--
nvidia drivers version bump (173.14.20)
https://bugs.launchpad.net/bugs/398893
You received this bug notification because
** Attachment added: drm_agp_memory_173-2.6.31.patch
http://launchpadlibrarian.net/30579899/drm_agp_memory_173-2.6.31.patch
--
nvidia drivers version bump (173.14.20)
https://bugs.launchpad.net/bugs/398893
You received this bug notification because you are a member of Ubuntu
Bugs, which is
note, these patches work with current 173-173.14.16 package in karmic
--
nvidia drivers version bump (173.14.20)
https://bugs.launchpad.net/bugs/398893
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
in
karmic on 2.6.31 kernels, i'll put test packages in ppa
https://launchpad.net/~dinxter/+archive/ppa
** Attachment added: proc_owner_96-2.6.31.patch
http://launchpadlibrarian.net/30579993/proc_owner_96-2.6.31.patch
--
nvidia-96-kernel-source fails to build on Karmic
https://bugs.launchpad.net/bugs
** Attachment added: drm_agp_memory_96-2.6.31.patch
http://launchpadlibrarian.net/30580002/drm_agp_memory_96-2.6.31.patch
--
nvidia-96-kernel-source fails to build on Karmic
https://bugs.launchpad.net/bugs/391768
You received this bug notification because you are a member of Ubuntu
Bugs,
*** This bug is a duplicate of bug 325973 ***
https://bugs.launchpad.net/bugs/325973
** Changed in: nautilus (Ubuntu)
Status: Invalid = Confirmed
--
Nautilus hangs with show_desktop=false
https://bugs.launchpad.net/bugs/413568
You received this bug notification because you are a
how about,
#! /bin/sh
set -e
if [ $1 = purge ]
then
( userdel syslog
ERR=$?
if [ $ERR -eq 8 ] ; then
echo Ignoring removal of logged in user syslog
exit 0
else
exit $ERR
re added some patches from the last release to this one, module will
build and install but can't guarantee it'll actually work
fglrx-installer (2:8.632-0ubuntu2~dinxter2) karmic; urgency=low
* added find_task_by_vpid.patch (LP: #394985)
* added fglrx-2.6.30-irqreturn_t.patch
* added
latest virtualbox 3.0.4-50677 add to SUPDrv-linux.c so that = 2.6.31
kernels simply warn about nmi
/* 2.6.31+: The performance counter framework will initialize the LVTPC
* vector as NMI. We can't disable the framework but the kernel loader
* script will do 'echo 2
i've added the patched ose version that i'm using to my ppa if anyone else
finds it useful. note it has a small fix for building against
libpulse-dev/karmic uptodate 1:0.9.16~test4-0ubuntu1 so i dont know how it'll
go with non up to date pulseaudio versions.
https://launchpad.net/~dinxter
** Bug watch added: GNOME Bug Tracker #590965
http://bugzilla.gnome.org/show_bug.cgi?id=590965
** Also affects: gdm via
http://bugzilla.gnome.org/show_bug.cgi?id=590965
Importance: Unknown
Status: Unknown
--
gdm restarts on shutdown or restart in karmic
*** This bug is a duplicate of bug 403829 ***
https://bugs.launchpad.net/bugs/403829
** This bug has been marked a duplicate of bug 403829
flashplugin-installer prerm script fix
--
package flashplugin-installer 10.0.22.87ubuntu2 failed to install/upgrade:
subprocess installed
2 bugs in one. the sysklogd error is a duplicate so i'll reassign as a
gdm error
** Package changed: sysklogd (Ubuntu) = gdm (Ubuntu)
--
package gdm 2.27.4-0ubuntu6 failed to install/upgrade: subprocess installed
post-removal script returned error exit status 1
*** This bug is a duplicate of bug 401056 ***
https://bugs.launchpad.net/bugs/401056
** This bug has been marked a duplicate of bug 401056
package sysklogd (not installed) failed to install/upgrade: subprocess
installed post-removal script returned error exit status 1
--
package
sorry, should have mentioned which sysklogd bug duplicate
https://bugs.launchpad.net/ubuntu/+source/sysklogd/+bug/401056
my apologies
--
package gdm 2.27.4-0ubuntu6 failed to install/upgrade: subprocess installed
post-removal script returned error exit status 1
*** This bug is a duplicate of bug 403829 ***
https://bugs.launchpad.net/bugs/403829
** This bug has been marked a duplicate of bug 403829
flashplugin-installer prerm script fix
--
package flashplugin-installer 10.0.22.87ubuntu2 failed to install/upgrade:
subprocess installed
*** This bug is a duplicate of bug 403829 ***
https://bugs.launchpad.net/bugs/403829
** This bug has been marked a duplicate of bug 403829
flashplugin-installer prerm script fix
--
flashplugin cannot be reinstalled or desinstalled inconsistant...
https://bugs.launchpad.net/bugs/406507
*** This bug is a duplicate of bug 403829 ***
https://bugs.launchpad.net/bugs/403829
** This bug has been marked a duplicate of bug 403829
flashplugin-installer prerm script fix
--
Package doesn't install cleanly, then won't uninstall cleanly
https://bugs.launchpad.net/bugs/406085
You
it seems like a bit of a redundant check to me, trying to remove an
alternatives name is it has no links. but if we've removed the last link
then the name is automatically removed anyway. unless theres something
i'm missing we could drop altogether. still, daniels fix will certainly
do the trick
*** This bug is a duplicate of bug 399732 ***
https://bugs.launchpad.net/bugs/399732
** This bug has been marked a duplicate of bug 399732
vboxdrv occasionally fails to load on karmic 2.6.30 kernels due to active
nmi_watchdog
--
VirtualBox cannot load in the kernel 2.6.31-5 Karmic
from changelog,
dpkg (1.15.0) experimental; urgency=low
[ Raphael Hertzog ]
* Modify update-alternatives to always remove the alternative group when the
last alternative is removed (even in manual mode).
** Changed in: flashplugin-nonfree (Ubuntu)
Status: New = Confirmed
--
i'm using a version check to only remove-all on update-alternatives
1.15 since its redundant with 1.15,
DPKG_VERSION=`update-alternatives --version |head -n1 |cut -f4 -d `
if [ $DPKG_VERSION \ 1.15 ] ; then
for p in $VARIANTS; do
[ `update-alternatives --list
i've *ERROR* map not found - inconsistent kernel data!!! happens with
at least up to 9.6 too, and that its the ati binary at fault so needs to
be fixed by them. don't know if thats true or not though. general
consensus seems to be that apart from filling up you log files with
hundreds of lines it
you can probably disable the messages if needs be but i don't have an
ati card to try, i'm guessing you might be able to drop the debug trace
parts below but its probably not that good an idea anyway
/usr/src/fglrx-8.620/firegl_public.c
#define TRACE_VM_OPEN_CLOSE(_f, _v) \
Public bug reported:
desktop entry is broken, heap-snapshot-viewer doesn't exist
$less /usr/share/applications/mprof-heap-viewer.desktop
[Desktop Entry]
Type=Application
Name=Mono Heap Snapshot Viewer
Exec=heap-snapshot-viewer
Terminal=false
Icon=monodoc
Categories=Profiling;Development;
$
Public bug reported:
Binary package hint: gdm
- boot to desktop with usplash enabled
- select shutdown or restart from desktop menu
- gdm respawns before being killed by the shutdown process
note i cant get this bug is usplash is disabled
attached /var/log/gdm, .1 files being the log on normal
** Attachment added: gdm.tar.gz
http://launchpadlibrarian.net/29720277/gdm.tar.gz
--
gdm restarts on shutdown or restart in karmic
https://bugs.launchpad.net/bugs/406962
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
also, in case its relevant i have
AutomaticLoginEnable=true
--
gdm restarts on shutdown or restart in karmic
https://bugs.launchpad.net/bugs/406962
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
seems something is happening with tty order as well
- on boot, system messages are on tty1, X on tty7 as normal
- on shutdown, system messages now appear on tty7 with gdm respawning on tty1
--
gdm restarts on shutdown or restart in karmic
https://bugs.launchpad.net/bugs/406962
You received this
* moved find_task_by_vpid to pid_task to fix,
- add file find_task_by_vpid.patch to /usr/src/fglrx-8.620/patches/
- add following lines to /usr/src/fglrx-8.620/dkms.conf
PATCH[6]=find_task_by_vpid.patch
PATCH_MATCH[6]=2.6.3[1]
- rebuild dkms module
** find_task_by_vpid.patch
https://launchpad.net/~dinxter/+archive/ppa
added find_task_by_vpid.patch to ppa (fglrx-installer - 2:8.620-0ubuntu4~ppa3 )
** Attachment added: fglrx-installer_8.620-0ubuntu4~ppa3.debdiff
http://launchpadlibrarian.net/29698911/fglrx-installer_8.620-0ubuntu4%7Eppa3.debdiff
--
fglrx
** Attachment added: dmesg.txt
http://launchpadlibrarian.net/29511446/dmesg.txt
--
2.6.31 kernels autoload i915, nouveau and nvidia modules on nvidia geforce card
https://bugs.launchpad.net/bugs/404496
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Public bug reported:
the kernel automatically loads i915,nvidia, and nouveau drivers. using
nouveau or nvidia for X still works as expected but its not ideal, a
broken ttm being loaded by i915 automatically a few weeks ago caused
problems loading the nouveau driver (see
*** This bug is a duplicate of bug 404496 ***
https://bugs.launchpad.net/bugs/404496
** This bug has been marked a duplicate of bug 404496
2.6.31 kernels autoload i915, nouveau and nvidia modules on nvidia geforce
card
--
0.0.14+git20090715-0ubuntu1 FATAL: Error inserting nouveau ttm:
** Attachment added: lsmod.txt
http://launchpadlibrarian.net/29511469/lsmod.txt
--
2.6.31 kernels autoload i915, nouveau and nvidia modules on nvidia geforce card
https://bugs.launchpad.net/bugs/404496
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Attachment added: lspci.txt
http://launchpadlibrarian.net/29511470/lspci.txt
--
2.6.31 kernels autoload i915, nouveau and nvidia modules on nvidia geforce card
https://bugs.launchpad.net/bugs/404496
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Actually, the user for the rsyslogd process is still syslog.
thats the essence of the problem. thats why i thought it might be a good
idea to test to make sure rsyslog isnt installed before attempting to
remove user syslog, i'm sure there are better ways than that to check if
sysklogd 'owns' the
sysklogd fails on postrm during purge since it tries to delete the user
syslog, but the replacement rsyslogd is logged in in as that user now.
D02: fork/exec /var/lib/dpkg/info/sysklogd.postrm ( purge )
userdel: user syslog is currently logged in
/usr/sbin/deluser: `/usr/sbin/userdel syslog'
The problem seems to be that the kernel is convinced i have some sort of
intel card and is trying to load the i915 module on boot for some
unknown reason which fails with lots of drm errors
[2.188278] [drm] Initialized drm 1.1.0 20060810
[2.189221] i915: Unknown symbol
i'm guessing this is a kernel bug and not nouveau which loads fine left
to its own devices. the bug seems to be kernel unneccessarily loading
i915 on boot, and it being broken, leaving nouveau unable to load ttm on
top of the remaining loaded drm module from i915 for whatever reason.
i'm guessing
*** This bug is a duplicate of bug 399482 ***
https://bugs.launchpad.net/bugs/399482
** This bug is no longer a duplicate of bug 399543
package bluez 4.45-0ubuntu2 failed to install/upgrade: subprocess new
pre-removal script returned error exit status 1
** This bug has been marked a
*** This bug is a duplicate of bug 399482 ***
https://bugs.launchpad.net/bugs/399482
** This bug is no longer a duplicate of bug 399543
package bluez 4.45-0ubuntu2 failed to install/upgrade: subprocess new
pre-removal script returned error exit status 1
** This bug has been marked a
*** This bug is a duplicate of bug 399482 ***
https://bugs.launchpad.net/bugs/399482
** This bug is no longer a duplicate of bug 399543
package bluez 4.45-0ubuntu2 failed to install/upgrade: subprocess new
pre-removal script returned error exit status 1
** This bug has been marked a
*** This bug is a duplicate of bug 399482 ***
https://bugs.launchpad.net/bugs/399482
** This bug is no longer a duplicate of bug 399543
package bluez 4.45-0ubuntu2 failed to install/upgrade: subprocess new
pre-removal script returned error exit status 1
** This bug has been marked a
*** This bug is a duplicate of bug 399482 ***
https://bugs.launchpad.net/bugs/399482
** This bug is no longer a duplicate of bug 399543
package bluez 4.45-0ubuntu2 failed to install/upgrade: subprocess new
pre-removal script returned error exit status 1
** This bug has been marked a
*** This bug is a duplicate of bug 399482 ***
https://bugs.launchpad.net/bugs/399482
** Changed in: bluez (Ubuntu)
Status: New = Confirmed
** This bug has been marked a duplicate of bug 399482
bluez: upgrade from 4.45-0ubuntu1 to 4.45-0ubuntu2 fails
--
package bluez 4.45-0ubuntu2
*** This bug is a duplicate of bug 399482 ***
https://bugs.launchpad.net/bugs/399482
** This bug is no longer a duplicate of bug 399543
package bluez 4.45-0ubuntu2 failed to install/upgrade: subprocess new
pre-removal script returned error exit status 1
** This bug has been marked a
*** This bug is a duplicate of bug 399482 ***
https://bugs.launchpad.net/bugs/399482
** This bug is no longer a duplicate of bug 399543
package bluez 4.45-0ubuntu2 failed to install/upgrade: subprocess new
pre-removal script returned error exit status 1
** This bug has been marked a
Public bug reported:
Binary package hint: nouveau-kernel-source
0.0.14+git20090715 module errors on install on up to date karmic amd64
$modprobe nouveau
FATAL: Error inserting nouveau
(/lib/modules/2.6.31-3-generic/updates/dkms/nouveau.ko): Unknown symbol in
module, or unknown parameter (see
Public bug reported:
Binary package hint: virtualbox-ose
the vboxdrv module has an occasional load error on karmic 2.6.30
kernels,
Jul 12 07:13:17 crystaltree kernel: [ 28.053203] vboxdrv: Trying to
deactivate the NMI watchdog permanently...
Jul 12 07:13:17 crystaltree kernel: [ 28.053207]
r...@crystaltree:~# modinfo ttm
filename: /lib/modules/2.6.31-3-generic/updates/dkms/ttm.ko
license:GPL and additional rights
description:TTM memory manager subsystem (for DRM device)
author: Thomas Hellstrom, Jerome Glisse
srcversion: 3BA5DC8F8CC665FDD7A44ED
depends:
also fails on 2.6.31-2-generic, with the one error
[ 93.984229] nouveau: Unknown symbol drm_find_matching_map
i've attached the same info as above for 2.6.31-2-generic if needed
** Attachment added: nouveau-2.6.31-2-generic.txt
*** This bug is a duplicate of bug 391398 ***
https://bugs.launchpad.net/bugs/391398
** This bug has been marked a duplicate of bug 391398
Applications segfault with gtk+ version 2.17.2 when selecting listbox values
--
Rhythmbox Segmentation Fault when editing Automatic Playlists
just to add that i still get this random crashing too as before with
latest gdm though i cant be sure gdm is the cause since it does seem to
be random rather than reproducible. twice in about 5 minutes this
morning, now i've enabled apport, attached to gdb and can't get the
thing to crash! i've
just to add that i still get this random crashing too as before with
latest gdm though i cant be sure gdm is the cause since it does seem to
be random rather than reproducible. twice in about 5 minutes this
morning, now i've enabled apport, attached to gdb and can't get the
thing to crash! i've
tarred logs attached. seemed to only be able to reproduce this on first
boot when X starts on tty1, when it crashes it restarts on 7. bug 396226
is exactly the problem i've been having so i'll move there if it isnt a
duplicate of this one
** Attachment added: gdm-logs.tar.gz
Might be helpful
seems i can regularly repeat the crash by booting as normal which gives,
- X starts on tty1
- open up something such as gnome-terminal
- type in several dozen characters press enter
- gdm crashes and restarts on tty7
In this scenario all the tty's are set to a US keymap which is
sudo stop tty1 certainly cures the problem here.
is the problem that usplash has control of tty7 when gdm tries to start and so
forces it onto tty1 instead?
--
GDM logs out after some minutes of typing on the keyboard
https://bugs.launchpad.net/bugs/396226
You received this bug notification
or have gdm bring usplash down if its still sitting on tty7 when it
starts so it can take over tty7
--
GDM logs out after some minutes of typing on the keyboard
https://bugs.launchpad.net/bugs/396226
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
i'm confused, init.d/gdm checks for splash and brings it down, but we
still end up on tty1. but if usplash isnt started on boot, all the
problems go away and we end up on tty7
--
GDM logs out after some minutes of typing on the keyboard
https://bugs.launchpad.net/bugs/396226
You received this
either,
- sudo stop tty1 after logging into your gnome session
or,
- boot kernel without the splash option to stop it using usplash
both methods work on this computer
--
GDM logs out after some minutes of typing on the keyboard
https://bugs.launchpad.net/bugs/396226
You received this bug
i've set a thread here,
http://ubuntuforums.org/showthread.php?t=1206717
for problems with this bug as it is triaged
--
GDM logs out after some minutes of typing on the keyboard
https://bugs.launchpad.net/bugs/396226
You received this bug notification because you are a member of Ubuntu
Bugs,
have attached the proper gdm logs, messages and syslog (* SESSION STARTED - 6 *
lines are just my mark on starting a gnome session)
if its any help, gdm starts on tty1 and on crashing leaves a few lines of junk
text on the console.
** Attachment added: gdm-crash_060709.tar.bz2
login from gdm session is fine but after a random amount of time the
session crashes when typing, happens no matter what app is being typed
into at the time. if you start the session from a tty 'startx' then
theres no problem, i can only assume its gdm related at the moment
amd64
gdm/karmic
sorry, the last attachment of logs were the logs for the restarted gdm
on crash hence the :1, its a sunday thing, i'm trying to generate proper
logs at the moment
seems to be a few people with this problem, when it happens are other
people always typing at the time?
--
gdm 2.26.1-0ubuntu2:
(hd0) /dev/sda
(hd1) /dev/sdb
(hd2) /dev/sdc
(hd3) /dev/sdd
(hd4) /dev/sde
/boot/grub/device.map (END)
which is fine. still dont get the install to device prompt either from
synaptic or apt-get with grub-pc purged and grub installed then
installing grub-pc again, though i do when
** Changed in: network-manager-openvpn (Ubuntu)
Status: New = Confirmed
--
network-manager openvpn package has no implementation
https://bugs.launchpad.net/bugs/395541
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
1 - 100 of 238 matches
Mail list logo
