And yes, xrandr at all times shows this:
andrew@desky:~$ xrandr --verbose
Screen 0: minimum 320 x 200, current 3840 x 1080, maximum 16384 x 16384
DisplayPort-0 connected primary 1920x1080+0+0 (0x5a) normal (normal left
inverted right x axis y axis) 480mm x 270mm
Identifier: 0x55
Been a while, but now that I'm on 21.10, colord is not picking up all
devices once again - just one monitor and printer...
andrew@desky:~$ sudo colormgr get-devices-by-kind display
[sudo] password for andrew:
Object Path:
Well, colord no one tracks bugs (and I see lot's of ancient and very
open bugs).
Seen a couple that may or may not be similar, and the bugs go all the
way back to 11.04 - so I guess I'm the only person in the entire world
experiencing this...
But in case not, this problem would have a downstream
Okay, if I do a reinstallion of colord, I can see both monitors and
actually set the profile on the second screen. I lose the printer
profile upon doing this. This works until next reboot and then
everything reverts (only see one monitor and the printer color
profiles).
--
You received this
>From system settings, I can see both monitors in Display configuration.
>From command prompt, I can see both displays when I use xrandr.
>From command prompt, I can only see one display when I use colormgr get-
devices-by-kind display
Did not have this issue with Kubuntu 20.10.
My notebook,
Public bug reported:
I just made the switch to 21.04, and I've immediatly run into problem
with color corrections.
In the Color Correction - System settings Module, I can only see and
apply a color profile to my first display on the first display port
(DP0). My second display on the 2nd display
This seems to be a duplicate bug - see 1864061
So the fix is to edit alsa-base.conf
options snd_hda_intel dmic_detect=0
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1901139
Title:
No Intel HD
Updated Linux image 5.8.0-26 also not working.
** Description changed:
Just upgraded from Kubuntu 20.04 to 20.10 to find no audio device
detected. lsmod shows module loaded, but alsa/pulse/etc is not picking
up the audio device. If I boot using the old kernel that was left
behind, it
Public bug reported:
Just upgraded from Kubuntu 20.04 to 20.10 to find no audio device
detected. lsmod shows module loaded, but alsa/pulse/etc is not picking
up the audio device. If I boot using the old kernel that was left
behind, it works (5.4.0-52 from 20.04). It does not work with shipped
Well, still brokenOr rather a key package is MIA. Trying to
configuring up my new HTPC and this was one of the major headaches I was
having with getting the video card operating properly. But thanks to
Patola, I pulled the missing package (vdpau-va-driver_0.7.4-7_amd64.deb)
from Debian - yes
Notified of update today, and noticed one of the updates was for Kernel
Image 5.3.0-46. So I removed the testdsp SMP kernel today and installed
5.3.0-46 proper kernel: Intel HDA driver not loading (so dummy output).
So I'm back to workaround from 12.
--
You received this bug notification
I've just recently run into this on my Acer Swift 5 - works on 5.3.0.40,
doesn't work on 5.3.0.42 or 5.3.0.45. The work around works, as does
not using the work around with patched kernel 5.3.0.46 provided here.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
This can be closed - totally my fault. I had several locked pacakages
(forgot about them) and was using a couple PPA's (Padoka's Stable MESA
PPA and Kubuntu backports). Was able to resolve it all with Aptitude
(just took a few hours) System is fully upgraded now that I fixed the
locked packages
Public bug reported:
I got the notice a few days ago the upgrade was available, held off to
today due to time availability.
I ran the upgrade from konsole: *** "do-release-upgrade -m desktop
-f DistUpgradeViewKDE"
I did note the following errors:
QInotifyFileSystemWatcherEngine::addPaths:
It was a Pavilion 15-ab188ca. And no I can't test, computer has been
permanently retired (stripped down and parted out) when the battery
charge circuit failed and could no longer properly detect a fully
charged battery (don't want or need my mom using a fire hazard).
--
You received this bug
I looked at the release notes and it appears amdgpu-pro only supports
discrete/dedicated graphics. I don't see any APU GPU based core listed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1577074
Oh, BTW, to be ry clear - I didn't provide (or do) any work on this
experimental (always consider it experimental) kernel - just the link to
it. I only found it through a Phoronix article and used it to test.
Thank M-bab for his hard work. :-)
--
You received this bug notification because you
I just checked on Phoronix, AMD's DC stack has not been accepted for
kernel 4.13 - so very unlikely to make it into Ubuntu 17.10. Maybe AMD
steps on it they get it into kernel 4.14 at the earliest. The basic
(overly simplistic) problem is how it's coded and would make it a total
nightmare for
Whoa, hold up - it *may not* be. The kernel main line developers have
rejected the code for various reasons. Untill it's acepted mainline,
it's not a part of the kernel. Read the readme on the github site. AMD
has to make changes to DC (formerly known as DAL) to be accepted. So
anyone using
Well, I'm a bit sorry I only filed the bug and haven't done anything
else except follow it (in hopes I'll be able to redo the system when
Windows no longer cuts the mustard on it and it returns to my
possession).
--
You received this bug notification because you are a member of Ubuntu
Bugs,
I was lucky and was able to pawn the computer off to another family
member with Windows installed (and I got myself an i3 based Dell that
works fine). That said, I had the computer back a month ago (to clean
out the heat sink and remove a virus - natch) and looked into it with an
external USB
Sorry, if you wish to try I breifly tested with this kernel:
https://github.com/M-Bab/linux-kernel-amdgpu-binaries
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1577074
Title:
[HP Pavilion 15]
I'm sure it will - the kernel in every release receives periodic
updates. But 4.6 is only a "candidate release" - a technical preview if
you will while bugs and such are fully baked out of the pie for final
release. You'll see one of the 4.5 kernels first - hopefully with a
fix, but it's also
I was using the closed fglrx (a.k.a. Crimson 15.12) on Kubuntu 15.10
(the latest updates from the regular repository - not the ones form the
various PPA's) and that worked fine for me. For 16.04 Wily, the kernel
packages from http://kernel.ubuntu.com/~kernel-
ppa/mainline/v4.6-rc6-wily have newer
Been investigating a wireless problem that lead me to install Kernel
4.6-RC6 from PPA - this Kernel seems to fix this bug (as haven't run
into this issue with the release candidate kernel).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Package changed: ubuntu => xserver-xorg-video-amdgpu (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1577074
Title:
AMDGPU driver problems on "Carrizo" APU
To manage notifications about
I believe the bug is in the current open DRI amdgpu display driver.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1577074
Title:
AMDGPU driver problems on "Carrizo" APU
To manage notifications
Public bug reported:
Summery: I'm having a hard time tracing this down. I updated to Kubuntu
16.04 (from Kubuntu 15.10 - that was using the Linux Crimson 15.12
driver) a couple days ago on my notebook (HP Pavilion, A10-8700P APU),
and ever since I've been having random black screens. I started
Sorry for pointing that out - I just want to see this fixed right the
first time
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1129409
Title:
Nvidia and AMD graphics drivers should indicate
Well, in respect to what I see in the nVidia drivers (nvidia-opencl-
icd-331-updates) and in the AMD drivers, shouldn't there be an enhances
line (Enhances libopencl1) - the AMD driver is afterall providing
enhancements, but in it's base package as opposed to a seperate opencl
pacakge...
--
You
Actually looking at my nVidia equipped system, the nVidia packages
installed on it, and my AMD system and the AMD packages installed on it
right now... Thinking about it, shouldn't the AMD driver depend on ocl-
icd-libopencl1 package? Should the AMD pacakge be broken up into
seperate packages
*** This bug is a duplicate of bug 1129409 ***
https://bugs.launchpad.net/bugs/1129409
Sadly, for the moment anyone who wishes to install both packages (which
will be everyone with an AMD card wishing to use the closed Catalyst
driver and Wine) will have to be a power user and use a work
*** This bug is a duplicate of bug 1129409 ***
https://bugs.launchpad.net/bugs/1129409
Hi Jack,
The bug isn't in the Wine package's (at least, not any more), the show
stopper for getting Wine working with Catalyst is being caused by a
fight between ocl-icd-libopencl1 packages and the
I posted on bug # 1376587... I fixed a couple bugs regarding the AMD
Catalyst drivers...
Okay, so the replaces line needs to change to this:
Enhances: libopencl1
Replaces: fglrx-driver-core
Provides: fglrx-driver-core, opencl-icd, amd-opencl-icd
Fresh install, I had to get rid of libopencl1 in
*** This bug is a duplicate of bug 1129409 ***
https://bugs.launchpad.net/bugs/1129409
Boo-YA! Got it. AND (!!! not fully related, but getting this working
also lead into fixing another problem), I got OpenCL working with out
haveing to resort to installing (or partialy installing the AMD
*** This bug is a duplicate of bug 1129409 ***
https://bugs.launchpad.net/bugs/1129409
Uhh, doesn't that solution induce another issue? I'm looking at it: if
I read the solution right and looking at what wine installed,
libOpenCL1.so.1 that is provided by the AMD Catalyst driver will be over
*** This bug is a duplicate of bug 1129409 ***
https://bugs.launchpad.net/bugs/1129409
Okay, more studying of what was going on - I'd like to modify the above
procedure. The provides line I belive should look like this:
Provides: fglrx-driver-core, opencl-icd, amd-opencl-icd
--
You
*** This bug is a duplicate of bug 1129409 ***
https://bugs.launchpad.net/bugs/1129409
Bla, after all that work on the updated drivers in the repository, and
working on the drivers from AMD's site (which are nice and zippy), Wine
*STILL* insists on removing the AMD drivers and installing
Okay, I added a whole pile of debugging statments into it, and kept
running it as root - it is picking up the parameter configure, but the
files aren't updating. So next I tried executing a direct command from
the postinst file, to explicitly update the i386 file (as root): update-
alternatives
Public bug reported:
I have two computers, both are now running run Kubuntu 13.04 x86-64
editions (the desktop also has Ubuntu Studio 13.04 x86-64), both use
closed source drivers (laptop has nVidia 9600M GS adapter, desktop has
AMD Radeon HD 6770). Before upgrading, both system's and three
sorry I didn't list a specific package, it's cause I'm not sure if it's
the nVidia/AMD packages, or related to another package. I did
deinstall/reinstall the video drivers numerous times over the weekend
(first thought was drivers didn't install properly, then started
thinking bug in the actual
Starting my tracing... But I think the bug is in a script of a package
that uses libc-bin, and it isn't a bug in libc-bin.
** Package changed: ubuntu = eglibc (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Sorry, this is not a libc-bin bug... But looking through the postinst
scripts for the package's for both the ATI and nVidia drivers, it
appears that for some reason when the script is executed, the script's
in the 64-bit packages are skipping neumerous update-alternative lines,
hence ldconfig
I know, this is taking me a while - I'm not a script kitty or a
programmer, so I'm not the swiftest at picking out on what's happening -
it's study-study, and rip appart and slowly nit pick my way through the
scripts while I'm jugling other tasks). ;-)
At any rate, with the AMD fglrx-updates
Given that dpkg is passing a parameter ($1) onto the scripts, I
beleive the target package is dpkg.
** Package changed: ubuntu = dpkg (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1182677
Better more effective work around - extract the postinst files from the
appropriate deb files and then execute them as root:
**@:~/temp$ ./postinst configure
That got it!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Err, no it didn't - not on my Laptop or Ubuntu Studio build (forgot to
remove the lines from the ld.so.conf files). Command line parameters
(in this case configure) are not being passed into the scripts. I
really hope this isn't affecting other packages or distro's. :-(
--
You received this
Well, Aptitude can't tell the difference between the architectures - so
it's possible the packages may not have need to be removed. I had the
same problem which aptitude wanted to blow away practically my entire
system - it wanted to remove X and KDE, and everything that relied on
them, not the
Public bug reported:
Binary package hint: plasma-widget-networkmanagement
I recently upgraded my router to a dual band one due to the heavy
proliferation of single band wireless networks in my apartment building.
I configured up the router and my Vostro accordingly, however, no matter
how I
Hmm, looking back at some of the earlier posts, maybe it's not. :-(
--
NetworkManager or wpa_supplicant timing out when connecting wireless
https://bugs.launchpad.net/bugs/572777
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
It seems to be fixed in Maveric - I hope that means this will hit the
backports for Lucid users.
--
NetworkManager or wpa_supplicant timing out when connecting wireless
https://bugs.launchpad.net/bugs/572777
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Well, I'm not a developer here so I can't bump the severity. When I
attempted to compile wpasupplicant and replace the packed one, I
couldn't connect to any network - after fighting for an hour, I just got
lazy and did the port from sid (and that did work for me at least a
few others)... I'm
Go to to Debain Packages Organization and manually download (watch your
arcitecture - i386 for 32-bit installs, AMD64 for 64-bit installs, etc,
etc - do not use ia64 for standard 64bit installes - that specifically
for the Intel Itanium CPU will cause very large problems/headaches)
wpasupplicant
Thanks Nils - I did what you said but that just really upset network
manager for me. But that gave me an idea, and I ended up pulling in
wpasuppicant form Debian Sid (along with libssl0.9.8 and libpcslite1) -
that fixed it up for me.
--
NetworkManager or wpa_supplicant timing out when
So far, no issues with me my Debain Sid ported wpasupplicant
libriaries - worked out of the box, no other work beyond installing the
debs was required.
I hope the guys with Intel WiFi chips suffering the same problem try
both fixes out and that one of these fixes will help them. If neither
of
It doesn't help me at all. Before anyoen asks, I haven't gotten around
to compileing wpasupplicant or network manager - I'm in the middle of a
reno that's dominating my time right now. Hope to get on it this
weekend.
--
NetworkManager or wpa_supplicant timing out when connecting wireless
Hi Rick - are you using the closed wl driver or the open B43 driver (for
further confirmation of other drivers the bug is effecting)?
--
NetworkManager or wpa_supplicant timing out when connecting wireless
https://bugs.launchpad.net/bugs/572777
You received this bug notification because you are
Okay. So far just tthe Intel 5300 and the closed Broadcom STA drivers
seem to be effected (at least as reported in this bug so far).
--
NetworkManager or wpa_supplicant timing out when connecting wireless
https://bugs.launchpad.net/bugs/572777
You received this bug notification because you are
Okay, I'm comfortable this is not a duplicate of 496093 - I'm using the
wl Broadcom Hybird STA driver. Last night I downloaded the driver
directly from Broadcom, compiled it and replaced the one in my kernel -
no change in establishing connection (I initally tried using the
packaged version
Hmmm... Well, I see a couple of things to go on right now. I haven't
tried unsecured or WEP based encrypted access points like Steve has -
I'll dig out my old back up router and configure it up as a non-
protected access point as well as a WEP encrypted one this weekend to
check those ends as
*** This bug is a duplicate of bug 575677 ***
https://bugs.launchpad.net/bugs/575677
This bug is not a duplicate of bug 572777 - I can see all the access
points around my computer, I'm just unable to connect to them.
--
NetworkManager or wpa_supplicant timing out when connecting wireless
*** This bug is a duplicate of bug 575677 ***
https://bugs.launchpad.net/bugs/575677
Err, sorry - this bug is not a duplicate of bug 575677 - I can see all
the access points around my computer, I'm just unable to connect to
them.
--
NetworkManager or wpa_supplicant timing out when
Before I mark a bug I reported on Friday a duplicate - is this bug
specific to a problem with the RaLink drivers or is this a bug in
wpa_supplicant? The more read, the more I think this bug report is
specific to a problem in the RaLink driver - which does not effect me as
I'm not using it.
Still researching and reading - if this is a duplicate bug, then it's
possibly a duplicate of 496093. The threads mostly around RaLink
drivers, but I've seen a few postings from people with Intel wireless
and Broadcom wireless based cards having the same issue. Looking at my
log, I see the same
I'm agreeing with a few more people and think it's more probable to be a
bug in wpa_supplicant. plasma_widget_manager doesn't work, nor does
wicd when I eliminate NetworkManager altogether.
--
NetworkManager or wpa_supplicant timing out when connecting wireless
Full log attached...
** Attachment added: Debugging output...
http://launchpadlibrarian.net/47838476/bug.txt
--
NetworkManager or wpa_supplicant timing out when connecting wireless
https://bugs.launchpad.net/bugs/572777
You received this bug notification because you are a member of Ubuntu
Read through this, and I'm really confused Is this bug a cause or
an effect for bug a bug I reported on Friday - bug # 572777 reported
here https://bugs.launchpad.net/ubuntu/+bug/572777
I had no problems with 9.04, and upgrading to 9.10, but my upgrade to
10.04 (Lucid) has left me with
Read through this, and I'm really confused on what this bug is
effecting I'm tryign to determine if this bug might be cause or an
effect for bug a bug I reported on Friday - bug # 572777 reported here
https://bugs.launchpad.net/ubuntu/+bug/572777
I had no problems with 9.04, and upgrading to
Possibly bug # 572777 is a duplicate of this bug. When i upgraded form
9.10 to 10.04 I was using knetworkmanager - on a wired connection I
removed it and tried plasma-widget-networkmanagement and had the same
result with the screen prompt. Don't have a syslog to attach because
I'm using ME-II,
Public bug reported:
I have a Vostro 1720 notebook running Kubuntu 10.04 with a Broadcom 4322
wireless adapter. It's using the Broadcom STA driver. I haven't had
any issues in the past with my setup with 9.04 (Jaunty) or 9.10
(Karmac), but but with the recent switch to the release of 10.04
Another Edid failure. This is on a new Dell Vostro 1720 with nVidia
9600M GS video card with 1920x1200 Premium display and a fresh install
of Kubuntu 9.04 Jaunty (also applies to Ubuntu). I can only access
1920x1200x24 bit video. Fine for daily use, but no good for gaming when
a lower
Sorry, nearly forgot the log file...
** Attachment added: Xorg.0.log
http://launchpadlibrarian.net/28861281/Xorg.0.log
--
MASTER: EDID fail
https://bugs.launchpad.net/bugs/194760
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
i8042.reset i8042.nomux is all that I needed.
--
Dell Laptop vostro 1310, Internal Keyboard and Touchpad not working anymore on
9.04 jaunty
https://bugs.launchpad.net/bugs/334249
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
Can confirm this. I'm just setting up my new notebook and it took me a
good while to narrow this problem to the current hal update packages (I
thought it was another problem originally).
--
New version (0.5.12~rc1+git20090403-0ubuntu3) breaks wireless (Broadcom wl
driver)
Yet another confirmation on my three day old Dell Vostro 1720 - no
keyboard or mouse on cold boots. I'm using a clean install of Kubuntu
9.04 and Kernel 2.6.28-13-Generic (64-bit). Occurrence for me is 100%
on cold boot only, regardless of being on battery power or on AC power.
The only work
I won't be able to try untill this weekend. I'll swap my 250G HD in my
laptop over to teh original 120g one and give it a shot and let you
know.
--
SMB error: Unable to mount location when server configured with security=share
https://bugs.launchpad.net/bugs/209520
You received this bug
Yes, it most certainly does effect Debian as well.
My desktop has this problem (Ubuntu Intrepid) and I cannot connect to my
D-Link DNS-323 NAS unless I mount it manually from the command prompt.
I did try all of the suggestions here. I can see the server, I can see
the share, I get prompted for
Sorry about being so slow - I've have a very hectic schedule. I deleted
my folders.db file and that fixed the problem.
--
cannot empty virtual imap trash
https://bugs.launchpad.net/bugs/64762
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
I'm not runing Kubuntu on my Acer Aspire 5002WLMi anymore - I'm running
Debian AMD64 Etch/Lenny/Sid (Etch with serveral things ported from
testing unstable). At anyrate, try compiling a Kernel from kernel.org
- all my wireless problems completly disappeared when I started running
the Kernel
Public bug reported:
Binary package hint: evolution
I can't delete old emails in waste basket - doesn't matter if I expunge
the folder or right click on the trash and hit the empty trash. Nothing
happens except the screen refreshes and all the old unwanted email is
still present.
ProblemType:
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/19522028/Dependencies.txt
** Attachment added: ProcMaps.txt
http://launchpadlibrarian.net/19522029/ProcMaps.txt
** Attachment added: ProcStatus.txt
http://launchpadlibrarian.net/19522030/ProcStatus.txt
--
Evolution
Same problem being experienced here - the driver loads, but in aMSN
Ekiga Softphone I can't make any adjustments to the video leaving a
nearly black image. It work's, but it is so dark and with no adjustment
control I would exactly call it usable.
--
Quickcam video too dark
Sorry, I'm unable to test the new kernel for this bug - I changed my
Laptop over to Debian Etch a few months ago (my other computer is still
running Ubuntu). :-(
--
B43 driver causing numerous APIC errors
https://bugs.launchpad.net/bugs/222174
You received this bug notification because you are a
Change that - when the computer goes into sleep mode (when I'm using it
on battery - I have all that disabled when runnign on hydro), the
wireless won't wake up. I tried having the computer unload B43 and ssb
modules before suspending, and then reload them on wake up - and it
won't connect to any
Sorry for taking so long to write back - I disabled APIC mode using the
noapic kernel boot parameter. And have been testing it for a few days
to fully confirmed that all the hardware is working properly - a touch
slower to boot, and can see a few things that were on separate
interrupts are now
I just checked my old logs, and I don't have 'em. But I can give you
two fresh logs in a few minutes - I'll unblock the ssb and b43 drivers
while I block ndiswrapper and boot the kernel 2.6.17 that I'm having the
problems with, then I'll block them again and unblock ndiswrapper and do
another
Log with APIC error's. I think this happens with wireless network
activity.
** Attachment added: ssb b43 causing APIC errors
http://launchpadlibrarian.net/14413993/dmesg-apicerr.txt
--
B43 driver causing numerous APIC errors
https://bugs.launchpad.net/bugs/222174
You received this bug
Same kernel, ssb b43 blacklisted while ndiswrapper is unblacklisted.
** Attachment added: ndiswrapper - no APIC errors
http://launchpadlibrarian.net/14414022/dmesg-noerr.txt
--
B43 driver causing numerous APIC errors
https://bugs.launchpad.net/bugs/222174
You received this bug notification
Bug also exists in 2.6.24-17 Generic. I also must apologize that I
labeled the Kernel version's wrong: 2.6.24-16 Generic is the Kernel I
was having problems with originally. The kernel that works fine for me
is Gusty's Kernel 2.6.22-14 Generic (my extreme bad)
With Kernel 2.6.24-17 2.6.2-16 I
Public bug reported:
I have an Acer Aspire 5002WLMI and am not able to use the B43 driver in
Kernel 2.6.16-24 Generic. When I do, I get tons of APIC error messages
in dmesg while the system runs slowly and eventually crashes hard at
random. If I use Gusty Kernel 2.6.14-22 Generic with
*** This bug is a duplicate of bug 153889 ***
https://bugs.launchpad.net/bugs/153889
Okay, the button showed up fine when I want to do the upgrade the first
time - but it's still showing up, and that is my problem. I did try
hitting it the second time, and eventualy it figured out that it
Public bug reported:
Binary package hint: update-manager
When 7.10 went live, I had my system upgraded right away. 1/2 hour ago
(when I first powered up the computer after getting home from work),
Aptitude reports there's a distribution upgrade, which fails as system
is up to date (as I already
I have, it made no difference on any other hardware. I'm presently
working away at UDEV HAL to figure out why HAL is not picking up the
physical unplugging of my MP3 player (this is why it has been failing to
reconnect my MP3 player on subsequent re-connects, HAL think the player
was never
Same issue here - Acer Aspire 5002WLMi notebook with (really crappy) SiS
video adapter. If I let the laptop idle for 30 minutes then Xorg starts
eating CPU cycles and maxes out the CPU. If left maxed more then 15
minutes, the only recovery is to kill the X.org process from another
terminal
Did some more investigating, it appears that I'm experiencing bug
109507, not this bug - my bad. I unloaded superkaramba and the problem
has completely disappeared.
--
Xorg process freezes, uses 100% of CPU. Can be killed by remote terminal.
https://bugs.launchpad.net/bugs/51991
You received
Strange, but I can add further verification of this bug... With
superkaramba loaded, Xorg would ramp up to 100% usage over 30 minutes
when my laptop was left to idle. 15 minutes after it reach top speed it
the system would crash if I did anything except kill Xorg. I hadn't
experienced this
Okay, I borrowed a powered hub to see if it's a hardware related issue.
I'm now starting to believe this could very well be a hardware bug. I
still get very brief stalled messages as before when the transfers of
each file I'm copying (moving, deleting, etc) initially occur for each
file, however
Okay, problem does not exist on my Desktop (Ubuntu Feisty 7.04 instead
of Kubuntu).
I've been checking, and Hal is not picking up USB device disconnects
properly on the Laptop. When I disconnect my Sansa, the Hal Device
manager shows it as still being plugged in.
--
Oops in scsi_mod and
No error's reported at all in dmesg - it shows the the device hooking up
and disconnecting. I get the STALLED message in the lower left corner
of Konquoror, in GPHOTO, and I also get it in dialog boxes of both when
attempting to copy files from the camera.
--
Kodak USB connection stalls
Okay, I've updated and graded over to Kubuntu 7.04 (Feisty), and the
transfers are still slow with lots of stall messages.
--
Kodak USB connection stalls
https://bugs.launchpad.net/bugs/105232
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact
1 - 100 of 116 matches
Mail list logo
