Solution in #4 did NOT work for me.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1786822
Title:
Pinta constantly crashes in Ubuntu fresh install [double free or
corruption (out)]
To manage
Sorry I was not clear enough.
When I said "Filled with" I meant that they were the files occupying space. I'm
sorry if that gave the idea that the corresponding vmlinuz-* files weren't
present - it was just that in terms of bytes occupied, the initrd files are the
big ones.
As you can see from
Ok, did it.
That's freed up a load of space.
Where would I file the bug about having two sets of kernels?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1678187
Title:
Removing a linux-image-extra
I've not yet found a way to make a USB boot that would allow me to start
the machine in the event of something going wrong. Without a plan to
revert the change, I'm a bit nervous. I know it *should* work fine - but
I don't want to suddenly have an unbootable laptop I can't rescue.
--
You
This happens for me on 20.04 LTS when the file being copied has a colon
(:) in its name. The error doesn't pop up until the very end of the
file copy process, and in the end, the file is not copied to the
destination.
--
You received this bug notification because you are a member of Ubuntu
Thanks for that advice.
I'm a bit in trepidation about removing the default HWE. How do I protect
myself from having an unbootable system?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1678187
And then I tried "sudo linux-purge --keep=1".
That has tidied up a bit, but there's still not much space?field.comment=And
then I tried "sudo linux-purge --keep=1".
That has tidied up a bit, but there's still not much space.
Now /boot contains:
# du -sh /boot/*
248K
Here is the result of linux-purge --info
My /boot is like this:
# du -sh /boot/*
248K/boot/config-5.10.0-1038-oem
248K/boot/config-5.10.0-1044-oem
248K/boot/config-5.11.0-25-generic
248K/boot/config-5.11.0-27-generic
244K/boot/config-5.8.0-63-generic
48M /boot/efi
8.0M
I managed to get some free space back on /boot.
I'm posting this in the hopes that what I did may inform any fixing process.
1) List kernels with `dpkg -l | tail -n +6 | grep -E 'linux-image-[0-9]+'`
2) Delete the oldest initrd with update-initramfs -d -k 5.8.0-59-generic. There
was now 111Mb
I have now run linux-purge. It only freed up 50Mb or so, and no kernels
got removed
** Attachment added: "Directory listing for /boot"
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1678187/+attachment/5512828/+files/slash-boot-contents-post-linux-purge.txt
--
You received
Ok, more information. Just got warned that /boot is full again.
I have attached a directory listing for /boot.
Where do I find the logs for the update process that's doing this?
** Attachment added: "Directory listing for /boot"
This was a fresh install of 20.04. I enabled encryption as it's a work laptop.
I don't think I have logs - just the failure due to /boot being full on the
update UI.
I then followed the instructions at
https://help.ubuntu.com/community/RemoveOldKernels under "Safely remove old
kernels" so I
Just ran in to this on Ubuntu 20.04, with an encrypted root partition. The
partition layout is the one automatically generated when you install and ask
for root partition encryption - I didn't mess with it.
Drive is 512Gb NVME
Machine is a Lenovo Thinkbook 15
Kernel 5.8.0-59-generic
The /boot
/usr/lib/ubuntu-release-upgrader/check-new-release appears to lack any
architecture-awareness.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1790202
Title:
Ubuntu 16.04 on powerpc offered to
I think I see the same bug on Dell Inc. Latitude 7390 2-in-1/0YNG30,
BIOS 1.10.0 07/04/2019
Distributor ID: Pop
Description:Pop!_OS 20.04 LTS
Release:20.04
Codename: focal
Observed on the latest four kernel versions:
vmlinuz-5.4.0-7618-generic
vmlinuz-5.4.0-7629-generic
I cannot reproduce this issue.
These are the steps I used to attempt to reproduce:
1. Installed Ubuntu 18.04 from the Microsoft Store.
2. Created a new user on launch.
3. Confirmed openssh-server was installed.
4. Confirmed no .ssh folder existed in ~.
5. Ran $ ssh-keygen -t rsa -b 4096 to
Public bug reported:
"This message is shown once once a day." contains a typo.
It should read:
"This message is shown once a day."
** Affects: ubuntuwsl
Importance: Undecided
Status: New
** Affects: update-motd (Ubuntu)
Importance: Undecided
Status: New
** Also
/etc/update-motd.d/91-release-upgrade:
#!/bin/sh
# if the current release is under development there won't be a new one
if [ "$(lsb_release -sd | cut -d' ' -f4)" = "(development" ]; then
exit 0
fi
if [ -x /usr/lib/ubuntu-release-upgrader/release-upgrade-motd ]; then
exec
Public bug reported:
motd on demo of 20.04:
Welcome to Ubuntu 20.04 LTS (GNU/Linux 4.19.84-microsoft-standard
x86_64)
26 updates can be installed immediately.
0 of these updates are security updates.
To see these additional updates run: apt list --upgradable
I am changing the status of this bug to in progress because a patch for
this on WSl 1 is now available on Insiders Fast Ring and will be
backported to existing Windows 10 builds in the coming weeks.
We are tracking general issues on this at
https://bugs.launchpad.net/ubuntuwsl/+bug/1871240
**
** Summary changed:
- [focal][wsl] can't upgrade from eoan to focal due to libc6 postinst
+ Can't upgrade to Focal on WSL1 due to libc6 postinst
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1871240
** Changed in: ubuntuwsl
Status: New => Opinion
** Summary changed:
- Support for WSL
+ Support graphical applications out of the box in WSL
** Changed in: ubuntuwsl
Importance: Undecided => Medium
** Changed in: ubuntuwsl
Importance: Medium => Wishlist
--
You received this bug
This is a known issue and is being tracked upstream in WSL:
https://github.com/microsoft/WSL/issues/4898
We have guidance on this: https://discourse.ubuntu.com/t/ubuntu-20-04
-and-wsl-1/15291
** Bug watch added: github.com/microsoft/WSL/issues #4898
I concur on the urgency of these fixes at this late date.
wslu is a distinguishing feature of Ubuntu on WSL. It is important to
address these bugs in 20.04.
callmepk is the upstream author of wslu so I have confidence in his
patches.
I am running a build from callmepk's branch and have not
Public bug reported:
Upgrade path from 16.04 to 20.04 fails.
console-setup-linux_1.194ubuntu3_all.deb tries to overwrite
'/lib/systemd/system/console-setup.service', which is also in package
keyboard-configuration 1.108ubuntu15.5.
I have reproduced this bug on bare metal and WSL.
Log:
Public bug reported:
hayden@t470s:~$ sudo apt-get install gnome-boxes
[sudo] password for hayden:
Reading package lists... Done
Building dependency tree
Reading state information... Done
gnome-boxes is already the newest version (3.36.2-1).
0 upgraded, 0 newly installed, 0 to remove and 0
Thank you for trying.
I think it may have something to do with installing lubuntu-desktop on
an Ubuntu Sever image with other DEs at the same time.
If I get around to it I will see if I can reproduce it in isolation and
if so re-open.
--
You received this bug notification because you are a
Public bug reported:
The preinst script in ubuntukylin-default-settings overwrites Ubuntu in
/etc/os-release:
sed -i 's/\(NAME="Ubuntu\)"/\1 Kylin"/' /etc/os-release
sed -i 's/\(PRETTY_NAME="Ubuntu\) 1/\1 Kylin 1/' /etc/os-release
This results in:
$ cat /etc/os-release
NAME="Ubuntu
Public bug reported:
Steps to reproduce:
1. Install lubuntu-desktop on focal
2. Login via gdm3
3. Open QTerminal
4. $ snap install slack --classic
5. Open LXQt main menu
Expected results:
That newly installed snap applications would appear in LXQt main menu,
on an official flavor of Ubuntu.
** This bug is no longer a duplicate of bug 1869440
missing breaks/replaces for files moved between packages?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1869443
Title:
libvte attempts to
Public bug reported:
libvte-2.91-0 0.60.0-2ubuntu1 from focal-proposed tries to install
/usr/lib/systemd/user/vte-spawn-.scope.d/defaults.conf which is already
provided by libvte-2.91-common 0.60.0-2ubuntu1 and fails.
Steps to reproduce:
1. sudo apt install libvte-2.91-common
2. sudo apt
Since my upgrade today to 19.10 I am affected by the same bug, but with
different hardware
$ lspci -nnk | grep Network -A2
00:14.3 Network controller [0280]: Intel Corporation Cannon Point-LP CNVi
[Wireless-AC] [8086:9df0] (rev 30)
Subsystem: Intel
ASUS Vivobook S13 ASUS S330UA
Running "fprint-demo" reports "No devices found".
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1641290
Title:
[04f3:0903] Elan Microelectronics Corp fingerprint
This was determined to be a bug in the WSL1 ELF loader and fix is
inbound from the WSL side.
https://github.com/microsoft/WSL/issues/4461#issuecomment-536023805
Please close on Ubuntu.
** Bug watch added: github.com/microsoft/WSL/issues #4461
https://github.com/microsoft/WSL/issues/4461
--
>From the WSL issues page:
> Now, thing is, all of the new binaries (f.e. /bin/ls) have that
.plt.sec section also, and they work just fine. Also compiling a hello.c
with -fcf-protection works. Because of course it does. The only other
new section in there (Disco gzip has 27 sections, Eoan has
Public bug reported:
Summary:
Running gzip on WSL1 results in the following error:
$ gzip
-bash: /bin/gzip: cannot execute binary file: Exec format error
What I expect to happen:
gzip executes correctly on WSL1.
What happens instead:
gzip fails with an Exec format error.
Notes:
I suspect
For me, the root cause of this was systemd's inability to create
temporary files. I would get a ton of messages similar to "Unsafe
symlinks encountered in /var/run/sshd, refusing." in the systemd log,
By changing my system root directory (i.e. /) to be owned by root, it
fixed all these problems,
@rbalint
I can confirm working in bionic-proposed on WSL.
https://gist.github.com/sirredbeard/6c5f4a6501233c7887234e3b7ca64bc8
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1774120
Title:
I did some testing with bionic-proposed, it must not have come through
yet.
https://gist.github.com/sirredbeard/7afc9a95cb040a7d0886301cb26ccaae
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1774120
Thank you Balint.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1774120
Title:
ebtables cannot be upgraded from 2.0.10.4-3.5ubuntu2 to
2.0.10.4-3.5ubuntu2.18.04.1 on WSL
To manage notifications
of extraneous
dependencies.
There should be no need for adwaita-icon-theme, qt5-gtk-platformtheme,
and libxrandr2 on a machine with no X.
See:
hayden@t470s:~$ sudo apt-get install youtube-dl
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following
Balint,
I have opened a bug report upstream with netfilter team, who inherited
ebtables, regarding this.
https://bugzilla.netfilter.org/show_bug.cgi?id=1259
Hayden
** Bug watch added: bugzilla.netfilter.org/ #1259
http://bugzilla.netfilter.org/show_bug.cgi?id=1259
--
You received this bug
Dan and Eric,
Thank you for addressing this bug, I sincerely appreciate it.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1774120
Title:
ebtables cannot be upgraded from 2.0.10.4-3.5ubuntu2 to
According to https://github.com/marchom:
"The problem comes from the install/remove scripts trying to do service
ebtables stop and failing. You can see this by trying to stop ebtables
manually."
https://github.com/Microsoft/WSL/issues/1761#issuecomment-392575807
The temporary workaround is an
$ apt-get -V -s upgrade
NOTE: This is only a simulation!
apt-get needs root privileges for real execution.
Keep also in mind that locking is deactivated,
so don't depend on the relevance to the real current situation!
Reading package lists... Done
Building dependency tree
Reading state
Public bug reported:
ebtables cannot be upgraded on Ubuntu 18.04 for WSL.
apt-get upgrade fails with the following error:
Reading package lists...
Building dependency tree...
Reading state information...
Calculating upgrade...
The following packages will be upgraded:
ebtables
1 upgraded, 0
This is also affecting Ubuntu users on WSL.
https://github.com/Microsoft/WSL/issues/1761
** Bug watch added: github.com/Microsoft/WSL/issues #1761
https://github.com/Microsoft/WSL/issues/1761
** Attachment added: "terminal output of apt-get upgrade.txt"
Public bug reported:
The current packaged version is 3.2.6.
Spyder is already up to 3.2.8.
Fedora, SUSE, other distros have long since updated.
https://repology.org/metapackage/spyder/versions
** Affects: spyder (Ubuntu)
Importance: Undecided
Status: New
--
You received this
** Summary changed:
- cannot creat VMs
+ Cannot Create VMs in gnome-boxes
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1767800
Title:
Cannot Create VMs in gnome-boxes
To manage notifications
** Changed in: snapcraft (Ubuntu)
Status: Incomplete => New
** Changed in: snapcraft
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/1766101
Title:
Snapcraft
I am experiencing this issue as well.
** Attachment added: "troubleshooting info"
https://bugs.launchpad.net/ubuntu/+source/gnome-boxes/+bug/1767800/+attachment/5134592/+files/troubleshooting%20info
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
The upstream project has now switched to Meson, so while issues #1 and
#2 might still be issues with snap creation, and your fix may work, I am
now focusing on issue #3, getting snap to build with the Meson plugin.
If I run into any issues, I will open a separate bug ticket. Thank you.
**
** Description changed:
snapcraft, version 2.41+18.4.2
I am trying to build my first snap from a Github project,
- jangernert/FeedReader, https://github.com/jangernert/FeedReader.
+ jangernert/FeedReader. There is no Debian/Ubuntu package available and
+ the Flatpak is broken.
- This is
snapcraft, version 2.41+18.4.2
** Also affects: snapcraft (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1766101
Title:
Snapcraft not handling
Public bug reported:
[needs-packaging] feedreader
FeedReader is a modern desktop application designed to complement
existing web-based RSS accounts.
FeedReader supports Feedbin, feedly, FreshRSS, InoReader, OwnCloud, The
Old Reader, Tiny Tiny RSS, and local RSS.
FeedReader can save to
There's a discussion here possibly about the same problem:
https://patchwork.ozlabs.org/patch/801533/
And they referred to this patch:
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-
stable.git/commit/?id=242d3a49a2a1a71d8eb9f953db1bcaa9d698ce00
The changes look like they
Thanks for the deep dive, Elvis! :) Is it possible to adjust some of
these settings in the Ubuntu packages, or is just the way it will be
going forward?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
My system worked correctly with the mainline 4.4.68 kernel, so it
appears to be fixed upstream.
** Tags added: kernel-fixed-upstream
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
** Description changed:
- After upgrading from 4.4.0-63 to 4.4.0-64, X.org will no longer
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1691174
Title:
Kernel 4.4.0-64 fails to provide /dev/dri/card0 for Radeon card
To
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1691174/+attachment/4877696/+files/UdevDb.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1691174
Title:
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1691174/+attachment/4877697/+files/WifiSyslog.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1691174
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1691174/+attachment/4877691/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1691174
apport information
** Attachment added: "PulseList.txt"
https://bugs.launchpad.net/bugs/1691174/+attachment/4877695/+files/PulseList.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1691174
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1691174/+attachment/4877687/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/1691174/+attachment/4877690/+files/Lsusb.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1691174
Title:
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1691174/+attachment/4877689/+files/Lspci.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1691174
Title:
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1691174/+attachment/4877692/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1691174
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1691174/+attachment/4877693/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Tags added: apport-collected xenial
** Description changed:
After upgrading from 4.4.0-63 to 4.4.0-64, X.org will no longer load my
Radeon card and I am presented with a low-res fallback desktop.
Reverting to the 4.4.0-63 kernel restores ability of X.org to load the
apport information
** Attachment added: "JournalErrors.txt"
https://bugs.launchpad.net/bugs/1691174/+attachment/4877688/+files/JournalErrors.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1691174/+attachment/4877694/+files/ProcModules.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1691174
Public bug reported:
After upgrading from 4.4.0-63 to 4.4.0-64, X.org will no longer load my
Radeon card and I am presented with a low-res fallback desktop.
Reverting to the 4.4.0-63 kernel restores ability of X.org to load the
Radeon driver.
I receive the following message in Xorg.0.log:
[
My testing was done on Xen virtual machines, KVM virtual machines, and
bare metal.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1638695
Title:
Python 2.7.12 performance regression
To manage
Public bug reported:
This is apparently fixed in systemd 231:
https://lists.freedesktop.org/archives/systemd-
devel/2016-August/037385.html
When systemd tries to put a VLAN interface into a bridge on Xenial, it
fails:
# journalctl --boot -u systemd-networkd
Jan 15 09:16:46 hydrogen
Thanks for confirming that, Matthias. Testing with GCC 4.8 seemed to
yield (mostly) better results. I put the data into a Google Sheet:
https://goo.gl/9gW82j
Out of the 10 pyperformance tests:
* 3 tests were actually faster with python compiled w/gcc-4.8
* 4 tests were slightly slower
I can try that. Just to be clear, you're suggesting to do the
following:
1) Install gcc-4.8 on 16.04
2) Compile 2.7.12 with gcc-4.8 on 16.04
3) Re-run tests
Did I get that right?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Hello Matthias,
I'm sorry for the confusion there. What I meant is that I compiled
2.7.12 on 14.04 and found that it had the same performance as 2.7.6
(from the default Ubuntu python package) on 14.04. I also loaded
Xenial's kernel on the 14.04 installation and found no performance
difference
Public bug reported:
I work on the OpenStack-Ansible project and we've noticed that testing
jobs on 16.04 take quite a bit longer to complete than on 14.04. They
complete within an hour on 14.04 but they normally take 90 minutes or
more on 16.04. We use the same version of Ansible with both
@Andon-2 -- I wish I had better news. :/
Long story short, I was able to build a 3.19-ish kernel with some
additional ASoC patches earlier this week and the card showed up on the
I2S bus with full input/output capabilities. However, whenever I played
sounds, I never heard anything. PulseAudio
I'm building with those new SoC patches now. My first couple of builds
didn't work out and I discovered that my .config didn't have modules
enabled for some of those SoC audio codecs. I'll hopefully know
something more soon.
--
You received this bug notification because you are a member of
I tested David's rt288.patch above on 3.19-rc7 and it had no effect on
the audio problem. I tried it with and without reverting the i2c IRQ
patch that fixed the touchpad.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Done with the git bisect. It's somewhere in the late days of 3.17 and
early days of 3.18. Here's the RHBZ with the patch:
https://bugzilla.redhat.com/show_bug.cgi?id=1188439#c25
I'm hoping someone with more knowledge than me around this part of the
kernel can make sense of it. If I pull the
I'll be firing up a kernel bisect this weekend to see if I can find the
issue. From multiple reports (incuding some in the RHBZ[1]), 3.16 works
and 3.17 has issues. 3.18 and 3.19-rc7 have no improvements.
[1] https://bugzilla.redhat.com/show_bug.cgi?id=1188439
--
You received this bug
Mario --
So 3.18 didn't have any touchpad freeze or tapping issues? I've tested
3.18.3 and 3.18.5 on Fedora and they have the freezes. I'm wondering if
something broke between 3.18.0 and 3.18.3. Do you have any additional
details on that 3.18 kernel you tested? Perhaps the git hash?
--
You
FWIW, this issue happens for me on the same hardware on Fedora. Already
tried kernels 3.17.4, 3.18.3, and 3.18.5. Blacklisting i2c_hid doesn't
have an effect on the touchpad freeze-ups that Jared noted.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
I can confirm that changing dependency from sysvinit to sysvinit-utils
fixes the issue.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1408135
Title:
live-config fails to install
To manage
Sorry if I wasn't clear, but the packages provided by Maarten 100% fix
the issue with me. I'll attempt to label this bug as verification
done
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1313986
Changed fixes issue
** Tags removed: verification-needed-trusty
** Tags added: verification-done-trusty
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1313986
Title:
[GeForce 9400 GT] Nouveau
Yes the driver works as expected with those packages at that URL.
Linux hayden-ubuntu 3.13.0-25-generic #47lp1313986 SMP Tue Apr 29
11:51:24 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux
[39.642] (II) LoadModule: nouveau
[39.642] (II) Loading /usr/lib/xorg/modules/drivers/nouveau_drv.so
So It still works for me ..How ever some AP's don't. very strange
indeed. I connects then boots me after a few seconds on some AP's. not
sure why..about ready to try Fedora again. I post a fix if I figure out
something better..
peace
--
You received this bug notification because you are a
Also hardware is NVIDIA Corporation G96 [GeForce 9400 GT] (which you'll
also see from the lspci output)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1313986
Title:
Nouveau driver does not work
Public bug reported:
From /var/log/Xorg.0.log:
[35.117] (EE) open /dev/dri/card0: Invalid argument
root@hayden-ubuntu:~# lsmod | grep nouveau
nouveau 1097199 0
mxm_wmi13021 1 nouveau
wmi19177 2 mxm_wmi,nouveau
video 19476
Attaching log from successful launch on kernel 3.14.2-031402 (upstream)
** Attachment added: Xorg.0.log.old
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1313986/+attachment/4099979/+files/Xorg.0.log.old
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Attaching Xorg.0.log from failed launch on 3.13.0-24
** Attachment added: Xorg.0.log
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1313986/+attachment/4099978/+files/Xorg.0.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Glad to be of assistance Jorge ! this is what the open source community is all
about! Lubuntu runs well on My new
windows 8 Asus laptop..well its not windows 8 any more! with secure boot
enabled! UEFI ! runs super fast now..thanks to all the hard work of the DEVs.
--
You received this bug
This is What worked for me
sudo apt-get install wicd
sudo apt-get purge network-manager-gnome
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1308348
Title:
network settings indicator missing
I am also getting this error on 13.10.
I would like a solution so I can stream my new music. :(
** Also affects: ubuntu
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
*** This bug is a duplicate of bug 1235054 ***
https://bugs.launchpad.net/bugs/1235054
I cannot see the bug that this issue was marked a duplicate of. I
believe this may be a mistake.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
together with no whitespace.
Best Regards,
Collin Hayden
** Affects: ubuntu-docs (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1200816
Title:
ldap
ArecordDevices:
List of CAPTURE Hardware Devices
card 0: PCH [HDA Intel PCH], device 0: ALC270 Analog [ALC270 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: hayden 1863 F pulseaudio
/dev/snd
1 - 100 of 165 matches
Mail list logo
