Bug#1002741: Excessive messages regarding accessibility bus

Package: thunar-volmanVersion: 4.16.0-1Severity: importantX-Debbugs-Cc: dbrazz...@snet.net Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate ***    * What led up to the situation?Start Thunar   * What exactly did you do (or not do) that was effective (or 

Bug#1001720: Fixed by accessing page from remote machine

When accessing the page from the localhost only 43 directories of 197 were displayed in the'Rock' directory. After accessing the page from a remote host all 197 directories weredisplayed and the musicindex cache directory began to be populated as designed.Very weird.

Bug#1001720: Cache directory not populated, directory omissions

Package: libapache2-mod-musicindexVersion: 1.4.1-3.1Severity: importantX-Debbugs-Cc: dbrazz...@snet.net Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate ***    * What led up to the situation?Run apache2 with mod-musicindex configured    * What exactly

Bug#1001268: snmpd fails to start at boot if network is not online

Package: snmpdVersion: 5.9.1+dfsg-1Severity: importantX-Debbugs-Cc: dbrazz...@snet.net Dear Maintainer,    * What led up to the situation? After boot snmpd not running   * What exactly did you do (or not do) that was effective (or     ineffective)?   * What was the outcome of this action?Message

Bug#992583: Program works as designed

'getpwnam' retturns 'Success' even on non-existent user names. This was confusing but the program does error out with exit code 1. OK to close.

Bug#992583: 'chown' example program returns success but file ownership not changed

Package: manpages-devVersion: 5.10-1Severity: normal Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate ***    * What led up to the situation?Compiling and running the example program   * What exactly did you do (or not do) that was effective (or     

Bug#992377: manpages-dev

Package: manpages-dev Version: 5.10-1 Severity: normal X-Debbugs-Cc: dbrazz...@snet.net Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate ***    * What led up to the situation? Tried to compile the man 2 add_key example program    * What exactly did

Bug#984956: Still occurring here with 4.1.0-9

I installed openmpi-{bin, common} V4.1.0-9 from unstable and still have the problem. mpirun.openmpi -host X:2,Y:2 hostname results in the same ORTE_ERROR_LOG messagesfollowed by FORCE-TERMINATE.

Bug#912693: streamtuner2: Won't start - python crash

Package: streamtuner2 Version: 2.2.0+dfsg-1 Severity: normal Dear Maintainer, streamtuner2 didn't start from the Multimedia Applications menu. Trying to start it from the command line showed this: streamtuner2 Traceback (most recent call last): File "/usr/bin/streamtuner2", line 12, in

Bug#906662: backuppc: BackupPC_Link reports MakeFileLink -5 errors

Package: backuppc Version: 3.3.1-5 Severity: normal Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? Run backup * What exactly did you do (or not do) that was effective (or ineffective)?

Bug#903217: backuppc: Web interface status page doesn't show graphs

Package: backuppc Version: 3.3.1-5 Severity: normal Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? Select status page * What exactly did you do (or not do) that was effective (or ineffective)?

Bug#884262: Problem still exists in testing / unstable

Problem still exists on buster

Bug#901965: Also affects upowerd

Over 100,000 messages from upowerd, the same two repeated over and over until upowerservice is stopped: upowerd[1281]: unhandled action 'bind' on /sys/devices/pci:00/:00:1a.0/usb3/3-1/3-1.2/3-1.2:1.0 upowerd[1281]: unhandled action 'unbind' on

Bug#901965: bluez: hid2hci fails, spams syslog with failed exit code 1 messages

Package: bluez Version: 5.49-4Severity: normal Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate ***    * What led up to the situation?     boot       * What exactly did you do (or not do) that was effective (or     ineffective)?    * What was the outcome

Bug#787289: Rearing it's ugly head again

The last three days have given HTTP connection timeouts (500) on several mirrors. Direct connection to 'ftp.us.debian.org' works, but using acng fails.

Bug#881422: Seems like some signal callbacks are causing the wait

I found some signal mask stuff that must be the source of the futex waits in do_changelog stuff from the source. Looking at the source code now.

Bug#881422: aptitude changelog hangs waiting on futex

Package: aptitude Version: 0.8.9-1 Severity: normal Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? aptitude changelog [ package name ] * What exactly did you do (or not do) that was effective (or

Bug#873620: util-linux: dmesg stops if kernel ring buffer fills

Package: util-linux Version: 2.29.2-4 Severity: normal Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? dmesg -T * What exactly did you do (or not do) that was effective (or ineffective)?

Bug#395295: This could probably be closed

ll /dev/nbd* brw-rw 1 root disk 43, 0 Jul 6 08:31 /dev/nbd0 brw-rw 1 root disk 43, 16 Jul 6 08:31 /dev/nbd1 brw-rw 1 root disk 43, 160 Jul 6 08:31 /dev/nbd10 brw-rw 1 root disk 43, 176 Jul 6 08:31 /dev/nbd11 brw-rw 1 root disk 43, 192 Jul 6 08:31 /dev/nbd12 brw-rw 1

Bug#865223: 'DAEMON_ARGS' is missing

The accton command requires a path to the accounting file as an argument. This start clause in the script refers to 'DAEMON_ARGS' which was not defined. This patch fixes it: --- acct~ 2017-06-16 08:53:33.0 -0400 +++ acct2017-06-26 06:41:10.315888206 -0400 @@ -19,6 +19,7 @@

Bug#760148: Deleted Fedora partition

This particular problem went away after removing the Fedora partition.

Bug#760148: CPU grind occurs on multi-boot

I get this long running effect one system which contains Debian, Fedora and Windows XP. The longest time is spent with grub-mount running and much I/O. >From the output (systemd log) I see the gap between timestamps when mounted tests and subtests are run against the Fedora partition: Sep 27

Bug#832077: gvim is affected by this bug

Starting gvim from terminal emits: (gvim:25334): Gtk-WARNING **: GtkWindow 0x81964260 is drawn without a current allocation. This should not happen. Several times. I am on testing distribution, libgtk-3-0 version 3.21.5-3:i386. Fedora 24 version is 3.20.9-1 and does not emit the warnings.

Bug#832775: OK to close

I forgot about the '-forever' parameter. From 'man x11vnc': Keep listening for more connections rather than exiting as soon as the first client(s) disconnect. Same as -many Working as designed, sorry for the noise. OK to close.

Bug#833018: xstartup file, non-GUI

Hello, Ola! The parts of the file after the 'exec' line are never executed. I should have pointed out that my working xstarted opts for the 'regular desktop session' by uncommenting the 3 lines at the beginning. Those lines are, by default, commented out and xstartup only executes an xterm.

Bug#829696: Disregard last post

Fixed by repositioning panel to very top after unlocking.

Bug#829696: Different problem, same component(s)?

I am having a problem with xfce4-panel not positioned on the top row of the screen at startup. The result is that maximized windows over(under)lap the panel in for a few pixels. This effect obscures title bars on open xfce4-terminals and tab labels in chromium. I don't know if this is an

Bug#729614: Thanks for your work on this

As far as the restart failure is concerned, I have noticed it as well. Atop won't start after reboot if the atop file for the current day exists. The 'daily.log' or 'atop.log' (Fedora) indicates 'existing file has incompatible header'. I will file a separate bug for that and look into it.

Bug#832889: OK to close

This is a kernel bug, filed here: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=832905

Bug#832775: OK to close, this is a kernel bug

The same stack trace appears at boot time. Bug filed against 'linux-image-686-pae': https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=832905

Bug#833018: vncconfig not run for regular desktop

Package: vnc4server Version: 4.1.1+X4.3.0-39 Severity: important Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? VNC regular desktop session has no cut & paste * What exactly did you do (or

Bug#832905: Also filed on freedesktop

https://bugs.freedesktop.org/show_bug.cgi?id=93509

Bug#832905: Fedora report at same address from intel video driver

The following Fedora bug hit the exact same location in the drm driver, was filed against 'xorg-x11-drv-intel', which is Fedora's version of 'xserver-xorg-video-intel' I believe: https://bugzilla.redhat.com/show_bug.cgi?id=1313323

Bug#832905: linux-image-686-pae: kernel warning at drm_irq.c

Package: linux-image-686-pae Version: 4.6+74 Severity: wishlist Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? Vinagre session to x11vnc * What exactly did you do (or not do) that was effective (or

Bug#832894: vnc4server

Package: vnc4server Version: 4.1.1+X4.3.0-39 Severity: wishlist Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? Tried to start regular X session via ~/.vnc/xstartup * What exactly did you do (or not

Bug#832775: Kernel stack trace

Attached is a kernel stack trace that accompanies the x11vnc crash. The above information is from a different x11vnc crash. Each stack trace accompanies a different x11vnc crash. All that is required to recreate the bug is to start x11vnc and login to the remote desktop, then disconnect. Jul 28

Bug#832889: x11vnc crash

Package: x11vnc Version: 0.9.13-1.2+b4 Severity: normal Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? Connecting to x11vnc with vinagre * What exactly did you do (or not do) that was effective (or

Bug#832779: x11vnc: Generates kernel warning then exits without warning

Package: x11vnc Version: 0.9.13-1.2+b4 Severity: normal Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? Connecting to x11vnc with vinagre * What exactly did you do (or not do) that was effective (or

Bug#832775: x11vnc crash

Package: x11vnc Version: 0.9.13-1.2+b4 Severity: normal Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? Connecting to x11vnc with vinagre * What exactly did you do (or not do) that was effective (or

Bug#805711: Can't easily remove light-locker w/task-xfce-desktop installed

Removing light-locker is non-trivial if task-xfce-desktop is installed, as all the dependency / recommends packages are removed as well.

Bug#803342: Error still happening

This time on a fresh dhelp install, the cron weekly job crapped out. Output attached. Subject: Anacron job 'cron.weekly' on debianx Content-Type: text/plain; charset=UTF-8 Message-Id: Date: Sun, 15 May 2016 07:42:42 -0400 run-parts: executing

Bug#803342: Iiiittt's baaaack

Package ruby-bdb caused index++ to choke on 'README_en.html': run-parts: executing /etc/cron.weekly/0anacron run-parts: executing /etc/cron.weekly/dhelp terminate called after throwing an instance of 'std::out_of_range' what(): basic_string::erase: __pos (which is 4294967295) >

Bug#600262: RandomizedDelaySec keeps adding time?

What's going on here? journalctl -u apt-daily.timer -- Logs begin at Wed 2016-04-13 11:31:47 EDT, end at Wed 2016-04-13 12:45:01 EDT. -- Apr 13 11:32:03 dell2800 systemd[1]: apt-daily.timer: Adding 3h 24min 46.546088s random time. Apr 13 11:32:03 dell2800 systemd[1]: Started Daily apt

Bug#750498: IdleExitTimeout is the silver bullet

Just specifying 'IdleExitTimeout 0' keeps the CUPS daemon from exiting on idle activity. 'SystemdIdleTimeout' does not work and throws an error in cupsd.conf.

Bug#813334: colord: syslog spam after failure to get session

Package: colord Version: 1.2.12-1 Severity: important Every time the CUPS scheduler wakes up and runs, colord drops 3 messages in the message log: Jan 30 09:02:02 dell2800 colord[587]: (colord:587): Cd-WARNING **: failed to get session [pid 485]: No such device or address Jan 30 09:02:02

Bug#750498: 'SystemdIdleTimeout' and 'IdleExitTimeout' are not in 'man cupsd.conf'

I know the intent was there per the cups changelog entry from Mon, 09 Jun 2014: [ Didier Raboud ] * Add SystemdIdleExit and IdleExitTimeout references in cupsd.conf manpage Perhaps it was documented at some point, but it is not there in cups V2.1.2-2. Even worse, it looks like

Bug#803342: SUCCESS!

The weekly cron job ran successfully, and the a new 'documents.index' file was created. The old index size was 69,336,284, the new size was 23,835,082. The larger size of the old index could be due to multiple manual runs of index++ couple with some packages which may have been removed

Bug#729614: Latest upstream version is 2.2-3

The latest atop version is needed for compatibility with the optional netatop module. Older versions (i.e. 1.2x) check for kernel patches, which have long since been removed.

Bug#803342: Good Run of index++ on '/var/lib/dhelp/pending.list'

After unregistering some problem packages (see above) which contained '[pdf|ps].gz' file entries and running 'dhelp_parse -r' to create a new pending list (/var/lib/dhelp/pending.list), I was able to create a valid 'documents.index' file by manually running index++ against it, and

Bug#805734: Similar to Bug 803342

This looks like another error in swish++. For methodology in debugging see http://bugs.debian.org/803342.

Bug#803342: Double Filter Construction

I have a good 'documents.index' now, and searching works for all doc-base terms except the entries that caused the out-of-range errors. Indeed, the doc-base entries that caused the indexer to choke were those containing files that required compound filters to extract the original format

Bug#803342: More testing

As seen in above post, many of the errors are thrown on compressed files. The dhelp swish++ configuration (/usr/share/dhelp/config/swish++.conf) has filters for *.gz, *.ps, and *.pdf, but combinations of those files (i.e. *.ps.gz, *.pdf.gz) seem to throw index++ for a loop; i.e. the

Bug#803342: Thanks for the quick reply!

I have begun isolating the problem parts, and will now iterate through them, deregistering the packages from doc-base to try and get a successful run. The output from the second index run, after having taken out the successul parts, is as follows: Processing 02.part Error

Bug#795025: Spoke too soon

The error still exists here even after specifying '-B 255' because this WD Caviar drive does not support APM. I'll let upstream handle this.

Bug#795025: systemd-udevd: Process '/lib/udev/hdparm' failed with exit code 5

Package: hdparm Version: 9.43-2 Severity: normal Message appears in systemd journal (journalctl) after startup. I think systemd-udevd processes '85-hdparm.rules' it runs '/lib/udev/hdparm', which produces the message. It's odd because previously the hdparm startup script

Bug#795025: Old disk drive doesn't support APM

This error occurs on my Western Digital Caviar series drive. Uncommenting '#apm = 256' to disable APM for this drive gets rid of the error message. FWIW, the following check in '/lib/hdparm/hdparm-functions' to check the device path is incorrect: local ID_PATH=$(udevadm info -n

Bug#795025: Caused by I/O error on disk with no APM support

Running '/lib/udev/hdparm' with trace on shows it trying to execute '/usr/sbin/hdparm -B254 /dev/sdX', with the following result (with --verbose parm passed to hdparm): sudo hdparm --verbose -B254 /dev/sda /dev/sda: setting Advanced Power Management level to 0xfe (254) outgoing

Bug#767361: Workaround

The problem is in the conversion of integer 'ver' to float 'ver_f'. Workaround is to just use the integer '2', as python-reportlab is currently at version 3.2.1. --- sendfaxdialog.py~ 2015-08-02 16:35:28.795557914 -0400 +++ sendfaxdialog.py2015-08-02 16:37:31.105875325 -0400 @@ -76,13

Bug#709892: HTTP connection timing out

After setting the debug flag '-d' and redirection stderr to stdout (21) I get the following message in /var/log/messages: popularity-contest: unable to submit report to http://popcon.debian.org/cgi-bin/popcon.cgi. Also, the cron job output 'popcon Timed out.'. So I guess the HTTP error is a

Bug#782833: Tried those two tips, no joy

Thanks for the tips! Unfortunately, #1 (Allow pages to choose their own fonts) was already set, and for #2, I don't have the 'Noscript' plugin installed. I disabled AdBlock Plus and reloaded the page but no success. -- To UNSUBSCRIBE, email to

Bug#782833: Good news on at least one site

I can see the widgets on www.shoutcast.com now. I have upgraded to iceweasel V38.0.1-5. One oddity I noticed when checking the 'Allow pages to choose...' setting is that the that the 'Advanced' button on 'Preferences/Content' has a little box with 'acb' in it to the

Bug#788851: Corrected patch

There was a dangling 'fi' in previous version. Here is the corrected patch: --- acct.cron.daily 2015-06-15 11:18:29.527749598 -0400 +++ acct.cron.daily.new 2015-06-16 11:02:40.215254804 -0400 @@ -15,7 +15,16 @@ savelog -g adm -m 0640 -u root -c ${ACCT_LOGGING} /var/log/account/pacct

Bug#784969: Me to with older video card (Intel 865G)

There is a bug fix out for Fedora that fixes what looks like a similar issue for V2.99.917-9 (https://bugzilla.redhat.com/show_bug.cgi?id=1226531). Apparently DRI3 (which was enabled on 917-2) was disabled in 917-9. It would be nice to have a later version available in Debian to test

Bug#788851: acct: Sometimes new acct records not written after cron.daily/savelog

Package: acct Version: 6.5.5-2.1 Severity: normal Tags: patch Occasionally the accounting subsystem doesn not begin writing to the new account file ('/var/log/accout/pacct') after the savelog is done in '/etc/cron.daily/acct'. I had observed this phenomena on Fedora systems and recently

Bug#787289: Point(s) of failure

It's quite possible there was some combination of conditions existing on my acng box that caused this condition. I've mentioned the high amount of available updates, some of the following factors may have been at play: 1. System has been up for weeks, maybe some

Bug#787289: Success pipeline depths 255/10 for acng/apt

I read in the apt.conf man page that the default apt pipeline depth used to be 10 (and remember seeing it in the past), so I set it to 10 in a couple of clients (localhost and another machine on the LAN) and had success with the apt-get update and about 50 megs of package downloads. I'll

Bug#787289: SUCCESS!

Using PipelineDepth=1 was successful! I noticed that the default for apt was 0, meaning pipelining disabled. I will mention that there a _lot_ of updates available when I did the apt-get updates. Want me to split the difference and try PipelineDepth=128? -- To UNSUBSCRIBE, email to

Bug#787289: Good run of apt-get update with direct connection

I ran with a direct connection to a mirror and go updates. Log is attached. GET /debian/dists/testing/InRelease HTTP/1.1 Host: debian.mirror.frontiernet.net Cache-Control: max-age=0 Accept: text/* If-Modified-Since: Sat, 30 May 2015 09:38:09 GMT User-Agent: Debian APT-HTTP/1.3 (1.0.9.9)

Bug#787289: apt-cacher-ng: Connection timeout 500

Package: apt-cacher-ng Version: 0.8.3-1 Severity: normal Dear Maintainer, 'apt-get update' and maintenance job (cron.daily) fail with 'Connection timeout. Can't get up to date InRelease and package list files. I've tried switching Debian mirrors but that doesn't help. I am attaching

Bug#784781: apt-listchanges: Document 'browser' setting may include args

Package: apt-listchanges Version: 2.85.13+nmu1 Severity: wishlist Dear Maintainer, The 'listchanges.conf' documentation states that the 'browser' parm points to the browser, but not that arguments may be passed to the browser script/executable. In my case I like to run iceweasel with a

Bug#778836: gvfs-backends: gvfsd-dnssd segfault

Package: gvfs-backends Version: 1.22.2-1 Severity: normal Segfault, strcmp-ssse3.S not found. Backtrace and core dump attached. -- System Information: Debian Release: 8.0 APT prefers testing APT policy: (990, 'testing'), (500, 'unstable') Architecture: i386 (i686) Kernel: Linux

Bug#776511: network-manager: Please package 'NetworkManager-wait-online.service'

Package: network-manager Version: 0.9.10.0-5 Severity: wishlist Fedora has a handy service that network applications can use to insure network interfaces (particularly wireless) are all the way up before proceeding. For a practical example see Debian Bug #775522. Attached is the service

Bug#776511: Whoops

Didn't see that there for some reason Sorry for the noise. OK to close. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#775522: network-online.target reached too early

Reference https://bbs.archlinux.org/viewtopic.php?id=171496 If NetworkManager needs to be up and and start interface(s), services depending on said interfaces (i.e. distccd --listen ip address) need to depend on a unit such as 'NetworkManager-wait-online.service' (from Fedora

Bug#775522: Load triggered?

This problem may be triggered by heavy load at startup. I am experiencing this on a 'server' type system that starts many services at boot time, while another Debian machine with wireless starts distccd successfully. Systemd derives the dependencies of LSB scripts from the

Bug#775522: distcc daemon fails to start on wireless host

Package: distcc Version: 3.1-6.1 Severity: important Dear Maintainer, In a wireless environment, distccd fails to start before the wireless connection is activated by NetworkManager. It fails with exit code 102, log shows: distcc-list-by-addr Bind of IP address *IP addr *:3632

Bug#774786: Upstream bug number

Issue #446874: http://code.google.com/p/chromium/issues/detail?id=446874 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#542874: This is fixed in Debian, I think

I have had the message in Fedora for awhile but don't have it on Debian for some time now. I think the lastest version installs the atop module as setuid root, per 'man atop': PROCESS ACCOUNTING * snip * Notice that root-privileges are required to switch on process accounting in

Bug#506191: Issue addressed upstream in V2.1

From http://atoptool.nl/downloadatop.php: Modifications for atop: New daemon atopacctd: This daemon has been added to control the process accounting mechanism. It takes care of truncating the original process accounting file regularly and creates small-sized shadow files

Bug#770391: Missing files cause this problem

I ran into this exact problem months back and I think I filed a bug report but can't seem to find it. The 'logrotate.d/atop' file was deleted in the atop.postinst: #!/bin/bash set -e if dpkg-maintscript-helper supports rm_conffile; then dpkg-maintscript-helper rm_conffile \

Bug#772149: backuppc: Add configurable I/O scheduling parameter

Package: backuppc Version: 3.3.0-2 Severity: wishlist Tags: patch Add a parameter 'IONICE' to '/etc/default/backuppc' to be able to start the daemon with an I/O scheduling priority other than default (i.e. 'idle' instead of 'none/best effort'. -- System Information: Debian Release:

Bug#670377: Thanks, no dump now

My chipset is Intel 945GME. From looking at 'vainfo' source I learned that the driver name is from whatever driver is loaded in the X server, as indicated in the following lines from the X log: [57.145] (II) intel(0): [DRI2] Setup complete [57.145] (II) intel(0): [DRI2]

Bug#762101: Me too

Version: 215-5+b1 I too am getting slammed by this message, one every ~51 seconds. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#762101: Already have persistent network names

I don't change adapters/adapter locations often enough to have a need for the new network name schemes and have long ago put in place a custom '/etc/udev/rules.d/70-persistent-net.rules', template generated by '/lib/udev/rules.d/75-persistent-net-generator.rules'. The wired adapter is

Bug#762101: Which change?

Whatever happened to cause the NamePolicy messages to appear every n seconds. As noted previously by Martin Krafft, I have not opted-in, but I also see the message all the time. Maybe opt-in isn't working as planned?. Let's see what I would have to do to make these messages go

Bug#762101: Understood

Now I get it. Thank you. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#670377: i965 driver doesn't work on my 945GME

Problem: no VA support for intel G45 and others reason: missing i915_drv_video.so, which is not delivered by any package solution: Should the installed i965_drv_video.so be loaded instead of the missing i915_drv_video.so? After looking at the source for vainfo, I tried to load i965 and got a

Bug#767354: hplip-gui: hp-sendfax dialog never gets past step 3

Package: hplip-gui Version: 3.14.6-1 Severity: important Dear Maintainer, The 'hp-sendfax' dialog, whether started from the command line or through the device manager, never progresses past first screen which asks which files to add. The 'Next' (as well as 'Back', Move Up/Down and Remove)

Bug#767361: hplip: hp-check/doctor/sendfax incorrectly reports python-reportlab 2.0+ not installed

Package: hplip Version: 3.14.6-1+b1 Severity: normal Dear Maintainer, 'hp-sendfax -g' (as well as hp-check/doctor) report: 'Pre-2.0' version of Reportlab instgalled. Fax coverpages disabled...Please install Reportlab 2.0+ This is incorrect, as python-reportlab 3.1.8-3 is installed. (per

Bug#765542: systemd: man systemd refers to obsolete command 'systemctl dump'

Package: systemd Version: 215-5+b1 Severity: minor Tags: patch The man page refers to the 'dump' function of systemctl in the SIGUSR2 explanation. The dump function has been moved to 'systemd-analyze dump'. Patch attached to change the wording. -- Package-specific info: -- System

Bug#765101: systemd: systemctl -t ... fails to list units, access denied

Package: systemd Version: 215-5+b1 Severity: normal When running as non-root, systemctl -t {...} (i.e. systemctl -t socket) fails with access denied: systemctl -t socket Failed to list units: Access denied. Systemd journal shows dbus rejected the send messages. Attached are the

Bug#765101: Purging systemd-shim

Beautiful! Thanks, that did the trick. I suspected systemd-shim, because I never understood what it was for in the first place. I've been on systemd init system for years now and when I see some systemd 'helper' to ease conversions from sysvinit I am always suspicious. Then when I saw

Bug#762087: Seems like a systemd issue

This problem with samba shutting down seems to have happened since the upgrade from systemd 208 to 215. I believe the samba init script(s) have been been in place for awhile now (at least 9/22/2013 according to this changelog entry Merge contents of samba-ad-dc into samba.) and there

Bug#740942: Fw: Seems like a systemd issue

I didn't notice that 762087 had been merged with 740942, so I am forwarding my last post to 762087, will follow up with this bug from now forward. Begin forwarded message: Date: Sat, 11 Oct 2014 11:11:55 -0400 From: Dominique Brazziel dbrazz...@snet.net To: 762...@bugs.debian.org Subject: Seems

Bug#762087: I'm really confused now

On one machine (same systemd and samba versions as production machine) I was able to work around this problem by masking samba-ad-dc.service. I tried the same thing on the production machine and now nmbd.service is waiting, but there is definitely an nmbd process running. systemctl

Bug#762087: Production machine is local master browser

I had a theory that maybe nmbd has some housekeeping (terminate active connections, initiate elections?) to do before it bows out, it the master browser on my LAN, the test machine is just a client. Will turn on debugging in nmbd and test. -- To UNSUBSCRIBE, email to

Bug#762087: samba-ad-dc script doesn't check for running process in stop

I am not running an ad-dc samba server, the role is 'auto', so that process never gets started. At the top of the 'start' stanza we see: SERVER_ROLE=`samba-tool testparm --parameter-name=server role 2/dev/null | tail -1` if [ $SERVER_ROLE != active directory domain

Bug#760950: Bunch of updates today

Many testing updates arrived today, including some packages that were previously in unstable (i.e. vim, upower). OK to close. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#760950: apt: Setting 'APT:Default-Release testing; ' in testing/unstable prevents updates

Package: apt Version: 1.0.7 Severity: important Dear Maintainer, After upgrade to apt 1.0.7 on 9/3 apt-show-versions stopped showing any upgradeable packages. I have a mixed testing/unstable environment, so the list of upgradeable packages usually includes a few packages. After

Bug#760950: All upgradeable packages from unstable

apt list --upgradable and apt-show-versions -u without APT::Default-Release set show ~367 packages upgradable but they are all in unstable. Output from apt list is attached. Maybe the lack of upgradable packages from testing is related to the testing freeze mentioned in the

  1   2   3   4   5   6   7   >