** Attachment added: xrandr + xdpyinfo output after LVDS is turned off and
TMDS is only active monitor
http://launchpadlibrarian.net/22912460/list.after-turn-off-lvds-and-tmds-1-to-1920
--
Screen dimensions of external monitor not correct on X server startup (intel
driver)
Hi Bryce,
I've tried again with Kubuntu Jaunty-19-Feb-2009 and same the harware
(D830 ..., Dell 24'' TFT ...) The problem is still reproduceable :(
Minor change: xdpyinfo list 129 instead of 147 dpi at the beginning.
xserver-xorg-video-intel 2:2.6.1-1ubuntu2
** Attachment added: xrandr + xdpyinfo after an adiditional logout/in
http://launchpadlibrarian.net/22912520/list.after-logout-in-with-only-TMDS-active
--
Screen dimensions of external monitor not correct on X server startup (intel
driver)
https://bugs.launchpad.net/bugs/135557
You
** Attachment added: CoreDump.gz
http://launchpadlibrarian.net/22027395/CoreDump.gz
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/22027396/Dependencies.txt
** Attachment added: Disassembly.txt
http://launchpadlibrarian.net/22027397/Disassembly.txt
** Attachment
I get the same here in hardy. The relevant peace of buggy code has not
changed in jaunty. Problem is that gconftool complains to stderr when a
value is not set (in hardy and jaunty):
$ gconftool --get /system/http_proxy/port
No value set for `/system/http_proxy/port'
redirecting to stderr
Todays dist-upgrade: Tim Gardner included the firmware in linux-firmware 1.5.
So I set the status to fix released.
Thx Tim!!
** Changed in: linux-firmware (Ubuntu)
Status: New = Fix Released
--
firmware for Hauppauge Nova-T too old: needs: dvb-usb-dib0700-1.20.fw
Public bug reported:
Binary package hint: linux-firmware
Hi, my Hauppauge Nova-T works fine in intrepid dvb-usb-dib0700-1.10.fw In
Jaunty the kernel want 1.20 that is
not in linux-firmware page. My Hauppauge Nova-T is
Bus 007 Device 004: ID 2040:7070 Hauppauge
the 2.6.28-4-generic kernel
I've recorded a peace of TV with kaffeine. The mpeg file gives sound
with dragon video player, no sound with kaffeine. So the firmware is
not the problem and works as expected.
Achim
--
firmware for Hauppauge Nova-T too old: needs: dvb-usb-dib0700-1.20.fw
FWIW: I had a quick try booting the liveCDs of Fedora 10 and OpenSuSE
11.1.
* Fedora 10: same error 96 dpi. Therefore fonts really small
* OpenSuSE 11.1: Display dimension used is wrong: 1260x960 instead
of 1400x1050 (Xorg.conf contains: Option PreferredMode 1400x1050) the
displaysize
HI Bryce,
I'm writing this from Kubuntu Jaunty LiveCD (15-Jan-2009) session. I still see
the problem.
dpi is 96 instead of 124.
** Attachment added: wrong dpi: jaunty xorg.0.log
http://launchpadlibrarian.net/21249984/Xorg.0.log
--
ati radeon driver does not autodetect displaysize on
** Attachment added: lshal output
http://launchpadlibrarian.net/21250268/lshal.out
--
ati radeon driver does not autodetect displaysize on Latitude D600, therefore
uses wrong resolution
https://bugs.launchpad.net/bugs/80940
You received this bug notification because you are a member of
** Attachment added: get-edid | parse-edit output
http://launchpadlibrarian.net/21250242/edid.out
--
ati radeon driver does not autodetect displaysize on Latitude D600, therefore
uses wrong resolution
https://bugs.launchpad.net/bugs/80940
You received this bug notification because you are a
** Attachment added: xrandr --verbose output
http://launchpadlibrarian.net/21250303/xrandr.out
--
ati radeon driver does not autodetect displaysize on Latitude D600, therefore
uses wrong resolution
https://bugs.launchpad.net/bugs/80940
You received this bug notification because you are a
** Changed in: exiv2 (Ubuntu Feisty)
Assignee: Achim Bohnet (allee) = (unassigned)
** Changed in: exiv2 (Ubuntu)
Assignee: Achim Bohnet (allee) = (unassigned)
--
portrait CRW files (EOS 300D) are upside down
https://bugs.launchpad.net/bugs/105947
You received this bug notification
Kubuntus KDE4 only contains kipi-plugins for KDE 3 not KDE4. As gwenview uses
KDE4 it find no kipi plugins as
KDE 3 kipi-plugins can't be used with an KDE 4 app.
--
Genview does not detect kipi plugins
https://bugs.launchpad.net/bugs/278822
You received this bug notification because you are a
Problem, 96 dpi as default instead of 125 , is still there with
* dell latitude 600 with ati card, 1400x1050 display
* intrepid live cd 20080917.4 session
* the radeon xorg driver
** Attachment added: install xorg driver list
http://launchpadlibrarian.net/17728843/pkgs.list
--
ati
** Attachment added: Xorg.0.log
http://launchpadlibrarian.net/17730939/Xorg.0.log
--
ati radeon driver does not autodetect displaysize on Latitude D600, therefore
uses wrong resolution
https://bugs.launchpad.net/bugs/80940
You received this bug notification because you are a member of
** Attachment added: xorg.conf
http://launchpadlibrarian.net/17732067/xorg.conf
--
ati radeon driver does not autodetect displaysize on Latitude D600, therefore
uses wrong resolution
https://bugs.launchpad.net/bugs/80940
You received this bug notification because you are a member of Ubuntu
** Attachment added: xdpyinfo.out
http://launchpadlibrarian.net/17732357/xdpyinfo.out
--
ati radeon driver does not autodetect displaysize on Latitude D600, therefore
uses wrong resolution
https://bugs.launchpad.net/bugs/80940
You received this bug notification because you are a member of
Adding Option IgnoreEDID does not help. DPI still 96.
** Attachment added: Diff of output files when IgnoreEDID is added
http://launchpadlibrarian.net/17732480/with-ignoreedid.diff
--
ati radeon driver does not autodetect displaysize on Latitude D600, therefore
uses wrong resolution
Using IgnoreEDID and Display size and xdpyinfo still reports 96 dpi :(
Strange is that in xorg.log xserver says dpi (124 142). Diff to the default
attached.
** Attachment added: with-ignoreedid-and-displaysize.diff
http://launchpadlibrarian.net/17732545/with-ignoreedid-and-displaysize.diff
No change, i.e. still the wrong 96 dpi, when only displaysize is used
(without ignoreedid) :(
Lemme know if you need further info.
Achim
--
ati radeon driver does not autodetect displaysize on Latitude D600, therefore
uses wrong resolution
https://bugs.launchpad.net/bugs/80940
You received
Can not reproduce here. openafs client still works fine in hardy for me
(I get the 'same' msg in kern.log)
# uname -r
2.6.24-16-server
# dpkg -l openafs-modules-2.6.24-16-server |tail -1
ii openafs-modules-2.6.24-16-server 1.4.6.dfsg1-2+2.6.24-16.30 AFS
distributed filesystem kernel
I can reproduce your problem. I can read/write files
without problem with openafs-modules-2.6.24-16-generic
1.4.6.dfsg1-2+2.6.24-16.30
Please update from 2.6.24-12-generic to the current 2.6.24-16-generic kernel
and try again.
** Changed in: openafs (Ubuntu)
Status: New = Incomplete
--
Can you check that the package digikam-dbg is installed, and if not install it.
Next time crash handler output should contain less '??' after
[KCrash handler]
Further please give the output of
dpkg -l showfoto digikam* *kipi* *exiv2* *kdcraw*
--
Crash on exit, often
Mhmm, my last digikam update only disabled debug output. I doubt that this is
related but I'm happy to hear that it works now.
@Brendan: When it happens again: The problem was/is with your self installed
stuff
below /usr/local: e.g. /usr/local/lib/kde3/kio_digikamalbums.la. Clean up
stuff
Your problem was:
Could not open library '/usr/lib/kde3/kio_digikamalbums.la'.
libexiv2.so.0: cannot open shared object file: No such file or directory
I've check the .la files here and found no reference to libexiv2.so.0.
In fact in hardy libexiv2-2 pkg is used everywhere and
Hi Brendan,
digikam work without problems here. if checked an dist-upgraded hardy
(i386) still no problem. As it's a different problem (complain about lib
instead of URL) can you open a new bug report, please?
Just to make sure nothing is kept open: logout/login and retry.
Add to the new report
** Summary changed:
- ds9 in feisty hangs on exit (version in dapper is okay)
+ ds9 in hardy/gutsy/feisty hangs on exit (version in dapper is okay)
--
ds9 in hardy/gutsy/feisty hangs on exit (version in dapper is okay)
https://bugs.launchpad.net/bugs/122329
You received this bug notification
Today kipi-plugin 0.1.5-1 entered hardy. So this should be fixed.
Can you confirm it?
--
[hardy] batch resize generates error
https://bugs.launchpad.net/bugs/178356
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
Batch tools are from kipi-plugins. Today new kipi-plugins 0.1.5-1 entered
hardy.
Can you still reproduce it?
I could not reproduce with Batch - Resize Image on 2 jpgs to another folder
in the digikam library. Everything works fine.
If you still can reproduce it with 0.1.5-1
* tell us
Today kipi-plugins 0.1.5-1 entered hardy. When the
mjpegtools package is not installed, I get an dialog
with
Cannot find 'mp2enc' binary program from Mjpegtools package.
please install it.
mjpegtools is not free software. So kipi-plugins pkg can't depend on
or recommend it.
Today new showfoto entered hardy. Do you still get the
crashes?
** Changed in: digikam (Ubuntu)
Status: New = Incomplete
--
[Hardy] Showfoto crashes on exit
https://bugs.launchpad.net/bugs/206354
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Which kubuntu release are you using? What's the output of
dpkg -l digikam kipi-plugins
What did you do exactly? Did you use the Batch tools the image editor?
Please provide step by step instruction to reproduce the error.
If you're using hardy, today new version were uploaded. You still
Prepared pkgs for upload are at:
https://edge.launchpad.net/~allee/+archive/
I ping on #kubuntu-devel about upload.
--
[Hardy] digikam duplicates downloaded images while overwriting existing ones
https://bugs.launchpad.net/bugs/201053
You received this bug notification because you are a
Too late. I was told that there already in freeze due to the beta release.
After beta it will go in.
--
[Hardy] digikam duplicates downloaded images while overwriting existing ones
https://bugs.launchpad.net/bugs/201053
You received this bug notification because you are a member of Ubuntu
Bugs,
I assume that the 'Errorfile already exists. Aborting.' is due to the
fact that you can't override an file in the NFSroot. That is due to
https://bugs.edge.launchpad.net/ubuntu/+source/fai/+bug/197006
If you enabled remote login (e.g. via fai-chboot -IFv hostname)
you can login and check the
Thx Olivier for the report. Gilles final commit contains two more one line
changes.
I've used this to create an debdiff for hardy:
* Fix: [Hardy] digikam duplicates downloaded images while overwriting
existing ones. Added: patches/10_lp201053_fix_download_rename_race.diff
This is a
digikam 0.10 is based on KDE4 and more or less a rewrite.
IMHO it's not something to consider for hardy. If nothing goes wrong
digikam 0.10 will be ready together for KDE 4.1 in Juli and there will be
backports, either officiall ones or in my repo.
Achim
--
digikam will not start with
* New upstream release
[ Achim Bohnet ]
* debian/copyright:
+ new, again DSFG compliant, dcwraw license.
+ upstream authors.
* debian/control:
+ use Vcs-* instead of XS-Vcs-* as Vcs-* are now official.
+ add the new Homepage header field. Remove homepage URL from long
Libdcraw supports more raw camera models and has again a DSFG compatible
license.
No bugs in debian BTS or launchpad. Upstream NEWS for 0.1.2 - 0.1.3 is:
- updated dcraw to 8.81
new cameras: Canon G7, Fuji FinePix S9100/S9600, Olympus SP560UZ, Panasonic
DMC-L10
- updated dcraw to 8.80
new
I could not reproduce is as default behaviour. I did in Gutsy:
kdesu konsole
and no knemo instance shows up.What are you doing to
trigger the second knemo instance?
FWIW:
knemo is a implemented via a kded service.Every KDE
application needs a kded running. So
when you run an kde
Sorry, that's
printenv HOME
printenv KDEHOME
without the $.
--
two knemo icons while running anything with kdesu
https://bugs.launchpad.net/bugs/159810
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing
Hi Jerome,
is this a fresh FAI install or did you upgrade from earlier versions?
Can you try to chroot to the fai NFS root directory
(the default is /srv/fai/nfsroot/live/filesystem.dir) and run
apt-get install --reinstall install fai-nfsroot
If this does not give any hint what's going
@Johan: yes, libgphoto2-2 version 2.4.0-2ubuntu2 should have fixed it.
When it does not for you, you have another problem.
Install gphoto2 and run
gphoto2 --auto-detect
if gphoto2 finds your camera and digikam does not then you _still_ have the
bug, but I doubt it. Did your camera work
Public bug reported:
Binary package hint: kdesudo
kdesudo strips one level of quotes, that makes it unnecessarily complicated
and deviates from sudo behaviour (and FWIW all other command line tools).
kdesudo kate one two# opens 2 files: 'one' and
'two' - BUG
sudo
That this ever worked in kdesu was a bug IMHO.kdesudo (kdesu is now
a link to it)
Here's why
sudo id whoami - sudo: id whoami: command not found
Even su complain. To do what you want with su one has to use
su -c comamnd1 command2
There is a -c (pass to shell) command. As
Ah, okay. So your bug is not related at all to this one:
digikam does not use libgphoto for USB Mass Storage cameras.
It has it's own implementation for them.
USB mass storage cameras/devices /plain dirs work fine here
ith digikam, so maybe it's really a bug in the kernel as you suspects.
*** This bug is a duplicate of bug 157043 ***
https://bugs.launchpad.net/bugs/157043
** This bug has been marked a duplicate of bug 157043
command chaining with doesn't work AS IT strips one level of quoting
--
kdesudo/kdesu strips quoting
https://bugs.launchpad.net/bugs/157733
You
Bug 157733 is the side of the same coin. Marking as duplicate.
Bug is that kdesu/do strips one level of quoting. Breaking with
usual shell parsing behaviour:
kdesudo strips one level of quotes, that makes it unnecessarily complicated
and deviates from sudo behaviour (and FWIW all other command
No. I'm using my dapper 1.4.4-x backports. Ditto for edgy but there are now
all replace with feisty.
I trust upstream enough, to backports on dapper ... gutsy the new 1.4.*
releases. Sorry, lame
excuse to not test it :(
--
Openafs has a security hole with enabled suid
@don:
this only means that the d600 has a different problem.
Find out your pci id and codec, google/search launchpad if there
already a bug report. If not open a new one and add a ref
to https://wiki.kubuntu.org/LaptopTestingTeam/DellLatitudeD800
--
[gutsy] no sound on Dell Latitude
Feisty: fai 3.1.8 has two problems:
1) fai kernel version != distro version. So endless, e.g. hda versus sda
trouble
2) fai softupdate does not work
So I would suggest for feisty update/backport fai to 3.2.1, instead of
spending time with the obsolete fai-kernels.
Feisty (and Dapper)
gusty: fai 3.2 does not need a special fai-kernels anymore. And the pkgs is
removed from archive.
therefore I mark the bug as invalid for gutsy.
** Changed in: fai-kernels (Ubuntu)
Status: New = Invalid
--
FAI kernel does not include working bnx2 driver (Broadcom, Dell)
fwiw: Missing changelog -- #149297
--
[gutsy] Xorg or Intel Driver Shows bar at bottom fter upgrade
https://bugs.launchpad.net/bugs/151256
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
Feisty: fai 3.1.8 has two problems:
1) fai kernel version != distro version. So endless, e.g. hda versus sda
trouble
2) fai softupdate does not work
So I would suggest for feisty update/backport fai to 3.2.1, instead of
spending time with the obsolete fai-kernels.
Feisty (and Dapper)
gusty: fai 3.2 does not need a special fai-kernels anymore. And the pkgs is
removed from archive.
therefore I mark the bug as invalid for gutsy.
** Changed in: fai-kernels (Ubuntu)
Status: New = Invalid
--
FAI kernel does not include working bnx2 driver (Broadcom, Dell)
Status unchanged with -14 kernel: By default no sound.
Latitude D830 with:
module-assistant -l 2.6.22-14-generic auto-install alsa # builds:
1.0.14-1ubuntu2+2.6.22-14.41
and sound works again after reboot as with -13 kernel.
--
[gutsy] no sound on Dell Latitude D630/D830/Precision
** Changed in: openafs (Ubuntu)
Status: New = Invalid
--
openafs gives segfault on kernel 2.6.22-13
https://bugs.launchpad.net/bugs/150469
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
Or try
DisplaySize width height
This optional entry gives the width and height, in millimetres,
of the picture area of the monitor. If
given this is used to calculate the horizontal and vertical pitch
(DPI) of the screen.
In the monitor section of
FWIW: if your laptop model is not listed in the bug summary add it:
Actions: Edit description/tags: - add it to summary field
--
[gutsy] no sound on Dell Latitude D630/D830/Precision M4300/Vostro 1500/1700
pci id 8086:284b
https://bugs.launchpad.net/bugs/131133
You received this bug
*** This bug is a duplicate of bug 149297 ***
https://bugs.launchpad.net/bugs/149297
** This bug has been marked a duplicate of bug 149297
xserver-xorg-video-intel package missing changelog
--
intel video driver ships without changelog.Debian
https://bugs.launchpad.net/bugs/150496
You
I can't reproduce it on. klog works fine with my AFS user.
Linux allee 2.6.22-13-generic #1 SMP Thu Oct 4 17:18:44 GMT 2007 i686
GNU/Linux
[EMAIL PROTECTED](0) ~ $ dpkg -l \*afs\* | grep ^i
ii libpam-openafs-kaserver 1.4.4.dfsg1-7 AFS
distributed filesystem
Rebuilding alsa with module assistant and rebooting make sound with 2.6.22-13
on my Latitude D830
working.
ii alsa-modules-2.6.22-13-generic 1.0.14-1ubuntu2+2.6.22-13.40
ALSA modules for kernel 2.6.22-13-generic
Pending problems with this approach:
a) output jack does not mute internal
** Description changed:
I have no sound in Gutsy x86_64. In Feisty, sound worked fine.
My laptop is a Dell Latitude D830.
Found in dmesg log file:
[ 23.252496] hda_intel: azx_get_response timeout, switching to polling
mode...
[ 23.550621] ipw3945: Detected geography ABG
@Micheal: this is listed already on Gutsy_Intel_HD_Audio_Controller wiki page.
See also my comment
https://bugs.edge.launchpad.net/ubuntu/+source/linux-source-2.6.22/+bug/131133/comments/58
@all: dded the wikipage to the bug description
I've added the workaround that works for me to the
Sorry, can't help. I tried to reproduce and could not.
Just want to add: I'm authenticating against a kerberos4
server.
Maybe strace output or running under gdb gives an idea?
--
openafs gives segfault on kernel 2.6.22-13
https://bugs.launchpad.net/bugs/150469
You received this bug
Thx Fred for the clarification.
My docked Dell D830 gives:
$ cat /proc/asound/card0/codec#* | grep Codec
Codec: SigmaTel STAC9205
Codec: Conexant ID 2c06
$ lspci | grep -i audio
00:1b.0 Audio device: Intel Corporation 82801H (ICH8 Family) HD Audio
Controller (rev 02)
$ lspci -n | grep
*** This bug is a duplicate of bug 145239 ***
https://bugs.launchpad.net/bugs/145239
@Oliver: first ,thx for your kind words.
About 'next bug ...'. Please open a new bug report for every problem you find.
I'm notified about every bug for digikam package and will have a look.
a) I'm not
*** This bug is a duplicate of bug 149297 ***
https://bugs.launchpad.net/bugs/149297
** This bug has been marked a duplicate of bug 149297
xserver-xorg-video-intel package missing changelog
--
xserver-xorg-video-intel contains no changelog.Debian
https://bugs.launchpad.net/bugs/140794
Weired. Looks like digikam in kubuntu now needs the .la files of the
libgphoto2 plugins too.
Debian always had this problem: Plugings not starting with lib* need the .la
files:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=390703
At least in Feisty digikam/kdelibs works fine without
On Thursday 18 May 2006 19:21, Ivan Krstic wrote:
Carl Karsten wrote:
[EMAIL PROTECTED]:~$ uname -a
Linux tsp2 2.6.15-21-386 #1 PREEMPT Fri Apr 21 16:43:33 UTC 2006 i686
That's the desktop kernel. The default installed by the u-s CD should
have been set to the server kernel a while back.
201 - 272 of 272 matches
Mail list logo
