The specific bug I am interested in is case 2 from comment 70: 2. Some
people had bad files on the local box (through proxy or direct download)
and for them the fix was "sudo mv /var/lib/apt/lists
/var/lib/apt/lists.old ; sudo mkdir -p /var/lib/apt/lists/partial".
This can happen because of common
My DSL modem, when the network is down, responds to anything http with a
page redirecting to an error page on the modem. I found some examples of
this in some of the *Release files in my /var/lib/apt/lists. Hard to
imagine why apt-get prefers a local copy that it has PROVED to be bogus
over re-fetc
*** This bug is a duplicate of bug 24061 ***
https://bugs.launchpad.net/bugs/24061
My symptoms and how I made them go away match this bug report exactly.
The so-called duplicate bug #24061 has become a long discussion of many
different bugs and user errors that can result in a GPG key error.
Public bug reported:
On my Dell laptop, which was fresh-installed with Xubuntu 11.10 and
upgraded to 12.04, the official Ubuntu version of Clementine ignores the
multimedia keys. The PPA version in http://ppa.launchpad.net/me-
davidsansome/clementine/ubuntu responds as expected to the play/pause,
Sorry, everybody is too busy fighting over misunderstandings created
by the launchpad system, to actually fix anything. Or maybe they are
still throwing away their time trying to fix the ironically-named
"Unity".
On Fri, 06 Jan 2012 21:32:03 -
ehcpdeveloper wrote:
> I am still affected by th
Launchpad kept giving me an information-free error popup whenever I hit
"post" and so I did not know it was actually posting until I hit
refresh. Sorry (but it's not my fault really, is it).
--
[MASTER] [WORKAROUND] "Offline Mode" feature fails to detect proper online
state for networks that are
Some recent (this is July 26, 2010) update to Lucid has caused
NetworkManager to wake up, on a system that has no need for it (static,
permanent, wired, unmanaged network link only) and begin broadcasting
via ipc-of-the-week (DBUS?) that the machine had no network connection,
causing Firefox, claws
Some recent (this is July 26, 2010) update to Lucid has caused
NetworkManager to wake up, on a system that has no need for it (static,
permanent, wired, unmanaged network link only) and begin broadcasting
via ipc-of-the-week (DBUS?) that the machine had no network connection,
causing Firefox, claws
Some recent (this is July 26, 2010) update to Lucid has caused
NetworkManager to wake up, on a system that has no need for it (static,
permanent, wired, unmanaged network link only) and begin broadcasting
via ipc-of-the-week (DBUS?) that the machine had no network connection,
causing Firefox, claws
Some recent (this is July 26, 2010) update to Lucid has caused
NetworkManager to wake up, on a system that has no need for it (static,
permanent, wired, unmanaged network link only) and begin broadcasting
via ipc-of-the-week (DBUS?) that the machine had no network connection,
causing Firefox, claws
Some recent (this is July 26, 2010) update to Lucid has caused
NetworkManager to wake up, on a system that has no need for it (static,
permanent, wired, unmanaged network link only) and begin broadcasting
via ipc-of-the-week (DBUS?) that the machine had no network connection,
causing Firefox, claws
Some recent (this is July 26, 2010) update to Lucid has caused
NetworkManager to wake up, on a system that has no need for it (static,
permanent, wired, unmanaged network link only) and begin broadcasting
via ipc-of-the-week (DBUS?) that the machine had no network connection,
causing Firefox, claws
Some recent (this is July 26, 2010) update to Lucid has caused
NetworkManager to wake up, on a system that has no need for it (static,
permanent, wired, unmanaged network link only) and begin broadcasting
via ipc-of-the-week (DBUS?) that the machine had no network connection,
causing Firefox, claws
Some recent (this is July 26, 2010) update to Lucid has caused
NetworkManager to wake up, on a system that has no need for it (static,
permanent, wired, unmanaged network link only) and begin broadcasting
via ipc-of-the-week (DBUS?) that the machine had no network connection,
causing Firefox, claws
Some recent (this is July 26, 2010) update to Lucid has caused
NetworkManager to wake up, on a system that has no need for it (static,
permanent, wired, unmanaged network link only) and begin broadcasting
via ipc-of-the-week (DBUS?) that the machine had no network connection,
causing Firefox, claws
On initial install of Lucid, networking was fine, but after some very recent
update, NetworkManager woke up and started telling every part of the system
that was foolish enough to pay attention to that there was was no network
connection even though there was.
This desktop computer has a wired e
Computers are flexible, if you do not tell the computer what you want, it will
do something else instead.
Computers are stupid, they only understand what they understand.
Ubuntu Studio always seems to have a reach that is far beyond its grasp,
resulting in much spilled milk.
No one listen to Zath
Is this an example of a bug which becomes much easier to fix now that
jackd has been moved into "main"? That is, many things, including
PulseAudio, have code to be able to run "on top of" jackd in the sound
stack, but that code could not be enabled when jackd was not in the
"main" repository. If Pu
>> We will get fewer bug reports, those that we get will be of higher quality,
>> and we will be able to handle a greater
>> fraction than what we do today? ;-)
I understand those goals. I see the current process as sacrificing those
goals in favor of generating some good looking (but misleading)
backtrace resembles that for bug 509468, which has the log files. I
can't reliably trigger the bug, though, and trying to do so under Lucid
is not practical for me at this time. If Ubuntu makes reporting bugs in
a way they will accept harder than switching to another distribution,
guess what will h
** Attachment added: "/var/log/gdm/:0.log.1 after X abort"
http://launchpadlibrarian.net/38066771/x-blowup-log.txt
** Attachment added: "BootDmesg.txt"
http://launchpadlibrarian.net/38066772/BootDmesg.txt
** Attachment added: "CurrentDmesg.txt"
http://launchpadlibrarian.net/38066773/Cur
Public bug reported:
Binary package hint: xserver-xorg-video-intel
X server crashes unpredictably while I'm doing something interactive.
Screen goes black, login session vanishes, eventually gdm login screen
appears. started after upgrade to Karmic. key lines from
/var/log/gdm/:0.log.1 logfile:
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/35371334/Dependencies.txt
** Attachment added: "ProcMaps.txt"
http://launchpadlibrarian.net/35371335/ProcMaps.txt
** Attachment added: "ProcStatus.txt"
http://launchpadlibrarian.net/35371336/ProcStatus.txt
--
broken
Public bug reported:
Binary package hint: rhythmbox
For variable bit rate MP3 files such as those lame calls ABR or VBR,
program uses a very inaccurate estimate of the bit rate of the file to
calculate the time duration of the audio. Programs that do not suck
provide an option to find the true du
Ubuntu 8.10.
Wired and Wireless connections, sometimes use one, sometimes the other.
DHCP works, but I want to use fixed addresses on some networks even when DHCP
server is available.
Bug: changes made via the NetworkManager applet sometimes stick, but usually
get silently thrown away either at o
I'm annoyed that Ubuntu is resorting to cooking their statistics by
closing bugs as invalid just because they can't be bothered to read
them.
** Changed in: ubuntu
Status: Invalid => Confirmed
--
mounts wrong partition on boot
https://bugs.launchpad.net/bugs/133152
You received this bug n
On my computer the problem happened because /etc/fstab contained
mountpoints that used UUIDs just as recommended, in fact as set up by
the Kubuntu installer and not messed with by me. The problem is that a
byte-for-byte copy of a partition has the same UUID as the original
partition, even if it is
"(Note that there is no way for the computer to magically know which
card you want to be the default upon a fresh install of Ubuntu.)"
The above comment has nothing to do with this bug report and is
"invalid" as a reason to mark the bug report invalid. What's going on?
Is Ubuntu trying to make its
Similar symptoms here with regular 32-bit kernel. Realtime (-rt) 32-bit
kernel still gives "irq 18 nobody cares try irqpoll" message but works
even without irqpoll option.
irq 18: nobody cared (try booting with the "irqpoll" option)
** Attachment added: "dmesg output after -rt kernel boot"
htt
** Summary changed:
- dragging album to play queue does not preserve the same order as shown in
entry view
+ bug reports not welcome
** Description changed:
- Binary package hint: rhythmbox
-
- Rhythmbox 0.11.2, Gutsy Gibbon (still waiting for the Heron to
- stabilize).
-
- The first thing I
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/15087113/Dependencies.txt
** Attachment added: "ProcMaps.txt"
http://launchpadlibrarian.net/15087114/ProcMaps.txt
** Attachment added: "ProcStatus.txt"
http://launchpadlibrarian.net/15087115/ProcStatus.txt
--
usecas
Public bug reported:
Binary package hint: rhythmbox
Rhythmbox 0.11.2, Gutsy Gibbon (still waiting for the Heron to
stabilize).
The first thing I try to do with an audio player program is to play a bunch of
audio files, sorted by file name.
Does giving filenames as command line arguments do it (
As suggested by Nick and several others, I've installed dbus-x11. It may
be awhile before I know if this fixes my symptom reported above, but it
looks like there is a bug in the package dependency declarations anyway.
When the dbus package was split into dbus and dbus-x11, some other
packages (gnom
I also on login (to Gnome) sometimes get messages about not being able to
contact the dbus service,
appearing on screen and in various log files. Usually if I logout and login
again, all looks normal on second login.
Sure looks like there is insufficient synchronization of the things that run
du
I find resizing windows on Gutsy very frustrating. The draggable window
borders are narrower than the accuracy with which I can position the
mouse.
Obviously this is one of those things where some people cannot imagine
how anyone could be bothered by it, others (like me) don't have to
imagine it,
** Summary changed:
- kubuntu upgrade to 7.04 broke wpa wireless link
+ kubuntu cannot deal with wpa wireless link
** Description changed:
- Binary package hint: network-manager
+ Current (December 2007) status: the upgrade for 7.10 (Gutsy) left my
+ "put magic text in config files with my bare
** Also affects: knetworkmanager (Ubuntu)
Importance: Undecided
Status: New
--
kubuntu upgrade to 7.04 broke wpa wireless link
https://bugs.launchpad.net/bugs/110325
You received this bug notification because you are a member of Kubuntu
Team, which is a bug contact for knetworkmanager i
The good news is that my laptop upgraded from Kubuntu 7.04 to 7.10
upgraded without incident, once I deleted the ubuntustudio repositories
from the apt configuration.
My manual, untouched by GUI applications, WPA2 (pre-shared key) wireless
networking set-up, which works even though I don't underst
OK, I appended to /etc/modprobe.d/alsa-base the lines
options snd_hda_intel index=0
options snd_ice1712 index=1
ran sudo update-modules, rebooted.
Now indeed the sound device numbers are swapped (back) and my sound
applications are happy again.
Looking at the bug reports which someone has hel
I'm running Gutsy and just noticed today that applications that had been
happily playing through my built-in snd_hda_intel device were failing.
It looks like some recent update (or random cosmic rays) caused my two
sound devices to swap indexes. I now have
cat /proc/asound/modules
0 snd_ice1712
As far as i am concerned, this can be marked "fixed". As I recall, there
was another update to xserver-xorg-video-intel and once that was
installed, I could boot the latest kernel version and get X to work. For
what it's worth, I installed from Tribe 4 and have basically just let
the system update
Sorry to speculate, but it kind of looks like the xserver-xorg-video-
intel and the kernel versions are chasing each other in a circle over
how to allocate some resource.
The lspci attached is from running the -13 kernel, the one that works at
the moment.
** Also affects: linux-source-2.6.22 (Bal
Public bug reported:
Binary package hint: xserver-xorg-video-intel
Symptoms appeared after second version of -14 kernel image installed. OK now
under -13 kernel.
Symptoms: bottom part of screen is rectangular blocks of color, or sometimes
other junk.
** Affects: xserver-xorg-video-intel (Ubunt
Recent updates seem to have fixed the problem on this computer.
Probably fixed by updating xserver-xorg-video-intel to 2:2.1.1-0ubuntu6.
Now the 2.6.22-13-generic kernel and X are OK.
--
X broken by -13 kernel, -12 still OK
https://bugs.launchpad.net/bugs/149929
You received this bug notification
I also have a computer with Intel G33 graphics and the -13 kernel was
bad luck for it also. See bug 149929.
--
kernel 2.6.22-13 regression: Intel G33 graphics not recognized
https://bugs.launchpad.net/bugs/150099
You received this bug notification because you are a member of Ubuntu
Bugs, which is
This could be the same bug as Bug 149929, which has several relevant
dmesg logs attached already.
--
2.6.22-13 kernel crash
https://bugs.launchpad.net/bugs/149945
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mail
For what it's worth, I see a similar difference in dmesg output here also
between -12 and -13 kernels.
X keeps trying and failing to start in "normal" mode, falls back into some kind
of low-rez "safe" mode.
I captured the dmesg.13 by clicking "shut down" and falling into a root,
text-mode shell.
Public bug reported:
Binary package hint: xorg
Today's updated gutsy beta went from
"Linux wolf 2.6.22-12-generic #1 SMP Sun Sep 23 18:11:30 GMT 2007 i686
GNU/Linux"
to a 2.6.22-13 kernel. On Booting the new kernel, got a dialogue saying X
needed
configuring to get out of low-rez mode, but whe
** Attachment added: "xorg.conf"
http://launchpadlibrarian.net/9846510/xorg.conf
--
X broken by -13 kernel, -12 still OK
https://bugs.launchpad.net/bugs/149929
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mai
** Visibility changed to: Public
--
hydrogen crashed with SIGSEGV in std::basic_string, std::allocator >::basic_string()
https://bugs.launchpad.net/bugs/147470
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing
** Attachment added: "CoreDump.gz"
http://launchpadlibrarian.net/9829818/CoreDump.gz
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/9829819/Dependencies.txt
** Attachment added: "Disassembly.txt"
http://launchpadlibrarian.net/9829820/Disassembly.txt
** Attachment
Public bug reported:
Binary package hint: hydrogen
Hydrogen playing under Jack Transport control while Ardour was recording a
vocal.
Jack noticed the Hydrogen had died and shut down.
14:41:44.247 Audio connection graph change.
14:55:10.101 Audio connection graph change.
14:55:10.263 Audio conne
Using Kubuntu 7.04 version of Hydrogen. I have had some crashes that seemed to
be related
to using a pattern size of 7 (as in 7/4 time). But it doesn't always crash when
I do this.
--
Crashes when I try to reduce pattern size
https://bugs.launchpad.net/bugs/77163
You received this bug notificat
Similar error here. Dell Inspiron 530 Desktop computer.
I've noticed "KDSETKEYCODE: Invalid argument" errors on bootup for a long time
(possibly since I started with Tribe 4).
But since about Sept 19 or 20, Update Manager always reports error due to
hotkey-setup errors.
dpkg: error processing h
Public bug reported:
Kubuntu 7.04 (upgraded from 6.10) confuses partitions on different
disks.
Machine is configured to dual boot with XP. Normally, when I boot Kubuntu, the
XP partition is mounted on /media/xp (I think I assigned that pathname during
the initial install). But, some time ago I
** Attachment added: "CoreDump.gz"
http://launchpadlibrarian.net/8818052/CoreDump.gz
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/8818053/Dependencies.txt
** Attachment added: "Disassembly.txt"
http://launchpadlibrarian.net/8818054/Disassembly.txt
** Attachment
Public bug reported:
Binary package hint: totem
double-clicked the Experience Ubuntu icon in the examples folder in
Gutsy Tribe 4 live-CD on new Dell Inspiron 530 (Vista version). Player
appeared, went gray, vanished.
ProblemType: Crash
Architecture: i386
Date: Tue Aug 14 15:34:56 2007
DistroRel
Here is the apt.log too.
** Attachment added: "apt.log"
http://librarian.launchpad.net/7480033/apt.log
--
kubuntu upgrade to 7.04 broke wpa wireless link
https://bugs.launchpad.net/bugs/110325
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact
As you can see in the attachment, I also encountered the "crash trying
to remove old packages" bug, which I reported along with many others.
But that appears to be the very last step before rebooting, so I don't
think that the upgrade missed anything.
** Attachment added: "/var/log/dist-upgrade/ma
Javier,
Thank you for the helpful reply. The wireless link seems to be OK today.
I'll try the instructions in
https://help.ubuntu.com/community/WifiDocs/WPAHowTo/Kubuntu#EasySteps
if/when I get time to experiment. For now, having the network connect
without user intervention and before I even log
Public bug reported:
Binary package hint: network-manager
After much else failed, I got Edgy to use my wireless link using the
instructions at http://ubuntuforums.org/showthread.php?t=202834 The
hardware driver was never an issue -- the problem is that Ubuntu's
handling of WPA (wireless encrypti
I had what looks like the same crash yesterday, on a laptop with 1 Gig RAM and
2 Gig swap.
Crashed after asking permission to delete obsolete packages, ate swap space
rapidly then out of memory.
System appeared to reboot OK afterward, though wireless networking was broken
by the upgrade.
What ar
I recently updated a Dapper installation to Edgy using the recommended
"gksu update-manager -c" procedure. On booting into Edgy, it failed to
the "enter root password to repair" prompt, obviously a bad message for
Ubuntu to show a newbie since root isn't supposed to have a password.
Above that the
63 matches
Mail list logo
