Public bug reported:
Binary package hint: kde-guidance
Crash of a python script after upgrade to 7.04
ProblemType: Crash
Architecture: i386
Date: Wed May 9 00:34:10 2007
DistroRelease: Ubuntu 7.04
ExecutablePath: /usr/share/python-support/kde-guidance/displayconfig-restore.py
InterpreterPath: /
** Attachment added: "CoreDump.gz"
http://librarian.launchpad.net/7586294/CoreDump.gz
** Attachment added: "Dependencies.txt"
http://librarian.launchpad.net/7586295/Dependencies.txt
** Attachment added: "Disassembly.txt"
http://librarian.launchpad.net/7586296/Disassembly.txt
** Attachm
the
cd?
Filippo
On Thu, Apr 22, 2010 at 17:23, Jeremy Foshee
wrote:
> Hi Filippo,
>
> This bug was reported a while ago and there hasn't been any activity in it
> recently. We were wondering if this is still an issue? Can you try with the
> latest development release of Ubuntu
** Tags removed: needs-upstream-testing
--
System freeze
https://bugs.launchpad.net/bugs/476979
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.com/mailman/li
I removed the
"need-upstream-testing" tag.
Let me know if you need from me some other testing.
Filippo
On Tue, Apr 27, 2010 at 17:44, Jeremy Foshee
wrote:
> Hi Filippo,
> I am asking that you test against the latest development release which
> is currently 10.04. As this is
Public bug reported:
Binary package hint: dmz-cursor-theme
Kubuntu 9.10, dmz-cursor-theme v.0.4.1
the files fd_double_arrow and bd_double_arrow (in both DMZ_White and DMZ_Black)
are switched.
To see the problem, open System Settings -> Keybord & Mouse -> Mouse -> Cursor
Theme
and select DMZ(Wh
Public bug reported:
Binary package hint: nautilus
After upgrade to karmic I'm not able to mount a veecam devices
(http://www.vee-cam.com/). It was working with 8.04, but now ehci_hcd
reset my device after few seconds.
I followed https://wiki.ubuntu.com/DebuggingRemovableDevices for this
bug rep
** Attachment added: "debugging report"
http://launchpadlibrarian.net/37103976/report.zip
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/37103977/Dependencies.txt
** Attachment added: "ProcMaps.txt"
http://launchpadlibrarian.net/37103978/ProcMaps.txt
** Attachmen
I understood that they need to deal with new codec inclusion, via GStreamer o
other libs,
and that writing code and manage a community is not a simple task.
Said that,
IMHO there are three big question with bluetooth and PulseAudio:
1. in these days we (probably most of us) are always on web con
I installed 5.10.6 and 5.10.7 in linux mint 20.1 (via "ubuntu mainline
kernel installer") and the issue remains: i'm trying to pair Huawei
bluetooth mouse to my matebook 13 AMD.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://b
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: filippo5817 F pulseaudio
/dev/snd/controlC0: filippo5817 F pulseaudio
CurrentDesktop: ubuntu:GNOME
Date: Fri Nov 3 10:07:17 2017
InstallationDate: Installed on 2017-09-17 (46 days ago
Dear joseph,
answer in your text.
bye Filippo
On Fri, Nov 3, 2017 at 6:15 PM, Joseph Salisbury <
joseph.salisb...@canonical.com> wrote:
> Did this issue start happening after an update/upgrade? Was there a
> prior kernel version where you were not having this particular problem
Public bug reported:
no idea
ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: postgres-xc 1.1-2ubuntu2
ProcVersionSignature: Ubuntu 3.13.0-95.142-generic 3.13.11-ckt39
Uname: Linux 3.13.0-95-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.21
AptOrdering:
postgres-xc: Purge
postgres-xc-cl
Public bug reported:
continuous errors while updatng to new kernel 3.13.0.48
ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: openafs-modules-dkms 1.6.7-1
ProcVersionSignature: Ubuntu 3.13.0-46.76-generic 3.13.11-ckt15
Uname: Linux 3.13.0-46-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.
Public bug reported:
When I try to install ubuntu (distro 14.04) from a usb bootloader, at
the end of the process,I got an error ''the installation of the package
'grub-efi-amd64-signed' is impossible.Without grub, the installed system
won't load''.
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Pa
Public bug reported:
don't know
ProblemType: Package
DistroRelease: Ubuntu 14.10
Package: nvidia-331 331.89-0ubuntu5
ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6
Uname: Linux 3.11.0-13-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.14.7-0ubuntu8
Architecture: amd64
DKMSK
Public bug reported:
I installed Ubuntu 20.04.3 on a Fujitsu Lifeboob U7510, and the touchpad
s not working: it is also not present in the file
/proc/bus/input/devices, and seems not to be detected by the system.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.11.0-27-generic
Public bug reported:
The system indicates this bug, I don't know what it means.
ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: grub-pc 2.04-1ubuntu26.13
ProcVersionSignature: Ubuntu 5.11.0-27.29~20.04.1-generic 5.11.22
Uname: Linux 5.11.0-27-generic x86_64
ApportVersion: 2.20.11-0ubunt
zoomy942, the relevant part of that thread (the one about uvcvideo driver)
suggests to install latest trunk from uvcvideo svn.
That's the latest version before uvcvideo was included in mainline kernel
(2.27) and probably the same (or almost the same) one included in Hardy.
If it fixes the issue
> It may be the case that Cheese makes correct use of the API, in a way most
> other applications don't use the API, and that uvcvideo breaks when used
> this way.
The API? which api are you talking about? the v4l2 api? we just do *one* ioctl,
it's a very basic and simple one and it's already bee
Francisco, as I said previously (not sure if it was here), I'm not upset
with you or with anyone at all. It's just that lately I hear so many
people complaining that cheese doesn't work, I even read some rather
"expert" guy in the forums saying to newbies things like "cheese is
completely broken in
I talked about this issue with the uvcvideo maintainer. It seems it is
strictly connected with gstreamer's v4l2src switch to libv4l2. Anyway he
came up with a patch that fixes it, or at least fixes mine. He will
commit it to his branch on linuxtv.org soon, I'll keep you updated.
--
cheese malfunc
zoomy942,
Sure I didn't post it here because I was waiting for him to commit it.
The changeset is: http://linuxtv.org/hg/~pinchartl/uvcvideo/rev/62c88b326ecd
Could any of you give it a test to see if it fixes your issue too?
You can get the source running hg clone
http://linuxtv.org/hg/~pinchartl
zoomy, see the big fat warning printed when you run make? svn repository
is deprecated. If you want to give some help you should really try the
mercurial repository I pointed you a couple of hours ago
(http://linuxtv.org/hg/~pinchartl/uvcvideo). Anyway notice that it
contains the whole v4l-dvb stac
Jose, no it doesn't work by following the wiki. The method you posted is under
the statement "Use this section if you are using an Ubuntu version prior to
Gusty 7.10. ", so that guide supposes that intrepid should have debug symbols.
Anyway I already rebuilt the library from source, debugged my i
*** This bug is a duplicate of bug 290506 ***
https://bugs.launchpad.net/bugs/290506
Marking this bug as a duplicate of bug 290506, I know at least two
people with the very same hardware that managed to fix the issue
installing Stefan Bader kernel package listed in that bug or manually
compili
Hi, I'm a cheese developer, I really believe this is a duplicate of bug 290506.
I didn't find though any information about your laptop, can you confirm that
your webcam uses uvcvideo driver? Could you attach here the output from lsusb
and dmesg?
--
[Regression] Cheese stops when I try to record
For what it's worth (I wrote the patch), I confirm the package in hardy-
proposed fixes the issue here.
--
GNOME Mastermind grid is shifted to the right with new cairo releases
https://bugs.launchpad.net/bugs/222580
You received this bug notification because you are a member of Ubuntu
Bugs, which
The ChangeLog says this bug has been fixed in 2.6.30 with commit:
commit a8aa401f38cfb5fa26e970b48e93fb851d68fe64
Author: Johannes Berg
Date: Sat Apr 18 11:00:39 2009 +0200
USB: pass mem_flags to dma_alloc_coherent
When I want to use my webcam, I get:
I don't believe the feature requested here will happen anytime soon. Photos are
saved directly from the same stream of the viewfinder, a frame is taken and
encoded into a jpeg file. To do what the OP suggested we will need to stop the
pipeline, close the device, reopen it with an higher resoluti
Known bug, fixed in 2.27.2
** Bug watch added: GNOME Bug Tracker #582240
http://bugzilla.gnome.org/show_bug.cgi?id=582240
** Also affects: cheese via
http://bugzilla.gnome.org/show_bug.cgi?id=582240
Importance: Unknown
Status: Unknown
** Changed in: cheese (Ubuntu)
Status:
Also backported in 2.26.2
--
Cheese should be dependend on gnome-icon-theme
https://bugs.launchpad.net/bugs/375917
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.ub
** Bug watch added: GNOME Bug Tracker #585761
http://bugzilla.gnome.org/show_bug.cgi?id=585761
** Also affects: cheese via
http://bugzilla.gnome.org/show_bug.cgi?id=585761
Importance: Unknown
Status: Unknown
--
Audio track becomes choppy & de-synchronized after 30 or so seconds o
Added a bug for this in the upstream tracker.
Please forward your bugs there if you want Cheese developers to notice it and
have a chance to get them fixed. I take a look here sometimes but it doesn't
happen really often.
--
Audio track becomes choppy & de-synchronized after 30 or so seconds of
Could you guys test the my last git commit? I'm quite confident it should fix
or at least reduce a lot a/v sync errors.
http://git.gnome.org/cgit/cheese/commit/?id=d25b64149249be6a1329880ae42d4accc0db06d3
--
Audio track becomes choppy & de-synchronized after 30 or so seconds of
recording.
https
Public bug reported:
fili...@b612:~$ lsb_release -rd
Description:Ubuntu 9.04
Release:9.04
fili...@b612:~$ aptitude show gnome-do
Package: gnome-do
State: installed
Automatically installed: no
Version: 0.8.1.3-0ubuntu2
search for a file, choose "open with..." and select emacs-gtk. Aft
Public bug reported:
fili...@b612:~$ lsb_release -rd
Description:Ubuntu 9.04
Release:9.04
fili...@b612:~$ aptitude show gnome-do
Package: gnome-do
State: installed
Automatically installed: no
Version: 0.8.1.3-0ubuntu2
fili...@b612:~$ aptitude show gnome-do-plugins
Package: gnome-do-p
Could you attach a "cheese -v" log?
Which driver does that webcam use? it seems it misreports the formats it
supports (as far as I can tell it advertises to support a continuous range of
resolutions, and that's quite unlikely, it should give a discrete list of
resolution/framerates)
--
cheese
reh4c, you have a different bug than this one. This is about cheese hanging on
start yours is about cheese hanging on video recording. It happens with almost
all netbooks because they are too much underpowered to do live theora encoding.
See http://bugzilla.gnome.org/show_bug.cgi?id=564957
** Bu
Cheese doesn't fail anything here. It is a known libv4l bug. Hans has
fixed it in a test development snapshot and it will definitely be fixed
in the next release. See
http://bugzilla.gnome.org/show_bug.cgi?id=571772
** Also affects: libv4l (Ubuntu)
Importance: Undecided
Status: New
** C
*** This bug is a duplicate of bug 345080 ***
https://bugs.launchpad.net/bugs/345080
** This bug is no longer a duplicate of bug 349255
Green webcam capture on isight
** This bug has been marked a duplicate of bug 345080
iSight camera images have green/purple tint
--
all-green image on
*** This bug is a duplicate of bug 345080 ***
https://bugs.launchpad.net/bugs/345080
** This bug has been marked a duplicate of bug 345080
iSight camera images have green/purple tint
--
Green webcam capture on isight
https://bugs.launchpad.net/bugs/349255
You received this bug notificatio
> Is it the same as bug #349255 ?
Yes it is, marked as duplicate
--
iSight camera images have green/purple tint
https://bugs.launchpad.net/bugs/345080
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-b
same problem here.
***
fili...@b612:~$ nautilus
Initializing nautilus-open-terminal extension
** (nautilus:20691): WARNING **: Unable to add monitor: Not supported
Nautilus-Share-Message: Called
this bug also prevent opening wastebasket and to mount devices.
I've tried reinstalling gvfs but without success.
--
Opening "Places/Computer" nautilus crash with Segmentation fault
https://bugs.launchpad.net/bugs/395710
You received this bug notification because you are a member of Ubuntu
Bugs,
this is a bt for nautilus crashing after clicking Computer icon:
0xb8017430 in __kernel_vsyscall ()
(gdb) continue
Continuing.
[New Thread 0xb6d2ab90 (LWP 4850)]
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0xb6f92750 (LWP 4837)]
0xb78fa3d7 in g_str_hash () from /usr/
purging
*ubuntuone-client
*ubuntuone-client-gnome
*ubuntuone-ppa-beta
"fixes" this problem. We have to wait for ubuntuone-client to be
updated.
--
Opening "Places/Computer" nautilus crash with Segmentation fault
https://bugs.launchpad.net/bugs/395710
You received this bug notification because
fili...@b612:~$ apt-cache policy ubuntuone-client
ubuntuone-client:
Installed: 0.90.3+r63-0ubuntu1~ppa2~jaunty
Candidate: 0.90.3+r63-0ubuntu1~ppa2~jaunty
Version table:
*** 0.90.3+r63-0ubuntu1~ppa2~jaunty 0
500 http://ppa.launchpad.net jaunty/main Packages
100 /var/lib/dpkg/s
Hi Sebastien,
can you set:
* Status->confirmed
* Importance->high
* Assigned to-> anyone who can solve this issue
?
I've reported it at
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/395834 using
apport.
--
Opening "Places/Computer" nautilus crash with Segmentation fault
https://bu
Public bug reported:
After upgrading to Jaunty brightness settings are not remembered anymore when
rebooting or when disconnecting power cable.
During boot process brigthness changes multiple times:
- at BIOS screen brightness gets correctly restored to last used one
- when ubuntu starts loading
** Attachment added: "dmesg.log"
http://launchpadlibrarian.net/23109865/dmesg.log
--
Brightness changes multiple times during boot up and doesn't get back to the
last used one
https://bugs.launchpad.net/bugs/334206
You received this bug notification because you are a member of Ubuntu
Bugs, w
** Attachment added: "lspci-vnvn.log"
http://launchpadlibrarian.net/23109880/lspci-vnvn.log
--
Brightness changes multiple times during boot up and doesn't get back to the
last used one
https://bugs.launchpad.net/bugs/334206
You received this bug notification because you are a member of Ubun
** Attachment added: "uname-a.log"
http://launchpadlibrarian.net/23109887/uname-a.log
--
Brightness changes multiple times during boot up and doesn't get back to the
last used one
https://bugs.launchpad.net/bugs/334206
You received this bug notification because you are a member of Ubuntu
Bug
** Attachment added: "version.log"
http://launchpadlibrarian.net/23109893/version.log
** Summary changed:
- Brightness changes multiple times during boot up and gets back to the last
used one
+ Brightness changes multiple times during boot up and doesn't get back to the
last used one
--
B
Bryce, I think you're following a wrong path.. it's not a matter of single keys
not mapped correctly. It's the layout setting that gets forgotten after reboot.
Considering that dell-mini uses autologin I really believe this is a duplicate
of bug #196277
--
UNR - Italian Keyboard Configuration o
** Description changed:
After upgrading to Jaunty brightness settings are not remembered anymore when
rebooting or when disconnecting power cable.
During boot process brigthness changes multiple times:
- at BIOS screen brightness gets correctly restored to last used one
- when ubuntu star
I believe Ubuntu Hardy shipped with Dell Mini 9 is also affected by this bug
(it uses autologin), at least it is after latest upgrades.
As far as I can tell it worked fine before the upgrades so it could be fixed
reverting the change that introduced it, I don't know but maybe it would be
easier
Public bug reported:
$ lsb_release -rd
Description:Ubuntu 9.04
Release:9.04
printer auto configuration misses canon pixma mp 210 (it said it can't find any
suitable driver) but configuring it manually and using the canon pixma mp 220
(in jaunty) makes the printer fully operational.
Confirming the issue for gnome-power-manager: it sets brightness level to 100
as soon as it starts.
There is still something else that does the same while ubuntu is loading but
still I don't know which package.
pi...@tux:~$ killall gnome-power-manager
pi...@tux:~$ cat /proc/acpi/video/VGA/LCD/br
Another thing, not sure if it is ok to ask it on a launchpad bug.. could
anybody verify if the issue still stands with mainline drivers from the
v4l-dvb mercurial tree so that we can understand if it is an ubuntu
specific regression or an upstream one?
--
cheese doesn't work with my webcam (Phili
@Valerio,
I don't really think this is a gstreamer bug since both skype and xawtv users
reported the very same issue (see duplicates of this bug).
I don't know why it still works with vlc (someone said it works with camorama
too but I think it's using v4l1 api) but it's likely that this issue com
Andres, as I said in bugzilla I was wrong about libv4l.. I don't know
what made me believe that patch fixed the issue (it was late and I was
really tired) but, unfortunately, it doesn't.
Also please forgive me if I appeared rude with you, I didn't want it,
it's just that lately too much people say
I don't think the point here is if it works good with gstreamer+v4lsrc.
As Baptiste said in the upstream bug report the webcam works with right
colors using v4lsrc (v4l1) from gstreamer properties but it's tinted
green using it as a v4l2 device. So the bug is the v4l2 green tint,
forcing it to use
*** This bug is a duplicate of bug 282473 ***
https://bugs.launchpad.net/bugs/282473
Andres please notice that bug is not really linked to upstream.. it is
linked to a cheese bugzilla bug that I didn't close yet as NOTGNOME just
because I want it to still stay there as a reference for other
re
@Andres, no this bug really is a pwc specific one and it's not cheese related
at all.
Bug #290506 is uvcvideo specific and maybe it has something to do with cheese
but I'm still not sure.
--
cheese doesn't work with my webcam (Philips PCVC740K ToUcam Pro)
https://bugs.launchpad.net/bugs/282473
Andres, cheese asking hal for v4l capable devices has absolutely no
relation with this bug. Please don't blame us if you don't know what you
are talking about.
We just use gstreamer to access the webcam device.
The only thing we do on our own (directly accessing the device) is a
VIDIOC_QUERYCAP i
iSmith, do you mean the first gst-launch command? what about the second one?
does it lock you webcam?
Thanks
--
cheese doesn't show v4l2 video output and disables output on gstreamer-based
apps ran afterwards
https://bugs.launchpad.net/bugs/290506
You received this bug notification because you
Fabian, probably your webcam doesn't support 1280x1024
Could you please check if gst-launch v4l2src ! xvimagesink locks the webcam?
--
cheese doesn't show v4l2 video output and disables output on gstreamer-based
apps ran afterwards
https://bugs.launchpad.net/bugs/290506
You received this bug not
dominko, that's a known issue with your webcam driver please take a look at
http://bugzilla.gnome.org/show_bug.cgi?id=531835 and
http://bugs.mediati.org/r5u870/issue17
So, am I the only one able to reproduce it both with cheese and plain
gstreamer?
--
cheese doesn't show v4l2 video output and d
Could any of you check if the issue can be reproduced with pre 2.27 kernels
too? The last one from 2.26 series should be fine.
I want to be 100% sure this thing has nothing to do with cheese (and possibly
with gstreamer too) and it is a uvcvideo issue only.
--
cheese doesn't show v4l2 video out
o mentioned
> above. Otherwise, we'll close this as expired.
Indeed, I might be able to do some tests this weekend.
thanks,
filippo
--
Filippo Giunchedi - http://esaurito.net
PGP key: 0x6B79D401
random quote follows:
Everyone is entitled to his own opinion, but not his own facts.
-- Daniel Patrick
On Intrepid, I'm now using radeon driver and Virtualdesktop option in xorg.conf.
A big Virtualdesktop is more useful for me as I can move windows between
monitors.
I briefly tested fglrx and it doesn't log errors.
Log noise in Hardy disappeared after an update (see my previous
comment).
I'd clos
Public bug reported:
Not too much to say.. I have a segfault on a libselinux function but I'm
not able to debug it since there is no debug package. There was one in
hard (libselinux1-dbg) why it has been removed?
** Affects: libselinux (Ubuntu)
Importance: Undecided
Status: New
--
First, that guide doesn't talk about intrepid.
Second, there is no libselinux-dbg package in intrepid repos and no
libselinux-dbgsym package in intrepid ddebs repository.
Am I missing anything? As far as I can tell the debug package has been removed
in intrepid while there was one in hardy.. corr
Still I cannot understand why this patch is not being considered.. I
think it's ok, is there any reason why it cannot be commited in Hardy?
it's been 3 months since this bug is open and noone complained.
--
GNOME Mastermind grid is shifted to the right with new cairo releases
https://bugs.launchp
I confirm that this issue has nothing to do with libavg, I'm experiencing it
with gst-inspect too.
The sigsegv happens in fini_contex_translations function (setrans_client.c)
because it free a couple of uninitialized contexts.
Mike's patch doesn't seem to solve the issue here (current intrepid) t
Bug confirmed, cryptkeeper in indipendent from each file manager. It
use an own file manager
--
cryptkeeper shouldn't depend on nautilus
https://bugs.launchpad.net/bugs/251666
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-b
hi you can use this workaround sudo cp /usr/share/jwm/xsessions/Jwm.desktop
/usr/share/xsessions/
at reboot you have jwm in login session
--
jwm does not appear in sessions. Hardy beta.
https://bugs.launchpad.net/bugs/205431
You received this bug notification because you are a member of Ubuntu
t do? I'm running unstable. Of course I can test
xserver-xorg-video-intel (2:2.3.2-2ubuntu3) if needed.
filippo
--
Filippo Giunchedi - http://esaurito.net
PGP key: 0x6B79D401
random quote follows:
Age is not a particularly interesting subject. Anyone can get old. All
you have to do is li
Public bug reported:
Binary package hint: rhythmbox
Richt click on a song -> move to trash -> nothing happens... Only a red
icon like "denied access" in the column in the left of the song name, in
a column.
Than, when you click on the same song, the icon disappears and the song
is still in the l
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/16525291/Dependencies.txt
** Attachment added: "ProcMaps.txt"
http://launchpadlibrarian.net/16525292/ProcMaps.txt
** Attachment added: "ProcStatus.txt"
http://launchpadlibrarian.net/16525293/ProcStatus.txt
--
moving
I have tested with Hardy Heron, kde3.5, ( kernel 2.6.24-20-generic )
wich, without libsrvg2-common, cellwriter run in silenty mode, without
traybar icon.
--
cellwriter package should depend on librsvg2-common
https://bugs.launchpad.net/bugs/254604
You received this bug notification because you a
dear Chris,
out of rhythmbox everything goes well, i can move whatever song i want to
trash, but i can't from inside of rhythmbox...
Here you are the result of the command "mount -l":
/dev/sda3 on / type ext3 (rw,relatime,errors=remount-ro) []
proc on /proc type proc (rw,noexec,nosuid,nodev)
/s
I'm trying to delete songs that are on NTFS filesystem directly from
Rhythbox.
And here you are the last line of the ".xsession-errors" file after that
i try to move to trash a ntfs file from rhythbox...
(rhythmbox:6569): Rhythmbox-WARNING **: Could not open device
/dev/radio0
As you can, why d
*** This bug is a duplicate of bug 192629 ***
https://bugs.launchpad.net/bugs/192629
Sorry Chris. Now i'm laughing for this stupidity and i'm sorry because i
didn't want you to lose time. Thanks by the way.
This is the price to pay when someone doesn't know very well linux
systems.
Bye!
--
eed
it will at least make uvcvideo webcams work again with cheese).
Just as a reference consider taking a look at
http://freshmeat.net/redir/libv4l/76006/url_changelog/marc.info where the
author strongly suggests an upgrade ("every one is urged to
upgrade to 0.5.7 asap!")
Thank you,
Fili
really think it's so much code, just
normal bugfixes that we considered unharmful enough for 2.24 series. (By the
way, I thought GNOME 2.24.x series had some kind of fast path with SRUs, isn't
it?)
Thank you for looking at this,
Filippo
--
SRU for cheese 2.24.2
https://bugs.launchpad.net
I confirm the bug, it seems to happen with metacity themes that change their
color with the gtk color scheme. I can see it with almost every theme but
Ubuntu ones (probably ubuntu metacity has hardcoded color). Almost every other
window border is just pink after the upgrades.
I'm using stock ubu
Same problem here on a Dell Mini 9 after latest upgrades. I can switch
keyboard layout from preferences and set it to Italian, it works but
after reboot I get again US mapped keys.
Also note that with latest upgrades Super key is not binded to F11
anymore so magic fullscreen doesn't work.
** Also
On Mon, Feb 2, 2009 at 11:08 PM, Chris Gregan wrote:
> Not a bug concerning the Shipping Dell mini OS
Why not? It uses Ubuntu Hardy and this bug affects Ubuntu Hardy. You
ship custom packages for Dell Mini which also include this bug.
Either disable the upgrades or fix it in your custom packages.
On Thu, Jan 8, 2009 at 10:00 PM, Tormod Volden wrote:
> Tested the version 2.24.2-0ubuntu0+intrepid1 (with my Genius Eye) and
> everything worked fine, no regressions AFAICS. I can not comment on any
> bug fixes though. Where is that debug information supposed to show up?
It should come up runnin
On Thu, Jan 8, 2009 at 11:32 PM, Tormod Volden wrote:
> I tried -v and --verbose with no luck. These options are not mentioned
> in the man page, but that would be another bug.
As far as I remember we don't ship any man page, probably it comes
from a debian or ubuntu patch.
Anyway, do you mean ch
On Tue, Dec 23, 2008 at 10:35 PM, WillSmith wrote:
> I did not run the commands found in that ubuntuforums post. I don't have
> interest to inject potentially unstable modules into my kernel.
> >From what I have seen the update should just be of the kernel and v4l2
> packages.
> Do we know when t
@everybody:
Please also note that libv4l 0.5.6 has got a nasty bug that prevents uvcvideo
webcams to correctly work.
So the kernel alone is not enough to make Cheese work again.
The new libv4l 0.5.7, with the fix, already went through a SRU and should enter
intrepid-proposed soon (if it didn't y
Currently the upgrade fails with:
Preparing to replace nvidia-glx-180-dev 180.35-0ubuntu1 (using
.../nvidia-glx-180-dev_180.37-0ubuntu1_i386.deb) ...
dpkg-divert: rename involves overwriting `/usr/lib/libGL.so' with
different file `/usr/lib/nvidia/libGL.so.xlibmesa', not allowed
dpkg: error pro
Thanks Alberto, you're right, I don't know dpkg enought to distinguish
the two errors :)
--
dpkg-divert mismatch when upgrading or reinstalling nvidia-glx-180
https://bugs.launchpad.net/bugs/333550
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Ok, new cheese package with the fix is out, could you guys confirm that
this bug is fixed?
--
on photo capture cheese blanks the screen until logout
https://bugs.launchpad.net/bugs/297890
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
-
Public bug reported:
Binary package hint: cheese
>From the debdiff:
+ifeq ($(DEB_BUILD_ARCH),lpia)
+ DEB_CONFIGURE_EXTRA_FLAGS += --enable-hildon
+endif
As far as I can tell I'm not supposed to run lpia packages on a
hildonized desktop, that's the reason there is a separate cheese-hildon
p
Subscribing Michael who worked on splitting hildon stuff in a separate
package.
--
lpia package built with hildon support while there is a separate hildon package
https://bugs.launchpad.net/bugs/345772
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
I'm currently discussing with gnome accessibility experts to try to nail down
this issue. It is definetely confirmed that it only happens if a11y is enabled.
There is probably some locking issue with gdk threads.
Anyway, why the upstream tracker is set to Incomplete? the bug is marked as NEW
in
1 - 100 of 315 matches
Mail list logo