Bug#1032773: lxterminal: a new lxterminal cmdline invoke opens new instances only as the first instance user
Package: lxterminal Version: 0.4.0-2 Severity: normal X-Debbugs-Cc: osma...@gmail.com any new lxterminal invocation (as another user) will open the new window as the first invocation. a sample session: user1@hostname:~/folder1/folder2 lxterminal & [1] 7*** user1@hostname:~/folder1/folder2$ su Password: [1]+ Donelxterminal user1@dhostname:~/folder1/folder2$ su Password: root@hostname:/home/user1/folder1/folder2# lxterminal root@hostname:/home/user1/folder1/folder2# *** the new instance will prompt user1@hostname:~/folder1/folder2 instead of root@hostname:/home/user1/folder1/folder2# both commands will open lxterminal as user1, anyway if i swith user using su - , the lxterminal is gonna open as root . i think its something related to the way lxterminal connect to dbus and determined to connect to the orginal instance. -- System Information: Debian Release: bookworm/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.1.0-5-amd64 (SMP w/4 CPU threads; PREEMPT) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages lxterminal depends on: ii libc62.36-8 ii libgdk-pixbuf-2.0-0 2.42.10+dfsg-1+b1 ii libglib2.0-0 2.74.5-1 ii libgtk-3-0 3.24.36-4 ii libpango-1.0-0 1.50.12+ds-1 ii libvte-2.91-00.70.3-1 ii libx11-6 2:1.8.3-3 lxterminal recommends no packages. lxterminal suggests no packages. -- no debconf information
Bug#1017884: reportbug: qemu-system-x86_64 freezes after i access samba server on a windows-xp host
Package: qemu-system-x86
Version: 1:7.0+dfsg-7+b1
Severity: important
X-Debbugs-Cc: osma...@gmail.com
I use qemu as the following:
/usr/bin/qemu-system-x86_64 -soundhw ac97 -machine accel=kvm -m 1033 -cdrom
windowsxp.iso -hda windowsxp.img -boot once=d,menu=off -net nic,model=rtl8139
-net user -net user,smb="/path/to/shared/folder/inside/my/home" -rtc
base=localtime -name "Windows XP x32"
it boots normally after installation, but when i access shared folder (just by
typing qemu user network ip "\\10.0.2.2\qemu") inside the run dialog everything
freezed , i can't even grab my pointer outside qemu window without
restarting window manager.
i also have this inside my smb.conf
==
#
# Sample configuration file for the Samba suite for Debian GNU/Linux.
#
#
# This is the main Samba configuration file. You should read the
# smb.conf(5) manual page in order to understand the options listed
# here. Samba has a huge number of configurable options most of which
# are not shown in this example
#
# Some options that are often worth tuning have been included as
# commented-out examples in this file.
# - When such options are commented with ";", the proposed setting
#differs from the default Samba behaviour
# - When commented with "#", the proposed setting is the default
#behaviour of Samba but the option is considered important
#enough to be mentioned here
#
# NOTE: Whenever you modify this file you should run the command
# "testparm" to check that you have not made any basic syntactic
# errors.
#=== Global Settings ===
[global]
## Browsing/Identification ###
# Change this to the workgroup/NT-domain name your Samba server will part of
workgroup = WORKGROUP
Networking
# The specific set of interfaces / networks to bind to
# This can be either the interface name or an IP address/netmask;
# interface names are normally preferred
; interfaces = 127.0.0.0/8 eth0
# Only bind to the named interfaces and/or networks; you must use the
# 'interfaces' option above to use this.
# It is recommended that you enable this feature if your Samba machine is
# not protected by a firewall or is a firewall itself. However, this
# option cannot handle dynamic or non-broadcast interfaces correctly.
; bind interfaces only = yes
Debugging/Accounting
# This tells Samba to use a separate log file for each machine
# that connects
log file = /var/log/samba/log.%m
# Cap the size of the individual log files (in KiB).
max log size = 1000
# We want Samba to only log to /var/log/samba/log.{smbd,nmbd}.
# Append syslog@1 if you want important messages to be sent to syslog too.
logging = file
# Do something sensible when Samba crashes: mail the admin a backtrace
panic action = /usr/share/samba/panic-action %d
### Authentication ###
# Server role. Defines in which mode Samba will operate. Possible
# values are "standalone server", "member server", "classic primary
# domain controller", "classic backup domain controller", "active
# directory domain controller".
#
# Most people will want "standalone server" or "member server".
# Running as "active directory domain controller" will require first
# running "samba-tool domain provision" to wipe databases and create a
# new domain.
server role = standalone server
obey pam restrictions = yes
# This boolean parameter controls whether Samba attempts to sync the Unix
# password with the SMB password when the encrypted SMB password in the
# passdb is changed.
unix password sync = yes
# For Unix password sync to work on a Debian GNU/Linux system, the following
# parameters must be set (thanks to Ian Kahan < for
# sending the correct chat script for the passwd program in Debian Sarge).
passwd program = /usr/bin/passwd %u
passwd chat = *Enter\snew\s*\spassword:* %n\n *Retype\snew\s*\spassword:*
%n\n *password\supdated\ssuccessfully* .
# This boolean controls whether PAM will be used for password changes
# when requested by an SMB client instead of the program listed in
# 'passwd program'. The default is 'no'.
pam password change = yes
# This option controls how unsuccessful authentication attempts are mapped
# to anonymous connections
map to guest = bad user
## Domains ###
#
# The following settings only takes effect if 'server role = classic
# primary domain controller', 'server role = classic backup domain controller'
# or 'domain logons' is set
#
# It specifies the location of the user's
# profile directory from the client point of view) The following
# required a [profiles] share to be setup on the samba server (see
# below)
; logon path = \\%N\profiles\%U
# Another common choice is storing the profile in the user's home directory
# (this is Samba's default)
# logon path = \\%N\%U\profile
# The following setting only takes effect if 'domain logons' is set
#
Bug#935115: passing variable assignments to functions (was Re: Bug#935115: bash: [regression] passing variable assignments to functions broken in POSIX mode, violating POSIX)
looks like it has been fixed, i can't reproduce in either unstable, testing or stable by the moment of now.
Bug#970925: hexchat: underscore-character glaphs doesn't appear in hexchat chat widget
Package: hexchat Version: 2.14.3-3 Severity: normal X-Debbugs-Cc: osma...@gmail.com Dear Maintainer, * What led up to the situation? sending something contains underscore character (_) in hexchat, with any font (only in chat widget , the rest of application UI is not effected) * What was the outcome of this action? simply underscore glaphs doesn't render, it looks like a space * What outcome did you expect instead? an underscore, my IRC nickname is "os_" and appearing like "os" -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.8.0-2-amd64 (SMP w/4 CPU threads) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages hexchat depends on: ii hexchat-common 2.14.3-3 ii libc6 2.31-3 ii libcanberra00.30-7 ii libdbus-glib-1-20.110-5 ii libgdk-pixbuf2.0-0 2.40.0+dfsg-5 ii libglib2.0-02.66.0-2 ii libgtk2.0-0 2.24.32-4 ii libnotify4 0.7.9-1 ii libpango-1.0-0 1.46.1-1 ii libproxy1v5 0.4.15-13 ii libssl1.1 1.1.1g-1 ii libx11-62:1.6.12-1 Versions of packages hexchat recommends: ii hexchat-perl 2.14.3-3 ii hexchat-plugins 2.14.3-3 ii hexchat-python3 2.14.3-3 ii libglib2.0-bin 2.66.0-2 Versions of packages hexchat suggests: pn hexchat-otr pn unifont -- no debconf information
Bug#794666: c++-annotations-pdf: a mistake in this example
Package: c++-annotations-pdf Version: 9.9.1-2 Severity: important Tags: newcomer Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** in cplusplus.pdf, page 80 (actually it the 102th page, you know!), the second example of stoi function it is: value = stoi(string( 123, 0, 5)); // assigns value 38 * What outcome did you expect instead? it is : value = stoi(string( 123), 0, 5); // assigns value thanks -- System Information: Debian Release: 8.1 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: i386 (i686) Kernel: Linux 3.16.0-4-686-pae (SMP w/4 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) c++-annotations-pdf depends on no packages. c++-annotations-pdf recommends no packages. Versions of packages c++-annotations-pdf suggests: pn bisonc++ none -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
