apport information
** Attachment added: "acpidump.txt"
https://bugs.launchpad.net/bugs/1928355/+attachment/5497162/+files/acpidump.txt
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1928355/+attachment/5497161/+files/WifiSyslog.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1928355
Ti
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1928355/+attachment/5497160/+files/UdevDb.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1928355
Title:
li
apport information
** Attachment added: "RfKill.txt"
https://bugs.launchpad.net/bugs/1928355/+attachment/5497159/+files/RfKill.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1928355
Title:
li
apport information
** Attachment added: "PulseList.txt"
https://bugs.launchpad.net/bugs/1928355/+attachment/5497158/+files/PulseList.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1928355
Titl
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1928355/+attachment/5497157/+files/ProcModules.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1928355
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1928355/+attachment/5497156/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/192
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1928355/+attachment/5497155/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1928355
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1928355/+attachment/5497154/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1928355/+attachment/5497153/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1928355
apport information
** Attachment added: "PaInfo.txt"
https://bugs.launchpad.net/bugs/1928355/+attachment/5497152/+files/PaInfo.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1928355
Title:
li
apport information
** Attachment added: "Lsusb-v.txt"
https://bugs.launchpad.net/bugs/1928355/+attachment/5497151/+files/Lsusb-v.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1928355
Title:
apport information
** Attachment added: "Lsusb-t.txt"
https://bugs.launchpad.net/bugs/1928355/+attachment/5497150/+files/Lsusb-t.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1928355
Title:
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/1928355/+attachment/5497149/+files/Lsusb.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1928355
Title:
linu
apport information
** Attachment added: "Lspci-vt.txt"
https://bugs.launchpad.net/bugs/1928355/+attachment/5497148/+files/Lspci-vt.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1928355
Title:
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1928355/+attachment/5497147/+files/Lspci.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1928355
Title:
linu
apport information
** Attachment added: "IwConfig.txt"
https://bugs.launchpad.net/bugs/1928355/+attachment/5497146/+files/IwConfig.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1928355
Title:
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1928355/+attachment/5497145/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1928355
apport information
** Attachment added: "CRDA.txt"
https://bugs.launchpad.net/bugs/1928355/+attachment/5497144/+files/CRDA.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1928355
Title:
linux
apport information
** Tags added: apport-collected
** Description changed:
A kernel update was rolled out to hirsute yesterday (12/5) to 5.11.0-17
from 5.11.0-16
After the update X would not start.
I could see from the logs the amdgpu kernel model was not loaded.
Reverting bac
** Attachment added: "version.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1928355/+attachment/5497133/+files/version.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1928355
Title:
** Attachment added: "lspci-vnvn.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1928355/+attachment/5497132/+files/lspci-vnvn.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1928355
T
Public bug reported:
A kernel update was rolled out to hirsute yesterday (12/5) to 5.11.0-17
from 5.11.0-16
After the update X would not start.
I could see from the logs the amdgpu kernel model was not loaded.
Reverting back to the 5.11.0-16 kernel worked as expected.
The amdgpu module is blac
I narrowed down the issue to the linux-backports-modules-alsa-lucid-
generic specifically linux-backports-modules-alsa-2.6.32-24-generic
Once I removed the alsa backports modules from the 2.6.32-24 kernel the
cpu lockup issue did not occur.
Is this still the correct place for this bug or should I
** Attachment added: "lspci-vnvn.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/618155/+attachment/1491395/+files/lspci-vnvn.log
--
kernel 2.6.32-24 usb audio device causes cpu lockup
https://bugs.launchpad.net/bugs/618155
You received this bug notification because you are a membe
** Attachment added: "dmesg.log"
https://bugs.launchpad.net/bugs/618155/+attachment/1491394/+files/dmesg.log
--
kernel 2.6.32-24 usb audio device causes cpu lockup
https://bugs.launchpad.net/bugs/618155
You received this bug notification because you are a member of Ubuntu
Bugs, which is subsc
Public bug reported:
When my usb headset is plugged in using the 2.6.32-24 kernel there is a
cpu lockup. This also causes the gui to lockup and the keyboard is
unresponsive. A hard reset is required to use the computer again.
This is the specific information from when the usb device is plugged in
This version seems to work
ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: vnc4server 4.1.1+xorg4.3.0-37ubuntu2
ProcVersionSignature: Ubuntu 2.6.32-21.31-generic 2.6.32.11+drm33.2
Uname: Linux 2.6.32-21-generic x86_64
Architecture: amd64
Date: Fri Apr 16 15:55:35 2010
ExecutablePath: /usr/bin
Here are some of the obscure messages when you try and run some programs
from an xterm using Xvnc4 as a display...
m...@poseidon:~$ glxgears
Error: couldn't get an RGB, Double-buffered visual
m...@poseidon:~$ quadrapassel
Failed to initialise clutter: Unable to find suitable fbconfig for the GL
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/44434837/Dependencies.txt
** Attachment added: "ProcMaps.txt"
http://launchpadlibrarian.net/44434838/ProcMaps.txt
** Attachment added: "ProcStatus.txt"
http://launchpadlibrarian.net/44434839/ProcStatus.txt
--
Xvnc d
Public bug reported:
Xvnc4 does not support open gl
This means (among other things)
glxgears does not run
quadrappasel does not start
Xvnc4 can be configured with open gl as the version with centos 5 has
it.
bug numbers 150942 and 556270 may be similar, I report again so you get
up to date versi
OK, on my debian system the environment variable LANG is set to 'en_GB'.
On my ubuntu system the environment variable LANG is set to 'en_GB.UTF-8'.
setting the LANG environment variable consistently gives consistent behaviour
between ubuntu and debian.
Is there something wrong with the UTF8 local
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/42372625/Dependencies.txt
** Attachment added: "ProcAttrCurrent.gz"
http://launchpadlibrarian.net/42372626/ProcAttrCurrent.gz
** Attachment added: "ProcMaps.txt"
http://launchpadlibrarian.net/42372627/ProcMaps.txt
**
Public bug reported:
Binary package hint: aptitude
Using putty (0.60) to connect to ubuntu 10.4 beta server.
run aptitude
The border boxes and menu boxes are drawn inconsistently.
If putty is set to UTF-8 the menu boxes (hit f10 for menus) are drawn correctly
but the other boxes (eg l for limit
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/42368379/Dependencies.txt
--
Xvnc does not start up properly
https://bugs.launchpad.net/bugs/550844
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
Public bug reported:
vnc4server exits unexpectedly before you can even try connecting to it
command line to run as user
su -c 'Xvnc -query localhost -once -geometry 1280x1024 -rfbauth
/home//.vnc/passwd :2'
output on console
=cut here==
Xvnc Free Edition 4.1.1
Copyright (
** Summary changed:
- Xvnx terminates unexpectedly after a few seconds
+ Xvnc terminates unexpectedly after a few seconds
--
Xvnc terminates unexpectedly after a few seconds
https://bugs.launchpad.net/bugs/550831
You received this bug notification because you are a member of Ubuntu
Bugs, which i
Public bug reported:
trying to use Xvnc with XDMCP to allow remote use of compute server
command line (run as user ):
su -c 'Xvnc -query localhost -once -geometry 1280x1024 -rfbauth
/home//.vnc/passwd :2'
windows (XP) vncviewer - tried tightvnc, ultravnc and the original vnc4,
all
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/42366223/Dependencies.txt
** Attachment added: "ProcAttrCurrent.gz"
http://launchpadlibrarian.net/42366224/ProcAttrCurrent.gz
** Attachment added: "ProcMaps.txt"
http://launchpadlibrarian.net/42366225/ProcMaps.txt
**
Thank you yaohua! Your fix worked for me as well. I wanted to note that
I already had a module present at
/lib/modules/2.6.28-15-generic/kernel/drivers/net/atl1e/at1le.ko, but
this pre-installed one didn't work. I had to download the one from
Atheros.
--
linux: hardy: Add support for Atheros(R) A
Hi Alexander,
Sorry about the delay in getting back about this bug.
Initially when I tried this out on intrepid I was unable to connect to
my ap with the ssid hidden using wpa_supplicant.
There must have been some update in the past months that fixed this
problem, as I can now connect using wpa_
Ok Maybe not quite fixed yet.
I experinced this problem when I first tested 0.6.6-0ubuntu5 though I
was not able to replicate it again until now.
Vary rarely on a reconnect (ie a successfull connection was made, then
disconnect occurred) it seems that AP_SCAN 1
is being used.
Apr 6 07:26:39
Hi Alexander,
NM in hardy (0.6.6-0ubuntu5) has fixed this issue.
--
Gutsy Network Manager 0.6.5 and Ndiswrapper fails to connect to hidden AP
https://bugs.launchpad.net/bugs/156786
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubu
Same here. running Kubuntu(hardy):kde4:beta freshly installed and
updated.
When text doc is opened through service menu (both Kate and Kword)
Dolphin/Konqueror goes mainly blank for about 30 seconds, and re-appears
with the error message above. The document itself is opened without
delay or proble
For those who are going to use or have tried my fix.
Martin is correct.
ACTION=="add", RUN+="/sbin/start-stop-daemon --start --background --pidfile
/var/run/network/bogus --startas /sbin/ifup -- --allow auto $env{INTERFACE}"
The '--' applies to start-stop-daemon, not to ifup. Everything after --
Public bug reported:
Binary package hint: network-manager
After upgrading to gutsy I could not connect to a hidden wireless
through Network Manager using the Ndiswrapper driver.
I am running Kubuntu on IBM laptop Z60t with Atheros wireless card AR5212
My wireless router is a Netgear WGR614.
The
Hi Alexander,
This patch you have applied has affected the ndiswrapper driver.
I am running Kubuntu on IBM laptop Z60t with Atheros wireless card
AR5212
Originally I think it was on Fiesty I had problems with a kernel
upgrade that effected my wireless connectivity to hidden networks.
I downloa
maco: i now have a happy SD card!
confirm that there were whitespaces in the install script - i even checked
it myself b4 running it, duh! - which was likely the cause of my probs.
Ran the latest, kicked out a couple errors:
ERROR: Module tifm_sd does not exist in /proc/modules
ERROR: Module mmc_
i ran the script, partial success in that my logfiles dont fill with
errors but it did not mount - kern.log has
tifm_sd: disagrees about version of symbol tifm_eject
tifm_sd: Unknown symbol tifm_eject
and more similar (attached); also attached the install.log...
any advice?
** Attachment added:
Public bug reported:
Fujitsu-Siemens Amilo proV 2040: feisty, 2.6.20-13-generic.
Whole system failure occured due to lack of disc space; kern.log,
kern.log.0, syslog, syslog.0 (@ about 500MB each), messages & messages.0
(@ about 250MB each) accounted for the remaining space on the
partition.
I
Same issue with gnomebaker - able to burn iso as root with the following
output in terminal:
[EMAIL PROTECTED]:~$ sudo gnomebaker
(process:5791): GStreamer-WARNING **: The GStreamer function
gst_init_get_option_group() was
called, but the GLib threading system has not been initialised
I think I have found a solution to this problem, well it's fixed things
for me.
This is quite a verbose answer if you are not interested in all the details, see
the section labeled FIX at the bottom for the file to change.
There are two systems that I have found that deal with the network
interfa
52 matches
Mail list logo
