[Desktop-packages] [Bug 1814465] Re: Firefox 65 cannot load Flash on trusty because of libxul.so broken dependency
According to https://hg.mozilla.org/integration/autoland/rev/6fc6bdea42a6 (associated with https://bugzilla.mozilla.org/show_bug.cgi?id=1501218), > --enable-default-toolkit=cairo-gtk3-wayland is left to _force_ wayland > support being built in, while --enable-default-toolkit=cairo-gtk3 still > allows to build against a Gtk+ version that doesn't support wayland. So FF 65/66/67/+ could potentially be built for trusty with functional linkage to Flash. ** Bug watch added: Mozilla Bugzilla #1501218 https://bugzilla.mozilla.org/show_bug.cgi?id=1501218 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1814465 Title: Firefox 65 cannot load Flash on trusty because of libxul.so broken dependency Status in firefox package in Ubuntu: Confirmed Bug description: Package: firefox 65.0+build2-0ubuntu0.14.04.1 Error message in shell: /usr/lib/firefox/plugin-container: symbol lookup error: /usr/lib/firefox/libxul.so: undefined symbol: wl_surface_interface [Parent 3419, Gecko_IOThread] WARNING: pipe error (151): Connection reset by peer: file /build/firefox-mzqi2a/firefox-65.0+build2/ipc/chromium/src/chrome/common/ipc_channel_posix.cc, line 349 Steps: 1) Run firefox 65 on Ubuntu 14.04.5 LTS in a terminal 2) Visit a flash site and no flash content is displayed 3) Look in the terminal for the libxul.so error message Note: This bug is similar to Bug #1720908 fixed in 2017 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1814465/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1677397] [NEW] lightdm-gtk-greeter SIGSEGV when invoked by Xvnc -inetd -query
Public bug reported:
To reproduce:
1. Install Xubuntu 16.04 LTS, update fully
2. Install packages xinetd, vnc4server
3. Append to /etc/services:
vnc 5900/tcp# VNC Virtual Network
Computing
4. Append to /etc/lightdm/lightdm.conf:
[XDMCPServer]
enabled=true
5. Create /etc/xinetd.d/vnc:
service vnc
{
disable = no
socket_type = stream
protocol= tcp
group = tty
wait= no
user= nobody
server = /usr/bin/Xvnc
server_args = -inetd -query localhost -once -securitytypes=none
-geometry 1024x768
}
# NOTE: might need to add an arg like ":1" to get out of way of local X server
# my case is special as I am trying to run headless, nobody is logged in on
console
6. Signal xinetd and lightdm to reconfigure:
$ sudo killall -1 xinetd
$ sudo service lightdm restart # or however your init system works
7. Don't know if significant (I am 400 miles away from test host and can't
test):
do NOT have anyone logged in on the test host console. In fact, to most closely
reproduce my case, shut down the test host, power it off, disconnect all
monitors
and keyboards, then power it on and access from the net.
8. From another system, connect to the test host:
$ gvncviewer testhost:0 # Your favorite VNC viewer & test host name...
9. VNC connects briefly, displays grey hashed background, disconnects. Syslog
on
test host says:
Mar 29 15:07:40 osmium lightdm[13828]: (lightdm:13828): GLib-GObject-CRITICAL
**: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
Mar 29 15:07:40 osmium systemd[1]: Started Session c11 of user lightdm.
Mar 29 15:07:40 osmium lightdm[13828]: ** (lightdm:13828): WARNING **: Error
activating login1 session: GDBus.Error:org.freedesktop.DBus.Error.NotSupported:
Operation not supported
Mar 29 15:07:40 osmium kernel: [14985.100699] lightdm-gtk-gre[13972]: segfault
at 0 ip 7f3f23bd09bf sp 7ffc64b32058 error 4 in
libc-2.23.so[7f3f23b3b000+1bf000]
Mar 29 15:07:41 osmium lightdm[13828]: /etc/modprobe.d is not a file
Mar 29 15:07:41 osmium lightdm[13828]: message repeated 4 times: [
/etc/modprobe.d is not a file]
Mar 29 15:07:41 osmium lightdm[13828]: update-alternatives: error: no
alternatives for x86_64-linux-gnu_gfxcore_conf
and core-like-thing ends up in /var/crash/...
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-70.91-generic 4.4.49
Uname: Linux 4.4.0-70-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: amd64
CurrentDesktop: XFCE
Date: Wed Mar 29 14:52:52 2017
InstallationDate: Installed on 2017-03-28 (1 days ago)
InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
ProcEnviron:
TERM=xterm
SHELL=/bin/bash
PATH=(custom, no user)
LANG=en_US.UTF-8
XDG_RUNTIME_DIR=
SourcePackage: xorg
Symptom: display
Title: Xorg crash
UpgradeStatus: No upgrade log present (probably fresh install)
** Affects: lightdm-gtk-greeter (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug crash xenial
** Package changed: xorg (Ubuntu) => lightdm-gtk-greeter (Ubuntu)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1677397
Title:
lightdm-gtk-greeter SIGSEGV when invoked by Xvnc -inetd -query
Status in lightdm-gtk-greeter package in Ubuntu:
New
Bug description:
To reproduce:
1. Install Xubuntu 16.04 LTS, update fully
2. Install packages xinetd, vnc4server
3. Append to /etc/services:
vnc 5900/tcp# VNC Virtual Network
Computing
4. Append to /etc/lightdm/lightdm.conf:
[XDMCPServer]
enabled=true
5. Create /etc/xinetd.d/vnc:
service vnc
{
disable = no
socket_type = stream
protocol= tcp
group = tty
wait= no
user= nobody
server = /usr/bin/Xvnc
server_args = -inetd -query localhost -once -securitytypes=none
-geometry 1024x768
}
# NOTE: might need to add an arg like ":1" to get out of way of local X server
# my case is special as I am trying to run headless, nobody is logged in on
console
6. Signal xinetd and lightdm to reconfigure:
$ sudo killall -1 xinetd
$ sudo service lightdm restart # or however your init system works
7. Don't know if significant (I am 400 miles away from test host and can't
test):
do NOT have anyone logged in on the test host console. In fact, to most
closely
reproduce my case, shut down the test host, power it off, disconnect all
monitors
and keyboards, then power it on and access from the net.
8. From another system, connect to the test host:
$ gvncviewer
[Desktop-packages] [Bug 157319] Re: Xlib: extension RANDR missing on display :0.0 while using -nvidia with Xinerama turned on
Note that Xinerama does not appear to be in the process of being deprecated. The wikipedia article was modified a year ago, describing the old words as full of lies: http://en.wikipedia.org/w/index.php?title=Xineramadiff=421530795oldid=415820495. Nothing on x.org seems to lead to deprecation. Instead, issues like conflicting with compositing have been fixed. I think the fundamental flaw here is in how XRANDR and Xinerama interact in the X server. Enabling Xinerama shouldn't disable the XRANDR extension protocol. It should instead allow all of the read-only operations (allowing `xrandr -q` to work); and return errors for attempts to actually *change* things which would conflict with Xinerama. All of which is, obviously, upstream work. Both Xinerama and XRANDR would need some work, plus -nvidia to stop forcibly disabling XRANDR when Xinerama is active. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtk+2.0 in Ubuntu. https://bugs.launchpad.net/bugs/157319 Title: Xlib: extension RANDR missing on display :0.0 while using -nvidia with Xinerama turned on Status in GTK+ GUI Toolkit: Fix Released Status in “gtk+2.0” package in Ubuntu: Confirmed Bug description: Binary package hint: xorg Interesting problem. Whenever I start up X, it loads RandR, so far as I can tell (The xorg log shows that it is indeed loaded), but If I ever try to do anything via xrandr, it tells me that the extension is missing on my display. m3r1k@reborn-desktop:~$ cat /var/log/Xorg.0.log |grep RandR (==) RandR enabled (==) RandR enabled m3r1k@reborn-desktop:~$ xrandr -q Xlib: extension RANDR missing on display :0.0. RandR extension missing I'm not sure what to do. To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/157319/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 157319] Re: Xlib: extension RANDR missing on display :0.0 while using -nvidia with Xinerama turned on
I'm using Xinerama to make one large T-shaped virtual display out of two 1920x1200 monitors, one landscape and one portrait. I've read stuff which implies it might be possible to do this with some melange of XRANDR + -nvidia TwinView + Virtual in the Screen section, Display subsection -- see http://thinkwiki.org/wiki/Xorg_RandR_1.2 -- but I didn't get anything but a frustrated headache from my attempts. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtk+2.0 in Ubuntu. https://bugs.launchpad.net/bugs/157319 Title: Xlib: extension RANDR missing on display :0.0 while using -nvidia with Xinerama turned on Status in GTK+ GUI Toolkit: Fix Released Status in “gtk+2.0” package in Ubuntu: Confirmed Bug description: Binary package hint: xorg Interesting problem. Whenever I start up X, it loads RandR, so far as I can tell (The xorg log shows that it is indeed loaded), but If I ever try to do anything via xrandr, it tells me that the extension is missing on my display. m3r1k@reborn-desktop:~$ cat /var/log/Xorg.0.log |grep RandR (==) RandR enabled (==) RandR enabled m3r1k@reborn-desktop:~$ xrandr -q Xlib: extension RANDR missing on display :0.0. RandR extension missing I'm not sure what to do. To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/157319/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 902780] [NEW] gnome-control-center Keyboard Layout and User Accounts modules crash under IceWM
Public bug reported: Ubuntu 11.10 patched to the minute with oneiric-proposed Specifically, gnome-control-center 1:3.2.2-0ubuntu1; icewm 1.3.7-1 Cause: IceWM does not set environment variable $XDG_CURRENT_DESKTOP; gnome-control-center relies on this variable to be set. Crash happens because it tries to dereference a null pointer returned by getenv(). The bug (actually two bugs) is introduced by the Ubuntu patches 10_keyboard_layout_on_unity.patch and 53_use_ubuntu_help.patch. TO REPRODUCE under any window manager: $ env -u XDG_CURRENT_DESKTOP gnome-control-center [ click on Keyboard Layout ] [ OR click on Keyboard, then Layout Settings ] [ OR click on User Accounts ] Patch attached. The patch makes gnome-control-center treat a missing $XDG_CURRENT_DESKTOP the same as an empty value. ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/902780 Title: gnome-control-center Keyboard Layout and User Accounts modules crash under IceWM Status in “gnome-control-center” package in Ubuntu: New Bug description: Ubuntu 11.10 patched to the minute with oneiric-proposed Specifically, gnome-control-center 1:3.2.2-0ubuntu1; icewm 1.3.7-1 Cause: IceWM does not set environment variable $XDG_CURRENT_DESKTOP; gnome-control-center relies on this variable to be set. Crash happens because it tries to dereference a null pointer returned by getenv(). The bug (actually two bugs) is introduced by the Ubuntu patches 10_keyboard_layout_on_unity.patch and 53_use_ubuntu_help.patch. TO REPRODUCE under any window manager: $ env -u XDG_CURRENT_DESKTOP gnome-control-center [ click on Keyboard Layout ] [ OR click on Keyboard, then Layout Settings ] [ OR click on User Accounts ] Patch attached. The patch makes gnome-control-center treat a missing $XDG_CURRENT_DESKTOP the same as an empty value. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/902780/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 902780] Re: gnome-control-center Keyboard Layout and User Accounts modules crash under IceWM
** Patch added: harden against unset XDG_CURRENT_DESKTOP https://bugs.launchpad.net/bugs/902780/+attachment/2627922/+files/missing-xdg_current_desktop.patch ** Bug watch added: GNOME Bug Tracker #665947 https://bugzilla.gnome.org/show_bug.cgi?id=665947 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/902780 Title: gnome-control-center Keyboard Layout and User Accounts modules crash under IceWM Status in “gnome-control-center” package in Ubuntu: New Bug description: Ubuntu 11.10 patched to the minute with oneiric-proposed Specifically, gnome-control-center 1:3.2.2-0ubuntu1; icewm 1.3.7-1 Cause: IceWM does not set environment variable $XDG_CURRENT_DESKTOP; gnome-control-center relies on this variable to be set. Crash happens because it tries to dereference a null pointer returned by getenv(). The bug (actually two bugs) is introduced by the Ubuntu patches 10_keyboard_layout_on_unity.patch and 53_use_ubuntu_help.patch. TO REPRODUCE under any window manager: $ env -u XDG_CURRENT_DESKTOP gnome-control-center [ click on Keyboard Layout ] [ OR click on Keyboard, then Layout Settings ] [ OR click on User Accounts ] Patch attached. The patch makes gnome-control-center treat a missing $XDG_CURRENT_DESKTOP the same as an empty value. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/902780/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 902780] Re: gnome-control-center Keyboard Layout and User Accounts modules crash under IceWM
(See also https://bugzilla.gnome.org/show_bug.cgi?id=665947 -- retracted when I realized the bug was in Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/902780 Title: gnome-control-center Keyboard Layout and User Accounts modules crash under IceWM Status in “gnome-control-center” package in Ubuntu: New Bug description: Ubuntu 11.10 patched to the minute with oneiric-proposed Specifically, gnome-control-center 1:3.2.2-0ubuntu1; icewm 1.3.7-1 Cause: IceWM does not set environment variable $XDG_CURRENT_DESKTOP; gnome-control-center relies on this variable to be set. Crash happens because it tries to dereference a null pointer returned by getenv(). The bug (actually two bugs) is introduced by the Ubuntu patches 10_keyboard_layout_on_unity.patch and 53_use_ubuntu_help.patch. TO REPRODUCE under any window manager: $ env -u XDG_CURRENT_DESKTOP gnome-control-center [ click on Keyboard Layout ] [ OR click on Keyboard, then Layout Settings ] [ OR click on User Accounts ] Patch attached. The patch makes gnome-control-center treat a missing $XDG_CURRENT_DESKTOP the same as an empty value. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/902780/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 848492] Re: I cannot install libreoffice
libreoffice 3.4.3 now installs cleanly, and successfully opens the 6 sample MS documents in /usr/share/checkbox/data/documents/. Björn , could you comment on what caused the ~24hr delay in uploading libreoffice-common? I ask in the spirit of research learning -- teach me to fish, show me the discovery trail to the web page where the build status was red or whatever. (- email) thanks! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/848492 Title: I cannot install libreoffice Status in LibreOffice Productivity Suite: Invalid Status in “libreoffice” package in Ubuntu: Fix Released Bug description: Steps to reproduce: 1) Start synaptic 2) Type libreoffice in the search box. 3) right-click on libreoffice and select the install option 4) click the Mark button on the Mark additional required changes dialog. 5) you receive the following error: The following packages have unresovable dependencies. libreoffice: Depends: libreoffice-core but it is not going to be installed Depends: libreoffice-writer but it is not going to be installed Depends: libreoffice-calc but it is not going to be installed Depends: libreoffice-impress but it is not going to be installed Depends: libreoffice-draw but it is not going to be installed Depends: libreoffice-math but it is not going to be installed Depends: libreoffice-base but it is not going to be installed Depends: libreoffice-report-builder-bin but it is not going to be installed Depends: libreoffice-filter-mobiledev but it is not going to be installed Depends: libreoffice-java-common but it is not going to be installed I had previously installed the ppa:libreoffice/ppa PPA using the commands: sudo add-apt-repository ppa:user/ppa-name sudo apt-get update They ran with no errors. I then tried to install libreoffice using apt-get: tim@Timbuntu:~$ sudo apt-get install libreoffice 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: libreoffice : Depends: libreoffice-core (= 1:3.4.3-1ubuntu1) but it is not going to be installed Depends: libreoffice-writer but it is not going to be installed Depends: libreoffice-calc but it is not going to be installed Depends: libreoffice-impress but it is not going to be installed Depends: libreoffice-draw but it is not going to be installed Depends: libreoffice-math but it is not going to be installed Depends: libreoffice-base but it is not going to be installed Depends: libreoffice-report-builder-bin but it is not going to be installed Depends: libreoffice-filter-mobiledev but it is not going to be installed Depends: libreoffice-java-common (= 1:3.4.3~) but it is not going to be installed E: Unable to correct problems, you have held broken packages. Synaptic tells me I have no broken packages. To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/848492/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 719861] Re: After installation icon theme default to gnome-icon-theme and cannot be changed
Warning generated by this fix: Setting up librsvg2-common (2.34.1-2) ... /var/lib/dpkg/info/librsvg2-common:amd64.postinst: 15: cannot create /usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0//gdk-pixbuf-query-loaders/loaders.cache: Directory nonexistent Patch is attached. ** Attachment added: Don't take the query-loaders binary as a version number! https://bugs.launchpad.net/ubuntu/+source/librsvg/+bug/719861/+attachment/2377806/+files/amd64.postinst.dif -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to librsvg in Ubuntu. https://bugs.launchpad.net/bugs/719861 Title: After installation icon theme default to gnome-icon-theme and cannot be changed Status in “librsvg” package in Ubuntu: Fix Released Status in “librsvg” source package in Natty: Fix Released Bug description: Binary package hint: gnome-icon-theme After a fresh installation of Natty, the icon theme displayed is gnome-icon-theme and can not be changed. In gnome-appearance-properties the theme selected is Ambiance and the icon theme is Ubuntu-mono-dark. If you select another icon theme, the theme displayed does not change (still gnome-icon-theme) gnome-setting-deamon is running The problem is the same with Unity and a Classic Desktop session. TEST CASE: 1. Install Natty ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: gnome-icon-theme 2.31.0-0ubuntu2 ProcVersionSignature: Ubuntu 2.6.38-3.30-generic 2.6.38-rc4 Uname: Linux 2.6.38-3-generic i686 Architecture: i386 Date: Wed Feb 16 09:23:50 2011 InstallationMedia: Ubuntu 11.04 Natty Narwhal - Alpha i386 (20110209) PackageArchitecture: all ProcEnviron: LANGUAGE=en_US:en LANG=en_US.UTF-8 LC_MESSAGES=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-icon-theme To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/librsvg/+bug/719861/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
