[Touch-packages] [Bug 658960] Re: add "sudo" before apt-get autoremove in warning

[A. Eibach]

>Use 'apt-get autoremove' to remove them.

>while it should give the warning as
>Use 'sudo apt-get autoremove' to remove them

It NOT that simple.
There should be made a case decision:

- Are we really sudo'ing?
- Are we working directly under root, i. e. the shell with the hash prompt?

In the latter case, a 'sudo' would be total nonsense.

In a nutshell, we have to check for internal user ID (zero, non-zero).

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

Title:
  add "sudo" before apt-get autoremove in warning

Status in apt package in Ubuntu:
  Confirmed

Bug description:
  Binary package hint: apt

  The following packages were automatically installed and are no longer 
required:
  ABCD
  Use 'apt-get autoremove' to remove them.

  while it should give the warning as 
  Use 'sudo apt-get autoremove' to remove them

  SUDO should be added.

  ProblemType: Bug
  DistroRelease: Ubuntu 10.10
  Package: synaptic 0.63.1ubuntu14
  ProcVersionSignature: Ubuntu 2.6.35-22.34-generic 2.6.35.4
  Uname: Linux 2.6.35-22-generic x86_64
  NonfreeKernelModules: wl fglrx
  Architecture: amd64
  Date: Tue Oct 12 01:22:51 2010
  ExecutablePath: /usr/sbin/synaptic
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Alpha amd64 (20100803.1)
  ProcEnviron:
   PATH=(custom, no user)
   LANG=en_US.utf8
   SHELL=/bin/bash
  SourcePackage: synaptic

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/658960/+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 1537895] Re: Please include poppler-glib-demo tool in standard package

[A. Eibach]

>It's not useful on a normal system since it's for debugging
Depends on point of view. :) 
*As long as* everything is still working fine, there is no need for that tool. 
But once evince goes all wonky with a certain PDF, it's the best tool to use 
and NOT (as most users do) put the entire blame on evince itself. But evince is 
merely the "executive power", while highly dependent on the API it accesses 
under the hood.

>Do you know if what binary fedora includes the binary? 
Sure, but you will get the information only because you've explicitly asked for 
it. :) So here goes...

Originally, it was in poppler-utils, cf.
https://bugzilla.redhat.com/show_bug.cgi?id=872338

Later, Marek moved it to its own subpackage 'poppler-demos'.
Version 0.40 is now in the wild out there:
http://arm.koji.fedoraproject.org/koji/rpminfo?rpmID=1912994


** Bug watch added: Red Hat Bugzilla #872338
   https://bugzilla.redhat.com/show_bug.cgi?id=872338

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

Title:
  Please include poppler-glib-demo tool in standard package

Status in poppler package in Ubuntu:
  Confirmed

Bug description:
  I'm having an occasional issue with evince, and since the issue is
  clearly related to the PDF engine underneath which it uses (*this), I
  got a tip to run a PDF directly with 'poppler-glib-demo' in the
  'poppler-demos' package.

  However, this tip was NOT suitable for Ubuntu, as there is nothing like a 
'poppler-demos' package, but the whole package structure is different.
  So this is one more for the wishlist.
  poppler-glib-demo is not just a demo for developers, but will also show 
errors that evince may be blamed for (for no reason at all). evince simply uses 
lots of things under the hood, and one of them is poppler for PDF rendering.

  ISTR that our Fedora colleagues do have this tool compiled in binary form and 
included in the package.
  As I think it might be pretty useful for bug-hunting, I'd ask you kindly to 
no longer do without it when building the Ubuntu poppler package.
  Thanks for considering.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/poppler/+bug/1537895/+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 1537915] Re: libgtk-3-common: Adwaita theme dependency not recognized

[A. Eibach]

No problem, can do.

user@mybuntubox~$:~$ sudo apt-get --no-install-recommends install 
libgtk-3-common=3.18.6-1ubuntu1
[sudo] password for user: 
Reading package lists... Done
Building dependency tree   
Reading state information... Done
Some packages could not be installed. 

The following information may help to resolve the situation:

The following packages have unmet dependencies.
 libgtk-3-common : Depends: adwaita-icon-theme (>= 3.18) but it is not going to 
be installed
E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by 
held packages.

Same thing, no?

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

Title:
  libgtk-3-common: Adwaita theme dependency not recognized

Status in gtk+3.0 package in Ubuntu:
  New

Bug description:
  Pre-note: due to severe bugs, I had to go down from 3.19.x back to 3.18.6.
  I think the following content will speak for itself:

  user@mybuntubox:~$ sudo apt-get install --reinstall adwaita-icon-theme
  Reading package lists... Done
  Building dependency tree
  Reading state information... Done
  0 to upgrade, 0 to newly install, 1 reinstalled, 0 to remove and 70 not to 
upgrade.
  Need to get 0 B/897 kB of archives.
  After this operation, 0 B of additional disk space will be used.
  (Reading database ... 307199 files and directories currently installed.)
  Preparing to unpack .../adwaita-icon-theme_3.18.0-2ubuntu1_all.deb ...
  Unpacking adwaita-icon-theme (3.18.0-2ubuntu1) over (3.18.0-2ubuntu1) ...
  Setting up adwaita-icon-theme (3.18.0-2ubuntu1) ...

  +++ OKAY. Adwaita Icon Theme is now installed and expected to be
  working. Version = __3.18.0-2__

  user@mybuntubox~$ sudo apt-get install libgtk-3-common=3.18.6-1ubuntu1
  Reading package lists... Done
  Building dependency tree
  Reading state information... Done
  Some packages could not be installed. This may mean that you have
  requested an impossible situation or if you are using the unstable
  distribution that some required packages have not yet been created
  or been moved out of Incoming.
  The following information may help to resolve the situation:

  The following packages have unmet dependencies.
   libgtk-3-common : Depends: adwaita-icon-theme (>= 3.18) but it is not going 
to be installed
     Recommends: libgtk-3-0 but it is not going to be installed
  E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by 
held packages.

  There is clearly something wrong.
  Just for "emphasis", I reinstalled Adwaita icon theme 3.18.x again above, to 
be sure it is really expected to be there.

  But it seems to be a bug that libgtk-3-common does not recognize it as there.
  Plus, --force-depends appears to be unavailable when using the '=' sign for a 
version-specific downgrade.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1537915/+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 1537915] Re: libgtk-3-common: Adwaita theme dependency not recognized

[A. Eibach]

Heheh, Manfred, I like that. You're trying to prove in the end that it's
a PEBKAC case after all. But still we can agree it is none...that is,
STILL. :-)

andy@andy-lubuntubox:~$ apt-get --simulate --no-install-recommends install 
libgtk-3-common=3.18.6-1ubuntu1 adwaita-icon-theme
NOTE: This is only a simulation!
  apt-get needs root privileges for real execution.
  Keep also in mind that locking is deactivated,
  so don't depend on the relevance to the real current situation!
Reading package lists... Done
Building dependency tree   
Reading state information... Done
adwaita-icon-theme is already the newest version (3.18.0-2ubuntu1).
Some packages could not be installed. 

The following information may help to resolve the situation:

The following packages have unmet dependencies.
 adwaita-icon-theme : Depends: libgtk-3-bin but it is not going to be installed
E: Unable to correct problems, you have held broken packages.

HEH!
Now it wants libgtk-3-bin first...

Dude, YOU DO KNOW YOUR STUFF!
I take my hat off.

$ sudo apt-get install libgtk-3-bin=3.18.6-1ubuntu1

THAT fixed it.

Still, I think behavior is wrong, because it clearly told about 
> libgtk-3-common : Depends: adwaita-icon-theme (>= 3.18) but it is not going 
> to be installed

And adwaita...3.18 was working and installed.
It didn't mention _anything_ about libgtk-3-bin, until you did that sneaky 
simulation line.

Anyways, it was worth posting here, because I might need that "trick"
somewhere else in the future! :)

Thanks again.

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

Title:
  libgtk-3-common: Adwaita theme dependency not recognized

Status in gtk+3.0 package in Ubuntu:
  New

Bug description:
  Pre-note: due to severe bugs, I had to go down from 3.19.x back to 3.18.6.
  I think the following content will speak for itself:

  user@mybuntubox:~$ sudo apt-get install --reinstall adwaita-icon-theme
  Reading package lists... Done
  Building dependency tree
  Reading state information... Done
  0 to upgrade, 0 to newly install, 1 reinstalled, 0 to remove and 70 not to 
upgrade.
  Need to get 0 B/897 kB of archives.
  After this operation, 0 B of additional disk space will be used.
  (Reading database ... 307199 files and directories currently installed.)
  Preparing to unpack .../adwaita-icon-theme_3.18.0-2ubuntu1_all.deb ...
  Unpacking adwaita-icon-theme (3.18.0-2ubuntu1) over (3.18.0-2ubuntu1) ...
  Setting up adwaita-icon-theme (3.18.0-2ubuntu1) ...

  +++ OKAY. Adwaita Icon Theme is now installed and expected to be
  working. Version = __3.18.0-2__

  user@mybuntubox~$ sudo apt-get install libgtk-3-common=3.18.6-1ubuntu1
  Reading package lists... Done
  Building dependency tree
  Reading state information... Done
  Some packages could not be installed. This may mean that you have
  requested an impossible situation or if you are using the unstable
  distribution that some required packages have not yet been created
  or been moved out of Incoming.
  The following information may help to resolve the situation:

  The following packages have unmet dependencies.
   libgtk-3-common : Depends: adwaita-icon-theme (>= 3.18) but it is not going 
to be installed
     Recommends: libgtk-3-0 but it is not going to be installed
  E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by 
held packages.

  There is clearly something wrong.
  Just for "emphasis", I reinstalled Adwaita icon theme 3.18.x again above, to 
be sure it is really expected to be there.

  But it seems to be a bug that libgtk-3-common does not recognize it as there.
  Plus, --force-depends appears to be unavailable when using the '=' sign for a 
version-specific downgrade.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1537915/+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 1537915] Re: libgtk-3-common: Adwaita theme dependency misdetected because of missing libgtk-3-bin

[A. Eibach]

** Summary changed:

- libgtk-3-common: Adwaita theme dependency not recognized
+ libgtk-3-common: Adwaita theme dependency misdetected because of missing 
libgtk-3-bin

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

Title:
  libgtk-3-common: Adwaita theme dependency misdetected because of
  missing libgtk-3-bin

Status in gtk+3.0 package in Ubuntu:
  New

Bug description:
  Pre-note: due to severe bugs, I had to go down from 3.19.x back to 3.18.6.
  I think the following content will speak for itself:

  user@mybuntubox:~$ sudo apt-get install --reinstall adwaita-icon-theme
  Reading package lists... Done
  Building dependency tree
  Reading state information... Done
  0 to upgrade, 0 to newly install, 1 reinstalled, 0 to remove and 70 not to 
upgrade.
  Need to get 0 B/897 kB of archives.
  After this operation, 0 B of additional disk space will be used.
  (Reading database ... 307199 files and directories currently installed.)
  Preparing to unpack .../adwaita-icon-theme_3.18.0-2ubuntu1_all.deb ...
  Unpacking adwaita-icon-theme (3.18.0-2ubuntu1) over (3.18.0-2ubuntu1) ...
  Setting up adwaita-icon-theme (3.18.0-2ubuntu1) ...

  +++ OKAY. Adwaita Icon Theme is now installed and expected to be
  working. Version = __3.18.0-2__

  user@mybuntubox~$ sudo apt-get install libgtk-3-common=3.18.6-1ubuntu1
  Reading package lists... Done
  Building dependency tree
  Reading state information... Done
  Some packages could not be installed. This may mean that you have
  requested an impossible situation or if you are using the unstable
  distribution that some required packages have not yet been created
  or been moved out of Incoming.
  The following information may help to resolve the situation:

  The following packages have unmet dependencies.
   libgtk-3-common : Depends: adwaita-icon-theme (>= 3.18) but it is not going 
to be installed
     Recommends: libgtk-3-0 but it is not going to be installed
  E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by 
held packages.

  There is clearly something wrong.
  Just for "emphasis", I reinstalled Adwaita icon theme 3.18.x again above, to 
be sure it is really expected to be there.

  But it seems to be a bug that libgtk-3-common does not recognize it as there.
  Plus, --force-depends appears to be unavailable when using the '=' sign for a 
version-specific downgrade.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1537915/+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 1537915] [NEW] libgtk-3-common: Adwaita theme dependency not recognized

[A. Eibach]

Public bug reported:

Pre-note: due to severe bugs, I had to go down from 3.19.x back to 3.18.6.
I think the following content will speak for itself:

user@mybuntubox:~$ sudo apt-get install --reinstall adwaita-icon-theme
Reading package lists... Done
Building dependency tree
Reading state information... Done
0 to upgrade, 0 to newly install, 1 reinstalled, 0 to remove and 70 not to 
upgrade.
Need to get 0 B/897 kB of archives.
After this operation, 0 B of additional disk space will be used.
(Reading database ... 307199 files and directories currently installed.)
Preparing to unpack .../adwaita-icon-theme_3.18.0-2ubuntu1_all.deb ...
Unpacking adwaita-icon-theme (3.18.0-2ubuntu1) over (3.18.0-2ubuntu1) ...
Setting up adwaita-icon-theme (3.18.0-2ubuntu1) ...

+++ OKAY. Adwaita Icon Theme is now installed and expected to be
working. Version = __3.18.0-2__

user@mybuntubox~$ sudo apt-get install libgtk-3-common=3.18.6-1ubuntu1
Reading package lists... Done
Building dependency tree
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies.
 libgtk-3-common : Depends: adwaita-icon-theme (>= 3.18) but it is not going to 
be installed
   Recommends: libgtk-3-0 but it is not going to be installed
E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by 
held packages.

There is clearly something wrong.
Just for "emphasis", I reinstalled Adwaita icon theme 3.18.x again above, to be 
sure it is really expected to be there.

But it seems to be a bug that libgtk-3-common does not recognize it as there.
Plus, --force-depends appears to be unavailable when using the '=' sign for a 
version-specific downgrade.

** Affects: gtk+3.0 (Ubuntu)
 Importance: Undecided
 Status: New

** Description changed:

  Pre-note: due to severe bugs, I had to go down from 3.19.x back to 3.18.6.
  I think the following content will speak for itself:
  
  user@mybuntubox:~$ sudo apt-get install --reinstall adwaita-icon-theme
  Reading package lists... Done
  Building dependency tree
  Reading state information... Done
  0 to upgrade, 0 to newly install, 1 reinstalled, 0 to remove and 70 not to 
upgrade.
  Need to get 0 B/897 kB of archives.
  After this operation, 0 B of additional disk space will be used.
  (Reading database ... 307199 files and directories currently installed.)
  Preparing to unpack .../adwaita-icon-theme_3.18.0-2ubuntu1_all.deb ...
  Unpacking adwaita-icon-theme (3.18.0-2ubuntu1) over (3.18.0-2ubuntu1) ...
  Setting up adwaita-icon-theme (3.18.0-2ubuntu1) ...
  
  +++ OKAY. Adwaita Icon Theme is now installed and expected to be
- working. Version = 3.18.0-2.
+ working. Version = __3.18.0-2__
  
  user@mybuntubox~$ sudo apt-get install libgtk-3-common=3.18.6-1ubuntu1
  Reading package lists... Done
  Building dependency tree
  Reading state information... Done
  Some packages could not be installed. This may mean that you have
  requested an impossible situation or if you are using the unstable
  distribution that some required packages have not yet been created
  or been moved out of Incoming.
  The following information may help to resolve the situation:
  
  The following packages have unmet dependencies.
-  libgtk-3-common : Depends: adwaita-icon-theme (>= 3.18) but it is not going 
to be installed
-Recommends: libgtk-3-0 but it is not going to be installed
+  libgtk-3-common : Depends: adwaita-icon-theme (>= 3.18) but it is not going 
to be installed
+    Recommends: libgtk-3-0 but it is not going to be installed
  E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by 
held packages.
  
  There is clearly something wrong.
  Just for "emphasis", I reinstalled Adwaita icon theme 3.18.x again above, to 
be sure it is really expected to be there.
  
  But it seems to be a bug that libgtk-3-common does not recognize it as there.
  Plus, --force-depends appears to be unavailable when using the '=' sign for a 
version-specific downgrade.

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

Title:
  libgtk-3-common: Adwaita theme dependency not recognized

Status in gtk+3.0 package in Ubuntu:
  New

Bug description:
  Pre-note: due to severe bugs, I had to go down from 3.19.x back to 3.18.6.
  I think the following content will speak for itself:

  user@mybuntubox:~$ sudo apt-get install --reinstall adwaita-icon-theme
  Reading package lists... Done
  Building dependency tree
  Reading state information... Done
  0 to upgrade, 0 to newly install, 1 reinstalled, 0 to remove and 70 not 

[Touch-packages] [Bug 1537895] [NEW] Please include poppler-glib-demo tool in standard package

[A. Eibach]

Public bug reported:

I'm having an occasional issue with evince, and since the issue is
clearly related to the PDF engine underneath which it uses (*this), I
got a tip to run a PDF directly with 'poppler-glib-demo' in the
'poppler-demos' package.

However, this tip was NOT suitable for Ubuntu, as there is nothing like a 
'poppler-demos' package, but the whole package structure is different.
So this is one more for the wishlist.
poppler-glib-demo is not just a demo for developers, but will also show errors 
that evince may be blamed for (for no reason at all). evince simply uses lots 
of things under the hood, and one of them is poppler for PDF rendering.

ISTR that our Fedora colleagues do have this tool compiled in binary form and 
included in the package.
As I think it might be pretty useful for bug-hunting, I'd ask you kindly to no 
longer do without it when building the Ubuntu poppler package.
Thanks for considering.

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

** Description changed:

  I'm having an occasional issue with evince, and since the issue is
  clearly related to the PDF engine underneath which it uses (*this), I
  got a tip to run a PDF directly with 'poppler-glib-demo' in the
  'poppler-demos' package.
  
  This is one more for the wishlist.
  poppler-glib-demo is not just a demo for developers, but will also show 
errors that evince may be blamed for (for no reason at all). evince simply uses 
lots of things under the hood, and one of them is poppler for PDF rendering.
  
  ISTR that our Fedora colleagues do have this tool compiled in binary form and 
included in the package.
- As I think it might be pretty useful for bug-hunting, I'd ask you kindly to 
no longer omit it when building the package.
+ As I think it might be pretty useful for bug-hunting, I'd ask you kindly to 
no longer omit it when building the Ubuntu poppler package.
  Thanks for considering.

** Description changed:

  I'm having an occasional issue with evince, and since the issue is
  clearly related to the PDF engine underneath which it uses (*this), I
  got a tip to run a PDF directly with 'poppler-glib-demo' in the
  'poppler-demos' package.
  
  This is one more for the wishlist.
  poppler-glib-demo is not just a demo for developers, but will also show 
errors that evince may be blamed for (for no reason at all). evince simply uses 
lots of things under the hood, and one of them is poppler for PDF rendering.
  
  ISTR that our Fedora colleagues do have this tool compiled in binary form and 
included in the package.
- As I think it might be pretty useful for bug-hunting, I'd ask you kindly to 
no longer omit it when building the Ubuntu poppler package.
+ As I think it might be pretty useful for bug-hunting, I'd ask you kindly to 
no longer do without it when building the Ubuntu poppler package.
  Thanks for considering.

** Description changed:

  I'm having an occasional issue with evince, and since the issue is
  clearly related to the PDF engine underneath which it uses (*this), I
  got a tip to run a PDF directly with 'poppler-glib-demo' in the
  'poppler-demos' package.
  
- This is one more for the wishlist.
+ However, this tip was NOT suitable for Ubuntu, as there is nothing like a 
'poppler-demos' package, but the whole package structure is different.
+ So this is one more for the wishlist.
  poppler-glib-demo is not just a demo for developers, but will also show 
errors that evince may be blamed for (for no reason at all). evince simply uses 
lots of things under the hood, and one of them is poppler for PDF rendering.
  
  ISTR that our Fedora colleagues do have this tool compiled in binary form and 
included in the package.
  As I think it might be pretty useful for bug-hunting, I'd ask you kindly to 
no longer do without it when building the Ubuntu poppler package.
  Thanks for considering.

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

Title:
  Please include poppler-glib-demo tool in standard package

Status in poppler package in Ubuntu:
  New

Bug description:
  I'm having an occasional issue with evince, and since the issue is
  clearly related to the PDF engine underneath which it uses (*this), I
  got a tip to run a PDF directly with 'poppler-glib-demo' in the
  'poppler-demos' package.

  However, this tip was NOT suitable for Ubuntu, as there is nothing like a 
'poppler-demos' package, but the whole package structure is different.
  So this is one more for the wishlist.
  poppler-glib-demo is not just a demo for developers, but will also show 
errors that evince may be blamed for (for no reason at all). evince simply uses 
lots of things under the hood, and one of them is poppler for PDF rendering.

  ISTR that our Fedora colleagues do have this tool compiled in binary form and 
included in the package.
  As I think it might be 

[Touch-packages] [Bug 1489154] Re: NetworkManager does not start / fails to start

[A. Eibach]

TBH, I only enabled -proposed because openbox 3.6.0 runs so well and
because of major and severe bugs with old openbox and lxappearance. This
was so unbearable that I chose to upgrade to (allegedly "unstable")
v3.6.0 ... and lo' and behold, haven't run into problems for weeks.

-- 
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/1489154

Title:
  NetworkManager does not start / fails to start

Status in One Hundred Papercuts:
  Invalid
Status in network-manager package in Ubuntu:
  Invalid

Bug description:
  Yesterday i did the upgrade to version 1.0.4 of NetworkManger.

  Today my Xubuntu 15.10 cannot connect to the net, and wants to upload a crash 
report.
  This also fails cause the start of the NetworkManger fails after booting.

  Trying manually to start with

  ~$ sudo systemctl start NetworkManager

  leads that the icon comes up, disappears, comes up, disappears for 3,
  4 times and then it's gone forever.

  ~$ journalctl -xe
  Aug 26 22:02:34 Wily NetworkManager[1578]:   monitoring ifupdown state 
file '/run/network/ifstate'.
  Aug 26 22:02:34 Wily NetworkManager[1578]:   Loaded device plugin: 
NMVxlanFactory (internal)
  Aug 26 22:02:34 Wily NetworkManager[1578]:   Loaded device plugin: 
NMVlanFactory (internal)
  Aug 26 22:02:34 Wily NetworkManager[1578]:   Loaded device plugin: 
NMVethFactory (internal)
  Aug 26 22:02:34 Wily NetworkManager[1578]:   Loaded device plugin: 
NMTunFactory (internal)
  Aug 26 22:02:34 Wily NetworkManager[1578]:   Loaded device plugin: 
NMMacvlanFactory (internal)
  Aug 26 22:02:34 Wily NetworkManager[1578]:   Loaded device plugin: 
NMInfinibandFactory (internal)
  Aug 26 22:02:34 Wily NetworkManager[1578]:   Loaded device plugin: 
NMGreFactory (internal)
  Aug 26 22:02:34 Wily NetworkManager[1578]:   Loaded device plugin: 
NMEthernetFactory (internal)
  Aug 26 22:02:34 Wily NetworkManager[1578]:   Loaded device plugin: 
NMBridgeFactory (internal)
  Aug 26 22:02:34 Wily NetworkManager[1578]:   Loaded device plugin: 
NMBondFactory (internal)
  Aug 26 22:02:34 Wily NetworkManager[1578]:   Loaded device plugin: 
NMAtmManager 
(/usr/lib/i386-linux-gnu/NetworkManager/libnm-device-plugin-adsl.so)
  Aug 26 22:02:34 Wily NetworkManager[1578]:   Loaded device plugin: 
NMWifiFactory 
(/usr/lib/i386-linux-gnu/NetworkManager/libnm-device-plugin-wifi.so)
  Aug 26 22:02:34 Wily NetworkManager[1578]:   Loaded device plugin: 
NMBluezManager 
(/usr/lib/i386-linux-gnu/NetworkManager/libnm-device-plugin-bluetooth.so)
  Aug 26 22:02:34 Wily NetworkManager[1578]:   Loaded device plugin: 
NMWwanFactory 
(/usr/lib/i386-linux-gnu/NetworkManager/libnm-device-plugin-wwan.so)
  Aug 26 22:02:34 Wily NetworkManager[1578]:   WiFi enabled by radio 
killswitch; enabled by state file
  Aug 26 22:02:34 Wily NetworkManager[1578]:   WWAN enabled by radio 
killswitch; enabled by state file
  Aug 26 22:02:34 Wily NetworkManager[1578]:   WiMAX enabled by radio 
killswitch; enabled by state file
  Aug 26 22:02:34 Wily NetworkManager[1578]:   Networking is enabled by 
state file
  Aug 26 22:02:34 Wily NetworkManager[1578]: nm_device_get_device_type: 
assertion 'NM_IS_DEVICE (self)' failed
  Aug 26 22:02:34 Wily NetworkManager[1578]:   (lo): link connected
  Aug 26 22:02:34 Wily NetworkManager[1578]:   (lo): new Generic device 
(carrier: ON, driver: 'unknown', ifindex: 1)
  Aug 26 22:02:34 Wily NetworkManager[1578]:   (enp0s3): link connected
  Aug 26 22:02:34 Wily NetworkManager[1578]:   (enp0s3): new Ethernet 
device (carrier: ON, driver: 'e1000', ifindex: 2)
  Aug 26 22:02:34 Wily NetworkManager[1578]:   (enp0s3): device state 
change: unmanaged -> unavailable (reason 'managed') [10 20 2]
  Aug 26 22:02:34 Wily NetworkManager[1578]:   keyfile: add connection 
in-memory (4251ae7f-22a1-4de8-8f11-7a62fd420d65,"Kabelnetzwerkverbindung 1")
  Aug 26 22:02:34 Wily NetworkManager[1578]:   (enp0s3): created default 
wired connection 'Kabelnetzwerkverbindung 1'
  Aug 26 22:02:34 Wily NetworkManager[1578]:   urfkill disappeared from 
the bus
  Aug 26 22:02:34 Wily NetworkManager[1578]:   wpa_supplicant running
  Aug 26 22:02:34 Wily NetworkManager[1578]:   ModemManager available in 
the bus
  Aug 26 22:02:34 Wily NetworkManager[1578]:   ofono is now available
  Aug 26 22:02:34 Wily NetworkManager[1578]: (NetworkManager:1578): 
GLib-GObject-WARNING **: 
/build/glib2.0-6GfMH1/glib2.0-2.45.4/./gobject/gsignal.c:2480: signal 
'ModemAdded' is invalid for instance
  Aug 26 22:02:34 Wily NetworkManager[1578]: (NetworkManager:1578): 
GLib-GObject-WARNING **: 
/build/glib2.0-6GfMH1/glib2.0-2.45.4/./gobject/gsignal.c:2480: signal 
'ModemRemoved' is invalid for instan
  Aug 26 22:02:34 Wily NetworkManager[1578]: (NetworkManager:1578): 
GLib-CRITICAL **: g_variant_get_va: assertion 'value != NULL' failed
  Aug 26 22:02:34 Wily kernel: NetworkManager[1578]: segfault at c ip b6f4b97a 
sp bffb4890 

[Touch-packages] [Bug 1434986] Re: Not working network connection after boot

[A. Eibach]

...which has even been marked 'Invalid' as now.

-- 
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/1434986

Title:
  Not working network connection after boot

Status in NetworkManager:
  Confirmed
Status in network-manager package in Ubuntu:
  Triaged

Bug description:
  Directly after boot the network connections are not working. I am
  connected and have an IP address, but I cannot establish a connection
  with any Internet server.

  I have the impression it is related to thee DNS lookup, which waits
  forever for a result.

  Cycling the connection (disconnect->reconnect) seems to fix the
  problem for some time.

  I am reporting this against network-manager, but I am not sure if it is 
directly in network manager or if it is systemd related.
  With 14.10 everything worked perfectly.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: network-manager 0.9.10.0-4ubuntu11
  ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1
  Uname: Linux 3.19.0-9-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.16.2-0ubuntu4
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sun Mar 22 12:38:26 2015
  EcryptfsInUse: Yes
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2015-01-30 (50 days ago)
  InstallationMedia: Ubuntu-GNOME 14.10 "Utopic Unicorn" - Release amd64 
(20141022.1)
  IpRoute:
   default via 192.168.1.1 dev eth0  proto static  metric 1024 
   169.254.0.0/16 dev wlan0  scope link  metric 1000 
   192.168.1.0/24 dev wlan0  proto kernel  scope link  src 192.168.1.26 
   192.168.1.0/24 dev eth0  proto kernel  scope link  src 192.168.1.29
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to vivid on 2015-03-19 (3 days ago)
  modified.conffile..etc.NetworkManager.NetworkManager.conf: [modified]
  mtime.conffile..etc.NetworkManager.NetworkManager.conf: 
2015-02-16T00:14:50.662693
  nmcli-dev:
   DEVICE  TYPE  STATE  DBUS-PATH  
CONNECTION CON-UUID  CON-PATH   

   eth0ethernet  connected  /org/freedesktop/NetworkManager/Devices/2  
Kabelnetzwerkverbindung 1  4a581685-6002-4401-a993-49aa649667eb  
/org/freedesktop/NetworkManager/ActiveConnection/4 
   wlan0   wifi  connected  /org/freedesktop/NetworkManager/Devices/1  
4A616E7320574C414E f45aa3a7-fb44-41b7-a02a-ea9720d79414  
/org/freedesktop/NetworkManager/ActiveConnection/3 
   lo  loopback  unmanaged  /org/freedesktop/NetworkManager/Devices/0  --   
  ----
  nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 
2: Error: Object 'nm' is unknown, try 'nmcli help'.

To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager/+bug/1434986/+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 1263540] Re: Apt-get reports NO_PUBKEY gpg error for keys that are present in trusted.gpg.

[A. Eibach]

Ok, nuked /etc/apt/trusted.gpg and rebuilt is using

sudo apt-key update

YAY!!
That finally caused the error message of the very key 40976EAF437D05B5 to 
disappear. Good riddance. :P

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

Title:
  Apt-get reports NO_PUBKEY gpg error for keys that are present in
  trusted.gpg.

Status in APT:
  Fix Released
Status in apt package in Ubuntu:
  Fix Released

Bug description:
  Ubuntu 13.10
  apt  0.9.9.1~ubuntu3

  'apt-get update' has started showing several warnings like the
  following, even though the keys are present:

  W: GPG error: http://us.archive.ubuntu.com saucy Release: The
  following signatures couldn't be verified because the public key is
  not available: NO_PUBKEY 40976EAF437D05B5 NO_PUBKEY 3B4FE6ACC0B21F32

  'apt-key list' shows the keys in question in its output...

  pub   1024D/437D05B5 2004-09-12
  uid  Ubuntu Archive Automatic Signing Key 

  sub   2048g/79164387 2004-09-12

  pub   4096R/C0B21F32 2012-05-11
  uid  Ubuntu Archive Automatic Signing Key (2012) 


  ...and its output begins with the following:

  gpg: keyblock resource `/etc/apt/trusted.gpg.d//webupd8team-y-ppa-
  manager.gpg': resource limit

  I see the same gpg message when I manually update/remove/add the keys
  in question. E.g.:

  $ sudo apt-key update
  gpg: keyblock resource `/etc/apt/trusted.gpg.d//webupd8team-java.gpg': 
resource limit
  gpg: keyblock resource 
`/etc/apt/trusted.gpg.d//webupd8team-y-ppa-manager.gpg': resource limit
  gpg: key 437D05B5: "Ubuntu Archive Automatic Signing Key 
" not changed
  gpg: key FBB75451: "Ubuntu CD Image Automatic Signing Key 
" not changed
  gpg: key C0B21F32: "Ubuntu Archive Automatic Signing Key (2012) 
" not changed
  gpg: key EFE21092: "Ubuntu CD Image Automatic Signing Key (2012) 
" not changed
  gpg: Total number processed: 4
  gpg:  unchanged: 4

  I asked about the "resource limit" message on the gnupg-users mailing list...
  http://www.mail-archive.com/gnupg-users@gnupg.org/msg23300.html
  Based on Werner Koch's (the dev) answer...
  http://www.mail-archive.com/gnupg-users@gnupg.org/msg23302.html
  ...the secure apt related programs might be making gpg use more than the 
maximum number of keyrings that it can handle.

To manage notifications about this bug go to:
https://bugs.launchpad.net/apt/+bug/1263540/+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 1263540] Re: Apt-get reports NO_PUBKEY gpg error for keys that are present in trusted.gpg.

[A. Eibach]

(comment 7)

I can't believe it! THAT'S MINE!!!

40976EAF437D05B5

As I thought that it could even be related to some local repo not
updating their stuff in time (yes this happens sometimes in minor form),
I chenged to fr. and ch. domains sequentially. To no avail at all.

Thanks for the idea to use the 'del' option in apt-key.

I can't believe that so many people have problems with this, and all
that developers are (usually) raving about is whether Ubuntu should be
verbose to the user about global hotkey assignments or not. Securtity
paranoiacs, most of them, but if it comes to such basic-security issue
as here, they just go 'shrug, works for me, you're just too daft'.

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

Title:
  Apt-get reports NO_PUBKEY gpg error for keys that are present in
  trusted.gpg.

Status in APT:
  Fix Released
Status in apt package in Ubuntu:
  Fix Released

Bug description:
  Ubuntu 13.10
  apt  0.9.9.1~ubuntu3

  'apt-get update' has started showing several warnings like the
  following, even though the keys are present:

  W: GPG error: http://us.archive.ubuntu.com saucy Release: The
  following signatures couldn't be verified because the public key is
  not available: NO_PUBKEY 40976EAF437D05B5 NO_PUBKEY 3B4FE6ACC0B21F32

  'apt-key list' shows the keys in question in its output...

  pub   1024D/437D05B5 2004-09-12
  uid  Ubuntu Archive Automatic Signing Key 

  sub   2048g/79164387 2004-09-12

  pub   4096R/C0B21F32 2012-05-11
  uid  Ubuntu Archive Automatic Signing Key (2012) 


  ...and its output begins with the following:

  gpg: keyblock resource `/etc/apt/trusted.gpg.d//webupd8team-y-ppa-
  manager.gpg': resource limit

  I see the same gpg message when I manually update/remove/add the keys
  in question. E.g.:

  $ sudo apt-key update
  gpg: keyblock resource `/etc/apt/trusted.gpg.d//webupd8team-java.gpg': 
resource limit
  gpg: keyblock resource 
`/etc/apt/trusted.gpg.d//webupd8team-y-ppa-manager.gpg': resource limit
  gpg: key 437D05B5: "Ubuntu Archive Automatic Signing Key 
" not changed
  gpg: key FBB75451: "Ubuntu CD Image Automatic Signing Key 
" not changed
  gpg: key C0B21F32: "Ubuntu Archive Automatic Signing Key (2012) 
" not changed
  gpg: key EFE21092: "Ubuntu CD Image Automatic Signing Key (2012) 
" not changed
  gpg: Total number processed: 4
  gpg:  unchanged: 4

  I asked about the "resource limit" message on the gnupg-users mailing list...
  http://www.mail-archive.com/gnupg-users@gnupg.org/msg23300.html
  Based on Werner Koch's (the dev) answer...
  http://www.mail-archive.com/gnupg-users@gnupg.org/msg23302.html
  ...the secure apt related programs might be making gpg use more than the 
maximum number of keyrings that it can handle.

To manage notifications about this bug go to:
https://bugs.launchpad.net/apt/+bug/1263540/+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 1489154] Re: NetworkManager does not start / fails to start

[A. Eibach]

>For reference, the way to upgrade NetworkManager is the following:
>
>sudo apt-get install -t wily-proposed network-manager libnm0 libnm-glib4 
>libnm-util2 gir1.2-networkmanager-1.0

Mathieu,

though this ssounds all pretty structured and logical, I think I know where 
these issues come from.
Most users will just go the all-in-one upgrade way by 'apt-get upgrade' and 
hence would not be able to fine-tune settings as in the APT line I've quoted 
from you above.

What you've suggested must be executed BEFORE even THINKING about using apt-get 
upgrade.
Because then, the network-manager including its dependencies will already have 
been crossed out from the list.

-- 
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/1489154

Title:
  NetworkManager does not start / fails to start

Status in One Hundred Papercuts:
  Invalid
Status in network-manager package in Ubuntu:
  Invalid

Bug description:
  Yesterday i did the upgrade to version 1.0.4 of NetworkManger.

  Today my Xubuntu 15.10 cannot connect to the net, and wants to upload a crash 
report.
  This also fails cause the start of the NetworkManger fails after booting.

  Trying manually to start with

  ~$ sudo systemctl start NetworkManager

  leads that the icon comes up, disappears, comes up, disappears for 3,
  4 times and then it's gone forever.

  ~$ journalctl -xe
  Aug 26 22:02:34 Wily NetworkManager[1578]:   monitoring ifupdown state 
file '/run/network/ifstate'.
  Aug 26 22:02:34 Wily NetworkManager[1578]:   Loaded device plugin: 
NMVxlanFactory (internal)
  Aug 26 22:02:34 Wily NetworkManager[1578]:   Loaded device plugin: 
NMVlanFactory (internal)
  Aug 26 22:02:34 Wily NetworkManager[1578]:   Loaded device plugin: 
NMVethFactory (internal)
  Aug 26 22:02:34 Wily NetworkManager[1578]:   Loaded device plugin: 
NMTunFactory (internal)
  Aug 26 22:02:34 Wily NetworkManager[1578]:   Loaded device plugin: 
NMMacvlanFactory (internal)
  Aug 26 22:02:34 Wily NetworkManager[1578]:   Loaded device plugin: 
NMInfinibandFactory (internal)
  Aug 26 22:02:34 Wily NetworkManager[1578]:   Loaded device plugin: 
NMGreFactory (internal)
  Aug 26 22:02:34 Wily NetworkManager[1578]:   Loaded device plugin: 
NMEthernetFactory (internal)
  Aug 26 22:02:34 Wily NetworkManager[1578]:   Loaded device plugin: 
NMBridgeFactory (internal)
  Aug 26 22:02:34 Wily NetworkManager[1578]:   Loaded device plugin: 
NMBondFactory (internal)
  Aug 26 22:02:34 Wily NetworkManager[1578]:   Loaded device plugin: 
NMAtmManager 
(/usr/lib/i386-linux-gnu/NetworkManager/libnm-device-plugin-adsl.so)
  Aug 26 22:02:34 Wily NetworkManager[1578]:   Loaded device plugin: 
NMWifiFactory 
(/usr/lib/i386-linux-gnu/NetworkManager/libnm-device-plugin-wifi.so)
  Aug 26 22:02:34 Wily NetworkManager[1578]:   Loaded device plugin: 
NMBluezManager 
(/usr/lib/i386-linux-gnu/NetworkManager/libnm-device-plugin-bluetooth.so)
  Aug 26 22:02:34 Wily NetworkManager[1578]:   Loaded device plugin: 
NMWwanFactory 
(/usr/lib/i386-linux-gnu/NetworkManager/libnm-device-plugin-wwan.so)
  Aug 26 22:02:34 Wily NetworkManager[1578]:   WiFi enabled by radio 
killswitch; enabled by state file
  Aug 26 22:02:34 Wily NetworkManager[1578]:   WWAN enabled by radio 
killswitch; enabled by state file
  Aug 26 22:02:34 Wily NetworkManager[1578]:   WiMAX enabled by radio 
killswitch; enabled by state file
  Aug 26 22:02:34 Wily NetworkManager[1578]:   Networking is enabled by 
state file
  Aug 26 22:02:34 Wily NetworkManager[1578]: nm_device_get_device_type: 
assertion 'NM_IS_DEVICE (self)' failed
  Aug 26 22:02:34 Wily NetworkManager[1578]:   (lo): link connected
  Aug 26 22:02:34 Wily NetworkManager[1578]:   (lo): new Generic device 
(carrier: ON, driver: 'unknown', ifindex: 1)
  Aug 26 22:02:34 Wily NetworkManager[1578]:   (enp0s3): link connected
  Aug 26 22:02:34 Wily NetworkManager[1578]:   (enp0s3): new Ethernet 
device (carrier: ON, driver: 'e1000', ifindex: 2)
  Aug 26 22:02:34 Wily NetworkManager[1578]:   (enp0s3): device state 
change: unmanaged -> unavailable (reason 'managed') [10 20 2]
  Aug 26 22:02:34 Wily NetworkManager[1578]:   keyfile: add connection 
in-memory (4251ae7f-22a1-4de8-8f11-7a62fd420d65,"Kabelnetzwerkverbindung 1")
  Aug 26 22:02:34 Wily NetworkManager[1578]:   (enp0s3): created default 
wired connection 'Kabelnetzwerkverbindung 1'
  Aug 26 22:02:34 Wily NetworkManager[1578]:   urfkill disappeared from 
the bus
  Aug 26 22:02:34 Wily NetworkManager[1578]:   wpa_supplicant running
  Aug 26 22:02:34 Wily NetworkManager[1578]:   ModemManager available in 
the bus
  Aug 26 22:02:34 Wily NetworkManager[1578]:   ofono is now available
  Aug 26 22:02:34 Wily NetworkManager[1578]: (NetworkManager:1578): 
GLib-GObject-WARNING **: 
/build/glib2.0-6GfMH1/glib2.0-2.45.4/./gobject/gsignal.c:2480: signal 
'ModemAdded' is invalid for instance
  Aug 26 22:02:34 Wily NetworkManager[1578]: 

[Touch-packages] [Bug 1489154] Re: NetworkManager does not start / fails to start

[A. Eibach]

Importance=Critical --- YES!
No network, no internet - zilch. That is, if you choose to use this broken 
version.

Any developer around?

Please, anyone don't you go annoying me with apport reports (I hate
apport), you will only get these few gdb lines from me, which ought to
be enough to find the problem:

Reading symbols from /usr/sbin/NetworkManager...(no debugging symbols 
found)...done.
[New LWP 1745]
[New LWP 1746]
[New LWP 1747]
[New LWP 1748]
[Thread debugging using libthread_db enabled]
Using host libthread_db library /lib/i386-linux-gnu/libthread_db.so.1.
Core was generated by `NetworkManager'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0  0xb6f4961a in g_variant_iter_loop ()
   from /lib/i386-linux-gnu/libglib-2.0.so.0

--

g_variant_iter_loop()

It's an iterator mechanism: 
https://developer.gnome.org/glib/stable/glib-GVariant.html#g-variant-iter-loop
Possibly one pointer is NULL or the new NM build will only work with a 
bleeding-edge, devel version of glib (I assume it's the latter).

-- 
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/1489154

Title:
  NetworkManager does not start / fails to start

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Yesterday i did the upgrade to version 1.0.4 of NetworkManger.

  Today my Xubuntu 15.10 cannot connect to the net, and wants to upload a crash 
report.
  This also fails cause the start of the NetworkManger fails after booting.

  Trying manually to start with

  ~$ sudo systemctl start NetworkManager

  leads that the icon comes up, disappears, comes up, disappears for 3,
  4 times and then it's gone forever.

  ~$ journalctl -xe
  Aug 26 22:02:34 Wily NetworkManager[1578]: info  monitoring ifupdown state 
file '/run/network/ifstate'.
  Aug 26 22:02:34 Wily NetworkManager[1578]: info  Loaded device plugin: 
NMVxlanFactory (internal)
  Aug 26 22:02:34 Wily NetworkManager[1578]: info  Loaded device plugin: 
NMVlanFactory (internal)
  Aug 26 22:02:34 Wily NetworkManager[1578]: info  Loaded device plugin: 
NMVethFactory (internal)
  Aug 26 22:02:34 Wily NetworkManager[1578]: info  Loaded device plugin: 
NMTunFactory (internal)
  Aug 26 22:02:34 Wily NetworkManager[1578]: info  Loaded device plugin: 
NMMacvlanFactory (internal)
  Aug 26 22:02:34 Wily NetworkManager[1578]: info  Loaded device plugin: 
NMInfinibandFactory (internal)
  Aug 26 22:02:34 Wily NetworkManager[1578]: info  Loaded device plugin: 
NMGreFactory (internal)
  Aug 26 22:02:34 Wily NetworkManager[1578]: info  Loaded device plugin: 
NMEthernetFactory (internal)
  Aug 26 22:02:34 Wily NetworkManager[1578]: info  Loaded device plugin: 
NMBridgeFactory (internal)
  Aug 26 22:02:34 Wily NetworkManager[1578]: info  Loaded device plugin: 
NMBondFactory (internal)
  Aug 26 22:02:34 Wily NetworkManager[1578]: info  Loaded device plugin: 
NMAtmManager 
(/usr/lib/i386-linux-gnu/NetworkManager/libnm-device-plugin-adsl.so)
  Aug 26 22:02:34 Wily NetworkManager[1578]: info  Loaded device plugin: 
NMWifiFactory 
(/usr/lib/i386-linux-gnu/NetworkManager/libnm-device-plugin-wifi.so)
  Aug 26 22:02:34 Wily NetworkManager[1578]: info  Loaded device plugin: 
NMBluezManager 
(/usr/lib/i386-linux-gnu/NetworkManager/libnm-device-plugin-bluetooth.so)
  Aug 26 22:02:34 Wily NetworkManager[1578]: info  Loaded device plugin: 
NMWwanFactory 
(/usr/lib/i386-linux-gnu/NetworkManager/libnm-device-plugin-wwan.so)
  Aug 26 22:02:34 Wily NetworkManager[1578]: info  WiFi enabled by radio 
killswitch; enabled by state file
  Aug 26 22:02:34 Wily NetworkManager[1578]: info  WWAN enabled by radio 
killswitch; enabled by state file
  Aug 26 22:02:34 Wily NetworkManager[1578]: info  WiMAX enabled by radio 
killswitch; enabled by state file
  Aug 26 22:02:34 Wily NetworkManager[1578]: info  Networking is enabled by 
state file
  Aug 26 22:02:34 Wily NetworkManager[1578]: nm_device_get_device_type: 
assertion 'NM_IS_DEVICE (self)' failed
  Aug 26 22:02:34 Wily NetworkManager[1578]: info  (lo): link connected
  Aug 26 22:02:34 Wily NetworkManager[1578]: info  (lo): new Generic device 
(carrier: ON, driver: 'unknown', ifindex: 1)
  Aug 26 22:02:34 Wily NetworkManager[1578]: info  (enp0s3): link connected
  Aug 26 22:02:34 Wily NetworkManager[1578]: info  (enp0s3): new Ethernet 
device (carrier: ON, driver: 'e1000', ifindex: 2)
  Aug 26 22:02:34 Wily NetworkManager[1578]: info  (enp0s3): device state 
change: unmanaged - unavailable (reason 'managed') [10 20 2]
  Aug 26 22:02:34 Wily NetworkManager[1578]: info  keyfile: add connection 
in-memory (4251ae7f-22a1-4de8-8f11-7a62fd420d65,Kabelnetzwerkverbindung 1)
  Aug 26 22:02:34 Wily NetworkManager[1578]: info  (enp0s3): created default 
wired connection 'Kabelnetzwerkverbindung 1'
  Aug 26 22:02:34 Wily NetworkManager[1578]: info  urfkill disappeared from 
the bus
  Aug 26 22:02:34 Wily NetworkManager[1578]: 

[Touch-packages] [Bug 1489154] Re: NetworkManager does not start / fails to start

[A. Eibach]

JFTR, mine is 2.45.3-1 . (libglibmm @ 2.44.0-1)

-- 
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/1489154

Title:
  NetworkManager does not start / fails to start

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Yesterday i did the upgrade to version 1.0.4 of NetworkManger.

  Today my Xubuntu 15.10 cannot connect to the net, and wants to upload a crash 
report.
  This also fails cause the start of the NetworkManger fails after booting.

  Trying manually to start with

  ~$ sudo systemctl start NetworkManager

  leads that the icon comes up, disappears, comes up, disappears for 3,
  4 times and then it's gone forever.

  ~$ journalctl -xe
  Aug 26 22:02:34 Wily NetworkManager[1578]: info  monitoring ifupdown state 
file '/run/network/ifstate'.
  Aug 26 22:02:34 Wily NetworkManager[1578]: info  Loaded device plugin: 
NMVxlanFactory (internal)
  Aug 26 22:02:34 Wily NetworkManager[1578]: info  Loaded device plugin: 
NMVlanFactory (internal)
  Aug 26 22:02:34 Wily NetworkManager[1578]: info  Loaded device plugin: 
NMVethFactory (internal)
  Aug 26 22:02:34 Wily NetworkManager[1578]: info  Loaded device plugin: 
NMTunFactory (internal)
  Aug 26 22:02:34 Wily NetworkManager[1578]: info  Loaded device plugin: 
NMMacvlanFactory (internal)
  Aug 26 22:02:34 Wily NetworkManager[1578]: info  Loaded device plugin: 
NMInfinibandFactory (internal)
  Aug 26 22:02:34 Wily NetworkManager[1578]: info  Loaded device plugin: 
NMGreFactory (internal)
  Aug 26 22:02:34 Wily NetworkManager[1578]: info  Loaded device plugin: 
NMEthernetFactory (internal)
  Aug 26 22:02:34 Wily NetworkManager[1578]: info  Loaded device plugin: 
NMBridgeFactory (internal)
  Aug 26 22:02:34 Wily NetworkManager[1578]: info  Loaded device plugin: 
NMBondFactory (internal)
  Aug 26 22:02:34 Wily NetworkManager[1578]: info  Loaded device plugin: 
NMAtmManager 
(/usr/lib/i386-linux-gnu/NetworkManager/libnm-device-plugin-adsl.so)
  Aug 26 22:02:34 Wily NetworkManager[1578]: info  Loaded device plugin: 
NMWifiFactory 
(/usr/lib/i386-linux-gnu/NetworkManager/libnm-device-plugin-wifi.so)
  Aug 26 22:02:34 Wily NetworkManager[1578]: info  Loaded device plugin: 
NMBluezManager 
(/usr/lib/i386-linux-gnu/NetworkManager/libnm-device-plugin-bluetooth.so)
  Aug 26 22:02:34 Wily NetworkManager[1578]: info  Loaded device plugin: 
NMWwanFactory 
(/usr/lib/i386-linux-gnu/NetworkManager/libnm-device-plugin-wwan.so)
  Aug 26 22:02:34 Wily NetworkManager[1578]: info  WiFi enabled by radio 
killswitch; enabled by state file
  Aug 26 22:02:34 Wily NetworkManager[1578]: info  WWAN enabled by radio 
killswitch; enabled by state file
  Aug 26 22:02:34 Wily NetworkManager[1578]: info  WiMAX enabled by radio 
killswitch; enabled by state file
  Aug 26 22:02:34 Wily NetworkManager[1578]: info  Networking is enabled by 
state file
  Aug 26 22:02:34 Wily NetworkManager[1578]: nm_device_get_device_type: 
assertion 'NM_IS_DEVICE (self)' failed
  Aug 26 22:02:34 Wily NetworkManager[1578]: info  (lo): link connected
  Aug 26 22:02:34 Wily NetworkManager[1578]: info  (lo): new Generic device 
(carrier: ON, driver: 'unknown', ifindex: 1)
  Aug 26 22:02:34 Wily NetworkManager[1578]: info  (enp0s3): link connected
  Aug 26 22:02:34 Wily NetworkManager[1578]: info  (enp0s3): new Ethernet 
device (carrier: ON, driver: 'e1000', ifindex: 2)
  Aug 26 22:02:34 Wily NetworkManager[1578]: info  (enp0s3): device state 
change: unmanaged - unavailable (reason 'managed') [10 20 2]
  Aug 26 22:02:34 Wily NetworkManager[1578]: info  keyfile: add connection 
in-memory (4251ae7f-22a1-4de8-8f11-7a62fd420d65,Kabelnetzwerkverbindung 1)
  Aug 26 22:02:34 Wily NetworkManager[1578]: info  (enp0s3): created default 
wired connection 'Kabelnetzwerkverbindung 1'
  Aug 26 22:02:34 Wily NetworkManager[1578]: info  urfkill disappeared from 
the bus
  Aug 26 22:02:34 Wily NetworkManager[1578]: info  wpa_supplicant running
  Aug 26 22:02:34 Wily NetworkManager[1578]: info  ModemManager available in 
the bus
  Aug 26 22:02:34 Wily NetworkManager[1578]: info  ofono is now available
  Aug 26 22:02:34 Wily NetworkManager[1578]: (NetworkManager:1578): 
GLib-GObject-WARNING **: 
/build/glib2.0-6GfMH1/glib2.0-2.45.4/./gobject/gsignal.c:2480: signal 
'ModemAdded' is invalid for instance
  Aug 26 22:02:34 Wily NetworkManager[1578]: (NetworkManager:1578): 
GLib-GObject-WARNING **: 
/build/glib2.0-6GfMH1/glib2.0-2.45.4/./gobject/gsignal.c:2480: signal 
'ModemRemoved' is invalid for instan
  Aug 26 22:02:34 Wily NetworkManager[1578]: (NetworkManager:1578): 
GLib-CRITICAL **: g_variant_get_va: assertion 'value != NULL' failed
  Aug 26 22:02:34 Wily kernel: NetworkManager[1578]: segfault at c ip b6f4b97a 
sp bffb4890 error 4 in libglib-2.0.so.0.4504.0[b6ec8000+127000]
  Aug 26 22:02:34 Wily systemd[1]: NetworkManager.service: Main process exited, 
code=dumped, 

[Touch-packages] [Bug 1434986] Re: Not working network connection after boot

[A. Eibach]

Confirming with 1.0.4.

But WFM with 0.19.10.0.

BTW, instead of funny guessing, just do

ps -ef | grep NetworkManager


/usr/sbin/NetworkManager *MUST* be running if you want to access the Internet.

1.0.4 did NOT run. When checking /var/log/*.crash files, I found a 
network-manager-related crash file which indicated that NM had crashed way 
before it got to the graphical login screen.
Downgraded NM and everything worked as expected.

-- 
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/1434986

Title:
  Not working network connection after boot

Status in NetworkManager:
  Confirmed
Status in network-manager package in Ubuntu:
  Triaged

Bug description:
  Directly after boot the network connections are not working. I am
  connected and have an IP address, but I cannot establish a connection
  with any Internet server.

  I have the impression it is related to thee DNS lookup, which waits
  forever for a result.

  Cycling the connection (disconnect-reconnect) seems to fix the
  problem for some time.

  I am reporting this against network-manager, but I am not sure if it is 
directly in network manager or if it is systemd related.
  With 14.10 everything worked perfectly.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: network-manager 0.9.10.0-4ubuntu11
  ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1
  Uname: Linux 3.19.0-9-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.16.2-0ubuntu4
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sun Mar 22 12:38:26 2015
  EcryptfsInUse: Yes
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2015-01-30 (50 days ago)
  InstallationMedia: Ubuntu-GNOME 14.10 Utopic Unicorn - Release amd64 
(20141022.1)
  IpRoute:
   default via 192.168.1.1 dev eth0  proto static  metric 1024 
   169.254.0.0/16 dev wlan0  scope link  metric 1000 
   192.168.1.0/24 dev wlan0  proto kernel  scope link  src 192.168.1.26 
   192.168.1.0/24 dev eth0  proto kernel  scope link  src 192.168.1.29
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to vivid on 2015-03-19 (3 days ago)
  modified.conffile..etc.NetworkManager.NetworkManager.conf: [modified]
  mtime.conffile..etc.NetworkManager.NetworkManager.conf: 
2015-02-16T00:14:50.662693
  nmcli-dev:
   DEVICE  TYPE  STATE  DBUS-PATH  
CONNECTION CON-UUID  CON-PATH   

   eth0ethernet  connected  /org/freedesktop/NetworkManager/Devices/2  
Kabelnetzwerkverbindung 1  4a581685-6002-4401-a993-49aa649667eb  
/org/freedesktop/NetworkManager/ActiveConnection/4 
   wlan0   wifi  connected  /org/freedesktop/NetworkManager/Devices/1  
4A616E7320574C414E f45aa3a7-fb44-41b7-a02a-ea9720d79414  
/org/freedesktop/NetworkManager/ActiveConnection/3 
   lo  loopback  unmanaged  /org/freedesktop/NetworkManager/Devices/0  --   
  ----
  nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 
2: Error: Object 'nm' is unknown, try 'nmcli help'.

To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager/+bug/1434986/+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 1489154] Re: NetworkManager does not start / fails to start

[A. Eibach]

OK,  so my bug must be in ./NetworkManager/libnm/nm-device-wifi.c

in the function as follows:

prepare_scan_options (GVariant *options)
{
 ..

if (!options)
284 variant = g_variant_new_array (G_VARIANT_TYPE ({sv}), 
NULL, 0);
285 else {
286 g_variant_builder_init (builder, 
G_VARIANT_TYPE_VARDICT);
287 g_variant_iter_init (iter, options);
288 while (g_variant_iter_loop (iter, {sv}, key, 
value))
289 {
290 // FIXME: verify options here?
291 g_variant_builder_add (builder, {sv}, key, 
value);
292 }
293 variant = g_variant_builder_end (builder);
294 }
...
}

Heh...

// FIXME: verify options here?

Yes, that would be a good idea. Otherwise things like these here may
happen. :-]

-- 
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/1489154

Title:
  NetworkManager does not start / fails to start

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Yesterday i did the upgrade to version 1.0.4 of NetworkManger.

  Today my Xubuntu 15.10 cannot connect to the net, and wants to upload a crash 
report.
  This also fails cause the start of the NetworkManger fails after booting.

  Trying manually to start with

  ~$ sudo systemctl start NetworkManager

  leads that the icon comes up, disappears, comes up, disappears for 3,
  4 times and then it's gone forever.

  ~$ journalctl -xe
  Aug 26 22:02:34 Wily NetworkManager[1578]: info  monitoring ifupdown state 
file '/run/network/ifstate'.
  Aug 26 22:02:34 Wily NetworkManager[1578]: info  Loaded device plugin: 
NMVxlanFactory (internal)
  Aug 26 22:02:34 Wily NetworkManager[1578]: info  Loaded device plugin: 
NMVlanFactory (internal)
  Aug 26 22:02:34 Wily NetworkManager[1578]: info  Loaded device plugin: 
NMVethFactory (internal)
  Aug 26 22:02:34 Wily NetworkManager[1578]: info  Loaded device plugin: 
NMTunFactory (internal)
  Aug 26 22:02:34 Wily NetworkManager[1578]: info  Loaded device plugin: 
NMMacvlanFactory (internal)
  Aug 26 22:02:34 Wily NetworkManager[1578]: info  Loaded device plugin: 
NMInfinibandFactory (internal)
  Aug 26 22:02:34 Wily NetworkManager[1578]: info  Loaded device plugin: 
NMGreFactory (internal)
  Aug 26 22:02:34 Wily NetworkManager[1578]: info  Loaded device plugin: 
NMEthernetFactory (internal)
  Aug 26 22:02:34 Wily NetworkManager[1578]: info  Loaded device plugin: 
NMBridgeFactory (internal)
  Aug 26 22:02:34 Wily NetworkManager[1578]: info  Loaded device plugin: 
NMBondFactory (internal)
  Aug 26 22:02:34 Wily NetworkManager[1578]: info  Loaded device plugin: 
NMAtmManager 
(/usr/lib/i386-linux-gnu/NetworkManager/libnm-device-plugin-adsl.so)
  Aug 26 22:02:34 Wily NetworkManager[1578]: info  Loaded device plugin: 
NMWifiFactory 
(/usr/lib/i386-linux-gnu/NetworkManager/libnm-device-plugin-wifi.so)
  Aug 26 22:02:34 Wily NetworkManager[1578]: info  Loaded device plugin: 
NMBluezManager 
(/usr/lib/i386-linux-gnu/NetworkManager/libnm-device-plugin-bluetooth.so)
  Aug 26 22:02:34 Wily NetworkManager[1578]: info  Loaded device plugin: 
NMWwanFactory 
(/usr/lib/i386-linux-gnu/NetworkManager/libnm-device-plugin-wwan.so)
  Aug 26 22:02:34 Wily NetworkManager[1578]: info  WiFi enabled by radio 
killswitch; enabled by state file
  Aug 26 22:02:34 Wily NetworkManager[1578]: info  WWAN enabled by radio 
killswitch; enabled by state file
  Aug 26 22:02:34 Wily NetworkManager[1578]: info  WiMAX enabled by radio 
killswitch; enabled by state file
  Aug 26 22:02:34 Wily NetworkManager[1578]: info  Networking is enabled by 
state file
  Aug 26 22:02:34 Wily NetworkManager[1578]: nm_device_get_device_type: 
assertion 'NM_IS_DEVICE (self)' failed
  Aug 26 22:02:34 Wily NetworkManager[1578]: info  (lo): link connected
  Aug 26 22:02:34 Wily NetworkManager[1578]: info  (lo): new Generic device 
(carrier: ON, driver: 'unknown', ifindex: 1)
  Aug 26 22:02:34 Wily NetworkManager[1578]: info  (enp0s3): link connected
  Aug 26 22:02:34 Wily NetworkManager[1578]: info  (enp0s3): new Ethernet 
device (carrier: ON, driver: 'e1000', ifindex: 2)
  Aug 26 22:02:34 Wily NetworkManager[1578]: info  (enp0s3): device state 
change: unmanaged - unavailable (reason 'managed') [10 20 2]
  Aug 26 22:02:34 Wily NetworkManager[1578]: info  keyfile: add connection 
in-memory (4251ae7f-22a1-4de8-8f11-7a62fd420d65,Kabelnetzwerkverbindung 1)
  Aug 26 22:02:34 Wily NetworkManager[1578]: info  (enp0s3): created default 
wired connection 'Kabelnetzwerkverbindung 1'
  Aug 26 22:02:34 Wily NetworkManager[1578]: info  urfkill disappeared from 
the bus
  Aug 26 22:02:34 Wily NetworkManager[1578]: info  wpa_supplicant running
  Aug 26 22:02:34 Wily NetworkManager[1578]: info  ModemManager available in 
the bus
  Aug 26 

[Touch-packages] [Bug 1384416] Re: coreutils 'info command' broken

[A. Eibach]

Nice ... just wondering if this fix wouldn't have to be rolled back
again soon since roughly 100 tools have been recompiled after the recent
change(s)?

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

Title:
  coreutils 'info command' broken

Status in The Gnu Core Utilities:
  Fix Released
Status in “coreutils” package in Ubuntu:
  Triaged

Bug description:
  Try the following on Ubuntu (or one of its flavors) and tell me what
  you see:

  $ info coreutils 'cat invocation'

  Should give you the *detailed* cat manual. However,  you will in fact
  land on 2.14 'coreutils' Multi-call binary in the documentation. Now
  idea yet how to fix this.

  Great job. Seems the bug they reported on Debian mailing list on 9/11
  (2014)

  https://www.mail-archive.com/debian-bugs-
  d...@lists.debian.org/msg1256146.html

  ... has now made its way into the Ubuntu version of coreutils as well.

  By the way,  isn't that a great comment again??

  though downstream 8.23 could be tweaked to avoid this issue.

  Cool. They've broken something that worked perfectly _for years_ and
  all the user gets is yeah, 8.23 'could be tweaked'. If only he had
  said _how_ to tweak it!! But apparently the commenter was way too lazy
  to write one more line.

To manage notifications about this bug go to:
https://bugs.launchpad.net/coreutils/+bug/1384416/+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 1384416] Re: coreutils 'info command' broken

[A. Eibach]

** Package changed: ubuntu = coreutils (Ubuntu)

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

Title:
  coreutils 'info command' broken

Status in “coreutils” package in Ubuntu:
  New

Bug description:
  Try the following on Ubuntu (or one of its flavors) and tell me what
  you see:

  $ info coreutils 'cat invocation'

  Should give you the *detailed* cat manual. However,  you will in fact
  land on 2.14 'coreutils' Multi-call binary in the documentation. Now
  idea yet how to fix this.

  Great job. Seems the bug they reported on Debian mailing list on 9/11
  (2014)

  https://www.mail-archive.com/debian-bugs-
  d...@lists.debian.org/msg1256146.html

  ... has now made its way into the Ubuntu version of coreutils as well.

  By the way,  isn't that a great comment again??

  though downstream 8.23 could be tweaked to avoid this issue.

  Cool. They've broken something that worked perfectly _for years_ and
  all the user gets is yeah, 8.23 'could be tweaked'. If only he had
  said _how_ to tweak it!! But apparently the commenter was way too lazy
  to write one more line.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/1384416/+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 1359990] Re: Strange quotation in german messages. i.e. 'cp -v .bashrc /tmp/' outputs: ».bashrc“ - »/tmp/.bashrc“

[A. Eibach]

Agree. They should definitely not be _mixed_.

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

Title:
  Strange quotation in german messages. i.e. 'cp -v .bashrc /tmp/'
  outputs: ».bashrc“ - »/tmp/.bashrc“

Status in “coreutils” package in Ubuntu:
  New

Bug description:
  This is about a strange quotation in some german messages, see:

  $ cp -v .bashrc /tmp/
  ».bashrc“ - »/tmp/.bashrc“

  $ cp /tmp/does_not_exist .
  cp: der Aufruf von stat für »/tmp/does_not_exist“ ist nicht möglich: Datei 
oder Verzeichnis nicht gefunden

  I'm talking about the » and “ characters. They should be „ and “, as
  can be found in the usage message of cp:

  $ cp
  cp: Fehlender Dateioperand
  „cp --help“ liefert weitere Informationen.

  The english messages all use ' for the quotation marks, which is ok:

  $ LANG=C cp -v .bashrc /tmp/
  '.bashrc' - '/tmp/.bashrc'

  I'd like to sum up the german wikipedia on quotation marks
  (https://de.wikipedia.org/wiki/Anführungszeichen):

  * When using a typewriter, both ... or '...' can be used.
  * In germany and austria, both „...“ and »...« can be used. I'd prefer „...“, 
as the latter is not widely used in germany.
  * In switzerland, liechtenstein and france, «…» is used.

  Note that  (typewriter version) and “ (to be used together with „)
  are different characters.

  Sure, there are many possibilities, but the current messages are
  wrong!

  I'd prefer '...' at least for the output of 'cp -v ...', as this might be 
parsed in some shell scripts. For consistency,
  I would vote for using '...' everywhere.

  Alternatively, using „...“ everywhere would also be a good choice.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: coreutils 8.21-1ubuntu5
  ProcVersionSignature: Ubuntu 3.13.0-34.60-generic 3.13.11.4
  Uname: Linux 3.13.0-34-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.3
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Thu Aug 21 23:20:41 2014
  InstallationDate: Installed on 2012-08-12 (739 days ago)
  InstallationMedia: Kubuntu 12.04 LTS Precise Pangolin - Release amd64 
(20120423)
  SourcePackage: coreutils
  UpgradeStatus: Upgraded to trusty on 2014-04-21 (122 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/1359990/+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 1179487] Re: wrong output of command /usr/bin/seq

[A. Eibach]

WFM!  (at least now)

Lubuntu 14.10 (devel)

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

Title:
  wrong output of command /usr/bin/seq

Status in “coreutils” package in Ubuntu:
  New

Bug description:
  The command seq return wrong output when parameter -s is used

  $ seq --help
  ...
  -s, --separator=STRING   use STRING to separate numbers (default: \n)
  ...

  Example:

  On Ubuntu (wrong):
  $ /usr/bin/seq -s , 10
  1
  2,3,4,5,6,7,8,9,10,


  On Debian (all right):
  $ /usr/bin/seq -s , 10
  1,2,3,4,5,6,7,8,9,10

  More info:

  $ lsb_release -rd
  Description:Ubuntu 13.04
  Release:13.04

  $ dpkg -l coreutils
  ii  coreutils  8.20-3ubuntu5  
  amd64GNU core utilities

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: coreutils 8.20-3ubuntu5
  ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8
  Uname: Linux 3.8.0-19-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.9.2-0ubuntu8
  Architecture: amd64
  Date: Mon May 13 14:27:36 2013
  MarkForUpload: True
  SourcePackage: coreutils
  UpgradeStatus: Upgraded to raring on 2013-04-26 (16 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/1179487/+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 1242373] Re: package coreutils 8.13-3ubuntu3.2 [modified: usr/bin/dircolors] failed to install/upgrade: ErrorMessage: Link zur Sicherung von »./usr/bin/csplit« vor Installation d

[A. Eibach]

-begin quote-
DuplicateSignature: package:coreutils:8.13-3ubuntu3.2 
[modified: usr/bin/dircolors]:ErrorMessage: Link zur Sicherung von 
»./usr/bin/csplit« vor Installation der neuen Version kann nicht angelegt 
werden: Die Operation ist nicht erlaubt
-end quote-

First of all, let's translate this German text to English: (only a
minority will speak German here)

It says that the (sym)link to backup ./usr/bin/csplit cannot be created,
permission denied.

The bug seems that there is a dot before the /usr, which denotes
search /usr/bin/csplit from current directory.

A dirty workaround might be to work directly from / (root) directory,
because then even ./usr/bin/csplit will refer to the physical
/usr/bin/csplit directory.

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

Title:
  package coreutils 8.13-3ubuntu3.2 [modified: usr/bin/dircolors] failed
  to install/upgrade: ErrorMessage: Link zur Sicherung von
  »./usr/bin/csplit« vor Installation der neuen Version kann nicht
  angelegt werden: Die Operation ist nicht erlaubt

Status in “coreutils” package in Ubuntu:
  New

Bug description:
  can't install or remove coreutils

  ProblemType: Package
  DistroRelease: Ubuntu 13.04
  Package: coreutils 8.13-3ubuntu3.2 [modified: usr/bin/dircolors]
  ProcVersionSignature: Ubuntu 3.5.0-41.64-generic 3.5.7.21
  Uname: Linux 3.5.0-41-generic x86_64
  NonfreeKernelModules: fglrx
  ApportVersion: 2.6.1-0ubuntu12
  Architecture: amd64
  Date: Sun Oct 20 17:03:51 2013
  DuplicateSignature: package:coreutils:8.13-3ubuntu3.2 [modified: 
usr/bin/dircolors]:ErrorMessage: Link zur Sicherung von »./usr/bin/csplit« vor 
Installation der neuen Version kann nicht angelegt werden: Die Operation ist 
nicht erlaubt
  ErrorMessage: ErrorMessage: Link zur Sicherung von »./usr/bin/csplit« vor 
Installation der neuen Version kann nicht angelegt werden: Die Operation ist 
nicht erlaubt
  InstallationDate: Installed on 2012-12-17 (307 days ago)
  InstallationMedia: Ubuntu 12.04.1 LTS Precise Pangolin - Release amd64 
(20120823.1)
  MarkForUpload: True
  SourcePackage: coreutils
  Title: package coreutils 8.13-3ubuntu3.2 [modified: usr/bin/dircolors] failed 
to install/upgrade: ErrorMessage: Link zur Sicherung von »./usr/bin/csplit« vor 
Installation der neuen Version kann nicht angelegt werden: Die Operation ist 
nicht erlaubt
  UpgradeStatus: Upgraded to raring on 2013-10-20 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/1242373/+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 1004319] Re: du -s show a wrong directory size

[A. Eibach]

21474836480 = overflow.

This is 500,000,000 in hexadecimal. (500 million)

BTW, your output is extremely specific on your settings in date and such. It 
depends on whether I want to display the month or not.
There is a -ls option in find; no need to pipe this through xargs.

So try

$ find . -type f -ls | awk '{print $7}'

This should give a much smaller footprint on your CPU load.
Maybe this fixes the bug you reported as well,

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

Title:
  du -s show a wrong directory size

Status in “coreutils” package in Ubuntu:
  New

Bug description:
  root@machine1:/data/directory# du -s *
  7116400   backup_dir1
  root@machine1:/data/directory# find -type f|xargs ls -al|cut -b 23-34
   19327352832
   424
  1983
30
   21474836480
   421
  2211
30
   21474836480
   422
  2110
30
30
8589934592
   423
  2001
  root@machine1:/data/directory#

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: coreutils 8.13-3ubuntu3
  ProcVersionSignature: Ubuntu 3.2.0-24.38-generic 3.2.16
  Uname: Linux 3.2.0-24-generic x86_64
  ApportVersion: 2.0.1-0ubuntu7
  Architecture: amd64
  Date: Fri May 25 07:19:41 2012
  InstallationMedia: Ubuntu-Server 12.04 LTS Precise Pangolin - Release amd64 
(20120424.1)
  ProcEnviron:
   SHELL=/bin/bash
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   LANGUAGE=en_US:en
  SourcePackage: coreutils
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/1004319/+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 1384416] Re: coreutils 'info command' broken

[A. Eibach]

Your bypass did not work at all, but thanks to the debbug entry you
linked, I got two working variants now:

(fully compatible, anywhere)

$ info '(coreutils) cat invocation'

(note: might not work everywhere)

$ info Coreutils 'cat invocation'

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

Title:
  coreutils 'info command' broken

Status in The Gnu Core Utilities:
  Unknown
Status in “coreutils” package in Ubuntu:
  Triaged

Bug description:
  Try the following on Ubuntu (or one of its flavors) and tell me what
  you see:

  $ info coreutils 'cat invocation'

  Should give you the *detailed* cat manual. However,  you will in fact
  land on 2.14 'coreutils' Multi-call binary in the documentation. Now
  idea yet how to fix this.

  Great job. Seems the bug they reported on Debian mailing list on 9/11
  (2014)

  https://www.mail-archive.com/debian-bugs-
  d...@lists.debian.org/msg1256146.html

  ... has now made its way into the Ubuntu version of coreutils as well.

  By the way,  isn't that a great comment again??

  though downstream 8.23 could be tweaked to avoid this issue.

  Cool. They've broken something that worked perfectly _for years_ and
  all the user gets is yeah, 8.23 'could be tweaked'. If only he had
  said _how_ to tweak it!! But apparently the commenter was way too lazy
  to write one more line.

To manage notifications about this bug go to:
https://bugs.launchpad.net/coreutils/+bug/1384416/+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 1384416] Re: coreutils 'info command' broken

[A. Eibach]

OK, this one-liner has to do the trick for me, until this is fixed
downstream:

#!/bin/bash
[[ $1 ==  ]] || info Coreutils $1 invocation

Wish this could be made an alias, but this is impossible since the
variable is _inside_ instead of at EOL

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

Title:
  coreutils 'info command' broken

Status in The Gnu Core Utilities:
  Unknown
Status in “coreutils” package in Ubuntu:
  Triaged

Bug description:
  Try the following on Ubuntu (or one of its flavors) and tell me what
  you see:

  $ info coreutils 'cat invocation'

  Should give you the *detailed* cat manual. However,  you will in fact
  land on 2.14 'coreutils' Multi-call binary in the documentation. Now
  idea yet how to fix this.

  Great job. Seems the bug they reported on Debian mailing list on 9/11
  (2014)

  https://www.mail-archive.com/debian-bugs-
  d...@lists.debian.org/msg1256146.html

  ... has now made its way into the Ubuntu version of coreutils as well.

  By the way,  isn't that a great comment again??

  though downstream 8.23 could be tweaked to avoid this issue.

  Cool. They've broken something that worked perfectly _for years_ and
  all the user gets is yeah, 8.23 'could be tweaked'. If only he had
  said _how_ to tweak it!! But apparently the commenter was way too lazy
  to write one more line.

To manage notifications about this bug go to:
https://bugs.launchpad.net/coreutils/+bug/1384416/+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 16492] Re: Mouse pointer should disappear when keyboard is in use and mouse isn't

[A. Eibach]

No 'unclutter' here on Lubuntu Utopic (beta; default). Had to install it
manually. Considering the age of this bug, and that even Mr. Ubuntu
himself has replied here, this should have been included in the default
distro long ago??

Anyways, this is not why I chose to comment here as well.

A good idea would maybe also be a CLIENT-SERVER solution. (or client-
daemon if you insist)

Compare: With only basic Python knowledge, you can write a scriptlet that might 
catch messages sent via dbus using something like notify-send.
This might be a way out for this mouse pointer hide/show issue as well.
 The daemon/server would be used as an observer to keep on guard for idle 
keyboard and whatnot, and if so, send an internal message to the various 
clients (e. g. text-processing apps) that can hide the cursor.

Downer/Disadvantage:

EACH of these applications will have to be made message-aware first
before the observer can send its demand to them.

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

Title:
  Mouse pointer should disappear when keyboard is in use and mouse isn't

Status in GTK+ GUI Toolkit:
  New
Status in One Hundred Papercuts:
  Triaged
Status in “gtk+2.0” package in Ubuntu:
  Triaged

Bug description:
  Steps to reproduce:
  1.  Click near the top left of a text field to focus it.
  2.  Start typing.
  Or:
  1.  Click in a browser window to focus the page.
  2.  Read the page, scrolling with the arrow keys.
  Or:
  1.  Click in an e-mail message window to focus the message.
  2.  Read the message, scrolling with the arrow keys.

  What happens:
  *   The mouse pointer gets in the way of what you're typing/reading.

  What should happen:
  *   Whenever you press a non-modifier key on the keyboard, if the pointing
  device has been neither moved nor clicked in the past ~0.25 seconds, the 
pointer
  should disappear until the pointing device is next moved or clicked.

  But won't this make people lose the pointer?
  *   No. For human eyes, such a small object is much easier to find by movement
  than by searching the entire screen. As soon as they grab the mouse again, the
  pointer will appear, and they'll see where it is.

  This is nuts!
  *   It's worked on the Mac for over two decades. Most people haven't noticed.
  They just get slightly irritated on *other* platforms when the pointer gets in
  the way.

  (Apologies if this is filed under the wrong product.)

  http://www.quinn.echidna.id.au/Quinn/WWW/HISubtleties/PointerObscuring.html:
  http://www.quinn.echidna.id.au/Quinn/WWW/HISubtleties/PointerObscuring.html

To manage notifications about this bug go to:
https://bugs.launchpad.net/gtk/+bug/16492/+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 1010095] Re: Droid Sans Mono is not exactly monospace

[A. Eibach]

There is *definitely only* the Regular style of this font. I can say
for sure for I've just used this font for a small part of my conky text
output and it would not respond on either the italic style or on  the
bold one.

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

Title:
  Droid Sans Mono is not exactly monospace

Status in “fonts-android” package in Ubuntu:
  Confirmed

Bug description:
  The Droid Sans Mono font has different character sizes in normal and bold 
variants, including the italic combinations.
  This affects numerous programs that use the Droid Mono font, or those using 
Monospace family, since Monospace is aliased to Driod Sans Mono by default.

  I am attaching a screenshot.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: fonts-droid 20101110+git-2
  ProcVersionSignature: Ubuntu 3.2.0-24.39-generic 3.2.16
  Uname: Linux 3.2.0-24-generic x86_64
  ApportVersion: 2.0.1-0ubuntu8
  Architecture: amd64
  Date: Thu Jun  7 19:33:16 2012
  Dependencies:
   
  InstallationMedia: Xubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012)
  PackageArchitecture: all
  SourcePackage: fonts-droid
  UpgradeStatus: Upgraded to precise on 2012-06-05 (2 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fonts-android/+bug/1010095/+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 1252121] Re: missing PrepareForSleep signal after resuming, causing networking to stay disabled

[A. Eibach]

Good question!

I'm on Utopic development version (i. e. 14.10)  and there is no way to
get network back on automatically after hibernate! (suspend often caused
my machine to hard-lock so I can only use hibernate in my case)

It's a shame everyone ignores us, saying this is of minor importance.
BTW, it worked fine in Saucy, so this is evidence enough that someone
dabbled with the code and broke it AGAIN.

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

Title:
  missing PrepareForSleep signal after resuming, causing networking to
  stay disabled

Status in NetworkManager:
  New
Status in wicd:
  New
Status in “systemd-shim” package in Ubuntu:
  Confirmed
Status in “systemd-shim” source package in Saucy:
  Confirmed
Status in “systemd-shim” source package in Trusty:
  Confirmed

Bug description:
  As per request from bug #1184262, this is a new report, along with
  dbus (to be attached)

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: systemd-services 204-0ubuntu19
  Uname: Linux 3.12.0-custom x86_64
  ApportVersion: 2.12.5-0ubuntu2.1
  Architecture: amd64
  Date: Sun Nov 17 20:24:41 2013
  MarkForUpload: True
  SourcePackage: systemd
  UpgradeStatus: Upgraded to saucy on 2013-10-17 (31 days ago)

  SRU INFORMATION:
  FIX: https://github.com/desrt/systemd-shim/commit/9e1ebe3ab (in trusty 
already)

  Regression potential: Low. Flushing the session bus was introduced in
  version 4 and is obviously bogus as in a system D-BUS service there is
  no session bus. This causes lots of confusing error messages and
  unnecessary overhead like trying to start dbus-launch. Flushing the
  system bus is low-risk, in most cases it's a no-op and it would
  otherwise prevent losing signals after waking up. No known
  regressions.

  TEST CASE: Run several suspend/resume cycles with the lid, session
  indicator menu, and verify that the network comes back up. It is known
  that this fix is necessary but not sufficient, so it is not expected
  to fix all cases. But it should not make things worse, so if network
  now does not come up any more on a machine where it previously worked
  this would count as failure/regression.

To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager/+bug/1252121/+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 1252121] Re: missing PrepareForSleep signal after resuming, causing networking to stay disabled

[A. Eibach]

Yes, hibernation itself DOES work in Utopic (Lubuntu flavor). However,
as I notice that I'm even able to hibernate my machine via GUI menu, I
might have done some change that enables this (because I do remember
there was something on launchpad about this being disabled in the
vanilla installation)

But anyways, 'sudo pm-hibernate' works fine regardless of what policy
has been set.

However, I've enabled 'S3' mode in my BIOS, though I have no idea
whether 'Buntu will care about that at all. :)

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

Title:
  missing PrepareForSleep signal after resuming, causing networking to
  stay disabled

Status in NetworkManager:
  New
Status in wicd:
  New
Status in “systemd-shim” package in Ubuntu:
  Confirmed
Status in “systemd-shim” source package in Saucy:
  Confirmed
Status in “systemd-shim” source package in Trusty:
  Confirmed

Bug description:
  As per request from bug #1184262, this is a new report, along with
  dbus (to be attached)

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: systemd-services 204-0ubuntu19
  Uname: Linux 3.12.0-custom x86_64
  ApportVersion: 2.12.5-0ubuntu2.1
  Architecture: amd64
  Date: Sun Nov 17 20:24:41 2013
  MarkForUpload: True
  SourcePackage: systemd
  UpgradeStatus: Upgraded to saucy on 2013-10-17 (31 days ago)

  SRU INFORMATION:
  FIX: https://github.com/desrt/systemd-shim/commit/9e1ebe3ab (in trusty 
already)

  Regression potential: Low. Flushing the session bus was introduced in
  version 4 and is obviously bogus as in a system D-BUS service there is
  no session bus. This causes lots of confusing error messages and
  unnecessary overhead like trying to start dbus-launch. Flushing the
  system bus is low-risk, in most cases it's a no-op and it would
  otherwise prevent losing signals after waking up. No known
  regressions.

  TEST CASE: Run several suspend/resume cycles with the lid, session
  indicator menu, and verify that the network comes back up. It is known
  that this fix is necessary but not sufficient, so it is not expected
  to fix all cases. But it should not make things worse, so if network
  now does not come up any more on a machine where it previously worked
  this would count as failure/regression.

To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager/+bug/1252121/+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 1351295] Re: Boot fails if /sbin/init (or init= arg) is an absolute symlink

[A. Eibach]

Thank you! 
Hmm...Latest kernel...that's another interesting thing...always got nothing 
but black screens in 3.16, hence I had to go back to the 3.13 series (patch 
levels 30 +) and --- no more problems.

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

Title:
  Boot fails if /sbin/init (or init= arg) is an absolute symlink

Status in “initramfs-tools” package in Ubuntu:
  Fix Released

Bug description:
  Booting current Utopic with init=/bin/systemd fails., or installing
  systemd-sysv fails. In both cases we are dealing with an absolute
  symlink /bin/systemd - /lib/systemd/systemd or /sbin/init -
  /lib/systemd/systemd. I see:

  /init: line 307: readlink: not found
  Target filesystem doesn't have requested /bin/systemd
  and then a kernel panic.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1351295/+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 1351295] Re: Boot fails if /sbin/init (or init= arg) is an absolute symlink

[A. Eibach]

$ sudo update-initramfs -k 3.13.0-32-generic -u

voila !! thanks again for leading me in the right direction.
I've decided to post this too here; maybe it will help some more users new to 
Ubuntu.

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

Title:
  Boot fails if /sbin/init (or init= arg) is an absolute symlink

Status in “initramfs-tools” package in Ubuntu:
  Fix Released

Bug description:
  Booting current Utopic with init=/bin/systemd fails., or installing
  systemd-sysv fails. In both cases we are dealing with an absolute
  symlink /bin/systemd - /lib/systemd/systemd or /sbin/init -
  /lib/systemd/systemd. I see:

  /init: line 307: readlink: not found
  Target filesystem doesn't have requested /bin/systemd
  and then a kernel panic.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1351295/+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 1342233] [NEW] Window resizing happens at snail's pace in gEdit 3.12

[A. Eibach]

Public bug reported:

I'm on Lubuntu Trusty 14.04.

This has never happened before 3.12.
Although I can confirm the CPU peaks when changing focus with different windows 
(see https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1299759), my issue is 
different from that described in 1299759.

Mine is about _resizing_ the editor window. This problem hasn't occurred
until gedit got that (IMHO totally pointless) overhaul with the new
layout and everything non-trivial hidden behind that cog wheel...

Whenever I try to expand or shrink the window, it works but listen how!
It will behave sluggishly, like a slideshow, rhythmically changing
window size in steps of fractions ofan i-i-i-i-i-i-nch. (feels like a
demanding application from the 2000s that is run on an ancient 286)

Well, I can't be the only one who has experienced this?

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


** Tags: gedit resize sluggish window

** Package changed: ibus (Ubuntu) = gedit (Ubuntu)

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

Title:
  Window resizing happens at snail's pace in gEdit 3.12

Status in “gedit” package in Ubuntu:
  New

Bug description:
  I'm on Lubuntu Trusty 14.04.

  This has never happened before 3.12.
  Although I can confirm the CPU peaks when changing focus with different 
windows (see https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1299759), my 
issue is different from that described in 1299759.

  Mine is about _resizing_ the editor window. This problem hasn't
  occurred until gedit got that (IMHO totally pointless) overhaul with
  the new layout and everything non-trivial hidden behind that cog
  wheel...

  Whenever I try to expand or shrink the window, it works but listen
  how! It will behave sluggishly, like a slideshow, rhythmically
  changing window size in steps of fractions ofan i-i-i-i-i-i-nch.
  (feels like a demanding application from the 2000s that is run on an
  ancient 286)

  Well, I can't be the only one who has experienced this?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1342233/+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