Public bug reported:
Binary package hint: firefox
Not sure if this is a bug with firefox, compiz, or gnome-panel, but
firefox is the only app where I see this behavior.
Sometimes firefox will exhibit this weird behavior:
1) Firefox appears to freeze, so I close it. The firefox entry in the
** Attachment added: Screenshot.png
http://librarian.launchpad.net/7112421/Screenshot.png
--
firefox disappears, but remains open
https://bugs.launchpad.net/bugs/100047
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
Public bug reported:
Binary package hint: compiz
The cube effect on compiz on my default feisty beta install didn't work.
A little poking around (= me installing gnome-compiz-manager) showed
that the cube effect had only one desktop enabled.
This can't possibly be the default behavior for
I'd like to confirm this bug on my machine too (Feisty beta).
Here's my lsusb:
Bus 003 Device 004: ID 090c:1000 Feiya Technology Corp. Memory Bar
Bus 003 Device 001: ID :
Bus 002 Device 001: ID :
Bus 001 Device 001: ID :
and my lshal is attached.
** Attachment
** Attachment added: Screenshot of problem described in bug report.
http://librarian.launchpad.net/6990859/Screenshot.png
--
compiz - windows won't maximize, but border changes and twitches
https://launchpad.net/bugs/96785
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
Public bug reported:
Binary package hint: compiz
Kind of the opposite of bug #71818; sometimes when I try to maximize a
window, it stays the same size but the window border changes to its
maximized state.
Running Feisty Beta on an ATI Radeon IGP. I had to apply the Option
XAANoOffscreenPixmaps
I'd like to confirm this problem also, with a new feisty beta
installation. Adding XAANoOffscreenPixmaps to xorg.conf fixed my
problem as well.
Using oss ati drivers on an ati radeon igp.
--
desktop-effects doesn't start compiz correctly
https://launchpad.net/bugs/80734
--
ubuntu-bugs mailing
Public bug reported:
Binary package hint: hal
Bug #65028 (https://bugs.launchpad.net/bugs/65028) still exists in
feisty beta. This bug concerned not being able to change screen
brightness in gnome-power-manager.
There was a fix posted to the edgy eft version of this bug (sudo mv /bin/sh
Public bug reported:
Binary package hint: gnome-power-manager
I have a sony PCG-K15 laptop. In Dapper I could change my screen
brightness settings using the gnome-power-manager configurator. In Edgy,
I can't anymore.
I'm not sure what information you need to figure out why this is
happening, so
Cool. Thanks!
--
can't change screen brightness
https://launchpad.net/bugs/69975
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
I have the exact same problem. Attached are lspciv.txt and lspcivvn.txt
from my computer.
** Attachment added: lspci output
http://librarian.launchpad.net/4564131/lspci%20output.tar.bz2
--
dhclient connect wireless in kernel 2.6.15, but not in 2.6.17
https://launchpad.net/bugs/61566
--
11 matches
Mail list logo