Bug 523880

I just updated my system tonight and the update broke rednotebook; Same issue. 


$rednotebook
INFO     Writing log to file "/home/Jason/.rednotebook/rednotebook.log"
INFO     Using libyaml for loading and dumping
INFO     AppDir: /usr/lib/python2.6/site-packages/rednotebook
INFO     BaseDir: /usr/lib/python2.6/site-packages
INFO     The config file /usr/lib/python2.6/site-packages/rednotebook/files/default.cfg was read
INFO     The config file /home/Jason/.rednotebook/configuration.cfg was read
INFO     Running in portable mode: 0
INFO     First Start: False
INFO     RedNotebook version: 0.8.6
INFO     System info: machine: i686, platform: Linux-2.6.30.5-43.fc11.i686.PAE-i686-with-fedora-11-Leonidas, processor: i686, python_version: 2.6.0, release: 2.6.30.5-43.fc11.i686.PAE, system: Linux, GTK version: (2, 16, 6), PyGTK version: (2, 14, 1), Yaml version: 3.08,
ERROR    An error occured while loading the GUI: Duplicate object id 'cellrenderertext2' on line 562 (previously on line 162)
ERROR    RedNotebook requires at least gtk+ 2.14. If you cannot update gtk, you might want to try an older version of RedNotebook.

No problems here:

$ rednotebook 
INFO     Writing log to file "/home/chris/.rednotebook/rednotebook.log"
INFO     Using libyaml for loading and dumping
INFO     AppDir: /usr/lib/python2.6/site-packages/rednotebook
INFO     BaseDir: /usr/lib/python2.6/site-packages
INFO     The config file /usr/lib/python2.6/site-packages/rednotebook/files/default.cfg was read
INFO     The config file /home/chris/.rednotebook/configuration.cfg was read
INFO     Running in portable mode: 0
INFO     First Start: False
INFO     RedNotebook version: 0.8.6
INFO     System info: machine: x86_64, platform: Linux-2.6.30.5-43.fc11.x86_64-x86_64-with-fedora-11-Leonidas, processor: x86_64, python_version: 2.6.0, release: 2.6.30.5-43.fc11.x86_64, system: Linux, GTK version: (2, 16, 5), PyGTK version: (2, 14, 1), Yaml version: 3.08, 
INFO     Cloud ignore list: ['comma', 'filter', 'separated', 'these', 'words']
INFO     Opening journal at /home/chris/.rednotebook/data
INFO     Connected Signals: 1 2 3 6 15 20 

I wonder why you guys have gtk 2.16.6 while I still have 2.16.5. I can't see 2.16.6 on my mirrors, but I do see it was pushed two days ago.

What locales are you using?

I am using simplified Chinese. Here is my locales:

$ locale
LANG=zh_CN.UTF-8
LC_CTYPE="zh_CN.UTF-8"
LC_NUMERIC="zh_CN.UTF-8"
LC_TIME="zh_CN.UTF-8"
LC_COLLATE="zh_CN.UTF-8"
LC_MONETARY="zh_CN.UTF-8"
LC_MESSAGES="zh_CN.UTF-8"
LC_PAPER="zh_CN.UTF-8"
LC_NAME="zh_CN.UTF-8"
LC_ADDRESS="zh_CN.UTF-8"
LC_TELEPHONE="zh_CN.UTF-8"
LC_MEASUREMENT="zh_CN.UTF-8"
LC_IDENTIFICATION="zh_CN.UTF-8"
LC_ALL=

Great, thanks. After manually upgrading to 2.16.6 I can reproduce the error and I already fixed it. It was a trivial fix and had nothing to do with the locales.

An update is on it's way. Thanks both of you for your reports.

rednotebook-0.8.6-2.fc11 has been submitted as an update for Fedora 11.
http://admin.fedoraproject.org/updates/rednotebook-0.8.6-2.fc11

Uh, upstream already released 0.8.6.1 with a fix on September 4th, but never announced it.

rednotebook-0.8.6.1-1.fc11 has been submitted as an update for Fedora 11.
http://admin.fedoraproject.org/updates/rednotebook-0.8.6.1-1.fc11

Thanks. I will wait for the update from repo.

rednotebook-0.8.6.1-1.fc11 has been pushed to the Fedora 11 testing repository.  If problems still persist, please make note of it in this bug report.
 If you want to test the update, you can install it with 
 su -c 'yum --enablerepo=updates-testing update rednotebook'.  You can provide feedback for this update here: http://admin.fedoraproject.org/updates/F11/FEDORA-2009-9727

Thanks! The update is applied and Rednotebook is back to normal.

Am I right to close it? Well, I am new to bugzilla, forgive me if I was wrong.

(In reply to comment #11)
> Am I right to close it? Well, I am new to bugzilla, forgive me if I was wrong.  

No problem, Mark. We leave this bug open and the Fedora update system will automatically update it's status and close the bug with the proper resolution once the update is actually in the repos.

Now the proper status would be "ON_QA" because the package was released for testing. When it becomes stable, the bug will be closed ERRATA.

For more info on bugzilla's bug statuses, pls see:
https://bugzilla.redhat.com/page.cgi?id=fields.html#status

Thanks for your help, Christoph! I will check it out.

rednotebook-0.8.6.1-1.fc11 has been pushed to the Fedora 11 stable repository.  If problems still persist, please make note of it in this bug report.

Doesn't seem any better.

$ rpm -q rednotebook
rednotebook-0.8.6-1.fc11.noarch
$ rednotebook
INFO     Writing log to file "/home/jrowens/.rednotebook/rednotebook.log"
INFO     Using libyaml for loading and dumping
INFO     AppDir: /usr/lib/python2.6/site-packages/rednotebook
INFO     BaseDir: /usr/lib/python2.6/site-packages
INFO     The config file /usr/lib/python2.6/site-packages/rednotebook/files/default.cfg was read
INFO     The config file /home/jrowens/.rednotebook/configuration.cfg was read
INFO     Running in portable mode: 0
INFO     First Start: False
INFO     RedNotebook version: 0.8.6
INFO     System info: machine: x86_64, platform: Linux-2.6.30.5-43.fc11.x86_64-x86_64-with-fedora-11-Leonidas, processor: x86_64, python_version: 2.6.0, release: 2.6.30.5-43.fc11.x86_64, system: Linux, GTK version: (2, 16, 6), PyGTK version: (2, 14, 1), Yaml version: 3.08,
ERROR    An error occured while loading the GUI: Duplicate object id 'cellrenderertext2' on line 562 (previously on line 162)
ERROR    RedNotebook requires at least gtk+ 2.14. If you cannot update gtk, you might want to try an older version of RedNotebook.
Exit 1

(In reply to comment #15)
> Doesn't seem any better.
> 
> $ rpm -q rednotebook
> rednotebook-0.8.6-1.fc11.noarch

This is still the old version, please note the difference between
0.8.6-1 and
0.8.6.1-1

Please wait another day until the update has reached all mirrors and reopen the bug, if you can still reproduce it with 0.8.6.1-1.

Yes, as soon as I got home and saw it in my rsync log, I realized the difference.  Sorry about that.