[Python-modules-team] Bug#800693: python-urwid: breaks wicd-curses

Package: python-urwid Version: 1.3.0-1+b1 Severity: critical Justification: breaks unrelated software Dear Maintainer, the new version breaks wicd-curses. See attachment. -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable'), (500,

Bug#800693: python-urwid: breaks wicd-curses

Package: python-urwid Version: 1.3.0-1+b1 Severity: critical Justification: breaks unrelated software Dear Maintainer, the new version breaks wicd-curses. See attachment. -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable'), (500,

Bug#799837: sddm becomes unusable after logout

> Does the problem go away if you boot your machine after removing consolekit? Plasma 5 goes away if I remove consolekit (see attached aptitude log), so your suggestion is not really useful to me. Thanks aptitude Description: Binary data

Bug#799837: sddm becomes unusable after logout

> Does the problem go away if you boot your machine after removing consolekit? Plasma 5 goes away if I remove consolekit (see attached aptitude log), so your suggestion is not really useful to me. Thanks aptitude Description: Binary data

Bug#800532: RM: plasma-widget-smooth-tasks -- ROM; The package is obsolete

Package: ftp.debian.org Severity: normal Please see #793048 and https://bitbucket.org/flupp/smooth-tasks-fork/issues/43/ The package is useless in its current status and upstream is not responsive.

Bug#799837: sddm becomes unusable after logout

Package: sddm Version: 0.12.0-4 Severity: critical Justification: breaks the whole system Dear Maintainer, I normally use a laptop where I am the single user, so I only login once in sddm, and I use "shutdown" when I (rarely) need to turn it off. Today I needed to logout and login again. What

Bug#799837: sddm becomes unusable after logout

Package: sddm Version: 0.12.0-4 Severity: critical Justification: breaks the whole system Dear Maintainer, I normally use a laptop where I am the single user, so I only login once in sddm, and I use "shutdown" when I (rarely) need to turn it off. Today I needed to logout and login again. What

Bug#799837: sddm becomes unusable after logout

Package: sddm Version: 0.12.0-4 Severity: critical Justification: breaks the whole system Dear Maintainer, I normally use a laptop where I am the single user, so I only login once in sddm, and I use "shutdown" when I (rarely) need to turn it off. Today I needed to logout and login again. What

Bug#799645: sonnet-plugins: Missing dependency on aspell

Package: sonnet-plugins Version: 5.14.0-1 Severity: normal Dear Maintainer, basically #798915 but that was marked as fixed in a previous version and it does nont seem fixed at all. The description of sonnet should explicitly mention that it requires aspell and does not work with myspell. Best

Bug#799645: sonnet-plugins: Missing dependency on aspell

Package: sonnet-plugins Version: 5.14.0-1 Severity: normal Dear Maintainer, basically #798915 but that was marked as fixed in a previous version and it does nont seem fixed at all. The description of sonnet should explicitly mention that it requires aspell and does not work with myspell. Best

Bug#798579: linux: fails to boot MPU-401 device not found or busy

Hello, I was using systemd. It boots with sysvinit. 2015-09-18 18:08 GMT+02:00 Ben Hutchings <b...@decadent.org.uk>: > Control: retitle -1 Boot hangs under Linux 3.16 after I/O errors for sr0 > Control: severity -1 important > Control: tag -1 moreinfo > > On Thu, 10 Sep 2015

Bug#798579: linux: fails to boot MPU-401 device not found or busy

Hello, I was using systemd. It boots with sysvinit. 2015-09-18 18:08 GMT+02:00 Ben Hutchings <b...@decadent.org.uk>: > Control: retitle -1 Boot hangs under Linux 3.16 after I/O errors for sr0 > Control: severity -1 important > Control: tag -1 moreinfo > > On Thu, 10 Sep 2015

Bug#798365: libpolkit-gobject-1-0: depends on deprecated libsystemd-login0 package

Package: libpolkit-gobject-1-0 Version: 0.112-3 Severity: normal Dear Maintainer, the package lists this: > Depends: libc6 (>= 2.7), libglib2.0-0 (>= 2.31.8), libsystemd-login0 (>= 31) however the last package no longer exists. Best -- System Information: Debian Release: stretch/sid APT

[Pkg-utopia-maintainers] Bug#798365: libpolkit-gobject-1-0: depends on deprecated libsystemd-login0 package

Package: libpolkit-gobject-1-0 Version: 0.112-3 Severity: normal Dear Maintainer, the package lists this: > Depends: libc6 (>= 2.7), libglib2.0-0 (>= 2.31.8), libsystemd-login0 (>= 31) however the last package no longer exists. Best -- System Information: Debian Release: stretch/sid APT

Re: nitrogen tissue saturation toggle is broken

> But they are linked, so if you don’t display the ceiling the other two have > no effect. Thank you. So I think that they should get disabled if the 1st button is not set. Also, my initial situation was that somehow the ceiling was not displayed but the saturation (2nd buttonI) was. But after

Bug#798272: sddm: messes up with last session

Package: sddm Version: 0.12.0-1 Severity: minor Dear Maintainer, after the last upgrade of the package, I restarted sddm. Instead of logging in inside Plasma (which was the last session I was usinig) it opened e17. Best -- System Information: Debian Release: stretch/sid APT prefers unstable

Bug#798272: sddm: messes up with last session

Package: sddm Version: 0.12.0-1 Severity: minor Dear Maintainer, after the last upgrade of the package, I restarted sddm. Instead of logging in inside Plasma (which was the last session I was usinig) it opened e17. Best -- System Information: Debian Release: stretch/sid APT prefers unstable

Re: nitrogen tissue saturation toggle is broken

> I was wondering about your build problems. With the latest master you should > be able to simply compile from source. Oh I thought I had replied. Problem 1: there is no URL on the website that I can give to git clone. I am stuck at this step. This page

Bug#797746: kopete: should not depend on kdepim-runtime

Package: kopete Version: 4:4.14.1-2 Severity: normal Dear Maintainer, kopete works just fine without kdepim-runtime. It cannot integrate with kaddressbook but that is an extra feature. So I believe that it should recommend kdepim-runtime rather than depending on it. Currently kopete is not

Re: observations about the FB integration

> It is indeed the Facebook site, shown the way Facebook recommends that > applications do things. The challenge with opening it in a separate > browser window is getting back the token into Subsurface. Not impossible, > but not something anyone has undertaken. I can't think of an obvious easy

Bug#797670: kgpg: Should not depend on kdepim-runtime

Package: kgpg Version: 4:4.14.2-1 Severity: normal Dear Maintainer, kgpg runs fine without kdepim-runtime, so it should not depend on it. kdepim-runtime will install mysql and akonadi, and perhaps the user just wanted a UI to sign keys. The dependency should be moved to suggests or recommends.

Bug#797670: kgpg: Should not depend on kdepim-runtime

Package: kgpg Version: 4:4.14.2-1 Severity: normal Dear Maintainer, kgpg runs fine without kdepim-runtime, so it should not depend on it. kdepim-runtime will install mysql and akonadi, and perhaps the user just wanted a UI to sign keys. The dependency should be moved to suggests or recommends.

observations about the FB integration

Hello, After the recent turmoil I started using the PPA, since after all I still prefer to log my dives. I have some points to raise about the facebook integration. In the settings it asks me to insert my username and password inside a window that looks very much like facebook but might not be,

[Pkg-kde-extras] Bug#796172: konversation: should not depend on kdepim-runtime

Thank you. I've installed it already from incoming. 2015-08-28 21:13 GMT+02:00 Diane Trout : > version: 1.6-1 > > Hello, > > Upstream dropped the kdepim dependency in 1.6. At some point they're planning > on using kpeople to replace it. Check

Bug#796172: konversation: should not depend on kdepim-runtime

Thank you. I've installed it already from incoming. 2015-08-28 21:13 GMT+02:00 Diane Trout : > version: 1.6-1 > > Hello, > > Upstream dropped the kdepim dependency in 1.6. At some point they're planning > on using kpeople to replace it. Check

Re: [Pkg-running-devel] Bug#789875: subsurface: FTBFS in experimental

Hello, can we please stop? Christoph, if you want to take over subsurface in debian you can. But patches that need to be maintained are going to be huge; it is a lot of work. If you don't intend to do this work you can stop using it, compile their source code or get their binaries. Either way

Bug#789875: [Pkg-running-devel] Bug#789875: subsurface: FTBFS in experimental

Hello, can we please stop? Christoph, if you want to take over subsurface in debian you can. But patches that need to be maintained are going to be huge; it is a lot of work. If you don't intend to do this work you can stop using it, compile their source code or get their binaries. Either way

Bug#789875: [Pkg-running-devel] Bug#789875: subsurface: FTBFS in experimental

Hello, can we please stop? Christoph, if you want to take over subsurface in debian you can. But patches that need to be maintained are going to be huge; it is a lot of work. If you don't intend to do this work you can stop using it, compile their source code or get their binaries. Either way

Bug#779974:

Sorry! I had forgot about this bug. I tried to import the certs as you said, but: keytool -v -importcert -trustcacerts -alias rapidssl_ca -file /tmp/osm-tile-cert-1.crt -keystore /etc/ssl/certs/java/cacerts -storepass changeitErrore keytool: java.lang.Exception: L'input non è un certificato

Bug#779974: josm: invalid certificate (incomplete /etc/ssl/certs/java/cacert)

I tried using it today again. I've noticed that after I get the initial error asking me to configure a proxy, if I just hit cancel I can go on working normally. 2015-08-26 12:42 GMT+02:00 Sebastiaan Couwenberg sebas...@xs4all.nl: Hi Salvo Java Team, As reported in the #779974 josm is not

Re: Bug#779974: josm: invalid certificate (incomplete /etc/ssl/certs/java/cacert)

I tried using it today again. I've noticed that after I get the initial error asking me to configure a proxy, if I just hit cancel I can go on working normally. 2015-08-26 12:42 GMT+02:00 Sebastiaan Couwenberg sebas...@xs4all.nl: Hi Salvo Java Team, As reported in the #779974 josm is not

Bug#779974: josm: invalid certificate (incomplete /etc/ssl/certs/java/cacert)

I tried using it today again. I've noticed that after I get the initial error asking me to configure a proxy, if I just hit cancel I can go on working normally. 2015-08-26 12:42 GMT+02:00 Sebastiaan Couwenberg sebas...@xs4all.nl: Hi Salvo Java Team, As reported in the #779974 josm is not

[Pkg-kde-extras] Bug#796764: konversation: please package latest release

Package: konversation Version: 1.5-2 Severity: normal Dear Maintainer, the latest release of conversation uses Qt5, and the newer KDE libraries. It would be nice to update it, especially because Qt4 are being phased out. Is help needed with packaging? Best -- System Information: Debian

Bug#796764: konversation: please package latest release

Package: konversation Version: 1.5-2 Severity: normal Dear Maintainer, the latest release of conversation uses Qt5, and the newer KDE libraries. It would be nice to update it, especially because Qt4 are being phased out. Is help needed with packaging? Best -- System Information: Debian

Bug#796177: akregator: should not depend on kdepim-runtime

Package: akregator Version: 4:4.14.2-2 Severity: important Dear Maintainer, akregator currently depends on kdepim-runtime. According to section 7.2 of the debian policy, it should at most suggest it. Because I've just created a dummy kdepim-runtime and konversation is running just fine. So it

Bug#796177: akregator: should not depend on kdepim-runtime

Package: akregator Version: 4:4.14.2-2 Severity: important Dear Maintainer, akregator currently depends on kdepim-runtime. According to section 7.2 of the debian policy, it should at most suggest it. Because I've just created a dummy kdepim-runtime and konversation is running just fine. So it

Bug#796172: konversation: should not depend on kdepim-runtime

Package: konversation Version: 1.5-2 Severity: important Dear Maintainer, for reasons unknown to mankind, konversation currently depends on kdepim-runtime. According to section 7.2 of the debian policy, it should at most suggest it. Because I've just created a dummy kdepim-runtime and

[Pkg-kde-extras] Bug#796172: konversation: should not depend on kdepim-runtime

Package: konversation Version: 1.5-2 Severity: important Dear Maintainer, for reasons unknown to mankind, konversation currently depends on kdepim-runtime. According to section 7.2 of the debian policy, it should at most suggest it. Because I've just created a dummy kdepim-runtime and

Bug#795733: plasma-workspace: trackpoint not recognized by touchpad applet

Package: plasma-workspace Version: 4:5.3.2-4 Severity: minor Tags: upstream Dear Maintainer, this is an upstream bug but I failed to locate the component where this belongs so I hope you can help? I have a Thinkpad, so it has a touchpad+the red dot. When I disable the touchpad from the applet,

Bug#795733: plasma-workspace: trackpoint not recognized by touchpad applet

Package: plasma-workspace Version: 4:5.3.2-4 Severity: minor Tags: upstream Dear Maintainer, this is an upstream bug but I failed to locate the component where this belongs so I hope you can help? I have a Thinkpad, so it has a touchpad+the red dot. When I disable the touchpad from the applet,

Bug#789875: [Pkg-running-devel] Bug#789875: needs to be removed

packaging impossible. Not the static linking. -- Salvo Tomaselli Io non mi sento obbligato a credere che lo stesso Dio che ci ha dotato di senso, ragione ed intelletto intendesse che noi ne facessimo a meno. -- Galileo Galilei http://ltworf.github.io/ltworf/

Bug#789875: [Pkg-running-devel] Bug#789875: needs to be removed

packaging impossible. Not the static linking. -- Salvo Tomaselli Io non mi sento obbligato a credere che lo stesso Dio che ci ha dotato di senso, ragione ed intelletto intendesse che noi ne facessimo a meno. -- Galileo Galilei http://ltworf.github.io/ltworf/

Bug#789875: needs to be removed

@subsurface-divelog.org/msg05634.html Honestly, there is nothing I can do, that doesn't involve forking subsurface. Sorry -- Salvo Tomaselli Io non mi sento obbligato a credere che lo stesso Dio che ci ha dotato di senso, ragione ed intelletto intendesse che noi ne facessimo a meno

Bug#789875: needs to be removed

@subsurface-divelog.org/msg05634.html Honestly, there is nothing I can do, that doesn't involve forking subsurface. Sorry -- Salvo Tomaselli Io non mi sento obbligato a credere che lo stesso Dio che ci ha dotato di senso, ragione ed intelletto intendesse che noi ne facessimo a meno

Bug#795238: subsurface: Please remove

Package: subsurface Version: 4.3-2 Severity: grave Dear Maintainer, upstream forked quite a lot of libraries. Packaging subsurface is impossible. It should be removed. -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'),

Bug#795238: subsurface: Please remove

Package: subsurface Version: 4.3-2 Severity: grave Dear Maintainer, upstream forked quite a lot of libraries. Packaging subsurface is impossible. It should be removed. -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'),

Re: libgit 0.23.0 support

I have filed a grave debian bug that will lead to automatic removal from the archive. I am a bit bitter about it, especially after the hours spent packaging it last summer; but besides forking it, there is nothing I can do. I normally avoid installing things that are not packaged, unless I

Bug#794573: kwin-style-breeze: breaks kwin_x11

Package: kwin-style-breeze Version: 4:5.3.2-4 Severity: critical Justification: breaks unrelated software Dear Maintainer, after the last upgrade of this package, kwin_x11 hangs and needs to be killed. I am attaching the output that it gives, in hopes that it can be helpful. I suspect the

Bug#794573: kwin-style-breeze: breaks kwin_x11

Package: kwin-style-breeze Version: 4:5.3.2-4 Severity: critical Justification: breaks unrelated software Dear Maintainer, after the last upgrade of this package, kwin_x11 hangs and needs to be killed. I am attaching the output that it gives, in hopes that it can be helpful. I suspect the

Bug#794573: kwin-style-breeze: breaks kwin_x11

Package: kwin-style-breeze Version: 4:5.3.2-4 Severity: critical Justification: breaks unrelated software Dear Maintainer, after the last upgrade of this package, kwin_x11 hangs and needs to be killed. I am attaching the output that it gives, in hopes that it can be helpful. I suspect the

Bug#794061: breeze: Breeze theme completely stopped working after the last upgrade

It should, that's the default path embedded in the libs. The en variable might be used to override it. As I said, doing unset QT_PLUGIN_PATH and then running anything qt4 does not work either. -- Salvo Tomaselli Io non mi sento obbligato a credere che lo stesso Dio che ci ha dotato di

Bug#794061: breeze: Breeze theme completely stopped working after the last upgrade

It should, that's the default path embedded in the libs. The en variable might be used to override it. As I said, doing unset QT_PLUGIN_PATH and then running anything qt4 does not work either. -- Salvo Tomaselli Io non mi sento obbligato a credere che lo stesso Dio che ci ha dotato di

Bug#794061: breeze: Breeze theme completely stopped working after the last upgrade

It should, that's the default path embedded in the libs. The en variable might be used to override it. As I said, doing unset QT_PLUGIN_PATH and then running anything qt4 does not work either. -- Salvo Tomaselli Io non mi sento obbligato a credere che lo stesso Dio che ci ha dotato di

Bug#794061: breeze: Breeze theme completely stopped working after the last upgrade

it loads the breeze style even when the path is not explicitly listed in QT_PLUGIN_PATH. I don't think it does load it without the env-var :) -- Salvo Tomaselli Io non mi sento obbligato a credere che lo stesso Dio che ci ha dotato di senso, ragione ed intelletto intendesse che noi ne facessimo

Bug#794061: breeze: Breeze theme completely stopped working after the last upgrade

it loads the breeze style even when the path is not explicitly listed in QT_PLUGIN_PATH. I don't think it does load it without the env-var :) -- Salvo Tomaselli Io non mi sento obbligato a credere che lo stesso Dio che ci ha dotato di senso, ragione ed intelletto intendesse che noi ne facessimo

Bug#794061: breeze: Breeze theme completely stopped working after the last upgrade

it loads the breeze style even when the path is not explicitly listed in QT_PLUGIN_PATH. I don't think it does load it without the env-var :) -- Salvo Tomaselli Io non mi sento obbligato a credere che lo stesso Dio che ci ha dotato di senso, ragione ed intelletto intendesse che noi ne facessimo

Bug#794061: breeze: Breeze theme completely stopped working after the last upgrade

-style breeze. Does it still not use the breeze style? Yes, the option doesn't do anything. Does qtconfig-qt4 (package qt4-qtconfig) list breeze in the style list? No. It shows Unknown as the selected style. Let me know if you need more tests. Best -- Salvo Tomaselli Io non mi sento obbligato

Bug#794061: breeze: Breeze theme completely stopped working after the last upgrade

-style breeze. Does it still not use the breeze style? Yes, the option doesn't do anything. Does qtconfig-qt4 (package qt4-qtconfig) list breeze in the style list? No. It shows Unknown as the selected style. Let me know if you need more tests. Best -- Salvo Tomaselli Io non mi sento obbligato

Bug#794061: breeze: Breeze theme completely stopped working after the last upgrade

-style breeze. Does it still not use the breeze style? Yes, the option doesn't do anything. Does qtconfig-qt4 (package qt4-qtconfig) list breeze in the style list? No. It shows Unknown as the selected style. Let me know if you need more tests. Best -- Salvo Tomaselli Io non mi sento obbligato

Bug#794061: breeze: Breeze theme completely stopped working after the last upgrade

don't understand what you mean. -- Salvo Tomaselli Io non mi sento obbligato a credere che lo stesso Dio che ci ha dotato di senso, ragione ed intelletto intendesse che noi ne facessimo a meno. -- Galileo Galilei http://ltworf.github.io/ltworf

Bug#794061: breeze: Breeze theme completely stopped working after the last upgrade

don't understand what you mean. -- Salvo Tomaselli Io non mi sento obbligato a credere che lo stesso Dio che ci ha dotato di senso, ragione ed intelletto intendesse che noi ne facessimo a meno. -- Galileo Galilei http://ltworf.github.io/ltworf

Bug#794061: breeze: Breeze theme completely stopped working after the last upgrade

don't understand what you mean. -- Salvo Tomaselli Io non mi sento obbligato a credere che lo stesso Dio che ci ha dotato di senso, ragione ed intelletto intendesse che noi ne facessimo a meno. -- Galileo Galilei http://ltworf.github.io/ltworf

Bug#793853: powerdevil: Powerdevil does not do anything

Package: powerdevil Version: 4:5.3.2-1 Severity: normal Dear Maintainer, in light of the recent becoming compulsory of powerdevil, I've decided to give it a try, rather than using my own acpi script in python. Results are rather bad. I have configured it to dim the screen when on battery, and

Bug#793853: powerdevil: Powerdevil does not do anything

Package: powerdevil Version: 4:5.3.2-1 Severity: normal Dear Maintainer, in light of the recent becoming compulsory of powerdevil, I've decided to give it a try, rather than using my own acpi script in python. Results are rather bad. I have configured it to dim the screen when on battery, and

Bug#793682: Moreinfo

Hello, I believe the problem I had was due to the absence of konsole4-kpart. I suppose maybe in an earlier version it was not installed? I suppose the bug can be closed. Thanks 2015-07-27 16:12 GMT+02:00 Lisandro Damián Nicanor Pérez Meyer perezme...@gmail.com: Salvo: I forgot to CC you,

Bug#793463: powerdevil is necessary to not use powerdevil

https://bugs.kde.org/show_bug.cgi?id=350685 2015-07-27 23:44 GMT+02:00 Lisandro Damián Nicanor Pérez perezme...@gmail.com: On Monday 27 July 2015 10:11:58 Salvo Tomaselli wrote: Apparently powerdevil is necessary to NOT use power management. After installing powerdevil, the checkbox about

Bug#793463: powerdevil is necessary to not use powerdevil

https://bugs.kde.org/show_bug.cgi?id=350685 2015-07-27 23:44 GMT+02:00 Lisandro Damián Nicanor Pérez perezme...@gmail.com: On Monday 27 July 2015 10:11:58 Salvo Tomaselli wrote: Apparently powerdevil is necessary to NOT use power management. After installing powerdevil, the checkbox about

Bug#793463: powerdevil is necessary to not use powerdevil

weird, I suppose that the screen locking functionality should be moved inside powerdevil. -- Salvo Tomaselli Io non mi sento obbligato a credere che lo stesso Dio che ci ha dotato di senso, ragione ed intelletto intendesse che noi ne facessimo a meno. -- Galileo Galilei

Bug#793463: powerdevil is necessary to not use powerdevil

weird, I suppose that the screen locking functionality should be moved inside powerdevil. -- Salvo Tomaselli Io non mi sento obbligato a credere che lo stesso Dio che ci ha dotato di senso, ragione ed intelletto intendesse che noi ne facessimo a meno. -- Galileo Galilei

Re: Bug#792290: Mitigation

I feel that this is going OT. Probably a new bugreport would be better to discuss the issue.

Bug#793682: yakuake: Should conflict with konsole in experimental

Package: yakuake Version: 2.9.9-1 Severity: normal Dear Maintainer, installing the version of konsole currently in experimental: 4:15.04.3-1 will break yakuake. Perhaps it would be better to change the control file to reflect this. Best -- System Information: Debian Release: stretch/sid

Re: Bug#792290: Mitigation

Tried this setting only PATH, and it prevented me to log in... Probably a mistake in your script that causes sh to terminate.

Bug#793738: fonts-oxygen: Antialiasing is rather bad

Package: fonts-oxygen Version: 4:5.3.2-1 Severity: normal Tags: upstream Dear Maintainer, I have noticed that compared to the Dejavu font, the antialiasing in this is very bad. What I first noticed was the monospaced font. It is really less readable. This font is set by default in plasma 5

Bug#793738: fonts-oxygen: Antialiasing is rather bad

Package: fonts-oxygen Version: 4:5.3.2-1 Severity: normal Tags: upstream Dear Maintainer, I have noticed that compared to the Dejavu font, the antialiasing in this is very bad. What I first noticed was the monospaced font. It is really less readable. This font is set by default in plasma 5

Bug#793739: frameworkintegration: Should not depend on fonts-oxygen

Package: frameworkintegration Version: 5.12.0-1 Severity: normal Dear Maintainer, it should probably just recommend the fonts. I am using Dejavu (because it looks much better with antialiasing) but I can't uninstall the package. Best -- System Information: Debian Release: stretch/sid APT

Bug#793739: frameworkintegration: Should not depend on fonts-oxygen

Package: frameworkintegration Version: 5.12.0-1 Severity: normal Dear Maintainer, it should probably just recommend the fonts. I am using Dejavu (because it looks much better with antialiasing) but I can't uninstall the package. Best -- System Information: Debian Release: stretch/sid APT

Bug#793740: kwrite: spell checking does not work at all

Package: kwrite Version: 4:15.04.3-1 Severity: normal Dear Maintainer, using the experimental version, spell checking feature is not working. Hspell: can't open /usr/share/hspell/hebrew.wgz.sizes. HSpellDict::HSpellDict: Init failed sonnet.plugins.hunspell: HunspellClient::HunspellClient No

Bug#793740: kwrite: spell checking does not work at all

Package: kwrite Version: 4:15.04.3-1 Severity: normal Dear Maintainer, using the experimental version, spell checking feature is not working. Hspell: can't open /usr/share/hspell/hebrew.wgz.sizes. HSpellDict::HSpellDict: Init failed sonnet.plugins.hunspell: HunspellClient::HunspellClient No

Bug#793463: suspend

Forget the part about suspending, it was caused by another thing that does not run in KDE. -- Salvo Tomaselli Io non mi sento obbligato a credere che lo stesso Dio che ci ha dotato di senso, ragione ed intelletto intendesse che noi ne facessimo a meno. -- Galileo Galilei

Bug#793463: suspend

Forget the part about suspending, it was caused by another thing that does not run in KDE. -- Salvo Tomaselli Io non mi sento obbligato a credere che lo stesso Dio che ci ha dotato di senso, ragione ed intelletto intendesse che noi ne facessimo a meno. -- Galileo Galilei

Bug#792290: Mitigation

It is possible to mitigate the issue by placing shell scripts in ~/.config/plasma-workspace/env However it must be noted that they will be sourced, not executed in separate processes. -- Salvo Tomaselli Io non mi sento obbligato a credere che lo stesso Dio che ci ha dotato di senso, ragione

Bug#792290: Mitigation

It is possible to mitigate the issue by placing shell scripts in ~/.config/plasma-workspace/env However it must be noted that they will be sourced, not executed in separate processes. -- Salvo Tomaselli Io non mi sento obbligato a credere che lo stesso Dio che ci ha dotato di senso, ragione

Bug#793105: Workaround

Env variables can be set for the entire session like this: editor ~/.config/plasma-workspace/env/path.sh And then in the file write #!/bin/sh export PATH=$PATH:~/bin This can be used to set any env var -- Salvo Tomaselli Io non mi sento obbligato a credere che lo stesso Dio che ci ha dotato

Bug#793105: Workaround

Env variables can be set for the entire session like this: editor ~/.config/plasma-workspace/env/path.sh And then in the file write #!/bin/sh export PATH=$PATH:~/bin This can be used to set any env var -- Salvo Tomaselli Io non mi sento obbligato a credere che lo stesso Dio che ci ha dotato

Bug#793463: plasma-workspace: Impossible to configure or disable powersaving

Package: plasma-workspace Version: 4:5.3.2-3 Severity: normal Dear Maintainer, I am using the plasmoid to show the battery status. As discussed on IRC, powersaving options are currently not configurable but this is not what the bug is about. I left the computer to do a 2h long job, when I came

Bug#793463: plasma-workspace: Impossible to configure or disable powersaving

Package: plasma-workspace Version: 4:5.3.2-3 Severity: normal Dear Maintainer, I am using the plasmoid to show the battery status. As discussed on IRC, powersaving options are currently not configurable but this is not what the bug is about. I left the computer to do a 2h long job, when I came

Bug#793466: plasma-workspace: Ignores preferred browser settings

Package: plasma-workspace Version: 4:5.3.2-3 Severity: normal Dear Maintainer, I've decided to switch from using iceweasel to chromium. So I've opened systemsettings5, and changed the preferred browser to chromium. Then I tried typing deb:akregator in krunner, and the link was opened with

Bug#793466: plasma-workspace: Ignores preferred browser settings

Package: plasma-workspace Version: 4:5.3.2-3 Severity: normal Dear Maintainer, I've decided to switch from using iceweasel to chromium. So I've opened systemsettings5, and changed the preferred browser to chromium. Then I tried typing deb:akregator in krunner, and the link was opened with

Bug#793105: sddm probably

Reading the mailing list, it is probably related to this https://github.com/sddm/sddm/issues/256 -- To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive:

Bug#793105: sddm probably

Reading the mailing list, it is probably related to this https://github.com/sddm/sddm/issues/256 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#793105: plasma-workspace: krunner no longer searches $PATH

Package: plasma-workspace Version: 4:5.3.2-3 Severity: normal Dear Maintainer, after the last update of this package, krunner no longer searches $PATH for binaries. I can run a binary located in /usr/bin or in /bin but i can't run binaries in ~/bin that are in my $PATH and can be executed if I

Bug#793105: plasma-workspace: krunner no longer searches $PATH

Package: plasma-workspace Version: 4:5.3.2-3 Severity: normal Dear Maintainer, after the last update of this package, krunner no longer searches $PATH for binaries. I can run a binary located in /usr/bin or in /bin but i can't run binaries in ~/bin that are in my $PATH and can be executed if I

Bug#792290: .desktop files are used, symlinks to script not

should create the .desktop file myself, at best. But I haven't tried that. -- Salvo Tomaselli Io non mi sento obbligato a credere che lo stesso Dio che ci ha dotato di senso, ragione ed intelletto intendesse che noi ne facessimo a meno. -- Galileo Galilei http

Bug#792290: .desktop files are used, symlinks to script not

should create the .desktop file myself, at best. But I haven't tried that. -- Salvo Tomaselli Io non mi sento obbligato a credere che lo stesso Dio che ci ha dotato di senso, ragione ed intelletto intendesse che noi ne facessimo a meno. -- Galileo Galilei http

Bug#793019: kde-config-sddm: Can't save changes

Package: kde-config-sddm Version: 4:5.3.2-1 Severity: grave Justification: renders package unusable Dear Maintainer, this package should probably depend on whatever plasma5 wants to use to elevate privileges. Right now, whenever I try to save the changes, I see a notification with a red icon,

Bug#793019: kde-config-sddm: Can't save changes

Package: kde-config-sddm Version: 4:5.3.2-1 Severity: grave Justification: renders package unusable Dear Maintainer, this package should probably depend on whatever plasma5 wants to use to elevate privileges. Right now, whenever I try to save the changes, I see a notification with a red icon,

Bug#793019: kde-config-sddm: Can't save changes

Package: kde-config-sddm Version: 4:5.3.2-1 Severity: grave Justification: renders package unusable Dear Maintainer, this package should probably depend on whatever plasma5 wants to use to elevate privileges. Right now, whenever I try to save the changes, I see a notification with a red icon,

Bug#793048: plasma-widget-smooth-tasks: Doesn't work with plasma 5

Package: plasma-widget-smooth-tasks Version: 1flupp0~hg20120610-2+b1 Severity: grave Tags: upstream Justification: renders package unusable Dear Maintainer, this package in the current state is useless, given the transition to Plasma 5. Whishlist bug for this was created a while ago

Bug#793048: plasma-widget-smooth-tasks: Doesn't work with plasma 5

Package: plasma-widget-smooth-tasks Version: 1flupp0~hg20120610-2+b1 Severity: grave Tags: upstream Justification: renders package unusable Dear Maintainer, this package in the current state is useless, given the transition to Plasma 5. Whishlist bug for this was created a while ago

Smooth tasks

Hello, I am co-maintainer of smooth tasks. Upstream has still activity but there are no commits in the direction of supporting plasma 5. Meanwhile, there is a plasmoid in plasma5 that does something similar, but I think overall it's rather crappy. For example it groups windows and has no option

<    1   2   3   4   5   6   7   8   9   10   >