Bug#1025318: Acknowledgement (nextcloud-desktop: libGL error: failed to load driver: i915 (Segmentation fault))
> Debian Bug Tracking System 於2022年12月2日 21:57寫道： > > Thank you for filing a new Bug report with Debian. > > You can follow progress on this Bug here: 1025318: > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025318. > > 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. > > Your message has been sent to the package maintainer(s): > ownCloud for Debian maintainers > > > If you wish to submit further information on this problem, please > send it to 1025...@bugs.debian.org. > > Please do not send mail to ow...@bugs.debian.org unless you wish > to report a problem with the Bug-tracking system. > > -- > 1025318: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025318 > Debian Bug Tracking System > Contact ow...@bugs.debian.org with problems
Bug#1025318: nextcloud-desktop: libGL error: failed to load driver: i915 (Segmentation fault)
Package: nextcloud-desktop
Version: 3.6.1-1
Severity: normal
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
When I open "nextcloud-desktop" on terminal, it cannot open and reture
the error messages:
libGL error: MESA-LOADER: failed to retrieve device information
libGL error: MESA-LOADER: failed to open i915: /usr/lib/dri/i915_dri.so:
cannot open shared object file: No such file or directory (search paths
/usr/lib/x86_64-linux-gnu/dri:\$${ORIGIN}/dri:/usr/lib/dri, su
ffix _dri)
libGL error: failed to load driver: i915
libGL error: MESA-LOADER: failed to retrieve device information
libGL error: MESA-LOADER: failed to open i915: /usr/lib/dri/i915_dri.so:
cannot open shared object file: No such file or directory (search paths
/usr/lib/x86_64-linux-gnu/dri:\$${ORIGIN}/dri:/usr/lib/dri, su
ffix _dri)
libGL error: failed to load driver: i915
Segmentation fault
Please help, thank you.
*** End of the template - remove these template lines ***
-- System Information:
Debian Release: bookworm/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 6.0.0-5-amd64 (SMP w/8 CPU threads; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8),
LANGUAGE=en_US:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages nextcloud-desktop depends on:
ii libc6 2.36-6
ii libcloudproviders0 0.3.1-2
ii libgcc-s1 12.2.0-9
ii libglib2.0-0 2.74.2-1
ii libnextcloudsync0 3.6.1-1
ii libqt5core5a 5.15.6+dfsg-4
ii libqt5dbus55.15.6+dfsg-4
ii libqt5gui5 5.15.6+dfsg-4
ii libqt5keychain10.13.2-5
ii libqt5network5 5.15.6+dfsg-4
ii libqt5qml5 5.15.6+dfsg-2
ii libqt5quick5 5.15.6+dfsg-2
ii libqt5quickcontrols2-5 5.15.6+dfsg-2
ii libqt5sql5-sqlite 5.15.6+dfsg-4
ii libqt5svg5 5.15.6-2
ii libqt5webenginecore5 5.15.10+dfsg-7+b1
ii libqt5webenginewidgets55.15.10+dfsg-7+b1
ii libqt5widgets5 5.15.6+dfsg-4
ii libstdc++6 12.2.0-9
ii nextcloud-desktop-common 3.6.1-1
ii nextcloud-desktop-l10n 3.6.1-1
ii qml-module-qt-labs-platform5.15.6+dfsg-2
ii qml-module-qtgraphicaleffects 5.15.6-2
ii qml-module-qtqml-models2 5.15.6+dfsg-2
ii qml-module-qtquick-controls2 5.15.6+dfsg-2
ii qml-module-qtquick-dialogs 5.15.6-2
ii qml-module-qtquick-layouts 5.15.6+dfsg-2
ii qml-module-qtquick-window2 5.15.6+dfsg-2
ii qml-module-qtquick25.15.6+dfsg-2
Versions of packages nextcloud-desktop recommends:
pn nextcloud-desktop-doc
nextcloud-desktop suggests no packages.
-- no debconf information
Bug#1021187: gnome-keyring: /usr/bin/gnome-keyring-daemon --daemonize --login 100% CPU usage
Package: gnome-keyring Version: 42.1-1 Severity: normal Dear Maintainer, I just noticed recently, the "/usr/bin/gnome-keyring-daemon --daemonize --login" running 100% (1 vcpu) CPU usage everytime when I login (until I kill it) Please help and thank you. *** 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 the outcome of this action? * What outcome did you expect instead? *** End of the template - remove these template lines *** -- System Information: Debian Release: bookworm/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 5.19.0-2-amd64 (SMP w/8 CPU threads; PREEMPT) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages gnome-keyring depends on: ii dbus-user-session [default-dbus-session-bus] 1.14.2-1 ii dbus-x11 [dbus-session-bus] 1.14.2-1 ii dconf-gsettings-backend [gsettings-backend] 0.40.0-3 ii gcr 3.41.1-1 ii init-system-helpers 1.65.2 ii libc6 2.35-1 ii libgck-1-03.41.1-1 ii libgcr-base-3-1 3.41.1-1 ii libgcrypt20 1.10.1-2 ii libglib2.0-0 2.74.0-2 ii libsystemd0 251.5-1 ii p11-kit 0.24.1-1 ii pinentry-gnome3 1.2.0-2 Versions of packages gnome-keyring recommends: ii gnome-keyring-pkcs11 42.1-1 ii libpam-gnome-keyring 42.1-1 gnome-keyring suggests no packages. -- no debconf information
Bug#993232: lxc: Cannot add ipv4 gateway for network device "eth0" when not bringing up the interface.
On 1/28/22 08:19, Pierre-Elliott Bécue wrote: Control: tags -1 +moreinfo Le dimanche 29 août 2021 à 12:23:09+0800, John a écrit : Package: lxc Version: 1:4.0.10-1 Severity: normal X-Debbugs-Cc: jo...@wonghome.net Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** After upgraded lxc from 4.0.6-2 to 4.0.10-1. lxc container cannot start. I find the error with "lxc-start -l trace" like below: network.c:lxc_network_setup_in_child_namespaces_common:3894 - Cannot add ipv4 gateway for network device "eth0" when not bringing up the interface network.c:lxc_setup_network_in_child_namespaces:4038 - Function not implemented - Failed to setup netdev conf.c:lxc_setup:4080 - Failed to setup network start.c:do_start:1291 - Failed to setup container "vbox" If I rollback to 4.0.6-2, everything work fine as before. If I remove the line "lxc.net.0.ipv4.gateway = 10.0.3.1" in "/var/lib/lxc/vbox/config" (container config), the container can start again, but result no network , only loopback interface (lo) in container (no eth0 in container). From where I stand, I'm unable to reproduce: ❯ sudo lxc-create toto -t debian -- -r bullseye [snip] ❯ sudo service lxc-net start ❯ ip a [snip] 7: lxcbr0: mtu 1500 qdisc noqueue state DOWN group default qlen 1000 link/ether 00:16:3e:00:00:00 brd ff:ff:ff:ff:ff:ff inet 10.0.3.1/24 brd 10.0.3.255 scope global lxcbr0 valid_lft forever preferred_lft forever ❯ sudo lxc-ls -f NAME STATE AUTOSTART GROUPS IPV4 IPV6 UNPRIVILEGED toto STOPPED 0 - --false ❯ sudo vim /var/lib/lxc/toto/config [adding ip conf] ❯ sudo cat /var/lib/lxc/toto/config # Template used to create this container: /usr/share/lxc/templates/lxc-debian # Parameters passed to the template: -r bullseye # For additional config options, please look at lxc.container.conf(5) # Uncomment the following line to support nesting containers: #lxc.include = /usr/share/lxc/config/nesting.conf # (Be aware this has security implications) lxc.net.0.type = veth lxc.net.0.hwaddr = 00:16:3e:cb:a1:76 lxc.net.0.link = lxcbr0 lxc.net.0.flags = up lxc.net.0.ipv4.address = 10.0.3.3/24 lxc.net.0.ipv4.gateway = 10.0.3.1 lxc.apparmor.profile = generated lxc.apparmor.allow_nesting = 1 lxc.rootfs.path = dir:/var/lib/lxc/toto/rootfs # Common configuration lxc.include = /usr/share/lxc/config/debian.common.conf # Container specific configuration lxc.tty.max = 4 lxc.uts.name = toto lxc.arch = amd64 lxc.pty.max = 1024 ❯ sudo lxc-start toto ❯ sudo lxc-ls -f NAME STATE AUTOSTART GROUPS IPV4 IPV6 UNPRIVILEGED toto RUNNING 0 - 10.0.3.3 -false Please, try creating a new unprivileged container and make some tests with it, as for what I see, it doesn't seem like LXC is buggy. Cheers! Since the bug report is over a half year, and somehow I don't have the problem anymore, so I will close it first, if anyone has the problem present, please try to create a new bug report, thanks. Regards, John.
Bug#1004003: chromium: After upgrade to latest version, chromium cannot open anymore.
Package: chromium
Version: 97.0.4692.71-0.1~deb11u1
Severity: normal
X-Debbugs-Cc: johnw.m...@gmail.com
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
Hi, after upgraded the latest version of chromium on my chromebook(lxd),
chromium cannot working anymore.
When I type chromium on console, it just hang on there.
Thanks.
* What led up to the situation?
* What exactly did you do (or not do) that was effective (or
ineffective)?
* What was the outcome of this action?
* What outcome did you expect instead?
*** End of the template - remove these template lines ***
-- System Information:
Debian Release: 11.2
APT prefers stable-security
APT policy: (500, 'stable-security'), (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 5.4.157-17185-gbd27b903c738 (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 /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages chromium depends on:
ii chromium-common 97.0.4692.71-0.1~deb11u1
ii libasound2 1.2.4-1.1
ii libatk-bridge2.0-0 2.38.0-1
ii libatk1.0-0 2.36.0-2
ii libatomic1 10.2.1-6
ii libatspi2.0-0 2.38.0-4
ii libc6 2.31-13+deb11u2
ii libcairo2 1.16.0-5
ii libcups22.3.3op2-3+deb11u1
ii libdbus-1-3 1.12.20-2
ii libdrm2 2.4.104-1
ii libevent-2.1-7 2.1.12-stable-1
ii libexpat1 2.2.10-2
ii libflac81.3.3-2
ii libfontconfig1 2.13.1-4.2
ii libfreetype62.10.4+dfsg-1
ii libgbm1 20.3.5-1
ii libgcc-s1 10.2.1-6
ii libglib2.0-02.66.8-1
ii libharfbuzz0b 2.7.4-1
ii libicu6767.1-7
ii libjpeg62-turbo 1:2.0.6-4
ii libjsoncpp241.9.4-4
ii liblcms2-2 2.12~rc1-2
ii libminizip1 1.1-8+b1
ii libnspr42:4.29-1
ii libnss3 2:3.61-1+deb11u1
ii libopenjp2-72.4.0-3
ii libopus01.3.1-0.1
ii libpango-1.0-0 1.46.2-3
ii libpng16-16 1.6.37-3
ii libpulse0 14.2-2
ii libre2-920210201+dfsg-1
ii libsnappy1v51.1.8-1
ii libstdc++6 10.2.1-6
ii libwebp60.6.1-2.1
ii libwebpdemux2 0.6.1-2.1
ii libwebpmux3 0.6.1-2.1
ii libx11-62:1.7.2-1
ii libxcb1 1.14-3
ii libxcomposite1 1:0.4.5-1
ii libxdamage1 1:1.1.5-2
ii libxext62:1.3.3-1.1
ii libxfixes3 1:5.0.3-2
ii libxkbcommon0 1.0.3-2
ii libxml2 2.9.10+dfsg-6.7
ii libxrandr2 2:1.5.1-1
ii libxslt1.1 1.1.34-4
ii zlib1g 1:1.2.11.dfsg-2
Versions of packages chromium recommends:
ii chromium-sandbox 97.0.4692.71-0.1~deb11u1
Versions of packages chromium suggests:
pn chromium-driver
pn chromium-l10n
pn chromium-shell
Versions of packages chromium-common depends on:
ii libc6 2.31-13+deb11u2
ii libstdc++6 10.2.1-6
ii libx11-62:1.7.2-1
ii libxext62:1.3.3-1.1
ii x11-utils 7.7+5
ii xdg-utils 1.1.3-4.1
ii zlib1g 1:1.2.11.dfsg-2
Versions of packages chromium-common recommends:
ii chromium-sandbox 97.0.4692.71-0.1~deb11u1
pn fonts-liberation
ii libgl1-mesa-dri20.3.5-1
pn libu2f-udev
pn notification-daemon
pn system-config-printer
pn upower
Versions of packages chromium-sandbox depends on:
ii libc6 2.31-13+deb11u2
-- Configuration Files:
/etc/chromium/master_preferences changed:
{
"distribution": {
"import_bookmarks": false,
"import_bookmarks_from_file": "/etc/chromium/initial_bookmarks.html",
"make_chrome_default": false,
"make_chrome_default_for_user": false,
"verbose_logging": true,
"skip_first_run_ui": true,
"create_all_shortcuts": true,
"suppress_first_run_default_browser_prompt": true
},
"browser": {
"show_home_button": true,
"has_seen_welcome_page" : true,
"check_default_browser" : false
},
"profile": {
"default_content_setting_values": {
"payment_handler": 2
}
},
"bookmark_bar": {
"show_on_all_tabs": false
},
"net": {
"network_prediction_options": 2
},
"search": {
"suggest_enabled": false
},
"signin": {
"allowed": false,
"allowed_on_next_startup": false
},
"autofill": {
"profile_enabled": false,
"credit_card_enabled": false
},
"payments": {
"can_make_payment_enabled": false
},
"safebrowsing": {
"enabled": false
},
"dns_prefetching": {
"enabled": false
},
"alternate_error_pages": {
"enabled": false
},
"credentials_enable_service": false,
"credentials_enable_autosignin": false,
"default_apps": "noinstall",
"hide_web_store_icon": true,
"homepage_is_newtabpage": true,
"homepage": "https://www.google.com;
}
-- no debconf information
Bug#995035: lxc: Operation not permitted - Failed to mount "proc" onto "/usr/lib/x86_64-linux-gnu/lxc/rootfs/proc"
Package: lxc Version: 1:4.0.10-1 Severity: normal Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** After upgraded to 4.0.10-1, I cannot start unprivs container anymore (it works before upgrade). I start the unprivs container as root with this: lxc-start -n dmz011 -l trace -o log and I found this error message in the log like below: utils - utils.c:safe_mount:1198 - Operation not permitted - Failed to mount "proc" onto "/usr/lib/x86_64-linux-gnu/lxc/rootfs/proc" conf - conf.c:lxc_mount_auto_mounts:801 - Operation not permitted - Failed to mount "proc" on "/usr/lib/x86_64-linux-gnu/lxc/rootfs/proc" with flags 14 The container config like below: # Distribution configuration lxc.include = /usr/share/lxc/config/common.conf lxc.include = /usr/share/lxc/config/userns.conf lxc.arch = linux64 # Container specific configuration lxc.idmap = u 0 110 65536 lxc.idmap = g 0 110 65536 lxc.apparmor.profile = unconfined # Network configuration lxc.net.0.type = none lxc.rootfs.path = dir:/var/lib/lxc/dmz011/rootfs lxc.uts.name = dmz011 If I remove lxc.idmap, run the container as privs container, it can start. * What led up to the situation? * What exactly did you do (or not do) that was effective (or ineffective)? * What was the outcome of this action? * What outcome did you expect instead? *** End of the template - remove these template lines *** -- System Information: Debian Release: bookworm/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 5.14.0-1-amd64 (SMP w/8 CPU threads) Kernel taint flags: TAINT_WARN Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages lxc depends on: ii bridge-utils 1.7-1 ii debconf [debconf-2.0]1.5.77 ii dnsmasq-base [dnsmasq-base] 2.86-1 ii iproute2 5.14.0-1 ii iptables 1.8.7-1 ii libc62.32-4 ii libcap2 1:2.44-1 ii libgcc-s111.2.0-8 ii liblxc1 1:4.0.10-1 ii libseccomp2 2.5.2-1 ii libselinux1 3.1-3 ii lsb-base 11.1.0 Versions of packages lxc recommends: ii apparmor 3.0.3-2 pn debootstrap ii dirmngr2.2.27-2 ii gnupg 2.2.27-2 pn libpam-cgfs ii lxc-templates 3.0.4-5 ii lxcfs 4.0.7-1 ii openssl1.1.1l-1 ii rsync 3.2.3-7 pn uidmap ii wget 1.21-1+b1 Versions of packages lxc suggests: ii btrfs-progs 5.14.1-1 ii lvm2 2.03.11-2.1 ii python3-lxc 1:3.0.4-1+b4 -- Configuration Files: /etc/default/lxc-net changed: USE_LXC_BRIDGE="false" -- debconf information: lxc/auto_update_config:
Bug#994858: libglib2.0-0: After upgrade to 2.70.0-1, broken nextcloud-desktop
On 9/22/21 3:36 PM, Simon McVittie wrote: Control: tags -1 + moreinfo Control: notfound -1 2.68.4-1 Control: found -1 2.70.0-1 On Wed, 22 Sep 2021 at 11:52:21 +0800, John Wong wrote: After upgrade from 2.68.4-1 to 2.70.0-1, nextcloud-desktop cannot work anymore, rollback to 2.68.4-1 fixed problem. What exactly does "cannot work" mean? What version of nextcloud-desktop are you using? If you run nextcloud-desktop from a terminal such as gnome-terminal or xterm while using libglib2.0-0 2.70.0-1, are there any error messages? What would a developer who does not normally use nextcloud-desktop need to do to reproduce this problem? I tried installing nextcloud-desktop version 3.3.3-1 and connecting it to an account created by <https://try.nextcloud.com/> on the demo instance <https://demo1.nextcloud.com/>. It was able to download files and did not produce any obvious errors or warnings. smcv Hi Simon, When I run nextcloud-desktop on terminal, there is no error but just hang on there and cannot login. (sorry cannot provide useful information) https://ibb.co/mzn9ykH I rollback (with btrfs snapshot) , and hold the package. john@redcat:~$ dpkg --get-selections |grep hold libglib2.0-0:amd64 hold john@redcat:~$ sudo apt upgrade Reading package lists... Done Building dependency tree... Done Reading state information... Done Calculating upgrade... Done The following packages have been kept back: gir1.2-freedesktop gir1.2-glib-2.0 glib-networking glib-networking-services libgirepository-1.0-1 libglib2.0-0 0 upgraded, 0 newly installed, 0 to remove and 6 not upgraded. john@redcat:~$ Regards & Thanks, John.
Bug#994858: libglib2.0-0: After upgrade to 2.70.0-1, broken nextcloud-desktop
Package: libglib2.0-0 Version: 2.68.4-1 Severity: normal Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** After upgrade from 2.68.4-1 to 2.70.0-1, nextcloud-desktop cannot work anymore, rollback to 2.68.4-1 fixed problem. * What led up to the situation? * What exactly did you do (or not do) that was effective (or ineffective)? * What was the outcome of this action? * What outcome did you expect instead? *** End of the template - remove these template lines *** -- System Information: Debian Release: bookworm/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 5.10.0-8-amd64 (SMP w/8 CPU threads) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages libglib2.0-0 depends on: ii libc62.32-4 ii libffi7 3.3-6 ii libmount12.37.2-2 ii libpcre3 2:8.39-13 ii libselinux1 3.1-3 ii zlib1g 1:1.2.11.dfsg-2 Versions of packages libglib2.0-0 recommends: pn libglib2.0-data ii shared-mime-info 2.0-1 ii xdg-user-dirs 0.17-2 libglib2.0-0 suggests no packages. -- no debconf information
Bug#993232: lxc: Cannot add ipv4 gateway for network device "eth0" when not bringing up the interface.
Attached lxc-net, lxc-config and ifconfig-lxcbr0.txt for reference, thanks. (let me know, if need any/more information) Regards, John. On 8/29/21 12:23 PM, John wrote: Package: lxc Version: 1:4.0.10-1 Severity: normal X-Debbugs-Cc: jo...@wonghome.net Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** After upgraded lxc from 4.0.6-2 to 4.0.10-1. lxc container cannot start. I find the error with "lxc-start -l trace" like below: network.c:lxc_network_setup_in_child_namespaces_common:3894 - Cannot add ipv4 gateway for network device "eth0" when not bringing up the interface network.c:lxc_setup_network_in_child_namespaces:4038 - Function not implemented - Failed to setup netdev conf.c:lxc_setup:4080 - Failed to setup network start.c:do_start:1291 - Failed to setup container "vbox" If I rollback to 4.0.6-2, everything work fine as before. If I remove the line "lxc.net.0.ipv4.gateway = 10.0.3.1" in "/var/lib/lxc/vbox/config" (container config), the container can start again, but result no network , only loopback interface (lo) in container (no eth0 in container). Thanks. * What led up to the situation? * What exactly did you do (or not do) that was effective (or ineffective)? * What was the outcome of this action? * What outcome did you expect instead? *** End of the template - remove these template lines *** -- System Information: Debian Release: bookworm/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 5.10.0-8-cloud-amd64 (SMP w/2 CPU threads) 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 lxc depends on: ii bridge-utils 1.7-1 ii debconf [debconf-2.0]1.5.77 ii dnsmasq-base [dnsmasq-base] 2.85-1 ii iproute2 5.13.0-2 ii iptables 1.8.7-1 ii libc62.31-17 ii libcap2 1:2.44-1 ii libgcc-s111.2.0-3 ii liblxc1 1:4.0.10-1 ii libseccomp2 2.5.1-1 ii libselinux1 3.1-3 ii lsb-base 11.1.0 Versions of packages lxc recommends: ii apparmor 2.13.6-10 pn debootstrap pn dirmngr pn gnupg pn libpam-cgfs pn lxc-templates ii lxcfs 4.0.7-1 ii openssl1.1.1l-1 pn rsync pn uidmap ii wget 1.21-1+b1 Versions of packages lxc suggests: pn btrfs-progs pn lvm2 pn python3-lxc -- Configuration Files: /etc/default/lxc-net changed: USE_LXC_BRIDGE="true" LXC_BRIDGE="lxcbr0" LXC_ADDR="10.0.3.1" LXC_NETMASK="255.255.255.0" LXC_NETWORK="10.0.3.0/24" LXC_DHCP_RANGE="10.0.3.2,10.0.3.254" LXC_DHCP_MAX="253" LXC_DHCP_CONFILE="" LXC_DOMAIN="" -- debconf information: lxc/auto_update_config: lxcbr0: flags=4099 mtu 1500 inet 10.0.3.1 netmask 255.255.255.0 broadcast 10.0.3.255 ether 00:16:3e:00:00:00 txqueuelen 1000 (Ethernet) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 # Template used to create this container: /usr/share/lxc/templates/lxc-download # Parameters passed to the template: # Template script checksum (SHA-1): 273c51343604eb85f7e294c8da0a5eb769d648f3 # For additional config options, please look at lxc.container.conf(5) # Uncomment the following line to support nesting containers: #lxc.include = /usr/share/lxc/config/nesting.conf # (Be aware this has security implications) # Distribution configuration lxc.include = /usr/share/lxc/config/common.conf lxc.include = /usr/share/lxc/config/userns.conf lxc.arch = linux64 lxc.tty.dir = # Container specific configuration #lxc.apparmor.profile = lxc-container-default-cgns-local lxc.apparmor.profile = generated lxc.apparmor.allow_nesting = 0 lxc.rootfs.path = dir:/var/lib/lxc/vbox/rootfs lxc.uts.name = vbox # Container specific configuration lxc.start.auto = 1 lxc.start.delay = 0 lxc.idmap = u 0 30 65536 lxc.idmap = g 0 30 65536 lxc.cap.drop = sys_module mac_admin mac_override sys_time mknod net_raw sys_rawio sys_admin lxc.no_new_privs = 1 # Network configuration lxc.net.0.flags = up lxc.net.0.type = veth lxc.net.0.link = lxcbr0 lxc.net.0.hwaddr = 00:16:3e:00:00:03 lxc.net.0.ipv4.address = 10.0.3.3/24 lxc.net.0.ipv4.gateway = 10.0.3.1 lxc.cgroup2.memory.max = 800M lxc.hook.pre-start = /var/lib/lxc/vbox/pre-start.sh lxc.mount.entry = proc proc proc rw,remount,nodev,nosuid,noexec,relatime,hidepid=2,gid=0 0 0 lxc.mount.entry = tmpfs run tmpfs rw,nosuid,nodev,noexec,relatime,mode=0755,size=100M,create=dir 0 0 lxc.mount.entry = tmpfs
Bug#978065: lxc: After upgrade lxc to 4.0.5-1, cannot start with lxc.cap.drop sys_admin
Package: lxc
Version: 1:4.0.5-1
Severity: normal
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
As title, rollback to previous version or remove
"lxc.cap.drop=sys_admin" solved the issue.
I found this error in debug.log
conf - conf.c:lxc_mount_auto_mounts:728 - Invalid cross-device
link - Failed to mount "/sys/fs/cgroup"
* What led up to the situation?
* What exactly did you do (or not do) that was effective (or
ineffective)?
* What was the outcome of this action?
* What outcome did you expect instead?
*** End of the template - remove these template lines ***
-- System Information:
Debian Release: bullseye/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 5.9.0-5-amd64 (SMP w/8 CPU threads)
Kernel taint flags: TAINT_WARN
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8),
LANGUAGE=en_US:en
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages lxc depends on:
ii debconf [debconf-2.0] 1.5.74
ii libc6 2.31-6
ii libcap21:2.44-1
ii libgcc-s1 10.2.1-3
ii liblxc11:4.0.5-1
ii libseccomp22.5.1-1
ii libselinux13.1-2+b2
ii lsb-base 11.1.0
Versions of packages lxc recommends:
ii apparmor 2.13.5-1+b2
ii bridge-utils 1.6-3
pn debootstrap
ii dirmngr2.2.20-1
pn dnsmasq-base
ii gnupg 2.2.20-1
ii iproute2 5.10.0-1
pn libpam-cgfs
ii lxc-templates 3.0.4-4
ii lxcfs 4.0.5-1
ii nftables 0.9.7-1
ii openssl1.1.1i-1
ii rsync 3.2.3-3
pn uidmap
Versions of packages lxc suggests:
ii btrfs-progs 5.9-1+b1
ii lvm2 2.03.10-1
ii python3-lxc 1:3.0.4-1+b4
-- Configuration Files:
/etc/apparmor.d/usr.bin.lxc-start changed:
/usr/bin/lxc-start flags=(attach_disconnected) {
#include
mount options=(rw, bind) -> /proc/sys/kernel/random/boot_id,
mount options=(ro, nosuid, nodev, noexec, remount, bind) ->
/proc/sys/kernel/random/boot_id,
}
/etc/default/lxc-net changed:
USE_LXC_BRIDGE="false"
/etc/lxc/default.conf changed:
lxc.net.0.type = veth
lxc.net.0.link = lxcbr0
lxc.net.0.flags = up
lxc.apparmor.profile = generated
lxc.apparmor.allow_nesting = 0
-- debconf information:
lxc/auto_update_config:
Bug#966238: tigervnc-xorg-extension: libvnc.so cannot load
Package: tigervnc-xorg-extension Version: 1.10.1+dfsg-6 Severity: important Dear Maintainer, After upgrade tigervnc-xorg-extension to 1.10.1+dfsg-6, libvnc.so cannot load. And the error message in Xorg.log like this: "(EE) Failed to load /usr/lib/xorg/modules/extensions/libvnc.so: /usr/lib/xorg/modules/extensions/libvnc.so: undefined symbol: gnutls_sec_param_to_pk_bits" It work well before, please help, thanks. *** 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 the outcome of this action? * What outcome did you expect instead? *** End of the template - remove these template lines *** -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 5.7.0-1-amd64 (SMP w/8 CPU threads) Kernel taint flags: TAINT_WARN Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages tigervnc-xorg-extension depends on: ii libc6 2.31-2 ii libgcc-s1 10.1.0-6 ii libstdc++6 10.1.0-6 ii xserver-xorg-core 2:1.20.8-2 Versions of packages tigervnc-xorg-extension recommends: pn tigervnc-common tigervnc-xorg-extension suggests no packages.
Bug#964236: php-redis: After upgrade to php-redis (5.3.0+4.3.0-1), php-fpm crash
Package: php-redis Version: After upgrade to php-redis (5.3.0+4.3.0-1), php-fpm crash Severity: normal Dear Maintainer, After upgrade to php-redis (5.3.0+4.3.0-1), php-fpm crash. traps: php-fpm7.4[198823] general protection fault ip:55da0ea4c634 sp:7ffc14657008 error:0 in php-fpm7.4[55da0e8a8000+268000] php-fpm7.4[198824]: segfault at 10001 ip 55da0ea4b3b6 sp 7ffc14656fb8 error 4 in php-fpm7.4[55da0e8a8000+268000] Code: 85 8b 7a e7 ff 48 8b 47 10 48 83 c0 38 48 39 47 18 48 89 c2 48 89 47 10 48 0f 43 57 18 48 8b 47 50 48 89 57 18 48 85 c0 74 0a <48> 8b 10 48 89 57 50 c3 66 90 be 06 00 00 00 e9 96 e5 ff f f 66 0f Please help, thank you. *** 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 the outcome of this action? * What outcome did you expect instead? *** End of the template - remove these template lines *** -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 5.7.0-1-amd64 (SMP w/8 CPU cores) Kernel taint flags: TAINT_WARN Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
Bug#963601: chromium: Can not upgrade chromium
Package: chromium
Version: 81.0.4044.92-1
Severity: normal
Dear Maintainer,
How to solve the depend issue? Thanks.
sudo apt install chromium
Reading package lists... Done
Building dependency tree
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:
The following packages have unmet dependencies:
chromium : Depends: libavcodec58 (>= 7:4.2)
libavformat58 : Depends: libavcodec58 (= 7:4.3-2)
Depends: libchromaprint1 (>= 1.3.2) but it is
not going to be installed
E: Unable to correct problems, you have held
broken packages.
*** 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 the outcome of this action?
* What outcome did you expect instead?
*** End of the template - remove these template lines ***
-- System Information:
Debian Release: bullseye/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 5.6.0-2-amd64 (SMP w/8 CPU cores)
Kernel taint flags: TAINT_CRAP
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8),
LANGUAGE=en_US:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages chromium depends on:
ii chromium-common 81.0.4044.92-1
ii libasound2 1.2.2-2.2
ii libatk-bridge2.0-0 2.34.1-3
ii libatk1.0-0 2.36.0-2
ii libatspi2.0-02.36.0-2
ii libavcodec58 7:4.3-2
ii libavformat587:4.3-2
ii libavutil56 7:4.3-2
ii libc62.30-8
ii libcairo21.16.0-4
ii libcups2 2.3.3-1
ii libdbus-1-3 1.12.18-1
ii libdrm2 2.4.102-1
ii libevent-2.1-7 2.1.11-stable-1
ii libexpat12.2.9-1
ii libflac8 1.3.3-1
ii libfontconfig1 2.13.1-4.2
ii libfreetype6 2.10.1-2
ii libgbm1 20.1.1-1
ii libgcc-s110.1.0-4
ii libgdk-pixbuf2.0-0 2.40.0+dfsg-5
ii libglib2.0-0 2.64.3-1
ii libgtk-3-0 3.24.20-1
ii libharfbuzz0b2.6.7-1
ii libicu63 63.2-3
ii libjpeg62-turbo 1:1.5.2-2+b1
ii libjsoncpp1 1.7.4-3.1
ii liblcms2-2 2.9-4+b1
ii libminizip1 1.1-8+b1
ii libnspr4 2:4.25-1
ii libnss3 2:3.53.1-1
ii libopenjp2-7 2.3.1-1
ii libopus0 1.3-1+b1
ii libpango-1.0-0 1.44.7-4
ii libpangocairo-1.0-0 1.44.7-4
ii libpng16-16 1.6.37-2
ii libpulse013.0-5
ii libre2-6 20200401+dfsg-1
ii libsnappy1v5 1.1.8-1
ii libstdc++6 10.1.0-4
ii libvpx6 1.8.2-1
ii libwebp6 0.6.1-2+b1
ii libwebpdemux20.6.1-2+b1
ii libwebpmux3 0.6.1-2+b1
ii libx11-6 2:1.6.9-2+b1
ii libx11-xcb1 2:1.6.9-2+b1
ii libxcb-dri3-01.14-2
ii libxcb1 1.14-2
ii libxcomposite1 1:0.4.5-1
ii libxcursor1 1:1.2.0-2
ii libxdamage1 1:1.1.5-2
ii libxext6 2:1.3.3-1+b2
ii libxfixes3 1:5.0.3-2
ii libxi6 2:1.7.10-1
ii libxml2 2.9.10+dfsg-5+b1
ii libxrandr2 2:1.5.1-1
ii libxrender1 1:0.9.10-1
ii libxslt1.1 1.1.34-4
ii libxss1 1:1.2.3-1
ii libxtst6 2:1.2.3-1
ii zlib1g 1:1.2.11.dfsg-2
Versions of packages chromium recommends:
ii chromium-sandbox 81.0.4044.92-1
Versions of packages chromium suggests:
pn chromium-driver
pn chromium-l10n
pn chromium-shell
Versions of packages chromium-common depends on:
ii x11-utils 7.7+5
ii xdg-utils 1.1.3-2
Versions of packages chromium-common recommends:
ii chromium-sandbox 81.0.4044.92-1
pn fonts-liberation
ii libgl1-mesa-dri 20.1.1-1
pn libu2f-udev
pn system-config-printer
ii upower 0.99.11-2
ii xfce4-notifyd [notification-daemon] 0.4.4-1+b1
Versions of packages chromium-sandbox depends on:
ii libc6 2.30-8
-- Configuration Files:
/etc/chromium/master_preferences changed:
{
"distribution": {
"import_bookmarks": false,
"import_bookmarks_from_file": "/etc/chromium/initial_bookmarks.html",
"make_chrome_default": false,
"make_chrome_default_for_user": false,
"verbose_logging": true,
"skip_first_run_ui": true,
Bug#963175: chromium: Chromium crash on https://novnc.com/noVNC/vnc.html
Package: chromium
Version: 81.0.4044.92-1
Severity: normal
Dear Maintainer,
I noticed chromium crash on https://novnc.com/noVNC/vnc.html,
after upgrade
libavcodec58:amd64 to 7:4.3-2
libavformat58:amd64 to 7:4.3-2
libavutil56:amd64 to 7:4.3-2
Please help, thank you.
*** 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 the outcome of this action?
* What outcome did you expect instead?
*** End of the template - remove these template lines ***
-- System Information:
Debian Release: bullseye/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 5.6.0-2-amd64 (SMP w/8 CPU cores)
Kernel taint flags: TAINT_CRAP
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8),
LANGUAGE=en_US:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages chromium depends on:
ii chromium-common 81.0.4044.92-1
ii libasound2 1.2.2-2.2
ii libatk-bridge2.0-0 2.34.1-3
ii libatk1.0-0 2.36.0-2
ii libatspi2.0-02.36.0-2
ii libavcodec58 7:4.3-2
ii libavformat587:4.3-2
ii libavutil56 7:4.3-2
ii libc62.30-8
ii libcairo21.16.0-4
ii libcups2 2.3.3-1
ii libdbus-1-3 1.12.18-1
ii libdrm2 2.4.101-2
ii libevent-2.1-7 2.1.11-stable-1
ii libexpat12.2.9-1
ii libflac8 1.3.3-1
ii libfontconfig1 2.13.1-4.2
ii libfreetype6 2.10.1-2
ii libgbm1 20.1.1-1
ii libgcc-s110.1.0-4
ii libgdk-pixbuf2.0-0 2.40.0+dfsg-5
ii libglib2.0-0 2.64.3-1
ii libgtk-3-0 3.24.20-1
ii libharfbuzz0b2.6.7-1
ii libicu63 63.2-3
ii libjpeg62-turbo 1:1.5.2-2+b1
ii libjsoncpp1 1.7.4-3.1
ii liblcms2-2 2.9-4+b1
ii libminizip1 1.1-8+b1
ii libnspr4 2:4.25-1
ii libnss3 2:3.53-1
ii libopenjp2-7 2.3.1-1
ii libopus0 1.3-1+b1
ii libpango-1.0-0 1.44.7-4
ii libpangocairo-1.0-0 1.44.7-4
ii libpng16-16 1.6.37-2
ii libpulse013.0-5
ii libre2-6 20200401+dfsg-1
ii libsnappy1v5 1.1.8-1
ii libstdc++6 10.1.0-4
ii libvpx6 1.8.2-1
ii libwebp6 0.6.1-2+b1
ii libwebpdemux20.6.1-2+b1
ii libwebpmux3 0.6.1-2+b1
ii libx11-6 2:1.6.9-2+b1
ii libx11-xcb1 2:1.6.9-2+b1
ii libxcb-dri3-01.14-2
ii libxcb1 1.14-2
ii libxcomposite1 1:0.4.5-1
ii libxcursor1 1:1.2.0-2
ii libxdamage1 1:1.1.5-2
ii libxext6 2:1.3.3-1+b2
ii libxfixes3 1:5.0.3-2
ii libxi6 2:1.7.10-1
ii libxml2 2.9.10+dfsg-5+b1
ii libxrandr2 2:1.5.1-1
ii libxrender1 1:0.9.10-1
ii libxslt1.1 1.1.34-4
ii libxss1 1:1.2.3-1
ii libxtst6 2:1.2.3-1
ii zlib1g 1:1.2.11.dfsg-2
Versions of packages chromium recommends:
ii chromium-sandbox 81.0.4044.92-1
Versions of packages chromium suggests:
pn chromium-driver
pn chromium-l10n
pn chromium-shell
Versions of packages chromium-common depends on:
ii x11-utils 7.7+5
ii xdg-utils 1.1.3-2
Versions of packages chromium-common recommends:
ii chromium-sandbox 81.0.4044.92-1
pn fonts-liberation
ii libgl1-mesa-dri 20.1.1-1
pn libu2f-udev
pn system-config-printer
ii upower 0.99.11-2
ii xfce4-notifyd [notification-daemon] 0.4.4-1+b1
Versions of packages chromium-sandbox depends on:
ii libc6 2.30-8
-- Configuration Files:
/etc/chromium/master_preferences changed:
{
"distribution": {
"import_bookmarks": false,
"import_bookmarks_from_file": "/etc/chromium/initial_bookmarks.html",
"make_chrome_default": false,
"make_chrome_default_for_user": false,
"verbose_logging": true,
"skip_first_run_ui": true,
"create_all_shortcuts": true,
"suppress_first_run_default_browser_prompt": true
},
"browser": {
"show_home_button": true,
"has_seen_welcome_page" : true,
"check_default_browser" : false
},
"profile": {
"default_content_setting_values": {
"payment_handler": 2
}
},
"bookmark_bar": {
"show_on_all_tabs": true
},
"net": {
"network_prediction_options": 2
},
"search": {
"suggest_enabled": false
},
"signin": {
"allowed": false,
"allowed_on_next_startup": false
},
"autofill": {
"profile_enabled": false,
"credit_card_enabled": false
},
"payments": {
"can_make_payment_enabled":
Bug#956502: docker: Error response from daemon: no status provided on response: unknown.
Package: docker.io Version: 19.03.6+dfsg1-3 Severity: important Dear Maintainer, After upgrade docker.io to 19.03.6+dfsg1-3 today, container cannot start, and show the error message like below: docker: Error response from daemon: no status provided on response: unknown. Downgrade to 19.03.6+dfsg1-2 solved the issue. Thanks. *** 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 the outcome of this action? * What outcome did you expect instead? *** End of the template - remove these template lines *** -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 5.5.0-1-amd64 (SMP w/8 CPU cores) Kernel taint flags: TAINT_CRAP Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages docker.io depends on: ii adduser 3.118 pn iptables ii libc6 2.30-4 ii libdevmapper1.02.1 2:1.02.167-1+b1 ii libltdl72.4.6-14 ii libnspr42:4.25-1 ii libnss3 2:3.51-1 ii libseccomp2 2.4.3-1 ii libsystemd0 245.4-3 ii lsb-base11.1.0 pn runc pn tini Versions of packages docker.io recommends: ii ca-certificates 20190110 pn cgroupfs-mount pn git pn needrestart ii xz-utils 5.2.4-1+b1 Versions of packages docker.io suggests: pn aufs-tools ii btrfs-progs 5.6-1 pn debootstrap pn docker-doc ii e2fsprogs1.45.6-1 pn rinse pn xfsprogs pn zfs-fuse | zfsutils
Bug#951847: php-imagick: Please support php7.4
Package: php-imagick Version: 3.4.4-1 Severity: wishlist Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** As title said, please support php7.4, since it is the default version of php on sid, thanks. * What led up to the situation? * What exactly did you do (or not do) that was effective (or ineffective)? * What was the outcome of this action? * What outcome did you expect instead? *** End of the template - remove these template lines *** -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 5.4.0-4-amd64 (SMP w/4 CPU cores) Kernel taint flags: TAINT_CRAP Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages php-imagick depends on: ii libc6 2.29-10 pn libmagickcore-6.q16-6 pn libmagickwand-6.q16-6 pn php-common pn phpapi-20180731 Versions of packages php-imagick recommends: pn ghostscript pn ttf-dejavu-core php-imagick suggests no packages.
Bug#951852: php-igbinary: Please support php7.4
Package: php-igbinary Version: 3.0.0-1 Severity: wishlist Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** As title said, please support php7.4, since it is the default version of php on sid, thanks. * What led up to the situation? * What exactly did you do (or not do) that was effective (or ineffective)? * What was the outcome of this action? * What outcome did you expect instead? *** End of the template - remove these template lines *** -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 5.4.0-4-amd64 (SMP w/4 CPU cores) Kernel taint flags: TAINT_CRAP Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages php-igbinary depends on: ii libc62.29-10 pn php-common pn phpapi-20180731 php-igbinary recommends no packages. php-igbinary suggests no packages.
Bug#951849: php-gnupg: Please support php7.4
Package: php-gnupg Version: 1.4.0-3 Severity: wishlist Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** As title said, please support php7.4, since it is the default version of php on sid, thanks. * What led up to the situation? * What exactly did you do (or not do) that was effective (or ineffective)? * What was the outcome of this action? * What outcome did you expect instead? *** End of the template - remove these template lines *** -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 5.4.0-4-amd64 (SMP w/4 CPU cores) Kernel taint flags: TAINT_CRAP Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages php-gnupg depends on: ii libc62.29-10 ii libgpgme11 1.13.1-6 pn php-common pn phpapi-20180731 ii ucf 3.0038+nmu1 php-gnupg recommends no packages. php-gnupg suggests no packages.
Bug#951845: php-redis: Please support php7.4, since it is the default php version on sid
Package: php-redis Severity: wishlist Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** As title said, please support php7.4, since it is the default version of php on sid, thanks. * What led up to the situation? * What exactly did you do (or not do) that was effective (or ineffective)? * What was the outcome of this action? * What outcome did you expect instead? *** End of the template - remove these template lines *** -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 5.4.0-4-amd64 (SMP w/4 CPU cores) Kernel taint flags: TAINT_CRAP Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages php-redis depends on: ii libc62.29-10 pn php-common pn php-igbinary pn phpapi-20180731 php-redis recommends no packages. Versions of packages php-redis suggests: pn redis-server
Bug#942886: linux-image-5.3.0-1-amd64: Can not modprobe "snd_hda_codec_hdmi"
Package: src:linux Version: 5.3.7-1 Severity: important Dear Maintainer, After upgrade kernel to linux-image-5.3.0-1-amd64, I can not modprobe "snd_hda_codec_hdmi" any more, it show the error message, modprobe: ERROR: could not insert 'snd_hda_codec_hdmi': Key was rejected by service and my monitor no sound output. Please help, thank you. *** 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 the outcome of this action? * What outcome did you expect instead? *** End of the template - remove these template lines *** -- Package-specific info: ** Version: Linux version 5.3.0-1-amd64 (debian-ker...@lists.debian.org) (gcc version 9.2.1 20191008 (Debian 9.2.1-9)) #1 SMP Debian 5.3.7-1 (2019-10-19) ** Command line: BOOT_IMAGE=/vmlinuz-5.3.0-1-amd64 root=/dev/mapper/nvme0n1p1_crypt ro rootflags=subvol=rootfs apparmor=1 security=apparmor nosmt rootfstype=btrfs rootflags=subvol=rootfs quiet ** Not tainted ** Kernel log: [7.126154] bridge: filtering via arp/ip/ip6tables is no longer available by default. Update your scripts to load br_netfilter if you need this. [7.127219] snd_hda_codec_generic hdaudioC0D0: autoconfig for Generic: line_outs=0 (0x0/0x0/0x0/0x0/0x0) type:line [7.127221] snd_hda_codec_generic hdaudioC0D0:speaker_outs=0 (0x0/0x0/0x0/0x0/0x0) [7.127222] snd_hda_codec_generic hdaudioC0D0:hp_outs=0 (0x0/0x0/0x0/0x0/0x0) [7.127222] snd_hda_codec_generic hdaudioC0D0:mono: mono_out=0x0 [7.127223] snd_hda_codec_generic hdaudioC0D0:dig-out=0x3/0x0 [7.127223] snd_hda_codec_generic hdaudioC0D0:inputs: [7.127667] input: HDA Intel HDMI HDMI as /devices/pci:00/:00:03.0/sound/card0/input17 [7.153862] EXT4-fs (sdb1): mounted filesystem with ordered data mode. Opts: (null) [7.181175] Rounding down aligned max_sectors from 4294967295 to 4294967288 [7.181662] db_root: cannot open: /etc/target [7.245336] Adding 1952764k swap on /dev/mapper/swap. Priority:-2 extents:1 across:1952764k SSFS [7.279906] bcache: bch_journal_replay() journal replay done, 177 keys in 12 entries, seq 6365286 [7.289114] bcache: bch_cached_dev_attach() Caching sda1 as bcache0 on set 3ec1b954-b969-438d-b264-91a36d2a1a4c [7.289136] bcache: register_cache() registered cache device dm-5 [7.298596] intel_rapl_common: Found RAPL domain package [7.298598] intel_rapl_common: Found RAPL domain core [7.298598] intel_rapl_common: Found RAPL domain uncore [7.298599] intel_rapl_common: Found RAPL domain dram [ 11.171939] BTRFS: device fsid b6b55d64-9811-4f26-9d77-f5af7750193f devid 1 transid 2690791 /dev/dm-8 [ 11.189503] BTRFS info (device dm-8): enabling ssd optimizations [ 11.189504] BTRFS info (device dm-8): turning on discard [ 11.189507] BTRFS info (device dm-8): use lzo compression, level 0 [ 11.189508] BTRFS info (device dm-8): disk space caching is enabled [ 11.189509] BTRFS info (device dm-8): has skinny extents [ 11.269858] audit: type=1400 audit(1571773003.787:2): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/sbin/tcpdump" pid=949 comm="apparmor_parser" [ 11.270455] audit: type=1400 audit(1571773003.787:3): apparmor="STATUS" operation="profile_load" profile="unconfined" name="transmission" pid=950 comm="apparmor_parser" [ 11.270943] audit: type=1400 audit(1571773003.787:4): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/bin/gpicview" pid=948 comm="apparmor_parser" [ 11.272458] audit: type=1400 audit(1571773003.787:5): apparmor="STATUS" operation="profile_load" profile="unconfined" name="un-archiver" pid=951 comm="apparmor_parser" [ 11.272475] audit: type=1400 audit(1571773003.787:6): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/bin/wget" pid=952 comm="apparmor_parser" [ 11.274990] audit: type=1400 audit(1571773003.791:7): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/bin/xarchiver" pid=953 comm="apparmor_parser" [ 11.275621] audit: type=1400 audit(1571773003.791:8): apparmor="STATUS" operation="profile_load" profile="unconfined" name="rsyslogd" pid=954 comm="apparmor_parser" [ 11.276773] audit: type=1400 audit(1571773003.791:9): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/bin/filezilla" pid=955 comm="apparmor_parser" [ 11.277188] audit: type=1400 audit(1571773003.795:10): apparmor="STATUS" operation="profile_load" profile="unconfined" name="libreoffice-oopslash" pid=956 comm="apparmor_parser" [ 11.278016] audit: type=1400 audit(1571773003.795:11): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/bin/pavucontrol" pid=957 comm="apparmor_parser" [ 11.463897] new mount options do not match the existing superblock, will be
Bug#934387: lxc: I have this problem too, any plan to backport?
Package: lxc Version: 1:3.1.0+really3.0.4-1 Followup-For: Bug #934387 Dear Maintainer, I have this problem too, any plan to backport the fix? Thanks. *** 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 the outcome of this action? * What outcome did you expect instead? *** End of the template - remove these template lines *** -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 5.2.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages lxc depends on: ii debconf [debconf-2.0] 1.5.73 ii libc6 2.28-10 ii libcap21:2.25-2 ii libgcc11:9.2.1-1 ii liblxc11:3.1.0+really3.0.4-1 ii libseccomp22.4.1-2 ii libselinux12.9-2+b2 ii lsb-base 11.0.1 Versions of packages lxc recommends: ii apparmor 2.13.3-4 ii bridge-utils 1.6-2 pn debootstrap ii dirmngr2.2.17-3 pn dnsmasq-base ii gnupg 2.2.17-3 ii iproute2 5.2.0-1 pn libpam-cgfs ii lxc-templates 3.0.3-1+b1 ii lxcfs 3.0.4-2 ii nftables 0.9.1-2+b1 ii openssl1.1.1c-1 ii rsync 3.1.3-6+b1 pn uidmap Versions of packages lxc suggests: ii btrfs-progs 5.2.1-1 ii lvm2 2.03.02-3 ii python3-lxc 1:3.0.3-1+b1 -- debconf information excluded
Bug#917124: udev 240-1 break my system too
On 12/24/18 12:58 PM, John Wong wrote: > Yes, udev 240-1 break my lvm2 system. > Hi, replace /lib/systemd/systemd-udevd with udev version 239's (/lib/systemd/systemd-udevd), then update-initramfs -u. I can boot my system again. -- Key fingerprint: CDB3 6C62 254B C088 1E5D DD32 182C 97DB CF2C 80AC
Bug#917124: udev 240-1 break my system too
Yes, udev 240-1 break my lvm2 system. -- Key fingerprint: CDB3 6C62 254B C088 1E5D DD32 182C 97DB CF2C 80AC
Bug#912840: linux-image-4.18.0-2-amd64: kernel 4.18 with core2 cpu break kvm/qemu
Package: src:linux Version: 4.18.10-2+b1 Severity: normal Dear Maintainer, I have a system with intel core2 cpu, running kvm/qemu (host), after upgrade to 4.18 kernel, (both linux-image-4.18.0-1-amd64 or linux-image-4.18.0-2-amd64), then some kvm/qemu quest can not boot. I think the system hit the bug. https://www.spinics.net/lists/kvm/msg175557.html https://patchwork.kernel.org/patch/10614795/ Could you like to backport the patch, or upgrade the kernel version to 4.18.16/4.19? Thanks.
Bug#908223: lxc: Can not start unprivileged LXC containers with 4.18 kernel
Package: lxc Version: 1:2.0.9-6.1 Severity: normal Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** After upgrade kernel to linux-image-4.18.0-1-amd64, I can not start unprivileged LXC containers, Maybe related to this one "https://lists.linuxfoundation.org/pipermail/containers/2018-June/039174.html;, and "https://github.com/lxc/lxc/pull/2438;. Please help and thank you. * What led up to the situation? * What exactly did you do (or not do) that was effective (or ineffective)? * What was the outcome of this action? * What outcome did you expect instead? *** End of the template - remove these template lines *** -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 4.18.0-1-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages lxc depends on: ii libapparmor1 2.13-8 ii libc6 2.27-6 ii libcap2 1:2.25-1.2 ii libgnutls30 3.5.19-1 ii liblxc1 1:2.0.9-6.1 ii libseccomp2 2.3.3-3 ii libselinux1 2.8-1+b1 ii lsb-base 9.20170808 ii python3 3.6.6-1 ii python3-lxc 1:2.0.9-6.1 Versions of packages lxc recommends: ii bridge-utils 1.5-16 pn debootstrap ii dirmngr 2.2.10-1 pn dnsmasq-base ii gnupg 2.2.10-1 ii iptables 1.6.2-1.1 pn libpam-cgfs pn lxcfs ii openssl 1.1.1~~pre9-1 ii rsync 3.1.2-2.2 pn uidmap Versions of packages lxc suggests: ii apparmor 2.13-8 ii btrfs-progs 4.17-1 pn lvm2 -- no debconf information
Bug#908192: linux-image-4.18.0-1-amd64: After upgrade kernel to linux-image-4.18.0-1-amd64, LXC can not start
Package: src:linux Version: 4.18.6-1 Severity: normal Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** As title, after upgrade to linux-image-4.18.0-1-amd64, lxc can not start, If boot to old kernel (4.17-3..), lxc can start again. * What led up to the situation? * What exactly did you do (or not do) that was effective (or ineffective)? * What was the outcome of this action? * What outcome did you expect instead? *** End of the template - remove these template lines *** -- Package-specific info: ** Version: Linux version 4.18.0-1-amd64 (debian-ker...@lists.debian.org) (gcc version 7.3.0 (Debian 7.3.0-29)) #1 SMP Debian 4.18.6-1 (2018-09-06) ** Command line: BOOT_IMAGE=/boot/vmlinuz-4.18.0-1-amd64 root=UUID=5cb16262-d214-4feb-9369-81a291a2388b ro apparmor=1 security=apparmor quiet ** Not tainted ** Kernel log: ** Model information [ 50.617580] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready [ 50.617598] lxcbr0: port 2(veth471YAX) entered blocking state [ 50.617599] lxcbr0: port 2(veth471YAX) entered forwarding state [ 50.633435] lxcbr0: port 2(veth471YAX) entered disabled state [ 50.633527] device veth471YAX left promiscuous mode [ 50.633528] lxcbr0: port 2(veth471YAX) entered disabled state [ 111.648345] lxcbr0: port 2(vethMT2FWQ) entered blocking state [ 111.648347] lxcbr0: port 2(vethMT2FWQ) entered disabled state [ 111.648372] device vethMT2FWQ entered promiscuous mode [ 111.651743] lxcbr0: port 2(vethMT2FWQ) entered disabled state [ 111.651866] device vethMT2FWQ left promiscuous mode [ 111.651867] lxcbr0: port 2(vethMT2FWQ) entered disabled state [ 221.679794] lxcbr0: port 2(vethYPTVY4) entered blocking state [ 221.679795] lxcbr0: port 2(vethYPTVY4) entered disabled state [ 221.679821] device vethYPTVY4 entered promiscuous mode [ 221.701044] eth0: renamed from vethHEA5JH [ 221.724082] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready [ 221.725177] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready [ 221.725196] lxcbr0: port 2(vethYPTVY4) entered blocking state [ 221.725197] lxcbr0: port 2(vethYPTVY4) entered forwarding state [ 221.740431] lxcbr0: port 2(vethYPTVY4) entered disabled state [ 221.740526] device vethYPTVY4 left promiscuous mode [ 221.740527] lxcbr0: port 2(vethYPTVY4) entered disabled state [ 229.743698] lxcbr0: port 2(vethG6VBDH) entered blocking state [ 229.743699] lxcbr0: port 2(vethG6VBDH) entered disabled state [ 229.743727] device vethG6VBDH entered promiscuous mode [ 229.769070] eth0: renamed from vethESL89I [ 229.791893] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready [ 229.792987] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready [ 229.793003] lxcbr0: port 2(vethG6VBDH) entered blocking state [ 229.793004] lxcbr0: port 2(vethG6VBDH) entered forwarding state [ 229.804473] lxcbr0: port 2(vethG6VBDH) entered disabled state [ 229.804572] device vethG6VBDH left promiscuous mode [ 229.804573] lxcbr0: port 2(vethG6VBDH) entered disabled state [ 252.543415] lxcbr0: port 2(vethQTK7VL) entered blocking state [ 252.543416] lxcbr0: port 2(vethQTK7VL) entered disabled state [ 252.543442] device vethQTK7VL entered promiscuous mode [ 252.573029] eth0: renamed from veth8J8RJX [ 252.587882] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready [ 252.589098] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready [ 252.589115] lxcbr0: port 2(vethQTK7VL) entered blocking state [ 252.589116] lxcbr0: port 2(vethQTK7VL) entered forwarding state [ 252.600700] lxcbr0: port 2(vethQTK7VL) entered disabled state [ 252.600801] device vethQTK7VL left promiscuous mode [ 252.600802] lxcbr0: port 2(vethQTK7VL) entered disabled state [ 1270.152712] lxcbr0: port 2(veth83ORBG) entered blocking state [ 1270.152713] lxcbr0: port 2(veth83ORBG) entered disabled state [ 1270.152741] device veth83ORBG entered promiscuous mode [ 1270.175792] eth0: renamed from vethXLKI4X [ 1270.199037] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready [ 1270.200115] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready [ 1270.200133] lxcbr0: port 2(veth83ORBG) entered blocking state [ 1270.200134] lxcbr0: port 2(veth83ORBG) entered forwarding state [ 1270.215342] lxcbr0: port 2(veth83ORBG) entered disabled state [ 1270.215431] device veth83ORBG left promiscuous mode [ 1270.215432] lxcbr0: port 2(veth83ORBG) entered disabled state [ 1281.911374] lxcbr0: port 2(vethWLL3H7) entered blocking state [ 1281.911375] lxcbr0: port 2(vethWLL3H7) entered disabled state [ 1281.911402] device vethWLL3H7 entered promiscuous mode [ 1281.935451] eth0: renamed from vethDVX7T8 [ 1281.946282] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready [ 1281.947522] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready [ 1281.947540] lxcbr0: port 2(vethWLL3H7) entered blocking state [ 1281.947541] lxcbr0: port 2(vethWLL3H7) entered forwarding state [ 1281.968923] lxcbr0: port 2(vethWLL3H7) entered
Bug#898824: btrfs-progs: missing libbtrfs.so.0
Package: btrfs-progs Version: 4.16.1-2 Severity: important Dear Maintainer, After upgrade to 4.16.1-2, some prog show the error message, like below: (snapper list) "snapper: error while loading shared libraries: libbtrfs.so.0: cannot open shared object file: No such file or directory" Please help, thank you. *** 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 the outcome of this action? * What outcome did you expect instead? *** End of the template - remove these template lines *** -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 4.16.0-1-amd64 (SMP w/8 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages btrfs-progs depends on: ii libblkid1 2.32-0.1 ii libc6 2.27-3 ii liblzo2-2 2.10-0.1 ii libuuid1 2.32-0.1 ii zlib1g 1:1.2.11.dfsg-1 btrfs-progs recommends no packages. Versions of packages btrfs-progs suggests: pn duperemove -- no debconf information
Bug#895100: roundcube: Remove php-mcrypt dependent
Package: roundcube Version: 1.3.3+dfsg.1-2 Severity: wishlist Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** Since php7.2 is the default debian's php's version, and php7.2 does not had php-mcrypt, So, please remove php-mcrypt dependent. Thanks. *** End of the template - remove these template lines *** -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 4.15.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages roundcube depends on: ii dpkg1.19.0.5 pn roundcube-core roundcube recommends no packages. roundcube suggests no packages.
Bug#885155: chromium: Enable audio/microphone support (Again)
Package: chromium
Version: 63.0.3239.84-1
Severity: wishlist
Dear Maintainer,
After upgrade chromium, I can not use microphone/voice search with
chromium any more,
It work well before upgrade, please help, thanks.
o< - >o
--- /usr/share/chromium/master_preferences 2017-12-04 00:05:00.0
+0800
+++ /tmp/master_preferences 2017-12-25 12:29:07.927500500 +0800
@@ -27,7 +27,7 @@
"enabled": false
},
"hardware": {
-"audio_capture_enabled": false
+"audio_capture_enabled": true
},
"default_apps": "noinstall",
"hide_web_store_icon": true,
o< - >o
-- System Information:
Debian Release: buster/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 4.14.0-1-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8), LANGUAGE=en_US:en
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages chromium depends on:
ii chromium-common 63.0.3239.84-1
ii libasound2 1.1.3-5
ii libatk1.0-0 2.26.1-2
ii libavcodec57 7:3.4.1-1+b1
ii libavformat577:3.4.1-1+b1
ii libavutil55 7:3.4.1-1+b1
ii libc62.25-5
ii libcairo21.15.8-3
ii libcups2 2.2.6-3
ii libdbus-1-3 1.12.2-1
ii libevent-2.1-6 2.1.8-stable-4
ii libexpat12.2.5-3
ii libflac8 1.3.2-1
ii libfontconfig1 2.12.6-0.1
ii libfreetype6 2.8.1-0.1
ii libgcc1 1:7.2.0-18
ii libgdk-pixbuf2.0-0 2.36.11-1
ii libglib2.0-0 2.54.2-4
ii libgtk-3-0 3.22.26-2
ii libharfbuzz0b1.7.2-1
ii libicu57 57.1-8
ii libjpeg62-turbo 1:1.5.2-2+b1
ii liblcms2-2 2.9-1
ii libminizip1 1.1-8+b1
ii libnspr4 2:4.16-1+b1
ii libnss3 2:3.34-1
ii libopus0 1.2.1-1
ii libpango-1.0-0 1.40.14-1
ii libpangocairo-1.0-0 1.40.14-1
ii libpng16-16 1.6.34-1
ii libpulse011.1-4
ii libre2-3 20170101+dfsg-1
ii libsnappy1v5 1.1.7-1
ii libstdc++6 7.2.0-18
ii libvpx4 1.6.1-3
ii libwebp6 0.6.0-4
ii libwebpdemux20.6.0-4
ii libwebpmux3 0.6.0-4
ii libx11-6 2:1.6.4-3
ii libx11-xcb1 2:1.6.4-3
ii libxcb1 1.12-1
ii libxcomposite1 1:0.4.4-2
ii libxcursor1 1:1.1.15-1
ii libxdamage1 1:1.1.4-3
ii libxext6 2:1.3.3-1+b2
ii libxfixes3 1:5.0.3-1
ii libxi6 2:1.7.9-1
ii libxml2 2.9.4+dfsg1-5.2
ii libxrandr2 2:1.5.1-1
ii libxrender1 1:0.9.10-1
ii libxslt1.1 1.1.29-5
ii libxss1 1:1.2.2-1+b2
ii libxtst6 2:1.2.3-1
ii zlib1g 1:1.2.8.dfsg-5
Versions of packages chromium recommends:
pn fonts-liberation
Versions of packages chromium suggests:
pn chromium-driver
pn chromium-l10n
pn chromium-shell
pn chromium-widevine
-- no debconf information
Bug#766581: ibus: After upgrade to 1.5.9-1, can not input chinese (class quick)
Package: ibus Version: 1.5.9-1 Severity: normal Dear Maintainer, Today(24-Oct-2014), after apt-get dist-upgrade, ibus upgrade to 1.5.9-1, I can not input any chinese any more, I use ibus-table-quick-classic. Thank you. *** 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 the outcome of this action? * What outcome did you expect instead? *** End of the template - remove these template lines *** -- Package-specific info: default-display-manager: /usr/sbin/gdm3 ibus is /usr/bin/ibus ibus-setup is /usr/bin/ibus-setup im-config -l = ibus xim im-config -m = default missing ibus XMODIFIERS=@im=ibus GTK_IM_MODULE=ibus QT4_IM_MODULE=ibus QT_IM_MODULE=ibus XDG_DATA_DIRS=/usr/share/xfce4:/usr/local/share/:/usr/share/ XDG_MENU_PREFIX= PATH=~/bin:/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games:/sbin:/usr/sbin:usr/local/sbin ls -l /usr/lib/ibus/ total 292 -rwxr-xr-x 1 root root 19088 Oct 23 00:12 ibus-dconf -rwxr-xr-x 1 root root 10576 Oct 23 00:12 ibus-engine-simple -rwxr-xr-x 1 root root 1925 Oct 24 00:10 ibus-engine-table -rwxr-xr-x 1 root root 1068 Oct 24 00:10 ibus-setup-table -rwxr-xr-x 1 root root 165048 Oct 23 00:12 ibus-ui-gtk3 -rwxr-xr-x 1 root root 89496 Oct 23 00:12 ibus-x11 -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16-3-amd64 (SMP w/8 CPU cores) Locale: LANG=zh_HK.UTF-8, LC_CTYPE=zh_HK.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages ibus depends on: ii dconf-cli0.22.0-1 ii dconf-gsettings-backend [gsettings-backend] 0.22.0-1 ii gir1.2-gtk-3.0 3.14.4-1 ii gir1.2-ibus-1.0 1.5.9-1 it gnome-icon-theme 3.12.0-1 ii libatk1.0-0 2.14.0-1 ii libc62.19-12 ii libcairo21.14.0-2 ii libdconf10.22.0-1 ii libgdk-pixbuf2.0-0 2.31.1-2+b1 ii libglib2.0-0 2.42.0-2 ii libgtk-3-0 3.14.4-1 it libgtk2.0-0 2.24.25-1 ii libibus-1.0-51.5.9-1 ii libnotify4 0.7.6-2 ii libpango-1.0-0 1.36.8-2 ii libpangocairo-1.0-0 1.36.8-2 ii librsvg2-common 2.40.5-1 ii libx11-6 2:1.6.2-3 ii libxi6 2:1.7.4-1 ii python-notify0.1.1-4 ii python3-gi 3.14.0-1 pn python3:any none Versions of packages ibus recommends: ii ibus-gtk1.5.9-1 ii ibus-gtk3 1.5.9-1 ii ibus-qt41.3.2-2 ii im-config 0.27-1 ii libqt5gui5 5.3.2+dfsg-4+b1 Versions of packages ibus suggests: ii ibus-clutter 0.0+git20090728.a936bacf-5.1+b1 pn ibus-doc none ii ibus-qt4 1.3.2-2 ii libqt5gui55.3.2+dfsg-4+b1 -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#756375: systemd-sysv: Can not normal shutdown with ulatencyd
Package: systemd-sysv Version: 208-6 Severity: normal Dear Maintainer, I want to reopen bug report (the old one number: 755375) When my system installed ulatencyd, my system can not normal shutdown, even as root. I opened the bug report, number: 755375, deveplor said: - I believe this is a configuration issue, not a bug. Please see (1) https://github.com/poelzi/ulatencyd/wiki/Faq#id4 Closing, please reopen if the problem persists after adjusting the systemd configuration as documented in the ulatencyd faq. - I tried remove /etc/ulatencyd, then reinstall ulatencyd with default setup/config (/etc/ulatencyd/*), but still can not normal shutdown. then I tried following the (1)Faq#id4 add 3 line to /etc/ulatencyd/system.conf --- DefaultControllers= JoinControllers= controllers= --- but still can not normal shutdown. then I remove ulatencyd (apt-get remove ulatencyd), my system can normal shutdown. So, I want to reopen this bug report. Thank you. -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.14-2-amd64 (SMP w/8 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages systemd-sysv depends on: ii systemd 208-6 systemd-sysv recommends no packages. systemd-sysv suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#755996: ulatencyd: Install ulatencyd with systemd can not normal shutdown (even as root)
Package: ulatencyd Version: 0.5.0-9 Severity: normal Dear Maintainer, I want to reopen bug report (the old one number: 755375) When my system installed ulatencyd, my system can not normal shutdown, even as root. I opened the bug report, number: 755375, deveplor said: - I believe this is a configuration issue, not a bug. Please see (1) https://github.com/poelzi/ulatencyd/wiki/Faq#id4 Closing, please reopen if the problem persists after adjusting the systemd configuration as documented in the ulatencyd faq. - I tried remove /etc/ulatencyd, then reinstall ulatencyd with default setup/config (/etc/ulatencyd/*), but still can not normal shutdown. then I tried following the (1)Faq#id4 add 3 line to /etc/ulatencyd/system.conf --- DefaultControllers= JoinControllers= controllers= --- but still can not normal shutdown. then I remove ulatencyd (apt-get remove ulatencyd), my system can normal shutdown. So, I want to reopen this bug report. Thank you. *** End of the template - remove these template lines *** -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.14-2-amd64 (SMP w/8 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages ulatencyd depends on: ii dbus 1.8.6-1 ii libc6 2.19-7 ii libdbus-1-31.8.6-1 ii libdbus-glib-1-2 0.102-1 ii libglib2.0-0 2.40.0-3 ii liblua5.1-05.1.5-5 ii libpolkit-gobject-1-0 0.105-6.1 ii libxau61:1.0.8-1 ii libxcb11.10-3 ii lua-posix 31-2 ii lua5.1 [lua] 5.1.5-5 Versions of packages ulatencyd recommends: ii consolekit 0.4.6-5 ulatencyd suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#755512: systemd-sysv: Can not normal /sbin/shutdown (even as root)
Package: systemd-sysv Version: 208-6 Severity: normal Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** Recently(over 2 weeks), I noticed my system can not normal shutdown, even as root (/sbin/shutdown -h now). (but not everytime, sometime can normal shutdown, but usually can not) When I type /sbin/shutdown -h now (as root), my system will exit Xorg/xfce4 to console mode, then hang on it without any response (alt-ctrl-delete, Ctrl-c), until I put the power/reset button. I see some error/warning messages in /var/log/syslog, like this when shuting down: (ulatencyd:1173): WARNING **: pid: 10735 parnet 10731 missing. attaching to pid 1 So I try to remove ulatency/ulatencyd package, after that, my system can normal shutdown everytime. My english is so bad, what I want to say is: 1. When installed ulatencyd, my system can not normal shutdown. (but not everytime) 2. when remove ulatencyd, my system can normal shutdown everytime. Thank you. ulatency/ulatencyd version is: 0.5.0-9 systemd-sysv version is: 208-6 *** End of the template - remove these template lines *** -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.14-1-amd64 (SMP w/8 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages systemd-sysv depends on: ii systemd 208-6 systemd-sysv recommends no packages. systemd-sysv suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#750844: apparmor-notify: aa-notify started but no notification
Package: apparmor-notify Version: 2.8.0-5.1 Severity: normal Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** 1. aa-notify not start up on boot (I added the user to adm group) 2. aa-notify do not notify/popup the warning messages, even some program denied by apparmor. (I can see those warning messages in /var/log/kern.log and aa-notify is running) my system is installed a two weeks, sid/64bit. aa-notify never work on this system. but my old computer(damaged) also running sid/64bit, and aa-notify well on this old computer, automatic running on system boot, and do notify the warning messages, when some program denied by apparmor. how do I find out the problem? thanks. * What led up to the situation? * What exactly did you do (or not do) that was effective (or ineffective)? * What was the outcome of this action? * What outcome did you expect instead? *** End of the template - remove these template lines *** -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 3.14-1-amd64 (SMP w/8 CPU cores) Locale: LANG=zh_HK.UTF-8, LC_CTYPE=zh_HK.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages apparmor-notify depends on: ii libapparmor-perl 2.8.0-5.1 ii libnotify-bin 0.7.6-2 ii perl 5.18.2-4 apparmor-notify recommends no packages. apparmor-notify suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#531201: Pidgin disconnects when removing a invalid MSN buddy
Package: pidgin Version: 2.5.6-1 I typed in an invalid email address for a MSN buddy, and when I try to remove it, I get: Connection error from Notification server: Reading error giving two options: Modify Account or Reconnect. If I idle a bit, it automatically reconnects. One other thing I've noticed since version 2.5.5 is the Unable to add user Unknown error (204) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#335810: gaim logging not logging closing of conversation windows
Yes, Luke. It is the notifications that a conversation was closed which is no longer being reported. John On Wed, Oct 26, 2005 at 10:18:55AM -0400, Luke Schierer wrote: On Tue, Oct 25, 2005 at 03:30:07PM -0700, John Wong wrote: Using the same prefs.xml, the updated version of gaim doesn't log the closing of conversations. It's not reported in the conversation box. Downgrading to the previous package 1.5.0-1 brought back that functionality. I am using Debian sid, kernel 2.6.13 and glibc 2.3.5-7 Are you refering to the MSN notifications that a conversation was closed by the person you are talking to? luke -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#335810: gaim logging not logging closing of conversation windows
Package: gaim Version: 1.5.0+1.5.1cvs20051015 Using the same prefs.xml, the updated version of gaim doesn't log the closing of conversations. It's not reported in the conversation box. Downgrading to the previous package 1.5.0-1 brought back that functionality. I am using Debian sid, kernel 2.6.13 and glibc 2.3.5-7 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
