Dear Chuck.Almost 2 years have passed and now I'm on Jaunty and I don't use
tunnels anymore. When I reported this bug, I've done some research of the
problem and at that time I was ready to provide any information requested.
But now I cannot help anyhow to fix this bug.
Anyway, thanks for your
Dear Chuck.Almost 2 years have passed and now I'm on Jaunty and I don't use
tunnels anymore. When I reported this bug, I've done some research of the
problem and at that time I was ready to provide any information requested.
But now I cannot help anyhow to fix this bug.
Anyway, thanks for your
1. sudo sh /usr/share/ati/fglrx-uninstall.sh
2. sudo apt-get install --reinstall xserver-xorg-driver-ati
On Wed, Dec 10, 2008 at 11:39 AM, Hali [EMAIL PROTECTED] wrote:
After I installed the latest catalyst Driver I cannot successfully
switch back to the free driver ATI catalyst control center
Dear Mario.
I think it's a good idea to mark fglrx-driver and xserver-xorg-video-ati as
conflicting packages. Installing of xserver-xorg-video-ati should automatically
remove fglrx-driverand vise-versa, because these packages replace files of
each other, thus they are conflicting.
--
r3xx
Dear Mario.
Why the status of this bug for Intrepid is marked as Fix Commited?
Where is the fix itself? Problem is still there.
On Wed, Nov 5, 2008 at 7:31 AM, Mario Limonciello
[EMAIL PROTECTED]wrote:
Esteban00:
This is an update to transition people with r3xx away from fglrx to the
open
You can use ATI open-source driver, but You should completely remove fglrx
driver.
They have some overlapping files and fglrx driver replaces ati driver files.
So You should just do the followinf things:
1. sudo apt-get remove --purge fglrx*
2. sudo apt-get remove --purge xserver-xorg-video-ati
BTW: problem is still there with version 2:8.543-0ubuntu2
--
Unable to load module fglrx: cannot allocate memory
https://bugs.launchpad.net/bugs/283836
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
I can also confirm. Exactly the same bug. ATI Mobility Radeon 9600.
--
Unable to load module fglrx: cannot allocate memory
https://bugs.launchpad.net/bugs/283836
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
I can also confirm. Exactly the same bug. ATI Mobility Radeon 9600.
--
Unable to load module fglrx: cannot allocate memory
https://bugs.launchpad.net/bugs/283836
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
Dear Dustin.
Thanks for note.
This happened in Gutsy. I'll check it in Hardy soon and I'll post here
messages from ssh with -vvv option.
On Wed, Apr 23, 2008 at 5:55 AM, Dustin Kirkland [EMAIL PROTECTED] wrote:
You can use -vvv option to ssh to log more verbosely. Would be
interesting to
Dear Dustin.
Thanks for note.
This happened in Gutsy. I'll check it in Hardy soon and I'll post here
messages from ssh with -vvv option.
On Wed, Apr 23, 2008 at 5:55 AM, Dustin Kirkland [EMAIL PROTECTED] wrote:
You can use -vvv option to ssh to log more verbosely. Would be
interesting to
Ethernet on both ends.
If I use port forwarding using -L option - connection does not die.
It happens only when I use ssh tunnel.
On Tue, Apr 22, 2008 at 12:03 AM, Rolf Leggewie
[EMAIL PROTECTED] wrote:
What kind of internet connection? DSL, dynIP?
--
ssh tunnel dies unexpectedly
Ethernet on both ends.
If I use port forwarding using -L option - connection does not die.
It happens only when I use ssh tunnel.
On Tue, Apr 22, 2008 at 12:03 AM, Rolf Leggewie
[EMAIL PROTECTED] wrote:
What kind of internet connection? DSL, dynIP?
--
ssh tunnel dies unexpectedly
yes. It's still there.
How can I resolve that?
Now I temporary switched to using ssh -L portforwarding (and it's
working good), because it's really frustrating
to restart tunnel 5-6 times a day.
On Tue, Feb 19, 2008 at 6:56 AM, Nicolas Valcárcel (nxvl)
[EMAIL PROTECTED] wrote:
Does this bug is
Public bug reported:
Dear all.
I have a problem: my ssh tunnel works fine for a while (this time varies from
minutes to hours) and then just stops to forward packets in one direction.
I tried to google this problem, but didn't find the solution.
Detailed description:
I have Gutsy on both
** Changed in: kdebase (Ubuntu)
Status: New = Fix Released
--
Cannot switch keyboard layout in KDE after upgrade from Feisty
https://bugs.launchpad.net/bugs/150388
You received this bug notification because you are a member of Kubuntu
Team, which is a bug contact for kdebase in ubuntu.
I found out, that bug was caused by attached patch.
Can anybody explain me details about this patch?
** Attachment added: kubuntu_72_kxkb_xmodmap.diff
http://launchpadlibrarian.net/9862986/kubuntu_72_kxkb_xmodmap.diff
--
Cannot switch keyboard layout in KDE after upgrade from Feisty
If I removed .Xmodmap file from my home directory - then evrything works
just fine.
Is it normal behavior?
Attached is my .Xmodmap file.
** Attachment added: Xmodmap
http://launchpadlibrarian.net/9863006/Xmodmap
--
Cannot switch keyboard layout in KDE after upgrade from Feisty
Public bug reported:
Binary package hint: kdebase-bin
I got a problem with KDE after upgrade to Gutsy.
I use Kxkb to switch keyboard layouts in Feisty and it worked just fine. But
now it does not work.
When I press Ctrl+Shift to switch layout to russian, icon in system tray is
changed, but
Dear all.
I tried to downgrade the version of kdebase-bin package to
kdebase-bin_3.5.6-0ubuntu20.4_i386.deb(from Feisty) and It helped: layout
switching works.
Then I tried to install new verison from gutsy repository and problem
appeared one more time. That means, that bug exists between
20 matches
Mail list logo
