It no longers appears to be a problem ( for me at least ) and can be
closed I guess
--
swap vol_id incorrect after some updates
https://bugs.launchpad.net/bugs/97480
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
just upgraded to hardy a few days ago. I was about to file a bug when
I realised this
one was still open.
On Tue, Feb 26, 2008 at 11:40 PM, Brian Murray <[EMAIL PROTECTED]> wrote:
> Are you still using Feisty or have you upgraded?
>
>
> --
> swap vol_id incorrect after some updates
>
>
> https:/
Public bug reported:
Binary package hint: compiz
probably similar to Bug #87399. tried compiz with regular ati driver and
it worked fine. Then installed and enabled fglrx with the new restricted
driver thingy. Restarted computer, then tried starting compix, got an
error "no composite extension fo
** Attachment added: "CoreDump.gz"
http://librarian.launchpad.net/6778629/CoreDump.gz
** Attachment added: "Dependencies.txt"
http://librarian.launchpad.net/6778630/Dependencies.txt
** Attachment added: "Disassembly.txt"
http://librarian.launchpad.net/6778631/Disassembly.txt
** Attachm
Public bug reported:
Binary package hint: update-notifier
seems to be the same as bug #88104 - except I was using synaptic
ProblemType: Crash
Date: Tue Feb 27 00:03:13 2007
DistroRelease: Ubuntu 7.04
ExecutablePath: /usr/lib/update-notifier/apt-check
InterpreterPath: /usr/bin/python2.5
Package:
** Attachment added: "Dependencies.txt"
http://librarian.launchpad.net/6543795/Dependencies.txt
** Attachment added: "ProcMaps.txt"
http://librarian.launchpad.net/6543796/ProcMaps.txt
** Attachment added: "ProcStatus.txt"
http://librarian.launchpad.net/6543797/ProcStatus.txt
--
[appor
Public bug reported:
Binary package hint: grip
I typed grip, program opened for a brief moment and then died
ProblemType: Crash
Architecture: i386
CrashCounter: 1
Date: Wed Feb 28 16:45:30 2007
DistroRelease: Ubuntu 7.04
ExecutablePath: /usr/bin/grip
Package: grip 3.3.1-11
ProcCmdline: grip
Proc
** Attachment added: "CoreDump.gz"
http://librarian.launchpad.net/6568046/CoreDump.gz
** Attachment added: "Dependencies.txt"
http://librarian.launchpad.net/6568047/Dependencies.txt
** Attachment added: "Disassembly.txt"
http://librarian.launchpad.net/6568048/Disassembly.txt
** Attachm
Public bug reported:
Binary package hint: compiz
right click on compiz-tray-icon, select preferences, compiz crashes
ProblemType: Crash
Architecture: i386
Date: Wed Feb 28 22:19:32 2007
DistroRelease: Ubuntu 7.04
ExecutablePath: /usr/bin/compiz.real
Package: compiz-core 1:0.3.6-1ubuntu7
ProcCmdl
** Attachment added: "CoreDump.gz"
http://librarian.launchpad.net/6579879/CoreDump.gz
** Attachment added: "Dependencies.txt"
http://librarian.launchpad.net/6579880/Dependencies.txt
** Attachment added: "Disassembly.txt"
http://librarian.launchpad.net/6579881/Disassembly.txt
** Attachm
Public bug reported:
occurs in feisty,
after some updates ( usually involving a kernel update ) the ID_FS_UUID for my
swap partition, as reported by vol_id, is changed so that it differs from the
value in fstab. To fix this I have to edit the fstab file and update the uuid
value.
If the uuid is
Problem persists in this kernel update (2.6.31-17) for the huawei e220 modem.
Kernel seems to recognise it as a storage device, then as a modem, then as a
storage device ...
I have attached the output of /var/log/messages
Lucky for me I still have kernel 2.6.31-11 with which the modem works han
Public bug reported:
Binary package hint: xorg
when the visual effects are disabled, the notifications which appear on the top
right of the screen are
garbled. Instead of text on a black background, a grid of different colours
appears. The same happens
with the system monitior, including the
** Attachment added: "systemManager.png"
http://launchpadlibrarian.net/34336023/systemManager.png
** Attachment added: "BootDmesg.txt"
http://launchpadlibrarian.net/34336024/BootDmesg.txt
** Attachment added: "CurrentDmesg.txt"
http://launchpadlibrarian.net/34336026/CurrentDmesg.txt
**
Public bug reported:
Sometimes if I run `pulseaudio -k` a few times, sound returns.
Sometimes if I run `sudo alsa force-reload`, sound returns.
Sometimes if I shutdown and start the laptop, sound returns.
This first occurred a few months ago when I was running 20.04, and I
upgraded to 21.10 in th
15 matches
Mail list logo