[Bug 1831630] Re: After updating 18.04 login freezes on gnome-flashback

2019-06-04 Thread Art Edwards
I removed xorg.conf, and gnome-flashback started working perfectly on
the stand alone laptop. I think I need to go elsewhere for help with
xorg.conf. YOu can mark this resolved.

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

Title:
  After updating 18.04 login freezes on gnome-flashback

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-flashback/+bug/1831630/+subscriptions

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

[Bug 1831630] Re: After updating 18.04 login freezes on gnome-flashback

2019-06-04 Thread Art Edwards
So, following your lead, I looked at the xorg.conf. It is set up for my
external monitor. When I attached it to the monitor and rebooted,
everything was fine. This solves half the problem. I think I need a
stanza for the internal screen as well?

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

Title:
  After updating 18.04 login freezes on gnome-flashback

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-flashback/+bug/1831630/+subscriptions

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

[Bug 1831630] Re: After updating 18.04 login freezes on gnome-flashback

2019-06-04 Thread Art Edwards
xorg.conf is attached

** Attachment added: "Here it is."
   
https://bugs.launchpad.net/ubuntu/+source/gnome-flashback/+bug/1831630/+attachment/5268794/+files/xorg.conf

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

Title:
  After updating 18.04 login freezes on gnome-flashback

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-flashback/+bug/1831630/+subscriptions

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

[Bug 1831630] Re: After updating 18.04 login freezes on gnome-flashback

2019-06-04 Thread Art Edwards
Here is a snip of syslog, starting with reboot. Line 1295 is where I
believe the problem starts

** Attachment added: "end of syslog, starting with system reboot."
   
https://bugs.launchpad.net/ubuntu/+source/gnome-flashback/+bug/1831630/+attachment/5268791/+files/syslog_snip

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

Title:
  After updating 18.04 login freezes on gnome-flashback

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-flashback/+bug/1831630/+subscriptions

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

[Bug 1831630] [NEW] After updating 18.04 login freezes on gnome-flashback

2019-06-04 Thread Art Edwards
Public bug reported:

I have looked at #1802094, and this problem has different symptoms. The
display freezes. I can use cntrl-alt f4 to start a console, and I can
kill X. After that, the login sreen  reappears. I can only login to
Ubuntu on Wayland. I'll send a piece of syslog on next reboot.

** Affects: gnome-flashback (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/1831630

Title:
  After updating 18.04 login freezes on gnome-flashback

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-flashback/+bug/1831630/+subscriptions

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

[Bug 1699878] Re: nvidia-375 375.66-0ubuntu0.16.04.1: nvidia-375 kernel module failed to build [make[1]: *** No rule to make target 'Makefile'. Stop.]

2017-06-27 Thread Art Edwards
I know that there is another bug report on 4.4.0-81, and that there is a
candidate kernel 4.4.0-83 that fixes other problems (octave and scilab
not booting.) It would be prudent to see if nvidia-375
375.66-0ubuntu0.16.04.1 builds on the new candidate.

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

Title:
  nvidia-375 375.66-0ubuntu0.16.04.1: nvidia-375 kernel module failed to
  build [make[1]: *** No rule to make target 'Makefile'.  Stop.]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-375/+bug/1699878/+subscriptions

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


Re: [Bug 1460812] Re: Installation crashed during copying of files

2015-06-01 Thread Art Edwards
Thanks very much for the quick reply. That is what I suspected, but
filed the bug in case this was actually a problem. I am now creating a
USB thumb-drive start-up disk. I should point out that the instructions
on the page 

http://www.ubuntu.com/download/desktop/create-a-usb-stick-on-ubuntu

Are only for Unity. I am using the older gnome-like interface (I think
it's called gnome-flashback). It would be useful to include the one line
stating that gtk-usb-creator is the analog command for use in that
environment. 

Again, thanks for being so prompt. You saved me worry about my hard
drive being at fault.

Art Edwards


-- 
  Arthur H. Edwards
  edwards...@fastmail.fm

On Mon, Jun 1, 2015, at 02:53 PM, Phillip Susi wrote:
> Your installation medium is corrupt.  You will need to recreate it and
> should use the check disc option from the boot menu to verify it.
> 
> 
> ** Changed in: ubiquity (Ubuntu)
>Status: New => Invalid
> 
> -- 
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1460812
> 
> Title:
>   Installation crashed during copying of files
> 
> Status in ubiquity package in Ubuntu:
>   Invalid
> 
> Bug description:
>   Information should have been uploaded.
> 
>   ProblemType: Bug
>   DistroRelease: Ubuntu 14.04
>   Package: ubiquity 2.18.8
>   ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4
>   Uname: Linux 3.13.0-32-generic x86_64
>   ApportVersion: 2.14.1-0ubuntu3.2
>   Architecture: amd64
>   CasperVersion: 1.340
>   Date: Mon Jun  1 14:26:45 2015
>   InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi
>   file=/cdrom/preseed/ubuntu.seed boot=casper only-ubiquity quiet splash
>   --
>   LiveMediaBuild: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64
>   (20140722.2)
>   ProcEnviron:
>TERM=linux
>PATH=(custom, no user)
>XDG_RUNTIME_DIR=
>LANG=en_US.UTF-8
>   SourcePackage: ubiquity
>   UpgradeStatus: No upgrade log present (probably fresh install)
> 
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1460812/+subscriptions

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

Title:
  Installation crashed during copying of files

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

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


[Bug 1460812] [NEW] Installation crashed during copying of files

2015-06-01 Thread Art Edwards
Public bug reported:

Information should have been uploaded.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: ubiquity 2.18.8
ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4
Uname: Linux 3.13.0-32-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.2
Architecture: amd64
CasperVersion: 1.340
Date: Mon Jun  1 14:26:45 2015
InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi file=/cdrom/preseed/ubuntu.seed 
boot=casper only-ubiquity quiet splash --
LiveMediaBuild: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2)
ProcEnviron:
 TERM=linux
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
SourcePackage: ubiquity
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug trusty ubiquity-2.18.8 ubuntu

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

Title:
  Installation crashed during copying of files

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

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


[Bug 879377] Re: FirewallD is not running. Network printer detection needs services mdns, ipp, ipp-client and samba-client enabled on firewall

2014-08-11 Thread Art Edwards
I just started having the same problem. I am running 12.04 on two
machines, and they both have the same problem. Interestingly, this only
happened within the last few days. The printer had been discovered, and
working. It then acted as if it were disconnected. This appears to be a
fairly simple fix, and the problem is, what, two years old? Why hasn't
this problem been assigned?

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

Title:
  FirewallD is not running. Network printer detection needs services
  mdns, ipp, ipp-client and samba-client enabled on firewall

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

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


[Bug 848164] Re: Auto connect to 3G network only works after manually enabling mobile broadband after modem inserted/bootup/resume

2014-06-04 Thread Art Edwards
I am running 12.10 on Dell  inspiron 14-z, and I'm using the novatel
M760 over virgin mobile. I still have the problem that the system
doesn't see the device  if I remove, and re-insert it. I have tried the
solution suggested in #27, and, now, the modem does autoconnect.
However, it has not solved the re-insertion problem. I note the Bug
Watch updater that there is a new network-manager as of 2014-05-07. Will
this be back-ported to 12.10?

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

Title:
  Auto connect to 3G network only works after manually enabling mobile
  broadband after modem inserted/bootup/resume

To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager/+bug/848164/+subscriptions

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