The patch is now in 2.6.31-rc1
--
[PATCH] appletouch reports multiple fingers when only one is pressed
https://bugs.launchpad.net/bugs/371574
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.
This patch should be in 2.6.31 http://www.spinics.net/lists/linux-
input/msg03595.html
--
[PATCH] appletouch reports multiple fingers when only one is pressed
https://bugs.launchpad.net/bugs/371574
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
*** This bug is a duplicate of bug 371574 ***
https://bugs.launchpad.net/bugs/371574
** This bug has been marked a duplicate of bug 371574
[PATCH] appletouch reports multiple fingers when only one is pressed
--
synaptics driver middle clicks on text selection
https://bugs.launchpad.net/bu
BTW, I did sent it to linux-input.
--
[PATCH] appletouch reports multiple fingers when only one is pressed
https://bugs.launchpad.net/bugs/371574
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@li
Public bug reported:
Binary package hint: libgl1-mesa-dri
ubuntu jaunty 9.04
Apple PowerBook G4
libgl1-mesa-dri 7.4-0ubuntu3
glxgears shows a blue background instead of a black background.
Fedora rawhide does not have this problem. I don't have any more sample
points.
:00:10.0 VGA compat
Yeah, it's definitely loading the swrast dri driver... and I can't
figure out a way trick it into using r300...
:00:10.0 VGA compatible controller: ATI Technologies Inc RV350 [Mobility
Radeon 9600 M10]
Subsystem: ATI Technologies Inc RV350 [Mobility Radeon 9600 M10]
Control:
I just noticed this in /var/log/Xorg.0.log:
(II) AIGLX: Screen 0 is not DRI2 capable
(II) AIGLX: Screen 0 is not DRI capable
(II) AIGLX: Loaded and initialized /usr/lib/dri/swrast_dri.so
(II) GLX: Initialized DRISWRAST GL provider for screen 0
... ?
--
swrast, r300: backgrounds render blue inst
Yes, it happens with the livecd.
Also of possible interest, I need to use video=ofonly to get the livecd
to work for me. I don't need that with the installed kernel for some
reason (I removed it from yaboot.conf and reran ybin).
--
swrast, r300: backgrounds render blue instead of black
https:/
Architecture: powerpc
DistroRelease: Ubuntu 9.04
Package: mesa
ProcEnviron:
SHELL=/bin/bash
LANG=en_US.UTF-8
ProcVersion: Linux version 2.6.28-6-powerpc (bui...@adare) (gcc version 4.3.3
(Ubuntu 4.3.3-5ubuntu4) ) #20-Ubuntu Fri Apr 17 08:30:40 UTC 2009
Uname: Linux 2.6.28-6-powerpc ppc
UserGroup
Ok, this is certainly a kernel issue. After changing over to Fedora's
2.6.29.1-111 kernel, the issue has gone away.
Here are related kernel log entries when the problem was occurring with the
ubuntu kernel:
[ 30.413499] radeonfb :00:10.0: Invalid ROM contents
[ 30.593004] [drm] Initializ
Architecture: powerpc
DistroRelease: Ubuntu 9.04
Package: mesa
ProcEnviron:
SHELL=/bin/bash
LANG=en_US.UTF-8
ProcVersion: Linux version 2.6.29.1-111.fc11.ppc
(mockbu...@ppc6.fedora.phx.redhat.com) (gcc version 4.4.0 20090423 (Red Hat
4.4.0-1) (GCC) ) #1 Fri Apr 24 10:44:43 EDT 2009
Uname: Linux
** Attachment added: "xdpyinfo.txt"
http://launchpadlibrarian.net/26224938/xdpyinfo.txt
--
r300 on "PowerBook G4" mac: only swrast after booting and backgrounds render
blue instead of black
https://bugs.launchpad.net/bugs/370200
You received this bug notification because you are a member of
** Attachment added: "system.txt"
http://launchpadlibrarian.net/26224937/system.txt
--
r300 on "PowerBook G4" mac: only swrast after booting and backgrounds render
blue instead of black
https://bugs.launchpad.net/bugs/370200
You received this bug notification because you are a member of Ubun
** Attachment added: "xkbcomp.txt"
http://launchpadlibrarian.net/26224940/xkbcomp.txt
--
r300 on "PowerBook G4" mac: only swrast after booting and backgrounds render
blue instead of black
https://bugs.launchpad.net/bugs/370200
You received this bug notification because you are a member of Ub
This second round of apport-collect is with Ubuntu mesa/libdrm/Xorg/ati
x11 drivers and the fc11 kernel. The only non-ubuntu bits are the
Fedora kernel.
I'm going to try the karmic kernel, but it looks like it's going to be a
pain, since it's not building on ppc right now due to missing
debian/ru
I have not ever had this problem in a fedora kernel, but I don't have
many sample points. I have only used:
2.6.27.xx from fc10 (all versions used in fc10 have been good)
2.6.29.1-46 from fc11
2.6.29.1-111 from fc11
Note that versions between 2.6.29.1-46 and -111 had other issues
preventing r300
Using current master from the karmic kernel
(c14be1e8e5d32db04cdf02a51b2a5e47c292a5c0) and a config based on the
jaunty ppc kernel, I am no loner experiencing this issue...
so the issue is either solved in mainline or a patch has been added to
ubuntu kernel to address the problem.
I'm guessing th
*** This bug is a duplicate of bug 223812 ***
https://bugs.launchpad.net/bugs/223812
Over a year later and still happening in jaunty and the current karmic
kernel (2.30-rc4 based)
--
powernowd init script does not start the daemon on ppc (ondemand problem)
https://bugs.launchpad.net/bugs/200
*** This bug is a duplicate of bug 223812 ***
https://bugs.launchpad.net/bugs/223812
And this isn't a bug with powernowd. This is a kernel bug... please
change the component appropriately.
--
powernowd init script does not start the daemon on ppc (ondemand problem)
https://bugs.launchpad.ne
Public bug reported:
Binary package hint: kernel-package
2.6.29 and later kernels have section mismatch reported my modpost.
This is reported upstream where I provided a patch:
http://bugzilla.kernel.org/show_bug.cgi?id=13228
** Affects: kernel-package (Ubuntu)
Importance: Undecided
2.6.29.2 vanilla does not have this issue either.
--
r300 on "PowerBook G4" mac: only swrast after booting and backgrounds render
blue instead of black
https://bugs.launchpad.net/bugs/370200
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu
2.6.28.9 vanilla also has working drm and agp. The last commit in
linux-2.6.28.y that should affect this code was on 12/23:
commit 8960223d5973b3eaf8cbc1984969bb6c7661e7b9
Merge: d519c8d... 077ebed...
Author: Linus Torvalds
Date: Tue Dec 23 17:01:40 2008 -0800
Merge branch 'drm-fixes' of
Public bug reported:
Binary package hint: xserver-xorg-input-synaptics
I think there might be a problem in the synaptics driver. I'm using my
powerbook G4 on Ubuntu Jaunty with a recent kernel (2.6.30-rc4 ish) and
the appletouch driver.
I have 'enable mouse clicks with touchpad' disabled in gno
Also the enable/disable 2-finger scrolling option in the Mouse
Preferences just changes the rate (the"Synaptics Scrolling Distance"
property). It doesn't actually enable/disable scrolling. You also
need to change this property:
xinput set-int-prop appletouch "Synaptics Two-Finger Scrolling" 8 1
** Attachment added: "appletouch.patch"
http://launchpadlibrarian.net/26305586/appletouch.patch
--
[PATCH] appletouch reports multiple fingers when only one is pressed
https://bugs.launchpad.net/bugs/371574
You received this bug notification because you are a member of Ubuntu
Bugs, which is s
Public bug reported:
Binary package hint: kernel-package
This issue affects atleast jaunty and karmic. The patch is against
current karmic.
The appletouch driver is prone to reporting multiple fingers when only one is
pressing. The appletouch driver queries an array of pressure sensors and
cou
Is it completely hung? Can you ssh in from another box? I noticed a
problem with the nvidia drivers resuming from suspend, but I could still
ssh in from another box to debug. X was consuming all my CPU and it
looks like it was spinning in the nvidia drivers with this backtrace:
(gdb) bt
#0 0x0
Public bug reported:
I am choosing "I don't know" for the package because this tool seems
broken. I selected "linux-image-2.6-amd64-generic" from the "Choose..."
list, but it still complains!
kernel is 2.6.28-11 generic
echo "mem" > /sys/power/state
press power to resume.
The screen does not r
I also notice "vbetool post" consuming 100% CPU during resume. See this
bug report for more info on the specific problem, but there's an oops
before vbetool gets run, so vbetool's hangup may be an artifact of
another bug (but it should still not sit and spin).
https://bugs.launchpad.net/ubuntu/+b
The screen state restore is problematic, and I think there are multiple
issues at work here. When I boot my kernel with 'test_suspend=standby
no_console_suspend', I still get the following:
[ 14.176212] [ cut here ]
[ 14.176277] WARNING: at /build/buildd/linux-2.6.28/
After looking at the kernel source, I realized that wasn't an oops... it
was just a stack trace warning that was triggered by the resume taking
too long (but it unfortunately doesn't identify exactly WHAT made it
take so long). This occurs with test_suspend=standby on boot, so it's
not related
The title needs to be changed since this is not an oops, but I don't see
where to do that...
I used the pm trace functionality described here:
https://wiki.ubuntu.com/DebuggingKernelSuspend
but I did not get anywhere with that. On the next boot, dmesg showed:
Magic number: 5:435:547
but there w
I did send it to Jason Parekh (jasonparekh at nospam gmail.com) who
was the one who wrote the original code.
I have not sent it to linux-input.
On May 4, 2009, at 17:36, Leann Ogasawara wrote:
> Hi Jeremy,
>
> Thanks so much for the patch. Just curious if you've also submitted
> this upstream
The problem goes away when I remove third party repos from the list.
--
9.10 upgrade fails in setting new software channels for ppc
https://bugs.launchpad.net/bugs/404694
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs ma
The blue-backgrounds doesn't seem to be ppc dependent (nor ubuntu
dependent for that matter). I just saw the exact issue when debugging
mesa swrast on an linux/intel client and a darwin/ppc x11 server.
--
r300 on "PowerBook G4" mac: only swrast after booting and backgrounds render
blue instead
My guess is that this is a hardware bug... unless someone else can
reproduce it and knows a workaround, I suggest we close the bug.
--
2.6.28-11 Oops - resume from suspend, blank monitor
https://bugs.launchpad.net/bugs/367134
You received this bug notification because you are a member of Ubuntu
B
The powerpc-next tree has had this fix in it for a couple months now:
http://git.kernel.org/?p=linux/kernel/git/benh/powerpc.git;a=commit;h=baf75b0a42a1b3f6fca80f8949b6141eaff61b0d
--
[PATCH] karmic kernel powerpc, section mismatch warning
https://bugs.launchpad.net/bugs/371134
You received this
Public bug reported:
Binary package hint: gnome-power-manager
gnome-power-manager reports that my PowerMac G4 is connected to AC when
in fact it is on battery. This is a regresison from Jaunty which
correctly reported its status and handled change to a low-power state.
jer...@aeris:~$ cat /proc
powersaved works as a workaround for dimming the screen, etc ... but it
would be nice if gnome-power-manager could be updated to correctly show
the status.
--
[karmic regression] gnome-power-manager does not recognize that powermac g4 is
on battery
https://bugs.launchpad.net/bugs/414357
You rece
Public bug reported:
1) Run "update-manager -d"
2) Click "Upgrade" next to "9.10 is available"
3) Click "Upgrade to confirm"
4) Watch as the upgrade process fails in step 2: "Setting new software channels"
The following appears in a dialog box about the failure:
W:Failed to fetch http://ports.ub
Yes, those the two are likely dupes.
--
r300 on "PowerBook G4" mac: only swrast after booting and backgrounds render
blue instead of black
https://bugs.launchpad.net/bugs/370200
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu
Although there is still a mesa bug here in that swrast is rendering blue
backgrounds.
--
r300 on "PowerBook G4" mac: only swrast after booting and backgrounds render
blue instead of black
https://bugs.launchpad.net/bugs/370200
You received this bug notification because you are a member of Ubuntu
This has been upstream since November. When is it going to land in an
updated Ubuntu kernel?
--
b43 panic
https://bugs.launchpad.net/bugs/430225
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@li
** Summary changed:
- [karmic regression] gnome-power-manager does not recognize that powermac g4
is on battery
+ [karmic regression] APM: gnome-power-manager does not recognize state of
APM-only (non-ACPI) systems
--
[karmic regression] APM: gnome-power-manager does not recognize state of
AP
BTW, the XFCE Power Manager works as expected and properly detects the
state.
--
[karmic regression] APM: gnome-power-manager does not recognize state of
APM-only (non-ACPI) systems
https://bugs.launchpad.net/bugs/414357
You received this bug notification because you are a member of Ubuntu
Bugs,
Public bug reported:
Binary package hint: kernel-image-2.6.31-8-powerpc-di
With the Karmic kernel, the system panics on shutdown. The stack trace
indicates it is failing in the broadcom wireless driver (b43). This
problem happens with the built Karmic kernels (all 2.6.31 builds I've
tried) as w
This happens just by disabling wireless once it's active, so it's easier
to verify. Here's the log:
[ 46.732182] eth0: no IPv6 routers present
[ 49.568008] ondemand governor failed, too long transition latency of HW,
fallback to performance governor
[ 86.389403] wlan0: authenticate with AP
http://git.kernel.org/?p=linux/kernel/git/stable/linux-2.6.31.y.git;a=commit;h=d50bae33d1358b909ade05ae121d83d3a60ab63f
--
b43 panic
https://bugs.launchpad.net/bugs/430225
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs m
https://bugs.freedesktop.org/show_bug.cgi?id=27502
In 2.6.32, this can be addressed by editing /etc/modprobe.d/radeon-
kms.conf and setting modeset=0 instead of modeset=1
** Bug watch added: freedesktop.org Bugzilla #27502
http://bugs.freedesktop.org/show_bug.cgi?id=27502
--
r300 on "PowerBo
Or even better, you can stop building radeonfb into the kernel, so the
KMS radeon driver will provide the FB and HW rendering
--
r300 on "PowerBook G4" mac: only swrast after booting and backgrounds render
blue instead of black
https://bugs.launchpad.net/bugs/370200
You received this bug notific
Public bug reported:
Binary package hint: thunderbird
I have an IMAP server with a TLS cert signed by cacert.org, but
thunderbird does not know about this CA by default, so it comes up with
a dialog box asking me to add a security exception. I check the
checkbox "Permanently store this exception
This issue is still occuring with the latest ubuntu kernel:
Linux aerith 2.6.32-19-powerpc #28-Ubuntu Thu Apr 1 14:38:11 UTC 2010 ppc
GNU/Linux
r...@aerith:~# dmesg | grep radeon
[0.084204] radeonfb :00:10.0: enabling device (0006 -> 0007)
[0.471816] radeonfb :00:10.0: Invalid ROM
Public bug reported:
Binary package hint: avahi-daemon
I just updated from 9.10 to 10.04 beta. Upon restarting, avahi-daemon
has been a huge resource hog:
606 avahi 20 0 4808 2316 1432 R 83.8 0.2 10:02.08 avahi-
daemon
I am on a rather rich bonjour network. uptime is around 30 minu
I ran the command, but it doesn't look like anything was attached:
apport-collect -p linux 436084
Logging into Launchpad... You have to allow "Change anything" privileges.
Downloading bug information...
The authorization page:
(https://edge.launchpad.net/+authorize-token?oauth_token=DchHszwFLG
This is working after a recent update.
** Changed in: linux (Ubuntu)
Status: Incomplete => Fix Released
--
karmic: networking does not start automatically
https://bugs.launchpad.net/bugs/436084
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
ping. This is a fairly annoying regression with Karmic/Gnome
--
[karmic regression] APM: gnome-power-manager does not recognize state of
APM-only (non-ACPI) systems
https://bugs.launchpad.net/bugs/414357
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscr
Here is the patch from the upstream bug report which I have verified to
correct the problem.
** Attachment added: "wireless.patch"
http://launchpadlibrarian.net/0190/wireless.patch
--
b43 panic
https://bugs.launchpad.net/bugs/430225
You received this bug notification because you are a mem
I hit this a few months back, but I haven't seen the problem since...
--
gnome-power-manager crashed with SIGSEGV in __libc_start_main()
https://bugs.launchpad.net/bugs/376205
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bu
** Changed in: linux (Ubuntu)
Status: New => Invalid
--
2.6.28-11 Oops - resume from suspend, blank monitor
https://bugs.launchpad.net/bugs/367134
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu
I was told that this isn't an issue in gnome-power-manager but probably
a misconfiguration in HAL, since gnome-power-manager is abstracted above
the APM/ACPI barrier... I have not confirmed this, however.
--
[karmic regression] APM: gnome-power-manager does not recognize state of
APM-only (non-A
Here is the final released fix:
diff --git a/drivers/net/wireless/b43/rfkill.c
b/drivers/net/wireless/b43/rfkill.c
index 31e5599..dcde92d 100644
--- a/drivers/net/wireless/b43/rfkill.c
+++ b/drivers/net/wireless/b43/rfkill.c
@@ -33,7 +33,8 @@ bool b43_is_hw_radio_enabled(struct b43_wldev *dev)
It doesn't look like I have access to linux-crashdump. It's only built
for i386 and x86_64 ... should I build it manually for ppc, or is there
a reason it's not built for ppc?
http://packages.ubuntu.com/karmic/linux-crashdump
--
b43 panic
https://bugs.launchpad.net/bugs/430225
You received this
For that matter, it doesn't look like the linux-crashdump package even
installs anything:
http://packages.ubuntu.com/karmic/amd64/linux-crashdump/filelist
--
b43 panic
https://bugs.launchpad.net/bugs/430225
You received this bug notification because you are a member of Ubuntu
Bugs, which is subs
Public bug reported:
I recently updated ~500 packages in karmic (I hadn't updated in about a
week or so). Something in this update has messed with networking.
network-manager reports that it is running.
ifconfig shows my devices are up, but they are not configured.
I can do 'sudo dhclient eth0'
** Attachment added: "linux-image-2.6.31-6-powerpc.184386.crash"
http://launchpadlibrarian.net/32393283/linux-image-2.6.31-6-powerpc.184386.crash
--
b43 panic
https://bugs.launchpad.net/bugs/430225
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribe
I can't run apport-retrace because of bug #436157.
The problem occurs when doing 'ifconfig wlan0 down' ... but I can work
around it by just 'rmmod b43' instead.
** Attachment added: "linux-image-2.6.31-10-powerpc.178098.crash"
http://launchpadlibrarian.net/32401792/linux-image-2.6.31-10-power
I won't have access to the machine again until 10/5, so I'll report
back when I can...
On Sep 25, 2009, at 12:05, Leann Ogasawara wrote:
> Hi Jeremy,
>
> After you have to manually bring up networking, can you run the
> following command which will gather and attach additional debug
> informati
Architecture: powerpc
DistroRelease: Ubuntu 9.10
Package: gnome-power-manager 2.28.1-0ubuntu1
PackageArchitecture: powerpc
ProcEnviron:
SHELL=/bin/bash
LANG=en_US.UTF-8
ProcVersionSignature: Ubuntu 2.6.31-14.48-powerpc
Uname: Linux 2.6.31-14-powerpc ppc
UserGroups:
--
[karmic regression] APM: g
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/37894073/Dependencies.txt
--
[karmic regression] APM: gnome-power-manager does not recognize state of
APM-only (non-ACPI) systems
https://bugs.launchpad.net/bugs/414357
You received this bug notification because you are a
** Attachment added: "DevkitPower.txt"
http://launchpadlibrarian.net/37894077/DevkitPower.txt
--
[karmic regression] APM: gnome-power-manager does not recognize state of
APM-only (non-ACPI) systems
https://bugs.launchpad.net/bugs/414357
You received this bug notification because you are a me
** Attachment added: "GConfNonDefault.txt"
http://launchpadlibrarian.net/37894086/GConfNonDefault.txt
--
[karmic regression] APM: gnome-power-manager does not recognize state of
APM-only (non-ACPI) systems
https://bugs.launchpad.net/bugs/414357
You received this bug notification because you
** Attachment added: "XsessionErrors.txt"
http://launchpadlibrarian.net/37894087/XsessionErrors.txt
--
[karmic regression] APM: gnome-power-manager does not recognize state of
APM-only (non-ACPI) systems
https://bugs.launchpad.net/bugs/414357
You received this bug notification because you ar
** Attachment added: "gnome-power-bugreport.txt"
http://launchpadlibrarian.net/37894088/gnome-power-bugreport.txt
** Changed in: gnome-power-manager (Ubuntu)
Status: Incomplete => New
** Tags added: apport-collected
--
[karmic regression] APM: gnome-power-manager does not recognize s
Distro version: squeeze/sid
Kernel version: 2.6.31-14-powerpc
g-p-m version:2.28.1
HAL version: 0.5.13
System manufacturer: missing
System version: missing
System product: missing
AC adapter present: yes
Battery present: yes
Laptop panel present: yes
As mentioned, xfce notices the state correctly, so I believe it's a
problem with gpm or something that gpm depends on that xfce's power
manager doesn't
--
[karmic regression] APM: gnome-power-manager does not recognize state of
APM-only (non-ACPI) systems
https://bugs.launchpad.net/bugs/414357
Y
This seems more like a server issue. I think it could easily be possible for
the server to guarantee that XIDs are not reused within a certain time period
since it issued a DestroyNotify. That won't guarantee that clients are happy,
but it can certainly help. We just need to store a timestamp
Is this still an issue?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/255826
Title:
scrolling in Firefox causes Xorg-process to lag (S3 Savage driver)
To manage notifications about this bug go to:
This is coming from R128InitDDARegisters during init in r128_driver.c:
Roff = XclksPerTransferPrecise * (DisplayFifoDepth - 4);
Ron = (4 * info->ram->MB
+ 3 * MAX(info->ram->Trcd - 2, 0)
+ 2 * info->ram->Trp
+ info->ram->Twr
+ info->r
Can you provide a server log for a working state and a broken state for
comparison? What version change introduces the problem? A new radeon driver
or a new server?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launc
Is this still an issue. The ubuntu bug was closed due to lack of response, so
I'm wondering if it has been fixed already.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/41148
Title:
buggy d
Do you still have hardware to test this? Is it still an issue?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/35794
Title:
TV out is broken with VT1621 chip
To manage notifications about th
AFAICT, nobody has followed my direction above and brought this up for
discussion on xorg-devel. Without that, it's not likely to be fixed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/883319
Title:
AFAICT, nobody has followed my direction above and brought this up for
discussion on xorg-devel. Without that, it's not likely to be fixed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/881046
Title:
Which exactly matches my comment above about this being the likely
culprit:
commit 9faf6136ff4647452580b019f4b16f8c5082e589
Author: Matthew Garrett
Date: Sat Sep 20 13:19:46 2014 +0200
ACPI / SBS: Disable smart battery manager on Apple
Touching the smart battery manager at all on Apple
Still reproduces on 2016.04.1's kernel.
I narrowed it down to the sbs kernel module. If I move the sbs module
out of /lib/modules (or just build my kernel without it), the issue does
not reproduce.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribe
I just sent a ping email to Matthew about this. I emailed him last year
without response.
Can we just revert that change in the Ubuntu kernel to get things back
to a usable state?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https
The last hunk looks quite wrong to me. The manager_present logic looks
inverted.
- result = acpi_manager_get_info(sbs);
- if (!result) {
- sbs->manager_present = 1;
- for (id = 0; id < MAX_SBS_BAT; ++id)
- if ((sbs->batteries_supported
Actually, the obvious logic bug was fixed by 61f8ff69 (which is already
in 4.4), but the other issue still remains.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1489622
Title:
15.10 20150826 snapsh
Nope. But I did do a manual change to remove the Apple quirk (the
revert isn't clean due to additional changes, but it's simple enough to
remove the few lines that setup the quirk). I was running fine for a
while, but eventually started seeing the same behavior
(/sys/firmware/acpi/interrupts/gpe1
Will be fixed in 1.12.1 RC2
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/968726
Title:
Passive touch grab ungrabbing is unimplemented
To manage notifications about this bug go to:
https://bugs.lau
Please send your patch to xorg-devel for discussion.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/883319
Title:
xrandr --scale restricts area in which mouse moves
To manage notifications about thi
Chris, could you put together the combined patch you mentioned and send
it to xorg-devel for review? Thanks.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/883319
Title:
xrandr --scale restricts are
@colin-law no, this bug does not apply to Unity. This bug was filed
years before Unity even existed. If it is "fixed" by changing to Unity,
that's great for Unity users, but simply sweeping an issue under the rug
because you changed window systems doesn't change the fact the the bug
continues to
Public bug reported:
I just put the 20150826 15.10 snapshot onto my MacBookPro3,1. I
blacklisted nouveau due to
https://bugs.freedesktop.org/show_bug.cgi?id=91779 and updated systemd
to start in text mode instead of launching X11.
After booting into this configuration and letting the system idle
I wonder if it is ACPI related:
$ uptime && cat /sys/firmware/acpi/interrupts/gpe17
16:22:48 up 0 min, 1 user, load average: 2.26, 0.74, 0.26
376509 enabled
that's a lot of interrupts for a system that has been up less than a
minute.
--
You received this bug notification because you are
Although even with gpe17, I'm still seeing the load average around 1.25
with perf reporting a lot of time in acpi_processor_ffh_cstate_enter
- 43.32%43.32% swapper [kernel.kallsyms] [k]
acpi_processor_ffh_cstate_enter
--
You received this bug notification because you ar
** Attachment added: "dmidecode.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1489622/+attachment/4453568/+files/dmidecode.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1489622
Tit
** Attachment added: "acpidump.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1489622/+attachment/4453569/+files/acpidump.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1489622
Title
On one particular boot with the external power connected, there were
only 1176 interrupts for this event a few minutes after boot. It was
stable at 1176. Upon disconnecting external power, it started its rapid
cycling. Reconnecting the external power source did not solve the
problem.
On another
Upon trying it again, I'm actually seeing the load drop down in the
"steady gpe17 after boot" case. I just didn't wait long enough for the
boot load spike to get out of the average. Please disregard that second
half of my previous comment.
Here are some more experiments:
With processor.max_csta
1 - 100 of 216 matches
Mail list logo
