Can not type in commit message area

Bug #651283 reported by jj3666 on 2010-09-29
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
git-cola (Ubuntu)
Low
Unassigned

Bug Description

Binary package hint: git-cola

Description: Ubuntu maverick (development branch)
Release: 10.10

git-cola:
  Installed: 1.4.2.1-1

In 'Commit message editor' window, I wanted to type a message for my staged files, but it would not let me. After selecting 'commit' button and receiving error about blank messages, it would then allow me to type in the editor.

ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: git-cola 1.4.2.1-1
ProcVersionSignature: Ubuntu 2.6.35-22.33-generic 2.6.35.4
Uname: Linux 2.6.35-22-generic x86_64
NonfreeKernelModules: nvidia
Architecture: amd64
Date: Wed Sep 29 09:26:46 2010
EcryptfsInUse: Yes
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429)
PackageArchitecture: all
ProcEnviron:
 PATH=(custom, user)
 LANG=en_US.utf8
 SHELL=/bin/bash
SourcePackage: git-cola

jj3666 (jj3666) wrote :
Iulian Udrea (iulian) wrote :

I couldn't reproduce it. What error do you get? I've only got this:

Please supply a commit message.

A good commit message has the following format:

- First line: Describe in one sentence what you did.
- Second line: Blank
- Remaining lines: Describe why this change is good.

Could you please provide more information 'bout this?

Ta.

Changed in git-cola (Ubuntu):
status: New → Incomplete

 I did not receive any errors. Only after receiving the following error
would it let me type into the editor, not before.

The process to reproduce.
0) Open progam selecting open and choosing a local repo
1) Stage file(s)
2) Try to type a commit message ... it would not let me.
3) I clicked on the commit button, received the error below
4) Then it would let me type a message into the editor
5) I then clicked on commit again and message was added properly.

After staging files, I should not have to click the commit message
button before being able to type into the editor window.

Jared Johnson

On 09/29/2010 10:03 AM, Iulian Udrea wrote:
> I couldn't reproduce it. What error do you get? I've only got this:
>
> Please supply a commit message.
>
> A good commit message has the following format:
>
> - First line: Describe in one sentence what you did.
> - Second line: Blank
> - Remaining lines: Describe why this change is good.
>
> Could you please provide more information 'bout this?
>
> Ta.
>
> ** Changed in: git-cola (Ubuntu)
> Status: New => Incomplete
>

Iulian Udrea (iulian) wrote :

It works just fine over here. What error do you get? Could you please paste the error message here?

 I am not getting an error message. It just will not let me type into
the 'Commit Message Editor' window after staging files until I either
click the 'Sign Off' button or the 'Commit' button and receive the error
message you posted previously. I believe I should be able to type a
commit message after staging files without having to click either of the
buttons first.
Jared Johnson

On 09/29/2010 11:35 AM, Iulian Udrea wrote:
> It works just fine over here. What error do you get? Could you please
> paste the error message here?
>

Iulian Udrea (iulian) wrote :

OK, that's not an error and this is definitely not a bug but a feature request. Anyway, I'll let David (author of git-cola) know 'bout this.

Thank you for your time.

Changed in git-cola (Ubuntu):
status: Incomplete → Triaged
importance: Undecided → Low
daveinthesky (davvid) wrote :

I am under the impression that this bug is another fallout from something going on in python-qt4.

https://bugs.launchpad.net/ubuntu/+source/python-qt4/+bug/660363

daveinthesky (davvid) wrote :

Also tracking this request here: http://github.com/davvid/git-cola/issues#issue/65

Jared: are you able to type if you click into the commit message text area? Is this a feature request to have cola give that widget keyboard focus after staging?

jj3666 (jj3666) wrote :

SOLVED! After loading alternate cd and installing identical packages (with exception of nvidia-current) everything still worked properly. Since the nvidia was the only missing package, I thought about the issues I have with window focus in WINE. The only other configuration difference between running machine and VM would be the Desktop Effects under the Appearance preference, being that the VM is set to none. I set my desktop to none and git-cola worked as it should. Thanks all for listening to my rambling, and I hope this may help someone else, or maybe if someone else has the time to track down the reason... signing off this comment for good!

jj3666 (jj3666) wrote :

PS Should this be assigned to a bug now? Since it only works with Visual Effects set to none... maybe someone else can verify this?

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers