Public bug reported:
After performing an upgrade from 12.4 to 13.10 on an x86_64 system, each
login by my account is reporting this error.
ProblemType: Package
DistroRelease: Ubuntu 13.10
Package: ca-certificates 20130610
ProcVersionSignature: Ubuntu 3.11.0-15.22-generic 3.11.10
Uname: Linux
When it was happening to me, I believe an alternative was to login via SSH
and kill the X11 desktop session (including the display driver). In my
case it was usually quicker to login and just issue a reboot command.
FWIW, after getting the latest NVidia video driver for my three-screen
system
I've been running Oneiric since December use it as primary workstation
weekdays, two NVidia cards driving three screens and I haven't had the
stuck mouse issue. (Though I had applied the PPA version on my
previous workstation so the problem has been a distant memory for me
for quite a while...)
On Tue, Jan 31, 2012 at 07:18, Hugh Whinfrey h...@svarsmaal.dk wrote:
My system has 2 graphics cards and 3 screens. The cursor gets stuck
between screens (either pair) several times a day. It only started
happening after I upgraded to Lucid. It is beyond annoying to have to
reboot the system
*** This bug is a duplicate of bug 650539 ***
https://bugs.launchpad.net/bugs/650539
Is this the same bug as filed in this bug report:
https://bugs.launchpad.net/ubuntu/maverick/+source/xorg-server/+bug/650539
I'm in the process of installing the temporary fix the other bug report
lists
If it helps any, I too am getting this and I've been using gcore to
generate a core file from the Xorg process.
I have two nVidia G-series video cards:
* GeForce 9400 GT - this drives screen 1 (middle)
* GeForce 8600 GT - this drives screen 0 and screen 2 (left and right)
My xorg.conf section
I too am getting this error. Very easy to reproduce on my system: put
an MP3 into the playlist (right-click the song, choose Append to
Playlist), then right-click on the new playlist entry and choose
Remove from playlist. Happens about 50% of the time.
Here's the backtrace from my system
I see that the HDX18 has an updated F.23 BIOS released on 5/26. I'll be
applying it tonight to see if it resolves the issues I'm having.
I'll report with my findings.
DanL
* *** *** * *** **
Quis custodiet ipsos custodes? (Who can watch the watchmen?) -- from the
HP needs proof it's a BIOS problem, correct?
If someone can reverse-engineer the F0.9/F0.11 BIOS and compare it to
the F.21 bios (that freak007 mentioned fixing his laptop on 2008-12-02),
then we can possibly work through their team to show how this bug exists
in other models that don't have the
Unfortunately TwinView doesn't work for those of us with three+
monitors (TripletView anyone?).
Dan
(Or am I missing something with TwinView to make it work with my two
NVidia cards -- GeForce 8600 GT, and older GeForce2 MX/MX 400? I'm
using the NVidia driver for the 8600, and the opensource nv
On Fri, Jan 16, 2009 at 1:48 PM, chimaster sp...@queenstown.com wrote:
Please post performance improvements that you implemented, I'd love to
get a little more performance out of my Nvidia 9500GT.
Lets keep this trouble ticket on track and not post speed improvments.
Travis: Can you tell us
@Reuben Firmin (and other fellow KDE users).
I found a work-around for us, but it's a pain and only works if you have
both Gnome and KDE available on the system.
1: Switch to a text console (Control-Alt-F1) and login as your user.
2: Run killall kwin to kill the KDE Window manager.
3: Run
Mr. Browne: Thank you!
I walked through these steps when my system was functioning, and succeeded
in re-creating the error (I lost mouse clicks after step 4.).
I was able to 'fix' it by following the steps. Maybe a developer can use
these to re-create the problem with the mouse input?
Dan
My
Until this is resolved, can someone post a series of steps to downgrade
just the xorg drivers under Intrepid?
Dan
(This happens to me too - I'm testing to see if window managers make a
difference. Gnome happened after about 90 minutes, KDE took a few
hours, I'll try E16 next..)
--
X.org will
On Sun, Nov 2, 2008 at 11:15 AM, Erica [EMAIL PROTECTED] wrote:
Hmmm. I had booted into low-graphics mode after failing to manually
install the nvidia driver, when the third-party drivers icon appeared in
my taskbar. It offered me two proprietary nvidia drivers to install - I
chose the
Public bug reported:
Binary package hint: ca-certificates-java
In general, the keytool is erroring out when it trys to add
certificates during the upgrade process.
This is returned by apt-get update:
Setting up ca-certificates-java (20080712ubuntu2) ...
creating /etc/ssl/certs/java/cacerts...
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/18885345/Dependencies.txt
** Attachment added: DpkgTerminalLog.gz
http://launchpadlibrarian.net/18885346/DpkgTerminalLog.gz
--
package ca-certificates-java 20080712ubuntu2 failed to install/upgrade:
subprocess
Second confirmation of 64bit Kubuntu 8.10.
--
kblueplugd crashed with DBusException in call_blocking()
https://bugs.launchpad.net/bugs/279983
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
*bump*
Any update on this? Last night I upgraded from 8.04 to 8.10 and I'm
running into this issue too.
I'm running kernel linux-image-2.6.27-4-generic and trying to install
NVIDIA-Linux-x86_64-177.70-pkg2.run.
Dan
--
Ubuntu 8.04 server kernel / Xen enabled / Nvidia problem
Is there any update on this issue? My workstation (AMD, x86_64, NVidia
video card) has been exhibiting the same issue for quite a while too.
Is there any additional debugging information anyone needs?
--
Lost window decorations in KDE 4
https://bugs.launchpad.net/bugs/228758
You received this
I think there is more to it than this. I found bug #204728 first by
searching for the error message (KLauncher could not be reached via
D-Bus, error when calling start_service_by_desktop_path: empty).
Unfortunately, my error occurs right as KDE4 is starting up, not when
starting Kate. If I
My issue resolved itself after I updated my drives flash version. Check
with your manufacturers to see if there is a later version if you're
experiencing problems.
Dan
--
Quis custodiet ipsos custodes? (Who can watch the watchmen?) -- from the
Satires of Juvenal
I do not fear computers, I fear
I agree. For my use, I need to VPN into work/clients to allow me to bring
up XWindows displays, but I also need to surf the web to research answers.
I've got into the habit of manually adding my ISP's DNS servers into the
/etc/resolv.conf file but it's a royal pain.
** Attachment added: unnamed
Public bug reported:
Binary package hint: update-manager
Apparently the libxml-simple-perl and libxml-sax-perl packages gave the
updater issues. No other errors aside from the Errors were encountered while
processing message.
List of packages:
xl2tpd
l2tpd
libxml-sax-perl
libxml-libxmml-perl
This is still happening on my Gutsy release. I had to remove the file
in /var/lib/apt/lists/partial, and the update worked. I'm running apt
0.7.6ubuntu14.1, and I see the link (by Robert Coup) shows this being
fixed in apt 0.7.7 - when is 0.7.7 getting pushed into the Gutsy
distribution?
Dan
The setting changes (above) plus the latest kernel update (now running
2.6.22-14-generic) didn't fix this.
--
Feisty freeze, kernel (?) tries to access DVD drive
https://bugs.launchpad.net/bugs/75295
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug
On my setup I can normally hit the eject button on the DVD drive after
it has locked up between the burn and verify state, and that normally
returns the system to normal (of course it can't verify then).
I'm going to test these DMA settings tonight (/dev/hdb is my DVD):
1: hdparm -d 1 /dev/hdb
2:
On Jan 9, 2008 12:29 AM, tad1073 [EMAIL PROTECTED] wrote:
From the Ubuntu boot screen I selected Check CD for Defects and got
the errors listed below:
[364.283722] ata1.01: Exception Emask 0x0 Sact 0x0 Serr 0x0 action 0x2
Frozen
[364.283771] ata1.01 (BMDMA stat 0x44)
[364.283822] ata1.01:
Capt. Salty: I agree.
Tad: If the CD passes the check on a different system, then I would suspect
the CD-ROM drive on your system. The original problem this thread was about
was specifically the hard-drive controller being recognized correctly
*after* installation.
From what you've told us, I'd
Same here - fresh install (reformatted HDD) and Adept Manager (using
kubuntu) keeps pointing to a new version.
--
version upgrade available after upgrade
https://bugs.launchpad.net/bugs/154213
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact
*** This bug is a duplicate of bug 153889 ***
https://bugs.launchpad.net/bugs/153889
The head of this report says it is marked as a duplicate of bug
#153889, but I beg to differ.
The problem that I'm having is that I downloaded the Gutsy/7.10 release
ISO image, burned a CD, and then did a
*** This bug is a duplicate of bug 110585 ***
https://bugs.launchpad.net/bugs/110585
On Wed, October 17, 2007 08:34, Ben Collins wrote:
Not sure we can fix this reliably. The problem isn't that cpqarray isn't
in the initramfs, it's the fact that it overlaps with sym53c8xx driver
on two
On Mon, September 17, 2007 19:39, Jonathan Jesse wrote:
I noticed the last update on this bug was 2007-03-09 and I am wondering
if you are still having problems with amarok crashing? Can you please
update the status of this bug?
Not recently - my main workstation runs Amarok most of the day
I was having a similar issue, but a solution in this bug report fixed it
for me:
https://bugs.launchpad.net/ubuntu/+source/initramfs-
tools/+bug/99439/comments/1
[Quote]
Try adding /sbin/udevsettle --timeout=10 in /usr/share/initramfs-tools/init
before line:
log_begin_msg Mounting root file
Public bug reported:
Binary package hint: python-xen-3.1
During normal apt-get update process, it was failing in Setting up
debconf. See
http://ubuntuforums.org/showthread.php?p=3092478#post3092478;.
This was the error message:
1 Setting up debconf (1.5.14) ...
2 Compiling
On Tue, July 17, 2007 09:52, Colin Watson wrote:
Any luck with this?
Sorry, no I haven't. I ended up manually partitioning the drive and
moving on from there.
Dan
--
Crash when getting to the partition disk screen.
https://bugs.launchpad.net/bugs/94970
You received this bug notification
I was having a similar problem too (the booting issue, not the USB
keyboard issue). It turned out to be a race condition within the
init script the system was running on boot. The md weren't getting
built quick enough before the boot process tried to use them.
Here is what I did:
1: Edit the
Public bug reported:
Binary package hint: firefox
Don't know how to reproduce this. I keep up-to-date via apt-get
update/upgrade on a regular basis. System is stable in all other
respects.
ProblemType: Crash
Architecture: i386
Date: Tue May 8 10:18:03 2007
DistroRelease: Ubuntu 7.04
** Attachment added: CoreDump.gz
http://librarian.launchpad.net/7589436/CoreDump.gz
** Attachment added: Dependencies.txt
http://librarian.launchpad.net/7589437/Dependencies.txt
** Attachment added: Disassembly.txt
http://librarian.launchpad.net/7589438/Disassembly.txt
** Attachment
*** This bug is a duplicate of bug 78725 ***
https://bugs.launchpad.net/bugs/78725
I believe you'll want to login to this bugs web page:
https://bugs.launchpad.net/bugs/113597
When you get on, follow the Unsubscribe action on the left side of the
window.
Whenever you submit a bug-report to
I too encountered this error - K3b had been working well the last time I burned
a CD (4-6 weeks ago) and I have been running Feisty release candidates since
January I believe.
When I re-inserted the CD and re-ran the wodim command:
/usr/bin/wodim -v gracetime=2 dev=/dev/hdc speed=8 -dao
{touching bug to enable e-mail about changes option. -Dan}
--
Regression: k3b fails to verify
https://bugs.launchpad.net/bugs/103558
You received this bug notification because you are a member of Kubuntu
Team, which is a bug contact for k3b in ubuntu.
--
kubuntu-bugs mailing list
[EMAIL
I believe this crash happened because I was running it as a normal user,
not as root via sudo.
Can anyone confirm?
Dan
- - - -
Wait for that wisest of all counselors, time. -- Pericles
I do not fear computers, I fear the lack of them. -- Isaac Asimov
--
[apport] oem-config crashed with
** Attachment added: Dependencies.txt
http://librarian.launchpad.net/7458666/Dependencies.txt
** Attachment added: ProcMaps.txt
http://librarian.launchpad.net/7458667/ProcMaps.txt
** Attachment added: ProcStatus.txt
http://librarian.launchpad.net/7458668/ProcStatus.txt
** Attachment
Public bug reported:
Binary package hint: oem-config
Ran oem-config and it crashed right after selecting timezone (Chicago).
ProblemType: Crash
Architecture: i386
Date: Sat Apr 28 15:19:41 2007
DistroRelease: Ubuntu 7.04
ExecutablePath: /usr/sbin/oem-config
InterpreterPath: /usr/bin/python2.5
Killercow wrote:
Dan,
My install did a 2.6.17-14 install.
I also tried a 7.04 feisty install but that livecd couldn't recognize the
array size
The simplest solution is to add cpqarray to the
/etc/mkinitramfs/modules file.
I.e.
# cat /etc/mkinitramfs/modules
# List of modules that
** Attachment added: CoreDump.gz
http://librarian.launchpad.net/7122289/CoreDump.gz
** Attachment added: Dependencies.txt
http://librarian.launchpad.net/7122290/Dependencies.txt
** Attachment added: Disassembly.txt
http://librarian.launchpad.net/7122291/Disassembly.txt
** Attachment
Public bug reported:
Might not be related, but the NetworkManager died at the same time
Mondo archive died. Will try to re-produce at a later date.
ProblemType: Crash
Architecture: i386
Date: Sun Apr 1 11:11:01 2007
DistroRelease: Ubuntu 7.04
ExecutablePath: /usr/sbin/NetworkManager
Package:
On Wed, March 28, 2007 05:21, Killercow wrote:
Rumor was wrong,
cpqarray still breaks on 6.10
I tried both the alternate cd, and normald server install, both don't
work.
This was testen on a compaq smartarray 5300 controller inside a DL380 g1
My recent install of 6.10 put on a 2.6.15
On Wed, March 28, 2007 05:21, Killercow wrote:
Rumor was wrong,
cpqarray still breaks on 6.10
I tried both the alternate cd, and normald server install, both don't
work.
This was testen on a compaq smartarray 5300 controller inside a DL380 g1
My recent install of 6.10 put on a 2.6.15
** Attachment added: CoreDump.gz
http://librarian.launchpad.net/7030741/CoreDump.gz
** Attachment added: Dependencies.txt
http://librarian.launchpad.net/7030742/Dependencies.txt
** Attachment added: Disassembly.txt
http://librarian.launchpad.net/7030743/Disassembly.txt
** Attachment
Public bug reported:
Binary package hint: heliodor
Tried using Beryl as my window manager with the X.org/ATI drivers
(Radeon Mobility 9600 video card). Crashed with no other information
on the screen.
ProblemType: Crash
Architecture: i386
CrashCounter: 1
Date: Tue Mar 27 20:06:00 2007
I just went through the same problem on a DL380 G1. The problem is that
the cpqarray module needs to be part of the initrd image. You either
need to recompile the kernel with this driver built in (slow on our
older hardware), or rebuild the initrd to include this driver (much
faster).
I
P.S. It appears that this wasn't an issue until the 2.6.15 kernel, and
from what I hear this has been fixed in 2.6.18. I wanted to stick with
the stock repository packages so I just updated the modules file -- hope
this fix sticks the next time the kernel is updated. :)
--
Installing Edgy on
Rumor has it that there was a patch included in 2.6.18 that fixed the
cpqarray issue - any chance that patch can get backported to 2.6.15?
--
Boot fails after 6.06 server install on Compaq Proliant DL360
https://launchpad.net/bugs/47526
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
On Fri, March 23, 2007 04:52, Colin Watson wrote:
Could you please attach /var/log/syslog and /var/log/partman to this
bug, following the directions in
http://wiki.ubuntu.com/DebuggingUbiquity/AttachingLogs? Thanks in
advance.
I was installing via the Kubuntu Live CD at the time, and I
On Fri, March 23, 2007 06:56, Colin Watson wrote:
Could somebody get a log of this failure with DEBCONF_DEBUG=developer
set in the environment? It would help to see what's actually happening.
I will try to run adept_updater in the following manner:
sudo script -c ~/tmp/DebugAdept.sh
where
Public bug reported:
Binary package hint: ubiquity
I got into the Ubiquity partition screen the first time and chose next with
guided partitioning selected (it also selected my /dev/ida/c0d0 disk in my
Compaq DL380 with integrated hardware RAID SCSI controller). That crashed
after I hit
Mr. Holbach,
The crash dump submitted was automatically generated by the system.
If it happens again today I will try to send as much information as
possible.
Dan
On Tue, March 20, 2007 08:22, Daniel Holbach wrote:
** Tags added: need-i386-retrace
** Changed in: amarok (Ubuntu)
Public bug reported:
Binary package hint: amarok
There was other 'weirdness' on this system after updating to kernel
2.6.20-12-generic.
ProblemType: Crash
Architecture: i386
CrashCounter: 1
Date: Mon Mar 19 14:29:25 2007
Disassembly: 0xe410:
DistroRelease: Ubuntu 7.04
ExecutablePath:
** Attachment added: CoreDump.gz
http://librarian.launchpad.net/6860879/CoreDump.gz
** Attachment added: Dependencies.txt
http://librarian.launchpad.net/6860880/Dependencies.txt
** Attachment added: ProcMaps.txt
http://librarian.launchpad.net/6860881/ProcMaps.txt
** Attachment added:
I can confirm that this is happening on a fresh install of Kubuntu-Herd5
(downloaded via .torrent March 7).
I had just booted up the first time and ran Adept Manager to get the latest
updates (March 8 @ 18:41 GMT). After the downloads finished, it errored with
the screen shot here(also
I don't believe this is related to the exact package being installed,
rather the installer itself or a back-end process.
And the various tests for nice values (i.e. Pauls comment #8 :
https://launchpad.net/ubuntu/+source/xorg/+bug/68267/comments/8), is there
other code to ensure that the value
63 matches
Mail list logo
