I can confirm that the same error occurs when installing World of
Warcraft under wine in Ubuntu 7.10 AMD64:
"err:ole:OLEPictureImpl_LoadJpeg Trying to load JPEG picture, but JPEG
supported not compiled in."
My hardware -
Motherboard: Gigabyte GA-K8N Pro-SLI (Nvidia nForce4 based)
CPU: Athlon 64
The only way I've ever been able to control SPDIF output with any Linux
distribution using alsa is by installing aumix or a variant and
controlling SPDIF with the "Digital1" control.
For Ubuntu Feisty you can install aumix (a terminal based mixer) or
aumix-gtk (gtk GUI). I use the gtk version.
So
I ran the tests as you requested with all the latest updates and
"60-cdrom_id.rules" is the culprit. Whenever its enabled blkid is silent
and I can't mount. Note that even with the cdrom_id rules commented out
the drive becomes locked after mounting media and then closing the tray
with no media in
OK, test done. I first verified I still couldn't blkid or mount with the
cdrom_id rules enabled (since a lot of updates have been occurring) and
I couldn't, so I disabled the rules and rebooted and was able to
blkid/mount. Then I ran the trace you requested, but was still able to
blkid/mount after
** Attachment added: "kernel log with cdrom_id rules disabled"
http://launchpadlibrarian.net/33049783/kern.log
--
CD-ROMs not detected unless when booting with one inserted already
https://bugs.launchpad.net/bugs/439137
You received this bug notification because you are a member of Ubuntu
Bug
I just got home an updated and rebooted and my ODD drive works perfectly
now!. I don't know what you devs did, but it sure worked for me. Thank
you very much.
You can close this bug unless someone else is still having problems.
--
CD-ROMs not detected unless when booting with one inserted alread
I have the same problem, and the workaround Daniel Ellis described
(booting with a DVD or CD in the drive) works for me also. If I don't
boot with media in the drive my DVD/CD drive is basically dead in the
water. Even though I can manually mount it, I can't burn anything to it
because Brasero does
I don't understand. No one has reported that the attempted fixes have
worked, and they don't. I just checked again.
But I tried to file a new bug report anyway as requested, but after
trying for almost an hour launchpad simply won't let me. In fact when I
attempted to associate my login with Open
Public bug reported:
Binary package hint: udev
This is simply a users attempt to reopen bug #431055 which was
arbitrarily closed without resolution. The symptoms haven't changed, and
the attempted fixes had no effect upon the problem, as was reported by
all the users in the original bug report. H
OK, after half a day of effort I was finally able to get past all the
GPG nonsense for a normal user to file a bug report. I have opened bug
#439137 in an attempt to assure that Ubuntu doesn't release a beta that
can't mount or use DVD/CD media.
Sheesh.
It would have been much easier if the devs
puter for the rest of the day. By the way, the drive I
have has a SATA interface, and I'm running Ubuntu x86_65 Karmic Alpha 6
with all updates as of this moment.
** Attachment added: "Requested udev log from muncrief"
http://launchpadlibrarian.net/32758014/udev.log
--
CD-ROMs
** Attachment added: "Requested dk log from muncrief"
http://launchpadlibrarian.net/32758038/dk.log
--
CD-ROMs not detected unless when booting with one inserted already
https://bugs.launchpad.net/bugs/439137
You received this bug notification because you are a member of Ubuntu
B
** Attachment added: "Requested udev dump log from muncrief"
http://launchpadlibrarian.net/32758097/udev-dump.txt
--
CD-ROMs not detected unless when booting with one inserted already
https://bugs.launchpad.net/bugs/439137
You received this bug notification because you are a member
** Attachment added: "Requested dk dump log from muncrief"
http://launchpadlibrarian.net/32758102/dk-dump.txt
--
CD-ROMs not detected unless when booting with one inserted already
https://bugs.launchpad.net/bugs/439137
You received this bug notification because you are a member
I just noticed after rebooting with media in the drive that although
automount does consistently work, the physical eject button on the drive
actually doesn't work. However, I can consistently unmount and eject via
nautilus.
--
CD-ROMs not detected unless when booting with one inserted already
ht
Well, I don't know what has changed since yesterday but there is an even
worse problem after booting with media in the drive. As I said, I can
consistently automount media, and unmount/eject it via nautilus, but
only until I close the drive with no media in it.
Once I close the drive with no media
** Attachment added: "kern.log"
http://launchpadlibrarian.net/32762648/kern.log
--
CD-ROMs not detected unless when booting with one inserted already
https://bugs.launchpad.net/bugs/439137
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubunt
OK, I've attached the data you requested. Sorry for forgetting the
kernel log before. I did have the cdrom in /etc/fstab and I removed it.
I thought it fixed the problem at first because after I rebooted and
inserted the DVD it automounted, but it only did it once. I tried
rebooting numerous times
** Attachment added: "eject.trace"
http://launchpadlibrarian.net/32762642/eject.trace
--
CD-ROMs not detected unless when booting with one inserted already
https://bugs.launchpad.net/bugs/439137
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
First of all, just to let you know my level of expertise, I was an R&D
engineer for over two decades, but generally considered an embedded
systems designer because I'm a multi-disciplined
hardware/firmware/software engineer, developing everything from custom
microprocessors and assemblers, to enter
Excellent idea, but I have to get some sleep now (it's 2:30AM here), but
I'll do it first thing after I get up and report back ASAP.
--
CD-ROMs not detected unless when booting with one inserted already
https://bugs.launchpad.net/bugs/439137
You received this bug notification because you are a me
Public bug reported:
My computer was just sitting idle with no applications running when a
crash was detected at I was asked to submit this bug report.
ProblemType: KernelOops
Annotation: Your system might become unstable now and might need to be
restarted.
Architecture: amd64
AudioDevicesInUse:
** Attachment added: "AlsaDevices.txt"
http://launchpadlibrarian.net/33757935/AlsaDevices.txt
** Attachment added: "AplayDevices.txt"
http://launchpadlibrarian.net/33757936/AplayDevices.txt
** Attachment added: "ArecordDevices.txt"
http://launchpadlibrarian.net/33757937/ArecordDevices.t
Public bug reported:
This may be a duplicate of other ECC related bugs but I'm not
knowledgeable enough to tell for sure so I just have to report it as
new. I have Windows 7 RC on /dev/sda1, root on /dev/sda5 and home on
/dev/sda6. I just installed the Karmic alpha two days ago to evaluate it
and
** Attachment added: "all-logs.log"
http://launchpadlibrarian.net/31928789/all-logs.log
** Attachment added: "AlsaDevices.txt"
http://launchpadlibrarian.net/31928791/AlsaDevices.txt
** Attachment added: "AplayDevices.txt"
http://launchpadlibrarian.net/31928792/AplayDevices.txt
** Attac
I just tried Karmic again and after manually running fsck on all ext4
volumes I can know reliably boot into gdm. I initially dropped into a
console shell but as I said running fsck on all ext4 volumes enabled gdm
boot.
It's not pretty, and there are a lot of errors reported, but I installed
all my
OK, I installed the Jaunty kernel as requested with no problem.
Unfortunately, and surprisingly, it worked the same as the Karmic
kernel. None of my media will automount, and once I open and then close
the tray without media it locks up. I even saw the same USB errors
during boot, which also surpri
Wow, a lot of people must be trying to download the beta. I tried direct
and torrent downloads and they both would take a day or more. So I'm
going to keep Jaunty installed for now because I don't think installing
alpha 6 again would change anything. So if you want me to run any tests
on Jaunty or
OK, I did a clean beta install and still have the same problems. Just
let me know what to try next.
--
CD-ROMs not detected unless when booting with one inserted already
https://bugs.launchpad.net/bugs/439137
You received this bug notification because you are a member of Ubuntu
Bugs, which is sub
Oh wait, I see what you mean. It did fail with the Jaunty kernel under
Karmic. Sorry, it's getting late and I'm not thinking straight :)
In any case after reviewing the apport bug data if you still want me to
try the rules changes I'll do it tomorrow. Good night for now.
--
CD-ROMs not detected
No, I think you misunderstood, the drive works perfectly with Jaunty. It
only has problems under Karmic. In fact a gnome-vfs crash just occurred
and apport generated an automatic bug report with all kinds of trace
data. It's bug #440427. Hopefully you can look at the data and see what
happened.
Wo
I was unable to get the icedtea java plugin to work on Ubuntu Jaunty
x86_64 after trying all the suggestions on this thread, and others I
found elsewhere.
However, I just discovered that Sun now provides a 64 bit plugin and
it's in the Ubuntu repositories. I simply uninstalled icedtea java and
ins
I tested libepoxy0_1.3.1-1ubuntu0.16.04.2 amd64 and i386 as requested
and it works without error. My system is Xubuntu 16.04.2 with kernel
4.9.35-lowlatency. Thank you for your excellent work!
** Tags removed: verification-needed-xenial
** Tags added: verification-done-xenial
--
You received thi
This bug is marked as "Fix Released" but after years of running Manjaro
I decided to give Ubuntu a try again with Disco Dingo 19.04 and it was
simply impossible because it still exists. I could get past the initial
error, and Ubuntu thought it was installed, but trying to boot just
output the error
Public bug reported:
When updating my Xubuntu 16.04.2 system today the upgrade from libepoxy0
1.3.1-1 to libepoxy0 1.3.1-1ubuntu0.16.04.1 caused my system to hang
right before the login screen.
Unfortunately since this was a complete system lock up I can't provide
any logs as I had to restore the
Yes Micheal, that's all anyone confronted with this bug needs to do
initially so they can boot.
After booting they should also open a terminal and issue one of the
following commands:
For amd64 systems:
sudo apt-mark hold libepoxy-dev libepoxy0 libepoxy0:i386
For i386 systems:
sudo apt-mark hold
I removed the libepoxy0 package holds, added the LocutusOfBorg
repository, and did an apt-get update and apt-get dist-upgrade. However
my system still hung on reboot. If I did something wrong please let me
know.
Also the problem only occurs with AMDGPU-PRO, I should have been clear
about that. Unf
@LocutusOfBorg, I tried adding your repository again today and received
this error with sudo apt-get update:
Err:33
https://launchpad.net/~costamagnagianfranco/+archive/ubuntu/locutusofborg-ppa/+packages
xenial/main amd64 Packages
404 Not Found
I don't know if this occurred before, but in an
The Mesa drivers only support OpenGL 4.5 Core mode, they don't support
OpenGL 4.5 Compatibility mode. It's odd but for some reason they only
support OpenGL 3.3 Compatibility mode, and the developers have stated
they don't intend on changing it. So games and other software that
require higher Compat
@LocutusOfBorg, this seems to work perfectly. I tried a few iterations
of playing No Man's Sky, browsing with Chrome, and playing video with
VLC and everything worked as expected. Thank you for the quick fix.
If anyone else needs this update before it's in the main repositories
execute the followi
I tried the 1.4.3-0ubuntu2 version as well and it also reintroduced the
black screen hang on boot for me. I reverted back to
1.3.1-1ubuntu1.16.04.2.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/169823
Public bug reported:
I keep my database in a different directory for contents that are backed
up. To accomplish that I modify /etc/mysql/mysql.conf.d/mysqld.cnf,
/etc/apparmor.d/usr.sbin.mysqld, and /usr/share/mysql/mysql-systemd-
start.
When the software update ran it crashed instead of asking m
This bug still exists in Xubuntu 16.04.1 amd64 as of today. Thunar is
version 1.6.10-2ubuntu1, and the system has all current updates applied.
I installed Xubuntu about a week ago and Thunar crashes almost every
time I try to rename a file with it. I've started using mv from the
terminal to avoid f
I can confirm the same problem exists with Xubuntu x64 16.04 as well.
However I can also confirm that this has been a problem with all Ubuntu
flavors for many years.
The difference now is that nothing can be done on the user side to fix
it. After all these years I'd become quite adept at editing d
I can confirm this problem still exists with Xubuntu 16.04 x64. I hope
it's fixed someday. It's difficult to win Windows users over when common
things like this don't work, it's very confusing for them and they just
want me to reinstall Windows :(
--
You received this bug notification because you
Public bug reported:
Trying to install Ubuntu 14.10 on Biostar TA970 motherboard with HD6450
graphics card and 12GB DDR3 ram.
ProblemType: Bug
DistroRelease: Ubuntu 14.10
Package: ubiquity 2.20.0
ProcVersionSignature: Ubuntu 3.16.0-23.31-generic 3.16.4
Uname: Linux 3.16.0-23-generic x86_64
Apport
On 05/14/2015 06:11 AM, Phillip Susi wrote:
> Please choose the check disc option from the boot menu to verify the
> integrity of the installation image, as well as the memtest option and
> let it run for at least 15 minutes to see if your ram has errors.
>
>
> ** Changed in: ubiquity (Ubuntu)
>
This bug occurs on Ubuntu 14.04 as well, which is what I'm running. But
for some reason the bug utility will only let me report it on this
thread.
I already knew that the Catalyst 15.2 beta drivers didn't work, that's
why I never moved to Ubuntu 15.04. The last working drivers are Catalyst
14.12.
Same problem on Ubuntu 14.04.2. Can't install fglrx for HD3300.
version.h is missing. The worst part is that the default drivers are
very slow and trying to run a virtual machine with them is almost
impossible. I hope this can be fixed, it seems it's been a problem for a
long time.
--
You receive
AMD Catalyst 14.12 drivers will not compile on Ubuntu 15.04. I am using
an HD 6450 and can compile the drivers fine on 14.04 LTS. The fglrx beta
drivers included with 15.04 are very buggy and unusable with cairo-dock
so it is critical to able to compile the 14.12 drivers.
--
You received this bug
*** This bug is a duplicate of bug 1431068 ***
https://bugs.launchpad.net/bugs/1431068
Public bug reported:
Catalyst 14.12 will not compile for an HD 6450 card on Ubuntu Mate
15.04.
ProblemType: Package
DistroRelease: Ubuntu 15.04
Package: fglrx-core 2:14.501-0ubuntu1
ProcVersionSignature: U
I have the same problem as pramathesh. In addition if you enable logout
and shutdown in the main menu neither work. I have tried the various
"delay start up" solutions found on the Internet but none work.
There is also a problem if you attempt to use the GLX mode. The entire
dock will intermittent
52 matches
Mail list logo
