Bug#1068181: asunder: Additional Information following maintainer response.

2024-04-03 Thread Joshua Aspinall
Package: asunder
Version: 3.0.1+ds-1
Followup-For: Bug #1068181
X-Debbugs-Cc: joshaspin...@member.fsf.org

Dear Maintainer,

Thanks for your response and information.  Please find the steps below I carry 
out to reproduce, noting the update of the repos
before attempting to install.

Please also note that installing grimripper fails in the same manner.

:~$ sudo apt update && sudo apt install asunder
[sudo] password for joshua: 
Hit:1 http://deb.debian.org/debian trixie InRelease
Hit:2 http://security.debian.org/debian-security trixie-security InRelease
Fetched 1,493 B in 0s (5,049 B/s)
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
All packages are up to date.
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following additional packages will be installed:
  cdparanoia flac lame libopusenc0 libopusfile0 opus-tools vorbis-tools wavpack
Suggested packages:
  musepack-tools lame-doc
The following NEW packages will be installed:
  asunder cdparanoia flac lame libopusenc0 libopusfile0 opus-tools vorbis-tools 
wavpack
0 upgraded, 9 newly installed, 0 to remove and 0 not upgraded.
Need to get 112 kB/1,066 kB of archives.
After this operation, 3,357 kB of additional disk space will be used.
Do you want to continue? [Y/n] y
Err:1 http://deb.debian.org/debian trixie/main amd64 wavpack amd64 5.6.0-1+b1
  404  Not Found [IP: 146.75.74.132 80]
E: Failed to fetch 
http://deb.debian.org/debian/pool/main/w/wavpack/wavpack_5.6.0-1%2bb1_amd64.deb 
 404  Not Found [IP: 146.75.74.132 80]
E: Unable to fetch some archives, maybe run apt-get update or try with 
--fix-missing?

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

Kernel: Linux 6.6.15-amd64 (SMP w/32 CPU threads; PREEMPT)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_GB:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages asunder depends on:
pn  cdparanoia   
ii  libatk1.0-0  2.50.0-1+b1
ii  libc62.37-15
ii  libcddb2 1.3.2-7
ii  libgdk-pixbuf-2.0-0  2.42.10+dfsg-3+b1
ii  libglib2.0-0 2.78.4-1
ii  libgtk2.0-0  2.24.33-3

Versions of packages asunder recommends:
pn  flac  
pn  lame  
pn  opus-tools
pn  vorbis-tools  
pn  wavpack   

Versions of packages asunder suggests:
pn  musepack-tools  



Bug#1068239: jq: JSON filters can be fooled by \u0041 or other escapes in object names

2024-04-02 Thread Joshua Hudson
Package: jq
Version: 1.6-2.1
Severity: important

Consider this JSON file:

{
"\u0041PIModule": "/test2.dll",
"APIModule": "/test.dll"
}

On running jq .APIModule < test.json, the output is "/test.dll". The
expected output is "/test2.dll", "/test.dll", or alternately an error
message as this input file is in fact malformed. The order of the two
input lines does not matter: reversing the order in input does not
change the output.

This bug is security class, and was discovered by looking for a solution
to a security problem we uncovered in new development; however this is
not a security bug for everybody. Most people don't try to determine if
JSON input is trustworthy this way.

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

Kernel: Linux 6.1.0-18-amd64 (SMP w/8 CPU threads; PREEMPT)
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 jq depends on:
ii  libc6   2.36-9+deb12u4
ii  libjq1  1.6-2.1

jq recommends no packages.

jq suggests no packages.

-- no debconf information



Bug#1068181: asunder: Asunder package calls wavpack version not present (5.6.0-1+b1). 5.7.0-1 in repo. Cannot install.

2024-04-01 Thread Joshua Aspinall
Package: asunder
Version: 3.0.1+ds-1
Severity: normal
X-Debbugs-Cc: joshaspin...@member.fsf.org

Dear Maintainer,

Cannot install Asunder on testing under normal conditions due to wavpack 
version not present (reports file not found)

Looking through the packages browser can see a newer version (5.7.0-1) than 
that one it tries to grab.  Hopefully a simple fix!

Please contact me if I can help further.

Kind Regards,
Josh.

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

Kernel: Linux 6.6.15-amd64 (SMP w/32 CPU threads; PREEMPT)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_GB:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages asunder depends on:
pn  cdparanoia   
ii  libatk1.0-0  2.50.0-1+b1
ii  libc62.37-15
ii  libcddb2 1.3.2-7
ii  libgdk-pixbuf-2.0-0  2.42.10+dfsg-3+b1
ii  libglib2.0-0 2.78.4-1
ii  libgtk2.0-0  2.24.33-3

Versions of packages asunder recommends:
pn  flac  
pn  lame  
pn  opus-tools
pn  vorbis-tools  
pn  wavpack   

Versions of packages asunder suggests:
pn  musepack-tools  



Bug#1068024: Potential solution to your downgrade problem in dpkg

2024-03-30 Thread Joshua Hudson
The dpkg -> xz-utils downgrade problem has a suggestion that suggests
itself.

1) Downgrade dpkg's dependency to the last known good. It doesn't matter
how old so long as it can read the file formats. I understand this is
likely to be 5.4.1.

2) Statically link all the decompressor libraries into dpkg. Yes this means
gzip, bzip2, zstd, and xz's libraries. Today's compile and link time
optimizers are pretty good; it should be able to drop all references to the
compression side pretty much by itself. This would generally be a pretty
good change of its own as it makes the minimal system easier to understand
and the net-install CD smaller.

Then you're free to do what you need to do for all the other dependencies
of xz-utils.


Bug#1059030: closed by Safir Secerovic (Fixed in version 1.0-1)

2024-03-25 Thread Joshua AE Lee

This still seems to be an issue ion stable

On 3/25/24 08:12, Debian Bug Tracking System wrote:

This is an automatic notification regarding your Bug report
which was filed against the goverlay package:

#1059030: goverlay missing dependency libglu1-mesa

It has been closed by Safir Secerovic .

Their explanation is attached below along with your original report.
If this explanation is unsatisfactory and you have not received a
better one in a separate message then please contact Safir Secerovic 
 by
replying to this email.






Bug#1065754: timidity-daemon: Timidity STILL breaks sound after install by adding itself the the audio group in /etc/group

2024-03-09 Thread Joshua Richards
Package: timidity-daemon
Version: 2.14.0-8.1
Severity: critical
Justification: breaks unrelated software
X-Debbugs-Cc: joshuapricha...@gmail.com

Dear Maintainer,

   * What led up to the situation?
I installed Timidity.  It doesn't break until after a reboot (which may take
weeks for some people).  After I rebooted days later for an unrelated reason, I
lost all audio and PulseAudio no longer showed my sound card at all.
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
Researched online, found a 6 year old bug marked as CLOSED, and impemented the
fix by removing timidity from the
audio:
 line in /etc/group where it was put by timidity-daemon.postinst line 48 as
referenced in reply #58 HERE (ty Kingsley): https://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=901931#58
   * What was the outcome of this action?
After removing timidity from the audio: line in /etc/group and rebooting, aduio
was restored and PulseAudio once again showed my sound card as present.
   * What outcome did you expect instead?
Bug #901931 to not have been marked as resolved and this to have been fixed SIX
YEARS ago.



-- System Information:
Debian Release: 12.5
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 6.6.11-amd64 (SMP w/8 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: sysvinit (via /sbin/init)
LSM: AppArmor: enabled

Versions of packages timidity-daemon depends on:
ii  adduser3.134
ii  lsb-base   11.6
ii  sysvinit-utils [lsb-base]  3.06-4
ii  timidity   2.14.0-8.1

timidity-daemon recommends no packages.

timidity-daemon suggests no packages.

-- no debconf information



Bug#557171: /bin/chvt: accessability issue

2024-03-07 Thread Joshua
Package: kbd
Version: 2.5.1-1+b1
Followup-For: Bug #557171

request tag accessability security important

I am restriced to one hand and forced to enable stickykeys everywhere

It's too difficult to switch consoles with three finget hotkey and sometimes 
impossible.

as emergency action I set suid root on chvt which setting suid on a binary not 
designed for it is a bad idea

-- System Information:
Debian Release: 12.4
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 6.4.12 (SMP w/12 CPU threads; PREEMPT)
Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: unable to detect
LSM: AppArmor: enabled

Versions of packages kbd depends on:
ii  libc6  2.36-9+deb12u4

Versions of packages kbd recommends:
ii  console-data   2:1.12-9
ii  console-setup  1.221

kbd suggests no packages.

-- no debconf information



Bug#1065335: gdebi: Install closes instantly if launched from .deb file dependency but works if GDebi is opened first

2024-03-02 Thread Joshua Richards
Package: gdebi
Version: 0.9.5.7+nmu6
Severity: normal
Tags: patch
X-Debbugs-Cc: joshuapricha...@gmail.com

Dear Maintainer,



   * What led up to the situation?
Opened a .deb file from file manager / browser
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
Edited /usr/share/applications/gdebi.desktop and replaced the line "Exec=gdebi-
gtk %f" with "Exec=gksudo gdebi-gtk %f"
   * What was the outcome of this action?
GDebi now installs the package as expected after prompting for sudo
   * What outcome did you expect instead?
Unsure why GDebi would instantly close instead of displaying an error about
lack of priviledge



-- System Information:
Debian Release: 12.5
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 6.6.11-amd64 (SMP w/8 CPU threads; PREEMPT)
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: sysvinit (via /sbin/init)
LSM: AppArmor: enabled

Versions of packages gdebi depends on:
ii  gdebi-core0.9.5.7+nmu6
ii  gir1.2-gtk-3.03.24.38-2~deb12u1
ii  gir1.2-vte-2.91   0.70.6-2~deb12u1
ii  gnome-icon-theme  3.12.0-5
ii  policykit-1   122-3
ii  python3   3.11.2-1+b1
ii  python3-gi3.42.2-3+b1

Versions of packages gdebi recommends:
pn  libgtk2-perl  
pn  lintian   
ii  shared-mime-info  2.2-1

gdebi suggests no packages.

-- no debconf information



Bug#1063668: linux-image-6.1.0-18-amd64: Nvidia 525.147.05-4 issues

2024-02-10 Thread Joshua Beckwith
Package: linux-image-6.1.0-18-amd64
Version: linux-image-6.1.0-18
Severity: important
X-Debbugs-Cc: joshua.beckwith@gmail.com

Dear Maintainer,

I have noticed some issues pertaining to both packages, namely linux-
image-6.1.0-18-amd64 & linux-headers-6.1.0-18-amd64-common. The repository
Nvidia Driver 525.147.05-4 fails to build the module for this Kernel with exit
code: 10.

I hope this isn't too much of a problem.

Kind regards

Joshua Beckwith



-- System Information:
Debian Release: 12.1
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 6.7.4-1-liquorix-amd64 (SMP w/8 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages linux-image-6.1.0-18-amd64 depends on:
ii  initramfs-tools [linux-initramfs-tool]  0.142
ii  kmod30+20221128-1
ii  linux-base  4.9

Versions of packages linux-image-6.1.0-18-amd64 recommends:
ii  apparmor 3.0.8-3
ii  firmware-linux-free  20200122-1

Versions of packages linux-image-6.1.0-18-amd64 suggests:
pn  debian-kernel-handbook  
ii  grub-efi-amd64  2.06-13+deb12u1
pn  linux-doc-6.1   



Bug#1061404: dpkg read buffer overrun unpacking K (long symbolic) records in data.tar

2024-01-23 Thread Joshua Hudson
On Tue, Jan 23, 2024 at 5:40 PM Guillem Jover  wrote:
>
> Hi!
>
> On Tue, 2024-01-23 at 16:47:34 -0800, Joshua Hudson wrote:
> > On Tue, Jan 23, 2024 at 3:16 PM Guillem Jover  wrote:
> > > On Tue, 2024-01-23 at 13:46:53 -0800, Joshua Hudson wrote:
> > > > Package: dpkg
> > > > Version: 1.21.22
> > > > Severity: important
>
> > > > Source for long link record length does not include trailing null:
> > > >
> > > > https://repo.or.cz/libtar.git/blob/HEAD:/lib/block.c#l294
> > > >
> > > > I've stashed the offending .deb package but I'm not sure if I can
> > > > get clearance to release it.
> > >
> > > Ack. I did not try to reproduce this yet because it was not obvious
> > > exactly how to do that from the report, instead just inspected the
> > > code for potential brokenness related to this, and I think I've fixed
> > > this now, but as I've not tested it, could you instead try applying
> > > the attached patch against dpkg and test with your package whether
> > > this fixes the problem you've found?
> >
> > That patch fixed the bug. Knowing where the bug is, I can see how
> > the bug works and explain why. I'm wondering if this was just a
> > pending disaster for everybody or if there's some actual reason it
> > doesn't trip on official packages.
>
> Thanks for testing! Much appreciated.
>
> It looks like the code in libdpkg has been like that since long GNU
> names and links were implemented (around Oct 1999, in dpkg commit
> <https://git.dpkg.org/cgit/dpkg/dpkg.git/commit/?id=3252594427f5285ab4091a6beca2adaa5082a883>).
>
> Checking now the libdpkg test suite and the GNU tar implementation
> which is what gets used to generate .debs by dpkg-deb, I see it always
> includes the NUL byte as part of the size, which explains why this has
> never been a problem when using the dpkg-deb tooling combined with GNU
> tar.
>
>   <https://git.savannah.gnu.org/cgit/tar.git/tree/src/create.c#n542>
>
> I assume, given the libtar link you provided initially, that your custom
> .deb package is being generated by something using that library? If so
> that would also explain things. I think libtar should probably get a
> bug report to mimic the GNU behavior.

I used a couple of different sample sources to find how Gnu LongLinks work,
and yes libar was one of them. It looks like gnutar itself is the
oddball; everybody
else I found set the size to not include the trailing null. What's
funny is I thought
I had found that gnutar did the same; I guess I just misread the
hexdump of its output.
I guess that's what we all get for lack of an actual specification on it.

Incidentally, gnutar will read either way. Robustness is a good thing.

Here's another generator. Search for WriteAsGnu. Sorry I can't link to line
because of new web accessibility issues on github.

https://raw.githubusercontent.com/dotnet/runtime/d250dcc2deae28fa9726ecad78dddf614b1420a8/src/libraries/System.Formats.Tar/src/System/Formats/Tar/TarHeader.Write.cs

> But regardless of libtar getting fixed or not, I'm still going to be
> committing the change, to make the parser robust against such input.

Much appreciated.

> Thanks,
> Guillem



Bug#1061404: dpkg read buffer overrun unpacking K (long symbolic) records in data.tar

2024-01-23 Thread Joshua Hudson
On Tue, Jan 23, 2024 at 3:16 PM Guillem Jover  wrote:
>
> Hi!
>
> On Tue, 2024-01-23 at 13:46:53 -0800, Joshua Hudson wrote:
> > Package: dpkg
> > Version: 1.21.22
> > Severity: important
>
> > On unpacking a custom .dpkg file with long symbolic links, I found a
> > bunch of symbolic links ending in right, and one with copyright. The
> > overrun made all the links exactly the same length; suggesting reuse
> > of some kind of static buffer, but it's not clear if that's really
> > the case.
> >
> > Making long link records an extra byte longer for the trailing null
> > fixed the overrun and allowed the package to unpack correctly.
>
> Where those long name lengths exactly multiples of 512?

They were not. Must have been a 0 byte in the buffer after copyright.

>
> > Source for long link record length does not include trailing null:
> >
> > https://repo.or.cz/libtar.git/blob/HEAD:/lib/block.c#l294
> >
> > I've stashed the offending .deb package but I'm not sure if I can
> > get clearance to release it.
>
> Ack. I did not try to reproduce this yet because it was not obvious
> exactly how to do that from the report, instead just inspected the
> code for potential brokenness related to this, and I think I've fixed
> this now, but as I've not tested it, could you instead try applying
> the attached patch against dpkg and test with your package whether
> this fixes the problem you've found?

That patch fixed the bug. Knowing where the bug is, I can see how
the bug works and explain why. I'm wondering if this was just a
pending disaster for everybody or if there's some actual reason it
doesn't trip on official packages.



Bug#1061404: dpkg read buffer overrun unpacking K (long symbolic) records in data.tar

2024-01-23 Thread Joshua Hudson
Package: dpkg
Version: 1.21.22
Severity: important

Dear Maintainer,

On unpacking a custom .dpkg file with long symbolic links, I found a
bunch of symbolic links ending in right, and one with copyright. The
overrun made all the links exactly the same length; suggesting reuse
of some kind of static buffer, but it's not clear if that's really
the case.

Making long link records an extra byte longer for the trailing null
fixed the overrun and allowed the package to unpack correctly.

Source for long link record length does not include trailing null:

https://repo.or.cz/libtar.git/blob/HEAD:/lib/block.c#l294

I've stashed the offending .deb package but I'm not sure if I can
get clearance to release it.

This is a potential security vulnerability due to the bug class,
but I can'd find a plausible exploit pathway.

-- Package-specific info:
This system uses merged-usr-via-aliased-dirs, going behind dpkg's
back, breaking its core assumptions. This can cause silent file
overwrites and disappearances, and its general tools misbehavior.
See .

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

Kernel: Linux 6.1.0-16-amd64 (SMP w/8 CPU threads; PREEMPT)
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 dpkg depends on:
ii  libbz2-1.0   1.0.8-5+b1
ii  libc62.36-9+deb12u3
ii  liblzma5 5.4.1-0.2
ii  libmd0   1.0.4-2
ii  libselinux1  3.4-1+b6
ii  libzstd1 1.5.4+dfsg2-5
ii  tar  1.34+dfsg-1.2
ii  zlib1g   1:1.2.13.dfsg-1

dpkg recommends no packages.

Versions of packages dpkg suggests:
ii  apt2.6.1
pn  debsig-verify  

-- no debconf information



Bug#1059030: goverlay missing dependency libglu1-mesa

2023-12-19 Thread Joshua AE Lee

Package: goverlay

Version: 0.9.1-1
Severity: important

Dear Maintainer,

Attempting to open Goverlay to try out the packlage as I'm fairly new to 
trying out mangohud.


After trying to launch it via a graphical application launcher (in this 
case rofi) I got the result of no action.
So as a good linux user I fire up ye old faithful terminal and attempt 
to run goverlay from there netting this response:


joshua@desktop:~$ goverlay
[FORMS.PP] ExceptionOccurred
  Sender=Exception
  Exception=Could not load library: libGLU.so.1
  Stack trace:
  $005F720B
Exception at 005F720B: Exception:
Could not load library: libGLU.so.1.

After a quick apt search libglu I saw that libglu1-mesa was not 
installed and as a curious I just install it and now goverlay launches
fine. Checking both testing and unstable branches I see that it's called 
there as a dependency.


So since this fix was simple can someone add libglu1-mesa as a depency
for this package? I would work on submitting the patch myself but I'll
be honest and say I don't know the first thing about working with a deb
file.

*** End of the template - remove these template lines ***


-- System Information:
Debian Release: 12.4
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 
'stable')

Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 6.5.0-0.deb12.4-amd64 (SMP w/12 CPU threads; PREEMPT)
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 goverlay depends on:
ii  libc6 2.36-9+deb12u3
ii  libgl1    1.6.0-1
ii  libqt5pas1    2.6+2.2.0+dfsg1-3
ii  libx11-6  2:1.8.4-2+deb12u2
ii  mangohud  0.6.8-2
ii  mesa-utils    8.5.0-1
ii  vulkan-tools  1.3.239.0+dfsg1-1

Versions of packages goverlay recommends:
ii  gamescope  3.11.49-1
ii  git    1:2.39.2-1.1
ii  vkbasalt   0.3.2.8-1

goverlay suggests no packages.

-- no debconf information



Bug#1057276: pat: PACTOR mode is broken

2023-12-02 Thread Joshua Hoffmann | DC7IA

Package: pat
Version: 0.15.0-1+b3
Severity: important
X-Debbugs-Cc: martin.h.peder...@gmail.com, d...@dc7ia.eu

Dear Debian Hamradio Maintainers,

connecting to a station using PACTOR is broken. This bug is not present 
when using upstream packages.


```
pat-winlink connect "pactor:///DB0ZAV"
2023/12/02 15:38:18 Connecting to DB0ZAV (pactor)...
2023/12/02 15:38:18 Unable to establish connection to remote: No dialer 
has been registered for this scheme

```

The following incorrect behaviour occurs as well, which might have the 
same reason:


- The web interface does not show any option to select PACTOR
- When selecting an alias in the web interface that uses PACTOR, it gets 
overwritten to ARDOP
- The connect string list that `pat-winlink rmslist` produces only 
contains ` for entries that use PACTOR, example: `DB0ZAV [JO40JF] 
15590 205 Pactor 1,2,3 7.051.00 MHz 7.051.00 MHz `


Using the upstream packages for 0.15.0 and 0.15.1 from GitHub everything 
works as expected.


Best Regards,

Joshua aka DC7IA

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

Kernel: Linux 6.5.0-4-amd64 (SMP w/4 CPU threads; PREEMPT)
Kernel taint flags: TAINT_USER
Locale: LANG=C.UTF-8, LC_CTYPE=C.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 pat depends on:
ii libax25 0.0.12-rc5+git20230513+5581005-1
ii libc6 2.37-12

pat recommends no packages.

Versions of packages pat suggests:
pn ax25-tools 
ii gpsd 3.25-2
ii libhamlib-utils 4.5.5-3
pn tmd710-tncsetup 

-- no debconf information

--
Joshua Hoffmann DC7IA | KK4RVI | M6KIQ

ARRL/VEC accredited Amateur Extra Volunteer Examiner (VE)
Interested in the US amateur radio license? I'll answer your questions. :)

Matrix: @erebion:erebion.eu
Blog: https://blog.dc7ia.eu/

Technische Leitung Matrix-Chat chat.darc.de | Head of the Technical Department 
of the Matrix chat at chat.darc.de

My languages: German, English, Swedish, Norwegian, Danish
Yes, I'm a language nerd. Feel free to write to me in any of the aforementioned 
languages.

PGP-Signed E-Mails, my key:
https://pgp.dc7ia.eu



OpenPGP_0x3F7D2FE0C7150F8C.asc
Description: OpenPGP public key


OpenPGP_signature.asc
Description: OpenPGP digital signature


Bug#1050578:

2023-08-26 Thread Joshua Hudson
Bug verified *upstream* on stock kernel version 6.4.12



Bug#1050578: linux-image-6.1.0-11-amd64: kernel disk device cache coherency issue: stale reads on /dev/sda1

2023-08-26 Thread Joshua
Package: src:linux
Version: 6.1.38-4
Severity: important

Dear Maintainer,

   * What led up to the situation?

Upgrade to bookworm fragmented the EFI paritition (due to changing boot logo) 
and defrag was in order. As this BIOS
currently has broken legacy boot, I used dosbox-x to defrag the EFI partition 
rather than boot the FreeDOS CD-ROM.
Thus this uncovered the bug. On minimizing the bug, it got very simple. I can 
reliably reproduce as follows:

# hexedit /dev/sda
G 10  (your value may vary)
PgDn
PgDn
^C
# hexedit /dev/sda1
PgDn
write a marker to the padding between the BPB and the first FAT sector.
(If your system doesn't have one, edit an error message in the boot sector)
# hexedit /dev/sda1
G 10
PgDn
PgDn
Look for marker written above, find it's not there !!!
^C

For demonstration of the fact the cache is wrong but the data is sved, you can 
do the following:

# reboot
# hexedit /dev/sda
G 1
PgDn
PgDn
Look for marker written above, find it's there !!!

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

Only effective workaround I could find was reboot at certain locations.

   * What outcome did you expect instead?

I seriously expect no possability of block level cache incoherency between
different partition devices on the same block device.
Quite frankly, I am amazed this doesn't cause tons and tons of issues.

-- Package-specific info:
** Version:
Linux version 6.1.0-11-amd64 (debian-ker...@lists.debian.org) (gcc-12 (Debian 
12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40) #1 SMP 
PREEMPT_DYNAMIC Debian 6.1.38-4 (2023-08-08)

** Command line:
BOOT_IMAGE=/vmlinuz-6.1.0-11-amd64 root=/dev/mapper/NOVA-lvol2 ro video=960x540 
net.ifnames=0 biosdevname=0 quiet

(Note that I'm working on the EFI parititon, which is not inside LVM due to 
incompatibilities.)

** Not tainted

** Kernel log:

There is nothing useful in the log. The last log entry is before reproducing 
the issue.

** Model information
sys_vendor: Micro-Star International Co., Ltd.
product_name: MS-7C56
product_version: 2.0
chassis_vendor: Micro-Star International Co., Ltd.
chassis_version: 2.0
bios_vendor: American Megatrends International, LLC.
bios_version: A.C0
board_vendor: Micro-Star International Co., Ltd.
board_name: B550-A PRO (MS-7C56)
board_version: 2.0

** Loaded modules:
8021q
garp
stp
mrp
llc
bnep
bluetooth
jitterentropy_rng
drbg
ansi_cprng
ecdh_generic
rfkill
ecc
binfmt_misc
uinput
fuse
nft_chain_nat
xt_MASQUERADE
nf_nat
nf_conntrack
nf_defrag_ipv6
nf_defrag_ipv4
nft_compat
x_tables
nf_tables
nfnetlink
nls_ascii
nls_cp437
vfat
fat
dm_crypt
amdgpu
snd_hda_codec_realtek
snd_hda_codec_generic
ledtrig_audio
intel_rapl_msr
intel_rapl_common
snd_hda_codec_hdmi
edac_mce_amd
gpu_sched
snd_hda_intel
drm_buddy
snd_intel_dspcfg
snd_intel_sdw_acpi
drm_display_helper
kvm_amd
snd_hda_codec
cec
snd_hda_core
joydev
rc_core
snd_hwdep
drm_ttm_helper
kvm
ttm
snd_pcm_oss
irqbypass
drm_kms_helper
snd_mixer_oss
rapl
snd_pcm
drm
snd_timer
k10temp
evdev
wmi_bmof
sp5100_tco
efi_pstore
snd
ccp
sg
i2c_algo_bit
soundcore
watchdog
rng_core
acpi_cpufreq
button
efivarfs
ext4
crc16
mbcache
jbd2
dm_mirror
dm_region_hash
dm_log
raid1
dm_raid
raid456
async_raid6_recov
async_memcpy
async_pq
async_xor
async_tx
md_mod
xor
raid6_pq
libcrc32c
crc32c_generic
dm_mod
hid_generic
crc32_pclmul
crc32c_intel
sd_mod
t10_pi
usbhid
crc64_rocksoft_generic
hid
crc64_rocksoft
crc_t10dif
ghash_clmulni_intel
crct10dif_generic
sr_mod
crct10dif_pclmul
crc64
cdrom
sha512_ssse3
crct10dif_common
sha512_generic
ahci
xhci_pci
libahci
xhci_hcd
libata
r8169
aesni_intel
realtek
usbcore
mdio_devres
scsi_mod
crypto_simd
libphy
cryptd
i2c_piix4
video
usb_common
scsi_common
wmi
gpio_amdpt
gpio_generic

** PCI devices:
00:00.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Renoir/Cezanne 
Root Complex [1022:1630]
Subsystem: Micro-Star International Co., Ltd. [MSI] Renoir/Cezanne Root 
Complex [1462:7c56]
Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- 

00:01.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Renoir PCIe 
Dummy Host Bridge [1022:1632]
Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities: 
Kernel driver in use: pcieport

00:08.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Renoir PCIe 
Dummy Host Bridge [1022:1632]
Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- TAbort- Reset- FastB2B-

Bug#1050483:

2023-08-25 Thread Joshua Hudson
Trying on sid (2023-08-25) objdump fails with: "./mv: file format not
recognized" and readelf still works.

objdump version from sid: GNU objdump (GNU Binutils for Debian) 2.41



Bug#1050483: /usr/bin/x86_64-linux-gnu-objdump: objdump and nm choke on fully stripped ELF executables

2023-08-24 Thread Joshua
Package: binutils-x86-64-linux-gnu
Version: 2.35.2-2
Severity: normal
File: /usr/bin/x86_64-linux-gnu-nm

Dear Maintainer,

   * What led up to the situation?

Originally, trying to figure out why these programs would not load. Ultimately,
discovering that nm (my normal go-to tool) and objdump could not handle these.
I'm not exactly sure what the problem is, but it appears to be the tools cannot
handle binaries that have less than two sections.

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

After discovering that readelf could cope with the problem I was able to repair
the binary headers; however even so, objdump and nm cannot cope.

   * What outcome did you expect instead?

A more sane error message than a section that doesn't exist has an offset 
outside
the file repeated twice.

Diagnostic output:

$ objdump --all ./mv
objdump: warning: ./mv has a corrupt section with a size (7ba002000) larger 
than the file size
objdump: warning: ./mv has a corrupt section with a size (7ba002000) larger 
than the file size
objdump: ./mv: file format not recognized
$ readelf --all ./mv
ELF Header:
  Magic:   7f 45 4c 46 02 01 01 03 00 00 00 00 00 00 00 00 
  Class: ELF64
  Data:  2's complement, little endian
  Version:   1 (current)
  OS/ABI:UNIX - GNU
  ABI Version:   0
  Type:  EXEC (Executable file)
  Machine:   Advanced Micro Devices X86-64
  Version:   0x1
  Entry point address:   0x200078
  Start of program headers:  64 (bytes into file)
  Start of section headers:  120 (bytes into file)
  Flags: 0x0
  Size of this header:   64 (bytes)
  Size of program headers:   56 (bytes)
  Number of program headers: 1
  Size of section headers:   0 (bytes)
  Number of section headers: 0
  Section header string table index: 0
readelf: Warning: possibly corrupt ELF file header - it has a non-zero section 
header offset, but no section headers

There are no sections to group in this file.

Program Headers:
  Type   Offset VirtAddr   PhysAddr
 FileSizMemSiz  Flags  Align
  LOAD   0x 0x0020 0x
 0x00ee 0x00ee  R E0x1000

There is no dynamic section in this file.
$

Here are three binaries with which to reproduce the problem:

begin-base64 755 chmod
f0VMRgIBAQMAAAIAPgABeAAgAABAAHgA
AEAAOAABAAEFACAA
DQENAQAQWEiD+AN1S15eMckxwKw8
AHQPLDByPDwIczjB4QMJwevsic5fuFoPBffYdBtQvwIAAABIjTQlBgEg
ALoHuAEPBViXuDwPBb8CSI00Je8AIAC6FwAAALgB
DwW/DgAAALg8DwVVc2FnZTogY2htb2Qgbm5ubiBmaWxlCkVycm9yIQo=


begin-base64 755 mv
f0VMRgIBAQMAAAIAPgABeAAgAABAAHgA
AEAAOAABAAEFACAA
7gDuAAAQWEiD+AN1MV9fXrhS
DwX32HQbUL8CSI00JecAIAC6BwAAALgBDwVYl7g8DwW/AgAA
AEiNNCXVACAAuhIAAAC4AQ8Fvw4AAAC4PA8FVXNhZ2U6IG12IHNy
YyBkc3QKRXJyb3IhCg==


begin-base64 755 sln
f0VMRgIBAQMAAAIAPgABeAAgAABAAHgA
AEAAOAABAAEFACAA
7wDvAAAQWEiD+AN1MV9fXrhY
DwX32HQbUL8CSI00JegAIAC6BwAAALgBDwVYl7g8DwW/AgAA
AEiNNCXVACAAuhMAAAC4AQ8Fvw4AAAC4PA8FVXNhZ2U6IHNsbiBz
cmMgZHN0CkVycm9yIQo=


-- System Information:
Debian Release: 11.6
  APT prefers oldstable-updates
  APT policy: (500, 'oldstable-updates'), (500, 'oldstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.10.0-20-amd64 (SMP w/12 CPU threads)
Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: unable to detect
LSM: AppArmor: enabled

Versions of packages binutils-x86-64-linux-gnu depends on:
ii  binutils-common  2.35.2-2
ii  libbinutils  2.35.2-2
ii  libc62.31-13+deb11u5
ii  libctf-nobfd02.35.2-2
ii  libctf0  2.35.2-2
ii  libgcc-s110.2.1-6
ii  libstdc++6   10.2.1-6
ii  zlib1g   1:1.2.11.dfsg-2+deb11u2

binutils-x86-64-linux-gnu recommends no packages.

Versions of packages binutils-x86-64-linux-gnu suggests:
pn  binutils-doc  

-- no debconf information



Bug#1043406: Package: libnvidia-egl-wayland1

2023-08-10 Thread Murphy Joshua
Package: libnvidia-egl-wayland1
Source: egl-wayland
Version: 1:1.1.10-1
Architecture: amd64
Maintainer: Ubuntu Developers 
Original-Maintainer: Timo Aaltonen 


Hi!

I'm writing to you in a hope to draw attention to the recent updates to the 
""libnvidia-egl-wayland1" package upstream at 
https://github.com/NVIDIA/egl-wayland.

[https://opengraph.githubassets.com/d1c9b719f8b7e9ea82d70f1b5027500b373b63cb6f9e835ceedbbeb5e52b1cbd/NVIDIA/egl-wayland]
GitHub - NVIDIA/egl-wayland: The EGLStream-based Wayland external 
platform
The EGLStream-based Wayland external platform. Contribute to NVIDIA/egl-wayland 
development by creating an account on GitHub.
github.com


If libnvidia-egl-wayland1 is an essential package for (nVidia Users) kDE - 
Ubuntu / Debian based Distro's can we please get it updated to the latest 
version: 1.1.12

https://github.com/NVIDIA/egl-wayland
version: 1.1.12
- Added support for version 4 of the Linux DMA-BUF protocol
- Added support for EGL_EXT_explicit_device extension
- Fixed incomplete window resizing regression from 1.1.10
- Fixed eglSwapInterval when using DMA-BUF path

The libnvidia-egl-wayland1 package was last updated in the Ubuntu / Debian 
2021/ 2022 but has none of the above fixes.


Why is libnvidia-egl-wayland1 and essential package?

Because in currently in Plasma Wayland session, if this lib is not installed, 
then LLVMPIPE is used instead of the nVidia Driver (all releases).


Timo Aaltonen is the original maintainer for ubuntu.

Timo Aaltonen is also the maintainer for the package in Debian which is also 
outdated.


I use kDE_NEON. your bug tracker was a bit beyond me at the moment.


I do appreciate how incredibly busy everyone is.

Thankyou

https://www.phoronix.com/news/Mesa-23.3-EGL-Explicit-Device
https://wayland.app/protocols/linux-dmabuf-unstable-v1
https://registry.khronos.org/EGL/sdk/docs/man/html/eglSwapInterval.xhtml



Bug#1037539: multipath-tools: the /lib/udev/rules.d/60-multipath.rules file is missing

2023-06-13 Thread Joshua Huber
Package: multipath-tools
Version: 0.9.4-3
Severity: important
Tags: patch

Dear Maintainer,

Since verison 0.9.4-1, the multipath.rules udev file is no longer included in
the Debian package. Upstream changed from shipping a static file to a
file generated at build time (multipath.rules.in), and the debian packaging
didn't account for this change. I've come up with something that works, but
it might not be the best/correct solution according to packaging policy
and such.

The missing rules file results in missing udev device properties, such as
DM_MULTIPATH_DEVICE_PATH. This, at the very least, has the effect of:

1) Not skipping LVM device scanning on multipath path devices, which could
   result in a failure to bring up a multipath device. (or worse --
   I wouldn't be surprised if concurrently operating on a dm-multipath device
   and one or more of its child devices could cause data loss, if unlucky.)

2) Not removing partition table entries for multipath child devices.
   (the del-part-nodes rules apply if DM_MULTIPATH_DEVICE_PATH is set.)

If you need any more information, happy to provide it!

-- Package-specific info:
/etc/multipath.conf does not exist.


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

Kernel: Linux 6.1.0-9-amd64 (SMP w/2 CPU threads; PREEMPT)
Locale: LANG=C.UTF-8, LC_CTYPE=C.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 multipath-tools depends on:
ii  init-system-helpers1.65.2
ii  kpartx 0.9.4-3
ii  libaio10.3.113-4
ii  libc6  2.36-9
ii  libdevmapper1.02.1 2:1.02.185-2
ii  libedit2   3.1-20221030-2
ii  libjson-c5 0.16-2
ii  libsystemd0252.6-1
ii  libudev1   252.6-1
ii  liburcu8   0.13.2-1
ii  sg3-utils-udev 1.46-3
ii  sysvinit-utils [lsb-base]  3.06-4
ii  udev   252.6-1

multipath-tools recommends no packages.

Versions of packages multipath-tools suggests:
pn  multipath-tools-boot  

-- no debconf information

*** fix-missing-multipath-udev-rules.patch
commit 81d3e7e0a23bf7b384accd65d85070008ac7142a (HEAD -> master)
Author: Joshua Huber 
Date:   Tue Jun 13 14:15:30 2023 -0400

account for upstream multipath.rules changing to a generated file

diff --git a/debian/rules b/debian/rules
index 28839b67..e56419ae 100755
--- a/debian/rules
+++ b/debian/rules
@@ -47,9 +47,10 @@ override_dh_auto_install:
[ ! -f kpartx/del-part-nodes.rules ] || cp kpartx/del-part-nodes.rules 
debian/kpartx.del-part-nodes.udev
[ ! -f kpartx/dm-parts.rules ] || cp kpartx/dm-parts.rules 
debian/kpartx.dm-parts.udev
[ ! -f kpartx/kpartx.rules ] || cp kpartx/kpartx.rules 
debian/kpartx.udev
-   [ ! -f multipath/multipath.rules ] || cp multipath/multipath.rules 
debian/multipath.udev
[ ! -f multipath/11-dm-mpath.rules ] || cp multipath/11-dm-mpath.rules 
debian/dm-mpath.udev

+   cp -v debian/build-deb/multipath/multipath.rules 
debian/multipath-tools.multipath.udev
+
dh_auto_install --sourcedirectory=debian/build-deb -- 
DESTDIR=$(CURDIR)/debian/tmp
dh_auto_install --sourcedirectory=debian/build-udeb -- 
DESTDIR=$(CURDIR)/debian/tmp-multipath-udeb



Bug#1037516: ircd-hybrid hates winbindd users

2023-06-13 Thread Joshua Hudson
Package: ircd-hybrid
Version: 1:8.2.43+dfsg.1-1
Severity: important
Tags: newcomer upstream

Dear Maintainer,

When connecting to ircd-hybrid on localhost, users from a Windows domain get 
kicked out with invalid user.

I tracked this down to the source code; ircd-hybrid believes that \ is an 
invalid character in username
while ident reports the full username including the \ character in the middle.

Problem exists upstream.

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

Kernel: Linux 6.1.0-9-amd64 (SMP w/8 CPU threads; PREEMPT)
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 ircd-hybrid depends on:
ii  debconf [debconf-2.0]  1.5.82
ii  libc6  2.36-9
ii  libcrypt1  1:4.4.33-2
ii  libgnutls303.7.9-2
ii  libltdl7   2.4.7-5
ii  lsb-base   11.6
ii  openssl3.0.9-1
ii  sysvinit-utils [lsb-base]  3.06-4

Versions of packages ircd-hybrid recommends:
ii  whois  5.5.17

Versions of packages ircd-hybrid suggests:
pn  anope  

-- Configuration Files:
/etc/ircd-hybrid/cert.cnf [Errno 13] Permission denied: 
'/etc/ircd-hybrid/cert.cnf'
/etc/ircd-hybrid/ircd.conf [Errno 13] Permission denied: 
'/etc/ircd-hybrid/ircd.conf'
/etc/ircd-hybrid/ircd.motd [Errno 13] Permission denied: 
'/etc/ircd-hybrid/ircd.motd'

-- debconf information:
  ircd-hybrid/upgrade_secure_links_warn: true
  ircd-hybrid/automatically_fix_config: false
  ircd-hybrid/restart_on_upgrade: true



Bug#1036773: cloud.debian.org: During vagrant up, mounting NFS fails

2023-05-25 Thread Joshua Kugler
Package: cloud.debian.org
Severity: important

Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation?
I tried to use the debian/testing64 vagrant box.

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

I ran `vagrant up`. It mostly runs, but hangs on ==> default: Mounting 
NFS shared folders...
After sitting there 

   * What was the outcome of this action?

It mostly runs, but hangs on ==> default: Mounting NFS shared folders...
After sitting there for a while, it fails with:

The following SSH command responded with a non-zero exit status.
Vagrant assumes that this means the command failed!

mount -o vers=4 192.168.121.1:/home/jkugler/vmware/vagrant_debian 
/vagrant

Stdout from the command:


Stderr from the command:

mount.nfs: Connection refused


   * What outcome did you expect instead?

I expected the machine to come up without issue.

I noticed in the default Vagrantfile that comes with the box, there is 
an NFS shared folder.
That should probably be removed and allow the user to configure shared 
folders as they see fit.



Bug#1011594: Re: kotlin-mode needs a source-only upload for testing migration

2023-02-04 Thread Joshua Peisach
Hi Nicholas, I'm sorry for bunting. I really should be working with the emacsen 
team and using other examples. For this, I have created a branch called 
'1011594-fixes' which aims to solve these problems.

Before reading, just want to say that you aren't being harsh. You're giving the 
'deeply concerned and worried' attitude, not the 'how dare you' mood. You went 
into a lot of depth with the problems, and you are looking out for me. For what 
I am doing, it is sensible for me to do the work, so this is a good "pause and 
think" moment. I greatly appreciate it, no matter how deep of a hole I may be 
digging for myself. :)


  1.
Changelog for 'upstream release' - Using ggtags as an example, I'm setting that 
to "Update to new upstream commit" - 
https://salsa.debian.org/emacsen-team/ggtags/-/blob/master/debian/changelog
  2.  The patch. I had to fresh the patch. Honestly, I took the lazy route 
since I did not do this in a while and just.. created a new one and put your 
name down as the 'first' author to show you did it first.
 *   First: In terms of a FOSS project, what I did was tremendously dumb. I 
should've thought about what I was doing but I didn't. I was focused on getting 
the thing done by just doing what was needed to get dpkg-source and quilt apply 
the patch happily. and next time I need to think logistically about how to 
handle this.
 *   The wording I did was taken from you, for the 'Declare correct MELPA 
version'. The text in the patch is taken directly from the file. If it helps 
you understand what I did, I created an entirely new patch. I did the quilt 
new, quilt add, (edit-file-command), quilt refresh, quilt header -e --dep3, 
quilt pop.
 *   My current step process: I have reverted the commit (git revert. I 
rarely revert commits, and I try to avoid force pushing unless I'm tremendously 
lost). I am running back to Chapter 8 of the maintenance guide, setup dquilt 
and am following the updating patch part of section 8.3, under the conflict 
part with the new upstream source. I edit kotlin-mode.el file, ran dquilt push 
and refresh, going back to 8.1 for changelog. Using projectile's changelog as 
an example, and I'm saying "Refresh patch 0001 (update source version)"
  3.  Standards Version - I always use the updating checklist! It's the most 
helpful tool. Ran through both 4.6.1 and 4.6.2. I took your suggestion for 
"Declare compliance with.." though I've always used "Update Std-Ver". For a 
second changelog point, I should've put that in but I did not. For reasoning, I 
will say that the file says required emacs 24.3 and buster has 
1:26.1+1-3.2+deb10u3. Plus, for bookworm the current emacs version is 
1:28.2+1-10. Users keeping their system up-to-date meet the constraint.
  4.  Copyright years - I am a bit embarrased to say I had no idea Threshold of 
Originality is a thing. Looking at other examples, best thing to do is leave 
it. Unfortunately I cannot quite meet the 'one-time history change' as I have 
already used it on the patch, but I can offer you a commit that just takes off 
the -2023 with an explanation. Not every file has changed, and it seems there 
are different rules of threshold of originality per country. I am in the US 
personally, and I think I meet the "small value" but I don't feel like risking 
it.

I have just updated the changelog, made commits, the tests passed, ran lintian 
and fixed the changelog line being too long, updated changelog time again, 
committed and pushed.

If possible, can you review the branch?

Thanks again for checking everything out, and I am so sorry for all the 
problems created.

-Josh



From: Nicholas D Steeves
Sent: Monday, January 30, 2023 10:48 PM
To: Joshua Peisach; 1011...@bugs.debian.org
Subject: Re: Bug#1011594: Re: kotlin-mode needs a source-only upload for 
testing migration

Hi Josh,

Thank you for the quick reply, and for updating the maintainer :) I've
tried to write an email that will help you understand the issues with as
quickly as possible, since the final deadline is days away. 'hope it's
not too long or harsh 

As you know, Debian has high standards, and you may remember some of this
from our first review.  When you didn't follow up, I fixed the remaining
issues myself (see 30eb8be to faef886); This time around, please resolve
the issues noted below yourself, before the 5th of February.

If you're short on time and want to take the fastest path, skip to the
paragraph that starts with "If you want".

Upstream has not made a release, so the first changelog point is wrong.
What is really being packaged?

d51515f * Refresh and update patches
  - I would write the following no matter who the original author of the
  patch was: This looks like an attempt to take credit for someone
  else's work by making some some changes that aren't significant for
  the purposes of copyright; this sort of thing w

Bug#1011594: Re: kotlin-mode needs a source-only upload for testing migration

2023-01-29 Thread Joshua Peisach
Hi,

Review on the repo here on this bug is okay! I am sending this to the bug 
email, and I've also updated the maintainer.

Thanks
-Josh

From: Nicholas D Steeves 
Sent: Friday, January 27, 2023 2:59 AM
To: Joshua Peisach ; 1011...@bugs.debian.org 
<1011...@bugs.debian.org>
Cc: Adrian Bunk ; Hans-Christoph Steiner 
Subject: Re: Bug#1011594: Re: kotlin-mode needs a source-only upload for 
testing migration

Hi Josh,

Joshua Peisach  writes:

> Hi Nicholas,
>
> I have imported the latest upstream snapshot into Salsa :)
>

Thank you!

I've reviewed the new commits, and the current state of the git repo is
not yet ready to sponsor.  Would you like the review to occur at this
(#1011594 "Please package new upstream snapshot") bug, at a
yet-to-be-filed RFS bug, or on the Emacsen Team or Debian mentors
mailing list?  Debian is developed in the open, so private mail isn't an
option.

Alternatively, if you'd like to learn or practise "Git Feature Branch
Workflow" [1], then I'm happy to review that way too.

IMPORTANT: We're in the "Freeze"[2] so deadlines are in effect.  This
work has to be completed before the end of next week.

Cheers,
Nicholas

[1] 
https://www.atlassian.com/git/tutorials/comparing-workflows/feature-branch-workflow
[2] https://release.debian.org/bullseye/freeze_policy.html

P.S.  Also, I'm still waiting for you to make the following change:

diff --git a/debian/control b/debian/control
index 6576d4e..8ae5a20 100644
--- a/debian/control
+++ b/debian/control
@@ -1,7 +1,8 @@
 Source: kotlin-mode
 Section: editors
 Priority: optional
-Maintainer: Joshua Peisach 
+Maintainer: Debian Emacsen team 
+Uploaders: Joshua Peisach 
 Build-Depends: debhelper-compat (= 13),
  dh-elpa
 Standards-Version: 4.6.2


Bug#1011594: (thread)

2023-01-25 Thread Joshua Peisach
Hi Nicholas,

I have imported the latest upstream snapshot into Salsa :)

-Josh



Bug#1029167: mozjs78: Fails to build on armhf and armel

2023-01-18 Thread Joshua Peisach
CJS ported to mozjs78 in October 2020, and Cinnamon is still finishing their 
5.6x releases/making cleanups.

Considering upstream uses Ubuntu Jammy, mozjs102 isn’t an option unless they 
are willing to build it for their main development target. I think Cjs should 
rebase for mozjs91,
Especially if mozjs78 is EOL.

> On Jan 18, 2023, at 1:59 PM, Jeremy Bicha  wrote:
> 
> Source: mozjs78
> Version: 78.15.0-6
> Severity: serious
> Tags: ftbfs
> Justification: fails to build from source (but built successfully in the past)
> X-Debbugs-Cc: debian-...@lists.debian.org, c...@packages.debian.org
> User: debian-...@lists.debian.org
> Usertags: armel armhf
> 
> mozjs78 fails to build on armhf & armel.
> 
> I have little interest in working on this bug myself. I only stumbled
> across this bug because I applied a build fix needed by Debian's
> switch to Python 3.11. mozjs78 has been End of Life since October 2021
> and is only still in Debian because Cinnamon hasn't switched to
> mozjs102 yet.
> 
> By the way, 0ad has an embedded copy of mozjs78 and still builds on
> armhf so maybe it includes a fix or a workaround for this build
> failure.
> 
> I'm pasting the end of the build log below, but the actual build error
> may have been earlier in the log.
> 
> /usr/bin/arm-linux-gnueabihf-g++ -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=2
> -fstack-protector-strong -Wdate-time -D_FORTIFY_SOURCE=2 -Wall
> -Wempty-body -Wignored-qualifiers -Woverloaded-virtual -Wpointer-arith
> -Wsign-compare -Wtype-limits -Wunreachable-code -Wwrite-strings
> -Wno-invalid-offsetof -Wc++2a-compat -Wduplicated-cond
> -Wimplicit-fallthrough -Wunused-function -Wunused-variable
> -Wno-error=maybe-uninitialized -Wno-error=deprecated-declarations
> -Wno-error=array-bounds -Wno-error=coverage-mismatch
> -Wno-error=free-nonheap-object -Wno-multistatement-macros
> -Wno-error=class-memaccess -Wno-error=deprecated-copy -Wformat
> -Wformat-overflow=2 -Wno-noexcept-type -fno-sized-deallocation
> -fno-aligned-new -g -O2 -ffile-prefix-map=/<>=.
> -fstack-protector-strong -Wformat -Werror=format-security -fno-rtti
> -ffunction-sections -fdata-sections -fno-exceptions -fno-math-errno
> -pthread -pipe -g -freorder-blocks -O3 -fomit-frame-pointer
> -funwind-tables  -fPIC -shared -Wl,-z,defs -Wl,--gc-sections
> -Wl,-h,libmozjs-78.so -o libmozjs-78.so
> /<>/debian/build/js/src/build/libmozjs-78_so.list
> -lpthread -Wl,-z,relro -Wl,-z,noexecstack -Wl,-z,text -Wl,-z,relro
> -Wl,-z,nocopyreloc -Wl,-Bsymbolic-functions -Wl,--build-id=sha1
> -fstack-protector-strong
> -Wl,-rpath-link,/<>/debian/build/dist/bin
> -Wl,-rpath-link,/usr/lib
> /<>/debian/build/armv7-unknown-linux-gnueabihf/release/libjsrust.a
> -Wl,--version-script,symverscript -Wl,-soname,libmozjs-78.so.0  -lm
> -lz -lm -ldl
> /usr/bin/ld: 
> /<>/debian/build/js/src/build/../../../config/external/icu/common/rbbi.o:
> in function `std::type_info::operator!=(std::type_info const&) const':
> /usr/include/c++/12/typeinfo:115: undefined reference to
> `std::type_info::operator==(std::type_info const&) const'
> /usr/bin/ld: 
> /<>/debian/build/js/src/build/../../../config/external/icu/common/schriter.o:
> in function `std::type_info::operator!=(std::type_info const&) const':
> /usr/include/c++/12/typeinfo:115: undefined reference to
> `std::type_info::operator==(std::type_info const&) const'
> /usr/bin/ld: 
> /<>/debian/build/js/src/build/../../../config/external/icu/common/stringtriebuilder.o:
> in function 
> `icu_67::StringTrieBuilder::Node::operator==(icu_67::StringTrieBuilder::Node
> const&) const':
> ./debian/build/config/external/icu/common/./intl/icu/source/common/stringtriebuilder.cpp:388:
> undefined reference to `std::type_info::operator==(std::type_info
> const&) const'
> /usr/bin/ld: 
> ./debian/build/config/external/icu/common/./intl/icu/source/common/stringtriebuilder.cpp:388:
> undefined reference to `std::type_info::operator==(std::type_info
> const&) const'
> /usr/bin/ld: 
> ./debian/build/config/external/icu/common/./intl/icu/source/common/stringtriebuilder.cpp:388:
> undefined reference to `std::type_info::operator==(std::type_info
> const&) const'
> /usr/bin/ld: 
> /<>/debian/build/js/src/build/../../../config/external/icu/common/stringtriebuilder.o:./debian/build/config/external/icu/common/./intl/icu/source/common/stringtriebuilder.cpp:388:
> more undefined references to
> `std::type_info::operator==(std::type_info const&) const' follow
> collect2: error: ld returned 1 exit status
> make[4]: *** [/<>/config/rules.mk:608: libmozjs-78.so] Error 1
> make[4]: Leaving directory '/<>/debian/build/js/src/build'
> make[3]: *** [/<>/config/recurse.mk:74:
> js/src/build/target] Error 2
> make[3]: Leaving directory '/<>/debian/build'
> make[2]: *** [/<>/config/recurse.mk:34: compile] Error 2
> make[2]: Leaving directory '/<>/debian/build'
> make[1]: *** [/<>/config/rules.mk:392: default] Error 2
> make[1]: Leaving directory '/<>/debian/build'
> dh_auto_build: error: cd debian/build && make -j8 returned 

Bug#987503: swap partition only 1 GB instead of at least 1 x RAM size

2022-12-29 Thread Joshua McNeil
On Thu, 8 Dec 2022 13:05:48 +0100 Bastian Blank  wrote:
>
> The current default is suitable.  Hibernation does not work on any
> modern x86 machine and you don't want to have huge swap on desktop
> machines as it only adds latency.
>
> Bastian
>

I recently ran into this issue while considering Debian for desktop and
laptop usage and would also like to request increasing the swap default to
at least the size of RAM.

Hibernation works just fine on all of my modern x86_64 machines when the
swap space is sufficient. Could you elaborate on why you believe it doesn't?

If the primary objective was reducing memory latency I would suggest
instead modifying the default vm.swappiness which would actually affect how
often swap is used. I agree that in many cases swap causes degraded
performance for modern systems. However, hibernation is a good use for it.

In my experience when hibernation fails Debian appears less battery
efficient on laptops due to the need to retain power to memory when the lid
is closed. Ensuring the default  swap size is sufficient to support
hibernation helps improve this experience.


Bug#1022347: cppimport: FTBFS: dpkg-source: error: aborting due to unexpected upstream changes, see /tmp/cppimport_22.08.02-1.diff.gO41k5

2022-11-17 Thread Joshua Peisach
Hi Lucas,

VCS has 22.08.02-2 which should fix this.

On Sun, 23 Oct 2022 14:59:40 +0200 Lucas Nussbaum  wrote:
> Source: cppimport
> Version: 22.08.02-1
> Severity: serious
> Justification: FTBFS
> Tags: bookworm sid ftbfs
> User: lu...@debian.org
> Usertags: ftbfs-20221023 ftbfs-bookworm
> 
> Hi,
> 
> During a rebuild of all packages in sid, your package failed to build
> on amd64.
> 
> 
> Relevant part (hopefully):
> >  debian/rules clean
> > dh clean --with python3 --buildsystem=pybuild
> >dh_auto_clean -O--buildsystem=pybuild
> > I: pybuild base:240: python3.10 setup.py clean 
> > /usr/lib/python3/dist-packages/setuptools/dist.py:530: UserWarning: 
> > Normalizing '22.08.02' to '22.8.2'
> >   warnings.warn(tmpl.format(**locals()))
> > running clean
> > removing '/<>/.pybuild/cpython3_3.10_cppimport/build' (and 
> > everything under it)
> > 'build/bdist.linux-x86_64' does not exist -- can't clean it
> > 'build/scripts-3.10' does not exist -- can't clean it
> >dh_autoreconf_clean -O--buildsystem=pybuild
> >dh_clean -O--buildsystem=pybuild
> >  dpkg-source -b .
> > dpkg-source: info: using options from 
> > cppimport-22.08.02/debian/source/options: 
> > --extend-diff-ignore=^[^/]*[.]egg-info/
> > dpkg-source: info: using source format '3.0 (quilt)'
> > dpkg-source: info: building cppimport using existing 
> > ./cppimport_22.08.02.orig.tar.gz
> > dpkg-source: info: using patch list from debian/patches/series
> > dpkg-source: info: local changes detected, the modified files are:
> >  cppimport-22.08.02/cppimport/_version.py
> > dpkg-source: error: aborting due to unexpected upstream changes, see 
> > /tmp/cppimport_22.08.02-1.diff.gO41k5
> > dpkg-source: info: Hint: make sure the version in debian/changelog matches 
> > the unpacked source tree
> > dpkg-source: info: you can integrate the local changes with dpkg-source 
> > --commit
> > dpkg-buildpackage: error: dpkg-source -b . subprocess returned exit status 2
> > 
> > Build finished at 2022-10-23T07:40:14Z
> 
> 
> The full build log is available from:
> http://qa-logs.debian.net/2022/10/23/cppimport_22.08.02-1_unstable.log
> 
> All bugs filed during this archive rebuild are listed at:
> https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20221023;users=lu...@debian.org
> or:
> https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20221023=lu...@debian.org=1=1=1=1#results
> 
> A list of current common problems and possible solutions is available at
> http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!
> 
> If you reassign this bug to another package, please marking it as 
> 'affects'-ing
> this package. See https://www.debian.org/Bugs/server-control#affects
> 
> If you fail to reproduce this, please provide a build log and diff it with 
> mine
> so that we can identify if something relevant changed in the meantime.
> 
> 



Bug#1012634: RFS: cppimport/22.05.11-1 -- cppimport - Import C++ directly from Python! (Python 3

2022-06-10 Thread Joshua Peisach
Package: sponsorship-requests
Severity: normal

Dear mentors,

I am looking for a sponsor for my package "cppimport":

 * Package name: cppimport
   Version : 22.05.11-1
   Upstream Author : Ben Thompson 
 * URL : https://github.com/tbenthompson/cppimport
 * License : Expat
 * Vcs : https://salsa.debian.org/python-team/packages/cppimport
   Section : python

The source builds the following binary packages:

  python3-cppimport - cppimport - Import C++ directly from Python! (Python 3)

To access further information about this package, please visit the following 
URL:

  https://mentors.debian.net/package/cppimport/

Alternatively, you can download the package with 'dget' using this command:

  dget -x 
https://mentors.debian.net/debian/pool/main/c/cppimport/cppimport_22.05.11-1.dsc

Changes since the last upload:

 cppimport (22.05.11-1) unstable; urgency=medium
 .
   * New upstream version 22.05.11
   * Add python3-setuptools-scm to build-deps
   * Update copyright

Regards,
--
  Joshua Peisach



Bug#1011594: Please import new upstream snapshot (currently at 0.0~git20220518.60ebf56)

2022-05-25 Thread Joshua Peisach
 -l test/kotlin-mode-test.el --eval 
\(ert-run-tests-batch-and-exit\) returned exit code 1
make: *** [debian/rules:4: binary] Error 25
dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2
debuild: fatal error at line 1182:
dpkg-buildpackage -us -uc -ui -i -I failed
gbp:error: 'debuild -i -I' failed: it exited with 29

I honestly do not know anything about the kotlin-mode package's code itself, 
just that it's for Kotlin. I'm willing to still QA and make small fixes if I 
have to.

I also get accepted into a magnet school, so I will continue to be busy but 
will get good classes in computer science 

Thanks, I'll catch up with you when either I patch it or it gets fixed.
-Josh

From: Nicholas D Steeves 
Sent: Tuesday, May 24, 2022 6:50 PM
To: Debian Bug Tracking System 
Subject: Bug#1011594: Please import new upstream snapshot (currently at 
0.0~git20220518.60ebf56)

Package: kotlin-mode
Version: 0.0~git20210917.3e0c340-1
Severity: normal
X-Debbugs-Cc: s...@debian.org

Hi Joshua,

Upstream has released bugfixes, so please import them into your package :)

Also, your package doesn't yet declare a team maintainer.  To make it
officially team maintained, please apply the following diff:

diff --git a/debian/control b/debian/control
index 41ade1f..ad10a0b 100644
--- a/debian/control
+++ b/debian/control
@@ -1,7 +1,8 @@
 Source: kotlin-mode
 Section: editors
 Priority: optional
-Maintainer: Joshua Peisach 
+Maintainer: Debian Emacsen team 
+Uploaders: Joshua Peisach 
 Build-Depends: debhelper-compat (= 13),
  dh-elpa
 Standards-Version: 4.6.0

Sorry I forgot to ask if you intended for this package to be team-maintained 
during the initial sponsorship process.

Don't forget to close this bug from the changelog, and please let me know when 
you're ready for me to sponsor.

Regards,
Nicholas

P.S. I'm not sure if you noticed, but kotlin-mode didn't upgrade to testing 
because you didn't request a -2 (second Debian release) source-only upload.  
Uploading this new version as a source-only upload will resolve this issue.


Bug#1011349: sway: PATH remains set to ENV_SUPATH in sway environment

2022-05-20 Thread Joshua Honeycutt
Package: sway
Version: 1.7-2
Severity: normal

Dear Maintainer,

On a new install running bookworm my regular user has the wrong PATH 
set. The path used matches ENV_SUPATH from /etc/login.defs.

I think this is because sway inherits the environment from the desktop 
manager (gdm3) which is run as root.

One solution I found in #968910 (message #15) is to modify 
/usr/share/wayland-sessions/sway.desktop to run sway in a login shell.

Another similar bug is #1011088 (zsh) but I installed Gnome and logged 
into a Wayland session and my user got the correct PATH in my bash 
shell (did not test under zsh, but I don't expect a difference).

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

Kernel: Linux 5.17.0-1-amd64 (SMP w/4 CPU threads; PREEMPT)
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 sway depends on:
ii  libc62.33-7
ii  libcairo21.16.0-5
ii  libevdev21.12.1+dfsg-1
ii  libgdk-pixbuf-2.0-0  2.42.8+dfsg-1
ii  libgl1-mesa-dri  21.3.8-1
ii  libgles2 1.4.0-1
ii  libglib2.0-0 2.72.1-1
ii  libinput10   1.20.1-1
ii  libjson-c5   0.16-1
ii  libpango-1.0-0   1.50.7+ds-1
ii  libpangocairo-1.0-0  1.50.7+ds-1
ii  libpcre3 2:8.39-14
ii  libpixman-1-00.40.0-1
ii  libsystemd0  250.4-1
ii  libudev1 250.4-1
ii  libwayland-client0   1.20.0-1
ii  libwayland-cursor0   1.20.0-1
ii  libwayland-server0   1.20.0-1
ii  libwlroots10 0.15.1-2
ii  libxcb1  1.14-3
ii  libxkbcommon01.4.0-1
ii  policykit-1  0.105-33
ii  swaybg   1.1.1-2

Versions of packages sway recommends:
ii  foot  1.12.1-1
ii  suckless-tools46-2
ii  sway-backgrounds  1.7-2

Versions of packages sway suggests:
ii  swayidle1.7.1-2
ii  swaylock1.6-2
pn  xdg-desktop-portal-wlr  

-- no debconf information



Bug#1010949: Reply to MIchael Biebl's message

2022-05-18 Thread Joshua Brickel
Okay, you got me convinced. So I guess I should try the one kernel below.

Is there a howto page on how to do this and make sure grub knows about it
too?






On Tue, 17 May 2022 11:03:28 +0200 Michael Biebl  wrote:
> Am 17.05.22 um 11:02 schrieb Michael Biebl:
> > Am 17.05.22 um 00:22 schrieb Joshua Brickel:
> >>
> >> I only figured it was systemd because systemd, from what I know is
> >> responsible for initiating suspend, and I figured waking up from it
> >> afterwards.
> >
> > While systemd triggers the suspend (which is basically) writing the
> > string "mem" to /sys/power/state, the actual suspend and subsequent
> > hibernate is handled by the kernel.
>
> s/hibernate/resume/
>


Bug#1010949: Reply to MIchael Biebl's message

2022-05-16 Thread Joshua Brickel
I only figured it was systemd because systemd, from what I know is
responsible for initiating suspend, and I figured waking up from it
afterwards.  But I'm not discounting the possibility it is a kernel issue.
If there is any testing you want me to do (logs and that sort of thing) to
determine what is causing this, I will be happy to try and oblige.  And if
you truly think this is a kernel issue, and have the authority to reassign
the bug to the kernel team, then by all means please do so.  My only
interest is trying to get this issue solved.

Also I'm not sure why I didn't get your reply to my posting.  So sorry for
the late follow-up.


Bug#1010949: Wake up from Suspend makes computer unusable

2022-05-13 Thread Joshua Brickel
Package: systemd

Version: 247.3-7

Severity: critical

Justification: breaks the whole system


This is happening on Debian 11 Stable version, most up to date software.
This

only started a week or two ago.


How to repeat the bug.

Boot computer.

Send computer into suspend mode.

Wait for the computer to be in suspend mode

Touch a letter on the keyboard.


What happens:

When waking up from suspend mode only one monitor goes active (of two in my

case), and the keyboard and mouse no longer respond. The system is thus

unusable, any information not saved before suspend is lost as the only way
to

bring down the computer at that point is to shut it off from the physical
power

button.


I have tried this from both gnome and KDE, same issue. So I'm pretty sure it

is within the Systemd subsystem.


-- Package-specific info:


-- System Information:

Debian Release: 11.3

APT prefers stable-security

APT policy: (500, 'stable-security'), (500, 'stable')

Architecture: amd64 (x86_64)

Foreign Architectures: i386


Kernel: Linux 5.10.0-14-amd64 (SMP w/48 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


Versions of packages systemd depends on:

ii adduser 3.118

ii libacl1 2.2.53-10

ii libapparmor1 2.13.6-10

ii libaudit1 1:3.0-2

ii libblkid1 2.36.1-8+deb11u1

ii libc6 2.31-13+deb11u3

ii libcap2 1:2.44-1

ii libcrypt1 1:4.4.18-4

ii libcryptsetup12 2:2.3.7-1+deb11u1

ii libgcrypt20 1.8.7-6

ii libgnutls30 3.7.1-5

ii libgpg-error0 1.38-2

ii libip4tc2 1.8.7-1

ii libkmod2 28-1

ii liblz4-1 1.9.3-2

ii liblzma5 5.2.5-2.1~deb11u1

ii libmount1 2.36.1-8+deb11u1

ii libpam0g 1.4.0-9+deb11u1

ii libseccomp2 2.5.1-1+deb11u1

ii libselinux1 3.1-3

ii libsystemd0 247.3-7

ii libzstd1 1.4.8+dfsg-2.1

ii mount 2.36.1-8+deb11u1

ii util-linux 2.36.1-8+deb11u1


Versions of packages systemd recommends:

ii dbus 1.12.20-2

ii systemd-timesyncd [time-daemon] 247.3-7


Versions of packages systemd suggests:

ii policykit-1 0.105-31+deb11u1

pn systemd-container 


Versions of packages systemd is related to:

pn dracut 

ii initramfs-tools 0.140

ii libnss-systemd 247.3-7

ii libpam-systemd 247.3-7

ii udev 247.3-7


-- Configuration Files:

/etc/systemd/logind.conf changed:

[Login]

IdleAction=suspend

IdleActionSec=10min



-- no debconf information


Bug#1008507:

2022-03-29 Thread Joshua Hudson
diff -ur glibc.orig/glibc/sysdeps/unix/sysv/linux/pathconf.c
glibc/glibc/sysdeps/unix/sysv/linux/pathconf.c
--- glibc.orig/glibc/sysdeps/unix/sysv/linux/pathconf.c2022-03-29
17:50:12.558027042 -0700
+++ glibc/glibc/sysdeps/unix/sysv/linux/pathconf.c2022-03-29
17:52:33.262157543 -0700
@@ -183,6 +183,11 @@
 case XFS_SUPER_MAGIC:
   return XFS_LINK_MAX;

+case MSDOS_SUPER_MAGIC:
+#ifdef EXFAT_SUPER_MAGIC // For when it gets added in about 30 years
+case EXFAT_SUPER_MAGIC:
+#endif
+  return 1;
 case LUSTRE_SUPER_MAGIC:
   return LUSTRE_LINK_MAX;



Bug#1008507:

2022-03-29 Thread Joshua Hudson
/* reproduce glibc bug */

/*
 * I don't typically care what the return of pathconf(..., _PC_LINK_MAX)
 * is; I just care whether or not it's greater than 1 because I'm checking
 * whether the filesystem supports hard links or not.
 */

#include 
#include 
#include 
#include 
#include 
#include 

int main()
{
char file[40];
char dir[40];
char commandbuf[120];
sprintf(file, "/tmp/%u.img", getpid());
sprintf(dir, "/tmp/%u.mnt", getpid());
FILE *fimage = fopen(file, "wb");
fseek(fimage, 1440 * 1024 - 1, SEEK_SET);
fputc(0, fimage);
fclose(fimage);
mkdir(dir, 0);
sprintf(commandbuf, "mkfs.fat /tmp/%u.img", getpid());
if (system(commandbuf) != 0) {
rmdir(dir);
unlink(file);
return 1;
}

sprintf(commandbuf, "mount -o loop -t msdos %s %s", file, dir);
if (system(commandbuf) != 0) {
rmdir(dir);
unlink(file);
return 1;
}

int r;
printf("Testing pathconf(%s, _PC_LINK_MAX)...");
r = pathconf(dir, _PC_LINK_MAX) != 1;
printf(r ? "Failed\n" : "OK\n");
sprintf(commandbuf, "umount %s", dir);
system(commandbuf);
rmdir(dir);
unlink(file);
return r;
}



Bug#1008507: libc6: pathconf("mountpont of FAT filesystem", _PC_LINK_MAX) returns 127, expected 1

2022-03-27 Thread Joshua
Package: libc6
Version: All of them
Severity: normal
Tags: newcomer

Dear Maintainer,

what lead up to the situation is well-described in my stackoverflow post:
https://stackoverflow.com/questions/71641957/how-to-check-if-a-filesystem-supports-hard-links-in-linux

Since posting it, I have traced the bug through the glibc sources and found 
that it's bugged.
There's cases for common filesystems that have nonstandard values, but you 
almost never care
what the actual value is.

On the other hand, there are no cases for writable filesystems that simply 
don't have hard links.
(FAT). EXFAT would also fall into this but that only exists as a FUSE module 
right now.

These turn out to be the ones we care about becasue they are three of the four 
widely supported
filesystems on removable media (with the fourth being UDF).

Writing a patch is trivial. Getting it into glibc, well I'm gonna try but you 
may have more luck.

-- System Information:
Debian Release: 10.11
  APT prefers oldstable-updates
  APT policy: (500, 'oldstable-updates'), (500, 'oldstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.19.0-18-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1), LANGUAGE=en_US 
(charmap=ISO-8859-1)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit-sysv
LSM: AppArmor: enabled



Bug#1003855: (everything)

2022-02-23 Thread Joshua Peisach
Hi Nicholas, and thank you for helping me!

I've applied your suggestions (I kind of bunted the long description, looked at 
other descriptions in other emacs packages). As for d/rules, I tried a 
drop-down approach. I hope it works.

In d/copyright, a small glance at the header of the .el files show the license 
(lol)

I pushed my commits and am about to upload to mentors again.

Thanks
-Josh


Bug#1003855: RFS: kotlin-mode/20210917git0-1 [RFP] -- Major mode for kotlin

2022-01-16 Thread Joshua Peisach
Package: sponsorship-requests
Severity: wishlist

Dear mentors,

I am looking for a sponsor for my package "kotlin-mode":

 * Package name: kotlin-mode
   Version : 20210917git0-1
   Upstream Author : Emacs Kotlin Mode Maintainers
 * URL : 
https://github.com/Emacs-Kotlin-Mode-Maintainers/kotlin-mode
 * License : GPL-3+
 * Vcs : https://salsa.debian.org/emacsen-team/kotlin-mode
   Section : lisp

It builds those binary packages:

  elpa-kotlin-mode - Major mode for kotlin

To access further information about this package, please visit the following 
URL:

  https://mentors.debian.net/package/kotlin-mode/

Alternatively, one can download the package with dget using this command:

  dget -x 
https://mentors.debian.net/debian/pool/main/k/kotlin-mode/kotlin-mode_20210917git0-1.dsc

Changes for the initial release:

 kotlin-mode (20210917git0-1) unstable; urgency=medium
 .
   * Initial release. (Closes: #922934)

Regards,
--
  Joshua Peisach



Bug#1002715: ITP: sc-im -- An ncurses spreadsheet program for terminal

2021-12-27 Thread Joshua Peisach
Package: wnpp
Severity: wishlist
Owner: Joshua Peisach 
X-Debbugs-Cc: debian-de...@lists.debian.org, itzswirlz2...@outlook.com

* Package name: sc-im
  Version : 0.8.2
  Upstream Author : Andrés Martinelli 
* URL : https://github.com/andmarti1424/sc-im
* License : All rights reserved
  Programming Lang: C, has Lua scripting support
  Description : An ncurses spreadsheet program for terminal

sc-im is a fork of sc, the spreadsheet calculator that is now
deprecated/unmaintained. It has a ton of new features including theme
support, undo/redo, filtering autobackups, key mappings, etc.

It still has Vim-like keybindings and is similar to sc (users migrating
should not have any issues), which easily replaces the 'sc' package being
autoremoved.

I will maintain this with others under the Debian Math Team on Salsa, and
will be requesting a sponsor/RFS.

https://salsa.debian.org/math-team/sc-im


Bug#987755: Mips build failure in new rpf 1.0.9 (Was: Bug#987755: r-cran-rpf: FTBFS on mips due to a variable called 'mips')

2021-10-19 Thread Joshua N Pritikin
On Tue, Oct 19, 2021 at 06:00:35PM +0530, Nilesh Patra wrote:
> There is still a failure in the latest version as well (1.0.9)
> a minor change fixes it, please consider applying attached patch.

Gah! Will do



Bug#994912: Re: Bug#994912: RFS: pyupgrade/2.24.0-1 [RFP] -- Tool to automatically upgrade Python 3 syntax for newer versions

2021-09-24 Thread Joshua Peisach
Hello zigo, thanks for your review. Wrote a lot but trimmed it down. Dependency 
chain goes to tokenize-rt. I'll get it packaged and RFS later
-Josh


Bug#994912: RFS: pyupgrade/2.24.0-1 [RFP] -- Tool to automatically upgrade Python 3 syntax for newer versions

2021-09-22 Thread Joshua Peisach
Package: sponsorship-requests
Severity: wishlist

Dear mentors,

I am looking for a sponsor for my package "pyupgrade":

 * Package name: pyupgrade
   Version : 2.24.0-1
   Upstream Author : Anthony Sottile 
 * URL : https://github.com/asottile/pyupgrade
 * License : MIT
 * Vcs : https://salsa.debian.org/python-team/packages/pyupgrade
   Section : devel

It builds those binary packages:

  pyupgrade - Tool to automatically upgrade Python 3 syntax for newer versions

To access further information about this package, please visit the following 
URL:

  https://mentors.debian.net/package/pyupgrade/

Alternatively, one can download the package with dget using this command:

  dget -x 
https://mentors.debian.net/debian/pool/main/p/pyupgrade/pyupgrade_2.24.0-1.dsc

Changes for the initial release:

 pyupgrade (2.24.0-1) unstable; urgency=medium
 .
   * Initial packaging
   * Fix lintian issues, cleanup and add a few extra essentials
 .
   * Initial release (Closes: #988658)

Regards,
--
  Joshua Peisach



Bug#969202: ITA: binutils-avr -- Binary utilities supporting Atmel's AVR targets

2021-09-13 Thread Joshua Horn
Owner: knapper...@aol.com

Bug#969202:

2021-09-13 Thread Joshua Horn
Control: retitle -1 ITA: binutils-avr -- Binary utilities supporting Atmel's 
AVR targets

Bug#969202: ITA: binutils-avr -- Binary utilities supporting Atmel's AVR targets

2021-09-13 Thread Joshua Horn
Control: retitle -1 ITA: binutils-avr -- Binary utilities supporting Atmel's 
AVR targetsControl: owner knapper...@aol.com



Maintainer,

Would like to start contributing by taking over this package.

Bug#993343: OpenLDAP 2.5 FTBFS on GNU/Hurd: MAXPATHLEN undeclared

2021-09-04 Thread Joshua Branson
Ryan Tandy  writes:

> Source: openldap
> Version: 2.5.5+dfsg-1~exp1
> Severity: important
> Tags: upstream ftbfs help
> Forwarded: https://bugs.openldap.org/show_bug.cgi?id=9658
>
> I confirmed locally that current git master is still affected.
>
> It's well-known that GNU/Hurd doesn't provide MAXPATHLEN.
> https://www.gnu.org/software/hurd/hurd/porting/guidelines.html#PATH_MAX_tt_MAX_PATH_tt_MAXPATHL
>
> I don't have the bandwidth to work on this myself. It would be great
> if someone from the Hurd community could look at it.

This is supposed to be an "easy fix".  I'd be willing to try to work
with you to help you fix this.  Bear in mind, I'm not the best C
developer.  I'm on Eastern Standard Time.  I'm usually free in the
mornings.  Does that sound good for you?

https://www.gnu.org/software/hurd/community/gsoc/project_ideas/maxpath.html

>
> thanks
> Ryan
>

--
Joshua Branson (jab in #guix)
Sent from Emacs and Gnus
  https://gnucode.me
  https://video.hardlimit.com/accounts/joshua_branson/video-channels
  https://propernaming.org
  "You can have whatever you want, as long as you help
enough other people get what they want." - Zig Ziglar



Bug#909228: RFP: loop -- "UNIX's missing loop command!"

2021-08-24 Thread Joshua Peisach
>  Well, then good luck with search of sponsor/maintainer

I don't think you were trying to ride off a "I hope someone will want to pick 
this up", but if you were then he doesn't need any. I'll take care of it. Per 
rust packaging team standards, this should be converted into an ITP. ("Don't 
file ITPs for library crates, but do file them for binary crates.")

In reality I just need to contribute more to Debian so I can do more stuff with 
Cinnamon, but a small package like this should be easy to maintain, and with 
debcargo it should be an easy chore.


Bug#992214: RFS: nemo-audio-tab/5.0.0-1 [ITP] -- View audio tag information from Nemo's properties tab

2021-08-15 Thread Joshua Peisach
Package: sponsorship-requests
Severity: wishlist

Dear mentors,

I am looking for a sponsor for my package "nemo-audio-tab":

 * Package name: nemo-audio-tab
   Version : 5.0.0-1
   Upstream Author : Clement Lefebvre 
 * URL : https://community.linuxmint.com/software/view/nemo-audio-
tab
 * License : GPL-3+
 * Vcs : https://salsa.debian.org/cinnamon-team/nemo-audio-tab
   Section : utils

It builds those binary packages:

  nemo-audio-tab - View audio tag information from Nemo's properties tab

To access further information about this package, please visit the following
URL:

  https://mentors.debian.net/package/nemo-audio-tab/

Alternatively, one can download the package with dget using this command:

  dget -x https://mentors.debian.net/debian/pool/main/n/nemo-audio-tab/nemo-
audio-tab_5.0.0-1.dsc

Or, to view the code as a whole, visit:

  https://salsa.debian.org/cinnamon-team/nemo-audio-tab

Changes for the initial release:

 nemo-audio-tab (5.0.0-1) unstable; urgency=medium
 .
   * Initial release. (Closes: #971971)

Regards,
--
  Joshua Peisach



Bug#991789: gnome: Suspend activates in multi-seat environment when only one seat is active

2021-08-01 Thread Joshua Brickel
Package: gnome
Version: 1:3.38+3
Severity: important
X-Debbugs-Cc: joshua.bric...@gmail.com

I have a two seat multi-seat setup.  When one seat is active and the other
is not (under GDM control), then after about twenty minutes the computer
goes into suspend mode, even in the middle of typing a sentence on the
active seat.

The system was not doing this till a software update came through about a
week ago.  Hence why I think this is a gnome issue, and probably a GDM
issue.

Note this happens even though on the active seat I set the under
settings->Power->Automatic
Suspend to OFF.




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

Kernel: Linux 5.10.0-8-amd64 (SMP w/48 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

Versions of packages gnome depends on:
ii  avahi-daemon 0.8-5
ii  cheese   3.38.0-3
ii  cups-pk-helper   0.2.6-1+b1
ii  desktop-base 11.0.3
ii  evolution3.38.3-1
ii  evolution-plugins3.38.3-1
ii  file-roller  3.38.1-1
ii  gedit-plugins3.38.1-1
ii  gnome-calendar   3.38.2-1
ii  gnome-clocks 3.38.0-1
ii  gnome-color-manager  3.36.0-1
ii  gnome-core   1:3.38+3
ii  gnome-documents  3.34.0-2
ii  gnome-getting-started-docs   3.38.0-1
ii  gnome-maps   3.38.2-1
ii  gnome-music  3.36.7-1
ii  gnome-screenshot 3.38.0-1
ii  gnome-sound-recorder 3.38.1-1
ii  gnome-todo   3.28.1-6
ii  gnome-tweaks 3.34.0-4
ii  gnome-weather3.36.1-1
ii  gstreamer1.0-libav   1.18.4-3
ii  gstreamer1.0-plugins-ugly1.18.4-2
ii  libgsf-bin   1.14.47-1
ii  libproxy1-plugin-networkmanager  0.4.17-1
ii  libreoffice-calc 1:7.0.4-4
ii  libreoffice-gnome1:7.0.4-4
ii  libreoffice-impress  1:7.0.4-4
ii  libreoffice-writer   1:7.0.4-4
ii  network-manager-gnome1.20.0-3
ii  orca 3.38.2-1
ii  rhythmbox3.4.4-4
ii  rhythmbox-plugin-cdrecorder  3.4.4-4
ii  rhythmbox-plugins3.4.4-4
ii  rygel-playbin0.40.0-1
ii  rygel-tracker0.40.0-1
ii  seahorse 3.38.0.1-2
ii  shotwell 0.30.11-1
ii  simple-scan  3.38.1-1
ii  totem-plugins3.38.0-2
ii  xdg-user-dirs-gtk0.10-3

Versions of packages gnome recommends:
ii  gnome-games 1:3.38+3
ii  gnome-remote-desktop0.1.9-5
ii  nautilus-extension-brasero  3.12.2-6
ii  transmission-gtk3.00-1

Versions of packages gnome suggests:
pn  alacarte 
pn  empathy  
pn  firefox-esr-l10n-all | firefox-l10n-all  
pn  goobox | sound-juicer
pn  polari   
ii  vinagre  3.22.0-8.1
pn  webext-ublock-origin 

Versions of packages gnome-core depends on:
ii  adwaita-icon-theme3.38.0-1
ii  at-spi2-core  2.38.0-4
ii  baobab3.38.0-1
ii  caribou   0.4.21-7.1
ii  dconf-cli 0.38.0-2
ii  dconf-gsettings-backend   0.38.0-2
ii  eog   3.38.2-1
ii  evince3.38.2-1
ii  evolution-data-server 3.38.3-1
ii  firefox-esr   78.12.0esr-1
ii  fonts-cantarell   0.111-3
ii  gdm3  3.38.2.1-1
ii  gedit 3.38.1-1
ii  gkbd-capplet  3.26.1-1
ii  glib-networking   2.66.0-2
ii  gnome-backgrounds 3.38.0-1
ii  gnome-bluetooth   3.34.3-2
ii  gnome-calculator  3.38.2-1
ii  gnome-characters  3.34.0-1
ii  gnome-contacts3.38.1-1+b1
ii  gnome-control-center  1:3.38.4-1
ii  gnome-disk-utility3.38.2-1
ii  gnome-font-viewer 3.34.0-2+b1
ii  gnome-keyring 3.36.0-1
ii  gnome-logs3.36.0-2
ii  gnome-menus   3.36.0-1
ii  gnome-online-accounts 3.38.0-3
ii  gnome-online-miners   3.34.0-2
ii  gnome-session 3.38.0-4
ii  gnome-settings-daemon 3.38.2-1
ii  gnome-shell   3.38.4-1
ii  gnome-shell-extensions3.38.2-1
ii  gnome-software3.38.1-1
ii  gnome-sushi   

Bug#203805: basilisk2: timing speeds are messed up in new version

2021-07-25 Thread Joshua Kwan
Hi Paul,

That's pretty fun to revive an 18 year old Debian bug! I did a triple take
looking at the header.

I don't think I even have the proper setup to validate this bug any more,
so you're welcome to close it out. Thanks for readopting basiliskII!

best,
Josh

On Sun, Jul 25, 2021 at 10:44 PM Paul Wise  wrote:

> On Fri, 01 Aug 2003 12:18:24 -0700 Joshua Kwan wrote:
>
> > I just upgraded basilisk2 from the last version (the one uploaded long
> > ago), and now the emulator is extremely unstable.
>
> Since you reported this issue, basilisk2 was removed from Debian but
> was then reintroduced to Debian, would you mind testing if this issue
> is still present in the latest Debian package?
>
> --
> bye,
> pabs
>
> https://wiki.debian.org/PaulWise
>


Bug#987833: r-cran-openmx: FTBFS on mips due to a variable called 'mips'

2021-05-05 Thread Joshua N Pritikin
On Wed, May 05, 2021 at 09:38:03AM +0200, Andreas Tille wrote:
> Control: tags -1 upstream
> Control: forwarded -1 Joshua Pritikin 
> 
> Hi Joshua,
> 
> here is another instance of the mips variable.  It would be great
> if you could fix this in your next release.

Yeah, will do



Bug#987755: r-cran-rpf: FTBFS on mips due to a variable called 'mips'

2021-04-29 Thread Joshua N Pritikin
On Thu, Apr 29, 2021 at 04:18:07PM +0200, Andreas Tille wrote:
> Control: tags -1 upstream
> Control: forwarded -1 Joshua Pritikin 
> 
> Hi Joshua,
> 
> I wonder whether you want to fix this issue with the suggested
> patch upstream.

Thank you.

Yes, I will apply it.



Bug#985373: mirror submission for debian.mirror.treudler.net

2021-03-16 Thread Joshua Treudler
Package: mirrors
Severity: wishlist
User: mirr...@packages.debian.org
Usertags: mirror-submission

Submission-Type: new
Site: debian.mirror.treudler.net
Type: leaf
Archive-architecture: ALL amd64 arm64 armel armhf hurd-i386 i386 kfreebsd-amd64 
kfreebsd-i386 mips mips64el mipsel powerpc ppc64el s390x
Archive-http: /debian/
Maintainer: Joshua Treudler 
Country: DE Germany




Trace Url: http://debian.mirror.treudler.net/debian/project/trace/
Trace Url: 
http://debian.mirror.treudler.net/debian/project/trace/ftp-master.debian.org
Trace Url: 
http://debian.mirror.treudler.net/debian/project/trace/debian.mirror.treudler.net



Bug#985318: mirror submission for debian.mirror.treudler.net

2021-03-15 Thread Joshua Treudler
Package: mirrors
Severity: wishlist
User: mirr...@packages.debian.org
Usertags: mirror-submission

Submission-Type: new
Site: debian.mirror.treudler.net
Type: leaf
Archive-architecture: ALL amd64 arm64 armel armhf hurd-i386 i386 kfreebsd-amd64 
kfreebsd-i386 mips mips64el mipsel powerpc ppc64el s390x
Archive-http: /debian/
Maintainer: Joshua Treudler 
Country: DE Germany




Trace Url: http://debian.mirror.treudler.net/debian/project/trace/
Trace Url: 
http://debian.mirror.treudler.net/debian/project/trace/ftp-master.debian.org
Trace Url: 
http://debian.mirror.treudler.net/debian/project/trace/debian.mirror.treudler.net



Bug#985310: ITP: xfce4-xapp-status-plugin -- Xapp status icon plugin for the Xfce 4 panel

2021-03-15 Thread Joshua Peisach
Package: wnpp
Severity: wishlist
Owner: Joshua Peisach 
X-Debbugs-Cc: debian-de...@lists.debian.org, itzswirlz2...@outlook.com

* Package name: xfce4-xapp-status-plugin
  Version : 0.2.2
  Upstream Author : Clement Lefebvre 
* URL : https://github.com/linuxmint/xfce4-xapp-status-plugin
* License : GPL-3+
  Programming Lang: C
  Description : Xapp status icon plugin for the Xfce 4 panel

This adds a status icon for displaying XappStatus in the Xfce 4 panel.
This is the same as xfce4-statusnotifier-plugin, but for Xapps.

If anyone is using an X-App, seen in Cinnamon, then they could have a status
notifier in the panel.

I will hopefully get this into xfce-extras-team.



Bug#971681: r-cran-openmx regression on arm, will not migrate to testing due to failing autopkgtests

2021-03-12 Thread Joshua N Pritikin
On Wed, Feb 17, 2021 at 07:57:11AM +0100, Andreas Tille wrote:
> On Fri, Feb 12, 2021 at 01:03:23PM -0500, Joshua N Pritikin wrote:
> > > I submitted a new release to CRAN yesterday. It usually takes a few days 
> > > to correct any lingering issues and get it approved.
> > 
> > CRAN peeps said that v2.19.1 is accepted. I know the package info page 
> > isn't updated yet, but I expect that to happen soon.
> 
> Openmx version 2.18.1 made it finally to Debian testing and thus is a
> release candidate.  We are currently in freeze for the next stable
> release.  So any bump to a new upstream version should be very well
> thought.  Could you give any reason why we should better release with

I know it's too late, but v2.19.1 is now out on CRAN.



Bug#984964: gnome: Graphics Card remains black when waking from suspend

2021-03-10 Thread Joshua Brickel
Package: gnome
Version: 1:3.38+3
Severity: important
X-Debbugs-Cc: joshua.bric...@gmail.com

This only began happenning with the latest updates for bullseye (I had a
version from a few weeks ago that worked fine, but updated the other day).

What happens is that if one suspends the computer then wake it back up the
computer comes back up (lights inside the computer box turn on, fans start up,
etc), but the graphics remains black.  If I pull the cord on the back of the
monitor it then recognized it no longer is talking to a grahpics card, but if I
plug the cord back in it still remains just black.

The procedure I did was:
1) Boot up the computer
2) Login to a user
3) Suspend the machine.
4) After it fully suspends, I try to wake it back up.

Result:  Black screen with no way to interact with the computer.



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

Kernel: Linux 5.10.0-4-amd64 (SMP w/48 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

Versions of packages gnome depends on:
ii  avahi-daemon 0.8-5
ii  cheese   3.38.0-3
ii  cups-pk-helper   0.2.6-1+b1
ii  desktop-base 11.0.1
ii  evolution3.38.3-1
ii  evolution-plugins3.38.3-1
ii  file-roller  3.38.0-1
ii  gedit-plugins3.38.1-1
ii  gnome-calendar   3.38.2-1
ii  gnome-clocks 3.38.0-1
ii  gnome-color-manager  3.36.0-1
ii  gnome-core   1:3.38+3
ii  gnome-documents  3.34.0-2
ii  gnome-getting-started-docs   3.38.0-1
ii  gnome-maps   3.38.2-1
ii  gnome-music  3.36.7-1
ii  gnome-screenshot 3.38.0-1
ii  gnome-sound-recorder 3.38.0-3
ii  gnome-todo   3.28.1-6
ii  gnome-tweaks 3.34.0-4
ii  gnome-weather3.36.1-1
ii  gstreamer1.0-libav   1.18.3-1
ii  gstreamer1.0-plugins-ugly1.18.3-1
ii  libgsf-bin   1.14.47-1
ii  libproxy1-plugin-networkmanager  0.4.17-1
ii  libreoffice-calc 1:6.1.5-3+deb10u6
ii  libreoffice-gnome1:6.1.5-3+deb10u6
ii  libreoffice-impress  1:6.1.5-3+deb10u6
ii  libreoffice-writer   1:6.1.5-3+deb10u6
ii  network-manager-gnome1.20.0-3
ii  orca 3.38.2-1
ii  rhythmbox3.4.4-4
ii  rhythmbox-plugin-cdrecorder  3.4.4-4
ii  rhythmbox-plugins3.4.4-4
ii  rygel-playbin0.40.0-1
ii  rygel-tracker0.40.0-1
ii  seahorse 3.38.0.1-1
ii  shotwell 0.30.11-1
ii  simple-scan  3.38.1-1
ii  totem-plugins3.38.0-2
ii  xdg-user-dirs-gtk0.10-3

Versions of packages gnome recommends:
ii  gnome-games 1:3.38+3
ii  gnome-remote-desktop0.1.9-4
ii  nautilus-extension-brasero  3.12.2-6
ii  transmission-gtk3.00-1

Versions of packages gnome suggests:
pn  alacarte 
pn  empathy  
pn  firefox-esr-l10n-all | firefox-l10n-all  
pn  goobox | sound-juicer
pn  polari   
ii  vinagre  3.22.0-8
pn  webext-ublock-origin 

Versions of packages gnome-core depends on:
ii  adwaita-icon-theme3.38.0-1
ii  at-spi2-core  2.38.0-2
ii  baobab3.38.0-1
ii  caribou   0.4.21-7.1
ii  dconf-cli 0.38.0-2
ii  dconf-gsettings-backend   0.38.0-2
ii  eog   3.38.2-1
ii  evince3.38.2-1
ii  evolution-data-server 3.38.3-1
ii  firefox-esr   78.8.0esr-1
ii  fonts-cantarell   0.111-3
ii  gdm3  3.38.2.1-1
ii  gedit 3.38.1-1
ii  gkbd-capplet  3.26.1-1
ii  glib-networking   2.66.0-2
ii  gnome-backgrounds 3.38.0-1
ii  gnome-bluetooth   3.34.3-2
ii  gnome-calculator  3.38.2-1
ii  gnome-characters  3.34.0-1
ii  gnome-contacts3.38.1-1+b1
ii  gnome-control-center  1:3.38.4-1
ii  gnome-disk-utility3.38.2-1
ii  gnome-font-viewer 3.34.0-2+b1
ii  gnome-keyring 3.36.0-1
ii  gnome-logs3.36.0-2
ii  gnome-menus   3.36.0-1
ii  gnome-online-accounts 3.38.0-3
ii  gnome-online-miners   3.34.0-2
ii  gnome-session  

Bug#984903: gnome: Sound output device changes unexpectedly. It keeps changing back to Digitial Output (S/PDIF) -USB Audio despite being changed to another device.

2021-03-09 Thread Joshua Brickel
Package: gnome
Version: 1:3.38+3
Severity: normal
Tags: a11y
X-Debbugs-Cc: joshua.bric...@gmail.com

Under settings in gnome when I change to a different Audio Source it for some
reason at what seems like random times switches back to
its default of Digitial Output (S/PDIF).  This affects other sofware like VLC
which then all of a sudden stops playing the audio portion.


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

Kernel: Linux 5.10.0-4-amd64 (SMP w/48 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

Versions of packages gnome depends on:
ii  avahi-daemon 0.8-5
ii  cheese   3.38.0-3
ii  cups-pk-helper   0.2.6-1+b1
ii  desktop-base 11.0.1
ii  evolution3.38.3-1
ii  evolution-plugins3.38.3-1
ii  file-roller  3.38.0-1
ii  gedit-plugins3.38.1-1
ii  gnome-calendar   3.38.2-1
ii  gnome-clocks 3.38.0-1
ii  gnome-color-manager  3.36.0-1
ii  gnome-core   1:3.38+3
ii  gnome-documents  3.34.0-2
ii  gnome-getting-started-docs   3.38.0-1
ii  gnome-maps   3.38.2-1
ii  gnome-music  3.36.7-1
ii  gnome-screenshot 3.38.0-1
ii  gnome-sound-recorder 3.38.0-3
ii  gnome-todo   3.28.1-6
ii  gnome-tweaks 3.34.0-4
ii  gnome-weather3.36.1-1
ii  gstreamer1.0-libav   1.18.3-1
ii  gstreamer1.0-plugins-ugly1.18.3-1
ii  libgsf-bin   1.14.47-1
ii  libproxy1-plugin-networkmanager  0.4.17-1
ii  libreoffice-calc 1:6.1.5-3+deb10u6
ii  libreoffice-gnome1:6.1.5-3+deb10u6
ii  libreoffice-impress  1:6.1.5-3+deb10u6
ii  libreoffice-writer   1:6.1.5-3+deb10u6
ii  network-manager-gnome1.20.0-3
ii  orca 3.38.2-1
ii  rhythmbox3.4.4-4
ii  rhythmbox-plugin-cdrecorder  3.4.4-4
ii  rhythmbox-plugins3.4.4-4
ii  rygel-playbin0.40.0-1
ii  rygel-tracker0.40.0-1
ii  seahorse 3.38.0.1-1
ii  shotwell 0.30.11-1
ii  simple-scan  3.38.1-1
ii  totem-plugins3.38.0-2
ii  xdg-user-dirs-gtk0.10-3

Versions of packages gnome recommends:
ii  gnome-games 1:3.38+3
ii  gnome-remote-desktop0.1.9-4
ii  nautilus-extension-brasero  3.12.2-6
ii  transmission-gtk3.00-1

Versions of packages gnome suggests:
pn  alacarte 
pn  empathy  
pn  firefox-esr-l10n-all | firefox-l10n-all  
pn  goobox | sound-juicer
pn  polari   
ii  vinagre  3.22.0-8
pn  webext-ublock-origin 

Versions of packages gnome-core depends on:
ii  adwaita-icon-theme3.38.0-1
ii  at-spi2-core  2.38.0-2
ii  baobab3.38.0-1
ii  caribou   0.4.21-7.1
ii  dconf-cli 0.38.0-2
ii  dconf-gsettings-backend   0.38.0-2
ii  eog   3.38.2-1
ii  evince3.38.2-1
ii  evolution-data-server 3.38.3-1
ii  firefox-esr   78.8.0esr-1
ii  fonts-cantarell   0.111-3
ii  gdm3  3.38.2.1-1
ii  gedit 3.38.1-1
ii  gkbd-capplet  3.26.1-1
ii  glib-networking   2.66.0-2
ii  gnome-backgrounds 3.38.0-1
ii  gnome-bluetooth   3.34.3-2
ii  gnome-calculator  3.38.2-1
ii  gnome-characters  3.34.0-1
ii  gnome-contacts3.38.1-1+b1
ii  gnome-control-center  1:3.38.4-1
ii  gnome-disk-utility3.38.2-1
ii  gnome-font-viewer 3.34.0-2+b1
ii  gnome-keyring 3.36.0-1
ii  gnome-logs3.36.0-2
ii  gnome-menus   3.36.0-1
ii  gnome-online-accounts 3.38.0-3
ii  gnome-online-miners   3.34.0-2
ii  gnome-session 3.38.0-3
ii  gnome-settings-daemon 3.38.1-3
ii  gnome-shell   3.38.3-3
ii  gnome-shell-extensions3.38.2-1
ii  gnome-software3.38.1-1
ii  gnome-sushi   3.38.0-1
ii  gnome-system-monitor  3.38.0-1
ii  gnome-terminal3.38.3-1
ii  gnome-themes-extra3.28-1
ii  gnome-user-docs   3.38.2-1
ii  gnome-user-share  

Bug#971681: r-cran-openmx regression on arm, will not migrate to testing due to failing autopkgtests

2021-02-12 Thread Joshua N Pritikin
On Sat, Jan 30, 2021 at 08:31:51AM -0500, Joshua N Pritikin wrote:
> On Sat, Jan 30, 2021 at 06:32:48PM +0530, Nilesh Patra wrote:
> > Many thanks for fixes,
> >
> > The freeze has started and soft freeze time is near as well.(2 weeks 
> > from now) OpenMx has removals of a bunch of packages from testing.
> > 
> > Hence, please consider doing a new upstream release if it looks okay 
> > to you.
> 
> I submitted a new release to CRAN yesterday. It usually takes a few days 
> to correct any lingering issues and get it approved.

CRAN peeps said that v2.19.1 is accepted. I know the package info page 
isn't updated yet, but I expect that to happen soon.



Bug#971681: r-cran-openmx regression on arm, will not migrate to testing due to failing autopkgtests

2021-01-30 Thread Joshua N Pritikin
On Sat, Jan 30, 2021 at 06:32:48PM +0530, Nilesh Patra wrote:
> Many thanks for fixes,
>
> The freeze has started and soft freeze time is near as well.(2 weeks 
> from now) OpenMx has removals of a bunch of packages from testing.
> 
> Hence, please consider doing a new upstream release if it looks okay 
> to you.

I submitted a new release to CRAN yesterday. It usually takes a few days 
to correct any lingering issues and get it approved.

Thanks.



Bug#971681: r-cran-openmx regression on arm, will not migrate to testing due to failing autopkgtests

2020-12-17 Thread Joshua N Pritikin
On Thu, Dec 17, 2020 at 11:04:02AM +0100, Andreas Tille wrote:
> In case it will work at least on arm64 we could ignore armhf issues 
> for the most practical use cases and exclude this architecture for 
> Debian until it gets finally fixed.

Yeah, that sounds like a good solution. I don't anticipate a lot of 
demand for OpenMx on 32bit arm. I believe we already have 64bit arm 
working. We'll try to get a new release out soon.

Do we need to do anything from our side to exclude OpenMx from armhf?



Bug#973504: ITP: nemo-preview -- quick previewer for nemo

2020-10-31 Thread Joshua Peisach
Package: wnpp
Severity: wishlist
Owner: Joshua Peisach 
X-Debbugs-Cc: debian-de...@lists.debian.org, itzswirlz2...@outlook.com

* Package name: nemo-preview
  Version : 4.6.0
  Upstream Author : Clement Lefebvre , Cosimo Cecchi

* URL : https://github.com/linuxmint/nemo-
extensions/tree/master/nemo-preview
* License : GPL-2+
  Programming Lang: C, JS
  Description : quick previewer for nemo

I will maintain this by myself until I can hopefully get it into cinnamon-team.



Bug#973502: RFS: nemo-pastebin/4.6.0-1 [ITP] -- Nemo extension to send files to a pastebin

2020-10-31 Thread Joshua Peisach
Package: sponsorship-requests
Severity: wishlist
X-Debbugs-Cc: itzswirlz2...@outlook.com

Dear mentors,

I am looking for a sponsor for my package "nemo-pastebin":

 * Package name: nemo-pastebin
   Version : 4.6.0-1
   Upstream Author : Clement Lefebvre , Michael Webster

 * URL : https://community.linuxmint.com/software/view/nemo-
pastebin
 * License : GPL-2+
 * Vcs : https://salsa.debian.org/ItzSwirlz-guest/nemo-pastebin
   Section : utils

It builds those binary packages:

  nemo-pastebin - Nemo extension to send files to a pastebin

To access further information about this package, please visit the following
URL:

  https://mentors.debian.net/package/nemo-pastebin/

Alternatively, one can download the package with dget using this command:

  dget -x https://mentors.debian.net/debian/pool/main/n/nemo-pastebin/nemo-
pastebin_4.6.0-1.dsc

The repo is hosted on Salsa: https://salsa.debian.org/ItzSwirlz-guest/nemo-
pastebin

This closes ITP bug #973321: https://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=973321

Changes for the initial release:

 nemo-pastebin (4.6.0-1) experimental; urgency=medium
 .
   * Initial release. (Closes: #973321)

Regards,
--
  Joshua Peisach



-- System Information:
Debian Release: bullseye/sid
  APT prefers groovy-updates
  APT policy: (500, 'groovy-updates'), (500, 'groovy-security'), (500, 'groovy')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.8.0-25-generic (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#973501: RFS: nemo-media-columns/4.6.0-1 [ITP] -- Nemo Extension to display music/EXIF and PDF metadata

2020-10-31 Thread Joshua Peisach
Package: sponsorship-requests
Severity: wishlist
X-Debbugs-Cc: itzswirlz2...@outlook.com

Dear mentors,

I am looking for a sponsor for my package "nemo-media-columns":

 * Package name: nemo-media-columns
   Version : 4.6.0-1
   Upstream Author : Clement Lefebvre 
 * URL : https://community.linuxmint.com/software/view/nemo-media-
columns
 * License : GPL-3+
 * Vcs : https://salsa.debian.org/ItzSwirlz-guest/nemo-media-
columns
   Section : utils

It builds those binary packages:

  nemo-media-columns - Nemo Extension to display music/EXIF and PDF metadata

To access further information about this package, please visit the following
URL:

  https://mentors.debian.net/package/nemo-media-columns/

Alternatively, one can download the package with dget using this command:

  dget -x https://mentors.debian.net/debian/pool/main/n/nemo-media-
columns/nemo-media-columns_4.6.0-1.dsc

This is hosted on Salsa: https://salsa.debian.org/ItzSwirlz-guest/nemo-media-
columns

This closes ITP Bug #972984): https://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=972984

Changes for the initial release:

 nemo-media-columns (4.6.0-1) experimental; urgency=medium
 .
   * Initial release. (Closes: #972984)

Regards,
--
  Joshua Peisach



-- System Information:
Debian Release: bullseye/sid
  APT prefers groovy-updates
  APT policy: (500, 'groovy-updates'), (500, 'groovy-security'), (500, 'groovy')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.8.0-25-generic (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#973500: RFS: nemo-image-converter/4.6.0-1 [ITP] -- nemo extension to mass resize or rotate images

2020-10-31 Thread Joshua Peisach
Package: sponsorship-requests
Severity: wishlist
X-Debbugs-Cc: itzswirlz2...@outlook.com

Dear mentors,

I am looking for a sponsor for my package "nemo-image-converter":

 * Package name: nemo-image-converter
   Version : 4.6.0-1
   Upstream Author : Clement Lefebvre 
 * URL : https://community.linuxmint.com/software/view/nemo-image-
converter
 * License : GPL-2+
 * Vcs : https://salsa.debian.org/ItzSwirlz-guest/nemo-image-
converter
   Section : utils

It builds those binary packages:

  nemo-image-converter - nemo extension to mass resize or rotate images

To access further information about this package, please visit the following
URL:

  https://mentors.debian.net/package/nemo-image-converter/

Alternatively, one can download the package with dget using this command:

  dget -x https://mentors.debian.net/debian/pool/main/n/nemo-image-
converter/nemo-image-converter_4.6.0-1.dsc

This repo is hosted on salsa: https://salsa.debian.org/ItzSwirlz-guest/nemo-
image-converter

This closes ITP Bug 972367: https://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=972367

Changes for the initial release:

 nemo-image-converter (4.6.0-1) experimental; urgency=medium
 .
   * Initial release. (Closes: #972367)

Regards,
--
  Joshua Peisach



-- System Information:
Debian Release: bullseye/sid
  APT prefers groovy-updates
  APT policy: (500, 'groovy-updates'), (500, 'groovy-security'), (500, 'groovy')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.8.0-25-generic (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#973498: RFS: nemo-filename-repairer/4.6.0-1 [ITP] -- Nemo extension for filename encoding repair

2020-10-31 Thread Joshua Peisach
Package: sponsorship-requests
Severity: wishlist
X-Debbugs-Cc: itzswirlz2...@outlook.com

Dear mentors,

I am looking for a sponsor for my package "nemo-filename-repairer":

 * Package name: nemo-filename-repairer
   Version : 4.6.0-1
   Upstream Author : Clement Lefebvre , Choe Hwanjin

 * URL : https://community.linuxmint.com/software/view/nemo-
filename-repairer
 * License : GPL-1
 * Vcs : https://salsa.debian.org/ItzSwirlz-guest/nemo-filename-
repairer
   Section : utils

It builds those binary packages:

  nemo-filename-repairer - Nemo extension for filename encoding repair

To access further information about this package, please visit the following
URL:

  https://mentors.debian.net/package/nemo-filename-repairer/

Alternatively, one can download the package with dget using this command:

  dget -x https://mentors.debian.net/debian/pool/main/n/nemo-filename-
repairer/nemo-filename-repairer_4.6.0-1.dsc

If you need, the repo is also hosted on Salsa:
https://salsa.debian.org/ItzSwirlz-guest/nemo-filename-repairer

This bug closes: #973466: https://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=973466

Changes for the initial release:

 nemo-filename-repairer (4.6.0-1) experimental; urgency=medium
 .
   * Initial release. (Closes: #973466)

Regards,
--
  Joshua Peisach



-- System Information:
Debian Release: bullseye/sid
  APT prefers groovy-updates
  APT policy: (500, 'groovy-updates'), (500, 'groovy-security'), (500, 'groovy')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.8.0-25-generic (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#973466: ITP: nemo-filename-repairer -- Nemo extension for filename encoding repair

2020-10-30 Thread Joshua Peisach
Package: wnpp
Severity: wishlist
Owner: Joshua Peisach 
X-Debbugs-Cc: debian-de...@lists.debian.org, itzswirlz2...@outlook.com

* Package name: nemo-filename-repairer
  Version : 4.6.0
  Upstream Author : Choe Hwanjin 
* URL : https://github.com/linuxmint/nemo-
extensions/tree/master/nemo-repairer
* License : GPL-2
  Programming Lang: C
  Description : Nemo extension for filename encoding repair

 This is a Nemo extension which repairs filename which uses wrong
 encoding in Nemo. This extension provides the context menu for any
 file whose filename uses wrong encoding, so that you cannot read the
 filename in Nemo.
 .
 You can find a candidate for filename in context menu or submenu.
 This extension also provides a decoded name for URL encoded filename.


I will maintain this by myself until I can hopefully get it into cinnamon-team.



Bug#973321: ITP: nemo-pastebin -- Nemo extension to send files to a pastebin

2020-10-28 Thread Joshua Peisach
Package: wnpp
Severity: wishlist
Owner: Joshua Peisach 
X-Debbugs-Cc: debian-de...@lists.debian.org, itzswirlz2...@outlook.com

* Package name: nemo-pastebin
  Version : 4.6.0
  Upstream Author : Clement Lefebvre 
* URL : https://community.linuxmint.com/software/view/nemo-
pastebin, https://github.com/linuxmint/nemo-extensions/blob/master/nemo-
pastebin
* License : GPL-2+
  Programming Lang: Python
  Description : Nemo extension to send files to a pastebin

 nemo-pastebin is a Nemo extension written in Python, which
 allows users to upload text-only files to a pastebin service just
 by right-clicking on them.
 .
 After sending the files, a notification will be shown and the paste
 URL copied into the clipboard.
 .
 Users can also customize the extension's behaviour just by using
 nemo-pastebin-configurator, an easy-to-use configuration tool.


I plan to maintain this by myself until I can hopefully get it into cinnamon-
team.



Bug#972984: ITP: nemo-media-columns -- Nemo Extension to display music/EXIF and PDF metadata

2020-10-26 Thread Joshua Peisach
Package: wnpp
Severity: wishlist
Owner: Joshua Peisach 
X-Debbugs-Cc: debian-de...@lists.debian.org, itzswirlz2...@outlook.com

* Package name: nemo-media-columns
  Version : 4.6.0
  Upstream Author : Clement Lefebvre 
* URL : https://github.com/linuxmint/nemo-
extensions/tree/master/nemo-media-columns
* License : GPL-3+
  Programming Lang: Python
  Description : Nemo Extension to display music/EXIF and PDF metadata

A Nemo extension to display music/EXIF and PDF metadata info
in the Nemo List View.

This package enhances the Nemo file manager.
I will maintain this by myself before I hopefully get it into cinnamon-team.



Bug#972367: ITP: nemo-image-converter -- nemo extension to mass resize or rotate images

2020-10-16 Thread Joshua Peisach
Package: wnpp
Severity: wishlist
Owner: Joshua Peisach 

* Package name: nemo-image-converter
  Version : 4.6.0
  Upstream Author : Julien Lavergne 
* URL : https://github.com/linuxmint/nemo-
extensions/tree/master/nemo-image-converter
* License : GPL-2+
  Programming Lang: C
  Description : nemo extension to mass resize or rotate images

This package adds a "Resize Images..." menu item to
the context menu of all images. This opens a dialog
where you set the desired image size and file name.
A click on "Resize" finally resizes the image(s)
using ImageMagick's convert tool.

I will maintain this by myself and then hopefully move it into cinnamon-team



Bug#971971: ITP: nemo-audio-tab -- Nemo extension to view audio tag information from the file manager's properties tab

2020-10-10 Thread Joshua Peisach
Package: wnpp
Severity: wishlist
Owner: Joshua Peisach 

* Package name: nemo-audio-tab
  Version : 4.6.0
  Upstream Author : Clement Lefebvre 
* URL : https://community.linuxmint.com/software/view/nemo-audio-
tab
* License : GPL-3+
  Programming Lang: Python
  Description : Nemo extension to view audio tag information from the file
manager's properties tab

No long description provided upstream.

This enhances Nemo (is a nemo extension), and will be maintained by myself
here:
https://salsa.debian.org/ItzSwirlz-guest/nemo-audio-tab

until it can be moved into cinnamon-team.



Bug#971921: ITP: nemo-terminal -- Nemo extension to enable an embedded terminal

2020-10-09 Thread Joshua Peisach
Package: wnpp
Severity: wishlist
Owner: Joshua Peisach 

* Package name: nemo-terminal
  Version : 4.6.0
  Upstream Author : Clement Lefebvre 
* URL : https://github.com/linuxmint/nemo-
extensions/blob/master/nemo-terminal,
https://community.linuxmint.com/software/view/nemo-terminal
* License : GPL-3+
  Programming Lang: Python
  Description : Nemo extension to enable an embedded terminal

 Nemo Terminal is an embedded terminal for Nemo, the Cinnamon file manager.
 It embeds a terminal pane into Nemo that is accessible by hotkey (default F4)
 and automatically follows the currently active directory in Nemo.

I plan to maintain this myself and hopefully get this into cinnamon-team.

During development, the repo will be at:
https://salsa.debian.org/ItzSwirlz-guest/nemo-terminal



Bug#971681: r-cran-openmx regression on arm, will not migrate to testing due to failing autopkgtests

2020-10-06 Thread Joshua N Pritikin
On Tue, Oct 06, 2020 at 04:07:59PM +0200, Andreas Tille wrote:
> While I could include this as a patch I wonder whether you plan to do a
> new release featuring this patch in the next couple of days.  If this is
> the case I would wait for the new release with an upload to Debian.

Prior to the next release, we'd like to address the failures on armhf as 
well. However, we don't have experience debugging on the armhf 
architecture. I anticipate that it will take us a while to get up to 
speed. Hence, it may be weeks before the next release rather than days.

Thank you



Bug#971681: r-cran-openmx regression on arm, will not migrate to testing due to failing autopkgtests

2020-10-06 Thread Joshua N Pritikin
On Tue, Oct 06, 2020 at 08:06:22AM +0200, Andreas Tille wrote:
> the version 2.18.1 of the openmx CRAN package that was build for Debian
> shows a test suite error on arm64 architecture.  Here is an extract of
> the full test log[1] (if you want to inspect the full log I'd recommend
> to seek for some strings you can find below quite at the end):

This is fixed by
https://github.com/OpenMx/OpenMx/commit/2c0deff425365302ede4ac12d5a4222c167a49bb



Bug#925466: Progress Check

2020-09-28 Thread ItzSwirlz Joshua Peisach
1) Shouldn't this be called golang-github-fyneio-fyne or something that has the 
github in it?

2) Where is the packaging being worked on?

3) Is there an upstream GitHub issue for this?


Bug#970997: RFS: cinnamon-dev-tools/4.6.0-1 [ITP] -- Tools for Cinnamon Developers

2020-09-25 Thread Joshua Peisach
Package: sponsorship-requests
Severity: wishlist
Tags: patch

Dear mentors,

I am looking for a sponsor for my package "cinnamon-dev-tools":

 * Package name: cinnamon-dev-tools
   Version : 4.6.0-1
   Upstream Author : Joshua Peisach 
 * URL : https://github.com/ItzSwirlz/cinnamon-dev-tools
 * License : GPL-3+
 * Vcs : https://github.com/ItzSwirlz/cinnamon-dev-tools
   Section : admin

It builds those binary packages:

  cinnamon-dev-tools - Tools for Cinnamon Developers

To access further information about this package, please visit the following
URL:

  https://mentors.debian.net/package/cinnamon-dev-tools/

Alternatively, one can download the package with dget using this command:

  dget -x https://mentors.debian.net/debian/pool/main/c/cinnamon-dev-
tools/cinnamon-dev-tools_4.6.0-1.dsc

All of the above and mre information can be accessed through Salsa and on the
upstream GitHub:

Salsa: https://salsa.debian.org/ItzSwirlz-guest/cinnamon-dev-tools

GitHub: https://github.com/ItzSwirlz/cinnamon-dev-tools

Changes for the initial release:

 cinnamon-dev-tools (4.6.0-1) testing; urgency=medium
 .
   * Initial release. (Closes: #970996)

Regards,
--
  Joshua Peisach



-- System Information:
Debian Release: bullseye/sid
  APT prefers focal-updates
  APT policy: (500, 'focal-updates'), (500, 'focal-security'), (500, 'focal'), 
(100, 'focal-backports')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.4.0-47-generic (SMP w/4 CPU cores)
Kernel taint flags: TAINT_OOT_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



Bug#969489: systemd: systemctl can hang up waiting for device nodes that are already mounted

2020-09-04 Thread Joshua Hudson
I'd really rather not run systems at all but pulseaudio is just too broken
now.

On Friday, September 4, 2020, Joshua Hudson  wrote:

> I'm not convinced it's dmraid because udev reports the nodes up. It looks
> like systems only thinks the first device name on the list is alive.
> Unfortunately that name isn't stable across boots.
>
> On Fri, Sep 4, 2020, 12:58 PM Michael Biebl  wrote:
>
>> On Thu, 3 Sep 2020 16:06:28 -0700 Joshua Hudson 
>> wrote:
>> > Yeah dmraid's still in use. Is there a way to just get rid of all
>> > those device units because they don't do anything right now except
>> > cause problems? I've modified the boot order so systemd sees
>> > everything already mounted.
>>
>> My recommendation would be to get rid of dmraid.
>> It's dead upstream and unmaintained in Debian as well.
>> You are bound to run into problems and it's only getting worse in the
>> future.
>>
>> Michael
>>
>>


Bug#969489: systemd: systemctl can hang up waiting for device nodes that are already mounted

2020-09-04 Thread Joshua Hudson
I'm not convinced it's dmraid because udev reports the nodes up. It looks
like systems only thinks the first device name on the list is alive.
Unfortunately that name isn't stable across boots.

On Fri, Sep 4, 2020, 12:58 PM Michael Biebl  wrote:

> On Thu, 3 Sep 2020 16:06:28 -0700 Joshua Hudson 
> wrote:
> > Yeah dmraid's still in use. Is there a way to just get rid of all
> > those device units because they don't do anything right now except
> > cause problems? I've modified the boot order so systemd sees
> > everything already mounted.
>
> My recommendation would be to get rid of dmraid.
> It's dead upstream and unmaintained in Debian as well.
> You are bound to run into problems and it's only getting worse in the
> future.
>
> Michael
>
>


Bug#969489: systemd: systemctl can hang up waiting for device nodes that are already mounted

2020-09-03 Thread Joshua Hudson
Yeah dmraid's still in use. Is there a way to just get rid of all
those device units because they don't do anything right now except
cause problems? I've modified the boot order so systemd sees
everything already mounted.

On 9/3/20, Michael Biebl  wrote:
> Am 04.09.2020 um 00:58 schrieb Joshua Hudson:
>> I don't think it's a duplicate. #947806 is getting stuck waiting for
>> dmraid nodes to come up so filesystems can be mounted.
>
> Are you using dmraid?
>
>
> --
> Why is it that all of the instruments seeking intelligent life in the
> universe are pointed away from Earth?
>
>



Bug#969489: systemd: systemctl can hang up waiting for device nodes that are already mounted

2020-09-03 Thread Joshua Hudson
I don't think it's a duplicate. #947806 is getting stuck waiting for
dmraid nodes to come up so filesystems can be mounted.

This #969489 is something took a dependency on an implicit unit that
probably shouldn't have a dependency on that unit.

On 9/3/20, Michael Biebl  wrote:
> Am 04.09.2020 um 00:10 schrieb Joshua Hudson:
>> brw-rw 1 root disk 254, 2 Sep  3 14:51
>> /dev/mapper/isw_cfbejbfeib_Volume12
>>
>> udevadm command output attached.
>>
>> The device isn't dead. It works when accessed directly by name.
>>
>> $ /sbin/swapon
>> NAMETYPE  SIZE USED PRIO
>> /dev/mapper/isw_cfbejbfeib_Volume12 partition  32G   0B   -2
>>
>
> Duplicate of #947806 ?
> Are you still using dmraid?
>
> --
> Why is it that all of the instruments seeking intelligent life in the
> universe are pointed away from Earth?
>
>



Bug#969489: systemd: systemctl can hang up waiting for device nodes that are already mounted

2020-09-03 Thread Joshua Hudson
brw-rw 1 root disk 254, 2 Sep  3 14:51 /dev/mapper/isw_cfbejbfeib_Volume12

udevadm command output attached.

The device isn't dead. It works when accessed directly by name.

$ /sbin/swapon
NAMETYPE  SIZE USED PRIO
/dev/mapper/isw_cfbejbfeib_Volume12 partition  32G   0B   -2


udevadm
Description: Binary data


Bug#969245: cinnamon: Network applet - List of Wireless Networks doesn't refresh properly when clicking the applet logo

2020-08-29 Thread Joshua Peisach
Package: cinnamon
Version: 4.6.7-1
Severity: normal
Tags: patch
X-Debbugs-Cc: itzswirlz2...@outlook.com

Dear Maintainer,

All the information for the bug is here:
https://github.com/linuxmint/cinnamon/issues/9531

When the list of wireless connections is displayed, the list of wireless
connections available don't refresh properly.

A patch here is now available for just that, from this commit:
https://github.com/linuxmint/cinnamon/commit/42960e3

Bug has already been reported and fixed upstream.



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

Kernel: Linux 5.7.0-2-amd64 (SMP w/2 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

Versions of packages cinnamon depends on:
ii  cinnamon-common  4.6.7-1
ii  cinnamon-control-center  4.6.2-2
ii  cinnamon-desktop-data4.6.4-1
ii  cinnamon-screensaver 4.6.0-2
ii  cinnamon-session 4.6.2-1
ii  cinnamon-settings-daemon 4.6.4-1
ii  cjs  4.6.0-2
ii  cups-pk-helper   0.2.6-1+b1
ii  dconf-gsettings-backend [gsettings-backend]  0.36.0-1
ii  gir1.2-accountsservice-1.0   0.6.55-3
ii  gir1.2-caribou-1.0   0.4.21-7
ii  gir1.2-clutter-1.0   1.26.4+dfsg-1
ii  gir1.2-cmenu-3.0 4.6.1-1
ii  gir1.2-cogl-1.0  1.22.8-1
ii  gir1.2-cvc-1.0   4.6.4-1
ii  gir1.2-gdkpixbuf-2.0 2.40.0+dfsg-5
ii  gir1.2-gkbd-3.0  3.26.1-1
ii  gir1.2-glib-2.0  1.64.1-1
ii  gir1.2-gnomedesktop-3.0  3.36.4-1
ii  gir1.2-gtk-3.0   3.24.22-1
ii  gir1.2-gtkclutter-1.01.8.4-4
ii  gir1.2-keybinder-3.0 0.3.2-1+b1
ii  gir1.2-meta-muffin-0.0   4.6.3-1
ii  gir1.2-nemo-3.0  4.6.5-1
ii  gir1.2-nm-1.01.26.2-1
ii  gir1.2-nma-1.0   1.8.30-1
ii  gir1.2-notify-0.70.7.9-1
ii  gir1.2-pango-1.0 1.46.0-2
ii  gir1.2-polkit-1.00.105-29
ii  gir1.2-soup-2.4  2.70.0-1
ii  gir1.2-timezonemap-1.0   0.4.6-2
ii  gir1.2-upowerglib-1.00.99.11-2
ii  gir1.2-xapp-1.0  1.8.9-1
ii  gkbd-capplet 3.26.1-1
ii  gnome-backgrounds3.36.0-1
ii  gnome-themes-extra   3.28-1
ii  gsettings-desktop-schemas3.36.1-1
ii  iso-flags-png-320x2401.0.2-1
ii  libatk-bridge2.0-0   2.34.1-3
ii  libatk1.0-0  2.36.0-2
ii  libc62.31-3
ii  libcairo21.16.0-4
ii  libcinnamon-desktop4 4.6.4-1
ii  libcinnamon-menu-3-0 4.6.1-1
ii  libcjs0  4.6.0-2
ii  libcroco30.6.13-1
ii  libgdk-pixbuf2.0-0   2.40.0+dfsg-5
ii  libgirepository-1.0-11.64.1-1
ii  libgl1   1.3.2-1
ii  libglib2.0-0 2.64.4-1
ii  libglib2.0-bin   2.64.4-1
ii  libgstreamer1.0-01.16.2-2
ii  libgtk-3-0   3.24.22-1
ii  libmuffin0   4.6.3-1
ii  libpango-1.0-0   1.46.0-2
ii  libpangocairo-1.0-0  1.46.0-2
ii  libstartup-notification0 0.12-6
ii  libx11-6 2:1.6.10-3
ii  libxfixes3   1:5.0.3-2
ii  libxml2  2.9.10+dfsg-5+b1
ii  mesa-utils   8.4.0-1+b1
ii  muffin   4.6.3-1
ii  nemo 4.6.5-1
ii  network-manager-gnome1.18.0-1
ii  policykit-1-gnome0.105-7
ii  python3  3.8.2-3
ii  python3-dbus 1.2.16-3
ii  python3-distro   1.5.0-1
ii  python3-gi   3.36.0-4
ii  python3-gi-cairo 3.36.0-4
ii  python3-pampy   

Bug#963833: The sneaky deets

2020-06-28 Thread ItzSwirlz Joshua Peisach
Okay-so the option IS --disable-Werror, but you can't invoke it via 
dh_auto_configure.

dh_autoreconf is not responsible for this as the file is in ./configure.

dh_auto_configure automatically adds flags that I copied over using verbose and 
then added -disable-Werror flag in. This is what the new debian/rules 
override_dh_auto_configure looks like:

override_dh_auto_configure:
./configure --build=x86_64-linux-gnu \
--prefix=/usr \
--includedir=\${prefix}/include \
--mandir=\${prefix}/share/man \
--infodir=\${prefix}/share/info \
--sysconfdir=/etc --localstatedir=/var \
--disable-silent-rules \
--libdir=\${prefix}/lib/x86_64-linux-gnu \
--libexecdir=\${prefix}/lib/x86_64-linux-gnu \
--runstatedir=/run \
--disable-maintainer-mode \
--disable-dependency-tracking \
--disable-Werror

The diff will add that and update dependencies.


Bug#963833: dh_auto_build: libglib update breaks build (GParameters)

2020-06-27 Thread Joshua Peisach
Package: cjs
Version: 4.4.0-4
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)

Building on: Ubuntu Focal 20.04. Also applies on unstable branch 20.10 Groovy

It looks like there is a new update in libglib2.0, or a new update that
breaks/deprecates GParamaters.

This may be because -Werror is still applied in the compilation-therefore this
could be overwritten by removing it but I don't think it's a smart choice.

I compiled upstream and it went flawlessly. I didn't look through anything to
see if they removed -Werror as a whole but it still exists in configure.ac

Tomorrow I will probably do deeper comparisons and see if a .patch is needed to
fit with someone missing from upstream.

For now, here is the output of dh_auto_build:

libtool: compile:  g++ -std=gnu++11 -DHAVE_CONFIG_H -I. -DG_LOG_DOMAIN=\"Cjs\"
-I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -pthread
-include /usr/include/mozjs-52/js/RequiredDefines.h -I/usr/include/gobject-
introspection-1.0 -I/usr/include/libmount -I/usr/include/blkid
-I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include
-I/usr/include/mozjs-52 -DGJS_TOP_SRCDIR=\".\" -DGJS_TOP_BUILDDIR=\".\"
-DGJS_JS_DIR=\"/usr/share/cjs-1.0\" -DPKGLIBDIR=\"/usr/lib/x86_64-linux-
gnu/cjs\" -I./gi -DGJS_COMPILATION -pthread -I/usr/include/gtk-3.0
-I/usr/include/at-spi2-atk/2.0 -I/usr/include/at-spi-2.0
-I/usr/include/dbus-1.0 -I/usr/lib/x86_64-linux-gnu/dbus-1.0/include
-I/usr/include/gtk-3.0 -I/usr/include/gio-unix-2.0 -I/usr/include/cairo
-I/usr/include/pango-1.0 -I/usr/include/fribidi -I/usr/include/harfbuzz
-I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pixman-1
-I/usr/include/uuid -I/usr/include/freetype2 -I/usr/include/libpng16
-I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libmount -I/usr/include/blkid
-I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -Wdate-
time -D_FORTIFY_SOURCE=2 -fno-strict-aliasing -Wall -Wextra -Wundef -Wwrite-
strings -Wpointer-arith -Wmissing-declarations -Wredundant-decls -Wno-unused-
parameter -Wno-missing-field-initializers -Wformat=2 -Wcast-align -Wformat-
nonliteral -Wformat-security -Wsign-compare -Wstrict-aliasing -Wshadow -Winline
-Wpacked -Wmissing-format-attribute -Wmissing-noreturn -Winit-self -Wmissing-
include-dirs -Wunused-but-set-variable -Warray-bounds -Wreturn-type -Wno-
overloaded-virtual -Wswitch-enum -Wswitch-default -Werror -Wno-suggest-
attribute=format -Wno-error=unused-parameter -Wno-error=missing-field-
initializers -Wno-error=overloaded-virtual -g -O2 -fdebug-prefix-
map=/home/jpeisach/Desktop/cjs-4.6.0=. -fstack-protector-strong -Wformat
-Werror=format-security -c gi/object.cpp  -fPIC -DPIC -o gi/.libs/libcjs_la-
object.o

gi/object.cpp:246:56: error: ‘GParameter’ is deprecated [-Werror=deprecated-
declarations]
  246 |boolconstructing)
  |^
In file included from /usr/include/glib-2.0/gobject/gobject.h:26,
 from /usr/include/glib-2.0/gobject/gbinding.h:29,
 from /usr/include/glib-2.0/glib-object.h:22,
 from gi/object.h:29,
 from gi/object.cpp:34:
/usr/include/glib-2.0/gobject/gparam.h:194:28: note: declared here
  194 | typedef struct _GParameter GParameter GLIB_DEPRECATED_TYPE_IN_2_54;
  |^~
gi/object.cpp: In function ‘bool set_g_param_from_prop(JSContext*,
ObjectInstance*, const char*, bool&, JS::HandleValue, JS::ObjectOpResult&)’:
gi/object.cpp:487:16: error: ‘GParameter’ is deprecated [-Werror=deprecated-
declarations]
  487 | GParameter param = { NULL, { 0, }};
  |^
In file included from /usr/include/glib-2.0/gobject/gobject.h:26,
 from /usr/include/glib-2.0/gobject/gbinding.h:29,
 from /usr/include/glib-2.0/glib-object.h:22,
 from gi/object.h:29,
 from gi/object.cpp:34:
/usr/include/glib-2.0/gobject/gparam.h:194:28: note: declared here
  194 | typedef struct _GParameter GParameter GLIB_DEPRECATED_TYPE_IN_2_54;
  |^~
gi/object.cpp: At global scope:
gi/object.cpp:963:51: error: ‘GParameter’ is deprecated [-Werror=deprecated-
declarations]
  963 |   std::vector&
gparams)
  |   ^~
In file included from /usr/include/glib-2.0/gobject/gobject.h:26,
 from /usr/include/glib-2.0/gobject/gbinding.h:29,
 from /usr/include/glib-2.0/glib-object.h:22,
 from gi/object.h:29,
 from gi/object.cpp:34:
/usr/include/glib-2.0/gobject/gparam.h:194:28: note: declared here
  194 | typedef struct _GParameter GParameter GLIB_DEPRECATED_TYPE_IN_2_54;
  |^~
gi/object.cpp: In function ‘bool

Bug#962926: Images of aptitude screens are illegible due to being scaled to browser width

2020-06-15 Thread Joshua C. Lackey
Package: aptitude-doc-en
Version: 0.8.13-1

All of the screenshots are illegible because a width="100%" property
is set in each  tag, causing them to be stretched and introducing
significant aliasing. Resizing the browser window to a smaller size
does not help much. Due to the low resolution of the images (484x316)
and small size of the text, even minimal scaling causes blurring and
aliasing. The text, though small, is completely clear and legible when
the images are rendered at their native resolution.

This is the case in the HTML help installed to
/usr/share/doc/aptitude/html/en by the aptitude-doc-en package, as
well as the online version.

Please view for an example:
https://www.debian.org/doc/manuals/aptitude/ch01s01s01.en.html

I suggest removing the width='100%' property from each of the the
 tags in the DocBook XML source (/doc/en/aptitude.xml) or
adding an img selector in the CSS stylesheet (/doc/aptitude.css) with
a width:auto property, which will override the the HTML  tags.



Bug#946974: systemd: hang waiting for VM ethernet card to come online

2020-04-26 Thread Joshua Hudson
I never had both at the same time. I toggled of auto eth0 when I put
the line into /etc/rc.local.

> If so, what happens if you just disable rc.local?

No network connection, and "auto eth0" causes 5 mins delay at boot.

On 4/26/20, Guus Sliepen  wrote:
> On Sun, Apr 26, 2020 at 01:09:06PM -0700, Joshua Hudson wrote:
>
>> I suspect it might be confusing since I filed two different eth0-related
>> bugs.
>>
>> In this particular instance, the DHCP server was live, and I could
>> have omitted the & from the line in rc.local and it would have come up
>> only a couple of seconds slower.
>
> Just to be sure, did you have both the /etc/rc.local file trying to run
> dhclient AND /etc/network/interfaces set to automatically bring up eth0?
> If so, what happens if you just disable rc.local?
>
> --
> Met vriendelijke groet / with kind regards,
>   Guus Sliepen 
>



Bug#946974: systemd: hang waiting for VM ethernet card to come online

2020-04-26 Thread Joshua Hudson
I suspect it might be confusing since I filed two different eth0-related bugs.

In this particular instance, the DHCP server was live, and I could
have omitted the & from the line in rc.local and it would have come up
only a couple of seconds slower.



Bug#955594: cinnamon-common: System info looks for non-existant attribute 'linux_distribution', not allowing info to show

2020-04-02 Thread Joshua Peisach
Package: cinnamon-common
Version: 4.4.8-2
Severity: normal
Tags: upstream

Dear Maintainer,

Was testing my Ubuntu Cinnamon Remix. Testers reported "System Info" not
working. Ran 'cinnamon-settings' in terminal and SystemInfo returned: "moduel
'platform' has no attribtue 'linux-distribution'. I reported the bug on
Ubuntu's Launchpad (bugs.launchpad.net/ubuntu/+source/cinnamon/+bug/1869565)
and people have found this to be in all Ubuntu, and I have found in unstable
(bullseye) debian. Basically, system info is looking for 'linux_distribution'
but doesn't exist, not allowing it to work. Here is some additional info, you
can find the whole scoop on the launchpad:

Traceback (most recent call last):
  File "/usr/share/cinnamon/cinnamon-settings/cinnamon-settings.py", line 670,
in button_press
self.side_view_nav(widget, None, category)
  File "/usr/share/cinnamon/cinnamon-settings/cinnamon-settings.py", line 174,
in side_view_nav
self.go_to_sidepage(cat, filtered_path, user_action=True)
  File "/usr/share/cinnamon/cinnamon-settings/cinnamon-settings.py", line 189,
in go_to_sidepage
sidePage.build()
  File "/usr/share/cinnamon/cinnamon-settings/bin/SettingsWidgets.py", line
213, in build
self.module.on_module_selected()
  File "/usr/share/cinnamon/cinnamon-settings/modules/cs_info.py", line 149, in
on_module_selected
infos = createSystemInfos()
  File "/usr/share/cinnamon/cinnamon-settings/modules/cs_info.py", line 108, in
createSystemInfos
s = '%s (%s)' % (' '.join(platform.linux_distribution()), arch)
AttributeError: module 'platform' has no attribute 'linux_distribution'

ProblemType: crash
DistroRelease: Found on Debian and on Ubuntu 20.04.
Package: cinnamon-common 4.4.8-2
Arch: amd64
File: /usr/share/cinnamon/cinnamon-settings/cinnamon-settings.py
Source Package: Cinnamon
Kernel: 5.0.4-4
Lang/Locale: English (US)

Can't find any other information that'd be somewhat helpful except cinnamon is
base-and these link to cinnamon-control-center and cinnamon-settings-daemon.



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

Kernel: Linux 5.4.0-4-amd64 (SMP w/1 CPU core)
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 cinnamon-common depends on:
ii  dconf-gsettings-backend [gsettings-backend]  0.36.0-1
ii  gettext  0.19.8.1-10
ii  gir1.2-cinnamondesktop-3.0   4.4.1-3
ii  gir1.2-meta-muffin-0.0   4.4.2-3
ii  libglib2.0-bin   2.64.1-1
ii  python3  3.8.2-2
ii  python3-xapp 1.8.1-2
ii  xdg-utils1.1.3-2

cinnamon-common recommends no packages.

cinnamon-common suggests no packages.

-- no debconf information



Bug#950748: bootparamd does not receive broadcast messages unless rpcbind is run with -r

2020-02-05 Thread Joshua Honeycutt

Package: bootparamd
Version: 0.17-10
Severity: normal

Dear Maintainer,

I was attempting to use rarpd/tftp/bootparamd/nfs to do a solaris 
jumpstart installation. When running "rpc.bootparamd -d" I could see 
requests directly to the host (testing via callbootd), but requests
sent broadcast (both 192.168.1.255/24 and 255.255.255.255) never reached 
bootparamd.


I found adding the remote call option (-r) in /etc/default/rpcbind 
caused bootparamd to start seeing broadcast messages.


I see this behavior is documented in /usr/share/doc/rpcbind/README.Debian
but I'm wondering if you think there should be a information in
rpc.bootparamd(8) or other docs to indicate broadcasts may be ignored
by default because it's not obvious rpcbind may be involved.

-- System Information:
Debian Release: 10.2
 APT prefers stable-debug
 APT policy: (500, 'stable-debug'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.19.0-6-amd64 (SMP w/12 CPU cores)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, 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 /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages bootparamd depends on:
ii  libc6  2.28-10
ii  rpcbind [portmap]  1.2.5-0.3+deb10u1

bootparamd recommends no packages.

bootparamd suggests no packages.



Bug#947806: systemd doesn't like my raid, times out waiting for online partitions to come online, and can't continue boot

2020-01-12 Thread Joshua Hudson
Hey I got lucky with a google search and found what would be a dupe if
it were ever finished.
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=805821

Somebody else managed to track the problem down.

For some reason systemd is only watching for /dev/dm-* rather than the
long dmraid device names. This is the equivalent of watching for
/dev/sda1 instead of the UUID.  Nikita Youshchenko:

> This way boot is ok (i.e. no delays and swap is enabled). But this is ugly 
> and unreliable.

This does work when there's only one raid array in the OS, which is
most of the time. These are two real devices (no symlinks) with the
same major and minor numbers.



Bug#947806: systemd doesn't like my raid, times out waiting for online partitions to come online, and can't continue boot

2020-01-12 Thread Joshua Hudson
I double-checked with init=/bin/sh. All the devices already exist in
/dev/mapper before /linuxrc shuts down the initrd copy of udev.
systemd will never see the activation of a udev device because that's
already done. They're all active.



Bug#947806: systemd doesn't like my raid, times out waiting for online partitions to come online, and can't continue boot

2020-01-12 Thread Joshua Hudson
That turned out to be really easy to track down. The reason you aren't
getting any notification of the raid array being activated is it was
already activated in initrd. It will not be activated a second time.

dmraid has some interesting principles in play here.

1) dmraid has its own idea of persistent, path-independent names of devices.
2) dmraid is incompatible with UUID= or LABEL=; all users of dmraid
must have the raid device names in /etc/fstab and on the kernel
command line. GRUB_LINUX_DISABLE_UUID *must* be used.
3) Under normal operation, dmraid is included in initrd as soon as it
is installed on the system.
4) If dmraid is installed in initrd, udev will discover the dmraid
devices before / is mounted. If udev discovers the dmraid devices, it
will start the system.
5) Redundant activations are not possible.

So the effect of all this is really simple. systemd can just assume
that a dmraid device under /dev/mapper is active if the device node
exists at all, and on any reasonable system it doesn't even need to
poll the device path; it can check *once* and know the success or
failure immediately.



Bug#947811: systemd: don't check *mounted* filesystems by default

2020-01-12 Thread Joshua Hudson
> If you want to fsck/mount your partitions manually via a custom script
that is run before init, then I would set passno to 0.

I've since masked the job that systemd uses to run fsck. It's still a
bug because if somebody forgets and leaves a filesystem mounted
read-write in the emergency shell (fixing anything other than fsck
problems in the emergency shell usually requires mounting things
read-write), the same problem happens and no custom script is
involved.



Bug#947806: systemd doesn't like my raid, times out waiting for online partitions to come online, and can't continue boot

2020-01-12 Thread Joshua Hudson
>> Dec 31 08:27:23 nova dmraid-activate[554]: ERROR: Cannot retrieve RAID
set information for isw_cfbejbfeib_Volume1
> Have you further investigated those error messages?

I have now investigated and it's clearly spurious.

udev tries to run the following commands:

/sbin/dmraid-activate /dev/sda
/sbin/dmraid-activate /dev/sdb
/sbin/dmraid-activate sda
/sbin/dmraid-activate sdb

The first two are correct and succeed. The second two are not correct
and fail. The failure results in log spam.

> Have you tried with mdadm instead?

mdadm doesn't recognize the raid descriptor.

> udevadm info /dev/mapper/isw_cfbejbfeib_Volume14

output of this command for this device and all similar devices attached.
P: /devices/virtual/block/dm-0
N: dm-0
L: 0
S: disk/by-id/dm-uuid-DMRAID-isw_cfbejbfeib_Volume1
S: disk/by-id/dm-name-isw_cfbejbfeib_Volume1
S: android0
E: DEVPATH=/devices/virtual/block/dm-0
E: DEVNAME=/dev/dm-0
E: DEVTYPE=disk
E: MAJOR=254
E: MINOR=0
E: SUBSYSTEM=block
E: USEC_INITIALIZED=1701034
E: DM_UDEV_DISABLE_DM_RULES_FLAG=1
E: DM_UDEV_DISABLE_SUBSYSTEM_RULES_FLAG=1
E: DM_UDEV_PRIMARY_SOURCE_FLAG=1
E: DM_UDEV_RULES=1
E: DM_UDEV_RULES_VSN=2
E: DM_ACTIVATION=1
E: DM_NAME=isw_cfbejbfeib_Volume1
E: DM_UUID=DMRAID-isw_cfbejbfeib_Volume1
E: DM_SUSPENDED=0
E: ID_PART_TABLE_UUID=373c9bd5
E: ID_PART_TABLE_TYPE=dos
E: DEVLINKS=/dev/disk/by-id/dm-uuid-DMRAID-isw_cfbejbfeib_Volume1 /dev/disk/by-id/dm-name-isw_cfbejbfeib_Volume1 /dev/android0
E: TAGS=:systemd:

P: /devices/virtual/block/dm-1
N: dm-1
L: 0
S: android1
S: disk/by-id/dm-uuid-DMRAID-isw_cfbejbfeib_Volume11
S: disk/by-id/dm-name-isw_cfbejbfeib_Volume11
S: disk/by-uuid/d847c628-aa10-4bef-92b6-72ebacc07d7b
E: DEVPATH=/devices/virtual/block/dm-1
E: DEVNAME=/dev/dm-1
E: DEVTYPE=disk
E: MAJOR=254
E: MINOR=1
E: SUBSYSTEM=block
E: USEC_INITIALIZED=1707100
E: DM_UDEV_DISABLE_DM_RULES_FLAG=1
E: DM_UDEV_DISABLE_SUBSYSTEM_RULES_FLAG=1
E: DM_UDEV_PRIMARY_SOURCE_FLAG=1
E: DM_UDEV_RULES=1
E: DM_UDEV_RULES_VSN=2
E: DM_ACTIVATION=1
E: DM_NAME=isw_cfbejbfeib_Volume11
E: DM_UUID=DMRAID-isw_cfbejbfeib_Volume11
E: DM_SUSPENDED=0
E: ID_FS_UUID=d847c628-aa10-4bef-92b6-72ebacc07d7b
E: ID_FS_UUID_ENC=d847c628-aa10-4bef-92b6-72ebacc07d7b
E: ID_FS_VERSION=1.0
E: ID_FS_TYPE=ext3
E: ID_FS_USAGE=filesystem
E: DEVLINKS=/dev/android1 /dev/disk/by-id/dm-uuid-DMRAID-isw_cfbejbfeib_Volume11 /dev/disk/by-id/dm-name-isw_cfbejbfeib_Volume11 /dev/disk/by-uuid/d847c628-aa10-4bef-92b6-72ebacc07d7b
E: TAGS=:systemd:

P: /devices/virtual/block/dm-2
N: dm-2
L: 0
S: disk/by-id/dm-name-isw_cfbejbfeib_Volume12
S: disk/by-id/dm-uuid-DMRAID-isw_cfbejbfeib_Volume12
S: disk/by-uuid/baad791f-0ba2-4c87-92a1-0cd0ef4f7301
S: android2
E: DEVPATH=/devices/virtual/block/dm-2
E: DEVNAME=/dev/dm-2
E: DEVTYPE=disk
E: MAJOR=254
E: MINOR=2
E: SUBSYSTEM=block
E: USEC_INITIALIZED=1707179
E: DM_UDEV_DISABLE_DM_RULES_FLAG=1
E: DM_UDEV_DISABLE_SUBSYSTEM_RULES_FLAG=1
E: DM_UDEV_PRIMARY_SOURCE_FLAG=1
E: DM_UDEV_RULES=1
E: DM_UDEV_RULES_VSN=2
E: DM_ACTIVATION=1
E: DM_NAME=isw_cfbejbfeib_Volume12
E: DM_UUID=DMRAID-isw_cfbejbfeib_Volume12
E: DM_SUSPENDED=0
E: ID_FS_UUID=baad791f-0ba2-4c87-92a1-0cd0ef4f7301
E: ID_FS_UUID_ENC=baad791f-0ba2-4c87-92a1-0cd0ef4f7301
E: ID_FS_VERSION=1
E: ID_FS_TYPE=swap
E: ID_FS_USAGE=other
E: DEVLINKS=/dev/disk/by-id/dm-name-isw_cfbejbfeib_Volume12 /dev/disk/by-id/dm-uuid-DMRAID-isw_cfbejbfeib_Volume12 /dev/disk/by-uuid/baad791f-0ba2-4c87-92a1-0cd0ef4f7301 /dev/android2
E: TAGS=:systemd:

P: /devices/virtual/block/dm-3
N: dm-3
L: 0
S: android3
S: disk/by-id/dm-name-isw_cfbejbfeib_Volume13
S: disk/by-id/dm-uuid-DMRAID-isw_cfbejbfeib_Volume13
S: disk/by-uuid/5744b8b7-dcbf-48c4-868e-fb71fa65d456
E: DEVPATH=/devices/virtual/block/dm-3
E: DEVNAME=/dev/dm-3
E: DEVTYPE=disk
E: MAJOR=254
E: MINOR=3
E: SUBSYSTEM=block
E: USEC_INITIALIZED=1707545
E: DM_UDEV_DISABLE_DM_RULES_FLAG=1
E: DM_UDEV_DISABLE_SUBSYSTEM_RULES_FLAG=1
E: DM_UDEV_PRIMARY_SOURCE_FLAG=1
E: DM_UDEV_RULES=1
E: DM_UDEV_RULES_VSN=2
E: DM_ACTIVATION=1
E: DM_NAME=isw_cfbejbfeib_Volume13
E: DM_UUID=DMRAID-isw_cfbejbfeib_Volume13
E: DM_SUSPENDED=0
E: ID_FS_UUID=5744b8b7-dcbf-48c4-868e-fb71fa65d456
E: ID_FS_UUID_ENC=5744b8b7-dcbf-48c4-868e-fb71fa65d456
E: ID_FS_VERSION=1.0
E: ID_FS_TYPE=ext3
E: ID_FS_USAGE=filesystem
E: DEVLINKS=/dev/android3 /dev/disk/by-id/dm-name-isw_cfbejbfeib_Volume13 /dev/disk/by-id/dm-uuid-DMRAID-isw_cfbejbfeib_Volume13 /dev/disk/by-uuid/5744b8b7-dcbf-48c4-868e-fb71fa65d456
E: TAGS=:systemd:

P: /devices/virtual/block/dm-4
N: dm-4
L: 0
S: disk/by-id/dm-uuid-DMRAID-isw_cfbejbfeib_Volume14
S: disk/by-uuid/c03a09e6-ff90-4803-bd7c-78e34e99457e
S: disk/by-id/dm-name-isw_cfbejbfeib_Volume14
S: android4
E: DEVPATH=/devices/virtual/block/dm-4
E: DEVNAME=/dev/dm-4
E: DEVTYPE=disk
E: MAJOR=254
E: MINOR=4
E: SUBSYSTEM=block
E: USEC_INITIALIZED=1708143
E: DM_UDEV_DISABLE_DM_RULES_FLAG=1
E: DM_UDEV_DISABLE_SUBSYSTEM_RULES_FLAG=1
E: DM_UDEV_PRIMARY_SOURCE_FLAG=1
E: DM_UDEV_RULES=1
E: DM_UDEV_RULES_VSN=2
E: DM_ACTIVATION=1
E: 

Bug#947811: systemd: don't check *mounted* filesystems by default

2020-01-12 Thread Joshua Hudson
#need_real_mtab
/dev/mapper/isw_cfbejbfeib_Volume11 / ext3 defaults 0 1
/dev/mapper/isw_cfbejbfeib_Volume12 none swap sw 0 0
none /tmp tmpfs defaults 0 0
/dev/mapper/isw_cfbejbfeib_Volume13 /home ext3 defaults 0 2
/dev/mapper/isw_cfbejbfeib_Volume14 /home/joshua/imagefiles ext3 defaults 0 3
/dev/sr0 /media/cdrom iso9660 noauto,ro,user 0 0
/dev/sr1 /media/cdrom1 iso9660 noauto,ro,user 0 0



Bug#947908: pulseaudio: sound doesn't play on first launch of pulseaudio at login; restarting it always results in working sound but will reoccur on next boot

2020-01-03 Thread Joshua Hudson
> Is there actually a pulseaudio daemon running?

yup.

> Where?

Not sure what this is supposed to mean.

> Is it managed by systemd?

I dunno how starting it at login is supposed to work.

client.conf:

autospawn = no

Ok this makes absolutely no sense at all. The problem went away when I
took ethernet device configuration away from systemd by masking off
all the networking stuff and sticking ifup -a & into /sbin/init. This
does make system boot a _lot_ faster.



Bug#947993: systemd: mysterious timeout /sys/subsystem/net/device/multi/user

2020-01-02 Thread Joshua
Package: systemd
Version: 241-7~deb10u2
Severity: normal

Mysterious timeout booting on multi/user ficticious device


-- Package-specific info:

-- System Information:
Debian Release: 10.2
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.19.0-6-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1), LANGUAGE=en_US 
(charmap=ISO-8859-1)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages systemd depends on:
ii  adduser  3.118
ii  libacl1  2.2.53-4
ii  libapparmor1 2.13.2-10
ii  libaudit11:2.8.4-3
ii  libblkid12.33.1-0.1
ii  libc62.28-10
ii  libcap2  1:2.25-2
ii  libcryptsetup12  2:2.1.0-5+deb10u2
ii  libgcrypt20  1.8.4-5
ii  libgnutls30  3.6.7-4
ii  libgpg-error01.35-1
ii  libidn11 1.33-2.2
ii  libip4tc01.8.2-4
ii  libkmod2 26-1
ii  liblz4-1 1.8.3-1
ii  liblzma5 5.2.4-1
ii  libmount12.33.1-0.1
ii  libpam0g 1.3.1-5
ii  libseccomp2  2.3.3-4
ii  libselinux1  2.8-1+b1
ii  libsystemd0  241-7~deb10u2
ii  mount2.33.1-0.1
ii  util-linux   2.33.1-0.1

Versions of packages systemd recommends:
ii  dbus1.12.16-1
ii  libpam-systemd  241-7~deb10u2

Versions of packages systemd suggests:
ii  policykit-10.105-25
pn  systemd-container  

Versions of packages systemd is related to:
pn  dracut   
ii  initramfs-tools  0.133+deb10u1
ii  udev 241-7~deb10u2

-- Configuration Files:
/etc/systemd/journald.conf changed:
[Journal]
Storage=volatile
ForwardToSyslog=1


-- no debconf information



Bug#947908: pulseaudio: sound doesn't play on first launch of pulseaudio at login; restarting it always results in working sound but will reoccur on next boot

2020-01-02 Thread Joshua Hudson
> Does `journalctl --user-unit pulseaudio.service` have anything to say?

Says "daemon already running" quite a few times.

> You can set the debug flags on daemon.conf to force it to verbose mode.

Spectacular:

E: [pulseaudio] pid.c: Daemon already running.
E: [pulseaudio] main.c: pa_pid_file_create() failed.

Must clear the log file every time.

$ grep -v '^$' /etc/pulse/daemon.conf | grep -v '^;' | grep -v '^#'
$ cat ~/.pulse/daemon.conf

exit-idle-time=-1
log-target=file:/home/joshua/.pulse/daemon.log
log-level=info
kill=yes

and aplay reports:

ALSA lib pcm_dmix.c:1108:(snd_pcm_dmix_open) unable to open slave
aplay: main:828: audio open error: No such file or directory

but writing directly to /dev/audio1 makes some noise



Bug#947908: pulseaudio: sound doesn't play on first launch of pulseaudio at login; restarting it always results in working sound but will reoccur on next boot

2020-01-01 Thread Joshua
Package: pulseaudio
Version: 12.2-4+deb10u1
Severity: normal

After installing systemd, the following problem appeared in pulseaudio:

The first login after boot launches a non-working pulseaudio. Killing and 
restarting pulseaudio results in
a working pulseaudio. It's not a wait for device to initialize problem. It 
doesn't matter how long I stare
at the login screen before logging in.

The normal debug steps are useless as the problem won't recur when pulseaudio 
is not restarted.

-- Package-specific info:
File '/etc/default/pulseaudio' does not exist


-- System Information:
Debian Release: 10.2
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.19.0-6-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1), LANGUAGE=en_US 
(charmap=ISO-8859-1)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages pulseaudio depends on:
ii  adduser  3.118
ii  libasound2   1.1.8-1
ii  libasound2-plugins   1:1.1.8-dmo1
ii  libc62.28-10
ii  libcap2  1:2.25-2
ii  libdbus-1-3  1.12.16-1
ii  libgcc1  1:8.3.0-6
ii  libice6  2:1.0.9-2
ii  libltdl7 2.4.6-9
ii  liborc-0.4-0 1:0.4.28-3.1
ii  libpulse012.2-4+deb10u1
ii  libsm6   2:1.2.3-1
ii  libsndfile1  1.0.28-6
ii  libsoxr0 0.1.2-3
ii  libspeexdsp1 1.2~rc1.2-1+b2
ii  libstdc++6   8.3.0-6
ii  libsystemd0  241-7~deb10u2
ii  libtdb1  1.3.16-2+b1
ii  libudev1 241-7~deb10u2
ii  libwebrtc-audio-processing1  0.3-1
ii  libx11-6 2:1.6.7-1
ii  libx11-xcb1  2:1.6.7-1
ii  libxcb1  1.13.1-2
ii  libxtst6 2:1.2.3-1
ii  lsb-base 10.2019051400
ii  pulseaudio-utils 12.2-4+deb10u1

Versions of packages pulseaudio recommends:
pn  dbus-user-session  
ii  libpam-systemd 241-7~deb10u2
pn  rtkit  

Versions of packages pulseaudio suggests:
pn  paman
pn  paprefs  
ii  pavucontrol  3.0-4
pn  pavumeter
ii  udev 241-7~deb10u2

-- no debconf information
# This file is part of PulseAudio.
#
# PulseAudio is free software; you can redistribute it and/or modify
# it under the terms of the GNU Lesser General Public License as published by
# the Free Software Foundation; either version 2 of the License, or
# (at your option) any later version.
#
# PulseAudio is distributed in the hope that it will be useful, but
# WITHOUT ANY WARRANTY; without even the implied warranty of
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
# General Public License for more details.
#
# You should have received a copy of the GNU Lesser General Public License
# along with PulseAudio; if not, see .

## Configuration file for PulseAudio clients. See pulse-client.conf(5) for
## more information. Default values are commented out.  Use either ; or # for
## commenting.

; default-sink =
; default-source =
; default-server =
; default-dbus-server =

; autospawn = yes
; daemon-binary = /usr/bin/pulseaudio
; extra-arguments = --log-target=syslog

; cookie-file =

; enable-shm = yes
; shm-size-bytes = 0 # setting this 0 will use the system-default, usually 64 
MiB

; auto-connect-localhost = no
; auto-connect-display = no
# This file is part of PulseAudio.
#
# PulseAudio is free software; you can redistribute it and/or modify
# it under the terms of the GNU Lesser General Public License as published by
# the Free Software Foundation; either version 2 of the License, or
# (at your option) any later version.
#
# PulseAudio is distributed in the hope that it will be useful, but
# WITHOUT ANY WARRANTY; without even the implied warranty of
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
# General Public License for more details.
#
# You should have received a copy of the GNU Lesser General Public License
# along with PulseAudio; if not, see .

## Configuration file for the PulseAudio daemon. See pulse-daemon.conf(5) for
## more information. Default values are commented out.  Use either ; or # for
## commenting.

; daemonize = no
; fail = yes
; allow-module-loading = yes
; allow-exit = yes
; use-pid-file = yes
; system-instance = no
; local-server-type = user
; enable-shm = yes
; enable-memfd = yes
; shm-size-bytes = 0 # setting this 0 will use the system-default, usually 64 
MiB
; lock-memory = no
; cpu-limit = no

; high-priority = yes
; nice-level = -11

; realtime-scheduling = yes
; realtime-priority = 5

; exit-idle-time = 20
; scache-idle-time = 20

; dl-search-path = 

  1   2   3   4   5   6   7   8   9   10   >