Same problem here with a first-generation MacBook. Downgrading HAL
fixes it - evidently something in the new HAL update caused this. Could
this be looked at for Hardy final? This seems like a bad regression to
have...
--
MacBook brightness adjustment does not work in Hardy
Try installing the -virtual kernel flavor - that has the modules needed.
On Sun, Mar 9, 2008 at 4:31 PM, Philipp Knuesel
[EMAIL PROTECTED] wrote:
From the install process:
* Loading open-vm-tools modules
FATAL: Module vmhgfs not found.
FATAL: Module vmmemctl not found.
--
VMware Fusion
Public bug reported:
In Hardy, the linux-virtual metapackage is broken. To be specific, said
package depends on a linux-restricted-modules-virtual package - one that
doesn't exist. Could this dependency be removed such that the linux-
virtual metapackage could work properly?
** Affects:
Could this be nominated for beta? It is still around, and it would be
pretty bad IMO to have this in the final product - particularly for an
LTS. I had a posted fix that works somewhat (towards the beginning of
this bug) - could the devs responsible for g-p-m take a look at this and
integrate
This still happens on Hardy alpha 5. I posted a potential fix in this
bug - could devs look at this/potentially tidy up what I did? I'm kind
of out of the loop for Hardy (first discovered this in Gutsy testing
cycle), but I do plan to be back for the Intrepid Ibex test cycle
(hopefully it will
Public bug reported:
After I install open-vm-tools, I expected to have a new HGFS mount point
at /mnt/hgfs, just as I do after installing standard VMware Tools.
However, this was not created, and I had to manually create it and
create the mount point. Could this be done automatically by the
Public bug reported:
Currently, the linux-ubuntu-modules package for the virtual kernel
type used on virtual machines doesn'tinclude the ES1370/1 drivers used
for the sound card that VMware emulates. As a result, when using this
kernel with VMware productsyou get no sound. Could the proper
Public bug reported:
After I installed open-vm-tools in an Ubuntu Hardy guest running on
VMware Fusion 1.1.1, I received the following error message during the
open-vm-tools configuration process and on every subsequent boot during
the boot process:
The VMware Tools poweron script did not run
That is my experience (as the original bug reporter) myself - though I
haven't tested 2.6.24-2 yet (I did use -12, though). Does anyone know for
sure when it was fixed? Was it still an issue in 2.6.23 or 2.6.24-1? It
would be nice to see an official backport of the fix to Gutsy...
On 1/1/08,
** Attachment added: dmesg2
http://launchpadlibrarian.net/10228603/dmesg2
--
New in 2.6.22-13: System doesn't always wake from suspend
https://bugs.launchpad.net/bugs/151016
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
Also, here is my /var/log/dmesg from after the suspend. It is different
from the dmesg command output...
** Attachment added: dmesgvarlog
http://launchpadlibrarian.net/10228820/dmesgvarlog
--
New in 2.6.22-13: System doesn't always wake from suspend
https://bugs.launchpad.net/bugs/151016
According to Volanin's analysis, this seems to be something introduced upstream
- likely in 2.6.22.8 or 2.6.22.9.
I will also concur with the fact that after waiting 5-10 minutes one can always
wake up the system - and sometimes pressing the power button wakes it before
that.
Anyway, I have
I believe I have traced the bug. Anyway, in my suspend/resume testing,
through trial and error I found that the issue does NOT occur if I
unload the ohci1394 module prior to suspend. Even if I'm having it
occur almost every suspend on a particular boot, unloading ohci1394
makes it go away. As
Apparently, there is an upstream fix. Could this be done as a SRU?
--
Songs that have a space in their path are not imported automatically from
watched music folders
https://bugs.launchpad.net/bugs/147883
You received this bug notification because you are a member of Ubuntu
Bugs, which is the
I spoke too soon - it started happening again with ohci1394 unloaded.
Thus, I'm still completely baffled as to what introduced the issue...
** Summary changed:
- New in 2.6.22-13: ohci1394 causes system to take a LONG time to resume from
suspend
+ New in 2.6.22-13: system takes a LONG time to
In that case, something should be done, as aggressive power management is
enabled by default - and as the reports demonstrate, this is causing a
significantly shorter disk life than on other OSes.
On 10/24/07, Matthew Garrett [EMAIL PROTECTED] wrote:
By default, we do nothing to set any disk
Is my problem different from this? Because I know that the latest ppa
package does NOT fix it for me - my NetworkManager still randomly
crashes...
--
Network manager crash with WPA
https://bugs.launchpad.net/bugs/145683
You received this bug notification because you are a member of Ubuntu
Bugs,
Does it work fine with -12? If not, your problem is different. If so, your
problem is the same.
On 10/22/07, Jens Bergqvist [EMAIL PROTECTED] wrote:
The bug is not limited to MacBooks. I can confirm this exact behaviour on
an HP NX7300 laptop (Intel Core 2 T5600 / 945GM) running the latest
P.S. You can get the -12 kernel from the links on the MacBook wiki at:
https://help.ubuntu.com/community/MacBook
On 10/22/07, Tim Hull [EMAIL PROTECTED] wrote:
Does it work fine with -12? If not, your problem is different. If so,
your problem is the same.
On 10/22/07, Jens Bergqvist
What chipset/graphics card/etc does your laptop have? Wifi? I'm curious,
as I'd like to narrow down what component this bug caused a regression with.
On 10/22/07, Jens Bergqvist [EMAIL PROTECTED] wrote:
I tracked down 2.6.22-12 just after I posted my comment and as far as I
can tell it works
The chipset and graphics are the same as mine - everything else is different
(I have a Core Duo and Atheros wireless).
On 10/22/07, Jens Bergqvist [EMAIL PROTECTED] wrote:
Some general specs:
CPU: Intel Core 2 Duo T5600 1.83GHz
Chipset: Mobile Intel 945GM Express
Graphics: Intel Graphic
I just noticed that someone else mentioned this on the Ubuntu MacBook wiki
and directed MacBook users to the 2.6.22-12 kernel as the last working
kernel. Indeed, I am actually running that kernel right now so that I can
have suspend.
Anyway, It would be nice to get this fixed so that MacBook
I did some testing, and it appears it *is* a kernel bug after all, as
this happens when using Kubuntu or when manually running pmi from the
command line. Also, I reloaded my system with the -12 kernel (from
Ubuntu beta) and the issue doesn't appear. Marking as invalid, and
reopening the previous
My bad - I spoke too soon. Even though I got some errors from g-p-m in
the process, the root problem remains with the kernel. I've reverted my
kernel to the -12 kernel included on the Gutsy beta CD and it works
fine, though I would like to see this fixed in a SRU for the current
Gutsy kernel.
Also of not - sometimes I can wake my system when frozen in this state
by closing the lid, waiting a few seconds, connecting/disconnecting the
power cord, and then pressing the power dutton. However, this only
revives the system about half of the time.
--
New in 2.6.22-13: System doesn't always
The issue is new on Gutsy, so that would be expected.
If you can, try the patch I posted above, However, this would require
compiling gnome-power-manager from source...
On 10/18/07, Vaioinman [EMAIL PROTECTED] wrote:
Hi
My laptop is Compaq V3527, Core 2 Duo 7300, Intel X3100 and I have
OK - I am managing to reproduce it when suspending using the menu options. I
am, however, opening the lid to resume in this case.
In any case, I figure g-p-m is somehow receiving erroneous lid and/or
suspend events, and as such is stuck in a suspend loop.
--
System doesn't always resume
Honestly, I'd remove the package - I've heard many reports of breakage on
many configurations, and better to ship nothing at all than the horrible
breakage that is displayconfig-gtk.
On 10/17/07, David Fokkema [EMAIL PROTECTED] wrote:
With only 1 day to go... I'm afraid this won't make it
If you reset your virtual machine, does NetworkManager work for a while
after the reset?
On 10/16/07, Ryan Gordon [EMAIL PROTECTED] wrote:
Just wanted to let you know that I'm experiencing the same problems as
Tim Hull. I'm on Ubuntu Gusty installed into VMWare - Everything was
working fine
OK, so it probably is a different issue - my problem is that NetworkManager
dies after working properly for a while...
On 10/16/07, Ryan Gordon [EMAIL PROTECTED] wrote:
No, it doesn't work if I reset my virtual machine. I've tried it several
times before already.
What I did was:
1) Burn
Any way we could get a patch for this in Gutsy? It seems like the patch
would simply have to ensure compiz starts in the right order...
--
Large fonts in window titles
https://bugs.launchpad.net/bugs/141001
You received this bug notification because you are a member of Ubuntu
Bugs, which is the
Could this be looked at? Currently, changing *anything* in
displayconfig-gtk results in a bad xorg.conf for me...
--
displayconfig-gtk recognizes the correct resolution but uses 640x480 instead
https://bugs.launchpad.net/bugs/137792
You received this bug notification because you are a member of
The bug is actually a gnome-power-manager bug, so I'm closing this and
opening a bug against it. I actually *can* get video after this type of
freeze - it's just that I have to close the lid for a while and press
the on button.
** Changed in: linux-source-2.6.22 (Ubuntu)
Status: New =
Public bug reported:
Binary package hint: gnome-power-manager
In recent versions of gnome-power-manager (recent meaning 2.20ish
versions), my system (MacBook Core Duo) sometimes doesn't properly wake
from suspend if I open the lid.
When this happens, I hear some system noise on resume but get
Here's the backtrace info...
Program received signal SIGPIPE, Broken pipe.
[Switching to Thread -1212664144 (LWP 3388)]
0xe410 in __kernel_vsyscall ()
(gdb) bt
#0 0xe410 in __kernel_vsyscall ()
#1 0xb7c8ddce in writev () from /lib/tls/i686/cmov/libc.so.6
#2 0xb7e9deb6 in ?? () from
Here's the thread apply all backtrace:
(gdb) thread apply all bt
Thread 3 (Thread -1221059696 (LWP 3394)):
#0 0xe410 in __kernel_vsyscall ()
#1 0xb7c8b647 in poll () from /lib/tls/i686/cmov/libc.so.6
#2 0xb7dac593 in ?? () from /usr/lib/libglib-2.0.so.0
#3 0x0809d628 in ?? ()
#4
Here's the output before the crash...
[EMAIL PROTECTED]:/root/network-manager-0.6.5/src$ sudo gdb
.libs/lt-NetworkManager
GNU gdb 6.6-debian
Copyright (C) 2006 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or
is this a patch for my issue? If so, could you post a .deb?
On 10/15/07, Alexander Sack [EMAIL PROTECTED] wrote:
** Attachment added: patch to drop supplicant shutdown feature and its
followup patches
http://launchpadlibrarian.net/10004427/lp145683-proposed.patch
--
Network manager
I figure it sounds like a DS game :) Though I called it the Grey Blocks of
Death.
In any case, it's good to see this fixed - now i810/915resolution can be
banished forever.
On 10/14/07, Sitsofe Wheeler [EMAIL PROTECTED] wrote:
Juan, Peter, Bryce (and everyone else) - thanks for your work on
This happens here if i disable and then re-enable Compiz in the same
session.
--
window title bar disappears completely on all windows
https://bugs.launchpad.net/bugs/148958
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
This also happens, independently of when it happens in other
applications, in OpenOffice.org. As is the case with the title bar
fonts, it occurs sporadically.
--
Large fonts in window titles
https://bugs.launchpad.net/bugs/141001
You received this bug notification because you are a member of
This seems to have been fixed with recent uploads. Closing.
** Changed in: compiz (Ubuntu)
Status: Confirmed = Fix Released
--
Large fonts in window titles
https://bugs.launchpad.net/bugs/141001
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug
I still can't reproduce anymore here - maybe your mirror is behind or this
issue is one that is very hardware/settings specific.
One question - could you try changing the desktop effects settings to
maximum, then back to normal effects, and then rebooting? That may have
been what fixed it for me
I will try sometime in the next few days - I've been busy...
On 10/11/07, Alexander Sack [EMAIL PROTECTED] wrote:
Tim, if you can reproduce this, please come to #ubuntu-mozillateam
channel on irc.freenode.net and ping me (asac).
Thanks,
- Alexander
--
Network manager crash with WPA
Yes, I know that - this just isn't the greatest time at the moment. I
should have time tomorrow, though - and Monday/Tuesday...
I just installed your new package, and will report if it improves anything.
On 10/12/07, Alexander Sack [EMAIL PROTECTED] wrote:
well ... time is not on our side ...
Reopening since it started happening again...
** Changed in: compiz (Ubuntu)
Status: Fix Released = New
--
Large fonts in window titles
https://bugs.launchpad.net/bugs/141001
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
Have you tried the .deb posted above for testing? That is supposed to fix
the problem - and does for me...
On 10/11/07, naught101 [EMAIL PROTECTED] wrote:
I'm still getting this on the latest updates for gutsy (kubuntu).
The bug is serious, it makes it impossible to shut down, or hibernate
TDB: could you try with the 2.6.22-12 kernel from the beta release? I'm
wondering if you're experiencing bug #151016...
On 10/11/07, TDB [EMAIL PROTECTED] wrote:
@Bryce Harrington
Testing xserver-xorg-video-intel_2.1.1-0ubuntu7~bwh1_i386.deb
VT switch OK (used to work 100% for me anyway),
Are you saying that this does happen with the 2.6.22-12 kernel for you? If
so, then your issue is different from mine - as my machine has suspend
issues with 2.6.22-13 and up but works fine in -12.
On 10/11/07, TDB [EMAIL PROTECTED] wrote:
@Tim Hull:
now running 2.6.22.12.15
there's newer
Here is a picture of the large fonts in question...
** Attachment added: Screenshot.png
http://launchpadlibrarian.net/9948678/Screenshot.png
--
Large fonts in window titles
https://bugs.launchpad.net/bugs/141001
You received this bug notification because you are a member of Ubuntu
Bugs,
And here is a picture of normal fonts to compare...
** Attachment added: Screenshot-1.png
http://launchpadlibrarian.net/9948688/Screenshot-1.png
--
Large fonts in window titles
https://bugs.launchpad.net/bugs/141001
You received this bug notification because you are a member of Ubuntu
Bugs,
Could everybody who is seeing this bug please e-mail the Ubuntu
Technical Board at [EMAIL PROTECTED] and give detailed
information about your hardware/how this issue effects you? I'm having
trouble getting any devs to look at this - they think it is MacBook-
specific, and are thus considering it
I have - they haven't seemed to really notice it...
On 10/11/07, Simon Ruggier [EMAIL PROTECTED] wrote:
Why not send a link to this bug?
--
Screen brightness resets to default (maximum) on idle with AC plugged in
https://bugs.launchpad.net/bugs/137598
You received this bug notification
2.6.22-14 also exhibits this. It seems like it tends to happen if the
machine is left in suspend for an extensive period of time (i.e. more
than a few minutes).
--
New in 2.6.22-13: No video after resume from suspend on MacBook
https://bugs.launchpad.net/bugs/151016
You received this bug
I see what you are saying - i810 is an inferior driver to intel, crash
issues aside. However, at the same time, shipping a driver known to
hard crash randomly upon doing such common things as logging out or
suspending to RAM seems irresponsible.
I feel that Ubuntu should go back to i810 as
Sorry for the lack of info in earlier posts...
My video chipset is 945GM. Also, my issue in particular happens randomly when:
1) changing VTs
2) Logging out
3) Killing the X-server
4) Suspending to RAM
Under each of these circumstances, I randomly get the grey blocks of
death, and then my
OK - that makes some sense to me. In that case, could this bug be
mentioned in the release notes with instructions on switching to i810
for those who experience an intolerable number of crashes? I believe
OpenSUSE had such a note in their 10.3 release notes and shipped both
drivers with -intel
OK - I've added a blurb to the release notes about the issue. If possible,
sould some people test and make sure the graphical X setting tool can
properly change the driver? I've had some problems with this, but it should
work as it is a showcased feature in Gutsy.
On 10/10/07, Bryce Harrington
Is anyone seeing this on non-MacBook hardware? I ask because a few of
the devs are not seeing this issue, and I would like to see it fixed in
Gutsy. Also, does anyone have a patch from upstream or another
distribution?
--
Screen brightness resets to default (maximum) on idle with AC plugged in
Is anyone seeing this on non-MacBook hardware? I ask because a few of
the devs are not seeing this issue, and I would like to see it fixed in
Gutsy. Also, does anyone have a patch from upstream or another
distribution? My patch doesn't fully fix the issue (i.e. the brightness
still changes upon
Is there anything else I can do to help resolve this issue? Is my issue
different from that originally reported? This is quite annoying, as I
have to deal with network-manager randomly crashing on a regular
basis...
--
Network manager crash with WPA
https://bugs.launchpad.net/bugs/145683
You
*** This bug is a duplicate of bug 127101 ***
https://bugs.launchpad.net/bugs/127101
Somehow, I totally missed the boat on this one. The issue is indeed X -
and in particular the craptastic intel X server. Marking as dupe of
127101, since this seems like a special, unique case of that.
**
On a somewhat-related note:
For some wacky reason, the graphical X configuration tool keeps giving me an
unusable 640x480 setup. Should the release notes be updated to direct users
to xorg.conf?
On 10/10/07, Tim Hull [EMAIL PROTECTED] wrote:
I tried turning off DRI, and while the issue went
I tried turning off DRI, and while the issue went away (or at least
lessened), I then became unable to resume from suspend-to-RAM (no video
appeared). This happened spontaneously with DRI enabled, but happened all
the time with DRI disabled. Thus, I feel that using i810 is a more
recommendable
I just installed the new package, spent about 20 minutes trying to crash it
with the usual methods, and I have been unable to reproduce the crashes
anymore. I repeatedly suspended-to-RAM, logged out, changed VTs, and even
killed the X server - with no grey block crashes. In the past, I could
In further investigation, X does seem to be involved (the issue does
seem to occur more with the -intel driver, and especially if you disable
DRI), but so does the kernel. Reopening as a kernel bug, as this does
seem to be an issue that does NOT exist on -12 and does on -13 and -14.
Could devs
I just installed it, and will keep you updated as to whether the problem
comes back or disappears...
--
Network manager crash with WPA
https://bugs.launchpad.net/bugs/145683
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
I very much doubt upstream will have anything before Gutsy release.
Could we integrate my patch or possibly a similar one with some minor
changes? It wouldn't be very good IMO to have the brightness randomly
increasing in Gutsy final as it does now...
--
Screen brightness resets to default
I have figured out that the current font problem is limited to Compiz,
so adding that as a package which this bug occurs in and re-closing the
bug in xorg-server...
** Also affects: compiz (Ubuntu)
Importance: Undecided
Status: New
** Changed in: xorg-server (Ubuntu)
Status: New
Please look at this as it related to Compiz... I have huge title bar
fonts after starting X with Compiz enabled (with Compiz disabled, it's
fine...).
--
Font sizes in Gutsy are affected by bad X.org DPI detection
https://bugs.launchpad.net/bugs/118745
You received this bug notification because
I have had the crash occur with the latest update - dunno what triggered
it...
On 10/9/07, Peter Weissgerber [EMAIL PROTECTED] wrote:
Hmm, I repeated these steps now 15 times in a row. No crash.
Before the yesterday's update I was able to crash the computer simply by
1. go to a terminal and
Because of this issue's importance and ability to crash systems, I just
e-mailed the Technical Board to ask them to switch back to i810 as the
default driver for supported chipsets in Gutsy (as was the case in Feisty).
Yes, you may have to use 915resolution, but you lose the random crashes - in
my
** Changed in: compiz (Ubuntu)
Status: New = Invalid
--
Font sizes in Gutsy are affected by bad X.org DPI detection
https://bugs.launchpad.net/bugs/118745
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs
Public bug reported:
Binary package hint: linux-image-2.6.22-13-generic
On my MacBook Core Duo (first generation, 32-bit), in the newest Ubuntu
kernel I have no video after resuming from suspend-to-RAM on my MacBook
about 1 out of every 4 or 5 suspend/resume cycles. This only started
after the
** Attachment added: acpid
http://launchpadlibrarian.net/9899879/acpid
--
New in 2.6.22-13: No video after resume from suspend on MacBook
https://bugs.launchpad.net/bugs/151016
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
** Attachment added: dmesg
http://launchpadlibrarian.net/9899884/dmesg
--
New in 2.6.22-13: No video after resume from suspend on MacBook
https://bugs.launchpad.net/bugs/151016
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
** Attachment added: kern.log
http://launchpadlibrarian.net/9899885/kern.log
--
New in 2.6.22-13: No video after resume from suspend on MacBook
https://bugs.launchpad.net/bugs/151016
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for
** Attachment added: user.log
http://launchpadlibrarian.net/9899886/user.log
--
New in 2.6.22-13: No video after resume from suspend on MacBook
https://bugs.launchpad.net/bugs/151016
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for
I just had a crash occur with the newly-updated packages from the PPA.
After the crash, nm-applet continues to run, but reports no network
devices found. This just occured out of the blue - I wasn't
associated with any networks and didn't suspend-to-RAM, log out, or
anything of that sort.
I
Still not working for me with those updates.
On 10/9/07, Jeff Sharpe [EMAIL PROTECTED] wrote:
Works with this mornings updates:
ii compiz 1:
0.6.0+git20071006-0ubuntu2 OpenGL window and compositing manager
ii compiz-core
I should note that the i810 driver doesn't have this problem, so if your
card supports it you can use this and avoid the crashes. You do need
915resolution, though...
Devs: If this problem doesn't get fixed for final, could the default driver
be set to i810(+915resolution included) for cards
I'm somewhat busy currently and don't have access to my Linux install, but I
will point out something that I think is related to the issue - the fact
that my system has a widescreen display. I have a feeling that the code to
do the splash screen on Gutsy is somehow messed up in the way it handles
Since the patch, I am noticing that while NetworkManager doesn't seem to
disappear from the system tray spontaneously as before, it does become
non-operational (i.e. the nm-applet says No network Devices have been
found). Thus, if the problem I'm experiencing is indeed a duplicate of
this bug
In Gutsy Beta 1, I am seeing this problem again with VMware Fusion 1.0 and
1.1b1. In particular, what is happening is that in addition to the vmmouse
driver not being used by default, it isn't even *included* on the beta 1 cd.
Thus, I had to download it from the repository and manually edit
In Gutsy this works fine.
** Changed in: fontconfig (Ubuntu)
Status: New = Invalid
--
Times should map to Times New Roman, etc, if installed...
https://bugs.launchpad.net/bugs/137601
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for
The issue still isn't fully fixed for me. On my MacBook (13.3,
1280x800, intel graphics), the fonts for the user id on the login screen
and for application title bars are still gigantic. However, the rest of
the fonts are OK, and restarting X once after booting up will resolve
the issue with the
There is no issue as long as the touchpad is in the xorg.conf. From my
understanding, xorg.conf-less operation is not officially supported in
Gutsy, so closing this.
** Changed in: gnome-control-center (Ubuntu)
Status: New = Invalid
--
Tap to click option in Touchpad settings has no
Gutsy fixes this.
** Changed in: ubuntu-meta (Ubuntu)
Status: New = Fix Released
--
Remove mouseemu from Ubuntu default install
https://bugs.launchpad.net/bugs/137594
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
** Changed in: gnome-power-manager (Ubuntu)
Status: Fix Committed = Fix Released
--
Brightness Head-Up dialogue always appears after Idle
https://bugs.launchpad.net/bugs/122682
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
It seems a bit better in Gutsy, and you can adjust the speed through
xorg.conf. You still can't change the speed in the GUI, but that's for
a future release. Closing.
** Changed in: linux-source-2.6.20 (Ubuntu)
Status: New = Fix Released
--
MacBook trackpad is glacial
** Changed in: mouseemu (Ubuntu)
Status: Fix Committed = Fix Released
--
No Caps Lock light on Macbook Pro
https://bugs.launchpad.net/bugs/103375
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
Public bug reported:
Binary package hint: powermanagement-interface
After I resume my MacBook from suspend in Ubuntu Gutsy, the Bluetooth icon in
my GNOME system tray disappears.
All other icons remain in the system tray - it's only the Bluetooth icon that
disappears. I am using a MacBook
Public bug reported:
Binary package hint: compiz
On my MacBook Core Duo (first generation) with Ubuntu Gutsy installed, the
bottom GNOME taskbar doesn't appear after logging in with Compiz enabled.
To get it to appear, I must click on the bottom of the screen - at which point
it appears. On
Public bug reported:
Binary package hint: xserver-xorg-driver-vmware
In Gutsy, when using VMware Fusion with the autodetected settings and
the vmware driver, the resolution used by default is significantly
larger than the maximum resolution of my MacBook's screen (1680x1050).
In previous
Well, there isn't really a problem if idle dimming is enabled - in that case
it dims properly to the idle brightness setting. That is, unless
brightness is already set to a lower setting, in which case the brightness
increases (but that's another bug).
In any case, if some kind of patch can't be
Yes - fixing that would require a previous brightness variable in the
code. It would basically be checked, and then the brightness code would
take it into account when exiting idle.
I figure the best way to fix all these brightness problems would be to:
1. Do not use idle events when
Here is the patch I came up with. Basically, when the idle callback
is called, this will stop it from changing the brightness if idle
dimming is disabled. Hope this is suitable - I know one could suppress
the idle callback from being called, but it seems that it is used for
other things
This is now once again an issue with the latest gnome-power-manager code
in Gutsy.
** Changed in: gnome-power-manager (Ubuntu)
Status: Fix Released = Confirmed
--
Error in automatic diminuition of brightness when idle
https://bugs.launchpad.net/bugs/63543
You received this bug
Here is a patch that should resolve the issue...
** Attachment added: gpm-backlight.c.diff
http://launchpadlibrarian.net/9690441/gpm-backlight.c.diff
--
Error in automatic diminuition of brightness when idle
https://bugs.launchpad.net/bugs/63543
You received this bug notification because you
It seems like my issue intermittently occurs - and occurs most when I'm
resuming from suspend. I'm not connecting to any wireless networks when
it happens, though there are many in range.
Could we possibly restart NetworkManager on resume from suspend? It
seems that this would help somewhat in
1 - 100 of 210 matches
Mail list logo
