The patch that fixes this bug was merged upstream yesterday:
https://github.com/torvalds/linux/commit/e950267ab802c8558f1100eafd4087fd039ad634
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1433906
Please note that while the above "quirk based" patch by gmiscko does
make the Acer Integrated Camera work, it is an earlier attempt at the
fix which was not approved by the UVC maintainer. The patch that has
been signed off and sent towards upstream maintainers attempts to fix
the brokenness in a
Hi Joseph
The patch has landed in this repository:
https://git.linuxtv.org/media_tree.git/log/
While I have no experience with this process, I was speculating that
this entire branch will be pulled into mainline when the next merge
window opens. But like I said, I don't actually know what to
Update: The patch got a 3rd signed-off-by and is now queued for
inclusion upstream. (But if I understand the kernel process correctly,
that can only happen when 4.10 merge window opens?)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Hi
Thanks for providing the test kernel to people! I have also installed it
and successfully tested. (Even I don't always recompile my own patch
from source every time there's an upgrade.)
The patch status is that the uvcvideo maintainer has signed-off on it,
and forwarded it to linux-media
Progress is unfortunately slow. The work to be done is minimal, but
response time from the maintainer has been in months. I guess this is a
reflection of Linux being mostly a server OS, and the desktop side being
developed in people's free time.
I would have had higher hopes for Canonical
Patching and building your own kernel is indeed a bit non-trivial. Some
guides were written already earlier in this thread. Personally I've used
this process: https://wiki.ubuntu.com/Kernel/BuildYourOwnKernel
A good first step is to simply check out the right ubuntu kernel,
compile it and reboot,
Teq, can you clarify your above message a bit? The submitted patch works
and fixes the problem and has been confirmed by many. If you have
evidence to the contrary, please report the specific errors you see. If
you do, please also attach the output of the command "lsusb" to verify
your webcam is
Thanks Brad :-) Maybe a little encouragement was all I needed, because a
new patch was now sent to the mailing list:
https://sourceforge.net/p/linux-uvc/mailman/message/35123087/
Commentary: https://sourceforge.net/p/linux-uvc/mailman/message/35123103/
In short, Laurent (the module maintainer)
Hi
The update is that after receiving the latest review (which itself took
some time), it's taken quite long for me to context switch back to
implement the requested changes. I do have an editor open in front of me
right now, so hopefully it can happen in the next few days.
The review comments
Hi
Just wanted to ask Canonical guys: It's encouraging to see some activity
on this ticket, is there any chance this will actually get into Ubuntu
before next .04 release? (Or, if next release is an LTS, is there any
chance this will get in right after that?)
(Yeah, I'm lazy, I don't even
** Patch added:
"0001-uvcvideo-Acer-Integrated-Camera-5986-055a-add-UVC_QU.patch"
https://bugs.launchpad.net/ubuntu/+source/linux-lts-utopic/+bug/1433906/+attachment/4532782/+files/0001-uvcvideo-Acer-Integrated-Camera-5986-055a-add-UVC_QU.patch
--
You received this bug notification because
Hi
I've submitted a patch that fixes this issue. Maybe give it a few days
for comments, but would be great if Ubuntu could incorporate this patch
ahead of upstream, since a lot of us seem to be using Lenovo. (Thinkpad
used to be known as a brand that just worked with Linux, sad to see it's
no
Hi
I've been analyzing this and proposed some solutions. See
http://sourceforge.net/p/linux-uvc/mailman/message/34681976/
I don't know what the kernel maintainers want from a fix, but for those
of us who use (K)ubuntu on a Lenovo, I think it would make us very happy
to simply do my last
It seems when I just build from source and do make install, it works
fine:
hingo@mermaid:~/hacking/drizzle/builds/2012.01.30-src$ sbin/drizzled
InnoDB: The log sequence number in ibdata files does not match the log sequence
number in the ib_logfiles!
120124 9:58:10 InnoDB: Database was not
Ok, I see why it respawns: it doesn't actually exit cleanly. This is
what it looks like when you do shutdown from inside drizzled...
hingo@mermaid:~/hacking/drizzle/deb$ sudo /usr/sbin/drizzled --user=drizzle
InnoDB: The log sequence number in ibdata files does not match the log sequence
number
** Changed in: drizzle
Status: Invalid = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/920175
Title:
Drizzled cannot shutdown itself on ubuntu, upstart restarts it
To manage
So this was built from the 2012.01.30 release sources, using updated debian
packaging scripts.
TODO:
- verify that it also happens with plain make install
- (kind of unrelated) I'll upload the deb packaging stuff shortly. (Is it
called source deb?)
** Summary changed:
- Drizzled cannot
Well, it would be good to confirm whether this is the case currently
or not.
Hi
Finally had time to test this again.
I deleted my Wifi configuration from my laptop. The Waiting for network
connection... text doesn't come back anymore.
I also had one more laptop that wasn't yet updated to
Steve, what do you mean invalid? What do you mean with unreliable boot
sequence?
I have a laptop. I take it onto a business trip. I want to work on the
airplane. There is no internet connection within miles. That (K)Ubuntu
wants to wait for several minutes until it accepts the fact that there
is
FWIW, here's my
$ cat /etc/network/interfaces
auto lo
iface lo inet loopback
Note that:
- this is not from fresh install but the system was upgraded a few
times from previous Kubuntu versions, I don't know how much the file has
lived on since then.
- I'm actually not sure my system suffers
This bug was marked as a duplicate of #856810 but it is not. This bug is
about a laptop/desktop user having to wait at boot time. The other is
about system failing to start at all.
** This bug is no longer a duplicate of bug 856810
Boot hangs at Booting system without full network
Just want to confirm same symptoms and same workaround.
A couple of weeks ago dad's Kubuntu doesn't print anymore.
Recognize that cups isn't running.
Verify that it should be (ls /etc/rc*/*cups)
Diagnose some more, realise that runlevel returns unknown
Eventually find this bug
Downgrade to
23 matches
Mail list logo
