Re: [Bug 185524] Re: ssh tunnel dies unexpectedly several times a day
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 effort. If nobody else has the same problem, then I suppose it's reasonable to close this bug. Regards. On Thu, Oct 15, 2009 at 1:57 AM, Chuck Short wrote: > We'd like to figure out what's causing this bug for you, but we haven't > heard back from you in a while. Could you please provide the requested > information? Thanks! > > -- > ssh tunnel dies unexpectedly several times a day > https://bugs.launchpad.net/bugs/185524 > You received this bug notification because you are a direct subscriber > of the bug. > -- ssh tunnel dies unexpectedly several times a day https://bugs.launchpad.net/bugs/185524 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 284408] Re: r3xx Hardware does not work with fglrx [EPR#257839]
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 still shows > up under application, how do I return the system to it's previous state > ? > > Currently it insists on booting into low graphics mode. > > -- > r3xx Hardware does not work with fglrx [EPR#257839] > https://bugs.launchpad.net/bugs/284408 > You received this bug notification because you are a direct subscriber > of a duplicate bug. > -- r3xx Hardware does not work with fglrx [EPR#257839] https://bugs.launchpad.net/bugs/284408 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 284408] Re: r3xx Hardware does not work with fglrx [EPR#257839]
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 Hardware does not work with fglrx [EPR#257839] https://bugs.launchpad.net/bugs/284408 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 284408] Re: r3xx Hardware does not work with fglrx
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 > source driver. It's applicable to anyone running hardy w/ r3xx and fglrx > that is considering upgrading. > > On Tue, Nov 4, 2008 at 14:24, Esteban00 <[EMAIL PROTECTED]> > wrote: > > > Sorry Martin, what have been added on proposed repos ? > > A new driver update ? > > i only saw some updates for Compiz and nothing more ... > > > > -- > > r3xx Hardware does not work with fglrx > > https://bugs.launchpad.net/bugs/284408 > > You received this bug notification because you are a bug assignee. > > > > > -- > Mario Limonciello > [EMAIL PROTECTED] > > -- > r3xx Hardware does not work with fglrx > https://bugs.launchpad.net/bugs/284408 > You received this bug notification because you are a direct subscriber > of a duplicate bug. > -- r3xx Hardware does not work with fglrx https://bugs.launchpad.net/bugs/284408 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 283836] Re: Unable to load module fglrx: cannot allocate memory
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 xserver-xorg-video-radeon 3. sudo apt-get install xserver-xorg-video-ati That's all. In my case it helped (ATI mobility radeon 9600) Good luck. On Tue, Oct 21, 2008 at 5:50 PM, p_alfa <[EMAIL PROTECTED]> wrote: > Yesterday, 20081020, just to give a try I update 7.04 to intrepid beta > and fglrx showed the same problem reported in these follow-ups, too. I > tried to use the OS driver (ati), and it does not work either. > > Pietro > > -- > Unable to load module fglrx: cannot allocate memory > https://bugs.launchpad.net/bugs/283836 > You received this bug notification because you are a direct subscriber > of the bug. > -- 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 283836] Re: Unable to load module fglrx: cannot allocate memory
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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 283836] Re: Unable to load module fglrx: cannot allocate memory
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 list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 283836] Re: Unable to load module fglrx: cannot allocate memory
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 list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 185524] Re: ssh tunnel dies unexpectedly several times a day
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 capture the message that occur when your tunneled > connection breaks. > > > :-Dustin > > -- > > > ssh tunnel dies unexpectedly several times a day > https://bugs.launchpad.net/bugs/185524 > You received this bug notification because you are a direct subscriber > of the bug. > -- ssh tunnel dies unexpectedly several times a day https://bugs.launchpad.net/bugs/185524 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 185524] Re: ssh tunnel dies unexpectedly several times a day
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 several times a day > https://bugs.launchpad.net/bugs/185524 > You received this bug notification because you are a direct subscriber > of the bug. > -- ssh tunnel dies unexpectedly several times a day https://bugs.launchpad.net/bugs/185524 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 185524] Re: ssh tunnel dies unexpectedly several times a day
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 still present? > > > > -- > ssh tunnel dies unexpectedly several times a day > https://bugs.launchpad.net/bugs/185524 > You received this bug notification because you are a direct subscriber > of the bug. > -- ssh tunnel dies unexpectedly several times a day https://bugs.launchpad.net/bugs/185524 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.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 185524] ssh tunnel dies unexpectedly several times a day
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 machines. Machine A - is client, machine B - server. My /etc/network/interfaces files looks like this: Machine A: iface tun0 inet static pre-up echo 1 > /proc/sys/net/ipv4/ip_forward pre-up ssh -f -w 0:0 machine_b_ip_address 'ifdown tun0; ifup tun0' pre-up sleep 5 address 10.0.0.1 pointopoint 10.0.0.2 netmask 255.255.255.0 up route add -net 192.168.1.0 netmask 255.255.255.0 gw 10.0.0.2 tun0 down route del -net 192.168.1.0 netmask 255.255.255.0 gw 10.0.0.2 tun0 Machine B: iface tun0 inet static pre-up echo 1 > /proc/sys/net/ipv4/ip_forward pre-up sleep 5 address 10.0.0.2 pointopoint 10.0.0.1 netmask 255.255.255.0 up route add -net 10.88.171.0 netmask 255.255.255.0 gw 10.0.0.1 tun0 down route del -net 10.88.171.0 netmask 255.255.255.0 gw 10.0.0.1 tun0 I start tunnel using "sudo ifup tun0". Then everything is working for some time. When it stops to work, I found out, that tunnel does not forward traffic from machine B to machine A, while traffic from machine A to machine B is forwarded correctly. Network device tun0 on machine B just stops transmitting the data. Also I noted, that it happens more frequently, while transmitting big amount of data. Please, help me to fix that. It's really borring to restart tunnel so often. ** Affects: openssh (Ubuntu) Importance: Undecided Status: New -- ssh tunnel dies unexpectedly several times a day https://bugs.launchpad.net/bugs/185524 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.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 150388] Re: Cannot switch keyboard layout in KDE after upgrade from Feisty
** 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. -- kubuntu-bugs mailing list [EMAIL PROTECTED] https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 150388] Re: 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 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. -- kubuntu-bugs mailing list [EMAIL PROTECTED] https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 150388] Re: Cannot switch keyboard layout in KDE after upgrade from Feisty
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 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. -- kubuntu-bugs mailing list [EMAIL PROTECTED] https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 150388] Re: Cannot switch keyboard layout in KDE after upgrade from Feisty
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 Feisty and Gutsy versions. Can anybody fix it? I can provide any details/logs, which You may need. -- 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 Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 150388] 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 layout is not switched. Even thought icon displays russian layout I still type in english. If in terminal I directly execute "setxkbmap -model pc104 -layout ru -variant winkeys", then I can type in russian. Also I tried to set it up using xorg.conf by specifying additional layout and disable layout switch in kxkb. But situation is the same: KKBSwitch displays correctly russian layout, but I still type in english. How can I fix that? P.S. In Gnome everything works fine ** Affects: kdebase (Ubuntu) Importance: Undecided Status: New -- 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 Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
