** Also affects: metacity (Ubuntu)
Importance: Undecided
Status: New
** Also affects: metacity (Ubuntu Jaunty)
Importance: Undecided
Status: New
--
Undecorating maximised windows sometimes leaves a blank space below the window
(Intrepid & Jaunty)
https://bugs.launchpad.net/b
Not a maximus bug
** Changed in: maximus
Status: New => Invalid
--
Undecorating maximised windows sometimes leaves a blank space below the window
(Intrepid & Jaunty)
https://bugs.launchpad.net/bugs/283447
You received this bug notification because you are a member of Ubuntu
Desktop Bugs,
Is there a recipe to reproduce this? I see this bug on synaptic
/startup/, but it fixes itself quickly as the window contents are
updated.
--
Undecorating maximised windows sometimes leaves a blank space below the window
(Intrepid & Jaunty)
https://bugs.launchpad.net/bugs/283447
You received th
metacity 2.26.0 in my PPA
** Changed in: metacity (Ubuntu)
Assignee: (unassigned) => Loïc Minier (lool)
** Changed in: metacity (Ubuntu Jaunty)
Importance: Undecided => Medium
** Changed in: metacity (Ubuntu Jaunty)
Status: New => Triaged
** Changed in: metacity (Ubun
Tested and fixes the bug in karmic.
--
Undecorating maximised windows sometimes leaves a blank space below the window
(Intrepid & Jaunty)
https://bugs.launchpad.net/bugs/283447
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to metacity in
Impact: display glitches or misrenderings while using apps under UNR.
Fix in development branch was to trigger a metacity resize of the window after
the maximize event.
Attaching the patch which was merged upstream.
Regression potential: can't really think of anything, perhaps more redraws?
** De
** Changed in: metacity (Ubuntu Jaunty)
Status: In Progress => Fix Committed
--
Undecorating maximised windows sometimes leaves a blank space below the window
(Intrepid & Jaunty)
https://bugs.launchpad.net/bugs/283447
You received this bug notification because you are a member of Ubuntu
D
http://translate.google.com/translate_t?hl=en&sl=en&tl=es#en|es|videos
disagrees with you; are there multiple possible versions?
** Package changed: netbook-launcher (Ubuntu) => xdg-user-dirs (Ubuntu)
** Changed in: xdg-user-dirs (Ubuntu)
Importance: Undecided => Medium
** Changed in: xdg-use
I'll leave this bug to the Spanish translators for Ubuntu; thanks for
your input!
** Changed in: xdg-user-dirs (Ubuntu)
Status: Incomplete => New
** Summary changed:
- Incorrect translation in spanish for Video folder
+ Incorrect translation in South-American Spanish for Video folder
**
Tested fine; the nautilus test case is much easier to verify, but I
verified both with synaptic and nautilus and windows are properly
maximized.
--
Undecorating maximised windows sometimes leaves a blank space below the window
(Intrepid & Jaunty)
https://bugs.launchpad.net/bugs/283447
You receiv
I see this too
** Changed in: gnome-power-manager (Ubuntu)
Importance: Undecided => Medium
** Changed in: gnome-power-manager (Ubuntu)
Status: New => Triaged
** Bug watch added: Linux Kernel Bug Tracker #12632
http://bugzilla.kernel.org/show_bug.cgi?id=12632
** Also affects: linux
** Attachment added: "gpm-low-capacity.png"
http://launchpadlibrarian.net/27139375/gpm-low-capacity.png
--
Broken and weird warning dialogs when booting with an empty battery
https://bugs.launchpad.net/bugs/380255
You received this bug notification because you are a member of Ubuntu
Desktop
Public bug reported:
Binary package hint: gnome-power-manager
Hi
I'm seeing bug #379599; when I bring my system back up with the second battery,
GPM shows a weird dialog (will attach). I don't think this dialog is warranted
at all, but if it is then the Cancel button should be removed.
Thanks
Here's another example which happens for everybody I think since /apps
/gnome-power-manager/notify/fully_charged is true by default
** Attachment added: "stupid-Power Manager.png"
http://launchpadlibrarian.net/27139458/stupid-Power%20Manager.png
** Changed in: gnome-power-manager (Ubuntu)
I guess we're not using the upstream projects to track bugs for for UNR
packages anymore, but only the Ubuntu source packages.
Since this bug doesn't need upstreaming anymore and I know for sure the
dialog in netbook-launcher does differ, I'm reopening it ;-)
** Changed in: netbook-launcher (Ub
This is fixed in jaunty
--
libgtk2.0-dev : dependency version for libcairo2-dev not specified (intrepid)
https://bugs.launchpad.net/bugs/382334
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gtk+2.0 in ubuntu.
--
desktop-bugs mailing l
This is fixed in jaunty
** Changed in: gtk+2.0 (Ubuntu)
Status: New => Fix Released
--
libgtk2.0-dev : dependency version for libcairo2-dev not specified (intrepid)
https://bugs.launchpad.net/bugs/382334
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, w
Public bug reported:
Binary package hint: gnome-panel
Hi
attaching screenshot
[ I have this bug since a long time on three different machines now, but I
wondered whether I had weird or even corrupted settings since I war running
development releases. I just got it again on this new install,
** Attachment added: "workspace-applet-bug.png"
http://launchpadlibrarian.net/27694916/workspace-applet-bug.png
--
workspace switcher applet doesn't fit to panel
https://bugs.launchpad.net/bugs/385220
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is
'd like to do a security review.
** Changed in: papyon (Ubuntu Karmic)
Assignee: (unassigned) => Loïc Minier (lool)
** Changed in: papyon (Ubuntu Karmic)
Status: New => Incomplete
--
Move Empathy Dependencies to Main and Update Desktop Seed
https://bugs.launchpad.net/bugs/38
@Ken: gupnp-igd needs a MIR wiki page
** Changed in: gupnp-igd (Ubuntu Karmic)
Status: New => Incomplete
--
Move Empathy Dependencies to Main and Update Desktop Seed
https://bugs.launchpad.net/bugs/388898
You received this bug notification because you are a member of Ubuntu
Desktop Bugs,
@Devid: I'd prefer if you would include it for now until the python
policy gets revised to match the unilateral changes on the pysupport
side.
@Laurent: but the package IS named python-papyon, right? it's uesful to
allow other packages to depend on a particular version of the package,
e.g. a pyth
papyon approved
** Changed in: papyon (Ubuntu Karmic)
Status: New => Fix Committed
--
Move Empathy Dependencies to Main and Update Desktop Seed
https://bugs.launchpad.net/bugs/388898
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to
** Changed in: papyon (Ubuntu Karmic)
Assignee: Loïc Minier (lool) => (unassigned)
--
Move Empathy Dependencies to Main and Update Desktop Seed
https://bugs.launchpad.net/bugs/388898
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed
I get that with latest karmic virtualbox running latest UNR daily (alpha
5 proposed image).
--
gvfs-gdu-volume-monitor crashed with SIGSEGV in gdu_pool_get_presentables()
https://bugs.launchpad.net/bugs/376145
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, whi
No remaining active MIRs, I'm unsubscribing ~ubuntu-mir from the bug;
please subscribe us again if there's something new to look at. Thanks!
--
[MIR] empathy dependencies
https://bugs.launchpad.net/bugs/388898
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, wh
** Summary changed:
- Connectivity subsystem has to account for Ofono's racy cell announcement
+ [DUAL SIM] Connectivity subsystem has to account for Ofono's racy cell
announcement
** Changed in: location-service (Ubuntu)
Importance: Critical => High
--
You received this bug notification be
** Changed in: trust-store (Ubuntu)
Importance: Critical => High
** Changed in: location-service (Ubuntu RTM)
Importance: Critical => High
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to location-service in Ubuntu.
https://bugs.
** Changed in: ubuntu-system-settings (Ubuntu)
Assignee: David Barth (dbarth) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to location-service in Ubuntu.
https://bugs.launchpad.net/bugs/1374577
Title:
'unconfine
Crashes have dried down completely
** Changed in: location-service (Ubuntu RTM)
Status: Confirmed => Invalid
** Changed in: trust-store (Ubuntu)
Status: Confirmed => Invalid
** Changed in: location-service (Ubuntu RTM)
Status: Invalid => Incomplete
** Changed in: trust-stor
** Changed in: location-service (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to location-service in Ubuntu.
https://bugs.launchpad.net/bugs/1356468
Title:
TOP RTM CRASHER: /usr/bin/tru
Public bug reported:
(This is a tracking bug)
When Android GPS device / GPS hardware is accessed too early, it
sometimes gets confused on krillin/mako.
To workaround this, location-service upstart job shipped in lxc-android-
config sleeps for 10 seconds before startup.
This is obviously an ugly
** Changed in: location-service (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to location-service in Ubuntu.
https://bugs.launchpad.net/bugs/1374577
Title:
'unconfined' should be precached
This bug was about a specific issue which got resolved; there might be other
bugs tracked elsewhere, like:
https://bugs.launchpad.net/ubuntu/+source/location-service/+bug/1382501
which affected webapps; this one has a fix proposed in rtm silo 4
--
You received this bug notification because you a
unconfined should never be shown.
On Monday, October 20, 2014, Víctor R. Ruiz <1354...@bugs.launchpad.net>
wrote:
> Some of the strings still appear untranslated, specially "unconfined".
> The trust-store.mo appear to ship half of those strings (and maybe
> location-service the other half of them?
Dropped before landing
** Changed in: lxc-android-config (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to location-service in Ubuntu.
https://bugs.launchpad.net/bugs/1382066
Title:
Drop sl
Dropped before landing
** Changed in: location-service (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to location-service in Ubuntu.
https://bugs.launchpad.net/bugs/1382066
Title:
Dro
Is that still an issue? we've fixed a startup issue in recent images
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to location-service in Ubuntu.
https://bugs.launchpad.net/bugs/1383724
Title:
In the welcome wizard enable location bu
** Summary changed:
- Location detection insists on being turned on
+ Location detection is always on, despite indicator
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to location-service in Ubuntu.
https://bugs.launchpad.net/bugs/13784
** Also affects: location-service (Ubuntu)
Importance: Undecided
Status: New
** Changed in: location-service (Ubuntu)
Importance: Undecided => Critical
** Changed in: location-service (Ubuntu)
Status: New => Confirmed
** Also affects: location-service (Ubuntu RTM)
Importan
To test whether the low-level HERE stack gets a location, put
http://people.canonical.com/~lool/espoo-cli on your phone (will be included
along HERE bits in the future) and run with:
chmod a+x espoo-cli
GLOG_logtostderr=1 GLOG_v=100
LD_LIBRARY_PATH=/custom/vendor/here/location-provider/lib/arm-l
Public bug reported:
Hi,
1. start one or more location using apps; see that they get location updates as
you move around
2. lock your screen, wait 30s
3. unlock screen, none of the apps get any location update anymore
4. kill and restart one of the location using apps, all apps now get location
Adding a sleep 15 before slpgwd exec has helped at least Alexander get a
position more reliably.
HERE debug on some affected phones shows a "general error" being
reported.
I've run a connectivity upstart job with "start on started dbus" to
start it in similar conditions; it did show a problematic
Public bug reported:
Hi,
https://bugs.launchpad.net/ubuntu/+source/location-service/+bug/1389874
was a symptom for an issue with connectivity API which doesn't work when
it starts before network-manager is started or when leaving airplane
mode.
To reproduce, create an upstart job like connectivi
** Branch linked: lp:~lool/ubuntu-location-provider-here/lp1389874
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to location-service in Ubuntu.
https://bugs.launchpad.net/bugs/1389874
Title:
Location detection is not working
To mana
** Changed in: location-service (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to location-service in Ubuntu.
https://bugs.launchpad.net/bugs/1389874
Title:
Location detection is not working
Public bug reported:
Hi,
in apps and with espoo-cli, I've noticed that the horizontal accuracy
(in meters) keeps climbing; I had seen this on cell in the past, but
it's particularly visible on wifi. Symptom is that your position is very
accurate, but the circle around it is very large, and keeps
Might be the same bug as https://bugs.launchpad.net/ubuntu/+source
/location-service/+bug/1387643 but need to debug with Thomas
** Changed in: location-service (Ubuntu)
Assignee: (unassigned) => Thomas Voß (thomas-voss)
--
You received this bug notification because you are a member of Ubun
** Also affects: ubuntu-location-provider-here (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to location-service in Ubuntu.
https://bugs.launchpad.net/bugs/1415029
Title:
Not yet a
** Changed in: ubuntu-location-provider-here (Ubuntu)
Assignee: (unassigned) => Loïc Minier (lool)
** Changed in: ubuntu-location-provider-here (Ubuntu)
Status: New => In Progress
** Changed in: ubuntu-location-provider-here (Ubuntu)
Importance: Undecided => High
--
You
You can use the defaults in Ubuntu, it should be picked up from /etc;
however .deb packages should ship schemas in /usr/share; this is
achieved by dh_gconf I think: it will move them from /etc to /usr.
--
GCONF_SCHEMA_FILE_DIR incorrect in gconf-2.m4
https://bugs.launchpad.net/bugs/537907
You rec
Public bug reported:
Hi,
To test location-service with latest utopic-proposed image on mako, I had to
make some adjustments:
1) change:
export HERE_IMEI_FRAGMENT=$Serial
to:
export HERE_IMEI_FRAGMENT=35513605
in /etc/init/ubuntu-location-provider-here-posclientd.conf to help the service
Public bug reported:
Hi,
while testing location-service in utopic-proposed on mako, I've reproduced the
exact same setup as in bug #1367835, but disabled the GPS provider to avoid the
error described in this bug:
1) change:
export HERE_IMEI_FRAGMENT=$Serial
to:
export HERE_IMEI_FRAGMENT
this is not reproducible 100% of the time
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to location-service in Ubuntu.
https://bugs.launchpad.net/bugs/1367836
Title:
ubuntu-location-serviced crashed with SIGABRT in
__gnu_cxx::__ver
Public bug reported:
Hey
when restarting ubuntu-location-service, trust-store agent is restarted but
spawns too quickly; this is its upstart snippet:
start on (started dbus and xsession SESSION=ubuntu-touch) or \
:sys:started JOB=ubuntu-location-service
stop on desktop-end or :sys:stopping J
** Changed in: location-service (Ubuntu)
Assignee: (unassigned) => Thomas Voß (thomas-voss)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to location-service in Ubuntu.
https://bugs.launchpad.net/bugs/1369692
Title:
Sleep 2 -- T
so first, the GPS download warning is indeed just a warning; the GPS
provider currently only works standalone, there's a bug preventing it to
work with the HERE location provider ("Espoo").
The issue you now have is that the default location service config
points to the HERE location provider whic
In my experience, due to LP #1367244 it's rare that HERE works on boot.
However, I can reliably get a position in my regular testing setup by
restarting ubuntu-location-provider-here-posclientd after boot. Then I
always get a position after 30s in OSMTouch and in webapps.
--
You received this bug
This hits other users of dbus-cpp API; e.g.
https://bugs.launchpad.net/espoo/+bug/1368247
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to location-service in Ubuntu.
https://bugs.launchpad.net/bugs/1358918
Title:
ubuntu-location-ser
Just use , + c rather than ' + c?
--
cedilla appears as accented c (ć instead of ç) when typing 'c
https://bugs.launchpad.net/bugs/518056
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gtk+2.0 in ubuntu.
--
desktop-bugs mailing list
de
Ah I thought you were using a compose-key sequence, but it's just a
regular sequence.
I think changing the default input method for Gtk+ when using an en
layout would be quite intrusive though. Perhaps we can fix the en
default input method to be more useful to type French ç instead.
--
cedilla
BTW I think you can override the immodules definition with
/etc/gtk-2.0/gtk.immodules.
--
cedilla appears as accented c (ć instead of ç) when typing 'c
https://bugs.launchpad.net/bugs/518056
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to
** Changed in: gtk+2.0 (Ubuntu)
Assignee: (unassigned) => Loïc Minier (lool)
--
redundant declarations of gtk_widget_set_realized, gtk_widget_get_realized,
gtk_widget_set_mapped, and gtk_widget_get_mapped
https://bugs.launchpad.net/bugs/521135
You received this bug notification because
Not sure what you mean with hardcoded; these are from the libc6.symbols
deps.
--
upper dependencies on libc6 (<< 2.11)
https://bugs.launchpad.net/bugs/508702
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to glib2.0 in ubuntu.
--
desktop-
In the case of glib2.0, I see it's at least using __abort_msg which will
cause a dep on libc6 (>> 2.10), libc6 (<< 2.11); this is added in a
packaging patch.
--
upper dependencies on libc6 (<< 2.11)
https://bugs.launchpad.net/bugs/508702
You received this bug notification because you are a member
Rolf, Ubuntu binaries are not ready for an embedded use case where the
space saving issue would really make a difference. However we do care
to have support for Thai out of the box -- especially if it's so cheap
in terms of space to get.
I think a bettter argument against the libthai dep is the r
Upstream bug which triggered this change in behavior in glib:
https://bugzilla.gnome.org/show_bug.cgi?id=563627
** Bug watch added: GNOME Bug Tracker #563627
https://bugzilla.gnome.org/show_bug.cgi?id=563627
--
g_set_prgname() called multiple times
https://bugs.launchpad.net/bugs/501670
You r
** Changed in: gtk+2.0 (Ubuntu)
Assignee: (unassigned) => Loïc Minier (lool)
--
drag-dest signal handlers don't get correctly disconnected when unsetting the
drag dest
https://bugs.launchpad.net/bugs/514473
You received this bug notification because you are a member of Ubuntu
Desk
LDFLAGS or CFLAGS? LDFLAGS default to no optimization (-O0) not O2.
--
nautilus assert failure: *** stack smashing detected ***: nautilus terminated
https://bugs.launchpad.net/bugs/512959
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to n
I've uploaded this and am hence lowering importance, but this needs to be filed
with binutils upstream.
nautilus (1:2.29.2-0ubuntu2) lucid; urgency=low
* Only add -Wl,-O1 to LDFLAGS if DEB_HOST_ARCH != armel; thanks Paul Larson;
LP #512959.
-- Loïc Minier Tue, 02 Feb 2010 19:
Revert the nautilus change and redid the change for gvfs; sorry, was
focused on the bug title and that matched the nautilus rules, my bad.
--
nautilus assert failure: *** stack smashing detected ***: nautilus terminated
https://bugs.launchpad.net/bugs/512959
You received this bug notification bec
*** This bug is a duplicate of bug 375896 ***
https://bugs.launchpad.net/bugs/375896
** This bug has been marked a duplicate of bug 375896
yelp crashes on start
--
help crashes on startup
https://bugs.launchpad.net/bugs/387560
You received this bug notification because you are a member of
*** This bug is a duplicate of bug 375896 ***
https://bugs.launchpad.net/bugs/375896
** This bug has been marked a duplicate of bug 375896
yelp crashes on start
--
yelp crashed with SIGSEGV in rrn_for_each_in_category()
https://bugs.launchpad.net/bugs/384381
You received this bug notifica
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7f40212da950 (LWP 32511)]
0x7f4032af2730 in ?? () from /usr/lib/librarian.so.0
Current language: auto; currently asm
(gdb) bt
#0 0x7f4032af2730 in ?? () from /usr/lib/librarian.so.0
#1 0x7f4032af2827 in ?? ()
After a debug build of rarian, I see:
(gdb) bt
#0 0x7fd3763337b0 in strcmp () from /lib/libc.so.6
#1 0x7fd3774d23fe in ?? () from /usr/lib/librarian.so.0
#2 0x7fd3774d24a7 in ?? () from /usr/lib/librarian.so.0
#3 0x7fd3774d21ff in ?? () from /usr/lib/librarian.so.0
#4 0x7fd
Public bug reported:
Binary package hint: gnome-panel
Hi
After installing Ubuntu on this system from the alternate CD, I noticed
that gnome-panel didn't have any location configured in the clock
applet. However I had to pick a timezone during install and this
timezone was honored in the GNOME s
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/28109921/Dependencies.txt
--
No location set in gnome-panel after install with alternate CD
https://bugs.launchpad.net/bugs/389392
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is
Rebuilding yelp with noopt nostrip didn't help either, backtrace is
still awful.
I straced -f yelp and it would open /usr/share/gnome/help/libs/shipped-
docs last, but commenting out everythingin this file didn't help it get
any further in the strace.
--
yelp crashes on start
https://bugs.launch
Fix Committed
** Changed in: rarian (Ubuntu)
Assignee: (unassigned) => Loïc Minier (lool)
--
yelp crashes on start
https://bugs.launchpad.net/bugs/375896
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to rarian in ubuntu.
--
d
*** This bug is a duplicate of bug 375896 ***
https://bugs.launchpad.net/bugs/375896
** This bug has been marked a duplicate of bug 375896
yelp crashes on start
--
yelp crash when user is not root.
https://bugs.launchpad.net/bugs/384360
You received this bug notification because you are
*** This bug is a duplicate of bug 375896 ***
https://bugs.launchpad.net/bugs/375896
** This bug has been marked a duplicate of bug 375896
yelp crashes on start
--
yelp segfault
https://bugs.launchpad.net/bugs/382119
You received this bug notification because you are a member of Ubuntu
De
** Also affects: f-spot (Ubuntu Jaunty)
Importance: Undecided
Status: New
** Also affects: f-spot (Ubuntu Karmic)
Importance: Low
Assignee: Iain Lane (laney)
Status: In Progress
** Changed in: f-spot (Ubuntu Karmic)
Status: In Progress => Fix Committed
--
Imports
** Changed in: f-spot (Ubuntu)
Assignee: (unassigned) => Canonical Mobile Team (canonical-mobile)
--
f-spot seems wrongly packaged / unusable for armel
https://bugs.launchpad.net/bugs/390591
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscrib
*** This bug is a duplicate of bug 390591 ***
https://bugs.launchpad.net/bugs/390591
** Visibility changed to: Public
--
f-spot.exe crashed with SIGSEGV on ARM
https://bugs.launchpad.net/bugs/390701
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is
Could you please attach the updated Babbage 2 RedBoot as well? I tried
reproducing, but I can't boot using the B1 RedBoot.
--
notification area applets crash on login
https://bugs.launchpad.net/bugs/392716
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which
I didn't find the 200925 RedBoot source drop, only 200918; are you
blocking on this for release?
--
notification area applets crash on login
https://bugs.launchpad.net/bugs/392716
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
des
I took a rootfs with GNOME I had prepared for Babbage 2 which was
working fine there, moved that to Babbage 1; it's on a SATA disk which I
plug via an USB adapter. I could boot this using the new RedBoot
attached to this bug report (candidate 200925 I guess) and it would
trigger the described erro
I confirmed that I'm using the proper RedBoot versions above; with "FSL
200918 - built 09:45:10, Apr 29 2009" I still get the bug. This is FSL
binary.
--
notification area applets crash on login
https://bugs.launchpad.net/bugs/392716
You received this bug notification because you are a member of
Still with the same kernel, I tried with Ubuntu's RedBoot "FSL 200910 -
built 14:12:08, Apr 7 2009" as extracted from the jaunty/karmic
redboot-imx51-babbage 200910-0ubuntu2 armel .deb and I don't get the
issue. (I only get the mixer applet warning which is due to lack of
sound support.)
--
not
So this time the dmesg was different! I see this delta:
-mc13892 Rev 0.0 FinVer 0 detected
+mc13892 Rev 1.1 FinVer 0 detected
and this:
-eth0: ethernet 00:00:00:00:00:00
+eth0: ethernet 00:00:45:67:89:ab
There is a difference though: I did a hot reboot instead of a cold reboot. In
particular t
So in all "bad" boots, eth0's HWaddr was 00:00:00:00:00:00, and in all
good boots it was set properly; I think this just indicates that RedBoot
does more platform init in the old Ubuntu versions than in the newer FSL
binaries.
--
notification area applets crash on login
https://bugs.launchpad.net
Comparing a good cold and hot reboot, I saw no big difference; mostly timing
and clock:
-pmic_rtc pmic_rtc.1: setting system clock to 2009-06-30 15:22:04 UTC
(1246375324)
+pmic_rtc pmic_rtc.1: setting system clock to 1970-01-01 00:00:21 UTC (21)
--
notification area applets crash on login
https
Ok, I booted with RedBoot 200918, still got the issue, stopped gdm,
checked the date and it was "Tue Aug 14 06:58:02 WEST 1923".
I set the date with date -s, restarted gdm, and didn't have the issue
anymore.
I tried resetting the date to 'Tue Aug 14 06:58:02 WEST 1923', but could
NOT as it's an i
So my understanding is:
- some redboot + kernel combo doesn't set RTC correctly on boot anymore; it
looks like it's because the I2C chip isn't initialized properly:
redboot-200918/dmesg-bad:sgtl5000-i2c 1-000a: Device initialisation failed
redboot-200925/dmesg-bad:sgtl5000-i2c 1-000a: Device initi
(all tests on Babbage 1)
--
notification area applets crash on login
https://bugs.launchpad.net/bugs/392716
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubunt
Note that with the broken RedBoot, I get a zeroed MAC address which prevents
bringing up the network here.
# ifup eth0
SIOCSIFFLAGS: Cannot assign requested address
SIOCSIFFLAGS: Cannot assign requested address
after setting the MAC manually, it works.
** Package changed: gnome-applets (Ubuntu)
Fixed in karmic some time ago:
gtk+2.0 (2.16.1-0ubuntu3) karmic; urgency=low
* Add missing backslash after --enable-print-backend which cause the --host
and --build args to be ignored and hence the wrong triplet to be used.
-- Loic Minier Sun, 10 May 2009 19:34:06 +0200
** Changed in:
I had uploaded g-k built with -O1 to workaround this bug in jaunty.
** Changed in: gnome-keyring (Ubuntu Jaunty)
Status: Won't Fix => Fix Released
** Changed in: gnome-keyring (Ubuntu Jaunty)
Assignee: Oliver Grawert (ogra) => Loïc Minier (lool)
--
[arm] gnome-keyring-da
This is fixed for me with the latest 009 version of devicekit-power
** Changed in: gnome-power-manager (Ubuntu)
Status: Confirmed => Fix Released
--
Broken and weird warning dialogs when booting with an empty battery
https://bugs.launchpad.net/bugs/380255
You received this bug notificati
I believe the latest version of devicekit-power fixes this, but it needs
testing.
--
System shutdown on 0% for 1 of 2 batteries.
https://bugs.launchpad.net/bugs/379599
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-power-manager in
1 - 100 of 371 matches
Mail list logo
