Bug#903836: pcmanfm-qt: Depends transitively on libgtk2.0-0

[Tsu Jan]

And by "latest version", I meant the latest git version. It'll take a 
while until it's released.


However, even its old versions never depended on GTK but only on GLib.

Bug#903836: pcmanfm-qt: Depends transitively on libgtk2.0-0

[Tsu Jan]

pcmanfm-qt doesn't depend on GTK. It neither depends on libfm anymore -- 
the latest version of libfm-qt is independent of libfm.


pcmanfm-qt uses Qt for its GUI (and some other things) and GLib for its 
file management because GLib is better than Qt when it comes to file 
management. GTK depends on GLib but not conversely. So, pcmanfm-qt has 
nothing to do with GTK, whether directly or indirectly.

Bug#830683: no sound anymore after upgrade to 9.0-1.1

[Tsu Jan]

The same thing happened here. I first downgraded to 8.0-2+b2 and had 
sound again. Then Google lead me to this report and I upgraded 
pulseaudio but, this time, installed pulseaudio-module-udev too, which 
solved the problem.

Therefore, for some reason, pulseaudio-module-udev was quite needed here.
IMO, pulseaudio-module-udev shouldn't be among "Recommends" anymore. 
After all, recommending something means that it is NOT essential to the 
functioning.

Bug#829557: lightdm 1.18.2-1 breaks D-BUS

[Tsu Jan]

Today I encountered the same issue but in a worse way. After the first 
log-in, everything was OK. But once I logged out of LXQt and logged in 
again, not only PCManFM-Qt didn't start, but also it couldn't be started 
in terminal, the notification area didn't run, Pidgin crashed and 
Firefox said "No D-BUS daemon running". I think Firefox's message 
explains everything.


Downgrading to lightdm-1.18.1-1 fixed all issues.

Bug#813647: connman: daemon no longer starts after upgrade

[Tsu Jan]

Isn't connman maintained anymore in Debian ?!

Bug#813580: [Pkg-netfilter-devel] Bug#813580: Bug#813580: No Internet Connection with iptables-1.6.0-2

[Tsu Jan]

On Thu, 4 Feb 2016 08:51:57 +0100 Arturo Borrero Gonzalez 
 wrote:

> Hi Tsu,
>
> I would need you to provide additional info about this bug:
> * connman config
> * connman service systemd detailed log
> * connman own log? (if exists)
> * kernel log (the dmesg one)
> * iptables service systemd detailed log (if exists)
> * iptables ruleset (from iptables-save)
>
> thanks
> --
> Arturo Borrero González
>
>
Hi,

My bad! I had another Debian with network-manager instead of connman. 
Last night I had time to upgrade it and no problem occurred. So, this is 
about connman and not iptables. Apparently, building connman-1.21 
against libxtables11 wasn't enough for it to work with iptables-1.6.0.


Should I write another bug report or you could reassign this one to 
connman (with high severity)?


I haven't changed connman config -- it's the default Debian one.

I saved journalctl output before downgrading connman and iptables and 
there was no iptable line in it but its connman lines were so:


Feb 03 14:20:51 debian systemd[1]: connman.service: Main process exited, 
code=exited, status=1/FAILURE


Feb 03 14:20:51 debian systemd[1]: connman.service: Unit entered failed 
state.


Feb 03 14:20:51 debian systemd[1]: connman.service: Failed with result 
'exit-code'.


Feb 03 14:20:51 debian systemd[1]: connman.service: Service hold-off 
time over, scheduling restart.






Feb 03 14:20:57 debian systemd[1]: connman.service: Failed with result 
'start-limit'.


I've attached my current iptables-save and dmesg logs. Sorry, I couldn't 
find the logs related to that specific boot and I can't upgrade now to 
reproduce the issue because this is my work system.


Thanks, Tsu


-- Logs begin at Thu 2016-02-04 13:43:28 IRST, end at Thu 2016-02-04 14:25:05 
IRST. --
Feb 04 13:43:28 debian kernel: Initializing cgroup subsys cpuset
Feb 04 13:43:28 debian kernel: Initializing cgroup subsys cpu
Feb 04 13:43:28 debian kernel: Initializing cgroup subsys cpuacct
Feb 04 13:43:28 debian kernel: Linux version 4.3.0-1-amd64 
(debian-ker...@lists.debian.org) (gcc version 5.3.1 20160114 (Debian 5.3.1-6) ) 
#1 SMP Debian 4.3.3-7 (2016-01-19)
Feb 04 13:43:28 debian kernel: Command line: 
BOOT_IMAGE=/boot/vmlinuz-4.3.0-1-amd64 root=/dev/sda5
Feb 04 13:43:28 debian kernel: x86/fpu: xstate_offset[2]: 0240, 
xstate_sizes[2]: 0100
Feb 04 13:43:28 debian kernel: x86/fpu: Supporting XSAVE feature 0x01: 'x87 
floating point registers'
Feb 04 13:43:28 debian kernel: x86/fpu: Supporting XSAVE feature 0x02: 'SSE 
registers'
Feb 04 13:43:28 debian kernel: x86/fpu: Supporting XSAVE feature 0x04: 'AVX 
registers'
Feb 04 13:43:28 debian kernel: x86/fpu: Enabled xstate features 0x7, context 
size is 0x340 bytes, using 'standard' format.
Feb 04 13:43:28 debian kernel: x86/fpu: Using 'eager' FPU context switches.
Feb 04 13:43:28 debian kernel: e820: BIOS-provided physical RAM map:
Feb 04 13:43:28 debian kernel: BIOS-e820: [mem 
0x-0x0009c7ff] usable
Feb 04 13:43:28 debian kernel: BIOS-e820: [mem 
0x0009c800-0x0009] reserved
Feb 04 13:43:28 debian kernel: BIOS-e820: [mem 
0x000e-0x000f] reserved
Feb 04 13:43:28 debian kernel: BIOS-e820: [mem 
0x0010-0xb9862fff] usable
Feb 04 13:43:28 debian kernel: BIOS-e820: [mem 
0xb9863000-0xb9869fff] ACPI NVS
Feb 04 13:43:28 debian kernel: BIOS-e820: [mem 
0xb986a000-0xba0e3fff] usable
Feb 04 13:43:28 debian kernel: BIOS-e820: [mem 
0xba0e4000-0xba383fff] reserved
Feb 04 13:43:28 debian kernel: BIOS-e820: [mem 
0xba384000-0xc98c7fff] usable
Feb 04 13:43:28 debian kernel: BIOS-e820: [mem 
0xc98c8000-0xc9ad0fff] reserved
Feb 04 13:43:28 debian kernel: BIOS-e820: [mem 
0xc9ad1000-0xc9e02fff] usable
Feb 04 13:43:28 debian kernel: BIOS-e820: [mem 
0xc9e03000-0xcab07fff] ACPI NVS
Feb 04 13:43:28 debian kernel: BIOS-e820: [mem 
0xcab08000-0xcaffefff] reserved
Feb 04 13:43:28 debian kernel: BIOS-e820: [mem 
0xcafff000-0xcaff] usable
Feb 04 13:43:28 debian kernel: BIOS-e820: [mem 
0xcbc0-0xcfdf] reserved
Feb 04 13:43:28 debian kernel: BIOS-e820: [mem 
0xf800-0xfbff] reserved
Feb 04 13:43:28 debian kernel: BIOS-e820: [mem 
0xfec0-0xfec00fff] reserved
Feb 04 13:43:28 debian kernel: BIOS-e820: [mem 
0xfed0-0xfed03fff] reserved
Feb 04 13:43:28 debian kernel: BIOS-e820: [mem 
0xfed1c000-0xfed1] reserved
Feb 04 13:43:28 debian kernel: BIOS-e820: [mem 
0xfee0-0xfee00fff] reserved
Feb 04 13:43:28 debian kernel: BIOS-e820: [mem 
0xff00-0x] reserved
Feb 04 13:43:28 debian kernel: BIOS-e820: [mem 
0x0001-0x00032f1f] usable
Feb 04 13:43:28 debian kernel: NX (Execute Disable) protection: active
Feb 04 

Bug#813580: [Pkg-netfilter-devel] Bug#813580: Bug#813580: Bug#813580: No Internet Connection with iptables-1.6.0-2

[Tsu Jan]

On Thu, 4 Feb 2016 13:17:15 +0100 Arturo Borrero Gonzalez 
 wrote:

> For the record, the ruleset you shared was generated with a previous
> version of iptables? the file contains:
> Generated by iptables-save v1.4.21 on Thu Feb 4 14:14:09 2016
>
>
Yes! As I said I had to downgrade iptables to have Internet connection 
with connman and I knew the ruleset might be of no use.
I'm pretty sure that this is a connman issue; otherwise it would also 
happen to my other system (with the latest iptables, network-manager and 
KDE but identical to this one in other respects).

Bug#813580: No Internet Connection with iptables-1.6.0-2

[Tsu Jan]

Found Bug#813647 :)

Bug#813647: connman: daemon no longer starts after upgrade

[Tsu Jan]

I encountered the same issue (Bug #813580). After applying these 
patches, connman started to work with iptables-1.6.0-2:


http://git.kernel.org/cgit/network/connman/connman.git/commit/?id=acea08a0e4234a4c1a87bedc087c73ff36de0c7b

http://git.kernel.org/cgit/network/connman/connman.git/commit/?id=754cc1678f5c61501299bbde70a73c58d691609b

Bug#813580: No Internet Connection with iptables-1.6.0-2

[Tsu Jan]

Package: iptables

Version: 1.6.0-2

Yesterday iptables was upgraded from v1.4.21-2+b1 to v1.6.0-2 in Debian 
Testing and today I had no Internet connection (connman.service: Main 
process exited, code=exited, status=1/FAILURE). Fortunately, I had 
another system and could download and then downgrade iptables to 
v1.4.21-2+b1.


System Information:

-- Debian Release: Testing Kernel: 4.3.3-7 libc6: 2.21-7 
(Architecture: amd64)

Bug#813580: [Pkg-netfilter-devel] Bug#813580: No Internet Connection with iptables-1.6.0-2

[Tsu Jan]

On Wed, 3 Feb 2016 13:00:24 +0100 Arturo Borrero Gonzalez 
<arturo.borrero.g...@gmail.com> wrote:

> On 3 February 2016 at 12:13, Tsu Jan <tsujan2...@gmail.com> wrote:
> You were using connman? Or are you using iptables rules directly?
> Which version of connman are you running?
> --
> Arturo Borrero González
>

Yes, I use connman, which was upgraded alongside iptables from 
v1.21-1.2+b1 to v1.21-1.2+b2 (rebuild against libxtables11).


Downgrading connman alone didn't fix the issue, although I had 
libxtables10 too.

Bug#808802: #808802 synaptic: Can't drop privileges for downloading as file '/var/lib/apt/lists/partial/ftp.fr.debian.org_debian_dists_testing_InRelease'

[Tsu Jan]

I was wrong. The problem still persists :(

Bug#808802: #808802 synaptic: Can't drop privileges for downloading as file '/var/lib/apt/lists/partial/ftp.fr.debian.org_debian_dists_testing_InRelease'

[Tsu Jan]

It seems that this issue is fixed by apt-1.2 but it's replaced by 
another message:


The method driver /usr/lib/apt/methods/https could not be found. I hope 
the latter will be fixed by apt-1.2.1, which I haven't tried yet.

Bug#808802: #808802 synaptic: Can't drop privileges for downloading as file '/var/lib/apt/lists/partial/ftp.fr.debian.org_debian_dists_testing_InRelease'

[Tsu Jan]

On Mon, 25 Jan 2016 12:17:45 +0100 Michael Vogt  wrote:
> This is a bug indeed, the question is how it got triggered, that dir
> should be owend by the _apt user.
>
> What is the output of:
> $ ls -dl /var/cache/apt/archives/partial/
>
> Thanks,
> Michael

That directory has been owned by root from time immemorial. I've never 
had an "_apt" user/group and no update created such a user/group. In 
other words, this is a *new* problem that started after a recent update 
(of apt?).


The output of "ls -dl":

drwxr-xr-x 2 root root 4096 Jan 25 13:20 /var/cache/apt/archives/partial/

Thanks!

Bug#808802: #808802 synaptic: Can't drop privileges for downloading as file '/var/lib/apt/lists/partial/ftp.fr.debian.org_debian_dists_testing_InRelease'

[Tsu Jan]

On Mon, 25 Jan 2016 17:03:36 +0100 Michael Vogt  wrote:
>
> Thanks! If you do not have an _apt user, that appears to be the
> problem. If I do:
>
> $ grep -B2 _apt /var/lib/dpkg/info/apt.postinst
>
> I see that the postinst tries to create such a user. Is there anything
> unusual about your system that might prevent creating this user?
>
> Thanks,
> Michael
>

Nothing unusual about my system, as far as I know. As you can see, 
similar reports are posted by others (I didn't open this bug report 
either). This is the output for me:


# add unprivileged user for the apt methods

adduser --force-badname --system --home /nonexistent \

--no-create-home --quiet _apt || true

# Fixup any mistake in the home directory of the _apt user

if dpkg --compare-versions "$2" lt-nl 1.1~exp10~; then

usermod --home /nonexistent _apt

Bug#808802: #808802 synaptic: Can't drop privileges for downloading as file '/var/lib/apt/lists/partial/ftp.fr.debian.org_debian_dists_testing_InRelease'

[Tsu Jan]

On Wed, 23 Dec 2015 11:01:29 +0100 Alexandre Detiste 
 wrote:

> This is likely a duplicate of this (read from #15), IE, not a bug:

For me, in Debian Testing, the message is:


W: Can't drop privileges for downloading as file 
'/var/cache/apt/archives/partial/PACKAGE' couldn't be accessed by user 
'_apt'. - pkgAcquire::Run (13: Permission denied)


This IS a bug for, at least, two reasons:

(1) The Synaptic user encounters such an unhelpful message after the 
download is complete;


(2) The message is not only unhelpful but also meaningless TO THE END 
USER because there's no '/var/cache/apt/archives/partial/PACKAGE' when 
the download in complete.

Bug#798341: [inkscape] impossible to install inkscape

[Tsu Jan]

> please don't (as it will not help with this ticket at all).


I won't.


> Say, how would you organize a C++ ABI transition that affects some 
1000 packages then?



If this is a real question, you could ask Manjaro's maintainers. The 
same "transition" happened there and I didn't even notice it. Not a 
single broken package! Or is Manjaro sh*t too, as Matteo believed about 
deb-multimedia.org?

Bug#798341: [inkscape] impossible to install inkscape

[Tsu Jan]

On Tue, 22 Sep 2015 23:33:43 +1000 Stuart Prescott  
wrote:

> inkscape can be installed in sid without any issues...

@ Stuart

Hi,

Thank you for the info!

I'm not a new Debian user: when I said I removed deb-multimedia, I 
implicitly meant I removed all its packages too, although I reinstalled 
them after I realized deb-multimedia was innocent -- because I needed them.


I think you might know that the problem is deeper than Inkscape's case. 
Several reports could be made for packages that aren't even remotely 
related to deb-multimedia.


Last but not least, I like Debian and hope it won't have a fate like 
that of Gnome3, although I see similarities in attitudes nowadays.

Bug#798341: [inkscape] impossible to install inkscape

[Tsu Jan]

Dear maintainers, if by "unofficial repositories" you mean the excellent 
work that is being done at "deb-multimedia.org", it's not to be blamed: 
the current mess persists after removing it from "sources.list". I have 
a working system only because I use Synaptic to upgrade packages one by one.



IMHO, the word "transition" has become a widespread excuse for the poor 
maintenance. Each maintainer MAY do his/her job well enough but the lack 
of coordination is obvious.

Bug#793026: kde-window-manager: upgrade to 4:5.3.2-2 generates

[Tsu Jan]

On Tue, 04 Aug 2015 16:43:50 -0300 Lisandro 
=?ISO-8859-1?Q?Dami=E1n_Nicanor_P=E9rez?= Meyer perezme...@gmail.com 
wrote:


 Sorry, but stating that we do not test what we ship is actually not 
polite at all.


That's an expression of a suspicion based on observation. It's being 
reinforced by you words (see below). You could deny it but calling it an 
impolite statement is meaningless, at best.



 We the maintainers consider that it's useful enough to start...


So, you mean it wasn't a mistake and will be continued for KDE in the 
future ? You talk about We, the maintainers as if it's the rule. It 
isn't, of course. For example, kernel maintainers don't push every 
kernel version into Testing. On the contrary, there are several versions 
that never come to Testing. The same is true for many other packages.



 ...but they will never get ironed out if we don't push it to the archive.


Could you please explain how they're ironed when they're inflicted on 
the users of Debian Testing? Weren't the users of Debian Unstable enough 
for that ironing? There is a difference between the Testing and 
Unstable repositories.



 I'm using it even on my $job machine.


You mean the maintaining job? Yes, of course, you SHOULD have a Debian 
Unstable for THAT job. By use I meant ordinarily using your operating 
system for any job. An environment, whose CPU usage goes high for no 
good reason, whose network manager can't remember any password, whose 
custom shortcuts and mouse gestures are missing, whose file manager 
crashes once in a while,... is not for use yet. There's nothing 
complicated about the meaning of the word use here. Or do you want to 
play with words instead of reasoning, as you tried to do in the case of 
the word polite, or in another place, where you wrote about Qt4's 
being dead?



 If you don't like that, please, use stable.


Totally irrelevant to the discussion. Criticizing this way of 
maintaining KDE/Qt doesn't have anything to do with disliking Debian 
Testing. Red herring?!



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

Bug#793026: kde-window-manager: upgrade to 4:5.3.2-2 generates

[Tsu Jan]

This is an excerpt from The Debian Administrator's Handbook, section 
1.6.3, Migration to Testing:



Every day a program automatically selects the packages to include in 
Testing, according to elements guaranteeing a certain level of quality:


(1) lack of critical bugs, or, AT LEAST FEWER THAN THE VERSION CURRENTLY 
INCLUDED IN TESTING;


(2) at least 10 days spent in Unstable... etc. etc.


My point is capitalized in (1); and there is a reason it comes first. As 
I said earlier, mistakes happen but become exceptions when not rationalized.



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

Bug#793026: kde-window-manager: upgrade to 4:5.3.2-2 generates

[Tsu Jan]

On Wed, 05 Aug 2015 14:49:55 +0200 Diederik de Haas 
didi.deb...@cknow.org wrote:

 On Wednesday 05 August 2015 15:36:09 Tsu Jan wrote:
  This is an excerpt from The Debian Administrator's Handbook, section
  1.6.3, Migration to Testing:

 Do you realize how EXTREMELY condescending just that statement alone 
is


I don't understand why you dramatized a simple situation with words like 
condescending, de-motivating, not willing or capable to do, I 
will ignore you, annoyed, negative, unconstructive. etc.


My statements were clear and polite enough. I tried to point out a 
GENERAL problem here, hoping that it'll be avoided in the future and 
knowing that I couldn't force anyone to consider or ignore it.


Obviously, this couldn't be about persons but about the quality of their 
WORK. I don't participate in psychological discussions about something 
that should be considered logically.



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

Bug#793026: kde-window-manager: upgrade to 4:5.3.2-2 generates

[Tsu Jan]

On Tue, 04 Aug 2015 13:30:22 -0300 Lisandro 
=?ISO-8859-1?Q?Dami=E1n_Nicanor_P=E9rez?= Meyer perezme...@gmail.com 
wrote:

 On Tuesday 04 August 2015 16:25:03 Pedram Pourang wrote:
 [snip]
  Why uploading a buggy KDE to Testing? Why not just keeping them in 
Unstable
  until a reliable version comes out? Dear maintainers, PLEASE DO USE 
WHAT YOU

  MAINTAIN! At least for a few days!

 Pedram, I find that offensive. We do use Plasma5, we know it has 
glitches, we

 know it's the only way forward to prepare the next stable release.

 If you really want something more stable, please, use Debian stable.

Hi,

I'm Pedram (Tsu). Please don't be offended by a rational and POLITE 
criticism! Otherwise you would make any criticism impossible.



I use Debian Testing (with some packages from Unstable) for more that 6 
years. It has been stable, secure and fairly up-to-date. Those, who want 
to maintain/test/have new software, go to Unstable and those, who don't 
want frequent updates or want to run a server, go to Stable. In short, 
Debian Testing has never been for testing NEW SOFTWARE but for testing 
already tested software against the strict Debian standards for Stable.



As for maintainers that don't use Debian (NOT all maintainers, of 
course), I've seen signs of that but will be really glad if I'm wrong.


I ask again: If you knew that KF5 wasn't ready for use (and I could 
write several lines why it isn't), why did you uploaded it from Unstable 
to Testing? This is a rational question, not a means to offend anyone. 
You don't have to answer it if that was just a mistake because mistakes 
happen. I'm just worried about their becoming more that exceptions.



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

Bug#712938: RFP: sni-qt -- Indicator support for Qt

[Tsu Jan]

On Fri, 31 Jul 2015 15:19:50 +0200 Peto Kadlecik 
peto.kadle...@gmail.com wrote:

 Thank you all for this effort.
 However, are there any instructions around on how to build sni-qt from
 sources? I'm particulary interested in how to configure sni-qt in order
 to link against my locally built (patched) Qt libs and not those from
 the system - I tried to look around for this but I haven't found an 
answer.


Aren't Ubuntu's sni-qt deb packages installable on your Debian? If I 
remember correctly, I just installed Ubuntu's 64 and 32-bit packages.



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

Bug#712938: RFP: sni-qt -- Indicator support for Qt

[Tsu Jan]

On Fri, 31 Jul 2015 16:13:45 +0200 Peto Kadlecik 
peto.kadle...@gmail.com wrote:

 It is, but of course it's also linked against system Qt libs in
 /usr/lib/... and I'd like to test this without having to replace the
 system Qt libs with my own.

Ubuntu's deb package just puts 'libsni-qt.so' in the qt4 plugins 
directory and 'sni-qt.conf' in '/etc/xdg/'. It has no 
pre-/post-installation script.

If you compile sni-qt manually, the same files should go to the same places.


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

Bug#712938: RFP: sni-qt -- Indicator support for Qt

[Tsu Jan]

Today I found that the tray icon of my Qt5 app isn't shown in 
Enlightenment, although I compiled it against qt5-5.4.2. Are your Qt5 
tray icons OK in KF5?



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

Bug#712938: RFP: sni-qt -- Indicator support for Qt

[Tsu Jan]

Sorry, it was an E bug.


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

Bug#712938: RFP: sni-qt -- Indicator support for Qt

[Tsu Jan]

On Mon, 27 Jul 2015 15:44:24 + 1...@o2o2.tk wrote:
 Your build is ok for me, so I only compiled 32bit package.

And your 32-bit package revived Skype's tray icon for me under Enlightenment. 
I'll use it under a stable KF5 too. I lock qt4 with Synaptic for now.

Nice sharing and thanks again!


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

Bug#712938: RFP: sni-qt -- Indicator support for Qt

[Tsu Jan]

On Mon, 27 Jul 2015 15:24:06 + 1...@o2o2.tk wrote:
 So, if anybody interested, this is patched libqtgui i386:
 https://mega.nz/#!rUEzCBiB!-83j59IHbhhWgTZsxE4AK55BppZ85vOf2TsyvJOIKI8

 I'll test it. Thanks! Did my 64-bit deb package work for you or did you 
compiled your own?


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

Bug#712938: sni-qt -- Indicator support for Qt

[Tsu Jan]

On Mon, 27 Jul 2015 07:54:18 +0200 Niels Thykier ni...@thykier.net wrote:
 Please note the following statement from Debian's diversity statement[1]:
 
 
   We welcome contributions from everyone as long as they interact
   constructively with our community.
 
 
 As such, Debian does not (and will not) require that you (or any other
 contributor) must use a particular operation system as primary OS.

Constructive interaction can be interpreted arbitrarily. IMO, usability 
should take priority. Particularly when maintainers don't use Debian (as their 
primary system), it's natural to expect that they will listen to those who do. 
Listening doesn't mean arguing with them that what they need is against this 
or that principle. Such arguments remind me of Gnome devs' infamous attitude, 
which I hope won't enter Debian.

 ... getting Debian to move in a particular direction (or
 contain a particular package) involves motivating people to do it (with
 people possibly including oneself).

That's why I write these lines.

 I have not been following this from the beginning, so I do not know what
 said warning is...

Read the first four comments on the report page.


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

Bug#712938: Info received (sni-qt -- Indicator support for Qt)

[Tsu Jan]

On Sun, 26 Jul 2015 13:42:51 + 1...@o2o2.tk wrote:
 It's actually not possible, because Debian includes qt  4_4.8.7 (in sid). So 
I can't replace files with older version, most likely it won't work. How do you 
have 4.8.6 in Debian?
 
 
 
The system on which I did so still  has Qt-4.8.6. Sorry that I didn't check 
that! On my laptop, I have qt  4_4.8.7 but I haven't updated KDE.


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

Bug#712938: No change?

[Tsu Jan]

On Sun, 26 Jul 2015 10:52:13 -0300 Lisandro 
=?ISO-8859-1?Q?Dami=E1n_Nicanor_P=E9rez?= Meyer perezme...@gmail.com wrote:
 On Sunday 26 July 2015 12:42:56 Michał Milanowski wrote:
  Can't any debian dev see his stupidity regarding to this issue? There are
  tons of qt4 apps that are widely used and will be probably never ported to
  qt5, like Skype for example, but many others too.
 
 Hi! I'm the Qt maintainer, and yes, I understand your arguments, but again: 
do 
 you really want to push dead-upstream code and support it trough the whole 
 life of Stretch? I don't.

Your argument is that of principles against usability. People USE Debian. The 
principles are important, of course, but as far as they don't interfere with 
usability.

You speak about dead code as if Qt4 has totally disappeared. As you know, 
there are and will be so many Qt4 apps. Porting to Qt5 is a good advice but, 
here again, an advice against usability?!


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

Bug#712938: sni-qt -- Indicator support for Qt

[Tsu Jan]

On Sun, 26 Jul 2015 10:48:07 -0300 Lisandro 
=?ISO-8859-1?Q?Dami=E1n_Nicanor_P=E9rez?= Meyer perezme...@gmail.com wrote: 
 That's the perfect way to break your system... 

I was cautious when doing that and my system works well. The compilation were 
compatible, otherwise my Qt4 apps wouldn't work. My Debian is Testing.
And I emphasized on backing up the original files.


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

Bug#712938: sni-qt -- Indicator support for Qt

[Tsu Jan]

On Sun, 26 Jul 2015 12:47:03 + 1...@o2o2.tk wrote:
 I can't compile qt after applying above patch from ubuntu:

On 64-bit machine, I added the attached patch to the standard debian patches 
of qt4-4.8.7 and got no compilation error after 5 minutes, although I 
interrupted the compilation process because I needed 32-bit packages (for 
Skype). Are you on 32-bit?

kubuntu_14_systemtrayicon.diff.tar.gz
Description: application/compressed-tar

Bug#712938: sni-qt -- Indicator support for Qt

[Tsu Jan]

On Sun, 26 Jul 2015 20:59:22 + 1...@o2o2.tk wrote:
 
 
   Yes, nvidia drivers installed via nvidia's installer. But what should I 
 do
 to fix this issue?

You should install the nVidia deb packages instead. Try the experimental 
repository for that but always have a light environment like IceWM if 
something goes wrong.

BTW, my compilation is being finished after one hour and a half. I'll leave a 
DropBox link for libqtgui4 if it works.


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

Bug#712938: sni-qt -- Indicator support for Qt

[Tsu Jan]

On Sun, 26 Jul 2015 20:26:49 + 1...@o2o2.tk wrote:
 Thanks for you solution, I previously tried official way as described in 
debian documentation and totally failed. Now almost there compilation 
success (with patch applied), but it refuses to build package, with error 
message:
 
 dpkg-shlibdeps: error: no dependency information found for 
/usr/lib/libGL.so.1 (used by debian/libqt4-opengl/usr/lib/x86_64-linux-
gnu/libQtOpenGL.so.4.8.7)

Good to know that it compiles so fast for you!

Do you have any nVidia/ATI/AMD driver that's installed manually or without a 
Debian package? If so, that could explain the error message.


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

Bug#712938: sni-qt -- Indicator support for Qt

[Tsu Jan]

On Sun, 26 Jul 2015 12:47:03 + 1...@o2o2.tk wrote:
 I can't compile qt after applying above patch from ubuntu...

Most probably, you don't need to recompile Qt4. Just get:

libqtgui4_4.8.6+git64-g5dc8b2b+dfsg-3~ubuntu6.1_amd64.deb
and/or
libqtgui4_4.8.6+git64-g5dc8b2b+dfsg-3~ubuntu6.1_i386.deb

from the Ubuntu Vivid repository, extract them, and overwrite 'usr/lib/x86_64-
linux-gnu/libQtGui.so.4.8.6' and/or /usr/lib/i386-linux-gnu/libQtGui.so.4.8.6' 
AFTER BACKING THEM UP.

Of course, you should have sni-qt too. That works for me without any problem 
under Enlightenment. I haven't needed it under KDE yet because I haven't 
upgraded KDE-4.14.2.


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

Bug#712938: sni-qt -- Indicator support for Qt

[Tsu Jan]

On Sun, 26 Jul 2015 17:36:59 + 1...@o2o2.tk wrote:
 
 
   Are you patching qt from sid (4_4.8.7)? You said you interrupted
 compilation, are you able to finish it with success?

I'm on Testing but the qt4 version is the same (4.8.7). With the 2-core CPU of 
my desktop computer, compilation would take 2 hours; hence the interruption. 
My laptop's CPU is far stronger but I'm not sure about the cooling system.

I may repeat the 64-bit compilation later, when I have enough time or find an 
easier way, but I can't do anything about 32-bit.


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

Bug#712938: sni-qt -- Indicator support for Qt

[Tsu Jan]

This is my 64-bit package at last:


https://dl.dropboxusercontent.com/u/7793460/libqtgui4_4.8.7%2Bdfsg-1_amd64.deb


I made it with the patch in question in addition to the standard Debian 
patches for qt4-4.8.7+dfsg-1, under Debian Testing. It works well for me 
under both Enlightenment and KDE (although my KDE doesn't need it yet).



If you want to install it, please do so under a non-Qt environment 
(IceWM, for example) -- but before that, download the original package 
for manual installation with sudo dpkg -i in case anything goes wrong. 
I ACCEPT NO RESPONSIBILITY and will remove the link after a while (but 
you could put it somewhere else).



All in all, it's weird that in spite of Dave's and my early warnings, 
this problem still arose. Isn't Debian a community-based distro? Or some 
Debian maintainers don't use Debian?!



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

Bug#712938: sni-qt -- Indicator support for Qt

[Tsu Jan]

On Sun, 26 Jul 2015 18:27:53 + 1...@o2o2.tk wrote:
 However I'm not sure if I did all things properly ...

Clean compilation and deb packaging is easy (maybe not for CPU though):

(1) Get the source and the debian folder from:

http://http.debian.net/debian/pool/main/q/qt4-x11/qt4-x11_4.8.7+dfsg.orig.tar.xz

and

http://http.debian.net/debian/pool/main/q/qt4-x11/qt4-x11_4.8.7+dfsg-1.debian.tar.xz

(2) Copy the (attached) patch to debian/patches and also add its full name to 
the end of debian/patches/series.

(3) Put the debian folder inside the source, open a terminal there, and issue 
dpkg-buildpackage -rfakeroot.

(4) Fnd an effective way of cooling down your CPU during the long compilation.


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

Bug#793026: kde-window-manager: upgrade to 4:5.3.2-2 generates

[Tsu Jan]

I wanted to confirm the existence of this problem and add that the recent KDE 
updates in Debian Testing paralyze important parts of KDE. For example, today, 
my wireless got disconnected after upgrading plasma-nm to 4:5.3.2-1 and 
systemsettings stopped working after upgrading to 4:5.3.2-2 (also see bug 
#792819). All of such problems can be fixed by downgrading but that isn't a 
straightforward process sometimes.

In short, it seems that there is a GENERAL and SERIOUS problem with upgrading 
of KDE parts -- a problem that I've never encountered before on Debian.


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

Bug#792819: Dolphin 4:15.04.3-1 seems buggy

[Tsu Jan]

Package: dolphin
Version: 4:15.04.3-1
Severity: normal

Dear Maintainer,

Either Dolphin 4:15.04.3-1 is buggy or it isn't intended to work under KDE 
4.14.2 in Debian Testing. Apart from some bugs in its bookmarks (that can be 
avoided), I'd like to mention this one:

Randomly but not frequently, when I move a file or folder into Trash with 
Dolphin 4:15.04.3-1, the whole Plasma crashes and restarts.


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

Kernel: Linux 4.0.0-2-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages dolphin depends on:
ii  kde-runtime4:4.14.2-2
ii  libbaloocore4  4:4.14.2-1.1
ii  libbaloofiles4 4:4.14.2-1.1
ii  libbaloowidgets4   4:4.14.0-1
ii  libc6  2.19-18
ii  libkactivities64:4.13.3-1
ii  libkcmutils4   4:4.14.2-5
ii  libkdecore54:4.14.2-5
ii  libkdeui5  4:4.14.2-5
ii  libkfile4  4:4.14.2-5
ii  libkfilemetadata4  4:4.14.0-1+b2
ii  libkio54:4.14.2-5
ii  libknewstuff3-44:4.14.2-5
ii  libkonq5abi1   4:15.04.3-1
ii  libkparts4 4:4.14.2-5
ii  libphonon4 4:4.8.0-5
ii  libplasma3 4:4.14.2-5
ii  libqt4-dbus4:4.8.7+dfsg-1
ii  libqt4-xml 4:4.8.7+dfsg-1
ii  libqtcore4 4:4.8.7+dfsg-1
ii  libqtgui4  4:4.8.7+dfsg-1
ii  libsolid4  4:4.14.2-5
ii  libstdc++6 5.1.1-14
ii  libxrender11:0.9.8-1+b1
ii  phonon 4:4.8.0-5

Versions of packages dolphin recommends:
pn  baloo-kf5  none
pn  ruby   none

Versions of packages dolphin suggests:
pn  kdesdk-dolphin-plugins  none

-- no debconf information


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

Bug#792819: Dolphin 4:15.04.3-1 seems buggy - Additional Info

[Tsu Jan]

Downgrading all these packages to their previous version in Debian Testing 
(4.14.2-1) resulted in a working Dolphin again:

dolphin
kde-baseapps-bin
kde-baseapps-data
kdebase-bin
kdepasswd
kfind
konqueror
konqueror-nsplugins
libkcddb4
libkonq-common
libkonq5-dev
libkonq5-temp
libkonq5abi1
libkonqsidebarplugin4a
plasma-widget-folderview


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

Bug#712938: Qt4 and sni-qt

[Tsu Jan]

On Thu, 07 May 2015 11:28:28 -0300 Lisandro 
=?ISO-8859-1?Q?Dami=E1n_Nicanor_P=E9rez?= Meyer perezme...@gmail.com wrote:
 - sni-qt seems to be dead-upstream:
 ...
 Uploading dead-upstream stuff to the archive doesn't seems a wise idea to me, 
 so if anyone wants this in then jump in as sni-qt upstream. Or **much** 
better 
 yet, just help porting the code to Qt5.

sni-qt is only for Qt4 and needs a patch. As far as I know, no change will be 
needed with Qt5 = 5.4 for the systray icons to work.

sni-qt  may be dead-upstream but Qt4 is so too and yet there are so many Qt4 
apps. As mentioned above, Enlightenment already needs sni-qt for Qt4 apps to 
show their systray icons.


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

Bug#767388: gdm3: (with default=kdm) gdm.service gives failed status

[Tsu Jan]

This is fixed here with systemd-215-16 and gdm3-3.14.1-7.


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

Bug#754200: KDE fails to recognize keyboard backlight capabilities on fresh boot

[Tsu Jan]

I had exactly the same issue in an Asus G56JK and Andres's workaround worked 
for me.


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

Bug#712938: sni-qt -- Indicator support for Qt

[Tsu Jan]

No maintainer uses E19 or Plasma5!? sni-qt is needed by them.


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

Bug#767388: gdm3: (with default=kdm) gdm.service gives failed status

[Tsu Jan]

I have systemd 215-8 (which is now in Testing) and have the same problem 
but with gdm3 and lightdm. Here, both lightdm (1.10.3-3) and gdm3 
(3.14.1-3) are installed but the former is set to be the default display 
manager. I get lines like these:



gdm.service: control process exited, code=exited status=1

Failed to start GNOME Display Manager.

Dependency failed for X11 Display Manager.

Unit gdm.service entered failed state.


They seem harmless and I can uninstall gdm3 to get rid of them but this 
is definitely a bug. It seems that systemd has a bias toward gdm and 
sees it indispensable even when it isn't the default DM.



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

Bug#770840: ark: Ark crashes on exit when nested archives opened

[Tsu Jan]

I confirm the existence of the bug and also that this commit fixes it:

http://quickgit.kde.org/?p=ark.gita=commith=9c30f30b38c36a31e6fcb3aa047a0247ac5a22fb


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

Bug#712938: sni-qt -- Indicator support for Qt

[Tsu Jan]

I applied the above-mentioned Qt4 patch successfully and sni-qt worked under 
E19. Is there any chance that Debian includes it for Qt4 as Ubuntu does? There 
will be no Qt4 update and, without the patch, Debian KDE users will have 
problems with systray icons of Qt4 apps in the near future.


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

Bug#712938: sni-qt -- Indicator support for Qt

[Tsu Jan]

It seems that for sni-qt to work, Qt4 should to be patched with:

https://bazaar.launchpad.net/~indicator-applet-developers/sni-qt/trunk.13.04/view/head:/patches/qsystemtrayicon-plugin-system-4.7.4.diff

It's needed with any systray that works based on appindicator. Enlightenment 
already has it and KDE will soon 
(http://blog.martin-graesslin.com/blog/2014/06/where-are-my-systray-icons/).


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

Bug#744249: libgtk-3-0: gtk 3.12 breaks usability by forcing client side decorations on X11 forcing client side decorations on X11

[Tsu Jan]

On Fri, 17 Oct 2014 16:04:19 +0400 =?UTF-8?B?VmxhZCBPcmxvdg==?= 
mon...@inbox.ru wrote:
 Strangely, I can't seem to find any upstream bugs about
 the inability to resize CSD windows. How come...?
The only CSD I see in KDE is gtk3-widget-factory and it can be resized. The 
mouse cursor changes when it goes near sides or corners and it makes no 
difference if I use the default GTK3 theme or a customized one.


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

Bug#744249: Re: libgtk-3-0: gtk 3.12 breaks usability by forcing client side decorations on X11

[Tsu Jan]

On Mon, 13 Oct 2014 15:00:44 +0400 =?UTF-8?B?VmxhZCBPcmxvdg==?= 
mon...@inbox.ru wrote:
 Yes, they come from Gnome project but that doesn't mean that the users of 
other
 desktop environments don't use them.
 ...
 Last but not least, think of the simple window managers, e.g. WindowMaker, 
which
 Matti Hamalainen (the reporter of this bug) does use.

I think a misunderstanding has occurred here.

My second DE is Enlightenment-19 and it has just a few apps of its own. So, I 
use GTK and mostly Qt4 apps with it but rarely Gnome ones if ever. For 
example, qpdfview is far better than evince, or Nemo than Nautilus, or 
SMPlayer than Totem, etc. As image viewer, I use (a hacked version of) 
LXImage-Qt. I've made GTK3 apps but never needed devhelp. There are nice text 
editors that can be used instead of gEdit (I use my own). All in all, these 
are personal preferences.

I thought may point was clear enough. If not, I explain it more:

If GTK3 forces CSD on non-Gnome apps that don't use it explicitly, that IS a 
bug in GTK3. But if ONLY Gnome apps get CSD, that could be seen as a bug in 
THEM (or in Gnome) and not in GTK3.

Now, Gnome developers could happily say they make Gnome apps just for Gnome 
(as they've said things more amusing than that) but they couldn't say that 
they make GTK3 only for Gnome because GTK3 is the GIMP ToolKit, not Gnome 
ToolKit (- http://www.gtk.org/).


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

Bug#744249: libgtk-3-0: gtk 3.12 breaks usability by forcing client side decorations on X11

[Tsu Jan]

On Sat, 11 Oct 2014 12:01:38 +0400 Vlad Orlov mon...@inbox.ru wrote:
 Hi,
 
  Today, gkt-3.14.1 afflicted Testing. I use just a few gtk3 apps under KDE 
(Meld,
  pavucontrol and Synaptic) and they have no CSD, not even in their dialogs.
  (They broke themes again though.)
 
 Please see the list of CSD apps (and a screenshot) at 
 https://bugs.debian.org/744249#127

Hi,

I don't know about gthumb but gnome-calculator, devhelp, gedit and totem are 
Gnome apps. _IF_ Gnome devs want to make an isolated DE, it'll be logical not 
to use their apps outside Gnome. Here, the problem is GTK3 itself: GTK3 is NOT 
supposed to be a Gnome-specific toolkit. GTK-3.12 was starting to be so and all 
I say is that apparently GTK-3.14 isn't.

So, please tell us if you know of any GTK3 app that has this problem and is 
not specific to Gnome. I can't give more examples because I have no reason to 
use more GTK3 apps. gthumb may be a case. We'll need more examples if we want 
to prove our point clearly.


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

Bug#744249: libgtk-3-0: gtk 3.12 breaks usability by forcing client side decorations on X11

[Tsu Jan]

Today, gkt-3.14.1 afflicted Testing. I use just a few gtk3 apps under KDE 
(Meld, 
pavucontrol and Synaptic) and they have no CSD, not even in their dialogs. 
(They broke themes again though.)

So, perhaps, if you don't use Gnome apps CSD won't show up.


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

Bug#744249: libgtk-3-0: gtk 3.12 breaks usability by forcing client side decorations on X11

[Tsu Jan]

On Fri, 10 Oct 2014 17:29:08 +0200 Christoph Anton Mitterer 
cales...@scientia.net wrote:
 It's basically as if they'd create their own isolated OS, something like
 Android, and people from inside can't cleanly use stuff from the outside
 and vice-versa.
 If they want this (and actually they seem to do) fine... but then they
 should be kicked out of any Linux distribution.
The direction they go in is doubtless what you described, at least since four 
years ago. I think Debian should change its default DE sooner or later. (Is it 
still Gnome?)


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

Bug#744249: libgtk-3-0: gtk 3.12 breaks usability by forcing client side decorations on X11

[Tsu Jan]

On Fri, 10 Oct 2014 18:39:50 +0200 Christoph Anton Mitterer 
cales...@scientia.net wrote:
 they changed it some months ago, but reverted now back to GNOME o.O

Oh, I didn't know that! Fortunately many Linux users know the meaning of 
quality. Gnome couldn't be forced on them by such maneuvers.


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

Bug#744249: libgtk-3-0: gtk 3.12 breaks usability by forcing client side decorations on X11

[Tsu Jan]

On Fri, 10 Oct 2014 18:51:24 +0200 Michael Biebl bi...@debian.org wrote:
 ... If you don't stop this behaviour... I'm  going to report this to the bts 
 and list maintainers and ask for a ban... 

Your concern is understandable but the way you put it into words was rather 
like a threat. I beg both parties to calm down and focus on the practical side 
of the problem.

This bug report says that GTK3 breaks usability. If there's a good patch to 
cure that, it could be applied. If not, something should be done about how 
Gnome affects people outside it. After all, Debian isn't equal to Gnome even if 
its default DE is Gnome.


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

Bug#744249: libgtk-3-0: gtk 3.12 breaks usability by forcing client side decorations on X11

[Tsu Jan]

On Fri, 3 Oct 2014 15:18:26 +0300 (EEST) Matti Hamalainen c...@tnsp.org 
wrote:
 I am somewhat at loss for how to proceed, unless Gtk+ devs themselves come 
 up with a standard solution.

They don't see any problem to find a solution for. What we've tagged as an 
important bug here, is probably a feature to them.


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

Bug#744249: libgtk-3-0: gtk 3.12 breaks usability by forcing client side decorations on X11

[Tsu Jan]

On Wed, 1 Oct 2014 17:43:53 +0300 (EEST) Matti Hamalainen c...@tnsp.org 
wrote: 
 With that patch, even gnome-calculator submits to not using CSD. The patch 
 may have some redundant sections, but it's difficult to know what is
 necessary and what is not without deeper understanding of the 
 CSD/headerbar logic (which I have no time nor patience for, sorry.)

I think returning FALSE from gtk_window_supports_csd() in gtkwindow.c is 
enough, although I haven't tested GTK-3.14 yet.


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

Bug#754828: fixed in nvidia-graphics-drivers 340.24-1

[Tsu Jan]

I'm afraid the problem isn't fixed for multi-arch systems: the Unstable 
nvidia isn't installable because libgl1-nvidia-glx:i386 has no v340.24-1.



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

Bug#754828: fixed in nvidia-graphics-drivers 340.24-1

[Tsu Jan]

OK! Thank you for your fast reply!


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

Bug#753305: No contact displayed

[Tsu Jan]

The problem is fixed for me after installing kde-telepathy-kpeople, which 
wasn't needed before.


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

Bug#753305: No contact displayed

[Tsu Jan]

Exactly the same issue here. It's said that v0.8 needs akonadi-4.13 
(https://bugs.kde.org/show_bug.cgi?id=332643) but I didn't dare to try 
the experimental repository for such a package.



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

Bug#616308: libcairo2 1.10.2-4 makes the desktop environment very unresponsive with NVidia drivers

[Tsu Jan]

Now Cairo's version is 1.12.16 and I still have to patch it with any DE 
other than KDE. As wm4 said, the patch is so simple. Strange! Anything 
even remotely related to Gnome has become illogical!



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

Bug#744249: libgtk-3-0: gtk 3.12 breaks usability by forcing client side decorations on X11

[Tsu Jan]

For now, I use the attached patch in addition to the one at


http://redmine.audacious-media-player.org/boards/1/topics/1135


to get rid of CSD completely. I don't have Gnome and don't know if they 
could make any trouble under Gnome-Shell.


diff -ruNp gtk+-3.12.1-orig/gtk/gtkwindow.c gtk+-3.12.1/gtk/gtkwindow.c
--- gtk+-3.12.1-orig/gtk/gtkwindow.c	2014-04-12 09:34:53.0 +0430
+++ gtk+-3.12.1/gtk/gtkwindow.c	2014-05-04 13:37:07.248913645 +0430
@@ -3607,18 +3607,7 @@ gdk_window_supports_csd (GtkWindow *wind
 #ifdef GDK_WINDOWING_X11
   if (GDK_IS_X11_DISPLAY (gtk_widget_get_display (widget)))
 {
-  GdkScreen *screen;
-  GdkVisual *visual;
-
-  screen = gtk_widget_get_screen (widget);
-
-  if (!gdk_screen_is_composited (screen))
-return FALSE;
-
-  /* We need a visual with alpha */
-  visual = gdk_screen_get_rgba_visual (screen);
-  if (!visual)
-return FALSE;
+  return FALSE;
 }
 #endif
 

Bug#722217: libc6: Update fails halfway with segfault

[Tsu Jan]

Exactly the same thing happened for me a few times and also today. I 
have nvidia (now from Testing but sometimes from Unstable/Experimental) 
and the same sys info the reporter gave. Here I have Gnome, IceWM and 
E18 but it makes no difference where I use Synaptic.



Each time I got my system working again just by pressing ctrl+alt+F1, 
using sudo apt-get -f dist-upgrade and then, rebooting.



The strange thing is that I've never had this problem with my other 
Debian Testing installed on another partition but with KDE (and with the 
same versions of nvidia).



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

Bug#722217: libc6: Update fails halfway with segfault

[Tsu Jan]

I forgot to say this: the bug is filed against 
libgl1-nvidia-legacy-173xx-glx but I don't have it. My installed nvidia 
packages are:



libgl1-nvidia-glx_331.67-1_amd64.deb

libgl1-nvidia-glx_331.67-1_i386.deb

libnvidia-ml1_331.67-1_amd64.deb

nvidia-alternative_331.67-1_amd64.deb

nvidia-driver_331.67-1_amd64.deb

nvidia-glx_331.67-1_amd64.deb

nvidia-kernel-dkms_331.67-1_amd64.deb

nvidia-settings_331.67-1_amd64.deb

nvidia-vdpau-driver_331.67-1_amd64.deb

xserver-xorg-video-nvidia_331.67-1_amd64.deb


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

Bug#703484: Pulseaudio 3.0 Stops Working With Old Config

[Tsu Jan]

In fact, the problem was fixed when PulseAudio-3 came into Testing (or 
Unstable?). Sorry that I didn't tell about that! I thought it wasn't so 
important that an Experimental version was buggy.



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

Bug#691812: udevil -- flexible CLI tool

[Tsu Jan]

Now, it's needed even with KDE-4.11, where auto-mount doesn't work by default. 
A nifty app indeed!


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

Bug#725978: /usr/lib/udisks2/udisksd: Doesn't event on CD/DVD media insertion

[Tsu Jan]

 I solved the problem by applying this patch...

Thanks for the link. Kernel polling can also be enabled with this in 
/etc/rc.local:

echo 2000  /sys/module/block/parameters/events_dfl_poll_msecs

 The event is activated when System Settings - Permissions...

Also see here: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=709148

 ...or with the command: $ udisks --enumerate

So, you still have udisks. The problem is that udisks2 has replaced it (udisks 
can be removed now) and automount doesn't work.


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

Bug#725978: /usr/lib/udisks2/udisksd: Doesn't event on CD/DVD media insertion

[Tsu Jan]

I encountered the same problem after upgrading to KDE-4.11, which needed 
udisks2: no automount after inserting CD/DVD media -- a serious drawback.

After hours of searching the Internet, I could fix the issue only with udevil, 
which worked like a charm but, sadly, hasn't come to Debian's repositories 
yet.


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

Bug#728262: gdebi-kde: does not start gdebi-kde

[Tsu Jan]

The root of this problem was that the upgrades for python-qt4 and python-kde4 
weren't synchronized. Now it's fixed but it might happen again unless the 
maintainers of those packages synchronize their updates.


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

Bug#432561: Please test my preview package

[Tsu Jan]

Not a single crash with Rolf's packages.


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

Bug#432561: Please test my preview package

[Tsu Jan]

@Rolf Leggewie

I installed your package downloaded from 
https://launchpad.net/~r0lf/+archive/stable and saw no Polipo crash for a day, 
while, with polipo v1.0.4.1-4, I encountered a random crash once or twice a 
day.

The strange thing is that, with polipo v1.0.4.1-3, I never experienced any 
crash at all, although it has the same source as v1.0.4.1-4 does.


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

Bug#728262: gdebi-kde: does not start gdebi-kde

[Tsu Jan]

OK, I downgraded python-qt4 and python-qt4-dbus to 4.10.2-2 and the problem 
disappeared. For now, I lock them with Synaptic.


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

Bug#728262: Same Problem Here

[Tsu Jan]

After updating python-qt4 from 4.10.2-2 to 4.10.3-2, not only gdebi-kde stopped 
working but also the Plasma desktop crashed. Only after I removed 
plasma-scriptengine-python, the Plasma desktop started normally (without 
Python-based Plasmoids, of course).

BTW, I remember that the same problem happened a few times in the past after 
updating Qt4 Python bindings.


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

Bug#707976: Not Fixed Yet

[Tsu Jan]

I just wanted to confirm that the wine-unstable v1.5.7-4 isn't usable. In fact, 
I was surprised to see that after upgrading from v1.5.6-2 with Synaptic, tens 
of MiB of disk space was freed. Only 1.5.6-2 works.


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

Bug#610287: plymouth shutdown part failing

[Tsu Jan]

I just wanted to add that Plymouth works OK during shutdown on my KDE
Debian installation. Here, the problem only appears with Gnome and GDM.


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

Bug#703484: Pulseaudio 3.0 Stops Working With Old Config

[Tsu Jan]

Package: pulseaudio
Version: 3.0-1
Severity: normal

Dear Maintainer,

After upgrading PA to 3.0-1 from Experimental, sound was good at first
but, after a while, it stopped working (no sound at all). After reboot,
the same thing happened again. However, when I removed '~/.pulse/' and
'~/.pulse-cookie' (and the same files from the root home) everything
became OK.

So, contrary to the notes at freedesktop.org, the new PA doesn't work
with the old config files well. It would be better if the new deb
package removed the old config files both from user's home and from the
root home or, at least, gave a warning.

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

Kernel: Linux 3.6.8-pf (SMP w/2 CPU cores; PREEMPT)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages pulseaudio depends on:
ii  adduser   3.113+nmu3
ii  consolekit0.4.5-3.1
ii  libasound21.0.25-4
ii  libasound2-plugins1.0.25-2
ii  libc6 2.13-38
ii  libcap2   1:2.22-1.2
ii  libdbus-1-3   1.6.8-1
ii  libfftw3-33.3.2-3.1
ii  libgcc1   1:4.7.2-5
ii  libice6   2:1.0.8-2
ii  libltdl7  2.4.2-1.1
ii  liborc-0.4-0  1:0.4.16-2
ii  libpulse0 3.0-1
ii  libsamplerate00.1.8-5
ii  libsm62:1.2.1-2
ii  libsndfile1   1.0.25-5
ii  libspeexdsp1  1.2~rc1-7
ii  libstdc++64.7.2-5
ii  libsystemd-daemon044-11
ii  libsystemd-login0 44-11
ii  libtdb1   1.2.10-2
ii  libudev0  175-7.1
ii  libwebrtc-audio-processing-0  0.1-2
ii  libx11-6  2:1.5.0-1
ii  libx11-xcb1   2:1.5.0-1
ii  libxcb1   1.8.1-2
ii  libxtst6  2:1.2.1-1
ii  lsb-base  4.1+Debian8
ii  udev  175-7.1

Versions of packages pulseaudio recommends:
ii  gstreamer0.10-pulseaudio  0.10.31-3+nmu1
pn  pulseaudio-module-x11 none
pn  rtkit none

Versions of packages pulseaudio suggests:
ii  paman 0.9.4-1
ii  paprefs   0.9.10-1
ii  pavucontrol   1.0-1
ii  pavumeter 0.9.3-4
ii  pulseaudio-utils  3.0-1

-- no debconf information


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

Bug#703484: Suddenly No Sound Again

[Tsu Jan]

It seems that the problem is deeper. After several hours, suddenly not
only there was no sound but even media players (Totem, Gnome-MPlayer,
SMPlayer) couldn't play videos (ffplay played videos without audio).

Logging out of Gnome and logging into IceWM didn't do anything but GDM
had its system sound working. Only killing and restarting PA solved the
issue.

I couldn't find any error message.


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

Bug#680175: gnome-mime-data

[Tsu Jan]

This isn't specific to gnome-mime-data. I see the same thing in KDE and with 
Dolphin: vmlinuz is seen as application/x-ms-dos-executable.


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

Bug#676833: The Patch Works

[Tsu Jan]

I just wanted to confirm that Cyril's patch solved my problem with kde4libs 
package build.


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

Bug#694791: gdm3 disappears after several log-outs

[Tsu Jan]

Package: gdm3
Version: 3.6.1-2
Severity: normal

Dear Maintainer,

With the Experimental gdm3, after several times of logging out of
GNOME-Shell (6-7 times, for example), the text terminal is shown instead
of GDM. Logging in with the text terminal and restarting gdm3 make it
appear again though.

In addition to that (and perhaps as another bug), GDM's shut-down and
restart menuitems doesn't do anything anymore.

I have nVidia 304.64-2 from Unstable and haven't
changed /etc/gdm3/greeter.gsettings (gdm uses gdm-fallback).


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

Kernel: Linux 3.6.8-pf (SMP w/2 CPU cores; PREEMPT)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages gdm3 depends on:
ii  accountsservice 0.6.21-7
ii  adduser 3.113+nmu3
ii  dconf-gsettings-backend 0.12.1-2
ii  dconf-tools 0.12.1-2
ii  debconf [debconf-2.0]   1.5.46
ii  dpkg1.16.9
ii  gir1.2-glib-2.0 1.34.2-1
ii  gnome-session [x-session-manager]   3.6.0-1
ii  gnome-session-bin   3.6.0-1
ii  gnome-session-fallback [x-session-manager]  3.6.0-1
ii  gnome-settings-daemon   3.6.1-1
ii  gnome-terminal [x-terminal-emulator]3.6.1-1
ii  gsettings-desktop-schemas   3.6.0-1
ii  icewm [x-window-manager]1.3.7-4
ii  libaccountsservice0 0.6.21-7
ii  libatk1.0-0 2.6.0-1
ii  libaudit0   1:1.7.18-1.1
ii  libc6   2.13-37
ii  libcairo-gobject2   1.12.2-2.1
ii  libcairo2   1.12.2-2.1
ii  libcanberra-gtk3-0  0.28-5
ii  libcanberra00.28-5
ii  libfontconfig1  2.9.0-7
ii  libgdk-pixbuf2.0-0  2.26.1-1
ii  libglib2.0-02.34.2-1
ii  libglib2.0-bin  2.34.2-1
ii  libgtk-3-0  3.6.1-1
ii  libpam-modules  1.1.3-7.1
ii  libpam-runtime  1.1.3-7.1
ii  libpam0g1.1.3-7.1
ii  libpango1.0-0   1.30.0-1
ii  librsvg2-common 2.36.4-1
ii  libselinux1 2.1.9-5
ii  libupower-glib1 0.9.17-1
ii  libwrap07.6.q-24
ii  libx11-62:1.5.0-1
ii  libxau6 1:1.0.7-1
ii  libxdmcp6   1:1.1.1-1
ii  libxrandr2  2:1.3.2-2
ii  lsb-base4.1+Debian8
ii  metacity [x-window-manager] 1:2.34.3-3
ii  policykit-1-gnome   0.105-2
ii  twm [x-window-manager]  1:1.0.6-1
ii  upower  0.9.17-1
ii  x11-common  1:7.7+1
ii  x11-xserver-utils   7.7~3
ii  xterm [x-terminal-emulator] 278-2

Versions of packages gdm3 recommends:
ii  at-spi2-core   2.7.1-1
ii  desktop-base   7.0.3
ii  gnome-icon-theme   3.6.0-1
ii  gnome-icon-theme-symbolic  3.6.0-1
ii  x11-xkb-utils  7.7~1
ii  xserver-xephyr 2:1.12.4-3
ii  xserver-xorg   1:7.7+1
ii  zenity 3.4.0-2

Versions of packages gdm3 suggests:
pn  gnome-orcanone
ii  gnome-shell   3.6.2-1
pn  gok   none
ii  libpam-gnome-keyring  3.6.1-1

-- debconf information:
* shared/default-x-display-manager: gdm3
  gdm3/daemon_name: /usr/sbin/gdm3





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

Bug#680175: gnome-mime-data

[Tsu Jan]

I also see this bug since almost two months ago. Now I have a liquorix
kernel 3.5.4 and the vmlinuz icon is that of x-ms-dos-executable, which
is distinct from other executable icons in the set I use. It's funny to
have an MS related icon in the root directory of Linux ;)


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

Bug#594753: Cdrtools instead of libburnia

[Tsu Jan]

The bug may be related to how Brasero uses libburnia+libisofs. I
recompiled Brasero after disabling libisofs and libburnia plugins and,
at least with Jörg Schilling's Cdrtools instead of wodim, Brasero v3.4
burned a DVD correctly.

I don't think the bug is in libburnia because SimpleBurn doesn't have
any problem with it.


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

Bug#684620: gnome-screenshot: Alt+Print gives corrupted image

[Tsu Jan]

Package: gnome-screenshot
Version: 3.4.1-1
Severity: normal

Dear Maintainer,

With nvidia 304.32-1, gnome-screenshot gives corrupted images of windows
(Alt+Print) in Gnome-Shell 4.3.2-1. It still produces correct
screenshots of the whole screen. It also produces correct screenshots of
windows in the fallback mode.

The problem probably appeared after upgrading nvidia from 295.59. I
reported this bug against gnome-screenshot just because Shutter, for
example, has no problem with taking window screenshots.

I found these related reports:

http://www.nvnews.net/vbulletin/showthread.php?p=2570902

https://bugs.archlinux.org/task/31087

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

Kernel: Linux 3.4.4-pf (SMP w/2 CPU cores; PREEMPT)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages gnome-screenshot depends on:
ii  dconf-gsettings-backend [gsettings-backend]  0.12.1-2
ii  libc62.13-35
ii  libcairo21.12.2-2
ii  libcanberra-gtk3-0   0.28-4
ii  libcanberra0 0.28-4
ii  libgdk-pixbuf2.0-0   2.26.1-1
ii  libglib2.0-0 2.32.3-1
ii  libgtk-3-0   3.4.2-2
ii  libx11-6 2:1.5.0-1
ii  libxext6 2:1.3.1-2

gnome-screenshot recommends no packages.

gnome-screenshot suggests no packages.


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

Bug#594753: Brasero is Unreliable

[Tsu Jan]

For more than two years (= 4 Gnome versions), Brasero has been
unreliable. Version 3.2 couldn't even start burning so I used my bash
script+Zenity based on Jörg Schilling's Cdrtools for burning (always
fast and reliable) and, now, v3.4 gives corrupted DVDs (two times was
more than enough for me), which makes me use my own script again.

I know that Debian maintainers can't do anything about this problem but
I wonder why the Gnome team allow this app to ruin their nice creature!


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

Bug#684055: libsasl2-2: Multiarch Issue

[Tsu Jan]

Source: libsasl2-2
Version: 2.1.25.dfsg1-4+b1
Severity: normal

Dear Maintainer,

Installation of libsasl2-2:i386 alongside libsasl2-2:amd64 on a 64-bit
debian is impossible because of this error:

trying to overwrite shared
'/usr/share/doc/libsasl2-2/changelog.Debian.gz', which is different from
other instances of package libsasl2-2:i386

So, I had to repackage it after replacing the file changelog.Debian.gz
with the same file from its 64-bit counterpart. It's a dependency of
libcurl3:i386, needed by Adobe's stand-alone Flash player, among others.

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

Kernel: Linux 3.4.4-pf (SMP w/2 CPU cores; PREEMPT)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash


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

Bug#681652: GStreamer does not play MP4

[Tsu Jan]

Package: gstreamer0.10-plugins-bad
Version: 0.10.23-6

Totem, using gstreamer0.10-plugins-bad v0.10.23-6, can't play mp4 files.
No error message, just a blank screen.

There's a discussion and a patch at:

https://bugs.launchpad.net/ubuntu/+source/gst-plugins-bad0.10/+bug/973014

I applied a modified form of that patch to gst-plugins-bad0.10_0.10.23
from Debian repository and the issue is fixed for me. The patch I
applied is attached.

Doug McMahon, at Launchpad, recommended I refer you to:

http://cgit.freedesktop.org/gstreamer/gst-plugins-bad/commit/?h=0.10id=845d8dc844225557440dd12d22299fad941d8dfb


-- System Information:
Debian Release: wheezy/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 3.4.2-pf (SMP w/2 CPU cores; PREEMPT)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages gstreamer0.10-plugins-bad depends on:
ii  dconf-gsettings-backend [gsettings-backend]  0.12.1-2
ii  gstreamer0.10-plugins-base   0.10.36-1
ii  libass4  0.10.0-3
ii  libbz2-1.0   1.0.6-3
ii  libc62.13-33
ii  libcairo21.12.2-2
ii  libcdaudio1  0.99.12p2-12
ii  libcurl3-gnutls  7.26.0-1
ii  libdc1394-22 2.2.0-2
ii  libdca0  0.0.5-5
ii  libdirac-encoder01.0.2-6
ii  libdirectfb-1.2-91.2.10.0-5
ii  libdvdnav4   4.2.0+20120524-2
ii  libdvdread4  4.2.0+20120521-2
ii  libfaad2 2.7-8
ii  libflite11.4-release-5
ii  libgcc1  1:4.7.1-2
ii  libglib2.0-0 2.32.3-1
ii  libgme0  0.5.5-2
ii  libgsm1  1.0.13-4
ii  libgstreamer-plugins-bad0.10-0   0.10.23-6.1
ii  libgstreamer-plugins-base0.10-0  0.10.36-1
ii  libgstreamer0.10-0   0.10.36-1
ii  libjasper1   1.900.1-13
ii  libkate1 0.4.1-1
ii  liblrdf0 0.4.0-5
ii  libmimic01.0.4-2.1
ii  libmms0  0.6.2-3
ii  libmodplug1  1:0.8.8.4-3
ii  libmpcdec6   2:0.1~r459-4
ii  libofa0  0.9.3-5
ii  libopenal1   1:1.14-4
ii  libopus0 0.9.14+20120615-1
ii  liborc-0.4-0 1:0.4.16-2
ii  libpng12-0   1.2.49-1
ii  librsvg2-2   2.36.1-1
ii  librtmp0 2.4
+20111222.git4e06e21-1
ii  libschroedinger-1.0-01.0.11-2
ii  libslv2-90.6.6+dfsg1-2
ii  libsndfile1  1.0.25-5
ii  libsoundtouch0   1.6.0-3
ii  libspandsp2  0.0.6~pre18-2+b2
ii  libssl1.0.0  1.0.1c-3
ii  libstdc++6   4.7.1-2
ii  libvo-aacenc00.1.2-1
ii  libvo-amrwbenc0  0.1.2-1
ii  libvpx1  1.1.0-1
ii  libwildmidi1 0.2.3.4-2.1
ii  libx11-6 2:1.5.0-1
ii  libxml2  2.8.0+dfsg1-4
ii  libxvidcore4 3:1.3.2-dmo1
ii  libzbar0 0.10+doc-7+b2
ii  libzvbi0 0.2.33-6
ii  multiarch-support2.13-33

gstreamer0.10-plugins-bad recommends no packages.

Versions of packages gstreamer0.10-plugins-bad suggests:
ii  frei0r-plugins  1.1.22git20091109-1.2


h264parse01023.patch.gz
Description: GNU Zip compressed data

Bug#660084: evolution: Evolution crashes on startup

[Tsu Jan]

I also confirm that nvidia-295.33-1 fixes all issues.




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

Bug#660084: Evolution crash and nvidia

[Tsu Jan]

In my report #661559, a crash in Evolution is caused by nvidia v295.20-1
only when a new mail is being received. Do you also use nvidia?





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

Bug#661559: Evolution Crashes On Receiving Email

[Tsu Jan]

Package: evolution
Version: 3.2.2-1

After a recent system update, Evolution crashes on receiving emails.
Mails still can be sent without problem.

The terminal just says Segmentation Fault and nothing else. When I use
gdb, strace or ddd, Evolution doesn't crash anymore and there's nothing
suspicious about the outputs.

I even ran Evolution in ICEWM with the same results.

-- System Information:
Debian Release: wheezy/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 3.2.2-tuxonice (SMP w/2 CPU cores; PREEMPT)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages evolution depends on:
ii  dbus  1.4.18-1
ii  debconf [debconf-2.0] 1.5.41
ii  evolution-common  3.2.2-1
ii  evolution-data-server 3.2.2-1
ii  gconf22.32.4-1
ii  gnome-icon-theme  3.2.1.2-1
ii  libatk1.0-0   2.2.0-2
ii  libc6 2.13-26
ii  libcairo-gobject2 1.10.2-6.2
ii  libcairo2 1.10.2-6.2
ii  libcamel-1.2-29   3.2.2-1
ii  libcanberra-gtk3-00.28-3
ii  libcanberra0  0.28-3
ii  libclutter-1.0-0  1.8.4-1
ii  libclutter-gtk-1.0-0  1.0.4-1
ii  libcogl-pango01.8.2-1
ii  libcogl5  1.8.2-1
ii  libdrm2   2.4.30-1
ii  libebackend-1.2-1 3.2.2-1
ii  libebook-1.2-12   3.2.2-1
ii  libecal-1.2-103.2.2-1
ii  libedataserver-1.2-15 3.2.2-1
ii  libedataserverui-3.0-13.2.2-1
ii  libenchant1c2a1.6.0-7
ii  libevolution  3.2.2-1
ii  libfontconfig12.8.0-3.1
ii  libfreetype6  2.4.8-1
ii  libgail-3-0   3.2.3-1
ii  libgconf2-4   2.32.4-1
ii  libgdata130.10.1-2
ii  libgdk-pixbuf2.0-02.24.1-1
ii  libgl1-mesa-glx [libgl1]  7.11.2-1
ii  libglib2.0-0  2.30.2-6
ii  libgnome-desktop-3-2  3.2.1-3
ii  libgtk-3-03.2.3-1
ii  libgtkhtml-4.0-0  4.2.2-1
ii  libgtkhtml-editor-4.0-0   4.2.2-1
ii  libgweather-3-0   3.2.1-1
ii  libical0  0.44-3
ii  libjson-glib-1.0-00.14.2-1
ii  libmx-1.0-2   1.4.1-1
ii  libnotify40.7.4-1
ii  libnspr4-0d   4.9~beta5-2
ii  libnss3-1d3.13.1.with.ckbi.1.88-1
ii  libpango1.0-0 1.29.4-2
ii  libsoup-gnome2.4-12.34.3-1
ii  libsoup2.4-1  2.34.3-1
ii  libsqlite3-0  3.7.10-1
ii  libx11-6  2:1.4.4-4
ii  libxcomposite11:0.4.3-2
ii  libxdamage1   1:1.1.3-2
ii  libxext6  2:1.3.0-3
ii  libxfixes31:5.0-4
ii  libxi62:1.4.5-1
ii  libxml2   2.7.8.dfsg-7
ii  psmisc22.15-2

Versions of packages evolution recommends:
ii  bogofilter 1.2.2+dfsg1-1
ii  evolution-plugins  3.2.2-1
ii  evolution-webcal   none
ii  yelp   3.2.1+dfsg-1+b1

Versions of packages evolution suggests:
ii  evolution-dbg   3.2.2-1
ii  evolution-exchange  none
ii  evolution-plugins-experimental  none
ii  gnupg   1.4.11-3
ii  network-manager 0.9.2.0-2

-- debconf information:
  evolution/kill_processes:
  evolution/needs_shutdown:





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

Bug#661559: Was Related to nVidia

[Tsu Jan]

Strangely enough, after I downgraded the nVidia driver from v295.20-1 to
v290.10-1, the problem disappeared!




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

Bug#659115: Fixed with the ustable libpixman

[Tsu Jan]

Thanks! The problem is fixed with libpixman-1-0 v0.24.4-1 from unstable.




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

Bug#659115: Problems with Non-Zero Border Radius of GTK Widgets after Upgrading libpixman-1-0

[Tsu Jan]

Package: libpixman-1-0
Version: 0.24.2-1

After upgrading libpixman-1-0 to v0.24.2-1, some problems related to
border radius appeared in GTK3 (and GTK2) apps. One of them is so:

If border-radius is set to a non-zero value for GtkNotebooks (in
.notebook block of gtk-widgets.css and even in the Adwaita theme), the
left border won't be shown when the leftmost (first) tab is active, and
only when another tab is active it will be shown. This can be easily
seen in Bluefish but exists in all GTK3 (and perhaps, GTK2) apps.
However, it isn't ugly in Nautilus because Nautilus' pane separator is
visible with Adwaita.

There's also another issue when the toolbar border radius is non-zero
but this issue can't be seen with a modified Adwaita.

I reported this bug against libpixman-1-0 just because downgrading it to
v0.24.0-1 solved both problems.

System Information:
--
Debian Release: wheezy/sid
Kernel: Linux 3.1.0-1-amd64
libc6: 2.13.26
libcairo2: 1.10.2-6.2
libgtk-3-0: 3.2.3-1 
nVidia: 290.10-1

info on libpixman-1-0 0.24.2-1
--
Depends: libc6 (= 2.3)
Pre-Depends: multiarch-support






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

Bug#642223: closed

[Tsu Jan]

Here, Vidalia 0.12.14-3 starts Tor 0.2.2.33-1 with TCP connection.




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

Bug#642223: closed

[Tsu Jan]

I confirm that Vidalia doesn't have to start Tor anymore. If the user is 
in the debian-tor group, Tor runs with start-up and can be used by the 
user. This is good as there's no need to use Vidalia for running Tor 
anymore :)


However, if Tor is STOPPED WITH VIDALIA, Vidalia couldn't start it 
again. Can't this be seen as a bug in Vidalia?





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

Bug#616308: Looks like NVidia finally fixed it

[Tsu Jan]

 As of libcairo2 1.10.2-6.1 and NVidia drivers 280.13.really.275.28-1 ...

I confirm that, with libcairo2 1.10.2-6.1 and nVidia 285.05.09, THIS bug 
doesn't occur anymore. Another bug, related to trapezoid acceleration, 
has appeared with Xorg 1.11.1, which causes terrible slowdowns and high 
CPU usage. The temporary cure is a patch at 
http://www.nvnews.net/vbulletin/showthread.php?t=166698page=2





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

Bug#642223: vidalia cannot start tor

[Tsu Jan]

Same problem here. Setting Vidalia to use TCP connection didn't help 
either. Downgrading it to v0.2.12-2 fixed the issue.





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