If your running Sid do not upgrade hal.

Message

craigevil · #1 Post by **craigevil** » 2007-10-23 03:28

View topic - keyboard issues / tastatur-probleme
http://sidux.com/PNphpBB2-viewtopic-t-6553.html

Lots of us ran into many keyboard related issues with todays hal update. Things like arrow,delete keys not working, unable to use keyboard at all or moue in fullscreen games.

Non-US keyboard layouts were changed to US but still had the other problems as well.

CocoAUS · #2 Post by **CocoAUS** » 2007-10-23 04:04

I just did a dist-upgrade and haven't had any issues whatsoever.

rickh · #3 Post by **rickh** » 2007-10-23 04:29

I just did a dist-upgrade and haven't had any issues whatsoever.

Me, too. A couple hours ago, on my AMD64 system. I did notice that Hal was one of the upgrades.

Maybe it's a Sidux issue.

Edit: Reading the link in Craigevil's post, it appears that some people running pure Sid experienced it, too. There is a bug report. Guess I'll be cautious with my 32-bit system.

...and, another edit. After saying I had no issues, I guess I hit my up-arrow for the first time since my dist-upgrade ... Sure enough, problems. Believe me, downgrading Hal is no picnic ... A lot of stuff goes with it, and has to be reinstalled. Avoid it.

hellfire[bg] · #4 Post by **hellfire[bg]** » 2007-10-23 07:27

Thanks for the topic. You saved my day, Apt-listbugs didn`t mention anything about problems with hal so i gues i would have upgraded.

hkoster1 · #5 Post by **hkoster1** » 2007-10-23 09:47

A reply to the bug report mentioned by rickh gives a solution: uninstall the xserver-xorg-input-evdev package (and also the xserver-xorg-input-all meta-package to get rid of dependency problems). I can confirm that it works on my AMD64 system, the up-arrow is back to normal.

sinical · #6 Post by **sinical** » 2007-10-23 10:54

Tooo late

EDIT: My arrows are working fine

rickh · #7 Post by **rickh** » 2007-10-23 12:01

hkoster1 wrote:A reply to the bug report mentioned by rickh gives a solution: uninstall the xserver-xorg-input-evdev package (and also the xserver-xorg-input-all meta-package to get rid of dependency problems). I can confirm that it works on my AMD64 system, the up-arrow is back to normal.

Just for the sake of proper attribution, that solution seems to be from the Sidux forum, not the bug report.

Karel_ · #8 Post by **Karel_** » 2007-10-23 12:22

I can confirm it for Debian Sid. Arrow keys not working + messed up keyboard layout after today(apostrophe)s update.

rickh · #9 Post by **rickh** » 2007-10-23 12:35

hkoster1 wrote: ... uninstall the xserver-xorg-input-evdev package (and also the xserver-xorg-input-all meta-package to get rid of dependency problems). I can confirm that it works on my AMD64 system, the up-arrow is back to normal.

Confirmation on that. I am now running the current Sid version of Hal without problems.

# aptitude remove xserver-xorg-input-evdev

... took xserver-xorg-input-all with it, but left xserver-xorg-input-kbd and xserver-xorg-input-mouse in place. Everything is fine ... So, the upshot seems to be that there is no bug in Hal at all, but rather in xserver-xorg-input-evdev

x0as · #10 Post by **x0as** » 2007-10-23 12:52

Just dist-upgraded, no issues here.

edit: just checked, I haven't got hal installed

mzilikazi · #11 Post by **mzilikazi** » 2007-10-23 13:15

Well I had no problems at all because as usual - I never do dist-upgrade. Someday you'll learn.

Look how apt-get upgrade (not dist-upgrade) treats you nice (yet once again):

/snip/

Code: Select all

The following packages have been kept back:
  hal hal-info

I prefer to just let that stuff come down when it's ready.
Just the same I also nuked xserver-xorg-input-evdev

rickh · #12 Post by **rickh** » 2007-10-23 13:27

I'll bet that if you had attempted that upgrade a few hours ago, you'd have been bitten as well. With the flurry of activity overnight related to this issue, I suspect that Hal may have been flagged as a broken package. If the repository maintainers are really on top of things, though, now that you have removed xserver-xorg-input-evdev, another upgrade may allow Hal to come down.

Bro.Tiag · #13 Post by **Bro.Tiag** » 2007-10-23 14:55

Could someone point me to the documentation on how to do a dist-upgrade while excluding a potential problem, like hal?

Cheers

hkoster1 · #14 Post by **hkoster1** » 2007-10-23 16:29

No special documentation. If a dist-upgrade wants to remove a bunch of important packages, then you could do a simple apt-get upgrade instead and wait for the problem (likely asynchronous seeding of the mirrors) to be sorted out. Now, you could extend that sensible strategy to upgrades of dicey packages like hal. But that gives a problem if everybody does it that way -- how will the devs then know that there is a bug? I think going ahead with a dist-upgrade like hal is really taking your responsibility; filing a bug and/or initiating discussions like these will help the Gnu/Linux project forward. (Did I mention never to use Sid as your main or only OS?)

alleluia20 · #15 Post by **alleluia20** » 2007-10-23 16:53

This morning, I upgraded everything by hand (ie, no dist-upgrade) including hal, and apt did not say anything about broken dependencies.

And I had the problem.

You can solve it by activating the testing release, downgrading hal-info first, and downgrading hal afterwards. In this order, there is no problem with the downgrade.

Then, reboot.

Bro.Tiag · #16 Post by **Bro.Tiag** » 2007-10-23 19:20

Thank you.

hkoster1 wrote:No special documentation. If a dist-upgrade wants to remove a bunch of important packages, then you could do a simple apt-get upgrade instead and wait for the problem (likely asynchronous seeding of the mirrors) to be sorted out. Now, you could extend that sensible strategy to upgrades of dicey packages like hal. But that gives a problem if everybody does it that way -- how will the devs then know that there is a bug? I think going ahead with a dist-upgrade like hal is really taking your responsibility; filing a bug and/or initiating discussions like these will help the Gnu/Linux project forward. (Did I mention never to use Sid as your main or only OS?)

The issue with the last part of your reply is I'm not smart enough to be able to distinguish the difference between operating error and a bug.

Cheers

hellfire[bg] · #17 Post by **hellfire[bg]** » 2007-10-23 19:33

I dist-upgraded several hours ago and removed xserver-xorg-input-edev. No problems so far.

mzilikazi · #18 Post by **mzilikazi** » 2007-10-23 20:33

hkoster1 wrote:No special documentation. If a dist-upgrade wants to remove a bunch of important packages, then you could do a simple apt-get upgrade instead and wait for the problem (likely asynchronous seeding of the mirrors) to be sorted out.

Exactly. All the mirrors do not have all packages at the same time. So my strategy is wait. You do not cosmicly alter the state of your system simply by not exercising your dist-upgrade option, in fact you can handle the upgrade manually by explicitly installing any package that does not come along w/ a dist-upgrade or you can always dist-upgrade later if for example some packages do not get pulled in for a longer than usual period of time but quite often these packages will come in on their own in due time.

I think going ahead with a dist-upgrade like hal is really taking your responsibility; filing a bug and/or initiating discussions like these will help the Gnu/Linux project forward.

If that's the case everyone should run Sid at least on a test partition so that they too can submit bugs.

(Did I mention never to use Sid as your main or only OS?)

While Debian Sid is not my only OS it is most certainly my main desktop OS and has been for some years.

hkoster1 · #19 Post by **hkoster1** » 2007-10-23 20:48

mzilikazi wrote:While Debian Sid is not my only OS it is most certainly my main desktop OS and has been for some years.

Right, same here. All it takes is a bit of care upgrading (and keeping a regular backup of personal stuff off the premises). Luckily, using "apt-get dist-upgrade" always gives the choice of proceeding or not, and often I don't and substitute "apt-get upgrade" or wait altogether. Common sense, really. I know apt-get is not popular here, but I don't think aptitude gives the same freedom of upgrading... but do correct me if I'm wrong on this.

rickh · #20 Post by **rickh** » 2007-10-23 20:50

I don't think aptitude gives the same freedom of upgrading... but do correct me if I'm wrong on this

You're wrong, but we've already had enough of that discusssion.