I can confirm that
copy_exec /lib//liblzma.so.5
in /usr/share/initramfs-tools/hooks/kmod fixes the problem for me.
—Ethan
Package: libuwind8
Version: i386
Severity: normal
X-Debbugs-Cc: deb...@tutamail.com
Dear Maintainer, I can't install the wine package because of dependencies.
ibgstreamer1.0-0:i386 : Depends: libunwind8:i386 but it is not going to be
installed
Error: Unable to correct problems, you have h
Package: gdm3
Version: 47.0-3
Followup-For: Bug #1059245
X-Debbugs-Cc: deb...@tutamail.com
Dear Maintainer,
I just deleted the file /usr/lib/udev/rules.d/61-gdm.rules :D
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
no wayland
Package: gnome
Version: 1:47+3
Severity: normal
X-Debbugs-Cc: deb...@tutamail.com
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
I don't know for sure, but it looks like I've changed from stable to
unstable
Some addtional information :
Rendered page output from browser with older libraries:
+
{
"Version Information": {
"WebKit version": "WebKitGTK 2.42.5 (tarball)",
"Operating system": "Linux 6.7.12-amd64 #1 SMP
Would an fsck even be able to recognize corruption, if metadata were
unaffected? Without file checksumming, can it discern?
Subject: g++-multilib: bullseye & bookworm currently has amd64 support for this
package, add support for aarch64 (64-bit ARM)
Package: g++-multilib
X-Debbugs-Cc: jahway-bug-repo...@proton.me
Severity: wishlist
Dear Maintainer,
* What led up to the situation? Requiring the ability to com
Subject: gcc-multilib: bullseye & bookworm currently has amd64 support for this
package, add support for aarch64 (64-bit ARM)
Package: gcc-multilib
X-Debbugs-Cc: jahway-bug-repo...@proton.me
Severity: wishlist
Dear Maintainer,
* What led up to the situation? Requiring the ability to com
Subject: gcc-multilib: make it available on arm64 architecture (known as
aarch64)
Package: gcc-multilib
X-Debbugs-Cc: jahway-bug-repo...@proton.me
Severity: wishlist
Dear Maintainer,
* What led up to the situation? Unable to compile certain
* software without gcc-multilib library
Subject: g++-multilib: make it available on arm64 architecture (known as
aarch64)
Package: g++-multilib
X-Debbugs-Cc: jahway-bug-repo...@proton.me
Severity: wishlist
Dear Maintainer,
* What led up to the situation? Unable to compile certain
* software without g++-multilib library
22.3.3-1 works here!
But the upstream bug is unanswered still:
https://gitlab.freedesktop.org/mesa/mesa/-/issues/8007.
And there's another guy who did the same to no avail. It's not fixed for
everyone. If we want to fix it for all, why not just revert it globally now,
until the caus
ble usually, many 'normal' people use it in prod. This is
a very severe bug in my book, right next to that kernel one a few months ago
killing screens. Unless you're rather deep into Debian, you're never going to
find the workaround, and likely just move on.
On Sat, Nov 05, 2022 at 01:47:25PM +0100, Andreas Metzler
wrote:
> It is WX related, problably missing EGL support in glew.
>
> It worked my in own tests. I realize now that was because I have this
> setting in ~/.config/hugin.conf:
> [GLPreviewFrame]
> [...]
> isShown=0
>
> (i.e. The OpenGL P
Is there an easy way to unbrick a system affected by the issue? such as
a kernel-line option or a configuration file in /etc? I don't see how I
can set a GLIBC_TUNABLES environment variable for the whole system.
I was trying during my testing to set such option globally somehow, but
failed, tho
Now that we understood the bug, I actually find strange that the
microcode update is fixing this, it looks like that the BMI2
instructions support has been added in a microcode update. Would it be
possible to give the output of /proc/cpuinfo with and without the
microcode update applied?
The
I can confirm updating the microcode by installing the intel-microcode
package and rebooting does indeed mitigate this issue. An LXC container
that was previously bricked due to update now starts and seems to behave
fully normally.
[0.00] microcode: microcode updated early to revision
Hello, sorry for delayed response, I've managed to collect and analyze a
few coredump files with valid symbols (I installed libc6-dbg and
dpkg-dev, and pointed gdb at Debian's debuginfod server, also used
apt-get source to get the sources for libc6).
It seems there are at least 3-4 distinct pl
sing this env var workaround and then try running some
program under gdb itself with this variable cleared? I've never actually
used gdb debugger, but surely a simple debugging up to a crash couldn't
be that hard...
> The changes that are in this stable release have been (or at least
AVX2 and changes made to some functions utilizing this
instruction set. I don't know much about Debian bug reporting, so
forgive me any mistakes I've made.
The issue is on both host, LXC and Docker.
I have described more on this link:
https://github.com/debuerreotype/docker-debian-artifa
Package: squidguard
Version: 1.6.0-2
Severity: normal
X-Debbugs-Cc: fernando.alves.ra...@gmail.com
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
* What exactly did you do (or not do) that was effective (or
Hello Andrei:
True, the package is not from Debian, but the purpose of me filing a bug
report is to generate an RFP so that the package can be adapted by
Debian. Adapting the package by Debian is the first step in moving
things forward. So far I haven't found any issues, and the packa
Package: atari800
Version: 4.2.0-4
Severity: important
X-Debbugs-Cc: mcluo...@grr.la
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
Switching pulse audio output to hdmi instead of sound card audio out
Package: ifenslave
Version: 2.12
Problem while trying to bring up bond0 or any bonding interface.
ifup[933]: No iface stanza found for master bond0
The root cause is ifenslave shipped with a script, referring to ifstate command
which is not present.
Script:/etc/network/if-pre-up.d/ifenslave
Package: Debian stable installer
Version: 10.8.0
Severity: Critical
Report submitted on behalf of from #xfce Freenode Network.
Svartoyg reports that Debian installer 10.8.0 would not write file
systems to disk if an EFI partition was installed first. His report
consists of -notebook w
Package: Debian stable installer
Version: 10.7.0, and 10.8.0
Severity: Critical
Hard drive was formated as GPT. Installer will not write to disk after
setting up file system/partitions if an EFI partition is created first.
Error message indicates "Can't write to disk". Once the EFI par
the order they have
been manually rearranged or moved to.
* What outcome did you expect instead?
Normal mate-panel memory usage.
An earlier bug report on this issue #966292 was closed six months ago
on 12 Aug 2020 with the note:
"fixed in the latest version of mate-
For the use case of containerized environments BusyBox already provides
a cron applet with custom logging capabilities:
busybox crond -f -L /dev/stdout
Dear Maintainer
I have two machines, one with this bug, and one without.
#922214
I've tried a few things including dpkg-repack and a
rebuild from source. The only thing that works is an
install of the version 1.2.49-3 and manual linking
to the newer code.
The difference in the two mac
This raises a warning in `systemd-analyze verify` too.
Please consider backporting
https://github.com/fail2ban/fail2ban/commit/d5a5efcd5af272372153e86436d7c8cde2ddf66d.
This should fix the issues all together.
This is a duplicate of
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=902413
This is a duplicate of
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=910362
Package: gimp2.0
Version: gimp_2.10.12-1_amd64.deb
I am running Debian|testing
one or more recent upgrades caused gimp to
fail to open.
The cause seems to be an incompatibility in the
installation of libgegl-common
/quote
libgegl-common : Conflicts: libgegl-0.4-0 (<= 1:0.4.0-dmo1) but 0.4.1
Dear Maintainer,
re: pgadmin3
I am running Debian Testing and
postgresql ver 12.1 on an amd machine
I forward this as an update to bug #935881
because there is no real fix for this bug.
The pgadmin site says that pgadmin3 is no longer
supported. It would appear that migration to
pgAdmin4
Your bug report
#38574: Bug#946620: diff called 'GNU'
which was filed against the diffutils package, has been closed.
The explanation is attached below, along with your original report.
If you require more details, please reply to 38...@debbugs.gnu.org.
--
38574: http://debbugs.g
Package: nemo
Version: 3.8.5-1+b1
Severity: normal
Dear Maintainer,
[Problem description]
The default application associated with a file is hidden, if the file is set
with the execute permission. As a result, the user cannot open an executable
file in the default associated application from a c
Thank you for filing a new bug report with debbugs.gnu.org.
This is an automatically generated reply to let you know your message
has been received.
Your message is being forwarded to the package maintainers and other
interested parties for their attention; they will reply in due course.
As you
Package: thunderbird
Version: 1:68.2.2-1~deb10u1
Severity: important
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
* What exactly did you do (or not do) that was effective (or
ineffective)?
* What was
lookup error: bitcoin-qt: undefined symbol:
_ZN7leveldb4port5Mutex6UnlockEv
Also reported by: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933311
-- System Information:
Debian Release: bullseye/sid
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'stable')
Sorry, used reportbug for the first time... Misprint the email.
I also noticed that at least sodomized-sheep.cow had been removed in
the latest update, breaking a login script on my system. Please
restore the previous cows. Thanks!
Package: less
Version: 487-0.1+b1
Severity: important
Tags: upstream
This is not a bug in any current Debian package, but an FYI about an
upstream regression.
As of version 520 the following test-case will wait a full 5 seconds
before printing "hello":
(echo "hello"; sl
Package: socnetv
Version: 2.1-1.1
Severity: important
Dear Maintainer,
I had written a perl application to produce a database table
of linked organisations by extracting details from a book.
My preferred way of producing the network graph id to produce
a pajek.net file from the postgresql tabl
Package: php-memcached
Version: 3.0.1+2.2.0-1
Severity: normal
--- Please enter the report below this line. ---
Unusable in testing with php7.1 so must be split or add files for both
version.
--- System information. ---
Architecture:
Kernel: Linux 4.9.0-4-amd64
Debian Release: 9.1
999 stable
Package: php-xdebug
Version: 2.5.5-3
Severity: normal
--- Please enter the report below this line. ---
Must be split to php7.0-xdebug and php7.1-xdebug as many other php
packages or as some packages include files in both dir
/usr/lib/php/20151012 and /usr/lib/php/20160303
--- System informat
Followup-For: Bug #256588
Package: anacron
Dear Maintainer,
It looked like my machine hadn't run anacron for many months,
and for some undetermined reason, it wasn't reported.
After some checks, I found in syslog :
anacron: Error opening /etc/anacrontab: no such file or directo
() failed.
It looks like a bug in the source code in this line:
I: [pulseaudio] main.c: setrlimit(RLIMIT_NICE, (31, 31)) failed: Operation not
permitted
I haven't checked to see if this is resolved in later versions of pulseaudio.
HopeThisHelps
-- Package-specific info:
File '/etc/def
Hi maintainer,
I'm running debian stable (Stretch) and have had problems with
SMPlayer ever since I upgraded to Stretch. I'm running the older
versions of xorg and xserver, in case that makes any difference.
I'm seeing the bug reported as #867115, and I'm forwarding this
Hi,
Freshly made pool with noting in it:
# zpool scrub stor04
# zpool status stor04
pool: stor04
state: ONLINE
scan: scrub repaired 0 in 0h0m with 0 errors on Mon Jul 3 23:32:30 2017
config:
NAME STATE READ
WRITE CKSUM
I solved this by updating the ca-certificates-java package in backports. I
could then install the jdk and jre.
apt-get install -t jessie-backports ca-certificates-java
--bs
Package: cowsay
Version: 3.03+dfsg1-16
Severity: wishlist
In 3.03+dfsg1-13 the cowsay-off package was created in response to
#769194. I used one of those cows in a login script and on upgrade had
an error about a nonexisting cow.
It took me longer than it otherwise would have to figure out what w
Package: vmdebootstrap
Version: 1.2-1
Severity: important
-- System Information:
Debian Release: 8.2
APT prefers stable
APT policy: (500, 'stable'), (50, 'unstable')
Architecture: armhf (armv7l)
Kernel: Linux 4.1.6-249 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (char
Package: vmdebootstrap
Version: 0.10-1
Severity: important
DEBUG Config:
[config]
output =
log =
log-level = debug
log-max = 0
log-keep = 10
log-mode = 0600
dump-memory-profile = simple
memory-dump-interval = 300
verbose = True
image = image.img
size = 39
bootsize = 12800
boottype =
Package: vmdebootstrap
Version: 0.8-1
Severity: important
Tags: upstream
Hi,
I get the following error using the latest Debian package version 0.9-1 in sid:
Traceback (most recent call last):
File "/usr/lib/python2.7/dist-packages/cliapp/app.py", line 189, in _run
self.process_args(args)
> I am in the process of packaging the new upstream version of plowshare.
> There has been a significant change so that the core framework (of shell
> scripts) is kept entirely separate to the scripts which use this API to
> implement support for specific external sites.
While separating the core
Source: frama-c
Version: 20140301+neon+dfsg-3
Severity: wishlist
According to the INSTALL document in the frama-c source distribution,
the GTK GUI and the associated dependencies are optional.
However, in Debian both the frama-c and the frama-c-base package
depend on the liblablgtk* packages.
P
Package: gcc-msp430
Version: 4.6.3~mspgcc-20120406-7
The long description for gcc-msp430 contains the following scary warning:
BEWARE: due to a bug in the memory layout reference of FRAM-based
chips, this package DOES NOT WORK with MSP430FR5xxx chips (eg.
FraunchPad devkit). DO NOT use gcc
Package: gcc-msp430
Version: 4.6.3~mspgcc-20120406-7
Severity: important
The gcc-msp430 package in Debian is based on the obsolete mspgcc project.
Now that upstream gcc officially supports the msp430 architecture, there should
be a new gcc-msp430 package providing an msp430 cross-compiler based o
Package: vmdebootstrap
Version: 0.8-1
Severity: important
Tags: patch
-- System Information:
Debian Release: stretch/sid
APT prefers testing
APT policy: (650, 'testing'), (600, 'unstable'), (500, 'oldstable-updates'),
(500, 'oldstable')
Architecture: amd64 (x86_64)
Kernel: Linux 3.16.0-4-a
Package: plowshare4
Version: 1.0.5-1
Severity: grave
Tags: security
(Rationale for severity grave: introduces a security hole
allowing access to the accounts of users who use the package.
plowshare4 is a command-line tool for downloading files from
cyberlocker-type sites. For some sites, this req
With udev rules that call a script to applies the apm_on_ac or apm_on_battery
settings accordingly,
the systemd resume could be handled with a unit file like this:
[Unit]
Description=Trigger all block device udev rules on resume to re-apply
non-permanent device settings (e.g. smartctl and hdpar
Package: hdparm
Severity: serious
The apm/pm-utils suspend/resume functionalities, provided by shipping the
files 20hdparm and 95hdparm-apm scripts, do not work with systemd.
(missing systemd unit files)
To allow setting defaults I would suggest to support wildcards in hdparm.conf.
And ship with
Control: reopen 744753
Please ship a working systemd unit file as given in the last comments.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Control: reopen 725284
Udev rules are only trigged when devices appear/disapper,
but not when the kernel suspends (with the device staying
present and only entering a low power state)
A systemd unit file is required to recover all hdparm settings that
devices wrongly initialize back to factory d
Package: apt-listchanges
Version: 2.85.13+nmu1
Severity: minor
I discovered this bug after leaving the message buffer of
apt-listchanges around for days in a screen session while the pager
was set to read the changelog:
Fetched 186 MB in 10s (17.8 MB/s)
Reading changelogs... Done
I'm sorry, somehow I missed to post the bug description.
I'm using LXDE with openbox and have it configured to always put
windows/dialogs onto the monitor where the mouse pointer currently is.
Gimp instead *always* opens the save-file dialog and some other dialogs
on the other monito
Package: pdns-server
Version: 3.4.1-3
Severity: important
I upgraded to 3.4.0 and my authoritative nameserver stopped working,
nothing major was noted in the Changelog or NEWS file, I think it's
worth a mention that the value for allow-axfr-ips changed from
0.0.0.0/0,::/0 to 127.0.0.0/8,::1, this
Package: pdns-server
Version: 3.4.1-3
Severity: grave
When I upgraded from 3.3.* I started getting this in error log:
Nov 17 19:28:30 u pdns[14671]: Loading '/usr/lib/powerdns/libbindbackend.so'
Nov 17 19:28:30 u pdns[14671]: Unable to load module
'/usr/lib/powerdns/libbindbackend.so': /
Package: iodine
Version: 0.6.0~rc1-19
Severity: serious
I couldn't find out how to re-open an existing bug but this issue that
I reported & was resolved a while ago is now happening again:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=612723
Upgrading from 0.6.0~rc1-12 to 0.6.0~rc1-
Package: cronolog
Version: 1.6.2+rpk-1
Severity: wishlist
Tags: upstream
When you run cronolog successfully it exits with a non-zero exit code
due to this bit of code in main():
n_bytes_read = read(0, read_buf, sizeof read_buf);
if (n_bytes_read == 0)
{
exit(3);
}
I.e. if
Package: cronolog
Version: 1.6.2+rpk-1
Severity: normal
On my system:
$ cronolog --version
cronolog version 1.6.2
$ cronolog --vesion
Segmentation fault
A backtrace for this is:
Program received signal SIGSEGV, Segmentation fault.
0x77ab5f4c in ?? () from /lib/x86_64-linux-gnu/libc.so.6
Hi,
in fact, 1.6.0 was released 2014-01-04, so upgrading to 1.5.11 got
pointless ;)
Moritz
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
'handlersocket.so' (errno: 0 API
version for DAEMON plugin is too different)
it seems that this problem has occured in previous version which is reported in
bug 649214
* What led up to the situation?
-- System Information:
Debian Release: 7.2
APT prefers stable-updates
APT p
Package: plasma-desktop
Version: 4:4.10.5-3
Severity: grave
Justification: renders package unusable
Since an update to the packages on Debian testing last night, the KDE desktop
crashes on boot, giving a message that prompts to create a backtrace. Here is
that backtrace.
As you can see, running D
Thank you for the kind response and information.
Looking forward to it.
With "auto-assembly support" you have a much better
description then my "using udev rules".
Basicly, I think it is about moving the assembly functionality from the
startup scripts to event driven rules, and leaving only so
Package: mdadm
Wondering about why nothing happened when hot-plugging a
raid member drive, I found the following answer in the changelog:
* disabled the incremental assembly upstream turned on in 3.1.3 for
now, this will have to wait until after the squeeze release.
And saw the Maintainer c
Package: gdm
I noticed lmt was again not properly setting the hdparm values on resume.
Turning on the verbose output revealed many
"Couldn't acquire prelim lock on descriptor" errors.
I have no idea about the real cause for this. But stopping lmt before suspend
in a /etc/pm/sleep.d/99laptop_mode
Your bug report
#14686: Bug#713022: truncate man and info pages must mention -s / -r mandatory
which was filed against the coreutils package, has been closed.
The explanation is attached below, along with your original report.
If you require more details, please reply to 14...@debbugs.gnu.org
Thank you for filing a new bug report with debbugs.gnu.org.
This is an automatically generated reply to let you know your message
has been received.
Your message is being forwarded to the package maintainers and other
interested parties for their attention; they will reply in due course.
As you
Package: xscreensaver-screensaver-bsod
Version: 5.15-3
Severity: minor
Dear Maintainer,
Select the BSOD screensaver and configure it to use only one type of bsod.
I tried it several times with linux(fsck) option, then the linux(sparc) option
and then bsd
option. Then lock the system to start the
e the bug open, to reflect the status
and point other admins and users to the solution.
Have a nice weekend.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
> If you believe in that solution, please feel free to provide a patch.
> Complaints without action tend to be counter-productive time wasters.
Exactly. That would surely be the answer if filing this for packages that
depend on wine.
Exept, wine-party is resposible for a package that currently
> > Thus, the idea of letting the packet managment script provide the
> message.
>
> Or having the front end fix their assumptions. Please consider filing
> a bug against q4wine.
Please sleep over this. This sounds funny to me.
The debian wine package maintainers want up
> Which front end are you using?
It was q4wine
> message should pop up via
> xmessage, and if not it will be dumped to stdout. So if your front
> end is preventing that, the issue should be fixed there.
Unfortunately, missing files already cause errors during the frontend
configuration proces
> Are you saying that the following message was never displayed to you?
Correct, the message was never displayed.
As reported, I installed a frontend that depends on wine, and strange error
messages popped up instead, caused by all kinds of missing files.
Thus my suggestion you use a high prio
t to use
a high priority debconf question to draw attention to it, if no automated
solution is possible.
(My reopen attempt did not work out. I think it wold be good to let the report
open.
When trying to figure out what the problem was I came accross a closed bug
that mentioned this, but I was lead
reopen: 707226
> If you install the wine package instead of wine-bin, you will get the
> wine64-bin package,
Yes, that is also what the bug title says and exaclty what happened by
installing a package that depends on wine.
> which will present the above helpful info to t
Package: wine
Severity: grave
On a freshly installed Debian stable (wheezy) on amd64, installing a frontend
like q4wine and wine seems to succeed, but running it produces strange errors.
The reason: Actually, no wine binaries or libs were installed.
Please add some debconf script to the wine-bin
Package: release-notes
Hello,
after seaching a lot, it finaly turned up not only questions
but also a solution on how to upgrade a squeeze gnome
system to a wheezy xfce system.
Found at the end of this thread:
debianforum.de/forum/viewtopic.php?f=12&t=140311
This request seems quite justified
Thank you
It looked like a bug to me
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
I forgot to tell that my wheezy install is about 3 weeks old.
I use a local mirror that is not updated
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
For the sake of completeness for users that are bitten by this bug and search
for instructions:
The filesystem permissions of a fully publicly shared directory (i.e. ~/public)
has to be drwxrwsrwx.
chmod a+rwx ~/public
chmod g+s ~/public
And /etc/samba/smb.conf has to contain the line
The experience after a couple of months showed that the solution that sets
"inherit permissions = yes" as default works very well.
I'd suggest to implement that change as a fix. (Either in the default config
file shipped, or better, by adjusting the fallback value that samba uses if the
option
Package: krossruby
Source: kross-interpreters
Severity: wishlist
krossruby no longer exists in testing.
It would be nice for it to come back, if possible.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.deb
Tools like gnome-system-tools or accountservice allow to add the user to the
nopasswdlogin group. You might adopt that, to avoid the sudo breakage with
empty passwords.
A description of the method:
https://wiki.archlinux.org/index.php/GDM#Passwordless_login
--
To UNSUBSCRIBE, email to debian
Am Wed, 10 Oct 2012 21:09:05 +
schrieb ow...@bugs.debian.org (Debian Bug Tracking System):
> wheezy-updates does now exist.
Thanks! Is the creation of the dir now included in the script/procedure
for post wheezy releases?
--
To UNSUBSCRIBE, email to debian-bugs-dist-r
is how kernel has responded:
[21974.560657] iscsi_trgt: BUG at
/var/lib/dkms/iscsitarget/1.4.20.2/build/kernel/iscsi.c:392 assert(req->tio)
[21974.560667] Pid: 3288, comm: istiod1 Tainted: G O 3.2.0-3-amd64 #1
[21974.560671] Call Trace:
[21974.560683] [] ? send_data_rsp+0x45/0x
In the meanwhile in 2012...
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Package: gdm
Hello,
in contrast to slim, kdm, or startx, gdm breaks the central
umask configuration.
This is in debian stable (squeeze).
GDM sets the default umask to an explicit value (0022),
however, it should leave it as set by the system's default settings.
(The default umask is set with pam
Hello,
thank you very much for your help.
The umask returned in the .xsession xterm is 0022.
Does this mean gdm is wrongly setting the umask?
Could you then please reassign this bug to gdm?
> > Package: xfce4
> >
> > Hello,
> > this is in debian stable (squeeze).
&
Package: xfce4
Hello,
this is in debian stable (squeeze).
Something in the desktop environment sets the default umask
to an explicit value (0022), instead of leaving it as set according
to the system's default settings.
(The default umask is set with pam_umask according to
http://wiki.debian.o
1 - 100 of 367 matches
Mail list logo
