I grabbed the updated package from Steve's PPA (#19), installed it, made
sure intramfs were all properly updated (update-initramfs -u -k all) and
rebooted.
I confirm my laptop now boot properly (running Ubuntu 20.04).
--
You received this bug notification because you are a member of Ubuntu
Bugs,
*** This bug is a duplicate of bug 1882890 ***
https://bugs.launchpad.net/bugs/1882890
I just did that (following what you posted on bug 1882890), and I
confirm it now boot as it should.
(I'm going to cross post this on the other bug, in closed this one
closed as duplicate)
--
You received
*** This bug is a duplicate of bug 1882890 ***
https://bugs.launchpad.net/bugs/1882890
*in case this one is closed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1882914
Title:
Thinkpad T460S wo
Hi Steve,
I confirm:
SRBDS: Vulnerable: No microcode
microcode: sig=0x406e3, pf=0x80, revision=0xd6
microcode: Microcode Update Driver: v2.2.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1882914
Ti
Public bug reported:
This morning I installed the security update "3.20200609.0ubuntu0.20.04.0" of
intel microcode and then, after rebooting, my T460S laptop is stuck with the
"loading initial ramdisk" message.
Selecting an older kernel did not help.
What I had to do to recover is boot on a liv
Successfully tested on eoan.
I enabled the proposed repository, upgraded everything (so including pulseaudio
13.0-1ubuntu1.1) then rebooted.
The audio device is no longer switched to HDMI when the screen wake up after
standby or when login-out and in.
(note that the workaround from the descripti
@vanvugt: I booted the latest 20.04 daily (which does contain the new
pulseaudio package) and I confirm the behaviour is now back to "normal",
which is to say to the 19.04 (and older) behaviour.
So this is indeed fixed on Focal in my point of view.
--
You received this bug notification because
Note that Debian Stretch Backport is already up to date. So this is just
a matter of syncing version 2.5.2+dfsg-1~bpo9+1 from there.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1780278
Title:
ansi
The required libphp7.0-embed version (1:7.0+35ubuntu6.1) is available in
the "Proposed" repository.
The new uwsgi package should not have been pushed to standard repos
before the new libphp7.0-embed.
I see two options:
* Release a new uwsgi version with a lower dependency on libphp7.0-embed
* Mig
@Dmitry: Please check that python3-launchpadlib is installed on your
system.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/253119
Title:
PPA packages do not show a changelog in update-manager
To ma
I confirm the proposed fix works as expected.
** Tags removed: verification-needed
** Tags added: 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/1585121
Title:
awstats produces reg
Since OTA 13 this is even worse: now the webview of my webapp just crashes when
the audio playback starts.
Before there was no sound but it was possible to browse the website. Now there
is a white page with an error message and a refresh button.
As before, removing "--enable-media-hub-audio" fix
Public bug reported:
On my Nexus 4, when I open the mouse & touchpad panel the following
string is displayed:
"You need to use a Bluetooth mouse or touchpad with this display. Make
sure it is close to the device and its batteries are charged."
I'm not a native English speaker but this wording s
I confirm this issue with my "uFip" webapp.
Also I confirm this is a regression from the OTA 12 development cycle: I
flashed back my Nexus 4 to OTA 11 and it started working again.
Here are some logs that may be interesting:
[DD 2016-07-18 21:37:17.822452] [player_stub.cpp:189@operator()]
Playb
Thanks Colin, I proposed a merge request which implements your suggested
approach.
However I noticed python3-launchpadlib is not seeded in the default install (at
least on Ubuntu Xenial), so I assumed it would not be acceptable to pull this
library, along with its dependencies, everywhere just f
** Branch linked: lp:~malizor/update-manager/ppa-changelogs
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/253119
Title:
PPA packages do not show a changelog in update-manager
To manage notification
As explained here some years ago (and I confirm it is still valid as of
update-manager on Xenial), UM already looks for changelog published
alongside .deb packages. It's in the "UpdateManager/Core/MyCache.py"
file.
So, IMHO, the proper fix for this issue would be to make Launchpad/Soyuz
publish a
I confirm this bug is fixed on Xenial with adium-theme-ubuntu 0.3.4-0ubuntu1.1.
Many thanks!
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.
Public bug reported:
Had this while installing the "openjdk-9-jdk" package on the command line.
Running "sudo apt install" just after seems to have fixed it.
ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: openjdk-9-jdk (not installed)
ProcVersionSignature: Ubuntu 4.4.0-22.38-generic 4.
Thanks Andrew, your patch seems to work for me.
Maybe you should provide a branch with your patch and/or a debdiff?
I would be great if this long standing bug was finally fixed out of the box on
Ubuntu 16.04.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
@Alexandre: If you come by here again, I'm still interested by the way I
could inject JS in webapp-container. It would really help if you could
point me to a documentation or to an existing app source code :-)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
If it happens to be a feature, do you know of any way to inject javascript on a
page, eg. to remove the _blank targets in question?
I don't think webapp-container is able to do that, but perhaps there is a more
advanced container somewhere?
--
You received this bug notification because you are
Hmm, looking closer at it it seems all non-working links have the
'target="_blank"' attribute set.
So, is this a feature? Is there anyway to force these links to open in the
browser?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
ht
Public bug reported:
Hi,
I do not manage to confine my webapp on its site, the "--webappUrlPatterns"
just seems to be ignored.
I tested on Ubuntu 15.10 and on Mako (up-to-date rc-proposed).
Test case 1 (working):
Run "webapp-container --webappUrlPatterns=http://foo.org/*
http://www.google.com/
For some reason, subsequent DNS queries do not always bring the same
result here with the above configuration:
First queries after a reboot return what's expected:
nicolas@nicolas-desktop:~ 0 $ dig www.dnssec-failed.org
; <<>> DiG 9.9.5-11ubuntu1.1-Ubuntu <<>> www.dnssec-failed.org
;; global opt
On Wily, I edited /etc/dnsmasq.d/network-manager and added the following
lines:
# DNSSEC setup
dnssec
trust-anchor=.,19036,8,2,49AAC11D7B6F6446702E54A1607371607A1A41855200FD2CE1CDDE32F24E8FB5
dnssec-check-unsigned
I then restarted network-manager and tried to connect to
http://www.dnssec-failed.
@Stephen: I had the same problem after today's upgrade.
Activating the proposed repository and upgrading lxc to version
1.0.7-0ubuntu0.9 fixed the issue for me.
See comment #11 for details.
But it's a shame this proposed fix was not released to everyone before
the new kernel.
** Tags removed: v
Here is the full dmesg when I boot on the faulty kernel.
** Description changed:
- Similar to #1503568 and #1503754, but on Vivid.
+ Similar to LP: #1503568 and LP: #1503754, but on Vivid.
After rebooting on the freshly installed 3.19.0-31-generic kernel, I'm
able to login on lightdm and s
Public bug reported:
Similar to LP: #1503568 and LP: #1503754, but on Vivid.
After rebooting on the freshly installed 3.19.0-31-generic kernel, I'm
able to login on lightdm and see the desktop, but I have no network and
I'm not able to poweroff/reboot/logout via the UI or via the terminal
(the co
Hmm, in fact not only the "--interaction" argument is missing.
This is not a serious patch, but the issue can be worked-around by
adding the following lines after line 90 in /usr/lib/python3/dist-
packages/sessioninstaller/gstinstaller.py:
parser.add_option("", "--interaction")
parser.add_option(
Adding sessioninstaller, as it provides gst-install as the default
gstreamer-codec-install alternative.
It does not support the --interaction option and therefore conflict with the
current gst-plugins-base in Wily.
I don't know which one of them should be fixed, so I guess my investigation
stop
Switched to gst-plugins-base, as the unknown parameter is set there:
gst-libs/gst/pbutils/install-plugins.c:g_ptr_array_add (arr,
g_strdup_printf ("--interaction=%s",
Now, I don't know if this parameter is supposed to do and if it should
really be supported.
** Also affects: gst-plugins-base
Public bug reported:
Attempting to play a mp3 file with Totem on the latest Wily daily build
(from the USB stick).
Totem opens but no playback start.
On the terminal I got this:
** Message: Missing plugin: gstreamer|1.0|totem|MPEG-1 Layer 3 (MP3)
decoder|decoder-audio/mpeg, mpegversion=(int)1,
I agree with you all and don't wanted to be mean with Alberto or whoever
else.
I really don't care of who is guilty (if there is ever such a "who"),
but what concerns me is that from the outside there have been no sign
from Canonical, the kernel team or whatever to at least acknowledge that
what h
I don't understand why everyone thanks Canonical here.
I mean, they messed up the SRU kernel process and broke a big number of stable
desktops in the wild (including some LTS users).
An now everyone is saying everything is great &all now that an update was
pushed?
But did you think of those casu
Well, the new FGLRX is only in proposed, so most users are still affected. The
only sane option in my point of view would be to release a new kernel without
the patch that broke things originally.
Don't forget that the fix here does nothing for people that installed FGLRX
directly from the AMD w
@Brad: Bug 1479913 (stated in comment #1 and in the previous bug report
of this proposed kernel)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1483630
Title:
linux: 3.19.0-26.28 -proposed tracker
T
Kernel 3.19.0-26.28 was pushed as a security update to all Ubuntu users today
(it is no longer in the, disabled by default, "proposed" repository).
This means all FGLRX users on Vivid (and those that installed 14.04.2) will
lose their graphical environment as soon as they reboot.
The only worka
Congratulation, you just broke the graphical environment of all FGLRX users.
I don't know if there is the same problem on Trusty, but Vivid is definitely
KO. I have to select the former kernel in grub each time.
What is the point of having new kernels in "proposed" first if you ignore bug
reports
Will this new package also revert the patch that break the proprietary ATI
driver?
It is apparently because of 'PCI: Propagate the "ignore hotplug" setting to
parent'
See Bug 1479913, although I don't think it is reasonable to expect users
to update fglrx before installing this new kernel (and
This update break fglrx.
I opened bug 1479945 about 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/1479055
Title:
linux: 3.19.0-26.27 -proposed tracker
To manage notifications about this
Public bug reported:
This update broke fglrx here (and so my graphical environment).
I tested with the fglrx from standard repositories and with the latest driver
from the amd website. Same error in both cases.
If fails during the DKMS build:
Error! Bad return status for module build on kernel
I sent a mail to the ubuntu-translators mailing list about this, we will
see.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1478208
Title:
File size units are not localized
To manage notifications
In fact this is just that: GLib translations are not included in the
phone.
I simply copied "/usr/share/locale-langpack/fr/LC_MESSAGES/glib20.mo"
from my Ubuntu 15.04 desktop to the same location on the phone and,
after restarting the Settings app, all size units are properly
translated.
I see tw
** Description changed:
When updating a click package or the system image, the download progress
- is not properly internationalized.
+ is not properly internationalized. Same thing in the Storage view, all
+ units are displayed the English way.
After investigating, the following string:
Public bug reported:
When updating a click package or the system image, the download progress
is not properly internationalized.
After investigating, the following string:
http://bazaar.launchpad.net/~system-settings-touch/ubuntu-system-settings/trunk/view/head:/plugins/system-update/PageComponen
Successfully tested on both Trusty and Utopic.
** Tags removed: verification-needed
** Tags added: 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/1445829
Title:
No video playback p
And here is the same for Trusty.
** Patch added: "totem-plugin-arte_3.2.1-2ubuntu0.14.04.2.debdiff"
https://bugs.launchpad.net/ubuntu/+source/totem-plugin-arte/+bug/1445829/+attachment/4380779/+files/totem-plugin-arte_3.2.1-2ubuntu0.14.04.2.debdiff
--
You received this bug notification becau
@sponsors: Here is a debdiff for Utopic.
It only adds a 6 lines patch to make the plugin usable again.
** Patch added: "totem-plugin-arte_3.2.1-2ubuntu0.14.10.2.debdiff"
https://bugs.launchpad.net/ubuntu/+source/totem-plugin-arte/+bug/1445829/+attachment/4380778/+files/totem-plugin-arte_3.2.1-
** Description changed:
+ [Impact]
+ The current totem-plugin-arte package found in Utopic and Trusty is unusable.
+ Because of changes Arte made to it's Website, the plugin is unable to extract
any video URL. It is therefore useless.
+
+ Note that that Vivid can't be fixed. See LP: #1446775
+
** Description changed:
- Totem > 3.10 dropped support for "traditional" plugins like totem-plugin-arte.
+ Totem >= 3.12 dropped support for "traditional" plugins like
totem-plugin-arte.
The only way forward is to rewrite it as a Grilo plugin, which is far from
finished for now (and it won't b
@Sam: the PPA contains the same package as in the repo, except the version is
different.
Your system will automatically upgrade to the higher version available.
You don't need to worry about which version to use, just use one that works :-)
I'm going to provide patched version for inclusion into
** Description changed:
Totem > 3.10 dropped support for "traditional" plugins like totem-plugin-arte.
- The only way forward is to rewrite it as a Grilo plugin, which is far from
finished for now (and it won't be a Totem plugin only when it's done).
+ The only way forward is to rewrite it as a
atched version for inclusion into Trusty and
Utopic.
** Changed in: totem-plugin-arte (Ubuntu Trusty)
Status: New => In Progress
** Changed in: totem-plugin-arte (Ubuntu Utopic)
Status: New => In Progress
** Changed in: totem-plugin-arte (Ubuntu Trusty)
Assignee: (unassigned) =&g
Public bug reported:
Totem > 3.10 dropped support for "traditional" plugins like totem-plugin-arte.
The only way forward is to rewrite it as a Grilo plugin, which is far from
finished for now (and it won't be a Totem plugin only when it's done).
The current package in Vivid should FTBS and is ba
Thanks Sam.
Strangely enough, today the plugin is also broken for me: I got the same wrong
URL as you. I don't know why it worked yesterday for me and not for you.
Arte made some changes on the website and it broke the plugin.
I proposed a patch upstream and I updated my PPA with new packages ve
** Changed in: totem-plugin-arte (Ubuntu)
Assignee: (unassigned) => Nicolas Delvaux (malizor)
** Changed in: totem-plugin-arte (Ubuntu)
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Hi,
I am not able to reproduce your problem.
For me, the plugin works fine on both Ubuntu 14.04 and 14.10. I can browse the
video list and watch them.
Please post a screenshot of what you are seeing and give me what is
printed when you launch Totem via the command line.
Cheers,
Nicolas
** Cha
It is enabled in Vivid (and it works fine).
So, except if developers decide to remove the broadway support before the
release, this bug is now fixed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/9336
** Tags removed: verification-needed
** Tags added: 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/1368596
Title:
video URL extraction fails
To manage notifications about this bug
And here is one for Utopic.
This is the same as Trusty, except for a version bump (to ensure dist
upgrades are fine).
** Patch added: "totem-plugin-arte_3.2.1-2ubuntu1+14.10.debdiff"
https://bugs.launchpad.net/ubuntu/+source/totem-plugin-arte/+bug/1368596/+attachment/4265627/+files/totem-plug
-arte/+bug/1368596/+attachment/4265617/+files/totem-plugin-arte_3.2.1-2ubuntu1%2B14.04.debdiff
** Changed in: totem-plugin-arte (Ubuntu Trusty)
Status: New => In Progress
** Changed in: totem-plugin-arte (Ubuntu Trusty)
Assignee: (unassigned) => Nicolas Delvaux (malizor)
** C
I submitted some more changes upstream, including a patch for the low quality
playback.
https://gitorious.org/totem-plugin-arte/mainline/merge_requests/20
I'm waiting for a review.
As this particular patch is straight forward, I will go ahead and provide a
debdiff with just the minimum backporte
Public bug reported:
After flashing and completing the welcome/first-boot wizard, I have to
manually set the timezone in the settings.
AFAIK, most other phone OS directly ask the user to set it during their
welcome wizard.
** Affects: ubuntu-system-settings (Ubuntu)
Importance: Undecided
Public bug reported:
This seems a bit similar to LP #1333564, but this time the .pot is
apparently up to date in trunk...
For example, the "4 digits only" string from "wizard/qml/Pages/30
-passwd-type.qml" is marked as translatable and appears in the .pot,
however it is not translatable on Launch
** Summary changed:
- video URL Extraktionsfehler
+ video URL extraction fails
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1368596
Title:
video URL extraction fails
To manage notifications about
** Description changed:
+ [Impact]
+ The current totem-plugin-arte package found in Utopic, Trusty and Precise is
unusable.
+ Because of changes Arte made to it's Website, the plugin is unable to extract
any video URL. It is therefore useless.
+
+ [Test Case]
+ - Install the totem-plugin-arte p
Ok, so let's follow the rule and first try to fix the development
version (Vivid).
Here is the updated packaging archive that works against the latest upstream
release found here:
http://wenner.ch/files/public/mirror/totem-plugin-arte/totem-plugin-arte-3.2.2.tar.gz
Note to sponsors: the package
And here is a debdiff, just in case.
Just as a reminder, the current package in Vivid (but also Precise, Trusty and
Utopic...) is broken.
Broken as in "not usable". So there is no regression potential that I could
think of.
** Patch added: "totem-plugin-arte_3.2.2-0ubuntu1.debdiff"
https://
Here is a .dsc if you ever need it.
** Attachment added: "totem-plugin-arte_3.2.2-0ubuntu1.dsc"
https://bugs.launchpad.net/ubuntu/+source/totem-plugin-arte/+bug/1368596/+attachment/4256855/+files/totem-plugin-arte_3.2.2-0ubuntu1.dsc
--
You received this bug notification because you are a mem
Hi,
I advise you to use my PPA: https://launchpad.net/~malizor/+archive/ubuntu/ppa
It has the latest upstream version of totem-plugin-arte.
Getting a fixed version uploaded in official repo is time consuming and very
frustrating.
For example I still did not managed to get a fixed totem-plugin-ar
Thank you for your bug report.
I proposed a patch upstream[1], if it is accepted I will push for an
update in Ubuntu.
[1] https://gitorious.org/totem-plugin-arte/mainline/merge_requests/19
** Changed in: totem-plugin-arte (Ubuntu)
Assignee: (unassigned) => Nicolas Delvaux (mali
Just installed and tested: it works.
Thank you.
** Tags removed: verification-needed
** Tags added: 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/1354367
Title:
Imagination tries
This is already fixed in Debian and Utopic with version 3.0-5 (Trusty
has 3.0-3).
This should be suitable for a SRU, no?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1354367
Title:
Imagination try
Public bug reported:
Tried on Ubuntu 14.04.
All exports fail with "cannot launch 'ffmpeg', (no such file or directory)"
I workarounded it by installing libav-tools and then:
sudo ln -s /usr/bin/avconf /usr/bin/ffmpeg
** Affects: imagination (Ubuntu)
Importance: Undecided
Status: Ne
I got this same issue while upgrading from Precise to Trusty.
I had to remove the same lines as #15.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1017031
Title:
dpkg: error: duplicate file trigger
I upgraded to empathy 3.12 via the following PPA and, for now, I don't
encounter this bug anymore.
https://launchpad.net/~gnome3-team/+archive/ubuntu/gnome3-staging
I just added the PPA to my system, "sudo apt-get update && sudo apt-get
install empathy" and then I removed the PPA because I didn't
Public bug reported:
I tried to rebuild the current trusty package as is in pbuilder and it
failed.
Steps to reproduce:
- pbuilder-dist trusty create/update
- dget
https://launchpad.net/ubuntu/trusty/+source/gtk+3.0/3.10.7-0ubuntu2/+files/gtk+3.0_3.10.7-0ubuntu2.dsc
- pbuilder-dist trusty build
Same problem on Saucy (3.8.4-0ubuntu1)
It works on Debian Sid and with the version found in the gnome3-staging
PPA.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1129948
Title:
evolution-ews cant c
Note that this is only fixed on Saucy for now.
I'm trying to get it fixed on Debian Stable and Ubuntu Precise.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1212824
Title:
changed URL; no videos wat
[1] https://launchpad.net/~malizor/+archive/ppa
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1233307
Title:
Sync totem-plugin-arte 3.2.1-1 (universe) from Debian unstable (main)
To manage notifica
The current package in Saucy FTBS and is unusable (because of changes in
Totem 3.8 API and on the Arte website), so this sync is really needed.
The fixes included in this package are in my PPA[1] and were tested by
some users, so I'm confident on the reliability of this new version.
Sorry for be
unstable
* Depend on the right version of dpkg-dev
* Bump Debian Policy to 3.9.4, no change needed
* Build against valac-0.20, closes: #707441, #709702
-- Nicolas Delvaux Sun, 22 Sep 2013
20:24:55 +0200
** Affects: totem-plugin-arte (Ubuntu)
Importance: Undecided
Status: New
** Bug watch removed: Debian Bug tracker #722432
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=722432
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1211024
Title:
fails to build with totem 3.8
This bug was fixed upstream and I'm currently waiting for a mentor to
upload the new package into Debian before asking for a sync in Ubuntu.
If a DD is around and wants to help, the RFS is here:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=722432
In the mean time users, you can use my PPA:
ht
Hi Matthias,
This bug was fixed upstream and I'm currently waiting for a mentor to
upload the new package into Debian before porting the fix to Ubuntu.
In the mean time, you can use my PPA:
https://launchpad.net/~malizor/+archive/ppa
Cheers,
Nicolas
--
You received this bug notification becaus
** Changed in: linux (Ubuntu)
Status: Incomplete => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1214059
Title:
Wifi and bluetooth disabled at boot and hard to re-enable
To man
Public bug reported:
On an up-to-date Saucy, I'm no longer able to "edge scroll".
There is a "Two fingers scroll" box in the Mouse & Touchpad panel. It is
checked by default but it is also grayed out (since the hardware does
not support multitouch), so I can't disable it.
On Raring, the box is s
Hi Alex,
I'm afraid I don't have access to this laptop anymore, so I can't test your
patch.
Hopefully someone from the CC list may be able to help?
Thanks anyway.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpa
Hi Alex,
I'm afraid I don't have access to this laptop anymore, so I can't test your
patch.
Hopefully someone from the CC list may be able to help?
Thanks anyway.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpa
Christopher M. Penalve, here is a quote of this very link:
Fix Committed:
[...]
Upstream bug task: the fix is in CVS/SVN/bzr or committed to some place
Which is actually the case since this is fixed upstream.
** Changed in: linux (Ubuntu)
Status: Confirmed => Fix Committed
--
You r
Christopher M. Penalve, in my last comment I explained that this bug was
already fixed upstream (the faulty commit was reverted).
So it will be "fix-released" in the next RC.
** Changed in: linux (Ubuntu)
Status: Confirmed => Fix Committed
--
You received this bug notification because yo
Ok, after a lot of time git bisect tell me that the bad commit is
a53ee0a308b16e392e0219c585b10f329345766b.
It turns out this commit was reverted yesterday in
e2982a04ede454b23ea2f5af11ba4d77d8a70155.
My problem is indeed gone in the HEAD kernel.
I guess it's a good news but I'm still a bit disa
3.11.0-* (starting from 3.11.0-0) -> not ok, see bug description
3.10.0-* -> ok but wifi is *sometime* turned off at boot (I have to check
"Enable Wifi network" in NM)
In this case I see a "RF_KILL bit toggled to disable radio" in dmesg with no
visible error.
The fact that this is random is quit
Yes, it worked fine before Saucy.
For example, this laptop is dual-booting with Ubuntu 12.04 (3.2 kernel I think)
and I don't have this problem with it.
Before Saucy I was testing Raring and it worked fine (so 3.8 kernel).
Is there an easy way to install older kernels on Saucy so that we can find
I did the Bios upgrade but it changed nothing. I still get the same
behaviour as the one I described above.
~$ sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date
68PDV Ver. F.20
12/08/2011
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
** Tags removed: bi
Tested with the 09/18 kernel, same problem.
Perhaps there is some relation with Network Manager somewhere, because,
among other things (see above), I always have to disable/enable the
network from the NM indicator before being able to connect...
** Tags added: kernel-bug-exists-upstream
** Chang
*08/18 kernel
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1214059
Title:
Wifi and bluetooth disabled at boot and hard to re-enable
To manage notifications about this bug go to:
https://bugs.launc
Some interesting things in the WifiSyslog.txt file it seems (where you
can see my various attempt before finally connecting)
iwlwifi seems to often fails to load the firmware...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://
Public bug reported:
Network Manager says either "Device not ready" or "wireless is disabled by
hardware switch" (it depends).
Enabling Bluetooth in the control-center just enable it for like half a second
and then it's switched off again.
I have a combined hardware button for both Wifi and Blu
1 - 100 of 450 matches
Mail list logo
