Shed Fat

[Brian]

Body Wrap at Home to lose 6-20 inches in one hour.

With Bodywrap we guarantee:
 you'll lose 6-8 Inches in one hour 
 100% Satisfaction or your money back

Bodywrap is soothing formula that contours, 
cleanses and rejuvenates your body while
reducing inches.

http://barnhard.loseweightsystems.com










cotty agb brevity ugq snowstorm jf brag nt chastise tqj polk gc 
chit qho afraid cz level adg yard gw aqua rhl ant nok begun aei tercel ilj 
http://barnhard.loseweightsystems.com/r


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#738153: Found this bug report trying to work with qtcreator...

[Brian Jackson]

Found this bug report trying to work with qtcreator + qt5 on Debian
recently. I'm not sure if I actually solved the problem, but I've had
more luck after installing some of the qtdeclarative5-* packages
(specifically in the case of getting the basic demo working, I installed
qtdeclarative5-qtquick2-plugin I think). Would be interesting to know if
that helps anybody else get rolling with qtcreator. For reference I did
the same thing on a Ubuntu 14.04 system to get it working after having
the same problem there too.


-- 
To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/534190ee.4060...@theiggy.com

Bug#911702: okular: Does not print to network printers

[Brian Potkin]

On Tue 23 Oct 2018 at 18:28:59 +0100, Brian Potkin wrote:

> 2.2.8-5 is the CUPS version. cups-browsed is not running.
> 
>  brian@test:~$ lpstat -l -e
>  ENVY4500 network none ipp://ENVY4500._ipp._tcp.local/
>  LaserJet_300_desktop network none 
> ipps://LaserJet-300%20%40%20desktop._ipps._tcp.local/cups
>  realq_desktop network none ipps://realq%20%40%20desktop._ipps._tcp.local/cups
>  test permanent ipp://localhost/printers/test 
> usb://HP/ENVY%204500%20series?serial=CN56G332DT060D&interface=1
>  zzz_desktop3 network none ipps://zzz%20%40%20desktop3._ipps._tcp.local/cups
> 
> There are three printers/queues on the network and a local queue, test.

Four, actually. But who's counting? And none of them print.

Regards,

Brian.

Bug#911844: okular: Prints to the wrong printer

[Brian Potkin]

Package: okular
Version: 4:17.12.2-2
Severity: critical
Tags: upstream security



"critical" because a document should always go to where it is sent.
Please reduce the severity if I have overestimated the security
implications.

The CUPS version being used is 2.2.8-5 and cups-browsed is not running.
The issue was encountered while taking another look at #911702.

 brian@test:~$ lpstat -e
 aaa
 realq_desktop
 test

aaa and test are local queues set up with

 lpadmin -p  -v file:/home/brian/capture -E -m 
drv:///sample.drv/generic.ppd

and realq_desktop is a queue on a remote machine.

Okular was started from a terminal. Printing to realq_desktop produces an
output of

 request id is aaa-41 (1 file(s))

The job is always sent to a local queue when its destination precedes
realq_desktop alphabetically.

Removing the aaa queue gets

 /usr/bin/lp: No such file of directory (which is #911702)

I believe printing from LibreOffice to be based on the same principles
as printing from Okular. Printing from that application is not an issue.
qpdfview is another affected application.

Regards,

Brian.

Bug#942653: kde-plasma-desktop: On system start, primary display does not render background or allow r-click to access menu

[Brian R.]

Package: kde-plasma-desktop
Version: 5:104
Severity: important

Dear Maintainer,

System is Asus P8Z77 w/ Intel i7 2600K processor and AMD RTX5700 graphics. Dual
monitor setup with Samsung Syncmaster primary on DVI and LG smart TV secondary
on HDMI. LightDM is installed with Plasma and Cinnamon DE's.

After login from system start, the primary display will not have the background
wallpaper displayed; background is black. System tray shows and main menu is
accessible, but r-click on background to call up desktop menu not functional.
On secondary display however the wallpaper is displayed and the desktop menu
will appear with r-click. Logging out of session then logging back in generally
corrects the issue and functions as normal once new session starts with
background and desktop menu on r-click.

I've seen previous reports of similar behavior with Nvidea graphics; can
confirm bug exists with AMD graphics as well. Issue not present when logging
into Cinnamon.



-- System Information:
Debian Release: bullseye/sid
  APT prefers testing
  APT policy: (500, 'testing'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.2.0-0.bpo.2-rt-amd64 (SMP w/8 CPU cores; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE= 
(charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages kde-plasma-desktop depends on:
ii  kde-baseapps  4:17.08.3+5.104
ii  plasma-desktop4:5.14.5.1-4
ii  plasma-workspace  4:5.14.5.1-3+b1
ii  udisks2   2.8.4-1
ii  upower0.99.11-1

Versions of packages kde-plasma-desktop recommends:
ii  kwin-x11  4:5.14.5-1
ii  sddm  0.18.0-1
ii  xserver-xorg  1:7.7+19

Versions of packages kde-plasma-desktop suggests:
ii  kdeconnect  1.3.3-2

-- no debconf information

Bug#942654: kde-baseapps: Numlock state not changed per settings during startup or screenlock

[Brian R.]

Package: kde-baseapps
Version: 4:17.08.3+5.104
Severity: normal

Dear Maintainer,

I've set numlock "on" at login in KDE system settings, but after recent
updates, the numlock state is no longer applied per user settings. Numlock must
be turned on manually. If screen locks due to inactivity, numlock state is lost
again and must be turned on manually. Verified that in KDE System Settings,
"Numlock on Plasma startup" option is checked "Yes."



-- System Information:
Debian Release: bullseye/sid
  APT prefers testing
  APT policy: (500, 'testing'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.2.0-0.bpo.2-rt-amd64 (SMP w/8 CPU cores; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE= 
(charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages kde-baseapps depends on:
ii  dolphin 4:19.08.1-1
ii  kdialog 4:17.08.3-2
ii  keditbookmarks  17.08.3-2
ii  kfind   4:19.08.1-1
ii  konqueror   4:19.08.2-2
ii  konsole 4:19.08.1-2
ii  kwrite  4:19.08.2-1

kde-baseapps recommends no packages.

kde-baseapps suggests no packages.

-- no debconf information

Bug#952704: libqt5printsupport5: Printer and queue attributes not available

[Brian Potkin]

Package: libqt5printsupport5
Version: 5.12.5+dfsg-8
Severity: important


I have an up-to-date unstable system with CUPS and cups-filters 
   
installed. cups-browsed is not installed.   
  

   
The Qt print dialog has two entries: ENVY4500 and LaserJet_300_desktop. 
   
The ENVY is an IPP printer on the network and the LaserJet is an
   
advertised queue on a remote CUPS server. The enumeration is done via   
   
DNS-SD from the printer and the server and both devices are capable of  
   
two-sided printing. All ok up to there. 
   

   
Looking under Options, the duplex options are greyed out. Furthermore,  
   
"Advanced" under "Properties" is also greyed out. The latter means that 
   
a user cannot set values for Media Type, Color Model and Print Quality. 
   
Rather a disadvantage, I would have thought. Here is an output from
querying the printer:   


   
brian@cupstest:~$ lpoptions -p envy4500 -l  
   
PageSize/Media Size: 100x150mm 111.76x152.4mm 3.5x5 3.5x5.Borderless 3x5
   4x6 4x6.Borderless 5x7 5x7.Borderless 
5x8 8x10 8x10.Borderless *A4
 A4.Borderless A5 A6 A6.Borderless B5 Env10 EnvA2 EnvC5 EnvC6 EnvChou3  
EnvChou4 EnvDL EnvMonarch EnvPersonal 
Executive ISOB5 Legal Letter
 Letter.Borderless Postcard Postcard.Borderless Statement Custom.WIDTHxHEIGHT   

MediaType/Media Type: *Stationery PhotographicGlossy
   
ColorModel/Output Mode: *RGB Gray Gray16 DeviceGray DeviceRGB AdobeRGB  
   
Duplex/Duplex: *None DuplexNoTumble DuplexTumble
   
cupsPrintQuality/cupsPrintQuality: Draft *Normal High   
   
brian@cupstest:~$   
   

   
If the printer or print queue is printed to, CUPS forms a temporary,
   
local queue and a PPD is generated in /etc/cups/ppd from the queries
   
made. This queue exists for a minute and during that time the duplex and
   
Advanced options are available in the Qt dialog.
   

   
It seems to me that the dialog is not querying either printer or queue  
   
to get their attributes to display but, OTOH, is happy to deal with 
   
local queues, which is what cups-browsed supplies. It would be good to  
   
take full advantage of what CUPS offers and fix this unsatisfactory 
   
behaviour.  
   

   
Regards,
   

   
Brian. 

Bug#293283: not able to use Linux font despite following instructions in README.Linux-font

[Brian Kimball]

Package: konsole
Version: 4:3.3.2-1
Severity: normal

Hi, the subject says it all.  I've followed the directions in
README.Linux-font and I still can't get the Linux font working in
Konsole.  I get the following error message:

   Font `-misc-console-medium-r-normal--16-160-72-72-c-80-iso10646-1' not
   found.

   Check /usr/share/doc/konsole/README.Linux-font for help.

FWIW I'm able to view the above font just fine in xfontsel.  I also
don't think this is a problem with my fontconfig configuration because
my /etc/fonts/{fonts.conf,local.conf} files match character-for-character
files on another machine where the Linux font *does* work.  I've tried
turning on and off anti-aliasing, deleting my user's .fonts.conf file,
even starting with a fresh test user.  Nothing works.

If there's anything I can do to give you more information, please let me
know.

Cheers,

Brian



-- System Information:
Debian Release: 3.1
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.6.10
Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1)

Versions of packages konsole depends on:
ii  kdelibs4 4:3.3.2-1   KDE core libraries
ii  libart-2.0-2 2.3.17-1Library of functions for 2D graphi
ii  libc62.3.2.ds1-20GNU C Library: Shared libraries an
ii  libfam0c102  2.7.0-6 client library to control the FAM 
ii  libgcc1  1:3.4.3-7   GCC support library
ii  libice6  4.3.0.dfsg.1-10 Inter-Client Exchange library
ii  libidn11 0.5.2-3 GNU libidn library, implementation
ii  libpng12-0   1.2.8rel-1  PNG library - runtime
ii  libqt3c102-mt3:3.3.3-8   Qt GUI Library (Threaded runtime v
ii  libsm6   4.3.0.dfsg.1-10 X Window System Session Management
ii  libstdc++5   1:3.3.5-8   The GNU Standard C++ Library v3
ii  libx11-6 4.3.0.dfsg.1-10 X Window System protocol client li
ii  libxext6 4.3.0.dfsg.1-10 X Window System miscellaneous exte
ii  libxrender1  0.8.3-7 X Rendering Extension client libra
ii  libxtst6 4.3.0.dfsg.1-10 X Window System event recording an
ii  xlibs4.3.0.dfsg.1-10 X Keyboard Extension (XKB) configu
ii  zlib1g   1:1.2.2-4   compression library - runtime

-- no debconf information


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#293283: not able to use Linux font despite following instructions in README.Linux-font

[Brian Kimball]

On Friday 04 February 2005 05:06 am, Josh Metzler wrote:

> Could you send us the output of
>
> $ grep -A 4 bitmapped /etc/fonts/local.conf

There is no output on the machine in question, and
also on the machine where the font works.

# grep -A 4 bitmapped /etc/fonts/local.conf
#

> $ dpkg --list xfonts-konsole

Now now, of course I have it installed. :-)  This
is a completely fresh installation on a new laptop.
3.3.2-1 was installed clean, not upgraded.  Don't
know if that helps or not.

ii  xfonts-konsole3.3.2-1   Fonts used by 
the KDE Konsole

thanks,

 brian


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: DRM in PDF readers

[Brian Ristuccia]

On Sat, Mar 12, 2005 at 03:01:15PM +0100, Frederic Peters wrote:
> Hello,
> 
> I recently adopted pdftohtml, a program to translate PDF documents into
> HTML.  It is a derivative of xpdf.  I am now asked to override the DRM
> tests (current code checks for "don't copy me" pdf flag and aborts if
> set).
> 

I wrote a patch for xpdf to fix the permissions problem discussed in Debian
bug #145559. The package maintainer eventually got together a more
comprehensive fix and the bug was closed. Here's an excerpt from my message
on the BTS explaining why it was a severity important bug:

   Being unable to print and use the X selection facility for certain
   documents has a "major effect on the usability of a package, without
   rendering it completely unusable to everyone." Pdftotext is the only easy
   way to feed the contents of a pdf file into a text-to-speech program.
   [...] For the vision impaired, xpdf is mostly or completely useless if
   pdftotext refuses to run on many valid pdf files.

> 
> My current idea is to default to upstream behaviour and implements an
> option to override the settings but I would like to have some comments
> on the "DRM-in-Debian" situation.
> 

Almost every bit of software in Debian either completely ignores  copyright
license information embedded in files. As an example, cp will not prevent
you from copying a Debian package contrary to terms in its
/usr/share/doc/../copyright file. PDF readers and pdftohtml should be no
exception.

It is important to be careful not to introduce new bugs when closing this
one. Just like a fix to a "refuses to copy" bug in cp could not cause cp to
silently strip the copyright file out of Debian packages it copies, your bug
fix must not break the pdf reader's ability to display or output the
copyright license data if it had that feature before.

-- 
Brian Ristuccia
[EMAIL PROTECTED]


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#306694: ITP: qt-x11-opensource -- Qt 4 cross-platform C++ application framework

[Brian Nelson]

Package: wnpp
Severity: wishlist

* Package name: qt-x11-opensource
  Version : 4.0 beta 2
  Upstream Author : Trolltech AS
* URL or Web page : http://www.trolltech.com
* License : Dual GPL/QPL
  Description : Qt 4 cross-platform C++ application framework

Qt is a cross-platform C++ application framework.  Qt's primary feature
is its rich set of widgets that provide standard GUI functionality.

Qt 4 is the next major revision of Qt, currently planned for a late Q2
release.

Preliminary packaging is available here:

  http://people.debian.org/~pyro/experimental/

I would like to group-maintain this package and have set the maintainer
to "Debian Qt/KDE Maintainers " in the
preliminary packages.  Please let me know if this is inappropriate for
whatever reason.

I plan to maintain the packaging in a distributed version control
system, once I figure out which of the 20 or so is the most practical.

-- 
Society is never going to make any progress until we all learn to
pretend to like each other.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#269791: (no subject)

[Brian Beck]

Package: kpat
Version: 3.3.2-1
Severity: normal

This bug still exists in KDE 3.3.2.  Does anyone know if it is a KDE issue or a 
Debian issue?

When I run kpat from the console these are the error messages I receive...

$kpat
QObject::connect: Cannot connect (null)::undoPossible(bool) to 
pWidget::undoPossible(bool)
QObject::connect: Cannot connect (null)::gameWon(bool) to pWidget::gameWon(bool)
QObject::connect: Cannot connect (null)::gameLost() to pWidget::gameLost()
KCrash: Application 'kpat' crashing...
$


Here is the output from the KDE Crash Handler Backtrace...

(no debugging symbols found)
Using host libthread_db library "/lib/libthread_db.so.1".
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 16384 (LWP 7250)]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[KCrash handler]
#5  0x0805eaac in ?? ()
#6  0x081c9480 in ?? ()
#7  0x081483f0 in ?? ()
#8  0xbfffee28 in ?? ()
#9  0x08099259 in _IO_stdin_used ()
#10 0x0809924a in _IO_stdin_used ()
#11 0x081483f0 in ?? ()
#12 0xbfffef58 in ?? ()
#13 0x08064a47 in ?? ()
#14 0x in ?? ()
#15 0x0001 in ?? ()
#16 0x081483f0 in ?? ()
#17 0x08099268 in _IO_stdin_used ()
#18 0x40639300 in __after_morecore_hook () from /lib/libc.so.6
#19 0x081706d0 in ?? ()
#20 0xbfffee68 in ?? ()
#21 0x41358d7a in pthread_mutex_unlock () from /lib/libpthread.so.0


$ uname -a
Linux legionWorld 2.4.27-1-386 #1 Wed Dec 1 19:43:08 JST 2004 i686 GNU/Linux

$ ls -l /lib/libc.so.6
lrwxrwxrwx  1 root root 13 2005-04-23 00:25 /lib/libc.so.6 -> libc-2.3.2.so

Thanks for looking into this.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#313472: Viewing the kdepasswd manpage displays errors

[Brian Beck]

Package: kdepasswd
Version: 3.3.2-1
Severity: minor

When I attempt to get the man page for kdepasswd lots of errors are flashed 
onto the screen before I get the manpage.  Below are the errors I receive...

$ man kdepasswd
Reformatting kdepasswd(1), please wait...
/tmp/zmanzGrp2D:23: a special character is not allowed in a name
/tmp/zmanzGrp2D:27: a special character is not allowed in a name
/tmp/zmanzGrp2D:31: a special character is not allowed in a name
/tmp/zmanzGrp2D:35: a special character is not allowed in a name
/tmp/zmanzGrp2D:39: a special character is not allowed in a name
/tmp/zmanzGrp2D:43: a special character is not allowed in a name
/tmp/zmanzGrp2D:47: a special character is not allowed in a name
/tmp/zmanzGrp2D:53: a special character is not allowed in a name
/tmp/zmanzGrp2D:57: a special character is not allowed in a name
/tmp/zmanzGrp2D:61: a special character is not allowed in a name
/tmp/zmanzGrp2D:66: a special character is not allowed in a name
/tmp/zmanzGrp2D:73: a special character is not allowed in a name
/tmp/zmanzGrp2D:77: a special character is not allowed in a name
/tmp/zmanzGrp2D:82: a special character is not allowed in a name
/tmp/zmanzGrp2D:86: a special character is not allowed in a name
/tmp/zmanzGrp2D:90: a special character is not allowed in a name
/tmp/zmanzGrp2D:96: a special character is not allowed in a name
/tmp/zmanzGrp2D:100: a special character is not allowed in a name
/tmp/zmanzGrp2D:104: a special character is not allowed in a name
/tmp/zmanzGrp2D:108: a special character is not allowed in a name
/tmp/zmanzGrp2D:112: a special character is not allowed in a name
/tmp/zmanzGrp2D:115: a special character is not allowed in a name
/tmp/zmanzGrp2D:121: a special character is not allowed in a name
/tmp/zmanzGrp2D:125: a special character is not allowed in a name
/tmp/zmanzGrp2D:129: a special character is not allowed in a name
/tmp/zmanzGrp2D:135: a special character is not allowed in a name
/tmp/zmanzGrp2D:139: a special character is not allowed in a name
/tmp/zmanzGrp2D:143: a special character is not allowed in a name
/tmp/zmanzGrp2D:147: a special character is not allowed in a name
/tmp/zmanzGrp2D:151: a special character is not allowed in a name
/tmp/zmanzGrp2D:155: a special character is not allowed in a name
/tmp/zmanzGrp2D:159: a special character is not allowed in a name
/tmp/zmanzGrp2D:161: a special character is not allowed in a name
/tmp/zmanzGrp2D:165: a special character is not allowed in a name

I get the error message in xterm, gnome-console, and konsole.

Below is the output i get from locale (I don't know if it's useful but)...

$ locale
LANG=en_US
LC_CTYPE="en_US"
LC_NUMERIC="en_US"
LC_TIME="en_US"
LC_COLLATE="en_US"
LC_MONETARY="en_US"
LC_MESSAGES="en_US"
LC_PAPER="en_US"
LC_NAME="en_US"
LC_ADDRESS="en_US"
LC_TELEPHONE="en_US"
LC_MEASUREMENT="en_US"
LC_IDENTIFICATION="en_US"
LC_ALL=


$ uname -a
Linux singer 2.6.8-1-386 #1 Thu Nov 25 04:24:08 UTC 2004 i686 GNU/Linux

$ ls -l /lib/libc.so.6
lrwxrwxrwx  1 root root 13 2005-05-12 12:56 /lib/libc.so.6 -> libc-2.3.2.so

If there is anymore information I can provide please don't hesitate to ask.

Thanks


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#314691: Typos in the kcharselect manpage

[Brian Beck]

Package: kcharselect
Version: 3.3.2-1
Severity: minor

The second paragraph of the kcharselect manpage has typos.

I have rewritten the second paragraph, hopefully it is easier to read now.


Using KCharSelect one can view all the glyphs, organized by character table, 
available from any installed font.  One can also assemble a string of 
characters by clicking on a character in the table.  The string can be 
exported to the clipboard for later use.  KCharSelect is helpful for 
determining what characters in a font have glyphs as well as selecting 
characters that may be difficult produce.


$ uname -a
Linux singer 2.6.8-1-386 #1 Thu Nov 25 04:24:08 UTC 2004 i686 GNU/Linux

$ ls -l /lib/libc.so.6
lrwxrwxrwx  1 root root 13 2005-05-12 12:56 /lib/libc.so.6 -> libc-2.3.2.so

If I can be of any more help please don't hesitate to ask.

Thanks.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#729603: Baloo

[Brian DeRocher]

Looks like it will be replace with something better in KDE 4.13

http://dot.kde.org/2014/02/24/kdes-next-generation-semantic-search

-- 
Brian DeRocher
http://brian.derocher.org
http://mappingdc.org
http://about.me/brian.derocher


-- 
To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/701769480.xHSeHUyT79@three

Bug#759618: recheck the option

[Brian DeRocher]

I saw this too.  Unchecking and rechecking "Prefer HTML to plain text" seems to 
fix the issue.

But clearly there was some underlying issue that needs to be fixed.

Brian

-- 
http://brian.derocher.org
http://mappingdc.org
http://about.me/brian.derocher

Re: Wheezy update of kde4libs?

[Brian May]

Maximiliano Curia  writes:

> I just did the upload to unstable, with the karchive fix from upstream and an 
> modified version of that one for kde4libs. The second one needs some test, 
> sadly adding the (binary) test file used in karchive is a bit of a burden.
>
> After these packages are available we would need to backport the change to 
> stable. Right now, I can't promise that I would have the time to take care of 
> this. So volunteers for taking care of this are welcome.

I had a look at doing this for wheezy LTS several days ago. It looks
like it should be reasonably straight forward (famous last words?) to
apply the changes manually to the wheezy version, although the files
have moved (and automatic patching failed). If nobody takes this up by
next month I should have some time then to continue this.
-- 
Brian May 

Bug#911844: Severity 911844 normal

[Brian Potkin]

On Sun 10 Mar 2019 at 14:09:27 +, Andrew M.A. Cater wrote:

> Severity 911844 normal

It would be useful to know the reason why the severity has been reduced
to normal. I would have thought a confidential document should not end
up on a machine it was not intended for.

Regards,

Brian.

Bug#911844: Severity 911844 normal

[Brian Potkin]

On Fri 05 Apr 2019 at 16:44:31 +0100, Brian Potkin wrote:

> On Sun 10 Mar 2019 at 14:09:27 +, Andrew M.A. Cater wrote:
> 
> > Severity 911844 normal
> 
> It would be useful to know the reason why the severity has been reduced
> to normal. I would have thought a confidential document should not end
> up on a machine it was not intended for.

Being accorded the courtesy of a reply is not, it seems, on the horizon.
And one wonders why Debian is sometimes not seen as an OS responsive to
a reasonable request.

Never mind. If the intention is to dissuade from questioning, the lack
of response has made its point. The motto appears to be - it's a secret:
don't ask!

Regards,

Brian.

Bug#911844: okular: Prints to the wrong printer

[Brian Potkin]

Severity: critical
thanks



On Thu 25 Oct 2018 at 12:50:25 +0100, Brian Potkin wrote:

> Package: okular
> Version: 4:17.12.2-2
> Severity: critical
> Tags: upstream security
> 
> 
> 
> "critical" because a document should always go to where it is sent.
> Please reduce the severity if I have overestimated the security
> implications.
> 
> The CUPS version being used is 2.2.8-5 and cups-browsed is not running.
> The issue was encountered while taking another look at #911702.
> 
>  brian@test:~$ lpstat -e
>  aaa
>  realq_desktop
>  test
> 
> aaa and test are local queues set up with
> 
>  lpadmin -p  -v file:/home/brian/capture -E -m 
> drv:///sample.drv/generic.ppd
> 
> and realq_desktop is a queue on a remote machine.
> 
> Okular was started from a terminal. Printing to realq_desktop produces an
> output of
> 
>  request id is aaa-41 (1 file(s))
> 
> The job is always sent to a local queue when its destination precedes
> realq_desktop alphabetically.
> 
> Removing the aaa queue gets
> 
>  /usr/bin/lp: No such file of directory (which is #911702)
> 
> I believe printing from LibreOffice to be based on the same principles
> as printing from Okular. Printing from that application is not an issue.
> qpdfview is another affected application.

I have retested this. There is no change on the present unstable. I
cannot see why a confidential print job going to a staff printer is
anything but a security issue. Maybe this is something that merits
the tag of normal but explanations are in short supply.

Regards,

Brian.

Re: Bug#911844: okular: Prints to the wrong printer

[Brian Potkin]

On Tue 11 Jun 2019 at 09:53:50 +0200, Martin Steigerwald wrote:

> severity: important
> thanks
> 
> Hi Brian,
> 
> Brian Potkin - 10.06.19, 21:32:
> > Severity: critical
> > thanks
> > 
> > On Thu 25 Oct 2018 at 12:50:25 +0100, Brian Potkin wrote:
> > > Package: okular
> > > Version: 4:17.12.2-2
> > > Severity: critical
> > > Tags: upstream security
> > > 
> > > 
> > > 
> > > "critical" because a document should always go to where it is sent.
> > > Please reduce the severity if I have overestimated the security
> > > implications.
> > > 
> > > The CUPS version being used is 2.2.8-5 and cups-browsed is not
> > > running. The issue was encountered while taking another look at
> > > #911702.> 
> […]
> > > The job is always sent to a local queue when its destination
> > > precedes
> > > realq_desktop alphabetically.
> […]
> > I have retested this. There is no change on the present unstable. I
> > cannot see why a confidential print job going to a staff printer is
> > anything but a security issue. Maybe this is something that merits
> > the tag of normal but explanations are in short supply.
> 
> Brian, before raising a bug severity to the highest severity possible, 
> please read and understand the Debian's release team guidelines 
> regarding release critical bugs¹ as well as the general descriptions of 
> bug severities².
> 
> A "critical" bug is a bug that introduces a (remotely exploitable) 
> security hole on systems you install the package to. A "grave" bug is a 
> bug that introduces a (remotely exploitable) security hole allowing 
> access to the accounts of users using the package.

Thank you, Martin, for taking the time and trouble to explain. I admit
to feeling uneasy about raising the severity level and did give it some
thought - but obviously not enough. Anyway, something it's for me to
take into account for the future.

> None of this is the case here.
> 
> If at all, the bug might be "serious" if in the maintainers opinion it 
> would make the package unsuitable for release.
> 
> Now please respect the reduced bug severity. Raising the severity again 
> won't get you any priority handling with an already understaffed Debian 
> Qt/KDE team. This is a community of people who are mostly doing unpaid 
> work.
 
I have no intention of touching the severity level again.

> Two ways to use your (and our) time in a more productive manner are:
> 
> 1) Retest with Okular 18.04 from Debian experimental (in case you run 
> buster/sid). Or start KDE Neon in a machine and try with the newest 
> Okular available there.

There might be time for me to do both of these today or tomorrow.
 
> 2) Remind upstream in a friendly way to have a look at the issue. Once 
> there is a patch upstream it is very likely it could be backported for 
> buster. Maybe it would be an idea to raise the upstream bug to KDE's 
> security team.

You seem to have done that. Thanks.

Regards,

Brian.

Bug#911844: okular: Prints to the wrong printer

[Brian Potkin]

On Tue 11 Jun 2019 at 13:20:40 +0200, Martin Steigerwald wrote:

> Brian Potkin - 11.06.19, 10:42:
> > On Tue 11 Jun 2019 at 09:53:50 +0200, Martin Steigerwald wrote:
> […]
> > > Two ways to use your (and our) time in a more productive manner are:
> > > 
> > > 1) Retest with Okular 18.04 from Debian experimental (in case you
> > > run
> > > buster/sid). Or start KDE Neon in a machine and try with the newest
> > > Okular available there.
> > 
> > There might be time for me to do both of these today or tomorrow.
> 
> Wonderful.

And good fun.

I used the neon-user-20190606-1138.iso (okular 19.04.1). Everything
behaved normally. No observed bug there. Okular 18.04 from experimental
wouldn't install because of unmet depenencies. Another time, perhaps.

> > > 2) Remind upstream in a friendly way to have a look at the issue.
> > > Once there is a patch upstream it is very likely it could be
> > > backported for buster. Maybe it would be an idea to raise the
> > > upstream bug to KDE's security team.
> > 
> > You seem to have done that. Thanks.
> 
> Yes, appeared to be the quickest way to more this forward for me.
> 
> There is a reply by Albert already. He is member of KDE security team 
> and AFAIK also develops on Okular. Please review his comments there and 
> answer accordingly. It appears he does not yet understand on how to 
> reproduce. Maybe, if you can, give a concrete example with the necessary 
> CUPS commands or probably an example configuration file.

I will reply to the upstream bug report later.

The various contributions to this report are appreciated. I have learnt
a thing or two.

Regards,

Brian.

Bug#911844: okular: Prints to the wrong printer

[Brian Potkin]

On Sun 16 Jun 2019 at 20:30:05 +0300, Dmitry Shachnev wrote:

> Hi Michael and all!
> 
> On Sat, Jun 15, 2019 at 11:52:08PM +0200, Michael Weghorn wrote:
> > I've investigated a bit and it's not an Okular issue, but one in the Qt
> > print dialog with printers that don't have PPD files. It can be
> > reproduced e.g. with kate just the same and Brian even mentioned in the
> > initial report that qpdfview is affected as well.
> >
> > The issue has been fixed upstream (qtbase) with the following commit (so
> > that's what would have to be backported):
> >
> > commit 84cc8d0badb4abc3c9a96d59c61dddce916a216c
> > Author: Albert Astals Cid 
> > Date:   Mon Feb 5 09:20:20 2018 +0100
> >
> > cups: Support raw printers
> >
> > They don't have a ppd but we don't *really* need a ppd to just
> > print
> >
> > Change-Id: Idf6b6dafc19420a511b057194488e2170cae4d70
> 
> Thanks a lot for finding the commit which fixes this bug!
> 
> I have uploaded a new version of qtbase to unstable today, which has
> it backported.
> 
> Can you please test that it really fixes the bug for you? If yes,
> I will file an unblock request for this upload.
> 
> > This probably also fixes #911702, but I didn't test that explicitly.
> 
> If someone tests that too, it would also be nice.

A couple of quick tests and it seems to me that #911844 and #911702
have been fixed with this upload.

Regards,

Brian.

Bug#952704: libqt5printsupport5: Printer and queue attributes not available

[Brian Potkin]

tags 952704 upstream
found 952704 5.15.2+dfsg-16
thanks


In my opinion, the Qt print dialog should support the CUPS temporary
queue facility correctly. CUPS has APIs to do this. There shoudn't be
any need to set up a permanent manual queue or have cups-browsed add
a permanent queue in order to get remote queue or printer attributes 

Cheers,

Brian.

Bug#437354: libqt4-dev: Put qmake into its own package

[Brian Nelson]

Sune Vuorela <[EMAIL PROTECTED]> writes:

> On Tuesday 12 February 2008, Brian Nelson wrote:
>> Evgeni Golov <[EMAIL PROTECTED]> writes:
>> > Hi,
>> >
>> > are there any updates on this? I maintain pokerth which needs qmake4,
>> > libqt4-core and libqt4-gui, but not -sql, -qt3support etc.
>> > At the moment it build-depends on libqt4-dev which fetches way too much
>> > stuff in during building, what is annoying :)
>>
>> I don't see any compelling reason to split out qmake, and doing so now
>> would probably break some package builds.  I think this should be closed
>> or tagged wontfix.
>
> Some of us are talking about reorganizing how qt4 is packaged. for example, 
> libQtCore is quite nice for all sorts of things locally, but you can't 
> install that on debian without pulling all sorts of other things in.

I think it would be reasonable to put each library in a separate
package.  When I first packaged Qt4, there was nothing out there using
just, e.g. libQtCore, without using other parts of Qt, so it seemed
wasteful to split everything up.  That's probably no longer the case.

> The dev package has not yet been discussed, but it might be possible to do 
> something at the same time.

When it comes to -dev packages, the more things are split up the more
users get confused IMO.  When a user installs libqt4-dev, I think
they'll usually think they're getting the full Qt4 development
environment.  We could have libqt4-dev pull in e.g. qt4-qmake or
whatever, but I think that would be catering to such a tiny niche that
it wouldn't be worth the package bloat.

Plus, qmake is a shitty build tool and I'd rather not encourage its use
by splitting it out of libqt4-dev. :P

-- 
Captain Logic is not steering this tugboat.



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#437354: libqt4-dev: Put qmake into its own package

[Brian Nelson]

Evgeni Golov <[EMAIL PROTECTED]> writes:

> Hi,
>
> are there any updates on this? I maintain pokerth which needs qmake4,
> libqt4-core and libqt4-gui, but not -sql, -qt3support etc.
> At the moment it build-depends on libqt4-dev which fetches way too much
> stuff in during building, what is annoying :)

I don't see any compelling reason to split out qmake, and doing so now
would probably break some package builds.  I think this should be closed
or tagged wontfix.

-- 
Captain Logic is not steering this tugboat.



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#469783: libqt4-dev: Please add qtdemo back and provide the examples

[Brian Nelson]

Dirk Eddelbuettel <[EMAIL PROTECTED]> writes:

> PS It would be nice if you could change debian/rules to set
>
>   -demosdir "/usr/share/qt4/demos" \
>   -examplesdir "/usr/share/qt4/examples" \
>
> as the current qmake binary has the rather awkward paths 
>/usr/demos
>/usr/examples
> preset given thet prefix=/usr.

That's a fine change to make, but it also illustrates the problem of
including a usable qtdemo.  All of the demo sources and binaries would
end up in /usr/share/qt4/demos, which is fine for the sources but bad
for the binaries.  The binaries would need to go in /usr/lib/qt4/demos
or something, and qtdemo would need to be hacked to find those
binaries...  and it becomes annoyingly difficult to include useful demos
for qtdemo...

At least that's what I found when I tried to include it a couple years
ago...

-- 
Captain Logic is not steering this tugboat.



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

kdelibs5-dev for powerpc missing

[Brian DeRocher]

Hi,

Kmail persistently crashes on me.  It may be this bug 
https://bugs.kde.org/show_bug.cgi?id=178319

I'm trying to recompile it, but kdelibs5-dev 4.2 for powerpc is missing.  Can 
you upload it along with all other source packages.

thanks,
Brian


-- 
To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#548976: please support non-orphaned ODBC

[Brian Sammon]

Package: libqt4-sql-odbc
Version: 4.5.2-2

as iodbc seems to be orphaned in Debian, please consider providing a qt4-sql 
package for use with unixODBC.
Maybe two qt4-odbc packages, one called
libqt4-sql-iodbc and another called libqt4-sql-unixodbc.



-- 
To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#330094: qt4-dev-tools: should depend on libqt4-dev

[Brian Nelson]

Ken Bloom <[EMAIL PROTECTED]> writes:

> qt4-dev-tools should depend on libqt4-dev rather than simply recommend
> it

Why?  All of the apps in qt4-dev-tools, AFAIK, function properly without
libqt4-dev installed.

-- 
Captain Logic is not steering this tugboat.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#330094: qt4-dev-tools: should depend on libqt4-dev

[Brian Nelson]

Ken Bloom <[EMAIL PROTECTED]> writes:

> Brian Nelson wrote:
>> Ken Bloom <[EMAIL PROTECTED]> writes:
>> 
>> 
>>>qt4-dev-tools should depend on libqt4-dev rather than simply recommend
>>>it
>> 
>> 
>> Why?  All of the apps in qt4-dev-tools, AFAIK, function properly without
>> libqt4-dev installed.
>
> designer-qt4 needs libqt4-dev the first time it runs as a given user in
> order to configure itself properly. Without that, it can't find its
> widgets or templates. You can remove libqt4-dev after that and things
> will still work, but if you remove ~/.config then you'll need libqt4-dev
> so that designer-qt4 can configure itself again.

Ah, I see.  In that case, I think I should just split out designer into
a separate package, and merge libqt4-designer into it.  Then this new
qt4-designer package could depend on libqt4-dev.

-- 
Captain Logic is not steering this tugboat.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#280777: Kopete IRC connection with SSL connection crash

[Brian Beck]

Package: kopete
Version: 3.4.2-3

I hope this is helpful, I noticed that the KCrash handler output is different 
so I thought I would send it in.  If it's unnecessary I apologize.

Steps to reproduce:
1. Create an IRC account in kopete with "Prefer SSL-based connections" 
checked.  (I used the Freenode network, when setting up my account.)
2. Try to connect.  The IRC icon will blink for awhile.
3. After you get tired of watching the IRC icon blink set IRC to offline.  
Kopete will now crash.

If I modify my IRC account by unchecking "Prefer SSL-based connections" I am 
able to connect to the server without incident.

[KCrash handler]
#3  0xb7505288 in KSSL::write () from /usr/lib/libkio.so.4
#4  0xb5d50cac in KSSLSocket::writeBlock () from /usr/lib/kde3/kopete_irc.so
#5  0xb5d4acc0 in KIRC::Message::writeRawMessage ()
   from /usr/lib/kde3/kopete_irc.so
#6  0xb5d4b182 in KIRC::Message::writeMessage ()
   from /usr/lib/kde3/kopete_irc.so
#7  0xb5d4b282 in KIRC::Message::writeMessage ()
   from /usr/lib/kde3/kopete_irc.so
#8  0xb5d3a8ac in KIRC::Engine::writeMessage ()
   from /usr/lib/kde3/kopete_irc.so
#9  0xb5d44731 in KIRC::Engine::quit () from /usr/lib/kde3/kopete_irc.so
#10 0xb5d055d9 in IRCAccount::quit () from /usr/lib/kde3/kopete_irc.so
#11 0xb5d05683 in IRCAccount::disconnect () from /usr/lib/kde3/kopete_irc.so
#12 0xb5cfd04c in IRCAccount::setOnlineStatus ()
   from /usr/lib/kde3/kopete_irc.so
#13 0xb5d199b6 in IRCAccount::qt_invoke () from /usr/lib/kde3/kopete_irc.so
#14 0xb6980c5f in QObject::activate_signal () from /usr/lib/libqt-mt.so.3
#15 0xb7ef2b7a in Kopete::OnlineStatusAction::activated ()
   from /usr/lib/libkopete.so.1
#16 0xb7ef2c40 in Kopete::OnlineStatusAction::slotActivated ()
   from /usr/lib/libkopete.so.1
#17 0xb72d30bb in KAction::slotPopupActivated () from /usr/lib/libkdeui.so.4
#18 0xb72d33dd in KAction::qt_invoke () from /usr/lib/libkdeui.so.4
#19 0xb7eee29c in Kopete::OnlineStatusAction::qt_invoke ()
   from /usr/lib/libkopete.so.1
#20 0xb6980c5f in QObject::activate_signal () from /usr/lib/libqt-mt.so.3
#21 0xb6d115a5 in QSignal::signal () from /usr/lib/libqt-mt.so.3
#22 0xb699eb30 in QSignal::activate () from /usr/lib/libqt-mt.so.3
#23 0xb6aa88f7 in QPopupMenu::mouseReleaseEvent () from /usr/lib/libqt-mt.so.3
#24 0xb728f930 in KPopupMenu::mouseReleaseEvent () from /usr/lib/libkdeui.so.4
#25 0xb69bbfb6 in QWidget::event () from /usr/lib/libqt-mt.so.3
#26 0xb6916778 in QApplication::internalNotify () from /usr/lib/libqt-mt.so.3
#27 0xb6916d4b in QApplication::notify () from /usr/lib/libqt-mt.so.3
#28 0xb708f9fc in KApplication::notify () from /usr/lib/libkdecore.so.4
#29 0xb68a66d3 in QApplication::sendSpontaneousEvent ()
   from /usr/lib/libqt-mt.so.3
#30 0xb68a18f8 in QETWidget::translateMouseEvent () 
from /usr/lib/libqt-mt.so.3
#31 0xb689fe3e in QApplication::x11ProcessEvent () from /usr/lib/libqt-mt.so.3
#32 0xb68b995c in QEventLoop::processEvents () from /usr/lib/libqt-mt.so.3
#33 0xb692eea2 in QEventLoop::enterLoop () from /usr/lib/libqt-mt.so.3
#34 0xb692edcb in QEventLoop::exec () from /usr/lib/libqt-mt.so.3
#35 0xb6915305 in QApplication::exec () from /usr/lib/libqt-mt.so.3
#36 0x080773e6 in ?? ()
#37 0xbf8d1de0 in ?? ()
#38 0xbf8d1f14 in ?? ()
#39 0xbf8d1f28 in ?? ()
#40 0x080773c6 in ?? ()
#41 0x000d in ?? ()
#42 0xb7faed60 in ?? () from /usr/lib/libktexteditor.so.0
#43 0xb7fd5ff4 in ?? () from /lib/ld-linux.so.2
#44 0xb62baff4 in ?? () from /lib/tls/libc.so.6
#45 0xb62bd1e0 in __malloc_initialize_hook () from /lib/tls/libc.so.6
#46 0x000c in ?? ()
#47 0xbf8d1df8 in ?? ()
#48 0xb61f0c4c in malloc () from /lib/tls/libc.so.6
#49 0xb619cec0 in __libc_start_main () from /lib/tls/libc.so.6
#50 0x0806dc41 in ?? ()


Depends: kdelibs4c2 (>= 4:3.4.2-1), libart-2.0-2 (>= 2.3.16), libaudio2, libc6 
(>= 2.3.5-1), libfam0, libfontconfig1 (>= 2.3.0), libfreetype6 (>= 2.1.5-1), 
libgadu3 (>= 1:1.5+20050808+1.6rc3), libgcc1 (>= 1:4.0.1), libice6 | xlibs 
(>> 4.1.0), libidn11 (>= 0.5.18), libjpeg62, libpcre3 (>= 4.5), libpng12-0 
(>= 1.2.8rel), libqt3-mt (>= 3:3.3.5), libsm6 | xlibs (>> 4.1.0), libstdc++6 
(>= 4.0.1-9), libx11-6 | xlibs (>> 4.1.0), libxcursor1 (>> 1.1.2), libxext6 | 
xlibs (>> 4.1.0), libxft2 (>> 2.1.1), libxi6 | xlibs (>> 4.1.0), 
libxinerama1, libxml2 (>= 2.6.21), libxrandr2 | xlibs (>> 4.3.0), libxrender1 
(>> 1:0.9.0-1), libxslt1.1 (>= 1.1.15), libxt6 | xlibs (>> 4.1.0), zlib1g (>= 
1:1.2.1)

$ uname -a
Linux legionWorld 2.6.12-1-386 #1 Tue Sep 27 12:41:08 JST 2005 i686 GNU/Linux

$ ls -l /lib/libc.so.6
lrwxrwxrwx  1 root root 13 Sep 22 04:05 /lib/libc.so.6 -> libc-2.3.5.so

Thanks.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#331036: kmail: Tray to window restoration sets focus on different desktop

[Brian Sipos]

Package: kmail
Version: 4:3.4.2-2
Severity: normal

When kmail is minimized to the 'notification area' in Gnome on a particular
virtual desktop (the original desktop), the view is changed to a different
virtual desktop, and the 'notification area' icon is clicked to restore the
kmail window, kmail is restored to the original desktop and focus is changed
to that desktop.

The window should be restored to whatever the current virtual desktop happens
to be and no desktop focus change should take place.


-- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.10
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)

Versions of packages kmail depends on:
ii  kdebase-kio-plugins   4:3.4.2-3  core I/O slaves for KDE
ii  kdelibs4c24:3.4.2-4  core libraries for all KDE applica
ii  kdepim-kio-plugins4:3.4.2-2  KDE pim I/O Slaves
ii  libart-2.0-2  2.3.17-1   Library of functions for 2D graphi
ii  libaudio2 1.7-3  The Network Audio System (NAS). (s
ii  libc6 2.3.5-6GNU C Library: Shared libraries an
ii  libfontconfig12.3.2-1generic font configuration library
ii  libfreetype6  2.1.10-1   FreeType 2 font engine, shared lib
ii  libgcc1   1:4.0.1-9  GCC support library
ii  libice6   6.8.2.dfsg.1-7 Inter-Client Exchange library
ii  libidn11  0.5.18-1   GNU libidn library, implementation
ii  libjpeg62 6b-10  The Independent JPEG Group's JPEG 
ii  libkcal2b 4:3.4.2-2  KDE calendaring library
ii  libkdepim1a   4:3.4.2-2  KDE PIM library
ii  libkleopatra0a4:3.4.2-2  KDE GnuPG interface libraries
ii  libkmime2 4:3.4.2-2  KDE MIME interface library
ii  libkpimidentities14:3.4.2-2  KDE PIM user identity information 
ii  libksieve04:3.4.2-2  KDE mail/news message filtering li
ii  libmimelib1c2 4:3.4.2-2  KDE mime library
ii  libpng12-01.2.8rel-4 PNG library - runtime
ii  libqt3-mt 3:3.3.5-1  Qt GUI Library (Threaded runtime v
ii  libsm66.8.2.dfsg.1-7 X Window System Session Management
ii  libstdc++64.0.1-9The GNU Standard C++ Library v3
ii  libx11-6  6.8.2.dfsg.1-7 X Window System protocol client li
ii  libxcursor1   1.1.3-1X cursor management library
ii  libxext6  6.8.2.dfsg.1-7 X Window System miscellaneous exte
ii  libxft2   2.1.7-1FreeType-based font drawing librar
ii  libxi66.8.2.dfsg.1-7 X Window System Input extension li
ii  libxinerama1  6.8.2.dfsg.1-7 X Window System multi-head display
ii  libxrandr26.8.2.dfsg.1-7 X Window System Resize, Rotate and
ii  libxrender1   1:0.9.0-2  X Rendering Extension client libra
ii  libxt66.8.2.dfsg.1-7 X Toolkit Intrinsics
ii  perl  5.8.7-5Larry Wall's Practical Extraction 
ii  xlibs 6.8.2.dfsg.1-7 X Window System client libraries m
ii  zlib1g1:1.2.3-4  compression library - runtime

Versions of packages kmail recommends:
ii  kdebase-kio-plugins   4:3.4.2-3  core I/O slaves for KDE
ii  kdepim-kio-plugins4:3.4.2-2  KDE pim I/O Slaves
ii  procmail  3.22-11Versatile e-mail processor

-- no debconf information


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#336492: libqt4-gui: conflicts with libqt4-core 4.0.1-2

[Brian Nelson]

Jean-Christophe Dubacq <[EMAIL PROTECTED]> writes:

> When upgrading from 4.0.1-2 to 4.0.1-4, libqt4-gui tries to overwrite
> libqjpeg.so:
> dpkg: error processing
> /var/cache/apt/archives/libqt4-gui_4.0.1-4_i386.deb (--unpack):
>  trying to overwrite `/usr/lib/qt4/plugins/imageformats/libqjpeg.so', which 
> is also in package libqt4-core
> dpkg-deb: subprocess paste killed by signal (Broken pipe)
>
> The answer is simple: It should have some more headers:
> Replaces: libqt4-core (<<4.0.1-4)
> Conflicts: libqt4-core (<<4.0.1-4)

Thanks.  It should just replace libqt4-core though, and not conflict
with it.

-- 
Captain Logic is not steering this tugboat.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#337297: libqt4-dev: -lXxf86vm missing with qt3support for qmake

[Brian Nelson]

José Ramón Álvarez Sánchez <[EMAIL PROTECTED]> writes:

> After trying to build a external program that uses libxxf86vm
> and with a line QT += qt3support in the .pro file for qmake,
> i got linking errors about symbols XF86VidModeQueryVersion and
> XF86VidModeGetModeLine not defined.
>
> Just added "-lXxf86vm" to the line QMAKE_PRL_LIBS
> in file /usr/lib/libQt3Support.prl  and it worked OK,
> although I am not sure if that is the best way it must be corrected
> (or, is libxxf86vm not considered system library?)

AFAIK, Qt4 doesn't have native support for Xxf86vm, so if you use it,
you're responsible for modifying the build system of your application to
link against it.

For example, using qmake, you'd add something like this to your .pro:

LIBS += -lXxf86vm

Or am I misunderstanding this bug report?

-- 
Captain Logic is not steering this tugboat.

Bug#337847: qt4-designer: I see nothing in the menu

[Brian Nelson]

jjluza <[EMAIL PROTECTED]> writes:

> Le Dimanche 6 Novembre 2005 23:59, cedric a écrit :
>> I had the same problem. but after restarting my computer, all works well.
>> And I can't reproduce it.
>
> For my part, I still get the problem after restarting.

Does removing ~/.designer and restarting fix it?

-- 
Captain Logic is not steering this tugboat.

Bug#338380: qt4-designer: please provide a pure debug build of designer

[Brian Nelson]

Andreas Pakulat <[EMAIL PROTECTED]> writes:

> today I was struck by designer and release vs. debug built of Qt4. I
> have a Custom Widget which is visible in designer when I have no logic
> in it. But it completely "breaks" designer if I put the real code in it,
> the solution to this is that the widget uses a shared library. This
> library is built in debug mode (the custom widget is built with release
> mode) and that was the cause. Now I have to built the widget in release
> mode, because Qt4 was built using release or the combined release+debug
> building mode (in which case, designer gets built in release mode).
> Designer can thus only load widgets which are built in the same mode as
> designer itself and as you can see all libraries these widgets depend
> upon need to use release built too. 
>
> So the conclusion is: Please provide 2 designer packages, one using
> release built and one using a debug-only built of Qt4. I know this means
> building Qt4 twice for each update, but it's not possible to debug any
> custom widget in the current setup due to the missing debug symbols.

I'd rather wait and see what kind of improvements go into the designer
in Qt4.1.  The current version has proven to be very buggy, and this
seems like something that should definitely be supported by a single
designer binary.

> The above might also explain some of the problems reported in 325782
>
> If you feel this is more a wishlist than a minor bug, please downgrade,
> but I thought as it breaks debug-building custom widgets its a minor
> bug not a wishlist.

I'd say it's a "normal" bug.  Minor is more for spelling errors and
stuff.

-- 
Captain Logic is not steering this tugboat.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#339357: libqt4-dev: QMenu::exec() returns wrong value

[Brian Nelson]

Artur Wiebe <[EMAIL PROTECTED]> writes:

> When opening a popup menu with QMenu::exec() and clicking left outside
> of the menu exec() returns not 0 as I would expect it. If this is not a
> bug, sry for wasting your time.

It does sound like a bug.  Did you search the bug reports on
http://www.trolltech.com/developer/tasktracker.html for anything
relevant?  I just looked but couldn't find anything.

-- 
Captain Logic is not steering this tugboat.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#337764: libqt4-debug: Building apps in debug mode breaks image loading

[Brian Nelson]

Andreas Pakulat <[EMAIL PROTECTED]> writes:

> Building QT4 apps using
>
> CONFIG += debug
>
> breaks the loading of any icons in the application. Remove debug and
> everythings fine. This not only happens to the icons created for that
> app, but also for the icons in standard dialog, like the QFileDialog.

Hmm, I can't reproduce this.  Can you test some of the examples from Qt
and see if you can reproduce it with any of those.  The stuff under
mainwindows/ seem like good candidates.

You can find the examples in the Qt source, or in the new qt4-doc
package I'm about to upload (4.0.1-5).

-- 
Captain Logic is not steering this tugboat.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#337764: libqt4-debug: Building apps in debug mode breaks image loading

[Brian Nelson]

tag 337764 confirmed
thanks

Andreas Pakulat <[EMAIL PROTECTED]> writes:

> On 18.11.05 10:20:54, Brian Nelson wrote:
>> Andreas Pakulat <[EMAIL PROTECTED]> writes:
>> 
>> > Building QT4 apps using
>> >
>> > CONFIG += debug
>> >
>> > breaks the loading of any icons in the application. Remove debug and
>> > everythings fine. This not only happens to the icons created for that
>> > app, but also for the icons in standard dialog, like the QFileDialog.
>> 
>> Hmm, I can't reproduce this.  Can you test some of the examples from Qt
>> and see if you can reproduce it with any of those.  The stuff under
>> mainwindows/ seem like good candidates.
>
> Sure, just take the "application" example, add
>
> CONFIG += debug
>
> and run qmake-qt4 && make. The program won't display any icon, except the
> one for paste. This is with an up to date sid and I'm having Qt3 as
> default Qt (i.e. qmake == qmake-qt3).
>
> QTDIR is set to point to /usr/share/qt3, but changing to /usr/share/qt4
> doesn't help either.

OK, I see it now.  Strange I couldn't reproduce it the first time I
tried.

I wonder if this is a consequence of this bug:
http://www.trolltech.com/developer/tasktracker.html?method=entry&id=86441

Examining the strace, it does look like it's loading both the debug and
non-debug versions of the plugins.

-- 
Captain Logic is not steering this tugboat.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#327359: qmake generates invalid -L linker Option

[Brian Nelson]

tag 327359 upstream
thanks

This actual bug is filed as
http://www.trolltech.com/developer/tasktracker.html?method=entry&id=87775
upstream, scheduled to be fixed in 4.1.1.

-- 
Captain Logic is not steering this tugboat.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#339969: Installing Krita puts four documentation links in KHelpCenter

[Brian Beck]

Package: krita
Version: 1.4.2-2

I installed krita via aptitude, and I recently noticed that in the KHelpCenter 
there are four locations for the krita documentation.  Two in "Application 
Manuals" -> Graphics and two in "Application Manuals" -> Office.  I suspect 
that there ought to be only one in each category (Graphics and Office).

uname -a
Linux legionWorld 2.6.12-1-386 #1 Tue Sep 27 12:41:08 JST 2005 i686 GNU/Linux

ls -l /lib/libc.so.6
lrwxrwxrwx 1 root root 13 2005-11-19 16:43 /lib/libc.so.6 -> libc-2.3.5.so

If I can provide more information that will help please ask.

Thanks.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#339357: libqt4-dev: a simple test

[Brian Nelson]

Artur Wiebe <[EMAIL PROTECTED]> writes:

> No, I could not find anything. I've just played around with this: A
> QTreeWidget with setContextMenuPolicy(Qt::CustomContextMenu) and the signal
> customContextMenuRequested(const QPoint&) connected to a my_slot(const
> QPoint&) which looks like
>
> void myView::my_slot(const QPoint& pos)
> {
> QMenu popup(this);
>
> popup.addAction("test 1");
> popup.addAction("test 2");
> popup.addAction("test 3");
>
> //QAction* retval = popup.exec(m_tw->mapToGlobal(pos));
> QAction* retval = popup.exec(QCursor::pos());
> qDebug() << retval;
> }
>
> This works. The commented out version does not. It opens a popup but
> clicking left outside the menu returns not 0.

Well, I just looked over the QMenu code to try to see what could be
happening here, but nothing obvious stood out.

Would you like to file a bug upstream and see if the trolls can figure
it out?

-- 
Captain Logic is not steering this tugboat.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#341658: libqt4-core: QBitArray operator{&,|,^}(...) missing from libQtCore.so

[Brian Nelson]

tag 341658 fixed-upstream
thanks

Torsten Marek <[EMAIL PROTECTED]> writes:

> The functions
>
> QBitArray operator&(const QBitArray &, const QBitArray &);
> QBitArray operator|(const QBitArray &, const QBitArray &);
> QBitArray operator^(const QBitArray &, const QBitArray &);
>
> are missing from libQtCore.so.

This is upstream bug scheduled to be fixed in 4.1.0:

  http://www.trolltech.com/developer/tasktracker.html?method=entry&id=83512

-- 
Captain Logic is not steering this tugboat.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: QT4: need confirmation on debug version

[Brian Nelson]

Christian Welzel <[EMAIL PROTECTED]> writes:

> I'm currently developing an application on qt4 and wondered why qt doesnt
> complain about not existing signals/slots during connect().
> After trying to compile the stuff myself i discovered this:
[...]
> As you can see the build process does not compile the debug version on its own
> but only links the objects of the release-version into the debug-version.
>
> Because release version is compliled with QT_NO_DEBUG even the debug version
> does not through errors.
>
> I used the 4.0.1-5 patch on qt-x11 4.0.1 from trolltech website.
>
> Please confirm this behavoir and fix it in the next upload.

I think this is due to this upstream bug:

  http://www.trolltech.com/developer/tasktracker.html?method=entry&id=90812

It's scheduled to be fixed in 4.1.1.

-- 
Captain Logic is not steering this tugboat.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#342658: libqt4-core: Locking Issue?

[Brian Nelson]

Ian Wienand <[EMAIL PROTECTED]> writes:

[...]
> (gdb) back
> #0  0x21363d81 in __pthread_sigsuspend (set=0x6fbf7270)
> at ../linuxthreads/sysdeps/unix/sysv/linux/ia64/pt-sigsuspend.c:32
> #1  0x21362380 in __pthread_wait_for_restart_signal 
> (self=0x2137edc8) at pthread.c:1216
> #2  0x2135d050 in __pthread_cond_wait (cond=0x60004338, 
> mutex=0x600042e0) at restart.h:34
> #3  0x2103f400 in QReadWriteLock::lockForWrite () from 
> /usr/lib/libQtCore.so.4
> #4  0x211d0340 in qt_addObject () from /usr/lib/libQtCore.so.4
> #5  0x211d0e50 in QObject::QObject () from /usr/lib/libQtCore.so.4
> #6  0x21184e20 in QFactoryLoader::QFactoryLoader () from 
> /usr/lib/libQtCore.so.4
> #7  0x2120b670 in QTextDecoder::~QTextDecoder () from 
> /usr/lib/libQtCore.so.4
> #8  0x21210ef0 in QTextCodec::codecForName () from 
> /usr/lib/libQtCore.so.4
> #9  0x2120c160 in QTextEncoder::fromUnicode () from 
> /usr/lib/libQtCore.so.4
> #10 0x2120efd0 in QTextCodec::codecForLocale () from 
> /usr/lib/libQtCore.so.4
> #11 0x210b30d0 in QString::toLocal8Bit () from /usr/lib/libQtCore.so.4
> #12 0x210e04b0 in locale_encode () from /usr/lib/libQtCore.so.4
> #13 0x210e06f0 in QFile::encodeName () from /usr/lib/libQtCore.so.4
> #14 0x210f8e20 in QFileEngineHandler::QFileEngineHandler () from 
> /usr/lib/libQtCore.so.4
> #15 0x210e5460 in QFile::open () from /usr/lib/libQtCore.so.4
> #16 0x40001070 in main ()
>
> It seems that lock in qt_addObject has already been taken by
> something.  Has anything changed in this area recently?

In the code?  No, not by me.  I don't see any reason why that lock would
be taken indefinitely anyway.

> BTW, using the libQtCore_debug.so.4 library didn't give me any useful
> line numbers or other debugging info.  If you load it into gdb and run
> 'info functions' all the symbols are defined as non-debugging symbols.
> This may have something to do with the way it was built.

That's bug #341807.

-- 
Captain Logic is not steering this tugboat.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#343190: libqt4-dev: qmake adding unneeded libraries to the linker command line

[Brian Nelson]

Benjamin Mesing <[EMAIL PROTECTED]> writes:

> to reduce dependencies between packages, it is suggested to add only
> neccessary libraries as linker arguments. Steve Langasek explained the
> problems in [1]. Now qmake pulls in loads of unneeded dependencies,
> including e.g. libfreetype (-lfreetype). 

Any idea of how to fix it?

-- 
Captain Logic is not steering this tugboat.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#343739: qt4-dev-tools: menu item for assistant

[Brian Nelson]

Petr Mensik <[EMAIL PROTECTED]> writes:

> Is there any reason why Qt Assistant does have any Menuitem in some
> debian Xserver menus? In KDE menu i didnt found any of Qt Designer, Qt
> Linguist, or Qt Assistant. That doest bother me much, as its under
> Debian subtree. Still i think it might be there, because who else will
> try using Qt language than KDE programmer? 

Plenty, I'd guess, including myself...

> But maybe against debian policies, dunno. But what i look for is
> Assistant menuitem somewhere.  Its simple program, but its helpful
> when you doing something with Qt.  But i did not found other way of
> starting assistant, than from commandline. I think some menuitem would
> not do something bad, so why would not add Qt Assistant to help
> section or applications/programming?  Not everyone know he has
> installed it when he cant find it in menu. Will it be there, or there
> are reasons why its not already there?

There is a menu entry for it, under Apps/Tools.  This might not be the
most logical place for it, but the Debian menu hierarchy is a total mess
anyway.  I don't think Apps/Programming is appropriate since you can't
actually use it for programming, unlike the other stuff that appears
under there.  I'm open to other suggestions though.

-- 
Captain Logic is not steering this tugboat.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#345388: libqt4-dev: qmake adds -L/usr/lib

[Brian Nelson]

Marc Glisse <[EMAIL PROTECTED]> writes:

> qmake adds -L/usr/lib to (the beginning of) LIBS. This is unneeded, and
> actually causes many problems.

I agree it's unneeded, but what problems does it cause?

-- 
Captain Logic is not steering this tugboat.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#345801: main window empty

[Brian Nelson]

[EMAIL PROTECTED] writes:

> when I start the qt4 designer, I get the full workbench, everything
> seems ok. But when starting a new form and choosing a "main window",
> the created window is just empty. Regarding to the docs it should have
> the usual decoration such as a menu bar. It should be possible to
> create a missing menu bar through the context menu. 
>
> But there is neither a menu bar, nor does the context menu allow
> this. The other decorations are missing as well. 
>
> Any idea?

Does the new version, 4.1.0, which just hit unstable today, look better
to you?

-- 
Captain Logic is not steering this tugboat.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#345801: main window empty

[Brian Nelson]

Hadmut Danisch <[EMAIL PROTECTED]> writes:

> On Thu, Jan 05, 2006 at 06:08:00PM -0500, Brian Nelson wrote:
>> 
>> Does the new version, 4.1.0, which just hit unstable today, look better
>> to you?
>
>
> Yup, now there is a menu bar. 
>
> But shouldn't there be a status bar at the bottom as well? 

There is--it's just empty.  It appears in the .ui though.

-- 
Captain Logic is not steering this tugboat.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#342658: libqt4-core: Locking Issue?

[Brian Nelson]

Ian Wienand <[EMAIL PROTECTED]> writes:

> On Mon, Dec 12, 2005 at 01:39:13PM +0200, Brian Nelson wrote:
>> Ian Wienand <[EMAIL PROTECTED]> writes:
>> 
>> [...]
>> > (gdb) back
>> > #0  0x21363d81 in __pthread_sigsuspend (set=0x6fbf7270)
>> > at ../linuxthreads/sysdeps/unix/sysv/linux/ia64/pt-sigsuspend.c:32
>> > #1  0x21362380 in __pthread_wait_for_restart_signal 
>> > (self=0x2137edc8) at pthread.c:1216
>> > #2  0x2135d050 in __pthread_cond_wait (cond=0x60004338, 
>> > mutex=0x600042e0) at restart.h:34
>> > #3  0x2103f400 in QReadWriteLock::lockForWrite () from 
>> > /usr/lib/libQtCore.so.4
>> > #4  0x211d0340 in qt_addObject () from /usr/lib/libQtCore.so.4
>> > #5  0x211d0e50 in QObject::QObject () from /usr/lib/libQtCore.so.4
>> > #6  0x21184e20 in QFactoryLoader::QFactoryLoader () from 
>> > /usr/lib/libQtCore.so.4
>> > #7  0x2120b670 in QTextDecoder::~QTextDecoder () from 
>> > /usr/lib/libQtCore.so.4
>> > #8  0x21210ef0 in QTextCodec::codecForName () from 
>> > /usr/lib/libQtCore.so.4
>> > #9  0x2120c160 in QTextEncoder::fromUnicode () from 
>> > /usr/lib/libQtCore.so.4
>> > #10 0x2120efd0 in QTextCodec::codecForLocale () from 
>> > /usr/lib/libQtCore.so.4
>> > #11 0x210b30d0 in QString::toLocal8Bit () from 
>> > /usr/lib/libQtCore.so.4
>> > #12 0x210e04b0 in locale_encode () from /usr/lib/libQtCore.so.4
>> > #13 0x210e06f0 in QFile::encodeName () from /usr/lib/libQtCore.so.4
>> > #14 0x210f8e20 in QFileEngineHandler::QFileEngineHandler () from 
>> > /usr/lib/libQtCore.so.4
>> > #15 0x210e5460 in QFile::open () from /usr/lib/libQtCore.so.4
>> > #16 0x40001070 in main ()
>> >
>> > It seems that lock in qt_addObject has already been taken by
>> > something.  Has anything changed in this area recently?
>> 
>> In the code?  No, not by me.  I don't see any reason why that lock would
>> be taken indefinitely anyway.
>
> I ruled out a few things, namely it seems to happen with both
> LinuxThreads and NPTL, so it seems unlikely that the threading
> library/kernel is at fault.
>
> The changes-4.0.1 file says that support has been added for SGI Altix,
> which means someone must have been interested in getting it working on
> IA64?  Any idea who that person might be?

No, no idea.

Does this still happen with Qt 4.1.0?

-- 
Captain Logic is not steering this tugboat.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#347251: libqt4-gui: Most icons don't load for some reason (and crash from time to time)

[Brian Nelson]

severity 347251 important
thanks

"Nach M. S." <[EMAIL PROTECTED]> writes:

> Since the upgrade to Qt 4.1.0, I noticed icons pretty much everywhere
> have disappeared. For example, load up Designer, aside from the Window
> icon, icons everywhere else such as tool bar or for the item pains and
> menus have all disappeared.

Try removing libqt4-debug and see if the problem still occurs.  If that
fixes it, then it's due to some upstream problems with the build system
and plugins loading.  See, for example, #337764, #337847, #341807 ...

> In my own apps I noticed the same thing, icons vanished everywhere but
> from the Window icons. Also in my own apps, I've gotten this:
>
> Program received signal SIGSEGV, Segmentation fault.
> [Switching to Thread -1220241728 (LWP 22025)]
> 0xb7bb8893 in QImage::scanLine () from /usr/lib/libQtGui.so.4

Hmm, I haven't seen this before.  I wonder if it's related, or if it's
yet another bug...

-- 
Captain Logic is not steering this tugboat.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Crash when loading application image

[Brian Nelson]

Benjamin Mesing <[EMAIL PROTECTED]> writes:

>> I've received a bug report [1] against packagesearch crashing on arch
>> i386 (it was reported to work fine on amd64). The backtrace [2]
>> indicates that the problem lies within the QT library, and the fact that
>> with Qt 4.0.1 everything worked fine seem to support this thesis.
>> Therefore I would like to reassign the bug to libqt4-core. 
>> 
>> [1] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=346565
>> [2] 
>> #0  0xb76c2883 in QImage::scanLine () from /usr/lib/libQtGui.so.4
>> #1  0xb76ab2d9 in QWidgetPrivate::setWindowIcon_sys () from 
>> /usr/lib/libQtGui.so.4
>> #2  0xb7681a8e in QWidget::setWindowIcon () from /usr/lib/libQtGui.so.4
>> #3  0x08070ea0 in Ui_PackageSearch::setupUi ()
>> #4  0x0806ae01 in PackageSearchImpl::PackageSearchImpl ()
>> #5  0x0806222e in main ()
>
> Taking a look into it, I seems very likely, that the following code is
> causing the crash:
> 
> PackageSearch->setWindowIcon(QIcon(QString::fromUtf8("../icons/packagesearch.png")));
> and it crashes only if packagesearch.png is not available in ../icons/.
> This used to work fine in earlier versions of QT (up to 4.0.1) and
> probably should not lead to a crash. The line was created in from a ui
> file, and I had it there to have a nice symbol when editing the file in
> the designer. Later in the code I am setting the icon to something that
> works for the normal installation. 
> So a quick fix for packagesearch is, to simply remove the reference to
> the icon from the ui file. However I think it is still no the
> appropriate thing to crash (and it seems not to do so on amd64). Perhaps
> a bug report to Trolltech is due?

Looks like it's already been filed:

http://www.trolltech.com/developer/tasktracker.html?method=entry&id=95955

-- 
Captain Logic is not steering this tugboat.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#346586: libqt4-dev: linker error: /usr/lib/libQtSql.so: undefined reference to

[Brian Nelson]

Benjamin Mesing <[EMAIL PROTECTED]> writes:

>> /usr/lib/libQtSql.so: undefined reference to [EMAIL PROTECTED]'
>> /usr/lib/libQtSql.so: undefined reference to [EMAIL PROTECTED]'
>> [...]
> An update of libmysqlclient14(-dev) to version 4.1.15-1 solved the
> issue. 
> So maybe libqt4-dev should depend on libmysqlclient14(-dev) >= 4.1.15-1?
>
> Btw. I have a wishlist bug to build against libmysqlclient15 instead of
> 14, any chance you will switch over at one point? Couldn't find a
> relevant wishlist bug for your packages.

Yeah, I plan to do so for the next upload.

-- 
Captain Logic is not steering this tugboat.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#346605: libqt4-dev: linker error cannot find -lQt3Support_debug when compiling in debug mode

[Brian Nelson]

Benjamin Mesing <[EMAIL PROTECTED]> writes:

> An update of libqt4-debug to 4.1 (which was still 4.0.1 before) fixed
> this issue and brought it down to bug 346586.
> So probably libqt4-dev 4.1 should conflict with libqt4-debug <= 4.0.1?

Conflicts with earlier versions are frowned upon in policy (7.3).  I
think the right thing to do would be to split all of the _debug.so
symlinks into a separate libqt4-debug-dev package.  The current scheme
of lumping them all into libqt4-dev and not explicitly depending on
libqt4-debug is broken, I think.

Then, if you're going to build and link against the debug libs, you just
declare a build dependency on libqt4-debug-dev.

-- 
Captain Logic is not steering this tugboat.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#335831: qt4-x11 4.1.0-1 still FTBFS in mips/mipsel

[Brian Nelson]

Isaac Clerencia <[EMAIL PROTECTED]> writes:

> It looks like the problem still exists, I'm attaching a fixed qatomic32.s 
> created by Ryan Murray.

Eh, did no one see this message?

http://lists.debian.org/debian-mips/2006/01/msg00021.html

-- 
Captain Logic is not steering this tugboat.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#347360: qt4-x11: FTBFS in ARM (no matching function for call to 'getXDefault(const char [4], const char [6], qreal*))

[Brian Nelson]

Isaac Clerencia <[EMAIL PROTECTED]> writes:

> qt4 is FTBFS'ing in ARM with the following problem:
> kernel/qapplication_x11.cpp: In function 'void
>   qt_init(QApplicationPrivate*, int, Display*, Qt::HANDLE, Qt::HANDLE)':
> kernel/qapplication_x11.cpp:1547: error: no matching function for call
>   to 'getXDefault(const char [4], const char [6], qreal*)'
> kernel/qapplication_x11.cpp:1174: note: candidates are: void
>   getXDefault(const char*, const char*, int*)
> kernel/qapplication_x11.cpp:1185: note: void
>   getXDefault(const char*, const char*, double*)
> kernel/qapplication_x11.cpp:1196: note: void
>   getXDefault(const char*, const char*, bool*)
> kernel/qapplication_x11.cpp: At global scope:
> kernel/qapplication_x11.cpp:1185: warning: 'void getXDefault(const
>   char*, const char*, double*)' defined but not used
>
> the problem is that in ARM qreal is defined as float and not as double,

Do you know if there's a good reason for this?

> I guess the easiest fix would be to add another implementation of
> getXDefault with prototype: void getXDefault(const char*, const char*,
> float*) similar to the double one in kernel/qapplication_x11.cpp.

I already applied a different fix in svn--I changed the qreal
declaration to double instead of float, which is how it was declared
before 4.1.0.  If you think this will be problematic for some reason,
let me know.

-- 
Captain Logic is not steering this tugboat.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: libqt4-dev and pkg-config

[Brian Nelson]

Cédric <[EMAIL PROTECTED]> writes:

> I tryed to use 'pkg-config --cflags QtCore' to compile a little program with 
> qt4, but this give me that line :
> -DQT_SHARED -I/usr/include/qt4
>
> Because in QT4, all headers are splited in subdirectory according to their 
> module, if I use this include directory, I should include for example 
>  or  instead of  which looks like the 
> mandatory include according to the trolltech documentation on QT4.
>
> So, I think all *.pc files provided by the package libqt4-dev are wrong and 
> should return -I/usr/include/qt4/

You're probably right.  Feel free to file a report to Trolltech and send
me a patch if you want it fixed in the Debian packages.  :)

-- 
Captain Logic is not steering this tugboat.

Bug#347782: Add sqlite support to Qt-4.1.0

[Brian Nelson]

Thorvald Natvig <[EMAIL PROTECTED]> writes:

> Could you add sqlite3 support to Qt? The source is included in the Qt
> distribution, so it's just a matter of adding -qt-sql-sqlite to the
> configure string.

Already added to 4.1.0-2, which is currently sitting in the NEW queue
and should become available shortly.

-- 
Captain Logic is not steering this tugboat.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#348092: libqt4-gui: Built to not support gifs (as per build default)

[Brian Nelson]

severity 348092 wishlist
thanks

Russell Jones <[EMAIL PROTECTED]> writes:

> Package: libqt4-gui
> Version: 4.0.1-5
> Severity: important

Woah, hey now, don't you think that severity is a little over-inflated?

> I understand that by default the Qt configure script disables gif
> support. It can be re-enabled in debian/rules by supplying -qt-gif
> as a parameter to ./configure.  I have not tested this thoroughly, but I
> cannot find any mention of gif in the debian directory, so I assume this
> has not been changed. I have had a problem when a Qt4 application I
> compiled tried to load a gif, but due to the nature of the application
> it's hard to test whether there's a problem or not.

Hmm, well I don't any reason to not enable it, so I'll include it in the
next upload.

-- 
Captain Logic is not steering this tugboat.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#349141: /usr/lib/libQtSql.so: undefined reference to `mysql ...

[Brian Nelson]

[EMAIL PROTECTED] writes:

> Package: libqt4-sql
> Version: 4.1.0-3
>
>
> Hi, when i try to use this lib in my software I get:
>
> linux>make
> g++  -o prova main.o   -L/usr/lib -lQtSql -lQtGui -lQtCore -lpthread
> /usr/lib/libQtSql.so: undefined reference to [EMAIL PROTECTED]'
> /usr/lib/libQtSql.so: undefined reference to [EMAIL PROTECTED]'
> /usr/lib/libQtSql.so: undefined reference to [EMAIL PROTECTED]'
> /usr/lib/libQtSql.so: undefined reference to [EMAIL PROTECTED]'
> /usr/lib/libQtSql.so: undefined reference to [EMAIL PROTECTED]'
> ...
> ...
> ...
> /usr/lib/libQtSql.so: undefined reference to [EMAIL PROTECTED]'
> /usr/lib/libQtSql.so: undefined reference to [EMAIL PROTECTED]'
> /usr/lib/libQtSql.so: undefined reference to [EMAIL PROTECTED]'
> collect2: ld returned 1 exit status
> make: *** [prova] Error 1

Does upgrading libmysqlclient15 to 5.0.18-7 fix it?  I think this might
be related to this bug:

http://bugs.debian.org/348854

-- 
Captain Logic is not steering this tugboat.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#349438: libqt4-dev: Need symlink to /usr/bin/rcc

[Brian Nelson]

Steve Halasz <[EMAIL PROTECTED]> writes:

> To build qgis from CVS (--with-qtdir=/usr/share/qt4) I need a symlink
> from /usr/share/qt4/bin/rcc to /usr/bin/rcc. I could work around this
> in qgis, but it seems reasonable to have the link there.

Sure, I'll add it in the next upload.

-- 
Captain Logic is not steering this tugboat.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#354266: libqt4-gui: Error loading MNG file(s)

[Brian Nelson]

Anthony Awtrey <[EMAIL PROTECTED]> writes:

> I was just about to report this as a bug in the packaging of the qt4-x11
> files, so I'll just append your report. We saw that when we linked to
> the debug libs we got animated gif and mng support, but with the
> optimized libs they didn't work. There are some missing files missing
> from the libqt4-gui package's install file:
>
>
> In the qt4-x11/debian/libqt4-gui.install file:
>
> usr/lib/libQtGui.so.*
> usr/lib/libQtOpenGL.so.*
> usr/bin/qtconfig-qt4
> usr/lib/qt4/plugins/imageformats/libqjpeg.so
> usr/lib/qt4/plugins/imageformats/libqgif.so   <-- Add this
> usr/lib/qt4/plugins/imageformats/libqmng.so   <-- Add this
> usr/lib/qt4/plugins/codecs/*codecs.so

Thanks, I'll be sure to add these to the package in the next release.

> It takes a long time to rebuild (like over an hour on our 2.5GHz box
> with a gig of RAM), but when it is done you should have debs that will work.
>
> I think the problem exists because it is easy for the debug files to get
> masked in as "*debug.so", but the non-debug files must be specified by
> name or they are not included in the package.

Indeed.  Unfortunately, there's no way with dh_install AFAIK to use
wildcards with a not clause, e.g. *.so files that don't end in
_debug.so.

-- 
Captain Logic is not steering this tugboat.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Problem using qt4 in unstable

[Brian Nelson]

Thomas Weber <[EMAIL PROTECTED]> writes:

[...]
> The relevant error message from config.log:
> ==
> /usr/bin/ld: cannot find -lQtAssistantClient
> ==
>
> Indeed, the qt4 packages don't contain this lib, whereas a local qt4
> build has them.
>
> I have installed every package with qt4 in its name. Any help would be
> appreciated.

You're correct that that library is not included in any Qt4 package.
It's probably a bug...

-- 
Captain Logic is not steering this tugboat.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Problem using qt4 in unstable

[Brian Nelson]

Thomas Weber <[EMAIL PROTECTED]> writes:

> Am Dienstag, den 07.03.2006, 18:21 -0800 schrieb Brian Nelson:
>> Thomas Weber <[EMAIL PROTECTED]> writes:
>> 
>> [...]
>> > The relevant error message from config.log:
>> > ==
>> > /usr/bin/ld: cannot find -lQtAssistantClient
>> > ==
>> >
>> > Indeed, the qt4 packages don't contain this lib, whereas a local qt4
>> > build has them.
>> >
>> > I have installed every package with qt4 in its name. Any help would be
>> > appreciated.
>> 
>> You're correct that that library is not included in any Qt4 package.
>> It's probably a bug...
>
> Should I file a bugreport or what is the preferred way to continue from
> here? 

Yes, please file a bug report to make sure I don't forget about it.

-- 
Captain Logic is not steering this tugboat.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: qmake-qt4 CONFIG has debug by default

[Brian Nelson]

Arnaud Cornet <[EMAIL PROTECTED]> writes:

> Since libqt4-dev 4.1.1-1, /usr/share/qt4/mkspecs/qconfig.pri adds
> "debug" to CONFIG by default.
>
> Is this expected behavior ?

Well, it's what upstream does by default.  Whether it's intentional or
correct, I'm not so sure...

-- 
Captain Logic is not steering this tugboat.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#357136: libqt4-dev sould depend on libqt4-debug-dev

[Brian Nelson]

"Jeremiah Savage" <[EMAIL PROTECTED]> writes:

> Package: libqt4-dev
> Version: 4.1.1-1
>
> When building the tutorial "Hello World" example, I got the following error:
> 
> $ qmake-qt4 -project
> $ qmake-qt4
> $ make
> g++ -c -pipe -g -Wall -W -D_REENTRANT  -DQT_GUI_LIB -DQT_CORE_LIB
> -I/usr/share/qt4/mkspecs/linux-g++ -I. -I/usr/include/qt4/QtCore
> -I/usr/include/qt4/QtGui -I/usr/include/qt4 -I. -I. -I. -o hello.o
> hello.cc
> g++  -o kdeprog hello.o-L/usr/lib -lQtGui_debug -lQtCore_debug -lpthread
> /usr/bin/ld: cannot find -lQtGui_debug
> collect2: ld returned 1 exit status
> make: *** [kdeprog] Error 1
> 
>
> Installing libqt4-debug-dev allowed the program to compile without error:

Well, OK, but then the correct fix would be to make qmake not link
against the debug libs by default.  Having libqt4-dev depend on
libqt4-debug-dev doesn't make any sense.

-- 
Captain Logic is not steering this tugboat.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#358972: Fixed in 4.1.2?

[Brian Nelson]

Hi Benjamin,

Both of these bugs you reported were regressions in 4.1.1.  Can you test
the 4.1.2 packages and see if either of these bugs are fixed there?

-- 
Captain Logic is not steering this tugboat.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#357136: debug building by default

[Brian Nelson]

This is scheduled to be fixed upstream for 4.2.0:

http://www.trolltech.com/developer/task-tracker/index_html?method=entry&id=111573

(assuming the debug default on linux is a bug)

-- 
Captain Logic is not steering this tugboat.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#368883: qt4-x11: FTBFS on alpha

[Brian Nelson]

Filipus Klutiero <[EMAIL PROTECTED]> writes:

> gcc ICEd when attempting to build qt4-x11 on alpha on 2006-05-14. I
> don't know what's the issue and what could fix. However, 4.1.2-1 built
> and the changes to -2 seem minimal, so it should be easy to check
> whether there was a gcc regression or the qt4-x11 changes triggered the
> FTBFS and need
> a workaround.

Isn't an ICE always a compiler bug?  In any case, nothing in the Qt code
changed between -1 and -2, so it's certainly a GCC regression.

-- 
Captain Logic is not steering this tugboat.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#369835: qt4-x11: uninstallable with nvidia-glx-dev

[Brian Nelson]

severity 369835 normal
thanks

[Problems involving non-free packages are not RC bugs]

Mathieu Malaterre <[EMAIL PROTECTED]> writes:

> Package: qt4-x11
> Severity: grave
> Justification: renders package unusable
>
>
> I simply cannot install qt4-x11, therefore I cannot get the
> libQtAssistantClient libraries (Bug #355902).

Why would this be qt4's problem?  I'd think nvidia-glx-dev would be the
one that needs fixing.

-- 
Captain Logic is not steering this tugboat.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Bug#368883: qt4-x11: FTBFS on alpha

[Brian Nelson]

Pierre Habouzit <[EMAIL PROTECTED]> writes:

> tag 368883 + pending
> thanks
>
> Le Sam 3 Juin 2006 10:57, Samuel Thibault a écrit :
>> Hi,
>>
>> Could this be fixed any time soon?  qt4-x11 is currently blocking no
>> less than 83 packages.
>>
>> Samuel
>
> that one is quite annoying.
>
> Brian: will you have time to fix that soon (like in less than a couple 
> of days ?) else I'll do an upload just to fix the alpha FTBFS now that 
> there is a patch.
>
> If I've no news from you, I suppose I'll do an upload on sunday.

I should be able to do it today (Saturday). If not, go ahead and upload
on Sunday.

-- 
Captain Logic is not steering this tugboat.

Bug#377236: kate: treats non-unique paths as unique files

[Brian Sipos]

Package: kate
Version: 4:3.5.3-2
Severity: normal

The file loading will treat semantically-identical but string-differing 
paths as unique files. For example:
/path/to/file
/path/to//file
are treated as two different files, even though they really aren't.

This causes problems when using the internal file-searching tool when 
the "Folder" entry contains a trailing slash. The file-opening code 
should probably trim out unnecessary path elements before checking that 
the file isn't already open.

-- System Information:
Debian Release: testing/unstable
  APT prefers testing
  APT policy: (500, 'testing'), (500, 'stable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.16-2-686
Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1)

Versions of packages kate depends on:
ii  kdelibs4c2a 4:3.5.3-1core libraries and binaries for al
ii  libacl1 2.2.39-1 Access control list shared library
ii  libart-2.0-22.3.17-1 Library of functions for 2D graphi
ii  libattr12.4.32-1 Extended attribute shared library
ii  libaudio2   1.7-9The Network Audio System (NAS). (s
ii  libc6   2.3.6-15 GNU C Library: Shared libraries
ii  libfontconfig1  2.3.2-7  generic font configuration library
ii  libfreetype62.2.1-2  FreeType 2 font engine, shared lib
ii  libgamin0 [libfam0] 0.1.7-3  Client library for the gamin file 
ii  libgcc1 1:4.1.1-5GCC support library
ii  libice6 1:1.0.0-3X11 Inter-Client Exchange library
ii  libidn110.6.3-1  GNU libidn library, implementation
ii  libjpeg62   6b-13The Independent JPEG Group's JPEG 
ii  libpng12-0  1.2.8rel-5.1 PNG library - runtime
ii  libqt3-mt   3:3.3.6-2Qt GUI Library (Threaded runtime v
ii  libsm6  1:1.0.0-4X11 Session Management library
ii  libstdc++6  4.1.1-5  The GNU Standard C++ Library v3
ii  libx11-62:1.0.0-7X11 client-side library
ii  libxcursor1 1.1.5.2-5X cursor management library
ii  libxext61:1.0.0-4X11 miscellaneous extension librar
ii  libxft2 2.1.8.2-8FreeType-based font drawing librar
ii  libxi6  1:1.0.0-5X11 Input extension library
ii  libxinerama11:1.0.1-4X11 Xinerama extension library
ii  libxrandr2  2:1.1.0.2-4  X11 RandR extension library
ii  libxrender1 1:0.9.0.2-4  X Rendering Extension client libra
ii  libxt6  1:1.0.0-5X11 toolkit intrinsics library
ii  zlib1g  1:1.2.3-11   compression library - runtime

Versions of packages kate recommends:
pn  kregexpeditor  (no description available)

-- no debconf information


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#365348: kmail: IMAP-SSL fails with "connection to server is broken"

[Brian White]

Okay...  It is reproducable because I just ran in to the same problem.

Package: kmail
Version: 4:3.3.2-3

This is from the "stable" distribution.

I believe my problem to be that it is not honoring the "port" setting. 
I have it set to "993" for IMAPS but tcpdump shows that connection 
attempts are still going to port 143 (imap2).


  Brian
 ( [EMAIL PROTECTED] )

---
Treat someone as they are and they will remain that way.  Treat someone
 as they can be and they will become that way.


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#380253: libqt4-gui conflicts with libqt4-designer

[Brian Nelson]

Michael Bann <[EMAIL PROTECTED]> writes:

> The exact error message is the following:
> Preparing to replace libqt4-gui 4.1.3-3 (using
> .../libqt4-gui_4.1.4-1_i386.deb) ...
> Unpacking replacement libqt4-gui ...
> dpkg: error processing
> /var/cache/apt/archives/libqt4-gui_4.1.4-1_i386.deb (--unpack):
>  trying to overwrite `/usr/lib/libQtDesigner.so.4', which is also in
> package libqt4-designer
> Errors were encountered while processing:
>  /var/cache/apt/archives/libqt4-gui_4.1.4-1_i386.deb
> E: Sub-process /usr/bin/dpkg returned an error code (1)
>
> This problem happened while trying to update the system using apt-get
> upgrade.
>
> The incorrect behavior is that it didn't upgrade, and is blocking any
> further apt-get upgrades as it won't upgrade without this package
> successfully installed first.

Just purge libqt4-designer.  That package was merged into qt4-designer
back in version 4.0.1-3.

-- 
Captain Logic is not steering this tugboat.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#382238: libqt4-sql not built against sqlite3

[Brian Nelson]

Martin Gruner <[EMAIL PROTECTED]> writes:

> Please make libqt4-sql support sqlite3. Currently it only links against 
> sqlite2. Trying to use the sqlite3 backend does not work. Thanks.
>
> ldd libQtSql.so | grep sqlite
> libsqlite.so.0 => /usr/lib/libsqlite.so.0 (0xa7cd3000)  #sqlite2

sqlite3 support is supposed to be statically linked--upstream actually
ships a copy of the source.  Any idea why it doesn't work?

-- 
Captain Logic is not steering this tugboat.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#327618: dependency on libpq-dev for libqt4-dev

[Brian Nelson]

Margarita Manterola <[EMAIL PROTECTED]> writes:

> Hi!
>
> Georg Baum reopened bug 327618, since apparently libqt4-dev 
> stopped having the needed dependency on libpq-dev.
>
> I've been checking the packages on snapshot.debian.org, and found out that
> the dependency was dropped on 4.1.0-2, the relevant changelog entry seems
> to be:
>
>   * debian/control: added explicit dependencies for libqt4-dev on the
> Source-Version packages libqt4-core, libqt4-gui, libqt4-sql, and
> libqt4-qt3support.  These dependencies were accidentally dropped in
> the last version.  Also removed some unneeded dependencies.
>
> Apparently, libpq-dev for libqt4-dev was removed as unneeded dep.
>
> Brian, is this the case?  If so, could please explain it to Georg?

FWIW, I don't remember what I was thinking.  Removing that depending may
have been a mistake.  *shrug*

-- 
Captain Logic is not steering this tugboat.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#386460: Building a package with libqt4-dev on arm times out

[Brian Nelson]

Tobias Toedter <[EMAIL PROTECTED]> writes:

> Package: libqt4-dev
> Version: 4.1.4-1.1
> Severity: normal
>
> Hi,
>
> my package qbrew FTBFS on arm, it links against libqt4. The reason for the 
> build failure is a time out while running this command:
> /usr/bin/uic-qt4 src/calcconfig.ui -o build/ui_calcconfig.h
>
> I've talked to the arm porters on IRC, and they suggested that it might be 
> related to libqt4 not being compiled with -DQT_QLOCALE_USES_FCVT, which was 
> a needed fix for libqt3 on arm. From the changelog:
>
> qt-x11-free (3:3.3.3-4.1) unstable; urgency=high 
>* On arm-linux, configure using -DQT_QLOCALE_USES_FCVT. Seems to be a
>  known issue, mentioned in the 3.3.2 release notes, but nowhere in
>  the 3.3.3 sources. Great! Thanks to Paul Brook and Jan Niehusmann for
>  the investigations. Closes: #270202.
>
> The build log of my package qbrew can be found here:
> 
>
> Are you aware of this problem? Is anyone trying to compile qt4 
> with -DQT_QLOCALE_USES_FCVT on arm, to see if the problem can be solved?

Not me...  Did you ask the arm porters to try it?

-- 
Captain Logic is not steering this tugboat.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#386460: Building a package with libqt4-dev on arm times out

[Brian Nelson]

Tobias Toedter <[EMAIL PROTECTED]> writes:

> On Friday 06 October 2006 04:01, Brian Nelson wrote:
>> Tobias Toedter <[EMAIL PROTECTED]> writes:
>> > Are you aware of this problem? Is anyone trying to compile qt4
>> > with -DQT_QLOCALE_USES_FCVT on arm, to see if the problem can be
>> > solved?
>>
>> Not me...  Did you ask the arm porters to try it?
>
> Hi,
>
> the arm porters did not offer to try this. However, they offered to provide 
> a chroot on an arm machine to me, so that I could recompile libqt with that 
> flag and see if the error persists or not.
>
> On IRC, we concluded that it might be best to first check with you guys 
> whether you know about this issue or not, so that the compilation of libqt 
> might be avoided.
>
> How should we go on from here? Do you have access to an arm machine to 
> recompile libqt? Note that I'm not a DD.

I just have access to whatever arm machines are available to developers,
but building on one of those would require getting all of the build
dependencies installed, and then (presumably) getting the built packages
installed to test the qbrew build.

However, the QT_QLOCALE_USES_FCVT macro still exists in the Qt4 source.
My understanding is that it would still be valid to use, so I can try
adding it in the next Qt4 upload and see what happens.  With a little
luck it'll fix the problem.

-- 
Captain Logic is not steering this tugboat.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#392451: Undefined symbol in konqueror modules

[Brian Bassett]

Christopher:

Thanks for the information.  Restarting my X session did indeed fix the 
issue.  Please feel free to close this bug report.


Brian

Quoting Christopher Martin <[EMAIL PROTECTED]>:


tags 392451 unreproducible
severity 392451 important
stop


These types of errors are occassionally encountered when upgrading. A
restart of X (or the whole system) should almost certainly fix it
(we've had such reports in the past, and they always go away). Rather
than block the release, I'm downgrading this bug's severity for the
moment, but if I'm wrong and a reset doesn't make the problem go away,
let us know.

Cheers,
Christopher Martin

Brian Bassett wrote:

Package: konqueror
Version: 4:3.5.5-1
Severity: grave

Upon starting konqueror as a file manager (using the "Home (Personal
Files)" link on the K menu, popups indicate there were errors loading
modules used by Konqueror, all reporting that the
_ZN6KParts16BrowserExtension12itemsRemovedERK8QPtrListI9KFileItemE
symbol is undefined in /usr/lib/kde3/konq_{icon,list}view.so.
Konqueror then starts up in the Photobook mode, with no images
displayed (since I don't have any in my home directory).

The specific error messages that pop up are:








--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#392902: qmake-qt4 no longer escapes quotes for -Dfoo="value" on gcc command line

[Brian Nelson]

"Steve M. Robbins" <[EMAIL PROTECTED]> writes:

> Package: libqt4-dev
> Version: 4.2.0-1
> Severity: grave
>
> Hello,
>
> Ipe uses qmake to build, with a "config.pri" file that contains the
> following:
>
>   IPEDOCDIR  = $${IPEPREFIX}/share/doc/ipe/doc
>
> Back in July, the generated Makefile resulted in
>
>   -DIPEDOCDIR=\"/usr/share/doc/ipe/doc\"
>
> passed to the g++ command line -- see the ipe buildd logs.  Now it is
> passing
>
>   -DIPEDOCDIR="/usr/share/doc/ipe/doc"
>
> which, not surprisingly, causes a syntax error and the build fails.

I suppose that's a side-effect of this qmake change:

2.10a -

   support for spaces in filenames.


> Can you put it back the way it was?

Err, well I can file a bug upstream.  I suppose it's possible to just
completely revert qmake to the version shipped in 4.1.4, but I don't
want to do that unless absolutely necessary.

-- 
Captain Logic is not steering this tugboat.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#392902: qmake-qt4 no longer escapes quotes for -Dfoo="value" on gcc command line

[Brian Nelson]

severity 392902 important
thanks

I'm downgrading this since a workaround has been presented, and I don't
think it's affecting the build of many packages.

Perhaps this should be closed since it sounds like a permanent change
from upstream?

-- 
Captain Logic is not steering this tugboat.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#391902: qt4-x11: [m68k] missing inotify defines

[Brian Nelson]

Roman Zippel <[EMAIL PROTECTED]> writes:

> Hi,
>
> Is there any progress here?
> If there is anything I can do to help, please ask, but please don't ignore 
> this bug...
> Thanks.

Sorry, I was just dealing with RC bugs first...

To what file should those lines be added?  There isn't a buildd log for
m68k on buildd.d.o, so I can't see the actual error.

-- 
Captain Logic is not steering this tugboat.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#392558: libqt4-dev: Missing dependency for libsqlite-dev

[Brian Nelson]

Peter Schwindt <[EMAIL PROTECTED]> writes:

> Package: libqt4-dev
> Version: 4.2.0-1
> Severity: normal
>
> libqt4-dev needs libsqlite-dev in order to compile some software (f.e.
> psi)
>
> Dependency is missing, I had to reinstall by hand.

Err, which libsqlite-dev package (libsqlite0-dev or libsqlite3-dev)?
libsqlite-dev is a virtual package that those two provide.

-- 
Captain Logic is not steering this tugboat.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#391996: kmix: global shortcut problem confirmed

[Brian Kimball]

Package: kmix
Version: 4:3.5.5-1
Followup-For: Bug #391996

Hi, same problem here.  Downgrading kmix also fixed problem.

-- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (990, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.18
Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1)

Versions of packages kmix depends on:
ii  kdelibs4c2a4:3.5.5a.dfsg.1-1 core libraries and binaries for al
ii  libasound2 1.0.13-1  ALSA library
ii  libc6  2.3.6.ds1-6   GNU C Library: Shared libraries
ii  libgcc11:4.1.1-16GCC support library
ii  libstdc++6 4.1.1-16  The GNU Standard C++ Library v3

kmix recommends no packages.

-- no debconf information


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#394953: qt4-x11_4.2.1-1(hppa/unstable): FTBFS: missing defines

[Brian Nelson]

[EMAIL PROTECTED] writes:
[...]
> A full build log can be found at:
> http://buildd.debian.org/build.php?arch=hppa&pkg=qt4-x11&ver=4.2.1-1
>
> How about using the system inotify syscall numbers and such instead of
> private ones???

Ehhh, I don't know why they do that.  Maybe so that they can verify that
those arches work first?  Who knows...

-- 
Captain Logic is not steering this tugboat.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#396034: closed by Brian Nelson <[EMAIL PROTECTED]> (Re: Bug#396034: qmake-qt4: CONFIG+=opengl doesn't add QtOpenGL include path or link -lQtOpenGL)

[Brian Nelson]

Tim Day <[EMAIL PROTECTED]> writes:

> On Mon, 2006-10-30 at 19:48 -0800, Debian Bug Tracking System wrote:
>> Brian Nelson wrote:
>> > Use "QT += opengl", not CONFIG.  See the Qt4 qmake documentation for
>> > more info.
>
> Thanks for the tip; QT += opengl (instead of CONFIG += opengl) does
> exactly what I was expecting.
>
> However, the current etch docs may be out of date.  My
>   file:///usr/share/qt4/doc/html/qmake-variable-reference.html
> makes no mention at all of a QT variable, and lists opengl along
> with all the others used via CONFIG.

I think that's been updated in the 4.2 docs.  However, you still have
this:

file:///usr/share/qt4/doc/html/qmake-project-files.html#declaring-qt-libraries

-- 
Captain Logic is not steering this tugboat.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: anyone give me some advice about split scim-bridge

[Brian Nelson]

ZhengPeng Hou <[EMAIL PROTECTED]> writes:

> hi all,
>I've already splited scim-brodge into scom-brodge-agent
>scim-brodge-client-gtk, scim-bridge-client-qt, and scim-bridge(a
>dumy package for upgrade), but now the upstream has added qt4
>support, so shall I split it into five? likde -agent, -client-gtk
>-client-qt3, and -client-qt4? is this scheme ok?

Is there any significant difference between the two to give a reason to
justify having both?  If not, I'd just pick the best supported one and
just package that.

-- 
Captain Logic is not steering this tugboat.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#437354: libqt4-dev: Put qmake into its own package

[Brian Nelson]

Jan Michael Alonzo <[EMAIL PROTECTED]> writes:

> Hi! I'm currently trying to build gnome + webkit without distro-specific
> packages. But for this I need "qmake" which is part of libqt4-dev. The problem
> is libqt4 is built with -glib enabled. Is there a reaason why qt4-dev needs
> glib? And also, if it's really needed can we separate qmake because it's used
> not only by QT4 apps but also third party applications like WebKit.
>
> I'm just not sure how coupled qmake is to the whole QT libs, if not, it would 
> be
> nice if qmake is in its own package.

The reason I originally included qmake in the -dev package was that I
was under the impression that no 3rd party apps used it.  It's certainly
possible to package it separately, though I'd be surprised anything
using it wasn't closely tied to Qt.

I don't understand what you mean about building with "distro-specific
packages" or why glib support would be a problem though.

-- 
Captain Logic is not steering this tugboat.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#274676: kleopatra: New version uninstallable

[Brian Pack]

Package: kleopatra
Version: 4:3.3.0-2
Severity: grave
Justification: renders package unusable

When running synaptic, I get the following error when trying to upgrade

kleopatra:
 Depends: gnupg2 but it is not installable
 Depends: gnupg-agent but it is not installable

-- System Information:
Debian Release: 3.1
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing')
Architecture: i386 (i686)
Kernel: Linux 2.6.8-20040927
Locale: LANG=C, LC_CTYPE=C

Versions of packages kleopatra depends on:
ii  kdelibs44:3.3.0-2KDE core libraries
ii  libc6   2.3.2.ds1-17 GNU C Library: Shared libraries an
ii  libgcc1 1:3.4.2-2GCC support library
ii  libkleopatra0   4:3.3.0-2KDE GnuPG interface libraries
ii  libqt3c102-mt   3:3.3.3-4.1  Qt GUI Library (Threaded runtime v
ii  libstdc++5  1:3.3.4-13   The GNU Standard C++ Library v3

-- no debconf information

Bug#238227: kdesktop: drop shadow on desktop icon text is incomplete

[Brian McGroarty]

Package: kdesktop
Version: 4:3.2.1-1
Severity: minor

This will seem unbelievably petty, but once you notice it it may bug
you. :)

The drop shadow on fonts used on the desktop is incomplete. It seems
that text is rendered in 8 positions around the original position to
create a broad outline, but not in the center of the original
position. The result is that if you use a font that has a 1-pixel
period, it makes a hollow box for the shadow instead of a solid
box. There is no way that shadow would match the period.

-- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.4.22
Locale: LANG=C, LC_CTYPE=C

Versions of packages kdesktop depends on:
ii  kdebase-bin 4:3.2.1-1KDE Base (binaries)
ii  kdelibs44:3.2.1-1KDE core libraries
ii  libart-2.0-22.3.16-1 Library of functions for 2D graphi
ii  libc6   2.3.2.ds1-11 GNU C Library: Shared libraries an
ii  libfam0c102 2.7.0-5  client library to control the FAM 
ii  libgcc1 1:3.3.3-2GCC support library
ii  libice6 4.3.0-5  Inter-Client Exchange library
ii  libjpeg62   6b-9 The Independent JPEG Group's JPEG 
ii  libkonq44:3.2.1-1Core libraries for KDE's file mana
ii  libpcre34.5-1.1  Perl 5 Compatible Regular Expressi
ii  libpng12-0  1.2.5.0-5PNG library - runtime
ii  libqt3c102-mt   3:3.2.3-2Qt GUI Library (Threaded runtime v
ii  libsm6  4.3.0-5  X Window System Session Management
ii  libstdc++5  1:3.3.3-2The GNU Standard C++ Library v3
ii  libx11-64.3.0-5  X Window System protocol client li
ii  libxext64.3.0-5  X Window System miscellaneous exte
ii  libxrender1 0.8.3-7  X Rendering Extension client libra
ii  xlibs   4.3.0-5  X Window System client libraries m
ii  zlib1g  1:1.2.1-5compression library - runtime

-- no debconf information

Bug#245645: /usr/bin/konqueror: konqueror renders a page a second time, far right of original

[Brian McGroarty]

Package: konqueror
Version: 4:3.2.2-1
Severity: normal
File: /usr/bin/konqueror

Konqeror renders a second copy of this page about fifty screens to the
right of the first copy:

http://www.empiricalsoup.org/

This does not seem to happen with other browsers.

-- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.4.22
Locale: LANG=C, LC_CTYPE=C

Versions of packages konqueror depends on:
ii  kcontrol4:3.2.2-1KDE Control Center
ii  kdebase-kio-plugins 4:3.2.2-1KDE I/O Slaves
ii  kdelibs44:3.2.2-2KDE core libraries
ii  kdesktop4:3.2.2-1KDE Desktop
ii  kfind   4:3.2.2-1KDE File Find Utility
ii  libart-2.0-22.3.16-5 Library of functions for 2D graphi
ii  libc6   2.3.2.ds1-12 GNU C Library: Shared libraries an
ii  libfam0c102 2.7.0-5  client library to control the FAM 
hi  libgcc1 1:3.3.3-6GCC support library
ii  libice6 4.3.0-7  Inter-Client Exchange library
ii  libjpeg62   6b-9 The Independent JPEG Group's JPEG 
ii  libkonq44:3.2.2-1Core libraries for KDE's file mana
ii  libpcre34.5-1.1  Perl 5 Compatible Regular Expressi
ii  libpng12-0  1.2.5.0-5PNG library - runtime
ii  libqt3c102-mt   3:3.2.3-2Qt GUI Library (Threaded runtime v
ii  libsm6  4.3.0-7  X Window System Session Management
ii  libstdc++5  1:3.3.3-6The GNU Standard C++ Library v3
ii  libx11-64.3.0-7  X Window System protocol client li
ii  libxext64.3.0-7  X Window System miscellaneous exte
ii  libxrender1 0.8.3-7  X Rendering Extension client libra
ii  xlibs   4.3.0-7  X Window System client libraries m
ii  zlib1g  1:1.2.1-5compression library - runtime

-- no debconf information

Re: Bug#250452: Out of date Qt makes Indian languages totally unusable in Qt/KDE apps

[Brian Nelson]

"Jaldhar H. Vyas" <[EMAIL PROTECTED]> writes:

> [I'm Cc'ing the qt-kde packagers list for more input.]
>
> On Sun, 30 May 2004, Brian Nelson wrote:
>
>> I've been maintaining my own Qt packages for some time at
>> http://bignachos.com/~nelson/debian .  I've been considering hijacking
>> the Debian Qt packages because I use Qt extensively at work and am
>> extremely dissatisfied with the packages currently in Debian.
>
> Go for it.  I sympathize with madkiss if he is busy but he should have the
> decency to ask for help instead of leaving such an important package to
> stagnate like this.

Well, my packages are not yet fit for upload yet.  They contain some
drastic changes that really need to be tested more.

-- 
You win again, gravity!

Re: Bug#250452: Out of date Qt makes Indian languages totally unusable in Qt/KDE apps

[Brian Nelson]

"Jaldhar H. Vyas" <[EMAIL PROTECTED]> writes:

> On Sun, 30 May 2004, Brian Nelson wrote:
>
>> Well, my packages are not yet fit for upload yet.  They contain some
>> drastic changes that really need to be tested more.
>>
>
> Would it be possible to upload the latest version at least?  That would
> solve my problem.

Not by me, at least for 9 days or so.  I didn't bring my private key
with me to Debconf4.  I can look at the packages you made though and let
you know if they look OK to NMU.

-- 
You win again, gravity!

Re: QT needs new maintainer(s), or at least an NMU

[Brian Nelson]

Martin Loschwitz <[EMAIL PROTECTED]> writes:

> However, as already said -- I would love to see people help me; I am
> thinking of doing a Qt 3.2.x upload to fix at least one of the two 
> outstanding release critical bugs. Additionally, re-enabling STL is
> something one might take into consideration.

I (and many others) consider the lack of STL support to be
release-critical as well.

-- 
You win again, gravity!

Re: Announcing the availability of first Qt 3.3 packages

[Brian Nelson]

Martin Loschwitz <[EMAIL PROTECTED]> writes:

> Developers, please test these packages heavily and report anything you see --
> whether the packages work fine, whether they fix bugs you reported before, and
> of course whether they rise new bugs. There are some minor things on my TODO; 
> if these packages turn out to be okay, I will fix the mentioned minor bugs 
> and 
> upload 3.3.2-1 to the official unstable archive as soon as the 
> -0pre1-packages 
> made it into experimental.

For one, they're missing the qaccessible.h header.  It appears to
missing from the 3.2.3 packages as well.

-- 
You win again, gravity!

Re: Announcing the availability of first Qt 3.3 packages

[Brian Nelson]

Christopher Martin <[EMAIL PROTECTED]> writes:

> On June 13, 2004 12:44, Brian Nelson wrote:
>> For one, they're missing the qaccessible.h header.  It appears to
>> missing from the 3.2.3 packages as well.
>
> Martin, there seem to be a few other bugs open regarding missing files. 
> qvfbhdr.h is missing - #182366. tabwidget.png should also allegedly exist 
> - #195189. And someone raised a question over the location of headers 
> under /u/i/qt3, that I'm not qualified to answer fully, but thought I'd 
> mention - please see #226990. There are yet more reports on missing 
> headers, but these are the ones that are still relevant, from what I can 
> tell.

IMO, the reason for the missing files is the ridiculous number of
superfluous packages Qt has been split into.  Is it really necessary to
have libqt3-mt-dev, libqt3-headers, libqt3-compat-headers,
qt3-dev-tools, qt3-designer, qt3-apps-dev, qt3-linguist, qt3-assistant,
qt3-qtconfig, qt3-dev-tools-embedded, qt3-dev-tools-compat, etc. (I
think I even left some out!) in separate packages?  Just a single -dev
package seems sufficient to me.

It makes me wonder what kind of a bribe it took to get this past the
ftp-masters.

-- 
You win again, gravity!

Re: Announcing the availability of first Qt 3.3 packages

[Brian Nelson]

Dominique Devriese <[EMAIL PROTECTED]> writes:

> Brian Nelson writes:
>
>> Christopher Martin <[EMAIL PROTECTED]> writes:
>>> On June 13, 2004 12:44, Brian Nelson wrote:
>>>> For one, they're missing the qaccessible.h header.  It appears to
>>>> missing from the 3.2.3 packages as well.
>>>
>>> Martin, there seem to be a few other bugs open regarding missing
>>> files. qvfbhdr.h is missing - #182366. tabwidget.png should also
>>> allegedly exist
>>> - #195189. And someone raised a question over the location of
>>>   #headers
>>> under /u/i/qt3, that I'm not qualified to answer fully, but thought
>>> I'd mention - please see #226990. There are yet more reports on
>>> missing headers, but these are the ones that are still relevant,
>>> from what I can tell.
>
>> IMO, the reason for the missing files is the ridiculous number of
>> superfluous packages Qt has been split into.  Is it really necessary
>> to have libqt3-mt-dev, libqt3-headers, libqt3-compat-headers,
>> qt3-dev-tools, qt3-designer, qt3-apps-dev, qt3-linguist,
>> qt3-assistant, qt3-qtconfig, qt3-dev-tools-embedded,
>> qt3-dev-tools-compat, etc. (I think I even left some out!) in
>> separate packages?  Just a single -dev package seems sufficient to
>> me.
>
>> It makes me wonder what kind of a bribe it took to get this past the
>> ftp-masters.
>
> Are you sure you know what you're talking about ?  I can think of
> a lot of situations in which those tools are used in various different
> combinations, so that it really is a good idea to have them in
> separate packages.

Huh?  That's absolutely no reason to put a bunch of small binaries in
separate packages.  You gain nothing except unnecessary complexity.

Also, you must only be talking about qt3-assistant, qt3-qtconfig,
qt3-linguist, and qt3-designer.  What you've said doesn't apply to
headers, and who the hell knows what the difference between
qt3-dev-tools, qt3-apps-dev, etc. is anyway?

-- 
You win again, gravity!

Re: Announcing the availability of first Qt 3.3 packages

[Brian Nelson]

Dominique Devriese <[EMAIL PROTECTED]> writes:

> Brian Nelson writes:
>
>>>> IMO, the reason for the missing files is the ridiculous number of
>>>> superfluous packages Qt has been split into.  Is it really
>>>> necessary to have libqt3-mt-dev, libqt3-headers,
>>>> libqt3-compat-headers, qt3-dev-tools, qt3-designer, qt3-apps-dev,
>>>> qt3-linguist, qt3-assistant, qt3-qtconfig, qt3-dev-tools-embedded,
>>>> qt3-dev-tools-compat, etc. (I think I even left some out!) in
>>>> separate packages?  Just a single -dev package seems sufficient to
>>>> me.
>>>
>>>> It makes me wonder what kind of a bribe it took to get this past
>>>> the ftp-masters.
>>>
>>> Are you sure you know what you're talking about ?  I can think of a
>>> lot of situations in which those tools are used in various
>>> different combinations, so that it really is a good idea to have
>>> them in separate packages.
>
>> Huh?  That's absolutely no reason to put a bunch of small binaries
>> in separate packages.  You gain nothing except unnecessary
>> complexity.
>
> Let's see.  I don't consider these small binaries:
> qt3-assistant_3%3a3.3.2-0pre1_i386.deb  229K
> qt3-designer_3%3a3.3.2-0pre1_i386.deb   3,9M
> qt3-linguist_3%3a3.3.2-0pre1_i386.deb   324K
> qt3-dev-tools_3%3a3.3.2-0pre1_i386.deb  1,2M
> qt3-dev-tools-embedded_3%3a3.3.2-0pre1_i386.deb 273K

Well, anything under 500K or so I consider to be quite small.

For a full Qt development environment (i.e. if you're doing Qt
development, you really need all this stuff) with these 3.3.2 packages,
you need:

41k  libqt3-mt-dev_3.3.2-0pre1_i386.deb
2.9M libqt3c102-mt_3.3.2-0pre1_i386.deb
335k libqt3-headers_3.3.2-0pre1_all.deb
71k  libqt3-compat-headers_3.3.2-0pre1_all.deb
1.1M qt3-dev-tools_3.3.2-0pre1_i386.deb
5.2M qt3-doc_3.3.2-0pre1_all.deb
324k qt3-linguist_3.3.2-0pre1_i386.deb
85k  qt3-qtconfig_3.3.2-0pre1_i386.deb
229k qt3-assistant_3.3.2-0pre1_i386.deb
80k  libqt3-i18n_3.3.2-0pre1_all.deb

Total: 11M

I left out qt3-designer because I don't use it, and to show the worst
case scenario for my argument.


A minimal build environment would require:

41k  libqt3-mt-dev_3.3.2-0pre1_i386.deb
2.9M libqt3c102-mt_3.3.2-0pre1_i386.deb
335k libqt3-headers_3.3.2-0pre1_all.deb
71k  libqt3-compat-headers_3.3.2-0pre1_all.deb
1.1M qt3-dev-tools_3.3.2-0pre1_i386.deb

Total: 4.5M


A Non-developer user of the libraries would need:

2.9M libqt3c102-mt_3.3.2-0pre1_i386.deb
85k  qt3-qtconfig_3.3.2-0pre1_i386.deb
80k  libqt3-i18n_3.3.2-0pre1_all.deb

Total: 3.0M


>> Also, you must only be talking about qt3-assistant, qt3-qtconfig,
>> qt3-linguist, and qt3-designer.  
>
>> What you've said doesn't apply to headers, and who the hell knows
>> what the difference between qt3-dev-tools, qt3-apps-dev, etc. is
>> anyway?
>
> I do, and you would too if you had taken the time to look at the
> package descriptions:
>
> qt3-dev-tools: a number of binaries ( note: architecture dependent, so
>you don't want them in an arch independent headers
>package ) for normal development with Qt

Who said we need a arch-indep headers package anyway?  I don't know of
any other library packages in Debian that have one.  Hell, I co-maintain
one, if not the, largest library package in Debian and it doesn't have
headers split into a separate package.

> qt3-apps-dev: stuff you need when you're going to be doing special
>   things with embedding Qt designer and stuff.  Almost
>   noone needs this.

"Special things"?  What the hell are "special things"?  And the package
name in no way suggests any difference from qt3-dev-tools.

> Anyway, if you're going to be making claims like this, it would be a
> lot more useful if you could provide us with a proposal about how you
> would like to see the package split up, so we could consider this in a
> useful manner.

As I said before, I think most stuff should be moved into a single -dev
package.  For a working example, see the packages at
http://bignachos.com/~nelson/debian .

Full a full Qt development environment with these packages:

1.6Mlibqt3-mt-dev_3.3.2-1_i386.deb
3.6Mlibqt3c102-mt_3.3.2-1_i386.deb
17M qt-x11-free_3.3.2.orig.tar.gz
4.8Mqt3-dev-tools_3.3.2-1_i386.deb
6.3Mqt3-doc_3.3.2-1_all.deb

Total: 17M

So there's a 6M difference, 4M of which are due to qt3-designer (I'd
have no problem splitting out qt3-designer).  The rest of the difference
is presumably due to the random stuff missing from Madkiss's packages,
as seen in all the bug reports.


A minimal build environment would require