date:20161002

[Touch-packages] [Bug 1627502] Re: Black screen, cursor shown, wifi connection popup shown

2016-10-02 Thread Timo Jyrinki

Not other than standard kernel updates in yakkety. It's Intel Braswell
hardware.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1627502

Title:
  Black screen, cursor shown, wifi connection popup shown

Status in lightdm package in Ubuntu:
  Incomplete

Bug description:
  My yakkety installation is now for some reason in shape that lightdm
  only starts with a black screen, although mouse cursor is shown and
  movable and "wifi networks available" popup is shown at the top right
  corner.

  After some while this disappears and the system goes to some sort of
  tty switching loop where sometimes text cursor is shown and sometimes
  just blank screen. If I want to recover text console control of
  machine I need to quickly after booting switch to tty1 and stop
  lightdm.

  This started happening last week after some upgrades and a reboot.

  I've tried reinstalling and everything I can think of, but I can't fix
  it. Meanwhile using sddm I can't log in to Unity 7 or 8, and gdm
  doesn't start at all. So I'm using sddm + Plasma now but would like to
  be also be able to run Unity 7 and Unity 8.

  I couldn't also use ubuntu-bug since I can't use the browser interface
  from command line (otherwise it works fine until that point) and it
  segfaults under Plasma environment while collecting information.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1554878] Re: fix up usage of XDG_CURRENT_DESKTOP

2016-10-02 Thread Launchpad Bug Tracker

** Branch linked: lp:~robert-ancell/unity-control-center/xdg-current-
desktop

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to indicator-bluetooth in
Ubuntu.
https://bugs.launchpad.net/bugs/1554878

Title:
  fix up usage of XDG_CURRENT_DESKTOP

Status in GLib:
  Confirmed
Status in Python XDG App:
  Confirmed
Status in empathy package in Ubuntu:
  Fix Released
Status in eog package in Ubuntu:
  Fix Released
Status in gnome-control-center package in Ubuntu:
  Fix Released
Status in indicator-bluetooth package in Ubuntu:
  Fix Committed
Status in nautilus package in Ubuntu:
  Fix Released
Status in totem package in Ubuntu:
  Fix Released
Status in unity-control-center package in Ubuntu:
  Fix Committed
Status in unity-settings-daemon package in Ubuntu:
  Fix Committed
Status in yelp package in Ubuntu:
  Fix Released

Bug description:
  Since being standardised XDG_CURRENT_DESKTOP supports specifying
  multiple Desktop Names seperated by a colon, however many of the
  patches in Ubuntu pre-date this change so don't correctly support the
  current format in some cases.

  These days XDG_CURRENT_DESKTOP will look something like
  Unity
  GNOME (gnome-shell)
  GNOME-Classic:GNOME (gnome-shell classic mode)
  GNOME-Flashback:Unity (Flashback sesison, although upstream and debian use 
GNOME-Flashack:GNOME for this)

  Many of the patches only check for == "Unity" or == "GNOME", so
  misbehave for the latter cases in the list above.

  I suspect this will be more widespread than just nautilus, but fixing
  that would be a good start. Since most of this code is still Ubuntu
  specific (upstream mainly use XDG_CURRENT_DESKTOP for onlyShowIn etc),
  probably taking the last value in the string would get the desired
  result of Unity vs GNOME3 behaviour

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: nautilus 1:3.18.4.is.3.14.3-0ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-8.23-generic 4.4.2
  Uname: Linux 4.4.0-8-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Wed Mar  9 15:04:36 2016
  SourcePackage: nautilus
  UpgradeStatus: Upgraded to xenial on 2015-11-28 (102 days ago)

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1554878] Re: fix up usage of XDG_CURRENT_DESKTOP

2016-10-02 Thread Robert Ancell

This is affecting Ubuntu 16.10 now as XDG_CURRENT_DESKTOP is now set to
"Unity:Unity7" (e.g. bug 1629668)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to indicator-bluetooth in
Ubuntu.
https://bugs.launchpad.net/bugs/1554878

Title:
  fix up usage of XDG_CURRENT_DESKTOP

Status in GLib:
  Confirmed
Status in Python XDG App:
  Confirmed
Status in empathy package in Ubuntu:
  Fix Released
Status in eog package in Ubuntu:
  Fix Released
Status in gnome-control-center package in Ubuntu:
  Fix Released
Status in indicator-bluetooth package in Ubuntu:
  Fix Committed
Status in nautilus package in Ubuntu:
  Fix Released
Status in totem package in Ubuntu:
  Fix Released
Status in unity-control-center package in Ubuntu:
  Fix Committed
Status in unity-settings-daemon package in Ubuntu:
  Fix Committed
Status in yelp package in Ubuntu:
  Fix Released

Bug description:
  Since being standardised XDG_CURRENT_DESKTOP supports specifying
  multiple Desktop Names seperated by a colon, however many of the
  patches in Ubuntu pre-date this change so don't correctly support the
  current format in some cases.

  These days XDG_CURRENT_DESKTOP will look something like
  Unity
  GNOME (gnome-shell)
  GNOME-Classic:GNOME (gnome-shell classic mode)
  GNOME-Flashback:Unity (Flashback sesison, although upstream and debian use 
GNOME-Flashack:GNOME for this)

  Many of the patches only check for == "Unity" or == "GNOME", so
  misbehave for the latter cases in the list above.

  I suspect this will be more widespread than just nautilus, but fixing
  that would be a good start. Since most of this code is still Ubuntu
  specific (upstream mainly use XDG_CURRENT_DESKTOP for onlyShowIn etc),
  probably taking the last value in the string would get the desired
  result of Unity vs GNOME3 behaviour

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: nautilus 1:3.18.4.is.3.14.3-0ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-8.23-generic 4.4.2
  Uname: Linux 4.4.0-8-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Wed Mar  9 15:04:36 2016
  SourcePackage: nautilus
  UpgradeStatus: Upgraded to xenial on 2015-11-28 (102 days ago)

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1168742] Re: [udev] Disks are not unmounted when physical eject button is used

2016-10-02 Thread Phil Wright

@ Peter Bennet (comment #30)
Sorry, I don't use Video CD's so I can't check what the problem is - presumably 
'dvd-rw-mediainfo' doesn't recognise Video CD's and produces an error of some 
kind. You could try running 'dvd-rw-mediainfo /dev/sr0; echo "status = $?"' 
while a Video CD is in the drive to see what exit status dvd-rw-mediainfo 
returns, and modify the 'sr0_change.sh' script condition to ignore that exit 
status value, assuming that exit status is unique for Video CDs (if it's a 
general exit status, then ignore this suggestion):
'if [ "$n" -ne '0' ] && [ "$n" -ne '' ] ;then eject 
/dev/sr0;fi

@ Robert M. Muncrief (comment #31)
I agree, this is the sort of functionality that should work out of the box 
without fail. At the moment it sends the same old Linux subtext of 'geeks only 
need apply'. I've set up lots of Linux systems for complete newbies, and 
they've used them quite happily, but if I hadn't been there to work around some 
of these issues they would never have got started.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1168742

Title:
  [udev] Disks are not unmounted when physical eject button is used

Status in systemd:
  Confirmed
Status in systemd package in Ubuntu:
  Fix Released

Bug description:
  In 13.04, disks (DVDs, CDS) are not unmounted when ejected via the
  hardware button on the drive. After ejecting disks via the hardware
  button, an entry for the disk still shows up in the file manager, and
  shows when I run df. If I do a soft eject (ie from the right click
  menu from the icon on the launcher), however, everything works
  properly.

  Just as a note, as per
  https://wiki.ubuntu.com/Bugs/FindRightPackage#Hardware_Malfunctions, I
  attempted to report this using ubuntu-bug storage, however there is
  not an option dealing with unmounting devices, and clicking other
  tells you that you should run ubuntu-bug again with a specific package
  name. In an attempt to get this to a semi-relevant audience, I ended
  up just saying that a disk wasn't auto-mounted, clicking through the
  next few popups, and ended up here. If this isn't the right place to
  report this bug, I apologize.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: linux-image-3.8.0-17-generic 3.8.0-17.27
  ProcVersionSignature: Ubuntu 3.8.0-17.27-generic 3.8.6
  Uname: Linux 3.8.0-17-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.9.2-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  chris  1590 F pulseaudio
   /dev/snd/controlC0:  chris  1590 F pulseaudio
  Date: Sat Apr 13 12:54:33 2013
  GvfsMonitorLog: Monitoring events. Press Ctrl+C to quit.
  HibernationDevice: RESUME=UUID=bd2c881c-7bf8-4996-8b05-7efbd9852333
  HotplugNewDevices:

  HotplugNewMounts:

  InstallationDate: Installed on 2013-03-26 (18 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130325)
  MachineType: ASUSTeK COMPUTER INC. G55VW
  MarkForUpload: True
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB:

  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-17-generic 
root=UUID=f44b6481-8a06-4cf1-a494-0e4c233720c8 ro quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-3.8.0-17-generic N/A
   linux-backports-modules-3.8.0-17-generic  N/A
   linux-firmware1.105
  SourcePackage: linux
  Symptom: storage
  UdevMonitorLog:
   monitor will print the received events for:
   UDEV - the event which udev sends out after rule processing
  UdisksMonitorLog:
   Monitoring the udisks daemon. Press Ctrl+C to exit.
   12:54:42.343: The udisks-daemon is running (name-owner :1.39).
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/05/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: G55VW.206
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: G55VW
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrG55VW.206:bd04/05/2012:svnASUSTeKCOMPUTERINC.:pnG55VW:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG55VW:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: G55VW
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1614393] Re: NetworkManager does not always start at boot/first login

2016-10-02 Thread Andrew

*** This bug is a duplicate of bug 1594715 ***
https://bugs.launchpad.net/bugs/1594715

Still affected by this bug. No whoopsie but I have attached relevant
snippet of kern.log

More info:
$ uname -ra
Linux TOSgeek 4.4.0-38-generic #57-Ubuntu SMP Tue Sep 6 15:42:33 UTC 2016 
x86_64 x86_64 x86_64 GNU/Linux


** Attachment added: "kern.log.networkmanager"
   
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1614393/+attachment/4753160/+files/kern.log.networkmanager

** This bug has been marked a duplicate of bug 1594715
   wifi does not work roughly half of the times

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1614393

Title:
  NetworkManager does not always start at boot/first login

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Syslog says:
  Aug 18 17:03:41  whoopsie[1010]: [17:03:41] Could not get the Network 
Manager state:
  Aug 18 17:03:41  whoopsie[1010]: [17:03:41] 
GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name 
org.freedesktop.NetworkManager was not provided by any .service files

  Sometimes rebooting fixes it. Otherwise, need to run sudo systemctl
  start network-manager manually.

  This is a blocker for Internet access (using wlan0)

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1629728] [NEW] Package renamed causes conflicts

2016-10-02 Thread Marcos Alano

Public bug reported:

I'm trying to install a program called Nixnote2. In his latest version
it depends of package libopencv-highgui2.4 (available on Trusty) or
libopencv-highgui2.4v5 (available on Xenial). The problem is on Yakkety
this packages was replaced by package libopencv-highgui2.4-deb0. That's
fine (even just seems the package was renamed). But I think the package
libopencv-highgui2.4v5 needs to become virtual on Yakkety and libopencv-
highgui2.4-deb0 should provides it.

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to opencv in Ubuntu.
https://bugs.launchpad.net/bugs/1629728

Title:
  Package renamed causes conflicts

Status in opencv package in Ubuntu:
  New

Bug description:
  I'm trying to install a program called Nixnote2. In his latest version
  it depends of package libopencv-highgui2.4 (available on Trusty) or
  libopencv-highgui2.4v5 (available on Xenial). The problem is on
  Yakkety this packages was replaced by package libopencv-
  highgui2.4-deb0. That's fine (even just seems the package was
  renamed). But I think the package libopencv-highgui2.4v5 needs to
  become virtual on Yakkety and libopencv-highgui2.4-deb0 should
  provides it.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1627502] Re: Black screen, cursor shown, wifi connection popup shown

2016-10-02 Thread Robert Ancell

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1627502

Title:
  Black screen, cursor shown, wifi connection popup shown

Status in lightdm package in Ubuntu:
  Incomplete

Bug description:
  My yakkety installation is now for some reason in shape that lightdm
  only starts with a black screen, although mouse cursor is shown and
  movable and "wifi networks available" popup is shown at the top right
  corner.

  After some while this disappears and the system goes to some sort of
  tty switching loop where sometimes text cursor is shown and sometimes
  just blank screen. If I want to recover text console control of
  machine I need to quickly after booting switch to tty1 and stop
  lightdm.

  This started happening last week after some upgrades and a reboot.

  I've tried reinstalling and everything I can think of, but I can't fix
  it. Meanwhile using sddm I can't log in to Unity 7 or 8, and gdm
  doesn't start at all. So I'm using sddm + Plasma now but would like to
  be also be able to run Unity 7 and Unity 8.

  I couldn't also use ubuntu-bug since I can't use the browser interface
  from command line (otherwise it works fine until that point) and it
  segfaults under Plasma environment while collecting information.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1628790] Re: Changing the user settings to autologin on Lubuntu 16.04 causes LightDM to get stuck in a login loop

2016-10-02 Thread Robert Ancell

What version of Lubuntu / LightDM is this? Can you check the permissions
on .Xauthority with ls -l after this occurs?

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1628790

Title:
  Changing the user settings to autologin on Lubuntu 16.04 causes
  LightDM to get stuck in a login loop

Status in lightdm package in Ubuntu:
  Incomplete

Bug description:
  After setting my account to login automatically through the user and
  groups setting in Lubuntu. After the computer reboots it gets stuck in
  a loop on the login screen. Logging in will just send you back to the
  same screen.

  The only way I could fix the issue was to press CRTL + ALT + F1, logging in 
through the CLI and typing:
  "sudo mv .Xauthority .Xauthority.bak"
  and then once I was back to the login screen I was able to login and turn the 
setting off. 

  I did check to see weather that was what caused it, by restarting the
  computer without turning off the auto-login. However the same issue
  happened and only turning off auto-login would stop the login loop.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1628922] Re: Postpone login attempts if X have failed

2016-10-02 Thread Robert Ancell

The correct place to configure this is in PAM, where is can apply to any
method of logging in.

For example, see:
http://unix.stackexchange.com/questions/78182/how-to-lock-users-after-5-unsuccessful-login-tries

** Changed in: lightdm (Ubuntu)
Status: New => Won't Fix

--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1628922

Title:
Postpone login attempts if X have failed

Status in lightdm package in Ubuntu:
Won't Fix

Bug description:
** This is a feature request that regards to security. **

Please add to the login method a mechanism that postpones successive
login attempts if X attempts failed.

Obviously this can be further enhanced - for example:
If X successive login attempts failed, then disable that specific login
method for that specific user for Y minutes.
If Y minutes have passed and the additional successive attempts failed again
- then disable that specific login method for that specific user for 2*Y
minutes.
And so on...

Values of X and Y should be configured by the 'root' user.

Benefits: greatly reduces the risk of brute-forcing the password.
Scenarios that this can defend from:
* If someone hacked a user in the system, then this prevents him to brute
force the password for root.
* A keyboard can be emulated via a physical connection while it tries to
brute force the password.

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

--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp

89 matches

Mail list logo