*** This bug is a duplicate of bug 1050404 ***
https://bugs.launchpad.net/bugs/1050404
Public bug reported:
The .postinst scripts of both openjdk-6-jre-lib and openjdk-7-jre-lib
delete files belonging to tzdata-java.
This leads to unexpected errors in Java applications. One such is
Eclipse.
The message RANDR extension is not present originates from the package
gnome-desktop3
libgnome-desktop/gnome-rr.c::gnome_rr_screen_initable_init()
if (XRRQueryExtension (dpy, event_base, ignore))
{
...
}
else
{
g_set_error (error, GNOME_RR_ERROR, GNOME_RR_ERROR_NO_RANDR_EXTENSION,
libgnome-desktop/gnome-rr.c::gnome_rr_screen_new() says:
* Returns: a unique #GnomeRRScreen instance, specific to the @screen, or NULL
* if this could not be created, for instance if the driver does not support
* Xrandr 1.2. Each #GdkScreen thus has a single instance of #GnomeRRScreen.
** Changed in: gnome-control-center (Ubuntu)
Status: New = In Progress
** Changed in: gnome-control-center (Ubuntu)
Assignee: (unassigned) = TJ (tj)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-control-center
I've uploaded the potential fix to my PPA for Precise. Please test and
report back.
https://launchpad.net/~tj/+archive/bugfixes
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-control-center in Ubuntu.
https://bugs.launchpad.net
Mathieu Trudel-Lapierre (mathieu-tl) wrote on 2012-04-24: #4
Carl:
There's no bug there: we're on purpose defaulting to system-wide connections
since Oneiric. This means one will need administrator rights to be able to
create system-wide connection profiles, which explains the popup.
On
This also affects Evince and Gedit.
I discovered the bug whilst trying to print using Evince to a custom page size
(A4 but with a 40mm left border) which I called Sunshine Border.
Both preview and printing either fail or sometimes print using default A4
margins. I was trying to track down the
Public bug reported:
Affects 12.04 Precise. This appears identical to bug #348202 Impossible
to print to custom page size in Evince.
Evince doesn't respect a custom paper size with a reduced margin ( for
printing on pre-printed paper).
Using a HP Deskjet 995C A4 ink-jet printer with duplexer
In modules/printbackends/cups/gtkprintbackendcups.c:
static void
add_cups_options (const gchar *key,
const gchar *value,
gpointer user_data)
{
...
/* Add Custom. prefix to custom values. */
if (custom_value)
{
new_value = g_strdup_printf
Here's confirmation obtained using gdb with evince:
Breakpoint 5, add_cups_options (key=0x7faa10a346b0 cups-PageSize,
value=0x7faa11235a20 Custom.595.28x841.89,
user_data=0x7faa11041090) at
/build/buildd/gtk+3.0-3.4.2/./modules/printbackends/cups/gtkprintbackendcups.c:521
521 in
** Changed in: gtk+3.0 (Ubuntu Precise)
Status: Confirmed = In Progress
** Changed in: gtk+3.0 (Ubuntu Precise)
Assignee: (unassigned) = TJ (intuitivenipple)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gimp in Ubuntu
- gtk+3.0 - do not duplicate CUPS Custom.
https://bugs.launchpad.net/ubuntu/precise/+source/gtk+3.0/+bug/998156/+attachment/3239331/+files/gtk%2B3.0_3.4.2-0ubuntu0.5%7Eppa%7Etj.debdiff
** Changed in: gtk+3.0 (Ubuntu Precise)
Assignee: TJ (intuitivenipple) = (unassigned)
--
You received
** Changed in: apt-cacher-ng (Ubuntu)
Status: New = Confirmed
** Changed in: apt-cacher-ng (Ubuntu)
Importance: Undecided = High
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to software-center in Ubuntu.
** Also affects: apt (Ubuntu)
Importance: Undecided
Status: New
** Changed in: apt (Ubuntu)
Importance: Undecided = Critical
** Changed in: apt (Ubuntu)
Status: New = In Progress
** Changed in: apt (Ubuntu)
Assignee: (unassigned) = TJ (intuitivenipple)
--
You received
://bugs.launchpad.net/ubuntu/+source/apt/+bug/1008289/+attachment/3245093/+files/apt_0.8.16%7Eexp12ubuntu10.3%7Etj.debdiff
** Changed in: apt (Ubuntu)
Status: In Progress = Triaged
** Changed in: apt (Ubuntu)
Assignee: TJ (intuitivenipple) = (unassigned)
--
You received this bug
Sary. If Ubuntu is not supporting the standard features of the PC then
it is a bug. We know that the Linux kernel is passing the key-codes so
now its my job to figure out what the fix is and which package that
applies to.
If I need to change the package this bug is assigned to I will do that.
For
Public bug reported:
Ubuntu 12.04 Precise, /var/log/cups/error_log shows:
E [10/Dec/2012:11:28:56 +] Unknown directive SystemGroup on line 16
of /etc/cups/cupsd.conf.
The file contains:
# Administrator user group...
SystemGroup lpadmin
I can find no reference to SystemGroup in man 5
Looking at the patches for CVE-2012-5519 committed 3rd December 2012 it
seems that the SystemGroup variable was removed from cupsd.conf
configuration but existing entries in cupds.conf were not migrated in
the post-inst scripts.
cups (1.5.3-0ubuntu5.1) precise-security; urgency=low
* SECURITY
wrapped
Dec 10 13:07:30 XPSm1530 cupsd[18772]: Error attempting to open
[/home/tj/.ecryptfs/wrapped-passphrase] for reading
Dec 10 13:07:30 XPSm1530 cupsd[18772]: Error attempting to unwrap passphrase
from file [/home/tj/.ecryptfs/wrapped-passphrase]; rc = [-5]
Dec 10 13:07:30 XPSm1530 cupsd[18772
adsmith's script doesn't work on Precise so I've reworked it and removed
the dependency on naming interfaces. My script will act whenever any
eth* interface comes or goes. It also logs to
/var/log/NetworkManager.log.
Install to /etc/NetworkManager/prefer_wired_over_radio.sh
Once copied to that
Removed the upstream bug-watch since that only fixes in trunk (currently
0.13.3). This report is for versions =0.12.8 in 10.04 Long Term Support
affected by a change in the MusicBrainz remote API and consequent
breaking of the libmusicbrainz lookups.
** Changed in: rhythmbox
Importance: High =
Hey Dan.
When I get a few minutes I'm going to investigate the most appropriate
fix for this, which for an LTS must meet the Stable Release Update (SRU)
requirements of being minimally invasive and demonstrably not
introducing potential regressions in other areas.
--
You received this bug
-daemon (Ubuntu)
Assignee: (unassigned) = TJ (intuitivenipple)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-settings-daemon in Ubuntu.
https://bugs.launchpad.net/bugs/995185
Title:
Multimedia keys are disabled
Status
From the provided dmesg log:
TOSHIBA SATELLITE M100/HAQAA
input: AT Translated Set 2 keyboard as
/devices/platform/i8042/serio0/input/input3
input: Video Bus as
/devices/LNXSYSTM:00/device:00/PNP0A08:00/device:01/LNXVIDEO:00/input/input4
input: PS/2 Mouse as
Could you do a test and document the results?
Boot the laptop from a cold start and then press and release each of the
media keys in turn. Write down the keys and the order you press them in.
Then attach the /var/log/dmesg file along with the ordered list of keys
you pressed.
This will allow me
I forgot to ask. Please also report the model number and any other codes
printed on the label on the base of the M100 so we can identify the
exact variation.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-settings-daemon in
Hi Sary, thanks for the prompt response.
The first thing I notice is the kernel version you just used is
different to the original dmesg:
Original:
[0.00] Linux version 3.2.0-23-generic (buildd@crested) (gcc version
4.6.3 (Ubuntu/Linaro 4.6.3-1ubuntu4) ) #36-Ubuntu SMP Tue Apr 10
** Changed in: simple-scan (Ubuntu)
Assignee: TJ (tj) = (unassigned)
** Changed in: simple-scan
Assignee: TJ (tj) = (unassigned)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to simple-scan in Ubuntu.
https://bugs.launchpad.net
Unfortunately this driver has suffered bit-rot upstream since the chip-
set is ancient and not widely used, and support for it in the 12.04 and
14.04 releases is poor to non-existant.
Marking as Won't Fix since we haven't found the expertise to fix it in
7 years.
** Changed in: xorg (Ubuntu)
I found this affecting 14.04 Trusty.
$ pactl set-card-profile bluez_card.30_17_C8_8B_DF_B1 a2dp
Failure: Input/Output error
so I thought I'd capture some debug logging to /var/log/syslog from
bluetoothd (system daemon) by adding -d (debug logging) to the Upstart
service file
-xfree86-nonfree, xfs
** Affects: flashplugin-nonfree (Ubuntu)
Importance: Undecided
Assignee: TJ (tj)
Status: Triaged
** Affects: wdm (Ubuntu)
Importance: Undecided
Assignee: TJ (tj)
Status: Triaged
** Affects: xfonts-terminus (Ubuntu)
Importance: Undecided
Added the source package hplip since the issue is likely in binary
package printer-driver-hpcups.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/1069507
Title:
(REGRESSION) printable
Affects Ubuntu 13.04 Raring amd64, with HP Deskjet 995C ink-jet using HP
drivers 3.13.3 hpcups. Using the hpijs driver the top margin is correct.
That seems to confirm the issue is in the CUPS driver.
** Also affects: hplip (Ubuntu)
Importance: Undecided
Status: New
** Changed in:
I tried using the driver HP DeskJet 995C - CUPS+Gutenprint v5.2.9 -
the third option for this printer - and the same top-margin crop occurs,
so the common issue is CUPS.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to cups in Ubuntu.
Using the debugging instructions from
https://wiki.ubuntu.com/DebuggingPrintingProblems#Capturing_print_job_data
I captured the job whilst using the hpcups driver. The spooled file was
PDF format. Evince (the PDF viewer) showed that the data in the spool
file has an identical top-margin to the
The following event shows up in syslog:
signond[6900]: ../../../../src/signond/signondaemon.cpp 360 init Failed
to SUID root. Secure storage will not be available.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to empathy in Ubuntu.
Public bug reported:
This report appears in syslog each time Empathy tries and fails to
connect to Google Talk using the google-talkplugin interface.
It is not clear whether this SUID report is related to the Empathy
failure.
See bug #1168582 Google talk Requires Authorization after
The empathy debug log shows (empathy-debugger):
gabbleconnection-DEBUG: 20/05/13 10:47:25.225645: gabble_connection_constructed
(connection.c:547): defaulted resource to fa965dbf
wocky/-DEBUG: 20/05/13 10:47:25.343826: wocky_xmpp_writer_stream_open:
wocky-xmpp-writer.c:302: Writing stream
I discovered that deleting the Jabber GTalk account and replacing it
with a full Google account solves the problem, so it looks like a bad
interaction with the gabble --- signond -- google-talkplugin
combination.
--
You received this bug notification because you are a member of Desktop
Packages,
** Description changed:
+ signond[7451]: ../../../../src/signond/signondaemon.cpp 360 init Failed
+ to SUID root. Secure storage will not be available.
+
This report appears in syslog each time Empathy tries and fails to
connect to Google Talk using the google-talkplugin interface.
It
On 04/07/13 15:34, Raymond wrote:
use hda-jack-sense-test to find out which nodes corresponding to which
headphone jacks
The laptop - Dell XPS m1530 - has two front headphone sockets and
external microphone socket and internal stereo speakers and microphone.
Unfortunately David
After applying the following patch the tool produced some output but I'm
not sure if it as expected.
$ sudo /usr/bin/hda-jack-sense-test
Unable to find proc file '/proc/asound/card0/codec#0'
Pin 0x0a (Black HP Out): present = No
Pin 0x0e (Black Mic): present = No
Pin 0x0f (Black Line Out):
I checked hda-jack-sense-test and noticed it can take the command-line
option -d|--codec so I tried using that:
$ sudo /usr/bin/hda-jack-sense-test -d 2
Sigmatel specific Analog Loopback: 0x00 verb ignored for the moment
Traceback (most recent call last):
File /usr/bin/hda-jack-sense-test, line
I fixed up the problems with the old version of the hda_analyzer code:
$ cd /dev/shm/
$ sudo wget http://www.alsa-project.org/hda-analyzer.py
$ cd hda-analyzer/
$ sudo cp /usr/bin/hda-jack-sense-test .
$ sudo ./hda-jack-sense-test -d 2
Sigmatel specific Analog Loopback: 0x00 verb ignored for the
A test package built for Raring will be available in my bug-fixes PPA
shortly.
https://launchpad.net/~tj/+archive/bugfixes
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to simple-scan in Ubuntu.
https://bugs.launchpad.net/bugs/892915
** Also affects: simple-scan (Ubuntu)
Importance: Undecided
Status: New
** Changed in: simple-scan (Ubuntu)
Status: New = In Progress
** Changed in: simple-scan (Ubuntu)
Importance: Undecided = Low
** Changed in: simple-scan (Ubuntu)
Assignee: (unassigned) = TJ (tj
I'm seeing this on a fleet of laptops which all have Fast Ethernet,
802.11a/g/n and GSM HSPA interfaces.
If the WLAN is active and configured as the default route when the GSM
HSPA WWAN is activated the default route is changed to be the WWAN.
I wonder if NM could accept a user-specified (or
This prevents the installation of the ubuntu-usb tasksel.
** Changed in: usb-modeswitch (Ubuntu)
Importance: Undecided = High
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to usb-modeswitch in Ubuntu.
)
Status: New = Triaged
** Changed in: alsa-utils (Ubuntu)
Importance: Undecided = Critical
** Changed in: alsa-utils (Ubuntu)
Assignee: (unassigned) = TJ (tj)
** Changed in: alsa-utils (Ubuntu)
Status: Triaged = In Progress
--
You received this bug notification because you
I'm in the process of rustling up a patch for alsa-utils, but this
highlights that upstart really needs guard conditions for file-job ==
NULL before trying to dereference it.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alsa-utils in
Attaching a tar.gz archive that can be extracted to /etc/init/ which
replaces the faulty alsa-utils upstart conf files:
$ tar -tf lp1269731-upstart-alsa-utls.tar.gz
etc/
etc/init/
etc/init/alsa-state.conf
etc/init/alsa-restore.conf
etc/init/alsa-store.conf
To install, download the attachment and
** Changed in: alsa-utils (Ubuntu)
Status: In Progress = Triaged
** Changed in: alsa-utils (Ubuntu)
Assignee: TJ (tj) = (unassigned)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alsa-utils in Ubuntu.
https
Julien: It'd be better to open a brand new bug report with details of
the system exhibiting the problem. In the description give a reference
to this issue using bug #40125 and the bug-tracker will hyperlink it
to this page.
--
You received this bug notification because you are a member of
Public bug reported:
On 13.04 with two mobile broadband devices disabling Mobile Broadband
only disables the first device. The first device is an internal min-PCIe
device, the second an external USB 'dongle'.
Both devices use the same connection APN info so disabling a connection
is not a
Public bug reported:
1) Set locale to English (Denmark) and set Apply System-Wide so that
24-hour time is used
System Settings Language Support Regional Formats English (Denmark)
Apply System-Wide
2) logout and then log back in
3) set locations to be shown in clock applet
gsettings set
** Changed in: nvclock (Ubuntu)
Assignee: TJ (tj) = (unassigned)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nvidia-graphics-drivers-updates in
Ubuntu.
https://bugs.launchpad.net/bugs/1039916
Title:
Nvidia driver causing
Public bug reported:
With the Trusty version 3.10.2-0ubuntu1 Cheese will crash when taking a
snapshot *after* having recorded a video.
The camera is a laptop USB UVC built-in with a maximum resolution of
1600x1200. Cheese was set to a video resolution of 800x600 and photo
resolution of 1600x1200
** Also affects: nvidia-graphics-drivers-340 (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nvidia-graphics-drivers-331-updates in
Ubuntu.
https://bugs.launchpad.net/bugs/1247736
I've published a possibly fixed package for Trusty to my PPA at:
https://launchpad.net/~tj/+archive/ubuntu/nvidia
Please test and report back if that fixes the issue. If it does I can
attach the fixed branch to bug #1431753 where the other release fixes
are being tracked.
** Changed in: nvidia
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu)
Status: New = Triaged
** Changed in: linux (Ubuntu)
Importance: Undecided = High
** Changed in: linux (Ubuntu)
Milestone: None = ubuntu-14.04.3
--
You received this bug
** Description changed:
My Huawei E173 modem is not recognized as a modem anymore after
installing Ubuntu 15.04 and Mainline kernel 4.0 RC6. It worked out of
the box with Ubuntu 14.10.
I tried various guides (editing /etc/modules and
/lib/udev/rules.d/40-usb_modeswitch.rules) but
This may be caused by upstream changes to the Huawei device handling:
Version 2.2.0, 2014/05/29
Introduction of parameter HuaweiNewMode, wrapping the standard bulk
message for all newer Huawei devices; support for generic fall-back
config files, combined with OS switch (per vendor
** Information type changed from Private to Public
** Changed in: xorg-server (Ubuntu)
Status: Invalid = Incomplete
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1479009
$ apt-file search /usr/share/accounts/services/google-im.service
account-plugin-google: /usr/share/accounts/services/google-im.service
kde-config-telepathy-accounts: /usr/share/accounts/services/google-im.service
** Also affects: account-plugins (Ubuntu)
Importance: Undecided
Status:
I've been looking at this on Wily with a user suffering the bug, and it
looks at first glance to be a timing issue - namely, that NM doesn't
wait long enough after starting dnsmasq to query the name on the bus.
The code is Ubuntu specific, and introduced via
Public bug reported:
I have a Canon printer, Pixma 920, that I installed and was working
great. I used the driver/install script via the Asian Canon site (as
recommended by others.)
I'm not sure what changed but I can no longer print/scan with it from my
Ubuntu laptop (the app on my Android
This still affects Okular in 15.10 Wily.
Printing an 84 A5 page PDF duplex onto A4 every page has extended left
and bottom margins, cropped right and top edges, and also scales
(magnifies) the content.
Using the identical printer settings with Evince ( Document Viewer) the
document prints with
The report in /var/log/Xorg.0.log:
"_XSERVTransMakeAllCOTSServerListeners: server already running"
suggests the system (user: gdm, uid: 116) display manager X server on
VT7 owns/uses the socket in "/tmp/.X11-unix/" which prevents the user
(uid:1000) display manager on VT2 from using the same
** Tags added: apport-request-retrace
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1237904
Title:
Xorg crashed with SIGABRT in OsAbort()
Status in xorg-server package in
Public bug reported:
The explicit copyright text in each source file is Proprietary all
rights reserved, not open source.
The package copyright file /usr/share/doc/nvidia-340/copyright is less
than ideal and only purports to repeat extracts from an email exchange,
it is not a copyright license.
Also happening in 15.10 Wily, with lightdm 1.15.3-0ubuntu3
Repeated 3 times per second constantly for about 15 minutes and then
system froze - not sure if this was the cause of the freeze but it was
the only logged info immediately before the freeze.
Sep 1 19:23:43 hephaestion lightdm[951]:
Public bug reported:
Helping a user on IRC where ubuntu-drivers failed to detect
0a:00.0 3D controller [0302]: NVIDIA Corporation GM107M [GeForce GTX
850M] [10de:1391] (rev a2)
Looking at the source-code I noticed that
/usr/lib/python3/dist-
** Changed in: xorg-server (Ubuntu)
Status: Expired => Triaged
** Changed in: xorg-server (Ubuntu)
Importance: Low => Medium
** Also affects: plymouth (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Desktop
** Description changed:
- The mouse cursor is gone when Oneiric starts. The mouse itself is
+ The mouse cursor is gone when the GUI starts. The mouse itself is
responding, but the pointer is invisible. Very annoying. I do have a
workaround. One must simply restart the lightdm interface with
Hit this again today with lightdm spamming the logs.
I'd left the PC for about 45 minutes; came back to a backlit but black
display and no response to input.
I connected via SSH and found lightdm had TWO instances of X running,
one on tty7 and the other on tty8
I could find no clues in any of
Hit this again today; Was working fine until about 05:40 when I locked
the session and left. Returned around 12:20, touched the mousepad to
wake the monitors, backlights come on but no display. SSH from another
host shows a 2nd X server attempts to start on :1 at the time I
returned, fails, tries
Public bug reported:
[+0.00s] DEBUG: Logging to /var/log/lightdm/lightdm.log
[+0.00s] DEBUG: Starting Light Display Manager 1.16.0, UID=0 PID=1118
[+0.00s] DEBUG: Loading configuration dirs from
/usr/share/lightdm/lightdm.conf.d
...
[+0.00s] DEBUG: Loading configuration from
** Changed in: network-manager (Ubuntu Trusty)
Status: Fix Released => In Progress
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1441095
Title:
novatel: improve
** Changed in: xserver-xorg-input-evdev (Ubuntu)
Assignee: Jakob Povsic (jakob-povsic) => (unassigned)
** Changed in: xserver-xorg-input-evdev (Ubuntu)
Status: Fix Released => Incomplete
--
You received this bug notification because you are a member of Desktop
Packages, which is
** Changed in: network-manager (Ubuntu)
Importance: Undecided => High
** Also affects: isc-dhcp (Ubuntu)
Importance: Undecided
Status: New
** Changed in: isc-dhcp (Ubuntu)
Importance: Undecided => High
** Changed in: isc-dhcp (Ubuntu)
Status: New => Triaged
--
You
Further debugging indicates that when the IPv6 lease file contains an
expired lease as its last entry dhclient 'depreferences' it (gives it
up) but doesn't go on to attempt to gain a replacement lease because NM
cancels (kills) the dhclient process as a result of the 'expires'
message.
NM starts
The debug log contains:
Mar 31 01:34:59 hephaestion NetworkManager[9095]: [1459384499.752259]
[dhcp-manager/nm-dhcp-client.c:222] reason_to_state(): (wlp3s0): unmapped DHCP
state 'DEPREF6'
Mar 31 01:34:59 hephaestion NetworkManager[9095]: [1459384499.758516]
Here's some notes from my digging into the code paths being followed.
Using the messages logged by NM to syslog I've been able to reconstruct
the call heirarchy. In summary, when the state transitions from "expire"
to "done":
nm_dhcp_client_set_state () fires a NM_DHCP_STATE_EXPIRE signal
Attaching a Network Manager TRACE log_level from syslog generated using:
/etc/NetworkManager/conf.d/logging.conf:
---
[logging]
level=TRACE
---
I've removed any extraneous messages from processes other than NM and
dhclient. I've also removed IPv4 related messages to make it easier to
follow.
**
** Bug watch added: GNOME Bug Tracker #748268
https://bugzilla.gnome.org/show_bug.cgi?id=748268
** Also affects: network-manager via
https://bugzilla.gnome.org/show_bug.cgi?id=748268
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a
After deleting the dhcp6${UUID}-${IF}.lease file and reconnecting the
interface the "starts" timestamp is now up to date. Not sure if this is
relevant to the internals of dhclient though.
$ cat dhclient6-0775a2a6-a4a1-40bf-bd85-9c3068582dbc-wlp3s0.lease
default-duid
Looking at the files related to dhclient managed by Network Manager
under /var/lib/NetworkManager/ I noticed that although the new lease
file seems to contain the correct (in the future) timestamps the
"timestamps" file entry for that same lease UUID is still set to the
time the original lease
Yes, seeing this too on 15.10 since around the first week of March, as
best I can tell, but irrespective of Suspend.
It looks like dhclient thinks/is told the new lease is 'depreferred' and
therefore quits, and the dhclient process is terminated, but the address
remains on the interface until the
** Changed in: isc-dhcp (Ubuntu)
Status: Invalid => In Progress
** Changed in: isc-dhcp (Ubuntu)
Importance: Low => High
** Changed in: isc-dhcp (Ubuntu)
Assignee: (unassigned) => TJ (tj)
--
You received this bug notification because you are a member of Desktop
Packag
It seems there's a deficiency in isc-dhcp client that leads to this.
Fedora have been carrying a patch since 2013 that solves it by the
simple expedient of scanning the .lease file first for unexpired leases
before allocate an address.
See:
** Summary changed:
- Failed to renew DHCPv6 lease after suspend
+ dhclient killed when DHCPv6 lease is out-of date
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1533631
** Changed in: network-manager (Ubuntu)
Assignee: (unassigned) => TJ (tj)
** Changed in: network-manager (Ubuntu)
Status: Triaged => In Progress
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in
** Changed in: isc-dhcp (Ubuntu)
Importance: High => Low
** Changed in: isc-dhcp (Ubuntu)
Status: Triaged => Invalid
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
** Description changed:
- After fixing IPv6 address assignment (#1469346), IPv6 works fine until
- sleep. On wake up ubuntu fails to renew its IPv6 lease:
+ Network Manager summarily kills the IPv6 dhclient process when the
+ DHCPv6 lease contained in the dhclient6-${UUID}.lease file is out-of
+
** Changed in: xinput (Ubuntu)
Status: Confirmed => Triaged
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xinput in Ubuntu.
https://bugs.launchpad.net/bugs/1480673
Title:
Asus T300 CHI bluetooth Touchpad is recognized
** Summary changed:
- 16,04: Asus T300 CHI: touchscreen digitiser missing at boot
+ Asus T300 CHI: Synaptics Touch Digitizer - missing at boot
** Changed in: xinput (Ubuntu)
Status: New => Triaged
** Changed in: xinput (Ubuntu)
Importance: Undecided => Medium
--
You received this
** Description changed:
This is a related but separate issue to bug #1480673 "Asus T300 CHI
bluetooth Touchpad is recognized incorrectly".
- Affecting this digitizer is also bug #1574028 "Asus T300 CHI:
- touchscreen digitiser missing at boot".
+ Affecting this digitizer is also bug
** Description changed:
+ Moved the touchscreen issues to bug #1574341 "[Asus T300 CHI] Synaptics
+ Touch Digitizer V04 - no multitouch".
+
The Asus T300 CHI has a touchscreen and a (bluetooth) keyboard/touchpad combo.
Both (touchscreen, touchpad) only work like a mouse (moving pointer, left
Public bug reported:
This is a related but separate issue to bug #1480673 "Asus T300 CHI
bluetooth Touchpad is recognized incorrectly".
Affecting this digitizer is also bug #1574028 "Asus T300 CHI:
touchscreen digitiser missing at boot".
Using 16.04 amd64 Ubuntu (unity).
In this case the
** Description changed:
This is a related but separate issue to bug #1480673 "Asus T300 CHI
bluetooth Touchpad is recognized incorrectly".
- Affecting this digitizer is also bug #1574028 "Asus T300 CHI: Synaptics
- Touch Digitizer - missing at boot".
+ Affecting this digitizer is also bug
1 - 100 of 247 matches
Mail list logo
