I can confirm that choosing cancel is a working workaround (altough with
the setup in English).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/905886
Title:
mythtv-setup.real crashed with SIGSEGV in
Is this backtrace any help? If not, please point me to the right way, as
I do not have any prior experience creating backtraces.
I should add I have not found a way to use apport, as I am running this
on a headless server using X-redirection over ssh. I do not have X on
the server. Mythtv is
Same here in up-to-date precise:
Program received signal SIGSEGV, Segmentation fault.
0x02020d9b in QVariant::QVariant(QVariant const) () from
/usr/lib/i386-linux-gnu/libQtCore.so.4
quit
Also the same segfault with the mythbuntu 0.24 ppa.
--
You received this bug notification because you are a
Confirmed, 2.6.38-11 fixes my issues.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/761065
Title:
[Sandybridge] Spurious *ERROR* Hangcheck timer elapsed... blt ring
idle messages in dmesg when
Robert Hooker: Thanks for your explanation, now that 2.6.38-10 has hit
-updates, I see forward to the following kernel in -proposed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/761065
Title:
What does 'applied' mean in this message?
https://lists.ubuntu.com/archives/kernel-team/2011-June/015962.html
There isn't a new kernel in natty-updates, and in natty-proposed this
bug isn't mentioned (http://kernel.ubuntu.com/~kernel-ppa/reports/sru-
report.html)...
Am I misunderstanding
*** This bug is a duplicate of bug 771518 ***
https://bugs.launchpad.net/bugs/771518
** This bug has been marked a duplicate of bug 771518
Unity launcher is easy to trigger when reaching for the browser back button
--
You received this bug notification because you are a member of Ubuntu
*** This bug is a duplicate of bug 771518 ***
https://bugs.launchpad.net/bugs/771518
** This bug has been marked a duplicate of bug 771518
Unity launcher is easy to trigger when reaching for the browser back button
--
You received this bug notification because you are a member of Ubuntu
I was for a time not able to test, but now I updated to the newest packages.
Now the following is happening:
-There is no more difference in using the 'nomodeset' parameter, both boot and
both render the gears with glxgears
-There is now a popup during boot with the message that the hardware is
After updating to latest packages and booting with modeset enabled, X
does not freeze anymore. I can move the mouse and go to a virtual
terminal, but unity does not come up and does not fall back to 2d unity.
All I see is the mouse pointer and the desktop background. To get a
usable desktop (2d) I
** Also affects: unity
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/745639
Title:
Xorg freezes with KMS, uses vesa without KMS
--
ubuntu-bugs mailing
Public bug reported:
Binary package hint: xorg
When starting the unity desktop for the first time, it locked up just
displaying the desktop background. As I had to use the nomodeset option
in Ubuntu 10.10 for glxgears to display anything, I also added this
option to the grub configuration file.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/745639
Title:
Xorg freezes with KMS, uses vesa without KMS
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
I believe lipstick meant it the other way around: chromium-browser-l10n
as dependency of chromium-browser.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/629129
Title:
chromium-browser should be
I have the same behaviour:
libusb couldn't open USB device /dev/bus/usb/005/002: Permission denied.
libusb requires write access to USB device nodes.
Using sudo with fprint_demo solves the permission issues.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
I have also a cpu family 15, model 3 Intel Pentium 4 3 GHz HT and also get the
NX warning message. As I was not sure which proc I really had I searched the
Intel site and narrowed it down to the following three models (based on cpu
freq, fsb freq and L2 cache size):
530/530J:
OK, never mind then, I just wanted to help!
--
lirc dpkg-config should split ir-receiver and remote configuration
https://bugs.launchpad.net/bugs/636896
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Public bug reported:
Binary package hint: lirc
IR-receiver and remote used are not an integrated whole. To be able to
present user friendly options, it would be better in the dpkg configure
screen to first ask about the IR-receiver, and then ask which remote is
used. Right now it assumes that if
apport information
** Tags added: apport-collected
** Description changed:
Because of bug https://bugs.launchpad.net/bugs/219382 I noticed that my
laptop (NEC Versa P550) incorrectly reports a 'discharging' state while
on AC.
Here are the outputs of the battery info:
cat
apport information
** Attachment added: AplayDevices.txt
http://launchpadlibrarian.net/42420864/AplayDevices.txt
--
battery charging state reports 'discharging' while on AC
https://bugs.launchpad.net/bugs/393984
You received this bug notification because you are a member of Ubuntu
Bugs,
apport information
** Attachment added: ArecordDevices.txt
http://launchpadlibrarian.net/42420898/ArecordDevices.txt
--
battery charging state reports 'discharging' while on AC
https://bugs.launchpad.net/bugs/393984
You received this bug notification because you are a member of Ubuntu
Bugs,
apport information
** Attachment added: BootDmesg.txt
http://launchpadlibrarian.net/42420947/BootDmesg.txt
--
battery charging state reports 'discharging' while on AC
https://bugs.launchpad.net/bugs/393984
You received this bug notification because you are a member of Ubuntu
Bugs, which is
apport information
** Attachment added: Card0.Codecs.codec97.0.ac97.0.0.txt
http://launchpadlibrarian.net/42420957/Card0.Codecs.codec97.0.ac97.0.0.txt
--
battery charging state reports 'discharging' while on AC
https://bugs.launchpad.net/bugs/393984
You received this bug notification because
apport information
** Attachment added: CurrentDmesg.txt
http://launchpadlibrarian.net/42420960/CurrentDmesg.txt
--
battery charging state reports 'discharging' while on AC
https://bugs.launchpad.net/bugs/393984
You received this bug notification because you are a member of Ubuntu
Bugs,
apport information
** Attachment added: Card0.Codecs.codec97.0.ac97.0.0.regs.txt
http://launchpadlibrarian.net/42420959/Card0.Codecs.codec97.0.ac97.0.0.regs.txt
--
battery charging state reports 'discharging' while on AC
https://bugs.launchpad.net/bugs/393984
You received this bug
apport information
** Attachment added: IwConfig.txt
http://launchpadlibrarian.net/42420964/IwConfig.txt
--
battery charging state reports 'discharging' while on AC
https://bugs.launchpad.net/bugs/393984
You received this bug notification because you are a member of Ubuntu
Bugs, which is
apport information
** Attachment added: Lspci.txt
http://launchpadlibrarian.net/42420967/Lspci.txt
--
battery charging state reports 'discharging' while on AC
https://bugs.launchpad.net/bugs/393984
You received this bug notification because you are a member of Ubuntu
Bugs, which is
apport information
** Attachment added: ProcCpuinfo.txt
http://launchpadlibrarian.net/42420971/ProcCpuinfo.txt
--
battery charging state reports 'discharging' while on AC
https://bugs.launchpad.net/bugs/393984
You received this bug notification because you are a member of Ubuntu
Bugs, which
apport information
** Attachment added: UdevLog.txt
http://launchpadlibrarian.net/42421044/UdevLog.txt
--
battery charging state reports 'discharging' while on AC
https://bugs.launchpad.net/bugs/393984
You received this bug notification because you are a member of Ubuntu
Bugs, which is
apport information
** Attachment added: PciMultimedia.txt
http://launchpadlibrarian.net/42420970/PciMultimedia.txt
--
battery charging state reports 'discharging' while on AC
https://bugs.launchpad.net/bugs/393984
You received this bug notification because you are a member of Ubuntu
Bugs,
apport information
** Attachment added: ProcInterrupts.txt
http://launchpadlibrarian.net/42420973/ProcInterrupts.txt
--
battery charging state reports 'discharging' while on AC
https://bugs.launchpad.net/bugs/393984
You received this bug notification because you are a member of Ubuntu
Bugs,
apport information
** Attachment added: ProcModules.txt
http://launchpadlibrarian.net/42420975/ProcModules.txt
--
battery charging state reports 'discharging' while on AC
https://bugs.launchpad.net/bugs/393984
You received this bug notification because you are a member of Ubuntu
Bugs, which
apport information
** Attachment added: UdevDb.txt
http://launchpadlibrarian.net/42420997/UdevDb.txt
--
battery charging state reports 'discharging' while on AC
https://bugs.launchpad.net/bugs/393984
You received this bug notification because you are a member of Ubuntu
Bugs, which is
apport information
** Attachment added: WifiSyslog.txt
http://launchpadlibrarian.net/42421046/WifiSyslog.txt
--
battery charging state reports 'discharging' while on AC
https://bugs.launchpad.net/bugs/393984
You received this bug notification because you are a member of Ubuntu
Bugs, which is
I have upgraded to lucid and still have the problem. I am not running
the most recent kernel, as that one freezes X very regular. As I was
running apport the battery indicator popped in and out from the
notification area, so I am not sure if it collected data on the right
moment.
--
battery
apport information
** Attachment added: Lsusb.txt
http://launchpadlibrarian.net/42420969/Lsusb.txt
--
battery charging state reports 'discharging' while on AC
https://bugs.launchpad.net/bugs/393984
You received this bug notification because you are a member of Ubuntu
Bugs, which is
apport information
** Attachment added: Card0.Amixer.values.txt
http://launchpadlibrarian.net/42420952/Card0.Amixer.values.txt
--
battery charging state reports 'discharging' while on AC
https://bugs.launchpad.net/bugs/393984
You received this bug notification because you are a member of
Got this issue after upgrading to lucid today. On karmic I did not have
this problem.
I've attached the output of
time dig -t a noc.sixxs.net +nofail | grep -e status -e A -e time
time dig -t noc.sixxs.net +nofail | grep -e status -e -e time
time getent hosts www.sixxs.net
**
Public bug reported:
Because of bug https://bugs.launchpad.net/bugs/219382 I noticed that my
laptop (NEC Versa P550) incorrectly reports a 'discharging' state while
on AC.
Here are the outputs of the battery info:
cat /proc/acpi/battery/BAT1/info
present: yes
design capacity:
Public bug reported:
When trying to upgrade using the update manager an exit error was
returned.
ProblemType: Package
Architecture: i386
DistroRelease: Ubuntu 9.04
ErrorMessage: subproces post-installation script gaf een foutwaarde 1 terug
HalComputerInfo:
Error: command ['lshal', '-u',
** Attachment added: BootDmesg.txt
http://launchpadlibrarian.net/28237370/BootDmesg.txt
** Attachment added: CurrentDmesg.txt
http://launchpadlibrarian.net/28237371/CurrentDmesg.txt
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/28237372/Dependencies.txt
**
When I ran update manager again, I chose to overwrite the menu.lst.
There seems to be no backup of the old one. Everything seems fine I believe.
Steffen Banhardt schreef:
Please post your menu.lst (which can be found at /boot/grub/menu.lst ),
there seems to be a problem with this file for
42 matches
Mail list logo
