Public bug reported:
Ubuntu 14.04 installed on x86_64 PC hardware.
Starting amarok from the CLI and I get:
QDBusConnection: session D-Bus connection created before QCoreApplication.
Application may misbehave.
QDBusConnection: session D-Bus connection created before QCoreApplication.
Public bug reported:
11.04 desktop installer crashes when installing on a Dell Optiplex 760
if there is no Internet connection.
If the Internet is available then the installer works fine.
Install is done with PXE-boot over our network without the Internet. I
can give Internet access to the
** Attachment added: syslog
https://bugs.launchpad.net/bugs/816497/+attachment/2234338/+files/syslog
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/816497
Title:
installer crashes when not
** Attachment added: partman
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/816497/+attachment/2234355/+files/partman
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/816497
Title:
FWIW I'm also getting this crash with *all* of my photos taken from my
camera. Attached is one image that causes a problem.
Shotwell seems to open the images fine though.
This crash has made f-spot completely and totally unusable for me.
** Attachment added: CRW_2607.CRW
Oh, one more thing. My problem is that F-spot crashes on *import* as
opposed to importing fine and crashing later (as outlined in the gnone-
bugs #633020 here: https://bugzilla.gnome.org/show_bug.cgi?id=633020 )
Basically, I open f-spot, click import, select the directory on the hard
drive the
I get the feeling we're expected to buy new hardware.
On Mon, 2010-10-18 at 10:56 +, Novastorm wrote:
Is some sort of fix for this ever going to make it into Lucid? Or are we
expected to just pick and choose our own solutions?
--
[i855gm] Freeze shortly after X startup on Intel i855
After a couple other folks said they had luck by getting rid of network-
manager, I figured I'd give wicd another shot. I removed network
manager, rebooted, manually configured a wired network, then installed
wicd. I've been going on a few days now with no disconnects, so perhaps
something is
With kernel: Linux venus 2.6.34-020634rc6-generic #020634rc6 SMP Fri Apr
30 10:09:34 UTC 2010 i686 GNU/Linux, the system doesn't lockup, but I
get messages the kernel is tainted and I can't do anything with the
wireless network until I reboot.
--
ar9170 taints kernel
** Changed in: pulseaudio (Ubuntu)
Status: Invalid = New
--
internal mic does not work on Fujitsu P7120
https://bugs.launchpad.net/bugs/569399
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Public bug reported:
Binary package hint: pulseaudio
On my P7120, running 10.04 final RC, my internal microphones (stereo
mic) do not give any signal in sound properties, nor do they record in
any application. They work fine in Windows, so the problem is
software/driver related.
This seems to
** Attachment added: AlsaDevices.txt
http://launchpadlibrarian.net/45172007/AlsaDevices.txt
** Attachment added: AplayDevices.txt
http://launchpadlibrarian.net/45172008/AplayDevices.txt
** Attachment added: ArecordDevices.txt
http://launchpadlibrarian.net/45172009/ArecordDevices.txt
Ok, despite the lack of clarity in your response, I found some
information elsewhere on the internet to decipher what you mean.
I have done the following:
amixer set 'Mic/Line Jack Mode',0 'Mic 80pc bias'
amixer set 'Capture',0 100%/100% unmute
amixer set 'Capture',1 100%/100% unmute
to no
Public bug reported:
Using a new DLink DWA-160 A2 wireless card on lucid, the connection
keeps dropping and reconnecting, which has already been reported, but
after a couple days, my kernel becomes tainted and I can't even shutdown
the system. I have to physically power cycle the system.
** Attachment added: AlsaDevices.txt
http://launchpadlibrarian.net/44960600/AlsaDevices.txt
** Attachment added: AplayDevices.txt
http://launchpadlibrarian.net/44960601/AplayDevices.txt
** Attachment added: ArecordDevices.txt
http://launchpadlibrarian.net/44960602/ArecordDevices.txt
I also have this same issue on 10.04 beta, 2.6.32-21-generic. In fact,
I have found wireless to be horrible in lucid. Not only does the
connection drop and reconnect very frequently, sometimes it won't
connect at all with dhcp. In that case, the essid gets mangled. I can
get around that issue
Public bug reported:
Binary package hint: openoffice.org
During an upgrade, the following error occurred:
E: /var/cache/apt/archives/openoffice.org-
emailmerge_1%3a3.1.1-5ubuntu1.1_all.deb: subprocess new pre-installation
script returned error exit status 1
ProblemType: Package
Architecture:
*** This bug is a duplicate of bug 526876 ***
https://bugs.launchpad.net/bugs/526876
** Attachment added: AptOrdering.txt
http://launchpadlibrarian.net/39732570/AptOrdering.txt
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/39732571/Dependencies.txt
** Attachment
Public bug reported:
Binary package hint: qtcreator
Fresh install of qtcreator (at the same time as qt-designer). go to open
an example project (any) and try to build and the little build progress
bar at the left gets approx 10% and nothing happens. Any created project
does not build either.
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/39146255/Dependencies.txt
** Attachment added: XsessionErrors.txt
http://launchpadlibrarian.net/39146256/XsessionErrors.txt
--
QT Creator does not build any projects on default install
Further investigation:
qtcreator does not depend on libqt4-dev (!)
Tried installing libqt4-dev however it depends on libpq-dev
libpq-dev can't be installed due to it depending on a different version of
libpq5 (8.4.2-0ubuntu9.10) than is what was installed (8.4.2-1~jaunty1)
Fix: Forced downgrade
Cannot change 'affects' package. Any help? How do i get this bug in the
hands of the repo maintainers?
--
QT Creator does not build any projects on default install
https://bugs.launchpad.net/bugs/521409
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Thanks Eric, I followed the instructions to get pulseaudio just working
on my PCM channel and it seems to have done the trick. I think the main
problem is still in the ALSA driver due to the non-working ALSA master
slider, however after stuffing around with ALSA conf files too long,
it's good to
Public bug reported:
I have a Fujitsu P5020 laptop running Karmic. When I adjust my
pulseaudio volume, the output from either speakers or headphones if
they're plugged in is constant, and not affected by the pulseaudio
slider until it reaches around 80%.
Further investigation reveals that the
On Thu, 2009-09-17 at 07:25 +, nomnex wrote:
Panasonic Driver
Hi, thank you very much for your answer. It brings much clarity. I was
slow to answer because I did some research in the meantime.
Nevertheless, it is bit technical for my understanding. May I ask your
advice to help me go
And since you have tested your Panasonic under Karmic, could you install
the old driver too? What is your advice? Karmic is available soon. I was
planning to install it on the notebook.
Don't touch Karmic until it's released. It's the same story there,
you'll need to install the 2.4 drivers.
, 2009-09-17 at 04:02 +, nomnex wrote:
@Mike Rose and everybody on the thread.
Hi, glad I found this thread. I am fairly new to Ubuntu and certainly
less experienced than any of you. I use Jaunty on a Panasonic Let's note
model CF-W2 I bought in Japan a few years ago (Intel chipset must
Public bug reported:
Ever since gnome-volume-applet was deemed deprecated, it's replacement
gnome-volume-control has been acting strange. Odd crashes here and there
weren't too bad and to be expected in alpha testing, however, recently,
it has just started segfaulting on startup.
Not only is it ugly and in english only, but other google features are
missing (eg. searching for 1 pound in kg doesn't return what you'd
expect). Huge regressions for what? What was wrong with the old google
search?
If the idea was to make more money out of searches, you've lost me
ubuntu. I've
Incorrect. Not fixed as of 2:2.8.0-0ubuntu1
In addition, I can't even seem to install the older 2.4 version over the top
anymore, so now I'm stuck with this buggy driver. Very frustrating when I'm
trying to work.
Bryce, is it at all possible to put the old intel driver in the official ubuntu
Well I got it to happen again, everything updated/upgraded as of about
15 minutes ago. Switched back over to xserver-xorg-video-intel (from
xserver-xorg-video-intel-2.4) rebooted, followed the instructions at
with verbose debugging
output or something. I don't mind it running a little slow while I'm
testing, I just want this bug sorted. :)
Mike
Bryce Harrington wrote:
suckertoo, no problem, hopefully Mike Rose can test. I am fairly
certain this bug is gone in Karmic, so if no one is able to test
:
suckertoo, no problem, hopefully Mike Rose can test. I am fairly
certain this bug is gone in Karmic, so if no one is able to test, I'm
confident we can close it, but I'll give a month for people to try.
Good luck in Afghanistan
** Changed in: xserver-xorg-video-intel (Ubuntu)
Status
I can confirm this happens for me too. Using Jaunty on i386. lsusb as follows:
Bus 001 Device 004: ID 13d3:3206 IMC Networks DNTV Live! Tiny USB2 BDA (No
Remote)
Error message refers to non-existent link. I haven't yet tuned any
channels in.
--
Attempting to watch TV in totem with a USB
after looking through some older totem code upstream, it appears the link
should be:
http://projects.gnome.org/totem/#dvb
It seems that upstream is working on a scanning GUI however I couldn't
find any details about the timeframe. Hopefully they'll have something
out by Karmic! :)
In the
For what it's worth, I'm now running on the old 2.4 driver and I'm still
getting those MTRR errors, but no freezing. Happens on both XAA and EXA
with the old driver, seemingly when X initialises. I can force these
errors by 'zapping' X at the login screen.
Sidenote - Interesting excerpt from
Public bug reported:
Running Jaunty on a Panasonic CF-R3 notebook with intel 855GM graphics
chipset and pentium M processor. X (running compiz) will completely
freeze seemingly randomly (fairly often though - easily 5 times a day),
necessitating a hardware restart (or REISUB) although the mouse
Murphy's law. I just got two more freezes, with the above 'fix'
Back to the drawing board :)
--
Jaunty - X freezing on intel 855GM - MTRR issue
https://bugs.launchpad.net/bugs/370292
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
Public bug reported:
Using a Panasonic R3 laptop (Pentium M, intel chipset)
Just distupgraded from 8.10 to 9.04 via Update Manager
Upon reboot I got an error message 'CPU Frequency scaling not supported' or
similar, as I had the gnome cpufreq applet in my panel
$ cat /proc/cpuinfo
processor
39 matches
Mail list logo
