FWIW, I did the following:
$ git clone git://kernel.ubuntu.com/ubuntu/linux-firmware.git
...
$ cd linux-firmware
$ git checkout bionic
...
$ sudo cp ath10k/QCA6147/hw3.0/* /lib/firmware/ath10k/QCA6147/hw3.0/
The new firmware seems to drop my connections much more infrequently.
Perhaps upgrading t
I have had almost identical behavior with a completely different wifi
setup. My card is the following:
3a:00.0 Network controller: Qualcomm Atheros QCA6174 802.11ac Wireless
Network Adapter (rev 32)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribe
And FWIW, I did try the generic upstream kernel. Exact same behavior.
Also found this: https://askubuntu.com/questions/967355/wifi-unstable-
after-17-10-update/969282#
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launc
This has been a problem for quite a while. What functionality would I
lose by uninstalling urfkill?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1385641
Title:
urfkilld use 100% cpu after resume
T
I just had this happen on 15.10.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1385641
Title:
urfkilld use 100% cpu after resume
To manage notifications about this bug go to:
https://bugs.launchpad
Here's some more info:
I ran "dpkg --configure -a" as root, which failed.
Then I ran "sudo dpkg --configure -a" as my user with sudo privileges
and it worked. Now my system is not in an unconfigured state.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is s
Public bug reported:
This package failed to be configured during an upgrade.
ProblemType: Package
DistroRelease: Ubuntu 15.10
Package: gconf2 3.2.6-3ubuntu3
ProcVersionSignature: Ubuntu 4.2.0-12.14-generic 4.2.1
Uname: Linux 4.2.0-12-generic x86_64
ApportVersion: 2.19.1-0ubuntu2
Architecture: amd
Is it possible to run that kernel with the wl wireless driver? Dell
stupidly ships this laptop with a wireless nic that requires a
proprietary driver.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1475
The following appeared in dmesg after I got that last dmesg.txt:
[ 831.299129] Raw EDID:
[ 831.299132] 02 03 1d f1 50 90 05 04 03 02 07 16 01 06 11 12
[ 831.299133] 15 13 14 1f 20 23 09 1f 07 83 01 00 00 02 3a 80
[ 831.299134] 18 71 38 2d 40 58 2c 45 00 81 91 21 00
** Attachment added: "Here's another dmesg.txt with ubuntu kernel version
3.19.0-25-generic #26"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1475729/+attachment/4439081/+files/dmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribe
Public bug reported:
I am using the Dell XPS 13 9343. When I plug into a Dell U3014 monitor,
there is a lot of funky behavior. In dmesg I see a ton of backtraces.
I've attached a dmesg output with the traces.
ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: linux-image-3.19.0-22-generic 3.19
Thanks for that info Seth. I guess I am suffering from multiple issues.
Is there any work on the BCM4352 in the linux kernel right now? This
proprietary driver is a black box.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bug
Public bug reported:
I've included a dmesg from after a point when the wireless is no longer
working. Also, I experience frequent panics (caps lock blinking). I
don't know if that is related since I haven't yet been able to get any
information after such a crash. When it crashes that way, I genera
FWIW, I can't figure out how to close this issue.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1395553
Title:
iwlwifi contiually crashes
To manage notifications about this bug go to:
https://bugs.
Okay, so I did some further research. I found that my linux-firmware
package was not upgrading. It was stuck at some ancient version. That is
why I didn't have the updated firmware. The weird thing was that "apt-
get dist-upgrade" was not showing is as a package that needed upgrading.
However, "apt
I do get this message with the utopic kernel with the v9 firmware:
[ 394.569319] [ cut here ]
[ 394.569358] WARNING: CPU: 0 PID: 1290 at
/build/buildd/linux-3.16.0/drivers/net/wireless/iwlwifi/mvm/tx.c:191
iwl_mvm_set_tx_params+0x5da/0x6d0 [iwlmvm]()
[ 394.569361] Got a
Oh yeah, this works a million times better with firmware v9 on the
utopic kernel. The V8 firmware appears to be broken with my setup. Is
there any chance that the v9 firmware for the 7620 at
http://wireless.kernel.org/en/users/Drivers/iwlwifi/ can be added to
linux-firmware?
Also, why isn't apport
It seems to work much better with firmware version 9 on the mainline
3.17.4. I don't see any of the firmware SW error messages. I will reboot
now and try the normal utopic kernel.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https:/
I installed the 3.17 from the mainline kernels from that wiki page. Here's the
uname -a:
Linux braindead 3.17.4-031704-generic #201411211317 SMP Fri Nov 21 18:18:15 UTC
2014 x86_64 x86_64 x86_64 GNU/Linux
It fails in a similar way:
[ 167.366951] iwlwifi :02:00.0: Microcode SW error detected
There is a performance impact in that my WIFI sometimes drops out with
no seeming cause. I usually have to stop networking and restart it in
the network manager menu. I don't know if this is related to the
microcode software.
I know that I was having some issues in 14.04. However, I don't know if
Public bug reported:
I am getting "Microcode SW error detected" constantly in my dmesg
output. As a result, I am getting a lot of apport popups. However, the
apport popups are not launching a browser when I say to report the bug.
I am filing this bug with "ubuntu-bug linux". Hopefully, all the nee
I just found that the apparmor profile for docker was disabled for some
reason. After removing the symlink from /etc/apparmor.d/disable/docker,
it works. I don't remember ever adding docker to the apparmor disable
links.
--
You received this bug notification because you are a member of Ubuntu
Bug
I also tried the 3.17.0-031700-generic #2001410060605 linked above. It
also does not work on that kernel.
# docker run -i -t ubuntu /bin/bash
Unable to find image 'ubuntu' locally
Pulling repository ubuntu
1357f421be38: Download complete
511136ea3c5a: Download complete
1de2bd7201a2: Download com
Just so you know, here's the docker.io package version also:
ii docker.io 1.2.0~dfsg1-1ubuntu1 amd64Linux container runtime
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1371310
Title:
I am getting the following still.
# docker run -i -t ubuntu /bin/bash
set apparmor profile docker-default: no such file or directory2014/10/13
11:05:41 Error response from daemon: Cannot start container
7981801146ab1771470fd72bc97e6582ff573fa159199f6cb86afaa7eaa74ea9: set apparmor
profile docker
Public bug reported:
I was upgrading to the development version of 14.10 today, and kernel-
common asked about the config file /etc/kernel-img.conf. I don't know
how to handle the issue, but the file content report that the contents
are only there for legacy use. Should it consider just overwritin
AFAICT, the code doesn't do anything with gids. It only creates the user
ACL.
Also, I understand there are other files that probably need their perms
changed. However, my only point was that udisks is in a position to be
more helpful by either informing the user of what is happening or
rewriting p
Okay, if I understand this correctly, you're saying that we shouldn't
even tell the user that the directory that udisks would have created has
different permissions than what udisks would have created it with?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Sure, changing a uid is not that common, but it is a supported operation
through the usermod tool, and there are valid reasons to do it.
In this specific case, I didn't change the uid while logged in. I logged
out, logged in with a different user on tty1, "sudo -i" to get a root
shell, then change
Here's some links to code.
Here's the upstream code link:
http://cgit.freedesktop.org/udisks/tree/src/udiskslinuxfilesystem.c#n899
Here's the Utopic code:
http://bazaar.launchpad.net/~ubuntu-branches/ubuntu/utopic/udisks2/utopic/view/head:/src/udiskslinuxfilesystem.c#L891
Here's the trusty code:
This bug is not invalid. There is a very real UX concern here.
** Changed in: udisks2 (Ubuntu)
Status: Invalid => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1335384
Title:
udisks does
Public bug reported:
I am using a just updated copy of 14.04. The version of the udisks2
package is 2.1.3-1.
I changed the UID of a user on my system from 1001 to something else.
After the change, the ACL permissions on /media/ still
reflected the old UID. After I deleted the directory and insert
So, it seems like the kernel problem is solved. Now, where do I file a
bug about crappy behavior of the touchscreen in Xorg (and Unity as a
result)? I don't want to clutter this bug with that info.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Just rebooted into this kernel. Seems to be working so far.
wt
On Thu, May 15, 2014 at 12:12 PM, Kent Baxley <1305...@bugs.launchpad.net>wrote:
> Also tested acelan's kernels with an XPS15 (model 9530) which has the
> same touchscreen but a non i2c synaptics touchpad. The touchscreen and
> tou
So I loaded the module, there are no messages generated in dmesg as a
result.
Also, I ran this in another window while loading the module just to make sure:
# udevadm monitor
monitor will print the received events for:
UDEV - the event which udev sends out after rule processing
KERNEL - the kernel
Here's the logs just after reboot. I also added a "uname -a" to make
sure that it's clear which kernel version is being used.
FWIW, when I rebooted the laptop, it locked up on the dell bios screen.
I had to cold boot to get it to boot into ubuntu. This probably was more
prevalent before the latest
Here are logs for the above linked kernel.
Uname for reference:
$ uname -a
Linux braindead 3.13.0-24-generic #46 SMP Tue Apr 22 09:25:58 UTC 2014 x86_64
x86_64 x86_64 GNU/Linux
** Attachment added: "requested logs for 3.13.0-24-generic kernel"
https://bugs.launchpad.net/ubuntu/+source/linux
Is this fix expected to break my touchscreen?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1305522
Title:
Backport Synaptics HID touchpad driver for 14.04
To manage notifications about this bug go
I just realized that this kernel has broken my touchscreen. Is that
expected?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1265885
Title:
regression: SynPS/2 touchpad detected as DLL060A:00 pointer
This bug is probably going to be fixed when bug 1265885 is. There is a
working kernel that was linked to the other bug. I don't know if the
patch has made it to a stable kernel yet.
FWIW, this bug may just be a dupe of bug 1265885.
--
You received this bug notification because you are a member o
I just wanted to report in and say this is still working great. Thanks
for the hard work on this. This will be great for anyone else using the
same hardware.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bu
Public bug reported:
I have attached a patch for support for lzo files. Please feel free to
contribute it upstream if there is such a thing.
** Affects: bash-completion (Ubuntu)
Importance: Undecided
Status: New
** Tags: patch
** Attachment added: "The two character patch to add
Great news! With the new kernel, everything seems to work like when I
don't blacklist the driver. The devices are named differently though.
wt@braindead:~$ xinput list
⎡ Virtual core pointer id=2[master pointer (3)]
⎜ ↳ Virtual core XTEST pointerid=4
Do you want me to install that kernel? Or are you talking to Janus?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1265885
Title:
regression: SynPS/2 touchpad detected as DLL060A:00 pointer
To manag
This bug doesn't appear to exist in the new Trusty release.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1263219
Title:
kernel panics with BUG
To manage notifications about this bug go to:
https:/
What is the fix that was released? Do I still need to blacklist in
trusty?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1265885
Title:
regression: SynPS/2 touchpad detected as DLL060A:00 pointer
T
Okay, I am booted into the kernel @http://kernel.ubuntu.com/~kernel-
ppa/mainline/v3.11-saucy/. It works just fine. This seems to be a
mainline 3.11 kernel. Does that help close the gap for where the problem
showed up?
--
You received this bug notification because you are a member of Ubuntu
Bugs,
The latest proposed kernel fails even worse than my original report. The
conditions when it fails (that is when the iwlwifi module is loaded) is
the same. However, now blacklisting iwlwifi and then manually modprobing
it after logging in locks up the system such that I cannot capture the
dmesg. Bef
I am just curious. Is saucy going to be updated? It might be a shocker
to someone when they can't get a network connection on saucy?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1263219
Title:
kern
There are all kinds of ACPI errors in the dmesg.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1265885
Title:
regression with respect touchpad
To manage notifications about this bug go to:
https://
With code based on linus' tree in a git clone that I git pulled this
morning, I get the same results. I have attached the dmesg.
** Attachment added: "dmesg from linux-3.14.beforerc1"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1265885/+attachment/3963823/+files/linux-3.14.beforerc1.d
The iwlwifi module works fine with a kernel based on Linus' tree that I
compiled this morning.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1263219
Title:
kernel panics with BUG
To manage notifica
The version "3.13.1-031301-generic" also seems to work without issues.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1263219
Title:
kernel panics with BUG
To manage notifications about this bug go
Work with regard to the iwlwifi module, that is.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1263219
Title:
kernel panics with BUG
To manage notifications about this bug go to:
https://bugs.launc
I can confirm that that kernel version v3.13.1 from the above line still
has the bug. I can also confirm that blacklisting i2c_hid makes the
touchpad work in that kernel version.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://
Similar to bug 1265885. FTR, I tried the blacklist trick and it worked.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1273403
Title:
[Dell XPS 13 9333] Touchpad not detected correctly
To manage not
This bug is appears to be a duplicate of bug 1263319. However, I have
not reinstalled. I would really like to help make sure this issue is
handled properly so that other don't upgrade into this state like I
did.
--
You received this bug notification because you are a member of Ubuntu
Bugs, whic
Bah, I guess that was expected since the 3.11 series of kernels worked.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1265885
Title:
regression with respect touchpad
To manage notifications about t
I just tried another of the generic kernel. Here's some info:
wt@braindead:~/Documents$ cat linux-3.9.0-030900.has_touchpad_controls.txt
uname -a
Linux braindead 3.9.0-030900-generic #201304291257 SMP Mon Apr 29 16:58:15 UTC
2013 x86_64 x86_64 x86_64 GNU/Linux
dmesg | grep syn
[ 10.221126] ps
I just tried the kernel you pointed me to (version
"3.12.0-031200-generic #201311071835") does not show the touchpad
controls. And just for the record, I don't see any of the messages I
posted above shortly after boot. Here's proof:
wt@braindead:~$ dmesg | grep syn
wt@braindead:~$
--
You receive
Here's another data point as I just tried another of the generic
kernels. Version "3.12.0-031200-generic #201311071835" has no problems
with the iwlwifi AFAICT.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net
I am sorry. I have been extremely busy these past couple weeks. I'll try
to make some progress soon.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1265885
Title:
regression with respect touchpad
To
Oh, and FWIW, I found this in dmesg:
wt@braindead:~$ dmesg | grep syn
[202484.540150] psmouse serio1: synaptics: Unable to query device.
[204320.591775] psmouse serio1: synaptics: Unable to query device.
[206356.441278] psmouse serio1: synaptics: Unable to query device.
[214607.673218] psmouse ser
I am sorry. I have been extremely busy these past couple weeks. I'll try
to make some progress soon.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1263219
Title:
kernel panics with BUG
To manage no
Okay. I loaded the trusty linux-image+extras (3.12.0-8-generic) into
saucy. There are still no input settings for my touchpad in the system
settings.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/12658
Okay. I loaded the trusty linux-image+extras (3.12.0-8-generic) into
saucy. There are no problems with wifi in this version. Dmesg is clean.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1263219
Title
Okay, so I found 3.11.0-15.23. Is that the one you'd like me to test at
this time?
I found it: at http://archive.ubuntu.com/ubuntu/ubuntu/pool/main/l/linux
/linux-image-3.11.0-15-generic_3.11.0-15.23_amd64.deb
--
You received this bug notification because you are a member of Ubuntu
Bugs, which i
FTR, there is a crash with 3.11.0-15.16. It looked different though. It
happened after I saw the message about searching for Btrfs filesystemss.
I don't have any more info at this time. I want to try the 3.11.0-15.22
kernel and maybe the latest trusty kernels. Where do I find them?
--
You receive
@jsalisbury, I only see 15.16...where do I get that one from?
@Christopher. I'll see what I can do as this is my work laptop.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1263219
Title:
kernel pan
I am just warning you that this problem may existing in what will become
trusty. Is this not a valid bug to file in that case?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1265885
Title:
regression
This regression is present in kernel version 3.12.6-031206-generic.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1265885
Title:
regression with respect touchpad
To manage notifications about this
This kernel BUG does not occur on kernel version 3.12.6-031206-generic.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1263219
Title:
kernel panics with BUG
To manage notifications about this bug go
Public bug reported:
This regression occurs somewhere between 3.11.0-14-generic (latest on
saucy) and 3.13.0-031300rc6-generic (a test kernel). On the earlier
kernel, I actually get settings for setting up my touchpad in the unity
interface. With the updated kernel, those options disappear. I onl
Filed new bug:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1265885
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1263219
Title:
kernel panics with BUG
To manage notifications about this bu
Is there a bug for the suspend? I have additional information I don't
want to pollute this bug with.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1263219
Title:
kernel panics with BUG
To manage no
For the record, the problem doesn't to be related to resuming after
suspend, I have the same touchpad problem after reboot with the new
kernel.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1263219
Ti
Well, I see the touchpad in the xinput list. It's just that the options
for the touchpad are gone in the System Settings.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1263219
Title:
kernel panics w
FWIW, a new issue has cropped up with the new kernel. It looks like my
touchpad disappears after resume from suspend for the night.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1263219
Title:
kerne
FTR, here's the kernel version that's failing to boot:
$ dpkg -s linux-generic | grep Version
Version: 3.11.0.14.15
I see a number of other kernels associated with saucy in the list at
http://kernel.ubuntu.com/~kernel-ppa/mainline/. Are there updates that
haven't made it to saucy yet?
--
You re
Sorry for the delay...holidays and all. I installed version
3.13.0-031300rc6-generic, which is beyond what was listed above. I hope
that is okay. Everything seems to work just fine in this kernel. No
panics and no BUGS during boot. Dmesg is also clean.
** Tags added: kernel-fixed-upstream
--
You
Here is the dmesg output.
This info is a little tricky to collect since I can't bring up my
network (or shutdown my computer normally) after the BUG occurs. I have
to boot into a 13.04 kernel to actually post this info. :) Does the
apport store the output locally somewhere that will survive a rebo
Public bug reported:
I have a Dell Sputnik 3 that I just got and upgraded it to
12.10->13.04->13.10. On boot the kernel crashes with a BUG. I can
prevent the crash by blacklisting the iwlwifi module and I can cause the
BUG by manually loading the module. I will attach a dmesg output from
after the
Public bug reported:
This happened while upgrading to 13.10 with update-manager -d.
ProblemType: Package
DistroRelease: Ubuntu 13.10
Package: dell-recovery (not installed)
ProcVersionSignature: Ubuntu 3.11.0-4.9-generic 3.11.0-rc7
Uname: Linux 3.11.0-4-generic x86_64
ApportVersion: 2.12.1-0ubuntu
Mine is also broken.
$ uname -a
Linux wt-demo 3.8.0-23-generic #34-Ubuntu SMP Wed May 29 20:22:58 UTC 2013
x86_64 x86_64 x86_64 GNU/Linux
This is a 1080P model that came with 12.04 and was upgraded to 13.04.
The brightness can be changed when in grub, but it stops working once I
am in LInux. I a
To quote my original description:
Expected Results:
The user should be able to "Save as..." to a new file and just have a copy of
the PDF with the filled in form data.
I believe this is exactly what Marcus was asking for.
--
You received this bug notification because you are a member of Ubuntu
I am running a sputnik laptop in a dual boot configuration with Ubuntu
12.04. I just updated my grub-pc to version 1.99-21ubuntu3.4 and am
getting the blocklists error. Selecting /dev/sda6 during the upgrade of
the package fails. I had to select that I was okay skipping the
installation of the boot
** Description changed:
The network-manager service doesn't start automatically after I boot up
a laptop recently upgraded to Quantal.
- Here's the /etc/network/interfaces:
- auto lo
- iface lo inet loopback
+ == Regression details ==
+ Discovered in version: 0.9.6.0-0ubuntu7 (12.10 beta 1)
BTW, this is a regression in functionality. I hope it can be fixed
before the final as it's a bad scenario where an improper auto stanza in
a network configuration can stop network-manager from starting. This
could catch people off guard.
Is there anything else I can do to help track this down?
*
Actually, I copied the /etc/network/interfaces from the wrong computer. Here's
the right one:
auto lo
iface lo inet loopback
auto sprint
iface sprint inet ppp
provider "sprint"
That second interface had no chance to successfully come up as I don't even
have that wifi card anymore. When I comm
Public bug reported:
The network-manager service doesn't start automatically after I boot up
a laptop recently upgraded to Quantal.
Here's the /etc/network/interfaces:
auto lo
iface lo inet loopback
** Affects: network-manager (Ubuntu)
Importance: Undecided
Status: New
--
You rec
Public bug reported:
The autostart file at /etc/xdg/autostart/blueman.desktop seems to make blueman
start for all non-LXDE desktop environments. It does this with the following
line:
NotShowIn=LXDE
I think that this line should be replaced with a line that explicitly only
starts blueman in cer
Is there a better tag than patch to indicate that I have added a fix, if
not a patch, to this bug.
** Tags added: patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/682211
Title:
lastcomm cannot f
I should mention that I am using the autoconf packaged for meerkat (i.e.
version 2.67-2ubuntu1) to regenerate the configure script.
** Also affects: acct
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
***FIX INCLUDED***
This appears to actually be a result of the default accounting file path
being /var/log/account instead of /var/account. I looked at the source,
and it appears that the configure code for setting the default file
location is simply not working. The config check looking for the f
At the risk of being a me-tooer, I am experiencing this with the following card:
01:00.0 VGA compatible controller: nVidia Corporation G96 [Quadro FX 380] (rev1)
01:00.0 0300: 10de:0658 (rev a1)
In my case, this is happening on meerkat. I don't know if the 10.10
instalation was working correctly a
At the risk of being a me-tooer, I am experiencing this with the following card:
01:00.0 VGA compatible controller: nVidia Corporation G96 [Quadro FX 380] (rev1)
01:00.0 0300: 10de:0658 (rev a1)
In my case, this is happening on meerkat. I don't know if the 10.10
instalation was working correctly a
At the risk of being a me-tooer, I am experiencing this with the following card:
01:00.0 VGA compatible controller: nVidia Corporation G96 [Quadro FX 380] (rev1)
01:00.0 0300: 10de:0658 (rev a1)
In my case, this is happening on meerkat. I don't know if the 10.10
instalation was working correctly a
BTW, I used to get this same informational message when logging into KDE
after upgrading to the Beta of Lucid. I haven't seen that instance of
the message in a few days though.
--
freecad preferences indicates problem with Qt Jambi
https://bugs.launchpad.net/bugs/555001
You received this bug noti
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/43050188/Dependencies.txt
--
freecad preferences indicates problem with Qt Jambi
https://bugs.launchpad.net/bugs/555001
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubun
Public bug reported:
Binary package hint: freecad
When I click on Edit -> Preferences..., I get the following informational
message in a modal dialog box:
"Could not locate the java virtual machine.
Qt Jambi plugins have been disabled."
I don't understand why it can't find my JVM since I can j
1 - 100 of 108 matches
Mail list logo
