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,
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
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
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
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
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,
Public bug reported:
Binary package hint: linux-image-2.6-386
On my MacBook, which uses the appletouch kernel driver and the synaptics X11
driver for trackpad support, the pointer acceleration
can't be changed. Attempts to change this acceleration by using the GNOME
mouse control panel,
Apparently, doing an rmmod appletouch and a modprobe appletouch will fix the
problem until X is restarted.
At that point, the previous behavior returns, and you have to redo the rmmod
and modprobe commands...
** Summary changed:
- Can't change pointer acceleartion on MacBook trackpad
+ Can't
Seems to be fixed as of Gutsy Tribe 1 - suspend/resume worked in my
tests on the same MacBook I had problems with in the past...
--
Macbook (core duo) does not sleep
https://bugs.launchpad.net/bugs/92635
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug
Public bug reported:
Binary package hint: mouseemu
When mouseemu is used - which it is in default installs on the MacBook - the
F11 and F12 keys are used by default as middle-click and right-click.
This is a very odd and unintuitive choice for a default - most users don't
expect to use F keys
Public bug reported:
Binary package hint: ubuntu-desktop
MANY laptops use touchpads that are handled by the Synaptics driver.
These touchpads have many advanced functions such as scrolling, tapping,
and so on. However, there is currently no way to change any of these
settings without editing
I have figured out the fix to this issue.
Apparently, the default xorg.conf has a line which interferes with changes in
acceleration.
Changing the line:
Option SendCoreEvents true
to
Option CorePointer
cures the issue.
Is there any way this can be made the default?
** Changed in: xorg
In my experience, these keys do NOT generate the same scancode - on my MacBook
one of them is 125 and the other is 126 (decimal - which mouseemu uses).
Anyway, I know F11 and F12 have been used for ever, but this is quite possibly
one of the most common issues mentioned in install walkthroughs
I guess cmd-click isn't that intuitive either (it's actually ctrl-click
on OS X, but ctrl is little-used on OS X, like command/meta on Ubuntu)
It is, however, physically easier to use than F11/F12. The ideal way to
do right-click with Macs on Ubuntu, though, is probably two-finger tap -
which I
Public bug reported:
Binary package hint: xorg-driver-synaptics
In the synaptics driver, there is an option to make two-finger tap
right-click. Could this be enabled by default? It is used on Macs
commonly, and would be quite helpful in this case (with only one mouse
button). I know that
I can confirm that the caps lock does not work on Gutsy on my MacBook
with mouseemu installed (and does work without it installed). I suggest
we disable this and just use the synaptics driver's advanced trackpad
functions for right-clicks (and maybe xkbmap).
--
No Caps Lock light on Macbook Pro
*** This bug is a duplicate of bug 33762 ***
https://bugs.launchpad.net/bugs/33762
** This bug has been marked a duplicate of bug 33762
Appletouch trackpad unbearably slow
--
Can't change pointer acceleration on MacBook trackpad
https://bugs.launchpad.net/bugs/119964
You received this
I managed to fix this by changing the SendCoreEvents line in xorg.conf to
Option CorePointer
Then I get better acceleration...
This only works on Gutsy, though - it breaks the trackpad on Feisty...
Can we get a fix in Gutsy?
--
Appletouch trackpad unbearably slow
I can confirm that patching libata-core.c as described in the
abovementioned link does indeed fix suspend-to-RAM on my first-
generation MacBook - which doesn't work on the Feisty stock kernel. I
made no other changes to the default Feisty kernel and built using the
Ubuntu kernel build procedure
Public bug reported:
Binary package hint: gnome-power-manager
When the system is suspended through Gnome Power Manager (right-clicking on
battery icon, setting it to suspend on lid close, etc etc), it
asks for the user's password upon resume. There should be an option to disable
this in the
Public bug reported:
Binary package hint: rhythmbox
After installing Feisty, I connected my iPod mini with the intent of
synchronizing my song library as I do in iTunes.
Upon connecting my iPod, rhythmbox appeared. It will read my iPod's songs, but
will not write songs to the iPod.
I am aware
Public bug reported:
In Ubuntu Feisty, plugging in an iPod (in my case, an iPod mini second
generation) and unmounting it by right-clicking the iPod desktop icon
and selecting Eject doesn't unmount the iPod cleanly. If this is done, an
unable to eject error message is displayed. Additionally,
I can confirm this on my MacBook (first generation). Changing the
tracking settings has no effect whatsoever - the speed of the trackpad
remains slow no matter what.
** Changed in: linux-source-2.6.20 (Ubuntu)
Sourcepackagename: None = linux-source-2.6.20
--
MacBook trackpad is glacial
*** This bug is a duplicate of bug 97255 ***
https://bugs.launchpad.net/bugs/97255
Public bug reported:
Binary package hint: libgimme-codec0
If I play an unprotected AAC audio file such as something ripped using iTunes
in the Totem media player, I get prompted twice to install codecs
This also happens for me.
If I play an unprotected AAC audio file such as something ripped using iTunes
in the Totem media player, I get prompted twice to install codecs before the
file will play.
The first time the codec wizard pops up when playing an AAC file, it suggests
installing a
Public bug reported:
Binary package hint: libgimme-codec0
If I play an AAC, MP3, or other format that the default Ubuntu install doesn't
support in the Totem player, the Easy-to-Install Codec Wizard prompts to
install the necessary codecs.
However, if I use rhythmbox, banshee, or just about
This, in fact, only occurs with hfsplus (Mac OS Extended)-formatted iPods.
FAT32 iPods unmount cleanly.
However, it is still an issue for these iPods.
--
iPod doesn't unmount cleanly
https://bugs.launchpad.net/bugs/113466
You received this bug notification because you are a member of Ubuntu
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
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
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
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
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
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
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
I have managed to determine that the problem only happens with madwifi
drivers loaded, and not when they are disabled. Thus, this seems like
it could be a madwifi issue - though it could be wireless/networkmanager
in general.
Here is the syslog output...
Oct 2 16:47:37 thully-laptop
*** This bug is a duplicate of bug 137738 ***
https://bugs.launchpad.net/bugs/137738
** This bug has been marked a duplicate of bug 137738
[gutsy] suspend / hibernate works fine, but after resume, I get a Failed to
suspend popup
--
Computer failed to suspend message on resume from
Public bug reported:
Binary package hint: powermanagement-interface
In Ubuntu Feisty and Gutsy, when I resume from suspend-to-RAM, about one
out every four times my system resumes to a black text console with a
blinking cursor instead of the normal X display. I am able to activate
the X display
This is on a MacBook Core Duo (first generation), just so the devs know.
It does NOT happen if I disable screen dimming altogether in gconf.
--
Screen brightness resets to default (maximum) on idle with AC plugged in
https://bugs.launchpad.net/bugs/137598
You received this bug notification
Here is the trace from gnome-power-manager when the brightness changes
to maximum on idle...
gpm_screensaver_powersave_idle_changed] gpm-screensaver.c:102 (23:12:51):
emitting powersave-idle-changed : (1)
[powersave_idle_changed_cb] gpm-idle.c:335 (23:12:51): Received GS powesave
idle
The issue here is:
*g-p-m changes the brightness to the dim brightness on idle with dim enabled
*g-p-m changes brightness value to full brightness on leaving idle with dim
enabled
*g-p-m changes brightness value to full brightness on idle with dim disabled
This all takes place in
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
I only have the problem in Firefox.
** Changed in: firefox (Ubuntu)
Status: Incomplete = New
--
Firefox horizontal scroll doesn't work properly
https://bugs.launchpad.net/bugs/126064
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for
** Changed in: gnome-mount (Ubuntu)
Status: Confirmed = New
--
Ubuntu has stopped recognizing my ipod
https://bugs.launchpad.net/bugs/121203
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
** Changed in: gnome-power-manager (Ubuntu)
Status: Confirmed = New
--
Error in automatic diminuition of brightness when idle
https://bugs.launchpad.net/bugs/63543
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
** Changed in: linux
Status: Confirmed = Invalid
--
MacBook makes whining noise when uhci-hcd loaded
https://bugs.launchpad.net/bugs/124642
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
This has been fixed with recent releases..
** Changed in: xorg-driver-synaptics (Ubuntu)
Status: Confirmed = Fix Released
--
Appletouch trackpad unbearably slow
https://bugs.launchpad.net/bugs/33762
You received this bug notification because you are a member of Ubuntu
Bugs, which is a
** Changed in: fontconfig (Ubuntu)
Status: Confirmed = New
--
fontconfig don't use autohinter as default
https://bugs.launchpad.net/bugs/14310
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs mailing list
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
** 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
Public bug reported:
Binary package hint: hal
On my MacBook in Gutsy Beta, suspending to RAM results in a Your
computer failed to suspend and an Action forbidden message from the
gnome-power-manager. As the system in fact suspended and resumed
successfully, this is in error. To me, this seems
Public bug reported:
Binary package hint: msttcorefonts
When installing msttcorefonts, one is presented with extremely verbose
information referring to the Debian Font Manager (defoma). This
information wasn't presented in Feisty, and is for the most part
irrelevant to 99% of Ubuntu users, as
Public bug reported:
Binary package hint: ubiquity
If I run the Ubuntu ubiquity installer and start an install (i.e. to the
point of copying files...), closing the status window does NOT
kill ubiquity and the install process. To the contrary, it continues to run in
the background. Could this
Public bug reported:
Binary package hint: ubiquity
Installing from the Ubuntu Gutsy Beta Desktop CD seems to leave an entry for
the CD itself in the sources.list.
This can be confusing and is for the most part unnecessary, as there is very
few packages on the CD itself (and of those that are
Public bug reported:
Binary package hint: usplash
When booting from the Gutsy live CD, the progress bar is off center with
respect to the Ubuntu logo, creating an ugly/unpolished appearance. It
looks fine on a Feisty live boot, as well as from a Gutsy installed
system. This has existed since
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
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
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 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
1 - 100 of 210 matches
Mail list logo
