Public bug reported:
I own a Kodak ZD710 camera, which is a standard USB PTP camera. In
Gutsy, my camera worked out-of-box with libgphoto2, in GNOME and in
KDE's digiKam.
In Hardy, I am unable to access the camera as a normal user. When opening the
camera, digiKam reports:
Failed to connect to t
** Attachment added: "kern.log"
http://launchpadlibrarian.net/12756194/kern.log
--
Permissions error with Kodak ZD710 prevents opening of camera
https://bugs.launchpad.net/bugs/203402
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
-
I plugged in the camera to the USB port.
** Attachment added: "hal.log"
http://launchpadlibrarian.net/12756199/hal.log
--
Permissions error with Kodak ZD710 prevents opening of camera
https://bugs.launchpad.net/bugs/203402
You received this bug notification because you are a member of Ubuntu
output of lshal after the camera was plugged in
** Attachment added: "lshal.txt"
http://launchpadlibrarian.net/12756201/lshal.txt
--
Permissions error with Kodak ZD710 prevents opening of camera
https://bugs.launchpad.net/bugs/203402
You received this bug notification because you are a member
Don't know if this is of any help, but noticed that the camera appears
to be detected correctly by that rule:
udi = '/org/freedesktop/Hal/devices/usb_device_40a_5c0_KCXHG73305836_if0'
access_control.file = '/dev/bus/usb/004/002' (string)
access_control.type = 'camera' (string)
camera.acces
Ah, that would explain it.
As far as I'm aware, Ubuntu prefers to manage as few patches as possible
against the linux kernel tree, even if it means waiting for drivers to
go from patches to the vanilla kernel to packages.
Although it's somewhat surprising when tools' package versions don't
match
@vectart:
1. Please don't swear.
2. As far as I am aware, the bamboo fun has never worked "out of the box" on
either Gutsy or Hardy. It is possible to get them to work by manually compiling
and installing the driver. However, I am surprised this is necessary for this
hardware considering the dri
Just for reference when hardy+1 does open, you may wish to look at the
dependencies for e.g. the wordpress package in universe, which depends
on the following (among others):
- apache2 | httpd
(can be satisfied by, among others, lighttpd and one of the various apache2
mpms)
- libapache2-mod-php5
Okay, thank you for taking it into consideration.
--
Lighttpd support
https://bugs.launchpad.net/bugs/190461
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.c
I suspect since feisty and gutsy use different kernels, *if* this is
still a problem with newer versions of *buntu, it should be re-assigned
to the newer kernel packages...
--
Kernel does not read DVDs, no automount
https://bugs.launchpad.net/bugs/37876
You received this bug notification because
Feisty seems to contain a lot of blueprints about making udev play
nicely with certain disk arrangements (i.e. LVM, EVMS). I'm wondering
whether if and how casper was modified when scripts for e.g. udev were
modified to run on the upstart (replacement init) model.
(According to https://blueprints.
Hmm... what about downloading the 2.6.13 patch, and applying it in
reverse before applying to 2.6.20 unionfs patch?
i.e.:
(under linux src dir)
zcat <2.6.13 patch> | patch -p1 -R
zcat <2.6.20 patch> | patch -p1
That might work better...
--
feisty 20070210/herd5 persistent mode doesn't work
http
If this user is still experiencing problems, might it be a problem with
the drive's firmware (e.g. requiring updating)? AFAIK, disc types are
identified by the drive itself and then reported to the OS.
--
cdrecord in Ubuntu Breezy does not seem to support ultra speed media
https://bugs.launchpad.
Just curious, but is there a difference between suspending a USB device
and turning it off entirely and turning it on later, and if so, what is
it? Maybe one could actually somehow shut off the devices which crash on
suspend and turn them back on when the PC comes back? Can we selectively
suspend U
The following seem somewhat relevant:
http://lkml.org/lkml/2006/9/14/252
http://lkml.org/lkml/2007/1/14/98
http://lkml.org/lkml/2007/1/15/92
Someone seems to have known about this even in January, but there
doesn't seem to be a good way of fixing this, apart from perhaps having
a separate kernel
Most problems are thought out at least once before people start curtly
responding "well it's an incompatibility with XYZ and we can't do
anything unless they fix XYZ and this is what we think is the best way
of fixing it" -- summing things up elegantly does take some work.
(Performing Google search
I no longer have access to the affected hardware, so I am no longer able
to test whether or not this is still an issue. If someone else who is
affected could take a look, that'd be appreciated.
--
[Dell Inc. Vostro 1520] suspend/resume failure [non-free: wl]
https://bugs.launchpad.net/bugs/442554
This machine was on loan from work at the time, but I no longer have
access to it to do any further testing. Does anyone else following this
report have this particular hardware?
--
WARNING: at /build/buildd/linux-2.6.31/mm/page_alloc.c:1751
__alloc_pages_slowpath+0x459/0x480()
https://bugs.laun
The work-around in
https://bugs.launchpad.net/ubuntu/+source/mountall/+bug/514012/comments/2
appears to works for me.
--
Upgrade fails while upgrading to Ubuntu 10.04 from Ubuntu 9.10 server
https://bugs.launchpad.net/bugs/533020
You received this bug notification because you are a member of Ubun
*** This bug is a duplicate of bug 533020 ***
https://bugs.launchpad.net/bugs/533020
** This bug has been marked a duplicate of bug 533020
Upgrade fails while upgrading to Ubuntu 10.04 from Ubuntu 9.10 server
--
cyclic dependency between mountall and libplymouth
https://bugs.launchpad.net
Public bug reported:
Tried to suspend and resume. No password dialog showed up in X, only a
black screen and a terminal.
Trying to log in at the console yielded the following kernel error:
EXT4-fs error (device dm-1): __ext4_get_inode_loc: unable to read inode
block - inode=131558, block=524398
** Attachment added: "AlsaDevices.txt"
http://launchpadlibrarian.net/32997081/AlsaDevices.txt
** Attachment added: "BootDmesg.txt"
http://launchpadlibrarian.net/32997082/BootDmesg.txt
** Attachment added: "Card0.Amixer.values.txt"
http://launchpadlibrarian.net/32997083/Card0.Amixer.valu
mich...@kiwi:~$ apt-cache policy empathy
empathy:
Installed: 2.27.5-0ubuntu1
Candidate: 2.27.5-0ubuntu1
Version table:
*** 2.27.5-0ubuntu1 0
500 http://kiwi karmic/main Packages
500 http://ca.archive.ubuntu.com karmic/main Packages
100 /var/lib/dpkg/status
mich...@kiw
Public bug reported:
Apport seems to keep thinking that this is a crash that needs reporting,
but I don't notice any issues when using Ubuntu.
Not sure of this is actually a problem with my kernel or if it is an
issue with apport.
ProblemType: KernelOops
Annotation: Your system might become unst
** Attachment added: "AlsaDevices.txt"
http://launchpadlibrarian.net/32524930/AlsaDevices.txt
** Attachment added: "BootDmesg.txt"
http://launchpadlibrarian.net/32524931/BootDmesg.txt
** Attachment added: "Card0.Amixer.values.txt"
http://launchpadlibrarian.net/32524932/Card0.Amixer.valu
I'm currently away from the machine in question which was exhibiting
this behavior, so I can't say whether that commit solves my issue at
this time.
--
[i865g][Karmic Alpha 3] X corruption and freeze when clicking "Other" on GDM
login screen
https://bugs.launchpad.net/bugs/407793
You received th
New bug was marked as a dupe of existing bug #551911. Remote watch
updated.
** Bug watch added: GNOME Bug Tracker #551911
http://bugzilla.gnome.org/show_bug.cgi?id=551911
** Changed in: empathy
Status: New => Unknown
** Changed in: empathy
Remote watch: GNOME Bug Tracker #593351 => GN
I confirm the problem is now fixed in utopic-proposed. The result is
below.
ubuntu@ip-10-0-0-30:~$ sudo apt-get install nsd/utopic-proposed
Reading package lists... Done
Building dependency tree
Reading state information... Done
Selected version '4.0.3-1ubuntu0.1' (Ubuntu:14.10/utopic-propo
According to bug 569543, the cause is because gwibber tries to parse
user data which is only sent to gwibber the first time the gwibber
application is authorized for a given facebook account. Is there anyone
affected by this bug who is a first-time user of gwibber?
Workaround that works for me:
-
101 - 129 of 129 matches
Mail list logo
