Bug#871793: backupninja: excessively long report lines cause mail delivery failure

Package: backupninja Version: 1.0.1-2 Severity: normal The smarthost for my server rejected backupninja's emailed error report because it contained an error line in excess of 3000 characters. The line was an "Error:" line containing a rdiff-backup stack dump due to running out of disk space on

Bug#868804: xrdp: doesn't show the session after loggin with Xorg

Package: xrdp Version: 0.9.1-9 Followup-For: Bug #868804 The README.Debian suggests to use xserver-xorg-legacy. The opposite was true for me. After purging this package, and purging & reinstalling xrdp just for good measure (and manually killing xrdp process, since it was wedged), the issue was

Bug#851524: Building armhf image fwith qemu fails at bootstrapping stage if firmware section enabled

On January 15, 2017 6:39:27 PM Jason Heeris wrote: If I change the line: --archive-areas 'main firmware' Firmware is not a valid archive area in the Debian archive. Perhaps you meant non-free, where non-free firmwares are kept? ...to... --archive-areas 'main'

Bug#849342: [xrdp] xrdp-sesman: Fails to start Xorg

Interesting. Well, the system has a long and complicated history so this is unsurprising, I guess. Thanks for that insight. If it happens to any of my or systems, I'll know where to look. Ben P.S. This system also had a hardware-specific section for the console's monitor in

Bug#849342: [xrdp] xrdp-sesman: Fails to start Xorg

I do indeed (or did)! Purging it fixes the issue. Thanks for all of your help. I believe you can close this now, though it may be helpful to point users at potential issues with xserver-xorg-legacy in the README.Debian unless you work out a fix for that. I'm happy to report the MS Android client

Bug#849342: [xrdp] xrdp-sesman: Fails to start Xorg

track with my Xwrapper.config and polkit. I added that config a long time ago. I'll check and see if that option is even valid anymore, and if it is, then look at polkit configuration. Ben On Mon, Jan 2, 2017 at 4:02 PM, Ben Armstrong <synerg...@gmail.com> wrote: > > > On Sun, Jan 1, 201

Bug#849342: [xrdp] xrdp-sesman: Fails to start Xorg

On Sun, Jan 1, 2017 at 1:05 PM, Dominik George wrote: > > I had originally similar thoughts, but after many unsuccessful attempts > > to get the actual Xorg failure logged somewhere, I eventually gave up > > (e.g. param lines in sesman.ini to pass -logfile and its argument).

Bug#849827: live-build fails to build amd64 target

On January 1, 2017 4:47:39 PM "Peter.Stein" wrote: I actually had a bunch of comments, but suspected they would not be well received Try us. and thus tried to be diplomatic I must have missed that. ;) and productive by suggesting a step-by-step HOWTO. It's

Bug#849827: live-build fails to build amd64 target

On January 1, 2017 2:26:58 PM "Peter.Stein" wrote: I eventually figured out by trial and error how to get the iso to build. Not because of the documentation, but in spite of it. The resulting iso won't boot via GRUB2, but that's a GRUB issue not a live-build issue.

Bug#849342: [xrdp] xrdp-sesman: Fails to start Xorg

On January 1, 2017 12:48:05 PM Dominik George wrote: Hi, Other ideas? Hmm… not right now. I am positive that the only change that could be responsible for this can be the use of xauth that was introduced in this version, so maybe play around with that for a while. I

Bug#849342: [xrdp] xrdp-sesman: Fails to start Xorg

Yes, xauth is installed: $ apt-cache policy xauth xauth: Installed: 1:1.0.9-1 Candidate: 1:1.0.9-1 Version table: *** 1:1.0.9-1 990 990 http://lear.edennet:/debian stretch/main i386 Packages 500 http://lear.edennet:/debian sid/main i386 Packages 100

Bug#849342: [xrdp] xrdp-sesman: Fails to start Xorg

On Sun, Jan 1, 2017 at 6:25 AM, Dominik George wrote: > Control: tags -1 + moreinfo > > Hi Ben, > > > Dec 25 15:49:14 lear xrdp-sesman[15632]: (15632)(-148605184)[INFO ] Xorg > :10 -auth .Xauthority -config xrdp/xorg.conf -noreset -nolisten tcp > > Can you please try running

Bug#849827: Fwd: Re: Bug#849827: live-build fails to build amd64 target

User error. This bug should be closed. --- Forwarded message --- From: Ben Armstrong <sy...@sanctuary.nslug.ns.ca> Date: December 31, 2016 5:45:12 PM Subject: Re: Bug#849827: live-build fails to build amd64 target To: Peter.Stein <peter.st...@comcast.net>, sub...@bugs.deb

Bug#849827: live-build fails to build amd64 target

You are misusing the --linux-packages option which is only to specify kernel and kernel modules. See live-manual and use package lists instead. Ben On December 31, 2016 4:45:26 PM "Peter.Stein" wrote: Package: live-build Version: 1:20161216 I configure with: lb

Bug#849827: live-build fails to build amd64 target

On December 31, 2016 6:10:55 PM "Peter.Stein" wrote: I'm only seeing --linux-packages as a possible option for specifying configuration PACKAGES. Is there another option in this list that's appropriate? No. You use package lists instead. As for what's in that

Bug#849342: [xrdp] xrdp-sesman: Fails to start Xorg

Package: xrdp Version: 0.9.1-1 Severity: normal --- Please enter the report below this line. --- After upgrading to 0.9.1-1, Xorg is no longer started when xrdp-sesman runs. Downgrading back to xrdp_0.9.1~20161126+git589b29f-1 resolves the issue. Here's what is in journalctl -u xrdp-sesman

Bug#817735: xpilot-extra: diff for NMU version 4.7.2+nmu2

-12-21 11:38:02.0 +0100 +++ xpilot-extra-4.7.2+nmu2/debian/control 2016-12-18 12:57:38.0 +0100 @@ -2,7 +2,7 @@ Section: games Priority: optional Maintainer: Ben Armstrong <sy...@sanctuary.nslug.ns.ca> -Build-Depends-Indep: debhelper (>= 4.0.0) +Build-Depends-In

Bug#842580: chromium: Crash with: free(): invalid next size (fast): 0xed320dd0

Package: chromium Version: 53.0.2785.143-1 Severity: normal Chromium, with all extensions and plugins disabled, and no apps running, reliably crashes for me on some sites. One example is Facebook (after about 10-20 seconds of interacting with the site). Another is using habitica-chat-extension

Bug#842578: quassel-core: Please inform Postgresql users, qt plugin needs to be upgraded

Package: quassel-core Version: 1:0.12.4-2 Severity: normal I recently upgraded the system hosting my quassel-core from Jessie to Stretch. Upon upgrading, it no longer saw my postgresql database. Instead, it defaulted to sqlite and wanted to guide me through the setup process again when I first

Bug#842070: libgtk-3-0: Upgrade breaks gvim: Gtk-CRITICAL **: gtk_widget_set_size_request: assertion 'width >= -1' failed

Simon, Here is the info you requested ... On 25/10/16 03:14 PM, Simon McVittie wrote: What 'guiopts' do you use in gvim? (type ":set guiopts?" into gvim) Do you mean ":set guioptions?" If so: guioptions=aegimrLtTf Which Gtk theme are you using? I ask because I use vim.gtk3 myself, and I

Bug#842070: libgtk-3-0: Upgrade breaks gvim: Gtk-CRITICAL **: gtk_widget_set_size_request: assertion 'width >= -1' failed

Package: libgtk-3-0 Version: 3.22.2-1 Severity: normal Dear Maintainer, * What led up to the situation? I upgraded from libgtk-3-0 3.22.1-1 to 3.22.2-1. * What exactly did you do (or not do) that was effective (or ineffective)? I attempted to open gvim (vim.gtk3 -g), with or

Bug#606337: po4a: [text] Add support for SiSU markup

On September 14, 2016 1:47:00 PM Ralph Amissah wrote: Please close bug (and do not apply patch). As far as I understand it the patch was not needed, and ended up being forgotten about. Ben please feel free to chime in. I take your word for it. Your memory about

Bug#833173: O: eeepc-acpi-scripts -- 00cfc39420956e29eab8942cc6c0b1a4

Package: wnpp Severity: normal I intend to orphan the eeepc-acpi-scripts package. I have retired, and nobody remains from the original debian-eeepc team to look after it, since the project officially ended years ago. Thanks, Ben Armstrong The package description is: role::plugin, works

Bug#819369: linux-image-4.4.0-1-amd64: kernel oops in DRM/Intel switching VTs triggered by light-locker

. Thanks, Ben Armstrong -- Package-specific info: ** Version: Linux version 4.4.0-1-amd64 (debian-ker...@lists.debian.org) (gcc version 5.3.1 20160307 (Debian 5.3.1-11) ) #1 SMP Debian 4.4.6-1 (2016-03-17) ** Command line: BOOT_IMAGE=/boot/vmlinuz-4.4.0-1-amd64 root=UUID=b7d082d8-c134-477f-8b6d

Bug#819350: bugs.debian.org: 500 on attempt to view bug #819083

Package: bugs.debian.org Severity: normal I believe my system is affected by: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=819083 However, I cannot view this bug because it returns an HTTP status 500. I can view some other bugs successfully, just not this one. Meanwhile, I'll see if I can

Bug#812358: debian-live: Please add gparted

On 28/01/16 03:34 AM, Christian Brunotte wrote: > An official "Debian Rescue CD" would seem an unnecessary waste of > storage and buildd resources if it were 99% identical with the "Live > CD". If it contained the Live CD and additional tools, on the other > hand, who would still be downloading

Bug#812358: debian-live: Please add gparted

On Jan 26, 2016 5:21 PM, Don Raikes wrote: > When I do > $ apt-get live-images > > From within jesse, I see a /usr/share/live/images/rescue folder and except > for about 4 packages it seems to build fine. > > Couldn't we just fixup those few packages and/or remove them

Bug#812358: debian-live: Please add gparted

used in blends for their specific stuff.) > > What I mean is that my article begins with me trying to make a > tasksel-rescue package and it turns out that this package name not > even exists. > > 2) Ben Armstrong wanted to reuse some of the packages I used on > Rescatux. I warned him

Bug#812358: debian-live: Please add gparted

On 23/01/16 07:59 AM, Iain R. Learmonth wrote: > Ben - blends packaging needs to happen within the blends project, and a > mailing list could also be created in that project. If there is a packaging > project alongside, then it would make sense to create a seperate Alioth > project, but the blends

Bug#812358: debian-live: Please add gparted

On 22/01/16 12:46 PM, Christian Hammers wrote: > Package: debian-live > Version: 8.2.0-amd64-xfce-desktop > Severity: wishlist > > Hello > > Please add "gparted" to the Debian Live CD. > > Live CDs are greate to rescue broken systems or to shrink/enlarge > root file systems etc. In such cases the

Bug#808413: xpilot-extra: Depends on virtual package "perl5" which is gone with perl/5.22

On 19/12/15 05:00 PM, gregor herrmann wrote: > Package: xpilot-extra > Version: 4.7.2 > Severity: serious > Tags: sid patch > > Justification: package uninstallable > User: debian-p...@lists.debian.org > Usertags: perl-5.22-transition > > The perl 5.22 transition just started (see >

Bug#807972: live-build: For i386 no longer include 586 kernel flavour

Package: live-build Version: 5.0~a11-2 Severity: normal With the upload of linux 4.3.1-1 on Dec. 13, the 586 kernel flavour for i386 architecture has been removed. Please remove this flavour from the default flavours for i386, the flavours included with the installer, and also the doc (see

Bug#802947: dolphin-emu: Initially stuck controller axes, cleared by moving and restarting

Package: dolphin-emu Version: 5.0~rc33+dfsg-1 Severity: normal Dear Maintainer, * What led up to the situation? Upgrading from dolphin-emu 4.0.2 to 5.0, which I did to solve other issues with 4.x. I'm happy with the upgrade except for this one issue, for which I have a workaround. * What

Bug#800238: xletters - seeking new maintainer

like to take over xletters. Thanks, Ben Forwarded Message Subject:Bug#800238: xletters: Please migrate a supported debhelper compat level Resent-Date:Sun, 27 Sep 2015 15:52:44 + Resent-From:ni...@thykier.net Resent-To: Ben Armstrong <

Bug#798004: xletters: Non-standard charset makes some characters untypeable and wrongly displayed.

Thanks for your report, On 04/09/15 08:34 AM, chill3 wrote: > I've installed xletters in Spanish, but, due to an incorrect charset probably > on the translation, the characters on the upper half of the ASCII character > table don't display correctly. > > For each character on that half, the

Bug#765749: icedove: empty folder pane

Package: icedove Version: 38.1.0-1 Followup-For: Bug #765749 Steps to reproduce are not 100% reliable: - With View > Folder > Unified selected, - Open an MS Exchange Server IMAP account - Delete a subfolder (was Projects > 068) - Open Trash - A passive error dialog shows: - "The current

Bug#765749: icedove: empty folder pane

Package: icedove Version: 38.1.0-1 Followup-For: Bug #765749 Hi, Switching to View > Folder > Unread, restarting icedove, and switching back to View > Folder > Unified works around the issue for me just as others have reported. I believe this is because there is a problem with one or more

Bug#730084: Potential removal - python-irc

On 29/08/15 07:12 PM, Iain R. Learmonth wrote: ... Ben Armstrong sy...@sanctuary.nslug.ns.ca (xpilot-ng-common) ... I'm not familiar with these packages that are depending on python-irc, but if you would like to continue to have them depend on python-irc, please update bug #730084

Bug#792258: putty: Truetype font rendering very CPU intensive

Package: putty Version: 0.64-1 Severity: normal Truetype font rendering is very CPU intensive. This was equally the case with 0.63, so is not a regression in the latest version, but I only today got around to testing properly. When my window is maximized on a 1280x1024 display with

Bug#792258: putty: Truetype font rendering very CPU intensive

Package: putty Version: 0.64-1 Followup-For: Bug #792258 I underreported actual CPU usage. Here are the exact steps to test, and comparisons between putty with Truetype, putty without Truetype (fixed), and urxvt with Truetype. I also switched Truetype fonts to match what I'm using with urxvt. -

Bug#719601: ITP: libjs-jquery-datatable

On 15/04/15 05:20 PM, Ole Streicher wrote: But could you, Ben, or Martin sponsor? Martin Ole, I'm sorry. I had the best of intentions in initially offering to help, but my project that required this has subsequently been shelved and other priorities added to the top of my queue. I had hoped to

Bug#783364: cdimage.debian.org: on live, kdm/lightdm fail when booting with 'splash'

Package: cdimage.debian.org Severity: important Blocking bug for #782456 (plymouth). -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#783240: blends-doc: Please add URLs for the Blends team online

Package: blends-doc Version: 0.6.92.2 Severity: minor Please add sufficient URLs for the reader to be able to locate Blends support resources online. I noticed in my review there are no links to the wiki page nor the irc channel: https://wiki.debian.org/DebianPureBlends Linked already within

Bug#780025: dm-tool: lock locks a new VT instead of current VT

Package: lightdm Version: 1.10.3-3 Severity: normal I wanted to use dm-tool to debug a problem I'm having (lxpanel Lock screen does not lock the screen, which I will report separately on that package) so I tried dm-tool lock to verify if locking works at all. Unfortunately, instead of locking

Bug#780025: dm-tool: Document light-locker needed for dm-tool lock

Package: lightdm Version: 1.10.3-3 Followup-For: Bug #780025 In #780024 I discovered the failured the root cause of my inability to lock the screen was that I did not have xscreensaver installed and did not replace it with an alternative screen locker. It appears that light-locker is the

Bug#780024: lxsession-logout: Improve man page to refer to helper scripts

Package: lxsession Version: 0.5.1-2 Followup-For: Bug #780024 After direct examination of the source, I discovered lxsession-logout calls lxlock to perform the Lock Screen function. In turn, the lxlock helper script man page tells me: lxlock is a simple script to lock the session, using third

Bug#780024: lxsession-logout: Fails to lock screen

Package: lxsession Version: 0.5.1-2 Severity: important Pressing the Lock Screen button does not lock the screen. Unfortunately, nothing at all is logged, neither to stdout/stderr nor to any user or system log that I can locate. Being able to lock the screen is a fairly important function of the

Bug#780025: [Pkg-xfce-devel] Bug#780025: dm-tool: lock locks a new VT instead of current VT

On 08/03/15 10:25 AM, Yves-Alexis Perez wrote: Actually that's not what happens. dm-tool locks will just call the Lock() dbus method on the current seat. In response to that, lightdm will emit a dbus signal for locking, then switch vt to display a login screen. Sure. Makes sense. And aligns

Bug#777680: Following my instructions could expose password

Be careful following my instructions. If you don't first chmod 600 ~/.nut-monitor/favorites.ini (touch it first if it doesn't exist) you risk exposing the password saved there due to #06. -- Sent from my Android device with K-9 Mail. Please excuse my brevity.

Bug#777707: nut-monitor: please minimize to tray when window closed instead of exiting

Package: nut-monitor Version: 2.7.2-1.1 Severity: wishlist For applets that live in the system tray, it is common practice to intercept a close window action and minimize to system tray rather than terminating the application. Please make NUT-Monitor behave this way, as otherwise an unsuspecting

Bug#777706: nut-monitor: insecure storage of password

Package: nut-monitor Version: 2.7.2-1.1 Severity: normal After discovering how to save and use Favorites with NUT-Monitor (see #777680 for the steps I performed), I wanted to know how and where NUT-Monitor stored its configuration. I found the configuration in ~/.nut-monitor/favorites.ini and

Bug#777706: nut-monitor: password is stored only mildly obfuscated

Package: nut-monitor Version: 2.7.2-1.1 Followup-For: Bug #06 I have bumped the severity to critical, as this introduces a security hole on the system. The password is stored world-readable by default and only mildly obfuscated (base64, not crypted as I had assumed, though even if it had been

Bug#777706: nut-monitor: Inform user of compromised passwords

Package: nut-monitor Version: 2.7.2-1.1 Followup-For: Bug #06 Thinking this through a bit more, it's not sufficient to just fix the permissions on the file. The user should be notified if they have passwords stored insecurely and warned to change them, as they should be considered

Bug#777680: nut-monitor: missing documentation

Package: nut-monitor Version: 2.7.2-1.1 Severity: normal NUT-Monitor is missing documentation. NUT-Monitor -h provides insufficient help to figure out how to use favorites. The application is fussy about the order of operations, so I had to determine this empirically. I have put both my goal and

Bug#775436: ITP: xlennart -- An XBill fork but with Lennart and SystenD instead of Bill and Wingdows

On 16/01/15 08:15 AM, Stephan Seitz wrote: On Fri, Jan 16, 2015 at 07:32:41AM +1100, Riley Baird wrote: (Also, in any case, don't you think that this game is going a little too far? It's fine to be opposed to systemd, but don't do to Lennart Well, do you see a difference to the original game

Bug#775436: ITP: xlennart -- An XBill fork but with Lennart and SystenD instead of Bill and Wingdows

to enter Debian or not. So yes, it's a necessary part of the process. On 01/16/2015 03:48 PM, Ben Armstrong wrote: Do you honestly not see the difference between poking fun at an upstream that is at the center of an ongoing controversy vs. poking fun at a competitor? 1. Everybody (who

Bug#775436: ITP: xlennart -- An XBill fork but with Lennart and SystenD instead of Bill and Wingdows

On 16/01/15 11:34 AM, Markus Koschany wrote: My personal opinion is that both XBill and xlennart are mildly entertaining and it is rather immature to depict living people as a virus. The message is either silly or offensive. While we're talking about personal opinions, and clarifying for

Bug#775436: ITP: xlennart -- An XBill fork but with Lennart and SystenD instead of Bill and Wingdows

Dmitry, On 16/01/15 12:17 PM, Dmitry Yu Okunev wrote: I see. By the way, it's _not my_ changes. I'm just a Debian user that tries to get more experience of Debian packaging. I found the project (xlennart) and just wanted to make a package and find a sponsor. I didn't expected that this will

Bug#775436: ITP: xlennart -- An XBill fork but with Lennart and SystenD instead of Bill and Wingdows

On 16/01/15 01:33 PM, Dmitry Yu Okunev wrote: Isn't it premature? Shouldn't abandoned ITP be converted to RFP. If I close the bug it may be duplicated by somebody else, soon. Sorry for my newbie-ness. Closing the bug doesn't make it vanish from the system. People will still be able to find it

Bug#775436: ITP: xlennart -- An XBill fork but with Lennart and SystenD instead of Bill and Wingdows

On 16/01/15 01:33 PM, Dmitry Yu Okunev wrote: Isn't it premature? Shouldn't abandoned ITP be converted to RFP. If I close the bug it may be duplicated by somebody else, soon. Sorry for my newbie-ness. Closing the bug doesn't make it vanish from the system. People will still be able to find it

Bug#775101: tuxpaint-data: Include osk and im data to fix --onscreen-keyboard

Package: tuxpaint-data Version: 1:0.9.22-1 Severity: important The osk and im directories have been omitted from /usr/share/tuxpaint. They need to be included. Thanks to Pere Pujal on irc for this report. Without osk, if you specify tuxpaint --onscreen-keyboard, select the text tool and click on

Bug#775103: unblock (pre-approval): tuxpaint/1:0.9.22-2

Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package tuxpaint This unblock fixes #775101, which is particularly important to touchscreen users, and includes remaining missing files that were accidentally omitted as

Bug#772948: putty: bolded text disappears due to accidentally changed default

Package: putty Version: 0.63-8 Severity: normal Thanks to David G. on #debian @ irc.oftc.net for bringing this to my attention and helping with testing and finding the commit that fixes the issue. He first discovered this bug using Windows PuTTY 0.63 connecting to a Debian wheezy system running

Bug#769339: gcompris cannot execute tuxpaint

On 12/11/14 09:14 PM, Ben Armstrong wrote: I'm filing a separate bug, myself, on tuxpaint to fix the doc. See #769368 for this. Ben -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#769339: gcompris cannot execute tuxpaint

Leopold, thanks for the report. Yann, On 12/11/14 07:32 PM, Yann Dirson wrote: OTOH, neither the manpage nor --help explain what this value for --fullscreen should be. It rather looks like a bug in recent tuxpaint: downgrading to 0.9.21-1.1 (and tuxpaint-config 0.0.12-3 accordingly) shows

Bug#769339: gcompris cannot execute tuxpaint

On 12/11/14 08:42 PM, Ben Armstrong wrote: Is that enough to get gcompris working again? If so, I would be inclined to drop the severity to normal and after I've received a patch from upstream for both the help and the man page, upload a new version with the patch applied. I'm pretty sure it's

Bug#769368: tuxpaint: Describe required argument in --fullscreen man/help

Package: tuxpaint Version: 1:0.9.22-1 Severity: normal When you type tuxpaint --fullscreen, tuxpaint does not start and this error message is shown: Command line option '--fullscreen' needs a value In addition to confusing users who launch tuxpaint from the command-line, this change in

Bug#734467: Broken systemd unit file?

It looks like the reason /home/debian-transmission is even looked at is, after upgrading from sysvinit-core to systemd-sysv, the unit file doesn't obey the options specified in /etc/default/transmission-daemon, so the daemon can't find its config anymore:

Bug#739980: [Debian-eeepc-devel] Bug#739980: RE: eeepc-acpi-scripts doesn't work any more after reboot

On 03/10/14 03:55 AM, johan laenen wrote: I can confirm this exact behavior on an 901 eeepc.The 4 hotkeys on top don't work after a boot. When I dpkg-reconfigure eeepc-acpi-scripts everything is ok. A reboot disables the hotkeys once more. As I pointed out to Hans in #760876, this package

Bug#739980: [Debian-eeepc-devel] Bug#739980: eeepc-acpi-scripts doesn't work any more after reboot

On 03/10/14 01:00 PM, johan laenen wrote: Solved! systemctl status acpid said acpid was inactive! I did a systemctl enable acpid, rebooted my 901, and everything is working! I don't know much about the debian processes, I don't know how to do an upload. Can someone move the package back

Bug#763565: cinnamon: Input stops working until cinnamon is HUPed and restarts

Package: cinnamon Version: 2.2.16-3 Severity: normal Dear Maintainer, Occasionally, input stops working, i.e. keyboard and mouse fail to control the application. * What led up to the situation? All incidents so far were discovered when running Minecraft in fullscreen mode. So far, other

Bug#762342: task-cinnamon-desktop: Please turn on display of Cinnamon desktop task

On 23/09/14 02:36 PM, Joey Hess wrote: One way might be to decide if a given DE is fundamentally different than the others in some way, and if not, only include one of a set that share common characteristics. So, maybe only gnome and not cinnamon since it's a rather near cousin (AFIACS).

Bug#762342: task-cinnamon-desktop: Please turn on display of Cinnamon desktop task

Package: tasksel Version: 3.26 Severity: normal Please turn on display of the Cinnamon desktop task. I have tested building Jessie live images with Cinnamon included and it seems to already provide a usable desktop. It would be useful for testers to be able to see Cinnamon so they can try it and

Bug#762345: task-mate-desktop: typo in tasks/mate-desktop Relevance: field

Package: tasksel Version: 3.26 Severity: normal Tags: patch There is a typo in the tasks/mate-desktop file. I have attached a patch to fix it. diff -Nru tasksel-3.26/tasks/mate-desktop tasksel-3.26+nmu1/tasks/mate-desktop --- tasksel-3.26/tasks/mate-desktop 2014-09-20 10:57:09.0 -0300 +++

Bug#761598: task-mate-desktop: pull in lightdm

No, you need to put the virtual package second, otherwise an arbitrary package providing it will be selected, which makes it unpredictable. Ben

Bug#712696: tasksel: Task for cinnamon

On 06/09/14 08:56 AM, Margarita Manterola wrote: Cinnamon includes a meta package (cinnamon-desktop-environment) that contains everything the task should contain. I'm attaching a diff that creates the task package with that dependency. I hope this can get applied before the freeze. I made

Bug#758218: live-build: Packages helper includes packages excluded by tasksel

On 22/08/14 12:24 PM, Daniel Baumann wrote: having though about this again, i think we should do two things: * keep the Packages helper as is - it's a 'stupid' tool that just does exactly what told: trying to install all packages matching a certain criteria without

Bug#758724: vit: Depend on taskwarrior not transitional task package

Package: vit Version: 1.2-1 Severity: normal Please make vit depend on 'taskwarrior' instead of 'task' to allow the transitional package to be removed. Thanks, Ben -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact

Bug#758218: live-build: Packages helper includes packages excluded by tasksel

Package: live-build Version: 4.0~alpha39-1 Severity: important The helper /usr/share/live/build/bin/Packages uses dctrl-tools to achieve what d-i does with tasksel to select 'standard' (or other) priority packages. Unfortunately, this breaks current builds against jessie, and has been breaking

Bug#758218: live-build: Packages helper includes packages excluded by tasksel

Package: live-build Version: 4.0~alpha39-1 Followup-For: Bug #758218 Sorry, forgot to include my patch in the original submission. Now attached. From 2e9cfe4811435025abd9a6a6af9a4d48f745eefc Mon Sep 17 00:00:00 2001 From: Ben Armstrong sy...@debian.org Date: Fri, 15 Aug 2014 09:51:22 -0300

Bug#758218: live-build: Packages helper includes packages excluded by tasksel

On 15/08/14 12:53 PM, Daniel Baumann wrote: On 08/15/2014 02:52 PM, Ben Armstrong wrote: has been breaking them for months[0] because it fails to exclude certain packages that tasksel excludes (those that are either in a 'lib' section or non-main section). i still think that this is a very

Bug#758218: live-build: Packages helper includes packages excluded by tasksel

On 15/08/14 01:14 PM, Daniel Baumann wrote: (without having tried^diffed the two outputs) the idea would be that you would only see a line: W: automatically excluding packages: libdb5.1 (or something like that) in the current case, and if that package is gone from testing eventually, you

Bug#757755: xpilot-ng: Please update to use wxpython3.0

On 11/08/14 02:41 AM, Olly Betts wrote: We're aiming to migrate the archive to using wxpython3.0 instead of wxwidgets2.8, and hope to drop wxwidgets2.8 before jessie is released. I've rebuilt xpilot-ng with the attached patch, and tested it works with wxPython 3.0, and everything seems to be

Bug#754274: live-config-sysvinit: inittab rewrite fails for ttyS0

Niels, Your patch breaks the normal use case (non-serial autologin) and is unnecessary anyway. You should simply customize live-config as explained in the manual to implement whatever non-standard behaviors you want, if the standard behaviors don't suit your needs. Ben -- Sent from my

Bug#754274: live-config-sysvinit: inittab rewrite fails for ttyS0

I see. I'll try it when I have a moment. -- Sent from my Android device with K-9 Mail. Please excuse my brevity.

Bug#624122: Better workaround

We've had numerous reports on irc that making apt prefer gz is a better workaround for this issue (i.e. actually works, unlike some other things suggested above :) apt-get -o 'Acquire::CompressionTypes::Order::=gz' update Or add this to /etc/apt/apt.conf : Acquire::CompressionTypes::Order:: gz;

Bug#742286: calvin.cow has tab characters in his hair

Package: cowsay Version: 3.03+dfsg1-4 Severity: minor Tags: patch The calvin.cow file has tab characters in his hair. These are normally invisible, but when output on irc in irssi, they become visible as inverted capital I characters. I have attached a patch correcting this problem. -- System

Bug#742286: Several cow files include tab characters

Package: cowsay Version: 3.03+dfsg1-4 Followup-For: Bug #742286 I have attached an updated patch superceding my previous patch which fies three different cow files, each with tabs in them: calvin.cow cock.cow moofasa.cow In the case of the first two, I simply removed the trailing tabs. In the

Bug#739980: [Debian-eeepc-devel] Bug#739980: eeepc-acpi-scripts doesn't work any more after reboot

Please include output of: lsmod |grep eeepc -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#660747: New Forwarded to from new issues system

Package: task Followup-For: Bug #660747 With 2.3.0 now poised to migrate to testing in a number of days, I went reviewing old bugs that are still on the books to see how we're doing with them. I followed the link to the upstream issue system on this bug and it broke. It looks like the URL in the

Bug#738326: live-build installs extra packages (suggests or based on source package instead of binary)

On 09/02/14 03:38 AM, Daniel Dickinson wrote: Package: live-build Version: 3.0.5-1 Severity: normal live-build is adding gnuplot to my images even though no package in Depends or Recommends for gnuplot is in package-lists nor is even being installed via apt-get. Please include a log of

Bug#719601: What is the status of the packaging?

, and this package includes jquery.datatable.min.js for some extended functionality. I would like to replace this by this Debian package. What is the current status here? i started the packaging here [1] and mailed with Ben Armstrong who is willing (or was ;) ) to sponsor it but i lost track I'll take

Bug#737567: mopd: Fails to handle Elf32 image: NetBSD 6.1.3 vax

Package: mopd Version: 1:2.5.3-21 Severity: normal Hi, I tried mopd with the NetBSD 6.1.3 (latest release) vax bootloader. Apparently Debian mopd doesn't support it. When I used installation/netboot/boot from NetBSD 6.1.3, mopd claimed to send it, but the VAX (VAXstation 4000 VLC) could not use

Bug#721647: taskd now released

See: http://taskwarrior.org/news/186 After three years, 400 commits, a false start, a wrong turn, and a lengthy beta, Taskserver is finally released. ... Taskwarrior 2.3.0 (also released today) supports Taskserver. Also, note that jwilk put taskwarrior 2.3 in experimental recently. So

Bug#733825: apt-listchanges: missing dependency on dpkg-dev

Package: apt-listchanges Version: 2.85.12 Severity: serious apt-listchanges now needs a dependency on dpkg-dev. If you don't have dpkg-dev installed, when apt-listchanges attempts to execute dpkg-architecture it results in this traceback and error: Traceback (most recent call last): File

Bug#593303: acpi-support: screensaver not activated until seconds after resuming

Package: acpi-support Version: 0.141-2 Followup-For: Bug #593303 I agree that it is not OK to not wait for the screensaver before suspending or hibernating. Please revert this patch. What happens both in my case and another user on Wheezy reporting via irc today is the screensaver fails to

Bug#725781: xserver-xorg-video-intel: Failed to submit batch buffer, expect rendering corruption

Package: xserver-xorg-video-intel Version: 2:2.21.15-1+b2 Followup-For: Bug #725781 The upstream bug for this is: https://bugs.freedesktop.org/show_bug.cgi?id=59771 A couple of patches to libdrm were provided by upstream, but reports by testers are that neither of them fixed the problem. I'm

Bug#725781: xserver-xorg-video-intel: Failed to submit batch buffer, expect rendering corruption

Package: xserver-xorg-video-intel Version: 2:2.21.15-1+b2 Followup-For: Bug #725781 Correction, we *can* use SNA. My method for configuring was: X -configure (Interestingly, in my case this is not without errors, but it generates a usable config for my purposes; I'll check the error later/file

Bug#725781: xserver-xorg-video-intel: Failed to submit batch buffer, expect rendering corruption

On 11/11/13 01:39 PM, Julien Cristau wrote: Unreviewed and testers said it doesn't work aren't exactly the same. Which is it? A bit of both. Chris Wilson provided two patches. After applying the first patch, one tester said the problem was fixed. Chris then came up with a second patch which he

Bug#725781: xserver-xorg-video-intel: Failed to submit batch buffer, expect rendering corruption

Package: xserver-xorg-video-intel Version: 2:2.21.15-1+b2 Followup-For: Bug #725781 Neither the latest xserver-xorg-video-intel nor new kernel (3.11.6-2 unstable or 3.12~rc7-1~exp1 experimental) fix the problem. Furthermore, although my workaround switching the xrandr parameters back and forth

  1   2   3   4   5   >