** Bug watch added: freedesktop.org Bugzilla #24383
https://bugs.freedesktop.org/show_bug.cgi?id=24383
** Also affects: xserver-xorg-video-intel via
https://bugs.freedesktop.org/show_bug.cgi?id=24383
Importance: Unknown
Status: Unknown
--
kdm does not restart X server (that
The kernel fix referred to above is now available in Karmic:
linux (2.6.31-12.39) karmic;
* agp/intel: Fix the pre-9xx chipset flush.
Please update your kernel to linux-image-2.6.31-12-generic and test.
There are already several confirmations this new kernel solves the
issue.
--
[i865] karmic:
Testing shows this problem only occurs with KMS active.
Debugging with gdb shows we get a new frontbuffer when we logout and the
xserver is reset. However, the new frontbuffer is not connected to the crtc .
in drmmode_set_mode_major we have:
if (drmmode-fb_id == 0) {
ret
This bug has been fixed upstream. The commit is included in mesa 7.6
branch.
commit 2921a2555d0a76fa649b23c31e3264bbc78b2ff5
Author: Ian Romanick ian.d.roman...@intel.com
Date: Wed Sep 16 07:39:58 2009 -0700
intel: Deassociated drawables from private context struct in
intelUnbindContext
If
Closing the -intel task, as the bug was fixed in mesa:
mesa (7.6.0~git20090817.7c422387-0ubuntu4) karmic; urgency=low
* Add 109_fix_relocation_delta_for_wm_surfaces.patch: Fix relocation
delta for WM surfaces. This was a regression introduced in
0f328c90dbc893e15005f2ab441d309c1c176245
There is a kernel fix in Eric Anholt's drm-intel-next git tree that
seems to solve the freeze issue for me (on 865):
committer Eric Anholt e...@anholt.net
Fri, 11 Sep 2009 18:39:23 + (11:39 -0700)
commit e517a5e97080bbe52857bd0d7df9b66602d53c4d
agp/intel: Fix the pre-9xx
This bug has been fixed upstream. The commit is included in mesa 7.6
branch.
commit 2921a2555d0a76fa649b23c31e3264bbc78b2ff5
Author: Ian Romanick ian.d.roman...@intel.com
Date: Wed Sep 16 07:39:58 2009 -0700
intel: Deassociated drawables from private context struct in
intelUnbindContext
The most easy way to get logout/login working on intel in Kubuntu is to
set TerminateServer=true in kdmrc.
--- /etc/kde4/kdm/kdmrc.orig2009-09-17 00:06:11.209433377 +0200
+++ /etc/kde4/kdm/kdmrc 2009-09-17 00:02:03.920288377 +0200
@@ -493,7 +493,7 @@
# Restart instead of resetting the local
mesa commit i965: Fix relocation delta for WM surfaces (5604b27b93),
solves the same (or at least similar) issue for me on Intel GM965. It
was the error kernel: [ 184.761959] PGTBL_ER: 0x0080 in syslog
that pointed me to that commit. Both the missing window borders and the
freeze are fixed
** Also affects: gnome-bluetooth via
http://bugzilla.gnome.org/show_bug.cgi?id=593777
Importance: Unknown
Status: Unknown
--
setup new device doesn't do anything
https://bugs.launchpad.net/bugs/423090
You received this bug notification because you are a member of Ubuntu
Bugs, which
This issue was discussed on intel-gfx recently. The ringbuffer wraps
around in the middle of an instruction:
0x0001fff8: 0x1081: MI_STORE_DATA_INDEX
0x0001fffc: 0x0080:dword 1
Buffer size too small in MI_STORE_DATA_INDEX (2 3)
A fix has been committed in Eric Anholt's
Public bug reported:
This bug was originally reported upstream as
https://bugs.freedesktop.org/show_bug.cgi?id=22946
The upstream report was made running mesa, libdrm, xserver and -intel
from git. Now that mesa 7.6-devel arrived in Karmic, the same crash
happens in a pure Karmic installation
** Attachment added: BootDmesg.txt
http://launchpadlibrarian.net/30978260/BootDmesg.txt
** Attachment added: CurrentDmesg.txt
http://launchpadlibrarian.net/30978261/CurrentDmesg.txt
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/30978262/Dependencies.txt
**
The stacktrace on Karmic
** Attachment added: mesa_stacktrace.txt
http://launchpadlibrarian.net/30978301/mesa_stacktrace.txt
** Bug watch added: freedesktop.org Bugzilla #22946
https://bugs.freedesktop.org/show_bug.cgi?id=22946
** Also affects: mesa via
** Visibility changed to: Public
--
nautilus crashed with SIGSEGV in strcmp()
https://bugs.launchpad.net/bugs/413660
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
Attached is the output of hal-device
/org/freedesktop/Hal/devices/storage_model_DVDRW_SSM_8515S
There was no disk in the drive.
The crash happened before I could start anything myself.
** Attachment added: haldevice.txt
http://launchpadlibrarian.net/30322126/haldevice.txt
--
nautilus
Upstream git commit c255543c Should fix #591826 – nautilus crashed with
SIGSEGV in strcmp() solves the problem for me.
--
nautilus crashed with SIGSEGV in strcmp()
https://bugs.launchpad.net/bugs/413660
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Those lines in xsession-errors confirm compiz sets LIBGL_ALWAYS_INDIRECT:
Checking for texture_from_pixmap: not present.
Trying again with indirect rendering:
Checking for texture_from_pixmap: present.
However, your X log shows texture_from_pixmap is supported by the driver:
(II) AIGLX: enabled
Hi George,
to debug this issue, we need a bit more information:
- please attach the file .xsession-errors (from your home directory)
- please run the command glxinfo glxinfo.txt and attach the file glxinfo.txt
Most likely LIBGL_ALWAYS_INDIRECT is set by compiz. Can you disable compiz and
let
In Karmic you are using KMS. With KMS the names of the outputs have changed.
VGA is now VGA1 and LVDS is now LVDS1.
These are the output names you have to use in xrandr commands.
So, most likely, xrandr --output VGA1 --right-of LVDS1 --auto will do something
now.
Please let us know if that
ACL handling has moved again, now from udev-extras into udev (in 143-1).
As xserver-xorg already recommends udev, this issue should be fixed now.
** Changed in: xserver-xorg-video-intel (Ubuntu)
Status: Confirmed = Fix Released
--
[i945gme] Xorg very slow after upgrade
udev-extras is a dependency of ubuntu-standard, which is installed both in
todays live image and in the jaunty image.
Is it possible ubuntu-standard was removed during a partial upgrade for you?
--
[i945gme] Xorg very slow after upgrade
https://bugs.launchpad.net/bugs/384934
You received this
Great! I will close the bug then.
** Changed in: xserver-xorg-video-intel (Ubuntu)
Status: Incomplete = Fix Released
--
X server restarts when playing video, visualization
https://bugs.launchpad.net/bugs/368159
You received this bug notification because you are a member of Ubuntu
Bugs,
Your Xorg log shows i915_dri.so is properly loaded and drm was opened.
Yet glxinfo shows you get software rendering. That looks like a
permission problem with /dev/dri/card0. Permissions are handled via ACL
and the ACL should be set by udev in Karmic. However, your udev log does
not show any ACL
Kernel 2.6.28-13.44 with G41 support is now available in jaunty-updates.
** Changed in: linux (Ubuntu)
Status: Fix Committed = Fix Released
--
[g41] UXA - Test = broken, black screen after x11 start
https://bugs.launchpad.net/bugs/373765
You received this bug notification because you are
freedesktop 22189 was marked duplicate of 21322. Updated the bug watch.
** Bug watch added: freedesktop.org Bugzilla #21322
https://bugs.freedesktop.org/show_bug.cgi?id=21322
** Changed in: xserver-xorg-video-intel
Status: Invalid = Unknown
** Changed in: xserver-xorg-video-intel
Current Operating System: Linux mpt-ubuntu 2.6.27-11-generic #1 SMP Wed
Apr 1 20:57:48 UTC 2009 i686
You are using the Intrepid kernel, which does not have GEM. The fake bufmgr
which you get instead of GEM is too small to play video. If you want to play
video, you will need to use the jaunty
ProcVersion: Linux version 2.6.24-19-server
You are using a hardy server kernel, which does not have GEM.
Can you please install the jaunty generic kernel (2.6.28-11-generic) and boot
and test with that kernel?
** Changed in: xserver-xorg-video-intel (Ubuntu)
Status: Confirmed =
You are using the server kernel, which uses PAE. GEM is not compatible with PAE
and is therefore disabled.
That means you get the fake bufmgr, which is too small to handle video
correctly (fake bufmgr (1024 kB)).
Unfortunately, allocating more memory for the fake bufmgr was tried during
jaunty
*** This bug is a duplicate of bug 363821 ***
https://bugs.launchpad.net/bugs/363821
Blacklisted PCIID '8086:2a02' found
Compiz was disabled for GM965 in jaunty because of a major freeze bug. This is
not related to UXA.
See bug 363821 for the current status and suggestion how you can enable
You are using the intrepid kernel (2.6.27-11-generic x86_64), which does not
have GEM.
To play video in jaunty, you do need to use a gem enabled kernel.
Can you please test with the jaunty kernel (2.6.28-11-generic) and let us know
if that works?
** Changed in: xserver-xorg-video-intel (Ubuntu)
From Xorg log:
Current Operating System: Linux richardwolf 2.6.30-7-server #8-Ubuntu SMP Mon
May 25 15:03:02 UTC 2009 i686
That kernel is built with CONFIG_HIGHMEM64G=y and CONFIG_X86_PAE=y. Therefore
GEM is disabled.
Can you please test with the 2.6.30-7-generic kernel and see if that works?
Should be fixed by commit Fix segfault in DRI2 vblank syncing if the
region isn't onscreen, which handles the crtc=0x0 case.
** Package changed: xorg (Ubuntu) = xserver-xorg-video-intel (Ubuntu)
--
x server dies with a SIGSEGV when gnome screen saver blanks the display
The message (WW) intel(0): Failed to open DRM device in your X log suggests
kernel module i915 is not properly loaded.
Can you boot with kernel 2.6.30 and run the commands:
- lsmod lsmod.txt
- lshal lshal.txt
and attach the two files to this bug report?
Also, assuming i915 is indeed not
You could boot into 2.6.28, then install the set of packages you had when you
first filed this bug. After that, reboot in 2.6.30
Alternatively, you could try to set modeset=0 in /etc/modules and see if that
allows to start X with 2.6.30.
--
[945G/GZ] no direct rendering after upgrade to
*** This bug is a duplicate of bug 379504 ***
https://bugs.launchpad.net/bugs/379504
The cause of the problem is already known, see bug 379504
** This bug has been marked a duplicate of bug 379504
Xorg falls back to VESA on intel hardware
--
[i965GM] Karmic -intel 2.7.1-1ubuntu1: Xorg
Now the question is: Is something writing or reading beyond the end of
the exa offscreen buffer? Without the 32 MB unused memory after the exa
offscreen buffer, that would be beyond end of aperture. How can I find
what is doing that?
For further testing, I enabled DEBUG_MIGRATE in the xserver
Based on Eric Anholt's findings about freezes due to prefetching beyond
end of aperture (b.fd.o 21488), I have done some testing.
With Eric's patch applied in kernel 2.6.30-rc6 I still got the freeze. That
seemed to make sense: we are using EXA, and the exa offscreen buffer is using
the last
Thanks for the confirmation lshardytest.
Marking fix committed as the fixed kernel is currently available in
jaunty-proposed.
** Package changed: xserver-xorg-video-intel (Ubuntu) = linux (Ubuntu)
** Changed in: linux (Ubuntu)
Status: Incomplete = Fix Committed
--
[g41] UXA - Test =
Current Operating System: Linux mindvirus-laptop 2.6.27-8-eeepc-lean
Kernel 2.6.27 does not have GEM. Therefore UXA cannot work.
If you want to test UXA, you will need to use at least a 2.6.28 kernel.
--
[i945gme] Xorg crashes on startup (UXA bug)
https://bugs.launchpad.net/bugs/357942
You
The G41 graphics card is not supported yet in the jaunty kernel.
Therefore DRM and GEM are not available and UXA cannot work. Also
hardware acceleration is not available.
Fortunately support for the G41 has been added in kernel 2.6.28-12.43, which is
now available in jaunty-proposed.
It would be
According to the tvtime website, tvtime requires XV:
http://tvtime.sourceforge.net/problems.html#vidmemory
XV can only work with DRI, but DRI was disabled for the 865, see the message in
Xorg.0.log:
(**) intel(0): DRI is disabled because it fails to run without freezing on i810
and i865G
On Tue, 2009-04-21 at 11:31 -0700, Jesse Barnes wrote:
but can you include the whole log?
Sure, this is the full log of the same freeze of
http://launchpadlibrarian.net/25826804/intel_debug.tar.gz
** Attachment added: gdm-intel-debug.log.bz2
Can you try running your environment under INTEL_DEBUG=batch to see
batchbuffers as
they're executed?
I started gdm with sudo INTEL_DEBUG=batch /etc.init.d/gdm start and took
the last 5.000 lines from the gdm log (gdm-tail.log).
** Attachment added: intel_debug.tar.gz
Attached are the results with Jesse's error state patch.
After the freeze i915_gem_interrupt did not change.
** Attachment added: gpudump-errorstate.tar.gz
http://launchpadlibrarian.net/25802051/gpudump-errorstate.tar.gz
--
[i965] X freezes starting on April 3rd
On Sat, 2009-04-18 at 21:17 +, Zack Evans wrote:
@Sebastien: The Intel driver doesn't do acceleration with Virtual over
2048 - known limitation
That limitation does not apply to GM965.
--
[i965] X freezes starting on April 3rd
https://bugs.launchpad.net/bugs/359392
You received this bug
On Sat, 2009-04-18 at 21:02 +, JesseBarnes wrote:
I wonder if disabling render accel altogether would as well (ExaNoComposite
true
in xorg.conf)? Can someone who's seeing this frequently give that a try?
With ExaNoComposite true X still froze. Actually, it even seems to
freeze faster.
Xorg log shows:
(EE) intel(0): Cannot support DRI with frame buffer width 2048.
which is caused by this setting in your xorg.conf
Virtual 2560 1024
If you want to use compiz, you will need to reduce the virtual display
width to a maximum of 2048.
--
Poor display performance w/Intel 945GM,
I was able to reproduce the freeze with kernel 2.6.30-rc2 and capture
intel_gpu_dump data.
** Attachment added: intel-gpu-dump.tar.gz
http://launchpadlibrarian.net/25684031/intel-gpu-dump.tar.gz
** Attachment added: regs-after.txt
http://launchpadlibrarian.net/25684032/regs-after.txt
**
No problem Péter, thanks for confirming all is ok now.
** Changed in: xserver-xorg-video-intel (Ubuntu)
Status: Triaged = Invalid
--
[G33] performance drop (20-40fps) in games and compiz after upgrade to Jaunty
https://bugs.launchpad.net/bugs/359629
You received this bug notification
Given you have a GM945 and Xorg.0.log contains the lines
(EE) intel(0): Failed to set tiling on front buffer: rejected by kernel
(EE) intel(0): Failed to set tiling on back buffer: rejected by kernel
(EE) intel(0): Failed to set tiling on depth buffer: rejected by kernel
you are most likely
Your Xorg.0.log shows you are using an intrepid kernel (Current Operating
System: Linux skynet 2.6.27-7-generic).
This kernel does not support GEM, therefore you cannot use UXA.
EXA with a non-gem kernel is slow due to bug
http://bugs.freedesktop.org/show_bug.cgi?id=20797 (Non-GEM allocations
Your xorg.conf contains the line:
Virtual 3200 1200
Therefore DRI cannot be used:
(EE) intel(0): Cannot support DRI with frame buffer width 2048.
In Intrepid XV could still be used with overlay video. In jaunty XV
overlay needs DRI as well.
As a workaround you can use non-XV video, like you
I was able to reproduce this on my 945 and got a full backtrace.
** Attachment added: totem-crash.txt
http://launchpadlibrarian.net/24835744/totem-crash.txt
--
crash in drm_intel_gem_bo_start_gtt_access
https://bugs.launchpad.net/bugs/354688
You received this bug notification because you are
The problem is in xxv-intel, src/i830_video.c
In I830PutImage:
if (pPriv-buf == NULL) {
pPriv-buf = drm_intel_bo_alloc(pI830-bufmgr,
xv buffer, alloc_size, 4096);
if (pPriv-buf == NULL)
return BadAlloc;
if
** Bug watch added: freedesktop.org Bugzilla #21060
https://bugs.freedesktop.org/show_bug.cgi?id=21060
** Also affects: xserver-xorg-video-intel via
https://bugs.freedesktop.org/show_bug.cgi?id=21060
Importance: Unknown
Status: Unknown
--
crash in
(EE) intel(0): Cannot support DRI with frame buffer width 2048
caused by:
SubSection Display
Virtual 2640 800
EndSubSection
was the problem.
** Changed in: xserver-xorg-video-intel (Ubuntu)
Status: Fix Committed = Invalid
--
Compiz doesn't start after upgrade xorg-video-intel
This is fixed in Debian, libpcap 1.0.0-1:
* debian/patches/20-fix-any-intf.diff: New patch cherry-picked from
upstream; fixes handling of the 'any' device.
The any interface can be used in both tcpdump and wireshark again.
$ sudo tcpdump -D
1.eth0
2.wmaster0
3.wlan0
4.any (Pseudo-device
** Description changed:
+ Please sync libpcap 1.0.0-1 (main) from Debian unstable (main)
+
+ Motivation: the update fixes a bug where the any pseudo interface cannot
+ be used in tcpdump.
+
+ The package builds fine in a jaunty pbuilder and installs and runs fine on a
jaunty system. Tested
Public bug reported:
Binary package hint: module-init-tools
Upgrading module-init-tools 3.7~pre7-3 within a jaunty chroot on a hardy system
failed.
Running /var/lib/dpkg/info/module-init-tools.postinst configure with set +e
gives:
Running depmod for 2.6.28-8-generic...
WARNING: Couldn't open
Fixed upstream in Revision 11329:
* src/cpufreq-selector/cpufreq-selector-service.c: Make enum error
values array static. Fixes bug #573762.
--
cpufreq-selector crashed with SIGSEGV in dbus_g_method_return_error()
https://bugs.launchpad.net/bugs/331044
You received this bug
Public bug reported:
Binary package hint: apport
I had a crash in cpufreq-selector. When I wanted to report this crash by
clicking on the crash icon, then selecting Report, apport itself crashed.
As apport also couldn't report the apport crash, I have unpacked the crash file
with apport-unpack
** Attachment added: ApportLog.txt
http://launchpadlibrarian.net/23451194/ApportLog.txt
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/23451195/Dependencies.txt
--
apport-gtk crashed: UnboundLocalError: local variable 'replacements' referenced
before assignment
** Attachment added: Date
http://launchpadlibrarian.net/23451355/Date
** Attachment added: ExecutablePath
http://launchpadlibrarian.net/23451356/ExecutablePath
** Attachment added: InterpreterPath
http://launchpadlibrarian.net/23451357/InterpreterPath
** Attachment added: ProblemType
** Changed in: gwget2 (Ubuntu)
Assignee: Albert Damen (albrt) = (unassigned)
--
[jaunty] Please update gwget to 1.0.1 version
https://bugs.launchpad.net/bugs/334164
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
** Bug watch added: GNOME Bug Tracker #533152
http://bugzilla.gnome.org/show_bug.cgi?id=533152
** Also affects: gwget via
http://bugzilla.gnome.org/show_bug.cgi?id=533152
Importance: Unknown
Status: Unknown
--
unable to select options in recursive option window (all selected)
This seems to be http://bugs.freedesktop.org/show_bug.cgi?id=18668
Both this LP bug and the Redhat bug are referenced in that bug.
Fix was pushed as 9fe9b6e4ef669b192ee349e3290db5d2aeea273c and nominated for 1.6
Steven Harms reports the fix works on Intrepid.
** Also affects: xorg-server via
Attached are the requested info files.
Tweaking 60-persistent-storage.rules I found the disk activity only
occurs when a watch is added on a partition used for LVM.
Attached are the modified rules and the resulting watches
in /dev/.udev/watch.
** Attachment added: dpkgl.txt
Attached are the requested tar files. I used the modified
60-persistent-storage.rules from comment 49 to be able to boot.
Somehow this feels like I won the lottery today. Only a handful of
systems is affected, but yet, I have two of those
There is a difference though: my laptop (Intel ICH8 /
The problem seems to come from the watch option added in 60-persistent-
storage.rules.
1. Booting with break=premount drops me in busybox without problems. With
break=mount the disk activity already starts.
2. Booting with break=premount, then starting udevd and calling udevadm trigger
I have tested with two accounts, one old and one newly created.
The old account works fine when I login with password. Also manually umounting
and mounting Private works fine. However, this account was apparently created
before this bug was fixed, so automatic login is hit by comment 60 and 61.
Successfully tested in a hardy pbuilder.
A. with only hardy and hardy-updates enabled in the pbuilder the update failed:
Setting up tdsodbc (0.82-3) ...
rmdir: failed to remove `/var/lib/odbc': No such file or directory
snip
The upgrade is completed but there were errors during the ugprade
Bisecting patches 157 - 160 blames patch 158_raise_maxclients.patch.
Without this patch compiz works fine again on jaunty / nvidia-glx-180.
--
compiz/kwin freezes on login as of xorg-server 1.5.99.902-0ubuntu2
https://bugs.launchpad.net/bugs/326344
You received this bug notification because you
Fixed in:
hal (0.5.12~rc1-0ubuntu6)
* Add 00git_fix_drm_acls.patch: Fix copypaste error which assigned
the wrong access_control.file for /dev/drm/card* devices. It
previously copied input.device, but should be
linux.device_file. This brings back hardware GL rendering,
/lib/udev/rules.d/85-lvm2.rules contains RUN+=watershed sh -c '/sbin/lvm
vgscan; /sbin/lvm vgchange -a y' and
watershed needs /var/run.
Previously /var/run was created in the initramfs by
/usr/share/initramfs-tools/hooks/udev.
Now watershed is a separate package, so I added mkdir -p
GDM will only update the symlink for specific combinations of sequence
number / old gdm version, so it knows the symlink was not updated by the
system administrator. In this case, you changed the symlink yourself, so
gdm is not supposed to update it.
** Changed in: xorg-server (Ubuntu)
Fabien, the error message in your X log (EE) config/hal: couldn't
initialise context: (null) ((null)) looks similar to bug 264256. It
seems gdm may be started before hal for you as well. That would also
explain why a gdm restart works fine.
Can you please check the sequence numbers of the
In /usr/share/hal/fdi/policy/10osvendor/20-acl-management.fdi I replaced the
line:
merge key=access_control.file type=copy_propertyinput.device/merge
by:
merge key=access_control.file type=copy_propertylinux.device_file/merge
After a reboot, I got access to /dev/dri/card0 and graphics
I am not a member of group video:
$ groups
albert adm dialout cdrom plugdev lpadmin admin sambashare
(first user on the system, installed from intrepid live cd, upgraded to
jaunty)
Then for the hal acl:
- polkit-gnome-authorization shows console and active console should have
access to Video
http://cgit.freedesktop.org/hal/tree/fdi/policy/10osvendor/20-acl-
management.fdi shows the same lines for the DRM device. Forwarded
upstream.
** Bug watch added: freedesktop.org Bugzilla #18955
https://bugs.freedesktop.org/show_bug.cgi?id=18955
** Also affects: hal via
Can you please check the file permissions of /dev/dri/card* ?
libdrm in jaunty uses udev to create the device node, and I found
/dev/dri/card0 now gets mode 660 (crw-rw), instead of 666. If you get mode
660, please try to change the mode to 666 with sudo chmod 666 /dev/dri/card*
and test
Public bug reported:
libdrm 2.4.1 in Jaunty is configured with --enable-udev, so the device node
/dev/dri/card* now is created via udev and patch 01_default_perms.diff does not
help to set the right permissions anymore.
Therefore /dev/dri/card0 now gets file permissions crw-rw. This results
Thanks for testing. As this didn't help for Kevin, I have filed the
permissions issue as bug 306014.
** Changed in: xserver-xorg-video-intel (Ubuntu)
Status: Incomplete = Confirmed
--
2.5.1 driver release is outrageously slow
https://bugs.launchpad.net/bugs/303011
You received this bug
are no longer created after a reboot.
** Attachment added: sysklogd.debdiff
http://launchpadlibrarian.net/20258467/sysklogd.debdiff
** Changed in: sysklogd (Ubuntu)
Assignee: Albert Damen (albrt) = (unassigned)
Status: In Progress = Confirmed
--
[jaunty] klogd still active at shutdown
Thanks for the confirmation Graziano. I will add a proposal for a fix in
the new bug.
For future reference, if you find a bug affects a different package then you
thought first, you can change the package in the existing bug report. You can
do that by pressing the down arrow in the yellow bar,
are neither stopped by the rc0/6 stop symlinks
nor by the sendsigs script. Therefore the file system remains busy and
cannot be unmounted during shutdown or reboot.
** Changed in: sysklogd (Ubuntu)
Assignee: (unassigned) = Albert Damen (albrt)
Status: New = In Progress
--
[jaunty
To mark a bug as closed/solved, it either needs the status fix released or
invalid.
I will mark the bug as invalid, as it was not a real problem with glibc in
Ununtu.
** Changed in: ubuntu
Status: Fix Committed = Invalid
--
glibc missing on ibex 64bits
The lines Kernel logging re-started after SIGSTOP are strange.
I have the same messages (with / on ext3), also seeing / is busy when I
shutdown or reboot. It seems klogd and syslogd are not terminated anymore, and
keep the file system busy.
As a work-around, I have created symlinks in
Can you please attach a syslog containing a shutdown sequence?
If you do it quickly after you started your system it will be in
/var/log/syslog. If you do it later the log may have rotated to
/var/log/syslog.0
** Changed in: sysvinit (Ubuntu)
Status: New = Incomplete
--
initscripts in
I have installed dbus, dbus-x11 and libdbus-1-3 from hardy-proposed
(1.1.20-1ubuntu3.2) since yesterday and found no regressions.
- plugging in a USB memory stick opens a nautilus window showing the contents
of the memory stick
- disabling networking in the network-manager applet sets firefox,
+1
- with libglib2.0-0 from intrepid, the disk icon for Private was shown on
several places (desktop, places menu and under places in Nautilus)
- with libglib2.0-0 from intrepid-proposed the disk icons are not shown
anymore. Only the Private directory is visible in Nautilus.
- The Private
unebaguettesvp: can you please attach the file /var/log/Xorg.0.log (with the
gamepads attached to your pc)?
Did you reboot your pc after you installed the new xserver-xorg-input-evdev
package?
--
Intrepid: Gamepad Saitek P580 not working in games, buttons not detected.
Nick, I am surprised Gutsy works for you with inode size 256, given the
grub change was first made in Hardy (and even Debian got that fix only
in 0.97-30, Feb 2008). So I tested this and for me the Gutsy vm fails to
boot with grub error 2, just like Dapper did.
--
Dapper images fail to boot
Recently I had the grub error 2 when I wanted to move my system from an old
hard-disk to a new one.
It turned out recent mkfs will create the filesystem with inode size 256. This
is only supported by grub since hardy (grub 0.97-29ubuntu19).
ubuntu-vm-builder on hardy uses inode size 128 both
Ah, that was not too hard.
In /usr/share/pyshared/VMBuilder/disk.py line 282/283, I changed:
def mkfs_fstype(self):
return { TYPE_EXT2: ['mkfs.ext2', '-F'], TYPE_EXT3: ['mkfs.ext3',
'-F'], TYPE_XFS: ['mkfs.xfs'], TYPE_SWAP: ['mkswap'] }[self.type]
into:
def mkfs_fstype(self):
Please sponsor the attached debdiff to update gwget2 for epiphany 2.24.
The package builds fine in an intrepid pbuilder, installs and works in
epiphany-gecko 2.24.
** Attachment added: gwget2.debdiff
http://launchpadlibrarian.net/18612356/gwget2.debdiff
** Summary changed:
- 8.10 64-bit -
Sorry, I left out the pDev part. Here it is.
** Attachment added: pDev
http://launchpadlibrarian.net/18558872/pDev
--
Joystick detected as mouse, crashes X
https://bugs.launchpad.net/bugs/274203
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Looking at the change made in xorg-server (2:1.5.1-1ubuntu3), it seems
like the case of key_code255 should be captured and not cause a crash
anymore. So I guessed pDev might have something interesting, and indeed,
it does:
(gdb) print pDev-key
$2 = (KeyClassPtr) 0x0
(gdb) print *pDev-key
Cannot
I tested the attached patch against xorg-server 2:1.5.1-1ubuntu3 (1.5.2 is not
installable at the moment).
With this patch I could press all gamepad buttons without causing a crash.
* Add patch 143_fix-joystick-segfault.patch to fix segfault when a
joystick or gamepad is detected as mouse.
hal-device output for the Rumblepad.
** Attachment added: haldev-gamepad.txt
http://launchpadlibrarian.net/18535223/haldev-gamepad.txt
--
Joystick detected as mouse, crashes X
https://bugs.launchpad.net/bugs/274203
You received this bug notification because you are a member of Ubuntu
Bugs,
101 - 200 of 342 matches
Mail list logo
