[Edubuntu-bugs] [Bug 1862208] [NEW] Remove moodle from Focal 20.04

2020-02-06 Thread Mike Salvatore
Public bug reported:

Moodle in 18.04 and later does not work at all. The bug discussed in [1]
manifests as a result of moodle 3.0.3 requiring php5.4.x, php5.5.x, or
php7.0.x. PHP7.2 and later are available in ubuntu 18.04 and later, but
these version of PHP are not compatible with moodle 3.0.3 [2].

The moodle package has been removed from the debian archive as of
2017-10-09. The only reverse dependency of moodle is jclicmoodle, which
is a moodle plugin that was also removed from the debian archive.

I am recommending that:

1) moodle and jclicmoodle be removed from the ubuntu archive for focal 20.04 
and later
2) we consider replacing moodle and jclicmoodle with a empty packages for 18.04 
and later.

[1] https://moodle.org/mod/forum/discuss.php?d=165833
[2] https://docs.moodle.org/dev/Moodle_3.0_release_notes#Server_requirements

** Affects: moodle (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Edubuntu
Bugsquad, which is subscribed to moodle in Ubuntu.
https://bugs.launchpad.net/bugs/1862208

Title:
  Remove moodle from Focal 20.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/moodle/+bug/1862208/+subscriptions

___
Mailing list: https://launchpad.net/~edubuntu-bugs
Post to : edubuntu-bugs@lists.launchpad.net
Unsubscribe : https://launchpad.net/~edubuntu-bugs
More help   : https://help.launchpad.net/ListHelp


[Edubuntu-bugs] [Bug 1862208] Re: Remove moodle from Focal 20.04

2020-02-06 Thread Tomasz (Tomek) Muras
I agree, it should be removed.

-- 
You received this bug notification because you are a member of Edubuntu
Bugsquad, which is subscribed to moodle in Ubuntu.
https://bugs.launchpad.net/bugs/1862208

Title:
  Remove moodle from Focal 20.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/moodle/+bug/1862208/+subscriptions

___
Mailing list: https://launchpad.net/~edubuntu-bugs
Post to : edubuntu-bugs@lists.launchpad.net
Unsubscribe : https://launchpad.net/~edubuntu-bugs
More help   : https://help.launchpad.net/ListHelp


[Edubuntu-bugs] [Bug 1853707] [NEW] Whole system stopped responding because of single program's fault - no way out, had to force power off

2020-02-06 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

What I did was:

- install LibreCAD (by adding their ppa and then using apt-get)
- open it
- try to open the attached .dwf file

LibreCAD hanged and the whole system stopped responding. The mouse
button stopped moving, the system wouldn't respond to keyboard strokes,
AND not even Ctrl+Alt+F1 worked to open a virtual terminal where I could
have tried killing some process.

Obviously there's a bug in LibreCAD, but no matter how badly a buggy (or
even evil) process behaves, if a single misbehaving program can cause
the whole OS to stall in a way that you cannot recover from, then by
definition there's a bug in the OS.

You must ALWAYS be able to kill the offending program and resume normal
operation without having to stop one single application other than the
offending one.

I have no idea whether the bug is actually in Xorg or somewhere else;
the reason I'm reporting it against xorg is that ctrl+alt+F1 wouldn't
work. I might very well be wrong but I believe xorg is responsible for
providing the virtual terminal via ctrl+alt+f1?

Either way, that MUST ALWAYS be available no matter how badly things go.

That a single program hanging causes me to have to force-power down the
computer is outrageous.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3.1
ProcVersionSignature: Ubuntu 4.4.0-169.198-generic 4.4.197
Uname: Linux 4.4.0-169-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia
.proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  340.107  Thu May 24 21:54:01 
PDT 2018
 GCC version:  gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.12)
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2.21
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CurrentDesktop: Unity
Date: Sat Nov 23 17:27:22 2019
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 
09) (prog-if 00 [VGA controller])
   Subsystem: Acer Incorporated [ALI] 3rd Gen Core processor Graphics 
Controller [1025:0647]
 NVIDIA Corporation GF117M [GeForce 610M/710M/810M/820M / GT 
620M/625M/630M/720M] [10de:1140] (rev a1) (prog-if 00 [VGA controller])
   Subsystem: Acer Incorporated [ALI] GeForce 710M [1025:0691]
InstallationDate: Installed on 2013-10-11 (2233 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
MachineType: Acer Aspire V3-571G
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-169-generic 
root=UUID=5830b30e-69e8-4bb4-8a2b-bc2b43c7414a ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/15/2012
dmi.bios.vendor: Acer
dmi.bios.version: V2.07
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: VA50_HC_CR
dmi.board.vendor: Acer
dmi.board.version: Type2 - Board Version
dmi.chassis.type: 10
dmi.chassis.vendor: Acer
dmi.chassis.version: V2.07
dmi.modalias: 
dmi:bvnAcer:bvrV2.07:bd10/15/2012:svnAcer:pnAspireV3-571G:pvrV2.07:rvnAcer:rnVA50_HC_CR:rvrType2-BoardVersion:cvnAcer:ct10:cvrV2.07:
dmi.product.name: Aspire V3-571G
dmi.product.version: V2.07
dmi.sys.vendor: Acer
version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.91-2~16.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.8
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2
xserver.bootTime: Sat Nov 23 17:25:58 2019
xserver.configfile: /etc/X11/xorg.conf
xserver.errors:
 NVIDIA(0): Failed to initiate mode change.
 NVIDIA(0): Failed to complete mode change
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.18.4-0ubuntu0.8

** Affects: librecad-dev
 Importance: Unknown
 Status: Unknown

** Affects: librecad (Ubuntu)
 Importance: Undecided
 Status: New

** Affects: unity (Ubuntu)
 Importance: Undecided
 Status: Incomplete


** Tags: amd64 apport-bug compiz-0.9 third-party-packages ubuntu xenial
-- 
Whole system stopped responding because 

[Edubuntu-bugs] [Bug 1853707] Re: Whole system stopped responding because of single program's fault - no way out, had to force power off

2020-02-06 Thread Daniel van Vugt
OK, we have two separate bugs here then:

* LibreCAD uses all the memory

* The desktop stops responding when memory is exhausted

These really should be two different bug IDs.

The latter is practically impossible to fix as it would require re-
engineering from the ground up to make it more robust. Plus that would
be re-engineering a desktop environment that we no longer support
(Compiz/Unity), in 16.04 which will reach end of standard support in
just over a year from now. So if you like you can open a separate bug
for that, but it's unlikely to ever be resolved.

I will make this bug about the first issue only. That can realistically
be resolved.

** Package changed: compiz (Ubuntu) => librecad (Ubuntu)

** Changed in: librecad (Ubuntu)
   Status: Incomplete => New

** No longer affects: unity (Ubuntu)

-- 
You received this bug notification because you are a member of Edubuntu
Bugsquad, which is subscribed to librecad in Ubuntu.
https://bugs.launchpad.net/bugs/1853707

Title:
  Whole system stopped responding because of single program's fault - no
  way out, had to force power off

To manage notifications about this bug go to:
https://bugs.launchpad.net/librecad-dev/+bug/1853707/+subscriptions

___
Mailing list: https://launchpad.net/~edubuntu-bugs
Post to : edubuntu-bugs@lists.launchpad.net
Unsubscribe : https://launchpad.net/~edubuntu-bugs
More help   : https://help.launchpad.net/ListHelp


[Edubuntu-bugs] [Bug 1853707] Re: Whole system stopped responding because of single program's fault - no way out, had to force power off

2020-02-06 Thread Armin Stebich
This ticket is a cross post. It is already posted in LibreCAD issues:
https://github.com/LibreCAD/LibreCAD/issues/1161.

This bug is indeed caused by LibreCAD or more exactly by libdxfrw, the DXF/DWG 
library it uses.
DWG support in libdxfrw is very rudimentary and therefor a warning message 
appear when opening a DWG file in LibreCAD. This warning states, that this 
could happen.

-- 
You received this bug notification because you are a member of Edubuntu
Bugsquad, which is subscribed to librecad in Ubuntu.
https://bugs.launchpad.net/bugs/1853707

Title:
  Whole system stopped responding because of single program's fault - no
  way out, had to force power off

To manage notifications about this bug go to:
https://bugs.launchpad.net/librecad-dev/+bug/1853707/+subscriptions

___
Mailing list: https://launchpad.net/~edubuntu-bugs
Post to : edubuntu-bugs@lists.launchpad.net
Unsubscribe : https://launchpad.net/~edubuntu-bugs
More help   : https://help.launchpad.net/ListHelp