[Bug 669301] Re: After upgrade to 10.10 rhythmbox no longer minimises to system tray and prevents mouse buttons from working
*** This bug is a duplicate of bug 636311 *** https://bugs.launchpad.net/bugs/636311 Did some digging. The correct duplicate bug is #636311. I have updated the details. ** This bug is no longer a duplicate of bug 658590 Rhythmbox will not minimize to sound-indicator if music is not playing ** This bug has been marked a duplicate of bug 636311 Keyboard special keys interfere with mouse * You can subscribe to bug 636311 by following this link: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-evdev/+bug/636311/+subscribe -- After upgrade to 10.10 rhythmbox no longer minimises to system tray and prevents mouse buttons from working https://bugs.launchpad.net/bugs/669301 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to rhythmbox in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 669301] Re: After upgrade to 10.10 rhythmbox no longer minimises to system tray and prevents mouse buttons from working
*** This bug is a duplicate of bug 658590 *** https://bugs.launchpad.net/bugs/658590 Actually, I don't think this is a duplicate. The other bug (658950) is related to the change in the way rhythmbox minimises. If you look at my comments I am fine with that part (once I found out where to look for it) but the real problem is that when running minimised, Rhythmbox still seems to swallow left mouse clicks and prevent me from using the left mouse button. This behaviour is not documented in 658950. It may well be a duplicate of another bug but not 658950. -- After upgrade to 10.10 rhythmbox no longer minimises to system tray and prevents mouse buttons from working https://bugs.launchpad.net/bugs/669301 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to rhythmbox in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 669301] [NEW] After upgrade to 10.10 rhythmbox no longer minimises to system tray and prevents mouse buttons from working
Public bug reported: Binary package hint: rhythmbox After upgrading to 10.10, closing rhythmbox no longer causes it to minimise to the tray. It is still playing but there is no notification anywhere. While in this state the left mouse button stops responding. The cursor moves but clicking the left button anywhere has no effect. Keyboard is unaffected. Icons will highlight when the cursor is over them and tooltips work but left mouse clicks will not work. All I can guess is that somewhere rhythmbox is still capturing all the left mouse click events. This only seems to occur after I have closed rhythmbox to try to minimise to the tray. If I just leave it open it seems to work fine. Once in this state, killing rhythmbox does not bring the mouse back (ctrl-alt-f1 to bring up the console and the kill command) . I have to reboot. ProblemType: Bug DistroRelease: Ubuntu 10.10 Package: rhythmbox 0.13.1-0ubuntu5 ProcVersionSignature: Ubuntu 2.6.35-22.35-generic 2.6.35.4 Uname: Linux 2.6.35-22-generic x86_64 Architecture: amd64 Date: Mon Nov 1 14:12:51 2010 ExecutablePath: /usr/bin/rhythmbox InstallationMedia: Ubuntu 10.04 LTS Lucid Lynx - Release amd64 (20100429) ProcEnviron: LANG=en_AU.utf8 SHELL=/bin/bash SourcePackage: rhythmbox ** Affects: rhythmbox (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug maverick -- After upgrade to 10.10 rhythmbox no longer minimises to system tray and prevents mouse buttons from working https://bugs.launchpad.net/bugs/669301 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to rhythmbox in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 669301] Re: After upgrade to 10.10 rhythmbox no longer minimises to system tray and prevents mouse buttons from working
-- After upgrade to 10.10 rhythmbox no longer minimises to system tray and prevents mouse buttons from working https://bugs.launchpad.net/bugs/669301 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to rhythmbox in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 669301] Re: After upgrade to 10.10 rhythmbox no longer minimises to system tray and prevents mouse buttons from working
OK. I found out that rhythmbox is now inside the sound menu. Nevertheless, hit the play button (in the main gui or in the sound menu) and that's the last left click I can make. After that the left button becomes totally unresponsive. I just discovered that unplugging and re-plugging the mouse brings it back. At least I don't need to reboot. -- After upgrade to 10.10 rhythmbox no longer minimises to system tray and prevents mouse buttons from working https://bugs.launchpad.net/bugs/669301 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to rhythmbox in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 377564] Re: Color palette : Bad choice !
This issue is still present in maverick beta: gnome-terminal: Installed: 2.31.91-0ubuntu1 -- Color palette : Bad choice ! https://bugs.launchpad.net/bugs/377564 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.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 377564] Re: Color palette : Bad choice !
Additional note here: It appears that for all the actual predefined colour schemes, black is black. Black isn't black however for the default colour scheme set up when a new user account is created. To observe, remove ~/.gconf/apps/gnome-terminal, log out and in again. -- Color palette : Bad choice ! https://bugs.launchpad.net/bugs/377564 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.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 550825] Re: Recommend a grace timeout between blanking and locking the screen
Note that the problem still exists in the lucid release (2.30.0-0ubuntu1) -- Recommend a grace timeout between blanking and locking the screen https://bugs.launchpad.net/bugs/550825 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-screensaver in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 377564] Re: Color palette : Bad choice !
I've never seen this fixed, and it still happens in lucid. Fullscreen programs such as aptitude still get that washed-out look. (Observed on the armel UNE image) ** Changed in: gnome-terminal (Ubuntu) Status: Fix Released = Confirmed -- Color palette : Bad choice ! https://bugs.launchpad.net/bugs/377564 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.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 550825] [NEW] Recommend a grace timeout between blanking and locking the screen
Public bug reported: Binary package hint: gnome-screensaver On armel, the screensaver is not shown by default and instead the screen locks immediately when gnome-screensaver's timeout fires. This means that you get no chance to avoid entering your password, whereas if the screensaver were to be shown you would be able to press a key or wiggle the mouse to avoid the screen locking. This is especially annoying if it occurs during passive activities such as reading a document or web page for example. For the armel default configuration, it could make sense to blank the screen for a short period before locking it so the user has a chance to respond. I don't know to what extent this applies to other architectures. ** Affects: gnome-screensaver (Ubuntu) Importance: Undecided Status: New ** Tags: armel -- Recommend a grace timeout between blanking and locking the screen https://bugs.launchpad.net/bugs/550825 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-screensaver in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
RE: [Bug 550825] Re: Recommend a grace timeout between blanking andlocking the screen
Hi, On armel, the screensaver is not shown by default and instead the screen locks immediately when gnome-screensaver's timeout fires. This is already the case, as the screensaver fades out gradually. Are you not seeing the fade on armel? Was this feature added recently? If it was added in the last few days, there's a chance I haven't picked it up yet. Otherwise, I expect it depends on the graphics driver capabilities. The default graphics driver setup for armel platforms is fbdev, and we run with fancy desktop features turned off for this reason. Fading may fall victim to that (anyway, the tearing doesn't look good when fading a software framebuffer, not to mention that we don't really want a power and CPU load spike when the platform is nominally idle...) Would it be feasible to insert, say, a 10-15 second blanking delay in between the fade-out (if present) and locking? This need not be applied when the user explicitly requests that the display be locked. Cheers ---Dave -- Recommend a grace timeout between blanking and locking the screen https://bugs.launchpad.net/bugs/550825 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-screensaver in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 550825] Re: Recommend a grace timeout between blanking and locking the screen
That might work. Is there an easy way I can try that out? -- Recommend a grace timeout between blanking and locking the screen https://bugs.launchpad.net/bugs/550825 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-screensaver in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 524532] [NEW] Whole gnome-terminal window flashes whenever the window title changes
Public bug reported: Binary package hint: gnome-terminal Ubuntu lucid gnome-terminal 2.29.6-0ubuntu1 Architecture: armel (imx51); probably applies to other arches too? The effect may be an inappropriately used visual bell, or more probably something else. An infuriating side-effect is that the whole window flashes black every time I change directory. Fiddling with escape sequences, the flash happens if either of the following sequence specified a different title from the current one: ESC ] 0 ; title BEL ESC ] 2 ; title BEL Note that the XTerm icon name change sequence (ESC ] 1 ; title BEL) doesn't cause the flash even if title is different. ** Affects: gnome-terminal (Ubuntu) Importance: Undecided Status: New -- Whole gnome-terminal window flashes whenever the window title changes https://bugs.launchpad.net/bugs/524532 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-terminal in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 491872] Re: [armel] Atomic intrinsics are not implemented correctly
FIx confirmed in fixed in 4.4.2-5ubuntu1 -- [armel] Atomic intrinsics are not implemented correctly https://bugs.launchpad.net/bugs/491872 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to glib2.0 in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 491872] Re: [armel] Atomic intrinsics are not implemented correctly
Thanks! -- [armel] Atomic intrinsics are not implemented correctly https://bugs.launchpad.net/bugs/491872 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to glib2.0 in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 491872] Re: [armel] Atomic intrinsics are not implemented correctly
** Changed in: gcc-4.4 (Ubuntu) Status: Fix Released = Confirmed -- [armel] Atomic intrinsics are not implemented correctly https://bugs.launchpad.net/bugs/491872 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to glib2.0 in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 491872] Re: [armel] Atomic intrinsics are not implemented correctly
Unfortunately, the __sync_synchronize() bug appears still to be present in the
updated GCC.
A call to this intrinsic still disappears in the compiler's output.
The __sync_lock_test_and_set() bug may still be present; however it is
also possible that the __sync_synchronize() bug is masking the fix.
$ apt-cache policy gcc-4.4 cpp-4.4
gcc-4.4:
Installed: 4.4.2-3ubuntu2
Candidate: 4.4.2-3ubuntu2
Version table:
*** 4.4.2-3ubuntu2 0
500 http://arm-ports-ubuntu lucid/main Packages
100 /var/lib/dpkg/status
cpp-4.4:
Installed: 4.4.2-3ubuntu2
Candidate: 4.4.2-3ubuntu2
Version table:
*** 4.4.2-3ubuntu2 0
500 http://arm-ports-ubuntu lucid/main Packages
100 /var/lib/dpkg/status
$ echo 'void f(void) { __sync_synchronize(); }' | gcc -S -o- -xc -
.syntax unified
.arch armv7-a
.eabi_attribute 27, 3
.fpu vfpv3-d16
.eabi_attribute 20, 1
.eabi_attribute 21, 1
.eabi_attribute 23, 3
.eabi_attribute 24, 1
.eabi_attribute 25, 1
.eabi_attribute 26, 2
.eabi_attribute 30, 6
.eabi_attribute 18, 4
.thumb
.file
.text
.align 2
.global f
.thumb
.thumb_func
.type f, %function
f:
@ args = 0, pretend = 0, frame = 0
@ frame_needed = 1, uses_anonymous_args = 0
@ link register save eliminated.
push{r7}
add r7, sp, #0
mov sp, r7
pop {r7}
bx lr
.size f, .-f
.ident GCC: (Ubuntu 4.4.2-3ubuntu2) 4.4.2
.section.note.GNU-stack,,%progbits
__sync_lock_test_and_set_* still don't contain a barrier in the right place,
though this may be due to the above bug.
8e04 __sync_lock_test_and_set_4:
8e04: e92d 41f0 stmdb sp!, {r4, r5, r6, r7, r8, lr}
8e08: f640 76c0 movwr6, #4032 ; 0xfc0
8e0c: 4605mov r5, r0
8e0e: 460fmov r7, r1
8e10: f6cf 76ff movtr6, #65535 ; 0x
8e14: 682cldr r4, [r5, #0]
8e16: 4639mov r1, r7
8e18: 462amov r2, r5
8e1a: 4620mov r0, r4
8e1c: 47b0blx r6
8e1e: 2800cmp r0, #0
8e20: d1f8bne.n 8e14 __sync_lock_test_and_set_4+0x10
8e22: 4620mov r0, r4
8e24: e8bd 81f0 ldmia.w sp!, {r4, r5, r6, r7, r8, pc}
--
[armel] Atomic intrinsics are not implemented correctly
https://bugs.launchpad.net/bugs/491872
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to glib2.0 in ubuntu.
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 491872] Re: [armel] Atomic intrinsics are not implemented correctly
-mimplicit-it=thumb does now seem to be passed correctly to the
assembler, though:
$ echo 'void f(void) { asm volatile(moveq r0, #1); }' | gcc -c -o
tmp.o -xc - objdump -d tmp.o
f:
...
4: bf08it eq
6: 2001moveq r0, #1
--
[armel] Atomic intrinsics are not implemented correctly
https://bugs.launchpad.net/bugs/491872
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to glib2.0 in ubuntu.
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 491342] Re: assembly fails to build on armel/lucid
Thanks for this. My build failed, but I think this may be due to some autoconf version mismatch or similar, or incorrect versions of some build dependency. However, a .so was build successfully and looks correct (notwithstanding the missing __sync_synchronize() calls resulting from https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/491872) /bin/bash: line 20: @GTKDOC_REBASE@: command not found make[6]: *** [install-data-local] Error 127 make[6]: Leaving directory `/home/ubuntu/src/glib2.0/glib2.0-2.23.0/debian/build/deb/docs/reference/glib' Unless someone else gets the same problem, this doesn't look like it's related in any way to my changes. -- assembly fails to build on armel/lucid https://bugs.launchpad.net/bugs/491342 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to glib2.0 in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 491342] Re: assembly fails to build on armel/lucid
I got a good build, but it's not quite right... the __sync_synchronize() calls compile away to nothing, which is not what's intended. For now, the package builds and should run fine on uniprocessor platforms, so this should unblock you, but I'll provide an additional patch shortly once I've worked out what the problem is... In the meantime, can you disassemble debian/build/deb/glibc/gatomic.o (if you still have the build tree), and double-check check whether there is a call to __sync_val_compare_and_swap_4 in atomic_spin_lock ? This will confirm that configure is working correctly. You should also see the following if things worked correctly: build log: checking whether to use assembler code for atomic operations... arm checking whether GCC supports atomic intrinsics... yes debian/build/gdeb/config.h #define G_ATOMIC_ARM_USE_GCC_INTRINSICS 1 -- assembly fails to build on armel/lucid https://bugs.launchpad.net/bugs/491342 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to glib2.0 in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 491872] [NEW] [armel] Atomic intrinsics are not implemented correctly
Public bug reported: Binary package hint: gcc-4.4 Observed in gcc 4.4.2-3ubuntu1 Believed to affect all versions __sync_synchronnize() should perform a memory barrier, but is a noop (at least with -O2) __sync_lock_release() should place a memory barrier before the compare-exchange operation, but actually puts the barrier after, which may cause unsafe spinlock release Implications: packages built with unfixed gcc which use these intrinsics may not be multicore-safe on armel. Upstream bug link and further information to follow shortly, when available. ** Affects: gcc-4.4 (Ubuntu) Importance: Undecided Status: New ** Affects: glib2.0 (Ubuntu) Importance: Undecided Status: New ** Tags: armel armv7 ** Also affects: glib2.0 (Ubuntu) Importance: Undecided Status: New -- [armel] Atomic intrinsics are not implemented correctly https://bugs.launchpad.net/bugs/491872 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to glib2.0 in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 491342] Re: assembly fails to build on armel/lucid
** Description changed: latest glib upload failed to build in lucid: 12:52 asac https://edge.launchpad.net/ubuntu/+source/glib2.0/2.23.0-1ubuntu1/+build/1374402 - 12:53 asac libtool: compile: gcc -DHAVE_CONFIG_H -I. -I/build/buildd/glib2.0-2.23.0/glib -I.. -I/build/buildd/glib2.0-2.23.0 -DG_LOG_DOMAIN=\GLib\ -DG_ENABLE_DEBUG - -DG_DISABLE_DEPRECATED -DGLIB_COMPILATION -DPCRE_STATIC -DG_DISABLE_SINGLE_INCLUDES -pthread -g -O2 -Wall -g -O2 -MT gatomic.lo -MD -MP -MF - .deps/gatomic.Tpo -c /build/buildd/glib2.0-2.23.0/glib/gatomic.c -fPIC -DPIC -o .libs/gatomic.o + 12:53 asac libtool: compile: gcc -DHAVE_CONFIG_H -I. -I/build/buildd/glib2.0-2.23.0/glib -I.. -I/build/buildd/glib2.0-2.23.0 -DG_LOG_DOMAIN=\GLib\ -DG_ENABLE_DEBUG + -DG_DISABLE_DEPRECATED -DGLIB_COMPILATION -DPCRE_STATIC -DG_DISABLE_SINGLE_INCLUDES -pthread -g -O2 -Wall -g -O2 -MT gatomic.lo -MD -MP -MF + .deps/gatomic.Tpo -c /build/buildd/glib2.0-2.23.0/glib/gatomic.c -fPIC -DPIC -o .libs/gatomic.o 12:53 asac /tmp/cc7twNnB.s: Assembler messages: 12:53 asac /tmp/cc7twNnB.s:161: Error: selected processor does not support `swp r3,r5,[r4]' 12:53 asac /tmp/cc7twNnB.s:179: Error: selected processor does not support `swp r3,r5,[r4]' + + *** Note: this package requires a rebuild when + https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/491872 is + resolved *** -- assembly fails to build on armel/lucid https://bugs.launchpad.net/bugs/491342 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to glib2.0 in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 491872] Re: [armel] Atomic intrinsics are not implemented correctly
I expect to be able to post a patch soon; it may be simplest to leave this unfixed until then. -- [armel] Atomic intrinsics are not implemented correctly https://bugs.launchpad.net/bugs/491872 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to glib2.0 in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 491872] Re: [armel] Atomic intrinsics are not implemented correctly
This patch should fix the issue with __sync_lock_release(): http://gcc.gnu.org/ml/gcc-patches/2009-12/msg00198.html The __sync_synchronize() is not fixed by this— another patch should follow soon. -- [armel] Atomic intrinsics are not implemented correctly https://bugs.launchpad.net/bugs/491872 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to glib2.0 in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 491872] Re: [armel] Atomic intrinsics are not implemented correctly
This patch should fix the __sync_synchronize() issue, by making sure GCC does not optimise away the call to the libgcc function which implements this: http://gcc.gnu.org/ml/gcc-patches/2009-08/msg00600.html These should now be fixed on the GCC trunk and await backporting to the upstream 4.4 branch. I've referenced the relevant GCC bugzilla entry from this bug. ** Bug watch added: GCC Bugzilla #42263 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42263 ** Also affects: gcc via http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42263 Importance: Unknown Status: Unknown -- [armel] Atomic intrinsics are not implemented correctly https://bugs.launchpad.net/bugs/491872 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to glib2.0 in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 491342] Re: assembly fails to build on armel/lucid
This patch converts to a cleaner and slightly more efficient implementation, avoiding the need for the explcit __sync_synchronize() in atomic_spinlock_release() This patch should apply on top of the patch stack in debian/patches, assuming that patch attached above has already been merged. Note that autoconf will need to be run again before pushing the source package update, since configure.in is updated. My test build hasn't finished yet, but it seems to be going OK. ** Attachment added: convert the spinlock to use the more appropriate __sync_lock_test_and_set() and __sync_lock_release() functions, and make configure checks more rigorous http://launchpadlibrarian.net/36395782/glib2.0-gatomic-arm-2.diff -- assembly fails to build on armel/lucid https://bugs.launchpad.net/bugs/491342 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to glib2.0 in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 491342] Re: assembly fails to build on armel/lucid
** Tags added: armel armv7 -- assembly fails to build on armel/lucid https://bugs.launchpad.net/bugs/491342 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to glib2.0 in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 491342] Re: assembly fails to build on armel/lucid
[Added the armv7 tag to help track ARMv7 migration issues.] Agreed, the best way to solve cases like this is to use the GCC intrinsics instead of inline asm. The attached patch should hopefully work for this; but I haven't been able to build or test it just yet. I've tried to modify configure to check for support for the intrinsics in GCC, by doing a link test on a call to __sync_synchronize(). Assuming the support is there, this uses some code in glib/qatomic.c which uses the intrinsics instead of inline asm -- this results in a simpler implementation. I've also turned on memory barriers to make sure that the code is SMP- safe. Conveniently, the support for this was already in there; I just needed to define how to do a memory barrier and set the appropriate variable in configure. Note: 1) The GCC atomic intrinsics require linux-2.6.13 or higher. This is no problem for Ubuntu, but upstream people using old kernels may get problems, so we might want an extra configure argument to turn on my modifications, and pass it from the build rules. 2) People using old compilers won't get the benefits, and will fall back to the SWP-based code. Again, this is not a problem for Ubuntu, but may affect upstream people using older tools. If this is seen as an issue we could include some inline asm which reproduces the intrinsics' behaviour as an additional fallback, if building for -march=armv6 or above (for older architectures, SWP is the right way since nothing else existed there). ** Attachment added: (untested) patch to implement splinlock lock and unlock for glib2.0 using GCC atomic intrinsics on armel http://launchpadlibrarian.net/36338207/glib2.0-gatomic-arm.diff -- assembly fails to build on armel/lucid https://bugs.launchpad.net/bugs/491342 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to glib2.0 in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 462724] Re: Installed user's keyboard doesn't match that chosen during installation of Karmic?
$ grep ^X /etc/default/console-setup XKBMODEL=pc105 XKBLAYOUT=gb XKBVARIANT= XKBOPTIONS= This does not ever seem to change, even when the bug occurs and US keyboard layout is used. Basically, the bug seems to persist from installation until the default user logs in explicitly (not using gdm auto-login) or sets the keyboard layout explicitly. If I destroy and manually recreate the default user by copying /etc/default/skel and deleting /var/cache/gdm/user, the problem does not seem to recur. Maybe it is the way the default user account is configured during installation which is causing the problem. -- Installed user's keyboard doesn't match that chosen during installation of Karmic? https://bugs.launchpad.net/bugs/462724 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 462724] Re: Installed user's keyboard doesn't match that chosen during installation of Karmic?
This is using auto-login. I didn't select anything explicitly, so I was expecting the system default to be used. Maybe there is something wrong with the initial user's preferences are initialised during installation? I currently have a reinstall under way; I'll try to answer the other points when that's done. -- Installed user's keyboard doesn't match that chosen during installation of Karmic? https://bugs.launchpad.net/bugs/462724 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 462724] Re: Installed user's keyboard doesn't match that chosen during installation of Karmic?
When logging in explicitly though GDM on the first boot after installation, the keyboard layout option at the login screen defaults correctly to UK, and I get UK keyboard layout after login. If I then restart gdm so that auto-login happens again, I get UK layout in the desktop session again, so it looks like once the setting is established, it persists. If I remove /var/cache/gdm/yourusername/dmrc and ~/.dmrc, then auto- login again, the layout is US once more. No ~.dmrc appears to be created. -- Installed user's keyboard doesn't match that chosen during installation of Karmic? https://bugs.launchpad.net/bugs/462724 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 461912] Re: gnome-panel crashed with SIGSEGV in gdk_window_impl_x11_get_colormap()
Unfortunately, Valgrind is not available for armel at this time. -- gnome-panel crashed with SIGSEGV in gdk_window_impl_x11_get_colormap() https://bugs.launchpad.net/bugs/461912 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.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 458109] Re: gnome-panel crashed with SIGSEGV in free()
I now have a backtrace for a similar case. See: https://bugs.launchpad.net/ubuntu/+source/gnome-panel/+bug/461912 (gnome-panel crashed with SIGSEGV in gdk_window_impl_x11_get_colormap()) -- gnome-panel crashed with SIGSEGV in free() https://bugs.launchpad.net/bugs/458109 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.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 461912] Re: gnome-panel crashed with SIGSEGV in gdk_window_impl_x11_get_colormap()
** Visibility changed to: Public -- gnome-panel crashed with SIGSEGV in gdk_window_impl_x11_get_colormap() https://bugs.launchpad.net/bugs/461912 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-panel in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 461912] Re: gnome-panel crashed with SIGSEGV in gdk_window_impl_x11_get_colormap()
The panel disappears for a moment and then respawns. No specific action appears to be required to provoke the bug, but if it happens at all it happens shortly after login, when the system may still be thrashing starting up applets etc. The problem has maybe happened to be 3-4 times during the Karmic release cycle, so it might be fair to say it affects about 2-4% of logins. It won't necessarily happen reliably on a system when it occurred (for instance, I saw this in a live session, but after shutting down and starting another live session from the same image, I didn't see the problem a second time). -- gnome-panel crashed with SIGSEGV in gdk_window_impl_x11_get_colormap() https://bugs.launchpad.net/bugs/461912 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-panel in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 458109] Re: gnome-panel crashed with SIGSEGV in free()
Looks like there is a gnome-panel-dbg package in main after all. I've grabbed this, but I can't promise quick feedback --- I don't know how to provoke the error... -- gnome-panel crashed with SIGSEGV in free() https://bugs.launchpad.net/bugs/458109 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.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 458109] Re: gnome-panel crashed with SIGSEGV in free()
Valgrind is not available for armel. Is there another way to get useful extra debugging information? -- gnome-panel crashed with SIGSEGV in free() https://bugs.launchpad.net/bugs/458109 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.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 458109] Re: gnome-panel crashed with SIGSEGV in free()
There seems to be no ddeb for gnome-panel for armel either. The most recent armel ddeb seems to be for gnome-panel 2.26.0-0ubuntu7 (at http://ddebs.ubuntu.com/pool/main/g/gnome-panel/gnome-panel- dbgsym_2.26.0-0ubuntu7_armel.ddeb), and is absent from the package lists. Is is possible that an up-to-date ddeb is just not on the server yet, or could something have gone wrong when the package was built? -- gnome-panel crashed with SIGSEGV in free() https://bugs.launchpad.net/bugs/458109 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.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 451285] [NEW] If pam policy requires the default user's password to be changed, gdm hangs, never reaching a login box or the desktop
Public bug reported: Binary package hint: gdm If pam policy requires the default user's password to be changed when gdm starts up, gdm hangs... never reaching a login box or the desktop This issue was observed in http://cdimages.ubuntu.com/ports/daily- live/20091014/karmic-desktop-armel+imx51.img, when installing via ubiquity --debug and when the password entered for the default user in ubiquity does not meet PAM's password security requirements, but I'm guessing the problem is not restricted to this particular set of circumstances. The problem can be provoked on an installed system by setting the password last changed time field in /etc/shadow for the default user to 0, configuring gdm to auto-login (if it wasn't so configured before) and restarting gdm. From experience on a previous daily-live image, I believe there may also be problems even if gdm is not configured to auto-login. ProblemType: Bug Architecture: armel Date: Wed Oct 14 14:54:52 2009 DistroRelease: Ubuntu 9.10 InstallationMedia: Ubuntu 9.10 Karmic Koala - Alpha armel+imx51 (20091014) Package: gdm 2.28.0-0ubuntu14 ProcEnviron: LANG=en_GB.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.31-103.11-imx51 SourcePackage: gdm Uname: Linux 2.6.31-103-imx51 armv7l XsessionErrors: (gnome-settings-daemon:2267): GLib-CRITICAL **: g_propagate_error: assertion `src != NULL' failed (gnome-settings-daemon:2267): GLib-CRITICAL **: g_propagate_error: assertion `src != NULL' failed (nautilus:2320): Eel-CRITICAL **: eel_preferences_get_boolean: assertion `preferences_is_initialized ()' failed (polkit-gnome-authentication-agent-1:2342): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed ** Affects: gdm (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug armel -- If pam policy requires the default user's password to be changed, gdm hangs, never reaching a login box or the desktop https://bugs.launchpad.net/bugs/451285 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 451285] Re: If pam policy requires the default user's password to be changed, gdm hangs, never reaching a login box or the desktop
** Attachment added: Dependencies.txt http://launchpadlibrarian.net/33654515/Dependencies.txt -- If pam policy requires the default user's password to be changed, gdm hangs, never reaching a login box or the desktop https://bugs.launchpad.net/bugs/451285 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 390591] [NEW] f-spot seems wrongly packaged / unusable for armel
Public bug reported: Binary package hint: f-spot Installing f-spot on armel installs a load of Win32 PE executables (.exe, .dll) and seems to rely on executing these to work. dpkg prints out a load of illegal instruction errors when trying to configure the package, but the package is erroneously marked as successfully configured after installation. It looks like f-spot and related packages (*mono* etc.) should not be packaged for armel at all, or ARM-targeted binaries need to be built (if this is supported by the source packages; apparently, mono can support ARM but I don't have much experience of these packages). The affected binary packages seem to be: f-spot libart2.24-cil libflickrnet2.1.5-cil libgconf2.24-cil libglade2.0-cil libglib2.0-cil libgnome2.24-cil libgnome-keyring1.0-cil libgnome-vfs2.24-cil libgtk2.0-cil libmono2.0-cil libmono-addins0.2-cil libmono-addins-gui0.2-cil libmono-cairo2.0-cil libmono-corlib2.0-cil libmono-data2.0-cil libmono-data-tds2.0-cil libmono-getoptions2.0-cil libmono-i18n2.0-cil libmono-posix2.0-cil libmono-security2.0-cil libmono-sharpzip2.84-cil libmono-sqlite2.0-cil libmono-system2.0-cil libmono-system-data2.0-cil libmono-system-web2.0-cil libndesk-dbus1.0-cil libndesk-dbus-glib1.0-cil mono-2.0-gac ** Affects: f-spot (Ubuntu) Importance: Undecided Status: New ** Tags: armel -- 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 subscribed to f-spot in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 390591] Re: f-spot seems wrongly packaged / unusable for armel
Note: the above issue applies to the following source package versions, on Jaunty: f-spot 0.5.0.3-1ubuntu6 mono 2.0.1-4 I haven't investigated whether Karmic is affected. -- 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 subscribed to f-spot in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 390179] Re: RTL is printed in reverse
*** This bug is a duplicate of bug 390591 *** https://bugs.launchpad.net/bugs/390591 This bug seems totally unrelated to https://bugs.launchpad.net/bugs/390591 (which is about an architecture/build problem in f-spot/mono and has nothing to do with text rendering). Should the duplicate status be removed? -- RTL is printed in reverse https://bugs.launchpad.net/bugs/390179 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-terminal in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
RE: [Bug 390591] Re: f-spot seems wrongly packaged / unusable for armel
David: Its not clear if you've not used mono or C# before, I haven't. but mono uses the PE format for its executables, but instead of using i386 or other assembly code, its CIL byte code. Wikipedia has a fairly good writeup of how .NET (and thus mono) applications work http://en.wikipedia.org/wiki/.NET_Framework. I realize its confusing to see .exec and .dlls on a Linux system, but rest assured that this is proper and expected behavior. Thanks for the clarification --- this explains a lot. I'll take a look! I will try to post some more detailed symptom information when I have it. -- IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you. -- 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 subscribed to f-spot in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
