Oh my goodness this is old. I have no recollection how I got around it. I
probably just trashed the installation and loaded clean. Might as well
close this as 'too old, irrelevant now'
--
Can't upgrade Kubuntu Feisty to Gutsy
https://bugs.launchpad.net/bugs/223206
You received this bug notifi
Confirmed. New install of Kubuntu 8.10. Updated to current on all packages.
`sudo apt-get install xastir` then `xastir &` launched the program. After
configuring my station location, I enabled tigermap.geo, and immediately got
the error mentioned above in the konsole window from which I laun
Well, recompiling from source didn't work for me:
sudo apt-get build-dep xastir
sudo apt-get source xastir
sudo chown -R rtg.rtg xastir-1.9.2/
cd xastir-1.9.2
./configure
make
ends with:
map_tif.c:1312: error: ‘TIFFTAG_PHOTOMETRIC’ undeclared (first use in this
function)
map_tif.c:1312: error:
Found the problem. Ubuntu (and I'm told other Debian derivatives)
installs libgeotiff in a non-standard location, so when compiling under
ubuntu, an override is necessary at the './configure' step:
./configure CPPFLAGS="-I/usr/include/geotiff"
Reference:
http://www.xastir.org/wiki/index.php/HowT
Thank you kko for confirming this bug and parsing the evidence out of the
log file for easy readibility.
I gave a suggested resolution in one of my first posts: A one-line warning
in the web page, instructing the user to use the server update process
from a console TTY, not from an terminal win
On Mon, 6 Oct 2008, kko wrote:
> "So why does it take six months to get a one-line change made to a single
> web page???"
>
> Hmm well, there's a limited number of eyes looking at bugs and of people
> fixing things, so patience is a virtue. You did mention you're impatient
> though. :-)
Yes, I
*** This bug is a duplicate of bug 221382 ***
https://bugs.launchpad.net/bugs/221382
I did `apt-get remove audacious-plugins`, which also forced the removal of
audacious and ubuntustudio-audio. I then ran `do-release-upgrade`, which
completed the upgrade process. I then did `apt-get instal
I'm happy to report that after upgrading my ubuntustudio install on an
emachines M6810 to hardy (amd64), I got a full-brilliance display on the
first boot!
--
LCD Brightness on Laptop Always Set Very Low at Boot
https://bugs.launchpad.net/bugs/12637
You received this bug notification because yo
On Fri, 20 Mar 2009, Adam Plumb wrote:
> Maybe someone else with an M6810 (would be rare, the laptop is almost 5
> years old) can confirm. Otherwise, I would call this one fixed for
> jaunty.
>
I have an M6810 running Ubuntustudio 8.04. The -rt kernel was reportedly
broken in 8.10, so I was a
Verified again with kernel 2.6.15-25-686
--
Fail to boot smp kernel
https://launchpad.net/bugs/24533
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
I stumbled on a few blog posts, writing about a fix for Ubuntu Bug #36596 and
#38802, (note: the fixes here may also apply to bug #16873, #38181 and #47775).
My system also is equipped with a Radeon 7000/VE, so I'm curious that this
bug, too, may be another manifestation of this same problem.
Verified - The problem still occurs with kernel 2.6.15-26-686.
I booted into a text console, then issued the startx command. the
system froze up as it got to the 'restoring session' phase of KDE
initialization.
--
Fail to boot smp kernel
https://launchpad.net/bugs/24533
--
kubuntu-bugs mailin
I found an old Matrox Millenium PCI video card, and swapped it into this
machine.
lspci reports it as:
VGA compatible controller: Matrox Graphics, Inc. MGA 2064W [Millennium] (rev 01)
With it, I've been able to boot the 686SMP kernel, and startx with KDE. It's
been running all of ten minutes no
Another data point: The system seems to be stable with the 686SMP kernel with
an ATI rage pro PCI video card installed:
VGA compatible controller: ATI Technologies Inc 3D Rage Pro 215GP (rev 5c)
Now, the question seems to be whether the bug is specific to the Radeon
7000 chipset, or possibly som
System booted and appears stable with X and KDE running. Current video card is:
VGA compatible controller: nVidia Corporation NV5M64 [RIVA TNT2 Model 64/Model
64 Pro] (rev 15)
So it isn't the AGP bus per se. Unfortunatly, I don't have a PCI version of
the Radeon 7000 card available, to see if
OK, here's the last video card in my drawer:
VGA compatible controller: nVidia Corporation NV11 [GeForce2 MX/MX 400] (rev
b2)
It's an AGP card, and the system appears stable running X and KDE.
So here's the bottom line: kernel 2.6.15-26-686, and at least four
earlier 686 kernels, lock up solid
On Wed, 20 Sep 2006, Antonio Ricardo Soares da Silva Correia wrote:
> Richard, perhaps you are right in what concerns the ATI 7000 but that
> doesn't explain why my system works flawlessly with the other
> distributions and only fails with (K)Ubuntu. Oddly enough, now, even the
> plain 686 kern
That's not the issue. the 386 kernel is the default, and is what I've been
running. The desire for a 686 non-SMP kernel is to determine if the
problem is with the 686 optimizations or the SMP code.
WHat I really want is for someone with knowledge of the kernel internals
to look at Paul's pat
On Thu, 21 Sep 2006, Ben Collins wrote:
> How about booting the 686 kernel with the nosmp on the boot command
> line?
That was suggested earlier, and I reported that it threw all kind of
wierd missing interrupt errors, finally giving up on mounting the disk,
and dropped me into busybox.
>
> A
I was also looking at the discussion on bug # 16873, which appears to be the
same problem, but they are looking at the radeon driver side rather than the
kernel, and they appear to have a patch that's looking promising, but it's edgy
only at this point. But a 'stable release' (does that mean dap
*** This bug is a duplicate of bug 221382 ***
https://bugs.launchpad.net/bugs/221382
That's not the point. Of course a reinstall works. But an upgrade is
supposed to work as well...
--
The update manager can't update Ubuntu 7.10 to 8.04
https://bugs.launchpad.net/bugs/188705
You received
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/13936782/Dependencies.txt
--
package update-manager 1:0.81.2 failed to install/upgrade: ErrorMessage:
SystemError in cache.commit(): E:Couldn't configure pre-depend
audacious-plugins for audacious-plugins-extra, probably
Public bug reported:
Binary package hint: update-manager
Attempting to upgrade ubuntustudio on AMD64 to Hardy. Went to bed when
it told me it needed four hours to download over 1000 packages. Got up
to this message.
ProblemType: Package
Architecture: amd64
Date: Sat Apr 26 02:11:26 2008
Distro
Just encountered this:
Upgraded my Kubuntu Dapper box to Hardy using update-manager -d. This box
had been set up with vnc support in xorg. Next time I attempted to connect
from my workstation in the garage(Kubuntu feisty using vncviewer), I can log
in, and get the desktop displayed, but with
Public bug reported:
Binary package hint: adept-updater
Adept offered me a version upgrade. I made sure I had refreshed the
repositories, and applied all available updates, then I asked for the
version upgrade. It showed me the release announcement for Gutsy, and
then told me it was downloading
Public bug reported:
I just upgraded from Dapper to Hardy (Kubuntu) using the command-line
process described on the web site.
Several issues actually:
part-way into the upgrade, it tells me that kdm has to be manually shut down
before it can proceed. Grrr! I'm running this in a root konsole
Issue #1, here's the web page I followed:
http://www.ubuntu.com/getubuntu/upgrading#head-db224ea9add28760e373240f8239afb9b817f197
Towards the bottom of that page, is the following:
Network upgrade for Kubuntu desktops (recommended)
To upgrade from Kubuntu 6.06 to 8.04 over the Internet, use the
Well, the first one was about manually configuring nut. There was
something about manually converting postgresql databases. There were lots
of errors from some perl module telling me that it couldn't set locale
because of some missing file, and listed three environment variables it
was trying
Here are the logs. The evidence is in apt-term.log, although it isn't
easy to see. It's surrounded by curses escape sequences...
--
Upgrade from kubuntu Dapper requires manual intervention and kdm shutdown
https://bugs.launchpad.net/bugs/223226
You received this bug notification because you ar
** Attachment added: "apt.log"
http://launchpadlibrarian.net/13983377/apt.log
** Attachment added: "apt-term.log"
http://launchpadlibrarian.net/13983378/apt-term.log
** Attachment added: "main.log"
http://launchpadlibrarian.net/13983379/main.log
** Attachment added: "main_pre_req.log"
** Description changed:
I just upgraded from Dapper to Hardy (Kubuntu) using the command-line
process described on the web site.
Several issues actually:
- part-way into the upgrade, it tells me that kdm has to be manually shut
down before it can proceed. Grrr! I'm running this in a
The bug was still present in the released version of feisty. I have not
tried installing any of the gutsy milestones, since that machine is in
'production' use right now. Perhaps if I could locate a spare drive sled
for it, I could again do test installs on it.
--
Touchpad not fully function
The original problem seems to have been fixed (fail to commit)
with todays' daily build (20070410), the 'version upgrade' problem is still
there, but different:
the message offering a new version is still there, but the 'next' button is now
labelled 'version upgrade' and is not grayed out. The me
see also bug #'s 104542 and 105139
--
Unable to commit changes
https://bugs.launchpad.net/bugs/103163
You received this bug notification because you are a member of Kubuntu
Team, which is a bug contact for adept in ubuntu.
--
kubuntu-bugs mailing list
kubuntu-bugs@lists.ubuntu.com
https://lists
Sorry, I got that 'demidecode' from a comment/info request on a similar
bug #81548...
--
Won't return from suspend on emachines M6810
https://bugs.launchpad.net/bugs/103719
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu
Ditto on another system with ATI Radeon RV100 QY(Radeon 7000/VE)
--
Video not detected Hardy KDE 4
https://bugs.launchpad.net/bugs/196858
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubun
I think you missed the first line of my report. I was runing a daily build
of the LiveCD, and the problem was manifest by X not coming up at all. I
won't be able to run a browser to log into launchpad, so I'll try it
again, and see if I can find those files and ftp or sneakernet them to
anothe
On Sat, 1 Mar 2008, Dereck Wonnacott wrote:
> Please attach your X server configuration file
> (/etc/X11/xorg.conf)
> and X server log file (/var/log/Xorg.0.log) to the
> bug report
/etc/X11/xorg.conf is present, but is a zero-length, empty file.
/var/log/Xorg.0.log is non-existant, as is any
Here's the dmesg output. see file attached.
These are the lines that look to me to be video related, and they don't
say anything unusual to me:
/snip/
[ 24.140033] Console: colour VGA+ 80x25
[ 24.140042] console [tty0] enabled
/snip/
[ 25.865200] Boot video device is :01:00.0
/snip/
I had also reported and confirmed this bug earlier. This weekend, I built
up a test system (Dual PIII-550 w/ Radeon 7000 video) I booted it with a
Hardy Alpha 4 server(already on HDD), then used aptitude to install
kubuntu-desktop. I was able to startx, and the KDE desktop came up fine.
I th
Don't do that! The bug is still there in Gutsy.
--
Dim LCD backlight on boot
https://bugs.launchpad.net/bugs/88691
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-bugs@lists.ubuntu.com
https://l
*** This bug is a duplicate of bug 12637 ***
https://bugs.launchpad.net/bugs/12637
I missed your request for info a month ago. I'm downloading hardy alpha 4
now, will test against that.
I've also marked this as a duplicate of bug#12637, which appears to be
the same problem on the gateway
Just booted the Hardy alpha 4 live CD (Kubuntu amd_64), and the LiveCD session
booted up normally, without dimming the LCD!
Since this is a working laptop now, I don't want to do a complete reinstall
with the hardy alpha. Is there a way I can install just the kernel package
from the hardy CD
Here's some more info. I went to system/administration/services, and disabled
gdm, thinking I'd reboot to a console, just to see if this was a kernel
problem, or possibly an xorg problem, since it's happening just milliseconds
before the screen blanks to switch to X.
Well, that wasn't clean a
Well, I saw the problem with Ubuntu, Kubuntu, and Ubuntustudio x86_64 at
the 7.10 release, so I don't think it's a desktop issue. Also, last night
I managed to boot clumsily without X and gdm, and I also saw the problem
when there was no X launching, so that kinda confirms it for me that its
n
Public bug reported:
Hardy daily build 20080220 KDE 4.0
Booting liveCD on AMD Duron 1.3G, 256M system with SIS video, the system
appears to hang before KDM comes up. Looking closer, I found a shell prompt
buried within the boot messages, so I decided to investigate. Neither dmesg
nor tail /va
On Thu, 20 Sep 2007, Robert Drake wrote:
> If I get the chance, I'll start throwing "got here" kprintf's in the
> kernel in places before "Kernel is Active" to see what I find.
>
On my emachines M6810, the 'Kernel alive' message comes on bright,
followed by a message beginning 'kernel mapping
With the feisty release kernel (2.6.20-15) The problem is still there.
As well as an additional problem: I can hibernate the machine just
once. After returning from hibernate, the system is in a 'screen
locked' state, which wakes up with a stroke on the touchpad, and I can
unlock the screen and
I don't know if I'm up to the challenge of compiling my own kernels. I
haven't done that since about 1.2.x sometime... And that was just to
config in a driver. I'm an old PL/I & COBOL programmer, and quite 'C'
challenged.
One item of note: this happens with amd_64 kernels only. Last week,
Public bug reported:
Binary package hint: linux-source-2.6.20
My AMD_64 laptop, an emachines M6810, refuses to wake up from suspend. I was
tracking bug # 74877, but when that was apparently fixed at 2.4.20-14 for the
HP laptops, and I continue to have the problem, I was asked to open a new one
/var/log/kern.log.0
** Attachment added: "kern.log.0"
http://librarian.launchpad.net/7179507/kern.log.0
--
Won't return from suspend on emachines M6810
https://bugs.launchpad.net/bugs/103719
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact f
[EMAIL PROTECTED]:~$ uname -a
Linux rtg-laptop 2.6.20-14-generic #2 SMP Mon Apr 2 16:32:46 UTC 2007 x86_64
GNU/Linux
[EMAIL PROTECTED]:~$ sudo lspci -vv >kerndebug.txt
[EMAIL PROTECTED]:~$ sudo lspci -vvn >>kerndebug.txt
[EMAIL PROTECTED]:~$ sudo demidecode >>kerndebug.txt
sudo: demidecode: comman
** Attachment added: "dmidecode.txt"
http://librarian.launchpad.net/7192533/dmidecode.txt
--
Won't return from suspend on emachines M6810
https://bugs.launchpad.net/bugs/103719
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
with the 20070405 build, I experienced the same problem, and one additional
problem: The CDR came up with DMA support off.
WHen I started k3b, it notified me that DMA was off, but for the next few
minutes, my system was incredibly unresponsive. Even the cursor! It took me
several minutes to mo
Public bug reported:
Binary package hint: ubiquity
Booted from Feisty desktop amd64 daily build 20070406, after frist
having verified CD integrity. Clisked on 'install' icon on desktop.
Received crash message.
ProblemType: Crash
Architecture: amd64
Date: Sat Apr 7 04:51:31 2007
DistroRelease:
** Attachment added: "Dependencies.txt"
http://librarian.launchpad.net/7193329/Dependencies.txt
** Attachment added: "ProcMaps.txt"
http://librarian.launchpad.net/7193330/ProcMaps.txt
** Attachment added: "ProcStatus.txt"
http://librarian.launchpad.net/7193331/ProcStatus.txt
** Attachm
here's the 'debug info' produced by k3b while trying to burn the 0407
daily build.
System
---
K3b Version: 1.0
KDE Version: 3.5.6
QT Version: 3.3.7
Kernel: 2.6.20-14-generic
Devices
---
Slimtype COMBO LSC-24082K JBK2 (/dev/hdc, ) [CD-R, CD-RW, CD-ROM,
same - immediate crash as KDE starts. First launch of daily build 20070407 on
amd64
backtrace attached
** Attachment added: "kdesktop.backtrace"
http://librarian.launchpad.net/7214003/kdesktop.backtrace
--
KDesktop crash on KDE-initiated restart (SIGSEGV 11)
https://bugs.launchpad.net/bugs/
I ran dpkg-reconfigure -phigh xserver-xorg (see bug #89289 ) and
rebooted. X and kde came up with the right resolution, and no crash
this time.
--
KDesktop crash on KDE-initiated restart (SIGSEGV 11)
https://bugs.launchpad.net/bugs/71856
You received this bug notification because you are a memb
Public bug reported:
trying to compile Maiko's JNOS2 package:
www.physics.umanitoba.ca/~maiko/jnos2_fc5src.tar.gz
I get the following errors on both Dapper and Edgy systems:
gcc -DUNIX -g3 -DDEVELOPMENT -DDEBUG -W -Wimplicit -Wreturn-type -Wswitch
-Wpointer-arith -Wcast-qual -Wcast-align -Wagg
*** This bug is a duplicate of bug 68267 ***
Which tool did you use?
I had this experience with adept, and I was successful in completing the
update with 'apt-get upgrade' on the command line.
--
Kubuntu 7.04 chash at update
https://launchpad.net/bugs/87814
--
ubuntu-bugs mailing list
ubun
I installed Kubuntu Herd 4 AMD_64 on an emachines M6810 (amd64 w/ATI radeon
9600), and experience this same problem. So it may be a larger X problem, not
just nv.
Initial install selected 1024x768, when I have a 1280x800 widescreen.
I changed resolution to 1280x768, and the 'test' showed a scr
Confirmed on emachines M6810 with ati Radeon 9600 and 1280x800 LCD
--
graphics card has wrong resolution and no acceleration
https://launchpad.net/bugs/88670
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Public bug reported:
Binary package hint: ubiquity
Installing Kubuntu Herd 4 AMD_64. Selected manual partitioning. qtparted
opened in a separate window, very small. Had to expand window in order to use
it. When I finished setting up my partitions, I closed the qtparted window,
revealing th
Public bug reported:
Binary package hint: xorg
Feisty Herd 4 on emachines M6810 (Radeon Mobility 9600). On boot, screen
is very dark. I must use fn-F8 hotkey to raise backlight brightness in
order to make screen usable.
This is both in 'liveCD mode, and after installation to HD.
** Affects: xo
Public bug reported:
Binary package hint: xorg
Feisty Herd 4 (X86_64) on emachines M6810. Synaptics touchpad only
partially works. Cursor movement OK. single-tap sometimes works, but
not on all buttons. Double-tap/drag does not work. Scroll area at
right of touchpad not recognized as a scrol
Public bug reported:
Binary package hint: adept
after installing Kubuntu Herd 4 X86_64 on emachines M6810, I ran adept-updater
by clicking on the quickstart notification icon next to the clock.
It presented me with 200+ updates. Downloading them seemed to go quickly,
but as they were being
Additional info:
I just ran adept from the K menu, ran 'fetch updates' and learned that adept
is upgradable. I requested installation, and again got the same error.
The popup window is labelled 'Debconf on rtg-laptop', the message requests an
integer between '-20 and 19', and the active butto
I keep trying...
I ran 'apt-get install adept' from a root shell, and it told me that adept
was already at the current level. It then went on to tell me that there were 5
packages not fully installed, and it gave me 5 'setting up...' messages for
x11-common, libxau6, libxdmcp6, libxcb1, libxc
I ran 'apt-get install apt' from a root console. It upgraded 11 packages,
including apt-utils, adept-manager, adept-installer, adept-updater, and
adept-notifier.
Then I tried another adept run. 'Full upgrade' told me it would upgrade 195
packages, but when I clicked 'apply changes', the adep
Back to the root console
apt-get update;apt-get upgrade; apt-get dist-upgrade' followed by a reboot, and
now I can use adept again. I successfully installed the xastir package, as
well as the 10 dependencies it pulled in.
SO this was apparently fixed by one of the ~200 packages updated since t
Bug confirmed still present on emachines M6810 with kernel 2.6.20-9 x86_64
(Feisty herd 4+)
AMD Athlon 64 3200+; ATI Radeon mobility 9600
Just before it dimms, the graphical screen is replaced by a text screen, and
I see the words 'Kernel is Active' briefly appear at the bottom.
--
LCD Brigh
I'm on herd 4, AMD_64 with ATI radeon 9600. While I've messed with the
X config using the system settings GUI, so I can't be absolutely sure,
here is the relevant section of xorg.conf.1, which I think is the
original one from the installation:
Section "InputDevice"
Identifier "Confi
More info:
initial install mis-identified the touchpad. This might explain the limited
functionality. Snippet from xorg.conf:
Section "InputDevice"
Identifier "Configured Mouse"
Driver "mouse"
option "CorePointer"
option "Device" "/dev/input/mice"
option "Protocol" "ExplorerPS/2"
o
On Fri, 2 Mar 2007, Duncan Lithgow wrote:
> Richard, please make a seperate bugreport for your problem. If they're
> similar then you can mention that here.
>
>
I did:
#88691 (LCD backlight set to dim at boot)
#88692 (touchpad not fully functional)
--
Wrong resolution with an nvidia GeForceG
Done, #89289
--
Wrong resolution with an nvidia GeForceGo 7300
https://launchpad.net/bugs/79016
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Public bug reported:
Binary package hint: xorg
Initial install of Feisty Herd 4 on emachines M6810 showed problems with
hardware detection in xorg:
LCD is 1280x800, but X came up as 1024x768
KCD backlight very dim on boot (Bug # 88691)
Touchpad not fully functional (Bug #88692)
I had init
Still happening on Feisty herd 5 Kubuntu live CD.
--
LCD Brightness on Laptop Always Set Very Low at Boot
https://launchpad.net/bugs/12637
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Installing herd 5 -
Apparently a change has been made to ubiquity. WHen I select 'manual
partitioning', I now get a disk summary within the ubiquity window, that looks
different from gparted or qtparted.
Since I didn't really want to repartition, I had to poke a bit before I
discovered th
Public bug reported:
Binary package hint: ubiquity
While installing Herd 5 (Kubuntu X86_64), after partitioning, at about the 70%
mark while installing files, my screen went from the X desktop, to a text
console (probably pty0, it had the kernel messages on it, with 'Kernel active'
at the bott
Public bug reported:
Feisty Herd 4 and Herd 5 X86_64
When restarting a liveCD session, or restarting into the freshly-installed
system, theCD fails to eject as earlier releases did.
I'm left with a message on the screen that tells me to remove the CD and
press enter.
When I press the CD tray
*** This bug is a duplicate of bug 85979 ***
Fresh install of Feisty herd 5 X86_64
Adept updater tells me there are 115 updates, two packages to remove.
After downloading, window shows a progress bar labelled 'preparing...' at 0%.
A second window opens labelled 'Debconf on rtg-laptop' with the
OK, here's a herd 5 update:
LiveCD, as well as initial install gave me 1024x768. xorg.conf is attached.
At a suggestion I read on another (nv, but similar) bug report, I switched to a
text console, logged in as root, ran dpkg-reconfigure -phigh xserver-xorg, then
rebooted. It came up in the p
Here's the xorg.conf as produced by dpkg-reconfigure -phigh xserver-
xorg.
** Attachment added: "xorg.conf produced by dpkg-reconfigure"
http://librarian.launchpad.net/6634504/xorg.conf.reconfigure
--
Wrong resolution on initial install - Radeon 9600 Laptop LCD
https://launchpad.net/bugs/8928
Herd 5 now:
same problem on initial install. While researching another problem (#89289),
I was prompted to run 'dpkg-reconfigure -phigh xserver-xorg' This re-created
the xorg.conf file, and did indeed detect the synaptic touchpad.
The vertical scroll area and the double-tap-and-drag selection
My second attempt to install went without a hitch, as I forced myself to
sit on my hands and not explore the LiveCD system while ubiquity was
busy...
--
Screen blanks, locks during install of herd 5
https://launchpad.net/bugs/89878
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
http
Public bug reported:
Fresh install of Feisty herd 5. installed jackd, jackctl. Modprobe
raw1394, jackd -d freebob produced this SYSSEGV immediately.
ProblemType: Crash
Architecture: amd64
Date: Mon Mar 5 18:46:17 2007
Disassembly: 0x2ad1ae10:
DistroRelease: Ubuntu 7.04
ExecutablePath: /usr
** Attachment added: "CoreDump.gz"
http://librarian.launchpad.net/6639670/CoreDump.gz
** Attachment added: "Dependencies.txt"
http://librarian.launchpad.net/6639671/Dependencies.txt
** Attachment added: "ProcMaps.txt"
http://librarian.launchpad.net/6639672/ProcMaps.txt
** Attachment ad
Also experiencing this problem on an emachines m6810 AMD_64 with ATI Radeon
9600.
Suspend is slow, but eventually goes down, leaving power light blinking. When
I touch any key, the power light comes back on solid, but the video never comes
back. Pwr cycle and reboot is necessary.
--
Regress
another note: jackd -d alsa did not crash, in fact I was able to start
ardour and make and play back a simple recording.
At the time of the crash, no firewire audio device was plugged in. I
don't actually own any device supported by freebob, I was trying to get
the software loaded and configured
*** This bug is a duplicate of bug 68267 ***
I see someone marked this as a duplicate of #68267.
WHy would anyone think this is a problem with x11-common?
It seems clear from my experience, and comments on others also marked as dups
to 68267, that the problem clearly happens when running adept
Actually, I wasn't able to get this to repeat. It occurred on an AMD64
with 512MB RAM as I was exploring the K menu (not actually opening any
apps) while ubiquity was doing the initial load. The system didn't crash
- just the screen went blank. I could see the hdd light blinking, so the
file
*** This bug is a duplicate of bug 68267 ***
I got the error three times:
First, when the adept window just said 'preparing...'
Second, when adept said 'preparing update for x11-common'
and a third time, soon after, when I didn't catch the package name in question.
I also got it when using adept
OK, Here's a copy of casper.log from a live session
Kubuntu daily build 20070401 amd_64
** Attachment added: "csper.log from live session"
http://librarian.launchpad.net/7099830/casper.log
--
Wrong resolution on initial install - Radeon 9600 Laptop LCD
https://launchpad.net/bugs/89289
--
ub
I've been having this same problem occur with Feisty, from herd 4 thru today's
daily build (20070401) I'm running Kubuntu AMD_64.
laptop-detect returns true.
on herd-5,the last one I installed, dpkg --reconfigure xserver-xorg did
correctly detect both the touchpad and the monitor, giving me the p
Confirmed again on Kubuntu Feisty daily build 20070401 amd_64
--
LCD Brightness on Laptop Always Set Very Low at Boot
https://launchpad.net/bugs/12637
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Public bug reported:
Binary package hint: ubiquity
This appeared as I selected 'manual partition' in step 4 of the
installer.
Traceback (most recent call last):
File "/usr/lib/ubiquity/ubiquity/frontend/kde-ui.py", line 2559, in data
return QVariant(item.data(index.column()))
File "/usr/
** Attachment added: "/var/log/partman"
http://librarian.launchpad.net/7099954/partman
--
Installer crashed at 'manual partition'
https://launchpad.net/bugs/99825
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
** Attachment added: "/var/log/syslog"
http://librarian.launchpad.net/7099956/syslog
** Tags added: regression
--
Installer crashed at 'manual partition'
https://launchpad.net/bugs/99825
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubun
Confirmed: Still uninstallable on Kubuntu Feisty daily build 20070322.1
amd_64
--
[UNMETDEPS] Uninstallable on AMD64
https://launchpad.net/bugs/32460
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
1 - 100 of 116 matches
Mail list logo
