Bug#1077286: marco: can't rename workspace via keyboard shortcut

[Mike Kupfer]

> But the window flickering would need to be fixed for this to
> be useful.

I looked into this a little more.  My trixie system is a VirtualBox VM,
which I normally run with 3D graphics acceleration enabled.  I tried
booting the VM with 3D graphics acceleration disabled, and zenity worked
fine.

Also, I see that "=" is not needed for the command-line options.  But
both --display and --class apparently need to be removed.  This command
works fine:

  zenity --entry --title Marco --text "New Workspace Name:" --entry-text Home 
--ok-label OK --cancel-label Cancel

regards,
mike

Bug#1077286: marco: can't rename workspace via keyboard shortcut

[Mike Kupfer]

Package: marco
Version: 1.26.2-4+b4
Severity: normal
Tags: upstream
X-Debbugs-Cc: kup...@rawbw.com

Dear Maintainer,

I assigned a keyboard shortcut to rename the current workspace.  In
bookworm, I get a popup where I can enter the new workspace name and
click on "ok".  In trixie, no window appears.  Instead, the following
line appears in .xsession-errors:

  This option is not available. Please see --help for all possible
  usages.

It looks like this is because bookworm has zenity v3, whereas trixie
has zenity v4, and the zenity v4 CLI is not compatible with the v3
CLI.

In bookworm, the zenity invocation looks something like

  zenity --entry --display :0.0 --class marco-dialog --title Marco --text "New 
Workspace Name:" --entry-text Home --ok-label OK --cancel-label Cancel

I tried running the following command in trixie from a shell:

  zenity --entry "--text=New Workspace Name:" --entry-text=Home --ok-label=OK 
--cancel-label=Cancel

That sort of works, but it isn't usable.  I briefly see a new window,
then the window disappears.  Then portions or all of the window
randomly appear and disappear.  With a little guesswork, I can enter
some text and click on OK, and zenity does print the text that I
entered.  But the window flickering would need to be fixed for this to
be useful.

I think this is the same as upstream bug
https://github.com/mate-desktop/marco/issues/755.

I don't know if there are other places in MATE that use zenity.  If
there are, I assume they would be broken, too.

-- System Information:
Debian Release: trixie/sid
  APT prefers testing-debug
  APT policy: (500, 'testing-debug'), (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 6.9.10-amd64 (SMP w/2 CPU threads; PREEMPT)
Kernel taint flags: TAINT_WARN, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages marco depends on:
ii  libc62.39-4
ii  libcairo21.18.0-3+b1
ii  libgdk-pixbuf-2.0-0  2.42.12+dfsg-1
ii  libglib2.0-0t64  2.80.4-1
ii  libgtk-3-0t643.24.43-1
ii  libmarco-private21.26.2-4+b4
ii  libpango-1.0-0   1.54.0+ds-1
ii  libx11-6 2:1.8.7-1+b1
ii  marco-common 1.26.2-4
ii  mate-desktop-common  1.26.2-1.1
ii  zenity   4.0.2-1

marco recommends no packages.

marco suggests no packages.

-- no debconf information

Bug#1070876: still seeing hangs with 5.10.0-30 kernel

[Mike Kupfer]

I have upgraded the Latitude to Bookworm, and I'm no longer seeing hangs
with that system.

The AMD box is now running the 5.10.0-30 (5.10.218-1) kernel, and I'm
still seeing occasional hangs on resume.  Unfortunately, I haven't come
up with a reliable way to reproduce the hangs.

Here's the system information for the AMD box from reportbug:

-- Package-specific info:
** Version:
Linux version 5.10.0-29-amd64 (debian-ker...@lists.debian.org) (gcc-10 (Debian 
10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2) #1 SMP 
Debian 5.10.216-1 (2024-05-03)

** Command line:
BOOT_IMAGE=/vmlinuz-5.10.0-29-amd64 root=/dev/mapper/alto--vg-root ro quiet

** Not tainted

** Kernel log:
[   29.743332] systemd[1]: Starting Set the console keyboard layout...
[   29.744014] systemd[1]: Starting Create list of static device nodes for the 
current kernel...
[   29.744716] systemd[1]: Starting Monitoring of LVM2 mirrors, snapshots etc. 
using dmeventd or progress polling...
[   29.745545] systemd[1]: Starting Load Kernel Module configfs...
[   29.746457] systemd[1]: Starting Load Kernel Module drm...
[   29.747390] systemd[1]: Starting Load Kernel Module fuse...
[   29.817867] systemd[1]: Condition check resulted in Set Up Additional Binary 
Formats being skipped.
[   29.817938] systemd[1]: Condition check resulted in File System Check on 
Root Device being skipped.
[   29.819464] systemd[1]: Starting Journal Service...
[   29.843668] systemd[1]: Starting Load Kernel Modules...
[   29.844340] systemd[1]: Starting Remount Root and Kernel File Systems...
[   29.845019] systemd[1]: Starting Coldplug All udev Devices...
[   29.846591] systemd[1]: Mounted Huge Pages File System.
[   29.846706] systemd[1]: Mounted POSIX Message Queue File System.
[   29.846799] systemd[1]: Mounted Kernel Debug File System.
[   29.846890] systemd[1]: Mounted Kernel Trace File System.
[   29.847156] systemd[1]: Finished Create list of static device nodes for the 
current kernel.
[   29.847404] systemd[1]: modprobe@drm.service: Succeeded.
[   29.847589] systemd[1]: Finished Load Kernel Module drm.
[   29.866893] fuse: init (API version 7.32)
[   29.867463] systemd[1]: modprobe@fuse.service: Succeeded.
[   29.867663] systemd[1]: Finished Load Kernel Module fuse.
[   29.868467] systemd[1]: Mounting FUSE Control File System...
[   29.870561] systemd[1]: Mounted FUSE Control File System.
[   29.888175] systemd[1]: modprobe@configfs.service: Succeeded.
[   29.888407] systemd[1]: Finished Load Kernel Module configfs.
[   29.889274] systemd[1]: Mounting Kernel Configuration File System...
[   29.891231] systemd[1]: Mounted Kernel Configuration File System.
[   29.900285] EXT4-fs (dm-1): re-mounted. Opts: errors=remount-ro
[   29.901298] systemd[1]: Finished Remount Root and Kernel File Systems.
[   30.023041] systemd[1]: Condition check resulted in Rebuild Hardware 
Database being skipped.
[   30.023096] systemd[1]: Condition check resulted in Platform Persistent 
Storage Archival being skipped.
[   30.023870] systemd[1]: Starting Load/Save Random Seed...
[   30.024571] systemd[1]: Starting Create System Users...
[   30.087030] systemd[1]: Started Journal Service.
[   30.158266] systemd-journald[453]: Received client request to flush runtime 
journal.
[   30.346605] lp: driver loaded but no devices found
[   30.392185] ppdev: user-space parallel port driver
[   30.438582] parport_pc 00:02: reported by Plug and Play ACPI
[   30.438655] parport0: PC-style at 0x378, irq 7 [PCSPP,TRISTATE]
[   30.463217] systemd-journald[453]: File 
/var/log/journal/6e6ee8d379da4c0f978c260c534761b1/system.journal corrupted or 
uncleanly shut down, renaming and replacing.
[   30.549968] lp0: using parport0 (interrupt-driven).
[   33.655388] acpi_cpufreq: overriding BIOS provided _PSD data
[   33.895785] input: PC Speaker as /devices/platform/pcspkr/input/input9
[   34.009756] sd 1:0:1:0: Attached scsi generic sg0 type 0
[   34.026732] sp5100_tco: SP5100/SB800 TCO WatchDog Timer Driver
[   34.074675] ATK0110 ATK0110:00: Overriding interface detection
[   35.116512] kvm: Nested Virtualization enabled
[   35.116532] SVM: kvm: Nested Paging enabled
[   35.657221] MCE: In-kernel MCE decoding enabled.
[   35.695914] EDAC amd64: F15h detected (node 0).
[   35.695986] EDAC amd64: Node 0: DRAM ECC disabled.
[   36.083419] snd_hda_codec_hdmi hdaudioC1D0: HDMI ATI/AMD: no speaker 
allocation for ELD
[   36.085019] input: HDA ATI HDMI HDMI/DP,pcm=3 as 
/devices/pci:00/:00:01.0/:01:05.1/sound/card1/input10
[   36.178087] snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC887-VD: 
line_outs=1 (0x14/0x0/0x0/0x0/0x0) type:line
[   36.178092] snd_hda_codec_realtek hdaudioC0D0:speaker_outs=0 
(0x0/0x0/0x0/0x0/0x0)
[   36.178095] snd_hda_codec_realtek hdaudioC0D0:hp_outs=1 
(0x1b/0x0/0x0/0x0/0x0)
[   36.178097] snd_hda_codec_realtek hdaudioC0D0:mono: mono_out=0x0
[   36.178099] snd_hda_codec_realtek hdaudioC0D0:dig-out=0x11/0x0
[   36.178101] snd_hda_code

Bug#1070997: sorry about the new bug

[Mike Kupfer]

Apologies, I had meant to update 1070876, not create a new bug.  I guess
they should be merged?

regards,
mike

Bug#1070997: linux-image-5.10.0-29-amd64: more info

[Mike Kupfer]

Package: src:linux
Version: 5.10.216-1
Followup-For: Bug #1070876
X-Debbugs-Cc: kup...@rawbw.com

Dear Maintainer,

Sorry about the lack of system information in the original submission.
(I had run "reportbug linux" rather than "reportbug kernel".)

The kernel log is from a fresh boot.  Please let me know if there are
any files from /var/log that I should include.

-- Package-specific info:
** Version:
Linux version 5.10.0-29-amd64 (debian-ker...@lists.debian.org) (gcc-10 (Debian 
10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2) #1 SMP 
Debian 5.10.216-1 (2024-05-03)

** Command line:
BOOT_IMAGE=/vmlinuz-5.10.0-29-amd64 root=/dev/mapper/ceylon--vg-root ro quiet

** Not tainted

** Kernel log:
[   10.876427] usbcore: registered new interface driver uvcvideo
[   10.876429] USB Video Class driver (1.1.1)
[   10.877628] intel_rapl_common: Found RAPL domain package
[   10.877630] intel_rapl_common: Found RAPL domain core
[   10.877631] intel_rapl_common: Found RAPL domain uncore
[   10.877638] intel_rapl_common: RAPL package-0 domain package locked by BIOS
[   10.905380] Adding 1003516k swap on /dev/mapper/ceylon--vg-swap_1.  
Priority:-2 extents:1 across:1003516k SSFS
[   10.924828] cfg80211: Loaded X.509 cert 'romain.per...@gmail.com: 
3abbc6ec146e09d1b6016ab9d6cf71dd233f0328'
[   10.925204] cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7'
[   10.929617] input: HDA Intel HDMI HDMI/DP,pcm=3 as 
/devices/pci:00/:00:03.0/sound/card0/input12
[   10.929692] input: HDA Intel HDMI HDMI/DP,pcm=7 as 
/devices/pci:00/:00:03.0/sound/card0/input13
[   10.929754] input: HDA Intel HDMI HDMI/DP,pcm=8 as 
/devices/pci:00/:00:03.0/sound/card0/input14
[   10.929825] input: HDA Intel HDMI HDMI/DP,pcm=9 as 
/devices/pci:00/:00:03.0/sound/card0/input15
[   10.930695] input: HDA Intel HDMI HDMI/DP,pcm=10 as 
/devices/pci:00/:00:03.0/sound/card0/input16
[   10.931777] cfg80211: Loaded X.509 cert 'wens: 
61c038651aabdcf94bd0ac7ff06c7248db18c600'
[   10.938367] platform regulatory.0: firmware: direct-loading firmware 
regulatory.db
[   10.940753] platform regulatory.0: firmware: direct-loading firmware 
regulatory.db.p7s
[   11.007023] Bluetooth: Core ver 2.22
[   11.007082] NET: Registered protocol family 31
[   11.007084] Bluetooth: HCI device and connection manager initialized
[   11.007216] Bluetooth: HCI socket layer initialized
[   11.007219] Bluetooth: L2CAP socket layer initialized
[   11.007225] Bluetooth: SCO socket layer initialized
[   11.007354] snd_hda_codec_realtek hdaudioC1D0: autoconfig for ALC3235: 
line_outs=1 (0x16/0x0/0x0/0x0/0x0) type:line
[   11.007356] snd_hda_codec_realtek hdaudioC1D0:speaker_outs=1 
(0x14/0x0/0x0/0x0/0x0)
[   11.007358] snd_hda_codec_realtek hdaudioC1D0:hp_outs=1 
(0x15/0x0/0x0/0x0/0x0)
[   11.007360] snd_hda_codec_realtek hdaudioC1D0:mono: mono_out=0x0
[   11.007362] snd_hda_codec_realtek hdaudioC1D0:inputs:
[   11.007364] snd_hda_codec_realtek hdaudioC1D0:  Headset Mic=0x1a
[   11.007366] snd_hda_codec_realtek hdaudioC1D0:  Dock Mic=0x19
[   11.007368] snd_hda_codec_realtek hdaudioC1D0:  Headphone Mic=0x18
[   11.007370] snd_hda_codec_realtek hdaudioC1D0:  Internal Mic=0x13
[   11.041503] usbcore: registered new interface driver btusb
[   11.046768] usb 1-1.3: firmware: failed to load ar3k/AthrBT_0x3101.dfu 
(-2)
[   11.046820] firmware_class: See https://wiki.debian.org/Firmware for 
information about missing firmware
[   11.046874] usb 1-1.3: Direct firmware load for ar3k/AthrBT_0x3101.dfu 
failed with error -2
[   11.046885] Bluetooth: Loading patch file failed
[   11.046926] ath3k: probe of 1-1.3:1.0 failed with error -2
[   11.047085] usbcore: registered new interface driver ath3k
[   11.065040] input: HDA Digital PCBeep as 
/devices/pci:00/:00:1b.0/sound/card1/input17
[   11.065129] input: HDA Intel PCH Dock Mic as 
/devices/pci:00/:00:1b.0/sound/card1/input18
[   11.065190] input: HDA Intel PCH Headphone Mic as 
/devices/pci:00/:00:1b.0/sound/card1/input19
[   11.065254] input: HDA Intel PCH Dock Line Out as 
/devices/pci:00/:00:1b.0/sound/card1/input20
[   11.071353] EXT4-fs (sda2): mounting ext2 file system using the ext4 
subsystem
[   11.082092] EXT4-fs (sda2): mounted filesystem without journal. Opts: (null)
[   11.082099] ext2 filesystem being mounted at /boot supports timestamps until 
2038 (0x7fff)
[   11.112440] ath9k :02:00.0: enabling device ( -> 0002)
[   11.112594] ath: phy0: WB335 2-ANT card detected
[   11.112595] ath: phy0: Set BT/WLAN RX diversity capability
[   11.120307] ath: phy0: Enable LNA combining
[   11.121445] ath: phy0: ASPM enabled: 0x42
[   11.121448] ath: EEPROM regdomain: 0x6c
[   11.121449] ath: EEPROM indicates we should expect a direct regpair map
[   11.121451] ath: Country alpha2 being used: 00
[   11.121452] ath: Regpair used: 0x6c
[   11.123371] ieee80211 phy0: Selected rate control algorithm 'm

Bug#1070876: linux: hang when resuming from suspend

[Mike Kupfer]

Source: linux
Version: 5.10.0-29
Severity: important
X-Debbugs-Cc: kup...@rawbw.com

Dear Maintainer,

With the 5.10.0-29 kernel, my Dell Latitude E7250 hangs when resuming
from suspend-to-RAM.  I have not once gotten a successful resume; this
problem does not appear at all with the 5.10.0-28 kernel.

The visible symptom is that I see the display as it was at the time of
suspend, but there is no response to the trackpad or keyboard.  If
there is a screen locker that displays the time (e.g., Cinnamon), the
time-of-suspend is displayed, even when the resume happens several
minutes (or longer) after the suspend.  I have tried the following
desktop sessions: Cinnamon, i3, and maybe Xfce, too.  I've also seen
this hang after suspending from the lightdm login screen.

I have also seen the same (or at least a similar) hang a couple times
with the 5.10.0-29 kernel on a different system.  That one is a
ZaReason Limbo (AMD FX-6300 processor, Radeon graphics).  Most of the
time, though, I can resume that system okay, at least with Cinnamon
and i3.

-- System Information:
Debian Release: 11.9
  APT prefers oldstable-security
  APT policy: (500, 'oldstable-security'), (500, 'oldstable')
Architecture: amd64 (x86_64)

Kernel: Linux 5.10.0-29-amd64 (SMP w/4 CPU threads)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Bug#1051973: tzdata: no warning about moving US/* to tzdata-legacy

[Mike Kupfer]

Mike Kupfer wrote:

> I'm okay with the change itself, but it really should get more
> visibility.  That is, on upgrade the user should get some sort of
> heads-up that they are getting an incompatible change and may need to
> take corrective action.

To clarify, what I have in mind is a news entry, which apt-listchanges
would display.  (I'm not really familiar with Debian packaging, so I
couldn't describe the mechanism when I filed the bug last night.  I
guess what I'm requesting is a NEWS.Debian entry.)

thanks,
mike

Bug#1051973: tzdata: no warning about moving US/* to tzdata-legacy

[Mike Kupfer]

Package: tzdata
Version: 2023c-10
Severity: important
X-Debbugs-Cc: kup...@rawbw.com

Dear Maintainer,

After using synaptic or apt to upgrade tzdata from 2023c-7 to
2023c-10, I would get the wrong time in my desktop environments and on
a virtual terminal (no X).  I would get UTC, rather than my local
time.  Though the lightdm screen would display the correct time.

I tracked this down to the fix for #1040997.  So, changing TZ from
US/Pacific to America/Los_Angeles makes the problem go away.  Or,
keeping TZ at US/Pacific, installing tzdata-legacy makes the problem
go away.

I'm okay with the change itself, but it really should get more
visibility.  That is, on upgrade the user should get some sort of
heads-up that they are getting an incompatible change and may need to
take corrective action.

thanks,
mike

-- System Information:
Debian Release: trixie/sid
  APT prefers testing-debug
  APT policy: (500, 'testing-debug'), (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 6.4.0-3-amd64 (SMP w/2 CPU threads; PREEMPT)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages tzdata depends on:
ii  debconf [debconf-2.0]  1.5.82

tzdata recommends no packages.

tzdata suggests no packages.

-- debconf information:
  tzdata/Zones/Pacific:
  tzdata/Zones/Africa:
  tzdata/Zones/Europe:
  tzdata/Zones/Arctic:
* tzdata/Zones/America: Los_Angeles
* tzdata/Areas: America
* tzdata/Zones/Etc: UTC
  tzdata/Zones/Australia:
  tzdata/Zones/Antarctica:
  tzdata/Zones/US:
  tzdata/Zones/Indian:
  tzdata/Zones/Atlantic:
  tzdata/Zones/SystemV:
  tzdata/Zones/Asia:

Bug#1023880: mate-panel: workspace-switcher applet doesn't maintain aspect ratio with panel resize

[Mike Kupfer]

Package: mate-panel
Version: 1.27.0-1
Severity: normal
X-Debbugs-Cc: mkup...@alum.berkeley.edu

Dear Maintainer,

This is a continuation of bug#995601, which went away on its own back
in June but is back now.  I had tried to reopen 995601, but it's
already been archived, so here's a new bug.

In my Bookworm VM (VirtualBox 7), the thumbnails in the workspace
switcher appear to be in portrait layout, with the height greater than
the width.  I expect the aspect ratio of the thumbnails to match (more
or less) the display, which is wider than the height.  (See bug#995601
for some screenshots.)

Here's some additional information:

I created a new user account on the VM and logged in, and I noticed
something interesting.  On the initial login, the applet thumbnails
are a little narrow relative to the display's aspect ratio (see the
"24 pixels" attachment), but not too bad.  If I increase the panel
size to 36 pixels, the applet increases in height, but its width
remains the same, giving it a noticeably odd shape (see the "36
pixels" attachment).  I also took a screenshot with the panel at the
smallest possible height ("19 pixels").  Again, the width of the
applet remained the same; just the aspect ratio changed.  I hope this
is helpful in tracking down the problem.

best regards,
mike

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

Kernel: Linux 6.0.0-3-amd64 (SMP w/2 CPU threads; PREEMPT)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages mate-panel depends on:
ii  dconf-gsettings-backend [gsettings-backend]  0.40.0-3
ii  libatk1.0-0  2.46.0-3
ii  libc62.36-4
ii  libcairo21.16.0-6
ii  libgdk-pixbuf-2.0-0  2.42.9+dfsg-1
ii  libglib2.0-0 2.74.1-2
ii  libgtk-3-0   3.24.34-3
ii  libgtk-layer-shell0  0.8.0-1
ii  libice6  2:1.0.10-1
ii  libmate-desktop-2-17 1.26.0-1
ii  libmate-menu21.26.0-3
ii  libmate-panel-applet-4-1 1.27.0-1
ii  libmateweather1  1.26.0-1.1
ii  libpango-1.0-0   1.50.10+ds-1
ii  librda0  0.0.5-1.1
ii  libsm6   2:1.2.3-1
ii  libwayland-client0   1.21.0-1
ii  libwnck-3-0  43.0-2
ii  libx11-6 2:1.8.1-2
ii  libxrandr2   2:1.5.2-2+b1
ii  mate-desktop 1.26.0-1
ii  mate-menus   1.26.0-3
ii  mate-panel-common1.27.0-1
ii  mate-polkit  1.26.1-1

mate-panel recommends no packages.

mate-panel suggests no packages.

-- no debconf information

Bug#1014394: linux kernel 5.10.0-15 on virtualbox host causes random process crashes in guests

[Mike Kupfer]

Bastian Blank wrote:

> As Virtualbox uses it's own kernel module, we can't provide any help.
> You need to ask them for a fixed version to work with that kernel
> version.

FWIW, I'm running a test build[1] of VirtualBox with the -15 kernel on
the host.  I, too, had the problem of Firefox crashing regularly with
VirtualBox 6.1.34, but things seem stable with VirtualBox 6.1.35
r151864.

mike
[1] https://www.virtualbox.org/wiki/Testbuilds

Bug#995601: Acknowledgement (mate-panel: workspace switcher applet is compressed horizontally)

[Mike Kupfer]

Today I upgraded the VM that I was seeing this problem on.  I hadn't run
MATE on it for awhile, but when I started it today, I noticed that this
problem is no longer present.  The baremetal system that had this
problem got reverted back to Stable some months ago, so I can't verify
that it's also fixed on that system.

In any case, feel free to close this bug.

cheers,
mike

Bug#995601: additional data

[Mike Kupfer]

I just realized that Bullseye also has mate-panel 1.24.1-1.  But I don't
see the compression problem with my Bullseye VM, just with the systems
that are running Bookworm.

Also, on my Bookwork VM, if I tell the applet to display the workspaces
in 2 rows, they have the correct dimensions.  If I go back to displaying
the workspaces in 1 row, they go back to being taller than wide.

regards,
mike

Bug#995601: mate-panel: workspace switcher applet is compressed horizontally

[Mike Kupfer]

Package: mate-panel
Version: 1.24.1-1+b1
Severity: normal
X-Debbugs-Cc: mkup...@alum.berkeley.edu

Dear Maintainer,

I have a display that is wider than tall, but the workspace switcher
applet shows it as taller than wide.  Similar, a mate-terminal window
that is wider than tall gets shown as taller than wide.

The dimensions of the pop-up workspace switcher are fine.

I see this on both a VirtualBox guest and a baremetal system (Dell
Latitude E7250).

I am currently using the Blue Menta theme, but I see this with other
themes as well.

Output from xdpyinfo:

-8<-8<-
name of display::0.0
version number:11.0
vendor string:The X.Org Foundation
vendor release number:12011000
X.Org version: 1.20.11
maximum request size:  16777212 bytes
motion buffer size:  256
bitmap unit, bit order, padding:32, LSBFirst, 32
image byte order:LSBFirst
number of supported pixmap formats:7
supported pixmap formats:
depth 1, bits_per_pixel 1, scanline_pad 32
depth 4, bits_per_pixel 8, scanline_pad 32
depth 8, bits_per_pixel 8, scanline_pad 32
depth 15, bits_per_pixel 16, scanline_pad 32
depth 16, bits_per_pixel 16, scanline_pad 32
depth 24, bits_per_pixel 32, scanline_pad 32
depth 32, bits_per_pixel 32, scanline_pad 32
keycode range:minimum 8, maximum 255
focus:  window 0x3e00156, revert to PointerRoot
number of extensions:29
BIG-REQUESTS
Composite
DAMAGE
DOUBLE-BUFFER
DPMS
DRI2
DRI3
GLX
Generic Event Extension
MIT-SCREEN-SAVER
MIT-SHM
Present
RANDR
RECORD
RENDER
SECURITY
SHAPE
SYNC
VMWARE_CTRL
X-Resource
XC-MISC
XFIXES
XFree86-DGA
XFree86-VidModeExtension
XINERAMA
XInputExtension
XKEYBOARD
XTEST
XVideo
default screen number:0
number of screens:1

screen #0:
  dimensions:1920x1098 pixels (508x291 millimeters)
  resolution:96x96 dots per inch
  depths (7):24, 1, 4, 8, 15, 16, 32
  root window id:0x182
  depth of root window:24 planes
  number of colormaps:minimum 1, maximum 1
  default colormap:0x20
  default number of colormap cells:256
  preallocated pixels:black 0, white 16777215
  options:backing-store WHEN MAPPED, save-unders NO
  largest cursor:64x64
  current input event mask:0xfa8033
KeyPressMask KeyReleaseMask   EnterWindowMask  
LeaveWindowMask  ExposureMask StructureNotifyMask  
SubstructureNotifyMask   SubstructureRedirectMask FocusChangeMask  
PropertyChangeMask   ColormapChangeMask   
  number of visuals:108
  default visual id:  0x21
  visual:
visual id:0x21
class:TrueColor
depth:24 planes
available colormap entries:256 per subfield
red, green, blue masks:0xff, 0xff00, 0xff
significant bits in color specification:8 bits
  visual:
visual id:0x22
class:DirectColor
depth:24 planes
available colormap entries:256 per subfield
red, green, blue masks:0xff, 0xff00, 0xff
significant bits in color specification:8 bits
  visual:
visual id:0x118
class:TrueColor
depth:24 planes
available colormap entries:256 per subfield
red, green, blue masks:0xff, 0xff00, 0xff
significant bits in color specification:8 bits
  visual:
visual id:0x119
class:TrueColor
depth:24 planes
available colormap entries:256 per subfield
red, green, blue masks:0xff, 0xff00, 0xff
significant bits in color specification:8 bits
  visual:
visual id:0x11a
class:TrueColor
depth:24 planes
available colormap entries:256 per subfield
red, green, blue masks:0xff, 0xff00, 0xff
significant bits in color specification:8 bits
  visual:
visual id:0x11b
class:TrueColor
depth:24 planes
available colormap entries:256 per subfield
red, green, blue masks:0xff, 0xff00, 0xff
significant bits in color specification:8 bits
  visual:
visual id:0x11c
class:TrueColor
depth:24 planes
available colormap entries:256 per subfield
red, green, blue masks:0xff, 0xff00, 0xff
significant bits in color specification:8 bits
  visual:
visual id:0x11d
class:TrueColor
depth:24 planes
available colormap entries:256 per subfield
red, green, blue masks:0xff, 0xff00, 0xff
significant bits in color specification:8 bits
  visual:
visual id:0x11e
class:TrueColor
depth:24 planes
available colormap entries:256 per subfield
red, green, blue masks:0xff, 0xff00, 0xff
significant bits in color specification:8 bits
  visual:
visual id:0x11f
class:TrueColor
depth:24 planes
available colormap entrie

Bug#942676: mate-menu: Can't add MATE Advanced Menu to panel

[Mike Kupfer]

Package: mate-menu
Version: 19.10.2-1
Severity: important

Dear Maintainer,

I had an instance of the MATE Advanced menu in my panel.  After an
upgrade a couple weeks back (sorry, I don't remember exactly when),
that spot in the panel was blank, and clicking in that area had no
effect.

Since then I have reset my panels (right-click on a panel, select
Reset Panel) and tried to re-add the advanced menu.  I select the
advanced menu and click on "Add", but I don't see anything happen.  No
lines are added to .xsession-errors.

I have tried hiding $HOME/.config and logging out/in; that doesn't
help.

Turning compositing on/off doesn't help.

The system is a VirtualBox VM.  I've seen the problem with VirtualBox
6.0.12 and 6.0.14 on the host.  I tried changing the video adapter
from VBoxVGA (no-3D acceleration) to VMSVGA (with 3D acceleration);
didn't help.  VBoxSVGA (with 3D acceleration) doesn't work, either.
Updating to the 6.0.14 VirtualBox Guest Additions did not help.

I'm able to add other applets to the panel (e.g., System Monitor,
Window Selector).

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

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

Versions of packages mate-menu depends on:
ii  dconf-gsettings-backend [gsettings-backend]  0.34.0-1
ii  gir1.2-gtk-3.0   3.24.12-1
ii  gir1.2-matedesktop-2.0   1.22.2-1
ii  gir1.2-matemenu-2.0  1.22.1-1
ii  gir1.2-matepanelapplet-4.0   1.22.2-1
ii  libglib2.0-bin   2.62.1-1
ii  mozo 1.22.2-1
ii  python3  3.7.5-1
ii  python3-configobj5.0.6-3
ii  python3-pkg-resources41.2.0-1
ii  python3-setproctitle 1.1.10-1+b2
ii  python3-unidecode1.1.1-2
ii  python3-xdg  0.25-5
ii  python3-xlib 0.23-2
ii  xdg-utils1.1.3-1

mate-menu recommends no packages.

Versions of packages mate-menu suggests:
pn  software-center  
ii  synaptic 0.84.6+b1

-- no debconf information

Bug#936090: xfce4-settings: scrollbar disappears, doesn't want to come back

[Mike Kupfer]

Package: xfce4-settings
Version: 4.14.1-1
Severity: normal

Dear Maintainer,

Suppose I go to the Appearance section, which has a nice long list of
styles.

If I drag the scrollbar thumb and then pause while holding the (left)
mouse button down, the scrollbar disappears after about 3 seconds.
That's fine.  But if I release the mouse button and start moving the
mouse around in the list of styles, I'd like for the scrollbar to
reappear.  It doesn't.  Moving the input focus somewhere else and then
back to Appearance doesn't help.  I have to click in the window (not
necessarily in the style list) for the scrollbar to come back.

I've tried several different widget styles, and the problem seems
independent of the style.

I can't reproduce the problem with xfce4-terminal: the scrollbar stays
visible as long as I hold the mouse button.  I can reproduce the
problem with xfce4-settings-editor, but only when run from the
settings manager.  If I start xfce4-settings-editor directly from a
terminal emulator, the scrollbar stays visible as long as I hold the
mouse button.

I do have some GTK settings related to scrollbars.  I don't know if
they're relevant.

In settings.ini:

  gtk-primary-button-warps-slider=0

In gtk-3.0/gtk.css:

  .scrollbar {
  -GtkScrollbar-has-backward-stepper: 1;
  -GtkScrollbar-has-forward-stepper: 1;
  }
  
  scrollbar {
-GtkScrollbar-has-backward-stepper: true;
-GtkScrollbar-has-forward-stepper: true;
  }



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

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

Versions of packages xfce4-settings depends on:
ii  libatk1.0-0  2.33.3+really2.32.0-4
ii  libc62.28-10
ii  libcairo21.16.0-4
ii  libcolord2   1.4.3-4
ii  libexo-2-0   0.12.8-1
ii  libfontconfig1   2.13.1-2+b1
ii  libgarcon-1-00.6.4-1
ii  libgarcon-common 0.6.4-1
ii  libgdk-pixbuf2.0-0   2.38.1+dfsg-1
ii  libglib2.0-0 2.60.6-2
ii  libgtk-3-0   3.24.10-1
ii  libnotify4   0.7.8-1
ii  libpango-1.0-0   1.42.4-7
ii  libpangocairo-1.0-0  1.42.4-7
ii  libupower-glib3  0.99.10-1
ii  libx11-6 2:1.6.7-1
ii  libxcursor1  1:1.2.0-2
ii  libxfce4ui-2-0   4.14.1-1+b1
ii  libxfce4util74.14.0-1
ii  libxfconf-0-34.14.1-1
ii  libxi6   2:1.7.9-1
ii  libxklavier165.4-4
ii  libxrandr2   2:1.5.1-1
ii  xfconf   4.14.1-1

Versions of packages xfce4-settings recommends:
pn  colord 
ii  x11-utils  7.7+4
pn  xiccd  

xfce4-settings suggests no packages.

-- no debconf information

Bug#807063: dup of 881365?

[Mike Kupfer]

The symptoms of this bug sound like what is described in #881365.  That
bug lists a workaround.

regards,
mike

Bug#899148: xfdesktop4: xcb assertion failure when deleting a file

[Mike Kupfer]

Package: xfdesktop4
Version: 4.12.4-1
Severity: normal

Dear Maintainer,

I right-clicked on a desktop icon for a PDF and selected "move to
trash".  This apparently caused xfdesktop4 to crash.  I found this
text in .xsession-errors:

  [xcb] Unknown sequence number while processing queue
  [xcb] Most likely this is a multi-threaded client and XInitThreads has not 
been called
  [xcb] Aborting, sorry about that.
  xfdesktop: ../../src/xcb_io.c:259: poll_for_event: Assertion 
`!xcb_xlib_threads_sequence_lost' failed.

And I found a core file with the following stack:

  Core was generated by `xfdesktop --display :0.0 --sm-client-id 
29f38e940-3cce-4627-9f73-2a9b5e779bd4'.
  Program terminated with signal SIGABRT, Aborted.
  #0  __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:51
  51../sysdeps/unix/sysv/linux/raise.c: No such file or directory.
  [Current thread is 1 (Thread 0x7ffadb3f7a80 (LWP 14252))]
  (gdb) bt
  #0  __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:51
  #1  0x7ffad77de231 in __GI_abort () at abort.c:79
  #2  0x7ffad77d59da in __assert_fail_base (
  fmt=0x7ffad7928d48 "%s%s%s:%u: %s%sAssertion `%s' failed.\n%n", 
  assertion=assertion@entry=0x7ffadad743e0 
"!xcb_xlib_threads_sequence_lost", file=file@entry=0x7ffadad7424b 
"../../src/xcb_io.c", line=line@entry=259, 
  function=function@entry=0x7ffadad74688 <__PRETTY_FUNCTION__.14896> 
"poll_for_event") at assert.c:92
  #3  0x7ffad77d5a52 in __GI___assert_fail (
  assertion=assertion@entry=0x7ffadad743e0 
"!xcb_xlib_threads_sequence_lost", file=file@entry=0x7ffadad7424b 
"../../src/xcb_io.c", line=line@entry=259, 
  function=function@entry=0x7ffadad74688 <__PRETTY_FUNCTION__.14896> 
"poll_for_event") at assert.c:101
  #4  0x7ffadad033ca in poll_for_event (dpy=dpy@entry=0x556075846370)
  at ../../src/xcb_io.c:256
  #5  0x7ffadad0346e in poll_for_response (dpy=dpy@entry=0x556075846370)
  at ../../src/xcb_io.c:274
  #6  0x7ffadad0375d in _XEventsQueued (dpy=dpy@entry=0x556075846370, 
  mode=mode@entry=2) at ../../src/xcb_io.c:349
  #7  0x7ffadacf52cd in XPending (dpy=0x556075846370)
  at ../../src/Pending.c:55
  #8  0x7ffad95100a5 in gdk_check_xpending (display=)
  at ./gdk/x11/gdkevents-x11.c:159
  #9  gdk_event_check (source=0x556075874ea0) at ./gdk/x11/gdkevents-x11.c:2400
  #10 0x7ffad7dd3e51 in g_main_context_check (
  context=context@entry=0x55607582f8b0, max_priority=2147483647, 
  fds=fds@entry=0x5560759a09d0, n_fds=n_fds@entry=5)
  at ../../../../glib/gmain.c:3736
  #11 0x7ffad7dd43e0 in g_main_context_iterate (context=0x55607582f8b0, 
  block=block@entry=1, dispatch=dispatch@entry=1, self=)
  at ../../../../glib/gmain.c:3900
  #12 0x7ffad7dd47d2 in g_main_loop_run (loop=0x556075995650)
  at ../../../../glib/gmain.c:4099
  #13 0x7ffad989f977 in IA__gtk_main () at ./gtk/gtkmain.c:1270
  #14 0x5560745d3780 in xfdesktop_application_start (app=0x55607582b150)
  at xfdesktop-application.c:768
  #15 0x5560745d3be6 in cb_wait_for_window_manager_destroyed (
  data=0x7ffac0007d80) at xfdesktop-application.c:630
  #16 0x7ffad7dd0ae3 in g_source_callback_unref (cb_data=0x5560758b91d0)
  at ../../../../glib/gmain.c:1546
  #17 0x7ffad7dd155c in g_source_destroy_internal (source=0x5560758d1560, 
  context=0x55607582f8b0, have_lock=1) at ../../../../glib/gmain.c:1236
  #18 0x7ffad7dd4180 in g_main_dispatch (context=0x55607582f8b0)
  at ../../../../glib/gmain.c:3201
  #19 g_main_context_dispatch (context=context@entry=0x55607582f8b0)
  at ../../../../glib/gmain.c:3830
  #20 0x7ffad7dd44c0 in g_main_context_iterate (
  context=context@entry=0x55607582f8b0, block=block@entry=1, 
  dispatch=dispatch@entry=1, self=)
  at ../../../../glib/gmain.c:3903
  #21 0x7ffad7dd454c in g_main_context_iteration (
  context=context@entry=0x55607582f8b0, may_block=may_block@entry=1)
  at ../../../../glib/gmain.c:3964
  #22 0x7ffad881acdd in g_application_run (application=0x55607582b150, 
  argc=, argv=)
  at ../../../../gio/gapplication.c:2470
  #23 0x5560745c8c8d in main (argc=5, argv=0x7ffed54983e8) at main.c:86

I have not been able to reproduce the crash.  After xfdesktop4
restarted, I was able to delete the PDF file (right-click, move to
trash).

The system is a VirtualBox guest.  The host is running Debian Stretch
with VirtualBox 5.2.12.  The guest is running with the 5.2.12 Guest
Additions.

Some 5-10 minutes before the crash, I had installed a bunch of
updates, logged out, logged in again, and then created the PDF file
(printing from Firefox).  I did not do any operations on desktop
objects prior to the attempted deletion.


-- System Information:
Debian Release: buster/sid
  APT prefers testing-debug
  APT policy: (500, 'testing-debug'), (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 4.16.0-1-amd64 (SMP w/2 CPU 

Bug#881365: try installing policykit-1-gnome

[Mike Kupfer]

I dug a little deeper into the differences between MATE and Xfce.

If I run synaptic-pkexec as myself from a shell in a terminal emulator,
it works with MATE: I get a pop-up that prompts for the root password,
and I eventually get Synaptic.

If I ran it with Xfce, I didn't get a pop-up.  And entering the root
password didn't work.

  $ synaptic-pkexec 
   AUTHENTICATING FOR com.ubuntu.pkexec.synaptic ===
  Authentication is required to run the Synaptic Package Manager
  Authenticating as: root
  Password: 
  polkit-agent-helper-1: error response to PolicyKit daemon: 
GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for cookie
   AUTHENTICATION FAILED ===
  Error executing command as another user: Not authorized
  
  This incident has been reported.
  $ 
  
The "no session" error led me to wonder if there was a daemon missing.
I installed policykit-1-gnome, logged out, and then logged in again.
And now I can start Synaptic from the Xfce main menu.

Bug#881365: Synaptic Does Not Work on XFCE Unless Launched from Terminal.

[Mike Kupfer]

Package: synaptic
Version: 0.84.2
Followup-For: Bug #881365

Dear Maintainer,

I am seeing the same issue: if I try to start Synaptic from the Xfce
main menu, there is no visible activity.  If I want to run Synaptic in
Xfce, I start it from a root shell process.

This may be a bug in some Xfce package.  Starting Synaptic from the
menu works fine in MATE.

regards,
mike

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

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

Versions of packages synaptic depends on:
ii  hicolor-icon-theme   0.17-1
ii  libapt-inst2.0   1.6~beta1
ii  libapt-pkg5.01.6~beta1
ii  libatk1.0-0  2.26.1-3
ii  libc62.27-2
ii  libcairo-gobject21.15.10-1
ii  libcairo21.15.10-1
ii  libept1.5.0  1.1+nmu3+b1
ii  libgcc1  1:8-20180312-2
ii  libgdk-pixbuf2.0-0   2.36.11-1
ii  libglib2.0-0 2.54.3-2
ii  libgnutls30  3.5.18-1
ii  libgtk-3-0   3.22.28-1
ii  libpango-1.0-0   1.40.14-1
ii  libpangocairo-1.0-0  1.40.14-1
ii  libpcre2-8-0 10.31-3
ii  libstdc++6   8-20180312-2
ii  libvte-2.91-00.50.2-4
ii  libx11-6 2:1.6.4-3
ii  libxapian30  1.4.5-1
ii  policykit-1  0.105-18
ii  zlib1g   1:1.2.8.dfsg-5

Versions of packages synaptic recommends:
ii  libgtk2-perl   2:1.24992-1+b1
pn  rarian-compat  
ii  xdg-utils  1.1.2-2

Versions of packages synaptic suggests:
ii  apt-xapian-index 0.49
pn  deborphan
pn  dwww 
ii  menu 2.1.47+b1
pn  software-properties-gtk  
ii  tasksel  3.43

-- no debconf information

Bug#887860: tracker-extract: repeated SIGSYS in execve()

[Mike Kupfer]

Simon McVittie wrote:

> On Sat, 20 Jan 2018 at 15:58:38 -0800, Mike Kupfer wrote:

> > Hmm.  Synaptic reports 4 locally installed gstreamer packages:
> > 
> >   gstreamer0.10-fluendo-mp3
> >   gstreamer0.10-plugins-base
> >   libgstreamer0.10-0
> >   libgstreamer-plugins-base0.10
> 
> It's good to have removed these, but GStreamer 0.10 and 1.0 are separate
> (and any modern version of tracker-extract uses 1.0), so these shouldn't
> affect anything.

Indeed, tracker-extract (well, GStreamer) still tries on occasion to run
gst-plugin-scanner, with tracker-extract dying as a result.

regards,
mike

Bug#887860: tracker-extract: repeated SIGSYS in execve()

[Mike Kupfer]

Simon McVittie wrote:

> I'm not sure under what circumstances GStreamer runs gst-plugin-scanner:
> it must be something slightly unusual about your system, perhaps a
> locally-installed GStreamer plugin with a timestamp newer than the
> registry of available plugins, otherwise other people would see this
> bug all the time.

Hmm.  Synaptic reports 4 locally installed gstreamer packages:

  gstreamer0.10-fluendo-mp3
  gstreamer0.10-plugins-base
  libgstreamer0.10-0
  libgstreamer-plugins-base0.10

I suspect these are left over from when the system was upgraded from
Jessie to Stretch.

I've removed the packages and will report back if any new core files
appear.

thanks,
mike

Bug#887860: tracker-extract: repeated SIGSYS in execve()

[Mike Kupfer]

Package: tracker-extract
Version: 1.10.5-1
Severity: normal

Dear Maintainer,

Every few days I find a core file in $HOME.  file(1) tells me they're
coming from tracker-extract.  I've taken a quick look at a couple with
gdb, and (IIRC), gdb has said each time that tracker-extract died with
SIGSYS in execve().

I haven't been able to determine if a particular file is causing the
crashes or if it's a more general problem.

Today I finally got around to getting a stack trace:

alto$ ls -l core
-rw--- 1 kupfer kupfer 192376832 Jan 20 07:29 core
alto$ file core
core: ELF 64-bit LSB core file x86-64, version 1 (SYSV), SVR4-style, from 
'/usr/lib/tracker/tracker-extract', real uid: 1000, effective uid: 1000, real 
gid: 1000, effective gid: 1000, execfn: '/usr/lib/tracker/tracker-extract', 
platform: 'x86_64'
alto$ gdb /usr/lib/tracker/tracker-extract core
GNU gdb (Debian 7.12-6) 7.12.0.20161007-git
Copyright (C) 2016 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
.
Find the GDB manual and other documentation resources online at:
.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from /usr/lib/tracker/tracker-extract...(no debugging symbols 
found)...done.

warning: core file may not match specified executable file.
[New LWP 11353]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
Core was generated by `/usr/lib/tracker/tracker-extract'.
Program terminated with signal SIGSYS, Bad system call.
#0  0x7fde9d6c3677 in execve () at ../sysdeps/unix/syscall-template.S:84
84  ../sysdeps/unix/syscall-template.S: No such file or directory.
(gdb) bt
#0  0x7fde9d6c3677 in execve () at ../sysdeps/unix/syscall-template.S:84
#1  0x7fde9d6c376f in execv (path=, argv=)
at execv.c:25
#2  0x7fde9dc5c31e in g_execute (search_path_from_envp=0, search_path=0, 
envp=0x0, argv=0x7fde6bb198b0, file=0x7fde641bb000 
"/usr/lib/x86_64-linux-gnu/gstreamer1.0/gstreamer-1.0/gst-plugin-scanner") at 
././glib/gspawn.c:1680
#3  0x7fde9dc5c31e in do_exec (child_err_report_fd=18, stdin_fd=, stdout_fd=22, stderr_fd=-1, 
working_directory=working_directory@entry=0x0, argv=argv@entry=0x7fde6bb198b0, 
envp=0x0, close_descriptors=1, search_path=0, search_path_from_envp=0, 
stdout_to_null=0, stderr_to_null=0, child_inherits_stdin=0, 
file_and_argv_zero=0, child_setup=0x0, user_data=0x0)
at ././glib/gspawn.c:1229
#4  0x7fde9dc5cb01 in fork_exec_with_pipes 
(intermediate_child=intermediate_child@entry=0, 
working_directory=working_directory@entry=0x0, argv=argv@entry=0x7fde6bb198b0, 
envp=envp@entry=0x0, close_descriptors=close_descriptors@entry=1, 
search_path=search_path@entry=0, search_path_from_envp=0, stdout_to_null=0, 
stderr_to_null=0, child_inherits_stdin=0, file_and_argv_zero=0, 
cloexec_pipes=0, child_setup=0x0, user_data=0x0, child_pid=0x7fde6400a6d4, 
standard_input=0x7fde6400a6d8, standard_output=0x7fde6400a6e0, 
standard_error=0x0, error=0x0)
at ././glib/gspawn.c:1426
#5  0x7fde9dc5d545 in g_spawn_async_with_pipes 
(working_directory=working_directory@entry=0x0, argv=argv@entry=0x7fde6bb198b0, 
envp=envp@entry=0x0, flags=flags@entry=G_SPAWN_DO_NOT_REAP_CHILD, 
child_setup=child_setup@entry=0x0, user_dat---Type  to continue, or q 
 to quit---
a=user_data@entry=0x0, child_pid=0x7fde6400a6d4, standard_input=0x7fde6400a6d8, 
standard_output=0x7fde6400a6e0, standard_error=0x0, error=0x0)
at ././glib/gspawn.c:656
#6  0x7fde70930ea9 in gst_plugin_loader_try_helper 
(loader=loader@entry=0x7fde6400a6c0, location=location@entry=0x7fde641bb000 
"/usr/lib/x86_64-linux-gnu/gstreamer1.0/gstreamer-1.0/gst-plugin-scanner") at 
gstpluginloader.c:431
#7  0x7fde70930fd1 in gst_plugin_loader_spawn (loader=0x7fde6400a6c0)
at gstpluginloader.c:494
#8  0x7fde70931555 in gst_plugin_loader_spawn (loader=0x7fde6400a6c0)
at gstpluginloader.c:258
#9  0x7fde70931555 in plugin_loader_load (loader=0x7fde6400a6c0, 
filename=0x7fde641b92c0 
"/usr/lib/x86_64-linux-gnu/gstreamer-1.0/libgstvaapi.so", file_size=732184, 
file_mtime=1487860804) at gstpluginloader.c:228
#10 0x7fde7093a73c in gst_registry_scan_plugin_file 
(context=context@entry=0x7fde6bb19b00, filename=filename@entry=0x7fde641b92c0 
"/usr/lib/x86_64-linux-gnu/gstreamer-1.0/libgstvaapi.so", file_size=732184, 
file_mtime=1487860804)
at gstregistry.c:1176
#11 0x7fde7093b8a1 in gst_registry_scan_path_level 
(context=context@entry=0x7fde6bb19b00, path=pa

Bug#862037: xfce4-systemload-plugin: frequent core files from systemload plugin

[Mike Kupfer]

Package: xfce4-systemload-plugin
Version: 1.1.2-1+b1
Severity: normal

Dear Maintainer,

I frequently notice a core file in $HOME.  The timestamps on the core
files suggest that they are generated when I log out.

$ file core
core: ELF 64-bit LSB core file x86-64, version 1 (SYSV), SVR4-style, from 
'/usr/lib/x86_64-linux-gnu/xfce4/panel/wrapper-1.0 
/usr/lib/x86_64-linux-gnu/xfc', real uid: 1000, effective uid: 1000, real gid: 
1000, effective gid: 1000, execfn: 
'/usr/lib/x86_64-linux-gnu/xfce4/panel/wrapper-1.0', platform: 'x86_64'

Suspecting this might be from the System Load Monitor plugin, I
right-clicked on it and removed it, which yielded another core.

Re-adding the plugin to the panel and immediately removing it (i.e.,
without changing its configuration) produced yet another core file.

I've seen core files when I use this plugin on Oracle Linux 7, so I
suspect--but am not certain--that this is an upstream bug.

Here's a stack trace from gdb.

$ gdb /usr/lib/x86_64-linux-gnu/xfce4/panel/wrapper-1.0 core.bugreport
GNU gdb (Debian 7.12-6) 7.12.0.20161007-git
Copyright (C) 2016 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
.
Find the GDB manual and other documentation resources online at:
.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from /usr/lib/x86_64-linux-gnu/xfce4/panel/wrapper-1.0...(no 
debugging symbols found)...done.

warning: core file may not match specified executable file.
[New LWP 2159]
[New LWP 2160]
[New LWP 2161]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
Core was generated by `/usr/lib/x86_64-linux-gnu/xfce4/panel/wrapper-1.0 
/usr/lib/x86_64-linux-gnu/xfc'.
Program terminated with signal SIGABRT, Aborted.
#0  __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:51
51  ../sysdeps/unix/sysv/linux/raise.c: No such file or directory.
[Current thread is 1 (Thread 0x7fb597310a80 (LWP 2159))]
(gdb) bt
#0  __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:51
#1  0x7fb5950133fa in __GI_abort () at abort.c:89
#2  0x7fb59504fbd0 in __libc_message (do_abort=do_abort@entry=2, 
fmt=fmt@entry=0x7fb595144bd0 "*** Error in `%s': %s: 0x%s ***\n")
at ../sysdeps/posix/libc_fatal.c:175
#3  0x7fb595055f96 in malloc_printerr (action=3, 
str=0x7fb59514176d "free(): invalid pointer", ptr=, 
ar_ptr=) at malloc.c:5046
#4  0x7fb59505678e in _int_free (av=0x7fb595377b00 , 
p=0x55c345ae39c0, have_lock=0) at malloc.c:3902
#5  0x7fb58e43abee in ?? ()
   from /usr/lib/x86_64-linux-gnu/xfce4/panel/plugins/libsystemload.so
#6  0x7fb595cdef75 in g_closure_invoke (closure=0x55c345af53b0, 
return_value=return_value@entry=0x0, n_param_values=1, 
param_values=param_values@entry=0x7ffd3e241630, 
invocation_hint=invocation_hint@entry=0x7ffd3e2415b0)
at ././gobject/gclosure.c:804
#7  0x7fb595cf0f82 in signal_emit_unlocked_R (
node=node@entry=0x55c345aa8650, detail=detail@entry=0, 
instance=instance@entry=0x55c345a9f0c0, 
emission_return=emission_return@entry=0x0, 
instance_and_params=instance_and_params@entry=0x7ffd3e241630)
at ././gobject/gsignal.c:3635
---Type  to continue, or q  to quit---
#8  0x7fb595cf9bdc in g_signal_emit_valist (instance=, 
signal_id=, detail=, 
var_args=var_args@entry=0x7ffd3e2417e0) at ././gobject/gsignal.c:3391
#9  0x7fb595cf9fbf in g_signal_emit (instance=, 
signal_id=, detail=)
at ././gobject/gsignal.c:3447
#10 0x7fb596f9fe87 in ?? ()
   from /usr/lib/x86_64-linux-gnu/libxfce4panel-1.0.so.4
#11 0x7fb595ce5648 in g_object_run_dispose (object=0x55c345a9f0c0)
at ././gobject/gobject.c:1084
#12 0x7fb5969fefdf in gtk_container_destroy (object=0x55c345ac7090)
at ./gtk/gtkcontainer.c:1073
#13 0x7fb595cdef75 in g_closure_invoke (
closure=closure@entry=0x55c345a81400, return_value=return_value@entry=0x0, 
n_param_values=1, param_values=param_values@entry=0x7ffd3e241ab0, 
invocation_hint=invocation_hint@entry=0x7ffd3e241a30)
at ././gobject/gclosure.c:804
#14 0x7fb595cf1296 in signal_emit_unlocked_R (
node=node@entry=0x55c345a81450, detail=detail@entry=0, 
instance=instance@entry=0x55c345ac7090, 
emission_return=emission_return@entry=0x0, 
instance_and_params=instance_and_params@entry=0x7ffd3e241ab0)
at ././gobject/gsignal.c:3751
---Type  to continue, or q  to quit---
#15 0x7fb595cf9bdc in g_signal_emit

Bug#779892: workaround: disable join dialog

[Mike Kupfer]

Mattia Rizzolo wrote:

> I happen to be the new hexchat maintainer in Debian :)

Hi, pleased to meet you. :-)

> You haven't provide this "improved" stack trace, but more importantly,
> there is now a quite new version I'd like you to try, 2.12.4.  Could
> you?

Yeah, sorry about never getting the improved stack trace.

Sure, I can try 2.12.4.  I see it's in testing, so I'll update my
testing VM and give it a spin.  I'll try to find time this weekend.

cheers,
mike

Bug#849828: xpad: [text] changed to /text/

[Mike Kupfer]

Package: xpad
Version: 4.8.0-1
Severity: normal

Dear Maintainer,

I have a pad that contains some notes about a bug that I wanted to
file a report on.  After filing the bug report, I added the following
text to the pad:

[bug filed 31dec16]

The next time I started xpad, the text appeared as

/bug filed 31dec16/

Looking at the saved text in $HOME/.config/xpad/, I see that the text
was saved as

u+e000[u+e000/bug filed 31dec16u+e000]u+e000/

(where "u+e000" represents a single unicode character with the value
0xe000).

When I originally entered the text, the matching square brackets got
highlighted.  Perhaps the u+e000 and "/" have something to do with the
highlighting?

What I expect is that when I start xpad, it shows me the text that I
had typed in.  I don't care whether the brackets are highlighted.


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

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

Versions of packages xpad depends on:
ii  libatk1.0-0 2.22.0-1
ii  libc6   2.24-8
ii  libcairo-gobject2   1.14.8-1
ii  libcairo2   1.14.8-1
ii  libgdk-pixbuf2.0-0  2.36.0-1
ii  libglib2.0-02.50.2-2
ii  libgtk-3-0  3.22.5-1
ii  libgtksourceview-3.0-1  3.22.1-1
ii  libice6 2:1.0.9-1+b1
ii  libpango-1.0-0  1.40.3-3
ii  libpangocairo-1.0-0 1.40.3-3
ii  libsm6  2:1.2.2-1+b1

xpad recommends no packages.

xpad suggests no packages.

-- no debconf information

Bug#849823: xfdesktop4: can't click to select a folder with background images

[Mike Kupfer]

Package: xfdesktop4
Version: 4.12.3-3
Severity: normal

Dear Maintainer,

Suppose I want to use a background image that is in a different folder
than my current background image.  I bring up the Desktop Settings
window (right-click on the desktop), click on the Folder
chooser in the Background tab, then click "other...".  This brings up
a chooser, with a pathbar at the top.

The buttons in the pathbar work.  For example, if my current
background is in /usr/share/backgrounds/xfce, I can click on
"backgrounds" in the pathbar, and the chooser shows other folders in
/usr/share/backgrounds.  The problem is that these other folders are
grayed out; clicking on them has no effect.

Workaround: click on the icon in the upper left of the chooser.  This
creates a Location text field in the chooser window.  Type the path of
the desired folder there.

This might be the same as #822761, but I'm not sure, so I'm filing
this as a new bug.  Part of why I'm not sure is that I'm confused by
the title of the chooser.  It says "Select a File".  But is it really
used to select an image file, or is it just supposed to be used to
select a folder?

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

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

Versions of packages xfdesktop4 depends on:
ii  exo-utils0.10.7-1
ii  libc62.24-8
ii  libcairo21.14.8-1
ii  libdbus-1-3  1.10.14-1
ii  libdbus-glib-1-2 0.108-1
ii  libexo-1-0   0.10.7-1
ii  libgarcon-1-00.4.0-2
ii  libgdk-pixbuf2.0-0   2.36.0-1
ii  libglib2.0-0 2.50.2-2
ii  libgtk2.0-0  2.24.31-1
ii  libnotify4   0.7.7-1
ii  libpango-1.0-0   1.40.3-3
ii  libpangocairo-1.0-0  1.40.3-3
ii  libthunarx-2-0   1.6.10-4
ii  libwnck222.30.7-5.1
ii  libx11-6 2:1.6.4-2
ii  libxfce4ui-1-0   4.12.1-2
ii  libxfce4util74.12.1-3
ii  libxfconf-0-24.12.1-1
ii  xfdesktop4-data  4.12.3-3

Versions of packages xfdesktop4 recommends:
ii  dbus-x11 [dbus-session-bus]  1.10.14-1
ii  librsvg2-common  2.40.16-1
ii  tumbler  0.1.31-2+b3
ii  xdg-user-dirs0.15-2

Versions of packages xfdesktop4 suggests:
ii  menu  2.1.47

-- no debconf information

Bug#849793: xpad: "restore to previous state" fails to open notes

[Mike Kupfer]

Package: xpad
Version: 4.8.0-1
Severity: normal

Dear Maintainer,

In the Startup tab for Xpad preferences, if I set "Display pads" to
"Restore to previous state", it doesn't work for open pads.  That is,
if I have pads open and then restart Xpad, the pads are not reopened.

"Open all pads" does work.


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

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

Versions of packages xpad depends on:
ii  libatk1.0-0 2.22.0-1
ii  libc6   2.24-8
ii  libcairo-gobject2   1.14.8-1
ii  libcairo2   1.14.8-1
ii  libgdk-pixbuf2.0-0  2.36.0-1
ii  libglib2.0-02.50.2-2
ii  libgtk-3-0  3.22.5-1
ii  libgtksourceview-3.0-1  3.22.1-1
ii  libice6 2:1.0.9-1+b1
ii  libpango-1.0-0  1.40.3-3
ii  libpangocairo-1.0-0 1.40.3-3
ii  libsm6  2:1.2.2-1+b1

xpad recommends no packages.

xpad suggests no packages.

-- no debconf information

Bug#849792: xpad: selection not visible when using custom colors

[Mike Kupfer]

Package: xpad
Version: 4.8.0-1
Severity: normal

Dear Maintainer,

If I configure xpad to use specific text and background colors (rather than
"colors from theme"), there's no visible feedback when I select text in a
note (e.g., doing click and drag).  The text is selected (I can copy and
paste it), but the lack of visible feedback makes it hard to use.

I see this on both Xfce and Mate.  It seems to be independent of the 
background color that I choose and independent of the current GTK theme.



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

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

Versions of packages xpad depends on:
ii  libatk1.0-0 2.22.0-1
ii  libc6   2.24-8
ii  libcairo-gobject2   1.14.8-1
ii  libcairo2   1.14.8-1
ii  libgdk-pixbuf2.0-0  2.36.0-1
ii  libglib2.0-02.50.2-2
ii  libgtk-3-0  3.22.5-1
ii  libgtksourceview-3.0-1  3.22.1-1
ii  libice6 2:1.0.9-1+b1
ii  libpango-1.0-0  1.40.3-3
ii  libpangocairo-1.0-0 1.40.3-3
ii  libsm6  2:1.2.2-1+b1

xpad recommends no packages.

xpad suggests no packages.

-- no debconf information

Bug#810742: upstream bug

[Mike Kupfer]

The upstream bug for this is

  https://sourceforge.net/p/mh-e/bugs/476/

regards,
mike

Bug#846977: [Pkg-xfce-devel] Bug#846977: thunar: thumbnail for rotated jpeg appears as unrotated

[Mike Kupfer]

Yves-Alexis Perez wrote:

> So you have a jpeg file /path/to/file.jpg, you open /path/to with Thunar and
> the thumbnail is generated. Then you open the file in Shotwell, rotate it,
> then save the rotated file in /path/to/other/file.jpg. Then when you open
> /path/to/other in Thunar the thumbnail is already there and is not rotated.

No, the image was imported directly from the camera to Shotwell on a
Jessie system.  I'm afraid I don't remember how I got the image out of
Shotwell.

Hmm.  If I look at the directory in Shotwell's storage area using any of
Thunar, Nautilus, or Caja, the file appears unrotated (landscape
orientation).  It has an md5sum of

  306c0a274435016922cea2f3c1898819

and jpegexiforient says it has an Exif Orientation Tag of 1.

Maybe I rotated the file outside Shotwell (e.g., using Eye of GNOME or
Eye of MATE).  But I think that trying to figure out how I produced the
image is a distraction.

I have a copy of the sample file (message #10 of the bug report) in a
separate folder, on both the Jessie system and the Stretch VM that I
submitted the bug from.  The md5sum for this file is

  5445cbb90960a93259db3b7045cdaf77

and jpegexiforient says it has an orientation of 8.

On Jessie:

If I open that folder using Caja or Nautilus, the sample file appears
rotated.  If I open the same folder using Thunar, it appears unrotated.
(I can have both Caja and Thunar open at the same time; Caja shows the
image rotated, Thunar shows it unrotated.)

If I open the sample file using GIMP, I get a popup saying that the exif
data says the image should be rotated and do I want to do that.  If I
click on Rotate, I get the rotated image.  If I dismiss the popup, I get
the unrotated image.  So perhaps with Thunar the exif data is getting
ignored when the thumbnail is generated.

On Stretch:

It depends on which program I run first.  If I delete the cached
thumbnails and then view the folder using Caja, both Caja and Thunar
show the image as rotated.  If I clear the thumbnail cache again and
then view the folder using Thunar, both Caja and Thunar show the image
as unrotated.  (I guess with Stretch they share the same thumbnail
cache?)

I hope this gives you the information you were looking for.  If not, let
me know what I missed and I'll try again.

cheers,
mike

Bug#846977: thunar: thumbnail for rotated jpeg appears as unrotated

[Mike Kupfer]

Package: thunar
Version: 1.6.10-4
Severity: normal

Dear Maintainer,

I have several photos that I have rotated in Shotwell and then saved the
JPEG to some other directory.  Xfce (Thunar, xfdesktop4) shows the
thumbnail in its original orientation (unrotated).  But if I delete the
thumbnail and then view the directory in MATE or GNOME (i.e., using Caja
or Nautilus), the thumbnail is shown rotated.  If I open the jpeg, the
image is shown rotated, so I view the unrotated thumbnail as a bug.

I can't tell if this is a problem with Xfce or whatever thumbnailer
Xfce uses (tumbler?); please reassign if appropriate.

I see the problem in both Jessie and Stretch.

I will attach a sample file.

regards,
mike

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

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

Versions of packages thunar depends on:
ii  desktop-file-utils  0.23-1
ii  exo-utils   0.10.7-1
ii  libatk1.0-0 2.22.0-1
ii  libc6   2.24-7
ii  libcairo2   1.14.6-1.1
ii  libdbus-1-3 1.10.14-1
ii  libdbus-glib-1-20.108-1
ii  libexo-1-0  0.10.7-1
ii  libgdk-pixbuf2.0-0  2.36.0-1
ii  libglib2.0-02.50.2-2
ii  libgtk2.0-0 2.24.31-1
ii  libgudev-1.0-0  230-3
ii  libice6 2:1.0.9-1+b1
ii  libnotify4  0.7.7-1
ii  libpango-1.0-0  1.40.3-3
ii  libsm6  2:1.2.2-1+b1
ii  libthunarx-2-0  1.6.10-4
ii  libxfce4ui-1-0  4.12.1-2
ii  libxfce4util7   4.12.1-3
ii  libxfconf-0-2   4.12.1-1
ii  shared-mime-info1.7-1
ii  thunar-data 1.6.10-4

Versions of packages thunar recommends:
ii  dbus-x11 1.10.14-1
ii  gvfs 1.30.2-2
ii  libfontconfig1   2.11.0-6.7
ii  libfreetype6 2.6.3-3+b1
ii  libpangocairo-1.0-0  1.40.3-3
ii  libpangoft2-1.0-01.40.3-3
ii  thunar-volman0.8.1-2
ii  tumbler  0.1.31-2+b3
ii  xdg-user-dirs0.15-2
ii  xfce4-panel  4.12.1-2

Versions of packages thunar suggests:
pn  thunar-archive-plugin 
pn  thunar-media-tags-plugin  

-- no debconf information

Bug#843341: lxde: installing lxde doesn't give me an LXDE session

[Mike Kupfer]

Hi Andriy, thanks for the prompt response.

Andriy Grytsenko wrote:

> Thank you very much for reporting this. Apparently this issue is coming
> from the fact there is no lxde-session package which is named lxde-common
> and therefore many are confused because lxde package is just metapackage
> with components but session files itself.

Well, the dependencies in Jessie are set up so that task-lxde-desktop
pulls in lxde; lxde pulls in lxde-core; and lxde-core pulls in
lxde-common; lxde-common contains the xsession file.

This makes it convenient for users:

- if they want a full LXDE desktop with all the standard Debian
  applications, they just install task-lxde-desktop

- if they want a "standard" LXDE desktop, they just install lxde

- if they want a minimal LXDE desktop, they install lxde-core

I think that's the way things should work in Stretch, too.

I'm not sure what fix you have in mind, but I'm guessing that you're
thinking about renaming lxde-common.  If you require users to install
that package in addition to one of the metapackages, you'll make LXDE
more work to install compared to how things are in Jessie.

warm regards,
mike

Bug#843341: lxde: installing lxde doesn't give me an LXDE session

[Mike Kupfer]

Package: lxde
Version: 7
Severity: normal

Dear Maintainer,

Using Synaptic in an XFCE session, I installed the "lxde" package.
After logging out, I expected to be able to select the LXDE session in
the lightdm controls, but LXDE was not listed.  I had to install
lxde-common as well to get an LXDE session.  Also, when installing
lxde-common, I noticed that it, not lxde, pulled in openbox.

I guess lxde-common was not pulled in because I already had a package
installed that provides x-session-manager.  I think that for most
users, this does not provide the right behavior.  And the current
behavior doesn't align with the documentation in
https://wiki.debian.org/LXDE.



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

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

Versions of packages lxde depends on:
ii  galculator 2.1.4-1
ii  gpicview   0.2.5-2
ii  leafpad0.8.18.1-5
ii  lxappearance   0.6.2-1
ii  lxappearance-obconf0.2.3-1
ii  lxde-common [x-session-manager]0.99.1-1
ii  lxde-core  7
ii  lxde-icon-theme0.5.1-1
ii  lxinput0.3.5-1
ii  lxrandr0.3.1-1
ii  lxsession [x-session-manager]  0.5.1-2
pn  lxsession-edit 
ii  lxterminal 0.2.0-1
ii  openbox [x-session-manager]3.6.1-3
ii  xarchiver  1:0.5.4-5
ii  xfce4-session [x-session-manager]  4.12.1-4

Versions of packages lxde recommends:
pn  alsamixergui 
pn  clipit   
pn  deluge | transmission-gtk
pn  evince-gtk | pdf-viewer  
pn  gnome-disk-utility   
pn  gnome-mplayer
pn  gnome-system-tools   
ii  gucharmap1:9.0.1-1
ii  i3-wm [x-window-manager] 4.12-2
ii  lightdm [x-display-manager]  1.18.2-2
pn  lxmusic | audacious  
ii  lxsession [lxpolkit] 0.5.1-2
pn  menu-xdg 
ii  network-manager-gnome1.4.2-1
ii  openbox [x-window-manager]   3.6.1-3
pn  usermode 
ii  w3m [www-browser]0.5.3-31
ii  xfwm4 [x-window-manager] 4.12.3-3
ii  xserver-xorg 1:7.7+16

Versions of packages lxde suggests:
pn  gimp
ii  gnome-packagekit [update-notifier]  3.20.0-1
pn  libreoffice 
pn  lxlauncher  
pn  lxtask  
pn  pidgin  
ii  xfce4-power-manager 1.4.4-4

-- no debconf information

Bug#815313: network-manager-gnome: nm-applet crashes after connecting to OpenConnect VPN

[Mike Kupfer]

Mike Miller wrote:

> Also please take a look at #815668, looks like the same error to me.

Agreed.

mike

Bug#815313: network-manager-gnome: nm-applet crashes after connecting to OpenConnect VPN

[Mike Kupfer]

Mike Miller wrote:

> Still failing with 1.1.91-1?

Nope, 1.1.91-1 works fine.  (Well, I can't configure OpenConnect, but I
guess that's to be expected until you update the plugin.  I can connect
using the OpenConnect VPN that I already had configured.)

thanks,
mike

Bug#815313: network-manager-gnome: nm-applet crashes after connecting to OpenConnect VPN

[Mike Kupfer]

Package: network-manager-gnome
Version: 1.1.90-3
Severity: normal

Dear Maintainer,

I have an account on an OpenConnect (AnyConnect) VPN.  I can
successfully connect to the VPN, but when I do, nm-applet dies.  It
leaves behind a core file with the following stack trace:

#0  0x7fc701ef3507 in raise () from /lib/x86_64-linux-gnu/libc.so.6
#1  0x7fc701ef48da in abort () from /lib/x86_64-linux-gnu/libc.so.6
#2  0x7fc702720b75 in g_assertion_message (
domain=domain@entry=0x4334fc "nm-applet", 
file=file@entry=0x433288 "applet.c", line=line@entry=1227, 
func=func@entry=0x434d20 "applet_get_first_active_vpn_connection", 
message=message@entry=0x25f0560 "assertion failed: (s_con)")
at /build/glib2.0-2.46.2/./glib/gtestutils.c:2429
#3  0x7fc702720c0a in g_assertion_message_expr (
domain=0x4334fc "nm-applet", file=0x433288 "applet.c", line=1227, 
func=0x434d20 "applet_get_first_active_vpn_connection", 
expr=) at /build/glib2.0-2.46.2/./glib/gtestutils.c:2444
#4  0x0041297f in ?? ()
#5  0x004188fe in ?? ()
#6  0x7fc7026fae8a in g_main_dispatch (context=0x24da480)
at /build/glib2.0-2.46.2/./glib/gmain.c:3154
#7  g_main_context_dispatch (context=context@entry=0x24da480)
at /build/glib2.0-2.46.2/./glib/gmain.c:3769
#8  0x7fc7026fb230 in g_main_context_iterate (context=0x24da480, 
block=block@entry=1, dispatch=dispatch@entry=1, self=)
at /build/glib2.0-2.46.2/./glib/gmain.c:3840
#9  0x7fc7026fb552 in g_main_loop_run (loop=0x24a0d70)
at /build/glib2.0-2.46.2/./glib/gmain.c:4034
#10 0x00411f22 in main ()

I see these messages in .xsession-errors, though I'm don't know if any
of them are relevant (other than the one about
applet_get_first_active_vpn_connection assertion failure):

  ** (nm-applet:6746): WARNING **: Couldn't register with accessibility bus: 
Did not receive a reply. Possible causes include: the remote application did 
not send a reply, the message bus security policy blocked the reply, the reply 
timeout expired, or the network connection was broken.
  [...]
  nm-applet:ERROR:applet.c:1227:applet_get_first_active_vpn_connection: 
assertion failed: (s_con)
  Gtk-Message: GtkDialog mapped without a transient parent. This is discouraged.
  [...]
  ** Message: vpn: 
(openconnect,/etc/NetworkManager/VPN/nm-openconnect-service.name) cannot load 
legacy-only plugin

Hmm.  That last message ("cannot load legacy-only plugin") probably
explains why I can't edit the configuration for the VPN account...

This is with Xfce.

The workaround is to restart nm-applet.

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

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

Versions of packages network-manager-gnome depends on:
ii  dbus-x11 1.10.6-1
ii  dconf-gsettings-backend [gsettings-backend]  0.24.0-2
ii  gnome-icon-theme 3.12.0-1
ii  libatk1.0-0  2.18.0-1
ii  libc62.21-8
ii  libcairo21.14.6-1
ii  libdbus-1-3  1.10.6-1
ii  libdbus-glib-1-2 0.106-1
ii  libgdk-pixbuf2.0-0   2.32.3-1.2
ii  libglib2.0-0 2.46.2-3
ii  libgtk-3-0   3.18.7-1
ii  libmm-glib0  1.4.12-1
ii  libnm0   1.1.90-6
ii  libnma0  1.1.90-3
ii  libnotify4   0.7.6-2
ii  libpango-1.0-0   1.38.1-1
ii  libpangocairo-1.0-0  1.38.1-1
ii  libsecret-1-00.18.3-1
ii  mate-polkit [policykit-1-gnome]  1.12.0-1
ii  network-manager  1.1.90-6
ii  policykit-1-gnome0.105-2

Versions of packages network-manager-gnome recommends:
ii  gnome-keyring   3.18.3-1
ii  iso-codes   3.65-1
ii  mate-notification-daemon [notification-daemon]  1.12.1-1
ii  mobile-broadband-provider-info  20140317-1
ii  xfce4-notifyd [notification-daemon] 0.2.4-3+b1

Versions of packages network-manager-gnome suggests:
ii  network-manager-openconnect-gnome  1.0.2-1+b1
pn  network-manager-openvpn-gnome  
pn  network-manager-pptp-gnome 
pn  network-manager-vpnc-gnome 

-- no debconf information

Bug#732615: XInput problem only happens in VirtualBox guest?

[Mike Kupfer]

I'm still seeing this problem where the pencil, text, and highlight
annotations all fail to work when XInput is enabled.  It may have
something to do with VirtualBox.  I see it on 2 VMs, one running Jessie
and one running Stretch, but I don't see it on my baremetal Jessie
system.

I have tried uninstalling the VirtualBox X11 guest additions, but that
didn't seem to help.

When I get some time, I plan to track down some other applications that
use XInput and see if they show similar problems.

regards,
mike

Bug#779892: workaround: disable join dialog

[Mike Kupfer]

I remembered that I could use ldd to find out what libraries hexchat is
linking against.  It's a long list, so I only downloaded debug symbols
for likely-looking packages.  Unfortunately, that didn't give me a
better stack trace.  When I get more time, I'll try additional debug
packages.

I did figure out how to work around the crashes that I'm seeing.  (I
don't know if this helps for the crashes that the original submitter was
seeing.)  In $HOME/.config/hexchat/hexchat.conf, change

gui_join_dialog = 1

  to

gui_join_dialog = 0

regards,
mike

Bug#779892: segv with /server, hexchat 2.10.2-1+b3

[Mike Kupfer]

I am seeing segmentation faults when I use the following line to connect
to my IRC server:

  /server -ssl  6697 

I don't know if this is the same issue that Lauri Alanko provided a
patch for, but I figured I'd start here.

Connecting from the server list window works okay.  But that causes my
password to be saved as plaintext on disk, so I don't think this is a
good workaround.

gdb gives me the following stack trace:

  (gdb) bt
  #0  0x004325c7 in ?? ()
  #1  0x0042bf03 in fe_server_event ()
  #2  0x0046370c in ?? ()
  #3  0x00466358 in inbound_login_end ()
  #4  0x004859b9 in ?? ()
  #5  0x004759b8 in ?? ()
  #6  0x74ce8e8a in g_main_context_dispatch ()
 from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  #7  0x74ce9230 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  #8  0x74ce9552 in g_main_loop_run ()
 from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  #9  0x778c0587 in gtk_main ()
 from /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0
  #10 0x0042a9b9 in fe_main ()
  #11 0x0041efe4 in main ()

I don't know what debug packages to install to get a more meaningful
stack.

https://github.com/hexchat/hexchat/issues/950 has a similar-looking bug,
but unlike that bug, I didn't add any certs, and I don't use a proxy.

This /server command works okay in xchat, but xchat has been removed
from Stretch, so that's not a viable workaround.

This failure happens on both Jessie and Stretch, (both x86_64).

mike

Bug#805191: issue appears to be fixed in sid

[Mike Kupfer]

With

  synaptic  0.82.4
  libgtk-3-03.18.6-1

the scrollbar now appears when it's supposed to.  So I guess this bug
can be closed.  (I can confirm that the problem was still present with
libgtk-3-0 3.18.5-1.)

mike

Bug#805191: libgtk-3-0: scrollbar fails to appear

[Mike Kupfer]

Package: libgtk-3-0
Version: 3.18.4-1
Severity: important

Dear Maintainer,

I upgraded libgtk-3-0 and libgtk-3-common this morning (from 3.18.2-1
to 3.18.4-1).  This changed the scrollbar behavior for the package
list pane in Synaptic.  I verified this in GNOME, Cinnamon, Xfce, and
Mate.

Old behavior: the scrollbar would appear if I moved the mouse into the
package list pane.  (I don't remember if anywhere in the pane worked,
or only if I moved the mouse to the right-hand side of the pane.)

New behavior: I cannot get the scrollbar to appear with just the
mouse.  I can get it to appear by selecting a package and then
pressing the Down key enought times to force the package list to
scroll.  Once the scrollbar appears, I can use it normally, but after
a few seconds of idle time it disappears again.

This is a serious usability regression.

I see the same behavior with Nautilus, though with other apps (GNOME
Terminal, Wireshark), the scrollbar is always visible.

(Can we just get rid of the dynamicall-appearing scrollbar?  It hides
valuable information when it's not visible--there's no visual clue
about how many more packages there are beyond the ones you can see in
the pane.  Also, I recall getting unexpected behavior where I would
click near the bottom of the scrollbar to get a vertical scroll, but a
horizontal scrollbar would appear and I'd get a horizontal scroll
instead.)


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

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

Versions of packages libgtk-3-0 depends on:
ii  libatk-bridge2.0-0  2.18.1-1
ii  libatk1.0-0 2.18.0-1
ii  libc6   2.19-22
ii  libcairo-gobject2   1.14.4-1
ii  libcairo2   1.14.4-1
ii  libcolord2  1.2.12-1
ii  libcups22.1.0-6
ii  libepoxy0   1.3.1-1
ii  libfontconfig1  2.11.0-6.3
ii  libfreetype62.6-2
ii  libgdk-pixbuf2.0-0  2.32.1-1
ii  libglib2.0-02.46.1-2
ii  libgtk-3-common 3.18.4-1
ii  libjson-glib-1.0-0  1.0.4-2
ii  libpango-1.0-0  1.38.1-1
ii  libpangocairo-1.0-0 1.38.1-1
ii  libpangoft2-1.0-0   1.38.1-1
ii  librest-0.7-0   0.7.93-1
ii  libsoup2.4-12.52.1-1
ii  libwayland-client0  1.9.0-1
ii  libwayland-cursor0  1.9.0-1
ii  libwayland-egl1-mesa [libwayland-egl1]  11.0.4-1
ii  libx11-62:1.6.3-1
ii  libxcomposite1  1:0.4.4-1
ii  libxcursor1 1:1.1.14-1+b1
ii  libxdamage1 1:1.1.4-2+b1
ii  libxext62:1.3.3-1
ii  libxfixes3  1:5.0.1-2+b2
ii  libxi6  2:1.7.5-1
ii  libxinerama12:1.1.3-1+b1
ii  libxkbcommon0   0.5.0-1
ii  libxml2 2.9.2+zdfsg1-4
ii  libxrandr2  2:1.5.0-1
ii  shared-mime-info1.5-2

Versions of packages libgtk-3-0 recommends:
ii  libgtk-3-bin  3.18.2-1

Versions of packages libgtk-3-0 suggests:
ii  gvfs 1.26.2-1
ii  librsvg2-common  2.40.11-1

-- no debconf information

Bug#612607: can't ssh over OpenConnect from client running sid

[Mike Kupfer]

I've been seeing an issue that is very similar to what is described in
747098 and 612607, where there's a hang after

  ...
  debug1: kex: server->client aes128-ctr umac...@openssh.com z...@openssh.com
  debug1: kex: client->server aes128-ctr umac...@openssh.com z...@openssh.com
  debug1: sending SSH2_MSG_KEX_ECDH_INIT
  debug1: expecting SSH2_MSG_KEX_ECDH_REPLY

This only happens when connecting through an OpenConnect tunnel; ssh
works fine when I'm not using VPN.

Specifying a cipher didn't help, but lowering the MTU for the VPN tunnel
from 1500 to 1300 fixed things.

# ip li set mtu 1300 dev vpn0

mike

Bug#732615: xournal: default "Use XInput" cause misbehaviours in annotations

[Mike Kupfer]

Hi Carlo,

Carlo Segre wrote:

> With Use XInput checked, this
> seems to work fine on my sid system.

Well, I can try again in a few days.  Maybe there's some fix in unstable
that hasn't propagated to testing yet.

Are you using Xfce?  If you're using a different environment, I'd be
willing to try to reproduce the problem in it.

thanks,
mike


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

Bug#732615: xournal: default "Use XInput" cause misbehaviours in annotations

[Mike Kupfer]

Package: xournal
Version: 1:0.4.8-1
Followup-For: Bug #732615

Dear Maintainer,

If I start Xournal from the Xfce applications menu
(Accessories>Xournal), I get a window that has the standard background
(simulated lined paper).  But none of the pencil, text, or highlight
annotations work *at all*.  That is, the document is marked dirty (I
get a prompt to save the file if I try to close it), but there's no
visual indication that any change has been made.  And if I save the
file and then open it using Xournal in Jessie, all I see is the blank
piece of paper.

If I disable "Use XInput", annotations work again.

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

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

Versions of packages xournal depends on:
ii  ghostscript-x9.06~dfsg-2
ii  libart-2.0-2 2.3.21-2
ii  libatk1.0-0  2.16.0-2
ii  libc62.19-19
ii  libcairo21.14.2-2
ii  libfontconfig1   2.11.0-6.3
ii  libfreetype6 2.5.2-4
ii  libgdk-pixbuf2.0-0   2.31.5-1
ii  libglib2.0-0 2.44.1-1.1
ii  libgnomecanvas2-02.30.3-2
ii  libgtk2.0-0  2.24.28-1
ii  libpango-1.0-0   1.36.8-3
ii  libpangocairo-1.0-0  1.36.8-3
ii  libpangoft2-1.0-01.36.8-3
ii  libpoppler-glib8 0.26.5-2
ii  libx11-6 2:1.6.3-1
ii  zlib1g   1:1.2.8.dfsg-2+b1

xournal recommends no packages.

xournal suggests no packages.

-- no debconf information


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

Bug#786646: sox: play(1) confused about mp3 length, can segv

[Mike Kupfer]

Package: sox
Version: 14.4.1-5
Severity: normal

Dear Maintainer,

I have an MP3 file that I wanted to listen to using play(1).  The file
is approximately 52 minutes long and can be downloaded from
http://audiodharma.org/teacher/22/talk/2815/venue/IMC/20120105-Daniel_Bowling-IMC-mindfulness_conflict_resolution_and_neuroscience_part_1.mp3.

If I start from the very beginning, i.e.,

  play FILE

everything is okay.  If I start a few seconds in, e.g.,

  play FILE trim 0:05

I can listen to the recording, though I get this message:

  play WARN mp3: MAD lost sync

If I start even further in, like 39 minutes into the recording, I get
the same "lost sync" message, and play(1) exits at approximately
39:10.

If I try to start the recording even further in, e.g.,

  play FILE trim 46:00

play(1) dies with a segmentation violation.

syslog message:

  May 23 14:28:34 allegro kernel: [11001.672046] play[6752]: segfault at 0 ip 
7f74fdae0f19 sp 7fffcff0d010 error 4 in 
libmad.so.0.2.1[7f74fdade000+1e000]

I don't know if this is a sox issue or a libmad issue, but I'll note
that

  madplay -s 46:00 FILE

works just fine.

-- System Information:
Debian Release: 8.0
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)

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

Versions of packages sox depends on:
ii  libc6 2.19-18
ii  libgomp1  4.9.2-10
ii  libsox-fmt-alsa   14.4.1-5
ii  libsox-fmt-ao 14.4.1-5
ii  libsox-fmt-base   14.4.1-5
ii  libsox-fmt-oss14.4.1-5
ii  libsox-fmt-pulse  14.4.1-5
ii  libsox2   14.4.1-5

sox recommends no packages.

Versions of packages sox suggests:
ii  libsox-fmt-all  14.4.1-5

-- no debconf information


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

Bug#773151: simply uninstall mh-e

[Mike Kupfer]

Peter S Galbraith wrote:

> Hi all,
> 
> Given that the released MH-E v8.5 doesn't work with nmh 1.6, and that
> MH-E 2 v8.6 is bundled in Emacs-24, I guess it's time for me to remove
> the mh-e package from debian?

Hi Peter, yeah, I've been wondering for awhile if there's still value in
having a separate package for MH-E.  I know I don't really have the time
to help with maintaining it.  And even if I get some cycles, I suspect
there are better ways for me to use that time, like actual MH-E
development.  So I don't object to removing the separate package.

warm regards,
mike


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

Bug#783291: /bin/touch is missing if built with BUSYBOX=n

[Mike Kupfer]

Michael Biebl wrote:

> Am 25.04.2015 um 15:55 schrieb Michael Biebl:
> > Am 25.04.2015 um 14:21 schrieb Michael Biebl:
> >> I can reproduce the missing /bin/touch if I build the initramfs without
> >> busybox support. Can you check your /etc/initramfs-tools/initramfs.conf
> >> if it contains BUSYBOX=n or if you have a snippet in
> >> /etc/initramfs-tools/conf.d/ which sets BUSYBOX=n. Can you confirm, that
> >> the missing /bin/touch is due to BUSYBOX=n?
> > 
> > The alternative is, that you have BUSYBOX=y, but you've uninstalled the
> > busybox package.
> > 
> > Mike, can you confirm that either one of those two is the case?

It's the latter: initramfs.conf has BUSYBOX=y, but busybox is not
installed.  I don't recall uninstalling it, but this VM has a pretty
long history.

regards,
mike


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

Bug#782522: still seeing multiple fsck's of /

[Mike Kupfer]

Michael Biebl wrote:

> Which initramfs-tools version do you have installed?

ii  initramfs-tool 0.120all  generic modular initramfs generat

> Have you made sure,
> your initramfs is update (via update-initramfs).

I did

  # update-initramfs -u -k all
  update-initramfs: Generating /boot/initrd.img-3.16.0-4-amd64

And rebooted.  Still seeing 2 fsck's for / (/dev/sda1).

> If you have initramfs-tools 0.120 installed and active, you should have
> flag files such as /run/initramfs/fsck-root, indicating that the
> initramfs has checked your / filesystem. In that case, systemd will skip
> the check.

$ ls /run/initramfs
fsck.log

(That's after running update-initramfs.)

> If those flag files are missing, either your initramfs-tools version is
> not recent enough, or your initramfs was not updated.

I have an alternate suggestion.  In the thread "boot-time messages,
/init touch not found" on debian-user, The Wanderer suggested that I
unpack the initramfs image and see whether it contains bin/touch.

I did that, and it does not in fact contain anything called "touch".

# find . -name touch
# 

Here's what bin contains:

# ls bin
cat false   insmodlosetup  mknod pivot_root  run-init  udevadm
chroot  fstype  ipconfig  ls   mount poweroffshumount
cpiogunzip  kill  minips   mvreadlinksleep uname
dd  gzipkmod  mkdirnfsmount  reboot  sync
dmesg   haltlnmkfifo   nuke  resume  true

I'm guessing that the lack of bin/touch is preventing this flag file
from being created.

regards,
mike


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

Bug#782522: still seeing multiple fsck's of /

[Mike Kupfer]

Michael Biebl wrote:

> Ok, so sda1 is your /, what is the status of
> $ systemctl status systemd-fsck-root.service

$ systemctl status systemd-fsck-root.service
● systemd-fsck-root.service - File System Check on Root Device
   Loaded: loaded (/lib/systemd/system/systemd-fsck-root.service; static)
   Active: active (exited) since Fri 2015-04-24 08:25:09 PDT; 41s ago
 Docs: man:systemd-fsck-root.service(8)
  Process: 125 ExecStart=/lib/systemd/systemd-fsck (code=exited, 
status=0/SUCCESS)
 Main PID: 125 (code=exited, status=0/SUCCESS)
   CGroup: /system.slice/systemd-fsck-root.service

regards,
mike


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

Bug#782522: still seeing multiple fsck's of /

[Mike Kupfer]

Hi, I have

$ dpkg -l initramfs-tools systemd
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name   Version  Architecture Description
+++-==---=
ii  initramfs-tool 0.120all  generic modular initramfs generat
ii  systemd215-17   amd64system and service manager

but on boot I am still seeing multiple fsck messages for /dev/sda1 (/).

The first fsck appears to be from util-linux.  The second fsck is
systemd-fsck.

The system is a VirtualBox guest (the host is also running Jessie).

Please let me know if there is additional information I should provide.

thanks,
mike


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

Bug#780500: atril: warning message directs user to non-existent URL

[Mike Kupfer]

Package: atril
Version: 1.8.1+dfsg1-3
Severity: normal

Dear Maintainer,

I used atril to view the March/April 2015 PDF issue of IEEE Software.
atril gave me the following warning:

** (atril:22608): WARNING **: Unimplemented annotation: 
POPPLER_ANNOT_SCREEN, please post a bug report in Atril bugzilla 
(http://bugzilla.mate.org) with a testcase.

Unfortunately, that URL does not appear to exist--I get taken to a
domain holding site.  The current web site for Mate is
mate-desktop.org, though I can't seem to find anything to indicate
that there is a bug tracker at the site.

So, what I expect is that if I get a warning asking me to file a bug,
the message should include correct instructions for how to do so.

-- System Information:
Debian Release: 8.0
  APT prefers testing-updates
  APT policy: (500, 'testing-updates'), (500, 'testing')
Architecture: amd64 (x86_64)

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

Versions of packages atril depends on:
ii  atril-common 1.8.1+dfsg1-3
ii  dconf-gsettings-backend [gsettings-backend]  0.22.0-1
ii  libatk1.0-0  2.14.0-1
ii  libatrildocument31.8.1+dfsg1-3
ii  libatrilview31.8.1+dfsg1-3
ii  libc62.19-15
ii  libcairo21.14.0-2.1
ii  libcaja-extension1   1.8.2-2
ii  libfontconfig1   2.11.0-6.3
ii  libfreetype6 2.5.2-3
ii  libgail182.24.25-3
ii  libgdk-pixbuf2.0-0   2.31.1-2+b1
ii  libglib2.0-0 2.42.1-1
ii  libgtk2.0-0  2.24.25-3
ii  libice6  2:1.0.9-1+b1
ii  libpango-1.0-0   1.36.8-3
ii  libpangocairo-1.0-0  1.36.8-3
ii  libpangoft2-1.0-01.36.8-3
ii  libsecret-1-00.18-1+b1
ii  libsm6   2:1.2.2-1+b1
ii  libx11-6 2:1.6.2-3
ii  libxml2  2.9.1+dfsg1-5
ii  mate-desktop-common  1.8.1+dfsg1-2
ii  mate-icon-theme  1.8.0-1
ii  shared-mime-info 1.3-1
ii  zlib1g   1:1.2.8.dfsg-2+b1

Versions of packages atril recommends:
ii  dbus-x11  1.8.16-1
ii  gvfs  1.22.2-1

Versions of packages atril suggests:
pn  caja  
ii  poppler-data  0.4.7-1
pn  unrar 

-- no debconf information


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

Bug#774532: gvfs-backends: syslog messages about index.bdmv when I mount any removable media

[Mike Kupfer]

Package: gvfs-backends
Version: 1.22.2-1
Severity: minor

Dear Maintainer,

If I connect a USB drive, an icon appears for it on my Xfce desktop.
If I mount the drive by right-clicking on the icon, the drive mounts
okay, but some noise appears in /var/log/syslog, e.g.,

  Jan  3 16:53:19 allegro org.gtk.Private.UDisks2VolumeMonitor[1169]: 
index_parse.c:191: indx_parse(): error opening 
/media/kupfer/external/BDMV/index.bdmv
  Jan  3 16:53:19 allegro org.gtk.Private.UDisks2VolumeMonitor[1169]: 
index_parse.c:191: indx_parse(): error opening 
/media/kupfer/external/BDMV/BACKUP/index.bdmv

A web search indicates that these messages have something to do with
Blu-Ray, but I get these messages for non-DVD devices, e.g., a
FAT-formatted thumb drive or a hard disk that is formatted with ext3.

I would prefer not to have this clutter in my syslog, or at least get
rid of the word "error" in the message.  As things stand, these
messages make it harder for me to detect legitimate error messages.

If I mount the device from the shell ("sudo mount ...") I do not get
these error messages.

-- System Information:
Debian Release: 8.0
  APT prefers testing-updates
  APT policy: (500, 'testing-updates'), (500, 'testing')
Architecture: amd64 (x86_64)

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

Versions of packages gvfs-backends depends on:
ii  dconf-gsettings-backend [gsettings-backend]  0.22.0-1
ii  gvfs 1.22.2-1
ii  gvfs-common  1.22.2-1
ii  gvfs-daemons 1.22.2-1
ii  gvfs-libs1.22.2-1
ii  libarchive13 3.1.2-10
ii  libatk1.0-0  2.14.0-1
ii  libavahi-client3 0.6.31-4+b2
ii  libavahi-common3 0.6.31-4+b2
ii  libavahi-glib1   0.6.31-4+b2
ii  libbluetooth35.23-2
ii  libbluray1   1:0.6.2-1
ii  libc62.19-13
ii  libcairo-gobject21.14.0-2.1
ii  libcairo21.14.0-2.1
ii  libcdio-cdda10.83-4.2
ii  libcdio-paranoia10.83-4.2
ii  libcdio130.83-4.2
ii  libdbus-1-3  1.8.12-3
ii  libdbus-glib-1-2 0.102-1
ii  libexif120.6.21-2
ii  libexpat12.1.0-6+b3
ii  libgcrypt20  1.6.2-4+b1
ii  libgdk-pixbuf2.0-0   2.31.1-2+b1
ii  libglib2.0-0 2.42.1-1
ii  libgoa-1.0-0b3.14.2-1
ii  libgphoto2-6 2.5.4-1.1+b2
ii  libgphoto2-port102.5.4-1.1+b2
ii  libgtk-3-0   3.14.5-1
ii  libgudev-1.0-0   215-8
ii  libimobiledevice41.1.6+dfsg-3.1
ii  libmtp9  1.1.8-1+b1
ii  libpango-1.0-0   1.36.8-3
ii  libpangocairo-1.0-0  1.36.8-3
ii  libplist21.11-3
ii  libsecret-1-00.18-1+b1
ii  libsmbclient 2:4.1.13+dfsg-2
ii  libsoup2.4-1 2.48.0-1
ii  libusb-1.0-0 2:1.0.19-1
ii  libxml2  2.9.1+dfsg1-4
ii  psmisc   22.21-2

Versions of packages gvfs-backends recommends:
ii  gnome-keyring  3.14.0-1+b1

Versions of packages gvfs-backends suggests:
pn  obex-data-server  
pn  samba-common  

-- no debconf information


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

Bug#773151: mh-e: draft messages contain raw template text

[Mike Kupfer]

Package: mh-e
Version: 8.5-2
Severity: important

Dear Maintainer,

When I compose a new email with "M-x mh-smail", the draft contains the
template text from /etc/nmh/components.  It should instead contain the
post-processed text.

This issue is fixed in MH-E 8.6.  If it's not feasible to include that
release in Jessie, I can submit the patch that went into MH-E 8.6 to
fix this issue.  Wheezy has this issue, too, so it'd be nice if we
could get this fixed for Jessie.

The workaround, just for the record, is to put the processed
components file in the user's /components file.

-- System Information:
Debian Release: 8.0
  APT prefers testing-updates
  APT policy: (500, 'testing-updates'), (500, 'testing')
Architecture: amd64 (x86_64)

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

Versions of packages mh-e depends on:
ii  dpkg  1.17.21
ii  emacs24   24.4+1-4
ii  install-info  5.2.0.dfsg.1-6
ii  nmh   1.6-2

Versions of packages mh-e recommends:
ii  compface  1:1.5.2-5

Versions of packages mh-e suggests:
pn  imagemagick
pn  mailcrypt  
pn  picon-domains  
pn  swish++
pn  w3m-el 
ii  wget   1.16-1

-- no debconf information


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

Bug#772584: [Pkg-xfce-devel] Bug#772584: xfce4-power-manager: display unlocked after resume

[Mike Kupfer]

Yves-Alexis Perez wrote:

> If you're using the logout dialog, you're actually using xfce4-session,
> which also has a (different from xfpm) setting for locking the screen
> before suspend/sleep. You can check that in the session settings, last
> (Advanced) tab. Can you report back?

Aha!  Yes, the setting was unset in for xfce4-session.  I set it, and
now I get a locked screen when I resume from suspend or hibernation.
Thanks!

> Also, if you want your power manager icon back, you should add the power
> manager plugin to your panel.

Yes, I found the power manager plugin.  But this is for a desktop
system, so the main thing I used the icon for was initiating
suspend/hibernate, and the plugin doesn't provide that functionality.
(Sorry, I worded that part of the bug report badly.)  Thanks anyway.

warm regards,
mike


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

Bug#772584: xfce4-power-manager: display unlocked after resume

[Mike Kupfer]

Package: xfce4-power-manager
Version: 1.4.1-1
Severity: important

Dear Maintainer,

   * What led up to the situation?

I installed Jessie, using a dual-boot configuration (Jessie, Wheezy
(7.7)) with a shared /home.  I then tried testing suspend/resume and
hibernate/resume.  The checkbox (in the power manager preferences) to
lock the screen is selected.

   * What exactly did you do (or not do) that was effective (or
 ineffective)?

I suspended the system from the logout dialog, waited a few seconds,
then pressed a keyboard key to resume.

I hibernated the system from the logout dialog, waited a few seconds,
then pressed the power button to reboot/resume.

   * What was the outcome of this action?

My desktop reappeared.

   * What outcome did you expect instead?

I expected the display to be locked.

I have verified that the screen lock does work if I invoke it manually.

With Wheezy I don't normally use the logout dialog to
suspend/hibernate.  Instead, I invoke suspend/hibernate from the power
manager icon in the systray; when resuming, I get a locked screen.
If I use the logout dialog to suspend/hibernate, I do not get a locked
screen.

But in Jessie there does not appear to be a power manager icon, so the
logout dialog appears to be the only way to suspend/hibernate. 

I marked the severity "important" because of the security implications
and lack of workaround.

This could be the same as 739871, but since I wasn't sure, I thought it
best to file a new bug.

-- System Information:
Debian Release: 8.0
  APT prefers testing-updates
  APT policy: (500, 'testing-updates'), (500, 'testing')
Architecture: amd64 (x86_64)

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

Versions of packages xfce4-power-manager depends on:
ii  libc6 2.19-13
ii  libdbus-1-3   1.8.12-1
ii  libdbus-glib-1-2  0.102-1
ii  libgdk-pixbuf2.0-02.31.1-2+b1
ii  libglib2.0-0  2.42.1-1
ii  libgtk2.0-0   2.24.25-1
ii  libnotify40.7.6-2
ii  libupower-glib3   0.99.1-3.1
ii  libx11-6  2:1.6.2-3
ii  libxext6  2:1.3.3-1
ii  libxfce4ui-1-04.10.0-6
ii  libxfce4util6 4.10.1-2
ii  libxfconf-0-2 4.10.0-3
ii  libxrandr22:1.4.2-1+b1
ii  upower0.99.1-3.1
ii  xfce4-power-manager-data  1.4.1-1

Versions of packages xfce4-power-manager recommends:
ii  libpam-systemd   215-7
ii  xfce4-power-manager-plugins  1.4.1-1

xfce4-power-manager suggests no packages.

-- no debconf information


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

Bug#767443: network-manager: nm-applet left-click menu disappears when button is released

[Mike Kupfer]

Package: network-manager
Version: 0.9.10.0-3
Severity: normal
Tags: upstream

Dear Maintainer,

If I left-click on the nm-applet icon (in the Xfce systray), the menu
only stays up as long as I hold the button down.  As soon as I release
the button, the menu disappears.  If I click-release, I expect the
menu to stay open.

(If I right-click and release, the menu stays open as expected.)

A web search revealed an Arch Linux discussion[1], which refers to a
Fedora bug and workaround patch[2].

[1] https://bbs.archlinux.org/viewtopic.php?pid=1470199
[2] https://bugzilla.redhat.com/show_bug.cgi?id=1149335

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

Kernel: Linux 3.16-3-amd64 (SMP w/1 CPU core)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages network-manager depends on:
ii  adduser3.113+nmu3
ii  dbus   1.8.8-2
ii  init-system-helpers1.21
ii  isc-dhcp-client4.3.1-5
ii  libc6  2.19-12
ii  libdbus-1-31.8.8-2
ii  libdbus-glib-1-2   0.102-1
ii  libgcrypt201.6.2-3
ii  libglib2.0-0   2.42.0-2
ii  libgnutls-deb0-28  3.3.8-3
ii  libgudev-1.0-0 215-5+b1
ii  libmm-glib01.4.0-1
ii  libndp01.4-2
ii  libnewt0.520.52.17-1
ii  libnl-3-2003.2.24-2
ii  libnl-genl-3-200   3.2.24-2
ii  libnl-route-3-200  3.2.24-2
ii  libnm-glib40.9.10.0-3
ii  libnm-util20.9.10.0-3
ii  libpam-systemd 208-8
ii  libpolkit-gobject-1-0  0.105-7
ii  libreadline6   6.3-8
ii  libsoup2.4-1   2.48.0-1
ii  libsystemd0215-5+b1
ii  libteamdctl0   1.12-1
ii  libuuid1   2.25.1-5
ii  lsb-base   4.1+Debian13+nmu1
ii  policykit-10.105-7
ii  udev   208-8
ii  wpasupplicant  2.3-1

Versions of packages network-manager recommends:
pn  crda  
ii  dnsmasq-base  2.72-2
ii  iptables  1.4.21-2
pn  modemmanager  
pn  ppp   

Versions of packages network-manager suggests:
pn  avahi-autoipd  
pn  libteam-utils  

-- no debconf information


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

Bug#740455: xfce4-terminal: crash when detaching multiple tabs

[Mike Kupfer]

Package: xfce4-terminal
Version: 0.6.3-1
Severity: normal

Dear Maintainer,

I can reliably make xfce4-terminal crash by doing the following:

  1. start xfce4-terminal
  2. create 3 additional tabs from the menubar (File>Open Tab)
  3. right-click>Detach Tab on the 2nd-from-the-left tab
  4. right-click>Detach Tab on the (now) middle tab
  5. right-click>Detach on the (now) right-hand tab


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

Kernel: Linux 3.12-1-amd64 (SMP w/1 CPU core)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages xfce4-terminal depends on:
ii  exo-utils   0.10.2-2
ii  libatk1.0-0 2.10.0-2
ii  libc6   2.17-97
ii  libgdk-pixbuf2.0-0  2.30.5-1
ii  libglib2.0-02.38.2-5
ii  libgtk2.0-0 2.24.22-1
ii  libpango-1.0-0  1.36.0-1+b1
ii  libvte9 1:0.28.2-5
ii  libx11-62:1.6.2-1
ii  libxfce4ui-1-0  4.10.0-5
ii  libxfce4util6   4.10.1-1

Versions of packages xfce4-terminal recommends:
ii  dbus-x11  1.8.0-1

xfce4-terminal suggests no packages.

-- no debconf information


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