I was able to get around this problem by executing usb-creator-gtk using
the following command:
sudo usb-creator-gtk --allow-system-internal
Be careful that you choose the correct device to erase, but this should
be a viable workaround until a fix is found.
--
You received this bug
This issue is solved with the 8.632 build from ati. I ran the
ati-driver-installer-9-4-x86.x86_64.run --buildpkg Ubuntu/jaunty
Build went fine, and I then installed the deb packages the installer generated.
--
[HD 4870] Power-off and power-on of monitors in multiheaded fglrx xorg
I should also note that I am no longer using ndependent screens. I am
using xinerama, and everything seems to be working ok with this
configuration (not xgl which xinerama does not support). Thanks to
everyone that has looked into this issue. My system is now usable
again, and I have not
Bryce, 8.620 does not resolve this particular issue. I see the same problem
with the new driver. It does fix other problems, such as restarting X cleanly
without power cycling the computer and xinerama. Please let me know if I can
provide further assistance.
Thanks.
--
[HD 4870] Power-off
** Attachment added: Screenshot-Startup Applications Preferences.png
http://launchpadlibrarian.net/26311622/Screenshot-Startup%20Applications%20Preferences.png
--
Power-off and power-on of monitors in multiheaded fglrx xorg configuration
causes X to become unresponsive/freeze in Jaunty
Sure. I am including my Xorg.0.log file. I'll also attach my xorg.conf
file. However, I have discovered that when the GDM Login display is
present, and I cycle the monitors, X does not freeze up. This leads me
to believe that there is something running in my session that is causing
this
Ok, I disabled the power management app in the startup applications, rebooted
the system, and tried again. Still having the same problem. I then rebooted,
ran a ps -welf pre-session-processes.list to output all the processes running
during the GDM session before logging in. Then I logged
Public bug reported:
Binary package hint: xorg
I am using Ubuntu 9.04_amd64 with the latest packages. I've installed Catalyst
released for 9.4 (the problem also existed wth 9.3), and am attaching my
xorg.conf file. I have 3 monitors and 2 rv770 (radeon hd4870) cards, and use
them as 3
** Attachment added: xorg configuration for recreating the bug
http://launchpadlibrarian.net/26190783/xorg.conf
** Description changed:
Binary package hint: xorg
I am using Ubuntu 9.04_amd64 with the latest packages. I've installed
Catalyst released for 9.4 (the problem also existed
** Description changed:
Binary package hint: xorg
- I am using Ubuntu 9.04_amd64 with the latest packages. I've installed
Catalyst released for 9.4 (the problem also existed wth 9.3), and am attaching
my xorg.conf file. I have 3 monitors and 2 rv770 (radeon hd4870) cards, and
use them
** Attachment added: submission.xml
http://launchpadlibrarian.net/26191697/submission.xml
--
Power-off and power-on of monitors in multiheaded fglrx xorg configuration
causes X to become unresponsive/freeze in Jaunty
https://bugs.launchpad.net/bugs/370051
You received this bug notification
Turned on screensaver and power management. Monitors go to sleep at the
specified time, but do not come back up when activating mouse or
keyboard. I assume because the input is not being passed to X.
Pressing Caps Lock or Num Lock do not change the led indicators on the
keyboard.
--
Power-off
Turned on screensaver and power management. Monitors go to sleep at the
specified time, but do not come back up when activating mouse or
keyboard. I assume because the input is not being passed to X.
Pressing Caps Lock or Num Lock do not change the led indicators on the
keyboard.
--
Power-off
I've tracked the problem to redirecting sound to the rdesktop client.
For example, 'rdesktop -u username -p password-a 16 -r sound:local
-bCNzPg 1600x1110 terminal server. Whenever a sound event is sent to
rdesktop, there is a high probability of rdesktop crashing. Disabling
sound seems to keep
Executing sudo /etc/dbus-1/event.d/25NetworkManager restart and trying 'Connect
to Other Wireless Network' works.
However, it does not re-associate if I loose the connection, or move within the
building to another location... which should prompt it to connect to the
closest/strongest wireless
network-manager0.6.5-0ubuntu16
network-manager-gnome 0.6.5-0ubuntu10
--
Added Leap Support plus fixes
https://bugs.launchpad.net/bugs/122059
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
I am using LEAP, which I believe is wpa-eap. Perhaps my problem is due
to the fact that I am unable to actually connect to the network, so the
fix doesn't even come into play yet?
On Fri, 2007-10-12 at 18:27 +, Andrew Jorgensen wrote:
Luxor wrote:
Applied Andrew's fix. The password
Applied Andrew's fix. The password is being held in the keyring... (was
doing so even before this fix), but I don't think the information is
being retrieved from the keyring to pass to wpa_supplicant by nm-applet.
I don't see wpa in the process list until I use the 'connect to other
wireless
syslog.luxor is the log of the failures.
syslog.luxor4 is the log of the successful connection.
Please let me know if you need anything further. Also, how can I view the
messages between nm and wpa_supplicant?
Thanks
** Attachment added: syslog of failure and success
** Attachment added: syslog.luxor4
http://launchpadlibrarian.net/9955383/syslog.luxor4
--
Added Leap Support plus fixes
https://bugs.launchpad.net/bugs/122059
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs
I retried after removing the %gonf.xml files, and the bug still exists.
When the key is not provided, wpa_supplicant does not get called, but if
I use the 'connect to other wireless network', then I can see
wpa_supplicant in the process list. Unfortunately, some other bug down
the line is causing
Applied Andrew's fix. The password is being held in the keyring... (was
doing so even before this fix), but I don't think the authentication
information is being retrieved from the keyring to pass to
wpa_supplicant by nm-applet. I don't see wpa in the process list until I
use the 'connect to other
I've found that this bug is related to
https://bugs.launchpad.net/bugs/41134. /usr/bin/wpa_supplicant is not
listed in the process list unless you re-login to a network by using the
'connect to other wireless network' option in nm-applet. When I do
login, wpa_supplicant -g
I have network-manager 0.6.5-0ubuntu15, and can confirm that this does
not work for LEAP.
--
Does not store WPA-Enterprise password in keyring
https://bugs.launchpad.net/bugs/41134
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
Please ignore my comment above. I need to retry this after removing the
%gconf.xml file
--
Does not store WPA-Enterprise password in keyring
https://bugs.launchpad.net/bugs/41134
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
** Changed in: rdesktop (Ubuntu)
Status: New = Confirmed
--
rdesktop locks keyboard
https://bugs.launchpad.net/bugs/81854
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
I am experiencing similar problems, but haven't verified that it is triggered
by a network failure. But once triggered, I have to minimize the rdesktop
window to regain keyboard focus for other applications. If I restore the
rdesktop window, keyboard is again locked, and the entire rdesktop
Alexander, here is my follow up to the first report:
When I first boot up and log into my account, nm-applet attempts to connect,
but seems to not have the appropriate keys (according to syslog), so I choose
'Connect to Other Wireless Network...' and enter the information for leap, and
see the
I am running Gutsy with atheros wireless and following packages:
network-manager0.6.5-0ubuntu12
network-manager-gnome 0.6.5-0ubuntu9
network-manager-openvpn0.3.2svn2342-1ubuntu2
network-manager-pptp
Looks like he is using the madwifi driver:
Sep 13 10:00:25 vorfeed NetworkManager: info SUP: sending command
'INTERFACE_ADD ath0^I^Imadwifi^I/var/run/wpa_supplicant3^I'
--
[gutsy] NetworkManager crashes on LEAP attempt
https://bugs.launchpad.net/bugs/139387
You received this bug notification
30 matches
Mail list logo
