[Bug 173833] Re: evdev mouse fails on hardy: cannot open input pEvdev

2008-09-24 Thread m_gol
Using "mouse" driver would be enough for me if it recognized all buttons of my mouse well. I've got Logitech MX310 and it has one special button, in MS Windows used as application changer (a replacement for Alt+Tab). Evdev recognizes it properly, whereas "mouse" driver thinks it's the same as middl

[Bug 150083] Re: Gutsy: Gnome fail to start after update to kernel 2.6.22-13-generic

2008-02-13 Thread m_gol
Is it a dup of #21412? -- Gutsy: Gnome fail to start after update to kernel 2.6.22-13-generic https://bugs.launchpad.net/bugs/150083 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.ubu

[Bug 150083] Re: Gutsy: Gnome fail to start after update to kernel 2.6.22-13-generic

2008-02-13 Thread m_gol
Sorry, I've written in the wrong bug report. :/ -- Gutsy: Gnome fail to start after update to kernel 2.6.22-13-generic https://bugs.launchpad.net/bugs/150083 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing l

[Bug 140982] Re: update-grub new kernel fails

2008-02-13 Thread m_gol
I agree with jimjin. I did not manually change menu.lst after an installation of Ubuntu. I just put "/boot" as a different partition than "/" so menu.lst should set up correctly by default. Unfortunately, after every kernel update, my proper "hd(0,0)" automatically changes to "hd(0,1)". I can manag

[Bug 21412] Re: Default update-grub behaviour is not intuitive with respect to user modifications

2008-02-13 Thread m_gol
I have such a partition configuration: /dev/sda1: /boot /dev/sda2: swap /dev/sda3: windows /dev/sda5: / /dev/sda6: /home In my menu.lst file I have lines containing: "root (hd0,0)" which is true. Nonetheless, after every kernel update, it automatically changes to "hd(0,1)" which breaks running of

[Bug 163116] Re: libsmbclient: upgrade fails with error 403

2007-11-17 Thread m_gol
@ itismike: Yes, read my notes. I thought (wrong) that You don't know how to update it, but I fully agree that such work-around doesn't deserve a "Fix Released" status. -- libsmbclient: upgrade fails with error 403 https://bugs.launchpad.net/bugs/163116 You received this bug notification because

[Bug 163116] Re: libsmbclient: upgrade fails with error 403

2007-11-17 Thread m_gol
@ Neal McBurnett: So it should be "Confirmed" or "In Progress", but not "Fix Released", as the issue has not been fixed yet, has it? -- libsmbclient: upgrade fails with error 403 https://bugs.launchpad.net/bugs/163116 You received this bug notification because you are a member of Ubuntu Bugs, wh

[Bug 163116] Re: libsmbclient: upgrade fails with error 403

2007-11-17 Thread m_gol
@ itismike: You have to open a console and write: sudo apt-get upgrade Then everything will be ok. Bu that's what I'm talking about - You shouldn't force people to use apt-get manually. They don't need to learn this. ** Changed in: samba (Ubuntu) Status: Fix Released => Invalid -- libsm

[Bug 163116] Re: libsmbclient: upgrade fails with error 403

2007-11-17 Thread m_gol
Super, but I can still see a problem. Yes, 'apt-get upgrade' works fine, but Ubuntu update manager doesn't use 'apt-get upgrade'. Ubuntu is oriented at usual people, that often want only to check e-mail, write a document and talk to others. They don't have to realize that there is a text console so