[Bug 443004] Re: Eclispe GTK is not working correct - especially buttons

2009-10-05 Thread h-gent-o

** Attachment added: Dependencies.txt
   http://launchpadlibrarian.net/33021995/Dependencies.txt

** Attachment added: ProcMaps.txt
   http://launchpadlibrarian.net/33021996/ProcMaps.txt

** Attachment added: ProcStatus.txt
   http://launchpadlibrarian.net/33021997/ProcStatus.txt

** Attachment added: XsessionErrors.txt
   http://launchpadlibrarian.net/33021998/XsessionErrors.txt

-- 
Eclispe GTK is not working correct - especially buttons
https://bugs.launchpad.net/bugs/443004
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 443004] Re: Eclispe GTK is not working correct - especially buttons

2009-10-05 Thread h-gent-o
Eclispe == Eclipse (sorry for the typo)

-- 
Eclispe GTK is not working correct - especially buttons
https://bugs.launchpad.net/bugs/443004
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 443004] [NEW] Eclispe GTK is not working correct - especially buttons

2009-10-05 Thread h-gent-o
Public bug reported:

After update from alpha 6 to beta Karmic Koala - Eclispe is no longer working 
correct. It seems to be a problem with GTK.
Few buttons are not working - nothing happens when pressing the button or the 
expected dialog is not shown as expected.
I also tested other eclispe package with same result.

ProblemType: Bug
Architecture: i386
Date: Mon Oct  5 11:46:47 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/yelp
Package: yelp 2.28.0-0ubuntu1
ProcEnviron:
 PATH=(custom, user)
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-11.38-generic
SourcePackage: yelp
Uname: Linux 2.6.31-11-generic i686

** Affects: ubuntu
 Importance: Undecided
 Status: New


** Tags: apport-bug i386

-- 
Eclispe GTK is not working correct - especially buttons
https://bugs.launchpad.net/bugs/443004
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 443004] Re: Eclipse GTK is not working correct - especially buttons

2009-10-05 Thread h-gent-o
I attached the screenshot. For example clicking on the ok button has no
effect.

Maybe you can rebuild. Download Eclipse SDK 3.5.X -- Start Eclipse --
Menubar -- Help -- Tipps and Tricks ...  -- try to press the ok
button. This is only one example where the button is not working.

I'm pretty sure this is a GTK issue. I couldn't see few lines in a
listview but when I switch my theme to another one the lines are there,
but buttons are still not working. I have to say I updated over the last
month Karmic Koala from Alpha2 up to the latest beta.

P: Thanks, I didn't know to change the title would be possible
afterwards

** Attachment added: Sample where ok button is not working
   http://launchpadlibrarian.net/33050270/Screenshot.png

-- 
Eclipse GTK is not working correct - especially buttons
https://bugs.launchpad.net/bugs/443004
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


Re: [Bug 443004] Re: Eclipse GTK is not working correct - especially buttons

2009-10-05 Thread h-gent-o
I'll test if this happens with eclipse package from the ubuntu 
repository as well. Just to let you know, everything was working fine 
with Karmic until aplha6. With the beta of Karmic something must have 
changed causing the problems. Also it would be for the very first time, 
that the binary eclipse package would not work with ubuntu. We have the 
same eclipse environment (binary package) on different dev systems 
runnings, including ubuntu 9.04 and earlier without any issues.

-- 
Eclipse GTK is not working correct - especially buttons
https://bugs.launchpad.net/bugs/443004
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 352248] Re: can not create a new fixed size vdi

2009-04-15 Thread h-gent-o
I was not able to rebuild the issue. I was able to build vdi container.
So you might close the bug report. However, I would like to add the
building of the vdi container seems to me very slowly compared to
previous versions - perhaps it is the flash drive I'm using. I'll test
this more - but at least if not somebody else has the same issue we can
close this.

The machine I tested with:

X301 Lenovo Thinkpad with 128GB SSD

-- 
can not create a new fixed size vdi
https://bugs.launchpad.net/bugs/352248
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 352248] [NEW] can not create a new fixed size vdi

2009-03-31 Thread h-gent-o
Public bug reported:

Binary package hint: virtualbox-ose

Jaunty beta - I can't create a new fixed size vdi. the computer stops.
Partition is an ext3 partition.

ProblemType: Bug
Architecture: i386
DistroRelease: Ubuntu 9.04
Package: virtualbox-ose 2.1.4-dfsg-1ubuntu3
ProcEnviron:
 PATH=(custom, user)
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
SourcePackage: virtualbox-ose
Uname: Linux 2.6.28-11-generic i686

** Affects: virtualbox-ose (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: apport-bug i386

-- 
can not create a new fixed size vdi
https://bugs.launchpad.net/bugs/352248
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 352248] Re: can not create a new fixed size vdi

2009-03-31 Thread h-gent-o

** Attachment added: Dependencies.txt
   http://launchpadlibrarian.net/24564174/Dependencies.txt

-- 
can not create a new fixed size vdi
https://bugs.launchpad.net/bugs/352248
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 107311] Re: shoutcast list is empty

2009-03-30 Thread h-gent-o
I thought this bug was fixed for Ubuntu 8.10. But it seems the bug is
back again in Jaunty.

Reload of shoutcast station removes all stations from list and don't
show the refreshed entries.

-- 
shoutcast list is empty
https://bugs.launchpad.net/bugs/107311
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 144178] Re: Silicon Motion X driver fails to correctly restore text mode; requires modprobe vga16fb fbcon

2008-11-02 Thread h-gent-o
It seems something there is something fundamentally wrong/broken. I have
a Acer C100 TabletPC with SM720 lynx3dm silicon motion chipset. First I
installed the final Ubuntu 8.10 where installation was running well
until the reboot and where the gdm login should be there was just a
blank screen. I gave xubuntu a try and installed Xubuntu 8.10 - same
result everything fine until login screen (black but the system is
normally running ctrl+alt+del brings the system down).

Interesting the file xorg.conf is empty after installation process
(under Ubuntu and Xubuntu)!! The command dpkg-reconfigure -phigh
xserver-xorg build a simple xorg.conf but did not recognise the driver.
So I added to the Device section Driver siliconmotion.

I had to add  fbcon and vga16fb to /etc/modules as well, otherwise the
system remains black screened when trying to start with startx from root
console. now the system tells me fatal server error |
Addscreen/ScreenInit failed for driver 0

So far I'm not capable to enter the login screen somehow with 8.10.
Before 8.10 there was Ubuntu 6.06 running smoothly ;-(

-- 
Silicon Motion X driver fails to correctly restore text mode; requires modprobe 
vga16fb fbcon
https://bugs.launchpad.net/bugs/144178
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 72065] smb4k screwed the sudoers sudo command no longer available!

2006-11-16 Thread h-gent-o
Public bug reported:

Binary package hint: smb4k

Well I think this is major bug in smb4k as I found web entries with the
same problem. I don't know excatly what happens but the result was a
system only able to rescue with a live cd. Well I have ubuntu 6.10. the
I did install the smb4k via synaptic with all the other (depending)
packages. Then there was an error, system is not able to mount. So I
tried to change the configuration of smb4k and I think it is the super
user panel what brings up the error. So I activate Use super user
privileges to mount and unmount   Well this did not worked out with
error. Back to the normal systen suddenly the sudo command did not work
any longer (without and su account the system is totally srewed up)
Putting sudo tho the konsole brings this:

sudo cat /etc/sudoers
 sudoers file: syntax error, line 0 
 sudoers file: syntax error, line 1 
 sudoers file: syntax error, line 2 
 sudoers file: syntax error, line 3 
 sudoers file: syntax error, line 4 
 sudoers file: syntax error, line 5 
 sudoers file: syntax error, line 6 
 sudoers file: syntax error, line 7 
 sudoers file: syntax error, line 8 
 sudoers file: syntax error, line 9 
sudo: parse error in /etc/sudoers near line 0

Well I took a live cd, mount the root partition of ubuntu and took a
look to sudoers. I found this at the top of my sudoers!

X Error: BadDevice, invalid or uninitialized input device 169
  Major opcode:  147
  Minor opcode:  3
  Resource id:  0x0
Failed to open device
X Error: BadDevice, invalid or uninitialized input device 169
  Major opcode:  147
  Minor opcode:  3
  Resource id:  0x0
Failed to open device
# /etc/sudoers
#

I just remove the error entries and reboot and the system is fine again.
But how could this happen?


Greetings

** Affects: smb4k (Ubuntu)
 Importance: Undecided
 Status: Unconfirmed

-- 
smb4k screwed the sudoers sudo command no longer available! 
https://launchpad.net/bugs/72065

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs