Getting binaries for hardy...
[Updating] gtk+2.0 (2.12.2-0ubuntu1 [Ubuntu] 2.12.2-1 [Debian])
* Trying to add gtk+2.0...
- gtk+2.0_2.12.2.orig.tar.gz: already in distro - downloading from
librarian - gtk+2.0_2.12.2-1.dsc: downloading from
http://ftp.uk.debian.org/debian/
-
** Changed in: gnome-vfs2 (Ubuntu)
Target: hardy-alpha-1 = hardy-alpha-2
--
trash lists / content due to .trash_entry_cache value
https://bugs.launchpad.net/bugs/85608
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug contact for
I've just tested with downgrading to the intrepid version of gnome-
screensaver; same results.
I've also done a bit of stracing, and the helper does get as far as
reading /etc/pam.d and loading the modules; then it falls down somewhere
around where it spawns a separate thread for PAM in order to
Output from gnome-screensaver --no-daemon --debug while trying to get
the screen to unlock:
[find_window_at_pointer] gs-manager.c:1175 (01:53:03): Requesting unlock for
screen 0
[gs_window_request_unlock] gs-window-x11.c:1586 (01:53:03): Requesting
unlock
[window_dialog_up_cb]
I would like to hear back from the original submitter before concluding
this was a duplicate, especially since the bug in question was *not*
fixed yet on Jan 21 when you commented that it had stopped for you.
--
gnome-settings-daemon crashed with SIGSEGV in gnome_rr_config_match()
Tested without GTK_IM_MODULE set per Seb - gnome-screensaver works fine
when not using GTK_IM_MODULE=xim.
** Changed in: gtk+2.0 (Ubuntu Jaunty)
Sourcepackagename: gnome-screensaver = gtk+2.0
--
gnome-screensaver dialog helper spins indefinitely, never unlocks the session,
when GTK_IM_MODULE
** Summary changed:
- gnome-screensaver dialog helper spins indefinitely, never unlocks the session
+ gnome-screensaver dialog helper spins indefinitely, never unlocks the
session, when GTK_IM_MODULE is set
--
gnome-screensaver dialog helper spins indefinitely, never unlocks the session,
when
' and then suspending with Fn+F4.
** Changed in: hal (Ubuntu)
Status: New = Invalid
** Changed in: acpi-support (Ubuntu)
Sourcepackagename: linux = acpi-support
Assignee: Andy Whitcroft (apw) = Steve Langasek (vorlon)
Status: In Progress = Fix Committed
** Changed in: gnome-power
To the extent that this is an acpi-support problem, the fix is committed
now and will be uploaded soon. However, with or without acpi-support,
the kernel now synthesizes a keypress event for these buttons due to the
mask set in /sys/devices/platform/thinkpad_acpi/hotkey_mask. The
setting of this
On Sun, Feb 01, 2009 at 03:24:34PM -, Arne Goetje wrote:
Can you please test with GTK_IM_MODULE=scim-bridge, since that is the
default setting in Intrepid and Jaunty?
Confirmed, the problem is also present when specifying
GTK_IM_MODULE=scim-bridge.
--
Steve Langasek Give
*** This bug is a duplicate of bug 322126 ***
https://bugs.launchpad.net/bugs/322126
** Attachment added: CoreDump.gz
http://launchpadlibrarian.net/21892439/CoreDump.gz
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/21892440/Dependencies.txt
** Attachment added:
Looks like my apport bug got automarked as a duplicate of this one. I'm
happy to do a valgrind test - can you provide more guidance wrt the best
way to launch a gvfsd backend under valgrind, given that these are
normally auto-spawned by gvfsd itself?
--
gvfsd-gphoto2 crashed with SIGSEGV in
*** This bug is a duplicate of bug 321311 ***
https://bugs.launchpad.net/bugs/321311
** This bug has been marked a duplicate of bug 321311
gnome-screensaver dialog helper spins indefinitely, never unlocks the
session, when GTK_IM_MODULE is set
--
gnome-screensaver fails to unlock after
of 'lshal -m'.)
It's not clear to me why this affects some systems and not other.
For me, lshal -m shows:
17:05:11.878: computer_logicaldev_input_4 condition ButtonPressed =
sleep
and no other events when hitting Fn+F4.
--
Steve Langasek Give me a lever long enough and a Free
Based on discussion with apw, reopening this task since it appears that
gnome-power-manager is responding to both an X key event and a hal event
when it shouldn't do so.
** Changed in: gnome-power-manager (Ubuntu)
Status: Invalid = Confirmed
--
Resume (from memory) goes back to sleep
I can confirm that this bug is fixed in the latest jaunty upload.
** Changed in: gvfs (Ubuntu)
Status: Incomplete = Fix Released
--
gvfsd-gphoto2 crashed with SIGSEGV in malloc()
https://bugs.launchpad.net/bugs/322126
You received this bug notification because you are a member of Ubuntu
The 'disable touchpad' key currently doesn't work with acpi-support
because it relies on the obsolete synclient command. The right command
to toggle touchpads in 8.10 and above is xinput:
$ xinput set-int-prop devnum 'Device Enabled' 8 [0|1]
hal needs to be fixed to relay this event, and
** Tags added: verification-done
** Tags removed: verification-needed
--
Suspends that are longer than 6 hours will inexplicably claim to fail, but not
really fail
https://bugs.launchpad.net/bugs/242713
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which
Public bug reported:
Binary package hint: gnome-panel
From at least Feb 1 on, I'm unable to change my current timezone in
jaunty. Clicking the 'set' button results in a dialog popup:
Failed to set the system timezone
Launch helper exited with unknown return code 1
ProblemType: Bug
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/22035830/Dependencies.txt
** Changed in: gnome-panel (Ubuntu Jaunty)
Importance: Undecided = Medium
Assignee: (unassigned) = Ubuntu Desktop Bugs (desktop-bugs)
Status: New = Confirmed
** Tags added:
Public bug reported:
Binary package hint: gnome-settings-daemon
While debugging keymap issues, I've manually stopped and restarted
gnome-settings-daemon, which leaves stderr attached to the tty. I
notice that every time I switch VTs (e.g., when suspending/resuming),
g-s-d spits out a lot of
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/22035974/Dependencies.txt
** Changed in: gnome-settings-daemon (Ubuntu)
Importance: Undecided = Low
--
g-s-d spews warnings when switching VTs
https://bugs.launchpad.net/bugs/326088
You received this bug notification
Ah, I distinctly did not restart gnome-panel after upgrade. Done so now
and it's fixed, thanks. :)
** Changed in: gnome-panel (Ubuntu Jaunty)
Status: Confirmed = Fix Released
--
can't set the timezone from the clock applet: Launch helper exited with unknown
return code 1
bug #327550 has been marked as a duplicate of this one, but this bug is
two years old whereas the crash has only started happening for me this
week. Something must have changed - do you have any idea what?
--
[apport] evolution crashed with SIGSEGV in ORBit_small_get_servant()
Thank you for taking the time to report this bug and help to improve
Ubuntu.
The acpi-support package is deprecated, and the key handling provided
there is being phased out in favor of direct handling by hal and the
GNOME desktop. I believe gnome-settings-daemon is the component that
handles the
Thank you for taking the time to report this issue and help to improve
Ubuntu.
This hotkey is not handled by acpi-support; it must be handled by either
gnome-power-manager or the kernel. Reassigning to g-p-m.
** Changed in: gnome-power-manager (Ubuntu)
Sourcepackagename: acpi-support =
Public bug reported:
Binary package hint: gnome-keyring
I want to make sure this bug gets reported because it seems like a
pretty serious regression in gnome-keyring, but I'm not sending a
coredump to launchpad because gnome-keyring-daemon actually had ahold of
my ssh private key at the time it
This bug is marked as resolved in Ubuntu 8.04; are you sure this is the
bug you're seeing? You don't give any details about the problem you're
having.
--
SMB error: Unable to mount location when server configured with security=share
https://bugs.launchpad.net/bugs/209520
You received this bug
** Changed in: gnome-keyring (Ubuntu)
Sourcepackagename: acpi-support = gnome-keyring
--
[Intrepid] suspend to ram, gnome ssh askpass
https://bugs.launchpad.net/bugs/280242
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-keyring
** Changed in: linux (Ubuntu)
Sourcepackagename: acpi-support = linux
** Changed in: gnome-panel (Ubuntu)
Sourcepackagename: linux = gnome-panel
--
When I press the shutdown button, the bar disappears and I cannot run command
line
https://bugs.launchpad.net/bugs/301242
You received this bug
** Changed in: gnome-screensaver (Ubuntu)
Sourcepackagename: acpi-support = gnome-screensaver
--
on user change after resume, system hibernate again
https://bugs.launchpad.net/bugs/305730
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to
** Changed in: gnome-power-manager (Ubuntu)
Sourcepackagename: acpi-support = gnome-power-manager
--
[intrepid] Laptop suspends randomly (Medion MD 95400)
https://bugs.launchpad.net/bugs/298836
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is
the apport-retrace command appears to be broken in jaunty, but here's a
backtrace from manually unpacking the apport report and running gdb with
the dbgsym packages installed.
(gdb) thread apply all bt full
Thread 2 (process 1322):
#0 0x7f84d11b8496 in poll () from /lib/libc.so.6
No symbol
oh - sorry, you mentioned upgrading from 7.10 so I assumed you were
running 8.04. Yes, for 8.10 and above the default samba client behavior
matches upstream's, and doesn't allow insecure security=share
connections by default.
You can change the behavior on the client side by setting 'client
marking invalid for acpi-support; this is a gnome-power-manager issue
only, acpi-support is not triggering this shutdown.
** Changed in: acpi-support (Ubuntu)
Status: Confirmed = Invalid
--
shutdown after plugging in AC with critical battery
https://bugs.launchpad.net/bugs/70293
You
acked for sponsorship and FFe.
** Changed in: gtk-doc (Ubuntu)
Status: New = Confirmed
--
Please sync gtk-doc 1.11-3 (main) from debian unstable (main)
https://bugs.launchpad.net/bugs/331201
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is
[Updating] gtk-doc (1.10-1ubuntu1 [Ubuntu] 1.11-3 [Debian])
* Trying to add gtk-doc...
- gtk-doc_1.11.orig.tar.gz: downloading from http://ftp.debian.org/debian/
- gtk-doc_1.11-3.dsc: downloading from http://ftp.debian.org/debian/
- gtk-doc_1.11-3.diff.gz: downloading from
** Changed in: yelp (Ubuntu Intrepid)
Assignee: wangker (272788089-qq) = (unassigned)
--
Intrepid Compiz hangs on login for i830MG, i845, (and i945GM?) video cards
https://bugs.launchpad.net/bugs/259385
You received this bug notification because you are a member of Ubuntu
Desktop Bugs,
reassigning to glibc, because I was just about to file for removal of
belocs-locales-bin from jaunty since it's now uninstallable following
the last glibc change.
** Changed in: glibc (Ubuntu)
Sourcepackagename: belocs-locales-bin = glibc
--
Can't select Esperanto language in gnome
Public bug reported:
Given a .desktop file with the following line:
Exec=env WINEPREFIX=/home/vorlon/.wine wine
C:\\comlogo\\Comlogo.exe c:\\comlogo\\demo\\kidspac.lgp
clicking on it causes the following command to be executed:
wine C:\comlogo\Comlogo.exe c:comlogodemokidspac.lgp
I.e.,
This is not a bug in 'acpi', which is an unrelated Ubuntu package.
Marking invalid.
** Changed in: acpi (Ubuntu)
Status: Confirmed = Invalid
--
Resuming from Suspend cause power button action to be called
https://bugs.launchpad.net/bugs/272587
You received this bug notification because
PhilT,
If you stop acpid ('sudo service acpid stop'), does this problem
persist?
I suspect that this is a linux kernel bug, not a bug in acpi-support.
--
Resuming from Suspend cause power button action to be called
https://bugs.launchpad.net/bugs/272587
You received this bug notification
that's not an appropriate use of the 'incomplete' status.
** Changed in: shadow (Ubuntu)
Status: Incomplete = New
** Changed in: pam (Ubuntu)
Status: Incomplete = New
--
users with no password can't log in with gdm
https://bugs.launchpad.net/bugs/104957
You received this bug
The 'incomplete' status is meant to indicate that more information is
needed from the bug submitter. You appear to be asking for information
from the developers...
It's already been acknowledged by one of the shadow developers as a bug
in that package. I'm still considering whether we should
** Changed in: shadow (Ubuntu)
Importance: Undecided = Low
** Changed in: shadow (Ubuntu)
Status: New = Confirmed
** Changed in: shadow (Ubuntu)
Status: Confirmed = Triaged
--
users with no password can't log in with gdm
https://bugs.launchpad.net/bugs/104957
You received this
Public bug reported:
Binary package hint: gnome-control-center
In karmic using KMS, gnome-display-properties shows both my laptop LCD
and my external monitor as 'Unknown'. I know it gave useful descriptors
to these in the past, so I think this is a regression connected to KMS
itself. In any
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/27424589/Dependencies.txt
** Tags added: regression-potential
--
gnome-display-properties doesn't show output names with KMS
https://bugs.launchpad.net/bugs/382873
You received this bug notification because you are a member
Thank you for taking the time to report this bug and help to improve
Ubuntu.
The acpi-support package is not involved with the screen locking policy;
this would seem to be a screensaver issue. You don't mention whether
you're using Ubuntu or another variant, so assuming gnome-screensaver.
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/27462946/Dependencies.txt
--
seahorse no longer running after upgrade to karmic, no gpg agent available
https://bugs.launchpad.net/bugs/383256
You received this bug notification because you are a member of Ubuntu
Desktop
Public bug reported:
Binary package hint: seahorse
With the merge of seahorse 2.24.1-1 from Debian, seahorse no longer
ships an Xsession file, so seahorse is not started by default on the
desktop. The net result of this is that there's no gpg agent running
anymore; since this is the only thing
Public bug reported:
Binary package hint: gnome-power-manager
After upgrade to karmic, gnome-power-manager is showing all the icons
using the default GNOME theme instead of the Ubuntu theme. It's ugly
and jarring and I can't make sense of any of the icons. Please fix. :-)
ProblemType: Bug
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/27463818/Dependencies.txt
** Attachment added: DevkitPower.txt
http://launchpadlibrarian.net/27463819/DevkitPower.txt
** Attachment added: GConfNonDefault.txt
http://launchpadlibrarian.net/27463820/GConfNonDefault.txt
Public bug reported:
Binary package hint: gnome-power-manager
In karmic, mouseovers on gnome-power-manager show only one of three
values for me: 79%, 49%, or 19%. Before upgrading, a mouseover would
show an accurate value for battery charge, as well as an estimate of
remaining time. I have no
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/27470240/Dependencies.txt
** Attachment added: DevkitPower.txt
http://launchpadlibrarian.net/27470241/DevkitPower.txt
** Attachment added: GConfNonDefault.txt
http://launchpadlibrarian.net/27470242/GConfNonDefault.txt
Thanks for the output. One difference to my system is this:
blank_screen = false
On my system this is set to blank_screen = true. Does changing this
setting have any effect on the behavior?
Also, I don't know if you missed my earlier question: when you close
the lid, does the screensaver
*** This bug is a duplicate of bug 357673 ***
https://bugs.launchpad.net/bugs/357673
** This bug has been marked a duplicate of bug 357673
No notification when sliding audio volume, muting volume on ThinkPad X31,
X32, X41, X60, T22, T42, T60, R50e, R51, R52
--
Wrong handling of volume
** Changed in: hotkey-setup (Ubuntu)
Status: New = Invalid
--
Cannot change volume with keyboard volume dial while in drop down menu.
https://bugs.launchpad.net/bugs/286050
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
Thank you for taking the time to report this bug and help to improve
Ubuntu.
You say that the keys are recognized when you try to bind them in gnome-
keybinding-properties - are they shown with exactly these names -
XF86Mail, XF86Homepage, and XF86Launch2?
If you can see these key names, then
Thank you for taking the time to report this issue and help to improve
Ubuntu.
Since you are seeing the visualization, the hotkeys themselves are
working normally but the desktop evidently does not have them mapped to
the correct mixer. If you look in System-Preferences-Sound, which
device do
rolling this back to 'triaged' since the fix in hardy-proposed seems to
not work. I'm uploading a new gvfs package to hardy-proposed with this
patch reverted, and trying to fix bug #216104.
** Changed in: gvfs (Ubuntu Hardy)
Status: Fix Committed = Triaged
--
nautilus does not display
On Thu, Jun 18, 2009 at 01:27:49PM -, Martin G Miller wrote:
Something about DNS redirection causes network browsing failures in
Nautilus.
That is unrelated to this bug report.
--
Steve Langasek Give me a lever long enough and a Free OS
Debian Developer
This was never a bug in shadow. Closing that task as invalid.
** Changed in: shadow (Ubuntu)
Status: Confirmed = Invalid
--
Cannot access wireless networks keys when user change his session password.
https://bugs.launchpad.net/bugs/162710
You received this bug notification because you
The actual fix was included in Debian version 2.26.0-3 of gnome-keyring,
and that fix is now in karmic. Changelog:
gnome-keyring (2.26.0-3) unstable; urgency=low
* libgp11-0.shlibs: add shlibs file for libgp11. Closes: #522381.
* libgcr0.symbols, libgnome-keyring0.symbols: add
Public bug reported:
Binary package hint: gnome-settings-daemon
After a recent upgrade in karmic, gnome-settings-daemon has started
giving me dialogs on every login, informing me that two of my disks are
low on disk space (one is at 97% full, the other at 98% full).
I didn't ask its opinion.
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/28189347/Dependencies.txt
--
gnome-settings-daemon should keep its opinions about my disk management to
itself
https://bugs.launchpad.net/bugs/390504
You received this bug notification because you are a member of Ubuntu
example screenshot.
** Attachment added: gnome-nagging-daemon.png
http://launchpadlibrarian.net/28189349/gnome-nagging-daemon.png
** Also affects: gnome-settings-daemon (Ubuntu Karmic)
Importance: Undecided
Status: New
** Changed in: gnome-settings-daemon (Ubuntu Karmic)
** Changed in: metacity (Ubuntu)
Status: Confirmed = Triaged
--
Resizing windows by grabbing window borders is difficult [please no more
comments; patches welcome]
https://bugs.launchpad.net/bugs/160311
You received this bug notification because you are a member of Ubuntu
Desktop Bugs,
Fixed, actually. Sorry for not following up; seems to have gone away
post-karmic.
** Changed in: gnome-settings-daemon (Ubuntu)
Status: Invalid = Fix Released
--
when I open my laptop lid, gsd changes my resolution
https://bugs.launchpad.net/bugs/434269
You received this bug
Ah, sorry for misreading. The thing is that plymouthd is supposed to be
run *twice* on the system, once at startup and once at shutdown. I
assumed that what you were seeing was a plymouthd process running at
shutdown like it's supposed to; the open /var/log/boot.log (and the
--mode=boot argument
someone should check whether this also affects kdm - it probably does.
--
plymouthd alive when umountroot runs (prevents clean unmount)
https://bugs.launchpad.net/bugs/665195
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm in ubuntu.
It's not unpredictable; it just requires that, once the gdm or kdm job
starts, it takes care of stopping plymouth before it exits.
There is no simpler design that satisfies the boot-time requirements.
--
plymouthd alive when umountroot runs (prevents clean unmount)
This is not a bug in cryptsetup; like various others, it's a bug in
whatever is mounting the disk without properly unmounting it on logout.
Maybe this is gnome-disk-utility?
Log out of first use and log into second user (switching users would
also do)
No, because that implies that you want both
to be clear about the
rationale and note that there are use cases that ntpdate will not satisfy.
--
Steve Langasek Give me a lever long enough and a Free OS
Debian Developer to set it on, and I can move the world.
Ubuntu Developer
;)
--
Steve Langasek Give me a lever long enough and a Free OS
Debian Developer to set it on, and I can move the world.
Ubuntu Developerhttp://www.debian.org/
slanga...@ubuntu.com vor...@debian.org
Caused by having the new pango1.0 installed, but not the new plymouth.
I think we want pango1.0 to declare Breaks: plymouth ( $fixedver) to
ensure smooth upgrades.
** Package changed: initramfs-tools (Ubuntu) = pango1.0 (Ubuntu)
** Changed in: pango1.0 (Ubuntu)
Importance: Undecided = High
Public bug reported:
Binary package hint: gnome-media
On upgrade to natty, gnome-volume-control is no longer useful as a tool
for selecting audio devices for input and output. Under each tab, it
only shows the *current* device, giving no capability to select a
different device even though this
** Tags added: regression
** Changed in: gnome-media (Ubuntu)
Importance: Undecided = High
** Also affects: gnome-media (Ubuntu Natty)
Importance: High
Status: New
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to
Yes, but that's a wrong fix. You should upgrade the plymouth package to
the current version instead.
** Changed in: pango1.0 (Ubuntu)
Assignee: (unassigned) = Steve Langasek (vorlon)
** Also affects: pango1.0 (Ubuntu Natty)
Importance: High
Assignee: Steve Langasek (vorlon
This bug is also not reproducible for me after a reboot (I had restarted X
once, but not restarted the whole system, following the upgrade). So
perhaps this bug should be closed, or perhaps this gives you more
information about how the upgrade could be made more robust?
Thanks,
--
Steve Langasek
** Changed in: gnome-media (Ubuntu Natty)
Status: New = Won't Fix
** Changed in: gnome-media (Ubuntu)
Importance: High = Medium
** Changed in: gnome-media (Ubuntu Natty)
Importance: High = Medium
--
You received this bug notification because you are a member of Ubuntu
Desktop
The original bug is now fixed, but a converse bug is present that if
plymouth is upgraded before pango, plymouth is looking for these modules
in the *new* path and fails for the same reason.
I think in this direction a more subtle fix is needed than a Breaks,
since there are cases where plymouth
Public bug reported:
gnome-games version 1:2.32.1-0ubuntu4 failed to build on armel
Link to failed build:
https://launchpad.net/ubuntu/+source/gnome-games/1:2.32.1-0ubuntu4/+buildjob/2419394
Direct link to the build log: https://launchpad.net/ubuntu/+source
This is a buggy assumption on the part of cmake. The standard interface
that glib provides for consumers to query its library paths and cflags
is pkg-config. On natty:
$ pkg-config --cflags glib-2.0
-I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include
$
cmake should use
as a workaround.
** Also affects: bamf (Ubuntu)
Importance: Undecided
Status: New
** Changed in: bamf (Ubuntu)
Status: New = Triaged
** Changed in: bamf (Ubuntu)
Importance: Undecided = High
** Changed in: bamf (Ubuntu)
Assignee: (unassigned) = Steve Langasek (vorlon
Public bug reported:
Binary package hint: metacity
Using metacity in natty (with the intel driver), if I use alt+tab to
cycle between three windows, and I cycle past a window which overlaps
the previously-foregrounded window, a line is left behind after alt+tab
where the border of the
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to metacity in Ubuntu.
https://bugs.launchpad.net/bugs/759203
Title:
alt+tab window cycling leaves window borders drawn across windows
--
desktop-bugs mailing list
screenshot.
** Attachment added: wm-snail-trail.png
https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/759203/+attachment/2026655/+files/wm-snail-trail.png
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to metacity in Ubuntu.
to reproduce:
- open three terminal windows on the desktop.
- position two of the windows so that they partially overlap
- adjust the alt-tab order of the windows so that the overlapping windows are
the first two in the list.
- alt-tab to the third window (cycling past the second one)
- the
*** This bug is a duplicate of bug 740387 ***
https://bugs.launchpad.net/bugs/740387
Yes, removing that patch corrects the issue. Marking as a duplicate.
** This bug has been marked a duplicate of bug 740387
graphical corruption with multiple drivers and classic desktop
* You can
I initially thought the problem was fixed, but after subsequent use I
was still seeing corruption. I wasn't sure whether I had accidentally
overwritten my locally-built package so didn't follow up... but now I've
upgraded to the metacity that's supposed to fix bug #740387 and I'm
still seeing
Public bug reported:
glib2.0 is failing to build on armel with the following error:
/bin/bash ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I.
-I/build/buildd/glib2.0-2.25.8/glib -I.. -I/build/buildd/glib2.0-2.25.8
-DG_LOG_DOMAIN=\GLib\ -DG_ENABLE_DEBUG -DG_DISABLE_DEPRECATED
Marcin, could you have a look at fixing this?
** Changed in: glib2.0 (Ubuntu Maverick)
Milestone: maverick-alpha-2 = None
** Changed in: glib2.0 (Ubuntu Maverick)
Assignee: (unassigned) = Marcin Juszkiewicz (hrw)
--
glib2.0 2.25.8-1ubuntu1 FTBFS on armel: expected 'struct va_list *'
Ok, none of these acpi events are translated by acpi-support into a
battery notification message. Reassigning this report to gnome-power-
manager.
** Package changed: acpi-support (Ubuntu) = gnome-power-manager
(Ubuntu)
** Changed in: gnome-power-manager (Ubuntu)
Status: Incomplete = New
Accepted into lucid-proposed, the package will build now and be
available in a few hours. Please test and give feedback here. See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed. Thank you in advance!
** Tags added: verification-needed
--
gedit
Accepted into lucid-proposed, the package will build now and be
available in a few hours. Please test and give feedback here. See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed. Thank you in advance!
** Tags added: verification-needed
--
Gedit
Accepted into lucid-proposed, the package will build now and be
available in a few hours. Please test and give feedback here. See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed. Thank you in advance!
** Tags added: verification-needed
--
The SSH
** Package changed: acpi-support (Ubuntu) = gnome-power-manager
(Ubuntu)
--
Screen brightness is not saved
https://bugs.launchpad.net/bugs/601626
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-power-manager in ubuntu.
--
cryptsetup 1.1.2 has been merged into maverick - can anyone confirm this
is fixed there?
--
Plugging in a LUKS device causes the following error: Error unlocking device:
cryptsetup exited with exit code 239: Command failed: Device already exists
https://bugs.launchpad.net/bugs/484429
You
Well, the gdm-2.20 package *was* supposed to be a workaround for this
issue, but was removed from lucid before release because xubuntu was no
longer using it. :/ So we appear not to have a good xdmcp solution for
10.04 users at present.
--
No option to log in remotely via XDMCP
Documented at
https://wiki.ubuntu.com/LucidLynx/ReleaseNotes#GDM%20does%20not%20support%20XDMCP:
The version of gdm included in Ubuntu 10.04 LTS does not support the
XDMCP protocol for remote graphical logins. Users who require XDMCP
support will need to install another display manager, such as
401 - 500 of 1611 matches
Mail list logo
