Public bug reported:
The tl;dr: version:
An RPCNFSARGS variable needs to be added to /etc/default/nfs-kernel-
server file in order to facilitate turning off NFSv3, so that the
rpcbind dependency goes away. Otherwise the user is forced to snoop
through all the related systemd service files (as I
** Description changed:
This bug applies to both Ubuntu 18.04 and Ubuntu 20.04, the two distros
I've checked.
This is likely a packaging error. The syslog user appears in
/etc/passwd as:
- syslog:x:102:106::/home/syslog:/usr/sbin/nologin
+
Public bug reported:
This bug applies to both Ubuntu 18.04 and Ubuntu 20.04, the two distros
I've checked.
This is likely a packaging error. The cups-pk-helper user appears in
/etc/passwd as:
cups-pk-helper:x:111:118:user for cups-pk-helper service,,,:/home/cups-
pk-helper:/usr/sbin/nologin
Public bug reported:
This bug applies to both Ubuntu 18.04 and Ubuntu 20.04, the two distros
I've checked.
This is likely a packaging error. The syslog user appears in
/etc/passwd as:
syslog:x:102:106::/home/syslog:/usr/sbin/nologin
Of course there is no directory /home/syslog. This
I'm having exactly the same problem with a Gigabyte Z97 MB which has the
Realtek ALC1150 audio chip. Howver, in my case, I'm trying to run a
current version of Arch linux, meaning that the linux kernel, sound
drivers, and pulseaudio are maximally up to date as of August 17, 2015.
So in
So, I ended up in a menu which allowed me to test the bootable USB stick
I was trying to use to install 13.04 AMD server, and it reported errors.
I downloaded another copy of the 13.04 ISO and made another bootable
USB. This one allowed the system to be installed with no problems
whatsoever, so
I'm having exactly the same problem with 13.04 64-bit server. Can
someone elaborate on what's involved in using the linux-server package
in the preseed? Thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apt-get installs software from online repositories (i.e. remote
servers), not downloaded files.
Here are instructions for installing Libre Office on Ubuntu Maverick:
http://www.liberiangeek.net/2011/01/install-libreoffice-ubuntu-10-10
-maverick-meerkat-ppa/
Upgrade to Libre Office and you should be fine.
On 08/06/2012 09:42 AM, Ioan Merches wrote:
Sound doesn't play at all at ubuntu 10.10 in .pps files. What can I do?
Thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I forgot to add that the problem is reproducable on several different
Ubuntu Precise (12.04) amd64 machines -- every one that I tried.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1018016
Title:
Public bug reported:
I've only experienced this problem trying to use rhino. Basically,
hitting Backspace or Left Arrow jumps the cursor several characters to
the left and the screen becomes unreadable. This was not a problem in
Jaunty, the only other distro I've tested for this bug. It's
After speaking with the package maintainer about this and doing a little
more experimentation, it became clear that this is really caused by a
bug in the pine mbox format. mb2md expects message content lines in
mbox files which begin with the word From to have been converted to
From:
From
Public bug reported:
Binary package hint: mb2md
mb2md, which is still widely used, fragments messages in which the
message body contains a line beginning with the word From, presumably
because this is used as the new message delimiter in mbox files. The
easy fix for this is that email headers
In my case, when scanning 8.5'x11 documents the top 4cm are always cut
off no matter how I adjust the Settings/Preferences.
DistroRelease: Ubuntu 10.10
Scanner: HP54xx Flatbed Scanner
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
We've been informed that this bug is now fixed; however with no
information about how or what the actual problem was. I followed the
links to the referenced debian bug reports and couldn't find anything
posted there. Mind sharing how Bug Watch knows that the bug is fixed
and what the fix was?
@focamonje:
I try with the PowerPoint Viewer + Wine (pptview) and the sound works but
sometimes this application freezes the s.o.
Any solution?
Yes. What I did was install Virtualbox using Windows XP as a VM. Then
it's a simple matter to install either Powerpoint Viewer or Powerpoint.
This
@GRALLIEN
Please read the entire thread of a bug report before commenting with
random noise. I clearly stated in the very first comment that THIS IS
NOT A PROBLEM IN LUCID. pps/ppt files which play perfectly in Lucid do
not work in Maverick.
--
You received this bug notification because you
I recently dist-upgraded one of my 10.10 machines that won't play sound
for .pps/.ppt files. This did not fix the problem. Note that my
problem is not the same as Andre Mangan's -- sound works perfectly with
every other application I've tried (VLC, firefox flash plugin, system
sounds, etc..).
fixed by installation of the kernel-specific alsa-driver update
What kernel are you using? It would be great if this issue could be
resolved by a simple apt-get dist-upgrade.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Here is a sample .pps file. The sound works on a relatively generic
lucid (Ubuntu 10.04, 64-bit) machine, does not work on maverick (Ubuntu
10.10, 64-bit).
** Attachment added: SalzburgolacunadeMozart.pps
Public bug reported:
Binary package hint: openoffice.org
On a Maverick (ubuntu 10.10) system (using OpenOffice 3.2.1-7), when I
try to open a .ppt file containing audio, the slides show, but the sound
doesn't play. Otherwise sound works on this system. If I take the same
.ppt file and open it
Public bug reported:
Binary package hint: php5-mcrypt
This bug only affects error logging (unfortunately I don't remember what
log file reported the problem), but should be extremely easy to fix.
The comment in /etc/php5/conf.d/mcrypt.ini is:
# configuration for php MCrypt module
but should
Mathias Gug wrote on 2010-04-01:
If /dev/xconsole doesn't exist rsyslog doesn't complain. So there is no real
need to comment the section in /dev/xconsole.
Not true:
May 16 09:58:56 ibis rsyslogd-2039: Could no open output file '/dev/xconsole'
[try http://www.rsyslog.com/e/2039 ]
I agree
Public bug reported:
Binary package hint: rsyslog
Particularly on servers, email should not be logged to. /var/log/syslog
by default, as this clogs up syslog with tons of stuff that is already
being logged to /var/log/mail.log, /var/log/mail.err,
/var/log/mail.info, and /var/log/mail.warn by
Public bug reported:
Why is this package listed under cyrus-sasl2 on launchpad when the
actual package name is sasl2-bin? This makes it hard to accurately
report bugs. Please stick to the convention package_name =
package_name_in_launchpad. Thanks.
** Affects: cyrus-sasl2 (Ubuntu)
I should have also pointed out that using the URL
http://bugs.launchpad.net/ubuntu/+source/sasl2-bin/+filebug?no-redirect
produces a page not found sort of thing.
--
Package is actually called sasl2-bin
https://bugs.launchpad.net/bugs/580700
You received this bug notification because you are a
Public bug reported:
I am trying to use postfix with cyrus. Since the debian postfix runs
chrooted by default and since the version of cyrus shipping with Lucid
has the location of the saslauthd socket hard-coded, it seems like the
best idea is to run separate saslauthd daemons for these
Please cancel this bug report -- I'm retarded. In the process of
testing all this stuff I created a /var/run/saslauthd symlink which I
had forgotten about. This is what was causing the second saslauthd
instance to fail.
** Changed in: cyrus-sasl2 (Ubuntu)
Status: New = Invalid
--
Public bug reported:
Why is this package listed under cyrus-sasl2 on launchpad when the
actual package name is sasl2-bin? This makes it hard to accurately
report bugs. Please stick to the convention package_name =
package_name_in_launchpad. Thanks.
** Affects: cyrus-sasl2 (Ubuntu)
I should have also pointed out that using the URL
http://bugs.launchpad.net/ubuntu/+source/sasl2-bin/+filebug?no-redirect
produces a page not found sort of thing.
--
Package is actually called sasl2-bin
https://bugs.launchpad.net/bugs/580700
You received this bug notification because you are a
Public bug reported:
I am trying to use postfix with cyrus. Since the debian postfix runs
chrooted by default and since the version of cyrus shipping with Lucid
has the location of the saslauthd socket hard-coded, it seems like the
best idea is to run separate saslauthd daemons for these
Please cancel this bug report -- I'm retarded. In the process of
testing all this stuff I created a /var/run/saslauthd symlink which I
had forgotten about. This is what was causing the second saslauthd
instance to fail.
** Changed in: cyrus-sasl2 (Ubuntu)
Status: New = Invalid
--
0-2 Today. Source package is called cyrus-sasl2
** Changed in: cyrus-sasl2 (Ubuntu)
Status: New = Invalid
--
Package is actually called sasl2-bin
https://bugs.launchpad.net/bugs/580700
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
could you place a Linux system in that 192.168.1.0/24 network and
reproduce the trace?
Good call, Thierry! I was certain that the linux machine would be able
to connect from 192.168.1.0/24, but was shocked to discover that it
doesn't. A trace of the packets shows the same lack of response from
could you place a Linux system in that 192.168.1.0/24 network and
reproduce the trace?
Good call, Thierry! I was certain that the linux machine would be able
to connect from 192.168.1.0/24, but was shocked to discover that it
doesn't. A trace of the packets shows the same lack of response from
For 10.4 Lucid, 32-bit Alpha3 + updates to Mar 8, Acer Aspire 3000
laptop, I still get the message Unsupported WMI interface, unable to
load, however the machine boots. Console video doesn't work properly,
and X doesn't display properly until I execute Ctrl-Alt-F1
followed by Ctrl-Alt-F7.
--
Thierry, as usual, thanks for your rapid response/attention to these
issues.
Good suggestion; I will try using a linux machine to connect from
192.168.1.x, which is my home network. First, let me point out that Win
XP and Mac OS X machines on various networks have been unable to connect
to the
Thierry, as usual, thanks for your rapid response/attention to these
issues.
Good suggestion; I will try using a linux machine to connect from
192.168.1.x, which is my home network. First, let me point out that Win
XP and Mac OS X machines on various networks have been unable to connect
to the
+1 for comment #13. It would be nice to see a running console log of
processes being started, even if this is only of psychological benefit.
--
Graphical Ubuntu logo enabled on servers, no more login prompt
https://bugs.launchpad.net/bugs/506297
You received this bug notification because you
Public bug reported:
Binary package hint: samba
Distro: Ubuntu Lucid Alpha 3
Package: samba 2:3.4.5~dfsg-2ubuntu3
I've been holding off on reporting this as a bug for several days, but
simply am not able to make any more progress. Previously we were
running Samba 3.0.2 on a Debian machine
** Attachment added: windowsXP_connect_attempt.pcap
http://launchpadlibrarian.net/40208367/windowsXP_connect_attempt.pcap
--
Samba: remote Win XP and Mac OS X machines can no longer mount shares
https://bugs.launchpad.net/bugs/532286
You received this bug notification because you are a
** Attachment added: linux_connect_negotiation.pcap
http://launchpadlibrarian.net/40208374/linux_connect_negotiation.pcap
--
Samba: remote Win XP and Mac OS X machines can no longer mount shares
https://bugs.launchpad.net/bugs/532286
You received this bug notification because you are a
Public bug reported:
Binary package hint: samba
Distro: Ubuntu Lucid Alpha 3
Package: samba 2:3.4.5~dfsg-2ubuntu3
I've been holding off on reporting this as a bug for several days, but
simply am not able to make any more progress. Previously we were
running Samba 3.0.2 on a Debian machine
** Attachment added: windowsXP_connect_attempt.pcap
http://launchpadlibrarian.net/40208367/windowsXP_connect_attempt.pcap
--
Samba: remote Win XP and Mac OS X machines can no longer mount shares
https://bugs.launchpad.net/bugs/532286
You received this bug notification because you are a
** Attachment added: linux_connect_negotiation.pcap
http://launchpadlibrarian.net/40208374/linux_connect_negotiation.pcap
--
Samba: remote Win XP and Mac OS X machines can no longer mount shares
https://bugs.launchpad.net/bugs/532286
You received this bug notification because you are a
Thanks for the clarification. I should have been more clear: when /var
is on a separate partition, the server won't boot -- period. I suppose
maybe I didn't wait long enough, but I don't think so -- it just hangs.
I think this issue is worthy of some discussion, as perhaps thanks to
the LSB,
I don't know if it's worth backporting 3.4.5 to Karmic. In researching
this problem and talking to a number of windows sys admins it seems that
most samba server users have just given up on roaming profiles because
they can't get them to work. It doesn't help that the XP Group Policy
settings
I don't know if it's worth backporting 3.4.5 to Karmic. In researching
this problem and talking to a number of windows sys admins it seems that
most samba server users have just given up on roaming profiles because
they can't get them to work. It doesn't help that the XP Group Policy
settings
Public bug reported:
Binary package hint: upstart
Distro: Ubuntu Lucid AMD64 Server daily build 2010-02-15
I think this is a problem with upstart, apologies in advance if it's
not. In installing Lucid on a new server, I discovered that grub2 has
problems with large / partitions (see Bug
This seems to be the default behavior for the current Lucid server
install. I.e., after I install Lucid AMD64 and every time the machine
reboots, it comes up to a flashing - prompt on vt7. I must then use
Alt-F1 to get to a login prompt. Not a big deal, but could be
confusing to new users of
OK, Samba 3.4.5, as shipped with Lucid (2:3.4.5~dfsg-2ubuntu1) solves
the roaming profile problem, more or less. Windows is very picky about
the precise permissions of the profile folder. The permissions on the
profile folders were drwx-wx---. This worked fine for fully patched
Windows XP SP3
** Attachment added: smb.conf
http://launchpadlibrarian.net/39499358/smb.conf
--
Samba 3.4.0 denies access to Roaming Profiles for XP Clients
https://bugs.launchpad.net/bugs/521085
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba
OK, Samba 3.4.5, as shipped with Lucid (2:3.4.5~dfsg-2ubuntu1) solves
the roaming profile problem, more or less. Windows is very picky about
the precise permissions of the profile folder. The permissions on the
profile folders were drwx-wx---. This worked fine for fully patched
Windows XP SP3
** Attachment added: smb.conf
http://launchpadlibrarian.net/39499358/smb.conf
--
Samba 3.4.0 denies access to Roaming Profiles for XP Clients
https://bugs.launchpad.net/bugs/521085
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
OK, I've determined that the problem was indeed the partition size. I
did another clean install, but this time set the size of the root
partition to a more manageable 50GB, and -- although the system insisted
on leaving the booted system at a non-existent vt7 prompt (server
install generally
Public bug reported:
Distro: Lucid AMD64 Server Daily Build 2010-02-15
Package: grub-common 1.98~20100128-1ubuntu3 (?)
After a clean install of this OS from CD, the machine reboots to a grub
prompt with no knowledge of root or boot information (i.e. the ls
command produces nothing). The only
Were you able to confirm that 3.4.5 is working correctly ?
Not yet; I will try and re-install with Lucid tomorrow and should have
an answer by Monday.
@Chuck: some indication of what additional information you want
(smb.conf? log files? output from ubuntu-bug?) would be helpful.
--
Samba 3.4.0
I've attached the last iteration of my smb.conf file before I gave up
and decided this must be a bug.
** Attachment added: smb.conf
http://launchpadlibrarian.net/39275245/smb.conf
--
Samba 3.4.0 denies access to Roaming Profiles for XP Clients
https://bugs.launchpad.net/bugs/521085
You
This is the similar current (original) smb.conf file which is still
working with 3.0.2
The big difference as far as this issue is concerned is this change in
the [profile] section:
force create mode = 0777
force directory mode = 0777
---
create mode = 0600
directory mode = 0700
Also attached output from ubuntu-bug.
** Attachment added: apport.samba.6Og_Ad.apport
http://launchpadlibrarian.net/39275483/apport.samba.6Og_Ad.apport
--
Samba 3.4.0 denies access to Roaming Profiles for XP Clients
https://bugs.launchpad.net/bugs/521085
You received this bug notification
Were you able to confirm that 3.4.5 is working correctly ?
Not yet; I will try and re-install with Lucid tomorrow and should have
an answer by Monday.
@Chuck: some indication of what additional information you want
(smb.conf? log files? output from ubuntu-bug?) would be helpful.
--
Samba 3.4.0
I've attached the last iteration of my smb.conf file before I gave up
and decided this must be a bug.
** Attachment added: smb.conf
http://launchpadlibrarian.net/39275245/smb.conf
--
Samba 3.4.0 denies access to Roaming Profiles for XP Clients
https://bugs.launchpad.net/bugs/521085
You
This is the similar current (original) smb.conf file which is still
working with 3.0.2
The big difference as far as this issue is concerned is this change in
the [profile] section:
force create mode = 0777
force directory mode = 0777
---
create mode = 0600
directory mode = 0700
Also attached output from ubuntu-bug.
** Attachment added: apport.samba.6Og_Ad.apport
http://launchpadlibrarian.net/39275483/apport.samba.6Og_Ad.apport
--
Samba 3.4.0 denies access to Roaming Profiles for XP Clients
https://bugs.launchpad.net/bugs/521085
You received this bug notification
Hmm, I see that you created and someone tested a modified 3.3.2 PPA
version, followed by the comment Marking this fixed in development
release (as 3.4.x contains the fix), and nominating for a Jaunty SRU.
but didn't see any actual evidence that the patch made it into 3.4.x.
My assumption was that
Let me know if I need to provide more information in order to confirm
this bug. Since I'm trying to upgrade production servers and am already
behind schedule, my plan was to go ahead and upgrade to Lucid (which has
samba 3.4.5) in order to solve the problem. People stuck running Karmic
who need
Hmm, I see that you created and someone tested a modified 3.3.2 PPA
version, followed by the comment Marking this fixed in development
release (as 3.4.x contains the fix), and nominating for a Jaunty SRU.
but didn't see any actual evidence that the patch made it into 3.4.x.
My assumption was that
Let me know if I need to provide more information in order to confirm
this bug. Since I'm trying to upgrade production servers and am already
behind schedule, my plan was to go ahead and upgrade to Lucid (which has
samba 3.4.5) in order to solve the problem. People stuck running Karmic
who need
Public bug reported:
Binary package hint: samba
Source Package: samba_2:3.4.0-3ubuntu5.4
Ubuntu Release: 9.10 (Karmic 64-bit AMD Server)
This is basically the same problem as reported in Bug #397699; however
the problem persists in Karmic (9.10) and has not been fixed, as far as
I can tell.
Public bug reported:
Binary package hint: samba
Source Package: samba_2:3.4.0-3ubuntu5.4
Ubuntu Release: 9.10 (Karmic 64-bit AMD Server)
This is basically the same problem as reported in Bug #397699; however
the problem persists in Karmic (9.10) and has not been fixed, as far as
I can tell.
Are you saying the workaround I posted to this bug doesn't work for you?
bpollen wrote:
Only workaround I have found is to reinstall grub-pc and grub-common...
EACH AND EVERY time you boot to Karmic. The it will time out and boot to
the default OS. But the next time you boot to Karmic (whether
Latest trunk includes my fix plus part of Felix' -- Robert Millan
Can you clarify what this means? Is this the latest trunk of grub2 dev?
When can we expect this to show up in the 10.4 daily build? Anyone who
dual boots Windows/linux (e.g. gamers) and already has Windows installed
is dead in
Jason Heblack wrote:
Hi:
I had an issue with karmic so now am on LTS 8.04. The issue was with
grub2
and I'm wondering if you had read this:
http://ubuntuforums.org/showthread.php?t=1312798highlight=grub
This does sound like it could be the same (or similar)
In the future please attempt to mentally parse a bug report before
marking it as invalid. Yes I do understand how syslog works. Note that
reporting a bug != to fixing a bug. If I have to download .src packages
and sift through source files and postinst scripts in order to describe
precisely
It's an unversioned dependency, so the old version satisfies the
dependency just as well and therefore apt doesn't bother to upgrade it.
(This may be an error in how the dependency is declared, but it's how it
is right now.)
Can we call this a bug? It seems pointless to have a dummy package
Yes, I understand, that's the point. If grub2 depends on grub-pc,
shouldn't this have updated as well when I updated grub2?
I noticed the grub problem on the initial install of alpha4 (or the
current daily build, I can't remember which) and worked around it as
outlined in the bug report. When
apt-get install grub2 updated the grub2 package to 1.97~beta3-1ubuntu8.
This appears to have fixed the problem, i.e. I ran
grub-install /dev/sda
and then changed the value of GRUB_HIDDEN_TIMEOUT back to 0 (the package
default)
GRUB_HIDDEN_TIMEOUT=0
ran grub-update, and the machine still
Steve Beattie wrote:
Patrick: can you update to the current version of grub2 in karmic and do
grub-install on your boot device (likely /dev/sda, but possibly not). I
am unable to reproduce the behavior you see with the current version of
grub2,
The current version is 1.97~beta3-1ubuntu8. I
Public bug reported:
Binary package hint: dovecot-postfix
I've been working with the dovecot-postfix package in karmic koala a5.
postfix seems not to be working properly with rsyslog; e.g. doesn't seem to be
aware of /etc/rsyslog.conf. All SMTP activity is logged to /var/log/syslog even
Public bug reported:
Binary package hint: dovecot-postfix
I've been working with the dovecot-postfix package in karmic koala a5.
postfix seems not to be working properly with rsyslog; e.g. doesn't seem to be
aware of /etc/rsyslog.conf. All SMTP activity is logged to /var/log/syslog even
Correction: dovecot 1.2.5 has just been released. This release
includes some critical performance fixes for large installations.
Surely it should be possible to upgrade this in Karmic before release?
--
New upstream version
https://bugs.launchpad.net/bugs/398272
You received this bug
Correction: dovecot 1.2.5 has just been released. This release
includes some critical performance fixes for large installations.
Surely it should be possible to upgrade this in Karmic before release?
--
New upstream version
https://bugs.launchpad.net/bugs/398272
You received this bug
Public bug reported:
Binary package hint: grub-common
The default settings for /etc/default/grub won't allow the machine to
boot through automatically to the default OS -- someone must hit Enter
on the console, which is almost never an appropriate configuration for a
server. Here is the default
Sebastien Bacher wrote:
could you try if that's still an issue in jaunty?
OK, I was just waiting for Alpha 3 to come out before giving it a try;
so can probably do this in the next few days.
--
Trash always full
https://bugs.launchpad.net/bugs/269441
You received this bug notification
This is a known bug, and has apparently been fixed in Java 6-10. The
version of java currently packaged for Intrepid is 6-07. This should be
upgraded to = 6-10 before Intrepid is released in order to resolve this
issue. Note that there is a workaround described at the very bottom of
the first
Public bug reported:
Binary package hint: alpine
Alpine 0.82+dfsg-5 (the version which ships with Ubuntu 7.04) seg faults
when attempting to view certain messages with attachments.
This problem is resolved in Alpine 0.99+dfsg-1, which I compiled from
debian source. At least it's resolved for
Public bug reported:
I'm using Feisty herd 4 and am doing some checksum tests with older
(Dapper Desktop/Alternative) CD's. Every time a Dapper CD is inserted
in the cdrom drive, a dialog box pops up with Upgrade volume detected
giving the user the choice to upgrade -- to an older version of the
*** This bug is a duplicate of bug 51792 ***
Public bug reported:
Binary package hint: blitz++
I experienced this while installing additional packages using Feisty
herd 4, which includes blitz++ 1:0.9-1.2
When using synaptic to install the blitz++ package, atlas3-3dnow is
auto-installed as a
Martin Schaaf wrote:
But why does the vesa driver use higher resolutions?
I'm just not sure -- there must be some kind of driver incompatability
which I haven't seen. What is the exact model of your laptop and what
does lspci tell you the video chip is?
--
dapper: intel 945 runs 640x480
Martin Schaaf wrote:
Someone suggested to increase the size of the video hardware in the BIOS
I do not have this option in the BIOS. And the vesa driver starts in
higher resolutions. The X server shows that my card has 8MB of memory.
hmmm, that's really weird. Changing the bios solved my
Martin Schaaf wrote:
Here my log for the non working lfp. Why can the vesa driver start in
higher reolutions? Can I set the supported panel size directly?
** Attachment added: i810 with the local flat panel.
http://librarian.launchpad.net/6197910/Xorg.log.lfp
Are you sure one of the
I'm still having all the problems described above with Edgy (6.10).
--
Unable to load any usable fontset
https://launchpad.net/bugs/2066
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
I was having similar problems (kernel panic when trying to install) with
a dual Opteron system, and actually tried every AMD/i386 version of
Dapper. The 21-Sep-2006 build of Edgy appears to install fine, though.
--
Dapper Flight 5 kernel panic on boot
https://launchpad.net/bugs/34515
--
Public bug reported:
Binary package hint: xserver-xorg-driver-i810
I installed Ubuntu 6.06 on a Dell SX260 and am only able to get one
resolution: 640x480 with 16 bits of color. The agpgart kernel module
is loaded DRI is working, the correct video driver (i810) is being used,
the problem seems
94 matches
Mail list logo
