Would be happy to see your HTML if you email it to me. I'm using Google
Apps too; so, some follow-up questions:
1) What language/country is Google Apps in?
2) What kind of connection are you using? How fast is it?
3) What browser are you using on what hardware?
I wonder if speed of
Stefan's helped me do more debugging and moving the isCorrectPage() call
*inside* the timeout (to mitigate the Gmail dynamic loading) has got it
working for him.
Gmail3.user.patch is a consolidated patch which should work in more
circumstances.
** Patch added: Consolidated patch
*** This bug is a duplicate of bug 1073397 ***
https://bugs.launchpad.net/bugs/1073397
** This bug has been marked a duplicate of bug 1073397
unityLoaded never gets called
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Another patch. This one corrects the XPath to get the correct labels and
ALSO includes three window.alert debug points:
1) Script initialisation
2) When isCorrectPage() returns true
3) After Unity integration has initialised
If the patch still isn't working for you, please record which of these
I've upgraded another machine to Quantal, and despite being asked
whether or not I want to install it; installing it and restarting
Firefox - no Launcher integration for Gmail. Google Calendar and
Launchpad both work fine here too.
--
You received this bug notification because you are a member
Public bug reported:
This is a continuation of bug #1059051 which seems to be resolved for
some but not others.
I'm using 2.4.7 of unity-webapps-gmail in Firefox
16.0.2+build1-0ubuntu0.12.10.1 in Quantal.
As described on bug #1059051, the request to install appears, but
nothing appears in the
I've done some more investigation and opened bug #1073397, since this
one is released.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1059051
Title:
Gmail Webapp doesn't work
To manage
Found it, it's the passing of login which doesn't work. Removing
login from the call to `Unity.init' gets me a launcher icon:
8
Unity.init({ name: GMail,
iconUrl: icon://unity-webapps-gmail,
homepage: 'https://mail.google.com',
Once passed that there are a couple of other issues:
1) `checkMessangesCount()' [sic] doesn't handle the fact that there could be
newlines/whitespace after the Mail (there is in my DOM)
2) The label identification code is completely wrong for my setup.
The attached patch to GMail.user.js
I've attached a patch to bug #1073397 which has got the Gmail
integration working in my Firefox instance. Comments from others
welcome.
No recompilation is necessary since the patch can be made directly to
the JavaScript at /usr/share/unity-webapps/userscripts/unity-webapps-
gmail/GMail.user.js.
The patch's fix to the labels isn't quite right. I'm getting the ones
below the More v fold appear in the messaging menu, rather than the
ones above it. Should be an easy fix, though.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Exactly as described for me with unity-webapps-gmail 2.4.7 and Firefox
16.0.1+build1-0ubuntu1. Other web apps, such as Google Calendar and
Launchpad work fine.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I'm using Google Apps in the UK (e.g. Bin rather than Trash and
n...@gmail.com address); perhaps it's related to bug #1069576 which
deals with the issues with it in Germany.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I've also found that having synergys running causes additional problems
if there is a screen configured to the left.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1057000
Title:
[Ubuntu
Still not working for me. Purged nvidia-.*; installed NVIDIA-
Linux-x86-304.51.run from nvidia.com. Interestingly the xorg.conf it
created has ConstrainCursor in the *screen* section. However, the
launcher doesn't reveal whether it's there, or also in the Device
section.
/var/log/Xorg.0.log
I've now switched to a new NVidia card. Unfortunately that's not without
its share of bugs either (e.g. bug #1057000 and bug #993604).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/968520
Title:
I've had this on every version of the NVidia drivers I've tried. The
window outlines still roughly appear, but the contents are white.
There's a brief display of the correct representation. I can drag the
windows about and the system isn't unresponsive.
However, when I exit from the workspace
I have 304.43-0ubuntu0.1 from precise-proposed and still can't get the
launcher to auto-reveal. nvidia-settings confirms the NVIDIA driver
version is 304.43.
Adding the constrain-cursor option to /etc/X11/xorg.conf had no effect
(though, worryingly, it still had 'Driver intel' rather than
Still failing in 3.6-rc3. Every 5 seconds in X there's a freeze (except
for the mouse pointer), and then re-rendering tainted areas of the
screen is erratic.
dmesg says:
56.148632] [ cut here ]
[ 56.148660] WARNING: at
Any ideas on further things I could try?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/968520
Title:
i915 GPU hang with WARNING: at
/build/buildd/linux-3.2.0/drivers/gpu/drm/i915/i915_drv.c:413
** Changed in: linux (Ubuntu)
Status: Incomplete = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/968520
Title:
i915 GPU hang with WARNING: at
3.5 seems as bad as 3.4 - lots of weird graphical effects and glitches.
Attached the full dmesg output: lots of problems listed.
** Attachment added: dmesg-3.5.txt
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/968520/+attachment/3215934/+files/dmesg-3.5.txt
--
You received this bug
Within a few minutes of using 3.2-rc6, the screen flickered black and
back exactly as it does when the problem occurs; it was then immediately
followed by the full machine hang I saw with 3.2-rc5.
So, IMHO the problems possibly started with the GPU hang in
3.2-rc4-oneiric, turned into a full
With 3.2-rc5-precise I get a full machine lockup (doesn't respond to
pings, mouse doesn't move, can't switch to console) after some period of
usage (first time was after ~1h, second time after ~5m)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
3.2-rc3 doesn't have any precompiled packages, just the headers:
http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.2-rc3-oneiric/
Installing 3.2-rc4-oneiric now. Previous testing showed 3.2-rc4-precise
to be OK (IIRC)
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Using 3.2-rc4-oneiric gave a different problem. Unlike the immediate and
frequent screen blanks/X reinitialisations, X hung. dmesg showed a GPU
hang. Attached the stack in gpu-hang.txt.
** Attachment added: i915 dmesg log with 3.2-rc4-oneiric
Will do (3.2-rc5-precise, right? Is there any difference between the
-oneiric -precise versions?)
It's also worth noting I'm using the -pae versions where available.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Given bug 806255 was High and the use of super alt keys in
VMs/Synergy is quite popular; shouldn't this be higher than Medium?!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/741869
Title:
v3.1.10-precise: fine
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/968520
Title:
i915 GPU hang with WARNING: at
/build/buildd/linux-3.2.0/drivers/gpu/drm/i915/i915_drv.c:413
v3.2-rc2-oneiric: also fine, but there's no PAE version of that
available so it's not an exactly equivalent test.
However, uname output from versions which *are* affected:
* 3.2.0-23-generic-pae #36-Ubuntu
* 3.2.0-24-generic-pae #38-Ubuntu
--
You received this bug notification because you
I've been doing a bisection and it _seems_ 3.1.x is fine, but 3.2.x
onwards isn't. I've not yet tried all of them to narrow down further
where the regression occurred.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
@Joseph, sure - no problem. Interestingly, although the Oneiric kernel
seems fine, apport-gpu-intel.py keeps popping up after booting. It
doesn't seem to properly succeed, though, so maybe it's picking up
previous indicators somehow (no idea how it works)
--
You received this bug notification
I'm seeing very similar issues, with a similar stack in dmesg in
3.2.0-24-generic-pae in X (from linux-image-3.2.0.24-generic-
pae/3.2.0-24.37)
Manifests itself as X going black for a second or two before redispaying
the desktop, unreliable input after it comes back and general flakiness.
The 3.4.0 rc didn't help. i915.i915_enable_rc6=0 caused an oops with
3.4.x (in NFS, so possibly unrelated) whereas it seems to have helped
with graphics stability in 3.2.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: linux-image-3.2.0-24-generic-pae_3.2.0-24.37.dmesg
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/968520/+attachment/3104986/+files/linux-image-3.2.0-24-generic-pae_3.2.0-24.37.dmesg
--
You received this bug notification because you are a member of Ubuntu
Bugs,
** Attachment added:
linux-image-3.4.0-030400rc4-generic-pae_3.4.0-030400rc4.201204230908.dmesg
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/968520/+attachment/3104987/+files/linux-image-3.4.0-030400rc4-generic-pae_3.4.0-030400rc4.201204230908.dmesg
** Changed in: linux (Ubuntu)
@jsalisbury, yes - boot with either the 3.2.x or 3.4.x kernels: log in
using Unity 3D; start Chrome, Firefox and a Terminal; use for a few
minutes.
Going back to a 3.0.x (3.0.0-19-generic-pae) kernel seems to be fine.
--
You received this bug notification because you are a member of Ubuntu
Relevant thread: http://ubuntuforums.org/showthread.php?t=1307577
ACPI seems to be reporting the state correctly:
and...@eve:~$ cat /proc/acpi/battery/BAT1/state
present: yes
capacity state: ok
charging state: discharging
present rate:810 mA
The proposed updates do, indeed, stop the keyboard going into laptop
mode when the numlock/clear key is pressed.
It's still sub-optimal, though:
* The function keys only work when 'fn' is held down. The pb_fnmode value
change corrects this, but this *should* be the default: without 'fn' held
This isn't a normal PC keyboard and we shouldn't try to make it one.
As has been pointed out above, though: the primary OS for this keyboard
is OS X. Apps for OS X use function keys a *lot* less than Linux apps in
terms of keyboard shortcuts etc. This is argument #1 - from a user-
centred design
Can confirm the patch above does at least result in music from Rhythmbox
and sound from Totem coming out of a Windows PulseAudio server. This may
not mean it's the right patch, though - but WORKSFORME.
--
Gstreamer with Pulseaudio on Network : no Sound
https://bugs.launchpad.net/bugs/211016
You
A slightly neater way, rather than modifying root_locale is to add a new
root_opts file:
1) Create /usr/share/initramfs-tools/conf.d/root_opts containing export
ROOTFLAGS [ this is the root cause of step 2 not working alone]
2) Append rootflags=gid=115,fmask=113,dmask=002 to the end of the
Frédéric is creating links between the multiple issues. There's also
some strong arguments in
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/201887 for why the
current default behaviour is wrong.
I wrote there, in support of the same arguments eloquently made by
Tommy, Luke, Nicolas and
@Frédéric Grosshans:
It's a mis-feature at best. Ubuntu isn't OS X, and Apple sell these
keyboards as any other keyboard manufacturer. They are Apple keyboards,
not Mac keyboards; therefore trying to enforce they work like Macs -
when they might well not be being used on Mac hardware, and
An addendum: the patch works for me.
--
eject -T doesn't close the tray
https://bugs.launchpad.net/bugs/91873
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
See also #91873 for a patch to ignore the tray open error when trying
to close the tray.
--
Apple media keyboard eject key only opens cd tray, doesn't close it
https://bugs.launchpad.net/bugs/37785
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct
This isn't just a Mac issue, I see the same behaviour on X86_64 (Linux
serenity 2.6.20-16-generic #2 SMP Thu Aug 30 23:16:15 UTC 2007 x86_64
GNU/Linux)
[EMAIL PROTECTED]:~$ eject -v -T
eject: using default device `cdrom'
eject: device name is `cdrom'
eject: expanded name is `/dev/cdrom'
eject:
This also affects non-Apple hardware using an eject key.
gnome-volume-manager no longer (in Feisty) supports the eject_command
key, and gnome-mount is hardcoded to use eject. However, it doesn't
specify a path.
Therefore a workaround is to have an executable shell script in your
path ahead of
48 matches
Mail list logo
