Closed
Bug 713834
Opened 13 years ago
Closed 13 years ago
TB 8 (on GTK 2.10 system) not updating on release update channel, but the same version (9) is available to download at getthunderbird.com and system requirements still allow GTK 2.10
Categories
(Mozilla Messaging Graveyard :: Release Engineering, defect)
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: frenando.alonso, Unassigned)
Details
Attachments
(1 file)
|
102.25 KB,
image/png
|
Details |
User Agent: Mozilla/5.0 (X11; Linux i686 on x86_64; rv:9.0.1) Gecko/20100101 Firefox/9.0.1
Build ID: 20111220165912
Steps to reproduce:
I check for updates starting from "about Mozilla TB" on a linux box
Actual results:
Get the message, TB is up to date. This has happened also with previous releases
Expected results:
Show that version 9 is available
Comment 1•13 years ago
|
||
(In reply to frenando.alonso from comment #0)
But the version you have appears to be up-to-date (9.0.1).
| Reporter | ||
Comment 2•13 years ago
|
||
That's FF version, TB is 8.0
I got the update for 9.0.1 on linux.
(It broke the install, but that is another problem.)
Make sure TB is not set to be offline.
| Reporter | ||
Comment 4•13 years ago
|
||
picture of my screen a while ago. running 8.0 and getting "it is up to date"
| Reporter | ||
Comment 5•13 years ago
|
||
(In reply to :aceman from comment #3)
> I got the update for 9.0.1 on linux.
> (It broke the install, but that is another problem.)
>
> Make sure TB is not set to be offline.
no, it's not offline.
Comment 6•13 years ago
|
||
what do you see in Tools -> Error console , when you set app.update.log to true in the config editor.
| Reporter | ||
Comment 7•13 years ago
|
||
It says
Failed to load native module at path '/opt/thunderbird8/thunderbird/components/libmozgnome.so': (80004005) libnotify.so.1: no se puede abrir el fichero del objeto compartido: No existe el fichero o el directorio (translated to something like cannot open shred objetc: file or directory do not exist)
But the files are there
[gaepc17] /opt/thunderbird8/thunderbird > ls -l components/
total 40
-rw-r--r-- 1 root root 67 nov 5 11:55 binary.manifest
-rwxr-xr-x 1 root root 10564 nov 5 11:55 libdbusservice.so
-rwxr-xr-x 1 root root 23656 nov 5 11:55 libmozgnome.so
Try to 'ldd ./libmozgnome.so' (in the terminal) and see if libnotify.so.1 is really missing.
| Reporter | ||
Comment 9•13 years ago
|
||
forgot to say that app.update.log does not appear at all in my about:config
| Reporter | ||
Comment 10•13 years ago
|
||
No, it is not there.
ldd ./libmozgnome.so |grep noti
libnotify.so.1 => not found
BTW, this is a standard installation from mozilla tar
Comment 11•13 years ago
|
||
But libnotify is a system library. Try to look it up in your distribution repository. Or try to find it on your system (/usr/lib) if any older version is installed (not .1 but something else).
Comment 12•13 years ago
|
||
(In reply to frenando.alonso from comment #9)
> forgot to say that app.update.log does not appear at all in my about:config
Add it as a boolean value and set it to 1.
| Reporter | ||
Comment 13•13 years ago
|
||
libnotify was not on my system, I have just installed it. The error disappeared, but the problems subsists.
I also set correctly app.update.log and get this messages when I search for updates:
*** AUS:SVC Checker:getUpdateURL - update URL: https://aus2.mozillamessaging.com/update/3/Thunderbird/8.0/20111105021619/Linux_x86-gcc3/en-US/default/Linux%202.6.18-274.7.1.el5%20(GTK%202.10.4)/default/default/update.xml?force=1
*** AUS:SVC Checker:checkForUpdates - sending request to: https://aus2.mozillamessaging.com/update/3/Thunderbird/8.0/20111105021619/Linux_x86-gcc3/en-US/default/Linux%202.6.18-274.7.1.el5%20(GTK%202.10.4)/default/default/update.xml?force=1
*** AUS:SVC Checker:onLoad - request completed downloading document
*** AUS:SVC Checker:onLoad - number of updates available: 0
*** AUS:SVC UpdateService:removeDownloadListener - no downloader!
Comment 14•13 years ago
|
||
There is something wrong with the string, the server really does not return any updates.
It looks like it has problems with the 'Linux%202.6.18-274.7.1.el5%20(GTK%202.10.4)' system identifier because when I created this nonsense (notice Linux and Windows_NT):
https://aus2.mozillamessaging.com/update/3/Thunderbird/8.0/20111105021619/Linux_x86-gcc3/en-US/release/Windows_NT%205.1.3.0%20%28x86%29/default/default/update.xml?force=1
It returned and 9.0.1 update for Linux fine. Also notice I used /release/, not /default/ after 'en-US'. the 'default' does not seem to work. Have you been messing with the update channel you are on? See what is app.update.channel set to in about:config.
This URL works too:
https://aus2.mozillamessaging.com/update/3/Thunderbird/8.0/20111105021619/Linux_x86-gcc3/en-US/release/Linux/default/default/update.xml?force=1
While this does not:
https://aus2.mozillamessaging.com/update/3/Thunderbird/8.0/20111105021619/Linux_x86-gcc3/en-US/default/Linux/default/default/update.xml?force=1
I'll confirm the bug on the basis that your TB is using a wrong update URL. Why that is the case is left to further analysis.
Status: UNCONFIRMED → NEW
Component: General → Application Update
Ever confirmed: true
Product: Thunderbird → Toolkit
QA Contact: general → application.update
Version: 8 → 8 Branch
Comment 15•13 years ago
|
||
Forgot to note that just fixing 'default' to 'release' in the original URL in comment 13 didn't work alone, that is why I started to change the system version string.
| Reporter | ||
Comment 16•13 years ago
|
||
(In reply to :aceman from comment #14)
> There is something wrong with the string, the server really does not return
> any updates.
>
> It looks like it has problems with the
> 'Linux%202.6.18-274.7.1.el5%20(GTK%202.10.4)' system identifier because when
> I created this nonsense (notice Linux and Windows_NT):
> https://aus2.mozillamessaging.com/update/3/Thunderbird/8.0/20111105021619/
> Linux_x86-gcc3/en-US/release/Windows_NT%205.1.3.0%20%28x86%29/default/
> default/update.xml?force=1
>
> It returned and 9.0.1 update for Linux fine. Also notice I used /release/,
> not /default/ after 'en-US'. the 'default' does not seem to work. Have you
> been messing with the update channel you are on? See what is
> app.update.channel set to in about:config.
>
> This URL works too:
> https://aus2.mozillamessaging.com/update/3/Thunderbird/8.0/20111105021619/
> Linux_x86-gcc3/en-US/release/Linux/default/default/update.xml?force=1
>
> While this does not:
> https://aus2.mozillamessaging.com/update/3/Thunderbird/8.0/20111105021619/
> Linux_x86-gcc3/en-US/default/Linux/default/default/update.xml?force=1
>
> I'll confirm the bug on the basis that your TB is using a wrong update URL.
> Why that is the case is left to further analysis.
Yes I changed to release as one of my first attempts to get the updates and forgot to revert the change. Now I'm on release with the same problem.
*** AUS:SVC UpdateManager:_loadXMLFileIntoArray: XML file does not exist
*** AUS:SVC getLocale - getting locale from file: /opt/thunderbird8/thunderbird/update.locale, locale: en-US
*** AUS:SVC Checker:getUpdateURL - update URL: https://aus2.mozillamessaging.com/update/3/Thunderbird/8.0/20111105021619/Linux_x86-gcc3/en-US/release/Linux%202.6.18-274.7.1.el5%20(GTK%202.10.4)/default/default/update.xml?force=1
*** AUS:SVC gCanCheckForUpdates - able to check for updates
*** AUS:SVC Checker:checkForUpdates - sending request to: https://aus2.mozillamessaging.com/update/3/Thunderbird/8.0/20111105021619/Linux_x86-gcc3/en-US/release/Linux%202.6.18-274.7.1.el5%20(GTK%202.10.4)/default/default/update.xml?force=1
*** AUS:SVC Checker:onLoad - request completed downloading document
*** AUS:SVC Checker:onLoad - number of updates available: 0
*** AUS:SVC UpdateService:removeDownloadListener - no downloader!
[
| Reporter | ||
Comment 17•13 years ago
|
||
Hi,
at least from the browser (don't know how to patch it inside TB) the problem seems to be the blank space between GTK and 2.10.4
this works:
https://aus2.mozillamessaging.com/update/3/Thunderbird/8.0/20111105021619/Linux_x86-gcc3/en-US/release/Linux%202.6.18-274.7.1.el5%20%28GTK2.10.4%29/default/default/update.xml?force=1
Comment 18•13 years ago
|
||
I don't recall the minimum Linux version but that may be what is causing this.
Moving over to AUS since this is likely due to the server not providing an update and not the client code.
Assignee: nobody → morgamic
Component: Application Update → Administration
Product: Toolkit → AUS
QA Contact: application.update → administration
Version: 8 Branch → 3.0
Comment 19•13 years ago
|
||
This is my string:
AUS:SVC Checker:getUpdateURL - update URL: https://aus2.mozillamessaging.com/update/3/Thunderbird/9.0.1/20111222141531/Linux_x86-gcc3/en-US/release/Linux%202.6.41.7%20(GTK%202.24.4)/default/default/update.xml?force=1
It contains the space too and I didn't see any problems yet. I even got update from 9.0 to 9.0.1.
I think I did try to increase the kernel version in URL from comment 13 and it didn't work. GTK 2.10 should also be supported (is in minimum requirements for TB).
Comment 20•13 years ago
|
||
Note this the issue is with aus2.mozillamessaging.com, but lets assume it's set up the same as aus2/aus3.mozilla.org.
The problem will be that GTK 2.10 is no longer supported (bug 666735), due to web-page rendering artefacts using the correspondingly old Freetype on LCD screens. As such updates are not offered to anyone with that version of GTK.
I don't know why Thunderbird 8.0 would be querying with channel=default (see comment #13) other than a vague memory that some builds were created like that by mistake and later corrected.
Assignee: morgamic → nobody
Component: Administration → Release Engineering
Product: AUS → Mozilla Messaging
QA Contact: administration → release
Version: 3.0 → other
Comment 21•13 years ago
|
||
(In reply to Nick Thomas [:nthomas] from comment #20)
> The problem will be that GTK 2.10 is no longer supported (bug 666735), due
> to web-page rendering artefacts using the correspondingly old Freetype on
> LCD screens. As such updates are not offered to anyone with that version of
> GTK.
Then please update
http://www.mozilla.org/en-US/thunderbird/9.0/system-requirements/ and later versions.
> I don't know why Thunderbird 8.0 would be querying with channel=default (see
> comment #13) other than a vague memory that some builds were created like
> that by mistake and later corrected.
I think that the reporter changed the channel in some way and already fixed it in comment 16.
Comment 22•13 years ago
|
||
> Then please update
> http://www.mozilla.org/en-US/thunderbird/9.0/system-requirements/ and later
> versions.
Yes, that's a fair call. It should be done for 7.0* and 8.0* too, since GTK 2.10 is blocked from 7.0 onwards. I'll leave it to someone from Thunderbird who knows the right place to move this there or file a separate bug. Fixing it for Firefox is bug 708103.
Comment 23•13 years ago
|
||
But how comes the reporter is on TB8 and it works for him? Do you only hide the update? But if anybody downloads it manually then TB works fine on that old setup?
Comment 24•13 years ago
|
||
As I said, there are rendering artefacts - specifically text in html. The developers took the option of de-supporting those GTK/Freetype version, and so we don't provide updates. The the builds still run, for now anyway.
Comment 25•13 years ago
|
||
I meant there is now a discrepancy. You allow to download and run a version on old system without any warning. But you do not provide the same version through update channels. That is confusing to users.
That is actually what this bug is about.
Summary: TB not updating on release update channel → TB 8 (on GTK 2.10 system) not updating on release update channel, but the same version (9) is available to download at getthunderbird.com and system requirements still allow GTK 2.10
Comment 26•13 years ago
|
||
So this is either WONTFIX or INVALID.
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → WONTFIX
Comment 27•13 years ago
|
||
Only if you file bugs for the 2 remaining issues found in the discussion.
Status: RESOLVED → REOPENED
Resolution: WONTFIX → ---
Comment 28•13 years ago
|
||
The system requirements issues have been fixed for a while now.
I don't think there is anything we can do here for checking the system requirements limits before download. I guess a bug in websites/www.mozilla.org might suggest something. The fact it still runs should probably be filed as a dependency to the original bug and probably in core somewhere, though I've no idea where.
Status: REOPENED → RESOLVED
Closed: 13 years ago → 13 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•