Workaround:
Empathy uses gstreamer. You can change it in gstreamer-properties.
Or in gconf-editor /system/gstreamer/0.10/default/videosrc
From: v4l2src
To: v4l2src device="/dev/video1"
It would be nice to place some hint to this option.
--
Cannot choose which video device to use
https://bugs.l
Strange thing happened with me:
I was trying various parameters of the bttv module, if the autodetection is
wrong.
I noticed that after this. The autodetected paramters was the same, i used last
time.
And this was continoued until restart.
But the real strange thing:
After this i have taken out
Works for me in Jaunty and Karmic. With the notice that the original
"upper" panel must be the upper one and the "lower" must be the lower
else it flips back.
Did you tried it with different panel order? Or with fresh install?
--
The desktop panels flip after logout
https://bugs.launchpad.net/bu
Tested with just the Nvidia related packages and then with all packages were
updated.
Nothing happened.
Some other ideas?
--
[JauntyKdetv does not see/show my tv card (regression)
https://bugs.launchpad.net/bugs/325874
You received this bug notification because you are a member of Ubuntu
Bugs,
*** This bug is a duplicate of bug 146206 ***
https://bugs.launchpad.net/bugs/146206
** This bug has been marked a duplicate of bug 146206
files are copied to a local directory before being extracted
--
file-roller puts temporary files in the home dir instead of /tmp
https://bugs.launchpa
In addition to my last post:
After x restart and re-login kdetv sees the card only until reboot. :(
It's must be some deeper issue.
Does anyone have a clue?
@ O.S. : The bug is not in the packages listed above. I bet none of the experts
can reproduce or investigate the bug. It's enough not to c
There is some progress finding the source of the problem:
After a lot test I've got interesting results:
I did minimal installs (from server CD) and then installed the required
packages...
On a Jaunty base system installed every other package from Intrepid repos. ->
Kdetv not see the card.
On a
It's not the Nvidia driver's problem.
I tested it with the ver. 173 both on Intrepid and Jaunty: On Intrepid kdetv
worked on Jaunty not.
It's easy to blame the closed source driver...
--
[JauntyKdetv does not see/show my tv card (regression)
https://bugs.launchpad.net/bugs/325874
You received t
I booted Intrepid livecd installed kdetv it saw the TV card.
I booted Jaunty livecd installed kdetv it didn't saw the TV card.
The stderr-s are in the attachment.
The only difference is a lot of libzvbi line.
libzvbi0 package switched version from 0.2.30 to 0.2.31 between the two
releases.
Ins
Tested with nouveau instead of nvidia. -> Same result.
Rebuilt with apt-build. -> Same result.
Any other ideas?
--
[JauntyKdetv does not see/show my tv card (regression)
https://bugs.launchpad.net/bugs/325874
You received this bug notification because you are a member of Ubuntu
Bugs, which is su
In the first post Tomasz said "[...]are working properly in other analog tv
apps" so it's not a question that other apps work.
In the second post Tomas states "I've checked that intrepid kdetv packages is
just the same package as in jaunty". I confirm that.
The question is:
Is the bug in kdetv
I used intrepid with 2.6.28 (from jaunty beta) and kdetv worked fine.
I made some investigation and found that x.org must be responsible:
I added xorg.conf the following:
Load "v4l"
Restarted x.org. Then in kdetv appeared the station list which I
imported before from the wo
Unicode support exits only from 0.22.
Currently 0.19 is the newest from repos. (Still in Jaunty.)
Workaround:
Install the following packages from Debian SID:
obexftp
libusb-0.1-4
libbluetooth2
libopenobex1
libmulticobex1
libobexftp0
It's working in Jaunty. Please include the new version in repo
I did some further research:
I installed linux-image2.6.28-4-generic (from jaunty)
rebooted and the irda worked.
I think it's can be done with older(hardy's) kernels too.
If the bug is in the kernel then the older kernel will do it.
--
frezees trying to connect 6610i via sigmatel stir4200 irda
"I'm not sure, but in hardy it seemed to work faster ( I'm sure i didn't
anything like changing max baud rate)"
Could you test it both in hardy and jaunty alpha?
gmobilemedia and irda-utils packages are the same in hardy and intrepid
(and in jaunty till now). I can't imagine that they have broken
Are you sure its no an irda-utils, kernel, stb bug?
Have you tried it in jaunty alpha?
I have the same adapter. Worked in hardy AND works in jaunty alpha but
not in intrepid.
Did you tried to recive a file with ircp?
1) plug in the device
2) irattach irda0 -s (or sudo ifconfig irda0 up)
3) irc
It works with Jaunty alpha updated till now. (gnome 2.25.x) But will it
be fixed in Intrepid / Hardy? (The original bug is about Hardy.)
--
[hardy] amsn does not "blink" / "flash" on new messages with metacity on hardy
https://bugs.launchpad.net/bugs/220555
You received this bug notification beca
** Attachment added: "After logout"
http://launchpadlibrarian.net/20013406/after.png
--
The desktop panels flip after logout
https://bugs.launchpad.net/bugs/26921
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs mailing
Almost the same problem exists in Intrepid: Two panel stacked at one
side(Not the edge) of the screen are flipping their position
Drag the Top panel under the Bottom one.
Logout and login again. Then the panels are flipped.
- Not always
- In the live CD environment the problem not present.
** At
The assigned bug (gnome-bugs #528927) has been fixed in 2.23.x , but the
problem still exists in Intrepid.
--
[hardy] amsn does not "blink" / "flash" on new messages with metacity on hardy
https://bugs.launchpad.net/bugs/220555
You received this bug notification because you are a member of Ubuntu
20 matches
Mail list logo
