** Attachment added: "kern.log (during suspend&resume)"
http://launchpadlibrarian.net/12620093/kern.log
--
gnome-power-manager reports an error on succesful resume
https://bugs.launchpad.net/bugs/160138
You received this bug notification because you are a member of Ubuntu
Bugs, which is subsc
** Attachment added: "syslog (during suspend&resume)"
http://launchpadlibrarian.net/12620090/syslog
--
gnome-power-manager reports an error on succesful resume
https://bugs.launchpad.net/bugs/160138
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribe
started "lshal -m", suspended, resumed. Output attached.
** Attachment added: "lshal output (from suspend&resume)"
http://launchpadlibrarian.net/12619970/lshal.log
--
gnome-power-manager reports an error on succesful resume
https://bugs.launchpad.net/bugs/160138
You received this bug notifica
output from gnome-power-bugreport.sh attached
** Attachment added: "gnome-power-bugreport.sh output"
http://launchpadlibrarian.net/12619951/gpm.log
--
gnome-power-manager reports an error on succesful resume
https://bugs.launchpad.net/bugs/160138
You received this bug notification because you
Public bug reported:
Binary package hint: gnome-power-manager
I get a "failed to suspend" balloon every time the laptop successfully
resumes from suspend.
Steps to reproduce:
* select suspend (through System-menu or gnome-power-manager applet).
* resume
* see balloon appear
This is fully reprod
Well, I don't know hwere the xdg config was created, but I don't think
I've ever had desktop_is_home_dir set to true.
--
files from ~ shown on desktop (desktop_is_home_dir == false)
https://bugs.launchpad.net/bugs/154037
You received this bug notification because you are a member of Ubuntu
Bugs,
> Does it happen with a new created user? It could be a broken nautilus
configuration.
Thanks for the suggestion. I did some tests with a new user and figured out
what happened:
Nautilus works fine for new user, so I started copying some config files over
from my account and found the culprit.
** Description changed:
Binary package hint: nautilus
The gconf key /apps/nautilus/preferences/desktop_is_home_dir is set to
- false. Still, my desktop is full of files (from my home. ~/Desktop is
- practically empty). Also, clicking Places ->Desktop opens my home dir...
+ false. Still, my
Public bug reported:
Binary package hint: nautilus
The gconf key /apps/nautilus/preferences/desktop_is_home_dir is set to
false. Still, my desktop is full of files (from my home directory,
~/Desktop is practically empty). Also, clicking Places ->Desktop opens
my home dir...
Restarting nautilus d
Confirming. This does not prevent the upgrade though.
** Changed in: scrollkeeper (Ubuntu)
Status: New => Confirmed
--
scrollkeeper error
https://bugs.launchpad.net/bugs/148990
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu
J C Nash, just to make sure: are you saying that even though your
"default grub root device"-line was set correctly like this:
# groot=(hd0,0)
Your actual menu.lst entries still got set changed to "(hd0.1)"?
--
Linux-image upgrade messes up menu.1st
https://bugs.launchpad.net/bugs/84289
You rec
Public bug reported:
I do not have compiz installed (hardware not capable of fancy stuff like that),
but was still testing the new "Appearance Settings". Selecting normal or extra
effects on the desktop effects tab results in the following:
* Dialog "Failed to execute child process "compiz" (No
** Changed in: poldi (Ubuntu)
Status: New => Confirmed
--
libpam-poldi crashes when device is in use
https://bugs.launchpad.net/bugs/74209
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-b
** Changed in: gnupg (Ubuntu)
Status: New => Confirmed
--
segfault when running addcardkey for OpenPGP smartcard
https://bugs.launchpad.net/bugs/78120
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing l
Sorry Peter, I wasn't subscribed to this bug and forgot this.
This is probably not a problem after so many months, but just in case it still
is:
Please read the menu.lst-file, it is quite well documented (although I admit
the file format is just weird). The groot-line is _not_ a comment, update-
Last updates to command-not-found and command-not-found-data indeed fix
this. Changing status accordingly.
Hassan, you're probably seeing another bug and should file another
report.
** Changed in: command-not-found (Ubuntu)
Status: Confirmed => Fix Released
--
doesn't cope with db format
Confirming. I'm seeing this too on a fresh gutsy install.
** Changed in: command-not-found (Ubuntu)
Status: New => Confirmed
--
doesn't cope with db format transition
https://bugs.launchpad.net/bugs/133691
You received this bug notification because you are a member of Ubuntu
Bugs, which i
kaleidoscopeit, you do not have to fix this after every kernel upgrade
if you edit your grub configuration properly. Please see the comments in
"/boot/grub/menu.lst" and "man update-grub" for more info ("Default
kernel options" is what you are looking for...)
By the way, commenting in a bug manage
Matthias, like I said, the bug is not reproducible.
I would mark this WORKSFORME (or whatever is the equivalent in
launchpad), but I don't seem to be able to: I can't find a link or a
button to do that -- no idea if I have the rights to do that or not.
People say launchpad is easy, but for a longt
Attaching the output from "poldi-ctrl -d"
Version: 0.3.0-4 (in Feisty)
** Attachment added: "output from "poldi-ctrl -d""
http://librarian.launchpad.net/7113132/poldi-output
--
libpam-poldi crashes when device is in use
https://bugs.launchpad.net/bugs/74209
You received this bug notification
*** This bug is a duplicate of bug 74209 ***
My launchpad fu was evidently weak (marked duplicate).
This seems to happen because I had gpg-agent running.
--
"double free or corruption" in poldi-ctrl
https://launchpad.net/bugs/99893
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
htt
*** This bug is a duplicate of bug 74209 ***
Public bug reported:
Binary package hint: libpam-poldi
I tried to use my GnuPG smartcard for logging in using the instructions here:
http://www.schiessle.org/howto/poldi.shtml
Feisty has the needed libpam-poldi, but trying to run poldi-ctrl results
hackeron, that is quite probably another bug altogether. All kernels
>=2.6.18.2 have the fix...
Check the function names in the panic screen and if they aren't the same
as in the screenshot that's attached to this bug, file a new bug for
your issue.
--
Kernel panic - not syncing, when installing
** Summary changed:
- edgy->fetisty dist-upgrade only works if ~/.gnupg file is there
+ edgy->feisty dist-upgrade only works if ~/.gnupg file is there
--
edgy->feisty dist-upgrade only works if ~/.gnupg file is there
https://launchpad.net/bugs/78673
--
ubuntu-bugs mailing list
ubuntu-bugs@list
A work-around: Instead of using 'addcardkey', use first 'addkey' and
then 'keytocard'. This worked flawlessly for me.
Some notes:
- use 1024 bit RSA (encrypt only), for the encryption key
- use 1024 bit RSA (sign only), for the signature and auth keys
- select the new sub key before 'keytocard' -
I can confirm this exact behaviour on Edgy: There are three possible outcomes
to a 'addcardkey' command:
- error (exactly same as original poster)
- segfault (this actually comes after the key generation succeeds -- the
results aren't saved in the keyring though)
- success (this is rare, very
> Anyway, it appears that whatever is updating the menu.1st file
> when a linux-image upgrade is done is disregarding the
> existing menu.1st entries and misreading the partition table.
Updates to menu.lst are done according to the AUTOMAGIC KERNELS LIST
-part of the same file -- the option you
** Also affects: linux-source-2.6.15 (Debian) via
http://bugzilla.kernel.org/show_bug.cgi?id=5534
Importance: Unknown
Status: Unknown
--
CPU fan not activating on HP NX6125
https://launchpad.net/bugs/24308
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubunt
*** This bug is a duplicate of bug 63134 ***
** This bug is no longer a duplicate of bug 69790
kernel panic
** This bug has been marked a duplicate of bug 63134
Kernel panic - not syncing, when installing Edgy Beta1
--
Kernel panic
https://launchpad.net/bugs/69874
--
ubuntu-bugs mailing
*** This bug is a duplicate of bug 63134 ***
Hi chak, thanks for the comment
I'm going to mark this a duplicate of the other bug based on your
message. I hope it gets fixed soon.
** This bug has been marked a duplicate of bug 63134
Kernel panic - not syncing, when installing Edgy Beta1
--
I suspect this may really be a duplicate of bug 63134 based on the panic
and the hardware you have (although my french is pretty rusty). Can you
check if the kernel panic screen mentions "quirk_via_abnormal_poweroff"
like the screenshot in
http://librarian.launchpad.net/4557331/DSC01924.JPG?
Using
*** This bug is a duplicate of bug 69790 ***
This looks like the same bug you reported earlier. I'm going to mark it
duplicate, if you disagree please revert.
** This bug has been marked a duplicate of bug 69790
kernel panic
--
Kernel panic
https://launchpad.net/bugs/69874
--
ubuntu-bugs m
*** This bug is a duplicate of bug 63134 ***
As far as I can see this is a duplicate of bug 63134 (or maybe the other
way round as this one is older, but the other bug has a patch attached
so I'm going this way).
This bug has quite a few people posting in it, so I had some problems
identifying t
*** This bug is a duplicate of bug 63134 ***
Jae, judging from that "quirk_via_abnormal_poweroff" function in your
panic log, I'd say this is a duplicate of bug 63134. I'm marking this as
such.
There is a patch and a workaround (use "acpi=force" boot option) in
63134.
** This bug has been marke
Hi linpin,
I suspect your bug is a duplicate of bug 63134, based on the chipset on
your laptop (it's VIA, right?). I'm not sure, so I'm not marking this
duplicate yet.
Can you take a look at bug 63134 and see if the error you get is the
same as in the screenshot? Specifically, does your panic mes
I suspect this is a duplicate of 63134. Please mark this as as such if
you agree.
About 63134:
* VIA chipset related
* There's a workaround: use "acpi=force" as boot parameter.
* The stable kernel.org kernels have had a fix for it for about a month.
--
kernel panic on edgy RC
https://launchpad.n
*** This bug is a duplicate of bug 63134 ***
I'm going to mark this as a duplicate of bug 63134, as the kernel
versions and your chipset indicates that way. Please revert if you
disagree.
For a quick fix, use the "acpi=force" boot parameter.
** This bug has been marked a duplicate of bug 63134
Upstream uses the patch in the stable kernel (actually used in the last
one, 2.6.18.2, already):
http://kernel.org/pub/linux/kernel/v2.6/ChangeLog-2.6.18.2
I hope the reason for not putting this forward is not the low
urgency/importance settings -- those must surely be wrong. As already
stated thi
*** This bug is a duplicate of bug 63134 ***
This seems to be a duplicate of 63134 -- the fixes listed there work.
** This bug has been marked a duplicate of bug 63134
Kernel panic - not syncing, when installing Edgy Beta1
--
kernel panic when booting (init)
https://launchpad.net/bugs/72351
Public bug reported:
Kernel panics every time I try to boot into the Edgy default kernel
(2.6.17-10-386). Everything works with 2.6.15-27-386.
Here is the last lines of the boot output
---
Call Trace:
iounmap+0x4c/0xd0 acpi_hw_registe
I tried upgrading Dapper into Edgy on the same machine, and the same
panic happens when the machine is booted to the new kernel. so it is not
a installer bug, but a kernel bug.
It seems I cannot change the product or close my own bug in launchpad...
or have I gone blind? Anyway, I'll investigate m
Hardware in question is a fully integrated really small VIA chipset:
CPU: VIA EDEN-N Nano 800MHz (onboard)
North/South Bridge: VIA CLE266 / VT8235
I/O: VIA VT1211
Audio: VIA VT1612
Video: VIA UniChrome (onboard)
Ethernet: VIA VT6103
--
Edgy netboot kernel-panics (Dapper works fine)
https://launc
Public bug reported:
Binary package hint: debian-installer
I've tried to install 6.10 via netboot several times now on my mini-
computer (ebox 3850), and I always get a "kernel panic" about 20 seconds
after the installer starts:
The dapper netboot install works fine.
Here are the last lines of
Just in case this is useful:
* lsusb gives the same output in both kernels (see below)
* lshw does not output anything in 2.6.17-10. In the Dapper kernel (2.6.15-27)
the output is this:
> [EMAIL PROTECTED]:~$ sudo lshw -C network
> *-network
>description: Ethernet interfac
Public bug reported:
Openoffice crashed on startup. Started from the menu (Applications -
Office - OpenOffice.Org Word Processor). The program seemed to be
loaded, the window and all widgets had been drawn, but as I moved the
mouse to select File-menu, it crashed (without clicking).
** Affects: o
attached is the crash report that was created,
The crash does not seem to be reproducable.
** Attachment added: "crash report from OO.o"
http://librarian.launchpad.net/4942111/_usr_lib_openoffice_program_ooqstart.1000.crash
--
crash on startup
https://launchpad.net/bugs/69538
--
ubuntu-bu
** Summary changed:
- pegasus usb-ethernet driver does not work in Edgy
+ user is not informed if there is not enough power for usb devices
** Description changed:
+ EDIT: Original title was: "pegasus usb-ethernet driver does not work in
+ Edgy" -- edited when the real reason was found out (see
Ok, found the real reason:
Kernels => 2.6.16 have a feature that checks whether devices can be
given as much power as they claim to need. If there's not enough juice
(like in my case), the device is not activated. So a feature, not a bug.
The Debian bug I linked to is about notifying the user abo
Possibly our problems were different after all -- "irqpoll" option has
no effect here. The confirmation of the bug may have been premature...
I'm quite willing to help, but I have no idea what information a
developer would want.
--
pegasus usb-ethernet driver does not work in Edgy
https://launch
Found a workaround for the bug: setting xserver bitdepth to 24 (it was
16 because of maemo development. long story) stopped the crashing.
--
firefox hangs with flash plugin installed on certain sites
https://launchpad.net/bugs/302
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https:/
Public bug reported:
Binary package hint: linux-image-2.6.17-10-generic
In Dapper my usb ethernet adapter worked out-of-the-box. After upgrading
to Edgy RC it didn't. Booting into the last Dapper kernel
(2.6.15-27-686) fixes the issue.
The device uses the pegasus driver. In 2.6.15-27-686 connect
*** This bug is a duplicate of bug 67848 ***
I created a new bug (#67848) and marked this duplicate as I couldn't
figure out how to change the product (I hadn't assigned one
originally)...
** This bug has been marked a duplicate of bug 67848
pegasus usb-ethernet driver does not work in Edgy
-
I see the same problem as Dominik, Donald and Ben. I too am on Edgy that
was upgraded from Dapper... New profile, no extensions.
I'm afraid re-using this old bug was a mistake though -- the symptoms are not
exactly same (original bug description talks about a hang, not a crash)... I
hope the de
Public bug reported:
In Dapper my usb ethernet adapter worked out-of-the-box. After upgrading
to Edgy RC it didn't. Booting into the last Dapper kernel
(2.6.15-27-686) fixes the issue.
The device uses the pegasus driver. I do not know (yet) if the driver
can be loaded by hand in Edgy kernel, will
As far as I understand gksuexec should accept only userA password, exactly like
sudo... Using userB password should not work.
So when you're logged in as UserA, you gksudoexec with userA password
and select userB. You need to have permissions for this of course...
This seems to work as expected,
55 matches
Mail list logo
