Public bug reported:
Trying to install from a USB stick. Had Fedora 27 installed and working
before. Is on an NVMe drive if that matters. I selected the default
"delete everything, and repartition" option. Also told it to download
updates and 3rd party things (like for MP3 and WiFi). And trie
Public bug reported:
I'm on an ARM system, but I'm guessing this could happen on x86 or x64
too.
I start with a stock raring (13.04) install that does not have the
raring-updates debian package location in /etc/apt/sources.list. I
install xubuntu-desktop and chromium-browser. The last package a
A coworker found a PPA to test this with and it let our test script run
(that worked on an x86 similar system). Would be great to release it to
regular folks too :-)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchp
How can I test this? We'd really like this to work.
And was it correct that you changed chromium-browser, and not chromium-
driver?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1248745
Title:
chr
I don't have it in front of me (at home...and this is on a work
computer), but from what I remember the original chromedriver had
version numbers that looked like the chromium build. With the current
Ubuntu binary I saw v30... which roughly matches the current Chromium
build version number on the
Public bug reported:
While using selenium code that worked fine with chromedriver v2.3 and
v30 Chrome on x86 (but trying to run on an armhf system) I hit an error
that looks very similar to
https://code.google.com/p/chromedriver/issues/detail?id=471
Exception:
WebDriverException: Message: u"Unkno
Thanks for this, but I hit an issue that looks like
https://code.google.com/p/chromedriver/issues/detail?id=471...and the
response was "ChromeDriver 1 does not work with Chrome 29." There is a
ChromeDriver2 that needs to be packaged up. I assume a new bug should
be added, but figured it might be
Strike my statement above (can't find edit). Install didn't
automatically enable the device. After a manual "sudo ifconfig eth0 up"
and a "sudo dhclient eth0" it seems to work.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://
Still happens with 13.10 even though ppa referenced above claims the
drivers are in kernel 3.11 and the changes in the ppa are not needed on
saucy salamander (fails to install when I tried too).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Seems like it is related to making the USB bootable media on a Windows
machine. znorris said in a forum thread that making the USB stick with
DD let him install fine.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launch
The bug is likely the filename is too long for a FAT file system. I'd
guess DD makes a different filesystem.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1041911
Title:
Integrity Failure Alternati
*** This bug is a duplicate of bug 828850 ***
https://bugs.launchpad.net/bugs/828850
Was taken here automatically while trying to change my server target
after my initial change gave me an error after clicking the Check button
to get the list of available updates again.
--
You received this
Second try worked without problem. I've seen crashes/problems with
VirtualBox before on a couple different machines I have it on, so might
not be an Ubuntu problem.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpa
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/989270
Title:
Installing on a fresh VirtualBox machine it crashed/stopped
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubunt
Public bug reported:
Apparently this component failed during install into a new VirtualBox
virtual machine. Have turned on a lot of features that aren't defaults
so might be one of those (3d acceleration, VT-x, PAE/NX, 2 CPU's not
default of 1, USB 2.0 [EHCI] Controller) and have the extensions p
I'm still stuck using the less accelerated driver. I'd happily report
this upstream if I knew where.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/891947
Title:
Desktop not completely displayed aft
Installed copy is working using the Nouveau driver. Tried to switch by
just disabling the "post-release updates" entry in the 3rd party drivers
applet. Rebooted and same problem. This might be because I'd created
an xorg.conf in the process of trying to fix my problem. It still
listed the "nvid
Randomness...I setup my system to automatically login, but it seems to
boot up and let me start a terminal only to show the login prompt (that
I can't see). I've worked around it, but that seems broken too and
might stop others from even using their system.
Inside broken install sudo xrandr -q gi
Problem appears using Nvidia's driver, but not with NOUVEAU. Targeting
that package for now. Also appears in "post-release updates" version
aka nvidia-current-updates.
** Package changed: ubuntu => nvidia-graphics-drivers (Ubuntu)
--
You received this bug notification because you are a member
>From USB stick (try out Ubuntu), sudo randr -q gives...
Screen 0: minimum 320 x 200, current 1920 x 1200, maximum 8192 x 8192
DVI-I-1 connected 1920x1200+0+0 (normal left inverted right x axis y axis)
432mm x 324mm
1920x1200 60.0*+
1920x1080 60.0
1600x1200 60.0
168
I'm installing regular desktop Ubuntu, not server, x64 from USB as I've
hit a CD media bug with this system a while ago (updated existing bug
and not fixed). My motherboard does support EFI. For me to be able to
boot from the USB media in my BIOS's boot menu I can't do a "USB" boot,
I must do an
** Changed in: ubuntu
Status: Incomplete => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/891947
Title:
Desktop not completely displayed after install
To manage notifications about this
No change after installing "post-release updates" version and rebooting.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/891947
Title:
Desktop not completely displayed after install
To manage notific
Yep, I checked and the current driver version from Nvidia seemed to be
installed. I'm not sure how to install the experimental version. And
not sure how to switch to Nouveau (or if that could help). Command line
instructions are preferred.
--
You received this bug notification because you are
Public bug reported:
After installing my desktop is shifted to the left and up (can't see
that part of the screen). That seems to indicate the wrong resolution
or frequency to me. I'm using DVI output and a DVI to HDMI cable
(monitor was sold as a monitor, not TV). 1920x1200 is default
resoluti
I've hit this fairly repeatedly (always hit a grub2 error) on my system
after install. I'm doing a dual boot Windows 7 / Ubuntu 11.10 install
where I delete the existing Ubuntu install. I've fixed it every time
with instructions from the web that had me...
Boot with install media and select "try
** Description changed:
After installing my desktop is shifted to the left and up (can't see
that part of the screen). That seems to indicate the wrong resolution
or frequency to me. I'm using DVI output and a DVI to HDMI cable
(monitor was sold as a monitor, not TV). 1920x1200 is defau
Looks like I was wrong about this already working. But it is being
worked on (here http://wiki.debian.org/Multiarch/Implementation and here
https://wiki.ubuntu.com/MultiarchCross). Feel free to close this or use
it to justify the work :-).
Also if others need to do this you can try to use a scri
Public bug reported:
It appears the libmxml-dev package only installs the library for my
running system. I need to compile a 32 bit application on my 64 bit
system and the linker skips the installed libraries (.so and .a) as
they're incompatible with my object files.
I managed to manually get it
I hit this on a box I built myself. The same media has worked on two
other systems so I trust it. I tried using it a few different times and
tried to add a boot parameter of "all_generic_ide" at the suggestion
from a Linux Mint bug I found by Google'ing for the text. Only got
around it by instal
I've hit this twice now. I dual boot Windows and shrunk my boot
partition from inside it as I tend to trust MS tools manipulating their
own partitions better. Both times I came into Ubuntu's installer and it
acted as if there was no free space on the drive and that it had to
shrink the existing b
31 matches
Mail list logo
