Package uploaded to REVU
--
[needs-packaging] tv_grab_dvb
https://bugs.launchpad.net/bugs/116147
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
Package uploaded to REVU
--
[needs-packaging] ocropus
https://bugs.launchpad.net/bugs/105411
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
** Changed in: ubuntu
Assignee: Kevin DuBois (kdub) = (unassigned)
--
[needs-packaging] ocropus
https://bugs.launchpad.net/bugs/105411
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs
** Changed in: ubuntu
Assignee: (unassigned) = Kevin DuBois (kdub)
--
[needs-packaging] tv_grab_dvb
https://bugs.launchpad.net/bugs/116147
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu
** Changed in: ubuntu
Assignee: MOTU (motu) = Kevin DuBois (kdub)
--
[needs-packaging] ocropus
https://bugs.launchpad.net/bugs/105411
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs
** Changed in: ubuntu
Assignee: (unassigned) = Kevin DuBois (kdub)
--
[needs-packaging] ocropus
https://bugs.launchpad.net/bugs/105411
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs
This problem should be solved in hardy. To my knowledge. there was a
problem that has been fixed with XV that caused the blacklisting. Refer
to http://ubuntuforums.org/showthread.php?p=3451249 for workarounds.
--
compiz doesn't work with Intel GMA X3100
https://bugs.launchpad.net/bugs/194086
The kernel interface must be recompiled for each new kernel
installation. I'm sure that this is a common problem, but I am unsure of
the level to which Ubuntu plans on supporting this.
--
ubuntu Hardy Heron update on mar 10 evening. wiped out nvidia
https://bugs.launchpad.net/bugs/200847
You
xorg.conf is a critical system file for most users, IMO. An unprivileged
user should not have write access. It may be wise to prompt for the root
password, instead of simply exiting with an error.
--
nvidia-settings doesn't have permissions to write xorg.conf
I was merely investigating the possible use of a better driver for
ubuntu. i am in no way asking for support. the current driver is
blacklisted
--
Compiz Fusion Unusable w/ Intel GMA965
https://bugs.launchpad.net/bugs/183675
You received this bug notification because you are a member of Ubuntu
** Changed in: ubuntu
Assignee: MOTU (motu) = Kevin DuBois (kdub)
--
[needs-packaging] Entropy
https://bugs.launchpad.net/bugs/95690
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs
DuBois (kdub432)
Status: New
** Changed in: compiz (Ubuntu)
Assignee: (unassigned) = Kevin DuBois (kdub432)
--
Compiz Fusion Unusable w/ Intel GMA965
https://bugs.launchpad.net/bugs/183675
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug
Public bug reported:
Binary package hint: grub
I have a custom LFS based system sitting on another partition in my
laptop. whenever i upgrade grub, the entry in menu.lst for my custom
distro disappears. Perhaps, the upgrade process should assume that any
modifications are there on purpose
**
There appears to be a discrepancy between the default hardy drivers for
the Intel GMA965 chipset and the intellinuxgraphics.org developer's
drivers i was running on gutsy that causes loose binding to cause
nothing to update itself. I will try out the drivers from the developers
to see if this
The specific hard drive setup is
sda1 --- / (for ubuntu), contains the /boot directory that the MBR looks at
first
sda2 --- swap
sda3 --- /home
sda4 --- / (for my LFS)
--
Grub Upgrade procedure Overwrites Menu.lst
https://bugs.launchpad.net/bugs/183693
You received this bug notification
This is indeed the problem. Thanks, it looks like we can close this bug
** Changed in: grub (Ubuntu)
Status: Incomplete = Invalid
--
Grub Upgrade procedure Overwrites Menu.lst
https://bugs.launchpad.net/bugs/183693
You received this bug notification because you are a member of Ubuntu
More information is needed. How are you trying to install open office?
Attach a screenshot of 'ugly virtual terminals'. Is gnome-settings-
daemon running?
--
Not being able to install openoffice in Hardy and virtual terminals look ugly
https://bugs.launchpad.net/bugs/182479
You received this bug
I too have noticed evince hogging ungodly amounts of memory for small
files. This should probably be investigated, as having a pdf open on a
slower system of mine all but stops things from happening...
** Changed in: evince (Ubuntu)
Status: New = Confirmed
--
evince consuming a lot of
are you running a 'stable' version of compiz?
--
Compiz crashes on startup, but then reloads and works automatically.
https://bugs.launchpad.net/bugs/182099
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing
more information is needed. network configuration is complex. what
specific problem are you having? can you attach logs to help us figure
out if this is really a bug?
--
ubuntu network connection problem
https://bugs.launchpad.net/bugs/181463
You received this bug notification because you are a
perhaps it would be better to have the package install symlinks to
directories already in $PATH or to modify the build the package so that
it is installed to somewhere in $PATH
--
Add rubygems bin to PATH
https://bugs.launchpad.net/bugs/145267
You received this bug notification because you are a
** Changed in: ubuntu
Status: New = Fix Released
--
wlan broken after cups update
https://bugs.launchpad.net/bugs/181565
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:
In the Power Management configuration program, the display brightness on
On AC Power is set relative to 0% whereas under On battery power it
is set relative to 100%. This is a minor annoyance that is easily
changeable, I would imagine.
** Affects: ubuntu
Importance:
Do you have the proper graphics card drivers installed? if i'm not
mistaken this is a opengl accelerated function of rhythmbox. I could not
reproduce using a properly installed intel graphics card
** Changed in: rhythmbox (Ubuntu)
Assignee: (unassigned) = Kevin DuBois (kdub432)
Status
Manually run the command dpkg --configure -a to fix this. You have
broken dependancies
** Changed in: synaptic (Ubuntu)
Status: New = Invalid
--
error in synaptic
https://bugs.launchpad.net/bugs/158898
You received this bug notification because you are a member of Ubuntu
Bugs, which is
*** This bug is a duplicate of bug 122560 ***
https://bugs.launchpad.net/bugs/122560
I had resolved this issue, had sound working great with the modules I compiled
from alsa mercurial and 8/17/2007.
However, I'm a developer and wanted to start help the compiz fusion guys, so I
compiled a
POSSIBLE BIOS ISSUE ROOT
Ubuntu Gutsy Tribe 4. Lenovo X61 Tablet. Intel AD 1984 Audio Chipset.
Drivers Installed: ALSA CVS/Mercurial 22 Aug 2007.
After banging my head against the wall, for 6 hours straight with this
issue, I reset my BIOS to factory defaults. This seemed to enable all
sounds,
Public bug reported:
In Ubuntu Gutsy, Tribe 4. Intel GMA 965 video drivers in x3100 chipset on
Lenovo x61 tablet. latest gutsy version of drivers. Firstly, kudos for getting
the intel graphics cards to work out of the box. However, with my computer,
occassionally at boot, the auto-adjust
** Attachment added: discover --disable
http://launchpadlibrarian.net/9000367/discover.txt
--
Intel GMA965 Brightness Adjustments
https://bugs.launchpad.net/bugs/134429
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
uname -r
2.6.22-9-generic
--
Intel GMA965 Brightness Adjustments
https://bugs.launchpad.net/bugs/134429
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
** Attachment added: lspci -n
http://launchpadlibrarian.net/9000355/lspci.txt
--
Intel GMA965 Brightness Adjustments
https://bugs.launchpad.net/bugs/134429
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs
xresprobe:
id:
res: 1400x1050
freq:
disptype: lcd/lvds
--
Intel GMA965 Brightness Adjustments
https://bugs.launchpad.net/bugs/134429
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
** Attachment added: old xorg log (from previous session)
http://launchpadlibrarian.net/9000397/Xorg.0.log.old
--
Intel GMA965 Brightness Adjustments
https://bugs.launchpad.net/bugs/134429
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact
** Attachment added: xorg log
http://launchpadlibrarian.net/9000389/Xorg.0.log
--
Intel GMA965 Brightness Adjustments
https://bugs.launchpad.net/bugs/134429
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs
Compiling latest alsa drivers from mercurial and ensuring bios is set to
default works for my talbet x61. An odd bug this driver has though, is
whenever I switch the computer to tablet mode, the sound stops working.
Switching back to notebook mode and unloading/reloading the driver
works.
--
no
sputniksh...@gmail.com
wrote:
Hi!
I am missing OCRopus in Ubuntu Intrepid. How is it going on?
--
[needs-packaging] ocropus
https://bugs.launchpad.net/bugs/105411
You received this bug notification because you are a bug assignee.
--
Kevin DuBois
kdub...@gmail.com
PGP fingerprint
80CF 7C1D 0A1C
Hi dadrivr,
There are still a few things you can do to help us debug this issue.
1) Did this device ever work? perhaps with an older version of Ubuntu, or an
older kernel? If so, please describe.
2) Please try a mainline kernel and let us know how it goes. Please try the
2.6.30 mainline
I have this problem too. Webcam works fine with other programs like VLC
or Skype.
** Changed in: cheese (Ubuntu)
Status: Invalid = Incomplete
--
SIGSEGV in cheese_camera_device_get_best_format at cheese-camera-device.c:592
https://bugs.launchpad.net/bugs/598819
You received this bug
duplicate of lp:1189938
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1190894
Title:
FTBFS: buffer.cpp:93: undefined reference to `eglCreateImageKHR'
To manage notifications about this bug go to:
the issue was that the hwcomposer was relying on HWC_GEOMETRY_CHANGED
flag to do some initialization of its internal data structures
(including some pthread mutexes). Mir was not setting this flag leaving
those mutexes uninitialized. When hwc tried to lock the uninitialized
mutexes, we would
for the reports about 'my nexus 7 works'
In mir, we first try to load the HWC display mechanism, and then, if we
can't load HWC, we load an alternative display mechanism (FB)
We saw that the HWC was segfaulting, so we removed hwcomposer.tegra3.so from
the build. This forced FB composition.
) = Kevin DuBois (kdub)
** Changed in: mir
Status: Triaged = In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1238695
Title:
unity8 display flickers and stops responding on Nexus 7
a little bit more background... mir is currently 'detached' from what is
on the device because we maintain our own headers in the mir tree
(gralloc.h, fb.h and hwcomposer.h)
mir should depend on the headers in this package so that if they change,
mir's build would break instead of failing later
fix coming...
https://code.launchpad.net/~kdub/mir/fix-1215979/+merge/187346
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1215979
Title:
visual glitches and flashing on Nexus 4
To manage
** Branch linked: lp:~kdub/mir/fix-1215979
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1215979
Title:
visual glitches and flashing on Nexus 4
To manage notifications about this bug go to:
this is more of a blueprint than a bug. One is already in place for
tracking progress.
https://blueprints.launchpad.net/ubuntu/+spec/client-1307-mir-nexus10
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
my suspicions are correct... it appears that, with the tegra3 driver,
the use of a texture with glReadPixels is simply broken. If you use a
renderbuffer with glReadPixels, screenshotting is okay. I have something
working on my device here, have to figure out the best way to land
--
You received
** Changed in: mir
Status: In Progress = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1231917
Title:
Mir servers crash with SIGSEGV in libhybris-common.so.1 on Nexus7 when
old nexus 7 (nvidia hardware) or new nexus 7 (qcom hardware)?
it might be that the hwc isn't working for the nexus 7. You can try to
mv /system/lib/hw/hwcomposer.* out of that directory, which will force
mir into a backup composition mode.
--
You received this bug notification because you are a
any complaints in logcat or dmesg?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1235190
Title:
[mako] Unity8 on Mir got slow
To manage notifications about this bug go to:
when I had this build on
root@ubuntu-phablet:/# system-image-cli -i
current build number: 82
device name: mako
channel: devel-proposed
last update: 2013-10-05 00:46:03
version version: 82
version ubuntu: 20131004.1
version device: 20131003.2
i couldn't get mir to start with older revisions of mir
this appears to prevent the error from happening:
# touch /userdata/.writable_image
# reboot
probably some firmware, device file, or driver that is needed has been
made inaccessible in the image
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
*** This bug is a duplicate of bug 1188504 ***
https://bugs.launchpad.net/bugs/1188504
apologies for the confusion, i could not reproduce the fix i proposed in
the earlier comment. I probably was just not controlling for the blank
state carefully enough
--
You received this bug notification
so cutting unity8 out of the loop altogether by using
mir_demo_standalone_render_to_fb, here's what I see
(from powerd-cli listen)
Received DisplayPowerStateChange: state=1 flags=0x04
root@ubuntu-phablet:/root# ./mir_demo_standalone_render_to_fb
renders ok for a while until the screen
powerd calls unity8 (via dbus) which calls mir to turn off the display.
If i cut unity8 out of the loop, then powerd and mir disagree on the fb
state more often because calls to change the state (originating from
powerd) don't update mir.
kgunn probably didn't see any problems (and users
I'm a bit concerned that the clocks of the gpu or the memory bus are
going low inappropriately. Still haven't been able to reproduce, but
that'll be the first thing I check
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
upgrading my previous statement from 'concerned' to 'strongly suspect'
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1235190
Title:
[mako] Unity8 on Mir got slow
To manage notifications about
I see wild (and explainable) mood swings in mir performance when we have
our clocks kicked out from under us. When this problem occurs, try
turning clocks up to 11:
echo performance /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
This at least turns the cpu clocks to high and probably
my current working theory is that powerd (when it talked to
surfaceflinger) would just hang when we running mir, because we would
forcibly stop the surfaceflinger. Now that powerd talks to unity, which
talks to mir, so it is starting to make actual power requests, including
scaling back the
its not the cpu itself, when you force the cpu to performance, you also force
the system bus to stay on.
So you can have a low percentage of ram, low cpu usage, and still be going slow
because the pixels aren't making it back and forth from the gpu to the ram to
the screen fast enough. the
and just to be clear (seems to have been some confusion about this)
turning the cpu to 'performance' is not a landable solution because of
battery life. It is a good test to see if the problem is the clocks are
turned to low (a system power management problem), or mir itself is
getting stucks
trying to keep this bug focused :)
lool's comment #13, noting a memory leak in upstart, would only affect
longer term mir usage... since we see the bug very quickly, this is
probably not what we're seeing
comments 14 15 17 18 20 21 22 23 24 25 26 all have to do with
ogra is spot on in
https://bugs.launchpad.net/ubuntu/+source/mir/+bug/1235190/comments/22
about having to collect more quantifiable data about what is reported as
'slowness'
we have some profile data collected from rsalveti that indicates the cpu
is more than 50% idle when this is happening:
between image 62/65, we added more waits that ensure the gpu is done
rendering (this was a bug in mir that caused flickering on screen).
However, this did introduce more waiting during the rendering pass, and
I think it pushed us from 16ms frames (60fps) to a bit over (perhaps
19-20ms). This
yes, linked branch improves performance by shifting where we wait for
render completion out of the unity8 render thread and into mir's
composition pass. This better pipelines the composition pass with the
render pass, and gets performance to vsync rate. Performance improvement
was verified by
** Changed in: mir
Status: Confirmed = In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1235190
Title:
[mako] Scrolling and animations are very slow with Mir
To manage
With the way things are now, I'm pretty sure if we simply retried in mir
after experiencing an error, we would hang the driver. Once we get these
throws, the driver has essentially been put into an unrecoverable state.
It seems Seth's investigation aligned with my intuition about the
driver.
--
** Branch linked: lp:~kdub/mir/fix-1238695
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1238695
Title:
unity8 display flickers and stops responding on Nexus 7 (grouper)
To manage notifications
okay, given the chance of us poking nvidia to fix this old/rotting
driver, i'm working on accomodating the brokenness by acquiring
snapshots via renderbuffers instead of textures.
I noticed surfaceflinger notes in some of the comments for code around
the time of this driver that some 'old
** Branch linked: lp:~sforshee/powerd/fix-display-timing
** Changed in: mir
Milestone: 0.1.4 = None
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1258655
Title:
Abort when blanking/unblanking
my testing reveals that the branch lp:~kdub/mir/fix-1238695 fixes the
problem on the nexus 7... but cause problems on the nexus 4. Need to
find a way that makes everyone happy.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Working on proposing lp:~kdub/mir/snapshot-error-checking to fail more
gracefully.
This should provide relief from taking Unity8 down on this device,
although it will not provide application thumbnails yet (so the bug
probably should remain open)
** Branch linked:
If I understand, we have a fix, so lets move with that.
We can always improve mir to be more robust, but the heart of this
problem was that mir/unity-mir was not given the guarantee that it needs
(the system on enough to start operations).
--
You received this bug notification because you are a
I abandoned my efforts in lp:~kdub/mir/snapshot-error-checking, as it
turned out not to be that robust (errors were still being generated).
Rather, I kept investigating, and found that the same EGLImages bound in
the rendering thread and the snapshot thread on this driver (but not any
of the
** Tags removed: regression
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1258655
Title:
Abort when blanking/unblanking screen
To manage notifications about this bug go to:
** Changed in: mir (Ubuntu)
Status: Confirmed = In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1258655
Title:
Abort when blanking/unblanking screen
To manage notifications about
From mir's perspective, i see start, stop, start, stop, ..., start,
start being called on the compositor. The double start, start causes
an error in the compositor. (specifically, an egl context is current in
two threads, causing an error BAD_ACCESS in the second thread).
powerd-cli listen just
Gerry collected this helpful dbus log
http://pastebin.ubuntu.com/6567567/ (also attached) that shows we get an
on, on message from dbus.
the error shown:
terminate called after throwing an instance of
I also did a mir-only test to make sure mir can perform a display on/off
in quick succession in a loop (which it can), as well as on/display some
frames/off in a loop (which it also can). So it doesn't look like the
drivers are breaking on us, just something between mir/unity-
mir/unity8/powerd is
mir needs to be robustified against the double on and double off
calls. Even when I account for this though, the system will still run
into problems.
I still have reason to suspect that when the dbus message to unity mir
to turn the display on is received, the system is still in the suspend
regardless of whether we throw or not on unblank, the problem at the
root of this bug is that mir and powerd are not synced up about the
power state of the system (clocks, suspend, fb available, etc). This
problem sometimes manifests in failure in the blank/unblank request,
sometimes a hang
i've identified some problems in powerd that cause double requests to be
called. currently working to eliminate those in that code base.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1258655
Title:
** Also affects: powerd
Importance: Undecided
Status: New
** Changed in: powerd
Status: New = In Progress
** Changed in: powerd
Assignee: (unassigned) = Kevin DuBois (kdub)
** Changed in: mir (Ubuntu)
Status: Triaged = Invalid
--
You received this bug notification
I've been able to avert the problem on mako by patching powerd.
Currently cooking up a patch to propose to powerd that works in the
generic case. The root of the problem was that devices with early
suspend were turning mir on and off when they did not guarantee the
framebuffer was in a usable
this problem would only affect devices that use 'earlysuspend'. Other
devices do not have a second thread messing with the display state
tracking, only earlysuspend devices would spawn the thread that was
causing problems.
** Changed in: mir
Milestone: 0.1.3 = None
--
You received this bug
** Branch linked: lp:~kdub/powerd/fix-1258655
** Changed in: mir
Status: In Progress = Invalid
** Changed in: powerd
Importance: Undecided = Critical
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: mir
Status: Triaged = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1203268
Title:
Mir fails to start on Nexus 10 - std::exception::what: Could not
unblank
This would be best to go in before we switch the device images to
android-4.4 based, just to make sure mir is in sync with the hal headers
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1224635
Title:
I'm investigating from the mir side, this might be something in the
power system too. The branch Daniel mentioned may help but the branch
was only meant to address a TODO. I'm working to confirm that it helps
or not
--
You received this bug notification because you are a member of Ubuntu
Bugs,
The maguro driver does not provide an enableScreen() function hook at
all, so mir skips calling into the driver during a power request. The
lp:~kdub/mir/fb-device-enablescreen will not fix the problem in this
bug. The power button was working before, so I'm curious how... will
keep digging
--
https://android.googlesource.com/platform/hardware/ti/omap4xxx/+/android-cts-4.4_r1/hwc/hwc.c
line 1961 might have a clue... seems both levers mir can push are just null
hooks
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Its strange that tapping the screen after the power button will turn it
on, input logic is far away from mir's android display system. Perhaps a
compositor update isn't being triggered, or the interplay between unity-
mir and powerd has changed subtly.
--
You received this bug notification
Public bug reported:
There appears to be some mismatch between the header files in google's
source tree and the header files in our package that cause some
breakage, particularly around some macros.
I attached a file of checksum comparison between the headers in this
package vs
not sure why i can't change importance, but it should be 'wishlist'
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1224635
Title:
android-platform-headers does not inclue hwcomper headers
To manage
Public bug reported:
hardware/hwcomposer.h and hardware/hwcomposer_defs.h should be included
in the headers along with gralloc and the rest of the platform headers
** Affects: libhybris (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you
we should move include/shared/mir_toolkit/mesa/native_display.h
somewhere upstream, to mesa.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1192908
Title:
Mir/Mesa packaging have a dependency cycle
** Branch linked: lp:~unity-team/unity/fix-924636
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/924636
Title:
Number shortcut overlay won't show if mouse hovers launcher bar area
To manage
** Changed in: unity
Status: In Progress = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/924636
Title:
Number shortcut overlay won't show if mouse hovers launcher bar area
To
** Changed in: unity
Assignee: (unassigned) = Kevin DuBois (kdub)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/924636
Title:
Number shortcut overlay won't show if mouse hovers launcher bar
** Changed in: unity
Status: Triaged = In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/924636
Title:
Number shortcut overlay won't show if mouse hovers launcher bar area
To manage
1 - 100 of 349 matches
Mail list logo
