[Bug 1338492] Re: Xorg crashed with SIGABRT in OsAbort()

2018-02-12 Thread The Computer Geek
Does ANYONE have an ETA on when this is going to be fixed? THIS IS
AFFECTING MY MAIN COMP!

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

Title:
  Xorg crashed with SIGABRT in OsAbort()

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

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

[Bug 1746149] [NEW] lightdm crashes when unlocking system- User attempting to unlock is logged out

2018-01-29 Thread The Computer Geek
Public bug reported:

Sometimes when I go to unlock my system, lightdm will crash and log me
out. This is infuriatingly annoying. This usually happens when my system
is either locked and then left alone for over 20 minutes, or when my
system locks due to inactivity.

Ubuntu version: 16.04.3 LTS
lightdm version: 1.18.3-0ubuntu1.1 500
What I expect to happen:
1) I lock the computer or it locks on it's own
2) It's left alone for over 20 minutes
3) I go to unlock
4) It unlocks and everything's open

What actually happens:
1) I lock the computer or it locks on it's own
2) It's left alone for over 20 minutes
3) I go to unlock
4) The screen goes black for 2 to 5 seconds, then comes back up a login prompt
5) I login
6) I get a desktop, and everything's been closed

This is the output of /var/log/lightdm/lightdm.log after the incident:

[+93016.79s] DEBUG: Continue authentication
[+93016.80s] DEBUG: Session pid=13591: Authentication complete with return 
value 0: Success
[+93016.80s] DEBUG: Authenticate result for user the-computer-geek: Success
[+93016.80s] DEBUG: User the-computer-geek authorized
[+93016.81s] DEBUG: Greeter sets language en_US
[+93016.86s] DEBUG: Greeter requests session xubuntu
[+93016.86s] DEBUG: Seat seat0: Returning to existing user session 
the-computer-geek
[+93016.86s] DEBUG: Unlocking login1 session c12
[+93016.86s] DEBUG: Activating VT 7
[+93016.96s] DEBUG: Seat seat0: Stopping greeter
[+93016.96s] DEBUG: Session pid=13506: Sending SIGTERM
[+93016.96s] DEBUG: Activating login1 session c12
[+93016.97s] DEBUG: Session pid=13591: Exited with return value 0
[+93016.97s] DEBUG: Seat seat0: Session stopped
[+93016.97s] DEBUG: Seat seat0 changes active session to c12
[+93016.97s] DEBUG: Session c12 is already active
[+93016.97s] DEBUG: Session pid=13506: Exited with return value 0
[+93016.97s] DEBUG: Seat seat0: Session stopped
[+93016.97s] DEBUG: Seat seat0: Stopping display server, no sessions require it
[+93016.97s] DEBUG: Sending signal 15 to process 13492
[+93017.03s] DEBUG: Process 13492 exited with return value 0
[+93017.03s] DEBUG: DisplayServer x-1: X server stopped
[+93017.03s] DEBUG: Releasing VT 8
[+93017.03s] DEBUG: DisplayServer x-1: Removing X server authority 
/var/run/lightdm/root/:1
[+93017.03s] DEBUG: Seat seat0: Display server stopped
[+93021.37s] DEBUG: Process 7864 terminated with signal 6
[+93021.37s] DEBUG: DisplayServer x-0: X server stopped
[+93021.37s] DEBUG: Releasing VT 7
[+93021.37s] DEBUG: DisplayServer x-0: Removing X server authority 
/var/run/lightdm/root/:0
[+93021.37s] DEBUG: Seat seat0: Display server stopped
[+93021.37s] DEBUG: Seat seat0: Stopping session
[+93021.37s] DEBUG: Session pid=8073: Sending SIGTERM
[+93021.37s] DEBUG: Seat seat0: Active display server stopped, starting greeter
[+93021.37s] DEBUG: Seat seat0: Creating greeter session
[+93021.37s] DEBUG: Seat seat0: Creating display server of type x
[+93021.37s] DEBUG: Using VT 7
[+93021.37s] DEBUG: Seat seat0: Starting local X display on VT 7
[+93021.37s] DEBUG: DisplayServer x-0: Logging to /var/log/lightdm/x-0.log
[+93021.37s] DEBUG: DisplayServer x-0: Writing X server authority to 
/var/run/lightdm/root/:0
[+93021.37s] DEBUG: DisplayServer x-0: Launching X Server
[+93021.37s] DEBUG: Launching process 17470: /usr/bin/X -core :0 -seat seat0 
-auth /var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch
[+93021.37s] DEBUG: DisplayServer x-0: Waiting for ready signal from X server :0
[+93021.96s] DEBUG: Session pid=8073: Exited with return value 0
[+93021.96s] DEBUG: Seat seat0: Session stopped
[+93021.96s] DEBUG: Seat seat0: Stopping display server, no sessions require it
[+93021.97s] DEBUG: Got signal 10 from process 17470
[+93021.97s] DEBUG: DisplayServer x-0: Got signal from X server :0
[+93021.97s] DEBUG: DisplayServer x-0: Connecting to XServer :0
[+93021.97s] DEBUG: Seat seat0: Display server ready, starting session 
authentication
[+93021.98s] DEBUG: Session pid=17605: Started with service 'lightdm-greeter', 
username 'lightdm'
[+93021.98s] DEBUG: Session pid=17605: Authentication complete with return 
value 0: Success
[+93021.98s] DEBUG: Seat seat0: Session authenticated, running command
[+93021.98s] DEBUG: Session pid=17605: Running command 
/usr/lib/lightdm/lightdm-greeter-session /usr/sbin/lightdm-gtk-greeter
[+93021.98s] DEBUG: Creating shared data directory /var/lib/lightdm-data/lightdm
[+93021.98s] DEBUG: Session pid=17605: Logging to 
/var/log/lightdm/seat0-greeter.log
[+93022.00s] DEBUG: Activating VT 7
[+93022.00s] DEBUG: Activating login1 session c16
[+93022.00s] DEBUG: Seat seat0 changes active session to c16
[+93022.00s] DEBUG: Session c16 is already active
[+93022.07s] DEBUG: Greeter connected version=1.18.3 resettable=false
[+93022.22s] DEBUG: Greeter start authentication for the-computer-geek
[+93022.22s] DEBUG: Session pid=17678: Started with service 'lightdm', username 
'the-computer-geek'
[+93022.22s] DEBUG: Session pid=17678: Got 1 message(s) from PAM
[+93022.22s] DEBUG

[Bug 350572] Re: xorg-driver-fglrx doesnt work with ATI Radeon x1200 card

2009-03-30 Thread Kubuntu COmputer Geek
lspci -vvnn:
m...@mike-desktop:~$ lspci -vvnn
00:00.0 Host bridge [0600]: ATI Technologies Inc RS690 Host Bridge [1002:7910]
Subsystem: ASUSTeK Computer Inc. Device [1043:826d]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap- 66MHz+ UDF- FastB2B- ParErr- DEVSEL=medium TAbort- 
TAbort- MAbort+ SERR- PERR- INTx-
Latency: 64
Kernel modules: ati-agp

00:01.0 PCI bridge [0604]: ATI Technologies Inc RS690 PCI to PCI Bridge 
(Internal gfx) [1002:7912]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz+ UDF- FastB2B- ParErr- DEVSEL=medium TAbort- 
TAbort- MAbort- SERR- PERR- INTx-
Latency: 99
Bus: primary=00, secondary=01, subordinate=01, sec-latency=68
I/O behind bridge: d000-dfff
Memory behind bridge: fdb0-fdcf
Prefetchable memory behind bridge: f000-f7ff
Secondary status: 66MHz+ FastB2B- ParErr- DEVSEL=medium TAbort- 
TAbort- MAbort+ SERR- PERR-
BridgeCtl: Parity- SERR- NoISA- VGA+ MAbort- Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities: access denied
Kernel modules: shpchp

00:07.0 PCI bridge [0604]: ATI Technologies Inc RS690 PCI to PCI Bridge (PCI 
Express Port 3) [1002:7917]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast TAbort- TAbort- 
MAbort- SERR- PERR- INTx-
Latency: 0, Cache Line Size: 32 bytes
Bus: primary=00, secondary=02, subordinate=02, sec-latency=0
I/O behind bridge: e000-efff
Memory behind bridge: fda0-fdaf
Prefetchable memory behind bridge: fdf0-fdff
Secondary status: 66MHz- FastB2B- ParErr- DEVSEL=fast TAbort- TAbort- 
MAbort- SERR- PERR-
BridgeCtl: Parity- SERR- NoISA- VGA- MAbort- Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities: access denied
Kernel driver in use: pcieport-driver
Kernel modules: shpchp

00:12.0 SATA controller [0106]: ATI Technologies Inc SB600 Non-Raid-5 SATA 
[1002:4380] (prog-if 01)
Subsystem: ASUSTeK Computer Inc. Device [1043:81ef]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz+ UDF- FastB2B- ParErr- DEVSEL=medium TAbort- 
TAbort- MAbort- SERR- PERR- INTx-
Latency: 64
Interrupt: pin A routed to IRQ 22
Region 0: I/O ports at ff00 [size=8]
Region 1: I/O ports at fe00 [size=4]
Region 2: I/O ports at fd00 [size=8]
Region 3: I/O ports at fc00 [size=4]
Region 4: I/O ports at fb00 [size=16]
Region 5: Memory at fe02f000 (32-bit, non-prefetchable) [size=1K]
Capabilities: access denied
Kernel driver in use: ahci

00:13.0 USB Controller [0c03]: ATI Technologies Inc SB600 USB (OHCI0) 
[1002:4387] (prog-if 10)
Subsystem: ASUSTeK Computer Inc. Device [1043:81ef]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap- 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium TAbort- 
TAbort- MAbort- SERR- PERR- INTx-
Latency: 64, Cache Line Size: 32 bytes
Interrupt: pin A routed to IRQ 16
Region 0: Memory at fe02e000 (32-bit, non-prefetchable) [size=4K]
Kernel driver in use: ohci_hcd

00:13.1 USB Controller [0c03]: ATI Technologies Inc SB600 USB (OHCI1) 
[1002:4388] (prog-if 10)
Subsystem: ASUSTeK Computer Inc. Device [1043:81ef]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap- 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium TAbort- 
TAbort- MAbort- SERR- PERR- INTx-
Latency: 64, Cache Line Size: 32 bytes
Interrupt: pin B routed to IRQ 17
Region 0: Memory at fe02d000 (32-bit, non-prefetchable) [size=4K]
Kernel driver in use: ohci_hcd

00:13.2 USB Controller [0c03]: ATI Technologies Inc SB600 USB (OHCI2) 
[1002:4389] (prog-if 10)
Subsystem: ASUSTeK Computer Inc. Device [1043:81ef]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap- 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium TAbort- 
TAbort- MAbort- SERR- PERR- INTx-
Latency: 64, Cache Line Size: 32 bytes
Interrupt: pin C routed to IRQ 18
Region 0: Memory at fe02c000 (32-bit, non-prefetchable) [size=4K]
Kernel driver in use: ohci_hcd

00:13.3 USB Controller [0c03]: ATI Technologies Inc SB600 USB (OHCI3) 
[1002:438a] (prog-if 10)
Subsystem: ASUSTeK Computer Inc. Device [1043:81ef]
  

[Bug 350572] [NEW] xorg-driver-fglrx doesnt work with ATI Radeon x1200 card

2009-03-28 Thread Kubuntu COmputer Geek
Public bug reported:

Binary package hint: xorg-driver-fglrx

When I use the xorg-driver-fglx driver when I boot up the screen just
freezes and I can't do anything. I am running Ubuntu 9.04 Beta 3/28/09.

** Affects: fglrx-installer (Ubuntu)
 Importance: Undecided
 Status: New

-- 
xorg-driver-fglrx doesnt work with ATI Radeon x1200 card
https://bugs.launchpad.net/bugs/350572
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

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


[Bug 346289] Re: Choppy Flash playback in full screen.

2009-03-24 Thread Kubuntu COmputer Geek
I also have the same issue I am running Ubuntu 9.04 ALpha 6 03/24/09 and
my full screen video is choppy.

-- 
Choppy Flash playback in full screen.
https://bugs.launchpad.net/bugs/346289
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

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


[Bug 345096] [NEW] No Sound In Flash

2009-03-18 Thread Kubuntu COmputer Geek
Public bug reported:

I am running Kubuntu 9.04 Alpha 6 AMD64 and I have no sound in the
flash-player. I do have sound in all of my other programs however.

** Affects: ubuntu
 Importance: Undecided
 Status: New

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

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


Re: [Bug 40485] Re: fat32 drive label shows up wierd

2007-01-11 Thread Computer Geek
Shows up proper in Dapper and Edgy so i would consider it closed.

On 1/11/07, Daniel Holbach [EMAIL PROTECTED] wrote:

 Your bug lacks information we would need to investigate further. We
 are now going to close the bug - please reopen if you have more
 information at hand.

 ** Changed in: Ubuntu
Status: Needs Info = Rejected

 --
 fat32 drive label shows up wierd
 https://launchpad.net/bugs/40485



-- 
KtecK Web Solutions
Website Design,  Maintenance and more...
http://kteck-webs.com

KTecK Blog - Syndicated
Computer and Tech news as we know it...
http://kteck-webs.com/blog

Kevin's Computer Zone
Computer history, gallerys and more...
http://www.kcomputerzone.ca

Call 4 Help
Self-Help For Your Computer...
http://call-4-help.ca

-- 
fat32 drive label shows up wierd
https://launchpad.net/bugs/40485

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


[Bug 40487] Re: Intel Create and Share Camera Pack (CS330) Does not work...

2006-10-22 Thread Computer Geek
Situation still hasn't changed... Same error occurs in a fully updated
6.06. Same error happens in 6.10.  I have since bought a HP Photosmart
M425 that works like a charm  in Ubuntu... But the intel camera is my
webcam which i would like to have working in Ubuntu.

-- 
Intel Create and Share Camera Pack (CS330) Does not work...
https://launchpad.net/bugs/40487

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


[Bug 22007] Re: no 'Settings' button in gnome-screensaver

2006-08-11 Thread Computer Geek
At least allow gnome-screensaver to be removed seperate of ubuntu-
desktop... then i could install xscreensaver and use that instead.

-- 
no 'Settings' button in gnome-screensaver
https://launchpad.net/bugs/22007

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


[Bug 49965] dosfsck breaks usplash

2006-06-16 Thread Computer Geek
Public bug reported:

Binary package hint: usplash

When booting my Ubuntu 6.06 machine breaks out of usplash to check my
vfat drives using dosfsck. As soon as it begins checking my vfat drive\
it quits out of usplash to the standard text boot. While this is not a
mission critical bug... its still annoying.

** Affects: usplash (Ubuntu)
 Importance: Untriaged
 Status: Unconfirmed

** Description changed:

  Binary package hint: usplash
  
  When booting my Ubuntu 6.06 machine breaks out of usplash to check my
- vfat drives using dosfsck. While this is not a mission critical bug...
- its still annoying.
+ vfat drives using dosfsck. As soon as it begins checking my vfat drive\
+ it quits out of usplash to the standard text boot. While this is not a
+ mission critical bug... its still annoying.

-- 
dosfsck breaks usplash
https://launchpad.net/bugs/49965

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