I must note that I do have the composite extension enabled. If I disable
composite, I see these issues occur much less frequetly.
On 7/27/07, Julien Cristau [EMAIL PROTECTED] wrote:
On Thu, Jul 26, 2007 at 23:27:51 -0400, Tim Hull wrote:
When using the new intel video driver that replaced
Goglin [EMAIL PROTECTED] wrote:
Tim Hull wrote:
I must note that I do have the composite extension enabled. If I
disable composite, I see these issues occur much less frequetly.
Less frequency or not at all?
Brice
driver. This did not happen with
i810+915resolution.
Before freezing/rebooting, the console always displays a checkerboard
pattern.
On 8/9/07, Tim Hull [EMAIL PROTECTED] wrote:
Actually, I don't think it happens at all - at least I can't reproduce it
as of now without composite. So this seems
Package: fontconfig-config
Version: 2.4.2-1.2
With the default font configuration, Arial and the other fonts that make up
the MS Core Fonts aren't remapped/aliased to any sane alternative. Thus, if
Arial is used by a website in a browser that uses the system default font
configuration, it will
Package: compiz
Version: 0.5.0.dfsg-2
Priority: important
On Debian sid with the latest Compiz and X installed, running compiz
--replace with an active Gnome/Metacity session results in there being no
window borders. Compiz effects (cube, window effects, alt+tab, etc) all
work, but none of my
Package: debian-installer
Version: 20070308
Priority: wishlist
During installs from CD-ROM and DVD media, users are still currently
prompted to set up the network and download security fixes from the
network. However, many (quite possibly most) users who use the full-blown
install media (as
Package: debian-installer
Version: 20070308
During an Etch install, the partitioning step is inconsistent about the
definition of a gigabyte.
For example, when LVM volumes are created, the definition of GB used for
specifying their size is
(1024*1024*1024) bytes. However, the definition of GB
Package: gdebi
Version: 0.2.4debian1
Currently, I have gdebi installed on my Debian Sid system. While it is
registered as a handler for the MIME type application/x-deb in the system,
it is NOT the default application for GNOME/Iceweasel/etc to handle .deb
files (File Roller is). It seems like
Package: debian-installer
Version: 20070308
I recently used d-i to install Debian Etch to a volume that was part of an
LVM volume group that contained an active snapshot volume. While the
installation proceeded fine, it issued an error message to the effect that
something was wrong with the
Package: gnome-power-manager
Version: 2.18.3-1
Priority: wishlist
Currently, when one suspends-to-RAM using the Suspend option in
gnome-power-manager, the display is locked upon resume from suspend. This
is somewhat annoying, as I did not set my system to lock on suspend-to-RAM
in the suspend
I guess having it look for a network in the background and silently fail
would be preferable, in any case. Is this doable?
On 8/10/07, Christian Perrier [EMAIL PROTECTED] wrote:
Quoting Tim Hull ([EMAIL PROTECTED]):
It would be GREAT if the network-related steps would be skipped/bypassed
Of course security updates should be enabled by default, and I do agree
that it's sensible for the system to _ask_ to try to install security
updates even if there's no network. But there are cases where security
updates don't make much sense, and I do think that the current behaviour
Package: nautilus-cd-burner
Version: 2.18.2-1
In a Debian sid install with the desktop task installed,
nautilus-cd-burner isn't the default handler
associated with the mimetype for .ISO files - file-roller is. This should
be changed, such that opening a .iso file burns its contents to a CD.
The message states:
Unable to determine geometry of file/device. You should not use Parted
unless you REALLY know what you're doing!
The log is attached...
On 8/10/07, Otavio Salvador [EMAIL PROTECTED] wrote:
Tim Hull [EMAIL PROTECTED] writes:
Package: debian-installer
Version
Any warning?
Is gtk-window-decorator running after starting compiz? if so, kill it
and compiz --replace again and again?
Brice
The warnings I got were:
GLX_EXT_texture_from_pixmap is not available with direct rendering.
GLX_EXT_texture_from_pixmap is available with indirect rendering.
This is intentional, because it is a very bad idea, security speaking,
not to lock the screen when you are not using the system.
If you really want to do that, you can change
the /apps/gnome-power-manager/lock_on_suspend GConf key.
OK - I guess I don't like it because Mac OS X and Windows
Hi,
Is there any progress on this issue (spontaneous rebooting in X with the
intel driver)?
I'm experiencing this on both Debian and Ubuntu with said driver, so it
definitely is an upstream issue.
Has an upstream bug been filed? I'm not acquainted with X.org's bug
reporting system myself...
In
Package: gksu
Version: 2.0.0-1
On my Debian Etch install with backported 2.6.22 kernel, running any
application that uses gksu (such as the Root Terminal) causes an
extraordinarily high amount of wakeups (and thus, a large amount of power to
be consumed) as measured with the PowerTOP 1.7 tool.
-- Forwarded message --
From: Joey Hess [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Date: Wed, 15 Aug 2007 16:13:23 -0400
Subject: Re: Bug#437018: Network shouldn't be used/enforced on non-network
installs
Wouter Verhelst wrote:
(there's no working connection to the Internet,
Package: network-manager
Version: 0.6.4-8
When using a madwifi-based wireless card (with driver built from
madwifi-source 0.9.3-3 in sid), it is currently impossible to associate to
any access point using NetworkManager. NetworkManager will see the access
points, but upon attempting to
Package: linux-image-2.6-686
Version: 2.6.22-1
Since kernel 2.6.21, my MacBook has made a subtle whining noise when idle.
This happens when using the Debian stock kernels from testing and unstable,
but also when using other kernels. I believe it has something to do with
certain ACPI
Package: udev
Version: 0.105-4
On my hardware (MacBook Core Duo), the appletouch module is used for maximum
functionality of the touchpad. However, this module is not loaded at boot
by default - instead, the usbhid module is used, which works but doesn't
support advanced features of the
: ID 05ac:8240 Apple Computer, Inc.
Bus 003 Device 001: ID :
Bus 001 Device 008: ID 05ac:0217 Apple Computer, Inc.
Bus 001 Device 001: ID :
On 7/24/07, Marco d'Itri [EMAIL PROTECTED] wrote:
On Jul 24, Tim Hull [EMAIL PROTECTED] wrote:
On my hardware (MacBook Core Duo
Package: kernel-image-2.6-686
Version: 2.6.22-1
On my MacBook Core Duo, I am experiencing random kernel panics on boot.
The message I am getting is as follows:
Kernel panic - not syncing: IO-APIC + timer doesn't work!
This appears about 50% of the time on boot, and happens on every version of
I have spent a significant amount of time dealing with issues between
MadWifi and wext/wpasupplicant/NetworkManager on Debian (etch, lenny, AND
sid). As it stands, there are still significant issues - in factI cannot
associate *at all* to my stock, unencrypted WRT54G using
NetworkManager+madwifi
Package: madwifi-source
Version: 0.9.3-3
Severity: wishlist
Currently, the release version of madwifi is missing a significant amount of
functionality when compared to the trunk builds at madwifi.org. For one
thing, the trunk builds add support for 802.11n Atheros chipsets, which are
found in
I think this just simply a dupe of 399039, and I figure Ubuntu is building
HAL with MacBook support. From the looks of that kernel driver, it appears
us MacBook users are stuck with pommed until somebody writes a kernel driver
to interface with HAL..
On 7/26/07, Tim Hull [EMAIL PROTECTED] wrote
I'm actually on a MacBook (non-Pro) but I figure HAL works the same in both
cases...
On 7/26/07, Sven Arvidsson [EMAIL PROTECTED] wrote:
On Thu, 2007-07-26 at 18:14 +0200, Julien BLACHE wrote:
HAL/g-p-m should support the MacBook {,Pro} out of the box, and
without pommed as far as the LCD
brightness
control support as I do on Ubuntu with the same version of g-p-m?
I am running Debian unstable currently, so I do have the latest versions of
everything...
On 7/26/07, Loïc Minier [EMAIL PROTECTED] wrote:
On Thu, Jul 26, 2007, Tim Hull wrote:
In Ubuntu Feisty, gnome-power-manager includes
Package: gnome-power-manager
Version: 2.18.3-1
Severity: wishlist
In Ubuntu Feisty, gnome-power-manager includes support for controlling LCD
brightness. In Debian, the shipped version of gnome-power-manager does NOT
have this feature. Could Debian please sync with the Ubuntu patchset for
this
configurations? I figure Ubuntu includes the patches necessary to adjust
MacBook brightness, and Debian does not.
On 7/26/07, Loïc Minier [EMAIL PROTECTED] wrote:
On Thu, Jul 26, 2007, Tim Hull wrote:
I have acpi-support, and I have the other significant power-management
stuff
installed here
I applied the attached patch (from Ubuntu) to the latest 2.6.22 kernel from
Sid and it resolved the problem. Could this be looked into?
On 7/24/07, Debian Bug Tracking System [EMAIL PROTECTED] wrote:
Thank you for the problem report you have sent regarding Debian.
This is an automatically
OK - It appears the underlying issue is that HAL is built without MacBook
support for the reason that it uses hackish solutions (writing directly to
/dev/mem in particular). Ubuntu builds HAL with MacBook support, and hence
g-p-m functions fine on that distribution.
I merged this with the bug
Then I figure that this is NOT, in fact, an issue of merging Ubuntu patches
OR an issue related to pommed but a bug with g-p-m recognizing MacBooks in
Debian. I've retitled the bug appropriately. Does anyone have a clue as to
where I would look? I'm thinking Ubuntu configures something to make
Just default acpi-support + gnome-power-manager (I set my system to suspend
on lid close).
On 7/27/07, Julien Cristau [EMAIL PROTECTED] wrote:
On Thu, Jul 26, 2007 at 23:27:51 -0400, Tim Hull wrote:
When using the new intel video driver that replaced the former i810
driver in Debian, I am
I figure that's the issue for me - though I don't have access to a Lenny/Sid
machine to test it at the moment. You can go ahead and close this if you
wish...
On 8/24/07, Sven Arvidsson [EMAIL PROTECTED] wrote:
On Fri, 2007-08-24 at 22:14 +0200, Brice Goglin wrote:
So the actual original bug
Hi,
I am thinking 408207 and 385599 are dupes - they sould like pretty much the
same bug to me.
Anyway, this still exists in the latest package - I can use my Wifi by
configuring it manually through GNOME's Network control panel,
but not through network manager.
What I have found is that the
37 matches
Mail list logo
