[Bug 116785] linux-libc-dev update dependency problem

2007-05-25 Thread Tim Parker
Public bug reported:

Binary package hint: update-manager

On 6.10 i386. linux-libc-dev is permanently being reported an available
update from 2.6.17.1-11.37 to 2.6.20-15.27, although the system is using
kernels no later than 2.6.17-11 (all kernels from standard update
process - no 'extra' kernels installed by hand). It seems that the libc
kernel header package is not checking the installed kernel versions.
This may in part be related to bug #37937, in which the fact that the
linux-libc-dev is treated as a separate package causes problems. The
rejection of that bug seemed to miss the point, viz :-

On mar, 2006-04-04 at 01:24 +, Matt Zimmerman wrote:

> The headers are not installed by default; if you want them, install the 
> corresponding linux-headers- package for the linux- package you are 
> using, and it will track the same versions.
>
> ** Changed in: Ubuntu
> Status: Unconfirmed => Rejected

The headers are NOT tracking the versions of the kernel (if i'm reading
Matt replies correctly). It makes no sense, and is a potential build
issue, to update the headers regardless of the kernel version... also
irritating that you cannot 'turn off' the update warning from the
update-manager without uninstalling the package.. but this is linked
with the dependency issue between the kernel and the header package
which seems to have been ignored. Shurly shome mysteak.

** Affects: update-manager (Ubuntu)
 Importance: Undecided
 Status: Unconfirmed

-- 
linux-libc-dev update dependency problem
https://bugs.launchpad.net/bugs/116785
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.

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


[Bug 1060907] Re: NetworkManager stores wifi passwords in plain text

2013-02-05 Thread Tim Parker
I am also having issues with this. In my use case, with
NetworkManager-1.0.9.6.4-3.fc17 (64-bit), I have a VPN connection for a
non-root user which is set to NOT connect automatically and NOT allowed
on a system basis. If I do not enter a passphrase I cannot save the VPN
configuration. If I do add a passphrase it is stored under /etc/ with
only root permissions rw permissions as  'protection'. As far as I
remember,I was not offered the option to store to keyring when I set it
up - nor would I want it to.

There seems to be an implicit requirement in the design, or belief in
the authors, that the password should be stored - I have no idea why
this should be. There is further the belief that storing it as plain-
text is as safe as it needs to be - perhaps if you're storing it in /etc
or in the users keyring that's true, but there is life beyond them..
which is just as well given their limitations.

It used to be possible to create configurations without
passwords/passphrases, which lead to a prompt for credentials when
making a connection using such a configuration - this seems eminently
sensible, especially if the passphrase can be protected in memory or
otherwise safe-guarded (as done elsewhere). That this ability it no
longer there, it would seem to indicate that there was a conscious
decision to remove it - if so, can I ask what the thinking was behind it
?... if not, why was it then removed ?

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

Title:
  NetworkManager stores wifi passwords in plain text

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

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


[Bug 1823698] [NEW] dont know

2019-04-08 Thread tim parker
Public bug reported:

could be via email ?

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 4.15.0-47.50-generic 4.15.18
Uname: Linux 4.15.0-47-generic i686
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.9-0ubuntu7.6
Architecture: i386
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
Date: Mon Apr  8 12:14:53 2019
DistUpgraded: 2018-08-28 23:59:06,593 DEBUG icon theme changed, re-reading
DistroCodename: bionic
DistroVariant: ubuntu
GraphicsCard:
 Intel Corporation 4 Series Chipset Integrated Graphics Controller [8086:2e32] 
(rev 03) (prog-if 00 [VGA controller])
   Subsystem: ASUSTeK Computer Inc. 4 Series Chipset Integrated Graphics 
Controller [1043:836d]
InstallationDate: Installed on 2012-03-13 (2582 days ago)
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1)
MachineType: System manufacturer System Product Name
ProcEnviron:
 LANGUAGE=en_GB:en
 PATH=(custom, no user)
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-47-generic 
root=UUID=b5d5d6d6-6240-4254-9586-c18faee66775 ro splash quiet
SourcePackage: xorg
UpgradeStatus: Upgraded to bionic on 2018-08-28 (222 days ago)
dmi.bios.date: 11/22/2010
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0405
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: P5G41T-M LX2/GB
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev X.0x
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0405:bd11/22/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5G41T-MLX2/GB:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.family: To Be Filled By O.E.M.
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer
version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
version.libdrm2: libdrm2 2.4.95-1~18.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2
version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
xserver.bootTime: Tue Aug 28 20:10:43 2018
xserver.configfile: default
xserver.devices:
 inputPower Button KEYBOARD, id 6
 inputPower Button KEYBOARD, id 7
 inputMicrosoft NaturalĀ® Ergonomic Keyboard 4000 KEYBOARD, id 8
 inputMicrosoft NaturalĀ® Ergonomic Keyboard 4000 KEYBOARD, id 9
 inputLogitech USB-PS/2 Optical Mouse MOUSE, id 10
xserver.errors:
 /dev/dri/card0: failed to set DRM interface version 1.4: Permission denied
 /dev/dri/card0: failed to set DRM interface version 1.4: Permission denied
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id1432 
 vendor SAM
xserver.version: 2:1.18.4-0ubuntu0.8

** Affects: xorg (Ubuntu)
 Importance: Low
 Status: Incomplete


** Tags: apport-bug bionic i386 ubuntu

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

Title:
  dont know

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

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

[Bug 1823698] Re: dont know

2019-04-08 Thread tim parker
bug could have been received by email on yahoo on another linked
computer

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

Title:
  dont know

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

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

[Bug 116785] Re: linux-libc-dev update dependency problem

2008-12-08 Thread Tim Parker
> We are closing this bug report

Ok - no problem

> because it lacks the information we need to investigate the problem,

No it doesn't - the information is all there and in the cross-referenced
bug report AFAICS and no further request for information regarding this
was made here.

> as described in the previous comments.

No it wasn't - and what this "missing" information may or may not be has
not been explained (please don't say you couldn't try and reproduce
without knowing whether later versions also, as that is not relevant in
this case). However, seeing as this seemed to be a distribution specific
bug for which the distribution is no longer actively supported - and
does not seem to manifest in a similar form in later distributions -
then i'm ok with it closing... just as long as the reason for closing is
given correctly.

Sorry about the tone - I honestly do very much appreciate all the work
put in but as a software devvie myself, people trying to close bugs with
completely bogus reasons really gets on my nerves.

Best regards
Tim

-- 
linux-libc-dev update dependency problem
https://bugs.launchpad.net/bugs/116785
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

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