[Bug 1814174] Re: Xorg crash report after resume

2019-02-03 Thread derek kelly
I don't see a "Closed" status.  The closest thing I see to make it go
away is "Invalid", but I would say that you can close it, unless the
thing to do is add Crash to the config by default so it isn't a manual
step.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1814174

Title:
  Xorg crash report after resume

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1814174/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1814174] Re: Xorg crash report after resume

2019-02-03 Thread derek kelly
Adding Crash to the config file seems to have done the trick.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1814174

Title:
  Xorg crash report after resume

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1814174/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1814174] Re: Xorg crash report after resume

2019-02-01 Thread derek kelly
>From that bug report I followed this step:

"It works to edit /etc/apport/crashdb.conf and add 'Crash' to the
'problem_types': ['Bug', 'Package', 'Crash'], or to make that change in
a separate file and run".

So I'll see how that fares.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1814174

Title:
  Xorg crash report after resume

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1814174/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1814174] Re: Xorg crash report after resume

2019-02-01 Thread derek kelly
Output of ls -l
total 2320
-rw-r- 1 root whoopsie 2373147 Feb  1 13:35 _usr_lib_xorg_Xorg.0.crash

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1814174

Title:
  Xorg crash report after resume

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1814174/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1814174] Re: Xorg crash report after resume

2019-02-01 Thread derek kelly
1. I'm not sure what you mean by the ID of the bug.
   The file is owned by root, group whoopsie

2. The contents of the file whoopsie-id are:
ad2a60d37ef07a75f5bb69241962893c2ee51bf68be6d93a3b37992aaf2d45370ac7a5094e472b57985c4979bd5355af775f1d483c51977972fa4f743003d70c

3. didn't do this part

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1814174

Title:
  Xorg crash report after resume

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1814174/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1814174] [NEW] Xorg crash report after resume

2019-01-31 Thread derek kelly
Public bug reported:

Crash Report when resuming from sleep.
Similar to https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1586223
This is a Sager NP8278 (Clevo P170SM-A) laptop with an Nvidia GeForce GTX 970M, 
driver 390.77
The crash log doesn't have much info in it IMO, but I uploaded here 
http://s000.tinyupload.com/?file_id=09497843963607449328

Output from sudo dmidecode -s bios-version && sudo dmidecode -s 
bios-release-date
4.6.5
11/14/2014

Output from uname -a
Linux dksager2linux 4.15.0-44-generic #47-Ubuntu SMP Mon Jan 14 11:26:59 UTC 
2019 x86_64 x86_64 x86_64 GNU/Linux

Output from cat /etc/*ase
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=18.04
DISTRIB_CODENAME=bionic
DISTRIB_DESCRIPTION="Ubuntu 18.04.1 LTS"
NAME="Ubuntu"
VERSION="18.04.1 LTS (Bionic Beaver)"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Ubuntu 18.04.1 LTS"
VERSION_ID="18.04"
HOME_URL="https://www.ubuntu.com/;
SUPPORT_URL="https://help.ubuntu.com/;
BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/;
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy;
VERSION_CODENAME=bionic
UBUNTU_CODENAME=bionic

Output from lspci
00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor 
DRAM Controller (rev 06)
00:01.0 PCI bridge: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor 
PCI Express x16 Controller (rev 06)
00:02.0 VGA compatible controller: Intel Corporation 4th Gen Core Processor 
Integrated Graphics Controller (rev 06)
00:03.0 Audio device: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor 
HD Audio Controller (rev 06)
00:14.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family 
USB xHCI (rev 05)
00:16.0 Communication controller: Intel Corporation 8 Series/C220 Series 
Chipset Family MEI Controller #1 (rev 04)
00:1a.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family 
USB EHCI #2 (rev 05)
00:1b.0 Audio device: Intel Corporation 8 Series/C220 Series Chipset High 
Definition Audio Controller (rev 05)
00:1c.0 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI 
Express Root Port #1 (rev d5)
00:1c.1 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI 
Express Root Port #2 (rev d5)
00:1c.2 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI 
Express Root Port #3 (rev d5)
00:1c.3 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI 
Express Root Port #4 (rev d5)
00:1d.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family 
USB EHCI #1 (rev 05)
00:1f.0 ISA bridge: Intel Corporation HM87 Express LPC Controller (rev 05)
00:1f.2 SATA controller: Intel Corporation 8 Series/C220 Series Chipset Family 
6-port SATA Controller 1 [AHCI mode] (rev 05)
00:1f.3 SMBus: Intel Corporation 8 Series/C220 Series Chipset Family SMBus 
Controller (rev 05)
01:00.0 VGA compatible controller: NVIDIA Corporation GM204M [GeForce GTX 970M] 
(rev a1)
03:00.0 PCI bridge: Texas Instruments XIO2213A/B/XIO2221 PCI Express to PCI 
Bridge [Cheetah Express] (rev 01)
04:00.0 FireWire (IEEE 1394): Texas Instruments XIO2213A/B/XIO2221 IEEE-1394b 
OHCI Controller [Cheetah Express] (rev 01)
05:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTL8411 PCI 
Express Card Reader (rev 01)
05:00.2 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 
PCI Express Gigabit Ethernet Controller (rev 0a)
06:00.0 Network controller: Intel Corporation Wireless 7260 (rev bb)

The nuisance inspired me to create a script on the desktop called 
ClearCrashLog.sh (info I got from a YouTube video)
ls /var/crash
sudo rm /var/crash/*

It's annoying to have to type the password every time, but since root owns the 
crash log it's necessary.
I've used Lubuntu for years.  My prior laptop was a Sager with an AMD card.  It 
had the same sort of issue versions ago.  I got in the habit of just clicking 
it away.  I think that the Report Crash fails because the log is owned by root 
and I don't have rights to it.  Perhaps adding myself to the whoopsie group 
would resolve that (and needing sudo to delete too), so I think I'll try that.
It's the only thing about Lubuntu that would be a turn off to new users. 

It's not a high priority thing, because the system works just fine.  But
it is a nuisance.

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

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1814174

Title:
  Xorg crash report after resume

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1099201] Re: Transcode can't rip DVD's (in K3b with file type MPEG4)

2014-07-27 Thread derek kelly
It still has this bug.

I worked around it by using k3b to Copy Disc to the hard drive as an iso.
Then mounted the iso and used HardBrake to rip the contents.

Log info, in case it helps:

System
---
K3b Version: 2.0.2
KDE Version: 4.13.2
QT Version:  4.8.6
Kernel:  3.13.0-30-generic

Used versions
---
transcode: 1.1.7

transcode
---
transcode v1.1.7 (C) 2001-2003 Thomas Oestreich, 2003-2010 Transcode Team
[dvd_reader.c] DVD title 1/8: 8 chapter(s), 1 angle(s), title set 2
[dvd_reader.c] title playback time: 00:44:01.11  2642 sec
[dvd_reader.c] DVD title 1/8: 8 chapter(s), 1 angle(s), title set 2
[dvd_reader.c] title playback time: 00:44:01.11  2642 sec
[transcode] V: auto-probing | /dev/sr0 (OK)
...
[decode_mpeg2.c] libmpeg2 acceleration: mmxext
[export_ffmpeg.so] Using FFMPEG codec 'mpeg4' (FourCC 'DIVX', MPEG4 compliant 
video).
[export_ffmpeg.so] No profile selected
[export_ffmpeg.so] Error opening configuration file ./ffmpeg.cfg: No such file 
or directory
[export_ffmpeg.so] Starting 1 thread(s)
[export_ffmpeg.so] Set display aspect ratio to input
libdvdread: Attempting to retrieve all CSS keys
...
encoding=1 frame=62186 first=0 last=-1 fps=78.197 done=-1.00 
timestamp=2593.674 timeleft=-1 decodebuf=0 filterbuf=9 encodebuf=11
encoding=1 frame=62713 first=0 last=-1 fps=78.354 done=-1.00 
timestamp=2615.655 timeleft=-1 decodebuf=0 filterbuf=9 encodebuf=11
[dvd_reader.c] warning: Can't read pid from lock file 
/tmp/LCK..dvd
encoding=1 frame=63240 first=0 last=-1 fps=78.567 done=-1.00 
timestamp=2637.635 timeleft=-1 decodebuf=0 filterbuf=9 encodebuf=11
*** Error in `/usr/bin/transcode': munmap_chunk(): invalid pointer: 
0x7f1d35162e7a ***

I was ripping multiple videos, so I noticed that the address changes
slightly each time.

...
*** Error in `/usr/bin/transcode': munmap_chunk(): invalid pointer: 
0x7fc249971e7a ***
...
*** Error in `/usr/bin/transcode': munmap_chunk(): invalid pointer: 
0x7f4871affe7a ***
...
*** Error in `/usr/bin/transcode': munmap_chunk(): invalid pointer: 
0x7fd9e72d2e7a ***
...
*** Error in `/usr/bin/transcode': munmap_chunk(): invalid pointer: 
0x7f2dd0340e7a ***
...
*** Error in `/usr/bin/transcode': munmap_chunk(): invalid pointer: 
0x7fd5f2472e7a ***
...
transcode command:
---
/usr/bin/transcode --nice 19 --log_no_color --progress_meter 2 --progress_rate 
527 -i /dev/sr0 -x dvd -T 1,-1,1 -a 0 -j 0,0,0,0 -R 
1,/tmp/kde-username/k3b_0.log -y ffmpeg,null -o /dev/null -F mpeg4 -w 1200 -Z 
640x480
/usr/bin/transcode --nice 19 --log_no_color --progress_meter 2 --progress_rate 
231 -i /dev/sr0 -x dvd -T 2,-1,1 -a 0 -j 0,0,0,0 -R 
1,/tmp/kde-username/k3b_0.log -y ffmpeg,null -o /dev/null -F mpeg4 -w 1200 -Z 
640x480
...

-- 
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to k3b in Ubuntu.
https://bugs.launchpad.net/bugs/1099201

Title:
  Transcode can't rip DVD's (in K3b with file type MPEG4)

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

-- 
kubuntu-bugs mailing list
kubuntu-b...@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs